Randomly crashed this morning, now it is in a perpetual bootloop no matter what I do.
I have a Nexus S 4g
I did a factory reset and that didn't work.
I tried to use CWM USB mounting to copy over a new rom and that didn't work.
I updated CWM to the latest version and sideloaded CM10.1.2 and the latest gapps, and yet the bootloop persists. I'm positive that it installed both of these zips successfully.
My last resort was trying to return it to stock using a a 2.3.4 image and relocked and unrooted. Still won't boot up.
What can I do to fix this? I'm confused. Is it possible that my phone is entirely broken?
Related
I've searched endlessly for a fix to this. It all started when ROM Manager tried to flash a new CWM version to my Optimus T (US). It failed. Yesterday, I managed to flash the stock INDIAN ROM to it. After rooting, reinstalling a stable version of CWM, and reinstalling CM7, my network stopped working (no signal, no 3G, etc.). I attempted a reboot, and got stuck in fastboot. I fixed that, and flashed V10S to my phone via KDZ, which is now not working (boot loop). It has no custom recovery, and I can't seem to get the normal recovery to work. Any fix for this?
Note: I saw in a thread somewhere that it's suggested that my recovery could be the root of my problems. If so, could some one verify this and point me in the right direction to get this thing at least back to factory settings? This is a really weird type of bootloop that seems to have no straight foward fix.
CodmasterRob said:
I've searched endlessly for a fix to this. It all started when ROM Manager tried to flash a new CWM version to my Optimus T (US). It failed. Yesterday, I managed to flash the stock INDIAN ROM to it. After rooting, reinstalling a stable version of CWM, and reinstalling CM7, my network stopped working (no signal, no 3G, etc.). I attempted a reboot, and got stuck in fastboot. I fixed that, and flashed V10S to my phone via KDZ, which is now not working (boot loop). It has no custom recovery, and I can't seem to get the normal recovery to work. Any fix for this?
Note: I saw in a thread somewhere that it's suggested that my recovery could be the root of my problems. If so, could some one verify this and point me in the right direction to get this thing at least back to factory settings? This is a really weird type of bootloop that seems to have no straight foward fix.
Click to expand...
Click to collapse
go to emergency mode and use kdz. and don't use a rom with old baseband
Hello,
I recently was running Cyanogenmod 10.1.3 (i think... it was the latest stable build) when I got a notification to update to 10.2.1. I did so through the cyanogen updater and it seemed to work fine but the phone would randomly reboot. Finally it did so but remained at the initial loading screen. I then booted into TWRP and flashed the 10.2.1 again. Same deal it just wouldn't boot it remained frozen. I then tried to reflash 10.1.3, the previous version I was running. The phone imediatley booted into fastboot with a flash failure indicator despite TWRP saying it had been sucessful. I have since tried to install the Mototola's OEM firmware, as well as do a restore from a backup I had made in TWRP. nothing works and I can't move past fastboot. Im interested to know why this is happening and how I can reflash properly without getting an error? Any replies will help. Thanks.
-Justin
So I was on Marshmallow, got tired of the excessive battery drain and SD card limitations, and flashed back to Lollipop. I was able to flash TWRP, but then when I rebooted, I was told there was an update, so I reflashed the stock recovery and updated. Now I can't get back to TWRP. I flashed it repeatedly and every time I reboot into recovery, it's still on stock. I've lost root and nothing I've tried works. WTF?
Nevermind, I just tried flashing TWRP 2.8.7.1 and it worked. 2.8.7.3 apparently does not anymore.
Can a mod delete this?
Hi all,
I have a P5110 tab 2.
I rooted and installed CM 10 on this device some time ago, and it's been working fine for many months.
Recently, it's started rebooting itself from the OS - i.e not at boot logo etc - it actually gets into the OS, lets you do a few things for a few seconds, then thows you out and reboots.
This device has an older version of CWM on.
I can boot into CWM Recovery, have tried wiping dalvic, cache, - everything - but still the reboots.
Have tried to load twp from zip via CWM, it says installed ok. I reboot, go back into recovery, and its still this old version of CWM.
With this being an older version of CWM, it wont let me install the later versions of CWM.
Im thinking of reflashing the stock rom (4.x.x afair), to hopefully stop the reboots, so I can get into the OS and flash the later version of TWRP, so I can then flash a later version of CM.
All a PITA!
Question is - why does the p5110 keep rebooting, out of the OS?
I read somewhere that this could be a hardware issue - chip over heating or something.
Is this device worth bothering with?
Second question - why wont CWM let me install TWRP (from Zip in external SD, .img is in the zip) - even though it says it has installed it?
Any thoughts or assistance greatly appreciated!
Could this be the "dreaded emmc chip" issue?
If this was indeed the issue - would it boot to the OS at all?
I'm assuming not, and therefore this isnt the issue - can someone confirm?
http://forum.xda-developers.com/galaxy-tab-2/general/discussion-alternative-tab-2-emmc-bug-t3306862
Maybe it is. You said you tried to flash the later versions of cwm but it didn't work yes? I think one of the symptoms is that you can't flash anything on the device because it became read-only. I may be wrong though so kindly check
EDIT: Maybe do a factory reset? If everything is still there after the wipe, 99% your emmc got read-only.
so yesterday, I decided to root my tablet. Everything was working nicely after I rooted and downloaded clockwork mod. The whole problem started when I used an app called quick boot, and I booted into recovery mode. As it was rebooting, it asked for permissions(I accepted obviously), and I haven't been able to get past the logo screen ever since. I tried wiping everything, but it still doesn't work. Any solution to this?
Reflash stock firmware with odin should probably work.
I managed to fix it by using the adb sideload thing in twrp.