Database Users

How do I get clockwork 2.5.1.2 back when I'm already in ext4? (solved)

So I have been on ext4 for a few days using quantum 2.5. Everything was working as expected there with clockworkmod 2.5.1.0 and 2.5.1.2 installed and available. This morning, I tried flashing the new midnight rom, but my file was corrupted so I went back to Mammon's Bonsai4All 1.0.4 with an ext4 kernel. Now, I can't get back into cwm 2.5.1.2. Bonsai4All should have a working recovery redirect, so I'm guessing I need to reinstall 2.5.1.2. The problem is, I can't flash the prepare.zip to ext4 with 2.5.1.0. So the question is, what do I need to push to the phone to get the modded recovery back? I have the prepare.zip and all other files from the onelickext4 1.3 and I'm not afraid of adb or using the terminal on my phone.

Boot into recovery. Goto advance. Select reboot recovery. That should bring you to v where you wanna be. If it don't then its time to odin
Sent from my SPH-D700 using Tapatalk

If you boot into CWM then go to advanced then reboot recovery that should put you in 2.5.1.2
Beat me to it.

mysteryemotionz said:
Boot into recovery. Goto advance. Select reboot recovery. That should bring you to v where you wanna be. If it don't then its time to odin
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
The problem is, that when I reboot recovery, it brings me back to 2.5.1.0. I have a working phone right now, so I don't feel like using Odin again, yet.
It seems like there should be a way to get the correct recovery back on the phone with the terminal or adb. I've only been using android since October, so it is taking some work to learn how everything is done in the android world. Luckily, I went to school for programming on linux, but I'm a little rusty.

found this tidbit in an the ext4 thread over at ppcgeeks
Please note that until other ROMs add support (namely the new recovery binary in /system/bin/recoveryfiles) I cannot guarantee recovery will function properly
Click to expand...
Click to collapse
So I'm going to try pushing the recovery file from the prepare.zip and see if that works.
edit: It works! I'm getting errors from missing bitmap files, but that should be pretty simple to copy over as well.

Bonsai4All 1.0.4 does not support ext4. I'm surprised your phone even boots, which leads me to believe that you may still be rfs.

DiGi760 said:
found this tidbit in an the ext4 thread over at ppcgeeks
So I'm going to try pushing the recovery file from the prepare.zip and see if that works.
Click to expand...
Click to collapse
Midnight has those files already
Sent from my SPH-D700 using Tapatalk

You could download the QuickBoot app from the Market. Selecting Recovery from within the app automatically boots the phone into Clockwork 2.5.1.2

siphuyoda said:
You could download the QuickBoot app from the Market. Selecting Recovery from within the app automatically boots the phone into Clockwork 2.5.1.2
Click to expand...
Click to collapse
He can't boot up so how would he get a app
Sent from my SPH-D700 using Tapatalk

You all misunderstand.
I can boot just fine. I was on Quantum 2.5 and switched to Bonsai4All 1.0.4, which was pre-ext4. I installed the ext4 kernel at the time of flashing, so the phone works.
No matter how I got into recovery after installing Bonsai4All, it went to 2.5.1.0. That includes using quickboot or reboot recovery from within recovery. And I can't flash anything with 2.5.1.0 since it won't flash to ext 4.
How I fixed it:
1. Remount as rw
2. Copy /system/bin/recoveryfiles/recovery and /system/bin/recoveryres/* from the prepare.zip to my phone.
3. Remount as ro
And voila! Now I can get into 2.5.1.0 and 2.5.1.2.

Check.to make sure you do indeed have ext4 working by using adb shell. I just don't see how the phone booted on bonsai if you have ext4 installed.
Sent from my Evo killer

I too have epic experience 2.0.07 working with ext4. I actually have the same problem he's having so I'm gonna try his method. It boots up fine and and works but can't get into CW 2.5.1.2. Funny thing is I can still flash zip files through regular CW. Probably because they're not roms. I've checked through adb and and it says I'm using ext4. I can also tell the differance to. My quadrant score is like 1536. I know quadrant it ain't real world but the dev of midnight rom has a video in his blog showing the differance. I'm pretty close to what he got.
Sent from my SPH-D700 using XDA App

musclehead84 said:
Check.to make sure you do indeed have ext4 working by using adb shell. I just don't see how the phone booted on bonsai if you have ext4 installed.
Sent from my Evo killer
Click to expand...
Click to collapse
The new Dual Kernel maybe? It bridges the gap between the two file systems.

musclehead84 said:
Check.to make sure you do indeed have ext4 working by using adb shell. I just don't see how the phone booted on bonsai if you have ext4 installed.
Sent from my Evo killer
Click to expand...
Click to collapse
You can make other DK28 roms work with ext4 by flashing an ext4 compatible kernel after flashing the rom. If I had just tried to flash bonsai without an ext4 compatible kernel, it would freeze at the samsung screen and I would have to Odin out of it. I made that mistake once already when I stopped paying attention to what I was doing.

It says (solved) but I don't see the solution. guess that means I'm still an android n00b.
Stuck at SAMSUNG screen (Help!)
I had CWM3 and EXT4
I flashed Quantum Rom 2.7
tried to flash Nebula Rom 1.6 but it didn't take cuz of EXT4
I flashed ReRFS.Format.ROM.DK28-signed.zip to bring me back to RFS
reboot - hangs at SAMSUNG splash
reboot back into recovery, now 2.5.1.0
tried flashing Nebula Rom 1.6 - but reboot still hangs at SAMSUNG
tried flashing Quantum Rom 2.7 - but reboot still hangs at SAMSUNG
tried Odin, but I don't know what to do with Odin except flash the DK28 modem, so I did that, but it didn't help
so I'm basically trying a bunch of crap without knowing what I am doing, and as fun as this is - I'm kinda stuck - just going in circles

plus I keep seeing "E:can't open /cache/recovery/log" while in ClockworkMod Recovery 2.5.1.0 - and when I do the Reboot Recovery as people have said to make it go to 2.5.1.2, it still just hangs at the SAMSUNG splash...

I found SPH-D700-DK28-8G-REL.tar.md5 and flashed that and now I'm back in business - **phew**

Cobaltikus said:
It says (solved) but I don't see the solution. guess that means I'm still an android n00b.
Stuck at SAMSUNG screen (Help!)
I had CWM3 and EXT4
I flashed Quantum Rom 2.7
tried to flash Nebula Rom 1.6 but it didn't take cuz of EXT4
I flashed ReRFS.Format.ROM.DK28-signed.zip to bring me back to RFS
reboot - hangs at SAMSUNG splash
reboot back into recovery, now 2.5.1.0
tried flashing Nebula Rom 1.6 - but reboot still hangs at SAMSUNG
tried flashing Quantum Rom 2.7 - but reboot still hangs at SAMSUNG
tried Odin, but I don't know what to do with Odin except flash the DK28 modem, so I did that, but it didn't help
so I'm basically trying a bunch of crap without knowing what I am doing, and as fun as this is - I'm kinda stuck - just going in circles
Click to expand...
Click to collapse
Clarification on how I solved my problem is below. I had a usable phone the entire time, I just didn't have the cwm I needed.
It almost sounds like a your problem is a kernel issue, except you have it with so many roms. There may have been an error in the file system conversion somewhere that is causing you trouble. You don't usually get the "E: can't do whatever" error if your cwm is compatible with your file system.
My suggestion to you would be to Odin back to a good image. You do it basically the same as doing the modem. Uncheck everything on the left. Put your .pit in the pit section. Put your .tar file (or .tar.md5) into the box that says pda (the first box). Then, plug your phone in and flash.
After that, you can run the one-click root and recovery to get root and cwm 2.5.1.0 back. Then you can start playing again. Remember, if you use ext4 then you must have an ext4 compatible kernel. If you use rfs, you must use an rfs compatible kernel. You can use any rom on ext4 if you flash an ext4 kernel immediately after you flash the rom and before you reboot the phone. If you forget to do the kernel, you will hang at the samsung screen. Some roms are ext4 or rfs only, and some have a dual file system kernel. Currently, you can mix and match any dk28 kernel with any dk28 rom. Don't try to mix kernels and roms from different builds, though.
Now for further clarification on how I got 2.5.1.2 back when using a rom that didn't have it baked in:
DiGi760 said:
How I fixed it:
1. Remount as rw
2. Copy /system/bin/recoveryfiles/recovery and /system/bin/recoveryres/* from the prepare.zip to my phone.
3. Remount as ro
And voila! Now I can get into 2.5.1.0 and 2.5.1.2.
Click to expand...
Click to collapse
I guess my solution was about as clear as mud. In order to do this, it helps to be somewhat comfortable using a command line.
I used the prepare.zip that was a part of the original ext4 conversion to get the recovery files. When you open the prepare.zip it has the standard flashable zip structure and is organized according to where the files are supposed to end up on your phone. Open the zip, open the system folder, open the bin folder and copy the folder named "recoveryres" to your sd card. Then open the "recoveryfiles" folder and copy a file named "recovery" to your card as well. Put these files somewhere easy to find, like a folder named "cwm" at the root of your card.
Next, use a terminal emulator to remount your phone to rw so you can write to the protected areas. Most of our roms included a small remount script, so all you have to do is type "remount rw" without the quotes. Later you will use "remount ro" to make things read only again.
Now, you're going to copy those files that you got from the prepare.zip to their proper places on your phone. You did leave them somewhere easy to find, right?
Copy "recovery" to /system/bin/recoveryfiles/ and copy the "recoveryres" folder to /system/bin/. You may have to watch and make sure it doesn't skip any files when copying the recoveryres folder.
After that, remount ro and you are done.

[RECOVERY] 3e Recovery Modded w/ No Verification

NOTE
This is took from untermensch's thread in the Vibrant forum so I take no credit for this (http://forum.xda-developers.com/showthread.php?t=833423)
I have noticed some of you are having issues after installing a new kernel or rom, when you boot into recovery you now have 3e, which does not allow unsigned zips to be flashed. With this version of 3e it has no-verification check, now allowing you to flash whatever you want.
This zip has
1) 3e recovery modified to disable signature checking
2) disables the forced wipe after installing any update.
Instructions
1)Download and extract the file below
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system
3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there
4)Now, reboot and you should have a modded 3e recovery with no signature verification
You can either leave the modded 3e recovery or you can now flash CWM via Rom Manager
**Just like anything else, I am not responsible if this bricks your phone, this is fairly simple, follow the guide...Do at your own risk**

Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.

designgears said:
Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.
Click to expand...
Click to collapse
I done the exact method above and works fine for me...
Place extracted recovery file in /system/bin/ , reboot and flash cwm via rom manager, works perfectly fine...the reason I posted was, if you read Hardcores thread, and seen this in other threads, that after flashing his kernel, when they goto recovery they now have 3e (depending on which method when entering recovery)..alot of people have done it the way I posted with no issues...im not trying to argue with you, you by far know more then me, just posting what worked for me and some others

sounds like a good idea for the people that updated to Rogers froyo that has the 3e recovery. You could just flash a new kernel, but this is definately a good alternative.
Thanks
Sent from my SGH-I897 using XDA App

If you look at Darkyy's rom he has a script that does this.

Thanks, this works flawlessly on a Rogers Froyo Stock. Now I have CWM working and good to go. The only thing left would be to apply some kind of lagfix.

Tested and works with Rogers 2.2 Rom. Thanks

skorchir said:
Tested and works with Rogers 2.2 Rom. Thanks
Click to expand...
Click to collapse
I also have.
Thanks

Works great on Rogers 2.2. Thanks

I tested it on Galaxy S i9000m bell and it work A+
i do not have to flash cf-boot to make unsigned zip to be installed
thanks a lot for your hard work.
only thing is botton function become different then original 3e
but its working A+

I'm a little confused on how the Recovery works..... I have a I897 that I flashed Cognition 2.3b8 to with ROM Manager/CWM and when I chose "reboot into recovery" from ROM Manager from inside Cognition, it worked fine after reloading packages once. A few days ago, I flashed Perception 10.1 with the firebird kernel. After noticing the battery didn't last as long as it used to with Cognition, I did some research and found the SpeedMod kernel K12L. Before I flashed it, I did a backup from ROM Manager which rebooted into CWM with no problems and did the backup with no problem. I have since flashed K12M and K12N. Now I thought I would give Cog 3.0 a shot and wanted to back up my current config with Perception 10.1/SpeedMod K12N. From ROM Manager, I chose to backup, named my backup and the phone rebooted into 3e Recovery and gave the errors you listed above but I don't understand why? Is it because of the I9000 kernel which doesn't make sense since Firebird is a I9000 kernel. Was it from flashing SpeedMod? Also noticed, that only the volume up/down buttons worked, not the power button which is also the select key. Only way out was to 3 button reboot (or pull the battery) which rebooted into CWM and then initiated the ROM Manager backup.
Any ideas why? Also, if I was to ODIN flash JH6 back to the phone, would that restore the Stock 2e Recovery? Sorry for the long post, but I'm still trying to learn this stuff and think you guys are awesome. The captivate would be a crappy phone if it wasn't for you all.

I guess if I had read your second post a little closer I would have seen that flashing SpeedMod causes it. I used your fix in the OP and when I tell it to "Reboot into Recovery" from ROM Manager, it boots into what I assume is 3e (Goes by real quick) and shows something about MOVI and verification and then boots into CWM Recovery v2.5.1.2. If I 3 button boot into recovery, it boots into CWM v2.5.1.0 SpeedMod ULFK. Seems to work now but I'm still confused. Thanks again.

Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.

davidis57 said:
Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.
Click to expand...
Click to collapse
Use a terminal emulator or adb shell and type...
Code:
chmod 777 /system/bin/recovery
That should give r/w permission to the file, ...i just tested to verify it and it worked for me. also if you have Root Explorer you can just long press the file and select Permissions and check all the boxes.

Exact the same thing is happening to me! Beforehand I had flashed CF Root to get Superuser also at the same time when rooting. I Still can boot into recovery with 3BR and come into the speedmod ULFK settings. Speedmod introduces 3e and you need signed packages. You must have 2e for this I assume!? Can anyone tell me what goes wrong?

Im using the Speedmod kernel and it always pissed me off that everytime I wanted to flash somethng via CWM that I had to pull the battery and restart my phone for it to finish because of the 3e 'no signed packages'
I did the steps in the OP and I noticed that I didnt even have a recovery file in system/bin but I put it in there anyway. I rebooted and flashed a different modem just to check and sure enough, it worked. Now I dont have to worry about pulling my battery and having to reboot my phone everytime I want to flash something.
Thanks for this!

Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?

davidis57 said:
Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?
Click to expand...
Click to collapse
Once you install cwm and reboot back into 3e, select reinstall packages, it will install cwm and then load into it , if it doesn't then the file didn't copy over, make sure it replaces it ok, I've used this quite a few times and it works everytime, and everyone that has posted has not had an issue, so it does work
Sent from my SGH-I897 using XDA App

It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App

davidis57 said:
It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Try starting over, delete the recovery file and also delete the update.zip on the root of the sdcard, then copy the modded recovery over to /system/bin/ , then open rom manager and install cwm again, something could have happened with the update.zip, cause if you are able to get into 3e and select reinstall packages and it actually starts but errors out with the update.zip, then something could possibly be wrong with the update.zip .. it might restart after you select reinstall packages, but it should then load in to cwm, if it doesnt and boots back into android, then go into rom manager and select restart recovery and see if that works

Issues with clockwork recovery backup feature?

I recently did a back up if my stock mt4g using clockwork. When I went to do a restore of that rom and rebooted it stayed stuck on the mt4g load screen. Anyone else have this problem? Did I do something wrong?
Sent from my HTC Glacier using XDA App

what version of clockwork did you use to make the backup?

3.0.0.5
Sent from my HTC Glacier using XDA App

spokenjeremy said:
3.0.0.5
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Welcome to brick world, that's exactly what destroyed my phone and, like you, I was running 3.0.0.5 If you ever do get the phone working again let me know how you did it, please?
Not sent from my MyTouch 4G because it's a brick now!

xs11e said:
Welcome to brick world, that's exactly what destroyed my phone and, like you, I was running 3.0.0.5 If you ever do get the phone working again let me know how you did it, please?
Not sent from my MyTouch 4G because it's a brick now!
Click to expand...
Click to collapse
The reason your phone appears to be bricked is it (CWRM 3.0.0.5) is a ext4 recovery image, and 2.2 is a ext3 ROM....
. If you find a 2.x version of CWRM you can flash it via the ADB commands and restore the phone.
OR
boot into recovery and flash the CM7 w/ gapps then download CWRM ( the free one ) and flash 2.x that way. You'll have to scroll to the bottom and select one of the 2.x recovery images.
If you can get into Recovery or into fastboot your phone is not truly bricked.

I have CM7 installed and Rom Manager, but when i try to flash an older recovery it says it cannot be flashed. How exactly would you flash the 2.X version via ADB? Thanks.

xs11e said:
Welcome to brick world, that's exactly what destroyed my phone and, like you, I was running 3.0.0.5 If you ever do get the phone working again let me know how you did it, please?
Not sent from my MyTouch 4G because it's a brick now!
Click to expand...
Click to collapse
You nor he is bricked.
Pentlander said:
I have CM7 installed and Rom Manager, but when i try to flash an older recovery it says it cannot be flashed. How exactly would you flash the 2.X version via ADB? Thanks.
Click to expand...
Click to collapse
If you can get into CwM recovery then just flash my zip and use the 3.0.0.6 recovery that is included. Then make sure that you make/restore all backups from recovery and not rom manager. Rom manager is not compatable with CwM 3.0.0.X when it comes to making nandroids.

Thanks a lot, but i keep running into and issue at the recovery. I followed the instructions from your thread, and i got into the blue recovery screen, but it says
"E:Can't mount CACHE:recovery/command
E:Can't mount DATA:data/recovery/log"
And the only option to restore is the Applysdcard:update.zip and that fails

Pentlander said:
Thanks a lot, but i keep running into and issue at the recovery. I followed the instructions from your thread, and i got into the blue recovery screen, but it says
"E:Can't mount CACHE:recovery/command
E:Can't mount DATA:data/recovery/log"
And the only option to restore is the Applysdcard:update.zip and that fails
Click to expand...
Click to collapse
So, that is the stock recovery. You need to choose the 3.0.0.5 version from "All ClockworkMod recoveries" if using my zip. If that wont work, try sending a new recovery via fastboot or terminal emulator.
You can set up adb/fastboot by checking out the link in my sig and using the command (make sure you rename the recovery to recovery.img for ease of use)
Code:
fastboot flash recovery recovery.img
or you can try terminal method by placing the recovery on your sd card and renaming it recovery.img Then open up TE and type "su" then the flollowing
Code:
flash_image recovery recovery.img
If that doesnt work, then let me know and we will find some other things to try.

Whoops haha. Thanks for all the help it's working great now

Pentlander said:
Whoops haha. Thanks for all the help it's working great now
Click to expand...
Click to collapse
What step got it working again for you?

neidlinger said:
The reason your phone appears to be bricked is it (CWRM 3.0.0.5) is a ext4 recovery image, and 2.2 is a ext3 ROM....
If you can get into Recovery or into fastboot your phone is not truly bricked.
Click to expand...
Click to collapse
Can't do either.

[Q] Help With ClockworkMod Recovery Downgrading

Hello,
I am currently running Rom Manager 3.0.1.0 with ClockworkMod Recovery version 3.0.0.6. I'm trying to install GorillaSense DHD-MT4G Revolution theme on my phone but, I can't seem to install the update due to the ClockworkMod version. I need to downgrade to 2.5.1.2. When I do this through the Rom Manager it states that I have successfully flashed ClockworkMod Recovery but when I reboot into recovery, it doesn't load.
The versions available to me is 3.0.0.6 and 2.5.1.4. Is there any way I can get access to 2.5.1.2 again?
Any help would be appreciated. Thanks.

clone132 said:
Hello,
I am currently running Rom Manager 3.0.1.0 with ClockworkMod Recovery version 3.0.0.6. I'm trying to install GorillaSense DHD-MT4G Revolution theme on my phone but, I can't seem to install the update due to the ClockworkMod version. I need to downgrade to 2.5.1.2. When I do this through the Rom Manager it states that I have successfully flashed ClockworkMod Recovery but when I reboot into recovery, it doesn't load.
The versions available to me is 3.0.0.6 and 2.5.1.4. Is there any way I can get access to 2.5.1.2 again?
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Well if you have Rom Manager 3.0.1.0 then yes you can flash Recovery 2.5.1.2 by going to Rom Manager and go down to the last option "All clockworkmod recoveries". Find 2.5.1.2 from the list and it will flash it for you.

Thank you for your quick reply. My problem lies in the fact that Rom Manager states that I have successfully flashed 2.5.1.2 but when I try load boot into recovery the recovery does not load.

clone132 said:
Thank you for your quick reply. My problem lies in the fact that Rom Manager states that I have successfully flashed 2.5.1.2 but when I try load boot into recovery the recovery does not load.
Click to expand...
Click to collapse
Well in that case manually flash it via terminal. Just put the 2.5.1.2 recovery.img in SDCard and flash it.
HKM said:
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
cp /sdcard/flash_image /system/bin [hit enter]
flash_image recovery /sdcard/recovery.img [hit enter]
Click to expand...
Click to collapse
You will need flash_recovery file which you can find by using search function along with 2.5.1.2.img this meth works as I did it always.
EDIT: Sorry if you can't find it but here is the atth as I keep backup of almost everything on mSD.BkP so download it and unzip them in root of your /sdcard so you will have standalone flash_recovery and recovery.img in it.

Thanks for all your help. That worked perfectly.
Sent from my HTC Glacier using XDA App

clone132 said:
Thanks for all your help. That worked perfectly.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
No problem glad could help, thats why I love console(terminal) once you understand SC and basic *nix arc you can virtually rip apart anything without any GUI frame.
Sent from my HTC Glacier

BlackSHELF said:
Well in that case manually flash it via terminal. Just put the 2.5.1.2 recovery.img in SDCard and flash it.
You will need flash_recovery file which you can find by using search function along with 2.5.1.2.img this meth works as I did it always.
EDIT: Sorry if you can't find it but here is the atth as I keep backup of almost everything on mSD.BkP so download it and unzip them in root of your /sdcard so you will have standalone flash_recovery and recovery.img in it.
Click to expand...
Click to collapse
Had a similar issue and followed your directions above in terminal. After I enter in the last line and hit enter, is it supposed to show something going on because it just goes to the next line. I downloaded your attached clockwork file and put it on the root of my SD card. Thanks for any help.

boroarke said:
Had a similar issue and followed your directions above in terminal. After I enter in the last line and hit enter, is it supposed to show something going on because it just goes to the next line. I downloaded your attached clockwork file and put it on the root of my SD card. Thanks for any help.
Click to expand...
Click to collapse
I don't quite remember what happens after you enter the last command on the terminal but, the only command I entered when I downloaded the files and extracted it to the root was "su[enter]
flash_image recovery /sdcard/recovery.img[enter]"
After that I was able to boot into recovery.
Another option is deleting the copy of the recovery in your SD card and redownloading it with ROM Manager. Just go to: /sdcard/clockworkmod/download/mirror1.kanged.net/recoveries. Delete recovery-clockwork-2.5.1.2-glacier.img, redownload and try loading it with Rom Manager again.
Hopes this helps.

CWM-Rom manager not working on N7 JB 4.2.1

Is anyone else having loads of problems with clockwork mod and rom manager since updating to 4.2.1
For me RM doesnt do anything and I CWM keeps will not re-flash a backup unless its 4.2.1. Even though I copy n past to new directory where CWM keeps backups but will not reflash them. Also everytime after I use CWM it seems to delete itself and i have to reflash via the command line. Help welcome. Thx in advance....
Update: Not sure if its RM or CWM. Have just worked out CWM is deleting itself everytime after use. IT doesnt leave any other option once you try to re-boot device from CWM....

veroby said:
Is anyone else having loads of problems with clockwork mod and rom manager since updating to 4.2.1
For me RM doesnt do anything and I CWM keeps will not re-flash a backup unless its 4.2.1. Even though I copy n past to new directory where CWM keeps backups but will not reflash them. Also everytime after I use CWM it seems to delete itself and i have to reflash via the command line. Help welcome. Thx in advance....
Update: Not sure if its RM or CWM. Have just worked out CWM is deleting itself everytime after use. IT doesnt leave any other option once you try to re-boot device from CWM....
Click to expand...
Click to collapse
There's a file in /system that you should either rename or delete called: recovery-from-boot.p
That reloads the stock Android recovery at each reboot. Then once you have renamed/deleted it, reflash CWM Recovery again from the command line and it should stick now.
You're using the latest CWM Recovery correct? I don't use RM or CWMR at all (TWRP), so I may not be able to totally help out.

RMarkwald said:
There's a file in /system that you should either rename or delete called: recovery-from-boot.p
That reloads the stock Android recovery at each reboot. Then once you have renamed/deleted it, reflash CWM Recovery again from the command line and it should stick now.
You're using the latest CWM Recovery correct? I don't use RM or CWMR at all (TWRP), so I may not be able to totally help out.
Click to expand...
Click to collapse
Hey thx - I have always used them and found them to be easy tools in the past. Dont really want to change to TWRP but it seems all recommendations are leaning towards and its the way to go with 4.2.1. Thx again... I have to ask why that file exist in the first place. Just to catch donkeys like me out.....Also if you know and are still around. Is there a way to restore old backups from 4.1.1

veroby said:
Hey thx - I have always used them and found them to be easy tools in the past. Dont really want to change to TWRP but it seems all recommendations are leaning towards and its the way to go with 4.2.1. Thx again... I have to ask why that file exist in the first place. Just to catch donkeys like me out.....Also if you know and are still around. Is there a way to restore old backups from 4.1.1
Click to expand...
Click to collapse
I've had no issues flashing 4.1.1/4.1.2 ROMs to 4.2.1 and vice versa...but again I'm using TWRP Recovery.
The file is in the stock images from Google, and it's there to reload stock Android recovery at boot...other than that I'm not sure of the exact reasoning.
I know that Android 4.2 has multi-user support, and that has been the cause for many issues with 4.2 in general due to it creating a folder /sdcard/0...so flashing multiple 4.2 ROMs without the latest CWM Recovery version 6.0.1.9 would cause another folder created there at /sdcard/0/0...and so on. If you created another user, they would have their own folder at /sdcard/1...and so on.
I would make sure that you have the latest CWM Recovery flashed to your device, then put your backup in the correct folder. From what I remember when using RM and CWM, there's the folder for your backup and then one level up from that there's the blobs folder, you'll need BOTH of those in order to restore things, as the blobs folder is the backup.