Related
Hi guys,
My Kindle just arrived and I really want to root it but I'm really confused as to the order and steps required to do so. I'm by no means a rooting newbie, I had a G1 and a Vibrant, but I can't find any consistent/up-to-date information for everything. Would anyone be willing to do a quick step-by-step write up for me? It would be much appreciated!
It depends on the version you have.
- For the latest one, just updated by Amazon as an OTA update, 6.2.1, there is not a permanent root by now. Read "TWRP Installer (Any Firmware Version)" by Vashypooh in Development section for a new exploit by Jcase of TeamAndIRC.
You can just use a "factory cable" (ID pin pulled-up to vcc) to start to fastboot, install from TWRP from there and a pre-rooted 6.2.1 version (or CM7 if you prefer).
Some people say that pre-rooted 6.2.1 has finaly updated to stock 6.2.1 and lost root.
- For 6.1 or 6.2 you can root with OneClickRoot, or just with Kindle Fire Utility v.6
If you have used adb or fastboot before just take a look at the source of both scripts (TWRP Installer and Kindle Fire utility) to see what they do step by step. They are very clear.
jovi_juan said:
It depends on the version you have.
- For the latest one, just updated by Amazon as an OTA update, 6.2.1, there is not a permanent root by now. Read "TWRP Installer (Any Firmware Version)" by Vashypooh in Development section for a new exploit by Jcase of TeamAndIRC.
You can just use a "factory cable" (ID pin pulled-up to vcc) to start to fastboot, install from TWRP from there and a pre-rooted 6.2.1 version (or CM7 if you prefer).
Some people say that pre-rooted 6.2.1 has finaly updated to stock 6.2.1 and lost root.
- For 6.1 or 6.2 you can root with OneClickRoot, or just with Kindle Fire Utility v.6
If you have used adb or fastboot before just take a look at the source of both scripts (TWRP Installer and Kindle Fire utility) to see what they do step by step. They are very clear.
Click to expand...
Click to collapse
That's not what I need. I need to know what order to install them in and, preferably, step by step instructions on how to do it from a pre 6.2.1 version.
r0man said:
That's not what I need. I need to know what order to install them in and, preferably, step by step instructions on how to do it from a pre 6.2.1 version.
Click to expand...
Click to collapse
FIREFIREFIRE is included with TWRP
1) install drivers included with Kindle Fire Utility
2) launch utility and install TWRP following the script instructions. This uses ZergRush to gain root access, but I'm not sure if this is a permanent root, if not, just use SuperOneClick to get it
I am about as confused as you re but I think I might start to catch on what to do.
My impression of what to do is the following(someone please correct this list, will help both me and the starter of the thread):
For 6.2 and lower
1. Get Kindle Fire Utility
2. Install the drivers included for your kindle fire
3. Flash TWRP 2.0 by choosing that option in the utility
4. When it is done flashing, restart the device and somehow you should be able to enter TWRP(which is just like CWM but for touch devices)
5. From TWRP you should be able to select to install a new ROM
6. Restart and enjoy your new ROM
There are many of these steps that probably lacks a lot of details such as "should i clear cache before installing ROM?" and so on.
The thing that I feel is nmost uncertain is if you need to do somethign more than just press install TWRP in the utility. Or is it simple as that?
I suggest being familiar with adb, fastboot, and command line. use the universal tool instead by hashypooh
Sent from my HTC Glacier using xda premium
I am back to full root with TWRP installed after following the new method from androidpolice.com. After I did that, then I was able to install TWRP according to the instructions at Rootzwiki. I would post the links, but the forum won't let me because I haven't had enough posts. My KF was updated to 6.2.1 and I had lost root, but everything is back to normal with root now!
This guide is for never-rooted 2014 Fire HDs. Don't use it on any 2015 (5th gen) Fire. If your Fire has an sd card slot, go here.
Mar 3 Update: This guide is out of date. It could brick you! Don't use it!
Instead, follow one of these guides:
http://forum.xda-developers.com/fire-hd/general/root-os-5-1-2-kingroot-tools-play-store-t3371824
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Ignore these hidden text boxes
Feb. 5, 2016 Update: Don't use this to root OS 5.1.1 yet. It needs to be updated!!
Jan. 18, 2016 Update: Don't use this guide if you are running OS 4.5.5.1.
Look at Settings->Device->System Updates. If it says 4.5.5.1, installing the Developer Preview will brick your device.
Before You Begin:
OS 4.5.4, 4.5.5 (NOT 4.5.5.1) - Follow these steps to install the Developers Preview (OS 5):
Here are 2 methods. If you request it from Amazon it could take 24 hours, but if it causes problems you have proof that it downloaded to device. If you don't care about that and want it right now, use method 2.
1/23/16 UPDATE: Developers Preview is no longer available from Amazon. Method 2 is the only option.
Keep in mind, this is your choice. We can no longer blame Amazon for downloading "bad" firmware to device.
1/22/16 UPDATE: Use only method 2 until the risk of OTA updating to 4.5.5.1 is over.
METHOD 1 - From Amazon
Go here and request the developers preview: https://developer.amazon.com/public...campaign=FireOSPreview&sc_ detail=GetPreview]
It could take 24 hours but usually doesn't.
Goto Settings->Device->System Updates and press "Update Now"
If it doesn't download, wait an hour and try again.
METHOD 2 - From device
Turn OFF wifi.
Get update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin from here.
Copy/move the update file to device
Goto Settings->Device->System Updates and press "Update Now"
The file will install. [long startup.]
If you haven't installed adb drivers, do that now and you're ready to go! Be sure to keep wifi off.
Note: If it hasn't booted after 20 minutes--it's stuck at "Fire" logo--hold down Power and Volume-up buttons to get to recovery menu. In recovery, factory reset, wipe cache and then boot to system.
OS 4.5.3 - Keep wifi OFF. Put the tablet into airplane mode immediately.
.
OS below 4.5.3 - Follow these steps to install OS 4.5.3:
Turn OFF wifi.
Download the 4.5.3 update to pc and copy/move it to device.
Go to Settings->Device->System Updates and press "Update Now."
The file will install. [long startup.]
If you haven't installed adb drivers, do that now and you're ready to go!
Install adb device drivers. Here's an illustrated guide for Windows.
* OS 5.0.n: Install driver for both OS mode and sideload mode.
* OS 4.5.3: Install driver for OS mode only.)
.
If you don't know how to drag & drop or copy/paste into the terminal/CMD window, read this.
This guide simply pulls together existing material, almost none of which is original to me. All thanks go to Powerpoint45, who discovered how to downgrade to rootable OS 4.5.3; bibikalka for the ingenious recovery-swap update method that preserves root; seigesoldier, hawkazn and hariiiii for file captures and fearless testing.
A - Root!
Make sure ADB drivers are installed and adb is enabled in Developer Options.
Turn OFF wifi (airplane mode)
OS 4.5.3 - Download Kingroot (link below), open a terminal/CMD window from the folder you put it in, and go to step 6.
OS 5.0.n - Download to computer:
- 4.5.3 update bin: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
- Kingroot: http://www.kingroot.net/
Downgrade to 4.5.3 (thanks to @powerpoint45):a. Connect to computer and open terminal/CMD window from folder containing bin file and kingroot.
b. Enter: adb reboot recovery
c. On tablet, use volume buttons to select “apply update from ADB” and then press power.
d. If you KNOW you have working adb driver for sideload mode, go to step e. Otherwise, see here:
To see if sideload-mode driver is installed, open Device Manager and see if your adb driver is listed under Android Device.
- If it is, close this text box and continue the steps.
- If it IS NOT and you're on Windows, do the following:
(1) Find KFARWI under "Other devices." NOTE: If you don't see KFARWI under "Other," disconnect/reconnect and look again.
(2) Right-click KFARWI and select "Update Driver Software." [see Update Driver Software screen].
(3) Click "Browse my computer" and then "Let me pick from a list . . ." [see Select your device type . . ."]
(4) Click Android Device. [see "Select the device driver you want . . .]
(5) Select your usual adb driver from the list, press Next, and say yes at warning screen. [see "Windows has successfully updated your driver software"]
(6) In CMD window, run adb devices and confirm you see your device ID and "sideload," like this:List of devices attached
SERIALNUMBER sideloadIf you don't see serial number, reboot tablet and computer and repeat "adb reboot recovery" and "Apply update from ADB" steps. Device should now be recognized.
e. From computer, enter: adb sideload update-kindle-20.4.5.3_user_453011120.bin
f. On tablet select "wipe data/factory reset" and then "reboot system" [long startup]
Enter language in Amazon setup, but skip registration and keep wifi OFF.
On computer, enter commands to block OTA:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Install Kingroot from computer: adb install app_filename.apk
Turn on wifi, run Kingroot on Fire and press "root." If you don't get success (100%), keep trying.Kingroot works over wifi, so do this where signal strength is best.
If the latest Kingroot from the link just won't work, try version 4.0.0 or 4.0.1 downloaded from any safe site.
On computer, give commands to confirm su access, granting root access on tablet when prompted:
adb shell
su
(In Windows, a # prompt indicates root.)
Type exit two times to get out of su.
B - Install TWRP and Get Files for the Upgrade
Download JMZ's ariel TWRP image to the Fire's download folder (or to computer and move to tablet).
Download Flashify v 1.9.1 to computer folder where you opened CMD window.
Install Flashify from computer: adb install app_filename.apk
Run Flashify on Fire and install the ariel TWRP.
If you have any question, follow the steps here. You must select Recovery image and Choose a File, and navigate to the ariel image.
Boot to recovery and confirm you're in TWRP:
adb command = adb reboot recovery; manual = power off, hold power & volume-up buttons until Amazon logo appears and then let go.
Tap Reboot, then System to boot back to OS.
Delete anything in tablet Download folder and get files for the upgrade.
.
Files for the Upgrade
Please hit Thanks when you pick up a file from an XDA site
Download apks to computer for later install.
- SuperSU: http://www.apkmirror.com/apk/chainfire/supersu/supersu-2-52-android-apk-download/
- ES File Explorer: http://www.apkmirror.com/apk/es-glo...file-explorer-4-0-2-3-3-android-apk-download/
Download to tablet (or to computer and move to tablet Download folder):
➜ Take care here: Be sure to get the right files and that they all download completely.
- 5.2.2u2 UPDATE BIN (linked in the post) This is update-kindle-full_ariel-20.5.2.2_user_522053520.bin
Confirm downloaded filename matches the above and then rename the extension from .bin to .zip.
- 5.2.0 STOCK RECOVERY ONLY (5.2.0_stock_recovery_only.zip - attached to post) AND . . .
- MAKE_SPACE (make_space_v01.zip - attached to post)
- Latest PICO-uni GAPPS: Get "tk_gapps-modular-pico-5.1.1(uni)-5.1.1-*-signed.zip"
C - Upgrade to OS 5.0.1 and Install Gapps
Bibikalka's Lollipop guide has info about the upgrade (and a Thanks button we all ought to hit!)
The boots into recovery and the OS can take a long time; don't interrupt them (by trying to manually reboot, e.g.)
Turn OFF wifi and connect to computer.
Boot to recovery. (Manually or "adb reboot recovery" from pc).
[TWRP screen displayed on tablet.]
In TWRP, do following exactly and if you have any problem, post immediately and wait for reply :
a. Factory reset (Tap Wipe and swipe "Swipe to Factory Reset." At "Successful," tap TWRP home icon at bottom-left)
b. Install the update-kindle-full_ariel-20.5.2.2 UPDATE zip
. . (Tap Install button, navigate to Downloads folder and tap the UPDATE zip. Repeat for the following zips.)
c. Install the 5.2.0 STOCK RECOVERY ONLY zip
d. Install the MAKE_SPACE zip
e. Install the GAPPS zip
f. Tap Reboot > Recovery and when prompted (top of screen) "install SuperSU?," swipe the slider to install it!
[long startup]
➜ You're now running rooted OS 5.0.1 and TWRP is gone. If you need it again, see here. Do not try to reinstall TWRP with Flashify. (Brick!)
Confirm you see stock 5.2.0 recovery.
If tablet doesn't boot to recovery or is still booting after 30 minutes, post in bibikalka's Lollipop thread
Reboot to system [takes at least 10 minutes] and when prompted on tablet to allow USB debugging, say "yes"
- If you miss "Allow USB debugging" prompt, unplug/replug to see it
- If tablet bootloops or is still booting after 40 minutes, see step 4 in bibikalka's Lollipop thread
At Setup screen, press Exit (or choose language if required). Do not connect to wifi; tap COMPLETE SETUP LATER.
D - Install the Apps, Block OTA and Open Play Store
On computer, open terminal/CMD window from folder containing ES File Explorer and SuperSU apks and install each with this command:
adb install -r app_filename.apk
On tablet:
a. Enable apps from unknown sources in Settings > Security.
b. Run File Explorer and enable Root Explorer (in menu under Tools), granting root access when prompted.
c. Run SuperSU to update binaries and reboot when prompted.
. . [If SuperSU gives choice of "CWM/TWRP" or "Normal," choose Normal]
Block OTA:
a. In the terminal/CMD window, enter these commands granting root access on tablet after the su command:adb shell
su
pm disable com.amazon.otaverifier
pm enable com.amazon.dcp <--(renables dcp from Section A. This block is not needed after you do the next step.)b. Use File Explorer on tablet to navigate to /system/priv-app/DeviceSoftwareOTA and rename extension of DeviceSoftwareOTA.apk to .apk_
Turn on wifi, open Play Store and sign in.
Register the Fire HD with Amazon.
Whew! Yay! :victory:
Some brave soul still needs to try to flash GAPPS during the 5.2.0 install in TWRP
If that fails, one will have to downgrade to 4.5.3, root, and get back to 5.2.0. So 20 minutes tops, not the end of the world ...
Yes, purposefully didn't put it in cuz untested. I'm thinking about it per your post at other thread. Just need to gird my loins
In Section C Step 7 adb returns failure due to the app already existing. When I was in Step 3f TWRP gave me the option to skip root install or to install SuperSu, which it only does the installer and that requires Google Play or TWRP to complete the installation. What should I do there?
ROMAddiction said:
In Section C Step 7 adb returns failure due to the app already existing. When I was in Step 3f TWRP gave me the option to skip root install or to install SuperSu, which it only does the installer and that requires Google Play or TWRP to complete the installation. What should I do there?
Click to expand...
Click to collapse
As the first line says, This guide is only for Fire HDs running the unrooted Developer Preview of Lollipop. I will clarify that. Since you had SuperSU installed, at C7 use "adb install -r name_of_your_supersu.apk." I assume you said yes at step 3f when prompted to root, but I do not understand this phrase, "which it only does the installer and that requires Google Play or TWRP to complete the installation."
DoLooper said:
As the first line says, This guide is only for Fire HDs running the unrooted Developer Preview of Lollipop. I will clarify that. Since you had SuperSU installed, at C7 use "adb install -r name_of_your_supersu.apk." I assume you said yes at step 3f when prompted to root, but I do not understand this phrase, "which it only does the installer and that requires Google Play or TWRP to complete the installation."
Click to expand...
Click to collapse
Yeah, I started out with my Fire on the developer's build and have been working my way back to it with root. I did say yes at step 3f and TWRP then installed a SuperSu Installer App. When you tap on the app it says it will install SuperSU but either from the Google Play Store or through TWRP. This is where I'm stuck because I can't install it from the Play Store or from TWRP, nor can I use ADB and install it from there because it says that SuperSu is already on my Fire.
Sent from my LG-H811 using XDA Forums Pro.
ROMAddiction said:
Yeah, I started out with my Fire on the developer's build and have been working my way back to it with root.
Click to expand...
Click to collapse
If you were on 4.5.4 and wanted to get to rooted 5.2.0, this is the guide you wanted: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950. But I thought you had done that and that's when you lost recovery. Oh, well, doesn't matter now, as long as you were able to boot to stock recovery at step C4.
Did you reinstall superSU with "adb install -r name_of_your_supersu.apk." as said in my last post? (Notice the -r) Please do that and continue the steps. Let me know if "adb shell" "su" does not show you're rooted. If step 13 insists on Play Store, skip that step, finish the guide and run SuperSU after Gapps is installed. Please let me know if you have to skip step 13, so I can edit the guide. Thank you.
DoLooper said:
. . . Since you had SuperSU installed, at C7 use "adb install -r name_of_your_supersu.apk."
Click to expand...
Click to collapse
DoLooper said:
If you were on 4.5.4 and wanted to get to rooted 5.2.0, this is the guide you wanted: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950. But I thought you had done that and that's when you lost recovery. Oh, well, doesn't matter now, as long as you were able to boot to stock recovery at step C4.
Did you reinstall superSU with "adb install -r name_of_your_supersu.apk." as said in my last post? (Notice the -r) Please do that and continue the steps. Let me know if "adb shell" "su" does not show you're rooted. If step 13 insists on Play Store, skip that step, finish the guide and run SuperSU after Gapps is installed. Please let me know if you have to skip step 13, so I can edit the guide. Thank you.
Click to expand...
Click to collapse
Ah, no I had been updated to 4.5.5 the other day and was wanting to roll back and root my Fire to make it much more useful to me. Signed up as a Developer to get it to update me to the 5.2 update and then followed the steps here to get me rooted and back to 4.5.3, etc.
I did the adb install -r with the apk and it loaded, but not in the app drawer. I could find it in Settings under Apps but the App Info wouldn't let me do anything like Force Stop or Clear Cache. Thinking that I may have to start back over from the beginning to fix this. Always make some sort of screw up when I do this sort of thing. Hopefully I won't have to bother you with anything again. I'll check to see if abd shell will tell me if I'm good and get back to you. Thanks for the help!
Sent from my LG-H811 using XDA Forums Pro.
ROMAddiction said:
I did the adb install -r with the apk and it loaded, but not in the app drawer. I could find it in Settings under Apps but the App Info wouldn't let me do anything like Force Stop or Clear Cache. Thinking that I may have to start back over from the beginning to fix this. Always make some sort of screw up when I do this sort of thing. Hopefully I won't have to bother you with anything again. I'll check to see if abd shell will tell me if I'm good and get back to you. Thanks for the help!.
Click to expand...
Click to collapse
Please do "bother" me again. You're first to use this.
Please confirm you got into recovery OK. Also, do step 8 and post result from su command.
Don't worry about the superSU app right now. Just post above, then finish the steps, skipping running superSU. Please do not start back from the beginning.Thank you.
DoLooper said:
Please do "bother" me again. You're first to use this.
Please confirm you got into recovery OK. Also, do step 8 and post result from su command.
Don't worry about the superSU app right now. Just post above, then finish the steps, skipping running superSU. Please do not start back from the beginning.Thank you.
Click to expand...
Click to collapse
Alright! When I get home tonight I'll complete the rest of the steps as best as possible.
Sent from my LG-H811 using XDA Forums Pro.
Hint: You can also flash tk gapps in twrp
meganoahj said:
Hint: You can also flash tk gapps in twrp
Click to expand...
Click to collapse
Right! Did you do that--flash 5.2.0 UPDATE, RECOVERY then GAPPS before rebooting to 5.2.0 recovery? Bibikalka and I have been wanting to know if that'd been tested yet. thanks.
DoLooper said:
Right! Did you do that--flash 5.2.0 UPDATE, RECOVERY then GAPPS before rebooting to 5.2.0 recovery? Bibikalka and I have been wanting to know if that'd been tested yet. thanks.
Click to expand...
Click to collapse
Yes i done that, now you have The new lollipop Google Login when you add a Google account
And All works play Services updating and All fine (im on OS 5 with root,tkgapps,xposed framework)
meganoahj said:
Yes i done that, now you have The new lollipop Google Login when you add a Google account
And All works play Services updating and All fine (im on OS 5 with root,tkgapps,xposed framework)
Click to expand...
Click to collapse
Hey, that's great! Couple questions:
You got Gapps from here? http://forum.xda-developers.com/android/software/tk-gapps-t3116347/post60944096#post60944096
Which package?
Do you know how much space you had left in /system after the update (and before you added anything else)?
Any chance you flashed Xposed at same time?
@bibikalka will also be glad to hear this! Thanks!
DoLooper said:
Please do "bother" me again. You're first to use this.
Please confirm you got into recovery OK. Also, do step 8 and post result from su command.
Don't worry about the superSU app right now. Just post above, then finish the steps, skipping running superSU. Please do not start back from the beginning.Thank you.
Click to expand...
Click to collapse
When I perform: option: adb shell
su
It returns 1|[email protected]:/ $
I'm going to try "option: adb install -r name_of_your_supersu.apk" here and see if that makes a difference.
Edit: That did it! SuperSu installed, Google Play Store/Services installed, and I'm good to go.
DoLooper said:
Hey, that's great! Couple questions:
You got Gapps from here? http://forum.xda-developers.com/android/software/tk-gapps-t3116347/post60944096#post60944096
Which package?
Do you know how much space you had left in /system after the update (and before you added anything else)?
Any chance you flashed Xposed at same time?
@bibikalka will also be glad to hear this! Thanks!
Click to expand...
Click to collapse
Yes i got gapps from There
Gapps: Pico Modular Package (Proper DPI Play Services)
I flashed xposed after the reboot to fire os 5 (back to twrp method)
but i think you can flash xposed after the gapps!
And i dont Know the space free in /system cuz im installed gapps directly after flashing the Update!
Ah sorry i forget that after i flashed xposed framework anytime my fire boots i got the android is upgrading screen
10 seconds long
meganoahj said:
I flashed xposed after the reboot to fire os 5 (back to twrp method)
but i think you can flash xposed after the gapps!
And i dont Know the space free in /system cuz im installed gapps directly after flashing the Update!
Click to expand...
Click to collapse
I meant how much space in /system after you got back to OS , after the upgrade and before deleting/adding any system apps. So, how much space in /system now?
meganoahj said:
Ah sorry i forget that after i flashed xposed framework anytime my fire boots i got the android is upgrading screen
10 seconds long
Click to expand...
Click to collapse
I got Xposed same way as you and don't get that. Maybe it's a module you installed(?)
Other than Kingroot taking forever and Xposed refusing to flash in TWRP everything went great and I was finally able to install all my apps from the Play Store on my wife's tablet following this guide.
Many thanks!
DoLooper said:
I meant how much space in /system after you got back to OS , after the upgrade and before deleting/adding any system apps. So, how much space in /system now?
I got Xposed same way as you and don't get that. Maybe it's a module you installed(?)
Click to expand...
Click to collapse
With gapps + xposed is 49.8 mb free in /system
I had the upgrading screen also without an Module
Please DO NOT use this guide anymore due to bricks. Instead use an up to date guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
I was debating whether to make a new thread or not but ended up doing so. First off I want to thank the people on XDA including @bibikalka , @DoLooper , and @jmz who made everything work. I'm a visual & hands-on learner so I like making these types of tutorials and I hope others who favor more visual tutorials will find them useful as well. This video guide is a combo from guides from @bibikalka (ROOT & GAPPS & OTHER) , @DoLooper (ROOT & GAPPS & OTHER) , and @jmz (TWRP).
This video tutorial explains how you can get root, GAPPS, and the Play Store on Fire OS 5.0. This video is one of the more andvanced ones and contains many steps. I take no responsibility if something happens to your device. Try to follow the video as close as you can and you sould be fine. The basic process consists of downgrading to a root vulnerable OS, rooting it and installing TWRP, then through TWRP install the new 5.0 version and then GAPPS, root, etc.
Video
www.youtube.com/watch?v=gC0nm8I3IFE
Here are the in depth steps. Follow along with video for more insight:
1.Install USB ADB drivers: https://www.youtube.com/watch?v=CyJlmTtLsIg
Download Software version 4.5.3: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
Reboot into recovery: "adb reboot recovery"
Enter sideload mode from recovery
Install v4.5.3: "adb sideload update-kindle-20.4.5.3_user_453011120.bin"
Wiipe data/ factory restet from recovery
Reboot & keep wifi off so that it does not re-update
Disable ota updates with "adb shell pm block com.amazon.dcp" and "adb shell pm block com.amazon.otaverifier"
Turn on wifi
Download kingroot from http://www.kingroot.net/ onto device
Root with app
Test root with "adb shell" and "su"
Download TWRP IMG: https://drive.google.com/file/d/0Bx_94ujbh0qobGpZcGV6aHNKT3M/view?usp=sharing
Check md5sum: 4fefd8b46ca97a2b66e4c8852d4c3396
Push recovery to device with "adb push openrecovery-twrp-2.8.6.0-ariel.img /data/local/tmp"
Go into root shell with "adb shell" and "su"
Go to /data/local/tmp/ directory: "cd /data/local/tmp/"
Install TWRP: "dd if=openrecovery-twrp-2.8.6.0-ariel.img of=/dev/block/mmcblk0p7"
Test TWRP with "adb reboot recovery"
Boot back up
Download 5.2.2 firmware: https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
Download 5.2.0 stock recovery: http://forum.xda-developers.com/attachment.php?attachmentid=3416498&d=1437711793
Download pico gapps package (Play Store etc): https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Download make_space zip: http://forum.xda-developers.com/attachment.php?attachmentid=3519998&d=1445918906
Move firmware, recovery, gapps, and make_space zip onto Fire internal storage
Rename 5.2.2 firmware to a .zip file instead of a .bin file so TWRP recognizes it
Reboot into TWRP: "adb reboot recovery"
STEPS 28-33 MUST BE DONE IN ONE SESSION
Do another factory reset
Flash 5.2.2 firmware
Flash 5.2.0 recovery
Flash/run make_space zip to clear up system space
Flash Pico GAPPS zip
Choose reboot into recovery from TWRP and tell TWRP that you would like to install superSU
Reboot device and wait for it to boot up (will take about ten minutes)
After booted up, disable ota updates with "adb shell", "su", "pm disable com.amazon.otaverifier", and "pm enable com.amazon.dcp"
Update SuperSU from Play Store, open it and choose to install normally
Root, GAPPS, and Play Store should all be working now
Click to expand...
Click to collapse
Notes:
Do not try to re-flash TWRP the same way you did on 4.4.3. It will not work
Click to expand...
Click to collapse
Links & Downloads:
•XDA Guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
•USB driver tutorial: https://www.youtube.com/watch?v=CyJlmTtLsIg
•4.5.3 software: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
•KingRoot: http://www.kingroot.net/
•TWRP image: https://drive.google.com/file/d/0Bx_94ujbh0qobGpZcGV6aHNKT3M/view?usp=sharing
•5.2.2 firmware: https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
•5.2.0 stock recovery: http://forum.xda-developers.com/attachment.php?attachmentid=3416498&d=1437711793
•pico gapps package (Play Store etc): https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
•make_space zip: http://forum.xda-developers.com/attachment.php?attachmentid=3519998&d=1445918906
Click to expand...
Click to collapse
Detailed tutorial
Will try later today.
Thanks a lot for the video. Used it and got everything working no problems!
argrr101 said:
Thanks a lot for the video. Used it and got everything working no problems!
Click to expand...
Click to collapse
Awesome to hear. Enjoy
Sent from my KFARWI using Tapatalk
powerpoint45 said:
I was debating whether to make a new thread or not but ended up doing so. First off I want to thank the people on XDA including @bibikalka , @DoLooper , and @jmz who made everything work. I'm a visual & hands-on learner so I like making these types of tutorials and I hope others who favor more visual tutorials will find them useful as well. This video guide is a combo from guides from @bibikalka (ROOT & GAPPS & OTHER) , @DoLooper (ROOT & GAPPS & OTHER) , and @jmz (TWRP).
This video tutorial explains how you can get root, GAPPS, and the Play Store on Fire OS 5.0. This video is one of the more andvanced ones and contains many steps. I take no responsibility if something happens to your device. Try to follow the video as close as you can and you sould be fine. The basic process consists of downgrading to a root vulnerable OS, rooting it and installing TWRP, then through TWRP install the new 5.0 version and then GAPPS, root, etc.
Video
www.youtube.com/watch?v=gC0nm8I3IFE
Here are the in depth steps. Follow along with video for more insight:
Notes:
Links & Downloads:
Click to expand...
Click to collapse
Got a " E: failed to verify whole-file signature" error message when trying to sideload 4.5.3 update
2006yamahaR6 said:
Got a " E: failed to verify whole-file signature" error message when trying to sideload 4.5.3 update
Click to expand...
Click to collapse
Hmm. Maybe try redownloading the update file as it cold be corrupted. I'm really not sure about this one
@DoLooper you've got any ideas?
Sent from my KFARWI using Tapatalk
@powerpoint45 Are you using the Amazon launcher or a custom one? Has anyone tried to change the launcher using the method that worked for 4.5.3?
2006yamahaR6 said:
Got a " E: failed to verify whole-file signature" error message when trying to sideload 4.5.3 update
Click to expand...
Click to collapse
powerpoint45 said:
Hmm. Maybe try redownloading the update file as it cold be corrupted. I'm really not sure about this one
@DoLooper you've got any ideas?
Click to expand...
Click to collapse
Only that a search turns up lots of hits.
argrr101 said:
@powerpoint45 Are you using the Amazon launcher or a custom one? Has anyone tried to change the launcher using the method that worked for 4.5.3?
Click to expand...
Click to collapse
I'm using a custom one. If you have root just install your custom Launcher, go into adb shell, type "su", and then "pm disable com.amazon.firelauncher"
Sent from my SPH-L710 using Tapatalk
argrr101 said:
[MENTION=4469251]Has anyone tried to change the launcher using the method that worked for 4.5.3?
Click to expand...
Click to collapse
This is for latest OS 5.0.1 (5.2.2u2). Be sure to install custom launcher first. Need to be in SU.
pm disable com.amazon.firelauncher
Thanks, got Nova Launcher up and working.
cxm170 said:
Will try later today.
Click to expand...
Click to collapse
works like a charm
. thanks
Excellent write-up I didn't even bother watching the video... My hd6 is now working as it should!
One note - I had to register with both Amazon and Google via wifi before I could update SuperSU and disable ota updates through adb. Not sure if I did something wrong, but that's how it ended up working for me.
Hello, I have tried this tutorial but I'm unable to downgrade to 4.5.3
I get a signature verification error when sending the file; the exact error from the recovery logs is:
Code:
I: failed to verify against RSA key 0
E: failed to verify whole-file signature
The installed OS version is 5.0.1 on a Fire 5th generation.
Does anyone have a solution for this problem?
Get the same error :
E:failed to verify whole-file signature
E: signature verification failed
Installation aborted
Can smone help pls?
I followed this guide to root my fire, it worked.
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
wasted whole day, try 3 times already, doesn't work on Fire HD6, Followed all the steps, upgraded from 4.5.5 to 5.0.1 Preview, then downgraded to 4.5.3, install KingRoot to get su, install TWRP, copy all zip packages, flash them, reboot via TWRP to install superSU and after 10 minutes it shows kindle fire OS 5.0.1, and to perform step 35, no SU access any more, can't complete step 35, such a wastage of hours and hours
george9584 said:
wasted whole day, try 3 times already, doesn't work on Fire HD6, Followed all the steps, upgraded from 4.5.5 to 5.0.1 Preview, then downgraded to 4.5.3, install KingRoot to get su, install TWRP, copy all zip packages, flash them, reboot via TWRP to install superSU and after 10 minutes it shows kindle fire OS 5.0.1, and to perform step 35, no SU access any more, can't complete step 35, such a wastage of hours and hours
Click to expand...
Click to collapse
Man I am glad I read this post... I have a Gen 4 HD6 that came with 4.5.5, and I would LOVE to get root and GAPPS and make this thing work the way it should, but these tutorials are confusing as hell...
Do we use ADB+Fastboot or do we have to install ADB from the SDK? There is NO mention of this in the video tutorials... I am confused.
Not everyone uses Linux. I am on a Windows box here at work and would love to make this happen... Can anyone shed light?
Hello,
@Team Scream, I suggest you look at Imma Wake's video "Downgrade and root Fire HD6/HD7". This one is giving you all you need to move from 4.5.5 to 5.0.1 and get root rights. It's shorter(18 steps) and rather self-explanatory. As an example, I did it today without any hiccups.
I used ADB+Fastboot (the one he made a video about), but didn't had to use any fastboot command. So don't get confused, it's just a rather simple way to get ADB up and running.
If it may be of any help, just know that I had to re setup the driver in the device manager will the tab was in sideload mode.
@powerpoint45 not forgetting ppl who made this tutorial possible, I deeply thank you for the tremendous work you've done! I will give it a shot soon hopping it goes as smoothly as the guide i mention before.
All the best,
EDIT
It all went smooth and easy.
So here is my backlog:
"Fire HD6" on "Fire OS 4.5.5"
Upgrade to 5.0.1 (dev version)
Downgrad to 4.5.3 and grant ROOT access via kingroot. (followed the 18 step tutorial made prior to this one. check his youtube videos. additionnaly I did "adb shell pm block com.amazon.dcp" not mention in the 18, but 37steps tutorial just to be safe about OTA stuff)
Catch up on this tutorial at step12. Upgraded to 5.0 + ROOT + GAPPS + Play Store
@powerpoint45, You may want to swap step 35 and 36 because by the time you reach 35, you can't "su" in "adb shell". In fact, 36 is meant to allow "su" usages as far as i can tell
Due to the above "su" issue, I was scared that during the SuperSU setup(needing Wifi and prior to OTA disable) between step 34 and 36 is that some update happen eventually transforming a piece of cake into nightmare. Is it something to be worried about for ppl following your tutorial?
Lastly, the "System Updates" panel state "Fire OS 5.0.1", but isn't "5.2.2 firmware" + "5.2.0 stock recovery" suppose to increase the OS number to 5.2.X? (that's the rookie question I suppose)
Once again, thank you very much for this great video tutorial and all the best to you stepping into it.
user0x80 said:
Hello,
@Team Scream, I suggest you look at Imma Wake's video "Downgrade and root Fire HD6/HD7". This one is giving you all you need to move from 4.5.5 to 5.0.1 and get root rights. It's shorter(18 steps) and rather self-explanatory. As an example, I did it today without any hiccups.
I used ADB+Fastboot (the one he made a video about), but didn't had to use any fastboot command. So don't get confused, it's just a rather simple way to get ADB up and running.
If it may be of any help, just know that I had to re setup the driver in the device manager will the tab was in sideload mode.
@powerpoint45 not forgetting ppl who made this tutorial possible, I deeply thank you for the tremendous work you've done! I will give it a shot soon hopping it goes as smoothly as the guide i mention before.
All the best,
EDIT
It all went smooth and easy.
So here is my backlog:
"Fire HD6" on "Fire OS 4.5.5"
Upgrade to 5.0.1 (dev version)
Downgrad to 4.5.3 and grant ROOT access via kingroot. (followed the 18 step tutorial made prior to this one. check his youtube videos. additionnaly I did "adb shell pm block com.amazon.dcp" not mention in the 18, but 37steps tutorial just to be safe about OTA stuff)
Catch up on this tutorial at step12. Upgraded to 5.0 + ROOT + GAPPS + Play Store
@powerpoint45, You may want to swap step 35 and 36 because by the time you reach 35, you can't "su" in "adb shell". In fact, 36 is meant to allow "su" usages as far as i can tell
Due to the above "su" issue, I was scared that during the SuperSU setup(needing Wifi and prior to OTA disable) between step 34 and 36 is that some update happen eventually transforming a piece of cake into nightmare. Is it something to be worried about for ppl following your tutorial?
Lastly, the "System Updates" panel state "Fire OS 5.0.1", but isn't "5.2.2 firmware" + "5.2.0 stock recovery" suppose to increase the OS number to 5.2.X? (that's the rookie question I suppose)
Once again, thank you very much for this great video tutorial and all the best to you stepping into it.
Click to expand...
Click to collapse
Ok so first off thank you so much for taking the time to try and help, and forgive me for being needy.
In your post you mention following Imma Wake's video which I tried to do, but the very first step is a brick wall. The YouTube video which supposedly shows how to upgrade to the 5.0 Developer preview has been removed. It is no longer there, so that very crucial first step is one that I cannot take.
Next, in your post, you reference upgrading the Kindle HD6 using both the 5.0 Developer preview AND the 5.01 Developer preview which has me totally confused. I do not see any videos on Imma Wake you tube channel referencing the 5.01 Developer preview. The last thing I want to do is brick my brand new Kindle...
SO, once again, I am back here at square one, stuck. Any chance you can point me to the quick and easy method of upgrading to 5.0 Developer so I can get past that step? I have signed up on Amazon and the developer page indicates that my device will be upgraded within 48 hours, but I am sitting here with time on my hands today and really wanted to give this a shot today.
Thanks.
Hello Guys,
At first a little background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately, I applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
I am not responsible if anything goes wrong.
Ok, so let's get started:
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Windows: https://forum.xda-developers.com/showthread.php?t=2588979
Linux/Mac: http://rootmygalaxy.net/install-adb-and-fastboot-on-mac-or-linux/
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of your choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip not working anymore, official link:
http://developer.download.nvidia.com/mobile/shield/SHIELD_Family_WHQL_USB_driver_201801.zip
-As many of you are experiencing problems with my previously mentioned TWRP 2.8.7.3 version I am replacing the link with the official TWRP Shield Tablet Download Site. Just take the newest stable version: https://dl.twrp.me/shieldtablet/ (Put the file into the ADB+Fastboot Folder)
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder): Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "sudo" in front of it...)
Mac:
You also don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "./" in front of it...)
Flash Recovery
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installed, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
EDIT: 4.1 To enable the fastboot protocol, you must select "Fastboot mode" on the Tablet. After that type
Code:
fastboot devices
in order to check if fastboot is enabled.
5. Before you can do anything you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. Now you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-x.x.x-x-shieldtablet.img
6.2 Wait until it is finished then navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a custom rom
Custom Rom
If you want to be on the safe side you should consider wiping the /data partition (Troubleshoot section at the end of the Post)
1. You can access your tablet from your PC
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice.
2.1.1 Cyanogenmod 12.1 (Android 5.1.1) and BlissPop v4.0.3 https://www.androidfilehost.com/?w=files&flid=150249
2.1.2 Cyanogenmod 13.0 (Android 6.0) https://androidfilehost.com/?w=files&flid=27600&sort_by=date&sort_dir=DESC
2.1.3 Nvidia Shield Tablet Resurrection ROM (Android 6.x) https://androidfilehost.com/?w=files&flid=60681&sort_by=date&sort_dir=DESC
2.1.4 BlissPop
2.2 Download Google Apps (Gapps) (ARM Device)
2.2.1 Android 5.1 http://opengapps.org/?api=5.1&variant=stock
2.2.2 Android 6.0 http://opengapps.org/?api=6.0&variant=nano
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
3.1 Now go to Wipe. For a dirty flash you will only need to wipe the Dalvik and Cache for a full wipe select Dalvik, System, Data, Cache
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips and select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
For Android 7.0 (Nougat) the SuperSU r4 2.78 version is confirmed working.
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installed
Xposed Framework
Download the Xposed Framework Zip file, take the newest version:
(The Shield Quad Core has a 32 bit arm architecture, so you need the framework for arm)
SDK21 for Android 5.0: http://dl-xda.xposed.info/framework/sdk21/arm/
SDK22 for Android 5.1: http://dl-xda.xposed.info/framework/sdk22/arm/
SDK23 for Android 6.0: http://dl-xda.xposed.info/framework/sdk23/arm/
and the apk: https://forum.xda-developers.com/attachment.php?attachmentid=3921508&d=1477916609
and move them to you Tablet.
Developer Thread (for the uninstaller): https://forum.xda-developers.com/showthread.php?t=3034811
Go to Recovery with Root
1. Now that you have root you don't need you PC anymore. Go to the Play store and download Quick Boot
2. Open Quick Boot and klick on Recovery
3. Allow Root rights and the Tablet should boot into recovery
Go to Recovery without Root
1. Shut down your Tablet
2. Press and hold the Vol down button and the Power button until the Bootloader screen appears
3. Navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
Install Xposed Framework
1. In the TWRP Recovery (Optionally you can make a Backup) select Install and choose the xposed-v80-sdk22-arm.zip file
2. When you get an Error let me know
3. Now Restart you Tablet and install the .apk file normally
4. In the App Press Framework and now there should be a green writing saying: Xposed Framework version 80 is active
5. Here is a list of very useful programs for the Xposed Framework: http://forum.xda-developers.com/android/general/best-xposed-modules-android-t3103027
Please Leave a post if you are getting errors or something isn't clearly explained! And if I could help you, consider giving me a Thanks
Troubleshoot
If you are stuck in a Bootloop:
Without data loss(e.g. when you installed Xposed framework zip and its stuck in a bootloop)
1. flash the stock rom boot image BUT ONLY IF YOU DONT USE A CUSTOM ROM (it will probably loose root). go to https://developer.nvidia.com/gameworksdownload#?search=SHIELD Tablet K1&tx=$additional,shield and download the latest NVIDIA SHIELD Tablet K1 Recovery OS Image
2. Unpack the zip file and flash it to your Tablet
Code:
fastboot flash boot boot.img
If something went wrong while flashing a custom rom (after that you will need to flash the custom/stock rom again)
wipe the /data partition. It could be encrypted from the previous rom. Be aware that you need to reinstall the rom, therefore loose all your data. Troubleshot guide by agentbob123
-Toby
Credits:
@xsquid mac support
@agentbob123 suggestion to mention to wipe the /data partition as a solution for being stuck in a bootloop
@champs777 suggested the newest TWRP
@grävling mentioned importance of waiting until the recovery flash is finished
Toby9 said:
Hello Guys,
At first a litte background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately i applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
Ok, so let's get started:
I am not responsible if anything goes wrong.
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of you choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder):
Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a sudo in front of it...)
Mac:
2016/02/16 Please leave a post if you how to do this
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installen, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
5. Before you can do anyting you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. No you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-2.8.7.3-shieldtablet.img
6.2 Wait until it is finished then move with the volume buttons through the Menu on your Tablet an choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a cutom rom
Custom Rom
1. You can access your tablet on your pc
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice. I decided to use Cyanogenmod 12.1 (Android 5.1.1) http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043
2.2 Download Google Apps (Gapps) (ARM Device) http://opengapps.org/?api=5.1&variant=stock
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips an select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installen
Please Leave a post if you are getting errors or someting isn't clearly explaned!
-Toby
Click to expand...
Click to collapse
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock
xsquid said:
On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock
Click to expand...
Click to collapse
Thank you I added this in guide
nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
Try other TWRP versions like 2.8.7.0 or 2.8.7.1 i think the 3.0.0.0 is for Andoid 6.0 devices so if you are currently in the newest version of the Android OS try this one out
The 3.0 versionof TWRP was unstabel on my device so you should flash it wipe the storage and flash one of the older ones
nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
fards said:
Try deleting recoveryonboot.p in /system
Click to expand...
Click to collapse
Credit to fards.
xsquid said:
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
Credit to fards.
Click to expand...
Click to collapse
How can I remove this file without root ?
SonicDBZFan07 said:
How can I remove this file without root ?
Click to expand...
Click to collapse
Try your normal command line for flashing recovery except change flash to boot. It doesn't flash it, just boots to it.
In other words, if you are using:
1. Fastboot Flash recovery recoveryname.img
Do instead:
2. Fastboot boot recovery recoveryname.img
While in recovery (make sure the supersu zip is on the sd card or wherever you normally flash files from first) flash supersu. You should now be rooted but without a recovery.
Go then to delete the file and then reboot, flash the recovery as normal (#1), reboot and then it should be good to go. It was for me.
rooted device no need to unlock bootloader it will unlock for ittself
just go to playstore and dowload twrp manager
choose the name of your device
and choose one of the two versions available
for shield tablet the version 3.0.0.0 doesnt work well it spilts the screen but wthe other version Works great
the link is twrpmanager on play.google
this way you dont need to connect your tablet to your pc
Great work!
Thank you for the awesome guide. Besides deleting the TegraOTA apk, is there any other app/service that I should disable to prevent OTA updates?
Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.
diji1 said:
Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.
Click to expand...
Click to collapse
I'm sorry that you had that problem but this guide is a general guide and not an screw nvidia (besides they are awesom giving us a really good tablet for 200 Buck, but jea?) guide. TWRP v3.0.0 has his bugs so generally when you have finished deleting the stock rom you should flash TWRP 2.8.7.3 works the most stabel.
Trafalgar Square said:
Great work!
Click to expand...
Click to collapse
Thanks, i appreciate that
Add TWRP to M image (Shield 1.1)
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks
psychic99 said:
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks
Click to expand...
Click to collapse
After you flash twrp reboot to recovery. I may be wrong, but I think the stock ROM overwrites the custom recovery at reboot. If you reboot to twrp first after flash, twrp will disable this.
Sent from my SHIELD Tablet K1 using Tapatalk
Rooting
Hi everyone,
Yesterday got my new Nvidia Shield Tegra K1 and upon using it I noticed it's a great tablet for it's price range and will do my job easier while flying my Phantom 4. To be honest it's seems very stable and solid but was thinking about rooting it. I have some questions regarding the process wince I haven't rooted anything since my HTC Fire, log time ago that was. What are the benefits of rooting this device ? Will I still be able to update the Shield with its official updates ? Will I be able to roll back to an unrooted tablet should I need too ? I wasn't planning on flashing a custom rom but if I'll do what are the pros and cons of doing so ? I know that maybe searching this forum I would find all the answers needed but since there is so much information and threads I'm lost as from were to start from.
Would be nice to guide me about how to properly root my device with all the necessary links. My tab is running on Android 6.0.
I thank you so much guys for the hard work you all do in providing such information. I know it takes a lot of time and patience.
I just got a Shield K1. I like it a lot but I wanted to root it. Then I saw how confusing it is to distinguish between it and the previous model. My guess is whatever is out there that says Shield Tablet means the old one not the K1. I also updated mine to MM cause I'm using and 128GB micro sd card for internal storage. I guess I'll just have to wait until more support comes out for this tablet such as a stable TWRP 3.0 Recovery and the ability to gain root access and custom ROMs like CM 13.
do you recommed to install all OTAs before install custom recovery and custom roms or is it better to install twrp-2.8.7.1 out of the box and then go for the custom stuff ?
I would install all updates to get the latest bootloader. Do not install twrp 2.8.7.1. Install the official 3.0.x from the official site.
Edit - just an FYI for complete transparency. I have moved from the Pixel 3a XL to the Pixel 6. I no longer own my Pixel 3a XL. While I've been told (thanks @AndDiSa) that the root process for Android 12 is the same as it historically has been, I no longer can test things myself. (The root process for the Pixel 6 is different and more complicated than this phone). If you run into any problems or issues, please post in this thread and someone will hopefully be able to answer them.
I'm assuming you understand how to use ADB on your computer. If you need assistance with installing or using ADB, please refer to this XDA article for more information. However, here are some common issues that people have with ADB if it doesn't work initially for you. 1) Check the Android System Notification that appears in your phone's notifications after you plug in your USB cord. Your phone probably defaults to "No data transfer" and you need to change it to "file transfer" to allow the phone to connect. 2) Make sure you have USB debugging turned on in the Settings/System (advanced)/Developer options. 3) If this is your first time using this phone/computer combination, you will have to accept the connection when it pops up on your phone.
You also need an unlocked bootloader to complete these steps. If you need assistance with unlocking your bootloader, here is decent set of instructions. Those instructions are based on the Pixel 3 phone, but the steps are the same for the 3a devices.
Here are the official Magisk installation instructions. I will walk through them to help everyone understand them. Please note that while TWRP does work with Android 9 (Pie), it does not work currently with Android 10 or 11. If you are still on Pie for some reason you can choose either installation option, but if you have moved to a later Android version, you must use the "Boot Image Patching" installation method.
Custom Recovery Installation Method - (available for Android Version 9/Pie only because TWRP does not work currently with the Android 10/11)
This is the easier installation method IMHO, but it does require using TWRP. If you don't know how to get TWRP for the Pixel 3a, please refer to the official TWRP for Pixel 3a thread
Step 1 - Download and install the Magisk manager app on your phone. (link to the latest stable version can be found here).
Step 2 - Using the Magisk manager app, select "Install Magisk" and select the "Download Zip Only" option. This simply downloads the installation zip to your phone's download folder. It doesn't attempt to install anything.
Step 3 - Boot into TWRP - (because TWRP is not permanent on the stock Pie OS, we must follow these instructions each time we want to boot into TWRP).
Step 3a - Download the latest TWRP image for the 3a to your computer (not your phone) from the official TWRP for 3a thread.Step 3b - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".Step 3c - Boot your phone into the bootloader (type the command "adb reboot bootloader").Step 3d - Boot into TWRP using this command, "fastboot boot twrp-3.x.x-x.img" (where "twrp-3.x.x-x.img" = whatever the name of the TWRP download is). Please note you are not using the "flash" command as we are not permanently installing TWRP.Step 4 - Once the device boots into TWRP, select "Install" and then find the Magisk.zip download from step 2. Swipe to confirm the installation
Step 5 - After the installation is complete, simply reboot system.
Step 6 - Enjoy your rooted phone and install any Magisk modules that appeal to you
Step 7 - Be sure to turn off the "Automatic System Updates" setting found in Developer settings (Settings /System (advanced) /Developer Options). This will prevent the phone from automatically installing an OTA update and instead allow you to follow the steps listed under the "Taking an OTA Update" section below
The Boot Image Patching Installation method - (the only method currently available under Android 10, 11 or 12, but it also works with Pie).
Use this method if you are on Android 10 or 11 or you are on Android 9/Pie but you don't want to or can't use TWRP.
Step 1 - Obtain a stock boot.img file for the OS version/update that you are currently on. The easiest method is probably to download the applicable full stock image directly from Google. Unzip the files and unzip the second folder and you should find the boot.img file inside.
Step 2 - Copy the stock boot.img file to your phone's storage - probably to /sdcard or to /sdcard/downloads
Step 3 - Download and install the Magisk manager app on your phone. (link to the latest version can be found here). If you are early in the Android 12 cycle, you probably need to use a Canary build of Magisk.
Step 4 - Using the Magisk manager app, press "Install --> Install --> Select and Patch a File" - select the stock boot.img file that you put on your phone in step 2.
Step 5 - Magisk will modify the stock boot.img file and create a patched boot image file. It will save this modified file at "sdcard/Download/magisk_patched.img"
Step 6 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 7 - Copy the patched boot image from your device to your PC and the adb folder. If you can’t find the file on your phone via MTP or Windows Explorer, you can pull the file by typing the command "adb pull /sdcard/Download/magisk_patched.img" - Please note, I would suggest double checking the "file modified date" prior to moving the file. Be sure to only move the file if it was last modified on the date you are doing this. I've had a strange situation before where the newly modified file didn't immediately show up and the file showed a modified date of the previous month. If you flash an old version, your phone will bootloop.
Step 8 - Boot your phone into the bootloader (type the command "adb reboot bootloader").
Step 9 - Flash the patched boot image to your device using this command, "fastboot flash boot magisk_patched.img"
Step 10 - Reboot (using command "fastboot reboot").
Step 11 - Enjoy your rooted phone and install any Magisk modules that appeal to you
Step 12 - Be sure to turn off the "Automatic System Updates" setting found in Developer settings (Settings /System (advanced) /Developer Options). This will prevent the phone from automatically installing an OTA update and instead allow you to follow the steps listed next.......
Taking an OTA update in the future (if you used this method to install Magisk).
Taking OTA updates is very easy with the Pixel devices because of their A/B partition system. It allows us to uninstall Magisk, take the OTA update, and reinstall Magisk - all from the phone and all without rebooting during the process. Here are the offical Magisk OTA instructions. I will go through the steps to help explain them.
Step 1 - In the Magisk manager app: Click “Uninstall” then “restore images”. DO NOT REBOOT or press the reboot button.
Step 2 - Download and install OTA (in your phone's Settings/System/System Update). DO NOT REBOOT or press the reboot button.
Step 3 - Open the Magisk manager app and click “Install” next to Magisk (usually it says "Magisk is up to date") then “Install to second/inactive slot (After OTA)”
Step 4 - Press the Reboot button in Magisk.
That should be all it takes to install an OTA and keep root.
Please note, we are getting reports that users are getting notifications that an OTA update has been installed even when they have "Automatic Updates" turned off. If this happens to you, don't reboot the phone which is suppose to be the final step in the update process. Instead, follow the above instructions on taking an OTA update, but start in step 3. In other words, you shouldn't have to uninstall Magisk because the update has already been installed. All you need to do is install Magisk to the "second/inactive slot (After OTA)”. After completing that step, you can reboot your phone to complete the update process. Be sure to post your experiences in this thread to let us know if this process works or not.
Just remember that many custom parts (like kernels and Magisk modules) may need to be updated to any new OTA version. Please be sure to check out the forums for each custom kernel or module that you may want to install to ensure it has been updated to the lastest OS version. Don't assume anything or you may find yourself in a bootloop.
If you find yourself in a bootloop after upgrading an already rooted phone
If you find yourself in a bootloop after updating to a new OS version and flashing the magisk_modified boot.img again, it is likely due to an installed Magisk module not being compatible with the new update. To uninstall all Magisk modules to fix the bootloop, follow these steps:
Step 1 - Connect your phone to the computer you use ADB on.
Step 2 - In ADB type the command "adb wait-for-device shell magisk --remove-modules"
Step 3 - Start your phone again or wait for it to go through another bootloop cycle.
Step 4 - as soon as ADB is available (which occurs even during a bootloop) the command will activate, the modules will be removed, and the phone will reboot.
If the normal OTA method isn't working - sideload the OTA update
Taking an OTA update should be as easy as the above instructions. However there is another option available to install an OTA update called sideloading. Sometimes the update doesn't appear on the phone in a timely manner and you may want to manually install the update. Other times the OTA update seems to fail for some reason. In the end, you may decide to sideload the OTA instead of trying get it via the update feature on the phone. Surprisingly, it's actually faster to install the update via sideloading than it will be to take the OTA normally. I'll walk through the sideloading steps.....
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on a couple Android 10 images, but most do not require this step.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (See note below about initial boot times).
Step 9 - To obtain root again, please use one of the two root methods listed above
Please note, while the initial boot is usually pretty quick, it can take longer. I've occasionally seen the process take upwards of 20 minutes and longer. I think part of the reason it can take so long is that sometimes it optimizes the apps during this boot process. The more apps you have, the longer the process may take. When you take an regular OTA update, the phone will change to a screen where is specifically tells you it is optimizing the apps and counts up as the apps are optimized to give you status updates. When you use the side-load method, it all happens with just the regular boot animation running and without any status updates. Because of this, it is easy to assume something has gone wrong with the boot process while in fact the phone is working through the process normally. If it isn't boot looping (showing the initial power screen before moving back to the boot animation), everything is fine and you just need be patient and let the phone complete the process.
My rant about using these "Pre-patched Boot image" files
I started this thread during a period of time where there was a another thread on this forum started by pbanj that showed users how to root their phone by using some pre-patched boot image files. This method is not the generally accepted method and while it works, there are major shortcomings with it (see explanation below). Because it was the only root thread available at the time and he only showed the "pre-patched boot image" method, many people blindly followed his directions only to be confused when it came time to update the software on their phones. I wrote this thread in an effort to show people the official Magisk installation method. Pbanj has since updated his thread and it now includes the preferred method as well. With his edits, the two threads are sharing the same information now, although Pbanj thread still offers people the "pre-patched boot image" method (which I don't recommend people using).
EDIT - Yet another thread pushing a pre-patched root method has been started. It suffers the same issues as listed below.
Shortcomings with using the "pre-patched boot image" method.
As I already mentioned, there is a huge shortcoming with using the "pre-patched boot image" method described in the other root thread. Because he provides a pre-patched boot.img file, you skip some normal installation steps. In the end you have the exact same patched file (which is why his method works), but you cripple the system when it comes to taking any future OTA. That's because the first step in taking an OTA update is having Magisk reflash the stock boot.img effectively uninstalling itself. This step fails if you used his pre-patched boot image method because you skip the step where Magisk creates the backup of the stock boot.img that it needs to uninstall itself.
I already used the "pre-patched boot image" method to gain root. What can I do?
First, let me clarify and say that there is nothing wrong with your phone or root privileges. Your phone will work exactly as expected and root and Magisk will work exactly as expected. That being said, in the near future you will want to update your phone to the latest Android update and this is where the "pre-patched boot image" method is much more cumbersome. The best option is to simply undo his root method and re-root using the method described above. To do this, flash the correct stock boot.img file to your boot partition and then follow the steps above to reinstall Magisk. Jbanj has confirmed this method will work. The other option is just wait until you need to take an update and then sideload the OTA update following the instructions above. This will remove root and you can then follow one of the two methods to obtain root as outlined in this thread.
Notes
- Please be sure you are on the latest adb and drivers which can be found here.
- You do not need to keep the stock boot.img file (from step 2 of the Boot Image Patching method) on your phone after completing these steps. Magisk saves the stock boot.img backup at /root/data in a file with the name "stock_boot_XXXXXXXXXXXX.img.gz"
Thanks to.......
@ZVNexus for getting TWRP working on the 3a and 3a XL phones
@topjohnwu for making Magisk what it is today
Made it to step 7/8, went to reboot, and entered bootloop. Not sure exactly what happened, gonna fix this and give it another go.
EDIT: Should I be flashing in fastboot or recovery mode?
EDIT 2: Working! Thanks!
You know there are more ways to skin a cat, right? This is another method to acquire root. I don't think you need to bash the work that pbanj has done. He provides modified boot.img and also offers help on getting it working. I think acting like your method is the only acceptable way to gain root is extremely pompous and arrogant.
Sent from my Pixel 3a using Tapatalk
jmtjr278 said:
You know there are more ways to skin a cat, right? This is another method to acquire root. I don't think you need to bash the work that pbanj has done. He provides modified boot.img and also offers help on getting it working. I think acting like your method is the only acceptable way to gain root is extremely pompous and arrogant.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
I don't think that this method is the only way to get root, nor is this "my method". It is however the method spelled out by the Magisk developers and it is the only method that uses Magisk strengths when trying to take an OTA update.. I'll simply leave it at that......
sic0048 said:
I don't think that this method is the only way to get root, nor is this "my method". It is however the method spelled out by the Magisk developers and it is the only method that uses Magisk strengths when trying to take an OTA update.. I'll simply leave it at that......
Click to expand...
Click to collapse
Sure. It's the way I do it also. But show some class and don't call out other, helpful members in this fashion and crap all over what they do. I have seen your posts and know your a helpful members also, let's respect each other and be classy.
Sent from my Pixel 3a using Tapatalk
@sic0048
Thank you. I got to admit it was pretty tense for a while. Thanks to you I made it. Had to do a sideload, had to do some stupid things but I made it. Now, I got through all the steps and I have two items; Having done this transition can I now do the magisk-uninstall-restore images for all future OTAs and is step 9 performing the magisk install process a second time?
Bankuu said:
Made it to step 7/8, went to reboot, and entered bootloop. Not sure exactly what happened, gonna fix this and give it another go.
EDIT: Should I be flashing in fastboot or recovery mode?
EDIT 2: Working! Thanks!
Click to expand...
Click to collapse
I've edited the steps and added a few more going into greater detail to try and make it even clearer for users. Let me know if you have any suggestions.
alliance1975 said:
@sic0048
Thank you. I got to admit it was pretty tense for a while. Thanks to you I made it. Had to do a sideload, had to do some stupid things but I made it. Now, I got through all the steps and I have two items; Having done this transition can I now do the magisk-uninstall-restore images for all future OTAs and is step 9 performing the magisk install process a second time?
Click to expand...
Click to collapse
You should be able to use the normal Magisk OTA update instructions for future updates.
I've updated the thread and I think the "step 9" you listed isn't the same anymore, but I think I understand your question. Actually I think my original instructions were inaccurate as far as that step. I've always gone back into Magisk after flashing the modified boot.img and I thought I hit install to install the Magisk framework (if that is the correct term). But after reading some other guides, I think my memory is incorrect and you don't really have to install anything after the flashing portion of the steps.
Once you reboot after flashing, that should be all you have to do. I'll uninstall Magisk here in a while and walk through the steps myself to ensure this is correct howeve.
The OP should be made a sticky.
Cool guide. Can the method be applied to Q beta 4 ?
MPAI said:
Cool guide. Can the method be applied to Q beta 4 ?
Click to expand...
Click to collapse
No root for Android q on our devices yet afaik.
Sent from my Pixel 3a using Tapatalk
@sic0048
Should we keep the stock boot image copied to the phone storage in step 2? Is this where Magisk will look for it to do an image restore?
alliance1975 said:
@sic0048
Should we keep the stock boot image copied to the phone storage in step 2? Is this where Magisk will look for it to do an image restore?
Click to expand...
Click to collapse
You do not need to keep the stock boot image that was copied over in step 2. Magisk saves the backup of the boot.img at /root/data. It will have the name "stock_boot_XXXXXXXXXXXXXXXXXXX.img.gz"
sic0048 said:
You do not need to keep the stock boot image that was copied over in step 2. Magisk saves the backup of the boot.img at /root/data. It will have the name "stock_boot_XXXXXXXXXXXXXXXXXXX.img.gz"
Click to expand...
Click to collapse
Thanks sic0048. You put up with my dumb questions and helped make my pixel 3a a great phone.
Respect.
Edited - now that jbanj has confirmed we can simply flash the stock boot.img file to the boot partition and start over, the post I originally had here is pointless.
Alliance's question got me to thinking.....
Since Magisk saves the stock boot.img backup at /root/data in a file named "stock_boot_XXXXXXXXXXXX.img.gz" I wonder if we can't simply share a backup file with someone that used jbanj "modified boot image" method and have them copy it to that location. I suspect Magisk will then allow the normal OTA update prceedures to work.
I can share the backup file that I have, but it is for the 3a XL model, Android version 9 (Pie) and the June 5, 2019 security update. That means it will be next month before there will be another OTA update pushed out.
If someone is still on the OEM March update and rooted using the normal directions and is willing to share their backup file, we might be able to try it sooner.
Unfortunately I don't know if Magisk modifies the backup to be some sort of unique file. I doubt it, but I don't know for sure. Of course worse case scenario is that it doesn't work and the person has to flash the OTA manually - which is no different than what they would have to do anyway. So there really isn't much risk in trying this.
MPAI said:
Cool guide. Can the method be applied to Q beta 4 ?
Click to expand...
Click to collapse
Wondering the same thing. I know the OTA is rolling out again today IIRC. But I also read something about root not being available on Q yet, so not sure how that would work out.
Bankuu said:
Wondering the same thing. I know the OTA is rolling out again today IIRC. But I also read something about root not being available on Q yet, so not sure how that would work out.
Click to expand...
Click to collapse
Google has changed the file structure in the Q beta 4 release and root is not possible at this time. This is true across all devices (not just the Pixel 3a). I know John Wu (the Magisk developer) is working on a solution and I would expect to see results before Android 10 is released, but only time will tell.
However, at this time there is no root on the Q beta 4. If you need root, you will have to stick to Pie for now.
@sic0048 I've updated my thread
I'm getting weird behavior here that I've been able to replicate.
Bottom line, if you use the Magisk patch method, upon flashing that boot image, your phone will auto-play music every single time it boots up. That's incredibly annoying.
Uninstall and go back to stock boot.img, and it goes away. Flash again, it's right back.
Guess I'll just wait for TWRP instead of going through those steps again, lol.