[WIP] ClockworkMod Recovery - FreeXperia

[Bin4ry]

Hi,

here comes Recovery for Play of Team FreeXperia.

Download here: (Beta1 - Update 20.06.2011 - 18:28h GMT+1)
http://www.multiupload.com/VC3JRZ74H0

Broken:
Cannot backup&restore boot partition (kernel related)

To test use this command:
fastboot boot recoveryPLAY.img

Button mapping: (thanks Logseman)
Back- Back
Home/Vol UP - Up
Menu/Vol DOWN - Down
Search - OK

Please DO NOT FLASH! This recovery is designed to work just as recovery, if you flash it to your device it will NOT boot system anymore!

Please test and report functions. If there are errors please include EXACT outpot of errormessage.

Thanks to Blagus for his Xperia Play Kernel!

To gain root on every ROM (Stock ones too) just flash the attached RootXperia.zip via Recovery
Regards
Bin4ry & Team FreeXperia

 

[Logseman]

I assume we need to install the custom kernel first?

 

[Bin4ry]

No! You have NOT to install custom kernel to use this.
Just issue the command i wrote on your windows console. Then phone boots into recovery!

Regards

 

[Blagus]

I assume we need to install the custom kernel first?

The recovery image is structured exatcly as boot.img, with the difference in executable files - regular boot.img boots Android system from /system partition, while recovery boots into... well, recovery
So, since it's structured just as boot.img, you have to pack kernel inside as well. That's where, in this case mine, zImage comes in handy instead of unpacking SE's special boot.img structure, it was easier to take zImage from standard boot.img.

 

[AndroHero]

ive just tried it now, boots into CWM fine, im going to try a nandroid and report back

 

[Logseman]

It looks weird in this DDMS capture, but in the phone it looks all right (black background, orange text). I've had no error messages of any kind.

Button mapping:
Back- Back
Home/Vol UP - Up
Menu/Vol DOWN - Down
Search/Power - OK

 

[Bin4ry]

This capture looks funny
But important is how it looks on device. I doubt that ddms cannot capture 32bit framebuffers

Regards
Bin4ry

 

[AndroHero]

Ok, i did a nandroid, rebooted, booted back into bootloader and fastboot erased /system/, pushed the recovery back and tried to restore /system/ but i get the error " Error formatting system " i also get the same error in the mounts & storage menu can i flash the nandroid image from fastboot?


*edit* no it wont let me flash it from fastboot, it tells me the image is too large lol probably because i moved some widgets and lwp's to /system/, no worries i'll flash the image in the development section.

 

[mehmehmen]

Recovery booted fine, did a nandroid backup worked fine, not sure i want to follow suit and delete a load of stuff and try restore. will wait to see what androhero and bin4ry can figure out first with andro's issue

 

[AndroHero]

Recovery booted fine, did a nandroid backup worked fine, not sure i want to follow suit and delete a load of stuff and try restore. will wait to see what androhero and bin4ry can figure out first with andro's issue

try and clear cache, see if you get the same error? if the action works it wont matter if cache gets formatted

 

[Logseman]

I hope you can help me figure this out, because right now I am astonished at least.

I've been poking around with ClockworkMod, and getting a couple of errors. I know there is an error reporting utility inside CWM, "Report Error" in "advanced" so I made use of it. However, the log would save to "/sdcard/clockworkmod/recovery.log".

Since I'm using the custom kernel, I'm not able to use the sdcard as it seems to be improperly mounted. It shows as mounted in CWM, I unmounted it and remounted it again to no avail... though it can be mounted on the computer properly.

However, that's not the point. I thought I'd do a search on "recovery" with Root Explorer, wanting to find the Recovery.log somewhere else. And boy, did I find it. I found the two recovery logs I saved inside the folder /data/system/dropbox . I happen to have DB installed in my Android. But not only that, I found my kmsg logs, and boot logs, registered there as well.

Hereby I attach the two recovery logs. Does it make sense that these kinds of logs are saved in such a folder? Am I worrying unnecessarily?

 

[AndroHero]

this is one of the reaons why google take root access off us in the first place isnt it?

 

[Bin4ry]

Thanks for the logs.Dunno why they was stored in DB folder


@AndroHero:
Yes just restore the img files from backup via fastboot flash.

Regards
Bin4ry

 

[crispyduckling]

where excatly do i put the play recovery.img?

 

[AndroHero]

where excatly do i put the play recovery.img?

just put it in the same folder as fastboot.exe

 

[svenk919]

When backing up the progress bar doesn't work and it can take some minutes, so just be patient when doing a back-up.

Are their any specific options you like us to play with?

 

[crispyduckling]

just put it in the same folder as fastboot.exe

cheers mate

 

[mehmehmen]

okay so i formatted the cache and it comes back

Cach wipe complete.
E:Can't Mount /cache/recovery/log
E:Can't Open /cache/recovery/log
E:Cant mount /cache/recovery/last_log
E:Cant Open /cache/recovery/last_log


it wiped cache ok but is this error something i need to be worried about in away before attempt wipe and restore of system with my nandroid?

 

[Logseman]

Do not bother trying to restore a nandroid backup: the /system partition won't get formatted and the operation will be cancelled.

 

[svenk919]

The back-up made a cache.img, data.img, system.img and a .android_secure.img

I assume I can flash the system.img with fastboot like I used to do when rooting through fastboot? Could safe me the bloatware removal trouble after I get into a bootloop (yet again ).