Related
Hi... I just found that Clockwork Recovery has new version from their website but in zip format. Try to install it through ROM Manager and recovery mode but it is just temporary recovery. Every time I enter recovery mode by pressing power and vol down and choose recovery it is back to old recovery.
Does anyone try this new recovery and how to make it permanent or is it available in img format so I can flash it using Android Flasher.
for your reference please find it here :
hxxp://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.zip (please change hxxp into http)
*** sorry for my horrible English and grammar
it is cause you use the fake-flash method, launching CWM 5.0.0 by flashing a .zip file from your current recovery.
in order to permanently change your recovery you would have to be S-OFF and have a .img file of the new recovery
My HTC Desire already S-OFF but where to find this img file of new CWM Recovery?
I have search over Google and this forum but did not found. Is it possible to change this zip file into img file?
The file:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img
Md5Sum:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img.md5sum.txt
davebugyi said:
The file:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img
Md5Sum:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img.md5sum.txt
Click to expand...
Click to collapse
Thank you very much... how can I missed that
davebugyi said:
The file:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img
Md5Sum:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.0.0-bravo.img.md5sum.txt
Click to expand...
Click to collapse
You are smart
CWM website folder can browse
got it
http://download.clockworkmod.com/recoveries/
recovery-clockwork-5.0.0.0-bravo.img 30-Aug-2011 23:25 3106816
recovery-clockwork-5.0.0.0-bravo.img.md5sum.txt 30-Aug-2011 23:25 92
Easier just to look here:
http://www.clockworkmod.com/recovery_images.html
EddyOS said:
Easier just to look here:
http://www.clockworkmod.com/recovery_images.html
Click to expand...
Click to collapse
Yes but not all file available.
like HTC Bravo only latest recovery in zip format only.
Thanks
Yeah, but as this thread is for v5.0.0.0 then people will want the newest will they not?
someone already did some test?
for example backup the current rom (maybe one with ext partition), then flash an other rom (just for test), and then restore the backup (and see if boots and everything ok)?
i will try later anyway, but of course will be nice to already know if its work or have some problems
Has any one had the edify script error with CWM 5.0.0.0 recovery ?
I flashed CWM 5.0.0.0 today via fastboot and it works fine - however I tried flashing Cool 3D V9 Rom and then when i flashed the boot loop fix & got the edify scripting error does any one know of a work around ??? I did a search and i found some code by coolexe and baadnews but not sure if there is a way to fix this ?
-Dan
danw1million said:
Has any one had the edify script error with CWM 5.0.0.0 recovery ?
I flashed CWM 5.0.0.0 today via fastboot and it works fine - however I tried flashing Cool 3D V9 Rom and then when i flashed the boot loop fix & got the edify scripting error does any one know of a work around ??? I did a search and i found some code by coolexe and baadnews but not sure if there is a way to fix this ?
-Dan
Click to expand...
Click to collapse
ask the dev to update the script in the flashable zip or flash a 2.x recovery (amend script is no more supported from 3.x and up, only edify is supported)
anyone have a changelog? cant find one anywhere!
andQlimax said:
ask the dev to update the script in the flashable zip or flash a 2.x recovery (edify script is no more supported from 3.x and up)
Click to expand...
Click to collapse
Thanks for the advice will do.
sjknight413 said:
anyone have a changelog? cant find one anywhere!
Click to expand...
Click to collapse
follow koush or clockworkmod on twitter..5.x has faster backups (now it used .tar files) and preserve the file system of each partition (if ur sd-ext is ext3, it will be backup and restore as ext3, if u have ext4 it will be ext4, etc..with previous cwm recoveries the sdext was restored always as ext3)
also a new color sheme..now is blue light
edit: new recovery seems available 5.0.1.0 http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.1.0-bravo.img
I read from a koush twit :
"Desire and Desire CDMA users: I have just switched you to real flashing rather than fakeflash. You will need to S-OFF. with unrevoked."
so, out of curiosity, how Rom Manager can flash the recovery for real?
I always use fastboot, and i though there was no other way than that and the PB99IMG.zip method..
Someone know how that works (i mean the flashing through an app)?
i'm fine with 4.xxxx
andQlimax said:
I read from a koush twit :
"Desire and Desire CDMA users: I have just switched you to real flashing rather than fakeflash. You will need to S-OFF. with unrevoked."
so, out of curiosity, how Rom Manager can flash the recovery for real?
I always use fastboot, and i though there was no other way than that and the PB99IMG.zip method..
Someone know how that works (i mean the flashing through an app)?
Click to expand...
Click to collapse
Well there have always been another way just not on desire, since s-on users couldn't write to system or recovery while system was booted. But with s-off using a flash_image script will work just fine, which is pretty much what rom manager does(i assume).
So I asked koush on twitter to change us to native recovery flashing since s-off have been around for quite some time for desire
edit: so for everyone s-off that means: to update just install/open rommanager and press "flash clockworkmod recovery"(tested and working just fine)
mortenmhp said:
Well there have always been another way just not on desire, since s-on users couldn't write to system or recovery while system was booted. But with s-off using a flash_image script will work just fine, which is pretty much what rom manager does(i assume).
So I asked koush on twitter to change us to native recovery flashing since s-off have been around for quite some time for desire
edit: so for everyone s-off that means: to update just install/open rommanager and press "flash clockworkmod recovery"(tested and working just fine)
Click to expand...
Click to collapse
Thanks to ur tips, i found how it works!
from the terminat emulator on the phone:
Code:
flash_image recovery /sdcard/recovery.img
that should flash the recovery (even other partition i though), without use fastboot and without use the pc! thats nice!
On AOSP roms the flash_image utility is already included on /system/bin..in other roms (like stock ones) it should be downloaded and placed on the phone and used in the same way
that probably what rom manager does
So there is no way to get the latest version of ClockworkMod Recovery if we are on S-ON ?
I feel like one of my daily job is flashing new ROMs these days.....
Any way, we are getting lots of ROMS that we can flash with different methods.
Because I'm flashing the ROMs almost every day in these days, I just wanted to share some information how I do my daily job. (Lot's of Devs are flashing the Roms with their own ways but I believe the general concept is same and we are always trying to avoid the 'bricks' caused by wrong direction.
In here, what I'm doing is my safest way and I never failed with this method but please do this with your own risk if you want to follow this guide. There are tons of other guide and directions that you may also want to consider.
[Most important thing is, you must follow ROM publisher's instruction first. The information in here is the way what I'm doing day to day basis. So, it may not work based on your situation. Don't blame be if you phone bricked]
* Flashing Calk rooted Stock Rom
1. if you don't have the Modified CWMRecovery kernel something like Rogue Recovery Kernel, before following this guide, you need to download 'it' first.
For me, I use Rogue's FB27 recovery Kernel until another newest stable version comes out. You can download it from
http://forum.xda-developers.com/showthread.php?t=1390393
If you use the .tar file, then I assume that you already have a odin executable in your pc (.tar file in you pc) or mobile odin in your phone (.tar file in your sdcard).
Or if you use the zip file, you need to be sure that you are able to install the zip file through the recovery (zip file in your sdcard).
2. download Calk's rooted stock Rom and place into your sdcard (or external SD).
Most recent Calk's rooted stock Rom can be found at
http://forum.xda-developers.com/showthread.php?t=1552117
Modem file also needs to be required if you want to install the modem at the same time when you flash his rom. If the modem tar file available from other Dev's post, you can flash the modem later or before the flashing his rom thru odin or mobile odin.
3. Be sure that you already have nandroid backup of your current rom or make the nandroid backup before flashing his rom.
4. Check if there's any stock kernel available. If there's no separate kernel available, you need to extract zImage file from Calk's zip file and save to sdcard (for mobile odin) or to PC (for odin). If you want to keep the current Recovery Kernel, you don't need this step.
5. Now I assume that you have all the files ready and placed those to the right places. If your current kernel is not Rogue's, then install his recovery kernel. For me, I use mobile odin and pick it up from sdcard.
After installation, phone automatically reboot. Before the first screen comes out, press vol up + power keys at the same time. It will bring you to the Rogue CWM recovery screen.
6. From recovery screen, select install from zip and point the Calk's zip file you saved. Select and install it.
7. If you want to install the modem at the same time, do the same thing as step 6 but choose the modem zip file. There's no special sequence between step 6 & 7. Anything can be installed first. If you don't have modem zip file but have modem tar file, modem can be installed later. Or you can install the modem first before starting all these steps.
8. reboot
9. The kernel went back to stock kernel. So, if you need to do some recovery task, you need to start from step 5. One example is, if you want to run Calk's Bare Rom converter tool but you missed doing it after installing the ROM, then you need to install the Rogue recovery Kernel again. Usually Rogue Kernel is behind of current Kernel. But don't worry about coming back after the recovery task. This is the reason why I added step 4 above.
Additional steps coming back to current Kernel after the Recovery Task -
1. Install Rogue Recovry Kernel (usually previous kernel version)
2. Reboot and do the recovery task (backup, running Bare Rom converter zip file, cleaning data/dalvik cache, format battery stat, etc).
3. Reboot
4. if you use mobile odin, then install the zImage file or any kernel that you want.
If you use odin, go to the download mode by pressing vol down + power button together and install the kernel.
- if the kernel zip file is also available, then you can skip the steps 3 and 4. Just after the step 2, install the kernel zip file and reboot.
* Flashing ODIN/TAR rooted stock Rom
The basic idea is same to flashing Calk's ROM.
The most recent Stock rooted odin/tar file can be found in http://forum.xda-developers.com/showthread.php?t=1551901
1. if you don't have the Modified CWMRecovery kernel something like Rogue Recovery Kernel, before following this guide, you need to download 'it' first.
For me, I use Rogue's FB27 recovery Kernel until another newest stable version comes out. You can download it from
http://forum.xda-developers.com/showthread.php?t=1390393
If you use the .tar file, then I assume that you already have a odin executable in your pc (.tar file in you pc) or mobile odin in your phone (.tar file in your sdcard).
Or if you use the zip file, you need to be sure that you are able to install the zip file through the recovery (zip file in your sdcard).
2. download odin/tar file. For me, I use sfhub's one-click self-extractor package.
To install this ROM into your phone, please read his instruction carefully. In his package, you can install everything with just one odin or you can install modem/kernel/rom separately. Also, there are two packages available, one is for whom don't want the old data, and another one is for whom want to keep the old data.
3. after the odin finished, phone restarts automatically. Now you have the new ROM installed on your phone but there's no modified recovery Kernel. To do the recovery task, you need to follow the steps in 'Additional steps coming back to current Kernel after the Recovery Task'.
Important - if you don't know what you are doing, please be sure that you know what you are doing before doing anything by asking your questions to someone! There would be someone who can help you about your questions but there's no one who is responsible for your bricked phone!
sup guys!
I would like to have the JB update from ARHD 16 but im totally lost in the proces of how to do it.
i succesfully unlocked the bootloader
Installed Custom recovery and did a nandroid backup
also my phone is rooted
-Downloaded the custom rom
-Downloaded the flash boot IMG
soo what is the exact thing i need to do know? i know i need to update Hboot.. but when and how. also i want a custom kernel for max battery life.. IM CONFUSED!?!
with my motorola defy it was so easy..
First you need to update your HBOOT.
Easiest way is using >> THIS tools thanks to Stuart001.
After you succesfully done that you can flash the rom, a rom flash instruction is described in rom thread where you download the rom.zip.
Normal steps go like this:
upload downloaded rom.zip to storage on your device
flash boot.img
clear cache
install rom.zip using recovery option
Aroma installer (in rom.zip) has an option to wipe your device, I suggest you do that during rom install as well.
Of course this will erase all data, I'm just trying to help and don't take any responsibility.
if you have a supporting cid. Then only you can install jb sense roms.
ah nevermind. already found out how by chrashing my phone haha. i already solved it and now running custom rom!
ok im truely frustrated after trying to figure this out in past 2 days and reading more than 60 threads/websites.
Problem:
my one x was running 4.0.4 rooted +supre user+CWM, till i got the notification for 4.1 update. i pressed install now and downloaded around 380 MB, during the update phase a red exclamation icon appeared and phone rebooted into 4.0.4.
relocked bootloader, flashed stock recovery and downloaded it again and this time copied the OTA file before pressing install. so i installed and same issue.
uninstalled Avast AV (android) and ran through the same process again, same thing, started up into 4.0.4 again.
unlocked the bootloader, flashed CWM 5.8.4, copied ota file into phone and renamed it to update.zip. ran it from recovery menu and got status 7 error.
downloaded and ran JBFWTOOL21 and followed the instructions, during one of the steps i encountered an error and after restarting the phone i was stock at "HTC One x" with "beatsound" logo at bottom.
NOW NOTHING WORKS
what ive tried so far:
relocked loader and flashed stock recovery and tried Factory Reset, no luck.
unlocked loader and flash CWM and tried wiping cache and wiping disk. nothing.
relocked loader,flashed recovery and ran stock RUU "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed" but it doesnt work, give an error related to version numbers or something.
extracted system.img, boot.img from RUU temp folder ROM.zip and tried to flash but cant flash system.img (918mb). something about not enough HEAP i think.
from the OTA JB zip extracted recovery.img, boot.img and recovery.img and flashed them. nothing.
downloaded "One_X_All-In-One_Kit_v2.1" and tried kernel flash, nothing.
clearing cache via fastboot command also doesnt work
really appreciate any helpful input guys, im really frustrated. thanks
Oh my.. First, stop unlock and relock of bootloader. Do you have a cwm backup from before all this started? Flashing cwm and restoring that backup will get you far.
The first ota attempt failed due to cwm, always return to stock recovery (recovery.img from your cwm backup image) before applying ota update!
Kind Regards
TwinAdk
unfortunately, no. no backup.
since it all started from the official update i didnt make any backups.
Stop trying flash randomly. Run the following command:
fastboot getvar version-main
it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4
woomera said:
it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4
Click to expand...
Click to collapse
Well that's why the older RUU wouldn't work. You have the latest.
You'll need to go to the ROM backups thread and see if you can get a backup and flash its boot.img and restore it from CWM.
Actually, reboot your PC and try to flash system.img and boot.img again. You will probably need to be locked.
but isnt that the boot.img from "OTA_ENDEAVOR_U_JB_45_S_HTC_ARA_3.16.415.4-2.17.415.2_release_304331jrfus698taf4vm1x"?
cause i have already tried it, didnt work. i have the OTA file.
Modified my post. Look up.
i have boot.img from firmware with hboot 3.16 and 3.19, which one to use?
and the system.img is from stock RUU which is "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed", will that work?
the OTA JB is a zip file and doesnt have system.img.
Err.. 1.39?
yes
the firmware included in "JBFWTOOL21" is 1.36 which is used by many to manually upgrade to JB but the firmware inside the OTA file itself is 3.19 which is also the version i updated to since i thought its the reason the update doesnt work.
the Hboot version on my phone is 1.39 at the moment.
Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.
BenPope said:
Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.
Click to expand...
Click to collapse
i dont understand, a backup of what? the system.img?
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
I thought about suggesting that too, but I'm new to flashing so I didn't feel confident enough to do it..
But off the top of my head, a custom rom, complete with boot.img and everything should work..
I'm using http://forum.xda-developers.com/showthread.php?t=2013506, it's super great and support all hboot versions.
No guarantees it will work though.
Kind Regards
TwinAdk
sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
guess it worth a try even though i'd rather fix the problem in hand in another fashion.
gonna give it a try and post the results.
k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM
woomera said:
i dont understand, a backup of what? the system.img?
Click to expand...
Click to collapse
A nandroid backup, like what Clockworkmod recovery makes.
woomera said:
k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM
Click to expand...
Click to collapse
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
NOTE: These instructions require that you have one of the ICS hboot versions in order to work (1.12.0000 or lower). If you have one of the new JB hboots 1.28, 1.31 or 1.33 there is currently no way to return to stock until a JB ruu is released for your device.
Click to expand...
Click to collapse
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk
BenPope said:
A nandroid backup, like what Clockworkmod recovery makes.
Click to expand...
Click to collapse
thanks for the clarification
TwinAdk said:
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk
Click to expand...
Click to collapse
i have read the same thing, also "BenPope" mentioned it. so with this version of Hboot (1.39) i cant restore unless its a nandroid backup.
but i dont wanna go back to stock ICS! i wanna finish what i was trying to do in first place, Upgrade to JB.
but no matter what i do i get the "status 7 error". i have tried it with the OTA my phone downloaded and also downloaded it again directly from HTC website via a link from one of the threads in forum.
so status 7 apparently is related to CRC error but how can that be? and what is my option right now to do the upgrade? also bear in mind that before all these happened the normal upgrade process via the "system update" also failed with a red icon error.
Tried to change to the desire-z hboot to add extra space when running kitkat 4.4.2. Used the PC10IMG.zip file in developer forum.
It replaced the hboot and the radio, plus the recovery.img. The recovery.img was from 3.0.2.4. Before running the PC10IMG.zip I was using
the latest Clockwork Recovery file. Needles to say the phone won't boot. I need to make a PC10IMG.file that will replace the files
that were in the in the original files on the phone. Needless to say I can't us ADB because that fastboot is not working. I tried update files
form earlier versions(PC10IMG.Zip), they didn't work because hboot was different and I got a version error. Got any suggestions where I can
some later .img files to restore the bad ones.
Thanks,
Clyde
boot into recovery and write down everything from that screen here
Restore prceedure
Clyde909 said:
Tried to change to the desire-z hboot to add extra space when running kitkat 4.4.2. Used the PC10IMG.zip file in developer forum.
It replaced the hboot and the radio, plus the recovery.img. The recovery.img was from 3.0.2.4. Before running the PC10IMG.zip I was using
the latest Clockwork Recovery file. Needles to say the phone won't boot. I need to make a PC10IMG.file that will replace the files
that were in the in the original files on the phone. Needless to say I can't us ADB because that fastboot is not working. I tried update files
form earlier versions(PC10IMG.Zip), they didn't work because hboot was different and I got a version error. Got any suggestions where I can
some later .img files to restore the bad ones.
Thanks,
Clyde
Click to expand...
Click to collapse
Found a file cwmr_6045_vision.PC10IMG.zip (used Google). Deleted every char before PC in file name and wrote file to SDrom then rebooted
and was able to get into recovery and recovered from there.
This might be a plan for those who can't get anything to work.
Thanks,
Clyde
I meant to say write all info from bootloader not recovery, but anyway glad its working
(Future reference be careful flashing random PC10IMG.zips, they can lead to a quick a brick)
Sent from my Nexus 7 using XDA Premium 4 mobile app