[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 8 2017 (douglas)

[CuF]

ok sry for double post, thanks for the help, now have 15.1 installed

Did that fix your issue?

 

[hayabusa777]

Did that fix your issue?

Yes

 

[CuF]

Glad to hear it. That issue is the reason I'm sticking with 15.1 as well.

 

[chamelo003]

Can this be performed on fire os 5.7.0.0?

 

[vjunk]

Can this be performed on fire os 5.7.0.0?

Yes, but I had some trouble following the original instructions so put together some of my own. I only ran through these once so they are not perfect, but at least they provide more detail.

Start with the original instructions, then, when you get to this part:

NOTE: If you are on a firmware newer than 5.6.4.0, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)
If you chose the brick option, you don't need to run step-2.sh below:

Do the following:

1. Make sure ModemManager is disabled or uninstalled (as per the original instructions).
2. if the latest version of amonet-douglas is still 1.2, there is a bug in the code. To fix it:
   a. Under amonet/bin, copy functions.inc to functions.inc.org.
   b. Edit functions.inc. In the get_root() function, change the following:
   

       while [ $ROOT -ne 0 ]; do
         adb shell /data/local/tmp/mtk-su -c "/data/local/tmp/busybox mount /data/local/tmp/minisu.img /system/xbin/"
         adb shell su -c id | grep uid=0\(root\)
         ROOT=$?
         [ $ROOT -ne 0 ] && sleep 1
       done

   to:
   

       COUNTER=30
       while [[ $ROOT -ne 0  &&  $COUNTER -gt 0 ]]; do
         adb shell /data/local/tmp/mtk-su -c "/data/local/tmp/busybox mount /data/local/tmp/minisu.img /system/xbin/"
         adb shell su -c id | grep uid=0\(root\)
         ROOT=$?
         [ $ROOT -ne 0 ] && sleep 1
         echo Trying for $COUNTER more seconds...
         ((COUNTER--))
       done

3. Download and extract "brick-douglas.zip".
4. Copy the extracted mtk-su (in one of the original steps) from the arm64 directory to the brick-douglas/amonet/bin directory.
5. Open another Terminal window on the computer and switch to brick-douglas/amonet. (We are not re-using the same window because we will come back to it.)
6. Run the following: sudo ./brick-9820.sh
7. Type "YES" and Enter to continue.
8. Power down the tablet and wait about 5 seconds.
9. Getting ready to let go of them quickly, power up the tablet into RECOVERY mode by holding down the power and volume downbuttons. AS SOON AS YOU SEE "RECOVERY" IN THE LOWER LEFT OR THE TEXT SCREEN WITH "Amazon system recovery <3e>", LET GO!
   • If you don't let go in time and the tablet reboots, catch it the next time.
   • Note, if you can't get into RECOVERY mode, it often helps to briefly let go of the power button and press it again as soon as you see the Amazon logo.
10. Get into FASTBOOT mode by using the volume buttons to move to "reboot to bootloader" and pressing the power button to select it.
11. The script should continue as soon as the tablet is in FASTBOOT mode. If it doesn't and stays at "< waiting for any device >", press Ctrl+C to terminate the script, then re-run it.
12. The script may pause at "Writing 'brick'...". Watch the tablet and, when it says "All good...", wait a few seconds, unplug the USB cable from the tablet, and power it off by holding down the powerbutton until the screen turns off.
    • Note, the script may say it FAILED. As long as the tablet said "All good...", the script succeeded.
13. Switch back to the other Terminal window, the one in the "amonet-douglas-v1.2/amonet" directory.
    • If you closed it or re-used it for the bricking procedure, switch back to amonet-douglas-v1.2/amonet.
    • You can close the "brick" window or leave it open for now in case we need to use it again.
14. Next, run the following in Terminal: sudo ./bootrom-step.sh
    • DO NOT RUN THE ONE WITH "minimal" IN THE NAME!
15. Plug the USB cable back into the tablet. It should power itself up but you will not be able to tell since the screen will remain black.
    • If the script does not show "* * * Press Enter to continue * * *", you may need to momentarily press the power button.
    • Wait about 15 seconds. If the script still does not show "* * * Press Enter to continue * * *", make sure the USB cable is firmly plugged into the tablet and computer. For best results, use the cable that came with the tablet.
    • Hold down the power button for at least 50 seconds as a last resort! If you STILL cannot get it to work, stop the script with Ctrl+C and restart it. REMEMBER, THE TABLET'S SCREEN SHOULD REMAIN BLACK as the script re-flashes it.
    • You can see if the tablet is connected to the computer by running the following in Terminal: sudo lsusb
      • It should show something like "MediaTek Inc. MT65xx Preloader", "MediaTek Inc. MT6227 phone", "Lab126, Inc. Android", or "Lab126, Inc. Fire". The correct one that it should be in is "MediaTek Inc. MT6227 phone".
    • Worst case scenario, there is a recovery method that should work that involves opening the tablet. See Fire hd8 2017 root, debrick for details.
16. Press Enter in Terminal to continue.
17. The script should end with "Force fastboot", "Flash preloader header", and "Reboot" and the tablet should reboot into HACKED FASTBOOT mode. However, it's difficult to tell SINCE THE SCREEN WILL REMAIN BLACK!
    • If you are sure the tablet did not reboot, try pressing the power button for about 15 seconds, waiting a few seconds, then pressing it again for about 15 seconds. If that doesn't work, repeat the same process but hold the power button down for at least 45 seconds both times.
    • Note, if the tablet is powered up, running "lsusb" in the Terminal window should show one of these: "MediaTek Inc. MT65xx Preloader", "MediaTek Inc. MT6227 phone", "Lab126, Inc. Android", or "Lab126, Inc. Fire".
    • If it powers up to FASTBOOT mode, return to Step 6. Note, if sudo ./brick-9820.sh didn't work properly, you can try sudo ./brick.sh instead. If you do, keep in mind that you should run sudo ./bootrom-step-minimal.sh instead of sudo ./bootrom-step.sh in Step 14.
18. While in HACKED FASTBOOT mode (still a black screen), run the following: sudo ./fastboot-step.sh
19. When the script is done, it will say "Your device will now reboot into TWRP." and the tablet will reboot into TWRP.
20. Once the tablet reboots into TWRP, you are now past Step 4 in the original instructions and can proceed to install Magisk and/or follow the [ROM][UNOFFICIAL][10] LineageOS 17.1 for Amazon Fire HD8 7/6th gen (douglas/giza) thread. Note, if installing the "2023-05-20" build from that thread, before trying to flash OpenGapps, delete the app-sizes.txt file from the ZIP file; otherwise it won't fit. You can also install microG or BitGapps core instead of OpenGapps.

Good luck!

 

[nuclear_bullet]

vjunk, THANK YOU. I was one of many that was probably stuck on that step scratching my head. THANK YOU again, I'm staring at TWRP on my Fire HD 8 Douglas!!!

 

[ApathyImp]

@vjunk thank you soooooo much! this was exactly what we needed to get unstuck. you are a scholar and a gentleperson!~

 

[OctaneZ]

Thank you @vjunk for updating the guide....

I am running into trouble still. No problem getting into fastboot with `adb reboot bootloader`

but when I run the brick commands I get:

sudo ./brick-9820.sh
Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)
YES
Bricking PL Header
Check instructions on device


< waiting for any device >
Sending sparse 'brick' 1/1 (12 KB)                 OKAY [  0.018s]
Writing 'brick'                                    FAILED (remote: 'the command you input is restricted on locked hw')
fastboot: error: Command failed

But whether I reboot into recover or using ADB I can't get past this "restricted on locked hw"

any advice?

 

[vjunk]

I haven’t seen the "restricted on locked hw" message before. Then again, I’ve only unlocked two Fire HD 8 tablets so far. A few things to double-check:

• The tablet is the Fire HD 8, 7th gen/2017 version, code name douglas.
• You are using amonet-douglas-v1.2.zip, not the 1.0 or 1.1 version.
• The Fire OS version is newer than 5.6.4.0. (I believe mine were 5.7.0.0.)
  • If it’s 5.6.4.0 or older, follow the original procedure in the first post since there is no need to temporarily brick the device.
  • Note, if Amazon released a new version in the past few months, they may have patched the flaw that allows bricking the tablet with this method. If so, there may not be a way around it without opening up the tablet.
• mtk-su was copied from the arm64 directory to the brick-douglas/amonet/bin directory.

If all of the above is correct, the only thing I can think of is trying sudo ./brick.sh instead of sudo ./brick-9820.sh. If you do, run sudo ./bootrom-step-minimal.sh instead of sudo ./bootrom-step.sh in Step 14.

If that doesn’t work, perhaps @k4y0z can provide some advice. If not, @Rortiz2 knows these devices very well and may have an idea (although his expertise is more in building the ROMs for these).

Good luck!

 

[SynPolka]

Is it method still work on fire os 5.7.1.0?

 

[ApathyImp]

Is it method still work on fire os 5.7.1.0?

i was able to do it on 5.3.7.0, which is considerably older and i had to use the modified instructions @vjunk provided in the more recent replies on this board.

realistically the only way to know for sure is to try it and see what happens, but that does run the risk of potentially permanently bricking your device so i would suggest you only do so if you’re experienced, knowledgeable, and fully accept that risk of losing the device completely if things go wrong.

if i were to make an educated guess though, i would say it is increasingly less likely to work with each newer update from amazon as this is the kind of thing that security patches tend to target. so it might not be worth the hassle, but that is something you will have to decide for yourself.

 

[SynPolka]

i was able to do it on 5.3.7.0, which is considerably older and i had to use the modified instructions @vjunk provided in the more recent replies on this board.

realistically the only way to know for sure is to try it and see what happens, but that does run the risk of potentially permanently bricking your device so i would suggest you only do so if you’re experienced, knowledgeable, and fully accept that risk of losing the device completely if things go wrong.

if i were to make an educated guess though, i would say it is increasingly less likely to work with each newer update from amazon as this is the kind of thing that security patches tend to target. so it might not be worth the hassle, but that is something you will have to decide for yourself.

Thank for your reply ,Apathylmp,and I will try vjunk´s method as soon as I can get an Ubuntu PC.

And in addition,I don't know how my fire could get update from 5.6.4.0 to 5.7.1.0 when the most of amazon device services are unavailable in China.

 

[SynPolka]

i was able to do it on 5.3.7.0, which is considerably older and i had to use the modified instructions @vjunk provided in the more recent replies on this board.

realistically the only way to know for sure is to try it and see what happens, but that does run the risk of potentially permanently bricking your device so i would suggest you only do so if you’re experienced, knowledgeable, and fully accept that risk of losing the device completely if things go wrong.

if i were to make an educated guess though, i would say it is increasingly less likely to work with each newer update from amazon as this is the kind of thing that security patches tend to target. so it might not be worth the hassle, but that is something you will have to decide for yourself.

OK,and I have already tried @vjunk 's method,and the method still work on fire os 5.7.1.0.Thans for everybody's help.

 

[ApathyImp]

OK,and I have already tried @vjunk 's method,and the method still work on fire os 5.7.1.0.Thans for everybody's help.View attachment 6013571View attachment 6013573View attachment 6013575

nice! thanks for updating everyone, good to know it’s still working on [more] current versions.