Related
I am planning to buy one this month a 8gb model 7in tablet
Once I buy it, can I root it. If so where do I need to look to root this tablet. Thank you
LASERWOLF452 said:
I am planning to buy one this month a 8gb model 7in tablet
Once I buy it, can I root it. If so where do I need to look to root this tablet. Thank you
Click to expand...
Click to collapse
That very much depends on the kind of device you plan on getting, what OS version the device ships with, and your level of familiarity with rooting. Could you give me a price point and a seller for the device you want to get? I'm guessing you want the latest Fire, which can be found here.
monster1612 said:
That very much depends on the kind of device you plan on getting, what OS version the device ships with, and your level of familiarity with rooting. Could you give me a price point and a seller for the device you want to get? I'm guessing you want the latest Fire, which can be found here.
Click to expand...
Click to collapse
pretty much what i am looking at, i dont know what OS its on and all i have is amazon gift cards to cover the rest of the rice after i sink in $30 to it for my YouTube channel, if there is a kindle fire HD that can be rooted let me know i aim for that, i dont wanna buy it and not be able to root
LASERWOLF452 said:
pretty much what i am looking at, i dont know what OS its on and all i have is amazon gift cards to cover the rest of the rice after i sink in $30 to it for my YouTube channel, if there is a kindle fire HD that can be rooted let me know i aim for that, i dont wanna buy it and not be able to root
Click to expand...
Click to collapse
That device's codename is ford, and the XDA forums for that device may be found here. This would be the wrong forum for this discussion, but I'll provide you some important things to know for the Ford (my sister has that same device, so I've done a lot of reading):
Always read the forums. This can't be stressed enough, and I highly recommend you read the forums before you even purchase the device. I haven't covered everything, and there's likely new developments coming that I've missed. I'm giving you a general primer, but this is by no means complete. Definitely read the development threads, help threads, and other device forums before you do anything with the Fire (including buying it or setting it up for the first time!).
If you get the Fire, it's possible that it'll ship with an older software version (hopefully 5.1.4 or lower). 5.1.4 isn't rootable itself, but it can be downgraded to 5.1.2 (which is rootable). Once you have root, you'll likely want a custom ROM, so make sure to get that flashed as soon as you can once rooted.
If/when you get the Fire, do NOT connect it to wifi or otherwise set up the device via Amazon's wizard. If you do, the Fire will OTA update to 5.3.1.0, which is neither rootable nor downgradable (as of the time of writing). Given time and resources, I'm sure somebody will find a root exploit for that version as well, but don't get your hopes up too quickly.
Downgrading is complex and may not work. For example - you cannot downgrade 5.3.x to 5.1.x or 5.0.x, and you also can't downgrade 5.1.x to 5.0.x. Amazon enforces anti-rollback protection checks at the hardware level if I remember correctly, and downgrading between versions like that will brick the device.
Custom recoveries (like TWRP) can't be booted, especially with 5.1.x or later bootloaders. From what I've read, one can boot TWRP via fastboot on 5.0.x releases, but that was patched with the 5.1.x bootloader. To flash ROMs, you'll need to use Chainfire's FlashFire. Again, you will need to look through the device forum for specific directions.
In short, here's what I'd recommend you do:
Keep tabs on the forums often.
When you buy, cross your fingers and hope you don't get 5.3.x preinstalled.
When you get the Fire, do NOT connect to wifi or go through the setup wizard.
Check your software version (again, don't connect to wifi). If you have 5.3.x, wait for a root exploit. If you have anything below that, read the forums and then downgrade (if necessary), root, and flash a ROM as soon as possible.
Good luck!
monster1612 said:
That very much depends on the kind of device you plan on getting, what OS version the device ships with, and your level of familiarity with rooting. Could you give me a price point and a seller for the device you want to get? I'm guessing you want the latest Fire, which can be found here.
Click to expand...
Click to collapse
monster1612 said:
That device's codename is ford, and the XDA forums for that device may be found here. This would be the wrong forum for this discussion, but I'll provide you some important things to know for the Ford (my sister has that same device, so I've done a lot of reading):
Always read the forums. This can't be stressed enough, and I highly recommend you read the forums before you even purchase the device. I haven't covered everything, and there's likely new developments coming that I've missed. I'm giving you a general primer, but this is by no means complete. Definitely read the development threads, help threads, and other device forums before you do anything with the Fire (including buying it or setting it up for the first time!).
If you get the Fire, it's possible that it'll ship with an older software version (hopefully 5.1.4 or lower). 5.1.4 isn't rootable itself, but it can be downgraded to 5.1.2 (which is rootable). Once you have root, you'll likely want a custom ROM, so make sure to get that flashed as soon as you can once rooted.
If/when you get the Fire, do NOT connect it to wifi or otherwise set up the device via Amazon's wizard. If you do, the Fire will OTA update to 5.3.1.0, which is neither rootable nor downgradable (as of the time of writing). Given time and resources, I'm sure somebody will find a root exploit for that version as well, but don't get your hopes up too quickly.
Downgrading is complex and may not work. For example - you cannot downgrade 5.3.x to 5.1.x or 5.0.x, and you also can't downgrade 5.1.x to 5.0.x. Amazon enforces anti-rollback protection checks at the hardware level if I remember correctly, and downgrading between versions like that will brick the device.
Custom recoveries (like TWRP) can't be booted, especially with 5.1.x or later bootloaders. From what I've read, one can boot TWRP via fastboot on 5.0.x releases, but that was patched with the 5.1.x bootloader. To flash ROMs, you'll need to use Chainfire's FlashFire. Again, you will need to look through the device forum for specific directions.
In short, here's what I'd recommend you do:
Keep tabs on the forums often.
When you buy, cross your fingers and hope you don't get 5.3.x preinstalled.
When you get the Fire, do NOT connect to wifi or go through the setup wizard.
Check your software version (again, don't connect to wifi). If you have 5.3.x, wait for a root exploit. If you have anything below that, read the forums and then downgrade (if necessary), root, and flash a ROM as soon as possible.
Good luck!
Click to expand...
Click to collapse
thank you for all the info. that i needed. i hope it comes with 5.1, i had a feeling not to have it on wifi but thank you for the heads up, i wont get my hopes up cause i know these companies dont wont us to root our devices even tho the gov. passed that we can do what we want with it that we paid fior
im not to worried about MM as i am staying away from phones and android devices that can no be rooted and if i am suck with one, it either be a Netflix device, camera or dust collector
my elipises tablet almost became a dust collector cause its a sucky tablet from Verizon but i was able to disable most of the bloatware without root and there is no support that well for it
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
you can downgrade and then you can root
Ubuntu_noobi said:
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
Click to expand...
Click to collapse
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Davey126 said:
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Click to expand...
Click to collapse
I've tried moving the factory update after downloading it to the DCIM, when trying to update, it states that you can't update because it's an older version of the os. Is it required to side load?
Ubuntu_noobi said:
I've tried moving the factory update after downloading it to the DCIM, when trying to update, it states that you can't update because it's an older version of the os.
Click to expand...
Click to collapse
Wrong procedure. See forum index for details, in particular the first two posts in this thread.
Ubuntu_noobi said:
Is it required to side load?
Click to expand...
Click to collapse
Yes.
So glad I found this post. Researching the same thing. Trying it out now
Sent from my iPhone using Tapatalk
yungskeeme01 said:
So glad I found this post. Researching the same thing. Trying it out now
Click to expand...
Click to collapse
Any new info to share? I still haven't been able to figure it out
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
What exactly are you trying to "figure out"? Responded a few days ago with downgrade/rollback links which includes a step-by-step video.
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
I downgraded to 5.3.1. Rooted the fire and am now running CM 12.1. Very smooth!. Took me a awhile to get since I have a Mac but got it working. Used Rootjunky's YouTube video on how to restore. That's how I downgraded. Then used his Supertool for Mac and rooted. I then installed Flashfire and put CM12 on the tablet.
Sent from my iPhone using Tapatalk
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
Davey126 already answered it here.
Davey126 said:
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Click to expand...
Click to collapse
I also bought the Fire a few days ago and I dealt with 5.3.2 by first using "adb sideload" to go to 5.3.1 and then rooting it.
I had problems with rooting via the SuperTool, as it used an old KingRoot version and after several rooting attempts when it finally succeeded, the SuperTool had problems removing KingRoot and replacing it with SuperSu (this error made it lose root somehow). Same problem occurred when I used the SuperTool but with the newest KingRoot, so instead of using the SuperTool I used newest KingRoot directly and decided not to replace it with SuperSu.
All is fine now, lockscreen ads are gone, AdAway is installed and OTA updates blocked.
amerkiller1995 said:
I used KingRoot directly and decided not to replace it with SuperSu.
Click to expand...
Click to collapse
FYI - recognize KingRoot is a shady tool whose authors have uncertain motivations. Even after rooting it continues to send/receive information without apparent reason. One has to question any app that is offered for free and aggressively resists being uninstalled. Given the unknowns I would reconsider the decision to retain KingRoot/KingUser.
amerkiller1995 said:
Davey126 already answered it here.
I also bought the Fire a few days ago and I dealt with 5.3.2 by first using "adb sideload" to go to 5.3.1 and then rooting it.
I had problems with rooting via the SuperTool, as it used an old KingRoot version and after several rooting attempts when it finally succeeded, the SuperTool had problems removing KingRoot and replacing it with SuperSu (this error made it lose root somehow). Same problem occurred when I used the SuperTool but with the newest KingRoot, so instead of using the SuperTool I used newest KingRoot directly and decided not to replace it with SuperSu.
All is fine now, lockscreen ads are gone, AdAway is installed and OTA updates blocked.
Click to expand...
Click to collapse
I had the issue with King Root as well. What I did was download a newer version and replaced in the SuperTool folder
Sent from my iPhone using Tapatalk
Davey126 said:
FYI - recognize KingRoot is a shady tool whose authors have uncertain motivations. Even after rooting it continues to send/receive information without apparent reason. One has to question any app that is offered for free and aggressively resists being uninstalled. Given the unknowns I would reconsider the decision to retain KingRoot/KingUser.
Click to expand...
Click to collapse
Yes, it certainly gives that vibe. However my Fire is just a portable anime player, it's offline and there's nothing on it except anime, so I'll let it be.
BTW KingRoot flagged AdAway as a "risk"
yungskeeme01 said:
I had the issue with King Root as well. What I did was download a newer version and replaced in the SuperTool folder
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I've done that, it's in the post you quoted. Still, in the replacing step, the SuperTool deletes KingRoot, but then fails to put SuperSu in its place, it prints some errors to the console like ERR_WRITE or something.
amerkiller1995 said:
Yes, it certainly gives that vibe. However my Fire is just a portable anime player, it's offline and there's nothing on it except anime, so I'll let it be.
BTW KingRoot flagged AdAway as a "risk"
I've done that, it's in the post you quoted. Still, in the replacing step, the SuperTool deletes KingRoot, but then fails to put SuperSu in its place, it prints some errors to the console like ERR_WRITE or something.
Click to expand...
Click to collapse
Sorry if I misread it. I used the version included and KingRoot so I replaced it in Supertool and re-rooted using SuperTool and it removed it no issues. Whatever though, it got rooted one way or another!
Sent from my iPhone using Tapatalk
Awesome I will try again tonight
Solved!!! Finally!!!
Ubuntu_noobi said:
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
Click to expand...
Click to collapse
TL;DR: THERE IS NO "One click" OPTION THAT WORKS. I DOWNLOADED ALL OF THEM. IVE TRIED EVERY DAMN ONE OF THEM. STOP SEARCHING. You MUST side load the system with the code necessary to make it capable to root. Downgrading to 5.3.1 was the secret, instead of trying to root on 5.3.2. I made a glossary of the confusing terminology, made a step by step walk through for noobs
SO, having felt encouraged by the response by people on this forum, last night I decided it was worth another try.
I finally figured out what I was missing. IF YOU CURRENTLY HAVE FIREOS VERSION 5.3.1, YOU MUST ROLL IT BACK THRU SIDE LOADING see here: SIDELOAD TUTORIAL
I tried to load straight onto the system disk and caused all kinds of problems. Once I followed that step by step, which TBH, was a lot of pausing and rewinding. I am not familiar with many terms so I made this...
Android Common Terms:
Boot: A sequence of commands written into the underlying software that tells the device what order to operate in
Bootloader: See Previous (this is the sequence I referenced previously)
Locked Bootloader: Think of trying to edit a PDF you did not create... Exactly.
ADB Fastboot: THIS IS A PROGRAM... NOT A FUNCTION. I still get this confused, thinking that it is a quicker version of the boot sequence... IT IS NOT. ADB Fastboot is a program that gives access to the base software code making it reachable to use certain sections of to "edit the PDF".
Custom Recovery: It is the new version of Windows 10 you were updating to when your crappy laptop you JUST bought came with Windows 8.1. Essentially.
Root: Remember the PDF? Well, if you work somewhere that has Adobe Reader, and you see the window on the right pop up with the ability to login to Adobe Online or whatever? Well, rooting is having login credentials to ACTUALLY edit that damn PDF.
Flash: Download from the internet, and install on your hard drive, or SD Card. It actually means you erase whatever is there completely first, then install. It's two steps, which is why they don't just call it installing... I think.
Partition: Have you ever worked in an office with cubicles? Exactly. A partition is a wall that you put up to segregate files, or programs, or whatever.
SuperTool: Based in your computer. RootJunky Went through and basically made one tool that has everything you need for rooting. PROBLEM IS THAT HE TELLS YOU TO DOWNLOAD ADB FASTBOOT AND DRIVERS AND A BUNCH OF STUFF, then says, or you can just download the SuperTool, which means, I now HAVE TWO OF ALL OF IT, and then I spend the next three hours trying to figure out if its the "custom rom that I sideload into the TWRP, or if the Flashed version of the bootloader gets added to the recovery image, but not before the drivers are flashed into the fastboot."
While this doesn't cover a lot, I hope that people in this community understand what it is like for someone unversed in the lingo to grasp exactly what is going on. I don't think we should speak like idiots and elementary students, but I also think we lose a ton of people that may have something to offer one day because they got frustrated with the terminology and gave up. Luckily, I stuck it out and gave it one last chance and I got it.
So, once I downgraded from 5.3.2 to 5.3.1, I went about trying to root the device, which was also a little confusing.
Step 1: Downgrade if you have 5.3.2 to 5.3.1
Step 2: Enable ADB and Debug in the Settings
Step 3: Hold down the Power and Volume Down button, release the power button once the device starts to reboot and a menu will popup
Step 4: Use the volume keys to access the first selection. This is how you access the "sideloading".
Step 5: Open the SuperTool, click on the batch file which should say Auto... because calling it SuperTool would be confusing
Step 6: follow the super easy instructions. Honestly.
It will walk you through the process and get you to the part about Kingroot and FlashFire and eventually root the device.
I honestly hope this helps someone. God knows it would have saved me from spending approximately 30 hours trying to figure this out.
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
I have Fire 7 5th Gen that is rooted using SuperTool on FireOS 5.1.1. I disabled auto system updates. For some reason, Ads do not appear anymore. I tried rebooting and shutting down, but none of that helped. I have ADB setup and all, not sure what to do next.
Thanks in advance
seskanda said:
I have Fire 7 5th Gen that is rooted using SuperTool on FireOS 5.1.1. I disabled auto system updates. For some reason, Ads do not appear anymore. I tried rebooting and shutting down, but none of that helped. I have ADB setup and all, not sure what to do next.
Thanks in advance
Click to expand...
Click to collapse
Likely related to killing OTA updates. Reinstall FireOS 5.1.1 if you really want those ads.
Make double sure that it's the fireOS version that's at 5.1.1, not the generic Android one. They are easily confused, and may result in bricks. If in doubt, check the bootloader timestamp (inside the partition) - should be 20150923-180133 for your OS.
If you need to reinstall/re-root, precautions are in place. You decide whether getting ads is wirth risking root at all.
Davey126 said:
Likely related to killing OTA updates. Reinstall FireOS 5.1.1 if you really want those ads.
Click to expand...
Click to collapse
I see, but we also have an old Fire HD 7 2nd gen that is rooted and still shows ads. How can it have ads but this newer one does not? If I re-install FireOS 5.1.1, will it turn off OTA updates and/or remove root?
Where can I find the right version of FireOS 5.1.1? I do not want to lose root just for some ads.
seskanda said:
I see, but we also have an old Fire HD 7 2nd gen that is rooted and still shows ads. How can it have ads but this newer one does not? If I re-install FireOS 5.1.1, will it turn off OTA updates and/or remove root?
Where can I find the right version of FireOS 5.1.1? I do not want to lose root just for some ads.
Click to expand...
Click to collapse
The SuperTool disables a bunch of different stuff depending on FireOS build; the local ad server likely got caught up in that.
Reloading FireOS will remove root and enable OTA updates. With WiFi enabled the device would immediately be exposed to an wanted update to FireOS 5.6 which can not be rooted. You also need to be confident of the current FireOS version to avoid bricking the device; see previous post by @steve8x8.
In your shoes I'd leave things as-is. But if you really need to see those ads past FireOS builds can be found here.
Davey126 said:
The SuperTool disables a bunch of different stuff depending on FireOS build; the local ad server likely got caught up in that.
Reloading FireOS will remove root and enable OTA updates. With WiFi enabled the device would immediately be exposed to an wanted update to FireOS 5.6 which can not be rooted. You also need to be confident of the current FireOS version to avoid bricking the device; see previous post by @steve8x8.
In your shoes I'd leave things as-is. But if you really need to see those ads past FireOS builds can be found here.
Click to expand...
Click to collapse
I recall choosing the options to root and disable OTA updates, and that's all. I did not pick the one to turn off lock screen ads.
So if I root and then disable OTA updates, the ads will stop completely? What does OTA updates do with lock screen ads? If that is the case, there is really no need for me to re-install FireOS at this point. I think the FireOS builds from the link you gave are fine to use.
I do not see the benefit of ads if it breaks root or keeps OTA updates on.
seskanda said:
I recall choosing the options to root and disable OTA updates, and that's all. I did not pick the one to turn off lock screen ads.
So if I root and then disable OTA updates, the ads will stop completely? What does OTA updates do with lock screen ads? If that is the case, there is really no need for me to re-install FireOS at this point. I think the FireOS builds from the link you gave are fine to use.
I do not see the benefit of ads if it breaks root or keeps OTA updates on.
Click to expand...
Click to collapse
Never saw the benefit of ads. If you are happy with the status quo there is no need to take any action. Should you decide to reload FireOS:
- be 100% sure you have the correct build; using the 'wrong' version can have unfavorable outcomes
- you'll need to reroot and assume the risk of taking an unwanted OTA update during that process
- the SuperTool throws a lot of switches; some may do more than advertised, especially on older FireOS builds
- in most cases disabling OTA updates via the SuperTool does not block ads
- you'll need to take manual actions to block OTA updates and/or lock screen ads if you want more precise control
As the old saying goes "if it ain't broke don't fix it".
Davey126 said:
Never saw the benefit of ads. If you are happy with the status quo there is no need to take any action. Should you decide to reload FireOS:
- be 100% sure you have the correct build; using the 'wrong' version can have unfavorable outcomes
- you'll need to reroot and assume the risk of taking an unwanted OTA update during that process
- the SuperTool throws a lot of switches; some may do more than advertised, especially on older FireOS builds
- in most cases disabling OTA updates via the SuperTool does not block ads
- you'll need to take manual actions to block OTA updates and/or lock screen ads if you want more precise control
As the old saying goes "if it ain't broke don't fix it".
Click to expand...
Click to collapse
Actually the ads do suck overall I agree with you, just want to know why or how to fix it, that's all.
If I use the FireOS 5.1.1 in the link provided will that be the correct build for me?
If I disconnect WiFi, will that guarantee not being force-fed an OTA update?
Which version of SuperTool is the best or most stable one? Or that does not mess up lock screen ads when disabling OTA updates?
Do you know in which case will disabling OTA updates break lock screen ads?
What do you mean by this? Let's say I did disable lock screen ads via SuperTool by accident, is any way to undo that by chance?
seskanda said:
Actually the ads do suck overall I agree with you, just want to know why or how to fix it, that's all.
If I use the FireOS 5.1.1 in the link provided will that be the correct build for me?
If I disconnect WiFi, will that guarantee not being force-fed an OTA update?
Which version of SuperTool is the best or most stable one? Or that does not mess up lock screen ads when disabling OTA updates?
Do you know in which case will disabling OTA updates break lock screen ads?
What do you mean by this? Let's say I did disable lock screen ads via SuperTool by accident, is any way to undo that by chance?
Click to expand...
Click to collapse
Lots of questions that would take much back-and-forth to definitively answer. Many would love to be in your shoes. You have a rooted, working system with no ads or notable deficits. Enjoy your device.
Davey126 said:
Lots of questions that would take much back-and-forth to definitively answer. Many would love to be in your shoes. You have a rooted, working system with no ads or notable deficits. Enjoy your device.
Click to expand...
Click to collapse
Appreciate if you could answer the first question and any question about SuperTool. Or else, if someone can chime in that'd be fine also.
seskanda said:
Appreciate if you could answer the first question and any question about SuperTool.
Click to expand...
Click to collapse
You need to verify with 100% certainty which version of FireOS your device is currently running. Many confuse Android 5.1.1, which is the base for all FireOS v5 builds with a specific FireOS version number. The latter is all that matters and should be shown under Settings->System Updates (details).
Davey126 said:
You need to verify with 100% certainty which version of FireOS your device is currently running. Many confuse Android 5.1.1, which is the base for all FireOS v5 builds with a specific FireOS version number. The latter is all that matters and should be shown under Settings->System Updates (details).
Click to expand...
Click to collapse
I see, according to Settings-->System Updates it is FireOS 5.1.1. Does that mean the one linked here is the correct build for me?
seskanda said:
I see, according to Settings-->System Updates it is FireOS 5.1.1. Does that mean the one linked here is the correct build for me?
Click to expand...
Click to collapse
Correct. You are fortunate to be on what may view to be a 'preferred' build of FireOS. IMO the chance of taking an spontaneous OTA to an unrootable build outweighs whatever benefits might be realized given your device appears to be performing as expected sans lock screen ads. As an alternative you could simply perform a factory reset. However, the risks of an unwanted OTA sneaking in remains until the device is rerooted and updates blocked. Good luck with whatever course of action you choose.
Davey126 said:
Correct. You are fortunate to be on what may view to be a 'preferred' build of FireOS. IMO the chance of taking an spontaneous OTA to an unrootable build outweighs whatever benefits might be realized given your device appears to be performing as expected sans lock screen ads. As an alternative you could simply perform a factory reset. However, the risks of an unwanted OTA sneaking in remains until the device is rerooted and updates blocked. Good luck with whatever course of action you choose.
Click to expand...
Click to collapse
Yes, I was lucky that I rooted it quickly and disabled OTA updates at the same time. The Wifi was disconnected when I did both of that. I'm thinking If I do something similar it should end up as is now. With WiFi not connected, there is zero chance of OTA update, right? Will factory reset keep root? If not, then I might as well re-install the firmware for FireOS 5.1.1.
seskanda said:
With WiFi not connected, there is zero chance of OTA update, right? Will factory reset keep root?
Click to expand...
Click to collapse
- OTA updates are delivered via WiFi which typically must be enabled to root
- Root may or may not survive a factory reset
Davey126 said:
- OTA updates are delivered via WiFi which typically must be enabled to root
- Root may or may not survive a factory reset
Click to expand...
Click to collapse
It's been awhile since I rooted this, but do not recall needing WiFi to root, why would that be required?
Well, then I should definitely try a factory reset first before re-loading the firmware.
seskanda said:
It's been awhile since I rooted this, but do not recall needing WiFi to root, why would that be required?
Well, then I should definitely try a factory reset first before re-loading the firmware.
Click to expand...
Click to collapse
Unless using the desktop (tethered) varient KingRoot receives/retrieves 'instructions' from the cloud.
Davey126 said:
Unless using the desktop (tethered) varient KingRoot receives/retrieves 'instructions' from the cloud.
Click to expand...
Click to collapse
I use SuperTool, which is desktop (tethered) so do not internet to root. Do you know if SuperTool retains root after a factory reset?
Davey126 said:
Unless using the desktop (tethered) varient KingRoot receives/retrieves 'instructions' from the cloud.
Click to expand...
Click to collapse
I use SuperTool, which is desktop (tethered) so do not need internet to root. Do you know if SuperTool retains root after a factory reset?
seskanda said:
I use SuperTool, which is desktop (tethered) so do not need internet to root. Do you know if SuperTool retains root after a factory reset?
Click to expand...
Click to collapse
Last I knew the version of KingRoot included with the SuperTool is the standalone build which DOES need internet access. As for your second question the SuperTool has nothing to do with retaining root following a factory reset.