Related
Your feedback has helped me add all sorts of goodies and changes!
Confirmation on all restores, wipes, and anything that would otherwise change your system.
Alphabetically sorted zip and nandroid lists.
Support for all ext2/3/4 partitions.
Added a back button/power button select for ephumuris!!!!! When recovery starts, press up/down/up/down to turn it on or off. (Basically, scroll over the top/bottom of the menu several times)
Better error integration with ROM Manager.
Command line nandroid.
Backup of Froyo apps2sd!
Test Drive it with fakeflash:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-bravo.zip
Image to use with Unrevoked 3:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-bravo.img
You're a genius, man.
Well done!
Thanks!
nice one, cheers
ah, it would be awesome if you add a partiotion sd function into recovery
yeah is format partition on there pal? so we can create ext2, etc?
Hmmm, ROM manager still does not have the latest version updated, do I need to do anything to make it see this new version?
Nice , will test it out Thanks
Vulpix said:
Hmmm, ROM manager still does not have the latest version updated, do I need to do anything to make it see this new version?
Click to expand...
Click to collapse
Since this is experimental, it is only available if you scroll to the bottom and select "All ClockworkMod Recoveries".
Koush said:
Since this is experimental, it is only available if you scroll to the bottom and select "All ClockworkMod Recoveries".
Click to expand...
Click to collapse
Oh okay, so this is considered a beta?
Vulpix said:
Oh okay, so this is considered a beta?
Click to expand...
Click to collapse
Yes, I need some feedback and bug reports before I can release it into the wild on ROM Manager That's why I came to XDA first
can't get into 2.5 is stuck on bootscreen.. Running defrost 2.0f recovery doesn't work in unrevoked and not trew rommanager..
Just flashed using Unrevocked 3 and got stuck at the white HTC screen.
Left it for 5, pulled the battery and tried to enter recovery. The same again.
Pulled, rebooted to the OS and re-flashed the new Unrevoked without the custom image and I now have access to recovery 2.0.2.4.
freddyemmer said:
can't get into 2.5 is stuck on bootscreen.. Running defrost 2.0f recovery doesn't work in unrevoked and not trew rommanager..
Click to expand...
Click to collapse
How did you install? If you used the fakeflash zip it is completely harmless.
qubit76 said:
Just flashed using Unrevocked 3 and got stuck at the white HTC screen.
Left it for 5, pulled the battery and tried to enter recovery. The same again.
Pulled, rebooted to the OS and re-flashed the new Unrevoked without the custom image and I now have access to recovery 2.0.2.4.
Click to expand...
Click to collapse
Hmm let me figure out what's wrong.
Vulpix said:
Hmmm, ROM manager still does not have the latest version updated, do I need to do anything to make it see this new version?
Click to expand...
Click to collapse
same here...
also the filename in the link provided in first post says:"legend"...is it right?
LOL wow i am dumb. I posted legend recovery images (sorry, I support 17 devices, and I made bad copy paste mistake Updating links now!
why are links to *legend.* files, this is desire forum?
edit: nvm
nbedford said:
why are links to *legend.* files, this is desire forum?
Click to expand...
Click to collapse
Fixed, sorry!
How easy/hard is it to do it? I am currently running Amon-Ra, moved to Cyanogen Mod and want to use Clockwork to grab the nightly builds. Is it as simple as installing it in the Clockwork app menu? I don't want to break anything, so I'd appreciate an answer before I do it.
Thanks in advance!
Not hard at all especially if you use rom manager
Just flash it from ROM Manager. If you want to keep your backups, copy /sdcard/nandroid/ to the ROM Manager Nandroid folder... Which I forget off the top of my head.
I suppose it's easy, but when I tried to flash Amon-RA today, it just booted me into fastboot, and I couldn't get to recovery until I flashed back clockwork. It could also just be because I did something to my rom, and I also can't install anything, from anywhere >_>
but you know, meh
mistersquirrle said:
I suppose it's easy, but when I tried to flash Amon-RA today, it just booted me into fastboot, and I couldn't get to recovery until I flashed back clockwork. It could also just be because I did something to my rom, and I also can't install anything, from anywhere >_>
but you know, meh
Click to expand...
Click to collapse
Same thing happened to me w/ Amon-Ra. I guess I'm going to use Clockwork forever.
mylasthope said:
Same thing happened to me w/ Amon-Ra. I guess I'm going to use Clockwork forever.
Click to expand...
Click to collapse
did you try flashing Amon-RA from ROM manager? maybe it's just doing something wrong with it cause it likes clockwork to much
mistersquirrle said:
did you try flashing Amon-RA from ROM manager? maybe it's just doing something wrong with it cause it likes clockwork to much
Click to expand...
Click to collapse
Exactly what I did. I'm not too root-saavy so I don't know how else to flash amon-ra. lol.
mylasthope said:
Exactly what I did. I'm not too root-saavy so I don't know how else to flash amon-ra. lol.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=705026
This is the Amon-RA recovery topic, and near the bottom of his post, it tells you how to do it manually, then you can just use ROM Manager to get back to Clockwork if needed
mistersquirrle said:
http://forum.xda-developers.com/showthread.php?t=705026
This is the Amon-RA recovery topic, and near the bottom of his post, it tells you how to do it manually, then you can just use ROM Manager to get back to Clockwork if needed
Click to expand...
Click to collapse
Thanks for the link, but I still can't get it to flash. I tried fastboot and nothing opens up. I then tried on ADB, but I get the following error: mtd: not writing bad block at 0x00340000
mylasthope said:
Thanks for the link, but I still can't get it to flash. I tried fastboot and nothing opens up. I then tried on ADB, but I get the following error: mtd: not writing bad block at 0x00340000
Click to expand...
Click to collapse
no clue. I haven't tried it myself yet. I was thinking about it earlier... but I'm lazy. Maybe just try again? or do it from a terminal on the phone (using connectbot or something)
mistersquirrle said:
no clue. I haven't tried it myself yet. I was thinking about it earlier... but I'm lazy. Maybe just try again? or do it from a terminal on the phone (using connectbot or something)
Click to expand...
Click to collapse
Haha. Thanks. I'm done fooling around w/ Ra. Clockwork has worked just fine for me, even though it doesn't wipe dalvik.
I have the same issue. I cant get it to work. I get the Writing... FAILED: (update image error)
Got clockwork to work again. i might download amon again?
One thing to remember though (from what I've seen), is that they use nand differently, so if you back something up with clockwork, make sure you restore it with clockwork or it may not restore correctly. If you backup with clockwork, restore with clockwork. If you backup with ar, restore with ar.
Sent from my blah blah blah blah
Hi, guys, please advise, what am I doing wrong?
Trying to put LeeDrOiD 2.4.1 A2SD.
Doing a full wipe.
Created a ex2, then converted to ex3.
Flashing ok but after reboot, shows the logo and all here, waiting for nearly an hour.
ps while writing the post, decided to try to put LeeDrOiD 2.4.1 without a2sd - got no problems. I'm at a loss
LeeDroid gave me infininite reboots while loading, specialy in the latest versions (3.0.x), which recovery do you have?
flaffy said:
Hi, guys, please advise, what am I doing wrong?
Trying to put LeeDrOiD 2.4.1 A2SD.
Doing a full wipe.
Created a ex2, then converted to ex3.
Flashing ok but after reboot, shows the logo and all here, waiting for nearly an hour.
ps while writing the post, decided to try to put LeeDrOiD 2.4.1 without a2sd - got no problems. I'm at a loss
Click to expand...
Click to collapse
What recovery are you using?
AmonRa - v.1.7.0.2-R5
hmmmm.... Update recovery can help solve the problem?
flaffy said:
AmonRa - v.1.7.0.2-R5
hmmmm.... Update recovery can help solve the problem?
Click to expand...
Click to collapse
Maybe... I just installed LeeDrOiD v3.0.5 with AmonRa v.2.0.1 and A2SD+ works perfect
Sent from my HTC Desire using XDA App
MatDrOiD said:
Maybe... I just installed LeeDrOiD v3.0.5 with AmonRa v.2.0.1 and A2SD+ works perfect
Click to expand...
Click to collapse
Thx! went to update my recovery
flaffy said:
Created a ex2, then converted to ex3.
Click to expand...
Click to collapse
Make your main fat32 partition first then make your ext3(512mb or 1gb whatever you think you'll need). If your gonna make an ext why not just make it a 3 to start, 2.4.1 supports ext3 + ext4. Maybe this will help?
hi, if needed here is a link with ARv2.0.1 http://dl.dropbox.com/u/22152187/recovery-RA-desire-v2.0.1.img
flash it through fasboot, the easest way (should need S-off to do so)
hope this help
nochains said:
LeeDroid gave me infininite reboots while loading, specialy in the latest versions (3.0.x), which recovery do you have?
Click to expand...
Click to collapse
I have the same problem with AmonRa 2.0.1 recovery and S-ON, 1 GB EXT-3 partition created through recovery.
Does anyone have a solution for this?
harrer said:
I have the same problem with AmonRa 2.0.1 recovery and S-ON, 1 GB EXT-3 partition created through recovery.
Does anyone have a solution for this?
Click to expand...
Click to collapse
Just try within the recovery and after flasing the rom to mount the sd card manually before booting.
It worked for me...
i've been using Leedroid 3.03 for the last week or so... before i installed the ROM i did s-off, mostly because it updates your HBOOT without having to re-root. If you dont have HBOOT at 0.93x there will be problems flashing the ROM. IDK why, not that technically minded, but when I read the threads for 3.x that was the consensus. Is your HBOOt up to date?
@thelloydr
My HBOOT is 0.93.0001
I guess it is ok?
bertrand13 said:
Just try within the recovery and after flasing the rom to mount the sd card manually before booting.
It worked for me...
Click to expand...
Click to collapse
I tried what you recomended.
Boot loop has gone, but I'm stuck on white HTC logo for almost an hour.
What did you mount exactly?
/system
/cache
/data
/sd-ext
/sdcard
?
harrer said:
I tried what you recomended.
Boot loop has gone, but I'm stuck on white HTC logo for almost an hour.
What did you mount exactly?
/system
/cache
/data
/sd-ext
/sdcard
?
Click to expand...
Click to collapse
I think I mounted /sd-ext
bertrand13 said:
I think I mounted /sd-ext
Click to expand...
Click to collapse
nevermind. thx.
i gave up and went back to CM7. it's faster anyway
Perfect work
Tiii said:
Perfect work
Click to expand...
Click to collapse
B-)
Sent from my HTC Desire using XDA App
ClockworkMod Recovery 6.0.1.4
Here is a CWM-Based 6.0.1.4 Recovery built from source
Disclaimer
I am not responsible if you break,brick,hump,throw against wall or any other action you do to your phone By using this recovery. you agree anything that happens is your own noobtastic fault. Any attempts at blaming me for anything other than this being fantastic will result in you being pointed and laughed at.
what is "recovery" ?
Recovery mode is a minimal, alternative mode of booting which allows you to install software from zip files, backup/restore your device, and perform low-level operations like factory reset and formatting partitions. All Android devices have a recovery mode (it's part of the stock AOSP environment), but the default recovery mode is very limited. For example, it only allows you to flash zips which have been signed by the vendor's private key.
ClockworkMod Recovery was developed by Koushik Dutta (@koush), and is much more flexible... If you want to flash CyanogenMod, you MUST have a non-stock recovery. Right now that means ClockworkMod Recovery.
Download link : http://www.mediafire.com/?on3x3oydjiy2i6j
How to install:
just flash the recovery zip
Changelog:
https://github.com/CyanogenMod/android_bootable_recovery/commits/jellybean
NOTE: koush's version of clockworkmod 6.0.1.4 that is in rom manager for the p350 is broken, installing koush version will brick your device. Please use this clockworkmod recovery
Features:
Latest fixes from upstream CM
fonts , graphic is like cwm 5
Power off charging
UI changes
Four times smaller backups
New CWM changes
Fully compatible with Rom Manager
ScreenShots:
soon....
Credits:
koush - for making cwm recovery
If you like this recovery then help me to feel up my thanks meter by pressing thanks button
maybe i need this later
last mine
now you can post your review
everything is ok, but mass storage mount is not working, screen is jumping up-down and font is too big...
key_master said:
everything is ok, but mass storage mount is not working, screen is jumping up-down and font is too big...
Click to expand...
Click to collapse
in next i will try to fix
this all bugs because i have build cwm from this site
http://builder.clockworkmod.com/
v6 source is not released
but i will try of fix
Touch Recovery? Or not?
Sent from my LG-P350 using Tapatalk 2
dbarrera said:
Touch Recovery? Or not?
Sent from my LG-P350 using Tapatalk 2
Click to expand...
Click to collapse
no touch recovery
i have AmonRa Recovery.
can i use this one to change my recovery??
Or is this Compatible to My Recovery??
why change ?
hello,
why would i use this ?
whats different from Amonra ?
and whats the EXT4 for ?
can i reformat the partition without deleting everything ? what is stored on that partition ?
thx for the Work on P350.
n1ck018 said:
i have AmonRa Recovery.
can i use this one to change my recovery??
Or is this Compatible to My Recovery??
Click to expand...
Click to collapse
yes you can use and yes compatible
benjamin3005 said:
hello,
why would i use this ?
whats different from Amonra ?
and whats the EXT4 for ?
can i reformat the partition without deleting everything ? what is stored on that partition ?
thx for the Work on P350.
Click to expand...
Click to collapse
amon ra 2.2.1 is old and this is new and compiled from ics branch, and why you need to reformat your sdcard partition, after flash recovery it will not delete your any sdcard partition and from wiki ext4 is
The ext4 or fourth extended filesystem is a journaling file system for Linux/Android, developed as the successor to ext3.
Restore not work
Skyff48 said:
Restore not work
Click to expand...
Click to collapse
v5.0.2.8 backup?
ron gokhle said:
yes you can use and yes compatible
Click to expand...
Click to collapse
OK ill try this 1:good:
ron gokhle said:
v5.0.2.8 backup?
Click to expand...
Click to collapse
No, in v5.0.2.8 backup work, but in v5.0.2.8 and v6.0.0.0 not work restore
Skyff48 said:
No, in v5.0.2.8 backup work, but in v5.0.2.8 and v6.0.0.0 not work restore
Click to expand...
Click to collapse
ok i mean you can't restore your 5.0.2.8 backup in v6.x.x.x . This are diff version i already posted note about this in 1st post
n1ck018 said:
OK ill try this 1:good:
Click to expand...
Click to collapse
if you think i will use this then make sure your backup made by amon ra will not restore in cwm
TOO hard to use ..
can u edit the size of the font its to big
and Why it read so slow??
n1ck018 said:
TOO hard to use ..
can u edit the size of the font its to big
and Why it read so slow??
Click to expand...
Click to collapse
i'm working to fix this in next version
ron gokhle said:
i'm working to fix this in next version
Click to expand...
Click to collapse
nc thx! :good:
I've been searching for a solution before writing my own post, for I'm aware there are probably many, many topics of people dealing with the same issue.
Well, here's is my problem.
I've got two wildfires A3333. Flashed CM 7.2.0 on both of them, successfully. GPS does work on only one of them. I've tried the GPS test on the other one. The compass is working, the localization is not.
So, as said before, I've googled for some solution for the other one, and here comes the temporary downgrading of CWM to 2.5.0.7 and then installing one of the following: buzz.radio-3.35.15.31-signed.zip, buzz.radio-3.35.20.10-signed.zip or buzz.radio-3.35.19.25-signed.zip that will be put on the SD.
Ok, everything is set up, let's reboot to recovery.
Now, the recovery screen is showing version 3.0.0.6 and I don't know if that's normal, since I've set it to 2.5.0.7 before rebooting. Won't mind for now.
Let's flash the zips. And all I get is this message, with all of the radios:
E: signature verification failed
Installation aborted.
Uhm, let's try by setting the option toggle signature verification to disabled.
Here's a different message:
Amend scripting (update-script) is no longer supported. Amend scripting was deprecated by Google in Android 1.5. It was necessary to remove it when upgrading to the Clockworkmod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation aborted.
It seems that the 3.0.0.6 version shown on the main menu is kind of relevant... Should it show 2.5.0.7 instead of that? What now?
Thanks in advance.
After flashing the temporary CWM,it'll automatically boot into that CWM version. Now flash the radio with that.
And if you reboot you'll return to the CWM version you had before.
To fix GPS you could also use this method,
http://forum.xda-developers.com/showthread.php?t=2354499
lakshan_456 said:
After flashing the temporary CWM,it'll automatically boot into that CWM version. Now flash the radio with that.
And if you reboot you'll return to the CWM version you had before.
To fix GPS you could also use this method,
http://forum.xda-developers.com/showthread.php?t=2354499
Click to expand...
Click to collapse
Yes, if by "flashing the temporary CWM" you mean entering the ROM manager, tapping on All ClockwordMod Recoveries, download the 2.5.0.7 version, let it install and tap Reboot into recovery, well that's exactly what I did. And the recovery screen is showing me this 3.0.0.6 version anyway, which is kind of suspicious to me.
I've already read the topic you linked, some days ago, but that means having to wipe the CM 7.2.0 and reinstall it later and I'm not sure whether I can backup the apps that are in the EXT partition since I'm using Link2SD. And honestly, I'm not even sure I'm able to make a good backup.
Snakebar said:
Yes, if by "flashing the temporary CWM" you mean entering the ROM manager, tapping on All ClockwordMod Recoveries, download the 2.5.0.7 version, let it install and tap Reboot into recovery, well that's exactly what I did. And the recovery screen is showing me this 3.0.0.6 version anyway, which is kind of suspicious to me.
I've already read the topic you linked, some days ago, but that means having to wipe the CM 7.2.0 and reinstall it later and I'm not sure whether I can backup the apps that are in the EXT partition since I'm using Link2SD. And honestly, I'm not even sure I'm able to make a good backup.
Click to expand...
Click to collapse
I wouldn't really recommend using ROM Manager, and what I meant by flashing was to flash the CWM zip with your current Clockworkmod recovery.
And also consider upgrading your recovery.
And about the guide, just make a nandroid backup with CWM, and restore it instead of flashing a new rom.
Hope this helps
I shall give a try to it all and let you know.
One last question before I proceed. In order to upgrade my recovery I'd have to download the latest CWM available for Buzz and install it the same way I'll do with v2.5.0.7 (of course, after that step), am I right?
Thanks!
Ok, I've installed the v2.5.0.7 via the install from .zip option and got to install the radios. Woo!!
No, hold back.
Now the GPS icon is showing up but GPStest doesn't detect any activity.
I've installed 13.55.55.24H_3.35.20.10 first, then 13.45.55.24H_3.35.15.31 and then 13.53.55.24H_3.35.19.25. Same result.
Now should I rely on plan B?
I've read of someone who got it working by installing the 3 radios in crescent order. Is it worth a try?
Snakebar said:
I shall give a try to it all and let you know.
One last question before I proceed. In order to upgrade my recovery I'd have to download the latest CWM available for Buzz and install it the same way I'll do with v2.5.0.7 (of course, after that step), am I right?
Thanks!
Click to expand...
Click to collapse
No, that'll only be temporary, as with 2.5.
Get the PC49IMG.zip file for that recovery, put it on the root of the SD, reboot to bootloader, it'll scan and will ask to install, select yes, you're done.
First GPS fix will take some time, maybe from 2-10 mins.
I've only flashed the .20.10 Radio. It worked for me...
Or if you have a sense rom or the backup of your stock rom, give the guide a try...
Try this radio file. link, worked for me under cwm 2.5.0.7
lakshan_456 said:
No, that'll only be temporary, as with 2.5.
Get the PC49IMG.zip file for that recovery, put it on the root of the SD, reboot to bootloader, it'll scan and will ask to install, select yes, you're done.
First GPS fix will take some time, maybe from 2-10 mins.
I've only flashed the .20.10 Radio. It worked for me...
Or if you have a sense rom or the backup of your stock rom, give the guide a try...
Click to expand...
Click to collapse
My fault, there's something I should make clear.
The radios I've been talking about before have been installed on the first Wildfire, the one I said the GPS was working (and in the meanwhile it proved to be untrue as I discovered the GPS icon has never showed up before flashing the radio). This one Wildfire has CWM 2.5.0.1, installed with Unrevoked. The second Wildfire (which I'd like to use as my usual phone) was rooted with PC49IMG as Unrevoked wouldn't work with it and is running CWM 3.0.0.6, which I've reported in the first post.
For now, let's discard the CWM 3.0.0.6 phone.
It is on the CWM 2.5.0.1 phone where I've temporarily installed 2.5.0.7 and flashed the radios. Could it be relevant?
(maybe I'd better update the CWM anyway)
ChristianPe said:
Try this radio file. link, worked for me under cwm 2.5.0.7
Click to expand...
Click to collapse
Uhm, link is broken. My CWM 2.5.0.7 looks to be working properly anyway.
stick with 2.5.0.7 recovery and 20.10 radios, that worked for me using Navitel, as for file here.
Flashed Froyo 2.2.1 shipped ROM... and GPS didn't work on it either. Great.
I've restored my CM backup and found out all my link2SD linked apps to be screwed in return. Vanished. Link2SD says there's soooo much free space in that second partition... can't imagine when it's been formatted, but nevermind.
ChristianPe said:
stick with 2.5.0.7 recovery and 20.10 radios, that worked for me using Navitel, as for file here.
Click to expand...
Click to collapse
I've already got that radio version but tried to flash the one you've gently provided me, well, same as the other radios. Icon showing but no activity at all.
I give up.
Snakebar said:
Flashed Froyo 2.2.1 shipped ROM... and GPS didn't work on it either. Great.
I've restored my CM backup and found out all my link2SD linked apps to be screwed in return. Vanished. Link2SD says there's soooo much free space in that second partition... can't imagine when it's been formatted, but nevermind.
I've already got that radio version but tried to flash the one you've gently provided me, well, same as the other radios. Icon showing but no activity at all.
I give up.
Click to expand...
Click to collapse
where you at?, i might be a weather-related issue?
ChristianPe said:
where you at?, i might be a weather-related issue?
Click to expand...
Click to collapse
Unlikely, it's been some days I'm testing the GPS on the phone. But I shall test it away from home to be sure.
I'm from Naples, (IT) by the way.
Snakebar said:
It is on the CWM 2.5.0.1 phone where I've temporarily installed 2.5.0.7 and flashed the radios. Could it be relevant?
(maybe I'd better update the CWM anyway)
Click to expand...
Click to collapse
Not really sure if CWM matters or not, we use 2.5 to flash radios because the flashing script is different from currently used ones.
Ty upgrading anyway,
Are you sure it isn't a hardware fault. If GPS doesnt work in stock rom, it could possibly be a hardware issue...
lakshan_456 said:
Not really sure if CWM matters or not, we use 2.5 to flash radios because the flashing script is different from currently used ones.
Ty upgrading anyway,
Are you sure it isn't a hardware fault. If GPS doesnt work in stock rom, it could possibly be a hardware issue...
Click to expand...
Click to collapse
Too weird it happens on both devices, even if... well them both have had a nice dive in the sea but GPS used to work before flashing the new ROMs on each phone.
Sure there's something not correct in my procedure but can't find it out.
Snakebar said:
Too weird it happens on both devices, even if... well them both have had a nice dive in the sea but GPS used to work before flashing the new ROMs on each phone.
Sure there's something not correct in my procedure but can't find it out.
Click to expand...
Click to collapse
Well, I'm sorry mate. unless its a hardware fault or something I'm not in the know of, there are no more solutions I can think of.
Behold! He's thinking back.
It just looks like it's not able to track many satellites. Well, at least that's a relief.
Snakebar said:
Behold! He's thinking back.
It just looks like it's not able to track many satellites. Well, at least that's a relief.
Click to expand...
Click to collapse
Indeed it is, atleast it wasn't a hardware issue
Well done mate...
P.S. :- I'd recommend using 'GPS status and Toolbox' app which is much better than GPStest.
Sent from my HTC Wildfire using Tapatalk 2
lakshan_456 said:
P.S. :- I'd recommend using 'GPS status and Toolbox' app which is much better than GPStest.
Click to expand...
Click to collapse
Done!
~400s for first GPS lock... yeesh...
Snakebar said:
Done!
~400s for first GPS lock... yeesh...
Click to expand...
Click to collapse
Mission accomplished.
Cheers
Sent from my HTC Wildfire using Tapatalk 2