I want to root a new Fire Phone that came with Fire OS 4.6.1 (461013320) and upgrade to the latest Fire OS.
The phone came with an unlocking code, if that matters.
I've read through the rooting threads, and there seems to be a lot of old and conflicting info.
Is it best to root before upgrading to the latest Fire OS, or best to upgrade the Fire OS to the latest version first? I'm not planning on using CM at this time.
Is there a way to root Fire OS 4.6.1 or later without using King Root? It seems that most of the suggestions involve King Root, but then people express significant concerns about what King Root really installs. After using King Root, many people are then going through tedious processes to get rid of all the King Root stuff, and switch to SU.
I would prefer not to lose root during future Fire OS updates.
In summary, I have a new Fire Phone with Fire OS 4.6.1 that I want to root and be updated to the latest Fire OS. What is the fastest, cleanest, and safest way to accomplish this task?
Unfortunately, right now Kingroot is the only (known) method to root the Fire Phone. Then, as you said, it's recommendable to switch to SU. It's the only way, sorry.
Thanks Sergio. I thought I read a post that someone found another way to root. It was in one of the Kingroot threads, but I've been having trouble finding it. I'll keep looking.
Is it best to OTA update the Fire OS to the latest version before or after obtaining root? Do OTA's cause users to lose root?
Update before rooting, but first make sure that the last FireOS update is rootable (if FireOS 5 reaches the Fire Phone, this can't be emphasized enough).
rockpaperlizard said:
I thought I read a post that someone found another way to root. It was in one of the Kingroot threads, but I've been having trouble finding it. I'll keep looking.
Click to expand...
Click to collapse
Hi, is this the post you are looking for: http://forum.xda-developers.com/showpost.php?p=61854585&postcount=106
You can root using kingroot and then use Super-Sume to remove it.
Sorry to jump in but on a related subject I've been on rooted 461 for a few months can I still use super sume or does it have to be deployed immediately after root?
ratbags said:
Sorry to jump in but on a related subject I've been on rooted 461 for a few months can I still use super sume or does it have to be deployed immediately after root?
Click to expand...
Click to collapse
Well, if you left the "auto update over wifi" option activated, (can be found in the KingUser app, not Kingroot, just to be clear) then it may have updated itself by now.
Reason why I mention this: Super-Sume is only available in the paid version. gatesjunior removed the free version from the Play Store.
So you could give it a shot with the "old" free version, that you backed up earlier *wink wink* and hope that it still works with your current "King apps".
In general: no, it doesn't have to be used immediately after Kingroot install. And since the Kingxteam is cranky, it will be the old cat and mouse game and gatesjunior will need to adjust his tool from time to time...
I managed to root my Fire Phone (Fire OS 4.6.3, T-Mobile Netlock) coupla seconds ago with Kingroot, so it's everything OK.
cthulhu1987 said:
I managed to root my Fire Phone (Fire OS 4.6.3, T-Mobile Netlock) coupla seconds ago with Kingroot, so it's everything OK.
Click to expand...
Click to collapse
It's not that using Kingroot is bad per se, but that some of us (the ones that care about our data) prefer using root methods that come from reliable sources. We use SuperSU because it was developed by a XDA user we trust, and if a backdoor or vulnerability is detected, we can always PM him to get it patched. The same cannot be said about Kingroot, that uses only-god-knows-what to root the device, automatically installs a bloatware app and makes it very hard to uninstall without losing root. If you aren't concerned about who could be using your data, Kingroot is no bad for you.
jack9955 said:
Hi, is this the post you are looking for: http://forum.xda-developers.com/showpost.php?p=61854585&postcount=106
Click to expand...
Click to collapse
Thank you Jack! That's the post.
Has anyone else tried this? Seems like a better idea than Kingroot.
sergio687 said:
It's not that using Kingroot is bad per se, but that some of us (the ones that care about our data) prefer using root methods that come from reliable sources. We use SuperSU because it was developed by a XDA user we trust, and if a backdoor or vulnerability is detected, we can always PM him to get it patched. The same cannot be said about Kingroot, that uses only-god-knows-what to root the device, automatically installs a bloatware app and makes it very hard to uninstall without losing root. If you aren't concerned about who could be using your data, Kingroot is no bad for you.
Click to expand...
Click to collapse
'k, can I safely uninstall this app with the Chinese name, it keeps bugging me with some kinda ad-crap?
cthulhu1987 said:
'k, can I safely uninstall this app with the Chinese name, it keeps bugging me with some kinda ad-crap?
Click to expand...
Click to collapse
If you uninstall that bloat app, you'll lose root. That's one of the reasons why Kingroot is not reliable. There's not any reason at all for a root app to come with a "device management" app, and even if so, the developer wouldn't need to make it so hard to delete it without losing root. It's shady, and anyone (myself included) could think that it opens possibilities that the Kingroot combo does more than just rooting.
Getting Kingroot to root the device and then replace it with SuperSU is not mandatory, but recommendable. You decide what you do with your device
sergio687 said:
If you uninstall that bloat app, you'll lose root. That's one of the reasons why Kingroot is not reliable. There's not any reason at all for a root app to come with a "device management" app, and even if so, the developer wouldn't need to make it so hard to delete it without losing root. It's shady, and anyone (myself included) could think that it opens possibilities that the Kingroot combo does more than just rooting.
Getting Kingroot to root the device and then replace it with SuperSU is not mandatory, but recommendable. You decide what you do with your device
Click to expand...
Click to collapse
I see, so Super-sume would help me get rid of KingRoot and this annoying adware (it is not even adware in a language I speak), right?
cthulhu1987 said:
I see, so Super-sume would help me get rid of KingRoot and this annoying adware (it is not even adware in a language I speak), right?
Click to expand...
Click to collapse
Right.
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
Or you could use the method @jack9955 mentioned last page.
sergio687 said:
Right.
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
Or you could use the method @jack9955 mentioned last page.
Click to expand...
Click to collapse
No problem, I installed Super-Sume, the phone rebooted one time or two and now KingUser & adware is gone and SuperSU was installed. Awesome!! :good: :highfive: :fingers-crossed: :laugh:
I just ordered a Fire Phone off eBay so i'm still waiting to get my hands on it. I don't know what OS is on it, so I figured just to be on the safe side, it could have 4.6.4....as far as KingRoot goes.......do I install KingRoot, then go download Super-Sume, install that, then go remove KingRoot?
Related
I'm asking for every ones input and thoughts to help those who have not yet rooted and are still thinking about it. Should they root there note 8 before OTA 4.4 and not have to worry about the knox boot loader, and should they even be worried?
Sent from my GT-N5110 using xda app-developers app
There is no concrete/definite ETA on 4.4. It could be April, May, who knows it could be September. Why won't you root then?
Most likely 4.4 will come with knox , so an alternative root method would be required. Versus if rooting before you wouldn't have to worry about. But I believe knox would would need to be removed from the rom if 4.3 and above.
Sent from my GT-N5110 using xda app-developers app
Before
I could see how Knox might make a sticky situation when it comes to rooting, and rooting now would save you from potentially having to downgrade and then upgrade.
statum2013 said:
I could see how Knox might make a sticky situation when it comes to rooting, and rooting now would save you from potentially having to downgrade and then upgrade.
Click to expand...
Click to collapse
I've tried reading up on this and it seems that once you have upgrade there's no turning back being that your stuck with the Knox boot loader. Which just means you voided your warranty and can't hide it.
livis n fur said:
Most likely 4.4 will come with knox , so an alternative root method would be required. Versus if rooting before you wouldn't have to worry about. But I believe knox would would need to be removed from the rom if 4.3 and above.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
I rooted with a new universal rooter tool that does disable Knox before rooting. Easy peasy and safe to boot! Look up saferoot.zip
---------- Post added at 02:40 PM ---------- Previous post was at 02:32 PM ----------
livis n fur said:
I've tried reading up on this and it seems that once you have upgrade there's no turning back being that your stuck with the Knox boot loader. Which just means you voided your warranty and can't hide it.
Click to expand...
Click to collapse
I use root cloak and root cloak donate. Kies detects no issues with safe root installed, as it disables Knox.
I will wait on any 4.4 load, as there always will be bugs with developed apps in Xposed. Gosh, I am still waiting for 4.2 bug fixes on some Xposed apps. I rather have a fully working device than a half baked device you can get from any vendor. I get so irritated at official released updates that break things, let alone get a new device out of the box to find out it was not fully tested. I guess Microsoft has made peeps give in to poorly developed function. Just reboot,or patch and you will be fine. ( A poor excuse for releasing something too soon. Just look at Xbox and other game consoles being push out in a rush to gain sales. Bah!!!!
gooberdude said:
I rooted with a new universal rooter tool that does disable Knox before rooting. Easy peasy and safe to boot! Look up saferoot.zip
---------- Post added at 02:40 PM ---------- Previous post was at 02:32 PM ----------
I use root cloak and root cloak donate. Kies detects no issues with safe root installed, as it disables Knox.
I will wait on any 4.4 load, as there always will be bugs with developed apps in Xposed. Gosh, I am still waiting for 4.2 bug fixes on some Xposed apps. I rather have a fully working device than a half baked device you can get from any vendor. I get so irritated at official released updates that break things, let alone get a new device out of the box to find out it was not fully tested. I guess Microsoft has made peeps give in to poorly developed function. Just reboot,or patch and you will be fine. ( A poor excuse for releasing something too soon. Just look at Xbox and other game consoles being push out in a rush to gain sales. Bah!!!!
Click to expand...
Click to collapse
So is the boot loader just disabled completely removed? Thanks for the feed back much appreciated.
livis n fur said:
So is the boot loader just disabled completely removed? Thanks for the feed back much appreciated.
Click to expand...
Click to collapse
You would have to search the forum for Saferoot... and contact the developer. I am just a user and do not know what he does with his script.
I do know that is loads Busybox, Root, and I think ADB. Not sure about the last for terminology, but it does three things besides disabling Knox before installing root and tools. I think there is a video but may not cover all the details.
Hi peeps, looked at rooting my nice new G3 and went in for the kill with towel root [emoji16] only to find out didn't support my version. Decided to go with purpledrake (not got there yet) found a couple of apps not working because of root which root checker says I don't have. My question is do I need to root now regardless even if only to unroot? To get things back to normal?
stigslim said:
Hi peeps, looked at rooting my nice new G3 and went in for the kill with towel root [emoji16] only to find out didn't support my version. Decided to go with purpledrake (not got there yet) found a couple of apps not working because of root which root checker says I don't have. My question is do I need to root now regardless even if only to unroot? To get things back to normal?
Click to expand...
Click to collapse
After rooting, did you install SuperSU?
Also, there's StumpRoot as a 3rd option.
That's just it. Towel root told me my phone wasn't supported and root checker says I don't have root, yet the app in question says I do so super user seems a bit pointless.
stigslim said:
That's just it. Towel root told me my phone wasn't supported and root checker says I don't have root, yet the app in question says I do so super user seems a bit pointless.
Click to expand...
Click to collapse
SuperSU is needed after you root to give apps root access. Try to install it, if it works, you're rooted and you can go along with your rooted apps.
Otherwise, try StumpRoot (Towel and Purple's didn't support my version either), install SuperSU and enjoy your root apps!
Tried to install it with no luck. Seems something's gone wrong somewhere.
Says I need to manually 're root of I just upgraded to android 4.3. As it can't install su binaries.
Sent from my LG-D855
stigslim said:
Tried to install it with no luck. Seems something's gone wrong somewhere.
Says I need to manually 're root of I just upgraded to android 4.3. As it can't install su binaries.
Sent from my LG-D855
Click to expand...
Click to collapse
Time to give StumpRoot a shot then.
Yeah I think your right. The only issue left is the app I want to use fails when rooted and the root cloak module/app doesn't currently support it [emoji20]
Edit:
Well i tried stump root and got nowhere [emoji20] looking like purple is my only way forward. And if i want to use that particular app then root, unroot is the only way forward. [emoji45]
Howdy,
I love my first Fire phone (OTA to v4.6.3, unlocked version). I put Gapps on it, works great, love the form factor and everything.
Then I bought a second one, which came 3.5.1. I figured why not root it? I have rooted a few so I did not wait. I stayed away Kingroot knowing too well how Chinese apps leave backdoor to Beijing. (i am Chinese American, was gonna buy a Moto, but, maybe,,,)
Now I am at this stage, the phone is downgraded to 3.5 per XDA post. I have put the Airplane mode on all the time fearing OTA. I will try to sideload Towelroot to avoid turning Wifi (OTA you know).
My question is, once I root it, how do I prevent future OTAs? Which steps I have to take to disable automatic upgrade forced down by Amazon?
My second question is, once rooted, is there anyways to upgrade it to 4.6.x and keep root, or use a fully functional ROM? Again I would not use any apps from China to flash ROM.
Appreciate any tips, thanks,
OK, here is an update. The moment I turned on Wifi, the auto upgrade started (i remember it would be 4.6.1 as indicated by the process). I had to race to Towelroot the phone. Because the original phone has no file manager app (my oversight), I had to keep Wifi on and register with Amazon and get ES File Explorer from Amazon Appstore. With ES File Exp, I side loaded Super SU, and two root checker apps. Luncky I was able to confirm root before the phone finished downloading upgrade. (turn off Wifi the moment I got ES File Exp).
Now, I need to stop the auto upgrade. Here is a link I have not tried. :
http://forum.xda-developers.com/fire-phone/general/guide-disabling-auto-updates-fire-phone-t2930319
I read somewhere else on xda that I can delete the Device Service Platform in system/apps, but I could not find it.
I would appreciate some advice hereon how to go forward. Which is best way to stop the pending upgrade and eliminate future auto upgrade. Many thanks,
You understand that 4.6.x can be rooted, right?
No need to stay on 3.5.x to root.
Plenty of info aout this on this forum.
lol Yea dude like hack said, you can root up to the latest version. http://forum.xda-developers.com/fire-phone/help/installing-root-safestrap-cm11-t3157339/post61862217#post61862217 here's a thread with a guide go wild =)
If you want a later version, you have to root it with KingRoot. I have heard Wondershare works too. But no experience with that or not sure why you would/wouldn't trust it more than Kingroot. And why just not use Supersume to clean Kingroot up afterwards? Those guys are very active on xda and are very trustworthy.
Hi all, I'm a root noob, I've never rooted an Android device before but I'm strongly tempted to root my Tab S 8.4. This method looks rather complicated, though the fact that it's confirmed working for Lollipop and safe with Knox is nice. On the other hand, CF-Auto-Root looks rather easy but the official website says nothing about Lollipop on the Tab S 8.4, and if I'm reading correctly, requires an unlocked bootloader? What's the easiest and safest way to root?
DeltaEternal said:
Hi all, I'm a root noob, I've never rooted an Android device before but I'm strongly tempted to root my Tab S 8.4. This method looks rather complicated, though the fact that it's confirmed working for Lollipop and safe with Knox is nice. On the other hand, CF-Auto-Root looks rather easy but the official website says nothing about Lollipop on the Tab S 8.4, and if I'm reading correctly, requires an unlocked bootloader? What's the easiest and safest way to root?
Click to expand...
Click to collapse
The easiest way is to use KingRoot. Worked for me on my SMT-700 without any problems..oh yeah, you'll see a scary message about "device failure" or "device not compatible" or something like that. [emoji12]
Then check out "SuperSume" to change the superuser app...if you wanna'.
Don't forget about boot image and recovery...TWRP is my favorite.
Happy rooting!
......TiTiB (tweak it 'til it breaks)......
Galaxy Tab S | SMT-T700 | klimtwifi
TiTiB said:
The easiest way is to use KingRoot. Worked for me on my SMT-700 without any problems..oh yeah, you'll see a scary message about "device failure" or "device not compatible" or something like that. [emoji12]
Then check out "SuperSume" to change the superuser app...if you wanna'.
Don't forget about boot image and recovery...TWRP is my favorite.
Click to expand...
Click to collapse
I don't mean to bother you or anything, but to be totally honest that method has me rather confused XD It sounds like I need to go to samsung-updates.com and download and flash the Kitkat firmware for my region using Odin, which will unfortunately wipe my device. Then I use Kingroot, reboot, and uninstall Kingroot. Next, I use the terminal to gain root privileges, use System App Remover to uninstall Kinguser, again ensure I have root privileges, and use said temporary root privileges reflash the stock firmware. Then I install a bootloader because flashing stock firmware erased the one I already had (?) using download mode and Odin. That sounds awful messy, though if it's confirmed to be rather safe and solid, I'll still gladly consider it. Am I correct in this interpretation of the guide? Additionally, would the second flash using Flashfire also require me to wipe my device? (I'm guessing no.)
Sounds like you want to just root, and *not* install a new OS. If this is the case then simply use KingRoot. It doesn't do anything except provide root priviledges/access and install Kinguser, as you mentioned. [you really did your part in researching, unlike some folks who just want to be spoon fed, I and others really appreciate that].
I provide a link to the version of KingRoot that used. There is also, as previously mentioned, SuperSume. I noticed there is a paid version on Play, but I know there is the "original" free version that, I think, was written by an xda member.
Hope this helps
https://drive.google.com/folder/d/0B8tvUtXZ--2aRWtLWVZwTlRIUjA/edit
TiTiB said:
Sounds like you want to just root, and *not* install a new OS. If this is the case then simply use KingRoot. It doesn't do anything except provide root priviledges/access and install Kinguser, as you mentioned. [you really did your part in researching, unlike some folks who just want to be spoon fed, I and others really appreciate that].
I provide a link to the version of KingRoot that used. There is also, as previously mentioned, SuperSume. I noticed there is a paid version on Play, but I know there is the "original" free version that, I think, was written by an xda member.
Click to expand...
Click to collapse
You are correct, I just want stock Lollipop with root on top. In that case, should I follow the Kingroot guide I linked to above and omit certain steps, or should I just install Kingroot and do something else entirely? Would this method obtain a root access that is persistent across reboots? (It sounds like in the guide it only gives you root until the device next shuts down.) Additionally, how would I go about receiving an OTA update? I anticipate that installing an OTA while rooted could cause problems.
Oh, and thanks for linking me to the Drive folder and such!
DeltaEternal said:
You are correct, I just want stock Lollipop with root on top. In that case, should I follow the Kingroot guide I linked to above and omit certain steps, or should I just install Kingroot and do something else entirely? Would this method obtain a root access that is persistent across reboots? (It sounds like in the guide it only gives you root until the device next shuts down.) Additionally, how would I go about receiving an OTA update? I anticipate that installing an OTA while rooted could cause problems.
Oh, and thanks for linking me to the Drive folder and such!
Click to expand...
Click to collapse
What you are asking is beyond my knowledge/experience level. I've only used custom ROMs after rooting and never had any thought of keeping stock anything...getting rid of every piece of Samsung software was the main reason for me to root.
As for KingRoot, though, I used it once and have done many flashes of new ROMs, TWRP versions, etc., and have not had to use it again. Hope this info helps.
Someone else will need to chime in on this..good luck.
......TiTiB (tweak it 'til it breaks)......
Galaxy Tab S | SMT-T700 | klimtwifi
The whole point of the kingroot method is to preserve the knox counter for warranty purposes.
If you don't care about knox then simply flash CF-autoroot and be done.
The kingroot method is long-winded because it converts you to supersu which is required to use Flashfire, which in turn is used to flash updates.
Hi, im planing to root my AFTV stick with Kingroot.
What services, apps, bloatware will you recommend to disable in order to free some ram and improve user experience?
Thanks!
Antieco said:
Hi, im planing to root my AFTV stick with Kingroot.
What services, apps, bloatware will you recommend to disable in order to free some ram and improve user experience?
Thanks!
Click to expand...
Click to collapse
Some have blocked the kingroot app from calling home? Look in the forums if you want to do that? I also recommended blocking ota updates from amazon once rooted! & finally don't try to use Super Sume or Super Sume Pro because quite a few have bricked after a reboot after successfully swapping kingroots su for the super su (you have been warned).
deanr1977 said:
Some have blocked the kingroot app from calling home? Look in the forums if you want to do that? I also recommended blocking ota updates from amazon once rooted! & finally don't try to use Super Sume or Super Sume Pro because quite a few have bricked after a reboot after successfully swapping kingroots su for the super su (you have been warned).
Click to expand...
Click to collapse
Many thanks.
Is it possible to load xposed as the bootloader is locked and no custom recovery is known?
You can use xposed without a recovery.... BUT.... It is not recommended! rbox a Developer in the AFTV thread Is working on a recovery for our device & also a prerooted rom so for now just root, block ota amazon updates & then wait until he's ready to release it, then we can start messing with xposed!
Sent from my SM-G900F using Tapatalk