Database Users

[Tutorial] Wonderfully Root 6.2.1 with SuperOneClick, ADB, kindleroot_androidpolice

The method is similar to the original Root tutorial before but with help of kindleroot_androidpolice.apk released from http://www.androidpolice.com as more obstacles in 6.2.1.
1. Download kindleroot_androidpolice.apk
http://www.androidpolice.com/2011/1...on-kindle-regardless-of-its-software-version/
2. Copy kindleroot_androidpolice.apk to your Kindle Fire device and install it.
3. Run it! Click Agree > You Rock > Root
4. Now you can connect your Kindle fire to your PC with USB line.
For the Windows System:
Start > Run > CMD
Code:
cd C:\Program Files\Android\android-sdk\platform-tools
(I installed the SDK by default so you can see my directory above that way)
If you installed your SDK to C:\Android then you should
Code:
cd C:\Android
If you download some guy's package for ADB and unzipped it to C:\adb, simply you should enter command
Code:
cd C:\adb
5. Download the latest version for SuperOneClickv2.3.2-ShortFuse from official site http://shortfuse.org/?p=171
Unzip the package and Run SuperOneClick.exe
Click Root Button
Unfortunately you will find that the commands will stop at WaitForDevice.
What should we do now?
6. Don't be panic! Just Run these lines in your command window:
Code:
adb root
adb kill-server
adb remount
Everything is okay now and the commands will be continued to END
Root completely
You can check SuperUser working well again on your KF
Screenshot images and package files are post in a Chinese Kindle Fire Forum, just check them at:
http://www.92kindle.com/thread-2905-1-1.html

Damn I think I'm gonna try that after installing 6.2.1 but it better work.
Sent from my Kindle Fire using Tapatalk

Anyone tried this method yet and can confirm that it works?

The method on androidpolice works. I am running 6.2.1 rooted right now!

Course BurritoRoot works, with a name like that it has to
edit
trollololololol

Actually this method works better. There seems to be a problem with the su program on androidpolice. It gives root alright but some programs don't get root access for some reason. SuperOneClick works better.

jlocohustler said:
Actually this method works better. There seems to be a problem with the su program on androidpolice. It gives root alright but some programs don't get root access for some reason. SuperOneClick works better.
Click to expand...
Click to collapse
i dont know if u read! but superoneclick was broken after last update, and jcase was nice enough to root this blindly so we could root !!!

jlocohustler said:
Actually this method works better. There seems to be a problem with the su program on androidpolice. It gives root alright but some programs don't get root access for some reason. SuperOneClick works better.
Click to expand...
Click to collapse
SuperOneClick can not root 6.21. Hence the use of BurritoRoot in the OP.
Methods to gain root are the same, since they use the same app to do it.
There was a problem with the su binary on AP but its been replaced.

I can verify the Android Police method works just fine without the SuperOneClick. Triedit twice, rooted then unrooted so I could watch Prime Video, then rerooted so I can install OTA Rootkeeper so I could watch video without unrooting. Only difference for me was I had SuperUser already from my pre-6.2.1 root but its the same as the the one AP distributes.
FYI my computer is a Mac so this was executed from shell.

Ibis, can you give me some more information on how you did this on a Mac?
I tried and it seemed to work but don't think it took as I cant copy the framework Apk to system/apps and when I try to run market it force closes with a vending error.

What am I doing wrong?

I have updated the drivers on my kindle through ADB so now on my x64 Windows 7 it showes up as an Android phone USB driver/device but when running Adb Devices in the cmd through ADB no devices appear. I don't have the SDK or anything do I need it? Help if possible please .

Use this: http://forum.xda-developers.com/showthread.php?t=1399889

When installing the drivers for the Kindle Fire Utility the CMD windows says can not find the path specified.

[Q] 6.2.2 Root Mac?

Has anyone been able to successfully root the KF on 6.2.2 using Mac OSX Lion, I have tried numerous times and have failed , I haven't found any posts or tutorials either. Any help?

kfu for mac/linux:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
you would have to patch it like the windows version:
http://forum.xda-developers.com/showthread.php?p=21602553#post21602553

I rooted it on mine, you have to update the drivers and some different commands. Biggest problem for me was adb
Sent from my Amazon Kindle Fire using xda premium

Is there any step by step for it?
I rooted my EVO no problem and I know how to use ADb to push pull etc but that damn KF doesn't want to show up on ADB

If adb doesn't see it on your mac, do
mkdir ~/.android
echo 0x1949 >> ~/.android/adb_usb.ini

ADB wont see kf

I've tried every way on the kfu post and no go. anyone have a simple method they r willing to share?

did you have the .android in your home directory?
how windows recognize your kf?
what room do you have installed?

ADB not recognize KF
deathisonlyfreedom said:
I've tried every way on the kfu post and no go. anyone have a simple method they r willing to share?
Click to expand...
Click to collapse
I am having the same problem, tried all methods, tried all different windows OS.
Device manager recognize KF as ADB device/interface, but when check list under ADB command prompt, it's not there. Can't run KFU to root.
Please help, anyone.

.android folder in your home dir and adb_usb.ini with 0x1949 and 0x18d1 entries in it in the folder

b63 said:
.android folder in your home dir and adb_usb.ini with 0x1949 and 0x18d1 entries in it in the folder
Click to expand...
Click to collapse
I don't know, I am at work, when I get home I will check for those. Thanks.

Have you installed the Android SDK and the Android USB Drivers? I was rooting my KF and forgot about this, installed it and it worked perfectly.

mugabuga said:
Have you installed the Android SDK and the Android USB Drivers? I was rooting my KF and forgot about this, installed it and it worked perfectly.
Click to expand...
Click to collapse
I did install USB driver but not Android SDK. I did install Kindle ADB though.

just a hint: if you download the latest kfu there is everything you need - the drivers and all necessary commands in the tools folder (ie with sdk you have to get the fastboot command as it is not included) - you don't need the sdk at all and save a lot of time and space

The newest Krupp does indeed fix the not found issues
Sent from my Kindle Fire using Tapatalk

jgdovin said:
The newest Krupp does indeed fix the not found issues
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Where can I find that "newest Krupp"???
@b63: Attached are the pictures I captured, please look at them and tell me what I did wrong, how to fix it?
Thanks, bro

[Solved) Need Help - I have formatted my Nex7 using TWRP

Hi,
I have been trying to educate myself by using TWRP (ver 2.3.2.1) and loading custom ROM's
I have used the format option in TWRP and now I can no long load or push any files to the SD card. I am able to use WegFresh Root Tool Kit (ver 1.6.1) and get to TWRP and to the bootloader (Android laying on it's back - chest open)
How do I re-create the proper file structure to be able to load ROM's once again. As an example..... "/system" is completely empty.
Thank you....
Update - The problem has been solved and it was due to the driver between my laptop and the Nex7. In Device Manager it was showing up as "Andriod Phone - Andriod Bootloader Interface" THIS WILL NOT WORK!
Your device manager has to say - "Android Phone - Android ADB Interface" for it to be able to push files to the Nex7
Thanks to all who helped me.

Have you reflashed your ROM of choice?
- Sent from my US Cellular SGS3

RMarkwald said:
Have you reflashed your ROM of choice?
- Sent from my US Cellular SGS3
Click to expand...
Click to collapse
Thank you for the reply. I am unable to push any ROM (zip file) using TWRP or adb push.....
When I use a DOS prompt and type - "adb push rom.zip /sdcard" I get a reply "error: device not found" It seems as thought I can't write any files to the sdcard since I formatted the sdcard. Is it a permission issue? How can I restore the proper file structure of the sdcard so that a rom can be pushed and loaded?
Thanks

Dekan54 said:
Thank you for the reply. I am unable to push any ROM (zip file) using TWRP or adb push.....
When I use a DOS prompt and type - "adb push rom.zip /sdcard" I get a reply "error: device not found" It seems as thought I can't write any files to the sdcard since I formatted the sdcard. Is it a permission issue? How can I restore the proper file structure of the sdcard so that a rom can be pushed and loaded?
Thanks
Click to expand...
Click to collapse
How does the device show up in Device Manager? I assume you're using Windows.
- Sent from my US Cellular SGS3

Yes - I am using Windows 8 (64bit)
In Device Manager it shows as "Andriod Phone - Andriod Bootloader Interface"
I have no OS on the NEX 7 so I can't turn "debug mode" on......
TWRP see the device id......
Thanks

Dekan54 said:
Yes - I am using Windows 8 (64bit)
In Device Manager it shows as "Andriod Phone - Andriod Bootloader Interface"
I have no OS on the NEX 7 so I can't turn "debug mode" on......
TWRP see the device id......
Thanks
Click to expand...
Click to collapse
I've heard that Win8 causes issues, specifically with fastboot flashing files. I've heard you can install the drivers and is recommended to turn off driver signing.
Debug mode only works when the device is booted in the OS, not recovery. Do you have access to another OS, like Linux or Win7? This may be easier to do.
- Sent from my US Cellular SGS3

I will fire up my old Win 7 laptop in the morning and give that go.....
Thank you for your help this evening.

Dekan54 said:
I will fire up my old Win 7 laptop in the morning and give that go.....
Thank you for your help this evening.
Click to expand...
Click to collapse
No problem! The reason I've suggested this is I've worked with someone for three hours and in the end it was Win8. Win7 worked in minutes.
Good luck! Post with an update!
- Sent from my US Cellular SGS3
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
And honestly, I'd flash to stock 4.2.1 from Google, re-root, flash recovery, then flash ROM of choice. With the latest version of Recovery of your choice you shouldn't run into this issue in the future.
- Sent from my US Cellular SGS3

if still not working reflash stock rom from google
Sent from my Nexus 7 using XDA Premium HD app

ngoralph said:
if still not working reflash stock rom from google
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I would love to reflash any rom.... (cwm 10, Google, etc....) but my NEX7 will not except (push) any files to it. If I could just get a rom.zip file over to it I could then load it via TWRP.
I am open to suggestions from anyone.
Thanks

RMarkwald said:
No problem! The reason I've suggested this is I've worked with someone for three hours and in the end it was Win8. Win7 worked in minutes.
Good luck! Post with an update!
- Sent from my US Cellular SGS3
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
And honestly, I'd flash to stock 4.2.1 from Google, re-root, flash recovery, then flash ROM of choice. With the latest version of Recovery of your choice you shouldn't run into this issue in the future.
- Sent from my US Cellular SGS3
Click to expand...
Click to collapse
Just an update....
I am getting the same results with Win7 OS that I was getting last night when you were helping me. My Nex7 is displayed in the device manager as - "Android Phone - Android Bootloader Interface" in Win7 just as it is in Win8.
I have been using Wegfresh's Nexus Root Toolkit (1.6.1). It will show me the device ID went I click the button - show device id. I am able to reboot into bootloader. I am able to boot into recovery and get to TWRP and navigate around.
If I could just get a stock or custom ROM file to the NEX7 I would be in good shape. But I am unable to "adb push" anything to the nex7.
I will be glad to go "step by step" to trouble shoot this with you.
Thanks

I've not mypc, so I can't help you step by step.
You can use the advanced options of the toolkit to flash a zip or use the sdk to use the adb sideload.
google will help you to found how use "adb sideload", as the option you can see in recovery.
ADB Sideload
What is ADB sideload?
--------------------------------------------------------------------------------
ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. ADB sideload is a different ADB mode that you can use to push and install a zip using one command from your computer. Most likely ADB sideload won't be very useful for your average recovery user, but ADB sideload can be a huge time-saver for a ROM developer.
How do I use ADB sideload?
--------------------------------------------------------------------------------
1.Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher
2.Have newer ADB binaries installed on your computer. If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.
3.Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
4.From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.

Blackdragon77 said:
I've not mypc, so I can't help you step by step.
You can use the advanced options of the toolkit to flash a zip or use the sdk to use the adb sideload.
google will help you to found how use "adb sideload", as the option you can see in recovery.
Click to expand...
Click to collapse
Thank you for the reply. I have tried the "adb sideload" option in TWRP and it fails. I get the error - "error - device not found"
I welcome anyone who might have some idea's for me to try.
Thanks

Thy to see my edit upon how to run sideload.
You must not use the tookit, but you must install android sdk and use the true adb

Blackdragon77 said:
Thy to see my edit upon how to run sideload.
You must not use the tookit, but you must install android sdk and use the true adb
Click to expand...
Click to collapse
I will load the true adb sdk toolkit and give that a shot. Thank you for your help.

No problem! Tell me if that's the solution!
Inviato dal mio Nexus 7 con Tapatalk 2

I was having the same problem also. Correct me if I'm wrong, but I believe in Fastboot mode (Android laying on it's back - chest open), you cannot use adb. Here you can use Fastboot. Adb is use when in Recovery mode. Have you tried using fastboot.

Dekan54 said:
I would love to reflash any rom.... (cwm 10, Google, etc....) but my NEX7 will not except (push) any files to it. If I could just get a rom.zip file over to it I could then load it via TWRP.
I am open to suggestions from anyone.
Thanks
Click to expand...
Click to collapse
Do you connect your N7 with adb ? if yes, try the clockworkmod recovery v6.0.1.9 , it has a fuction very good to push rooms, it is the "instal zip from sideload"
---------- Post added at 08:25 PM ---------- Previous post was at 08:21 PM ----------
Dekan54 said:
I will load the true adb sdk toolkit and give that a shot. Thank you for your help.
Click to expand...
Click to collapse
follow this videos :
1º How to Install ADB Drivers for Google Devices
http://www.youtube.com/watch?v=vUSRmtexmUo
2º How To Install ADB and Fastboot for Windows
http://www.youtube.com/watch?v=Yc4z-KYypgY
it worked for me

tabbiex said:
I was having the same problem also. Correct me if I'm wrong, but I believe in Fastboot mode (Android laying on it's back - chest open), you cannot use adb. Here you can use Fastboot. Adb is use when in Recovery mode. Have you tried using fastboot.
Click to expand...
Click to collapse
You are correct, the OP needs to go into recovery (TWRP recovery is fine) and use adb to push files to the device- you can't use adb from fastboot.
I have used exactly the same method myself as I was in exactly the same situation myself.
Of course the OP needs adb on his PC from the SDK as mentioned earlier in the thread.

Still having the same error after installing adb from the sdk on my Win7 computer. I also made sure I installed JAVA and downloader the updates for the adb sdk.
The error is still - "error - device not found"
When I use TWRP to look at the files on my Nex7 the following folders are present
cache
data
dev
proc
res
root
sbin
sdcard
sys
system
tmp
usb-otg
default.prop
fstab.grouper
fstab.qcom
init
init.rc
ueventd.goldfish.rc
ueventd.grouper.rc
uevent.rc
The folder "sdcard is empty except for a twrp folder....
Any other things I should try?
Thanks