Hi Guys,
So I recently got my hands on a kindle fire 5th gen (2015), running the latest OS 5.3.2.1.
I have read many things and many different opinions on what can and cannot be done, and ideally I am looking for a conclusive list i there is one available.
So I was searching and Root Junky has provided custom ROM's and a few other files, however, this is my understanding
CANNOT: root
CAN: downgrade to an older OS, which may allow root, but its likely it will brick it
CANNOT: unlock bootloader for custom ROM installation
CANNOT: install a custom flash zip file from the inbuilt android recovery interface
I dont know if they just happened to crash down and lockdown the fire recently, but pages such as this below, indicate it can (or at least could) be done.
https://www.thepolyglotdeveloper.com/2016/05/install-better-custom-rom-amazon-kindle-fire/
and this, indicates its probably too late since I connected it and downloaded 5.3.2.1.
http://android.stackexchange.com/qu...ot-and-install-cm-12-1-on-5th-gen-kindle-fire
So, is there a conclusive list, aside "using your tablet as out of the box" as to what you can and cannot do to modify the fire 5th gen?
I got mine right before bootloader lock running slim LP haven't updated since used flash fire on 5.1.1 to the best of my knowledge
Sent from my Robin using Tapatalk
FF51, so very lucky, I am really envious actually.
The fire, when not suffering pixel outages, and without a dire need for GPS, makes an excellent hardware base, and from my reading, installng a custom rom would really unlock the xperience of the tablet and give it a much more competitive edge.
Out of curiosity, did you jump straight into the slim build, or did you try others?
Also I have read you cannot install CM13+ due to the limitations of the bootloader, but can you install CM12 instead (I think thats based on lollipop isnt it?) and can you do that with the stock bootloader / recovery module?
jeebob said:
Also I have read you cannot install CM13+ due to the limitations of the bootloader, but can you install CM12 instead (I think thats based on lollipop isnt it?) and can you do that with the stock bootloader / recovery module?
Click to expand...
Click to collapse
- can not root (at present) or downgrade (ever) FireOS 5.3.2.1
- bootloader remains locked; no custom kernels or recoveries (eg: TWRP)
- rooted devices can only run Lollipop based ROMs due to kernel restrictions
- custom ROMs must be installed with FlashFire
- see forum index for further info: http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Hi every one!
Tell me please, can I use FlashFire and install CM12.1 into my Kindle 7 with 5.3.2.1 without root device?
So I can`t downgrade 5.3.2.1?
My device isn`t rooted and locked. my only achievement was the google play store
Davey126 said:
- can not root (at present) or downgrade (ever) FireOS 5.3.2.1
- bootloader remains locked; no custom kernels or recoveries (eg: TWRP)
- rooted devices can only run Lollipop based ROMs due to kernel restrictions
- custom ROMs must be installed with FlashFire
- see forum index for further info: http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Click to expand...
Click to collapse
Thanks Davey, a concise list which is great, now I just have to hope we can get the bootloader and root sorted on 5.3.2.1!
bojkoio said:
Hi every one!
Tell me please, can I use FlashFire and install CM12.1 into my Kindle 7 with 5.3.2.1 without root device?
Click to expand...
Click to collapse
It looks like the answer is not at this time, as from my reading, 5.3.2.1 cannot be rooted directly with current methods, only 5.3.1 onwards.
freaky2xd said:
So I can`t downgrade 5.3.2.1?
My device isn`t rooted and locked. my only achievement was the google play store
Click to expand...
Click to collapse
thats all I have managed to achieve so far, next I want to remove the adverts!
bojkoio said:
Hi every one!
Tell me please, can I use FlashFire and install CM12.1 into my Kindle 7 with 5.3.2.1 without root device?
Click to expand...
Click to collapse
Nope - no custom ROMs without root.
---------- Post added at 12:50 PM ---------- Previous post was at 12:49 PM ----------
freaky2xd said:
So I can`t downgrade 5.3.2.1?
My device isn`t rooted and locked. my only achievement was the google play store
Click to expand...
Click to collapse
No - nor likely ever. Best hope is for a root solution.
Well Sh*t
I got all 3 of my daughters a kindle fire 7" 5th gen for Christmas. I ran thru the updates and was going to install the google framework and all that goes with it to be able to install works of ahhh painting app. However, I have hit a roadblock since it seems even tho I have enabled unknown sources and rebooted each device (all running 5.3.2.1) I can download apks but when I attempt to install them, it's like the install button just doesn't register touch response no matter what direction you rotate the device. I'm not new to this, I got kindles because of how easy it was to customize a previous one my 7 year old had, and besides, $30 each was a pretty good deal. So maybe it's a software glitch in the new update, maybe it's that I just don't care enough to dig into it but that's where it stands here.
Edit: A simple reboot after allowing unknown sources fixed the problem and I completed the installation of Google play store
luck_shawn said:
I got all 3 of my daughters a kindle fire 7" 5th gen for Christmas. I ran thru the updates and was going to install the google framework and all that goes with it to be able to install works of ahhh painting app. However, I have hit a roadblock since it seems even tho I have enabled unknown sources and rebooted each device (all running 5.3.2.1) I can download apks but when I attempt to install them, it's like the install button just doesn't register touch response no matter what direction you rotate the device. I'm not new to this, I got kindles because of how easy it was to customize a previous one my 7 year old had, and besides, $30 each was a pretty good deal. So maybe it's a software glitch in the new update, maybe it's that I just don't care enough to dig into it but that's where it stands here.
Click to expand...
Click to collapse
On mine I downloaded the four apks needed installed them (in proper order) using apk permission remover and it worked for me. There's a thread in the fourms I folllwed
I just used the kindle supertool to install the google framework and APK's. once click and leave it to its own devices - a tool by superjunky I think?
Anyway, as for the rotation, I havent noticed any particular problems with it, but I havent done a lot of work with testing it, I will try take a look a bit later!
i have the same problem. I managed to install Google Play but trying to side load the Popcorntime apk fails with the next and install button not registering touch input, cancel button works fine.
oilyrag said:
i have the same problem. I managed to install Google Play but trying to side load the Popcorntime apk fails with the next and install button not registering touch input, cancel button works fine.
Click to expand...
Click to collapse
Have you enabled FireOS setting that allows installs from unknown sources and then rebooted device?
Davey126 said:
Have you enabled FireOS setting that allows installs from unknown sources and then rebooted device?
Click to expand...
Click to collapse
Thought I had rebooted device, done it again, now works. Many thanks
Sent from my SM-N9005 using Tapatalk
I bought two 7" fires on the Black Friday sale to use as home automation panels in the house (with SmartThings). I installed the Play Store but found the SmartThings app was still not compatible . But really I was waiting for the new ActionTiles (web client) to come out. The one Fire upgraded to 5.3.2.1 and I haven't opened the other yet. The Play Store will no longer launch on the 5.3.2.1 tablet either. My original thought was to probably flash a new rom that is not as restrictive but doesn't look like that will happen now. Have a few additional questions for the "can" and "can't" list with 5.3.2.1 please:
1) Can the lock screen be disabled/removed?
2) Can the device be woken up by screen touch?
3) Does the non-root Play Store hack still work? (maybe I just need to redo something after the upgrade?)
4) Are there any browsers I can have auto load the ActionTiles dashboard (web page) and always keep it up and full screen?
Thanks a lot!
Coods said:
1) Can the lock screen be disabled/removed?
2) Can the device be woken up by screen touch?
3) Does the non-root Play Store hack still work? (maybe I just need to redo something after the upgrade?)
4) Are there any browsers I can have auto load the ActionTiles dashboard (web page) and always keep it up and full screen?
Thanks a lot!
Click to expand...
Click to collapse
1) not completely that I have found, unless you keep the screen alive 24/7.
2) power button only however root could allow this but 5.3.2.1 doesn't support (or should I say have a method for) root at this time.
3) yes it does, I have uploaded it to about 6 different kindle recently all running 5.3.2.1
4) again root would help, however you can use automateit free or pro from plastered. It's very powerful and you should be able to achieve a lot with it. If it doesn't support it though, tasker is another powerful tool which might be worth exploring
Sent from my D6603 using Tapatalk
jeebob said:
2) power button only however root could allow this but 5.3.2.1 doesn't support (or should I say have a method for) root at this time.
Click to expand...
Click to collapse
No hardware support for this capability regardless of root (re: touch to wake).
Davey126 said:
No hardware support for this capability regardless of root (re: touch to wake).
Click to expand...
Click to collapse
Thanks for confirming davey!
Sent from my D6603 using Tapatalk
Thanks for the info guys, appreciate it! This helps me understand the direction I want to take with these as alarm panels
Related
Hello and thanks for reading!
I have a Kindle Fire 5th Gen that was just given to me. I'd like to get rid of the Amazon OS and install anything (I'll take CM or whatever). It is currently running 5.1.2 yet KingRoot v4.9.2 says it is 5.1.1.
I've tried KingRoot a few times (apparently you need root to get TWRP going) and nothing happens - it keeps failing.
I've gone through some RootJunky videos but those aren't updated for 5.1.2 via Windows.
I'm at a loss of what to do next. This video says that installing an old version of Fire OS will brick your Kindle.
All of these different threads have me confused.
My questions are:
I understand that TWRP doesn't work on 5.1.2, so how do I get to a different version of Fire OS? And how do I disable OTA's? Turn off Wifi?
When I get to a different version of Fire OS, will RootJunky's tools work like in his videos?
I apologize if this is already answered in another thread as I can't find it and am new to the Kindle Fire.
I'd like to be able to use it for my school books next semester instead of having to bring the big effin things back and forth. For $50 bucks (retail), this seems like a steal to get a vanilla version of Android running on it!
Thanks in advance!
Pcprik said:
Hello and thanks for reading!
I have a Kindle Fire 5th Gen that was just given to me. I'd like to get rid of the Amazon OS and install anything (I'll take CM or whatever). It is currently running 5.1.2 yet KingRoot v4.9.2 says it is 5.1.1.
I've tried KingRoot a few times (apparently you need root to get TWRP going) and nothing happens - it keeps failing.
I've gone through some RootJunky videos but those aren't updated for 5.1.2 via Windows.
I'm at a loss of what to do next. This video says that installing an old version of Fire OS will brick your Kindle.
All of these different threads have me confused.
My questions are:
I understand that TWRP doesn't work on 5.1.2, so how do I get to a different version of Fire OS? And how do I disable OTA's? Turn off Wifi?
When I get to a different version of Fire OS, will RootJunky's tools work like in his videos?
I apologize if this is already answered in another thread as I can't find it and am new to the Kindle Fire.
I'd like to be able to use it for my school books next semester instead of having to bring the big effin things back and forth. For $50 bucks (retail), this seems like a steal to get a vanilla version of Android running on it!
Thanks in advance!
Click to expand...
Click to collapse
- although your device shows 5.1.2 it is likely running 5.1.2.1 which can not be rooted at present
- you need to reload (sideload) 'pure' 5.1.2 via the stock recovery menu; there are instructions and videos posted elsewhere in this forum
- once on 5.1.2 use the SuperTool to root, block OTA, swap out Kinguser for SuperSU and obtain FlashFire which is used to install custom roms
- TWRP is not an option for your device at this time (nor is it likely in the near future)
- suggest looking through the index for relevant material (link below)
- keep reading; you'll get the hang of it
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Davey126 said:
- although your device shows 5.1.2 it is likely running 5.1.2.1 which can not be rooted at present
- you need to reload (sideload) 'pure' 5.1.2 via the stock recovery menu; there are instructions and videos posted elsewhere in this forum
- once on 5.1.2 use the SuperTool to root, block OTA, swap out Kinguser for SuperSU and obtain FlashFire which is used to install custom roms
- TWRP is not an option for your device at this time (nor is it likely in the near future)
- suggest looking through the index for relevant material (link below)
- keep reading; you'll get the hang of it
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Click to expand...
Click to collapse
Thanks!
I may have hit a 'small' snag though. When I put 5.1.2 from the Index page on, Kingroot still didn't work so I put the next oldest version on (5.1.1 I believe). Now it won't startup and just has a black screen - I believe I forgot to select wipe cache before restarting. When I plug it into my Surface, Device Manager keeps making noises and I have installed the MTK VCOM drivers. I'm going to try to put 5.1.2.1 back on but I'm wondering if this thing is actually bricked? According to this thread it's possible to 'unbrick' it but if it doesn't turn on, how does it get into recovery mode?! Perhaps it's in recovery mode now with the blank screen? When I do 'adb devices', nothing shows up so I'm guessing it's not connected? Even doing 'adb sideload <filename>' shows no devices connected.
Thanks again!
Pcprik said:
Thanks!
I may have hit a 'small' snag though. When I put 5.1.2 from the Index page on, Kingroot still didn't work so I put the next oldest version on (5.1.1 I believe). Now it won't startup and just has a black screen - I believe I forgot to select wipe cache before restarting. When I plug it into my Surface, Device Manager keeps making noises and I have installed the MTK VCOM drivers. I'm going to try to put 5.1.2.1 back on but I'm wondering if this thing is actually bricked? According to this thread it's possible to 'unbrick' it but if it doesn't turn on, how does it get into recovery mode?! Perhaps it's in recovery mode now with the blank screen? When I do 'adb devices', nothing shows up so I'm guessing it's not connected? Even doing 'adb sideload <filename>' shows no devices connected.
Thanks again!
Click to expand...
Click to collapse
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Davey126 said:
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Click to expand...
Click to collapse
That's what I thought.
Thanks again for your help!
Davey126 said:
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Click to expand...
Click to collapse
Just to confirm, I should have put 5.1.2 and then rooted, correct? I may buy a new one.
Pcprik said:
Just to confirm, I should have put 5.1.2 and then rooted, correct? I may buy a new one.
Click to expand...
Click to collapse
Correct. Summary here; see index for more robust coverage.
I have rooted 5th Gen 7" Kindle at OS 5.0.0. Do I need to update to another version of the OS? Like 5.1.2?
The only things I have done so far is that:
1. I rooted my Kindle 5th gen using this thread:
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
2. Installed Google Play with JunkyDSL's supertool:
http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/SuperTool
Before I do anything else, I figured I should check with you guys. I literally have not done anything else. I have never signed in on the device. I just took it out of the box and rooted it and added Play Store. I haven't even connected it to the WiFi yet! Play Store seems to work as I am in the login screen.
Please advise as to whether I should update the OS. And if I do, which version?
chowyungfatso said:
I have rooted 5th Gen 7" Kindle at OS 5.0.0. Do I need to update to another version of the OS? Like 5.1.2?
The only things I have done so far is that:
1. I rooted my Kindle 5th gen using this thread:
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
2. Installed Google Play with JunkyDSL's supertool:
http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/SuperTool
Before I do anything else, I figured I should check with you guys. I literally have not done anything else. I have never signed in on the device. I just took it out of the box and rooted it and added Play Store. I haven't even connected it to the WiFi yet! Play Store seems to work as I am in the login screen.
Please advise as to whether I should update the OS. And if I do, which version?
Click to expand...
Click to collapse
If your objective is to install a custom rom (now or in the future) you should not update FireOS in the usual manner as you will loose the ability to boot TWRP. There is an alternative method for manually updating FireOS while preserving the bootloader which gives you the best of both worlds. I'll leave it to others to post links. For now do not register your device as an automatic update to the latest version of FireOS, including the bootloader, will quickly follow.
Davey126 said:
If your objective is to install a custom rom (now or in the future) you should not update FireOS in the usual manner as you will loose the ability to boot TWRP. There is an alternative method for manually updating FireOS while preserving the bootloader which gives you the best of both worlds. I'll leave it to others to post links. For now do not register your device as an automatic update to the latest version of FireOS, including the bootloader, will quickly follow.
Click to expand...
Click to collapse
1. I definitely want flexibility, so thanks for the note re: losing the ability to change bootloaders.
2. I will have to research updating FireOS manually
Is there even a benefit to updating FireOS? My goal right now is to keep it as "standard" as possible, but with the possibility to install a custom ROM in the future--as soon as I get tired of FireOS (not a huge fan but I'm willing to live with it until I have more time).
chowyungfatso said:
1. I definitely want flexibility, so thanks for the note re: losing the ability to change bootloaders.
2. I will have to research updating FireOS manually
Is there even a benefit to updating FireOS? My goal right now is to keep it as "standard" as possible, but with the possibility to install a custom ROM in the future--as soon as I get tired of FireOS (not a huge fan but I'm willing to live with it until I have more time).
Click to expand...
Click to collapse
If it ain't broke don't fix it. You always have the option of updating later if/when needed. The opposite is not necessarily true.
chowyungfatso said:
I have rooted 5th Gen 7" Kindle at OS 5.0.0. Do I need to update to another version of the OS? Like 5.1.2?
The only things I have done so far is that:
1. I rooted my Kindle 5th gen using this thread:
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
2. Installed Google Play with JunkyDSL's supertool:
http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/SuperTool
Before I do anything else, I figured I should check with you guys. I literally have not done anything else. I have never signed in on the device. I just took it out of the box and rooted it and added Play Store. I haven't even connected it to the WiFi yet! Play Store seems to work as I am in the login screen.
Please advise as to whether I should update the OS. And if I do, which version?
Click to expand...
Click to collapse
Actually, it'd be interesting to save a copy of the preloader and the bootloaders (TEE1, UBOOT) for 5.0.0 Or is it available somewhere already ? I wonder if this early preloader may be free of the anti-rollback protections, and that would allow for downgrades on the other Fires.
chowyungfatso said:
I have rooted 5th Gen 7" Kindle at OS 5.0.0.
Click to expand...
Click to collapse
Can you dump some partitions by running these commands in adb (if your version is indeed 5.0.0):
Code:
adb shell
su
cd /sdcard
mkdir images
cd images
dd if=/dev/block/mmcblk0boot0 of=/sdcard/images/boot0.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/images/09_tee1.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/images/10_tee2.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/images/04_uboot.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/images/08_logo.img
Then zip, and upload here.
It'll be interesting to see if the preloader already has the anti-rollback strings in this early version !
bibikalka said:
Can you dump some partitions by running these commands in adb (if your version is indeed 5.0.0):
It'll be interesting to see if the preloader already has the anti-rollback strings in this early version !
Click to expand...
Click to collapse
I'm out of town for a few weeks. I will get to it when I get back!
bibikalka said:
Can you dump some partitions by running these commands in adb (if your version is indeed 5.0.0):
...
Click to expand...
Click to collapse
See attached. I also included the list of results. Let me know if this is what you need. This is what it said when I bring up the screen System Updates:
Fire OS 5.0.0 (Build date Saturday, August 1, 2015, 10:39 PM GMT).
chowyungfatso said:
See attached. I also included the list of results. Let me know if this is what you need. This is what it said when I bring up the screen System Updates:
Fire OS 5.0.0 (Build date Saturday, August 1, 2015, 10:39 PM GMT).
Click to expand...
Click to collapse
Thanks for going through the trouble of downloading the partitions !!!
Added your info to this :
http://forum.xda-developers.com/amazon-fire/development/identify-bootloader-version-t3424634
Unfortunately, this preloader already has ANTI ROLLBACK strings, so I doubt it'd help to use it to downgrade the newer versions.
For your upgrade, you could either just go to 5.0.1 bootloaders in this post (& 5.3.1 FireOS):
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
As an alternative, I could make a zip file for you to flash your 5.0.0 bootloaders back after upgrading to 5.3.1 (but not clear why are these so needed anymore ...)
bibikalka said:
Thanks for going through the trouble of downloading the partitions !!!
Unfortunately, this preloader already has ANTI ROLLBACK strings, so I doubt it'd help to use it to downgrade the newer versions.
Click to expand...
Click to collapse
Well at least the communicator has a copy of this version now too.
I haven't felt like I needed to switch to a custom ROM yet, which I understand would be the main (only?) reason to upgrade the bootloader.
chowyungfatso said:
Well at least the communicator has a copy of this version now too.
I haven't felt like I needed to switch to a custom ROM yet, which I understand would be the main (only?) reason to upgrade the bootloader.
Click to expand...
Click to collapse
No need to update the bootloader for custom rom support, at least with the current suite of roms. Retaining a 5.0.x bootloader is desirable as it permits booting TWRP (or another custom recovery) which is generally more flexible than 'soft' flashing (requires root and a working rom) plus enhanced recovery capabilities should something go wrong.
Hi all
I've just bought a Fire Tablet on Amazon day with the intention of rooting it and installing CM, but I am a newbie and there's so much information on here it's kind of overwhelming, and most of it has a lot of "if this, then that, or if you want to use that, do this" type guides, which for someones who doesn't really know what all the different methods and options are is really confusing!
So can someone please tell me the step by step process for doing it?
From what I've read I think I have to downgrade to 5.1.2 of the OS as I can't root on 5.1.4? Is that correct?
So do I have to root before I do that? Or do I downgrade first and then root, and then install the CM?
If someone can list each of the steps I need to take to get it from a fresh new 5th Gen Fire 7 to having all the Amazon rubbish off and having it running CM, then I can look for the guides for each step!
Thanks, I hope that makes sense!
:angel:
PS: I've already bricked one by trying to downgrade to 5.1.1 because that wasn't apparent until it was too late, replacement on its way!
Yeah, I read the same thing and I bought it on Prime day. When's the 5.14 tool going to come out? I know, beggars... I really think it's silly to have to downgrade and risk bricking it when normal root for those OS versions don't have such a concern.
Bob Boblaw said:
Hi all
I've just bought a Fire Tablet on Amazon day with the intention of rooting it and installing CM, but I am a newbie and there's so much information on here it's kind of overwhelming, and most of it has a lot of "if this, then that, or if you want to use that, do this" type guides, which for someones who doesn't really know what all the different methods and options are is really confusing!
So can someone please tell me the step by step process for doing it?
From what I've read I think I have to downgrade to 5.1.2 of the OS as I can't root on 5.1.4? Is that correct?
So do I have to root before I do that? Or do I downgrade first and then root, and then install the CM?
If someone can list each of the steps I need to take to get it from a fresh new 5th Gen Fire 7 to having all the Amazon rubbish off and having it running CM, then I can look for the guides for each step!
Thanks, I hope that makes sense!
:angel:
PS: I've already bricked one by trying to downgrade to 5.1.1 because that wasn't apparent until it was too late, replacement on its way!
Click to expand...
Click to collapse
I did the same thing, bought the tablet on prime day and was successfully able to root it and put the AOSP nexus rom
First things first make sure you have the 7-inch tablet for the following steps because apparently it only works with that specific model. Since this is my first post I can't post any links so sorry about that however, I have added the video title so that you can just google it and find the video.
Anything above fire os 5.1.2 ( that is 5.1.4, 5.1.3, 5.1.2.1) has to be downgraded to 5.1.2.
Also downgrading from 5.1.4 to 5.1.1 is going to give you a hard brick. I don't know how you didn't know that but it was clearly stated in the xda guide I was following
Basically you have to follow rootjunkys video and instead of using the file he uses in the video use the fire OS 5.1.2 file which is also available on his website.
Imortant: Do a factory reset before downgrading. I did not do that and the rooting process did not work.
Video title: How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet
After you have fire OS 5.1.2 follow the rooting process shown in another rootjunky video
Video title: How to root the Amazon Fire 5th gen 7in on Fire OS 5 1 2 SuperTool Mac linux and Windows
Note: He shows how to do the whole process while using mac but it can be done on windows awell and the windows files are already present. Instead of using the .sh file and opening the terminal double click the .bat file and follow along.
You can use his SuperTool to put the play store app and fire flash app.
Note: For some reason fire flash was not working properly for me by using the SuperTool, so I just installed it from the google play store.
Now you should have rooted fire OS 5.1.2 along with superSU. Now with the fire flash app and you can download any rom that you want to flash. Follow the steps in the video for instructions
Video title: Amazon Fire 5th gen AOSP Nexus rom install with Flash Fire app
Hope this helps.
All credit to rootjunky
erikthebikeman said:
Yeah, I read the same thing and I bought it on Prime day. When's the 5.14 tool going to come out? I know, beggars... I really think it's silly to have to downgrade and risk bricking it when normal root for those OS versions don't have such a concern.
Click to expand...
Click to collapse
It's not a matter of someone getting off their keister and whipping up a "tool" (presumably you are talking about root) that works with FireOS 5.1.4 or whatever the latest version is. Like many manufactures Amazon actively discourages rooting devices and attempt to block known exploits. It's a cat and mouse game. We may see a "tool" soon, much further down the road or never. Be happy you can root the device at all and be thankful for the individuals who unselfishly share their time and talents with the community.
Thanks nefarian.
The problem was that the guide I was referred to for getting CM onto it already assumed it had been rooted, and when I started googling and looking on the different guides on rootjunky there were so many coming from different angles but nothing giving the clear start to end steps for what I wanted to do, for a newbie it was very confusing. Plus in the guide I was following (a rootjunky one) he had an older version of the OS and the toolkit had different files/folders to what are in it now, so I guess at that time there was no mentioned of 5.1.4 and not being able to go back.
After thinking I needed to downgrade the OS I found the one for unbrinking and downgrading and did that fine to 5.1.2, but then when I tried the superkit it still said it was too new, so I tried to downgrade further, which is when I bricked it.
There was no mention of it on the video..... other than a bloody great overlay in the corner, which must have been added later on, and probably because I was tearing my hair out and getting confused I didn't spot it. That's my excuse anyway!
Thanks for your help, I'll have a go with the new one on Monday. So instead of trying to find an all in one guide, I need to find guide for the steps in this order;
1 - do a factory reset on the device (from the device settings, or do I need to do it in the bootloader settings?)
2 -downgrade to 5.1.2 (I should be able to do this now)
3 - root the device (and install supersu?)
4 - install CM
Then it should have full CM and none of the Amazon OS left.
I'm not missing any steps there am I?
Thanks again!
Bob Boblaw said:
Thanks nefarian.
The problem was that the guide I was referred to for getting CM onto it already assumed it had been rooted, and when I started googling and looking on the different guides on rootjunky there were so many coming from different angles but nothing giving the clear start to end steps for what I wanted to do, for a newbie it was very confusing. Plus in the guide I was following (a rootjunky one) he had an older version of the OS and the toolkit had different files/folders to what are in it now, so I guess at that time there was no mentioned of 5.1.4 and not being able to go back.
After thinking I needed to downgrade the OS I found the one for unbrinking and downgrading and did that fine to 5.1.2, but then when I tried the superkit it still said it was too new, so I tried to downgrade further, which is when I bricked it.
There was no mention of it on the video..... other than a bloody great overlay in the corner, which must have been added later on, and probably because I was tearing my hair out and getting confused I didn't spot it. That's my excuse anyway!
Thanks for your help, I'll have a go with the new one on Monday. So instead of trying to find an all in one guide, I need to find guide for the steps in this order;
1 - do a factory reset on the device (from the device settings, or do I need to do it in the bootloader settings?)
2 -downgrade to 5.1.2 (I should be able to do this now)
3 - root the device (and install supersu?)
4 - install CM
Then it should have full CM and none of the Amazon OS left.
I'm not missing any steps there am I?
Thanks again!
Click to expand...
Click to collapse
- no need for a factory reset at any point; offers no benefit for what you are trying to accomplish.
- installation of SuperSU (replacing Kinguser and related Kingroot cruft) after rooting is highly recommended prior to using FlashFire or any other tool that messes with the system partition. The SuperTool can facilitate this otherwise ugly task.
- if you are struggling with RootJunky videos you should give serious consideration to the challenges of installing a custom rom. It doesn't get any easier going forward.
Thanks. I managed to root my Nvidia Shield TV fine so I should be able to do it, I just needed to be clear of the full process from start to finish, and as I wasn't starting from the beginning of the process that made it more confusing. The rootjunky videos are great, but when someone is saying you can use this or that or do this or that it's putting choices and variables in to the mix so it's not a straighforward step by step, and when the kits and the webpages shown on the videos have changed since they were made, for someone trying to piece the info together it takes a bit more time.
Maybe I should point out that I didn't look on here initially when I started trying to do it, I basically saw the fire on offer mentioned on a forum I use and someone said yeah, it's easy to root and get CM on if, just user this video, with the link to a rootjunky YouTube video which didn't mention the prerequisite of already having downgraded the OS (why would it) so in hindsight I didn't start at the right place or have the best information.
After reading through some stuff on here (and that's over whelming for a first timer as there is so much stuff on here for many, many devices and platforms - even just finding the Amazon fire sub forum on an iPad wasn't easy!) I'm getting a better idea for attempt two.
I'll get there, and at least I know how to not brick it now! :good:
OK, so making progress. I have downgraded the new one fine, it now has 5.1.2 of the Fire OS.
I've used rootjunkys supertool to root the device with Kingmaker, which then installed SuperSU, and I finally uninstalled Kingmaker/Purity.
So I now have a rooted Fire, which is great. I have also installed the Google Play store, disabled OTA updates and removed ads from the lock screen. But I don't want the Amazon OS on it (pretty fugly isn't it!), so the next step, flashing it with CM.
What guide would be best for a Fire with 5.1.2 on it? When I look at the Rootjunkys guide for installing CM on the Fire (https://www.youtube.com/watch?v=4dwguHoxTvo&feature=youtu.be) the super tool kit does differ, and the one I downloaded from his link only has the tool for doing it for OS 5.0.1, so it won't let me boot into TWRP recovery. What would be the best tools/guide/method to use for installing CM onto a Fire with 5.1.2?
Thanks
Bob Boblaw said:
OK, so making progress. I have downgraded the new one fine, it now has 5.1.2 of the Fire OS.
I've used rootjunkys supertool to root the device with Kingmaker, which then installed SuperSU, and I finally uninstalled Kingmaker/Purity.
So I now have a rooted Fire, which is great. I have also installed the Google Play store, disabled OTA updates and removed ads from the lock screen. But I don't want the Amazon OS on it (pretty fugly isn't it!), so the next step, flashing it with CM.
What guide would be best for a Fire with 5.1.2 on it? When I look at the Rootjunkys guide for installing CM on the Fire (
&feature=youtu.be) the super tool kit does differ, and the one I downloaded from his link only has the tool for doing it for OS 5.0.1, so it won't let me boot into TWRP recovery. What would be the best tools/guide/method to use for installing CM onto a Fire with 5.1.2?
Thanks
Click to expand...
Click to collapse
- Kingroot/Purify, not Kingmaker/Purity
- I can't think of a better suite of guides than the videos produced by RootJunky
- use FlashFire 0.51 to install (flash) the rom of your choice
- OP for Nexus rom has video link and and basic FlashFire guidance
- get over the minor variations in the language/tools used to support this device between the making of videos and the latest release.
Bob Boblaw said:
OK, so making progress. I have downgraded the new one fine, it now has 5.1.2 of the Fire OS.
I've used rootjunkys supertool to root the device with Kingmaker, which then installed SuperSU, and I finally uninstalled Kingmaker/Purity.
So I now have a rooted Fire, which is great. I have also installed the Google Play store, disabled OTA updates and removed ads from the lock screen. But I don't want the Amazon OS on it (pretty fugly isn't it!), so the next step, flashing it with CM.
What guide would be best for a Fire with 5.1.2 on it? When I look at the Rootjunkys guide for installing CM on the Fire (https://www.youtube.com/watch?v=4dwguHoxTvo&feature=youtu.be) the super tool kit does differ, and the one I downloaded from his link only has the tool for doing it for OS 5.0.1, so it won't let me boot into TWRP recovery. What would be the best tools/guide/method to use for installing CM onto a Fire with 5.1.2?
Thanks
Click to expand...
Click to collapse
1. Get the CM rom and put it in the tablet from here: http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416
2. Install FlashFire 0.51 from play store or use the SuperTool
3. Follow the video instructions and instead of the nexus rom use the CM rom you downloaded:
Thanks guys. All going well. CM12 is now installed using that Nexus guide. However, because he used Nexus the Play store was installed by default, which CM12 doesn't have.
Looking here - https://wiki.cyanogenmod.org/w/Google_Apps#Installation - I need to download Google Apps and install it, but which package for the Fire 7 5th gen? There are a number of variants to choose from. Looks like using twrp it would have been a pico one, but as it's a new OS a different one is needed?
So it's ARM device, Android 5.1 and Nano variant?
That gives me a zip file, but I can't work out how to install it. The videos I've found all have it as being installed as part of the OS installation via twrp. Should I have installed gapps when I installed the CM12.1 OS, or can I still install it later?
When I go into the boot menu the only install option is to apply update from ADB, wipe data/factory reset, wipe cache partition, reboot to bootloader or power down/reboot.
I tried to use apply update from ADB and did "adb sideload gapps-filename.zip" but it failed to complete the install and went back to the boot menu.
What do I need to do to get Play Store on there?
Thanks again
Bob Boblaw said:
Thanks guys. All going well. CM12 is now installed using that Nexus guide. However, because he used Nexus the Play store was installed by default, which CM12 doesn't have.
Looking here - https://wiki.cyanogenmod.org/w/Google_Apps#Installation - I need to download Google Apps and install it, but which package for the Fire 7 5th gen? There are a number of variants to choose from. Looks like using twrp it would have been a pico one, but as it's a new OS a different one is needed?
So it's ARM device, Android 5.1 and Nano variant?
That gives me a zip file, but I can't work out how to install it. The videos I've found all have it as being installed as part of the OS installation via twrp. Should I have installed gapps when I installed the CM12.1 OS, or can I still install it later?
When I go into the boot menu the only install option is to apply update from ADB, wipe data/factory reset, wipe cache partition, reboot to bootloader or power down/reboot.
I tried to use apply update from ADB and did "adb sideload gapps-filename.zip" but it failed to complete the install and went back to the boot menu.
What do I need to do to get Play Store on there?
Thanks again
Click to expand...
Click to collapse
Reinstall FlashFire 0.51 (here) on CM 12.1 then use it to flash the GAapps package. Agree with your selection: ARM/5.1/nano.
Ah, great, thank you, yep, that's got it on there.
Excellent! All modded and running very quickly! Thanks for the help guys, I appreciate the patience.
Not much space on these Fire's is there, it's already telling me it's low on space and I've only installed MediaMonkey!
Two more quick questions and I'll leave you alone....!
Is it possible to have the SD card to be used as combined storage? For example, my Shield TV lets me 'add' the SD card to the main storage so it sees it all as one instead of a second removable device, so can install apps on it, etc. If this possible with Cyanogenmod? (Not sure what you'd call that feature to search for it!) Thankfully the main reason I bought it was to help manage my music with MediaMonkey so I won't be installing lots on it, but if it is possible it would be useful.
Second, with regard to OS updates on CM, are they automated or do they need to be done manually (and, if so, with care?)
Thanks again!
Bob Boblaw said:
Two more quick questions and I'll leave you alone....!
Is it possible to have the SD card to be used as combined storage?
Second, with regard to OS updates on CM, are they automated or do they need to be done manually ...
Click to expand...
Click to collapse
Short answer: 'yes'. There are various approaches to utilizing SD cards for app installation/storage each with pros, cons and compromises. I highly recommend using a tool that leverages 'symbolic links' which is by far the most reliable method. An example is Link2SD which you can find in the Play Store.
All custom roms for this device are updated manually via FlaahFire or TWRP (if available). Instructions can usually be found in the OP.
@Bob Boblaw
did you open up the file manager and install the flashfire.apk? I am on the same problem you had on your post #11, but my problem I ran into now is flash fire says "root access could not be acquired" otherwise this would be a easy to do.
I think I might have to reinstall everything and start over. >_<
Yes, I copied it over via USB and installed it from the file manager. Do you have root enabled in the developer settings, I enabled it for adb and apps.
Bob Boblaw said:
Yes, I copied it over via USB and installed it from the file manager. Do you have root enabled in the developer settings, I enabled it for adb and apps.
Click to expand...
Click to collapse
Yes! Thank you, that is what I had missed plus I didn't reboot my device so took like 15mins trying to figure out why it wasn't still working.
Glad you got it working ! :good:
Great post guys!! I am getting ready to root my fire OS 5.1.4 and this helps me greatly! Been searching for a downgrade guide and this is it! Have one question is Cm only recovery program or is there a TWRP version for this ? I would think that lastest TWRP would work since its all android but have to ask .I like TWRP myself cause i have it on rooted tablets
thunderman98 said:
Great post guys!! I am getting ready to root my fire OS 5.1.4 and this helps me greatly! Been searching for a downgrade guide and this is it! Have one question is Cm only recovery program or is there a TWRP version for this ? I would think that lastest TWRP would work since its all android but have to ask .I like TWRP myself cause i have it on rooted tablets
Click to expand...
Click to collapse
You can not boot/install/use twrp on this device unless running FireOS 5.0.1 or lower. Nor can you rollback to any version below 5.1.2 without bricking the device. FlashFire is the tool of choice for installing roms and performing other maintenance tasks that are typically done in a custom recovery environment.
Quick backstory; I rooted my 5th Gen 7" Fire a loooong time ago, with I believe a version of Rootjunky's supertool. Removed auto OS updates, all that good stuff. Accordingly, I cannot access the OS info via System Updates (tapping it gives a blank screen for a moment, then goes back to the main settings screen). I have Google Play & services installed.
So, I tried today to use the Amazon Appstore, and I'm getting a "Network Unreachable" error right when the app launches. I can't use any functions of the store. I'm thinking it's maybe because the app is such a relatively old version, Amazon's network is giving it grief, but I don't know for certain.
Like I said, I can't see for sure what OS version I have, but it has to be one of the first iterations of 5.something.
If anyone has run into this, or has any suggestions to get the appstore working again, I'm all ears. I did a factory reset, both from in the OS and from the Amazon recovery (complete with wiping cache), with no luck. Thanks in advance for any help.
scooter1979 said:
Quick backstory; I rooted my 5th Gen 7" Fire a loooong time ago, with I believe a version of Rootjunky's supertool. Removed auto OS updates, all that good stuff. Accordingly, I cannot access the OS info via System Updates (tapping it gives a blank screen for a moment, then goes back to the main settings screen). I have Google Play & services installed.
So, I tried today to use the Amazon Appstore, and I'm getting a "Network Unreachable" error right when the app launches. I can't use any functions of the store. I'm thinking it's maybe because the app is such a relatively old version, Amazon's network is giving it grief, but I don't know for certain.
Like I said, I can't see for sure what OS version I have, but it has to be one of the first iterations of 5.something.
If anyone has run into this, or has any suggestions to get the appstore working again, I'm all ears. I did a factory reset, both from in the OS and from the Amazon recovery (complete with wiping cache), with no luck. Thanks in advance for any help.
Click to expand...
Click to collapse
Have you checked the clock? Sometimes, if the time is off, my store will break. Other than that, I'd recommend you download EZ File explorer, google form the most up to date amazon store apk, uninstall yours and give it a fresh install, especially if you feel out of date is the problem.
I'd also recommend you download a custom rom and flashfire and see if you can't fix that OS info problem, especially since you've already wiped all your data anyway.
elementalcobalt said:
Have you checked the clock? Sometimes, if the time is off, my store will break. Other than that, I'd recommend you download EZ File explorer, google form the most up to date amazon store apk, uninstall yours and give it a fresh install, especially if you feel out of date is the problem.
I'd also recommend you download a custom rom and flashfire and see if you can't fix that OS info problem, especially since you've already wiped all your data anyway.
Click to expand...
Click to collapse
This won't work:
- the version of Amazon's app store is different on FireOS; I don't believe it's available for download
- I did not see the OP had wiped his data; the OS info problem is related to blocking OTA updates
---------- Post added 02-12-2017 at 12:12 AM ---------- Previous post was 02-11-2017 at 11:56 PM ----------
scooter1979 said:
Quick backstory; I rooted my 5th Gen 7" Fire a loooong time ago, with I believe a version of Rootjunky's supertool. Removed auto OS updates, all that good stuff. Accordingly, I cannot access the OS info via System Updates (tapping it gives a blank screen for a moment, then goes back to the main settings screen). I have Google Play & services installed.
So, I tried today to use the Amazon Appstore, and I'm getting a "Network Unreachable" error right when the app launches. I can't use any functions of the store. I'm thinking it's maybe because the app is such a relatively old version, Amazon's network is giving it grief, but I don't know for certain.
Like I said, I can't see for sure what OS version I have, but it has to be one of the first iterations of 5.something.
If anyone has run into this, or has any suggestions to get the appstore working again, I'm all ears. I did a factory reset, both from in the OS and from the Amazon recovery (complete with wiping cache), with no luck. Thanks in advance for any help.
Click to expand...
Click to collapse
Best solution is to install a custom ROM; however you seem satisfied with FireOS.
Next best solution IMO is to reload FireOS (which includes Amazon's app store) but you will probably want to stick with version 5.0.1 if that's what is currently installed. Obvious problem is you can't determine that through normal means. Have to be careful here; if you attempt to reload 5.0.1 and your device is currently on 5.1.x or above it will brick. You would also need to reroot, reblock OTA updates, etc. In short, everything you did before. With no guarantee it will fix your original problem (although I think it will).
One way to test for 5.0.1 is to see if it will boot TWRP. However, that can be messy if you are unfamiliar with fastboot and/or have never established a connection with the device in question.
@steve8x8 - I seem to recall you wrote a tool that can query current component/system levels. Thoughts?
p.s. You could also go with FireOS 5.3.1 which is the last build that can be rooted at present. No brick risk as 5.3.1 is >= the current version of FireOS on the device.
elementalcobalt said:
Have you checked the clock? Sometimes, if the time is off, my store will break. Other than that, I'd recommend you download EZ File explorer, google form the most up to date amazon store apk, uninstall yours and give it a fresh install, especially if you feel out of date is the problem.
I'd also recommend you download a custom rom and flashfire and see if you can't fix that OS info problem, especially since you've already wiped all your data anyway.
Click to expand...
Click to collapse
It's not the clock, that's as it should be.
Davey126 said:
This won't work:
- the version of Amazon's app store is different on FireOS; I don't believe it's available for download
- I did not see the OP had wiped his data; the OS info problem is related to blocking OTA updates
---------- Post added 02-12-2017 at 12:12 AM ---------- Previous post was 02-11-2017 at 11:56 PM ----------
Best solution is to install a custom ROM; however you seem satisfied with FireOS.
Next best solution IMO is to reload FireOS (which includes Amazon's app store) but you will probably want to stick with version 5.0.1 if that's what is currently installed. Obvious problem is you can't determine that through normal means. Have to be careful here; if you attempt to reload 5.0.1 and your device is currently on 5.1.x or above it will brick. You would also need to reroot, reblock OTA updates, etc. In short, everything you did before. With no guarantee it will fix your original problem (although I think it will).
One way to test for 5.0.1 is to see if it will boot TWRP. However, that can be messy if you are unfamiliar with fastboot and/or have never established a connection with the device in question.
@steve8x8 - I seem to recall you wrote a tool that can query current component/system levels. Thoughts?
p.s. You could also go with FireOS 5.3.1 which is the last build that can be rooted at present. No brick risk as 5.3.1 is >= the current version of FireOS on the device.
Click to expand...
Click to collapse
You are correct, I am happy with the FireOS.
I've played in fastboot before, and given EXACT instructions, I can regurgitate results, but it's not my native tongue. I don't know if the appstore version is locked to the OS version, but according to Appstore Settings under the manage Amazon apps section, I'm rocking release-9.1011.5.1.39.0_2000145010, last updated 2/12/15. Any way to link that with OS version?
If no more info can be gleaned from my device, either from the appstore version or something steve8x8 may have, I may just load 5.3.1 on and run from there. Kinda rather not, but I'd kinda rather not not have appstore access.
scooter1979 said:
... I've played in fastboot before, and given EXACT instructions, I can regurgitate results, but it's not my native tongue. I don't know if the appstore version is locked to the OS version, but according to Appstore Settings under the manage Amazon apps section, I'm rocking release-9.1011.5.1.39.0_2000145010, last updated 2/12/15. Any way to link that with OS version?
If no more info can be gleaned from my device, either from the appstore version or something steve8x8 may have, I may just load 5.3.1 on and run from there. Kinda rather not, but I'd kinda rather not not have appstore access.
Click to expand...
Click to collapse
To my knowledge there is no direct correlation of appstore version to FireOS version. Obviously there's a range but we'd need a 1-1 match to draw a comfortable conclusion.
You can test TWRP bootability by following the guidance in this post. If TWRP boots you can safely sideload FireOS 5.0.1 from here using instructions in this thread (posts #1 and #2). That said, if you have no intention of every installing a custom ROM there really isn't any advantage to retaining an older bootloader. If that's the case might as well sideload FireOS 5.3.1. Be aware there is no going back if you take this step.
Davey126 said:
To my knowledge there is no direct correlation of appstore version to FireOS version. Obviously there's a range but we'd need a 1-1 match to draw a comfortable conclusion.
You can test TWRP bootability by following the guidance in this post. If TWRP boots you can safely sideload FireOS 5.0.1 from here using instructions in this thread (posts #1 and #2). That said, if you have no intention of every installing a custom ROM there really isn't any advantage to retaining an older bootloader. If that's the case might as well sideload FireOS 5.3.1. Be aware there is no going back if you take this step.
Click to expand...
Click to collapse
Ahhhh nuts. I'm getting "FAILED (remote: unknown command)" return on my Win7 machine trying to boot TWRP, and just simple USB transmission OK output on the device. Looks like I'm over 5.0.1.
Guess it's 5.3.1 for me. I'm assuming I can just follow the directions from sd_shadow's unbrick stock recovery ADB sideload thread, yes? Thanks for all of your help, I really appreciate it.
There's a guide to find bootloader version: https://forum.xda-developers.com/amazon-fire/development/identify-bootloader-version-t3424634
Sent from my Amazon Fire using XDA Labs
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
scooter1979 said:
Ahhhh nuts. I'm getting "FAILED (remote: unknown command)" return on my Win7 machine trying to boot TWRP, and just simple USB transmission OK output on the device. Looks like I'm over 5.0.1.
Guess it's 5.3.1 for me. I'm assuming I can just follow the directions from sd_shadow's unbrick stock recovery ADB sideload thread, yes? Thanks for all of your help, I really appreciate it.
Click to expand...
Click to collapse
Just be sure that you don't accidentally update. Don't connect to WiFi until you have KingRoot, and be sure not to let the os update finish downloading. Once you connect, it will start. Some tips I found on how to avoid updates:
Davey126 said:
- use Kingroot 4.92 or lower; avoid v5.x (nearly impossible to remove)
- partial OTA update files are erased each time the device reboots
- KingRoot reboots frequently
- find a slow AP (library, coffee shop, etc) to thoddle the pace of downloads
- enable WiFi only after KingRoot starts and kill it when run completes
- force reboot device if KingRoot hangs for a prolonged period
- you may have to repeat the process multiple times
- there are trickier approaches (eg: IP/domain blocking) with variable results; the above playbook has worked well for most
- good luck
Click to expand...
Click to collapse
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
Just be sure that you don't accidentally update. Don't connect to WiFi until you have KingRoot, and be sure not to let the os update finish downloading. Once you connect, it will start. Some tips I found on how to avoid updates:
s
Click to expand...
Click to collapse
Along with not hooking up wifi immediately, I was thinking of using rootjunky's supertool for root & update blocking, as the tool says it's now compatible with 5.3.1. Should be good enough, as long as I don't connect to a network until ALL of the supertool fun is done (I hope).
scooter1979 said:
Along with not hooking up wifi immediately, I was thinking of using rootjunky's supertool for root & update blocking, as the tool says it's now compatible with 5.3.1. Should be good enough, as long as I don't connect to a network until ALL of the supertool fun is done (I hope).
Click to expand...
Click to collapse
You need WiFi to root. That's why you need to be careful, since update starts quickly. Here's the thread the quote was from: https://forum.xda-developers.com/amazon-fire/help/dilemma-t3545062
If you can block the domains linked to in that thread, that'll help. It's not necessary, but it's a good idea.
EDIT: here's the post with them:
HughJeffner said:
Using stock 5.3.1 fresh install here are the domain names used in the update process:
softwareupdates.amazon.com
amzdigital-a.akamaihd.net
The first one is the actual update check, blocking DNS lookup of this domain effectively disabled auto-updates for me YMMV
The second domain name is where the firmware is actually downloaded from (not verified but seems probable). Note that this could change depending on how the update check is implemented.
I recommend blocking DNS resolution of softwareupdates.amazon.com if practical in your situation
Click to expand...
Click to collapse
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
You need WiFi to root. That's why you need to be careful, since update starts quickly. Here's the thread the quote was from: https://forum.xda-developers.com/amazon-fire/help/dilemma-t3545062
If you can block the domains linked to in that thread, that'll help. It's not necessary, but it's a good idea.
Click to expand...
Click to collapse
Ohhhhh, I didn't realize Kingroot needs internet access... Besides that, I saw in the tool's changelogs that it even removes Kingroot & puts the normal supersu in the system, so I thought everything was more or less a "normal" rooting procedure. Whoops. Thank you, I'll be DNS blocking before anything.
scooter1979 said:
Ohhhhh, I didn't realize Kingroot needs internet access... Besides that, I saw in the tool's changelogs that it even removes Kingroot & puts the normal supersu in the system, so I thought everything was more or less a "normal" rooting procedure. Whoops. Thank you, I'll be DNS blocking before anything.
Click to expand...
Click to collapse
It removes KingRoot after using it to root. AFAIK, KingRoot is the only thing that can root these tablets. Personally, I'd recommend finding your bootloader version and flashing that, but it's just a personal preference, and has no practical difference unless you have 5.0.x, which you don't. I just like having oldest I can in case a downgrade method is ever found.
Also I may have an updated appstore apk from my brother's 5.3.2.1 tablet, let me check.
EDIT: Nope, I don't. I do, however, have an (old) apk from the Amazon website. See if installing this version helps. Just out of curiosity, could you attach the apk from your current appstore? I'm wondering if it will install on Fire Nexus. The UI looks much better than the version I have downloaded.
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
Just out of curiosity, could you attach the apk from your current appstore? I'm wondering if it will install on Fire Nexus. The UI looks much better than the version I have downloaded.
Sent from my Amazon Fire using XDA Labs
Click to expand...
Click to collapse
I'll be happy to if you give me the path, or even the full name of the apk so I can search via root explorer.
scooter1979 said:
I'll be happy to if you give me the path.
Click to expand...
Click to collapse
If you have a file manager, search /system/app and /system/priv-app for com.amazon. venezia. Or, use an app like titanium backup to back it up.
It's taking forever to upload the apk I'm using, so here's the link if you want to test if it works: https://www.amazon.com/appstore_android_app
If not, I think you will need to reflash, unfortunately.
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
There's a guide to find bootloader version: https://forum.xda-developers.com/amazon-fire/development/identify-bootloader-version-t3424634
Click to expand...
Click to collapse
Used this method, I'm on 5.1.1 (5.4.1_112720 5.1.1). Dagnabbit, missed it by that much.
scooter1979 said:
Used this method, I'm on 5.1.1 (5.4.1_112720 5.1.1). Dagnabbit, missed it by that much.
Click to expand...
Click to collapse
Then I'd recommend flashing 5.1.1. Like I said, if a downgrade method is found, it will probably be for older versions. Plus it's harder to brick, since only one or two versions are below it.
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
It's taking forever to upload the apk I'm using, so here's the link if you want to test if it works: https://www.amazon.com/appstore_android_app
If not, I think you will need to reflash, unfortunately.
Sent from my Amazon Fire using XDA Labs
Click to expand...
Click to collapse
No go. Got a "Application Not Installed" error.
PorygonZRocks said:
Then I'd recommend flashing 5.1.1. Like I said, if a downgrade method is found, it will probably be for older versions. Plus it's harder to brick, since only one or two versions are below it.
Sent from my Amazon Fire using XDA Labs
Click to expand...
Click to collapse
The thing there is, if the issue is indeed related to the age of the appstore, which doesn't look like it has been updated since the OS was, sideloading the same version would put me in the same boat I'm in now. If I drop 5.3.1 on there, that should fix me, assuming the age of the store is the underlying issue. Unless there's something I'm missing.
Ok, my venezia is attached.
scooter1979 said:
No go. Got a "Application Not Installed" error.
The thing there is, if the issue is indeed related to the age of the appstore, which doesn't look like it has been updated since the OS was, sideloading the same version would put me in the same boat I'm in now. If I drop 5.3.1 on there, that should fix me, assuming the age of the store is the underlying issue. Unless there's something I'm missing.
Click to expand...
Click to collapse
A while back, I found a tutorial on how to upgrade system, but keep bootloader the same. Let me look...
Also, if it isn't the age of the app store, it has no effect. You could also try Amazon Underground app. It has a different package name, so it will install alongside the Appstore you have. This way, you can see if it has to do with the store or if it's just not working.
EDIT: Having trouble finding the link. I think what it was is you can download an update file, rename it from *.bin to *.zip, extract system.img, put it on the device, flash it, root, and disable ota immediately. I'll keep looking.
Sent from my Amazon Fire using XDA Labs
Umm, you guys?...
Ya wanna hear something wacky? Just for the fart of it, I ran the apk I just uploaded on my own device, and, um, the store works now. Zero problems. Connects just fine.
Now don't I feel like a horse's patoot?
Well, if nothing else, I learned what DNS to block if I upgrade to 5.3.1, how to check my bootloader via hex editor, and to rely on the kindness of strangers to fall bassackwards into an easy solution. Yeesh.
scooter1979 said:
Ya wanna hear something wacky? Just for the fart of it, I ran the apk I just uploaded on my own device, and, um, the store works now. Zero problems. Connects just fine.
Now don't I feel like a horse's patoot?
Well, if nothing else, I learned what DNS to block if I upgrade to 5.3.1, how to check my bootloader via hex editor, and to rely on the kindness of strangers to fall bassackwards into an easy solution. Yeesh.
Click to expand...
Click to collapse
Oh. Well, I found the thread, if you want. It gives instructions for FlashFire as well.
https://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Sent from my Amazon Fire using XDA Labs
---------- Post added at 07:37 AM ---------- Previous post was at 07:32 AM ----------
scooter1979 said:
Ok, my venezia is attached.
Click to expand...
Click to collapse
Was there a .odex in the folder, and/or a lib folder? If so, could you also upload that? If not, then it appears it will not work. Shame. Thanks for the apk.
Sent from my Amazon Fire using XDA Labs
hi guys. I was running the Nexus fire Rom using flashfire. its was on 5.1.2. I tried to flash the new updated version from this year of nexus fire from a clean wipe and now I dont have play store or anything. i cant remember the intial root process...its been while. I'm a little fuzzy as to how everything work cuz of the locked bootloader.
I dont have play store. i tried to side load flashfire into my downloads from pc but it wont show. it say dowloads empty. i literally have clock, calculator, downloads, settings and SU. i dunno what to do at this point. why arent the apks showing in downloads? any help is apprecaited. sad to see there is no real root yet..
havikx said:
hi guys. I was running the Nexus fire Rom using flashfire. its was on 5.1.2. I tried to flash the new updated version from this year of nexus fire from a clean wipe and now I dont have play store or anything. i cant remember the intial root process...its been while. I'm a little fuzzy as to how everything work cuz of the locked bootloader.
I dont have play store. i tried to side load flashfire into my downloads from pc but it wont show. it say dowloads empty. i literally have clock, calculator, downloads, settings and SU. i dunno what to do at this point. why arent the apks showing in downloads? any help is apprecaited. sad to see there is no real root yet..
Click to expand...
Click to collapse
There is "real" root on FireOS 5.1.2. Best option is to sideload (reinstall) that build of FireOS via stock recovery then use the SuperTool to root and prepare your device for installation of Nexus. Going through that process will refresh your memory. A few tips:
- be sure to get the 5.1.2 binary; no higher/lower
- don't register with Amazon on initial boot
- keep off WiFi to avoid forced OTA update to an unrootable FireOS build
- be sure to flash the version of Nexus ROM that includes GAaps; you likely used the ROM only variant on your last refresh attempt
Davey126 said:
There is "real" root on FireOS 5.1.2. Best option is to sideload (reinstall) that build of FireOS via stock recovery then use the SuperTool to root and prepare your device for installation of Nexus. Going through that process will refresh your memory. A few tips:
- be sure to get the 5.1.2 binary; no higher/lower
- don't register with Amazon on initial boot
- keep off WiFi to avoid forced OTA update to an unrootable FireOS build
- be sure to flash the version of Nexus ROM that includes GAaps; you likely used the ROM only variant on your last refresh attempt
Click to expand...
Click to collapse
now that you mention, thats probably exactly what i forgot to do. Also, i'm on 5.1.1. My bad. As far as i know, 5.1.1 system still has that locked bootloader preventing android upgrades. Though I havent kept up with development too much. Ill get started on returning to stock and rerooting. Hope this little tablet get a breakthru in the near future!
ok, so i sideloaded flashfire thru ADB and decided to switch over to lineage. thanks for your help. easier than returning to stock.
havikx said:
ok, so i sideloaded flashfire thru ADB and decided to switch over to lineage. thanks for your help. easier than returning to stock.
Click to expand...
Click to collapse
Agreed. The technique you used doesn't work for everyone; hence my generic 'return-to-stock and redo everything' guidance. Glad you are back in business with minimum fuss.