Related
I see many people having issues that are new to this kind of thing and here is a fairly simple troubleshooting guide that I have compiled that I think will help many of you get through rooting, Installing the Market, and installing twrp with no problems. This is a complete video walk through for those of you find the videos easier. I recommend that you watch the videos thoroughly before attempting this so that you can be sure that you make no mistakes…!!!
• Start off with a stock Kindle on original 6.2.1fw
• Go to this link for a video walkthrough to root the Kindle with Jcase’s Burrito root. All of the links are in the description of this video to do so. http://www.youtube.com/watch?feature=player_embedded&v=KapnjR89ICA
• Now to install the android Market this is another video walkthrough that is from the same person once again all of the links are in the video description for downloading what it is that you need to perform this action http://www.youtube.com/watch?featur...tion_598718&src_vid=KapnjR89ICA&v=rTkegVrnAvA
• Now to install a custom recovery (aka twrp2.0) this is also another video walkthrough also made from the same individual. Once again all of the files needed are in the video description http://www.youtube.com/watch?annota...&src_vid=KapnjR89ICA&feature=iv&v=JqKZLMaRSgc
• I have noticed that some people have problems getting stuck around 2:32 into the video where twrp is downloading and getting ready to install. If this happens to you and it is constantly “waiting for device” You may need to hit disconnect on your KF and run burrito root on your Kindle again, click “agree”,then click “You Rock”, Then click “root”. Once you do so you must re-open adb shell by opening a command prompt and typing the following:
cd c:\KindleADB to get into adb shell
adb devices to make sure your kindle is connected properly
adb root to get proper permissions
• Once you have done this re-open the run bat in KFU v0.9.1 and select option 5 again and it will install the twrp with proper root permissions.
• I have also noticed that some people also get stuck at 3:55 in this video at the firefire triangle. The fix for this is fairly easy and is explained in the video if you need a walkthrough step by step for doing this (Updating the drivers)here you go:
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
• If you also need a link for installing cm7 here is another video to do so also by the same individual. I do not recommend this as of yet until all of the bugs are worked out in this as I have heard many people have had problems with video playback or sound (mainly in ics) and usually end up flashing back to a custom rom anyway. It is your device though so it is completely up to you
http://www.youtube.com/watch?featur...tion_828059&v=L-zTJWY3CRc&src_vid=JqKZLMaRSgc
UPDATE JANUARY 3rd 2012
• Here is a link for a newer rom install called MIUI. This Rom is very smooth and the only thing confirmed not working at the moment (January 2, 2012 is video playback. There are however some individuals working on this issue and will hopefully have video working soon. Thanks to leeech for the MIUI port and nat3mil for the video. Here is the link for the easy to follow video tutorial.
http://www.youtube.com/watch?feature=endscreen&v=OqiX-If5w_4&NR=1
• Here is link on how to resize your internal storage (aka custom partitioning). This is called FireParted made by eldarerathis. This is good for those of you that think that they have too much storage in one place and not enough in another. Playing with partitions can cause you to lose data that is not backed up previously to editing partitions, so use at your own risk. I myself am going to use this to expand the storage on my sd card. Here is the easy to follow video tutorial.
http://www.youtube.com/watch?v=Bkff-bI-FrY
Big thanks for every one of these videos, made by nat3mil. So be sure to thank him and subscribe to his channel for all the latest easy to follow videos!
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update January 7th 2012 This is a program to fix boot loop Problems easily (For Windows Only)
I noticed that many people are still having problems with getting stuck in a recovery boot loop, firefirefire boot loop (Yellow Triangle), Or even the kindle fire boot loop. This is a program to fix it automatically like the kindle fire Utility. I believe that it was made by Zombiepiratez, and he made this to change all of the headaches that many people are having with bootloop problems, proper file permission problems, and bricking problems, so be sure to thank him if this helps you. Once again this is a batch file made only for windows so for those of you that are not on windows, I will leave the common manual fixes below. Here is the link to his thread and download for the Fire Utility Unbrick:
http://forum.xda-developers.com/showthread.php?t=1428428
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have also heard of the problem with some people getting caught in a boot loop and see a constant Kindle Fire boot screen. To fix this you must open up your cmd and type:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Also for people getting caught in a recovery boot (whenever they turn on their kindle they boot into recovery without hitting the power button do this in your cmd:
adb shell
su
idme bootmode 4000
reboot
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope that this clears up a lot of confusion for some of you weary of trying to do this to your kindle fire. I did all of this manually with my first Kindle. I have also used this method to be sure that it works and any problems that might come about when using this method and I have confirmed this to be successful. I really wanted to post this guide because I know that it is easier for some of you people new to this to follow along with a video. I know that some people say well there are a lot of tutorials out there but not one with a step by step and video links for a walk-through to do this whole procedure. If a mod could please sticky this I am sure that many would be greatful!!!
Remember that there is a thanks button…
DO not forget those who made this all possible:
Thanks to Jcase for Burrito Root & Vashypooh For KFU v.0.9.1 I would recommend that any of you that enjoy this and would like to see more mods such as these come out, to donate to these devs..
Thanks for the post. Really helped me out. Now that I have twrp 2.0 installed...
1.) how do I make a back up file (in case something happens when i try to flash a rom) so i can restore and recover to where i am at now
2.) once i do make a back up file, where is it saved and how would i access it, if i wanted to recover and restore.
3.) when i rooted my phone and flashed a new rom i had to use titanium back up to save all my apps and information. if i wanted to flash cm7, do i need to install titanium back up and do the same thing as i did on my phone or is the sd card untouched during the flashing process and all apps will remain?
Thanks
I was worried about doing this but now that I read your guide and seen the videos I am going to give this a try when I get settled in. Thank You!
I got a question as well
After installing the twrp2.0, what will happen to my Kindle? Does that mean the device is already rooted and good to go?
If I don't install the cm7, what can I do with the rooted KF?
You have to root the kindle before you can install the TWRP. the twrp 2.0 is used when you want to flash a rom and a few other things, (i think) you wont be able to install the twrp with out rooting first
babbabooey97 said:
Thanks for the post. Really helped me out. Now that I have twrp 2.0 installed...
1.) how do I make a back up file (in case something happens when i try to flash a rom) so i can restore and recover to where i am at now
2.) once i do make a back up file, where is it saved and how would i access it, if i wanted to recover and restore.
3.) when i rooted my phone and flashed a new rom i had to use titanium back up to save all my apps and information. if i wanted to flash cm7, do i need to install titanium back up and do the same thing as i did on my phone or is the sd card untouched during the flashing process and all apps will remain?
Thanks
Click to expand...
Click to collapse
I do believe that how to make a backup is on the install twrp2.0 video (the third one). I do not believe that you will have to install titanium backup like you do on your phone. I also do not believe that the sd card gets touched in the flashing process...
zwanzig said:
I got a question as well
After installing the twrp2.0, what will happen to my Kindle? Does that mean the device is already rooted and good to go?
If I don't install the cm7, what can I do with the rooted KF?
Click to expand...
Click to collapse
If you follow this guide in the order which was given everything will work out great after the first video your kindle will be Rooted. Twrp is really for creating a backup of your kindle in the current state and flashing different roms such as cm7 or ics... There are many things that you can do with a rooted Kindle really too many to name. You can run different market for starters which will give you more of a selection than what amazon has to offer. I did not mean to sound as if cm7 is not a good thing to use it is just not as stable as it could be and ics is still in the process of being worked on. I will be flashing to a different rom myself such as cm7 or cm9 or ics once they are stable with little or no bugs...
Awesome! Thanks again. I should be all set. one last question and I promise I am done bugging. if you install cm7 rom will you still get OTA updates that amazon sends out. I know on the most recent OTA update, it unrooted the kindle. As of now i am just rooted with go launcher running and i dont feel like trying to reroot if another update comes out. so if i flash to cm7 will i still receive these updates? I know this is the wrong thread for this but just thought you might know.
Thanks again for your help.. definite sticky
babbabooey97 said:
Awesome! Thanks again. I should be all set. one last question and I promise I am done bugging. if you install cm7 rom will you still get OTA updates that amazon sends out. I know on the most recent OTA update, it unrooted the kindle. As of now i am just rooted with go launcher running and i dont feel like trying to reroot if another update comes out. so if i flash to cm7 will i still receive these updates? I know this is the wrong thread for this but just thought you might know.
Thanks again for your help.. definite sticky
Click to expand...
Click to collapse
From what I understand if you are on a different rom such as cm7 you will not recieve a ota update, i could be wrong so do not quote me on that. I have however heard of people installing a modified 6.2.1 update that will help them update from the old fw to the previous one, so for them to have not gotten the update they must have either been using cm7 or turned their wifi off completely until they found a sure fix. Do a little searching on older threads you might find something when you do post back to this thread but make sure that you are sure that it does work as I would not like to have any mis-information in this thread... Thanks
[-_-] said:
From what I understand..... I would not like to have any mis-information in this thread... Thanks
Click to expand...
Click to collapse
Edited the quote for my own amusement.
What all do you use your KF for? I use mine while at work to keep from lugging my Mac around. Also for the occasional updates (socialnetworking=SN) and emailing.
Another question I would like to know is the types of differences there are when running alternatives in the ROM Dept.....fluid transitions, non changing wallpapers, and the like?
Can't give you a thanks yet because of low post count, but this is exactly the sort of thing someone needed to do.
I got home at 8:00 this morning and took a nap. I could not even sleep because I was so anxious to do this to my Kindle Fire, so I decided to get up from 2 hours of sleep in the last 48 hours and give this a shot. This was by far the best guide that I have seen to rooting the Kindle and I pulled it all off flawlessly. Thank you so much for posting this. I did have a few issues when trying to download the recovery file through Kindle Fire Utility, but I followed the guide to a tee and it worked for me perfectly!
I would thank you but I do not have enough posts to do so I hope that this thread gets pinned just in case I have some friends that need a sure fire way to do what I am about to show off to them.
Got my Kindle Fire Stuck in a bootloop.
This thread helped me a lot, now it's fixed!
Thanks a lot!
guides and explanations
Its good to see your hints, because all those really awsome videos have their traps and you can easily get trapped on it, as i did and i had a hard time to find the right way.
My secret for this is to fully understand why you have to do this and that, and here all the guides lack, because there is no explanation WHY you have to do this.
This needs more love. I was successful, because i know from my old background how a chmod works, why i had to install the drivers again and so on but it really took me a while to get this all done, because i didnt read this thread in time.
I also understand that developers are excited about their custom roms and the cyanogenMod, but really who wants to have a kindle fire without sound and a mod with so many bugs ?
I am so happy to have my kindle fire rerooted again after the latest update without opening it or using a special cable.
So this all works quite well, but the guides really need some more explanations to get a deeper understanding about what we are doing here.
I am still working on that, to learn the details.
I want to say a big thank you to all who invested their free time and to spread the knowledge about this awsome device and make the kindle fire a really usefull tablet.
Please keep on the good work ! And have fun with a fully rooted device. There are so many possibilities now !
JoshuaLintag said:
Got my Kindle Fire Stuck in a bootloop.
This thread helped me a lot, now it's fixed!
Thanks a lot!
Click to expand...
Click to collapse
You are very welcome I am glad to see that this guide helped you to get this accomplished!
Don't forget to give a big thanks to Jcase for Burrito Root and Vashypooh for Kindle Fire Utility!
BeerRunJoe said:
I got home at 8:00 this morning and took a nap. I could not even sleep because I was so anxious to do this to my Kindle Fire, so I decided to get up from 2 hours of sleep in the last 48 hours and give this a shot. This was by far the best guide that I have seen to rooting the Kindle and I pulled it all off flawlessly. Thank you so much for posting this. I did have a few issues when trying to download the recovery file through Kindle Fire Utility, but I followed the guide to a tee and it worked for me perfectly!
I would thank you but I do not have enough posts to do so I hope that this thread gets pinned just in case I have some friends that need a sure fire way to do what I am about to show off to them.
Click to expand...
Click to collapse
I am glad to see that you got through this flawlessly. This thread was made just for that very reason to help the lesser experienced user with any issues they might encounter without having to post threads that may get lost in all of the other "Help Me" threads...
If there is a mod that could please sticky this thread I do believe this will answer many questions for individuals and help new users pull off a flawless root, recovery, etc...
+1 on stickying this thread. I have just been pointing people having the same basic problems here. This thread (especially the OP) seems to be helping a lot of people who need help "filling in the blanks".
Good job [-_-]!
I have also directed many of my friends to this thread and they have also gotten through their minor problems. It is kind of funny because a lot of my friends tell me I think my kindle is bricked I just laugh say I doubt it and send them here. Can you also make a guide about going from cm7 back to a the amazon rom please. I put cm7 on my kindle and did not like it so I flashed badk and hit reboot and now I just keep booting up in recovery is there a way to get out of that?
BeerRunJoe said:
I put cm7 on my kindle and did not like it so I flashed badk and hit reboot and now I just keep booting up in recovery is there a way to get out of that?
Click to expand...
Click to collapse
Yes this will work...
1.Plug in USB cable to Kindle Fire on TWRP Recovery mode.
2.Bring up Command Prompt.
3.Key in adb shell.
4.Key in idme bootmode 4000.
5.Finally, key in reboot.
There you go..!!!
Great tutorial setup. Rooted, installed Android Market as mentioned without any issues. Have not installed the Recovery yet though.
Thanks for this thread.
The third sentence of first paragraph of the first post (by whistlestop) in the thread:
Amazon Kindle Fire> Kindle Fire Android Development > CM7 for Kindle Fire (aka standing on the shoulders Giants)
begins by referring to "The update.zip file available here".
Available where? I've put hours into searching for it (or for any version of update.zip other than the original one that this one supposedly replaced), but with no luck.
BTW, I couldn't post this question in the thread I'm referring to because, apparently, I haven't earned the right to post in the Developers' Forum.
from the op:
If you're coming from a STOCK ROM then use this version to flash.
If you're upgrading from an EXISTING CM7 install then use this ROM instead.
click on "this" ...
So, since I haven't changed the ROM before, presumably the one I need is the first one, update-cm7-wipeall.zip. The second one, update-cm7.zip, would only be for somebody who has a previous version of the cm7 ROM installed, then? (I also have one called update-wipeall.zip that I downloaded from somewhere, but I'm not absolutely sure it's for the Kindle Fire.) In any case, do these have to be renamed to update.zip, or can they be used with their present names?
Anyway, I haven't proceeded with any attempt to install CM7 yet. I got diverted by trying to first install TWRP 2.0, using the method at teamw.in/project/twrp2/79. Unfortunately, my KF is now frozen (hopefully not bricked) for the second time since I started on the TWRP attempt. The first time the Fire came back to life pretty-much by itself. I'm waiting to see if it does that again.
Incidentally, I have a file named cm7barebones-sdcardroot.7z that I also got from somewhere or other. Is it of any interest?
it seems you have downloaded different roms
the barebones i only one part - it needs 2
which one do you want to install ?
and what's your problem with twrp ? - you have to fix this first ! - how did you install twrp ? - manually or kfu ? - there is a failure in the run.bat of the current kfu (0.9.3) - take the one from this post:
http://forum.xda-developers.com/showpost.php?p=23536888&postcount=1007
I mentioned in my previous post that I may have screwed up and bricked my KF. At first it would freeze after boot with just the words kindle fire displayed on the screen until I would hold down the power button to force a shutdown. At that time, it could at least be seen by System Profiler on my Mac, though not by adb or anything else. But now the words kindle fire flash on and off every few seconds when it's plugged into the computer or a charger, and the KF is totally invisible to the computer! Moreover, it appears dead altogether when not plugged in.
Anyway, I don't think this forum is the right place to discuss this problem of mine, so, perhaps after taking a bit of time out to deal with the rest of my life, including my other gadgets, and somehow then getting the Kindle working again (perhaps even by 'stealing' a logic board from a busted KF), I'll come back here.
Anybody who has any suggestions for me that aren't relevant to this forum should send me a PM.
So, I feel like I've done my due diligence and searched the forums.
I have the HDX 7. It was on 4.5.3 and I was successful rolling it back
to 3.2.8. Safestrap installed no problem, rooted no problem.
I grabbed the Nexus 7 rom and flashed it no problem.
Problem: I flashed the Nexus 7 rom into the Stock slot, wiping out 3.2.8
I would like to get the 3.2.8 back....
Is it possible to reflash the stock slot back to 3.2.8
and then reflash the Nexus 7 rom into slot 1?
Or am I stuck with the Nexus 7 rom?
(I like the rom, but wanted the option of a dual boot)
upshot said:
So, I feel like I've done my due diligence and searched the forums.
I have the HDX 7. It was on 4.5.3 and I was successful rolling it back
to 3.2.8. Safestrap installed no problem, rooted no problem.
I grabbed the Nexus 7 rom and flashed it no problem.
Problem: I flashed the Nexus 7 rom into the Stock slot, wiping out 3.2.8
I would like to get the 3.2.8 back....
Is it possible to reflash the stock slot back to 3.2.8
and then reflash the Nexus 7 rom into slot 1?
Or am I stuck with the Nexus 7 rom?
(I like the rom, but wanted the option of a dual boot)
Click to expand...
Click to collapse
My sense is you would be taking an unnecessary risk. Leave things the way they are until you are ready for the next move. At present there is not a compelling alternative to Nexus unless you need KitKat/Lollipop compatibility and want to take a dance with stock 4.x.x. Plus if you want gaps things still seem a bit dicey at the 4.x level.
If/when a change is needed the 'upgrade' options may look very different (hopefully easier and/or more robust). You certainly won't be in any worse position leaving things they way they are now. You might even be able to recover a little space by deleting slot 1 (don't flash stock there; you will likely trash your device).
Thanks for the quick response.
The Nexus rom is great, I like it.
I'm just curious if I can flash 3.2.8 over it in the stock slot?
I'm not willing to experiment, however.
upshot said:
Thanks for the quick response.
The Nexus rom is great, I like it.
I'm just curious if I can flash 3.2.8 over it in the stock slot?
I'm not willing to experiment, however.
Click to expand...
Click to collapse
My concern is most stock images contain/assume stock recovery which can be problematic. There may be ways to mitigate with a custom flash but are likely untested. You will need to decide if the benefits outweigh the risks. Stay the course for now unless someone with more nuggets chimes in with a better solution.
Good advice. Thank you.
upshot said:
So, I feel like I've done my due diligence and searched the forums.
I have the HDX 7. It was on 4.5.3 and I was successful rolling it back
to 3.2.8. Safestrap installed no problem, rooted no problem.
I grabbed the Nexus 7 rom and flashed it no problem.
Problem: I flashed the Nexus 7 rom into the Stock slot, wiping out 3.2.8
I would like to get the 3.2.8 back....
Is it possible to reflash the stock slot back to 3.2.8
and then reflash the Nexus 7 rom into slot 1?
Or am I stuck with the Nexus 7 rom?
(I like the rom, but wanted the option of a dual boot)
Click to expand...
Click to collapse
Did you do a backup of stock slot before flashing nexus ROM into stock? By nexus 7 you mean Nexus for safestrap 1.0.1, right? If you do have a backup of stock 3.2.8, than of course you can reflash it back to stock, then switch to slot 1 and flash nexus for safestrap into slot 1, etc.
jeryll said:
Did you do a backup of stock slot before flashing nexus ROM into stock? By nexus 7 you mean Nexus for safestrap 1.0.1, right? If you do have a backup of stock 3.2.8, than of course you can reflash it back to stock, then switch to slot 1 and flash nexus for safestrap into slot 1, etc.
Click to expand...
Click to collapse
Yes, the Nexus for Safestrap. Great ROM.
Yeah....no, I didn't do a back up of 3.2.8.
Been rooting android phones for several years, I feel like such a noob.
Ok, for anyone still interested...
Turns out I had flashed the Nexus 2.0.2 Rom not the Safestrap 1.0.1
Everything worked fine except the Amazon Kindle app.
it would sync, but wouldn't display any of my books in the carousel, and
Amazon's site didn't recognize it as a valid device. No matter how many times
I would deregister, uninstall, reinstall...I got nothing from the Kindle app.
It was starting to bug me, a lot.
Just as I was about to wipe the tablet and re-flash the ROM, I realized
my mistake with the ROM version. So I got the correct version,
opened slot 1, flashed the 1.0.1 ROM into slot 1. It worked perfectly.
The Kindle app worked the way it's supposed to.
I then wiped the Stock slot and flashed the 1.0.1 into it.
Same results. Everything worked like it should.
I went back and deleted Slot 1, rebooted into the Stock slot
and it's all good. I now have a fantastic Nexus HDX tablet.
My question is then, Why didn't my initial mistake brick my tablet?
Are the ROMs similar enough that it slipped by with just the one problem?
I'm not sure I want to experiment with CM 12 or anything like that, but it
makes me wonder. And I'm going to check my serial number again to see
if I really do have a locked bootloader.
Thanks for reading,
upshot
upshot said:
Ok, for anyone still interested...
Turns out I had flashed the Nexus 2.0.2 Rom not the Safestrap 1.0.1
Everything worked fine except the Amazon Kindle app.
it would sync, but wouldn't display any of my books in the carousel, and
Amazon's site didn't recognize it as a valid device. No matter how many times
I would deregister, uninstall, reinstall...I got nothing from the Kindle app.
It was starting to bug me, a lot.
Just as I was about to wipe the tablet and re-flash the ROM, I realized
my mistake with the ROM version. So I got the correct version,
opened slot 1, flashed the 1.0.1 ROM into slot 1. It worked perfectly.
The Kindle app worked the way it's supposed to.
I then wiped the Stock slot and flashed the 1.0.1 into it.
Same results. Everything worked like it should.
I went back and deleted Slot 1, rebooted into the Stock slot
and it's all good. I now have a fantastic Nexus HDX tablet.
My question is then, Why didn't my initial mistake brick my tablet?
Are the ROMs similar enough that it slipped by with just the one problem?
I'm not sure I want to experiment with CM 12 or anything like that, but it
makes me wonder. And I'm going to check my serial number again to see
if I really do have a locked bootloader.
Thanks for reading,
upshot
Click to expand...
Click to collapse
Your serial number has nothing to do with whether you unlock your bootloader.
Since you're on 13.3.2.8, there's no way to rollback any further to a firmware with the signature exploit present.
Don't bother trying CM11 or CM12, or else you'll end up with a bricked tablet.
upshot said:
Ok, for anyone still interested...
Turns out I had flashed the Nexus 2.0.2 Rom not the Safestrap 1.0.1
...
My question is then, Why didn't my initial mistake brick my tablet?
Are the ROMs similar enough that it slipped by with just the one problem?
I'm not sure I want to experiment with CM 12 or anything like that, but it
makes me wonder. And I'm going to check my serial number again to see
if I really do have a locked bootloader.
Thanks for reading,
upshot
Click to expand...
Click to collapse
If you flashed Nexus 2.0.2 from this post then everything works as it should, Nexus 2.0.2 is designed to run with Safestrap...
And if you are on 3.2.8, then don't even try to flash CM12, that will not work with Safestrap and you will brick your device (for CM12 you need TWRP 2.8.5.0 and/or unlocked BL) ...
EncryptedCurse said:
Your serial number has nothing to do with whether you unlock your bootloader.
Since you're on 13.3.2.8, there's no way to rollback any further to a firmware with the signature exploit present.
Don't bother trying CM11 or CM12, or else you'll end up with a bricked tablet.
Click to expand...
Click to collapse
thanks for the input. I'm happy with the Nexus 1.0.1 ROM. It does everything I want it to do.
And, I didn't brick my HDX in the process.
Just out of interest, how did you root 3.2.8? I downgraded from 4.5.3 and back up to 4.5.2 for safestrap, rooted but got hit by the black screen when booting into recovery. I tried going back down to 3.2.8 but couldn't figure out how to root it.
Thanks in advance.
H3rrPie said:
Just out of interest, how did you root 3.2.8? I downgraded from 4.5.3 and back up to 4.5.2 for safestrap, rooted but got hit by the black screen when booting into recovery. I tried going back down to 3.2.8 but couldn't figure out how to root it.
Thanks in advance.
Click to expand...
Click to collapse
Towelroot works for 3.2.8 and below.
Davey126 said:
Towelroot works for 3.2.8 and below.
Click to expand...
Click to collapse
Awesome, thanks for the input. I'll give it a shot later as I've had enough of staring at it.
Success! I went through the process last night and I'm now running Safestrap and HDX Nexus v1.0.1.
Here's the steps I took for anyone else interested:
Went from 4.5.3 down to 3.2.8 using the instructions located here.
Downloaded Towelroot straight from the website, installed it on the Fire HDX Thor using ES File Explorer.
I then went and installed Safestrap located here and partitioned a new rom slot.
I then installed HDX Nexus v1.0.1 located here and booted it up... Success! Runs like a champ. I've come from a Nexus 7 (2012) so the speed is a great improvement over it.
Thanks for the advice about using Towelroot on 3.2.8. Much appreciated.
H3rrPie said:
Success! I went through the process last night and I'm now running Safestrap and HDX Nexus v1.0.1.
Here's the steps I took for anyone else interested:
Went from 4.5.3 down to 3.2.8 using the instructions located here.
Downloaded Towelroot straight from the website, installed it on the Fire HDX Thor using ES File Explorer.
I then went and installed Safestrap located here and partitioned a new rom slot.
I then installed HDX Nexus v1.0.1 located here and booted it up... Success! Runs like a champ. I've come from a Nexus 7 (2012) so the speed is a great improvement over it.
Thanks for the advice about using Towelroot on 3.2.8. Much appreciated.
Click to expand...
Click to collapse
Thanks for posting your success and the steps to get there. Handy reference for others to follow.
No problem, I've been using XDA for a long time now but have always just read content. Basically all I've learned about light tinkering with Android has come from this site so hopefully I can at least help out one person with the steps I took as a small return for all I've learned.
The opportunity to unlock the Fire HD 6/7 bootloader and unbrick all bricks is upon us ! Sadly, it's about ~4 years too late.
Nonetheless, if you are proficient with IDA Disassembler and Python, please follow these instructions to accomplish these 2 objectives.
1) Zero out rpmb partition ( mmcblk0rpmb ) - this will set all the bricks free and enable them to boot (this is how anti-rollback is wiped)
2) Enable permanent bootloader unlock (more advanced)
Here are the relevant posts on how to do this:
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256 (full instructions)
https://forum.xda-developers.com/amazon-fire/development/downgrade-fire-7-2015-softbrick-t3894671 (rpmb partition zeroing method for Fire 7 2015)
bibikalka said:
The opportunity to unlock the Fire HD 6/7 bootloader and unbrick all bricks is upon us ! Sadly, it's about ~4 years too late.
Nonetheless, if you are proficient with IDA Disassembler and Python, please follow these instructions to accomplish these 2 objectives.
1) Zero out rpmb partition ( mmcblk0rpmb ) - this will set all the bricks free and enable them to boot (this is how anti-rollback is wiped)
2) Enable permanent bootloader unlock (more advanced)
Click to expand...
Click to collapse
Yeah, I saw the Fire HD 8 thread and was wondering if it'd be possible for us. Unfortunately, I'm neither proficient with IDA Disassembler nor python. And currently my Fire is on the latest FireOS, unrooted, with the wrong recovery installed. So right now I can't get into recovery to downgrade and fix it, and the preloader method doesnt work because the read/write commands don't work on the newer FireOS. I am interested in if this is possible though!
Update: I attempted using the files from the Fire 7 thread and this is what I got:
Code:
[2019-01-29 17:33:56.846249] Waiting for bootrom
[2019-01-29 17:34:07.704879] Found port = /dev/ttyACM0
[2019-01-29 17:34:07.744128] Handshake
[2019-01-29 17:34:07.766738] Disable watchdog
b''
b'\x00\x01'
Traceback (most recent call last):
File "main.py", line 128, in <module>
main()
File "main.py", line 57, in main
handshake(dev)
File "/root/fire7-2015-downgrade-unbrick/fire7-2015-downgrade-unbrick/modules/handshake.py", line 11, in handshake
dev.write32(0x10007000, 0x22000000)
File "/root/fire7-2015-downgrade-unbrick/fire7-2015-downgrade-unbrick/modules/common.py", line 152, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/root/fire7-2015-downgrade-unbrick/fire7-2015-downgrade-unbrick/modules/common.py", line 89, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: Serial protocol mismatch
I was using the linux iso for unbricking, so I'm not sure if that had something to do with it. Also, I hand-typed that error message so if there are any inconsistencies that may be why (I didn't have an internet connection to post from the iso).
spenceboy98 said:
Yeah, I saw the Fire HD 8 thread and was wondering if it'd be possible for us. Unfortunately, I'm neither proficient with IDA Disassembler nor python. And currently my Fire is on the latest FireOS, unrooted, with the wrong recovery installed. So right now I can't get into recovery to downgrade and fix it, and the preloader method doesnt work because the read/write commands don't work on the newer FireOS. I am interested in if this is possible though!
Update: I attempted using the files from the Fire 7 thread and this is what I got:
Code:
...
RuntimeError: Serial protocol mismatch
I was using the linux iso for unbricking, so I'm not sure if that had something to do with it. Also, I hand-typed that error message so if there are any inconsistencies that may be why (I didn't have an internet connection to post from the iso).
Click to expand...
Click to collapse
See this post for the proper output:
https://forum.xda-developers.com/showpost.php?p=78792151&postcount=14
I think HD 2014 does not switch to the bootrom mode, and is in the pre-loader mode. That's why it says protocol mismatch. With Fire 7 I got the initial stages to work - so it did go into the right mode! But with HD 2014 I got the same messages as you, under Windows. So I think it's just not switching into the bootrom mode.
We need some old timers here if we are to get this done!!!
@powerpoint45
bibikalka said:
I think HD 2014 does not switch to the bootrom mode, and is in the pre-loader mode. That's why it says protocol mismatch. With Fire 7 I got the initial stages to work - so it did go into the right mode! But with HD 2014 I got the same messages as you, under Windows. So I think it's just not switching into the bootrom mode.
We need some old timers here if we are to get this done!!!
Click to expand...
Click to collapse
I'm willing to pop open the back of my Fire HD 6 to check some pins if necessary. Hopefully we're not the only ones wanting to see progress for this device.
spenceboy98 said:
I'm willing to pop open the back of my Fire HD 6 to check some pins if necessary. Hopefully we're not the only ones wanting to see progress for this device.
Click to expand...
Click to collapse
Oh, there are plenty of motherboard pictures floating around:
https://forum.xda-developers.com/showpost.php?p=78789821&postcount=90
Gotta find something like these pins : CMD, CLK, DAT0. I could not spot any labels on the motherboard pictures. If the pin is outside of a shield, it'd be trivial to pop the cover, and short the pin. Then one still has to get the right addresses for HD 2014 to make everything work
bibikalka said:
Oh, there are plenty of motherboard pictures floating around:
https://forum.xda-developers.com/showpost.php?p=78789821&postcount=90
Gotta find something like these pins : CMD, CLK, DAT0. I could not spot any labels on the motherboard pictures. If the pin is outside of a shield, it'd be trivial to pop the cover, and short the pin. Then one still has to get the right addresses for HD 2014 to make everything work
Click to expand...
Click to collapse
I didn't see any labels on the board, so I tried a few pins (the ones that xyz` suggested) and I didn't seem to have any luck there. It's possible that I wasn't holding the wire I was using firm enough against the pins, but I don't know. I'm not sure what test points on this motherboard look like and if you have any suggestions or ideas, I'm willing to give it a go.
Also, on a new installation of Ubuntu 18.10, it's not even detecting the preloader. It just boots normally. And when I try in Windows 10, the device shows up as MT65xx Preloader and won't show up as a COM device even after installing the correct drivers.
spenceboy98 said:
I didn't see any labels on the board, so I tried a few pins (the ones that xyz` suggested) and I didn't seem to have any luck there. It's possible that I wasn't holding the wire I was using firm enough against the pins, but I don't know. I'm not sure what test points on this motherboard look like and if you have any suggestions or ideas, I'm willing to give it a go.
Also, on a new installation of Ubuntu 18.10, it's not even detecting the preloader. It just boots normally. And when I try in Windows 10, the device shows up as MT65xx Preloader and won't show up as a COM device even after installing the correct drivers.
Click to expand...
Click to collapse
Yep - it's a tough cookie. No labels on the board, and button pushes don't work either to get the device into the BootRom mode. I could only get the pre-loader mode as well.
We will have to wait for somebody to figure out the electrical connections here. Unfortunately, I don't have time to dig around like that.
(HD7, 7th Gen)
Just chiming in, I tried a few pads on the board (on both sides), and was unable to kick it into bootrom mode. It also looks like our shielding is soldered on. :/
May try some other methods later, but likely not going to have the easiest of times messing with this thing.
r3pwn said:
(HD7, 7th Gen)
Just chiming in, I tried a few pads on the board (on both sides), and was unable to kick it into bootrom mode. It also looks like our shielding is soldered on. :/
May try some other methods later, but likely not going to have the easiest of times messing with this thing.
Click to expand...
Click to collapse
7th Gen, or 4th Gen? Sorry for nitpicking, but it is huge for context!
spenceboy98 said:
Yeah, I saw the Fire HD 8 thread and was wondering if it'd be possible for us. Unfortunately, I'm neither proficient with IDA Disassembler nor python. And currently my Fire is on the latest FireOS, unrooted, with the wrong recovery installed. So right now I can't get into recovery to downgrade and fix it, and the preloader method doesnt work because the read/write commands don't work on the newer FireOS. I am interested in if this is possible though!
...
Click to expand...
Click to collapse
Btw, you can always sideload FireOS 4, and get root that way. Then re-load your current latest fireos via TWRP, and install SuperSu.
bibikalka said:
Btw, you can always sideload FireOS 4, and get root that way. Then re-load your current latest fireos via TWRP, and install SuperSu.
Click to expand...
Click to collapse
I can't because I have FireOS 5 with the twrp img installed (I didn't realize that the latest update.bin didn't include a stock recovery image). And I can't use the unbricking iso because it doesnt work with the latest FireOS. So this method is my best bet for getting back to stock with a stock recovery.
Btw, I'm not sure what exactly happened, but I'm pretty sure that my playing with the pins messed with something. All I get now is the grey Amazon logo and it doesn't boot into the OS. :|
spenceboy98 said:
I can't because I have FireOS 5 with the twrp img installed (I didn't realize that the latest update.bin didn't include a stock recovery image). And I can't use the unbricking iso because it doesnt work with the latest FireOS. So this method is my best bet for getting back to stock with a stock recovery.
Btw, I'm not sure what exactly happened, but I'm pretty sure that my playing with the pins messed with something. All I get now is the grey Amazon logo and it doesn't boot into the OS. :|
Click to expand...
Click to collapse
I see. Usually, recovery is verified each time you boot, and the OS will overwrite it if the checksum does not match. But, in your case, TWRP disabled that feature, so you are out in the cold.
I have 2 tablets that are looping on the white Amazon logo. I tried to restore them via aftv2-tools, but nothing worked. It's interesting you got the same glitch.
Look at the bright side - keep poking around now on your motherboard, you have nothing to lose!
I attempted to overwrite the beginning of EMMC - and got an absolutely dead tablet, see here:
https://forum.xda-developers.com/showpost.php?p=78871662&postcount=784
No bootrom mode as far as I can see ... One of these days I'll open the case, and try to disconnect the battery.
bibikalka said:
7th Gen, or 4th Gen? Sorry for nitpicking, but it is huge for context!
Click to expand...
Click to collapse
2017 Fire HD7, so 7th gen, aka austin
r3pwn said:
2017 Fire HD7, so 7th gen, aka austin
Click to expand...
Click to collapse
You are in the wrong forum.
The 2017 Fire 7 AKA austin doesn't use the suffix HD. It's just Fire or Fire 7.
This is what you are looking for: https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
spenceboy98 said:
I can't because I have FireOS 5 with the twrp img installed (I didn't realize that the latest update.bin didn't include a stock recovery image). And I can't use the unbricking iso because it doesnt work with the latest FireOS. So this method is my best bet for getting back to stock with a stock recovery.
Btw, I'm not sure what exactly happened, but I'm pretty sure that my playing with the pins messed with something. All I get now is the grey Amazon logo and it doesn't boot into the OS. :|
Click to expand...
Click to collapse
Did put any more time into this? Was it some damaged contact?
bibikalka said:
Did put any more time into this? Was it some damaged contact?
Click to expand...
Click to collapse
No I haven't. Not sure what the issue is. As far as I know it's still not booting up to anything. I just started school recently and I left my Fire HD6 at home, so I haven't had the chance to mess around with it more.
Just for test. Is there any possiblility that pressing the power button with any volume button makes the tablet enter in BootROM. My Fire and my BQ enter in BootROM when I press volume -. Just try all the bootloaders for see if one support it like 5.0.1.
Regards!
bibikalka said:
The opportunity to unlock the Fire HD 6/7 bootloader and unbrick all bricks is upon us ! Sadly, it's about ~4 years too late.
Nonetheless, if you are proficient with IDA Disassembler and Python, please follow these instructions to accomplish these 2 objectives.
1) Zero out rpmb partition ( mmcblk0rpmb ) - this will set all the bricks free and enable them to boot (this is how anti-rollback is wiped)
2) Enable permanent bootloader unlock (more advanced)
Here are the relevant posts on how to do this:
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256 (full instructions)
https://forum.xda-developers.com/amazon-fire/development/downgrade-fire-7-2015-softbrick-t3894671 (rpmb partition zeroing method for Fire 7 2015)
Click to expand...
Click to collapse
I would love to get my HD 6 working again.
I recently ran the amonet script on my HD 10 and in a few minutes had an unlocked bootloader and TWRP. I read the HD 8 thread where the author posted his exploit and it really is an epic achievement. I'm also hoping the bootloader unlock comes to the 4K firestick as well. It's a lot of work from I read, but the firestick is popular enough to warrant that kind of attention. I have a Fire HD 6 which only boots to a recovery that allows me to reset or reboot but has no option to apply update from adb, so I've been stuck on stock Fire OS. It would be nice to finally get TWRP after so long on the HD 6.
***
Hey guys,
I was using TWRP + Lineage 15.1 ROM on my Fire HD 8 (2018 - 8th Gen) but decided to return to stock ROM and get rid of it.
As I didn't find any guidance anywhere I've tried to sideload the original stock ROM through TWRP even I didn't really think that was a good idea. I upladed the file (update-kindle-Fire_HD8_8th_Gen-PS7315_user_1958_0018354775684.bin - perhaps not the correct file anyway ) which resulted in boot loop. I now cannot access TWRP. Does anyone please have a link with instructions how to unbrick my device or even better with instructions to directly flash the stock ROM for 8th Gen please? I only keep finding links for older devices.
Many thanks guys.
ertech said:
Hey guys,
I was using TWRP + Lineage 15.1 ROM on my Fire HD 8 (2018 - 8th Gen) but decided to return to stock ROM and get rid of it.
As I didn't find any guidance anywhere I've tried to sideload the original stock ROM through TWRP even I didn't really think that was a good idea. I upladed the file (update-kindle-Fire_HD8_8th_Gen-PS7315_user_1958_0018354775684.bin - perhaps not the correct file anyway ) which resulted in boot loop. I now cannot access TWRP. Does anyone please have a link with instructions how to unbrick my device or even better with instructions to directly flash the stock ROM for 8th Gen please? I only keep finding links for older devices.
Many thanks guys.
Click to expand...
Click to collapse
It seems that the bootloader files for OS 6 (TZ and LK) are incompatible with OS 7.3.1.5. I found that you could not even shut down the tablet when it was bootlooping: holding the power button down for >30 seconds did nothing. To stop it you need to open the tablet and disconnect the battery.
You will need to copy a version of OS 6 onto a micro SD card (change the file extension from '.bin' to '.zip'). Insert the micro SD, after reconnecting the battery and putting the rear shell back on. You should be able to boot into recovery (TWRP) with the left volume button/ power button. Wipe system and data then flash the OS 6 zip.
Locate the newer thread for unlocking the HD 8/ 8th gen. tablet (amonet-3) and download the latest amonet version (currently 3.0.1) and the 'return to stock' zip, then follow the instructions in that thread to return to stock. Essentially you unzip the two downloads, merge, and run the return to stock script. From TWRP you boot the tablet into hacked fastboot mode and the script will restore stock boot and recovery images (unpatched). After a reboot you should be able to enter standard Amazon recovery mode. If you then ADB sideload the OS 7.3.1.5 software you will eventually boot into OS 7 (Pie).
Link to 'amonet-3' thread: https://forum.xda-developers.com/showpost.php?p=80166353&postcount=1
@MontysEvilTwin I haven't updated mine to 7.x release but wanted to see if you have been able to successfully unlock and root on newer firmware?
I'm guessing as you said bootloader files for OS 6 (TZ and LK) are incompatible, its not going to work?
madman said:
@MontysEvilTwin I haven't updated mine to 7.x release but wanted to see if you have been able to successfully unlock and root on newer firmware?
I'm guessing as you said bootloader files for OS 6 (TZ and LK) are incompatible, its not going to work?
Click to expand...
Click to collapse
I've had no luck unlocking the Karnak (or Mustang). I think there a couple of issues. The unlock doesn't work with the OS 7.3.1.5 bootloaders, you get a bootloop. I expected this as it is only the very first version of the Karnak LK file (OS 6.3.0.0) that has the necessary vulnerability for a full unlock. However if you use a modified version of Amonet to flash the OS 7.3.1.5 PL and TZ plus the OS 6.3.0.0 LK you get a bootloop, even without unlocking and unpatched stock boot and recovery images. It may not be impossible, I am hoping that the unlock authors (@xyz` and @k4y0z) will take a look at some point.
Thank you very much @MontysEvilTwin for your response and great explanation. Opening the device, disconnecting the battery and taking all these steps just to flash the stock ROM and selling it for a few pounds is probably way more effort than what it's worth. I'll probably just sell the case and hand the device for a safe disposal. It might be perhaps worth it to create a separate topic with a step by step walkthrough to safely revert a rooted device with TWRP & custom ROM back to Stock ROM for less advanced users like me? (I appreciate what I attempted to do was a bit stupid, just saying it would be useful having this explained somewhere...)
As I'm not going to use "Karnak" any more I'd like to thank everyone here for all their contributions as you made my experience with my device significantly better and also to thank everyone who found time to answer my questions. I just wanted to say that you're doing an amazing thing and making people like me happy. :good:
ertech said:
Thank you very much @MontysEvilTwin for your response and great explanation. Opening the device, disconnecting the battery and taking all these steps just to flash the stock ROM and selling it for a few pounds is probably way more effort than what it's worth. I'll probably just sell the case and hand the device for a safe disposal. It might be perhaps worth it to create a separate topic with a step by step walkthrough to safely revert a rooted device with TWRP & custom ROM back to Stock ROM for less advanced users like me? (I appreciate what I attempted to do was a bit stupid, just saying it would be useful having this explained somewhere...)
As I'm not going to use "Karnak" any more I'd like to thank everyone here for all their contributions as you made my experience with my device significantly better and also to thank everyone who found time to answer my questions. I just wanted to say that you're doing an amazing thing and making people like me happy. :good:
Click to expand...
Click to collapse
OK, if you just want to unbrick it is quite easy. If you have the latest TWRP (you will have if you unlocked with amonet version-3 for thIs tablet) it is likely that your bootloaders are unchanged. To get out of the bootloop you can either disconnect the battery or let it run down. Then you should be able to boot into recovery. From there you can flash a backup of your previous OS, or wipe system and data and reflash a stock OS 6 update.