Jump to content


Photo

[APP] Recovery Manager v0.36 [BETA]

* * * - - 7 votes

  • Please log in to reply
312 replies to this topic

#101
wederwoord

wederwoord

    Newbie

  • Members
  • Pip
  • 13 posts
  • Devices:ZTE BLADE

did you download the latest recovery image from the first page?


I still don't know what I did wrong but the app did not install clockwork or the firmware.
After installing usb drivers on my windows 7, I was able to install both clockwork and the firmware manually.

  • 0

#102
benmcd

benmcd

    Newbie

  • Members
  • Pip
  • 16 posts
Any luck on the modaco 2.1 force closes?

  • 0

#103
fineking

fineking

    Newbie

  • Members
  • Pip
  • 8 posts
  • Devices:softbank 003Z
Hello, Sebastian404

First, Thank you for the Recovery tools provided.

My phone is softbank 003Z (Japanese ZTE-Blade family), But When I used RecoveryManager_v0.26b to flash the clockwork-blade-2.5.1.8 Recovery image ,
encountered the following problem, Yesterday.


Before flash(The original Recovery system):
Switch on my phone by holding volume down + power, first display SoftBank Logo, after a few seconds display
the message "System Update, please put the update file to the SDcard" (the message is in japanese)


After flash(flashed the clockwork-blade-2.5.1.8 Recovery image by RecoveryManager_v0.26b):
Switch on my phone by holding volume down + power, display SoftBank Logo then the screen is freeze.
But the phone system Can be used normally, when Normal Reboot. It looks like only the Recovery System halt.

I run Recovery Manager in my phone, Click the Firmware button, display "Currently installed Firmware: Stock Firmware(SBM_P729J)".
Click the Recovery button, display "Currently installed Recovery: Unrecognised".

I tried flashing the clockwork-blade-2.5.1.8 Recovery image again and the clockwork-blade-2.5.1.3 Recovery image by RecoveryManager_v0.26b, but the problem is same.
I tried flashing the clockwork-blade-2.5.1.8 Recovery image by Android terminal, but the problem is same.

How to Install Clockwork Recovery on SoftBank 003Z ?

Please help me thank you very much.


P.S
1. I used Universal AndRoot to rooted and SuperUser.
2. I refer to the page
http://android.modac...-the-zte-blade/

  • 0

#104
ergo911

ergo911

    Regular

  • Members
  • PipPip
  • 83 posts
  • Gender:Male
  • Devices:HP Touchpad 32GB
thanks for your good work :lol:

  • 0
android.planet.ee

#105
ThrashMan

ThrashMan

    Diehard

  • MoDaCo Silver
  • PipPipPipPip
  • 464 posts
  • Gender:Male
  • Location:Miserable old git!
  • Devices:ZTE Blade [UK 512MB TFT]
Thanks for the App Sebastian404, nice work.

Tried installing the latest XenoROM (r4) and it failed. The problem was caused by the downloaded zip being called xenorom r4.zip (note the space).

Can Blade Recovery Manager be made to naturally quote the ROM filename? Assuming Clockwork accepts filenames with spaces if quoted?

Regards,
Andy.

  • 0

#106
ololizoz

ololizoz

    Enthusiast

  • Members
  • PipPipPip
  • 151 posts
  • Gender:Male
  • Location:Sweden
  • Devices:LG Optimus 2X P990
  • Twitter:@ololizoz
It doesent recognize JapJelly RLS8

  • 0

#107
ololizoz

ololizoz

    Enthusiast

  • Members
  • PipPipPip
  • 151 posts
  • Gender:Male
  • Location:Sweden
  • Devices:LG Optimus 2X P990
  • Twitter:@ololizoz
And if im upgrading from RLS8 to RLS9, should I use Install Firmware och Install Firmware update? I want to keep all my data.

  • 0

#108
Sebastian404

Sebastian404

    Hardcore

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

Thanks for the App Sebastian404, nice work.

Tried installing the latest XenoROM (r4) and it failed. The problem was caused by the downloaded zip being called xenorom r4.zip (note the space).

Can Blade Recovery Manager be made to naturally quote the ROM filename? Assuming Clockwork accepts filenames with spaces if quoted?

Regards,
Andy.


That seems to be a problem with clockworkmod recovery 2.5.1.8 unfortunately... I think someone else might of spotted it since it is fixed in 3.0.0.5....

I'm going to push out an updated version shortly that will add support for the v3 clockworkmod. that should fix your problem

  • 0

#109
Sebastian404

Sebastian404

    Hardcore

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

It doesent recognize JapJelly RLS8


I've (hopefully) managed to update the database with all the JJ roms I could find... if its still not recognized can you let me know which one your using?

  • 0

#110
Sebastian404

Sebastian404

    Hardcore

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

My phone is softbank 003Z (Japanese ZTE-Blade family), But When I used RecoveryManager_v0.26b to flash the clockwork-blade-2.5.1.8 Recovery image ,


Unfortunately the 003Z is not 100% compatible with the ZTE-Blade. I am trying to get hold of a device so I can do some testing, but not much luck so far..

  • 0

#111
olionair

olionair

    Enthusiast

  • MoDaCo Silver
  • PipPipPip
  • 181 posts
  • Gender:Male
  • Location:UK
  • Devices:Transformer and SGS2
  • Twitter:@OliverHaywood
it is FC ing on my FLB2.2 with 3.0.0.5

  • 0

#112
Sebastian404

Sebastian404

    Hardcore

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

it is FC ing on my FLB2.2 with 3.0.0.5


you run logcat on it?

  • 0

#113
The Soup Thief

The Soup Thief

    Hardcore

  • MoDaCo Silver
  • PipPipPipPipPipPip
  • 1,029 posts
  • Gender:Male
  • Location:Dublin
  • Devices:Nexus 5 (N4 etc retired)
  • Twitter:@TheSoupThief
Sorry, but I'm getting forced closes too opening up v0.29 after unzipping it and installing the app through Estrongs - seemed to install fine (running Paul's Froyo r11)

v0.26 was opening fine and letting me meddle about, though wouldn't recognise the ROM

(logcat's a bit beyond my ken, but if you tell me what to do I'll give it a go and post the outcome)

EDIT - tried installing the zip (md5 was fine, btw) through clockwork 3.0.0.5 but it aborted

Edited by The Soup Thief, 25 January 2011 - 08:45 PM.

  • 0

#114
FrankieADZ

FrankieADZ

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,255 posts
Hey,
Well Ive tired loading it up and it hangs on a black screen; Im currently using Paul's Froyo R11 rom.

I'll try again tomorrow to see if works.

  • 0

#115
Sebastian404

Sebastian404

    Hardcore

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

it is FC ing on my FLB2.2 with 3.0.0.5



Well thats annoying, I got it working with MoDaCo's 2.1 firmwares.. need to check 2.2 now grrr...

  • 0

#116
olionair

olionair

    Enthusiast

  • MoDaCo Silver
  • PipPipPip
  • 181 posts
  • Gender:Male
  • Location:UK
  • Devices:Transformer and SGS2
  • Twitter:@OliverHaywood

Well thats annoying, I got it working with MoDaCo's 2.1 firmwares.. need to check 2.2 now grrr...

do you want me to see what the problem is?

  • 0

#117
Sebastian404

Sebastian404

    Hardcore

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

do you want me to see what the problem is?



the problem seems to be that Paul likes to move CHMOD around :lol:

I downloaded r7 and it is Force closing...

Edited by Sebastian404, 25 January 2011 - 09:44 PM.

  • 0

#118
olionair

olionair

    Enthusiast

  • MoDaCo Silver
  • PipPipPip
  • 181 posts
  • Gender:Male
  • Location:UK
  • Devices:Transformer and SGS2
  • Twitter:@OliverHaywood

the problem seems to be that Paul likes to move CHMOD around :lol:

I downloaded r7 and it is Force closing...

k so same problem of flb i presume

  • 0

#119
Sebastian404

Sebastian404

    Hardcore

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

k so same problem of flb i presume


OK, it seems I messed up when I compiled the thing, if you re-download it from the first page, it should probably work now... (he said hopefully)...

I've tested it on the ModaCo 2.1 & 2.2 firmwares.. it seems to work...

I assume it should work on FLB too....

  • 0

#120
olionair

olionair

    Enthusiast

  • MoDaCo Silver
  • PipPipPip
  • 181 posts
  • Gender:Male
  • Location:UK
  • Devices:Transformer and SGS2
  • Twitter:@OliverHaywood
k thanks you fancy releasing this on the market?

  • 0




3 user(s) are reading this topic

0 members, 3 guests, 0 anonymous users