[Q] Question - unlocking and CM12 on HDX 7" - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

So I've been reading these forums for the last 3 or 4 hours and I seem to be in an endless loop. I'm hoping people can help me untangle this mess, and perhaps I can write this up for others to enjoy.
I just picked up a HDX 7" with 13.3.0.5 on it. I dont care about the stock software, my ultimate goal is to get CM12.1 running on it.
So I see this ROM is available...
http://forum.xda-developers.com/kin...ent/rom-cm-12-unofficial-apollo-thor-t3050199
So from previous ROMing I know I need to get TWRP installed to get that running. So I find this post...
http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
However, first step is to unlock the bootloader... so I find this...
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
That says the first step is to install the "vulnerable" 13.3.2.3 firmware. Ok great...
http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
That first step there is to install TWRP :/ Seems we have an infinite loop here. Can anyone explain the proper procedure for going from stock 13.3.0.5 to CM12.1 using these procedures?

TWRP can be installed on your current firmware, its just recommended that you use 3.2.3.2 as a base since it's the most up to date exploitable firmware. You can update without TWRP if needed, just place the Amazon update bin in the root of your internal storage and check for updates with WiFi disabled.

derpadoodle said:
TWRP can be installed on your current firmware, its just recommended that you use 3.2.3.2 as a base since it's the most up to date exploitable firmware. You can update without TWRP if needed, just place the Amazon update bin in the root of your internal storage and check for updates with WiFi disabled.
Click to expand...
Click to collapse
@insodus - I agree with derpadoodle and have puzzled over the conflicting guidance myself. I can also confirm flashing the latest TWRP on 13.3.0.x is fine followed by the 3.2.3 bootloader (only) upgrade. You can then proceed with unlocking your bootloader and installing CM12. Gab a nandroid or two along the way just in case (best done from within TWRP).
You will obviously need to root your current firmware before proceeding. Don't forget to block OTA if you plan to enable wifi anytime before dumping stock. Also note a few things still aren't 100% in CM12; CM11 might be a better short-term choice and can be installed on with a locked bootloader (unlocking is still recommended).

Davey126 said:
@insodus - I agree with derpadoodle and have puzzled over the conflicting guidance myself. I can also confirm flashing the latest TWRP on 13.3.0.x is fine followed by the 3.2.3 bootloader (only) upgrade. You can then proceed with unlocking your bootloader and installing CM12. Gab a nandroid or two along the way just in case (best done from within TWRP).
You will obviously need to root your current firmware before proceeding. Don't forget to block OTA if you plan to enable wifi anytime before dumping stock. Also note a few things still aren't 100% in CM12; CM11 might be a better short-term choice and can be installed on with a locked bootloader (unlocking is still recommended).
Click to expand...
Click to collapse
Ok, so if I dont care about the amazon firmware because I want CM only... I still should update to 13.3.2.3 before unlocking?
1- Root it (any preferable method? towelroot?)
2- Install TWRP
3- Update the bootloader to 13.3.2.3
4- Unlock bootloader
5- Flash cm image

insodus said:
Ok, so if I dont care about the amazon firmware because I want CM only... I still should update to 13.3.2.3 before unlocking?
Click to expand...
Click to collapse
The 13.3.2.3 bootloader update is quick and easy. This code remains on your device even with other roms. So yeah, you should apply the update.
insodus said:
1- Root it (any preferable method? towelroot?)
2- Install TWRP
3- Update the bootloader to 13.3.2.3
4- Unlock bootloader
5- Flash cm image
Click to expand...
Click to collapse
My preference is HDX toolkit as it avoids wifi, installs SuperSU and has other handy options. However, it is a tethered solution which can be a PiTA. Towelroot should work fine too; I have used both.
Although it involves little risk bootloader unlocking is not for the faint of heart. You can always flash CM11 after step #3 and play with that while researching the bootloader unlock procedure. A recent tutorial by travanx captures most of the steps in one post. You'll want to start about halfway down.

Related

[Q] Installing CM-10.2 Android-4.3

Hey guys, I've rooted, installed CWM Recovery, Unlocked Bootloader, and installed CyanogenMod on another phone before.
The thing is, I've had this phone for about 6 months and wanted to do the same. However, after browsing through the forums, man are there a lot of scary sh*t going down. I would like the request the procedure to install CyanogenMod safely, without losing any Keys/IMEI/XReality/DRMkeys/Etcetera.
I dont know if the method given by FXP is supposed to be this straight forward, but I too like others, do not want to risk losing important stuff if it can be avoided (Keys/IMEI/XReality/DRMkeys/Etcetera).
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Frankly speaking, the forums is pretty much jumbled up, and the existing [Guide] Threads are either incomplete (Lacking important steps), or Unclear (Non-Specific steps).
Perhaps someone could do me a favour by using the template that I have below to help me, and possibly others, to install CM 10.2 on our beast of a phone.
Template:
1. Backup TA and DRMkeys and stuff: http://forum-xda-developers-com/backup
2. Root: http://forum-xda-developers-com/root
3. Recovery : http://forum-xda-developers-com/recovery
4: Unlock Bootloader: http://forum-xda-developers-com/ulbl
5: Install FXP's CM 10.2 :http://forum.xda-developers.com/showthread.php?t=2461286
Something like that would suffice I think, as long as no important steps are missing that would cause me to lose stuff unique to my phone, that cannot be recovered if I didn't back it up.
P.S. My version is 14.1.B.2.257
P.P.S. Thank you in advance.
1. Root
2. Backup TA (VERY IMPORTANT)
3. Install Recovery and unlock the bootloader, or the other way around. Both ways work.
4. Install ROM by following the "guide" that you quoted above.
Sent from my C6833 using Tapatalk
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Xenogenics said:
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Click to expand...
Click to collapse
you will have to back up the data anyways. I think unlocking the bootloader does a factory reset, as well one is needed going from stock to CM if i unforget correctly
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
stiggy2012 said:
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
Click to expand...
Click to collapse
OK, so looking into this further, you already need to have root to be able to flash the "CWM for locked bootloader" rocovery. So as far as I can see, the only way to get root in order to back up the TA partition is to give your IMEI to the Chinese via vRoot?
Thank god the stock rom is so good.
tommo123 said:
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
Click to expand...
Click to collapse
You have to unlock the bootloader to flash custom ROMs. You can flash stock ROMs without unlocking it, but you have to unlock it if you want CM, PAC, PA etc.
Sent from my C6833 using Tapatalk
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
tommo123 said:
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
Click to expand...
Click to collapse
Nothing will happen if you try it now. You can easily unlock the bootloader by going to Sony's Dev site, request your key and use Flashtool to unlock it. It takes a couple of minutes once you have Flashtool and the drivers installed. It's also perfectly safe to unlock it and you will lose your warranty. BUT you can easily relock it again if something happens to your ZU and the warrenty will be back.
Remember to backup your TA before you unlock your bootloader. It contains a lot if device info and your unique DRM keys. Unlocking the bootloader will wipe the system partition, but you will still have root, photos, music etc. (But do a backup of those just in case).
Sent from my C6833 using Tapatalk
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
tommo123 said:
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
Click to expand...
Click to collapse
If you've already backed up your TA, it means that you have the drivers installed, so job done All you have to do is to install Flashtool and get your key from Sony (which you will get on your email straight away). Either way, just ask here if/when you want to unlock it so we can guide you through it (it's very easy though).
ran flashtool but gave me driver errors - missing. unable to install the drivers included (i guess due to windows 8 driver signing)

got 3.0.5 thor, how should I proceed?

I just got a 3.0.5 thor from the store.
I'm looking to have root / gapps / and a full backup if my tablet cannot boot.
If a custom rom, like CM11 works well, i'd be good witht that too
after browsing posts, i see people talking bout downgrade to 3.2.8, and hdx toolkit that works on 3.1-3.2.7, and some poepl talking bout 4.2.5 being the one to be on
so basically, i have a super low version, what should I upgrade to, to be able to do all that stuff ^^
wzzupp548 said:
I just got a 3.0.5 thor from the store.
I'm looking to have root / gapps / and a full backup if my tablet cannot boot.
If a custom rom, like CM11 works well, i'd be good witht that too
after browsing posts, i see people talking bout downgrade to 3.2.8, and hdx toolkit that works on 3.1-3.2.7, and some poepl talking bout 4.2.5 being the one to be on
so basically, i have a super low version, what should I upgrade to, to be able to do all that stuff ^^
Click to expand...
Click to collapse
Your best best is to unlock the bootloader (can only be done if the device has never been upgraded past 3.2.6) which will allow you to flash several custom roms including Nexus, CM11 and CM12. Basic steps:
- upgrade to 3.1.0 (stock)
- root and block OTA using HDX toolkit
- flash twrp (custom version for HDX)
- update bootloader to 3.2.3.2 (custom build)
- unlock bootloader (a bit tricky)
- flash the rom of your choice
- enjoy!
Some things you don't want to do:
- connect to wifi without blocking OTA (you'll quickly be ungraded to a higher firmware with fewer options)
- upgrade past 3.2.6 you will permanently loose the ability to unlock your device
There are threads discussing each of these areas. It will take some reading/research. A few of the tasks entail moderate risk; follow instructions carefully. Unlike other android devices if you brick and HDX with a locked bootloader you're pretty much done.
Edit: FireOS versions noted in red have been updated (previously stated 3.2.3 which was incorrect)
thnx, for the help, I shal get started, and let ya know how it goes
Davey126 said:
Your best best is to unlock the bootloader (can only be done if the device has never been upgraded past 3.2.3.2) which will allow you to flash several custom roms including Nexus, CM11 and CM12. Basic steps:
- upgrade to 3.1.0 (stock)
- root and block OTA using HDX toolkit
- flash twrp (custom version for HDX)
- update bootloader to 3.2.3.2 (custom build)
- unlock bootloader (a bit tricky)
- flash the rom of your choice
- enjoy!
Some things you don't want to do:
- connect to wifi without blocking OTA (you'll quickly be ungraded to a higher firmware with fewer options)
- upgrade past 3.2.3 you will permanently loose the ability to unlock your device
There are threads discussing each of these areas. It will take some reading/research. A few of the tasks entail moderate risk; follow instructions carefully. Unlike other android devices if you brick and HDX with a locked bootloader you're pretty much done.
Click to expand...
Click to collapse

A little confused on how to get TWRP on my new Kindle Fire HDX 7"

Hey, so I purchased a Kindle Fire HDX 7" that came with the 13.3.0.5 firmware.
From what I was able to gather on here I was able to root, and disable the OTA , also installed xposed and HDxposed.
I might have got a little ahead of myself seeing I really want to get the bootloader unlock, twrp installed, and get a proper android OS rom installed.
All the posts I can find seem to be updated to only work on firmware .3.2.3.2 , and by flashing a rom using adb or a third party app to get twrp installed. From there it's smooth sailing to installing a custom rom.
So my question is , how the heck to I upgrade to firmware .3.2.3.2 without twrp already installed, and where can I find these .bins to get there?
Thanks for the help in advance.
Darmoktalk said:
Hey, so I purchased a Kindle Fire HDX 7" that came with the 13.3.0.5 firmware.
From what I was able to gather on here I was able to root, and disable the OTA , also installed xposed and HDxposed.
I might have got a little ahead of myself seeing I really want to get the bootloader unlock, twrp installed, and get a proper android OS rom installed.
All the posts I can find seem to be updated to only work on firmware .3.2.3.2 , and by flashing a rom using adb or a third party app to get twrp installed. From there it's smooth sailing to installing a custom rom.
So my question is , how the heck to I upgrade to firmware .3.2.3.2 without twrp already installed, and where can I find these .bins to get there?
Thanks for the help in advance.
Click to expand...
Click to collapse
While 3.2.3.2 is the recommended base you don't need it to flash twrp. Suggested path with links (assumes FireOS < xx.3.3.x, root and OTA block):
- (recommended): remove Xposed and HDXposed as they are not needed and may present complications. If you used HDXposed to block OTA remove the block before uininstalling (make sure your device is in airplane mode!) and use HDX toolkit instead (here) which is a tethered solution that offers root and OTA blocking along with other capabilities.
- (optional): sideload ES File Explorer which can be used to locate/manage downloaded files and verify checksums along with a host of other capabilities.
- (optional): sideload Flashify which can be used to back-up your current recovery and flash various components from within a functioning ROM. Back-up your existing recovery and leave on device (small).
- flash twrp (here) using the adb commands shown in the post or Flashify from within FireOS. Be sure to grab the version appropriate to your device. Restart device using power+<vol-up> to validate twrp is working.
- (recommended): from within twrp take a full backup and copy to an external host (just in case ...)
- from twrp upgrade bootloader to 3.2.3.2 (here)
- from twrp backup your device and copy to an external host (very important; don't skip this step)
- (recommended): from twrp flash Nexus v2.0.5 (Jelly Bean) and associated gapps package over FireOS which will give you full access to Google Play and a more flexible platform to work through the bootloader unlock procedure. FireOS is fickle beast; best to remove it from the equation early. Also verifies all is well with twrp.
Bounce back when the above is working and we'll turn to bootloader unlocking. A word of caution: while the above steps are relatively safe any flash gone bad can yield a a non-recoverable brick. Follow the procedures carefully, verify checksums on downloaded images, think twice before acting and don't go off script. Ask questions if unsure. Good luck.
Davey126 said:
While 3.2.3.2 is the recommended base you don't need it to flash twrp. Suggested path with links (assumes FireOS < xx.3.3.x, root and OTA block):
- (recommended): remove Xposed and HDXposed as they are not needed and may present complications. If you used HDXposed to block OTA remove the block before uininstalling (make sure your device is in airplane mode!) and use HDX toolkit instead (here) which is a tethered solution that offers root and OTA blocking along with other capabilities.
- (optional): sideload ES File Explorer which can be used to locate/manage downloaded files and verify checksums along with a host of other capabilities.
- (optional): sideload Flashify which can be used to back-up your current recovery and flash various components from within a functioning ROM. Back-up your existing recovery and leave on device (small).
- flash twrp (here) using the adb commands shown in the post or Flashify from within FireOS. Be sure to grab the version appropriate to your device. Restart device using power+<vol-up> to validate twrp is working.
- (recommended): from within twrp take a full backup and copy to an external host (just in case ...)
- from twrp upgrade bootloader to 3.2.3.2 (here)
- from twrp backup your device and copy to an external host (very important; don't skip this step)
- (recommended): from twrp flash Nexus v2.0.5 (Jelly Bean) and associated gapps package over FireOS which will give you full access to Google Play and a more flexible platform to work through the bootloader unlock procedure. FireOS is fickle beast; best to remove it from the equation early. Also verifies all is well with twrp.
Bounce back when the above is working and we'll turn to bootloader unlocking. A word of caution: while the above steps are relatively safe any flash gone bad can yield a a non-recoverable brick. Follow the procedures carefully, verify checksums on downloaded images, think twice before acting and don't go off script. Ask questions if unsure. Good luck.
Click to expand...
Click to collapse
Hey, thanks. I was able to get TWRP 2.8.7.0 flashed, and I made a backup first thing.
I ran into a problem however after installing the bootloader upgrade zip, I did a reboot after, and I'm only getting a black screen :/
I managed to get back in TWRP, should I restore that backup, or just move forward with installing the custom rom since I'll be overwriting fireOS anyway?
Thanks.
Ok, so I figured it was just a conflict with the version of FireOS since the recovery seemed to be functioning correctly.
I went ahead and installed the Nexus 2.0.5 rom and gapps. Success.. Boots into the rom fine, I tested some of the google apps, all is nice.
It appears to be working well, so I guess I'd be looking at installing a more updated roms, which needs an unlocked bootloader, yes?
Thanks again.
Darmoktalk said:
Ok, so I figured it was just a conflict with the version of FireOS since the recovery seemed to be functioning correctly.
I went ahead and installed the Nexus 2.0.5 rom and gapps. Success.. Boots into the rom fine, I tested some of the google apps, all is nice.
It appears to be working well, so I guess I'd be looking at installing a more updated roms, which needs an unlocked bootloader, yes?
Thanks again.
Click to expand...
Click to collapse
Great! Was a bit nervous (but not overly worried) after your first response. You took the path I would have recommended (flashing Nexus v2).
Suggestions before moving on to bootloader:
- make a backup of your system w/Nexus (just in case ...)
- reflash 3.2.3.2 bootloader update. There is no test for bootloader version; want to make sure you are on 3.2.3.2
Next step is to make sure you can access fastboot via Windows host. Linux and OSX also work (and are somewhat easier) but most of the tools/tips assume Windows. Take a peek at this post; expand to see full discussion if needed. Bounce back when everything is working. I am on the hunt for a very nice post from @Cl4ncy that details the bootloader unlock procedure. There are several other resources--just though s/he did a good job filling in detail. Stay tuned ...
Edit: A couple bootloader resources for you to ponder:
- procedure including links to various resources (here)
- post from @Cl4ncy referenced above (here)
You'll probably find the material a bit confusing at first. It's easier to answer specific questions than attempt to cover all the nuances. A lot depends on your experience with Android, Windows and the other tools referenced.
BTW - if you are using a 64-bit version of Windows > 8.0 (eg: 8.1, 10) you may need to disable the signed driver check. Bounce back if you have trouble installing the Kindle drivers referenced above.
Good luck - ask for help/clarification if needed!
---------- Post added at 04:00 PM ---------- Previous post was at 03:42 PM ----------
Darmoktalk said:
It appears to be working well, so I guess I'd be looking at installing a more updated roms, which needs an unlocked bootloader, yes?
Click to expand...
Click to collapse
Correct; bootloader needs to be unlocked for HDX variants of CM11, CM12 and Nexus v4 (and probably anything newer that comes along). See previous post for info on BL unlock procedure.
Davey126 said:
Great! Was a bit nervous (but not overly worried) after your first response. You took the path I would have recommended (flashing Nexus v2).
Suggestions before moving on to bootloader:
- make a backup of your system w/Nexus (just in case ...)
- reflash 3.2.3.2 bootloader update. There is no test for bootloader version; want to make sure you are on 3.2.3.2
Next step is to make sure you can access fastboot via Windows host. Linux and OSX also work (and are somewhat easier) but most of the tools/tips assume Windows. Take a peek at this post; expand to see full discussion if needed. Bounce back when everything is working. I am on the hunt for a very nice post from @Cl4ncy that details the bootloader unlock procedure. There are several other resources--just though s/he did a good job filling in detail. Stay tuned ...
Edit: A couple bootloader resources for you to ponder:
- procedure including links to various resources (here)
- post from @Cl4ncy referenced above (here)
You'll probably find the material a bit confusing at first. It's easier to answer specific questions than attempt to cover all the nuances. A lot depends on your experience with Android, Windows and the other tools referenced.
BTW - if you are using a 64-bit version of Windows > 8.0 (eg: 8.1, 10) you may need to disable the signed driver check. Bounce back if you have trouble installing the Kindle drivers referenced above.
Good luck - ask for help/clarification if needed!
---------- Post added at 04:00 PM ---------- Previous post was at 03:42 PM ----------
Correct; bootloader needs to be unlocked for HDX variants of CM11, CM12 and Nexus v4 (and probably anything newer that comes along). See previous post for info on BL unlock procedure.
Click to expand...
Click to collapse
Ok, so I've got adb+fastboot in a folder, booted the HDX into fastboot mode via TWRP restart>bootloader, got the PDAnet drivers installed, issued a fastboot -i 0x1949 devices command, and got a response "D0FBA0A034520HL7 fastboot" .. So it seems like it's talking to my device correctly?
EDIT:
Ok, so I had the eye of tiger and decided to go through with the unlock using CuberHDX.py, mashed my serials together to get my unlock, rebooted to fastboot, issued the flash unlock command for the .unlock file.. All green on my kindle screen "unlock code ok" .. Rebooted, and all is good.
I think.. It's done? Custom recovery, unlocked bootloader.
Darmoktalk said:
Ok, so I've got adb+fastboot in a folder, booted the HDX into fastboot mode via TWRP restart>bootloader, got the PDAnet drivers installed, issued a fastboot -i 0x1949 devices command, and got a response "D0FBA0A034520HL7 fastboot" .. So it seems like it's talking to my device correctly?
EDIT:
Ok, so I had the eye of tiger and decided to go through with the unlock using CuberHDX.py, mashed my serials together to get my unlock, rebooted to fastboot, issued the flash unlock command for the .unlock file.. All green on my kindle screen "unlock code ok" .. Rebooted, and all is good.
I think.. It's done? Custom recovery, unlocked bootloader.
Click to expand...
Click to collapse
TWRP & unlocked bootloader, you're ready for the wonderland of HDX ROMs then.
Be sure to install the correct one for your device, i.e. don't mix up Thor and Apollo ROMs.
Now you can decide, Nexus, CM11 or CM12 - your choice. Read the Installation notes and requirements carefully!
Cl4ncy said:
TWRP & unlocked bootloader, you're ready for the wonderland of HDX ROMs then.
Be sure to install the correct one for your device, i.e. don't mix up Thor and Apollo ROMs.
Now you can decide, Nexus, CM11 or CM12 - your choice. Read the Installation notes and requirements carefully!
Click to expand...
Click to collapse
Darmoktalk said:
Ok, so I've got adb+fastboot in a folder, booted the HDX into fastboot mode via TWRP restart>bootloader, got the PDAnet drivers installed, issued a fastboot -i 0x1949 devices command, and got a response "D0FBA0A034520HL7 fastboot" .. So it seems like it's talking to my device correctly?
EDIT:
Ok, so I had the eye of tiger and decided to go through with the unlock using CuberHDX.py, mashed my serials together to get my unlock, rebooted to fastboot, issued the flash unlock command for the .unlock file.. All green on my kindle screen "unlock code ok" .. Rebooted, and all is good.
I think.. It's done? Custom recovery, unlocked bootloader.
Click to expand...
Click to collapse
Congrats! You're ready to roll. Don't forget the occasional backup; don't flash anything not specifically customized for your device as you can still brick the puppy (although recovery is easier/possible with an unlocked bootloader). ROMs can be snagged from the top of the page (full xda site) or from appropriate threads in the HDX Android development forum. Have fun!
Thank you so much for the help. I came late to the game, and spent a few days reading through all the posts trying to piece together a starting point , and path to make it happen.
Learned a lot, thanks Davey126 for the walktrough and patience, and thanks Cl4ncy for the bootloader unlock instructions.
:good::good::good:
Hopefully this thread will also help others down the line.
Great job, keep it up
Could this be stickied? as it is a great how to/information spot.
Hi Davey126-
I tried following your procedure on a Thor with 13.3.2.8:
Davey126 said:
While 3.2.3.2 is the recommended base you don't need it to flash twrp. Suggested path with links (assumes FireOS < xx.3.3.x, root and OTA block):
- (recommended): remove Xposed and HDXposed as they are not needed and may present complications. If you used HDXposed to block OTA remove the block before uininstalling (make sure your device is in airplane mode!) and use HDX toolkit instead (here) which is a tethered solution that offers root and OTA blocking along with other capabilities.
- (optional): sideload ES File Explorer which can be used to locate/manage downloaded files and verify checksums along with a host of other capabilities.
- (optional): sideload Flashify which can be used to back-up your current recovery and flash various components from within a functioning ROM. Back-up your existing recovery and leave on device (small).
- flash twrp (here) using the adb commands shown in the post or Flashify from within FireOS. Be sure to grab the version appropriate to your device. Restart device using power+<vol-up> to validate twrp is working.
- (recommended): from within twrp take a full backup and copy to an external host (just in case ...)
- from twrp upgrade bootloader to 3.2.3.2 (here)
Click to expand...
Click to collapse
I'm fine until I try to flash TWRP; using Flashify or ADB seems to work but the unit will not boot into recovery. If I flash the stock recovery back all is well.
Looking at the TWRP download page, there's a note that the bootloader must be unlocked. I used the 1-Click unlocker, and it fails with Unlock Code is NOT correct. I guess my bootloader is not 3.2.3.2
I'm kind of stymied at this point, I'm guessing that I can't start with 13.3.2.8? Any advice on how to proceed would be really appreciated
Bob_in_RI said:
Hi Davey126-
I tried following your procedure on a Thor with 13.3.2.8:
I'm fine until I try to flash TWRP; using Flashify or ADB seems to work but the unit will not boot into recovery. If I flash the stock recovery back all is well.
Looking at the TWRP download page, there's a note that the bootloader must be unlocked. I used the 1-Click unlocker, and it fails with Unlock Code is NOT correct. I guess my bootloader is not 3.2.3.2
I'm kind of stymied at this point, I'm guessing that I can't start with 13.3.2.8? Any advice on how to proceed would be really appreciated
Click to expand...
Click to collapse
You can't unlock or flash TWRP on a tablet with FireOS 3.2.8.
Your only options would be to stay on 3.2.8 and install Safestrap 3, or manually upgrade to 4.5.2 and install Safestrap 4.
Thanks! I was able to install a ton with safestrap.
Davey126 said:
While 3.2.3.2 is the recommended base you don't need it to flash twrp. Suggested path with links (assumes FireOS < xx.3.3.x, root and OTA block):
Click to expand...
Click to collapse
Will this method also work starting from 13.3.2.4 Firmware or do I have to downgrade somehow first? Thanks.
Nana99 said:
Will this method also work starting from 13.3.2.4 Firmware or do I have to downgrade somehow first? Thanks.
Click to expand...
Click to collapse
You must downgrade first. Good news is you can use the downgrade images provided by @ggow, check page 2 here (page 1 is for 3.2.5/3.2.6 users who can NOT use those images!).
Is your HDX rooted and Safestrap installed? It won't get any easier then.
Any questions ask before you brick your HDX!
After the downgrade you can install TWRP, update the bootloader to 3.2.3.2, then unlock - try the one-click-solution first.
Be sure to create a backup of your current Fire OS via TWRP and move it to your PC before you flash any custom ROM!
Cl4ncy said:
You must downgrade first. Good news is you can use the downgrade images provided by @ggow, check page 2 here (page 1 is for 3.2.5/3.2.6 users who can NOT use those images!).
Is your HDX rooted and Safestrap installed? It won't get any easier then.
Any questions ask before you brick your HDX!
After the downgrade you can install TWRP, update the bootloader to 3.2.3.2, then unlock - try the one-click-solution first.
Be sure to create a backup of your current Fire OS via TWRP and move it to your PC before you flash any custom ROM!
Click to expand...
Click to collapse
Thanks. Yes my HDX is rooted and safestrap als well as Xposed and HDXposed is installed. I did all this over year ago shortly after I bought the device and never really touched it since then. However over time many things have stopped working correctly so I do want to upgrade to a more stabel version with gapps working or to a custom rom.
Please tell me which Firmware I have to downgrade to. Is it 3.1.0 or 3.2.3.2?
Thanks again for your support.
Nana99 said:
Thanks. Yes my HDX is rooted and safestrap als well as Xposed and HDXposed is installed. I did all this over year ago shortly after I bought the device and never really touched it since then. However over time many things have stopped working correctly so I do want to upgrade to a more stabel version with gapps working or to a custom rom.
Please tell me which Firmware I have to downgrade to. Is it 3.1.0 or 3.2.3.2?
Thanks again for your support.
Click to expand...
Click to collapse
The downgrade image is a modified 3.2.4 which claims to be 3.0.9, so you can "update" to 3.1.0, which is enough to install TWRP 2.8.7.0 (I'm not sure about TWRP 3.0.0-0, so install 2.8.7.0 and update to 3.0.0-0 via TWRP itself later, if you want to). There's no need to update to 3.2.3.2 then, as you can just update the bootloader (see above), which you should do via TWRP to solve a screen grafic issue.
Keep WLAN off/flight mode active during the procedure, you don't want to get updated by Amazon!
Cl4ncy said:
The downgrade image is a modified 3.2.4 which claims to be 3.0.9, so you can "update" to 3.1.0, which is enough to install TWRP 2.8.7.0 (I'm not sure about TWRP 3.0.0-0, so install 2.8.7.0 and update to 3.0.0-0 via TWRP itself later, if you want to). There's no need to update to 3.2.3.2 then, as you can just update the bootloader (see above), which you should do via TWRP to solve a screen grafic issue.
Keep WLAN off/flight mode active during the procedure, you don't want to get updated by Amazon!
Click to expand...
Click to collapse
Thanks once again. Everything worked perfectly. I downgraded with 3.2.4_rollback and "upgraded" to 3.1.0, rooted and installed twrp. Then updated the bootloader and installed nexus 2.05. Then unlocked the bootloader with 1-click. I then installed the nexus 4.0.5 rom along with the gapps. After that I installed CM13 together with open gapps and super-su.
Couldn't have done it without your help!!!:good::good::good:
Nana99 said:
Thanks once again. Everything worked perfectly. I downgraded with 3.2.4_rollback and "upgraded" to 3.1.0, rooted and installed twrp. Then updated the bootloader and installed nexus 2.05. Then unlocked the bootloader with 1-click. I then installed the nexus 4.0.5 rom along with the gapps. After that I installed CM13 together with open gapps and super-su.
Couldn't have done it without your help!!!:good::good::good:
Click to expand...
Click to collapse
Great! Enjoy your "free" HDX.

Will there ever be a more simple way to unlock bootloader Thor 13.3.2.4

I am on rooted Thor with 13.3.2.4, with the Nexus Rom installed via safestrap. I have been reading all the threads on unlocking the bootloader and find all of the steps to be very scary. I would like to wait until there was some kind of "toolkit" for this rather than having to first downgrade and then use python through adb etc which I am somewhat uncomfortable with. Will there ever be such a simpler solution?
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
I think I might try it this weekend. Thanks for the help.
Cl4ncy said:
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
Click to expand...
Click to collapse
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
I am by no means an expert but I just went through this process myself yesterday and it was relatively simple. Check this thread. It has a number of helpful posts in it, including my questions from yesterday.
The correct TWRP image is here. Just follow the instructions in that thread. It's super simple if you use the minimal adb and fastboot linked by Cl4ncy in the first thread I linked. If you have any other questions I'll do my best to help you.
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Cl4ncy said:
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Click to expand...
Click to collapse
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
kbs24 said:
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
Click to expand...
Click to collapse
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Cl4ncy said:
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Click to expand...
Click to collapse
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
kbs24 said:
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
Click to expand...
Click to collapse
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Cl4ncy said:
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Click to expand...
Click to collapse
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
kbs24 said:
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
Click to expand...
Click to collapse
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Cl4ncy said:
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Click to expand...
Click to collapse
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
kbs24 said:
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
Click to expand...
Click to collapse
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Cl4ncy said:
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Click to expand...
Click to collapse
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
kbs24 said:
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
Click to expand...
Click to collapse
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Davey126 said:
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Click to expand...
Click to collapse
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
kbs24 said:
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
Click to expand...
Click to collapse
(Also as you suggested, I did try flashing the zip 3.1.0 and it did not work, never rebooted successfully. So went back again to 3.0.9.)
kbs24 said:
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
Click to expand...
Click to collapse
Glad you were able to make some progress. I believe you could have flashed twrp from Nexus as I believe you successfully downgraded/upgraded to 13.3.2.3 which would then be the base version when you reininstalled Safestrap. But you found another path which is just fine.
It is possible the 13.3.1.0 is invalid (possibly corrupt). You can use ES File Explorer to validate the MD5 (c49c0363de4d8dfa5c87c1bdb88aa2ba) or download a fresh copy here. You can also upgrade directly to 13.3.2.3 instead of hopscotching through 13.3.1.0 and then applying the 13.2.3.3 bootloader update.
I strongly suggest you NOT connect to WiFi as it is unpredictable if/when you will receive at OTA and what version will be downloaded. Options for getting files onto you device:
- use HDX toolkit to root and block OTA on 13.3.0.9; you can then enable WiFi
- tether your device and drop files into "Internal Storage"
- use 'adb push' to transfer files
You should not need to mess with build.prop as the 3.2.4->3.0.9 rollback should have handed that. It's quite easy to brick your device if you get any of the edits or permissions wrong.

Trying to root htc m8

I have an at&t variant HTC m8, I recently stitched to cricket wireless. SIM swap went fine. I've been wanting to gain root to remove att bloatware. I'm on android version 5.0.2. My main issue is I've gotten nowhere unlocking boot loader using a pc. Tonight I resorted to using kingroot from Google play,which worked on third attempt. However supersu said it needs an update.
So basically I'm lost and trying to find away to gain root without a computer if possible.
I've never used kingroot. What happens if you try to update the root binary?
May be a bit irrelevant. I think you'll need to unlock the bootloader to do what you want (delete bloatware). I don't think kingroot alone will get it done. Reason being, you can't modify the system partition with root alone. You need kernel mod wp_mod, which is flashed with custom recovery TWRP. And you need an unlocked bootloader to flash custom recovery.
What issues did you have exactly when trying to unlock the bootloader?
I believe my main issue was that my pc is out of date running an unauthorized widows 7 lol. I was unable to obtain adb or any twrp files to unlock boot loader hence my attempt at a one click type solution. I think I'm going to read up more and try the whole process over this weekend, but any tips guides or instructions would be helpful. The more I have looked into this the more conflicted things have become.
Lewis715 said:
I was unable to obtain adb or any twrp files to unlock boot loader hence my attempt at a one click type solution.
Click to expand...
Click to collapse
Not sure what "unable to obtain adb" means if you don't explain what happens exactly, where you are trying to get the files, etc. So all I can do is assume, and hope that I don't suggest you do things you already tried.
If you want an adb/fastboot installer, the following should work, and decently up to date: http://forum.xda-developers.com/showthread.php?t=2317790
Otherwise, there are other adb installers if you just type "easy adb" into the XDA search function.
No such thing as TWRP files that can help you unlock the bootloader. By definition, you can't install custom recovery until the bootloader is unlocked, and TWRP is a custom recovery. So nothing can be done with or by any TWRP files until you unlock the bootloader.
Lewis715 said:
I think I'm going to read up more and try the whole process over this weekend, but any tips guides or instructions would be helpful. The more I have looked into this the more conflicted things have become.
Click to expand...
Click to collapse
Again, can't really help with what is "conflicted" unless you give some specific details.
Its understandable that a lot of the threads may be confusing, as the info is often outdated. This is getting to be an old device, and a lot of folks that wrote the various guides have moved on, and not updating the guides.
The following is a pretty good AT&T specific guide: http://forum.xda-developers.com/showthread.php?t=2799796
But as mentioned, some things are outdated:
1) The driver package is old. You can get updated drivers by downloading HTC Sync from the HTC website. After installing (which will also install HTC drivers) you can uninstall Sync, but keep the drivers; if you don't want Sync (but I haven't had any problems keeping it).
2) I believe the Dropbox link for adb installer is dead, but I already gave an alternative above.
3) The TWRP version is really old, don't use it! Get TWRP 3.0.2 from here: https://dl.twrp.me/m8/
The exception might be in the stock Android version on your phone is old, but if you tell me what it says for OS number on the bootloader screen, I can advise more specifically.
4) TWRP version is old, again, don't use it! v2.76 is the latest "stable" version, and you can get it here: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Everything else in the guide should still apply.
Vomer's guide is also a good one:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Again, the TWRP version is out of date (use the current one linked above).
You only need to do Sections 0 and 1, as the remainder of the guide (S-off, SuperCID) doesn't apply for what you are doing (unlock bootloader, custom recovery, and root).
Also, highly recommended to make a TWRP backup of the stock ROM, before you root.
After root, flash wp_mod with TWRP to enable system partition changes to stick (and deleting bloatware is a system change). What wp_mod depends on your Android version. But for Marshallow, the wp_mod can be found here (you just need the zip wp_mod, not the whole ROM): http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Thanks for the help I'll give it another try, honestly have no real need to mess with device. I know the phone is old but I still have it and it works better than others I've had.
Lewis715 said:
Thanks for the help I'll give it another try, honestly have no real need to mess with device. I know the phone is old but I still have it and it works better than others I've had.
Click to expand...
Click to collapse
Of course, the vast majority of us don't have any real need to mess with the device. But we do, nonetheless!

Categories

Resources