Related
Hi, i have an A2017G device with a 7.1.1 stock rom. (no TWRP, no ROOT, nothing!)
I am trying to unlock the bootloader in order to flash a custom rom but MiFLash doesn't detect my device while in EDL mode (adb reboot edl, 15 Seconds ADB installed).
In device manager it is named as QUSB-BULK.
Can someone help me?
Thanks
As far as I know you need Qualcom HS-USB QDLoader 9008 for MiFlash (not really sure though), but give this a try. Right click the QUSB-BULK>Update driver>Browse my comp...>Let me pick...> then pick Qualcom HS-USB QDLoader 9008 if you see it and click next. Also have you tried installing drivers from MiFlash just incase?
Nicz14 said:
As far as I know you need Qualcom HS-USB QDLoader 9008 for MiFlash (not really sure though), but give this a try. Right click the QUSB-BULK>Update driver>Browse my comp...>Let me pick...> then pick Qualcom HS-USB QDLoader 9008 if you see it and click next. Also have you tried installing drivers from MiFlash just incase?
Click to expand...
Click to collapse
Solved:
It was an issue related with drivers/windows 10, i tried using windows 7, same steps, and while in edl mode it was named Qualcom HS-USB QDLoader 9008, then it worked.
PS: installing drivers from MiFlash didn't solve the issue while in windows 10.
Thanks
Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
amus76 said:
Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
Click to expand...
Click to collapse
All right, do this:
-Put the phone in Fastboot
-Open command prompt
-Run "fastboot erase userdata"
If it doesn't work, do this:
-Set up a TWRP on your fastboot folder (rename it to "recovery.img" [BE SURE THAT YOUR PC SHOWS FILE NAME EXTENSIONS] and put it on the folder where fastboot is located)
-Open command prompt in the folder where Fastboot is located
-Run this command:
fastboot boot recovery.img
Your phone should enter TWRP. It's not installed, it just boots it once.
Then try to format data from TWRP. Right after that, use "adb push recovery.img /sdcard" to push the recovery img to your internal storage. Then go (on your twrp) to "Install" - hit "Install image", then select the recovery.img, and select "recovery" and swipe to confirm.
After it is done, install LOS again. If it is 15.1 or 16 you have to have a Vendor compatible TWRP, such as Ordenkrieger's TWRP (From LOS16 thread). Follow the instructions precisely
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
amus76 said:
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
Click to expand...
Click to collapse
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
If you still have access the fastboot
Enter, reboot dm-verity enforcing
Check here
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214
Choose an username... said:
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
Click to expand...
Click to collapse
I did the fastboot boot recovery.img the phone reboot, i get the warning screen for unlocked bootloader and straight after "your device is corrupted and cannot be trusted and may not work properly" with the same style as the bootloader warninr screen.
So without a recovery I can't flash fastboot images
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Syberclone said:
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Click to expand...
Click to collapse
I didn't get access to EDL mode even through ADB, nor FTM screen. So MiFlash is useless
With Axon 7 tool, I tried to flash TWRP with no success, my phone was on DFU
Then I managed to dm-verity encrypted through ADB but the phone was not rebooting on recovery, still fastboot but the phone was not recognize by the PC
I have Qualcomm Drivers installed
Right now with Lineage, I can't acces FTM screen
I just pushed the button twice when I was with the red warninr screen and get access to TWRP (or Lineage boot screen)
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Syberclone said:
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Click to expand...
Click to collapse
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
amus76 said:
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
Click to expand...
Click to collapse
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Syberclone said:
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Click to expand...
Click to collapse
Just with "dm-verity enforcing" with ADB
Then: press button power when on the red warning, a pinguin will appear and again press the power button, it will reboot on TWRP or Lineage
My fasbtoot was inefficient a part for the dm-verity enforcing, no FTM also
amus76 said:
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Click to expand...
Click to collapse
I know this is an old reply, but I arrive from a google search. Sir, thanks a lot for this reply. I was stuck in your same situation and pressing the power button with the linux icon allowed me to go to TWRP. THANKS!
I get the pinguin, but if i press Power again, nothing happened. I have to wait for a while it reboots to System. I tried to hold Power while it is rebooting, but it always reboots to System. No chance to enter twrp...
Hi,
recently I hardbricked mi Mi5s. After reading and trying a lot of things, I managed to unbrick it. So, I left this as a guide of things to try in case someone else hardbricks it.
How did I brick it:
I was trying to fix finger sensor by flashing in EDL mode fastboot ROMS, in order to reflash persistent.img . I accidentally flashed a mi5 (gemini) ROM on the mi5s. After that, the PC recognised the device only as "hs-usb qdloader 9008" in the Windows Device Manager, associated with a COM port. (In my pc, it was COM7 or COM8).
How did I unbrick it:
I disabled integer_checks (following the androidbrick guide provided below) and installed new driver for qdloader 9008.
After that, I used miFlashTool (https://www.xiaomiflash.com/download/) and flashed latest global stable fastboot rom (https://en.miui.com/thread-5927598-1-1.html)
Note: if miFlashTool crashes, create a folder in miflash folder, and rename it to "log".
If you don't have a unlocked bootloader, you *must* use the test-point trick. (Use a deep flash cable) .
Links:
Driver that worked: https://www.mediafire.com/file/so0uvkd6nm6ie1m/Driver_x64.cab/file (x64) & https://www.mediafire.com/file/ryjc83s2ku6mmh5/Driver_x86.cab/file (x86)
Although it didn't work for me (i suspect thats becouse i hadn't installed the driver above), guide to use Qualcomm QFIL: https://en.miui.com/thread-432217-1-1.html
Another guide to Qualcomm QFIL: https://www.androidbrick.com/ultima...s-are-unbrickable-qhsusb_dload_qpst_qfil_edl/
If the PC doens't detect the mobile after installing that driver, it means that you're NOT into EDL mode. If you can't enter fastboot or EDL mode, you need a Deep flash cable. You can fabricate yourself one (there are youtube tutorials for that) using a test-point , or you can buy one from Aliexpress: https://es.aliexpress.com/item/PHON...290.html?spm=a2g0s.9042311.0.0.594263c0eXl7Lh
Guide to understand how EDL works and how to exploit it: https://alephsecurity.com/2018/01/22/qualcomm-edl-1/
Other useful links: https://forum.xda-developers.com/mi-5s/help/stupid-mistake-mi5s-bricked-t3725331
Other useful links: https://www.youtube.com/watch?v=Ds2Bp2TBizc
Other useful links:https://www.htcmania.com/showthread.php?t=1204227&page=5 (Spanish post)
Other useful links: https://www.youtube.com/watch?v=Mp_VdEqi0rc
Good luck!
Thank you for this great guide. Have a good day
is you fingerprint works after edl flashing?
Fastboot is no longer displayed, the screen remains dark. But I hear that the device is recognized. I use a depp flash cable.
MiFlash 20191206
port 9
status: try to reset status
after 18 sec flashmessage: write time out, maybe device was disconnected.
I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
[Thread Closed] Continue here.
I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
Shubham1211 said:
I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
Click to expand...
Click to collapse
Flash your stock recovery back! Twrp is not A11 compatible
Shubham1211 said:
I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
Click to expand...
Click to collapse
pyry666 said:
Flash your stock recovery back! Twrp is not A11 compatible
Click to expand...
Click to collapse
Yes and next time you should better read the threads.
pyry666 said:
Flash your stock recovery back! Twrp is not A11 compatible
Click to expand...
Click to collapse
OMG...how did this slipped through my mind. Damn thank you for this.
Kollachi said:
Yes and next time you should better read the threads.
Click to expand...
Click to collapse
I read many threads dear sir but this point totally slipped my mind about the android. Really appreciate the tip. Thank you.
pyry666 said:
Flash your stock recovery back! Twrp is not A11 compatible
Click to expand...
Click to collapse
ok but how do I flash my stock recovery back?
since the only thing I can access is fastboot mode, I tried flashing a stock fastboot rom but that clearly states that it cant be used to downgrade and currently there are no android 11 fastboot rom available so now what am I supposed to do wait?
Shubham1211 said:
ok but how do I flash my stock recovery back?
since the only thing I can access is fastboot mode, I tried flashing a stock fastboot rom but that clearly states that it cant be used to downgrade and currently there are no android 11 fastboot rom available so now what am I supposed to do wait?
Click to expand...
Click to collapse
Dl your current full rom and extract it from it using payload dumper. There are step by step guides how to do this
pyry666 said:
Dl your current full rom and extract it from it using payload dumper. There are step by step guides how to do this
Click to expand...
Click to collapse
I just did this. So what I did was since there were fastboot stock roms available but not for android 11, I downloaded one...ran it through payload dumper and copied these files to overwrite the one from 10.5.13. But when I did that and everything went 100% as it should. My phone was not turning on now...no response on button presses and no sound when connected to computer...I thought did I really became the first one to hardbrick a oneplus....then I just checked in device manager and it was showing as 9008 at the end..which meant it is EDL mode...that was exactly what I wanted. I immediately started MSM Tool and there it was then I just started and now my phone is back to normal along woth having OOS 10.5.13 exactly what I wanted so thank you for pointing my foolish mistake.
Just replying here because this was the only google result when searching the error messages. I could only get into fastboot, no edl, and recovery gave the error message about download mode. I noticed when holding both buttons down and plugging in it would come up as the Qualcomm USB thing 9008, but every 10s it would reboot again and if I wasn't holding the keys go into fastboot. The solution was...
Have the MSM tool started and ready
In the 5-10s you have while the device shows as Qualcomm USB (QUSB 9008 something) hit the start button
This kept it in that mode and although the screen never showed anything it went through the 300s restore and I was back to stock.
Danmanlott said:
Just replying here because this was the only google result when searching the error messages. I could only get into fastboot, no edl, and recovery gave the error message about download mode. I noticed when holding both buttons down and plugging in it would come up as the Qualcomm USB thing 9008, but every 10s it would reboot again and if I wasn't holding the keys go into fastboot. The solution was...
Have the MSM tool started and ready
In the 5-10s you have while the device shows as Qualcomm USB (QUSB 9008 something) hit the start button
This kept it in that mode and although the screen never showed anything it went through the 300s restore and I was back to stock.
Click to expand...
Click to collapse
Bare in mind that EDL mode doesn't last very long (least it didn't for me)
So make sure you're ready to press start on MSM, once the process has initialized it'll keep it in that mode.
Found it out by trial and error. I too thought I couldn't get into EDL but it's probably the last thing that would fail on the phone, if fast boot is working then EDL almost certainly is too.