I had Android 4.1.1 installed on a rooted Sprint Galaxy S3 with ClockworkMod. Someone recommended TWRP, so I installed it and used the backup feature, thinking I was completely covered if my foray into ROM flashing on the SGS3 went awry.
So I booted to TWRP, did a "Wipe Data/Factory Reset", and installed the "Blazer" ROM; didn't like it. So I TWRP'ed again, wiped it and flashed CyanogenMod 10.1. Didn't like it either. So I went back into TWRP, did the "Wipe Data/Factory Reset" again, and restored my backup.
When it finished rebooting, it was good for like 20 seconds. I left it on the "lock" screen, and the date reverted back to Dec 24th at some ungodly hour (4 am?). It wouldn't unlock. After less than a minute, it reboots. It kept doing this.
I had a hard time getting back *into* TWRP. I kept getting this weird picture of the battery (?) and the phone kept buzzing every 10 seconds or so. The battery had at least 30% charge. Eventually, by taking the battery out, I was able to get back into TWRP.
Tried it again 2 or 3 more times with the same result. This last time, I immediately got off the lock screen and let it "sit". It has been stable for 10 hours now.
Any idea what's going on?
(If I'm leaving out important information, I apologize. Please let me know and I'll add it.)
Something wrong happened in the restore process. Just make sure that you have at least 80% battery next time.
Sent from my SPH-L710
Thanks.
If I keep restoring it over and over again, is there a chance it will "take" one of these times?
Ok so, check the size of your backups and make sure that they are consistent (for the same ROM types)
I've seen an issue where someones recovery got corrupted, and all restores made with the corrupted recovery were unnaturally small and would bootloop once done restoring
Reflashing your recovery (i recommend through ODIN from a PC) should fix it if this is the issue
Related
Hey all, first time poster. I wrote a real nice explanation of my problem, but i lost it so anyways, i'll keep it short(ish).
The EVO is less than 3 weeks old, running the latest OTA, recently rooted using UnrEVOked 3, nothing fancy. I ran the battery down completely last night (first time since i got the phone) and once i got to a power source, it wouldn't boot correctly. It hangs at the white splash screen, and then finally boots up but won't respond to any touch input.
Also the phone seems to be running exceedingly slow, the boot process takes substantially long than normal once it gets past the splash screen and my live background is freezing and seems to be stuttering.
I launched into the bootloader and i get a "Touch Panel - Fail". LAME!
I'm not sure what to do at this point, whether i should wipe it or go back to stock or what. Any advice would be much appreciated.
UPDATE:
I managed to get the phone into the recovery console, make a back up (i was planning on going back to the stock image) and wipe the dalvik cache and fix permissions. I rebooted and voila! fixed. Hopes this helps any one else who has this problem.
Moral of this story: Travel with a charger.
Another update. It froze up again in the middle of sending a text. I rebooted by battery removal, and it did the same thing again. Super long splash screen and sluggish boot up, no touch response when it finally came up. I booted into recovery and cleared the dalvik cache again. Seems to be working again now. We'll see if it does it again.....
Well, the screen locked up again. I tried going through the whole process again. I wiped the caches and battery stats, nothing. I wiped all the storage and data, booted into a clean stock interface, nothing. Restored the backup image, and then at some point, through all the rebooting and whatnot, it just shut down completely. I can't even get it to the bootloader. I'm really feeling like it's a hardware problem, and i've made peace with sending it back for TEP, but i have no way to unroot it.
Any suggestions? Please......
Theres unroot processes out there. I cant remember where but ive seen them. Mine gets sluggish too, but after a reboot its ok. You cant even get into the bootloader tho. I'm not even close to an expert but.......uh I'd 'lose' it and call the insurance co....
The problem only happens when I reboot or turn on the phone. When it boots up, I get multiple results. A: It boots up normally (not a problem) B: When it gets to the samsung screen, it freaks out and reboots itself again and again. It's like it's struggling to boot up. One time it got to the gs 3, but then it looped back. C: This just happened today. I booted up and it went pass the samsung screen but when it got to the gs 3 screen, the screen turned a faint pink and it stayed on that screen.
This just happened right after version 8. I know 10 was messed up but on 9 and 11, this problem persisted. Also,I don't think the issue is the phone, since I don't have this problem on other Roms. If I'm wrong please let me know .
Any suggestions, advice, help, etc is welcomed.
Please... i really need help.
I suggest you start over, this will remove any corruption and gremlins you have klinging to your phone..
http://forum.xda-developers.com/showthread.php?t=1904099.. Then re root and flash anew.
Naddict said:
I suggest you start over, this will remove any corruption and gremlins you have klinging to your phone..
http://forum.xda-developers.com/showthread.php?t=1904099.. Then re root and flash anew.
Click to expand...
Click to collapse
I unrooted, went back to stock, it did a factory reset so no bugs should have been alive. I re-rooted, made a backup, did a factory reset and wiped dalvik, then I flashed the rom zip and rebooted. It gets stuck on the Gs III screen. I waited like 5 minutes and it didn't move. My battery was at 50% so I just put it on the charger and tried to boot up and it went through to the set up screen for gmail.Just to see if it was coincedental, I did another reboot but this time it got stuck again. It sounds like a system problem but i'm not sure.Like i said earlier, this only happens on Jellybomb.
Any other ideas?
Edit: I've tried switching recoveries but it doesn't fix it.
Sigh.
Was running PA latest build. I took the battery out of the phone and switched with my wife. When I tried to power it back on, it was stuck on the boot screen with the PA logo. I tried flashing the ROM over and several different PA builds and flashed Gapps and I am able to get it to go past boot and to android is upgrading and it checks all the apps but then wont boot after "Starting Apps". I fell asleep last night while trying to get it fixed and when I woke up this morning, it was still on android is upgrading, starting apps. If I wipe data, it works. but nothing changed before I took the battery out. If someone has any pointers I would really appreciate it! I would hate to loose all my data!
I did make a nandroid of everything and tried wiping certain things at a time and its only when I wipe data, it works.
I'll start from the beginining.. Okay so since i bought my tab (3 months ago) i had a battery problem, but it wasnt a bad battery problem. Once it got to 95% battery it stopped charging. Anyway, about a week after that i was unhappy with the performace of touchwiz on my tab so i decided to root it and install the cyanogenmod 12 nightlies. I was happy with cm for a while but eventually i got bored of all the bugs and instabilities so i decided to switch to a touchwiz rom.. This touchwiz rom was a vast improvement from the stock touchwiz so i decided to keep it. However i still wanted to improve the performace so i researched online for apk's/zip's that could improve my tabs performace. I came across crossbreeder and people said it was really good so i decided to install crossbreeder through TWRP. Once installed i rebooted my device and i instantly found many more battery problems. For example my battery would go from 50% to 20% in 5 mins/my battery would run out and i would reboot it and it would have had 40% etc. I downloaded some battery calibrating apps and calibrated my tab. After all that, that battery wasnt so bad. It was still dodgy but no where near as bad as it was straight after installing crossbreeder. Anyway, this was about 1 month ago. Since then, no new problems had occured with the battery until last night. Last night, my battery ent don to 1% then turned off like it should. I put my tab on charge and rebooted however when it rebooted nothing would work. My touchscreen didnt work, my home button didnt work, none of the keys next to the home button didnt work. So i thought that this was no problem and i could just boot into TWRP, factory reset and install the backup that i made. When i tried this, i booted into TWRP successfully however i couldnt press any of the TWRP buttons, again, i thought that this could be solved by flashing the stock firmware through odin. I put my tab into download mode and connected it to my pc, then flashed the stock rom. Once finished it showed a 'pass' and i thought everything was sorted.. When my tab booted up, it again, didnt let me press anything and none of the buttons would work. This is when i panicked. I then went into the stock recovery to factory reset my tab to see if that would work however, when i went into stock recovery, i couldnt go up or down using the volume keys.. So my volume keys didnt work either. I next put my tab in download mode and connected it to my pc. I opened odin and checked the 'Nand erase all' box thinking this would fully reset my whole tab. I then researched the 'nand erase all' function to find that everyone said that it breakes your device and puts it in bootloop etc. After reading this i instantly disconnected the usb from my computer to my tab. I tried rebooting my tab to see if it still booted and it didnt.. (i waited 20 mins). I then ran odin with 'clear efs' box ticked on. Again it didnt boot. I went into stock recovery again to see if the volume keys would work.. they didnt.. Infact when i opened stock recovery it had 3 errors showing (which it didnt last time i opened stock recovery). They all started with 'failed to mount /data'. Now i am here.. Sorry it was such a long read, i thought it would be better if i explained in detail. Thanks to anyone that replies/helps me.
NAND Erase All shouldn't destroy your device. What you need to do is boot into recovery, and choose the Factory Reset/Wipe Data option. From there, reboot and you should be good! Otherwise if it doesn't boot, just flash in Odin again, reboot to recovery, and then Factory Reset/Wipe Data again. We'll get you back up and running in no time
The reason why you are getting those errors is because your data partition is NOT formatted (because NAND Erase All wipes out your partition details, so it looks unformatted), so the recovery and your kernel are not finding your data partition. Your device will be unable to boot without. Factory Reset will reformat your data partition and get everything into place. Let me know how it goes!
A few months ago, the display broke on my Moto Z Play. It took me awhile, but I finally got a replacement display.
During the time I was not using it (starting immediately after it broke) it would make the sounds for my calendar notifications as they would come up, and continued to do so until the battery died.
While the battery was dead, I carefully took off the remnants of the old broken LCD.
About two weeks before I got the new display, I plugged it into my computer to see if I could pull any of my information off of it. Unfortunately, I was unable to get it to show up as a drive on my computer so I couldn't pull anything off of it.
Since it had power, it once again made sounds for my calendar notifications until the battery died.
I got my new display in the mail a couple days ago. I set about installing it and after I was done, I charged the battery to 96%. The charging screen appeared perfectly normal. I had no indication that there was going to be any problem when I went to use it until I powered it on at 96%. It looked like it was going to boot up just fine and made it three screens (not counting the triangle screen) into the boot up process and restarted the process.
The last time the phone was fully functional (as well as while it was on with a broken LCD) it was running OmniROM and it has TWRP 3.2.1-0 recovery on it.
First I tried clearing the cache and dalvik cache. That didn't help. Then, as I keep a copy of the zip for that ROM on my SD card, I decided to reflash OmniROM and 8.1 gapps. That didn't help. So, I decided to do a nandroid backup. It got part of the way through the back up and failed at system image. So, I decided to try to backup my data so that I can at least hopefully restore some of it at a later date on my computer or something. Thankfully, I was able to successfully backup my data partition.
After the backup finished, I decided to attempt to dirty flash CosmicOS.
However, I experienced the same boot loop.
I then did a full wipe and did a clean flash of OmniROM.
Still: the triangle screen, 3 seconds of the boot process and then it starts over again.
I am lost as to what to do now.
Help!
Hello?...