Develop Bugs

How to restore Download Mode if all you have is Fastboot

This is for the people [myself earlier] who cannot boot into Android (bootloop or worse), have no download mode, no recovery and can only boot into Fastboot. Download the file below, I have included fastboot (for windows) and the appropriate files to flash, all you have to do is run the commands in order below, then boot into download mode.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
It is best to use the CMD.exe file in the folder provided so you will already be running the commands from that folder without having to change directories. If you're on Linux then make sure you have Fastboot installed then run Terminal from the folder and run the same commands. This will restore the STOCK download mode and recovery partitions not TWRP or CWM.
Download Here

Artifesto said:
This is for the people [myself earlier] who cannot boot into Android (bootloop or worse), have no download mode, no recovery and can only boot into Fastboot. Download the file below, I have included fastboot (for windows) and the appropriate files to flash, all you have to do is run the commands in order below, then boot into download mode.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
It is best to use the CMD.exe file in the folder provided so you will already be running the commands from that folder without having to change directories. If you're on Linux then make sure you have Fastboot installed then run Terminal from the folder and run the same commands. This will restore the STOCK download mode and recovery partitions not TWRP or CWM.
Download Here
Click to expand...
Click to collapse
How would one go about repairing a broken download mode when all I can do is boot into a broken recovery? I cannot issue any fastboot commands as the device is only recognized as an ADB Bridge device. Are there ADB equivalent commands to accomplish the same things as you have detailed here?
SPRINT LS980 (was on Rooted Stock C and borked phone with D OTA) and a broken TWRP 2.7.1.0 Recovery

natefuhr said:
How would one go about repairing a broken download mode when all I can do is boot into a broken recovery? I cannot issue any fastboot commands as the device is only recognized as an ADB Bridge device. Are there ADB equivalent commands to accomplish the same things as you have detailed here?
SPRINT LS980 (was on Rooted Stock C and borked phone with D OTA) and a broken TWRP 2.7.1.0 Recovery
Click to expand...
Click to collapse
well you should never install any OTA with a custom recovery install. you should always keep at least one backup on your phone to restore to in these events. but i would try downloading a rom and installing via sideload before nuking any partitions. which is easy with TWRP. the sideload menu should be in Advanced then ADB Sideload and the command is adb sideload filename.zip and it will take awhile depending on the file size. make sure the file name is simple and it is placed in the folder you are running the sideload from.

Artifesto said:
well you should never install any OTA with a custom recovery install. you should always keep at least one backup on your phone to restore to in these events. but i would try downloading a rom and installing via sideload before nuking any partitions. which is easy with TWRP. the sideload menu should be in Advanced then ADB Sideload and the command is adb sideload filename.zip and it will take awhile depending on the file size. make sure the file name is simple and it is placed in the folder you are running the sideload from.
Click to expand...
Click to collapse
Yes yes I know... it was a moment of weakness late at night and I didn't think before telling the girl to go ahead and upgrade. That being said... Part of the problem now is that the one backup she made just up and disappeared. The ADB sideload option just hangs and never actually does anything. The original Stock Rooted file I had still on the sd partition doesn't fix the issue when I flash it... it looks like it flashes ok but on the next boot it just drops me back into TWRP right where I began. And download mode is still borked.
So let's talk thermonuclear resolution on this motherlover.... where do I begin?
Sent from my SM-N900P using Tapatalk

natefuhr said:
Yes yes I know... it was a moment of weakness late at night and I didn't think before telling the girl to go ahead and upgrade. That being said... Part of the problem now is that the one backup she made just up and disappeared. The ADB sideload option just hangs and never actually does anything. The original Stock Rooted file I had still on the sd partition doesn't fix the issue when I flash it... it looks like it flashes ok but on the next boot it just drops me back into TWRP right where I began. And download mode is still borked.
So let's talk thermonuclear resolution on this motherlover.... where do I begin?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
hmmmmm.... I've been able to get my G2 into fastboot by holding Volume + and Pwr after it setting for awhile turned off.. may be stupid but have you tried that button combo or Volume + and Volume - with Pwr

Could u tell me the command cause i went adb sideload filename.zip and it comes up file not found and i put it in my platform-tools folder any ideas i have adb version 1.30...it was above the version that they said you need on the twrp site
whatsamatta u alumni 1990-2011

Fastboot???
Artifesto said:
This is for the people [myself earlier] who cannot boot into Android (bootloop or worse), have no download mode, no recovery and can only boot into Fastboot. Download the file below, I have included fastboot (for windows) and the appropriate files to flash, all you have to do is run the commands in order below, then boot into download mode.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
It is best to use the CMD.exe file in the folder provided so you will already be running the commands from that folder without having to change directories. If you're on Linux then make sure you have Fastboot installed then run Terminal from the folder and run the same commands. This will restore the STOCK download mode and recovery partitions not TWRP or CWM.
Download Here
Click to expand...
Click to collapse
How do I get to fastboot. I can get to recovery but that's it. Download is not working. The Vol+/- and Power just gets me to key controls.

deathsquad737 said:
Could u tell me the command cause i went adb sideload filename.zip and it comes up file not found and i put it in my platform-tools folder any ideas i have adb version 1.30...it was above the version that they said you need on the twrp site
whatsamatta u alumni 1990-2011
Click to expand...
Click to collapse
i would try to rename your rom to something simple, like rom.zip. there cannot be any spaces in the name and it does need to be in the same folder you run the command from like you seem to be doing.
gelito81 said:
How do I get to fastboot. I can get to recovery but that's it. Download is not working. The Vol+/- and Power just gets me to key controls.
Click to expand...
Click to collapse
did you try vol+ and power together? When a functioning rom is installed it asks to do a factory reset but it may get into fastboot if you nuked that partition. i haven't tried this yet but if you're in adb sideload in twrp maybe the command
Code:
adb reboot fastboot
might help

Artifesto said:
i would try to rename your rom to something simple, like rom.zip. there cannot be any spaces in the name and it does need to be in the same folder you run the command from like you seem to be doing.
did you try vol+ and power together? When a functioning rom is installed it asks to do a factory reset but it may get into fastboot if you nuked that partition. i haven't tried this yet but if you're in adb sideload in twrp maybe the command
Code:
adb reboot fastboot
might help
Click to expand...
Click to collapse
Tried all of the above.... they all just send me into recovery or broken download mode
damn

I'm screwed. I gave this a try and now all I get is a black screen. The phone will connect to my computer but I can't send any commands to it through the command prompt. When it connects to the computer it opens a bunch of different drives and says I need to format them. I can't get into download mode and when I try to send a command in the prompt it just says waiting for device. Any ideas?
Edit: It shows up in device manager like this: http://i.imgur.com/NXGxpcX.png

http://forum.xda-developers.com/showthread.php?t=2582142 try that
Sent from my VS980 4G using XDA Free mobile app

how i can enter in FASTBOOT mode ?

I'm not sure if you can help me here. I have a Verizon G2 and am trying to reset to factory for a repair. I am trying to get into download mode, but only get fastboot when pressing volume up while powered off and plugging in my USB cord. Any help would be greatly appreciated.

razer_ins said:
how i can enter in FASTBOOT mode ?
Click to expand...
Click to collapse
Flash xdabbbeb 24a bootstack zip
WHATSAMATTA U ALUMNI
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
Crossxcalibur said:
I'm not sure if you can help me here. I have a Verizon G2 and am trying to reset to factory for a repair. I am trying to get into download mode, but only get fastboot when pressing volume up while powered off and plugging in my USB cord. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Read 2 post above yours i answered your ?
WHATSAMATTA U ALUMNI

For everyone who is having issues with drivers see the video below to get fastboot to work:
https://www.youtube.com/watch?v=NaK5OxUeDKM

[FIXED] I have no recovery after fimware update and can't connect fastboot!

Hey. I was using a 5.0.1 GPE Rom on my M8 and decided to update both the firmware and the rom to 5.1
I Backed everything up and decided to, as usual, use adb to sideload the firmware to the phone. I did and everything went as expected. After I finished I rebooted to android. I get NFC service stopped working, System UI stopped working and I can't interact with the phone. My thought, well let's go to the recovery and flash a rom I have in my external SD card. No recovery to be found just a android guy belly up with a red ! sign on his belly.
So I thought, I lost my recovery due to the firmware flash, I had happened before, So i went online found a TWRP recovery and went to flash it. Reboot to fastboot USB mode, but then in adb I cannot see the device at all. "adb devices" shows and empty list. I tried my windows 7 laptop to the same result.
Can anyone PLEASE PLEASE help me, I'm kinda freaking out at this point and am running out of options

xsidex said:
..... Reboot to fastboot USB mode, but then in adb I cannot see the device at all. "adb devices" shows and empty list.
Click to expand...
Click to collapse
When in fastboot mode - run command fastboot devices
No adb when in fastboot mode
To flash a recovery (unlocked bootloader)
fastboot flash recovery nameofrecovery.img

ckpv5 said:
When in fastboot mode - run command fastboot devices
No adb when in fastboot mode
To flash a recovery (unlocked bootloader)
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Sometimes some outside thought can be just ridiculasly helpfull when you are stuck in a tiny issue.
Thank you so much Kind sir, my heart rate thanks you aswell.
What a silly mistake

Phone has no fastboot.

Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.

Search for flash_image. I used it to flash recovery from running system. I suppose it can be used to flash fastboot too.

maciek90 said:
Search for flash_image. I used it to flash recovery from running system. I suppose it can be used to flash fastboot too.
Click to expand...
Click to collapse
The phone HAS RECOVERY does NOT HAVE BOOTLOADER

Read entire message. I wrote that this tool probably can be used to flash fastboot too.
You can also try "dd" command from busybox. Check sticky section in Zenfone General forum how to use it.

xRanker said:
Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.
Click to expand...
Click to collapse
You shouldn't mess with stuff you don't understand

If you have recovery, can you get to recovery menu?
Droid on back with error underneath and where you have to hold power then up volume to get to recovery menu.

Ok, here is link to flash_image tool.
http://forum.xda-developers.com/showthread.php?t=902493
I used it to flash recovery on HTC Sensation, but it should work with fastboot on Zenfone too. The command should be "flash_image fastboot /path/to/droidboot.img"
I'm not sure if it will work, but you already have messed up fastboot so this shouldn't make it worse
The second option is "dd if=/path/to/droidboot.img of=/dev/block/by-name/fastboot" or "dd if=/path/to/droidboot.img of=/dev/block/mmcblk0p3" as fastboot is the third partition. You can execute this even in terminal emulator on phone. Of course I haven't check it, but it's listed in general section to flash recovery (fastboot is just another partition, so it should work too).
About going to recovery maybe you can type " reboot recovery" in terminal emulator or from pc "adb reboot recovery". I'm not sure if it uses fastboot to boot into recovery but it's worth trying.

xRanker said:
Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.
Click to expand...
Click to collapse
Find Your Solution Here

Possibly Bricked Pixel XL

Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.

Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot

parakleet said:
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
Click to expand...
Click to collapse
No offence but i am lost by what you said, I am trying to get back to completely stock. Is part of my issue the fact that command prompt didn't detect my device? or no?
I'm not exactly sure what to do with the information you shared, sorry
I the tutorial i found it says to make sure the command prompt sees your device but doesnt say what to do when it doesnt see it.
Also, I downloaded the may factory image, i believe it was version O

Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble

jreink01 said:
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
Click to expand...
Click to collapse
If you did not get your phone from Verizon use this
7.1.2 (N2G47O, May 2017)
Download the zip
unpack all the zip files some are nested so unzipping one creates more keep unzipping until there are no more then gather the following img files
bootloader.img
radio.img
boot.img
system.img
system_other.img
vendor.img
modem.img
Some of those names are cut down as i hate typing long strings, jsut rename them as such.
Create a folder on root of c:\_PIXEL_XL_
put all the files there.
You will use way less files than you unpacked
once you have done that run the following commands
copy and paste
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
After last reboot just wait and you will be back at stock
if that doesnt work
Download latest version of TWRP place it in C:\_PIXEL_XL_
rename it twrp.img, again i hate typing long strings
from bootloader run
fastboot boot c:\_PIXEL_XL_\twrp.img
This will take you into twrp
you might need to wipe system and cache and data,
From memory the fourth entry at bottom is internal memory or user data, in any event if you do not check that your data stays on the phone.
Once you have wiped the other 3 rerun the fastboot commands and you will be back at stock
add the twrp and supersu commands from earlier to add root.
dont forget the signatureverify.img if you are doing that.
good luck.
you arent bricked
you just need to find the correct combination of steps to get your phone where you want it to be

Thanks for the response. I am having a hard time with this, the zip file i downloaded from the google website, when i open it, there are only 6 files, 1 of which is a zip file (marlin). When I open marlin it shows a bunch of files, none of which you mentioned. I am confused, was wondering if you would be nice enough to walk me through this over the phone, i would be really grateful.

Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!

jreink01 said:
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
Click to expand...
Click to collapse
Yes, i sent you a PM.

HALV0RS3N said:
Yes, i sent you a PM.
Click to expand...
Click to collapse
thanks, sent you my #

Okay so I had the exact problem yesterday. To to the Google developers site and download the official Google pixel or xl 7.1.2 nougut ota update. Once that's downloaded, go to your phone, I had all the exact same screens on my phone so it should work. Hold down the power button until it completely shuts down. Then hold the power and volume down to go to recovery mode, if it goes back to the ext 4 screen, try it again until it goes to recovery mode, then on command prompt type, fastboot boot twrp.img then once it's in twrp, go to advanced-then adb sideload and click both boxed and then swipe to enter sideload. Then on your computer, type adb sideload "file name for Google update" and hit enter. That should do the trick. Like I said, I had the exact same problem yesterday
---------- Post added at 06:56 PM ---------- Previous post was at 06:50 PM ----------
Also, I forgot to mention, download the twrp image file from the Internet. Shouldn't be hard to find just make sure it's the latest. Put that file in the adb file on your computer same with the Google update for your phone. Do not unzip either file. That's very important. DO NOT UNZIP THE UPDATE File. When you type in the twrp.img make sure you type img. And when you flash the update, make sure at the end of the file name you put
.zip ex( marlinpixelxl7.1.2.zip)

jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
Looking at your screen shot you didn't let the file finish flashing. It sticks at the "does not contain" for a bit before it continues.
You were doing it right. You just didn't wait.
If it wasn't going to work it would eventually give you a failure and jump to the command prompt.

jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.

RedBlueGreen said:
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
Click to expand...
Click to collapse
OP was flashing to stock. Didn't let it finish though.

Stuck in Fastboot Mode (Recovery mode does not work)

Hello lads,
I have been having issues with my OnePlus Nord N100.
On my fault, I wanted to root with magisk using fastboot. Unfortunately, I had flashed boot a magisk.img which was not compatible with OnePlus Nord N100.
The phone is currently stuck in Fastboot Mode. I have tried several times to flash boot it back to its original boot.img, unfortunately it does not work.
Every time I try to go to Recovery Mode, it leads me right back to the Fastboot main menu. I can turn off the phone and reboot it with no issues.
I believe I have soft bricked it, and I need help recovering it back to it's original state, or better yet root it in a riskless way.
Here is a list of commands and techniques I have tried so far:
- Fastboot -w
- Fastboot erase cache
- Fastboot erase boot
- Fastboot erase boot_a
- Fastboot erase boot_b
- Fastboot boot boot.img (Ends up with a failure)
- Fastboot flash boot boot.img (Command is successful, but no changes for boot)
- Tried all combinations keys to go to Recovery Mode (Power button + Volume Down Button + Volume Up Button)
Thank you for helping me out if you can.

Windwell said:
Hello lads,
I have been having issues with my OnePlus Nord N100.
On my fault, I wanted to root with magisk using fastboot. Unfortunately, I had flashed boot a magisk.img which was not compatible with OnePlus Nord N100.
The phone is currently stuck in Fastboot Mode. I have tried several times to flash boot it back to its original boot.img, unfortunately it does not work.
Every time I try to go to Recovery Mode, it leads me right back to the Fastboot main menu. I can turn off the phone and reboot it with no issues.
I believe I have soft bricked it, and I need help recovering it back to it's original state, or better yet root it in a riskless way.
Here is a list of commands and techniques I have tried so far:
- Fastboot -w
- Fastboot erase cache
- Fastboot erase boot
- Fastboot erase boot_a
- Fastboot erase boot_b
- Fastboot boot boot.img (Ends up with a failure)
- Fastboot flash boot boot.img (Command is successful, but no changes for boot)
- Tried all combinations keys to go to Recovery Mode (Power button + Volume Down Button + Volume Up Button)
Thank you for helping me out if you can.
Click to expand...
Click to collapse
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b

AJHutchinson said:
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
Click to expand...
Click to collapse
Hey mate,
Thanks for responding. Sorry for the late reply.
From what you had suggested, I did "fastboot --set-active=a" , "fastboot flash boot boot.img", and "fastboot reboot" (with the stock unpatched boot.img) the commands were successful once again, but there were no effective changes.
Afterwards, I did "fastboot --setactive-b", "fastboot flash boot boot.img", and "fastboot reboot" the commands were successful once more, and this time, I was finally able to go into recovery mode. On the other hand, in recovery mode I wiped the cache and erased everything, but unfortuantely I still could not boot into Android, even though I tried to flash boot the image once more.
Thank you for these commands, as I was at least able to recover recovery mode.
Any other suggestions maybe?

Hello,
Use this tool and it will fix it, I had the same problem. Just download the software and flash it in Qualcomm EDL mode.
MSMDownload image needed
Hello guys, I managed to flash the wrong image to OnePlus NORD N100 BE2013, I overlooked for the first time what I'm doing and messed it up Now it's in Qualcomm EDL mode and I need and image to flash it to bring it back do life, anyone I can...
forum.xda-developers.com
I alsp posted boot.img which is compatible you can flash it. Link is in the comments.
Thanks

Boot.img from nord n100 in this thread, I exctracted and rooted it myself.
I WHANT RECOVERY Boot.img FOR ROOT MY ONEPLUS NORD N100
I unlock bootloader and i whant to root with magisk my phone, i need boot.img for rocovery..I try anather boot.img from One plus nord, etc, i sucessfull flash this recovery's with command in windows but is no go in recovery, stay in bootloop..Can...
forum.xda-developers.com

Hello,
I used the tool MSMDownload but unfortunately I was unable at all to boot into Qualcomm Edl mode, even though I have installed correctly all the drivers for Windows Qualcomm, and OnePlus USB drivers, and used the correct method (Volume Button UP and Down at the same time whilst connecting the phone via USB). I tried flash booting with the boot.img you gave me, but still no changes. I am still stuck in Fastboot.
If you had encountered the same issue back then, can you tell me the excat procedure you did please?
Thank you so much.

I was in the exact same situation after flashing boot.img from one plus nord by mistake.
It got so bad it was totally bricked and just got into EDL mode by holding down the up and down volume buttons and holding power on. Even the screen didn't work.
Once that started, MSMDownload tool from the N100 thread worked fine, you downloaded the proper package right?
Which model does it say on the back? This was BE2013.
I think solution for you is a fastboot image, I extracted the payload.bin to .img files and brought it back to life with it and rooted it with magisk.
The boot.img I uploaded here was from Oxygen OS 10.5.5.
If you have fastboot you should 100% be able to boot into EDL mode, just hold down the up and down volume buttons for long time and then the power button
Thanks

AJHutchinson said:
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
Click to expand...
Click to collapse
oh
thts ok man
بلوک سبک

I will try to make a fastboot image for OnePlus NORD N100 BE2013 with 10.5.5 and upload it to mega, I'll send you the link. If you are in fastboot mode you will be able to flash it I believe, let me have a look.

Fast boot image is ready for Oxygen 10.5.5 Nord N100 EUROPE, I am uploading it to MEGA.

motovnet said:
I was in the exact same situation after flashing boot.img from one plus nord by mistake.
It got so bad it was totally bricked and just got into EDL mode by holding down the up and down volume buttons and holding power on. Even the screen didn't work.
Once that started, MSMDownload tool from the N100 thread worked fine, you downloaded the proper package right?
Which model does it say on the back? This was BE2013.
I think solution for you is a fastboot image, I extracted the payload.bin to .img files and brought it back to life with it and rooted it with magisk.
The boot.img I uploaded here was from Oxygen OS 10.5.5.
If you have fastboot you should 100% be able to boot into EDL mode, just hold down the up and down volume buttons for long time and then the power button
Thanks
Click to expand...
Click to collapse
For some reason Qualcomm Mode Edl does not launch whatsoever.

motovnet said:
Fast boot image is ready for Oxygen 10.5.5 Nord N100 EUROPE, I am uploading it to MEGA.
Click to expand...
Click to collapse
Thank you that's very kind of you. I think the only way to fix it by flash boot.img, but I have doubts because it does not work.
The only commands I am doing are "fastboot devices", "fastboot flash boot boot.img"

With the fastboot image you will be able to flash everything, it contains not only boot.img but system and etc. I managed to boot mine and bring it back to life by reflashing everyhing.

So the only thing I need to do is "fastboot flash boot ''.img" right?
Where can I get all the nesscary files?
And how did you manage to root it?

The fastboot image flashes all partitions, not just boot with stock Oxygen OS 10.5.5
What you need to do is run flash-all.bat from the archive and it will flash the entire os not just boot.img.
If you can't get to EDL mode, fastboot flash is the only solution. What model does it say in the back? This one was EUROPE BE2013.
Is your EU or Global device?
Archive is uploading still.
Thanks

The model is the correct one. BE2013, although it does not say EU or anything.
In the archive, I would just need to run flash-all.bat which flash boots all the nesscary images correct?
Thank you once agian.

2.55 GB file on MEGA
mega.nz
This is a fastboot image for OnePlus NORD N100 EU BE2013 device.
Extract it to a new folder, it contains fastboot in it.
Right click flash-all.bat and run as admin.
You can open the flash-all.bat file with notepad to check yourself there is nothing strange in it. I used a bat file from the forum that was fastboot image for OnePlus NORD and changed it to use the .img files for OnePlus NORD N100.
Contains Oxygen 10.5.5, once you bring it back to life (IF YOU HAVE THIS MODEL), you can use magisk to patch the boot.img and flash it via fastboot.
This is how I rooted it and it worked properly.
Please use it with caution and ensure your model matches! I can not guarantee it will work on other devices.
If you can't go to EDL mode, this is your way to go, but I don't know if flashing GLOBAL version will work.
Thanks

Windwell said:
The model is the correct one. BE2013, although it does not say EU or anything.
In the archive, I would just need to run flash-all.bat which flash boots all the nesscary images correct?
Thank you once agian.
Click to expand...
Click to collapse
I would guess BE2013 is the EU one, as this worked on mine.

motovnet said:
I would guess BE2013 is the EU one, as this worked on mine.
Click to expand...
Click to collapse
Okay thank you for helping me. I will try this later and keep you in touch.

Windwell said:
Okay thank you for helping me. I will try this later and keep you in touch.
Click to expand...
Click to collapse
Thanks, let me know if it works for you. If you're unable to flash it via fastboot, only EDL will help.