Database Develop

[DISCONTINUED][STOCK][LOCKED] Safestrap v4.0.1

***PLEASE UNLOCK YOUR BOOTLOADER INSTEAD. ***
*** IF ANY OF THE INFORMATION ON THIS THREAD IS MISUSED IT CAN RESULT IN A BRICKED DEVICE ***
Introduction
- BEFORE PROCEEDING READ THROUGH CAREFULLY, IF THERE IS ANY DOUBT THEN ASK BEFORE PROCEEDING
- Safestrap provides TWRP like recovery capabilities for locked devices.
- This is based on the original work of Hashcode.
- This is for Apollo and Thor devices only.
Known Issues
- Secondary slots boot, but the WiFi module does not load
- Since the secondary slots work but have no WiFi, you will need to flash Nexus v4 to the stock slot for now
Compatible ROMS
- HDX Nexus ROM v4
- CM-11
- Fire Nexus ROM
Prerequisites for Installation
- You must be on FireOS stock firmware 4.5.2, 4.5.3, 4.5.4, 4.5.5 or 4.5.5.1 <- Please confirm this before proceeding <-
- You must have root access
Installation
- Install the app
- Grant root access if needed
- Read user agreement and accept to proceed
- Then click install recovery
- When recovery is installed click reboot to recovery
- You should eventually end up in safestrap recovery.
Download
*** Please do NOT create any mirrors ***
- Safestrap for THOR
- Safestrap for APOLLO
Thanks to my Testers
- Davey126
- kudoz83
- lekofraggle
- zamtang
- paul26rem
XDA:DevDB Information
Safestrap KK, Device Specific App for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
Version Information
Status: Stable
Current Stable Version: 4.0.1
Stable Release Date: 2015-06-18
Created 2015-06-18
Last Updated 2019-10-02

Reserved

Is there a possibility of running cm 12 in this recovery?

paul26rem said:
Is there a possibility of running cm 12 in this recovery?
Click to expand...
Click to collapse
- Not at the moment and probably not likely.
- If amazon release a FireOS based on lollipop and we get root then yes maybe.

ggow said:
- Not at the moment and probably not likely.
- If amazon release a FireOS based on lollipop and we get root then yes maybe.
Click to expand...
Click to collapse
Although I prefer AOSP/Nexus the next logical question would be CM11 as it shares common roots with FireOS v4 / Nexus v4 and at present does not require an unlocked bootloader. Actually, not sure why anyone would opt for CM11 over Nexus on HDX given the status of the two roms. Don't get me wrong - CM is great and has some nice built in functionality (all of which is obtainiable via Xposed on Nexus) but the CM11/CM12 implementations still have a few issues with the HDX variants.

Davey126 said:
Although I prefer AOSP/Nexus the next logical question would be CM11 as it shares common roots with FireOS v4 / Nexus v4 and at present does not require an unlocked bootloader. Actually, not sure why anyone would opt for CM11 over Nexus on HDX given the status of the two roms. Don't get me wrong - CM is great and has some nice built in functionality (all of which is obtainiable via Xposed on Nexus) but the CM11/CM12 implementations still have a few issues with the HDX variants.
Click to expand...
Click to collapse
I agree. Don't get me wrong, I love cm, but If you want a stable Rom, Nexus is where it's at.

Hi, I used your safetrap version on fire OS 4.5.2 rooted, when I flash rom nexus 4.0.1 on secondary slot rom, It booted greatly! But as you said, it haven't wifi module, but when I flash it in stock slot, successfully, but it only boot to splash screen and no more, do you know my error? Please help me, thanks!
One more thing, I use fire OS 14.4.5.2.2004220, not 2004120, nothing different, right?

thuyrs said:
Hi, I used your safetrap version on fire OS 4.5.2 rooted, when I flash rom nexus 4.0.1 on secondary slot rom, It booted greatly! But as you said, it haven't wifi module, but when I flash it in stock slot, successfully, but it only boot to splash screen and no more, do you know my error? Please help me, thanks!
One more thing, I use fire OS 14.4.5.2.2004220, not 2004120, nothing different, right?
Click to expand...
Click to collapse
Can you get into Safestrap recovery? If so try a 'factory reset' located under the 'wipe' option and then reboot. If that does not work return to Safestrap recovery and perform an 'advanced wipe'. Check all of the partitions (Dalvik Cache, Data, Cache, System). After wiping reinstall Nexus v4 and gaps from within Safestrap and then reboot.
A few cautions/notes:
- make sure you are working with the correct slot!
- make sure you perform the 'factory reset' from safestrap recovery - not the native Amazon recovery built into your Kindle
- gaps is important for proper operation of Nexus v4. Some low level functions (eg: the home button) do not work correctly if gaps is not flashed immediately after Nexus v4
Please post the results to others can learn from your experience. Thanks!

Hi, after I wiped everything and reinstall to slot stock, it booted, and Wifi module worked correctly, thanks for your help!

hi
does ur version of stock 4.5.2 that u attached here already rooted? or do i have to towelroot it?
thx

loco09 said:
hi
does ur version of stock 4.5.2 that u attached here already rooted? or do i have to towelroot it?
thx
Click to expand...
Click to collapse
Flash SuperSU after and you have root access.
Also you will need to block ota updates so do not enable WiFi until you have done so.
EDIT: I have just added a note to the OP about this.
Sent from my Nexus 6 using Tapatalk

I run HDX 7in ver 3.2.8 rolled back by Amazon CS with OTA blocking included, with Safestrap and Nexus 1.0.1. Why will I need to update to this and how do I do it safely?

hfpop said:
I run HDX 7in ver 3.2.8 rolled back by Amazon CS with OTA blocking included, with Safestrap and Nexus 1.0.1. Why will I need to update to this and how do I do it safely?
Click to expand...
Click to collapse
You are in a tough situation given Amazon CS performed the 3.2.8 rollback and OTA is apparently blocked using an unknown method (likely at the Amazon servers but can't be sure).
Options as follows:
1) Contact Amazon CS and request an upgrade to 4.5.2. However, they will likely upgrade to 4.5.4 which is unrootable at present. You would then need to manually rollback to 3.2.8 followed by a manual upgrade to 4.5.2. All this involves risk with the consequence being a bricked device if things go wrong.
2) Attempt to manually update to 4.5.2 which may or may not work given the OTA block. There is less risk but the consequence of a bad upgrade is equally severe (bricked tablet).
3) Stay on FireOS 3.2.8, Safestrap v3.7.x and Nexus 1.0.1 for now. Better/safer upgrade options will likely evolve with time. Nexus 1.0.1 remains quite serviceable for all but the newest applications especially when combined with Xposed Framework and Gravitybox.
I strongly advise option #3 unless you are willing to toss your Kindle in the trash if things go wrong (or are still within your 1 year warranty).

Davey126 said:
You are in a tough situation given Amazon CS performed the 3.2.8 rollback and OTA is apparently blocked using an unknown method (likely at the Amazon servers but can't be sure).
Options as follows:
1) Contact Amazon CS and request an upgrade to 4.5.2. However, they will likely upgrade to 4.5.4 which is unrootable at present. You would then need to manually rollback to 3.2.8 followed by a manual upgrade to 4.5.2. All this involves risk with the consequence being a bricked device if things go wrong.
2) Attempt to manually update to 4.5.2 which may or may not work given the OTA block. There is less risk but the consequence of a bad upgrade is equally severe (bricked tablet).
3) Stay on FireOS 3.2.8, Safestrap v3.7.x and Nexus 1.0.1 for now. Better/safer upgrade options will likely evolve with time. Nexus 1.0.1 remains quite serviceable for all but the newest applications especially when combined with Xposed Framework and Gravitybox.
I strongly advise option #3 unless you are willing to toss your Kindle in the trash if things go wrong (or are still within your 1 year warranty).
Click to expand...
Click to collapse
Just to add to what Davey126. My current understanding is that a manual upgrade does indeed work. 3.2.8 only stops the OTA updates from coming through.

after install safetrap now i got a problem, i cannot boot on stock slot, my kindle boot and stop at logo kindle fire (white - yellow). I try wipe all but nothing change. How can i copy Stock Image to the sd card to flash in stock slot, my computer does not find kindle. Please help

ChuTeng said:
after install safetrap now i got a problem, i cannot boot on stock slot, my kindle boot and stop at logo kindle fire (white - yellow). I try wipe all but nothing change. How can i copy Stock Image to the sd card to flash in stock slot, my computer does not find kindle. Please help
Click to expand...
Click to collapse
Can you still get into Safestrap?

ggow said:
Can you still get into Safestrap?
Click to expand...
Click to collapse
adb driver in my computer is problem, i fixed. Thanks.

ChuTeng said:
adb driver in my computer is problem, i fixed. Thanks.
Click to expand...
Click to collapse
Does that mean you are up and running again?

Awesome job!!!!!!!!!!
Confirmation number: 67M75398MF9375820

I'm on 4.5.4 7", any options for me? Can I contact amazon n hope they will roll me back? What version do I ask for?

[ROM] [UNLOCKED BOOTLOADER] Fire OS 4.5.2

For anyone who has an unlocked bootloader and wants to update to Fire OS 4, here's a stock 4.5.2 ROM that won't overwrite your current unlocked bootloader or recovery partition.
DOWNLOAD HERE
All credit goes to Cpasjuste for the current version - I might be uploading 4.5.5 here soon.

bmccoy11 said:
For anyone who has an unlocked bootloader and wants to update to Fire OS 4, here's a stock 4.5.2 ROM that won't overwrite your current unlocked bootloader or recovery partition.
DOWNLOAD HERE
All credit goes to Cpasjuste for the current version - I might be uploading 4.5.5 here soon.
Click to expand...
Click to collapse
Any feedback on this ROM?
Can this be installed on its own? Can I wipe /system and install? Downloading now but figured I'd ask here.

riggsandroid said:
Any feedback on this ROM?
Can this be installed on its own? Can I wipe /system and install? Downloading now but figured I'd ask here.
Click to expand...
Click to collapse
Yes, it can be installed over a cleanly wiped system partition. This is just the stock ROM that doesn't overwrite unlocked bootloaders when flashed.

bmccoy11 said:
Yes, it can be installed over a cleanly wiped system partition. This is just the stock ROM that doesn't overwrite unlocked bootloaders when flashed.
Click to expand...
Click to collapse
Right so when I borked my previous rom (ooooops) without a backup, this will give me stock Amazon rom back.
Thanks.
@bmccoy11
Ok so it flashed fine and I noticed you already did otacerts.old in /system/etc/security and I don't see the dcp apk in /system/app, however it tried DL'ing an update right away.
How do you recommend stopping OTAs?
Trying this method - http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550 - seems to work
Thanks.

bmccoy11 said:
Yes, it can be installed over a cleanly wiped system partition. This is just the stock ROM that doesn't overwrite unlocked bootloaders when flashed.
Click to expand...
Click to collapse
Is the 4.5.5 build far away? Might give it a crack over the weekend if it will be up.

Yes, the 4.5.5 is available here, already OTA blocked. I had to do a factory reset after flashing it (use ONLY the factory reset within TWRP, NOT the native factory reset) to get it to work, but after that, clear sailing, works great.

Ok, I'm a little confused about the process. My kindle fire is sitting at 4.5.4. I have refused to turn it on, because I don't want it to take 4.5.5. I want to re-establish root. I understand there is a downgrade process that allows you to move back to 4.5.2, then you can install root.
My question is, how do I unlock the boot loader at this point? Do I need to have an unlocked boot loader to install new images. I really want to be able to root and have the google play store installed, and not have all the bull**** errors like before with the playstore crashing.
Thanks to all you guys that have the answers and knowledge.

rlkellyjr said:
Ok, I'm a little confused about the process. My kindle fire is sitting at 4.5.4. I have refused to turn it on, because I don't want it to take 4.5.5. I want to re-establish root. I understand there is a downgrade process that allows you to move back to 4.5.2, then you can install root.
My question is, how do I unlock the boot loader at this point? Do I need to have an unlocked boot loader to install new images. I really want to be able to root and have the google play store installed, and not have all the bull**** errors like before with the playstore crashing.
Thanks to all you guys that have the answers and knowledge.
Click to expand...
Click to collapse
You can not unlock the bootloader on that device as it can not be rolled back to a version of FireOS (3.2.3.2 or below) containing the vulnerability that the unlock procedure exploits. The lowest you can go is 3.2.8. Any attempt to go further will result in a brick.
To get to 4.5.2 you rollback to 3.2.8 first using the procedure in this thread. Follow instructions precisely or you can damage/brick your device. Understand there are risks involved; this is not a task for the uninformed. There are no step-by-step guides or slick videos. Copious reading is your best friend along with the community servicing HDX forums.
Once on 3.2.8 you can upgrade to 4.5.2, block OTA, root, install Safestrap v4 and then Nexus v4 or cm11 both of which give full access to the Google Play Store. I strongly advise against attempting to install the play store under FireOS. Amazon and Google components do not play nice. Best use a different rom.
Do some reading and decide if you are up for the adventure. Ask questions before acting. Make sure you fully understand the relevant tasks, expected outcomes and things you should never do (like enable WiFi while on 3.2.8 - instant brick).
Edit: Fixed typos...

Thanks! but i have a question, why CM ROM the sound quality is very bad, even i install Dolby.

a442509097 said:
Thanks! but i have a question, why CM ROM the sound quality is very bad, even i install Dolby.
Click to expand...
Click to collapse
Search the HDX LineageOS 14.1 thread; many claim Viper4 is a better solution. Seems a bit complicated to obtain/install but that may be a faux impression. I am satisfied with Dolby but don't demand much from my device from an audio performance perspective.

how to delete this reply…

a442509097 said:
Viper4 is same too, i think this is about audio drive problem, because i try 4.22 or 4.4.4 system(however custom) sound quality has enough bass.
Click to expand...
Click to collapse
Might reach out to those who have installed (and presumably customized) Viper4 for this device. They claim sound quality is equal to if not superior to stock FireOS v4 (4.4.x base). I did notice a mild degradation going from Fire Nexus KTU84Q (4.4.4) to Android 5+ but not enough to warrant additional actions beyond installation of Dolby for noise reduction (random pops during quiet passages) and extended volume range. The builds were heavily customized when development resources were heavily focused on ROM enrichment. Things are different now; you'll likely have to roll your own if you believe this issue is with core binaries. Third gen devices have been out of production for 2+ years.

You sure about that? Wikipedia page for the series is under the impression they're still producing and selling the 7 inch HDX (which never got a 4th gen release), at least for LTE users.

Insidious622 said:
You sure about that? Wikipedia page for the series is under the impression they're still producing and selling the 7 inch HDX (which never got a 4th gen release), at least for LTE users.
Click to expand...
Click to collapse
LOL - since when did Wikipedia become the definative resource for Amazon devices? 3rd gen HDX is definitely out of production and has been for quite some time.

Fair enough, I just wasn't sure. Sometimes it's accurate, sometimes it isn't

Hi guys i need a zip or a backup. fore the orginal apollo room. i delet the backup fore safetrap and now i stuck at cm 4.4.4 and i will unlock my bootloader and install a other room but i need a orginal apollo backup or a zip to flash.

Serbest955 said:
Hi guys i need a zip or a backup. fore the orginal apollo room. i delet the backup fore safetrap and now i stuck at cm 4.4.4 and i will unlock my bootloader and install a other room but i need a orginal apollo backup or a zip to flash.
Click to expand...
Click to collapse
Bootloader can be unlocked while using CM 11 (KitKat 4.4.4) under Safestrap. Just follow the instructions. No need to reload FireOS.

Davey126 said:
Bootloader can be unlocked while using CM 11 (KitKat 4.4.4) under Safestrap. Just follow the instructions. No need to reload FireOS.
Click to expand...
Click to collapse
I need help while I understand the service not quite? How do I create this unlock file?
i follow this instruktion https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 and i have now install twrp and need now the unlock file.

texmexdud said:
Yes, the 4.5.5 is available here, already OTA blocked. I had to do a factory reset after flashing it (use ONLY the factory reset within TWRP, NOT the native factory reset) to get it to work, but after that, clear sailing, works great.
Click to expand...
Click to collapse
Links to that one are dead, could you please give up to date links?

Booting custom ROM w/out fastboot

I've been installing custom ROMs/recovery on Android devices for years and is the first time I've run across one that recovery must be booted from fastboot. Just got the $35 Fire tablet and want to install CM12.1 variant.
So do I have to use fastboot from computer just to boot recovery only when needed but once ROM is installed it will boot on its own? Just want to confirm before diving in. Thanks in advance.

xenokc said:
I've been installing custom ROMs/recovery on Android devices for years and is the first time I've run across one that recovery must be booted from fastboot. Just got the $35 Fire tablet and want to install CM12.1 variant.
So do I have to use fastboot from computer just to boot recovery only when needed but once ROM is installed it will boot on its own? Just want to confirm before diving in. Thanks in advance.
Click to expand...
Click to collapse
After you fastboot to a recovery, you can install either SlimLP or CyanogenMod 12.1. After install you don't need to fastboot every boot. The only issue I have with CM 12 is I haven't figured out how to unmount the microSD (aside from shutting down). Everything else seems to be working.
The Kernel is still locked by the bootloader, so only Lollipop Roms or Roms that use the Lollipop kernel will work.

xenokc said:
I've been installing custom ROMs/recovery on Android devices for years and is the first time I've run across one that recovery must be booted from fastboot. Just got the $35 Fire tablet and want to install CM12.1 variant.
So do I have to use fastboot from computer just to boot recovery only when needed but once ROM is installed it will boot on its own? Just want to confirm before diving in. Thanks in advance.
Click to expand...
Click to collapse
Even using fastboot rom install isn't available if the tablet has been allowed to update to or shipped with 5.1.1
But yes the roms now do boot untethered.
---------- Post added at 10:06 PM ---------- Previous post was at 10:05 PM ----------
caster121 said:
After you fastboot to a recovery, you can install either SlimLP or CyanogenMod 12.1. After install you don't need to fastboot every boot. The only issue I have with CM 12 is I haven't figured out how to unmount the microSD (aside from shutting down). Everything else seems to be working.
Click to expand...
Click to collapse
There's a third one now. Resurrection-Remix

caster121 said:
After you fastboot to a recovery, you can install either SlimLP or CyanogenMod 12.1. After install you don't need to fastboot every boot. The only issue I have with CM 12 is I haven't figured out how to unmount the microSD (aside from shutting down). Everything else seems to be working.
Click to expand...
Click to collapse
There's a third one now. Resurrection-Remix

Pond-life said:
Even using fastboot rom install isn't available if the tablet has been allowed to update to or shipped with 5.1.1
But yes the roms now do boot untethered.
---------- Post added at 10:06 PM ---------- Previous post was at 10:05 PM ----------
There's a third one now. Resurrection-Remix
Click to expand...
Click to collapse
Bummer, my tablet shipped with 5.1.1. So can I even root?

xenokc said:
Bummer, my tablet shipped with 5.1.1. So can I even root?
Click to expand...
Click to collapse
you can now root on 5.1.1, use the supertool from below.
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695

xenokc said:
Bummer, my tablet shipped with 5.1.1. So can I even root?
Click to expand...
Click to collapse
Yep you can now root it.
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
Or it's in the supertool
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
FlashFire app has let some brave souls on 5.1.1 change to the Slim rom, but without the TWRP fallback I'd be wary.

Thanks all, am on it.

xenokc said:
Thanks all, am on it.
Click to expand...
Click to collapse
Root junky Video
Amazon Fire 5th gen 7in Slim Rom install on Fire OS 5 1 1 with FlashFire App
https://youtu.be/NaCBSuUuhRE
Sent from my KFFOWI using Tapatalk

fire OS FW's with no boot loader flashing for 5th gen and 7th gen

This is a collection of fire os FW for the 5th gen and 7th gen with no bootloader flashing.
Dsclaimer
- This is for flashing with TWRP or flash fire only.
-This doesn't stop you from flashing on other devices but it won't hard brick because there are no bootloader files in the ROM file
-newer releases will Not have OTA updates removed anymore
why...
I'm going to expand to the hd 8 and hd 10, I want to keep it stock. its a lot less time consuming to not edit system files
- I'm going to go back and do this with all previous versions of fire os FW (it will take a while)
available to download
-5.3.6.8 (7th gen only)
-5.6.3(won't work on older bootloaders)
-5.4.0
removing ads
this is the best way to remove ads.
it requires root
Code:
adb shell
su
settings put global LOCKSCREEN_AD_ENABLED 0
settings put global ksoHash 0
Then uninstall special offers and do a reboot
removing ota
The two apps you need to delete is DeviceSoftwareOTA and Forced OTA. that's all
Downloads
Everything will go to android file host but the 7th gen is the only thing up there for right now
5th gen
7th gen
enjoy!

Updates list
update 4-25-19
-fixed the links for the 5th gen
update 4-21-2019
-added 5.3.6.8 for 7th gen
update 2-12-2019 for 5.4.0
-fixed flashing the boot image
-fixed flashing for newer TWRP recovery

prime video not working
ANDROID2468 said:
update 2-12-2019 for 5.4.0
-fixed flashing the boot image
-fixed flashing for newer TWRP recovery
Click to expand...
Click to collapse
Thanks for your work on this ROM.
I'm using the 5.6.3 version on my 5th Gen:
When playback in Prime video is happening, there is audio but no video. I tried playing with the dpi and had mix results. It appears to be a resolution issue? What do you think could be wrong? When I revert back to stock recovery and flash the same version everything is fine. Does this have something to do with the unlocked bootloader?

bruinsrule said:
Thanks for your work on this ROM.
I'm using the 5.6.3 version on my 5th Gen:
When playback in Prime video is happening, there is audio but no video. I tried playing with the dpi and had mix results. It appears to be a resolution issue? What do you think could be wrong? When I revert back to stock recovery and flash the same version everything is fine. Does this have something to do with the unlocked bootloader?
Click to expand...
Click to collapse
Do you have the same issue on YouTube? If you only have this issue on prime video and only on this rom then it's possible that I removed a dependency, but I don't think that there is any.... sorry, I was thinking of the wrong rom. the only thing I removed from this rom was OTA updates. sometimes you might have issues like not having wifi when you do the unlock. try to redo the unlock. make sure you have the latest version of it.

ANDROID2468 said:
Do you have the same issue on YouTube? If you only have this issue on prime video and only on this rom then it's possible that I removed a dependency, but I don't think that there is any.... sorry, I was thinking of the wrong rom. the only thing I removed from this rom was OTA updates. sometimes you might have issues like not having wifi when you do the unlock. try to redo the unlock. make sure you have the latest version of it.
Click to expand...
Click to collapse
I've tried the revamped OS, this OS, and stock. When I unlock the prime video has the same behavior in each instance. Youtube works fine and the commercials within prime video work, oddly. I'll try doing a second unlock to see if that will do the trick. I was just wondering if anyone else was experiencing this, or they just don't use prime video.

@ANDROID2468 add stock android Lollipop lockscreen wallpaper in the next build please.
Add in the updater-script a command that extracts the wallpaper in
/data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
See this:
https://forum.xda-developers.com/hd8-hd10/help/root-change-lock-screen-wallpapers-t3859459

Rortiz2 said:
@ANDROID2468 add stock android Lollipop lockscreen wallpaper in the next build please.
Add in the updater-script a command that extracts the wallpaper in
/data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
See this:
https://forum.xda-developers.com/hd8-hd10/help/root-change-lock-screen-wallpapers-t3859459
Click to expand...
Click to collapse
The only thing I am changing in this rom is removing the ota updates. If you want a more costume fire os version please check out my fire os revamped . I'm keeping this rom as stock as possible.
In that rom I tried to change the wallpaper by decompiling the framework.res.apk and change it from there but I had no luck with that. If you do it how you mentioned above you will lose it when you factory reset.

bruinsrule said:
I've tried the revamped OS, this OS, and stock. When I unlock the prime video has the same behavior in each instance. Youtube works fine and the commercials within prime video work, oddly. I'll try doing a second unlock to see if that will do the trick. I was just wondering if anyone else was experiencing this, or they just don't use prime video.
Click to expand...
Click to collapse
Try the one in the play store

bruinsrule said:
I've tried the revamped OS, this OS, and stock. When I unlock the prime video has the same behavior in each instance. Youtube works fine and the commercials within prime video work, oddly. I'll try doing a second unlock to see if that will do the trick. I was just wondering if anyone else was experiencing this, or they just don't use prime video.
Click to expand...
Click to collapse
I get the same problem with the Fire 7, 5th gen. tablet. The FIre 7, 7th gen. (unlocked in the same way) is fine though: Prime Video works correctly. Could it be due to the OS 5.01 TZ file?

The problem with Prime Video is caused by flashing the OS 5.01 TZ file with Amonet. With the latest TZ file used (OS 5.6.3.0), video is displayed correctly. However doing this disables Wi-Fi on the tablet. I will post about this in the most relevant thread (see here). BTW, downloading Prime Video from Google Play is not a solution. Even if you delete the prime folder (com.amazon.avod) and contents from '/system/priv-app' and reboot, then install the Google Play version, the app crashes after opening.

There is a fix for the Prime Video playback issue described in the above posts: see here for details.

I just saw that there is a new FW available for all 7th gens, not 5th gens. fire os 5.3.6.8. I will have a non bootloader zip up soon

As a new guy, I am not sure how to use the "fire os 5.6.3-no BL+ no ota_adds" after I unzipped it. My device is 7 inch 5th gen with OS 5.6.8 Any help with this, please?

[Guide] Rooting Nexus 7 (2012) Lollipop [5 Simple Steps]

Every single guide i found went through a little bit too much, in this guide i'll show you how to root your device without installing custom recovery in 5 easy steps. I am going to assume that you already have android platform tools installed on your computer
Downloads
TWRP: Asus Nexus 7 2012 Wi-Fi | Asus Nexus 7 2012 3G
Latest Magisk from the official github repo
Steps
Boot into the bootloader by holding Power + Vol Down for about 10 secs
Connect your device using a usb cable to your computer
If you see LOCK STATE - UNLOCKED, skip this step, otherwise you need to unlock your bootloader by running this command from your computer. Accept and wait while device resets. *this will wipe your device
Code:
fastboot oem unlock
Your bootloader should now be unlocked, running this will give you access to twrp without installing it
Code:
fastboot boot path/to/twrp-recover.img
Now you have two pathways:~
Normal: Use your touch screen to install magisk.zip file you downloaded from github and you're done
Broken Screen/Digitizer: From your computer while twrp is open, type this command. * assuming that you renamed magisk archive to magisk.zip and copied it to your sdcard with adb push
Code:
adb shell twrp install /sdcard/magisk.zip
Going Back
GedBlake said:
If, in the unlikely event, you do mess up rooting your tablet, you can easily re-flash to factory using the factory stock images available at the links below...
Nexus 7 - WiFi only
https://developers.google.com/android/images/#nakasi
Nexus 7 - WiFi and 3G
https://developers.google.com/android/images/#nakasig
Click to expand...
Click to collapse
Reboot, Have fun!

pushqrdx said:
Every single guide i found went through a little bit too much, in this guide i'll show you how you can root your device without installing custom recovery with 5 easy steps. I am going to assume that you already have android platform tools installed on your computer
Downloads
1- TWRP: Asus Nexus 7 2012 Wi-Fi | Asus Nexus 7 2012 3G
2- Latest Magisk from the official github repo
Steps
1- Boot into the bootloader by holding Power + Vol Down for about 10 secs.
2- Connect your device using a usb cable to your computer.
3- If you see LOCK STATE - UNLOCKED, skip this step, otherwise you need to unlock your bootloader by running this command from your computer. Accept and wait while device resets * this will wipe your device
4- Your bootloader should now be unlocked, running this will give you access to twrp without installing it.
5- Now you have 2 pathways
Normal: Use your touch screen to install magisk.zip file you downloaded from github and you're done
Broken Screen/Digitizer: From your computer while twrp is open type this command. * assuming that you renamed magisk archive to magisk.zip and copied it to your sdcard
Reboot, Have fun
Click to expand...
Click to collapse
Hi, pushqrdx...
A nice and concise guide, and whilst it's perhaps a little late in the day (the Nexus 7 is, after all, some 7 years old now ~ where does the time go!), I always think that the more of these guides there are, the better.
For example, someone might have just picked up an old Nexus 7 somewhere second hand, and might be looking for such instructions as yours.
I also like the way you've updated the procedure for Magisk. The last time I rooted anything, let alone a Nexus 7, was with Chainfire's SuperSU root package. But of course, root is done via Magisk these days, so yours is a nicely updated guide.
And you've also provided a contingency scenario for a damaged screen/digitizer - not something I've had to deal with myself.
-------------------------
I hope you don't mind me adding a little additional tip for anyone reading this...
If, in the unlikely event you do mess up rooting the Nexus 7, you can easily reflash back to factory using the factory stock images available at the links below...
Nexus 7 - WiFi only
https://developers.google.com/android/images/#nakasi
Nexus 7 - WiFi and 3G
https://developers.google.com/android/images/#nakasig
-------------------------
So, in conclusion then, a straightforward and concise guide that covers all the basics to rooting the Nexus 7 - kudos to you sir for writing it.
Kind Rgrds,
Ged.

GedBlake said:
Hi, pushqrdx...
A nice and concise guide, and whilst it's perhaps a little late in the day (the Nexus 7 is, after all, some 7 years old now ~ where does the time go!), I always think that the more of these guides there are, the better.
For example, someone might have just picked up an old Nexus 7 somewhere second hand, and might be looking for such instructions as yours.
I also like the way you've updated the procedure for Magisk. The last time I rooted anything, let alone a Nexus 7, was with Chainfire's SuperSU root package. But of course, root is done via Magisk these days, so yours is a nicely updated guide.
And you've also provided a contingency scenario for a damaged screen/digitizer - not something I've had to deal with myself.
Click to expand...
Click to collapse
Thanks! I had to deal with a broken tablet recently and i thought it would be nice to share incase anybody finds it useful. And yeah Nexus 7 is so damn old ?. Also thanks for the tip i have edited the post to include it as a quote from you

Problem with Nexus
I have a Asus Nexus 7 2012 Wi-Fi. I have managed to unlock the bootloader and, using adb, checked the devise is authorised. When I try to run 'flash-all', I get stuck at '<waiting for a device>'.
PS C:\Users\OFFICE PC\Desktop\Nexus 7 KitKat\nakasi-ktu84p> .\fastboot flash-all
< waiting for any device >
I cannot fix this problem so I went to your tutorial, I have downloaded twrp and magisk. Do I run these from CMD?. Also, where is twrp-recover.img?

GaryWilliams said:
I have a Asus Nexus 7 2012 Wi-Fi. I have managed to unlock the bootloader and, using adb, checked the devise is authorised. When I try to run 'flash-all', I get stuck at '<waiting for a device>'.
PS C:\Users\OFFICE PC\Desktop\Nexus 7 KitKat\nakasi-ktu84p> .\fastboot flash-all
< waiting for any device >
I cannot fix this problem so I went to your tutorial, I have downloaded twrp and magisk. Do I run these from CMD?. Also, where is twrp-recover.img?
Click to expand...
Click to collapse
TWRP has to be in the same folder on the PC as your ADB tools. Then using the command given, you boot into TWRP. You don't install it as per this procedure. Then using the TWRP's 'Install' button, find the Magisk zip and install it(you should have copied/pushed it to the tab before).
EDIT: The 'twrp-recover.img' is the name you give to the TWRP which you downloaded.

Thanks, my mom still uses her 2012 nexus 7, great little tablet, but I updated to whatever the latest droid version and it SUCKS, stopped it in its tracks, jams up and slower than ever, want to get it back on the previous version of droid when it worked 10 times better.

doitinthedirt said:
Thanks, my mom still uses her 2012 nexus 7, great little tablet, but I updated to whatever the latest droid version and it SUCKS, stopped it in its tracks, jams up and slower than ever, want to get it back on the previous version of droid when it worked 10 times better.
Click to expand...
Click to collapse
Maybe it would run well on Android Go Edition, as that is designed for devices with 2GB of RAM or less. I'm thinking of trying that with my one but have no idea of how to go about it at the moment. Will have to read the OP here at least 7 times before any of it sinks in!

thank you