yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 1] iodemos:
My first 'regular' USB-A to USB-C only had three wires. With a four-wire USB-A to USB-C, I was able to revive my NP1 without opening it.
[Nothing Phone 1] maverixz:
Can you share how you restored it because I have not be able to restore mien despite haviung seen no failures in the process. Btw, I have a retail EDL cable.
[Nothing Phone 1] AnotherM1m:
@mark332 Hi!

Is it possible to have the source code of the program? i would be interested in studying the commands launched with edl for unbricking devices
[Nothing Phone 1] nawzo:
anyway to fix this?
[Nothing Phone 1] lucy1983:
Try clicking on "start" button BEFORE booting the phone to edl mode. Also in the device manager how is your phone listed?
[Nothing Phone 1] maverixz:
I was told there is a newer version of this EDL tool you created. Is that true and can you provide a download link for the newer version?
[Nothing Phone 1] ayed78:
how to solve this?
[Nothing Phone 1] lucy1983:
There is a timeout of 10 seconds aprox for your phone to stay in edl mode. If those 10 seconds pass without begining flash your phone will automatically exit edl mode.

To make sure you "catch" that short interval it is recommended to first click the "flash firmware" and only after that to put your phone into edl mode (either using a edl cable - if you phone doesn't boot or using command "adb reboot edl" - if your phone is able to boot into system). Flashing will automatically start when the program detects your phone into edl mode.
[Nothing Phone 1] ayed78:
i will try..thanks
[Nothing Phone 1] jerkyeights:
Ye ahhh
[Nothing Phone 1] M.Mosa007:
can you provide same package for nothing 2? or where should we find edl packages for nothing phone's

is there any specific or company site?
[Nothing Phone 1] mark332:
nothing for nothing 2, one edl package available in the market which is also encrypted and look like official nothing flashing utility
[Nothing Phone 1] M.Mosa007:
can you provide me the official link plz
[Nothing Phone 1] mark332:
no i don't have, some people selling it, you have to contact them on telegram
[Nothing Phone 1] M.Mosa007:
who have can you pass me contact
[Nothing Phone 1] NooBsteR2000:
I feel like im outta luck now. Idek how i bricked my device, I can still enter fastboot and use commands, but recovery and system are both dead. My /data partition also seems to be a bit funky because i can neither mount nor erase it in fastboot. Erasing through the tool in EDL mode also doesnt work.

I can make it into EDL mode without a fancy cable, however i keep getting this error when trying to flash firmware;

Waiting for EDL Device, Please Connect in EDL Mod

Connecting to Device: OKAY

Sending Loader: 23:09:39: ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes.

23:09:39: ERROR: function: sahara_main:982 Sahara protocol error

23:09:39: ERROR: function: main:320 Uploading Image using Sahara protocol failed

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

23:09:40: {ERROR: XML not formed correctly. Expected a &lt; character at loc 0}

23:09:40: {ERROR: 3. TAG not found or recognized}

23:09:40: {ERROR:

I dont know what any of this means unfortunately, and im beginning to wonder if my phone is an actual dud now. If someone could help me revive my phone, i would be very grateful for that. Or just tell me that its indeed a dud if thats the case
[Nothing Phone 1] ayed78:
mine boot on bootloader...but flash rom not boot to OS,any way to figure it?
[Nothing Phone 1] nontheoretical:
I was able to unbrick my phone from a black screen no boot with this amazing tool!

I bought a cheap EDL cable online with a button that acts as the green and black wire trick.

For anyone who might have run into the same issues I did, here are the exact steps I used:

Install Qualcomm drivers

Run the tool

Start flash mode in tool

Hold down Power + Volume Down button to turn off phone

Plugged EDL cable into a USB 3.0 port

Insert EDL cable with button pressed into phone

Immediately let go of Power and Volume down buttons after cable inserted

Wait 5 seconds

Let go of button on cable

Nothing Phone 1 boots into 9008 mode - but there is a warning icon in device manager

Bunch of errors in the tool's logs

Check windows update - it updates the Qualcomm drivers

Phone still in 9008 mode but this time no warning in device manager

Run the flash mode again

Flashing sequence starts

After a "Success" message, phone reboots

I thought this phone was fully dead, no backlight, no response, nothing.

Now it's back and I'm updating to the latest Nothing OS and can use my phone once more!
[Nothing Phone 1] lucy1983:
No phone is ever dead if it has available an EDL firmware that we can flash :)), unless there is a hardware problem. In that case the only solution is to change the motherboard.

By the way, maybe your phone didn't get recognized immediately in 9008 mode because you didn't install the 9008 drivers, only the Qualcomm ones.

Normally, if you have the 9008 drivers installed, the phone gets automatically recognized in Qualcomm 9008 mode as soon as you let go of the bottom (or separate the two wires if you have a homemade EDL cable).
[Nothing Phone 1] BrownTurtleBear:
Hi. I am looking to buying a cord for this tool. Can someone please suggest me one? I don't really understand the requirements of this. Thank you
[Nothing Phone 1] Renate:
"Invalid image type" probably means you are trying to load a 32 bit ELF when it wants a 64 bit ELF (or the other way around).

As always, you have no idea what file this was trying to load.
[Nothing Phone 1] ayed78:
mother issue...ufs storage broken
[Nothing Phone 1] Renate:
That may or may not be true.

In any case, that error is coming out of the PBL before it even knows/cares/looks what you have for flash.

Figure out what file it was trying to load.
[Nothing Phone 1] ayed78:
phone doesn't boot and no os install
[Nothing Phone 1] Renate:
So what?

You may have wiped the entire flash.

You've not made any attempt to load the correct Firehose loader.

You don't know what file you tried to load.

You don't know your HWID or the PKHASH.
[Nothing Phone 1] ayed78:
im follow instruction nothing more than that
[Nothing Phone 1] Renate:
Then you'll either need to get assistance from the OP or else pursue this yourself using generic EDL tools.

Google "bkerler edl" or use my EDL client in my sig.
[Nothing Phone 1] ayed78:
send to service center
[Nothing Phone 1] Renate:
You'll not win XDA's "Adventurous Spirit of the Year" 2023 award by sending things off to be repaired.
[Nothing Phone 1] ayed78:
i try out way and nothing is flash in phone...im check that ufs storage issue..even custom rom stock not stick in...only fastboot no recovery..this came from nothing crashdump issue
[Nothing Phone 1] Renate:
As I said, try the bkerler EDL client. That still works with the brain-dead Qualcomm drivers.

If you're going to send it in anyway, what do you have to lose?
[Nothing Phone 1] ayed78:
i dont lose any..what i predict is right after i send and what tech there said related what im figure.
[Nothing Phone 1] mark332:
the USB COM is invalid you replace a 900E use driver with 9008 which is invalid, use EDL cable to access Proper 9008 Mod
[Nothing Phone 1] nothingphone1:
Please help!​

I have my phone connected in edl mode but when I try to run your tool It just freezes and is stuck at this screen ""
[Nothing Phone 1] mark332:
send it to service center, if they ask to change motherboard take phone back & dm me

update driver, there is no 9008 device in device manager (may be it's qcom bulk)
[Nothing Phone 1] ayed78:
im already take back myphone
[Nothing Phone 1] lucy1983:
Hello. I made the mistake to not backup my persist partition and ended up losing the fingerprint functionalitty and the serial number of the phone. All the other sensors and functions work well and the size of my persist partition is 32 mb right now (i used root and termux to extract the current persist.img witch is broken). I tried to go back to stock using the latest Miflash method and lost persist. In the past i always used your tool to go back to stock and never had any problems.

You have any ideea if i can fix it without a backup or just send it to the service center?
[Nothing Phone 1] MyToasterBroke:
Thanks so much for this tool, my NP1 was crashing upwards of 10 times a day and this seems to have fixed it after running. The only issue I'm currently facing is that while I have the option to enroll a fingerprint, and the light of the scanner comes on, there's no vibration for actually registering the fingerprint etc.

Have I missed something around region? Tried relocking the bootloader, installing a plethora of custom roms but all of them have the same issue. The only persistent issue that might be of use is that all roms have no available serial number in the Phone info.
[Nothing Phone 1] lucy1983:
The exact same thing happent to me yesterday. No fingerprint and no serial number in phone settings. We both have broken persist partition and no backup. Hopefully somebody know a way ro recover. Else only sending it to service center can fix it.
[Nothing Phone 1] MyToasterBroke:
Damn, thanks for clarifying though! Tried a friends persist.img but had no luck like a couple others did. I'll take a stable phone over the fingerprint reader but sad that my lack of understanding resulted in the tradeoff.
[Nothing Phone 1] lucy1983:
Fingerprint Sensor Not Working after unbricking phone

Long story short, I bricked my device very hard, very many times while trying out different ROMS and getting accustomed to handling fastboot and adb. At some point along the journey I must've broken something to do with the fingerprint sensor (or...

xdaforums.com

Try to flash the persist.img provided in this thread in fastboot mode using the command "fastboot flash persist persist.img". I just did and the serial number of my phone came back.

But still I cannot enroll the fingerprint. The sensor lights up but it doesn't vibrate to enroll.
[Nothing Phone 1] MyToasterBroke:
I get the same result with that persist.img too. Might see if Nothing will fix the problem and what the quote is for it, but sending from New Zealand would probably cost more than it's worth. I'll keep an eye on this thread in hopes of a fix/workaround in the coming months. 😅
[Nothing Phone 1] chaos_since_78:
Hi,

first of all I really have to say thank you for this unbrick tool for Nothing Phone 1. It really brought my phone back to life. It was stuck in fastboot loop. I couldn't install anything because some partitions were missing and therefore could it not be updated with a custom rom. I probably messed the partions up. I think it all started when I tried to relock the bootloader to get OTAs working again.

However, I have some questions:

1. After flashing with unbrick tool me boot loader is still unlocked. Is that correct?

2. I updated the phone to the latest firmware. For some reason it worked via OTA which was previously not possible because an error message appeared everytime saying my bootloader was unlocked.

3. If I try to boot to recovery there is only this picture of the android on its back and the message "no command". Whats that about?

I installed the magisk boot.img from the other thread for version 2.0.2 and so far it works quite well.

Best regards

Joe
[Nothing Phone 1] skyNET:
Dear Mark332, can we directly downgrade our phone from 1.5.X to 1.1.7 using this tool?
[Nothing Phone 1] lucy1983:
Yes. Downgrade to stock 1.1.7 or return to stock 1.1.7 from custom ROM.
[Nothing Phone 1] skyNET:
Thanks for your answer. So, will this process cause fingerprint corruption or the problems you mentioned? I return from Nothing Os 2.02 to 1.1.7. Sorry for asking like this, but i must make sure before doing this.
[Nothing Phone 1] Renate:
Everything will work provided that the versions of the kernel modules (whatever.ko, inside /vendor, /product, /oem) agree with the version of the kernel (in the boot image).

This will be true if you consistently upgraded/downgraded everything.

Thow a mismatched boot image (with a different version kernel) in and you will break things.

This usually happens when somebody installs a Magisk'ed boot image that they got somewhere off the 'net instead of using the correct image.
[Nothing Phone 1] the-ebrahim:
Hi all , kindly help me , to understand this new device nothing Phone 1, weird device till now .I have fair experience with rooting and magisk ,not even single phone got hard bricked , I bought it new 2days back bcz it support custom roms

1. First I updated from 1.1.7 came out of box ,in incremental way till 2.0.2 then I unlocked it's bootloader

2. I then downloaded magisk patched boot image from xda thread of rom nothing phone 1 of exact version of my official rom 2.0.2.

3 then i installed magisk by using direct install method ,. But safety net was failing so i switched to delta-magisk by installing its apk and giving root permissions then direct install method (in past all other phones passed safetynet , banking apps worked via delta-magisk)

4. Then safety net was still failing , i installed tried one by one bunch of safety net fix modules in delta magisk . I install shamikoo in delta magisk , which was my big mistake after reading its faq .

5 then ui was crashing , everything was crashing system , apps ,

6then i reboot to fastboot mode and flashed official fastboot rom of version nothing os 2.0.2 from that chinese github link , all roms are there , by flash all. Bat , process completed.

7. But it then was soft bricked only directly booting in fastboot mode , then i tried lower version of offical rom , then 1.1.7 worked , it booted successfully , but updates are not working , something error 29 ,did research came to know i messed up partion table .

8.. then i thought of installing custom rom , project elixir , followed all steps flashed both boot and vender boot files , then format data then sideload via adb , it successfully flashed

9. Write after rebooting it gone in qualcom qfil mode , hard bricked nothing was comming adb , fastboot , why this happened ,can you explain what i did wrong ?

10. Then made edl cable at home , used unbricktool , from xda then it n

Viola it booted , the unbrick tool installed nothing os 1.1.7 then now i updated to 1.1.8 , so now tell me how to install custom rom , and what are those boot and vender boot files , also should i first update to official 2.0.2 .

11. After experiencing hard brick and near heart attack , dont want to do anything without help of you guys

12. Tell me What i did wrong step ,so that i can aware of it next time. technically it should have boot after installing custom rom elixir as we are changing boot and vender boot which i messed up earlier and new system flashed via adb sideload , i dont know how it went to qfil mode , hard bricked , definetley not a root friendly phone
[Nothing Phone 1] lucy1983:
Fastboot roms from that Chinese site have an incomplete flashall.bat file, witch result in not all the partition the phone needs to be flashed. Now you have to decide what method you want to go with, fastboot one or edl one. Do not combine those two.

I always use the edl method from this post to go back go stock rom.

But once I used the fastboot method. In this method you have to replace the original flashall.bat file from the extracted fastboot rom with a modified one, made by one of the contributors here in XDA, that makes sure it flashes all the partitions correctly. And after that you can update via OTA or DIALER method.

For flashing custom roms you don't need to previously be on latest 2.0.2 stock rom, because as you said you flash a different boot and vendor boot partitions (ones for the specific custom ROM you want to install).

My guess is you messed up some of the partitions and that's why you got a brick.

So please choose a method, fastboot or edl, and stick with it, do not combine them.
[Nothing Phone 1] lucy1983:
GitHub - LukeSkyD/NP1-FLASH-ALL-SCRIPT: Script to flash fastboot rom to your NP1

Script to flash fastboot rom to your NP1. Contribute to LukeSkyD/NP1-FLASH-ALL-SCRIPT development by creating an account on GitHub.

github.com

This is the file you have to replace in the original fastboot roms from the Chinese site.
[Nothing Phone 1] mspice96:
Hello,

unfortunately the tool does not seem to work for me.

Can anyone help me?
[Nothing Phone 1] mspice96:
Hey,

Thanks for your reply.

I've now managed it on the third pass... in Germany we say: "Alle Guten Dinge sind Drei".

That means literally translated: All good things come in threes.

I have no idea what I did differently this time though. :)
[Nothing Phone 1] the-ebrahim:
hi ,point 1

as you said to use fastboot or edl to go back to stock, does edl method is designed or created to be used as often ?, i mean it should be used only in emergencies and if some voltages got extra while flashing , it may mess up motherboard itself , this are just my thoughts , i am just saying fastboot is meant to be flashed as many times you want ,its safe and it will not mess up motherboard , and edl is meant for emergencies only, we cant make it default choice for flashing , also there is no guarantee edl will work all-time ,everytime ,and recover your Hardrick devices , it just luck and based on so many variables , permutation , combinations you may do mother board damage. you can say i got lucky that device recovered from flashing edl mode , in this case ,AM i correct ?

point 2

after step 7 in my original post , i said it was only booting in fastboot mode , before installing custom , was from that point itself hard bricked , can you tell at steep i got hard bricked it .
[Nothing Phone 1] allu.saarivirta:
Thanks friend, you saved my ass!
[Nothing Phone 1] M.Mosa007:
same error with me how you fixed that
[Nothing Phone 1] the-ebrahim:
lets connect for nothing phone 1 , you posted in thread of .what you have done to your phone which lead to hard brick
[Nothing Phone 1] Renate:
I can use EDL for everything and I do.

Some of the bad reputation EDL gets is because of all the stupid and bad implementations of EDL clients.

QFIL was designed for factory use just to slam in everything into an empty device.

How many times have you seen people complain that they bricked their device because they pushed the big button on the wrong software for their device?

Qualcomm got stuck on this "everything is a serial port" kick and I don't think that it has helped reliability.

Interacting with a device directly over a pair of bulk USB endpoints is better that using some stupid virtual com port.

Many other implementation suffer from stupid error reporting.

Simple errors should cause simple error messages.

That is, unless you're Windows Power Shell:

PS C:\> sdfsdf
sdfsdf : The term 'sdfsdf' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ sdfsdf
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: (sdfsdf:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

See also the mumbo-jumbo on Post #154
[Nothing Phone 1] stev0prince:
Please help. I tried on several computers with the same error. Note that my device does not work at all due to faulty software, but it enters edl mode by simply connecting it to the computer.
[Nothing Phone 1] Renate:
You might have another program that is already connected to Com10.

As a test (and only a test) you can try using Putty (a terminal program) to see if you can connect to Com10.

Obviously, a terminal program can do nothing since it doesn't speak the right protocol.

But you should be able to connect.

If you can locate which loader file this is using you can try using a generic EDL client to at least load the loader.
[Nothing Phone 1] falcon4fun:
Had the same problem.

Case:

Upgraded firmware from fastboot instead of bootloader

set_active command failed. Flash commands completed

Black screen phone after fastboot upgrade to 2.5.2

QUSB device inside DeviceManager without drivers

9008 COM device inside DeviceManager after installing drivers

The same error when sending loader

ERROR: function: sahara_rx_data:276: Unable to read packet header. Only read 0 bytes

And etc..

Resolution:

Disconnect all cables (used ordinary USB-A to USB-C)

Press volume down + power for 30s (I don't give a ****, waited 1m)

Wait just in case some time

Prepare unbrick tool (launch it)

Press volume up+down and hold

After 3s connect usb cable

Immidiately press Start

Wait for success and reboot.

Hooraaaay!

If unsuccess try this again from 1 step with volume down+power in step 5

As somebody mentioned: EDL ordinary waits around 10s, then it cancels this mode.
[Nothing Phone 1] IkeaShelf:
Same problem. I'm going to try your solution. I will notice you

Still no working
[Nothing Phone 1] falcon4fun:
Have u tryed EDL cable mod?
[Nothing Phone 1] IkeaShelf:
The problem is Windows 11. I have changed to Windows 10 and everything was perfect the first time.

Tnx anyway :)

{Mod edit: Inappropriate language removed. Oswald Boelcke, Senior Moderator}
[Nothing Phone 1] IkeaShelf:
Now my fingerprint doesn't work.

Does anyone know how to solve it?

Thank you :)
[Nothing Phone 1] Kuriiboh:
Hello,

@mark332

I'm using your tool and I got this error (check screenshot in attachments)

I'm using firmware read.

any idea how to fix it?

Thank you.
[Nothing Phone 1] Renate:
No, you're not using my edl.exe

I have nothing to do with this app.

As I said, open a regular command-line window and run my command-line executable from a command-line.
[Nothing Phone 1] Kuriiboh:
I was talking to mark about his unbrick tool.

your reply got me confused tbh.
[Nothing Phone 1] Renate:
Sorry.

If you're using their stuff then you have to reload the Qualcomm drivers.

If you're using mine, then you need the WinUsb driver.
[Nothing Phone 1] Help Im User Nokia:
Hello, I need urgent help, I have a Nokia X100 phone.

I was trying the developer options and touched some option and got stuck in fastboot mode.

Try adb with different applications but can't get past fastboot, please ask for help
[Nothing Phone 1] pyry666:
Wrong thread..
[Nothing Phone 1] AnotherM1m:
Locked bootloader, 2.5.2.hotfix, driver qualcomm 2.1.1.2 without driver signature

trying to read (dump) boot_a and boot_b, it gives me this error

Spoiler content hidden.
[Nothing Phone 1] Gimmly:
i used the tool. On Windows 11 i got errors only. After switching to Windows 10 the tool worked, and said success. The Phone rebooted but its only rebooting to Diagnostic Mode (900E)

What can i do?
[Nothing Phone 1] AnotherM1m:
What happened to your Phone 1 before the brick? How did it stop working?
[Nothing Phone 1] Gimmly:
I don't know exactly how... Its the Phone of my Wife... She came home and showed me that her phone has the Crash Dump Screen, and if we forced reboot it shows Nothing Logo and after 5-6 seconds Crash Dump Screen... She is very scatterbrained and often drops it from about 30cm hight... Could a drop be the issue?
[Nothing Phone 1] AnotherM1m:
people had the same issue without dropping it. very few of them are faulty. could also be a drop but i wouldn't bet my money on it.

If the phone after unbrick tool is still only capable of booting into edl then i would think Hardware issue and the phone needs to be sent to the service center.
[Nothing Phone 1] Gimmly:
Thx for your reply.

I contacted Nothing, but in a very mysterious way the device suddenly started working again after it had been turned off (via bootloader - power OFF) in a corner for 3 days. Today I simply turned it on again and could hardly believe it when the Nothing logo remained and finally started 1.1.7.
[Nothing Phone 1] Void_0:
Hey, I used this tool to revive my Nothing Phone 1, but it seems to have come back in the wrong regional variant, I'm not sure what kind of issues this might cause down the line so I'd like to switch back to EEA, the title says that this tool can supposedly do that, does anyone know how?