If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed.
This is a discussion on Recovery within the Motorola XYBoard Development forums, part of the Motorola XYBoard Forum category; Originally Posted by HussX So I've started going a little more hardball now. Using the clockwordmod recovery image I had created from the boot and ...
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).
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
Nexus 4 - CyanMod 10.1
SGS-II - Rooted - Jedi Mind Trick VX3
Samsung Note II - Jedi Master 13
Motorola Xoom - WiFi - Rooted - EOS 4.2.1 Nightlies
strongly thinking about it seeing how development seems to be going nowhere for this tablet
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