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.
Good day to all and I do apologize if this post is not in the proper forum but I am limited to where I may post.
I have what I believe is a Kindle Fire HD 2 ? I do own and have rooted and cyanogenMODed my kindle fire 1st
gen, 2nd gen and my kindle fire HD, this one I believe is the HD 2 running version 11.3.2.3.2_user_323001620.
I have been a member here for sometime and have learned a lot and I very well may have stumbled across
something a few minutes ago. From what I gather this version kindle has not yet been rooted or at least that I can
find any proof of ( my apologies if I am wrong ). I was just tinkering with it and downloaded a root app from here
named Root_with_Restore_by_Bin4ry_v35 I also downloaded and installed the Kindle Fire HD 8.9 ADB
drivers from here also and downloaded a file called pwn.zip too.... Anyway....
Under Windows 7 these are my procedures....
1. Extracted pwn.zip to the z2root folder
2. Right clicked RunMe.bat and chose run as administrator
3. Chose option 0
4. Then chose option 0 again.
5. Then connected the kindle to the USB cord
6. Hit Enter and allowed Root_with_Restore_by_Bin4ry_v35 run it's course following the onscreen instructions
and it seems as tho I am rooted.
Again, I apologize if I am posting to the wrong forum and I am also sorry I do not have all the steps for instructions...
to be honest...Im about to piss myself ... Sorry
Can anyone else try this and confirm it please?
Take~Care!!!
screenshots
Sorry they are not the best pics.
hey there, can you please provide a link to the files you used to execute this root method??
i would love to try this on mine, as i'm running the same version.
however, there is an update pending, which i haven't gotten.. (user_324002520)
doe deer said:
hey there, can you please provide a link to the files you used to execute this root method??
i would love to try this on mine, as i'm running the same version.
however, there is an update pending, which i haven't gotten.. (user_324002520)
Click to expand...
Click to collapse
All Files Needed - MediaFire 40.65 mb
http://www.mediafire.com/download/4ir8e0assy831ci/all_files_needed.zip
PS!:.. I am still having a lot of issues getting twrp recovery etc...
I need to invest in a fastboot cable, I find no way to get this KF HD to boot into FB =(
I have rooted the KF 1st gen, 2nd gen and the hd1.. this one is only giving me fits trying to get to FB and a recovery.
As soon as I get a recovery on this beast I will be playing with some CyanogenMod or Hellfire Roms.... Im sure they can be used as is.
Please Kepp me informed... Tkank You & Take~Care! Tony.
thanks alot for your reply and upload, it is very appreciated
unfortunately, i'm not having any luck with this .bat...
when i open the runme.bat as adminstrator, and run option 0... i get alot of "this path cannot be specified" msgs and nothing is applied / changed... my kindle never restarts
however, when i DON'T run option 0 as adminstrator, simply as user.... i get a little further along in the automated process, but again, nothing is effected / restarted.
i've also tried option 2 and 4, and they actually got so far as to restart the kindle, however root has not been granted.
any help is greatly appreciated!
it should be noted that i uninstalled / replaced my previous kindle drivers with the provided 8.9 drivers before any of these root trials were carried out.
doe deer said:
thanks alot for your reply and upload, it is very appreciated
unfortunately, i'm not having any luck with this .bat...
when i open the runme.bat as adminstrator, and run option 0... i get alot of "this path cannot be specified" msgs and nothing is applied / changed... my kindle never restarts
however, when i DON'T run option 0 as adminstrator, simply as user.... i get a little further along in the automated process, but again, nothing is effected / restarted.
i've also tried option 2 and 4, and they actually got so far as to restart the kindle, however root has not been granted.
any help is greatly appreciated!
it should be noted that i uninstalled / replaced my previous kindle drivers with the provided 8.9 drivers before any of these root trials were carried out.[/QUOT]
Try picking option 0 then option 1 and see what that does... none of the options have done anything other than those 2.
I just done a factory reset to try to retrace my steps and make it further..I am sure 4 eyes are better that 2,
please let's stick together =)
Click to expand...
Click to collapse
[/QUOT]
Try picking option 0 then option 1 and see what that does... none of the options have done anything other than those 2.
/QUOTE]
hey there, glad to report that appears to have done the trick, however, i don't believe i ran the .bat as administrator as option 0 then 1 also give me "this path cannot be specified" etc etc errors...
anyhow, i opened the .bat once more as user, hit option 0, then 1... plugged in my kindle.... and i made it to a point in the process where i stalled / hung there for a bit, until i went into my kindle options, disabled, then re-enabled ADB interfacing.....at which point, the .bat script continued, and i rebooted.... happily, with root access / capabilities.
congrats to you for finding this man, and certainly my gratitude / thanks to you, i can now use my ps3 controller wirelessly through bluetooth.....
a question. how can i now disable auto kindle firmware updates so as to retain my root access?
oh no, while charging my kindle i seem to have updated to the latest firmware automatically, thus i no longer have access to root functions!!
currently on 11.3.2.4 user 324002520 as of now..
i've tried to root once more with the provided files but so far no luck, having tried options 0>0 and 0>1, both as administrator and user.
doe deer said:
oh no, while charging my kindle i seem to have updated to the latest firmware automatically, thus i no longer have access to root functions!!
currently on 11.3.2.4 user 324002520 as of now..
i've tried to root once more with the provided files but so far no luck, having tried options 0>0 and 0>1, both as administrator and user.
Click to expand...
Click to collapse
I for some reason am not having this update issue... Have you tried option 14 in the KindleFire First Aid program ?
http://forum.xda-developers.com/showpost.php?p=38435305&postcount=1072
rb2tfm said:
I for some reason am not having this update issue... Have you tried option 14 in the KindleFire First Aid program ?
http://forum.xda-developers.com/showpost.php?p=38435305&postcount=1072
Click to expand...
Click to collapse
They have a KFHD Soho 2013 not Tate. KFFA is not for the Soho. The link in my signature can help with this. Get ahold of the dev and ask for an updated firerooter.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Hi there,
Firstly I apologise, this post may be a little vague, as am having trouble getting the truth out of my son. I was wondering if anyone might be able to help me identify what the heck he has done to his Kindle Fire HD 7"
When you turn the device on, despite initially saying Kindle fire HD, this text is soon replaced with a boot screen animation that simply reads "DROID".
When you begin to use the Kindle there is a small carousel of apps over the larger carousel. Also when you rotate the screen to landscape it doesn't seem to reorientate the display and only shows the top half of the screen. It also seems to crash and won't come out of the lock screen.
I am guessing he has tried to either root it or flash a custom rom, he says he installed an app called root master? But cannot see how an app would grant root access?
We bought this for him as a Christmas present, and whilst am sorely tempted to tell him "tough" as he's obviously tried to do something without fully understanding what he's doing, I would like to be able to sort this as soon as I stop being cross.
So whilst I appreciate this is all a bit vague, does anyone recognise any symptoms, and have any insight into what he might have done and/or installed and is there any sure fire method to get this back for him?
A couple of questions:
-> Is it the 2012 version with the camera and HDMI output, or is it the 2013 version that has neither of these?
-> Can you access the settings and enable ADB?
-> Can you solder or are willing to shell out $10-$15 to fix this?
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
hi there,
Thanks for the reply.
We got it for him for Christmas 2012.
Can get to settings. I have enabled ADB (just to see if I could, and I can).
Does this mean I might not need a soldering iron?
Do not claim to be any sort of expert, so please assume no knowledge here.
But will carefully follow instructions if there are any.
Am hoping to be able to hand him back a working device when he's learnt his lesson.
Thanks again
I would suggest you to use the Kindle Fire First Aid if fastboot works. That way you can go totally stock. And a few more questions:
Do you have the Android SDK installed on your PC? If yes,try using "adb devices" to see if it recognizes the Kindle
Shut down the Kindle. Boot it up. Do you see an orange Kindle animation only or a blue animation?
I suggest you buy a factory adapter from Team BlackHat here if fastboot doesn't work.
PS: Don't be too cross on him. It's perfectly understandable if he wanted to flash a custom ROM. I ended up hating Amazon after realizing what they did to Android....
SafinWasi said:
I would suggest you to use the Kindle Fire First Aid if fastboot works. That way you can go totally stock.
Click to expand...
Click to collapse
Is this what is being described here?
http://forum.xda-developers.com/showthread.php?t=2096888
If so, I will have a look this evening..
I like the fact that it has "noob" in the post description.
Although I flashed a custom rom onto my Samsung Galaxy S2 a couple of years back (using ODIN) a lot of the instructions in this Kindle Fire section seem to be very confusing. I wish I'd known he was planning to do something like this, as I'd have read up on it for him (and, most likely warned him off, amazon look like they have locked down this tablet to a horrific degree)
SafinWasi said:
And a few more questions:
Do you have the Android SDK installed on your PC? If yes,try using "adb devices" to see if it recognizes the Kindle
Click to expand...
Click to collapse
Okay, that sounds a good first place to start. I don't think I have the SDK currently installed but I guess I can grab it again from google.
I take it if the SDK can "see" it we're halfway there?
Just to clarify:
The device is "quite" responsive.
It will boot up (although I cannot find anything on the internet about this boot animation that just draws the word "DROID" - if I could, I might be able to figure what he's tried to do at least) and you can sort of use it (although there are onscreen glitches as described above) and it freezes up when the screen locks (so you have to reboot every time it locks the screen). But, at least it's not totally D.O.A, I guess.
SafinWasi said:
[*]Shut down the Kindle. Boot it up. Do you see an orange Kindle animation only or a blue animation?
Click to expand...
Click to collapse
It does initially flash up Kindle..
I thought I had solved the problem with a factory reset last night (I'll admit for a second I cheered), but after initially showing Kindle Fire, it then starts going to this blue DROID animation..
SafinWasi said:
I suggest you buy a factory adapter from Team BlackHat here if fastboot doesn't work.
Click to expand...
Click to collapse
Okay, cool I take it this is step three if the Kindle Fire First Aid doesn't work?
SafinWasi said:
PS: Don't be too cross on him. It's perfectly understandable if he wanted to flash a custom ROM. I ended up hating Amazon after realizing what they did to Android....
Click to expand...
Click to collapse
I am a lot calmer today, am sorry that the first post was written in "Angry Dad" mode
I was just annoyed that he tried to deny doing anything to his device, and claimed it was "just an amazon update" (when it was obvious it wasn't).
This is why I am hoping to fix it for him, it was a Christmas present after all, and I would like to (eventually, not right away) hand him back a working Kindle device.
I just wish I wasn't flying so blind.
Thing is I'm not 100% sure he know's what he's done, I think he's just blindly followed a YouTube video or similar and he's ended up with this.
I really, really appreciate you guys taking the time to reply to my post.
Thanks so much for reading and responding.
silentbazz said:
Is this what is being described here?
http://forum.xda-developers.com/showthread.php?t=2096888
If so, I will have a look this evening..
I like the fact that it has "noob" in the post description.
Although I flashed a custom rom onto my Samsung Galaxy S2 a couple of years back (using ODIN) a lot of the instructions in this Kindle Fire section seem to be very confusing. I wish I'd known he was planning to do something like this, as I'd have read up on it for him (and, most likely warned him off, amazon look like they have locked down this tablet to a horrific degree)
Okay, that sounds a good first place to start. I don't think I have the SDK currently installed but I guess I can grab it again from google.
I take it if the SDK can "see" it we're halfway there?
Just to clarify:
The device is "quite" responsive.
It will boot up (although I cannot find anything on the internet about this boot animation that just draws the word "DROID" - if I could, I might be able to figure what he's tried to do at least) and you can sort of use it (although there are onscreen glitches as described above) and it freezes up when the screen locks (so you have to reboot every time it locks the screen). But, at least it's not totally D.O.A, I guess.
It does initially flash up Kindle..
I thought I had solved the problem with a factory reset last night (I'll admit for a second I cheered), but after initially showing Kindle Fire, it then starts going to this blue DROID animation..
Okay, cool I take it this is step three if the Kindle Fire First Aid doesn't work?
I am a lot calmer today, am sorry that the first post was written in "Angry Dad" mode
I was just annoyed that he tried to deny doing anything to his device, and claimed it was "just an amazon update" (when it was obvious it wasn't).
This is why I am hoping to fix it for him, it was a Christmas present after all, and I would like to (eventually, not right away) hand him back a working Kindle device.
I just wish I wasn't flying so blind.
Thing is I'm not 100% sure he know's what he's done, I think he's just blindly followed a YouTube video or similar and he's ended up with this.
I really, really appreciate you guys taking the time to reply to my post.
Thanks so much for reading and responding.
Click to expand...
Click to collapse
Okay,I'll guide you through a step-by-step tutorial to restore your Kindle.
Download and install the Android SDK. That is the first thing any Android modding guy must have. It provides you with the ADB and Fastboot executables which you're gonna need.
Download and install the Kindle Fire HD ADB drivers. You're gonna need them since the official Google drivers that came with the SDK are not supported by Amazon.
Modify your path variable. To do this,right-click on 'My Computer' and select properties. Click on "Advanced System Settings" and then "Environment Variables". At this point,you should copy the path to the tools and platform-tools folders of your SDK and paste them in the "path" system variable . If you want a video tutorial:http://www.youtube.com/watch?v=oaNM-lt_aHw
See if ADB and fastboot works. Open CMD from Run and type in ADB or fastboot. If it returns a lot of text,it's working.
Now type in:
Code:
fastboot -i 0x1949 getvar product
It'll return <waiting for device>
Turn off the Kindle and plug it in. If it boots into fastboot,you're good to go with KFFA
If it doesn't boot into fastboot,you'll have to buy a fastboot adapter or make one.
---------- Post added at 06:53 AM ---------- Previous post was at 06:51 AM ----------
Although I have no idea how he got the Droid animation....
SafinWasi said:
Although I have no idea how he got the Droid animation....
Click to expand...
Click to collapse
Okay, apparently, he went to this 1mobile market to get a one click root app.
I have not been able to find the app myself, but am very worried that he's been downloading apps from an unofficial app store.
The change to the boot animation seems to have been achieved using a Xposed app (that requires XBlast?). It was after installing this, and changing the boot animation that he says the Kindle started to behave weirdly.
Have not had the time yet to sit down and go through the instructions provided, thank you for those, I will set time aside at the weekend as I don't want to rush it.
At least now I know where the weird boot animation came from
I provide this info as a warning to others.
silentbazz said:
Okay, apparently, he went to this 1mobile market to get a one click root app.
I have not been able to find the app myself, but am very worried that he's been downloading apps from an unofficial app store.
The change to the boot animation seems to have been achieved using a Xposed app (that requires XBlast?). It was after installing this, and changing the boot animation that he says the Kindle started to behave weirdly.
Have not had the time yet to sit down and go through the instructions provided, thank you for those, I will set time aside at the weekend as I don't want to rush it.
At least now I know where the weird boot animation came from
I provide this info as a warning to others.
Click to expand...
Click to collapse
1mobile is an OK place to download apps from. You just have to make sure the dev is reputable. XBlast can mess a tablet up if you play to much with it.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
I agree. It's tricky,XBlast. Any progress?
Sent from my device running CyanogenMod 11
SafinWasi said:
I agree. It's tricky,XBlast. Any progress?
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Alas, not good..
Am stumbling at the first hurdle really, have installed the AndroidSDK all okay but am trying to add the Kindle Fire drivers into the SDK as per amazon's instructions here .
But the SDK they describe doesn't seem to match the SDK environment I have installed (I have version 23.0.0.1245622 of eclipse installed, which seems to have a different menu structure to the one amazon describe?) and whenever I try and get
Eclipse to access the URL amazon has told me to (http://kindle-sdk.s3.amazonaws.com/addon.xml) I get the message "No repository found at http://kindle-sdk.s3.amazonaws.com/addon.xml"
Am really not sure what I'm doing wrong..
silentbazz said:
Alas, not good..
Am stumbling at the first hurdle really, have installed the AndroidSDK all okay but am trying to add the Kindle Fire drivers into the SDK as per amazon's instructions here .
But the SDK they describe doesn't seem to match the SDK environment I have installed (I have version 23.0.0.1245622 of eclipse installed, which seems to have a different menu structure to the one amazon describe?) and whenever I try and get
Eclipse to access the URL amazon has told me to (http://kindle-sdk.s3.amazonaws.com/addon.xml) I get the message "No repository found at http://kindle-sdk.s3.amazonaws.com/addon.xml"
Am really not sure what I'm doing wrong..
Click to expand...
Click to collapse
Don't do that. Just download my Flasher and extract it. There is another zip inside,which has the drivers. Just install them normally.
Sent from my device running CyanogenMod 11
silentbazz said:
Alas, not good..
Am stumbling at the first hurdle really, have installed the AndroidSDK all okay but am trying to add the Kindle Fire drivers into the SDK as per amazon's instructions here .
But the SDK they describe doesn't seem to match the SDK environment I have installed (I have version 23.0.0.1245622 of eclipse installed, which seems to have a different menu structure to the one amazon describe?) and whenever I try and get
Eclipse to access the URL amazon has told me to (http://kindle-sdk.s3.amazonaws.com/addon.xml) I get the message "No repository found at http://kindle-sdk.s3.amazonaws.com/addon.xml"
Am really not sure what I'm doing wrong..
Click to expand...
Click to collapse
Hi! One click root app was probably called VROOT. VROOT is still not identified as safe as there may be malware, sorry :\ However if you have a FASTBOOT cable go on this website and you should be able to restore it without SDK.
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
by the way once choosing an "option" please wait for at least 20 minutes as restoring the device takes a long process.
silentbazz said:
Am really not sure what I'm doing wrong..
Click to expand...
Click to collapse
Your tablet still has fastboot access which means it's almost surely restorable. The flasher offered above will work and so will the System Restore Tool. You just run the bat and wait to be restored. Make sure your drivers are installed properly. Windows 8/7 64bit need to be put in test mode so your drivers will install right.
Windows is not going to let you do this until you disable device driver signature enforcement.
Disable device driver signature enforcement in Windows 7 read on. Windows 8 has different steps.
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.*
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."*
Note: This must be done on every bootup you want to install something not MS signed.*
B. For a more permanent solution.*
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.*
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now type these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.*
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers next time. To exit test mode follow steps 1,2 and 3 in part B of my writeup and type these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS*
bcdedit.exe -set TESTSIGNING OFF
Now restart computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
SafinWasi said:
Okay,I'll guide you through a step-by-step tutorial to restore your Kindle.
Download and install the Android SDK. That is the first thing any Android modding guy must have. It provides you with the ADB and Fastboot executables which you're gonna need.
Download and install the Kindle Fire HD ADB drivers. You're gonna need them since the official Google drivers that came with the SDK are not supported by Amazon.
Modify your path variable. To do this,right-click on 'My Computer' and select properties. Click on "Advanced System Settings" and then "Environment Variables". At this point,you should copy the path to the tools and platform-tools folders of your SDK and paste them in the "path" system variable . If you want a video tutorial:http://www.youtube.com/watch?v=oaNM-lt_aHw
See if ADB and fastboot works. Open CMD from Run and type in ADB or fastboot. If it returns a lot of text,it's working.
Now type in:
Code:
fastboot -i 0x1949 getvar product
It'll return <waiting for device>
Turn off the Kindle and plug it in. If it boots into fastboot,you're good to go with KFFA
If it doesn't boot into fastboot,you'll have to buy a fastboot adapter or make one.
.
Click to expand...
Click to collapse
Okay, I got the amazon drivers installed on my machine, and had fastboot and adb working from the command prompt after adding all of the paths to the PATH environment setting.
I typed in:
Code:
fastboot -i 0x1949 getvar product
and I got the prompt <waiting for device>
However when I attach the device, it just boots (with the weird droid animation) - I cannot see anything to say that it has fastbooted. Does it display any different?
I have also typed adb devices and I don't think my PC is seeing the Kindle Fire HD as I get no devices shown in the List of Devices?
Does this mean I need a fastboot cable?
Would installing cyanogenmod on this be an option now? Or would that just make matters worse at this stage?
++ EDIT ++
Actually, uninstalled and reinstalled amazon adb drivers, and retyped:
Code:
adb devices
and it output:
D025A0A0241220KP device
so tried the fastboot -i 0x1949 getvar product command again, but still the device booted normally
SafinWasi said:
Don't do that. Just download my Flasher and extract it. There is another zip inside,which has the drivers. Just install them normally.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
By the way just wanted to say thanks for providing the Flasher.
Amazon drivers extracted and installed like a charm (once I allowed them to install to the default location)
silentbazz said:
Does this mean I need a fastboot cable?
Click to expand...
Click to collapse
The only time you don't need one is if you can access the OS and you have functioning root. If you don't have this then you must have a fastboot cable. If you have a Motorola cord laying around try that.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
The only time you don't need one is if you can access the OS and you have functioning root. If you don't have this then you must have a fastboot cable. If you have a Motorola cord laying around try that.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Ahh okay, I understood that I might be able to get the device to enter fastboot without a cable.
I must have read this wrong.
Okay, as I am not in the United States I am guessing eBay.co.uk is my best option?
Will something like this do the trick?
silentbazz said:
Ahh okay, I understood that I might be able to get the device to enter fastboot without a cable.
I must have read this wrong.
Okay, as I am not in the United States I am guessing eBay.co.uk is my best option?
Will something like this do the trick?
Click to expand...
Click to collapse
Should work fine.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
Should work fine.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Okay, great, have got one ordered, so will hopefully be able to get this sorted soon.
A sincere thanks to everyone who has offered sage advice above.
Some ace tips here, hopefully I'll get this sorted for him
Thanks again!!!!
silentbazz said:
Okay, great, have got one ordered, so will hopefully be able to get this sorted soon.
A sincere thanks to everyone who has offered sage advice above.
Some ace tips here, hopefully I'll get this sorted for him
Thanks again!!!!
Click to expand...
Click to collapse
You're welcome. Keep us updated.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
cam30era said:
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Click to expand...
Click to collapse
Hi cam30era, I tried that but it didn't help. I didn't try it after using Wug's toolkit so it's worth another shot.
Xplicit84 said:
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
Click to expand...
Click to collapse
Hi Xplicit84, I used the Wugs toolkit provided in the NRT to install the proper drivers (it worked fantastic, by the way... mad props to Wug). That didn't help unfortunately.
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
apristel said:
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
Click to expand...
Click to collapse
Hi apristel, yup, tried that too, as I had read that perhaps there may be an issue with USB 3.0 ports. I don't think I have USB 3.0 ports (my laptop is a 2012-era Alienware M17x R3) but I tried a different port for the sake of doing it and it didn't make a difference.
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
teddyearp said:
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
Click to expand...
Click to collapse
Hi teddyearp, I downloaded it from a link on Droid-Life. I don't remember the exact name of the file because I renamed it to something much shorter, but here's where I got it from -
http://www.droid-life.com/2015/03/1...s-for-nexus-devices-4-5-6-7-9-10/#more-163271
Edit - Here's the direct link (the one I used) - http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Any luck, having the same problem and it's driving me nuts.
Mongo23ny said:
Any luck, having the same problem and it's driving me nuts.
Click to expand...
Click to collapse
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
apristel said:
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
Click to expand...
Click to collapse
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Mongo23ny said:
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Click to expand...
Click to collapse
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
apristel said:
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Click to expand...
Click to collapse
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Gage_Hero said:
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
Click to expand...
Click to collapse
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Mongo23ny said:
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Click to expand...
Click to collapse
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
How do I install it properly? I got rid of some old drivers as well
Mongo23ny said:
How do I install it properly? I got rid of some old drivers as well
Click to expand...
Click to collapse
Well you can just change them in the device manager.
I'm willing to use team viewer and show you how. (you'd see everything i do) It's hard to write it out for me right now..just had hand surgery this morning and my hand is still completely numb. If you want to download this and run it http://download.teamviewer.com/download/TeamViewerQS_en.exe
PM me the id and password and i'll connect up and show ya. Just so you know, it'd be a one time thing connecting, your password changes everytime and you'd have to have that running to connect. I own a computer repair store and use it frequently.
apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Lucky Armpit said:
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Click to expand...
Click to collapse
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
apristel said:
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
Click to expand...
Click to collapse
PM sent. Thanks
Brand new nexus 6, build #LMY47E, running Android 5.1
OS Windows 7 Home Premium 64-bit SP1
My issue is when I plug the device into the computer, regardless of USB port, using the brand new cable provided by Motorola. If I leave USB Debugging off, the phone gets recognized and it says it is working properly. As soon as I turn on USB debugging, the computer attempts to download the drivers, but it always fails on adb interface. MTP gets installed, and Nexus 6 gets installed, but never adb.
What do I do?
a.demarco said:
Brand new nexus 6, build #LMY47E
OS Windows 7 Home Premium 64-bit SP1
My issue is when I plug the device into the computer, regardless of USB port, using the brand new cable provided by Motorola. If I leave USB Debugging off, the phone gets recognized and it says it is working properly. As soon as I turn on USB debugging, the computer attempts to download the drivers, but it always fails on adb interface. MTP gets installed, and Nexus 6 gets installed, but never adb.
What do I do?
Click to expand...
Click to collapse
Have you downloaded the Android SDK? If not, here it is:
https://developer.android.com/sdk/index.html
Once downloaded, you don't need all of the components. Just install platform-tools, and Google drivers. You may have to uninstall any drivers that aren't for your nexus 6. You may also have to point your PC to the Google drivers via device manager. :victory:
Evolution_Freak said:
Have you downloaded the Android SDK? If not, here it is:
https://developer.android.com/sdk/index.html
Once downloaded, you don't need all of the components. Just install platform-tools, and Google drivers. You may have to uninstall any drivers that aren't for your nexus 6. You may also have to point your PC to the Google drivers via device manager. :victory:
Click to expand...
Click to collapse
Yes, I downloaded Android SDK, and installed the 4 packages it said to. I will see if I can get it to work through device manager, thanks!
a.demarco said:
Yes, I downloaded Android SDK, and installed the 4 packages it said to. I will see if I can get it to work through device manager, thanks!
Click to expand...
Click to collapse
Yeah, I knew there were a couple other SDK components needed but I couldn't think of them off the top of my head and also get my kids ready for bed at the same time. Lol!! Glad you're on the right track! :good:
a.demarco said:
Yes, I downloaded Android SDK, and installed the 4 packages it said to. I will see if I can get it to work through device manager, thanks!
Click to expand...
Click to collapse
Try turning the device off and then boot into fastboot (Pwr + Vol down) then plug the phone into the computer. You can also install Wug's Toolkit at the link below:
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
slimc84 said:
Try turning the device off and then boot into fastboot (Pwr + Vol down) then plug the phone into the computer. You can also install Wug's Toolkit at the link below:
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
I will try turning it off and booting into fastboot, thanks for that! I am trying to avoid using toolkits, I enjoy the learning process.
a.demarco said:
I will try turning it off and booting into fastboot, thanks for that! I am trying to avoid using toolkits, I enjoy the learning process.
Click to expand...
Click to collapse
I was recommending the toolkit just to install the drivers. I too enjoy the learning process and familiarizing myself with adb. Just in case I need it one day.
slimc84 said:
I was recommending the toolkit just to install the drivers. I too enjoy the learning process and familiarizing myself with adb. Just in case I need it one day.
Click to expand...
Click to collapse
Ah, gotcha... Had no idea the drivers were in the toolkits!
a.demarco said:
Ah, gotcha... Had no idea the drivers were in the toolkits!
Click to expand...
Click to collapse
Are you still having driver issues or did you get it sorted out? Just curious.
Evolution_Freak said:
Are you still having driver issues or did you get it sorted out? Just curious.
Click to expand...
Click to collapse
Haven't tried it again since last night... Doing some high pressure ductile iron underground water piping all day today, will try later tonight.
a.demarco said:
Haven't tried it again since last night... Doing some high pressure ductile iron underground water piping all day today, will try later tonight.
Click to expand...
Click to collapse
Yes, priorities. If you have any questions later, don't hesitate to ask.
Download the nexus toolkit and follow the instructions given in it to install the drivers, you don't even need the android sdk,
a.demarco said:
OS Windows 7 Home Premium 64-bit SP1
...
What do I do?
Click to expand...
Click to collapse
Delete that crap and install a real operating system.
doitright said:
Delete that crap and install a real operating system.
Click to expand...
Click to collapse
And what in your opinion is a real operating system?