Database Users

Recovery doesn't want to change, im stuck at 2.5.1.2

I want to flash CM7, but everytime I try flashing Clockwork recovery 3, it ends up staying at 2.5.1.2. What am I doing wrong? I tried flashing it from ROM Manager and that didn't help, and I don't know if I can flash it with the fastboot method since I'm using CWR already. What can I do?
Additional notes: Right now, I'm running CM6 RC2. And my phone looks sexy.

Like you I also came across that issue but trying to install kernel in Ice Glacier. Now what you want to do is install it manually via console. Check my other thread all you need is the flash image and clockworkmod recovery. I myself flashed ClockworkMod 3.0.0.0 as other howoto failed and True's didn't stick.

OptLynx said:
Like you I also came across that issue but trying to install kernel in Ice Glacier. Now what you want to do is install it manually via console. Check my other thread all you need is the flash image and clockworkmod recovery. I myself flashed ClockworkMod 3.0.0.0 as other howoto failed and True's didn't stick.
Click to expand...
Click to collapse
true's method seems to be broken for now, but he has posted that he will be looking into the issue as soon as he get home.

GazaIan said:
I want to flash CM7, but everytime I try flashing Clockwork recovery 3, it ends up staying at 2.5.1.2. What am I doing wrong? I tried flashing it from ROM Manager and that didn't help, and I don't know if I can flash it with the fastboot method since I'm using CWR already. What can I do?
Additional notes: Right now, I'm running CM6 RC2. And my phone looks sexy.
Click to expand...
Click to collapse
Go here,
http://forum.xda-developers.com/showthread.php?t=916930
And hit on the link to download the cwm 3.xxxx
Once the file is downloaded use root explorer, navigate to /sdcard/downloads/ and find the recovery. Make sure that it shows as .img and not as .zip. if it is a zip then unzip to get the .img file
Select the recovery and change the name to some easier name like f.e cwmrec3 (nnow u will have a cwmrec3.img file).
Move it to /sdcard (root) for ease of method
Open terminal emulator and do
Su (enter) (# will change for $)
flash_image recovery /sdcard cwmrec3.img
Wait for it to go to the next line.
Reboot to recovery and ur text will now be orange. You now haz recovery 3.xxxx
Also, note that if u enter rom manager it will still say that you have cwm 2.xxx that does not matter though as long as ur recovery txt is orange and not green
Sent from my rooted glacier running CM7

Flashing via terminal worked, thanks!

GazaIan said:
Flashing via terminal worked, thanks!
Click to expand...
Click to collapse
You are welcome my friend enjoy cm7
Sent from my rooted glacier running CM7

GazaIan said:
I want to flash CM7, but everytime I try flashing Clockwork recovery 3, it ends up staying at 2.5.1.2. What am I doing wrong? I tried flashing it from ROM Manager and that didn't help, and I don't know if I can flash it with the fastboot method since I'm using CWR already. What can I do?
Additional notes: Right now, I'm running CM6 RC2. And my phone looks sexy.
Click to expand...
Click to collapse
the fastboot method will work if you have CWM 3.5.1.3 already. I did that this morning, and it worked like a charm.

so I was able to do the easy cw method installing the zip from recovery then choosing 2.5.1.4, but after a few runs with the latest builds of CM7 i was having major issues with my mobile data connection jumping from H to 3G, each time lagging out my connection and making streaming videos, etc impossible to play. So I reflashed to stock, and my H returned to normal. So i thought I'd give it another shot, rooted, downloaded ROM Manager, flashed to 2.5.1.2 smooth, then tried the above method. When I tried to load the 2.5.1.4 in ROM manager, it said "An error occurred while flashing your recovery." So I tried the terminal, and no matter how I rename the file, and I know I followed the instructions flawlessly, it says flash_image: not found. So while ROM Manager seems completely capable of flashing to the 2.5.1.2 version, nothing seems to work to get me past it. What could I be missing?

darinmc said:
so I was able to do the easy cw method installing the zip from recovery then choosing 2.5.1.4, but after a few runs with the latest builds of CM7 i was having major issues with my mobile data connection jumping from H to 3G, each time lagging out my connection and making streaming videos, etc impossible to play. So I reflashed to stock, and my H returned to normal. So i thought I'd give it another shot, rooted, downloaded ROM Manager, flashed to 2.5.1.2 smooth, then tried the above method. When I tried to load the 2.5.1.4 in ROM manager, it said "An error occurred while flashing your recovery." So I tried the terminal, and no matter how I rename the file, and I know I followed the instructions flawlessly, it says #flash_image not found. So while ROM Manager seems completely capable of flashing to the 2.5.1.2 version, nothing seems to work to get me past it. What could I be missing?
Click to expand...
Click to collapse
Thats because you flashed back to stock and stock roms do not have "flash_image" on /system/bin
Download this
http://db.tt/Rv63e76
Use root explorer and paste it to /system/bin
Try terminal again
Sent from my rooted glacier running CM7

worked like a charm, thanks.

darinmc said:
worked like a charm, thanks.
Click to expand...
Click to collapse
You can hit thanks
glad i could help
Sent from my rooted glacier running CM7

Help rooting phone. Trouble getting green recovery screen.

So I rooted my friends Vibrant last night. I rooted my Vibrant a few months ago and didn't run into this issue. But I rooted using the same program "Vibrant One Click Root/Unroot" and followed the same steps as I did when I rooted my phone. However, once I installed ROM Manager and installed Clockworkmod Recovery and booted into recovery and clicked reinstall packages, the phone just rebooted. I remember when I rooted my phone when I clicked reinstall packages it did its thing, then went back to the blue recovery screen. Then I clicked reinstall packages again and it took me to the green recovery screen where I was able to then install zip from sd. My friends phone just keeps booting to the blue recovery screen where I can only reboot now, reinstall packages, clear user data, and clear cache. He had to leave so I did not have time to troubleshoot.
Any ideas as to if I missed a step? Any input would be appreciated.
Thanks in advance!
Sorry for the n00bish attitude, if this was my phone, I would put a little more effort into finding the answer. I'm just trying to get this done as soon as possible.

Are you using the actual clockwork app to boot into recovery? If so id just go back to stock and redo the root
Sent from my SGH-T959 using XDA App

creglenn said:
Are you using the actual clockwork app to boot into recovery? If so id just go back to stock and redo the root
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yeah, I went into ROM Manager and clicked "boot into recovery". Where it brings me to the blue recovery screen. So you think I should unroot then re root? Because everything with the root seemed to work fine. It installed superiser and I had no problems downloading Titanium Backup or ROM Manager and allowing superuser permissions. Which made me think I was just forgetting something...but I might just try that. Thanks!

if your rooting stock 2.2 your gonna need a modded 3e recovery or one of supercurios voodoo kernels with CWM & root already built in. Superoneclick will root stock 2.2. If its 2.1, then you may need to hit reinstall packages a couple of times to get it to take.

drscott333 said:
So I rooted my friends Vibrant last night. I rooted my Vibrant a few months ago and didn't run into this issue. But I rooted using the same program "Vibrant One Click Root/Unroot" and followed the same steps as I did when I rooted my phone. However, once I installed ROM Manager and installed Clockworkmod Recovery and booted into recovery and clicked reinstall packages, the phone just rebooted. I remember when I rooted my phone when I clicked reinstall packages it did its thing, then went back to the blue recovery screen. Then I clicked reinstall packages again and it took me to the green recovery screen where I was able to then install zip from sd. My friends phone just keeps booting to the blue recovery screen where I can only reboot now, reinstall packages, clear user data, and clear cache. He had to leave so I did not have time to troubleshoot.
Any ideas as to if I missed a step? Any input would be appreciated.
Thanks in advance!
Sorry for the n00bish attitude, if this was my phone, I would put a little more effort into finding the answer. I'm just trying to get this done as soon as possible.
Click to expand...
Click to collapse
All you should need to do is hit reinstall packages again. When you do it the first time it will boot back into the same blue recovery again. Hit it once more then it should boot to the green recovery. If that doesn't work you probably have a bad zip file on the phone. In which case you'd re flash CWM again.
If you're not getting the superuser request when you flash CWM then root didn't take. Make sure root works first.

Did you actually run install cwm from rom manager so the update. zip is there?

Just make sure with Astro or another file manger that you have a .zip file and it should be 1.72 MB in size and you want that on your internal SD card....Then when you boot to recovery it should let you hit reinstall packages with no problem

I'm new here, but I have flashed 3 vibrants since last week. I had the same problem you did.
When I flashed my phone last week it was stock 2.2, so I had to flash the modified 3e recovery which fixed my issue getting into CWM to install my ROM. Today i was flashing a co-worker's vibrant who also was on stock 2.2. However, on his it would keep rebooting when reinstalling packages, even though i did the 3e recovery flash. I ended having to Odin back to 2.1 on his phone before i could flash the new ROM.
I just used AIO Vibrant Toolbox 2.5. Hope this helps.

Thanks for all the feedback!! I don't have the phone with me to check if the update.zip folder was for sure there. But if it is, I'll try reinstalling the packages again. Otherwise I'm just going to unroot and try rerooting with the AIO Toolbox. I'm not going to be able to do this until tomorrow though since our work schedules were pretty much opposite today. But once again, huge thanks to all of you!!! However I've never unrooted before...if I haven't flashed any ROMs, I shouldn't have any problems should I? Just click unroot?

[Q] ClockworkMod & Splash Screen

Hi guys, i have cwm 3.0.0.5 which is really a cwm 3.0.0.6 mod i downloaded from here. anyway,i cant get back too 2.5.1.2. when i go into rom manager the lowest it says is 2.5.1.3 and none of the 2.x work for me except my old one. i tried rebooting it, and flashing the original 3.0.0.5 and it still doesnt show up and i have the paid version by the way. so my question is how do i get it back?
second problem is i flashed a splash screen and its stuck on there with a staticky looking bar covering the top of the screen when i reboot. i have deleted the custom.img on the sdcard, wiped the phone, flashed another custom.img, factory reset the phone, and it still is there and i pushed the files through terminal emulator, i do everything from my phone because my computer is very laggy. can anyone help with the above problems?

TamiaSky said:
Hi guys, i have cwm 3.0.0.5 which is really a cwm 3.0.0.6 mod i downloaded from here. anyway,i cant get back too 2.5.1.2. when i go into rom manager the lowest it says is 2.5.1.3 and none of the 2.x work for me except my old one. i tried rebooting it, and flashing the original 3.0.0.5 and it still doesnt show up and i have the paid version by the way. so my question is how do i get it back?
Click to expand...
Click to collapse
you can always find just the recovery image and flash it via the ADB commands.
TamiaSky said:
second problem is i flashed a splash screen and its stuck on there with a staticky looking bar covering the top of the screen when i reboot. i have deleted the custom.img on the sdcard, wiped the phone, flashed another custom.img, factory reset the phone, and it still is there and i pushed the files through terminal emulator, i do everything from my phone because my computer is very laggy. can anyone help with the above problems?
Click to expand...
Click to collapse
you need to flash a new image, that is the only way to fix it.

neidlinger said:
you can always find just the recovery image and flash it via the ADB commands.
you need to flash a new image, that is the only way to fix it.
Click to expand...
Click to collapse
and where would i find the recovery image? and can it be done using terminal emulator, becuase my computer has a virus and it takes days to load stuff or do anything, thats why i do it straight from my phone
and i have flashed a new image just like u quoted me i deleted the stuck one, wiped the phone, then i flashed another one, then factory reset the phone and its still there!

TamiaSky said:
and where would i find the recovery image? and can it be done using terminal emulator, becuase my computer has a virus and it takes days to load stuff or do anything, thats why i do it straight from my phone
and i have flashed a new image just like u quoted me i deleted the stuck one, wiped the phone, then i flashed another one, then factory reset the phone and its still there!
Click to expand...
Click to collapse
i'm sure google has something on the recovery image. I only have 3.0.0.6 stored in a .zip.
you CAN flash the recovery image via the terminal but not the boot image.

TamiaSky said:
and where would i find the recovery image? and can it be done using terminal emulator, becuase my computer has a virus and it takes days to load stuff or do anything, thats why i do it straight from my phone
and i have flashed a new image just like u quoted me i deleted the stuck one, wiped the phone, then i flashed another one, then factory reset the phone and its still there!
Click to expand...
Click to collapse
Download a fresh cope of the latest version here: http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-glacier.img and flash it via terminal emulator. It automatically overwrites the previous installation.

No recovery, No bootloader and can't SBF

Never mind this can be removed if necessary!
7/26
Well I need help again, so I figured I might as well use this post rather than creating clutter...
So my original help request involved my inability to get my phone into bootloader OR recovery but I eventually got it... I was trying to SBF back to Froyo so I can re-root and flash MIUI.
So I got all that done, but I seem to be having issues getting Clockwork recovery to stick around. After I recovered back to Froyo via SBF, I was able to download ROM manager and flash CWM recovery and then bootstrap it, reboot to it and flash MIUI. After MIUI boots up (runs great by the way, for those considering it), I installed ROM manager again but it said that I had no recovery (or stock) so I re-flashed CWM, bootstrapped it again and rebooted into recovery, only to find myself in the STOCK recovery...??? So without doing a THING in stock recovery, I hit reboot and now my phone is stuck at the Motorola logo and I am unable to reach CWM recovery to re-flash or anything. I cannot find another way to get back into my phone without an SBF back to Froyo, thus back to step 1.
Can anyone help me out?
Oh and I've already wiped data/cache with stock recovery - still no dice

See above post

I asked a similar question. It's a good thing I decided to wait until I got an answer before using ROM Manager. I am not sure why it did what it did.
I would also like to know the answer to your question.
edit: Perhaps (after you SBFed again) if you flashed CWM from Rom Manager but don't bootstrap? It seems like bootstrapping erases the ROM Manager's CWM and doesn't install the one it has. Just a thought. (If bootstrapping is important, though, then disregard this.)
Another thought. Bootstrap first, then flash CWM from ROM Manager. See if that works. Also try going to CWM through the bootstrapper, if you can't do it manually.
edit2: Just tried it that way (D2B first, RM second). worked like a charm. Was able to successfully update Miui.

Man, I don't get why these phones do some of the things they do...
I just SBF'd my phone again, re-rooted and re-installed MIUI and NOW, for some strange reason, I am able to make my way into CMW recovery.
Veeerrryy interesting

n1ghtwish said:
Man, I don't get why these phones do some of the things they do...
I just SBF'd my phone again, re-rooted and re-installed MIUI and NOW, for some strange reason, I am able to make my way into CMW recovery.
Veeerrryy interesting
Click to expand...
Click to collapse
lol With this stuff it's hit and miss. You just gotta keep trying till it works.

4.2.2 Update / TWRP problem

Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?

The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.

MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
Maybe before you even answer, I'm sure I'll find a link on here to show me how?
One issue I have though, is that when I manually updated to 4.2.1 on my Nexus 7, I still got an OTA update a few days later, that actually ran.
I don't ever plan on flashing roms to any of my devices. Do I need to keep a custom recovery on my Nexus 4 or 7? If not, how to I revert back to the stock recovery?

If you saved the offical stock 4.2.1 images, to revert back to stock recovery, just use the 'fastboot flash recovery recovery.**************.img' command. If you haven't, you might have to flash the whole 4.2.2 rom which you can find on the google dev website. After this, if you only want to root then you don't need to flash a custom recovery, just use the 'boot' command instead of the 'flash' one.

MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
I flashed the OTA sideload file through TWRP and it installed succesfully.

jvbferrer said:
I flashed the OTA sideload file through TWRP and it installed succesfully.
Click to expand...
Click to collapse
How did you do that? Did you sideload wrinkle's file from this thread: http://forum.xda-developers.com/showthread.php?t=2145848?
I should let you know, that while I'm not afraid to install via the custom recovery, it doesn't mean I've done it via commands. I've always used toolkits, or one click methods of rooting and installing custom recoveries.

Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.

wvcadle said:
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
Click to expand...
Click to collapse
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?

MacHackz said:
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
Click to expand...
Click to collapse
Yes, stock rom, rooted and unlocked. I did install Beats today. Could this be the problem? If so, I found a revert zip that I'm assuming is supposed to revert me back to stock audio codecs.

I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.

MacHackz said:
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
Click to expand...
Click to collapse
Flashing the revert zip failed. I'm starting to think that flashing anything with TWRP will fail.
How about this. I made a backup of all system data + apps with Titanium earlier today. Could I just reset my phone back to factory defaults, restore my apps + some system data, then re-root (*without a custom recovery*) and wait for the update again? Or will it come again?
Also, I've used Wugfresh's Nexus Toolkit. I don't remember checking the custom recovery button, but ended up with TWRP anyway. What's the easiest way to root without installing a custom recovery?

You could try that, and the update will come straiht away. You can root without flashing a custom recovery, just use the 'boot recovery' instead of 'flash recovery'

MacHackz said:
flash cwm and see if there's any difference
Click to expand...
Click to collapse
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?

wvcadle said:
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
Click to expand...
Click to collapse
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot

MacHackz said:
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
Click to expand...
Click to collapse
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.

wvcadle said:
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
Click to expand...
Click to collapse
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440

MacHackz said:
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
Click to expand...
Click to collapse
Where in that thread does it show me how to flash the stock recovery back onto my device?

wvcadle said:
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
Click to expand...
Click to collapse
The same thing happened to me. I was rooted running stock ROM with TWRP recovery (used wugfresh toolkit). The problem was I forgot I was using a modified kernel (for color correction) by molesarecoming. I flashed the stock kernel back, downloaded and flashed the OTA file from the help desk thread (http://forum.xda-developers.com/showthread.php?t=2145848&highlight=beats), and it worked. Oh, and I flashed the Superuser file immediately after the OTA did it's thing (while still in TWRP) to regain root. I didn't really like how after the initial failed install of the OTA, it took my into TWRP with no error message showing or anything.
I don't think TWRP is your problem -- I think beats is your problem. It may have modified something. Try searching the above-linked thread for answers. Honestly, there's no rush to get 4.2.2, so take your time finding the answer. It's better than wiping the phone just to install a small android update and having to redo everything on your phone again.

Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.

wvcadle said:
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
Click to expand...
Click to collapse
I need some help here - I have nexus 7 with 3G and Google (takju) with 4.2.1 installed.
I had it 'rooted" and installed TWRP .
AT the time I followed instructions to chand extension of some file to .bak - to prevent 'unrooting"
I do not remember which file I unfortunately changed.
Now I cannot install the 4.2.2 upgrade - the OTA fails because it boots into TWRP and after that I rrid several selections from TWRP screen (flash, reboot, etc) - but all attempts failed.
I have the upgrade files (bot .tar and .zip) on /sdcard directory but have no idea how to update to 4.2.2.
Tried manual flashing using adb command - all fails.
I do not have beats drivers installed
Can someone tell me how to uninstall TWRP? If the CWM recovery works with this upgrade, I would like to change from TWRP to CWM.
Or any other suggestion wold be appreciated.
I am really struggling with Android operating system the way it configured on Nexus 7 by Google - any simplest is a major pain!
Hope I can get out of this and operate the device instead of continuously meddling with operating system.
Thanks in advance
[email protected]