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 ?
while trying many cusOMS RomS ANd FLAshable ZiPS ,Came aCRoss TWo TERMS Flash BY cwm RecOVeRy or sTOck cwM Wats THE Difference betwen THE two Sorry FOR a A NOOB quESTion but WAS very Anxious to KNow tHE DiFereNCE......THANKS IN ADVANCE
custom roms are modified versions of your current stock rom to make it beautiful and faster.
flashable zips are of 2 types:
1. They are made for updating/adding something in your current rom.
2. Its a file format which lets you to install things using cwm. It can be a rom itself too!
hell_lock said:
custom roms are modified versions of your current stock rom to make it beautiful and faster.
flashable zips are of 2 types:
1. They are made for updating/adding something in your current rom.
2. Its a file format which lets you to install things using cwm. It can be a rom itself too!
Click to expand...
Click to collapse
i want to ask wat is difference if we flash a rom using cwm or using stock recovery
talwarrokzz said:
i want to ask wat is difference if we flash a rom using cwm or using stock recovery
Click to expand...
Click to collapse
cwm has more options than the stock one so using cwm is preferable
hell_lock said:
cwm has more options than the stock one so using cwm is preferable
Click to expand...
Click to collapse
your answers are good but still cant fullfill my requirements (sorry if rude)
wanted to ask why some roms only prefer cwm recovery not stock and why only cwm is used to replace boot image of our phone
hell_lock said:
cwm has more options than the stock one so using cwm is preferable
Click to expand...
Click to collapse
CWM has more options and very simple to understand and use!
STOCK=less option.... hard to use... some times its cause a boot loop!
talwarrokzz said:
your answers are good but still cant fullfill my requirements (sorry if rude)
wanted to ask why some roms only prefer cwm recovery not stock and why only cwm is used to replace boot image of our phone
Click to expand...
Click to collapse
u can flash a rom from stock recovery too but as I said above, it is recommended to use so that u can restore ur phone if something goes wrong. Wen i tried to flash boot.img frm stock recovery it gave an error but wen u flash it from cwm it is successful . Any more doubts or are you still unsatisfied? ASK MORE!
hell_lock said:
u can flash a rom from stock recovery too but as I said above, it is recommended to use so that u can restore ur phone if something goes wrong. Wen i tried to flash boot.img frm stock recovery it gave an error but wen u flash it from cwm it is successful . Any more doubts or are you still unsatisfied? ASK MORE!
Click to expand...
Click to collapse
are you mad?
PwN.CraZyTagZ said:
are you mad?
Click to expand...
Click to collapse
Yes I am!!
its depends on scripting... stock recovery runs only amend scripting but cwm 3.0 or later edify scrpiting... and it has so many options then stock... one notable option and frequently using option is dalvik cache wipe... this is y most of em prefer cwm...
I GUESS THIS IS THE ANSWER... BUT IM NOT SURE ABOUT... GOOGLE IT FOR MORE INFO... I READ IT SOMEWHERE ONCE UPON A TIME... SO I FORGET SOME OF THE THINGS...
stock recovery require your zip to be signed for security reason. cmw is not. signing itself is simple process that only need few second, but once you signing your zip you can't change it's content. you must resign your zip if you do. that's why some people prefer cmw, because you can easily change zip content with regular archive manager without resign.
irfanbagus said:
stock recovery require your zip to be signed for security reason. cmw is not. signing itself is simple process that only need few second, but once you signing your zip you can't change it's content. you must resign your zip if you do. that's why some people prefer cmw, because you can easily change zip content with regular archive manager without resign.
Click to expand...
Click to collapse
Yes friend u r right............
Sent from my GT-S6102 using xda premium
Let's get to your qeury . . . Flashing via stock or CWM
With CWM Recovery you can:
Flash boot.img (kernel)
Flash Custom ROMS
Flash .zips without resinging packages
Choose what partition to be mounted during flash
With stock:
Flash boot.img (kernel) -but most kernel are ment to be flashed via CWM as it has a higher chance of success and less likely to cause bootloops
Flash Custom ROMS - but some ROMS use scripts that are NOT SUPPORTED by stock recovery
Flash .zips but requires zips to be signed and resigned if there are modifications on the package
CarlDeanCatabay said:
...
With stock:
Flash boot.img (kernel) -but most kernel are ment to be flashed via CWM as it has a higher chance of success and less likely to cause bootloops
Flash Custom ROMS - but some ROMS use scripts that are NOT SUPPORTED by stock recovery
...
Click to expand...
Click to collapse
that's not stock recovery problem, but custom rom problem. a lot of custom rom have poorly written (or generated) updater-script. rom dev put a lot of work on making his/her rom looks good, but give very small attention to installation process. some rom event try to mount /dev/stl19 to /system in instalation process. that partition not exist in sgy. and updater-script not depend to which recovery that you use. it's depend to updater-binary inside your zip file.
So for some reason, I catch an error everytime I try to flash a rom to my phone. Then I am forced to restore my backup.
I have it rooted with CWM v5.5.0.4.
i747.
Not sure what other information you guys would need to assist. Would I need to re-root it? Different version of CWM?
Are you wiping data before you flash any new roms? That could be it..
Yep, always wipe data/factory.
.... i'm pretty sure that telling us what the error message says would help, too....
I'll take a wag and say since your recovery is 5.5.0.4 your probably getting a status 7 error which simply means you need to update your recovery to the newest version. Check in the dev section for the cwm recovery thread.
jethro650 said:
I'll take a wag and say since your recovery is 5.5.0.4 your probably getting a status 7 error which simply means you need to update your recovery to the newest version. Check in the dev section for the cwm recovery thread.
Click to expand...
Click to collapse
Agreed, almost undoubtedly...in every recovery flashable .zip there is an update-binary file which is the actual executable that is commanded by the update-script on what operations to perform. The newer versions of this binary are incompatible with older versions of the recoveries. This effect is not necessarily one way either, an older recovery trying to flash a new .zip or vice versa can produce this error but as a general rule using the newest recoveries should minimize this problem. The only time the reverse is a problem is when there is an update to the recovery api and there hasn't been an updated update-script built into a .zip. The easiest way to check is download the appropriate rom manager for your recovery, Clockwork Rom Manger for CWM or Goomanager for TWRP.
Hi, my issue is when I try to flash fauxkernel zips in philztouch recovery for i9505, the installation has a problem with a line "assertprop jfltetmo" (from what i remember, i dont have it in front of me), and aborts.
To fix this, I flashed Clockwerk Recovery and I was then able to flash the kernel.
My question is, would there any way to be able to flash the zip without switching recoveries? And if so, would that be a safe thing to do?
This thread is here because I'm unable to post to the actually fauxkernel thread (New user restriction)
yukinose said:
Hi, my issue is when I try to flash fauxkernel zips in philztouch recovery for i9505, the installation has a problem with a line "assertprop jfltetmo" (from what i remember, i dont have it in front of me), and aborts.
To fix this, I flashed Clockwerk Recovery and I was then able to flash the kernel.
My question is, would there any way to be able to flash the zip without switching recoveries? And if so, would that be a safe thing to do?
This thread is here because I'm unable to post to the actually fauxkernel thread (New user restriction)
Click to expand...
Click to collapse
Sound like its checking for an .md5 or doing an active scan on the phone to see if its compatible with that kernel. If you can disable it in the options somewhere it should work fine.
Now we have official TWRP support, so this thread will not be updated anymore. For more info about official TWRP visit this thread.
Tired waiting for someone to repack kernel with your favorite version of recovery? Or tired to run recovery script every time you update your ROM or kernel? Now you don't need any repacked kernels or recovery-scripts. Use your FOTAKernel as recovery partition!
It works on any kernel with extract_elf_ramdisk utility (it's built in mostly all kernels for custom ROMs, but I am not sure) by @Dees_Troy. And don't forget, that you are doing on your own risk, I am not responsible for bricked devices, acid rains or thermonuclear war.
Installation:
Download zip and flash it via your current recovery. If your current recovery is unusable, you can flash it via terminal emulator:
- Extract FOTAKernel.img and place it to the root of your external SD-card
- Type su and grant root access
- Type
Code:
dd if=/ext_card/FOTAKernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
- Reboot to recovery to test if it works (if not, try again and check if you are doing it correctly).
Download:
TWRP 2.8.7.0
TWRP 2.8.6.0 (this and next versions are compiled for Xperia M by me)
Older versions and CWM:
TWRP 2.8.5.0 (port from Xperia L)
TWRP 2.8.4.0 (thanks to @Rohan purohit for bringimg it for Xperia L, I just ported and modded it)
TWRP 2.8.0.0/CWM (or scroll down, it's right below this post)
You can restore original FOTAKernel image by following instructions in this post (or just scroll down, it is 3rd post, lol).
Some info:
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader this partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by recognized developer @Dees_Troy (lead TWRP developer), he developed utility extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery! Here is some info from Dees_Troy.
Download
TWRP 2.8.6.0>>>
TWRP 2.8.5.0>>>
TWRP 2.8.4.0>>>
Restoring original image
- You can restore original FOTAKernel flashing it via Flashtool by flashing any firmware (just uncheck everything in "wipe" section and uncheck everything in "exclude" section excluding "FOTA" like in attached screenshot).
- Or install attached zip via recovery or flash FOTAKernel.img from archive as it is written in OP.
cucumber09 said:
TWRP version is 2.8.0.0, because I could not boot 2.8.3.0 this way (maybe due to ramdisk size limitations), I'll look for this later and will try to fix it
Click to expand...
Click to collapse
Excuse me sir,
is this recovery work with cm11 which I have now??
Can I flash it now,
so when I decided to flashing cm12 being ready[emoji4]
I hope I explained my idea
kh34d said:
Excuse me sir,
is this recovery work with cm11 which I have now??
Can I flash it now,
so when I decided to flashing cm12 being ready[emoji4]
I hope I explained my idea
Click to expand...
Click to collapse
I don't know for sure. Download both recoveries, try to flash one that differs from yours and reboot recovery. If it changes, that means it works on CM11 kernel. BTW, even if it doesn't work on CM11, it will work when you will flash CM12 kernel. So you can flash it to be prepared.
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
itsnie said:
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
Click to expand...
Click to collapse
Okay, I will upload original FOTAKernel.
itsnie said:
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
Click to expand...
Click to collapse
Everything about restoring is in 3rd post.
cucumber09 said:
Everything about restoring is in 3rd post.
Click to expand...
Click to collapse
Thangs, now all problem will be fixed ..
@cucumber09 Will it work for stock 4.3, i know you mentioned for custom rom but just curious about it, what do u think?
KHM90 said:
@cucumber09 Will it work for stock 4.3, i know you mentioned for custom rom but just curious about it, what do u think?
Click to expand...
Click to collapse
No, it needs custom kernel, that includes extract_elf_ramdisk, stock kernel doesn't. BTW, there are CWM-included kernels for all stock ROMs. And TWRP is not available for stock. I can try repacking stock kernel with TWRP, but I doubt it will work.
cucumber09 said:
No, it needs custom kernel, that includes extract_elf_ramdisk, stock kernel doesn't. BTW, there are CWM-included kernels for all stock ROMs. And TWRP is not available for stock. I can try repacking stock kernel with TWRP, but I doubt it will work.
Click to expand...
Click to collapse
Ok thx, Not needed just wanna know whether it will work or not
btw, FOTA kernel awesome idea:good:
I try to repack my custom kernel with justarchi twrp version. I can Confirm it doesn't boot to fota recovery. Main boot.img is cm12 first nightly. It always boot to CyanogenMod recovery. Still search for solution...
ndrancs said:
I try to repack my custom kernel with justarchi twrp version. I can Confirm it doesn't boot to fota recovery. Main boot.img is cm12 first nightly. It always boot to CyanogenMod recovery. Still search for solution...
Click to expand...
Click to collapse
I read sources of extract_elf_ramdisk utility. And found there something about uncompressed ramdisk size, there is limitation to 8 Mb by default. So, I think, we should reduce ramdisk size by removing unnecessary or redundant files and binaries (must be done very carefully) or to commit change in our kernel.
I'm confused, does it work for locked bootloader?
pincheraro said:
I'm confused, does it work for locked bootloader?
Click to expand...
Click to collapse
No way. It even won't work on stock kernel with unlocked BL.
@cucumber09 Which build is the attached FOTA restore zip from? .9?
elmkzgirxp said:
@cucumber09 Which build is the attached FOTA restore zip from? .9?
Click to expand...
Click to collapse
No, it is from earlier build, but also from 4.3. From first 4.3 build, as I remember.
cucumber09 said:
I read sources of extract_elf_ramdisk utility. And found there something about uncompressed ramdisk size, there is limitation to 8 Mb by default. So, I think, we should reduce ramdisk size by removing unnecessary or redundant files and binaries (must be done very carefully) or to commit change in our kernel.
Click to expand...
Click to collapse
You mean this source code: Dees-Troy
I inspect the twrp, but no found the file that save to be removed. Btw, what commit needed to apply to kernel?
ndrancs said:
You mean this source code: Dees-Troy
I inspect the twrp, but no found the file that save to be removed. Btw, what commit needed to apply to kernel?
Click to expand...
Click to collapse
I read these sources. And 49th line defines size of uncompressed ramdisk. But now I am not sure, which one is used in our kernel. I suppose, that newer one.