My phone stuck at QCOM 9008 - Xiaomi Redmi 3s Questions & Answers

I was flash xiaomi.eu package via TWRP and my phone is stuck at edl mode (qcom 900E)
I try to use MiFlash to flash MIUI but it's not recognized my phone
Please help !
Update : I fixed it using EDL cable, turn out I'm stuck at QCOM 900E (black screen,no fastboot, no qcom 9008 and I can't using MiFlash via this port)

Don't panic. Download a fresh copy of the latest official MIUI dev rom fastboot file, force vol dn + power to fastboot mode and then run MiFlash to flash that over 1st. Once that's done, then proceed with TWRP + xiaomi.eu ROM flashing.
I had your exact same issue before.
Sent from my Redmi 3S using Tapatalk

Suo.Eno said:
Don't panic. Download a fresh copy of the latest official MIUI dev rom fastboot file, force vol dn + power to fastboot mode and then run MiFlash to flash that over 1st. Once that's done, then proceed with TWRP + xiaomi.eu ROM flashing.
I had your exact same issue before.
Sent from my Redmi 3S using Tapatalk
Click to expand...
Click to collapse
I made a mistake, when MiFlash are flashing MIUI and I saw MiFlash will lock my bootloader so I un-plug my phone out. Now MiFlash don't recognized my phone anymore

hiimpig1 said:
I made a mistake, when MiFlash are flashing MIUI and I saw MiFlash will lock my bootloader so I un-plug my phone out. Now MiFlash don't recognized my phone anymore
Click to expand...
Click to collapse
You sure you tried to flash a xiaomi.eu ROM (which fyi isn't the main method to flash that btw) before? afaik BL will only be re-locked if you attempt to flash back to official stable?
If that's the case then no choice but to redo with the stable fastboot file instead and then unlock your BL afterwards.
Sent from my Redmi 3S using Tapatalk

Suo.Eno said:
You sure you tried to flash a xiaomi.eu ROM (which fyi isn't the main method to flash that btw) before? afaik BL will only be re-locked if you attempt to flash back to official stable?
Sent from my Redmi 3S using Tapatalk
Click to expand...
Click to collapse
No, I'm tried to flash xiaomi.eu rom when I can access recovery. After flash I press reboot into system and I don't know how I can get into EDL mode. I was stuck in there and I download stable ROM with MiFlash

I fixed it, read update

Same thing has happened to me also. Please help. Phone not turning on.
Status: 85% charged (before this could happen)
unable to enter either fastboot or recovery or even power button. None of them are working.
PC in device manager when connected via usb, detects as "Qualcomm HS-USB QD-loader 9008".
please help.

arceuss said:
Same thing has happened to me also. Please help. Phone not turning on.
Status: 85% charged (before this could happen)
unable to enter either fastboot or recovery or even power button. None of them are working.
PC in device manager when connected via usb, detects as "Qualcomm HS-USB QD-loader 9008".
please help.
Click to expand...
Click to collapse
See OP's solution.
Sent from my Redmi 3S using Tapatalk

arceuss said:
Same thing has happened to me also. Please help. Phone not turning on.
Status: 85% charged (before this could happen)
unable to enter either fastboot or recovery or even power button. None of them are working.
PC in device manager when connected via usb, detects as "Qualcomm HS-USB QD-loader 9008".
please help.
Click to expand...
Click to collapse

Related

URGENT ! Bricked, no download, no recovery after upgrade attempt.

Just bought this phone and attempted to upgrade from 7 to 8 and before so i done few things such as disabling some google sh*t. It upgraded and stuck on booting screen, vibrating sometimes. How do i handle this ? XiaoMiFlash says : flash tz error. Also there's no recovery and download mode.
If you have updated to MIUI 8.1.1.0 then I am afraid you have no other option left than flashing fastboot rom with deep flash cable using test point method presuming you have locked BL. For more info visit http://en.miui.com/thread-310325-1-1.html
But if you are still on MIUI 7 then you can flash using Mi flashtool in EDL mode.
For entering edl mode press volume + and volume - button simultaneously( test mode) and after plugging in USB cable with PC enter in windows CMD:
PHP:
fastboot oem edl
. After that proceed with flashing using flash tool
.
you cant disable Music, Youtube, Chrome,blah blah,... but dont disable Google, it will cause bootloop.
i figured this out after 15 bootloops lol
What ?! What the is deep flash cable ?! I don't have one ! Maybe i should exchange my Redmi 3s in shop next monday. It's stuck at mi logo and 3 circles, vibrating frequently...
UPDATE : Phone enters some screen where shows phone and cable and link to Mi Pc Suite. I click recovery flash option, but i says that phone is up to date. When i click recovery, nothing happens. How do i force flash ? Maybe i will flash a recovery rom using this mode, it's visible via adb.
rahulbarai said:
If you have updated to MIUI 8.1.1.0 then I am afraid you have no other option left than flashing fastboot rom with deep flash cable using test point method presuming you have locked BL. For more info visit http://en.miui.com/thread-310325-1-1.html
But if you are still on MIUI 7 then you can flash using Mi flashtool in EDL mode.
For entering edl mode press volume + and volume - button simultaneously( test mode) and after plugging in USB cable with PC enter in windows CMD:
PHP:
fastboot oem edl
. After that proceed with flashing using flash tool
.
Click to expand...
Click to collapse
Phone won't enter EDL mode ! Just Mi logo and nothing else...
jakubekw1997 said:
Phone won't enter EDL mode ! Just Mi logo and nothing else...
Click to expand...
Click to collapse
I have given you the link about how to make deep flash cable by yourself. Xiaomi has locked EDL mode post MIUI 8.0.3.0. So you wont be able to flash normally in EDL or Emergency Download mode. Now you are in bootloop so either you can unlock your bootloader and flash in fastboot mode, in this case you have to wait bit longer or you can make a deep flash cable and flash in the mode you have mentioned i.e MI logo with PC suite sign.
Sent from my Redmi 3S using XDA Labs
One more device saved
rahulbarai, Dude, I love you, you saved my skin, thought my smartphone had the "bootloader" unlocked, because on the home screen it appears "unlocked" but it was locked, unlocked now I can resurect normally and use the device, thank you very much!

Axon 7 A2017 problem

Hi, i'm domenico, i read everyday your forum from italy. I decided to write here becouse i don't know how to solve this damage.
I have the same problem reported here
https://forum.xda-developers.com/axon-7/help/signal-update-a2017gv1-2-0b02-t3602415
I read around that is needed to do a backup of modem and other file but i dont and now i can't use a sim card it says no network connection and when i try to call tell me airplane mode on.
Anyone please know if there is something i can do? i tried to run fastbot for use miflash and restore the original image but it doesn't work can't go in EDL mode
AmilDK said:
Hi, i'm domenico, i read everyday your forum from italy. I decided to write here becouse i don't know how to solve this damage.
I have the same problem reported here
https://forum.xda-developers.com/axon-7/help/signal-update-a2017gv1-2-0b02-t3602415
I read around that is needed to do a backup of modem and other file but i dont and now i can't use a sim card it says no network connection and when i try to call tell me airplane mode on.
Anyone please know if there is something i can do? i tried to run fastbot for use miflash and restore the original image but it doesn't work can't go in EDL mode
Click to expand...
Click to collapse
Flash universal bootloader and the modem for A2017 from the lineage os thread. Then you should get radio signal again.
I don't know how to do It Can you give me more information please?
AmilDK said:
I don't know how to do It Can you give me more information please?
Click to expand...
Click to collapse
Is your bootloader unlocked? Do you have TWRP? If you do, go to the LineageOS thread (located over 'ROMs, Kernels, Recoveries') and download the 'A2017X Universal Bootloader' and 'A2017 Modem' from there (there should be a link to androidfilehost where the universal bootloader and modem files are located). Be sure that you download the A2017 modem file (NOT the A2017G or A2017U one!).
After that simply put them on your phone and flash them via TWRP
Choose an username... said:
Is your bootloader unlocked? Do you have TWRP? If you do, go to the LineageOS thread (located over 'ROMs, Kernels, Recoveries') and download the 'A2017X Universal Bootloader' and 'A2017 Modem' from there (there should be a link to androidfilehost where the universal bootloader and modem files are located). Be sure that you download the A2017 modem file (NOT the A2017G or A2017U one!).
After that simply put them on your phone and flash them via TWRP
Click to expand...
Click to collapse
Thx for the help, i do not have bootloader unlocked and not have TWRP.
I've installed TWRP but when i try to enter in recovery (Power + volume up) nothing happen. Just blackscreen
AmilDK said:
I've installed TWRP but when i try to enter in recovery (Power + volume up) nothing happen. Just blackscreen
Click to expand...
Click to collapse
What version did you install? 3.1.1-0?
Followed a guide and with minimal fastboot and adb tool put in the phone the 3.0.4-0-ailsa_ii.img successful After that can't go on with steps and if try to open recovery nothing happen
Install Stock ROM from EDL with MiFlash.
WesTD said:
Install Stock ROM from EDL with MiFlash.
Click to expand...
Click to collapse
i tried with twrp 3.1.1.0 same can't access to recovery
miflash doesn't recognise my phone in edl
AmilDK said:
i tried with twrp 3.1.1.0 same can't access to recovery
miflash doesn't recognise my phone in edl
Click to expand...
Click to collapse
Is your phone on edl mode?
Yes i think had a problem with drivers. I out the phone in edl from cmd with adb then opened miflash but can't see the device
AmilDK said:
Yes i think had a problem with drivers. I out the phone in edl from cmd with adb then opened miflash but can't see the device
Click to expand...
Click to collapse
Try 'adb reboot recovery' from cmd
I don't know where i miss, i tried with adb and axon 7 tool, adb edl reboot, axon7tool axon7tool -r gpt boot recovery*, then axon7tool -w recovery, with twrp-3.1.1-0-ailsa_ii.img renamed in recovery bin, but from here nothing happen, i can't go in recovery if i try nothing happen black screen if i put the old recovery.bin can reboot in recovery but can't flash modem file or unlock bootloader. Tried with miflash but nothing happen give me error "cannot receave the hello packet"
PS my buil now is ZTE A2017GV1.2.0B04, the original one was ZTE_A2017V1.0.0B15
Choose an username... said:
What version did you install? 3.1.1-0?
Click to expand...
Click to collapse
i found a post with exactly my situation
https://forum.xda-developers.com/axon-7/help/sim-airplane-offbut-turnd-t3698325
perchance have you the file you talk in this post https://forum.xda-developers.com/showpost.php?p=74386034&postcount=24
i don't know how, but i did it.. with axon7toolkit, restored original rom, then updated to V.2.0.0B13, now works good

QFIL to Leeco le pro 3 (Lex722)

Hello everyone!
my problem is the next: I tried install a rom of MIUI but fail in my device, after, I tried to install differents roms but nothing work, just showed me the logo Leeco and no more, no avance from the logo.
But I still had recovery with TWRP and I thinked I can install official rom 26s, It was my error.
Now follow with the same problem but now I not have recovery mode (show me recovery with logo Leeco but it instantly turns off ) and bootloader is block.
My only hope, is QFIL to recover recovery mode o any rom, Does anyone have it or tell me how to create one?..
Please anybody will can help me, I have this problem 3 days ago.
Sorry for my bad english, I am learning.
PS. I tried with post of tora33 but no work
FlashOne2.0\le_zl1_qfil_ufs\prog_ufs_firehose_8996_ddr.elf"
22:00:34: ERROR: function: rx_data:247 Error occurred while reading from COM port
22:00:34: ERROR: function: sahara_main:854 Sahara protocol error
22:00:34: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
Are you sure you got Qualcomm drivers installed and your phone is in 9008 mode? Also try rebooting and re-enter 9008 mode. But the biggest problem that there is no qfil restoration files for x722 if I remember correctly, chances to boot with x720 ones are quite low.
Does your fastboot work volume and power down same time??
Sent from my LEX727 using xda premium
---------- Post added at 11:09 AM ---------- Previous post was at 10:53 AM ----------
worked on the phone i got off amazon. thanks!
[quote name="wpbear" post=71566961]This works on lastest USA update Stock (21s).
Have ADB/Fasboot tools on your computer
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device
Put emmc_appsboot.mbn from this zip (Download: x727-5.8.019s_bootloader-unlock.zip) in your adb directory on your PC
Put twrp.img from this zip (Download: TWRP) in your adb directory on your PC
On PC open admin CMD prompt
go into fastboot mode on phone (hold power and VOL -)
on PC type:
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
after flash force reboot using Power button. It will ask for a password, just ignore it and reboot back to fastboot by forcing power down then reboot to fastboot (hold power and VOL -)
on PC type:
fastboot devices
fastboot oem unlock-go
fastboot flash recovery twrp.img
boot into twrp (force power down, then hold POWER and VOL +)
TWRP will boot, choose modify system. Choose wipe - then swipe to factory reset, when that is done - then advacned then format data
In TWRP ensure MTP is enabled. In Windows File Explorer the phone should be visibile. Drag and Drop your new ROM.zip, gapps.zip, SU.zip etc...
In TWRP INSTALL new ROM and other zips; choose wipe/dalvik/cache
If you unlock bootloader push power off until it goes off then put it back into fastboot flash twrp .img them power off again power on when phone vibrate volume down you see stock recovery then twrp.
Reboot System.
DONE![/QUOTE]
Sent from my LEX727 using xda premium
voron00 said:
Are you sure you got Qualcomm drivers installed and your phone is in 9008 mode? Also try rebooting and re-enter 9008 mode. But the biggest problem that there is no qfil restoration files for x722 if I remember correctly, chances to boot with x720 ones are quite low.
Click to expand...
Click to collapse
Yeah, that is the problem, I have the drivers and my computer recognize it, the problem, always show the error sahara.
And flash in fastboot no work because bootloader is block and not let me to do flash of anything.
Someone know how to create a qfil? I am developer and I could try but I not found tutorial how to do and I do not have it clear.
zeckAlexs said:
Yeah, that is the problem, I have the drivers and my computer recognize it, the problem, always show the error sahara.
And flash in fastboot no work because bootloader is block and not let me to do flash of anything.
Someone know how to create a qfil? I am developer and I could try but I not found tutorial how to do and I do not have it clear.
Click to expand...
Click to collapse
Every so often the same questions and the same answers.
You should read more. The X722 subforum is for something.
There is no qfil for X722, and there are no magic solutions of X720 / X727. This is an X722, it is locked and NOTHING of X720 / X727 is going to fix it.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Greetings.
How do people keep ending up with bricks? Guess I'll have to find a mod to contact them about stickying a thread about the x722 here about stock 26s. It's a bad idea. Never update your x722 to stock 26s, because your bootloader will get locked when you try to flash TWRP. The only way to get out of 26s is to flash Batyan's 01D ROM (in the x722 Development section here), and then unlock your bootloader and flash TWRP. Flashing TWRP over stock 26s will cause a permanent brick because there's absolutely no QFIL file available for this device. Even in China.
sk8223 said:
How do people keep ending up with bricks? Guess I'll have to find a mod to contact them about stickying a thread about the x722 here about stock 26s. It's a bad idea. Never update your x722 to stock 26s, because your bootloader will get locked. The only way to get out of 26s is to flash Batyan's 01D ROM (in the x722 Development section here), and then unlock your bootloader and flash TWRP. Flashing TWRP over stock 26s will cause a permanent brick because there's absolutely no QFIL file available for this device. Even in China.
Click to expand...
Click to collapse
You know I don't really know how they keep doing it but I seen a lot new ones getting this phone and not really studying how to do this stuff and their not paying attention to what model this have this a solid phone.
Sent from my LEX720 using xda premium
This is true ?
https://dc5.androidfilehost.com/dl/...40/818070582850488404/le_zl1_qfil_ufs_fix.zip
paiktaras said:
This is true ?
https://dc5.androidfilehost.com/dl/...40/818070582850488404/le_zl1_qfil_ufs_fix.zip
Click to expand...
Click to collapse
ZL1 its x720/x727 not x722, it's a fix for ppl thata not work the normal qfil rom.

HELP! I Flashed a corrupted ROM and now I can not unbrick my phone

A few days ago I bought a Xiaomi Redmi Note 7, I unlocked its bootloader successfully and installed OrangeFox Recovery Project. After that, I installed xiaomi.eu ROM EMUI 12 - Android 10, the latest version of the weekly ROMs for this phone. Since it was a beta ROM, I found some bugs, so I downloaded the stable rom with EMUI 11, but I didn't notice that the zip was corrupted so OrangeFox return an error and I made the mistake of restarting the phone. It was stuck in boot logo and when I enter into fastboot mode, the PC doesn't recognize it. Also, the phone can not enter into recovery mode, it stucks in boot logo.
I have the drivers installed because I tested with another xiaomi en fastboot mode and this one is recognized.
I don't know what to do
Sorry for my english, but I am desperate to fix it. I would really appreciate if someone could help me, please.
it's ok , try format data from orangefox and flash a different zip/rom
EgyBob said:
it's ok , try format data from orangefox and flash a different zip/rom
Click to expand...
Click to collapse
The phone can not enter into recovery mode. :/
Can you enter into fastboot with poder off bottom + volume down ?
If you can then flash a fastboot ROM with mi flash
Check out not relock bootloader
Check "flash all" option https://update.miui.com/updates/v1/fullromdownload.php?d=lavender_global&b=F&r=global&n=
its easy
just unlock bootloader again with miflash unlock then flash any rom you like
uriel cruzitho said:
Can you enter into fastboot with poder off bottom + volume down ?
If you can then flash a fastboot ROM with mi flash
Check out not relock bootloader
Check "flash all" option https://update.miui.com/updates/v1/fullromdownload.php?d=lavender_global&b=F&r=global&n=
Click to expand...
Click to collapse
The problem is that since that happened my cell phone is no longer recognized by the computer.
Phone is not recognized by the PC
My phone is connected now and it is not recognized in fastboot mode.
Dont worry, just put in the commands into fastboot. My device dont get recognized too and i can flash everything.
hi my friend.
sry for my bad english.
i had a redmi 4 prime , and had same problem.
thats get unbricked with a shoke on the phone board.
on the main board of the phone , you have 2 little steel circle and named test points and must connect their to each other .
its easy if you can open the phone. if you cant , you must going to a phone repairer.
like this video
youtu.be/7KyYp_lTR0k
i hope can help you
If your phone can still boot up. Just try to fastboot mode power+vol down. Install latest usb driver for PC. Then try one by one usb port you have on your PC. Because I experienced some usb port doesn't work. And if connected try to reinstall TWRP again.
Uses the previous version of twrp, try connecting the phone to another computer. Use xiaomi usb cable.
228as091215t said:
Dont worry, just put in the commands into fastboot. My device dont get recognized too and i can flash everything.
Click to expand...
Click to collapse
Could you explain to me how you did the Flashing using commands? please
Always you can to made test point and flash with miflash . search in google
:good:
01MaxMarvin said:
A few days ago I bought a Xiaomi Redmi Note 7, I unlocked its bootloader successfully and installed OrangeFox Recovery Project. After that, I installed xiaomi.eu ROM EMUI 12 - Android 10, the latest version of the weekly ROMs for this phone. Since it was a beta ROM, I found some bugs, so I downloaded the stable rom with EMUI 11, but I didn't notice that the zip was corrupted so OrangeFox return an error and I made the mistake of restarting the phone. It was stuck in boot logo and when I enter into fastboot mode, the PC doesn't recognize it. Also, the phone can not enter into recovery mode, it stucks in boot logo.
I have the drivers installed because I tested with another xiaomi en fastboot mode and this one is recognized.
I don't know what to do
Sorry for my english, but I am desperate to fix it. I would really appreciate if someone could help me, please.
Click to expand...
Click to collapse
01MaxMarvin said:
A few days ago I bought a Xiaomi Redmi Note 7, I unlocked its bootloader successfully and installed OrangeFox Recovery Project. After that, I installed xiaomi.eu ROM EMUI 12 - Android 10, the latest version of the weekly ROMs for this phone. Since it was a beta ROM, I found some bugs, so I downloaded the stable rom with EMUI 11, but I didn't notice that the zip was corrupted so OrangeFox return an error and I made the mistake of restarting the phone. It was stuck in boot logo and when I enter into fastboot mode, the PC doesn't recognize it. Also, the phone can not enter into recovery mode, it stucks in boot logo.
I have the drivers installed because I tested with another xiaomi en fastboot mode and this one is recognized.
I don't know what to do
Sorry for my english, but I am desperate to fix it. I would really appreciate if someone could help me, please.
Click to expand...
Click to collapse
If you can put your phone in fastboot mode it's easy, 1) download stock rom. 2 ) unzip the file 3) open it ,and copy all files 3) open the file with ( xiaomi drivers ADB ) than : paste. From the files of the ROM you'll see
" flash all " connect your phone in fastboot mode double click "flash all " and flashing process will start immediately, don't remove your phone until it stops, done.
01MaxMarvin said:
A few days ago I bought a Xiaomi Redmi Note 7, I unlocked its bootloader successfully and installed OrangeFox Recovery Project. After that, I installed xiaomi.eu ROM EMUI 12 - Android 10, the latest version of the weekly ROMs for this phone. Since it was a beta ROM, I found some bugs, so I downloaded the stable rom with EMUI 11, but I didn't notice that the zip was corrupted so OrangeFox return an error and I made the mistake of restarting the phone. It was stuck in boot logo and when I enter into fastboot mode, the PC doesn't recognize it. Also, the phone can not enter into recovery mode, it stucks in boot logo.
I have the drivers installed because I tested with another xiaomi en fastboot mode and this one is recognized.
I don't know what to do
Sorry for my english, but I am desperate to fix it. I would really appreciate if someone could help me, please.
Click to expand...
Click to collapse
01MaxMarvin said:
The problem is that since that happened my cell phone is no longer recognized by the computer.
Click to expand...
Click to collapse
Dude , Try Chinese Version on MI PC Suit. That will recognise your phone for Sure. My phone was also in same situation.
Here is the link of Chinese MI PC Suit with English Translation
miui.blog/ any-devices/china-mi-pc-suite-english-translation/ (Remove Space before 'any')
Chinese MI PC Suit has much more features then Global Version. Like Wiping Your Device , Directly Installing Stock ROM, Etc
Contact Me at +918824712945 (WhatsApp Only - If Any Help Needed)
(Try it Once)

Oneplus 8 pro bricked sort of but can't seem to find an option to revert it

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.

Categories

Resources