Related
It seems that with the latest OTA update root functionality has been lost. I see that there are copies of past ROM versions available for download. Perhaps someone has the technical know-how on how to downgrade to these versions?
U need to restore with system.img using factory cable ot any other way geting fast boot mode
You don't need to downgrade the 8.9" as that is still rootable with the new version. Just re-root.
But yea get a motorola factory usb cable from ebay and and then use onelia's recovery to flash back to the previous KF2 or KFHD7 version
Nope...
DssTrainer said:
You don't need to downgrade the 8.9" as that is still rootable with the new version. Just re-root.
But yea get a motorola factory usb cable from ebay and and then use onelia's recovery to flash back to the previous KF2 or KFHD7 version
Click to expand...
Click to collapse
I'm going to have to agree with the initial poster on this thread and say that if your firmware is at 8.1.4, The Bin4ry root is NOT working. I've ran it several times even after a full factory erase / restore, and throughout the entire process all I keep seeing is "permission denied", etc., all indicating that it was unsuccessful. For example, in the terminal step where you type in the 2 commands.. BOTH said "file not found", telling me that the file was never allowed to enter the device in the first place.. in other words, blocked. YES, the process does indeed finish, but su access is certainly not there. I can side-load apks of course, etc... but any apps requiring root access do NOT work.
I have found a way to manually block OTA updates, so if someone can figure out a way to downgrade the firmware back a couple versions, I think we'll be in business.
Please don't take this post as any sort of insult to anyone's intelligence, but I'm just relaying my experiences with the Bin4ry root process. I hope we as a community can come up with a way around this so we can get some custom roms onto this beast soon. cheers.
The binary root still works as of 8.1.4. If you read the entire post for the root process, all the permission denied and file not founds are normal. The root takes advantage of the restore process. I rooted an hd 8.9 today running 8.1.4 with no problems. So unless you guys have the only two hd 8.9's that Amazon changed the software...
I can also confirm that it still works on 8.14.ive rooted about a dozen times now, don't ask you'll be bored. I've also downgraded to 8.13 without any trouble, or factory cable, and rooted afterward. That said, I did let it OTA after downgrading. Again, don't ask.
Peace
Sent from my KFJWI using xda premium
Root and Google Play for Amazon 7" Kindle Fire HD Software Version 8.1.4
fuyoo said:
It seems that with the latest OTA update root functionality has been lost. I see that there are copies of past ROM versions available for download. Perhaps someone has the technical know-how on how to downgrade to these versions?
Click to expand...
Click to collapse
fuyoo,
There is no need to downgrade, Software version roots just fine, see:
http://forum.xda-developers.com/showthread.php?t=2069117
If you get a file not found error:
http://forum.xda-developers.com/showthread.php?t=2086210
I have a Fire 5th gen tablet running v5.1.2 and am very much looking to root it with the aim of installing stock Android. Most of the resources I found online suggest the best rooting tool is KingRoot., however after several attempts and reboots it always fails to root the tablet. Although, now that I think about it, I've come across references on this site of people who were only successful on the 4th reboot; don't think I tried that many times in a row.
Unsure if this is useful information but the tablet was bought from UK Amazon store and it states a software version has been downloaded but not yet applied.
What options do I have to root the tablet? If there is a better tool out there for the job, please let me know. Likewise, if all I need to do is downgrade the software, I'll try it. I'll do anything to rid it of Amazon's-branded version of Android.
miguelg_ said:
I have a Fire 5th gen tablet running v5.1.2 and am very much looking to root it with the aim of installing stock Android. Most of the resources I found online suggest the best rooting tool is KingRoot., however after several attempts and reboots it always fails to root the tablet. Although, now that I think about it, I've come across references on this site of people who were only successful on the 4th reboot; don't think I tried that many times in a row.
Unsure if this is useful information but the tablet was bought from UK Amazon store and it states a software version has been downloaded but not yet applied.
What options do I have to root the tablet? If there is a better tool out there for the job, please let me know. Likewise, if all I need to do is downgrade the software, I'll try it. I'll do anything to rid it of Amazon's-branded version of Android.
Click to expand...
Click to collapse
There are two different FireOS versions that report 5.1.2 and only one of them is rootable (542168620). Many user reported that the rooting process works best if the device is not yet registered to Amazon.
fmc000 said:
There are two different FireOS versions that report 5.1.2 and only one of them is rootable (542168620). Many user reported that the rooting process works best if the device is not yet registered to Amazon.
Click to expand...
Click to collapse
Yep. Also be weary of the downloaded update which will likely push your tablet to 5.3.x which is not rootable.
You can rollback FireOS 5.1.2.1 to version 5.1.2 which can be rooted. Everything you need can be found in the forum index.
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Davey126 said:
Yep. Also be weary of the downloaded update which will likely push your tablet to 5.3.x which is not rootable.
Click to expand...
Click to collapse
So how would I avoid that? Kingroot insists on internet access, and given that it often requires multiple tries, I am afraid it will give Amazon plenty of time for OTA update.
railshot said:
So how would I avoid that? Kingroot insists on internet access, and given that it often requires multiple tries, I am afraid it will give Amazon plenty of time for OTA update.
Click to expand...
Click to collapse
Partial FireOS downloads are discarded each time the device reboots. Kingroot reboots with sufficient frequency during the rooting process to prevent a full OTA update from being downloaded with a typical 'home' connection (say <50 Mbps). Another option is the desktop/tether version of Kingroot that does not require the device have a network connection. Downside is the desktop UI is in Chinese but is pretty easy to follow.
Thank you. I blocked the amazon update domains on my router (what I could find at least) and managed to root it. Good to know that it was probably not needed
railshot said:
Thank you. I blocked the amazon update domains on my router (what I could find at least) and managed to root it. Good to know that it was probably not needed
Click to expand...
Click to collapse
For the benefit of future readers: blocking domains usually does not work long term to prevent OTA updates as Amazon (or their agents) rotate sources on a regular basis. I suspect this a for load balancing and other housekeeping, not an effort to circumvent user 'blocks'.
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.
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.
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.