Related
To Start off... This is for windows and Linux! I had a lot of trouble at first trying to root. But as soon as i stumbled upon this 1 click root and the correct adb drivers i rooted fast and easy. My kindle was running 8.4.3 for this. But several people have came to me saying it works with 8.4.6 os. So what u want is the normal usb cable and windows/linux. And download the two files at the bottom.
Before you begin, if you have Windows Vista or Windows 7 or 8, open a Command Prompt & type ‘ping 4.2.2.2‘ then press enter. If you get replies, carry on with the rest of the guide. If not, you’ll have to carry out this small fix first! Skip to the bottom where it says "Still not work? Then move onto the "How to?..."
How to?...
1. ENABLE ADB IN SETTINGS UNDER SECURITY
Step 1. Download all files provided in the post and keep kindle unplugged at all times
Step 2. To be safe uninstall any other drivers for the kindle installed on the operating system (Win.) And Reboot.
Step 3. Install the adb drivers provided in the .zip
Step 4. Unzip the bin4ry tool on ur desktop and run the .bat file for windows as admin/.sh for Linux.
Step 5. Keep kindle unplugged still... The menu u will be promoted with will ask you what is ur device type. Select normal.
Step 6. Once you selected normal and the command prompt will say plug in your device. Do it.
Step 7. It will say a bunch of stuff, once it stops spitting out lines, if your kindle isnt already. Unlock it.
Step 8. Hopefully u get a window on ur kindle asking to restore and enter ur credentials. JUST PRESS RESTORE AT THE BOTTOM.
Click to expand...
Click to collapse
IF U GET LOST... ON THE CMD JUST FOLLOW THE DIRECTIONS ON THE COMPUTER. If I helped press the like button:good:
Still not work?
Right click on My Computer/Computer (whichever you have) and choose Properties.
Go into System and this will open System properties. Once here, select ‘Advanced System Settings’.
Next choose ‘Environment Variables’ and under the ‘System Variables’ find ‘Path’.
Select ‘Path’ with your mouse and choose ‘edit’.
Scroll to the very end of the list in here. It’ll have various paths for different things, all separated by a semi-colon like this ‘;‘. Be careful not to change anything else here, simply paste in ‘;C:\Windows\System32‘. Note that there’s no space between ; and the C:\Windows\System32 and this statement isn’t case sensitive, it can be both upper and lowercase or a mix.
Click OK & repeat until you’ve closed System Properties.
Test by opening Command Prompt (Start > Run > cmd OK, Win-key + R > cmd OK, or however you prefer to get there) & ping 4.2.2.2 again. If you see replies, congratz, you’re all set!
Click to expand...
Click to collapse
Kindle Fire HD 8.9 ADB drivers.zip
Bin4ry Root v30
Reserved :highfive:
2nd bootloader and TWRP for 8.4.3
Brandonrz said:
To Start off... This is for windows and Linux! I had a lot of trouble at first trying to root. But as soon as i stumbled upon this 1 click root and the correct adb drivers i rooted fast and easy. My kindle was running 8.4.3 for this. So what u want is the normal usb cable and windows/linux. And download the two files at the bottom.
Before you begin, if you have Windows Vista or Windows 7, open a Command Prompt & type ‘ping 4.2.2.2‘ then press enter. If you get replies, carry on with the rest of the guide. If not, you’ll have to carry out this small fix first! Skip to the bottom where it says "Still not work? Then move onto the "How to?..."
How to?...
IF U GET LOST... ON THE CMD JUST FOLLOW THE DIRECTIONS ON THE COMPUTER. If I helped press the like button:good:
Still not work?
Kindle Fire HD 8.9 ADB drivers.zip
Bin4ry Root v30
Click to expand...
Click to collapse
Now that I'm rooted could you do a tutorial on how to add a 2nd bootloader plus TWRP using 8.4.3? It would be greatly appreciated by many of us beginners!
rebelduke said:
Now that I'm rooted could you do a tutorial on how to add a 2nd bootloader plus TWRP using 8.4.3? It would be greatly appreciated by many of us beginners!
Click to expand...
Click to collapse
I'll get on it asap, but remember that I'm playing it by ear since I just got my kindle about a week ago. Right now I'm creating a tut on how to install the play store.
Sent from my Kindle Fire 8.9 HD via T-T Hd
Unfortunately it's not working for me. My Kindle is on 8.4.3 and has ADB enabled.I've installed the ADB drivers and rebooted my Windows 7 64-bit PC. I've pinged the tablet and get a response. I run the batch file as admin and press (1). I get some messages including "connect your device". A demon gets succesfully started at 5037. But after that I see nothing... My kindle's screen is unlocked, btw.
Any ideas?
pattiman said:
Unfortunately it's not working for me. My Kindle is on 8.4.3 and has ADB enabled.I've installed the ADB drivers and rebooted my Windows 7 64-bit PC. I've pinged the tablet and get a response. I run the batch file as admin and press (1). I get some messages including "connect your device". A demon gets succesfully started at 5037. But after that I see nothing... My kindle's screen is unlocked, btw.
Any ideas?
Click to expand...
Click to collapse
Delete the bin4ry folder. And unzip it again, run option 1 while unplugged. Then plug in your kindle.
Sent from my Kindle Fire 8.9 HD via T-T Hd
I tried the older root option and that worked fine. Thanks for your effort!
pattiman said:
I tried the older root option and that worked fine. Thanks for your effort!
Click to expand...
Click to collapse
Np. Glad I could help.
Sent from my Kindle Fire 8.9 HD via T-T Hd
pattiman said:
I tried the older root option and that worked fine. Thanks for your effort!
Click to expand...
Click to collapse
What does this mean? The older root option?
I am in the exact same boat. I can ping the device, but when running runme.bat it just sticks at waiting for device.
I deleted and re-extracted the zip file. That did not help. I am going to go try other root options to see if I can figure out which one you did that worked.
spearoid said:
What does this mean? The older root option?
I am in the exact same boat. I can ping the device, but when running runme.bat it just sticks at waiting for device.
I deleted and re-extracted the zip file. That did not help. I am going to go try other root options to see if I can figure out which one you did that worked.
Click to expand...
Click to collapse
I was able to use the instructions in the OP to root my KFHD 8.9 on 8.4.3. The adb drivers linked to in the OP were the problem for me. I had previously installed drivers that were a different size exe (9.183 MB) that I reverted to that allowed me to connect to the Fire through adb and run the tool from the OP to root.
spearoid said:
What does this mean? The older root option?
Click to expand...
Click to collapse
I used the method from this thread: http://forum.xda-developers.com/showthread.php?t=2069117
spearoid said:
I was able to use the instructions in the OP to root my KFHD 8.9 on 8.4.3. The adb drivers linked to in the OP were the problem for me. I had previously installed drivers that were a different size exe (9.183 MB) that I reverted to that allowed me to connect to the Fire through adb and run the tool from the OP to root.
Click to expand...
Click to collapse
I'm glad I could help another root
Sent from my Kindle Fire 8.9 HD via T-T Hd
1 downgrade, 2 failed attempts, one brick and a redscreen later... I installed 2nd boot loader + twrp + cm10.1 All starting from 8.4.3 ganna post a tut soon for you guys.
Sent from my Amazon Kindle Fire HD using Tapatalk HD
Edit: Delete post, mod please.
Sent from my Amazon Kindle Fire HD using Tapatalk HD
so i did everything step by step ,
it appeared to communicate fine and said done, however my device remains unrooted - no super user function
any ideas?
///
Update - manually installed super user app and prompt app, got it working!!
wnyzfinest said:
so i did everything step by step ,
it appeared to communicate fine and said done, however my device remains unrooted - no super user function
any ideas?
///
Update - manually installed super user app and prompt app, got it working!!
Click to expand...
Click to collapse
Glad you got it
Sent from my Amazon Kindle Fire HD using Tapatalk HD
8.4.6 Update..
Does anyone know if this root method will work for the 8.4.6 update that my Kindle just automatically upgraded to? I had it rooted before on 8.4.3 using this method.
Trying to decide if I risk it or wait till someone with a factory cable tests it first. Please let me know if it works successfully for you and I will update with my results if I get brave and try it myself...
Board373 said:
Does anyone know if this root method will work for the 8.4.6 update that my Kindle just automatically upgraded to? I had it rooted before on 8.4.3 using this method.
Trying to decide if I risk it or wait till someone with a factory cable tests it first. Please let me know if it works successfully for you and I will update with my results if I get brave and try it myself...
Click to expand...
Click to collapse
Did you have OTA updates blocked on 8.4.3? If so, by what method? I'm just asking because I'm still nervous about leaving my wifi on after rooting 8.4.3 and using the method of OTA blocking which renames the otacerts file.
sonicanomaly said:
Did you have OTA updates blocked on 8.4.3? If so, by what method? I'm just asking because I'm still nervous about leaving my wifi on after rooting 8.4.3 and using the method of OTA blocking which renames the otacerts file.
Click to expand...
Click to collapse
No I did not have OTA updates blocked and I always leave WiFi on, otherwise its a paperweight in my opinion. I hope this method will work for root with 8.4.6 but I think I will wait for someone with a factory cable to attempt first.
Board373 said:
No I did not have OTA updates blocked and I always leave WiFi on, otherwise its a paperweight in my opinion. I hope this method will work for root with 8.4.6 but I think I will wait for someone with a factory cable to attempt first.
Click to expand...
Click to collapse
Ah, I agree about that and it's why I hate being uncertain if my OTA blocking works because I'd hate to be stuck with an update that finally breaks the rooting exploit or something of that sort. That said, however, from what I've read the 8.9" Fire HD doesn't need a factory cable to enter fastboot. No confirmation on my end of that, as I've yet to need to use fastboot and thus haven't tried it.
I do know, however, that KFFirstAide's method of rooting with the latest version of the software (downloaded from here: http://forum.xda-developers.com/showthread.php?t=2096888 ) worked flawlessly on 8.4.3 for me. And those who tried the older version on 8.4.3 didn't report any bricking or anything of that sort, simply that the process completed but did not successfully root. I would assume, but certainly not guarantee or suggest to know with any certainty, that it puts the risk of bricking in the event it can't root the firmware version down to a low percentage. It may be worth attempting. But I definitely see why you're worried about it; I'd be hesitant, as well.
Good luck, and I hope someone who's had experience with 8.4.6 can come along and offer you some solid answers. I'd definitely suggest blocking OTA updates when you regain root, though. With OTA blocked, you can still manually download any updates you want (preferably after seeing whether it's capable of being re-rooted) and install them via usb, whenever you wish.
Ok, so I'm a noob when it comes to this stuff, but I have managed to root my Kindle Fire HD 7" and I installed the Google play store, so I was happy thus far. Yesterday I lost root and couldn't figure out why. Today I noticed that my Kindle had done an update from 7.4.6 to 7.4.8 and I'm wondering if this is why I lost root? If so, how can I fix this to get my Kindle back into root? Like I said, I'm a noob and don't want to screw up my Kindle messing around with stuff when I don't have a clue. Any advice would be of great help, thanks in advance.
Oh yeah, I should add this information: I get this pop up from Superuser, "There is no SU binary installed and Superuser can not install it. This is a problem"
Yea when it updates it clears the system partition where the su binary is stored, you need to reroot it. Never heard of a 7.4.8 update, but if it is a new one and you can reroot it then you can just downgrade it with kindle fire first aid by sticking it into fastboot with a simple "adb reboot bootloader", think kffa will do it for you though.
Sent from my Amazon Kindle Fire HD using Tapatalk
masterndentske
stunts513 said:
Yea when it updates it clears the system partition where the su binary is stored, you need to reroot it. Never heard of a 7.4.8 update, but if it is a new one and you can reroot it then you can just downgrade it with kindle fire first aid by sticking it into fastboot with a simple "adb reboot bootloader", think kffa will do it for you though.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
" Never heard of a 7.4.8 update, but if it is a new one and you can reroot it " Hmmmm, the way you worded that makes me feel like I might be stepping into uncharted territory if I try to root it again and I don't like the thought of that. I'll think about it and maybe give it a try tomorrow after I get some sleep and my head is clear. Thanks for the advice, I really appreciate it.
cautiousone said:
" Never heard of a 7.4.8 update, but if it is a new one and you can reroot it " Hmmmm, the way you worded that makes me feel like I might be stepping into uncharted territory if I try to root it again and I don't like the thought of that. I'll think about it and maybe give it a try tomorrow after I get some sleep and my head is clear. Thanks for the advice, I really appreciate it.
Click to expand...
Click to collapse
I had the same problem starting yesterday. My Kindle upgraded to 7.4.8 and any app requiring root stopped working, namely Google Play Store, SuperUser, ... I used KFFirstAide to re-root the Kindle and all is working so far.
blackeyeX2 said:
I had the same problem starting yesterday. My Kindle upgraded to 7.4.8 and any app requiring root stopped working, namely Google Play Store, SuperUser, ... I used KFFirstAide to re-root the Kindle and all is working so far.
Click to expand...
Click to collapse
:good: Awesome, thanks for passing that on to me, I'm going to give it a go and see what happens. I'll post a status update later today after I've had a chance to thoroughly test it.
:victory: Well I got it to root again and reinstalled google play with no issues to report, all went well. So is there a way to stop Amazon from updating my Kindle in the future? Now, the next task is to get a second boot loader on it, although I don't have a fastboot cable, so I'm kinda chicken, hahaha. But I'm feeling confident now, so maybe I'll give it a shot tonight. Wish me luck... A big thanks for the help, I guess I just needed some reassurance on re-rooting the thing and I'm happy.
Just make sure you downgrade the bootloader first, if you don't use the fireflash method then I recommend making sure to check the md5sum of the bootloader before downgrading it so you don't end up with a paperweight.
Sent from my Amazon Kindle Fire HD using Tapatalk
I'm having this issue also. Same update, same loss of SU + Play store.
I can't get my kindle to root like before though. It says it was successful but my fire becomes extremely laggy, no icons appear, where the navigation swipe is there are slightly darker vertical lines and the only way I've fixed it is by factory restore.
How are you rerooting???
I can't remember how I rooted in the first place, I only remember that I had massive issues getting GP store on and used this KFFA which is what I'm now using to reroot.
http://forum.xda-developers.com/showthread.php?t=2069329
Any suggestions would be massively appreciated
kindle fire hd 7.4.8
same thing happen to me so I tried getting adb to work witch it didn't that well, so I downloaded the update .bin file from amazon and edited it useing winRAR just added SuperSU to /system/app then changed a few things in kindle first aid then used a fastboot cable to upload the custom update so my kindle is running v7.4.9 witch I changed it to because it didn't work any other way. i'll make a video
dEADwEIRD said:
I'm having this issue also. Same update, same loss of SU + Play store.
I can't get my kindle to root like before though. It says it was successful but my fire becomes extremely laggy, no icons appear, where the navigation swipe is there are slightly darker vertical lines and the only way I've fixed it is by factory restore.
How are you rerooting???
I can't remember how I rooted in the first place, I only remember that I had massive issues getting GP store on and used this KFFA which is what I'm now using to reroot.
http://forum.xda-developers.com/showthread.php?t=2069329
Any suggestions would be massively appreciated
Click to expand...
Click to collapse
I just followed the same steps as I did the first time I rooted it, I used KFFA. But this time around some of the actions described didn't happen, like Superuser didn't ask for permission as it did the first go around and a few other little things, but I just took it slow and easy and it came out working fine. Also I used KFFA to install GP, it also skipped a few actions, but I just have it a little extra time to do its thing and it works perfectly. I saw a fix for the laggy screen and icons issue somewhere, I think it's in KFFA? I would have to double check that when I get home to be certain.
stunts513 said:
Just make sure you downgrade the bootloader first, if you don't use the fireflash method then I recommend making sure to check the md5sum of the bootloader before downgrading it so you don't end up with a paperweight.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the heads up on that, I've held off on doing it until I have more time to research it. I like to feel somewhat comfortable going into it and not totally freaked out. Thanks again, you guys are great around here.
Sorted.
I rooted using The Bin4ry Method and using KFFA to bring all the other systems back on line.
is anyone having problems with ADB and fastboot on 7.4.8?
Because I tried rooting using KFFA that didn't work I kept getting errors so I tried using fastboot to flash the recovery using this code
Code:
fastboot flash recovery recovery.img
I get "device not found" or when it dose work i get "failed to flash" (something like that) but i have the adb drivers installed would there be different ones for 7.4.8? When I type
Code:
fastboot device
it finds the device it just dosn't work when I want to flash
and only half the adb commands work
You have to have it with a special parameter telling it what the kindles vendor id is so it should look like this...:
Code:
fastboot -i 0x1949 flash recovery recovery.IMG
Try that.
Sent from my Amazon Kindle Fire HD using Tapatalk
"... I used KFFirstAide to re-root the Kindle and all is working so far."
I tried using bin4ry's root, which is how I originally rooted my kindle, but it did not work.
I am pleased to say that KFFirstAide was able to restore root.
Thank you xda for pointing me in the right direction!
stunts513 said:
You have to have it with a special parameter telling it what the kindles vendor id is so it should look like this...:
Code:
fastboot -i 0x1949 flash recovery recovery.IMG
Try that.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thank you!!! i got root access by flashing with twrp recovery witch you can get more info at
http://forum.xda-developers.com/showthread.php?t=2128848
on my other kindle i used Bin4ry root witch work but i had to turn off adb/usb debugging and turn it back on during the process because it wouldn't find the device if i didn't
you can download Bin4ry here
http://forum.xda-developers.com/showthread.php?t=1886460
gregcavaretta said:
on my other kindle i used Bin4ry root witch work but i had to turn off adb/usb debugging and turn it back on during the process because it wouldn't find the device if i didn't
Click to expand...
Click to collapse
Thank's, KFFA not recovered and Bin4ry work only after turn off adb / usb debugging
Ciao dal Max
gregcavaretta said:
Thank you!!! i got root access by flashing with twrp recovery witch i downloaded at
http://teamw.in/project/twrp2/79
on my other kindle i used Bin4ry root witch work but i had to turn off adb/usb debugging and turn it back on during the process because it wouldn't find the device if i didn't
you can download Bin4ry here
http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
wtf????? that was a twrp image for the kf1, that should have broken more than it fixed on a kfhd.
Holy ****!!! Your kindle works after flashing the recovery IMG that was for the kf1???
Sent from my Kindle Fire HD 7 running PAC-man
wire55 said:
Holy ****!!! Your kindle works after flashing the recovery IMG that was for the kf1???
Sent from my Kindle Fire HD 7 running PAC-man
Click to expand...
Click to collapse
stunts513 said:
wtf????? that was a twrp image for the kf1, that should have broken more than it fixed on a kfhd.
Click to expand...
Click to collapse
I posted the Wrong link i'm truly sorry if you messed up your kindle fire
Hello and thanks for reading!
I have a Kindle Fire 5th Gen that was just given to me. I'd like to get rid of the Amazon OS and install anything (I'll take CM or whatever). It is currently running 5.1.2 yet KingRoot v4.9.2 says it is 5.1.1.
I've tried KingRoot a few times (apparently you need root to get TWRP going) and nothing happens - it keeps failing.
I've gone through some RootJunky videos but those aren't updated for 5.1.2 via Windows.
I'm at a loss of what to do next. This video says that installing an old version of Fire OS will brick your Kindle.
All of these different threads have me confused.
My questions are:
I understand that TWRP doesn't work on 5.1.2, so how do I get to a different version of Fire OS? And how do I disable OTA's? Turn off Wifi?
When I get to a different version of Fire OS, will RootJunky's tools work like in his videos?
I apologize if this is already answered in another thread as I can't find it and am new to the Kindle Fire.
I'd like to be able to use it for my school books next semester instead of having to bring the big effin things back and forth. For $50 bucks (retail), this seems like a steal to get a vanilla version of Android running on it!
Thanks in advance!
Pcprik said:
Hello and thanks for reading!
I have a Kindle Fire 5th Gen that was just given to me. I'd like to get rid of the Amazon OS and install anything (I'll take CM or whatever). It is currently running 5.1.2 yet KingRoot v4.9.2 says it is 5.1.1.
I've tried KingRoot a few times (apparently you need root to get TWRP going) and nothing happens - it keeps failing.
I've gone through some RootJunky videos but those aren't updated for 5.1.2 via Windows.
I'm at a loss of what to do next. This video says that installing an old version of Fire OS will brick your Kindle.
All of these different threads have me confused.
My questions are:
I understand that TWRP doesn't work on 5.1.2, so how do I get to a different version of Fire OS? And how do I disable OTA's? Turn off Wifi?
When I get to a different version of Fire OS, will RootJunky's tools work like in his videos?
I apologize if this is already answered in another thread as I can't find it and am new to the Kindle Fire.
I'd like to be able to use it for my school books next semester instead of having to bring the big effin things back and forth. For $50 bucks (retail), this seems like a steal to get a vanilla version of Android running on it!
Thanks in advance!
Click to expand...
Click to collapse
- although your device shows 5.1.2 it is likely running 5.1.2.1 which can not be rooted at present
- you need to reload (sideload) 'pure' 5.1.2 via the stock recovery menu; there are instructions and videos posted elsewhere in this forum
- once on 5.1.2 use the SuperTool to root, block OTA, swap out Kinguser for SuperSU and obtain FlashFire which is used to install custom roms
- TWRP is not an option for your device at this time (nor is it likely in the near future)
- suggest looking through the index for relevant material (link below)
- keep reading; you'll get the hang of it
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Davey126 said:
- although your device shows 5.1.2 it is likely running 5.1.2.1 which can not be rooted at present
- you need to reload (sideload) 'pure' 5.1.2 via the stock recovery menu; there are instructions and videos posted elsewhere in this forum
- once on 5.1.2 use the SuperTool to root, block OTA, swap out Kinguser for SuperSU and obtain FlashFire which is used to install custom roms
- TWRP is not an option for your device at this time (nor is it likely in the near future)
- suggest looking through the index for relevant material (link below)
- keep reading; you'll get the hang of it
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Click to expand...
Click to collapse
Thanks!
I may have hit a 'small' snag though. When I put 5.1.2 from the Index page on, Kingroot still didn't work so I put the next oldest version on (5.1.1 I believe). Now it won't startup and just has a black screen - I believe I forgot to select wipe cache before restarting. When I plug it into my Surface, Device Manager keeps making noises and I have installed the MTK VCOM drivers. I'm going to try to put 5.1.2.1 back on but I'm wondering if this thing is actually bricked? According to this thread it's possible to 'unbrick' it but if it doesn't turn on, how does it get into recovery mode?! Perhaps it's in recovery mode now with the blank screen? When I do 'adb devices', nothing shows up so I'm guessing it's not connected? Even doing 'adb sideload <filename>' shows no devices connected.
Thanks again!
Pcprik said:
Thanks!
I may have hit a 'small' snag though. When I put 5.1.2 from the Index page on, Kingroot still didn't work so I put the next oldest version on (5.1.1 I believe). Now it won't startup and just has a black screen - I believe I forgot to select wipe cache before restarting. When I plug it into my Surface, Device Manager keeps making noises and I have installed the MTK VCOM drivers. I'm going to try to put 5.1.2.1 back on but I'm wondering if this thing is actually bricked? According to this thread it's possible to 'unbrick' it but if it doesn't turn on, how does it get into recovery mode?! Perhaps it's in recovery mode now with the blank screen? When I do 'adb devices', nothing shows up so I'm guessing it's not connected? Even doing 'adb sideload <filename>' shows no devices connected.
Thanks again!
Click to expand...
Click to collapse
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Davey126 said:
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Click to expand...
Click to collapse
That's what I thought.
Thanks again for your help!
Davey126 said:
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Click to expand...
Click to collapse
Just to confirm, I should have put 5.1.2 and then rooted, correct? I may buy a new one.
Pcprik said:
Just to confirm, I should have put 5.1.2 and then rooted, correct? I may buy a new one.
Click to expand...
Click to collapse
Correct. Summary here; see index for more robust coverage.
Ok, so this device came with 5.1.1 and when I plugged it in to let it charge up (even in airplane mode) it had already gotten a hold of 5.1.2.1. So yeah, it installed 5.1.2.1 and after much aggravation and research, I realized I was able to downgrade to 5.1.2 I used the files from here: http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3 to get the 5.1.2 binary file.
It did downgrade successfully to 5.1.2 because now it's telling me "Your device is running Fire OS 5.1.2, Fire OS 5.1.2 (542169020) is ready to install."
Anyway, I've installed the latest official version of Kingroot (4.92 from June 3rd-2016) and it's a no-go.
It will get to between 16%-18% and then reboot itself. Then it will get to about 19% and then Kingroot will crash.
I've tried all the tricks, unplugged my USB, rebooted a million times, installed Kingroot several times, factory reset/cache clear, tried the PC version of Kingroot, removed Kingroot from "Recents" between reboots/crashes and I end up with the same. ZERO results.
If anyone has any insight into anything I may have missed or any other ideas, I would very much appreciate it.
Thank you
tucstwo said:
Ok, so this device came with 5.1.1 and when I plugged it in to let it charge up (even in airplane mode) it had already gotten a hold of 5.1.2.1. So yeah, it installed 5.1.2.1 and after much aggravation and research, I realized I was able to downgrade to 5.1.2 I used the files from here: http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3 to get the 5.1.2 binary file.
It did downgrade successfully to 5.1.2 because now it's telling me "Your device is running Fire OS 5.1.2, Fire OS 5.1.2 (542169020) is ready to install."
Anyway, I've installed the latest official version of Kingroot (4.92 from June 3rd-2016) and it's a no-go.
It will get to between 16%-18% and then reboot itself. Then it will get to about 19% and then Kingroot will crash.
I've tried all the tricks, unplugged my USB, rebooted a million times, installed Kingroot several times, factory reset/cache clear, tried the PC version of Kingroot, removed Kingroot from "Recents" between reboots/crashes and I end up with the same. ZERO results.
If anyone has any insight into anything I may have missed or any other ideas, I would very much appreciate it.
Thank you
Click to expand...
Click to collapse
- sideload 5.1.2 again
- on reboot do not register device with Amazon
- try rooting (kingroot)
Davey126 said:
- sideload 5.1.2 again
- on reboot do not register device with Amazon
- try rooting (kingroot)
Click to expand...
Click to collapse
Ill give this a shot. Thanks!
Davey126 said:
- sideload 5.1.2 again
- on reboot do not register device with Amazon
- try rooting (kingroot)
Click to expand...
Click to collapse
You, my friend... Are. The. Man! Thank you. It did hiccup on the first try but the second one was successful and I was able to switch over to SuperSu and all is well. Thank you!
What a dumb thing to cause such an issue. I would have pulled all my hair out before trying this. Thanks again!
tucstwo said:
You, my friend... Are. The. Man! Thank you. It did hiccup on the first try but the second one was successful and I was able to switch over to SuperSu and all is well. Thank you!
What a dumb thing to cause such an issue. I would have pulled all my hair out before trying this. Thanks again!
Click to expand...
Click to collapse
Glad it worked out! If you intend to flash a custom rom (CM12, Nexus, etc.) be sure to grab the latest version of FlashFire from here (guidance/tips here). Some earlier versions were a bit shaky on this device.
Davey126 said:
Glad it worked out! If you intend to flash a custom rom (CM12, Nexus, etc.) be sure to grab the latest version of FlashFire from here (guidance/tips here). Some earlier versions were a bit shaky on this device.
Click to expand...
Click to collapse
Yeah, I'm aware of all of those things. These were actually 4 separate tablets (3 for my daughters and one for my mother) and I just wanted to remove the lock screen ads and prevent future OTAs (all of which require root) plus plop on the Play Store.
I don't think any of them care about flashing ROMs, but I hate when a system takes control over my device and prevents me doing what I want to do with it.
Again, thanks for that most obscure of solutions (on top of the other obscure prerequisites)!
Davey126 said:
- sideload 5.1.2 again
- on reboot do not register device with Amazon
- try rooting (kingroot)
Click to expand...
Click to collapse
I am having the same issue as OP. I have tried not registering with Amazon and it still isn't working for me. I am definitely on 5.1.2 and not 5.1.2.1. I have 3 of these tablets and this is the only one that I haven't been able to get it to work on. The others only took 1 or 2 tries. Anything else I could try?
Edit: Right after posting this it finally worked. If anyone else finds this thread with the same issue, I would say just keep trying. It took me probably 15-20 attempts but it eventually just worked.
Also I had trouble using the kingroot app on the tablet. If you go to the website and dl it to the pc and use kr it works every time
Sent from my SM-N910T3 using XDA-Developers mobile app
My tablet just jumped from 5.3.2.1 to 5.3.3.0 in one day. I tried kingroot several times hoping it would work. It did not. I performed factory reset on it and signed into amazon. When i woke up it was at 5.4.0.0. My question is if a root exploit is found for 5.3.2.1 or 5.3.3.0 can it be rolled back? This all started from a bad SD card that kept resetting my old fire. I thought there was something wrong with the tablet and bought a used one off eBay hoping it would come with 5.1.2. I love AOSP on these machines.
daniel3016 said:
My tablet just jumped from 5.3.2.1 to 5.3.3.0 in one day. I tried kingroot several times hoping it would work. It did not. I performed factory reset on it and signed into amazon. When i woke up it was at 5.4.0.0. My question is if a root exploit is found for 5.3.2.1 or 5.3.3.0 can it be rolled back? This all started from a bad SD card that kept resetting my old fire. I thought there was something wrong with the tablet and bought a used one off eBay hoping it would come with 5.1.2. I love AOSP on these machines.
Click to expand...
Click to collapse
If I recall correctly, 5.3.3.0 COULD be rolled back to 5.3.2.1. And 5.4 supposedly, or theoretically can be rolled back to 5.3.3. So theoretically, yes it could be rolled back to 5.3.2.1 from 5.4.
Hello guys. I really appreciate what is done on this forum. Keep on doing it, it really helps a lot of people out there. I would like an explanation on how to roll back from OS 5.3.3.0 to OS 5.3.2.1 on Amazon fire 7" 5th gen. Thanks
ulrngui said:
Hello guys. I really appreciate what is done on this forum. Keep on doing it, it really helps a lot of people out there. I would like an explanation on how to roll back from OS 5.3.3.0 to OS 5.3.2.1 on Amazon fire 7" 5th gen. Thanks
Click to expand...
Click to collapse
There is no benefit to be gained with that action. However, if you insist: https://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
Just for heck it i adb sideloaded 5.3.2.1 while on 5.4.0.0 just to see what happened and it appears to have downgraded just fine. I know there was nothing to be gained from this but I needed to know. This tablet is to be kept off of wifi
daniel3016 - how did you sideload to downgrade 5.4 to 5.3.2.1? Thanks
smolie701 said:
daniel3016 - how did you sideload to downgrade 5.4 to 5.3.2.1? Thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
daniel3016 said:
Just for heck it i adb sideloaded 5.3.2.1 while on 5.4.0.0 just to see what happened and it appears to have downgraded just fine. I know there was nothing to be gained from this but I needed to know. This tablet is to be kept off of wifi
Click to expand...
Click to collapse
Hey, do you have a link (or tips) to how you did this? I have 5.4.0.0 and the advice I'm getting is that this system version cannot be rooted or downgraded, that trying will brick it. You're the only one who seems to have had success. The follow-up link given by someone else (https://forum.xda-developers.com/ama...h-gen-t3285294) doesn't have a shred of info on 5.4.x.x.
I just downgraded to 5.3.2.1 from 5.4.0.0 i have never acheived root. You gain nothing by doing it. I did it just to see if i could. Hope that helps.
Mr2nSmith said:
Hey, do you have a link (or tips) to how you did this? I have 5.4.0.0 and the advice I'm getting is that this system version cannot be rooted or downgraded, that trying will brick it. You're the only one who seems to have had success. The follow-up link given by someone else (https://forum.xda-developers.com/ama...h-gen-t3285294) doesn't have a shred of info on 5.4.x.x.
Click to expand...
Click to collapse
Clarification: you can not downgrade from 5.4.x.x+ to a rootable version of FireOS as of the date of this post (5.3.1.0/5.3.2.0 are the highest rootable builds). Amazon updated the bootloader concurrent with delivery of FireOS 5.3.2.1; manually rolling back to a lower version will brick the device. At present there is not a method for downgrading FireOS independent of the bootloader on an unrooted device.
Davey126 said:
Clarification: you can not downgrade from 5.4.x.x+ to a rootable version of FireOS as of the date of this post (5.3.1.0/5.3.2.0 are the highest rootable builds). Amazon updated the bootloader concurrent with delivery of FireOS 5.3.2.1; manually rolling back to a lower version will brick the device. At present there is not a method for downgrading FireOS independent of the bootloader on an unrooted device.
Click to expand...
Click to collapse
To Clarify - Can I downgrade 5.4.4 to 5.3.2.1 Safely?
savvytechwinner said:
To Clarify - Can I downgrade 5.4.4 to 5.3.2.1 Safely?
Click to expand...
Click to collapse
Probably 'yes' based on a couple user reports. However, there is no benefit to offset the potential brick risk if the version of FireOS currently on your device has an incompatible bootloader. 5.3.2.1 can not be rooted so what's the point?
Davey126 said:
Probably 'yes' based on a couple user reports. However, there is no benefit to offset the potential brick risk if the version of FireOS currently on your device has an incompatible bootloader. 5.3.2.1 can not be rooted so what's the point?
Click to expand...
Click to collapse
I downgraded. I had the system updates uninstalled so have no clue if it worked but I downgraded anyways because root might be found in a different method and got patched? have no clue and no suspecting it. Just proving that dowgrading is safe from 5.4 to 5.3.2.1
savvytechwinner said:
I downgraded. I had the system updates uninstalled so have no clue if it worked but I downgraded anyways because root might be found in a different method and got patched? have no clue and no suspecting it. Just proving that dowgrading is safe from 5.4 to 5.3.2.1
Click to expand...
Click to collapse
savvytechwinner, Can you please link to the tutorial you followed in order to downgrade?
ormaoz said:
savvytechwinner, Can you please link to the tutorial you followed in order to downgrade?
Click to expand...
Click to collapse
I believe you can find the 5.3.2.1 software here. I believe all you have to do is place the .bin into the internal storage (SDcard) and boot into recovery to flash it. I'm not 100% certain though.
DragonFire1024 said:
I believe you can find the 5.3.2.1 software here. I believe all you have to do is place the .bin into the internal storage (SDcard) and boot into recovery to flash it. I'm not 100% certain though.
Click to expand...
Click to collapse
You download the 5.3.2.1.bin file from rootjunkysdl.com and adb sideload it
ormaoz said:
savvytechwinner, Can you please link to the tutorial you followed in order to downgrade?
Click to expand...
Click to collapse
DragonFire1024 said:
I believe you can find the 5.3.2.1 software here. I believe all you have to do is place the .bin into the internal storage (SDcard) and boot into recovery to flash it. I'm not 100% certain though.
Click to expand...
Click to collapse
savvytechwinner said:
You download the 5.3.2.1.bin file from rootjunkysdl.com and adb sideload it
Click to expand...
Click to collapse
...or from the forum index which contains a ton of information and resources that most choose to ignore.
Davey126 said:
...or from the forum index which contains a ton of information and resources that most choose to ignore.
Click to expand...
Click to collapse
Or just forget. Not used to the index material.
Hi can i rollback from 5.4.0.1 to 5.3.2.1 ? or to 5.4.0.0 !?
Edit. The the rollback from 5.4.0.1 to 5.3.2.1 has worked well .
Any news in the community about a 5.6.0.0 rollback?