Okay, so I've installed Clockwork recovery on my Inspire, and as far as I remember, if you're on Froyo, you need 2.x.x.x, right? Well, if I choose to install an older version of CWM, I think it's 2.5.1.4, it gives me an error (an error occured while flashing your recovery). The last version of Rom Manager I had did the same thing with that version, but it at least had the option for 2 older 2.x.x.x versions.
Where can I get a functioning, older CWM?
Afaik everyone has changed their rom update scripts to support cw 3.*
Sent from my ADR6300 using XDA App
Okay. I was using LeeDroid and when I would go through a backup, it would lock at the HTC white screen. Everyone said it was because I'm on 3.X.X.X
2.5. 1.4 is screwed. Go to 2.5. 1.3
Inspired from my Inspire 4G using XDA Premium App
actually, the new 3.0.2.5 i thinkit is, works just fine
dylanf23 said:
actually, the new 3.0.2.5 i thinkit is, works just fine
Click to expand...
Click to collapse
Right on. Thanks, man.
Related
RESOLVED!
I flashed cm7, but not without making a nandroid of the stock rom. I tried restoring the backup and it would not make it to the boot animation. No errors or anything, same version of clockwork as before.
The only thing I didn't try was advanced restore. Would that do anything differently?
Sent from my HTC Glacier using XDA App
kimbernator said:
I flashed cm7, but not without making a nandroid of the stock rom. I tried restoring the backup and it would not make it to the boot animation. No errors or anything, same version of clockwork as before.
The only thing I didn't try was advanced restore. Would that do anything differently?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Being that you flashed CM7, and having troubles going back to 2.2.x you must be using 3.0.0.5 as a recovery image. You need 3.0.0.6, or a 2.x recovery image.
This thread [http://forum.xda-developers.com/showthread.php?t=986522] will help explain the ins and outs and how to flash 3.0.0.6.
Hey! I figured it out! And this should apply to all of us with mytouch 4gs.
The issue was that i was on clockwork 3.0.0.5, which i was on even when i backed up the stock rom. 3.0.0.5 allows for gingerbread flashing, but not froyo. So if you experience an issue like this, downgrade to 2.5.1.2 in rom manager and try recovering - lucky for me, even nandroids made in 3.0.0.5 were compatible with 2.5.1.2
kimbernator said:
Hey! I figured it out! And this should apply to all of us with mytouch 4gs.
The issue was that i was on clockwork 3.0.0.5, which i was on even when i backed up the stock rom. 3.0.0.5 allows for gingerbread flashing, but not froyo. So if you experience an issue like this, downgrade to 2.5.1.2 in rom manager and try recovering - lucky for me, even nandroids made in 3.0.0.5 were compatible with 2.5.1.2
Click to expand...
Click to collapse
That's what the thread i posted earlier explained. and showed you how to fix. It's sticked in the Q&A section.
What a breakthrough that was...I better write that down.
I was going to flash the Honeybread theme so I went into recovery and did a backup. I flashed the theme but my bottom bar was missing (due to the fact that I did a metamorph to remove the clock from bottom bar). I booted back into recovery and did a restore to the backup I did today. It went through the whole process and when it booted up it wanted me to go through a setup. What happened?
ATM I'm doing another restore to June 29th. Hopefully that works. I'm going to be pissed because it took me a while to set all my stuff up.
Sent from my PC36100 using XDA App
What version of ClockWorkMod are you running? Did you get it from RzoMManager?
Sent from my Xoom using Tapatalk
No. It's the Clockwork from solarnz. I restored another backup and it was fine. I have to fix it like I had it before but at least I don't have to start over.
I hate CWM. I wish we had AR on the Xoom.
Sent from my PC36100 using XDA App
Hear hear! The absence of the terminal in recovery is a GLARING OMISSION.
I just had the same thing, recovery using the latest from solarnz 3.2.0.0. rc4 100611 and have no apps. will try an older backup
edit: an older backup I had worked, odd
yoshitweaky said:
I just had the same thing, recovery using the latest from solarnz 3.2.0.0. rc4 100611 and have no apps. will try an older backup
edit: an older backup I had worked, odd
Click to expand...
Click to collapse
CWM sucks but it's all we have.
Sent from my PC36100 using XDA App
I have been using the twrp recovery for all from installs with no problems. In the directions for skyics is says you are supposed to use cwm. Is the a reason for that or is it personal preference?
Sent from my SAMSUNG-SGH-I727 using xda premium
I think its just on his experience. and that was comparing the new touch version versus the regular cwm. I use it fine. Had run into issues at one point where twrp didn't like one of the versions and I had to switch back to cwm to fix. but thats been fixed in the latest skyics and am now back on it.
so i downloaded a CWM touch recovery that claimed to be kexec compatible from another thread and pushed it to the phone. loaded up fine. what i found odd was that i though only v6.0+ CWM's were kexec compatible. this CWM, however, reads as v5.8.4.5
i don't run a kexec rom at the moment... i had it installed for a short stint with CM10. i've since switched back to synergy.
anyway, wondering if anyone can confirm that this CWM is indeed a kexec compatible recovery.
thanks!
byproxy said:
so i downloaded a CWM touch recovery that claimed to be kexec compatible from another thread and pushed it to the phone. loaded up fine. what i found odd was that i though only v6.0+ CWM's were kexec compatible. this CWM, however, reads as v5.8.4.5
i don't run a kexec rom at the moment... i had it installed for a short stint with CM10. i've since switched back to synergy.
anyway, wondering if anyone can confirm that this CWM is indeed a kexec compatible recovery.
thanks!
Click to expand...
Click to collapse
Yeah it's the cwm touch. You just edit a file and it's supposedly kexec enabled. I've been too chicken to try it though, just don't have time on my hands to flash back via Odin because I'm never home >. >
Sent from my SCH-I535 using xda app-developers app
I used cwm touch with the first kexec kernel/recovery package that required to reflash the kernel each reboot. I believe it was called "boosted v.01"...
Vorfidus said:
Yeah it's the cwm touch. You just edit a file and it's supposedly kexec enabled. I've been too chicken to try it though, just don't have time on my hands to flash back via Odin because I'm never home >. >
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I've used it and it worked with cm10 but not bean. Those are the only 2 kexec roms I've tried it on.
droidstyle said:
I used cwm touch with the first kexec kernel/recovery package that required to reflash the kernel each reboot. I believe it was called "boosted v.01"...
Click to expand...
Click to collapse
Yeah but that was just a kernel. I think Kexec has come a LONG way since then though.
I have been flashing (roms) for a while now devices including G2, HTC Hero, HTC Thunderbolt, Moto Razr, and now Galaxy S3. I don't typically post questions on any forums because I usually can find an answer with enough searching, it pains me to write this.
Problem: I can only flash certain roms on my Verizon SGS3.
I have no problem flashing unofficial aokp, unofficial cm10, and Synergy.
When I try to install different roms from xda and other websites i get the attached photo. These roms include paranoid android, miui, liquids jelly bean, and a few others.
My device is rooted, unlocked bootloader through ez unlock, running clockworkmod (touch) v5.8.4.5 via ez recovery.
Before I flash I always:
wipe data/factory reset
wipe cache partition
format system
wipe dalvik cache
Re-downloading has not fixed the issue. I'm sure im missing something simple any help would be warmly welcomed!
Thanks in advance all!
-Stumped S3 User
The problem is your running the wrong cwm recovery. 5 . something version causes problems with jb rom's. Surprising you got cm10 to run. Download cwm rom manager and install cwm touch 6.0.1.2 touch from in that application. EZ recovery does not offer that version of touch, but it does offer that version of regular. I don't see all the hype about ez recovery. That's definitely your issue.
Sent from my SCH-I535 using xda premium
annoyingduck said:
The problem is your running the wrong cwm recovery. 5 . something version causes problems with jb rom's. Surprising you got cm10 to run. Download cwm rom manager and install cwm touch 6.0.1.2 touch from in that application. EZ recovery does not offer that version of touch, but it does offer that version of regular. I don't see all the hype about ez recovery. That's definitely your issue.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Bingo!! Wrong version of CMW, just download e-z flasher from the play store and use it to flash either TWP or CMW. Easy peasy quick and easy.
I suggest you use twrp.
Twrp has bugs with jb rom's. Cwm regular or touch 6.0.1.2 is the most stable safe way to go. If your unsure at all, use cwm. Twrp on our devices at this time is NOT as stable as cwm, but does work effectively. If you use twrp, don't be surprised if you get a poor flash here and there.
Sent from my SCH-I535 using xda premium
annoyingduck said:
Twrp has bugs with jb rom's. Cwm regular or touch 6.0.1.2 is the most stable safe way to go. If your unsure at all, use cwm. Twrp on our devices at this time is NOT as stable as cwm, but does work effectively. If you use twrp, don't be surprised if you get a poor flash here and there.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Cwm 6.0.1.2 all day. Refuse to use anything else lol. Unless amon ra gets ported
Sent from my SCH-I535 using Tapatalk 2
Worked like a charm!
I downloaded rom manager, installed latest clock work, updated to touch, and it is working perfect! Thanks to all! The fun begins