Related
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?
I've gone through numerous threads about "unbricking" but I have not been able to find any specific instructions for what to do in my situation. I have installed Ubuntu on a USB drive in order to access ADB/Fastboot and have allowed myself to spend a few days troubleshooting the problem myself, but must admit that I am in over my head and require some sort of guidance if possible. Any insight or help is appreciated.
How I got to where I am:
I believe when I installed TWRP I had to use the build prop exploit, but I can't remember clearly
At some point after installing TWRP, I believe I removed SafeStrap
I installed the CM-11 ROM and used it for a period of time without issue
CM-12 for Thor was released, so I installed it over the CM-11 installation I believe
I realized that by installing CM-12, I had made my gf's save files for Final Fantasy inaccessible
I tried to restore to a backup I had made of CM-11 and was met with a bootloop
By trying to "start from scratch", I wiped all options allowed without realizing the consequences
Any reboots of the device brings it to a black screen after the gray Kindle Fire logo
Here are some observations I have made while trying to figure out a solution:
In TWRP, ADB shows the device as being in "recovery"
In "adb shell" with the device booted into TWRP, the command "su" produces "/sbin/sh: su: not found"
I am allowed to drag .zip files into "Internal Storage" for the device, but flashing "13.3.1.0.zip" or "cm-12 ... .zip", for example, leads to the device booting into a black screen (I have tried mounting /system in TWRP)
Fastboot commands tend to hang on the linux terminal with the device not responding to commands
EDIT: After a little dicking around, I found out how to make the device show up under Windows 8.1 by using a guide outlined here: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81-10/
I am now familiarizing myself with ADB/Fastboot commands a bit more to see if I can figure anything out on my own.
I haven't been able to figure this out on my own - is there anyone who could give me some advice about my situation?
Basically TLDR is that I did a factory reset on TWRP, I can boot into TWRP but can't seem to flash anything, though I can put zips on my internal storage.
aimlessanomaly said:
I haven't been able to figure this out on my own - is there anyone who could give me some advice about my situation?
Basically TLDR is that I did a factory reset on TWRP, I can boot into TWRP but can't seem to flash anything, though I can put zips on my internal storage.
Click to expand...
Click to collapse
Sound like you either lost write permissions on the system partition or the partition contents are corrupt. I have also heard problems within the data partition can create flashing problems. Have you tried the advanced wipe functions in twrp? You'll need to do a little poking around to determine which items are safe to wipe. Obviously you don't want to touch boot and recovery but (intelligently) neither is an option in twrp.
Davey126 said:
Sound like you either lost write permissions on the system partition or the partition contents are corrupt. I have also heard problems within the data partition can create flashing problems. Have you tried the advanced wipe functions in twrp? You'll need to do a little poking around to determine which items are safe to wipe. Obviously you don't want to touch boot and recovery but (intelligently) neither is an option in twrp.
Click to expand...
Click to collapse
I get a lot of errors involving /system when I try to mount and then repair or flash anything. Also, when I reboot it often says "Your device does not appear to be rooted - Install SuperSU now?" When I swipe to install it just restarts normally to my white kindle fire logo.
EDIT: I somehow was able to flash the cm11 ROM onto my kindle, rebooted, and my tablet is working again! I tried a bunch of different repair options and even used the option that makes you type out "yes" ( can't remember the name, need to sleep atm), but somehow got it working. Thanks for the help so far.
Hi everyone
I own an Amazon Fire HD 6 and I love it. It's a powerful little machine, but Fire OS 4.5.3 sucks. I've been looking to root it and run a custom ROM on the device since I got it in December 2014, but I never got around to doing it until now. (And there weren't instructions back then.)
I managed to follow instructions posted by @bibikalka that have proven to be very helpful, but I started encountering a problem at step 2).
bibikalka said:
[DONE] 0) get ADB drivers working on your PC, etc:
http://forum.xda-developers.com/fire-hd/general/root-supersu-stable-appstore-custom-t3113311
Tip: A quick way to debug your adb connectivity issues is to use USBDeView : http://www.nirsoft.net/utils/usb_devices_view.html
[DONE] 1) Determine your FireOS version, versions up to 4.5.3 are rootable, 4.5.4 will need to be upgraded to 5.0.2 and then downgraded to 4.5.3 :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
[DONE, WITH EXCEPTION] 2) Disable OTA updates ( adb shell ; pm block com.amazon.dcp or "Debloater" http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 ),
sideload Kingroot ( http://androidxda.com/download-kingroot-application ),
and let it root. Don't bother with SuperSu at this stage, you'll get it done later.
Click to expand...
Click to collapse
My Fire HD 6 shows up without error in
Code:
adb devices
but when I attempted to sideload Kingroot via
Code:
adb reboot recovery
I got the following error:
Code:
Fire System Recovery
Your Fire doesn't seem to be able to boot. Reseting your device to Factory defaults may help you to fix this issue.
I've since attempted to reset it to Factory defaults, but after trying to boot into recovery afterward, I didn't have any success.
I took it a step further by using the following code to install Kingroot:
Code:
adb install Kingroot_V4.5.0.722.apk
This worked and Kingroot rooted the device without error, but I'm curious to know if this is a big deal since I didn't sideloading the app.
The problem I have now is with sideloading the TWRP image. Without access to recovery, this doesn't appear to be possible. But how can I get my recovery back? I've done some research and apparently this is so messed up that I may need to purchase a factory cable, but I'm curious to know if anyone has any other advice or can help me better understand what went wrong.
Thanks in advance.
Is recovery gone?
pantyman said:
I managed to follow instructions posted by @bibikalka that have proven to be very helpful, but I started encountering a problem at step 2).
My Fire HD 6 shows up without error in . . . adb devices . . . but when I attempted to sideload Kingroot via . . . adb reboot recovery . . . I got the following error:
Fire System Recovery
Your Fire doesn't seem to be able to boot. Reseting your device to Factory defaults may help you to fix this issue.
Click to expand...
Click to collapse
Please do nothing more until @bibikalka or someone else can help you deal with the recovery issue. I'll just point out a few things:
(1) You don't sideload an apk in recovery. (I suspect you know this. For an apk, sideload just means copy/move the apk to the device and install it, with a file manager usually, whereas "adb sideload" from recovery is for bin, zip files.)
I've since attempted to reset it to Factory defaults, but after trying to boot into recovery afterward, I didn't have any success.
Click to expand...
Click to collapse
(2) I assume you got above error again. This is where you need someone else's help.
I took it a step further by using the following code to install Kingroot:
Code:
adb install Kingroot_V4.5.0.722.apk
This worked and Kingroot rooted the device without error, but I'm curious to know if this is a big deal since I didn't sideloading the app.
Click to expand...
Click to collapse
(3) Not a big deal. You got it installed.
The problem I have now is with sideloading the TWRP image. Without access to recovery, this doesn't appear to be possible.
Click to expand...
Click to collapse
(4) You don't adb sideload TWRP. Although there are other methods, we've been using TWRP Manager or Flashify. (Guide). As said, I wouldn't do anything until you figure out the status of recovery.
But how can I get my recovery back? I've done some research and apparently this is so messed up that I may need to purchase a factory cable, but I'm curious to know if anyone has any other advice or can help me better understand what went wrong.
Click to expand...
Click to collapse
Factory (fastboot) cable's don't work with this device; you get into fastboot mode with "adb reboot fastboot," but doing that would be a bad idea right now.
DoLooper said:
Please do nothing more until @bibikalka or someone else can help you deal with the recovery issue. I'll just point out a few things:
(1) You don't sideload an apk in recovery. (I suspect you know this. For an apk, sideload just means copy/move the apk to the device and install it, with a file manager usually, whereas "adb sideload" from recovery is for bin, zip files.)
(2) I assume you got above error again. This is where you need someone else's help.
(3) Not a big deal. You got it installed.
(4) You don't adb sideload TWRP. Although there are other methods, we've been using TWRP Manager or Flashify. (Guide). As said, I wouldn't do anything until you figure out the status of recovery.
Factory (fastboot) cable's don't work with this device; you get into fastboot mode with "adb reboot fastboot," but doing that would be a bad idea right now.
Click to expand...
Click to collapse
Thanks a lot for all of your advice, @DoLooper. I've since actually gotten everything to work by following instructions by @r3pwn on his alternate unbricking method for the Kindle Fire HDX 7" & 8.9"
No issues for me any more! The only thing I have to look for now is a good launcher for this thing. I'm not a big fan of the Vire Launcher.
I'm having this same problem but was unable to fix via the thread linked.
Help please?
I have a Fire HDX 7 on 13.3.2.5_user_325001120, Rooted, Safestrap 3.75 with Fire OS on Stock slot and ggow's HDX Nexus 2.0.2 on Slot-1. OTA updates are not disabled but no Wifi networks are added and Wifi is off within Fire OS.
I'm basically looking for clarification on the steps I need to take in order to unlock the Bootloader (for peace of mind and so that I can try out other ROMs freely).
To the best of my understanding I can Unlock with the following instructions:
Downgrade from 13.3.2.5 to 13.3.1.0
Download 13.3.1.0 .bin and script linked by kaeru00
Originally Posted by kaeru00
USE IT AT YOUR OWN RESPONSIBILITY because rewrite recovery partition.
How to use it.
1. install Towelroot and Supersu using KFHDX Toolkit v 0.94
2. If Disable OTA update , Airplane mode ON and Enable OTA update
3. If Install SafeStrap, uninstall safestrap on App.
4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
5. execute install.bat
6. reboot
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage.
8. Downgrade, wait a minute on the update menu, because display update button to take time.
9. disable OTA update.
This batch file works "kindle fire hdx 7" ONLY
This is tested on version 13.3.2.5 and 13.3.2.6.
Click to expand...
Click to collapse
If successful with the above I then proceed with the following to actually unlock:
Originally Posted by ceyo14
complete as follows. tested on HDX 7 (Thor) Rooted 13.3.1.0
get Python 2.7 for windows and install it
get GMPY2 for Python 2.7
open command prompt to your ADB directory:
Code:
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
from these 2 results you get your the code we need, insert the last 2 digits of the manfID with your serial
following
like this: mmssssssss
download the attachment on the following post: http://forum.xda-developers.com/show...2&postcount=46
Then place the file inside the attachement to C:\Python27 should be C:\Python\cuberHDX.py
open command prompt in: C:\Python27
replace "mmssssssss" with yours below:
Code:
python.exe cuberHDX.py 0xmmssssssss
that will put a new 0xmmssssssss.UNLOCK file in the Python27 directory
copy that file to your fastboot directory.
on an ADB prompt type
Code:
adb reboot-bootloader
then on a fastboot prompt type
Code:
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
fastboot -i 0x1949 reboot
thats it.
Click to expand...
Click to collapse
All going well, I'm then unlocked and can proceed to install TWRP and ROMs, correct?
Yes, but actually you can install TWRP after downgrading to 3.1.0 already.
And it's recommended (i.e. not mandatory) to update to 3.2.3.2 (can be done from TWRP, it's also possible to update the 3.2.3.2 bootloader only). Be sure to re-root if you update to 3.2.3.2! And keep WLAN off/flight mode active at all times. Stock firmwares are available here - ensure you get the correct for your device!
If you haven't done yet, install Minimal ADB and Fastboot, and grab these drivers for the unlock procedure in order to get the HDX recognized.
Then unlock the bootloader to be in the wonderland of HDX ROMs (=TWRP & unlocked bootloader), you can use Nexus, CM11 or CM12 then - read the installation notes and requirements carefully! Additional info for the unlock procedure after installation of the required software can be found here.
Disable OTA in Fire OS, make a backup in TWRP, and copy the backup to your PC before you flash any ROM!
Thank alot Cl4ncy.
Having now re-read the instructions I've posted, I'm abit unsure of the rollback process as below:
1. install Towelroot and Supersu using KFHDX Toolkit v 0.94
2. If Disable OTA update , Airplane mode ON and Enable OTA update
3. If Install SafeStrap, uninstall safestrap on App.
4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
5. execute install.bat
6. reboot
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage.
8. Downgrade, wait a minute on the update menu, because display update button to take time.
9. disable OTA update.
Steps 4 & 5, am I doing this on the HDX or on PC. Do I need the HDX connected to my PC, and if so what mode should it be in?
Could someone possibly expand the above steps to to be abit more clear?
316894 said:
Thank alot Cl4ncy.
Having now re-read the instructions I've posted, I'm abit unsure of the rollback process as below:
1. install Towelroot and Supersu using KFHDX Toolkit v 0.94
2. If Disable OTA update , Airplane mode ON and Enable OTA update
3. If Install SafeStrap, uninstall safestrap on App.
4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
5. execute install.bat
6. reboot
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage.
8. Downgrade, wait a minute on the update menu, because display update button to take time.
9. disable OTA update.
Steps 4 & 5, am I doing this on the HDX or on PC. Do I need the HDX connected to my PC, and if so what mode should it be in?
Could someone possibly expand the above steps to to be abit more clear?
Click to expand...
Click to collapse
After you downloaded the rollback.zip from that thread un-zip it to a folder on your PC, copy the update.bin into that folder, and execute the install.bat. Your HDX must be connected by USB, USB debugging must be active on the HDX, the install.bat will move (push) some files to the HDX.
Reboot the HDX then, copy the update.bin to your HDX and execute the downgrade.
Again: ensure you have WLAN off/flight mode active as you need OTA to be enabled in Fire OS! You do NOT want to get updated to 4.5.5 by Amazon.
Thanks again, that is as I suspected, having now opened the .bat in notepad.
Why is it generally recommended that we update to 3.2.3.2? Can this also be done the old fashioned way through the Fire OS update option or is it easier/safer through TWRP after taking a backup.
After that then I would re-root with Towelroot.
316894 said:
Thanks again, that is as I suspected, having now opened the .bat in notepad.
Why is it generally recommended that we update to 3.2.3.2? Can this also be done the old fashioned way through the Fire OS update option or is it easier/safer through TWRP after taking a backup.
After that then I would re-root with Towelroot.
Click to expand...
Click to collapse
There have been some screen issues with Nexus, thus it's recommended to use the 3.2.3.2 bootloader, which can be flashed itself in TWRP - check this thread.
So it's your choice, to update to 3.2.3.2 using the official update in TWRP or Fire OS, or just flash the 3.2.3.2 bootloader in TWRP. If you want to dump Fire OS anyway, just disable OTA in Fire OS via HDX Toolkit, backup Fire OS in TWRP, move it to your PC, update 3.2.3.2 bootloader from the thread mentioned above, unlock it, then flash Nexus, CM11 or CM12.
You can also check for the backup of the original Amazon recovery, should be somewhere on the HDX, after you installed TWRP (AFAIR TWRP creates a backup of the original recovery), and move that recovery backup to your PC as well.
Good stuff, this will give me something to do tonight when I get in from work.
I will report back with my results! Cheers. :good:
316894 said:
Good stuff, this will give me something to do tonight when I get in from work.
I will report back with my results! Cheers. :good:
Click to expand...
Click to collapse
One more thing:
You should remove the secondary slot with Nexus 2.0.2 before you un-install Safestrap. Otherwise the storage used by that slot could be still in use.
Success! 13.3.2.3.2 bootloader, unlocked and now running KitKat 4.4.4
Cheers for the help Cl4ncy. :good:
316894 said:
Success! 13.3.2.3.2 bootloader, unlocked and now running KitKat 4.4.4
Cheers for the help Cl4ncy. :good:
Click to expand...
Click to collapse
Great you got it working! Enjoy your "free" HDX.
Just to go for sure...
Hi there,
thanks for your great thread, I am in nearly the same position.
I am currently on: Safestrap 3.75, Nexus 2.0.2 from ggow on ROM-Slot-1 and Stock ROM has version: 13.3.2.4_user_324002120 (build on 20.th June, 2014, 23:58 GMT)
Some questions however remain:
How did you uninstall Safestrap? Boot to Stock ROM, start the Safestrap app there and hit uninstall? Or somewhere else?
I just want to go 100% sure before removing my "fallback" software, which Safestrap was until now.
The link in your post does no longer point to cuberHDX, I used this one: http://forum.xda-developers.com/showpost.php?p=58864282&postcount=46
I have adb and "KFHDX ToolKit v0.95" running to do things via my PC.
Do I need to use fastboot (it does not list my device yet, but I also have not changed the driver as Cl4ancy suggested)? If it is not needed, I will stick to my working adb.
The things I downloaded right now are:
13.3.2.4_rollback (from here: http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 ), to go back to .3.1.0 .
thor-bootloader-13.3.2.3.2_upgrade.zip (from here: http://forum.xda-developers.com/kindle-fire-hdx/development/twrp-flashable-3-2-3-bootloader-upgrade-t3025504 ), to update 3.1.0 to .3.2.3.2
cuberHDX from here: http://forum.xda-developers.com/showpost.php?p=58864282&postcount=46
I have retrieved the needed serials and are nearly ready to go. Just want to double check whether I have misunderstood something.
If not, I think this is the procedure, right:
1. Downgrade to .3.1.0 (how is this done? the zip contains folders, not a binary. The instruction say: 2. Flash the appropriate file for you device . Shall I do this by copying the zip to the device and install it via the still present Safestrap?) Can you please clarify on that?)
1.5 Delete Safestrap? (If this is still possible after downgrading? )
2. Upgrade to .3.2.3.2 by placing the .bin in the root folder ? ( I have no install.bat batch file supplied here).
3. Unlook bootloader as described here: http://forum.xda-developers.com/showpost.php?p=62253081&postcount=6
4. Flash twrp (as described here ) ?
As you see, I am a bit puzzled about Safestrap... appreciate your help!
Thanks in advance,
syk
You are in a slightly better situation, you can use the rollback images.
The downgrade is done by following the instructions in the rollback image thread. Basically you backup your current stock slot, delete secondary slots (if you created any) so the space isn't in use, copy the rollback image to the HDX, access Safestrap and flash the rollback image to the stock slot - Safestrap (like TWRP) flashes .zip files directly to the required partition(s). Then do a factory reset (i.e. wipe - do NOT go into advanced wipe! DO NOT wipe System!!). Keep WLAN off/flight mode active, so you won't get updated by Amazon! Follow the instructions 100% correctly! Copy the 3.1.0 stock update to the HDX, then update Fire OS.
Un-installation of Safestrap is simple: Just open the Safestrap app and select "Uninstall Recovery". But following the downgrade procedure incl. the factory reset, Safestrap will be gone anyway, so no need to worry about its removal (note that this applies to the usage of the rollback Image procedure only!).
After the downgrade to 3.1.0 and the removal of Safestrap you can install TWRP, then backup your Fire OS in TWRP and move the backup to your PC (if the HDX is powered off, you can access TWRP this way: press and hold Volume up, then press and hold the Power botton, release both buttons when the grey Kindle logo appears on Screen.
TWRP Installation can be done via ADB (recommended) or apps like e.g. Flashify. If you haven't installed ADB already, see the link below. The TWRP.bin must be in the root of your HDX, i.e. if you open the HDX in a file explorer, don't open any other directory, just paste it right there.
Then flash the 3.2.3.2 bootloader from the link you mentioned, it's a .zip file to be flashed in TWRP (the install.bat is required for 3.2.5 and 3.2.6 only, you have 3.2.4 and don't need it anyway).
You can unlock the bootloader then, but you should install Minimal ADB and Fastboot and grab these Drivers. You also need to install the software mentioned here (i.e Python 2.7 and GMPY2 for Python 2.7).
Hi Cl4ncy,
all worked well so far, less hassle than feared.
As expected, I could not uninstall Safestrap after I applied the rollback (since the app was gone).
I flashed original stock rom 3.1.0 ( from here, just in case anyone also needs these files reading this thread), and upgraded the bootloader to 3.2.3 (but can't really check whether this worked, or is there any possibility to check that?).
I already prepared the unlock file beforehand, but the final step is still missing: unlocking the bootloader.
I can set my device into fastboot mode with adb, but fastboot on my PC can't find my device (adb, in contrast, found it..), and the driver linked here can't be downloaded because the board is over capacity.
I hope the driver solves my problem soon.
Do you have an other location to download the file?
And in the meantime: Why do I need to unlock the bootloader? The installation of the old Nexus 2.0.2 ROM seemed to work without that via Safetrap (or it just did not say that it unlocked the bootloader?)
What are the benefits of doing that?
Thanks again,
syk
I uploaded the drivers here.
Unlocking the bootloader is required for e.g. CM12 - Nexus or CM11 for Safestrap v4 either require to update to 4.5.2, root, and install Safestrap v4, or an unlocked bootloader. TWRP also enables far better recovery options, so TWRP & unlocked bootloader open the wonderland of HDX ROMs for you.
Thanks a lot, the drivers worked. I am now trying out the latest SlimROM already. Seems to be the most stable Lollipop ROM as of now...
So I am in the process of attempting to unlock my bootloader and basically following the steps done by sykarian as we were in similar boats(my original situation described here) and I have a few questions.
So far I have used the rollback image and updated using the 3.1.0 stock firmware without any problems. According to the posts in this thread, my next steps would be to uninstall safestrap, install TWRP, and flash the 3.2.3 bootloader. My issue is uninstalling safestrap. As far as I can tell, it's already gone as I can no longer boot into recovery and there is no safestrap app present. I see sykarian mentioning a similar issue but it's not exactly clear what he did from that point.
Am I ok to just go ahead and install TWRP at this point or is there something specific I need to do to ensure safestrap is removed? Also, I notice in the TWRP thread, it says to ensure that I am running stock firmware 3.2.3.2 before installation but that is not mentioned anywhere in the posts here. Is it ok to install it on the 3.1.0 firmware I am currently running? I do see in the first reply in this thread Cl4ncy says TWRP can be installed after rollback to 3.1.0 but I just want to make sure that also applies to my situation and not just the OP.
If anyone could clear this up for me I'd really appreciate it
muunkin said:
So I am in the process of attempting to unlock my bootloader and basically following the steps done by sykarian as we were in similar boats(my original situation described here) and I have a few questions.
So far I have used the rollback image and updated using the 3.1.0 stock firmware without any problems. According to the posts in this thread, my next steps would be to uninstall safestrap, install TWRP, and flash the 3.2.3 bootloader. My issue is uninstalling safestrap. As far as I can tell, it's already gone as I can no longer boot into recovery and there is no safestrap app present. I see sykarian mentioning a similar issue but it's not exactly clear what he did from that point.
Am I ok to just go ahead and install TWRP at this point or is there something specific I need to do to ensure safestrap is removed? Also, I notice in the TWRP thread, it says to ensure that I am running stock firmware 3.2.3.2 before installation but that is not mentioned anywhere in the posts here. Is it ok to install it on the 3.1.0 firmware I am currently running? I do see in the first reply in this thread Cl4ncy says TWRP can be installed after rollback to 3.1.0 but I just want to make sure that also applies to my situation and not just the OP.
If anyone could clear this up for me I'd really appreciate it
Click to expand...
Click to collapse
Indeed Safestrap will be gone after the usage of the rollback image, and the 3.1.0 stock firmware along with the factory reset during the whole downgrade procedure, so no need to worry about Safestrap anymore. It's important to note the difference between using the downgrade images available for 3.2.4, and the different procedure for 3.2.5/3.2.6!
The requirements for TWRP are firmwares 3.1.0 to 3.2.3.2 IIRC, at least 3.2.3.2 or below - 3.2.3.2 is just recommended due to some graphic glitches with Nexus. You can flash the 3.2.3.2 bootloader upgrade (or even upgrade Fire OS 3.2.3.2) via TWRP without any problems (updated Fire OS would just require to re-root).
Cl4ncy said:
Indeed Safestrap will be gone after the usage of the rollback image, and the 3.1.0 stock firmware along with the factory reset during the whole downgrade procedure, so no need to worry about Safestrap anymore. It's important to note the difference between using the downgrade images available for 3.2.4, and the different procedure for 3.2.5/3.2.6!
The requirements for TWRP are firmwares 3.1.0 to 3.2.3.2 IIRC, at least 3.2.3.2 or below - 3.2.3.2 is just recommended due to some graphic glitches with Nexus. You can flash the 3.2.3.2 bootloader upgrade (or even upgrade Fire OS 3.2.3.2) via TWRP without any problems (updated Fire OS would just require to re-root).
Click to expand...
Click to collapse
Thanks for the quick reply. So I completed all that, got my unlock code good to go and put my kindle into fastboot mode no problem. Now I see that in order to get fastboot on my pc to find my device I need use to drivers linked in this thread. I downloaded those but I'm not sure exactly what to do with them. Looks like this is my last hurdle here. Really appreciate all the help
Edit: Just noticed one of the links in this thread is to a post explaining how to use them haha. Reading through that now.
---------- Post added at 09:12 PM ---------- Previous post was at 08:56 PM ----------
Ok after following the instructions from that post I get an error that says "The third party INF does not contain digital signature information" and it won't install the drivers. I don't see any option to bypass the warning. I am on windows 10 if that makes a difference.
muunkin said:
Thanks for the quick reply. So I completed all that, got my unlock code good to go and put my kindle into fastboot mode no problem. Now I see that in order to get fastboot on my pc to find my device I need use to drivers linked in this thread. I downloaded those but I'm not sure exactly what to do with them. Looks like this is my last hurdle here. Really appreciate all the help
Edit: Just noticed one of the links in this thread is to a post explaining how to use them haha. Reading through that now.
---------- Post added at 09:12 PM ---------- Previous post was at 08:56 PM ----------
Ok after following the instructions from that post I get an error that says "The third party INF does not contain digital signature information" and it won't install the drivers. I don't see any option to bypass the warning. I am on windows 10 if that makes a difference.
Click to expand...
Click to collapse
Do you use Win 10 x64? Unfortunately the installation of unsigned drivers in 64 bit Windows is a pain in the ass. It'd help if you'd access to a 32 bit system, preferable Win 7. Win 10 also seems to have signed driver enforcement active if secure boot is enabled, disabling secure boot helps on 32 bit Win 10.
Cl4ncy said:
Do you use Win 10 x64? Unfortunately the installation of unsigned drivers in 64 bit Windows is a pain in the ass. It'd help if you'd access to a 32 bit system, preferable Win 7.
Click to expand...
Click to collapse
No problem! Already figured it out with a quick google search. Looks I'm unlocked and ready to go!
Really appreciate your help and quick responses man. Cheers.
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
ganiman said:
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
Click to expand...
Click to collapse
Your understanding of TWRP is right. Basically, we dd the twrp image with OS 4.5.3 bootloaders (the only bootloaders that will boot unsigned recovery) and then before leaving TWRP flash back (almost) current bootloaders and recovery.
You should be able to adb-sideload the OS 5.1.2 update to fix the freeze. Was device rooted before it updated? Do you know what OS it was on? If you have adb access while device is frozen, run these commands for current OS info:
adb shell getprop ro.build.version.fireos
adb shell getprop ro.build.version.number
No CM12 available. Mostly-working CM11 is here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138
BTW, I assume you tried wiping cache and/or factory reset in recovery. If not, I'd do that first.