[RECOVERY] CWMT Recovery 5.0.2.7-th8.1 (Froyo-friendly!)

Status
Not open for further replies.
Re: [RECOVERY] CWMT Recovery 5.0.2.7-th7 (T is for TOUCH!)

[INFO]Special Announcement:
As many of you noticed from the first release of CWMT up until now, CWMT Recovery only supports Edify-based flashable ZIPs (aka Gingerbread). Support for Amend-based flashable ZIPs has been removed from ClockworkMod since version 3.0.0.4 thus Froyo ROMs are not flashable and throw an error message.

No more!

I'd like to announce that we are on the final legs of the journey to add support for Amend-based flashable ZIPs to CWMT 5.0.2.7!

Current Status:
Essentially Amend scripting is working, with a few bugs to be ironed out (two showstoppers).
1) SHOWSTOPPER Amend-based ZIPs fail on flashing boot.img (but the rest of the script works as intended) Fixed.
2) SHOWSTOPPER Recovery boot throws error message "E:failed to open /etc/fstab (No such file or directory)" This bug has been fixed 5 seconds prior to this writing.
3) COSMETIC The text output of Edify-based ZIPs doesn't display, however Edify-based ZIPs still flash correctly. And fixed.[/INFO]
 
Last edited:
Sweet drew, you rock! You are slowly but surely bringing all android goodness to this little engine that could. Outstanding!

Sent from my Nexus S 4G using Tapatalk 2
 
Re: [RECOVERY] CWMT Recovery 5.0.2.7-th7 (T is for TOUCH!)

[INFO]New update available:
CWMT Recovery 5.0.2.7-th8 is now available. Amend scripting has been enabled, and tar backups (and restores) have been disabled due to a major overhaul of the core Nandroid software.
[WARN]Warning:
Due to major core changes in the Nandroid software, any Nandroid backup made with CWMT Recovery 5.0.2.7-th7 will not be able to be restored with 5.0.2.7-th8. Please make a fresh backup immediately after flashing 5.0.2.7-th8. Xionia backups should be unaffected.[/WARN][/INFO]
 
Last edited:
Re: [RECOVERY] CWMT Recovery 5.0.2.7-th8 (Froyo-friendly!)

I like the battery indicator at the top of the recovery. Very nice touch!
 
Re: [RECOVERY] CWMT Recovery 5.0.2.7-th8 (Froyo-friendly!)

I wanted to report here that when I tried flashing thekraven's latest alpha in th8, it came up with an error. I didn't take too long to look at it, as i was kind of in a hurry, so i just flashed back to th6, and it installed the zip successfully.

I can probably recreate the error if you would like.
 
I wanted to report here that when I tried flashing thekraven's latest alpha in th8, it came up with an error. I didn't take too long to look at it, as i was kind of in a hurry, so i just flashed back to th6, and it installed the zip successfully.

I can probably recreate the error if you would like.

Recreate the error and then (while in recovery) post the contents of /tmp/recovery.log
 
Re: [RECOVERY] CWMT Recovery 5.0.2.7-th8 (Froyo-friendly!)

here you are sir. the .txt is in the .zip, as it wouldn't let me attach
 
Re: [RECOVERY] CWMT Recovery 5.0.2.7-th8 (Froyo-friendly!)

here you are sir. the .txt is in the .zip, as it wouldn't let me attach

Huh, that's interesting. It's not a bug in the recovery code.

There's a command in the updater-script called "getprop" which allows you to have your script make sure it's installing on the correct device.

In the case of thekraven's latest CM9 alpha, it's looking for "thunderc" but is really getting "thunderc_LS670". The build.prop that CWMT is getting comes straight from the IHO repository, so the REAL owner of this bug is blarf (the IHO maintainer).

Remove all "getprop" lines from thekraven's updater-script and the ROM will flash just fine.

I can fix this but what causes it is at the core of the IHO repository. You may also want to suggest to thekraven to remove all getprop lines from his updater-script since they are pretty much useless anyway.
 
Last edited:
  • Like
Reactions: prowlingfox
[INFO]New Build Available:
CWMT Recovery 5.0.2.7-th8.1 is now available. The build.prop has been changed to reflect the correct values of ro.product.device, ro.build.product and ro.product.board. All CM-based ROMs should be flashable now.

Want to help prevent this in the future? Ask the ROM developer of your favorite ROM to remove the assert command from the top of his/her updater-script, since it apparently breaks things sometimes.[/INFO]
 
Good work dude. Continuously pumping out the goodness!

Sent from my SPH-D710 using Android Central Forums
 
Hey drew I have a problem. I tried to flash the latest version using flash_image from term emulator and it gave me a whole bunch of read/write errors and at the end of each error it said this (out of memory). At the end of the command it said that my system is out of memory but I have around 19mb on my system partition and 90mb on my data partition. Any suggestions?

Sent from my LS670 using Android Central Forums
 
Hey drew I have a problem. I tried to flash the latest version using flash_image from term emulator and it gave me a whole bunch of read/write errors and at the end of each error it said this (out of memory). At the end of the command it said that my system is out of memory but I have around 19mb on my system partition and 90mb on my data partition. Any suggestions?

Sent from my LS670 using Android Central Forums

I can't reproduce that, you need to provide more info.

1) What ROM are you using?
2) What EXACTLY does flash_image spit out? (simply saying "errors" does not suffice)
 
Hey drew I have a problem. I tried to flash the latest version using flash_image from term emulator and it gave me a whole bunch of read/write errors and at the end of each error it said this (out of memory). At the end of the command it said that my system is out of memory but I have around 19mb on my system partition and 90mb on my data partition. Any suggestions?

Sent from my LS670 using Android Central Forums

EDIT: This was a bad idea.
 
Last edited:
Status
Not open for further replies.

Trending Posts

Forum statistics

Threads
957,398
Messages
6,972,767
Members
3,163,784
Latest member
KevinInKy