Database Develop

Lesson for all---Flashing Radios and Pulling Batteries = Brick

my phone wont turn on after applied the leaked OTA. does that mean my phone is gone?
ilinfinityil said:
so basically the moral of the story is to not be impatient or else you'll brick your phone.
that should be the idea everyone in the community keeps in mind anyways.
Click to expand...
Click to collapse

yep
Sent from my Incredible using XDA App

Wont turn on as-in when you press the power button absolutely nothing happens?
Take the battery out and press power a few times, then put the battery back in and try again

mattbbx said:
Wont turn on as-in when you press the power button absolutely nothing happens?
Take the battery out and press power a few times, then put the battery back in and try again
Click to expand...
Click to collapse
no, not even vol down + power. i will bring it to a verizon store and see.

zeke1988 said:
no, not even vol down + power. i will bring it to a verizon store and see.
Click to expand...
Click to collapse
Did you apply the OTA twice, if you did naughty naughty. You have a brick.
Also have you tried a battery pull?

TNS201 said:
Did you apply the OTA twice, if you did naughty naughty. You have a brick.
Also have you tried a battery pull?
Click to expand...
Click to collapse
no i didnt apply it twice. and yes i tried the pull. after applied the ota it ask me to hit power button to reboot and after that nothing happens.

zeke1988 said:
no, not even vol down + power. i will bring it to a verizon store and see.
Click to expand...
Click to collapse
As far as I know, bricking a radio update would atleast still allow you to turn the phone on, it would just be stuck at initializing the bootloader, correct me if I'm wrong anyone--
Also I would not bring it into a verizon store. Wait until the official OTA is released, then say you had a problem with that.

mattbbx said:
As far as I know, bricking a radio update would atleast still allow you to turn the phone on, it would just be stuck at initializing the bootloader, correct me if I'm wrong anyone--
Also I would not bring it into a verizon store. Wait until the official OTA is released, then say you had a problem with that.
Click to expand...
Click to collapse
thats a great idea. should i suspend my service or let it run for a month?

zeke1988 said:
thats a great idea. should i suspend my service or let it run for a month?
Click to expand...
Click to collapse
Just let your service continue as normal.
Also, silly question, I know, but have you tried variations of plugging it in/unplugging with/without battery?
And when you plug the phone in, does the charge light come on?

mattbbx said:
Just let your service continue as normal.
Also, silly question, I know, but have you tried variations of plugging it in/unplugging with/without battery?
And when you plug the phone in, does the charge light come on?
Click to expand...
Click to collapse
yea i did that, no light come on.

zeke1988 said:
thats a great idea. should i suspend my service or let it run for a month?
Click to expand...
Click to collapse
The update should be here in less than a month. Didn't you get the insurance? Just claim it lost/stolen. If you have a moral dilemma in doing that then just toss it in a dumpster or a lake. Then claim it lost/stolen.
Sent from my Rooted Incredible w/Froyo

zeke1988 said:
thats a great idea. should i suspend my service or let it run for a month?
Click to expand...
Click to collapse
Can you hold power + optical button to boot to bootloader and recovery? If so you could possible get it fixed of you follow this guide:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
If your phone doesnt function at all you could attempt the following.
You could just say this at a Verizon store.
I charged my phone last night, when I woke up this morning the back of the phone was extremely hot almost to hot to hold and when I tried to turn the phone on or whatever you want to say pressed the power key, etc it would not turn on or you could say your screen came on for a second and then went out and the phone powered down and would not come back on.
Or
if you have insurance just say it was stolen, lost, dropped in a lake, etc.

zeke1988 said:
yea i did that, no light come on.
Click to expand...
Click to collapse
Strange--i'm not sure if a bricked radio would cause that, but it could perhaps indicate another issue. Does the radio's firmware also control the phones power/charging system?

htc_woe_is_me said:
The update should be here in less than a month. Didn't you get the insurance? Just claim it lost/stolen. If you have a moral dilemma in doing that then just toss it in a dumpster or a lake. Then claim it lost/stolen.
Sent from my Rooted Incredible w/Froyo
Click to expand...
Click to collapse
i didnt bought the insurance. i guess i will use the 2.2 OTA reason. i hope its August 6th!!

htc_woe_is_me said:
The update should be here in less than a month. Didn't you get the insurance? Just claim it lost/stolen. If you have a moral dilemma in doing that then just toss it in a dumpster or a lake. Then claim it lost/stolen.
Sent from my Rooted Incredible w/Froyo
Click to expand...
Click to collapse
Dont forget to take out your SD card first, and battery

mattbbx said:
Strange--i'm not sure if a bricked radio would cause that, but it could perhaps indicate another issue. Does the radio's firmware also control the phones power/charging system?
Click to expand...
Click to collapse
yes and yes it could. the radio contains the big bad bootloaders. if it stopped mid update, its gone. you might try connecting usb to pc. and see if you get a device id.

Shadowmite said:
yes and yes it could. the radio contains the big bad bootloaders. if it stopped mid update, its gone. you might try connecting usb to pc. and see if you get a device id.
Click to expand...
Click to collapse
nope totally die. now i dont even have a backup phone to use...

Shadowmite said:
yes and yes it could. the radio contains the big bad bootloaders. if it stopped mid update, its gone. you might try connecting usb to pc. and see if you get a device id.
Click to expand...
Click to collapse
I guess if that gets nuked the only way to recover it would be a manual hot-air removal and a manual reflash of the chip itself (good luck finding the papers for it), and then reflowing the chip back to the board (also assuming here it's one NAND). You'd think with the way these things work they would have a fail-over chip or something, phone falls off desk during OTA, battery goes flying. FFFFFFFFFFFFFFFFFFFFFFUUUUUUUUUUUUUUUUU

explain exactly what you did, and what it did. as much detail as possible.

Shadowmite said:
explain exactly what you did, and what it did. as much detail as possible.
Click to expand...
Click to collapse
1. i downloaded PB31IMG from the leaked 2.2 thread last night. (old pb31img). installed and got it running. he said install official OTA but none pushed to me.
so i downloaded the new PB31IMG and installed over. BUT after installed, the phone reboot and running great.
2. next, i download the leaked OTA and rename it to update *zip file*
3. i boot into recovery and start the update. after that it said something like, hit power button/reboot to continue the process. so i did. after that a green circle with arrow point counter-clockwise showed up and after a moment it turned off and on *same green icon* and off again. after that nothing happens.

[Q] Phone will not boot. AGAIN.

This has happened to me numerous times, and I am dead frustrated.
On numerous roms, i would select reboot from the advanced menu,
the phone would proceed to shut down, and NOT boot up again.
It then appears to be dead until god knows when.
It will not respond to buttons and charge light will not come on.
I don't even know how i solved it previous times,
if i recall correctly, it was just constantly removing the battery, putting it back in and seeing if it worked.
My question is, is there an easy way to solve this? or is there a way to prevent this?
Also would like to add I am running blackrose hboot and 4ext touch recovery,
Thanks!

spazzy1912 said:
This has happened to me numerous times, and I am dead frustrated.
On numerous roms, i would select reboot from the advanced menu,
the phone would proceed to shut down, and NOT boot up again.
It then appears to be dead until god knows when.
It will not respond to buttons and charge light will not come on.
I don't even know how i solved it previous times,
if i recall correctly, it was just constantly removing the battery, putting it back in and seeing if it worked.
My question is, is there an easy way to solve this? or is there a way to prevent this?
Also would like to add I am running blackrose hboot and 4ext touch recovery,
Thanks!
Click to expand...
Click to collapse
are you sure your usb port works and it was charged? lol
i see there's a thread in this section "how to unbrick incredible s" someone mentions a software called j-tag.
never heard of it but maybe you could look into it

djbenny1 said:
are you sure your usb port works and it was charged? lol
i see there's a thread in this section "how to unbrick incredible s" someone mentions a software called j-tag.
never heard of it but maybe you could look into it
Click to expand...
Click to collapse
This happened when it was plugged in and charging lol.
and jtag isnt a software, it is an expensive box that recovers hard bricks
^ I THINK
but yeah, you use JTAG if you HARD BRICKED it.
i dont think i hard bricked mine lol

Charge overnight
Sent from my HTC One X using Tapatalk 2

QHSUSB_DLOAD mode??

Hi everybody,
a friend of mine got his HTC One (black) yesterday and rooted it. He flashed a proper custom ROM on it which I and another one of my work buddy use as well without any issues (InsertCoin). No further flashes done, no other custom kernels, no S-Off, no SuperCID. Just unlocked Bootloader and custom ROM.
He let the device run dry yesterday evening so it shut off itself automatically. He put it on his charger, the phone turned on, he did some surfing and installing apps from the market and set up his alarm. The phone charged over night and he was also able to switch off the alarm this morning.
He got ready for work, got into his car and wanted to switch on the screen on the one for some good tunes. But the screen stayed black.
When I arrived at work, he was a little upset and panicked a little. I thought I was able to recover the device.
After plugging it in to my work computer, the device manager just shows a unknown device called "QHSUSB_DLOAD" so I went to google and looked it up..
Weird thing is: QHSUSB_DLOAD wasnt seen yet on the HTC One (M7) as far as I can see it and it was pretty bad on the HTC One S. It means "Qualcom High Speed USB Download Mode" and on the One S as well as on the Nexus 4 this devices showed up after the bootloader got damaged or the device got stuck in that mode for good.
When plugging the device in (USB / Wall charger) the charging LED doesnt turn on at all, the capacitive buttons dont start to blink while holding down the power button as well.
This thing seems to be gone for good.
But aint it the way that we dont even have any access to the bootloader if its not an official update from HTC? Signature check and stuff? Since the device was rooted, no OTA updates were able to arrive at all. He told me that he didnt try to flash anything after we flashed the custom ROM.
Any advice on that?

Did you even try booting the device first thru hboot/bootloader or holding the power button to force a restart? If you did try connecting the device while on QHSUSB_DLOAD and execute a compatible RUU on your PC. RUU uses android's download mode to flash the ROM so it should be repaired by an RUU.

Already tried, no luck. Tells me the device has not been found.

I am sorry to hear that, man, but from the looks of it your friend now has a paperweight. I'd take it to an HTC service center and hear what they have to say regarding this; of course it will no longer be covered under warranty, but maybe they can fix it for you for a price or something.

Are you sure RUU can't find the phone? If it can't then I guess only a JTAG box can fix it so either send it to HTC for repair or have someone who knows JTAG fix it.
Try4Ce said:
Already tried, no luck. Tells me the device has not been found.
Click to expand...
Click to collapse

I saw this issue on my friend's GS3 once. It was hard bricked and there was no way to recover from what I read (at least on the GS3). I know I saw a thread somewhere here in this forum about the same issue and someone linked to a Sensation thread where there was a way to fix it but I'm not sure if it would apply to the One

Same problem - but the phone magically fixed itself!
I had the exact same problem with my HTC One as described in OP...
My alarm went off in the morning and I set off for work, my battery was low but I thought that I would just charge it when I got to work. I was playing a game (Dungelot) whilst waiting for my bus and was receiving pop up messages about low battery. When it got to 4% left I decided that I would finish the level then close the game down, but as I was just about to finish, the phone went blank...I assumed that I had naturally used up all the battery life and although peeved that I had probably lost my progress in the game, wasn't too bothered.
I got to work and plugged my phone in to charge on my computer. The computer wanted to search for QHSUSB_DLOAD drivers but I thought this must be what it does when my phone isn't switched on and it finds the device. I cancelled the search prompt and tried to switch my phone on...nothing happened.
I tried for the rest of the day, trying to force shut down the bricked phone by holding power in for 30 secs, trying to power into boot mode etc...everything! But the phone would not switch on and the only response I got from it was a little orange LED every now and again and the QHSUSB_DLOAD prompt.
After googling the prompt - I found myself here and REALLY began to sh*t my pants! I've only had the phone less than a month and felt I was tech-savvy enough to flash my phone with a new ROM (Android Revolution HD) to try and get rid of some of the bloatware. I had flashed a new ROM successfully a coupld of weeks before and everything had been fine up that point.
I went home depressed but throught i'd try to plug my phone into a proper mains charger rather than my work's old USB cable (that came with my previous HTC Desire Z) I was going to try a long night of searching the net to try and find a way where I could at least recover the photo's, Zoe's and vids of my new born son but had such a headache that I gave up and went for an early night.
I was woken unexpectedly the next morning by my phone alarm going off! I stopped the alarm and the home just went to Home screen as normal! I don't know how or why these events happened...whether it was the flashed ROM, the game I was playing, the battery running out before the phone could shut down properly, the old USB cable in my work not charging but detecting the device or a combination of all of those, but so far, the phone jumped back into life with the alarm after being charged in the mains all night!
Thought i'd share as it may just help someone else out there who encounters this!

Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
Also, its not unheard of. I've seen it happen a few times in these forums.
Sent from my HTC One using XDA Premium 4 mobile app

I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app

lampel said:
I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.

same here
Any idea how to fix it?

Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
Jtag or send it to HTC is the only way.
Sent from my HTC One using Tapatalk

My Solution
Had the same Problem.
My Solution was to Download "HTC One (M7) Toolkit" and force Fastboot.
Pushed Power and Volume Down until Screen was Flashing.
Took about 2 minutes and the Phone was rebooting.
I have no idea what was happening. I have no idea if this helps or works for others. But its worth trying.
Sorry for my bad english.

Try4Ce said:
Any advice on that?
Click to expand...
Click to collapse
CoryTallman said:
Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Click to expand...
Click to collapse
bkmenon said:
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.
Click to expand...
Click to collapse
Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
This is some kind of mode that is enabled when you hold power on button when the device battery is completely drained. i.e. when you try to turn device on it will not boot up (Special I was connected to usb cable via PC to charge my phone NEXUS 4 when I get into this mode). I saw a similar mode where nvflash commands are executed something like APX(can't recall correctly) with Tegra 4 device (that time also I was connected with a usb cable and charging the tablet when it was completely drained!). A simple solution to quit this issue is DO not Panic and let the device get a little charge. After that boot normally with the power button. In case if it didn't try other modes to enter such as recovery or fastboot reboot commands if your device is getting recognised..

QHSUSB DLOAD means its a hard bricked phone, No amount of messing about with it will fix it, Send it to a service centre, it will probable have to have the motherboard replaced..Sorry

My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..

danielr18 said:
My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..
Click to expand...
Click to collapse
What do you mean by "force"? What did you do exactly?

My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.

danielr18 said:
My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.
Click to expand...
Click to collapse
mine spent the night carrying on waking took the charger and the green light for continued access, tried to turn it on but could not. After reading your response, I tried to hold the power button for longer. After 15 seconds the phone rang and the light came on, everything works perfect so far

Today while I was updating firmware phone gone to QHSUSB_DLOAD mode.
I am guessing it's end of road. :crying:

[Q] My Note keepsTurning off, help ..URGENT

Hello developers,
Suddenly my note cant start any more, it shows the Samsung logo and then turn off.
in rare cases it will continue to the splash screen but then quickly turn off. ...
what would this be,,, a soft brick,,, a hard brick,,, or a battery problem,,,,

Alsager said:
Hello developers,
Suddenly my note cant start any more, it shows the Samsung logo and then turn off.
in rare cases it will continue to the splash screen but then quickly turn off. ...
what would this be,,, a soft brick,,, a hard brick,,, or a battery problem,,,,
Click to expand...
Click to collapse
Easiest way to make sure it's not a battery problem is just to buy a new one from ebay and eliminate the possibility.
But it sounds like an internal problem to me, not software related. You could try a wipe.

wrsg said:
Easiest way to make sure it's not a battery problem is just to buy a new one from ebay and eliminate the possibility.
But it sounds like an internal problem to me, not software related. You could try a wipe.
Click to expand...
Click to collapse
If the battery has waranity? how you find out is slow

wrsg said:
Easiest way to make sure it's not a battery problem is just to buy a new one from ebay and eliminate the possibility.
But it sounds like an internal problem to me, not software related. You could try a wipe.
Click to expand...
Click to collapse
drulo222 said:
If the battery has waranity? how you find out is slow
Click to expand...
Click to collapse
I did a factory reset ( I was on JB then) and didn't solve the issue. when the phone is connected to the charger it can go beyond the Samsung logo and the splash screen for a while but will turn off quickly. without a charger it will only show the Samsung logo and then turn OFF.

Can you go into recovery, plug the cable, and then power off the phone? leave it like that for few minutes.

I can go into the download mode but not recovery.... what does that mean???? Tried your other suggestion, but no luck...!!

Is your battery swollen if looking at the side and you say it will go past splash screen if plugged into charger so does that mean it will boot into the Rom if plugged in or does it just stay splash screen and also if not able to get into recovery could mean something happened with the kernel so flashing a fresh jb Rom with Odin maybe what you need. The problem with that is if your battery is bad it could cause more problems trying to flash anything with dead battery as in bricking the device. So you should start with new battery and let charge a few hours then see if your phone boots up if not then you could flash with pc Odin and go from there.
Sent from my GT-N7000 using XDA Premium 4 mobile app

He should try kernel option you gave him, if everything else failed. I read around there were like 3 people with same situation. Maybe they used the same thing?
Search philz kernel, download one or two, and flash those in odin. Its a safe kernel, and powerful cwm.
He probably fixed by now. Hope so, for his own good.

Issue Solved, It was broken battery, Changed the batter and the phone is working again. Thanks everybody for your help....

Alsager said:
Issue Solved, It was broken battery, Changed the batter and the phone is working again. Thanks everybody for your help....
Click to expand...
Click to collapse
by any chance, do you know what were the old battery voltages under measurements?

black screen

At least once a week I go to use my phone and it will not turn on? I have to hit the power and volume down to reboot the phone. It's getting worse and worse does anyone know why this is happening. I tried to search I didn't see anything. I am on Att and stock.

jason504 said:
At least once a week I go to use my phone and it will not turn on? I have to hit the power and volume down to reboot the phone. It's getting worse and worse does anyone know why this is happening. I tried to search I didn't see anything. I am on Att and stock.
Click to expand...
Click to collapse
I am sure you tried factory reset already? I had a few in phones in the past do that. Usually was a bad battery. When did it all start? How old is phone? Any apps you install and it started doing this?
Leaning more towards you will need to ship in for a warranty with Samsung.

Nick216ohio said:
I am sure you tried factory reset already? I had a few in phones in the past do that. Usually was a bad battery. When did it all start? How old is phone? Any apps you install and it started doing this?
Leaning more towards you will need to ship in for a warranty with Samsung.
Click to expand...
Click to collapse
This is my 2nd phone the first one got screwed up with a update. I have had this one for about 4 months and it just started doing it about a month ago. Now it has done it 3 times this week. Once just now and it happens on the charger and off the charger. It has made me late waking up twice. I haven't done a phone restore yet and I haven't installed any new apps.
Sent from my SM-N950U using Tapatalk

jason504 said:
This is my 2nd phone the first one got screwed up with a update. I have had this one for about 4 months and it just started doing it about a month ago. Now it has done it 3 times this week. Once just now and it happens on the charger and off the charger. It has made me late waking up twice. I haven't done a phone restore yet and I haven't installed any new apps.
Click to expand...
Click to collapse
Sorry didn't read right tired ha. Black screen usually sign of bad screen. Got mixed up and thought it was restarting on it's on. If there was no apps that caused it. You didn't mess with any settings? Said your stock.
If none of the solutions others suggest soon don`t work. I'd go for a factory reset last resort. Worst case you will have to ship again to Samsung sadly

Nick216ohio said:
Sorry didn't read right tired ha. Black screen usually sign of bad screen. Got mixed up and thought it was restarting on it's on. If there was no apps that caused it. You didn't mess with any settings? Said your stock.
If none of the solutions others suggest soon don`t work. I'd go for a factory reset last resort. Worst case you will have to ship again to Samsung sadly
Click to expand...
Click to collapse
I see a lot of people having this problem. Not on here but online and it's not just the Note 8 it's the S8 too.
Sent from my SM-N950U using Tapatalk

jason504 said:
I see a lot of people having this problem. Not on here but online and it's not just the Note 8 it's the S8 too.
Click to expand...
Click to collapse
That's concerning. I take it most people with same situation as yours, shipped into sammy? Sucks you gotta go through this bs again maybe.

Just as suggestion, but if you use AOD try turning it off and and see if this fixes the problem.
I had this problem with Ironman ROM and turning off AOD fixed the problem.

How to Fix A Samsung Tablet with Black Screen
jason504 said:
At least once a week I go to use my phone and it will not turn on? I have to hit the power and volume down to reboot the phone. It's getting worse and worse does anyone know why this is happening. I tried to search I didn't see anything. I am on Att and stock.
Click to expand...
Click to collapse
Hi,
If you can't reboot your device to fix black screen problem, you can try FoneLab broken android phone data extraction to fix it.
Download and install the program on your computer, and then connect device to computer.
Then you can scan, select and recover data with a few clicks.
More details from fonelab and the post How to Recover Data from Android Phone That Won't Turn On or How to Fix A Samsung Tablet with Black Screen.