Has anyone ever unlocked the bootloader for the Kindle Fire HDX or the Kindle Fire HD's?
No. It has been rooted, but no BL unlock.
Sent from my Nexus 7 using XDA Premium HD app
GSLEON3 said:
No. It has been rooted, but no BL unlock.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
The HDX 7" has been rooted? Where can I dl this--is it difficult to do?
Also, once I'm rooted, how do I keep Amazon from pushing through updates?
Major General said:
The HDX 7" has been rooted? Where can I dl this--is it difficult to do?
Also, once I'm rooted, how do I keep Amazon from pushing through updates?
Click to expand...
Click to collapse
You can use an app like Root Explorer or Solid to move or rename /system/etc/security/otacerts.zip. It may still download an update, but then you can delete it in Cache & it should stop future updates.
I would think at some point root will get patched though, as it really is a GAPING security hole that if used maliciously could have a devastating affect. Initially I thought 9695860 was only open to 64kb of data, however, after talking with jcase, he told me that saurik had figured out how to further the exploit, which from what I have read, you could now drive a truck through. It all depends on how much they do in-house & how much of Google's base code they rely on. If they update to a 4.3 base for Fire, say bye bye. Otherwise, it could stick around for a while at least. Hopefully by then we have more tools to combat them with, like a recovery. Hashcode is very busy right now, but now that we have root, he mentioned stopping by to see what we could get going, similar to what he's done for all the previous Amazon devices (which is quite a bit). For now, rename or move the certs to your sdcard & you should be okay.
Thanks for taking the time to answer--this sounds like it's complicated to do at this point--I'll wait a bit and see what tools become available to do it a bit easier.
GSLEON3 said:
You can use an app like Root Explorer or Solid to move or rename /system/etc/security/otacerts.zip. It may still download an update, but then you can delete it in Cache & it should stop future updates.
I would think at some point root will get patched though, as it really is a GAPING security hole that if used maliciously could have a devastating affect. Initially I thought 9695860 was only open to 64kb of data, however, after talking with jcase, he told me that saurik had figured out how to further the exploit, which from what I have read, you could now drive a truck through. It all depends on how much they do in-house & how much of Google's base code they rely on. If they update to a 4.3 base for Fire, say bye bye. Otherwise, it could stick around for a while at least. Hopefully by then we have more tools to combat them with, like a recovery. Hashcode is very busy right now, but now that we have root, he mentioned stopping by to see what we could get going, similar to what he's done for all the previous Amazon devices (which is quite a bit). For now, rename or move the certs to your sdcard & you should be okay.
Click to expand...
Click to collapse
Major General said:
Thanks for taking the time to answer--this sounds like it's complicated to do at this point--I'll wait a bit and see what tools become available to do it a bit easier.
Click to expand...
Click to collapse
Not really. Just root, use a root level explorer, like Root Explorer or ES File Explorer & move or rename one file. I don't think it is going to happen any time soon anyway. They just updated to 14.3.1 & they didn't patch it then. It will only really lock out this exploit with a new kernel that is patched.
I meant the process of rooting, from the other thread, seemed complicated. But maybe I didn't give it a close enough look...
Can you direct me to where I'd download the relevant files from/instructions on what to do, and how to keep Amazon from pushing through an update once I've done it? I have ES on my Kindle already.
GSLEON3 said:
Not really. Just root, use a root level explorer, like Root Explorer or ES File Explorer & move or rename one file. I don't think it is going to happen any time soon anyway. They just updated to 14.3.1 & they didn't patch it then. It will only really lock out this exploit with a new kernel that is patched.
Click to expand...
Click to collapse
which kernel is the 7" HDX device running on? We are working on a root exploit for 7" HD 3rd generation, maybe the root method you use, could work for us too.
Related
http://www.engadget.com/2011/11/16/kindle-fire-gets-rooted-with-one-click-paves-the-way-for-amaz/
Noooooooooo............
So..32sec ago..
Rooted or not, its still super limited and is waay weaker than NT. Hell, even unrooted I got all my sideloaded ebooks on it already, as well as 1080p videos on my 32gb sd. How much 1080p footage can you place on even rooted KF? Very, very little.
Yeah..until the KF gets a mic...2x memory and expandable SD slot...I'm keeping my NC and looking forward to the rooting of the NT.
I'm glad someone got it worked out. Hopefully the NT just more time in lieu of high expectations from the company. I mean, everyone wanted to know if it could be done to the KF.
What surprises me is that they've release the source code already. Maybe they tried so hard to compete with the ibrick that they suddenly realized they have more competition.
Good for us either way.
...and Amazon Puts Kindle Fire Source Code Up for Download
http://gizmodo.com/5860142/amazon-puts-kindle-fire-source-code-up-for-download
Oops, didn't see somebody mentioned it already...
I leaning towards KF after seeing the progress..
kevin_405 said:
I leaning towards KF after seeing the progress..
Click to expand...
Click to collapse
Perhaps you should give it some time...the NT has not Actually been released yet.
The root is based on zergrush and I think it should also work on NT. Just need someone with a NT to test.
http://forum.xda-developers.com/showthread.php?t=1296916
arda99 said:
The root is based on zergrush and I think it should also work on NT. Just need someone with a NT to test.
http://forum.xda-developers.com/showthread.php?t=1296916
Click to expand...
Click to collapse
Currently adb on the NT isn't where it was with NC.
Once the adb/'shell' can be found...its possible to test this or ask for code rewrite to support the new 'adb/shell'
discothan said:
Currently adb on the NT isn't where it was with NC.
Once the adb/'shell' can be found...its possible to test this or ask for code rewrite to support the new 'adb/shell'
Click to expand...
Click to collapse
Don't think adb is a must, how about sideload terminal app and run zergrush within that?
zergrush is good till 2.3.6. Whats the android version on NT? build.prop?
arda99 said:
Don't think adb is a must, how about sideload terminal app and run zergrush within that?
zergrush is good till 2.3.6. Whats the android version on NT? build.prop?
Click to expand...
Click to collapse
Doesn't terminal require su privileges?
Terminal runs as User - and is where you can enter SU if supported.
Hello everyone. First off, I'd like to say I've been reading/lurking here for quite sometime and have found it EXTREMELY helpful, and would like to thank the XDA community for all of the resources and help.
I found out today that Squaretrade actually covers rooted/jailbroken devices, and I have a ST warranty on my Prime.
I have not had quite as much trouble with my Prime as others, but still struggle with reboots and the ever-present 'not responding' alerts.
I was wondering what the advantages are to rooting my Prime. I am not extremely tech savvy, and am not a programmer/developer, so I would like to know what benefits an average user would see/get out of rooting.
Thanks for all of your help. Look forward to your responses as well as potentially rooting my Prime! :good:
If you want your Prime to run as it should then root and apply a couple of quick mods. It makes a huge difference and really does take just a few minutes to get it truly flying.
1. Very simple one stop root tool: HERE.
2. Then get stock browser running fast and smooth: HERE.
3. Finally eliminate any remaining lags by tweaking your system to load SIO scheduler and clock to 1600MHz using another great one-stop tool HERE.
Job done.
In similar position as OP - am very tempted by root thanks to the potential of Browser2RAM and Androwook. The only two issues/questions I have:
What is the risk of bricking my tablet during the rooting process?
Is it worth waiting for the next update/ community support for JB before installing something like Androwook?
Thanks guys, I know this is probably very pedantic but I've only been lurking here for the past month or so.
GS_Dan said:
In similar position as OP - am very tempted by root thanks to the potential of Browser2RAM and Androwook. The only two issues/questions I have:
What is the risk of bricking my tablet during the rooting process?
Is it worth waiting for the next update/ community support for JB before installing something like Androwook?
Thanks guys, I know this is probably very pedantic but I've only been lurking here for the past month or so.
Click to expand...
Click to collapse
You also need to unlock your bootloader to install androwook or another custom rom. Unlocking your bootloader will definitely void your warranty and will stop original asus updates on your device.
So let's talk about root: the risks in rooting process are virtually zero, i never heard of such a problem on every single device. I rooted my LG optimus 2X and my prime (two times) very easily and without problems.
I don't use browser2ram but i use the ATP tweak app and ezoverclock app (search for them in the development section) and they make my prime fly without problems.
If you only root your device you won't lose asus updates.
Sent from my LG-P990 using xda app-developers app
jason1993 said:
You also need to unlock your bootloader to install androwook or another custom rom. Unlocking your bootloader will definitely void your warranty and will stop original asus updates on your device.
So let's talk about root: the risks in rooting process are virtually zero, i never heard of such a problem on every single device. I rooted my LG optimus 2X and my prime (two times) very easily and without problems.
I don't use browser2ram but i use the ATP tweak app and ezoverclock app (search for them in the development section) and they make my prime fly without problems.
If you only root your device you won't lose asus updates.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Thanks duder, I'll try rooting and stick with that unless Asus mess things up badly.
benefits of rooting faster system, more stable then stock, longer battery life, more tools to optimize with and block ads within apps and thats just a few benefits
I have rooted every android device I have owned, (quite a few) but the Transformer is the first one I have just not found a really good reason to root. There just aren't and major upgraded kernal/Rom changes I have seen that retain full dock functionality so mine stays unrooted for the time being.
Sent from my PG86100 using xda app-developers app
Have rooted, was as easy as you guys said
Immediately put on those performance improvement apps and changed the default physical keyboard language so I don't have to switch to thumb keyboard manually when I undock -already worth rooting!
hi guys. tomorrow my new prime (tired of infinity wait) will arrive. so i just follow all the steps to root? im used to root original droid.. incredible.. lol tomorrow questions
Sent from my ADR6300 using xda premium
GS_Dan said:
Have rooted, was as easy as you guys said
Immediately put on those performance improvement apps and changed the default physical keyboard language so I don't have to switch to thumb keyboard manually when I undock -already worth unlocking!
Click to expand...
Click to collapse
Hope you meant "worth rooting"!!
I can't recommend "unlocking" the bootloader to those who aren't tech savvy =)
Btw, do be careful with any file management app & etc...
Do not delete or move files that you simply have no knowledge of =)
shinzz said:
Hope you meant "worth rooting"!!
I can't recommend "unlocking" the bootloader to those who aren't tech savvy =)
Btw, do be careful with any file management app & etc...
Do not delete or move files that you simply have no knowledge of =)
Click to expand...
Click to collapse
Haha yes, I meant rooting
shinzz said:
Hope you meant "worth rooting"!!
I can't recommend "unlocking" the bootloader to those who aren't tech savvy =)
Btw, do be careful with any file management app & etc...
Do not delete or move files that you simply have no knowledge of =)
Click to expand...
Click to collapse
+1
GS_Dan said:
In similar position as OP - am very tempted by root thanks to the potential of Browser2RAM and Androwook. The only two issues/questions I have:
What is the risk of bricking my tablet during the rooting process?
Is it worth waiting for the next update/ community support for JB before installing something like Androwook?
Thanks guys, I know this is probably very pedantic but I've only been lurking here for the past month or so.
Click to expand...
Click to collapse
Hi,
the chance to brick your device is relatively low (if you use the proposed "one click root tool" mentioned in this thread.
If you unlock the bootloader (with the ASUS APK) the chance is higher.
But I don't see an advantage to do that since the unroot tool also can handle the version 9.4.2.21 now!
AND: you can update via Asus update (system settings) which is impossible if you install another ROM!
Before you do that pls install the VOODOO ROOTKEEPER (which saves your root)
Once I get my tablet back from ASUS I am probably going to give rooting a shot for the first time. I do a lot of overclocking and stuff within windows but still pretty new to Android. I am just wondering which of these rooty things will be best, I am looking at Androwook which appears to offer better battery life and things, but how much faster, or better is the battery life. Will I be able to beat my 8-9 hours with wi-di and browsing?
no ads.
That makes it worth rooting
just got my prime... update 2 times... its runs amazing guys ! stock
Sent from my Transformer Prime TF201 using XDA Premium HD app
Hi all - just signed up. I'm receiving my 10 Monday. I have an Infinity and wanted to give the Nexus 10 shot as it seems like a great tablet. I'm not likely to root either one. Is there anything you all suggest to get the most out of the Nexus 10? I'm fairly new to the tablet world although have owned an android phone for several years.
Thanks!
Welcome and congrats! Here is a link someone started that shares your question.
http://forum.xda-developers.com/showthread.php?t=2023608
Sent from my Nexus 10 using Tapatalk HD
^ Great thread for starters but make sure and DO YOUR READING before you unlock and root your device -- or you will end up with a $400 makeshift frisbee disk. Unlocking your boot-loader/rooting is what makes android so much fun, I would recommend it
Derp: sounds you've rooted before, but I suppose the above statement still stands lol
TheEmpyre said:
^ Great thread for starters but make sure and DO YOUR READING before you unlock and root your device -- or you will end up with a $400 makeshift frisbee disk. Unlocking your boot-loader/rooting is what makes android so much fun, I would recommend it
Derp: sounds you've rooted before, but I suppose the above statement still stands lol
Click to expand...
Click to collapse
I did read that thread but as I said - I'm not likely to root...at least not right away.
stormricker said:
I did read that thread but as I said - I'm not likely to root...at least not right away.
Click to expand...
Click to collapse
Sounds like quite a few people are unlocking / rooting and leaving the stock ROM which is likely what I will do. I like having the freedom that Root provides to install some apps etc.
Nexus 10 will be my first tablet also, so I'll be having quite a bit of fun for the first few weeks figuring out how exactly I will be using it
TheEmpyre said:
Sounds like quite a few people are unlocking / rooting and leaving the stock ROM which is likely what I will do. I like having the freedom that Root provides to install some apps etc.
Nexus 10 will be my first tablet also, so I'll be having quite a bit of fun for the first few weeks figuring out how exactly I will be using it
Click to expand...
Click to collapse
Still a little nervous about the rooting process....and its risks. What exactly are the benefits?
stormricker said:
Still a little nervous about the rooting process....and its risks. What exactly are the benefits?
Click to expand...
Click to collapse
From what I've gathered, and from experience, I think the benefits of Root give the user a great deal more control of what goes on with his/her device -- that is, in part, what apps are accessing resources. For example, with my HTC One XL, I was able to install an app (which requires root access) that allows me to freeze apps while they are not in use -- launch them to unfreeze and use them when I need but when I'm not using, they aren't going to automatically run processes that drain my battery. I also installed a custom Kernel, and there is a root-required app that allows me to adjust my CPU frequencies and voltages to maximize battery life and performance.
I am relatively new to rooting devices, as I started in late October, but I can tell you that I have had a ton of fun doing it.
In any event, I really dont think rooting is that valuable to mainstream users if you ask me -- If you aren't looking into flashing custom ROMs or using special utilities/apps on your device then I wouldn't bother rooting/unlocking bootloader.
Since you asked risks I'll address that too: The risks are bricking (completely unusable) your device if you flash an incompatible ROM, but this is easily avoided by sticking only to flashing ROMs for the Nexus 10. You can also damage the components of your device if you overclock too much etc....Other risks are that ROMs are buggy sometimes despite the very hard work of the devs here (They are truly amazing here) but the bugs may take away from your experience potentially. There may be plenty of other risks but these are the ones I can think of so far.
I was completely unaware of root/unlock up until about 2 months ago and was completely new to the process. I was able to read great guides put together by the XDA community here that walked me through the process and I was successful in unlocking my One X and I now finally feel like I am getting the moneys worth out of my device that I payed good $$$ for.
stormricker said:
Still a little nervous about the rooting process....and its risks. What exactly are the benefits?
Click to expand...
Click to collapse
Rooting is quick and painless if you use the Nexus 10 Toolkit available in the development section! My Galaxy Nexus also has a toolkit from the same dev, makes things SO much easier/quicker.
The risks of rooting are almost non-existent. Really, if the procedure doesn't work for you, nothing changes & you just won't have root permissions. I've personally never had anything bad happen, but I'm sure there is someone out there who has tried some sketchy method to root...the methods here are far from that, just read up and follow the instructions.
Benefits are basically the freedom to remove system apps and make backups of any of your apps. There are also a ton of root apps that allow you to customize your device the way you like it. With root, you get full control and the freedom to tinker.
Nexus devices are absolutley meant for consumers who don't root or unlock, but what is great about them is if you want to do either of the latter..it is much easier to do.
Also, I suggest you try and personally compare your N10 and Infinity before you read any of the general comparison threads. lol
Oh and welcome to the vanilla side of Android! :good:
- Mac
xIC-MACIx said:
Rooting is quick and painless if you use the Nexus 10 Toolkit available in the development section! My Galaxy Nexus also has a toolkit from the same dev, makes things SO much easier/quicker.
The risks of rooting are almost non-existent. Really, if the procedure doesn't work for you, nothing changes & you just won't have root permissions. I've personally never had anything bad happen, but I'm sure there is someone out there who has tried some sketchy method to root...the methods here are far from that, just read up and follow the instructions.
Click to expand...
Click to collapse
Toolkits are a nice method for rooting for beginners, but (imo) it's better to learn how to flash (and do generally other stuff) without the need of a toolkit.
When I rooted my Nexus 10, I just unlocked the bootloader (manually with fastboot), restocked, installed custom recovery (TWRP; fastboot) and then flashed a SuperSU CWM-flashable package from recovery. I did a lot of messing around with flashing and stuff on my SGT7 and Nexus 7, so this wasn't really anything new or difficult at all. I started out with a toolkit on my Nexus 7, and found it very annoying after a while when trying to flash a custom recovery (generally took a while for the device to end up having to reboot and unlock, and if I already did unlock then I think the toolkit wouldn't continue on unless I selected another option, and then if drivers aren't installed properly (I switched between a few devices) then that can also cause the toolkit to mess up, drivers and adb would be outdated from the toolkit in-comparison to what Google offered, etc.).
Simply put, Toolkits might be nice in the beginning, but I wouldn't recommend relying on them forever If your only mission is to just root the device though, a toolkit can do that pretty painlessly.
espionage724 said:
Toolkits are a nice method for rooting for beginners, but (imo) it's better to learn how to flash (and do generally other stuff) without the need of a toolkit.
When I rooted my Nexus 10, I just unlocked the bootloader (manually with fastboot), restocked, installed custom recovery (TWRP; fastboot) and then flashed a SuperSU CWM-flashable package from recovery. I did a lot of messing around with flashing and stuff on my SGT7 and Nexus 7, so this wasn't really anything new or difficult at all. I started out with a toolkit on my Nexus 7, and found it very annoying after a while when trying to flash a custom recovery (generally took a while for the device to end up having to reboot and unlock, and if I already did unlock then I think the toolkit wouldn't continue on unless I selected another option, and then if drivers aren't installed properly (I switched between a few devices) then that can also cause the toolkit to mess up, drivers and adb would be outdated from the toolkit in-comparison to what Google offered, etc.).
Simply put, Toolkits might be nice in the beginning, but I wouldn't recommend relying on them forever If your only mission is to just root the device though, a toolkit can do that pretty painlessly.
Click to expand...
Click to collapse
Absolutely agree with you on that one. My first Android device was a Infuse 4G. Every root and recovery procedure was absolutely manual. Not to mention most of the methods were hackjobs from the OG Galaxy S and required some extra coersing w/ Root Explorer and a terminal lol. Once I got my GNex, I could do anything I needed to do manually; I was actually rather shocked at how simple things were w/ a Nexus device.
Really though, I don't at all mind these toolkits, it might be important to learn what goes on behind the scripts, but lots of ppl here would have never attempted to tinker w/ android w/o some sort of script/batch automation. That said, i'm sure they cause quite a bit more traffic in the Q&A section when things to go wrong. lol
Thanks for all of the replies.
It should arrive today and I'll compare it with my Infinity first and then go from there.
Looking forward to know the N10
When I first received mine, I didnt think that I would recieve it till closer to the end of day, as stated with UPS. But it arrived at 10am! Hoping it happens the second time around for my replacement. Would love to have the whole day playing with it
Sent from my SPH-L710 using xda app-developers app
I'm currently running an 8.9" HDX with a working AOSP - thanks to all the help I got on this forum and specifically followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582773
but the main applications that I now need to use for work are iOS only (don't ask... NOT happy) so I'm back to carrying an iPad around everywhere and as such I'm going to sell my HDX. Before I do that I need to return it back to stock... I found a number of threads referencing how to do this but wanted to be extra careful. At present I'm just running Safestrap with a second ROM slot that I boot with all the non-standard stuff, I got there via SuperSU.
What's the right sequence of de-activates / un-installs / magic incantations to get this thing back to "boring, stock" just like it would come from Amazon? Is it as simple as re-enabling over-the-air updates and letting it "fix" itself? Or do I need to specifically back out some of the safestrap/superSU stuff first?
Help? (and THANKS)
ljwobker said:
I'm currently running an 8.9" HDX with a working AOSP - thanks to all the help I got on this forum and specifically followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582773
but the main applications that I now need to use for work are iOS only (don't ask... NOT happy) so I'm back to carrying an iPad around everywhere and as such I'm going to sell my HDX. Before I do that I need to return it back to stock... I found a number of threads referencing how to do this but wanted to be extra careful. At present I'm just running Safestrap with a second ROM slot that I boot with all the non-standard stuff, I got there via SuperSU.
What's the right sequence of de-activates / un-installs / magic incantations to get this thing back to "boring, stock" just like it would come from Amazon? Is it as simple as re-enabling over-the-air updates and letting it "fix" itself? Or do I need to specifically back out some of the safestrap/superSU stuff first?
Help? (and THANKS)
Click to expand...
Click to collapse
Depends on how you used SafeStrap. If you ONLY installed in the stock rom, then an update likely would do it. If you installed safestrap a second time from the working rom-slot as well, then updates won't work, because the BL & Kernel CANNOT be flashed.
The best thing is to remove all wifi connections with "forget network", then go into safe strap & activate stock rom. Then go back to the boot options & delete the rom-slot you created. Boot back into stock partition, uninstall Safestrap & then reconnect to wifi & check for updates.
I would HIGHLY recommend you follow my directions about forgetting nearby, if not all, wifi networks. If you turn wifi off in a slot, but not in stock, or vice versa, it can cause boot issues , as well as wifi issues.
I would not return it to stock. That device could go for a premium right now to other users simply because you can get AOSP and so many cannot yet.
EniGmA1987 said:
I would not return it to stock. That device could go for a premium right now to other users simply because you can get AOSP and so many cannot yet.
Click to expand...
Click to collapse
Why would it go for a premium? It is absolutely 100% rootable. It has not been patched against the VolumeManager/vold ASEC exploit. In fact, I am nearly certain the bootloader can bed unlocked from my investigation. Unfortunately that part is beyond my abilities & exceeds the time I would need to get caught up on the msm89xx+ SoC, but I would just about bet the farm that it can be done.
GSLEON3 said:
Why would it go for a premium? It is absolutely 100% rootable. It has not been patched against the VolumeManager/vold ASEC exploit. In fact, I am nearly certain the bootloader can bed unlocked from my investigation. Unfortunately that part is beyond my abilities & exceeds the time I would need to get caught up on the msm89xx+ SoC, but I would just about bet the farm that it can be done.
Click to expand...
Click to collapse
Because when I posted that we had no root, and it was still a "hopefully sometime soon" with 9/10 of the HDX's on a version that couldnt be rooted.
It is nice that we have one Chinese method now and that you might get something soon, though I think you are suddenly pretty full of yourself on these forums with the little bit of knowledge you gained recently. Much better people at this have not been able to get the bootloader cracked. But best of luck to you.
EniGmA1987 said:
Because when I posted that we had no root, and it was still a "hopefully sometime soon" with 9/10 of the HDX's on a version that couldnt be rooted.
It is nice that we have one Chinese method now and that you might get something soon, though I think you are suddenly pretty full of yourself on these forums with the little bit of knowledge you gained recently. Much better people at this have not been able to get the bootloader cracked. But best of luck to you.
Click to expand...
Click to collapse
Actually, the little time I've been around is well over a decade. This ain't my first username. Secondly, there is already an ASEC based root that WAS created by someone better with this stuff than me, so it's not full of myself, it is FACT. I am rooted, have been each & every time, without blocking anything & without having to sacrifice connectivity, another FACT. Coincidentally, the reason it was never published, well I'd venture a guess that it's because of stupid posts & self-entitled people ignorantly writing or PM'ing to insist that things be done for them on their terms. Another fact, it was that kind of crap that made me leave this forum a few months ago. So, I don't know what "better people" you are talking about that have failed at it, but I do know the better people that have done it.
Another fact, anyone at all can read & discover just how small the patch for the ASEC vulnerability was. It doesn't take a genius to then decompile the vold & search for the that one event which was used to patch it, which subsequently tells all you need to know.
GSLEON3 said:
Actually, the little time I've been around is well over a decade. This ain't my first username. Secondly, there is already an ASEC based root that WAS created by someone better with this stuff than me, so it's not full of myself, it is FACT. I am rooted, have been each & every time, without blocking anything & without having to sacrifice connectivity, another FACT. Coincidentally, the reason it was never published, well I'd venture a guess that it's because of stupid posts & self-entitled people ignorantly writing or PM'ing to insist that things be done for them on their terms. Another fact, it was that kind of crap that made me leave this forum a few months ago. So, I don't know what "better people" you are talking about that have failed at it, but I do know the better people that have done it.
Another fact, anyone at all can read & discover just how small the patch for the ASEC vulnerability was. It doesn't take a genius to then decompile the vold & search for the that one event which was used to patch it, which subsequently tells all you need to know.
Click to expand...
Click to collapse
lol. I am glad you know your FACTS. No need to act so butthurt.
Hi all. I am hoping for some very basic advice. I got a Kindle HDX 7 a few days ago. I have not connected it to wifi yet to avoid automatic updating of the firmware. When I go to settings>device>system update it tells me that my current firmware version is 13.3.0.5 installed on Jul, 30, 2013. From all I have read that is a good thing if I want to root my device.
The big question I have is if I actually should?
In a perfect scenario I could just replace the fire OS with a normal version of Android and not have any hassles. But I have heard that could play hell with battery life and I haven't actually found a good guide on how to do that safely with a KF HDX, so back to just rooting.
-Is there a comprehensive tutorial on how to root my device with it's current settings? I have looked but it is difficult to judge what is old/outdated information and what still works.
-How safe is this aka. how likely am I to brick my device just by rooting it (I'm a tech savvy user, but I wouldn't dare delve deeper than that) and how buggy are rooted devices if at all?
-How would I keep my device from upgrading automatically after rooting?
-Isn't the point of upgrades also to plug security holes that would compromise personal data? How would that work with never upgrading?
I would appreciate if the experienced rooters amongst you could advise me on this. Thank you!
Welcome. It is nice to see these questions asked before you have broken your device, as opposed to after. While I am by no means an expert, here are a few answers to get the ball rolling.
snorklm said:
In a perfect scenario I could just replace the fire OS with a normal version of Android and not have any hassles. But I have heard that could play hell with battery life and I haven't actually found a good guide on how to do that safely with a KF HDX, so back to just rooting.
Click to expand...
Click to collapse
This is entirely doable, not all builds are buggy.
snorklm said:
Is there a comprehensive tutorial on how to root my device with it's current settings? I have looked but it is difficult to judge what is old/outdated information and what still works.
Click to expand...
Click to collapse
Not completely, but since root is what you are after currently, go to the dev section and check out the roundup on the rooting tool. Read through the posts.
However, it is simple for you to root. You can go to towelroot and do it that way. Regardless, I suggest reading the dev threads to see some of the other options. Also, there is some good info in the rollback, now what? Threads in this section.
snorklm said:
How safe is this aka. how likely am I to brick my device just by rooting it (I'm a tech savvy user, but I wouldn't dare delve deeper than that) and how buggy are rooted devices if at all?
Click to expand...
Click to collapse
All it does is give you the option of allowing root permissions to an app. Root in it of itself is perfectly harmless. It won't change the function of the device at all if you do not utilize this new power. However, if an app (or you), change the wrong file, it could be devastating.
snorklm said:
How would I keep my device from upgrading automatically after rooting?
Click to expand...
Click to collapse
There are some block updates threads. Probably the easiest is to use the kindle fire xposed plugin (I think that still works). Be careful with xposed. It does allow you to make changes which can make your device unstable.
snorklm said:
Isn't the point of upgrades also to plug security holes that would compromise personal data? How would that work with never upgrading?
Click to expand...
Click to collapse
Yes, and achieving root access is looked at as a security hole by Amazon. You also will be missing out on new "Features." This could include KitKat. Although, you can flash the new software with TWRP which if done correctly will be stable, but that will require a lot more reading. It is really only the custom builds which are unstable. They are buggy because they are not quite finished. Head over to the dev section to find out more. In the end, it all comes down to what you plan to do with it, and how much you plan to learn along the way.
Good luck,
Leko
Sent from my KFTHWI using Tapatalk
Hi Snorklm - welcome to the forums. The title of your post made my day
If you haven't already read through the response from Leko. Hits all the important points and mirrors what I was going to write (beat me to the punch).
Some additional thoughts:
- Be sure to block OTAs before connecting to WiFi. Your options will become much more restricted if Amazon pushes an update.
- I prefer HDX Toolkit to block OTAs. Xposed is great (I use many modules) but does carry some minor risks as Leko mentioned. Note HDX toolkit requires a tethered connection (standard USB cable is fine) along with installation of Kindle drivers on the host machine.
- While a bit more involved I suggest you consider installing TWRP which will provide more robust recovery options should something go wrong. It is very easy to do given your current firmware level. Life without TWRP (or similar recovery) is like driving without a seatbelt.
- I have been using ggow's excellent implementation of the Nexus ROM. Rock solid and functional. The only minor downside is its Jellybean roots. ggrow is currently working on bringing newer variants to the table; Lollipop seems likely at some point. CM11 and CM12 are also available (or being worked on) but have some minor issues that may or may not matter to you.
I know you were hoping for a step-by-step tutorial. While that may become reality someday I suggest you spend an evening reading through the forums before deciding on a course of action. Yup, a ton of information is old/confusing but there is no one right answer for everyone. Ask questions along the way. Lots of folks are happy/willing to help if you've done your homework.
Good luck!
lekofraggle said:
Welcome. It is nice to see these questions asked before you have broken your device, as opposed to after. While I am by no means an expert, here are a few answers to get the ball rolling.
Click to expand...
Click to collapse
Thanks for the overview and answering my questions! I'm still iffy on the whole process but I'm going to do some reading before I decide if this is for me .
Davey126 said:
Some additional thoughts:
- Be sure to block OTAs before connecting to WiFi. Your options will become much more restricted if Amazon pushes an update.
- I prefer HDX Toolkit to block OTAs. Xposed is great (I use many modules) but does carry some minor risks as Leko mentioned. Note HDX toolkit requires a tethered connection (standard USB cable is fine) along with installation of Kindle drivers on the host machine.
- While a bit more involved I suggest you consider installing TWRP which will provide more robust recovery options should something go wrong. It is very easy to do given your current firmware level. Life without TWRP (or similar recovery) is like driving without a seatbelt.
- I have been using ggow's excellent implementation of the Nexus ROM. Rock solid and functional. The only minor downside is its Jellybean roots. ggrow is currently working on bringing newer variants to the table; Lollipop seems likely at some point. CM11 and CM12 are also available (or being worked on) but have some minor issues that may or may not matter to you.
Click to expand...
Click to collapse
Thanks for the reply. I'm especially grateful that you name-dropped some specific recommendations because it gives me a starting point to research. I have already read about TWRP (though as of yet I have no idea how to install it) and I will definitely take a look at HDX Toolkit.
I am probably going to try rooting while keeping an eye on the stock Android variant. I'm not sure if I'm ever going to be brave/clever enough to dare try that though. Bricking my device would seriously make me cry .
I have one more question about the Firmware versions (well, I probably have several, but this is the only one I remember right now.) I have seen somewhere on this forum that you can also upgrade the amazon firmware manually until you have the version you want instead of getting pushed to the newest one from amazon itself. Is that correct? If yes, which is the best version to stop on while still being able to root and keeping the option of stock Android open? I ask because I would like to strike a balance between a reasonably upgraded OS and one I still can do stuff with without getting nannied by amazon.
Here is where I recomend you start reading.
http://forum.xda-developers.com/showthread.php?t=2986004
This is the link for the thor twrp.
Here is how a normal device works.
You gain root permissions, and then if you mess up, you jump into a recovery and fix things. You probably (definitely) will lose some data, but you learn, curse, and move on with your life.
However, the bootloader of the Kindle hdx is locked. This means that if you cannot boot right, and you cannot get to recovery, you have a 200 paperweight.
Now, on the old firmware, brilliant people found a way to unlock (sort of) the bootloader. So, you have a pretty universal reset switch. This is why the recommendation is there to grab twrp. It really is helpful if you have a hankering to tinker. In reality there is less of a risk of bricking the device with it. Once you have it, then you can update to the newest firmware (in theory) if you do so the right way, you still keep twrp.
Now, if you want root and do not care about the safety belt, update to 13.4.5.2 and root it, but block updates.
But know, you lose the option of twrp at that point.
I hope this helps.
~Leko
Sent from my KFTHWI using Tapatalk
Edit: whether you go the easy route, and choose towelroot (just google it or go to towelroot.com for that route), the more involved twrp, or something in between, I highly recommend you learn what adb is and how to use it. The hdx toolkit comes with the drivers and it is not too difficult to use, but it is essential if you get into a sticky situation. Here is the toolkit link.
http://forum.xda-developers.com/showthread.php?t=2665683
lekofraggle said:
I hope this helps.
~Leko
Click to expand...
Click to collapse
Yes, this helps. Thank you! :good:
lekofraggle said:
Now, if you want root and do not care about the safety belt, update to 13.4.5.2 and root it, but block updates.
But know, you lose the option of twrp at that point.
Click to expand...
Click to collapse
@snorklm - you can go up to 13.3.2.6, secure root and still retain the option to later install TWRP and a different ROM without having to engage Amazon for a downgrade (you will still have to roll your device back to an earlier FW before installing TWRP but you can do this yourself). Note the 13.3.x.x series is based on the previous version of Fire OS (which in turn is based on Jellybean) but it remains perfectly serviceable. A lot is happening with more recent Amazon firmwares which ultimately may allow other ROMs and recoveries to be installed without having to downgrade to 13.3.x.x. Keep an eye on the forums.
Thanks for starting this topic snorklm. I was thinking in the same way whether it's worth to get it rooted or not.
I don't mind about the warranty as I think I will not break my Kindle Fire some how, just care about the services from Amazon Prime.
Actually I already contact Amazon service to roll back to version 3.2.5 and I'm waiting for the instruction email. My plan is going to root it, play around with the device then if something doesn't satisfy me, I will do un-root.
Would anyone show us the real advantages of rooting Kindle Fire here? As far as I know basic users just root their device to install Google Play Store which can be done on other un-rooted ones (like the method of Imma Wake) I still like Amazon service for Movies streaming so I'm a bit confused of what to do next, keep update it accordingly or give Rooting a try
Please share more your stories here.
Thank you
leoclark said:
Thanks for starting this topic snorklm. I was thinking in the same way whether it's worth to get it rooted or not.
Would anyone show us the real advantages of rooting Kindle Fire here?
Thank you
Click to expand...
Click to collapse
I ran with 3.2.6 (rooted) for nearly a year before installing a different ROM. I was able to obtain most apps from either the Amazon store or 1Moble. The primary reason I rooted was to squash various Amazon services that launch at boot and consume resources in the background (CPU, memory, battery). Goodreads, FreeTime and numerous communication services to name a few. I also wanted to install Xposed for a few modules I find especially handy and block OTAs to retain maximum flexibility. I side loaded many gapps but never installed the play store and associated services. Also Opera (never liked Silk). I retained my Prime privileges and for the most part enjoyed the mostly stock tablet as Amazon intended. Ultimately I began to miss some purchased apps not available elsewhere and longed for Apex or Nova. Other launchers can be made to run on Fire OS but the experience isn't as fluid. There is also something to be said about having a fairly consistent UI across my various Android devices.
While Fire OS isn't horrible I recommend rooting (when possible) and blocking OTAs to maximize current/future options As others have pointed out the act of rooting generally does not introduce instability unless the method used to exploit a vulnerability has side effects or the conditions for root are not fully met. There are some risks as you now have the power to brick your device. SuperSU (or similar privilege manager) is your friend and should keep you out of trouble if used judiciously.