Our company bought new shiny ZiiO 7" to test some mobile aplications, but we are having trouble getting started. 'adb devices' shows empty list, but the device appears on 'lsusb' list (Bus 002 Device 007: ID 2350:0102) and we can access files by USB connection. We tried to set it up using standard steps (enable debugging, list devices, add vendor id, set permissions and restart adb server). We also tried several systems (Ubuntus and Windowses) and PCs. It's our first Creative device and first device with such problem.
So, is it known problem or maybe the device is broken? How to set up adb and device to work together on Ubuntu 10.04?
There's no ZiiO forum, so I posted here - hope it's ok.
i have the some problem, any ideas?
We managed to solve the problem. Here is what you should do on Ubuntu:
- add to xx-android.rules flowing line:
SUBSYSTEM=="usb",SYSFS{idVendor}=="2350",SYMLINK+="android_adb",MODE="0666"
- restart udev
- add folowing line to ~/.android/adb_usb.ini:
0x2350
- restart server
We also have the solution for Windows and Mac.
this work fine with MAC OSx too.
Sorry to be a newb, can you tell me how I can edit the file? I am a bit rusty with this stuff. Thanks!
Stawonog said:
We managed to solve the problem. Here is what you should do on Ubuntu:
- add to xx-android.rules flowing line:
SUBSYSTEM=="usb",SYSFS{idVendor}=="2350",SYMLINK+="android_adb",MODE="0666"
- restart udev
- add folowing line to ~/.android/adb_usb.ini:
0x2350
- restart server
We also have the solution for Windows and Mac.
Click to expand...
Click to collapse
Could you please outline the solution for Windows?
Thanks in advance.
here you go:
- download and install Google USB driver
- open file android_winusb.inf from the driver's directory. Find section [Google.NTx86] (if you have 32-bit Windows) or [Google.NTamd64] (for 64-bit). At the end of the section, add the following lines:
; Creative Ziio 7"
%SingleAdbInterface% = USB_Install, USB\VID_2350&PID_0102
%CompositeAdbInterface% = USB_Install, USB\VID_2350&PID_0102&MI_01
- find the device in Device Manager and update driver using previously installed USB driver
- add folowing line to %HOME/.android/adb_usb.ini:
0x2350
- restart server
you seem to be quite knowledgeable
so might be you know how to get permanent root on the ziio, I only get till temp root then tried this
F:\ADB>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox cp busybox /system/bin
./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/busybox
# busybox cp Superuser.apk /system/app
busybox cp Superuser.apk /system/app
# busybox cp su /system/bin
busybox cp su /system/bin
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
# exit
exit
But I always get su: unknown id: root in adb shell and su: must be suid to work properly in terminal emulator
If you have an xbin or sbin folder try moving su there, then chmodding it. That's the method I used to root the android emulator. Link is in my sig if you think it might help you out/give you some ideas. The emulator lost root on reboot but that's because it was a virtual device, pretty sure a real phone wouldn't lose root on reboot.
OK gave it a shot but didn't work either. No x or sbin on the ziio to begin with. will try some more later..
Is there anyway we can hack the ZiiO and root it with Android 2.2 ourselves?
Is there any way to get market working on these things?
Just picked up one of these.Great little device but I really need root and/or Frodo.
Any developers working on these yet?
Just got ADB working following stawonogs instructions. Then I was able to get a temp shell root with SuperOneClick. The full root doesn't work because of a Mount issue.
When you adb shell into the device, if you're logged in as root then you'll see '#' instead of '$'.
I was then able to adb push the googleapps pack, including vending.apk. Rebooted the device, but it looks like googleapps.apk doesn't work right, so the setupwizard.apk never completes, so I removed it. Went through setup manually, using the Youtube.apk method. Gmail.apk still fails due to googleapps.apk failing.
When I try to run vending.apk, I get a "server unavailable" error.
I waiting for good news to complete root for newbies user. Thanks.
/sys/block
hey guys,
i just found some files on the tablet, which could cause the trouble.
/sys/block/
i tried to remove them, but wasn`t able to...
rm: cannot remove ´/sys/block/... : Operation not permitted
i think without these files the rooting and flashing of the ziio should be possible...
but i´m not an expert... ;-)
maybe one of you is able to remove them and tell us if it´s working?
greetings
enzodroid
Stawonog said:
here you go:
- download and install Google USB driver
- open file android_winusb.inf from the driver's directory. Find section [Google.NTx86] (if you have 32-bit Windows) or [Google.NTamd64] (for 64-bit). At the end of the section, add the following lines:
; Creative Ziio 7"
%SingleAdbInterface% = USB_Install, USB\VID_2350&PID_0102
%CompositeAdbInterface% = USB_Install, USB\VID_2350&PID_0102&MI_01
- find the device in Device Manager and update driver using previously installed USB driver
- add folowing line to %HOME/.android/adb_usb.ini:
0x2350
- restart server
Click to expand...
Click to collapse
This worked perfectly on my Windows PC to the extent that my Ziio now shows up when I run DDMS. BUT, I cannot get the screen image to show up. I get the message "Unable to get frame buffer: EOF."
Anyone know what's that's about?
I have the Ziio 7" as well. I can get temp root using SuperOneClick but am unable to turn it in to permanent root.
I'm willing to try things if anyone has ideas on how to make this work!
I have the Ziio 7" as well. I can get temp root using SuperOneClick but am unable to turn it in to permanent root.
Click to expand...
Click to collapse
So, untill you shout down your device, you can use root apps? i got a ZiiO 7" yesterday, but its rather slow and needs root. Temp root would fix the issue for me i think, i just wont should it down.
add folowing line to %HOME/.android/adb_usb.ini:
0x2350
Click to expand...
Click to collapse
where do i find this file? cant find it anyway...
Stawonog said:
We managed to solve the problem. Here is what you should do on Ubuntu:
- add to xx-android.rules flowing line:
SUBSYSTEM=="usb",SYSFS{idVendor}=="2350",SYMLINK+="android_adb",MODE="0666"
- restart udev
- add folowing line to ~/.android/adb_usb.ini:
0x2350
- restart server
We also have the solution for Windows and Mac.
Click to expand...
Click to collapse
Hello,
I have also hit this problem with Creative ZiiO 10 on Mac OS X 10.6.7. If you would be kind enough to share your Mac solution it would be very much appreciated. Thanks!
Cheers,
Mark
Related
All credit for the binary goes to Sebastian Krahmer at http://c-skills.blogspot.com/. Please see fit to donate via Paypal to [email protected]
If you want a simpler 'one-click' process, go to this thread: Easier 1-2-3 Droid 2 Root for Windows / Linux / Mac
***NOTE: Proceed at your own risk. I and the providers of this code are not responsible for anything you do to your phone!***
Setup:
- Install adb (here) and Motorola drivers for windows(32-bit or 64-bit)
- Download attached archive
- Extract to a directory, I used c:\Droid2Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open command prompt
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- cd c:/Droid2Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two) to c:/Droid2Root
- cd c:/wherever-your-sdk-tools-folder-is
- adb kill-server
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
- exit
I'm sure there are certain steps that could be streamlined or eliminated, so please feel free to make a suggestion and I'll edit the post.
Additional thanks to @rainabba and AllDroid.org for their excellent Droid X rooting tutorial, which assisted me greatly in this process.
waiting for a recovery, glad to see its rooted
Android n00b here, I can remove the Verizon crapware with this right? And tether?
thelolotov said:
Android n00b here, I can remove the Verizon crapware with this right? And tether?
Click to expand...
Click to collapse
yes and yes
thelolotov said:
Android n00b here, I can remove the Verizon crapware with this right? And tether?
Click to expand...
Click to collapse
I wouldn't remove anything yet since we don't have a sbf file to recover from partial bricks. However, tethering and any other apps that require root can be used now.
I'm new to doing this all the adb way.
When you say extract to a directory what do you mean to extract. After it downloads the achive files its done.....
i understand the rest of the commands but im lost there
Hmm, alright, that's still worth it, will I lose my data/have to hard reset to root?
Right click the downloaded archive and "extract files". You need to do this so adb can push them to the phone.
thelolotov said:
Hmm, alright, that's still worth it, will I lose my data/have to hard reset to root?
Click to expand...
Click to collapse
Nope, it just gives you access. Nothing deleted.
I'm retarded i didnt realize it was attached to the post, i thought it was what adb downloaded when i first opened it cause it called them archives.
cannot access
I got as far as pushing super user su and busy box onto my phone but it says that system in read only.. how do i fix this?
Anybody actually try this?
Hello,
I am following your directions and when I get to the "adb push Superuser.apk" step I receive the following error:
"failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system"
I get this same error for the other adb push steps that follow.
Edit: To verify, I get a # shell.
Edit 2: I tried pushing the Superuser.apk to /data/local/tmp then cp to /system/app/, this also popped up a read-only file system error.
I'm currently trying it.
I have a 64 bit driver on my computer that i used to use for my D1 but it doesn't recognize my D2 when doing adb devices and i cant install the 32 bit driver
GSletta said:
I got as far as pushing super user su and busy box onto my phone but it says that system in read only.. how do i fix this?
Click to expand...
Click to collapse
Did you verify you have the # prompt three steps before that?
Yeah i get the # but it wont let me push superuser su and busybox
GSletta said:
Yeah i get the # but it wont let me push superuser su and busybox
Click to expand...
Click to collapse
Weird.. I didn't need to mount the system manually, but let me if there's a step I left out.
and some more screens (feel free to use in first post):
http://i.imgur.com/nPllt.jpg
http://i.imgur.com/COTEA.jpg
http://i.imgur.com/open3.jpg
djh816 said:
and some more screens (feel free to use in first post):
http://i.imgur.com/nPllt.jpg
http://i.imgur.com/COTEA.jpg
http://i.imgur.com/open3.jpg
Click to expand...
Click to collapse
Did you add any steps to mount the system? I don't believe I did, but it seems others are finding it to be read-only.
jerseyh22accord said:
I'm currently trying it.
I have a 64 bit driver on my computer that i used to use for my D1 but it doesn't recognize my D2 when doing adb devices and i cant install the 32 bit driver
Click to expand...
Click to collapse
Don't know if it will help you, but if it's anything like the DInc, you could just use the SDK's drivers and add a few device identifier lines to the INF file before installing them.
I hold no responsibility to how you use or not use this info and if you brick phone - you do this at your own risk
There is a couple away you can go about gaining root access with this phone I have tested all 3 ways but only had success with 2 of them.
a) You can download 'z4root' from the Android Market (If is still available) or search XDA forums for it.
b) Search the XDA forums for 'SuperOneClick' which requires mono to work on Linux. I have read people that have had success with 'SuperOneClick' but that was not the case for me.
c) My preferred method:
Prerequisite:
knowledge of Linux and Terminal
knowledge of ADB (guide available in forums)
I did all this using Debian (testing) 64bit, Android SDK.
Creating correct permissions to access the phone via USB:
i) create
Code:
/etc/udev/rules.d/51-android.rules
ii) in the file put
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
iii) then
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
iv) restart udev or reboot
Downloading and/or Installing required software:
1) Downloading and installing the android-sdk from: developer.android.com/sdk/index.html
2) Downloading and extracting 'SuperOneClick' (you will only need these 5 files: rageagainstthecage, sqlite3, su, busybox and superuser.apk)
3) Copy rageagainstthecage, sqlite3, su, busybox and superuser.apk into the platform-tools directory of android-sdk. Put phone in debug mode.
4) From a terminal (command line) change to the android/platform-tools directory and carefully do these steps.
Check to see if adb can see your phone properly:
Code:
./adb devices
You should see the serial number of you device, if you see bunch of '?' you have done something wrong.
Now for the fun part rooting the phone: <= no phun intended hehe
Code:
./adb push rageagainstthecage /data/local/tmp/rageagainstthecage
Code:
./adb shell
Code:
cd /data/local/tmp
Code:
chmod 0755 rageagainstthecage
Code:
./rageagainstthecage
5) Now wait until you get kicked out from adb before you do the following:
Code:
./adb shell
If everything worked now you should see a "#" instead of the "$" you saw previously in the adb shell which means you shouldn't get "permission denied" in the following steps:
Code:
mount -o rw,remount /dev/block/mdtblock4 /system
Code:
exit
Code:
./adb push su /system/bin/su
Code:
./adb push busybox /system/bin/busybox
Code:
./adb push sqlite3 /system/bin/sqlite3
Code:
./adb push Superuser.apk /system/app/Superuser.apk
Code:
./adb shell
Code:
cd /system/bin
Code:
chmod 4755 su
Code:
chmod 4755 busybox
Code:
chmod 4755 sqlite3
Code:
./adb reboot
Now you should be able to use apps like 'Cache Cleaner NG', 'Root Explorer', 'SetCPU' etc that require root access to work correctly.
Enjoy
Guide reflash FW for those who did some damage:
* Download from here that you want to install the FW
* Copy the folder in the microSD DLOAD (with the file inside UPADATE.APP)
* From phone off, Volume + Hold down RED BUTTON UP and power button.
* start the firmware upgrade, take a few minutes and then restart the phone . is a bit slow, do not be afraid, let him work and then back on (like the first time)
Help to get into recovery mode:
* down the 'volume up 'and 'green button'and then switch the device
Guide to bootloader mode:
* switch off, press and hold power button + volume down + red key
Overclock
Can this fone be oveclocked
SethIsHere said:
Can this fone be oveclocked
Click to expand...
Click to collapse
yes it can be OCed, I recommend using setCPU from the market
SethIsHere said:
Can this fone be oveclocked
Click to expand...
Click to collapse
Yes it can, to a Maximum of 600mhz (0.6 ghz) on the stock kernel
setCPU is no longer available on the market for free afaik.
Also can someone better translate the instructions to get into recovery mode? i can barely make sense of the above instructions ^^^
.produkt-R said:
Also can someone better translate the instructions to get into recovery mode? i can barely make sense of the above instructions ^^^
Click to expand...
Click to collapse
does this help:
http://forum.xda-developers.com/showpost.php?p=10371747&postcount=5
quail said:
does this help:
http://forum.xda-developers.com/showpost.php?p=10371747&postcount=5
Click to expand...
Click to collapse
Helped, Thanks.
Although after reading the entire page, i wonder if i should have a Recovery ROM installed. But i wonder if the phone will be left in it's current working state after installing it ?
i used z4root, worked fine for me
quail said:
Code:
chmod 4755 su
Code:
chmod 4755 busybox
Code:
chmod 4755 sqlite3
Click to expand...
Click to collapse
I think only "su" should be 4755 (setuid root), busybox and sqlite3 should just be 0755? Thanks for the instructions.
pb05life said:
i used z4root, worked fine for me
Click to expand...
Click to collapse
Ok I figured it ill shut up you have to use crappy dos command prompt and type everything in manually install proggies lol Google must die!
quail said:
Creating correct permissions to access the phone via USB:
i) create
Code:
/etc/udev/rules.d/51-android.rules
ii) in the file put
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
iii) then
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
iv) restart udev or reboot
Click to expand...
Click to collapse
Anyone know this part for windows XP?Not linux?
I got to rageagainstthecage and it says permission denied.
fvckyougooglescammer said:
So would you tell us, exactly how you did it?
Without using the market place?
Because I have tried 100 things downloaded all that junk wasted 5 hours.
And I do not know how to run the z4root on my phone.
I do not want to install another ROM.
I do not know why you can not run z4root and a file manager from the SD card I have tried methods with the SDK they are total rubbish.
Once again *without* using the market place.
Thanks
Click to expand...
Click to collapse
Download it mediafire.com/u8150
Sent from my Ideos using XDA App
could you explain why you prefer this way instead using z4root?
nitro-ale said:
could you explain why you prefer this way instead using z4root?
Click to expand...
Click to collapse
I have Z4root on the phone and its supposedly rooted.
Yet, I can install apps from PC onto phone, but can not uninstall them.
Adb always gives me failure.
And if I try from shell it always says permission denied.
tilal6991 said:
Download it
Sent from my Ideos using XDA App
Click to expand...
Click to collapse
Hi thanks downloaded it fine its on the phone but this doesn't tell me how to remove apps.
I have been able to install but not remove adb always says failure.
Thanks man,
Just worked perfectly on my IDEOS brought from 2degrees in NZ.
The copy of SuperOneClick that I downloaded contained a file called su-v2 instead of su. In order to get the hack to work I had to rename su-v2 to su before running ./rageagainstthecage . Pretty obvious, but it might help someone out.
Thanks
fvckyougooglescammer said:
I have Z4root on the phone and its supposedly rooted.
Yet, I can install apps from PC onto phone, but can not uninstall them.
Adb always gives me failure.
And if I try from shell it always says permission denied.
Click to expand...
Click to collapse
I followed your instructions and installed SetCPU to test my phone was rooted. It worked great! Thanks.
I still have a problem. When I try adb root it still says "adbd cannot run as root in production builds". I'm trying this to be able to control my phone with pc mouse/keyboard with androidscreencast.
Any suggestions will be much appreciated.
Answering to myself: I updated my phone with FUSIONideos 1.5 and now adb runs as root without problems.
Z4root
http://forum.xda-developers.com/showthread.php?t=833953
Worked for me
Does it removes simlock I have Huawei U8150 IDEOS Android phone with career lock ( Simlock ), so will this remove it
can there be a batch file / command / app for all this, too techy out there
also how to setup the environment to run these commands, i m windows user can i do it ?
Hi, it is possible to root ZiiO tablet with Android 2.2 ?
I try with z4root 1.3.0 but is not working
Is there any other solutions ?
my friend's sister is working as a designer and user experience officer at creative. as far as her knowledge will carry her, the answer to root is NO
in any case, why did you wish to root it? even after you root it, it wun be able to perform up to anywhere normal tablets can
Thanks for the replay, i what root access to try to install Android Market ... do you think is possible?
coljuay said:
in any case, why did you wish to root it? even after you root it, it wun be able to perform up to anywhere normal tablets can
Click to expand...
Click to collapse
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
get the adb driver from here
configure it to see the ziio using these instructions
get SuperOneClick from here
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)
Go to superoneclick's folder then in the Root folder you find there
Copy the su-v3 file to the adb folder (situated in Program Files/Android/android-sdk/platform-tools
Rename it to simply su
Start cmd and navigate to the adb folder
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
Open the new file in the adb folder named init.rc
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
Save the file
Push it back to the ziio using
Code:
adb push init.rc /system/ziilabs/init.rc
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.
rooting too...
i try the guide and my ziio has now permanent root and android market working fine...
Im going to give it a try as soon as i can find out how to update the drivers in windows. Cant find the device in device manager on XP.
Any tips?
EDIT: OMG thanks so much it worked!! PS you need to shell root first or you cant adb push su /sdin
Thanks! It worked great on my Ziio 10 as well.
Thanks to linkerro!
I also have rooted my Ziio 7". But some additions by using Windows 7 for the guide i have:
1. Every programm (Editor, CMD, etc.) you need to start it as Administrator!
2. I added the file "adb_usb.ini" manually in %USERPROFILE%\.android
3. The Superuser.apk i have copied it manually to /sbin by using ADB
Dont forget to press the THANKS button ;-)
Thanks!
Thx for this Guide.
My ZiiO 10" was rooted and i had google apps alredy installed, but without a change file (/ system / ziilabs / init.rc) Now i edited it with totalcomander on my ziio.
Is this a 100% root pernament?
Work all the root only programs?
Anyone tested Chainfire 3d @ ziio ?
Thanks a lof for guide, i have only one problem with my ziio, i haven't notrification sound i app (gmail, facebook, talk, vCommunicator), it's some fix for this problem ?
help
I am stuck... I cannot get my ziio 7 to appear under adb..
On putting 'adb devices' under cmd it just shows 'List of devices'.. but the list is empty.
With a lot of persistence i finally managed to root and get the market running.
Initially my Ziio 7 did not show under abd devices as the file adb_usb.ini was non existing.. then i followed another thread "Tegra forum about adb-usb driver"...... which helped me create the above mentioned file.. and then got my ziio 7 to appear on the adb devices list.
and following this guide i got the root....but to get the markets and rest stuff installed i have followed the below mentioned guide.
"19300-ziio-shell-root-fully-working-android-market-ad-hoc-fix.html"
avathor said:
Thx for this Guide.
My ZiiO 10" was rooted and i had google apps alredy installed, but without a change file (/ system / ziilabs / init.rc) Now i edited it with totalcomander on my ziio.
Is this a 100% root pernament?
Work all the root only programs?
Anyone tested Chainfire 3d @ ziio ?
Click to expand...
Click to collapse
Yes it is full root, all root requiring apps working 100%
I just want android market, don't need root. Is it possible? how to?
i have full root now... thanks...
ROM Manager
In ROM Manager, which ROM should I choose? Without which, don't believe I can install Google market.
laverdone said:
i try the guide and my ziio has now permanent root and android market working fine...
Click to expand...
Click to collapse
@laverdone What method did you use to install the google apps?
thasan said:
@laverdone What method did you use to install the google apps?
Click to expand...
Click to collapse
guide to installing google apps:
After you have rooted or shell rooted your ziio
1. download rar with the apps from here (http:// www. megaupload .com/ ?d=QSM6ATPB)
2. unrar them into a directory (and rename them to something like googleApps so it's easier to work with)
3. delete app/SetupWizard.apk (you allready have this)
4. use adb to push the files to /data/googleApps (or any directory as long as it's not on the sdcard)
5. run chmod -R 755 /data/googleApps in the adb shell
6. copy the files to /system (cp -rf /data/googleApps/* /system)
7. clean up (rm -r /data/googleApps)
One more thing. The market doesn't see gmail and the other apps as installed so you have to get them again from the market if you want updates.
Okay, this was my first time trying to root my phone and it would figure that non of the automated methods worked for me. Still, I was able to get root on my US Cellular Samsung Galaxy S Mesmerize (SCH-i500 for the kids keeping track at home) and these are the steps that I took. I hope this helps others who may be scratching their head wondering what to do when the developers haven't gotten around to (read: forsaken) us.
The nice thing about this method is that it doesn't require Windows (though you still do download SuperOneClick).
NOTE: This is only for an officially updated Mesmerize. Rooting is unnecessary for the leaked version.
APOLOGY: I can't post any links to anything outside the forum as I am a newer member, so, sorry for not being able to post URLs.
1. Download the Android SDK from the Android developer website and install/unzip it. You may need to add the path to the adb tool (found under platform-tools for me) to your PATH variable.
2. Download the SuperOneClick tool and unzip it
3a. If you are using Windows, then make sure to install the drivers for your phone. I don't have Windows, so don't ask me which file to download. Sorry.
3b. Enable USB Debugging on your phone (Settings->Applications->Development->Check "USB Debugging").
4. Connect your phone to your computer using the USB cable
5. Open a shell (or command prompt on Windows) and change directories to where you unzipped SuperOneClick
6. Run the following commands to copy files to your device
A. adb push psneuter /data/local/tmp/psneuter
B. adb push busybox /sdcard/busybox
C. adb push su-v2 /sdcard/su
NOTE: A quick note of each of these files.
A. psneuter - an exploit to gain root access temporarily on your phone
B. busybox - a compilation of common unix commands to help you along the CLI world
C. su - the super-user command used to gain elevated privileges
7. Run the following command to get a command line interface to your device
adb shell
At this point, you should see a $ prompt indicating that you are on your phone.
From here, you will change directories to where you put the exploit, change the permissions so you can run it, copy over the files that we need to sustain root access, and finally, install the Superuser.apk app so that you can manage root access from the UI.
Execute the following commands:
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
Here, you will be disconnected from your device. This is normal. Just run "adb shell" again to get back in, though now, you will notice that the prompt has changed to a #. The following commands will reflect that.
# mount -t rfs -o remount,rw /dev/block/st19 /system
# cd /system/xbin
# cat /sdcard/busybox > busybox
# cat /sdcard/su > su
# chmod 4755 busybox
# chmod 4755 su
# exit
Now, you will be back on your computer. Type the following to install the Superuser.apk app.
adb install Superuser.apk
That should do it! You now have root access. Go ahead and try to install Titanium Backup (requires root). You can also install a terminal app or anything else.
I hope this helps. Report your successes/failures in the comments.
Someone can help me how to root aigopad m60?.. im already searching all over the net...
Thanks.
kickhopperX said:
Someone can help me how to root aigopad m60?.. im already searching all over the net...
Thanks.
Click to expand...
Click to collapse
There are two apps aimed at rooting Android devices: 'z4root' and 'superoneclick' but success with these is hit or miss. It's worth a shot
Sent from my SCH-R880 using xda app-developers app
kickhopperX said:
Someone can help me how to root aigopad m60?.. im already searching all over the net...
Thanks.
Click to expand...
Click to collapse
Hello kickhopperX
I also have a tablet aigopad m60 like you. this tablet is already rooter, you need just one application as ES Explorer which will allow you access to the tree (/).
I needed time to mount my sd card external sd card to the system.
One question: your tablet restarts all the time?
Good Day
Escuse me if I speak a little sore I use google translate to translate.
aigoPad m60
fariik said:
Hello kickhopperX
I also have a tablet aigopad m60 like you. this tablet is already rooter, you need just one application as ES Explorer which will allow you access to the tree (/).
I needed time to mount my sd card external sd card to the system.
One question: your tablet restarts all the time?
Good Day
Escuse me if I speak a little sore I use google translate to translate.
Click to expand...
Click to collapse
do you mean that it's already rooted ?
have you tried Directory Bind or SwapSD ?
i already tried z4root & super one click to root this device..both option won't work..please help us
I already found the solution guys!
Search 4Shared this apps :
DamNxQQr/doomlord_v1_xperia-2011-ics-ro
hoho.. thanks dude.. its working!!..
well... got custom rom for this tablet?..
its working ? how u do it ?
kickhopperX said:
hoho.. thanks dude.. its working!!..
well... got custom rom for this tablet?..
Click to expand...
Click to collapse
Not working with my aigopad m60 need help here cause Im dont know where to start
already have DamNxQQr/doomlord_v1_xperia-2011-ics-ro download to my PC and i have not install anything yet on aigopad m60
follow the instruction on runme(windows batch file) and when i run the batch it say " adb server is out of date " and " more the 1 device and emulator " then its say "complete
YAY!!!!! nothing happen
arerain86 said:
I already found the solution guys!
Search 4Shared this apps :
DamNxQQr/doomlord_v1_xperia-2011-ics-ro
Click to expand...
Click to collapse
I'm trying on my AigoPad M60, but not working
Here's how i did it.
Download and install moborobo.Launch the app and let it download the driver for m60.
once stabilize, unplug your tablet and reboot. on your dektop exit moborobo and kill the process. Reconnect tablet and execute runme.bat.
Let me know.
Thanks
[ROOT] [HOWTO] aigoPad M60 rooting script + generic su + generic usb driver
Hi.
I owned several aigoPad M60 bought from all over (to say it have slightly different ICS 4.0.3 revisions) and some I actually got them revisions by sending to service centre and flashed to a newer firmware.
Nevertheless, all of them can be rooted using this script (for Windows, 380 KB).
I actually rooted a Kindle Fire HD first using this script found on some chinese site (sorry I already forgot where I did so please pardon me for lack of credits). I cleaned up and englicised the whole thing, and updated the ADB tools to greater (and more compatible) version. Actually most ICS root scripts found everywhere are more or less the same.
So far, devices tested and succeded:
- Amazon Kindle Fire HD (ICS version)
- aigoPad M60 (ICS)
- Samsung Galaxy SII (GT-I9100 & GT-I9100G) ICS and Jellybean (works on mine, both phones and both 4.0.3 and 4.1.2)
- Chinese Samsung Galaxy SIII clone (can't explain much since it's a bootleg, it has MTK board) (ICS)
- Several other chinese tablets which somehow lose it's root or not rooted (ICS): Momo.cn 3G, AMPE, MaPaN. Sorry didn't remember it's exact models anymore.
This script contains a batch file, ADB exe file and two API libraries, and a generic su found in chinese tablets. The su works up to certain level but it is preferred to replace that with SuperSU from chainfire (Superuser from chainsdd didn't work well on these ICS chinese tablets, for me. Not sure about koushik's). Just install and when it asks to replace binary, choose normal and tap yes.
You have to have installed USB driver first. I have uploaded the compatible USB ADB driver for most chinese phones and tablets (8.5 MB, have to be split into x32 and x64 since the forum doesn't allow 8MB+ attachments, if you're not sure, download both and merge the folders, overwriting duplicate files).
Note: The driver works on Windows XP, 7 and 8. On Win 7 and 8 you will have to disable driver signature verify in order to install. (Win 7: Boot, F8, Disable signature. Win 8: Setting, Change PC Settings, General, Advanced Startup, look for Disable signature)
Those who already have ADB and drivers installed, here it is (simplified form of the actual script):
Windows (no need admin for ADB, just for driver installation):
Code:
adb wait-for-device
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
adb wait-for-device
adb shell rm /data/local.prop
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
adb wait-for-device
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb reboot
adb kill-server
Linux:
Same
Tip: If you want to, you don't have to download anything. Just copy+paste the script. But make sure you have su in current directory. You can get chainfire's su from SuperSU.apk (assets\supersu.arm.png, rename it to su).
Careful though, this copy+paste script lacks safety measures compared to the one in the archive, such as it doesn't check if the rooting is a success or not, but the script inside archive will prompt you first before wiping /data/local/tmp ...
Note: What I mean by the su works 'up to certain level' is, it doesn't accept command lines such as su -c command. Also you will have to replace it with a proper superuser app (SuperSU, Superuser) if you want to use Titanium Backup, Lucky Patcher and so on...
i juz purchase one for my kids to play games and i google on how to root the aigopad m60, it took me here.
Many thanks for the guide, i succesfully root it.