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

Multi-platform 1-Click bootloader unlock for *ANY* 3rd Gen HDX (with VirtualBox)

Search This thread

mbuck2019

Member
Jan 2, 2019
18
3
Hi,

I have acquired a Kindle Fire HDX 8.9" 3rd Gen 64GB Wifi + LTE. I would like to get rid of FireOS 4.5.5.3. Is there any ROM that supports LTE ? I have successfully replaced FireOS by AospExtended-v4.6-thor in the past on a HDX 7" (non-LTE) but this time I have a 8.9" version with LTE. Before I brick the device, I just want to know if anyone has done it and get LTE to work.

Thanks a lot
m
 

superbloomie

New member
Feb 9, 2018
1
0
Appreciate you publishing this -- tool works great (after I re-read the instructions and actually followed them!)

Happy to finally put my old HDX back to use as an excellent home assistant tablet with fully kiosk browser.
 

mbuck2019

Member
Jan 2, 2019
18
3
Hi, I've got a KFHDX 7 32GB (3rdGen) on which I have replaced FireOS 4.5.5.3 with LOS16 using the 1-Click method from Draxie. The annoying issue I've been struggling with is the tablet keeps freezing randomly. I know it's not related to memory as it freezes also in TWRP recovery main screen (I can swipe halfway and it jerks back). I have tried to replace LOS by AOSPExtended4.6, same issue. I decided to give up and go back to FireOS 4.5.5.3, but, at some point I had tried to wipe everything (including system) when trying to fix the freeze. So I lost my FireOS backup. Now I don't have Amazon System Recovery (3e) when booting into fastboot. I have tried to put the FireOS firmware on the device renaming it from .bin to .zip and used TWRP to install it, it won't do it - it complains about the device is an omni-thor whereas the update is a thor. I could not find a workaround for that on the forum. Can somebody kindly let me know the steps to revert back to FireOS 4.5.5.3? Thanks a lot for your help.
 

draxie

Senior Member
Apr 20, 2014
508
610
Hi, I've got a KFHDX 7 32GB (3rdGen) on which I have replaced FireOS 4.5.5.3 with LOS16 using the 1-Click method from Draxie. The annoying issue I've been struggling with is the tablet keeps freezing randomly. I know it's not related to memory as it freezes also in TWRP recovery main screen (I can swipe halfway and it jerks back). I have tried to replace LOS by AOSPExtended4.6, same issue. I decided to give up and go back to FireOS 4.5.5.3, but, at some point I had tried to wipe everything (including system) when trying to fix the freeze. So I lost my FireOS backup. Now I don't have Amazon System Recovery (3e) when booting into fastboot. I have tried to put the FireOS firmware on the device renaming it from .bin to .zip and used TWRP to install it, it won't do it - it complains about the device is an omni-thor whereas the update is a thor. I could not find a workaround for that on the forum. Can somebody kindly let me know the steps to revert back to FireOS 4.5.5.3? Thanks a lot for your help.
I'm trying to attach my back2stock script without much success...
Alright... putting it in a ZIP archive did the trick...

NB: this goes fully stock, including recovery (i.e. you'll lose TWRP).
 

Attachments

  • back2stock.zip
    1 KB · Views: 8
Last edited:

mbuck2019

Member
Jan 2, 2019
18
3
Thanks a lot Draxie! So I take it I can use the current TWRP 3.5.0_9.1 to install that zip? Is that right?

cheers

Update: Ok, I opened up the script, so it looks like I just have to open up a terminal window in TWRP and execute back2stock UPDATE.BIN (where UPDATE.BIN = update-kindle-13.4.5.5_user_455007020.bin) , that's it? Sorry, just being careful before I cause chaos :)
 
Last edited:

draxie

Senior Member
Apr 20, 2014
508
610
Thanks a lot Draxie! So I take it I can use the current TWRP 3.5.0_9.1 to install that zip? Is that right?
I'd surely hope so; although you should start
with the Kindle booted as normal
(i.e. NOT in recovery/TWRP).

Update: Ok, I opened up the script, so it looks like I just have to open up a terminal window in TWRP and execute back2stock UPDATE.BIN (where UPDATE.BIN = update-kindle-13.4.5.5_user_455007020.bin) , that's it? Sorry, just being careful before I cause chaos :)
The script uses adb to communicate with both the normal Android-like OS (FireOS, LOS, etc.)
and TWRP and as such it should be run on a box with a Unix-like OS (Linux/MacOS/WSL) and have
bash, adb, and zip/unzip installed.

The tablet itself should be in normal OS mode to start with,
but it will get rebooted to TWRP during the process.


BTW, if all you want is a way to tweak the original update so that TWRP won't refuse to install it,
then extract META-INF/com/google/android/updater-script, remove any line
starting with getprop, and refresh the archive with the updated script.
Essentially that's what these lines do (with variables properly set, followed by a clean-up)
Code:
# remove device checks, since ROM:s tend to change model name 
unzip -u -o "$1" $u
sed -i '/^getprop/d' $u
zip -u "$z" $u
 
Last edited:

mbuck2019

Member
Jan 2, 2019
18
3
I'm getting this permission error below. I can't see where it's doing a chmod in the script. Ideas?

$ ./back2stock UPDATE.BIN
+ '[' -r UPDATE.BIN ']'
+ u=META-INF/com/google/android/updater-script
+ p=recovery/recovery-from-boot.p
+ d=system/etc/recovery-resource.dat
+ a=boot.img
+ t=/data/local/tmp
+ e=/sdcard/rec.img
+ z=UPDATE.BIN.zip
+ x=mv
+ (( 1 < 1 ))
+ x='cp -u'
+ cp -u -v UPDATE.BIN UPDATE.BIN.zip
'UPDATE.BIN' -> 'UPDATE.BIN.zip'
+ unzip -u -o UPDATE.BIN.zip recovery/recovery-from-boot.p system/etc/recovery-resource.dat boot.img
Archive: UPDATE.BIN.zip
signed by SignApk
inflating: boot.img
inflating: recovery/recovery-from-boot.p
inflating: system/etc/recovery-resource.dat
+ for i in p d a
+ adb push -p recovery/recovery-from-boot.p /data/local/tmp/p
recovery/recovery-from-boot.p: 1 file ...hed. 4.2 MB/s (435857 bytes in 0.100s)
+ for i in p d a
+ adb push -p system/etc/recovery-resource.dat /data/local/tmp/d
system/etc/recovery-resource.dat: 1 fi...d. 11.3 MB/s (1286910 bytes in 0.108s)
+ for i in p d a
+ adb push -p boot.img /data/local/tmp/a
boot.img: 1 file pushed. 6.7 MB/s (7831552 bytes in 1.113s)
+ unzip -p UPDATE.BIN.zip recovery/etc/install-recovery.sh
+ read -a x
+ case ${x[0]}${x[1]} in
+ read -a x
+ case ${x[0]}${x[1]} in
+ read -a x
+ case ${x[0]}${x[1]} in
+ read -a x
+ case ${x[0]}${x[1]} in
+ x[2]=/data/local/tmp/d
+ x[3]=/data/local/tmp/a
+ x[4]=/sdcard/rec.img
+ x[7]=c9f4d9810aea3b8757c134a4a225b6f4b14d237b:/data/local/tmp/p
+ adb shell touch /sdcard/rec.img
+ adb shell applypatch -b /data/local/tmp/d /data/local/tmp/a /sdcard/rec.img 5fa6a58da1ef09fa62f5cc6bd275543b1852e210 9590784 c9f4d9810aea3b8757c134a4a225b6f4b14d237b:/data/local/tmp/p
patch /data/local/tmp/a: now 5fa6a58d
chmod of "/sdcard/rec.img.patch" failed: Operation not permitted


FYI

$ adb shell ls -l /sdcard/rec*
-rw-rw---- 1 root sdcard_rw 0 2021-08-03 16:38 /sdcard/rec.img
-rw-rw---- 1 root sdcard_rw 9590784 2021-08-03 16:38 /sdcard/rec.img.patch

Looks like it's failing to overwrite rec.img by rec.img.patch ??

adb shell mv $e.patch $e
 
Last edited:

draxie

Senior Member
Apr 20, 2014
508
610
I think that chmod is internal to the applypatch command.
I also believe that the error is inconsequential, except possibly that it stops the script due
to the -e flag requesting to abort on error. Try tagging on || :
at the end of the offending line (#40), and try again. In other words line 40, should look like this:
Code:
            adb shell "${x[@]}" || :

BTW, I also re-uploaded a new version with that change above; so, you could grab that instead.
 

draxie

Senior Member
Apr 20, 2014
508
610
Looks like it's failing to overwrite rec.img by rec.img.patch ??

adb shell mv $e.patch $e
No, actually, it never gets that far... it fails on the line before.

BTW, on LOS16, I'm getting an even funkier error message...
+ adb shell applypatch -b /data/local/tmp/d /data/local/tmp/a /sdcard/rec.img b1ae2379c94e1d59cb842138294a4f56d3854a1a 9590784 e0a43fa04c7572c26a1dde38dcfd510668749392:/data/local/tmp/p
patch /data/local/tmp/a: Supporting patching EMMC targets only.
So, I guess the "right" way to structure the script _could_ be to first install
the tweaked ZIP to get FireOS back, and use the original applypatch
command to fix recovery. AND, I suppose the latter could be made optional,
in case people prefer to keep TWRP instead (a wise choice, unless preparing to re-sell...)

Of course, doing so would require extra reboots which tend to freak out people.
 
Last edited:

mbuck2019

Member
Jan 2, 2019
18
3
Looks like it completed successfully. It rebooted in TWRP and all I did is I rebooted the kindle. It then started the FireOS and run through the setup. I think I have a hardware issue with this device. It's not responding to touch - it's erratic. I have to tap several times and even it won't type in my amazon's email address in one go. As if the digitizer has gone mad.

This "freezing" issue started after I had patch the device with LOS 16 for Thor. I had to go back to LOS 14 as I noticed the freeze. After that, I could not fix that freezing issue. By the way, before I used 1-Click (which worked flawlessly on 2 other devices I had done before), this device was working well without the freezing issue. Tbh, I don't know what could have happened. I thought going back to FireOS would resolve the problem, but sadly not.

I will paste the outputs of back2stock next (for reference).

Thanks a lot Draxie. If there is anything you can think of that would help, do let me know.
 

mbuck2019

Member
Jan 2, 2019
18
3
$ ./back2stock UPDATE.BIN
+ '[' -r UPDATE.BIN ']'
+ u=META-INF/com/google/android/updater-script
+ p=recovery/recovery-from-boot.p
+ d=system/etc/recovery-resource.dat
+ a=boot.img
+ t=/data/local/tmp
+ e=/sdcard/rec.img
+ z=UPDATE.BIN.zip
+ x=mv
+ (( 1 < 1 ))
+ x='cp -u'
+ cp -u -v UPDATE.BIN UPDATE.BIN.zip
+ unzip -u -o UPDATE.BIN.zip recovery/recovery-from-boot.p system/etc/recovery-resource.dat boot.img
Archive: UPDATE.BIN.zip
signed by SignApk
+ for i in p d a
+ adb push -p recovery/recovery-from-boot.p /data/local/tmp/p
recovery/recovery-from-boot.p: 1 file ...hed. 6.3 MB/s (435857 bytes in 0.066s)
+ for i in p d a
+ adb push -p system/etc/recovery-resource.dat /data/local/tmp/d
system/etc/recovery-resource.dat: 1 fi...d. 12.6 MB/s (1286910 bytes in 0.098s)
+ for i in p d a
+ adb push -p boot.img /data/local/tmp/a
boot.img: 1 file pushed. 7.4 MB/s (7831552 bytes in 1.012s)
+ unzip -p UPDATE.BIN.zip recovery/etc/install-recovery.sh
+ read -a x
+ case ${x[0]}${x[1]} in
+ read -a x
+ case ${x[0]}${x[1]} in
+ read -a x
+ case ${x[0]}${x[1]} in
+ read -a x
+ case ${x[0]}${x[1]} in
+ x[2]=/data/local/tmp/d
+ x[3]=/data/local/tmp/a
+ x[4]=/sdcard/rec.img
+ x[7]=c9f4d9810aea3b8757c134a4a225b6f4b14d237b:/data/local/tmp/p
+ adb shell touch /sdcard/rec.img
+ adb shell applypatch -b /data/local/tmp/d /data/local/tmp/a /sdcard/rec.img 5fa6a58da1ef09fa62f5cc6bd275543b1852e210 9590784 c9f4d9810aea3b8757c134a4a225b6f4b14d237b:/data/local/tmp/p
patch /data/local/tmp/a: now 5fa6a58d
chmod of "/sdcard/rec.img.patch" failed: Operation not permitted
+ :
+ adb shell mv /sdcard/rec.img.patch /sdcard/rec.img
+ read -a x
+ adb shell rm -f '/data/local/tmp/[pda]'
+ unzip -u -o UPDATE.BIN META-INF/com/google/android/updater-script
Archive: UPDATE.BIN
signed by SignApk
inflating: META-INF/com/google/android/updater-script
+ sed -i '/^getprop/d' META-INF/com/google/android/updater-script
+ zip -u UPDATE.BIN.zip META-INF/com/google/android/updater-script
updating: META-INF/com/google/android/updater-script
zip warning: Local Entry CRC does not match CD: META-INF/com/google/android/updater-script
(deflated 85%)
+ adb push -p UPDATE.BIN.zip /sdcard/
UPDATE.BIN.zip: 1 file pushed. 7.2 MB/s (884405821 bytes in 117.478s)
+ rm -v META-INF/com/google/android/updater-script recovery/recovery-from-boot.p system/etc/recovery-resource.dat boot.img
removed 'META-INF/com/google/android/updater-script'
removed 'recovery/recovery-from-boot.p'
removed 'system/etc/recovery-resource.dat'
removed 'boot.img'
+ for i in u p d
+ rm -drv META-INF
removed directory 'META-INF/com/google/android'
removed directory 'META-INF/com/google'
removed directory 'META-INF/com'
removed directory 'META-INF'
+ for i in u p d
+ rm -drv recovery
removed directory 'recovery'
+ for i in u p d
+ rm -drv system
removed directory 'system/etc'
removed directory 'system'
+ adb reboot recovery
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
error: no devices/emulators found
+ sleep 1
+ case $(adb shell twrp get tw_version) in
++ adb shell twrp get tw_version
+ break
+ adb shell twrp install /sdcard/UPDATE.BIN.zip
Installing zip file '/sdcard/UPDATE.BIN.zip'
Checking for Digest file...
Unmounting System...
script succeeded: result was [/system]Done processing script file
+ p=/dev/block/platform
++ adb shell ls /dev/block/platform
+ d=msm_sdcc.1
+ adb shell dd if=/sdcard/rec.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=64k conv=notrunc
dd: conv option disabled

==> device rebooted in TWRP
==> shutdown/restart
 

draxie

Senior Member
Apr 20, 2014
508
610
Hmm.... I'm wondering what kind of HW issue you may be having.
Have you seen this relatively recent thread on touchscreen issues?
I don't suppose that would present itself as a "freeze", though...

BTW, I've just reworked the back2stock script,
but I have no desire rolling back my Kindle; so, I'm attaching it here
for anyone who feels compelled to test... As usual, no warranties.
 

Attachments

  • back2stock-v2.zip
    1.4 KB · Views: 1

mbuck2019

Member
Jan 2, 2019
18
3
Hmm.... I'm wondering what kind of HW issue you may be having.
Have you seen this relatively recent thread on touchscreen issues?
I don't suppose that would present itself as a "freeze", though...

BTW, I've just reworked the back2stock script,
but I have no desire rolling back my Kindle; so, I'm attaching it here
for anyone who feels compelled to test... As usual, no warranties.

Oh, I haven't seen that thread before. Yes, this is exactly what I am experiencing.
Even now after putting FireOS back, it has become worse. The device is basically unusable. It would seem the digitizer has been infected. At the moment, I can't do anything with the device, although it boots up. It's not responding to swipe, very erratic. Also, I forgot to say, it keeps complaining I'm not connected to the network and prompts me to register, but the Wifi is connected.

I think I won't be able to execute the back2stock (v2) as it doesn't have TWRP. I would have thought the bootloader would go back to Amazon recovery on Power+Vol down, but it keeps looping on the Kindle Fire logo.
 

draxie

Senior Member
Apr 20, 2014
508
610
I think I won't be able to execute the back2stock (v2) as it doesn't have TWRP. I would have thought the bootloader would go back to Amazon recovery on Power+Vol down, but it keeps looping on the Kindle Fire logo.
You can use 1-Click (again) to install TWRP (and a ROM, if you like, since that
does NOT seem to be the root cause of your issue).

Is there a way you can get me the file Synaptics.3.B.thor.img ?
You'll have to do that yourself, but there's definitely a way.

First of all, I'm not at all sure that you need the 3.B variant for Thor,
but you'll find it in IHEX format here. If that doesn't work, there are
a number of different variants in the same directory.

To convert IHEX to binary, there are literally a zillion alternatives.
If you're on Linux, objcopy works as described here.

You could also use this online utility, which supposedly runs entirely
in Javascript in your browser...
 

mbuck2019

Member
Jan 2, 2019
18
3
You can use 1-Click (again) to install TWRP (and a ROM, if you like, since that
does NOT seem to be the root cause of your issue).


You'll have to do that yourself, but there's definitely a way.

First of all, I'm not at all sure that you need the 3.B variant for Thor,
but you'll find it in IHEX format here. If that doesn't work, there are
a number of different variants in the same directory.

To convert IHEX to binary, there are literally a zillion alternatives.
If you're on Linux, objcopy works as described here.

You could also use this online utility, which supposedly runs entirely
in Javascript in your browser...
Yes, you are right. I was worried that I lost connectivity to the kindle as I won't appear when connected to the laptop. But I reran 1-Click and got TWRP back and was also able to apply AOSP.

With regards to the .hex, I saw the objcopy example in the README after my post. The only thing I wasn't sure if the .img was a .bin which was renamed to .img to run the command:

./synaptics_fw_updater -v -f -b Synaptics.3.B.thor.img

I have no idea of the different variants for thor, but I'll have a go and see if fixes it.

Thanks a lot. I will provide an update asap.
 
  • Like
Reactions: draxie

mbuck2019

Member
Jan 2, 2019
18
3
Yes, you are right. I was worried that I lost connectivity to the kindle as I won't appear when connected to the laptop. But I reran 1-Click and got TWRP back and was also able to apply AOSP.

With regards to the .hex, I saw the objcopy example in the README after my post. The only thing I wasn't sure if the .img was a .bin which was renamed to .img to run the command:

./synaptics_fw_updater -v -f -b Synaptics.3.B.thor.img

I have no idea of the different variants for thor, but I'll have a go and see if fixes it.

Thanks a lot. I will provide an update asap.
Yes, you are right. I was worried that I lost connectivity to the kindle as I won't appear when connected to the laptop. But I reran 1-Click and got TWRP back and was also able to apply AOSP.

With regards to the .hex, I saw the objcopy example in the README after my post. The only thing I wasn't sure if the .img was a .bin which was renamed to .img to run the command:

./synaptics_fw_updater -v -f -b Synaptics.3.B.thor.img

I have no idea of the different variants for thor, but I'll have a go and see if fixes it.

Thanks a lot. I will provide an update asap.

Ok, I have run synaptics_fw_update like so :

thor:/data # ./synaptics_fw_updater -v -f -b Synaptics.3.B.thor.img
Checksum in image file header = 0x671d0d20
Checksum computed from image file = 0x671d0d20
Sensor sysfs entry: /sys/class/input/input0
Image file: Synaptics.3.B.thor.img
Starting firmware update...
Force reflash
Firmware update finished...
Elapsed time = 67.991770 seconds
thor:/data #

rebooted, AOSP came up and seems to have fixed the touch screen, but, then I noticed that when I tried to start typing in my login to connect to wifi, it types random letters by itself. If I rebooted into TWRP, the symptoms is still there , i.e I can swipe halfway and it jerks back and won't complete. I have to restart a couple of times until the full swipe works.

I have tried to flash a couple of vairant of the thor .hex (2B, g) but no difference.
 

mbuck2019

Member
Jan 2, 2019
18
3
Update: I have tried all variants of Synaptics.X.y.thor.img after converting the .ihex on http://matrixstorm.com/avr/hextobin/ihexconverter.html , rebooted the device. I noticed the problem "seems" to go away in portrait mode, but in landscape, i have to swipe multiple times until it works. However, the issue would come back soon after. Interestingly, if I pulled the virtual keyboard, I find sometimes only the first line (quertyuiop..) works the first time when typing, but not the second or third line of the keyboard.

I have a 2nd kindle HDX 7 (but 16GB) which is running AOSPExtended flawlessly. Is it possible to restored a backup of the 16GB on this 32GB problem device? I did try a backup on TWRP and restore the .img on the device but it did not resolve the issue.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Had a Fire HDX 7 3rd gen (C9R6QM) sitting in a drawer wasting space, thought I'd give it a try with a new ROM. Could not for the life of me get the boot loader unlocked... until I found this thread. Yes, you have to wait for the download link, but it is worth it. Worked flawlessly, quickly, and was easy to understand. This is some solid, solid work. MANY thanks!
  • 164
    UPDATE 2020-12-24: Merry Magnifications

    Changed:
    • VirtualBox 6.1.x support (tested with 6.1.16)
      works fine on Linux with Firefox and USB2 ports
      tends to be flaky on MacOS with Safari; PLEASE use Firefox or Chrome!!
      may need to connect via a USB2 hub or try different ports and cables
    • More accurate state assessment (i.e. rooted/unlocked/etc)
    • More aggressive planning logic
      always look for ROM/GAPPS/SU in internal storage
      may end up offering choices that make very little sense
    • Assorted fixes and improvements
      hopefully fewer new bugs were introduced than old ones fixed

    Unchanged:
    1. No prerequisites on the device side
      • no root needed
      • full stock is OK
      • stuck in fastboot is fine
      • heck, it even works with _some_ soft-bricks
    2. Does NOT work on Windows
      1-Click is a virtual machine and a script that starts the VM in VirtualBox.
      Unfortunately, VirtualBox on Windows fails to pass certain USB devices
      including the HDX in bulk mode from Windows to the VM.
    3. Network access required to grab the right aboot + TWRP for your device
    4. Optional TWRP magic to auto-install ROM.zip, GAPPS.zip, and SU.zip from internal storage
    PM me for a personal link and please state your regular HOST operating system.

    Gotchas:
    • Requests without HOST OS information will be ignored.
      • Naturally, the same applies to requests with a Windows HOST OS.
    • Running 1-Click inside another VM is almost guaranteed NOT to work.
    • Link requests should be sent at the earliest 2 weeks after join date.
      Freshly joined members are encouraged to spend some time
      familiarizing themselves with the details of working with this device
      by studying the relevant threads in this forum.
    • If you send a request be sure to monitor your account for replies!
      A response should arrive within a week (or so), but the link is only valid for 2 days.
      Don't miss your chance!
    8
    Hi i need any working mirror of this tool pls, thank's

    Look, I'm really sorry I haven't been able to put out a new release for a **long** time.
    Believe it or not, I'm still working on it, when I have the time, but I've had *way* too
    much going on the last couple of months. I recall making a comment that I'll surely
    finish this by Xmas, but the didn't happen. I do apologize. There's barely anything
    worse than unkept promises...

    I'd give you an old version, if I had more of an order (version control, etc.) on this
    project, but -unfortunately- it's a bit of a chaos. I have different versions floating
    around on different USB sticks. My "master" copy is being totally reworked (and
    not yet fully functional, nor tested to any reasonable standards). I simply cannot
    take responsibility or give support to some random version, which is also why I'm
    asking not to mirror. If you happen to find the wrong version (there had been
    test releases, which didn't quite work -- no bricks, as far as I know, but no joy,
    either), you'll be in for a surprise.

    Here's what I'll (try to) do: I've just finished my delivery for work (you know, the
    stuff that actually pays... ;)), and I have only two more interesting 'research' projects
    going on besides this tool. I'll put those aside and concentrate on this one. Let's see
    if I can get out a usable version in a few days. (I have most parts working, but I need
    to put everything together and _thoroughly_ test; so, you don't end up with a brick.)
    5
    Any takers?

    Very cool! Will be interesting to try this out (have to wait for a someone with an eligible device that is willing to give it a whirl).

    BTW, this works with already unlocked devices also, :p
    if anyone is willing to do some independent testing.
    This is how I tested also... should be completely harmless. ;)
    5
    That's awesome! I appreciate all the work you guys do! Let us know when you have it up to your standards :)

    I just posted a download link...
    4
    Patience

    Any idea when the next version will be released? I"ve got some spare time so I figured I would get my HDX on full Android. Why did the link expire after 2 weeks?

    Unfortunately, I'm far too busy at the moment,
    but this is on the top of my list. Won't make any
    definite promises though. On the positive side,
    I got both a Thor and an Apollo delivered (both
    warehouse deals) yesterday. So, I can start
    testing without jeopardizing my daily driver.