Guest Ringli2k Posted February 10, 2011 Report Share Posted February 10, 2011 Hello, I flashed the Japanese Jellyfish RLS9 Rom on my Base Lutea. But now Recovery Manager says "Currently installed recovery: unrecognised" This are my steps: 1. I installed UniversalAndroot v1.6.1 on my Stock Rom then i got root 2. I installed ZTE-Blade Recovery Manager 0.29b 3. I installed recovery-clockwork-blade-2.5.1.8.img with ZTE-Blade Recovery Manager 0.29b 4. I installed the Japanese Jellyfish RLS9 Rom 5. after my device comes up I installed ZTE-Blade Recovery Manager 0.29b again 6. Recovery Manager says "Currently installed recovery: unrecognised" I installed clockwork several times again, but it doesn't resolve my problem. In some posts I saw this problem associate with a space in Filename/folder. My filename is recovery-clockwork-blade-2.5.1.8.img on /mnt/sdcard/ Does anyone now what's wrong??? Thanks, Ringli2k Link to comment Share on other sites More sharing options...
Guest olionair Posted February 10, 2011 Report Share Posted February 10, 2011 Hello, I flashed the Japanese Jellyfish RLS9 Rom on my Base Lutea. But now Recovery Manager says "Currently installed recovery: unrecognised" This are my steps: 1. I installed UniversalAndroot v1.6.1 on my Stock Rom then i got root 2. I installed ZTE-Blade Recovery Manager 0.29b 3. I installed recovery-clockwork-blade-2.5.1.8.img with ZTE-Blade Recovery Manager 0.29b 4. I installed the Japanese Jellyfish RLS9 Rom 5. after my device comes up I installed ZTE-Blade Recovery Manager 0.29b again 6. Recovery Manager says "Currently installed recovery: unrecognised" I installed clockwork several times again, but it doesn't resolve my problem. In some posts I saw this problem associate with a space in Filename/folder. My filename is recovery-clockwork-blade-2.5.1.8.img on /mnt/sdcard/ Does anyone now what's wrong??? Thanks, Ringli2k you need to update database when in the app press the menu button on your blade and hit update database. not all roms may be in this database Link to comment Share on other sites More sharing options...
Guest Ringli2k Posted February 10, 2011 Report Share Posted February 10, 2011 you need to update database when in the app press the menu button on your blade and hit update database. not all roms may be in this database i have update my database now, but same problem! Currently installed recovery: unrecognised I get the info for JJRLS9, but I can't backup or install any Rom with Recovery Manager. Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted February 10, 2011 Report Share Posted February 10, 2011 My filename is recovery-clockwork-blade-2.5.1.8.img on /mnt/sdcard/ From the sound of what your saying, it worked the first time... can you check the MD5SUM of that recovery on your SDCard? just to be sure its not got corrutped somehow? Link to comment Share on other sites More sharing options...
Guest Ringli2k Posted February 10, 2011 Report Share Posted February 10, 2011 From the sound of what your saying, it worked the first time... can you check the MD5SUM of that recovery on your SDCard? just to be sure its not got corrutped somehow? The recovery-clockwork-blade-2.5.1.8.img is since the first install the same. MD5 is cae9935b88359dc96859d39f20d8a821 Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted February 10, 2011 Report Share Posted February 10, 2011 The recovery-clockwork-blade-2.5.1.8.img is since the first install the same. MD5 is cae9935b88359dc96859d39f20d8a821 update your recoverymanger to 0.34 and also download clockworkmod recovery 3.0.0.5 if you still cant get it to reconize your recovery, press menu then select Debug and post up what it tells you here. Link to comment Share on other sites More sharing options...
Guest Ringli2k Posted February 10, 2011 Report Share Posted February 10, 2011 update your recoverymanger to 0.34 and also download clockworkmod recovery 3.0.0.5 if you still cant get it to reconize your recovery, press menu then select Debug and post up what it tells you here. Hello, here the Debug Info: version: v0.34beta device: blade recovery partition: mtd0: 00500000 00020000 "recovery" recovery md5: f7a59c6a6c2e358a26d4d34e9d 45abd8 firmware md5: 00aa49280a7aff36919c0b885fc 9e326 Currently installed Recovery: Unrecognised :-( :-( :-( Link to comment Share on other sites More sharing options...
Guest vareBlade Posted February 10, 2011 Report Share Posted February 10, 2011 Download and install this via the Recovery Manager: recovery-clockwork-3.0.0.5-blade.img - MD5: 24e5f51e0541c865f6b3232f30a0e6ee (its from Seb's clockworks recovery topic) I just did it 5 mins ago and it worked well. Link to comment Share on other sites More sharing options...
Guest Ringli2k Posted February 11, 2011 Report Share Posted February 11, 2011 Download and install this via the Recovery Manager: recovery-clockwork-3.0.0.5-blade.img - MD5: 24e5f51e0541c865f6b3232f30a0e6ee (its from Seb's clockworks recovery topic) I just did it 5 mins ago and it worked well. Hello, same problem and same debug output! :-( Link to comment Share on other sites More sharing options...
Guest vareBlade Posted February 11, 2011 Report Share Posted February 11, 2011 (edited) Your recovery's md5 is different from the one Seb posted: yours: f7a59c6a6c2e358a26d4d34e9d45abd8 seb's: 24e5f51e0541c865f6b3232f30a0e6ee Im not sure if the recovery md5 from your debug output is the md5 of the recovery image you installed but i guess it should be Edited February 11, 2011 by vareBlade Link to comment Share on other sites More sharing options...
Guest Ringli2k Posted February 11, 2011 Report Share Posted February 11, 2011 Your recovery's md5 is different from the one Seb posted: yours: f7a59c6a6c2e358a26d4d34e9d45abd8 seb's: 24e5f51e0541c865f6b3232f30a0e6ee Im not sure if the recovery md5 from your debug output is the md5 of the recovery image you installed but i guess it should be I checked it with Astro and the MD5 from the recovery-clockwork-3.0.0.5-blade.img file on my sd card is 24e5f51e0541c865f6b3232f30a0e6ee very strangely Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted February 11, 2011 Report Share Posted February 11, 2011 recovery partition: mtd0: 00500000 00020000 "recovery" there you go, thats the problem, the recovery partition is bigger than it should be.. Where did you get your blade from? did you check the version of the firmware on it before you install JJ? Did you use a TPT on it? If you do a 'boot into recovery' do you end up in clockwork mod? Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted February 11, 2011 Report Share Posted February 11, 2011 (edited) there you go, thats the problem, the recovery partition is bigger than it should be.. Where did you get your blade from? did you check the version of the firmware on it before you install JJ? Did you use a TPT on it? If you do a 'boot into recovery' do you end up in clockwork mod? actually, having gone back and checked, you have a Base... it has a bigger recovery than the blade.... interesting... Tho what I don't understand is how you got it to work the first time.... I will work on adding support for the base to the next version..... I'll also try and check the other dumps i've got incase there are anymore.. your the first person to point it out to me at least :P I sort of want to tell you to try the TPT, but I'm not sure how your device would take it... :D Edited February 11, 2011 by Sebastian404 Link to comment Share on other sites More sharing options...
Guest Ringli2k Posted February 12, 2011 Report Share Posted February 12, 2011 actually, having gone back and checked, you have a Base... it has a bigger recovery than the blade.... interesting... Tho what I don't understand is how you got it to work the first time.... I will work on adding support for the base to the next version..... I'll also try and check the other dumps i've got incase there are anymore.. your the first person to point it out to me at least :P I sort of want to tell you to try the TPT, but I'm not sure how your device would take it... :D Thank you for the information! After I read your post, I don't understand why does it work the first time too. But I'll waiting for your next relase of your recovery manger and hope, it works for my Base Lutea. I can flash a other rom directly from recovery. If you're looking for a test person, I'm your man! :huh: You make a great job Sebastian404!!! Link to comment Share on other sites More sharing options...
Guest Vansphone Posted February 15, 2011 Report Share Posted February 15, 2011 (edited) I have exactly the same problem as the OP. My Blade was delivered yesterday and I put on the lasted version of Recovery Manager (0.34) and checked the MD5 before install. I downloaded clockworkmod recovery 3.0.0.5 and again checked the MD5 before install. The app says the database is up to date. But I get Currently installed Recovery: Unrecognised I have not yet tried to flash a rom, not wanting to try until recovery is recognised. I have run debug but I do not know how to paste the result here however it does say this: recovery partition: mtd0:00480000 00020000 "recovery" Will I also have to wait until another version of Recovery Manager is issued? Thanks Edited February 15, 2011 by Vansphone Link to comment Share on other sites More sharing options...
Guest derek500 Posted February 15, 2011 Report Share Posted February 15, 2011 (edited) I have exactly the same problem as the OP. My Blade was delivered yesterday and I put on the lasted version of Recovery Manager (0.34) and checked the MD5 before install. I downloaded clockworkmod recovery 3.0.0.5 and again checked the MD5 before install. The app says the database is up to date. But I get Currently installed Recovery: Unrecognised I'm getting exactly the same problems with my one!! Spending all day going round in circles!! I have unlocked my phone, would that make a difference? From debug:- recovery partition: mtd0:00480000 00020000 "recovery" Edited February 15, 2011 by derek500 Link to comment Share on other sites More sharing options...
Guest Vansphone Posted February 15, 2011 Report Share Posted February 15, 2011 I'm getting exactly the same problems with my one!! Spending all day going round in circles!! I have unlocked my phone, would that make a difference? From debug:- recovery partition: mtd0:00480000 00020000 "recovery" I have unlocked my phone and rooted it. Out of interest, how old is your phone. I was wondering if something has just changed on the phone. Link to comment Share on other sites More sharing options...
Guest Vansphone Posted February 15, 2011 Report Share Posted February 15, 2011 I'm getting exactly the same problems with my one!! Spending all day going round in circles!! I have unlocked my phone, would that make a difference? From debug:- recovery partition: mtd0:00480000 00020000 "recovery" Just seen the fix on another thread. You get this error if the directory on the SD card containing the file has spaces. I have just removed my spaces and it now works Link to comment Share on other sites More sharing options...
Guest derek500 Posted February 15, 2011 Report Share Posted February 15, 2011 I have unlocked my phone and rooted it. Out of interest, how old is your phone. I was wondering if something has just changed on the phone. December 2010. TFT screen. Link to comment Share on other sites More sharing options...
Guest derek500 Posted February 15, 2011 Report Share Posted February 15, 2011 Just seen the fix on another thread. You get this error if the directory on the SD card containing the file has spaces. I have just removed my spaces and it now works I saw that too!! I put it on the SD card but not in a folder. I've just transferred it to a folder without spaces, 'downloads', but still not working. Link to comment Share on other sites More sharing options...
Guest Vansphone Posted February 15, 2011 Report Share Posted February 15, 2011 I saw that too!! I put it on the SD card but not in a folder. I've just transferred it to a folder without spaces, 'downloads', but still not working. Are using the latest version of Recovery Manager (0.34) and clockworkmod recovery (3.0.0.5) Have you pressed the menu button while the app is open and updated the database? As soon as I took out the spaces in the folder name mine worked like a charm Link to comment Share on other sites More sharing options...
Guest derek500 Posted February 15, 2011 Report Share Posted February 15, 2011 (edited) Are using the latest version of Recovery Manager (0.34) and clockworkmod recovery (3.0.0.5) Have you pressed the menu button while the app is open and updated the database? As soon as I took out the spaces in the folder name mine worked like a charm Yes, yes and yes. Perhaps I'm not grasping the 'spaces' thing. What spaces did you have in the folder name? Edited February 15, 2011 by derek500 Link to comment Share on other sites More sharing options...
Guest Sebastian404 Posted February 16, 2011 Report Share Posted February 16, 2011 Currently installed Recovery: Unrecognised Ok, I've made a slight update to the way RM detects your recovery image... can you give THIS VERSION a go and let me know if it recognizes your recovery now? Link to comment Share on other sites More sharing options...
Guest derek500 Posted February 18, 2011 Report Share Posted February 18, 2011 Ok, I've made a slight update to the way RM detects your recovery image... can you give THIS VERSION a go and let me know if it recognizes your recovery now? Sorry not to reply sooner. I gave up and tried the Fastboot method which worked splendidly. I upgraded to JJ RLS9, which is running with no problems. Incidentally it's improved the touch screen no end!! I could even use my Golfshot app wearing a leather glove and sliding decks of cards around playing Solitaire is so easy now. Link to comment Share on other sites More sharing options...
Guest hauiyub Posted February 21, 2011 Report Share Posted February 21, 2011 (edited) Install methods tested: * Recovery installed with Recovery Manager * Flash Image using Android Terminal Emulator $ flash_image recovery recovery.img (with recovery-clockwork-3.0.0.6-blade.img renamed as recovery.img Both methods give the same debug info in Recovery Manager. And... Currently installed Recovery: Unrecognised (With updated database) -- Recovery Manager, Debug Info DEBUG INFO: version: v0.35b device: blade recovery partiton: mtd0: 00480000 00020000 recovery md5: 85d509f77546e1bf2f89efceaa35e614 firmware md5: 62aff9524cfd71da7f89602f858aa898 -- -- Recovery Info installed recovery: recovery-clockwork-3.0.0.6-blade.img image size: 3772416 bytes recovery image from nandroid backup nandroid.md5: "85d509f77546e1bf2f89efceaa35e614 recovery.img" $ cp recovery.img recovery_tc.img $ truncate -s 3772416 recovery_tc.img $ md5sum recovery-clockwork-3.0.0.6-blade.img recovery_tc.img 4b949d51c54501e1a3dd0a4c6095766e recovery-clockwork-3.0.0.6-blade.img 4b949d51c54501e1a3dd0a4c6095766e recovery_tc.img -- {CyanogenMod-7.0.0-RC1-Blade} installed ok (directly using the installed recovery). And it works as expected. The backup of the original firmware (unmodified) was also ok, but I have not tried to restore it. Tested ok with "$ md5sum -c nandroid.md5" after copying the backup. So there seems to be a different size for the Recovery part of the NAND filesystem.??. for some of the ZTE Blades. This device: Orange SF with OLED screen. Edited February 21, 2011 by hauiyub 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