Hi,
I was fixing a hard brick using this thread for MSM tool.
https://forum.xda-developers.com/oneplus-7-pro/help/help-device-corrupt-trusted-boot-t3946658
I couldn't see the Qualcomm QD loader appear on my device manager but went ahead and started the tool. It looked like nothing was happening so I unplugged my phone and suddenly reaslised there was a progress bar on the MSM tool.
Now when I try and switch on my phone or hold down the vulume up and down buttons I get this message flashing up after a brief boot screen
<!>
Upgrade download failed!!!
Please check your download flow is right.
accompanied with a message on my PC that the usb device isn't functioning.
Update: I just tried it again and Qualcomm QD appeared on device manager briefly before the problem returned.
Advice?!?!?!?!?!?!?!?!?!?!?
OK issue resolved. Think my USB port is on the blink. Still, haven't seen that error message mentioned anywhere so quite interesting...
Thanks for sharing. Did you get the phone back to a working state?
I'm having this issue as well, did you manage to get this fixed?
same problem here
any solutions?
For any other forlorn souls who come across this thread, I was experiencing essentially the same bug I think, I'm not really sure what happened (I got up to get a drink), but when I came back to my computer my OnePlus 7 Pro was stuck in a terrifying boot loop while plugged in where all I would see, all in yellow was:
<!>
Upgrade download failed!!!
Please check your download flow is right.
That would be visible for a second or so and then the phone would power cycle and display the OnePlus splash screen for less than a second then back to the yellow error message. I could not boot into recovery, fastboot, or standard.
SOLUTION:
Plugged phone into PC via USB, held down the Volume Up and Volume Down buttons and waited for it to power cycle itself. Screen stayed off, but it showed up in Device Manager under ports, and I was able to start the MsmDownloadTool and flash a new system image.
So its odd but I get this message briefly as the phone boots up, but the phone works otherwise. Do you know how to do get rid of it because running the MSM tool has not fixed the message.
same here. anyone?
aPuddle said:
For any other forlorn souls who come across this thread, I was experiencing essentially the same bug I think, I'm not really sure what happened (I got up to get a drink), but when I came back to my computer my OnePlus 7 Pro was stuck in a terrifying boot loop while plugged in where all I would see, all in yellow was:
<!>
Upgrade download failed!!!
Please check your download flow is right.
That would be visible for a second or so and then the phone would power cycle and display the OnePlus splash screen for less than a second then back to the yellow error message. I could not boot into recovery, fastboot, or standard.
SOLUTION:
Plugged phone into PC via USB, held down the Volume Up and Volume Down buttons and waited for it to power cycle itself. Screen stayed off, but it showed up in Device Manager under ports, and I was able to start the MsmDownloadTool and flash a new system image.
Click to expand...
Click to collapse
Thank you so much that helped me a lot
I almost went to buy another phone
aPuddle said:
For any other forlorn souls who come across this thread, I was experiencing essentially the same bug I think, I'm not really sure what happened (I got up to get a drink), but when I came back to my computer my OnePlus 7 Pro was stuck in a terrifying boot loop while plugged in where all I would see, all in yellow was:
<!>
Upgrade download failed!!!
Please check your download flow is right.
That would be visible for a second or so and then the phone would power cycle and display the OnePlus splash screen for less than a second then back to the yellow error message. I could not boot into recovery, fastboot, or standard.
SOLUTION:
Plugged phone into PC via USB, held down the Volume Up and Volume Down buttons and waited for it to power cycle itself. Screen stayed off, but it showed up in Device Manager under ports, and I was able to start the MsmDownloadTool and flash a new system image.
Click to expand...
Click to collapse
You are an Hero you deserve your own heaven you can have my soul thank you so much
aPuddle said:
For any other forlorn souls who come across this thread, I was experiencing essentially the same bug I think, I'm not really sure what happened (I got up to get a drink), but when I came back to my computer my OnePlus 7 Pro was stuck in a terrifying boot loop while plugged in where all I would see, all in yellow was:
<!>
Upgrade download failed!!!
Please check your download flow is right.
That would be visible for a second or so and then the phone would power cycle and display the OnePlus splash screen for less than a second then back to the yellow error message. I could not boot into recovery, fastboot, or standard.
SOLUTION:
Plugged phone into PC via USB, held down the Volume Up and Volume Down buttons and waited for it to power cycle itself. Screen stayed off, but it showed up in Device Manager under ports, and I was able to start the MsmDownloadTool and flash a new system image.
Click to expand...
Click to collapse
You save my phone, thank you so much, this works to me.
Related
I got an HTC One S from a friend who got it from another friend. I don't have any history on the device. He gave it to me to fix because I'm the only Android user he knows and his phone won't start.
If I keep the power button pressed, the capacitive buttons flash exactly 15 times and occasionally the phone vibrates. I don't have a One S so not sure if that indicates that phone was started or shutdown.
Neither fastboot devices not adb devices shows the device. But every once in a while when it vibrates, if the phone is connected to the PC with a USB cable, it beeps - like it's connected. I don't see Android Phone in Device Manager. But I see a MTP USB Device with a yellow exclamation mark. Uninstalling and reinstalling HTC Drivers didn't fix the problem.
I have tried Power+Volume Down key. Shining a torch on it (seemed to work for a few people), keeping it plugged into the mains for 3 days, kept it in the freezer for 2-3 minutes (also seemed to work for one person).
I think when I first got the phone and plugged it into the mains, I saw a red charging light. But I may be mistaken. In any case, there is no light anymore indicating charging. But I don't think that's the problem.
I have no idea whether the device is bricked or not. And if there is any way to fix it. Samsung has Odin which makes any Samsung phone practically unbrickable. I haven't used any HTCs since the G1 so have not been in touch too much with the HTC development. But from reading, it seems that messing around with Romming with S-ON can cause the phone to be bricked. And perhaps that's what my friend or his friend did. Does this sound like that's what could have happened?
Thanks for any pointers.
I dont think the device is bricked. its just a little harder to press the power and volume down when you see the buttons flashing.
just check and do these steps.
connect the mobile to charger and see if the orange light comes and stays on
if the orange light is there, press the power button and keep your finger ready near the volume down button
you should keep the power button pressed and as soon as the orange light disappears you should press the volume down button until you end up in boot loader screen
give this a few tries and see if the device boots up in bootloader
ayyu3m said:
I dont think the device is bricked. its just a little harder to press the power and volume down when you see the buttons flashing.
just check and do these steps.
connect the mobile to charger and see if the orange light comes and stays on
if the orange light is there, press the power button and keep your finger ready near the volume down button
you should keep the power button pressed and as soon as the orange light disappears you should press the volume down button until you end up in boot loader screen
give this a few tries and see if the device boots up in bootloader
Click to expand...
Click to collapse
The problem is that I no longer see any light at all when I connect the phone to a charger. It's probably fully charged. Would that show a green light? If so, that's not visible either. I have a feeling that the bootloader has got wiped out or something.
I read in one post that the phone may be stuck in the QHUSB-DLOAD mode.
So I followed the steps in http://unlimited.io/qhsusbdload.htm. But that didn't help. I don't remember the exact statement since I was running an Ubuntu Live CD. But the gist was that it couldn't connect to the phone so presumably it's not stuck in QHUSB-DLOAD mode. Although the site states that it will NOT fix QHSUSB_DLOAD issues encountered by flashing ROMs - which may well be what may have happened.
I understand that running an RUU for the HTC One S may set it back to factory state. But for that I need fastboot to work.
OK so 15min ago my phone was working fine.
I plugged it into my computer via USB to I could copy some videos and my PC didn't detect it so I rebooted the phone to see if that would help....
From that point on, it doesn't go past the initial "Samsung" screen. Well, it sort of does... regardless of any button combinations I press while booting up it always goes into a bright write and green screen that isn't normal. It is some sort of ghosted or washed out image.
From there the only thing it responds to is a forced reboot and it loops back to this again.
I've tried every button combo available and they don't respond. I cannot get to the download menu or the recovery menu so I can't reload the ROM or the TWRP recovery.
I've never seen anything like this in over 10 years of rooting phones... and the worst part is that I wasn't making any changes, just doing a reboot.
Any ideas of the problem?
Hello there!
I tried to replace the battery of my phone with another one, but the phone doesn't boot up at all.
Shortly after I switched the battery, I managed to boot the phone: the HUAWEI writing showed up and then the phone shut down.
The red led was blinking while charging and other tentatives of boot-up failed with only a vibration shot and nothing more, with the screen still black.
Just out of curiosity, I tried to go to fastboot mode (by holding DOWN volume and plugging the USB cable on pc) and surprisingly enough the "plug in" Windows sound played but the phone remained pitch black.
The curious thing is that if I type
Code:
fastboot devices
It shows a number and the writing "fastboot" so I guess that the phone is recognized by the pc.
Is it bricked or something?
Or maybe the battery was faulty and ruined the motherboard?
Or maybe it is just the screen broken...
I don't really know how to proceed.
Was watching youtube videos last night before my phone died, now I can't get it to start boot into the OS. Not sure if this is relevant but my power button had been a little finnicky- rather maybe not the power button itself because it doesn't feel stuck or anything at all but I noticed that it would take an extra second or two after pressing the power button to get into my lock screen. I never really paid attention because it only happened once in a while and I would just restart my phone and be done with it. However I can't even get into the lock screen or anything now.
After my phone died last night I plugged it in right away and came back a while later to turn it on. I tried turning it on but noticed my phone just kept rebooting. It's still repeatedly rebooting and I can only get in the fastboot menu by holding down both volume buttons when rebooting. I get the options power off- which just reboots it after a while, start - which just reboots the phone, restart boot loader- which literally takes me back to the same menu, recovery mode- just reboots and show barcode which shows the barcode at the bottom of the menu.
I've tried downloading the qualcomm driver and trying to get into EDL mode but don't see it on my pc or msmtool, i'm also not even sure if i'm trying to get into EDL mode correctly. I've tried disable Driver signature Enforcement and then redownloading the qualcomm driver but still no luck. I don't know what else I should try. Someone please help me out, i'm pissed this happened just because my phone died, about to have ptsd whenever my phone is at 5% fml.
Also after seeing the 1+ logo and powered by android on the bottom, sometimes I would see like a line of color, which I would assume is text not being rendered all the way, fade out and then the phone shuts down and reboots itself.
yellownese said:
Was watching youtube videos last night before my phone died, now I can't get it to start boot into the OS. Not sure if this is relevant but my power button had been a little finnicky- rather maybe not the power button itself because it doesn't feel stuck or anything at all but I noticed that it would take an extra second or two after pressing the power button to get into my lock screen. I never really paid attention because it only happened once in a while and I would just restart my phone and be done with it. However I can't even get into the lock screen or anything now.
After my phone died last night I plugged it in right away and came back a while later to turn it on. I tried turning it on but noticed my phone just kept rebooting. It's still repeatedly rebooting and I can only get in the fastboot menu by holding down both volume buttons when rebooting. I get the options power off- which just reboots it after a while, start - which just reboots the phone, restart boot loader- which literally takes me back to the same menu, recovery mode- just reboots and show barcode which shows the barcode at the bottom of the menu.
I've tried downloading the qualcomm driver and trying to get into EDL mode but don't see it on my pc or msmtool, i'm also not even sure if i'm trying to get into EDL mode correctly. I've tried disable Driver signature Enforcement and then redownloading the qualcomm driver but still no luck. I don't know what else I should try. Someone please help me out, i'm pissed this happened just because my phone died, about to have ptsd whenever my phone is at 5% fml.
Also after seeing the 1+ logo and powered by android on the bottom, sometimes I would see like a line of color, which I would assume is text not being rendered all the way, fade out and then the phone shuts down and reboots itself.
Click to expand...
Click to collapse
Which OOS build are you on? And your device is unlocked or not?
Getting into EDL mode is tricky. Power off device completely. With the device powered off, hold down volume up and volume up at the same time, keep them pressed all the time, and during that time plug into PC (phone all the time powered off). Still hold both of the buttons. By the time you plug into PC, you should be in EDL mode, BUT it only lasts about 10 seconds. I mean you have to click start in this 10 seconds time bracket, other way phone exits EDL itself. After you click start, you can release button, obviously
Greetings, I'll try to keep it short. My device is a Zenfone 7 Pro (ZS671KS)
I was using the phone normally and then for some reason it got stuck and I had to perform a "holding the power button" force shutdown to get out of it. The same thing has happened a few times before and it always boots back to normal. This time however, happened after I just downloaded and installed the latest firmware update when the phone was in its "waiting for reboot" state.
It has been bricked ever since and holding the power button will just send it into a boot loop (a brief vibration every once in a while). Whatever I do nothing will show, no logo no LED indicator light or anything like that. All black. Holding volume up or down + power also don't do anything. Vibration is the only response I am getting.
The phone itself was not modified in any way, it was never rooted, didn't have a custom firmware and stuff. Is there anything I can try to save it and all the data inside (data being my priority) before I give up and admit defeat?
Don't think I've see anything quite like it before, so any idea is appreciated.