yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 1] mark332:
if FRP not working even after erasing the FRP Partition then you have to Erase some other critical partition
[Nothing Phone 1] MrZaga:
Did you get it to work? My phone only reboots when pressing the two volume buttons and inserting the cable :(
[Nothing Phone 1] thisjacoob:
how to unbrick the phone when the power up screen says press any key to shutdown?

instead of boot I used flash and now I can't even turn on fastboot mode to do anything

please can it be fixed somehow?

I can't turn on edl mode using the volume buttons, I took the phone apart to try using the buttons on the back and it still doesn't work. What about this situation?
[Nothing Phone 1] AnotherM1m:
You have to short them, connect them with something that conducts electricity

Like touch them both with the metal end of a screwdriver
[Nothing Phone 1] xtcislove:
unbrick tool- EDL Flash-Read-Repair Region Change tool

unbrick tool Now available for Nothing Phone1.. other unbrick tool by Me Redmi Note 8/8T, Redmi 9T/9 Power, Poco M3,Mi A2/6x,Mi A3,Redmi Note 7/ Note 7s,Note 6 Pro Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked...

xdaforums.com

IDK what id did here sorry.
[Nothing Phone 1] thisjacoob:
I try to connect these two points and then nothing, the phone turns off and on and shows "press any key to shutdown" and the computer does not detect it
[Nothing Phone 1] Renate:
Usually connecting the points should not reset the device.

The two test points are usually 1.8V source and a GPIO pin.

Normally you have to reset by yourself the device while the points are shorted.

But, it could be otherwise on your device. I don't know.
[Nothing Phone 1] thisjacoob:
it's stuck here and there's nothing to do
[Nothing Phone 1] AnotherM1m:
So after shorting the pin the phone still needs to receive a "reset" input right?

If someone like the user is stuck in semi hard brick, they also need the modified usb cable mentioned in this guide so that the edl mode can be forced on the device, right?

@thisjacoob can you try creating a modified usb cable following this guide?

Here's how to revive your Nothing Phone 1 back to factory firmware with this unbrick tool

The EDL flashing tool is now available for everyone

www.xda-developers.com
[Nothing Phone 1] thisjacoob:
in my two cables there were no such colors, only black and red
[Nothing Phone 1] AnotherM1m:
can you take a photo and share it with us?

I also saw that some major online market sites sell edl cable for deep flash qualcomm 9008 devices
[Nothing Phone 1] thisjacoob:
there is nothing left but to order such a cable and hope that it will work
[Nothing Phone 1] Renate:
You have a "charging only" cable there. A data cable has the standard colors R-W-G-Bk.

It's possible that those aren't actually the correct test points.

If the device resets when you short them they could be about anything.

If you have a voltmeter you should check the voltages.

If someone has a working, rooted device you can even experiment with gpiotest (in my sig).

The test point method is the "gold standard" because it's not dependent on anything in flash memory.

The "test cable" method is detected during xbl or abl (I'm not sure which) and won't work if those are broken.
[Nothing Phone 1] riccardorossi64:
Solved? I'm in the same situation...

ADB devices: recognized

ADB sideload: cannot find error

Some ideas?

Thanks
[Nothing Phone 1] TheNewHEROBRINE:
Can you do adb reboot edl?
[Nothing Phone 1] lucy1983:
The tool only supports 64 bit system. Because on my 32 bit it refuses to open when I click the .exe file.
[Nothing Phone 1] lucy1983:
My mistake. I didn't had .net.framework installed. Now the tool opens.

But when backing up IMEI it is stuck here and those are the files generated in the unbricl folder:
[Nothing Phone 1] MrZaga:
Hi everyone, I currently am in a bad situation with my Nothing Phone 1:

I wanted to flash the firmware, which sadly failed. Now, I am stuck on the boot screen displaying "press any key to shutdown". I can't access Fastboot nor the bootloader. I tried the EDL mode (using volume keys and shorting the test points) which both result in the boot screen again.

Am I doing something wrong?

How can I rescue my device?
[Nothing Phone 1] lucy1983:
Keep the two wires of the cable in contact and THEN plug the USB to the phone. Keep them in contact for about 5 seconds and then release them and you will see your phone display in device manager as 9008 mode.

You don't need to press volume buttons when using the USB cable to enter EDL mode. Just touch the two wires and keep them in contact with something while you plug the USB cable into your phone.

Prior to that, you must select "firmware flash" in the tool and click start. After that connect your phone to the PC in the way I described.
[Nothing Phone 1] VaSU#:
I got this error while flashing firmware

any help?

14:53:37: ERROR: function: is_ack_successful:1089 SAHARA_NAK_INVALID_IMAGE_TYPE
14:53:37: ERROR: function: sahara_start:953 Exiting abruptly
14:53:37: ERROR: function: sahara_main:982 Sahara protocol error
14:53:37: ERROR: function: main:320 Uploading Image using Sahara protocol failed
14:53:39: {ERROR: Failed to open com port '\\.\COM3'}

My PC is in test mode

Phone is in qdloader 9008
[Nothing Phone 1] lucy1983:
What usb port are you using? 2.0 or 3.0?
[Nothing Phone 1] VaSU#:
usb 3.0

my pc doesnt have a 2.0 port
[Nothing Phone 1] Renate:
It looks like you tried to send your device firmware.

You first have to send it a Firehose loader.

Please quote your command line along with the response.

(And using [code] looks prettier than [icode] for multi-line.)
[Nothing Phone 1] lucy1983:
That's the problem. Try to get an adapter from 3.0 to 2.0 or use another pc.
[Nothing Phone 1] VaSU#:
Alright, I will try that with USB 2.0 Thank you!
[Nothing Phone 1] VaSU#:
i got the same error with usb 2.0

it flashes for a while then lists a bunch of done and then displays this message
[Nothing Phone 1] lucy1983:
Describe the procedure you are doing step by step, please.
[Nothing Phone 1] VaSU#:
Alright

My phone got stuck in edl while I was testing a custom rom

I plugged it into the laptop and it said QUSB_BULK

then I installed the drivers and it showed Qualcomm HS-USB Diagnostics 900E

Then I changed the drivers to Qualcomm HS-USB QDLoader 9008

Now I plug it in and press start while using the tool and this error occurs after few minutes
[Nothing Phone 1] lucy1983:
So you changed the drivers manually, selecting what was of interest for you, in the device manager?

If yes, it is not the right way. You must install this .exe file to install them correctly.
[Nothing Phone 1] VaSU#:
If i install that i get Qualcomm HS-USB Diagnostics 900E
[Nothing Phone 1] lucy1983:
You said your pc only has usb 3.0. Did you tried on another pc or did you get an adaptor? If yes you installed the drivers and the phone came up as diagnostics 900E on the other pc?
[Nothing Phone 1] VaSU#:
Yeah i used another laptop and installed the same driver

I currently have 2 laptops (a spare) and tried all the following combination

USB c (thunderbolt 4 cable and port) to USB c

USB a 3.0 to USB c

USB a 2.0 to USB c

USB a 3.1 to USB c
[Nothing Phone 1] lucy1983:
I think that .exe file contains al Qualcomm diagnostics drivers. But it is strange for you it automatically delivers the 900E. For me it is seeing the phone like 9008 automatically when I put it into EDL mode.

How did you go to EDL? By cable?
[Nothing Phone 1] VaSU#:
my phone just rebooted to it. I have no idea how it ended up there. the entire phone is blank and I cant get out of it
[Nothing Phone 1] Renate:
The problem is that you're using a handy-dandy tool that is hiding all the details from you.

You don't even know what file that tool was trying to upload to Sahara as a Firehose loader.

Sahara has clearly said, "That is not a Firehose loader!"

You can't argue with that because you have no idea what file they meant.

Add to that the stupid virtual com port drivers and you're in superstition land.

"Well, it worked when I used a green cable with a right angle adapter..."

How to get on a scientific basis:

Figure out (presumably in that 2.6 GB) what is your Fireshose loader

Just use a generic EDL client with WinUsb drivers
[Nothing Phone 1] lucy1983:
Then you need to use a edl cable to reboot once again into EDL. Because EDL state gets automatically reset after 10-15 seconds if the phone it is not recognised correctly by the PC. That's why it get recognised only in diagnostics 900E.
[Nothing Phone 1] VaSU#:
ah ok thank you!
[Nothing Phone 1] lucy1983:
The first image is the content of the qfil firmware that can be used with a generic flasher like QPST and it contains an obvious programmer.

The second image is the content of the folder that contains the tool from this specific post, developed by mark332. So this are the files that the tool is using for edl flash. And it worked 100% for me. I flashed it several times when I wanted to go back to stock from custom rom.
[Nothing Phone 1] lucy1983:
You know how to make a EDL cable from a regular usb A to usb C one?

It's looking like in the picture. You must unpeal the isolation from the green and the black wire. Then you must keep those two wires in contact with something (preferable metalic), plug in the type C end to your phone, wait for about 5 seconds and then release the two wires and make sure they do not touch again. At that moment your phone will be displayed in device manager as 9008 diagnostics mode.

And if you opened the tool and clicked "start" button before doing the procedure with the cable, then the flashing will automatically start without doing anything else.
[Nothing Phone 1] VaSU#:
I would rather not waste a good cable

Gonna give it to the service center

Thank you so much for your help!!
[Nothing Phone 1] the_raz:
After flashing 1.1.3 EEA super.img and then flashing 1.0.2 FULL firmware with flash_all.bat script every partition flash on A is successful. Before the script reboot it does --set-active=b which had some partition flashes failing, like odm_b, vendor_b, system_b, system_ext_b, and product_b with the error code: FAILED (remote: 'No such file or directory'). So after reboot that goes to fastboot menu, i do --set-active=a and fastboot reboot - instantly device shows up in devmgmt as Qualcomm HS-USB Diagnostics 900E (why?).. Nonetheless, to go ontopic - I run this unbrick tool in EDL mode without errors exiting with

17:54:37: INFO: | |

17:54:37: INFO: __| | ___ _ __ ___

17:54:37: INFO: / _` |/ _ \| '_ \ / _ \

17:54:37: INFO: | (_| | (_) | | | | __/

17:54:37: INFO: \__,_|\___/|_| |_|\___|

17:54:37: INFO: {All Finished Successfully}

but still as soon as the phone reboots it's still stuck in fastboot-mode.. Any suggestions? I'll attach the port_trace.txt log-file in case that helps.

PLEASE if someone could lend some knowledge, been stuck on trying to unbrick this phone for a week now with all kinds of different firmwares and methods. All help is appreciated!!😐

EDIT: I've noticed that all the features of the tool listed on the 1st page say blabla (EDL) (locked bootloader) etc. Does that mean I should lock flashing and flashing_critical using fastboot before managing to get the device stuck in EDL mode for the next try using this tool?😅 Also worth to mention perhaps -firmware when brick happened was 1.1.7 EEA magisk patched.
[Nothing Phone 1] lucy1983:
It would help if you can describe the steps you did for flashing using the unbrick tool.

Anyway, to answer you last questions, no, it is not necessary to lock the bootloader before using this tool. I've used it successfully several times with an unlocked bootloader.
[Nothing Phone 1] the_raz:
Sorry for late reply. Here are the exact steps I'm doing (will also attach a .log of everything):

1. Flash 1.1.3 EEA super partition -fastboot flash super ./super.img with 9/9 successful.

2. ./flash_all.bat with 1.1.3 EEA firmware downloaded from download.ps1. FAILED (remote: 'No such file or directory') on a few partitions, e.x.: odm_a, product_a,system_a, system_ext_a, vendor_a. On b-partition I get FAILED (remote: 'Not enough space to resize partition') for system_b. Doesn't matter if try to flash system in fastboot or fastbootd it gives the same error..

fastboot is version 34.0.1-9680074

3. Delete all the logical partitions that gave me error and recreate new one including -cow partitions and create all new with fastboot create-logical-partition xxxx _a/b 100000 which allows me to flash them again successfully. Reboot into recovery and wipe data/factory reset then reboot straight into Qualcomm HS-USB Diagnostics 900E COM5 in devmgmt...

4. Udr unbrick-tool osv1.1.7 without any issues, see port_trace file. After automatic reboot straight into fastboot-bootloop again... I'm about 5 more attemptfrom throwing away this **** for good now...
[Nothing Phone 1] lucy1983:
Onestly, i don't understand why you complicated things so much. In the post instructions doesn't mention anything about flashing super.img and going to fastboot mode.

Just execute the .exe file in the unbrick folder, select "firmware", press "start", boot the phone into EDL MODE (not fastboot) and the flashing will automatically start. When it is finished the phone will reboot automatically also.
[Nothing Phone 1] the_raz:
Because I was following this guide: https://xdaforums.com/t/how-to-unbrick-nothing-phone-1-fastboot-bootloop.4501439/. Also I did just that after it failed. Here's port_trace.txt https://www.file.io/rNES/download/dcocHYiSA0Ng still when using this EDL flasdh tool reboots into fastboot loop.
[Nothing Phone 1] lucy1983:
In what state it your phone now? It is booting or not?

Do you have the Qualcomm drivers installed witch allows your PC to recognize the phone into EDL mode?

If your phone it is recognized properly in EDL mode by the PC, then starts the tool by executing the .exe file as administrator and do what I told you in my previous post.

Also use a USB 2.0 port on your PC because USB 3.0 generates problems of connection.
[Nothing Phone 1] lucy1983:
And use the tool listed in THIS post, not the one from the post you followed and that messed up your phone.
[Nothing Phone 1] the_raz:
Waiting for EDL Device, Please Connect in EDL Mod

Connecting to Device: OKAY

Sending Loader: Done ✓

Total to be tansferd with <program> or <read> is 6.11 GB

Writing > misc.img: Done ✓

Writing > super_.img: Done ✓

Writing > super_.img: Done ✓

Writing > super_.img: Done ✓

Writing > super_.img: Done ✓

Writing > super_.img: Done ✓

Writing > super_.img: Done ✓

Writing > vbmeta_system.img: Done ✓

Writing > vbmeta_system.img: Done ✓

Writing > metadata_.img: Done ✓

Writing > metadata_.img: Done ✓

Writing > userdata_.img: Done ✓

Writing > userdata_.img: Done ✓

Writing > userdata_.img: Done ✓

Writing > userdata_.img: Done ✓

Writing > userdata_.img: Done ✓

Writing > userdata_.img: Done ✓

Writing > userdata_.img: Done ✓

Writing > userdata_.img: Done ✓

Writing > userdata_.img: Done ✓

Writing > userdata_.img: Done ✓

Writing > userdata_.img: Done ✓

Writing > gpt_main.bin: Done ✓

Writing > gpt_backup.bin: Done ✓

Writing > xbl.elf: Done ✓

Writing > xbl_config.elf: Done ✓

Writing > gpt_main.bin: Done ✓

Writing > gpt_backup.bin: Done ✓

Writing > xbl.elf: Done ✓

Writing > xbl_config.elf: Done ✓

Writing > gpt_main.bin: Done ✓

Writing > gpt_backup.bin: Done ✓

Writing > gpt_main.bin: Done ✓

Writing > gpt_backup.bin: Done ✓

Writing > aop.mbn: Done ✓

Writing > tz.mbn: Done ✓

Writing > hypvm.mbn: Done ✓

Writing > NON-HLOS.bin: Done ✓

Writing > BTFM.bin: Done ✓

Writing > abl.elf: Done ✓

Writing > dspso.bin: Done ✓

Writing > km.mbn: Done ✓

Writing > boot.img: Done ✓

Writing > devcfg.mbn: Done ✓

Writing > qupvfw.elf: Done ✓

Writing > vbmeta.img: Done ✓

Writing > dtbo.img: Done ✓

Writing > uefi_sec.mbn: Done ✓

Writing > imagefv.elf: Done ✓

Writing > shrm.elf: Done ✓

Writing > multi_image.mbn: Done ✓

Writing > cpucp.elf: Done ✓

Writing > featenabler.mbn: Done ✓

Writing > vendor_boot.img: Done ✓

Writing > aop.mbn: Done ✓

Writing > tz.mbn: Done ✓

Writing > hypvm.mbn: Done ✓

Writing > NON-HLOS.bin: Done ✓

Writing > BTFM.bin: Done ✓

Writing > abl.elf: Done ✓

Writing > dspso.bin: Done ✓

Writing > km.mbn: Done ✓

Writing > boot.img: Done ✓

Writing > devcfg.mbn: Done ✓

Writing > qupvfw.elf: Done ✓

Writing > vbmeta.img: Done ✓

Writing > dtbo.img: Done ✓

Writing > uefi_sec.mbn: Done ✓

Writing > imagefv.elf: Done ✓

Writing > shrm.elf: Done ✓

Writing > multi_image.mbn: Done ✓

Writing > cpucp.elf: Done ✓

Writing > featenabler.mbn: Done ✓

Writing > vendor_boot.img: Done ✓

Writing > logfs_ufs_mb.bin: Done ✓

Writing > storsec.mbn: Done ✓

Writing > rtice.mbn: Done ✓

Writing > gpt_main.bin: Done ✓

Writing > gpt_backup.bin: Done ✓

Writing > gpt_main.bin: Done ✓

Writing > gpt_backup.bin: Done ✓

Success!

Phone still doesn't boot. Reboots into "The bootloader is unlocked bla bla" then shows Nothing Phone screen a few seconds, goes black and then repeat. And now after the 20th try in bootloop it went to fastbootmenu, unable to boot into recovery mode via choosing on phone or via fastboot reboot recovery.

Edit: I can get into recovery mode after --set-active=other but still not booting..
[Nothing Phone 1] lucy1983:
If you can go to recovery try to perform a factory reset.
[Nothing Phone 1] lucy1983:
If that doesn't work, boot into fastboot and send command "fastboot -w" or "fastboot erase userdata".
[Nothing Phone 1] the_raz:
C:\ADB>fastboot -w

Erasing 'userdata' OKAY [ 0.067s]

Erase successful, but not automatically formatting.

File system type raw not supported.

Erasing 'metadata' OKAY [ 0.004s]

Erase successful, but not automatically formatting.

File system type raw not supported.

Finished. Total time: 0.125s

C:\ADB>fastboot erase userdata

Erasing 'userdata' OKAY [ 0.068s]

Finished. Total time: 0.078s

fastboot reboot -> straight to fastbootmenu again.. Fml might have to send the phone to nothing or something.. But I don't understand, fastboot getvar all looks good (at leastd in my nooby opinon, compared to what it has looked like with all empty and on versions etc). Idk if it's so close to working or not but the computer recognizes in usbdeview and shows up as A063 which it hasnt done before..

I also did fastboot -w on slot a but there it created a new and formatted as opposed to b(?):

Spoiler content hidden.

Don't know if getvar all says anything but Ill post it ianyways.

C:\ADB>fastboot getvar all

Spoiler content hidden.
[Nothing Phone 1] lucy1983:
Try to run this commands from the LATEST platform tools folder in drive C, not the "adb" folder (i suppose you have the 15 seconds adb installed, if yes, then install latest platform tools - just Google it "platform tools" and acces the Google site).

Also, did you use USB 2.0 port?

Also, you did a format data/factory reset from recovery?
[Nothing Phone 1] Mr.N0nE:
I have tried to use the Read Firmware function but I received this error below. Does anyone else have the same issue? I was able to do Firmware Flash without any issue.

Is this the way how boot.img firmware is being dumped from incremental OTAs?

Waiting for EDL Device, Please Connect in EDL Mod
Connecting to Device: OKAY
Sending Loader: 18:21:53: ERROR: function: sahara_rx_data:286 Command packet length 1702240364 too large to fit
18:21:53: ERROR: function: sahara_main:982 Sahara protocol error
18:21:53: ERROR: function: main:320 Uploading Image using Sahara protocol failed
18:21:54: {ERROR: Option 'Phone' does not begin with --
ERROR: Could not append to 'port_trace.txt'
[Nothing Phone 1] kumar akarsh:
flash fastboot ROM if u can enter bootloader
[Nothing Phone 1] rogerrulez:
Try changing the active slot and see if it boots up.

These phones were made not to be messed with like other android phones. I don't like Nothing's approach to this idea and I will most likely not buy another. It looks like an iphone and acts like an iphone.
[Nothing Phone 1] the_raz:
Bootloop on slot b, slot a goes to fastbootmode bootloader only, can get into Recovery by fastboot command butnerasing userdata and metadata with -w doesnt help. Does it matter that this is a eu Phone? In Recovery logs there is 10 or more error msgs saying something about failed to load bitmap bla bla locale en_us failed with code -1.

Also factory resetting says "open failed: metadata/ota: No such file or directory" bit it formats data and metadata.

Tried with latest platform tools also minimal adb fastboot v 1.4.2-3 on win and Linux.

Can i adb sideload a newer patch even though its bricked or wont that do anything?

And also i agree,this is absurd. There is no excuse the phone wont boot after edl flash. Its pissing me off to the point i might just throw it into a million pieces straight into the wall soon.. pic is gargabe quality because Ive been stuck with a ****ty ass phone for months now
[Nothing Phone 1] rogerrulez:
No, it doesn't matter if it's an EU version or not. I think I read the whole thread and if I remember correctly you did everything right. But a couple of questions that I think you have already answered,

1. Did you unlock the critical partition before you tried the EDL method ?

2. Did you go into recovery, can you go into recovery, from the bootloader ? And if so, although you ran the command to erase, did you erase everything from within the recovery mode ?

Someone else had your same issue. I had a similar issue where it would just boot into the bootloader. Twice ! Second time was when I relocked the bootloader.

But all I had to do was fastboot flash version 1.5.2 on both partitions after unlocking bootloader and critical. Then before the phone tried to boot up I stopped it and went into recovery(which I read in another thread to do) and did a full wipe. Then started the phone from there. Twice it was successful and it booted up just fine. But I could not get the ota for version 1.5.3. So I fastboot flashed 1.5.3. Then when it booted up I was able to get the ota's.

I must say this is a messed up phone that is not root friendly. I'm not happy with that. They seemed to have made it as much identical with the iphone not only in looks but also in software. I doubt I will go with the Nothing 2. Android phones should not be this difficult.
[Nothing Phone 1] rogerrulez:
Yes, using the factory reset option in recovery mode. Sounds like you have a corrupt partition somewhere. Some people say to just flash the super.img. But personally, to save you more time and grief I would start from scratch.

Yes. There are links in this forum for the flashboot images. Insides of them are two .bat files. Flash a slot and flash b slot. Just doubleclick on each and they will do the rest.

Before you do make sure both the bootloader and critical partitions are unlocked. Run the command on the critical regardless, just in case.

If you I would downlaod the 1.17 fastboot ROM. The 1.5.2 Fastboot ROM and the 1.5.3 fastboot ROM. Extract each in their own folders. Start with 1.1.7 and then go up to 1.5.2 and not allow the phone to try and boot. Before you try to boot after flashing 1.5.2 clear everything in recovery mode. If everything goes right, and it should, you an see if there is an available update using the normal method. But I don;t think it would work. No worries. Go back to bootloader and make sure critical is unlocked and flash 1.5.3. Then everything should be good. Just make sure you do them in order.
[Nothing Phone 1] kumar akarsh:
Flash ROM in fastboot. here
[Nothing Phone 1] AnotherM1m:
Hello! I'm searching for uefisecapp.img partition for 152, did anyone do a full backup on 152 and can share that partition?
[Nothing Phone 1] thesm4rt1:
I can confirm this has fixed the "Any key to shutdown" bootloop issue for me. I spliced a USB-C cable crossing the green+black cables for a few seconds while plugging in the phone with both volume keys pressed. OP's software was already running in "Firmware Flash" mode.
[Nothing Phone 1] lucy1983:
It is not mandatory to press the volume buttons. Just plug in the cable while the two wires are in contact and release them after 5 seconds.
[Nothing Phone 1] thesm4rt1:
Good to know. Saw the volume button instructions in one of the comments so figured it wouldn't hurt.