Hello,
i got an HDX 8.9 with 14.3.0.2 as replacement for a bricked one.
The old one was delivered with 3.2.8.
What root options i have for the new one. I found twrp for 3.0.5 but not for older version.
Can any one give me an advise?
thanks
Peter
Keep WLAN off/flight mode active, update to 3.2.3.2, root, install TWRP, unlock bootloader, and enjoy the wonderland of HDX ROMs.
If you need more detailed info, ask before you brick your new HDX ... please.
acutally yes i need more infos
Where to get the firmware 3.2.3.2? at first? Which thread of all those is it? I got a little confused which tutorial to use.
klofisch said:
acutally yes i need more infos
Where to get the firmware 3.2.3.2? at first? Which thread of all those is it? I got a little confused which tutorial to use.
Click to expand...
Click to collapse
Alright, here we go ...
stock firmwares are available here, be sure to get the correct for your device!
Root can be obtained with the HDX Toolkit,
TWRP is here,
you should install Minimal ADB and Fastboot,
and grab these drivers,
bootloader unlock procedure is described here, and after installation of all software mentioned there, also here,
read all the info, and again if you're unsure ask first. And keep WLAN off/flight mode active during the process.
Before you install a custom ROM disable OTA with the HDX Toolkit, backup Fire OS in TWRP and copy it to your PC, then install a ROM of your choice.
i have hdx toolkit 0.95. i think that is ok. It contains also towelroot. Is that fine to use?
Why not getting an older version than 3.2.3.2? Can i use CM12 on my device somehow? ))
a lot questions....sorry and thanks in advance
klofisch said:
i have hdx toolkit 0.95. i think that is ok. It contains also towelroot. Is that fine to use?
Why not getting an older version than 3.2.3.2? Can i use CM12 on my device somehow? ))
a lot questions....sorry and thanks in advance
Click to expand...
Click to collapse
Yes, Towelroot will work with 3.2.4 and below.
It is recommended to use 3.2.3.2, but not mandatory. So if you update, I'd suggest to use the recommended version.
After unlocking the bootloader (important!) you can use CM12, but CM12 requires an unlocked bootloader! Note that only versions below 3.2.4 can be unlocked, i.e. 3.2.3.2 and lower!
i have done most steps. and have few questions again.
1. Just to be sure "Apollo" is the codename for the 8.9"?
2. TWRP 2.8.7.0 is made from 4.5.3-Sources but i can use it with 14.3.2.3.2?
3. The complete command is "dd if=/sdcard/signed-apollo-twrp-2870.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"?
klofisch said:
i have done most steps. and have few questions again.
1. Just to be sure "Apollo" is the codename for the 8.9"?
2. TWRP 2.8.7.0 is made from 4.5.3-Sources but i can use it with 14.3.2.3.2?
3. The complete command is "dd if=/sdcard/signed-apollo-twrp-2870.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"?
Click to expand...
Click to collapse
1. Yes, Apollo = 8.9", Thor = 7"
2. TWRP can be used on 3.2.3.2 and lower only, therefore yes you can use it.
3. Yes, if you didn't change the file name of the TWRP Image, that's the complete command you have to enter in the ADB prompt, after you entered adb shell, and SU commands, also ensure you obtained root! And you copied the TWRP image to the root directory of your HDX' sdcard .
mhhh i am getting
"/dev/block/platform/msm_sdcc.1/by-name/recovery: cannot open for write: Permission denied"
su worked fine. can i use "sudo" like normal on a linux?
klofisch said:
mhhh i am getting
"/dev/block/platform/msm_sdcc.1/by-name/recovery: cannot open for write: Permission denied"
su worked fine. can i use "sudo" like normal on a linux?
Click to expand...
Click to collapse
Did you root 3.2.3.2? Seems weird to me to get permission denied there. While you're at it, you can disable OTA with HDX Toolkit as well.
yes i've seen it on myself )).
thanks
I found that out on my own )
When i run
fastboot -i 0x1949 devices
i cant see any device listed. I think its because i havent enabled developer options. And i can't actually..... i can hit the serial number 7time, 10time or 20time with out getting dev ops activated.
Is there something different with 3.2.3.2??
#edit: ok i forgot to install the drivers. Thats stiff on Windows 10 with unsigned drivers.
When i want to unlock my boot.img. Do i need only 'mmssssssss.unlock'-file or do i need also a modified "boot.img"?
cuberHDX.py has both options, but its not clear to me when to use what.
ok i took the risk..... its all good.
Thanks u all!
klofisch said:
ok i took the risk..... its all good.
Thanks u all!
Click to expand...
Click to collapse
So you've TWRP & unlocked bootloader now? Congratulations, you are able to enjoy the wonderland of HDX ROMs now.
thanks
Which are the latest gapps to install on fireos with 14.3.2.3.2?
klofisch said:
thanks
Which are the latest gapps to install on fireos with 14.3.2.3.2?
Click to expand...
Click to collapse
Don't mess with gapps on FireOS. You'll just create a Frankenkindle. Flash a custom rom (Nexus v4, CM11 or CM12) and gain full access to the play store with no compromises or conflicts. Nearly every native Kindle function can be duplicated with Android apps either from Amazon or 3rd parties. Notable exceptions are Amazon video downloads (streaming works fine), Kindle book sharing (purchases/viewing are ok) and Mayday. Yeah, that last one is a killer.
Can i just flash it over the existing FireOS? I cant see a possibilty to create a new Slot in TWRP, like on my old HDX 7.
I allready did a back up with TWRP.
klofisch said:
Can i just flash it over the existing FireOS? I cant see a possibilty to create a new Slot in TWRP, like on my old HDX 7.
I allready did a back up with TWRP.
Click to expand...
Click to collapse
Yes - custom roms overwrite the existing contents of the system partition in 'native' twrp. There is no option to create a secondary slot. In your case FireOS will be replaced by the rom of your choice (Nexus v4, cm11 or cm12). I suggest starting Nexus v4 or cm11. Be sure to follow instructions carefully. Ask questions if unsure.
Related
Q&A for [ROM] cm-11-20141216-UNOFFICIAL-thor
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.
Before posting, please use the forum search and read through the discussion thread for [ROM] cm-11-20141216-UNOFFICIAL-thor. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
This is great news!! Hope somebody will release the 4.5.2 bootloader unlock or the right rooting method so that we can test this rom!.. I'ts nice to see people working on this kindle fire! Keep up the good work!:good:
xiloraptor said:
This is great news!! Hope somebody will release the 4.5.2 bootloader unlock or the right rooting method so that we can test this rom!.. I'ts nice to see people working on this kindle fire! Keep up the good work!:good:
Click to expand...
Click to collapse
Thanks ! The sooner should be a root method, crossing fingers
Is it possible to flash this from fully a rooted & safestrapped HDX Nexus 2.0.2. firmware?
Going Postal said:
Is it possible to flash this from fully a rooted & safestrapped HDX Nexus 2.0.2. firmware?
Click to expand...
Click to collapse
No.
i ve read this rom: cm-11-20141217-UNOFFICIAL-thor.zip on this topic: http://forum.xda-developers.com/kindle-fire-hdx/development/cm-11-20141216-unofficial-thor-t2974818
Cause my HDX have update automatically to FireOs 4.5.2 via wifi, then i have to wait for so long time, for any root version can apply for Fire OS 4.5.2, then use that rom, hopefully you guys can release that soon, thanks Cpasjuste, many thanks for your hardwork :good::good::good:
Dont try this ROM
Hi, I tried this ROM.
I am not on a late version of fire OS so I thought it would work - in actual fact I was on 13.3.2.4 with root access.
I now have a semi bricked kindle which just shows Amazon Kindle in white. As I have only owned the thing for a day this is somewhat gutting.
Any help anyone could offer would be appreciated.
I am getting a factory cable so will try to fix with that - if not a return is in order...
Avoid this mod like the plague...
Rob
buyaodanxin said:
Hi, I tried this ROM.
I am not on a late version of fire OS so I thought it would work - in actual fact I was on 13.3.2.4 with root access.
I now have a semi bricked kindle which just shows Amazon Kindle in white. As I have only owned the thing for a day this is somewhat gutting.
Any help anyone could offer would be appreciated.
I am getting a factory cable so will try to fix with that - if not a return is in order...
Avoid this mod like the plague...
Rob
Click to expand...
Click to collapse
Well the thread made it pretty clear...
Cpasjuste said:
There is currently a very few user which will be able to use it as you either need an unlocked bootloader or a root exploit for amazon firmware 4.5.2 (which will come someday...).
Click to expand...
Click to collapse
I am new to this - so didnt appreciate that I didnt have what the image said do you think a factory cable allow me to repair this or is it toast ?
EncryptedCurse said:
Well the thread made it pretty clear...
Click to expand...
Click to collapse
buyaodanxin said:
I am new to this - so didnt appreciate that I didnt have what the image said do you think a factory cable allow me to repair this or is it toast ?
Click to expand...
Click to collapse
How did you flash it?
D0ubl3_X said:
How did you flash it?
Click to expand...
Click to collapse
With Safestrap from Zip.
What I am guessing happened is safestrap was launched from initial bootloader - overflashed bits it shouldnt have now initial bootloader doesnt like what it sees so no booting...
Any suggestions appreciated.
That's strange. I didn't used safestrap since a while so I'm not 100% sure what happened but you probably flashed the ROM on your STOCK slot which probably erased safestrap... (Like said before you shouldn't have used this ROM in first place and you shouldn't flash to stock ROM).
The problem now is to get adb working so you can restore something but I guess it won't be enabled for you since your device do not boot the flashed kernel. I'm not sure if it will be possible to use fastboot for flashing a signed kernel made by @vortox , this is maybe your only solution.
Cpasjuste said:
That's strange. I didn't used safestrap since a while so I'm not 100% sure what happened but you probably flashed the ROM on your STOCK slot which probably erased safestrap... (Like said before you shouldn't have used this ROM in first place and you shouldn't flash to stock ROM).
The problem now is to get adb working so you can restore something but I guess it won't be enabled for you since your device do not boot the flashed kernel. I'm not sure if it will be possible to use fastboot for flashing a signed kernel made by @vortox , this is maybe your only solution.
Click to expand...
Click to collapse
I'm fairly certain that the boot image didn't flash, it's just the system that's not booting. I was reading through the bootloader source today and it *seems* that if the signature is invalid on a flashed partition, then the device will boot into fastboot mode. Had the boot image actually flashed, he would get a picture for about 2 seconds then a reboot. It wouldn't just hang if this was a sfv (signature verification failure, I decided to abbreviate because it's hell to type out).
r3pwn said:
I'm fairly certain that the boot image didn't flash, it's just the system that's not booting. I was reading through the bootloader source today and it *seems* that if the signature is invalid on a flashed partition, then the device will boot into fastboot mode. Had the boot image actually flashed, he would get a picture for about 2 seconds then a reboot. It wouldn't just hang if this was a sfv (signature verification failure, I decided to abbreviate because it's hell to type out).
Click to expand...
Click to collapse
Your right, the problem is now his system partition. With a few luck he still have adb enabled, I think its his last chance isn't it.
Can someone tell me what I need to do to move from the HDX ROM (Kernel .3.2.4) to this one?
Apollo Hartigan said:
Can someone tell me what I need to do to move from the HDX ROM (Kernel .3.2.4) to this one?
Click to expand...
Click to collapse
If I am not wrong:
Download the upload 13.3.1.0 update file from here: http://forum.xda-developers.com/showthread.php?t=2782159
Make a back-up of your data using Safestrap and copy it to your pc.
Flash one of the two backups files provided by ggow in http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 depending on device. That would install a stock version with root enabled (if not u would need to do the whole root process)
Do a factory reset of your system
Copy the 13.3.1.0 downloaded before into the root and reboot to get the update installed.
Once the system is in 13.3.1.0 u would be able to install the TRWP and later the cm.
Maybe i am missing something, can anybody confirm?
qkp said:
If I am not wrong:
Download the upload 13.3.1.0 update file from here: http://forum.xda-developers.com/showthread.php?t=2782159
Make a back-up of your data using Safestrap and copy it to your pc.
Flash one of the two backups files provided by ggow in http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 depending on device. That would install a stock version with root enabled (if not u would need to do the whole root process)
Do a factory reset of your system
Copy the 13.3.1.0 downloaded before into the root and reboot to get the update installed.
Once the system is in 13.3.1.0 u would be able to install the TRWP and later the cm.
Maybe i am missing something, can anybody confirm?
Click to expand...
Click to collapse
I can reply to myself. cm-11-20150101-UNOFFICIAL-thor.zip installed and running
I was in 13.3.2.4 with Safestrap, OTA updates disabled, root....
My steps:
1-Back up your data using Safestrap and copy it to your personal computer.
2-Select Stock rom.
3-Flash one of the two backups files provided by ggow in http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 depending on device (Thor in my case). That would install a stock version pointing to 13.3.0.9. In my case root was not found so I needed to use again [TOOL:FROZEN] Faznx's HDX ToolKit v0.95 to disable OTA and put root.
3-Put the http://forum.xda-developers.com/showthread.php?t=2782159 at root level. Reboot the device, that would help the system to recognize the update, sometimes it takes a while. Put also TRWP and the cyanogenmod, I put them into download folder, but it doesn't matter.
4-Update the system, it would require a reboot.
5-Once in 13.3.1.0, check OTA updates are disabled and root is enabled, using Faznx again.
6-With OTA updates disabled, switch on wifi and install a file manager.
7-Install Rashr, download it from http://forum.xda-developers.com/showthread.php?t=2334554
8-Install TRWP image using Rashr.
9-Reboot on TRWP. Swip to factory reset and install the CM build.
10-Install CM Gapps for CM11.
I have found an issue with wifi, it required a reboot to get it working. Testing the other features right now.
I would like to use the google now launcher but CM doesn't detect the launcher as launcher. Maybe it is an issue of my device. Can someone try to set the google now launcher as default launcher?
At first, thanks a lot to all involved people to making a great device gets its full potential. Great work.
As it works fine for me so far, I was wondering if it is necessary to keep all the partitions, I got an emulateed ( legacy and 0) as well as two others. I suppose, these are two from the other rom slots I created. Im not sure if they take space at all?
Again, thanks for your effort and cheers.
disTractoR said:
At first, thanks a lot to all involved people to making a great device gets its full potential. Great work.
As it works fine for me so far, I was wondering if it is necessary to keep all the partitions, I got an emulateed ( legacy and 0) as well as two others. I suppose, these are two from the other rom slots I created. Im not sure if they take space at all?
Again, thanks for your effort and cheers.
Click to expand...
Click to collapse
No you don't need to delete them they are symlink used by the system and do not use space.
Hello i am currently running 13.3.2.1 on my HDX, i already root it and everything the only problem is that on that version recoveries dont work.
I tried them already.
So I downloaded the 13.3.2.3.2 to test on that one, this would be an upgrade for me but i already disable the OTA's. How do i upgrade to use recovery?
and question will this lose root?
what are the steps dont find anything.
Thank you
masterchop said:
Hello i am currently running 13.3.2.1 on my HDX, i already root it and everything the only problem is that on that version recoveries dont work.
I tried them already.
So I downloaded the 13.3.2.3.2 to test on that one, this would be an upgrade for me but i already disable the OTA's. How do i upgrade to use recovery?
and question will this lose root?
what are the steps dont find anything.
Thank you
Click to expand...
Click to collapse
TWRP should work fine on your current firmware level (13.3.2.1). However, since it is advisable to upgrade the bootloader to 13.3.2.3 do the following:
- install Flashify (free download from your favorite app store)
- use Flashify to install bootloader upgrade (here)
- use Flashify to install TWRP (here)
Davey126 said:
TWRP should work fine on your current firmware level (13.3.2.1). However, since it is advisable to upgrade the bootloader to 13.3.2.3 do the following:
- install Flashify (free download from your favorite app store)
- use Flashify to install bootloader upgrade (here)
- use Flashify to install TWRP (here)
Click to expand...
Click to collapse
Thank you bro!! i just got a boner!! ajajaj ill test that at home today . thank you!!:good:
masterchop said:
Thank you bro!! i just got a boner!! ajajaj ill test that at home today . thank you!!:good:
Click to expand...
Click to collapse
Err...glad I could help. Hope the Kindle part goes ok too.
Flashify is a powerful tool. Make sure you know what your are doing and flash the right components into the proper partitions. Flashify offers some protections but you can easily brick your device if done wrong. Assuming everything else is ok with your device; if stock recovery is borked you should probably fix that first.
Davey126 said:
Err...glad I could help. Hope the Kindle part goes ok too.
Flashify is a powerful tool. Make sure you know what your are doing and flash the right components into the proper partitions. Flashify offers some protections but you can easily brick your device if done wrong. Assuming everything else is ok with your device; if stock recovery is borked you should probably fix that first.
Click to expand...
Click to collapse
I was about to install flashify but my Google store is force closing multiple times.
I think i have stock recovery broken, do when i go to recovery i get blank screen.
I manage to install it thank you it was super easy with it. I have the SIM card version have test any roms
masterchop said:
I manage to install it thank you it was super easy with it. I have the SIM card version have test any roms
Click to expand...
Click to collapse
Glad it worked out. You can now flash CM11 or Nexus 2.0.5. CM12 requires an unlocked bootloader.
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.
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.
I got a new Motherboard and daughterboard in my HDX Apollo. I was able to get TWRP on it, but it keeps saying i dont appear to have root. I tried installing the latest supersu but it apparently didnt work. Anyway, i have realized that i just keep getting myself into trouble playing with root. All i want is to get my 3rd gen back to 4.5.5.1 fire os and wait for the fire os 5 update for it(hopefully) Any help on how i can do that? Ive tried downloading the latest Kindle update for apollo, renaming the .bin to update.zip and transferring it over and installing it but it never boots further than the 'kindle' screen.
Thanks for your help, sorry to be a pain
If you're on Fire OS 4.x you don't have TWRP, but Safestrap v4. After what you've done, do you still have access to Safestrap? Installing an amazon update with Safestrap installed, or even just rooted could easily mess up the device, i.e. brick it.
I don't think it's fire os 4x then. It does boot into the twrp interface and is fully functional but when you go to reboot into a different recovery it says something like "it appears you do not have root. Would you like to install supersu?" Even if I say yes it acts like it installs but apparently doesn't. I can post pics later
Sent from my SM-G920V using XDA-Developers mobile app
Cl4ncy said:
If you're on Fire OS 4.x you don't have TWRP, but Safestrap v4. After what you've done, do you still have access to Safestrap? Installing an amazon update with Safestrap installed, or even just rooted could easily mess up the device, i.e. brick it.
Click to expand...
Click to collapse
Oh and I'm not sure what the new board had on it. It never fully booted. That's why I installed twrp. Thanks for the reply though!
Sent from my SM-G920V using XDA-Developers mobile app
mhuck0625 said:
I don't think it's fire os 4x then. It does boot into the twrp interface and is fully functional but when you go to reboot into a different recovery it says something like "it appears you do not have root. Would you like to install supersu?" Even if I say yes it acts like it installs but apparently doesn't. I can post pics later
Click to expand...
Click to collapse
mhuck0625 said:
Oh and I'm not sure what the new board had on it. It never fully booted. That's why I installed twrp. Thanks for the reply though!
Click to expand...
Click to collapse
- how did you "install" TWRP (method)?
- how are you accessing TWRP - just pressing the power button or some key combination (yes, it's important)?
- does a graphic vaguely resembling Frankenstein appear when you power up the device?
Davey126 said:
- how did you "install" TWRP (method)?
- how are you accessing TWRP - just pressing the power button or some key combination (yes, it's important)?
- does a graphic vaguely resembling Frankenstein appear when you power up the device?
Click to expand...
Click to collapse
I installed TWRP using the method instructed here: http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197
When i want to get to TWRP i press and hold Power + Vol UP until it rebootes into the Teamwin screen and TWRP. It is version 2.8.7.0 now(the instructions got 2.8.5.0 installed then i upgraded)
I dont remember what the graphic looked like when booting into TWRP but i know it said TeamWin. I can check when i get it charged back up enough to turn on. Ive had it sitting unplugged for days and the battery ran dead. I hope this is enough info to help get me pointed in the right direction. Thanks!
Ok, if it's the real TWRP which it seems to be, Safestrap has no TeamWin logo at boot, I'd suggest you leave it be. Currently you can use all available ROMs, so if there'll be a future version of Fire OS you could use a TWRP flashable version of it. I doubt there will be a Fire OS 5 update for the "old" Thor/Apollo line though.
You would destroy the possibilities you currently have by updating to Fire OS 4.5.5.1.
Meanwhile you can unlock your bootloader (if you haven't already), and update TWRP to 3.0.0-1 (requires unlocked bootloader).
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Sent from my SM-G920V using XDA-Developers mobile app
Cl4ncy said:
Ok, if it's the real TWRP which it seems to be, Safestrap has no TeamWin logo at boot, I'd suggest you leave it be. Currently you can use all available ROMs, so if there'll be a future version of Fire OS you could use a TWRP flashable version of it. I doubt there will be a Fire OS 5 update for the "old" Thor/Apollo line though.
You would destroy the possibilities you currently have by updating to Fire OS 4.5.5.1.
Meanwhile you can unlock your bootloader (if you haven't already), and update TWRP to 3.0.0-1 (requires unlocked bootloader).
Click to expand...
Click to collapse
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Sent from my SM-G920V using XDA-Developers mobile app
There's no risk in unlocking, the bootloader either unlocks or it errors/fails. Try the one-click-solution first (might require the PDANet drivers). It's recommended to update the bootloader to 3.2.3.2 (do it only, if the unlock worked ok).
TWRP can be updated from TWRP itself, so I'd recommend doing it that way. Just be sure to flash the TWRP image to the recovery partition.
Cl4ncy said:
There's no risk in unlocking, the bootloader either unlocks or it errors/fails. Try the one-click-solution first (might require the PDANet drivers). It's recommended to update the bootloader to 3.2.3.2 (do it only, if the unlock worked ok).
TWRP can be updated from TWRP itself, so I'd recommend doing it that way. Just be sure to flash the TWRP image to the recovery partition.
Click to expand...
Click to collapse
Tried 1-Click. In both Linux(Ubuntu 16.04) and Windows(10.1 x64) i get an error saying ADB is not enabled on the device. Ive tried booting into fastboot(with fastboot cable) tried using the regular cable and booting into TWRP. Any combination of boot modes and cables i can think of wont work. Where should i go from here?
Thanks
mhuck0625 said:
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Click to expand...
Click to collapse
Root is irrelevant at this stage as nothing has been flashed to the system partition (where ROMs live).
Davey126 said:
Root is irrelevant at this stage as nothing has been flashed to the system partition (where ROMs live).
Click to expand...
Click to collapse
Ok, so i will need root to install ROMs then? How do i solve my problem unlocking the bootloader?
mhuck0625 said:
Tried 1-Click. In both Linux(Ubuntu 16.04) and Windows(10.1 x64) i get an error saying ADB is not enabled on the device. Ive tried booting into fastboot(with fastboot cable) tried using the regular cable and booting into TWRP. Any combination of boot modes and cables i can think of wont work. Where should i go from here?
Thanks
Click to expand...
Click to collapse
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Davey126 said:
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Click to expand...
Click to collapse
I do have mtp access and can transfer files easily. Should I try installing a Rom to see if I get adb access? What's a good Rom to try
Sent from my SM-G920V using XDA-Developers mobile app
Davey126 said:
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Click to expand...
Click to collapse
Just curious on one thing. Whenever i see a ROM to download it says i need to unlock the bootloader and have root before i can do that. In MY case i do NOT have either, yet i was able to flash a new recovery(TWRP) How is this possible? How would i go about installing a new ROM or unlocking the bootloader?
Is there a way to flash the stock recovery back so i can reinstall fireOS and start from scratch?
Is there a way to tell what bootloader i have from within TWRP?
I realize i probably should have done a little more reading before i started messing with it :/ I do appreciate all the help you have been able to provide so far!
mhuck0625 said:
I do have mtp access and can transfer files easily. Should I try installing a Rom to see if I get adb access? What's a good Rom to try
Click to expand...
Click to collapse
mhuck0625 said:
Just curious on one thing. Whenever i see a ROM to download it says i need to unlock the bootloader and have root before i can do that. In MY case i do NOT have either, yet i was able to flash a new recovery(TWRP) How is this possible? How would i go about installing a new ROM or unlocking the bootloader?
Is there a way to flash the stock recovery back so i can reinstall fireOS and start from scratch?
Is there a way to tell what bootloader i have from within TWRP?
I realize i probably should have done a little more reading before i started messing with it :/ I do appreciate all the help you have been able to provide so far!
Click to expand...
Click to collapse
- traveling; response will be brief
- suggest flashing cm11 as it does not require an unlocked bootloader nor GAaps for basic functionality
- include SuperSU in flash package to secure root
- follow flashing directions in cm11 OP
- report back results; will go from there
Davey126 said:
- traveling; response will be brief
- suggest flashing cm11 as it does not require an unlocked bootloader nor GAaps for basic functionality
- include SuperSU in flash package to secure root
- follow flashing directions in cm11 OP
- report back results; will go from there
Click to expand...
Click to collapse
Downloaded CM11 and installed via this thread
http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
Copied it as well as the latest SuperSu(v2.65) to the Kindle Fire
Went to Install, saw both Zip files. Selected them(CM11 first, then Supersu second) Swipe to install, rebooted and nothing came up. Rebooted into TWRP and repeated the process after wiping dalvik/cache. Still nothing
mhuck0625 said:
Downloaded CM11 and installed via this thread
http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
Copied it as well as the latest SuperSu(v2.65) to the Kindle Fire
Went to Install, saw both Zip files. Selected them(CM11 first, then Supersu second) Swipe to install, rebooted and nothing came up. Rebooted into TWRP and repeated the process after wiping dalvik/cache. Still nothing
Click to expand...
Click to collapse
Makes sense. Likely no kernel. Will probably need to install a full version of FireOS for underlying components. Need to have a think about which build to maximize results, minimize rework. More later....
Davey126 said:
Makes sense. Likely no kernel. Will probably need to install a full version of FireOS for underlying components. Need to have a think about which build to maximize results, minimize rework. More later....
Click to expand...
Click to collapse
You have no idea how much i appreciate the help!
I look forward to hearing what you come up with!!
I would be happy just going straight back to full fire os - Stock EVERYTHING and not even worrying about running another OS. I just want to have a usable tablet again!