Database Info

[HowTo] Native Ubuntu - Post Install Questions Here not in [DEV]

PLEASE DO NOT POST QUESTIONS ON HOW TO GET THIS TO WORK IN THE [DEV] Native Ubuntu !! THREAD... POST THEM HERE
I would like to thank all those who spent a lot of time working on this project. I do not have the required skills and have not contributed other than writing this tutorial. This is a combination of steps and files from the Nvflash unbricking released! and [DEV] Native Ubuntu !! threads. Please thank those who brought this to us!
The download contains the windows drivers and dlls for this to work (thanks to Bumble-Bee (Apache14), rayman84) and my edits of Jhinta's scripts flash.sh and restore.sh. All I did was convert the coding from linux to windows.
Downloads are in the first post of the DEV forum with the newest version from 15 July.
Disclaimer:
Please be aware that this may cause your transformer not to boot. If this happens please see the Nvflash thread above to restore to Prime 1.4. After this you can install a recovery to flash any rom you want. YOU COULD LOSE ALL YOUR DATA but if all goes to plan you will not. Neither I nor any of the devs are responsible for any damage or loss of data.
This should not affect any data from your Android Install.
It only changes the boot.img and boots a root file stem that is located on the removable Micro SD card. When restoring android this will restore the boot.img (from prime) which will allow you to boot into your android ROM without making any changes.
Tutorial:
Backup!!
Code:
1. Backup everything
Download and unzip required files
Code:
2. Download Nvflashtf.zip file above (files from 10 Jul 2011) and unzip
3. Download the rootfs and unzip (available in [URL="http://forum.xda-developers.com/showthread.php?t=1147062"][DEV] Native Ubuntu !![/URL])
4. Place unzipped rootfs.ext2 in /removable/microsd/Ubuntu
(You will need to create the ubuntu folder)
Boot into APX mode
Code:
5. Plug your transformer into your computer using the USB cable
6. Shut down your transformer (cable must be plugged in)
7. Boot into APX mode: Hold down the Vol+ and Power buttons.
The screen will not turn on but the computer will recognize the transformer
Install Windows Nvflash Driver
Code:
8. Install the new drivers provided in the download folder
(Control Panel --> Device Manager --> APX Device -->
Update Driver --> Choose from file --> Navigate to unzipped Nvflashtf folder
--> Select usbpcdriver directory
9. Accept the warning message stating the driver is not signed
Install Ubuntu boot.img
Code:
10. If it is not already, Put transformer into APX mode (steps 5-7)
11. Navigate to the unzipped nvflashtf folder
12. Run (Double Click) flash.bat
13. Transformer will Say "!!!!!phone update successful!!!!!"
14. Eject APX device from windows
15. Reboot Transformer (Hold Power for 10 seconds) then press power
Connect to an Open Wifi Access point
Code:
16. Open Terminal and run
sudo ifconfig eth0 down
sudo iwconfig eth0 mode managed
sudo iwconfig eth0 essid "my network"
sudo ifconfig eth0 up
Open WICD Manager and click connect
Password is astf101
If your network uses encryption see the second post
Revert to Android boot.img
Code:
1. If it is not already, Put transformer into APX mode (steps 5-7)
2. Navigate to the unzipped nvflashtf folder
3. Run (Double Click) restore.bat
4. Transformer will Say "!!!!!phone update successful!!!!!"
5. Eject APX device from windows
6. Reboot Transformer (Hold Power for 10 seconds) then press power

Tips and Tricks
Working
Code:
Wifi - using terminal commands
Audio - Headphone Output only
Touchscreen
USB Host
Not Working
Code:
Touchpad (on dock)
HDMI Audio Out??
Speakers
Battery Stats
For future development including fixes being worked on please see the [DEV] thread
Scan for wireless networks
Code:
iwlist eth0 scan
Connect to encrypted networks
Code:
WPA:
sudo ifconfig eth0 down
sudo iwconfig eth0 mode managed
sudo iwconfig eth0 essid "nameofmyrouter"
sudo iwconfig eth0 key s:mypassword
sudo ifconfig eth0 up
[URL="http://forum.xda-developers.com/showpost.php?p=15528059&postcount=252"]WPA2[/URL]: thanks to belzebub40k
Automated Script for Wifi on Boot: Thanks to lugiber
advanced iwconfig information
Changelog
If you have any tips and tricks please post them here or PM me.

suggestion: maybe post the bugs/ working/ and being worked on. * just saying, so not so much clutter in this thread

I was building this very kind of zip archive and instructions for it earlier but got interrupted. I'm waiting for my backordered dock to arrive before I try ubuntu. This will be helpful.

Just to confirm then, you would need to switch the boot image via PC when you wanted to switch OS then?
BTW - thanks for the writeup, and directing traffic out of the dev thread.

DroidxRage said:
Just to confirm then, you would need to switch the boot image via PC when you wanted to switch OS then?
BTW - thanks for the writeup, and directing traffic out of the dev thread.
Click to expand...
Click to collapse
yep. 10 characters

Wow...this looks totally manageable. Thanks for the Guide!

What file system does the (micro) SD card need to be? I heard in the dev thread that it only works with FAT32, which would suck since it has a 4 GB limit (and I have a 16 GB card).

rdnetto said:
What file system does the (micro) SD card need to be? I heard in the dev thread that it only works with FAT32, which would suck since it has a 4 GB limit (and I have a 16 GB card).
Click to expand...
Click to collapse
no sir FAT had 4 GB limit. You are good with 16GB FAT32.
I'm loving 3.1 right now. I may try this down the road.

EDIT: Disregard this post =.= I managed to post in the wrong thread... might fill this in later...

EDIT: Alright... I managed to mis-post again... I'm really sorry for spamming your thread, OP, I must look like an idiot. Can someone please remove my posts... these were meant for the developement Ubuntu thread

ToyTank said:
no sir FAT had 4 GB limit. You are good with 16GB FAT32.
I'm loving 3.1 right now. I may try this down the road.
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/FAT32 said:
The maximum possible size for a file on a FAT32 volume is 4 GiB.
Click to expand...
Click to collapse
You must be thinking of the volume size. The file size limitation is the main reason everyone uses NTFS on Windows these days (improved access controls being the other reason).
The filesize limitation is why MS went to the trouble of creating exFAT - FAT32 can handle TB sized volumes, and journalling file systems like NTFS shorten the lifespan of flash media.

GadgetViews said:
suggestion: maybe post the bugs/ working/ and being worked on. * just saying, so not so much clutter in this thread
Click to expand...
Click to collapse
I wish I could do this, but unfortunately this will only be updated in the DEV thread. I will try to add some things in the second post to help with this.

rdnetto said:
What file system does the (micro) SD card need to be? I heard in the dev thread that it only works with FAT32, which would suck since it has a 4 GB limit (and I have a 16 GB card).
Click to expand...
Click to collapse
Main thing was buidling it , now add and fix optional things.
soon

When restoring to android, it restores the previous system state, or a fresh install of prime?
Are there any developments in order to make a dual boot mode along with standard Android?
This kind of implementation are great: http://www.alwaysinnovating.com/, allowing switch between os without restart. I would love to see some thing like this in the transformer.
Good work!

That stuff is kinda secondary. They're mostly trying to get ubuntu fully working right now. But if you have any good ideas for a dual boot process please share. Also it restores the previous rom on. It never actually touches the system or data partition.
Sent from my HTC Vision using XDA Premium App

Where is ubuntu installed? Internal mem? and can we you it with just the touchscreen? I haven't bought a keyboard yet.

SwiftLegend said:
Where is ubuntu installed? Internal mem? and can we you it with just the touchscreen? I haven't bought a keyboard yet.
Click to expand...
Click to collapse
It's ran from the root.fs on your sd card. The actual sdcard.
Sent from my HTC Vision using XDA Premium App

david279 said:
That stuff is kinda secondary. They're mostly trying to get ubuntu fully working right now. But if you have any good ideas for a dual boot process please share. Also it restores the previous rom on. It never actually touches the system or data partition.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I will update the OP to more prominently reflect that this does not modify the current install of android other than the boot.img

So far, mp3 playback and sound is very good. I have a question about the flash plugin, I recall that the Jhinta had a snapshot of Youtube up. I am unclear how to get the plugin, has anyone else gotten this working? Thanks in advance, loving this!

[US/WW/JP/TW/DE/TB] One-Click Universal root for stock firmware - V4

Here I am again...
This time I have written a shell script (linux only) and made a live-cd (for all windows/linux users) to automatically root the stock firmware on the TF101. Every stock firmware.
Today in Europe Asus rolled out the 3.2 upgrade. If you are on stock and you have alredy upgraded then download attached tar file and do as follows:
NOTE: Unfortunately, this script won't work with the latest revision of TF101 (3G version, B80 and some B70)
NOTE2: As someone pointed out (thank you Pieter) you need to be root on your linux box in order to make it work.
Code:
tar -xvf universal.tar
cd universal
./universal.sh
In Ubuntu the last command would be:
Code:
sudo ./universal.sh
Follow the instructions and you're done.
If you have a stock US/DE/TW/JP/TB firmware you can do the same.
If you are running an older version of Honeycomb the process is the same.
When ASUS will pull out another upgrade... same commands as above.
So this probably is the closest thing to one-click-root for the Transformer.
This won't install custom rom/CWM/strange other things (V2 version added the support for CWM); it's only root.
I've tested this morning after the 3.2 upgrade and it worked like a charm.
However this is in testing stage so, as always, if you brick/ruin/burn/crash something don't blame on me.
This package includes the Bootunpack tool, courtesy of Rayman84
LIVE CD INSTRUCTIONS
It's based on slitaz (http://www.slitaz.org/).
Burn the image into a cd or if you want it on a thumb usb drive follow this (http://doc.slitaz.org/en:guides:liveusb).
Put the cd/usb in your pc and reboot.
Follow the indication on screen (for setting locale and keymap).
When the desktop shows up, double click on "Universal Root for ASUS TF101".
Again follow the indication and you'll be ok.
For a guide on how to boot from cd/usb try this: http://www.passwordunlocker.com/knowledge/change-bios-settings.html
or search with google.
The option to install a stock boot/recovery (added on V3) is working even if not fully tested.
The program has correctly rebuilt a stock recovery on my WW version.
From version V4 root checker correctly says that the rom is not rooted after you do an unroot.
If you like the work i did take a look at that funny button under my name with the "donate to me" caption
Seriously, I appreciate even only a "Thanks".
FAQ
[Q] I'm running on Windows, how can I burn the live-cd?
[A] Try with cdburnerxp (it's the easiest way).
You can download one installer frome here:
http://cdburnerxp.se/en/download
or the portable package if you don't want to install other software:
http://download.cdburnerxp.se/portable/CDBurnerXP-4.3.8.2568.zip
Start the program (for the portable version the file is cdbxpp.exe) and click on "Burn iso image". Then select the .iso file you have downloaded and click "burn disk". All Done.
[Q] How can I reboot in APX/recovery mode?
[A] Do as follows:
VOL UP + POWER BUTTON for ~5sec = boot in APX mode. The screen will stay black as if it is turned off. This mode is used only when you use nvflash to flash boot/recovery/data partition (this is the first step in my script).
VOL DOWN + POWER BUTTON ~5sec = will appear a screen where it says to press vol down again to wipe all data (obviously you don't want to do it now), or press up to enter RCK (recovery mode). If you installed CWM you will see the main menu navigable with vol up / vol down / power button.
If you have the stock recovery you will see a green android with a esclamation mark on a yellow triangle.
[Q] Help! I can't reboot in recovery mode!
[A] I think the main problem here is that it is a bit tricky to get into CWM recovery, once you see the small text come up don't try to read anything, just hit volume up.
Hold volume down plus power until the text in upper left shows,if you let go too early it just boots up and you never see the text. If you wait too long you don't get the option to boot into recovery. Hope that helps..
Thx to ckuke4 for this answer http://forum.xda-developers.com/showpost.php?p=16306342&postcount=60
[Q] The live-cd gave me this error: "connection failed NvError 0x8" what is it?
[A] This means that either you are not in APX mode (read above), or that you have one of the latest revision of the tf101 (B7O) which have an unknown (for now) sbk.
For what i know, there's no knew method for rooting your device.
Maybe someone will find a way, but for now you have to be patient.
[Q] I'm running your scripts from my linux box, but it keep me saying "Permission Denied". Why?
[A] You need the root privileges on your local machine.
If you are running Ubuntu:
Code:
sudo ./universal.sh
[I](it will asks for your password)[/I]
If you are running another linux distro:
Code:
su
[I](it will asks for your password)[/I]
./universal.sh
[Q] I have rooted my tablet with this method, but I can't find the superuser app and Titanium Backup says that I am not rooted.
[A] The root script will asks you to reboot your tablet, make sure that usb debugging is turned on and then press any key.
You have to wait until you see a little bee on the bottom right of your tablet's screen, near the clock. Then press any key.
[Q] I've installed CWM but every time i try to do a backup, it says it can't find sdcard. But my microsd card work fine with root explorer!
[A] Don't get me wrong but, are you sure?
In root explorer you see a sdcard folder but it's not your microsd, it's the internal memory (it's weird, i know). In root explorer the microsd card is mounted under the "/removable/microsd" folder. You should also see a little sd card icon in the bottom right, near the clock.
Also you need to make sure the card is formatted correctly. Try reformat it with this: https://www.sdcard.org/consumers/formatter_3/
Thanks to skeeterpro for the link (http://forum.xda-developers.com/showpost.php?p=16385872&postcount=6)
[Q] The live cd stops at the command prompt, I can't see the desktop.
[A]The live cd doesn't include every driver for every video card, mouse, keyboard, etc.. (keep in mind that the original slitaz livecd is only 30MB).
You can do all the process in the text console, it's not much more difficult.
If it asks for a login insert "tux" (without quotes).
At the command line enter the following:
Code:
cd
cd universal
./universal.sh
Then the magic will start. The unroot script is called ./unroot.sh
CHANGELOG:
V4:
- Corrected some text
- Added a link on the Desktop to this thread
- Added stock ramdisk for all SKU (though JP, CN and DE are not the latest versions) (thanks to kovla for the latest TB recovery)
- Added a script on the Desktop to increase the font size on the fly for those who are using a very high dpi monitor/tv.
- Changed compression algoritm. Now the iso is ~10MB smaller.
- Maybe I have found the way to make everyone read the faq...
V3:
- [BETA] added a second script to come back to stock.
V2:
- added the option to install CWM (thanks Roach!)
- more error check
V1:
First version
=====> DOWNLOAD LIVE-CD V4 - (Mirror)<=====
DOWNLOAD LIVE-CD V3 (previous version)
DOWNLOAD LIVE-CD V2
As always, keep your eyes open and
Have Fun!

Hey, how about an equivalent windows script for those who prefer msft's os. Ok?

awesome -one root to rule them all!

ondoy1943 said:
Hey, how about an equivalent windows script for those who prefer msft's os. Ok?
Click to expand...
Click to collapse
In linux there's no need for drivers to work with tf101.
Windows seems to be problematic with driver (for someone seems to be way too difficult install the right ones).
As i stated above, adding this to a live linux cd will be the final one-click-root (put a live cd/usb-memory on your computer, reboot, follow the easy instructions and you're rooted).
Sincerely I don't know how to modify a livecd to add these scripts and programs.
If anyone wants to try, he is welcome.
Anyway I don't plan to do a windows port of this.

Disappointed! No windows support!

Will probably be trying this method from my PCLOS partition, if I can hold off the OTA update which has just begun pestering me.
Got to find out whether the modded adhoc wpa_supplicant works with 3.2 first, thanks for the effort HF

Excellent, glad to avoid having to dig out my old Windows box to root the TF Would advise people to drop it, new Mint/Ubuntu is much nicer visually than Win7 and my startup times are fantastic, not to mention the slick media support.
Does you script give also install CWM?
Will give this a go later and see how it works.

belrik said:
Excellent, glad to avoid having to dig out my old Windows box to root the TF Would advise people to drop it, new Mint/Ubuntu is much nicer visually than Win7 and my startup times are fantastic, not to mention the slick media support.
Does you script give also install CWM?
Will give this a go later and see how it works.
Click to expand...
Click to collapse
I was thinking on it, but perhaps it's better no.
Installing cwm means no more ota, since the update relies on the stock recovery.
This script was meant to leave all as stock as possible.

For all the windows folks:
I have added to the first post a live-cd with all the necessary tools.
Just run it and you'll be fine. (anyway, you are always in time to switch to linux)

Hallo and thanks!!!
what about mac's Users?

Can you explain a bit about what it does? So we can all learn.
Thank you,

Hi !
Will it work under wmware or virtual pc ?

Sorry if this is a dumb questions, but would this work in Terminal in OS X?

RayYung said:
Can you explain a bit about what it does? So we can all learn.
Thank you,
Click to expand...
Click to collapse
So you wanna learn? Good!
First i learned how to root the stock firmware from here: http://forum.xda-developers.com/showthread.php?t=1125714 .
Essentially the steps are:
1 - download a modified boot image into the tablet
2 - install the su and superuser packages.
My scripts do these 2 steps. I wrote a small howto that explains how to modify a boot image (http://forum.xda-developers.com/showthread.php?t=1193737)
Caramel said:
Hi !
Will it work under wmware or virtual pc ?
Click to expand...
Click to collapse
scirio said:
Sorry if this is a dumb questions, but would this work in Terminal in OS X?
Click to expand...
Click to collapse
I really would like to have an answer to these questions...
The Mac should have a layer of compatibility with linux (can't tell you more), but i really don't know the mac world.
*Maybe* the live cd will work under virtual machine; there should be some options to enable the usb feature. In Virtual Box there's an option to enable the usb controller and an option to filter what device will be accessible to the guest os; don't know vmware and virtual pc.
I don't know if an Intel based Macintosh is able to boot from a x86 live-cd, you could try.
I'm sorry i can't help you much more.

scirio said:
Sorry if this is a dumb questions, but would this work in Terminal in OS X?
Click to expand...
Click to collapse
Oops- no- there is no Nvflash for Mac. Sorry.

Created a live usb, booted via windows, and voila i am looking at a linux desktop, which i have not seen for a long time. Started going to its paces to root my tf, but did not push thru to the end, in as much as my tf is already rooted beforehand. But i can sense that barring any unforeseen miscues by the |op|, this almost one-click rooting procedure should produce its desired result. Highly recommended; good job |op|.
Looks like this calls for an "unrooting" routine to complement the rooting process. How about it?

Nice script! I just completed one of my own for unrooting the TF
One thing: why not just use adb reboot recovery instead of telling them how to do it manually?

brando56894 said:
Nice script! I just completed one of my own for unrooting the TF
One thing: why not just use adb reboot recovery instead of telling them how to do it manually?
Click to expand...
Click to collapse
I have already tried this, but seems it doesn't work.
if i write "adb reboot recovery" or "adb reboot bootloader" my tablet reboot in normal mode.
It's more reliable do it manually.

how can install ClockworkMod recovery
i rooted my transformer with your one click tool from live cd.
if i want install ClockworkMod recovery how can do ?

zulu99 said:
i rooted my transformer with your one click tool from live cd.
if i want install ClockworkMod recovery how can do ?
Click to expand...
Click to collapse
For now if you are running on windows, you can use one of these methods:
http://forum.xda-developers.com/showthread.php?t=1125714
http://forum.xda-developers.com/showthread.php?t=1185104
you are already rooted, so just need the cwm.
Since i had many requests on adding cwm, i am going to update the scripts and live-cd for adding this feature.
I'll keep you updated.

[ROOT][TOOL]Qemu automated root [09/18/2012]

This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC

Latest Supported Versions:
v7.1.5
Recent user reported supported version
v7.2.1

Awesome, want to try it when I receive my HD 7 this week...

Wrong thread sorry about that

Works perfectly. Thank you!
Sent from my KFTT using XDA Premium HD app

sparkym3 said:
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Click to expand...
Click to collapse
Hi sparkym3!
Thanks for your tools!
I love your tools in TF300 and TF700!
One questions about TF300, do you know anything about the APX mode and useful tools in APX mode?
---------- Post added at 06:41 PM ---------- Previous post was at 06:05 PM ----------
sparkym3 said:
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Click to expand...
Click to collapse
Hello, sparkym3!
Is there some mistake in the tool? Both the step 3 and step 5 are the same...
Code:
Step3:Checking for access...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
Code:
Step5:Checking superuser...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT

padest.com said:
Hi sparkym3!
Thanks for your tools!
I love your tools in TF300 and TF700!
One questions about TF300, do you know anything about the APX mode and useful tools in APX mode?
---------- Post added at 06:41 PM ---------- Previous post was at 06:05 PM ----------
Hello, sparkym3!
Is there some mistake in the tool? Both the step 3 and step 5 are the same...
Code:
Step3:Checking for access...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
Code:
Step5:Checking superuser...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
Click to expand...
Click to collapse
Both of those lines are checking for the "#" instead of the "$" to ensure that it has root access.

reverendkjr said:
Both of those lines are checking for the "#" instead of the "$" to ensure that it has root access.
Click to expand...
Click to collapse
Thanks.
I get it.

ADB is unresponsive
androitri said:
Awesome, want to try it when I receive my HD 7 this week...
Click to expand...
Click to collapse
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:35 AM ---------- Previous post was at 08:39 AM ----------
PMcHargue said:
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
Click to expand...
Click to collapse
got it. My file,
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7

PMcHargue said:
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:35 AM ---------- Previous post was at 08:39 AM ----------
got it. My file,
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
Click to expand...
Click to collapse
Interesting, I don't even have that file. I assume it is used to block devices so you could have one plug in for charging and ADB would just ignore it if it is not in the list.

Thanks, sparkym3
After I verified that ADB could see the KFHD7, I ran the 'RootQemu.bat' that was part of what you published. While it took a bit of time (about 1 minute) between reboots, it worked flawlessly. The Kindle Fire HD 7" I have is now rooted. I'll be looking next to replace the launcher, (probably Apex) and scrape the ads off of this.
Pat

Thanks
Thank you so much for this... really makes it easy and fast. However i was worried during the installation haha my device kept rebooting and it warning me to reconnect so i thought i was doing it wrong.

Well it seems that I messed up. Big time.
I got to step 3, and that's where all hell breaks loose. I get message on the cmd window which reads Cannot find specified file, and everything goes downhill from there. There's no more updating whatsoever. But that's not the bad part, I tried messing around with my kindle, and everything is now incredibly slow. The lag is unbearably bad. I'm in process of resetting everything to factory default at this moment.
EDIT: Just reset to factory default, everything is smooth again, but be careful when trying this exploit, things can go wrong!
I'm thinking there was something I did wrong, if this seems unfamiliar I'll list the steps I took in trying to manage everything. But I know you're thinking I did this on impulse, hence my low post count, but I have been lurking the kfhd subforum for a very long time now and have tried my best to educate myself. Sorry.

Vespus said:
I tried messing around with my kindle, and everything is now incredibly slow. The lag is unbearably bad.
Click to expand...
Click to collapse
That’s the result of the entry in /data/local.prop. If you remove that file and reboot, it will fix the lag.

I tried running the tool and it kept getting hung up on step 3, telling me something along the lines of file not found. I was able to root using the manual method though.

nvrmore100 said:
That’s the result of the entry in /data/local.prop. If you remove that file and reboot, it will fix the lag.
Click to expand...
Click to collapse
I suppose my method fixed it regardless
I'm thinking the reason my root backfired is because I wasn't as systematic as I should have been. Rooting my samsung vibrant allowed me to be a little more sloppy since there are backups and flashing is a cinch.
EDIT: This my 3rd time trying to get this thing to work, I get stuck on Step 3 "The system cannot find the file specified."
I really can't see how I'm managing to screw up this badly. Must be something stupid on my part.
EDIT2: Turns out I was using a crumby network directory the whole time, but even still it did not work. Fellows: Put the QemuRoot folder somewhere on your desktop, it's easier there. But after that the prompt would close immediately after step 4, so that took me a while to circumvent. Anyway, I ended up skipping to step 4 to get the superuser to work. I'm fairly sure everything DOES work, but it's hard to test right now.

PMcHargue said:
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:35 AM ---------- Previous post was at 08:39 AM ----------
got it. My file,
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
Click to expand...
Click to collapse
That's right! I have tested!
This is needed!!!

Thank you for work and contribution.

Thanks for the tip
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
worked!

KF HD has Superuser but no root access
sparkym3 said:
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Click to expand...
Click to collapse
Hi sparkym3
Thanks for all your hard work! I tried it though and it went through all the motions as if it was doing its job, like expected. But at the end of the rooting, I have superuser on the kf HD but no root access! ES explorer and Titanium have no root access. Tried rebooting several times. Still no root access. What could have gone wrong?
Cheers, mate!

How to download the latest ADB/Fastboot binaries without the sdk?

I want to download the latest possible ADB/Fastboot binaries because a little bird whispered in my ear that the Asus USB ID's have been added so -i 0x0b05 isn't needed when using fastboot on the TF201.
Anyways, I do NOT use the "android-sdk" nor have I ever downloaded it. I simply used a tool called knives and forks which put the binaries in system32/syswow64 and then somehow symlinked them to always respond when typing "adb" in CMD regardless of where i start the CMD. I don't need to cd to an android-sdk folder (I don't even have one, derp)
So how can I update to the latest binaries WITHOUT downloading the sdk?

removed

shabbypenguin said:
while not the most ideal answer, i work on a lot of low end devices and in an effort to keep it simple for em i bundle up the binaries needed for most devices. normally i have adb for all 3 platforms and fastboot for all three. ive yet to update the mac and linux binaries but my zip does have the latest windows adb/fastboot
www.Shabbypenguin.com/OUDstuff/Tools/ADB-Tools.zip
Click to expand...
Click to collapse
Much obliged!

Thank you! You just saved me from a 2-3hr download tethered to my phone!

shabbypenguin said:
while not the most ideal answer, i work on a lot of low end devices and in an effort to keep it simple for em i bundle up the binaries needed for most devices. normally i have adb for all 3 platforms and fastboot for all three. ive yet to update the mac and linux binaries but my zip does have the latest windows adb/fastboot
www.Shabbypenguin.com/OUDstuff/Tools/ADB-Tools.zip
Click to expand...
Click to collapse
I've been frustrated with error: device offline.
My SDK manager is still downloading stuff & I found this thread.
Latest adb helps!!!
Thank you so much.

dsymbol said:
I've been frustrated with error: device offline.
My SDK manager is still downloading stuff & I found this thread.
Latest adb helps!!!
Thank you so much.
Click to expand...
Click to collapse
that zip is old, instead http://androidforums.com/faqs/443072-adb-guide-updated-2013-05-21-a.html#post5389081
use teh attached file there. chances are the device offline is due to outdated adb and a 4.2 device.

shabbypenguin said:
that zip is old, instead http://androidforums.com/faqs/443072-adb-guide-updated-2013-05-21-a.html#post5389081
use teh attached file there. chances are the device offline is due to outdated adb and a 4.2 device.
Click to expand...
Click to collapse
you're absolutely correct.
i've updated to 4.3 & run into device offline problem.
Your adb 1.0.31 helps. in less than 5 mins, while i've been sitting here for 3 hours waiting for the SDK manager to update files.

Thanks for this!

[Q] Toshiba AT300SE-101 root

Hi,
Can I root my toshiba AT300SE-101 ?
Regards,

sdancer said:
Hi,
Can I root my toshiba AT300SE-101 ?
Regards,
Click to expand...
Click to collapse
Your lucky day
http://forum.xda-developers.com/show...php?p=42594876

Describe the steps
tasos66 said:
Your lucky day
http://forum.xda-developers.com/show...php?p=42594876
Click to expand...
Click to collapse
Tassos, can you please describe the steps you followed ?
Also verify or better upload the appropriate files to an upload server like rapidshare.
1) I changed the usb connection to debugging mode from settings of my tablet [AT300SE-101]
2) I installed the toshiba's WinUsb Driver [successfully installed]
3) I executed the motochopper's script run.bat and responded as this
deamon not running.starting it now on port 5037 *
deamon started successfully
stays here and nothing more !!

sdancer said:
Tassos, can you please describe the steps you followed ?
Also verify or better upload the appropriate files to an upload server like rapidshare.
1) I changed the usb connection to debugging mode from settings of my tablet [AT300SE-101]
2) I installed the toshiba's WinUsb Driver [successfully installed]
3) I executed the motochopper's script run.bat and responded as this
deamon not running.starting it now on port 5037 *
deamon started successfully
stays here and nothing more !!
Click to expand...
Click to collapse
Did you try using ADB Wifi? I've been able to do stuff with ADB wifi before. Not sure if this will work or not...but it's something worth trying..

sdancer said:
Tassos, can you please describe the steps you followed ?
Also verify or better upload the appropriate files to an upload server like rapidshare.
1) I changed the usb connection to debugging mode from settings of my tablet [AT300SE-101]
2) I installed the toshiba's WinUsb Driver [successfully installed]
3) I executed the motochopper's script run.bat and responded as this
deamon not running.starting it now on port 5037 *
deamon started successfully
stays here and nothing more !!
Click to expand...
Click to collapse
If you get this message and stack, then the adb driver is not installed correctly.
Connect the tablet to the computer.
Go to device manager, find an unknown device, right click and select update driver, select browse the computer for the driver and guide it to the folder you placed the adb driver.
When the unknown device mark is gone, you are ready to try again.
Use the following Motochopper http://mirror21.downloadandroidrom.com/download/GalaxyS4/root/motochopper.zip?token=

I dont know whats the problem.... but dont work

tasos66 said:
If you get this message and stack, then the adb driver is not installed correctly.
Connect the tablet to the computer.
Go to device manager, find an unknown device, right click and select update driver, select browse the computer for the driver and guide it to the folder you placed the adb driver.
When the unknown device mark is gone, you are ready to try again.
Use the following Motochopper
Click to expand...
Click to collapse
Hi
I already did this and win7 recognise the device as android Device --> Android ADB Interface. It says that this device works just fine.
Model Number AT300SE
Android version 4.1.1
Kernel version 3.1.10-00037-g59264fc
Build number JRO03C.000122808.95
Despite of that, in my computer device list i dont see anything only in the device manager as described before.
PS:How to work with ADB wifi ?
Sent from my AT300SE using xda app-developers app

tasos66 said:
If you get this message and stack, then the adb driver is not installed correctly.
Connect the tablet to the computer.
Go to device manager, find an unknown device, right click and select update driver, select browse the computer for the driver and guide it to the folder you placed the adb driver.
When the unknown device mark is gone, you are ready to try again.
Use the following Motochopper
Click to expand...
Click to collapse
Finally, I used another PC and it worked flawlessly !
Now my Toshiba AT300SE-101 is rooted !!
Thank you Tassos from Greece !! I am from Greece too ([email protected] city)
Best Regards,

sdancer said:
Finally, I used another PC and it worked flawlessly !
Now my Toshiba AT300SE-101 is rooted !!
Thank you Tassos from Greece !! I am from Greece too ([email protected] city)
Best Regards,
Click to expand...
Click to collapse
Γεια σου πατρίδα!
Thessaloniki city.

So I decided to resurrect this old tablet and turn it into a digital photo-frame. Decided just to reset it to factory settings. Easily done. I noticed there were no firmware updates. It is stuck on Jellybean. That can't be right, surely. A tablet that doesn't update to at least one new Android update!!