Related
1. Place the superuser.zip file attached at the end of the post on your sd card.
2. Flash recovery in bootloader with "fastboot flash recovery <filename>.img". I recommend CWM 5.0.2.3 found in this thread - http://forum.xda-developers.com/showthread.php?t=988686&highlight=recovery
3. Go to recovery, in "mounts and storage" select "mount system" and then flash su-install.zip (EDIT : Mounting system not necessary, the script does it automatically while flashing the zip, but just in case)
4. Fix Permissions and reboot system.
5. Use any root explorer (i recommend ROM Toolbox, free in market) and go to /etc and either rename "installrecovery.sh" to "installrecovery.sh.old" or just delete it (its not needed).
6. There it is - Rooted ICS with a recovery that sticks.
EDIT -- IF, by any chance, after following the above steps, you find that you're stuck without a recovery (android exclamation screen), just flash a recovery via fastboot and you'll be fine. This time the recovery WILL stick. I think its something to do with the su-install.zip. I dont know for sure because I found it off the internet, its not mine.
Also, I did the superuser market update and I DID NOT lose root. I have an I9020T. So others with the same can safely update, imo.
Thanks to ab.grafix for being a part of the team.
IMPORTANT -- The su-install.zip posted previously is NOT mine. I didnt know who made it but just found out. All credit to dzo binary and Chamb'. I just made a guide coz it worked for me and I thought it might help others too.
Tested on I9020T and I9023
Don't forget to click on that thanks button if this helped.
UPDATE -- Superuser was updated by ChainsDD to support ICS 4.0.3. Thank you ChainsDD! Updated zip is now attached.
So now that we have root we need a overclocked kernel...
Sent from my Nexus S using XDA App
works great but very old cwm
Worked as described. Thanks !
Old cwm? Wich version? Is it possible to flash the latest one with rom manager?
So I am on ICS alpha13.
I9023
- wipe everything and Flash Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader via clockworkmod
- Reboot in stock recovery and flash stock ICS
- Boot in ICS enable debug mode
- Run the bat follow instruction?
Is it ok?
Thanks
Hi will it work on the rogers i9023a? Can someone tell me which stock ICS to flash?
Thanks
Thanks, it worked and nothing was wiped since I was already unlocked. With apps that require root you no longer get asked for root permission nor do they show in app list in superuser but it seems to have root for now
For the guys using linux (like me ) , just download the archive in the first post , retrieve from there 2 files: root.zip and recovery.img and use them with your current ADB setup.
HOW-TO:
Prerequisites: you have installed Android SDK, fastboot and you have set-up correctly the udev (ubuntu).
1. Place the above mentioned 2 files in the working directory
2. reboot in bootloader mode (vol-up + power)
3. connect USB cable
4. run "./fastboot-linux-i386 flash recovery recovery.img"
5. reboot bootloader
6. reboot recovery
7. mounts and storage -> usb mass storage
8. copy root.zip in the phone storage
9. go back -> install zip from sd card -> root.zip
DONE !
I just tested and is working fine.
If there are newbies out there trying to understand the nonsense I wrote, try following the rooting guide for Gingerbread and just use the 2 files I mentioned in this post instead of the ones in the archive for gingerbread.
when in BL i dont have Unlock option :|
Thanks for your effort.
But I'm curious about the flashable zip file.
What's the difference of the zip file between the orignal superuser ?
And did the recovery do some magic which CWM can't do?
After reading the script , I just see the zip is important ,maybe the recovery is doing some magic too.
I'll just flash the zip and see what happen.
ro_explorer said:
For the guys using linux (like me ) , just download the archive in the first post , retrieve from there 2 files: root.zip and recovery.img and use them with your current ADB setup.
HOW-TO:
Prerequisites: you have installed Android SDK, fastboot and you have set-up correctly the udev (ubuntu).
1. Place the above mentioned 2 files in the working directory
2. reboot in bootloader mode (vol-up + power)
3. connect USB cable
4. run "./fastboot-linux-i386 flash recovery recovery.img"
5. reboot bootloader
6. reboot recovery
7. mounts and storage -> usb mass storage
8. copy root.zip in the phone storage
9. go back -> install zip from sd card -> root.zip
DONE !
I just tested and is working fine.
If there are newbies out there trying to understand the nonsense I wrote, try following the rooting guide for Gingerbread and just use the 2 files I mentioned in this post instead of the ones in the archive for gingerbread.
Click to expand...
Click to collapse
In fact, you can use any recovery image you want, including the latest clockwork for example. I used TWRP to do this and it worked just fine. On linux, just flashed root.zip.
I've done it, thanks a lot. I've also replaced the recovery.img file with the last cmw and all went well.
Now the rom doesn't show the root permission request toast but it works however.
I'd ask if its possible to manually update the superuser.apk or its better to mantain this one?
sakisds said:
In fact, you can use any recovery image you want, including the latest clockwork for example. I used TWRP to do this and it worked just fine. On linux, just flashed root.zip.
Click to expand...
Click to collapse
Great .. I'll do that because I miss my "old" cwm
EDIT: it worked, thanks!
thanks, working here on 9023. warning for other users - do not update superuser from the app itself, or it'll stop working. at least it did for me, when i updated it to 3.0.3
confirmed working I9020a...
[INFO] Working root for ICS 4.0.3
Credits to Chamb'.
Flash via CWM and you're done.
Tested working for ICS 4.0.3 I9020T.
Enjoy!
Source: http://forum.xda-developers.com/showpost.php?p=20394635&postcount=4
It seems to have worked like a charm, thank you!
I was even able to flash the latest CWM Recovery using ROM Manager
can I flash stock 2.3.6 with cwm?
Im on ics alpha13
Anyone got a download link for the stock 2.3.6?
bratfink said:
Anyone got a download link for the stock 2.3.6?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1063664
Dear Asus Transformer TF300T users,
Asus released the 4.2 Jellybean update. Since there are some people with fastboot problems or don't know how to install recovery or root, here is a guide which will let you:
- Install recovery and give you root acces on latest 4.2 update
- [Optional] Remove bloatware from your tablet
== Part 1 - Preparation ==
Before we start with this guide I can tell you guys it will work for:
- All 4.1 firmwares
- All 4.2 firmwares
So what do you need to do as a preparation of rooting and installing recovery:
1. Upgrade your tablet to the desired firmware: 4.1 or 4.2
2. Be sure the correct drivers for your tablet are installed!!
3. Download the updated rooting toolkit: Updated Motochopper rooting toolkit
4. Download TWRP for your firmware version:
- 4.1: TWRP 2.5.0.0 for Jellyeban 4.1
- 4.2: TWRP 2.5.0.0 for Jellybean 4.2
5. Rename the downloaded TWRP blob file to twrp.blob and copy it to the root of your sdcard
5. Extract the rooting toolkit to a place you like.
== Part 2 - Rooting ==
1. Open up the folder where you placed the rooting toolkit.
2. Open the run file and follow the instructions
After installation the tablet should reboot and you should be rooted.
== Part 3 - Latest TWRP recovery ==
Be sure you have twrp.blob on your removable sdcard or it won't work!
1. Open up CMD in the folder were you have your adb files (Shift + Right Mouse Click => Open CMD here) and use the following commands to install TWRP:
adb shell
su
dd if=/Removable/MicroSD/twrp.blob of=/dev/block/mmcblk0p4
2. After this you need to reboot your tablet to let it install the recovery
MOD EDIT: This Method ONLY applies to JB 4.1. Do Not Use on JB 4.2
Dear Asus Transformer TF300T users,
Asus released the Jellybean update in the United States. Here is a guide which will let you:
- Prepare your tablet for the Jellybean update
- Update your tablet to Jellybean software
- Install recovery and give you root acces
- [Optional] Remove bloatware from your tablet
- [Optional] Speed up your tablet using tweaks
== Part 1 - Prepare the tablet ==
First we need to install the 9.4.3.30 US update to be able to upgrade to the Jellybean software, then we will do the actual upgrade to Jellybean.
1) Download the US 9.4.4.3.30 update: Asus support site
2) Put the file on your tablets internal storage
3) Got to recovery and make a backup
4) In recovery do to a factory reset and wipe dalvik cache
- TWRP recovery: Wipe => Dalvik Cache and Wipe => Factory reset
- CWM recovery: Factory reset and Advanced => Wipe Dalvik Cache
5) Flash the US_epad-user-9.4.3.30.zip file
Don't install a custom recovery after doing this step. The Jellybean update will only be automatically launched with stock recovery
6) Reboot into your tablet and enable "USB-debugging" and "Unknown Sources" in settings
7) Connect your tablet to your pc and download this file: Automated Rooting Toolkit
8) Extract the rooting toolkit and follow the instructions to root your tablet.
9) Once you finished the rooting process you are ready to continue to the upgrade process
== Part 2 - Upgrade to Jellybean ==
This will upgrade your tablet to Jellybean (Android 4.1.1)
1) Download the necessary files:
- dlpkgfile: Jellybean OTA update Rename this file to dlpkgfile
- command: command.zip (Extract this zip before copying to your tablet)
2) Copy both files to your MicroSD card or internal storage
3) Open root explorer or another file explorer with root acces
4) Copy dlpkgfile to /cache folder and the file command to /cache/recovery
5) Now you need to reboot your tablet, this will start the installation of the Jellybean update
6) Wait untill the update is finished and now you have Jellybean on your tablet
== Part 3 - Install recovery and rooting ==
Let's start with installing the recovery
1) Download these 2 files:
- Jellybean recovery with fastboot files: Fastboot files + JB recovery
- Root files: Root Files
- You can also download the new CWM Touch recovery if you don't like TWRP: CWM Touch recovery thread
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
- TWRP: fastboot -i 0x0b05 flash recovery tf300t-jb.blob
- CWM: fastboot -i 0x0b05 flash recovery CWM-Touch.blob
6) A blue bar will appear and the recovery will be installed, when the blue bar is filled press volume up + power button to reboot into the tablet.
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
== credits ==
- eyeballer for TWRP recovery
- untermensch for CWM recovery
- sparkym3 for his automated rooting toolkit
- Redefined301 for his guide
== Part 4 - Remove the Bloatware ==
The bloatware that can be removed is listed here, I listed it in categories
== Live Wallpapers ==
Code:
Black Hole (wallpaper or live)[B][INDENT]- Galaxy4.apk
- Galaxy4.odex[/INDENT][/B]
Android Live Wallpapers[B][INDENT]- LiveWallpapers.apk
- LiveWallpapers.odex[/INDENT][/B]
Backgound Picker[B][INDENT]- LiveWallpapersPicker.apk
- LiveWallpapersPicker.odex[/INDENT][/B]
HoloSpiralWallpaper Wallpaper[B][INDENT]- HoloSpiralWallpaper.apk
- HoloSpiralWallpaper.odex[/INDENT] [/B]
Asus Water Live Wallpapers[B][INDENT]- MyWater.apk
- MyWater.odex
- MyWater2.apk
- MyWater2.odex[/INDENT][/B]
== Face Unlock Feature==
Code:
- All files in /system/vendor/pitpat
- /system/lib/libfacelock_jni.so
- Facelock.apk
== Widgets==
Code:
Battery widget[B][INDENT]- BatteryWidget.apk
- BatteryWidget.odex[/INDENT][/B]
Deskclock[B][INDENT]- DeskClock.apk
- DeskClock.odex[/INDENT][/B]
Email widget[B][INDENT]- EmailWidget.apk
- EmailWidget.odex[/INDENT][/B]
My Zine[B][INDENT]- MyZine.apk
- MyZine.odex[/INDENT][/B]
Weather[B][INDENT]- Weather.apk
- Weather.odex[/INDENT][/B]
== Google bloatware==
Code:
Books app[B][INDENT]- Books.apk[/INDENT][/B]
Google Chrome[B][INDENT]- Chrome.apk[/INDENT][/B]
Google Market Feedback[B][INDENT]- GoogleFeedback.apk[/INDENT][/B]
Google Maps & Streetview[B][INDENT]- GMS_Maps.apk
- Street.apk[/INDENT][/B]
Google Gallery[B][INDENT]- Galery2.apk
- Gallery2.odex[/INDENT][/B]
Google Plus[B][INDENT]- PlusOne.apk[/INDENT][/B]
Google Talk[B][INDENT]- Talk.apk[/INDENT][/B]
Google Search[B][INDENT]- QuickSearch.apk
- Velvet.apk[/INDENT][/B]
Google Video[B][INDENT]- Videos.apk[/INDENT][/B]
Youtube[B][INDENT]- Youtube.apk
- YoutubeSearch.apk
- YoutubeSearch.odex[/INDENT][/B]
== Asus & 3rd Party bloatware==
Code:
Asus reader[B][INDENT]- AsusReader.apk
- AsusReader.odex[/INDENT][/B]
Dictionary[B][INDENT]- Dictionary.apk
- Dictionary.odex[/INDENT][/B]
Facebook Poster[B][INDENT]- FacebookPoster.apk
- FacebookPoster.odex[/INDENT][/B]
Asus File Manager[B][INDENT]- FileManager2.apk
- FileManager2.odex[/INDENT][/B]
Asus PC Sync[B][INDENT]- FDHttpd30.apk
- PCSyncLauncher.apk
- PCSyncLauncher.odex[/INDENT][/B]
Kindle app[B][INDENT]- Kindle-OEM.apk[/INDENT][/B]
MMS/SMS app[B][INDENT]- MMS.apk
- MMS.odex[/INDENT][/B]
Asus My Cloud & My Net[B][INDENT]- MyCloud.apk
- MyCloud.odex
- MyNet.apk
- MyNet.odex[/INDENT][/B]
Netflix app[B][INDENT]- Netflix.apk[/INDENT][/B]
Sound Recorder[B][INDENT]- SoundRecorder.apk
- SoundRecorder.odex[/INDENT][/B]
Asus Vibe app[B][INDENT]- Vibe_CN.apk[/INDENT][/B]
Video Editor[B][INDENT]- VideoEditor.apk
- VideoEditor.odex[/INDENT][/B]
Maybe more to be added later
== Part 5 - Speed up the tablet ==
Tweaks will come here
Thanks.:fingers-crossed:
Added my own link to dlpkgfile (OTA update file)
I hope this helps a lot of people
There are a lot of threads here, but not one that's really easy to follow for people that don't know everything about adb and that stuff
is rooting ONLY for unlocked device?
neo_u said:
is rooting ONLY for unlocked device?
Click to expand...
Click to collapse
Well I'm not long into the Asus development I'm a Sony Xperia dev
I don't know if you can root with locked bootloader. If you can install the recovery with locked bootloader then you can also root
krabappel2548 said:
Well I'm not long into the Asus development I'm a Sony Xperia dev
I don't know if you can root with locked bootloader. If you can install the recovery with locked bootloader then you can also root
Click to expand...
Click to collapse
Yeah. I can try to install, but, can my TF become a brick?
krabappel2548 said:
1) Download the necessary files:
dlpkgfile: Jellybean OTA updatehttps://docs.google.com/file/d/0B6LWCm-r4bHtYjBkS29yeFVSN2c/edit
command: command.zip (Extract this zip before copying to your tablet)
Click to expand...
Click to collapse
First off, thanks for this!
Some questions.
Your link for the dlpkgfile currently seems to point to "GoogleDrive" and makes me login to mine and send a request to be able to download it, which I did. Not sure if you are aware of it working like that?
2nd and most importantly in my case:
I am currently running the Seanscreams Hydro ICS Rom and am considering going this or whatever path is necessary to upgrade to JB. Any tips or alternative suggestions to follow in a case such as mine since I'm not already coming from stock? Obviously I have unlocked and have root. Is there anyway to keep my current setup without having to wipe OR do I need to rely solely on TIBU in order to get back all my apps?
Thanks!
PS: Oh, one more question. Is there a current working recovery to allow for creating/saving a backup once on JB? The answer to this question may very well be my deciding factor on if to wait things out a bit longer or proceed to JB now.
neo_u said:
Yeah. I can try to install, but, can my TF become a brick?
Click to expand...
Click to collapse
If you think you'll brick your device, then it's best not to try it.
lazer9 said:
First off, thanks for this!
Some questions.
Your link for the dlpkgfile currently seems to point to "GoogleDrive" and makes me login to mine and send a request to be able to download it, which I did. Not sure if you are aware of it working like that?
2nd and most importantly in my case:
I am currently running the Seanscreams Hydro ICS Rom and am considering going this or whatever path is necessary to upgrade to JB. Any tips or alternative suggestions to follow in a case such as mine since I'm not already coming from stock? Obviously I have unlocked and have root. Is there anyway to keep my current setup without having to wipe OR do I need to rely solely on TIBU in order to get back all my apps?
Thanks!
PS: Oh, one more question. Is there a current working recovery to allow for creating/saving a backup once on JB? The answer to this question may very well be my deciding factor on if to wait things out a bit longer or proceed to JB now.
Click to expand...
Click to collapse
Oops, forgot to set the file as public Now everyone should be able to download it
There is a JB recovery it's TWRP recovery. It's in my tutorial in this part:
1) Download these 2 files:
Jellybean recovery with fastboot files: Fastboot files + JB recovery
Root files: Root Files
Click to expand...
Click to collapse
krabappel2548 said:
Oops, forgot to set the file as public Now everyone should be able to download it
There is a JB recovery it's TWRP recovery. It's in my tutorial in this part:
Click to expand...
Click to collapse
Thanks. I did get the GoogleDrive dl permission and started to dl the file. Unfortunately, it seems this is going to give me the same fits as some hosts such as goo, ect... from my work wifi as it seems to be hanging at 9% :silly:
I was just going to ask which recovery we are actually getting with your method and as per the "quoted" above, I see you mention it's TWRP. As to my understanding following some other threads, this still as of now doesn't allow for an actual "backup" - "restore". Is that correct?
lazer9 said:
Thanks. I did get the GoogleDrive dl permission and started to dl the file. Unfortunately, it seems this is going to give me the same fits as some hosts such as goo, ect... from my work wifi as it seems to be hanging at 9% :silly:
I was just going to ask which recovery we are actually getting with your method and as per the "quoted" above, I see you mention it's TWRP. As to my understanding following some other threads, this still as of now doesn't allow for an actual "backup" - "restore". Is that correct?
Click to expand...
Click to collapse
It surely does have an actual backup and restore. It's only slightly broken. It can't back up or restore /boot, but that can be fixed by flashing the ROM after restoring your backup.
I'm working on AROMA installer with working touch to remove bloatware
Does the downloaded dlpkgfile need its name changed when placed in /cache? When you download it, its a ridiculouslyLongName.bin ?
dlpkgfile is the file name. If you change this, you have to change the command.
The command says /cache/dlpkgfile . Ive changed the name several times. Im just trying to figure out why my update keeps crashing at 25%.
Where do you wipe the dalvik cache?
Sent from my ASUS Transformer Pad TF300T using xda premium
Tried the instructions at least 20 times and it won't work. Sure it's user error
Sent from my SGH-T989 using xda app-developers app
is this CWM recoery or TWRP ?
anyone know how to find out why the update is failing?
placed dlpkgfile into /cache/ and placed "command" file in /cache/recovery and the install failed.
pretty sure i "thawed" all my apps, and have the stock build.prop.....if i add apps to system/app will that cause a failed install? i just remembered as i typed this that i modded an app and placed it in system/app because it wasn't signed.
I haven't deciphered an answer for this question as of yet:
Does this work on an unlocked, rooted tablet running a custom ROM?
TIA
Update13, Oct 23, 2017: Everything still works with the latest 5.4.0.1, just grab the correct ROM file
Update12, Jul 23, 2016: Upgraded to FireOS 5.3.1, everything went smooth. It's not clear yet if 5.3.1 can be safely downgraded to 5.1.2 in order to get root. Stay put until we get some confirmation! It has been reported that the downgrade from 5.3.1 to 5.1.2 bricks the Fire HD!!! So downgrade to FireOS 4.5.3 instead, root, quickly turn off the WiFi, and then use this guide to go back to 5.3.1 (and do use 5.3.1 bootloaders!):
http://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
Update11, Apr 29, 2016: I installed the new 5.1.2 build from Mar 30, 2016 via the instructions below (using TWRP), and everything worked fine. This version is not rootable by Kingroot (yet). One good option (if you have this version now) is to sideload via the stock recovery the rootable 5.1.2 from Feb 26 https://kindle-fire-updates.s3.amaz...HBV/update-kindle-20.5.4.2_user_542168620.bin , and then run Kingroot. See Update10 for other tips on what to do.
Update10, Apr 8, 2016: According to the reports, the stock 5.1.2 (Feb 26, 2016 build) is rootable via Kingroot (update to 5.1.2 via the standard Amazon procedures, try Kingroot several times). Block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_ . Then you can install GAPPS as per these instructions : http://forum.xda-developers.com/showpost.php?p=65405511&postcount=268 Note that you will still benefit if you follow this guide: install TWRP, and reinstall 5.1.2 via the steps below and get all the Android goodies loaded at once (including Xposed) on an entirely clean /system partition with no Kingroot files.
Update9, Mar 21, 2016: The instructions below are updated for 5.1.2 . Kingroot does not work under 5.1.2, use adb sideload to 4.5.3 to get root! It seems that 5.1.2 has a bug where /sdcard is not visible for root (the issue seems to be this newer SuperSu version, not FireOS 5.1.2 ... I went back to SuperSu 2.46, and now it works as before). To be on the safe side, I modified scripts in post #2 to work with the newer SuperSu as well (but I don't recommend this newer SuperSu version ...) . According to a report, 5.1.1 bootloaders can be run after 5.1.2 without bricking. Regardless, here, all the bootloaders will be kept as 5.1.1 just to be sure
Update7, Feb 13, 2016: Instructions for the latest 5.4.1 update file (FireOS 5.1.1 -Bellini - with "blue shade") - Note that the instructions can be confusing, don't rush if you are not sure what you are doing (and especially if your Amazon warranty already expired) !!!
Update6: Since early Oct, there is a new evil (!!!) update named here as 5.2.2u2 (which bricked a few Fires), but thankfully the update glitches has been worked out!!! Back to business !!! Observe that once you booted 5.2.2u2 bootloaders (either through the Amazon update or the procedure below), there is no going back !!! The only other bootloaders you can run at this point are 4.5.3 as per post #2
Update4: Please do not deviate from the instructions, and do flash GAPPS during Step 1), together with Xposed. JMZ tool for installing GAPPS is not recommended!
For lazy ones I recommend skipping factory reset in Step 1) below if you already have Lollipop.
Install instructions.
Unless you have 4.5.3 bootloaders and TWRP at the moment, your path into TWRP goes via post #2 (and you do need TWRP to proceed!!!). No need to fear, I have made a simple script to flash 4.5.3 bootloaders and TWRP in just one click, see section "101" in post #2 !!!
Before proceeding, please write down your current FireOS version, and its date. To install the latest Lollipop you can pretty much start anywhere, these are rough suggestions how to get TWRP running in the quickest way possible :
unrooted Lollipop, pre-5.1.2 or 5.1.2, root via KingRoot (try several times), use post #2 for TWRP, re-load 5.1.2 from TWRP by following this post
unrooted Lollipop, alternative option, (note the version you have!!!), downgrade to 4.5.3 via stock recovery ADB sideload option (block updates immediately!!!), root 4.5.3, use post #2 to install TWRP
already rooted Lollipop, use post #2 to boot into TWRP, the bat script in section "101" is recommended (and can do a clean re-install of your current Lollipop version with the same procedure if you care)
rooted FireOS 4.5.x (latest Kingroot is known to root either 4.5.3 or 4.5.5.1, perhaps 4.5.4 & 4.5.5 as well) -then post #2 (if the bootloaders are not 4.5.3)
unrooted 4.5.x (>4.5.3 such as 4.5.4 or 4.5.5 but pre-4.5.5.1): disable OTA, run latest Kingroot, report back if failure, use post #2 for TWRP
unrooted whatever - write directly into memory 4.5.3 bootloaders & TWRP (somewhat slow, but can be an attractive option if you cannot root your version of Lollipop directly, and don't want to factory reset the device memore during the downgrade to 4.5.3 in order to root) :
http://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
0) Before proceeding, ensure that you have a functional non-system launcher (install any as user app), or enable the stock Amazon launcher via adb if it's blocked (pm enable com.amazon.firelauncher) !!! Make sure it works. This will ensure that you can avoid problems later on when the /system partition is overwritten, and your non-Amazon launcher that was installed as a system app is gone. I had Nova as the system app (overwritten by the upgrade!), and Amazon launcher blocked, so after the upgrade to 5.1.2 there was no working launcher. Not good ... Had to do a couple of system resets and TWRP restores until I figured out what was happening ...
1) boot into TWRP, and, in a single session (!!!!!)
(Optional) clear cache/dalvik (to shrink the backup size), run TWRP backup to a USB drive via USBOTG cable for your /data partition
(Optional) do factory reset (can skip if you already have Lollipop),
flash the latest FireOS from this official Amazon link (rename *bin to *zip such that TWRP can recognize it):
https://www.amazon.com/gp/help/customer/display.html?nodeId=201596850
If for some reason you need a different FireOS version, grab the file you need from the links in this post.
flash 5.2.0_stock_recovery_only.zip below. If you kept track of your prior FireOS versions and know what you are doing, you can flash
5.4.1_1133_stock_recovery_uboot.zip from post #2 (this will flash 5.2.0 stock recovery & 5.4.1 bootloaders). Note that if you downgraded from FireOS 5.3.1 to 4.5.3 to root, you must flash 5.5.2_1534_stock_recovery_uboot.zip instead, this will put the required 5.3.1 bootloaders back.
flash the attached make_space_v02.zip (this will remove moffice and weather to make room in /system for GAPPS , can always install this stuff from Play Store)
flash Supersu.zip https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
flash Xposed for Lollipop 5.1 (if you want it for misc modules, highly recommended to do this just in case)
http://forum.xda-developers.com/showthread.php?t=3034811
(version xposed-vXX-sdk22-arm.zip )
flash Pico (Uni) GAPPS for 5.1 :
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
clear cache/dalvik in TWRP
Another reminder: If you are absolutely sure that you have never run FireOS 4.5.5.1 bootloaders or Lollipop with anything but 5.2.0 bootloaders, you can flash 5.2.0_stock_recovery_uboot.zip from post #2 here, this way you preserve the well behaved 5.2.0 bootloaders. If you are not sure about any of this, don't do it !!!
2) reboot to recovery, you should see stock 5.2.0 recovery (this is just to see if it works, for troubleshooting, but otherwise a meaningless step from the update perspective ...). Notice that at this point you no longer have TWRP. Since it does not boot with the 5.x bootloaders anyway, TWRP was replaced with the stock recovery that has some useful features, such as adb sideload. Later on it's possible to get back into TWRP from within the rooted Lollipop by following post #2.
3) reboot to Lollipop (takes ~15 minutes), and hopefully, it works.
Bricking warning !!! If you flashed the wrong bootloaders, and you get a black screen upon reboot, there is good news - you can UNBRICK !!! The bad news is that the procedure is quite involved, and may take quite a bit of effort. So measure twice, cut once !!! If unsure about bootloaders, ask here first before flashing, instead of coming back to complain about the brick later.
4) if step 3) fails, you get into working 5.2.0 recovery by pressing "Pwr & Vol+". At this point you sideload 4.5.3 stock, and go back to step 0). Come back here and ask questions (and thank me again for being able to recover so easily !!! )
5) make_space_v02.zip already disabled OTA updates , but please verify that you now have DeviceSoftwareOTA.apk_ block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_
6) Consider adding an option to switch from pure Amazon interface to almost pure Android and back on the fly:
http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
Note: Using JMZ tool for installing GAPPS is not recommended, please flash GAPPS as per Step 1)
The next post discusses how to get into TWRP temporarily with Lollipop installed, and come back to Lollipop
Want to say thanks by clicking the "Thanks" button ?
{
"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"
}
Higher skill level operation - proceed with care !!!
Update3.5 : Updates for 5.3.1 !!! Please use 5.5.2_1534_stock_recovery_uboot.zip if you downgraded from stock FireOS 5.3.1 to 4.5.3 for rooting, meaning that you now have 5.3.1 bootloaders
Update3.4 : Updates for 5.1.2 !!! Please use the new WindowsAutoTWRP_v03.zip with 5.1.2 (backward compatible to 5.1.1 and before). There are tons of verification messages in the new script, please read carefully !!! It appears that in 5.1.2 there is a bug such that root cannot see /sdcard/gscript properly (this was the issue caused by the latest SuperSu I tried). To handle this, I redirected the path to /data/media/0/gscript . If you are using Gscript, delete the flash_453(_stay) scripts in Gscript, and open them again after you run WindowsAutoTWRP_v03 once. This way Gscript will pick up the corrected scripts with the updated path. Pay attention to the checksums !!!
Update3.3 : And now "Newbie Friendly" !!! Just one simple *.bat script under Windows !!! See section "101"
Update3.2 : If you are unsure what bootloader file to use, go with 5.4.1_1133_stock_recovery_uboot.zip
Update2: If you ever booted the Sept 2015 Lollipop (FireOS 5.0.1, called here 5.2.2u2), DO NOT use 5.2.0_stock_recovery_uboot.zip , it will brick!!!
Update1: Instructions are clarified with more detail on how to use "dd" correctly.
Important : do not try to use Flashify!!! Flashify cannot access all partitions that you need to flash !!! Flashify will brick your Fire !!!
Here you get to run TWRP again, and then return to Lollipop.
The steps must be executed with precision (all 3 files must be dd'ed successfully). Keep the 5.4.1_1133_stock_recovery_uboot.zip file from below on the device, in its /images directory you have 3 images for 5.4.1 which you can flash back right away if you need to abort. If something is wrong, DO NOT reboot for as long as it takes. Keep the device without reboots, and come back here for guidance.
To understand a bit what we are doing in this post, read this :
A bit of background. Fire HD boots TEE1 -> UBOOT -> recovery. With 4.5.3, we lucked out that TEE1 & UBOOT accepted unsigned recovery (aka TWRP). No such luck with 5.2.x - TEE1 & UBOOT expect signed recovery (for example, stock one). That's why I had everybody overwrite TWRP with stock recovery in post #1 as the last step in the upgrade. Otherwise after the upgrade to 5.2.x, TWRP would still be sitting in recovery, and being unsigned, it cannot boot !!! A few bricks were created because of this last point. But with the stock 5.2.0 recovery (which it will boot), at least there is an option to sideload another update file.
So, the key to running TWRP while in 5.2.x is to overwrite the 3 key components together (TEE1, UBOOT, recovery), and then return things to 5.2.x once TWRP is no longer needed.
For convenience, before proceeding save all the attached files on your Fire in "/sdcard/gscript"
101 - Automatic installation under Windows !!!
I managed to debug it and not to brick !!! Tested personally (gotta eat your dog food !!!) Heavily inspired by glitch3yf0x in http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804
Save the necessary Lollipop bootloaders zip into /sdcard/gscript on Fire HD, this will get you back into Lollipop
Download WindowsAutoTWRP_v03.zip to your PC with some Windows on it, unpack anywhere
Run the commands below, and make sure you authorize root access for adb when the question pops up on your Fire:
Code:
adb shell
su
exit
exit
Enable apps from unknown sources
Run 1_FIRE_HD_4TH_GEN_TWRP.bat
At the bottom you should see these checksums :
Code:
3a1f3cd1ef405eaeec719eaeb41ab791 /dev/block/mmcblk0p3
d605e31a180652c65d6957b58d2d8501 /dev/block/mmcblk0p5
305a5546ff8960b51cd573b59a05cde6 /dev/block/mmcblk0p7
Make sure the checksums are correct before rebooting !!! Do not reboot if checksums are wrong, keep the Fire running, and come back here to ask questions !!! I almost bricked under 5.1.2 due to the newer SuperSu version, but managed to catch the wrong checksums, and updated the scripts to have additional verifications.
A possible issue here is that you did not have root access, so the "dd" commands could not succeed. At this point you can go to method A since the script left all the necessary ingredients on the device, so all you need to do is to run the script from Gscript (installed for you!), make sure you click "needs SU". Delete the old flash_453 and flash_453_stay scripts from Gscript, and re-open them again after you run WindowsAutoTWRP_v03 at least once.
Verify again that you have 5.x.x bootloaders zip file on Fire HD which you will access from TWRP (it can also be on a USB drive if you got USB OTG cable) - Out of kindness I've provided the most popular bootloaders zip at the moment - 5.4.1 version, you can find it in /sdcard/gscript, it's TWRP ready, just flash it if 5.4.1 is OK for you (5.4.1 bootloaders will also work with FireOS 5.1.2 )
Type "adb reboot recovery"
In TWRP, after you are done with everything, don't forget to flash the 5.x.x bootloaders zip file in order to boot back into Lollipop!
After the batch file runs, you will have Gscript installed, together with the required script & image files in /sdcard/gscript, so you can head over to the next section (section A), and set up TWRP access without using a PC! You will also have scripts in there to enable/disable Amazon's stuff on the fly, as described in here :
http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
A - Instructions with Gscript.
Due to popular demand (looking at DoLooper here ), the approach is simplified and all the bootloaders are flashed via a script, and this assumes that you have Gscript installed (here : https://bitbucket.org/Equidamoid/gscript/downloads )
Download the attached "453_key_images.zip" to your Fire, create a folder (if does not exist) "/sdcard/gscript", and unpack this zip file in "/sdcard/gscript" (so all *bins sit in this directory)
[*]Download the attached "flash453.zip", copy to "/sdcard/gscript", unpack
Run the bat from WindowsAutoTWRP_v03 in section "101" at least once
Go to Gscript/Add script/Need Su (yes, check)/Load file "flash_453_stay.sh"
From Gscript run this "flash_453_stay.sh", and verify the checksums
If you are using versions prior to FireOS 5.1.2, you can use "flash_453.sh" and you should end up in TWRP (it will reboot automatically)
If unhappy about auto-reboot, use "flash_453_stay.sh" script, it will only do "dd" and exit back to the current OS (no auto-reboot to recovery)
B - Alternative (old) instructions via ADB
Download the attached "453_key_images.zip" to your Fire, create a folder "/sdcard/gscript", and unpack this zip file in "/sdcard/gscript". From the PC side, open ADB and start typing :
adb shell
su
cd /sdcard/gscript
ls
dd if=453_tee1.img of=/dev/block/mmcblk0p3
dd if=453_uboot.img of=/dev/block/mmcblk0p5
dd if=453_twrp.img of=/dev/block/mmcblk0p7
exit
exit
adb reboot recovery
These are 4.5.3 bootloaders, and TWRP. Just like in the good old days under FireOS 4.5.x
This is a sample log, your output should look similar (typed commands are colored in red) :
C:\Program Files\Minimal ADB and Fastboot>adb devices
List of devices attached
0000000000000XXX device
C:\Program Files\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # cd /sdcard/gscript
cd /sdcard/gscript
[email protected]:/sdcard/gscript # ls
ls
453_key_images.zip
453_tee1.img
453_twrp.img
453_uboot.img
[email protected]:/sdcard/gscript # dd if=453_tee1.img of=/dev/block/mmcblk0p3
dd if=453_tee1.img of=/dev/block/mmcblk0p3
6364+1 records in
6364+1 records out
3258876 bytes transferred in 0.543 secs (6001613 bytes/sec)
[email protected]:/sdcard/gscript # dd if=453_uboot.img of=/dev/block/mmcblk0p5
dd if=453_uboot.img of=/dev/block/mmcblk0p5
414+1 records in
414+1 records out
212116 bytes transferred in 0.041 secs (5173560 bytes/sec)
[email protected]:/sdcard/gscript # dd if=453_twrp.img of=/dev/block/mmcblk0p7
dd if=453_twrp.img of=/dev/block/mmcblk0p7
14004+0 records in
14004+0 records out
7170048 bytes transferred in 1.103 secs (6500496 bytes/sec)
[email protected]:/sdcard/gscript # exit
exit
[email protected]:/ $ exit
exit
C:\Program Files\Minimal ADB and Fastboot>adb reboot recovery
Click to expand...
Click to collapse
Reboot into recovery, and you should be in TWRP.
C - What am I doing in TWRP ???
-- Well, you tell me
Generally, you want to flash something (Xposed, GAPPS?). Keep flashing whatever else you need! Note that at this point you won't be able to boot into 5.2.x, siegesoldier has established this fact with his early upgrade attempts. 4.5.3 bootloaders will not boot 5.2.x kernel due to some missing parameters !
When you want to go back to Lollipop, in TWRP flash the attached 5.4.1_1133_stock_recovery_uboot.zip (or 5.5.2_1534_stock_recovery_uboot.zip). This will put 5.4.1 (or 5.5.2) bootloaders back, as well as 5.2.0 stock recovery. Note if you are sure that you never had 5.4.1, 5.2.2u3 or 5.2.2u2 bootloaders running (or stock FireOS 4.5.5.1), use 5.2.0_stock_recovery_uboot.zip (this is rare now, be very sure !!!) If you forget to flash the 5.x.x bootloaders, the device will cycle upon reboot with the Amazon logo continuously. This is not a big issue ! Just hold the power button until the Fire shuts off. Then from the turned off state turn it on by pressing power and Vol+ buttons together, and this will get you back into TWRP where you can flash the 5.x.x bootloaders and reboot to Lollipop.
Now reboot to system, and you should have your Lollipop
Want to say thanks by clicking the "Thanks" button ?
bibikalka said:
. . . and finally, when TWRP asks you to install root, say "yes" . . .
2) reboot to recovery, you should see stock 5.2.0 recovery.
Click to expand...
Click to collapse
Yahoo! I'm either almost there or am no longer rooted. adb shell, su doesn't return #-sign, but I can "cd" and "ls" all around /system. SuperSU installer says I'm "not fully rooted," but if you press Play (store) Amazon wants to open appstore of course, and no TWRP. Tried adb install, which failed:
Desktop>adb install eu.chainfire.supersu.apk
3017 KB/s (5904943 bytes in 1.911s)
pkg: /data/local/tmp/eu.chainfire.supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]Guess I'm partially rooted? Need some reassurance because had a little trouble flashing (which I won't explain unless I must) . Anyway, I have 5.2.0 recovery and if superuser is as expected, I'll go for post 2 (i think)! Thanks!
Managed to get the upgrade from reading the last thread, but no TWRP. Thanks!!
DoLooper said:
Yahoo! I'm either almost there or am no longer rooted. adb shell, su doesn't return #-sign, but I can "cd" and "ls" all around /system. SuperSU installer says I'm "not fully rooted," but if you press Play (store) Amazon wants to open appstore of course, and no TWRP. Tried adb install, which failed:
Desktop>adb install eu.chainfire.supersu.apk
3017 KB/s (5904943 bytes in 1.911s)
pkg: /data/local/tmp/eu.chainfire.supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]Guess I'm partially rooted? Need some reassurance because had a little trouble flashing (which I won't explain unless I must) . Anyway, I have 5.2.0 recovery and if superuser is as expected, I'll go for post 2 (i think)! Thanks!
Click to expand...
Click to collapse
This happened to me as well... the su binary was in /system/xbin but wasn't working, and the app said I had to flash or install from the Play Store. I copied the Superuser.apk to /sdcard and installed it device side, worked fine.
Yes! thx! (Can easily get es file explorer from appstore for this.)
Thanks for this bro! I can confirm this process works, and I will show the steps I took here (clarification for people who want to do this).
1. I started on 4.5.4 + Root + TWRP with adb installed on my Mac
2. I connected fire to computer, and did (in terminal window)
adb backup -apk -shared -all ~/Downloads
to save my data before factory reset (this should work on Mac + Linux).
3. Rebooted to TWRP
4. Performed a Factory Reset (the default one under Wipe on TWRP)
5. Installed the 5.2.0 bin file with adb sideload
6. Installed 5.20 stock recovery with adb sideload
7. Went to Reboot page and chose reboot recovery
8. TWRP will prompt you to install root, do it
9. It will then reboot into stock Amazon recovery, choose to reboot your system
10. Mine took forever, but it finally booted into 5.2.0
11. If you're plugged into the computer, it gives you the option to enable usb debugging, do this
12. I completed the setup process
13. Downloaded SupersSU from here on computer
14. Used
adb install -r supersu.apk
(or whatever your's is named)
15. Check you have root by running
adb shell
su
16. You should have root installed!
17. Now run
adb restore backup.ab
which will restore your data (apps)
18. SKIP UNLESS YOU HAD XPOSED INSTALLED If you had Xposed installed, it is not compatible now, so uninstall all of your modules (if you want to save space). I believe the problem with Xposed is that we need to change a build.prop sdk/api value, but that's something for us to figure out later.
19. Install jmz fire tools from here
20. Run it and choose install Gapps, your device will reboot
21. Sucess!!! Lollipop + Root + Gapps
Anyways, good luck to everyone I hope this helps someone in the future!
---------- Post added at 10:33 AM ---------- Previous post was at 10:32 AM ----------
DoLooper said:
Yahoo! I'm either almost there or am no longer rooted. adb shell, su doesn't return #-sign, but I can "cd" and "ls" all around /system. SuperSU installer says I'm "not fully rooted," but if you press Play (store) Amazon wants to open appstore of course, and no TWRP. Tried adb install, which failed:
Desktop>adb install eu.chainfire.supersu.apk
3017 KB/s (5904943 bytes in 1.911s)
pkg: /data/local/tmp/eu.chainfire.supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]Guess I'm partially rooted? Need some reassurance because had a little trouble flashing (which I won't explain unless I must) . Anyway, I have 5.2.0 recovery and if superuser is as expected, I'll go for post 2 (i think)! Thanks!
Click to expand...
Click to collapse
pcrhckyman said:
Managed to get the upgrade from reading the last thread, but no TWRP. Thanks!!
This happened to me as well... the su binary was in /system/xbin but wasn't working, and the app said I had to flash or install from the Play Store. I copied the Superuser.apk to /sdcard and installed it device side, worked fine.
Click to expand...
Click to collapse
I fixed this by running
adb install -r eu.chainfire.supersu.apk
or whatever your supersu file is named.
Easy TWRP and Gapps?
bibikalka said:
OK, here the risk is pretty simple - likely brick. On the upside, you get to run TWRP, and then return to 5.2.0.
Click to expand...
Click to collapse
Remolten said:
I fixed this by running adb install -r eu.chainfire.supersu.apk or whatever your supersu file is named.
Click to expand...
Click to collapse
Yep, still learning, and thanks for the detailed steps.
Why not adb install (or file explorer install) Flashify or TWRP manager, install TWRP, and then Gapps? Or for that matter, use Flashify to install Gapps? Thanks.
As far as GAPPS, go the lazy way of using JMZs app just worked for me. I'll be removing the modifications that prevent the apps from updating shortly. But the old playstore works fine on lolipop.
DoLooper said:
Yep, still learning, and thanks for the detailed steps.
Why not adb install (or file explorer install) Flashify or TWRP manager, install TWRP, and then Gapps? Or for that matter, use Flashify to install Gapps? Thanks.
Click to expand...
Click to collapse
I don't think the Flashify method works, but I will try it.
EDIT: Flashify requires custom recovery
EDIT 2: Trying siegesoldier's method
EDIT 3: We have a winner! Thanks siegesoldier and jmz!
siegesoldier said:
As far as GAPPS, go the lazy way of using JMZs app just worked for me. I'll be removing the modifications that prevent the apps from updating shortly. But the old playstore works fine on lolipop.
Click to expand...
Click to collapse
Thx for info, but JMZ's TWRP manager is crashing on me.
DoLooper said:
Thx for info, but JMZ's TWRP manager is crashing on me.
Click to expand...
Click to collapse
This one silly!
http://forum.xda-developers.com/fir...ool-jmz-fire-hd-7-tool-gapps-disable-t3113655
siegesoldier said:
This one silly!
Click to expand...
Click to collapse
lol thx. (Sorry for taking up more space here, but that was funny!)
FYI. Xposed is possible if you downgrade back to 4.5.3/twrp and after flashing lolipop, but before replacing recovery, flash xposed-v67-sdk22-arm-by-romracer-20150716.zip found in http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979 and install XposedInstaller_3.0_alpha4.apk once you're back into lolipop found here http://forum.xda-developers.com/showthread.php?t=3034811.
bibikalka said:
OK, fellas, 1st attempt for a reasonably safe journey to rooted Lollipop. The key now is to flash 5.2.0 recovery right after flashing 5.2.0 stock, this way there is an option to recover if something goes wrong.
Disclaimer : most of the info is compiled from other threads. Myself, I have tested flashing the attached 5.2.0 stock recovery zip from TWRP, it works fine.
Big credit here hawkazn for blazing the trail, and getting to a working rooted Lollipop first, then dumping the stock recovery:
http://forum.xda-developers.com/showpost.php?p=62009468&postcount=75
0) I assume you have TWRP installed and working, which means you've followed the guide to step 3) only, [and skip all the steps after 3) , since nobody is going to care, no extra credit here!]:
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
1) boot into TWRP, and, in a single session (!!!!!)
do factory reset,
flash the 5.2.0 update from this post (the official 5.2.0 zip will work just fine):
http://forum.xda-developers.com/fire-hd/general/lolipop-ota-capture-t3141810
flash the attached 5.2.0_stock_recovery_only.zip
and finally, when TWRP asks you to install root, say "yes"
Let's pause for a second and realize what we did here - we've put full stock 5.2.0, added root, and, most importantly, overwrote TWRP with 5.2.0 stock recovery.
2) reboot to recovery, you should see stock 5.2.0 recovery
3) reboot to 5.2.0 OS, and hopefully, it works. Install SuperSu to manage root requests.
4) if step 3) fails, you get into working 5.2.0 recovery by pressing "Pwr & Vol+". At this point you sideload 4.5.3 stock, and go back to step 0). Come back here and ask questions.
You may be asking about GAPPS - try to install manually, as indicated here :
http://forum.xda-developers.com/showpost.php?p=62008212&postcount=71
More experimental stuff in the next post.
Click to expand...
Click to collapse
Glad I was able to help out and get it working for everyone!
Fantastic effort in a short period of time !!! The sales of HDs and "brick" returns will surely skyrocket
Also, noting the confusion with TWRP, I've updated my post #2 to explain exactly why all that stuff needs to be done to run TWRP :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
DoLooper said:
Yep, still learning, and thanks for the detailed steps.
Why not adb install (or file explorer install) Flashify or TWRP manager, install TWRP, and then Gapps? Or for that matter, use Flashify to install Gapps? Thanks.
Click to expand...
Click to collapse
TWRP is not signed, and will not run with the bootloader from 5.2.0 which expects a signed recovery. That's was the whole reason to do the "circus" with 3 dd's, basically, one needs to flash all the bootloaders in the chain from 4.5.3, together with TWRP to be able to boot into TWRP. After that, one would reflash back all the bootloaders and recovery back to 5.2.0 versions.
Remolten said:
I don't think the Flashify method works, but I will try it.
EDIT: Flashify requires custom recovery
EDIT 2: Trying siegesoldier's method
EDIT 3: We have a winner! Thanks siegesoldier and jmz!
Click to expand...
Click to collapse
See the above answer, to get into TWRP, you have to flash all 3 files together. But itself, TWRP does not boot from 5.2.0 bootloaders, that's why people had bricks before when they did not replace TWRP after flashing 5.2.0
siegesoldier said:
FYI. Xposed is possible if you downgrade back to 4.5.3/twrp and after flashing lolipop, but before replacing recovery, flash xposed-v67-sdk22-arm-by-romracer-20150716.zip found in http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979 and install XposedInstaller_3.0_alpha4.apk once you're back into lolipop found here http://forum.xda-developers.com/showthread.php?t=3034811.
Click to expand...
Click to collapse
Ha-ha, love Alex' 3rd Fire! Must have chewed through 2 previous ones Indeed, you can run TWRP, provided it's booted via 4.5.3 bootloaders. And after flashing 5.2.0 in TWRP, that's the last time you see TWRP booted up unless you then "dd" them back as in my post #2.
I will update that post to make these points more clear.
hawkazn said:
Glad I was able to help out and get it working for everyone!
Click to expand...
Click to collapse
Yep, thanks for making the 5.2.0 into a dull flashing experience instead of the nail biting one !!!
I am loving this good-looking and way more customizeable update! Thanks again!
bibikalka said:
That's was the whole reason to do the "circus" with 3 dd's, basically, one needs to flash all the bootloaders in the chain from 4.5.3, together with TWRP to be able to boot into TWRP. After that, one would reflash back all the bootloaders and recovery back to 5.2.0 versions.
Click to expand...
Click to collapse
If one wanted to, the 3 dds circus could still be done any time, right? So if we wanted to slap on TWRP for a quick flash we could do that?
Speaking for myself, getting Gapps turned out to be a priority once I saw lollipop on the Fire. And the "JMZ tool/allow update" method was both expedient and didn't include the phrase, "likely brick"
DoLooper said:
I am loving this good-looking and way more customizeable update! Thanks again!
If one wanted to, the 3 dds circus could still be done any time, right? So if we wanted to slap on TWRP for a quick flash we could do that?
Speaking for myself, getting Gapps turned out to be a priority once I saw lollipop on the Fire. And the "JMZ tool/allow update" method was both expedient and didn't include the phrase, "likely brick"
Click to expand...
Click to collapse
Ha-ha, true, saying "likely brick" is poor marketing. I'll rephrase it to something more benign
Disable ota on rooted 5.20
bibikalka said:
OK, fellas, 1st attempt for a reasonably safe journey to rooted Lollipop. The key now is to flash 5.2.0 recovery right after flashing 5.2.0 stock, this way there is an option to recover if something goes wrong.
Disclaimer : most of the info is compiled from other threads. Myself, I have tested flashing the attached 5.2.0 stock recovery zip from TWRP, it works fine.
Big credit here hawkazn for blazing the trail, and getting to a working rooted Lollipop first, then dumping the stock recovery:
http://forum.xda-developers.com/showpost.php?p=62009468&postcount=75
0) I assume you have TWRP installed and working, which means you've followed the guide to step 3) only, [and skip all the steps after 3) , since nobody is going to care, no extra credit here!]:
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
1) boot into TWRP, and, in a single session (!!!!!)
do factory reset,
flash the 5.2.0 update from this post (the official 5.2.0 zip will work just fine):
http://forum.xda-developers.com/fire-hd/general/lolipop-ota-capture-t3141810
flash the attached 5.2.0_stock_recovery_only.zip
and finally, when TWRP asks you to install root, say "yes"
Thanks to Remolten, there is a very detailed write up regarding all of this:
http://forum.xda-developers.com/showpost.php?p=62018692&postcount=6
Note that this is the last time you see TWRP (unless you do what I recommend in post #2), so take an opportunity to flash other stuff such as Xposed, thanks to siegesoldier for pointing this out (not sure about GAPPS yet without at least one reboot into 5.2.0):
http://forum.xda-developers.com/showpost.php?p=62021411&postcount=13
Let's pause for a second and realize what we did here - we've put full stock 5.2.0, added root, and, most importantly, overwrote TWRP with 5.2.0 stock recovery.
2) reboot to recovery, you should see stock 5.2.0 recovery (this is just to see if it works, for troubleshooting, but otherwise a meaningless step from the update perspective ...)
3) reboot to 5.2.0 OS, and hopefully, it works. Install SuperSu to manage root requests.
4) if step 3) fails, you get into working 5.2.0 recovery by pressing "Pwr & Vol+". At this point you sideload 4.5.3 stock, and go back to step 0). Come back here and ask questions.
You may be asking about GAPPS - install them via JMZ tool, there are reports that everything works just fine:
http://forum.xda-developers.com/fir...ool-jmz-fire-hd-7-tool-gapps-disable-t3113655
More experimental stuff in the next post, this is how to get into TWRP again with 5.2.0 installed.
Click to expand...
Click to collapse
Is it necessary to disable ota after upgrading to 5.2.0 with root? If so. How?
Brofreeman said:
Is it necessary to disable ota after upgrading to 5.2.0 with root? If so. How?
Click to expand...
Click to collapse
I'm not sure if it is required, but it is a good precaution just in case. If you install the JMZ tool, the third page has a switch to disable OTA's.
This thread contains a tutorial on how to patch boot.img on Samsung Lollipop devices and achieve root with a stock firmware. The tutorial is intended for those who wish to make their own boot.img for their specific firmware. For the rest, a patched boot.img for each device variant is attached. Simplified instructions for flashing with these patched images is first, followed by the tutorial.
NOTES!
1: YOU MUST EXTRACT THE .IMG FILE FROM THE TAR AND FLASH WITH TWRP. For some reason flashing with ODIN does NOT work with the images attached to this thread.
2: To make ODIN tars, look at @drExel's post here.
3: In most variants, TWRP 2.8.7.0 appears to work, though there are some issues. On some devices, it takes a REALLY long time to boot into TWRP, making you believe the device has frozen, but just give it time and it will load eventually. On other devices, TWRP loads, but touch does not work. In these cases, the S-Pen works without any problems (but is very sensitive). Some users have posted alternate TWRPs that work properly; search the thread for this. I am not including it here because I have not personally tried these versions myself.
4: Since this issue came up multiple times, though it is mentioned in the instructions below, I am stressing this once again. DO NOT ALLOW TWRP TO AUTOMATICALLY INSTALL SUPERSU WHEN YOU HIT REBOOT. THIS WILL CAUSE A BOOTLOOP, GUARANTEED! YOU MUST FLASH THE BETA 2.52 SUPERSU MANUALLY AFTER FLASHING THE PATCHED BOOT.IMG AND CONFIRMING THE DEVICE WORKS PROPERLY!
5: If you take the time to read the entire thread, you will find redirects to other kernels, firmwares and more. I am sure they are excellent, but having not used any of them, I cannot vouch for the outcomes if you flash them. All information related to the other firmwares and any questions you have about them are best served by going to their dedicated threads. This thread is ONLY for a pure stock firmware with only the boot.img patched to permit root, and nothing else touched.
6: XPosed Framework does not work yet for TW LL, but @wanam has an unofficial version here that various members have reported works quite well.
7: Knox WILL be tripped. If you care about Knox, leave now and do not come back!
Simplified Instructions
The thread originally began as a pure tutorial, with only the P607T image. But given the requests others had, and my need to confirm that this works on all variants, I made more patched images. No 'simple instructions' were available earlier because this was not intended for end-users who might flash and find that it does not work. Now that all the images are confirmed working, and we have tested on all variants, here is a simplified set of instructions for those who just wish to flash and do not care what they are flashing.
1: Update to fully stock 5.1.1 for your device. Whether it is OTA or ODIN flash using a firmware from sammobile or elsewhere does not matter. You start with a fully stock device running 5.1.1.
2: Download the appropriate patched_boot.img for your device. They are attached as tar files due to XDA size restrictions, so you must untar and then save the .img file to your device. Also download SuperSU Beta 2.52.zip and save it as is to the same folder on your device where you put the .img file.
3: Download TWRP 2.8.7.0 for your device and flash it with ODIN. To get TWRP to stick, when the device reboots, you must go directly into recovery. If the device reboots normally, TWRP will be replaced by the stock recovery. There are guides on how to flash TWRP and you should go look at them if you are unsure how to do this.
4: Once you are in TWRP, go the Install area. The default is for installing .zip files. At the bottom right of the screen, you will see a button to change to Images. Hit this. Then select the patched_boot.img file that you saved on your device in the previous step. When you hit install, TWRP will ask you whether this is a boot image or a recovery image. Select Boot. Let TWRP do its thing. When done, go back and hit reboot. TWRP will volunteer to install SuperSU for you now. SAY NO TO THIS. If you accept this install, your device will bootloop and you have start all over again!
5: Make sure the device rebooted without any problems. You will see a red "Kernel SEAndroid Not Enforcing" message when you reboot. Ignore it, it just means that the patched boot.img is working. Once you have confirmed that the device is able to boot properly with the patched boot.img, reboot into recovery again. Go back to Install, this time, stick with Zip mode and install the Beta SuperSU 2.52.zip that you saved to your device. Reboot.
6: If you followed instructions properly, you will reboot without any problems. Run SuperSU, allow it to update if it wants to, and to disable knox if you want to. You have a rooted device now with a virgin firmware.
7: This process has worked for enough people now that any errors are user errors. If you are bootlooping after following these instructions to the letter, you should do a full factory reset and try from scratch. A previous incorrect flash of SuperSU that caused a bootloop seems to persist even if you reflash the stock firmware and messes things up. Always perform a clean install!
Tutorial to patch your own boot.img
This section is NOT meant for the non-technical end-user who "... just wants root ... "
So far, it seems the only way to get root on the 5.1.1 Firmware was to flash a permissive kernel that disabled SEAndroid completely. This is a bit like killing the patient to cure the disease. @Chainfire describes a 'trick' to get root with a fully stock kernel on this thread. Special Thanks to @garyd9 and @SHM for helping me get everything working properly.
Part 1:
1) Extract boot.img from your device's stock firmware.
2) Unpack the boot.img to get access to the ramdisk.
3) Copy the sepolicy file from the ramdisk. You will be patching this file to make the usual SuperSU method work again.
The stock image can be extracted from the firmware using any archive tool. To unpack the boot.img, you can take a look at the following threads for tools and instructions.
Carliv's Kitchen : Windows, very beginner friendly.
SHM's Toolset : I used this on Linux.
copy sepolicy from the ramdisk folder to your adb folder (If you are on Windows and using Minimal ADB and Fastboot; I am assuming linux users don't need to be told what to do here )
Part 2:
1) Connect an already rooted device running 4.4+ firmware & SuperSU Beta 2.50+ to your system. Make sure you have adb access.
2) Push the sepolicy file to the device.
3) Run supolicy on the sepolicy file to patch it.
4) Pull the sepolicy file back to your computer.
I used my rooted Note 2 to get the job done. ANY rooted device that permits adb should do the trick, but it needs to be on 4.4+ firmware and running SuperSU Beta 2.50+.
Once you have an adb connection established, do the following (this is from Chainfire's thread referenced at the beginning):
Code:
adb push sepolicy /data/local/tmp/sepolicy
adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out"
adb shell su -c "chmod 0644 /data/local/tmp/sepolicy_out"
adb pull /data/local/tmp/sepolicy_out sepolicy_out
Part 3:
1) Replace the sepolicy file in the stock ramdisk with the newly patched sepolicy file.
2) Repack the ramdisk.
3) Make a new boot.img with the stock kernel and repacked ramdisk.
4) Flash new boot.img on your Note 10.1. Reboot, make sure everything is working.
Replace the sepolicy in the ramdisk with the sepolicy_out file that you pulled from your reference device. This means RENAME sepolicy_out and overwrite the original sepolicy file.
Repack the ramdisk using the instructions that came with your tool.
Make a new patchedboot.img file using the instructions that came with your tool.
Copy this patchedboot.img file to your Note 10.1, reboot into TWRP, go to the install zip section, toggle image mode, flash the patchedboot.img file and reboot the device. DECLINE TWRP's friendly offer to install SuperSU for you. This will cause a bootloop!If the device reboots successfully, pat yourself on the back. At this point, all you have done is patched the sepolicy to allow rooting, but you have not yet rooted the device.
Part 4:
1) Use TWRP to install SuperSU Beta 2.50+ (I used 2.52)
2) Reboot
Copy SuperSU Beta 2.50+ (I used 2.52) to the device, reboot into TWRP and install SuperSU. Reboot for rooted Note 10.1 running a Stock Kernel and no compromised SEAndroid. Of course, it goes without saying, this will trip knox. Also, please note that XPosed is not out for 5.1.1 yet, at least not officially. @wanam has an unofficial version here that various members have reported works well.
Hey, So at what step in this do I start if I dl'ed the Patched boot img? Thanks in advance.
icemanscion said:
Hey, So at what step in this do I start if I dl'ed the Patched boot img? Thanks in advance.
Click to expand...
Click to collapse
Part 3, Step 4:
Flash new boot.img on your Note 10.1. Reboot, make sure everything is working.
Copy this patchedboot.img file to your Note 10.1, reboot into TWRP, go to the install zip section, toggle image mode, flash the patchedboot.img file and reboot the device. If the device reboots successfully, pat yourself on the back. At this point, all you have done is patched the sepolicy to allow rooting, but you have not yet rooted the device.
Click to expand...
Click to collapse
In TWRP, when you hit Install, on the bottom right, you will see an option for Images. Select that and when you goto the folder with your img, you should see the new img you copied on to your device. Continue with Part 4 for full root.
IF the device does not boot, you want to flash the stock boot.img again, so make sure you have a copy of that on your device as well, so you can recover easily!
karthikrr said:
Part 3, Step 4:
In TWRP, when you hit Install, on the bottom right, you will see an option for Images. Select that and when you goto the folder with your img, you should see the new img you copied on to your device. Continue with Part 4 for full root.
IF the device does not boot, you want to flash the stock boot.img again, so make sure you have a copy of that on your device as well, so you can recover easily!
Click to expand...
Click to collapse
I have issues with TWRP since it wont work properly for me, so I'm going to try it with Philz CWM. Thank you again.
icemanscion said:
I have issues with TWRP since it wont work properly for me, so I'm going to try it with Philz CWM. Thank you again.
Click to expand...
Click to collapse
Good luck Just make sure you have the stock boot.img around, in case there are any problems. You are the first one trying it on the P600, or at least the first who cared to write in this thread, so this is uncharted territory!
So to get the patches boot.img, we unpack the tar file posted in the OP?
Sent from my SM-P600 using Tapatalk
iridaki said:
So to get the patches boot.img, we unpack the tar file posted in the OP?
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Yes. xda does not allow me to post an image file greater than 8mb, but the P607T image is 10.5mb, so had to tar it. Decided to be consistent with all the images.
Technically, you can try to flash that .tar with ODIN, but in my case, it would not work. Only flashing the .img through TWRP did.
karthikrr said:
Yes. xda does not allow me to post an image file greater than 8mb, but the P607T image is 10.5mb, so had to tar it. Decided to be consistent with all the images.
Technically, you can try to flash that .tar with ODIN, but in my case, it would not work. Only flashing the .img through TWRP did.
Click to expand...
Click to collapse
Thank you! And thank you for providing us with a patched kernel!
I'll try rooting and installing Xposed tonight and report back!
iridaki said:
Thank you! And thank you for providing us with a patched kernel!
I'll try rooting and installing Xposed tonight and report back!
Click to expand...
Click to collapse
Technically its just a patched boot image with a STOCK kernel, but yea, glad to help The real work was done by Chainfire and garyd9 and SHM helped me put this thing together, so they deserve the thanks!
If you get Xposed on it, let me know which version. The official one does not work on TW LL yet, but I believe Wanam has another version out that does. I haven't had the time to install it and test it, so your review will be helpful.
karthikrr said:
Technically its just a patched boot image with a STOCK kernel, but yea, glad to help The real work was done by Chainfire and garyd9 and SHM helped me put this thing together, so they deserve the thanks!
If you get Xposed on it, let me know which version. The official one does not work on TW LL yet, but I believe Wanam has another version out that does. I haven't had the time to install it and test it, so your review will be helpful.
Click to expand...
Click to collapse
Any contribution is a worthy contribution!
Wanam Xposed works perfectly on my Note 4 and I think it will work on the 10.1 as well. I'll report back soon!
SM-P600-TWRP 2.8.7.0 touch input doesn't work, but stylus input does
Hi!
Thanks for your posts, I'm sifting through is now. I was reflashing TWRP 2.8.7.0 (for SM-P600) and discovered that it wasnt responding to touch input. But I quickly discovered that it's UI does respond to the s-pen
I'll share my rooting experience as soon as possible.
V
Hey !! Can you give me the ROM of Darkdroid for Micromax A177. Thanks
Vasishtha said:
Hi!
Thanks for your posts, I'm sifting through is now. I was reflashing TWRP 2.8.7.0 (for SM-P600) and discovered that it wasnt responding to touch input. But I quickly discovered that it's UI does respond to the s-pen
I'll share my rooting experience as soon as possible.
V
Click to expand...
Click to collapse
How do you make it? I cannot flash the twrp successfully, there is always an error saying ''Recovery is not SEAndroid Enforcing''.
iopxiang said:
How do you make it? I cannot flash the twrp successfully, there is always an error saying ''Recovery is not SEAndroid Enforcing''.
Click to expand...
Click to collapse
You should wait a few moments. TWRP will open.
Flashing the SU.zip ends up in Bootloop for me._.
Fabi7775 said:
You should wait a few moments. TWRP will open.
Flashing the SU.zip ends up in Bootloop for me._.
Click to expand...
Click to collapse
Did you flash the boot.img before flash SU?
iopxiang said:
Did you flash the boot.img before flash SU?
Click to expand...
Click to collapse
Actually not, sorry.
I just thougt it is worth a try.
The SM-P600 rooting(with your patched boot) was a success! I encountered no problems at all. Only the lack of touch responsiveness of twrp 2.8.x had me worried, but thankfully the s-pen had my back and I was able to browse the twrp UI with it.
I'm now restoring all my apps with titanium backup, I'll try out xposed later this afternoon.
Regarding the LL update: wow this tablet completely feels like a new device, the fluidity is just stunning. 60 fps animations
Vasishtha said:
The SM-P600 rooting(with your patched boot) was a success! I encountered no problems at all. Only the lack of touch responsiveness of twrp 2.8.x had me worried, but thankfully the s-pen had my back and I was able to browse the twrp UI with it.
I'm now restoring all my apps with titanium backup, I'll try out xposed later this afternoon.
Regarding the LL update: wow this tablet completely feels like a new device, the fluidity is just stunning. 60 fps animations
Click to expand...
Click to collapse
Finally, a confirmation Thanks for letting us know!
As for TWRP, I believe the 2.6.3.3 (or something else in the 2.6 series) works without any problems on the P600.
XPosed is officially not out for Samsung LL, BUT Wanam has a version in development that works well, according to @iridaki on this thread. If you switch TWRP or try Wanam Xposed, post an update here as well!
And yes, the LL update actually made the device feel so damn good, its practically a Note 10.1 (2015 Edition)!
karthikrr said:
Finally, a confirmation Thanks for letting us know!
As for TWRP, I believe the 2.6.3.3 (or something else in the 2.6 series) works without any problems on the P600.
XPosed is officially not out for Samsung LL, BUT Wanam has a version in development that works well, according to @iridaki on this thread. If you switch TWRP or try Wanam Xposed, post an update here as well!
And yes, the LL update actually made the device feel so damn good, its practically a Note 10.1 (2015 Edition)!
Click to expand...
Click to collapse
Twrp 2.6.x does work, however there is no option to flash .img files on those versions.
So you either have to use heimdall or something else in order to flash that boot.
The unofficial xposed 5.1.x on my nexus 5 worked without any problems, so I expect the same for the LL variant. But I'll keep you posted.
The multiwindow transitions now have fade in/out effects <3 and we now can snap floating windows to either the left or right sides D:
karthikrr said:
Update 3: The patched P600 image has been confirmed to work by @Vasishtha, who also says TWRP 2.8.7.0 works with the S-Pen, but no touch input.
Click to expand...
Click to collapse
Can we use Temasek's 2.8.7.0 TWRP that has touch working?
FYI, I created a custom flashable update.zip if anyone wants to flash from TWRP.
Note: You'll have to flash the two return to stock files: http://forum.xda-developers.com/android/development/rom-lg-g-stylo-h631-ms631-v10j-stock-t3211563
Steps:
1) Go to TWRP
2) Flash bootstack ZIP from XDA
3) Flash return to stock
4) flash custom update.zip attached below (or post 39 from thread http://androidforums.com/threads/ne...e-lg-stylo-h63110l.996880/page-2#post-7234560)
http://androidforums.com/attachments/update-zip.101841/
If you can't get the file downloaded, all I did was follow the getprop and setprop removal instructions from here: http://androiding.how/install-ota-update-twrp-zenfone-2/