Related
Q&A for [TOOL] HDX ToolKit v0.94
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
adb
Successfully rooted with adb!
Where is the folder of adb? I want to use adb driver in console.
---------- Post added at 07:26 AM ---------- Previous post was at 07:14 AM ----------
Problem solved. C:\Users\%username%\AppData\Local\Temp\afolder
Cannot detect device
Hi, I tried to install the ADB driver but it never shows as "Device Updated".
Also, when I tried to do Towelroot or anything else afterwards, the computer can't seem to detect the Kindle Fire HDX.
I have already enabled the ADB and Apps from Unknown Source. Please help.
Thanks and regards
Fire OS 4.5
I just bought my 4th Gen HDX 8.9 and I am guessing the Fire 4.5 version isn't supported yet by your tool? I also can't seem to find anywhere it states the long form software version running. I did try running through the various steps and I wasn't able to get KFHDX to see my device properly. Keeps saying waiting for device. Any idea or anything I can do to help speed up the rooting available for this version?
KFHDX 8.9 (2014 version) root-ability?
I just got 2 KFHDX 8.9s, which are the latest 2014 versions. I doubt this model is still called "Apollo", does anyone know?
In any case, it arrived on FireOS 4.5. I don't see anywhere on this forum that this can be rooted... Can it? Anyone know?
Thanks.
Update of KFDX root kit
Thanks for the update. Just need to know why the files from the main and mirror sites are different. The one from the main site has a "zip.exe" extension while the one from the mirror site is a regular "zip" file. The first was flagged by AVG as a threat while there was no problem with the one from the mirror site.
lennV said:
Thanks for the update. Just need to know why the files from the main and mirror sites are different. The one from the main site has a "zip.exe" extension while the one from the mirror site is a regular "zip" file. The first was flagged by AVG as a threat while there was no problem with the one from the mirror site.
Click to expand...
Click to collapse
The files are not different you clicked on one of dev-host's ads. I'll change the main host. I use ad-blocker and don't see any ads. Sorry .
Much appreciated
Faznx92 said:
The files are not different you clicked on one of dev-host's ads. I'll change the main host. I use ad-blocker and don't see any ads. Sorry .
Click to expand...
Click to collapse
No problem. Thanks for the super fast clarification!
Trying to root, device not found
Just got KFHDX7, updated to 13.3.2.5 manually, now trying to root using 0.95 ToolKit. I already had ADB installed from rooting previous KFHD7, but unistalled and reinstalled using the ToolKit and via latest post from OP. Try to root via #1 and it says device not found - waiting for device - . I can see the Kindle on my computer (Windows 8) as I was able to manually update. I've enablde ADB and apps from unknown sources. See attached for screen showing install of ADB via ToolKit and error trying to root. Sometimes it doesn't show the * daemon lines.
Thanks in advance for your help!
Update 11/13: Must be a Win8 / ADB issue. I was able to root and disable OTA using my wifes Win7 laptop and it worked just fine. Also the confirmation text for ADB install matched the tutorials vs my screenshot. Still interested to know if anyone has been able to get this to work with Win8.
Question
So if I were to use this could this root my kindle fire hdx OS 4.1.1?
Leafman said:
So if I were to use this could this root my kindle fire hdx OS 4.1.1?
Click to expand...
Click to collapse
No. There's currently no method to root 4.1.1.
root a new hdx 7 with 13.3.1.0
Hello,
i just got my new hdx 7 today and wanted to know what i should do first in order to root successfully.
1) should i root first, before i sign in with my account on that hdx and before i configure my wlan?
2) or should i first register it on my name, configure wlan, get an software update ota and finally try to root?
in advance thanks for you replies.
best regards,
mika
@big_mika:
I would root first and disable the OTA. No one needs the ****ty fireOS updates. get root, install xposed, good launcher and enjoy a good android feeling
I'm on version 13.3.0.0 on my kindle after my kindle updated to 13.3.2.5. I flashed the 13.3.1.0 but it shows every time the 13.3.0.0
Now my question: which toolkit should i use and it is recommended to change the build.prop settings and flash another time?
If you need some screenshots or a deeper explanation of the process i will post it.
unfortunately i failed...
@ taette: thanks for your reply but unfortunately i failed and now i am on os 4.5.1
so, if anybody got an idea how to root fire hdx 7" with fire os 4.5.1 just let me know
thank you very much.
Rooting Kindle 7 HDX (13.3.2.5) - possible?
Hi everyone,
Can't post to the appropriate thread due to being new here...
Just got a brand new Kindle for my son yesterday, but don't feel like re-purchasing his games from Google Play. Can it be rooted? It's not ver 14 yet, but after all instructions from thread http://forum.xda-developers.com/showthread.php?t=2665683 I get stuck on "waiting for device".
Thanks!
Need help on rooting process Kindle Fire HDX 7"
Okay. So I am thinking of getting a 64gb Kindle Fire HDX 7", but I want to root it so i can get google play. I know about towelroot and all that but I have seen that it doesn't work on the new update. So what would I have to do with the updates and such when I get my device so I can properly root it to get Google Play Services and all that.
ImmaFatJesus said:
Okay. So I am thinking of getting a 64gb Kindle Fire HDX 7", but I want to root it so i can get google play. I know about towelroot and all that but I have seen that it doesn't work on the new update. So what would I have to do with the updates and such when I get my device so I can properly root it to get Google Play Services and all that.
Click to expand...
Click to collapse
Since you seem new, I don't recommend this device for you. If you want a tablet and not the risk, buy an Ipadeek or a different tablet. This is a very nice device for people who are already on the rooted versions, people who like the fireos designeek, people who have prime and wanted a powerful device, or people who are side-loading everything from the play store. The hdx is a powerful tablet waiting to be unleashed but unless your ready to deal with a few headaches then don't. Many people bought this device but the potential for it is in the future. As of now you will need to deal with the current state. I recommend giving this a read.
No root access on any version past X.3.2.6 as of typing this. You can give it a shot at your version number. Like I said, know what you're buying first, rethink it over 2 times after that.
big_mika said:
@ taette: thanks for your reply but unfortunately i failed and now i am on os 4.5.1
so, if anybody got an idea how to root fire hdx 7" with fire os 4.5.1 just let me know
thank you very much.
Click to expand...
Click to collapse
It is not possible to Root the latest Updates... So the only solution is Rollback to Fire OS 3... check out this thread... http://forum.xda-developers.com/showthread.php?t=2946946
Sent from my KFTHWI using XDA Free mobile app
I can't find instructions :\
I tried rooting it with your toolkit but all it says is "device not found".
It's plugged in, ADB is activated and I just installed ADB driver. But still can't be found.
Tried Number 1 and 2 of your toolkit with "y" and "y"
HDX toolkit with 3.2.8
Hi,
anyone tried HDX toolkit with 3.2.8.
My HDX 7 was downgraded from 4.2.5 to 3.2.8 today and now I think about routing and installing play store etc.
Thanks, Stef.
(sorry for posting initially in the wrong thread)
I'm on a Kindle Fire HDX 7" that originally ran GGOW's older roms and safestrap.
I am now trying to put CM12 on the unit and have brought it back to factory specs.
I am version 3.2.5 firmware
I have tried to downgrade by placing older version firmwares on the kindle root and running the manual update.....this leads to 'verify failed' error.
I have been reading this site for 2 weeks to find the proper method for downgrading and haven't been able to accomplish it yet.
I am on a Mac, not Windows.
Reaching out to the community in general, I've tried to help myself and not bother anyone, I'm not succeeding.
Thanks for your generosity beforehand.
-John
Follow the instructions in this post: http://forum.xda-developers.com/showthread.php?p=55759790
EncryptedCurse said:
Follow the instructions in this post: http://forum.xda-developers.com/showthread.php?p=55759790
Click to expand...
Click to collapse
.bat file = WINDOWS
But at least we're getting somewhere, thank you!
johnwaters said:
I'm on a Kindle Fire HDX 7" that originally ran GGOW's older roms and safestrap.
I am now trying to put CM12 on the unit and have brought it back to factory specs.
I am version 3.2.5 firmware
I have tried to downgrade by placing older version firmwares on the kindle root and running the manual update.....this leads to 'verify failed' error.
I have been reading this site for 2 weeks to find the proper method for downgrading and haven't been able to accomplish it yet.
I am on a Mac, not Windows.
Reaching out to the community in general, I've tried to help myself and not bother anyone, I'm not succeeding.
Thanks for your generosity beforehand.
-John
Click to expand...
Click to collapse
Hi John, sorry for your troubles. See link provided by EncryptedCurse. Some thoughts:
- make sure you have a valid update-kindle-13.3.1.0_user_310079820.bin. Download it again. Look for a way to verify the MD5 both on your HDX (Hash Droid works) and on your Mac. MD5=0F2BC5278C057E7A6B4823B0F68D0727
- make sure OTA is reenabled following the same process/procedure used to disable (obviously turn off WiFi and remove all profiles)
- look through the batch file using a text editor. You are probably going to have to issue the ADB commands manually. But you're probably beyond that by now ...
- you may want to consider manually upgrading to 3.2.6 (if it takes) and then rolling back. Point of this excercise to to possibly repair any components that may have been altered while bringing it back to factory specs. There's some risk in this approach; need to think/talk through it.
Sorry if none of the above seems very helpful. Not really sure what's going on based on the symptoms. Hopefully someone else chimes in with a better solution.
Davey126 said:
Hi John, sorry for your troubles. See link provided by EncryptedCurse. Some thoughts:
- make sure you have a valid update-kindle-13.3.1.0_user_310079820.bin. Download it again. Look for a way to verify the MD5 both on your HDX (Hash Droid works) and on your Mac. MD5=0F2BC5278C057E7A6B4823B0F68D0727
- make sure OTA is reenabled following the same process/procedure used to disable (obviously turn off WiFi and remove all profiles)
- look through the batch file using a text editor. You are probably going to have to issue the ADB commands manually. But you're probably beyond that by now ...
- you may want to consider manually upgrading to 3.2.6 (if it takes) and then rolling back. Point of this excercise to to possibly repair any components that may have been altered while bringing it back to factory specs. There's some risk in this approach; need to think/talk through it.
Sorry if none of the above seems very helpful. Not really sure what's going on based on the symptoms. Hopefully someone else chimes in with a better solution.
Click to expand...
Click to collapse
Actually I'm just glad anybody responded at this point. I've done this so many times and am not a noob or a layman to the process, I just feel like one right now. I will go over everything you have pointed out with a fine-toothed comb. Again, thanks for your reply and suggestions, they are HIGHLY appreciated.
johnwaters said:
Actually I'm just glad anybody responded at this point. I've done this so many times and am not a noob or a layman to the process, I just feel like one right now. I will go over everything you have pointed out with a fine-toothed comb. Again, thanks for your reply and suggestions, they are HIGHLY appreciated.
Click to expand...
Click to collapse
We have all been there at some point. I appreciate the work done prior to reaching out; so many come begging for help without making an effort to help themselves. As a double check, make sure you are following the rollback procedure for 3.2.5-3.2.6 vs 3.2.4. If you are messing with build.prop directly you got the wrong procedure.
Davey126 said:
We have all been there at some point. I appreciate the work done prior to reaching out; so many come begging for help without making an effort to help themselves. As a double check, make sure you are following the rollback procedure for 3.2.5-3.2.6 vs 3.2.4. If you are messing with build.prop directly you got the wrong procedure.
Click to expand...
Click to collapse
Hi Davey and John,
Not having done this I don't have any real world experience, but could it be that the permissions need to be changed?
see post #36 here
Regards,
Kico
johnwaters said:
.bat file = WINDOWS
But at least we're getting somewhere, thank you!
Click to expand...
Click to collapse
You can always use a virtual machine or Wine.
On a side note, the script itself is adaptable for OS X, as it's really just executing a few ADB commands.
I'm not exactly sure what the Mac equivalent for 7z.exe would be, but all it does is extract a few files from the stock image, which can be done manually.
kico42 said:
... could it be that the permissions need to be changed?
see post #36 here
Click to expand...
Click to collapse
Yes, quite possible. I'm hoping that isn't the case as build.prop should not have been touched. If permissions do turn out to be the problem then it would be best if someone else helps with the solution. I know just enough about Android permissions to be dangerous ... certainly not confident enough to guide another given the disastrous consequences of screwing it up. Also possible permissions on the bin file are farkled ... but that seems very unlikely and easily remedied by deleting & recopying the bin file.
EncryptedCurse said:
You can always use a virtual machine or Wine.
On a side note, the script itself is adaptable for OS X, as it's really just executing a few ADB commands.
I'm not exactly sure what the Mac equivalent for 7z.exe would be, but all it does is extract a few files from the stock image, which can be done manually.
Click to expand...
Click to collapse
In the process of building a Windows VM right now. Again, thank you for all the help. This is the best community.
I make this post at 8PM and upgrade is completed 11pm.
THANK YOU XDA.
Hey guys ive got a hdx 7' RUNNING FIRE OS 3.2.4 everything i have been reading is saying that this version is somewhat unique in that there are a few roms availible mostly from safestrapp but most are not, twrp requires 3.2.3 and earlier as well as the bootloader unlock procedure. Can anyone point me in the direction on how to downgrade to one of the earlier versions. Currently i am rooted, ota disabled via: hdxtookit, i had safestrapp and a asop rom installed but was getting google play services stopped working error messages and restored to factory because i havent used the kindle in a year. Anyways i'm looking to get back into it and got cm 12.1 on my sgs3 and wanted to get something similar but keep runninginto problems with my version fire os. So just need a quick link to a roll back procedure in english and i should be able to do the rest from unlock - twrp - roms etc. I've been searching off and on the past few weeks but do not find anything definitive so i decided to finally ask to get an answer thanks for any and all help.
131 views no replies can anyone guide me to a solution?
rbkelley89 said:
131 views no replies can anyone guide me to a solution?
Click to expand...
Click to collapse
So basicaly for unlock BL and real TWRP you need have FW between x.3.1.0 and x.3.2.3:
Depending on your computer skills rollback can be achieved easy (or not).
Guide in english? Here, but you must mess with build.prop and on hdx especialy its really dangerous procedure - if you made simple mistake, it could be your last with that device and deadly for it for sure.
Sorry, I will not guide you through the process, if you feel you are lost, you can ask davey126 for help, but he answered this type of question soo many times . . . you can try read his posts before you ask him, there is high posibility he answered it somewhere...
jeryll said:
So basicaly for unlock BL and real TWRP you need have FW between x.3.1.0 and x.3.2.3:
Depending on your computer skills rollback can be achieved easy (or not).
Guide in english? Here, but you must mess with build.prop and on hdx especialy its really dangerous procedure - if you made simple mistake, it could be your last with that device and deadly for it for sure.
Sorry, I will not guide you through the process, if you feel you are lost, you can ask davey126 for help, but he answered this type of question soo many times . . . you can try read his posts before you ask him, there is high posibility he answered it somewhere...
Click to expand...
Click to collapse
@jeryll is spot on. There are a ton of helpful posts from a variety of authors that could get you started. This one comes to mind although there are many others. Lots of folks here are happy to answer targeted questions but you have to do your homework first. Read (and read some more), go slow, stop and post a question if unsure, don't take chances. Good luck.
Random thoughts:
- I strongly encourage upgrading to 13.3.2.5 or 13.3.2.6 prior to rolling back to 13.3.1.0. Lower risk and clears out 'crud' that could ruin your day.
- Use HDX toolkit to block/unblock OTA. Don't mess with any other technique; bad day follows.
- Once OTA is unblocked stay off WiFi. Period. Do transfer/installs via tether. Belt-and-suspenders types engage airplane mode and delete existing WiFi profiles too.
- Double check every action before executing. Stop and ask questions if unsure. Juggling babies is safer than taking a wrong turn (ok ... maybe that's a bit extreme).
- Many guides suggest bootloader unlocking before installing TWRP recovery. My comfort meter goes the opposite way. Your call. There are decent arguments for both approaches.
Davey126 said:
@jeryll is spot on. There are a ton of helpful posts from a variety of authors that could get you started. This one comes to mind although there are many others. Lots of folks here are happy to answer targeted questions but you have to do your homework first. Read (and read some more), go slow, stop and post a question if unsure, don't take chances. Good luck.
Random thoughts:
- I strongly encourage upgrading to 13.3.2.5 or 13.3.2.6 prior to rolling back to 13.3.1.0. Lower risk and clears out 'crud' that could ruin your day.
- Use HDX toolkit to block/unblock OTA. Don't mess with any other technique; bad day follows.
- Once OTA is unblocked stay off WiFi. Period. Do transfer/installs via tether. Belt-and-suspenders types engage airplane mode and delete existing WiFi profiles too.
- Double check every action before executing. Stop and ask questions if unsure. Juggling babies is safer than taking a wrong turn (ok ... maybe that's a bit extreme).
- Many guides suggest bootloader unlocking before installing TWRP recovery. My comfort meter goes the opposite way. Your call. There are decent arguments for both approaches.
Click to expand...
Click to collapse
How can I upgrade to 3.2.5 or 6. I believe I blocked ota it's been so lo.g ago I searched.for.the files and didn't see them anywhere so I assume it's still active even after factory restoration. And it's possible to twrp without unlocked boot loader? I didn't know that. What are the pros and cons. I'm not a dev so I went need to play around with much just want to rid of fire os and use a cm or nexus. If I can do that safety id LOVE that but still willing to try the adk route. Thanks for the info guys.
rbkelley89 said:
How can I upgrade to 3.2.5 or 6. I believe I blocked ota it's been so lo.g ago I searched.for.the files and didn't see them anywhere so I assume it's still active even after factory restoration. And it's possible to twrp without unlocked boot loader? I didn't know that. What are the pros and cons. I'm not a dev so I went need to play around with much just want to rid of fire os and use a cm or nexus. If I can do that safety id LOVE that but still willing to try the adk route. Thanks for the info guys.
Click to expand...
Click to collapse
Locate HDX toolkit in the Android Development thread and try to remove the OTA block that way. Keep WiFi off or you might receive an unwanted update.
Although not recommended twrp can be installed with a locked bootloader.
Travelling this week so can't get into more detail. Suggest you keep reading. Don't do stuff unless you are absolutely confident in your skills, knowledge, risks and expected outcome(s). Post questions. Many folks willing to help if you have done your homework. Sorry for brevity ...
Yes, be ESPECIALLY careful with build.prop. I learned this the hard way. They is nothing like Odin for Samsung that can save you.
XxD34THxX said:
Yes, be ESPECIALLY careful with build.prop. I learned this the hard way. They is nothing like Odin for Samsung that can save you.
Click to expand...
Click to collapse
The path I am suggesting does not involve modifying build.prop.
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Cl4ncy said:
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Click to expand...
Click to collapse
Nice finding, I absolutely forgot that this existed, of course he can use that thread with rollback images to downgrade to x.3.1.0! Then he can install TWRP etc... (as I did in the past - proof below )
jeryll said:
Thank you sir, successfully rolled back to 14.3.1.0, installed TWRP 2.8.1.0 and now I will play a little with TWRP
Click to expand...
Click to collapse
Cl4ncy said:
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Click to expand...
Click to collapse
Nice find! I had seen that post (long ago) but the significance never set in for Safestrap v3 users with FireOS xx.3.2.4 in the stock slot. Even if not rocking SS it is probably easier (and definitely a lot safer) to install SS vs rolling up just to roll back or messing with build.prop.
The OTA block could still be a problem as the @ggow's procedure still involves Amazon's native update mechanism.
Edit: Disregard OTA comment as modified 3.2.4 goes on first and should restore OTA capability (more importantly the ability to detect and process FireOS bin files in the appropriate location).
I upgraded from 13.3.2.4 to 13.3.2.5 and edited build.prop, so now my version shows 13.3.0.9. I downloaded 13.3.1.0 rom from Amazon server. When updating I always received the following error message "Unable to complete update because the update file is not valid. Please try downloading the file again" (I tried downloading 13.3.1.0 at least 5 times, but none of the downloaded file works). I suspect that something goes wrong with the rom file on Amazon server.
Anybody can help direct me to a non-amazon site or upload your working file to somewhere I can download from?
Thank you very much.
Davey126 said:
Nice find! I had seen that post (long ago) but the significance never set in for Safestrap v3 users with FireOS xx.3.2.4 in the stock slot. Even if not rocking SS it is probably easier (and definitely a lot safer) to install SS vs rolling up just to roll back or messing with build.prop.
The OTA block could still be a problem as the @ggow's procedure still involves Amazon's native update mechanism.
Edit: Disregard OTA comment as modified 3.2.4 goes on first and should restore OTA capability (more importantly the ability to detect and process FireOS bin files in the appropriate location).
Click to expand...
Click to collapse
pquan2009 said:
I upgraded from 13.3.2.4 to 13.3.2.5 and edited build.prop, so now my version shows 13.3.0.9. I downloaded 13.3.1.0 rom from Amazon server. When updating I always received the following error message "Unable to complete update because the update file is not valid. Please try downloading the file again" (I tried downloading 13.3.1.0 at least 5 times, but none of the downloaded file works). I suspect that something goes wrong with the rom file on Amazon server.
Anybody can help direct me to a non-amazon site or upload your working file to somewhere I can download from?
Thank you very much.
Click to expand...
Click to collapse
AFAIK after upgrading to x.3.2.5(or 6) you cant use downgrading via editing build.prop anymore (thanks to Amazon), check this thread for more info.
IF you decide to take further actions PLEASE READ INSTRUCTIONS CAREFULLY, so far you are lucky you didnt brick your kindle.
jeryll said:
AFAIK after upgrading to x.3.2.5(or 6) you cant use downgrading via editing build.prop anymore (thanks to Amazon), check this thread for more info.
IF you decide to take further actions PLEASE READ INSTRUCTIONS CAREFULLY, so far you are lucky you didnt brick your kindle.
Click to expand...
Click to collapse
if i go this route which looks relatively easy do i end up deleting safestrap because i thought twrp doesnt work with it installed? and which safestrap do i install ss 3.72 ... download links are down l?
rbkelley89 said:
if i go this route which looks relatively easy do i end up deleting safestrap because i thought twrp doesnt work with it installed? and which safestrap do i install ss 3.72 ... download links are down l?
Click to expand...
Click to collapse
Assuming you are on 13.3.2.4 (must be that version) you need Safestrap v3.75 b02 for Thor (here). See Safestrap OP for additional information on installing/configuring Safestrap. Or follow part 1-2 of this guide. You do not need to create secondary slots as you will be overwriting FireOS in the Stock ROM Slot. This obviously dangerous. If something goes wrong you could be left with an unbootable device. Make a backup of your current environment from Safestrap recovery before flashing the rollback file. Note rolling back to 3.1.0 is a two step process. Be sure you understand these instructions and have the correct files. Ask questions if unsure.
After you have successfully rolled back to 3.1.0 you should uninstall safestrap before flashing native twrp, bumping your bootloader to 3.2.3 and then unlocking. Alternatively, you can work on bootloader unlocking first while Safestrap is installed which will offer more robust recovery capabilities should something go wrong in subsequent steps.
Davey126 said:
Assuming you are on 13.3.2.4 (must be that version) you need Safestrap v3.75 b02 for Thor (here). See Safestrap OP for additional information on installing/configuring Safestrap. Or follow part 1-2 of this guide. You do not need to create secondary slots as you will be overwriting FireOS in the Stock ROM Slot. This obviously dangerous. If something goes wrong you could be left with an unbootable device. Make a backup of your current environment from Safestrap recovery before flashing the rollback file. Note rolling back to 3.1.0 is a two step process. Be sure you understand these instructions and have the correct files. Ask questions if unsure.
After you have successfully rolled back to 3.1.0 you should uninstall safestrap before flashing native twrp, bumping your bootloader to 3.2.3 and then unlocking. Alternatively, you can work on bootloader unlocking first while Safestrap is installed which will offer more robust recovery capabilities should something go wrong in subsequent steps.
Click to expand...
Click to collapse
thank you so much for the walk through and linking everything i am initiating the process and now have safestrap and backup installed. going through with the rollback then i will start the unlock rocedure. update with any questions or issues i run into. thank you again!
quick thing i ran into before doing factory reset and rebooting into modified stock 3.2.4 it says to have the stock 3.1.0 files where can i find that file it wasn't linked in the rollback instruction or under the modified stock 3.2.4 zip from what i could see?
rbkelley89 said:
thank you so much for the walk through and linking everything i am initiating the process and now have safestrap and backup installed. going through with the rollback then i will start the unlock rocedure. update with any questions or issues i run into. thank you again!
quick thing i ran into before doing factory reset and rebooting into modified stock 3.2.4 it says to have the stock 3.1.0 files where can i find that file it wasn't linked in the rollback instruction or under the modified stock 3.2.4 zip from what i could see?
Click to expand...
Click to collapse
You can grab stock images here. Be absolutely certain you snag the correct one for your device. Verify md5=c49c0363de4d8dfa5c87c1bdb88aa2ba with ES FIle Explorer (long click the file and select 'properties' from the 'more' menu). Note you will loose root and OTA blocking. Be sure to stay off wifi. Use HDX Toolkit (requires usb tether to Windows PC) to root 3.1.0 and reblock OTA if needed.
Hi
Newbie here. We bought a kindle which turnout to be blacklisted so we can't register it. Obviously it is useless as we can only use internet.
My kindle was running on latest firmware which meant I couldn't root it. Thanks to one of you xda geniuses. I was able to rollback to firmware 13.3.2.8
I change oat filed to avoid upgrades. I installed es explorer.
I then rooted my kindle and did root checked which confirms it is rooted on Kfthwi android 4.2.2
I installed su super user. Seems to work fine
After that I tried to install boot loader fireflash but it keeps stopping
I finally managed to install and launch Rashr but when I boot recovery with twrp or any other files my kindle boots and stops saying can't boot and offers me to do factory reset or starts again as if nothing happened. I haven't chosen factory reset as I don't think this will help.
I have added su super users to system hoping this would help but no success.
I have also tried loads of kfu from pc but although adb is ok it says boot status unknown and fails every time as if it can't find the path or something...
I have ran out of ideas. I don't know what to do anymore
My aim is to install cm12 or other versions... anything to make this kindle become android
Please help me!
Thanks
worldita said:
Hi
Newbie here. We bought a kindle which turnout to be blacklisted so we can't register it. Obviously it is useless as we can only use internet.
My kindle was running on latest firmware which meant I couldn't root it. Thanks to one of you xda geniuses. I was able to rollback to firmware 13.3.2.8
I change oat filed to avoid upgrades. I installed es explorer.
I then rooted my kindle and did root checked which confirms it is rooted on Kfthwi android 4.2.2
I installed su super user. Seems to work fine
After that I tried to install boot loader fireflash but it keeps stopping
I finally managed to install and launch Rashr but when I boot recovery with twrp or any other files my kindle boots and stops saying can't boot and offers me to do factory reset or starts again as if nothing happened. I haven't chosen factory reset as I don't think this will help.
I have added su super users to system hoping this would help but no success.
I have also tried loads of kfu from pc but although adb is ok it says boot status unknown and fails every time as if it can't find the path or something...
I have ran out of ideas. I don't know what to do anymore
My aim is to install cm12 or other versions... anything to make this kindle become android
Please help me!
Thanks
Click to expand...
Click to collapse
Sorry - will not provide assistance for a blacklisted device. Read the forums.
Davey126 said:
Sorry - will not provide assistance for a blacklisted device. Read the forums.
Click to expand...
Click to collapse
Hi I am sorry I misunderstood the terms. It is NOT blacklisted. It is unregistered.
We have called Amazon and it does not belong to anyone. We don't know how it happened we bought it second hand. The tablet is not letting registered but it is not blacklisted. Can you still help ?
You can NOT unlock the bootloader, use TWRP and CM12 anyway. You'd need 3.2.3.2 or lower for that, and you can NOT downgrade below 3.2.8.
Ok thanks for replying to me and for the info. So no more hope? I should just bin it?
So sad.... was supposed to be for my kids.
I guess this shows you really can't buy these tablets second hand!
Thanks again for your time.
worldita said:
Ok thanks for replying to me and for the info. So no more hope? I should just bin it?
So sad.... was supposed to be for my kids.
I guess this shows you really can't buy these tablets second hand!
Thanks again for your time.
Click to expand...
Click to collapse
You likely toasted the device by installing stuff that is not valid for a HDX.
Wow Davey126 thank you so much for all your positive feedback.
So helpful
worldita said:
Wow Davey126 thank you so much for all your positive feedback.
So helpful
Click to expand...
Click to collapse
Sorry for the prickly response. Reacting to: 1) device that will not register which is a bright red flag waving; and 2) installing fireflash which is for a different model and likely destroyed your device. You can not install twrp on a HDX that has been upgraded past 3.2.6 and you can not rollback to any version below 3.2.8 from any version above 3.2.6. A little reading would have quickly revealed the sensitivity of HDX models to 'hacks' other than the limited suite described in the forums. Your device joins countless others in the tower of bricks created by owners failing to research proper procedures.
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
PariahNine said:
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
Click to expand...
Click to collapse
Given your firmware level:
- verify device is still rooted (use towelroot if needed)
- flash twrp recovery
- update bootloader to v3.2.3.2
- unlock bootloader (try 1-click method)
- flash rom of choice (Nexus, CM 11/12/13), SlimLP)
Search through the forums for relevant threads. Ask questions along the way. You have some work ahead (hours) but a nice reward at the other end.
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
PariahNine said:
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
Click to expand...
Click to collapse
Thoughts:
- moving roms between slots (specifically stock) via backup/restore is generally a bad idea in Safestrap; consider yourself lucky if you used this technique
- if the rom in the stock slot (assuming FireOS 13.3.1.0) boots properly then you can safely remove Safestrap v3 via the uninstall option in the apk
- do not wipe anything in Safestrap nor execute a 'factory reset' from the native Kindle recovery menu (bad outcomes)
- keep WiFi off / airplane mode engaged unless you are 100% sure the OTA block is working
- snag a copy of Flashify to install twrp and the 3.2.3 bootloader update
- check MD5 checksums with ES File Explorer or another tool before flashing; especially important for bootloader update!
- backup your existing recovery with Flashify before flashing twrp; leave a copy on the device
- enable USB debugging in Kindle settings (optional but offers additional recovery options should something go wrong)
- flash twrp first and make sure it works (reboot to recovery; have a look around but don't change anything)
- reboot FireOS and then use Flashify to update bootloader. Did I mention you should check MD5?
Post when above tasks are complete or if you have questions. Cover bootloader unlock next. Be aware the above steps carry some risk including permanently bricking the device. Make sure you have a clear understand on what is suppose to happen; double/triple check everything before committing changes. Good luck.
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
PariahNine said:
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Click to expand...
Click to collapse
- use the original apk to remove (uninstall) Safestrap v3 recovery; you do not need to uninstall the apk itself
- uninstalling Safestrap will not impact root
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
PariahNine said:
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
Click to expand...
Click to collapse
The FireOS version number will not change following bootloader update. It is a separate 'component' whose version can not be independently queried or verified. Typically the system (what you see, ie: FireOS) and bootloader are updated together and share the same version identifier. In this instance are only flashing the bookloader update as FireOS will soon be replaced by a different ROM. No need to update it and assume the associated risks.
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
PariahNine said:
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
Click to expand...
Click to collapse
Hum. Best handled by @draxie who developed 1-click. Generally pretty responsive to forum posts. If 1-click doesn't do it can always try the manual approach (a LOT more involved but not risky). Let's see what shakes out.
This is what I'm getting from the batch cmd window:
VirtualBox does not appear to be installed
Downloading 'https://www.virtualbox.org/wiki/Downloads' to 'C:\Users\Pariah\Down
loads\1-Click\1-Click\dwnlds'
Download complete.
Downloading 'http://download.virtualbox.org/virtualbox/5.0.12/VirtualBox-5.0.12-
104815-Win.exe' to 'C:\Users\Pariah\Downloads\1-Click\1-Click\VirtualBox-5.0.12-
104815-Win.exe'
Download complete.
Launching the VirtualBox installer momentarily
Please complete the installation with USB support enabled
Installation complete.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Virtual machine '1-Click' is created and registered.
UUID: 6b44be97-c931-47a5-8eeb-b780f5783b78
Settings file: 'C:\Users\Pariah\VirtualBox VMs\1-Click\1-Click.vbox'
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xf
fffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\Syste
m32\acaptuser64.dll: None of the 1 path(s) have a trust anchor.: \Device\Harddis
kVolume2\Windows\System32\acaptuser64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\ac
aptuser64.dll': rcNt=0xc0000190
Oracle VM VirtualBox Headless Interface 5.0.12
(C) 2008-2015 Oracle Corporation
All rights reserved.
Click to expand...
Click to collapse
And the 1-click instance in Virtual Box is showing "Booting the kernel."
Here is the method I used to block OTA updates.
Originally Posted by berndt_toast
Yeah, I agree. Staying rooted is difficult, but doable. I am still on the rootable version (13.3.1.0) and have stayed on it even through the OTA updates that have been released. I have stopped them from auto-applying (and from even being seen as updates) by doing the following:
I renamed otacerts.zip to otacerts.zip.old in /etc/security/
I also renamed com.amazon.dcp.apk to com.amazon.dcp.apk.old in /system/app/
Doing those prevent OTA updates from working and if you check for updates from the device, it says none are found (at least it has worked for me).
Click to expand...
Click to collapse
Do I need to undo this before proceeding with the bootloader update and unlocking?
PariahNine said:
Here is the method I used to block OTA updates.
Do I need to undo this before proceeding with the bootloader update and unlocking?
Click to expand...
Click to collapse
No - tasks ahead have no dependence on Amazon's update engine.
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
PariahNine said:
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
EncryptedCurse said:
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
Click to expand...
Click to collapse
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Davey126 said:
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Click to expand...
Click to collapse
If you want to give manual unlocking a try:
- use these drivers; you likely need to reinstall when flipping between adb and fastboot
- detail procedure
- suggest browsing this thread for additional info/tips. Lots of noise but some diamonds in the rough too
- careful not to go down a rabbit hole; some solutions are one offs that worked great for the poster due to their familiarity with a particular too, platform or technique
- unlike almost everything else with HDX you can not harm your device with bootloader unlock attempts. It will either work or not with no adverse consequences either way
There are a few excellent posts by @Cl4ncy, @jerryl and others (possibly one of mine) in different threads; unfortunately I wasn't able to surface them in a quick search. Nature of the HDX forums. A gold mine if information that is a bxxtch to access.
Before diving in you may want to flash CM11 or Nexus v4 which can be done with a locked bootloader. Both are rock solid KitKat based roms that will expose the full capabilities of your device and offer continuity to CM13 once unlocked.
Good luck.
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
PariahNine said:
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
Click to expand...
Click to collapse
Happy to hear you were sucesfull. Thanks also for sharing your experiences and insights. Should be helpful to others as they navigate through the process. Every nugget of new information helps!