Database Develop

[INFO] The Atrix sbf thread

Single Binary Format
Hi,
I thought I would start this thread so that all info about sbf utilities and formats specific to the Motorola Atrix could be in one place. (Kenneth Penn's idea) I don't know everything, not a lot, barely anything really, but I will share what I do. Feel free to chime in and correct anything I say.
First off, the software I have found:
Welcome to 2008, Portable SBF Tool / desbf
Motorola android SBF [de]Packer
SBF recalc (waiting for 1.3 edition)
Of these utilities, the one that has done anything worthwhile for me is Desbf. SBF recalc keeps saying wait for version 1.3, and while sbf depacker has been updated for the Atrix, I haven't managed to sucessfully flash anything with it, it has the most promise though and hope for the future.
First, trying these utils is like walking into a shop in chinatown looking to buy a cheeseburger. Where am I? What do I do? How do you say "do something!"?
Desbf, I don't know the history behind this or what it has been used for in the past, it was on a list of google hits for the obscure motorola sbf format. You run it, select a sbf file, and it automatically creates a folder with all the files contained in the sbf extracted. You can delete files and then save an sbf that can be flashed. It has a parse CG button, don't know what it's for. It has been used to flash the Telstra radio onto Att and Bell. I have yet to use it to flash something using RDL3, just the radio using RDL1.
SBF Recalc, shows a lot of information, to use you split the file to a folder to start, do your thing with the files in that folder, and then open the folder to recalc checksum and save an sbf. Only problem is that is doesn't work (yet).
Motorola Android [De]packer is obviously the most in depth util, it shows even more information than SBF recalc. It does do things, not sure what, or if it's my lack of understanding of the format, but I haven't sucessfully done anything with it, it creates files, displays information, but complains about RDL files not being needed for the content, even if you delete all the RDL files.
Speaking of files, here is what I understand about them:
The utilities spit out SMG files, it's a motorola format, not sure of the acronym.
RDL1:
RDL3:
Ram downloader 1 is used for the radio, it is flashed after everything else, changing mode to do so, everything else is flashed using Ram downloader 3. I don't know what happened to RDL2.
CG2 22KB
CG3 512KB, CDT.bin
CG5 is the radio, plus other things apparently. In [De]Packer it's a virtual collection of mbn files, partition.mbn, amas_sec.mbn (the radio), osb1_sec.mbn, cefs.mbn, db1_sec.mbn. I have no idea what they are about. I know they are from CG5 because an sbf with just RDL1, RDL3, and CG5 spits out RDL1, RDL3, and the above without a CG5.
CG42 3072KB mostly zeros, ends at 0xff0
CG44 3072KB Bootloader
CG47 262144 Microboot (Engine and Slot for hashing in microboot priv.c) (ref to rdl1.bin, ptable, CDT.BIN, BCT.bin, PT.bin, EBT.bin, MBR.bin, EBB.bin)
CG50 is 2KB of 0xFF, no content, probably used to clear a partition
CG52 same as above, (sent to mmcblk0p7 to clear misc? -optionally used to pass commands to recovery, it fed with command line for example to flash an update -)
CG53 1014KB begins with SOL: logo.bin (mmcblk0p8)
CG54 2KB of 0xFF (possibly sent to mmcblk0p9, Kernel Panic Data)
CG55 recovery (header, ramdisk, kernel) (mmcblk0p10)
CG56 boot (header, ramdisk (/), kernel) (mmcblk0p11)
CG57 is the system image in ext3 linux format. (mmcblk0p12)
CG58 osh (webtop) system image in ext3 (mmcblk0p13)
CG59 20MB HFS, CDROM (Motorola Helper) (mmcblk0p14)
CG60 2KB of 0xFF (possibly sent to mmcblk0p15 to clear cache image)
CG61 2KB of 0xFF (sent to mmcblk0p16 to clear userdata image, tested)
CG62 preinstall image in ext3 (mmcblk0p17)
This is a work in progress.
New for Gingerbread 2.3.4:
CG39 looks like fs, pds update?
CG42 bootloader
CG47 same as before, just full partition size
CG56 boot logo
CG58 Recovery emmc image (kernel, ramdisk.gz)
CG59 Boot emmc image
CG60 system image APP
CG61 webtop image OSH
CG62 cdrom image motohelper
CG65 preinstall image
Code:
cat /proc/partitions
major minor #blocks name
7 0 7308 loop0
7 1 4190 loop1
179 0 15668736 mmcblk0
179 1 3584 mmcblk0p1
179 2 512 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 327680 mmcblk0p12
179 13 786432 mmcblk0p13
179 14 20480 mmcblk0p14
179 15 655360 mmcblk0p15
179 16 2097152 mmcblk0p16
179 17 353280 mmcblk0p17
179 18 11233792 mmcblk0p18
179 32 1931264 mmcblk1 (external sd card, 2 GB)
179 33 1930680 mmcblk1p1 (external sd card, 2 GB)
254 0 7308 dm-0
254 1 4189 dm-1
LINKS: (to be integrated)
http://forum.xda-developers.com/show...&postcount=502
http://and-developers.com/partitions:cdt
https://www.droid-developers.org/wiki/BootRecoverySignature
Cheers!

Heres a detailed list of the partitions:
http://forum.xda-developers.com/showpost.php?p=12687720&postcount=502

This is awesome. Thanks for the details.

Thanks,
I am thinking it might be possible to create an sbf from a dump of the partitions on a active phone. It would certainly be nice to have one for Bell. My idea is to replace all the active bits in an sbf file with versions from a dd dump of each partition. [De]Packer could possibly be used to compile a CG5 from all the bits, take that file and use Desbf to create the rest of it.
So if someone with a stock Bell Atrix could run this and post a link back with the resulting 7zip file it would help. Mediafire or some other file hosting service.
backup creator script
What it does is dump all the "other" partitions, not system or data, or webtop, but all the little ones up to 11 and 14
Cheers!

NFHimself said:
Thanks,
I am thinking it might be possible to create an sbf from a dump of the partitions on a active phone. It would certainly be nice to have one for Bell. My idea is to replace all the active bits in an sbf file with versions from a dd dump of each partition. [De]Packer could possibly be used to compile a CG5 from all the bits, take that file and use Desbf to create the rest of it.
So if someone with a stock Bell Atrix could run this and post a link back with the resulting 7zip file it would help. Mediafire or some other file hosting service.
backup creator script
What it does is dump all the "other" partitions, not system or data, or webtop, but all the little ones up to 11 and 14 15 16.
Cheers!
Click to expand...
Click to collapse
That would be a massive development for Bell users.

I have confirmed that removing CG61 causes a flash to not erase your userdata partition.
Cheers!

Great news! Keep us updated.

NFHimself said:
I have confirmed that removing CG61 causes a flash to not erase your userdata partition.
Cheers!
Click to expand...
Click to collapse
hey, how hard do you think it would be to modify the 1.2.6 SBF to also not wipe the user partition? Would it act like the 1.8.3 SBF which preserves all user settings and apps? Conversely, could we modify the 1.8.3 SBF to act like the 1.2.6 SBF by clearing all the settings out and returning completely back to stock? Sorry for all of the questions, but I just found the 1.8.3 SBF very cool, that it let me keep all my settings and apps, and thus cut down on the time I needed to spend on restoring things after the flash.

UncleCemka said:
hey, how hard do you think it would be to modify the 1.2.6 SBF to also not wipe the user partition?
Click to expand...
Click to collapse
Probably as easy as pulling CG61 out, if I recall correctly (pretty easy...)
EDIT: haha I see NFHimself confirmed this... that's the one .8.3 is missing (besides CG51 --ideas?)

That's all I did, selected CG61, hit delete, save in desbf, and run rsdlite.
Only thing about it is that Gingerbreak will still wipe your internal memory so you still have to backup that.

The error in [de]packer, where it says source not found, seems to be limited to cg3.smb, remove that and it compiles the folder.
Cheers!

Update on creating a Bell sbf:
Of the partitions 1-11, and 14, the ones with unique content are 3, 5, 9, 10, 11. Of these, 10 and 11 are straight dumps in the sbf file, the recovery and boot partitions, the partitions 3, 5, and 9 have no direct correlation to a CG that I can see so far.
However, I have managed to go from a Telstra firmware to a stock Bell firmware, just not using a sbf. I simply did a dd of all Bell partitions from sdcard to the phone, leaving mmcblk0p12 for last since it's the system partition. Well most of the partitions, I didn't dd internal memory or data, I just did a data wipe. So, you can go back to stock, you just can't recover from a bricked situation, using this method.
Cheers!

NFHimself said:
Update on creating a Bell sbf:
Of the partitions 1-11, and 14, the ones with unique content are 3, 5, 9, 10, 11. Of these, 10 and 11 are straight dumps in the sbf file, the recovery and boot partitions, the partitions 3, 5, and 9 have no direct correlation to a CG that I can see so far.
However, I have managed to go from a Telstra firmware to a stock Bell firmware, just not using a sbf. I simply did a dd of all Bell partitions from sdcard to the phone, leaving mmcblk0p12 for last since it's the system partition. Well most of the partitions, I didn't dd internal memory or data, I just did a data wipe. So, you can go back to stock, you just can't recover from a bricked situation, using this method.
Cheers!
Click to expand...
Click to collapse
that's great news and I hope that if an update comes out and Bell users aren't necessarily able to update that you might refine this method into an automated process or at least detail it for the rest of the community's benefit.

Wow. Great work NFHimself! That's the only reason I haven't taken Telstra for a spin. There's no going back......yet.
Sent from my rooted and frozen Motorola Olympus.

Well it was literally "dd if=sdcard/mmcblk0p1 of=/dev/block/mmcblk0p1" skipping 12 and continuing on, then doing 12. I did run setprop tcmd.suspend 2 first, and I was rooted, have to pull the battery to reboot since I overwrote the system partition and had no commands in my path, but that's it.
Just would need some online hosting space and do up a simple script, really.
Cheers!

NFHimself said:
Well it was literally "dd if=sdcard/mmcblk0p1 of=/dev/block/mmcblk0p1" skipping 12 and continuing on, then doing 12. I did run setprop tcmd.suspend 2 first, and I was rooted, have to pull the battery to reboot since I overwrote the system partition and had no commands in my path, but that's it.
Just would need some online hosting space and do up a simple script, really.
Cheers!
Click to expand...
Click to collapse
That is really ballsy. I will not write to my mmcblk0p1 because if there is the slightest error I believe I'd have a have a hard brick. All the options seen when holding power + volume-down (or up) can be found in that block device.
But this is not the case for Bell/Telstra?! Fascinating that your devices are different! Where *DOES* your bootloader live?
Actually, I now see that most the Telstra CG img files are signed by two keys, but almost all of the AT&T ones are signed by 3, and the keys differ between the two .sbfs (but are consistent within each.) How very strange. Our CG44s are very similar, but also different (for example do a diff on their strings):
Only in Telstra (1.4.2):
Code:
< UpdateBootBct
< BL size:%d
< MB size:%d
< NvMotBlReSign
< NvMotBctReSign End

I went through each one with hexedit, and nothing really struck me as being the bootloader, in fact, on my archos tablet, the bootloader was not stored in the mtd list at all, it was somewhere else, probably in the SOC somewhere.
Our partition 1 is all 0xFF, no danger there, either it's protected and can't be read or written to, or it really is 0xFF.
Cheers!

Oh, a dump of all the important Bell mtd partitions is available.
Bell_Full_Partition_Backup.tar.gz
Cheers!

Thanks! Yes, I suspect now that the OTA writes the mmcblk0p1 and that this is the location the new bootloader is updated from (on next boot?) and that RSD can simply skip this step and update directly. Just got an mmcblk0p1 from someone who never had an OTA (on ATT) and it is like yours "FF 00 00 00 FF: and then 3.5mb of FFs =) So, you were probably safe to overwrite it!
Will be interesting to confirm once you have your first OTA =) As for "SE" (Secured Engineering?) I don't know the difference to NS yet. Perhaps its related to the bootloader and certificate differences too.

Does anyone have much experience tinkering around with the PDS.bin file? There's reason to suspect that corruption in the mmcblk0p3 block occurs when the Internal SD is formatted and partitioned erroneously via custom recovery. this could be what causes the bottom of the touchscreen to become unresponsive for the bottom half inch of the screen (causes "ghosting" or misaligned touch response above the impacted area)
Tenfar advised me to properly format and partition mmcblk0p18 with the following command (#newfs_msdos -F 32 -S 512 -L MB860 -c 64 -u 16 /dev/block/mmcblk0p18) which did everything okay, but didn't make an impact unfortunately. Still tinkering around with this buggered AT&T Atrix for the last few weeks. Determined to fix this bish instead of sending it in lol

[Q] G1: Restore from a backup without recovery mode?.

I have a G1 htc dream (european variant = rogers 32a), and I'm slowly losing out. The thing is on CM-6.0, it never had enough memory, and eventually crashed it's way into a mess, and I'm pondering the next move.
What works: All phone features, root terminal, fastboot (r2d2s on skateboards), some programs. I can read/write the sdcards independently. I even have access with the old version of adb. It boots, & reboots.
I have a nandroid backup from late last year on the sdcard, which would do very nicely thank you if I could get it installed. Is there any way to install the backup without access to recovery mode? How are those image files cobbled together?
What doesn't work:
1. Recovery Mode(?) turn-on-with-home-pressed. I can't get off the (opening) blue screen. Remove the battery to restart.
2. /etc/fstab & /etc/mtab are no longer there :-/. /proc/mounts is. I don't know what else is missing, but it implies some essential daemon is awol. Amazingly it writes to the sdcard :-//.
3. Market - It says "starting download....." but it doesn't:-(
4. Memory control. I can start with a bit free, but as uptime continues, the memory vanishes, and anything you open crashes.
I do have linux, and a root terminal on the phone. But without /etc/fstab, all those crazy android device names are not to be seen :-//. ls /dev/block shows me loop0 - loop7; mmcblk0, mmcblk0p1 - mmcblk0p3; mtdblock0 - mtdblock5; vold.

If you have fastboot and a nandroid, you can flash all images separately, i.e.
fastboot flash system <system.img>
fastboot flash userdata <data.img>
...
In the Cyanogenmod Wiki you can find probably some additional hints
With fastboot you can also flash a new recovery ...

AndDiSa said:
If you have fastboot and a nandroid, you can flash all images separately, i.e.
fastboot flash system <system.img>
fastboot flash userdata <data.img>
...
In the Cyanogenmod Wiki you can find probably some additional hints
With fastboot you can also flash a new recovery ...
Click to expand...
Click to collapse
Thanks for the reply.
Image on pc, and fastboot on pc? I'll try that.
Ok. Not out of the woods, but I've made some progress. The obstacle is: recovery isn't mounted, and I only have /proc/mounts. In /dev/block
mtdblock3 is mounted on /system
mtdblock4 is mounted on /cache
mtdblock5 is mounted on /system/xbin
There is mtdblock 0-5. Where the $£%@! is recovery supposed to be mounted? what about the other ones? anyone got an /etc/fstab from a G1??
Actually, I probably have but it's archived. I had figured this on the android by using adb and dump_image, but that's restoring a system while it's running, and there should be laws against that sort of thing.

??? ... recovery is never mounted, it's like a second "mini" os.
Additionally: for using fastboot your phone must be in fastboot mode, i.e. boot with back+power. I suggest you to first read a bit more about fastboot, g1 partitions, etc. ...
Sent from my Gingerbread on Dream using XDA App

That worked after a fashion. I had the backup: system.img, boot.img, cache.img, recovery.img, data.img, & misc.img. Of these, I could flash recovery, cache, system, & boot. The data.img & misc.img threw errors, (me)not knowing where they should be put.
It wasn't enough. I had a trail of processes bailing out and a repeated crash in acore typical of memory being clogged. But I got back recovery mode, and I could apply the latest backup normally. I'm now back to the moments after my successful install of CM-6.0 - before I started civilising it. And I don't really have the ram for it.
Good good good, thank you very much. As I don't have the ram, I'll have to add swap, which I have my sdcard set up for. It's certainly less pain than looking for a lower level rom and going to a smaller OS.
I do have one hitch: I've lost root in the xterm (and I don't know where else).
$ su
permission denied
$
:-O?
EDIT:: I'm a twit. I forgot to run the fix_permissions script. Didn't know I backed up _THAT_ promptly. Permissions were AWOL. So are a few apps, but nothing I'm worried about. Now

[SOLVED] Checking uImage... Invalid Size, boot ArchLinuxARM

Checking uImage... Invalid Size
During Arch Linux boot...
I've CM9 and webOS 3.0.5, working fine...
Before Arch, I tested Bodhi, and it worked..
I searched about this in moboot, arch linux arm forum... I only found people talking about this problem in android, but it wasn't very conclusive...
I want to test Arch, because is my desktop distro...
Thanks, for all the info I get from this forum!

if your boot doesnt have enough space for a complete boot image, no matter what OS you are trying, it will fail.
Make sure there are no traces of other images (like Bodhi) or your /boot

I've only 4MB of free space on /boot.
I asked in this post if my /boot list files is normal...
There is another thing, when I created the partition for Arch, I had Bodhi... so I did this:
Code:
lvrename /dev/mapper/store-ext3fs /dev/store/arch-root
mkfs.ext3 /dev/store/arch-root
Then, I mounted the new partition and extracted Arch...

dubidu said:
if your boot doesnt have enough space for a complete boot image, no matter what OS you are trying, it will fail.
Make sure there are no traces of other images (like Bodhi) or your /boot
Click to expand...
Click to collapse
Very thanks!
Problem solved and it was very simple. Only today I had time to try to solve this since my post...
Solution: uImage.ArchLinuxARM was corrupted! (download it again)
Before:
Code:
-rw-r--r-- 1 root root 4472832 Feb 5 01:51 uImage.ArchLinuxARM
Now:
Code:
-rw-r--r-- 1 root root 4852245 Feb 12 11:44 uImage.ArchLinuxARM
md5sum is always good in this situations!
Pay attention, when using curl, if there's some error message during download. If there isn't enough space in /boot, curl can't preform correctly, it download but not the integral file...

[Q] Developer Help!!! with pushing cwm in adb

ok, long story short i have a problem. i've tried several methods of installing cwm until i found the link below.
i followed instructions on http://forum.xda-developers.com/showthread.php?t=1121952
it says get help if md5sum doesnt match, well it doesnt. here is what i got:
# busybox md5sum /dev/block/mmcblk0p14
efeebdda98ec1d7fb2ad83d23f0713bf /dev/block/mmcblk0p14
#
then i followed what the post showed later... and now i have gotten this
./adb shell busybox md5sum /sdcard/recovery-cwm-pr1.img
a1c61d06fa0f029411cf4cde44639b3f /sdcard/recovery-cwm-pr1.img
and tried to boot into CWM, but my phone when i confirmed my phone wiped and did not load CWM and instead completed a factory reset and wiped everything. i made backup .img's in adb previous to this, not sure how to use them though.

anybody able to help?

ok, apparently some things are still on my phone. i still have root and superuser was still installed on my phone. but all my other apps were gone. luckily i also used titanium backup to make backups so i'm using that to restore some things.

Wait!!! maybe solved, after restoring backups i ran step 7 again...
and then...
# busybox md5sum /dev/block/mmcblk0p14
a1c61d06fa0f029411cf4cde44639b3f /dev/block/mmcblk0p14
well, here goes nothing. nope, still no cwm and phone factory reset yet again. thank goodness i have a backup. i'm pretty sure i'll never get cwm working at this rate.

Hey I need some help and was wondering if I have a new phone zv4 software can I flash the zv8 tot file or do I have to step this up zv6, then zv7 , and then zv8 to get to zv9? Don't want to mess up this new phone. I appreciate anyone who knows. I have use the tot file method but went from zv7 to zv8 on my other phone.

yes you can, done it several times
---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------
arcane spade said:
Wait!!! maybe solved, after restoring backups i ran step 7 again...
and then...
# busybox md5sum /dev/block/mmcblk0p14
a1c61d06fa0f029411cf4cde44639b3f /dev/block/mmcblk0p14
well, here goes nothing. nope, still no cwm and phone factory reset yet again. thank goodness i have a backup. i'm pretty sure i'll never get cwm working at this rate.
Click to expand...
Click to collapse
If you havent got it by now i can upload just Cwm once you root with superone click you can then easily push cwm through adb

Highlimit, thanks for your reply. I know there must be something I'm overlooking or something. I have root access for sure. I have root programs running and root checker verified. The scripts in my first post are from my phone, as you can see by the # I have SU when shell'd in through adb. I also have CWM and it is on my sd card. Below is the output when I run md5sum in adb shell and I can see the file in root explorer.
./adb shell busybox md5sum /sdcard/recovery-cwm-pr1.img
a1c61d06fa0f029411cf4cde44639b3f /sdcard/recovery-cwm-pr1.img
Apparently my problem is related to /system/etc/install-recovery.sh
i read this thread http://forum.xda-developers.com/showthread.php?t=1594099
but i'm confused. should i just delete that file? is there a step to mounting CWM that I am missing from thecubed's thread http://forum.xda-developers.com/show....php?t=1121952
I dont really understand the part about install-recovery.sh so i'm afraid to just delete it.
Also, I have stock ZV9 on my phone right now.

got it! booted into CWM. pushed over broken out and flashed. sweet!
I had CWM in the wrong place, installed correctly now.

[Q] How to root Asus Memo Pad 7 (me572c) 2014 version

I just bought ASUS Memo Pad 7 (ME572C)
but I can't find root message for google
It android kitkat 4.4.2
please help me~
thanks

woff said:
I just bought ASUS Memo Pad 7 (ME572C)
but I can't find root message for google
It android kitkat 4.4.2
please help me~
thanks
Click to expand...
Click to collapse
You're gonna have to wait for a while. It hasn't yet reached general availability. Currently I can only find it for sale on John Lewis in the UK. And they brag about it being exclusive to them.

I just got it at Best Buy, so they're out and available and just waiting to be rooted...

Im also thinking of getting this new Asus Memo 7. Is this new intel chipset rootable?

I just found this for it.
http://www.xxxxxxxxxxxxxxxxxxxxx
Don't know if it's real or not.
Moderator Edit: No it isn't - now obfuscated.

I am also the happy owner of an ASUS Memo Pad 7 (ME572C).
Before this one I had the Nexus 7 (2012), a great tablet. But it broke and I bought the ME572C, which is a kind of up upgraded nexus.
Also waiting for a way to root it, to use all the possibilities of this quick processor.
The link in the mesagge before looks like spam to me.
Anybody any idea when someone will find the way to root it??

I just got an Asus ME572C, I wanted the Nexus 7 (2013) but it was not in stock. And I have to say, that despite is not Google stock, this tablet is a kick ass device.
So I hope and it would be nice, to add a forum for this great tablet and see some development. I think is a great device to work on.
I dont have much time but I will try to do some stuff with It. O if someone do something and want people to test it. Here I'm

I search a way to root this beautiful tablet..... the processor 64 bits is the thing which is difficult to root ?
I'm surprise that dolphin don't run on.

found this, but I haven't try anything yet
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 <partition> <fs type>
The first instruction is to mount partitions on the phone, will be mounted at / mnt / <partition> 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.
fastboot flash <path_to_phone> <path_on_local>
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 ...
Packaged on a free, self-interested hands.
-----------------------------------------------------------

gabriel-arg said:
found this, but I haven't try anything yet
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 <partition> <fs type>
The first instruction is to mount partitions on the phone, will be mounted at / mnt / <partition> 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.
fastboot flash <path_to_phone> <path_on_local>
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 ...
Packaged on a free, self-interested hands.
-----------------------------------------------------------
Click to expand...
Click to collapse
thank you
I try it !

woff said:
thank you
I try it !
Click to expand...
Click to collapse
Please send some feedback about how it did go!!
---------- Post added at 06:33 PM ---------- Previous post was at 06:25 PM ----------
and have someone tried NFC on this tablet?
according to all web sites it has NFC, but I cant find any setting about NFC on the tablet.

Did anyone try rooting this device with the rooting tool of Asus Zenfone 5? I think I may work. Currently I don't have this device. I will buy it the next 2 days.

I tried the asus zefone 5 root apk but it says that is only for zenfone....

Root) http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
http://www.asuszenfoneblog.com/2014/10/download-rootzenfone-1464r-apk.html

Thanks a lot it works great

How does this work? Just download and install the apk?

Hello scritchs,
Good to hear it worked for you.
Wondering if it will also work for me...
You just downloaded the RootZenFone 1.4.6.6r, installed the apk and it is rooted now?
I like to know if ours ME572C have the same specs:
Modelnumber K007
Buildnr KVT49L.WW etc
Android 4.4.2
thanks

thanks a lot
I try it~

woff said:
thanks a lot
I try it~
Click to expand...
Click to collapse
Yes i get the apk and its automatic the tab reboot and the root is on.....
This tab is great.... nothing to say
---------- Post added at 09:25 AM ---------- Previous post was at 09:17 AM ----------
I get the apk from the first link 1.4.6.r.6 from asus webstorage all works fine. Thanks again

How about a custom rom to remove the asus bloatware and return to the pure stock android?