Related
Hello my friend just made an update of his phone which is a redmi 3 pro
His little bro shutdowned the phone while update was in process. The result is that now the phone have a bootloop, can't access the recovery (blackscreen when trying) and have a locked bootloader.
So I am not sur how to unlock the BL if I can't install a dev rom and can't boot. Not sur how to get into the recovery with the 2 same problems.
Could anyone help me for this one? Which is hard to me.
Thanks
PS: I tried to do something with unpacking boot and remove a ",verify" thing in the ramdisk but I guess I'll need the unlockedbootloader to flash the new boot.img?
Kicroy said:
Hello my friend just made an update of his phone which is a redmi 3 pro
His little bro shutdowned the phone while update was in process. The result is that now the phone have a bootloop, can't access the recovery (blackscreen when trying) and have a locked bootloader.
So I am not sur how to unlock the BL if I can't install a dev rom and can't boot. Not sur how to get into the recovery with the 2 same problems.
Could anyone help me for this one? Which is hard to me.
Thanks
PS: I tried to do something with unpacking boot and remove a ",verify" thing in the ramdisk but I guess I'll need the unlockedbootloader to flash the new boot.img?
Click to expand...
Click to collapse
I have the similar problem with my Redmi3. The Fastboot screen is the only screen that I can get now. Let me know if you have answer. Thanks.
If you can acces fastboot then just connect the phone to computer in fastboot and enter fastboot oem edl in cmd (maybe you will need Minimal ADB and fastboot to do it). Then flash official ROM via MiFlash.
ohoh seems interesting then it won't say couldn't verify or smthg? will tell that to my friend asap, thanks
EDL mode allows flashing with locked bootloader. Some models have this mode locked, but I think that is not the case with Redmi 3.
Kicroy said:
ohoh seems interesting then it won't say couldn't verify or smthg? will tell that to my friend asap, thanks
Click to expand...
Click to collapse
to go to edl mode just turn off your phone.plug the cable to your laptop or desktop but not to your phone.now be ready to press both volume up and down button as you plug the usb cable to ur phone.immediately after inserting the usb cable press both volume buttons at the same time.it should vibrate and go to edl mode.edl mode appears in black screen so to know if its in edl mode or not open miflash and click refresh ,your device should be shown as com10,20 or com something like that .once you go to edl mode you know what to do if you have used miflash to flash roms.hope this helps you.
jokerpappu said:
to go to edl mode just turn off your phone.plug the cable to your laptop or desktop but not to your phone.now be ready to press both volume up and down button as you plug the usb cable to ur phone.immediately after inserting the usb cable press both volume buttons at the same time.it should vibrate and go to edl mode.edl mode appears in black screen so to know if its in edl mode or not open miflash and click refresh ,your device should be shown as com10,20 or com something like that .once you go to edl mode you know what to do if you have used miflash to flash roms.hope this helps you.
Click to expand...
Click to collapse
I have a problem with my redmi 3. It makes reboot and it does not charge if its not closed.
Can you help me to fix or do you now where i can find a solution.....
geuthym said:
I have a problem with my redmi 3. It makes reboot and it does not charge if its not closed.
Can you help me to fix or do you now where i can find a solution.....
Click to expand...
Click to collapse
Well about that i dont know.but your best bet to solve it is by changing the software.if that does not helps then you should take your device to a technician for repairing.
jokerpappu said:
Well about that i dont know.but your best bet to solve it is by changing the software.if that does not helps then you should take your device to a technician for repairing.
Click to expand...
Click to collapse
When i bouht it the software it was unnoficial then i put with miflash the china dev. All the problem start when i make updates apps and the android web view.
geuthym said:
When i bouht it the software it was unnoficial then i put with miflash the china dev. All the problem start when i make updates apps and the android web view.
Click to expand...
Click to collapse
try flashing official global rom then see if the problem still persists or not
Hey! I am back with some news of my friend!
He tried to run the EDL mode but when he does that the phone simply goes into the bootloop again... He asked a vendor from Aliexpress to get a french rom, is there a way that the phone doesn't have EDL because of the rom or something like that? I mean is EDL a hardware-thing or a software-thing
same problem
cukru said:
If you can acces fastboot then just connect the phone to computer in fastboot and enter fastboot oem edl in cmd (maybe you will need Minimal ADB and fastboot to do it). Then flash official ROM via MiFlash.
Click to expand...
Click to collapse
I have same problem, but this way is not work, because bootloader is locked. Im forget for replacing recovery.img in update package with twrp.
I had this problem before few monthes
my solution was to "force" putting this device on EDL mode
I clicked on vol up + vol down + power together and got into EDL mode, then miflash it.
google - xiaomi understanding download mode
it will send you into miui forum
then second method, download mode, it is what I've described
So, i installed Xposed, and like many people, i got stuck in the logo... No big deal there... Went to look for some help, and it said to go to fastboot, so I went, but it got stuck in the fastboot logo. Then I connected it to the computer and when I try to list the ADB devices I Ialways get an error saying the server is outdated...
I really need some help! I can't find anything online to help me!
Thanks in advance!
Edit: I submitted a bootloader unlock request to Xiaomi earlier today, but I can't see if its approved or not because phone doesn't work
well,
if you are in fastboot mode then the command is "Fastboot Devices", Not "adb Devices"
_____________________________________________
and about boot loop problem try to flash miui fastboot rom.
_____________________________________________
And about bootloader request problem you can go to edl mode and flash miui without any permissions
Thanks:good::good:
nishant2222 said:
well,
if you are in fastboot mode then the command is "Fastboot Devices", Not "adb Devices"
_____________________________________________
and about boot loop problem try to flash miui fastboot rom.
_____________________________________________
And about bootloader request problem you can go to edl mode and flash miui without any permissions
Thanks:good::good:
Click to expand...
Click to collapse
I tried, but i cant seem to go to edl mode through fastboot, any tips? and because of bootloader lock i cant flash fastboot rom with MI Flash
Edl mode needs a specific fastboot version.
For the Redmi Note 3 Pro / Special Edition
Download and extract this package on your PC.
Enter fastboot mode by holding Power and Vol- at the same time. Wait until the Mi Bunny appears, then connect the phone to the PC.
Run reboot.bat in the extracted package. A command prompt will appear. Press a key to reboot the phone to EDL mode.
Upon entering EDL mode, the screen should turn blank. The notification LED might be blinking red. Done.
To get out of EDL mode, hold the Power button for about 10 seconds.
Click to expand...
Click to collapse
Above quote taken from xiaomi reddit wiki.
If the above doesn't work, see the link for deep flash cable, shouldn't be need for kenzo/kate.
How you flashed/installed xposed on locked bootloader is another question?
You may need to update your adb/fastboot version + device drivers(adb)
corkiejp said:
Above quote taken from xiaomi reddit wiki.
If the above doesn't work, see the link for deep flash cable, shouldn't be need for kenzo/kate.
How you flashed/installed xposed on locked bootloader is another question?
You may need to update your adb/fastboot version + device drivers(adb)
Click to expand...
Click to collapse
Ok, so when i try to reboot in edl, it just reboots as normal after screen goes blank...
I installed Xposed with an APK
Sorry if i'm being annoying, but I just want this fixed
KaiZix said:
Ok, so when i try to reboot in edl, it just reboots as normal after screen goes blank...
I installed Xposed with an APK
Sorry if i'm being annoying, but I just want this fixed
Click to expand...
Click to collapse
Mate, watch any video on YouTube. You're not understanding from text instructions.
AtomR said:
Mate, watch any video on YouTube. You're not understanding from text instructions.
Click to expand...
Click to collapse
Can't find any... Recommendations?
EDL Mode: - https://www.youtube.com/watch?v=LDGViyDYPbU
If you can't get into EDL mode, you may need to use the deep flash cable method.
corkiejp said:
EDL Mode: - https://www.youtube.com/watch?v=LDGViyDYPbU
If you can't get into EDL mode, you may need to use the deep flash cable method.
Click to expand...
Click to collapse
I can't get into EDL mode, and I can't make/buy a deep flash cable... I'm getting really scared now...
About ADB, how can I fix it?
KaiZix said:
I can't get into EDL mode, and I can't make/buy a deep flash cable... I'm getting really scared now...
About ADB, how can I fix it?
Click to expand...
Click to collapse
Installing Mi Flash should have put the correct drivers on your PC.
But can be got from here: - https://xiaomifirmware.com/downloads/download-pc-drivers-xiaomi-redmi-note-3/
And I already linked adb/fastboot tools.
IF your comfortable opening your device, there is also a test point method you could try.
http://en.miui.com/thread-244814-1-1.html
Could not find a English video, so maybe try googling more and you might find one.
If not, you could ask at local repair shop, if they would fix it for you. Using Cable/ TP method.
Note for other readers:- MIUI roms need a special version of xposed, for it to work. And installing from an app would more than likely would have use the wrong version. Should never be done on a locked bootloader, only asking for trouble. (Rovo89 is currently trying to bring MIUI support to the official version for nougat roms)
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 ?
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.
Hoping for help here. In trying to root this phone, having successfully unlocked bootloader, I am trying to flash back to stock firmware (as rooting went less than well!)
Couldn;t get the MSM download tool to work, so thought I would try the fastboot zip file extraction method!
The only Oxygen OS I can find that has the flash all .bat file is
10.5.5-GLOBAL-NordOxygen_14_OTA_007_all_2008180221_c45e1d5febd1f-FASTBOOT
Which results in looking like its working within cmd with all fastboot instruction seemingly writing to phone. But upon reboot, it just goes back to the qualcomm crashdump screen....!!
Grateful for any help inc getting the MSM download tool working.
Many thanks all
> 10.5.5-GLOBAL-NordOxygen_14_OTA_007_all_2008180221_c45e1d5febd1f-FASTBOOT
It this from Oneplus Nord ? That cannot work on N10 of course.
Qualcomm EDL mode should always work and is your best way to recover the phone.
andreas__ said:
> 10.5.5-GLOBAL-NordOxygen_14_OTA_007_all_2008180221_c45e1d5febd1f-FASTBOOT
It this from Oneplus Nord ? That cannot work on N10 of course.
Qualcomm EDL mode should always work and is your best way to recover the phone.
Click to expand...
Click to collapse
But whats does Qualcomm EDL mode actually look like? A blank screen? Can't find an explanation as to what the screen shows on Qualcomm EDL mode
TheDon13 said:
But whats does Qualcomm EDL mode actually look like? A blank screen? Can't find an explanation as to what the screen shows on Qualcomm EDL mode
Click to expand...
Click to collapse
yes it is a black screen! You know that is in EDL mode when you look into the "Device Manager" in Windows. Further explanation on how to use the tool is in the respective thread https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/.
andreas__ said:
yes it is a black screen! You know that is in EDL mode when you look into the "Device Manager" in Windows. Further explanation on how to use the tool is in the respective thread https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/.
Click to expand...
Click to collapse
Nowhere does it say EDL mode is simply a blank (as if phone off!) screen btw.....
I always press start on msm tool first then either adb reboot edl or make sure phone is off then hold volume buttons