[Q&A] HDX Stock Images Pre-rooted, Updates Disabled - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

Q&A for HDX Stock Images Pre-rooted, Updates Disabled
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

---

access hdx7 filesystem via pc...without adb enabled on device
ggow said:
Hi All,
Here you can find stock firmware for both thor and apollo devices which are safestrap flashable.
Please note the following:
- These updates do NOT flash a new kernel or recovery - only a new /system image
- Before flashing ensure you know which stock base/kernel/safestrap you have installed and choose the appropriate version for that stock base/kernel.
I will be uploading them as and when I have time.
Thor Images:
13.3.1.0
If you want to re-enable over the air updates then do the following:
- rename /system/etc/security/otacert.old to otacert.zip
- rename /system/app/com.amazon.dcp.old to com.amazon.dcp.apk
Click to expand...
Click to collapse
I've had like a million or so android devices, and successfully hacked them all with 0 bricks to date. i've been pounding on an hdx7 for the past 2 days and i'm stuck.
background:
started off with fw 13.3.2.6
towelrooted/safestrapped/google play etc
been trying to downgrade fw to 13.3.1.0
now i'm in a situation where i flashed the thor fw in the 1st post in the "HDX Stock Images PreRooted, Updates Disabled" thread via safestrap recovery (yes the stock rom...i know i know) and now after safestrap exits to the system, all i get is a black screen. the device is on though. prior to this attempted downgrade, i did a full wipe. i have a nandroid (twrp) stock backup i have successfully reverted to a couple times so far, but this backup is now only on my computer due to the factory reset.
how can i push this file to the device with a black screen, on which adb has not yet been enabled?
i'm also open to other suggestions.
i did create a new rom slot, but it has no os on it either...
thx in advance

---

andyhax0r said:
I've had like a million or so android devices, and successfully hacked them all with 0 bricks to date. i've been pounding on an hdx7 for the past 2 days and i'm stuck.
background:
started off with fw 13.3.2.6
towelrooted/safestrapped/google play etc
been trying to downgrade fw to 13.3.1.0
now i'm in a situation where i flashed the thor fw in the 1st post in the "HDX Stock Images PreRooted, Updates Disabled" thread via safestrap recovery (yes the stock rom...i know i know) and now after safestrap exits to the system, all i get is a black screen. the device is on though. prior to this attempted downgrade, i did a full wipe. i have a nandroid (twrp) stock backup i have successfully reverted to a couple times so far, but this backup is now only on my computer due to the factory reset.
how can i push this file to the device with a black screen, on which adb has not yet been enabled?
i'm also open to other suggestions.
i did create a new rom slot, but it has no os on it either...
thx in advance
Click to expand...
Click to collapse
Can you get into safestrap?

---

mr. softbricked
ggow said:
Can you get into safestrap?
Click to expand...
Click to collapse
Yes I can boot into safestrap, I have tried using the ADB sideload feature but when I try issuing ADB commands using ADB in the Android Studio installation directory, it's always 'device not found'.
I tried to use the Terminal Command feature, and it asks me what directory on the HDX I want to start in, and I pretty much called it a night at that point.
Right now I'm thinking I probably have to order a fastboot cable, but I'd be very interested in exploring other options.
Thanks

---

andyhax0r said:
Yes I can boot into safestrap, I have tried using the ADB sideload feature but when I try issuing ADB commands using ADB in the Android Studio installation directory, it's always 'device not found'.
I tried to use the Terminal Command feature, and it asks me what directory on the HDX I want to start in, and I pretty much called it a night at that point.
Right now I'm thinking I probably have to order a fastboot cable, but I'd be very interested in exploring other options.
Thanks
Click to expand...
Click to collapse
Fastboot cable won't do you any good, don't waste your money
If you are running on windows then install this: http://forum.xda-developers.com/showthread.php?t=2588979
If you are on linux (my preference), be sure you have started adb with admin privileges. ie:
adb kill-server
sudo adb start-server
That may hopefully help your adb woes.
I'll upload a 13.3.2.6.zip file which you can push to your device and flash via safestrap.

---

sweet
ggow said:
Fastboot cable won't do you any good, don't waste your money
If you are running on windows then install this: http://forum.xda-developers.com/showthread.php?t=2588979
If you are on linux (my preference), be sure you have started adb with admin privileges. ie:
adb kill-server
sudo adb start-server
That may hopefully help your adb woes.
I'll upload a 13.3.2.6.zip file which you can push to your device and flash via safestrap.
Click to expand...
Click to collapse
wow thanks! yes i'm using windows, i will go grab my beautiful brick at lunchtime and try the utility. i do have a 13.3.2.6 bin file from amazon and a 13.3.2.6 zip file i got got from one of the HDX threads here. but if you upload a zip i can try it.
just to be clear, this is what i plan to try (please redirect me if i'm misguided):
on device: start adb sideload safestrap tool. on pc: (cmd prompt-admin) adb start-server, try an adb sideload myfwfile.zip
i really appreciate the assistance, i will definitely post an update once i try the adb utility.

---

andyhax0r said:
wow thanks! yes i'm using windows, i will go grab my beautiful brick at lunchtime and try the utility. i do have a 13.3.2.6 bin file from amazon and a 13.3.2.6 zip file i got got from one of the HDX threads here. but if you upload a zip i can try it.
just to be clear, this is what i plan to try (please redirect me if i'm misguided):
on device: start adb sideload safestrap tool. on pc: (cmd prompt-admin) adb start-server, try an adb sideload myfwfile.zip
i really appreciate the assistance, i will definitely post an update once i try the adb utility.
Click to expand...
Click to collapse
Forget about the sideload feature of safestrap for this exercise...
For windows the instructions would be this:
1. Download the 13.3.2.6.zip (which is uploading at the moment)
2. Open command prompt
3. cd to the folder where you saved the zip file
4. Connect your kindle if you haven't already.
5. Make sure it shows up as an adb device in the device manager
6. Issue the command <adb devices> and ensure your device is listed in the response.
7. Issue the command <adb push 13.3.2.6.zip /sdcard> - this will take a bit of time complete
8. Then on safestrap select the Install option and find your zip in /sdcard and flash it.
9. Do a factory reset and reboot from safestrap and you should be good to go.
Will let you know when the file is up.

---

@andyhax0r
13.3.2.6.zip can be found here:
http://forum.xda-developers.com/showpost.php?p=56148362&postcount=1

---

Softbricked HDX 7 Update
ggow said:
@andyhax0r
13.3.2.6.zip can be found here:
http://forum.xda-developers.com/showpost.php?p=56148362&postcount=1
Click to expand...
Click to collapse
Been working on pushing the recovery file to the device any possible way I can find.
- I downloaded the exe that installs ADB + Fastboot (system-wide)
- I downloaded and have been using the HDX Toolkit + Kindle drivers
- Tried Android Studio's Kindle Fire SDK + drivers installed from official Amazon repo
- Tried on Windows 7 x64
- Tried on Windows 8 x64
- Tried on WIndows 10 x64 Tech Preview
...always the same result:
Shows up only as Kindle FIre HDX with yellow exclamation point under Other Devices in Device Manager, even if I uninstall & delete the drivers & driver directory then reinstall. Whenever I point Device Manager to the C:\Program Files (x86)\Amazon.com\Kindle Fire\Drivers directory to install for the ADB drivers, Device Manager responds with Windows was unable to install your Kindle Fire HDX. Windows could not find the driver software for your device.
Therefore, I can't issue ADB or Fastboot commands because I always get 'error deivce not detected' or 'waiting for device' since driver isn't installed.
It's maddening since I can get into SafeStrap recovery and fastboot on the device, it's in mint condition, and it's completely worthless unless I can somehow get just 1 file to the internal storage. Too bad all the hardware manufacturers 'motivate' consumers to buy a more expensive model with a higher storage capacity by not installing a MicroSD card slot.
I spent numerous hours the past few days researching, installing different versions of Windows, trying to access the device. I really don't know what else to do besides sell it for parts online.

---

andyhax0r said:
Been working on pushing the recovery file to the device any possible way I can find.
- I downloaded the exe that installs ADB + Fastboot (system-wide)
- I downloaded and have been using the HDX Toolkit + Kindle drivers
- Tried Android Studio's Kindle Fire SDK + drivers installed from official Amazon repo
- Tried on Windows 7 x64
- Tried on Windows 8 x64
- Tried on WIndows 10 x64 Tech Preview
...always the same result:
Shows up only as Kindle FIre HDX with yellow exclamation point under Other Devices in Device Manager, even if I uninstall & delete the drivers & driver directory then reinstall. Whenever I point Device Manager to the C:\Program Files (x86)\Amazon.com\Kindle Fire\Drivers directory to install for the ADB drivers, Device Manager responds with Windows was unable to install your Kindle Fire HDX. Windows could not find the driver software for your device.
Therefore, I can't issue ADB or Fastboot commands because I always get 'error deivce not detected' or 'waiting for device' since driver isn't installed.
It's maddening since I can get into SafeStrap recovery and fastboot on the device, it's in mint condition, and it's completely worthless unless I can somehow get just 1 file to the internal storage. Too bad all the hardware manufacturers 'motivate' consumers to buy a more expensive model with a higher storage capacity by not installing a MicroSD card slot.
I spent numerous hours the past few days researching, installing different versions of Windows, trying to access the device. I really don't know what else to do besides sell it for parts online.
Click to expand...
Click to collapse
1. On device manager Right click on the Kindle HDX device and select Uninstall.
2. Then do a a scan for devices from the device manager.
3. It will now show up as a device requiring a driver.
4. Now right click on it and select properties and press the button 'Update Driver'
5. Then select Browse my computer
6. Look for the Android devices category and select an adb driver to install
7. Windows will then moan that the driver isn't correct for the device - ignore this and select install anyway or whatever the option is to proceed.
8. When installed issue command <adb devices> to confirm it's working.

---

FINALLY!
ggow said:
1. On device manager Right click on the Kindle HDX device and select Uninstall.
2. Then do a a scan for devices from the device manager.
3. It will now show up as a device requiring a driver.
4. Now right click on it and select properties and press the button 'Update Driver'
5. Then select Browse my computer
6. Look for the Android devices category and select an adb driver to install
7. Windows will then moan that the driver isn't correct for the device - ignore this and select install anyway or whatever the option is to proceed.
8. When installed issue command <adb devices> to confirm it's working.
Click to expand...
Click to collapse
Wanted to give an update with solution:
After trying every possible way I could find to get either a system update file (.bin) or flashable .zip to my softbricked hdx, I was out of options. I had spent numerous hours researching, memorized most adb and fastboot commands, and even installed 3 different versions of Windows trying to get a working environment.
I figured I can revisit the issue later, maybe in 6 months or a year there will be a fix. I boxed up the hdx and put it away. I bought a Nexus 7 2013 to play with, it being my favorite tablet and the one I have found to be most hackable. Got the WugFresh toolkit to unlock and root it, custom Slim rom + mini gapps, Elementalx kernel, and updated Adreno drivers.
I noticed that when I connected the Nexus to my laptop, I couldn't see it in Windows Explorer, no matter what mode put it in (media file transfer, camera, charge, etc). I had already installed the USB driver.
Then it hit me...
The one thing that the hdx and the nexus have in common - the USB cable. Had been using an original Asus Nexus 7 2013 data cable from a Nexus I previously owned.
I immediately changed the cable and got the hdx out, connected it, was able to install the drivers and in adb mode, I pushed both a flashable zip of 13.3.2.6 and a .bin to the /sdcard directory. Booted the hdx, flashed the zip in SafeStrap, and once again I had a working device!
I created a new rom slot, and tried to flash 13.3.1.0 to it, but still got a black screen when it started up. At least I still had my new stock rom to boot to. For some reason, I have been unable to downgrade the firmware on this device. That's okay, because even though I couldn't install the custom rom i wanted to make the hdx into a pure tablet, at least the hdx didn't beat me. I softbricked it, then put in work to come back from it, and learned a lot in the process.
Thanks for all your help!

---

Hey.
This may be a stupid question, but can I use the pre rooted 13.3.2.6 to update my 13.3.1.0.(rooted) to the latest rootable Version? Or how Do i Do that?
I already disabled ota and installed xposed.

---

I have a fire hdx Apollo that had been properly up(down)graded and running fine with 2.01. For some reason (and my lack of understanding the correct versions of things) I thought it would be a good idea to install the Apollo update on my stock rom. This of course has now caused boot loops on my stock boot but not my 2.01 boot.
Would love to be able to restore the stock as I do use some of the fire's capabilities from time to time. Sadly I did not do a backup before the update (kicks self furiously).
I DO have a backup from before the upgrade/downgrade so maybe I could restore that then push through the upgrade steps again or something. I'm worried that I will bork my safestrap or do something worse based on my proclivity for damage and chaos.
E.

---

Cpasjuste said:
Hi @ggow !
I made a flashable zip of the 4.5.2 update for Thor which is compatible with the signing exploit (bootloader/fw flashing removed and modified bootimage with happened dt) as there was some demand.
I'm not sure i should again create a thread for this rom(s) as we may be easily lost. Maybe all our "stock/modified stocks" roms should be in the same thread. What do you think about this ? Here is the link in case : http://android.mydedibox.fr/hdx/update-kindle-13.4.5.2_user_452004120-twrp.zip
Note that i only renamed "otacert.zip" to "otacert.old" on this rom as the "dcp" apk name has changed and i don't remember how i fixed that ... so ota updates may still be enabled isnt it ?
---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------
I don't know if it's the problem but the appolo recovery is based on an older kernel (3.1.0?) which doesn't have full selinux support. This prevented some zip to be properly flashed (at least on thor) until i use the 4.5.2 kernel sources. Unfortunately we will have to wait for @ggow to receive his new device, in the hope of an exploitable one (but this may be a different problem)
Edit : oups, you are on thor so it's not the problem !
Click to expand...
Click to collapse
Hello,
i found on android-hilfe.de forum which files must be renamed, for disabling ota, link:
/system/app/otaverifier.apk
/system/priv-app/devicesoftwareota.apk
But now i have an other problem, i can't use instant video anymore, i always get a LICENSE_ERROR, any idea, why?
Greets,
Marcel
Gesendet von meinem KFTHWI mit Tapatalk

---

...
But now i have an other problem, i can't use instant video anymore, i always get a LICENSE_ERROR, any idea, why?
Greets,
Marcel
Gesendet von meinem KFTHWI mit Tapatalk
Click to expand...
Click to collapse
I'm using Cpasjuste's 4.5.2 with those files renamed. I can still play Amazon instant videos without error. At first I renamed those files before the first boot and my kindle was acting weird. I wonder if it's related? May try rename those files back and play a video then immediately rename them again? Be extra careful though. There is a new 4.5.2 OS from Amazon already.

---

Okaaay, I tested it already and nothing, I can't play videos...
But I have an other thing ? I have a modified gapps zip, that fit for the rom ? I had to remove nearly everything out from it, only the libs, the sync apks and the market left, I will add the file to this post, when I uploaded it later.
Edit: Here is my gapps package:
https://docs.google.com/file/d/0Bw33k6BXtLiYcGdOVGk1VVBEcjg
please report if it works or not ??
Gesendet von meinem KFTHWI mit Tapatalk

---

Is this flashable from safestrap?I made a flashable zip of the 4.5.2 update for Thor which is compatible with the signing exploit (bootloader/fw flashing removed and modified bootimage with happened dt) as there was some demand.

---

Rom slot or Stock?
I tried flashing the 4.5.2 stock rom on a rom slot using safestrap and just got a black screen until it finally went back into recovery. I was wondering since it's a stock rom if I needed to flash it onto the stock slot. In that case, do I just flash it over what I have (3.2.8) or do I have to do a wipe? I'm currently using Nexus ROM but I enjoyed the new fire OS before I rolled back to get root back. Help appreciated!

---

The Rom you mentioned (4.5.2 from Cpasjuste) is for flashing with TWRP and not for safestrap.
TWRP is not working on 3.2.8

---

Oh for some reason I thought it was for safestrap and not twrp. Does anyone have a ROM like that for safestrap? Or is there a kernel issue or something?