Since yesterday, every time I try to flash something in ROM manager, it reboots into recovery, but just acts like I only booted into recovery. it never flashes anything. i've tried all the usual fixes (flash a different recovery, restore an old ROM, clear download cache) but the issue still persists.
I have an HTC incredible, latest radio, etc. and running cm6. (the 9 18 nightly)
anyone have any suggestions?
Related
Hey all. I can't seem to find anything about this via searching or asking folks I know In the community so I'm going to toss it in here and see if anyone has this problem.
I bought a brand new Nexus S GT-I9020T from best buy several days ago. I got it rooted and flashed the latest radio and cyanogenmod nightly. I wiped everything (boot, sd, system, data, cache, dalvik) and flashed again to be sure, but for some reason when I boot into clockwork recovery (via power off menu, adb, bootloader, or rom manager) It takes about 15 seconds to boot into recovery. I'll get the google logo then a black screen for about 10-15 seconds and clockwork recovery finally comes up. I've tried the following things and the issue remains.
Cleared rom manager download cache
Checked "erase recovery prior to flashing" in rom manager
Downloaded and flashed recovery multiple times
Not sure what the issue is here. Any ideas?
infinitybiff said:
Hey all. I can't seem to find anything about this via searching or asking folks I know In the community so I'm going to toss it in here and see if anyone has this problem.
I bought a brand new Nexus S GT-I9020T from best buy several days ago. I got it rooted and flashed the latest radio and cyanogenmod nightly. I wiped everything (boot, sd, system, data, cache, dalvik) and flashed again to be sure, but for some reason when I boot into clockwork recovery (via power off menu, adb, bootloader, or rom manager) It takes about 15 seconds to boot into recovery. I'll get the google logo then a black screen for about 10-15 seconds and clockwork recovery finally comes up. I've tried the following things and the issue remains.
Cleared rom manager download cache
Checked "erase recovery prior to flashing" in rom manager
Downloaded and flashed recovery multiple times
Not sure what the issue is here. Any ideas?
Click to expand...
Click to collapse
Twenty seconds doesn't sound bad. I think it's the normal time for Nexus S to boot into recovery. Try checking some videos on YouTube of nexus a booting into bootloader. That should give you an idea.
Yea checked all that and asked other nexus s users. No one has this problem. going to try an older recovery.
Update on this:
Flashed back to an earlier recovery from fastboot. Its a 2.x version and reboot recovery is instant (or at least the speed it should be) When flashing the latest recovery from rom manager, the problem returns.
So I'm stuck. Obviously its an annoyance more than anything but the first time it happened I thought I bricked my $500 new toy
infinitybiff said:
Hey all. I can't seem to find anything about this via searching or asking folks I know In the community so I'm going to toss it in here and see if anyone has this problem.
I bought a brand new Nexus S GT-I9020T from best buy several days ago. I got it rooted and flashed the latest radio and cyanogenmod nightly. I wiped everything (boot, sd, system, data, cache, dalvik) and flashed again to be sure, but for some reason when I boot into clockwork recovery (via power off menu, adb, bootloader, or rom manager) It takes about 15 seconds to boot into recovery. I'll get the google logo then a black screen for about 10-15 seconds and clockwork recovery finally comes up. I've tried the following things and the issue remains.
Cleared rom manager download cache
Checked "erase recovery prior to flashing" in rom manager
Downloaded and flashed recovery multiple times
Not sure what the issue is here. Any ideas?
Click to expand...
Click to collapse
The lag time was introduced with the 3.0.2.4 recovery, if it really bothers you flash back down to 3.0.0.5.
But i have it as well, im sure Koush will fix it soon
bringonblink said:
The lag time was introduced with the 3.0.2.4 recovery, if it really bothers you flash back down to 3.0.0.5.
But i have it as well, im sure Koush will fix it soon
Click to expand...
Click to collapse
glad to know i'm not crazy. thanks
Hello,
i had an old Custom Rom on the Desire HD from my girlfriend and now I tried to flash cm-11-20140916-UNOFFICIAL-M10-ace.zip. I had an old version of 4ext and tried to flash the rom. Did not worked, so i used the 4ext recovery updater to update to the newest version (v1.0.0.6 RC2). I tried to flash the rom again and it worked. I did the customisation at the beginning, that appears, when you start the rom the first time or do a factory reset. After that i installed all apps and shut down the phone. I tried to restart it and get stuck after the HTC Logo. There is only a black screen, that is lightened. I have to remove the battery to shut it down again. Tried it some times, but it did not worked. So I did full wipe and flashed cm-11-20140804-UNOFFICIAL-M9-ace.zip. I got the same problem after restarting. Does anybody know how to fix my problem?
btw, I also flashed GAPPS 4.4 PICO.
EDIT: This time I tried it without gapps and it did not work, too. I flashed CM7 and there the reboot works fine.
A customer (I kinda do this for work) brought to me about 8 months ago a MZ604 full stock. I rooted, enabled BigPart, flashed CM11, customer happy. Yesterday he called me because the tablet boots to Android and immediately reboots. Easy, wipe, reflash, done.
Nope. Wiped data, rebooted. All the same. Wiped SYSTEM, I mean, deleting the ROM, all the same. It's like the memory is freezed (like on Windows when you reboot and everything you did in that session resets).
Tried RSD, stock ICS. No avail. RSD reports the flashing was succesful, but everytime I boot I get the same CyanogenMod animation. ROM boots, works for a few secs, and then reboots again.
I HAVE NOT A CLUE. Whatever I do, no change. Noting happens.
Also, when trying to change the recovery via fastboot, it reports it flashed correctly, but the recovery stays the same version.
Hi everyone, i've got my OPO when CM12 still wasn't a thing, and it always did his job wonderfully, i've updated to CM12 when it first came out, then updated it every time a new stable version was out, YNG1TAS2I3 version included (with root access and TWRP). A few days ago, while i was listening to some music with Google Play Music, the phone started to reboot itself for no apparent reason, and after around 10 reboots with random timings, i found out there was a problem with google play services, so i blocked them with Titanium Backup, deleted updates, updated them again, reactivated, and everything went fine.
Yesterday, my phone once again rebooted by itself, but every time it was rebooting, while showing the boot logo, it rebooted again without actually loading android. I first tried to wipe cache, then dalvik cache, then data and system partitions, factory reset, but it kept rebooting no matter what, until i tried to flash CM11S on it. After a few tries and total wipes, CM11S was running with no reboots, and it worked flawlessly, no root, no custom recovery, everything stock flashed from official fastboot images zip.
After that, i tried to update via OTA to the more recent versions of CM11S, no problems so far, but as soon as i updated to CM12 via OTA once again, the phone started to reboot itself after the update, it says "Upgrading Android" like when you wipe the dalvik-cache, and then it freezes for a second, then reboots.
Things i've tried so far:
full wipe and factory reset from TWRP
erase and flash again all partitions
erase and flash again persist partition
flash colorOS and then flash CM12
After flashing the persist partition it managed to work for a minute on CM12, but then it started rebooting itself again, and i've managed to save the last part of logat log , but i'm not sure if it's worth anything to find out the problem! (i can't post it on forum because of the new user link restriction, but if you want to have a look at it, let me know)
So, basically, my phone works only on android 4.x and not on 5.x, I would think some app on it can make it crash, but even after a full wipe it still behaves like this, what could be the reason and how can i try to fix it? thanks in advice!
I recommend you to flash fastboot images of CMOS12 without skipping any file
Steps to flash >> http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
xKylesx said:
Hi everyone, i've got my OPO when CM12 still wasn't a thing, and it always did his job wonderfully, i've updated to CM12 when it first came out, then updated it every time a new stable version was out, YNG1TAS2I3 version included (with root access and TWRP). A few days ago, while i was listening to some music with Google Play Music, the phone started to reboot itself for no apparent reason, and after around 10 reboots with random timings, i found out there was a problem with google play services, so i blocked them with Titanium Backup, deleted updates, updated them again, reactivated, and everything went fine.
Yesterday, my phone once again rebooted by itself, but every time it was rebooting, while showing the boot logo, it rebooted again without actually loading android. I first tried to wipe cache, then dalvik cache, then data and system partitions, factory reset, but it kept rebooting no matter what, until i tried to flash CM11S on it. After a few tries and total wipes, CM11S was running with no reboots, and it worked flawlessly, no root, no custom recovery, everything stock flashed from official fastboot images zip.
After that, i tried to update via OTA to the more recent versions of CM11S, no problems so far, but as soon as i updated to CM12 via OTA once again, the phone started to reboot itself after the update, it says "Upgrading Android" like when you wipe the dalvik-cache, and then it freezes for a second, then reboots.
Things i've tried so far:
full wipe and factory reset from TWRP
erase and flash again all partitions
erase and flash again persist partition
flash colorOS and then flash CM12
After flashing the persist partition it managed to work for a minute on CM12, but then it started rebooting itself again, and i've managed to save the last part of logat log , but i'm not sure if it's worth anything to find out the problem! (i can't post it on forum because of the new user link restriction, but if you want to have a look at it, let me know)
So, basically, my phone works only on android 4.x and not on 5.x, I would think some app on it can make it crash, but even after a full wipe it still behaves like this, what could be the reason and how can i try to fix it? thanks in advice!
Click to expand...
Click to collapse
1)Are u tried cm 12.1
after u flashing cm 12 then reboot and again go back to recovery and flash cm 12.1
2) try to use different kernels supporting to cm 12 like boeffla /AK etc
3) try to flash cm 12 firmware via fastboot flash installation process
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.