Ok my phone has been reverted to unrooted stock for weeks. The only modded thing is s-off. today my phone just shut down and will lock up, shut down (and require a battery pull to restart) before booting fully or wake up once the screen goes dim.I get the lock screen then black when i slide it down. Since i was full stock i don't know what to do. I don't have clockwork so i don't have backups, can someone please help.
General Thread is thattaway _----->
sorry
they can delete this. I got it to work by pulling my sd card. sorry for misplacing it. I was afraid of s-off causing this or prohibiting me from getting my phone fixed and thought s-off was a development issue.
Related
This just crossed my mind; so IF my HTC Desire's screen would break and i would want to send it back for repair, how could i unroot it without being able to use the screen (let's assume the screen is totally f'd up)?
Thanks in advance!
If your device does power on, but you just can't see the screen, you can go into fastboot (power on whilst holding Volume-Down, wait 15 seconds for the sd card to "initialize" and press power) and run an RUU. You won't see whats going on but you can watch your computer for info on the restore process.
I hope this didn't happen to you, because that would really suck. Let's keep it a thought, shall we?
No worries, it hasn't happened to me, i just dreamt of that scenario
Thanks for the reply!
It happened to me... got the dreaded SLCD brick
made a mistake with framework-res.
device stuck in boot screen
Clockworkmod refused to restore the backup it created. Stuck with no other backup
Clockworkmod refused to flash any custom rom. Dont know why but always said signature verification failed.
Downloaded a RUU and flashed it... but turned out it bricked the LCD.
Then Downloaded another RUU and thankfully it restored the device to stock state.
Moral of the story: If you root, always have nandroid backup. If nandroid restore fails and you dont have any other backup, it will be a tough time ahead....atleast till you learn lessons like me..
i had a minor fall and checked if my phone was ok. it could boot in the splash screen and boot animation then i just shuts down. i suspected that i was low on batt.At home, i tried to charge it but nth happens. no charging sign or whatsover. Could not enter bootloader or anything. Just wondering if i would loose my root if i send it to HTC or will they just fix the hardware prob? Hoping for a quick reply thx
Chances are they'd fix it and put official software back on it as they'd turn the phone on to make sure it's working. Can't be sure though
Would they service the device if it's rooted?
Asking because I'm not willing to S-OFF my device should I ever need to use the warranty. However, if I don't have problems with having it serviced, I might give it a try
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
This is the hspa version.
svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!
This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!
I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.
Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.
I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/
Hi
Strange occurrence today. Turned on phone--nothing. Reset battery and it booted fine, but after awhile (when the screen timed out) it went back to black. When I turn it on it goes to dark blue (BSOD?) but nothing else happens, however as soon as I reset the battery, it will boot successfully and as long as the screen is on, the apps seem to work etc. As soon as I lose the screen, I lose the phone again. Volume down followed by power switch brings up the same BSOD.
The lcd is on and the phone is apparently charging regardless.
Can anyone help get me back in business?
Thanks
Are you using a custom rom of any kind, rooted etc. giving details like this helps people answer questions.
My advice is if you are useing a custom rom then backup your apps etc. then redownload the rom and flash it as new then recover your apps.
here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
ender127 said:
here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
Click to expand...
Click to collapse
there was an ota update a bit ago, 4.3...um, is it under warranty or does she have insurance, if so, go to the sprint techs and have them look at it, if not, what you can do/try for it is to completely flash the 4.3 ota update again using odin and download mode...you can do this by clicking on the 2nd link in my signature and see what happens, fixed my phone like this after 4.3 and myself messed it up lol and it's the exact same thing the sprint techs would do for it if you brought it in
so there's your options man...good luck, any questions just post up but the guide is very simple and straight fwd to follow and I provided all that is needed in my download bundle from my dropbox account
edit...if you can't boot up to enable the usb debugging mode, it should still work but it's recommended to do but again, shouldn't really matter, as long as it boots into download mode you should be ready to go
ender127 said:
here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
Click to expand...
Click to collapse
This isn't an uncommon problem with the S3. I just recently went through this. In my case, and in many other cases, it's a faulty motherboard. Nothing you can do to fix it other than get Sprint to replace the handset.
For me, if I left it completely off for a long time, when I turned it back in it was stable for a couple of hours. Not sure if it was a coincidence, happened a couple of times that way.