Or Continue to Thread: [Q] Root Creative ZiiO 7"…
Find Your Device:
23rd July 2011, 01:03 AM   |  #5  
Junior Member
Thanks Meter: 18
 
8 posts
Join Date:Joined: Jul 2009
Solution
Just finished rooting this damn thing and it wasn't the easiest thing to figure out.
I used a 2 stage process.

Stage 1 (run superoneclick using the psneuter option until it fails)
If you're familiar with this skip to stage 2
  1. get the adb driver from here
  2. configure it to see the ziio using these instructions
  3. get SuperOneClick from here
  4. run it with psneuter root option selected until it stops and says FAILED

Explenation:
The ADB driver is needed for interacting with the tablet in a command line.
SuperOneClick comes with all you need to crack this baby. It loads the psneuter app which gives you temporary shell root and loads busybox on which is an app everybody and their grandmother uses.

Stage 2 (finishing what superoneclick can't)
  1. Go to superoneclick's folder then in the Root folder you find there
  2. Copy the su-v3 file to the adb folder (situated in Program Files/Android/android-sdk/platform-tools
  3. Rename it to simply su
  4. Start cmd and navigate to the adb folder
  5. Use the following commands:
    Code:
    adb push su /sbin
    adb install Superuser.apk
    adb shell
    chmod 4755 /sbin/su
    rm /data/busybox/su
    cp /data/local/tmp/busybox /data/busybox/busybox
    chmod 4755 /data/busybox/busybox
    exit
    adb pull /system/ziilabs/init.rc
  6. Open the new file in the adb folder named init.rc
  7. Edit it and change the line
    Code:
    mount ext4 /dev/block/mmcblk_data1 /data nosuid nodev noatime nodiratime
    with
    Code:
    mount ext4 /dev/block/mmcblk_data1 /data nodev noatime nodiratime
  8. Save the file
  9. Push it back to the ziio using
    Code:
    adb push init.rc /system/ziilabs/init.rc
  10. Reboot the tablet and you should have root

Explanations:
SuperOneClick fails because it expects normal android file locations, which the ziio doesn't uses (probably to make it harder to root). All the files that are normally held in sbin apear to be in /data/busybox (weird). You have to delete the original su app, load the new su app in the /sbin directory where the superuser apk expects it to be, move the busybox application to the folder where the ziio has it's internal apps and allow it's use.

Thanks to CLShortFuse for superoneclick, to toolzz whose information gathering started me on this trail and thanks to mrrooty whose post here helped me figure out which su version I was suposed to use.
The Following 16 Users Say Thank You to linkerro For This Useful Post: [ View ]