Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Root request for Ematic EGP008

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Root request for Ematic EGP008

    Has anyone been able to root this tablet? I have tried a few scripts with no success, I know it is the RK3188 chip here is the rest of the info I have found out:

    OS 4.1.1
    CPU Model RK3188 ARM Cortex-A9
    Cores 2
    GPU Renderer Mali-400 MP
    Android SDK Version 16 (Android 4.1.x)
    Kernel Linux version 3.0.8+ (builder@server) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Tue Mar 19

    I have messed with Dans Root Script which connects but does not get the shell id to 0/root and says to kill the script, also tried TPSparkyRoot and Root with Restore, none seem to be able to work, thankfully the tablet still works..

    I will be patiently waiting for any help with this,

    Thanks

    #2
    Root EPG800 Ematic Tablet

    Originally posted by dycast View Post
    Has anyone been able to root this tablet? I have tried a few scripts with no success, I know it is the RK3188 chip here is the rest of the info I have found out:

    OS 4.1.1
    CPU Model RK3188 ARM Cortex-A9
    Cores 2
    GPU Renderer Mali-400 MP
    Android SDK Version 16 (Android 4.1.x)
    Kernel Linux version 3.0.8+ (builder@server) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Tue Mar 19

    I have messed with Dans Root Script which connects but does not get the shell id to 0/root and says to kill the script, also tried TPSparkyRoot and Root with Restore, none seem to be able to work, thankfully the tablet still works..

    I will be patiently waiting for any help with this,

    Thanks
    I'm happy to report I just rooted mine this evening so in order to give back to the community here are the steps (credits to Valentijn Sessink for his original inspiration at http://valentijn.sessink.nl/?p=382 and also to Finless for his tireless work in this area):

    Note: As with any rooting/flashing attempts, there is always risk of things going wrong. If you decide to proceed as follows then you accept these risks and I am not responsible for any related bricked devices, divorces, apocalypse etc

    The following instructions assume you are running a PC with Linux (they will likely work under Windows but I've read these related tools don't always work as expected)

    IMPORTANT: Read these instructions completely before starting – If you are not comfortable working with Linux then I suggest asking a friend who does to help

    1. Install the Android Developer Bridge (adb) – Google how to do this and follow instructions for your platform

    1a. Ensure that the file /etc/udev/rules.d/51-android.rules contains the following entry:
    SUBSYSTEM=="usb", ATTRS{idVendor}=="16d5", MODE="0666"
    then ensure correct permissions are applied with:
    sudo chmod a+r /etc/udev/rules.d/51-android.rules

    1b. Ensure that the file ~/.android/adb_usb.ini contains the following entry:
    0x16d5

    1c. Ensure the file /etc/udev/rules.d/ematic-android.rules contains the following entry:
    SUBSYSTEM=="usb", SYSFS{idVendor}=="16d5", MODE="0666"

    [All the above steps allow adb to properly recognise the device]

    2. Install libusb-1.0-0-dev and compile:
    sudo apt-get install libusb-1.0-0-dev


    3. Obtain rkflashtool from sourceforge (currently version 5.1) – Also download version.h from the same location as the zip file is currently missing this. Put all extracted files and version.h in a directory of your chosing

    4 . Compile rkflashtool from the directory where the files are installed:
    gcc -o rkflashtool rkflashtool.c -lusb-1.0 -O2 -W -Wall -s

    5. Verify table is properly talking to adb by typing 'adb devices' which should show the following:
    List of devices attached
    WAWJMHBTSF device

    6. Boot the tablet into bootloader using by typing 'adb reboot bootloader' (you can probably do this with the reset button too but I don't have a mini HDMI cable to verify if this works)

    7. Ensure you are in the directory where rkflashtool was compiled then display the device parameters by typing the following:
    sudo ./rkflashtool p

    which should return something like (Print this out or direct output to a text file in case you need it later):
    FIRMWARE_VER:4.0.4
    MACHINE_MODEL:EGP008
    MANUFACTURER:RK30SDK
    MAGIC: {hidden}
    ATAG: {hidden}
    MACHINE: 3066
    CHECK_MASK: 0x80
    KERNEL_IMG: 0x60408000
    #RECOVER_KEY: {hidden}
    CMDLINE: console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x 00004000@0x00004000(kernel),0x00008000@0x00008000( boot),0x00008000@0x00010000(recovery),0x000C0000@0 x00018000(backup),0x00106000@0x000D8000(cache),0x0 020A000@0x001DE000(userdata),0x00002000@0x003E8000 (kpanic),0x0020A000@0x003EA000(system),-@0x005F4000(user)

    8. IMPORTANT – If your data after CMDLINE does not match the above then STOP and seek help (you may simply have a different version of hardware but the following instructions assume the above parameters)


    9. Create a directory (below I use stockrom) where you will store your stock images and then backup your system images (boot, kernel, recovery, misc and system) as follows:

    sudo ./rkflashtool r 0x00008000 0x00008000 > ./stockrom/boot.loop

    sudo ./rkflashtool r 0x00004000 0x00004000 > ./stockrom/kernel.loop
    sudo ./rkflashtool r 0x00010000 0x00008000 > ./stockrom/recovery.loop
    sudo ./rkflashtool r 0x00002000 0x00002000 > ./stockrom/misc.loop
    sudo ./rkflashtool r 0x003EA000 0x0020A000 >./stockrom/system.loop
    Note: Keep these files safe! They are the only way to restore factory images

    10. Copy the system rom to a working directory (in this example I use 'customrom)
    cp ./stockrom/system.loop ./customrom

    11. Mount the system rom filesystem as follows:
    sudo mount -o loop ./customrom/system.loop /mnt

    12. Download the su and superuser.apk files (I got these from http://hosted.androidsu.com/superuser/ where I extracted from the download http://downloads.androidsu.com/super...arm-signed.zip )

    13. Copy the extracted files to your custom rom filesystem as follows (I'm assuming ~/Download as the location for the files to copy from):
    cd /mnt/app
    cp ~/Download/Superuser.apk /mnt/app
    cp ~/Download/su.arm /mnt/bin/su


    14. IMPORTANT: Change the permissions for su to be executable as follows:
    sudo chmod 6675 /mnt/bin/su

    15. Unmount the custom rom filesystem with 'sudo umount /mnt'

    16 WARNING – This is point of no return – Flash the image as follows:
    sudo ./rkflashtool w 0x00354000 0x00100000 < ./customrom/system.loop

    17. Reboot the tablet with 'sudo ./rkflashtool b'

    Enjoy rooted goodness

    -= Equinoxe =-
    Last edited by equinoxe; 01-21-2014, 00:49. Reason: Added a couple of extra steps

    Comment


      #3
      important note to the above: The actual system flash command should be as below (sorry for the error!)

      sudo ./rkflashtool w 0x003EA000 0x0020A000 >./customrom/system.loop

      Comment

      Working...
      X