[Thor][Apollo] Unlocking bootloader with any firmware

[nhatanh181]

FAQ:​

1. if your get "not such file or directory" after su in step 2 (this is SAFESTRAP related possibly)- try to use next commands:

adb shell
su
dd if=/storage/emulated/0/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/storage/emulated/0/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot

http://xdaforums.com/showpost.php?p=68751981&postcount=35

Shouldn't be possible. Will provide a more complete response within 12 hours. Got a few irons in the Fire at present (sorry)

I suppose you're right. I followed Step 2 and twrp recovery img might have override the safestrap.

I found safestrap rom-slot file as well as old kindle app folders:

 

[DB126]

FAQ:
1. if your get "not such file or directory" after su in step 2 (this is SAFESTRAP related possibly)- try to use next commands:

I suppose you're right. I followed Step 2 and twrp recovery img might have override the safestrap.

I found safestrap rom-slot file as well as old kindle app folders: https://www.youtube.com/watch?v=https://www.youtube.com/watch?v=7kUzm0FzOMU

After pondering a couple options I believe the safest path is to unlock the bootloader (realize this apparently failed before) and reflash twrp. That will yield a known configuration that is suitable for flashing CM13 or other HDX compatible ROMs.

Currently your device is in an unknown/unproven state. You should not have been able to flash TWRP 3.0.2 or CM-13 with a locked bootloader. Safestrap remnants are also concerning. Normally I would advise a full wipe and reflash of the system partition but that could have unfavorable outcomes given the potentially unstable config.

If CM-13 boots don't change anything! Retrace and repeat steps taken to unlock the bootloader, correcting any errors as needed. Once the bootloader is successfully unlocked return to CM-13 and use Flashify (available in the Play Store or via apkmirror) to backup your current recovery and flash HDX build of TWRP 3.0.2.

Once complete power down device and then restart via <power>+<vol-up> to confirm native TWRP 3.0.2 is properly installed in the recovery partition. That's your proof positive confirmation the device is unlocked. From there you can proceed with a full wipe (system, data, dalvik and cache partitions; can leave "internal storage" as is) and then reflash CM-13 plus a suitable GAaps package (suggest nano). Be sure to flash GAaps concurrent with CM-13; doing it later often leads to problems (generic CM 12/13 issue). Alternatively, you could go with Nexus 6.0.1 which is all inclusive; just one zip to flash!

Sorry for the novel. Again, ask questions as needed. Good luck.

 

[nhatanh181]

After pondering a couple options I believe the safest path is to unlock the bootloader (realize this apparently failed before) and reflash twrp. That will yield a known configuration that is suitable for flashing CM13 or other HDX compatible ROMs.

Currently your device is in an unknown/unproven state. You should not have been able to flash TWRP 3.0.2 or CM-13 with a locked bootloader. Safestrap remnants are also concerning. Normally I would advise a full wipe and reflash of the system partition but that could have unfavorable outcomes given the potentially unstable config.

If CM-13 boots don't change anything! Retrace and repeat steps taken to unlock the bootloader, correcting any errors as needed. Once the bootloader is successfully unlocked return to CM-13 and use Flashify (available in the Play Store or via apkmirror) to backup your current recovery and flash HDX build of TWRP 3.0.2.

Once complete power down device and then restart via <power>+<vol-up> to confirm native TWRP 3.0.2 is properly installed in the recovery partition. That's your proof positive confirmation the device is unlocked. From there you can proceed with a full wipe (system, data, dalvik and cache partitions; can leave "internal storage" as is) and then reflash CM-13 plus a suitable GAaps package (suggest nano). Be sure to flash GAaps concurrent with CM-13; doing it later often leads to problems (generic CM 12/13 issue). Alternatively, you could go with Nexus 6.0.1 which is all inclusive; just one zip to flash!

Sorry for the novel. Again, ask questions as needed. Good luck.

Good news! I got the bootloader unlock. I don't know why this time it works. May be your assurance give me confidence. Thank you!

I still want to use amazon prime benefits. Is there anyway i can have CM with kindle ROM ?

 

[DB126]

Good news! I got the bootloader unlock. I don't know why this time it works. May be your assurance give me confidence. Thank you!

I still want to use amazon prime benefits. Is there anyway i can have CM with kindle ROM ?

lol - no. One or the other. But most Prime benefits can be obtained through Amazon apps available through the Play Store. A notable exception is "Amazon Underground" (shopping and Prime Video) which must be obtained directly from Amazon. Google refuses to host it as offers apps (often free) that are available for purchase in the Play Store.

 

[nhatanh181]

lol - no. One or the other. But most Prime benefits can be obtained through Amazon apps available through the Play Store. A notable exception is "Amazon Underground" (shopping and Prime Video) which must be obtained directly from Amazon. Google refuses to host it as offers apps (often free) that are available for purchase in the Play Store.

CM13 is really tempting, but i must use kindle ROM to get a free borrow book every month (only thing i hold on to the crazy FireOS).

So i found this twrp compatible: http://xdaforums.com/kindle-fire-hdx/development/recovery-twrp-3-0-0-0-t3322547

I re-write down your steps to be sure that i get it right:
1 . Back up current recovery img with Flashify
2. Flash the twrp in the link above
3. Boot into recovery and Wipe Dalvik/Data/Cache/System and flash ROM

I can find anywhere stock recovery, does twrp back it up somewhere?

 

[DB126]

CM13 is really tempting, but i must use kindle ROM to get a free borrow book every month (only thing i hold on to the crazy FireOS).

So i found this twrp compatible: http://xdaforums.com/kindle-fire-hdx/development/recovery-twrp-3-0-0-0-t3322547

I re-write down your steps to be sure that i get it right:
1 . Back up current recovery img with Flashify
2. Flash the twrp in the link above
3. Boot into recovery and Wipe Dalvik/Data/Cache/System and flash ROM

I can find anywhere stock recovery, does twrp back it up somewhere?

Stock recovery was replaced when TWRP was flashed (no auto backup). Seems you prefer FireOS. What ROM is installed now? Care must be taken reinstalling FireOS to avoid a potential brick scenario.

 

[nhatanh181]

Stock recovery was replaced when TWRP was flashed (no auto backup). Seems you prefer FireOS. What ROM is installed now? Care must be taken reinstalling FireOS to avoid a potential brick scenario.

It's running CM 13 with twrp 3.0.2-0 ( i know lot of people would be happy to trade place with mine). The kindle is 7", the ultimate goal is to reverse to the original design with stock recovery, fireOS with safestrap and CM 11.

 

[DB126]

It's running CM 13 with twrp 3.0.2-0 ( i know lot of people would be happy to trade place with mine). The kindle is 7", the ultimate goal is to reverse to the original design with stock recovery, fireOS with safestrap and CM 11.

You're not going get stock recovery back (easily) nor is there any reason to. It sounds like you were running FireOS in the STOCK slot and CM 11 in a secondary slot. You decided which ROM to use (FireOS or CM 11) when the device booted. You used CM 11 most of the time but booted FireOS on occasion to grab a free book (more accurately borrow a book from the Kindle Owners' Lending Library). Is that correct? Sorry for all the questions but it's important to understand the desired end state.

Although you may not have known it running multiple ROMs under Safestrap v4 (a special version for HDX devices) introduces significant problems. ROMs in secondary slots never sleep and can only utilize two of the four available processors. The two active processors are locked full throttle increasing heat and taking a toll on battery life. WiFi and/or Bluetooth radios don't always work in secondary slots although CM11 seems to be an exception.

 

[nhatanh181]

You're not going get stock recovery back (easily) nor is there any reason to. It sounds like you were running FireOS in the STOCK slot and CM 11 in a secondary slot. You decided which ROM to use (FireOS or CM 11) when the device booted. You used CM 11 most of the time but booted FireOS on occasion to grab a free book (more accurately borrow a book from the Kindle Owners' Lending Library). Is that correct? Sorry for all the questions but it's important to understand the desired end state.

Although you may not have known it running multiple ROMs under Safestrap v4 (a special version for HDX devices) introduces significant problems. ROMs in secondary slots never sleep and can only utilize two of the four available processors. The two active processors are locked full throttle increasing heat and taking a toll on battery life. WiFi and/or Bluetooth radios don't always work in secondary slots although CM11 seems to be an exception.

Yes, that's the end game i'm looking for. Everything could have been like that nice and easy until i came across this thread. OP should have give a warning about how difficult it will be to reverse back the process. I always thought unlocked is better than locked so i can get CM13 running with FireOS, but it turns out to be one way street. I'm aware of heat and battery life while running safestrap, but i have no other options given the desire to have a free book every month.

 

[DB126]

Yes, that's the end game i'm looking for. Everything could have been like that nice and easy until i came across this thread. OP should have give a warning about how difficult it will be to reverse back the process. I always thought unlocked is better than locked so i can get CM13 running with FireOS, but it turns out to be one way street. I'm aware of heat and battery life while running safestrap, but i have no other options given the desire to have a free book every month.

Understood. You''ll need a special build of FireOS to accomplish your objectives without jeopardizing the device. I have put a request in to another contributor who has done this before; let's see what comes back in the next 24-48 hours. There are other options but all involve more work, risk or both.

 

[DB126]

Understood. You''ll need a special build of FireOS to accomplish your objectives without jeopardizing the device. I have put a request in to another contributor who has done this before; let's see what comes back in the next 24-48 hours. There are other options but all involve more work, risk or both.

Checking in. The contributor mentioned above has not responded to my inquiry and has been absent from XDA (no posts) for nearly two months. Thinking he may be out-of-pocket for awhile.

You need a custom build of FireOS that can be flashed with TWRP. A stock version downloaded from Amazon would likely brick your device. At present only version 4.5.5 is available which is not rootable. That means no Safestrap or CM11. While fully functional it can not be upgraded or rolled back as both operations depend on the Amazon stock recovery which has been overwritten by TWRP. Catch 22.

Up to you: hang on CM 13 (or any other custom ROM) or fall back to v4.5.5 which will leave you with pure FireOS. Conceivably you could keep backups of CM 13 and FireOS on your device (assuming a 32/64 GB model) and toggle back and forth by restoring archives in TWRP. Very messy. Alternatively, you can create your own custom FireOS 4.5.5.1 build using a python based developer tool. Doesn't look that tricky once you have python and associated libraries up an running on a suitable host.

 

[nhatanh181]

Checking in. The contributor mentioned above has not responded to my inquiry and has been absent from XDA (not posts) for nearly two months. Thinking he may be out-of-pocket for awhile.

You need a custom build of FireOS that can be flashed with TWRP. A stock version downloaded from Amazon would likely brick your device. At present only version 4.5.5 is available which is not rootable. That means no Safestrap or CM11. While fully functional it can not be upgraded or rolled back as both operations depend on the Amazon stock recovery which has been overwritten by TWRP. Catch 22.

Up to you: hang on CM 13 (or any other custom ROM) or fall back to v4.5.5 which will leave you with pure FireOS. Conceivably you could keep backups of CM 13 and FireOS on your device (assuming a 32/64 GB model) and toggle back and forth by restoring archives in TWRP. Very messy. Alternatively, you can create your own custom FireOS 4.5.5.1 build using a python based developer tool. Doesn't look that tricky once you have python and associated libraries up an running on a suitable host.

I will take your advice and stay still with CM for now. One small concern though, should i leave the unlocked bootloader be unlocked?

 

[DB126]

I will take your advice and stay still with CM for now. One small concern though, should i leave the unlocked bootloader be unlocked?

CM 13 (and most other custom ROMs for this device) and twrp require an unlocked bootloader. There are no risks, exposures or potential 'gotchas'. FireOS runs fine on unlocked devices. No need to relock.

 

[houkai4355]

/system/bin/sh: python.exe: not found

can not done the step 1.2 after install pyhon2.7 and gmpy2.2.0.2, I am a newbie,sry!

 

[DB126]

can not done the step 1.2 after install pyhon2.7 and gmpy2.2.0.2, I am a newbie,sry!

If you post your device manfid and serial another contributor may provide an unlock file. There is no risk publicly posting these values (and the corresponding unlock file) as they are only applicable to your device.

 

[ONYXis]

/system/bin/sh: python.exe: not found

Seems you tried to do this in adb shell
you need to do this in cmd

 

[DB126]

@ONYXis - was looking through OP again and noticed an important detail: seems twrp can be flashed on any 3rd gen HDX without first unlocking the bootloader. Explains why a recent poster was able to install twrp (and apparently flash cm13) despite a failed unlock (he subsequently fixed it). Any known issues/limitations aside from those imposed by the locked bootloader itself?

All my devices are unlocked so I didn't pick up on this earlier (just skimmed the OP). I can see situations where getting twrp working without immediately unlocking could be advantageous.

 

[houkai4355]

all done

thanks， I have flashed cm13

 

[ONYXis]

@ONYXis - was looking through OP again and noticed an important detail: seems twrp can be flashed on any 3rd gen HDX without first unlocking the bootloader..

Twrp image signed with cuber and vulnarable bootloader 3.2.3.2 can boot it without unlocking.
As for CM13 I remember what our devs wrote that is not enough to sign boot.img of custom rom with cuber to work, but I do not tried.
Sure, we can use twrp without unlock as advanced recovery, but why?

 

[DB126]

Twrp image signed with cuber and vulnarable bootloader 3.2.3.2 can boot it without unlocking.
As for CM13 I remember what our devs wrote that is not enough to sign boot.img of custom rom with cuber to work, but I do not tried.
Sure, we can use twrp without unlock as advanced recovery, but why?

Ah - thank you! Makes sense now as leveraging vulnerable 3.2.3.2 bootloader (missed that). As for custom ROMs I would never advocate flashing on a locked bootloader unless explicitly indicated it is acceptable by dev (currently only KitKat based roms).