One Plus Nord N10 5g - Stuck on FastBoot - OnePlus Nord N10 5G Questions & Answers

my oneplus nord n10 5g is stucked on fastboot. to reinstall stock rom , i want to unlock bootloader , but my usb debudding and oem unlocking is off. how can i fix that ?

hfsva007 said:
my oneplus nord n10 5g is stucked on fastboot. to reinstall stock rom , i want to unlock bootloader , but my usb debudding and oem unlocking is off. how can i fix that ?
Click to expand...
Click to collapse
You don't need either adb debugging or OEM unlock ticked to reset it to stock.
Just go into edl mode on your phone and start the process.

ninjasinabag said:
You don't need either adb debugging or OEM unlock ticked to reset it to stock.
Just go into edl mode on your phone and start the process.
Click to expand...
Click to collapse
Thanks mahn thatks for the help. the first time im head about edl mode. download the edl mode firmware and flashed it. its worked......thank a lotb

hfsva007 said:
Thanks mahn thatks for the help. the first time im head about edl mode. download the edl mode firmware and flashed it. its worked......thank a lotb
Click to expand...
Click to collapse
Care to explain how to do it please?
I get into fastboot, but I cant get in to EDL mode in any way.

There are a few other posts in this forum on this subject. I almost want to ask mods for a sticky on it, as it seems to screw up a lot of people. The threads are all there, I won't repeat them here, but here's the stuff I didn't find obvious:
Make sure you have the right drivers installed. There is a SPECIAL set of Qualcomm drivers- different from the phone, and anything fastboot/ADB, needed to make Windows happy. Without this, you will get nowhere.
If Windows isn't your OS, and you are running an emulator (e.g. VirtualBox on Linux), make sure the USB ports are pass-through to the VM. This often requires permissions settings NOT DONE by the installer.
Likewise, make sure you pull your computer off the internet during this process or Windows may randomly reboot you to do system updates, with your phone half-flashed.
When you use the plug-in method for EDL, YOU ONLY GET IT FOR LIKE 3-5 SECONDS. You will not have a screen indication. You will not have vibration, or any other signal I know of beyond the USB device indication.
Quick process refresher: If memory serves (it has been a while) have the phone powered off, hold AND CONTINUE TO HOLD both volume buttons, and plug the phone in. *THEN* it should show up in Windows as a Qualcomm device. Let go of the buttons, take a deep breath, pat yourself on the back for having VM and drivers installed correctly. Get the phone powered off again however you can, then repeat the process again with the flash tool running, and it should give you a short window of "ready" or whatever for you to start the flash. Once you do that, and it goes into "beginning firehose" something or other, you can let go of the volume buttons. If you miss the window, repeat again until you hit it.
FWIW, it is pretty much impossible to brick a OnePlus without physical damage. The EDL mode is a separate methodology that allows a complete overwrite of everything that can be overwritten.

Related

[GUIDE] EASY Axon 7 UNIVERSAL UNBRICK / FACTORY RESTORE

WARNING, THIS GUIDE WILL WIPE ALL THE DATA IN YOUR DEVICE.
!!! Whatever you do, it is at your own risk !!!​
This procedure will unbrick any Axon 7, returning it to stock. It fixes any kind of brick as long as your hardware is not damaged. You can't damage your hardware using software so if you have a healthy unit, you can recover it from any flashing "accident".
1. GET THE SOFTWARE
You need a Windows PC, Windows 10 is highly recommended. Do this:
01. Install MiFlash in your PC. It includes the Qualcomm Snapdragon SoC drivers, nonetheless you can always install the latest drivers.
02. Download the EDL flashable stock firmware package for your model:
A2017 (China): B14_MIFAVOR5 Android: 7.1.1
A2017G (Europe): B10_NOUGAT Android: 7.1.1
A2017U (Americas): B35_NOUGAT Android: 7.1.1
03. Unzip the firmware ZIP file to a folder in your hard drive.
2. ENTER EDL MODE
Option A: USING THE REBOOT COMMAND
If you still have access to your system but not to recovery or fastboot, then you just need to install any terminal app, open it and at the app's command prompt enter:
Code:
reboot edl
. You device will reboot into EDL mode. Now you can safely plug your Device to your computer. In your computer right click in the Windows Start Menu icon and select Device Manager. Under Ports (COM & LPT) your device should appear as Qualcomm HS-USB QDLoader 9008 using a virtual COM port. If you can see it, then you can continue to the flash section, step 14. Otherwise, if you do not see anything or a DFU device, then you'll need to explore the next option.
Option B: USING THE BUTTON COMBO
04. Press the VolUp and VolDn buttons in your device and keep them pressed.
05. Now press the power button until the red LED flashes, it does it really quick. Then release the buttons, starting by the power button.
06. Plug the device to your computer.
In your computer right click in the Windows Start Menu icon and select Device Manager. Under Ports (COM & LPT) your device should appear as Qualcomm HS-USB QDLoader 9008 using a virtual COM port. If you can see it, then you can continue to the flash section, step 14. Otherwise, if you do not see anything or a DFU device, then you need an EDL cable.
OPTION C: USING THE EDL CABLE
So, you need to get a Qualcomm EDL cable. With it you can recover from any situation. I use this one, DrakenFX uses this other model. There are cables out there not working properly so do not try to save 4 or 5 bucks and get yours from a reliable source. Alternatively you can solder your own by following this guide. If you are in an emergency (or your patience threshold is very low) and have a thin wire around you, then you can follow this DIY hack video.
Do you already have the EDL cable? then follow these steps:
07. Connect your bricked Axon 7 to your PC using the EDL cable.
08. Press the EDL cable button and keep it pressed.
09. Press the Power button of your bricked unit and keep it pressed too.
10. Wait 20 seconds.
11. Release the power button.
12. Wait 10 seconds.
13. Release the button of the EDL cable.
Voilà, your device is now in EDL mode. The device manager in your PC, under the ports category, should detect it as Qualcomm HS-USB QDLoader 9008. Now you can proceed to the flash section. If this procedure doesn't work, then your unit could have a hardware problem. Your only hope is to dissemble it by following this last resort guide.
3. FLASH FIRMWARE
14. Open MiFlash in your computer.
15. Click Browse button and select the folder you created in step 03 with the stock firmware files.
16. Click Refresh button and your device will appear listed as virtual COM port.
17. Click Flash button and wait for a few minutes until it finishes. Note that the bottom options are not applicable.
18. Now you have a stock Axon 7. Your data partition will still have garbage data, so you should enter recovery by pressing VolUp while rebooting your device with the power button. Release VolUp only when you reach Recovery. Using Recovery do a Factory Reset of your device.
That was the last step. Hopefully now you have a fully functional stock Axon 7.
By the way, this guide can also be used to return to stock any working device for selling or service!!!!
Cheers!!!!
Nice! I just disassembled mine and did it that way the other day.
thank you.
i will save the files and guide for rainy day.
i have A2017 that i converted into A2017U; which file do i need to download?
@Oki
Thnx for this guide :good:
Find the latest A2017G N-B10 here
Harmtan2 said:
Nice! I just disassembled mine and did it that way the other day.
Click to expand...
Click to collapse
Glad to see you solved your issue.
mb0 said:
thank you.
i will save the files and guide for rainy day.
i have A2017 that i converted into A2017U; which file do i need to download?
Click to expand...
Click to collapse
I don't know what you mean about converting an A2017 into an A2017U. They are the same device except for the radio, that that's a hardware difference. You should always use the right modem firmware for your radio hardware so you should use the A2017 modem firmware. After unbricking your unit, you can unlock it again and flash any universal firmware the same way you did before. It is a long but safe process.
yes, i meant to say that i flashed U radio over my A2017
so China version is for me.
mb0 said:
yes, i meant to say that i flashed U radio over my A2017
so China version is for me.
Click to expand...
Click to collapse
If you flashed the A2017U radio in a A2017 hardware and worked fine for you, then you can use the A2017U B35 stock firmware.
What will be the bootloader status after following this guide? I need my phone with a locked bootloader.
My phone shows up as Handset Diagnostic Interface (DFU) (COM3) but it doesn't get detected on Miflash program......
aLexzkter said:
What will be the bootloader status after following this guide? I need my phone with a locked bootloader.
Click to expand...
Click to collapse
It should be locked. But in case you end up with an unlocked phone, then locking it is very easy. You only need to connect your phone, enter into fastboot mode, download the adb/fastboot tools and execute the command fastboot oem lock from your computer.
Oki said:
It should be locked. But in case you end up with an unlocked phone, then locking it is very easy. You only need to connect your phone, enter into fastboot mode, download the adb/fastboot tools and execute the command fastboot oem lock from your computer.
Click to expand...
Click to collapse
I can't get into EDL mode. I hold down volume buttons, then power. When the red led lights up, I unpress power, then the volume buttons, connect the USB cable and nothing happens on my phone (black display) red led still on. On my computer I see ZTE Handset Diagnostic Interface(DFU) (COM3).
Edit: I managed to get into EDL mode thanks to Axon 7 EDL Tool but I got a "File analysis: error" "not important files found" so I went back to MiFlash and also got an error about the files. Will update the post when I get it to work.
aLexzkter said:
I can't get into EDL mode. I hold down volume buttons, then power. When the red led lights up, I unpress power, then the volume buttons, connect the USB cable and nothing happens on my phone (black display) red led still on. On my computer I see ZTE Handset Diagnostic Interface(DFU) (COM3)
Click to expand...
Click to collapse
You can enter EDL mode from the system. Just install any terminal app, open it and enter the command reboot edl
Oki said:
You can enter EDL mode from the system. Just install any terminal app, open it and enter the command reboot edl
Click to expand...
Click to collapse
xD My phone was bricked. I thought this tutorial was mainly targeted for bricked devices.
Anyway, my phone is working now. The downloaded EDL zip was corrupt so it only had a few files inside.
@Oki
Edit: I have a working phone on Nougat B10. But I can't lock the bootloader because I don't have access to fastboot. My phone's variant is A2017G
aLexzkter said:
xD My phone was bricked. I thought this tutorial was mainly targeted for bricked devices.
Anyway, my phone is working now. The downloaded EDL zip was corrupt so it only had a few files inside.
@Oki
Edit: I have a working phone on Nougat B10. But I can't lock the bootloader because I don't have access to fastboot. My phone's variant is A2017G
Click to expand...
Click to collapse
Glad to see you solved your issue. I misunderstood your problem. I thought you had access to the system and not to recovery or fastboot. Anyway, this guide is for unbrick or return to stock. I'll investigate the relock problem. Usually clearing devinfo partition should be enough to relock any bootloader.
Oki said:
Glad to see you solved your issue. I misunderstood your problem. I thought you had access to the system and not to recovery or fastboot. Anyway, this guide is for unbrick or return to stock. I'll investigate the relock problem. Usually clearing devinfo partition should be enough to relock any bootloader.
Click to expand...
Click to collapse
In order to get access to fastboot I had to use the tool Axon7Toolkit, select "unlock bootloader" option, make sure you have an old version of MiFlash installed (20161212) and then you can select "lock bootloader" on Axon7Toolkit.
Thanks for everything.
aLexzkter said:
In order to get access to fastboot I had to use the tool Axon7Toolkit, select "unlock bootloader" option, make sure you have an old version of MiFlash installed (20161212) and then you can select "lock bootloader" on Axon7Toolkit.
Thanks for everything.
Click to expand...
Click to collapse
Well, I am considering to link the older Marshmallow ROMs since the Nougat ROMs have some issues with fastboot. Anyway. It is going to take some time to test the alternatives. Thanks for letting us know!
Some of the most recent firmware for Axon 7 (@NFound's B12 bootstack, I think) doesn't support the EDL button combo. But if you have TWRP installed, you can boot to recovery, then reboot to EDL from there.
I kept getting the device registering in device manager in DFU mode. But I noticed that it briefly registers as QUSB_BULK before reverting to DFU. So I installed zadig winUSB driver and now it registers as QUSB_BULK when I turn on the device pressing all 3 buttons.
How can I proceed now?
Hi there
Thanks for this guide. I have a 2017U, so I got A2017U_B35_NOUGAT_FULL_EDL.zip file. After unzipping and connecting the phone to the computer it gets properly recognized and i can start the process from the MiFlash program. After reaching somewhere between 30-40% of the flashing process, it goes suddenly to 100% and it says that is finished. When I reboot the phone, it appears as if I was still under an unlocked bootloader (warning message + TUX penguin image) and the phone starts but during the initial setup process, i chose to start as a new phone but it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device" and obviously this is not what I am interested for.
How can I get rid of this message and get a full clean install, with bootloader relocked and all that??
Thank you for any help you can provide!
Flogisto said:
Hi there
Thanks for this guide. I have a 2017U, so I got A2017U_B35_NOUGAT_FULL_EDL.zip file. After unzipping and connecting the phone to the computer it gets properly recognized and i can start the process from the MiFlash program. After reaching somewhere between 30-40% of the flashing process, it goes suddenly to 100% and it says that is finished. When I reboot the phone, it appears as if I was still under an unlocked bootloader (warning message + TUX penguin image) and the phone starts but during the initial setup process, i chose to start as a new phone but it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device" and obviously this is not what I am interested for.
How can I get rid of this message and get a full clean install, with bootloader relocked and all that??
Thank you for any help you can provide!
Click to expand...
Click to collapse
There ate several ways to remove that. One involves TWRP 3.2.1-7 and the other Axon 7 EDL tool, if you dont have TWRP then use the second . Jusy go to the unlock menu and apply the google unlock.
A third way would be to setup the phone with your old google account and do afactory reset from within Android, not from the bootloader. That would remove also the owner safety.
Thank you so much for your guide and software bundle.
I even had to make a EDL cable to restore my device.
After flashing, I do not see vendor as a partition but looks like it is a folder. Is it OK for future ROMs ?

How to get Edl working in the DFU MultiDL tool by Raystef66

So by now most of you have seen the DFU MultiDL tool by @raystef66 only you had to switch from Multi tool to Miflash or Edl Tool.
I have worked out how to get Edl working in this tool.
First of all this tool was designed to run on Windows 7 so in Windows 10 it didn't seem to function properly.
So I set it to Windows 7 compatibility first off to see if it would work.
I had better results with phone detecting and saying connected instead of disconnect.
Next the phone needed to be booted into FTM mode if you are just flashing an Edl package, if your phone is in DFU it skips this step as per the instructions below.
Next I found it was better to place the Edl package within the MultiDL tool folders.
C:\program files > DFU MultiDL tool > DA > SMT > firehose and overwrite the exsiting firehose file.
Pics posted below show instruction (tranlated from Chinese to English) and MultiDL tool in flashing progress (sorry they are not very clear)
I hope this helps
I am trying to relock my bootloader to send my phone in for a warranty replacement, but EDL mode is disabled because I'm on B35. Can I use this tool to achieve that? I'd appreciate any help...
parmar.saab said:
I am trying to relock my bootloader to send my phone in for a warranty replacement, but EDL mode is disabled because I'm on B35. Can I use this tool to achieve that? I'd appreciate any help...
Click to expand...
Click to collapse
Boot your phone into FTM mode to start the process, it should switch to Edl mode.
This tool won't lock the bootloader, however some Edl packages will have a locked boot image.
If your Edl is still locked try the Edl tool by Djkuz.
Start Edl tool as admin, boot into FTM to start, follow the on screen instructions then unlock then choose Edl fix.
You may be able to lock the bootloader with Edl Tool or use the Axon 7 tool kit to relock.
I hope this helps
Syberclone said:
Boot your phone into FTM mode to start the process, it should switch to Edl mode.
If your Edl is still locked try the Edl tool by Djkuz.
Start Edl tool as admin, boot into FTM to start, follow the on screen instructions then unlock then choose Edl fix.
I hope this helps
Click to expand...
Click to collapse
This is the error I get in the EDL tool:
parmar.saab said:
This is the error I get in the EDL tool:
Click to expand...
Click to collapse
I can't get the pic to show properly, what is the error?
Make sure you have the Edl tool in the root directory of the drive.
Eg: C:\ or D:\ for it to operate properly.
Can you boot to FTM?
parmar.saab said:
This is the error I get in the EDL tool:
Click to expand...
Click to collapse
What happens if you use the key combination? Hold Vol+, Vol- and power. If there's a constant red LED then you're on DFU. Right after just use this tool and you'll get to EDL
But I don't get it? If you want to relock the bootloader, you'll have to roll back to B19. If you'll do so just flash the stock recovery and use a B19 package from ZTE US
Choose an username... said:
What happens if you use the key combination? Hold Vol+, Vol- and power. If there's a constant red LED then you're on DFU. Right after just use this tool and you'll get to EDL
But I don't get it? If you want to relock the bootloader, you'll have to roll back to B19. If you'll do so just flash the stock recovery and use a B19 package from ZTE US
Click to expand...
Click to collapse
Here's my situation:
I have an A2017U, that was initially running 15.1 and developed an issue that requires me to send it in for a warranty exchange. I found a thread to return it to stock, which left me on B35 stock with TWRP still intact. However, my bootloader if still unlocked, and I need to relock it before sending the phone in. I am somewhat of a noob when it comes to this, but what exactly would I need to do in order to relock the bootloader? I'd greatly appreciate it if you could point me in the right direction.
parmar.saab said:
Here's my situation:
I have an A2017U, that was initially running 15.1 and developed an issue that requires me to send it in for a warranty exchange. I found a thread to return it to stock, which left me on B35 stock with TWRP still intact. However, my bootloader if still unlocked, and I need to relock it before sending the phone in. I am somewhat of a noob when it comes to this, but what exactly would I need to do in order to relock the bootloader? I'd greatly appreciate it if you could point me in the right direction.
Click to expand...
Click to collapse
well, as a first you could respond to my question ?
If you can get into EDL by the key combination, then you're done. Just use a B19 EDL package to go back and you'll have fastboot there. After that, run the command to relock
Choose an username... said:
well, as a first you could respond to my question
If you can get into EDL by the key combination, then you're done. Just use a B19 EDL package to go back and you'll have fastboot there. After that, run the command to relock
Click to expand...
Click to collapse
That's the problem, the key combination doesn't work to get the phone into EDL mode (I'm guessing it's because it is disabled on B35). In essence, I don't have fastboot access. I tried relocking in FTM but get the error as shown in the picture.
parmar.saab said:
That's the problem, the key combination doesn't work to get the phone into EDL mode (I'm guessing it's because it is disabled on B35). In essence, I don't have fastboot access. I tried relocking in FTM but get the error as shown in the picture.
Click to expand...
Click to collapse
still you don't really respond. What HAPPENS when you use the key combination? Does it reboot? Does it stay black and show a red LED? Black with no LED?
Anyways, you can enter EDL simply by enabling adb and issuing "adb reboot edl" from the system. (or from FTM). it just seems weird that it would reboot, because usually the phone just goes into DFU when you use the combination
When I use the button combination, the phone shows a blank/black screen with a solid red notification light. However, I get no response on any commands from the Axon 7 Toolkit.
@Syberclone: Thanks for the recommendation to run the tool in Win7 compatibility mode, I have Windows 10 and the tool always shows as disconnected. I can use the tool to switch from DFU to EDL, no problem, but could never figure out how to use it to flash an EDL.
I'd like to point out that FTM isnt accessible if you're not running a stock-based ROM. In all my tests I was never able to boot into FTM on custom ROMs like LineageOS, AOSP Extended, etc.
However, if you can boot directly into EDL with the buttons, or can use this tool to switch from DFU to EDL, then access to FTM doesn't matter.
@parmar.saab: A black screen with a solid red light is DFU mode, you need to use the DFU MultiDL Tool to switch from DFU to EDL. EDL is a black screen too, but has a red light that will turn off if you use the button combo. In other words, it will blink rather than staying solid. Then you can use the Axon 7 Toolkit or Axon 7 EDL Tool to flash an EDL. Or you might be able to flash with the DFU tool, if you can get it to work.
@AnonVendetta No problem
It took me a while to work it out, a bit over 2 hours of testing and retesting using my Axon.
I didn't want to put it in to DFU to do a full test, however it worked a treat once I got it sorted.
FTM was as per the Chinese instructions not actually mine, apparently if the phone is in DFU the app will work accordingly.

[GUIDE][NORD/AVICII] Noob friendly guide to Unbrick/Restore Stock OxygenOS Firmware

Generic Disclaimer: By doing any of the process listed below you accept complete responsibility over any of your actions, I will not be responsible if you end up causing hard brick, data loss or any kind of loss to your personal property.
Hii XDA fellows,
So I have seen many people asking for noob friendly guide to restore original oxygen os firmware or basically unbrick device. There are several thread on this already but trust me I have tried them all and in my case I had to use my own brain. So I have compiled a noob friendly guide which I,myself have used to unbrick my device.
small warning this will wipe all of your data.
Firstly I wants to thank Some_Random_Username for bringing up MSM Unbrick tool for OnePlus Nord. His guide to unrick nord is also fairly good enough but in my case I was stuck in bootloop after installing a rom. My phone was not even booting to Qualcomm EDL Mode so that I can use MSM Tool.
Lets start with pre-requisites:
You must have unlocked bootloader.
Original Oneplus Type - C cable.
Windows PC.
ADB debugging turned on your phone.
Firstly Switch off your device, which I think most of you have already have as the device is bricked but in case your phone is stuck in bootloop or recovery or bootloader menu itself then try holding down voume up button and power button together hold them down till you get heptic feedback and screen goes off. Let it be cool down for about a minute.
Now Setup your PC:
Download MSM tool to from this guide : Click here
Setup adb environment in your PC if you havent already setup follow this guide
Download Qualcomm EDL drivers from here: Click here
Now download Unofficial TWRP recovery by Mauronofrio from here
On your PC right click on start menu icon and start Windows Powershell(Admin) and type this command bcdedit /set testsigning on This will turn off driver signature verifications on windows you will be required to restart your pc now after you restart your pc will boot into test mode and you'll see a watermark stating the same in bottom left of your desktop. Worry not we will undo this after we have finished restoring.
install Qualcomm EDL drivers by running the setup listed above.
Unzip MSMTool there you will see a file named MsmDownloadTool V4.0.exe run it, it'll take some time but after you see a pop up asking for user type user name and password, Select other as user type and leave other stuffs blank as it is and click next.
In the next window, In the target button select O2 while using global tool or India while using indian tool or EU when using european tool.
Now you have to boot into Qualcomm Emergency Download Mode
You can do this in several diffrent ways but one I am listing here is recommended :
Boot into fastboot/bootloader mode by pressing and holding Volume up, Volume down and power button together when you see a Menu pop up on your screen you can let go all the fingers at once.
Now connect your phone to your PC and go to that folder where TWRP recovery is located. Hold Shift button and Right click inside that folder you'll see an option "Open powershell window here click on it. In the powershell window type
fastboot devices and press enter your device will be listed as fastboot devices in powershell window. Now type
fastboot boot twrp1.img press enter
your device will boot up in TWRP recovery in twrp recovery go to reboot section and select Edl, This will boot your phone Edl mode your screen will go off as soon as it happens in the MSM tool window you'll see a device listed as com3/com5/com7.
Click on start button the restoration process will begin. Wait for about 400 secs and your device will automatically boot up.
Voila you've successfully unbricked your phone.
If you want to exit from Driver test mode on your pc simply start a powershell window with admin rights and type
bcdedit /set testsigning off
and restart your PC.
So first off all i want to say thanks for this guide.
So , i have a problem with my phone getting reconized by my pcs, so, my Phone just works fine but i want to restore it to stock, i'm using aospex 8.3.
Since a few days my phone dosnt get reconzied by my pc, i've tried windows and linux, both installations cant find my phone, i tried diffrent pc's,usb cables, driver, new installations of windows and linux mint, other phones dont have this problem, tried resetting , everything, do you have a idea what i could try or could it be just my phone port thats damaged and cant transfer data anymore, if anyone has an idea i would really be happy about an answer , thanks!
peppanzer said:
So first off all i want to say thanks for this guide.
So , i have a problem with my phone getting reconized by my pcs, so, my Phone just works fine but i want to restore it to stock, i'm using aospex 8.3.
Since a few days my phone dosnt get reconzied by my pc, i've tried windows and linux, both installations cant find my phone, i tried diffrent pc's,usb cables, driver, new installations of windows and linux mint, other phones dont have this problem, tried resetting , everything, do you have a idea what i could try or could it be just my phone port thats damaged and cant transfer data anymore, if anyone has an idea i would really be happy about an answer , thank
Click to expand...
Click to collapse
Seems like it's a software issue probably a bug in your rom rich out to the developer he might help you, as you have tried both with Linux and windows i don't think it's a driver issue, it could be an issue with the hardware also but chances are pretty low for this to happen. Try flashing other roms if you have backup of your phone, use orange fox recovery it has an option of taking nandroid backup.
IamAlok said:
Seems like it's a software issue probably a bug in your rom rich out to the developer he might help you, as you have tried both with Linux and windows i don't think it's a driver issue, it could be an issue with the hardware also but chances are pretty low for this to happen. Try flashing other roms if you have backup of your phone, use orange fox recovery it has an option of taking nandroid backup.
Click to expand...
Click to collapse
the thing is that i cant flash other roms, my phone dosn't gets recognized in fastboot, recovery and edl, so with the aex recovery installed i have no chance to change the rom without a pc, reached out to the dev but seems i'm the only person with the proplem, but thanks for helping.

Question Possible to get Android 12 via China rom?

So my question is that is it possible to flash China rom to global version and get OTA upgrade to android 12 as I heard china devices are getting zui 13?
It's available here. If you attempt to flash it, make a .qcn backup of your nv data first. You can attempt to flash it with these instructions (7th post), only if you have all the drivers necessary for both LMSA/RSA & QPST/QFIL and know how to set it up correctly (firehose config needs to be set to not erase; you will need to set storage type to ufs).
Problem is i cant unlock the bootloader yet cause adb devices command doesnt show up the phone. Tried couple of drivers but didnt work.
You don't need to unlock your bootloader as it will most likely be relocked once you flash it. Do you have these (not just for OnePlus8, for all Qualcomm devices)?
Ok I was able to connect and unlock bootlader. I am downloading China rom now and will try flashing using the instructions. Hopefully it doesn't get bricked.
Make a backup of your nv data (QCN) first. Then do both edit 1 & edit 2 of the instructions posted and make sure to do it carefully, or if you're brave enough do only edit 2.
So I followed the instructions and after flash it went black screen. It doesn't boot or get detected by RSA. Only thing I can do is QFIL detects COM6 port when connected
Force shut it down, hold power until screen flashes on. You forgot to check "Reset after downloading". If that doesn't work you will need to use the other firehose protocol (lite) and that should restore it to a booting state.
&(*) said:
Force shut it down, hold power key for until screen flashes on.
Click to expand...
Click to collapse
I think its in EDL mode cause nothing else happens. Do you use telegram or whatsapp?
Holding power doesn't do anything? It should at least shutdown and reboot and if the screen briefly flashes then yes it is in EDL. You will need to flash it back to Global or whatever was previously on it. Did you unlock the bootloader first or not? That might have been the issue.
Nope nothing happening when holding shutdown. When I hold for 15 sec then it resets phone but always black screen. I can understand that it reset from QFIL cause COM port gets disconnected then reconnects. I think its hardbricked now and there is no QFIL rom I could find so have to take service center then...
bukeyolacan said:
Nope nothing happening when holding shutdown. When I hold for 15 sec then it resets phone but always black screen. I can understand that it reset from QFIL cause COM port gets disconnected then reconnects. I think its hardbricked now and there is no QFIL rom I could find so have to take service center then...
Click to expand...
Click to collapse
Okay, try flashing it again with the firehose config option checked "Reset after Downloading". You used EDL to flash it the first time, right? If you still get a black screen you will need to flash the original Global firmware back onto it. You state that RSA doesn't find it? Did you unplug and plug it back in or leave it plugged in?
One other thing you might of forgot to change, storage type to UFS.
I tried firehose flash many times but keep getting sahara fail error or process fail. Storage type was always ufs I never touched it
Use firehose lite and check to see if device manager shows any yellow exclamations now.
Tried lite now, there is android device in device manager with yellow
Is it possible for you to connect remotely via teamviewer or do you know someone that can fix if I pay?
You can fix it. Just try updating the driver automatically and see if it finds it first
&(*) said:
You can fix it. Just try updating the driver automatically and see if it finds it first
Click to expand...
Click to collapse
I think its out of my level now, would need some help with it
The driver package you installed will read the USB ID and should find it within DriverStore. Right click on the android device that has the exclamation and update the driver.

Question How to reboot to Qualcomm EDL mode without ADB?

The TL;DR is, I bricked my phone (TMo Nord N200 5G, SIM unlocked, Bootloader unlocked). I'm trying to use the MSM to recover it. I can't boot to EDL (hold down volume up and volume down at the same time, while pressing power or plugging a USB cable into my PC). It just boots to Fastboot when I follow that procedure. I can't get to a place where I can use ADB commands (ADB shows device "unauthorized").
Longer version, my stock phone was upgraded to the June patch level, I think.
I did the SIM unlock, unlocked the bootloader, and installed the drivers.
I successfully flashed the latest PHH squeak FOSS by following this guide but it had some quirks that I wasn't completely satisfied with.
I flashed a SparkOS GSI linked from somewhere else, but it constantly beeped at me after I disabled Google Play Services, so I decided to move on.
I think the next OS I tried was CRdroid from the same place, but I also replaced the boot.img with a stock one that was patched for Magisk. I can't remember why I thought this was a good idea. There was also a thread that said Magisk doesn't like having nothing in system_a so flash this blank partition using these commands. It always errored out, but I tried it before rebooting.
At this point, my phone would either boot to Qualcomm CrashDump on its own, or Fastboot if I held volume down.
Using the latest Fastboot Enhance I was able to get into fastbootd by switching to "A" active, then rebooting to fastbootd. Have to remember to switch back to "B" active to get anything else to work.
I've tried flashing a few different things since I can get to fastbootd now. I'm no longer booting into the Qualcomm CrashDump, it reliably boots to fastboot as long as I'm "B" active. I just can't get anything resembling a working OS.
I've tried flashing the OTA TMo with Fastboot Enhance a few different times, and a few different GSIs through fastboot, and I really want to get back to stock now so I can start all over.
I've also tried a couple different MSM tool versions, but since my phone is never in EDL, it's never recognized.
Thank you for any assistance.
Holding the Vol +/- & power WILL force boot the N200 to EDL mode regardless of the software corruption as this is at the hardware level.
The thing you need to be concerned with is that you have the latest Qualcomm ADB tools installed so msmtool will recognise the phone while in this mode.
Install the latest adb driver and go into that folder when typing the command as you might have older adb installed already at another location (and in the system path) that is running instead.
Android MTK - How-to Guide and Root Tutorials
Android MTK is one of the best websites that provides the latest Root Tutorial, USB driver, Android Tool, Stock Firmware and How-to Guide.
androidmtk.com
Then you need to have msmtool running and ready to begin and the mouse button hovering over the start button. As soon as the first logo screen comes up, it will only go into EDL mode for about 3-4 seconds and then move on to booting and dump you into fastboot if the rom is corrupt/missing. You need to watch msmtool on the first line and the second it shows up, click start and it will flash.
If you are still missing it and in fastboot I think the the N200 supports the force phone to edl mode by fastboot command:
fastboot oem edl
scanman0 said:
Holding the Vol +/- & power WILL force boot the N200 to EDL mode regardless of the software corruption as this is at the hardware level.
The thing you need to be concerned with is that you have the latest Qualcomm ADB tools installed so msmtool will recognise the phone while in this mode.
Install the latest adb driver and go into that folder when typing the command as you might have older adb installed already at another location (and in the system path) that is running instead.
Android MTK - How-to Guide and Root Tutorials
Android MTK is one of the best websites that provides the latest Root Tutorial, USB driver, Android Tool, Stock Firmware and How-to Guide.
androidmtk.com
Then you need to have msmtool running and ready to begin and the mouse button hovering over the start button. As soon as the first logo screen comes up, it will only go into EDL mode for about 3-4 seconds and then move on to booting and dump you into fastboot if the rom is corrupt/missing. You need to watch msmtool on the first line and the second it shows up, click start and it will flash.
If you are still missing it and in fastboot I think the the N200 supports the force phone to edl mode by fastboot command:
fastboot oem edl
Click to expand...
Click to collapse
Thank you for responding!
The command fastboot oem edl is returning either:
FAILED (remote: 'Command not supported in default implementation')
FAILED (remote: 'unknown command')
I'm running fastboot version 33.0.2-8557947, it's not in my system path.
From a full power off, holding the buttons and plugging in the USB cable, it's about 5 seconds until I see the OnePlus logo, then 2 more seconds before I drop into Fastboot. I'm not sure what I'm looking for, to confirm EDL mode. I'm not seeing my Device Manager update in that time, and the MSM tool isn't displaying anything, either.
try insert cable then volume + and - and power. keep it holding for 10-15 seconds or till you see qualcomm device in device manager
qualcomm drivers
Qualcomm_Drivers_Setup.exe
drive.google.com
try holding both volume buttons (make sure its off!) then plugging your phone in to the computer with msm tool open (you can pre-press the start button) (make sure you have all the drivers installed)
How can I verify that I have all of the required Qualcomm drivers installed?
I've run pretty much every driver install in this thread, or that I could find by searching, and it still seems like my laptop isn't recognizing the phone.
yrrebeulB said:
How can I verify that I have all of the required Qualcomm drivers installed?
I've run pretty much every driver install in this thread, or that I could find by searching, and it still seems like my laptop isn't recognizing the phone.
Click to expand...
Click to collapse
Open up Device Manager in windows. and then attempt to connect it to the computer while in EDL mode. In EDL mode it will still look like it's off btw, that confused me a lot.
You're looking for a device to show up in Device Manager when you connect it. If you're in EDL mode and have the driver's installed correctly it'll say qualcomm-something-something. If you see unknown device, you don't have the drivers installed. If no new device is detected either you're not in EDL mode or you should try a different cable.
Same issue as OP, won't boot into edl
edit: use USB 2.0
You can try enumusb.exe here: http://www.temblast.com/windows.htm
Code:
C:\>enumusb.exe /l /v05c6 /p9008
It will list the first time that a QUSB_BULK was plugged into a port, even if there was no driver found/loaded.
If you want, you can clear past connections by (needs to be admin command line):
This does no harm. I clear everything out occasionally, it just means that next boot will take 5 seconds longer while it discovers "new" devices and installs the same drivers.
Code:
C:\>enumusb.exe /d /v05c6 /p9008
Or, if you don't like that, just plug your device into a different port and see if another port is listed in enumusb.exe /l
On that same page you can find usblog.exe
You just run it and it will show you what pops up and down.
But, this only shows devices that Windows has loaded drivers for.
swee08315 said:
Open up Device Manager in windows. and then attempt to connect it to the computer while in EDL mode. In EDL mode it will still look like it's off btw, that confused me a lot.
You're looking for a device to show up in Device Manager when you connect it. If you're in EDL mode and have the driver's installed correctly it'll say qualcomm-something-something. If you see unknown device, you don't have the drivers installed. If no new device is detected either you're not in EDL mode or you should try a different cable.
Click to expand...
Click to collapse
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
yrrebeulB said:
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
I re-installed the Qualcomm driver bundle while my phone was plugged in and in EDL mode, and MSM finally worked! Thank you kind stranger! I'm back to factory now.
Thank you Strangers ,
yrrebeulB , all of you​
Ytube21 said:
qualcomm drivers
Qualcomm_Drivers_Setup.exe
drive.google.com
Click to expand...
Click to collapse
thank you
yrrebeulB said:
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
this line literally saved me hours
yrrebeulB said:
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
Try my native Windows EDL client. It uses the same Firehose loader as your stock tool does.
At the very least this will give you a second opinion.
http://www.temblast.com/edl.htm

Categories

Resources