Related
So I'm getting my new Fire tablet tomorrow, got it at the $35 sale...
Planning to not allow it to connect to WiFi till I can load Google Play and disable OTA using the script given here (already did it on another one and it worked great) so it doesn't get 5.1.1.
Two questions:
1. How can I tell if it's running 5.0.0 or 5.0.1 (without doing the software update check obviously...)
(also not sure how to see it once OTA is disabled, any other place it shows up?)
2. If it's on 5.0.0. can I sideload the 5.0.1 image using ADB, seems that I should be on that version to get Google Play to work OK.
Thanks
I think Amazon is shipping these new ones with 5.1.1, but if they don't, just go to the latest 5.0.1 in RootJunky's video. After that is done, just skip the part in Setup which requires you to connect to Wi-Fi, disable the OTA Apks, and connect to Wi-Fi. You should be set from there, and you can do whatever modifications you want.
Vlasp said:
I think Amazon is shipping these new ones with 5.1.1, but if they don't, just go to the latest 5.0.1 in RootJunky's video. After that is done, just skip the part in Setup which requires you to connect to Wi-Fi, disable the OTA Apks, and connect to Wi-Fi. You should be set from there, and you can do whatever modifications you want.
Click to expand...
Click to collapse
Any reports of people receiving Fire's preloaded with 5.1.1?
First things first... Don't connect to wifi and disable ota updates.. Root.. Flash cm12.1 and never look back!
@87racer would love if you could capture the 5.1.1 update for us!
tuckerwagner said:
@87racer would love if you could capture the 5.1.1 update for us!
Click to expand...
Click to collapse
thanks @tuckerwagner, looks like we @p0lt just posted one for us. downloading now, should help us discern what happens during the 5.1.1 upgrade and maybe recover our bricks.
87racer said:
thanks @tuckerwagner, looks like we @p0lt just posted one for us. downloading now, should help us discern what happens during the 5.1.1 upgrade and maybe recover our bricks.
Click to expand...
Click to collapse
SWEET! I'd help but in don't know where to even start. Good luck!
The update from 5.0.1 to 5.1.1 isn't instantaneous. The device has to download the new version before installing it. Check your version and if it starts to download 5.1.1, just turn off your wifi. It will say "Download paused." Then disable OTAs or flash one of the two ROMs.
That said, it is highlyunlikely that you would get one that is still on 5.0.0. The one I got last week was already on 5.0.1
register it first so you can contact support for a replacement if it is "defective"... for my $35 fire all you had to do was enable adb, reboot to fastboot, and continue from there. Didn't mess with the fire OS at all except for registering the device.
levytom said:
So I'm getting my new Fire tablet tomorrow, got it at the $35 sale...
Planning to not allow it to connect to WiFi till I can load Google Play and disable OTA using the script given here (already did it on another one and it worked great) so it doesn't get 5.1.1.
Two questions:
1. How can I tell if it's running 5.0.0 or 5.0.1 (without doing the software update check obviously...)
(also not sure how to see it once OTA is disabled, any other place it shows up?)
2. If it's on 5.0.0. can I sideload the 5.0.1 image using ADB, seems that I should be on that version to get Google Play to work OK.
Thanks
Click to expand...
Click to collapse
Update:
Got the Fire tablet and this is what I did if you want to try the same:
1. Turned on the device
2. Skipped configuration process when it asked me to connect to WiFi
3. Setting->Devicve options->System update confirmed I'm on 5.0.1 (yey) it can't update obviously since WiFi is not connected, so I'm safe for now
4. Use the 1-click script to install google play, remove ads (http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122)
5. Disable OTA using the same script (menu option 3)
6. Reboot
7. Install Gmail (cause later there's a stage where native email app doesn't work...) and email myself the pre downloaded fire launcher (http://forum.xda-developers.com/attachment.php?attachmentid=3528797&d=1446499184) which will fix it
8. Replace launcher, using the launcher replace script (http://forum.xda-developers.com/amazon-fire/general/alternative-launcher-one-click-script-t3239966)
9. install fire launcher apk (because otherwise some stuff doesn't work) - and choose not to use it when clicking the home button
What's left?
1. Didn't root <any reason to root?>
2. Write access to SD card is reported not to work, didn't try that yet... maybe by the time I need it someone will solve it
3. Hope that OTA won't happen and disabling worked... (something is probably done right, because if you try to check for update it says that updates are disabled...) hopefully that's good enough...
4. Say thanks to sd_shadow, ChrBeck, and Awesomeslayerg for the information they provided as well as many others participating in this forum... so Thanks.
levytom said:
What's left?
1. Didn't root <any reason to root?>
2. Write access to SD card is reported not to work, didn't try that yet... maybe by the time I need it someone will solve it
3. Hope that OTA won't happen and disabling worked... (something is probably done right, because if you try to check for update it says that updates are disabled...) hopefully that's good enough...
4. Say thanks to sd_shadow, ChrBeck, and Awesomeslayerg for the information they provided as well as many others participating in this forum... so Thanks.
Click to expand...
Click to collapse
1. Personal choice, but ad blocking alone makes root essential for me.
2. Oh and the SDfix app on Play store needs root for that matter... https://play.google.com/store/apps/details?id=nextapp.sdfix
3. You can now flash the 5.1.1 update as seen in the http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594 thread so wouldn't need to worry about the current update at least.
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.
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
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.