The part I dont get is that, the only available recovery option is through SDcard reader, but xyboard does not have a SDcard reader slot. So how is the recovery supposed to work?
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; The part I dont get is that, the only available recovery option is through SDcard reader, but xyboard does not have a SDcard reader slot. ...
The part I dont get is that, the only available recovery option is through SDcard reader, but xyboard does not have a SDcard reader slot. So how is the recovery supposed to work?
Same way all the devices with not sdcard, your internal sdcard is not acyauly at /sdcard its normally at /data/media.
If u look at the sdcard location on root explore u can see that its actually a system link which to put understandably its kinda like a windows shortcut
Sent from my Galaxy Nexus using Tapatalk 2
Is that even possible?
I mean, hash isn't an encryption, you have to try different combinations of bytes and even then, what if it's not only checking the hash, but also the file size?
You have to build a file with same size, a working script and same hash, which is impossible in my eyes.
Greetings
SGS-IV-Stock_Rooted
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
Yes, I know. I think there should be some way to fake hash. I mean even file without any usefull information. But probably there no any utils to do that. It's kinda stupid job.
But I found something interesting on XDA developers.
Thats a thread [HOW-TO] Boot Debian with X11 and wifi from SD card. (Not chroot!) - xda-developers
the '-c' flag specifies arguments to pass to the kernel for boot.
This is probably the bare minimum.
Format is "fastboot -c 'kernelcmdline' boot zImage"we probably can use this trick to load citom ramdisk through fastboot. And if we will do recovery ramdisk and boot it like that, maybe we can update recovery with new onefastboot -c 'root=/dev/mmcblk0p2 rw rootfs=ext2 init=/sbin/init rootwait noinitrd' boot zImage
I will try to do it later.I think thats at least something
Hello Jasuramme.
Did you try it?
I am very curious!!
HAve a nice day!
I'm curious if the device is using an MD5 hash or some other type? MD5 apparently has a flaw where you can create files that have the same hash yet do completely different things. I was reading about it here:
Peter Selinger: MD5 Collision Demo
Unfortunately this type of thing is above my paygrade.
I'm still in the game. Just slow progress on my end. I'm leaving for a month in California in the morning, so I'm hoping I get some downtime there. Ive split and rebuilt the recovery like you said, but matching the hash and sigs... That's where the hex editing came in. I've not had any luck yet. Slow work, but I'm determined.
Sent from my MZ617 using Tapatalk 2