FORUMS
Remove All Ads from XDA

[TUT] Install [FireOS 5.3.1, Jun 24, 2016], ROOT & GAPPS

844 posts
Thanks Meter: 573
 
By bibikalka, Senior Member on 24th July 2015, 05:19 AM
Post Reply Email Thread
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...lipop-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.amazo..._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/show...&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 :
  1. 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
  2. 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
  3. 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)
  4. 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)
  5. 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
  6. 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...lipop-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 (!!!!!)
  1. (Optional) clear cache/dalvik (to shrink the backup size), run TWRP backup to a USB drive via USBOTG cable for your /data partition
  2. (Optional) do factory reset (can skip if you already have Lollipop),
  3. flash FireOS 5.3.1 (5.5.2) from this official Amazon link (rename *bin to *zip such that TWRP can recognize it):
    https://kindle-fire-updates.s3.amazo..._552153420.bin
    If for some reason you need a different FireOS version, grab the file you need from the links in this post.
  4. 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.
  5. 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)
  6. flash Supersu.zip https://download.chainfire.eu/696/Su...erSU-v2.46.zip
  7. 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/show....php?t=3034811
    (version xposed-vXX-sdk22-arm.zip )
  8. flash Pico (Uni) GAPPS for 5.1 :
    http://forum.xda-developers.com/andr...gapps-t3116347
  9. clear cache/dalvik in TWRP
  10. 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...ch-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 ?
Attached Files
File Type: zip 5.2.0_stock_recovery_only.zip - [Click for QR Code] (7.09 MB, 6986 views)
File Type: zip make_space_v01.zip - [Click for QR Code] (282.9 KB, 3366 views)
File Type: zip make_space_v02.zip - [Click for QR Code] (282.9 KB, 2516 views)
The Following 81 Users Say Thank You to bibikalka For This Useful Post: [ View ] Gift bibikalka Ad-Free
 
 
24th July 2015, 05:24 AM |#2  
OP Senior Member
Thanks Meter: 573
 
More
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/amaz...flash-t3281804
  1. Save the necessary Lollipop bootloaders zip into /sdcard/gscript on Fire HD, this will get you back into Lollipop
  2. Download WindowsAutoTWRP_v03.zip to your PC with some Windows on it, unpack anywhere
  3. 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
  4. Enable apps from unknown sources
  5. Run 1_FIRE_HD_4TH_GEN_TWRP.bat
  6. 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.
  7. 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 )
  8. Type "adb reboot recovery"
  9. 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...ch-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 )
  1. 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)
  2. Download the attached "flash453.zip", copy to "/sdcard/gscript", unpack
  3. Run the bat from WindowsAutoTWRP_v03 in section "101" at least once
  4. Go to Gscript/Add script/Need Su (yes, check)/Load file "flash_453_stay.sh"
  5. From Gscript run this "flash_453_stay.sh", and verify the checksums
  6. 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)
  7. 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
  1. 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) :

    Quote:

    C:\Program Files\Minimal ADB and Fastboot>adb devices
    List of devices attached
    0000000000000XXX device

    C:\Program Files\Minimal ADB and Fastboot>adb shell
    shell@ariel:/ $ su
    su
    root@ariel:/ # cd /sdcard/gscript
    cd /sdcard/gscript
    root@ariel:/sdcard/gscript # ls
    ls
    453_key_images.zip
    453_tee1.img
    453_twrp.img
    453_uboot.img
    root@ariel:/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)
    root@ariel:/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)
    root@ariel:/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)
    root@ariel:/sdcard/gscript # exit
    exit
    shell@ariel:/ $ exit
    exit

    C:\Program Files\Minimal ADB and Fastboot>adb reboot recovery

  2. Reboot into recovery, and you should be in TWRP.


C - What am I doing in TWRP ???



-- Well, you tell me
  1. 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 !
  2. 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.
  3. Now reboot to system, and you should have your Lollipop
Want to say thanks by clicking the "Thanks" button ?
The Following 43 Users Say Thank You to bibikalka For This Useful Post: [ View ] Gift bibikalka Ad-Free
24th July 2015, 03:05 PM |#3  
Senior Member
Thanks Meter: 335
 
More
Quote:
Originally Posted by bibikalka

. . . and finally, when TWRP asks you to install root, say "yes" . . .
2) reboot to recovery, you should see stock 5.2.0 recovery.

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!
The Following 2 Users Say Thank You to DoLooper For This Useful Post: [ View ] Gift DoLooper Ad-Free
24th July 2015, 03:31 PM |#4  
Junior Member
Thanks Meter: 8
 
More
Managed to get the upgrade from reading the last thread, but no TWRP. Thanks!!

Quote:
Originally Posted by DoLooper

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!

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.
The Following 2 Users Say Thank You to pcrhckyman For This Useful Post: [ View ] Gift pcrhckyman Ad-Free
24th July 2015, 04:23 PM |#5  
Senior Member
Thanks Meter: 335
 
More
Yes! thx! (Can easily get es file explorer from appstore for this.)
24th July 2015, 04:33 PM |#6  
Senior Member
Thanks Meter: 98
 
More
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 ----------

Quote:
Originally Posted by DoLooper

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!

Quote:
Originally Posted by pcrhckyman

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.

I fixed this by running
adb install -r eu.chainfire.supersu.apk
or whatever your supersu file is named.
The Following 5 Users Say Thank You to Remolten For This Useful Post: [ View ] Gift Remolten Ad-Free
24th July 2015, 05:20 PM |#7  
Senior Member
Thanks Meter: 335
 
More
Easy TWRP and Gapps?
Quote:
Originally Posted by bibikalka

OK, here the risk is pretty simple - likely brick. On the upside, you get to run TWRP, and then return to 5.2.0.

Quote:
Originally Posted by Remolten

I fixed this by running adb install -r eu.chainfire.supersu.apk or whatever your supersu file is named.

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.
The Following User Says Thank You to DoLooper For This Useful Post: [ View ] Gift DoLooper Ad-Free
24th July 2015, 05:29 PM |#8  
Senior Member
Thanks Meter: 50
 
More
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.
The Following 2 Users Say Thank You to siegesoldier For This Useful Post: [ View ] Gift siegesoldier Ad-Free
24th July 2015, 05:33 PM |#9  
Senior Member
Thanks Meter: 98
 
More
Quote:
Originally Posted by DoLooper

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.

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!
24th July 2015, 05:59 PM |#10  
Senior Member
Thanks Meter: 335
 
More
Quote:
Originally Posted by siegesoldier

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.

Thx for info, but JMZ's TWRP manager is crashing on me.
24th July 2015, 06:00 PM |#11  
Senior Member
Thanks Meter: 50
 
More
Quote:
Originally Posted by DoLooper

Thx for info, but JMZ's TWRP manager is crashing on me.

This one silly!

http://forum.xda-developers.com/fire...sable-t3113655
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes