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/
Hey guys, I accidentally deleted bootloader of my Lenovo p2....doesn't turn on now...only red led blinks when connected to PC...and PC is able to detect a connected device..but can't use adb....any hope for my device?
kirtikhurana said:
https://forum.xda-developers.com/lenovo-p2/how-to/how-to-restore-lenovo-p2-hard-brick-t3652900
Click to expand...
Click to collapse
Are you able to run this:
https://www.youtube.com/watch?v=-b7bx7Dl17w
That fixed my bootloop but I didn't remove the bootloader. You might be able to get in via the USB drivers in that video URL. Qualcomm_USB_Driver_2.2.0.0_Setup dot exe
Solved
kirtikhurana said:
https://forum.xda-developers.com/lenovo-p2/how-to/how-to-restore-lenovo-p2-hard-brick-t3652900
Click to expand...
Click to collapse
Thank youuuuuu so much... It worked... When I ran the blank flash file, the phone went into fastboot and I could load the bootloader and flash the ROM and recovery again...thank you...but I'm facing a problem of charging...when I plug it in, it restarts itself and doesn't charge...Everytime I plug it in to charger, it just restarts...but thank u...it works atleast..
How did your mobile got Hard Brick ? Reason ?
Hi all,
After reading many posts i got a little confused and i'm not getting any result. Please help.
What i want?: Flash stock rom and later consider rooting, and flashing haden or lineagos. (already found guidance but..)
The issue?: It doesn't get recognized through USB with my PC. (drivers installed, cable connected but...)
My questions? (correct me if wished):
1) In Odin mode (which i enter) is the usb port enabled by default? or it depends on the phone configuration.
2) In recovery mode i still cannot see the phone through the USB so is it open by default on stock recovery?
3) Finally can i flash stock rom i downloaded from sammobile through SD card? i found that to be my last resort but i think odin actual proper way or not?
I first thought it was the cable...since is not the original but it seems not be the case...which leads me to think its the phone's usb port....but with the cable i can charge the phone although i cannot see it through my PC.
So bottom line if the answer to my questions are that is always open (accesible through usb port) then it HAS to be the cable right?
If last quesiton is possible then i will conclude my searchings to be ended for now.
Thanks to all the posts within this tree.
Findings
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...
There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again
verdugon said:
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...
Click to expand...
Click to collapse
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.
Light at the end of the tunnel!!!
PMFRTT said:
There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again
Click to expand...
Click to collapse
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks
Light at the end of the tunnel!!!
SnowFuhrer said:
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.
Click to expand...
Click to collapse
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.
verdugon said:
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.
Click to expand...
Click to collapse
And to unlock the bootloader, just enable OEM unlock in the dev settings and it's ready to flash twrp. I remember when I got my Samsung and I was trying to fastboot unlock it lol.
Thanks to both of you! I will keep the thread on just in case...anyway may be it helps someone else.
verdugon said:
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks
Click to expand...
Click to collapse
Good luck! Let me know how it went.
Hey Guys,
I hope someone can help me.
I have a old galaxy a50 it is only booting into the download mode.
flash latest stock rom using odin
Odin can't find my connected device
Split1995 said:
Odin can't find my connected device
Click to expand...
Click to collapse
install samsung drivers
JuanTamqd21 said:
install samsung drivers
Click to expand...
Click to collapse
I've already installed them
Maybe update your drivers , like in windows update>more>optional updates or so
LR7875 said:
Maybe update your drivers , like in windows update>more>optional updates or so
Click to expand...
Click to collapse
That's the problem..
My drivers are up to date.. I can connect my other phone and this is no problem.
Just the A50 will not connected or detected by the pc.
Does the a50 charge and does the cable transfer data?
LR7875 said:
Does the a50 charge and does the cable transfer data?
Click to expand...
Click to collapse
The same cable works with the s20
And the A50 starts if I connect the cable.
No charge screen? Just straight boot to the Samsung screen and froze?
Straight to Samsung and than Downloader
LR7875 said:
No charge screen? Just straight boot to the Samsung screen and froze?
Click to expand...
Click to collapse
Need to make covid test BRB 30min 1h
Use other ports and/or charger
JuanTamqd21 said:
Use other ports and/or charger
Click to expand...
Click to collapse
As far as I know, the usb cable works flawlessly with a S20.
@Split1995 Please send me that what appears on the download mode screen.
LR7875 said:
@Split1995 Please send me that what appears on the download mode screen.
Click to expand...
Click to collapse
I've uploaded a screenshot at the Main Post of this Thread.
Odin Mode (AVB Fail)
Vbmeta Error verifying vbmeta xxxxx: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBMETA : No sign info
VBMETA .
Strange... Samsung phones have android vertified boot 2.0?
LR7875 said:
Strange... Samsung phones have android vertified boot 2.0?
Click to expand...
Click to collapse
Idk :-/
I Cannot Help You Fix Your Phone
Sorry
Samsung always does crap different. They integrated the nasty vertified boot but does not enable fastboot mode which allows disabling it. At least as far my knowledge reaches, your phone is just to me a fancy, glowing paperweight, although I know telling you that is heartbreaking.
Your options could really get up to:
Find, some other posts related, or senior members and developers who are helpful, or Google 'vertified boot Samsung bypass' as a last hope.
Define your A50 as obsolete, (maybe cry for your money then) sell it on ebay as 'parts / unfixable'. If you need the data protected, sell the body, screen, battery and dispose the motherboard in some known environmentally friendly way.
I don't recommend putting your hopes off, so I will provide some related posts from now on.
If you wanna get the data back, there is a (kind of hard) way to do it.
Unsolder your emmc chip and solder it onto a usb drive.
Also, replacing the EMMC storage chip may help as the corrupted data will be replaced, and maybe that is the answer of the problem but that requires high soldering skills which puts off most people.
Hello peeps.
My Poco F3 got hard bricked after update froze (was doing clean install of stable EU rom). Phone won't boot into any mode, and won't appear on pc. I've tried sorting the Test Pins 50 different ways and it still doesn't get picked up by the pc. Qualcomm Drivers are installed. Device is connected with working data transfer USB cable. It definitely is getting charge cause Battery and CPU are hotter than the rest of the phone. I'm at complete loss, I have no idea what I'm doing wrong or if I screwed up my phone that bad that EDL also doesn't work. Thanks for anyhelp!
1. Disconnect the battery
2. Make USB-Cable ready for Insertion
3. While shorting the 2 Test-pins, connect the USB-Cable
This is how I had to do it. ^^ This can be difficult and may require multiple trials, but this should work!
Windows should make the "Hardware connected"-Sound directly after connecting the USB-Cable, and show "Qualcomm 9008" in Device Manager.
If not, you need to repeat it: disconnect USB, short the 2 Test-pins and connect USB again. All while leaving battery unplugged.
Note: EDL Mode can't be bricked. This read-only Mode resides inside the Qualcomm SOC. There would have to be physical (hardware) damage for this to not function.
If you need more assistance or so, I can give you my Discord. Though you already seem quite far. Good luck dud.
cyanGalaxy said:
1. Disconnect the battery
2. Make USB-Cable ready for Insertion
3. While shorting the 2 Test-pins, connect the USB-Cable
This is how I had to do it. ^^ This can be difficult and may require multiple trials, but this should work!
Windows should make the "Hardware connected"-Sound directly after connecting the USB-Cable, and show "Qualcomm 9008" in Device Manager.
If not, you need to repeat it: disconnect USB, short the 2 Test-pins and connect USB again. All while leaving battery unplugged.
Note: EDL Mode can't be bricked. This read-only Mode resides inside the Qualcomm SOC. There would have to be physical (hardware) damage for this to not function.
If you need more assistance or so, I can give you my Discord. Though you already seem quite far. Good luck dud.
Click to expand...
Click to collapse
I'd love it if you added me on discord. Please do give me your name
sumurtugu said:
I'd love it if you added me on discord. Please do give me your name
Click to expand...
Click to collapse
cyanGalaxy#3161
Hello , Can someone help me please, edl mode ok but nothing more on my Poco F3....
gregdeberg33 said:
Hello , Can someone help me please, edl mode ok but nothing more on my Poco F3....
Click to expand...
Click to collapse
I am assuming the phone screen does not light up at all, no fastboot or recovery mode.
This would mean the phone's hard bricked. It will require EDL flashing which can be done by someone with an authorised Xiaomi account.
user0u said:
I am assuming the phone screen does not light up at all, no fastboot or recovery mode.
This would mean the phone's hard bricked. It will require EDL flashing which can be done by someone with an authorised Xiaomi account.
Click to expand...
Click to collapse
Hello Indeed and it has been done just to relock the bootloader, i have to use miflash with the same rom used and choose flash all with lock ?
gregdeberg33 said:
Hello Indeed and it has been done just to relock the bootloader, i have to use miflash with the same rom used and choose flash all with lock ?
Click to expand...
Click to collapse
Yes. Just to be safe I would flash the rom with "clean all" instead of "clean all and lock" if I were you. Then after booting up the phone you can later lock the bootloader safely using "fastboot oem lock" in adb.
^
user0u said:
Yes. Just to be safe I would flash the rom with "clean all" instead of "clean all and lock" if I were you. Then after booting up the phone you can later lock the bootloader safely using "fastboot oem lock" in adb.
Click to expand...
Click to collapse
Ok thanks but why ? Fastboot oem lock is better ?
gregdeberg33 said:
Ok thanks but why ? Fastboot oem lock is better ?
Click to expand...
Click to collapse
In case of "clean all and lock" if something goes wrong during flashing, the bootloader will be locked and you will not be able to fix the phone. So it is safer to flash the rom first without locking the bootloader and then lock it after booting up.
user0u said:
In case of "clean all and lock" if something goes wrong during flashing, the bootloader will be locked and you will not be able to fix the phone. So it is safer to flash the rom first without locking the bootloader and then lock it after booting up.
Click to expand...
Click to collapse
It will not.
If the Flash aborts, it won't even get to the stage of locking the bootloader.
gregdeberg33 said:
Ok thanks but why ? Fastboot oem lock is better ?
Click to expand...
Click to collapse
just clean & lock
cyanGalaxy said:
It will not.
If the Flash aborts, it won't even get to the stage of locking the bootloader.
Click to expand...
Click to collapse
I meant in case of a bootloop.
gregdeberg33 said:
Ok thanks but why ? Fastboot oem lock is better ?
Click to expand...
Click to collapse
Because if you lock bootloader while flashing a rom with a different region than what came in the box, you will hard brick your phone