Someone asked if it was possible to flash ClockworkMod Recovery through hboot instead of using RomManager. The answer...yes.
Primary reason something of this nature may be useful, as I see it, is if your recovery is damaged, your ROM is bootlooping, and you don't want to use or have access to ADB.
In that case you would:
remove your sdcard from your phone
place the zip on the root of the sdcard (using an adapter or another phone) and make sure it is named the appropriate "PG05IMG.zip"
place the sdcard back in your phone
boot to bootloader as if you're installing a radio (power+VolDown from powerOff). It will then find the zip, recognize it as recovery and ask if you want to install (if it does not prompt then select "Bootloader" from hboot).
Follow the instructions and after it finishes flashing pull your battery to power off (since the ROM will be bootlooping and hboot will constantly find the zip)
Now remove the sdcard and delete the zip (via adapter or other phone) like you did to put it on the sdcard, then place the card back in the phone.
Boot back to bootloader (Pwr+VolDwn)
Select "Recovery" and use CWR to wipe data/cache, flash a new rom, restore, or whatever you wish.
Obviously not the only reason since some people prefer this method over RM but clearly in that case the whole sdcard switching mess is unnecessary. Just do steps 2 and 4 and reboot when prompted like you do with radios.
Remember to remove any PGO5IMG.zip from your sdcard when done.
If this isn't useful to you, so be it. I just figured I'd throw this out there. Maybe it will help someone.
I will keep this updated as new versions come out for those few that find it useful.
**Credit to Koush and jcase**
All I did was decide to throw them in a zip that was useful in some situations for panicking users.
Updates
8/9/2011: Added latest official stable for mecha (4.0.1.5) released 8/8/2011.
8/30/2011: Added latest official stable for mecha (5.0.0.1) released less than an hour ago. Added mirror.
8/31/2011: Added latest official stable for mecha (5.0.0.8)
9/1/2011: Added latest official stable for mecha (5.0.1.0)
9/5/2011: Added latest official stable for mecha (5.0.2.1)
2/1/2012: Added touch based CWR released this morning (5.8.0.2) *NOTE: Have not personally tested.
If any of these cause problems please let me know immediately.
Latest Official=5.0.2.1
jcase modded=4.0.0.5
Mirror: http://www.mediafire.com/?9zt68cegl6qa3
MD5:
66750618ecfba292c0b0e42c50c2c3ee - (CWR3.1.0.2)PG05IMG.zip
1f390edad7e87310fe80b3264a57b14b - (CWR4.0.0.5)PG05IMG.zip
6aac529cedcd2b22afac7391a4cb7efb - (CWR4.0.1.5)PG05IMG.zip
bf25b2601441b9fffb7d68954c4ff3b5 - (CWR5.0.0.1)PG05IMG.zip
dfe1ddf0c574977ee2c1828735ef2dc0 - (CWR5.0.0.8)PG05IMG.zip
8474c8d607177b0144eec624dea687b7 - (CWR5.0.1.0)PG05IMG.zip
c4c1d9c5e553fd7b151352551b931369 - (CWR5.0.2.1)PG05IMG.zip
58557e1e355c795d748c2e6c66251f0a - (CWR5.8.0.2)PG05IMG.zip
Absolute_Zero said:
Someone asked if it was possible to flash ClockworkMod Recovery through hboot instead of using RomManager. I didn't see the need at the time but I took a few minutes to throw together a test. Let me know if it works for you or not.
I tested flashing the stock recovery from the custom firmware, confirmed it had replaced CWR, then used this to install CWR back.
Primary reason something of this nature may be useful, as I see it, is if your recovery is damaged, your ROM is bootlooping, and you don't want or have access to ADB. In that case you would just pull your sdcard, place this on the root (via adapter or someone else's phone) named the appropriate "PG05IMG.zip", place back in your phone, and boot to bootloader as if you're installing a radio. It should then find it, recognize it as recovery and ask if you want to install.
Additionally, seems if it is as easy as swapping the .img out which is all I did, then the original custom upgrade firmware flashed in the last step of the root guide could include this. Then you'd have CWR immediately after finishing the permaroot guide.
If this doesn't work and doesn't have any use for anyone, so be it. I just figured I'd throw this out there.
BTW, this is ClockworkMod Recovery 3.1.0.2 (latest for mecha at time of posting).
Note1: Only tested on Engr hboot with S-off obviously
Note2: I don't have access to an MD5 generator where I am so people that test this should have a booting ROM with RomManager or at least know how to manually reflash ClockworkMod Recovery if it doesn't work.
Click to expand...
Click to collapse
Good work.on this... A LOT of people are going enjoy it!! It is also a great way to install the modded 4.0.0.5 Clockwork with the boot to bootloader option.
I always had to "flash recovery" in adb.
Props!!
Sent from my ADR6400L using XDA App
good post will definitely come in hand props
DroidTh3ory said:
Good work.on this... A LOT of people are going enjoy it!! It is also a great way to install the modded 4.0.0.5 Clockwork with the boot to bootloader option.
I always had to "flash recovery" in adb.
Props!!
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
There's a modded 4.0.0.5 CWM Recovery out there?? Where can I find the post for this ?
Sword.Zero said:
There's a modded 4.0.0.5 CWM Recovery out there?? Where can I find the post for this ?
Click to expand...
Click to collapse
Post a link to it and I'll make one when I get home. That way I can test again. Hopefully the modded one you speak of is fully stable and functional.
Absolute_Zero said:
Post a link to it and I'll make one when I get home. That way I can test again. Hopefully the modded one you speak of is fully stable and functional.
Click to expand...
Click to collapse
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment (CWR4.0.0.5)PG05IMG.zip
DroidTh3ory said:
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment 661641
Click to expand...
Click to collapse
In your case it would probably be easier to just use flash_image from terminal on the phone (i.e. flash_image recovery /sdcard/recovery.img) assuming your current rom has it (if not just search and download it) or you have RM installed. The main case I saw this being useful was if you didn't have or want to use ADB and your ROM was unusable (e.g. bootlooping). I may add Jcase's modded recovery to the OP as well since it seems useful/wanted by some.
I thought the one JCase made had issues with nandroid backups installing? I could be wrong but for some reason I remember that issue for several people.
Mustang302LX said:
I thought the one JCase made had issues with nandroid backups installing? I could be wrong but for some reason I remember that issue for several people.
Click to expand...
Click to collapse
I have been using for a good month now on 3 different bolts... Never had a issue??
Absolute_Zero said:
Additionally, seems if it is as easy as swapping the .img out which is all I did, then the original custom upgrade firmware flashed in the last step of the root guide could include this. Then you'd have CWR immediately after finishing the permaroot guide.
Click to expand...
Click to collapse
actually,thats allready how it is ive rooted mr2 twice and the mr1 upgrade allready has clockwork installed.
it is that easy,i have done this,and i have also removed the hboot and stock recovery from PG05IMG RUUs so that i could flash without destroying recovery and my eng bootloader.
thanks for putting it together and offering the download, it has many uses, as people will see. the biggest one allready having been mentioned,if something screws up your OS and recovery,its easy to get it back.
did you make up your own android info file? or what did you take it from?
again thanks for posting this,it was commonplace to install inc recoverys in hboot,and ive done it on the eris as well
DroidTh3ory said:
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment 661641
Click to expand...
Click to collapse
thanks for the download. has he put up any posts on it? or is it still being developed?
scotty1223 said:
thanks for the download. has he put up any posts on it? or is it still being developed?
Click to expand...
Click to collapse
I believe he has it posted on rootzwiki
Sent from my ADR6400L using XDA App
cool,thanx... ill go over there and look for it.
edot:
here if anyone else wants it
Thanks for this. Just flashed 4.0.0.5 after being afraid/too lazy to do it through ADB (which is also a pain because I have it on my Windows partition whereas I regularly use Mac).
scotty1223 said:
actually,thats allready how it is ive rooted mr2 twice and the mr1 upgrade allready has clockwork installed.
Click to expand...
Click to collapse
Figures. It was too simple of a concept not to have been done but I didn't see anyone that had done it in Tbolt. I also hadn't seen anyone mention it was in the custom firmware either and I didn't have time to check this morning before I left for work. I guess I can pull that part out of the OP since you say it's already in there.
thanks for putting it together and offering the download, it has many uses, as people will see. the biggest one allready having been mentioned,if something screws up your OS and recovery,its easy to get it back.
Click to expand...
Click to collapse
Exactly my reasoning. I've seen to many people unaware of what to do in that situation
did you make up your own android info file? or what did you take it from?
Click to expand...
Click to collapse
I checked a few from the firmware and radios and they all looked the same so I just pulled one of those.
again thanks for posting this,it was commonplace to install inc recoverys in hboot,and ive done it on the eris as well
Click to expand...
Click to collapse
First HTC android phone I've owned but as I said, makes sense it would have been done a long time ago for other HTC phones.
DroidTh3ory said:
I believe he has it posted on rootzwiki
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Hey get out of here, you've got candy to make! I keeeed I keeeed! Great work on the recovery guys, VERY useful!
Sent from my ADR6400L using XDA Premium App
DroidTh3ory said:
I have been using for a good month now on 3 different bolts... Never had a issue??
Click to expand...
Click to collapse
Yup. Been using it since it's release. Restored many backups with absolutely no issues.
Absolute_Zero said:
Figures. It was too simple of a concept not to have been done but I didn't see anyone that had done it in Tbolt. I also hadn't seen anyone mention it was in the custom firmware either and I didn't have time to check this morning before I left for work. I guess I can pull that part out of the OP since you say it's already in there.
Click to expand...
Click to collapse
id be willing to bet most people dont know,lol.they prolly just blindly downloAd rom manager and flash it. i checked to see if it was there,after seeing this as one of the last statements in the root post: Reboot your phone. You should now have full root permissions, an engineering kernel and recovery.
Absolute_Zero said:
First HTC android phone I've owned but as I said, makes sense it would have been done a long time ago for other HTC phones.
Click to expand...
Click to collapse
its one of the things i really love about htc. i got used to installing recoverys,splash screens,etc. on my incredible,then started experimenting with img files on my eris,and discovered it was quite possible to simply move the images around kinda neat if you want to try a leaked ruu but dont want to wait for someone to post a CWM flashable roms. just pull out the hboot and stock recovery and flash away
it was quite common to manipulate things in hboot on the inc,but never mentioned in the eris forum,where most of the gurus frowned upon the s-off bootloader.kind of a shame... more bricked eris's prolly could have been revived after the clockwork fiasco if s-off was part of the common root process.
thanx for the android info info. when i make them up,it doesnt seem to matter which one i use. i dont think it even checks the text inside,i think you just need a text document titled "android info" lol
Thank you for the updated 5.0.0.1 cement recovery.
cam30era said:
Thank you for the updated 5.0.0.1 cement recovery.
Click to expand...
Click to collapse
Autocorrect fail? or did you have a problem with 5.0.0.1?
Related
Read This
http://forum.xda-developers.com/showpost.php?p=9542514&postcount=662
Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.
Still not that simple for me, since even a "Gtablet Vet" like myself tried the OP method and failed. My second out of box new Gtablet went in perma-loop when simply installing straight to 2.0, via recovery folder & update.zip. Ended up having to get CW on the device by putting on the sd card, remapping command and stopping the loop with power + volume to get CW installed. I then had to install TnT 1.02 and then finally got 2.0 installed after that (cache and data wipe of course).
Cleanest way seems install 1.02 via recovery folder / update.zip method and then install 2.0 the same way. Thats is unless I just had bad luck with second Gtablet. VERY possible.
added:
Frankly, we seem at the stage now where CW seems a survival requirement- IF you want to keep trying new roms & updates.
roebeet said:
Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.
Click to expand...
Click to collapse
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
Installing TnT 1.0 roms appears to zap CW pretty good.
roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
I have found that you can put the stock recovery img (let's call it recovery-stock.img) on the sdcard and get an adb shell while booted into cw recovery. Then it's just a
Code:
flash_image recovery recovery-stock.img
That should get you back to stock recovery.
Sent from my Incredible using XDA App
LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
I had to go back to stock at first because I kept getting status 7 errors with CW. Roebeet's suggestion to partition sdcard with CWR seems to have solved that.
Sent from my Incredible using XDA App
Flashed 2.0.0
I liked TnT 2.0.0 and it really helped performance but the gtab is still full of issues....
Out of the box my Gtab's proprietary email and photo app forced closed before ever loading. the viewsonic update didn't fix it and so I flashed it with TnT 2.0.0.
I got a System UID's warning while I did it and I guess that was the cause of those apps not working. I then did a system reset to factory default or whatever its called and lost everything but after flashing TnT 2.0.0 again it worked a lot better and the email app worked great, photo app still doesn't work. My new problems are that the sound and and flash don't work anymore. I reinstalled flash and the browser just crashes whenever flash is involved with a site. Sound will sometimes work when I first boot up but it quits after a while, especially after waking from sleep. A lot of the time I get crackles and pops when I first boot up or wake it from sleep.
I am returning this Gtab and I am going to buy another one from somewhere else in hopes that I don't get these issues out of the box.....I haven't read anywhere that anyone has experienced these specific problems other than the sound; as this is a TnT error; so I warn all, DON'T BUY FROM STAPLES!!!
Can any give me a link to the newest cw recovery?
Sent from my HTC Vision using Tapatalk
fliint said:
Can any give me a link to the newest cw recovery?
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
http://mrcellphoneunlocker.com/recovery.img
Download it from the RomManager.
Thanks
Sent from my HTC Vision using Tapatalk
its not on the rom manager, (yet)
gnunixguy said:
Download it from the RomManager.
Click to expand...
Click to collapse
Rom manager doesn't list 3.0, only 2.5.1.4 as being the latest
ROMmanager is 3.0.0.2 the recovery has not changed since november 10.
There's nothing wrong with cwm. Maybe one will come with GB.
vision
Does this recovery fix the "off issue" what's new in it?
PlatinumMOTO said:
Does this recovery fix the "off issue" what's new in it?
Click to expand...
Click to collapse
Support for ext4 file systems, that GB uses. If you're using any Android 2.2 based ROM, stay with CWM 2.5.1.3.
Sent from my HTC Desire Z using XDA App
AllWin said:
Support for ext4 file systems, that GB uses. If you're using any Android 2.2 based ROM, stay with CWM 2.5.1.4.
Sent from my HTC Desire Z using XDA App
Click to expand...
Click to collapse
For latest mine says 2.5.1.3
omarsalmin said:
For latest mine says 2.5.1.3
Click to expand...
Click to collapse
Sorry, that was a typo. Fixed.
i see what you mean... and i just installed 3.0.0 and its my color - orange
-- this is just for the gingerbread build by RHCP I am crazy because I am flashing gingerbread to my phone right now. i think ive gone insane.
androidcues said:
i see what you mean... and i just installed 3.0.0 and its my color - orange
-- this is just for the gingerbread build by RHCP I am crazy because I am flashing gingerbread to my phone right now. i think ive gone insane.
Click to expand...
Click to collapse
let us know the results? did your g2 survive?
can anyone let us know if any problems have been discovered with this so far?
warsng said:
let us know the results? did your g2 survive?
Click to expand...
Click to collapse
Yes it did --- I kinda jumped into it and did not really heed Cyanogen's big fat warnings... (reckless flashing) and I couldnt get gapps to flash -- the stuff from rhcp's CM7 thread -- but I got gingerbread going -- then I got distracted all night...woke up this morning trying to make the phone shape up for work -- that was a #fail and the battery seems horrible (then again by no means was it a proper battery test) -- so I decided to restore and that involved new drivers..(for some reason my SDK at work couldnt find the phone so I had to reinstall a fresh SDK (which i named gbSDK)... then found the current recovery at mybrainhurts.com and erased 3.0.0 and fastbooted the froyo recovery back in and restored. easy pie --
gingerbread is a whole 'nother game -- i just hope theres a way to go back and forth between froyo and GB (and eclair/cupcake/donut) without having to fastboot erase and fastboot flash relevant recoveries.
I am sure folks want to know if the new one fixes the "off" mode...and the answer is - i dont know. I didnt check. i kind of hope not because its a feature rather than a bug. theres no quick way to get to recovery when the phone is off. (on to fboot then to hboot then to recovery is too much work)
Is it even worth it to upgrade at this point in time? I'm a bit worried as it seems to be working pretty damn good with what I'm doing now. No partitions on my SD card because I don't care to put apps on it (it's not the fastest class card anyway).
androidcues said:
Yes it did --- I kinda jumped into it and did not really heed Cyanogen's big fat warnings... (reckless flashing) and I couldnt get gapps to flash -- the stuff from rhcp's CM7 thread -- but I got gingerbread going -- then I got distracted all night...woke up this morning trying to make the phone shape up for work -- that was a #fail and the battery seems horrible (then again by no means was it a proper battery test) -- so I decided to restore and that involved new drivers..(for some reason my SDK at work couldnt find the phone so I had to reinstall a fresh SDK (which i named gbSDK)... then found the current recovery at mybrainhurts.com and erased 3.0.0 and fastbooted the froyo recovery back in and restored. easy pie --
gingerbread is a whole 'nother game -- i just hope theres a way to go back and forth between froyo and GB (and eclair/cupcake/donut) without having to fastboot erase and fastboot flash relevant recoveries.
I am sure folks want to know if the new one fixes the "off" mode...and the answer is - i dont know. I didnt check. i kind of hope not because its a feature rather than a bug. theres no quick way to get to recovery when the phone is off. (on to fboot then to hboot then to recovery is too much work)
Click to expand...
Click to collapse
what exactly happened when you flashed the gapps?
at least it didn't fry your g2. i think i might give it a go once i hear a few more success stories. my main worry atm is the ext4 issue. i guess i could just wait until rc1 i guess.
by 'off mode', are you referring to s-off?
warsng said:
what exactly happened when you flashed the gapps?
at least it didn't fry your g2. i think i might give it a go once i hear a few more success stories. my main worry atm is the ext4 issue. i guess i could just wait until rc1 i guess.
by 'off mode', are you referring to s-off?
Click to expand...
Click to collapse
I read the rhcp cm7 thread and i needed to unmount system before flashing the gapps. Thats why gapps failed because i didnt read!
By Off i meant how cw doesnt let the phone turn off when charging... i hope cw 3.0 lets us keep that feature.
Ill probably give it another go this weekend...it works its just if you wanna go back to froyo you need to replace recoveries manually..not a big deal but frankly gingerbread isnt all that more exciting than froyo. I feel i have what i need.in Froyo..the gb keyboard...the gb market... and thats fine with me.
vision
androidcues said:
I read the rhcp cm7 thread and i needed to unmount system before flashing the gapps. Thats why gapps failed because i didnt read!
By Off i meant how cw doesnt let the phone turn off when charging... i hope cw 3.0 lets us keep that feature.
Ill probably give it another go this weekend...it works its just if you wanna go back to froyo you need to replace recoveries manually..not a big deal but frankly gingerbread isnt all that more exciting than froyo. I feel i have what i need.in Froyo..the gb keyboard...the gb market... and thats fine with me.
vision
Click to expand...
Click to collapse
appreciate the info , thanks.
Erase Recovery option
Call me naïve, but if people are making full-blown builds with an image recovery and everything from the CM gingerbread source (which includes the Clockwork Mod recovery 3.0.0 image if I'm reading the source properly), could you just go into ROM Manager, go into Settings, and check the "Erase Recovery" option to allow it to erase the recovery between flashes?
I would test this myself, but I need to go home and make myself fresh builds of CM7 and CM6.2 to try swapping/flashing back and forth between. I can report back once I get around to it later this afternoon.
If I understand that option correctly, applying a full flash of these alpha builds of CM7 should write the new recovery image (v3.0.0.0), and if you need to switch back to CM6, you should be able to just reflash a full build of 6.1.1/6.2 back and it will restore the older recovery image (v2.5.1.8 according to the latest froyo version).
EDIT: Negate that thought. Not sure how you would go about forcing the recovery image flash while in recovery. I got to research this a little more...
Ok guys so here is a little something i have been working on for yall. some of you may know rom manager and all its abilities (download roms and flash them without needing a computer, aka "OTA custom roms") well its done. only one team has the roms up and listed right now. now here is for the issues;
-rom manager does not recognize anything but 2.5.1.0 which is the first version of cwm we had going. afaik there are no plans to let it see cwm3 on teh epic
-any roms put on the list will be under premium, sorry ive tried talking to koush but this means you would need to have rom manager premium
now i am hoping we can get more rom devs up on the list and push for cwm3 to be recognized so that users of a certain rom can get notifications of updates and download them via wifi/4g/3g whenever they want. obviously i dont expect people to pay for the premium rom manager when they cant get the free one working.
if any rom devs wish to have their roms added to the list i will not do it for you but after a couple of hours of screwing with the lists (they are javascript.... >.<) i can offer some help on what may not be working. i am in the irc channels almost all the time, if you cant reach me there then shoot me a pm..
P.S. you may be wondering why i posted this in general eh? because this is partially for devs, but its for the users of the epic.. if this is a feature you want then yall need to speak up cuz as it stands now its pretty useless, im hoping by putting this out there that there will be enough of a cry for it that the situation gets handled and then everyone can use koush's awesome program
shabbypenguin said:
Ok guys so here is a little something i have been working on for yall. some of you may know rom manager and all its abilities (download roms and flash them without needing a computer, aka "OTA custom roms") well its done. only one team has the roms up and listed right now. now here is for the issues;
-rom manager does not recognize anything but 2.5.1.0 which is the first version of cwm we had going. afaik there are no plans to let it see cwm3 on teh epic
-any roms put on the list will be under premium, sorry ive tried talking to koush but this means you would need to have rom manager premium
now i am hoping we can get more rom devs up on the list and push for cwm3 to be recognized so that users of a certain rom can get notifications of updates and download them via wifi/4g/3g whenever they want. obviously i dont expect people to pay for the premium rom manager when they cant get the free one working.
if any rom devs wish to have their roms added to the list i will not do it for you but after a couple of hours of screwing with the lists (they are javascript.... >.<) i can offer some help on what may not be working. i am in the irc channels almost all the time, if you cant reach me there then shoot me a pm..
P.S. you may be wondering why i posted this in general eh? because this is partially for devs, but its for the users of the epic.. if this is a feature you want then yall need to speak up cuz as it stands now its pretty useless, im hoping by putting this out there that there will be enough of a cry for it that the situation gets handled and then everyone can use koush's awesome program
Click to expand...
Click to collapse
I thought this app was a cool idea when I first saw it..... then I realized it didn't work, and I never installed it anymore. if you can get it going, that would be awesome.... you've got my vote!
yogi2010 said:
I thought this app was a cool idea when I first saw it..... then I realized it didn't work, and I never installed it anymore. if you can get it going, that would be awesome.... you've got my vote!
Click to expand...
Click to collapse
He got it working <_<'
Thanks a bunch shabby! This should help with user error issues when it comes to flashing =D
I never see any roms when I go to download roms and I have the premium I thought that was bs.
Epic 4g
jbadboy2007 said:
I never see any roms when I go to download roms and I have the premium I thought that was bs.
Epic 4g
Click to expand...
Click to collapse
tahts because no one ever took the time to post em on there. im hoping to change that
I'm currently running cwm3; but when I open ROM Manager it tell me im running 2.5.1.0...
With that said.. I wonder if it'll work? ;p
wait you get rom manager to work with cwm3???
shabbypenguin said:
wait you get rom manager to work with cwm3???
Click to expand...
Click to collapse
No no no. I'm a moron disregard what I said haha.
All thats happened is ROM Manager thinks I'm running 2.5.1.0 when I'm not.
But; shouldn't this just be a redirector issue?
right but even with it thinking you have 2.5.1.0, what version of cwm do you have? does it pop up and ask you to install cwm version x.x.x.x???
I'm running cwm 3 running ext4.
Rom manager works on the phone; but anytime it needs to go into cwm it fails.
It'll hang at the sammy logo. Pulling the battery and powering the phone up normally does the same.
However..doing the three button recovery boot it attempts to load cwm and fails then gives me the Triangle with an Exclamation point inside it..along with the green android.
so how do you get into recovery? also is it 3.0.0.5 or 3.0.0.6?
shabbypenguin said:
so how do you get into recovery? also is it 3.0.0.5 or 3.0.0.6?
Click to expand...
Click to collapse
3.0.0.6
I'm unable to get into recovery through the manager it self. Once I do the three finger salute..it attempts to load and fails; I pull battery and just hold the power button and it loads into cwm.
ok so sounds like 3.0.0.6 is sorta working but we just need to be able to get into recovery normally now....
3.0.0.5 is confirmed to not be working at all
I would love this... had premium on my hero, but sadly I cannot use it on my epic.
Sent from my Samsung-SPH-D700 using Tapatalk
shabbypenguin said:
ok so sounds like 3.0.0.6 is sorta working but we just need to be able to get into recovery normally now....
3.0.0.5 is confirmed to not be working at all
Click to expand...
Click to collapse
Seems to me like it's just a redirector issue; but I've yet to dig into this too deeply so I could be wrong.
It seems to work fine..it just has issues loading directly into cwm.
Hey peeps hopefully someone here can help with almost similar problem.
I used one click root with cwm recovery 2.5.5 in both 2.1 DI18 and EB13. The recovery installed just fine on both.
When I download Rom manager from clockworkmod it doesnt detect that the recovery is installed. I cant do anything without installing the recovery according to ROM manager.
BUT it is installed! Why doesnt it detect it??
How can I get the rom manager to see that I do have clockworkmod recovery 2.5.5 installed?
Or is it not possible yet? I too am a suckered premium owner.
ErlyD said:
Hey peeps hopefully someone here can help with almost similar problem.
I used one click root with cwm recovery 2.5.5 in both 2.1 DI18 and EB13. The recovery installed just fine on both.
When I download Rom manager from clockworkmod it doesnt detect that the recovery is installed. I cant do anything without installing the recovery according to ROM manager.
BUT it is installed! Why doesnt it detect it??
How can I get the rom manager to see that I do have clockworkmod recovery 2.5.5 installed?
Or is it not possible yet? I too am a suckered premium owner.
Click to expand...
Click to collapse
I don't think that ROM Manager can detect recoveries on the phones partitions. I believe it downloads and installs recovery to the sd card.
I some how managed to get an older recovery installed 2.5.1 But still get "an error occured while downloading your recovery." when I click any option and select samsung epic from the prompted list. In an attempt to install the recovery.
If it doesn't install to the fixed partitions how does it install the recovery to boot from? I thought thats where it had to be? That would mean the current recovery I have is in the SD card? then a simple edit of a file would allow it to be detected?
ErlyD said:
I some how managed to get an older recovery installed 2.5.1 But still get "an error occured while downloading your recovery." when I click any option and select samsung epic from the prompted list. In an attempt to install the recovery.
If it doesn't install to the fixed partitions how does it install the recovery to boot from? I thought thats where it had to be? That would mean the current recovery I have is in the SD card? then a simple edit of a file would allow it to be detected?
Click to expand...
Click to collapse
I believe ROM Manager uses the stock recovery to redirect to a zip file on the sd. If the redirector isn't set up right it won't work. The One-Clicks we use to install CWM install it to fixed partition.
I do see that the ACS team is on board with this, hope to see more support soon. On my buddies Fastinate there is quite a bit to work with in Rom Manager, it is a very cool option.
Thanks to all the Dev's
Sent from DEEZ
[Solved!!]
When I open CWM I always get this error (see attached image) I have tried flashing an older version of CWM and I still get it... I have searched a TON to find the answer to this and it seems really common on Nexus S owners but I haven't found a solution... But because of this I can no longer flash anything.
Any ideas? I have fastboot erased EVERYTHING even tried fastboot flashing a Nandroid that I KNOW is a good backup... it seems to work but when I go to boot the device I get stuck that the bootscreen :/
[Solved!!!]
Anyone ever runs into this issue, flash CWM 2.X.X.X go to mounts, mount cache then format it. I couldn't mount cache in 3.X.X.X but it worked in 2.X.X.X. Not sure why this worked but whatever! lol
UPDATE!!!
SO the CWM Ghost is back, once again. Still nothing out of the ordanary done on my part, just started getting random FC's and boom there it's ugly mug is when I go to CWM to fix permissions...
BUT, here is the problem, I'm trying to fix it how I did last time and when I go to flash the new recovery in Fastboot via ADB I get this error:
sending 'recovery' <4000 KB>... OKAY [15.390s]
writing 'recovery' ...FAILED <remote: image update error>
I have tried a few different CWM recovery downloads... any ideas?
dcwiker05 said:
[Solved!!]
When I open CWM I always get this error (see attached image) I have tried flashing an older version of CWM and I still get it... I have searched a TON to find the answer to this and it seems really common on Nexus S owners but I haven't found a solution... But because of this I can no longer flash anything.
Any ideas? I have fastboot erased EVERYTHING even tried fastboot flashing a Nandroid that I KNOW is a good backup... it seems to work but when I go to boot the device I get stuck that the bootscreen :/
[Solved!!!]
Anyone ever runs into this issue, flash CWM 2.X.X.X go to mounts, mount cache then format it. I couldn't mount cache in 3.X.X.X but it worked in 2.X.X.X. Not sure why this worked but whatever! lol
Click to expand...
Click to collapse
You know, even though you solved it, I still think you should send a note to koush... the creator of CWM....
faux123 said:
You know, even though you solved it, I still think you should send a note to koush... the creator of CWM....
Click to expand...
Click to collapse
I sent him a private message detailing what led up to the error (and may or may not have caused it) as well as a link to this thread.
dcwiker05 said:
I sent him a private message detailing what led up to the error (and may or may not have caused it) as well as a link to this thread.
Click to expand...
Click to collapse
glad you fixed it, as many ppl have had this issue and have yet to recover from it!!! also, since you had fastboot set up i am assuming you have the 85.2007 engineering bootloader, correct?
i saw this preview post and all i could say is the cwm ghost got another one but it seems you got lucky!!!
irrelephant said:
glad you fixed it, as many ppl have had this issue and have yet to recover from it!!! also, since you had fastboot set up i am assuming you have the 85.2007 engineering bootloader, correct?
i saw this preview post and all i could say is the cwm ghost got another one but it seems you got lucky!!!
Click to expand...
Click to collapse
I would say "lucky" as well. but i'm wondering if the 2.x recovery image might be the fix for this problem. If one could "brick" their phone with the same symptoms as this phone. Then flash the 2.x recovery and see if it fixes the problems.
Yeah I have 85. Bootloader, because I read to flash CM7 it was best to have that installed. As for me fitting lucky yeah I guess I did, I didn't realize this was one of those "end all" errors lol. Specially since I really have no clue what possessed me to flash the old clock work. Basically I felt there had been known issues with 3.X. so I thought "what would it hurt?" Turns out it helped!!! I'm using the phone now and everything is 100%
Sent from the depths of hell cuz XDA's app is THAT good!!
dcwiker05 said:
Yeah I have 85. Bootloader, because I read to flash CM7 it was best to have that installed. As for me fitting lucky yeah I guess I did, I didn't realize this was one of those "end all" errors lol. Specially since I really have no clue what possessed me to flash the old clock work. Basically I felt there had been known issues with 3.X. so I thought "what would it hurt?" Turns out it helped!!! I'm using the phone now and everything is 100%
Sent from the depths of hell cuz XDA's app is THAT good!!
Click to expand...
Click to collapse
Nice i'm going to remember this thread.
TOPSIDE for some new developments. See OP for update...
I believe TrueBlue_Drew has a flashable zip for CWM 2.5.1.2 Have you tried that?
hello i need that recovery 2.___ for fix my problem same that! where i cant find_
vabeach454 said:
I believe TrueBlue_Drew has a flashable zip for CWM 2.5.1.2 Have you tried that?
Click to expand...
Click to collapse
I think I found what you are talking about HERE but from what I gather that needs your phone able to boot cuz it changes the recovery via Rom Manager. Sadly my phone doesn't boot, all I have is hboot and the 3.1.2.4 recovery available to use, both of which are basically broken. Thanks for the help and the idea though I really hope we come up with a way to fix this somehow. Any dev who needs a phone to experiment on, hit me up.
dcwiker05 said:
I think I found what you are talking about HERE but from what I gather that needs your phone able to boot cuz it changes the recovery via Rom Manager. Sadly my phone doesn't boot, all I have is hboot and the 3.1.2.4 recovery available to use, both of which are basically broken. Thanks for the help and the idea though I really hope we come up with a way to fix this somehow. Any dev who needs a phone to experiment on, hit me up.
Click to expand...
Click to collapse
Download zip from thread. Extract it to desktop or location of your choice. Go into the folders and find the recovery img that has 2.5.1.4 in the name. That is actually the 2.5.1.2 recovery. You can then re-name it to what ever you need to and push it to your device.
Hope this helps.
victorx said:
hello i need that recovery 2.___ for fix my problem same that! where i cant find_
Click to expand...
Click to collapse
Download this navigate to this (C:\Users\YOURUSERNAME\Recovery_2.5.1.2_to_RomManager.zip\sdcard\clockworkmod\download\mirrorbrain.cyanogenmod.com\cm\recoveries\) extract the recovery 2.5.1.2. Rename it recovery.img and try to flash it via adb in hboot (fastboot flash recovery recovery I BELIEVE that is the command I can't honestly remember but a quick google search will yield you a adb guide no problem
TrueBlue_Drew said:
Download zip from thread. Extract it to desktop or location of your choice. Go into the folders and find the recovery img that has 2.5.1.4 in the name. That is actually the 2.5.1.2 recovery. You can then re-name it to what ever you need to and push it to your device.
Hope this helps.
Click to expand...
Click to collapse
I can't push to my device which is the COMMAND problem. Now when I try to push via ADB I get an error saying write---FAILED. I have tried a few other tricks I have been told as well about like repartitionion the cache via ADB and that doesn't work either. So I hope this works for the OP
Due to koush for releasing a wonderful tool to the android community i threw in the current cwm into the builder and it came out with a new and shiny version!
Known Issues
Don't boot into recovery using rom manager, as is it will boot u into older version.. but if u delete the recovery-update.zip in the clockworkmod folder it will boot into the new recovery but with an error
The background images for the recovery are huge x_X
Recovery: recovery-clockwork-5.8.4.3-desirec.img
md5sum: db3e9d93c7f1f52a427b7f6ca427cabf
mine, just in case!
Do you have an Eris that you're testing this on? I was under the impression that CWM and ROM Manager didn't play nicely with the Eris. What's your experience been?
KarateExplosion6 said:
Do you have an Eris that you're testing this on? I was under the impression that CWM and ROM Manager didn't play nicely with the Eris. What's your experience been?
Click to expand...
Click to collapse
ya, I have an Eris.. I think that was long time ago which has been solved before even the latest official cwm..
I left the Eris long ago but keep it around as a pmp, since my trackball doesnt scroll and the mic is busted.. when I started using it again I couldn't flash anything new because I was on amonRA.. so I took the plunge and used cwm and I haven't ran into a single issue.. there, that's my Eris history xP right now I have it on cm7.2 stable
Sent from my Galaxy Nexus using Tapatalk 2
swordrune10 said:
ya, I have an Eris.. I think that was long time ago which has been solved before even the latest official cwm..
I left the Eris long ago but keep it around as a pmp, since my trackball doesnt scroll and the mic is busted.. when I started using it again I couldn't flash anything new because I was on amonRA.. so I took the plunge and used cwm and I haven't ran into a single issue.. there, that's my Eris history xP right now I have it on cm7.2 stable
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Fantastic! I was actually looking for someone running CM7.2 Stable. My brother is using my Eris and I've had him on xtrSense forever. I'd like to flash him up to Gingerbread. What do you think of the stable release?
KarateExplosion6 said:
Fantastic! I was actually looking for someone running CM7.2 Stable. My brother is using my Eris and I've had him on xtrSense forever. I'd like to flash him up to Gingerbread. What do you think of the stable release?
Click to expand...
Click to collapse
the only thing I have to say since I barely use the thing is that I have installed is a 32gb sdcard and before on 7.1 it sometimes didn't finish the boot cycle because every so often it gets stuck at checking sdcard.. now its more likely to boot completely.. don't get me wrong, it still sometimes gets stuck on boot... again fault is because of the 32gb sdcard.. and me having to have lots of music...
Sent from my Galaxy Nexus using Tapatalk 2
swordrune10 said:
the only thing I have to say since I barely use the thing is that I have installed is a 32gb sdcard and before on 7.1 it sometimes didn't finish the boot cycle because every so often it gets stuck at checking sdcard.. now its more likely to boot completely.. don't get me wrong, it still sometimes gets stuck on boot... again fault is because of the 32gb sdcard.. and me having to have lots of music...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Shouldn't matter to my brother. He doesn't even use an SD card!!
KarateExplosion6 said:
Shouldn't matter to my brother. He doesn't even use an SD card!!
Click to expand...
Click to collapse
x_X before I switched I used cm5 (unofficial) on Eris, it was good.. gingerbread is ok on it.. but ics on a better phone is a lot better
Sent from my Galaxy Nexus using Tapatalk 2
swordrune10 said:
Due to koush for releasing a wonderful tool to the android community i threw in the current cwm into the builder and it came out with a new and shiny version!
Known Issues
Don't boot into recovery using rom manager, as is it will boot u into older version.. but if u delete the recovery-update.zip in the clockworkmod folder it will boot into the new recovery but with an error
The background images for the recovery are huge x_X
Recovery: recovery-clockwork-5.8.4.3-desirec.img
md5sum: db3e9d93c7f1f52a427b7f6ca427cabf
Click to expand...
Click to collapse
How does the tool work? I want to get this to work on my htc hero gsm
jordfaz said:
How does the tool work? I want to get this to work on my htc hero gsm
Click to expand...
Click to collapse
what u do is u go to the site and insert a recovery ( even stock ) for ur device and it builds it for ur based on cwm.. fortunately ( or unforunately, if u wanted to do it urself ) there was already one done for the hero =] .... yes that means i looked through a good amount of them just to see what people were building x.x
swordrune10 said:
ya, I have an Eris.. I think that was long time ago which has been solved before even the latest official cwm..
Click to expand...
Click to collapse
There are lots of posts on this site (and on others), many relatively recent, from people with Erises that cannot boot that almost all started with a person who was running with ClockworkMod as their recovery image; none that I know of from people who started with Amon_RA. Scary Alien made a trackball-optional version of Amon_RA (with Amon_RA's permission) for the Eris which works with the hardware keys as well as the trackball. See http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
So, be careful with Clockwork Recovery.
doogald said:
There are lots of posts on this site (and on others), many relatively recent, from people with Erises that cannot boot that almost all started with a person who was running with ClockworkMod as their recovery image; none that I know of from people who started with Amon_RA. Scary Alien made a trackball-optional version of Amon_RA (with Amon_RA's permission) for the Eris which works with the hardware keys as well as the trackball. See http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
So, be careful with Clockwork Recovery.
Click to expand...
Click to collapse
I seriously think the issues have been resolved.. the way koush works on them brings what he did before to the next recovery he makes.. if that issue was still around there would be a lot of phones not booting..
Sent from my Galaxy Nexus using Tapatalk 2
swordrune10 said:
I seriously think the issues have been resolved.. the way koush works on them brings what he did before to the next recovery he makes.. if that issue was still around there would be a lot of phones not booting..
Click to expand...
Click to collapse
There was just an issue a week or two ago. http://forum.xda-developers.com/showthread.php?t=1702130
That's pretty typical - for some reason, these phones end up with bad blocks in some partitions (usually system.img, cache.img) that are difficult to resolve.
Note that you can install ROM Manager on a CM ROM and hit "install recovery". This installs an update.zip file in the root of the SD card. From Amon_RA you can flash the update.zip and it will start Clockwork. That method seems to be safe and is the way that I flash, Nandroid, etc., on the Eris.
Again, this seems to be an Eris issue with Clockwork as the default recovery. If it works for you, that's fine, but I would try to get on the 1.49.2000 S-OFF bootloader so that you can use fastboot as a recovery tool if you are not on that bootloader already.
doogald said:
There was just an issue a week or two ago. http://forum.xda-developers.com/showthread.php?t=1702130
That's pretty typical - for some reason, these phones end up with bad blocks in some partitions (usually system.img, cache.img) that are difficult to resolve.
Note that you can install ROM Manager on a CM ROM and hit "install recovery". This installs an update.zip file in the root of the SD card. From Amon_RA you can flash the update.zip and it will start Clockwork. That method seems to be safe and is the way that I flash, Nandroid, etc., on the Eris.
Again, this seems to be an Eris issue with Clockwork as the default recovery. If it works for you, that's fine, but I would try to get on the 1.49.2000 S-OFF bootloader so that you can use fastboot as a recovery tool if you are not on that bootloader already.
Click to expand...
Click to collapse
Yeah, that's how I always thought was the safest way to do it--running CWM from ROM Manager.
Yep, been using ROM Manager, and CWM through update.zip via Amon RA for a year and a half now without any issues. I don't think I'd ever be tempted to flash CWM over Amon RA; I'd rather have the best of both worlds without wondering if I'm taking any additional risk.
well.. I understand everyone's opinion and its cool.. I tried working on making a recovery.zip that just restarted the recovery not overwrite it, but it just wouldn't do it =/
Sent from my Galaxy Nexus using Tapatalk 2