Related
Ok I'm lost. I'm working today and my phone tries to reboot for no apparent reason and is put into a boot loop that I cannot get out of no matter what. In boot loader I have no recovery. Downloaded amon ra recovery's PC36IMG.zip. Booted into bootloader it said it updated the recovery but after I've rebooted I still have no recovery. I don't think this is very good.
Bootloader asked you to update and reboot and it went through completely?
Yeah, it said update was succesful. Thats why I'm so confused.
So when you go into recovery from the bootloader, do you see the triangle?
Nope just back to white screen boot loop. Trying to flash sprint lovers with the pcm36img over it maybe that will bring me back to stock rooted stat.
Edit: Back to white screen boot loop.
this same thing happened to me a week ago. were u running a cm7 rom?
yeah ex10 i was going to switch last night guess its too late
Damn I feel bad for you
I had that same problem when i first rooted and flashed my evo. I suddenly got into an infinite boot loop where i no longer had a recovery. Sorry man i had to take it to a sprint store after i tried flashing a different bootloader and then retry flashing a different recovery from clockwork to amon. and then even tried to flash the stock rom none work. if none of those work then you most likely is going to have to go to a sprint store.
Well, you could try running an RUU. This will leave you unrooted and completely stock so you will need to root again.
Here's a how-to over on Android Central.
http://forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/19278-how-unroot-return-stock.html
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Threw mine out of the window of my car and called sprint and told them I lost it. Cost me $100 to get a replacement and now I'm going to have to spend forever getting back to root and eng boot ect... sucks.
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies? Because I'm really wanting to go to the CM7 nightlies but not if the chance this is going to happen again.
ChacocII said:
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Click to expand...
Click to collapse
Does the bootloader let you run a PC36IMG.zip? If so, try running one (of a factory unrooted ROM), and when it goes to reboot and shows the green arrow facing down (if it gets that far) yank the battery at that point. I think that is when it's writing the radio image. If you can get it to that point, and then pull the battery, I'm pretty sure you'll have a brick. Aside from a battery pull during the radio flash, I'm not sure how to make a brick, without it being obvious of what you've done. You could rig your phone charger up to a 230 volt outlet from a drier or something, and plug it in. haha. maybe that would fry it, tell sprint you got a power surge when it was charging, and then it wouldnt turn on. (only 1/8 serious on that last part )
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
ChacocII said:
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
Click to expand...
Click to collapse
Damn, so you can still see s off? I have no clue how to get it to s on then, or make it so you can't even get to the bootloader. Yea, if you microwaved it (haha) i'm sure it wouldnt ever turn on again. However, whoever looks at it would be able to tell that something went very, very wrong, and it wasn't the phone's fault. ha. Maybe it won't even matter that it's s off. I've heard of people having luck with sprint looking at a phone that is s off, but I've also heard the oppositte (more often).
i actually told the sprint tech on the phone that i had rooted it and he still warranty replaced mine. im just hoping they dont change their minds when they get it back and see s-off and try to charge me 500 bucks for my new one.
Wow. Yeah, if it won't even run a PC36.img from bootloader, you're kinda SOL. That's pretty much a last resort. Granted, you should try a few different img's (different d/l sources) before assuming it's screwed. Sometimes, you can get a bad download. I had a stock Evo that wouldn't go into recovery, so I flashed a RUU from bootloader, and everything was fine. Best of luck with your replacement though, brother.
well i have 14 more days before i have to send it back. there must be some way to get it to not turn on at all without physical damage, just gotta figure it out.
Signed up for XDA because I got problems, and you guys seems to know everything when I need to use my googl-fu to solve a problem.
Have lurked for hours trying to figure this out. Nothing solves it.
Phone specs: Phone is babied, never dropped etc. Evo 4g on sprint, rooted unrevoked3 method, was running CM7 nightly95.
Have been running this for several days no issue, (since nightly95 came out.)
Was running a CM7 stable build before this. No issues.
And then the problem: Was just using my phone like normal at work it decided it wanted to reboot on me, once, restarts fine, and about an hour later reboots into a boot loop. It was on a charge cable to wall outlet, not pc when this happened, if that matters.
From the boot loop, just starts, vibrates, shows the htc evo screen maybe 10 seconds and reboots.
I can get into Hboot, (power + vol down) but can not get into recovery. if it's selected the boot looping starts again.
I have tried clearing storage, and flashing a couple PC36IMG.ZIP Since it seems to fix other peoples. Since the most I can figure out is putting the SD card into the computer and try loading files from Hboot.
Last one being this: http://forum.xda-developers.com/showthread.php?t=791019
Still boot looping, no recovery.
Any help is appreciated. But I am noob when it comes to command line adb stuff. Just so you know.
what PC36IMG are you trying to flash exactly?
try this one, its amon ra 2.3, its the one i have as a backup in case mine foks up, just take amonra out of the name so its only
PC36IMG.zip, then put in the root of your sd card, turn on phone while pressing volume down, to go into bootloader let the phone recognize it and select yes when asked to update, if thats gets your recovery up try wiping and restoring a backup
If all else fails, try the attached doc.
First, boot into the bootloader, look at the top of the screen and see if it still displays "S-OFF". If it does not, you need to re-root your device. If it displays "S-ON" then If you have a card reader, connect it to your PC or Mac and copy the contents of the SD card to your computer. Afterwards, re-format the card. Now copy a freshly downloaded rom and a freshly downloaded copy of the PC36IMG.zip file for amon-RA recovery version 2.3 to the root of your SD card (not in any folder). Re-insert the card in your EVO and boot to the bootloader. The PC36IMG.zip file *should* be automatically detected and you *should* be prompted to install it. Follow the prompts to install. Installation will take approximately 10 seconds. Afterwards, boot into your new recovery. Go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card. After that, flash the rom. Be patient during the initial boot process. You *should* be good to go afterwards.
posting & replying via the XDA Premium app.
HipKat said:
If all else fails, try the attached doc.
Click to expand...
Click to collapse
Tried this a bit ago.
Now it doesn't loop. But it's not any better.
It just boots, htc evo for a few seconds, and then vibrates approx 5 times and screen goes black and the top led flashes green.
Anybody else think this sounds like the bootloop of death? If so, there's no known fix. You can run the PC36IMG, but if that's what it is, you'll never get recovery or any rom to boot up.
I hope I'm wrong, though.
(from... Evo/MIUI/Tapatalk)
this sounds just like what happened to my phone. After spending hours on the forums and PM'ing back with a few people, I diagnosed it as the bootloop of death. Which sounds like exactly your going through....
no fix unfortunately...if your s on you can go back to sprint and get a brand new one. If not (like me) smash it pay the $100 deductible and get a refurb. Sucks I know.
For a more in depth thread search "boot loop + no recovery".
If I understand correctly, it's a problem with a partition size and was common with a certain Hardware version (0002?)
The good ole bootloop of death, that I fear so deeply. I hope this never happens to me. I'm sorry for your luck, but it sounds like plainjane is right. I agree, you got the bootloop of death, and most likely won't recover from it. Do you you have insurance ?
Sent from my PC36100 using XDA App
k2buckley said:
The good ole bootloop of death, that I fear so deeply. I hope this never happens to me.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My fear, too. Every time I boot up in the morning, I hold my breath a little til the Evo screen goes off and the boot.ani starts...
Well, After HipKat first suggestion I can get to s-on. I may try it again with a different RUU but I think it's dead too.
So, since it will be S-on, hopefully there is a new phone in my future, without any money out of pocket.
Thanks for the help guys. I'll let you know if anything fixes it, or what sprint says.
HipKat said:
My fear, too. Every time I boot up in the morning, I hold my breath a little til the Evo screen goes off and the boot.ani starts...
Click to expand...
Click to collapse
From what I remember reading about a month ago, when this seemed to be happening a lot, was that it was random.
Didn't start when you were trying to boot up, just suddenly, randomly, terrifyingly, and like death in the night....power off, and never to fully boot again. Just typing about it now kinda scares me like a hex. I hope to finish typing this sentance.
@ OP, really sorry about your luck, man. We all feel you.
Sent from my PC36100 using XDA Premium App
Thats crazy, the same exact thing happened to my brother running CM7 lke a month a go.. is this limited to just AOSP ROMs? I know there's always the potential of bricking your phone flashing, but from what I've been reading it seems its happening to lots of people on AOSP ROMs
fergie716 said:
Thats crazy, the same exact thing happened to my brother running CM7 lke a month a go.. is this limited to just AOSP ROMs? I know there's always the potential of bricking your phone flashing, but from what I've been reading it seems its happening to lots of people on AOSP ROMs
Click to expand...
Click to collapse
No, it's not limited to AOSP ROMs, but it does seem that most of the cases were people running CM7 and/or Clockwork Mod. I know there was an argument that it's just that there are so many people running CM that it just seems like CM was the culprit, but it was odd to me, anyhow, how overwhelmingly I saw that it was happening to people running that mod
HipKat said:
No, it's not limited to AOSP ROMs, but it does seem that most of the cases were people running CM7 and/or Clockwork Mod. I know there was an argument that it's just that there are so many people running CM that it just seems like CM was the culprit, but it was odd to me, anyhow, how overwhelmingly I saw that it was happening to people running that mod
Click to expand...
Click to collapse
Yea I was reading this happened a few days ago to a guy who was on Decks 2.3.4.. IDK I told my brother to just flash a radio and pull the battery while flashing to try and get a replacement.. But the whole thing freaked me out lol.. Feel bad cuz it could happen to anyone I suppose
Your lucky to get S-ON, I only read about one other person able to get S ON after bootlooping.....take it to the Sprint Store, they should give you a new one on the spot if they have stock, if not they order one overnight. Could have been way worse...
Right now it says s-off again. But acts likes it's on, can't erase anything through fastboot/adb.
Going to try to repeat the RUU install a few times to see if I can get it back to s-on then take it in.
I was one of the first 3 or so people to report about this on the forum - it happened to me over 4 months ago. Anyways, if you flash a PC36IMG-eng and pull the battery at exactly the right time, while the radio is updating your phone will completely brick - it won't even turn on. Then you can take your phone in and just tell sprint it wont turn on. Note, it took me over 20 battery pulls before it finally wouldn't turn on, but its your best option if you can't get S-ON.
Wow that's crazy. I've never heard of the bootloop of death.
Sent from my PC36100 using Tapatalk
Do a search for Boot loop white screen and you'll find a ton of threads/posts about it
So I thought I would give up my inexperienced life of flashing and possibly bricking my device(sent it in to get jtag repaired), so I attempted to put it back to stock. I got odin up and running, Downloaded(for the most part) the tar that would make it stock again. about 98% into the flashing it failed and made me a little nervous. I later remembered to flash the kernel, and with it, the phone booted up. Fine and dandy one day yadda yadda yadda.
Now comes day 2, and it just randomly turned off and booted again. it got to the little android boot screen, then shut down again, rinse repeat at different times of the boot process, add in some random shutdowns when I'm at the home screen and using my phone and there you have it.
I figured it was using an unfinished stock rom trying it's best to function, so I tried to put in clockwork mod. I did, but it was very difficult as I navigated through clockwork recovery, the phone would select things on its own, making the rooting process a giant pain. With that monkey on my back, I managed to root and install the juggernaut v.5 rom(which totally rocks) to see if the probably persists. The end result was it still happened, but when it didn't, I was able to work with it normally. At this point in time, I am trying to keep my phone turned on because if for a second the screen shuts off, the phone will start trying to shut itself down and game over. This is still very very annoying and was wondering if you fine people would happen to point someone thats green as grass with this stuff in the right direction
s1yfox said:
So I thought I would give up my inexperienced life of flashing and possibly bricking my device(sent it in to get jtag repaired), so I attempted to put it back to stock. I got odin up and running, Downloaded(for the most part) the tar that would make it stock again. about 98% into the flashing it failed and made me a little nervous. I later remembered to flash the kernel, and with it, the phone booted up. Fine and dandy one day yadda yadda yadda.
Now comes day 2, and it just randomly turned off and booted again. it got to the little android boot screen, then shut down again, rinse repeat at different times of the boot process, add in some random shutdowns when I'm at the home screen and using my phone and there you have it.
I figured it was using an unfinished stock rom trying it's best to function, so I tried to put in clockwork mod. I did, but it was very difficult as I navigated through clockwork recovery, the phone would select things on its own, making the rooting process a giant pain. With that monkey on my back, I managed to root and install the juggernaut v.5 rom(which totally rocks) to see if the probably persists. The end result was it still happened, but when it didn't, I was able to work with it normally. At this point in time, I am trying to keep my phone turned on because if for a second the screen shuts off, the phone will start trying to shut itself down and game over. This is still very very annoying and was wondering if you fine people would happen to point someone thats green as grass with this stuff in the right direction
Click to expand...
Click to collapse
I suggest you Odin back to stock. Here is a good guide to Odin back to GB stock:
http://forum.xda-developers.com/showthread.php?t=1513359
Heres a link to Odin back to ICS stock:
http://forum.xda-developers.com/showthread.php?t=1705565.
You can use this App to root your phone afterwards:
http://forum.xda-developers.com/showthread.php?t=1650908
I personally used this thread to Odin CWM then flashed SU later:
http://forum.xda-developers.com/showthread.php?t=1311194
Hope this helps!!
Thanks!
LoopDoGG79 said:
I suggest you Odin back to stock. Here is a good guide to Odin back to GB stock:
http://forum.xda-developers.com/showthread.php?t=1513359
Heres a link to Odin back to ICS stock:
http://forum.xda-developers.com/showthread.php?t=1705565.
You can use this App to root your phone afterwards:
http://forum.xda-developers.com/showthread.php?t=1650908
I personally used this thread to Odin CWM then flashed SU later:
http://forum.xda-developers.com/showthread.php?t=1311194
Hope this helps!!
Click to expand...
Click to collapse
You have definitely earned my thanks for providing such hearty solutions! I am super paranoid now when it comes to downloading files like those. my major concern is if the files never download completely :O I followed what was in that first thread to tooth, and as I installed that md5 towards the end I got a giant fail. regardless, I thank you for the awesome support man:good:
Hmm, try reflashing your recovery. Mount your USB (If you cant, take out your SD card, and mount it on your PC) and place this file on the root of your SD card( Just easier to find this way)
http://sourceforge.net/projects/darksidetools/files/SGH-T989_ClockworkMOD_5.0.2.7.zip/download
Flash it, and restart recovery. Your recovery should act normal, and do a clean install of whatever ROM you wish. By the way, Juggs was my first DD (daily driver) to!!
Superwipe?
LoopDoGG79 said:
Hmm, try reflashing your recovery. Mount your USB (If you cant, take out your SD card, and mount it on your PC) and place this file on the root of your SD card( Just easier to find this way)
http://sourceforge.net/projects/darksidetools/files/SGH-T989_ClockworkMOD_5.0.2.7.zip/download
Flash it, and restart recovery. Your recovery should act normal, and do a clean install of whatever ROM you wish. By the way, Juggs was my first DD (daily driver) to!!
Click to expand...
Click to collapse
that wouldn't happen to be darkside super wipe would it? I just tried it out, and I have the same issue :S
I just re downloaded the stock rom file you flash with odin, but haven't tried it out yet. I really hope it works :/
s1yfox said:
that wouldn't happen to be darkside super wipe would it? I just tried it out, and I have the same issue :S
I just re downloaded the stock rom file you flash with odin, but haven't tried it out yet. I really hope it works :/
Click to expand...
Click to collapse
Lol, no its CWM 5.0.2.7 or aka, CWM non-touch, I got that link from TDJ's OP, he so kindly provided us a link for it. From your OP, it sounds like CWM did not flash correctly, you can flash a recovery within a recovery, you just have to restart it or reboot your phone for it to take into effect. Do you have the T989 or T989D?
lets see
LoopDoGG79 said:
Hmm, try reflashing your recovery. Mount your USB (If you cant, take out your SD card, and mount it on your PC) and place this file on the root of your SD card( Just easier to find this way)
http://sourceforge.net/projects/darksidetools/files/SGH-T989_ClockworkMOD_5.0.2.7.zip/download
Flash it, and restart recovery. Your recovery should act normal, and do a clean install of whatever ROM you wish. By the way, Juggs was my first DD (daily driver) to!!
Click to expand...
Click to collapse
LoopDoGG79 said:
Lol, no its CWM 5.0.2.7 or aka, CWM non-touch, I got that link from TDJ's OP, he so kindly provided us a link for it. From your OP, it sounds like CWM did not flash correctly, you can flash a recovery within a recovery, you just have to restart it or reboot your phone for it to take into effect. Do you have the T989 or T989D?
Click to expand...
Click to collapse
its an sgh t...lets see if 5.0.2.7 can help me :S
no dice man
it still keeps on restarting even after the clockwork
s1yfox said:
it still keeps on restarting even after the clockwork
Click to expand...
Click to collapse
Did you do a clean install? Darkside Superwipe, flash ROM, reboot, wait ten minutes, then reboot?
Sent from AOKP Goodness :-D
Yeah unfortunately it is still randomly rebooting....washing lol
An update to this: all the same symptoms occur, but for some reason when I flashed darkside rom 3 the symptoms occurred less! For example, last night I was able to use this device for 4 hours straight without it acting up. I really wonder what the problem is. I. Mean the thing acts like an angel when in Odin mode, but when it comes. To cwm or anything else it tends to spaz out.
I too have this happening now. I don't know why its been doing it. I was running the latest aokp and than it started rebooting and shutting off. So I went back to my nandroid backup and still continues. Running darkside v7, and problem is still there. Anyone know why this is happening?
It started happening while listening to music.
Here's a logcat, I used catlog right before it shut down. I cannot comprehend what it is trying to say, hopefully one of you can help me out. Thank you.
http://db.tt/kf1iiWqt
Sent from my SGH-T989
Calz- said:
Here's a logcat, I used catlog right before it shut down. I cannot comprehend what it is trying to say, hopefully one of you can help me out. Thank you.
http://db.tt/kf1iiWqt
Sent from my SGH-T989
Click to expand...
Click to collapse
Im beginning to suspect our power buttons may be at fault here.
s1yfox said:
Im beginning to suspect our power buttons may be at fault here.
Click to expand...
Click to collapse
That's exactly what I was thinking. Everytime I would lock my phone with the power button it'll turn off and stay black vibrating. When I lock my phone using screen off and lock app it won't turn off but to unlock it I have to use the power button, than it turns off.
Sent from my SGH-T989 using xda app-developers app
Calz- said:
That's exactly what I was thinking. Everytime I would lock my phone with the power button it'll turn off and stay black vibrating. When I lock my phone using screen off and lock app it won't turn off but to unlock it I have to use the power button, than it turns off.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Bingo. The moment that I touch the power button my phone freaks out and shuts down. If you don't have the stones or craftiness to fix it yourself, you can join me in getting the power button replacement on mobile tech videos
s1yfox said:
Bingo. The moment that I touch the power button my phone freaks out and shuts down. If you don't have the stones or craftiness to fix it yourself, you can join me in getting the power button replacement on mobile tech videos
Click to expand...
Click to collapse
So I went to a T-Mobile store earlier and they told me they can't replace my phone because I'm rooted and they think its the rom, even tho I showed them.
I have to odin flash the original stock rom and go back to T-Mobile to get it replaced.
Know any way you can flash back without an internet connection on a computer?
Sent from my SGH-T989 using xda app-developers app
s1yfox said:
So I tried to put in clockwork mod. I did, but it was very difficult as I navigated through clockwork recovery, the phone would select things on its own, making the rooting process a giant pain. With that monkey on my back, I managed to root and install the juggernaut v.5 rom(which totally rocks)
Click to expand...
Click to collapse
In the non touch clockwork recovery use menu to scroll down. Home to scroll up. Back to go back. And search to select. I figured it out by my power button clicking things.
Sent from my SGH-T989 using xda app-developers app
Calz- said:
So I went to a T-Mobile store earlier and they told me they can't replace my phone because I'm rooted and they think its the rom, even tho I showed them.
I have to odin flash the original stock rom and go back to T-Mobile to get it replaced.
Know any way you can flash back without an internet connection on a computer?
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
the only way i know how is through odin. I've done it a few times. at the end of the flashing I find that the phone turns itself off or something which marks it down in odin as a FAIL..when in actuality it flashed....it just needs a kernel flash and it'll all be candysticks and lollipops.
At this point in my phones life though, however, it is increasingly harder to do anything in clockwork since the button is fudged up. I think I might have to pony up 35$, but if you can Odin your phone back to flash and tell T-Mobile/Samsung about it, you can probably get the repair for free
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
I brought my phone in to have the charger port replaced. It worked fine ad then all of a sudden the phone boots up, stays booted for a minute and then reboots. also the screen is unresponsive.
I have used a gnex kit to get into CWM and erase cache and dalvik cache and fix permission and the problem is not resolved.
with out the gnex kit i can't even get into CWM and all i get is a little droid guy with an open stomach hatch with a red mark.
i would erase all data and factory reset as a last option but i have some work photos on the device that are extremely important for me to extract. I should also mention that with the CWM kit I am unable to find the files I wish to pull yet for the few seconds I am able to boot into android my photos are there in the album.
can someone please help me find a way to extract those files so I can try to wipe the device and move on?
cardozanick said:
I brought my phone in to have the charger port replaced. It worked fine ad then all of a sudden the phone boots up, stays booted for a minute and then reboots. also the screen is unresponsive.
I have used a gnex kit to get into CWM and erase cache and dalvik cache and fix permission and the problem is not resolved.
with out the gnex kit i can't even get into CWM and all i get is a little droid guy with an open stomach hatch with a red mark.
i would erase all data and factory reset as a last option but i have some work photos on the device that are extremely important for me to extract. I should also mention that with the CWM kit I am unable to find the files I wish to pull yet for the few seconds I am able to boot into android my photos are there in the album.
can someone please help me find a way to extract those files so I can try to wipe the device and move on?
Click to expand...
Click to collapse
With factory reset your sdcard will not be touched. You will have all your files (unless youre in stock recovery I think). You can use adb pull /sdcard/ to get all youre files.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
With factory reset your sdcard will not be touched. You will have all your files (unless youre in stock recovery I think). You can use adb pull /sdcard/ to get all youre files.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
so what you're saying is if I boot into CWM with the kit, do a factory reset, all my photos will be there? can you please elaborate?
cardozanick said:
so what you're saying is if I boot into CWM with the kit, do a factory reset, all my photos will be there? can you please elaborate?
Click to expand...
Click to collapse
Yes that is correct. You can wipe everything as long as you dont wipe /sdcard. I am not a 100% sure since you are on stock but I know sure for 99%. Google is your friend
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Yes that is correct. You can wipe everything as long as you dont wipe /sdcard. I am not a 100% sure since you are on stock but I know sure for 99%. Google is your friend
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Alright,
alright, we have 50% success!
I was able to get all the files off that I was looking to get, albeit during 20 second intervals in which the phone would allow me to before rebooting....
which brings me to my next point - Phone is stuck in bootloop after following (successfully) this guide to flash stock and unroot which, needless to say, seems strange to me.
Now I supposedly have a fully formatted i9250 maguro with a fresh flash of stock running and i'm stuck in a boot loop which if i leave sitting long enough will eventually get to the "Welcome" [choose your language] screen with an unresponsive display panel until it reboots after about 30 seconds.
please help.
EDIT: I flashed the Factory Image Android 4.2.2 (JDQ39) and still stuck in bootloop with unresponsive screen. maybe this is better as a paperweight??
cardozanick said:
Alright,
alright, we have 50% success!
I was able to get all the files off that I was looking to get, albeit during 20 second intervals in which the phone would allow me to before rebooting....
which brings me to my next point - Phone is stuck in bootloop after following (successfully) this guide to flash stock and unroot which, needless to say, seems strange to me.
Now I supposedly have a fully formatted i9250 maguro with a fresh flash of stock running and i'm stuck in a boot loop which if i leave sitting long enough will eventually get to the "Welcome" [choose your language] screen with an unresponsive display panel until it reboots after about 30 seconds.
please help.
EDIT: I flashed the Factory Image Android 4.2.2 (JDQ39) and still stuck in bootloop with unresponsive screen. maybe this is better as a paperweight??
Click to expand...
Click to collapse
Thats strange. But you have your files and you are on completely stock unrooted. If you still have warranty you can send it back. Maybe you can try this: http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Sent from my Galaxy Nexus using XDA Premium HD app
Strange Fix reveals deeper issue
good news and bad news
Alright, so I have swapped the motherboard with an old gnex i had laying around that has a broken screen that wouldn't turn on at all..
I found out that the motherboard on the old phone must be dead because it won't work in the newer phone so I put the guts of the newer on into the broken screen phone and it worked perfectly - albeit with a huge crack in it. so i then thought maybe the issue was solved and put the guts that worked back into the original phone and it is unresponsive and reboots... I've come to the conclusion that the screen is the issue on that device.
but is this fixable??? i have taken the whole thing apart and can't see how that screen could be shorting the device and cause it to reboot nor can i understand why it wouldn't be responsive to the touch for no reason.
anybody have a clue how i can fix that?