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.
Related
I have a rooted VZ GS3 with SU, ROM Manager, some Titanium frozen apps. Wanting to load a ROM but need to backup first. Whenever I attempt to backup with CWM (5.8.4.8) I get "Error while backing up boot image!". There is plenty of space so any idea what I am missing?
Bump. I'm having the same issue. My Cwm doesn't show my external sdcard either. It used to show internal sdcard and external sdcard but after soft bricking and using Odin to flash a Rom I lost that ability.
Sent from my SCH-I535 using xda app-developers app
same problem
i also have same problem
Is that a version of CWM Touch?
I believe this is a common issue, at least when I was having it and researched, and the accepted fix is to use a non-touch CWM. I'd recommend 6.0.1.0 as it has the ability for kexec and ensures you won't have an issue with flashing aftermarket kernels
Sent from my SCH-I535
Josolanes said:
Is that a version of CWM Touch?
I believe this is a common issue, at least when I was having it and researched, and the accepted fix is to use a non-touch CWM. I'd recommend 6.0.1.0 as it has the ability for kexec and ensures you won't have an issue with flashing aftermarket kernels
Sent from my SCH-I535
Click to expand...
Click to collapse
This!
Verified the issue is with CWM Touch. I reverted to the non-touch version, and I had no issues backing up.
Try using a different version of CWM touch. I have trouble backing up and restoring with touch too
I have no issues with K-exec CWM http://goo.im/devs/BeansTown106/SGS3vzw/cm9/d2vzw_recovery.img
Josolanes said:
Is that a version of CWM Touch?
I believe this is a common issue, at least when I was having it and researched, and the accepted fix is to use a non-touch CWM. I'd recommend 6.0.1.0 as it has the ability for kexec and ensures you won't have an issue with flashing aftermarket kernels
Sent from my SCH-I535
Click to expand...
Click to collapse
6.0.1.0 should do it. Also, make sure you are selecting the option to back up to the internal sdcard and not the external. That one took me a few minutes to realize as i don't have a 2nd sd card in my phone.
So I installed Clockwork mod touch via terminal emulator and the image on their site. It installs fine and works.....not really.
When I get into recovery and attempt to perform a backup of my current rom it simply says an error has a occured. this happens weather I boot into recovery to do it manually or i attempt to do it through rom manager.
Any ideas of what could be wrong?
Try installing EZ-Recovery from the market, then flash CWM Touch from there. It's a one click flash to recovery, no terminal commands.
Sent from my SCH-I535 using xda app-developers app
Vorfidus said:
Try installing EZ-Recovery from the market, then flash CWM Touch from there. It's a one click flash to recovery, no terminal commands.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
jesus that app made it so much simpler. too bad it's still not working correctly. Now I'm wordering if the img got corrupted somehow during download to the phone.
After redownloading and flashing it the error is still happening. Regular CWM Recovery works perfectly. Touch...still getting errors. Basically when I click backup it says "backing up boot image" then nothing happens and it goes right back the menu. When I click it again I get the erroer message "Error while backing up root image"
One thing I've noticed is, even with CWM Touch flashed, rom manager still sees it as CWM Recovery 5.8.4.9
Is it possible it just doesn't like synergy?
Yeah I had the same problem when I installed CWM touch using the adb push method. Wouldn't backup, backup was fine with the non-touch version. However, installing via ez-recovery worked.
jasondhsd said:
Yeah I had the same problem when I installed CWM touch using the adb push method. Wouldn't backup, backup was fine with the non-touch version. However, installing via ez-recovery worked.
Click to expand...
Click to collapse
even using ez-recovery didn't work for me.
Hitman3984 said:
even using ez-recovery didn't work for me.
Click to expand...
Click to collapse
Same issue for me. Looking for possible solutions.....
SiXandSeven8ths said:
Same issue for me. Looking for possible solutions.....
Click to expand...
Click to collapse
glad I'm not the only one.
Also noticed tonight smart alert isn't working after flashing to synergy. I thought maybe haptic feedback in power saving could be the cause but it isn't.
Edit: Tried again for the hell of it and this time I pointed to the cwm touch apart of ezrecovery and not the custom option by chossing the file and it now works.
All of that said rom manager and the cwm touch don't seem to work well together(im guessing unless you purchase
?) When you make a backup manually from going into recovery rom manager doesn't see it. CWM Touch also doesn't see the recovery made from non touch made in rom manager. Also Clockwork mod also still shows recovery as cwm 4.8.4.9
I'm relatively experienced in flashing roms but not ALL things root so this could be normal and just how things work.
Smart alert, still doesn't work.
All of a sudden yesterday my phone started boot looping while I was running Invisiblek's CM10. I finally got that sorted out, and used ODIN to get me to the rooted version of the stock ROM. However, now when I flash custom ROMs, I get a boot loop and have to restore back to the rooted version of stock. I've tried Invisiblek's CM10 again, Bean's... oh, and my CWM background is missing and is just black. I've also noticed(not sure if this could be why) that when I go to the mount section under CWM, both system and data keep defaulting to unmounted. Any suggestions?
Have you been using ezrecovery to flash recoveries before flashing ROMs??
Sent from my SCH-I535 using Tapatalk 2
hopesrequiem said:
Have you been using ezrecovery to flash recoveries before flashing ROMs??
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Hm, no. The installation instructions never made any mention of ezrecovery. Is that my problem?
Flashed CWM through ezrecovery. CWM is working again it appears. Thank you very much!!
Krog216 said:
Hm, no. The installation instructions never made any mention of ezrecovery. Is that my problem?
Click to expand...
Click to collapse
What recovery are you using?
Sent from my Synergy GS3
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
I updated to MF1, and it changed my recovery from ClockWork Touch to a much more basic recovery mode (rom manager says CWR and TWRP are both installed). I tried to flash basic clockwork using rom manager and as it reboot I got a message saying "software not authorized" and it would not boot.
I just used ODIN to flash the VRALEC boot chain which allowed the phone to boot. I still seem to have still have MF1. Step 6 here http://forum.xda-developers.com/showthread.php?t=2046439 says to then install the correct boot chain, but i dont see one for MF1 yet.
I then tried ODIN to flash CWR from the the above post with the same results (had to re odin vralec).
1. Should I ODIN the VRBMD3 boot chain in the mean time?
2. How do I get ClockWork Recover for MF1, touch or regular?
blindguyinanorgy said:
I updated to MF1, and it changed my recovery from ClockWork Touch to a much more basic recovery mode (rom manager says CWR and TWRP are both installed). I tried to flash basic clockwork using rom manager and as it reboot I got a message saying "software not authorized" and it would not boot.
I just used ODIN to flash the VRALEC boot chain which allowed the phone to boot. I still seem to have still have MF1. Step 6 here http://forum.xda-developers.com/showthread.php?t=2046439 says to then install the correct boot chain, but i dont see one for MF1 yet.
I then tried ODIN to flash CWR from the the above post with the same results (had to re odin vralec).
1. Should I ODIN the VRBMD3 boot chain in the mean time?
2. How do I get ClockWork Recover for MF1, touch or regular?
Click to expand...
Click to collapse
1. No, you don't have to change the bootchain. Vralec is just an old ics bootchain and should run fine.
2. http://forum.xda-developers.com/showthread.php?t=2096735
Use ez recovery to flash the most recent CWM recovery, touch or non-touch should both work great. Don't use rom manager anymore until it's updated, that's the second report I've seen of it doing that.
Sent from my SCH-I535 using Tapatalk 2
Did you ota to mf1 by any chance? Im pretty sure your boot loader was relocked.
Sent from my SCH-I535 using xda premium
Watoy said:
Did you ota to mf1 by any chance? Im pretty sure your boot loader was relocked.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I did OTA. I can still get into recovery, it is just not CWR.
BadUsername said:
1. No, you don't have to change the bootchain. Vralec is just an old ics bootchain and should run fine.
2. http://forum.xda-developers.com/showthread.php?t=2096735
Use ez recovery to flash the most recent CWM recovery, touch or non-touch should both work great. Don't use rom manager anymore until it's updated, that's the second report I've seen of it doing that.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
EZ-Recovery worked, but i also think i did something different inside CWR. It asked me if I wanted to disable something and this time I said yes.
blindguyinanorgy said:
EZ-Recovery worked, but i also think i did something different inside CWR. It asked me if I wanted to disable something and this time I said yes.
Click to expand...
Click to collapse
Good, if you say no it'll reinstall the stock recovery and you don't want that. The recovery you were seeing is the stock recovery, very basic with the hardly any options.
Sent from my SCH-I535 using Tapatalk 2