yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 1] WoKoschekk:
I guess your phone doesn't boot. So, what should ./adb devices should show? You need a booted system/recovery for ADB. Do you mean ./fastboot devices?
[Nothing Phone 1] rogerrulez:
Why would you flash a boot image before locking the bootloader?
[Nothing Phone 1] mozek337:
I didn’t know if uninstalling magisk restored the original image
[Nothing Phone 1] mozek337:
I didn’t try /fastboot devices. I am really a begginer in all this and much too hasty. If you could tell me the difference between adb and fastboot i’d gladly appreciate that.
[Nothing Phone 1] rogerrulez:
It does. And whatever version of the boot image you flashed before locking has caused the problem I'm thinking.
[Nothing Phone 1] rogerrulez:
If you are able to get to the bootloader menu, yeah try fastboot devices to see if anything is listed. I'd you can boot up the phone to the bootloader menu then you should be able to recover from there.
[Nothing Phone 1] rogerrulez:
When you connect your phone to your computer does your computer make a sound indicating a device is connected ?

Also try a different port and/or cable as well. It's a very common issue.
[Nothing Phone 1] mozek337:
It does connect to the pc but i don’t really know where to go from there or how to restore original OS.
[Nothing Phone 1] rogerrulez:
First you need to have ADB installed on your computer. Then after that you can download one of the fastboot ROMs, extract the contents toa a folder. Inside of that folder you will find two .bat files. Flash_a.bat and fladh_b.bat. Run both. But even before you do that you are going to have to unlock the critical partition. Otherwise they won't work. I can't remember the exact command but it's in one of the threads relating to unbricking your phone. It's going to be fastboot unlock_critical I believe. This is dangerous territory as well. But it's the only way it will work to run those batch files. I would start with version 1.5.2. The phone will reboot. Then there will be an official update in settings.

Download that and all should be fine. But before you do that I would relock the critical partition first. I just did it.

But you will have to do some reading first to make sure you completely understand what you are doing because at this point you could permanently brick your phone. Kinda..
[Nothing Phone 1] mozek337:
Do you know if there is a thread or a tutorial about this?
[Nothing Phone 1] rogerrulez:
You are going to need to read through several. But you can start herewith this one.

[GUIDE][HowTo] Unlock and root Nothing Phone (1)

ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK. THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!) GOOD CONTINUATION TO ALL...

xdaforums.com
[Nothing Phone 1] rogerrulez:
You'll need to do everything but rooting. These phones are finicky. It seems that they don't want anyone messing with them. That's why people are having problems with them if you are unfamiliar with doing this stuff.

Reads through the other how to's and stuff like that. It's a long process. Even for me it took awhile.
[Nothing Phone 1] ethical_haquer:
Keep up the good work. :) (y)
[Nothing Phone 1] mozek337:
What do you mean by running the .bat files? What commands do i need to use to run them?
[Nothing Phone 1] mozek337:
I think i’m going to send it for an off warranty repair to the Nothing centre. Thanks for the help so far tho, I really appreciate it.
[Nothing Phone 1] rogerrulez:
They will have a .bat extension. There will be only two of them. Just double click on each one and those files will do the rest.
[Nothing Phone 1] rogerrulez:
I don't think they will cover that under warranty. You will probably have to pay for it. But better safe 4gwn sorry I suppose.
[Nothing Phone 1] mozek337:
Yeah it will be an out of warranty repair but that was expected.
[Nothing Phone 1] mozek337:
Hi, how do i flash it?
[Nothing Phone 1] WoKoschekk:
Extract the downloaded archive into your ADB/Fastboot folder on your desktop and double click the extracted flash.bat.
[Nothing Phone 1] mozek337:
The whole folder? or everything inside?
[Nothing Phone 1] WoKoschekk:
All

single files

from the archive must be in your ADB/Fastboot folder. Also the flash.bat files.
[Nothing Phone 1] mozek337:
What about the magisk folder? that too?
[Nothing Phone 1] WoKoschekk:
Are you currently rooted? If yes, then flash the Magisk patched image before you boot the system.
[Nothing Phone 1] mozek337:
not rooted. but the folder was already in the rom zip
[Nothing Phone 1] WoKoschekk:
You are going to flash the stock firmware with a stock boot.img (unpatched and not rooted!). If you want/need Magisk then you have to flash the patched boot.img afterwards or directly instead of the stock boot.img. But it's important not to boot your device with the stock boot.img when you were rooted before. If you do so then you are not rooted anymore.
[Nothing Phone 1] WoKoschekk:
The batch file won't flash the patched boot.img and you must flash it by yourself (if needed).
[Nothing Phone 1] mozek337:
Should i flash both “flash_slot_a” and “flash_slot_b”?
[Nothing Phone 1] WoKoschekk:
Do you know your active slot? If not, flash both.
[Nothing Phone 1] mozek337:
I flashed both yet the phone isn’t turning on. still in bootloader menu
[Nothing Phone 1] WoKoschekk:
For errors regarding the flash process we need a screenshot of your cmdline with all outputs.
[Nothing Phone 1] mozek337:
It’s already closed
[Nothing Phone 1] WoKoschekk:
Then flash again
[Nothing Phone 1] WoKoschekk:
@mozek337 Screenshot Windows: Win+Shift+S (see attachment).

I assume all the previous flash commands, that are NOT shown, were also executed successfully?

Try to switch the boot slot and reboot after each command:

fastboot -aa => switch to slot A

fastboot -ab => switch to slot B
[Nothing Phone 1] mozek337:
What previous flash commands? This is all that shows after flashing slot a (left) and slot b (right).

p.s. i know how to screenshot but it’s much faster to take a photo since i’m viewing xda on mobile. Thanks for shortcut tho.
[Nothing Phone 1] mozek337:
When switching to slot a, the phone goes straight to bootloader menu. When switching to slot b, the phone keeps booting and shutting down.
[Nothing Phone 1] WoKoschekk:
The ones you will see when you scroll up the screen.
[Nothing Phone 1] WoKoschekk:
@mozek337 Just to be clear: Your device's bootloader is unlocked and there aren't any modifications on your phone like root or sth else? It's just unlocked?
[Nothing Phone 1] mozek337:
Yes i unrooted the device before.

Also i sent 2 photos, one from the start and the other with the rest.

The bootloader is unlocked and the critical is also unlocked.
[Nothing Phone 1] rogerrulez:
Did you unlock the critical partition?
[Nothing Phone 1] mozek337:
yes, would unlocking it again to be sure help?
[Nothing Phone 1] rogerrulez:
Unless you unlock the critical partition, you can run those batch files all day long and they won't accomplish what you need to do. The critical partition must be unlocked in order for these fastboot ROMs to be able to be flashed properly. Period !
[Nothing Phone 1] WoKoschekk:
No, there are no errors in your screenshots and everything was flashed correctly.
[Nothing Phone 1] WoKoschekk:
How did you unroot? Did you boot the system after unrooting the phone?
[Nothing Phone 1] mozek337:
by uninstalling magisk, i also flashed 1.5.3 boot image because i didn’t know if uninstalling magisk restored the original boot img. after that i locked the bootloader which seems to be the problem
[Nothing Phone 1] rogerrulez:
I just looked at the screenshots. It looks like everything went okay. I had that problem as well. You will have to boot to recovery and wait for the options to appear, it's weird how it works, then do a full wipe of everything. After that your phone should boot up just fine.
[Nothing Phone 1] mozek337:
By selecting recovery mode the phone boots back to bootloader mode
[Nothing Phone 1] rogerrulez:
That's messed up. It shouldn't do that. At this point here is what I would recommend. Start over. Start by downloading the 1.1.7 fastboot ROM, unlock bootloader and critical, and flash that older ROM. See if the phone boots with that version.

When I flashed the A slot I did not allow the phone to try and boot. I stopped it and went back to the bootloader and flashed slot B. Then I found the phone would not boot. I had to go into recovery to do a full erase. I then rebooted the phone from recovery. If after that the phone still does not boot up then go back to bootloader and make sure everything is unloacked and flash fastboot ROM 1.5.2.

They made these phones like an iphone both in hardware looks and software. They don't want you messing with them. Disgusting IMO considering it's android but it is what it is.
[Nothing Phone 1] mozek337:
The 1.1.7 version didn’t boot but recovery worked! Can i safely lock the bootloader now? And if so do i need to lock critical aswell?
[Nothing Phone 1] WoKoschekk:
Your phone did not boot and you want to know if you can "safely" lock the bootloader??
[Nothing Phone 1] mozek337:
It didnt but recovery worked. it erased all and then the 1.1.7 booted fine but updates wont install. im guessing because bootloader unlocked
[Nothing Phone 1] WoKoschekk:
Sure that everything works? You have a mobile data signal, Wifi and Bluetooth? No bootloops? Then lock your bootloader. And yes, lock critical as well as flashing_lock.
[Nothing Phone 1] rogerrulez:
That's good news. At this point no. Leave and make sure everything is unlocked, bootloader and critical. Now fastboot flash the 1.5.2 ROM.
[Nothing Phone 1] rogerrulez:
Ibelieve the bootloader and critical gets locked automatically so make sure they are both unlocked before flashing 1.5.2. You phone should boot up after that. Make sure to flash both slots. Once the phone is booted up after flashing the 1.5.2 there will be a system update to 1.5.3. That update will relock everything as well.
[Nothing Phone 1] rogerrulez:
Forgot to add that you will have to go into recovery to do a full erase of everything.
[Nothing Phone 1] mozek337:
I am now on 1.5.2 and i have the 1.5.3 update available but I can’t update it, it says instalation failed.

I erased all data with recovery but still can’t update. You said that the bootloader will relock when i update to 1.5.3 but isn’t it that i need to lock the bootloader to succesfully update?
[Nothing Phone 1] rogerrulez:
Excellent Relock your bootloader and critical partition is they are not already locked. Double check.
[Nothing Phone 1] mozek337:
which should i lock first?
[Nothing Phone 1] rogerrulez:
Disable OEM unlocking in developer options first.
[Nothing Phone 1] rogerrulez:
Critical first.
[Nothing Phone 1] mozek337:
You can’t turn off oem unlocking with bootloader unlocked
[Nothing Phone 1] rogerrulez:
Right. So go ahead and make sure critical is relocked. Then relock bootloader and try the update again.
[Nothing Phone 1] rogerrulez:
Were you able to get the update ?
[Nothing Phone 1] mozek337:
I won’t be able to be on pc untill tomorrow. I’ll tell you how it went. Also I really appreciate the help of all of you😩💦. Thank you very much!
[Nothing Phone 1] lucy1983:
https://xdaforums.com/t/unbrick-tool-edl-flash-read-repair-region-change-tool.4552471/post-88349435

Just dump the fastboot method. It is too complicated. And use the EDL method instead from this link.

You just need to have a spare usb cable and make an EDL cable out of it. After that you need to follow the steps in the tutorial and flash the 1.1.7 firmware with the tool provided there.

After successfully flashing 1.1.7 you will be able to update via OTA to the latest 1.5.3.

The tool is tested by me personally and it works like a charm. No more hassle with slots, drivers, adb and fastboot stuff.

If you need any help to make your EDL cable from a regular usb one just ask me or watch YouTube. There are quite a few videos that show how to boot your phone into EDL mode.

Or, if you phone is already booted into system you can simply use the "adb reboot edl" command from CMD.
[Nothing Phone 1] mozek337:
What exactly is edl?
[Nothing Phone 1] lucy1983:
Emergency Download Mode. Every Qualcomm phone has it and it is the best way to reflash the stock ROM. Every service center uses the EDL method to bring the phones back from the brick state or if they are having problems by flashing in fastboot or recovery mode.

It practically writes back all the partitions on the phone, including the bootloader partition.

So, EDL is kind of what a BIOS is for a computer.

Flashing in EDL you only need to install one driver and you don't have to mess with partitions because the EDL program know exactly what to flash on each partition so that the phone will be in the same state it was when it got put of the factory.
[Nothing Phone 1] mozek337:
why is it important to use a spare cable?
[Nothing Phone 1] lucy1983:
Because you have to modify it so that you'll be able to short the green and black wires.

Just do a search on YouTube with "how to make edl cable".

But if your phone is booting into operating system you don't need a edl cable, just a regular one and type in command prompt "adb reboot edl".
[Nothing Phone 1] mozek337:
yes thanks that’s what i meant
[Nothing Phone 1] mozek337:
Now i successfully locked the bootloader both normal and critical and rebooted edl but it still says i can’t update to 1.5.3. Have any advice?
[Nothing Phone 1] rogerrulez:
Rebooted edl ? Why would you be in edl mode ? Anyways, did you disable oem unlock in developer settings ?
[Nothing Phone 1] mozek337:
I rebooted edl because @lucy1983 said i should. And tes oem unlocking is turned off
[Nothing Phone 1] lucy1983:
You must decide witch method you want to use for flashing: fastboot or EDL.

If you choose EDL then it doesn't matter if you have locked or unlocked bootloader, locked or unlocked "critical". The EDL tool will write all your partitions as if the phone where fresh from factory. And you will be able to update normally by OTA until you reach 1.5.3 firmware.
[Nothing Phone 1] WoKoschekk:
@mozek337

For your information

: EDL mode is useful for bricked devices with a corrupt bootloader that can't boot into fastboot mode or anything else. In other words: When your device is hard bricked and dead.

With the help of EDL and a special software tool you are able to flash a new bootloader to use fastboot mode again. The EDL mode is provided by Qualcomm.

Since you are able to boot into fastboot mode you should use the fastboot method.
[Nothing Phone 1] mozek337:
Thanks really for all the explaining. I really appreciate it!
[Nothing Phone 1] lucy1983:
And by the way, you don't need to have a LOCKED bootloader to be able to update normally, by OTA, your firmware.

You just need to have all your partitions correctly flashed, witch is what the ESL tool will do.

If you want to mess with partitions and fastboot and drivers and locking and unlocking, then feel free to use the fastboot method. But from what I read you used that and still you're not able to update correctly, witch means your partitions are messed up by all that flashing in different slots in fastboot mode.

That's why o told you to flash by EDL metod and be done with it in just 2 clicks.
[Nothing Phone 1] mozek337:
So what do i need to do to update successfully?
[Nothing Phone 1] rogerrulez:
You have already achieved boot so I don't know why you are going the edl method. That is a last resort. If the normal update route is not working and you are now on 1.5.2 as per my instructions then now to fully update you will have to manually update to 1.5.3 using the dialer method. *#*#682#*#*

Download the 1.5.3 update and put it on your phone. Dial the numbers as I described. It will bring you into the mnaula update mode. Select the file you downloaded and it should there manually update.
[Nothing Phone 1] mozek337:
by downloading the 1.5.3 you mean the ota package from github?
[Nothing Phone 1] rogerrulez:
That or the full rom itself. Try the OTA first.
[Nothing Phone 1] WoKoschekk:
I assume the partitions are flashed correctly because he can boot his device with a locked bootloader. In this state the device uses Android Verified Boot (AVB) and all related partitions like /boot, /vendor and /system are validated by this process. If one of these should still be modified, the device will show a warning screen or will deny to to boot.
[Nothing Phone 1] mozek337:
still can't update
[Nothing Phone 1] lucy1983:
He is not able to update even with the dialer method, like you well see in his comment bellow.

So something is not flashed correctly in fastboot.

That's why I told him to use the EDL tool and with just 2 clicks he'll be up and running his phone in 5 minutes.
[Nothing Phone 1] rogerrulez:
I had that problem before. Give me a bit to think of what I did to fix that. Oh. First, go into about phone and see what it says for software info.
[Nothing Phone 1] rogerrulez:
I was in his same position and I didn't have to use edl method. But I believe you are right in saying that something didn't flash correctly.
[Nothing Phone 1] lucy1983:
Download the tool from the post I shared with you a few comments ago.

Unzip the .zip file.

Inside you will find a .exe file.

Open it with admin rights.

Check ✔️ the "flash firmware" tab and click on "start" button.

After that put your phone into EDL mode by typing "adb reboot edl" in a command prompt window and the flashing process will begin by it self, you do not have to do anything else.

That's it.

After flashing is done (be patient) the phone will reboot by itself in the 1.1.7 firmware. From there you can update to 1.5.2 and then 1.5.3.

Make sure the port from the PC is usb 2.0 and NOT usb 3.0.
[Nothing Phone 1] rogerrulez:
Also, before trying anything else, go back to bootloader mode then recovery and do a full wipe.
[Nothing Phone 1] mozek337:
Do i need unlocked bootloader?
[Nothing Phone 1] rogerrulez:
What software version is your phone saying you are on ?
[Nothing Phone 1] mozek337:
1.5.2.
[Nothing Phone 1] rogerrulez:
I remember what I did when I had the same issue. I either flashed the OTA 1.5.2 to 1.5.3 or I think I reflashed the 1.5.2 ROM. When I had that problem after flashing 1.5.3 I believe, my phone was saying I was still on 1.1.7. So I just reflashed 1.5.2 and everything worked fine.

So it's up to you which method you choose from here.
[Nothing Phone 1] rogerrulez:
But I would clear everything in recovery first before trying anything.
[Nothing Phone 1] lucy1983:
If you do EDL no, no need for anything else except the correct drivers so that your phone can be recognized by the PC in 9008 mode under the tab "Ports" in Device Manager.
[Nothing Phone 1] lucy1983:
I'm ready to bet he will not succede because something is wrong in his table of partitions. It doesn't have to be something major like to prevent the phone to boot. But it is something that prevents him from updating his firmware.
[Nothing Phone 1] mozek337:
I dont believe myself enough to make an EDL cable.
[Nothing Phone 1] mozek337:
Could it be that when i rebooted edl i didnt wait for it to boot by itself but insted booted it on by holding oower button?
[Nothing Phone 1] lucy1983:
You don't need to make a cable if your phone is booting into the operating system.

Just open a command prompt (CMD) and type "adb reboot edl".

But before that you must press the "start" button in the tool I told you to open (that .exe file) with administrator rights.
[Nothing Phone 1] lucy1983:
The tool doesn't flash anything if it doesn't see that all the required conditions for flashing are accomplished.

You cannot corupt anything just by forcing the device out of EDL mode.
[Nothing Phone 1] WoKoschekk:
No, there isn't sth wrong with the partition table. That's impossible. You can't boot anything with a corrupt GPT.

Fastboot = EDL

bootflow: The primary bootloader (pbl.elf, build by your chip manufacturer) verifies and loads the extensible bootloader (xbl.elf, mostly partition 1 of 70-100) which also verifies and loads the Android bootloader (abl.elf, Fastboot mode). From this point the Trusted Execution Environment gets loaded and also the Kernel gets loaded into RAM and your system boots up and so on.

Let's stop between pbl.elf verifies the xbl.elf. If this process fails, your device will start the EDL mode.

What does the EDL mode do? Every EDL tool has a programmer.elf which is only a modified xbl.elf. You can compare both files, they are part of your EDL ROM. That means your PC is acting as the bootloader with the help of the programmer.elf. The programmer.elf must be signed in the same way the xbl.elf is signed in order to be able to communicate with the pbl on your device. This communication is done by the firehose protocol. On the other side the device's Qualcomm CPU will starts the sahara protocol when in EDL mode and opens the well known COM port to communicate with your PC/programmer.elf.

From this point on the EDL tool does the same as fastboot do: flashing images on your eMMC/eUFS chip to the corresponding partition.

At the end (no matter using EDL or fastboot mode) all partitions have the same content that could be verified by checksums. And this is what Android Verified Boot does.

So, a correctly booting Android device is the best proof that all partitions are fine.

EDL is only an uncomfortable way to flash your device in case of a corrupt bootloader with an unfunctional fastboot mode. There is no difference between these two methods and both do the same. It's all depending on the used images and their content.
[Nothing Phone 1] lucy1983:
I know all these.

I was more interested in the answer to the question: if all is fine, then why his device refuses to do a simple operation like updating a damn firmware via OTA or manual update?

Since I can only guess the reason, as all of you who suggested him to insist with the fastboot method, I provided a simple solution that worked for me several times and I'm able to do it again and again without any complications, just 2 clicks and 5 minutes of waiting time.

The proof that the fastboot method doesn't work for him is the fact that, no matter what he is doing regarding fastboot mode, he is not able to update.
[Nothing Phone 1] rogerrulez:
The question, was it done correctly. I had the exact same issue. I did the fastboot method flashing both partitions and doing a full erase in recovery. Then I had no issues with my phone taking the update.

I remember I got my phone manually to 1 5.3 then got the hotfix update easy through regular update.
[Nothing Phone 1] WoKoschekk:
Yes, that's right. But it's not the method of flashing, it's the content of flashing that's making the difference here. So, as I can see the EDL ROM is more extensive. Especially the userdata.img which is not a part of the fastboot ROM. But there are some other images that are also missing in the fastboot ROM. I think that's the reason why EDL flashing leads to a different result.

Unfortunately it's not possible to flash that userdata.img with simple fastboot commands. You need the EDL tool to read the XML files that told you on which storage block the splitted userdata_XX.img parts must be flashed to.
[Nothing Phone 1] mozek337:
So what do you guys think i should do?
[Nothing Phone 1] lucy1983:
Exactly. I also noticed the edl ROM has something more than the fastboot one, like it is more "complete". That's why I recommended him to flash by EDL. That method always worked for me. 100%. No problems at all.
[Nothing Phone 1] rogerrulez:
You already have a phone that boots. All you have to do is finish with the issue. No need to reinvent the wheel. Try doing a full wipe in recovery first. Also check to make sure your critical partition and bootloader is locked.

If that still doesn't.work you may have to reflash .I had to do the same thing. No big deal.
[Nothing Phone 1] lucy1983:
And you don't think it is more complicated flashing two partitions and being carefull witch partition is active and witch one is not? It isn't more user friendly to just boot into EDL and do 2 clicks in the EDL tool and then the tool doing automatically what it was programmed to do?