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
Related
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
I just flashed the my old stock rom to cm7 custom rom and want to back up the current rom. But when I hit the flash the CWM in rom manager, it just keeps loading without popping up the phone mode choosing interface. any help would be greatly appreciated.
chui1989 said:
I just flashed the my old stock rom to cm7 custom rom and want to back up the current rom. But when I hit the flash the CWM in rom manager, it just keeps loading without popping up the phone mode choosing interface. any help would be greatly appreciated.
Click to expand...
Click to collapse
Are you trying to flash a ROM or backup your ROM, the way you have that worded confuses me. Are you using the ROM manager app, because I've never gotten it to work to any degree. If you're trying to flash the CWM kernel you need to do that via Odin.
i am trying to back up the current rom, but in order to do that I have to flash the CWM recovery right? but anyway, I have figured it out. Thank you
Ok glad you got it! Yea you have to use Odin to flash kernels, such as CWM. I believe there is a way to flash kernels off the SD card while booted into recovery mode, but I'm not familiar with it. Just flash that kernel with Odin, boot into recovery (Power button + Volume Up) and you can backup, restore, flash ROMs, etc. Enjoy buddy!
i have install clockworkmode-ginger-gamma on my sam.mini.. then when reboot it wont start.. now my hp canot on... plss... ASAP
hi, i have a nexus s 4g and it has ClockWorkMod 5.0.2.0. when ever i try to boot into recovery by holding the volume up and power buttons at the same time, i get the stock android recovery, then i scroll down to recovery and then a picture of the android comes up, then after that a big yellow triangle with an exclamation point comes up and ClockWorkMod doesnt come up. but sometimes it works. i just want to be absolutely sure that i can boot to recovery so i can recover a nandroid backup when i am flashing roms just in case something goes wrong. please help
fastboot flash recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-crespo4g.img
are you using stock rom? stock rom erases your custom recovery every time you reboot your device.
if you are running stock rom flash this after you flash recovery and your custom recovery will stick
sean1984 said:
fastboot flash recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-crespo4g.img
are you using stock rom? stock rom erases your custom recovery every time you reboot your device.
if you are running stock rom flash this after you flash recovery and your custom recovery will stick
Click to expand...
Click to collapse
now it makes sense! thank you!
steineronie said:
now it makes sense! thank you!
Click to expand...
Click to collapse
anytime
sean1984 said:
fastboot flash recovery
are you using stock rom? stock rom erases your custom recovery every time you reboot your device.
if you are running stock rom flash this after you flash recovery and your custom recovery will stick
Click to expand...
Click to collapse
I am having the same problem as the OP, but this post doesn't make any sense to me. It seemed to have worked for him though, so could I ask you to elaborate?
I never had clockworkmod work for me, and I get to the same screen when I use the vol up button and the power button. I am not sure what to do with that file you posted though.
suncross said:
I am having the same problem as the OP, but this post doesn't make any sense to me. It seemed to have worked for him though, so could I ask you to elaborate?
I never had clockworkmod work for me, and I get to the same screen when I use the vol up button and the power button. I am not sure what to do with that file you posted though.
Click to expand...
Click to collapse
I had this exact same problem on 2.3 .. I'd have to flash CWM everytime I wanted something flashed. If it doesn't do it the first time and it shows u the stock recovery, reboot and open CWM and flash again. Then flash the Fix and ull be fine . For me it fixed itself once I got to 4.0.x
- Google
Reason: on a stock ROM the /system/etc/install-recovery.sh script will replace any custom recovery on each boot. Feel free to rename or delete this file, the next recovery you flash will stick until you flash another Stock ROM.
Harbb said:
Reason: on a stock ROM the /system/etc/install-recovery.sh script will replace any custom recovery on each boot. Feel free to rename or delete this file, the next recovery you flash will stick until you flash another Stock ROM.
Click to expand...
Click to collapse
I know this is a little bit of a older post but it seems relevant. I have a epoc 4g touch running AOKP Milestone 5 and I am unable to make CWM Stick keeps reverting to the stock android recovery. Any Ideas?
bsxed said:
I know this is a little bit of a older post but it seems relevant. I have a epoc 4g touch running AOKP Milestone 5 and I am unable to make CWM Stick keeps reverting to the stock android recovery. Any Ideas?
Click to expand...
Click to collapse
Well i don't have an Epic 4G Touch so i can't say for sure, but it's probably exactly what i said before. Rename or delete the file: /system/etc/install-recovery.sh
No harm will be done, all the script does is replace the stock recovery on boot if it finds that a non-stock one is present. You can do this with ES File explorer, FX or whatever file manager you please (or terminal if you know how).
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
j0hnnyn said:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
Click to expand...
Click to collapse
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
psycopanther said:
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
volume up/home/power button is recovery try that
and you used rom manger to flash rom?
j0hnnyn said:
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
PJnc284 said:
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
Click to expand...
Click to collapse
Yep, kexec rom (kernel) using a recovery that doesn't support it.
not sure if this can help but read this post I made, it may help:
http://forum.xda-developers.com/showthread.php?t=1842716
Make sure you have the right CWR version which is 6.0.1 or 6.0.2. Don't mess around with flashing things in rom manager.
To get to your recovery you need to use vol up+home+power.
The vol down puts the phone into Download/ODIN mode. It's like the bootloader/hboot screen of HTC phones.
I always super wipe)cache,data,dalvil,system) before any install, nandroid or fresh rom. And then install downloaded apps with tit backup.
To use Bean's nandroids after bootloader unlock, flash a fresh copy of bean first to install kexec, then flash your nandroid.
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1768209]
From what I have read in his original post for his new build, it does require an unlock and is running a custom non-kexec kernel, so it I would draw the same conclusion that you are and it should in theory work with the 6.0.1.2 version of CWM.
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
You should be able to use cwm6.0.1.2 to flash Imoseyons leankernel on any version of a custom touchwiz rom and enjoy no kexec
Im running beans 8 with imo's 2.2 kernel w/ no kexec...dont really like beans 9.
So I've been attempting to get a custom rom on this device for a friend of mine, and no matter what rom I install the phone keeps rebooting to either red CWM recovery or CWM 6.*.* not precisely sure what version it is when its blue.
I have no idea why it won't take a ROM? ANy ideas? Sometimes it will look like it installs a rom, but just continuously reboots to CWM.
shorteh said:
So I've been attempting to get a custom rom on this device for a friend of mine, and no matter what rom I install the phone keeps rebooting to either red CWM recovery or CWM 6.*.* not precisely sure what version it is when its blue.
I have no idea why it won't take a ROM? ANy ideas? Sometimes it will look like it installs a rom, but just continuously reboots to CWM.
Click to expand...
Click to collapse
sometimes it does that...
flash it back to stock and start over or try to flash this kernel and then flash cm9 twice
http://forum.xda-developers.com/showpost.php?p=25526654&postcount=3