So I was recently running AOSPA and loved PIE and HALO but there were some instabilities with it that caused it to randomly reboot. So I flashed CM again for stability purposes then read through the Carbon ROM reviews and decided to try flashing it to try to get those features back, as I could not find them in CM, after finding enough proof it was stable enough for me. So I flashed that ROM and in the middle of flashing it rebooted for some reason and the flash was incomplete so I can't flash through the android system and I just tried using ODIN to flash PHILZ touch recovery (I was previously using TWRP) but I still cannot access my recovery by powering on and holding power up...any suggestions?
Pull the battery then try again.
Sent from my SPH-L720 using xda premium
For some reason it appears I needed to try booting to recovery more than once to access it after it rebooted. I am still having problems getting through set up but that's an unrelated issue I'll try to figure out.
Related
Hi all,
So coming from a Samsung craptivate, Im having a little bit of trouble flashing CM 6.1.1 on my new N1
so far starting from stock I have
- Unlocked the bootloader
- used fastboot to flash the latest clockworkmod
now I am trying to boot into recovery to flash the CM zip on my SD and I keep getting to a screen with the android guy and an exclamation point, and have to do a battery pull to reboot, I have tried using adb and 3 button combo to get into clockwork,
so, what idiotic thing am I doing wrong?
You're booting in between installing the recovery and booting into recovery.
There are two files that restore the stock recovery upon a system boot (which is what you are seeing). If you go straight to recovery after flashing, the stock recovery won't be restored, then you can install a custom ROM.
The two files are missing from custom ROMs, so you won't have this problem again.
Typically, people remove these files once they have root access, but since you don't have root yet, that isn't an option...
Sent from my Nexus One using XDA App
thanks very much for your help, got it working
Reading the Wiki guides for installing recovery should have solved your question before you wrote it.
I tried to install CM nightly off the official CM mirror network.
I already had my phone rooted with Liberty ROM installed, so I simply rebooted into clockwork, did a backup, wiped the phone, and then installed the cm_droid2_full-21.zip from SD card.
Something is really buggy with the ROM and it FC's upon loading the home screen and then automatically reboots. I cannot get into clockwork by pulling the battery or holding down camera and power, or power and volume down---nothing works. I'm stuck in this bootloop and as of now my phone is useless....please help!!
Sounds like you have no option but to boot the phone in bootloader mode and flash froyo build back on your phone.
U try to get into stock recovery and wipe cache and data? Its usually the cache
Sent from my DROID2 using XDA App
I have been running AOKP on my Fascinate for a while now, but something wierd is going on with the device. After about a week of running AOKP (I tried the Hacksung ICS builds as well), the Fascinate begins to bootloop, so I have to go through and ODIN (cannot wipe and reflash because it continues to bootloop after wipe and reflash) then flash AOKP again. The process repeats itself after roughly a week of use.
I went back and Odin'ed to 2.3.5, but ever since then, I have been unable to install a working recovery on my device. I can flash the recovery fine (Voodoo, and CWM fixed for CM7), but when it boots up, and I try to flash a file, the screen goes black for a minute, then goes back to the recovery menu, like it is rebooting recovery. I've tried Heimdall and Odin.
Anyone got any tips? Am I just forgetting something?
Sent from my SCH-I500 using Tapatalk 2
in odin did you use the atlas.pit repartition file when you flashed back to stock?
if not then try that. also, which CWM are you trying to flash?
I know my fassy had problems with certain versions, but a 2.5.x version always worked for me no matter what happened to my phone.
This guide always worked for me.... http://forum.xda-developers.com/showthread.php?t=1238070
First, I searched and read all relevant threads concerning this issue. The five threads that showed up in the search did not help me solve my issue.
So on to my problem. I can no longer flash any rom onto my device. I attempted to flash the first official CM10 nightly (which I recently found out was not flashing properly for others) and had no success. I simply got a black screen and nothing more. I eventually got back into TWRP (v2.2.1.4) to try and Nandroid restore, but I noticed that /data was not formatting and the restore failed. Every time I would slide the bar across to confirm the restore TWRP would reboot itself. I then flashed CWM (v6.0.1.0) and the same problems were there. After that I flashed an earlier version of TWRP and successfully restored the backup. I'm not 100% sure how it was successful. So I decided to try flashing another ROM and no go. Same problems. Anyone have any ideas? When I was using CWM I got the error message below.
Code:
E: unable to locate volume information
E: unable to open ums lunfile '/sys/devices/platform/usb_mass_storage/lun0/file'
E: unable to format data
I'm running Bugless Beast with Motley #219
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
aznxk3vi17 said:
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What rom did you attempt to flash?
elementur said:
What rom did you attempt to flash?
Click to expand...
Click to collapse
So do I.I attempted to flash the first official CM10 8.18 nightly and had no success. I just got a black screen.Even more I boot into bootloader and choose to boot into recover but just stay at google logo.I try to flash recover once more,but just can't boot into recover!!
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Shano56 said:
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Click to expand...
Click to collapse
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
phiracle said:
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
Click to expand...
Click to collapse
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
android1234567 said:
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
Click to expand...
Click to collapse
Thank You Very Much!!!
I am having much the same problem as the OP. I finally rooted my Nexus 7 using WugFresh's Nexus Root Toolkit. It seemed all went well. I chose to use TWRP in a first attempt to install a ROM (I was on rooted stock), and following the instructions for installing my chosen ROM I went into it to wipe cache, Dalvic Cache and data. Both cache and dalvic cache wiped without issue, but when I attempted to wipe /data TWRP simply reported that it failed. With that failing, I did not attempt to install a rom. I was still able to boot out of recovery, but even with repeated attempts wiping data always failed. Is any one aware of any solution or have any suggestions. Thank you!
I unlocked my bootloader awhile back when the exploit first came to light and have been enjoying it mostly problem free since.
I've been using CWM with CM10.1 for the most part but the issues I was having with CM were finally getting to me so I thought I'd just try a debloated stock ROM, and thought it was a good time to try out TWRP while I was clearing everything out.
So I loaded up Matt's tool and flashed the stock ROM back (because for some reason my computer doesn't like to recognize CM over USB), no problems there. At the suggestion of the tool I also flashed the stock recovery (since I intended to flash TWRP I figured it was a good idea). Here's where my problem lies now: The phone boots fine back into stock ROM and I can get back into fastboot no problem but if I try to get into recovery (after flashing stock, CM or TWRP) I only get the opened up Android with the red triangle/exclamation.
Is there some step I need to take that I'm not?
I boot into fastboot and flash recovery (stock). Boot normally wait a couple min (skip setting up accounts, etc) then flash the custom recovery but I seem to end up back at the broken android every time.
EDIT: I might just be an idiot. I completely forgot to root the stock ROM before trying to put the custom recovery back.
Broken android is stock recovery...
Sent from my XT907 using Tapatalk 4