Related
I've finally decided to try to root my G2 but can't get past the ADB setup. I downloaded the SDK, but when I open the manager and try to install platform tools it goes through the motions and then tells me nothing was installed. When I open a command prompt and type "ADB devices" it doesn't recognize anything. What am I doing wrong??
EDIT: specifically, when I try to install platform-tools it tells me it couldn't create a directory and nothing was installed.
66 people have read this and nobody has any suggestions to help?
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
I have a problem after rebooting my PC: <Java not found...> Reinstalling doesn't help, adding environment variables too. Any idea?
Just root using the rage/visionary method. No adb needed and very easy to do. Here is the linkhttp://forum.xda-developers.com/showthread.php?t=834228
Sent from my SilverBullet 'HTCDesireZ running CM7'
juvanni said:
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
Click to expand...
Click to collapse
I don't understand? I'm trying to root following the recommended wiki instructions, and I haven't been able to get adb to work so I haven't gotten past that step.
Are you running windows x64? Cause the android installer has issues detecting java on x64 systems.
When it says 'Can't find java' or whatever the error is, click back, then next again, it should find it the second time around. Well thats what happened for me anyway.
-Nipqer
If you're on froyo just use the app z4 root or universal androot
You can also use superoneclick root 2.11
Its very easy and it only take about 3 minutes
Stewie just said that!
I appreciate the help so far, but my problem is I have gingerbread and everything I've read requires froyo for root, and the only way I've read to downgrade uses ADB, so any non-ADB rooting method still won't work for me. I've followed the "ADB for dummies" thread and the other instruction thread and everything seems fine, but when I type in the first command for the downgrading it says adb isn't a recognized command. Am I in the wrong command prompt? I feel like its probably something really dumb I'm doing or not doing but for the life of me I can't figure it out.
Navigate to the folder adb is in.
Hold shift, right click in the folder (make sure nothing is selected)
select 'Open command window here' (or something along those lines)
Adb should work.
-Nipqer
OK, so I'm definitely in the right folder, I read and followed ADB for Dummies thread. Trying to follow this direction:
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
$ adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length"
When I type that in, should there be spaces between the "adb" and "shell"? Should there be a space after the command prompt and before "adb"? I've tried several variations of it and it keeps telling me "adb is not recognized as an internal or external operable program or batch file."
ok you need to run the command from the folder with adb.exe in it, type it as adb<space>shell<space>cat<space>/dev/msm_rotator
If you are getting an error search for adb.exe and once found try the command again from this folder,if as you say you are in the right folder then I think you will have to reinstall adb as I just ran the command in the form above and it works so if you still get an error then something has gone wrong with the install
P.S Another way to make sure that adb is working and recognises your phone is to type adb devices, if your phone is attached and recognised then it will return a number
Thank you! I had to uninstall and reinstall the package, I don't know what was wrong but it seems to be working now. Also, I knew I was probably doing something stupid, and I was. I wasn't in the platform-tools directory for my command prompt, I was in the TOOLs directory. Just so I'm clear, every command I type into the terminal should be in the Platform-tools directory, correct?
Now, assuming I can follow all the other directions with no problems, once I get to the downgrade pushing steps, I will lose all my current settings, right? It will be a fresh froyo 2.2 like it came to me originally? Other than using Appbrain to back up my current apps, how else should I make a backup?
Final question, do I need to follow the temp root directions and push the downgrade all at one time? Or can I do the temp root and come back at a later time to push the downgrade?
First problem solved then!
Yes but follow this Step 4
Now we need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)if you want to.
Once done you can use ADB from the command prompt in ANY folder,very handy IMO.
If I was you I would set aside enough time and see it through,no point to temp rooting alone.
Get Titanium backup from the market an absolute essential app with this you can backup,upload to dropbox(Another essential app) uninstall apps and a host of other useful tools.
Read the guide first as well,good luck.
Not sure if this will help anyone, but I had a problem when rooting my new kindle fire 6.2.1
If you tried the Burrito Root method, I saw some few mistakes that I've done or didn't see in the video.
1. Updating the Kindle Drivers
I had previously rooted my android phone before, so when I plugged the kindle fire on my windows 7 laptop, I noticed that the windows was already indetifying it as an android phone, and had already labeled it for ADB. This auto-driver update thing might work for some people, but I find much better success replacing that driver that your computer identifies Kindle as, with the one that the BurritoRoot driver provides.
2. Getting the Kindle Root in the Listed Devices of ADB in command prompt.
This was probably the biggest issue I had when rooting the Kindle Fire. I was scratching my head, thinking why my Kindle Fire wasn't listed in the command prompt after typing "adb devices." I knew I did everything right from the beginning. Or so I thought?
One way I found that fixed that was downloading the Kindle Fire Utility v0.9.1
Unlucky for me, the download link was gone....
LUCKY for me, a fellow member here uploaded a mirror.
I somehow got it to work, with just luck but figured out the exact steps that seem to work for me (on Win 7 64 bit here).
1) Open up command prompt again, do the cd c:\KindleADB etc... upto the point where you typed in adb devices. you should be seeing no listed devices on the cmd (if you have that problem). LEAVE IT OPEN.
2) DOwnload the kindle fire utility, open the run.bat , it should have a message saying daemon started sucessfully, THEN QUICKLY FOLLOW THE NEXT STEP.
3) When the daemon started successfully message popped up on the KFU, go back to your CMD where you typed in adb devices and quickly type in "adb devices" again. it should say something like, killing out of date, starting daemon, and something about successful (Sorry if I'm not that much of a help, I tend to forget what the exact message said).
4) It should list the device. if not type it again.
5) Walla ! it should show a bunch of numbers, under listed devices.
3. Rooting the Kindle Fire in command prompt ERRORS
This wasn't much of a problem as it really was my mistake. I kept getting error messages when i typed in ADB ROOT in the command prompt during the BurritoRoot rooting method.
1) You have to make sure you have the BurritoRoot app installed in your kindle fire before starting the CMD adb root part. The app will tell you when to start typing away in CMD!
2) If you're doing the burritoroot method, you have to make sure you got all the names and directory right.
3) When you're doing the CMD adb root part, copy and paste it usually the best way to do it in CMD to avoid mistakes and erorrs! And no, you don't press CTRL+V in CMD. Rather, you right-click the CMD , then click paste (after copying the line you want to input).
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install com.noshufou.android.su-1.apk
adb reboot
Notice all those commands above that you're suppose to type in (or copy and paste). The ones I bolded, people tend to make mistakes there. When you put those files you downloaded into KindleADB, PLEASE MAKE SURE IT IS NAMED com.noshufou.android.su-1.apk, otherwise when you get to the part
Code:
adb install [B]com.noshufou.android.su-1.apk[/B]
change it to :
adb install WHATEVER IT IS CALLED.apk that is Superuser.
The most important part is to push the SU file (that has no file extension).
I had my kindle rooted, with Superuser installed, but I couldn't get any pop-ups from Superuser asking permission for any apps! That is, until I found out I forgot to push the su file to /system/xbin/su and other steps to chmod it.
Anyways, I hope this helps anyone that goes through any problem like I did above. If not, sorry to waste your time! If you guys have any other problems, please leave a question below and perhaps I could or a fellow member here could help you.
Thanks again!
http://forum.xda-developers.com/showthread.php?t=1417234
Ok, so I did something stupid, I tried to install a slider lock theme on my kindle and probably screwed up the Framework-Res. I did not have TWRP or a backup of any kind.
Now the kindle just sits at the boot splash screen.
The device was running on 6.2.2 and most tutorials seem to be made for 6.2.1
I have tried a few manual commands but remount is just say "Operation Not Permitted" (I cant figure out how to fix this either.
Running automated programs like Unbrick Utility just don't work, it says it has completed but you can see a bunch of errors saying it could not copy or not permitted etc...
At this point I just want my kindle fire back even if that means a complete restore, can someone please try to help or point me in the right direction I am about to go insane.
Added Info: To be more exact, I tried to use metamorph to install a slider lock theme, nothing seemed to happen so I closed the app. I thought everything was fine so I put the kindle to sleep, but I could not wake it up. I tried restarting it and that's how I got to were I am now.
Update:
Thanks to b63 I was able to get this fixed, I cant thank him enough.
Ok here is how I got it fixed
First I followed the directions given to me below by b63
he told me to refer to this http://forum.xda-developers.com/show...8&postcount=29 which I did, however When I got to 8 I did something different, I did not need to re install the whole Rom because I had only messed up the Framework-res.apk
So instead I pulled the Framework-res.apk from /system/framework in the official kindle 6.2.2 update.zip
I then used these commands to replace the broken apk on the device and restart in normal boot mode.
4. "adb remount"
5. "adb push framework-res.apk /system/framework/framework-res.apk"
6. "adb shell chown root /system/framework/framework-res.apk"
7. "adb shell chmod 644 /system/framework/framework-res.apk"
8. "adb shell idme bootmode 4000"
9. "adb reboot"
I know that this explanation is not super descriptive but most of what you need can be found below in the thread.
This problem is rather specific to my situation so if you are having the same problem and you can't figure it out send me a PM or reply to this thread.
Anyone? I'm starting to think i should just try to return it.
would need some more concrete information:
is it rooted only ?
what is the boot splash screen "kindle fire" (static or animated) or yellow triangle ?
do you have kfu available ?
moved and renamed so that it is at c:\kfu ?
patched the run.bat of kfu ?
what are the 3 status lines of kfu when you just start it ? - please don't do any option at the moment
os/bit of computer ?
driver status in device manager ?
b63 said:
would need some more concrete information:
is it rooted only ?
what is the boot splash screen "kindle fire" (static or animated) or yellow triangle ?
do you have kfu available ?
moved and renamed so that it is at c:\kfu ?
patched the run.bat of kfu ?
what are the 3 status lines of kfu when you just start it ? - please don't do any option at the moment
os/bit of computer ?
driver status in device manager ?
Click to expand...
Click to collapse
Thank you for the response, I'm not at my normal Computer now, but I will answer what I can from here.
Yes I believe it is rooted only, no roms or anything installed.
The Splash screen is Kindle Fire, It is static (no shine animation). I also never installed TWRP or firefirefire so I don't think it should be yellow. (I tried though)
I do have KFU available, but I'm getting operation not permitted errors
No I did not move/rename it (maybe that's the not permitted issue?)
Three Lines: ADB Status: Online ADB Rooted: No (it was rooted) Boot Status: 4000
Vista 32 Bit
Cant check at the moment (however I believe the drivers are working properly)
Thank you for the response Ill try to help the best I can, Im pretty techy but Ill admit I'm a noob at ADB
Damieok said:
Thank you for the response, I'm not at my normal Computer now, but I will answer what I can from here.
Yes I believe it is rooted only, no roms or anything installed.
The Splash screen is Kindle Fire, It is static (no shine animation). I also never installed TWRP or firefirefire so I don't think it should be yellow. (I tried though)
I do have KFU available, but I'm getting operation not permitted errors
No I did not move/rename it (maybe that's the not permitted issue?)
Three Lines: ADB Status: Online ADB Rooted: No (it was rooted) Boot Status: 4000
Vista 32 Bit
Cant check at the moment (however I believe the drivers are working properly)
Thank you for the response Ill try to help the best I can, Im pretty techy but Ill admit I'm a noob at ADB
Click to expand...
Click to collapse
ok i see a lot out of this - thanks
would recommend to do the move/rename of kfu to sort out any additional problems
you should have adb commands available and the kf is in normal boot mode
now the ultimate test is to issue:
"adb shell"
- if it goes into the shell ($ or # prompt) you can resume
- if it responds something like <exec "system/bin/sh": No such file or directory> then there is no possibility to get to fastboot mode to install fff and twrp which is necessary to install a fresh rom - if this is the case your only solution is to build or buy a "factory cable" - look at this thread :
http://forum.xda-developers.com/showthread.php?t=1392693
b63 said:
I would recommend to do the move/rename of kfu to sort out any additional problems
you should have adb commands available and the kf is in normal boot mode
now the ultimate test is to issue:
"adb shell"
- if it goes into the shell ($ or # prompt) you can resume
- if it responds something like <exec "system/bin/sh": No such file or directory> then there is no possibility to get to fastboot mode to install fff and twrp which is necessary to install a fresh rom - if this is the case your only solution is to build or buy a "factory cable" - look at this thread :
http://forum.xda-developers.com/showthread.php?t=1392693
Click to expand...
Click to collapse
Ok so I renamed the "Kindle Fire Utility" folder to "kfu" moved it to C:\
(if this is incorrect please let me know.)
And good news, adb shell responds with $, were should I go next. (also I have access to my normal computer now)
Thanks again for helping me out with this.
great !!! - simply try to follow this post starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
place the downloaded files in the tools folder of kfu since you are doing the commands from there
b63 said:
great !!! - simply try to follow this post starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
place the downloaded files in the tools folder of kfu since you are doing the commands from there
Click to expand...
Click to collapse
Im a little confused at this guide are the commands being entered into adb or in kfu? Were does kfu come into play?
Sorry the guide is a little hard to understand
it' not so complicated as it sounds ...
open a elevated command prompt and cd to c:\kfu\tools
here are all commands you need and where kfu comes in play
- you don't need kfu itself - only the tools folder
- leave the command window open all the time
Issue has been solved see last posts
For some reason when I run "KFU" it says windows cannot find tool/wget and when kfu loads up everything i click says it cannot find path specified. I have tried moving it to C:\ and using cmd... I have also tried earlier versions of kfu but to no avail. i found this http://forum.xda-developers.com/showthread.php?t=1473212 but nothing there helped I dont know what to do can someone please help me..
Sidenote, I have a kindle with 6.2.2 and im using windows 7.
I have rooted a kindle before with kfu and it worked almost flawlessly and that was around kfu 2...
espacially on win7 it seems to be be important to move and rename kfu that it is c:\kfu - it don't like spaces in pathname
check the tools folder of kfu - there should be wget.exe along with all other needed commands - it not -> redownload
i don't double click on run.bat - i use to open a (elevated) command prompt, cd to c:\kfu and enter run.bat
hope this helps ...
That is exactly what i have done it is in c:\kfu no spaces i have used cmd and typed exactly what you said before but when kfu loads it says "adb status offline""adb rooted no""boot status unknown"
I have also redownloaded it multiple times i tried the 9.2 kfu and patched it but that didnt works either i have even tried two different win7 computers and on the other win 7 i tried using kfu 8 but it said adb status offline
what does the device manager say under "android phone" ?
kf is in normal boot mode ?
allready tried a hard reset ? (holding pwr button ~20sec till it turns off - pwr on again)
some other ideas:
restarting adb on pc by issuing "adb kill-server" from the tools directory
checking with "adb devices"
check if you have c:\windows\system32 in your path ("path" at a command prompt)
android adb interface under android phone...
i hit normal boot manually power off and on the KF and the utility is stuck at waiting for device...
kill server goes through but list of devices shows nothing
and path on cmd shows up as c:\users\jamil>
i saw another post that said type set into cmd but that seems to not have done anything
thanks again for helping
this is what path shows
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\jamil>path
PATH=C:\Program Files (x86)\AMD APP\bin\x86_64;C:\Program Files (x86)\AMD APP\bi
n\x86;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System3
2\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-S
tatic
C:\Users\jamil>
Okay so i figured it out no when i right-click run.bat with admin rights it get the windows cant find tool.... but i noticed that when my other kindle gets connected it considers itself to be adb composite device when this one considers it self to be adb interface device or something like that i deleted both of the devices drivers and then i connected the one i am working with now and installed the drivers afterwards and voila... i got it too work thank you very much b63 for all the help
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
b63 said:
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Click to expand...
Click to collapse
I have done what he did and mine still gives the same error
its in C:\kfu
I have a 3rd Gen fire hdx 8.9 on 14.3.2.6. Safestrap is installed. I want to roll back and unlock my bootloader to install the nexus rom.
Is there a tutorial available? Do I need to uninstall safestrap first?
Check page 1 of this thread, basically it's all there, so read the info & the linked threads. Any questions ask first, i.e. before you brick your kindle.
Note that you can NOT use the rollback images, nor edit the build number. You must use the procedure described in post 1 of the thread and download the rollback zip I linked in post 4, you need to scroll down to get to the 3.2.5/3.2.6 procedure.
Cl4ncy said:
Check page 1 of this thread, basically it's all there, so read the info & the linked threads. Any questions ask first, i.e. before you brick your kindle.
Note that you can NOT use the rollback images, nor edit the build number. You must use the procedure described in post 1 of the thread and download the rollback zip I linked in post 4, you need to scroll down to get to the 3.2.5/3.2.6 procedure.
Click to expand...
Click to collapse
I followed the procedure but I'm not clear that I downgraded correctly. No when I look at my system update, it says I am on 14.3.0.0_user_300079820. I thought I was supposed to be on 14.3.1.0_user_310079820? The file I downloaded from the thread is indeed "update-kindle-14.3.1.0_user_310079820.bin". Is there something else I need to do to downgrade before updating the bootloader?
rootnooby said:
I followed the procedure but I'm not clear that I downgraded correctly. No when I look at my system update, it says I am on 14.3.0.0_user_300079820. I thought I was supposed to be on 14.3.1.0_user_310079820? The file I downloaded from the thread is indeed "update-kindle-14.3.1.0_user_310079820.bin". Is there something else I need to do to downgrade before updating the bootloader?
Click to expand...
Click to collapse
I checked the rollback.zip for Apollo, it seems to be in the build.prop file, so nothing to worry about.
Now you should install TWRP via adb, update the 3.2.3.2 bootloader in TWRP, and finally unlock the bootloader.
Be sure to root and disable OTA via HDXToolkit, and enable USB debugging in Fire OS, before you flash TWRP.
And be sure to create a backup of Fire OS in TWRP before you flash any custom ROM.
Thanks. Is there a link outlining the steps to install twrp via add? Sorry for the need to have my hand held through this!
rootnooby said:
Thanks. Is there a link outlining the steps to install twrp via add? Sorry for the need to have my hand held through this!
Click to expand...
Click to collapse
You must have Minimal ADB and Fastboot installed, download the Apollo TWRP Image here, copy it to the root of the sdcard (i.e. the directory you see in Explorer when you connect the HDX to your PC, so don't open any directory there),then you open a DOS box, change dir to the adb directory (enter cd\adb), then execute the commands mentioned in the TWRP thread with the correct file name for the Apollo TWRP image.
Thanks so much. I'll give it a go tonight.
rootnooby said:
Thanks so much. I'll give it a go tonight.
Click to expand...
Click to collapse
looks like I got through everything except the last remaining step of unlocking the bootloader. I confirmed that I am rooted and OTA is blocked. Not sure how to get this unlocked so I can finally have a real ROM!
rootnooby said:
looks like I got through everything except the last remaining step of unlocking the bootloader. I confirmed that I am rooted and OTA is blocked. Not sure how to get this unlocked so I can finally have a real ROM!
Click to expand...
Click to collapse
OK, so you have Minimal ADB and Fastboot installed, unlocking the bootloader is really simple (with a little knowledge about command prompts), so download these drivers you need to install when the good ol' "waiting for device" issue occurs (check device manager then, the HDX probably has a yellow exclamation mark there).
You must download the software and the Python script mentioned here, and then follow the path outlined there, or (after installation of the required software) also here. Basically you just need to open a couple of command prompts (DOS boxes), change dir to the adb directory (enter cd\adb - or cd\python27 to go to the Python directory), then get the ID and serial, use the Python script with them, and finally execute the fastboot commands to unlock the bootloader.
That's it - and it's a no brainer, you can't mess up anything, if the unlock code is incorrect, it just won't flash (well, you must enter the fastboot commands correctly of course).
Cl4ncy said:
OK, so you have Minimal ADB and Fastboot installed, unlocking the bootloader is really simple (with a little knowledge about command prompts), so download these drivers you need to install when the good ol' "waiting for device" issue occurs (check device manager then, the HDX probably has a yellow exclamation mark there).
You must download the software and the Python script mentioned here, and then follow the path outlined there, or (after installation of the required software) also here. Basically you just need to open a couple of command prompts (DOS boxes), change dir to the adb directory (enter cd\adb - or cd\python27 to go to the Python directory), then get the ID and serial, use the Python script with them, and finally execute the fastboot commands to unlock the bootloader.
That's it - and it's a no brainer, you can't mess up anything, if the unlock code is incorrect, it just won't flash (well, you must enter the fastboot commands correctly of course).
Click to expand...
Click to collapse
Thanks. Running into an error creating the unlock file. I installed python, but I don't think i installed gmpy2-2.0.7-cp27-none-win_amd64.whl (md5) properly. The error I'm getting when I run the following command "python.exe cuberHDX.py 0xmmssssssss" "is "no module named gmpy2". I am using my correct code in the previous command. When I downloaded the gmpy2-2.0.7-cp27-none-win_amd64.whl (md5), I copied into the Python27 directory. Not sure if this is correct.
rootnooby said:
Thanks. Running into an error creating the unlock file. I installed python, but I don't think i installed gmpy2-2.0.7-cp27-none-win_amd64.whl (md5) properly. The error I'm getting when I run the following command "python.exe cuberHDX.py 0xmmssssssss" "is "no module named gmpy2". I am using my correct code in the previous command. When I downloaded the gmpy2-2.0.7-cp27-none-win_amd64.whl (md5), I copied into the Python27 directory. Not sure if this is correct.
Click to expand...
Click to collapse
Try to use the exe installer for 2.0.6 from here. If it still fails, PM me your ID and serial, I'll create the .unlock file for you then.
Cl4ncy said:
Try to use the exe installer for 2.0.6 from here. If it still fails, PM me your ID and serial, I'll create the .unlock file for you then.
Click to expand...
Click to collapse
Thanks. It worked. I now have an unlock code. I'm not clear where my fastboot directory is? It says I need to "copy that file to your fastboot directory" before i run the commands. Would that just be the root of the kindle itself? Sorry for the question.
rootnooby said:
Thanks. It worked. I now have an unlock code. I'm not clear where my fastboot directory is? It says I need to "copy that file to your fastboot directory" before i run the commands. Would that just be the root of the kindle itself? Sorry for the question.
Click to expand...
Click to collapse
If you installed Minimal ADB and Fastboot, it's the adb directory (e.g. C:\adb), you should have fastboot.exe in there as well. Just copy/move the .unlock file in the adb directory, open two DOS boxes, enter cd\adb in both,
then enter adb reboot-bootloader in the first one,
and the fastboot commands
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock (mm=your ID, ssssssss=your serial)
fastboot -i 0x1949 reboot
in the second (again: if you see "waiting for device" on the fastboot prompt, install these drivers in device manager for the HDX (probably sitting there with a yellow exclamation mark).
Cl4ncy said:
If you installed Minimal ADB and Fastboot, it's the adb directory (e.g. C:\adb), you should have fastboot.exe in there as well. Just copy/move the .unlock file in the adb directory, open two DOS boxes, enter cd\adb in both,
then enter adb reboot-boorloader in the first one,
and the fastboot commands
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock (mm=your ID, ssssssss=your serial)
fastboot -i 0x1949 reboot
in the second (again: if you see "waiting for device" on the fastboot prompt, install these drivers in device manager for the HDX (probably sitting there with a yellow exclamation mark).
Click to expand...
Click to collapse
Wow. I think it all worked! Assuming that's it. I can go ahead and load ROMs!
rootnooby said:
Wow. I think it all worked! Assuming that's it. I can go ahead and load ROMs!
Click to expand...
Click to collapse
If it looked like this, i.e. unlock code is correct, then yes.
Enjoy your "free" HDX.
yes, it does look like that so I have unlocked successfully! I ran a backup using twrp, and that worked well. One problem I'm having now is that my computer doesn't seem to recognize the Kindle when connected via USB any more. I'm getting a message that says some candles are not compatible and a separate file needs to be downloaded. When I go to the Kindle support website, this is applicable for older systems running Windows XP. Have you seen this problem before? Now that I have a backup I want to move it over to my PC so I don't use all that storage.
rootnooby said:
yes, it does look like that so I have unlocked successfully! I ran a backup using twrp, and that worked well. One problem I'm having now is that my computer doesn't seem to recognize the Kindle when connected via USB any more. I'm getting a message that says some candles are not compatible and a separate file needs to be downloaded. When I go to the Kindle support website, this is applicable for older systems running Windows XP. Have you seen this problem before? Now that I have a backup I want to move it over to my PC so I don't use all that storage.
Click to expand...
Click to collapse
Yes, it seems that the drivers required for fastboot cause such a problem, remove them in device manager (select to delete the driver files), then dis- and re-connect the HDX, so the original HDX drivers will be re-installed. Should do the trick in this case.