Android LolliCrap 5.02 has totally screwed over my N7 2012 8GB, LolliCrap OS and accompanying support apps like Google Play are such Bloatware that none of my apps can update (insufficient space BS) when I had 1GB free before with OS 4.4.4!! Beside I HATE the new interface, it's SLOOOOOOOW and is some kind of nightmare! My M7 8GB is essentially BRICKED and useless now!! I hate you Google!
I also have a 2012 N7 32GB still running HAPPILY 4.4.4 and I want to keep it that way and NOT Screw it over too with any version of 5.x
HOW can I block the download of LolliCrap 5.x so it's not sitting there taking up Memory space because I will never install it and how can I block all future Android OS updates??? I'd rather NOT Root if at all possible, I'm not sure I'm technically qualified to Root my N7's.
I used to be a huge fan of Google and Android, this POS LolliCrap really has me pissed off .... I just may go and buy the "enemy" iFad Mini now!!
VintageGuitarz said:
Android LolliCrap 5.02 has totally screwed over my N7 2012 8GB, LolliCrap OS and accompanying support apps like Google Play are such Bloatware that none of my apps can update (insufficient space BS) when I had 1GB free before with OS 4.4.4!! Beside I HATE the new interface, it's SLOOOOOOOW and is some kind of nightmare! My M7 8GB is essentially BRICKED and useless now!! I hate you Google!
I also have a 2012 N7 32GB still running HAPPILY 4.4.4 and I want to keep it that way and NOT Screw it over too with any version of 5.x
HOW can I block the download of LolliCrap 5.x so it's not sitting there taking up Memory space because I will never install it and how can I block all future Android OS updates??? I'd rather NOT Root if at all possible, I'm not sure I'm technically qualified to Root my N7's.
I used to be a huge fan of Google and Android, this POS LolliCrap really has me pissed off .... I just may go and buy the "enemy" iFad Mini now!!
Click to expand...
Click to collapse
Without root, you can't block the updates. I'm using a custom 5.0 rom on my 2012 N7 and it's actually pretty snappy. I also changed the file system to F2FS and cranked up the GPU speeds though so that might have something to do with it. The Nexus stuff is one of the easiest things to root out there. I believe there are ways to do so without even unlocking the bootloader, which will require wiping the device completely. There are tool kits in the forum for your device that should help you do this with minimal effort.
Rooting is something I have not even attempted, can anyone recommend a tutorial, video and how to accomplish the rooting process on a N7 2012 for a newbie to rooting?? I've been in IT, but the hardware end, so I'm not tech challenged, just no experience on the SW Hacking side. I've got to get my N7 2012 32GB model blocked before it's devastated by 5.02 too!!
I'd also like to "Revert" my already "attacked" N7 8GB 2012 back to KitKat 4.4.4, is that possible? I've looked at Android OS DL's but which model name is the 2012 N7? "nakasi" or which??
Any help and suggestions from the experts on the forum appreciated.
VintageGuitarz said:
Rooting is something I have not even attempted, can anyone recommend a tutorial, video and how to accomplish the rooting process on a N7 2012 for a newbie to rooting?? I've been in IT, but the hardware end, so I'm not tech challenged, just no experience on the SW Hacking side. I've got to get my N7 2012 32GB model blocked before it's devastated by 5.02 too!!
I'd also like to "Revert" my already "attacked" N7 8GB 2012 back to KitKat 4.4.4, is that possible? I've looked at Android OS DL's but which model name is the 2012 N7? "nakasi" or which??
Any help and suggestions from the experts on the forum appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1766475
This tool / thread will have everything you need. You can root and downgrade with it. The "manual" way is not difficult either. You were correct, it is the "nakasi" model. Just need the drivers installed, extract the folder from the download (use 7zip if you don't have an app on your PC already for those kinds of files), reboot to the bootloader screen (power off then power on by holding Vol Down and Power), plug into the PC and make sure the drivers load, then double click the flash-all.bat file in the folder and let it do it's thing.
Thanks.
Gentlemen,
Thanks for all the information and I will review the links you supplied and I will take a shot at Rooting my 2 N7 2012's to keep any nasty 5.0x updates off until Google comes to their senses! Serously, 8 days after Android 5.02 invaded my N7 8GB, it still runs like crap, balks, stalls, crashes, even Services crashes and stalls routinely. .... Google has made a mess of this version of Android OS 5.x, damn them. All just to serve their stupid "wearable" as I have read on several Android sites. Google is turning into CrApple.
VintageGuitarz said:
Gentlemen,
Thanks for all the information and I will review the links you supplied and I will take a shot at Rooting my 2 N7 2012's to keep any nasty 5.0x updates off until Google comes to their senses! Serously, 8 days after Android 5.02 invaded my N7 8GB, it still runs like crap, balks, stalls, crashes, even Services crashes and stalls routinely. .... Google has made a mess of this version of Android OS 5.x, damn them. All just to serve their stupid "wearable" as I have read on several Android sites. Google is turning into CrApple.
Click to expand...
Click to collapse
I often find issues like that are caused from not resetting your device after OTAs. This kind of thing happens often enough between jumping OS versions, and is not just for the Nexus, but I've seen and read about it for every manufacturer, and even for Apple devices. There are plenty of people using Lollipop on the N7 without issues. Just every device is a bit different, even before you start adding your own apps and data.
es0tericcha0s said:
I often find issues like that are caused from not resetting your device after OTAs. This kind of thing happens often enough between jumping OS versions, and is not just for the Nexus, but I've seen and read about it for every manufacturer, and even for Apple devices. There are plenty of people using Lollipop on the N7 without issues. Just every device is a bit different, even before you start adding your own apps and data.
Click to expand...
Click to collapse
I beg to greatly differ with your opinion regarding the number of Nexus owners (at least older models) having problems with Lollipop OS, along with owners of other brands of phones and tablets. While looking for reason for all the problems I've experienced and how to fix or revert back to KitKat 4.4.4 (because it worked flawlessly) and how to block further Lollicrap 5.0x updates, I've "Googled" and visited at least 30 of 40 different forums, blogs, postings and news reports that EVERYONE chastises, complains and hates Lollicrap 5.0x. Even Bloomberg News has runs a few news stories about why everyone hates Android 5.0x Lollipop and won;t use it. Several Tech writers have pointed out that the main purpose of Lollicrap 5.0x is to promote Google's android based "Wearable" and obviously from all the complaints by us, we've been sacrificed for their greed.
Sorry, If I got to wipe out all my app installs and start all over again with a "reset", I won't waste my time with Buggy and Kluged LolliCrAp 5.0x anything and these will be the last Google product I'll ever buy ..... they've become CrApple! All for the money of it and screw the previous model owners. My next new Tablet will be a Surface Pro.
VintageGuitarz said:
I beg to greatly differ with your opinion regarding the number of Nexus owners (at least older models) having problems with Lollipop OS, along with owners of other brands of phones and tablets. While looking for reason for all the problems I've experienced and how to fix or revert back to KitKat 4.4.4 (because it worked flawlessly) and how to block further Lollicrap 5.0x updates, I've "Googled" and visited at least 30 of 40 different forums, blogs, postings and news reports that EVERYONE chastises, complains and hates Lollicrap 5.0x. Even Bloomberg News has runs a few news stories about why everyone hates Android 5.0x Lollipop and won;t use it. Several Tech writers have pointed out that the main purpose of Lollicrap 5.0x is to promote Google's android based "Wearable" and obviously from all the complaints by us, we've been sacrificed for their greed.
Sorry, If I got to wipe out all my app installs and start all over again with a "reset", I won't waste my time with Buggy and Kluged LolliCrAp 5.0x anything and these will be the last Google product I'll ever buy ..... they've become CrApple! All for the money of it and screw the previous model owners. My next new Tablet will be a Surface Pro.
Click to expand...
Click to collapse
Human nature - people are more likely to post complaining about things than complimenting them. Name an update on any device that you can't find people having issues with. Nature of the beast. But as I mentioned, the problems you are experiencing are very typical of issues with OTA updates and not factory resetting the device.
es0tericcha0s said:
Human nature - people are more likely to post complaining about things than complimenting them. Name an update on any device that you can't find people having issues with. Nature of the beast. But as I mentioned, the problems you are experiencing are very typical of issues with OTA updates and not factory resetting the device.
Click to expand...
Click to collapse
But you also have to take into account, that the vast majority of any device users, especially Smart Phones and Tablets, are not technologically "equipped" and DON'T B n C on-line and don't do postings looking for help, they just get pissed and move to another device or OS. So I postulate that all these hundreds of posts are an accurate reflection of the total percentage of people having issues with Android 5.0x and that since the tech media is taking note of it, it's the true nature of the problems. Sorry, my N7 2012 was pristine, ran perfectly under KitKat 4.4.4. If I'm having problems after and OTA update, so are the majority. It's just common sense and the odds.
VintageGuitarz said:
But you also have to take into account, that the vast majority of any device users, especially Smart Phones and Tablets, are not technologically "equipped" and DON'T B n C on-line and don't do postings looking for help, they just get pissed and move to another device or OS. So I postulate that all these hundreds of posts are an accurate reflection of the total percentage of pe If I'm having problems after and OTA update, so are the majority. It's just common sense and the odds.ople having issues with Android 5.0x and that since the tech media is taking note of it, it's the true nature of the problems. Sorry, my N7 2012 was pristine, ran perfectly under KitKat 4.4.4.
Click to expand...
Click to collapse
So many leaps of logic, assumptions, and lack of understanding of how software updates work here, it's not even worth getting into. If you need help downgrading, I'd be more than happy to help though. You can hit me up on Hangouts @ my screen name if you'd like.
Apparently the 5.02 Lollicrap Update is down loaded to your N7 (maybe other devices as well) without your permission when connected online.
Where is it stored as a file, in what folder and can it be deleted, prior to Rooting the N7?
I'd like help with Rooting both of my N7's (2012's), returning one back to KitKat 4.4.4 and keeping the other 32GB 2012 N7 from ever being updated without my permission.
Thanks
VintageGuitarz said:
Apparently the 5.02 Lollicrap Update is down loaded to your N7 (maybe other devices as well) without your permission when connected online.
Where is it stored as a file, in what folder and can it be deleted, prior to Rooting the N7?
I'd like help with Rooting both of my N7's (2012's), returning one back to KitKat 4.4.4 and keeping the other 32GB 2012 N7 from ever being updated without my permission.
Thanks
Click to expand...
Click to collapse
It should be in the /cache folder, which you won't have access to without root.
http://forum.xda-developers.com/showthread.php?t=1766475
Everything you need will be in that thread. As long as the drivers are loaded correctly and you have a good USB cable, the toolkit should be able to do everything else as far as rooting and downgrading. Once you are rooted, then I think you should be able to stop notifications/downloads of the updates by following this 1st post:
http://forum.xda-developers.com/showthread.php?t=2429820
and / or might need to do this too:
http://forum.xda-developers.com/showpost.php?p=53169162&postcount=21
Or install a custom rom.
I'm not so cool with "Leaps" of logic in your instructions that seem to contain a lot of "I think", "should be ale to", or "and / or might need to do this too", or "Or install a custom rom". I've never Rooted anything, this seems more like guess work than a proven method and I'm not about to sacrifice my working 32GB N7 with KitKat 4.4.4 "experimenting".
By this loose method you're advising, my logic in saying the majority of Android users are pissed (referenced dozens and dozens of forum sites) but most silent about LolliCrap screwing up their devices, is like the proven theory of relativity.
I'll keep looking for a forum thread by someone that has, with no "might have to", or "should's" in the process.
Thanks anyway.
VintageGuitarz said:
I'm not so cool with "Leaps" of logic in your instructions that seem to contain a lot of "I think", "should be ale to", or "and / or might need to do this too", or "Or install a custom rom". I've never Rooted anything, this seems more like guess work than a proven method and I'm not about to sacrifice my working 32GB N7 with KitKat 4.4.4 "experimenting".
By this loose method you're advising, my logic in saying the majority of Android users are pissed (referenced dozens and dozens of forum sites) but most silent about LolliCrap screwing up their devices, is like the proven theory of relativity.
I'll keep looking for a forum thread by someone that has, with no "might have to", or "should's" in the process.
Thanks anyway.
Click to expand...
Click to collapse
Sorry for not being more clear.
The update zip IS in the /cache folder, which you won't have access to without root.
The toolkit on from the link I provided has nothing to do with guess work as it is the easiest way to downgrade and root and has everything you need from the drivers to the root files to being able to download the 4.4.4 firmware and flash for you with very minimal interaction. As far as the notifications go, some people get away with one method, some have to do both. If you would feel more comfortable with someone helping via TeamViewer, I'd be willing to. I literally do this kind of stuff as a job and have experience with every kind of flashing, modding, upgrades, downgrades, etc for 100s of devices, as well as owning the same tablet you have.
Thanks for the clarifications, I'll download the Toolkit and run it to familiarize myself with it. If it looks confusing to me, I'll take you up on the offer to help using TeamViewer. I've used TV a few times with my IT clients.
Do you know which cashe folder Android stores the updates in? And once rooted and updates blocked, can I just delete that 5.02 file (I'm think my other 2012 N7 32GB which has not been updated)??
It's just in the /cache folder in the root of the OS. Yes, you can delete it without issue, though it's not going to give you any more usable apace as it's a different partition of the device that the normal data you save doesn't have access to. Still, might as well delete it.
Sent from my A0001 using XDA Premium 4 mobile app
es0tericcha0s said:
It's just in the /cache folder in the root of the OS. Yes, you can delete it without issue, though it's not going to give you any more usable apace as it's a different partition of the device that the normal data you save doesn't have access to. Still, might as well delete it.
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's been a while and I still haven't Rooted my Nexus 7, been researching the mechanics of how to do it and what methods are available that a complete "rooting newbee" can use without getting over my head in quicksand and a bricked N7 (2012) instead of one taken back to Kitkat 4.4.4 from a screwed up buggy 5.02 OTA update.
I was looking at a tutorial for using " Wugfresh" tool and a comment was made that "Unlocking will wipe the device.". Is this true? Is this always the case when rooting and unlocking?
I don't want to "wipe" my N7, just root it and return it to 4.4.4.
I also read that the boot loader in the factory 4.4.4 is faulty and a lot of girations are needed to reinstall 4.4.4. Has anyone experienced this?
Appreciate the thoughts and ideas.
VintageGuitarz said:
It's been a while and I still haven't Rooted my Nexus 7, been researching the mechanics of how to do it and what methods are available that a complete "rooting newbee" can use without getting over my head in quicksand and a bricked N7 (2012) instead of one taken back to Kitkat 4.4.4 from a screwed up buggy 5.02 OTA update.
I was looking at a tutorial for using " Wugfresh" tool and a comment was made that "Unlocking will wipe the device.". Is this true? Is this always the case when rooting and unlocking?
I don't want to "wipe" my N7, just root it and return it to 4.4.4.
I also read that the boot loader in the factory 4.4.4 is faulty and a lot of girations are needed to reinstall 4.4.4. Has anyone experienced this?
Appreciate the thoughts and ideas.
Click to expand...
Click to collapse
Literally just finished helping someone with downgrading back from LP because it wasn't working well for them either. You absolutely have to unlock the bootloader, which will wipe the device, no matter what you want to do - root / recovery / downgrade / etc. This is not an option as it is a security feature. There are so many ways to back up most of your stuff that it's really not THAT big of a deal. There are apps, Google, cloud storage, etc.
Yeah in doing my "research" on rooting to turn back the calendar to Kitkat 4.4.4 I've read more and more pretty pissed off N7 owners, seems to have hit the 2012 and 2013 model owners the most grievously.
Question then if I backup - since I'm on LP 5.02 on my 8GB N7 (2012) already, when I do a back up won't it also take with some of the LP oriented settings?
Is there a highly preferred BU method that will take everything from data, settings and apps so after I root and reinstall (flash?) 4.4.4 on a wiped N7 it puts everything back? Is there a BU method I can use to BU's to my PC, rather than a cloud? (I don't have a 8GB "cloud account with anyone)
Thanks very much.
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.
Hello
I recently got a Kindle Fire HDX 7.
Beside it being an extremly awesome device, i really wished i could get the Playstore on it like you can with the newer Ones.
I did spend quite some time reading about it here on XDA and elsewhere, but since those informations are like scattered in posts from 2013 until today i am a bit confused and don´t know which Methods are making sense now or just outdated...
Also i have the device on FireOS 4.5.5.3.
Is it possible to do this without too high risk?
I really could need some advice...
Drachenberg said:
Hello
I recently got a Kindle Fire HDX 7.
Beside it being an extremly awesome device, i really wished i could get the Playstore on it like you can with the newer Ones.
I did spend quite some time reading about it here on XDA and elsewhere, but since those informations are like scattered in posts from 2013 until today i am a bit confused and don´t know which Methods are making sense now or just outdated...
Also i have the device on FireOS 4.5.5.3.
Is it possible to do this without too high risk?
I really could need some advice...
Click to expand...
Click to collapse
Bootloader can be unlocked opening the door to all custom ROMs available for this device. Google services/store does not play nice with FireOS v4.
See here for overview of procedure. There is risk involved which can be effectively mitigated by carefully reading posted guidance and asking targeted questions BEFORE acting. Comfort with technology a strong plus. There are no step-by-step noob guides or videos. You'll need to do some reading and strap on a temporary propeller hat. Beverage of choice should be non-intoxicating if taking to the keyboard. Reward is a fully unlocked/unleashed device that competes favorably with contemporary hardware and far superior to any tablet Amazon sells today. That not just fanboy talk - a peek as the specs will quickly reveal the differences which play out in real world usage. Banging this out on a HDX 7 running a Nougat based ROM with full access to all Google services.
Davey126 said:
Bootloader can be unlocked opening the door to all custom ROMs available for this device. Google services/store does not play nice with FireOS v4.
See here for overview of procedure. There is risk involved which can be effectively mitigated by carefully reading posted guidance and asking targeted questions BEFORE acting. Comfort with technology a strong plus. There are no step-by-step noob guides or videos. You'll need to do some reading and strap on a temporary propeller hat. Beverage of choice should be non-intoxicating if taking to the keyboard. Reward is a fully unlocked/unleashed device that competes favorably with contemporary hardware and far superior to any tablet Amazon sells today. That not just fanboy talk - a peek as the specs will quickly reveal the differences which play out in real world usage. Banging this out on a HDX 7 running a Nougat based ROM with full access to all Google services.
Click to expand...
Click to collapse
Can confirm - I just picked up a 16gb on Craigslist this morning, and had it running Lineage 14 by 2pm. Great piece of hardware. Use the guides to the letter and you'll have no trouble at all.
Davey126 said:
Bootloader can be unlocked opening the door to all custom ROMs available for this device. Google services/store does not play nice with FireOS v4.
See here for overview of procedure. There is risk involved which can be effectively mitigated by carefully reading posted guidance and asking targeted questions BEFORE acting. Comfort with technology a strong plus. There are no step-by-step noob guides or videos. You'll need to do some reading and strap on a temporary propeller hat. Beverage of choice should be non-intoxicating if taking to the keyboard. Reward is a fully unlocked/unleashed device that competes favorably with contemporary hardware and far superior to any tablet Amazon sells today. That not just fanboy talk - a peek as the specs will quickly reveal the differences which play out in real world usage. Banging this out on a HDX 7 running a Nougat based ROM with full access to all Google services.
Click to expand...
Click to collapse
I try to setup for following that Guide. I downloaded all the stuff, the TWRP and also the Thor TWRP 3.1.1-1 image.
But how do i get that aboot_vuln.mbn? I did some research but i don´t understand from where to get that file.
Please Help.
Got it!
Figured it out finally
I even did the same with my recently bought HDX 8.9 Apollo right now!
The second time it took just a few Minutes and both run Slim 7 with Gapps Pico now
Thank you guys!
Bigolac said:
Can confirm - I just picked up a 16gb on Craigslist this morning, and had it running Lineage 14 by 2pm. Great piece of hardware. Use the guides to the letter and you'll have no trouble at all.
Click to expand...
Click to collapse
Did you follow the guide on that link you quoted? I'm not sure was ROM to use to get authentic Android but Lineage seems to be the best bet.
hwwof said:
Did you follow the guide on that link you quoted? I'm not sure was ROM to use to get authentic Android but Lineage seems to be the best bet.
Click to expand...
Click to collapse
Yes i followed the Guide.
I just use Slim 7 with pico gapps on both devices. Works well for me
Drachenberg said:
Yes i followed the Guide.
I just use Slim 7 with pico gapps on both devices. Works well for me
Click to expand...
Click to collapse
Thanks for the reply! Can you link me to those? Also, i just posted a help thread and I would really appreciate your input on any of the questions!
---------- Post added at 11:40 PM ---------- Previous post was at 11:38 PM ----------
Davey126 said:
Bootloader can be unlocked opening the door to all custom ROMs available for this device. Google services/store does not play nice with FireOS v4.
See here for overview of procedure. There is risk involved which can be effectively mitigated by carefully reading posted guidance and asking targeted questions BEFORE acting. Comfort with technology a strong plus. There are no step-by-step noob guides or videos. You'll need to do some reading and strap on a temporary propeller hat. Beverage of choice should be non-intoxicating if taking to the keyboard. Reward is a fully unlocked/unleashed device that competes favorably with contemporary hardware and far superior to any tablet Amazon sells today. That not just fanboy talk - a peek as the specs will quickly reveal the differences which play out in real world usage. Banging this out on a HDX 7 running a Nougat based ROM with full access to all Google services.
Click to expand...
Click to collapse
Davey, I would really appreciate your input on my specific thread. I followed your advice and asked targeted questions. Thank you so much for everything you do on this forum!