Recovery

[nchantmnt]

Btw does you guys have a real recovery with menu because when i tried to boot mine into recovery it just showed an android construction logo and no menu. There it sits till it reboots after some minutes. Can post a screen tonight.

Gesendet von meinem MB860

[Ads]

[runandhide05]

Btw does you guys have a real recovery with menu because when i tried to boot mine into recovery it just showed an android construction logo and no menu. There it sits till it reboots after some minutes. Can post a screen tonight.

Gesendet von meinem MB860

Once in recovery press power or a volume key and the options will pop up

Sent from my Galaxy Nexus using Tapatalk

[nchantmnt]

Ok thanks. Will check that tonight. Seemed not to be working last time i tried as i was stuck in bootloop.

Gesendet von meinem MB860

[HussX]

New idea, although it could be a bit outlandish. Dan's root method keeps everything from resetting on a reboot using an exploit on the Xyboard, right? I wonder if it would be possible to pull apart his script, see what "xyz" uses, and use that to our advantage?


Sent from my XB10.1

[luke.arran]

New idea, although it could be a bit outlandish. Dan's root method keeps everything from resetting on a reboot using an exploit on the Xyboard, right? I wonder if it would be possible to pull apart his script, see what "xyz" uses, and use that to our advantage?


Sent from my XB10.1

Is the any files which you want from my Xoom 2 which will help you?

[runandhide05]

Is the any files which you want from my Xoom 2 which will help you?

Which model do u have?

Sent from my Galaxy Nexus using Tapatalk

[luke.arran]

Xoom 2 - mz615 :-)

[runandhide05]

Xoom 2 - mz615 :-)

Rooted right?
Can u look at your /proc/partitions and tell me your recovery mmc block
Is that the wifi only?
Can u do this in terminal or shell from PC and upload the img that it creates on sdcard
dd if=/dev/block/mmcblk1p12 of=/sdcard/recovery.img
Sent from my Galaxy Nexus using Tapatalk

[luke.arran]

Hello and sorry for the late reply been a wee bit busy. Yes I'm rooted! And here are the block things -
And the recovery file is here -
http://db.tt/VjvRguLN

$ export PATH=/data/local/bin:$PATH
$ su
#  fdisk -l /dev/block/mmcblk1p1
 Disk /dev/block/mmcblk1p1: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p1 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p2
 Disk /dev/block/mmcblk1p2: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p2 doesn't contain a valid partition table
#  fdisk -l /dev/block/mmcblk1p3
 Disk /dev/block/mmcblk1p3: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p3 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p4
 Disk /dev/block/mmcblk1p4: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p4 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p5
 Disk /dev/block/mmcblk1p5: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p5 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p6
 Disk /dev/block/mmcblk1p6: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p6 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p7
 Disk /dev/block/mmcblk1p7: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p7 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p8
 Disk /dev/block/mmcblk1p8: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p8 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p9
 Disk /dev/block/mmcblk1p9: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p9 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p10
 Disk /dev/block/mmcblk1p10: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p10 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p11
 Disk /dev/block/mmcblk1p11: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p11 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p12
 Disk /dev/block/mmcblk1p12: 9 MB, 9437184 bytes
4 heads, 16 sectors/track, 288 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p12 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p13
 Disk /dev/block/mmcblk1p13: 222 MB, 222298112 bytes
4 heads, 16 sectors/track, 6784 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p13 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p14
 Disk /dev/block/mmcblk1p14: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p14 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p15
 Disk /dev/block/mmcblk1p15: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p15 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p16
 Disk /dev/block/mmcblk1p16: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p16 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p17
 Disk /dev/block/mmcblk1p17: 629 MB, 629145600 bytes
4 heads, 16 sectors/track, 19200 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p17 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p18
 Disk /dev/block/mmcblk1p18: 1004 MB, 1004535808 bytes
4 heads, 16 sectors/track, 30656 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p18 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p19
 Disk /dev/block/mmcblk1p19: 734 MB, 734003200 bytes
4 heads, 16 sectors/track, 22400 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p19 doesn't contain a valid partition table

#  fdisk -l /dev/block/mmcblk1p20
 Disk /dev/block/mmcblk1p20: 13.2 GB, 13270777856 bytes
4 heads, 16 sectors/track, 404992 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
 Disk /dev/block/mmcblk1p20 doesn't contain a valid partition table

#

[HussX]

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.