HELP: Can't boot/enter recovery - One (M8) Q&A, Help & Troubleshooting

Hi all, hopefully someone can help, I was using my phone fine earlier when all of a sudden it just switched off, wouldn't turn back on at all. After trying for a while I've gotten into fastboot. I've tried booting into recovery but no luck.
I've since tried wiping cache - no effect. Flashing recovery - 'FAILED (remote: image update error)'. Boot recovery image - reports success, does nothing.
I'm S-ON, was on a custom ROM. Anyone offer any advice?
Thanks.

Also, the phone doesn't seem to stay turned off now, keeps booting itself into fastboot.

What the model of the phone
Sent from my GT-I9195 using XDA Free mobile app

It's a UK One M8.

After a couple of hours of messing around with no luck it's now just turned on. No idea what that was about. Afraid to turn it off now!
If anyone sees this and does have advice I'd still appreciate it, feel like I'm probably on borrowed time...

top_bunk said:
After a couple of hours of messing around with no luck it's now just turned on. No idea what that was about. Afraid to turn it off now!
If anyone sees this and does have advice I'd still appreciate it, feel like I'm probably on borrowed time...
Click to expand...
Click to collapse
have you had custom rom, recovery or root installed before?

I've only had this phone a month or so, rooted it pretty much straight away and installed Viper ROM. Left it alone since then waiting for Lollipop.
If you just mean experience wise, I've rooted all my phones for years, never had one randomly turn off for no reason and refuse to enter recovery though (thankfully), usually when I have issues its cos I did something daft!

Half way through Christmas day the phone froze up, completely unresponsive. Once the battery had died and I could turn it on again I was back to where I was, can't boot up, can't get to recovery, fastboot won't flash a new recovery, get the same failed message as last time.
Anyone got any ideas?

top_bunk said:
Half way through Christmas day the phone froze up, completely unresponsive. Once the battery had died and I could turn it on again I was back to where I was, can't boot up, can't get to recovery, fastboot won't flash a new recovery, get the same failed message as last time.
Anyone got any ideas?
Click to expand...
Click to collapse
you could try this
http://android-revolution-hd.blogspot.com/2014/09/how-to-fix-random-reboots-on-htc-one-m8.html

Thanks clsA. I'll take a look at the link...
The phone started working again late last night though, again no reason, just did. I took the opportunity to update the recovery, do a full wipe and install a new ROM. Hopefully I won't see the same issue again, if I do I'll try out that fix.
Thanks!

Related

[Q] Boot Loop with No Recovery

So before everyone yells because of my inability to search the forum, please understand that not only have i searched this forum, but just about every other one. And if someone finds a thread with an answer to my question than i will admit defeat and have myself stoned and crucified.
I will greatly appreciate anyone's and everyone's help.
History in cliffnotes
Rooted with Unrevoked about a month ago, since then been running CM 6.
Have been happy with just using stock CM 6 and nothing else, haven't flashed any other kernels, radios, or for that matter roms.
Have always had problems with random reboots but didn't care.
Last night my phone appeared to have the desire to random reboot, and on start up got into a boot loop, just HTC splash boot loop. I can get into bootloader but if i try to go to recovery it is just more boot loops.
I'm running mac OS X however i eventually just tried running RUU on my roommates computer but to no avail, mostly, i think, because my phone can't boot into a state where its recognized by the program or sync, etc...
The real problem
As of now i've gone as far as basically completely unrooting, using a pc36img that i found through you guys here
So if you guys have any ideas, at this point, i'm completely willing to try them because, this was completely random that it happened, and i really am at a complete loss as to what to do besides buy a new phone.
i love you all in a masculine plutonic way. thanks.
well you could always re-root with unrevoked. all it needs is bootloader mode to root it and then once its done, flash a rooted rom on it, then proceed to unroot.
EDIT:
btw, i am a mac user too and unrevoked works great. if it fails, run it again. and no need to use an ruu, look up a thread in our development section titled shpped roms and they have pc36img versions of the ruu. you will be able to root with your mac and unroot all on the device. unrevoked has an s-on zip on their web page. to unroot it, flash the s-on zip then run the pc36img zip from the base of your sd card. thats all!
EDIT#2:
YOU CAN ALWAYS FLASH A RECOVERY VIA BOOTLOADER ALSO AND FLASH A ROM. LET ME KNOW WHICH RECOVERY YOU PREFFER, I GOT BOTH CLOCKWORKMOD AND RA.
EDIT#3: LOL, Sorry i didnt see that you mentioned a pc36img to unroot.
why dont you just download download the recovery img of amon_ra 2.2.1 in pc36img format and run it from boot loader. done, problem solved.
if that doesnt work download caukulins format all zip and run it and them reload your recovery and rom
t3project said:
why dont you just download download the recovery img of amon_ra 2.2.1 in pc36img format and run it from boot loader. done, problem solved.
if that doesnt work download caukulins format all zip and run it and them reload your recovery and rom
Click to expand...
Click to collapse
I am not trying to thread jack, but i too am having the same problem. I am not a noob at flashing and I am stuck at the white Evo screen and it just reboots when I click on recovery from the boot loader.
I too have flashed the recovery image from amen ra and it flashed ok, but each time I reboot and try to get into recovery it just reboots, so that did not fix getting into recovery.
The problem with the above suggestion is that you need to be able to boot into a recovery to use Caukulins format all zip, and if you can't get into recovery it does no good.
If anyone has any other suggestions please let the both of us know!
Well since you can't get into recovery, we suggested to flash a recovery in pc36img.zip format in bootloader mode.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!
paulieb81 said:
I am not trying to thread jack, but i too am having the same problem. I am not a noob at flashing and I am stuck at the white Evo screen and it just reboots when I click on recovery from the boot loader.
I too have flashed the recovery image from amen ra and it flashed ok, but each time I reboot and try to get into recovery it just reboots, so that did not fix getting into recovery.
The problem with the above suggestion is that you need to be able to boot into a recovery to use Caukulins format all zip, and if you can't get into recovery it does no good.
If anyone has any other suggestions please let the both of us know!
Click to expand...
Click to collapse
thats why i said flash a recovery in pc36img format first. more specifically this:
http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
rename to pc36img.zip and boot into bootloader
t3project said:
thats why i said flash a recovery in pc36img format first. more specifically this:
http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
rename to pc36img.zip and boot into bootloader
Click to expand...
Click to collapse
If you read my message you will see that I DID flash a recovery, that same one you just linked, and it flashed ok, but when i restart and choose to enter the recovery the phone just reboots again!
Did you solve this?
Yes I did, I went back to the store and had them replace the phone. I could not get it to boot into recovery for some reason.
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
ChacocII said:
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
Click to expand...
Click to collapse
Did they give you any problems about s-off being visible in the bootloader when you got your phone replaced? I'm to that point of taking it back with the EXACT same problem but I didn't know if it was an issue. (or is there any trick to get s-on back without being able to load into recovery i.e. a fastboot command?)
i was worried about the s-off as well because i also was unable to change that. all i could find for that was the s-on tool but since u cant actually flash anything, had to leave it s-off. i even tried a battery pull during the radio update on a pc36img so that they wouldnt be able to get to bootloader but i couldnt even brick it. i live more than 50 miles from a sprint store so they didnt make me drive to a sprint store. they sent me a replacement and i mailed my evo back. on the paperwork for the new phone they said i could still be charged 75 dollars for a recoverable phone and 125 for an unrecoverable phone. it was probably 2 weeks ago or so when i sent my old broken evo back and i havent been billed yet so i dont know what if anything they will charge. when i talked to the sprint tech on the phone i told him it was rooted because i knew they would see the s-off and i didnt want to get screwed when i sent them my broken phone and they said "u rooted, ur problem" but he said he would still replace it and he did.
k2buckley said:
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm in the same boat buckley. I don't get it?! I did run cm for a couple days but I was always looking at my phone wondering if something was going to happen. Almost gave myself a panic attack so I just went back to sense, lol.
ChacocII said:
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
Click to expand...
Click to collapse
And I just wanted to say, that although you've seen 5, and I've seen around 10, and that does suck, that the fact is, that this is an EXTREMELY low percentage of CM users that are experiencing this problem. With that noted, it's still enough for me to use a different rom, at least until someone can at least figure out what caused that to happen. I am just extremely curious, as to what the actual malfunction with the device is, when this sort of things happens. And why it seems to only be happening on CM. (at least from the reports I've seen around here)
Add me to the list of people with this problem. I think I'm going to try my chances at the Sprint store. They've been good to me so far.
k2buckley said:
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It has nothing to do with CM. It is clearly a hardware problem. It has happened on other roms, but more likely to happen to someone using CM as it is the most used Rom.
Sent from my PC36100 using XDA Premium App
Sorry to open this again, but I'm having the same issue. I'm actually on the HTC Sensation, but I'm posting this here because after hours of searching, this is the ONLY place that seemed to address this seriously.
The reboots began even on the original stock rom. I bought it from a guy on Craigslist, but I'm fairly certain it was the original stock rom, with S-off, unrooted, etc. I thought flashing other roms would help, but they haven't.
Here's my furthest observations thus far:
I have actually found a way to get out of this incessant boot loop. As you said, even recovery is impossible. I was so confused when everyone kept telling me to just go into bootloader mode and go to recovery. I can always get into bootloader mode, but recovery, as you guys said, is pointless, because it just boot loops.
However! I have found that if I leave the battery out for an extended period of time, maybe an hour to several hours later, upon inserting the battery back in, I'm able to load up correctly. But that doesn't last long. Usually I only get one chance. If I use that chance to go into recovery mode the next time it'll just boot loop again.
So now I really think it's something to do with the battery, because when I leave it out for a while, I can finally boot up the phone or get into recovery. I do know that HTC has that lame battery problem of boot looping when the battery is low, so do you guys think that it could be related to the battery stats? When my next "battery-free shift" is over, I'm going to try charging the phone and wiping battery stats.
Sometimes the other way I can get out of the boot loop is to charge the phone fully until it's green, so I'm just not sure. This is insane... any input at all would be greatly appreciated..
jkxklutz said:
Sorry to open this again, but I'm having the same issue. I'm actually on the HTC Sensation, but I'm posting this here because after hours of searching, this is the ONLY place that seemed to address this seriously.
The reboots began even on the original stock rom. I bought it from a guy on Craigslist, but I'm fairly certain it was the original stock rom, with S-off, unrooted, etc. I thought flashing other roms would help, but they haven't.
Here's my furthest observations thus far:
I have actually found a way to get out of this incessant boot loop. As you said, even recovery is impossible. I was so confused when everyone kept telling me to just go into bootloader mode and go to recovery. I can always get into bootloader mode, but recovery, as you guys said, is pointless, because it just boot loops.
However! I have found that if I leave the battery out for an extended period of time, maybe an hour to several hours later, upon inserting the battery back in, I'm able to load up correctly. But that doesn't last long. Usually I only get one chance. If I use that chance to go into recovery mode the next time it'll just boot loop again.
So now I really think it's something to do with the battery, because when I leave it out for a while, I can finally boot up the phone or get into recovery. I do know that HTC has that lame battery problem of boot looping when the battery is low, so do you guys think that it could be related to the battery stats? When my next "battery-free shift" is over, I'm going to try charging the phone and wiping battery stats.
Sometimes the other way I can get out of the boot loop is to charge the phone fully until it's green, so I'm just not sure. This is insane... any input at all would be greatly appreciated..
Click to expand...
Click to collapse
If its anything like the evo you might want to try and wipe cache and dalvik cache when you get into recovery let it boot back up if that doesn't work try to fix permission if that doesn't work wipe battery stats when your phone is at 100% using battery calibration app and if none of that works do a full wipe and flash a new ROM or unroot and run the ruu of the stock ROM .
Sorry I know nothing about that phone so IDK if any of that will work for you just trying to help and those are pretty much the steps I would take.
Sent from my PC36100 using XDA App
Happened to me
Hey guys this happened to me and i was running cm and sense roms i have had alot of experience with this and its an actual glitch that causes the os to stack on each other and confuse the boot the only way to fix is to wipe the entire phone back to stock if that dosent work call sprint and they gladly replace ur phone due to manufacture defect its been happening to unrooted phones also from the updatesnot being installed properly phone needs to be wiped every time u do a new rom

Rolling Restarts

I've done some research on this and haven't found and answer, so im putting it out there for you guys to get at me and let me know. I have been experiencing Rolling restarts on my phone. The phone will boot up fully, but randomly it will just restart it self. At times if I just push the power button, to turn of the screen, the phone will restart again. The phone also has an issue of staying in black and not coming back on, so I have to take the battery out in order for me to get it back to boot up.
Notes:
Im running EL29 Stock. Nothing special at all.
If there is a thread already created for this, I apologize, but ive looked and I couldn't find it.
I'm experiencing something similar except i'm running AGAT's tFH13 rom and kernel.
Every time I get the phone into recovery or even download mode, the phone just reboots itself.
Out of curiosity I opened the mobile odin app and it gave me an error saying it could not detect the device model. -_-
bas85 said:
I've done some research on this and haven't found and answer, so im putting it out there for you guys to get at me and let me know. I have been experiencing Rolling restarts on my phone. The phone will boot up fully, but randomly it will just restart it self. At times if I just push the power button, to turn of the screen, the phone will restart again. The phone also has an issue of staying in black and not coming back on, so I have to take the battery out in order for me to get it back to boot up.
Notes:
Im running EL29 Stock. Nothing special at all.
If there is a thread already created for this, I apologize, but ive looked and I couldn't find it.
Click to expand...
Click to collapse
Can you dump a logcat and attach?
(From ADB Shell)
Code:
logcat -d -f /sdcard/logdump.txt
Might help explain what's going on.
bas85 said:
I've done some research on this and haven't found and answer, so im putting it out there for you guys to get at me and let me know. I have been experiencing Rolling restarts on my phone. The phone will boot up fully, but randomly it will just restart it self. At times if I just push the power button, to turn of the screen, the phone will restart again. The phone also has an issue of staying in black and not coming back on, so I have to take the battery out in order for me to get it back to boot up.
Notes:
Im running EL29 Stock. Nothing special at all.
If there is a thread already created for this, I apologize, but ive looked and I couldn't find it.
Click to expand...
Click to collapse
That's pretty odd, I don't think I've ever heard of something like that happening unless there was something physically wrong with your phone.. have you ever tried to use Odin to reinstall a stock Rom? & out of curiosity do you have an antivirus app?
I did the Reflash back to stock through odin. Took it to sprint this morning though and found that it was a bad battery. So easy fix but annoying problem.
And with that being said, It did it to me again! Guess that wasn't the issue.
j7jman said:
That's pretty odd, I don't think I've ever heard of something like that happening unless there was something physically wrong with your phone.. have you ever tried to use Odin to reinstall a stock Rom? & out of curiosity do you have an antivirus app?
Click to expand...
Click to collapse
I have used Odin to reinstall a stock rom before. I do have an Antivirus app called Lookout. It might be something physically wrong with the phone at this point im not sure what to do.
*update* Just took it back to sprint and they replaced it for me for free. Went from black to white
I've been trying to flash it back to stock to take it to sprint but my phone just keeps rebooting even whilst in recovery mode. :-\
Sent from my cm_tenderloin using Tapatalk 2
bas85 said:
*update* Just took it back to sprint and they replaced it for me for free. Went from black to white
Click to expand...
Click to collapse
How long have you had your phone? I am having the exact same issues. My 1 year Samsung warranty expires on the 15th...
Was your phone rooted when you brought it in?
twoslo said:
I've been trying to flash it back to stock to take it to sprint but my phone just keeps rebooting even whilst in recovery mode. :-\
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
I would say keep trying. Mine was doing that too but it finally held out long enough once to not restart on me. What I did was i just tapped the screen ever 10-15 seconds. Not sure if that did anythign or if I was lucky but It made it through.
MoMatt said:
How long have you had your phone? I am having the exact same issues. My 1 year Samsung warranty expires on the 15th...
Was your phone rooted when you brought it in?
Click to expand...
Click to collapse
I had my phone for less than a year. I had a sprint warranty and the Samsung 1 year warranty. Both covered this issue with no problem. I suggest taking it in if you cant find a solution to the problem. But if your rooted. Flash back to stock.
I was able to restore to a previous backup. From there i got Mobile Odin working and was able to flash the FH13 OTA, rooted though. I still can't get the power button to work and its still randomly rebooting but not as often. Still trying to get the phone to STAY in download mode to flash to stock(unrooted) with Odin.
twoslo said:
I was able to restore to a previous backup. From there i got Mobile Odin working and was able to flash the FH13 OTA, rooted though. I still can't get the power button to work and its still randomly rebooting but not as often. Still trying to get the phone to STAY in download mode to flash to stock(unrooted) with Odin.
Click to expand...
Click to collapse
You can possibly take the "risk" but I took mine that was a Rooted Stock version, and it passed their software test, so they gave me the new phone. Also if its rebooting as much or as fast as mine was, Its hard for them to even run a real test because the phone wont give them a chance to. Its up to you tho to make that decision.
Finally got the phone to stay in download mode and i was able to flash the Unrooted FF18 OC.
Reboots are fewer now but power button still doesn't work. I checked my account and my phone is still under 1 year warranty & i have the insurance. I'll be heading to sprint after work today.
Thanks for your tips and replies. :good:
Same issue. The power button on this phone is iffy. At least i think that's the problem
Swyped from a Galaxy S2 on CM10
update : they are replacing my phone because the power button is broken
It's gonna be a few days till I get the new one, tech says they are back ordered?
The stability and shutdown issues for me seem to be caused by a bad battery. Brought it into Sprint and they gave me a new one, no charge. Seems to have solved the problem.

***Emergency Thread*** Here To Help!

I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!
In case of emergency!
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Rayman0625 said:
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Click to expand...
Click to collapse
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
...Awesome... said:
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Sv: ***Emergency Thread*** Here To Help!
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
lintz said:
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Phone wont boot without the battery in, and with it in I cant stay in recovery without with rebooting.
Rayman0625 said:
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Click to expand...
Click to collapse
Even better then lol just test it out at work. I'm about 80% its your battery specially if you OV/UC.
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
heartspains88 said:
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
Click to expand...
Click to collapse
after you odin, you need to wipe data/ factory reset to boot. If you can't get into recovery ( Power, Home Button, and Volume Up), then try reflashing your stock image in Odin and check your MD5 sum, so you can rule out a bad download
Thanks for the reply, I'm re-downloading the stock rom now to verify it's integrity and do a new flash. I cannot get into recovery, so we will see after the new flash. Pleading ignorance on one subject, how would I go about checking the MD5 sum to verify the file has no issues?
Additionally I did try to Odin recovery and still could not boot into it, this was however before attempting to re-download and flash a stock rom again.
**Edit//Update** Re-downloaded and flashed stock rom, was able to get into recovery and wipe, booted up fine.
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
frettfreak said:
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
Click to expand...
Click to collapse
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Towle said:
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
frettfreak said:
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
Click to expand...
Click to collapse
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Flashing stock with Odin can take up to ten minutes its normal like the man said above just let it do its thing
Towle said:
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Worked great! Thanks!!
http://forum.xda-developers.com/showthread.php?t=2113883
Let's see if you have any solution for me?
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
ohshootrawr said:
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
Click to expand...
Click to collapse
Do u happened to have apps that control frequency like setcpu etc? They might be conflicting each other
Sent from my HTC One S using Tapatalk 2

[Q] Nexus 7 suddenly bricked ?

Hello all, so yesterday I went on my tablet (Nexus 7 2013 WIFI ver.) and browsed the net a bit and went to sleep. I recall having around 30% battery power. This morning I wake up to an apparently flat battery (power button didn't turn on anything) so I just plugged it in and did something else. After a while, I took my tablet and started it with the power button. However, it got stuck on the Google logo and never fired up anything. I've rooted the tablet quite some time ago (months) so the cause is not from there.
Things I haven't recently done:
Installing an app.
Rooting or flashing anything.
Updating an app.
Things I have tried doing to fix the problem:
Booting into FASTBOOT then trying the recovery mode = still stuck on the Google logo.
Booting a custom recovery image using Wug's toolkit = frozen at the team logo (TWRP) / black screen (CWM).
Flash Stock + Unroot (Soft-Bricked/Bootloop) = FAILED (flash write failure).
So now I'm really stuck and desperate to make the device work again. I've been reading all day long and trying all sorts of solutions to no avail. And it seems far-fetched to me for a device like this to just instantly brick itself without any reason at all.
Can anyone help me with this case ? Or does anyone has any idea what just happened to my tablet ? :crying:
EDIT: I'm afraid that warranty might not work as the device was unlocked and rooted so it's the last solution for me.
Bumpity bump
No one has any idea what happened to the tablet and how to fix it ? I've tried doing some more flashing but to no avail. It just refuses to flash and keeps failing to write the files.
I think you need to leave out on the charger for 1/2hr without doing anything with it. You are probably using what little power it has charged by trying to reboot it, etc.
I had to do that once and it did the trick.
Sent from my Nexus 7 using XDA Free mobile app
There is no reason you should not be able to get in to recovery (power and volume down).
You could call Motorola. They have good tech support.
The exact same thing happened to me. I rooted it months ago and haven't changed a thing since then. It just froze up a few days ago. I restarted and it just gets stuck on the google screen. I can get into the bootloader, but when I try to go to recovery, the google screen comes up and won't go away. I've tried every method I can find for flashing the stock image and absolutely nothing is working. I just get stuck on the google screen.
Please update this if you find a solution!
Do u guys have the most up to date version of whatever particular recovery that you're on?
Yep. I've flashed the stock recovery multiple times to no avail. :/
nexusjas said:
Yep. I've flashed the stock recovery multiple times to no avail. :/
Click to expand...
Click to collapse
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Have you tried to see if your computer sees your N7 by typing fastboot devices if you have the sdk installed?
wantabe said:
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Click to expand...
Click to collapse
Not what I wanted to hear, but you're probably right. Thanks :/
nexusjas said:
Not what I wanted to hear, but you're probably right. Thanks :/
Click to expand...
Click to collapse
I was to slow with my update. Does your computer see your N7 with fastboot?
wantabe said:
I was to slow with my update. Does your computer see your N7 with fastboot?
Click to expand...
Click to collapse
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
nexusjas said:
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
Click to expand...
Click to collapse
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
wantabe said:
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
Click to expand...
Click to collapse
I'm not sure what happened, but I just ran this little utility again (I've done it many times over the last week or so to no avail) and it actually worked. Hopefully it keeps working!
Thanks for your help!

stuck on LG boot screen not rooted

Hey guys my verizon g4 is stuck in bootloop and im not rooted, i cant get the past the lg boot screen, it stays on their for around 20 seconds goes black and back to lg screen.
I can get into recovery but none of the options do anything ive tried safe mode, usb debug mode i even tried factory reset they all just go back to the lg screen.
I was just watching a video on facebook when it froze restarted and now im stuck, ive been restarting it all day and i was able to get it to boot up twice but it froze again within seconds any help is appreciated
it might be the defective motherboard issue that people are having. you could try reflashing the system, but if that doesn't work you probably need a new motherboard/phone
Not an answer, but an experience.
I have an HTC ONE M8, VZW. I s-offed it and rooted it right when I got it. I began adding some of my google apps and it did what your G4 is doing, stuck on VZW screen.
Since I was s-off I was able to get a recovery in and ready. I was able to get a custom rom onto the phones external sd. I flashed it with the recovery and the flash took, no more vzw screen lock up.
Your experience makes me wonder what VZW is doing to force bootloops on unlocked or rooted phones with their retail products. Paranoid maybe, but I can see VZW deliberately adding code to stick it to rooted users.....................................I say this still knowing that many have rooted the current run of devices without issues...........................
luck
i read about the problems with the motherboard going bad, im assuming thats what happened to mine. Lg sent me a replacement under warranty
Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.
killa408shark said:
Update!
i called verizon they sending me a replacement. just to let you know i flashed 13B KDZ but the bootloop was still there i let my phone on and finally turned on quickly i did a factory reset and booted up normal and its working again. still im gonna send it back. just sharing my experience maybe for other people might work too.
Click to expand...
Click to collapse
What is the 13B KDZ and how did you flash it? Im having same exact issue.
My G4 tanked over the weekend. I was browsing news and the phone locked up, then it shut off and turned back on. It just bootloops now. If I stick it in the freeze for a few minutes, sometimes it will boot to the OS where it starts to optimize the apps. It will get through about 20 before it shuts off and starts the bootloop process again. I haven't even been able to get the download mode to stay on, and when it does enter download mode, it is not detected by the computer. I think my problem is the motherboard. I'm just hoping that they aren't able to figure out I had it rooted!
I'm still waiting to hear back from Verizon about a replacement.
Does anyone have any ideas on how I can flash a stock rom back on this thing to try to save my tail? I am betting not since the phone won't stay on long enough to even flash the rom.
b3y0ndd34th said:
My G4 tanked over the weekend. I was browsing news and the phone locked up, then it shut off and turned back on. It just bootloops now. If I stick it in the freeze for a few minutes, sometimes it will boot to the OS where it starts to optimize the apps. It will get through about 20 before it shuts off and starts the bootloop process again. I haven't even been able to get the download mode to stay on, and when it does enter download mode, it is not detected by the computer. I think my problem is the motherboard. I'm just hoping that they aren't able to figure out I had it rooted!
I'm still waiting to hear back from Verizon about a replacement.
Does anyone have any ideas on how I can flash a stock rom back on this thing to try to save my tail? I am betting not since the phone won't stay on long enough to even flash the rom.
Click to expand...
Click to collapse
+
My phone was rooted and got into the bootloop also and I sent it in as is and nothing happened. So I think it would be fine to send it without the stock rom.
mainlygreen said:
+
My phone was rooted and got into the bootloop also and I sent it in as is and nothing happened. So I think it would be fine to send it without the stock rom.
Click to expand...
Click to collapse
Thank you for this information, this makes me feel a little better!
The replacement is already in the mail!
same issue of mine I was out then it cut off & wouldn't come back on but now it charges up & makes it to the boot screen
b3y0ndd34th said:
Thank you for this information, this makes me feel a little better!
The replacement is already in the mail!
Click to expand...
Click to collapse
did you send the faulty unit first or they are sending it on your complaint. I am outside US and my G4 got bootloop issue n i was wondering how to get the replacement through somebody as i wont be coming for another year.
thanks
bhuvesh89 said:
did you send the faulty unit first or they are sending it on your complaint. I am outside US and my G4 got bootloop issue n i was wondering how to get the replacement through somebody as i wont be coming for another year.
thanks
Click to expand...
Click to collapse
They mailed me a new one, no battery, no back. I put my battery, sim card, sd card, and back on the new phone, fired it up. Rolled it back, rooted it, then I mailed the old one back.
Personally, I love this phone, but I think I will be getting a nexus next.

Categories

Resources