bq Edison ICS – Root (on any operating system)

Hello everyone,

 

I have a new website, which is now at http://joaoventura.net/
All articles which were in this blog are now located at http://joaoventura.net/blog/

Please use of the links above to navigate to my new location!

 

Thanks,
João Ventura

6 Responses to “bq Edison ICS – Root (on any operating system)”

  1. gianluca Says:

    Thank you very much! My tablet Nextway E9 is rooted now!

    • Do Tien Anh Says:

      Hi. I have a E9 tablet but i can’t find drive to connect it and pc (win7). May you help me?!

  2. jose Says:

    Hi, I have a Bq Edison tablet with android 4.1 installed and ubuntu 13.04 64 bits. I have tried several times the script but the log is always the same.
    What can I do?
    Thanks in advance.

    —————————————————————
    CONFIRM ALL THE ABOVE THEN
    Press Enter to Continue
    — STARTING —-
    — WAITING FOR DEVICE
    adb server is out of date. killing…
    * daemon started successfully *
    — creating temporary directory
    mkdir failed for tmp, File exists
    — cleaning
    — symlinking tmp directory
    failed on ‘/data/local/tmp’ – Permission denied
    link failed File exists
    — Rebooting
    — WAITING FOR DEVICE TO RECONNECT
    — PLEASE WAIT, THIS MAY TAKE A WHILE
    if it gets stuck over here for a long time then try:
    disconnect usb cable and reconnect it
    toggle USB DEBUGGING (first disable it then enable it)
    — DEVICE FOUND
    — enabling emulator hack
    /system/bin/sh: can’t create /data/local.prop: Permission denied
    — Rebooting
    — WAITING FOR DEVICE TO RECONNECT
    — PLEASE WAIT, THIS MAY TAKE A WHILE
    if it gets stuck over here for a long time then try:
    disconnect usb cable and reconnect it
    toggle USB DEBUGGING (first disable it then enable it)
    — DEVICE FOUND
    — pushing busybox
    8668 KB/s (1075144 bytes in 0.121s)
    — correcting permissions
    — remounting /system
    mount: permission denied (are you root?)
    — checking free space on /system
    10 KB/s (439 bytes in 0.039s)
    — Free space on /system : 519763 bytes
    — no cleanup required
    — copying busybox to /system/xbin/
    /system/xbin/busybox: cannot open for write: Read-only file system
    — correcting ownership
    Unable to chown /system/xbin/busybox: No such file or directory
    — correcting permissions
    Unable to chmod /system/xbin/busybox: No such file or directory
    — installing busybox
    /system/bin/sh: /system/xbin/busybox: not found
    — pushing SU binary
    failed to copy ‘files/su’ to ‘/system/bin/su’: Read-only file system
    — correcting ownership
    Unable to chown /system/bin/su: No such file or directory
    — correcting permissions
    Unable to chmod /system/bin/su: No such file or directory
    — correcting symlinks
    rm failed for /system/xbin/su, No such file or directory
    link failed Read-only file system
    — pushing Superuser app
    failed to copy ‘files/Superuser.apk’ to ‘/system/app/./Superuser.apk’: Read-only file system
    — cleaning
    rm failed for /data/local.prop, No such file or directory
    rm failed for /data/local/tmp, Permission denied
    failed on ‘/data/local/tmp.bak’ – No such file or directory
    — rebooting
    ALL DONE!!!
    Press Enter to continue

    • joaojonesventura Says:

      This is for the bq Edison with Android 4.0 (ICS). For JellyBean you need to install CWM and then install a zip with busybox and a super user apk which will grant you root access..

  3. APS Says:

    Hello,

    I’ve tried to follow your indications but I’m in troubles. As this was my first Root had to go get the SDK with ADB to Google (may13), check!
    Then install it and updated the Path variable on Win7 (32bits) for tools and platform-tools. Done!
    Next was to actually connect the Edison with the permissions and install the drivers on the device manager from the link provided.
    It gets recognized as Android ADB Interface. (Not sure if expected)

    Returning to your instructions on the command line: adb devices
    * daemon not running. starting it now *
    * daemon started successfully *
    List of devices attached

    “blank”….
    I don’t know if there is a need for some reboots after some installs or if there is anything that I’m missing.
    I really appreciate any idea.

    Thanks in advance
    APS

  4. teagenes Says:

    Thank you. I was no able to detect my Edison, however I succeeded with your tutorial.
    But there is always something wrong in my path, and I can not get the “runme.sh” script. Would you mind to give us a new link? It would be great if it has not an “.exe” in the end.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s


%d bloggers like this: