yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] DrummerDanTX:
It worked!

I was on 5.4.0.0 (2017)

Tried step1 and got different results from

“the last partition is not userdata, refusing modification”

to getting stuck at “Testing Root access"

and another error I cant remember what it was

I reset to factory defaults at the Amazon recovery screen (from a power off state, hold vol down and power). Recovery or Reset system to factory defaults will be an option there. Make sure you leave Wifi OFF and do not connect to any networks when the recovery is complete.

After that I learned the script (step-1, etc) may not run and do it’s things when you’re in a completely booted mode. I tried activating the script shortly after the Amazon logo comes up after an initial power on, and then the magic started happening. Ran script1, then rebooted FireHD and ran script2 successfully. Couldn’t believe I was seeing TWRP on the device.

Was able to load Lineage 12 and so far so good.

HUGE THANK YOUS TO [MENTION=7104332]k4y0z[/MENTION], [MENTION=9667509]xyz`[/MENTION] [MENTION=8132642]diplomatic[/MENTION] [MENTION=9325417]t0x1cSH[/MENTION] and [MENTION=10103172]breakfastofsecrets[/MENTION]

EDIT : adding more info

A bit more info.

I installed OpenGapps pico and at first Play Store crashed. I had to force stop and try a few times until it would let me login.

App installs have been consistently successful, but yes I see as others have reported the delay when picking an app to install with the 'waiting to download' message. I just waited a few min and eventually the apps downloaded and installed.

Also I have another HD8 that is at 5.6.1.0 and both scripts are failing. Going to attempt to downgrade it.
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
you enable usb debug or not ( Enable ADB in Developer Settings )?
[Fire HD 8 and HD 10 Original Android Development] NTGDeveloper:
Awesome! This will definitely be useful. Do you happen to know if any ROMs are in development yet? That would be awesome if that would happen.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Not currently planned, I don't have that device, also not sure it it will be useful for that many people.

You'll have to give some more info, what exactly and how did you create the backup and what exactly are you trying to restore?

Did you enable ADB? What does

sudo adb devices

say?
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
You need to check the device screen and click allow USB debugging from this computer
[Fire HD 8 and HD 10 Original Android Development] yafi1710:
after running the command I see there is no devices listed. That means adb is not installed on Linux Shell! I am currently on Windows Linux Shell and my Windows 10 has adb. Do I need to install adb for the linux shell also? How to do that?

---------- Post added at 06:48 AM ---------- Previous post was at 06:39 AM ----------

Nothing on my screen! It seems Windows 10 Linux Shell is not detecting the device thorugh adb!
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
ok i modify my device and i added arabic language to system

i usually backup my system by dd command yesterday i see this method and flash twrp and i make back up for my system.

But when try to restore by twrp to my device or another ( same model ) the device stuck on amazon logo i try flash boot_x and recovery_x nothing happen but when i use dd command to restore every thing go ok

Please help my
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
Try this commands

sudo apt update

sudo apt-get install android-tools-adb android-tools-fastboot
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Just did some tests and it looks like backing up/restoring system this way somehow messes with selinux.

I will add the option to backup system as image in the next release.

I don't think WSL supports USB.

Wasn't your device already unlocked? Why did you run the bootrom-script?

Anyway it looks like somehow your GPT got messed up:

Do you have the 16GB or the 32GB version?

Do you still have the "gpt"-folder from running the initial unlock?

If so please attach it.
[Fire HD 8 and HD 10 Original Android Development] Oco:
One Fire 8 HD 2016 user here, that´s sad because this model lacks of Show Mode then trying to get it back to Android stock would be great.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
[MENTION=7104332]k4y0z[/MENTION] if you flashed amonet and then a clean flash to FireOS it will birck the device. (happened to t0x1cSH).
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Flashed how? What version? [MENTION=9325417]t0x1cSH[/MENTION] ?

I haven't had any issues flashing stock from TWRP.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
We were doing some tests (CM12.1) (it was booting to bootanimation) and reverted back to FireOS. That's OK FireOS was working but when tried to flash again our system & boot the tablet refused to set SELinux to permissive and always was at enforcing. He checked kernel cmdline and as expected is enforce. IDK if it has been that but seems that FireOS corrupted it. Also he has a rare partition (I think because he tested the pre-amonet version:

_y_s_4Z___ -> /dev/block/mmcblk0p1

So flashed amonet tought TWRP and bricked.

Well now he is AFK so it will not response till tonight. He is going to use his method for unbrick it and flash again this amonet.

Regards.
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
I have fire hd8 2017 32 GB i use bootrom script because i can not boot to twrp recovery or stock recovery just i get amazon logo.

And i am not undestand what you mean ( do you still have the gpt - folder from running initial unlock )
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
How are you setting selinux to permissive?

If your boot.img boots than amonet is working fine.

mmcblk0p1 should be proinfo, so that definitely doesn't look right.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
The boot was booting before. As all boot.img it has permissive in the cmdline:

https://github.com/CM12-1-Douglas/android_device_amazon_douglas/blob/cm-12.1/BoardConfig.mk#L52

And yeah I tought that partition was not good lol.

Well let's see what he does.

Regards!
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Are you sure it's 32GB?

Because the partition-table looks like a mix between 32 and 16GB.

And the fact that it fails writing to the boot also seems to indicate it is 16GB.

My guess was that you have two devices (one with 32 and one with 16) and unlocked the 16 after the 32.

So the GPT of the 32GB ended up on the 16GB somehow and the system tried correcting it.

I mean after you ran the step-1.sh it creates a folder "amonet/gpt" please zip that folder and attach it.

If anyone else with 16GB version could please dump their GPT that would be helpfull as well:

dd if=/dev/block/mmcblk0 bs=512 count=34 of=/sdcard/gpt.bin
adb pull /sdcard/gpt.bin
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
I thing you are right i use this method first time on 32GB and make backup ( twrp backup ) from it and then i use this backup on 16GB also i thing i use step-2 instead of step-1 ( i confused)

Ok when i go to home i will search for this folder and attach

Thank you too much my friend
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
i attache my gpt but i do not know this for 32 or 16 GB
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
The gpt.bin is from the 16GB-device the step1 and step2 GPT are from the 32G device.

So it happened exactly what I thought, you first did the 32G-unlock and then the 16G.

And it used the existing step1 and step2 from the 32G on the 16G.

The system then tried to fix it but that didn't work properly, because it expected userdata to be the last partition.

I'll update amonet, so this can't happen again and will also upload a gpt-fix later so you can fix your device.
[Fire HD 8 and HD 10 Original Android Development] Colossus96:
Why can't I install xposed? Any insight?

Fixed:

Needed to install arm version.
[Fire HD 8 and HD 10 Original Android Development] Fire_HD:
Hi Guys,

i tried a lot of things to get root on my device running 5.6.4.0 (636559820) but nothing worked. can i leave this step (sudo ./step-1.sh) and go straight to sudo ./fastboot-step.sh after using brick(-9820).sh?

or is there another option like shortn the tablet like it works on fire hd7 or the 8th gen?

can i use this methode - https://xdaforums.com/showpost.php?p=80287339&postcount=154 ?

thx!
[Fire HD 8 and HD 10 Original Android Development] Colossus96:
how can i go back to stock when i don't have the original amonet 1.1.zip file.. after unlocking & installing twrp i deleted that folder.
[Fire HD 8 and HD 10 Original Android Development] Colossus96:
Hi, I have a weird problem i hope someone can help me. I installed fire os 6.4.0.1 with twrp. It runs great and all but it doesn't charge,(original charger). But if i flash lineage or slimlp it charges okay with the same charger. Can someone help me? i don't want to install the current build of Lineage or SlimLP as both of them lag after a while.

NVM.. It was my cable's fault. Changed the cable and now it's working correctly.
[Fire HD 8 and HD 10 Original Android Development] Fire_HD:
I opened the tablet and used this method https://xdaforums.com/showpost.php?p=80287339&postcount=154
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
You need to run bootrom-step.sh after brick-9820.sh (as the script would tell you)

Why would you need the original amonet-v1.1 zip file? (Also it's still available for download)
[Fire HD 8 and HD 10 Original Android Development] Kingwalk1987:
It seems nobody knows the answer to our 5.3.7.0 question. Please help. Is there any method that works, hardware or software, on this latest update?
[Fire HD 8 and HD 10 Original Android Development] Airton araujo:
I was on 5.3.7.0 (650601220)

now i'm experiencing slim lp :)

here what I did: I created a folder and extracted zip amonet v 1.2 there

then I extracted zip brick-douglas in this same folder

I opened the terminal in that folder (following post from dl360 and mazzystr)

run

1 sudo adb reboot bootloader

once the tablet has restarted in the bootloader:

2 sudo ./brick-9820.sh

disconnect the cable

turn it off by pressing volume down and power

at this point the device will die until the next step is applied:

3 sudo ./bootrom-step.sh

reconnect the device. it will be found. press enter

(unfortunately my laptop battery ran out during this process and turned off so I couldn't save the log. so I had to restart this 3 step and I forgot if it was in that part before the laptop shut down if I was asked if I wanted to disable or uninstall "modemmanager" in the terminal. if so the command was:

"sudo systemctl disable ModemManager" or just "YES" I don't remember XD ...

the files started to load and my heart was filled with hope .. but this happened:

"... [8/8]

[2020-01-22 21: 51: 05.312384] Downgrade rpmb

[2020-01-22 21: 51: 05.314334] Recheck rpmb

[2020-01-22 21: 51: 06.209086] rpmb downgrade ok

[2020-01-22 21: 51: 06.209985] Flash preloader

Traceback (most recent call last):

**Main.py file, line 256, in <module>

****main ()

**Main.py file, line 214, in main

****flash_binary (dev, "../bin/preloader.bin", 8)

**Main.py file, line 53, in flash_binary

****with open (path, "rb") as fin:

FileNotFoundError: [Errno 2] No such file or directory: '../bin/preloader.bin'

airton @ airton-I38II: ~ / Desktop / amonet $ ... "

as you can see i had trouble flashing preloader.bin even though it was in the bin folder

to solve this I just changed the file in amonet / modules / main.py with the main.py file from zip amonet v1.1 once the first one came from v1.2 ...

again I redone step 3 and this time it worked !!!!

so I was able to apply the next step:

*

4 sudo ./fastboot-step.sh

finished

the device restarted on the twrp interface

:) :) :)

I was also having problems with "waitin for any device" and it was only solved by putting" sudo ./ "on each command line

also make sure that python and fastboot are up to date

done. thank you all so much for your efforts to free us from the amazom stock!

let's consider learning how to buy coffee or beer for these people, right?

I'm runing Ubuntu 18.04

Some screenshots drive.google.com/folderview?id=1-CMjMJy4RY9-WtJfAW2dSFHGJFhQxcmh

Let me try it on my sister's Karnak now
[Fire HD 8 and HD 10 Original Android Development] Kingwalk1987:
We're you already rooted?
[Fire HD 8 and HD 10 Original Android Development] Airton araujo:
No. I,m not. Root after on twrp
[Fire HD 8 and HD 10 Original Android Development] chennaiite:
Help - Recovery missing "Apply ADB update"

I'm surprised I can't find anything on Google or XDA about this. My Fire HD 8 - 7th Gen Douglas - does NOT show any option to apply updates via ADB in recovery mode. I have enabled ADB in developer settings. Below is what my recovery looks like.

Amazon system recover <3e>

reboot system now

wipe data/FR

wipe cache partition

reboot to bootloader

power down

view recovery logs​

Can anyone tell me what am I doing wrong? I need update via ADB option to sideload a higher verion of stock rom so this root/unlock method can work. My current version is 5.3.7.0 (650601220). And I need to update the ROM to 5.6.XX for the root to work.

Thanks in advance
[Fire HD 8 and HD 10 Original Android Development] Kingwalk1987:
You are on the latest firmware. "I know it's confusing" but 5.3.7.0 came after 5.6.4.0. Apparently you can still do the process but some of us are getting an error because the mtk-su file does not seem to be supported on the latest firmware.

---------- Post added at 03:33 PM ---------- Previous post was at 03:31 PM ----------

Ok and did you place the mtk-su file in amonet\bin or did you skip that part entirely? That is where we are having trouble. It is giving us "platform not supported"
[Fire HD 8 and HD 10 Original Android Development] jonathanmoneill:
Sorry if this seems a n00b response but....

Hi all,

I attempted the software method last night with my Fire HD8 2017. I had previously rooted the device and installed SuperSu. When I tried this last night using a linux mint live usb, I opened the terminal window in the amonet directory but the script hangs at the first stage (sudo ./step-1.sh). The terminal outputs "Testing Root Access" and just stops there. As (a slightly relevant) aside, I'm not sure what version of the firmware I'm currently running or how to find that out(disabled OTA a while ago). I'd really like to be able to use a custom ROM on this device so any advice on how to get to that point would be greatly appreciated.

Thanks,
[Fire HD 8 and HD 10 Original Android Development] winstonma:
I resetted my HD8 and I got the following error while running ./bootrom-step.sh:

RuntimeError: ERROR: Serial protocol mismatch

I am not sure if my tablet could use this tool so may I ask this question

I am using Amazon Fire HD8 (w/o any HW mod) with the firmware 5.3.7.0. So is it possible for the tablet to enter the TWRP? Thanks a lot
[Fire HD 8 and HD 10 Original Android Development] comegalletas:
I got the same error twice, I has not doing the TP28 with ground properly.... after 3 tries I managed to run it; however I broke the digitizer and a soldered cable on the motherboard, so be very careful.

---------- Post added at 10:19 PM ---------- Previous post was at 09:47 PM ----------

So... as I said in the previous anwser, I just broke the digitizer and a couple of cables an now my Fire don´t show anything on the screen. (still shows if connected to PC).

This is a picture of what I broke:

https://imggmi.com/full/2020/2/3/1cfb7517567e22550dab4feddcc64b69-full.png.html

Do anyone know where I can get the spare part?
[Fire HD 8 and HD 10 Original Android Development] speedrcr:
You can try to get back to the bootloader and run brick.sh again to restart the process. In the worst case, you can reset to factory and start from scratch again. No need to open the case even at version 5.3.7.0 (I just succeeded yesterday with my stock HD8-2017 yesterday)... the steps provided by Airton araujo will work (although you may need to use "brick.sh" instead of "brick-9820.sh"). Make sure you have updated everything from the required repos (python3 python3-serial adb fastboot dos2unix) and killed ModemManager to avoid problems later.
[Fire HD 8 and HD 10 Original Android Development] pechex:
Thanks! I did this steps to the letter and it worked. Only exception is that I didn't needed to copy the file from 1.1.

How do you root from TWRP? What root to download?

Instaling LineageOS now. thanks!!
[Fire HD 8 and HD 10 Original Android Development] speedrcr:
You're already rooted if you installed Lineage. You can install Magisk on top of that by using TWRP and doing ADB sideload (via Advanced menu and using the adb command line utility).
[Fire HD 8 and HD 10 Original Android Development] winstonma:
Thanks for this. I followed the steps and installed LOS

Thanks again
[Fire HD 8 and HD 10 Original Android Development] Kingwalk1987:
Exactly

You have hit the nail on the head with this. I am so scared to try this any further because it just seems like nobody knows how to do this without there being some sort of error. As badly as I want to I just can't. It will be my luck that another update comes before we get a clear cut answer. lol!
[Fire HD 8 and HD 10 Original Android Development] sidjones1:
Thought I would try...

Thought I would give this a shot. Not too much experience here.

Followed these steps mentioned below:

"I was on 5.3.7.0 (650601220)

now i'm experiencing slim lp

here what I did: I created a folder and extracted zip amonet v 1.2 there

then I extracted zip brick-douglas in this same folder

I opened the terminal in that folder (following post from dl360 and mazzystr)

run

1 sudo adb reboot bootloader

once the tablet has restarted in the bootloader:

2 sudo ./brick-9820.sh

disconnect the cable

turn it off by pressing volume down and power

at this point the device will die until the next step is applied:

3 sudo ./bootrom-step.sh

reconnect the device. it will be found. press enter"

Results:

sid@sid-Inspiron-11-3147:~/Downloads/Kindle8$ sudo ./bootrom-step.sh

[2020-02-04 15:39:08.586254] Waiting for bootrom

[2020-02-04 15:39:20.311452] Found port = /dev/ttyACM0

[2020-02-04 15:39:20.350417] Handshake

* * * If you have a short attached, remove it now * * *

* * * Press Enter to continue * * *

b''

b'\x00\x01'

Traceback (most recent call last):

File "main.py", line 256, in <module>

main()

File "main.py", line 129, in main

load_payload(dev, "../brom-payload/build/payload.bin")

File "/home/sid/Downloads/Kindle8/modules/load_payload.py", line 123, in load_payload

dev.write32(0x10007008, 0x1971) # low-level watchdog kick

File "/home/sid/Downloads/Kindle8/modules/common.py", line 163, in write32

self.check(self.dev.read(2), b'\x00\x01') # arg check

File "/home/sid/Downloads/Kindle8/modules/common.py", line 90, in check

raise RuntimeError("ERROR: Serial protocol mismatch")

RuntimeError: ERROR: Serial protocol mismatch

sid@sid-Inspiron-11-3147:~/Downloads/Kindle8$

As you can see, I had issues with a mismatch with file common.py. I even tried to use Amonet V1.1 common.py file. At least I didn't brick anything. It booted normally. I think I am better to wait until someone much smarter figures this out...lol BTW, am running Unbuntu 19.10, have a Kindle 8 2017 version 5.3.7.0 . I sure hope this get's figured out. It would be nice to have a more pure operating system on this :):good:
[Fire HD 8 and HD 10 Original Android Development] Airton araujo:
I'm glad you made it

I just flashed the magisk with the rom and gapps

well I preferred to use a full linux installation (ubuntu 18.04LTS) on a partition to not have connection problems and mismatched drivers

I really shot in the dark. I wouldn't even care if the device died

I just decided to share what worked for me.

it's true, the information is a bit confusing (at least for me, someone who doesn't understand english and uses the translator)

but I recommend that you proceed with caution

(I also don't want to be responsible for a world war 3 or anything :) )

---------- Post added at 03:37 AM ---------- Previous post was at 03:10 AM ----------

Yes, I extracted files from mtk-su there, but I don't think it makes any difference.

I don't remember seeing them at the terminal lines...

---------- Post added at 03:47 AM ---------- Previous post was at 03:37 AM ----------

such a messages never appeared to me: "platform cannot be supported or failed critical init step 4"

only: "no devices found" or "waiting for any device" until I used "sudo ./"
[Fire HD 8 and HD 10 Original Android Development] DrUnkeN_TiGeR:
So i installed Ubuntu on a virtual box on windows 10. I run the first 3 commands no problem. when i run sudo ./step-1.sh it asks for password i enter it then it just sits there and does nothing. at....all....
[Fire HD 8 and HD 10 Original Android Development] DB126:
Related post: https://xdaforums.com/hd8-hd10/orig...oftware-root-hd-8-hd-10-t3904595/post81744775
[Fire HD 8 and HD 10 Original Android Development] DrUnkeN_TiGeR:
so why is your fire hd 8 2017 on fire os 5.3.7.0 (650601220) working and mine wont that doesnt make any sense. i have to be doing something wrong
[Fire HD 8 and HD 10 Original Android Development] DrUnkeN_TiGeR:
so i am following this tut and i am in fast boot and i have android with an exclamation point. i have looked everywhere for the drivers i have done 15 min install i have tried downloading just the android drivers, i have removed and replugged in to let it try to auto install it says installing then it says its installed but it still shows exclamation point. i cant do anything in fast boot the device isnt seen. any help would be appreciated
[Fire HD 8 and HD 10 Original Android Development] diplomatic:
You just need to select the driver to install manually. Go to Update Driver for the device, browse for driver software, then "Universal Serial Bus devices", WinUsb Device, ADB Device. The same applies to both ADB and fastboot devices. No need to download any ADB or fastboot drivers, which are just inf files, ever.
[Fire HD 8 and HD 10 Original Android Development] PaperLawyer:
I have two HD8 tablets (well, they are my young daughters' tablets that I'm potentially bricking!) so I will try to replicate my eventual success with the first tablet last night with the second tablet this evening. For me, I wonder whether changing to a much shorter usb cable helped the process as I did keep receiving communication errors with the longer usb cable (connected through a usb hub). Alternatively, it may have simply been persistence with the power cycling.

I used a USB stick running a live version of Ubuntu as the OS and made a right shambles of getting amonet and the brick scripts onto it - hopefully it will be a much smoother process this evening with the second tablet...
[Fire HD 8 and HD 10 Original Android Development] DB126:
Avoid (usb) hubs; they make a mess of low level communications. Cable quality matter; length is secondary unless you're wrapping the house. :)
[Fire HD 8 and HD 10 Original Android Development] PaperLawyer:
For the greater good of others who may make the same error as me, here's my silly mistake....

Just managed to unlock tablet no.2 but had usual "serial mismatch" messages as others have suffered. I eventually managed to get the tablet to reboot and it was if it wasn't bricked. .... realised my error - when the bricking script asks you to confirm YES, it is case sensitive. Otherwise nothing happens.

So I ran the bricking script (the one with 9820 suffix) properly and managed to follow the rest of Airton's process easily - job done!
[Fire HD 8 and HD 10 Original Android Development] DrUnkeN_TiGeR:
no go tried both adb driver and and winusb device

i correct myself it did work i had to add the usb device in settings in my virtual machine with every step, i am booted into twrp now
[Fire HD 8 and HD 10 Original Android Development] ShmilyGone:
Anyone tried this method with Fire HD 8 6th (2016) gen? Does it work?