Update - Dec. 15th, 2018: Recently I attempted a couple of freshest ROM installs (update-kindle-37.6.0.5_user_605485120.bin and update-kindle-37.6.2.6_user_626533320.bin), and the device bootloops with the 5.1.2 bootloaders (cycling through the "Amazon" logo - looks like the newest kernel is incompatible with the older bootloaders). Using recovery, I had to sideload 5.1.2 again (which older bootloaders allowed me to do!), and re-root it using these instructions via Kingoroot. As such, the most recent version that I recommend here is update-kindle-37.5.7.9_user_579279320.bin (FireOS 5.4.0.1).
News : The update file for 5.3.1.0 is posted on the Amazon site, so time to upgrade! Note that you cannot get root by downgrading 5.3.1 to 5.1.2 (& Kingroot), because the 5.3.1.0 bootloaders will brick if rolled back (so stay put for now ...) :
http://forum.xda-developers.com/amazon-fire/help/installing-custom-rom-fireos-5-3-1-0-t3418541
Rootless in Seattle ...
[Updated July 16th, 2016]
Flashfire almost replicates TWRP functionality, thus I've significantly re-written this post to include branches for people who managed to keep TWRP from the old days of 5.0.1, and those who have to use Flashfire because of newer bootloaders (and thus lacking TWRP ...). If you want to quickly upgrade (or downgrade ?) your *rooted* FireOS while avoiding potential bricking issues, the post is for you (if you are not rooted yet, and have stock 5.3.1.0, do not attempt to downgrade, it'll brick the Fire !!!).
Before proceeding, remember these IMPORTANT points :
Take a note of your current bootloaders, this will be important later on. If you forgot what version you have, please follow this post to identify it:
http://forum.xda-developers.com/amazon-fire/development/identify-bootloader-version-t3424634
If you disabled the stock launcher via "pm hide", please re-enable it again before the procedure, or install some other launcher as the user app. For example, if you converted Nova or other launcher to a system app, it will disappear upon upgrade, so you need some other launcher operational. Until I fixed Nova, the tablet would freeze at the end of the "optimizing applications" stage because at this stage there was no working launcher (can be fixed by adb command line, but still a bit of a mess)
Turn on Airplane mode, so that you don't "catch" an update right after this upgrade (and before you have a chance to disable it)
A : TWRP Install instructions [if you still have the "good" 5.0.1 bootloaders]
0) install ADB and Fastboot drivers on your PC, and boot into TWRP ( http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548 ):
Code:
adb reboot-bootloader
fastboot boot TWRP_Fire_2.8.7.0.img
1) boot into TWRP and:
do factory reset (skip if don't want to),
flash whatever ROM you want from this post, for example, 5.3.1.0 ( rename *bin to *zip such that TWRP can recognize it):
update-kindle-37.5.7.9_user_579279320.bin
(Previous recommendation - update-kindle-global-37.5.5.2_user_552153420.bin)
flash the attached fire_boot_53820.zip . The objective of this file is to overwrite all the problematic bootloaders after 5.1.x update back to 5.0.1 version (53820 variety). This will allow to go into fastboot and then TWRP just like before.
flash Supersu.zip ( SR5-SuperSU-v2.82-SR5-20171001224502.zip; previous recommendation - 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
B: Flashfire Install instructions [Note that you will have 5.1.2 (or 5.1.1) bootloaders after this procedure]
Given that FlashFire is no longer supported, I recommend version v0.51 with the date hack in order to pass the date check (adb shell; su; busybox date -s "201509221745"). Copy all the necessary files to the local Fire storage, such as /sdcard/upgrade. In Flashfire, chain the following files as ZIP or OTA flashes in one batch (same options in each case, no R/W for /system partition by default):
the OTA file you want renamed to zip, such as this one update-kindle-37.5.7.9_user_579279320.bin
the attached fire_boot_5.1.2-5.4.2_542168620.zip (or fire_boot_5.1.1-5.4.1_541112720.zip). This will replace whatever bootloaders the OTA file has with those from 5.1.2 (or 5.1.1), in order to allow upgrades/downgrades without bricking. Preserving 5.1.2 bootloaders may seem a bit pointless now, but it's still good to freeze these as some hackable bugs may be discovered in the future, so the older bootloaders one has - the higher the chance they have useful bugs ! Again, if you still have 5.1.1 bootloaders, do use fire_boot_5.1.1-5.4.1_541112720.zip here !!! (thanks to Kramar111 for reminding of the rooting trick that works with 5.1.1 bootloaders [fastboot oem append-cmdline "androidboot.unlocked_kernel=true"]
flash Supersu.zip ( SR5-SuperSU-v2.82-SR5-20171001224502.zip; previous recommendation - https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip )
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 )
Pico (Uni) GAPPS for 5.1 :
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
After you've verified everything, hit the "FLASH" button.
See the screenshot below as an example of how the Flashfire screen should look. Note that Flashfire gives no margin of error because it reboot immediately, so if you are flashing a bricking FireOS (relative to your bootloaders), make sure that fire_boot_5.1.2-5.4.2_542168620.zip (or the 5.1.1 version !) is flashed immediately after !!! I've carefully followed this procedure, and verified that the bootloaders do get restored to 5.1.2 version regardless of what was in Amazon's OTA file.
2) reboot to FireOS 5. Verify that SuperSu works.
3) if step 2) fails, you get into working recovery by pressing "Pwr & Vol+". If you still have 5.0.1 bootloaders (getting rare by now ...), then sideload the old 5.0.1 update and root it: http://kindle-fire-updates.s3.amazo...ZjK/update-kindle-37.5.2.2_user_522054520.bin If you have 5.1.2 bootloaders, sideload 5.1.2 instead (the last rootable version as of now) : https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin If you have 5.1.1 bootloaders, sideload 5.1.1 !
4) block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_
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"
}
For clarity, this is for a person that is currently on 5.0.1, correct? This is to go from 5.0.1 to 5.1.1 while retaining root/TWRP, but this will not allow someone that is on 5.1.1 to access TRWP, right?
TallGrassShort said:
For clarity, this is for a person that is currently on 5.0.1, correct? This is to go from 5.0.1 to 5.1.1 while retaining root/TWRP, but this will not allow someone that is on 5.1.1 to access TRWP, right?
Click to expand...
Click to collapse
Indeed, you have to have 5.0.1 so that you can boot into TWRP
copied update to AFH:
https://www.androidfilehost.com/?fid=24269982087012932
MD5: 8dfcc416a0b2c47fe384dd28f2ef18ed
So once we're on this, they cant OTA us to 5.1.1 because we're already on it right? Now 5.1.2 ...
julianpaul said:
So once we're on this, they cant OTA us to 5.1.1 because we're already on it right? Now 5.1.2 ...
Click to expand...
Click to collapse
the last step is to block OTA updates.......sooooo....
So does anyone know what 5.1.1 offers over 5.0.1?
hp420 said:
the last step is to block OTA updates.......sooooo....
Click to expand...
Click to collapse
No i meant even if ota is left enabled, there's no immediate risk.
I will try to make a edited stock 5.1.1 ROM with Root, No Lockscreen Ads, etc.
Sent from my KFFOWI using Tapatalk
TallGrassShort said:
So does anyone know what 5.1.1 offers over 5.0.1?
Click to expand...
Click to collapse
I was wondering that
julianpaul said:
No i meant even if ota is left enabled, there's no immediate risk.
Click to expand...
Click to collapse
Yeah but you had that cliffhanger 5.1.2 ending...
Vlasp said:
I will try to make a edited stock 5.1.1 ROM with Root, No Lockscreen Ads, etc.
Click to expand...
Click to collapse
Sounds very useful
bibikalka said:
With the capture of the new FireOS 5.1.1, these the instructions to install 5.1.1 and keep root and TWRP access.
Click to expand...
Click to collapse
Will this work direct from 5.0.0? I see no reason it shouldn't but just checking.
I'm also curious, does this also work for an unrooted/stock 5.0.0? (a brand new device) Has anyone tried?
sina6002 said:
I'm also curious, does this also work for an unrooted/stock 5.0.0? (a brand new device) Has anyone tried?
Click to expand...
Click to collapse
Seen someone mention on another thread that they've done it.
Which is handy as I've got to talk someone through this on skype later in the week when theirs arrives.
bibikalka said:
With the capture of the new FireOS 5.1.1, these the instructions to install 5.1.1 and keep root and TWRP access.
Install instructions.
0) install ADB and Fastboot drivers on your PC, and boot into TWRP ( http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548 ):
Code:
adb reboot-bootloader
fastboot boot TWRP_Fire_2.8.7.0.img
1) boot into TWRP and:
do factory reset (skip if don't want to),
flash the update from this thread (update-kindle-full_ford-37.5.4.1_user_541112720.bin.zip, unpack bin.zip, rename *bin to *zip such that TWRP can recognize it, say thanks to the poster):
http://forum.xda-developers.com/showpost.php?p=64184649&postcount=46
flash the attached fire_boot_53820.zip
flash Supersu.zip ( https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip )
flash Pico (Uni) GAPPS for 5.1 :
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
2) reboot to 5.1.1. Verify that SuperSu works.
3) if step 2) fails, you get into working recovery by pressing "Pwr & Vol+". You can boot TWRP again, and sideload the old update : http://kindle-fire-updates.s3.amazo...ZjK/update-kindle-37.5.2.2_user_522054520.bin
4) block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_
Click to expand...
Click to collapse
So even after booting this up you can get back to fastboot and use fastboot boot to get back into TWRP?
sina6002 said:
I'm also curious, does this also work for an unrooted/stock 5.0.0? (a brand new device) Has anyone tried?
Click to expand...
Click to collapse
The new devices seem to be coming with 5.0.1 not 5.0.0.
87racer said:
So even after booting this up you can get back to fastboot and use fastboot boot to get back into TWRP?
The new devices seem to be coming with 5.0.1 not 5.0.0.
Click to expand...
Click to collapse
Mine came with 5.0.0 which i bought on black friday. I didn't open the other boxes, but i assume they are the same.
What benefits will I get with an 5.1.1 upgrade?
I have a 5.0.0 version (from before the black friday). Would be grateful to know if the instruction above works for it, cause I can't upgrade to 5.0.1 first anymore.
gad42000 said:
Mine came with 5.0.0 which i bought on black friday. I didn't open the other boxes, but i assume they are the same.
What benefits will I get with an 5.1.1 upgrade?
Click to expand...
Click to collapse
From the release notes on a 5.1.1 tablet:
Blue Shade - Makes everything ugly by removing blue (supposed to be better at night)
FreeTime Web Browser - Browser for kids (limits, curated content, tracking, etc)
Activity Center - More kid stalking, track what the are spending their time on
Curfew - Restrict kids from using tablet even when FreeTime is not in use
bibikalka said:
4) block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_
Click to expand...
Click to collapse
How do you find the system directory in Explorer? All I'm seeing is the internal "sd card" and the actual micro sd card.
Not that I'm expecting a new update in the time it takes me to let it online and download a file browser on the tablet, but seems I'm missing something that could be handy in future. Thanks.
---------- Post added at 08:48 PM ---------- Previous post was at 08:46 PM ----------
87racer said:
So even after booting this up you can get back to fastboot and use fastboot boot to get back into TWRP?
Click to expand...
Click to collapse
Having just done it. Yep, sat in twrp atm.
Pond-life said:
How do you find the system directory in Explorer? All I'm seeing is the internal "sd card" and the actual micro sd card.
Not that I'm expecting a new update in the time it takes me to let it online and download a file browser on the tablet, but seems I'm missing something that could be handy in future. Thanks.
---------- Post added at 08:48 PM ---------- Previous post was at 08:46 PM ----------
Having just done it. Yep, sat in twrp atm.
Click to expand...
Click to collapse
interesting so the 5.0.1 preloader and uboot work just fine with the 5.1.1 system image just not the other way around...think I will just RMA that tablet rather than get SP Flash Tools to work.
sina6002 said:
I have a 5.0.0 version (from before the black friday). Would be grateful to know if the instruction above works for it, cause I can't upgrade to 5.0.1 first anymore.
Click to expand...
Click to collapse
Well you can as you could download the 5.0.1 and install it through twrp, but if it's not needed it's somewhat pointless.
87racer said:
So even after booting this up you can get back to fastboot and use fastboot boot to get back into TWRP?
The new devices seem to be coming with 5.0.1 not 5.0.0.
Click to expand...
Click to collapse
I received one on October 21st that came with 5.0.0, I received one a week October 26th later that came with 5.0.1. That's from Amazon, I suppose ymmv if you got them at BestBuy or elsewhere.
Related
{
"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"
}
I have a Canadian ASUS TF300 purchased from Futureshop. It shipped with WW firmware, and I updated OTA to WW9.4.3.30 before starting this.
I have lost root in the process. But I wasn't keep on keeping it in the first place. I kept all my apps and am now on US10.4.2.9 Jellybean Android 4.1.1. Maybe someone can chip in on how to keep root.
My device is NOT unlocked. Following this procedure requires that you root your device temporarily.
You will end up with JB with one modified binary (su, but with safe system permissions as a result of the rooting process).
This method is very time consuming (1-2 hours), so I don't recommend it for everyone. You need knowledge of ADB to proceed with this.
How To Flash (Unlocked/locked Device)
1) Convert to US9.4.3.30 using the blob:
Download US9.4.3.30 from the ASUS download page here: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T
Open the firmware download package with 7zip or similar, and extract 'blob'.
2) Copy blob into your internal memory (/sdcard/). I used adb push to do this
3) Continue following 'Method 2' from here: http://forum.xda-developers.com/showthread.php?t=1622628
(You probably want to clean up the symlink after you finish this method)
You are now on the stock US9.4.3.30 firmware
4) Perform the official upgrade to the US10.4.2.9 firmware manually
Download US10.4.2.9 from Asus: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Remove any external storage media attached to the device before proceeding.
The downloaded file is to be placed in the root directory of the internal storage (/sdcard). Reboot to install if the prompt to install doesn't come up right away.
(instructions by Bolandk. not tested by me.)
FROM THIS POINT FORWARD, THE INSTRUCTIONS BELOW ARE OBSOLETE AND ARE KEPT HERE FOR FUTURE REFERENCE ONLY
4) Root the firmware using the DebugFS method: http://forum.xda-developers.com/showthread.php?t=1706588
IF YOU WANT TO KEEP ROOT, FOLLOW THIS: http://forum.xda-developers.com/showthread.php?t=1840504
5) Use this method to force the FOTA update (dlpkgfile)
Download dlpkgfile from this thread:
http://forum.xda-developers.com/showthread.php?t=1840397
Follow this: http://forum.xda-developers.com/showthread.php?t=1803090
The difference is that our device does not vibrate. You want to hit 'vol up' right when your device shows any text, and this is within 5 seconds of you pressing the voldown+power combination. If you miss this, you need to recopy 'command' back into /cache/recovery.
6) The update process will start automatically. This takes 20 minutes to complete.
Region conversion instructions
Since ASUS has posted the Jellybean updates for a while now, I thought I'd update this post with instructions to change to another region.
To region convert, you need to download the firmware for the target region. Ideally you want the version you are currently on. I think you may end up losing root in the process, but I don't know a way around that at the moment.
You do not have to be bootloader unlocked to do this.
Extract the xxxUpdateLauncher.zip into the root directory of a microSD card formatted to FAT/FAT32. Then rename the file as EP201_768_SDUPDATE.zip. Reboot into the bootloader (vol - and power), and select the first option (left most square) when the menu comes up. The firmware update will start automatically in this mode.
I converted back from a US to a WW build without wiping using this method.
xaueious said:
I have a Canadian ASUS TF300 purchased from Futureshop. It shipped with WW firmware, and I updated OTA to WW9.4.3.30 before starting this.
Good luck!
Click to expand...
Click to collapse
Do you know of a way to force downgrade from Jelly Bean to ICS 9.4.3.17? I don't have any root access and need to restore it.
This works good it took me a little over an hour
but you lose root and the ability to flash a custom recovery (CWM,TWRP)
Please correct me if I am wrong
I haven't tried it this way yet, but it seems a little easier if someone wanted to try it.
jvanassche said:
Alright, after some work, I finally got this to install on my unlocked device following these steps:
1) If not already on stock, wipe everything and reflash to stock .30 update and reinstall TWRP 2.2.1.3. Be sure to backup before wiping.
2) Download the zip from the OP, and extracted it to a folder on your hard drive.
3) Open META-INF\com\google\android\updater-script in Notepad.
4) Deleted line 3 and 4 of the file. The Line to be deleted should read assert(getprop("ro.product.device") == "EeePad" ||
getprop("ro.build.product") == "EeePad");
5) Create a new zip file containing all of the files you extracted in step 2, including the modified updater-script file, and copy to your device.
6) Reboot into TWRP
7) In TWRP, under mount section, ensure all four mount options are checked, and internal memory is checked at the bottom
8) Flash the zip file you copied in step 5.
9) Reboot, and enjoy your Jelly Beans.
Click to expand...
Click to collapse
Turbojugend said:
I haven't tried it this way yet, but it seems a little easier if someone wanted to try it.
Click to expand...
Click to collapse
Just attempted this but got "install fail"
Its my 1st time creating a zip file so maybe I goofed at it. Used 7zipper.
Sent from my Nexus S 4G using Tapatalk 2
I can confirm after slaving away at this method. It does work and I am now on Jelly Bean.
Zadeis said:
I can confirm after slaving away at this method. It does work and I am now on Jelly Bean.
Click to expand...
Click to collapse
You still have root or lost after flash the rom?
wonsanim said:
You still have root or lost after flash the rom?
Click to expand...
Click to collapse
You will lose root without a modified dlpkgfile update-script.
wonsanim said:
You still have root or lost after flash the rom?
Click to expand...
Click to collapse
Unfortunately, no. I used ota root keeper and everything only for it to not work in the end...
Zadeis said:
Unfortunately, no. I used ota root keeper and everything only for it to not work in the end...
Click to expand...
Click to collapse
I'm in the same boat. I backed up root with the OTA Rootkeeper, but after the upgrade, it it doesn't restore root.
I did read in another thread, that some people were successful in restoring root in JB with OTA Rootkeeper, but they had SuperSU installed. Of course, I came across that little tidbit right in the middle of the upgrade
Actually, i'll what I said back. I actually managed to restore my root. I'm not sure what I did differently, but I have thankfully have root again!
i was able to restore root too.
FYI, this worked for me with an unlocked bootloader.
Extremely happy right now. Thanks for this.
Works great with unlocked bootloader, thanks again.
Sorry but what is the point if you already unlocked bootloader/root/install custom recovery , and now you tried to flash back to stock to get OTA update ?
- You tried to root/ flash custom rom at first place, and now you back to stock to get OTA update and you can't root once you update to 4.1.1. More important, 3-4 peoples already get their tab bricked when they tried to flash CWM after Jelly bean update as they attempt to root their device again. And now they screw up cause they can get warranty from ASUS. Why don't you guys wait couple days when developers make a new custom roms based on official 4.1.1 updated so yous just easily flash through recovery. Just my 2 cents :highfive:
sorta works
It worked sort of.
My tf300 was already "unlocked"
But the instructions didnt work exactly.
Here is what I had to do:
1. Use TWRP recovery to install the ICS official rom from ASUS
2. Use the idcrysis method for rooting after initial setup (failed the first time but worked the second try after rebooting)
3. put the dlpk file on the root of the tablet from: http://forum.xda-developers.com/showthread.php?t=1840397
4. Root the firmware using the DebugFS method: http://forum.xda-developers.com/show....php?t=1706588
5. copy "dlpkgfile" into /cache/ directory
6. create the file called "command" under /cache/recovery/
7. write this statement in the file /cache/recovery/command (without qoutes) "--update_package=/cache/dlpkgfile"
Dunno why it didnt work for me the right way but this is how I got it to work. Not root doesnt work but I can live with that till I read about rooting Jelly Bean tomorrow when I wake up.
If anyone else has issues forcing the jelly bean update these steps I did worked. I am definetely NOT a programmer, just had to follow steps from multiple posts. I kind of wished I could relock the bootloader again. This was such a pain in the rear!
OTA and Fully Removied Moded Binary
xaueious said:
I have a Canadian ASUS TF300 purchased from Futureshop. It shipped with WW firmware, and I updated OTA to WW9.4.3.30 before starting this.
I have lost root in the process. But I wasn't keep on keeping it in the first place. I kept all my apps and am now on US10.4.2.9 Jellybean Android 4.1.1. Maybe someone can chip in on how to keep root.
My device is NOT unlocked. Following this procedure requires that you root your device temporarily.
You will end up with JB with one modified binary (su, but with safe system permissions as a result of the rooting process).
This method is very time consuming (1-2 hours), so I don't recommend it for everyone. You need knowledge of ADB to proceed with this.
How To Flash (Unlocked Device)
0) Download dlpkgfile from this thread:
http://forum.xda-developers.com/showthread.php?t=1840397
1) Convert to US9.4.3.30 using the blob:
Download US9.4.3.30 from the ASUS download page here: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T
Open the firmware download package with 7zip or similar, and extract 'blob'.
2) Copy blob into your internal memory (/sdcard/). I used adb push to do this
3) Continue following 'Method 2' from here: http://forum.xda-developers.com/showthread.php?t=1622628
(You probably want to clean up the symlink after you finish this method)
You are now on the stock US9.4.3.30 firmware
4) Root the firmware using the DebugFS method: http://forum.xda-developers.com/showthread.php?t=1706588
IF YOU WANT TO KEEP ROOT, FOLLOW THIS: http://forum.xda-developers.com/showthread.php?t=1840504
5) Use this method to force the FOTA update (dlpkgfile)
Follow this: http://forum.xda-developers.com/showthread.php?t=1803090
The difference is that our device does not vibrate. You want to hit 'vol up' right when your device shows any text, and this is within 5 seconds of you pressing the voldown+power combination. If you miss this, you need to recopy 'command' back into /cache/recovery.
6) The update process will start automatically. This takes 20 minutes to complete.
Good luck!
Edit:
If you are unlocked, you might as well wait for a repacked ROM.
Click to expand...
Click to collapse
I was wondering if you do a full reset, is the device OTA Eligible for future updates and are you able to remove the moded binary by doing a full reset.
does this have any side effects, eg no more ota or is the us version crippled because of patents?
OK....can someone confirm this for me.
I am stock,locked and rooted...my OTA failed due to some frozen apps.
So I would take the dlpkgfile and place it in /cache
I would then place the "command"file from the link in #5 and place that in c/cache/recovery
Then reboot into recovery and it should install on it's own?
Can anyone confirm this for me? Anyone locked have success with this process?
Also anyone have the dlpkgfile they can mirror...the original one generated too much traffic and is no longer available.
turdbogls said:
OK....can someone confirm this for me.
I am stock,locked and rooted...my OTA failed due to some frozen apps.
So I would take the dlpkgfile and place it in /cache
I would then place the "command"file from the link in #5 and place that in c/cache/recovery
Then reboot into recovery and it should install on it's own?
Can anyone confirm this for me? Anyone locked have success with this process?
Also anyone have the dlpkgfile they can mirror...the original one generated too much traffic and is no longer available.
Click to expand...
Click to collapse
dlpkgfile
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.
Update2, Feb 13, 2016: Great news!!! FireOS 5.1.1 has been captured, upgrading from 4.5.5.1 to 5.1.1 with root works fine (already tested by fizz1234). For people coming from 4.5.5.1 the keyword is 5.2.2u3_stock_recovery_uboot.zip , this is what you use with the update instructions : http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Just competently follow fizz1234 lead and you won't risk any bricking:
http://forum.xda-developers.com/showpost.php?p=65311612&postcount=233
Original post
There are great news out there that the latest Kingroot can acquire root on 4.5.5.1 :
http://forum.xda-developers.com/showpost.php?p=65208545&postcount=280
http://forum.xda-developers.com/showpost.php?p=65211912&postcount=282
http://forum.xda-developers.com/showpost.php?p=65212042&postcount=283
This most likely can also root 4.5.4 and 4.5.5 (if anybody still has those).
After you get root, disable OTA : [ in ES Explorer rename /system/priv-app/DeviceSoftwareOTA.apk to *apk_ ]
To get TWRP after rooting, please follow the guide below, once in TWRP, you are done, reboot back to system :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
(if you have rooted 4.5.5.1, only try this if you still have warranty, since we don't know if 4.5.3 bootloaders would run after 4.5.5.1)
( thanks to tolchuk , this way to install TWRP is now tested, and works!!!)
A note on TWRP. Do not keep updates open with installed TWRP [i.e. unblocked /system/priv-app/DeviceSoftwareOTA.apk], what will happen is that the new OS will install, but the recovery will remain un-updated (now unbootable TWRP), and so you'll get a working device but with no way to do any OS upgrades or downgrades.
For 4.5.5.1, there are no upgrade paths yet to Lollipop due to the bricking issues until we capture 5.1.1 (it's possible that the oldest update files might work without bricking [5.2.0, early 5.2.2], but it's generally recommended to wait ):
http://forum.xda-developers.com/fire-hd/general/psa-fireos-5-1-1-wild-t3304133
If you want to hang out @ 4.5.5.1 (while waiting for Lollipop), please follow this guide after step 2b (after TWRP is working) :
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
woot
Sent from my d2spr using Tapatalk
TWRP Successfully installed 4.5.5.1
Hi bibikalka,
I have successfully installed TWRP on 4.5.5.1 using your instructions from your thread.
I did it manually using Option B:
{
"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"
}
I'm going to install GAPPS next. (edit: removed question about upgrading after further reading)
Thank you for all your help.
tolchuk said:
Hi bibikalka,
I have successfully installed TWRP on 4.5.5.1 using your instructions from your thread.
I did it manually using Option B:
I'm going to install GAPPS next. (edit: removed question about upgrading after further reading)
Thank you for all your help.
Click to expand...
Click to collapse
OK, excellent news !!! So 4.5.3 + TWRP are confirmed !!! Thanks for daring !
Now stay put until 5.1.1 is captured since there is no reason to risk bricking with the earlier Lollipop versions.
Root confirm working on my HD6 running 4.5.5.1
I'll try flash GApps now, what package of GApps are you recommended?
thanks for the tut
I can add another confirmation that TWRP does work from OTA 4.5.5.1 after rooting via kingroot 4.8 and flashing TWRP via method B using ADB.
Maybe later I will use some of my horrible Java knowledge to automate the ADB method. Will give me another project instead of my lightweight HTTP server.
kenshin1388 said:
I can add another confirmation that TWRP does work from OTA 4.5.5.1 after rooting via kingroot 4.8 and flashing TWRP via method B using ADB.
Maybe later I will use some of my horrible Java knowledge to automate the ADB method. Will give me another project instead of my lightweight HTTP server.
Click to expand...
Click to collapse
What's wrong with the automation via Gscript as proposed in that TWRP post ? It works really well, I am using it all the time!
Nothing, I just know people like their options. As well as I would love to expand my knowledge in programming little by little.
I've worked on a simple chat room for the past 2 years simple because I've had no project ideas lol.
Edit: Okay just looked and it seems you must put all files in place for gscript and such. I was talking about a simple pre-packaged program simple to automate the entire process of placing the needed files and flashing everything for you. Something you can start up, it will check comparability, then if able you can click "flash TWRP" to start the process.
kenshin1388 said:
Nothing, I just know people like their options. As well as I would love to expand my knowledge in programming little by little.
I've worked on a simple chat room for the past 2 years simple because I've had no project ideas lol.
Edit: Okay just looked and it seems you must put all files in place for gscript and such. I was talking about a simple pre-packaged program simple to automate the entire process of placing the needed files and flashing everything for you. Something you can start up, it will check comparability, then if able you can click "flash TWRP" to start the process.
Click to expand...
Click to collapse
Ok, thanks! I just was not sure why it seems that Gscript looks scarier to people than other options. Indeed, a PC script could do the same thing, if one desires (I believe DoLooper was looking at something similar). Another idea is to have the script preserve the bootloaders that are on the device, and make a flashable zip out of those. Then it's super easy to return to what the device had before everything was replaced by 4.5.3 bootloaders + TWRP.
Guys, I am on 5.01 dev preview by following this guide http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408
I wanted to try to downgrade to OS4 and see if I can get 5.1.1, after requesting downgrade from my amazon account what do I need to do?
When you say downgrade to OS4 using TWRP,which zip file am I exactly flashing ?
After flashing OS4 where do I request OS5 update? from amazon account or by hitting "update" in the system update screen on the fire tablet ?
TIA
Hey, I know it is risky, but I really want to update to Fire OS 5, so could you suggest the safest way to flash? Thank alot.
Sent from my D6653 using Tapatalk
Antonntminh said:
Hey, I know it is risky, but I really want to update to Fire OS 5, so could you suggest the safest way to flash? Thank alot.
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
If you insist ...
There a slight chance that the earliest 5.2.0 bootloaders won't brick after 4.5.5.1 . On the other hand, they may brick just the same as the 5.2.2u2 bootloaders.
So follow instructions from here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
But, in Step 1).3 flash 5.2.0_stock_recovery_uboot.zip from post #2 instead of 5.2.0_stock_recovery_only.zip
This will replace the bootloaders with 5.2.0 version, which may (or may not) take off after 4.5.5.1
Please ensure that you have valid warranty !!! You've been warned
Thanks, I will save this for later if no guide for safe update to OS 5,
Btw, do we have any eta for the flash guide from 4.5.5.1 to 5.x?
Thanks
I just want to clarify something. If I'm currently on 4.5.5.1 and want to root my device, do I then NEED to disable OTA updates and install TWRP to proceed with installing OS 5? Or can I just leave on auto updates so I can get updated to OS 5 via OTA? Or will doing the OTA to OS 5 remove root? If I want to install Gapps do I need TWRP?
jleonard711 said:
I just want to clarify something. If I'm currently on 4.5.5.1 and want to root my device, do I then NEED to disable OTA updates and install TWRP? Or can I just leave on auto updates so I can get updated to OS 5 via OTA? Or will doing the OTA to OS 5 remove root?
Click to expand...
Click to collapse
Well, 5.1.1 has been already captured, so no need to try to grab it anymore :
http://forum.xda-developers.com/fire-hd/general/psa-fireos-5-1-1-wild-t3304133
If you auto-update, you'll get Lollipop, but without root. You'll have to downgrade to 4.5.3 to root, but you already have a rootable 4.5.5.1, so why no start here ? Therefore you actually do want to install TWRP, since that's how you install Lollipop with root :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
FireOS 4 is really resilient about OTA, once it starts downloading, it'll continue even after the OTA program is disabled. I recommend you do a factory reset to kill that right now. Then you root, install TWRP, and install Lollipop manually.
bibikalka said:
Well, 5.1.1 has been already captured, so no need to try to grab it anymore :
http://forum.xda-developers.com/fire-hd/general/psa-fireos-5-1-1-wild-t3304133
If you auto-update, you'll get Lollipop, but without root. You'll have to downgrade to 4.5.3 to root, but you already have a rootable 4.5.5.1, so why no start here ? Therefore you actually do want to install TWRP, since that's how you install Lollipop with root :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
FireOS 4 is really resilient about OTA, once it starts downloading, it'll continue even after the OTA program is disabled. I recommend you do a factory reset to kill that right now. Then you root, install TWRP, and install Lollipop manually.
Click to expand...
Click to collapse
Okay, so the only way to retain root while upgrading to Lollipop is to use TWRP? And I did already do a factory reset after I saw that 5.0.1 had started downloading because I wanted to root and then capture the file, but then literally right after I posted here I saw that someone else posted a few hours earlier that they had just captured it.
I have tried. Installing twrp with flashify says it flashed but won't go into recovery.king root worked fine. I am lost a little running 4.5.5.1 .there are a lot of tutorials not sure which one to follow any help appreciated. Thanks
Teilky said:
I have tried. Installing twrp with flashify says it flashed but won't go into recovery.king root worked fine. I am lost a little running 4.5.5.1 .there are a lot of tutorials not sure which one to follow any help appreciated. Thanks
Click to expand...
Click to collapse
You are not follow the guide properly, it use a different method to get twrp after rooting using kingroot, does not use flashify. Read the guide again and you will know.
Sent from my D6653 using Tapatalk
Teilky said:
I have tried. Installing twrp with flashify says it flashed but won't go into recovery.king root worked fine. I am lost a little running 4.5.5.1 .there are a lot of tutorials not sure which one to follow any help appreciated. Thanks
Click to expand...
Click to collapse
Antonntminh said:
You are not follow the guide properly, it use a different method to get twrp after rooting using kingroot, does not use flashify. Read the guide again and you will know.
Click to expand...
Click to collapse
Indeed! The problem with Flashify in 4.5.5.1 is that the bootloaders have not been replaced with the 4.5.3 version. That's what post #2 is for in the guide below! Follow the guide, and you will do fine :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
bibikalka said:
Indeed! The problem with Flashify in 4.5.5.1 is that the bootloaders have not been replaced with the 4.5.3 version. That's what post #2 is for in the guide below! Follow the guide, and you will do fine :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
So I was thinking for unrooted newbies coming from OS 4.5.4, 4.5.5 (if rootable without downgrading) and 4.5.5.1 it would be safer to go ahead and install TWRP on rooted device so if there's any problem with bootloader files, they can back out and still have TWRP.
But sounds like to install TWRP they must downgrade to 4.5.3 for the bootloaders. So that means either use post #2 method (no TWRP on device) or do extra step of downgrading. IDK. I worry about them. (I heart newbies)
Obviously, the brain's a little mushy tonight. The same is true for 4.5.4/.5 if they're rootable with latest kingroot, right? TWRP can't be installed on those with Flashify either cuz of need for 4.5.3 bootloaders. Thanks!EDIT @bibikalka: NVM. Just lost it for awhile. Guess I'll let them take their lives in their hands and dd 4.5.3 bootloaders and TWRP, hoping they got the right recovery_only or recovery_uboot on board with the update. (Dang, Amazon does not make this easy! It's like they have no sympathy for us at all!)
EDIT2: OH, COOL! Missed this crucial line: "To get TWRP after rooting, please follow the guide below, once in TWRP, you are done, reboot back to system." Works nicely. All's well!
Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"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"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.
If you could provide us the guide to root and come back to twrp I would be extremely happy
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.
y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.
can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!
Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.
I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.
This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.
I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.
Having tried many other ways, I got it done with this instruction.
Thank you!
marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.
Hi Guys,
So, I spend a few hours reading many posts regarding recovery of the Fire Stick 4K.
I'm in the infinite boot stage and trying to reset to the factory settings after Google Services fu*** up everything.
What I tried:
- adb connection from MacBook
- keyboard recovery
ADB Method Issues
When I connect via adb I get Device Unauthorized and don't really know what to do next. I tried to run fastboot but it stuck on Waiting for any device...
Screenshots:
{
"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"
}
Keyboard Method Issues
I tried the combination of Alt+I+PrintScr many times. None of the sources specifies if I should hold the buttons or keep pressing them on/off during the boot (eg 15x) or at which point I should start or finish pressing. So success here either.
I also tried to use remote but every source shows different buttons to press. Power + Volume Up, Middle Button + Arrow RIght etc.
What should I try next, I'm on OSX?
spyderdsn said:
What should I try next
Click to expand...
Click to collapse
Here is the unbrick thread.
Ok, so I need Windows PC to start with...any other options?
spyderdsn said:
Ok, so I need Windows PC to start with...any other options?
Click to expand...
Click to collapse
You can use the iso listed in that thread to do the unbricking and you will be left with a firestick that boots to twrp . Then you can follow this thread: https://forum.xda-developers.com/fi...ewbie-guide-how-to-unlock-bootloader-t4015273 . Good luck
brick00444 said:
You can use the iso listed in that thread to do the unbricking and you will be left with a firestick that boots to twrp . Then you can follow this thread: https://forum.xda-developers.com/fi...ewbie-guide-how-to-unlock-bootloader-t4015273 . Good luck
Click to expand...
Click to collapse
From what I see this is all custom firmware. I would like to restore to factory box standard. There is so many steps to unlock the device. What should I do to restore original firmware after twrp?
spyderdsn said:
From what I see this is all custom firmware. I would like to restore to factory box standard. There is so many steps to unlock the device. What should I do to restore original firmware after twrp?
Click to expand...
Click to collapse
I'm almost sure there is a factory rom posted here somewhere. Just use that instead of the rbox rom.
A good reminder to everyone, don't try anything with your device with debugging disabled.
spyderdsn said:
From what I see this is all custom firmware. I would like to restore to factory box standard. There is so many steps to unlock the device. What should I do to restore original firmware after twrp?
Click to expand...
Click to collapse
It isn't a cfw, but the stock recovery gets replaced during the unlock. Therefore the stock update app in fireOS won't work as expected, you need to use TWRP recovery and do all updates manually.
brick00444 said:
You can use the iso listed in that thread to do the unbricking and you will be left with a firestick that boots to twrp . Then you can follow this thread: https://forum.xda-developers.com/fi...ewbie-guide-how-to-unlock-bootloader-t4015273 . Good luck
Click to expand...
Click to collapse
So the steps in other post are not exactly clear as I'm using the iso
HTML:
https://github.com/amonet-kamakiri/fireiso/releases
.
I run the ISO from USB stick on my MacBook and what do I do next I have two opinions Default & Load to Memory...do I have to have firesick connected at this point...with the foil in it? Is there any step by step for the ISO setup? Can I use MacBook to rin the ISO at all?
Thanks
spyderdsn said:
So the steps in other post are not exactly clear as I'm using the iso
HTML:
https://github.com/amonet-kamakiri/fireiso/releases
.
I run the ISO from USB stick on my MacBook and what do I do next I have two opinions Default & Load to Memory...do I have to have firesick connected at this point...with the foil in it? Is there any step by step for the ISO setup? Can I use MacBook to rin the ISO at all?
Thanks
Click to expand...
Click to collapse
I don't own a macbook but I would think you can because you have to boot to the usb stick and I just use the default option. Wait until you see the desktop. Then go to the internet and look up the unlock thread. You may need to have an ethernet cord plugged into your mac to access the internet (my wifi doesn't work in the iso).
1. Download kamakiri-mantis-v1.2.zip from the link in the original thread.
2. Extract the kamakiri-mantis-v1.2.zip somewhere you will remember. I extract to desktop.
3. Open the kamakiri-mantis-v1.2 folder and then open the kamakiri folder and right click inside that folder and choose open terminal.
4. enter this command in terminal " ./bootrom-step.sh " minus the quotes and click enter. It will say something to the effect of "waiting for device".
5. Short the correct point to the tin casing. It looks like you are shorting it correctly by your pic.
6. Connect the stick to your computer (while keeping it shorted).
7. The script should tell you to release the short and hit enter,. Just pull the tinfoil off the stick . Then click enter (after removing short).
It will take awhile to finish so if it looks like it stalled out give it time.
8. When it is finished enter the command : " ./fastboot-step.sh " and click enter.
9. It will now reboot into TWRP.
10. You can now install the rom. If you don't know how you can follow this guide "https://forum.xda-developers.com/fire-tv/orig-development/newbie-guide-how-to-unlock-bootloader-t4015273" .
Hopefully this helps you. Anyone can add to it or correct it if I missed or forgot something.
Thanks guys for the help. I managed to unbrick my Firestick 4K. and after brick00444 steps I followed this steps:
HTML:
adb push <your download location you decided earlier here>/mantis-6.2.6.8-rooted_r1.zip / sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.8-rooted_r1.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
Worth mentioning. Since I used Mac I downloaded https://unetbootin.github.io/ to do the fat32 bootable stick. The stick runs to the menu but is not able to load Linux. I had to find Windows 10 machine and use https://rufus.ie/ to install the iso and everything worked. All other steps I followed brick00444
My Firestick did not had enough space to push the room zip above so I used Adblink http://www.jocala.com/ to remove some apps.
One more question.
I decided not to block amazon update services via adb. At the moment I’m on Fire OS 6.2.7.1. and fire stick is downloading some updates. I only wanted to unbrick the device not root. Can I apply the update on the top of mantis? Would this work. I’m happy to have stock. At the moment download kind of stuck on downloading system components 70%.
Thanks for your help.
spyderdsn said:
One more question.
I decided not to block amazon update services via adb. At the moment I’m on Fire OS 6.2.7.1. and fire stick is downloading some updates. I only wanted to unbrick the device not root. Can I apply the update on the top of mantis? Would this work. I’m happy to have stock. At the moment download kind of stuck on downloading system components 70%.
Thanks for your help.
Click to expand...
Click to collapse
Only app updates are working, all OS updates (reboot to stock recovery required) won't work.
Sus_i said:
Only app updates are working, all OS updates (reboot to stock recovery required) won't work.
Click to expand...
Click to collapse
The sick has been updated now. The update took whole night and it has downloaded 1GB of stuff as my storage was very low at the time. Now I have the latest update and everything seems to work fine.
Sus_i said:
Only app updates are working, all OS updates (reboot to stock recovery required) won't work.
Click to expand...
Click to collapse
Ok I noticed now when I power off the device and run again I get the recovery mode and reboot after that everything is fine until I power off the stick. What should I do to prevent this?
spyderdsn said:
Ok I noticed now when I power off the device and run again I get the recovery mode and reboot after that everything is fine until I power off the stick. What should I do to prevent this?
Click to expand...
Click to collapse
It's like I said, I guess there is a (partial or full) fireOS update pending
The OTA-update app downloads the update to /cache and place also some recovery commands for the stock recovery.
This is why your stick boots into recovery.
The stick will do that again and again and again, until the update is installed (won't work without the stock recovery).
Take a look on /cache with TWRP. There should be the latest update for your stick (it's a .bin file). In case it is a full update (~600MB in size), rename that file to zip and flash/install it with TWRP. Make sure you don't flash one of the smaller 'partial' updates (If there is a smaller update bin file, delete it... then the stick will download a full bin). After the install, wipe cache, reboot and your stick should be on the latest OS version. You have to do this erverytime you see that the stick boots into recovery
Another option, disable updates and keep the OS version on the stick (for now).
Code:
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.device.software.ota
But for this option you need magisk installed...
Sus_i said:
It's like I said, I guess there is a (partial or full) fireOS update pending
The OTA-update app downloads the update to /cache and place also some recovery commands for the stock recovery.
This is why your stick boots into recovery.
The stick will do that again and again and again, until the update is installed (won't work without the stock recovery).
Take a look on /cache with TWRP. There should be the latest update for your stick (it's a .bin file). In case it is a full update (~600MB in size), rename that file to zip and flash/install it with TWRP. Make sure you don't flash one of the smaller 'partial' updates (If there is a smaller update bin file, delete it... then the stick will download a full bin). After the install, wipe cache, reboot and your stick should be on the latest OS version. You have to do this erverytime you see that the stick boots into recovery
Another option, disable updates and keep the OS version on the stick (for now).
Code:
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.device.software.ota
But for this option you need magisk installed...
Click to expand...
Click to collapse
Actually you don't need Magisk to disable packages. Input disable-user after putting adb shell and the package can disable without root. Only works on Fire OS 6 and above
theflashfromthecw said:
Actually you don't need Magisk to disable packages. Input disable-user after putting adb shell and the package can disable without root. Only works on Fire OS 6 and above
Click to expand...
Click to collapse
Ok so if I understood this correctly. If I don’t bother with the updates for 1-2years. All I do is to delete the update files from the temp folder and prevent the updates by running this commands and I’m good to go.
spyderdsn said:
Ok so if I understood this correctly. If I don’t bother with the updates for 1-2years. All I do is to delete the update files from the temp folder and prevent the updates by running this commands and I’m good to go.
Click to expand...
Click to collapse
Yes and its all preferred to rename otacerts.zip to otacerts.zip.bak in TWRP by mounting the system as read write and hovering over to system/etc/security and you'll see otacerts.zip. The otacerts is certifying the update that's being rolled out properly and since you renamed it to .bak, you can no longer have it applying the update. It still will update but not apply it if you do end up keeping devicesoftwareota. Only disable the override and leave the rest alone for factory reset reasons because it needs the devicesoftwareota enabled to go through the wizard
theflashfromthecw said:
Yes and its all preferred to rename otacerts.zip to otacerts.zip.bak in TWRP by mounting the system as read write and hovering over to system/etc/security and you'll see otacerts.zip.
Click to expand...
Click to collapse
Personally, as soon as system modifications come to mind, I preffer a magisk install, just to avoid verity issues.
but renaming just one zip on system won't trigger dm-verity I guess!?
Sus_i said:
Personally, as soon as system modifications come to mind, I preffer a magisk install, just to avoid verity issues.
but renaming just one zip on system won't trigger dm-verity I guess!?
Click to expand...
Click to collapse
It won't. Fire TV devices don't have dm verify at all and it's safe to rename the zip however you want. Because of this, Amazon doesn't have oem unlock and a setting to enable it, there's no official way for the device to check for dm verify and because the bootloader unlock isn't modified to have its own recovery. I have an LG unlocked device that supports oem and after I unlock it, it tells me to relock the bootloader since the manufacturer allowed my device to be oem unlocked.