Question Unbrick phone, can't enter fastboot mode.

[coomac]

Same issue from flashing a rom. Did everyone with this problem send in their phones?
Adding a video of the issue as well.

 

[JeronimoMartinss]

i sent it and i got it repaired. I didn't pay anything for now

 

[tegazinho]

Same, got mine back today, 2 weeks exactly, all good, bootloader came locked again, but no issues.

 

[nickholtus]

Sadly same here when trying to go back to stock.

Phone got rejected for warranty, repair estimatie higher then buying a new one.
After getting in touch: because bootloader is unlocked, this is not covered in warranty

 

[coomac]

Trash support from a trash company with trash QC. They refused to repair mine even if I paid for the repair. I can smell the class action lawsuit brewing from this.

 

[nickholtus]

Trash support from a trash company with trash QC. They refused to repair mine even if I paid for the repair. I can smell the class action lawsuit brewing from this.

Well, Its a risk when unlocking bootloader.
Looks like it has to do with switching active slot from B to A
So i`m going to figure out how to fix this issue myself

 

[rackis18]

Well, Its a risk when unlocking bootloader.
Looks like it has to do with switching active slot from B to A
So i`m going to figure out how to fix this issue myself

Let me know if you get any soliution

 

[coomac]

Good luck. A Nothing employee confirmed they use the Qualcomm flash image loader (QFIL) to fix these issues but not sure if they use a special cable or firmware.

Well, Its a risk when unlocking bootloader.
Looks like it has to do with switching active slot from B to A
So i`m going to figure out how to fix this issue myself

 

[mystery007]

For this we need the "firmware.mbn"-file, right? Is this somewhere to download?

 

[oddlyspaced]

I too faced this. I spent a couple of days trying to find a solution but nothing worked. Ultimately went to the service centre and they fixed it for me in like 10 minutes and they did not charge anything for it. I'm in India.

 

[Mathes26]

Do we know, what exactly is the cause of this issue and how to avoid it during the root process? Seems like too many people have this problem, it really putting me off to even try rooting...

 

[oddlyspaced]

Do we know, what exactly is the cause of this issue and how to avoid it during the root process? Seems like too many people have this problem, it really putting me off to even try rooting...

In my experience I think this seems to be a lot mismatch issue. As far as I remember, I had my device with Stock on 1 slot and Custom on another. Was unable to install stock updates so thought that I should switch slots and try again, but it just messed it up.

 

[denndenn]

For this we need the "firmware.mbn"-file, right? Is this somewhere to download?

I have found a Guide to create/Backup the phone with Qfil.

I don't know if I can share the link here.

Edit: You need a loader / programmer file. Have not found any working for now.

 

[bhatt_4]

Same issue from flashing a rom. Did everyone with this problem send in their phones?
Adding a video of the issue as well.

This issue is caused by Windows and USB flags; you can resolve it by running a script or manually adding the missing flags to the registry. https://archive.org/download/usb-flag-fix/USB_flag_fix.bat

 

[coomac]

This issue is caused by Windows and USB flags; you can resolve it by running a script or manually adding the missing flags to the registry. https://archive.org/download/usb-flag-fix/USB_flag_fix.bat

Are you posting this solution from experience? If so, can you provide more detail on how you resolved the issue on the NP1?

Changing those USB flags was one of the first things I tried. The phone doesn't reach fastboot though so fastboot commands don't work in that state.

 

[bhatt_4]

Are you posting this solution from experience? If so, can you provide more detail on how you resolved the issue on the NP1?

Changing those USB flags was one of the first things I tried. The phone doesn't reach fastboot though so fastboot commands don't work in that state.

This issue isn't limited to nothing phone one; I've seen and experienced it on my Poco f1 and other phone with usb 2.0 spec as well.

 

[coomac]

This issue isn't limited to nothing phone one; I've seen and experienced it on my Poco f1 and other phone with usb 2.0 spec as well.

Yeah I saw it on a Xiaomi phone as well but this is slightly different. With Xiaomi phones, you get the error after the bootloader loads so when you fix the usb flags on windows, the usb connection is recognized and you can run fastboot commands.

As you can see in the video, the error comes up before the bootloader is fully loaded on the Nothing phone so fixing the usb flags on windows makes no difference. I use linux normally and a usb connection is not detected there at all. I dug up a windows computer to fix the usb flags, which had no effect because nothing is loaded yet. Also tried a usb 2.0 hub.

 

[NightMean]

Sadly same here when trying to go back to stock.

Phone got rejected for warranty, repair estimatie higher then buying a new one.
After getting in touch: because bootloader is unlocked, this is not covered in warranty

There was a tweet where someone asked if unlocking bootloader will void the warranty and Paranoid Android team said that it won't. The original tweet is unfortunately deleted but their reply is still there.

https://twitter.com/i/web/status/1548439560715059200

Unfortunately I wasn't able to find a confirmation regarding bootloader unlock from Nothing directly.