[Tutorial] Wonderfully Root 6.2.1 with SuperOneClick, ADB, kindleroot_androidpolice - Kindle Fire General

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.

Related

Having trouble rooting on Windows 7 64bit

I am having a bit of difficulty rooting my g2. I am not sure if its related to my os or not but i can not get it to work.
I have followed this and tried it all kinds of different ways.
addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/[/url]
I can get to my run command after doing all of that and it shows my serial number after typing adb devices but after that i can't enter any info in the sdk run command promt.
I have not been able to gain temp root yet because it won't let me enter the commands. I went to try to re-install java/sdk manager yet again and now it says java is not in the right path.
Any help?
If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.
martonikaj said:
If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.
Click to expand...
Click to collapse
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible
901-Memphis said:
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible
Click to expand...
Click to collapse
Yep let me grab a link for you (theres actually a video tutorial I wanna try and find). But basically instead of using ADB to push the files to the correct location, you just have to manually put the files in the right locations on the SDcard, which is where ADB pushes them anyways.
K so I followed this method: http://www.youtube.com/watch?v=tU9zn_BEth4
The files he refers to are in this thread: http://forum.xda-developers.com/showthread.php?t=833965
Now different people have had different issues with this. I personally had some issues where it tells you to run #sync, because my perm root wouldn't stick properly after reboot. If this doesn't work properly, I'm sure someone can help you with your drivers to get ADB working.
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.
If you got the adb devices command to work you are actually in good shape. You are supposed to enter all of the commands from what you are calling the "run command" prompt anyway (the one you used for adb devices).
martonikaj said:
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.
Click to expand...
Click to collapse
Unfortunately this won't work (if you don't want to use ADB, Visionary must be used to get temp root). ADB is needed in order to push the files directly to the phone. If you try copying the files to the SD card first, you won't have the correct permissions to copy the files to the phone in Terminal. You are also not allowed to execute programs directly from the SD card (mounted as noexec), so you can't try to obtain temp root from there. If you want to use the gfree method of rooting without using ADB, I made a guide using Visionary for the temp root here: http://forum.xda-developers.com/showthread.php?t=928160.
But the OP actually has ADB working, so he should be able to use any of the guides.
This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Uploaded with ImageShack.us
901-Memphis said:
This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Click to expand...
Click to collapse
You are supposed to be using the regular command prompt (I think you referred to it as the "run command prompt" earlier). It is the prompt in which you successfully ran the "adb devices" command. That is the only prompt you need to use.
Do i enter commands 1 at a time or all at once?
901-Memphis said:
Do i enter commands 1 at a time or all at once?
Click to expand...
Click to collapse
First off, Yes you enter each line as you see it.
Second just to make sure you are in the right area to enter these commands, to get to command prompt you can either search for it from the start menu or hold the "windows button + R".
That opens your run command from there type in "cmd" and that opens command prompt.
Next make sure your current directory is the one you installed adb into. To get to that you can type "cd C:/...... whatever folder you installed it to."
To make sure my adb is working I usually type "adb devices" and see if my phone shows up.
Good luck
Glad to see someone else from the good ole 901 around here =)
Sent from my HTC Vision using XDA App
Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file
901-Memphis said:
Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file
Click to expand...
Click to collapse
try pushing the file to that folder again
Re-Tried everything at least 3 times, including pushing the files that didn't go.
I give up Ive spent so much time on this only to have it fail at the most unlikely times.
Will wait for another method to root come available
You could try downloading and installing Droid Explorer. It installs adb and fastboot files in its install folder.
Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).
ianmcquinn said:
Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).
Click to expand...
Click to collapse
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything
901-Memphis said:
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything
Click to expand...
Click to collapse
You are supposed to do that command from your computer. (The instructions state "On the computer, open terminal and type the following commands".) Here, terminal means the command prompt that you've been running all of you other ADB commands from.
If you wanted to run the command from terminal on your phone, you would just type "chmod 777 /data/local/gfree".
You don't need ADB for G2s.
trance2315 said:
You don't need ADB for G2s.
Click to expand...
Click to collapse
Can someone link me a better guide for my G2 so that i can try this 1 more time ?
Maybe a link to the top choices for versions of android to run once i get it rooted?

[GUIDE] Root Kindle with 6.2.1 using JCase method

These are my notes and guide for rooting the Kindle with 6.2.1 firmware. If I left something out, or something is not working, please leave a comment and I'll try to update.
Credit goes to JCase for the root. Please consider making a donation to him here:
https://market.android.com/details?id=net.andirc.jcasedonate
Original procedure is here:
http://www.androidpolice.com/2011/1...on-kindle-regardless-of-its-software-version/
ADB INSTALL AND TEST - Method 1 (skip to the ROOT INSTALL section if you already have a working ADB)
NOTE: ADB = Android Debug Bridge. It is a command line interface to the android device. A working ADB is required before you can root your Kindle. ADB is installed on a PC and accesses the Kindle via USB cable.
Install Java SE Development Kit 7 on PC
The Android SDK Manager requires Java SDK
http://www.oracle.com/technetwork/java/javase/downloads/jdk-7u1-download-513651.html
Install Android SDK Manager on PC
The Android SDK has the drivers and ADB needed to perform the root procedure
http://developer.android.com/sdk/index.html
Uncheck Android 4.0
Check 2.33
Ensure Google USB Driver is checked
Install to c:\android to make typing easier later on
NOTE: The install can take a long time!
Manually update files so drivers will properly install
Open c:\users\your account name\.android\adb_usb.ini (or c:\documents and settings... if you have XP) and add the following
Code:
0x1949
Open c:\android\extras\google\usb_driver\android_winusb.inf and make additions as shown:
Code:
[Google.NTx86]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
....
[Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Install drivers
Find the Kindle device in device manager and update drivers. Point to the location with android_winusb .inf
Verify ADB works
Open a command prompt
CD to c:\android\platform-tools
Code:
adb kill-server
adb devices
If it's working, ADB will return a large number, like this:
Code:
312342134231342 device
ADB INSTALL AND TEST - Method 2
NOTE: I have not tried this, but Vashypooh's app can apparently handle the driver install, and run ADB without installing the above software. If all of this works, then his app would be the best way IMO.
NOTE 2: I've seen a lot of comments suggesting the driver install in Vashypooh's app doesn't work at this point.
http://forum.xda-developers.com/showthread.php?t=1399889
ROOT INSTALL - Method 1
Install JCase's kindleroot_androidpolice.apk
JCase's app gives ADB root access. Once this is done, you still need to install the superuser app
Download kindleroot_androidpolice.apk to PC
http://www.multiupload.com/VNZ6Y41EQF
Ensure the Kindle is connected via USB, and copy file to Kindle sdcard
Using ES File Explorer on Kindle, navigate to the kindleroot_androidpolice.apk and launch
Follow prompts and click root
Install superuser app
Download superuser-2 to PC
http://www.multiupload.com/M2CX14W7Y0
Unzip to c:\download\sufiles
Use ADB to install SU app
Code:
adb root
adb remount
adb push c:\download\sufiles\su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install c:\download\sufiles\Superuser.apk
adb reboot
ROOT INSTALL - Method 2
NOTE: I have not tried this, but Vashypooh's app can apparently handle the root process.
BurritoRoot (Temporary)
Install Permanent Root with Superuser
http://forum.xda-developers.com/showthread.php?t=1399889
A+ instructions, wish I could write my own that good lol.
jcase said:
A+ instructions, wish I could write my own that good lol.
Click to expand...
Click to collapse
Thanks to you for the root. I hope the guide will help those trying to root!
Thanks for the clear and easy steps.
Great guide Ectoplasmic!
One thing I would add though, in step 5 "Verify ADB Works", before you use the "adb devices" command, you need to type "adb kill-server". If you don't type in "adb kill-server" first, the device won't show up when you use the "adb devices" command. Or at least it didn't for me.
Otherwise, everything worked FLAWLESSLY. I verified I was rooted using Root Checker. Thank you!
zopzop25 said:
Great guide Ectoplasmic!
One thing I would add though, in step 5 "Verify ADB Works", before you use the "adb devices" command, you need to type "adb kill-server". If you don't type in "adb kill-server" first, the device won't show up when you use the "adb devices" command. Or at least it didn't for me.
Otherwise, everything worked FLAWLESSLY. I verified I was rooted using Root Checker. Thank you!
Click to expand...
Click to collapse
Thanks, I added this to the guide.
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Get help in irc from jcase and vashypool theyll probably be able to help u
tkcctkcc said:
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Click to expand...
Click to collapse
Unroot in my app (BurritoRoot) does not remove su, it just turns off adb root (which is what my app turns on) sorry for the confusion.
Will add in the future when I release burritomod
Here's the equivalent instructions for Mac
I am pretty new myself, but I'm happy to share what I've come up with so far. I am on a Mac OS X 10.6.8
Download the Android SDK for Mac (dl.google.com/android/android-sdk_r16-macosx.zip), the easiest place to put it is at the top of your user directory, from the browser download window chose your username from places on the left side, then name the zip "Android"
Next from Finder, navigate to the place where you downloaded the SDK, and double-click on it which should unzip it and create a folder of the same name e.g "Android". Open that and inside it will be a folder "tools", and inside that there will be a file "android". Double-click that to run it and the "Android SDK Manager" program window will pop up, you will also see a Terminal window in the background, don't worry about that. Uncheck all the boxes, then check "Android SDK Platform-tools" which should be the third from the top, and click install. This gets you the actual "dab" program.
Once adb is setup, to get it to recognize your kindle fire on your mac, you may need to make an entry in a config file if you haven't already.
Start Terminal Applications > Utilities > Terminal or if you are used to using spotlight, simply type in "Terminal". (here's an intro to using Terminal guides.macrumors.com/Terminal) and navigate to the directory where you have adb, e.g. if you placed it at the top of your user directory that would be
Code:
cd Android
or if you left it in the default downloads directory it would be
Code:
cd Downloads/android-sdk-macosx/
then enter the following commands
Code:
mkdir ~/.android
You may get the following error
Code:
mkdir: /Users/<username>/.android: File exists
If so, that is fine, continue to the next step
Code:
touch ~/.android/adb_usb.ini
open -e ~/.android/adb_usb.ini
TextEdit will open with that file open, you should have an entry in it on a single line that says
Code:
0x1949
if not, copy that in, then save and close it, then
Code:
./adb kill-server
Connect your kindle to the mac if it isn't already, then
Code:
./adb devices
You should see a message like
Code:
List of devices attached
2ED6000600000001 device
On your kindle, make sure you have a file navigation app, the example above ES FileExplorer is excellent and is the one I use from Amazon app store
Download Burrito Root from Android Police ( androidpolice.com/2011/12/23/exclusive-how-to-easily-root-the-amazon-kindle-regardless-of-its-software-version/)
Also download the Superuser.zip from the same page (multiupload.com/ONH28CB1GU) and unzip, then make sure you move the contents "su" and "Superuser.apk" into the same directory as adb
Through Finder copy the "kindleroot_androidpolice.apk" file you downloaded earlier to your kindle, some place like "download" so you can find it easily later
Now on the Kindle, tap disconnect on your KIndle so you can get back to the apps screen, launch the file explorer you installed earlier, navigate to folder you copied it to, e.g. "download" then install the "kindleroot_androidpolice.apk", open it, and go through the steps to launch click "Root"
Back on the Mac, in the terminal window where you had adb going, enter the commands
Code:
./adb root
./adb remount
./adb push su /system/xbin/su
./adb shell chown 0.0 /system/xbin/su
./adb shell chmod 06755 /system/xbin/su
./adb install Superuser.apk
./adb reboot
You should be rooted now, then you can follow the other instructions out there for getting Android market, etc working
TIP
here's a tip if you don't want to have to type in the period and slash ahead of adb every time. from your terminal window enter the
Code:
cd ~
touch .profile
open -e .profile
That will open text editor, and paste in the following line,
Code:
PATH=${PATH}:/Users/<username>/<sdk-directory>/platform-tools
replacing both our user name and the path to where you have sdk e.g. in my case
Code:
PATH=${PATH}:/Users/kbiz/Android/platform-tools
Then close the terminal window and reopen a new one and you should be good to go, now you'll only need to type in "adb".
Let me know if I missed something, trying to give back since this forum has been super helpful.
---------- Post added at 01:04 AM ---------- Previous post was at 12:58 AM ----------
tkcctkcc said:
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Click to expand...
Click to collapse
OTA Rootkeeper should work but since its not, try this (courtesy rootkindlefire.com/kindle-fire-unroot/how-to-unroot-kindle-fire/)
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/app/Superuser.apk
rm /system/xbin/su
reboot
after your Kindle restarts you won't have root and Amazon Video should work just fine.
Hello,
I have successfully rooted my device with the above instructions. While installing the Android market I was abusing of my root privileges and I've successfully "burned" my device. That is, the Kindle won't start up anymore (it stays forever in the initial phase showing the kindleFire logo).
I don't know where else to turn for help so I'm writing about this here. If anyone has hints of how I could recover my kindle from the void, please let me know
Cheers
http://forum.xda-developers.com/showthread.php?t=1356257
Yesssssssssss
Yesssssssssssssssssss. So nice to have root again. My Titanium Backup and SUFBS works again
I had ADB and SDK working when I had my Glacier, but since I have gotten my SGS2, and my Kindle, Android SDK Manager will not open... It just opens a command prompt, and then closes.. I have reinstalled both the SDK Manager and the Java Kit... Any ideas?
EDIT:
I must have messed with something in my system settings somewhere to corrupt a bunch of stuff... I did a system restore to the 18th of December, reinstalled, and everything works perfect now... Oh well! Haha
Hey, I used a combo of the link JCase gave me when I had questions, this guide, and the links off the rootzwiki guide and managed to get it first try. It was actually easier than I thought it was going to be. I've never rooted anything before, I didn't even have ADB or the SDK until tonight. The process (while using both guides and video tut) went smoothly without a hitch. I just finished installing the Android Market but have to wait til morning to access it, as I have no WiFi at home, and its too late for me to be driving to a hotspot. Thank you very much. You(JCase) and your comrades who put this all together f**king rule.
a really clear and easy guide ! - congratulations - you shoud try to let it pin on top !
Ectoplasmic said:
NOTE 2: I've seen a lot of comments suggesting the driver install in Vashypooh's app doesn't work at this point.
Click to expand...
Click to collapse
the reason people have problems with vashipooh's driver installation seems to be the old drivers - they don't manage to clean up the old drivers:
disconnect KF
Open an (elevated for win7) command prompt:
set devmgr_show_nonpresent_devices=1
devmgmt.msc
device manager opens - click "view" - click "show hidden devices"
now you see all devices ever connected/installed
uninstall all devices regarding "kindle" and "android (composite) adb device"
connect KF - will startup by itself
select the most recent driver (that you have installed before by install_driver.bat from KFU) manually (check date/time)
now you should be set up with a good driver installation
btw. i'm on xp - it's working for xp and 7, 32 and 64 bit

[q] help needed on 6.2.1

Hi all,
I got my KF few days back, Rooted it, before I could install the android market, got forced update to 6.2.1. 2 days ago saw this new root method using BurritoRoot. Tried rooting it, seems successful, however, now when I arrived at the home page, I cant even open the Superuser app at all. It goes the same for the Root Explorer - prompting:
"Root Explorer has not yet managed to obtain root access. Because of issues with Superuser, this often happens the first time the app is run but is usually fine from then on. Click ok and restart the app and try again. Make sure u respond correctly to the Superuser prompt." Then it comes with a force close.
Seriously I do not know whats wrong with it, now i cant even use the root explorer for me to install Android Market.
Anybody can help me with it?
Million Thanks.
did you use the superuser-2.apk ?
http://forum.xda-developers.com/showthread.php?p=20645033&highlight=superuser-2+apk#post20645033
b63 said:
did you use the superuser-2.apk ?
http://forum.xda-developers.com/showthread.php?p=20645033&highlight=superuser-2+apk#post20645033
Click to expand...
Click to collapse
Im using the ROOT INSTALL - Method 1 and I downloaded the file from Rootzwiki, apparently the file is named "com.noshufou.android.su-1.apk". and I used the following commands:
adb root
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install com.noshufou.android.su-1.apk
adb reboot
So which means I should use the Superuser -2.apk instead?
What should I do now? Download the Superuser-2 file and repeat the whole process again???
thanks.
yes - the new version seems to be the only one working with burritoroot
consider to use KFU to make things easier:
http://forum.xda-developers.com/showthread.php?t=1399889
should be option 2 (permanent root with superuser)

Kindle 7.2.3 Root Error: permission denied

Hey Guys,
i hope my english is ok and you can unterstand all what i mean.
I have a Kindle Fire HD Software version 7.2.3
i try to root my Kindle, fot the root i use this Method:
http://forum.xda-developers.com/showthread.php?t=1886460
Root_with_Restore_by_Bin4ry_v17 in the cmd.exe i got and error "permission denied"
then i use QemuRoot.bat and step 2 the same error "permission denied"
Driver installed and work correctly.
Kindel settings are correct.
maybe their have an idea.
I uploaded some pictures of the error in a few minutes.
CMD returned error "permission denied"
HarldOOOandSon said:
Hey Guys,
i hope my english is ok and you can unterstand all what i mean.
I have a Kindle Fire HD Software version 7.2.3
i try to root my Kindle, fot the root i use this Method:
http://forum.xda-developers.com/showthread.php?t=1886460
Root_with_Restore_by_Bin4ry_v17 in the cmd.exe i got and error "permission denied"
then i use QemuRoot.bat and step 2 the same error "permission denied"
Driver installed and work correctly.
Kindel settings are correct.
maybe their have an idea.
I uploaded some pictures of the error in a few minutes.
Click to expand...
Click to collapse
If I understand correctly, you try to execute the batch files to Root the Kindle Fire 7" HD: RunMe.bat (Step 1) or QemuRoot.bat (Step 2), Microsoft Windows returns an error Permission Denied or Access Denied. I suspect you are using Windows 7, correct? Try to Right Hand Mouse Click on then CMD.EXE Shortcut and choose "Run As Administrator".
prokennexusa said:
If I understand correctly, you try to execute the batch files to Root the Kindle Fire 7" HD: RunMe.bat (Step 1) or QemuRoot.bat (Step 2), Microsoft Windows returns an error Permission Denied or Access Denied. I suspect you are using Windows 7, correct? Try to Right Hand Mouse Click on then CMD.EXE Shortcut and choose "Run As Administrator".
Click to expand...
Click to collapse
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
HarldOOOandSon said:
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
Click to expand...
Click to collapse
I have the same exactly issue and I do run the .exe as administrator.... i don´t know whats going on....
HarldOOOandSon said:
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
Click to expand...
Click to collapse
Had the same problem. DL my package and see if you have any better luck:
http://www.mediafire.com/?t570mx55pqw5ezw
Or here are my instructions anyways:
Instructions:
1. Install/update Java from "chromeinstall-7u10.exe"
2. Install Kindle Fire ADB Drivers with "Kindle Fire ADB drivers.exe"
3. Place your Kindle fire in ADB mode (Settings->Security->Enable ADB->On) and connect your device by USB.
4. In the "Root_with_Restore_by_Bin4ry_v18" folder run "RunMe.bat"
5. Use Option one and follow the on-screen instructions
6. In the "QemuRoot_v1.0" folder, run "RootQemu.bat"
7. Follow the onscreen instructions.
8. You should be greeted with a success prompt.
*NOTE*
This method has gotten me farther and actually installs Superuser.apk, which I can open using ES File Explorer.
HOWEVER, Root still apparently doesn't work for me.
bigtimer5 said:
Had the same problem. DL my package and see if you have any better luck:
Or here are my instructions anyways:
Instructions:
1. Install/update Java from "chromeinstall-7u10.exe"
2. Install Kindle Fire ADB Drivers with "Kindle Fire ADB drivers.exe"
3. Place your Kindle fire in ADB mode (Settings->Security->Enable ADB->On) and connect your device by USB.
4. In the "Root_with_Restore_by_Bin4ry_v18" folder run "RunMe.bat"
5. Use Option one and follow the on-screen instructions
6. In the "QemuRoot_v1.0" folder, run "RootQemu.bat"
7. Follow the onscreen instructions.
8. You should be greeted with a success prompt.
*NOTE*
This method has gotten me farther and actually installs Superuser.apk, which I can open using ES File Explorer.
HOWEVER, Root still apparently doesn't work for me.
Click to expand...
Click to collapse
Still doesn´t work for me, the RunMe.Bat did finish the process but, the RooQuemu.Bat keeps teelling that in the 2nd step the prompting the access in denied
jose87413 said:
Still doesn´t work for me, the RunMe.Bat did finish the process but, the RooQuemu.Bat keeps teelling that in the 2nd step the prompting the access in denied
Click to expand...
Click to collapse
Same thing here. Doesnt matter which tutorial I follow. I get a permission or operation denied on anything that I want to do on the Kindle Fire.
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
HarldOOOandSon said:
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
Click to expand...
Click to collapse
Run everything again, first updating these utilities to the latest versions - these links have an updated ADB Server and API's:
https://dl.dropbox.com/u/54456659/Qmenu.zip
https://dl.dropbox.com/u/54456659/Ro...Bin4ry_v17.zip
Then follow these instructions again (Ignoring the links below):
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. When the Kindle asks to be Restored, CLICK on it (this installs the binary files).
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You now have Root.
prokennexusa said:
Run everything again, first updating these utilities to the latest versions - these links have an updated ADB Server and API's:
https://dl.dropbox.com/u/54456659/Qmenu.zip
https://dl.dropbox.com/u/54456659/Ro...Bin4ry_v17.zip
Then follow these instructions again (Ignoring the links below):
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. When the Kindle asks to be Restored, CLICK on it (this installs the binary files).
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You now have Root.
Click to expand...
Click to collapse
Thanks for the info (i'm having the same problem)
The 2nd download link does work (
Broken Link
Wilson157 said:
Thanks for the info (i'm having the same problem)
The 2nd download link does work (
Click to expand...
Click to collapse
2nd Download Link: Root_with_Restore_by_Bin4ry_v17.zip
thanks but no cigar
Thanks for the link.
I restored the kindle back to factory settings, followed your steps but i still get access denied on step 2 (exploiting) [local.prop]
(
Any help would be really really appreciated.
Step 1
Wilson157 said:
Thanks for the link.
I restored the kindle back to factory settings, followed your steps but i still get access denied on step 2 (exploiting) [local.prop]
(
Any help would be really really appreciated.
Click to expand...
Click to collapse
When you did Step 1, did you see Restore on the Kindle? Did you click on the Restore dialog and let the program reboot the Kindle? When the Kindle rebooted, was it running slow?
prokennexusa said:
When you did Step 1, did you see Restore on the Kindle? Did you click on the Restore dialog and let the program reboot the Kindle? When the Kindle rebooted, was it running slow?
Click to expand...
Click to collapse
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
Wilson157 said:
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
Click to expand...
Click to collapse
actually i've tried running the 1st step...and the kindle DOES run really slow. sorry for the confusion
Wilson157 said:
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
actually i've tried running the 1st step...and the kindle DOES run really slow. sorry for the confusion
Click to expand...
Click to collapse
yea, just tried. no go. any other ideas?
Qemu ADB Update
Wilson157 said:
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
actually i've tried running the 1st step...and the kindle DOES run really slow. sorry for the confusion
Click to expand...
Click to collapse
After the first step, do not do anything to the Kindle, leave it alone after the reboot and proceed using the following updated Qemu program.
You may download the updated version here: https://dl.dropbox.com/u/54456659/Qmenu.zip
Extract to your desktop and run the RootQemu.bat file. Choose Option 1.
littleengin said:
yea, just tried. no go. any other ideas?
Click to expand...
Click to collapse
in the words of alan partridge....A HAAAA!
Solved the issue.....Instead of running the batch file as admin, i opened up 'CMD' as admin, then navigated (using command prompt) to the folder containing the root files and ran them.....it worked!!! it passed through step 2.
However....when i run es file explorer. i cannot access root
Initialize Superuser.apk
Wilson157 said:
in the words of alan partridge....A HAAAA!
Solved the issue.....Instead of running the batch file as admin, i opened up 'CMD' as admin, then navigated (using command prompt) to the folder containing the root files and ran them.....it worked!!! it passed through step 2.
However....when i run es file explorer. i cannot access root
Click to expand...
Click to collapse
Ahhh, almost there. This is a bug in Superuser.apk - go into your Apps folder, you will see Superuser, click on it. It will open, now go to File Explorer, see if you can run as Root. I prefer Root Explorer.
Wilson157 said:
in the words of alan partridge....A HAAAA!
Solved the issue.....Instead of running the batch file as admin, i opened up 'CMD' as admin, then navigated (using command prompt) to the folder containing the root files and ran them.....it worked!!! it passed through step 2.
However....when i run es file explorer. i cannot access root
Click to expand...
Click to collapse
sorry my bad! Es file explorer was set to access root. Now i can access it. Thank you thank you thank you
I would post a picture of my ankle but the mods might class it as porn
Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
Since this thread had seen a lot of changes over the last couple of weeks, I decided it was time to consolidate everything again, so here it is the consolidated and updated link version as of 12/23/2012:
The problem "Device not Found" is usually driver related or ADB Security issue. I assume you have ADB enabled under Security - Enable ADB? Also enable "Allow Installation of Applications" under the Device tab - this will allow installation of Google Play applications. If all OK, move onto the next step.
Next, as per the Qemu thread noted here http://forum.xda-developers.com/show....php?t=1893838 you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", be sure to install the ADB driver package. Reboot the PC and next the Kindle.
As you noted, if you want to use Google Play, you must Root the device. Just to keep everything consolidated, I will give you a brief Rooting instructions which works for Software 7.2.2 and 7.2.3.
Download Root MANY ANDROID! to your desktop. Extract to your desktop.
Download Qemu automated root to your desktop. Extract to your desktop.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the batch files RunMe.bat and RootQemu.bat - otherwise Windows will respond with "Permission Denied".
Root Step 1: Run RunMe.bat from Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Choose option 1 Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. Click on Restore. When the program has completed, the Kindle will Reboot.
Root Step 2: When the Kindle reboots it will react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run RootQemu.bat from Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Follow the instructions Step-by-Step allowing Windows to re-detect the Kindle between reboots (about 2 minutes). Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You should now have root AND if this is true your ADB communication is also functional. Finally to Google Play.
Play Step 1 Move GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk to /system/app. Using Root explorer app on the Fire (be sure it has Superuser Permissions). Change permissions on both to Owner: Read-Write, Group: Read and Others: Read. Install GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk
Play Step 2 Reboot the Kindle
Play Step 3 Download Vending.apk
Play Step 4 Using Root explorer app on the Fire (be sure it has Superuser Permissions). Move Vending.apk to /system/app with permissions set to Owner: Read-Write, Group: Read and Others: Read.
Play Step 5 Install Vending.apk
Play Step 6 Google Play should show up in your Kindle Fire HD Apps. Tap on it and follow the steps.
Play Step 7 Download and install the Gplay3.8.17.apk to upgrade the the android market to the current Google Play market.
Play Step 8 Download google_apps - unzip to /sdcard/download
Play Step 9 Install Google Apps as needed. There is no need to move any of the apps to /system/app, just perform a normal apk install by using Root Explorer to install these apps.
I have also attached copies of these noted files to this thread.
Also, I have organized a few Google Apps & Services then zipped them into a folder you may download here: Google Apps. I have used all these Apps on my Kindle 7" HD successfully.
If you would like to disable the Amazon OTA Updates, delete or move /system/ect/security/otacerts.zip to /sdcard/download - Reboot the Kindle.
Finally, to eliminate Amazon from intercepting any Market requests, thus allowing Google Play to be the default Market move /system/app/MarketIntentProxy.apk to /sdcard/download - Reboot the Kindle
I'm also trying to do what previous users have been doing in this thread: running Rootqemu.bat but I still get permission denied on the second step. I've tried navigating to the folder using an administrator command prompt and running it through cmd, still fails on the second step with permission denied:
/system/bin/sh: cannot create /data/local.prop: Permission denied.
Have no idea where to go from here any help would be appreciated.

Temporary Magisk Root on VZW Pixel 2 (XL)

I have moved this from here https://forum.xda-developers.com/pixel-2-xl/how-to/zero-day-vzw-pixel-2-xl-root-t3977851/
Hey everyone!
I am here to post some good news. I have made a set of scripts that can give you temporary root through Magisk. It persists until the next reboot, but setting it up after the initial setup is a lot easier.
The script requires that it be run as root, which means that you need to run the temproot binary provided earlier.
Big thank you to Elliwigy for walking me through the initial process and for providing the commands.
Source code for the "exploit" binary can be found here, and compiled from source if you so desire.
This script is provided with no warranty whatsoever. This script may brick your phone. YOU ARE RUNNING THIS AT YOUR OWN RISK. I ACCEPT NO RESPONSIBILITY FOR WHAT THIS SCRIPT DOES TO YOUR PHONE.
Click to expand...
Click to collapse
IF YOU DO NOT WANT TO RISK YOUR PHONE BEING BRICKED, DO NOT CONTINUE!
Requirements:
A Verizon Pixel 2 (XL) on the September 2019 Security Patch
A computer with ADB If you need ADB, it can be found here
A USB cable
Appropriate USB drivers USB drivers can be found here if needed
Some knowledge of how to use the terminal
The taimentempmagisk.zip file (attached)
The APK for Magisk Manager (included in the zip)
Hope
Magisk and MagiskManager can also be downloaded from here if you wish.
If Magisk Manager prompts you to perform additional setup, DO NOT ACCEPT. (unless you like having a bricked phone)
Install the Magisk Manager APK onto your phone
Use ADB to push the attached ZIP file (taimentempmagisk.zip) to /data/local/tmp
Open an ADB shell and navigate to /data/local/tmp
Extract the ZIP file with the unzip command
Navigate into the scripts folder
Run ./exploit (If this step fails, repeat until you have a root shell)
Run ./installtemproot.sh magiskinit64
After you have done this, you now have root!
If you reboot and want root back, just run /data/local/tmp/scripts/exploit in an adb shell, then run /data/local/tmp/scripts/temproot.sh
Enjoy your root!
Does not work
Hexlay said:
Does not work
Click to expand...
Click to collapse
I'm currently working on a solution, it seems some terminal emulators error out on the mount command.
EDIT: Instructions updated.
logan2611 said:
I'm currently working on a solution, it seems some terminal emulators error out on the mount command.
EDIT: Instructions updated.
Click to expand...
Click to collapse
I'v tried, everything went fine, however magisk still does not detect root
Hexlay said:
I'v tried, everything went fine, however magisk still does not detect root
Click to expand...
Click to collapse
did u install magisk manager? if u dont have it installed then u womt b able to grant su permissions.. it does work as we spent hours testing and ensuring it works before he posted it.. id triple check each instruction and make sure u have magisk apk installed.. if not then reboot and try again from the beginning
elliwigy said:
did u install magisk manager? if u dont have it installed then u womt b able to grant su permissions.. it does work as we spent hours testing and ensuring it works before he posted it.. id triple check each instruction and make sure u have magisk apk installed.. if not then reboot and try again from the beginning
Click to expand...
Click to collapse
Yep, i have it pre-installed, i did follow every step provided, but prompt is not showing up and afterwards it does not detect root... Well, i'v done it several times, i tried ./temproot.sh after install script, but still same...
Well, i guess i have to reboot
Edit: tried reboot, still same.... i'll write down what i have done exactly.
Rebooted dvice
Went into terminal emulator and executed ./taimen
After that went one step back with cd .. and executed chmod -R 777 scripts
Then went to pc and entered ADB shell and executed ./taimen there too, because otherwise i was getting This script must be run as root. Exiting. on install script
Then ran install script. Process did complete successfully, however no magisk prompt was fired and afterwards root was not detected
I'v tried chmod -R 777 . even from adb shell, tried opening magisk app and then doing these whole process... no luck
First, thanks for your supporting and your instruction
I just install October(6/10) update so any risk if i follow your instruction
Anyone know how to delete the update? I've downloaded and refuse to restart my device in the wake of these new development
enigma2446 said:
Anyone know how to delete the update? I've downloaded and refuse to restart my device in the wake of these new development
Click to expand...
Click to collapse
I also want to know this. I need to reboot but I don't want to move to the October patch.
Hexlay said:
Yep, i have it pre-installed, i did follow every step provided, but prompt is not showing up and afterwards it does not detect root... Well, i'v done it several times, i tried ./temproot.sh after install script, but still same...
Well, i guess i have to reboot
Edit: tried reboot, still same.... i'll write down what i have done exactly.
Rebooted dvice
Went into terminal emulator and executed ./taimen
After that went one step back with cd .. and executed chmod -R 777 scripts
Then went to pc and entered ADB shell and executed ./taimen there too, because otherwise i was getting This script must be run as root. Exiting. on install script
Then ran install script. Process did complete successfully, however no magisk prompt was fired and afterwards root was not detected
I'v tried chmod -R 777 . even from adb shell, tried opening magisk app and then doing these whole process... no luck
Click to expand...
Click to collapse
Can you post the output of the script?
logan2611 said:
Can you post the output of the script?
Click to expand...
Click to collapse
That's output every time, it finishes script successfully
Hexlay said:
That's output every time, it finishes script successfully
Click to expand...
Click to collapse
Sorry, screenshot didn't load the first time. Looks like all the files are already in place, try rebooting and running temproot.sh
running ./taimen just gives a "permission denied" error
Some1CP said:
running ./taimen just gives a "permission denied" error
Click to expand...
Click to collapse
If you are getting this on the phone, you need to use a terminal emulator with access to a directory in /data. I used Termux in my example.
If you want to use Termux, here is how to get taimen running:
Install Termux
Open Termux and let it install
Run termux-setup-storage
Push the ZIP to /sdcard/Download
On the phone, move the ZIP file from ~/storage/downloads to ~
Continue from step 4 in OP
logan2611 said:
If you are getting this on the phone, you need to use a terminal emulator with access to a directory in /data. I used Termux in my example.
If you want to use Termux, here is how to get taimen running:
Install Termux
Open Termux and let it install
Run termux-setup-storage
Push the ZIP to /sdcard/Download
On the phone, move the ZIP file from ~/storage/downloads to ~
Continue from step 4 in OP
Click to expand...
Click to collapse
How would I move it to ~ without root?
Edit: nevermind, got it to run.
Just need to figure out how to make the temproot work.
Some1CP said:
How would I move it to ~ without root?
Click to expand...
Click to collapse
In Linux ~ is a shortcut for the home directory, which is always owned by the current user. Root is not required to move the ZIP from ~/storage/downloads to ~ on Termux.
Ok I can't run installtemproot.sh in adb, and neither on the phone itself through termux. Is there something I'm missing? su can't be find on the phone.
Edit: It works if you use Jack Pal's terminal emulator and you cd into its directory on adb. Sadly magisk doesn't recognize it's installed.
I'm on October 5 2018 security update and should flash September 5 2019 try temp root?I know stay away October's 2019 that's patch,sean
logan2611 said:
Sorry, screenshot didn't load the first time. Looks like all the files are already in place, try rebooting and running temproot.sh
Click to expand...
Click to collapse
Sorry for wait time, literally had to wait for type-c to type-c connection -_- it's pain....
Anyway i did reboot and tried again with just temproot.sh, without repeating previous stuff. No prompt is fired, but output is success
Hexlay said:
Sorry for wait time, literally had to wait for type-c to type-c connection -_- it's pain....
Anyway i did reboot and tried again with just temproot.sh, without repeating previous stuff. No prompt is fired, but output is success
Click to expand...
Click to collapse
client: launching new main daemon process
Click to expand...
Click to collapse
The output suggests that Magisk started successfully. What does Magisk Manager look like after running that script?

Categories

Resources