Guest solidchips Posted March 24, 2011 Report Share Posted March 24, 2011 Tried recovery manager 0.34b and got the output "The application recovery manager (process com.podtwo.recoverymanager) has stopped unexpectedly. Please try agian." Link to comment Share on other sites More sharing options...
Guest solidchips Posted March 24, 2011 Report Share Posted March 24, 2011 Wow... I don't know what happened. Previously when i tried a temporariness root using Z4root it stuck. But this time i successfully rooted my phone "temporarily" using Z4root. Link to comment Share on other sites More sharing options...
Guest Phil001 Posted March 28, 2011 Report Share Posted March 28, 2011 Hi, Sorry for my ignorance, been away from this for a while... Is this similar/the same as 'ROM manager', if not what are the differences? Many Thanks Link to comment Share on other sites More sharing options...
Guest hecatae Posted March 28, 2011 Report Share Posted March 28, 2011 Hi, Sorry for my ignorance, been away from this for a while... Is this similar/the same as 'ROM manager', if not what are the differences? Many Thanks similar to ROM Manager, but Blade only Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted March 29, 2011 Report Share Posted March 29, 2011 similar to ROM Manager, but Blade only It works on more than just the Blade, I know its been tested on the v9, Joe & Racer.... (and worked fine) Link to comment Share on other sites More sharing options...
Guest Phil001 Posted March 30, 2011 Report Share Posted March 30, 2011 It works on more than just the Blade, I know its been tested on the v9, Joe & Racer.... (and worked fine) thanks for that. It doesn't recognise my firmware/rom (FLB r10) (i have done a database update too) Does it only recognise certain roms? Many thanks though, looks like a good alternative to booting into recovery to install roms etc. Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted April 5, 2011 Report Share Posted April 5, 2011 It doesn't recognise my firmware/rom (FLB r10) (i have done a database update too) I've not really kept the firmware database upto date, but ultimately it's not too much of an issue as it does nothing with that other than shows you what it is... I've kind of removed a bit of the code, if it can recognize your firmware it will tell you, and if there is a 'known' update.. but its more about the recovery images really.. Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted April 5, 2011 Report Share Posted April 5, 2011 Also, A slight bump in version to 0.36 today.. nothing really amazing, just adding in extra debug info... expect more developments on the app soon.... depending on my 'real life commitments' Link to comment Share on other sites More sharing options...
Guest mrflibbles Posted April 6, 2011 Report Share Posted April 6, 2011 (edited) The latest 0.36b (with updated database) still doesn't recognise the recovery image for clockwork mod 3.0.1.4 for GEN1 phones. Does it still install if it is unrecognised? [Edit : It would appear so. Cool] Edited April 6, 2011 by mrflibbles Link to comment Share on other sites More sharing options...
Guest JayGB1982 Posted April 15, 2011 Report Share Posted April 15, 2011 Does this work on GEN2 phone's I have converted to GEN2 but cant use this it just Force Closes all the time. Can't use clockwork, How do you get a recovery working on GEN2 Link to comment Share on other sites More sharing options...
Guest hecatae Posted April 15, 2011 Report Share Posted April 15, 2011 Does this work on GEN2 phone's I have converted to GEN2 but cant use this it just Force Closes all the time. Can't use clockwork, How do you get a recovery working on GEN2 yes it works on gen2 phones, used it to remove the stock softbank 003z rom last night Link to comment Share on other sites More sharing options...
Guest Northern-Loop Posted April 16, 2011 Report Share Posted April 16, 2011 I've upgraded to GEN2 and when I open RA I just get a forced closed error message. Device is working file but can't flash my recovery image.. eek Link to comment Share on other sites More sharing options...
Guest Northern-Loop Posted April 16, 2011 Report Share Posted April 16, 2011 I've upgraded to GEN2 and when I open RA I just get a forced closed error message. Device is working file but can't flash my recovery image.. eek Ah noted it might not work with some versions of CM7 and I'm running GEN2 (upgraded) CM7 04092011 nightly. So at the moment I have no Recovery image. Can I install Clockworkmode via this ADB? I'm not sure how too? Link to comment Share on other sites More sharing options...
Guest Northern-Loop Posted April 16, 2011 Report Share Posted April 16, 2011 Ah noted it might not work with some versions of CM7 and I'm running GEN2 (upgraded) CM7 04092011 nightly. So at the moment I have no Recovery image. Can I install Clockworkmode via this ADB? I'm not sure how too? Found all my answers here http://android.modaco.com/content/zte-blad...en2-conversion/ Everything was working before I opened ROM manager which I guess flashed it to a GEN1 recovery. There was probably a post about it but I missed it. Link to comment Share on other sites More sharing options...
Guest willp93 Posted April 19, 2011 Report Share Posted April 19, 2011 hi can someone tell me where i can download 0.34b from thanks Link to comment Share on other sites More sharing options...
Guest diordnaBLADE Posted April 25, 2011 Report Share Posted April 25, 2011 My recovery manager is not working for me now. I installed it without any problems and was able to run it once, unfortunately it did not see the existing recovery and could not see the installed one either. I restarted the phone and when I try to run it (also after a reinstall) it crashes. Is this a show stopper for me now? Thx Link to comment Share on other sites More sharing options...
Guest dylan_r Posted May 4, 2011 Report Share Posted May 4, 2011 Been trying to root my ZTE v9 for ages (optus tab version) I'm on Froyo 2.2 and nothing seems to work so, i can't use this :S any mind helping me? Link to comment Share on other sites More sharing options...
Guest stevejab Posted May 5, 2011 Report Share Posted May 5, 2011 Hi Sebastian, I'm having some problems (Currently installed Recovery: Unrecognised) . I am using v0.36beta and installing recovery-clockwork-3.0.2.8-blade-gen1 When I use the "Reboot into Recovery" option from RM, clockwork seems to start just fine, so I thought the unrecognised message was benign. However, when I try to backup the existing firmware I get the error message:- "You need to install a custom recovery before you can back up your Firmware!" Similar error if I attempt to Install Firmware. The output of debug is:- version: v0.36beta device: blade ram_console: 02900000 recovery_partition: mtd0: 00480000 00020000 "recovery" recovery md5: d818bb3bd1bd8dbb878b3f7bdba6a7aa firmware md5: 2670a2f174fdc4ed55faffed918d57c0 I have a rooted standard ROM UK Orange San Francisco (Blade) with GEN1/oled Thanks, -Steve Link to comment Share on other sites More sharing options...
Guest destroyerGT540 Posted May 9, 2011 Report Share Posted May 9, 2011 (edited) Working on a stock My Tab upgrade to 2.2. At first it fc when I clicked 'Install Recovery', then I installed Rom Manager and did a fix permissions, reboot. Copied the gen 2 img version to sdcard and it worked! Thank you! Edited May 9, 2011 by destroyerGT540 Link to comment Share on other sites More sharing options...
Guest Panzerfaust101 Posted May 27, 2011 Report Share Posted May 27, 2011 When will you be able to fix this so that it would work would CM 7? Would be much appreciatedif you could get it done soon - I really need it >.<. Thanks Link to comment Share on other sites More sharing options...
Guest way708 Posted May 31, 2011 Report Share Posted May 31, 2011 Hi... friend iam new this site.....but iam trying upgrade my moble is Dell xcd28... when i installed recovery manager then open it's showing error like the application recovery manager (process com.podtwo.recoverymanager) has stopped unexpetedly.please try again. please help me ......... :D Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted June 2, 2011 Report Share Posted June 2, 2011 When will you be able to fix this so that it would work would CM 7? Would be much appreciatedif you could get it done soon - I really need it >.<. Thanks The problem is when the application is installed to the /data/app/ area, if you where to install it on the /system/app/ area it will work fine. there was a report in the CM bug tracker, its a common problem that affects lots of other apps. Link to comment Share on other sites More sharing options...
Guest asuferoth Posted June 9, 2011 Report Share Posted June 9, 2011 (edited) Hello, im having problems with recovery menager and clockwerk compatibility. Always says its not. but... ive looked in Sebastian's FTP directory and checked MD5 for all versions of Recovery Menager, heres what i found: Link to FTP: http://android.podtwo.com/recoverymanager/ [ ] RecoveryManager_v0.23b.zip 143k a068e46ce1b7573caa518060ee95e5c4 - 05ff1316f2a53a67f04a020c9776850a [ ] RecoveryManager_v0.26b.zip 145k 8d88b79410fdd67a3aa77661b1234a3e - 306ce12890b7bca7bc3b2970e5a434d [ ] RecoveryManager_v0.29b.zip 146k f8019d82eabaa8ef5fbf2498c13f5a12 - bcfe118d13d8a1d5cf5e28e92c339d0d [ ] RecoveryManager_v0.32b.zip 150k d23d123870cc2bac2e3a9065e18b33b7 - xxxxx [ ] RecoveryManager_v0.34b.zip 154k 6d5987ddd4640920e54af2b3cf0be17a - xxxx [ ] RecoveryManager_v0.35b.zip 154k 377c655270b25f41875cd2342099506e - xxxx [ ] RecoveryManager_v0.36b.zip 156k 89f5555e26155114347e95c121131f03 - xxxx Rest "xxx" aldso are different including leatest version. Im wondering may be a cause of compability error displays? Ive tryed to download each file moreless 10 times using different browsers (ie, fox, opera, chrome). And im usind MD5 check utility to see what Md's are. Each guide says it should be same, but it isnt. BTW: clockwerk's MD5 are correct as i checked... Does anyone have any clues? P.S. sorry for poor eng. Regards Edited June 9, 2011 by asuferoth Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted June 10, 2011 Report Share Posted June 10, 2011 [ ] RecoveryManager_v0.23b.zip 143k a068e46ce1b7573caa518060ee95e5c4 - 05ff1316f2a53a67f04a020c9776850a [ ] RecoveryManager_v0.26b.zip 145k 8d88b79410fdd67a3aa77661b1234a3e - 306ce12890b7bca7bc3b2970e5a434d [ ] RecoveryManager_v0.29b.zip 146k f8019d82eabaa8ef5fbf2498c13f5a12 - bcfe118d13d8a1d5cf5e28e92c339d0d [ ] RecoveryManager_v0.32b.zip 150k d23d123870cc2bac2e3a9065e18b33b7 - xxxxx [ ] RecoveryManager_v0.34b.zip 154k 6d5987ddd4640920e54af2b3cf0be17a - xxxx [ ] RecoveryManager_v0.35b.zip 154k 377c655270b25f41875cd2342099506e - xxxx [ ] RecoveryManager_v0.36b.zip 156k 89f5555e26155114347e95c121131f03 - xxxx laverna:~ sebastian$ laverna:~ sebastian$ wget http://android.podtwo.com/recoverymanager/RecoveryManager_v0.36b.zip --21:22:38-- http://android.podtwo.com/recoverymanager/RecoveryManager_v0.36b.zip => `RecoveryManager_v0.36b.zip' Resolving android.podtwo.com... 74.207.253.45 Connecting to android.podtwo.com|74.207.253.45|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 159,655 [application/zip] 100%[============================================================================ =====================================>] 159,655 46.10K/s ETA 00:00 21:22:42 (46.02 KB/s) - `RecoveryManager_v0.36b.zip' saved [159655/159655] laverna:~ sebastian$ md5 RecoveryManager_v0.36b.zip MD5 (RecoveryManager_v0.36b.zip) = 89f5555e26155114347e95c121131f03 laverna:~ sebastian$[/code] Are you sure you are checking the md5 of the Ziped file? not the APK inside it? Link to comment Share on other sites More sharing options...
Guest asuferoth Posted June 11, 2011 Report Share Posted June 11, 2011 Yeah found it:) So my bad and apoligizes. Wrong file checked. Everything is now ok. But here a TIP for any ZTE Blade users: 2 exactly same models from 1 seller: on first i could apply clockwork using recovery menager but on second couldnt (had to do this manualy and it worked) No idea why, same roms, same recovery menagers and clockworks. Problem was with clockwork. thanks for reply Seb. Cheers:) Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now