Question Nothing Phone 1 hangs in bootloader/fastboot mode. Not rooted and bootloader unlocked. bricked

[Sapphire86]

Hello,

I have a Nothing Phone 1 that hangs in bootloader/fastboot mode.
The bootloader is unlocked.
Unfortunately, the phone can no longer be booted into recovery mode.
With fastboot the device is still recognized.
So you could still flash files via fastboot.
The phone was not rooted.
The phone previously ran with the original stock firmware 1.1.7 hotfix.
It is an EEA device.

Is there anything that can be done?
Or is it now an expensive paperweight?

 

[ethical_haquer]

Try running "fastboot reboot recovery" in the terminal with your phone connected.

 

[Sapphire86]

Unfortunately this does not work.
Thanks for the quick reply.

 

[Sapphire86]

The device then boots back into the bootloader

 

[ethical_haquer]

It looks like they have Nothing OS downloads here. You could just try reflashing the phone through fastboot.

 

[ethical_haquer]

Looks like someone else is having the same problem. Keep an eye on that thread in case a solution comes up there.

 

[Sapphire86]

so, i have the unpacked payload.bin image files. Here fastboot tells me several errors with odm.img FAILED (remote: '(odm_b) No such partition'), with product.img FAILED (remote: 'Partition not found'), with system.img FAILED (remote: 'Partition not found'), with system_ext.img FAILED (remote: '(system_ext_b) No such partition') and with vendor.img FAILED (remote: 'Partition not found').

After a restart, the error remains.
There is also the fastbootD mode, but this does not work or does not boot.
After this command the device hangs in bootlogo (nothing).

Unfortunately very sad that there is still no solution for this. let's hope that there is soon a solution for this.

 

[ethical_haquer]

so, i have the unpacked payload.bin image files. Here fastboot tells me several errors with odm.img FAILED (remote: '(odm_b) No such partition'), with product.img FAILED (remote: 'Partition not found'), with system.img FAILED (remote: 'Partition not found'), with system_ext.img FAILED (remote: '(system_ext_b) No such partition') and with vendor.img FAILED (remote: 'Partition not found').

After a restart, the error remains.
There is also the fastbootD mode, but this does not work or does not boot.
After this command the device hangs in bootlogo (nothing).

Unfortunately very sad that there is still no solution for this. let's hope that there is soon a solution for this.

Type "fastboot reboot fastboot" in the terminal, with your phone connected, and then run "fastboot flash <yourimagename>.img".

 

[Sapphire86]

yes, when i enter this command the device restarts and hangs in the bootlogo and in the terminal it says then wait for any device. That means the Nothing Phone does not start the fastbootD mode.

 

[Sapphire86]

And if he doesn't do this, I think it looks really bad.

 

[ethical_haquer]

Are you using Windows to flash it?

 

[Sapphire86]

Yes windows 11 with the latest drivers, but I have already considered using linux.

 

[Sapphire86]

Which linux distribution would be best. Then I will download it and try it out.

 

[ethical_haquer]

I would recommend Ubuntu, if you have a spare computer to install it on (or dual boot). Just make sure you install the tools needed from here (Scroll down to the "Command line tools only" section and download the Linux version)
I only use Linux, so let me know if you have any questions.

 

[Sapphire86]

Ok thanks. I will have a look and install it on a notebook later.

 

[ziptric1805]

You have to be very careful. I had the same problem (bootloop in fastboot) and by dint of manipulation, no more fastboot, my smartphone is hard brick (black screen with logo and message key to shutdown)

 

[ethical_haquer]

You have to be very careful. I had the same problem (bootloop in fastboot) and by dint of manipulation, no more fastboot, my smartphone is hard brick (black screen with logo and message key to shutdown)

If your phone has a Qualcomm processor, you still have EDL mode.

 

[MakDroid]

It is not bricked. Just flash any cutom rom, I recommend Paranoid Android. Then revert back to stock NOS.

 

[Ostry10]

@MakDroid
I just installed Topaz 1 (A13) to save my bricked phone. How can i revert back to stock NOS from A13? There is any option or i have to wait for full rom with A13?

 

[MakDroid]

@MakDroid
I just installed Topaz 1 (A13) to save my bricked phone. How can i revert back to stock NOS from A13? There is any option or i have to wait for full rom with A13?

Download NOS 1.1.7 full from here.
Extract payload.bin and place all the extracted .img files inside a folder named "images".

Copy the images folder and the attached bat file (extract the zip to get the bat file) to the platform-tools folder.

Run the bat file and it will start flashing. Wait for it to complete and then simply update to latest version using stock updater.