For the past several months my phone would restart randomly when I used 3G, GPS or sometime just from heavy usage. It would turn off, boot to the white HTC screen but then the screen went black and it would vibrate 3 times and a led would blink. At that point the only way to turn it back on was to pull the battery and power on (although that usually didn't work until after a few tries or letting it sit for a while).
It has done this with both CM7.1 and decks 1.3 and with the Tiamat 3.3.7 & 4.1 kernels. I flashed Mason .14 on Tuesday hoping it might fix the problem. It did at first but after 24 hours it was back to restarting randomly, only this time it was worse. I was also getting a lot of force closes and it would restart even it was sitting unused. It would take hours until I could get it to successfully boot again. I attempted to do a full wipe and install CM7.2 yesterday only to find out I can not boot into recovery, attempting to do so causes the phone to turn off (I tried both through holding the power button and selecting recovery and through the bootloader).
As of right now my phone will not turn back on at all (going on 4 hours), I've had it successfully boot twice only to immediately turn off, other times it gets stuck on the white HTC screen.
I am still able to access the bootloader so I'm thinking my best option may be to place a PC36IMG.zip on my sdcard and see if I can't flash back to stock and then load CM7.2. My concerns are a) not sure if that will even work b) if the phone were to turn off in the middle of that would it completely brick my phone?
Sorry for the long post but I just wanted to provide as much info as possible. Any thoughts/suggestions would be greatly appreciated.
Can't boot into recovery? Have you tried reflashing your recovery? Get a PC36IMG file of your desired recovery (preferably amonRA, or drellisdee) and flash it thru bootloader. It only takes a second to flash, so I wouldn't be too worried about it shutting off while flashing it.
That's all I got.
Sent from my PC36100 using xda premium
scottspa74 said:
Can't boot into recovery? Have you tried reflashing your recovery? Get a PC36IMG file of your desired recovery (preferably amonRA, or drellisdee) and flash it thru bootloader. It only takes a second to flash, so I wouldn't be too worried about it shutting off while flashing it.
That's all I got.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Unfortunately that doesn't work. Flashes the recovery just fine but I still can't access it. I did manage to get my phone to boot into android after trying, not sure if that's a coincidence or not.
So I'm left with my original option, flashing a stock PC36IMG.zip. Also this might be a dumb question but can I rename anything PC36IMG.zip and flash? If so I could just rename Calkulin's format all, flash that and then repeat the process with CM7.2. Anyone know if this will work?
Edit: Should probably also ask if anyone knows what is causing this, is it a kernel issue?
Just a thought, maybe a bad battery or a bad usb?
Did you try the battery in another phone? Or, another battery in your phone?
Sounds like it may also be going for the reboot of death... If your recovery is corrupted and getting random reboots, maybe your internal storage is going bad...
Sent from my PC36100 using xda premium
imheroldman said:
Just a thought, maybe a bad battery or a bad usb?
Did you try the battery in another phone? Or, another battery in your phone?
Sounds like it may also be going for the reboot of death... If your recovery is corrupted and getting random reboots, maybe your internal storage is going bad...
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I was able to flash back to stock and it is still having similar problems. Turns off during any sort of data usage both 3g and Wifi. The fact that it has happened on multiple ROMs, multiple kernels, and multiple radios makes me think it is something hardware related. I guess I will talk to sprint and see what they can do.
BTW does anyone know of a method to flash an S-On zip file as a PC36IMG in the bootloader? I am still S-Off because I can't go into recovery to flash.
mcotter said:
BTW does anyone know of a method to flash an S-On zip file as a PC36IMG in the bootloader? I am still S-Off because I can't go into recovery to flash.
Click to expand...
Click to collapse
Well after going back to stock but still being S-Off I decided to try reflashing Amon_RA and I eventually got it to boot into recovery. It was similar to booting into the OS, I just had to pull the battery and wait 30+ mins before trying and then boot into bootloader and select recovery. It was a PITA since I needed flash a couple things but it worked. Got it back to S-On and took it to Sprint. Of course they didn't bother checking for any of that haha but I was able to get a replacement EVO.
Related
Ok, so here is my story:
I rooted way back in July right after I got my Evo, so I started on Android 2.1. I flashed and used OMJ's ROM for quite a while until I discovered Cyanogen mod, which I switched to after trying OMJ's 2.2 ROM.
I used CM6 for a long time, eventually flashing some nightly builds, culminating in nightly build number 140. At some point in this process, I started having real trouble with bootlooping CONSTANTLY (and I couldn't even make a nandroid backup because it would reboot inside the backup process). I eventually got it to stop bootlooping after many many reboots and wipes (full wipe, cache wipe, dalvik wipe) and restarts and got CM to boot.
I just now flashed CM6.1 and started getting constant bootloops again. I assumed it was a problem with CM, so I decided eff it, I'm going with a different ROM and downloaded Calkulin's EViO 1.5 rom to try, but it can't boot either.
I can get to the android screen, which displays no signal, then it reboots. I can't get out of this cycle. When I was on CM, I had issues with starting up - I had to hold down the power button quickly and press airplane mode, then it would reboot again, but it would come all the way up. Then once it was fully booted I could disable airplane mode and it would stay online. After that point, I just decided never to reboot the phone, but this is a huge problem that I can't figure out how to fix.
I have tried wiping using Clockwork and Amon Ra, but neither makes a difference.
Any help would be GREATLY appreciated. Thanks!!!
it reboots while making nandroid? So even if you hold vol down + power and go to the recovery from there it is rebooting?
xHausx said:
it reboots while making nandroid? So even if you hold vol down + power and go to the recovery from there it is rebooting?
Click to expand...
Click to collapse
Correct, I hold volume down + power to get into recovery, then choose nandroid and backup, then while it is creating a nandroid backup, it reboots.
Does anyone have any ideas? At this point, I have no clue what to do, and I can't boot into any ROM.
If you Google it you'll see its an incredibly common problem not just with those of us who have modded our phones but those with stock roms who have never done so it happened to me when I originally flashed cm6 to my phone as well but it eventually fixed itself if you can get it to boot try factory reset it may help
Sent from my PC36100 using XDA App
hackulous said:
If you Google it you'll see its an incredibly common problem not just with those of us who have modded our phones but those with stock roms who have never done so it happened to me when I originally flashed cm6 to my phone as well but it eventually fixed itself if you can get it to boot try factory reset it may help
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Factory reset just wipes your data using your recovery doesn't it? Either way, I've tried that, and no dice.
I mean, I guess at the very least I could try to bring the phone into Sprint... is there a shipped RUU I can flash so they can look at it?
edit: found the latest RUU (http://forum.xda-developers.com/showthread.php?p=8474707)
I'm gonna try this and see what happens.
http://www.google.com/m/url?client=...IQFjAA&usg=AFQjCNHQ2016xLF_DLz7uVoilk8Hm1EsRg
Sent from my PC36100 using XDA App
same problem. no solution. i am now fully bricked, aka i reboot before i can pull down lockscreen (rom changes, unroot, nothing works) return before it gets so bad you cant unroot.
No good man I hope you got insurance
Sent from my PC36100 using XDA App
Ewe, thats no good. I would use the ruu but Do Not Use The Newest One. You will lose root and the new 3.30 people are having trouble rooting
Sent from my PC36100 using XDA App
same thing happening to me. Stuck in bootloop now, started out as just a random reboot that would boot than reboot than hold for a while. Right now im completely stuck in bootloop =(.
Is there a way to put a stock rom on my phone with just booting to recovery?
These sound like hardware issues but if your recovery is working fine then it may be something else. Did you try the RUU while in the recovery?
Just don't use the newest one
Sent from my PC36100 using XDA App
dkdude36 said:
same problem. no solution. i am now fully bricked, aka i reboot before i can pull down lockscreen (rom changes, unroot, nothing works) return before it gets so bad you cant unroot.
Click to expand...
Click to collapse
I was finally able to get to a point where I could get it to boot - here is what I did.
I wiped everything using amon ra's recovery, then flashed the latest cyanogen mod from here: http://mirror.teamdouche.net/get/supersonic/update-cm-6.1.0-RC1-Supersonic-signed.zip, then when it booted, it would get constant bootloops, but it would get to the home screen for a few seconds each time.
You have to click through the intro menus reaaaallly freakin fast so you see the desktop with the live wallpaper. DON'T sign into a google account. It will probably bootloop again, and if it doesn't, quickly hold down the power button and select airplane mode. If it reboots again, it will power up completely successfully in airplane mode. Then make sure you're in an area of good signal and disable airplane mode until you have 3G, and then sign into a google account. If it starts bootlooping again, quickly hold the power button and press airplane mode - you can always boot successfully in airplane mode for some reason...
xHausx said:
These sound like hardware issues but if your recovery is working fine then it may be something else. Did you try the RUU while in the recovery?
Just don't use the newest one
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It could be hardware related, but I'm not 100% sure at this point...
The reboots seem to be correlated with signal strength. If I have 1 bar of signal (in CM, so not cell signal), it will reboot before it gets to 3G.
Also any flash on a website reboots the phone for some reason. I don't know if that's common or not.
Hey folk,
My buddy & I both have EVO 4G's, I rooted mine yesterday, downloaded rom manager did a backup and than downloaded a rom and everything went smooth no problems.
Now today I rooted by friends phone the same way I did mine, when It came to doing a backup or downloading a rom, every time it goes to reboot after the rom is downloaded or you do a backup, it will reboot and than all you see is the white screen and it showing the evo 4G logo.
I don't know what I did wrong? the root went successful and everything else is fine.
Any help folks thanks.
How long is it staying on the splash screen? Sometimes it can take a few minutes.
Is it stuck on the splash screen or can you get it up & running?
teh roxxorz said:
How long is it staying on the splash screen? Sometimes it can take a few minutes.
Click to expand...
Click to collapse
It was stuck on the splash screen for about 15 min or so than the battery died.
plainjane said:
Is it stuck on the splash screen or can you get it up & running?
Click to expand...
Click to collapse
It stays stuck on the flash screen it won't move, last it was running for 15 min on the splash screen and than the battery died, so I plugged it in to the charger and powered it up and it was still the stock rom but still was rooted.
2005blkgto said:
It stays stuck on the flash screen it won't move, last it was running for 15 min on the splash screen and than the battery died, so I plugged it in to the charger and powered it up and it was still the stock rom but still was rooted.
Click to expand...
Click to collapse
First thing: don't try to flash anything with a battery lower than 35%. It might be okay at levels lower than 35%, but it's better to be safe. You don't want to be flashing something after a wipe & the phone shut off.
Second: for some reason after rooting my phone, it takes a lot longer to reboot than it used to. This isn't something that always happens but it does some times. The first couple times it would even get stuck on the splash screen & I'd eventually pull the battery. I found that after I switched to amon ra recovery it stopped happening. You could try switching recoveries, but if you do rom manager won't function anymore & you'll have to do everything manually. It's not difficult.
Try again, this time with a full battery, and see what happens. Make sure cwm says that the flash was successful. If it takes a really long time to reboot, pull the battery & power it on normally. Sometimes it takes a while after wiping/flashing because it has to rebuild cache and/or load the rom for the first time, but it shouldn't take 15 minutes.
plainjane said:
First thing: don't try to flash anything with a battery lower than 35%. It might be okay at levels lower than 35%, but it's better to be safe. You don't want to be flashing something after a wipe & the phone shut off.
Second: for some reason after rooting my phone, it takes a lot longer to reboot than it used to. This isn't something that always happens but it does some times. The first couple times it would even get stuck on the splash screen & I'd eventually pull the battery. I found that after I switched to amon ra recovery it stopped happening. You could try switching recoveries, but if you do rom manager won't function anymore & you'll have to do everything manually. It's not difficult.
Try again, this time with a full battery, and see what happens. Make sure cwm says that the flash was successful. If it takes a really long time to reboot, pull the battery & power it on normally. Sometimes it takes a while after wiping/flashing because it has to rebuild cache and/or load the rom for the first time, but it shouldn't take 15 minutes.
Click to expand...
Click to collapse
Every said was correct. But I'd like to add, that its possible that it didn't wipe fully. The screen should never hang on the splash for 15 minutes...five is normal, and sometimes happens after flashing. But like plainjane said, try another wipe. Also, flashing under 35%, it'll flash, but if your phone dies midway, expect to have a fancy paper weight.
plainjane said:
First thing: don't try to flash anything with a battery lower than 35%. It might be okay at levels lower than 35%, but it's better to be safe. You don't want to be flashing something after a wipe & the phone shut off.
Second: for some reason after rooting my phone, it takes a lot longer to reboot than it used to. This isn't something that always happens but it does some times. The first couple times it would even get stuck on the splash screen & I'd eventually pull the battery. I found that after I switched to amon ra recovery it stopped happening. You could try switching recoveries, but if you do rom manager won't function anymore & you'll have to do everything manually. It's not difficult.
Try again, this time with a full battery, and see what happens. Make sure cwm says that the flash was successful. If it takes a really long time to reboot, pull the battery & power it on normally. Sometimes it takes a while after wiping/flashing because it has to rebuild cache and/or load the rom for the first time, but it shouldn't take 15 minutes.
Click to expand...
Click to collapse
teh roxxorz said:
Every said was correct. But I'd like to add, that its possible that it didn't wipe fully. The screen should never hang on the splash for 15 minutes...five is normal, and sometimes happens after flashing. But like plainjane said, try another wipe. Also, flashing under 35%, it'll flash, but if your phone dies midway, expect to have a fancy paper weight.
Click to expand...
Click to collapse
Thanks Guys I will give it another try, but I would also like to men-son nothing gets flashed, the phone reboots - black screen than white screen and thats all.
When I did the same thing to my EVO the white screen stayed for about 40 secs and than started flashing.
I will try to remove rom manager and reinstall it.
So I am still having trouble with my friends EVO, it stays on the splash screen and won't change it lasted for an hour and than I pulled the battery.
Nothing happen to phone.
When I try to unrevoke it, it asks me if my version is new and reboots.
Even when I try to go to clockwork it gets stuck on the splash screen.
What am I doing wrong?
does anyone not have an answer for this?
2005blkgto said:
does anyone not have an answer for this?
Click to expand...
Click to collapse
I'm not sure this will help you, but if it were me, I would download unrevoked's s-on zip and flash that. Then get the PC36IMG.zip for the Stock unrooted 3.70 OTA and install that so you will be completely back to stock and unrooted.
Then try to root again. Also, try Amon Ra since clockwork was giving you trouble.
jstalford said:
I'm not sure this will help you, but if it were me, I would download unrevoked's s-on zip and flash that. Then get the PC36IMG.zip for the Stock unrooted 3.70 OTA and install that so you will be completely back to stock and unrooted.
Then try to root again. Also, try Amon Ra since clockwork was giving you trouble.
Click to expand...
Click to collapse
I would recommend this as well, link: http://forum.xda-developers.com/showthread.php?t=884060
jstalford said:
I'm not sure this will help you, but if it were me, I would download unrevoked's s-on zip and flash that. Then get the PC36IMG.zip for the Stock unrooted 3.70 OTA and install that so you will be completely back to stock and unrooted.
Then try to root again. Also, try Amon Ra since clockwork was giving you trouble.
Click to expand...
Click to collapse
Heaterz16 said:
I would recommend this as well, link: http://forum.xda-developers.com/showthread.php?t=884060
Click to expand...
Click to collapse
Thanks I will give it a try.
One more question, the link you gave me, which one should I use being there is multiple links.
Thanks
Tried to do the recovery and same issue I can not get into clockworks so I am basically stuck, If I goto recovery it will just get stuck at the white splash screen.
I am really lost at what to do now
2005blkgto said:
Tried to do the recovery and same issue I can not get into clockworks so I am basically stuck, If I goto recovery it will just get stuck at the white splash screen.
I am really lost at what to do now
Click to expand...
Click to collapse
Can you boot into your ROM at all?
^^^^^
No not at all.
If I power down than press volume down and power it will take me to the screen where I can goto to recovery but when I select it and try to go to recovery it will reboot and show the white splash screen that says EVO 4G and thats it, it will just stay there.
If I try to download a ROM or do a Backup and when it reboots to the same white splash screen it will just stay stuck there.
It looks to me the phone is partially rooted cause wireless tether, superusers, rom manager works but when I tried to download titanium so I can do the unroot and wipe the data clean titanium won't work.
At this point I have read a-lot of other posts and tried many other things but they all require me to go into clockworks which I can't. I even tried another method I seen on Youtube but I can't find unrevoked on my EVO anywhere.
I mean can you boot your phone up normally, and from the looks of it you can. You just need to reflash your recovery. Boot your phone up, go into ROM Manager and hit flash clockwork. After doing that, choose the flash alternate recovery option to flash Amon Ra and then do all your ROM flashing through recovery and not through ROM manager from here on out.
_MetalHead_ said:
I mean can you boot your phone up normally, and from the looks of it you can. You just need to reflash your recovery. Boot your phone up, go into ROM Manager and hit flash clockwork. After doing that, choose the flash alternate recovery option to flash Amon Ra and then do all your ROM flashing through recovery and not through ROM manager from here on out.
Click to expand...
Click to collapse
I will try this tonight.
Thanks
On Saturday I was running cyanogenmod 6.1 on my phone, and I had gone through some of the files and deleted some of them. From what I understood, if something went wrong, you could just re flash the ROM. I was watching a Youtube video and my phone had one of those random shutdowns. It started back up at the splash screen, and I expected it to continue on into the ROM. After the splash screen it just shut off and restarted. I though it was just since I deleted HTC Copyright apk, so I would re flash the ROM. I went into H-BOOT, and hit recovery, and then the phone just shut down and started to reboot. I knew it was bad, so I put PB31IMG.zip on my phone that contained clockwork recovery. I then booted into clockwork, and it worked for 2 seconds and then the phone shut off. I flashed an earlier version to try again, and same thing. I tried to use different recoveries and they haven't worked either. Is there anything else that I can do to fix it after this point.
Sincerely
Cubusmybro
AFAIK you flash the PB31IMG.zip in H_BOOT, not recovery.
It's people like this that make the manufactures and service providers hate this community. You didn't know what you were doing, and you ****ed up your phone. You cant just go and delete things. Learn what youre doing before you do anything.
I did flash it through H-Boot, but the recovery wont stay up for more then 2 seconds without shutting down.
If you have s-on and 7.28 radio you can go to dougpiston.com and dowload stock RUU. Rename it PB31IMG.zip. H-boot then volume up to update.
Sent from my ADR6300 using XDA App
Nah
Your phone is not bricked if ti was bricked it wouldn't even turn on so you still have hope first thing i would do is try to return to stock and unroot http://forum.xda-developers.com/showthread.php?t=786436&highlight=stock
my htc inspire hd is stuck on hboot screen.. everytime i boot it up the screen is frozen and it says it cant find the pd98 file. so i looked through this thread to find some answers:
http://forum.xda-developers.com/showthread.php?t=1386387
i did everything i could and put the pd98 in the root of the sd card and then it got to the point where it still cant find the pd98diag.zip and .nbh file but it finds the pd98img and starts to load. then its just gets stuck on the parsing screen.. i rooted my phone a while back using ace hack kit so i could unlock the phone. this issue came out of no where, i was just using my phone and looking at nba scores and it just freezes so i pull out the battery and now this happens...
sjafar92 said:
my htc inspire hd is stuck on hboot screen.. everytime i boot it up the screen is frozen and it says it cant find the pd98 file. so i looked through this thread to find some answers:
http://forum.xda-developers.com/showthread.php?t=1386387
i did everything i could and put the pd98 in the root of the sd card and then it got to the point where it still cant find the pd98diag.zip and .nbh file but it finds the pd98img and starts to load. then its just gets stuck on the parsing screen.. i rooted my phone a while back using ace hack kit so i could unlock the phone. this issue came out of no where, i was just using my phone and looking at nba scores and it just freezes so i pull out the battery and now this happens...
Click to expand...
Click to collapse
can you access the recovery by going into the hboot, if so, all you need to do is flash a ROM from scratch, or restore a back up
no i cannot click on hboot, it just automatically reads the sd card and then loads the p98 file and gets stuck on parsing.
http://forum.xda-developers.com/showthread.php?t=1396253&highlight=hboot
ive been trying to follow this guide but i put the pd98 file from the first link on the sd card then boot up my phone and the phone is still stuck but reads the pd98 file and gets stuck on the parsing screen again and all it says is [1] recovery.
also i dont know if it helps everytime i power on my phone it automatically goes to hboot screen, i dont have to hold the volume down button.
Have you tried removing the p98 zip from the sdcard and then booting into recovery from the bootloader? or removing the sd card completely, and then powering on the phone?
yeah without the sd card when i try to turn it on it goes to the hboot screen and just stays there, i cant move up or down and with the sd card without the pd98 file, the phone looks for pd98img twice and doesnt find it and then looks for pd98 file and doesnt find it and then goes back to hboot screen
and thanks for getting back to me man and trying to help out!
I came across someone else with this issue not that long ago. Unfortunately your ribbons running to your volume keys, or other related hardware, have become damaged or failed prematurely and your volume key is indefinitely stuck down. The only way to fix this would be to replace the failed part yourself. The inspire is difficult to take apart and requires a special tool to remove the camera so warranty may be your best bet.
do you know how much repairs like that usually cost professionally?
If you have at&t, its free for your first one to braeak, it has to be software, so they won't know that its the volume rocker is broken. Because what it mostly looks like is software.
Sent from my Inspire 4G using XDA App
well i cant send it to att bc i didnt buy it from them, bought from a third party. is there a place i can order the parts and do it myself?
also maybe its a volume rocker problem bc if i hold the volume up button with the powerbutton it vibrates a couple of time and the led stays solid green but the screen remains blank. doesnt that show the rocker still works bc the combination of the volume and power triggered a different response then just pressing the power and the phone going into hboot?
hboot
i have a wierd situation. when i go into hboot, it vibrates like heck and it finally gets on. i can chose recovery and it vibes like crazy but it eventually does load. i get to cwm and i can do all the operations. wipe data, partitions etc etc. i install from zip card and it is successful. i reboot phone and it vibes like crazy and eventually the zip does work and the rom is flashed. i just found it peculiar that my hboot is screwy, but i can still flash roms, wipe data, go to recovery and etc. do i have anyting to worry about, or should i just stick with the screwy hboot? idk how to fix the hboot . any suggestions or insight would be surely appreciated.
chrisb906 said:
i have a wierd situation. when i go into hboot, it vibrates like heck and it finally gets on. i can chose recovery and it vibes like crazy but it eventually does load. i get to cwm and i can do all the operations. wipe data, partitions etc etc. i install from zip card and it is successful. i reboot phone and it vibes like crazy and eventually the zip does work and the rom is flashed. i just found it peculiar that my hboot is screwy, but i can still flash roms, wipe data, go to recovery and etc. do i have anyting to worry about, or should i just stick with the screwy hboot? idk how to fix the hboot . any suggestions or insight would be surely appreciated.
Click to expand...
Click to collapse
You have a froyo hboot. Just flash a gingerbread one and all will be normal again. Best thing to do is just use a PD98IMG.
Sent from my Nexus 7 using xda premium
k
Gizmoe said:
You have a froyo hboot. Just flash a gingerbread one and all will be normal again. Best thing to do is just use a PD98IMG.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
i tried your gizroot and it worked. but when irebooted the device, i got what ihad before. a crazy long vibrate and back to hboot. i managed to get to recovery and flash the android revolution. im afraid of rebooting device as it will probably get stuck again.
i have run out of patience. lol. how do i flash that image. ?every time i load bootloader it says that it cant load pd98 image. its actually been that way ever since i rooted my phone.
Here is a PD98IMG of the gingerbread hboot. I've tried this one and know it should work. Just give your phone time to recognize it.
http://db.tt/jwhkWYHz
Sent from my Nexus 7 using xda premium
First off, S-off phone
So, I've been running the GPE rom posted by Joel for a while now with no issues... Today a friend wanted to see the phone, so I pulled it out of my pocket; hit power; nadda...
So I held power down for a while; got teh HTC screen; then nadda.
So we then attempted to get into recovery, power + vol down then selected recovery... Nadda, just a black screen.
I then redownloaded TWRP and fastboot flash recovery recoveryname.img, it tries to push it then it'll throw an error saying: "remote: image update error"
I looked around and found a thread with full directions with an RUU.. So I tried doing that, hwoever after clearing the cache via fastboot, when I try to do fastboot oem rebootRUU nothing happens.... sometimes teh screen goes blank, sometimes not.
Anything else I can try? I'm really wondering if it isn't defective hardware... .only had it 2 weeks too...
You are sure the phone is fully charged right ?
Sent from my Nexus 7 using Tapatalk 4
dottat said:
You are sure the phone is fully charged right ?
Click to expand...
Click to collapse
i was going to say the same thing. not sure how but i sometimes pull the phone out of my pocket with the screen on... so who knows which programs could have been tapped and running if it's bumping around in your pocket.
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
wireroid said:
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
Click to expand...
Click to collapse
Guess I should have put more details in the first post... when I got it into TWRP the first time it showed an 88% charge. I attempted to restore a backup and inside the recovery it would say it failed reading the memory and then it couldn't browse anything.
If I attempted to simply factory reset inside the recovery it would just lock up. If I tried to flash a rom via zip, it would lock up...
After a few times of rebooting it into the recovery I couldn't even click anything inside it without locking up.
it was at that point I tried to flash a different recovery and started getting the errors...
Anyways, more I researched it simply was a bad phone with defective hardware.
all good...