So, I have been using Shohat rom for about a week so far, but I decided to switch back to stock since the camera kept crashing in most of the modes except auto on Shohat; I used TWRP to backup stock before flashing Shohat.
I started the restore about 40 minutes ago and it is currently stuck on "Restoring Modem..." which is where it has been for about 39 of those minutes, what do I do? Should I pull the battery and try again?
Edit: I went ahead and pulled the battery and restarted the recovery with "Restor Modem" unchecked...
Related
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.
Ive been running CM12 for a long time, but today I noticed I had a few missed calls and my phone hadnt rung. I rebooted the phone and it went into a boot loop. I cleared cache, but still bootlooping, dirty flashed the latest nightlie and then a full wipe - all of which resulted in the boot loop.
I restored my phone using the TOT method, but it would get to the setting up google account/wifi etc and reboot.
I used KDZ to install 30b lollipop ROM this seemed ok until reboot and then it would factory reset, optimise apps every time and be back to the setup screen.
I managed to install KK using KDZ and this seems more stable so used IOROOT and Autorec. I then flashed CM12 and GAPPS again, but it started to boot loop again.
I hadnt done anything to my phone prior to the problems - ie. no new ROMs, kernels or even apps.
Any suggestions or does it sound like something more physically wrong?
I have managed to get Cloudy G2 2.2 working without any problems except it isn't recognising my SIM. Does anyone have any thoughts or is this a dead phone?
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?
OK so I have been using this rom and updating it as new releases were available and presently am running the 1-20151101 version. I decided to encrypt my phone before I went to bed last night as the process could take over an hour. It went through several boots but when I went to bed it was still in the DevConnection boot screen. I figured it might be taking a little longer than normal and went to bed. When I woke up 8 hours later it was still on the same screen. So I forced a reboot. During the reboot process the phone asked me to enter the encryption pattern I had established the night before which I did. Then the screen went back to the DevConnection animation where it stayed for a couple of hours. I decided something must have gone really wrong and went to the bootloader to perform a factory reset, wipe partitions and dalvik cache and reinstalled the rom and gapps. Everything seemed normal but when I rebooted I was prompted to enter the encryption pattern. After I did it went right back to the DevConnection boot screen animation where it has remained for another hours or so. Any suggestions?
On Samsung Galaxy S4 running JDCTeam CM12 1-20151101
Kenyon
I upgraded to Nightly 20160107 today through a notification on my S4. After the upgrade, I noticed that the phone was not working right. A number of apps were missing and the camera was not responding, etc. I quickly went to Recovery and chose Restore. But I did not wipe before I pressed on the Restore Button. The process hung and did not advance after 10 MB of 5600 MB. After a fairly longtime, I removed the battery and after I reinserted, the phone hung on the boot screen showing SAMSUNG GALAXY S4. I have tried removing and reinserting the battery several times but got the same result.
Can somebody help me please?
Try to flash stock rom with odin http://www.sammobile.com/
Try a full wipe before restoring.
Normally, when you restore something, it automatically wipes.
But yeah, since the restore didn't complete you messed up the OS. In other words there is no OS to boot in. So I'd suggest flashing a rom. Any rom should do.