• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[HELP] Thor 4.5.5.3 Unlock Bootloader Specific Questions

Search This thread

hwwof

Member
May 28, 2015
34
2
I don't use Windows anymore, but I'm skeptical about File Explorer reporting file size as 0kb..
That's why I asked. When you get to it, can you also make sure to display the size in bytes?

https://gyazo.com/3692481bf94a77885fa0100b3b543e65

C:\adb>DIR
Directory of C:\adb

02/19/2018 12:43 AM <DIR> .
02/19/2018 12:43 AM <DIR> ..
10/23/2017 07:57 PM 347,456 aboot_vuln.mbn
01/11/2018 06:53 PM 1,784,320 adb.exe
01/11/2018 06:53 PM 97,792 AdbWinApi.dll
01/11/2018 06:53 PM 62,976 AdbWinUsbApi.dll
08/09/2015 01:50 PM 29,882 cmd-here.exe
02/26/2007 08:50 PM 342,016 dd.exe
01/11/2018 06:53 PM 853,504 fastboot.exe
02/04/2017 09:36 PM 318 get_code.bat
02/18/2018 05:56 PM 9,441,280 signed-thor-twrp-2870.img
02/16/2018 08:46 PM 8,978,432 thor-twrp-3.1.1-0.img
02/16/2018 09:09 PM 9,246,720 twrp_cubed.img
02/17/2018 03:29 PM 1,802 unins000.dat
02/17/2018 03:29 PM 717,985 unins000.exe
01/06/2017 06:49 PM 96 unlock.bat
02/19/2018 12:43 AM 0 unlock.code
15 File(s) 31,904,579 bytes
2 Dir(s) 308,310,306,816 bytes free

C:\adb>[/CODE]
 

DB126

Senior Member
Oct 15, 2013
15,270
10,046
https://gyazo.com/3692481bf94a77885fa0100b3b543e65

C:\adb>DIR
Directory of C:\adb

02/19/2018 12:43 AM <DIR> .
02/19/2018 12:43 AM <DIR> ..
10/23/2017 07:57 PM 347,456 aboot_vuln.mbn
01/11/2018 06:53 PM 1,784,320 adb.exe
01/11/2018 06:53 PM 97,792 AdbWinApi.dll
01/11/2018 06:53 PM 62,976 AdbWinUsbApi.dll
08/09/2015 01:50 PM 29,882 cmd-here.exe
02/26/2007 08:50 PM 342,016 dd.exe
01/11/2018 06:53 PM 853,504 fastboot.exe
02/04/2017 09:36 PM 318 get_code.bat
02/18/2018 05:56 PM 9,441,280 signed-thor-twrp-2870.img
02/16/2018 08:46 PM 8,978,432 thor-twrp-3.1.1-0.img
02/16/2018 09:09 PM 9,246,720 twrp_cubed.img
02/17/2018 03:29 PM 1,802 unins000.dat
02/17/2018 03:29 PM 717,985 unins000.exe
01/06/2017 06:49 PM 96 unlock.bat
02/19/2018 12:43 AM 0 unlock.code
15 File(s) 31,904,579 bytes
2 Dir(s) 308,310,306,816 bytes free

C:\adb>[/CODE]
Size of the file 'unclock.code' (0 bytes; effectively empty) indicates it was not successfully populated during prior run(s) of get_code.bat. While there are multiple ways to skin the cat I suggest the following:
- boot into Nexus
- verify adb bridge is enabled under settings -> developer options
- tether device; respond to any prompts (device and/or windows)
- open a Windows command prompt
- issue the following command: erase unlock.code
- validate connectivity with 'adb devices'
- run 'get_code.bat' (just type 'get_code' and press enter)
- issue the following command: dir unlock.code
- if length/size of unlock.code is 256 continue with following steps ...
- issue the following command: adb reboot bootloader
- validate connectivity with 'fastboot devices'
- issue the following command: fastboot -i 0x1949 flash unlock unlock.code

Post a screen description and/or screen snip of something fails or returns unexpected results.
 
  • Like
Reactions: draxie

hwwof

Member
May 28, 2015
34
2
Size of the file 'unclock.code' (0 bytes; effectively empty) indicates it was not successfully populated during prior run(s) of get_code.bat. While there are multiple ways to skin the cat I suggest the following:
- boot into Nexus
- verify adb bridge is enabled under settings -> developer options
- tether device; respond to any prompts (device and/or windows)
- open a Windows command prompt
- issue the following command: erase unlock.code
- validate connectivity with 'adb devices'
- run 'get_code.bat' (just type 'get_code' and press enter)
- issue the following command: dir unlock.code
- if length/size of unlock.code is 256 continue with following steps ...
- issue the following command: adb reboot bootloader
- validate connectivity with 'fastboot devices'
- issue the following command: fastboot -i 0x1949 flash unlock unlock.code

Post a screen description and/or screen snip of something fails or returns unexpected results.

Code:
C:\adb>adb devices
List of devices attached
D0FBA0A0351401GB        device


C:\adb>erase unlock.code

C:\adb>adb devices
List of devices attached
D0FBA0A0351401GB        device


C:\adb>get_code.bat
adb: error: cannot stat 'cuber': No such file or directory
Unable to open /data/local/tmp/cuber: No such file or directory
0x000045 0x09c8805d
/system/bin/sh: /data/local/tmp/cuber: not found
/data/local/tmp/unlock.code: 1 file pulled.
rm failed for /data/local/tmp/cuber, No such file or directory
Press any key to continue . . .

C:\adb>dir unlock.code
 Volume in drive C is OS
 Volume Serial Number is B684-989C

 Directory of C:\adb

02/19/2018  09:43 PM                 0 unlock.code
               1 File(s)              0 bytes
               0 Dir(s)  308,308,631,552 bytes free

C:\adb>
 
Last edited:

draxie

Senior Member
Apr 20, 2014
508
611
Code:
C:\adb>adb devices
List of devices attached
D0FBA0A0351401GB        device


C:\adb>erase unlock.code

C:\adb>adb devices
List of devices attached
D0FBA0A0351401GB        device


C:\adb>get_code.bat
adb: error: cannot stat 'cuber': No such file or directory
Unable to open /data/local/tmp/cuber: No such file or directory
0x000045 0x09c8805d
/system/bin/sh: /data/local/tmp/cuber: not found
/data/local/tmp/unlock.code: 1 file pulled.
rm failed for /data/local/tmp/cuber, No such file or directory
Press any key to continue . . .

C:\adb>dir unlock.code
 Volume in drive C is OS
 Volume Serial Number is B684-989C

 Directory of C:\adb

02/19/2018  09:43 PM                 0 unlock.code
               1 File(s)              0 bytes
               0 Dir(s)  308,308,631,552 bytes free

C:\adb>

You're missing a file named 'cuber' that should've been part of 'unlock.zip'.
Note that 'cuber' didn't show up in the listing you posted, either...
Try to extract that file and run 'get_code' again!

You can replace the last 3 steps in the previous post
- issue the following command: adb reboot bootloader
- validate connectivity with 'fastboot devices'
- issue the following command: fastboot -i 0x1949 flash unlock unlock.code

by simply running 'unlock.bat', since that's almost exactly what that
command does (except for the '-i 0x1949', which shouldn't be necessary
on Windows).
 
Last edited:

hwwof

Member
May 28, 2015
34
2
You're missing a file named 'cuber' that should've been part of 'unlock.zip'.
Note that 'cuber' didn't show up in the listing you posted, either...
Try to extract that file and run 'get_code' again!

You can replace the last 3 steps in the previous post
- issue the following command: adb reboot bootloader
- validate connectivity with 'fastboot devices'
- issue the following command: fastboot -i 0x1949 flash unlock unlock.code

by simply running 'unlock.bat', since that's almost exactly what that
command does (except for the '-i 0x1949', which shouldn't be necessary
on Windows).

...I can't believe that this whole time it's just been a missing file. rip me. Thank you so much. it says that the "unlock code is correct". How do I proceed from here to properly install AEX without messing my device up? Also, since the Nexus ROM had SuperSU and that means I'm rooted now, how do I work with OpenGapps and Magisk? @Davey216
 
Last edited:

DB126

Senior Member
Oct 15, 2013
15,270
10,046
You're missing a file named 'cuber' that should've been part of 'unlock.zip'.
Note that 'cuber' didn't show up in the listing you posted, either...
Try to extract that file and run 'get_code' again!
Nice work, @draxie. You are annoyingly consistent at ferreting out root (or something close to root) cause whether the 'problem' is simple or complex. :)

You can replace the last 3 steps in the previous post
- issue the following command: adb reboot bootloader
- validate connectivity with 'fastboot devices'
- issue the following command: fastboot -i 0x1949 flash unlock unlock.code

by simply running 'unlock.bat', since that's almost exactly what that
command does (except for the '-i 0x1949', which shouldn't be necessary
on Windows).
As you probably guessed I broke down the 'unlock.bat' file as it appeared to be failing based on screen snips shared by the poster. Completely overlooked the missing 'cuber' file ... although that only became fully apparent with the last set of snips (although there was an earlier clue as you alluded).
 
  • Like
Reactions: draxie

8675Thr

New member
Dec 14, 2018
1
0
Hello. Forgive the necro, but I've repeated the exact mistake made by hwwof: not extracting the cuber file to C:/adb (the unlock guide did not say to do so, only the .bat files) and receiving an empty unlock.code file.

Additional wrinkle: I cannot seem to boot into TWRP. Holding power+volume up just boots into fastboot as normal. The person I inherited the device from did report having nonfunctional sound, so it is a possibility that the volume up button is simply shot. What (if any) are my options here?

Command prompt log:
Code:
C:\adb>adb reboot bootloader

C:\adb>fastboot -i 0x1949 erase aboot
erasing 'aboot'...
OKAY [  0.052s]
finished. total time: 0.053s

C:\adb>fastboot -i 0x1949 reboot
rebooting...

finished. total time: 0.021s

C:\adb>wmic partition where index=22 get diskindex
DiskIndex
8


C:\adb>wmic partition where (index=17 and numberofblocks=20480) get diskindex
DiskIndex
8


C:\adb>wmic partition where (index=5 and numberofblocks=4096) get diskindex
DiskIndex
8


C:\adb>dd of=\\?\Device\Harddisk8\Partition6 if=emmc_appsboot-13.3.2.3.2_user_323001720.mbn
rawwrite dd for windows version 0.5.
Written by John Newbigin <[email protected]>
This program is covered by the GPL.  See copying.txt for details
Error reading file: 87 The parameter is incorrect
678+1 records in
678+1 records out

C:\adb>dd of=\\?\Device\Harddisk8\Partition18 if=thor_twrp-3.2.3-1.img
rawwrite dd for windows version 0.5.
Written by John Newbigin <[email protected]>
This program is covered by the GPL.  See copying.txt for details
18120+0 records in
18120+0 records out

C:\adb>unlock.bat
error: device '(null)' not found
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
FAILED ()
finished. total time: 0.001s
Press any key to continue . . .
 
Last edited:

draxie

Senior Member
Apr 20, 2014
508
611
(the unlock guide did not say to do so, only the .bat files)

Another case of blind leading the sightless.... (-;


Additional wrinkle: I cannot seem to boot into TWRP. Holding power+volume up just boots into fastboot as normal. The person I inherited the device from did report having nonfunctional sound, so it is a possibility that the volume up button is simply shot. What (if any) are my options here?

You may be able to apply pressure to the right place to revive the volume keys.
There's a thread (or two) on that somewhere. Unfortunately, I don't have a link.
If that doesn't work, you can always disassemble the device, re-seat the connector,
and put it back together.
 

Chrisrokc1

New member
Jan 3, 2019
3
0
Another case of blind leading the sightless.... (-;




You may be able to apply pressure to the right place to revive the volume keys.
There's a thread (or two) on that somewhere. Unfortunately, I don't have a link.
If that doesn't work, you can always disassemble the device, re-seat the connector,
and put it back together.

I have this same issue with one of mine, except the volume buttons do work on mine. If I hold the + it takes me to a screen with the Kindle Fire logo. If I hold the - it takes me to Fastboot. If I don't use the + OR - it takes me to Fastboot.

Should have understood the instructions better to know the unlock.code was incorrect before proceeding.

Suggestions?
 

DB126

Senior Member
Oct 15, 2013
15,270
10,046
I have this same issue with one of mine, except the volume buttons do work on mine. If I hold the + it takes me to a screen with the Kindle Fire logo. If I hold the - it takes me to Fastboot. If I don't use the + OR - it takes me to Fastboot.

Should have understood the instructions better to know the unlock.code was incorrect before proceeding.

Suggestions?
Answered here: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post78585887
 

wave_sailor

Senior Member
Sep 1, 2010
142
6
I am at fastboot step (get_code worked and I can see the unlock file), but my device manager shows Other Devices -> ! Android. I try changing driver to Fire by letting it search, but it doesn't find anything. I tried pointing to c:\adb, but it doesn't find anything there either. I reran the driver install and that works ok, but Android doesn't change to Fire Device.

adb devices list is blank.
 

irfan67670

New member
Sep 22, 2021
4
0
I am at fastboot step (get_code worked and I can see the unlock file), but my device manager shows Other Devices -> ! Android. I try changing driver to Fire by letting it search, but it doesn't find anything. I tried pointing to c:\adb, but it doesn't find anything there either. I reran the driver install and that works ok, but Android doesn't change to Fire Device.

adb devices list is blank.
I have the same problem here. Tried many windows reboots, different versions of adb fastboot drivers. Kindle boots fine into fastboot and says Ready, but windows cannot use any driver for it.
HDX7 3rd Gen
 

DB126

Senior Member
Oct 15, 2013
15,270
10,046
I have the same problem here. Tried many windows reboots, different versions of adb fastboot drivers. Kindle boots fine into fastboot and says Ready, but windows cannot use any driver for it.
HDX7 3rd Gen
Use drivers included with Motorola Device Manager 2.5.x; my goto for many years. Don't need to do anything with the manager itself; just install to get the drivers.

That said, not an instant panacea for all. Windows is a finiky platform; you'll have to experiment and read to find the elixure that works for you.

Don't asks for download link or other help; I moved on from this device. My 7 years of posts have all the details. Good luck.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I’ve been lurking on these forums for a while and I have decided that I’m willing to take the risk to unlock my Thor’s potential. I have made sure to read through advised reading materials, and searching through other posts before posting. (I tried figuring out how to quote multiple posts to make this thread easier to navigate but I couldn't, sorry)

    Device: Kindle Fire HDX 7” 3rd Generation running Fire OS 4.5.5.3
    I will be using a Windows 10 Home machine to do this.

    Purpose: Allow for the device to work well in Google’s ecosystem so I can have a useful device for medical school.
    I am currently trying to learn the steps outlined here, but I have some concerns:

    • Does it matter whether or not I factory reset my device before I begin?
    • Will my computer’s OS cause any issues? According to this, there might be some driver issues? Should I download the “Motorola Device manager”?
    • Where is the “aboot_vuln.mbn” file? Do I obtain it once I follow the steps in order?
    • I want to use “Minimal ADB and Fastboot” instead of the attached “15 seconds ADB Installer v1.4.3” because the later has not been updated in a while and the former was updated this month. According to the install instructions for the former, I need to have my device already plugged in and the “kindle fire USB driver” already installed. Will this affect step 4 of the procedure or anything else?
    • On step 5, am I correct in my assumption that changing the driver will be a simple few click process?
    • On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
    • Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
    • What ROM do you recommend for my needs? And could you provide me a link to the correct download/discussion board? I would prefer a ROM running at least Nougat that has long-term support planned. I read that “Fire Nexus ROM” is pretty basic, so I don’t think I want it. As of now, I’m looking at CM/Lineage 14.1, but I don’t know what ROM would work on my device from the website. AospExtended seems like a good option but apparently, there are wi-fi issues which are a deal-breaker.
    Thank you so much for reading through this. Hopefully all my research and proves to be useful for anyone trying to help. If I’m able to get this working cleanly, I would be willing to make a cleaned up guide for this version and device to better aid future people.
    2
    I’ve been lurking on these forums for a while and I have decided that I’m willing to take the risk to unlock my Thor’s potential. I have made sure to read through advised reading materials, and searching through other posts before posting. (I tried figuring out how to quote multiple posts to make this thread easier to navigate but I couldn't, sorry)

    Device: Kindle Fire HDX 7” 3rd Generation running Fire OS 4.5.5.3
    I will be using a Windows 10 Home machine to do this.

    Purpose: Allow for the device to work well in Google’s ecosystem so I can have a useful device for medical school.

    Hello @hwwof -

    You have done your homework (thank you!) and presented reasonable questions. I'm going to answer the first five 'in-line' below. Responses will be brief to keep the thread serviceable for those accessing XDA content on small screens; don't read anything into that. Bounce back on any items that need further elaboration.

    I am currently trying to learn the steps outlined here, but I have some concerns:

    Does it matter whether or not I factory reset my device before I begin?
    No; however, it would be better if you did NOT reset the device.

    Will my computer’s OS cause any issues? According to this, there might be some driver issues? Should I download the “Motorola Device manager”?
    Nope. Drivers installed via the Motorola Device manager are properly signed which mitigates any potential issues on 64-bit Win 10 builds (yet another reason to use the Moto drivers vs others that have been posted)

    Where is the “aboot_vuln.mbn” file? Do I obtain it once I follow the steps in order?
    It's contained within aboot-13-thor.zip; just named differently.

    I want to use “Minimal ADB and Fastboot” instead of the attached “15 seconds ADB Installer v1.4.3” because the later has not been updated in a while and the former was updated this month. According to the install instructions for the former, I need to have my device already plugged in and the “kindle fire USB driver” already installed. Will this affect step 4 of the procedure or anything else?
    Good idea. Your device does not need to be tethered while installing Minimal ADB and Fastboot. Take note of where the package is installed (typically "C:\Program Files (x86)\Minimal ADB and Fastboot") and practice opening a command window focused in that folder. To make life simpler you can direct the installer to place the files in "c:\work" which is a lot easier to type.

    On step 5, am I correct in my assumption that changing the driver will be a simple few click process?
    Yes - but here's were it gets interesting and a bit frustrating. Even with the Moto drivers Windows can be very fussy communicating with HDX devices. To complicate matters there are two modes to deal with: ADB and Fastboot. You'll learn which is which as time goes on and will likely have to switch Windows drivers for each mode. Sometimes a reboot is needed to get everyone talking. Note there is no danger involved simply tethering your device and issuing basic queries.

    To test basic ADB communications:
    - execute step #2 (only) from the linked procedure
    - open a Windows command prompt as outlined above
    - boot HDX into FireOS and move past the screen lock
    - tether device to windows; take note of any noises and/or confirmation messages
    - in the window command prompt issue the command "adb devices" and press Enter. What happens?

    Post back results and we'll go from there.
    2
    Thank you @Davey126 . I appreciate you taking the time to help me out. Answers to the other questions would be very appreciated as well!
    Second response is positive. Next issue the following command: 'adb reboot bootloader'. This will place your device in fastboot mode. If you are very lucky a 'Ready' prompt will appear on the device below the word 'fastboot'. Most likely you will need to head to Windows Device Manager, identify which entry is associated with the tethered HDX and then change the device driver to 'Moto Composite' or something similar (might not have the wording exactly right). Once you get a 'Ready' prompt issue the following command: 'fastboot devices'. If you get a response similar to 'adb devices' then you are good to go.

    Hints/tips:
    - to help determine which entry(s) are associated with your HDX tether/untether your device while Windows Device Manager is open
    - right click an entry to change the device driver; navigate 'Browse my computer ...' -> 'Let me pick ...'; do not choose any of the automated options
    - if you can't get a Ready prompt and/or an response to 'fastboot devices' reboot both devices and try again
    - if still no joy change USB ports and cables; the latter are especially problematic (people never believe that until trying 1821 other things - ugh!)

    Report back and we'll go from there. I know you prefer the rest of your questions answered up front. Experience suggests an incremental approach is more productive - for you, me and future readers.
    2
    Thank you! Now it says "ready" but I'm concerned about how to unplug it without messing anything up. here's the output:
    {content removed}
    You are correct that I would prefer having all the answers upfront, but it's only so I can then question the answers to get a better understanding before messing with the device. A quick reply would be appreciated!
    Great!! The purpose of this exercise was to validate connectivity in two different modes and, if needed, provide a safe 'test' environment for remediation. No worries about breaking the tether if there is no active data transfer taking place. Simply unplug and then long press <power> until the device shuts down.

    In response to your other questions:
    Q: On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
    A: Follow the steps as quoted

    Q: Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
    A1: You should assume all content on your device will be erased following completion of Step #9 (although it will likely remain intact)
    A2: The two files you will be 'flashing' with the dd command should be located in the same folder as "Minimal ADB and Fastboot"
    A3: Deal with that later (flashing ROM)

    Q: ROMs:
    A: All of the Nougat based custom ROMs for HDX are stable and feature complete. Nuances are subtle and probably not worth worrying about now; you can always change later. My personal preference is AEX (AospExtended). That said, Lineage 14.1 and Slim 7 are both excellent alternatives.
    1
    So I completed the instructions, booted to TWRP, turned it off, booted up, did the unlock batch, but I didn't get "unlock code is correct". I got a lot of green lines "getvar slot-count...OK getvar:slot-suffixes...OK getvar:has-slot:unlock...OK getvarartition-type:unlock...OK getvar:max-download-size...[[0x20000000 ]] download:00000000..." Here's the cmd when I try running unlock.bat https://gyazo.com/a041dc49c786f9846d706c049eacbbf3

    Did I mess something up or am I unlocked? I'm not sure what to do from here. I was still able to get back to TWRP. It's telling me to swipe to allow modifications or to keep read only. Where do I proceed from here? I'm reading in some places to wipe before installing, and a lot of other conflicting information. I downlaoded the AEX november build and would like to flash it. Do I have any need for rooting or SuperSU?

    Again, Thank you so much for all your help
    Device is NOT unlocked. Tied up for the next hour or two; will respond then. Do not wipe or attempt to flash anything. Sorry for wait ...