[Solved] Root TF101 without Windows, possible or not? Yes, it's doable!!! - Eee Pad Transformer Q&A, Help & Troubleshooting

Hi all!
Was about to purchase a Nexus 7 when I saw a huge discount on the Asus TF101 and decided to take it. How I have a it in front of me proudly informing it has the firmware revision IML74K.WW_epad-9.2.1.27-20120615. BTW, the s/n starts with B50 if it matters.
And now what? Wait for the official JB or root it right now? I usually root all my devices at least to have nandroid + TiBu, even if I don't plan to install any alternative FW.
The problem is it's an ICS 4.0.3 with the problem to enter into recovery mode and I have only a Mac computer, no Windows and no Linux machines around. I read the threads and see every time the Windows tools, nothing for Mac. No root from SD card neither.
Any advice how to root using the Transformer itself or my Mac? And any advice regarding best JB ROM or at least best kernel for stock 4.0.3 ROM with exFAT support? I don't use NTFS because my Macs can't write on and old FAT16 has the famous 4 Gb limit, not good for the movies.
Many thanks in advance.

You could try and install Windows on your Mac to essentially have a dual boot of both OS's. Or you could use something like VMWare (I think that's what it is but I'm like 5% sure) which allows you to run windows without necessarily installing it. Anyway, I suggest, if you can, to go ahead and root your device and install a JB ROM like EOS or CM10 or something.

If it's not possible to do Android modifications on a Macintosh it looks like your only option would be to setup a dual boot with Linux to do your Android Rooting and ROM flashing since I would imagine you would want to avoid having to use Windows for this It would be better to avoid virtual machines to do device modifications and just stick to the dual boot option since support for USB devices is iffy in virtual machines.

Hi all,
Shmi117 said:
You could try and install Windows on your Mac to essentially have a dual boot of both OS's.
Click to expand...
Click to collapse
No chance! I don't like to spend hours installing Windows and all this stuff again !!! :crying:
WCL1990 said:
If it's not possible to do Android modifications on a Macintosh it looks like your only option would be to setup a dual boot with Linux to do your Android Rooting and ROM flashing since I would imagine you would want to avoid having to use Windows for this It would be better to avoid virtual machines to do device modifications and just stick to the dual boot option since support for USB devices is iffy in virtual machines.
Click to expand...
Click to collapse
Basically what Linux can to Mac OS X can do. At least regarding adb and the command line use. The problem is I have found tons of good information about how to do it using Windows, but nothing for Linux nor Mac.
OK, here is the answer. One can root the Asus Eee Pad Transformer TF101 using Mac OS X only!
Developing in next message...

OK, here is the solution. :fingers-crossed:
First of all, I presume the Android SDK for Mac OS X is installed and upgraded.
Next, on the Transformer please go to Settings -> Developer options and activate the USB debugging. Finally, please check this forum thread and download the latest version of PERI. Yes, PERI for Windows 0.4 as of today. Please unzip the downloaded file.
No sorcery or black magic here, I've just learned from the bat file and tried to reproduce the whole procedure manually using adb.
Most Linux users will smile, but I will show the commands the way most Mac OS X user will need to input them. Basically, you don't really know that the shell path is and what "finally add adb to your path" means, right?
1. OK, please open the Finder and go to the directory where the adb executable lives. Something like ~/Downloads/android_sdk/android-sdk-macosx/platform-tools/.
2. Now please open the Terminal.app inside Application/Utilities folder and go to the same directory.
3. Please connect the Transformer to the Mac using the USB cable.
4. First of all, let's see if adb sees the Transformer. Please input
Code:
./adb devices
If everything is OK, you'll see something like this:
Code:
List of devices attached
024640c082db4561 device
5.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/recoveryblob /sdcard/
Basically you input ./adb push, drag the a.m. file and next input /sdcard/
6.
Code:
./adb shell mv /data/local/tmp /data/local/tmp.bak
7.
Code:
./adb shell exit
8.
Code:
./adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
9.
Code:
./adb reboot
Wait while the Transformer reboots.
10.
Code:
./adb shell dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
11.
Code:
./adb shell exit
12.
Code:
./adb reboot
Wait while the Transformer reboots.
13.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/Superuser-3.0.7-efghi-signed.zip /sdcard/
See #5.
14.
Code:
./adb reboot
Wait while the Transformer reboots.
15. Now please shut down the Transformer manually and boot into recovery. Please hold Power + Volume Down buttons and next confirm with Volume Up button when asked. Rogue XM recovery will boot.
16. Wipe cache, wipe Dalvik cache, next choose Install zip file from internal storage and choose the Superuser-3.0.7-efghi-signed.zip.
17. When it's done, reboot.
18. PROFIT. :good: Your device is rooted with Rogue XM recovery installed.
From there I suggest to install SuperSU and eventually SuperSU Pro as it seems to work better than Superuser and Superuser Elite respectively. You can eventually get rid of Superuser if you wish so, instructions available in this forum thread. As I own both SuperSU Pro and Superuser Elite, I've installed SuperSU and upgraded Superuser, just in case of. You should not mix them, though, thus I've revoked the root permission of Superuser.
Next I've installed Busybox. I don't know if it's the best version for TF101, works well on my GNote.
Finally, let's play with the recovery options courtesy of some awesome developers. :good: We can choose among Rogue XM Touch, CWM classic, CWM 6.x and official or modified TWRP. I've chosen the official TWRP with GooManager.
Next stop, Titanium Backup.
Should you have other recommendations, please do not hesitate.

Thanks a lot friend. I used the same procedure to root my TF101 using Ubuntu Are you using any Customised ROM ? I am using CM10 based ROM built by RaymanFX and it is simply awesome
iLearner said:
OK, here is the solution. :fingers-crossed:
First of all, I presume the Android SDK for Mac OS X is installed and upgraded.
Next, on the Transformer please go to Settings -> Developer options and activate the USB debugging. Finally, please check this forum thread and download the latest version of PERI. Yes, PERI for Windows 0.4 as of today. Please unzip the downloaded file.
No sorcery or black magic here, I've just learned from the bat file and tried to reproduce the whole procedure manually using adb.
Most Linux users will smile, but I will show the commands the way most Mac OS X user will need to input them. Basically, you don't really know that the shell path is and what "finally add adb to your path" means, right?
1. OK, please open the Finder and go to the directory where the adb executable lives. Something like ~/Downloads/android_sdk/android-sdk-macosx/platform-tools/.
2. Now please open the Terminal.app inside Application/Utilities folder and go to the same directory.
3. Please connect the Transformer to the Mac using the USB cable.
4. First of all, let's see if adb sees the Transformer. Please input
Code:
./adb devices
If everything is OK, you'll see something like this:
Code:
List of devices attached
024640c082db4561 device
5.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/recoveryblob /sdcard/
Basically you input ./adb push, drag the a.m. file and next input /sdcard/
6.
Code:
./adb shell mv /data/local/tmp /data/local/tmp.bak
7.
Code:
./adb shell exit
8.
Code:
./adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
9.
Code:
./adb reboot
Wait while the Transformer reboots.
10.
Code:
./adb shell dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
11.
Code:
./adb shell exit
12.
Code:
./adb reboot
Wait while the Transformer reboots.
13.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/Superuser-3.0.7-efghi-signed.zip /sdcard/
See #5.
14.
Code:
./adb reboot
Wait while the Transformer reboots.
15. Now please shut down the Transformer manually and boot into recovery. Please hold Power + Volume Down buttons and next confirm with Volume Up button when asked. Rogue XM recovery will boot.
16. Wipe cache, wipe Dalvik cache, next choose Install zip file from internal storage and choose the Superuser-3.0.7-efghi-signed.zip.
17. When it's done, reboot.
18. PROFIT. :good: Your device is rooted with Rogue XM recovery installed.
From there I suggest to install SuperSU and eventually SuperSU Pro as it seems to work better than Superuser and Superuser Elite respectively. You can eventually get rid of Superuser if you wish so, instructions available in this forum thread. As I own both SuperSU Pro and Superuser Elite, I've installed SuperSU and upgraded Superuser, just in case of. You should not mix them, though, thus I've revoked the root permission of Superuser.
Next I've installed Busybox. I don't know if it's the best version for TF101, works well on my GNote.
Finally, let's play with the recovery options courtesy of some awesome developers. :good: We can choose among Rogue XM Touch, CWM classic, CWM 6.x and official or modified TWRP. I've chosen the official TWRP with GooManager.
Next stop, Titanium Backup.
Should you have other recommendations, please do not hesitate.
Click to expand...
Click to collapse

Thanks, that worked nicely for me!
One thing I can't figure out yet, though, is how to do a backup - the microsd card doesn't mount at /sdcard/ and backing up to internal storage is not recommended...

Wheelie
Hi!
A linux only solution for B70(+) devices can be found here:
http://androidroot.mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/
It is what I used twice so far. Works as it should.
I do not claim credit for anything! I just stumbled upon the solution.

Problem rooting
Hi,
this is my first post on XDA.
After a lot of readings here, I think I have tried everything I could, but my knowledge in rooting is too limited to understand these bugs:
At first, when I tried running these lines on the terminal, I couldn't push the files to /data/local: permission denied.
Then, I tried pushing to /sdcard/ and it worked.
But the next error I get is when linking:
"link failed Function not implemented"
Can you help me please?
My computer is a Mac, so I have tried you method first. I also tried on my Parallel Desktop with Windows 8 and on the PC with Windows 8.1 of my girlfriend, with RootDebugFs.
Here is the description of my Infinity pad:
model: ASUS Transformer Pad TF700T
Android: 4.2.1
Kernel: 3.1.10-g9827b9a, [email protected] #1
Build: JOP40D.WW_epad-10.6.1.14.8
I had the build 14.10 but I found that I should downgrade to 14.8, so I did, but nothing changed.
I also unlocked my tablet by mistake, thinking it would help rooting.
Thanks for your help.
Best,
Yohan.

Just did this!!! Still works!!! Followed your steps. Now the recovery is TWRP 2.5!!! As the peri version changed I checked if the .bat was still doing the same things, and it is!!
Thanks for your tuto! Saved me some time installing W**** ...

Related

Coby Kyros 7015 - How to install CyanogenMod (Froyo based)

This will be an often-updated guide to all the latest successes of getting a quality port of CyanogenMod, a custom Froyo based Android distribution.
This thread was originally intended to be specific to the Coby Kyros, but since most issues relate to all Telechips tablets, it may prove useful to owners of other such devices as well.
Things we have working: Touchscreen, Screen Roation, WiFi (Connects to AP and Ad-Hoc), Market, Texting via Google Talk.
Things we have kinda working: WiFi can be a little wanky, but if you disable and re-enable it works fine.
Things that do not work/Issues: Some apps not working (like Angry Birds) due to sdcard not being properly addressed, video play back, sound recording is very nasty, missing on screen volume controls, occasionally the input box is not updated with what you're typing, but when you hide the keyboard the text is there.
Further Reading:
Most of the development for the Kyros 7015 has taken place in this thread.
and the developement of Cyanogen for Telechips tablets has taken place in the thread (on slatedroid.com).
Also check out my tutorial for Getting the Most Out of Eclair (Android 2.1) for this same device.
Instructions
1. Download and install ClockworkMod .
2: Preparations. If you have not already, install Android SDKto your PC. Download bootimage and system image. Create a "Cyanogen" folder in the clockwork/backup folder on your SD card and unzip both files into this folder. I also renamed and placed my recovery.img in here.
Contents of /Cyanogen
Code:
boot.img
nandroid.md5
recovery.img
system.img
3: Getting Some Files from Eclair. Connect your tablet to your PC and issue the following commands using ADB (Note: This step is to be done from Android 2.1, not from a previous version of CyanogenMod. If you already have CyanogenMod install, please revert to Android 2.1 to retrieve these files)
Code:
adb pull /sys/class/input/input1/calc_table calc_table
adb pull /data/softmac softmac
This should copy the calc_table and softmac files to the directory where ADB is located. Leave them where they are, and place build.prop and sensors.tcc92xx, from COBY7015-fixpack in there as well.
4: "Restoring" CyanogenMod. Boot into recovery mode (hold down front button and press the reset button on back of device). You should now be in ClockworkMod. IF YOU HAVEN'T ALREADY, MAKE A BACKUP! Choose "Wipe data / factory reset" and then "backup and restore." Restore from Cyanogen folder.
5: Restoring Some Key Files. With your tablet connected to your PC, issue the following ABD commands, taking care to keep your tablet awake:
Code:
adb remount
adb push build.prop /system/
adb shell chmod 644 /system/build.prop
adb push calc_table /system/etc/
adb shell chmod 644 /system/etc/calc_table
adb push sensors.tcc92xx.so /system/lib/hw/
adb shell chmod 644 /system/lib/hw/sensors.tcc92xx.so
adb push softmac /data/softmac
adb shell chmod 644 /data/softmac
adb reboot
After your tablet finishes rebooting, you should notice you have a working touch screen.
6: Enabling Google Apps. Download gapps-mdpi-tiny-20101020-signed.zip and MarketUpdateFroyoHdpi.zip. Place onto your SD card and reboot into recovery.vChoose "Install Zip from SDcard" and install gapps-mdpi-tiny-20101020-signed.zip and then MarketUpdateFroyoHdpi.zip. Reboot and accept the terms of the market!
7: Texting using Google Voice. Here is how to text with Google voice. You will need a working android phone (probably needs to be rooted) with Titanium Backup installed. Set up Google Voice on the phone-- make sure you opt for the Google phone number as that is the number you will be texting from. Once up and running, back up the program using Titanium. On the tablet, install Titanium Backup and use it to restore the Google Voice program (App+Data) to your tablet. (You may have to copy the backup files to the Titanium directory on the INTERNAL drive.) Once Google Voice Launches, switch back to Titanium Backup-- do not try to set up Google Voice. Titanium backup will then restore the data for Google Voice. You should now be able to text from your tablet.
This is all I have right now, more to follow.
Wouhou, first post!
thanks for that thread. Really great idea. I'll contributed at the best of my knowledge. Really like what you guys are doing and hope to have CyanogenMod fulling (or almost fulling) working.
stoned99 said:
Wouhou, first post!
thanks for that thread. Really great idea. I'll contributed at the best of my knowledge. Really like what you guys are doing and hope to have CyanogenMod fulling (or almost fulling) working.
Click to expand...
Click to collapse
Hope this helps, and I hope we can get everyone working on Cyanogen for the 7015 over to this thread to keep from getting this and the 2.1 root/mod project from getting too intermingled/confused.
Thanks. Finally had 15 minutes to install it and test it. Your procedure worked like a charm!
Only thing: Just add to fun_'s proedure for build.prop a shell like this
adb shell chmod 644 /system/build.prop
Great guide!
stoned99 said:
Thanks. Finally had 15 minutes to install it and test it. Your procedure worked like a charm!
Only thing: Just had to fun_'s proedure for build.prop a shell like this
adb shell chmod 644 /system/build.prop
Great guide!
Click to expand...
Click to collapse
Thanks, I got that error fixed.
I uploaded 12/12 build. to avoid confusion, old build was removed.
please update #2.
sorry for this inconvenience.
Fun_
So are the files under the obsolete folder now on that website.
Also wondering if someone can do a clockworkmod of the image
with most of the files edited I think for new peeps this will make it easier.
I have not flashed mine yet as I use it for video alot and
if that isn't working then it doesnt do me much good right now
adamdietrick could you modify your procedure for the new one and also add to do a nandroid backup as some new people with Android might not know it's important. I tested the procedure it's working fine.
so globally it would be something like that. Please modify it so it can be more easily to follow:
1) clockwork
2) Backup your nand: ClockworkMod recovery, backup and restore, backup
3) When booted in Eclair (stock rom):
adb usb
adb pull /sys/class/input/input1/calc_table calc_table
adb pull /data/softmac softmac
*be sure to know where the files are copied to your pc because you'll need to add them back on your device later.
4) Copy all files (system.img, boot.img, nandroid.md5) in the clockwordmod backup folder on sdcard
5) Restore from backup, choose Cyanogenmod
6)adb remount
adb push build.prop /system/
adb shell chmod 644 /system/build.prop
adb push calc_table /system/etc/
adb shell chmod 644 /system/etc/calc_table
adb push sensors.tcc92xx.so /system/lib/hw/
adb shell chmod 644 /system/lib/hw/sensors.tcc92xx.so
adb push softmac /data/softmac
adb shell chmod 644 /data/softmac
**at some point, you might loose connectivity with the device and waking up from sleep might not help, just unplug the usb cable, plug back in and type adb usb in the command prompt window
adb reboot
... continue with your current step 6 to 8 (install Gapps, market update and Google Voice)
Procedure was mostly taken from the readme file of fun_ so all credits go to him.
stoned99 said:
adamdietrick could you modify your procedure for the new one and also add to do a nandroid backup as some new people with Android might not know it's important. I tested the procedure it's working fine.
so globally it would be something like that. Please modify it so it can be more easily to follow:
1) clockwork
2) Backup your nand: ClockworkMod recovery, backup and restore, backup
3) When booted in Eclair (stock rom):
adb usb
adb pull /sys/class/input/input1/calc_table calc_table
adb pull /data/softmac softmac
*be sure to know where the files are copied to your pc because you'll need to add them back on your device later.
4) Copy all files (system.img, boot.img, nandroid.md5) in the clockwordmod backup folder on sdcard
5) Restore from backup, choose Cyanogenmod
6)adb remount
adb push build.prop /system/
adb shell chmod 644 /system/build.prop
adb push calc_table /system/etc/
adb shell chmod 644 /system/etc/calc_table
adb push sensors.tcc92xx.so /system/lib/hw/
adb shell chmod 644 /system/lib/hw/sensors.tcc92xx.so
adb push softmac /data/softmac
adb shell chmod 644 /data/softmac
**at some point, you might loose connectivity with the device and waking up from sleep might not help, just unplug the usb cable, plug back in and type adb usb in the command prompt window
adb reboot
... continue with your current step 6 to 8 (install Gapps, market update and Google Voice)
Procedure was mostly taken from the readme file of fun_ so all credits go to him.
Click to expand...
Click to collapse
Starting work on it now (that I'm not sleeping). This is what happens when fun_ brings out new version at bed time!
LOL
don't worry, you can do it after your sleep. It's just that if some people moved to CyanogenMod with the current guide, they'll need to restore their eclair nanddroid backup to their device to grab the calc and software or use linux to mount system.img and extract calc_table and softmac. I can provide you the linux procedure in case you want to add it (for people who don't want to restore their eclair rom)
stoned99 said:
LOL
don't worry, you can do it after your sleep. It's just that if some people moved to CyanogenMod with the current guide, they'll need to restore their eclair nanddroid backup to their device to grab the calc and software or use linux to mount system.img and extract calc_table and softmac. I can provide you the linux procedure in case you want to add it (for people who don't want to restore their eclair rom)
Click to expand...
Click to collapse
That would be great to have. I had to restore mine last night to run this procedure.
Weird, the procedure I used to use with my Android file with my iphone (I had dual boot IOS and Android) doesn't work. I might not be the same systemfile. I'll try something else and let you know if I solve it
Just out of curiosity, (as I don't have time to read through the slatedroid forum) Has there been anything figured out on:
1. video playing on cyanogen
2. games loading full size ( if I change the lcd density it solves this problem but then everything is way too large, is there a way to make it to where the density changes for the games and only the games?)
3. Games that install to the sd card having problems i.e. angry birds, and asphalt?
I know these have probably been answered over on slatedroid but like I said I just don't have time to read through over 200 pages, especially where most of it is stupid newbie crap that is probably making it very hard for asure, venomous, and fun_ to get any actual feedback on stuff.
I was able to mount the system and ramdisk. Unfortunately it seems the files (calc_table and softmac) are not in there. I see a folder called sys and a folder called data in the ramdisk but don't see any files inside. Maybe it's in the kernel. I was able to extract the kernel from the boot.img but can't mount it. Oh well, people will have to restore from their nandroid backup if they want to pull the files.
Sorry
stoned99 said:
I was able to mount the system and ramdisk. Unfortunately it seems the files (calc_table and softmac) are not in there. I see a folder called sys and a folder called data in the ramdisk but don't see any files inside. Maybe it's in the kernel. I was able to extract the kernel from the boot.img but can't mount it. Oh well, people will have to restore from their nandroid backup if they want to pull the files.
Sorry
Click to expand...
Click to collapse
softmac may be in data.img of eclair nandroid backup.
calc_table is only in live system. please restore eclair firmware and reboot.
dhadlock said:
1. video playing on cyanogen
Click to expand...
Click to collapse
no hardware decoding yet. please use rockplayer for armv6+vfp (consume CPU power...)
dhadlock said:
2. games loading full size ( if I change the lcd density it solves this problem but then everything is way too large, is there a way to make it to where the density changes for the games and only the games?)
Click to expand...
Click to collapse
try Compatibility off in SpareParts
dhadlock said:
3. Games that install to the sd card having problems i.e. angry birds, and asphalt?
Click to expand...
Click to collapse
I have no idea.
I'm suffering where/how to talk worthfully
(here is OK, of course
fun_ said:
no hardware decoding yet. please use rockplayer for armv6+vfp (consume CPU power...)
try Compatibility off in SpareParts
I have no idea.
I'm suffering where/how to talk worthfully
(here is OK, of course
Click to expand...
Click to collapse
Just to let you know, I have tried the disabling the compatibility setting with no success.
adamdietrick said:
Just to let you know, I have tried the disabling the compatibility setting with no success.
Click to expand...
Click to collapse
what app "no success"?
recently some tablets with large screen are sold from major company. it may make things better with app update... (just my hope, sorry)
fun_ said:
what app "no success"?
recently some tablets with large screen are sold from major company. it may make things better with app update... (just my hope, sorry)
Click to expand...
Click to collapse
The only two I have had issues with. Kitchen timer, raging tunder.

Huawei Ideos Super FAQ

This is an FAQ for the Huawei Ideos as there have been many questions on how to do the same things. Hopefully this should help. There are other FAQs but this one tries to compile as many as it can into one FAQ.
Feel free to reply to this if there are any questions or if you want me to make any additions. The FAQ won't be complete to begin with but I will add as I get time.
One thing I will say is that I WON'T TAKE RESPONSIBITY IF YOU DAMAGE YOUR PHONE. I AM PROVIDING THE INFORMATION AND WILL TRY TO HELP YOU IF SOMETHING BAD HAPPENS BUT I CAN'T TAKE ANY RESPONSIBILITY
1. How to root the IDEOS
This can be done quite simply by adapting what quail wrote:
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 here (WORKS)
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. (HAVEN'T CHECKED)
c) My preferred method: (HAVEN'T CHECKED)
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​
2. How to flash the Ultrakiller Recovery Image
Now this has been covered many times but there have been a lot of problems with the BSOD on the IDEOS. A few days ago Ultrakiller came up with a solution that works regardless of the LCD type. Now this was distributed as an IMG file so many people were confused so here is a link to one with everything you need included. All I did was remove the amon'ra image and copied the Ultrakiller recovery IMG to the folder and edited the scripts to point to the new file.
After you download the file:
* Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys (Yes, bootloader is just the IDEOS logo) WHILE YOUR DEVICE IS PLUGGED IN
* WINDOWS - double click 'install-recovery-windows.bat'
* MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-mac.sh' followed by './install-recovery-mac.sh'
* LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-linux.sh' followed by './install-recovery-linux.sh'​
See Q3 if you have Windows and the prompt hangs on "Waiting for Device"
3. How to solve problems with drivers on Windows in bootloader mode?
1. Unplug your phone
2. Download and install PDANet from here - at the end of the setup it will tell you to plug in your phone - do that
3. Put the phone into bootloader (See Q2 above)
4. Go to device manager and right click on "Android 1.0" and click "Update drivers"
5. Click "No, not this time" and Next
6. When it asks you where to look for drivers point it to PDANet's install location
7. Hopefully it should find the driver and prompt you to install it - it will take some time
8. You can now access your device in bootloader!​
Thanks to the following people:
Quail for the base of the guide and the ROM I'm using - it's amazing BTW
Ultrakiller for the recovery image
Changelog:
21/01/2010: Initial writeup
22/01/2010: Added Q3 and made some minor changes​
i unfortunately deleted a system app and upon restarting my phone it wont boot.....it keeps hanging at the startup and reboots.. help me how to system restore...
Hi - the Ultrakiller recovery IMG in the ZIP from the Link above is "Ultrakiller.img.img". Dunno if it didnt work cause of this - sry didnt test, just downloaded new Ultrakillers "UltraJack-Recovery_v4.6.2.img", saved into that folder and changed the .bat to "fastboot-windows.exe flash recovery UltraJack-Recovery_v4.6.2.img" and it worked for me Even superuser.apk didnt work for usb-root but z4root does it perfect and DroidExplorer showing files now .
Thanks so far to all investing their time here
P.S.: the HUAWEI background of Ultrakillers recovery is very delicious
General guide to Flash ROM
Can you please provide a detailed guide for flashing Huawei Ideos. Because it is super guide. So it must contain this topic also.
I want to flash official ROM on following link:
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS
Waiting for your response
yrnehukuht said:
i unfortunately deleted a system app and upon restarting my phone it wont boot.....it keeps hanging at the startup and reboots.. help me how to system restore...
Click to expand...
Click to collapse
Dear have u find out the solution of this problem?? COZ im also suffering from this if u find it then plz tell me [email protected]
I have downloaded a rom from xda-developers wiki from this link
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS
then updated my device software by going in to update mode(press vol up + end key + power button) .
This step returned me my original recovery.
But I am not going to recommend it bcoz i am facing problems like my cd drive which is automatically displayed has become inaccessible.
I am having problem to copy files to sd card.
My upgrade mode is not working now.
all these things were working immediately after the above mentioned process but I am now stuck with these things.
I think it is because i have flashed lower version number of rom on phone.
If you want to recover recovery mode only then I have successfully flashed UltraJack-Recovery 5.2.1 from this link
http://forum.xda-developers.com/showthread.php?t=860189&page=24
Inform about your progress
Thanx. Very useful
Hi guys. I am in a lot of trouble with my ideos.
Tried installing a custom ROm using ROM manager and it failed, although the original ROM is still there and its booting up and working perfectly.
However, when i try to boot into recovery, only the lit blackscreen shows.
I have tried everything from running ULTRAjack recovery on windows(which only shows 'waiting for device' on cmd, with the pdanet drivers installed) to ubuntu(which shows 'waiting for device' on Amon-ra recovery and permission denied on ULTRAjack).
Could it be i didnt root the device properly since i used z4 root?
Any more ideas?
900/2100 or 850/1700/1900/2100
Hello, How do I tell which sub-model my U8150 is please? Either HSDPA 900 / 2100 / AWS or HSDPA 850 / 1900 / 2100 / 1700. baseband = 22201003; build no.= U8150V100R001C183B825; IMEC = 355093040562676; IMEC-SV = 39.
Check out your fcc id suffix. I have heard there is a b version and a d version.
hi do flashing many roms affects my ideos mobile?
netskink said:
Check out your fcc id suffix. I have heard there is a b version and a d version.
Click to expand...
Click to collapse
All I got is a U8510-1, no letter... any thoughts?
Unlock u8150
Hello.
i have a T-Mobile Ideos u8150, also known as Comet.
it is locked to T-Mobile and requests a pin code when using another sim card.
is there a way to unlock the phone?
please help me...
thank you.
Enable USB Debugging & One Click Root with Unlock Root Tool

Recommended rooting procedure under Linux

Since the link about rooting the TF101 in the reference thread is broken, I would like to ask what is the cleanest way to root the TF101. I'm coming from a stock B80* device at the latest OTA update.
I'm working under Linux. I want to root my device, install a custom ROM and Ubuntu as well (for the last part I think this guide http://forum.xda-developers.com/showthread.php?t=1537566 is the one to follow).
So now I need a pointer to the "reference" rooting guide (I've done a bit of search but apart from 1-click tools to be used under Win platforms I couldn't tell what is the latest "manual" procedure.
Another question: I read on the XDA wiki that to install Ubuntu on SBK2 devices Wheelie is needed in order to access the nvflash mode, but in the XDA guide I linked above Wheelie isn't mentioned at all. What am I missing?
What is the "cleanest" way to go through this?
Thank you in advance.
Under Linux, I think the easiest is to use Wolf's method 3 from here: http://forum.xda-developers.com/showthread.php?t=1622628
You will need the adb executable for Linux. I am not sure if it is included, or if you have to get it from the Android SDK tools here: http://dl.google.com/android/android-sdk_r21.1-linux.tgz
You will need a recovery blob saved on the internal memory of your TF101. I would use TWRP recovery, download the TWRP recovery blob here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob I would rename this to recovery.blob and save it in the /sdcard/ for easy reference.
Also, save this copy of SuperSU that can be flashed through recovery in the /sdcard/: http://forum.xda-developers.com/attachment.php?attachmentid=1210576&d=1342793670
Next, connect your TF101 to your Linux machine via the charger cable. Go to Settings - Developer Options and enable USB Debugging.
Open a terminal window where you can execute adb and type the following:
Code:
adb devices
It should show one device connected. If so, proceed. If not, you will want to wait for a Linux guru to come along and assist.
Next, execute the following commands:
Code:
[B]adb shell[/B]
[email protected]# [B]mv /data/local/tmp /data/local/tmp.bak[/B]
[email protected]#[B] ln -s /dev/block/mmcblk0p4 /data/local/tmp[/B]
[email protected]#[B] exit[/B]
[B]adb reboot[/B]
Once you see the Asus loading screen, you should be able to use ADB again. If you want to wait until it is fully booted, that is fine.
Execute the following:
Code:
[B]adb shell[/B]
[email protected]# [B]dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4[/B]
8860+1 records in
8860+1 records out
4536396 bytes transferred in 1.718 secs (2640509 bytes/sec)
[email protected]# [B]exit[/B]
[B]adb reboot[/B]
Note, the numbers for records in and out will vary, but as long as it completes it should be fine.
Upon reboot you should see a progress indicator on the bottom of the Asus screen. This is when it updates the recovery to the custom one you dd'd.
After it boots, you can then boot to recovery by holding the VOL DOWN and POWER button on the tablet (not the keyboard dock) for about 12-15 seconds. When you see the white text, release both and tap VOL UP before the white text disappears.
You should boot to the custom recovery (if you get a dead android, you still have stock recovery)
Once in custom recovery, tap Install and choose the SuperSU flashable located in the /sdcard/. Once that completes, you are rooted.
As far as installing Linux on a SBK2, I am not sure on that one. I have been reluctant to mess with Linux on my TF101.
Here I am, the procedure worked flawlessly. Thank you
Awesome!

[ROOT] $99 Walmart Nextbook 8 (NX008HD8G)

The Nextbook 8 (NX008HD8G) is a $99 tablet available from Walmart. It sports a AMLogic AML8726-MX SoC (1.5Ghz dualcore Cortex-A9 w/400mhz dualcore Malli400 GPU), 1 Gb of DDR3 RAM, 8" display, and 8Gb internal storage. Its a nice little budget tablet for those who don't need a Nexus 7 or greater performance rated tablet. Not too long ago I discovered how to root it and apparently I'm the first to do it as far as I can tell. Now here's how.
What you will need is Bin4ary's One Touch Root App. This app will get you only partial root via the ADB Shell. My guess is the ADB exploit he uses does work to get basic root access for ADB, but some incompatibility prevents proper installation of su & SuperUser.apk. What we're going to do is finish the job manually.
First run Bin4ary's app and use the Normal Method. Be sure to ignore all errors. After your tablet reboots move su and Superuser.apk from Bin4ry's app folder to the root of the Internal SDCard. Next you will need ADB. If you don't have it you can get it either from Bin4ary's app folder you found su & superuser.apk in or you can install the Android SDK. At the command prompt enter the following:
Code:
adb shell
su
At this point you should see a # sign indicating root privileges. If you do enter the following commands.
Code:
mv /system/xbin/su /system/xbin/osu
cp /sdcard/su /system/xbin
chmod 6755 /system/xbin/su
The use Astro or your favorite file manager to navigate to /sdcard and install SuperUser.apk then reboot your tablet. From here on you should have full root on your tablet. Credit should definitely goto Bin4ry for his work on his One Touch Root App for getting us half way there.
Confirmed Working
Confirmed. Works as described.
Nice work!
Thank you for this information, works excellent.
Ron Overdrive said:
The Nextbook 8 (NX008HD8G) is a $99 tablet available from Walmart. It sports a AMLogic AML8726-MX SoC (1.5Ghz dualcore Cortex-A9 w/400mhz dualcore Malli400 GPU), 1 Gb of DDR3 RAM, 8" display, and 8Gb internal storage. Its a nice little budget tablet for those who don't need a Nexus 7 or greater performance rated tablet. Not too long ago I discovered how to root it and apparently I'm the first to do it as far as I can tell. Now here's how.
What you will need is Bin4ary's One Touch Root App. This app will get you only partial root via the ADB Shell. My guess is the ADB exploit he uses does work to get basic root access for ADB, but some incompatibility prevents proper installation of su & SuperUser.apk. What we're going to do is finish the job manually.
First run Bin4ary's app and use the Normal Method. Be sure to ignore all errors. After your tablet reboots move su and Superuser.apk from Bin4ry's app folder to the root of the Internal SDCard. Next you will need ADB. If you don't have it you can get it either from Bin4ary's app folder you found su & superuser.apk in or you can install the Android SDK. At the command prompt enter the following:
Code:
adb shell
su
At this point you should see a # sign indicating root privileges. If you do enter the following commands.
Code:
mv /system/xbin/su /system/xbin/osu
cp /sdcard/su /system/xbin
chmod 6755 /system/xbin/su
The use Astro or your favorite file manager to navigate to /sdcard and install SuperUser.apk then reboot your tablet. From here on you should have full root on your tablet. Credit should definitely goto Bin4ry for his work on his One Touch Root App for getting us half way there.
Click to expand...
Click to collapse
Did NOT work for me.
1-On first attempt, got pound sign....tried to push code resulting in cant find SD
2-On second attempts, would not let me be superuser su
3-Did a factory reset....same results as (2)
Im stomped!....please help
Amlogic Next8HD8G (NX008HD8G) Modified Recovery - Stock Rom - Root & Gapps
Modified recovery, stock rom, flashable root and flashable Gapps here: http://www.freaktab.com/showthread.php?7010-Amlogic-Next8HD8G-%28NX008HD8G%29-Modified-Recovery-Stock-Rom-amp-Flashable-Root
ShaunMT
Confirmed as well..
Ty... no fusses at all..
zenkillizen said:
Ty... no fusses at all..
Click to expand...
Click to collapse
I need someone to be more clear on rooting this device because I already bricked one using the method from tab freaks instructions aren't that clear and I don't want to brick another one ! Please thanks
andrew09 said:
I need someone to be more clear on rooting this device because I already bricked one using the method from tab freaks instructions aren't that clear and I don't want to brick another one ! Please thanks
Click to expand...
Click to collapse
this guide is like the clearest root guide I've seen Just sit down and read it, take your time Rooting my seem hard at first, but you catch on
Aiko0923 said:
this guide is like the clearest root guide I've seen Just sit down and read it, take your time Rooting my seem hard at first, but you catch on
Click to expand...
Click to collapse
Parts are missing from the guide like how to install the adb drivers the computer needs to recognise the tablet first before u try and root it I have read through it and I've already bricked one also I noticed if you go to recovery on this tablet it erases the system and factory reset doesn't fix anything there's no factory ROMs or anything to fix it if it messes up. If someone can't a sure me that the method is correct I'll do it I'll try it.
Does this method work on the newer models say model number starting with YFG12 and up?
I bought this today.
I am having problems here:
I did what you said to do:
Normal Mode enabled!
Pushing busybox....
4806 KB/s (1165484 bytes in 0.236s)
Pushing su binary ....
7134 KB/s (104576 bytes in 0.014s)
Pushing Superuser app
6792 KB/s (2139595 bytes in 0.307s)
Making busybox runable ...
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful I will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
RunMe.sh: line 222: wait: pid 10 is not a child of this shell
Waiting for device to show up again....
RunMe.sh: line 225: wait: pid 10 is not a child of this shell
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
---
And then I copied the files su and the .apk to /sdcard
Then I try to run su, and it says:
su
/system/bin/sh: su: not found
so I do
[email protected]:/sdcard $ ./su
/system/bin/sh: ./su: can't execute: Permission denied
---
Other times, it just does this:
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful I will tell you, if not this shell will run forever.
Running ...
and it runs forever
what do I do?
http://www.cydiaimpactor.com/
Worked for me.
YES! use cydia impactor
H0wdy said:
http://www.cydiaimpactor.com/
Worked for me.
Click to expand...
Click to collapse
Yes, I used it also. worked for me too (my serial for the tablet is YF07... in case there is a problem with the newer versions)
Thanks, H0wdy
Steps to do it:
Download Cydia Impactor
Turn on USB debug in settings-> Developer options
Plug in tablet into PC (I used a 32 bit Windows 8.1)
Wait a while... a long while for me... for windows to download drivers, disconnect tablet, wait a few seconds, then reconnect.
you should see in the device manager (on the top) android phone and underneath Android Composite ADB interface
Unzip Cydia, run impactor.exe and just choose start for # drop SuperSU su to /system/xbin/su
Wait a bit, then you're done. (no reboot or anything else necessary).
Install supersu (or I guess any other superuser app) from the android market. It will tell you that you can update the su binary... your choice, I updated without a problem.
I had supersu installed beforehand, but I guess it has nothing to do with it, it wasn't working anyway)
Ranting, but maybe someone has this issue also:
One ( -- BIG --) problem I had was getting the connection between the tablet and my computer, and Not because I can't plug-in a cable
the tablet said it was connected, but on the computer, nothing showed up in device manager and the list of devices kept refreshing.
The PC was beep-ing just like it found a device. the device list would refresh once or twice, then again beep, all this till the end of my patience.
At first I thought it was the USB 3.0 port, then the cable, then the ESXi USB redirection (my desktop is actually a VM), then the windows version, then the architecture,
Then I switched to a laptop, nothing.. same story.
I can BET it's Sony's F***ed up drivers
So, I used a clean system (no other adb or phone drivers installed) and worked as a charm
I think I hat this much trouble because I had a lot of other drivers (for sony, samsung, universal adb, etc etc.)
So on the computer I had all this stuff installed, it looked like the tablet was connected, then disconnected in the space of 10-15 seconds, then repeat forever.
If this happens to you, use a clean windows.

Root vtab1008 honeycomb (masterkey)

!!!UPDATE!!!!
Sorry I lost my root files. I still have the base code i used to make them. I am trying to work with @saurik to get vtab1008 working with the cydia impactor so that this process will be eaiser. sorry about not keeping up here.
The linux root is still working.
!!!!!!!!!!!!!!!!!!!!!!!!!!!
I was able to get the VTAB1008 HONEYCOMB ROOTED. This device is no longer doomed to a rootless existence.
ROOT AT YOUR OWN RISK! I AM IN NO WAY RESPONSIBLE IF THIS BREAKS SOMETHING.
----WINDOWS ROOT (This worked for me)----
!!Some people have had problems with 64 bit systems.!!
https://dl.dropboxusercontent.com/u/...nys Root.zip (restored by grnsl2)
Download the latest java sdk http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
(if it installs anywhere but C:\Program Files\Java\jdk1.7.0_45\bin\jdb change the path in the runme.bat)
Setup ADB
Follow instructions at http://www.google.com/url?sa=t&rct=...5IAx2Xg-VjGm5pQ&bvm=bv.57155469,d.cGU&cad=rja
for the inf file use the one in the skinnys root,zip
!!!THIS STEP IS VERY IMPORTANT ^ IF YOU ARE HAVING ISSUES YOU MAY HAVE NOT COMPLETED THIS STEP!!!
Run Exploit
open command prompt (windows 7 type cmd in start menu and press enter)
CD to location you extracted the zip
example: cd "C:\Users\skinny\Downloads\Skinnys Root"
type "runme.bat"
You will see a ton of data on the screen after a minute your tablet will show android.app.Activity
Paste the following into the shell (the prompt should have changed to look like >)
Code:
stop in android.os.MessageQueue.next()
Touch your tablets screen (the prompt should change to <1> main [1]
Paste the following into the shell
Code:
print java.lang.Runtime.getRuntime().exec("/system/bin/sh /data/local/tmp/rootme.sh")
Wait until you see something like Java.lang.Runtime.getRuntime().exec("/system/bin/sh /data/local/tmp/rootme.sh") = "Process[id=1265]"
Code:
exit
Press enter to reboot
----LINUX ROOT----
Get Linux on a live usb stick to run exploit (skip if you have a linux system)
Download 32bit kubuntu from http://www.kubuntu.org/getkubuntu/download
Get a thumbdrive at least 2 gig
Launch unetbootin
Select bubble next to diskimage
Choose ISO
Click on ...
Browse to the kubntu iso downloaded at A.
Set drive to your usb drive letter.
The next step will erase your thumb drive!!!!!
Click OK
Process will complete and ask you to reboot (reboot)
Select the thumbdrive at startup (i don't know what type of computer you are using but most systems you can press f8, f11, f12 or f2 tp get the boot prompt)
(For more information read this guide http://sourceforge.net/apps/trac/unetbootin/wiki/guide)
Select Default at the kubuntu boot prompt
Select Try Ubuntu
Get kubuntu linux setup for the exploit (skip if you already have android tools on linux)
Press alt+f2
Type "konsole" and press enter
Paste the following commands in.
Code:
sudo chown kubuntu:kubuntu /opt
mkdir /opt/exploit/
cd /opt/
wget http://dl.google.com/android/adt/adt-bundle-linux-x86-20131030.zip -O adt.zip
unzip adt.zip
mv adt-bundle-linux-x86-20131030/ adt/
echo 'export PATH=$PATH:/opt/adt/sdk/build-tools/android-4.4:/opt/adt/sdk/platform-tools' >> ~/.bashrc
source ~/.bashrc
sudo su -c "echo 'deb http://ppa.launchpad.net/webupd8team/java/ubuntu saucy main
deb-src http://ppa.launchpad.net/webupd8team/java/ubuntu saucy main' > /etc/apt/sources.list.d/oracle-java.list"
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys EEA14886
sudo apt-get update
sudo apt-get -y install git
cd /opt/exploit/
sudo apt-get -y install oracle-java7-installer
Accept Java license agreement to install java 7
Run Exploit
Plug in your tablet
Enable debugging mode (Settings -> Applications -> Development -> USB debugging)
Paste the following commands in your linux console (if following steps use the konsole that you have been running commands in).
If you are not using /opt/adb/sdk for your android devlopemnt use your dir on the 3rd step
Code:
git clone [url]https://github.com/raymondhardy/mkbreak.git[/url]
wget 'http://goo.gl/Ox8qDx' -O Superuser-3.1.3-arm-signed.zip #thanks to @Munk0
unzip Superuser-3.1.3-arm-signed.zip
cp system/bin/su mkbreak/
cp system/app/Superuser.apk mkbreak/
cd mkbreak
./doit.sh /opt/adt/sdk
You will see a ton of data on the screen after a minute your tablet will show android.app.Activity
Paste the following into the shell (the prompt should have changed to look like >)
Code:
stop in android.os.MessageQueue.next()
Touch your tablets screen (the prompt should change to <1> main [1]
Paste the following into the shell
Code:
print java.lang.Runtime.getRuntime().exec("/system/bin/sh /data/local/tmp/rootme.sh")
Wait until you see something like Java.lang.Runtime.getRuntime().exec("/system/bin/sh /data/local/tmp/rootme.sh") = "Process[id=1265]"
Code:
exit
Press enter to reboot
If you get stuck at any part of this process please post a reply with information about the problem you are having.
PROOF OF ROOT
Thanks and credit goes out to.
robertmillan
Jay Freeman (saurik)
PoC by Pau Oliva
Vinogans for leading me to masterkey exploit
NICE!!! Any instruction changes for windows?
gnoober said:
NICE!!! Any instruction changes for windows?
Click to expand...
Click to collapse
Not yet i suspect someone will make a better root later on as of now this is linux only. This exploit uses of linux commands for injecting code into a system application to gain root.
I will be updating the first post later on with steps and screenshots on how to do this on a ubuntu live instance (I may even throw in a shell script so you run it and then wait forever while it does the setup and starts the root. I will see what i can do.)
skinnyquiver said:
I will be updating the first post later on with steps and screenshots on how to do this on a ubuntu live instance (I may even throw in a shell script so you run it and then wait forever while it does the setup and starts the root. I will see what i can do.)
Click to expand...
Click to collapse
Awesome! Nicely done! Guess I'm gonna have to dig out the VTab and give this a shot. Thinking it's gonna need a charge!
Sent from my LG Optimus G using Tapatalk
I updated the steps and re-rooted my tablet with them several times to verify that they worked. Let me know if they work for you
dandrumheller said:
Awesome! Nicely done! Guess I'm gonna have to dig out the VTab and give this a shot. Thinking it's gonna need a charge!
Sent from my LG Optimus G using Tapatalk
Click to expand...
Click to collapse
gnoober said:
NICE!!! Any instruction changes for windows?
Click to expand...
Click to collapse
Got this working on windows (does not look very pretty but it works.
Hey skinnyquiver, that is awesome... my vtab has already gained like 5mm of pure dust. However, i gonna digg it out these days, install stock recovery to update it to honeycomb finally and then reroot this thing...
Btw, the paragraph above windows instructions still says linux only...
_________________________
tapatalked from GalaxyS3
FadeFx said:
Hey skinnyquiver, that is awesome... my vtab has already gained like 5mm of pure dust. However, i gonna digg it out these days, install stock recovery to update it to honeycomb finally and then reroot this thing...
Btw, the paragraph above windows instructions still says linux only...
_________________________
tapatalked from GalaxyS3
Click to expand...
Click to collapse
try to root it with master key exploit I am talking about the the version .57 .. then before updating to honeycomb grab the update.zip the one that belong to honey comb ... try to do this
vinogans said:
try to root it with master key exploit I am talking about the the version .57 .. then before updating to honeycomb grab the update.zip the one that belong to honey comb ... try to do this
Click to expand...
Click to collapse
i am currently charging... my device is rooted with frozen updater, firmware is currently 1.9.56 so i am not sure what is the update path, will i get the honeycomb firmware immediately or do i have to update to .57 first?
_________________________
tapatalked from GalaxyS3
FadeFx said:
i am currently charging... my device is rooted with frozen updater, firmware is currently 1.9.56 so i am not sure what is the update path, will i get the honeycomb firmware immediately or do i have to update to .57 first?
_________________________
tapatalked from GalaxyS3
Click to expand...
Click to collapse
u will have to update to .57 then u will get honeycomb update ..
vinogans said:
u will have to update to .57 then u will get honeycomb update ..
Click to expand...
Click to collapse
Thats bad, but i will give that a try. However, i cant promise that i will succeede and it will take me some days as i am quite busy with my real life as well
_________________________
tapatalked from GalaxyS3
So it's certainly exciting to see root for this guy after owning it now for a couple of years.
I believe with root we'll be able to get rid of some bloat and stuff unneeded but I'm assuming we'll stay on Honeycomb.
I'd like to figure out what the real upside to this is.
Sent from my DROID RAZR HD using Tapatalk
grnsl2 said:
So it's certainly exciting to see root for this guy after owning it now for a couple of years.
I believe with root we'll be able to get rid of some bloat and stuff unneeded but I'm assuming we'll stay on Honeycomb.
I'd like to figure out what the real upside to this is.
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
You should be able to use this root with the 5.7 before going to honeycomb. This way you can have gingerbead rooted if your device came with the 5.7 update. I would like to get this running cm9 or cm10. The first problem with this is it will require a new kernal. I am going to be moving this weekend so it will be a while until I can get a build env to work on this. I plan on using this tablet to learn all about android rom making. Hope I don't brick it.
As Vizio has not released the kernel source I think we may want to look at using the xo-3 kernel.
Everything seems like it works, everything says 'success', but root checker is showing no root. I had force closes on the System UI before rebooting it a second time.
I tried it straight from a factory reset, just to be sure, same issue.I'm on 3.2.1 on this Vtab.
Not sure what is missing? Anything I should check?
unqualified said:
Everything seems like it works, everything says 'success', but root checker is showing no root. I had force closes on the System UI before rebooting it a second time.
I tried it straight from a factory reset, just to be sure, same issue.I'm on 3.2.1 on this Vtab.
Not sure what is missing? Anything I should check?
Click to expand...
Click to collapse
What os do u use? Check if adb is working
_________________________
tapatalked from GalaxyS3
unqualified said:
Everything seems like it works, everything says 'success', but root checker is showing no root. I had force closes on the System UI before rebooting it a second time.
I tried it straight from a factory reset, just to be sure, same issue.I'm on 3.2.1 on this Vtab.
Not sure what is missing? Anything I should check?
Click to expand...
Click to collapse
I had this problem also in the first time .. try to check if java is installed and working well .. try to check if ADB driver is identified on ur pc ..
I am thinking it is just a java problem .. did u type the commands in the shell " just wondering " this will not work if u didnt type the commands and follow the steps ..
vinogans said:
I had this problem also in the first time .. try to check if java is installed and working well .. try to check if ADB driver is identified on ur pc ..
I am thinking it is just a java problem .. did u type the commands in the shell " just wondering " this will not work if u didnt type the commands and follow the steps ..
Click to expand...
Click to collapse
Thanks for all the suggestions! I was surprised so many people responded on such a forgotten tablet.
I did enter the two commands in the shell (copied and pasted the exact commands) at the appropriate times, and they appeared to work.
I wasn't able to do the ADB setup exactly per the link on the OP, because my computer already recognizes the VTAB1008 under debugging mode, and runs ADB. If I try to uninstall and manually install the generic driver from the Skinny Root zip, it re-discovers and says the current driver is 'more current'. However, since 'adb devices' recognizes the vtab, and all the commands appear to be working, I should be good to go with ADB, right? Or is the generic driver from the Skinny Root zip file a critical component?
I also uninstalled Java SDK for x86 and re-installed for 64 just in case, but that didn't fix it.
Also tried disabling antivirus, no luck...
Is there a basic way to check whether java is working correctly? Or to read the java output as it is running the commands? Maybe something would show up there.
Thanks again
Do u see superuser app installed? If so, what does it output when you open it?
_________________________
tapatalked from GalaxyS3

Categories

Resources