How to root and unlock the HDX for noobies

[ticketz]

Hi guys,

i think i bricked my device, at least i am stuck at fastboot after step 4.

all was fine until i started task 4. since i had the "cannot open for read: No such file or directory" message i started the "extra work needed". after adb push of "aboot" and "twrp" i restarted the device.

i started then again with "dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
/dev/block/platform/msm_sdcc.1/by-name/recovery <"

and then
"dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
/dev/block/platform/msm_sdcc.1/by-name/aboot <"

but both times the numbers of the records in and out did not match with the ones in the description of the task.

Since it got late i wanted to stop again and try at some other time. sadly now i am stuck at the fastboot screen when i try to reboot the kindle fire.

when i plugg it to the pc it get recognized and get the "ready" on screen but can not find it by "adb devices". anything i can do?

best regards

 

[gwardsc65]

Hi guys,

i think i bricked my device, at least i am stuck at fastboot after step 4.

all was fine until i started task 4. since i had the "cannot open for read: No such file or directory" message i started the "extra work needed". after adb push of "aboot" and "twrp" i restarted the device.

i started then again with "dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
/dev/block/platform/msm_sdcc.1/by-name/recovery <"

and then
"dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
/dev/block/platform/msm_sdcc.1/by-name/aboot <"


but both times the numbers of the records in and out did not match with the ones in the description of the task.

Since it got late i wanted to stop again and try at some other time. sadly now i am stuck at the fastboot screen when i try to reboot the kindle fire.

when i plugg it to the pc it get recognized and get the "ready" on screen but can not find it by "adb devices". anything i can do?

best regards

Did you run the unlock.bat file to unlock the bootloader and get the Unlock code is correct in green shown on the HDX screen?

If not, in fastboot mode with the HDX indicating ready. (brighter white) , type the following:

fastboot flash unlock unlock.code

If you replaced recovery and aboot correctly, the bootloader should now be unlocked after issuing the above command.

If the bootloader is already unlocked and thor_twrp-3.2.3-1.img is in the same folder as your fastboot.exe file, you can issue the following to get into recovery mode:

fastboot boot thor_twrp-3.2.3-1.img

Once in recovery flash whatever custom rom you want.

adb commands do not work when in fastboot mode.

 

[ticketz]

AWESOME! that worked. Thank you very much. so happy with the tablet now!

 

[yumsty]

My device is in a boot loop and I am unable to even connect to adb. The device does not show up on device manager either. I have tried installing the device drivers given but it still does not show up. Any help would be appreciated, Thanks.

 

[gwardsc65]

My device is in a boot loop and I am unable to even connect to adb. The device does not show up on device manager either. I have tried installing the device drivers given but it still does not show up. Any help would be appreciated, Thanks.

Not sure I can help much as I don't remember much about Safestrap. I think the first thing you must do is to get your HDX to communicate with your computer. 1-Click would probably be your best choice once you get the HDX and comptuer communicating. 1-Click, Bulk Mode, and this thread will not work otherwise. Can you get into recovery mode at all? Maybe the computer will be able recognize the HDX so you could at least load some files to internal storage and Install CM11 again??

 

[yumsty]

Not sure I can help much as I don't remember much about Safestrap. I think the first thing you must do is to get your HDX to communicate with your computer. 1-Click would probably be your best choice once you get the HDX and comptuer communicating. 1-Click, Bulk Mode, and this thread will not work otherwise. Can you get into recovery mode at all? Maybe the computer will be able recognize the HDX so you could at least load some files to internal storage and Install CM11 again??

I can get it into fire system recovery and I reset to default but it still does not seem to be able to communicate with my computer.

 

[gwardsc65]

I can get it into fire system recovery and I reset to default but it still does not seem to be able to communicate with my computer.

Only other suggestion I can offer, is to try different usb cables and/or computer.

 

[Plektrum]

confused noob

Hello,
Davey126 was kind enough to link me to this thread but I still just can't figure out how to proceed. I have read all the posts here and downloaded all the files and yet I have no idea what to do.

I own a Kindle Nexus HDX 7 (2013, 32 GB) and currently the Nexus Rom (Android 4.2.2) and Safetrap 3.75 (TWRP v2.7.1.0) are installed. Dave126 sent me 2 links - one to this thread, the other to Multi-platform 1-Click bootloader unlock for *ANY* 3rd Gen HDX (with VirtualBox). However, as it is stated within the text of the second link that it "Does NOT work on Windows" I guess there is no use in following the instructions there. So I guess I have to follow the steps described in this thread. Do I have to uninstall Safetrap/the custom rom first? If so, how do I do that? I'm super sorry for being such a noob. Any kind of constructive feedback is welcome. Thanks a lot - also for making this thread in general. =)

 

[gwardsc65]

Hello,
Davey126 was kind enough to link me to this thread but I still just can't figure out how to proceed. I have read all the posts here and downloaded all the files and yet I have no idea what to do.

I own a Kindle Nexus HDX 7 (2013, 32 GB) and currently the Nexus Rom (Android 4.2.2) and Safetrap 3.75 (TWRP v2.7.1.0) are installed. Dave126 sent me 2 links - one to this thread, the other to Multi-platform 1-Click bootloader unlock for *ANY* 3rd Gen HDX (with VirtualBox). However, as it is stated within the text of the second link that it "Does NOT work on Windows" I guess there is no use in following the instructions there. So I guess I have to follow the steps described in this thread. Do I have to uninstall Safetrap/the custom rom first? If so, how do I do that? I'm super sorry for being such a noob. Any kind of constructive feedback is welcome. Thanks a lot - also for making this thread in general. =)

I would like to help you out, but it would be better for Davey to answer where you should start from. I don't remember much about Safestrap and don't want you to get started off wrong. I may be able to help later on, if you need it. Wasn't there slots for a custom rom and Amazon stock? Do you have root access? Do you have adb access?

No matter where you start from, you can still get the necessary files organized, get adb and fastboot working and get the unlock code ready.

 

[gwardsc65]

Hello,
Davey126 was kind enough to link me to this thread but I still just can't figure out how to proceed. I have read all the posts here and downloaded all the files and yet I have no idea what to do.

I own a Kindle Nexus HDX 7 (2013, 32 GB) and currently the Nexus Rom (Android 4.2.2) and Safetrap 3.75 (TWRP v2.7.1.0) are installed. Dave126 sent me 2 links - one to this thread, the other to Multi-platform 1-Click bootloader unlock for *ANY* 3rd Gen HDX (with VirtualBox). However, as it is stated within the text of the second link that it "Does NOT work on Windows" I guess there is no use in following the instructions there. So I guess I have to follow the steps described in this thread. Do I have to uninstall Safetrap/the custom rom first? If so, how do I do that? I'm super sorry for being such a noob. Any kind of constructive feedback is welcome. Thanks a lot - also for making this thread in general. =)

I briefly looked at the Safestrap thread and I don't see any reason to uninstall anything. Just start from where you are. Safestrap is just a modified twrp recovery image over which you will flash the latest twrp recovery image, so that shouldn't be a problem. Any slots you may have created and the modified boot image will be over written when you flash a custom rom after unlocking the bootloader. I don't see a problem there either.

Your biggest challenge will be to get adb and fastboot working correctly, should be fairly easy after that. Start with Task 1 and work through the other Tasks, skipping through those you don't need (should have root access already, if I understood the Safestrap thread correctly).

 

[DB126]

I briefly looked at the Safestrap thread and I don't see any reason to uninstall anything. Just start from where you are. Safestrap is just a modified twrp recovery image over which you will flash the latest twrp recovery image, so that shouldn't be a problem. Any slots you may have created and the modified boot image will be over written when you flash a custom rom after unlocking the bootloader. I don't see a problem there either.

Your biggest challenge will be to get adb and fastboot working correctly, should be fairly easy after that. Start with Task 1 and work through the other Tasks, skipping through those you don't need (should have root access already, if I understood the Safestrap thread correctly).

Guidance is spot on. Just a minor clairification: Safestrap lives in the system and emulates TWRP - but isn't a true recovery. Stock recovery remains intact and can be invoked in the usual manner.

If FireOS remains in slot 0 SafeStrap can be uninstalled. However, there really isn't a need as bootloader unlock procedure is agnostic to currently installed ROM.

 

[paoxayla]

first, thanks for the guide and for the time

i have a simple question, when i get to the adb command state, where it says ready after step 1, when i type anything including adb devices, it doesnt recognize any devices even tho it says ready
but if i run the "unlock" batch file in my adb folder i can see something happening in the hdx

 

[gwardsc65]

first, thanks for the guide and for the time

i have a simple question, when i get to the adb command state, where it says ready after step 1, when i type anything including adb devices, it doesnt recognize any devices even tho it says ready
but if i run the "unlock" batch file in my adb folder i can see something happening in the hdx

I need more details before I can help you out. Step 1 is from where? Ready where? On your computer or the HDX? Are you sure adb and fastboot are working correctly? Have you replaced aboot and recovery before trying to unlock the bootloader ( i run the "unlock" batch file in my adb folder)? I have no idea where you are at in this process. Help me out a little. Lol.

 

[player594]

When I run get_code.bat I get this in cmd

adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
Press any key to continue . . .

And if I open cmd and run >adb get_code I get a 7kb file named get_code in the adb folder with no text in cmd. The file has no ext what so ever.
Any ideas?

 

[paoxayla]

I need more details before I can help you out. Step 1 is from where? Ready where? On your computer or the HDX? Are you sure adb and fastboot are working correctly? Have you replaced aboot and recovery before trying to unlock the bootloader ( i run the "unlock" batch file in my adb folder)? I have no idea where you are at in this process. Help me out a little. Lol.

sorry i didnt gave much details, i'll try to explain better what happened.

i followed exactly what it said in steps 1

i created a folder with files from "thor unlock files" and "adb and fastboot", using windows tool a started the cmd of this folder and the device was recognized using "adb devices" command(i also installed the drivers), after that i initiated fatboot mode but it didnt said "ready" on the device like it's supposed to be, than i updated the drivers like it said in the word file and the ready line was in the hdx device, everything good so far.

after that the device don't recognize any commands from cmd anymore, when i type "adb devices" it dosn't say anything basically, not even that the device is not recognized.

"Have you replaced aboot and recovery before trying to unlock the bootloader", maybe i missed this step, how should i do this? sorry

thanks for the help!

 

[gwardsc65]

sorry i didnt gave much details, i'll try to explain better what happened.

i followed exactly what it said in steps 1

i created a folder with files from "thor unlock files" and "adb and fastboot", using windows tool a started the cmd of this folder and the device was recognized using "adb devices" command(i also installed the drivers), after that i initiated fatboot mode but it didnt said "ready" on the device like it's supposed to be, than i updated the drivers like it said in the word file and the ready line was in the hdx device, everything good so far.

after that the device don't recognize any commands from cmd anymore, when i type "adb devices" it dosn't say anything basically, not even that the device is not recognized.

"Have you replaced aboot and recovery before trying to unlock the bootloader", maybe i missed this step, how should i do this? sorry

thanks for the help!

Still not sure where you are or doing. Will make some guesses. Task 1 was to get adb and fastboot working correctly. It appears that you accomplished that. You state the HDX is recognized when you issue the command adb devices. If the get_code.bat was issued while in adb mode it should get you the unlock.code. I assume in the previous post you were not in adb mode but perhaps fastboot mode.

adb commands only work in adb mode (and sometimes in recovery mode)
fastboot commands only work in fastboot mode

It appears you has accomplished Task 1 and 2. Have you rooted the HDX as per Task 3 or other means? I can only suggest you follow through each Task and not skip around. You look to be close, especially if adb and fastboot are working correctly.

 

[player594]

Still not sure where you are or doing. Will make some guesses. Task 1 was to get adb and fastboot working correctly. It appears that you accomplished that. You state the HDX is recognized when you issue the command adb devices. If the get_code.bat was issued while in adb mode it should get you the unlock.code. I assume in the previous post you were not in adb mode but perhaps fastboot mode.

adb commands only work in adb mode (and sometimes in recovery mode)
fastboot commands only work in fastboot mode

It appears you has accomplished Task 1 and 2. Have you rooted the HDX as per Task 3 or other means? I can only suggest you follow through each Task and not skip around. You look to be close, especially if adb and fastboot are working correctly.

Are you saying that the get_code should be done before going into fastboot mode or after? Because following the guide reads like doing it in fastboot mode.

 

[gwardsc65]

Are you saying that the get_code should be done before going into fastboot mode or after? Because following the guide reads like doing it in fastboot mode.

I recommend you get the unlock code as soon as you have adb and fastboot working correctly on your computer. Now to confuse you some more perhaps.

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

Indicates adb is working

C:\adb>get_code
cuber: 1 file pushed. 7.7 MB/s (506072 bytes in 0.062s)
/system/bin/sh: cat: /sys/class/block/mmcblk0/device/manfid: Permission denied
/system/bin/sh: cat: /sys/class/block/mmcblk0/device/serial: Permission denied

/data/local/tmp/unlock.code: 1 file pulled.
Press any key to continue . . .

Indicates the unlock.code file has been created and should be in the C:\adb> directory

Before doing this

C:\adb>unlock

you should have rooted the HDX and replaced the aboot and recovery partitions

I guess I didn't answer your question. Before. Run get_code in adb mode, it will not work in fastboot mode.

 

[player594]

I recommend you get the unlock code as soon as you have adb and fastboot working correctly on your computer. Now to confuse you some more perhaps.

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

Indicates adb is working

C:\adb>get_code
cuber: 1 file pushed. 7.7 MB/s (506072 bytes in 0.062s)
/system/bin/sh: cat: /sys/class/block/mmcblk0/device/manfid: Permission denied
/system/bin/sh: cat: /sys/class/block/mmcblk0/device/serial: Permission denied

/data/local/tmp/unlock.code: 1 file pulled.
Press any key to continue . . .

Indicates the unlock.code file has been created and should be in the C:\adb> directory

Before doing this

C:\adb>unlock

you should have rooted the HDX and replaced the aboot and recovery partitions

I guess I didn't answer your question. Before. Run get_code in adb mode, it will not work in fastboot mode.

Ok I got the unlock.code now but I can't get it to root

 

[gwardsc65]

Ok I got the unlock.code now but I can't get it to root

Sorry about the last post, I thought I was answering someone else. The last sentence would have answered your question. I guess you should start with Task 1 and work through the rest of the Tasks. Best I can do for now as I have no way of knowing what you are doing or have done already.