yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
I think that you can use brick.sh if you are in latest FW, but I'm not sure.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Unlocking devices on build 9820 would be using brick-9820.sh via fastboot and then bootrom-step.sh + fastboot-step.sh
[Fire HD 8 and HD 10 Original Android Development] Cobraroja:
Should I power on the tablet? I have tried but it's stuck in waiting for device (fastboot-step.sh) and keeps restarting (Amazon logo).
[Fire HD 8 and HD 10 Original Android Development] Supersonic27543:
Thank you for confirming!
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I have just uploaded version 1.2, please try that.
[Fire HD 8 and HD 10 Original Android Development] Cobraroja:
Now it boots correctly into hacked fastboot, however it's still waiting for device when executed fastboot-step.sh (fastboot devices shows nothing)
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Make sure to run fastboot-step.sh using sudo.
[Fire HD 8 and HD 10 Original Android Development] Cobraroja:
it's running under sudo.

~ sudo ./fastboot-step.sh

Your device will be reset to factory defaults...

Press Enter to Continue...

< waiting for device >
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Then try updating your fastboot or use a different PC.

You can try using this ISO, it has everything you need:

https://github.com/amonet-kamakiri/fireiso/releases
[Fire HD 8 and HD 10 Original Android Development] Cobraroja:
Can't believe the problem was in my fastboot executable, I got it from apt... Anyway, it's working now, thank you very much for your help, really appreciate it.
[Fire HD 8 and HD 10 Original Android Development] alivan:
That's logically, but what if it is not charging anymore? Is there a way to force it run fastboot step?. Thanks.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Why do you care so much if the message says "Reboot" or "Reboot to unlocked fastboot"?

That is just some debugging information and not relevant to what is actually happening.

It will reboot to fastboot in either case.

Don't mix up the scripts and use the current version.

As I've said a few posts earlier, update your fastboot or use the fireiso:

https://github.com/amonet-kamakiri/fireiso/releases
[Fire HD 8 and HD 10 Original Android Development] dontpanic-xda:
Thanks!

I just used this on my HD8 with build 9820, and successfully installed TWRP!
[Fire HD 8 and HD 10 Original Android Development] PlaidStallion:
I agree. I have been looking through the thread on and off for the past day or so and I am still not really sure if I can perform the root process on 9820 (stock untouched never been rooted) without opening the tablet. I would really love a detailed writeup on how to root the 9820 image. The only thing I see is "brick-9820.sh via fastboot and then bootrom-step.sh + fastboot-step.sh".

---------- Post added at 11:17 PM ---------- Previous post was at 11:04 PM ----------

Does it require you to open the tablet and perform a short or is all done through software still?
[Fire HD 8 and HD 10 Original Android Development] Korin67:
You do NOT need to open the tablet. I opened the tablet, tried the HW method (I did not know that brick-9820.sh exits at that moment) , failed then close my tablet. Yes, my tablet was 'untouched' from the original because the HW method did not change at all in my case. Then I ran brick-9820.sh, and other two shells as well. I succeeded. Actually, I have two douglas's. For the second douglas, I used brick-9820.sh without opening the tablet from the beginning.

Repeat, you do NOT need to open it. Good luck.

Edit: A simple description w/o opening the tablet.

First, under FireOS you need to set USB debug on. Then connect your tablet to PC (that includes adb, fastboot etc.) Check with 'adb devices' to see your tablet is listed as an adb device.

If you are ready, in PC, type 'adb reboot bootloader'. Wait until your tablet is recognized as a fastboot device. Check with 'fastboot devices' (or under Linux sudo adb devices). You should see your tablet is now listed as fastboot devices. Then run sudo ./brick-9820.sh. After a while you will see on tablet screen saying that you should power off the tablet and unplug the usb-cable. Then WITHOUT try to power on your tablet (your tablet is now bricked), in PC

run sudo ./bootrom-step.sh. Then plug USB-cable to your bricked tablet. You will see on PC screen quite a lot of messages and after a while your tablet will boot in bootloader unlocked state. Finally, in PC run sudo ./fastboot-step.sh. You will see TWRP screen on your tablet. All done, you can backup FireOS, install LOS12.1 etc. whatever you like.

Do NOT open your tablet.

Edit2: (or under Linux sudo adb devices) is incorrect, it should be 'sudo fastboot devices'. Sorry for the inconvenience.
[Fire HD 8 and HD 10 Original Android Development] PlaidStallion:
So is this really all there is to the process? Just run the brick-9820.sh and then bootrom-step.sh + fastboot-step.sh. No steps before that? What steps after that? Pick up in the original tutorial somewhere?

Thanks for your response.

---------- Post added 21st October 2019 at 12:17 AM ---------- Previous post was 20th October 2019 at 11:38 PM ----------

From brick-9820.sh:

".....

echo "Then continue with bootrom-step-minimal.sh"

fi

brick-9820.sh (END)

"

---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------

Thank you thank you thank you. I will try this when I get home. At any point do I need to use the commands from the original tutorial?:

"sudo systemctl stop ModemManager

sudo systemctl disable ModemManager"
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Those are all you need to do to get TWRP installed. Regarding the ModemManager matter, I already purged it because I do not need it at all.

Edit: In my description it should be 'under Linux sudo fastboot devices', sudo adb devices is incorrect, sorry.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Not sure, what's going on.

But I did notice, that your GPT doesn't look right.

The last two partitions should be both around 110MiB.

Try running the gpt-fix and see where it gets you.
[Fire HD 8 and HD 10 Original Android Development] lilsphinx90:
well after a lot of headscratching yesterday, it was a broken volume down button that was forcing my device into recovery mode

thanks for the ongoing support for something i ruled out initially, gotta review my troubleshooting steps for next time
[Fire HD 8 and HD 10 Original Android Development] dontpanic-xda:
I did not open my tablet.

The process I used was the same as described by Korin67 in post #272: https://xdaforums.com/showpost.php?p=80610487&postcount=272
[Fire HD 8 and HD 10 Original Android Development] markoajda:
Could you explain this. What do you mean by WITHOUT?

Thanks.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
It simply means NOT try to. Some people (including me) tried to power on the tablet before connect to PC. It is actually not possible because the tablet is already bricked at that moment.
[Fire HD 8 and HD 10 Original Android Development] AmznUser444 Dev:
What is brick-douglas.zip file?
[Fire HD 8 and HD 10 Original Android Development] Supersonic27543:
Just an idea, not sure of technical difficulties: As we could modify the partition table, wouldn't it be technically possible to port Treble to this device?
[Fire HD 8 and HD 10 Original Android Development] Orangedata:
I'm a little uncertain. What does "a while" mean? I've been waiting for half an hour and the console says "Sending 'brick' (111616 KB) ...", but did not crash. The display of the tablet says "USB Transferring ..."

How long should I wait? Any hints? :confused:
[Fire HD 8 and HD 10 Original Android Development] dontpanic-xda:
It might take a short while to transfer across the USB, but you should see progress right away. And you should be seeing console updates as the transfer progresses.

It's possible the script is having trouble finding your device when plugged in.
[Fire HD 8 and HD 10 Original Android Development] Orangedata:
Thanks for your quick reply. I still do not see any progress :(

osboxes@osboxes:~$ sudo fastboot devices
G090XXXXXXXXXXXX	fastboot
osboxes@osboxes:~$ cd Desktop/amonet/
osboxes@osboxes:~/Desktop/amonet$ sudo ./brick-9820.sh
Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)
YES
Bricking PL Header
Check instructions on device

target reported max download size of 114294784 bytes
Sending 'brick' (111616 KB)...

Can I kill this process and restart?
[Fire HD 8 and HD 10 Original Android Development] dontpanic-xda:
Yes.

There's a good chance it's waiting on the device, and not finding it. You may need to start troubleshooting reasons it's not seeing the tablet when you plug it in.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
I am a bit late came back here (due to my timezone). As already be answered 'a while' is quite a short period, might be less than five seconds or so. The message shown on the PC screen is not important. If your tablet says turn off the tablet, unplug the USB cable you are done. Be sure to turn OFF the tablet you need to press the PWR button more than fifteen seconds, nearly 30 seconds.
[Fire HD 8 and HD 10 Original Android Development] max0r4axor:
I keep getting platform not supported errors it pushes the 3 files then errors
[Fire HD 8 and HD 10 Original Android Development] CoolRalph:
is there a way to do this on windows yet?
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
No. Seems that python based scripts are not friendly with windows;)

You can use a Live USB or a VM.

Cheers!

---------- Post added at 06:21 PM ---------- Previous post was at 06:18 PM ----------

Sorry for bump but I could not resist answering xD.

Even if you manage to create the /vendor partition, you still can't boot GSIs. Vendor blobs are not prepared for treble, keep in mind that we are talking about Android 5.1;)

Also I don't think that current binder will be friendly with Android 7.1 and up:)

Cheers!
[Fire HD 8 and HD 10 Original Android Development] galapagos:
The last step seems to be a problem for me.

[root@sysresccd /tmp/amonet]# sudo ./fastboot-step.sh

Your device will be reset to factory defaults...

Press Enter to Continue...

Sending 'recovery_x' (13196 KB) OKAY [ 3.234s]

Writing 'recovery_x' OKAY [ 0.607s]

Finished. Total time: 3.898s

******** Did you mean to fastboot format this ext4 partition?

Erasing 'userdata' OKAY [ 0.132s]

Finished. Total time: 0.145s

fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.

./fastboot-step.sh: line 12: 2895 Aborted (core dumped) fastboot flash MISC bin/boot-recovery.bin

[root@sysresccd /tmp/amonet]#

Can anyone guide me to a solution? If I reboot, I end up with a hacked fastboot mode but twrp is nowhere to be seen
[Fire HD 8 and HD 10 Original Android Development] duck_quack:
This may sound like a noob question but are we supposed to some how update ammo net and if so how?
[Fire HD 8 and HD 10 Original Android Development] LanceLot9980:
You actually can if you have Windows 10. Search around for 'windows bash shell' and follow a tutorial. I unlocked mine with Windows. :)
[Fire HD 8 and HD 10 Original Android Development] dongzanara:
Why do I get an error? Even if we reset the device and try it again. Is there a solut

root@mint:/home/mint/amonet# sudo ./bootrom-step.sh

[2019-10-30 14:23:15.022605] Waiting for bootrom

[2019-10-30 14:23:28.479969] Found port = /dev/ttyACM0

[2019-10-30 14:23:28.513778] 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/mint/amonet/modules/load_payload.py", line 123, in load_payload

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

File "/home/mint/amonet/modules/common.py", line 163, in write32

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

File "/home/mint/amonet/modules/common.py", line 90, in check

raise RuntimeError("ERROR: Serial protocol mismatch")

RuntimeError: ERROR: Serial protocol mismatch

root@mint:/home/mint/amonet#

Why do I get an error? Even if we reset the device and try it again. Is there a solution?
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
What method are you using? Hardware one?

If yes, means that you're not shorting OK. Try again or disconnect the battery.

Cheers!
[Fire HD 8 and HD 10 Original Android Development] dongzanara:
Thank you. I solved it. It's not brick-8920.sh It was executed with brick.sh and processed normally.
[Fire HD 8 and HD 10 Original Android Development] xxxviom:
Hello! FireOS 5.3.6.4 Fire HD 8 2017, Ubuntu on Windows 10 64Bit, everything updated according to instructions... No luck with starting sudo ./step-1.sh... Sometimes it's just silence, sometimes starting ADB and thats all... ADB activated in developers menu, PC connection allowed, I'm in amonet folder in bash... and no luck with script start... Please help.
[Fire HD 8 and HD 10 Original Android Development] LanceLot9980:
Can you send a screenshot of your bash shell window or state what's written there? You need to make sure that the adb version (in adb folder in C Drive) and the adb version of the shell are the same. Do you get something like 'adb server version(x) doesn't match this match this client(y)' when you do 'adb devices' in shell? Version mismatch apparently causes problems here (I had this problem)
[Fire HD 8 and HD 10 Original Android Development] xxxviom:
Hello! And nothing happens after entering password...
[Fire HD 8 and HD 10 Original Android Development] LanceLot9980:
Try doing adb devices after going in shell
[Fire HD 8 and HD 10 Original Android Development] TheLoonyRebel:
Getting failed init step 4 this platform is not supported on my Douglas 2017 device. Using Zorin 15.
[Fire HD 8 and HD 10 Original Android Development] qfreddie:
Hi. How exactly did you fixed this ''adb server version(x) doesn't match this match this client(y)" issue? I am facing the same.

Strange is, that i have two tablets (each for the 2 kids), but i am facing the issue in case of only one, despite using the same laptop for the procedure.

Thanks
[Fire HD 8 and HD 10 Original Android Development] LanceLot9980:
That's weird....for me it fixed after I installed the same adb version as the shell but I don't know how to fix your issue. You can see if adb debugging is on in the tablet causing the issue. If it is, then I can't think of any other solutions, sorry. There are much more experienced people here and you can try asking them.
[Fire HD 8 and HD 10 Original Android Development] qfreddie:
I tried everything but it did not worked. Downloaded an Ubuntu VMWare image, followed tutorial, and all went smooth, with both tablets.

However, i have a small hunch, that one of the tablet was messed up a bit from an earlier root trial that it did not succeeded. Did a factory reset first, and than followed tutorial, and again, smooth.
[Fire HD 8 and HD 10 Original Android Development] LanceLot9980:
That's good. Happy to hear :)
[Fire HD 8 and HD 10 Original Android Development] arrush:
Hello, I found my daughters FireHD8 (2017) she hasn't used it much but it seems enough to be on 5.6.4.0 (-9820).

I've followed the guide and got Ubuntu installed with updates but things stop working on the first step with the sudo ./step-1.sh command. I get the "init step 4' error." which from what I understand is the incompatibility of mtk-su with my version. From what I understand I should be doing the bricking with brick-douglas.zip but when I execute sudo ./brick-9280.sh nothing happens. What state should the tablet be in at this point, on/off/recovery? Assuming this works, I unplug the tablet, run sudo ./bootrom-step.sh and plug it back in; and finally execute sudo ./fastboot-step.sh.

After this to I re-run sudo ./step-1.sh in the hopes that the "init step 4' error." disappears?

Thank you.
[Fire HD 8 and HD 10 Original Android Development] obvious:
I'm confused. Just came to this thread and people are mentioning lineage 12.1 but I thought that only worked on hd10? I have HD 8 2017 Douglas. Which lineage can I install, if any? Thanks!
[Fire HD 8 and HD 10 Original Android Development] dontpanic-xda:
@Rortiz2 has two Douglas ROMs for us to play with.

There's a LineageOS 12.1 ROM for Douglas in this discussion:

https://xdaforums.com/hd8-hd10/orig-development/rom-lineage-12-1-amazon-fire-hd8-2017-t3967537

There also a SlimLP ROM (which I believe is derived from LineageOS 12.1) available in this discussion:

https://xdaforums.com/hd8-hd10/orig-development/rom-slimlp-t3996003
[Fire HD 8 and HD 10 Original Android Development] mikeleachuno:
Can I use bash command line in windows 10

Can I set up a Linux Bash Shell on Windows 10 to do this? I noticed a need for some python3 support for the process. I'm far from any sort of expert but I feel much more comfortable using the command line to input the instructions. If a Bash shell would work for this, would I still follow the instructions in the order you have outlined? Thanks very much!
[Fire HD 8 and HD 10 Original Android Development] obvious:
****, step 3 "sudo ./step-1.sh" runs fine but after factory reset I get a flashing orange screen. Going into settings is possible using the pull down menu but serial number is greyed out and tapping on it seven times does nothing. The tablet is otherwise pretty much unusable as there's no homescreen etc.

This is using WSL. Any ideas? Thanks! Maybe someone could teamviewer into my laptop and take a look? I'm on telegram etc
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
What's your telegram? I can help you.

Cheers.

Enviado desde mi WAS-LX1A mediante Tapatalk
[Fire HD 8 and HD 10 Original Android Development] obvious:
Wow, thanks :) I'm @ tcpaulh
[Fire HD 8 and HD 10 Original Android Development] newfirehduser:
Openining case for 5.6.4.0 build 636558520

Very quick question

Am I right?

5.6.4.0 build 636559820 - one has to open case to unbrick.

5.6.4.0 build 636558520 - one doesn't have to open the case.

EDIT: So I didn't have to open my Fire HD 10 with soft 5.6.4.0 build 636558520 and twrp and everything works: xposed, magisk, and so on
[Fire HD 8 and HD 10 Original Android Development] dontpanic-xda:
I didn't have to open the case on my 9820 build to get TWRP installed. But I think there's a different procedure for the 9820 build than for the builds lower than that.

They say you should be ready to open your case if needed.

It gets confusing with the different procedures. I had to read through the thread several times to get it straight.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Truer words have never been spoken. Read through the thread until familiar with options and fallbacks (recovery methods) if something goes wrong... which it probably will in the first attempt. This stuff isn't hard but it requires attention to detail and a clear head. Other members are quick to help if you have done your homework and run into trouble.

tl;dr - be prepared to open the case.
[Fire HD 8 and HD 10 Original Android Development] dood.:
Hi all,

So I have build 9820 of Fire OS and I did the following.

sudo ./brick-9820.sh

sudo ./bootrom-step.sh

sudo ./fastboot-step.sh

On the last step the first time through I got the status message saying "sending recovery_x" but it seemed to hang on this part of the process so I killed it. I tried again and let it run overnight (which obviously it shouldn't take this long) and it was still stuck at "sending recovery_x". When I run sudo fastboot devices it shows up as:

G090MK07749706AT	fastboot

Can't figure out why it's failing on this last step. I'm connecting to the Kindle via a Ubuntu VM running in virtualbox on my Mac and under Devices -> USB I see it listed as Amazon Android [0100].

Any help is appreciated!
[Fire HD 8 and HD 10 Original Android Development] nujak:
I'd try different USB cables if you have them. Also, try a few different USB 2.0 ports. Someone else might help with alternative solutions. Just report back anything you try and the results.
[Fire HD 8 and HD 10 Original Android Development] arrush:
When you brick using 9820.sh does the tablet have to be on or off?
[Fire HD 8 and HD 10 Original Android Development] rolay07:
Hey (all),

I am also on 5.6.4.0 (636559820) and I am struggling with bricking it:

ubuntu-mate@ubuntu-mate:~/Downloads/amonet$ adb devices
List of devices attached
G090M...(omitted)	device

ubuntu-mate@ubuntu-mate:~/Downloads/amonet$ 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 >
^C
ubuntu-mate@ubuntu-mate:~/Downloads/amonet$

it gets stuck at the waiting for any device. Tried unplugging etc, nothing really seems to help proceed here. (What instructions should I follow on the device? There is nothing on the device.) Same with brick.sh.

If someone had similar issue or aware of the solution I would be grateful. :fingers-crossed:
[Fire HD 8 and HD 10 Original Android Development] arrush:
Sorry to ask, but you're ahead of me :) Are you running the brick with the tablet on or off?
[Fire HD 8 and HD 10 Original Android Development] nujak:
[MENTION=5455118]arrush[/MENTION]

[MENTION=4676259]rolay07[/MENTION]

This post a few pages back outlined the 9820 process pretty well.
[Fire HD 8 and HD 10 Original Android Development] dood.:
Thanks nujak for the inspiration! The problem was only USB 1.0 was enabled for my Ubuntu VM in Virtualbox. Here's how I fixed it.

Enabled USB 2.0 for Ubuntu VM from Virtualbox settings

Enabled serial port for Ubuntu VM

Charged battery and succeess!

sudo ./fastboot-step.sh

[sudo] password for sam:

Your device will be reset to factory defaults...

Press Enter to Continue...

target reported max download size of 113246208 bytes

sending 'recovery_x' (13196 KB)...

OKAY [ 2.777s]

writing 'recovery_x'...

OKAY [ 0.618s]

finished. total time: 3.395s

******** Did you mean to fastboot format this ext4 partition?

erasing 'userdata'...

OKAY [ 0.216s]

finished. total time: 0.216s

target reported max download size of 113246208 bytes

sending 'MISC' (0 KB)...

OKAY [ 0.020s]

writing 'MISC'...

OKAY [ 0.009s]

finished. total time: 0.029s

rebooting...

finished. total time: 5.114s

Your device will now reboot into TWRP.
[Fire HD 8 and HD 10 Original Android Development] nujak:
Nice to hear. I'm glad it was something simple. Thanks for sharing your solution.
[Fire HD 8 and HD 10 Original Android Development] rolay07:
Thanks mate, it did help and I managed to install lineageOS. :highfive:
[Fire HD 8 and HD 10 Original Android Development] vietbobcat:
My build is 9920. Are there any unlocks, root method for this yet? I didnt realize the development was this for along for the fire HD 8. Tired of all the Amazon Bloatware.
[Fire HD 8 and HD 10 Original Android Development] Mr Bigglesworth:
I've also just picked up a spare HD8 I had and it updated when I switched it on to 9920. Also interested to know if I can root this device. Thanks
[Fire HD 8 and HD 10 Original Android Development] Mr Bigglesworth:
Also, one of my other Kindle Fire HD8s is on 9720. Are there any changes to the instructions on the first page because of this to get this to wok?
[Fire HD 8 and HD 10 Original Android Development] ljm90:
I'm hoping you guys can help. I followed the post by user vendo on how to root using the wire trick and after a successful run on my RPI, it seems the screen is all black. Nothing I seem to do helps.

Any tips are appreciated. Thanks.
[Fire HD 8 and HD 10 Original Android Development] Antieco:
im on 9920 will this guide work on it?

---------- Post added at 07:58 PM ---------- Previous post was at 07:49 PM ----------

mine is on 9920, will this guide work?
[Fire HD 8 and HD 10 Original Android Development] Trecoolius:
On 9920 as well, any confirmation?