yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] -BoneZ-:
When you boot into TWRP (unit off, hold down Volume UP + Power at the same until Amazon logo appears), then select "Wipe" button, then "Advanced Wipe", then you can select Dalvik, System, Data, and Cache. Then swipe to wipe at the bottom. Then flash your zips while you're in TWRP by pressing the FLASH button, then selecting the zip you want to flash. But make sure all of your zips are in the root directory on your tablet before you go wiping.
[Fire HD 8 and HD 10 Original Android Development] idorobots:
How were you able to move the zips to the root directory? I get an error saying it's a "Read-only file system" even though I believe I'm doing it as root. I tried moving the zips to both '/' and '/root/'. Do you know if there's any other directories that remain untouched during the wipe? Maybe I can store the zips on an sd card and mount it before or after wiping?
[Fire HD 8 and HD 10 Original Android Development] -BoneZ-:
By root directory, I mean plugging the tablet in to your computer while it's booted up, and putting the zips on the internal storage (not inside any folder). When the tablet is plugged in, it is like plugging in a thumb drive where you can transfer files back and forth.

I should have said root directory of the internal storage. My apologies.
[Fire HD 8 and HD 10 Original Android Development] idorobots:
Oh okay. I was under the impression that after the wipe that I would not be able to connect through adb because of missing software and that you were making sure that I put the zips in a folder that won't be wiped haha
[Fire HD 8 and HD 10 Original Android Development] -BoneZ-:
Nope. Just move the zips over to the internal storage, boot into TWRP, wipe what I mentioned earlier, then Flash all the zips in the order mentioned earlier. You can select multiple zips, so you'll be able to select all 4 and it will flash all 4 in the order you select them.
[Fire HD 8 and HD 10 Original Android Development] idorobots:
Just finished wiping, do I now resize /system? When I try to resize it just resizes it to the same size (1563 mb) but it might already be big enough since in the OP you linked he mentioned 1.6gb being large enough.
[Fire HD 8 and HD 10 Original Android Development] -BoneZ-:
Nobody ever said anything about resizing the system, lol. That OP already did that in the ROM. Just wipe and flash the zips. That's it. :)
[Fire HD 8 and HD 10 Original Android Development] formerglory:
I have my Fire HD 10 rooted already using the offline root method that was posted here a while back, what’s the benefit of unlocking the boot loader if I’m already in a stable rooted setup?
[Fire HD 8 and HD 10 Original Android Development] Turkishflavor:
so, I'm rooted now and also have TWRP installed, running Fire OS 5.3.6.4.

Is it now possible to update to the latest version and keep root etc. or not?
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
If you update to the latest version of Fire OS, you'll just need to reflash Magisk in TWRP.

You'll also lose any of your system partition modifications, as the update wipes the system partition.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Well, that wasn't a very bright idea...

Why would you flash a GPT that is meant for a different device (tank)?

You are actually lucky, that the script flashed just the GPT and nothing else (because it couldn't find the files)

I have attached a zip-file that should flash a proper GPT for suez, it is for the 32GB-version.

Should you have the 64GB-version it should still work, but you will lose 32GB of storage space.

Or someone with access to a 64GB-version will have to upload their GPT.

Extract it in the same directory where you extracted amonet-suez-v1.1.2.zip
[Fire HD 8 and HD 10 Original Android Development] WetWilly:
Sharing an experience using VirtualBox (unsuccessfully) and a live Debian 10 USB stick (successfully) to do this process on a Fire HD 10 with OS 5.6.0.1 root/SuperSU/Xposed.

tl;dr - The surest thing time-wise if you don't have a Linux system is to use a live Linux distribution with optional persistence. Possible fix below if your MTP mode goes south.

So I try the VirtualBox method, install Virtual Box + Ubuntu (which takes longer than installing a live system to a USB stick). That part was easy, and this was on an older Dell Optiplex running Win 7.

1) The Fire showed up in adb devices just fine in VirtualBox/Ubuntu. However, I could NOT under any circumstances get the Fire's authorization for USB debugging working; the Fire showed up as "<serial number> unauthorized". Tried all permutations/toggling of USB debugging, MTP, and Camera mode switches, no go. But it worked in Win 7.

2) USB devices were detected and could be accessed in VirtualBox/Ubuntu, but upon exiting VirtualBox - every time - the USB ports were FUBAR'd in Win 7 to the point I had to reboot.

3) MTP mode on the HD 10 stopped working in Win 7, i.e., when I plugged in the Fire, I'd get an MTP driver error even though the Fire ADB device showed up. I installed Debian 10 on a USB stick (with persistence) and this TWRP install process went flawlessly once I set the HD 10 to Camera mode instead of MTP mode. But MTP mode still didn't work after the flash and accompanying factory reset. Flashed 5.6.4.0 through TWRP; MTP still didn't work. Went into TWRP, wiped system, data, Dalvik and cache partitions, then immediately flashed 5.6.4.0, and MTP came back. Can't pinpoint what screwed MTP mode up.

Regardless, many thanks to k4y0z for the hard work.
[Fire HD 8 and HD 10 Original Android Development] kumanotabi:
Thanks!!!

I was able to repair it safely!

I started it, but I take a Fire tablet that can not use wifi.

I can not use ADB commands because I can not enter developer mode.

It can not skip wifi connection at the first time of setup and can not open the setting.

So I came to XDA for the first time in a year and a half, I was very surprised.

The location of the test pins, the preloader repair script, and even used the custom ROM.

I felt that it worked by entering the forced fastboot mode from the test pin and burning a custom ROM.

However, when I tried the script from the test pin, I got something wrong and damaged the GPT area.

Then it arrived at the repair thread of "Fire Stick TV".

Beginning of a nightmare.泣いている
[Fire HD 8 and HD 10 Original Android Development] wisp4400:
I'm having trouble when i get to

sudo ./step-1.sh

I get

Testing root access...

Trying to use mtk-su to get temp root...
No mtk-su found, you can get it here: https://xdaforums.com/hd8-hd10/orig-development/experimental-software-root-hd-8-hd-10-t3904595

I've followed the directions on the link but it doesn't seem to change anything. I've added the file to the folder I'm in and still nothing. I'm not sure what else I can do for this.

Anyone have any advice?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Yeah...
[Fire HD 8 and HD 10 Original Android Development] genica:
What would need to be changed for this to work on the fire TV 2? They both have MT8173 chipset

Thanks
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
For unlock, the LK-payload would need to be ported.

The brom-payload (I.E flashing/dumping EMMC and downgrading) should pretty much work as is.
[Fire HD 8 and HD 10 Original Android Development] genica:
If this is something you want to work on, I'll be happy to test
[Fire HD 8 and HD 10 Original Android Development] haiti525:
Following the procedure in the first post on this thread, everything went ok, then after flashing the Magisk zip in TWRP, the Fire 10 is now in a bootloop. Was running 5.6.0.1, and previously rooted via the older "offline rooting" method, but without TWRP.

I can easily get back into TWRP despite the bootloop, but I'm not sure what the proper troubleshooting method to recover from this is, and I don't want to make things worse.

Would flashing DragonFire1024's rom be a viable recovery option:

----

xdaforums.com/hd8-hd10/development/rom-t3929969/

Format /system then flash ROM, stockboot ,magisk gapps in that order.

----

Suggestions appreciated!!
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
Not sure why flashing Magisk in TWRP would cause a bootloop.

Either way, you should be able to recover by flashing stock firmware, the modified stock firmware, or the new lineage build if you're feeling adventurous.

You can flash ROM and gapps at the same time, boot, then flash Magisk from recovery.
[Fire HD 8 and HD 10 Original Android Development] :
I'm getting stuck on "Check GPT" in the "bootrom-step.sh" file. Anyone know what the solution to this problem is?

Edit: It's because I ran it from a Mac. It seems to work for going back to stock but I guess not for this script. Using an Ubuntu USB worked fine.
[Fire HD 8 and HD 10 Original Android Development] DarraghMUFC:
Hi everyone. I just have a question about the first step in this process mainly

sudo ./step-1.sh

I had root via Kingoroot(I know don't kill me) with SuperSU and i tried inputting the above command in Ubuntu terminal(all relevant drivers are installed) but all I received was

sudo: ./step-1.sh: command not found

which is strange. I since factory reset my Fire10 and am in the process of doing the MTK-SU temporary root from the topic linked in OP's post to try and see if that fixes it but I think it might be something else. Any help welcome!
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
Did you open the terminal in the same directory as the unzipped exploit files?
[Fire HD 8 and HD 10 Original Android Development] DarraghMUFC:
Yeah I extracted the amonet files and right clicked open terminal while in the directory and tried to input but got an error.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
You probably extracted the files onto a FAT or NTFS partition which can't deal with linux-permissions.

Extract the files to the desktop and you should be good to go.
[Fire HD 8 and HD 10 Original Android Development] DarraghMUFC:
I think previously I made a new folder on the desktop and extracted both files there and opened terminal while in the folder. Do you think it should work if I put both on the desktop and opened from there? Apologises for the silly questions. PS: in the context of Ubuntu what do you mean by the FAT/NTFS partitions?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Just make sure you extract the ZIP while you're in Ubuntu, don't extract it on windows.

By FAT/NTFS partitions in this context I mostly mean "windows"-partitions.
[Fire HD 8 and HD 10 Original Android Development] DarraghMUFC:
Thanks for the advice. Everything I've done up to this point has been on ubuntu though. All I want to do is get magisk on my fire tablet and be done with it xD
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I'm sorry, not sure what else could be the issue.

The issue is definitely with your setup/linux environment and not with the tablet.

You can try (from a terminal in the directory where you extracted the files)

chmod 755 step-1.sh
[Fire HD 8 and HD 10 Original Android Development] DarraghMUFC:
Will do. I used Rufus when installing Ubuntu with a USB but it's possible there's a problem with the set up. Thanks again and I'll let you know if I fix it.
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
Perhaps you require persistent storage then?
[Fire HD 8 and HD 10 Original Android Development] DarraghMUFC:
Im almost certain that this is my problem. I was even told yesterday to use Linux Live USB creator but instead I picked Rufus. Each time I've booted I've had to restart my progress/redownloading adb drivers and the repositories. I'm going to do a fresh install with LL USB and start over and see if that helps. Huge thanks.
[Fire HD 8 and HD 10 Original Android Development] :
Just out of interest, how, in summary, does this exploit work. I understand the boot_x and recovery_x partitions are required but not exactly why. And is there any way this exploit could be ported to other devices with locked bootloaders (specifically the hacked bootloader mode) assuming root access could be acquired in some way beforehand?
[Fire HD 8 and HD 10 Original Android Development] gnino:
Will this work on the 5th gen 2015 hd 10? I have searched the threads and see nothing stated about it.
[Fire HD 8 and HD 10 Original Android Development] nujak:
This only works on the 7th gen Fire 10. Also, no need to quote the whole OP.
[Fire HD 8 and HD 10 Original Android Development] knownazepic:
I used VirtualBox + Ubuntu and it worked very well. Thanks!
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Question [MENTION=7104332]k4y0z[/MENTION] will this work on the HD 10 5th generation? I'm assuming worst case scenario would be taking the back off if so.

Nevermind. I see the few posts above. Is there a reason it would not work?
[Fire HD 8 and HD 10 Original Android Development] 1132422738:
how can i finish these steps using a Windows system? Maybe its too hard for person who dont have some professional knowledge .
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
You can't. You need Linux in one form or another. Be a virtual machine etc. I have 3 fire 10s and spent hours trying on windows. Just isn't possible.
[Fire HD 8 and HD 10 Original Android Development] hy93:
Thank you for your effort, I have the firmware 5.6.4.0 after i disconnect the device and run the

Code: sudo ./bootrom-step-minimal.sh it stuck on " waitting for bootrom" and the device still on !!
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Did you do step-1.sh first?

Did it run through without errors?

What do you mean by the device is still on? Is FireOS still loaded?
[Fire HD 8 and HD 10 Original Android Development] gb_mma:
I have this same issue, the device is recognised as being in the temp bricked bootloader but the script won't go any further than waiting for bootloader.

FireOS wont load as the device is bricked.
[Fire HD 8 and HD 10 Original Android Development] hy93:
Thank you for your respond, yes i did the step-1.sh with no errors and yes the FireOs still loaded !

I think I'm doing something wrong when i do the downgrade ( any Downgrade instruction?)
[Fire HD 8 and HD 10 Original Android Development] deiscodt:
Same situation over here. Did all steps an stuck with a "waiting for bootrom" prompt

---------- Post added at 10:49 AM ---------- Previous post was at 10:10 AM ----------

I'm such a fool and missed to carry out fastsboot shell file. :D:D

My apologies.
[Fire HD 8 and HD 10 Original Android Development] Hawk600:
Thank you very much OP for sharing our hard work! I got 2 new HD10 rooted today with Magisk installed.

One issue I am facing now is that I am getting a error 70 while trying to install Gapps, it wont install due to lack of room.

I tried to search and found nothing about it, can anybody please help?
[Fire HD 8 and HD 10 Original Android Development] ShneedlwWoods:
Same here. Error 70 with arm/pico gapps.
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
The system partition isn't super large on these things.

However, you have root, so you can delete the preinstalled Amazon apps that don't break anything.

Some examples would be the silk browser and the app store.
[Fire HD 8 and HD 10 Original Android Development] tylerhole:
This worked wonderfully! Thank you [MENTION=7104332]k4y0z[/MENTION] !!
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Let's just hope this is a fluke on my tablet and a domino effect doesn't happen with other tablets. It's probably in preloader. I just fired up one I thought was dead. Lsusb says that one is preloader and the interesting thing is, it says mediatek, but it doesn't say mt8173, it says something like MTxx65 or MT65xx.
[Fire HD 8 and HD 10 Original Android Development] Wall.swe:
Worked and TWRP is there, but when I try to boot into FireOS I get stuck on Amazon logo.

Any suggestions?
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Did you happen to flash Xposed?
[Fire HD 8 and HD 10 Original Android Development] Wall.swe:
No. I just followed the steps in the guide and as I didn't have Magsik at hand I tried to reboot from TWRP to FireOS.

I can access TWRP.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Similar issue with me, except I think the tablet defaulted to bootrom or preloader so I cannot access TWRP. Did you happen to flash a modified amazon update bin (changed it to .zip and edited the script) of FireOS and flash it in TWRP?
[Fire HD 8 and HD 10 Original Android Development] Wall.swe:
No, I didn't flash anything in TWRP. :) Just booted the tablet into TWRP from the second script in the guide and than rebooted

---------- Post added at 11:35 AM ---------- Previous post was at 11:32 AM ----------

Would it be safe to retry all the steps in the guide? (if I can)
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Yes.
[Fire HD 8 and HD 10 Original Android Development] Wall.swe:
Great, thank you! I'll try the steps again and this time I'll apply the root file in the guide if I lost root in the process.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
That would be

It's the same on all mediatek devices.

If you are stuck in preloader/bricked you will have to do the unbrick procedure.

It's pretty much the same as I described in the Fire 7 Unlock thread or in the Fire TV Stick 2 Unlock thread, just use the scripts from this thread (bootrom-step.sh).

To enter bootrom you will have to open the device, check [MENTION=3497316]retyre[/MENTION]s thread here (Don't use the zip-file from there as it will only work to recover from a downgrade)

I will add the unbrick procedure to this thread later.

That's weird, did you try to factory-reset?

If that doesn't work, install the stock-update-bin through TWRP.
[Fire HD 8 and HD 10 Original Android Development] Wall.swe:
Hi!

No I haven't dared to try anything yet :o. Could a factory reset in TWRP work?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Yeah, although I doubt it will make a difference.

Just out of curiosity, what FireOS-Version are you on?

It may be, that it's to old and doesn't like the new bootloader.

In that case just install the 5.6.3.0 update-bin (rename to .zip) through TWRP.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Interesting. I didn't do anything to get it into that mode. I just hope it's not the rom testing. But nothing is tied into anything aside from the system. Well I'll let you know how it goes when I get home and have a chance to experiment.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
If your boot.img is messed up, it could be stuck in preloader, allthough you should still be able to get into recovery using the button-combination.

Try holding the power button for 20+ seconds, to make sure it is powered off.

Then try to enter TWRP using volup + power.

EDIT:

Actually it should still go into LK and show the amazon logo.

So it seems your LK got messed up.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
There was a blank screen no matter what I did. I tried all button combos to no avail. I will see what I come up with.
[Fire HD 8 and HD 10 Original Android Development] Wall.swe:
I'm on 5.6.0.1.

I'll try to to do a factory reset in TWRP and if that doesn't work I just grab the official 5.6.3.0 update and rename it and put it on a sd-card or is there another way to get the file onto the tablet?

Thank you for all the help :)

---------- Post added at 01:41 PM ---------- Previous post was at 01:36 PM ----------

Just to be clear I just swipe to factory reset? or do I need to use the advanced wipe or format data option?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
You could also adb push the file to the tablet or use adb sideload

You could do format data, but I don't really expect it to make a difference.
[Fire HD 8 and HD 10 Original Android Development] Wall.swe:
You were right, factory reset did nothing.
[Fire HD 8 and HD 10 Original Android Development] bibikalka:
There were a couple of people in HD8 thread who bricked through what appears to be some twrp operations. One of those tried a custom Rom made by [MENTION=8978978]Rortiz2[/MENTION].

I wonder now how installing a Rom into /boot and /system only causes such devastation. Or was the Rom was trying to overwrite more than just these 2 partitions?I

Finally, are there perhaps some twrp bugs that show up and cause bricking? Of course, these could also be pure user errors.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
That shouldn't happen with this TWRP, as it should prevent you from overwriting lk/preloader/tz unless your updater-script specifically overwrites the protection. (Or you didn't use TWRP to flash)

[MENTION=8165603]DragonFire1024[/MENTION] Can you share the updater-script of the ROM you were flashing?

I haven't noticed any bugs like that.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Use GAaps nano which contains only essential Google apps including Play Services/Store. That's probably all you need. Any other Google property (app) such as YouTube can be individually loaded from the Play Store. Apps installed via the Play Store are placed in the much larger data/user partition. This approach is easier than manually pruning the system partition which can create havoc if you nail the wrong item. If desired, do the latter when you are ready and confident in your actions.
[Fire HD 8 and HD 10 Original Android Development] ShneedlwWoods:
Can you tell me how to do this? Is it via TWRP possbile?
[Fire HD 8 and HD 10 Original Android Development] Hawk600:
Thanks, I tried Gapps nano and pico and still getting the install error!

I was wondering if I could uninstall some Amazon bloatware with ADB to free up space, doing some research on it right now but I don't want mess up, Kindle is running great after k4y0z hack! :)

Another option could be flashing Lineage-12.1 room but it the headphone output still broken and I need that so I going to have to wait for the fix first.

---------- Post added at 12:11 PM ---------- Previous post was at 12:09 PM ----------

As far as I know you can only do it using ADB and I might try it if I cannott find a different solution.
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
There are a number of apps that can do it, such as link2sd or system safe app remover. Adb works well too. You can also do it with a file explorer.

There are a few guides here that can tell you what's safe to remove. Personally, I'd say less is more. Only remove what you need to get gapps to work.

If you're worried about breaking things, you can take full backups of your setup using TWRP. This way you can just restore from recovery if things go south.
[Fire HD 8 and HD 10 Original Android Development] ShneedlwWoods:
Thanks, after another wipe flashing gapps arm64 pico was working. Magisk aswell.
[Fire HD 8 and HD 10 Original Android Development] aleks79:
Bought one more FireHD and this time I have another issue )

Successfully performed step-1, but after this device was restarted to black screen that asked me PIN/Password. I haven't setup any. Tried to enter anything and had screen with

"Corrupt Encryption"

The PIN/Password you entered is correct, but unfortunately your data is corrupt. ....."

And it's asking me to perform factory reset.

Should I do it?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
there is no factory reset protection on the fires but there is protection from them being registered to Amazon again if they were stolen and reported as such. if you did not buy it brand new it's quite possible it was locked by that means. The only way the device would have been encrypted with a password if it was previously owned and encrypted.so a factory reset won't hurt it either way.