So I rooted my phone long ago when it was new just to get wifi teather which worked great and has been ever since. I never installed the AT&T update that it kept asking me to do because I did not want to lose root and the teather ability. I recently installed CWM Touch Req0very because I wanted to try a new ROM. This worked fine and I can get into CWM now. I completed a backup using CWM, thankfully. I then tried to load the LiquidSmooth ROM for this phone. Before doing so I used CWM to complete a factory reset, cache wipe, and dalvik cache. I then chose the LS zip file and it loaded and appeared to be successful. I then rebooted and got the Samsung unlock padlock image for a few seconds and then the screen went dark and the power LED turned blue. I let it sit for a few minutes but nothing changed. I pulled the battery and rebooted but got the same. I then went back into CWM and restored my backup which took my phone right back to where it was, very thankful for that. What did I do wrong and how can I get the ROM to install properly?
I tried to reinstall the ROM and when it booted it got further. It went past the LS splash screen and then started pulsing the LS ying yang type logo. It did this for about 10 minutes so I pulled the battery and tried again which it just repeated the same process. I pulled the battery and restored my backup again. Nothing seems to work as easily as the hours and hours of videos and pages I've researched. Why does this seem to work so easily for everyone else?
Related
I found a solution.
Setup: I have the Evo 4G, running the latest rooted 4.56 sprint update. I used the "infected" rom version. My phone was working great for about 3 weeks. No problems. Then yesterday, I pulled my phone out to use it and it was just stuck at the white HTC EVO 4G boot up splash screen. I pulled the battery out and the same thing happened. Here is what I did. Note that the LAST step actually fixed it, but I'm just documenting what I did. Also - I DID NOT LOSE ANY DATA! All my phone settings were left intact and didn't have to re-download anything.
1.) did a Nandroid backup though the recovery - just to be safe
2.) Rebooted to recovery and re installed the "infected" rom. rebooted and nothing changed. It was still stuck at the splash screen
3.) booted into recovery - Did a Dalvik wipe. rebooted
This fixed it! Not sure exactly what was wrong or how this fixed it, but I hope it helps someone else! The best part about this is that I did't lose any data at all.
Best of luck!
Buzz
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
thebullfrog said:
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
Click to expand...
Click to collapse
You might try and flash the stock kernel which should not allow any under/over clocking or under/over volting. Otherwise flash back to stock using the manual way here http://forum.xda-developers.com/showthread.php?t=1907796 or download the Nexus 7 toolkit and use it to do the same.
Try WugFresh's Nexus Root Toolkit. It has an option to go back to stock if you're soft-bricked.
Well I just did a factory restore/wipe (because Im SO looking forward to setting everything up again...) and it made zero difference. I'll try the stock kernel if someone could point me in the right direction to find a copy of it.
NVM found it. I'll give it a shot.
Ummmm okay then. I had my N7 turned off while looking for a solution to this fiasco. I picked it up so I could flash the stock kernel, and it had turned itself back on. Not only that, but it was fully booted up. Granted it's back to the initial setup after doing a factory restore, but there we go. It automagically fixed itself. Now to spend a couple hours putting everything back how it was. Yay.
Protip children: Always. Be. Nandroiding.
Very very strange I've never seen this before, so I was just doing my typical day walking around at work and all of a sudden I feel my phone got hot, pulled it out of my pocket and it was stuck on boot screen. So I did a battery pull to get it back to the rom and it just stopped at the bootscreen, after that I tried a dirty flash, then a clean flash...all I see is a bootscreen never gets past it. Recently updated to new firmware 2 weeks ago and did notice it was strange when I flashed the GE Rom kept asking me to Install SU. Anyone got any idea how to fix this? Only issue i noticed was during the install of the rom i get a unable to mount /preload but besides that everything completes fine
fadentales said:
Very very strange I've never seen this before, so I was just doing my typical day walking around at work and all of a sudden I feel my phone got hot, pulled it out of my pocket and it was stuck on boot screen. So I did a battery pull to get it back to the rom and it just stopped at the bootscreen, after that I tried a dirty flash, then a clean flash...all I see is a bootscreen never gets past it. Recently updated to new firmware 2 weeks ago and did notice it was strange when I flashed the GE Rom kept asking me to Install SU. Anyone got any idea how to fix this? Only issue i noticed was during the install of the rom i get a unable to mount /preload but besides that everything completes fine
Click to expand...
Click to collapse
Use odin to go back to full stock, upgrade to MF9, do a factory reset, later root the device install recovery, do a full wipe install GE rom fix permissions. Report back on what happens. (Keep in mind this will wipe internal memory MAKE BACKUP!)
Sent from my SPH-L720
ATT Galaxy S4 currently running Goldeneye 6.0 and TWRP 2.6.0.0 (never installed MF3 base, but have tried both MF3 and MDL modems)
First odd thing...
[About->Status->Device Status] is listed as "Sd card" instead of the more common "Official" or "Custom".
Anybody know what that means or is telling me?
This is the latest thing I've noticed with my phone, which has been having all sorts of issues lately that I cannot seem to figure out. My main problem is, I can reinstall a new ROM, boot into the ROM, change settings around, reboot just fine, but, as soon as I install anything from the Play Store, the next reboot will hang on the initial Samsung splash screen. Wiping is the only fix I've found, and fixing permissions in TWRP errors out with an error that it cannot chown one of the new/updated .apk files.
Both Goldeneye 5 and 6 are doing this now (5.0 was installed and rock solid for several weeks before this all showed up...it started sometime after I decided to try out a couple of the aroma roms and then came back to GE).
Used ODIN to go back to factory rom, re-rooted/installed TWRP, then reinstalled GE6.0, but the same thing happened. Everything looked good until I ran updates from the store, then I was stuck again (note: used Root Explorer to check to permissions on the updated apks before rebooting and they were all correct (755)).
Other things I've noticed are:
1. Sometimes, on any reboot, the startup locks at the initial Samsung screen and I have to long press the power button to get it to reboot. It usually boots the second time around (this is before I install any additional apps and am completely unable to reboot).
2. Sometimes when wiping cache, davlik, and/or data, TWRP will seem to hang for up to a minute when trying to initialize the partition. A couple of times it even hard reboot my phone when I did a cache+davlik wipe.
3. I rolled back to a recovery image just fine; however, it was a couple months old. Everything started off looking great, but once I updated to a new ROM, my issues returned.
Trying Heimdall to go back to factory; however, I'm having issue with my laptop and getting the Zadig drivers installed. While I'm working that out, figured I'd see if anyone else has any suggestions on what else I should be trying or looking out.
thx
I would flash your phone back to MDL stock with odin using the mdl tar. This should format your paritions correctly. You could also reinstall MDL using kies since they still don't support MF3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I've spent close to most a work day now searching for an answer but am stumped.
I'm on MDL.
Downloade and flashed latest version of Goldeneye. Works great. After a bit, went to reboot phone.
Phone stuck @ boot screen ("Samsung" w/ unlocked lock below).
pull battery, same screen.
Wipe/reflash - all is well. Then re-boot, and stuck at same screen.
I have tried restoring multiple Nandroids and loaded 2 differnet roms. All with same result.
Also tried wiping data and restoring ESF backup and restoring my first rooted stock backup.
Same issue. works great till I reboot. Obviously somehting isn't sticking.
Any ideas? I hope I gave enough info
what recovery are you using?