Recovery

[runandhide05]

So I've started going a little more hardball now. Using the clockwordmod recovery image I had created from the boot and recovery images, I hexedited all the stock parts of recovery back into the file minus the ramdisk (since it contains cwm).. Invalid CG HAB (Recovery). I'm not done playing with that aspect yet, however.
Edit: I also added in all trailing information from the stock recovery image including the Moto sigs after the embedded gzip files, making the image identical in size to stock.

New things learned:
Upon pulling apart the stock recovery image and reading the recovery init.rc, the stock recovery image IS actually trying to find an update in /sdcard directory. However, for some odd reason, it won't properly mount in the stock recovery.

Here is the stock recovery init.rc, if anyone wants to add some input:

on early-init
    start ueventd


on init
    export PATH /sbin
    export ANDROID_ROOT /system
    export ANDROID_DATA /data
    export EXTERNAL_STORAGE /sdcard


    symlink /system/etc /etc


    mkdir /sdcard
    mkdir /system
    mkdir /data
    mkdir /cache
    mount /tmp /tmp tmpfs


on boot


    ifup lo
    hostname localhost
    domainname localdomain


    class_start default


service ueventd /sbin/ueventd
    critical


service recovery /sbin/recovery


service adbd /sbin/adbd recovery


on property:persist.service.adb.enable=1
    start adbd


on property:persist.service.adb.enable=0
    stop adbd

I'm also going to attempt to see if it's possible to change the adbd settings in the recovery image to see if we can get some leeway there and lower the number of bricked devices, or help fix them (Zach).

I also started reading up on how sbf files work. I want to see if it's possible to build one or REbuild one with somebody's stock system files. It's a slow work in progress, but it's more than we're getting from Moto at the moment. Any and all help is greatly appreciated.

If u can enable adb in the stock recovery and still maintain the motor sign and get it to flash back then we could , in theory, mount the device in recovery and save a lot of peoples bricks tabs

Sent from my Galaxy Nexus using Tapatalk

[Ads]

[HussX]

That was the idea.. I'm still playing around with swapping different parts in the hex editor in what bits of free time I'm getting. This is the heavy work time of the year for me. I may get some chances and downtime while I'm in Cali in June, also. This next week is hell week for me (3 stores a day, 7 days a week).

[fharper2431]

Hi there was just wondering has there been anymore progress on the xyboard and wanted to ty to all the developers the are working on trying to get a custom recovery for it
but i ready to trade it for the 1st xoom or even the transformer prime

[ggrant3876]

Hi there was just wondering has there been anymore progress on the xyboard and wanted to ty to all the developers the are working on trying to get a custom recovery for it
but i ready to trade it for the 1st xoom or even the transformer prime

Welcome to the forum. Glad you decided to join us.

[runandhide05]

Hi there was just wondering has there been anymore progress on the xyboard and wanted to ty to all the developers the are working on trying to get a custom recovery for it
but i ready to trade it for the 1st xoom or even the transformer prime

Trade it (IMO)

Sent from my Galaxy Nexus using Tapatalk 2

[fharper2431]

strongly thinking about it seeing how development seems to be going nowhere for this tablet

[luke.arran]

strongly thinking about it seeing how development seems to be going nowhere for this tablet

£10 that Motorola unlocks the bootloader this year and then development will begin.

[runandhide05]

£10 that Motorola unlocks the bootloader this year and then development will begin.

Well I have already made a deodex from for it... not sure ow much us dollar but I'll take that bet

Sent from my Xoom using Tapatalk

[Elysian893]

£10 that Motorola unlocks the bootloader this year and then development will begin.

Yeah no, especially not the VZW version.

[Jasuramme]

Greetings, guys! HussX, are you still busy with recovery? What I did - when you dump recovery.img you can split it with some perl scripts. And you can assemble it back with scripts. I had success to put it back into /dev/block/*blah blah blah*/recovery by "dd" command. And it works, but... It is only when you don't touch ramdrive. Even if you will gunzip it and gzip it back, you will unable to start this recovery. After that i changed only one random byte in original recovery.img. It gives same error. I made new recovery img with same size that original one. Same story. So, it must be checking hash. That's how i think like. And probably, SHA1 hash, like in update.sh script. What I think. If to put there another one image file with same hash, will we get another error? I wonder, that it should check hash first, if it suits, it will try to unpack file. May be if we will put file with same hash, and not an archive, we will have another error, about package is broken? I'm to tired already today to do this peash. Will try later. Just posted it, if somebody interested to know what is already done here