[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] instantwater:
Bricked HDX 8.9 (3rd) [4.5.2], but ADB is available

I bricked my HDX 8.9 (3rd).

It has ROM version: 4.5.2.

Here's exactly that I have done.

I have rooted it with the cve20147911.apk,

Installed RootExplorer

disabled OTA and tried to install gapps with this tutorial

But the gapps package is too big, so I installed Titanium backup to convert some amazon apps (goodread, special offers, market, firefly, and some others) from system apps to user apps to free up some space on the system drive. I also freezed them, as I don't need them at all.

I managed to get about 80 MB free space on the system drive, then created a folder called "x" in the root, then copied the "system" folder to this "x" from the gapps package.

Selected the "system" folder in my "x" temporary folder, then selected Permission option, then set permissions to 644 RECURSIVELY to the "system" folder.

Then selected "system" folder in my "x" folder, then selected "cut" from the options, then pasted the clipboard content to "/" then the folder structure would match, so the system can copy all the files to the right place in a single step.

Root explorer asked about the existing folders, I selected "merge". There were no question about files, so all of them were new, which means I did not overwrite anything.

After finishing this copy, the screen started to blink very quickly in black and grey, then I turned off the tablet.

I tried to turn it on.

It stuck on the gray "Kindle Fire" screen, and couldn't get to the golden "Fire" loading screen.

After about a minute, it restarted itself to Recovery mode.

Tried to restart, but it stuck again the grey kindle fire screen, and restarted itself to recovery.

I made a (now I know) wrong decision at this point.

Restored to Factory defaults. Did not help.

In Windows 7 32bit, it appears as "Android Composite ADB Interface", but I can not see it in adb devices from now.

Rebooted to Linux mint 17.1 (Ubuntu 14.10).

It appears in lsusb for some seconds as:

Bus 001 Device 003: ID 1949:000d Lab126, Inc.

So I installed ADB and set the /etc/udev/rules.d/51-android.rules file with the following lines:

# Amazon Kindle Fire HDX 8.9
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", GROUP="plugdev"

SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0006", MODE="0600", OWNER="<username>"
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0005", MODE="0600", OWNER="<username>"
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="000d", MODE="0600", OWNER="<username>"

SUBSYSTEM=="usb",ATTR{idVendor}=="1949",ATTR{idProduct}=="000d",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="1949",ATTR{idProduct}=="000d",SYMLINK+="android_fastboot"
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"

I know not all of them necessary...

Then ran:

sudo service udev restart

Now I can see it properly in adb devices.

List of devices attached
B057070xxxxx	device

At this point I thought everything's fine despite the factory reset I still has access ADB.

The truth is that I can pull files (and probably push too) from my device (tried/system/ build.prop) to my computer.

But when I try "adb shell", it throw this error:

WARNING: linker: could not load library "/vendor/lib/libNimsWrap.so" from LD_PRELOAD for "/system/bin/sh"; caused by could not load library "libc.so" needed by "libNimsWrap.so"; caused by library "libc.so" not found
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "/system/bin/sh"; caused by library "libc.so" not found

(adb logcat give the same error)

At the moment I can not push anything to the "/system" because that is mounted Read Only, but I might be able to push to some RW folders, but have no idea how to move it without shell.

I managed to pull some files from the "/system" so it is readable (at least for some seconds).

Additional info:

There's a "No command." message in the middle of the screen in Recovery Mode

Please, if you have any ideas that we can do with my half-bricked HDX 8.9 (3rd), please share them. I would be very thankful.

Thank you.