Rooting device ASUS MeMO Pad 7
Some information [MeMOPad] ME572C of
Talk about the boring part:
Intel Z3560 / Z3580’s CPU, boot.img / fastboot.img / recovery.img of HEAD_PADDING back UNKNOWN_SIZE is 728 bytes, but BOOTSTUBSTACK_SIZE is 8192 bytes.
RootZenFone change it to use, and then release a small update late.
Inside sideload recovery is bad, adb port can not open, when to get there to do a software update or not repaired, guess should not want people to use it? fastboot there SD Download, it seems the future of factory image will be .raw format.
The more interesting part:
fastboot there is a small back door, can be used to do the root of the application:
fastboot oem mount
The first instruction is to mount partitions on the phone, will be mounted at / mnt / data folder, so I’m going to mount the system is ext4 fastboot oem Mount system , that is, you want to mount userdata fastboot oem mount data ext4 can.
The second instruction is to update the information on the phone route, originally only update existing files , but here I do not know why is modified to replace the existing file or upload , it is very interesting, root application ready. Because it is 4.4 and there is open SELinux, so the best way to modify the existing shell file will be executed, when it related to root after the brush into the program to reboot automatically go into.
The idea is simple:
fastboot oem Mount system ext4
fastboot Flash / mnt / system / xbin / su su
Flash /mnt/system/etc/install-recovery.sh install-recovery.sh fastboot
fastboot Flash /mnt/system/Superuser.apk Superuser.apk
Then find a .sh file can be used to modify the plug plug back in the boot judgment if no /system/etc/.installed_su_daemon run the installation program, produced /system/bin/.ext/ , / system / bin /. ext / su , / system / xbin / sugote , / system / xbin / sugote-mksh , / system / xbin / daemonsu …