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.
Related
ive read the thread in the general forum for noobs.
but i still dont quite understand all these things and what purpose they serve.
im SUPER new with all this stuff. so my apologies.
could someone help a brother out?
what is your question specifically?
just curious about what they are and do basically.
kevinallen4325 said:
ive read the thread in the general forum for noobs.
but i still dont quite understand all these things and what purpose they serve.
im SUPER new with all this stuff. so my apologies.
could someone help a brother out?
Click to expand...
Click to collapse
I'll try and help.
First you must ROOT your phone. This basically grants you access/permission to FIDDLE with a lot of things you can't normally. I use the word *fiddle* loosley, meaning you can install root tools (like overclock) custom Roms, change system settings, flash themes... the list goes on. It's kind of like the equivalent to "jailbreaking"
Rooting is the "first and foremost"... basically do this first. and all other things follow.
kevinallen4325 said:
just curious about what they are and do basically.
Click to expand...
Click to collapse
Well the sticky in the main forum really is a good place to start, as all these terms are defined there:
http://forum.xda-developers.com/showthread.php?t=1483113
As well as step-by-step instructions how to root. That should get you started!
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
It is much more than that. I wrote this out before, so I will copy it again:
People have problems when rooted because they are not careful or do not know what they are doing. Rooting gives you (to put in Windows terms) full Administrator rights to your phone. With this right comes responsibility, so you must be careful and do research. This is why rooting also voids the warranty. The phone is now open for the user to do whatever they want, and circumvent any restrictions put on the phone by the manufacturer (including those in place to prevent harm to the device). But like a computer with Admin rights, rooting allows you to install any application, any "OS theme", and tweak the hardware to do what YOU want with it, not what the manufacturer wants.
So please be sure to READ READ READ all you can before you start!!! You don't want a $600 phone coaster. Just browse the forums for a couple weeks and learn from the posts.
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
It depends what you consider a benefit. Sure..theming can be a benefit, but rooting provides the gateway to address any negative or less than ideal aspects of a device. For instance, The Note has been perceived as being somewhat laggy. So rooting allows you to free up system resources by eliminating unneeded bloatware that you can't remove if you remain stock. Also the lagginess has been addressed by overclocking, modding and building kernels that do specific things and of course making custom roms. The Note is still very early in the developmental process, so many things to improve the user experience of the device will become available over the course of time....but it all starts with being rooted.
Sent from my Samsung Galaxy Note LTE™
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
Android isn't like iOS. I had an iPhone for four years before my Note and I know where you coming from. What the other guy was saying is that rooting can be viewed similar to jailbreaking, but it is kind of completely different. You don't need to be rooted to use themes (or most of the stuff on Cydia). Rooting allows you to back up apps, flash custom ROMs, etc. Otherwise, you most likely don't need root.
tbran said:
It depends what you consider a benefit. Sure..theming can be a benefit, but rooting provides the gateway to address any negative or less than ideal aspects of a device. For instance, The Note has been perceived as being somewhat laggy. So rooting allows you to free up system resources by eliminating unneeded bloatware that you can't remove if you remain stock. Also the lagginess has been addressed by overclocking, modding and building kernels that do specific things and of course making custom roms. The Note is still very early in the developmental process, so many things to improve the user experience of the device will become available over the course of time....but it all starts with being rooted.
Sent from my Samsung Galaxy Note LTE™
Click to expand...
Click to collapse
if i were to root it and do whatever else would that affect the notes ability to update itself when the time comes?
like if i were to put some custom rom or whatever on it and lets say ics came out (lulz) would it still be able to update to it, and would it basically remove everything i did to it
kevinallen4325 said:
if i were to root it and do whatever else would that affect the notes ability to update itself when the time comes?
like if i were to put some custom rom or whatever on it and lets say ics came out (lulz) would it still be able to update to it, and would it basically remove everything i did to it
Click to expand...
Click to collapse
Trust me, if you go the root and custom rom way, you will never install an official update. not because you can't, but because it will be leaked and debloated months before it is official.
i installed saurom. with and ics theme. i like it alot. but i cant get into setcpu or any program that requires root access. which is kind of an issue. no one else seems to be having that as an issue.
I rooted my Note a couple days ago and am still trying to figure out the benefits of doing so. I guess just spend time reading through this forum for the answers. That's what I am doing, but so far I see no benefit at all. The phone does all I want it to do so far. Maybe I am missing something.
Also, When i run quadrant, the scores are consistently lower after rooting the device then they were before. Not sure why though.
You are correct that the Note and newer phones may need no help. Not like two years ago. But, the big advantage to rooting even if you don't want to flash roms is Titanium Backup for app mgt and nandroids or full image backups--imho. The other like mentioned is earlier os releases. I have had ICS on my N1 for quite awhile and is still not on most new phones.
Ken
kevinallen4325 said:
i installed saurom. with and ics theme. i like it alot. but i cant get into setcpu or any program that requires root access. which is kind of an issue. no one else seems to be having that as an issue.
Click to expand...
Click to collapse
If you are sure you are rooted, a dialog box with a little Android head wearing an eyepatch will pop up asking if you want to allow the application to have root access. You must allow it here.
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.
Hello,
I've seen some threads on rollbacks but want to be sure I'm doing it right since I'm on an old version.
I have a Apollo 8.9. I can't even remember all the steps I took to get Google apps, but I know I'm on 3.2.5 and have the HDXposed module installed to block updates etc. I'm on Safestrap v 3.75. All I want to do is get back to factory stock latest version so I can sell this. I don't care about getting root again or custom ROMs.
Any help is appreciated. Thanks!
Tim
Imo, it would be easier to sell as is. Many people want the flexibility that your device has. The ability to have a wonderful screen and be able to put one of many roms on it.
lekofraggle said:
Imo, it would be easier to sell as is. Many people want the flexibility that your device has. The ability to have a wonderful screen and be able to put one of many roms on it.
Click to expand...
Click to collapse
Agreed. Clearly state the firmware version and indicate the bootloader can be unlocked. Knowledgeable buyers will recognize what this means and may be willing to pay for this capability. Where to sell it and a fair asking price are unknowns (at least to me).
Ironically, market value may be reduced somewhat by a flurry of recent tool/rom releases that work on rooted HDX devices regardless of firmware level as it opens the door for many users who were previously shut out - unless they had a device like yours.
Attempting to restore you device to 'factory defaults' introduces risks that could yield a brick. Best not mess with it unless you are willing to assume those risks.
I have two THOR devices. Kindle HDX 7. (They're confiscated from my daughters. Long story short...don't have kids )
I want to sell them. They both currently have Nexus 4 installed, but they got there in different ways:
Tablet 1: started with 4.5.5 software
rolled back to 3.8.2
rolled up to 4.5.2 software
rooted with cve apk
OTA blocked by changing file name from to "donottouch..."
running safe strap version 4.0.1
back up of kindleos created and saved to laptop
flashed nexus 4 rom
flashed gaaps
created backup of nexus rom. deleted kindleos backup roms (from tablet I believe)
flashed supersu
wiped and rebooted
Tablet 2: started with 4.5.5.1 software
Rooted with King root version 4.8.0
blocked OTA updates by renaming file to "donottouch..."
installed safestrap 4.0.1
did not create backup of Kindle Android. Backup failed.
flashed nexus 4 rom
flashed gaaps
created backup of nexus rom
flashed supersu
wiped and rebooted
It appears, from the little bit of reading I've done before posting, that it might be best NOT to roll all the way back to the Stock Kindle OS. And that when I sell them to specify that they're rooted and OS they are running. Is this correct? And reasoning is because of the risk of bricking? If I chose to try this anyway, would someone be so kind as to point me in the direction of some instruction? (I'd at least like to read some on it) In addition, can I use the same method on both tablets seeing as how they were rooted differently? Or do I need to use two different methods to go back to stock?
Is my best option to just wipe/reinstall the nexus 4 ROM/OS? If so, I would guess that it's the same process for both tablets and that it's not too difficult? And could someone be so kind as to point me in the direction of instructions for this?
And I would welcome any other advice and tips that anyone would like to share.
Just out of curiosity, I'm wondering how these compare to tablets on the market now. Are they worth keeping/using? Or are there better options out there? I'm not one for rooting and playing around with them much, so that wouldn't be a factor for me.
anonymous93 said:
I have two THOR devices. Kindle HDX 7. (They're confiscated from my daughters. Long story short...don't have kids )
I want to sell them. They both currently have Nexus 4 installed, but they got there in different ways:
:
Just out of curiosity, I'm wondering how these compare to tablets on the market now. Are they worth keeping/using? Or are there better options out there? I'm not one for rooting and playing around with them much, so that wouldn't be a factor for me.
Click to expand...
Click to collapse
I would sell them as-is with the caveats noted. Otherwise you risk investing hours with little financial return. Going price for these pups is a fraction of original list and directly competes on price with contemporary Amazon offerings.
As for functional/hardware comparison HDX devices crush (far superior to) anything Amazon offers today which are just glorified, low spec shopping portals. Three are few alternatives from other vendors; those that exist carry much higher price tags. 3rd gen devices can be fully unlocked which opens the door to a variety of contemporary (Android 7/Nougat) ROMs. In short, a gently used HDX represents an outstanding value for those seeking a higher end experience (especially screen quality) in a small tablet form factor. Just have to find the right buyer.
Davey126 said:
3rd gen devices can be fully unlocked which opens the door to a variety of contemporary (Android 7/Nougat) ROMs. In short, a gently used HDX represents an outstanding value for those seeking a higher end experience (especially screen quality) in a small tablet form factor. Just have to find the right buyer.
Click to expand...
Click to collapse
Fully unlocked? I'm assuming more than what I've already done? Because I think when I did these tablets you still couldn't unlock the bootloader. I don't think I'd mind going to the trouble of getting android 7 on these tablets. Is there a specific thread or post that outlines the steps for this process? Sounds like I might be doing a lot of reading over the next week or so.
anonymous93 said:
Fully unlocked? I'm assuming more than what I've already done? Because I think when I did these tablets you still couldn't unlock the bootloader. I don't think I'd mind going to the trouble of getting android 7 on these tablets. Is there a specific thread or post that outlines the steps for this process? Sounds like I might be doing a lot of reading over the next week or so.
Click to expand...
Click to collapse
See linked thread. Be aware it is loaded with tons of misinformation along with a few gems. You'll need to a lot of reading and confidence building before taking this on. The actual unlock steps are not difficult and fairly reliable when performed correctly. Details matter; most stories of woe begin with shortcut attempts gone bad. Best approach is to read, develop a game plan and then post a brief summary of how you plan to proceed along with any questions. Good luck.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982