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.
Android N Preview npc56p (flashable & image with no encryption and dm verification)
This thread is for the first Android N Preview.
For Android N Preview 2 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **** The following are instruction for installing Android N Preview image released by Google on 3/9/2016. After the installation you will have TWRP recovery 3.0.0-1 and the data partition will be erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery
1- You need to have TWRP installed on your phone.
2- Download this flashable zip.
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N. If your internal storage is unencrypted before flashing it remains unencrypted. Your TWRP is also upgraded to 3.0.0-1.
Method 2: Flash update using a computer
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.0-1.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root
To obtain root after installing this update you should flash SuperSU 2.70 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726. Note that at least at the moment (as of SuperSU 2.70) the root method is a hack solution which requires a lot of further refinement. Many programs are still unable to acquire root and mount the system partition for R/W. However, it is possible to install the android terminal emulator, do an su, mount /system as rw, and do all the modifications within the terminal emulator. Of course you can always use TWRP to modify the system, for which you don't even need to root the device.
Hot dog! First for once... Thanks!
Sent from my Nexus 6 using Tapatalk
#2
will this wipe internal storage ? or only data partition?
For anyone interested...
I enrolled in the Developer Beta program and the OTA worked for me even though I was rooted with SuperSU v2.68.
However, despite installing TWRP 3.0.1 and then SuperSU v2.68 again, root doesn't stick. Fortunately the only critical previously-root-only app I want is a firewall, and Netguard doesn't need root. I can live for a while without Double Tap To Wake, Wakelock detector, Quick Reboot, etc. And the only app that seems to crash is BBC Radio Player, though BBC News and iPlayer still seem ok (warning about libraries, but still plays). And Battery Bot Pro seems to have lost its status bar display...
So it does pretty much what the warnings say - it's stable but not everything will work.
so if i flash this i will still have twrp once rebooted?
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
It would be nice moving forward if Google just made SuperSU/root part of their factory image under developer options. So once you enable developer option, there's a little toggle next to OEM unlock that says "root/SuperSU".
Would make life much easier.
simms22 said:
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
Click to expand...
Click to collapse
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
The zip doesn't include stock recovery so if you flash everything according to the instructions you will have twrp at the first reboot.
This kernel worked great thanks. I'm still decrypted and didn't have to wipe internal storage. I didn't run the .bat I manually flashed the img files. Wiped data with TWRP.
so can we flash this via twrp?
omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
no, those are IMG format, flash via fastboot.
I'd wait for root ready then flash...
omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
It literally says right next to the link, "Note that it is NOT a flashable zip."
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
it says twrp recovery in title, so I was wondering....
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
chapelfreak said:
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
Click to expand...
Click to collapse
I flashed that boot img and now i am encrypted and boot-looping. No access to SD card.
Does this build have new bootloader and radio? If so, is it backward compatible to Marshmallow roms or do we need to flash back M bootloader and radio to get M roms work?
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
I lold at this. :laugh::laugh::laugh::laugh:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
kclive said:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
Click to expand...
Click to collapse
Toggle on and off airplane mode. Turn off wifi and see if it works. I was at work and had to do this a few times
Flashed phh kernel (su-noverity - 3rd one) and installed this superuser. I now have root working.
{
"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"
}
T-Mobile USA LG-H830 20f
This thread provides a stock T-Mobile H830 TWRP-flashable update for 20f as well as the 20f KDZ and all IMGs.
Information:
20f is the second official Android 7.0 Nougat update from LG! 20f has patched the dirty cow bug which methods like recowvery and dirtysanta used for root. If on 20c or higher and you want TWRP/root you'll have to downgrade to 20a using LGUP + UPPERCUT + 20a KDZ then once back on 20a you can use recowvery to install TWRP and then once you're in TWRP you can flash SuperSU.. this 20f COMPLETE zip.. other custom ROMs.. etc.
Anti-Rollback Version: 01
Android Version: 7.0
Android security patch level: Mar 1, 2017
Baseband version: MPSS.TH.2.0.c1.4-00042-M8996FAAAANAZM-1.74312.1
Kernel version: 3.18.31
Build date: Mar 21, 2017
Build number: NRD90U
Stock 20f build.prop :
Install Directions:
Click button below to view install directions to update to 20f w/LG Bridge, LGUP (KDZ) or TWRP-flashable ZIPss.
For no root/100% stock just flash the KDZ. Flash KDZ with either LG Bridge or LGUP. LG Bridge downloads and flashes the KDZ automatically but can be weird/buggy. LGUP requires downloading 20f KDZ file yourself but it's pretty simple after that. If you have TWRP and want to keep it or want root then you'll want the zip files.
LG Bridge Directions:
Click button below to view steps
1. Download/install LG Bridge for Windows or Mac.
2. Launch LG Bridge and connect G5 while it is still booted in Android.
3. LG Bridge will detect and connect to your device then scan for updates. Update if available.
LGUP Directions:
Click button below to view steps
1. Download the following three(3) files on Windows PC (Windows only. Mac/Linux? Use a Windows Virtual Machine):
LGUP_Lab_Frame_Ver_1_14.msi
UPPERCUT
Latest LG Windows PC drivers
2. Download KDZ. Install LGUP 1.14 and LG USB drivers if not already installed.
3. Turn OFF device then place in Download Mode: Hold Volume Up while plugging in USB cable.
4. Double-click the UPPERCUT.exe to load LGUP...
How-to use LGUP and flash software:
Select device
Check BIN File box under File Type then select KDZ file
Check "Upgrade" box in center of program to keep data. Use "Refurbish" to run a factory reset and wipe all data.
Click START button to flash file to G5 (you may have to close and reopen LGUP before being able to hit Start)
Install via TWRP:
Click button below to view steps
Below are options for flashing zips in TWRP... if you want stock unrooted system w/TWRP(A) or stock rooted(B).. which will fail on SafetyNet check.
SafetyNet now checks for unlocked bootloader. A custom kernel is needed to bypass that.
To flash the 20f ZIPs you need the new TWRP 3.0.2-1.img from jcadduono and your bootloader unlocked.
If on M... See Tungkick's H830 Root Thread for info on obtaining unlocked bootloader status + TWRP. If on stock 20f and want TWRP/root... unlock your bootloader then you can install TWRP using the info here from z28james.
A. Stock Unrooted w/ TWRP.
You need the COMPLETE zip + either the no-verity-opt-encrypt.zip OR boot repack zip.
Data unncrypte users: Use no-verity-opt-encrypt.zip. Those keeping data encryption: boot repack zip.
If you don't want TWRP/root and don't want to use a KDZ.. flash the COMPLETE zip by itself.
Click the button below to view steps
1. Download files and place on G5 internal or external SD card.
Have encrypted data and no external sdcard? ADB Sideload in TWRP.
LG-H83020f-Flashable.COMPLETE-ARB01.zip
no-verity-opt-encrypt-4.1.zip.Thanks to @jcadduono!
android-boot-repack.zip. Thanks to @jcadduono!
2. (re)Boot into TWRP
3. Install the COMPLETE ZIP + noverity/bootrepack ZIP:
LG-H83020f-Flashable.COMPLETE-ARB01.zip (Install > select zip > swipe to confirm/flash)
no-verity-opt-encrypt.zip OR android-boot-repack.zip (Install > select zip > swipe to confirm/flash)
After zips finish flashing you can reboot! If TWRP asks if you want to install SU, hit no. If TWRP says No OS installed, ignore it.
B. Stock ROOTED. SafetyNet FAILS.
This is the default root method for M. Flashing the SuperSU zip which repacks the boot.img for systemless root.
SafeyNet fails due to bootloader unlock being detected. You'd need to unroot and relock bootloader to pass SafetyNet.. or you can stay unlocked by flashing a custom kernel.
Click the button below to view steps
1. Download the following two files and place on G5 internal or external SD card.
Have encrypted data and no external sdcard? ADB Sideload in TWRP.
LG-H83020f-Flashable.COMPLETE-ARB01.zip
Latest SuperSU [BETA] Thanks to Chainfire!
2. (re)Boot into TWRP
3. Install the COMPLETE ZIP and SuperSU ZIP:
LG-H83020f-Flashable.COMPLETE-ARB01.zip (Install > select zip > swipe to confirm/flash)
SuperSU zip (Install > select zip > swipe to confirm/flash)
OPTIONAL:
To be extra safe in making sure TWRP sticks (in case SuperSU doesn't repack boot or user error) you can delete the "recovery-from-boot.p" file in the root of /system and TWRP will 100% stick... boot repack or not). You can use the TWRP Mounts button mount system as RW. And use the Advanced button in TWRP to use the file manager to delete the "recovery-from-boot.p" in /system.
Personally I just flashed the COMPLETE ZIP then I flashed SuperSU SR5 ZIP then rebooted phone and all went well.
After zips finish flashing you can reboot! If TWRP asks if you want to install SU, hit no. If TWRP says No OS installed, ignore it.
Downloads:
Click button below to view downloads for 20f, H830 and all G5 variants.
Please do not mirror files!
LG-H83020f-Flashable.COMPLETE-ARB01.zip
LG-H83020f-Flashable.Bootloader-ARB01.zip
LG-H83020f-Flashable.Modem-ARB01.zip
LG-H83020f-Flashable.Boot.zip
H83020f_00_0103.kdz
Codefire Directories:
G5 IMGs, drivers, flash tools, DLLs, KDZs, ZIPs and more can be found in the following directories...
LG-H83020f | LG-H830 | LG G5 | LGUP
MD5 Sums:
Click button below to view MD5 for each file...
15bc82584049ec3a7c62d921c2897267 ./rct.img
ae47fb2a40f260119e12d4b28c36b6a9 ./apdp.img
1b4461ac58dced17ccd7f30b09ab6d52 ./hyp.img
bbc49fb8f8ae2522814a870b84d41f6e ./pmic.img
5680e1ff66730b8cd4c16634ba60f503 ./boot.img
208fb4ed5233ee47f7163480113854dc ./LG-H83020f-Flashable.COMPLETE-ARB01.zip
ae99fb58db90f2e9872efa48058a069e ./tz.img
3c55565bd6484008f6481568dc1dd49e ./LG-H83020f-Flashable.Modem-ARB01.zip
52b616602ecca40ee59abbd2bb5ae437 ./recovery.img
8d82829dacca5ba614e661de349f479a ./modem.img
43ccab930ead61362515404dcf09281c ./persist.img
a7f68864e6691d5cebd0839b893eb0ba ./LG-H83020f-Flashable.Bootloader-ARB01.zip
d683eb4f9dc5157552d4944e06567704 ./cmnlib.img
98af194b7d9aa8341ad27e148c757322 ./keymaster.img
15bc82584049ec3a7c62d921c2897267 ./factory.img
f99def11c81e1a334d1d50c99619d7dd ./raw_resources.img
eea80db6b255927aa64af28581bed93a ./xbl.img
eea80db6b255927aa64af28581bed93a ./xbl2.img
866cafe48798fe2eab74ab43f7840c96 ./laf.img
304158abb6de7a1cbc92a031b658b246 ./rpm.img
701c7aac129ccee27c95298386fcf958 ./LG-H83020f-Flashable.Boot.zip
67f4acdd417eb34720171038296dbb97 ./msadp.img
6c8272b24bac6356f82091b11909d7f3 ./H83020f_01_0321.kdz
93e5ae0cfad0264ea72ec40857fd9dad ./aboot.img
e014bbf28946a3dbb96a4ad055ea7d49 ./devcfg.img
50ff52f182343404236e56fd5ef7e93b ./sec.img
db7a1ba7ef4d7960ee13274323507cd1 ./cmnlib64.img
FAQ:
Click button below to view FAQ
Q: I don't care about root or TWRP.. do I have to worry about this fuse stuff?
A: Nope, if you don't want root or TWRP just use LG Bridge or LGUP to upgrade to stock 20f and keep it movin'. But you can still root on 10A/D/i/J and 20a.
Q: LGUP isn't working because ________ what should I do?
A: This isn't the LGUP thread. Try the LGUP G5 thread here.
Q: Anti-Rollback 01? What does this mean?
A: It means if you flash 20f you can't flash anything lower than anti-rollback (ARB) v01. 10A was v00. If you manage to flash 10A bootstack (bootloader/modem) after already being on 10D/10i/20a you will brick. If I had to guess... LG/T-Mobile did this to stop people from using the custom 10A TOT that installs TWRP. Just don't flash any 10A files and you're fine (as of Jan 17 2017.. can't predict future builds...)
Q: Why does the boot.img need to be repacked?
A: boot.img is repacked for systemless root. You also need to repack the boot.img to stop TWRP from getting replaced with stock recovery the first time you boot into android after installing a new system/boot. A patch file in the system.img checks the boot.img and if it's 100% stock it builds and flashes a stock recovery image... and this would replace TWRP. So to keep TWRP and keep a stock system.img you just repack the boot.img with either the verity/encryption zip or the boot repacker zip. If you don't care about keeping TWRP none of this matters.
Q: How do I know if /data and /sdcard are encrypted?
A: If you never used TWRP and wiped/formatted data then you have encrypted data. Have TWRP and aren't sure? Boot into TWRP and try to browse /data or /sdcard... if both are empty then you are encrypted. Can you see stuff in /data and /sdcard? Then your data is not safe and not encrypted(but at least you can see files in TWRP, right?...).
Click to expand...
Click to collapse
y u quote OP?
For more G5 info see my All-in-One Thread HERE
Follow me on twitter for future updates on LG-related things - twitter.com/@utoprime
Find this thread helpful? Hit the Thanks button!
Feeling extra generous? Click my name at the top of any post and hit donate or click here.
#TEAMCODEFIRE
Thanks!
Coming from Rooted Stock 20C. Flashed according to TWRP ROOT Install with failed SafteyNet. No problems at all.
Thanks Autoprime, you're the best!!
Thank you. I have been waiting for this.
Sent from my LG-H830 using Tapatalk
Great work, Autoprime, as usual. Much appreciated.......
I'm on h83020a with bootloader unlocked, rooted with supersu 2.7.4 and I have TWRP 3.0.2... If I want H83020f rooted, I can just follow the "B. Stock ROOTED. SafetyNet FAILS." instructions, right? (I will delete the recovery-from-boot.p file just to be sure).
If it's that simple, this is great news!! If I back up "all system apps + user data" in Titanium Backup on H83020a before I install, I suppose I won't be able to restore them on H83020f without problems?
It's a PITA that one cannot boot into TWRP on the LG G5 without wiping/formatting data... Would prefer to do a nandroid backup before wiping all data.
d3th.m0nk3y said:
I'm on h83020a with bootloader unlocked, rooted with supersu 2.7.4 and I have TWRP 3.0.2... If I want H83020f rooted, I can just follow the "B. Stock ROOTED. SafetyNet FAILS." instructions, right? (I will delete the recovery-from-boot.p file just to be sure).
If it's that simple, this is great news!! If I back up "all system apps + user data" in Titanium Backup on H83020a before I install, I suppose I won't be able to restore them on H83020f without problems?
It's a PITA that one cannot boot into TWRP on the LG G5 without wiping/formatting data... Would prefer to do a nandroid backup before wiping all data.
Click to expand...
Click to collapse
Yes it's that simple.
And you can boot into TWRP without wiping data. I assume you're referring to the factory reset screen shown when you boot I to recovery with the hardware buttons? Factory reset only happens of on stock recovery... If TWRP is installed it doesn't actually do the factory reset.
Or you could just boot into TWRP from within Android and skip that screen entirely... adb reboot recovery
autoprime said:
Yes it's that simple.
And you can boot into TWRP without wiping data. I assume you're referring to the factory reset screen shown when you boot I to recovery with the hardware buttons? Factory reset only happens of on stock recovery... If TWRP is installed it doesn't actually do the factory reset.
Or you could just boot into TWRP from within Android and skip that screen entirely... adb reboot recovery
Click to expand...
Click to collapse
Oh, I didn't know that... So I can just boot into TWRP from adb using the "adb reboot recovery" command? That's fantastic! ------------EDIT: That worked of course!! :good::laugh: Awesome... Now I can backup everything before upgrading to H83020f.
Thanks so much for your work!!
EDIT:
Ok... so I went for it. It worked perfectly just as @autoprime said! No problems whatsoever... :good:
First I backed up my apps + data in Titanium Backup and did a Nandroid backup in TWRP, then I placed the "LG-H83020f-Flashable.COMPLETE-ARB01.zip" and the "SR3-SuperSU-v2.79-SR3-20170114223742.zip" on my external sd card. I decided to try to flash the update over the H83020a rom to see if it worked or not.
So... I Renamed the "recovery-from-boot.p" in /system to "recovery-from-boot.bak" and rebooted into TWRP via adb as suggested above (adb reboot recovery) after turning usb debugging mode on in developer mode options of course... In TWRP I chose cancel when asked to enter PIN and on the next screen I swiped when asked if you want to allow system modifications.
Then, just as described above, I chose Install, found the LG-H83020f-Flashable.COMPLETE-ARB01.zip and swiped to confirm/flash.
Then I chose SR3-SuperSU-v2.79-SR3-20170114223742.zip and swiped to confirm/flash.
I did not wipe dalvik or cache. Then I chose reboot --> System and the phone booted up half way, then rebooted again and started updating to H83020f.
So far all my apps and + data seem to be intact. And I am now on H83020f and I am still rooted!!! :victory:
I had to uninstall and reinstall my current icon pack and disable and restart the firewall and they both work as before now, but apart from that... everything looks like it's working exactly like it was before the install.
Thanks again @autoprime!! Awesome job! :good:
Thanks @autoprime , worked just fine as always.
Sorry for my ignorance, but I would like to know the difference between 20a, 20c, 20f, or know what to install on my device since I see that my device says H83010i MM 6.0.1 and I want to install N 7.0 but I do not know which of those It's my device
I'm on 20f already and wanted to install TWRP to get lineageos running, however I'm running into an error when I try flashing TWRP recovery. I get this error "...FAILED (remote: unknown command)".
I'm not sure why. I did OEM bootloader unlock as well as fastboom bootloader unlock, I've installed all different types of USB drivers, LG UP, LG Bridge.. everything. I have no idea what's wrong
Are you trying to install TWRP directly from 20F? You can't. You have to revert to 20A, then run some exploits to install TWRP, then go from there.
Even though the bootloader is unlocked, it's not really. Lots of hoops to jump through to root or flash an alternate recovery.
waylo said:
Are you trying to install TWRP directly from 20F? You can't. You have to revert to 20A, then run some exploits to install TWRP, then go from there.
Even though the bootloader is unlocked, it's not really. Lots of hoops to jump through to root or flash an alternate recovery.
Click to expand...
Click to collapse
Ok i understand. I'll revert to 20a, use exploits, do what i want, and then reinstall 20f modem (and bootloader too? or leave that out?)
You'd want to install basically the complete .zip for 20F once you're done getting TWRP, which includes all the parts except the recovery. The phone really does not like mixing bootloaders, modems, systems.
Then you can decide if you want to root or not. You should also decide if you care about your /data partition being encrypted or not. It'll default to encrypted.
(Obviously LG backup your data first--it's actually a good stock app for real backups without root).
waylo said:
You'd want to install basically the complete .zip for 20F once you're done getting TWRP, which includes all the parts except the recovery. The phone really does not like mixing bootloaders, modems, systems.
Then you can decide if you want to root or not. You should also decide if you care about your /data partition being encrypted or not. It'll default to encrypted.
(Obviously LG backup your data first--it's actually a good stock app for real backups without root).
Click to expand...
Click to collapse
I was actually planning on installing Lineage instead. So would the process be flash 20a -> exploit -> flash TWRP -> flash 20f (minus recovery) -> flash Lineage?
Ahh, that's right. If it were me, I'd update to the latest bootloader/modem. So what you listed above is correct!
When I try to install LG-H83020f-Flashable.COMPLETE-ARB01.zip, TWRP says there is no md5 file found and then says the zip file is corrupt. How can I fix this?
OstapBender7 said:
When I try to install LG-H83020f-Flashable.COMPLETE-ARB01.zip, TWRP says there is no md5 file found and then says the zip file is corrupt. How can I fix this?
Click to expand...
Click to collapse
Redownload with a download manager (ex. Jdownloader 2 beta and/or IDM for PC. ADM for android)
Refresh kdz file link
Refresh kdz file link Please !! leurs:leurs:
---------- Post added at 04:52 PM ---------- Previous post was at 04:42 PM ----------
H83020f_01_0321.kdz => downloads.codefi.re/autoprime/LG/LG_G5/H830/H83020f/H83020f_01_0321.kdz
I plan to make a complete backup of the device so I can restore to stock and receive OTAs in the future. I would like to outline my intended process and hope a more seasoned community member will QC.
Step 1: Boot TWRP and perform a full backup
While in fastboot, run:
Code:
fastboot boot <twrp.img>
Navigate TWRP and perform full backup
Step 2: Root the Device via Magisk (or superSU if you desire):
See other threads for rooting
Step 3: Determine what partition recovery is located on:
Using ADB -> shell, run:
Code:
su
Grant root access and run:
Code:
ls -l /dev/block/*/by-name
Find the partition labelled recovery, note the path
Step 4: Extract the recovery and package into an image file:
Using ADB -> shell, run:
Code:
dd if='/dev/block/mmcblk0p<#>' of='/sdcard/stock_reco.img'
With this, if I want to go back to stock, I can restore the unrooted factory ROM with TWRP and flash the stock recovery with fastboot.
What is the communities thoughts?
I would love this ability too, sadly found nothing on forum that's even close, stock available once you have worked out at which update your bootloader is at.
Why lenovo/motorola decided on different model versions around the world seems crazy, surely easier for production and marketing to make international, especially supplying updates for OS.
Rant over.
sednafx said:
I plan to make a complete backup of the device so I can restore to stock and receive OTAs in the future. I would like to outline my intended process and hope a more seasoned community member will QC.
Step 1: Boot TWRP and perform a full backup
While in fastboot, run:
Code:
fastboot boot <twrp.img>
Navigate TWRP and perform full backup
Click to expand...
Click to collapse
Hi,
If you like "restore to stock and receive OTAs"...
Please, advise that you need to backup all of these partitions: BOOT, SYSTEM, OEM and RECOVERY. Not all TWRP versions will backup all!
Futhermore, if you will like to do a downgrade, then you need to backup all other parts.
I hope this helps to newbies!
manos78 said:
Hi,
If you like "restore to stock and receive OTAs"...
Please, advise that you need to backup all of these partitions: BOOT, SYSTEM, OEM and RECOVERY. Not all TWRP versions will backup all!
Futhermore, if you will like to do a downgrade, then you need to backup all other parts.
I hope this helps to newbies!
Click to expand...
Click to collapse
I would like to backup the full partition table. Please let me know what steps I am missing. TWRP should backup boot, and system. I understand recovery may need done separately.
sednafx said:
I plan to make a complete backup of the device so I can restore to stock and receive OTAs in the future. I would like to outline my intended process and hope a more seasoned community member will QC.
Step 1: Boot TWRP and perform a full backup
While in fastboot, run:
Code:
fastboot boot <twrp.img>
Navigate TWRP and perform full backup
Step 2: Root the Device via Magisk (or superSU if you desire):
See other threads for rooting
Step 3: Determine what partition recovery is located on:
Using ADB -> shell, run:
Code:
su
Grant root access and run:
Code:
ls -l /dev/block/*/by-name
Find the partition labelled recovery, note the path
Step 4: Extract the recovery and package into an image file:
Using ADB -> shell, run:
Code:
dd if='/dev/block/mmcblk0p<#>' of='/sdcard/stock_reco.img'
With this, if I want to go back to stock, I can restore the unrooted factory ROM with TWRP and flash the stock recovery with fastboot.
What is the communities thoughts?
Click to expand...
Click to collapse
OP, did you ever get an answer on this? I'm interested in using block copy as well to pull down a complete stock image.
I have researched this topic and from what I can gather, you have to be rooted to pull the block level data on system etc. I haven’t found a full tutorial to complete what I am trying to do.
sednafx said:
I have researched this topic and from what I can gather, you have to be rooted to pull the block level data on system etc. I haven’t found a full tutorial to complete what I am trying to do.
Click to expand...
Click to collapse
There was an option in TWRP to backup recovery. I haven’t tested if I restore everything... Can I get back OTAs.
I'm interested in doing the same thing. It seems there are no stock images for my XT1683 on NPN25.127.33 and I don't want to risk bricking it by eventually flashing the wrong image and taking a OTA. So the obvious solution would be to backup my own stock image. I've looked around and found the following thread and command:
https://forum.xda-developers.com/showthread.php?t=1758326
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img
I can't be sure, but it would seem this could be used to backup the entire partition set (including OEM as well as the stock recovery and bootloader). Even if there's no root access, one could boot into TWRP from fastboot and issue the command (exactly like OP's step 1). Do you think it would be possible to take this backup, restore it at a later date and still be able to take an OTA with no issues?
I also would like to know this. Or if a stock ROM is available for XT1684 NPNS25.137-33-11 as I've searched and had no luck.
Thanks.