Develop Bugs

Toolkit may be coming soon to you guys!

Looking to bring you guys into the action. I'm gonna purchase a kindle fire online on Monday and then make a toolkit on it.
Just a few questions.
You guys use Fastboot commands or no?
Ex: Fastboot flash recovery recovery.img, Fastboot flash boot boot.img
A personal question myself, since there is no removable battery, is there a button trick to shut it off if it freezes?
I have to put all this into consideration when I make the toolkit.
Thanks!
If you don't know what a toolkit is, look in my signature. Just don't look at the Sensation or MT4GS since I still have to update their UIs

Yep you just hold the power button if it freezes and itll shutoff pretty much no matter what. Also please do bring tool kit here

HaiKaiDo said:
Yep you just hold the power button if it freezes and itll shutoff pretty much no matter what. Also please do bring tool kit here
Click to expand...
Click to collapse
Thanks for the reply! What show I know about the device? Anything in particular?
Why is it necessary to flash a different bootloader? (I should be reading on it now, but I'll get a better analysis on it when I order it)
The toolkit is gonna basically be like this but with a graphical user interface
http://forum.xda-developers.com/showthread.php?t=1399889
Will add other options as well, just gotta see how this works since it is different than HTC phones.

bump
help me out so I can help you guys out as well!

Theres already a toolkit

trter10 said:
Theres already a toolkit
Click to expand...
Click to collapse
Who said another one won't hurt? It's good to have choices. Would you rather use one ROM or have choices to choose from?
Sent from my HTC_Amaze_4G using Tapatalk 2

Drivers are a big issue for the tool kit we do have.
Sent from my Kindle Fire using Tapatalk 2

jacewt said:
Drivers are a big issue for the tool kit we do have.
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Can you explain what you mean?
Sent from my HTC_Amaze_4G using Tapatalk 2

jacewt said:
Drivers are a big issue for the tool kit we do have.
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
This is true.
Sent from my ADR6400L using Tapatalk 2

What's wrong with the drivers?
Sent from my HTC_Amaze_4G using Tapatalk 2

hasoon2000 said:
What's wrong with the drivers?
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Lets just say If you can get it to connect through adb you are a genius.
Sent from my ADR6400L using Tapatalk 2

the device requires different drivers for adb/fastboot.
once u get adb working, and reboot into fastboot, it usually doesn't get seen by the PC. its one of the biggest issues and lots of people have them when rooting.
Sent from my HTC Glacier using xda premium

I used hasoons toolkit with my amaze and gotta say thanks.hasoon andcant wwait to see what you do fornthe kindle users too.
sent from my kindle fire running gedeROM

Fastboot works real well with the fire. Its a nice device to use with adb and fastboot.
The drivers are really finicky and once you get them set up....don't change anything with regard to your computer as far as your kindle fire development setup. The trick for me (windows 8) is to force disable windows driver signing protocol and to use the windows device manager and USB deview to get the kindle fire drivers established. I would not start off with the kindle fire utility kit or put that in the same directory as your kindle fire development file.
Its a great device and I think a new toolkit does no harm and promotes further development. I strongly advise using TWRP recovery and not clockwork mod as there's some unresolved issues with damaged emmc partitions causing brickedness. (See hashcodes thread with regard to cwm recovery for the 3.0 kernel)
That 3.0 kernel (by Hashcode) pumped massive growth into this device as we did not have hardware acceleration prior to that (outside of the Amazon forked build.)
Now I've no idea what a toolkit is but I'll help test drive anyhow. What's the other toolkit? Vashypoors KFU? That is a nice setup but IMHO people ought to be able to handle ADB and fastboot business before using that KFU or any other toolkit.
You asked about the bootloader? Great write up about why the stock image was replaced by FIREFIREFIRE by Pokey9000 I'll try to find it later but it should be one if the stickied threads here. You can't do a thing with the stock bootloader.
Edit --- I now know what you mean by a toolkit... I didnt realize you made one for the One-S. (nice work, that!!)
Now Im going to get a bit straightforward, dont get me wrong --- these toolkits are great, but they are akin to giving just about anyone on the street a loaded gun... toolkits give an absolute noob or a person who has absolutely no idea whatsoever what they are doing a false sense of security and they believe they have full control of the device where they clearly do not. You effectively give people the easy mind-numbingly-easy opportunity to change something on their device and then they have no idea what its doing or how to get out of any predicament. Thankfully, there are things called "Drivers-Education" and then a "Test" prior to all 16 year olds getting permission to operate motor vehicles!
IT WOULD be cool if you made your toolkit lockable which is unlocked only by the user successfully performing various executions of simple adb and fastboot activities.... i use these toolkits only when my keyboard is broke, or my hands are broke or otherwise occupied by children.
Sent from my HTC One S using xda premium

If you use the KFU on your kindle to root everything should go well. You may encounter problems if you do it manually at least I did a little a bit others my have not. For the driver issue the KFU comes with drivers use them instead when your computer asks for the location. I wish you luck with the toolkit the more the merrier
Sent from my Galaxy Nexus using xda premium

While I'm a huge proponent of the manual method of rooting/modifying the Kindle Fire, I don't think having programs like the KFU is a major problem. The only way Kindle Fire development is going to grow is with more users, even if those users are noobs looking to take the easy way out. The more popular the device becomes, the more likely experienced developers will jump on board.
There really isn't much you can do about people who refuse to follow directions or educate themselves before getting into trouble, other than complaining about it and posting stupid threads like "This is what you people sound like". It all comes with the territory, especially in a world where a mentally retarded two year old can jailbreak an iPhone and feel like a genius afterwards.
As long as people are still searching for the "any" key, I'll still be mumbling TSTFO and yelling HLMGIFY until my face turns blue but I'll be more than willing to put up with it to see this community grow and get some awesome development in the process. So yes, I say bring on the Toolkit, the worst that could happen is I get more fuel for my sick sense of humor.

build something that restores a kindle in an sbf like process to stock original correctly partitioned then you might have a tool that could rescue a whole bunch of people who have broken systems, bootloaders,recoveries and completly wacked out partitions then you will have a tool that will get used to death.

Thepooch said:
build something that restores a kindle in an sbf like process to stock original correctly partitioned then you might have a tool that could rescue a whole bunch of people who have broken systems, bootloaders,recoveries and completly wacked out partitions then you will have a tool that will get used to death.
Click to expand...
Click to collapse
I just have to learn more about it first before I get into doing that unless there is a fix that I can look at.
soupmagnet said:
While I'm a huge proponent of the manual method of rooting/modifying the Kindle Fire, I don't think having programs like the KFU is a major problem. The only way Kindle Fire development is going to grow is with more users, even if those users are noobs looking to take the easy way out. The more popular the device becomes, the more likely experienced developers will jump on board.
There really isn't much you can do about people who refuse to follow directions or educate themselves before getting into trouble, other than complaining about it and posting stupid threads like "This is what you people sound like". It all comes with the territory, especially in a world where a mentally retarded two year old can jailbreak an iPhone and feel like a genius afterwards.
As long as people are still searching for the "any" key, I'll still be mumbling TSTFO and yelling HLMGIFY until my face turns blue but I'll be more than willing to put up with it to see this community grow and get some awesome development in the process. So yes, I say bring on the Toolkit, the worst that could happen is I get more fuel for my sick sense of humor.
Click to expand...
Click to collapse
First, I loved the link to the humor thread. I started laughing because we always deal with that!
Second, I agree. Manual method is the way to go for new users to learn in case anything happens. I just hate doing commands manually all the time so I automate them to make it easier on me.
I would need you guys to help out since you guys have way more experience than me with the Kindle (I'm gonna order it soon). As long as you guys don't mind, then this will definitely come!
Kheladu said:
If you use the KFU on your kindle to root everything should go well. You may encounter problems if you do it manually at least I did a little a bit others my have not. For the driver issue the KFU comes with drivers use them instead when your computer asks for the location. I wish you luck with the toolkit the more the merrier
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thank you sir! I'll see if I can get the drivers issue fixed.
androidcues said:
Fastboot works real well with the fire. Its a nice device to use with adb and fastboot.
The drivers are really finicky and once you get them set up....don't change anything with regard to your computer as far as your kindle fire development setup. The trick for me (windows 8) is to force disable windows driver signing protocol and to use the windows device manager and USB deview to get the kindle fire drivers established. I would not start off with the kindle fire utility kit or put that in the same directory as your kindle fire development file.
Its a great device and I think a new toolkit does no harm and promotes further development. I strongly advise using TWRP recovery and not clockwork mod as there's some unresolved issues with damaged emmc partitions causing brickedness. (See hashcodes thread with regard to cwm recovery for the 3.0 kernel)
That 3.0 kernel (by Hashcode) pumped massive growth into this device as we did not have hardware acceleration prior to that (outside of the Amazon forked build.)
Now I've no idea what a toolkit is but I'll help test drive anyhow. What's the other toolkit? Vashypoors KFU? That is a nice setup but IMHO people ought to be able to handle ADB and fastboot business before using that KFU or any other toolkit.
You asked about the bootloader? Great write up about why the stock image was replaced by FIREFIREFIRE by Pokey9000 I'll try to find it later but it should be one if the stickied threads here. You can't do a thing with the stock bootloader.
Edit --- I now know what you mean by a toolkit... I didnt realize you made one for the One-S. (nice work, that!!)
Now Im going to get a bit straightforward, dont get me wrong --- these toolkits are great, but they are akin to giving just about anyone on the street a loaded gun... toolkits give an absolute noob or a person who has absolutely no idea whatsoever what they are doing a false sense of security and they believe they have full control of the device where they clearly do not. You effectively give people the easy mind-numbingly-easy opportunity to change something on their device and then they have no idea what its doing or how to get out of any predicament. Thankfully, there are things called "Drivers-Education" and then a "Test" prior to all 16 year olds getting permission to operate motor vehicles!
IT WOULD be cool if you made your toolkit lockable which is unlocked only by the user successfully performing various executions of simple adb and fastboot activities.... i use these toolkits only when my keyboard is broke, or my hands are broke or otherwise occupied by children.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
No offense taken! Positive criticism at its finest! lol. You really gave me a lot of info and helped out. As I said earlier, I'm new to this. (Still didn't order the kindle yet) so I'm trying to gather all the knowledge so I have a heads up.
I will user TWRP and not add CWM since we don't want anyone to have bad partitions. If you can, link me why the bootloader was replaced by FFF so I have an understanding on that please
I'm gonna update the One S toolkit soon just so you know!
I did have users who had no clue start using the toolkit. The issues they had were not reading the Post I have on Bugs (A directory issue) and they say it doesn't work. The other issue was root (which I fixed) and flashing a GB kernel onto an ICS ROM. They didn't know what it was and thought it was mandatory (even though it is under the optional section) and soft bricked their phones. I removed kernels and if they want to flash a kernel, they have to do it themselves so they can't blame me or anything.
But thanks again for all the info!
smirkis said:
the device requires different drivers for adb/fastboot.
once u get adb working, and reboot into fastboot, it usually doesn't get seen by the PC. its one of the biggest issues and lots of people have them when rooting.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Will do. Thanks for the heads up!
tgamble160 said:
I used hasoons toolkit with my amaze and gotta say thanks.hasoon andcant wwait to see what you do fornthe kindle users too.
sent from my kindle fire running gedeROM
Click to expand...
Click to collapse
Glad you liked my Amaze toolkit (btw, I updated it a few days ago if you didn't check yet)
------------------------------------------------------------------------------------------------
Everyone, I would like to thank you all for all the info you have given me! Feel free to pitch in some links of anything or anything I should know about before I make the toolkit!

Honestly, an absolute majority of the problems stem from not having the proper drivers installed. With that out of the way, I'm sure there would be a lot less posts from people complaining about stuff not working.

hasoon2000 said:
...
I will user TWRP and not add CWM since we don't want anyone to have bad partitions. If you can, link me why the bootloader was replaced by FFF so I have an understanding on that please
...
Click to expand...
Click to collapse
kinfauns wrote an excellent "Kindle Fire for Beginners" (http://forum.xda-developers.com/showthread.php?t=1552547) which goes into the details of things like why the stock bootloader was replaced w/ FFF. Main benefits of FFF is that it kicks in a temporary fastboot, and also enables easy access to recovery.
In the above-linked document, look under the "How do I unbrick my Kindle Fire?" heading for details of the benefits of FFF's temporary fastboot and access to recovery.
Having been a flashaholic, tinkerer and dabbling themer type on my Moto Droid X for the last 1.25 yrs (with several soft-bricks along the way), the general concepts w/ the Kindle Fire were familiar but the devil's in the details. Thanks to kinfaun's guides and other posts in the forums here, I learned the Kindle Fire stuff more quickly and understand things a lot better than I probably would have otherwise.

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] New KF 2nd gen, little confused

Hi everybody, just scored a 2nd gen Kindle Fire off ebay for a great price, loved my KF 1st gen.
I have been reading up and wanted to get some clarification on a few things before I start hacking it into pieces. XDA is amazing but can be confusing at times due to the raw amount of data and the age of some of the posts.
First, my info:
* KF 2nd gen 7" (non HD)
* 10.3.1 software ver (stock)
* Windows 7 pro x64 available
or
* Ubuntu 12.10 availalbe
* No Fastboot cable, but I am ok trying it without and ordering if I need to
Now, my questions:
* Is Jordan11's root method still the most usefull/sucessfull for 10.3.1 or is there another more accepted route to root? - http://forum.xda-developers.com/showthread.php?t=2075959
* Is fmkilo's 2nd bootloader/twrp script the accepted model for loading recovery image or is there a more manual but more sucessfull method? - http://forum.xda-developers.com/showthread.php?t=2106463
* Does the boot0 block still need to be backed up or has this issue been fixed? - http://forum.xda-developers.com/showthread.php?t=2106463
If the above methods are generally frowned on, please link replacement for root/2nd bootloader/recovery that you would recommend.
**Last but not least thanks for reading, any helpfull info you can think to add is much appreciated.

Anybody?
Never seen an unanswered post this long, is the kf2 not a popular device?
Or maybe just a holiday weekend?
I plan on attempting the above monday if nobody can steer me better by then...

Yes the method of root you choose will work,
I'd use hashcodes instructions for twrp install, but both should work fine
Backup your boot0 for good measure
Sent from my GT-P3110 using xda app-developers app

Much thanks, i'll put it through the paces tomorrow, anybody else is welcome to continue posting tips for success.

mog44net said:
Much thanks, i'll put it through the paces tomorrow, anybody else is welcome to continue posting tips for success.
Click to expand...
Click to collapse
Worked fine, booted into twrp recovery, did a factory reset wipe, loaded cm10.1 and it boot looped.
Ended up getting a factory fastboot cable and restoring it, then downgraded to 10.2.3, worked like a charm after that.
FYI, after root I used the adb install apk route to get and use the apk twrp and 2nd bootloader method, works perfect and fast.

[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.

help needed please !!

Hello All XDA members,
I have a Kindle HD 8.9 and as the warranty passed off, at the same time Christmas is nearing...I decided to install CM KK on my sons kindle as i don't have enough money to give a present to my son.
I've done all that is given here : http://forum.xda-developers.com/showthread.php?t=2100963.
Problems I've faced are as the thread didn't mention to root I was trying some codes without that but some how figured that i needed root to proceed..Simultaneously rooted my kindle rebooted and then proceeded with the codes i.e backup of system img and all the steps that were given.
I has all the downloaded files in download directory so the stack push didn't work first then i moved all the required files to C> ADB folder and everything worked but before figuring it out i googled stack file push failure and came across a guide that has the stack push directory to data/temp (I see that this was later edited here)
However i retried with the push to the location that is currently mentioned now and it worked (So the stack file is at 2 locations now)
Proceeded with all next steps and stuck at flashing bin file in fastboot, realized the downloaded file was .bin.html i renamed it to bin and flashed
Everything was done as mentioned except something that needed to be understood and done by logical thinking like removing .html and flashing .bin.
After all this when the kindle was supposed to reboot it didn't and its completely dead now... I have done all that was mentioned and have said all the errors or misses that i has above ..now is it that the kindle is dead brick forever ?
I cant trust how can that be because i really know how cautious i was and i did almost every thing as mentioned..
Saddest part is that now I've messed up my sons kindle which i thought of Flashing CM KK and giving a little gift as i'm not capable of providing any gift now ..I've messed his kindle as well now
I'd be really glad and thankful if some one can help me out in this situation and recover kindle.
Again i'd like to mention I've done as mentioned please trust me and still have the image backups, i read that the back up can be reflashed but as there is no commuication via ADB or flashboot i don't thing that can be done now .
Why did this happen what can be possible reason ?

Sounds like you may have accidently saved a webpage instead of the .bin file, that's why it had the .html on the end. If you tried to flash this to the bootloader then unfortunately you have bricked it

Broncos15 said:
Sounds like you may have accidently saved a webpage instead of the .bin file, that's why it had the .html on the end. If you tried to flash this to the bootloader then unfortunately you have bricked it
Click to expand...
Click to collapse
No if that was the case then why will the file bo .bin.html ?

Mr.Dumb said:
No if that was the case then why will the file bo .bin.html ?
Click to expand...
Click to collapse
It shouldn't have .html on the end. Check the md5 sum for the file and make sure that it is the same as it should be, you should ALWAYS do this when messing with the bootloader

Maybe you flashed wrong images.
I just went to the link of the guide that you followed in flashing a second bootloader and recovery. The instructions are for a Kindle Fire 2/ Otter2. Its a different device from the KF HD 8.9. So.... if you did flash the images from that link, it will lead to a bricked device no matter if you followed the instructions to the letter. Maybe you can sell it on ebay or Craigslist for parts. Just a thought...

maxaurelius said:
I just went to the link of the guide that you followed in flashing a second bootloader and recovery. The instructions are for a Kindle Fire 2/ Otter2. Its a different device from the KF HD 8.9. So.... if you did flash the images from that link, it will lead to a bricked device no matter if you followed the instructions to the letter. Maybe you can sell it on ebay or Craigslist for parts. Just a thought...
Click to expand...
Click to collapse
I actually plan on doing this for a similar reason. My sons kindle battery life is appalling as it drains faster than before and charges slower, plus kindle updates are lacking badly and some things don't work anymore.
I hope you can fix it somehow.
Happy new year.

Mr.Dumb said:
Hello All XDA members,
I have a Kindle HD 8.9 and as the warranty passed off, at the same time Christmas is nearing...I decided to install CM KK on my sons kindle as i don't have enough money to give a present to my son.
I've done all that is given here : http://forum.xda-developers.com/showthread.php?t=2100963.
Problems I've faced are as the thread didn't mention to root I was trying some codes without that but some how figured that i needed root to proceed..Simultaneously rooted my kindle rebooted and then proceeded with the codes i.e backup of system img and all the steps that were given.
I has all the downloaded files in download directory so the stack push didn't work first then i moved all the required files to C> ADB folder and everything worked but before figuring it out i googled stack file push failure and came across a guide that has the stack push directory to data/temp (I see that this was later edited here)
However i retried with the push to the location that is currently mentioned now and it worked (So the stack file is at 2 locations now)
Proceeded with all next steps and stuck at flashing bin file in fastboot, realized the downloaded file was .bin.html i renamed it to bin and flashed
Everything was done as mentioned except something that needed to be understood and done by logical thinking like removing .html and flashing .bin.
After all this when the kindle was supposed to reboot it didn't and its completely dead now... I have done all that was mentioned and have said all the errors or misses that i has above ..now is it that the kindle is dead brick forever ?
I cant trust how can that be because i really know how cautious i was and i did almost every thing as mentioned..
Saddest part is that now I've messed up my sons kindle which i thought of Flashing CM KK and giving a little gift as i'm not capable of providing any gift now ..I've messed his kindle as well now
I'd be really glad and thankful if some one can help me out in this situation and recover kindle.
Again i'd like to mention I've done as mentioned please trust me and still have the image backups, i read that the back up can be reflashed but as there is no commuication via ADB or flashboot i don't thing that can be done now .
Why did this happen what can be possible reason ?
Click to expand...
Click to collapse
As stated by Max above, if you flashed those images from that thread you linked to in your post, then those are the incorrect files for your device. and would have definitely bricked it! assuming you do have the FFHD 8.9 inch. but you still may be able to unbrick it. are you positive of which kindle device you have? if you are positive that it is indeed a KFHD 8.9, do you know which version it was on before you started the OP?
Mike

11fan said:
As stated by Max above, if you flashed those images from that thread you linked to in your post, then those are the incorrect files for your device. and would have definitely bricked it! assuming you do have the FFHD 8.9 inch. but you still may be able to unbrick it. are you positive of which kindle device you have? if you are positive that it is indeed a KFHD 8.9, do you know which version it was on before you started the OP?
Mike
Click to expand...
Click to collapse
Thanks a lot friends, i surely have a jem and i tried to read ad do things intended to do for jem only (seems strange to me that link i posted is for otter though i cross checked many times not to flash other device images but may be messed up in enthusiasm)
Never mind i eventually had to end up selling this on craiglist as a friend mentioned and got a working one from ebay ( to my shock it's reported as lost and stolen) looks i have great bad luck...
Now the kindle is just nothing unless i have cm in it but i will need all you guys help so that i dont end up like before
So please help me out with links so that i do all things correctly ...please i don't have any money now to loose or fix this ...
Thanks in advance
Edit : i tried to root kindle but was not able to, its on the highest or most up to date version of fire os as per amazon
I tried to root with restore by binary, cant see superuser in app drawer, able to see it in system/apps via root explorer
Tried to install firefire.apk it shows no root & root explorer doesn't rename system apps to .bak.... So i believe i cant root..
Please @11fan help me out now i need only cm on kindle thats fine for me.......
I'd be gratful to you for the help

Let me see if I got this correct, you sold the bricked kindle with the incorrect images on it on craislist? You Bought another kindle off eBay that has been reported stolen/lost? That sounds like some of my luck! So you got another kfhd 8.9? And you are for sure!? If so, go to about tablet in settings and see which version its currently running, also turn ON USB debugging and set it to allow 3rd party app installs in security settings, then get adb and fastboot working and we will go from there.
Mike
sent from my jem running CM11 using TapaTalk

11fan said:
Let me see if I got this correct, you sold the bricked kindle with the incorrect images on it on craislist? You Bought another kindle off eBay that has been reported stolen/lost? That sounds like some of my luck! So you got another kfhd 8.9? And you are for sure!? If so, go to about tablet in settings and see which version its currently running, also turn ON USB debugging and set it to allow 3rd party app installs in security settings, then get adb and fastboot working and we will go from there.
Mike
sent from my jem running CM11 using TapaTalk
Click to expand...
Click to collapse
Done all that mate and yes im sure its Kindle Fire HD 8.9 running os 8.5.1
Edit : After trying to root with binary tool and qemu tool (scripts) the device became extremely laggy

Mr.Dumb said:
Done all that mate and yes im sure its Kindle Fire HD 8.9 running os 8.5.1
Edit : After trying to root with binary tool and qemu tool (scripts) the device became extremely laggy
Click to expand...
Click to collapse
yes the lag is known issue after/when trying to root using some of the ways posted! if you can get through the lagg long enough to get an app on it i would recommend using an app called keyrootmaster you can get it here http://download.apks.org/?server=14&apkid=com.zhiqupk.root&ver=1.3.6 this is what i used and several other posters i know of, THE ONLY BAD THING IS the app is written in Indonesian language, BUT it works and after about 3 taps you got root! if you are going to CM or some other rom it shouldn't matter about the language anyway as all of that app will be gone and superuser is baked into CM anyway. see if you can get that app, get it rooted and let me know and i will try to help you get TWRP and CM installed. I hope this helps out some!
Mike

11fan said:
yes the lag is known issue after/when trying to root using some of the ways posted! if you can get through the lagg long enough to get an app on it i would recommend using an app called keyrootmaster you can get it here http://download.apks.org/?server=14&apkid=com.zhiqupk.root&ver=1.3.6 this is what i used and several other posters i know of, THE ONLY BAD THING IS the app is written in Indonesian language, BUT it works and after about 3 taps you got root! if you are going to CM or some other rom it shouldn't matter about the language anyway as all of that app will be gone and superuser is baked into CM anyway. see if you can get that app, get it rooted and let me know and i will try to help you get TWRP and CM installed. I hope this helps out some!
Mike
Click to expand...
Click to collapse
Yes please help me with TWRP / CWM. Please & I want to install CM on it now

Did you get it rooted?
Mike

11fan said:
Did you get it rooted?
Mike
Click to expand...
Click to collapse
Yes
Hello @11fan
Edit : got it rooted, TWRP installed, made a nandroid backuo & tried to flash CM (chkd MD5 as well) but CM boot screen stayed for so so long...so I rebooted the device to TWRP and did a full wipe as well as format data...now have no os installed, cant mount as usb storage to copy nandroid...kooks like i've messed again....
Praying to God that I have some way again to restore...
Edit 2 : sorted via adb sideload

Glad you got it....i was going to tell you that the LONG cm screen on first boot is normal! I just loaded cm12 on mine last night and first boot took about 8 minutes, maybe longer as I forgot to time it!
Mike