08-12-2012 05:00 PM
276 12345 ...
tools
  1. Invincible Madness's Avatar
    Does this include thekraven's CM7.2, or does this mean ZVH-based roms only?
    I'm on Kraven's cm7 12/22 build and I have this CWM installed
    I guess that answers your question.
    01-14-2012 11:18 PM
  2. ikeywatson's Avatar
    is it posible to post the adb shell commands line for line ,that might help people try out the new recovery
    01-15-2012 12:59 AM
  3. drewwalton19216801's Avatar
    Does this include thekraven's CM7.2, or does this mean ZVH-based roms only?
    CM7 is Gingerbread, so what do you think?

    Baseband version makes no difference. As long as the ROM you flash uses the newer Edify scripting it will work. ROMs using the legacy Amend scripting (Android 2.2) will fail to flash and will cause an error message to be displayed.

    I realize that most of you have no idea what Edify and Amend are, but I'm not going to describe them here. Google is your friend if you are so inclined
    01-15-2012 03:06 AM
  4. droidmike_k's Avatar
    CM7 is Gingerbread, so what do you think?

    Baseband version makes no difference. As long as the ROM you flash uses the newer Edify scripting it will work. ROMs using the legacy Amend scripting (Android 2.2) will fail to flash and will cause an error message to be displayed.
    Thanks! The reason I was asking about ZVH is because that was the first (and only so far) baseband that came with Gingerbread and maybe that was the difference you were referring to... And yes, I have no idea what Edify scripting is

    It seems like it is finally time to upgrade from Reborn to CM7 - I didn't feel like flashing a new recovery and now with the new tool and this recovery there is no reason not to!

    Michal
    01-15-2012 09:00 AM
  5. eletendre84's Avatar
    I know Drew has disabled the battery stat wiping, and for good reason. However, for those of you that want to do it anyway:

    fire up terminal emulator
    Code:
    $su
    #rm /data/system/batterystats.bin
    #exit
    $exit
    that will wipe battery stats as well.
    01-17-2012 09:06 AM
  6. dobbs69's Avatar
    I have a noob question. Can we rename our nandroid backups what ever we want and not screw something up? Or do we have to keep it the date that recovery names it? I have a hard time remembering what rom is which backup.
    01-18-2012 07:08 PM
  7. jstntp's Avatar
    Yes you can rename them. Just make sure not to use any spaces.
    dobbs69 likes this.
    01-18-2012 07:55 PM
  8. dobbs69's Avatar
    Cool, thanks!

    Sent from my LS670 using Tapatalk
    01-18-2012 07:58 PM
  9. dobbs69's Avatar
    I have another question. I'm wanting to flash the kraven's cm7. Know I have to revert to zvd. Can I flash the update.zip twice like you can with xoinx cwma2.6--- or do I need to flash a stock recovery? I like the zvh roms, however I like using cm7 too, so I go back and forth. Thanks for your help and I really like this recovery. I don't know about any one eles but this recovery seems more responsive then xoinx---.

    Sent from my LS670 using Tapatalk
    01-19-2012 11:59 AM
  10. drewwalton19216801's Avatar
    I have another question. I'm wanting to flash the kraven's cm7. Know I have to revert to zvd. Can I flash the update.zip twice like you can with xoinx cwma2.6--- or do I need to flash a stock recovery? I like the zvh roms, however I like using cm7 too, so I go back and forth. Thanks for your help and I really like this recovery. I don't know about any one eles but this recovery seems more responsive then xoinx---.

    Sent from my LS670 using Tapatalk
    Never heard of Xoinx recovery, you sure you aren't running Xionia?

    You should be fine flashing the update.zip twice with CWM Recovery.
    dobbs69 likes this.
    01-19-2012 02:18 PM
  11. dobbs69's Avatar
    Thanks, sorry for the bad spelling.

    Sent from my LS670 using Tapatalk
    01-19-2012 04:36 PM
  12. hlxanthus's Avatar
    Do you have any plans to add functionality for us still slumming on the zvd baseband? While i use thekravens cm7, in theory i might want to flash back to a froyo rom for profile/prl updating. I do want to be on the better recovery (love the idea of not needing the debug file), but without backward compatibility i will have to wait for hydro rom to release, because as soon as that drops i am dying to try it!
    01-19-2012 06:14 PM
  13. hlxanthus's Avatar
    Thanks, sorry for the bad spelling.

    Sent from my LS670 using Tapatalk
    No sweat i am sure! We all knew what you meant, drew just couldnt help poking a little fun. :-)
    dobbs69 likes this.
    01-19-2012 06:16 PM
  14. illinoissparks18's Avatar
    Hey i tried flashing and it works but i then try again lets say 10 mins later and it gives me the stock recovery again. Need help getting it to stick.thanks
    01-19-2012 06:51 PM
  15. hlxanthus's Avatar
    Staying on stock rom can cause this with a fresh reboot. I don't know how to avoid it, maybe someone else has a suggestion.
    01-19-2012 07:33 PM
  16. dobbs69's Avatar
    Never heard of Xoinx recovery, you sure you aren't running Xionia?

    You should be fine flashing the update.zip twice with CWM Recovery.
    Well I tried to flash zvd update.zip 3 times with cwm recovery with no luck. This recovery tries to update radio, then throws several errors. When I reboot I've got zvd stock rom but no radio and still got cwm recovery. I flashed it twice, three different times. So I restored a zvh rom then flashed xionia recovery and flashed zvd update zip twice and everything worked great.
    01-19-2012 08:25 PM
  17. drewwalton19216801's Avatar
    Well I tried to flash zvd update.zip 3 times with cwm recovery with no luck. This recovery tries to update radio, then throws several errors. When I reboot I've got zvd stock rom but no radio and still got cwm recovery. I flashed it twice, three different times. So I restored a zvh rom then flashed xionia recovery and flashed zvd update zip twice and everything worked great.
    Thank for reporting this. You may not realise it but you almost bricked your phone. BUT you also confirmed that this recovery does not attempt to flash radios, which is good.

    When I get home from work I will update it to allow you to flash the update.zip with no issues.
    01-19-2012 10:44 PM
  18. dobbs69's Avatar
    Thank for reporting this. You may not realise it but you almost bricked your phone. BUT you also confirmed that this recovery does not attempt to flash radios, which is good.

    When I get home from work I will update it to allow you to flash the update.zip with no issues.
    I had a feeling when I was getting the errors and then stock rom / cwma recovery plus my phone was quriky that. I had better step back and punt! Thanks for looking into it!

    Sent from my LS670 using Tapatalk
    01-20-2012 03:19 PM
  19. babbyboy80's Avatar
    Will this (Recovery) work with Rom Manager?
    01-22-2012 06:38 AM
  20. epidenimus's Avatar
    Will this (Recovery) work with Rom Manager?
    For the love of God, do NOT use ROM Manager. Now go read the stickies and say 5 Hail Marys for asking. It was going to be 10, but you did ask before doing, which is commendable.
    aaronrw and Warlord721 like this.
    01-22-2012 08:31 AM
  21. drewwalton19216801's Avatar
    Will this (Recovery) work with Rom Manager?
    Every time someone uses ROM Manager a kitten dies. Save the kittens.
    01-22-2012 11:08 AM
  22. babbyboy80's Avatar
    Thought so was just checking didn't know if u guys made it compatible. Thanks

    Sent from my LS670 using Tapatalk
    01-23-2012 07:22 AM
  23. THEBROWNTANIUMMAN's Avatar
    Can anybody lead me to a place where they will explain this to me like Im 4?
    I got a LG Optimus S two days ago and basicly all i wanna do is over clock my CPU and tweak the OS a little, unfortunatley this is all a bit over mah head..
    01-23-2012 03:31 PM
  24. therenegadenail's Avatar
    so i was currently using the CMW recovery 5.0.2.7-th3 and it would seem that any backup made during that time just wouldnt work, and it also made my previous xionia backups behave oddly, but only the ones that where yourmom roms, once i installed xionia again, the old backups made with xionia loaded up no problem, but the new ones did not, which i assumed wouldnt because maybe theyre stored differently or what ever

    then when i was looking at the files that make up a nandroid backup, any of the new ones had an extra wording in the file names, yaff2 or something like system.yaff2.img or data.yaff2.img, and i dont know if that was the problem but they only showed up in the new backups made with cwm recovery, everything else is working with xionia

    then just to see i reinstalled cwm recovery and re attempted the events and again the new backups made with the new recovery would not boot at all

    any ideas?
    01-23-2012 03:43 PM
  25. drewwalton19216801's Avatar
    so i was currently using the CMW recovery 5.0.2.7-th3 and it would seem that any backup made during that time just wouldnt work, and it also made my previous xionia backups behave oddly, but only the ones that where yourmom roms, once i installed xionia again, the old backups made with xionia loaded up no problem, but the new ones did not, which i assumed wouldnt because maybe theyre stored differently or what ever

    then when i was looking at the files that make up a nandroid backup, any of the new ones had an extra wording in the file names, yaff2 or something like system.yaff2.img or data.yaff2.img, and i dont know if that was the problem but they only showed up in the new backups made with cwm recovery, everything else is working with xionia

    then just to see i reinstalled cwm recovery and re attempted the events and again the new backups made with the new recovery would not boot at all

    any ideas?
    All of my backups work just fine. Ones made in Xionia work just as well as ones made in CWM Recovery.

    About your CWM backups not working in Xionia, that's because Xionia is based off an ancient version of ClockworkMod and can't support the new backups.

    When something isn't booting, it's better to grab a logcat log (if possible) instead of simply stating "it didn't boot" or something to that effect. I can't replicate your issue, so without a log I can't do a thing about it.
    01-23-2012 03:48 PM
276 12345 ...
LINK TO POST COPIED TO CLIPBOARD