[Q] Hard brick - Nexus 7 (2013) Q&A

Woke up this morning and my N7 wouldn't turn on. Plugged it in and the charging indicator came up showing at nearly full charge. Holding the power button then turned it on. Went away for an hour or two, came back and it was off. When I turned it back on it was stuck on the X screen. Forcing a reboot with power+vol just led to the tablet turning off. And now I just plugged it into my computer and QHSUSB_DLOAD came up.
Just got the damn thing a couple days ago and it was 100% stock. Any ideas as to what may have caused this?

Just unplugged it and it turned on but is again stuck on the X. Is QHSUSB_DLOAD no longer indicative of a hard brick?

I'm a newbie here, but let's try.
If you can get to the X one, then I think it's not brick yet.
Maybe your should try to press pwer button and volume down to get to fastboot. You press this combination when your Nexus is turned off.

opticaldh said:
I'm a newbie here, but let's try.
If you can get to the X one, then I think it's not brick yet.
Maybe your should try to press pwer button and volume down to get to fastboot. You press this combination when your Nexus is turned off.
Click to expand...
Click to collapse
once I turn it off the whole cycle starts over again. It's sporadically deciding whether or not it wants to boot but I'll keep trying to get into fastboot

herculesgs said:
Woke up this morning and my N7 wouldn't turn on. Plugged it in and the charging indicator came up showing at nearly full charge. Holding the power button then turned it on. Went away for an hour or two, came back and it was off. When I turned it back on it was stuck on the X screen. Forcing a reboot with power+vol just led to the tablet turning off. And now I just plugged it into my computer and QHSUSB_DLOAD came up.
Just got the damn thing a couple days ago and it was 100% stock. Any ideas as to what may have caused this?
Click to expand...
Click to collapse
In doing a little googling it looks to be possibly caused by the update. If you look up the error, you will see a common problem where HTC bricked a bunch of different phones when they pushed an ota a while back. I would say just return it and get a new one . You could do some research and try it yourself. Are you able to get into your bootloader ( vol+ and Vol - when you trun it on)?

uprightbass360 said:
In doing a little googling it looks to be possibly caused by the update. If you look up the error, you will see a common problem where HTC bricked a bunch of different phones when they pushed an ota a while back. I would say just return it and get a new one . You could do some research and try it yourself. Are you able to get into your bootloader ( vol+ and Vol - when you trun it on)?
Click to expand...
Click to collapse
I was able to get into it this morning and I wiped my cache. The next time it decides to turn on/I can get it into the bootloader I'll try a factory reset

herculesgs said:
I was able to get into it this morning and I wiped my cache. The next time it decides to turn on/I can get it into the bootloader I'll try a factory reset
Click to expand...
Click to collapse
Well something got corrupted, but if its booting its not hard bricked (that's good news). Luckily for you as well the aosp images are up so if you want to do a restore you can snag your images, and just do a fastboot install. I hope this isn't indicative of another problem with the device itself, I still maintain that you should probably exchange your device for a new one if you did indeed do nothing to the device. It would be a shame if the same problem happened again because of a faulty component.

uprightbass360 said:
Well something got corrupted, but if its booting its not hard bricked (that's good news). Luckily for you as well the aosp images are up so if you want to do a restore you can snag your images, and just do a fastboot install. I hope this isn't indicative of another problem with the device itself, I still maintain that you should probably exchange your device for a new one if you did indeed do nothing to the device. It would be a shame if the same problem happened again because of a faulty component.
Click to expand...
Click to collapse
Yeah, I most likely will. It'll boot to the X probably once every 25 tries so there's something weird going on and it's probably safer just to return it then find a fix and have it happen again.

herculesgs said:
Yeah, I most likely will. It'll boot to the X probably once every 25 tries so there's something weird going on and it's probably safer just to return it then find a fix and have it happen again.
Click to expand...
Click to collapse
Just out of curiosity, where did you purchase it from? Does the seller recognize a lemon as returnable, would you possibly have to tell them you just didn't like it?

uprightbass360 said:
Just out of curiosity, where did you purchase it from? Does the seller recognize a lemon as returnable, would you possibly have to tell them you just didn't like it?
Click to expand...
Click to collapse
Wally world. afaik they're pretty lax on returns

update
Got into the bootloader and did a factory reset. Everything seems to be working again now

herculesgs said:
Got into the bootloader and did a factory reset. Everything seems to be working again now
Click to expand...
Click to collapse
Awesome! Love a happy ending.

Mine was like that all day. I am unlocked and rooted but stock ROM. Damn thing was on an x all day. I was finally able to get to TWRP and flashed my latest backup. No ideas what happened or why.
Sent from my Nexus 7 using xda app-developers app

AnarchoXen said:
Mine was like that all day. I am unlocked and rooted but stock ROM. Damn thing was on an x all day. I was finally able to get to TWRP and flashed my latest backup. No ideas what happened or why.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.

What happens when you do vol down and power to try and get into the bootloader? Nothing at all?
Sent from my Nexus 7 using xda app-developers app

kd5dmg said:
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
Click to expand...
Click to collapse
Follow hercules advice. Vol Down + Power to get to bootloader. Then you should be able to get to recovery. Let us know.
Sent from my Nexus 7 using Tapatalk 4

kd5dmg said:
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
Click to expand...
Click to collapse
Stuck at Google means /system is corrupted or erased (fastboot to restore system.img)
Stuck at X means something wrong with userdata/cache (factory restore from recovery)
Won't start at all with USB identifying as QHSUSB_DLOAD means either bootloader corrupted or raw partitions corrupted
I suggest you reflash again.

Related

Galaxy Nexus in reboot cycle

Hi
My Galaxy Nexus has just started into a constant reboot cycle. The Google logo comes up and the the multi coloured animation thing like normal and then it goes back to beginning.
I never get to enter my pin or anything.
Has this happened anybody else?
It also gets quite hot after been in reboot phase for 20-30 mins.
Thanks
Brian
Need more details: what ROM/kernel you're using? Do you have ClockWork Recovery installed? What did you do to your phone before this happened?
Sent from my Galaxy Nexus using xda premium
MS. said:
Need more details: what ROM/kernel you're using? Do you have ClockWork Recovery installed? What did you do to your phone before this happened?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Im not sure on exact details other than its as it was when I bought it apart from 4.0.2 is installed
I didnt root it or change radio etc
I was just using it as normal, was going in to check battery level I think
ClockWork isnt installed
If I hold down power button and volume button and go into recovery options reocovery mode doesnt work, restart bootloader doesnt help either
Only other options I have are Start and Power off
When I try and go back into those options again all I get is a screen with green Android and Start > Downloading > Do not turn off target
It can stay in this screen for 5 mins or more and go nowhere
This happened earlier on as well so I just turned it off
I tried the same procedure again and I got the recovery menu again but it still didnt work and then tried it again and I just got the Downloading message again
Not sure if any of that helps, I cant check the kernel version anywhere right now.
Oh and its the GSM release of the Nexus
bmulvany said:
Im not sure on exact details other than its as it was when I bought it apart from 4.0.2 is installed
I didnt root it or change radio etc
I was just using it as normal, was going in to check battery level I think
ClockWork isnt installed
If I hold down power button and volume button and go into recovery options reocovery mode doesnt work, restart bootloader doesnt help either
Only other options I have are Start and Power off
When I try and go back into those options again all I get is a screen with green Android and Start > Downloading > Do not turn off target
It can stay in this screen for 5 mins or more and go nowhere
This happened earlier on as well so I just turned it off
I tried the same procedure again and I got the recovery menu again but it still didnt work and then tried it again and I just got the Downloading message again
Not sure if any of that helps, I cant check the kernel version anywhere right now.
Oh and its the GSM release of the Nexus
Click to expand...
Click to collapse
Try removing the battery and then turn it on, works for me; have you installed some new apps before this happened?
quiro91 said:
Try removing the battery and then turn it on, works for me; have you installed some new apps before this happened?
Click to expand...
Click to collapse
have tried that several times
installed nothing new in last few days but even if I did I have no way of getting in to uninstall it if thats what was causing the issue
bmulvany said:
have tried that several times
installed nothing new in last few days but even if I did I have no way of getting in to uninstall it if thats what was causing the issue
Click to expand...
Click to collapse
and you can't remove the battery and then boot in recovery mode? are you sure?
quiro91 said:
and you can't remove the battery and then boot in recovery mode? are you sure?
Click to expand...
Click to collapse
I choose recovery mode and the phone restarts, Google logo comes up and it then goes to a picture of android robot with a red excamation mark over it
It just stays there on that screen for about 2-3 minutes and then retarts
After restarting it goes through sme sequence as before constantly going from Google Logo to multi coloured animation and then restarts again. At no stage do I get to login screen.
Only other option I get when I hold down power button and volume button is to restart bootloader, start and power off.
bmulvany said:
I choose recovery mode and the phone restarts, Google logo comes up and it then goes to a picture of android robot with a red excamation mark over it
It just stays there on that screen for about 2-3 minutes and then retarts
After restarting it goes through sme sequence as before constantly going from Google Logo to multi coloured animation and then restarts again. At no stage do I get to login screen.
Only other option I get when I hold down power button and volume button is to restart bootloader, start and power off.
Click to expand...
Click to collapse
try this, from step 4:
http://forum.xda-developers.com/showthread.php?t=1366806
it should work
quiro91 said:
try this, from step 4:
http://forum.xda-developers.com/showthread.php?t=1366806
it should work
Click to expand...
Click to collapse
that worked thanks
the hardest part was getting my laptop to pick up my phone in bootloader mode but my laptop is getting old and on its last legs, the usb ports are dodgy for everything
Just to warn you, there's a good chance it will happen again eventually. A few days ago it happened to me for the second time (completely stock).
I decided this time to root it and install a custom rom seeing as how I'd have to flash stock again anyway. I'm hoping that whatever bug that caused it has been fixed in 4.0.3.
case0 said:
Just to warn you, there's a good chance it will happen again eventually. A few days ago it happened to me for the second time (completely stock).
I decided this time to root it and install a custom rom seeing as how I'd have to flash stock again anyway. I'm hoping that whatever bug that caused it has been fixed in 4.0.3.
Click to expand...
Click to collapse
how often has this happened to you where the phone goes into reboot cycle?
are you on 4.0.2 as well I assume its the gsm phone as well?
its handy to sort but a pain in the whole having to install all the apps again
bmulvany said:
how often has this happened to you where the phone goes into reboot cycle?
are you on 4.0.2 as well I assume its the gsm phone as well?
its handy to sort but a pain in the whole having to install all the apps again
Click to expand...
Click to collapse
The first time it happened was the 11th Jan, on 4.0.1, and the second time was the 29th Feb, on 4.0.2. And yeh it's GSM.
Yeh exactly, sucks having to install apps again etc. Now I'm rooted I've got a nandroid backup just in case it happens again.

Downloading...do not turn off target.

Hey guys I really need help here. I have no clue how but my phone into some weird mode displaying the message in the title. I have a stock Nexus and didn't try to flash or anything like that.
I tried everything on the internet but nothing seems like its working. I am a real noob and need any advice. Is there a way to get the phone back to normal without having to unlock it, root or something like that?
you most likely turned it on without realizing that your fingers are on the volume down and power at the same time. try pulling the battery and turn on the phone again
crazyalaa said:
Hey guys I really need help here. I have no clue how but my phone into some weird mode displaying the message in the title. I have a stock Nexus and didn't try to flash or anything like that.
I tried everything on the internet but nothing seems like its working. I am a real noob and need any advice. Is there a way to get the phone back to normal without having to unlock it, root or something like that?
Click to expand...
Click to collapse
You put your phone into download mode somehow.
At least, if your title is what your talking about.....then yea, your in download mode.
If you didn't flash anything....try just pulling the battery and restarting the phone.
I tried that. Nothing is working; the phone gets stuck on the google logo and then the logo itself goes and comes back really quickly then the phones turn off. When the phone turns off it takes 10 mins to get it up again!! No clue...
Now the phone won't turn on.
crazyalaa said:
I tried that. Nothing is working; the phone gets stuck on the google logo and then the logo itself goes and comes back really quickly then the phones turn off. When the phone turns off it takes 10 mins to get it up again!! No clue...
Click to expand...
Click to collapse
Can u boot into recovery? If so just flash a rom.
Sent from my Galaxy Nexus using xda premium
The phone isn't turning on anymore
Is the battery now dead? Will the phone turn on when its plugged in?
I got back to the same screen now, I removed the battery and phone won't even turn off. It's stuck on the same screen even without the battery??? what's going on?
Update: Ok the phone turned off and then I tried to turn it on. It goes to the Google logo and then the screen goes blank.
crazyalaa said:
I got back to the same screen now, I removed the battery and phone won't even turn off. It's stuck on the same screen even without the battery??? what's going on?
Update: Ok the phone turned off and then I tried to turn it on. It goes to the Google logo and then the screen goes blank.
Click to expand...
Click to collapse
Can you get to the bootloader?
Vol. Down + vol. Up and power together.
If so then you'll be fine. Just flash a factory image.
There are a few threads that will go through the process in more detail than I am willing to at 6:08am!
Is there a way to take my photos and contact from the phone while it's in the downloading mode or any other way before I flash it. Or am I screwed? I don't have my stuff synced with google+
crazyalaa said:
Is there a way to take my photos and contact from the phone while it's in the downloading mode or any other way before I flash it. Or am I screwed? I don't have my stuff synced with google+
Click to expand...
Click to collapse
If the phone doesnt completely reboots to android, I dont think you can get your photo's.
Can you still get in fastboot mode?
my phone is doing the same thing, the downloading screen. I am totally stock, and i can easily turn my phone on and off except i wanna get into bootloader to flash CWM recovery and i cant do so because this screen is popping up.
bendirkss said:
my phone is doing the same thing, the downloading screen. I am totally stock, and i can easily turn my phone on and off except i wanna get into bootloader to flash CWM recovery and i cant do so because this screen is popping up.
Click to expand...
Click to collapse
Are you able to boot into the OS? Or it's only giving you download mode no matter what?
Do you have adb set up if yes adb reboot boot loader that will boot you into the boot loader screen
Sent from my Galaxy Nexus using xda app-developers app
cmstlist said:
(...) it's only giving you download mode no matter what?
Click to expand...
Click to collapse
this first.
DaLoona said:
If the phone doesnt completely reboots to android, I dont think you can get your photo's.
Can you still get in fastboot mode?
Click to expand...
Click to collapse
Bfitz26 said:
Do you have adb set up if yes adb reboot boot loader that will boot you into the boot loader screen
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
he can if adb is already running on the system. seems to be that he can't.
@op, if you're stuck on download mode, try odin (damn i really hate suggesting it); i was trying to see if heimdall supports our device, have yet to find proof.
crazyalaa said:
Hey guys I really need help here. I have no clue how but my phone into some weird mode displaying the message in the title. I have a stock Nexus and didn't try to flash or anything like that.
I tried everything on the internet but nothing seems like its working. I am a real noob and need any advice. Is there a way to get the phone back to normal without having to unlock it, root or something like that?
Click to expand...
Click to collapse
Is there a big green outlined arrow box at the top of your screen that says start, and it points to your power button? If so you are just at the Odin screen instead of your boot loader screen. You get here by just holding vol down and power instead of of holding both vol up/down and power which would bring you to the bootlloader. Also your phone obviously needs to be off before doing either of these. If in fact you are at the Odin screen simply push power and your phone will boot.
sent from my nexus using all the new features of the iphone5
crazyalaa said:
Hey guys I really need help here. I have no clue how but my phone into some weird mode displaying the message in the title. I have a stock Nexus and didn't try to flash or anything like that.
I tried everything on the internet but nothing seems like its working. I am a real noob and need any advice. Is there a way to get the phone back to normal without having to unlock it, root or something like that?
Click to expand...
Click to collapse
It sounds like your volume-down button might be stuck in the pressed-down position (or just shorted out). If that is the case, every time you try to turn your phone on, you will see the screen you described. You can try pressing the volume buttons many times to see if you can get the volume-down button unstuck. If you can't, you can replace the buttons fairly cheaply.
Of course, it could be caused by something else entirely, but that's what it seems like to me.
strumcat said:
It sounds like your volume-down button might be stuck in the pressed-down position (or just shorted out). If that is the case, every time you try to turn your phone on, you will see the screen you described. You can try pressing the volume buttons many times to see if you can get the volume-down button unstuck. If you can't, you can replace the buttons fairly cheaply.
Of course, it could be caused by something else entirely, but that's what it seems like to me.
Click to expand...
Click to collapse
If the vol-down button is stuck, try booting it up with both up and down held. You might be able to get either recovery or bootloader.
cmstlist said:
If the vol-down button is stuck, try booting it up with both up and down held. You might be able to get either recovery or bootloader.
Click to expand...
Click to collapse
+1
yeah try that
cmstlist said:
Are you able to boot into the OS? Or it's only giving you download mode no matter what?
Click to expand...
Click to collapse
Its working fine now. Except when I flash CWM, vis cmd prompt like I usually do, I can only go unto cem right away and then once I boot up into the os and turn the phone off to get into recovery stock recovery comes back.
Sent from my Galaxy Nexus

T-Mobile Galaxy S3 won't boot after Odin-HELP

So I just flashed the stock image through Odin (used the USB cable that came with the phone) and it boots past the boot animation(the T-Mobile 4g one) and then just hangs on "SAMSUNG" and it's still glowing and so is the notification LED but it won't boot, it just stays there. Can someone point me in the right direction to get this thing going? Is this a brick? I don't know what is wrong with it.
I believe It is hanging on the kernel (panic.... not you, the phone). Have you tried booting into recovery and wiping cache? (volume up + home button during hard reset)
Edit: Also what are you flashing from (i.e. CM, AOKP, TW custom ROM)?
if you were on a custom rom prior to reverting to stock, you need to do a wipe in recovery
Serious_Beans said:
So I just flashed the stock image through Odin (used the USB cable that came with the phone) and it boots past the boot animation(the T-Mobile 4g one) and then just hangs on "SAMSUNG" and it's still glowing and so is the notification LED but it won't boot, it just stays there. Can someone point me in the right direction to get this thing going? Is this a brick? I don't know what is wrong with it.
Click to expand...
Click to collapse
It took mine a very long time to boot after odin stock flash. But i dont think your screwed since it still powers on. Can you still get into download mode? Try to flash it again and see what happens.
Go into stock recovery and do a factory reset. Then reboot, that should do the trick.
Powered by the SGSIII
Reboot after ODIN
sswb27 said:
It took mine a very long time to boot after odin stock flash. But i dont think your screwed since it still powers on. Can you still get into download mode? Try to flash it again and see what happens.
Click to expand...
Click to collapse
OK, I am sure I am going to get blasted for putting this on the wrong thread but I have search!
Ran the boot program through ODIN on the Sprint version SPH-L710 and phone will not reboot now and cannot power on
toolkit says waiting for device
get the battery, Samsung and download screen briefly then it dies,
Afraid that I bricked it!
Any help would be appreciated!
rvshaw said:
OK, I am sure I am going to get blasted for putting this on the wrong thread but I have search!
Ran the boot program through ODIN on the Sprint version SPH-L710 and phone will not reboot now and cannot power on
toolkit says waiting for device
get the battery, Samsung and download screen briefly then it dies,
Afraid that I bricked it!
Any help would be appreciated!
Click to expand...
Click to collapse
Take out battery, unplug from computer, press and hold volume keys, plug in cable and insert battery again.
See if it goes into download mode.
Powered by the SGSIII
ThC23 said:
Take out battery, unplug from computer, press and hold volume keys, plug in cable and insert battery again.
See if it goes into download mode.
Powered by the SGSIII
Click to expand...
Click to collapse
red light does come on in the left
then battery symbol flash for a minute and nothing else
I ran into this exact same issue. I tried flashing kernal and everything after I did odin. What I had to do in order for my phone to boot was boot into recovery and do a factory reset. Keep in mind this was stock recovery so everything on your sd card will be gone after the wipe.
crash822 said:
I ran into this exact same issue. I tried flashing kernal and everything after I did odin. What I had to do in order for my phone to boot was boot into recovery and do a factory reset. Keep in mind this was stock recovery so everything on your sd card will be gone after the wipe.
Click to expand...
Click to collapse
Yes, wish I could boot into recovery but it will not even boot into recovery. Not sure if is a soft brick cannot load a screen regardless
Volume down + home screen + power button doesn't work for download mode? If you're screen is still powering on and showing the battery charging icon and samsung logo you haven't bricked your phone. I know on previous phones I have had that even though it showed nothing but a black screen odin still picked the phone up and was able to flash it.
crash822 said:
Volume down + home screen + power button doesn't work for download mode? If you're screen is still powering on and showing the battery charging icon and samsung logo you haven't bricked your phone. I know on previous phones I have had that even though it showed nothing but a black screen odin still picked the phone up and was able to flash it.
Click to expand...
Click to collapse
No, Volume down+home screen+power button only produces the Samsung or the Battery symbol for about a second, goes away and nothing else after that but a black screen, ODIN does not see the phone as it is not powered on, hope that makes sense
Factory reset worked perfectly. Too bad T-Mobile already shipped the replacement.
Sent from my SGH-T999 using Tapatalk 2
Johnny Blaze says ________?
I can't believe you called T-Mo for a replacement before performing a simple factory reset. Talk about a waste of money. As a future business owner this upsets me.
Eh lol oh well. Didn't think it would boot.
Sent from my SGH-T999 using Tapatalk 2
Serious_Beans said:
Eh lol oh well. Didn't think it would boot.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Well, if you're gonna play the system, might as well use your old phone to help us diagnose the imei lost problem and help the community. If you feel like helping us out, get ahold of lordmorphus or someone closely involved in this situation to have you run a few tests so we can figure this thing out. Ill be your bestest friend if you do
mrmako777 said:
Well, if you're gonna play the system, might as well use your old phone to help us diagnose the imei lost problem and help the community. If you feel like helping us out, get ahold of lordmorphus or someone closely involved in this situation to have you run a few tests so we can figure this thing out. Ill be your bestest friend if you do
Click to expand...
Click to collapse
Sure I'll pm him and see what we can do.
Sent from my SGH-T999 using Tapatalk 2
I pmed him. I'll see what we can do when he responds.
Sent from my SGH-T999 using Tapatalk 2
Serious_Beans said:
Eh lol oh well. Didn't think it would boot.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I can care less about exchanging the phone, but you did get a reply here of what to do.
What was the point of asking if you weren't gonna bother listening??
Powered by the SGSIII
Oh, Sh*t, I think I just bricked my phone - same thing happened. It now won't even allow me to boot. I took the battery out, unplugged the USB. Plugged the USB in and then put the battery back in. The LED light comes on for about 30 seconds and then goes off and stays OFF. I've tried POWER+UP/DOWN volume and HOME...still no avail.
The computer does recognize [the phone] when I plug it in by making a thumping sound and then it makes a few thumping sounds and then that's it.
PLEASE HELP!

[Q] "Unfortunately, the process com.android.phone has stopped."

Hi guys, I'm very sorry if this has been solved already but I've been searching a lot now and none of the methods seemed to help me. I'm running a One X International. Until yesterday, I was running one of the older Cyanogenmod 10 Nightly builds but due to some performance issues and whatnot (nothing major), I decided to finally put in some work to update my phone to 10.1. My HBOOT was still on one of the older versions so after searching around, it seemed reinstalling the stock ICS and then doing some OTA updates would be the easiest way (for a n00b like me).
After doing so, I unlocked my bootloader again, re-rooted my phone, installed a newer version of CWM Recovery and finally flashed the latest stable build of CM 10.1. My first problem came after rebooting, where it would just hang at the Cyanogenmod ring loop and nothing else. I booted back to recovery and wiped everything (cache, data, dalvik etc.) and did a factory reset then reflashed the rom. This time it booted up but then, the "Unfortunately, the process com.android.phone has stopped." kept popping up. I literally can't do anything (there's a microsecond of space after I click OK before it would pop up again). I have read some people suggesting to others that they need to do a factory reset but I've tried doing that and it still didn't work. I've even tried installing the latest Nightly build of CM10.1 but it still didn't seem to make any difference.
Could someone please offer some advice? Thanks a lot in advance.
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
MarcusJKX said:
Could someone please offer some advice? Thanks a lot in advance.
Click to expand...
Click to collapse
Did you flash the boot image?, and if so, did you fastboot erase cache after flashing the boot image?
matt95 said:
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
Click to expand...
Click to collapse
I'm hoping that it's not and somehow I doubt it since I didn't have any problems like this until what I described earlier.
Did you flash the boot image?, and if so, did you fastboot erase cache after flashing the boot image?
Click to expand...
Click to collapse
I'm sorry, I'm not quite sure what you mean. Do you mean Boot image as in the bootloader? I didn't touch the bootloader except that it got upgraded whilst I updated the official HTC rom and also when I unlocked it. But I did erase everything before flashing.
MarcusJKX said:
I'm sorry, I'm not quite sure what you mean. Do you mean Boot image as in the bootloader? I didn't touch the bootloader except that it got upgraded whilst I updated the official HTC rom and also when I unlocked it. But I did erase everything before flashing.
Click to expand...
Click to collapse
he means
Code:
fastboot flash boot boot.img
matt95 said:
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
Click to expand...
Click to collapse
matt95 said:
he means
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I don't think I did this. What is it for? I don't remember reading it in any guides although I read so many that I might've have forgotten.
MarcusJKX said:
I don't think I did this. What is it for? I don't remember reading it in any guides although I read so many that I might've have forgotten.
Click to expand...
Click to collapse
you have to flash the boot.img everytime u flash different rom
it is inside the zip file of the rom just extract it from there and take your phone to the bootloader and flash the boot.img...thn it will work perfectly
have a good read on how to flash a rom
http://forum.xda-developers.com/showthread.php?t=2069904
ll_r1d0_ll said:
you have to flash the boot.img everytime u flash different rom
it is inside the zip file of the rom just extract it from there and take your phone to the bootloader and flash the boot.img...thn it will work perfectly
Click to expand...
Click to collapse
Thanks a lot! I can't right now because like an idiot, I was in a rush before coz I had to leave for a few hours and really needed my phone so I thought maybe I'd try redoing the process. I got to the stage where I relocked the bootloader, factory reset, erased the rom, cache and pretty much everything but then I had to leave. Now that I'm back, the phone is out of battery coz I had it plugged in but it just wouldn't shut down for some reason so the screen remained on the bootloader wasting a ton of battery. This had happened yesterday when I was doing this and the battery would charge really slowly since the screen was constantly on. Do you know why this is? I don't think it's a hardware issue since after installing the stock rom yesterday, it could turn the phone off through the bootloader, recovery or just in the actual OS.
MarcusJKX said:
Thanks a lot! I can't right now because like an idiot, I was in a rush before coz I had to leave for a few hours and really needed my phone so I thought maybe I'd try redoing the process. I got to the stage where I relocked the bootloader, factory reset, erased the rom, cache and pretty much everything but then I had to leave. Now that I'm back, the phone is out of battery coz I had it plugged in but it just wouldn't shut down for some reason so the screen remained on the bootloader wasting a ton of battery. This had happened yesterday when I was doing this and the battery would charge really slowly since the screen was constantly on. Do you know why this is? I don't think it's a hardware issue since after installing the stock rom yesterday, it could turn the phone off through the bootloader, recovery or just in the actual OS.
Click to expand...
Click to collapse
the phone never charges in the bootloader ....as ur phone is off right now just plug it to a wall charger and leave it for around 2-3 hours and check if the Red LED turns on which will show that your phone is charging
ll_r1d0_ll said:
the phone never charges in the bootloader ....as ur phone is off right now just plug it to a wall charger and leave it for around 2-3 hours and check if the Red LED turns on which will show that your phone is charging
Click to expand...
Click to collapse
Aha didn't know that! Well I did leave it on the charger before i left although it was on the bootloader so like you said, it didn't charge. But when i came back (several hours later), the screen was black and the red LED was not on. Again like an idiot, I tried to turn it on and it went into the bootloader although it said that the battery is critically low. I then tried restarting it and now it's staying on the HTC Quietly Brilliant screen. Does it charge here? The red LED is on. If i press power+vol down then it would go into the bootloader so i guess it's not bricked right?
MarcusJKX said:
Aha didn't know that! Well I did leave it on the charger before i left although it was on the bootloader so like you said, it didn't charge. But when i came back (several hours later), the screen was black and the red LED was not on. Again like an idiot, I tried to turn it on and it went into the bootloader although it said that the battery is critically low. I then tried restarting it and now it's staying on the HTC Quietly Brilliant screen. Does it charge here? The red LED is on. If i press power+vol down then it would go into the bootloader so i guess it's not bricked right?
Click to expand...
Click to collapse
nop its not bricked and if your phone is now on just press the power button for few seconds until the 3 buttons flash and it wll turn off and when your phone will have enough battery charged it will automatically turn on (my htc one x do this) and dn you continue the steps dat i told you
ll_r1d0_ll said:
nop its not bricked and if your phone is now on just press the power button for few seconds until the 3 buttons flash and it wll turn off and when your phone will have enough battery charged it will automatically turn on (my htc one x do this) and dn you continue the steps dat i told you
Click to expand...
Click to collapse
Hmm i still can't turn it off. After holding the power button and waiting for the 3 buttons to flash, it would just reboot into the HTC screen. But it seems to be charging because when I booted into the bootloader just then, it doesn't say "power critically low" anymore.
By the way, whilst we're on the subject, do you know if it's possible to disable the ability to restart the phone by holding down the power button even when the phone is locked? I have quite a bulky case (from Ballistic) which makes the power button stick out a bit and sometimes when it's in my jeans and I kneel down to tie my shoelace, my leg would press into the button making the phone restart. This doesn't happen with the iPhone for example. on the iPhone, when the screen is locked, the power button doesn't give any response and even when the screen is unlocked, holding down the power button will only display the option to shut it off. This has always annoyed me on the One X (don't know if this is the case for other Android phones).
MarcusJKX said:
Hmm i still can't turn it off. After holding the power button and waiting for the 3 buttons to flash, it would just reboot into the HTC screen. But it seems to be charging because when I booted into the bootloader just then, it doesn't say "power critically low" anymore.
By the way, whilst we're on the subject, do you know if it's possible to disable the ability to restart the phone by holding down the power button even when the phone is locked? I have quite a bulky case (from Ballistic) which makes the power button stick out a bit and sometimes when it's in my jeans and I kneel down to tie my shoelace, my leg would press into the button making the phone restart. This doesn't happen with the iPhone for example. on the iPhone, when the screen is locked, the power button doesn't give any response and even when the screen is unlocked, holding down the power button will only display the option to shut it off. This has always annoyed me on the One X (don't know if this is the case for other Android phones).
Click to expand...
Click to collapse
very good now ur phone is charging and i hope u have flashed the boot.img too well i also have that issue with that button :/ but i keep the phone in the opposite direction like the headphone jack side goes inside pocket and the mic side is on the outside whn inside the pocket ....thats the only idea i use :/
ll_r1d0_ll said:
very good now ur phone is charging and i hope u have flashed the boot.img too well i also have that issue with that button :/ but i keep the phone in the opposite direction like the headphone jack side goes inside pocket and the mic side is on the outside whn inside the pocket ....thats the only idea i use :/
Click to expand...
Click to collapse
Yeah I guess that's the only solution then. Glad I'm not the only one!
I just got home and it looks like I was wrong. The phone's screen was off and no red LED lights were showing even though it's plugged into the wall. I disconnected it and waited a few seconds and then reconnected it and after a couple of minutes, the red LED came back but it also started up into the bootloader automatically...this thing just won't stay off!! I will see what happens after an hour or so but at the moment, I can't think of what else I can do to shut it off to charge it.
By the way, as I said earlier, I have now resetted everything, cleared everything and relocked my bootloader. Can I flash the unlock_code.bin I got previously from HTC or has my Token ID changed now and I need to obtain a new one? I did a Google search and it sounds like it will have now changed but I just wanna make sure.
EDIT: ok I need to go to bed now but I just realised that the reason why it won't switch off is BECAUSE it is plugged in. After unplugging it and selecting Power Down from the bootloader menu, it's now switched off. But as soon as i plug it in again, the screen lights up again. I guess i have to leave it like this and hope that it charges overnight but I'm a bit worried that it's not so good for the screen not to mention it seems to get a little warm after awhile. We'll see...
MarcusJKX said:
Yeah I guess that's the only solution then. Glad I'm not the only one!
I just got home and it looks like I was wrong. The phone's screen was off and no red LED lights were showing even though it's plugged into the wall. I disconnected it and waited a few seconds and then reconnected it and after a couple of minutes, the red LED came back but it also started up into the bootloader automatically...this thing just won't stay off!! I will see what happens after an hour or so but at the moment, I can't think of what else I can do to shut it off to charge it.
By the way, as I said earlier, I have now resetted everything, cleared everything and relocked my bootloader. Can I flash the unlock_code.bin I got previously from HTC or has my Token ID changed now and I need to obtain a new one? I did a Google search and it sounds like it will have now changed but I just wanna make sure.
EDIT: ok I need to go to bed now but I just realised that the reason why it won't switch off is BECAUSE it is plugged in. After unplugging it and selecting Power Down from the bootloader menu, it's now switched off. But as soon as i plug it in again, the screen lights up again. I guess i have to leave it like this and hope that it charges overnight but I'm a bit worried that it's not so good for the screen not to mention it seems to get a little warm after awhile. We'll see...
Click to expand...
Click to collapse
no u just have to use the old unlock unlock_code.bin ....just charge it for 1-2 hours only and flash the boot.img in the bootloader and your go to go
ll_r1d0_ll said:
no u just have to use the old unlock unlock_code.bin ....just charge it for 1-2 hours only and flash the boot.img in the bootloader and your go to go
Click to expand...
Click to collapse
Thanks a lot man. So turns out that once again, it wasn't actually charging and the phone was dead when I woke up. So then I found another thread where someone had a similar issue and this was suggested:
mevorach said:
Hi
I have a solution for you
make a batch file :
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
put this file in the directory where you have fastboot.exe adb.exe and all other
files , also put the unlock.bin file that you have from htcdev
put your phone to bootfsatusb , and run the batch file , you will see the voltage
off the battry each time it loop , after an hour or two you will have enough power(~3.68mv) to unlock it , then charge it and do what ever you want
Click to expand...
Click to collapse
I did that and left it for a couple of hours and then the battery was at a high enough level for me to get to work again. I went through everything again remembering to flash the boot.img before flashing my new ROM and now everything is working perfectly! By the way, that guide written by hasoon2000 made a mistake I think. He said to flash the boot.img AFTER flashing the new rom which I did but then still got that com.android.phone problem. But then I flashed it again BEFORE flashing CM10.1 and now everything is smooth as butter.
Anyways, thanks all for your help. I really appreciate it!
MarcusJKX said:
Thanks a lot man. So turns out that once again, it wasn't actually charging and the phone was dead when I woke up. So then I found another thread where someone had a similar issue and this was suggested:
I did that and left it for a couple of hours and then the battery was at a high enough level for me to get to work again. I went through everything again remembering to flash the boot.img before flashing my new ROM and now everything is working perfectly! By the way, that guide written by hasoon2000 made a mistake I think. He said to flash the boot.img AFTER flashing the new rom which I did but then still got that com.android.phone problem. But then I flashed it again BEFORE flashing CM10.1 and now everything is smooth as butter.
Anyways, thanks all for your help. I really appreciate it!
Click to expand...
Click to collapse
glad to know that your htc one x is running like a fire well that method is just to show the current battery level nothing else ...and i had flashed the boot.img after the room but it worked for me cux i did fix permission wipe davlik cache and partition cache too...on some roms it works for me and on some roms it doesnt..well its better if you flash the boot.img before installing the room well um glad to help you and sort out your problem

Help! Pixel 3 XL wont turn on after Android Q Beta 6 OTA Update

Hello guys.
I just bought my Pixel 3 XL phone straight from the Google Store and it just arrived two days ago. After learning about Android Q, I opted-in on the android beta and downloaded the Beta 6 OTA update to my phone. The phone downloaded the OTA and installed it and it seems all is well until the moment it rebooted. It didn't turn on again. It won't turn on. I tried to force restart it by pressing the power button 10 seconds, 30 seconds, or even 1 minute+, won't turn on, no haptic feedback, nothing. I even tried the power button + volume down combo. I also tried plugging it to the original charger it came with for 30 minutes, nothing.
Before this, I have experience with flashing stock and custom roms with pixel devices and other brands (I have owned the OG Pixel until it wont boot due to its motherboard issue), and while normally, I could have just unlocked the bootloader and installed the beta firmware thru fastboot/recovery, or even installed a custom recovery, I didn't and instead tried the OTA update thingy (which claimed that you don't have to unlock your phone or anything). I didn't expect that it will brick this early and unexpectedly.
My suspicion would be that the OTA update broke the bootloader itself, or the firmware that loads the bootloader, thus not responding to the power button correctly. It's also not a power problem, because the phone warms up when plugged to the charger. Also, I download and applied the OTA while the phone is charging (around 70%). Could that also be the culprit?
I'm at my wit's end here. I'm thinking I should RMA this phone, which I haven't done before. Are there any similar issues like this before? Did anyone else had similar issues like this one?
wincaffeine said:
Hello guys.
I just bought my Pixel 3 XL phone straight from the Google Store and it just arrived two days ago. After learning about Android Q, I opted-in on the android beta and downloaded the Beta 6 OTA update to my phone. The phone downloaded the OTA and installed it and it seems all is well until the moment it rebooted. It didn't turn on again. It won't turn on. I tried to force restart it by pressing the power button 10 seconds, 30 seconds, or even 1 minute+, won't turn on, no haptic feedback, nothing. I even tried the power button + volume down combo. I also tried plugging it to the original charger it came with for 30 minutes, nothing.
Before this, I have experience with flashing stock and custom roms with pixel devices and other brands (I have owned the OG Pixel until it wont boot due to its motherboard issue), and while normally, I could have just unlocked the bootloader and installed the beta firmware thru fastboot/recovery, or even installed a custom recovery, I didn't and instead tried the OTA update thingy (which claimed that you don't have to unlock your phone or anything). I didn't expect that it will brick this early and unexpectedly.
My suspicion would be that the OTA update broke the bootloader itself, or the firmware that loads the bootloader, thus not responding to the power button correctly. It's also not a power problem, because the phone warms up when plugged to the charger. Also, I download and applied the OTA while the phone is charging (around 70%). Could that also be the culprit?
I'm at my wit's end here. I'm thinking I should RMA this phone, which I haven't done before. Are there any similar issues like this before? Did anyone else had similar issues like this one?
Click to expand...
Click to collapse
Plug the charger in and hold all 3 buttons together, not saying it will work but worth a try, it deletes battery stats and cache, if it does boot then keep hold of them for about 40 secs, hold them for over ten seconds even try for a whole minute, this sounds like hardware fault to me though. Also, if youve just bought it, swap it.
boe323 said:
Plug the charger in and hold all 3 buttons together, not saying it will work but worth a try, it deletes battery stats and cache, if it does boot then keep hold of them for about 40 secs, hold them for over ten seconds even try for a whole minute, this sounds like hardware fault to me though. Also, if youve just bought it, swap it.
Click to expand...
Click to collapse
I have tried what you suggested. Still nothing.
If I can I'd try to resolve this without returning the thing but yeah, it may really be a hardware fault. Guess I have to wait for a miracle to happen (like the phone turning on by itself after several hours, like with some posts that I have found around).
If all else fail, maybe I'd just ask Google to replace it.
Thanks anyway :good:
You may want to try to see if you get a USB notification from your computer on Windows and if it does try to flash it Back to stock. Hope it works
Sent from my SM-G975W using Tapatalk
kentek said:
You may want to try to see if you get a USB notification from your computer on Windows and if it does try to flash it Back to stock. Hope it works
Sent from my SM-G975W using Tapatalk
Click to expand...
Click to collapse
I also have tried that to no avail. The phone won't just turn on. Anyway I already returned the device. Thanks
wincaffeine said:
I also have tried that to no avail. The phone won't just turn on. Anyway I already returned the device. Thanks
Click to expand...
Click to collapse
Have you tried making an edl cable, to see if the phone boots to qualcomm flash/diagnostic mode. I dont understand why no one in this thread as mentioned EDL mode, its a life saver for when you brick your device. This allows a full factory image flash through qualcomm flash mode. Plenty of tuturials on internet for EDL. (Emergency Download)
boe323 said:
Have you tried making an edl cable, to see if the phone boots to qualcomm flash/diagnostic mode. I dont understand why no one in this thread as mentioned EDL mode, its a life saver for when you brick your device. This allows a full factory image flash through qualcomm flash mode. Plenty of tuturials on internet for EDL. (Emergency Download)
Click to expand...
Click to collapse
Because of warranty?

Categories

Resources