Develop Bugs

[q] bricked phone - qhsusb_dload

I've tried searching and there doesn't seem to be a solution to this problem for this device.
Yesterday I was flashing ROMs, namely AICP, but I accidentally pressed Reboot to Bootloader in CWM. I got stuck in bootloop after that and it kept returning to recovery. I google'd for a solution and found this(androidforums-.-com-/esteem-all-things-root/478814-how-get-out-clockworkmod-recovery-bootloop.html), which I downloaded and foolishly flashed (devices unsimilar). Flash is successful, and I reboot my phone.
It now will not show the LG splash screen, nor will it enter Download Mode. When connecting the device via USB, it does not seem to add a COM port on the computer. What it does do is try to install a driver named QHSUSB_DLOAD which fails to install.
Could someone please help me solve this problem? Thanks..

dylanraga said:
I've tried searching and there doesn't seem to be a solution to this problem for this device.
Yesterday I was flashing ROMs, namely AICP, but I accidentally pressed Reboot to Bootloader in CWM. I got stuck in bootloop after that and it kept returning to recovery. I google'd for a solution and found this(androidforums-.-com-/esteem-all-things-root/478814-how-get-out-clockworkmod-recovery-bootloop.html), which I downloaded and foolishly flashed (devices unsimilar). Flash is successful, and I reboot my phone.
It now will not show the LG splash screen, nor will it enter Download Mode. When connecting the device via USB, it does not seem to add a COM port on the computer. What it does do is try to install a driver named QHSUSB_DLOAD which fails to install.
Could someone please help me solve this problem? Thanks..
Click to expand...
Click to collapse
Hate to say two things to you bro:
1) You didn't search very hard, because there was a related thread on page 3 with "QHSUSB_DLOAD" in the title
http://forum.xda-developers.com/showthread.php?t=2781522
I forgive though, but just letting you know.
2) You're screwed. The phone is hard bricked. No way to get it back to life.
How do I know? Well, look who's the creator of the thread just linked to.
Read the entire thread. It's not very long.
PS: PM me if your phone is still under warranty and you want advice on how to get it replaced. If you still aren't under warranty, then you're doubly screwed.

Soft bricked zenfone 2. Need help. Need USB Debugging

I have a rooted zenfone 2. I checked for an update. Not knowing the risks of updating system while rooted, I installed the update, and now my phone is stuck on the boot animation screen. It is stuck on "Asus In search of incredible" screen with the turning gear. I can access fast boot mode and recovery mode, but can't start the phone. My phone has Android system recovery installed, not ClockworkMod or TWRP. I tried to install a different recovery, but my PC doesn't read the phone. I thought that wiping the data and cache will help, but didn't. Help me. I'm a 15 year old noob. My parents will kill me!! Also, I haven't tried to install any ROM's on it. So that's out of the picture.
And neither adb, not fastboot can detect the phone.
My phone is rooted, but the bootloader is not unlocked. I was going to unlock it, but thought of backing data up first. I was trying to find the backup app, but accidentally tapped on system update app. I thought there wouldn't be any harm in checking for an update... Apparently their was a lot of harm.
I also tried installing twrp recovery, but it gets stuck on "Waiting for device"
I'm in dire need of help.
I just need to find a way to switch USB debugging on...... That'll fix all my problems
thanks in advance.
I have the Z008 model, NOT the Z00A.

mudit99 said:
I have a rooted zenfone 2. I checked for an update. Not knowing the risks of updating system while rooted, I installed the update, and now my phone is stuck on the boot animation screen. It is stuck on "Asus In search of incredible" screen with the turning gear. I can access fast boot mode and recovery mode, but can't start the phone. My phone has Android system recovery installed, not ClockworkMod or TWRP. I tried to install a different recovery, but my PC doesn't read the phone. I thought that wiping the data and cache will help, but didn't. Help me. I'm a 15 year old noob. My parents will kill me!! Also, I haven't tried to install any ROM's on it. So that's out of the picture.
And neither adb, not fastboot can detect the phone.
My phone is rooted, but the bootloader is not unlocked. I was going to unlock it, but thought of backing data up first. I was trying to find the backup app, but accidentally tapped on system update app. I thought there wouldn't be any harm in checking for an update... Apparently their was a lot of harm.
I also tried installing twrp recovery, but it gets stuck on "Waiting for device"
I'm in dire need of help.
I just need to find a way to switch USB debugging on...... That'll fix all my problems
thanks in advance.
I have the Z008 model, NOT the Z00A.
Click to expand...
Click to collapse
Hey there!, have you fixed it yet? I'm having the same problem i'm trying this method wwwdottechmestodotcom/recover-bricked-asus-zenfone-2/

Maybe u need to look at this post
http://forum.xda-developers.com/zenfone2/general/guide-recover-fastboot-bricked-zenfone-t3284337
hope it will help u.

Phone no longer bricked (yay!), but not fastboot

The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.

kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image

yakub234go said:
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
Click to expand...
Click to collapse
Thanks for the response. I've tried this a dozen times, but unfortunately (this is going to sound weird) since it's not completely bricked it is only detected as Moorefield for a few seconds when started. This allows the xfstk tool to detect it and begin the download, but not long enough to complete the process so it times out. The only development access I have to the phone now is via adb, but since I don't have root I'm very limited in what I can do via command line. Since I can't access fastboot I can't achieve root. It's just a comedy of errors now.

kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..

sukhwant717 said:
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
Click to expand...
Click to collapse
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?

kidnova said:
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
Click to expand...
Click to collapse
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/

mrperalta said:
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
Click to expand...
Click to collapse
I've tried this many times, but it only shows Moorefield for a few seconds. I'm assuming this is because it has a fully operational OS so it doesn't stay in the generic USB device mode.
EDIT: I misread your original post. Holding power and volume DOWN does keep connect it in Moorefield. Thanks so much for that. The problem now is that once xFSTK gets to downloading the OS it reboots the phone which takes it out of USB mode and disconnects the tool. I'm still stuck where I was before, but that's a little progress. Any other thoughts?

New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?

kidnova said:
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
Click to expand...
Click to collapse
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
"those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds"
Click to expand...
Click to collapse
-sukhwant717

mrperalta said:
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
-sukhwant717
Click to expand...
Click to collapse
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.

kidnova said:
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
Click to expand...
Click to collapse
Hi, got the same issues, I've read many posts. Tried all of the million options. What was your final way of doing it, do you remember?

Bootloop without solution? happened suddenly

Hi everyone.
I have been reading a few posts about bootloops in hopes that someone would have been facing the same issue as me. It seems my case is a bit different. I am desperate for some help!
My Max 3 came initially with a chinese ROM but I followed some wonderful tutorials here and I unlocked it and installed initially the xiaomi.eu ROM. Then a couple of months later I installed AOSiP ROM, I updated it a couple of times dirty flashing over it, and settled in exactly the "AOSiP-9.0-Pizza-nitrogen-20190719" build. And there i was, for 4 months, all stable, then suddenly today I was going to unlock the phone with my fingerprint and asked for password.
This happens exactly 1 time per day but I noticed that today it was the second time. Then doesn't matter how many times I put my password correctly, it would keep asking for my password. So I decided to restart the device... and then the bootloop issue started. It starts, reaches the moment in which the AOSiP logo shows and (not even 1 second until the logo shows) freezes, and restarts the device.
I can access the recovery without issues so I didn't panic yet, I backed up all I could, wiped everything I could, started from zero: firmware 9.9.3 + AOSiP-9.0-Pizza-nitrogen-20191117 + gapps. The bootloop still there, in exactly the same way. So at this point I have no clue what could be the reason. I was always careful not to trigger any anti-rollback, it was all going good, now not even with a full factory reset seems to work. I even reinstalled the recovery.
Any ideas? does anyone know what could I try next? Thank you very much advance.

I forgot to attach some logs. I got using the TWRP Advanced > Copy Log option.

Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?

diegoocampo said:
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
Click to expand...
Click to collapse
The mi max 3 has arb enabled, so flashing old rom can cause it to brick.

Have you tried different button combinations to enter fastboot? If you can get to fastboot, just flash a fastboot rom, if that works.
If the brick is caused by triggering ARB, then that may cause some issues, and may need an Authorized Account to flash the ROM from scratch, with some qualcomm flashing tools things.
Though, there may be some way to bypass the authorization for mi max 3 on the internet and have your device unbricked.

Thank you for your replies. Yes probably ARB, I thought my phone had never installed a ROM with ARB and so I was safe to install xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1 (which it is also to be pre-ARB), but I guess I made a mistake at some point.
Situation now:
- with Mi Flash I am getting the authorization error with almost any ROM, with very old ROMs I am not even able to start the flashing process
- with Qualcomm QFIL tool I always get an error "function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes". And I also tried with the patched files from here https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I think at this point I tried everything that can be tried. My bootloader was unlocked, but at this point I am not even sure if its unlocked anymore since I can't see anything on the device screen.
The only positive thing is that the phone always shows under the Windows 10 device manager "Qualcomm HS-USB QDLoader 9008", so at least is a bit alive, and with the Mi Flash at least for some ROMs starts the flash process. I am not sure if disassembling it and trying things like removing the batter would make any difference.
If anyone knows any other way to bypass authorization please let me know.

Here I am back with another update:
- I fixed the full brick by disassembling the phone and disconnecting the battery, with the battery disconnected I could finally flash a Chinese ROM. That however was just the beginning... more problems came
- Common problem I guess is that after booting with that Chinese ROM i was getting a message about how the encryption was interrupted. This was easy, just changed the file system of Data and formatted it and it was fixed.
- Now I am stuck in another hard to solve problem. Any ROM that boots will not allow me to use WiFi or SIM cards. And the reason is that the IMEI is not set anymore. Reading about it I see that this is related with the EFS partition being corrupted. Nothing seems to work now. I don't have any EFS backup . Anyone knows how to fix the IMEI in this case?

5T - device corrupt

Hi Everyone,
I have a 5T running android 9 - completely stock. The device is SIM free, I have never customised it at all - if anything it's never been connected to a PC even.
A few days ago I was using my phone as normal (on whatsapp) but it completely froze. It now boots up to the "Your device is corrupt and cannot be trusted and may not work properly" - it freezes on start up and won't work at all.
- I can get to the fastboot screen
- I can get to the recovery screen to install from ADB
The fastboot screen says in red - device state - locked.
The device is a clean, un-customised phone. Only a few days prior I checked for any OTA updates but I haven't received android 10 yet.
I haven't flashed phone firmware or anything for years now. (By years, I literally mean years - back in the Nokia 8210 days). My only other experience of flashing firmware was with Samsung phones and 'debranding' them.
As I was not trying to root the device or anything - how do I fix this issue? I've searched the forums but I cannot fine a scenario similar to mine therefore I'm a bit confused as to what to do to resolve it.
I've tried to sideload this - oneplus.com/uk/support/softwareupgrade/details?code=PM1574156155944 via recovery but it says installation failed.
Any help appreciated thanks!

Sounds like you're straight out of luck to recover any data if your device is completely stock, as to unlock your bootloader to access encrypted data would mean a factory reset. You could try try one of the unbrick tools using the guide here. You will lose your data.

I tried the unbrick tool here - forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
... and it doesn't work. The phone now boots to a blank screen with a constant white LED.
Could this be a hardware issue?
I'm not too concerned about losing my data - already gave up on trying to keep my data when the problem first occurred!

After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...

oneplus5t_ said:
After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...
Click to expand...
Click to collapse
Problem fixed?

unfortunately not. Any ideas on next steps?

That's an odd issue for sure. My only idea would be installing TWRP and maybe formatting from there and using fix permissions etc. to see if it has any effect.

I've done some googling to try and understand "TWRP" but I'm not sure I fully understand. Are there any forum posts I can refer to?
- phone has been flashed several times
- before this whole saga dev mode was enabled, but only to reduce animation scale - USB debugging was never enabled
- the phone has always been stock / sim free - never rooted
Thanks

Can you get into recovery? If yes then try connecting to a pc whilst in recovery as it should let you open your phones internal storage on PC but im not too sure if stock recovery allows it, (TWRP) does. Then copy whatever files you need. Let us know if you can get into fastboot mode aswell

It sounds similar to an issue I have just experienced with a friends 5T. In my case it's a hardware issue (seems like Wi-Fi has died). Just for kicks try to flash the Android 7 firmware. For some reason it allowed me to boot the phone fine and use it, albeit without any Wi-Fi. I sideloaded OOS 4.7.6 and that seems to be the last version 7. You could also use the older unbrick software. Academic I fear as I think you have a hardware issue.