Database Info

[Q] any alternatives to the ROMmanager method?

i tried flashing a CM rom with ROMmanager. but that program isn't working on my phone for some reason. every time i try to reboot the phone into the clockworkmod recovery screen, it just takes me to the phones normal recovery screen. i'm a bit of a noob because i've never done this before, so if anyone could give me an alternative to flashing a custom rom or just help me fix ROMmanager, that would be awesome. (i also planned on installing an overclocking kernel, so i don't know if other methods would have any effect on me being able to do that or not.)

try flashing with rsd lite 4.9

lumberjack40 said:
i tried flashing a CM rom with ROMmanager. but that program isn't working on my phone for some reason. every time i try to reboot the phone into the clockworkmod recovery screen, it just takes me to the phones normal recovery screen. i'm a bit of a noob because i've never done this before, so if anyone could give me an alternative to flashing a custom rom or just help me fix ROMmanager, that would be awesome. (i also planned on installing an overclocking kernel, so i don't know if other methods would have any effect on me being able to do that or not.)
Click to expand...
Click to collapse
While you are still on stock rom, the stock recovery will keep coming back on every reboot. Try flashing clockworkmod recovery from within Rom Manager, let the phone reboot and then flash it again. You should be able to flash a Custom Rom now.
This is how it worked for me.

DirkGently1 said:
While you are still on stock rom, the stock recovery will keep coming back on every reboot. Try flashing clockworkmod recovery from within Rom Manager, let the phone reboot and then flash it again. You should be able to flash a Custom Rom now.
This is how it worked for me.
Click to expand...
Click to collapse
well thats the problem. i flashed the clockworkmod recovery screen, but it's still taking me to the phones normal recovery screen.

Try flashing an alternate recovery then flash clockwork again. I had a similiar problem and this helped me.
Sent from my ADR6300 using Tapatalk

Rooted i9023, some help needed please!

Ok guys so I have managed to root my i9023 and flash clockwork recovery which was all good, I set about flashing some new roms via rom manager, again, all good.
So now I settle on this cm7 based rom which I love, used anim mod to get some nice transitions, then I used font changer.
All was good, then I decided that the font I was using was a bit ott so I decided to change it again, upon reboot it starts boot looping, bollocks !!!
So I try to get into clockwork recovery, and it seems to have gone back to the stock bootloader, grrrrr
I re flash clockwork, wipe / clear etc... then flash the rom again, but it would not flash, so I went to my backup of stock n flashed that, all good.
I then install rom manager again and flash the rom I liked again, this time no problem, but when it loads up the home button and search button are not working
So i decide on a factory reset, I select wipe everything including sd just to be sure but it comes up "error null"???
So now I wipe the sd manually and then do the reset and it works, ok, I re load everything on from scratch and all is good, but when I installed rom manager it says that clockwork recovery IS NOT installed again
Can anyone here work out from my ramblings WTF is going on???
I dont get why the font changer all of a sudden caused a boot loop, as I had changed font about 15 times with it without issue, also why clockwork recovery will not stick anymore after a reboot, when before it did and I have not changed a thing!
Cheers!!!

Rename install-recovery.sh in system/etc to something else, flash cwm recovery again, this time it'll stick until you install a stock rom again.
Rom manager is causing more problems than it's saving time, hence I don't use it.
Sent from my Nexus S using XDA App

Thanks for the reply, can you go into detail on what exactly I need to do to get clockwork to stick? I still hold noob status!
Thanks!
Also rom manager seems fine, I flashed loads of roms with it with no issue, I also rebooted a few time at least between flashes so I dont get why clockwork suddenly decided to jump ship.
It was the font changer that f&%ked it all up for me, or anim mod (which I wont touch now even tho I miss the wicked transitions).

When using Font Changer, it's better to do a reboot manually instead of selecting Reboot from within the program. That sometimes cause me a boot loop too. But after turning the phone off / on a.k.a. "reboot manually", the phone boots fine.
To elaborate what rentaric said, use Root Explorer and go to /system/etc/, there should be a file named install-recovery.sh. This file is responsible for flashing the stock recovery every time the phone boots. If you rename it to something else e.g. install-recovery.sh.bak then CWM will stick on reboot.

Thanks, but when I get into the /system/etc/ there is not file called install-recovery.sh.
The only .sh in there is init.goldfish.sh
Any ideas???

bump...............

Flash cwm rec and either stock or custom rom.
Stock rom incl the .sh you want.
Sent from my Nexus S using XDA App

I've read on these forums that using Clockwork on the I9023 is a no-go. Serves up incompatible ROMs, etc.
BTW, I'm looking to root my I9023. Can the OP please point me to the method he used.

athani said:
I've read on these forums that using Clockwork on the I9023 is a no-go. Serves up incompatible ROMs, etc.
BTW, I'm looking to root my I9023. Can the OP please point me to the method he used.
Click to expand...
Click to collapse
LINK: http://forum.xda-developers.com/showthread.php?t=1007782
Please read the whole thread, if I had it would have saved me half a night scratching my head...lol

rentaric said:
Flash cwm rec and either stock or custom rom.
Stock rom incl the .sh you want.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yeah I have a custom rom installed, supercm7, but the install-recovery.sh. that I have been told is causing the problem of clockwork disappearing is not in the /system/etc/ folder, so I am asking if there is anything else that could be causing me to have to re flash clockwork via my pc every time I want to change rom?
I will tell you exactly what happens.
1. I go into rom manager
2. download a rom and choose flash rom from sd card
3. it asked if I want to wipe etc, i select yes
4. phone re boots and I get ! with an android
5. I pull the battery, hold volume up n power and boot / connect to my pc
6. re flash clockwork via SDK
7.the phone then load the new rom on its own
Before it would just flash the rom without me having to install clockwork again.

install-recovery.sh is only there if you're using a stock android rom.
"so I am asking if there is anything else that could be causing me to have to re flash clockwork via my pc every time I want to change rom?"
ROM Manager.
It's not a reliable working tool for ME as I'm changing ROMs/kernels on a regular basis and it might not work reliable the one time you need it.

Thanks for that, I may just sack rom manager then.
Its a shame as I flashed several roms with it without issue.
Oh well, loving this supercm7 so gonna stick with it untill an update comes out.
Many thanks to all who have replied, clicking the thanks buttons now!

I had the same problem but i installed a previus recovery and works fine formeforme
Sent from my Nexus S 4G using XDA Premium App

SOLVED - Can't Root Captivate

I flashed back to stock JF6 and am now trying to root the device so I can flash a new ROM. I have the update.zip on my SD card but when I choose reinstall packages in recovery (2e) mode it looks like it's installed the zip (however doesn't say replacing recovery with clockwork as it should) and just reboots normally (not to recovery).

Benjamindaines said:
I flashed back to stock JF6 and am now trying to root the device so I can flash a new ROM. I have the update.zip on my SD card but when I choose reinstall packages in recovery (2e) mode it looks like it's installed the zip (however doesn't say replacing recovery with clockwork as it should) and just reboots normally (not to recovery).
Been ******* with this thing for 3 hours... please help!
Click to expand...
Click to collapse
When you hit reinstall, it should install the zip then immediately take you into CWM. You shouldnt have to restart after installed the update.zip. Try selecting reinstall packages twice. That seems to work for most people.

capocaccia said:
When you hit reinstall, it should install the zip then immediately take you into CWM. You shouldnt have to restart after installed the update.zip. Try selecting reinstall packages twice. That seems to work for most people.
Click to expand...
Click to collapse
Nope doesn't work. When I click reinstall packages it says it's done, and restarts like it should. However, rather than starting back up in recovery mode, where you would click reinstall packages the second time it just boots normally. If I go back into recovery on my own it just does the same thing.

You might be better served to grab the speedmod kernel, which has CWM baked in, and flash it via ODIN. That would get around the issue you're seeing, and you'll be able to flash whatever you want.

jmtheiss said:
You might be better served to grab the speedmod kernel, which has CWM baked in, and flash it via ODIN. That would get around the issue you're seeing, and you'll be able to flash whatever you want.
Click to expand...
Click to collapse
Thank you very much!! Problem solved.

Edit. Woops

[Q] Install ClockworkMod persistently

Hi,
I downloaded and flashed my S2 with this firmware:
http://forum.xda-developers.com/showthread.php?t=1996714
Works very well. But I would like to have a better ClockworkMod Recovery. So I downloaded CWM Touch 5.8.1.5 (and also the "regular" CWM 4.0.1.5 as an alternative). I started the phone into recovery mode and used "apply zip". It says "replacing stock recovery", and the CWM Touch shows up with all functions working like a charm.
But next time I reboot the phone into recovery, the old recovery mode is present again. Same happens with the other CWM (4.0.1.5). It's like the installation is not done persistently on the partition but just temporarily into RAM ...
If I use the ROM Manager app to install one of the two CWMs, the app accepts the zip file, reboots the phone - but like before, the old recovery is still there. And it doesn't make a difference whether I select "wipe cache/data" and/or "wipe dalvik" prior to installation or not.
Is there a way of persistently installing this (or maybe a different) CWM?! Does it depend on the specific kernel that is in place with the firmware? Does said firmware and its kernel prevent installing a different CWM?
Regards,
Mac

Found a CWM6 here
http://forum.xda-developers.com/showthread.php?t=1877270
Works alright and can be installed permanently.
Mac

The cwm of kernel doesn't allow another cwm to be installed!
Unless you're on stock kernel,I think this won't be possible!
But there should be a way out!!
Sent from my MT11i using Tapatalk 2

Ghostfreak NB said:
The cwm of kernel doesn't allow another cwm to be installed!
Click to expand...
Click to collapse
Well, obviously it does. Said CWM 6 can be installed via Odin. I did not try CWM installation. This indeed may not work.
Mac

[Q] stuck in bootloop while installing elementalx.help!!!

i was installing elementalx on my nexus 5 via cwm. after going through the installer it asked if i wanted to fix root as i would lose it otherwise. i clicked yes. after that it started rebooting but got stuck on google. then went black. then again it showed google and is still looping. please help!!!

Try clearing cache by going to recovery.... Else my man you might need to flash stock again .....
To shutdown the phone press volume down and power till the time you get 3 vibrations

Dirty flash the ROM your on. What ROM did you flash EX on top of?

1) Download and flash the latest TWRP recovery.
2) Reflash your ROM. (Wipe cache and Dalvik)
3) Reflash ElementalX.
4) Never use CWM again. (It's completely outdated and is problematic with Lollipop).

BirchBarlow said:
4) Never use CWM again. (It's completely outdated and is problematic with Lollipop).
Click to expand...
Click to collapse
You know, it' funny. I keep hearing people say that but it still works fine for me. Maybe I'm just lucky. I've had way fewer issues with CWM than I've had with TWRP. There both good recoveries and TWRP is more current but to say CWM doesn't work is false.

theesotericone said:
You know, it' funny. I keep hearing people say that but it still works fine for me. Maybe I'm just lucky. I've had way fewer issues with CWM than I've had with TWRP. There both good recoveries and TWRP is more current but to say CWM doesn't work is false.
Click to expand...
Click to collapse
It was the other way round for me.... Twrp gave me issues .... I always use cwm touch .... Works good for me

i was on stock
BirchBarlow said:
1) Download and flash the latest TWRP recovery.
2) Reflash your ROM. (Wipe cache and Dalvik)
3) Reflash ElementalX.
4) Never use CWM again. (It's completely outdated and is problematic with Lollipop).
Click to expand...
Click to collapse
i am on stock so will i have to install the 5.0.1 factory image. also once in a while green screen comes asking whether to reboot or go into dload mode. also do i flash twrp before the factory image. can you tell me how this is done via pc as i was using flashify.

thanks guys
thanks guys it worked. i flashed stock and its working perfectly. thanks.

theesotericone said:
You know, it' funny. I keep hearing people say that but it still works fine for me. Maybe I'm just lucky. I've had way fewer issues with CWM than I've had with TWRP. There both good recoveries and TWRP is more current but to say CWM doesn't work is false.
Click to expand...
Click to collapse
I didn't say it doesn't work, I said it's problematic. I believe CWM is built on JB, so incompatibilities exist with KK and LP. For example, when you exit CWM whether you are rooted or not, it will tell you that you have a problem with root and offer to fix it. This is because CWM can't detect the SuperSU binary, it doesn't search the right place. Therefore novice users will say select okay causing CWM to install an outdated version of the SuperSU binary into the wrong location causing all sorts of problems with KK or LP. This is just one example of why it's better to just avoid CWM. TWRP is current and backward compatible. CWM is practically ancient.

1. CWM lacks functionality
2. CWM uses outdated legacy location of /data/media rather than /data/media/0 as sdcard/internal storage
3. CWM's option to "fix root" actually breaks root (and possibly other things)

BirchBarlow said:
I didn't say it doesn't work, I said it's problematic. I believe CWM is built on JB, so incompatibilities exist with KK and LP. For example, when you exit CWM whether you are rooted or not, it will tell you that you have a problem with root and offer to fix it. This is because CWM can't detect the SuperSU binary, it doesn't search the right place. Therefore novice users will say select okay causing CWM to install an outdated version of the SuperSU binary into the wrong location causing all sorts of problems with KK or LP. This is just one example of why it's better to just avoid CWM. TWRP is current and backward compatible. CWM is practically ancient.
Click to expand...
Click to collapse
Lethargy said:
1. CWM lacks functionality
2. CWM uses outdated legacy location of /data/media rather than /data/media/0 as sdcard/internal storage
3. CWM's option to "fix root" actually breaks root (and possibly other things)
Click to expand...
Click to collapse
I never really thought about it from a noob stand point so there is that. With me it works but I will stop publicly saying so after this post. You guys do bring up valid points and I'm just used to using it. TWRP back when had loads of issues so I steered very clear of it for a long time. Now it seems the tables are turned. I know eventually I'll have to make the switch but for now I'm still happy with playfulgods swipeable build of CWM. You both have my respect for trying to steer users down a more user friendly option.

theesotericone said:
I never really thought about it from a noob stand point so there is that. With me it works but I will stop publicly saying so after this post. You guys do bring up valid points and I'm just used to using it. TWRP back when had loads of issues so I steered very clear of it for a long time. Now it seems the tables are turned. I know eventually I'll have to make the switch but for now I'm still happy with playfulgods swipeable build of CWM. You both have my respect for trying to steer users down a more user friendly option.
Click to expand...
Click to collapse
Hey, what works for you, works (until it breaks, of course).
But for newer users, TWRP is now recommended as it's more friendly, as well as being up-to-date. CWM has had it's time.