Related
Hi to all I have a provlem I need help with.While trying to unlock my bootloader using rsd and fastboot.I get as far as the cmd line entries and have problems basically I cant seem to get my command line to use the fastboot command and or any other fastboot command I can find.What seems to happen all the time is that the command line responds with "this is not an internal or external command" or similar.
Any help appreciated Windows 7 64bit all latest drivers installed
scotty7910 said:
Hi to all I have a provlem I need help with.While trying to unlock my bootloader using rsd and fastboot.I get as far as the cmd line entries and have problems basically I cant seem to get my command line to use the fastboot command and or any other fastboot command I can find.What seems to happen all the time is that the command line responds with "this is not an internal or external command" or similar.
Any help appreciated Windows 7 64bit all latest drivers installed
Click to expand...
Click to collapse
are you in the same folder that the FASTBOOT.EXE is in when you run the command???
Make sure your running CMD as administrator. You can tell by the path that shows when cmd is launched. If its a regular user account it will path to something like: c:\users\"your username"\
If your running as admin it will path to something like: c:\windows\system32
Sent from my MB860 using XDA Premium App
Take your fastboot files and images and put them in a folder on the root of your C: drive... I use one named phone
Then you should be able to open your Command line and type
cd c:\phone
That will change you to the Phone directory you made in the root of C: earlier
If you want to make sure you can type DIR and it should list all the files you have in there.
At this time you can start using your fastboot commands and it will recognize them.
beatphreek said:
Take your fastboot files and images and put them in a folder on the root of your C: drive... I use one named phone
Then you should be able to open your Command line and type
cd c:\phone
That will change you to the Phone directory you made in the root of C: earlier
If you want to make sure you can type DIR and it should list all the files you have in there.
At this time you can start using your fastboot commands and it will recognize them.
Click to expand...
Click to collapse
Another handy thing is to open the folder then hold the shift key and then right click. You'll have an "Open command window here" option.
Yep I use that all the time...
used both the suggestions in here and still having trouble,can do the root of c folder,use the dir command see it is all there but the cd C:\fastbootpackage brings the same response again.Can anyone see where I am going wrong?Once the command line changes to fastboot what do I need to command?Phone is still attached (as per the guide I am following?)showing 100% phone needs manually rebooted.
I have all latest drivers on win 7 64bit and I am definetely running cmd as an administrator
Also as the third suggestion suggests if I open the cmd box from the folder what is the exact command to use from there?Is there an alternative to doing this as I am beginning to struggle?
Unlock your Bootloader
1. You need to download and install RDS lite on your PC:http://forum.xda-developers.com/attachment.php?attachmentid=634879&d=1308872277
2. Download and extract IHOP_Bell.rarhttp://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1136261&v=1&libid=1311795928774&out=http%3A%2F%2Fdiamantephoto.com%2FIHOP_Bell.rar&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D997&title=%5BPUDDING%5D%20International%20House%20of%20Pudding!%20(Unlock%2Froot%20thread)%20Updated%20July%2023%202011%20-%20xda-developers&txt=http%3A%2F%2Fdiamantephoto.com%2FIHOP_Bell.rar
3. Download and extract Fastboot tools http://gititbit.ch/FAST
4. Power down your Motorola Atrix
5. Take out your microSD card and SIM*card*for the flashing process
6. While turning the phone on, hold the Volume Up button until it acknowledges RSD
7. Your device will say “Starting RSD protocol support”
8. Run “RSD Lite” on your computer
9. Press the “. . .” button next to the box labeled “Filename”
10. Load up the SBF file – IHOP_Bell.sbf
11. Plug your device into your computer
12. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
13. Press the “Start” button
14. Be patient while the phone*reboots. It will take a long time.
15. Open and extract the Fastboot package from above
16. Open a command prompt window
a.On Windows, press Start and type “cmd” then press the enter button
17.Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example:* cd C:\Users\Kenneth\Desktop\fastboot-package)
a.cd*your directory here
18. Power down your Atrix device
19. Hold the power button and the downward volume button until you see “Fastboot”
20. Let go of the buttons and press the upward volume button once
21. You will now see “Starting Fastboot protocol support”
22. Plug your device into a USB port in the back slot of your computer
a.Front slots sometimes do not have enough power to stay connected to the device.
23. Type the following command:
a.fastboot oem unlock
24. You will now receive a warning along with a unique device ID
25. Type the following commands using your unique device ID in place of the ####:
a.fastboot oem unlock ####
b.fastboot reboot
26. Wait for your device to reboot. Congratulations! You now have an unlocked bootloader!
This is the guide I have been using, thanks again
scotty7910 said:
"this is not an internal or external command"
Click to expand...
Click to collapse
This msg will only show if you are in different folder than your fastboot. You don't need to run cmd as administrator. The best thing to do is:
copy those 3 files (AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe) to your main c:\ (do not put to the folder)
Run cmd and type "cd \" this will move you to c:\
Now type fastboot and press enter - you should see various commands that can be used. (your mobile doesn't need to be connect to your pc to see this)
Now you can continue with unlocking. If you applied ihop.sbf already then startt from step 18.
I'm 99% sure that you were in the wrong folder.
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
scotty7910 said:
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
Click to expand...
Click to collapse
Don't use the Rom Manager app. It sucks and doesn't work properly. Do things properly.
With XDA forum members there's no reason to do things half assed. Use your hole ass, dammit.
scotty7910 said:
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
Click to expand...
Click to collapse
Well if you came that far then try to install tenfar's recovery, download this file :recovery-en-goapk-0630-1029.zip Unzip and move recovery-en-goapk-0630-1029.img to your c:\....Now reboot your phone and enter to fastboot mode. In cmd go to c:\ and type "fastboot flash recovery recovery-en-goapk-0630-1029.img" and then "fastboot reboot" DONE
If you have any problems try to download moto-fastboot (http://forum.xda-developers.com/attachment.php?attachmentid=635584&d=1308928440). It's kind of the same thing as fastboot and to be honest I don't know what's the different between both (I think moto-fastboot is designed for 2.3.4 firmware). Extract zip and move moto-fastboot to c:\ and type the same command but instead of fastboot type moto-fastboot. I hope this make sense.
Also it's recommended to delete "install_recovery.sh" which apparently is in /system/etc/ BUT I never managed to find this file and I just ignored this step.
thanks foka, but I have already tried and tried again unsuccessfully to use tenfars cwm.I can install the recovery and delete the sh file all as normal using fastboot and astro.However for some reason there seems to be no way I can get into cwm having flashed it.when I attempt it I dont see the same menu I could scroll through as before.Then I tried a cwm of tenfars that was supposed to flash through rom manager.Again the flash went fine but could not seem to enter recovery mode.I see you installed aura 1.1 didi you flash a radio afterwards?My signal is comnstantly 1 bar.Could you reccomend a uk radio?
Well Ive flashed at&t radio N_01.77.30p which solved battery draining and 1 bar issue. I'm not sure why you can't use cwm recovery...
Sent from Motorola Atrix
What do you mean you don't see the same menu as before? When you hold volume down, power up phone, fastboot, scroll through the list and none of them say Android Recovery?
http://forum.xda-developers.com/showthread.php?t=1364416
I dowloaded SDK and os,and drivers,when i type fastboot -w,and other commands,cmd says that he doesn't know what to do with command.(I typed cd and path to fastboot.img...)
http://forum.xda-developers.com/showthread.php?t=927379
When i click on automatic boot it just shows for 1sec and then just dissipears.
My phone is in fastboot mod.
HELP ?
You have used the cd command to the path containing fastboot.exe, adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll?
What's the exact error message that comes up in cmd?
Just use this tool. There is nothing easier than this.
So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?
UpsideDownAce said:
So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?
Click to expand...
Click to collapse
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...
uncleswoop said:
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...
Click to expand...
Click to collapse
Just to be sure, you've apply sideload from adb in the recovery, correct?
ducatic said:
Just to be sure, you've apply sideload from adb in the recovery, correct?
Click to expand...
Click to collapse
I'm in the same boat! I tried, today, several times to sideload the update but I'm constantly getting the cannot read sideload error message. I guess I'm off to other sites to see what the fix is.
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
adb sideload 094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
Click to expand...
Click to collapse
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:
I might be just an idiot but why are you guys trying to SideLoad a system update?
AFAIK... sideload is merely to install apps into your rom that Jellybean or the Playstore doesn't like.
I think you guys want to use "ADB Fastboot" commands instead. Get a guide before you attempt to do this though. I used Wugs Toolkit to install the bootloader from 4.2.2 update.
fede01_8 said:
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
Click to expand...
Click to collapse
:laugh: true
For clarity:
- adb sideload can used for installing zip updates from PC, as an alternative for using the ROM/recovery manager on your tablet/phone.
Code:
adb sideload update.zip
- fastboot flash is used for installing img files to a specific partition (boot, recovery, system)
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
Thank you!!! Spending hours trying to figure it out, so simple. Although not sure why the toolkit didn't work, but using CMD did work.
fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
fede01_8 said:
YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:
Click to expand...
Click to collapse
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.
brandnewyc said:
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.
Click to expand...
Click to collapse
This is what got me on the right trail. I opened the command prompt, navigated to the correct folder, used the sideload command and copied the name of the update file into the command prompt window, but it wasn't until I appended it with the .zip extension that it finally worked.:victory:
Hey guys! I don't have the sideload problem anymore, but, I get this error. cannot read '(name of file).zip'
I am either really dumb or this isn't working! I have it connected to adb device number and all working fine. I have the zip in platforms-tools cmd window opened etc. when i go to adb sideload and then top of cmd window edit paste the name of the file add .zip and it says can not read file!
Please help!!
Same problem...fixed
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~
jihoon526 said:
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~
Click to expand...
Click to collapse
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!
Fix
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.
hkleiner said:
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.
Click to expand...
Click to collapse
are you on the same directory as your file?
teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
Try addind ".zip" at the end of the file name in CMD. So if the name in the directory is ROM, type into cmd "adb sideload ROM.zip"
DigitalOSH said:
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!
Click to expand...
Click to collapse
oddly this helped me a lot with another device. i was having the exact same problem and found this topic in searching for a solution. but after removing the extension, renaming, then renaming and re-adding the extension it worked. i also had to type adb sideload fielanme.zip.zip to get it working.
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.
Hey everyone, was hoping for some help here. Just sold my 6P and need to return it to stock and relock bootloader. I had no issues flashing all stock images but when I go to issue the command "fastboot flashing lock" I get this http://hastebin.com/iqideleloy.xm Not sure why this is happening but any insight would be appreciated, thanks.
Triscuit said:
Hey everyone, was hoping for some help here. Just sold my 6P and need to return it to stock and relock bootloader. I had no issues flashing all stock images but when I go to issue the command "fastboot flashing lock" I get this http://hastebin.com/iqideleloy.xm Not sure why this is happening but any insight would be appreciated, thanks.
Click to expand...
Click to collapse
That means your adb/fastboot isn't up to date, it doesn't recognise the command.
Heisenberg said:
That means your adb/fastboot isn't up to date, it doesn't recognise the command.
Click to expand...
Click to collapse
Thanks for the reply Heisenberg. I had a feeling that was the issue so I updated everything on my Ubuntu machine and its still not working. I have an older windows laptop that I'm going to try on next. I have a feeling there are leftover bits of the old adb/fastboot.
Triscuit said:
Thanks for the reply Heisenberg. I had a feeling that was the issue so I updated everything on my Ubuntu machine and its still not working. I have an older windows laptop that I'm going to try on next. I have a feeling there are leftover bits of the old adb/fastboot.
Click to expand...
Click to collapse
How did you install adb/fastboot on Ubuntu? If you're using the package that is in their official repos it won't update properly, you need to download the SDK package and install it that way.
Heisenberg said:
How did you install adb/fastboot on Ubuntu? If you're using the package that is in their official repos it won't update properly, you need to download the SDK package and install it that way.
Click to expand...
Click to collapse
Yea, that's how I updated. I'm not sure, I will try the other method and let you know.
Triscuit said:
Yea, that's how I updated. I'm not sure, I will try the other method and let you know.
Click to expand...
Click to collapse
Grab this zip:
https://dl.google.com/dl/android/studio/ide-zips/2.1.3.0/android-studio-ide-143.3101438-linux.zip
Create an SDK folder in your /home directory and extract the zip there. Once extracted open the tools folder and then run the Android program (this is the SDK manager). Install the platform-tools package and now you'll see a platform-tools folder in the SDK folder that you extracted the SDK zip into. Within this platform-tools folder are adb and fastboot. You need to open a terminal window from within that platform-tools folder (right-click, select open in terminal), then prefix any command with "./" so that it's using the fastboot within that directory and not the Ubuntu one. So the commands would be like this:
Code:
./fastboot devices
Code:
./fastboot flashing lock
Heisenberg said:
Grab this zip:
https://dl.google.com/dl/android/studio/ide-zips/2.1.3.0/android-studio-ide-143.3101438-linux.zip
Create an SDK folder in your /home directory and extract the zip there. Once extracted open the tools folder and then run the Android program (this is the SDK manager). Install the platform-tools package and now you'll see a platform-tools folder in the SDK folder that you extracted the SDK zip into. Within this platform-tools folder are adb and fastboot. You need to open a terminal window from within that platform-tools folder (right-click, select open in terminal), then prefix any command with "./" so that it's using the fastboot within that directory and not the Ubuntu one. So the commands would be like this:
Code:
./fastboot devices
Code:
./fastboot flashing lock
Click to expand...
Click to collapse
Thanks very much, this is just about what I did, but I will try it!
Triscuit said:
Thanks very much, this is just about what I did, but I will try it!
Click to expand...
Click to collapse
No worries, let me know how you go.
Heisenberg said:
No worries, let me know how you go.
Click to expand...
Click to collapse
Well I ended up using a windows laptop that has never had adb/fastboot installed on it. Followed your guide to the word.....and boom locked bootloader. Thanks for the help Heisenberg.
Triscuit said:
Well I ended up using a windows laptop that has never had adb/fastboot installed on it. Followed your guide to the word.....and boom locked bootloader. Thanks for the help Heisenberg.
Click to expand...
Click to collapse
Cool, glad you got it done.