Hello all, I appreciate any help you could give me.
I just recently bought a Kindle Fire (2015) with the intention of rooting it out, and throwing CyanogenMod on there, but I'm having trouble finding solid, step-by-step instructions. I'm not entirely unfamiliar with the process in general, I currently own a Nook Color that I did the same thing with. Originally my Nook was running off an SD card that had CM on it as part of a bootable SD card, but after a while I had decided to just skip the extra step, free up a little bit of space on the card, and throw it natively onto the Nook.
However, time has not been kind to my poor Color and with the 5th Gen Kindle being almost comically cheap, (I got it during a recent sale for less than 40 bucks after shipping) and way more powerful than my poor Nook it looked like it was time to retire my beloved tablet.
I've got a passing familiarity with how ADB works, and I've used some of the tools for college work. I've rummaged through CM's wiki on the unofficial release for the system, but honestly the thread on here for the process is not very concise. It gives leaps of steps, rather than an Idiot Proof methodology and I'd really rather not brick out the tablet no matter how cheap it cost.
Alternatively! I really only used my Nook for book reading, I just didn't like the limited functionality that it offered originally, is there any suggestions on other possible ROMs that would offer a bit more functionality without the somewhat unnecessary power that CM offers?
I appreciate, greatly, any guidance that you all could offer me. :highfive:
First step, turn off the wifi, then go into settings, Device Options, System Updates and see what Fire OS it says you are running.
If as I suspect it's 5.1.1 then you can't root or install any roms atm.
Pond-life said:
First step, turn off the wifi, then go into settings, Device Options, System Updates and see what Fire OS it says you are running.
If as I suspect it's 5.1.1 then you can't root or install any roms atm.
Click to expand...
Click to collapse
Most likely it is, but just out of curiosity, I don't currently have anything on it, so if I were to set it back to factory defaults would it still keep the 5.1.1, or since when I got it it updated (Which is why I think it does have the 5.1.1 as you said) would it bounce back to the previous version?
If it does bounce back, any suggestions on where to go to try and proceed with the rooting?
Vez'Roth said:
so if I were to set it back to factory defaults would it still keep the 5.1.1
Click to expand...
Click to collapse
Yep, once the fire updates itself, you're stuck with it. And don't try to manually side load 5.0.1, results in a brick.
No root is available for 5.1.1. No custom ROMs. Only thing you can currently do on 5.1.1 is install google play store.
Vez'Roth said:
Most likely it is, but just out of curiosity, I don't currently have anything on it, so if I were to set it back to factory defaults would it still keep the 5.1.1, or since when I got it it updated (Which is why I think it does have the 5.1.1 as you said) would it bounce back to the previous version?
If it does bounce back, any suggestions on where to go to try and proceed with the rooting?
Click to expand...
Click to collapse
Nope factory defaults doesn't affect the system only personal files, it would be on a clean 5.1.1 which it already is.
And trying to revert from 5.1.1 to the old 5.0.1 bricks the tablet.
So if it is on that, your quest to apply a different rom of any kind is thwarted for now.
Pond-life said:
Nope factory defaults doesn't affect the system only personal files, it would be on a clean 5.1.1 which it already is.
And trying to revert from 5.1.1 to the old 5.0.1 bricks the tablet.
So if it is on that, your quest to apply a different rom of any kind is thwarted for now.
Click to expand...
Click to collapse
Thank you for responding at least. I will remain thwarted, but I am sure that this will not stop you all, or me, for long. It'll be broken open again. I don't know why these companies are so against it.
Vez'Roth said:
Thank you for responding at least. I will remain thwarted, but I am sure that this will not stop you all, or me, for long. It'll be broken open again. I don't know why these companies are so against it.
Click to expand...
Click to collapse
Because they're EVILLLLL!
[emoji49] [emoji35] [emoji48]
[emoji83]
lol
Related
So today I was at work and a little notification popped up about a software update. I just left it alone and went on with work. I come back from lunch and it updated itself and disabled all my apps and root. The SD nethod with Nooter does NOT work. The software version showed 1.0.1. I ended up returning the Nook as its pretty useless with no root & 3rd party apps for me. I will be waiting and seeing where this all pans out as more people get the OTA. Good luck!
houseofbugs said:
So today I was at work and a little notification popped up about a software update. I just left it alone and went on with work. I come back from lunch and it updated itself and disabled all my apps and root. The SD nethod with Nooter does NOT work. The software version showed 1.0.1. I ended up returning the Nook as its pretty useless with no root & 3rd party apps for me. I will be waiting and seeing where this all pans out as more people get the OTA. Good luck!
Click to expand...
Click to collapse
I haven't gotten any notification of an update and I've been using the wifi all day. Don't see anything about an update on the Barnes and Noble site or community forums.
Not saying it doesn't exist. But if so, it's quite odd for them not to officially announce it the way they do for the original Nook firmware updates.
Keeping my WiFi off for the time being though.
This is definitely not good news. Can someone else confirm this firmware update ? B&N is not showing any updates on their website and the community forum over there is not indicating anything either. Haven't heard anything over on MobileRead.com forums either. I'd imagine that someone else would've gotten this update by now (either rooted or not) and reported it.
I'm wondering if mine just happened to get caught in a glitch in their system. Like how some Android phones got updated randomly before others. Your guess is a good as mine. I guess we will see if anyone else got hit too.
Any idea of where it saved it to? If this comes down the pipe, I'd like to pull it apart for a look at what they did
Those bastards
Maybe its time to edit the host file to prevent NC from calling home?
Sent from my SPH-D700 using XDA App
jimmyz said:
Maybe its time to edit the host file to prevent NC from calling home?
Click to expand...
Click to collapse
Do we know what domain the updates are coming from?
There are some instructions for blocking updates here:
http://forum.xda-developers.com/showthread.php?t=860480
But as the author says, they may not work (read the thread).
The best option is to flash a new rom probably and it looks like good progress is being made there.
houseofbugs: Did you get a notification before reboot? My guess would be that these updates are installed from recovery, so there may be an interim solution to delete the file from internal memory if you get a notice.
Far from perfect, but better than nothing.
So nobody else has received this update ? I Googled for any info, checked out the BN forums and another forum dedicated to the NC and nobody else has reported any kind of software update.
Just as a precaution I called my gf and had her turn off my nook and turn off wifi on hers, not looking forward to going home and finding root has been broken. Don't like the fact that it force updates itself without user interaction too, from what I gathered from the op's post. OTACerts.zip doesn't do anything on the nook?
ZeroSX said:
Just as a precaution I called my gf and had her turn off my nook and turn off wifi on hers, not looking forward to going home and finding root has been broken. Don't like the fact that it force updates itself without user interaction too, from what I gathered from the op's post. OTACerts.zip doesn't do anything on the nook?
Click to expand...
Click to collapse
If the Op didn't mess with the OTACerts.zip, then we wouldn't know. Op, did you disable updates as suggested in the thread above?
I haven't seen any "update" messages on mine. I double-checked and my NC is still running version 1.0.0. My wifi has been on for the past couple days (including all night last night) and I've seen nothing suggesting a firmware update.
Maybe I'm lucky. Looks like B&N may be planning to force a firmware update soon. It'd be nice if they gave us the option to decline it (they'll probably strip in-Store features without the most current version, but I've read here that rooting does away with in-Store features anyway).
There's another thread over in NC Android Dev where someone got a firmware update scare. Looks like a false-positive, but it's something to keep us on our toes.
Hmm no updates here either..
nothing...
I remember reading that someone else got an Update Available notification in the huge thread that started this forum. I think they said they did a system restore to factory and it allowed them to re-root it, but I don't recall if it had a version number in it. Same thing happened, nobody knew what was going on.
Regardless, we should eliminate the ability for B&N to apply automatic updates at will.
After un-rooting and resetting back to factory fresh settings, the Nook DID download an update, version 1.0.0.0. The notice appeared in the notification area.
The good news is that I am still able to root using the nooter method.
gojeda said:
After un-rooting and resetting back to factory fresh settings, the Nook DID download an update, version 1.0.0.0. The notice appeared in the notification area.
The good news is that I am still able to root using the nooter method.
Click to expand...
Click to collapse
That's not an update, it's an improper notification. It hasn't been *updated* to anything, since that's what it came with stock. It's just the nook's way of saying it's been reset to defaults.
Hopefully the update is not rolling out...
...but if it is I hope it hits my NC after this weekend when I have to take my son from the USA to the UK! Two flights and two airports without Angry Birds to keep him happy would be unpleasant.
Hmmm...
OTAcerts.zip would be my usual suggestion, for this kind of thing.
If anyone gets the nook with the update, try and grab the URL of the update via logcat.
Failing that, someone with the update might need to try things to get it rooted RageAgainstTheCage, anyone?
I don't know what you specifically need for the nook to let you sideload etc, but RageAgainstTheCage would make sense to work and get at least shell root.
I have found a great deal on a nook color but I need to know if I can deregister it so my daughter can buy from Barnes and Nobel using her own information. I plan on running a rom from an sd card, but keep the main B&N software for her. Thanks.
Really easy to deregister:
From the home screen, press the "N" button and then touch Settings. Then touch Device, then unregister and reset. I'm pretty sure that is the order. After it restores, it will walk you through the setup process again.
grindill said:
Really easy to deregister:
From the home screen, press the "N" button and then touch Settings. Then touch Device, then unregister and reset. I'm pretty sure that is the order. After it restores, it will walk you through the setup process again.
Click to expand...
Click to collapse
Nope that doesn't deregister it.
You need to have the original owner call BN and deregister it with them.
---------------------------------
Sent from my LG Optimus V using Tapatalk
That actually may work. It depends on what condition the prior owner left it in. If he didn't erase anything or password protect anything B&N wouldn't know the difference. If a password prompt pops up then he will need help from the prior owner or call B&N and do a lot of begging...
After alot of going back and forth between the 2, I went with the tablet. I feel once its unlocked (im sure it will be one day) it will be top notch. The processor and the mic did it for me.........Just looking at future capabilities once unlocked.
randyreed1971 said:
After alot of going back and forth between the 2, I went with the tablet. I feel once its unlocked (im sure it will be one day) it will be top notch. The processor and the mic did it for me.........Just looking at future capabilities once unlocked.
Click to expand...
Click to collapse
It has been already rooted. Unlocked? The jury is still out so don't buy it if you will be unhappy if they never beat the locked bootloader....
If you already have a Nook why don't you make a Nandroid Backup and just overwrite the new Nooks NAND with it?
Should work in theory, no?
EDIT: As for waiting for a Nook Tablet Unlock, if you wanted that you might have been better off with the Kindle Fire and it's open bootloader.
Hi!
I got my kindle fire hd today (german edition) and tried to root my device. So i watched the guide on *** and read several articles and forum threads to be prepared rooting the kindle fire. Ok first of all: i might have damaged the screen, although i have no clue how this happened. One of the corner led doesn't work properly anymore. The effect is like heavy clouding on led tvs.
I followed exactly the tutorial on ****. After the first step, the processor starts to heat up and the tablet slows a bit down. After the second reboot the tablet gets really hot and significantly slows down. The screen starts to flicker and the tablet needs about 10 seconds to execute a command. After a reset to factory defaults everything works like charm except the clouding. I changed the usb port, reinstalled the android sdk and even used qemuroot. Nothing works. I am going to send my kindle back and buy another one, but i wont try to root it without solving this problem. Does anyone have an idea??
/edit as a new member i can't post any urls. The first *** is reverendkyle.c*m and the second is an article on redmondpie
Sounds like you received a defective device. Send it back.
Maybe the "German Edition" versions were those that didn't make the first round of quality control checks.
soupmagnet said:
Sounds like you received a defective device. Send it back.
Maybe the "German Edition" versions were those that didn't make the first round of quality control checks.
Click to expand...
Click to collapse
I only mentioned it because my firmware version isn't 7.21 (sorry my fault) but 7.20. Never heard of it, maybe the eu version somehow differs from the us version.
noskill123 said:
I only mentioned it because my firmware version isn't 7.21 (sorry my fault) but 7.20. Never heard of it, maybe the eu version somehow differs from the us version.
Click to expand...
Click to collapse
7.20 is on the 32GB that I just received today.
soupmagnet said:
Sounds like you received a defective device. Send it back..
Click to expand...
Click to collapse
yup, it's the right advice. don't try to force any root, send the device back instead and have a new try with the next one.
The root will work for both 7.2.0 and 7.2.1, barring any anomalies with your specific device. I would use the automated root found on this forum when you try rooting next time, since it'll eliminate any possible mistakes (not saying you made any). Either way, everyone else is definitely right in saying you got a defective device. Luckily, Amazon's pretty good about replacements when you're under warranty. My own device's CPU was running so hot, it smelled like things were melting. Got it replaced with no fuss, and no extra charges.
noskill123 said:
Hi!
I got my kindle fire hd today (german edition) and tried to root my device. So i watched the guide on *** and read several articles and forum threads to be prepared rooting the kindle fire. Ok first of all: i might have damaged the screen, although i have no clue how this happened. One of the corner led doesn't work properly anymore. The effect is like heavy clouding on led tvs.
I followed exactly the tutorial on ****. After the first step, the processor starts to heat up and the tablet slows a bit down. After the second reboot the tablet gets really hot and significantly slows down. The screen starts to flicker and the tablet needs about 10 seconds to execute a command. After a reset to factory defaults everything works like charm except the clouding. I changed the usb port, reinstalled the android sdk and even used qemuroot. Nothing works. I am going to send my kindle back and buy another one, but i wont try to root it without solving this problem. Does anyone have an idea??
/edit as a new member i can't post any urls. The first *** is reverendkyle.c*m and the second is an article on redmondpie
Click to expand...
Click to collapse
That’s exactly what happen to me about 10 days ago my KFHD
Get hot and speed is unbelievable slow down but I do manage to reset to factory setting
http://forum.xda-developers.com/showthread.php?p=32866304#post32866304
But finally I manage to root my KFHD and switch off upgrade option because I don’t want
The same problem occurs to me again.
My mistake at the first time is I mix up the method using manually method by reverendkjr
And on half way using script giving by sparkym3, so on the second attempt I only use
manually method by reverendkjr doing exactly what he is done and I get my KFHD rooted
I hope this will help you
NB
Even I uncheck automatic update they still updated my KFHD now I am with 7.21
and became unroot yes will start allover again.:fingers-crossed:
Dear members of XDA Forums:
So, a few days ago I decided to purchase an e-reader, because there are a lot of books in their original language that are almost impossible to get here in Argentina in physical format. I looked in a few stores, and the Kindle Fire HD 7 seemed fine. It had android, wifi, and some cool random stuff. Well, I purchased it, and was really glad after realizing that what I had in my hands could be turned into a fully functional (and pretty powerful) tablet, not just a reader. So I rooted it, installed a custom launcher, that kind of stuff, and everything went well.
I've been trying to investigate even further, but there are a few particular points to which I found no answer on the forums:
- Currently I'm using the latest version of the firmware (I think it was 7.4.1), and it seems pretty obvious after a quick look at the forums that no wallpaper can be set in that version because Amazon disabled them with a switch in the framework or something like that, and it can only be accesed by decompiling or using the custom script created by mr. stunts513; both of which seem too dangerous for me at this moment (I have absolutely no way of getting a factory cable if something goes wrong, and this thing was worth 2/5 of my monthly salary...)
Was there any update regarding this, or it remains in the same situation?
- At some point before rooting, I'm sure I updated my Kindle. But I've only had it for a few days, so a data wipe doesn't scare me yet. What will happen if I do a total factory restore? I mean, without using any app, just hitting the button in the settings menu. I guess it will unroot and all my apps and personal stuff will be erased, but what about the firmware? Will it remain in the latest I had before restoring (7.4.1) or will it go back to the one it had when I took it from the box?
- I've read several ways to block OTA updates, but there seem to be mixed sollutions for the K7 and the K8'9 in the same threads. Regarding my 7, I only changed the name of the .zip file that controls it (can't remember it's name now, it was in system/etc/security, I think). Will that be enough for a 7?
Thanks in advance, and best regards!
P.S.
Mr. stunts513, please do not take my commentary as a way to despise your work; quite the contrary, I'm grateful and would try it without a doubt if I was sure I could unbrick my Kindle if something goes wrong. But there is no way to be 100% sure, so for now I'd rather wait with a black desktop.
Ah No problem I completely understand, if you feel safe trying to install 2nd boot loader and twrp you won't need a fastboot cable if it bricks, but that has some risks of its own. Factory reset I think pretty much just wipes the data folder, maybe some of the system folder, so it doesn't restore the is to a previous version, least as far as I have ever heard. I can't really speak for everyone but I think renaming the ota certs zip file does the trick but I have heard mixed reviews on whether it does as of late or not, I'd wait for someone else to confirm that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hi all,
Any easy / straightforward way to roll back to KK? I've tried my best to like lollipop, but ugh
I'd like to get back to KK, with root access and a debloat of sorts but maintaining DRM keys for camera functionality... anyone have a straightforward guide?
Could care less about google apps, but I do use the maps navigation quite alot... but hangouts, google now etc just irritates me.. is this possible?
Im all stock, never modded
Regards
I'm not an expert by any means, but can show you the guide I used. I was really glad I did it - it's involved, but totally worth it, and increased my Android ability/confidence with the Z3C. Losing the DRM keys, uncertainties with the bootloader etc. still make me nervous but my phone is currently the best it's ever been. Am on stock but rooted and partially debloated.
I'm on my phone at the moment but tomorrow at my desk I'll pull up the link for you.
schnidex said:
I'm not an expert by any means, but can show you the guide I used. I was really glad I did it - it's involved, but totally worth it, and increased my Android ability/confidence with the Z3C. Losing the DRM keys, uncertainties with the bootloader etc. still make me nervous but my phone is currently the best it's ever been. Am on stock but rooted and partially debloated.
I'm on my phone at the moment but tomorrow at my desk I'll pull up the link for you.
Click to expand...
Click to collapse
That would be most awesome.. thanks!
Gomezie said:
That would be most awesome.. thanks!
Click to expand...
Click to collapse
So this is the guide I used:
How-to: root, keep and backup DRM keys, etc. [KitKat/Lollipops]
..and I went from stock Lollipop I'd upgraded OTA, down to a rooted KK. For reference, from that guide, I'm a SIM free UK user so downloaded that .77 firmware and then built my own pre-rooted image when it came to step 26. The guide is, in only a few places, a little bit vague but it it's easy to figure out yourself once you're halfway through the process and actually doing it all.
While the process was involved, I did not find it challenging or frightening. Read it through several times in advance before attempting it, and download all the files you'll need ahead of time to save waiting around once you're actually rooting. Obviously back up all your valuable data before starting, just in case. If you come across any errors, make sure you have ADB debugging enabled, allow mock locations (and I also checked allow unknown sources as well). Also make sure you have all the relevant drivers. These are the most common things that trip people up when rooting on any device, in my experience so far.
Once you've successfully completed the process, I then installed a tool called Debloater. This is very easy to use, and allows you to tick off packages that you want to block, but you can also remove them entirely. What I'm doing right now is running for a week or two with the packages blocked that I'll probably want to remove, and once I'm satisfied everything is safe, I'll then actually remove them down the line.
There's no definitive list of what each package is or does though, so I removed the ones I definitely wanted to get rid of that I knew were obvious plus a few others that I took a safe guess at, or used other a few people's posts and cross-referenced them. Be careful though, some are essential to keep! I have those links bookmarked on my home PC and can dig them out for you once you're at that stage! Or alternatively, compile a list of what I've blocked myself. But I guess some of the fun is customising it to your own needs anyway, and learning along the way
Any questions, please let me know. I'm far from an expert but these boards don't seem to be too vibrant for our phones compared to other devices, probably because it took so long to get us to the point of being able to do this. Still, it's the best device I've ever owned and I'm very, very happy with where it is now thanks to the hard work of those who made root etc. possible.
This is awesome, ive got myself rooted and everything now.. will go ahead and deblot
I also concur regarding the phone.. easily my best too!
Thanks again