Related
Koush just tweeted that the desire HD is now officially supported in ROM manager! Enjoy peeps
Sent from my Desire HD using XDA App
Can anyone point me to the thread that explains how to get clockworkmod rom manager to work with pauls version? I know I read this somewhere but can't find it now.
Sent from my Desire HD using XDA App
ses_comms said:
Can anyone point me to the thread that explains how to get clockworkmod rom manager to work with pauls version? I know I read this somewhere but can't find it now.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
If you want just install Rom Manager then install Clockwork recovery from within Rom Manager. Just like i did.
Desire HD - Rooted
LeeDrOiD 1.2
Rom Manager 2.5.07
Did an update in the rom manager, HTC Desire HD was the only option
BUT "An error occurred while attempting to run privilidged commands!"
Now worked, for some reason superuser had been disabled, and I know it was not me
Nice!!!!!!!!!!!!!!
\o/ thanks, installing worked like a charm, just how it should
Sent from my Desire HD using XDA App
Upgraded from Paul's recovery.
Everything works great.
Thanks Koush
YEP! GOOD MORNING!
Thanks for the heads up, it's all working fine. Just wondering if anyone knows how to fix the issue regarding the phone turning on and booting into Clockwork recovery when it's off and being charged.
Sylpher said:
Thanks for the heads up, it's all working fine. Just wondering if anyone knows how to fix the issue regarding the phone turning on and booting into Clockwork recovery when it's off and being charged.
Click to expand...
Click to collapse
Pisses me off too
If I want to launch the clockwork I only get after the first boot an phone with a red sign with it...
I'm I doing something wrong?
Sent from my Desire HD using XDA App
osicka said:
If I want to launch the clockwork I only get after the first boot an phone with a red sign with it...
I'm I doing something wrong?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Need more info than you've given.
Have you got root on the device?
Have you got S-OFF?
If you have both, then simply download Rom manager from the market and install the recovery.
osicka said:
If I want to launch the clockwork I only get after the first boot an phone with a red sign with it...
I'm I doing something wrong?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
try turning off system/fastboot
osicka said:
If I want to launch the clockwork I only get after the first boot an phone with a red sign with it...
I'm I doing something wrong?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Hi
Try to run "Fix permissions" in Rom Manager. I had the same problem and this helped me.
Do we need to manually S-OFF before we can flash roms with this?
I didnt realise so i have already flashed recovery...
Do i need to go back and sort out S-OFF?
JamesBarnes said:
Do we need to manually S-OFF before we can flash roms with this?
I didnt realise so i have already flashed recovery...
Do i need to go back and sort out S-OFF?
Click to expand...
Click to collapse
Yes, i think you definately need S-OFF
Im somewhat confused now, one of the guides mentions that S-Off is not mandatory...
Can someone post to confirm please?
Thanks
Thanks for the update!
Sent from my Desire HD using XDA App
S-OFF is not mandatory!
Ok I don't get it.
I had permroot on my dhd with visionary and downloaded Rom manager now and flashed clockwork recovery by selecting my device. Now if I select reboot in recovery I only get options, reboot, sdcard update.zip and wipe. Also it says e:can't open cache/recovery/command
It does not show options like backup, restore or install from zip. Even after doing the fix permissions in Rom manager
What am I doing wrong?
Hey guys..
I just today rooted my lovely Nexus S, 9023 or what its called (non branded or nothing)
But i cant load recovery.. went fine when i rooted it, but now that i want to load an custom rom it fails.. i followed this guide to root: http://forum.xda-developers.com/showthread.php?t=883032
Anyone have some ideas??
I just get a android logo and triangle + ! in it.. as error.. (
Best regrads
n0ta
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
n0ta said:
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
Click to expand...
Click to collapse
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
I have had this happen on my NS4G. I know they are a little different, but it seems like you are having the same thing happen that I did and to solve it, I open Windows command prompt(or terminal depending on you OS) and fastboot flash recovery (insert recovery.img name here) and reflashed the recovery partition with clockwork. Very easy fix. Just make sure you boot straight into recovery after flashing and flash the Rom you want to flash before booting back into stock(also make a nandroid before that). After that you shouldn't have any more problems unless you unroot. There must be a small glitch somewhere when flashing the clockwork doesn't fully erase stock recovery partition.
krohnjw said:
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Works now thanks all to both of you.
n0ta said:
Works now thanks all to both of you.
Click to expand...
Click to collapse
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
bender_123 said:
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
Click to expand...
Click to collapse
The Nexus one did the same thing. Most OTAs verify / replace this file. It's easy enough to deal with if you're unlocked and rooted.
Sent from my Nexus S 4G using XDA Premium App
This is about the third or fourth time this question has come up over the past week...
bender_123 said:
This is about the third or fourth time this question has come up over the past week...
Click to expand...
Click to collapse
I assure you it won't be the last.
Sent from my Nexus S 4G using XDA Premium App
When I try to flash CWM, I get a signature verification fail error. I replaced the recovery binary but it still won't work.
I am using this rom: http://forum.xda-developers.com/showthread.php?t=1139326
Does anyone know a fix for this?
The link is broken... Have tried to Odin one of Dr Honk's kernels?
Sent from my SGH-T959V using xda premium
The link is working again. It looks like that kernel needs adb to access recovery, which I haven't been able to get to work. Do you have any other ideas?
Eraser310 said:
The link is working again. It looks like that kernel needs adb to access recovery, which I haven't been able to get to work. Do you have any other ideas?
Click to expand...
Click to collapse
I'm not sure what you mean by this. Are you just trying to get it into recovery? If so, do you have the Android software developer kit (SDK) installed? The SDK includes the adb binary. Download it, install it, then open a command prompt, cd to the 'platform-tools' directory where the SDK installed, insure your phone is on & plugged in via USB, and issues the command: adb reboot recovery.
If I'm off-base with what you're trying to accomplish, my apologies.
Eraser310 said:
When I try to flash CWM, I get a signature verification fail error. I replaced the recovery binary but it still won't work.
I am using this rom: http://forum.xda-developers.com/showthread.php?t=1139326
Does anyone know a fix for this?
Click to expand...
Click to collapse
Don't use a KFx rom, the KF1 and KF2 versions of Gingerbread were really buggy and will give you more trouble than they're worth. You're better off flashing Octane, Valhalla or ICBINB which get updated frequently.
FBis251 said:
Don't use a KFx rom, the KF1 and KF2 versions of Gingerbread were really buggy and will give you more trouble than they're worth. You're better off flashing Octane, Valhalla or ICBINB which get updated frequently.
Click to expand...
Click to collapse
Which also means that you need to flash a KG4 leak or newer for the proper GB bootloaders. If not, you'll get a rainbow screen.
Similar Problem
Hey Guys,
I had a similar problem. I am using Fire Expert to overwrite the new recovery to the \system\bin folder. However, I realized my mistake was that I did not mount as r/w. After I did that though and I held the volume up, down and power, I stay stuck at the initial splash screen and can't go into the stock recovery screen. I can't boot regularly either; I have to Odin recover. Any help would be greatly appreciated.
Thanks!
apodictic said:
Hey Guys,
I had a similar problem. I am using Fire Expert to overwrite the new recovery to the \system\bin folder. However, I realized my mistake was that I did not mount as r/w. After I did that though and I held the volume up, down and power, I stay stuck at the initial splash screen and can't go into the stock recovery screen. I can't boot regularly either; I have to Odin recover. Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Overwriting the old recovery and putting the update.zip file on the sdcard for CWM Final was for Froyo ROMs only, not Gingerbread (GB) ones. What ROM are you currently on?
In order to get into recovery since flashing the GB boot loaders I have to:
Power off the phone
Hold down Volume Up, Volume Down, and the Power button
When the Galaxy S screen comes on, wait a second, it'll get a tad bit brighter. When that happens let go of only the Power button
Wait a few seconds and you should be in recovery
Sounds like you might be a bit goofed at this point, though. If you were on GB before I'd suggest using one of the ROMs in bhundven's The KJ6 Heimdall One-Click Collection. The last one in the list will also give you root, CWM, and voodoo lagfix.
Hey. Thanks for the quick reply.
I am currently on Froyo, Kernal version 2.6.32.9.
Sent from my SGH-T959V using XDA App
apodictic said:
Hey. Thanks for the quick reply.
I am currently on Froyo, Kernal version 2.6.32.9.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Weird. All you should have to do is put the updated recovery in /system/bin & put the update.zip on the root of the sdcard.
What is the current state of the phone? I know in the previous post you said you would have to use ODIN to recover. Did you do that?
Yes I did use Odin to recover. I did it following the link provided in the sgs4g 10 commandments. This is the second time I recovered. After I recovered he first time, I tried the process again and the same thing happened: stuck at the initial splash screen.
Sent from my SGH-T959V using XDA App
apodictic said:
Yes I did use Odin to recover. I did it following the link provided in the sgs4g 10 commandments. This is the second time I recovered. After I recovered he first time, I tried the process again and the same thing happened: stuck at the initial splash screen.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Which step in the 10 Commandments did you follow to recover in ODIN?
What's the current status of the phone?
This is the Odin tutorial I used.
forum.xda-developers.com/showthread.php?t=1001759
Also, I am not too sure what you mean by the current state/status of my phone.
Sent from my SGH-T959V using XDA App
apodictic said:
This is the Odin tutorial I used.
forum.xda-developers.com/showthread.php?t=1001759
Also, I am not too sure what you mean by the current state/status of my phone.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Just wondering if your phone is currently working or not. I wasn't sure given that you reflashed with ODIN.
Yes everything is fine right now. Lucky all of my settings and apps were still there after following that tutorial.
Perhaps file expert doesn't work?
Sent from my SGH-T959V using XDA App
apodictic said:
Yes everything is fine right now. Lucky all of my settings and apps were still there after following that tutorial.
Perhaps file expert doesn't work?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I've not used it but if it allows you to mount /system read/write, then it should work fine as long as you're putting the 'recovery' file in /system/bin & the update.zip on the root of the sdcard.
If you try it again then reboot into recovery, what happens?
FBis251 said:
Don't use a KFx rom, the KF1 and KF2 versions of Gingerbread were really buggy and will give you more trouble than they're worth. You're better off flashing Octane, Valhalla or ICBINB which get updated frequently.
Click to expand...
Click to collapse
can you help me ?
my xperia play literally cant flash at all i go to recovery mode and try to install a rom but it aborts it and says signature error ive tried around 5 roms what shall i do please some one help me
ive tried everything and im a noob i dont know how to flash properly so please be very descriptive pleaseeee
UKemal said:
can you help me ?
my xperia play literally cant flash at all i go to recovery mode and try to install a rom but it aborts it and says signature error ive tried around 5 roms what shall i do please some one help me
ive tried everything and im a noob i dont know how to flash properly so please be very descriptive pleaseeee
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?p=21272961
Okay, is anyone else having a hard time using Rom Manager using it's features due to the fact that the MT4GS is NOT listed as one of the models. I mean, how am I supposed to enter manual flash override if I can't even select MY phone model. What are WE supposed to do???
Sent from my myTouch_4G_Slide using xda premium
we don't have an official recovery yet, so we have to use Modaco 4.0.0.9 for the time being..
WHATEVER YOU DO, DO NOT FLASH THE RECOVERY FOR ANOTHER PHONE..
That's a lil late however, I think I already did that, now I can't even enter recovery mode anymore, and when I power on while holding the volume button down. I get same message about trying to load and then it says no image. Even then if I try to press recovery I get stuck on the white t-mobile/HTC screen. Mt only option if to reboot. I'm st my wits end. Should I just Unroot and then just Root back again?
Sent from my myTouch_4G_Slide using xda premium
YES flash the PD15IMG file and start over from scratch with revolutionary and then upgrade to modaco's 4.0.0.9 recovery. There is no support for the MT4GS in ROM Manager and it's not safe at all to flash anything that's designed for another phone unless you want problems! Good luck!
dmarco said:
That's a lil late however, I think I already did that, now I can't even enter recovery mode anymore, and when I power on while holding the volume button down. I get same message about trying to load and then it says no image. Even then if I try to press recovery I get stuck on the white t-mobile/HTC screen. Mt only option if to reboot. I'm st my wits end. Should I just Unroot and then just Root back again?
Sent from my myTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
There's probably an easier way. Download the modaco recovery zip, unzip it and grab the img file and rename it to recovery.img. Then reboot into the bootloader and use fastboot to flash the img. That should do the trick.
unclespoon said:
YES flash the PD15IMG file and start over from scratch with revolutionary and then upgrade to modaco's 4.0.0.9 recovery. There is no support for the MT4GS in ROM Manager and it's not safe at all to flash anything that's designed for another phone unless you want problems! Good luck!
Click to expand...
Click to collapse
Just want to say thank you and I'm going to donate some coffee cash to you later. I followed your method of copying/transferring recovery image through terminal emulator on my phone and now it works PERFECTLY again. I think I accidentally flashed a different version of recovery for a different phone model through Rom Manager. So I learned my lesson. I also spoke with Koush yesterday and he assured me that a fix is on the way for the MT4GS, which is great to hear, otherwise, it's pretty much useless to us.
Sent from my myTouch_4G_Slide using xda premium
Where on my SD card am I supposed to stick the "recovery.img" file so that FASTBOOT will see it? I am having no luck finding/loading the IMG file....
I got it figured out. NEVERMIND =)
1) Download MoDaCo's recovery to your computer.
2) Download the Fastboot binary for your computer.
3) I'm assuming you have ADB set up on your computer, so type in "adb shell reboot bootloader".
4) When your phone is in the bootloader, type in "fastboot flash recovery */path/to/recovery.img*" and then "fastboot reboot".
5) You should be able to boot into recovery now.
Thank You Sir. I had already figured it out. I felt so stupid when I did too... It happens though... I guess I should have read more.
Yea I did this by accident once, flashed the MT4G recovery through Rom Manager. I suggest just go ahead and dont install that app at all, you cant really do anything with it anyway since most of the options are unavailable unless you flash CWM recovery through the app. Also, if you are using Unity Rom, CWM reads your device as a HTC Sensation, so dont be fooled. Once you flash the 4009 originally you should be good, if you accidentally flash another phones recovery, none of your nandroids will work
Jaytex24 said:
Yea I did this by accident once, flashed the MT4G recovery through Rom Manager. I suggest just go ahead and dont install that app at all, you cant really do anything with it anyway since most of the options are unavailable unless you flash CWM recovery through the app. Also, if you are using Unity Rom, CWM reads your device as a HTC Sensation, so dont be fooled. Once you flash the 4009 originally you should be good, if you accidentally flash another phones recovery, none of your nandroids will work
Click to expand...
Click to collapse
Yup, I learned that the hard way. Drove me nuts for 2 days til I finally figured out where I went wrong.lol Rom Manager is useless to us MT4GS owners for now
Sent from my myTouch_4G_Slide using xda premium
Sent from my myTouch_4G_Slide using xda premium
dmarco said:
Sent from my myTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
Thats actually a horrible score. Your overclocked to 1.8ghz and only at 5000? My RubiX is at 4900 with no overclock. One of my testers got 6100 using unity 1a kernel clocked to 1.6ghz.
Sent from my RubiX CubeD MT4GS using xda premium
The first time I flashed a from I used NVFlash but after that I used rom manager to boot into recovery when I was on gb now I'm running ics and I just hold down the power button click reboot>recovery and flash rooms from there and it works is this normal? Cuz I heard ur suppose to ALWAYS use nvflash
Sent from my LG-P999 using xda app-developers app
Laxshanth said:
The first time I flashed a from I used NVFlash but after that I used rom manager to boot into recovery when I was on gb now I'm running ics and I just hold down the power button click reboot>recovery and flash rooms from there and it works is this normal? Cuz I heard ur suppose to ALWAYS use nvflash
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
So which is it? If you're always doing Power button > Reboot > Recovery you are booting into the NvFlash'd CWM recovery not ROM Manager
xBkKx said:
So which is it? If you're always doing Power button > Reboot > Recovery you are booting into the NvFlash'd CWM recovery not ROM Manager
Click to expand...
Click to collapse
Ohh ok thanks makes sense but what about when I use to be on gb I use to use rom manager
Sent from my LG-P999 using xda app-developers app
You can also use ROM manager to boot to recovery, the reason people advise against using the app altogether is because the fake flashing that ROM manager does.
ROM manager will boot into nvflash recovery successfully as long as you never flashed the fake recovery via ROM manager.
So again, if you never flashed via ROM manager, then holding power>reboot recovery = going to ROM manager and booting to recovery.
buru898 said:
You can also use ROM manager to boot to recovery, the reason people advise against using the app altogether is because the fake flashing that ROM manager does.
ROM manager will boot into nvflash recovery successfully as long as you never flashed the fake recovery via ROM manager.
So again, if you never flashed via ROM manager, then holding power>reboot recovery = going to ROM manager and booting to recovery.
Click to expand...
Click to collapse
Okayy that's why it works lol thanks alot!
Sent from my LG-P999 using xda app-developers app
Not that it matters, but I have always flashed both recoveries. It's not that Rom Manager "fake" flashes it, it isn't flashed on a persistent partition that can be reached via button combo. I use Rom Manager and it's "fake" recovery mostly for nandroids. In reality, there's literally 2 separate recoveries, albeit, one is worthless in any "no boot" situation. Other than that, it's fine to flash roms and what not, just always have both, never just R M.
[email protected]
mustangtim49 said:
Not that it matters, but I have always flashed both recoveries. It's not that Rom Manager "fake" flashes it, it isn't flashed on a persistent partition that can be reached via button combo. I use Rom Manager and it's "fake" recovery mostly for nandroids. In reality, there's literally 2 separate recoveries, albeit, one is worthless in any "no boot" situation. Other than that, it's fine to flash roms and what not, just always have both, never just R M.
[email protected]
Click to expand...
Click to collapse
Before I'm pretty sure I downloaded a rom and it didn't have rom manager so I downloaded it from the play store and went into recovery through that and flashed a rom? Or is that normal?
Sent from my LG-P999 using xda app-developers app
That's fine, what we're all trying to explain is that if you mess up and your phone won't boot normally, you won't be able to recover it with the Rom Manager recovery since it is only accessible through a working a ROM. This is why we Nvflash it on a persistent partition that can be accessed regardless if you have a working rom or not. There's no difference between the two recoveries, only where they are flashed.
[email protected]
buru898 said:
You can also use ROM manager to boot to recovery, the reason people advise against using the app altogether is because the fake flashing that ROM manager does.
ROM manager will boot into nvflash recovery successfully as long as you never flashed the fake recovery via ROM manager.
So again, if you never flashed via ROM manager, then holding power>reboot recovery = going to ROM manager and booting to recovery.
Click to expand...
Click to collapse
I agree. ROM Manager which should be named ROM Mangler has seriously messed up phones causing its victims many hours of panic and grief. Stay away from it.
Kinda off topic but if rom manager is so bad why is it included with custom roms? One of the first things i do is uninstall it with titanium backup
Sent from my LG-P999 using xda app-developers app
bamathafan said:
Kinda off topic but if rom manager is so bad why is it included with custom roms? One of the first things i do is uninstall it with titanium backup
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Because it can be used to boot into Recovery, and it is useful for the purpose of organizing backups
Sent from my LG-P999 using xda premium