[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 10 2017 (suez)

Korin67

Senior Member
Feb 24, 2018
157
84
28
Should I run brick.sh, then bootrom-minimal.sh?

I'm a little lost as I thought if it tested for > 5.6.3 and failed it would ask for
permission to do the brick and then continue the script? Instead it continues without
asking and then fails with 'critical init step 4' error message.

It appears to have pushed the 3 three files to the tablet successfully, using mtk-su.

Fuz
Unfortunately, brick.sh does not work. bootrom-minimal.sh only works if your tablet is bricked. That means you first have to brick your tablet. To brick your tablet without using brick.sh (now it is useless), you need to root your tablet first. Article #1321 (the original article it refers) gives you the clue.
 

Robi2003

Member
Mar 30, 2020
7
0
1
3D
sudo ./bootrom-step-minimal.sh
re-connecting to usb cable
At this point i had to hold the power button for 20 seconds. and a message came up asking me to press enter after removng the short (no short was applied, so just press enter)
anther message came up asking if i had bricked the device, press enter. at this point it began injecting the payload.
I cannot make this step, I get this error:

Bildschirmfoto von 2021-02-17 12-53-56.png
 

fuzzynco

Senior Member
Oct 29, 2008
581
32
48
Unfortunately, brick.sh does not work. bootrom-minimal.sh only works if your tablet is bricked. That means you first have to brick your tablet. To brick your tablet without using brick.sh (now it is useless), you need to root your tablet first. Article #1321 (the original article it refers) gives you the clue.
The tablet is as it came from Amazon with Fire OS 5.6.4.0. mtk-su does still work.
Which version (fire os) was brick.sh written for?

Fuz
 

Korin67

Senior Member
Feb 24, 2018
157
84
28
I have no idea. I also tried with OS 5.6.4.0. When I tried brick.sh, the tablet just rebooted to FireOS as if nothing applied. It could not bring the tablet into brick.
 

pokemon81

New member
Jun 10, 2008
3
0
21
Hi,

i try to Root my Device for Lineage ROM. But it don't Work. i see Waintig Devices an nothing more. I need to Brick the Device because it was with latest fire OS 5 installed. here i my Console output:

Code:
[email protected]:~/amonet# sudo ./bootrom-step-minimal.sh
[2021-02-19 12:38:09.667910] Waiting for bootrom
[2021-02-19 12:38:15.504746] Found port = /dev/ttyACM0
[2021-02-19 12:38:15.507227] Handshake
[2021-02-19 12:38:15.512809] Disable watchdog

* * * Remove the short and press Enter * * *


[2021-02-19 12:38:27.277045] Init crypto engine
[2021-02-19 12:38:27.513155] Disable caches
[2021-02-19 12:38:27.516118] Disable bootrom range checks
[2021-02-19 12:38:27.638276] Load payload from ../brom-payload/build/payload.bin = 0x4820 bytes
[2021-02-19 12:38:27.676080] Send payload
[2021-02-19 12:38:34.028390] Let's rock
[2021-02-19 12:38:34.033964] Wait for the payload to come online...
[2021-02-19 12:38:34.037863] all good
[2021-02-19 12:38:34.039129] Running in minimal mode, assuming LK and TZ to have already been flash                                      ed.
[2021-02-19 12:38:34.039793] If this is correct (i.e. you used "brick" option in step 1) press ente                                      r, otherwise terminate with Ctrl+C

[2021-02-19 12:38:37.069439] Check GPT
[2021-02-19 12:38:41.743851]
[2021-02-19 12:38:41.744626] Sector size (logical): 512 bytes
[2021-02-19 12:38:41.745299] Disk identifier (GUID): B1541C10-343E-474B-B5B2-05796C64E992
[2021-02-19 12:38:41.745781] Partition table holds up to 128 entries
[2021-02-19 12:38:41.746218] This partition table begins at sector 2 and ends at sector 33
[2021-02-19 12:38:41.746638] First usable sector is 34, last usable sector is 61071326
[2021-02-19 12:38:41.747038] Other partition table is at sector 61071359
[2021-02-19 12:38:41.747428]
[2021-02-19 12:38:41.748086] Number   Start (sector)     End (sector)  Size          Name                                              
[2021-02-19 12:38:41.752948]     1             1024             7167  3.00 MiB      proinfo                                            
[2021-02-19 12:38:41.756000]     2             7168            16383  4.50 MiB      PMT                                                
[2021-02-19 12:38:41.758094]     3            16384            18431  1024.00 KiB   kb                                                  
[2021-02-19 12:38:41.760166]     4            18432            20479  1024.00 KiB   dkb                                                
[2021-02-19 12:38:41.762282]     5            20480            22527  1024.00 KiB   lk                                                  
[2021-02-19 12:38:41.764337]     6            22528            32767  5.00 MiB      tee1                                                
[2021-02-19 12:38:41.766409]     7            32768            43007  5.00 MiB      tee2                                                
[2021-02-19 12:38:41.768551]     8            43008           123903  39.50 MiB     metadata                                            
[2021-02-19 12:38:41.770634]     9           123904           124927  512.00 KiB    MISC                                                
[2021-02-19 12:38:41.772770]    10           124928           141311  8.00 MiB      reserved                                            
[2021-02-19 12:38:41.774977]    11           141312           174079  16.00 MiB     boot_x                                              
[2021-02-19 12:38:41.777100]    12           174080           208895  17.00 MiB     recovery_x                                          
[2021-02-19 12:38:41.779190]    13           208896          3515391  1.58 GiB      system                                              
[2021-02-19 12:38:41.781278]    14          3515392          4383743  424.00 MiB    cache                                              
[2021-02-19 12:38:41.783400]    15          4383744         60619775  26.82 GiB     userdata                                            
[2021-02-19 12:38:41.785539]    16         60619776         60845055  110.00 MiB    boot                                                
[2021-02-19 12:38:41.787567]    17         60845056         61070335  110.00 MiB    recovery                                            
[2021-02-19 12:38:41.897324]
[2021-02-19 12:38:41.898619] Check boot0
[2021-02-19 12:38:43.421270] Check rpmb
[2021-02-19 12:38:43.633027] rpmb looks broken; if this is expected (i.e. you're retrying the explo                                      it) press enter, otherwise terminate with Ctrl+C

[2021-02-19 12:38:53.911153] Clear preloader header
[8 / 8]
[2021-02-19 12:38:55.578061] Downgrade rpmb
[2021-02-19 12:38:55.582559] Recheck rpmb
[2021-02-19 12:38:56.474786] rpmb downgrade ok
[2021-02-19 12:38:56.475503] Inject payload
[1 / 1]
[807 / 807]
[1 / 1]
[807 / 807]
[2021-02-19 12:39:28.373408] Force fastboot
[2021-02-19 12:39:29.973640] Flash preloader
[361 / 361]
[353 / 353]
[2021-02-19 12:39:44.938608] Reboot to unlocked fastboot
[email protected]:~/amonet# sudo ./fastboot-step.sh
Your device will be reset to factory defaults...
Press Enter to Continue...

< waiting for any device >
^C

what are i am Missing ? When i connect the Display of teh Device i see an Loop with den "Amazon " Logo. i cannot get into recovery or Fastboot mode.
 

julianfairfax

Senior Member
May 28, 2019
86
10
18
I've been experimenting with the LineageOS 14.1 and 16.0 builds for this device, before that I had LineaegeOS 12.1 working fine, but now I can't get it to boot, and it's not detected by adb either. I've tried almost everything including redoing the whole bootloader unlocking process after restoring back to stock so I don't see what could be causing this. Does anyone have any ideas of how I could get LineaegeOS 12.1 working again? Thanks for your help!

Edit: I attempted to clear the misc partition, which worked, but didn't solve the issue.
Edit 2: I fixed this by wiping the metadata partition.
 
Last edited:

sga999

Senior Member
Mar 13, 2012
808
112
63
That's interesting, I tried Magisk 21.1 but it also left me unable to boot FireOS 5.6.8.0. But I could easily enough revert back to Magisk 20.4 and it booted back up with no problems. I didn't bother trying 21.0 as I assumed it would also fail.

The Magisk Manager update works fine, just Magisk itself doesn't.
I got a notification about a new Magisk version 22.0 today. It is a combined app and zip file. I thought maybe this boot problem would be fixed on our Fire HD 10, but no luck. And yet it looks like this problem was closed out the day after we mentioned it. I wonder why. Has anyone else encountered this issue with the newest version?

As we did before, flashing the older version of the zip works, but it sure would be nice to have the latest version installed.
 

mhardyman

Senior Member
Jul 10, 2007
179
27
58
I got a notification about a new Magisk version 22.0 today. It is a combined app and zip file. I thought maybe this boot problem would be fixed on our Fire HD 10, but no luck. And yet it looks like this problem was closed out the day after we mentioned it. I wonder why. Has anyone else encountered this issue with the newest version?

As we did before, flashing the older version of the zip works, but it sure would be nice to have the latest version installed.

I failed to boot with previous magisk update 21.4. Reverted to 18.1 and boots but can't access root. Installed v22 as an apk this morning and doesn't load. I think mine has got messed up. Is there a link to legacy magisk 20.4. Thanks.
 

sga999

Senior Member
Mar 13, 2012
808
112
63
I failed to boot with previous magisk update 21.4. Reverted to 18.1 and boots but can't access root. Installed v22 as an apk this morning and doesn't load. I think mine has got messed up. Is there a link to legacy magisk 20.4. Thanks.
I'm not very familiar with gitHub, but it looks like all old releases are there. Newer ones are listed first, so you may have to advance to a subsequent page to get the one you want.

 
  • Like
Reactions: mhardyman