Jump to content


Photo

[APP] Recovery Manager v0.36 [BETA]

* * * - - 7 votes

  • Please log in to reply
312 replies to this topic

#61
vareBlade

vareBlade

    Enthusiast

  • Members
  • PipPipPip
  • 206 posts
  • Gender:Male
  • Devices:ZTE-Blade
  • Twitter:@varemenos
Ok, i've installed the .26b now and placed the clockworks 2.5.1.8 in the sd card and the installation of recovery was successful. (though it still calls it "Unrecognized recovery").
By the way, why doesnt the firmware tab work for stock roms?

  • 0


-----------------------------------------------------------------------------------------
Varemenos.com | AKLP.gr
-----------------------------------------------------------------------------------------


#62
dbeckett

dbeckett

    Newbie

  • Members
  • Pip
  • 44 posts
Still having problems on Modaco R4 2.1

Cleared the programs cache, uninstalled it, unrooted device with androot, re-rooted device with androot, installed new version, get superuser permission, click allow, force closes

Tried logcat,hope this is right

On first entry(with superuser permission dialogue box)

C:\Users\David>adb logcat RecoveryManager:* *:s
D/RecoveryManager( 2939): extract_internal_file: called
D/RecoveryManager( 2939): extract_internal_file: raw/recovery_tool
D/RecoveryManager( 2939): extract_internal_file: /data/data/com.podtwo.RecoveryManager
D/RecoveryManager( 2939): extract_internal_file: 493
D/RecoveryManager( 2939): extract_internal_file: IOException Error: java.io.IOException: Error running exec(). Commands: [/system/bin/chmod, 0755, /data/data/com.podtwo.RecoveryManager/recovery_tool] Working Directory: null Environment: null
D/RecoveryManager( 2939): extract_internal_file: called
D/RecoveryManager( 2939): extract_internal_file: xml/device.xml
D/RecoveryManager( 2939): extract_internal_file: /data/data/com.podtwo.RecoveryManager/cache
D/RecoveryManager( 2939): extract_internal_file: 448
D/RecoveryManager( 2939): extract_internal_file: IOException Error: java.io.IOException: Error running exec(). Commands: [/system/bin/chmod, 0700, /data/data/com.podtwo.RecoveryManager/cache/device.xml] Working Directory: null Environment:null
D/RecoveryManager( 2939): extract_internal_file: called
D/RecoveryManager( 2939): extract_internal_file: xml/recovery.xml
D/RecoveryManager( 2939): extract_internal_file: /data/data/com.podtwo.RecoveryManager/cache
D/RecoveryManager( 2939): extract_internal_file: 448
D/RecoveryManager( 2939): extract_internal_file: IOException Error: java.io.IOException: Error running exec(). Commands: [/system/bin/chmod, 0700, /data/data/com.podtwo.RecoveryManager/cache/recovery.xml] Working Directory: null Environment: null
D/RecoveryManager( 2939): extract_internal_file: called
D/RecoveryManager( 2939): extract_internal_file: xml/firmware.xml
D/RecoveryManager( 2939): extract_internal_file: /data/data/com.podtwo.RecoveryManager/cache
D/RecoveryManager( 2939): extract_internal_file: 448
D/RecoveryManager( 2939): extract_internal_file: IOException Error: java.io.IOException: Error running exec(). Commands: [/system/bin/chmod, 0700, /data/data/com.podtwo.RecoveryManager/cache/firmware.xml] Working Directory: null Environment: null
D/RecoveryManager( 2939): extract_internal_file: called
D/RecoveryManager( 2939): extract_internal_file: xml/theme.xml
D/RecoveryManager( 2939): extract_internal_file: /data/data/com.podtwo.RecoveryManager/cache
D/RecoveryManager( 2939): extract_internal_file: 448
D/RecoveryManager( 2939): extract_internal_file: IOException Error: java.io.IOException: Error running exec(). Commands: [/system/bin/chmod, 0700, /data/data/com.podtwo.RecoveryManager/cache/theme.xml] Working Directory: null Environment: null
D/RecoveryManager( 2939): update_database: called
D/RecoveryManager( 2939): recovery_set_current: called
D/RecoveryManager( 2939): recovery_md5: called
D/RecoveryManager( 2939): recovery_md5: returning null




On second entry

C:\Users\David>adb logcat RecoveryManager:* *:s
D/RecoveryManager( 3204): extract_internal_file: called
D/RecoveryManager( 3204): extract_internal_file: raw/recovery_tool
D/RecoveryManager( 3204): extract_internal_file: /data/data/com.podtwo.RecoveryManager
D/RecoveryManager( 3204): extract_internal_file: 493
D/RecoveryManager( 3204): extract_internal_file: File exists or newer
D/RecoveryManager( 3204): extract_internal_file: called
D/RecoveryManager( 3204): extract_internal_file: xml/device.xml
D/RecoveryManager( 3204): extract_internal_file: /data/data/com.podtwo.RecoveryManager/cache
D/RecoveryManager( 3204): extract_internal_file: 448
D/RecoveryManager( 3204): extract_internal_file: File exists or newer
D/RecoveryManager( 3204): extract_internal_file: called
D/RecoveryManager( 3204): extract_internal_file: xml/recovery.xml
D/RecoveryManager( 3204): extract_internal_file: /data/data/com.podtwo.RecoveryManager/cache
D/RecoveryManager( 3204): extract_internal_file: 448
D/RecoveryManager( 3204): extract_internal_file: File exists or newer
D/RecoveryManager( 3204): extract_internal_file: called
D/RecoveryManager( 3204): extract_internal_file: xml/firmware.xml
D/RecoveryManager( 3204): extract_internal_file: /data/data/com.podtwo.RecoveryManager/cache
D/RecoveryManager( 3204): extract_internal_file: 448
D/RecoveryManager( 3204): extract_internal_file: File exists or newer
D/RecoveryManager( 3204): extract_internal_file: called
D/RecoveryManager( 3204): extract_internal_file: xml/theme.xml
D/RecoveryManager( 3204): extract_internal_file: /data/data/com.podtwo.RecoveryManager/cache
D/RecoveryManager( 3204): extract_internal_file: 448
D/RecoveryManager( 3204): extract_internal_file: File exists or newer
D/RecoveryManager( 3204): update_database: called
D/RecoveryManager( 3204): recovery_set_current: called
D/RecoveryManager( 3204): recovery_md5: called
D/RecoveryManager( 3204): recovery_md5: returning null


Edit- Might be r/w permissions?

Edited by dbeckett, 19 January 2011 - 04:56 PM.

  • 0

#63
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404

Ok, i've installed the .26b now and placed the clockworks 2.5.1.8 in the sd card and the installation of recovery was successful. (though it still calls it "Unrecognized recovery").


I noticed your not using a UK Blade... so I have couple of questions that might help us out..

Where did you get your device?
Have you used any of the TPT updates to resize your partitions?
do you know what size you recovery partition is?


To answer the last question you might need to look at your /proc/mtd file...

  • 0

#64
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404

Still having problems on Modaco R4 2.1

Cleared the programs cache, uninstalled it, unrooted device with androot, re-rooted device with androot, installed new version, get superuser permission, click allow, force closes

Tried logcat,hope this is right

On first entry(with superuser permission dialogue box)
On second entry
Edit- Might be r/w permissions?


Interesting, it looks like its not managed to SU correctly... tho I'd expected it to actually fail to even get as far as that before it fell over....

I'll download Modaco R4 and give it a go on my device, see if I cant replicate that and get to the bottom of it...

  • 0

#65
fonix232

fonix232

    Addict

  • Members
  • PipPipPipPipPip
  • 942 posts
  • Location:Hungary, Debrecen
  • Devices:ZTE Blade [TFT 512RAM]
  • Twitter:@fonix232
Seb, my offer is still standing ;) Just a word and I'm all yours!

  • 0
If you like my work, invite me for a drink or two!

Also, take a look at my Blade-dedicated site too! fonix232.co.cc

#66
vareBlade

vareBlade

    Enthusiast

  • Members
  • PipPipPip
  • 206 posts
  • Gender:Male
  • Devices:ZTE-Blade
  • Twitter:@varemenos

I noticed your not using a UK Blade... so I have couple of questions that might help us out..

Where did you get your device?
Have you used any of the TPT updates to resize your partitions?
do you know what size you recovery partition is?
To answer the last question you might need to look at your /proc/mtd file...


Hmmm, well i bought my device from Wind in Greece. Its a TFT 256mb one which i then used the hungarian-512-fix to get it to 512mb.
Except that time i switched it to 512 i never again used TPT. (idk, i never needed to).
dev:		 size			erasesize	   name
mtd0:		00480000		00020000		"recovery"

  • 0


-----------------------------------------------------------------------------------------
Varemenos.com | AKLP.gr
-----------------------------------------------------------------------------------------


#67
gameSTICKER

gameSTICKER

    Regular

  • Members
  • PipPip
  • 91 posts
  • Devices:Orange San Francisco OLED

Ok, i've installed the .26b now and placed the clockworks 2.5.1.8 in the sd card and the installation of recovery was successful. (though it still calls it "Unrecognized recovery").
By the way, why doesnt the firmware tab work for stock roms?

Unrecognised Recovery [Solved]

I had the same issue. The I went to http://android.podtwo.com/recovery/ as directed in second post and downloaded and installed recovery-clockwork-blade-2.5.1.8.img and it was recognized. Earlier I had dowloaded and installed my recovery from http://android.modac...overy-oled-tft/

Just out of curiosity, I compared the MD5s of both recoveries and they were different, so maybe the one in http://android.podtwo.com/recovery/ is a recent binary and hence it is recognized and not the old one available in http://android.modac...overy-oled-tft/

EDIT

Seb seems to have updated the recovery image at http://android.modac...overy-oled-tft/ too, so its only an issue for ppl who've got an earlier version of 2.5.1.8 (I have old version of 2.1.5.8 downloaded from the thread, and I swear its MD5s are different ;) )

Edited by gameSTICKER, 19 January 2011 - 09:48 PM.

  • 0
.: SanF - OLED 512 3.2MP :.
Swedish Spring RLS5, GEN1 Layout

#68
Quu

Quu

    Enthusiast

  • Members
  • PipPipPip
  • 165 posts
  • Devices:ZTE Blade
0.26b says "Unrecognised" on firmware and recovery.

Finnish Blade with JJ8.

  • 0

#69
gameSTICKER

gameSTICKER

    Regular

  • Members
  • PipPip
  • 91 posts
  • Devices:Orange San Francisco OLED
Hey Seb, just installed 0.26b, tried installing a couple of updates and all working fine. A few suggestions:
  • Under Firmware tab, Install Firmware and Install Firmware Update seems redundant. They can be replaced by any one of follows
    • Two seperate entries "Install Firmware" and "Install Firmware Addons/Updates" just like now, but "Install Firmware" displays zips >50mb and "Install Firmware Addons/Update" displays zips <50mb
    • A single entry "Install Firmware", on click displays list of ZIPs just like now, on select asks you to "wipe data/settings". User can select to wipe for firmware installs or can leave it unchecked for addon installation
  • Maybe the unimplemented entries can be disabled/greyed-out for now

  • 0
.: SanF - OLED 512 3.2MP :.
Swedish Spring RLS5, GEN1 Layout

#70
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404

Hmmm, well i bought my device from Wind in Greece. Its a TFT 256mb one which i then used the hungarian-512-fix to get it to 512mb.
Except that time i switched it to 512 i never again used TPT. (idk, i never needed to).

dev:		 size			erasesize	   name
mtd0:		00480000		00020000		"recovery"


hmm, no thats right, I was wondering if maybe your recovery image was a different size... OK, can you run the logcat command and see what its saying?

Oh which ROM are you using?

  • 0

#71
benmcd

benmcd

    Newbie

  • Members
  • Pip
  • 16 posts
Hey, I posted message in other topic, but might be best in here. I'm having same problems as other ppl with modaco 2.1, crashing everytime. Hope theres a solution, as it sounds like a great program. Thanks!

  • 0

#72
vareBlade

vareBlade

    Enthusiast

  • Members
  • PipPipPip
  • 206 posts
  • Gender:Male
  • Devices:ZTE-Blade
  • Twitter:@varemenos
GameSticker's guide worked for me, now its recognizing it.
Btw, my rom is the Wind stock 2.1 rom
Wind (Greece): ZTE Blade
WIND_P729BV1.0.0B02
CODE
ro.build.version.release=2.1-update1
ro.build.date=Mon Oct 25 16:44:45 CST 2010
ro.build.sw_internal_version=WIND_P729BV1.0.0B05
ro.build.display.id=ZTE_P729BV1.0.0B02
ro.com.google.gmsversion=2.1_r11

Also, i never tried logcat, so im not sure how to use it

  • 0


-----------------------------------------------------------------------------------------
Varemenos.com | AKLP.gr
-----------------------------------------------------------------------------------------


#73
Quu

Quu

    Enthusiast

  • Members
  • PipPipPip
  • 165 posts
  • Devices:ZTE Blade

0.26b says "Unrecognised" on firmware and recovery.

Finnish Blade with JJ8.



GameSticker's guide worked for me, now its recognizing it.


Okay.
That seems to do the work, recovery is now recognized.
Somehow i had "old" 2.5.1.8 or something?

  • 0

#74
bigblackbear7

bigblackbear7

    Newbie

  • Members
  • Pip
  • 1 posts
Im using the stock rom on the phone and trying to install new firmware from this app, it says that you need to change rom first.

  • 0

#75
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404

Hey, I posted message in other topic, but might be best in here. I'm having same problems as other ppl with modaco 2.1, crashing everytime. Hope theres a solution, as it sounds like a great program. Thanks!



I found the problem with the modaco rom, and I've got a fix for it, but Im not having much time to do that much, probably be an update at the weekend

  • 0

#76
Phoenix Silver

Phoenix Silver

    Hardcore

  • MoDaCo Silver
  • PipPipPipPipPipPip
  • 1,839 posts
  • Gender:Female
  • Location:Strasbourg.
  • Devices:ZTE Blade Orange France
  • Twitter:@phoenixbjp
one question i have recovery 2.5.1.8 experimental installed (with ext3 support)
is this works ?

  • 0
Si le corps est mortel, l’âme elle est éternelle.

#77
gavboy

gavboy

    Regular

  • MoDaCo Silver
  • PipPip
  • 95 posts
  • Location:London

I found the problem with the modaco rom, and I've got a fix for it, but Im not having much time to do that much, probably be an update at the weekend


Good to know! Looking forward to the fix.

Thanks

  • 0

#78
Sebastian404

Sebastian404

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,104 posts
  • Gender:Male
  • Location:Somwhere Near Mountain View, California
  • Devices:lots of them
  • Twitter:@sebastian404

one question i have recovery 2.5.1.8 experimental installed (with ext3 support)
is this works ?



Okay.
That seems to do the work, recovery is now recognized.
Somehow i had "old" 2.5.1.8 or something?



if either of you still have those old files, and you upload them somewhere and PM me the link? I'll look at adding them

  • 0

#79
gameSTICKER

gameSTICKER

    Regular

  • Members
  • PipPip
  • 91 posts
  • Devices:Orange San Francisco OLED

if either of you still have those old files, and you upload them somewhere and PM me the link? I'll look at adding them


http://www.sendspace.com/file/haf92s

  • 0
.: SanF - OLED 512 3.2MP :.
Swedish Spring RLS5, GEN1 Layout

#80
Xenon0816

Xenon0816

    Enthusiast

  • Members
  • PipPipPip
  • 222 posts
  • Gender:Male
  • Location:Berlin
  • Devices:HTC Blackstone, OSF
I just installed this app... At first the app didn't recognise the recovery I had installed (2.5.1.8), but I can confirm that a reinstall of the recovery via recovery manager sorts this problem.
Everything else worked good so far... I did a backup, installed a new rom... Fine!
But I have to agree with gamesticker:

Hey Seb, just installed 0.26b, tried installing a couple of updates and all working fine. A few suggestions:

  • Under Firmware tab, Install Firmware and Install Firmware Update seems redundant. They can be replaced by any one of follows
    • Two seperate entries "Install Firmware" and "Install Firmware Addons/Updates" just like now, but "Install Firmware" displays zips >50mb and "Install Firmware Addons/Update" displays zips <50mb
    • A single entry "Install Firmware", on click displays list of ZIPs just like now, on select asks you to "wipe data/settings". User can select to wipe for firmware installs or can leave it unchecked for addon installation
  • Maybe the unimplemented entries can be disabled/greyed-out for now


  • 0




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users