[Q] Go back to complete stock - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

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.

Related

FAQ: Rooting

Since I asked a lot of question on this forum I would like to share the answers with everybody and maybe help them.
NOTE: Please don't post any replys as I want to keep the post clean and room for updates, send me a PM if you have and idea or any fails that I made in this post, if this post helped you don't post hit just the thanks button. Cheers.
Current list of questions with answers(will be updated):
Why would I want to root my phone?
Is rooting worth the trouble?
Is rooting illegal?
Will I have any customer support?
Is it dangerous?
Isn't rooting a complex and difficult process?
Will I still receive operating system updates from my carrier?
Application updates?
What if I want to un-root my phone?
Do I run the risk of bricking my phone?
Could my phone overheat and explode?
Why would I want to root my phone?
Everything in a Linux system is a file, or is treated as a file. Since Android runs on top of Linux, it acts the same way. Most of the files you will need to access or change are available to you without having elevated permissions. "Most" being the key term here. When you want to do things that affect or change the core software of your device -- like updating the version of Android on your phone, or adding a nice piece of software from another device -- you'll have to do it as root. Dream and Magic users have been running Eclair on their phones for a good while now, and it’s because they have rooted their device. Rooting also gives you access to some handy software that you couldn’t use otherwise. Things like a complete system backup or ad blocking software require you to root your device. Don’t root your phone just for the sake of rooting your phone, but if you come across something you feel you could use or would like to have, then consider it. You'll find that the open source community is usually pretty helpful and encouraging new people to do new things is common. And when you get to the point where you can lend a hand to the new folks, pay it forward.
Is rooting worth the trouble?
The answer is a resounding yes. The phone is faster than it has ever been, the battery lasts longer, and have all kinds of new features, including free wireless tethering and notification-bar widgets. Rooting your phone is generally a fairly quick process, though the complexity depends on your specific situation. Once you're rooted your handset, you can begin installing apps (many directly from Android Market) that will take advantage of your handset's new capabilities. Installing custom ROMs (replacement operating systems) built by hackers is a longer, more involved process , and generally involves your wiping all the data from your phone, but even that is worthwhile.
Is rooting illegal?
Nope. You bought the phone, it's your equipment, you own it, and you can do what you want with it. No one is going to come and get you, and your service provider will not cancel your contract. In fact, the U.S. federal government recognized the legality of rooting a phone in July 2010.
What you will do, however, is void the warranty on your device. If you don't want to live without a warranty, rooting isn't for you. Personally, I finally decided to take the plunge when I realized that the potential benefits outweighed the potential consequences. My phone was becoming slow and buggy, with lots of force-closes, and I was just about eligible for an upgrade anyway.
Will I have any customer support?
Rooting can be daunting because there is no toll-free number you can call for help, and no governing body to which you can turn for definitive answers. But the collective process of rooting phones and creating custom ROMs has engendered cool and supportive communities. The user-generated forums out there contain a staggering amount of information; the CyanogenMod forum has offered answers to almost all of my questions, as has the XDA Developers forum, but you can find many more. No matter your question, the forums most likely already have threads that can answer it. If you really can't find anything, you can always start a new thread to ask your question. If you think you've really mucked things up and you need immediate help, many IRC chat channels specialize in support for rooters. (Download an IRC client on your computer and head to irc.freenode.net, where the channels #android and #android-root are particularly helpful.)
Is it dangerous?
It can be, It might, and Yes. By not allowing access to the superuser account, the manufacturer and your carrier have basically protected you from doing things that change the system and make it unusable. All it takes is one wrong keystroke to turn your shiny new Android phone into a plastic and metal brick with no connection. Most times this is recoverable, but not always. You have to decide how capable you feel you are, and how well written the instructions you’ve found seem to be. Nobody will blame you if you decide against the risk, especially your cell carrier. All major carriers and manufacturers plainly state that altering or using unapproved software voids your warranty, and rooting falls into that category. While that seems a bit harsh, they need to be able to support the products they sell. For that to happen, they need to know exactly what’s running and what it’s doing.
Apps that run as root need a little further consideration. You need to have a level of trust in the person who wrote the app first and foremost. Does the developer have other software available? Do the user comments (for Market apps) have anything that raises a red flag? Do the requested permissions seem a little odd? These are all questions you need to think about before you allow something to run as root. For a further level of security, think about installing an application that warns you anytime something tries to run as root. SuperUser Whitelist is a great little app that does exactly that. If you decide to go on and root, ask users with the same device as you for a link to a version of SuperUser Whitelist that works with your firmware. Once installed, anytime something wants to run as root, the app intercepts and asks if you would like to allow it. You’re given the choice to accept, decline, or grant the app in question full privileges each time it runs.
One last thing to touch on here. Many custom ROMs include some sort of SSH server. This can be a wonderful tool, or it can get you in hot water. This is what caused the whole “Rick-Roll” episode with the latest iPhone jailbreak. The server sits and waits for an outside connection, and if that connection provides the right password full control of the device is turned over. In the case of the iPhone, users never bothered to change the default SSH password for root. A clever (or devious) group of users simply scanned for servers listening on the correct port, then attempted to sign in as root with the default password. Lesson learned, but this is easy to prevent. Ask other users of the ROM or firmware you’re thinking of flashing if there is a server listening, and if so how to disable it or change the default password.
Isn't rooting a complex and difficult process?
Yes and no. It really depends on what model of phone you have. On many phones (such as the Nexus One, Motorola Defy, or EVO 4G) the process is incredibly easy: You can download an app such as Simple Root, Universal 1-Click, or Z4root that will safely root your phone with a single click. Those apps are no longer available from the Android Market, but you can find them online with a simple search and install them onto an SD Card.
It is important to note that different approaches will work for different phones. For example, Z4root will work on many Android phones, but it won't work on most HTC models. Some rooting apps will work on an early build of Android 2.2 (Froyo), but will not work on later builds (though more and more apps are being released for that now). Rooting is phone/OS specific, so make sure to check that the root tool you're considering is compatible with your phone. For other models, rooting may take much more work. You might be required to connect the phone to your computer and enter some lines of code in a terminal utility.
Fortunately, more and more root apps do not require you to hook up your computer and get in that deep. Do some research as to what is required for your setup, read some step-by-step guides, and be honest with yourself about how comfortable you would be trying to follow the directions. If it feels like you'd be in over your head, it's probably best to avoid rooting.
Note that generally rooting is even tougher to do if you use a Mac, as most of the software for doing this sort of thing is written for Windows or Linux.
Will I still receive operating system updates from my carrier?
Maybe. More than likely if you’ve just rooted your phone so you could have access to the full file system and haven’t drastically changed things, the phone will still pass your carrier's checks and upgrade. If you’ve delved deeper and really customized your device, count on not being able to upgrade. Carrier updates were designed to work with the original software, so they need to be sure that’s what the phone is running. Again, this is for your own good. T-Mobile or Verizon can’t offer technical support for things they haven’t trained their technicians on, and if you flash a carrier approved update over custom software it’s probably not going to work.
The good news is that failing the checks the carrier does during an update won’t cause any damage to your phone. The update will just quit and you’ll be back where you started. Then you can decide if you would like to un-root and upgrade or take another path. The worst case scenario is that the phone passes the carriers checks, updates, and then things get broken. That’s pretty unlikely, but possible. If that would happen, you won’t be alone. Everyone in your situation will scramble to their favorite Android user forum and hopefully a work around can be found.
Note - a carrier update may also break the ability to root the device and a new method will need to be found. Any discussion of upgrading and root needs this mentioned as well. Most folks who root and decide to install a custom ROM wait for the ROM developer to provide an update that includes any bug fixes or new capabilities of the carrier update.
Application updates?
Yes. While it’s not being used, the program that allows permissions to be upgraded just sits and does nothing. Normal applications won’t even be aware it’s there, and applications that use it expect it to be there. Application updates, whether they are from the Market or other third parties will still install as normal.
What if I want to un-root my phone?
It depends on the model of your phone. Some are ridiculously easy to revert, some not so much. This is the most important question you can ask before you dive in and root your phone. Usually the website you found the method to root your phone will also have a discussion about un-rooting and going back to stock firmware. Take the time to find and read this information so you’re aware of just how difficult it’s going to be to go back. Pay close attention and create backups when recommended while you’re rooting your phone, as these may be needed to go back. I’ve not heard of any device that can’t be restored to factory firmware provided the original was backed up properly as recommended during the rooting process. The most important thing to always remember is to ask for help. If you do find yourself stuck without a backup or a working phone and need to roll back, ask for advice. Our forums are full of fine folks from all walks of life, and the majority are more than happy to help. There’s a good chance you’re not the first person in that situation and a solution has already been worked up!
Do I run the risk of bricking my phone?
This is one of the Internet's favorite bogeymen. "Bricking" is the idea that if you try to tinker with root access, you'll mess something up so it becomes completely unusable, and you'll essentially turn your phone into a paperweight. While that's certainly not outside the realm of possibility, the good news is that Android phones are generally very hard to brick. Yes, even the Droid X, which was purported to be the "unrootable" phone, has been safely rooted for quite some time (Z4root reportedly works with the Droid X).
If you do get caught in a boot loop, you may have to connect your phone to your computer and rewrite some code, but if you are patient and willing to do some more reading, you will almost always be able to find a way to at least restore your phone to its original state (read more on where that help comes from in the next section).
A common mistake that actually will lead to a bricked phone is running out of battery power in the middle of trying to install a custom ROM. The operating system only half installs, and that really is tough to fix. So always make sure that your battery is full before you install a new OS or ROM.
Also, just because a phone is rootable does not mean you can install any custom ROM you want. Differerent ROMs will work for different phones. Even the extremely popular CyanogenMod works for many phones, but certainly not all, so do plenty of research to make sure your phone is supported before trying to install a custom ROM.
Could my phone overheat and explode?
One of the major incentives to root your phone is the ability to overclock your processor to gain more speed (or underclock it to extend battery life). My phone has gotten considerably faster because of overclocking. When you overclock your processor, though, it will get hotter. If you try to push your phone too far and you don't set any fail-safes (a maximum allowable temperature in the overclocking utility), then you could burn out your processor. However, it is very easy to set safety thresholds to ensure that you don't do that.
SetCPU, the most popular app for overclocking or underclocking, allows you to set up various profiles.
Reading the rooting forums will give you plenty of advice on how far you can push your specific device and maintain stability. It pays to do some experimentation: Different phones behave differently, even if they're the same model.
Sources: androidcentral.com, pcworld.com
Useful threads:
[TUTORIAL] Unlocking, rooting, custom roms installing, going back to stock
[INDEX] HTC Desire X (protou) - Everything Desire X is here!
Reserved.

[Q] help getting back to stock

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.

[Q] Noob hoping for some advice (no, I didn't brick/break anything)

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.

To Root or Not To Root

i am buying a new phone, the S8+ to be exact, and there have been a lot of new developments (problems) when it comes to rooting your device. i've been rooting my smartphone devices for over 10 years because i love the freedom it brings (er, brought). Now i read things like Netflix, Snapchat, and AndroidPay not working on rooted devices. So i am wondering what people's experiences have been like. Any regrets? Are the trade-offs worth it to you? Is it worth being able to uninstall bloatware and install custom ROMs if a lot of other features and apps will stop working? i know most of this is personal preference but would like to know more about what other people have experienced.
billybag said:
i am buying a new phone, the S8+ to be exact, and there have been a lot of new developments (problems) when it comes to rooting your device. i've been rooting my smartphone devices for over 10 years because i love the freedom it brings (er, brought). Now i read things like Netflix, Snapchat, and AndroidPay not working on rooted devices. So i am wondering what people's experiences have been like. Any regrets? Are the trade-offs worth it to you? Is it worth being able to uninstall bloatware and install custom ROMs if a lot of other features and apps will stop working? i know most of this is personal preference but would like to know more about what other people have experienced.
Click to expand...
Click to collapse
First and foremost, if you plan on getting a US variant, meaning it will have a SD835 in it, Root is unlikely to come soon for it, This doesn't mean it won't happen, just not soon. Now if we're talking international, the ones that ship with an Exynos in it, they're rootable now.
Now, with that out the way let's get into the questions you've asked. There will indeed be a selection of apps that will not work when rooted these days because of "SafetyNet" check failure. Some of the biggest would be Snapchat and Android pay, However they will work with the assistance of Magisk which will allow SafetyNet to pass it's check, Same goes for most apps that fail to work because of root presence.
Heading back to what I first mentioned now, Rooting a Samsung device of recent years comes with some pretty notable cons to it, These would include loss of KNOX, I'm not sure what your stance on security is but if security is a concern to you, losing KNOX is not good. Another big and notable con is you will lose all Samsung pay support permanently, Actually to be honest both of the latter are permanently lost once rooted. If these things aren't a concern for you then by all means root away.
On to other things now, Rooting these days doesn't present as many attractive things as it use to, especially on a Samsung device. Most OEMS have given alternatives to many of the things a user couldn't do without root before. Currently there is no Xposed on Nougat and above, it's being worked on but there is no foreseeable date that can be given on when it will be completed.
So all in all, Until root is achieved for the Snapdragon variants, I'd hold off on a purchase of an S8. If we're talking Exynos variants then by all means get one, as I've said they're rootable right now. But don't let that be the ray of sunshine, though they're rootable, They're in infact an Exynos and Samsung is unwilling to provide source code to their Exynos chipsets. Which basically means to you that custom ROMs will be limited to rehashes of the stock ROMs with a couple mods if possible, AOSP such as Lineage and others like it are next to impossible to happen on Exynos without​ a source code to work from. It has been done before but the resulting roms took a long time to develop and either were extremely buggy or were just simply not usable for daily use.
I'm pretty sure I've hopefully covered every aspect I could but if you've got any more questions I'll surely answer them.
I apologise for this being so long lol.
Perfect. Thank you, this helped a lot.
billybag said:
Perfect. Thank you, this helped a lot.
Click to expand...
Click to collapse
Glad I could help, Again sorry it was a lengthy response but it was necessary to cover all of it.

Selling: Restore to Stock Kindle OS or just do a clean install of custom ROM?

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

Categories

Resources