Database Users

[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

[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.

[ROOT] How To: Root the Kindle Fire 7" HD or 2 with Linux/MAC - Noob (Simple) Version

[ROOT] How To: Root the Kindle Fire 7" HD or 2 with Linux/MAC - Noob (Simple) Version
This is a simple Step-by-Step guide on How To: How To: Root the Kindle Fire 7" HD or 2 with Linux or Mac - Noob (Simple) Version. The main group steps are outlined with A, B, C while the sub-group steps are outlined with 1, 2, 3.
Prerequisites:
1. Software: Linux (tested on Linux Ubuntu Quantal Quetzal 32-bit and 64-bit) or Mac OS X 10.5.8 or later (32-bit and 64-bit)
2. Hardware: Free USB 2.0 or Greater Port
3. Software: Linux GNU C Library (glibc) 2.7 or later is required, On Ubuntu Linux, version 8.04 or later is required,
64-bit distributions must be capable of running 32-bit applications.
4. Hardware: Kindle Fire HD 7" or Kindle Fire 2 7"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enabling and using the "root" user in Mac OS X
It is important that you use our Software since we use the latest versions of Superuser.apk and the su binary.
A) First we will install the needed software, then move on to Rooting the Kindle through the ADB Service.
Unplug the Kindle from USB. Go to your Kindle, navigate to the pull down options bar, choose More > Security
Be sure to Enable ADB by clicking On
Next Go to your Kindle, navigate to the pull down options bar, choose More > Device
Be sure to Allow Installation of Applications by clicking On
Root Kindle Fire HD Step 1: Go to your Mac or Linux workstation, download and unzip Root MANY ANDROID! there are 3 different versions, we have taken steps to optimized for each specific platform, please select the correct one matching your platform. If you are having trouble determining which one to download post the question inside this thread. Pay close attention to the path where you unzipped the download.
Linux 32-bit Version 18.5.1: Linux32.zip
Linux 64-bit Version 18.5.1: Linux64.zip
Mac 64-bit Version 18.5.1: Apple64.zip
Root Kindle Fire HD Step 2: Plug the Kindle into the free USB 2.0 Port. Wait for the driver to install
about 2 minutes. Mac OS X and Linux do not require any special drivers, the default driver built into these platforms will be
sufficient.
Root Kindle Fire HD Step 3: Open up a Browser, go to Oracle Java, Download and Install Java Platform (JDK) 7u13 - Please reboot after the install:
Linux 32-bit JDK 7.13 Install Notes: http://docs.oracle.com/javase/7/docs/webnotes/install/linux/linux-jdk.html
Linux 64-bit JDK 7.13 Install Notes: http://docs.oracle.com/javase/7/docs/webnotes/install/linux/linux-jdk.html
Mac 64-bit JDK 7.13 Install Notes: http://docs.oracle.com/javase/7/docs/webnotes/install/mac/mac-jdk.html
Root Kindle Fire HD Step 4: Open up a Terminal, at the Terminal window ($ command prompt) type:
Code:
su -
Enter your Root Password if requested to do so. You should now see a # at the command prompt. Ubuntu Users would use:
Code:
sudo before each command (Ignore su-)
Root Kindle Fire HD Step 5: Next go back to the open command prompt at the /RootPackage32or64Folder/# enter:
Code:
chmod 777 RunMe.sh
sh RunMe.sh
OR
./RunMe.sh
Ubuntu Users would use:
Code:
sudo chmod 777 RunMe.sh
sudo sh ./RunMe.sh
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.
If you receive 'can not execute items in the stuff folder', please check to make sure you downloaded the correct package for your platform. The Linux 64-bit package will not work on a 32-bit computer. If you have verified your download and you are still seeing the 'can not execute items in the stuff folder' message, please post a screen shot in this thread.
Code:
exit
Root Kindle Fire HD Step 6: Finally go back to the Kindle, navigate to the /Apps tab, click on Device, next find and click on Superuser.apk initialize the Superuser daemon.
Root Kindle Fire HD Step 7: Finally, using a Web Browser Download suchecker.apk to the /RootPackage32or64Folder/#: suchecker.apk. After the download has completed, open a command prompt at the /RootPackage32or64Folder/# enter:
Code:
./stuff/adb kill-server
./stuff/adb start-server
./stuff/adb devices
./stuff/adb install [URL="https://dl.dropbox.com/u/54456659/suchecker.apk"]suchecker.apk[/URL]
./stuff/adb reboot
Root Kindle Fire HD Step 8: When the install has finished, go to your Apps. Launch Root Checker Basic When you check Root you will be presented with a "Allow" dialog box, be sure to Allow Root Checker. You should now see that Superuser.apk is working. Here is a screen shot of Root Checker Pro:
You should now have root AND if this is true your ADB communication is also functional!
B) Finally, let's disable the Amazon OTA (Over The Air) Updates so your hard work is not destroyed.
OTA Step 1:
[HOW TO] Disable Amazon OTA (Over The Air) System Updates Noob (Simple) Version
OTA Step 2: Reboot the Kindle.
Note: You may still install the updates manually after you have read the install notes and know what to expect. The updates and manual install instructions can be found on Amazon Support here: http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_sib?ie=UTF8&nodeId=201016350
Next, move onto our How to: Install Google Play Step-by-Step Thread.
If this was helpful and you would like to support our work, please send us a donation using this link:
http://forum.xda-developers.com/dona....php?u=4435645

Thanks great tutorial, many have been waiting for this and I am sure this is easy to follow like your other NOOB tutorials.

How To: Root the Kindle Fire 7" HD with Linux or MAC - Noob (Simple) Version
los911 said:
Thanks great tutorial, many have been waiting for this and I am sure this is easy to follow like your other NOOB tutorials.
Click to expand...
Click to collapse
Thank you for the feedback, we did receive a number of requests. We are truly honored
to be a part of the XDA Community and we have a passion around upgrading/tweaking
tablets.

Update - Linux
To All,
We did test the above steps on SUSE and Ubuntu Linux today. They both worked flawlessly.
Thank you to everyone for your support.

Permission denied on /data/local.prop
Thanks for posting this. I'm stuck at this step:
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
I did the earlier step of removing /data/local/tmp and symlinking /data/.
The data directory is owned by the system user:
130|[email protected]:/ $ ll
drwxr-xr-x root root 2012-12-31 22:59 acct
drwxrwx--- system cache 2012-12-22 01:17 cache
dr-x------ root root 2012-12-31 22:59 config
lrwxrwxrwx root root 2012-12-31 22:59 d -> /sys/kernel/debug
drwxrwx--x system system 2012-09-28 11:57 data
I tried chown and chmod, but apparently those commands aren't available in the android shell.
Any suggestions?

How To: Root the Kindle Fire 7" HD or 2 with Linux or MAC - Noob (Simple) Version
rwil said:
Thanks for posting this. I'm stuck at this step:
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
I did the earlier step of removing /data/local/tmp and symlinking /data/.
The data directory is owned by the system user:
130|[email protected]:/ $ ll
drwxr-xr-x root root 2012-12-31 22:59 acct
drwxrwx--- system cache 2012-12-22 01:17 cache
dr-x------ root root 2012-12-31 22:59 config
lrwxrwxrwx root root 2012-12-31 22:59 d -> /sys/kernel/debug
drwxrwx--x system system 2012-09-28 11:57 data
I tried chown and chmod, but apparently those commands aren't available in the android shell.
Any suggestions?
Click to expand...
Click to collapse
What version of Linux are you using? This is normally a permissions issue on the workstation.
Sometimes Ubuntu requires sudo before the adb statement. I am a bit concerned with the $ prompt
the prompt should be # but if you are on Ubuntu, sudo will solve your issue.

prokennexusa said:
What version of Linux are you using? This is normally a permissions issue on the workstation.
Sometimes Ubuntu requires sudo before the adb statement. I am a bit concerned with the $ prompt
the prompt should be # but if you are on Ubuntu, sudo will solve your issue.
Click to expand...
Click to collapse
Kubuntu 12.10.
I've tried running the 'adb shell' command using sudo and after switching to root with su -. Either way I end up at the [email protected] $ prompt.
I also tried adb kill-server and adb start-server with sudo and su, but no change.
It sounds like I should be seeing "[email protected] #" ?

Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
rwil said:
12.10.
I've tried running the 'adb shell' command using sudo and after switching to root with su -. Either way I end up at the [email protected] $ prompt.
I also tried adb kill-server and adb start-server with sudo and su, but no change.
It sounds like I should be seeing "[email protected] #" ?
Click to expand...
Click to collapse
No, you are OK. Is the Kindle a Kindle Fire 2 7" or a Kindle Fire HD 7"

prokennexusa said:
No, you are OK. Is the Kindle a Kindle Fire 2 7" or a Kindle Fire HD 7"
Click to expand...
Click to collapse
Kindle Fire HD 7"

Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
rwil said:
Kindle Fire HD 7"
Click to expand...
Click to collapse
Perfect, I just added some additional steps, look at the original post (RunMe.sh). This will get you fixed.
Sorry, I forgot an important step!

Follow Up - Feedback
rwil said:
Thanks for posting this. I'm stuck at this step:
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
I did the earlier step of removing /data/local/tmp and symlinking /data/.
The data directory is owned by the system user:
130|[email protected]:/ $ ll
drwxr-xr-x root root 2012-12-31 22:59 acct
drwxrwx--- system cache 2012-12-22 01:17 cache
dr-x------ root root 2012-12-31 22:59 config
lrwxrwxrwx root root 2012-12-31 22:59 d -> /sys/kernel/debug
drwxrwx--x system system 2012-09-28 11:57 data
I tried chown and chmod, but apparently those commands aren't available in the android shell.
Any suggestions?
Click to expand...
Click to collapse
rwil,
Did the new steps allow you to successfully Root the Kindle? We do offer free phone support
if you have not been able to achieve Root. Let me know what happened and how we can
improve this How to:

Yes, I was able to finally get it rooted. One thing I had to do was use the adb executable you posted instead of the one from Bin4ry. That one stalled at the intial stage saying it was waiting for the device.

binary file issue
Root Kindle Fire HD Step 4: Open up a Terminal, at the Terminal window ($ command prompt) type:
Code:
su -
Enter your Root Password if requested to do so. You should now see a # at the command prompt.
Root Kindle Fire HD Step 5: Download Superuser-3.1.3-arm-signed
Root Kindle Fire HD Step 6: Unzip Superuser-3.1.3-arm-signed.zip to Superuser-3.1.3-arm-signed
Root Kindle Fire HD Step 7: Copy the entire contents of Superuser-3.1.3-arm-signed to /Android/android-sdk/platform-tools/ (Step 1 install path).
Root Kindle Fire HD Step 7.1: Next go back to the open command prompt, at the /Root_with_Restore_by_Bin4ry_v17/# enter:
Code:
chmod 777 RunMe.sh
sh RunMe.sh
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.
The forum notes can be found here: Root MANY ANDROID! Forum.
OK... I am having trouble running the above code "chmod 777 RunMe.sh" and "sh RunMe.sh". The terminal file begins, I select option 1, and nothing happens on my Kindle Fire HD 7. I do not get a "restore" option on the KFHD7. In the terminal window I get many errors stating "cannot execute binary file" the script runs to the end with several cannot execute binary file errors. Also, while in su (root#) in terminal, I ran ./adb devices and the device does show. I am obviously missing something....
Thanks for any assistance....

ADB Communication Issues
Drewski35 said:
Root Kindle Fire HD Step 4: Open up a Terminal, at the Terminal window ($ command prompt) type:
Code:
su -
Enter your Root Password if requested to do so. You should now see a # at the command prompt.
Root Kindle Fire HD Step 5: Download Superuser-3.1.3-arm-signed
Root Kindle Fire HD Step 6: Unzip Superuser-3.1.3-arm-signed.zip to Superuser-3.1.3-arm-signed
Root Kindle Fire HD Step 7: Copy the entire contents of Superuser-3.1.3-arm-signed to /Android/android-sdk/platform-tools/ (Step 1 install path).
Root Kindle Fire HD Step 7.1: Next go back to the open command prompt, at the /Root_with_Restore_by_Bin4ry_v17/# enter:
Code:
chmod 777 RunMe.sh
sh RunMe.sh
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.
The forum notes can be found here: Root MANY ANDROID! Forum.
OK... I am having trouble running the above code "chmod 777 RunMe.sh" and "sh RunMe.sh". The terminal file begins, I select option 1, and nothing happens on my Kindle Fire HD 7. I do not get a "restore" option on the KFHD7. In the terminal window I get many errors stating "cannot execute binary file" the script runs to the end with several cannot execute binary file errors. Also, while in su (root#) in terminal, I ran ./adb devices and the device does show. I am obviously missing something....
Thanks for any assistance....
Click to expand...
Click to collapse
Drewski35,
You did obtain the software from us, correct? We found a bug in the older version of the adb binary. The new
download includes updates that may solve your problem. Please go back and download Root MANY ANDROID!
The date and time on the new Binary is 01/02/2013 1:33 PM.
The problem with a Linux tutorial is there are many variables between platforms. An example is
to obtain Superuser on SuSe Linux, it is a simple su -, then you will be at the # (Root) command
prompt. In Ubuntu Linux you need to type sudo before every command that requires Superuser
Permissions. Having said this, these utilities need to run at Root or Superuser. Have you tried
sudo before every command? First update, then try again.
Update.

This work on a Mac? & 7.2.3?
Ive been unsuccessful until now with either Mac or Win.
Thanks

ADB Communication Issues
dannyben said:
This work on a Mac? & 7.2.3?
Ive been unsuccessful until now with either Mac or Win.
Thanks
Click to expand...
Click to collapse
dannyben,
Have you tried out tutorial? We just posted new ADB Drivers with the tutorial, the links
are below. Try our steps again with the new driver, if you continue to have trouble, send
us a PM, we will call you and give you free phone support. We are usually able to resolve
the problem in less than a 30 minute call. Yes, this will work on MAC. Just make
sure you download the latest Android SDK included in the tutorial.

Would this work for the kindle fire hd 8.9?

Root and Google Play for Amazon 8.9" Kindle Fire HD Software Version 7.2.3
almosthalfwaythere said:
Would this work for the kindle fire hd 8.9?
Click to expand...
Click to collapse
almosthalfwaythere,
Sorry for the delay, we have been busy today.
Yes, this works for the 8.9". If you get stuck, let us know.

I'm having this same exact error. I'm running Ubuntu 12.04. I downloaded the latest version of everything and followed the latest instructions. It's Jan 4, 2013 now. I'm not sure what I could be doing wrong.
I am using the sudo command each time.
But I get to this and get stuck...
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
I noticed the other person who had this problem finally got it working. It's a failure for me.
Would like some help here.
prokennexusa said:
What version of Linux are you using? This is normally a permissions issue on the workstation.
Sometimes Ubuntu requires sudo before the adb statement. I am a bit concerned with the $ prompt
the prompt should be # but if you are on Ubuntu, sudo will solve your issue.
Click to expand...
Click to collapse

Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
josephcagle said:
I'm having this same exact error. I'm running Ubuntu 12.04. I downloaded the latest version of everything and followed the latest instructions. It's Jan 4, 2013 now. I'm not sure what I could be doing wrong.
I am using the sudo command each time.
But I get to this and get stuck...
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
I noticed the other person who had this problem finally got it working. It's a failure for me.
Would like some help here.
Click to expand...
Click to collapse
josephcagle,
When you run Root MANY ANDROID! Does the Kindle ask to be Restored? Do you click on
restore and let the software reboot the Kindle? I am turning in for the night, I have been working
for over 16 hours now. Let's connect tomorrow AM, will you be around about 11am PST GMT -8?
If yes, let's connect then, if that time does not work, what time works?

[ROOT] With working PlayStore Google Apps + Custom Launcher + superSU

###YOUTUBE VIDEO WILL BE UP SHORTLY###
###ALSO THE GUIDE WILL GET MORE DETAILS AND INFORMATION IN A SHORT PERIOD OF TIME###
###Before you ask, i use Quote instead of Code to NOT cut of the Code###
Requirement:
- Fire Tab 6" or 7" 4th Generation
- be patient
- be Aware - things can go wrong, if ANYthing is unclear, please ask first!
- Around 30~ to 60~ Minutes
depending how fast you get ADB and everything else required to get to the initial Root.
IF you already using ADB with your Fire, Check Step 3, THEN go to Step 7
Hi there,
In this Tutorial you will learn how you can root your Amazon Fire HD 6" or 7" Tablet.
First we are going to root it using Kingroot, after thet we Sideload SuperSU Root.
Please note this Tutorial requires the 4th(!) Generation of Fire Tabs.
Error-Solutions are at the BOTTOM of this Document!
NOTE: This Tutorial includes:
-Install ADB using Android Studio (also Windows 8, 10)
-Disable Fire Tab Ads
-Connect to Google
-Install Google GAPPS
-Install Custom Launcher
-Replace Default FireLauncher with Custom Launcher
-Root Device
-Sideload superSU, replace Root
-Install Google Store
-Implement Google Service as System-Apps
-Block Google-Phone-Home, AutoUpdates
Step 1:
Download the required Files (~180 MB)
Link: https://drive.google.com/file/d/0B5zOo5KIf0WdSVZKUllhQm85alk/view
Step 2:
Get Android Studio (FULL Install ~800MB)
Check the Android Studio Dir this ZIP contains and execute "Get AndroidStudio.lnk"
Step 2.1:
- After installing Android Studio launch it, click "Configuration" and Select the SDK (first Option)
- Select "Tools" at the Top and click "Manage Add-on Sites"
- Click the "User Defined Sites" Tab and click on "New..."
- Paste this URL:
http://kindle-sdk.s3.amazonaws.com/addon.xml
Click to expand...
Click to collapse
- confirm with "OK"
- Close this Window after and go back to the Mainwindow "Android SDK Manager"
Step 2.2:
- Scroll down until you see the "Extras" Folder, select "Kindle Fire USB Driver"
TIP: Click "Deselect All" first and reselect "Kindle USB Driver" so you don't have to install the Whole Package.
- Click "Install x packages..." after and wait until it's installed. After it's done you can close the SDK Manager Process.
Step 3:
- Open the Android SDK Main Dir wich is located for ex:
C:\Users\<USERNAME>\AppData\Local\Android\
Click to expand...
Click to collapse
- Enter "android-sdk\platform-tools"
- Copy the Content from "APT" Dir to this Folder, for ex:
C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
- Go back to the Mainfolder and enter "sdk\extras\amazon\kindle_fire_usb_driver"
Step 4:
- Open your Devicemanager (Controlpanel > Devices > Devicemanager) and connect your Fire Tab to the Computer
- Open the Internal Storage of your Fire Tab and go to "Download" Dir at, copy & paste the whole Content from APK Dir to Fire Tab's Download folder.
Step 5:
- Open "Settings" at your Fire Tab Device and select "Applications"-Tab, enable Third Party Application.
- Go back to Settings and go to your Device Propertys, now tap the "Serialnumber" Field until you enable the Dev-Mode.
- Enter Developersettings and enable "ADB" at the "Debugging"-Tab.
Step 6:
- Now (you are still at the Devicemanager) select the "Fire", it should be displayed as a protable device.
- Rightclick it and select "Uninstall".
If there is any other Kind of "Fire" you should install them, too.
Do NOT close the Devicemanager now.
###
---If you use Windows 8 or 10 - go to the Bottom now to see what you have to do instead of the following---
###
- Unplug your Device now and Run (As Admin) the "KindleDriver.exe" at your Amazon Folder located at AndroidSDK
- Install it (should give you a green tick if everything was correct)
- After you installed it - connect the Fire Tab again.
- If your Fire Tab Fire is not marked as "ADB Device" repeat
Step 7:
- Now ADB and your Fire Tab are ready to get tested.
- Your Fire should already be connected to your device, if not, do so.
- Run a Command Prompt (Win+R and type "cmd" without ")
- now first go to your Android AD Location wich should be by default:
C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
- After you found the correct dir, copy the Path, go to your Command Prompt, paste it with "cd " in Front of it.
cd C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
###NOTE: All ADB-Commands are single-lined Commands.
Even if there are empty lines between them, it's just for better orientation.
Each command has to be added, one by one!
Step 8:
- Now you should be at the correct Dir, write
adb kill-server
Click to expand...
Click to collapse
Then
adb start-server
Click to expand...
Click to collapse
- The Server should start now, after it's online write
adb devices
Click to expand...
Click to collapse
- Your Device should now be displayed at the Prompt, if it says "Unauthorized", check your Tab, accept the Message and type again
adb devices
Click to expand...
Click to collapse
- It should now be displayed as "device"
Step 9:
- Enter
adb shell
Click to expand...
Click to collapse
at your Command Prompt
- Now let's make connection with Google.
- Enter the following command and accept with Enter of course
pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
Click to expand...
Click to collapse
---Optional: to Block Ads from the Lockscreen menu type this:
pm block com.amazon.kindle.kso
Click to expand...
Click to collapse
Step 10:
- Go to your device and run Amazon Appstore look for "ES File Explorer" and install it.
- After that, we are starting to Install GAPPS.
NOTE: After each App, REBOOT your device and install the next one!
- Open ES File Explorer and go your "Download" Folder.
- Install the Apk's in this Order, don't forget to reboot:
Google Account Manager
Google Service Framework
Google Play Services
Google Play Store
Click to expand...
Click to collapse
- Now you can Create your Account and Log-In if you like
- After this Step, you do not need to reboot after the next APKs.
Google Play Games (also Create Acc/Login if you like)
Aptoide
VireLauncherPro
RootChecker
KindleReader (The default one may not work anymore)
Click to expand...
Click to collapse
Step 11:
- Back to adb Shell Prompt, we are going to Block our Amazon Default Launcher, type
pm block com.amazon.kindle.otter
Click to expand...
Click to collapse
- Now just Launch VireLauncher and mark it as default if it asks for.
- Now we got what we need to proceed for our root.
-----------IMPORTANT: In order to make sure all Amazonapps are Still working after the initial Root
-----------It is recommend to run all Amazon Apps you are going to use even once (MOST important after factory Reset)
Step 12:
- UNPLUG your Fire Tab (IMPORTANT)
- Open your ES File Explorer at the Download Tab and install
KingRoot-4.0.0.233-release-201505071219_105001
Click to expand...
Click to collapse
- Run KingRoot and tab the blue button at the bottom
- Now KingRoot is going to root your device, the device restarts during this Process.
- After the Device restarted.
- Click the Check Button (Top right Corner) and scroll up, it should say rooted, if NOT - restart KingRoot again and Root again.
Step 13:
- Go back to our Commandprompt (if you are still in ADB Shell, type "exit" first) and now excecute those Commands
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
Click to expand...
Click to collapse
- Now simply type
su
Click to expand...
Click to collapse
- now the following commands one after another, remember each command is a single line!
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
Click to expand...
Click to collapse
Leave the ADB Terminal for now and go back to your Device, open the KingUser App
Click at the Top Right Corner on the Screen, click the Root authorization Settings and Remove Root Permission.
go to Settings > Application > All Applications/Third Party and uninstall the other King Applications (KingRoot and a Chinese one)
Go back to ADB now and enter the following commands one after another:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/shipclean
rm /system/bin/start-ssh
busybox chattr -ia /system/etc/install-recovery.sh
busybox chattr -ia /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install_recovery.sh
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Click to expand...
Click to collapse
Step 14:
- leave the ADB Terminal again and open your ES File Explorer
- Install superSU now, then run it and let it update after that reboot your Device
- Leave the Device for around 5 Minutes after Reboot.
- Now run your RootChecker and click the Checkbutton at the Top right, and scroll up again, it should say "rooted".
Step 15:
- Go back to ES File Explorer but leave ADB open as always, Install
SysAppConverter
Click to expand...
Click to collapse
- Open the SysAppConverter after and add the following things to your "System-Apps"
Google Play Store (com.android.vending)
Google Services Framework (com.google.android.gsf)
Google Play Services (com.android.google.gms)
Click to expand...
Click to collapse
Step 16:
- After you have done this, go back to ADB Shell and stop them from Phoneing home
pm block com.amazon.otaverifier
pm block com.amazon.dcp
Click to expand...
Click to collapse
Also enter the Playstore, top right corner -> uncheck autoupdate
Swipe to the right, click Settings and also disable autoupdates.
Finally, you are ready and your Device is rooted including Access to Google Playstore
IMPORTANT: If Apps or Playstore should not work because of reasons, there is a simple trick just reset your Google Frame Services.
Open SystemAppConverter
Browser for "Google Play-Services" (The Puzzle Piece) and hit the "System" button to the right.
Now select "Remove Updates". Now wait around a minute. Try if it works, if not - restart the Device.
Sometimes the Screen can Flash or the Tab will just shut down.
-------------------------------------------------------------------------
WINDOWS 8
Go to the Windows 8 folder, There is a tutorial how to install ADB on Win 8, then back to Step 7
WINDOWS 10
Click this Link: http://pdanet.co/a/
Download PdaNet+ "Version 4.18 installer for Windows" for ex.
If you haven't done yet, unplug your Fire Tab and install PdaNet.
After you installed it completly ADB should be ready now.
Go to Step 7
-------------------------------------------------------------------------
###VIRE SETTINGS###
#Launcher Settings#
Enable reflections - y
Lock Home screen - n
Themes - Stock
Home transition style - Crystal
Advanced Features - include Wallpaper - y
" - Full Screen Transitions - y
" - Enable Frame
" - Enable HD Shaders - y
" - Enable infinite Scroll - y
" - Homescreen - iconlabelsize - large
Icon
Show icon Shadow - y
Icon Style - none
Icon pack Settings - None
Homescreen - Add App - Vire App - Clock
Click to expand...
Click to collapse

thanks for this- tried to download the link in Step 1 but the google drive link is protected. I requested access- email has "ben" in it, just hoping to try this out on my hd7.

I'd REALLY like to be able to follow your guide here, but...
Unfortunately I can't advance past the first couple steps because the google drive link posted in STEP ONE containing all the necessary files requires permission from you before I can download it.
Once you fix this, this guide will really help everyone.

Hell i'm sorry i updated the Link! Going to edit soon, there are a lot of parts pretty undetailed.

thank you, it's downloading for me now

Great, thanks for the Reply about that, just updated the "Tutorial" a bit, so it's maybe a bit more easy to read, my english is so rusted - i didn't even noticed before i wrote it.
As said, i'm going to add much more details, if ANYTHING is unclear, please reply i'm going to detail it more, so no mistakes will happen.

Step 7 CMD window - suggestion for noobs
vismxownz said:
Great, thanks for the Reply about that, just updated the "Tutorial" a bit, so it's maybe a bit more easy to read, my english is so rusted - i didn't even noticed before i wrote it.
As said, i'm going to add much more details, if ANYTHING is unclear, please reply i'm going to detail it more, so no mistakes will happen.
Click to expand...
Click to collapse
Wow! Thank you SO much. Step 7 might be a little unclear. Not sure "first copy the Android ADB Location" -- copy from where?-- and then "write to your Commandprompt" cd (ADB location)" -- do you mean write "cd" (no ") and paste what you copied? Just a thought . . .
Think it would be simpler to just open CMD window from adb.exe folder::
1. Open the folder containing adb.exe. (Should be C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools)
2. Hold down the shift key and right-click a white space in the folder. Choose "open command window here."

also for step 2.1 i wasn't able to get the fire SDK listed in the android SDK manager until i added the following URL
https://s3.amazonaws.com/android-sdk-manager/redist/addon.xml

I have to say that I am pretty underwhelmed by the instructions, since all they do is expand what others have tried for GAPPS with only limited success ...
Btw, the easiest way to get adb drivers is to follow this post, there is much less to download :
http://forum.xda-developers.com/showpost.php?p=58822885&postcount=6
And for the rest, follow the earlier guide to rooted Fire with non-working GAPPS:
http://forum.xda-developers.com/fire-hd/general/playstore-t3110773
Unfortunately, the GAPPS fail to work reliably using similar instructions, and there is no consistent fix yet.
Awaiting more useful instructions now ...

bibikalka said:
I have to say that I am pretty underwhelmed by the instructions, since all they do is expand what others have tried for GAPPS with only limited success ...
Btw, the easiest way to get adb drivers is to follow this post, there is much less to download :
http://forum.xda-developers.com/showpost.php?p=58822885&postcount=6
And for the rest, follow the earlier guide to rooted Fire with non-working GAPPS:
http://forum.xda-developers.com/fire-hd/general/playstore-t3110773
Unfortunately, the GAPPS fail to work reliably using similar instructions, and there is no consistent fix yet.
Awaiting more useful instructions now ...
Click to expand...
Click to collapse
First I want to say thank you for the instructions this is a more detailed version of the steps I was taking. I had full intention to clean up my guide once we solved the problems we are currently having. I'm pretty sure these steps above are the basic steps of getting the Playstore but we are still not without issues. I'd be interested to see how many people this is working.

After all that, i still dunno why People got still issues - in first place with PlayStore.
It's the 6th (and 5th Day) for both HD 7" - still everything is working - PlayStore, also downloads and Cache Cleaning like a charm.
Also the Tablet seems to work faster now, cause of disabled Amazon Startup-Apps.
Also bibikalka is right, there are less big downloads, also you can evade downloading the whole SDK if you do not like, to. But you safed it for Future uses and instructions.
Also my first DL is above 100MB because it also includes the GAPPS, they are working as said and still working after nearly a week of usage on 2 Fire Tabs.
Just wanted to help, not that pro in writing instructions as you may already know.

But after all this, is Play Store application working?

devicer said:
But after all this, is Play Store application working?
Click to expand...
Click to collapse
As said before, nearly a week without any problems. Applications updating fine (for sure execluding Google Apps, don't updating anymore) - they should work until there is a update wich REQUIRES a newer Version of any GAPPS. But as said they work.

Thanks for the tutorial!!!
I got supersu and playstore installed and worked. This is what I did.
First I used playsevice 6.5.99_(xxxxxxxxxx-034) the last 3 number (-034) suppose to be the correct one for HD6. It work only the first time then update itself to 7.3.29 so no good.
So I changed to playservice 6.1.88_(xxxxxxxxxx-032). This one so far working very good after a few reboots. It won't update itself. Maybe because its not the correct one? But since it work so who care.
Now I can download apps, games no problem at all. So anybody got problem, maybe try playservice 6.1.88_(xxxxxxxxxx-032). I think thats a reason.

droidnext said:
Thanks for the tutorial!!!
I got supersu and playstore installed and worked. This is what I did.
First I used playsevice 6.5.99_(xxxxxxxxxx-034) the last 3 number (-034) suppose to be the correct one for HD6. It work only the first time then update itself to 7.3.29 so no good.
So I changed to playservice 6.1.88_(xxxxxxxxxx-032). This one so far working very good after a few reboots. It won't update itself. Maybe because its not the correct one? But since it work so who care.
Now I can download apps, games no problem at all. So anybody got problem, maybe try playservice 6.1.88_(xxxxxxxxxx-032). I think thats a reason.
Click to expand...
Click to collapse
Yes the GoogleCode got Patchday and 034 got patched. BUT to evade you also can go to your SysCustomizer and Reset the Google Play-Service to "Systemdefault" so it resets back to the first installed version. Until this gets a problem you can do it over and over again, so it would take just like 1 minute to fix the issue. Also there is no error or fail in using an "outdated" Version. Thanks for your Sharing i updated my uploadings

Everything is working now, and does not self update, see here :
http://forum.xda-developers.com/fire-hd/general/root-play-store-short-disabled-self-t3113975

Anyone else have problems setting up supersu?
Sent from my LG-V480 using Tapatalk

I'm waiting for the tuto video
thanks for the work btw !!!

Wich Problems?
greetings

So if we want the Google play store, we won't be able to use the default launcher anymore ? damn it ...
is it an obligation ?

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?