Related
Okay, so recently installed the 4.4.2 OTA on my completely stock nexus 7 (unrooted, bootloader still locked).
Tried connecting to my PC via bluetooth (for headset) and noticed that it wasnt working (was working on 4.4), so decided that maybe a reboot would fix the problem.
And now the tablet doesn't boot. Completely unresponsive, no charging icon etc. either. Tried holding down the power button, power and +/- vol for 20+ secs to no avail. Connecting the tablet to my laptop makes windows update search for the QHSUSB_DLOAD driver. From what I've read this is supposed to be some sort of hardbrick?
I left the tablet completely stock and haven't done any tinkering except use the Wugfresh toolkit to do a backup (which only needed USB debugging on). Also the battery was definitely 60%+ before I attempted rebooting.
Help please? This is completely out of the blue seeing as I never even unlocked the bootloader or anything?
Please help!
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
mdamaged said:
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
crash91 said:
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
Click to expand...
Click to collapse
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
mdamaged said:
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
Click to expand...
Click to collapse
I'll update this tomorrow morning, thanks for your help!
crash91 said:
I'll update this tomorrow morning, thanks for your help!
Click to expand...
Click to collapse
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
mdamaged said:
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
Click to expand...
Click to collapse
Alright so still no dice. Warranty is out of the question because I bought an imported version off eBay before it was officially available on Google play here in India.
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
crash91 said:
(...)
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
Click to expand...
Click to collapse
Yeah, I don't know much about that either, sorry, I'm not going to be much help there.
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
crash91 said:
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
Click to expand...
Click to collapse
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
malikmoreni said:
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
Click to expand...
Click to collapse
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
crash91 said:
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
Click to expand...
Click to collapse
Try using the Qualcomm product support Tool google "QPST" for download links
malikmoreni said:
Try using the Qualcomm product support Tool google "QPST" for download links
Click to expand...
Click to collapse
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
crash91 said:
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
Click to expand...
Click to collapse
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
Click to expand...
Click to collapse
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
Click to expand...
Click to collapse
That's exactly the thing, it doesnt get into fastboot mode or anything, I assume you need a working bootloader to be able to boot fastboot? If it was in fastboot I would have attempted this already.
Anyway the seller says that the item is covered under a 1 year international warranty, thats my only chance now I guess....
The thing that concerns me is that I was completely stock, locked bootloader and unrooted. Only installed the official OTA updates (no sideloading either).
For those who are interested - I finally had time to drop by the service centre. They replaced the battery and motherboard (it was under warranty). I was expecting them to do some magic with QPST or something though.
The same has just happened to me, but I'm out of luck, the warranty has expired.
Did anyone have managed to fix it with the QPST drivers?
thanks.
Fyi, http://www.androidpolice.com/2015/0...rate-not-likely-a-result-of-firmware-updates/
Dear Friends,
I bricked my Galaxy W. Here is the bricking procedure.
- I reset my phone with original loader and converted into original factory state.
- Than with this clean phone, I rooted it by help of this guide
It was successful. Thanks for that guide.
- Than from google play, I loaded terminal emulator and tried to load recovery-clockwork-6.0.4.5-ancora
- Rebooted my phone and surprise: My phone is dead.
What I get:
- My phone is completely unbootable.
- No key combination is working
- Completely blank screen without any indication.
- But my PC recognizes my phone as QHSUSB_DLOAD
It seems that Qualcomm High Speed USB driver fits this thing and shows COM5.
- But ODIN does not see anything.
What I need:
- HELP!
Thanks
nemli said:
Dear Friends,
I bricked my Galaxy W. Here is the bricking procedure.
- I reset my phone with original loader and converted into original factory state.
- Than with this clean phone, I rooted it by help of this guide
It was successful. Thanks for that guide.
- Than from google play, I loaded terminal emulator and tried to load recovery-clockwork-6.0.4.5-ancora
- Rebooted my phone and surprise: My phone is dead.
What I get:
- My phone is completely unbootable.
- No key combination is working
- Completely blank screen without any indication.
- But my PC recognizes my phone as QHSUSB_DLOAD
It seems that Qualcomm High Speed USB driver fits this thing and shows COM5.
- But ODIN does not see anything.
What I need:
- HELP!
Thanks
Click to expand...
Click to collapse
Are you sure that you are not able to go download mode by key combination.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
sujithar37 said:
Are you sure that you are not able to go download mode by key combination.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
Click to expand...
Click to collapse
I can not see anything in my phone screen, therefore I can't be sure. But since I can not see any action in PC too I may say; I'm not able to go to download mode.
(I'm not expert on this subject, I always have doubt what I talked about, sorry for that)
However as I say in my first message Qualcomm High Speed driver is always in charge as the phone plugged.
nemli said:
I can not see anything in my phone screen, therefore I can't be sure. But since I can not see any action in PC too I may say; I'm not able to go to download mode.
(I'm not expert on this subject, I always have doubt what I talked about, sorry for that)
However as I say in my first message Qualcomm High Speed driver is always in charge as the phone plugged.
Click to expand...
Click to collapse
Please refer below the link, may be that would help you
http://forum.xda-developers.com/showthread.php?t=1853385
http://forum.xda-developers.com/showthread.php?t=1551016
The only way you can get back from this situation that is you have to enter download mode and flash stock firmware. Your issue will be resolved after that. Make sure you installed Samsung USB drivers into your pc. If this doesn't help then you may contact service center.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
sujithar37 said:
Please refer below the link, may be that would help you
http://forum.xda-developers.com/showthread.php?t=1853385
http://forum.xda-developers.com/showthread.php?t=1551016
The only way you can get back from this situation that is you have to enter download mode and flash stock firmware. Your issue will be resolved after that. Make sure you installed Samsung USB drivers into your pc. If this doesn't help then you may contact service center.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
Click to expand...
Click to collapse
Thanks for your valuable responses. I will try what is recommended in those two links, and of course will give the feedback to here to help the (potential) brickers.
full brick
Hello to all,
I have tried to enter with some different key combination, not worked.
I have tried USB-JIG, not worked.
Does anybody have an idea to go with QHSUSB drivers?
Because only with this, my computer recognizes my bricked phone.
Thanks
nemli said:
Hello to all,
I have tried to enter with some different key combination, not worked.
I have tried USB-JIG, not worked.
Does anybody have an idea to go with QHSUSB drivers?
Because only with this, my computer recognizes my bricked phone.
Thanks
Click to expand...
Click to collapse
same problem as me
usb does not recognize my phone
if u find a solution contact me please
Solved by JTAG
Dear friends,
I have tried all the procedures without touching phone PCB. Non of them worked.
I have decided to apply JTAG procedure. Actually this procedure is a little bit complicated for me. I have found a guy making this. And in a very short time, my phone returned back to life.
Now it is working with a Cyanogenmod release (based on Android 4.2.2.)
I have some issues but anyway, my phone is working now with better system performance.
JTAG saved my phone.
nemli said:
Dear friends,
I have tried all the procedures without touching phone PCB. Non of them worked.
I have decided to apply JTAG procedure. Actually this procedure is a little bit complicated for me. I have found a guy making this. And in a very short time, my phone returned back to life.
Now it is working with a Cyanogenmod release (based on Android 4.2.2.)
I have some issues but anyway, my phone is working now with better system performance.
JTAG saved my phone.
Click to expand...
Click to collapse
How much did he charge you for the JTAG? I am looking to JTAG few phones
MayB4ck said:
How much did he charge you for the JTAG? I am looking to JTAG few phones
Click to expand...
Click to collapse
Nearly 20€ per JTAG.
If someone need QHSUSB_DLOAD solution...
Maybe I can help him...
You need Qualcomm Drivers... forgotten which one exactly I have used...
QPST Version Build 411
http://forum.xda-developers.com/showpost.php?p=50204328&postcount=9
Procedure looks similar to this:
forum.xda-developers.com/attachment.php?attachmentid=2754655&d=1400627472
In this Thread I have tried many things...
http://forum.xda-developers.com/showpost.php?p=52808706&postcount=282
I could prepare files for testing for I8150...
Not tested by me nor confirmed with I8150... as only S8600 for me available...
If someony want test... PM me.
Next few hours or days I could upload files for QPST...
Code:
MBR from I8150
DBL from I8150
OSBL from I8150
Need testers and feedback please.
Best Regards
Will check my HD for Qualcomm drivers...
Maybe upload later...
Here are test files... because untested...
Risk to reach other bad status... So you could need JTAG...
Short description...
DBL and OSBL are taken from JTAG dump...
It seems chinese Version could be different...
But MBR... first 512 Bytes are 1:1 same in all I8150 JTAG dumps I have on my HD...
partition.mbn is MBR from I8150... 512 Byte
DBL and OSBL have size from partition... extracted from JTAG dump...
DBL is in partition 2
OSBL in partition 3...
Settings for QPST are hopefully visible in Screenshot...
It is mandatory to use QPST Build 411... older Versions not accept MBR as partition.mbn without header...
Header in MBR not deadly but could be bring other trouble...
For testing now only correct drivers "missing"...
I have so many stuff downloaded...
Will try to find correct one.
Again, I have only S8600 for test...
Maybe with I8150 not possible...
But before you buy JTAG you can try.
Good luck.
Best Regards
Edit 1.
Qualcomm driver to find should be not impossible... use magic search word: QHSUSB_DLOAD... for instance here:
http://forum.xda-developers.com/showpost.php?p=40072841&postcount=1
or try this one:
http://forum.xda-developers.com/showpost.php?p=40195799&postcount=7
And here again Link for working confirmed QPST Version Build 411... tested successfully by me with S8600:
http://forum.xda-developers.com/showpost.php?p=50204328&postcount=9
I rooted my friends htc desire 816g dual sim and got him cwm.
i flashed it with a programm on the pc (can't quite remember the name) after that it said ''boot in recovery mode?''
i pressed yes and it went into a bootloop,i was like ok fixable just go into fastboot and flash new rom right?
no it cannot go into bootloop or recovery and when it is connected to pc during this whole bootloop it shows me the cell phone with some drivers i installed with a yellow exclamation mark under it,also it doesn't stay connected for more than 3-5 seconds
thongdaddy said:
I rooted my friends htc desire 816g dual sim and got him cwm.
i flashed it with a programm on the pc (can't quite remember the name) after that it said ''boot in recovery mode?''
i pressed yes and it went into a bootloop,i was like ok fixable just go into fastboot and flash new rom right?
no it cannot go into bootloop or recovery and when it is connected to pc during this whole bootloop it shows me the cell phone with some drivers i installed with a yellow exclamation mark under it,also it doesn't stay connected for more than 3-5 seconds
Click to expand...
Click to collapse
Yeah the g is the Mediatek processor and needs to be flashed with flashtools and the phone off I believe. Not many custom roms for it either. So you think you flashed the wrong rom and did you use flashtools ? There's also a quad core version and octa core version that can't use each other's custom roms I believe. One is MT682 and the other is MT692 for octa core I believe.
thoctor said:
Yeah the g is the Mediatek processor and needs to be flashed with flashtools and the phone off I believe. Not many custom roms for it either. So you think you flashed the wrong rom and did you use flashtools ? There's also a quad core version and octa core version that can't use each other's custom roms I believe. One is MT682 and the other is MT692 for octa core I believe.
Click to expand...
Click to collapse
I didn't flash a rom I flashed cwm and It wasn't off indeed but I need help not to find the cause because I cannot get into any menus or get my pc to recognise it due to the minimum time it stays connected
thongdaddy said:
I didn't flash a rom I flashed cwm and It wasn't off indeed but I need help not to find the cause because I cannot get into any menus or get my pc to recognise it due to the minimum time it stays connected
Click to expand...
Click to collapse
Oh , yeah. My bad. I was tired last night and helping a few different people here and in other sites so the recovery flash slipped by me. Your going to have to get the phone powered down (either by you or by it draining down.)and use flashtools again I believe. Assuming that's what you used initially. XDA member Nukaru has helped people with Mediatek chipsets more than I have ( I have the a5_chl snapdragon) and I would recommend getting her help. I've never used flashtools with the Mediatek devices just ADB/fastboot with Qualcomm.
thoctor said:
Oh , yeah. My bad. I was tired last night and helping a few different people here and in other sites so the recovery flash slipped by me. Your going to have to get the phone powered down (either by you or by it draining down.)and use flashtools again I believe. Assuming that's what you used initially. XDA member Nukaru has helped people with Mediatek chipsets more than I have ( I have the a5_chl snapdragon) and I would recommend getting her help. I've never used flashtools with the Mediatek devices just ADB/fastboot with Qualcomm.
Click to expand...
Click to collapse
My computer cannot recognise it though because once I connect in it disconnects within seconds if I could do that I would have tried and the only reason I have hopes is because it turns on but not in android or any bootloader also my phone is discoverable by my pc only when it is in the state of turning on as soon as there is light on the screen it disconnects
thongdaddy said:
My computer cannot recognise it though because once I connect in it disconnects within seconds if I could do that I would have tried and the only reason I have hopes is because it turns on but not in android or any bootloader also my phone is discoverable by my pc only when it is in the state of turning on as soon as there is light on the screen it disconnects
Click to expand...
Click to collapse
I get all that . The phone won't enter recovery or bootloader or OS and keeps rebooting. I believe it's going to have to completely power down either by you or the phone itself then use flashtools. I provided a link to a flashtools forum for the HTC Mediatek devices. Yours is included. Also contact Nukaru as she has direct experience with the Mediatek chipset. The phone is going to have to run down basically so you don't get any reboots but like I said the Mediatek isn't my area of expertise. Follow my advice and you'll get it figured out. Good luck.
http://forum.xda-developers.com/android/general/htc-mtk-cpu-flash-files-flashtool-t3114271
thoctor said:
I get all that . The phone won't enter recovery or bootloader or OS and keeps rebooting. I believe it's going to have to completely power down either by you or the phone itself then use flashtools. I provided a link to a flashtools forum for the HTC Mediatek devices. Yours is included. Also contact Nukaru as she has direct experience with the Mediatek chipset. The phone is going to have to run down basically so you don't get any reboots but like I said the Mediatek isn't my area of expertise. Follow my advice and you'll get it figured out. Good luck.
http://forum.xda-developers.com/android/general/htc-mtk-cpu-flash-files-flashtool-t3114271
Click to expand...
Click to collapse
Sorry for replying again but just to make it clear I make the phone battery die so it doesn't reboot and I use the flash tools to flash a stock rom?
thongdaddy said:
Sorry for replying again but just to make it clear I make the phone battery die so it doesn't reboot and I use the flash tools to flash a stock rom?
Click to expand...
Click to collapse
Don't be sorry I'm happy to help. That's my understanding but bear in mind my knowledge with the Mediatek is really limited. I know you need flashtools and I'm pretty sure the device needs to be powered off. After that I'm kind of out of my area of expertise. Been told by Nukaru that the Mediatek is actually easier to flash/work with so that's good. Send her a PM and when she's not busy I'm sure she will try to help you here.
thoctor said:
Don't be sorry I'm happy to help. That's my understanding but bear in mind my knowledge with the Mediatek is really limited. I know you need flashtools and I'm pretty sure the device needs to be powered off. After that I'm kind of out of my area of expertise. Been told by Nukaru that the Mediatek is actually easier to flash/work with so that's good. Send her a PM and when she's not busy I'm sure she will try to help you here.
Click to expand...
Click to collapse
OK thank you for all your help
thongdaddy said:
Sorry for replying again but just to make it clear I make the phone battery die so it doesn't reboot and I use the flash tools to flash a stock rom?
Click to expand...
Click to collapse
Just popped in, I think I can help you.
SP Flashtool can detect the device even if it is on bootloop. On SP Flashtool just tick all items except preloader then click on download and connect the phone to the PC. If it still does not get recognized try holding the power button while you are connecting it to the PC to try and force it into the switched off state
The best way to flash RUU on a mediatek device is ALWAYS to remove the battery. Not removing the battery can brick your device!
To help I'll need more information about your device.
1. What RUU did you flash? European or Indian?
2. When and where was this phone bought, which region?
nukaru said:
The best way to flash RUU on a mediatek device is ALWAYS to remove the battery. Not removing the battery can brick your device!
To help I'll need more information about your device.
1. What RUU did you flash? European or Indian?
2. When and where was this phone bought, which region?
Click to expand...
Click to collapse
I flashed a clockwork mod it was European if that is ruu but I didn't flash a rom
the phone was bought about 1 year ago in Greece
Gibz97 said:
Just popped in, I think I can help you.
SP Flashtool can detect the device even if it is on bootloop. On SP Flashtool just tick all items except preloader then click on download and connect the phone to the PC. If it still does not get recognized try holding the power button while you are connecting it to the PC to try and force it into the switched off state
Click to expand...
Click to collapse
OK I will try that thanks
This (D816h) is the rom you'll need. Instructions are in the file description. If you're having trouble signing in, please contact me and I'll upload the file once I'm done with work.
And this is how to remove the battery.
nukaru said:
This (D816h) is the rom you'll need. Instructions are in the file description. If you're having trouble signing in, please contact me and I'll upload the file once I'm done with work.
And this is how to remove the battery.
Click to expand...
Click to collapse
it is stuck now because as soon as it connects it stays connected and it disconnects after a few seconds i also got an error about the usb port but i uninstalled the i guess false drivers i had installed by myself any other ideas?
Have you tried a different driver for your USB Port? Or connecting the device to another USB Port?
Flashtools won't disconnect, if the battery is removed, that's why it's always the safest bet to remove the battery.
nukaru said:
Have you tried a different driver for your USB Port? Or connecting the device to another USB Port?
Flashtools won't disconnect, if the battery is removed, that's why it's always the safest bet to remove the battery.
Click to expand...
Click to collapse
It still doesn't flash it it stays there at 0b/s maybe different settings?the options not quite like you told me it is a different version I guess
thongdaddy said:
It still doesn't flash it it stays there at 0b/s maybe different settings?the options not quite like you told me it is a different version I guess
Click to expand...
Click to collapse
What is your device model?
It is usually shown at the back bottom of the phone. It is usually something like 0PGZ100, 0PJ120... etc
thongdaddy said:
It still doesn't flash it it stays there at 0b/s maybe different settings?the options not quite like you told me it is a different version I guess
Click to expand...
Click to collapse
What error message do you get? Is there an error message?
Some versions of flashtool are problematic with Desire 816, which version did you install?
nukaru said:
What error message do you get? Is there an error message?
Some versions of flashtool are problematic with Desire 816, which version did you install?
Click to expand...
Click to collapse
It is 5. Something should I search some else version?
Hello guys,
After an update to android 7.0 my cell phone started to show difficulties to load. When I connect it on it gives the following message: Caution: High temperature of the device.
This happened after I updated the firmware to the latest version. I wonder if it is to restore the system and go back to version 6.0 of android?
Thank you all,
Best regards
Lando
I have a feeling you'd need to unlock the bootloader. Even so it may not allow you to install MMon it...
Usually the newer firmware replaces the bootloader that rejects older versions of the OS to be flashed.
Help
ultramag69 said:
I have a feeling you'd need to unlock the bootloader. Even so it may not allow you to install MMon it...
Usually the newer firmware replaces the bootloader that rejects older versions of the OS to be flashed.
Click to expand...
Click to collapse
Yes, actually I already unlocked but it did not work. When I try to flash the ROM it says that the version is impractical with the CPU. And nothing truth is not because I've tried more than 5 old roms.
Please if anyone knows how I do this downgrade help me, because I have to have to try several times to load the phone with it turned off.
Many thanks to any help!
landognr said:
Yes, actually I already unlocked but it did not work. When I try to flash the ROM it says that the version is impractical with the CPU. And nothing truth is not because I've tried more than 5 old roms.
Please if anyone knows how I do this downgrade help me, because I have to have to try several times to load the phone with it turned off.
Many thanks to any help!
Click to expand...
Click to collapse
Boot latest twrp
wipe everything on phone in twrp (tick all boxes)
Flash the correct (2.4ghz or 2.15ghz) android 6.0 rom from the asus website. You will need to transfer the zip file to your phone from computer while in recovery. Sometimes you have to reboot twrp after wiping to see the storage on your computer.
Be careful as wiping you phone will remove the os and will result in soft brick if u don't flash the android 6.0 rom.
I have reverted to android 6.0 twice on the sd821 variant but still only do this if you are confident.
I am not responsible if you brick your phone
Brick
Huffy1 said:
Boot latest twrp
wipe everything on phone in twrp (tick all boxes)
Flash the correct (2.4ghz or 2.15ghz) android 6.0 rom from the asus website. You will need to transfer the zip file to your phone from computer while in recovery. Sometimes you have to reboot twrp after wiping to see the storage on your computer.
Be careful as wiping you phone will remove the os and will result in soft brick if u don't flash the android 6.0 rom.
I have reverted to android 6.0 twice on the sd821 variant but still only do this if you are confident.
I am not responsible if you brick your phone
Click to expand...
Click to collapse
Hello friend,
Unfortunately at the time of doing the procedure by an oversight on my part I forgot to do the full wipe. I circled the correct ROM for my phone, but did not do the wipe.
The phone rebooted, hung up and did not call anymore. I can not believe it looks like it gave soft brick due to this my carelessness.
It does not go into fasboot or recovery mode. It gets totally off and when I connect to the pc it recognizes as Qualcomm hs-usb qdloader 9008.
I'm desperate, have I lost my phone? Is there any way to fix this friend? Please ask if anyone knows any procedure to correct it.
Thank you from the heart.
=(
landognr said:
Hello friend,
Unfortunately at the time of doing the procedure by an oversight on my part I forgot to do the full wipe. I circled the correct ROM for my phone, but did not do the wipe.
The phone rebooted, hung up and did not call anymore. I can not believe it looks like it gave soft brick due to this my carelessness.
It does not go into fasboot or recovery mode. It gets totally off and when I connect to the pc it recognizes as Qualcomm hs-usb qdloader 9008.
I'm desperate, have I lost my phone? Is there any way to fix this friend? Please ask if anyone knows any procedure to correct it.
Thank you from the heart.
=(
Click to expand...
Click to collapse
Hi sorry I'm having trouble understanding what your stuck at. You saying the phone doesn't boot at all?
Huffy1 said:
Hi sorry I'm having trouble understanding what your stuck at. You saying the phone doesn't boot at all?
Click to expand...
Click to collapse
Exactly! My phone doesn't boot, just recognizes how QUalcomm HS-USB QDLoader 9008 in my PC. He's dont boot or fastboot mode and dont recovery. Could you help me please?
landognr said:
Exactly! My phone doesn't boot, just recognizes how QUalcomm HS-USB QDLoader 9008 in my PC. He's dont boot or fastboot mode and dont recovery. Could you help me please?
Click to expand...
Click to collapse
Ok restoring your phone with the Qualcomm loader is a very lengthy and complicated process. When the phone is completely off. Hold down the volume up button and power button for a while until the Asus logo appears on the screen. Then open cmd in your android-sdk folder and type "fastboot devices." Let me know if it detects the phone
Huffy1 said:
Ok restoring your phone with the Qualcomm loader is a very lengthy and complicated process. When the phone is completely off. Hold down the volume up button and power button for a while until the Asus logo appears on the screen. Then open cmd in your android-sdk folder and type "fastboot devices." Let me know if it detects the phone
Click to expand...
Click to collapse
Hello friend,
Unfortunately this procedure dont work, my device dont turn on. With power + vol up or power + vol down or both at the same time dont work, because he gives no sign of life. All I can do is connect the PC and recognize how Qualcomm hs-usb qdloader 9008 in device manager. You know others procedure to do?? Thank you
landognr said:
Hello friend,
Unfortunately this procedure dont work, my device dont turn on. With power + vol up or power + vol down or both at the same time dont work, because he gives no sign of life. All I can do is connect the PC and recognize how Qualcomm hs-usb qdloader 9008 in device manager. You know others procedure to do?? Thank you
Click to expand...
Click to collapse
What phone version do u have? S821 or s820?
Huffy1 said:
What phone version do u have? S821 or s820?
Click to expand...
Click to collapse
I think s820, my phone is CPU 2.15GHz version. Thank your repply
landognr said:
I think s820, my phone is CPU 2.15GHz version. Thank your repply
Click to expand...
Click to collapse
Ok well unfortunately my phone is s821. You need someone here that has a s820 to factory reset then backup their phone. Then you can use the Qualcomm loader to restore your phone.
Huffy1 said:
Ok well unfortunately my phone is s821. You need someone here that has a s820 to factory reset then backup their phone. Then you can use the Qualcomm loader to restore your phone.
Click to expand...
Click to collapse
Ok man, but where can i find files to do a factory reset?
im searching in.web but i cant find. Please bro help me, i dont know what do. You are my last hope to solve this, thanks
landognr said:
Ok man, but where can i find files to do a factory reset?
im searching in.web but i cant find. Please bro help me, i dont know what do. You are my last hope to solve this, thanks
Click to expand...
Click to collapse
Like I said as this is such an uncommon phone it probably doesn't exist. You need someone willing to upload a backup of their phone 2.15ghz for u to restore.
Huffy1 said:
Like I said as this is such an uncommon phone it probably doesn't exist. You need someone willing to upload a backup of their phone 2.15ghz for u to restore.
Click to expand...
Click to collapse
Ok Man, but can you send me the step by step of how you managed to solve your problem, regardless of whether rom is different? I know you have nothing to do with it, but I have spent all my savings on this device and need to work out a way to recover it.
Thanks Huffy :good:
landognr said:
Hello guys,
After an update to android 7.0 my cell phone started to show difficulties to load. When I connect it on it gives the following message: Caution: High temperature of the device.
This happened after I updated the firmware to the latest version. I wonder if it is to restore the system and go back to version 6.0 of android?
Thank you all,
Best regards
Lando
Click to expand...
Click to collapse
Did you success?Have you unlock the bootloader of your phone?unlock is necessary!(even though somebody say it work on locked phone)
Here come the tip from Taiwan forum~
link
samson1357924 said:
Did you success?Have you unlock the bootloader of your phone?unlock is necessary!(even though somebody say it work on locked phone)
Here come the tip from Taiwan forum~
link
Click to expand...
Click to collapse
Yes, The bootloader was already unlocked before the problem happened on my phone. I dont think you really understood my problem. What I need is to recover the bootloader from my device.
You said: wonder if it is to restore the system and go back to version 6.0 of android?
So I give you the way to downgrade~It’s not difficult.
I don't know that you had brick your phone......
samson1357924 said:
You said: wonder if it is to restore the system and go back to version 6.0 of android?
So I give you the way to downgrade~It’s not difficult.
I don't know that you had brick your phone......
Click to expand...
Click to collapse
Will QuickCharge 3.0 work again if you return to Android 6 (given that it was removed in Android 7)?
AWT86 said:
Will QuickCharge 3.0 work again if you return to Android 6 (given that it was removed in Android 7)?
Click to expand...
Click to collapse
It was never removed it works fine on Android 7.0. Sometimes you have to factory reset your phone to get it working after an upgrade.
You do have to use the supplied ASUS charger though which is really annoying to get qc3.0 speeds. Other qc certified quick charge 3.0 will only charge at normal speeds. Something Asus have blocked themselves.
Hi Mates,
I have 1789-06 variant with unlocked bootloader.
I installed the pie version via flashall, all were OK.
but upon rebooting the splash screen prompted for "verity mode is set to disabled".
no matter what I tried, all failed - the phone reboots to the fastboot screen.
then I was wondering BP Tools mode where on the screen it was showing "disabled".
somehow I enabled and attempted to reboot - the screen went total black!
is there anything that can revive the phone?
thanks in advance for the support.
cheers.
Connect to your pc and simply try holding the pwr btn for a minute to see if it will boot, if not, try holding vol dwn + pwr for a minute to see if that will boot it. Listen and look to see if your pc is detecting the phone at all while you try. Also you can check your device manager to see if it is showing there.
41rw4lk said:
Connect to your pc and simply try holding the pwr btn for a minute to see if it will boot, if not, try holding vol dwn + pwr for a minute to see if that will boot it. Listen and look to see if your pc is detecting the phone at all while you try. Also you can check your device manager to see if it is showing there.
Click to expand...
Click to collapse
thanks bro for the prompt response.
however, no connection, no booting, no sound of device connection to the PC.
what can be the next mate?
beefytr said:
thanks bro for the prompt response.
however, no connection, no booting, no sound of device connection to the PC.
what can be the next mate?
Click to expand...
Click to collapse
Unfortunately, the black screen has been a bit of a fiasco with pie updates, especially for those who have tried pie on variants not intended for the firmware. No solution has been found yet, but I haven't heard of it happening by enabling bp tools. Connect to a 2.0 port and double check your device manager. Look for unknown devices, hs usb 9008, and try various button combos while trying to power and watch your device manager for new devices. In short you might be SOL, but if you're lucky and your pc recognizes the phone you might be able to blankflash.
41rw4lk said:
Unfortunately, the black screen has been a bit of a fiasco with pie updates, especially for those who have tried pie on variants not intended for the firmware. No solution has been found yet, but I haven't heard of it happening by enabling bp tools. Connect to a 2.0 port and double check your device manager. Look for unknown devices, hs usb 9008, and try various button combos while trying to power and watch your device manager for new devices. In short you might be SOL, but if you're lucky and your pc recognizes the phone you might be able to blankflash.
Click to expand...
Click to collapse
ok thanks.
actually, my phone was set to get the OTA.
the OTA s'mpy did not install without any reason saying "something went wrong".
anyways, the strange thing is that all happened after the BP tools thing.
I will see what I can do with USB 2.0.
this whole thing does not seem to be a brick, right?
beefytr said:
ok thanks.
actually, my phone was set to get the OTA.
the OTA s'mpy did not install without any reason saying "something went wrong".
anyways, the strange thing is that all happened after the BP tools thing.
I will see what I can do with USB 2.0.
this whole thing does not seem to be a brick, right?
Click to expand...
Click to collapse
Actually it kind of does. On oreo, it seemed the worst that would happen is you would soft birck. Basically a black screen but the phone would connect to the pc as a 9008 device and you could blankflash your way back to good. Since pie, something is happening and the exact reason hasn't been pinpointed. Usually it's those who have tried to flash pie for a variant it wasn't intended for. Some have lost their baseband and are still waiting for a solution to that, and a couple have full on bricked. At least there hasn't been any sign of life nor a way to do anything about it. Granted the bp tools thing is weird, but maybe a dav will pick up on this and maybe understand just what is happening and what is causing it.
41rw4lk said:
Actually it kind of does. On oreo, it seemed the worst that would happen is you would soft birck. Basically a black screen but the phone would connect to the pc as a 9008 device and you could blankflash your way back to good. Since pie, something is happening and the exact reason hasn't been pinpointed. Usually it's those who have tried to flash pie for a variant it wasn't intended for. Some have lost their baseband and are still waiting for a solution to that, and a couple have full on bricked. At least there hasn't been any sign of life nor a way to do anything about it. Granted the bp tools thing is weird, but maybe a dav will pick up on this and maybe understand just what is happening and what is causing it.
Click to expand...
Click to collapse
we'll wait and see!
thanks.
by the way, how do you "blankflash"? just in case...
beefytr said:
we'll wait and see!
thanks.
by the way, how do you "blankflash"? just in case...
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
All the best mate.
Thanks.
41rw4lk said:
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
what if what you advise does not work at all?
then it is a dead one?
beefytr said:
what if what you advise does not work at all?
then it is a dead one?
Click to expand...
Click to collapse
Yeah, the whole blankflash hinges on the fact that it is already in edl mode, but considering your circumstance, it is most likely dead like the few others. As of now there is no known way to revive them besides a jtag (untested and not confirmed) and you would need to tear your phone down to even try that, which isn't a viable option for most. Sorry I can't offer anything more.
41rw4lk said:
Yeah, the whole blankflash hinges on the fact that it is already in edl mode, but considering your circumstance, it is most likely dead like the few others. As of now there is no known way to revive them besides a jtag (untested and not confirmed) and you would need to tear your phone down to even try that, which isn't a viable option for most. Sorry I can't offer anything more.
Click to expand...
Click to collapse
thanks bro.
I will not bother for JTAG as it is - as you have rightfully said - untested.
my phone is still under warranty and I will try a replacement or a refund then.
cheers.
What did you do to boot your device.. Even mine is bootlooped.
---------- Post added at 10:58 AM ---------- Previous post was at 10:57 AM ----------
What did you do to boot your device.. Even mine is bootlooped.
... Is it bootlooping or does it just not power on at all?