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.
Related
hi all. I already Unlock the Bootloader, I flash the Amon Ra 1.5.3, it works. I made the Nandroid backup, then after reboot it doesn't work. is going to original recovery (see triangle with exclamation mark in the middle). what can I do? I was trying several times but same results. Amon Ra recovery is working only until reboot... What I have done wrong? thanks in advance
You have to flash a ROM after flashing the Recovery for the Recovery to stick, if the same principle from the G1 transfers over to the N1... ie, flash Recovery, boot into it, flash a ROM, you are good to go.
I mean. it will not remain if I will not flash a custom rom?
Are you flashing from sd or fastboot?
from fast boot. i was following the steps from http://androidcommunity.com/forums/...ing-amon-ras-recovery-on-the-nexus-one-30499/.
A nandroid backup does not have the proper permissions/formatting for your system to boot.
You need to nandroid
then fastboot flash boot boot.img, etc
DELETE......
wow way for them to steal my outdated tutorial..... bastards
ovigt71 said:
hi all. I already Unlock the Bootloader, I flash the Amon Ra 1.5.3, it works. I made the Nandroid backup, then after reboot it doesn't work. is going to original recovery (see triangle with exclamation mark in the middle). what can I do? I was trying several times but same results. Amon Ra recovery is working only until reboot... What I have done wrong? thanks in advance
Click to expand...
Click to collapse
Have you already flashed (through OTA or manually) the last update released by google? If yes you need to delete (you must be root for this) the install-recovery.sh you find in /system/etc:
Code:
adb shell
cd system
cd etc
rm install-recovery.sh
By deleting this file I solved this problem of having to reflash the recovery after each rom reboot
ok. so, finally, someone can post one link or a explicit tutorial about how to install this recovery? at least one link would be good enough.. ... thanks
eug89 said:
Have you already flashed (through OTA or manually) the last update released by google? If yes you need to delete (you must be root for this) the install-recovery.sh you find in /system/etc:
Code:
adb shell
cd system
cd etc
rm install-recovery.sh
By deleting this file I solved this problem of having to reflash the recovery after each rom reboot
Click to expand...
Click to collapse
yes. i already install the update.... I was trying to root by MoDaCo way, but after root I was no able to enable the wireless. WIfi was completely out of order. Lucky me 'cose I already done the nandroid backup, otherwise........ so I install again the Amon Ra recovery and I roll back the backup.... please help with one good tutorial regarding root.
http://forum.xda-developers.com/showthread.php?t=612858
easist recovery can be tricky
do u have SDK?
Yes, I have.... usualy I go in recoveryy mode from "ADB reboot booloader recovery"..
Think i should write a recovery flashing tutorial?
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.
yesterday i rooted, and backuped my phone with clockwork. installed CM7 and it worked perfectly fine. i also restored my backup just to make sure i could go back. reinstalled CM7 once more and have been using it all day. today i decided i like all my default apps better on stock MT4G. so when i went to do the restore the process seems to work fine and i reboot the device to run my Stock image, but my phone wont go past the mytouch 4g splash screen. i can instally CM7 still and run it, but i want to go back to stock. Can someone help me figure out whats going on?
mumbo101 said:
yesterday i rooted, and backuped my phone with clockwork. installed CM7 and it worked perfectly fine. i also restored my backup just to make sure i could go back. reinstalled CM7 once more and have been using it all day. today i decided i like all my default apps better on stock MT4G. so when i went to do the restore the process seems to work fine and i reboot the device to run my Stock image, but my phone wont go past the mytouch 4g splash screen. i can instally CM7 still and run it, but i want to go back to stock. Can someone help me figure out whats going on?
Click to expand...
Click to collapse
You have to revert back to older Recovery 2.5.1.2 or you can install the new 3.0.0.6 as normal CWM won't able to handle it. This same issue has been covered many times. Read the quote below to better understand if you still have problem well then post back ill help.
jggimi said:
you are using the wrong version of Recovery to install the new kernel. I'm guessing #2, because it's very common for people to assume a higher number is better, and use CWM Recovery 3.0.0.5 with Froyo-based ROMs and hose things up really well.
Restoration options, if you are using CWM 3.0.0.5:
a) Restore from the Nandroid backup you made before overlaying your kernel. Oh, yeah, you can't, you didn't make one, otherwise you'd have already done that and wouldn't have posted....
b) Flash the appropriate CWM Recovery (2.5.1.2 for Froyo-based ROMs) using adb from your PC. Reboot into it, find the kernel you wanted to use, and reinstall it.
c) Install a Gingerbread-based ROM, such as CM7.
Pick a,b, or c. If you have any specific questions, please ask.
Click to expand...
Click to collapse
Just for preventive measures of a follow up question. I did the same thing you did, and when you try to flash CM7 again (because that is basically your only option) you might get stuck on the boot screen. In the recovery screen, go to advanced and clear your davlik cache before you flash it. Worked fine after that.
I don't know how to flash different recoveries. So I'm going to stick with cm7 till its updated.
Sent from my HTC Glacier using XDA App
mumbo101 said:
I don't know how to flash different recoveries. So I'm going to stick with cm7 till its updated.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Well use my old instructions on howto as you can manually flash it via terminal. Just put the 3.0.0.6 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 along with 3.0.0.6.img for this meth to work so I provided you with everything as you just download it and unzip them in root of your /sdcard so you will have standalone flash_recovery and recovery.img in it.
i used true blues method for getting cmr 3.0.0.6. it worked wonderfully. when i would boot into recovery using volume down and power it would say 3.0.0.6 at the top. i switched to 2.5.1.2 to flash icons. when i went back to 3.0.0.5 in rom manager, it now says 3.0.0.5 when i boot up with volume down and power. i tried reflashing the zip for 3.0.0.6, but it still shows 3.0.0.5. any idea what went wrong? any help is greatly appreciated.
cveez11 said:
i used true blues method for getting cmr 3.0.0.6. it worked wonderfully. when i would boot into recovery using volume down and power it would say 3.0.0.6 at the top. i switched to 2.5.1.2 to flash icons. when i went back to 3.0.0.5 in rom manager, it now says 3.0.0.5 when i boot up with volume down and power. i tried reflashing the zip for 3.0.0.6, but it still shows 3.0.0.5. any idea what went wrong? any help is greatly appreciated.
Click to expand...
Click to collapse
As long as recovery says 3.0.0.6, then you are good to go. I get 3.0.0.5 in rom manager too but the proper version in recovery. I think it was mentioned in the thread that it would read 3.0.0.5 in Rom Manager.
thanks for the quick response. i understand that, but what i'm saying is that when use volume down and power now, it still says 3.0.0.5.
cveez11 said:
thanks for the quick response. i understand that, but what i'm saying is that when use volume down and power now, it still says 3.0.0.5.
Click to expand...
Click to collapse
Flash it via the ADB commands.
download this file and store just the image on the SDcard of your phone....
adb shell
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Can i ask why you downgraded to flash icons, and not use the 3.0.0.6 that you were on?
cveez11 said:
thanks for the quick response. i understand that, but what i'm saying is that when use volume down and power now, it still says 3.0.0.5.
Click to expand...
Click to collapse
sorry cveez, i need to learn how to read.
i tried to flash with 3.0.0.6 and it failed. flash with 2.5.1.2 and it worked perfectly. then when i tried to go back to 3.0.0.6 i find myself stuck on 3.0.0.5. BTW i tried to flash with adb and it says flash image not found. i am very new to adb. used true blues method for adb and it finds my device. not really sure what to do now.
cveez11 said:
i tried to flash with 3.0.0.6 and it failed. flash with 2.5.1.2 and it worked perfectly. then when i tried to go back to 3.0.0.6 i find myself stuck on 3.0.0.5. BTW i tried to flash with adb and it says flash image not found. i am very new to adb. used true blues method for adb and it finds my device. not really sure what to do now.
Click to expand...
Click to collapse
go into the adb screen.
type
adb kill-server
adb devices
Click to expand...
Click to collapse
and see if sees your device.
If you serial number shows up turn on USB storage, download the file i attached then extract just the image to the root of the SDcard, not in a folder, just on the SD card. Then un-mount the SDcard from the computer....
Then type
adb shell
Click to expand...
Click to collapse
that will begin the commands for you to flash the image.
the c:\______ line will disappear and just show a "#"
then type
su
Click to expand...
Click to collapse
after you see that type
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
I am leaving for work. I will try this when I get home in the morning. Thanks for the help.
Sent from my HTC Glacier using XDA App
Drew updated the file to be compatible with the new version of cmr and it works great. Thanks for the help
Sent from my HTC Glacier using XDA App
How do you Flash this because I was thinking of flashing Royalginger
Flash it the way you flash any recovery, via fastboot or in the terminal emulator.
TeeJay3800 said:
Flash it the way you flash any recovery, via fastboot or in the terminal emulator.
Click to expand...
Click to collapse
What steps do I need to take
tvotony said:
How do you Flash this because I was thinking of flashing Royalginger
Click to expand...
Click to collapse
Store just the .img on your SDcard, then from ADB commands.
Code:
adb shell
su
flash_image recovery /sdcard/recovery.img
neidlinger said:
Store just the .img on your SDcard, then from ADB commands.
Code:
adb shell
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Thanks a lot
neidlinger said:
Store just the .img on your SDcard, then from ADB commands.
Code:
adb shell
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
And if that doesn't work (it didn't for me...I got a flash_image error possibly because my ROM doesn't contain the proper binary), the fastboot command is
Code:
fastboot flash recovery recovery.img
Its not going through when i type the commands
What error are you getting?
TeeJay3800 said:
What error are you getting?
Click to expand...
Click to collapse
Adb: not found
tvotony said:
Adb: not found
Click to expand...
Click to collapse
You have to setup ADB up first! See this thread for instructions on how to do that.
no but i will now
why dont flash from recovery? easier i guess. just boot to recovery then flash zip from sd card and follow the instruction.
weird is that afterward in the rom manager my cwm version is still 3.0.0.5
ayamjago said:
weird is that afterward in the rom manager my cwm version is still 3.0.0.5
Click to expand...
Click to collapse
According to option94 who made version 3.0.0.6, he says here that that is normal. What's really weird is that ROM Manager still says I have 2.5.1.2 installed!
TeeJay3800 said:
According to option94 who made version 3.0.0.6, he says here that that is normal. What's really weird is that ROM Manager still says I have 2.5.1.2 installed!
Click to expand...
Click to collapse
from within the Clockwork ROM manager it will only pick up officially supported recoveries. You must boot into recovery to see what version [actual] it is .
ayamjago said:
why dont flash from recovery? easier i guess. just boot to recovery then flash zip from sd card and follow the instruction.
weird is that afterward in the rom manager my cwm version is still 3.0.0.5
Click to expand...
Click to collapse
Because it is more "fool proof" to flash it manually. The flashing method do work but flashing manually is always recommended.
neidlinger said:
from within the Clockwork ROM manager it will only pick up officially supported recoveries. You must boot into recovery to see what version [actual] it is .
Click to expand...
Click to collapse
I know that, but I thought it would show the latest official version, which is 3.0.0.5. I'm not sure why it thinks I still have 2.5.1.2.
TeeJay3800 said:
I know that, but I thought it would show the latest official version, which is 3.0.0.5. I'm not sure why it thinks I still have 2.5.1.2.
Click to expand...
Click to collapse
maybe that was the last official one you flashed.... i really don't know