Develop Bugs

[Q] Son in trouble with pissed off dad about bricked KF!

OK, I have ready many posts and guides an am completely lost. This is my 12 year old sons Kindle Fire that he decided to "root". I am fairly computer savvy but this thing has got me baffled. He used "superoneclick" and now it tries to boot and stops at the kindle fire boot screen and goes no further. Any help on pointing me in the right direction would be appreciated. I do know this. The hard reset obviously does not work because I have tried that at least 100 times. My pc currently does not allow me to access it as a drive although it does show up. It sounds like a bootloader" problem? Again, please give me hand before I kill my son after telling him in advance not to do this.
Thanks
Forrest

Try and see if you can get KindleFireUtility to recognize your Kindle Fire
http://forum.xda-developers.com/showthread.php?t=1399889

Veeman, thanks I will try that and report back.

do you have fastboot?
type
fastboot devices in terminal and see if it returns your kindle number.
you are stuck in fastbootmode.
kfu will sort it out for you.
some more info would be of help.
what operating system on pc?
has your son got fastboot installed in sdk/tools or sdk/platform tools?
what stage was he at in the rooting process?
don't worry, has far as i know there is only one hardbrick issue at the moment, and that has to do with one type of recovery and doing a wipe/restore.
Sent from my Galaxy Nexus using xda premium

I understand your concern, and I don't mean to be out of line and tell you how to be a parent but...
If you're really computer savvy, you know that on the way there, you fudged some settings that made the computer unstable or unbootable. You installed programs, printers, a different way and had it not quite work out because you didn't follow directions.
My point is this: A 12 year rooting his kindle shows a level of intellectual curiosity that I think should be commended and encouraged. Any electrician, programmer, repair guy, anyone who does this kind of stuff will tell you; they learned the most when they screwed up.
What I would do? Work together with him to fix it. Show him what and how you're doing it, how you're asking for help (and that that's okay) and where to find what he needs to fix it.
You're not hard bricked, at least its unlikely, you're likely just stuck in fastboot which is not a big deal at all.
Just take it with a grain of salt. I know to when a kid breaks something it's "There goes X dollars" But sometimes, you have to break some eggs.
Good luck though.

Well, you came to the right place for guidance! I'm sure a forum search for "stuck in fastboot" would lead you and your son in the right direction. Unless there is a better way I'm not aware of, you will need to get adb up and running on a PC (which is most of the work). Then you will be able to get the kf out of fastboot by issuing commands from your computer's terminal/command prompt
But....
I think you should let your son do it... Especially if he plans on keeping his fire rooted. "Rooting" allows users to make changes to critical system files... On one hand this is really cool because it will allow your son to load custom ROMs (operating systems) and take full advantage of the kf's hardware....But, it will also make it very easy to royally screw things up.
So, if that's something he's interested in he needs to learn how to troubleshoot and fix things himself. You definitely came to the right place though... xda is a very sweet resource.
Goodluck!

http://forum.xda-developers.com/showthread.php?t=1668159

Update
Ok folks, thanks for all the input so far. We (my son and I) have worked on it and found KFU useful. We installed the latest update and it is now working. However, TWRP will not go away. We need to take this in for service so I need to reset everything. We have tried the wipe and install of the update several times it restarts with the blue kindle fire logo with the option for recovery. How do we get rid of this?

Firemancfd said:
Ok folks, thanks for all the input so far. We (my son and I) have worked on it and found KFU useful. We installed the latest update and it is now working. However, TWRP will not go away. We need to take this in for service so I need to reset everything. We have tried the wipe and install of the update several times it restarts with the blue kindle fire logo with the option for recovery. How do we get rid of this?
Click to expand...
Click to collapse
1. Download Kindle Fire Software Update Version 6.3.1
2. Rename the file to update.zip
3. Get in to TWRP and mount USB drive
4. Copy update.zip to Kindle Fire
5. Unmount USB drive
6. Do factory reset, then wipe system cache, and dalvik cache
7. Flash the update.zip

Tera Tike, thanks for the answer. I have tried that multiple times and the twrp blue kindle fire with boot options keeps coming back.

Felnarion said:
My point is this: A 12 year rooting his kindle shows a level of intellectual curiosity that I think should be commended and encouraged. Any electrician, programmer, repair guy, anyone who does this kind of stuff will tell you; they learned the most when they screwed up.
Click to expand...
Click to collapse
True, but I think it's a tad different when you spend a couple of hundred dollars on something and specifically asked the lad not to do this one thing.

Firemancfd said:
Tera Tike, thanks for the answer. I have tried that multiple times and the twrp blue kindle fire with boot options keeps coming back.
Click to expand...
Click to collapse
Try letting it sit while it "bootloops."
Might sound strange but I've had this exact same thing happen recently after a fresh install, and it loaded up back to normal after a handful of loops.

sbeddoesdesign, you are right i was upset not about the act but that he done it after i told him not to, then he lied to me about doing it. Either way, I have calmed down about it now and he is helping and participating. We are learning a lot together and its good dad/son time.
anomalya, i tried that and let it sit for an hour and no change.

FIXED
Thanks to all who helped. We finally got it to work correctly. Everyone was a big help and we appreciate everything.

I am glad that you got it working, but I am posting this for anyone else that can't seem to read or do a simple search. If you have the KFU all you need to do is have it running and restart your KF while connected the computer, and send the normal boot cmd when it first connects for those few seconds, and you are good to go, but seeing how too many people are to stupid to understand this, I believe that everyone should stop responding to them!!! We see this too often and everyone gives them this long work around...

kinfauns said:
3) Not all "stuck on bootlogo" problems are fixable with the KFU remedy you provided.
Click to expand...
Click to collapse
Are -any- such problems fixable with KFU? :silly:

Yeah, because 99% of the problems can be fixed by simply sending the command to start in normal boot you are offended and want to try and say I was saying something about you? If you are offended, then yu might be one of the people that can't seem to learn from the past!!!
---------- Post added at 06:46 PM ---------- Previous post was at 06:43 PM ----------
BTW, seeing how most of the issues that fall under this, have been fixed in the exact way I described, it adds to my credit!

Firemancfd said:
Tera Tike, thanks for the answer. I have tried that multiple times and the twrp blue kindle fire with boot options keeps coming back.
Click to expand...
Click to collapse
Blue Kindle Fire logo is FFF1.4a

Thread cleaned up and closed.

Is it safe to root Kindle Fire

Hey everyone. I am ready to root my kindle fire and (if its a good idea) put a custom rom on it. I wanted to know what risks i take with using KFU and if its a good idea to use a custom rom instead of the stock rom rooted. I like some of the jelly bean ROMs, but I am ok with anything. I love customizing my devices, this is my first Android device. I don't really like the stock rom at all. I just wanted to make sure KFU is safe and I don't run a risk of bricking my Kindle.
Thanks, x10knight

x10knight said:
Hey everyone. I am ready to root my kindle fire and (if its a good idea) put a custom rom on it. I wanted to know what risks i take with using KFU and if its a good idea to use a custom rom instead of the stock rom rooted. I like some of the jelly bean ROMs, but I am ok with anything. I love customizing my devices, this is my first Android device. I don't really like the stock rom at all. I just wanted to make sure KFU is safe and I don't run a risk of bricking my Kindle.
Thanks, x10knight
Click to expand...
Click to collapse
Well, When I rooted my kindle it was very simple to root and I had absolutely no issues. I am not sure if amazon has been up to no good and did something to make fastboot more difficult to enter/use because a lot of people lately have been getting stuck in fastboot and needing help getting their kindle's "unbricked". If you would prefer using an AOSP ROM I would recommend trying one of the ICS roms first just because they are a little more stable and battery life is much more reliable. That or you could try Modaco to ease yourself into the rooting/ROMing game, it is rooted stock + google play. The rewards of rooting your device outweigh the risk but you just need to be patient. If your KFU seems like it is stuck, give it a few more minutes before you unplug your device or turn it off. Both of these leave you vulnerable to soft bricking your device and while it can be an easy fix, it is a headache that could be avoided. I am not completely up to date with it all but I would be happy to help if you need any advice or run into any difficulties. Best of luck!

x10knight said:
Hey everyone. I am ready to root my kindle fire and (if its a good idea) put a custom rom on it. I wanted to know what risks i take with using KFU and if its a good idea to use a custom rom instead of the stock rom rooted. I like some of the jelly bean ROMs, but I am ok with anything. I love customizing my devices, this is my first Android device. I don't really like the stock rom at all. I just wanted to make sure KFU is safe and I don't run a risk of bricking my Kindle.
Thanks, x10knight
Click to expand...
Click to collapse
There always is a risk of bricking a device when Rooting /Flashing. At lease with my experience with the fire the risk is no higher than any other Android based device. Flashing a Rom mostly revolves around if you are a Amazon Prime member and use there services like Video Steaming and Lending Books from Amazon I would recommend using a launcher like ADW Launcher but if none of that apply to you I will recommend This
http://forum.xda-developers.com/showthread.php?t=1766829
Edit I have not use the above ROM mostly because I use the Above services but if I did not use them this will be the one I would have chosen

Ok, I tried rooting twice. Everytime it says something about cannot download recovery, and i have to force the kindle out of fastboot.

x10knight said:
Ok, I tried rooting twice. Everytime it says something about cannot download recovery, and i have to force the kindle out of fastboot.
Click to expand...
Click to collapse
Can you give us a description of what you were doing before and until you got said error and any thing you may have tried to fix it.

I didn't try to fix it. That is the problem. It tries to download twrp and fails. Then I have to mess with it for windows to find it and put it to bootmode 4000.

The twrp download is broken with kfu in order to put twrp on your device it will have to be fastboot flashed...

Thepooch said:
The twrp download is broken with kfu in order to put twrp on your device it will have to be fastboot flashed...
Click to expand...
Click to collapse
couldn't you just download twrp and place the .bin into the twrp folder in KFU so that they don't have to mess around with the fastboot commands themselves?

I did but since goo.im was down it decided to delete twrp instead of using it and it was twrp 2.2 the correct file hopefully soon it will be resolved... someone stated that the server is back up but I can't test it till much later tonight...

popa_qwerty said:
There always is a risk of bricking a device when Rooting /Flashing. At lease with my experience with the fire the risk is no higher than any other Android based device. Flashing a Rom mostly revolves around if you are a Amazon Prime member and use there services like Video Steaming and Lending Books from Amazon I would recommend using a launcher like ADW Launcher but if none of that apply to you I will recommend This
http://forum.xda-developers.com/showthread.php?t=1766829
Edit I have not use the above ROM mostly because I use the Above services but if I did not use them this will be the one I would have chosen
Click to expand...
Click to collapse
i use firefirefire dualboot and i have jellybean and MoDaCo stock as the alternative and on the modaco i have ota rootkeeper so i can use prime instant videos and get lending library books! but i use the jellybean rom as my normal rom

Thepooch said:
I did but since goo.im was down it decided to delete twrp instead of using it and it was twrp 2.2 the correct file hopefully soon it will be resolved... someone stated that the server is back up but I can't test it till much later tonight...
Click to expand...
Click to collapse
I can host twrp on my mediafire account until things get back up and running.
just place the TWRP.img file in the folder /recovery in the KFU directory then just run the utility and it should just go to the part where it flashes the file to your kindle. Is it downloading FFF fine?
http://www.mediafire.com/?f3sr33214229pr2

Ok so we download that file and then we make a folder called " recovery" inside the Kfu folder? . and just run the utility again and do the perm root?

illusiiOnz said:
Ok so we download that file and then we make a folder called " recovery" inside the Kfu folder? . and just run the utility again and do the perm root?
Click to expand...
Click to collapse
There should be twrp.img file in KFU/recovery directory
Remember that if you somehow break the system while rooting(rather hard) the FFF bootloader can save you ass because it can switch Kindle in fastboot mode.

[Q] kindle fire unrecognized in windows. adb does not work. No SO. bricked

hello.
I write this post because right now I'm desperate. my kinde fire was rooted and works great. I wanted to install an unofficial ROM and there came all problems.
first of all I want to say that I resort to this message because I've tried everything, but I did manage to save my device.
My Kindle was rooted and TWRP works well. I inadvertently left the device without an operating system. I forgot to put a rom after you wipe. After this, when the device booted, first came out the white and orange logo, then white and blue recovery and eventually returned to the first logo.
First I tried to recover it with the original firmware. I could not access the device via the file browser windows, so I copied the. zip with adb push. after several attempts I went to plan B, because I always got the same "error 7", so I tried to install the cyanogen rom, but I had the same fate.
After that, I was reading about fastboot, so I downloaded kindle fire utility. I think something went here even worse, because now TWRP gone.
I finally discovered unbrick kindle utility, but now my pc does not recognize the device. drivers are installed and kindle fire utility says "adb: online", but I can not access the device.
I searched a lot of information, but I think I am increasingly far from the solution, so I decided to write this post.
anyone can help me to recover the kindle? I'm desperate now. I'd like to have everything as before, I do not lose the root
thanks!!!

Same problem
Hi! i alredy have the same issue. I tried to change the room but something was wrong... I tried to get back and i used kindle fire utility too. I think it was the problem because now i can not turn on. did you find the way to fix it!??????? help i am desperate as you were...:crying:

KFU IS FOR KF1
(that is all)

I know...
fmkilo said:
KFU IS FOR KF1
(that is all)
Click to expand...
Click to collapse
Yes i know that was a mistake... the issue here is to fix it. Some good ideas could be great!!!

i.robert, i'm follow in the same problem.
fmkilo, can you help solve it?

:\
"Onemelia" says that probably ours kindle are ruined... i just know that FireFireFire.bin was the mistake. However maybe we can get in to the sd memory for build everything from base. Only if the mother board is not ruined too...
http://forum.xda-developers.com/showthread.php?t=2010353&page=2

fmkilo said:
KFU IS FOR KF1
(that is all)
Click to expand...
Click to collapse
This forum is full of people doing the same thing. Why do people keep using tools that will brick their device, even though there are other posts saying it will happen.
Frustrating.
Sent from my Amazon Kindle Fire2 using Tapatalk HD

chronicfathead said:
This forum is full of people doing the same thing. Why do people keep using tools that will brick their device, even though there are other posts saying it will happen.
Frustrating.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
chronicfathead, the problem has no solution? is there any way to recover the bootloader?

Finally, I got in touch with Amazon. I explained my problem and they will send me a new one because it was under warranty.

Finally, I got in touch with Amazon. I explained my problem and they will send me a new one because it was under warranty .
i will recieve it tomorrow
thanks very much for your help
I hope not to have problems like this in the future
.

dewars14 said:
chronicfathead, the problem has no solution? is there any way to recover the bootloader?
Click to expand...
Click to collapse
Hi. I was just commenting that a lot of people are rushing into doing things without reading, or even checking what model they have. Admittedly Amazon hasn't made it easy by advertising it as the Kindle Fire 2. All the recent posts in this section of the forum are from people bricking their devices, mainly because they did something wrong.
I don't know how the situation can be changed, apart from building some checks into the KF1 rooting/modding tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD

chronicfathead said:
Hi. I was just commenting that a lot of people are rushing into doing things without reading, or even checking what model they have. Admittedly Amazon hasn't made it easy by advertising it as the Kindle Fire 2. All the recent posts in this section of the forum are from people bricking their devices, mainly because they did something wrong.
I don't know how the situation can be changed, apart from building some checks into the KF1 rooting/modding tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
Ok. I have already received my new kindle fire 2. I was lucky it was under warranty. Now I have to return the old and noticing more if I decide to put a new rom.
thanks anyway for your help

[Q&A] [RECOVERY] CWM Recovery 6.0.5.1.2

Q&A for [RECOVERY] CWM Recovery 6.0.5.1.2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Full backup of one AFTV and restore on another
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
modstore said:
I'm not sure if anyone has tried backing up one Fire TV and restoring to another, but I just tried it, and all seems good.
Doing the restore though, changed the registered account to that of the backup. So I'm not sure if it would have been registered properly, probably not. But I changed it to the account I wanted it registered too, and all seems good now.
Click to expand...
Click to collapse
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.

eville84 said:
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
Click to expand...
Click to collapse
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.

nyder said:
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
Click to expand...
Click to collapse
There might be a way to make it trigger the initial Registration page after doing a restore of a clone. I'll add it to my list and maybe come up with a special update.zip that will make it happen.

So if you have a FTV set up with xbmc etc you can make a direct copy of it into a stock FTV, thus cloning it as said above?

I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader

hellot1M said:
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
Click to expand...
Click to collapse
You need root first. What fw are you on? If it's a rootable version, do that first and then follow the guides for updating here.

Yea figured it out. I'm on 1.3.0 this sucks. I'm trying to sell my amazon box to get a nexus player. Amazon has no idea how to run a home media center.

Thanks!

Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk

patt2k said:
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS

0p3nsrc said:
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
Click to expand...
Click to collapse
Guide from AFTVNEWS.
I got recovery to work everything was fine I could reboot from recovery back to recovery again (CWM) but after I did factory reset in CWM it gets stuck on amazon logo.
The reason I did factory reset was because of Error.7 in CWM I had that few times when flashing different roms on different phones/tablets
sometimes getting older cwm or simply factory reset would help.
So now it gets stuck on Amazon logo the keyboard trick to get back into CWM does not work anymore.
Anything else I can try before I call up amazon hoping they replace it ?

I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS

0p3nsrc said:
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
Click to expand...
Click to collapse
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr

patt2k said:
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
Click to expand...
Click to collapse
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS

0p3nsrc said:
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
Click to expand...
Click to collapse
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.

patt2k said:
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
Click to expand...
Click to collapse
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS

0p3nsrc said:
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
Click to expand...
Click to collapse
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!

patt2k said:
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
Click to expand...
Click to collapse
Sorry I couldn't be of more help :/ the issue you'll probably see is that unlocking the bootloader voids any warranty with amazon.. So I'm not sure what amazon may or may not do for you.
Sent from my TARDIS

About the possible Lollipop ROM for FireTV,is there a way to get the latest qualcomm Adreno 320 drivers like [email protected] from another device for flashing in proper FTV directories since it is meant for Lollipop?
I am hoping for the fix for Dolphin to be runnable and Reicast to no longer cause reboots,as well as better performance for things like Mupen64Plus AE.

KINDLE FIREHD 8.9. TWRP unable to read/load rom error Help Please

Hi guys n Gals How you all doing? Staying safe i hope!! Im posting this incase it is of any use to anyone who happens to stumble upon an old tablet as i did, But is absolutely bamboozled with what to do next.
Well then i had been looking for help on this issue with regard to Kindle Jem and done my fair share of reading before signing up here.
I am right out of the wrapper and wet behind the ears with Kindles and the like(1st time rooting anything at all) however i managed to install TWRP 2.8.6.0 on su rooted kindle using the bin4ry method.
I followed step by step a tutorial on Youtube named " KindleFireHD89 to pure android"
1. At first i was getting read/load errors:
when attempting to flash cm10.1 cm11/12 through adb sideload i was getting the error message "unable to read cm 11/12" or "unable to load cm11/12" each time i try to flash the rom.
So I done some research on XDA and found a thread to do with the \LARGEADDRESS issue , so downloaded the program to use more than 2GB ram for the flash process, all to no avail. (THIS WAS ABSOLUTELY NO USE AT ALL)
I soon figured i was copying and pasting the commands for flash/fastboot wrong ( i was forgetting to add .img to the name of the image files i was pasting into the command prompt to flash lol)
2. I done a bit of reading around and saw that most , if not all the files were severely obsolete (like the Jem) so i searched around and first upgraded to TWRP 3.0.0.2 from 2.8.6.0 which i feel made a big difference if not just for a smoother gui alone.
3. As my determination and curiosity got the better of me i began replacing the roms also , flashing newer ones each time in this order:
cm 10.1 (success)
cm 11(success)
cm 12.1 (success)
And finally onto Lineage OS 14.1 along with GApps 7.1 Pico where i remain , however i am unable to fix the bluetooth issue as i dont know the commands/ paths or method to alter the LTE file replacement. (any help with this would be great guys or girls (i know Ladye made a fix i think) i just dont know how to go about editing these files.
I got into the menu brand new , though weirdly it wasnt by the volume up button, it was by turning on/off about 5 times and then holding the POWER button in and finally the TWRP Recovery screen would popup.
### edited### i know this is an old kiindle hence why there is no replies .....
####23rd May 2020 EDITED YET AGAIN ##### So i wondered whether there was a recent newish kinda Rom for the JEM after managing to flash (with great difficulty and beginners syndrome) custom rom in TWRP 3.0.0.2.
As i said earlier this was a kindle that was found and when i got it in out the rain and dried off with the hairdrier treatment , was amazed it still worked. So i figured it was a tough mofo and deserved to live outwith the bin since he made it this far.
Anyway when i checked it out the firehd 8.9 was blacklisted ((((Which i am assuming will mean i at least dont need to worry about disabling OTA updates??????))))
So bottom line and after all the fuss above trying to root etc i got 14.1 lineage os without the bluetooth but ill figure that out soon.
For anyone out there this post may help if you can be bothered to read through it haha.
###Last but not least I would like to thank all the guys n gals who make these mods possible and xda themselves for not binning these old posts for noobs like myself . Respect people . thanks again man ###