yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] DB126:
Don't fool yourself thinking this is a one-and-done exercise. Just look around at the number of redos - both self imposed (plenty of that) and externally driven. While I can appreciate your reluctance to dive into something unfamiliar (been there many times) you may find securing the knowledge/skills to help yourself when things go upside down outweighs the pain of having to engage a 3rd party every time something goes amiss. And they will go amiss at some point with these weird gizmos.

As an aside, I rarely root/unlock when other reasonable options exist for accomplishing goals for the device in question. I prioritize stability over capability and loath spending hours rectifying/rebuilding when thing don't go as planned.

tl;dr - enthusiasts will make it sound easy...but it rarely is.
[Fire HD 8 and HD 10 Original Android Development] tek3195:
Just a thought... root access being obtainable, does not mean it should be obtained by all. If the basic task (albeit unfamiliar) of rooting the device (tools being given to you and the hard work done for you) is too much in any way, then the responsability of maintaining such a device would surely be too much to bear.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
With that said, be warned. This is addictive.
[Fire HD 8 and HD 10 Original Android Development] azuremoonbeam:
i only want root for custom rom flashing im not a builder i just want a stable unamazon tablet that i can read books using either kindle as well as my moon epub reader as well as still be able to veiw prime video since i pay for it the rest just android so i can use my games and other apks that i know and trust.. why is that something i shouldnt have access to just because i dont wanna learn linux? if you can tell me how to completely strip amazon stuff and just keep pime video and the ability to use the regular android kindle app and make it as if its an android please do tell... if not please dont act like a god because you know linux and those that dont wanna or cant learn should just no bother seeking help from those more qualified...
[Fire HD 8 and HD 10 Original Android Development] nujak:
Well, first off, there is no need to get hostile. Reading up and following guides is kinda the spirit of XDA, IMO. If anything is beyond your capabilities you can always learn from other sources and revisit or skip all together until there is perhaps a more accessible way. Particularly, with this, each step from creating a bootable Linux to rooting the tablet is so spelled out its mostly a matter of just reading and repeating. If that's not something you want/care to do, then perhaps this isn't the right thread for you and your more than welcome to start a new one requesting the service you seek (assuming it's not against XDA rules).

Back on point, as of now, there are no custom roms for this device. Based on your needs, it sounds like the Fire Toolbox will be more than enough for your needs and usage case. You can use it to remove Amazon bloat, install Google Playstore and set a custom launcher, all from the comfort of Windows OS. You'll have an Amazon tablet with the look and feel of familiar Android.
[Fire HD 8 and HD 10 Original Android Development] azuremoonbeam:
thanks for the info and i was defensive because i felt disrespected because i said i wasnt interested in learning then i had a few different people say if i dont wanna learn basically go away and thats not cool just because we all learn at different levels and have some strenghts and weaknesses doesnt mean we shouldnt have equal access... i have learning diabilities but i try to learn what im capable of learning i know my limits and i shouldnt have to justify myself to someone who isnt even able to do it locally let alone anyone for that matter...
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I'm working on a custom stock firmware at the moment however I ran into a couple of oddities in the last couple hours. So I'm waiting for some advice and how to proceed. I'm going to check a few things before I jump to conclusions. But if all goes well I should have at least a general release in the next several days. Possibly even a week or so.

Also if I am jumping to conclusions and it isn't what I may think it might be, I may have just discovered how Amazon stoppped us from using live wallpapers. and if that's the case then I totally stumbled across this by accident as how most of my hacks usually have gone.

I really would like to go back to boot image on 5.6.1.0. because the latest version of fire OS really is just too much of a headache and I believe the boot image may be interfering with some of the things that go on in the system at least with my hacks.
[Fire HD 8 and HD 10 Original Android Development] oden3:
I am the same error as you.

You can not recover from the original recovery.

STEP2 is not good either.

help me.:crying:
[Fire HD 8 and HD 10 Original Android Development] :
I have this same issue. I bricked my device after running the bootloader unlock/TWRP flash process and then installing a Magisk Manager update that patched the system image. I can't run the bootrom tool to fix it because I get the same serial protocol mismatch error every time. Someone please help.
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
Did you update Magisk from Magisk Manager? If so, only flash Magisk from TWRP in the future.

If you can still boot TWRP, you can just flash stock firmware by changing the .bin file to .zip.
[Fire HD 8 and HD 10 Original Android Development] :
Yeah I'll make a note of that for the future. If I can even get this device working again. I can't boot to any system. All it does is show the amazon logo and then reboot. I've tried all versions of the bootrom tool and it just displays the same serial protocol mismatch error every time. I'm thinking of trying to restore with SP Flash Tool and the stock update bin. Would that work or make it worse?
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
Not sure if SP Flash Tool would work, but it couldn't hurt at this point. Still, I'm surprised you can't boot to recovery just from installing Magisk through Manager.

I assume you've tried the unbrick method described in step two, following the guide by retyre?
[Fire HD 8 and HD 10 Original Android Development] :
The first part of that guide says if you can get the amazon screen (which I can) then you shouldn't use it. I think I'll try SP Flash Tool with the stock update.bin file and see where that gets me. If that works then I'm just going to revert the partitions back to stock since this is too risky for me I think.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
SP-Flash tool won't work on the amazon-devices.

That is part of the reason why this exploit exists.

That said, there is no reason why you wouldn't be able to enter TWRP if all you did is mess up the boot by updating through Magisk Manager.

If you are sure you cannot access TWRP using the button-combination, you CAN use the unbrick method. It just isn't recommended if another way is available since it requires opening and (partially) disassembling the device.
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
he should be-able to just flash the stockboot from hacked fastboot no ?

[MENTION=4470081]topjohnwu[/MENTION]

is there a way to configure magisk to be-aware of the new boot path so it will work correctly on devices that need such exploites ?

it just needs to be /somepath/boot_x instend of somepath/boot

tho I guess this could be fixed when ever LOS gets ported ...
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
But he can't enter hacked fastboot if both boot and recovery are broken. (I still believe TWRP should work though)

For a custom rom/kernel that could be fixed the same why it is fixed in TWRP, by moving the symlinks: https://github.com/chaosmaster/android_device_amazon_suez/blob/master/recovery/root/fix-symlinks.sh

For stock that isn't an option.

I agree it would be nice if MagiskManager had the option to specify the boot-partition.
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
I mean the stock kernel we can build and boot

but fireos is just Ewwwwwww

I haven't seen much progress toward LOS tho I been stalking the usual Gerrits and git

but not surprised its always a huge pain in the ass
[Fire HD 8 and HD 10 Original Android Development] :
I was able to get the device to boot into TWRP using the hardware combination and I'm restoring FireOS 5.6.3.4 using ADB sideload. Neither the boot-recovery.sh nor the boot-fastboot.sh commands worked and neither of them displayed any errors so I didn't think the hardware combination would work either. Sorry for the time I wasted with this and thanks a lot for your help.

On a sidenote: I'll just use mtk-su and SuperSU from now on.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
The fix could be integrated into the stock-kernel (or into its initramfs to be exact)

Sadly I haven't had much time to work on it lately.

Status still is wifi working, audio partially, graphics working but some glitches in recent apps and navbar.
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
thats what I figured

I played with it some but whats the saying time and money ...
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Glad you got it worked out.

The boot-recovery and boot-fastboot scripts will only work as long as the boot-exploit is still intact.

Specifically the boot-fastboot script is meant to recover, should TWRP be broken and you are stuck in a bootloop (orange Fire logo still showing).

Booting into TWRP should automatically fix the boot-exploit should it have been broken i.e by updating through MagiskManager.

I am not sure I can recommend SuperSU on the HD10.

Magisk works well, you just have to take care not to update through MagiskManager but via TWRP.

Also as mentioned should you end up in that situation again, just boot into TWRP and then reboot it will be fixed automatically.
[Fire HD 8 and HD 10 Original Android Development] MisterMalakai:
I had the same issue happen to me yesterday. Download a stock ROM or one of dragonfires optimized ROMs, hold volume up and power at the same time to boot back into TWRP, transfer the ROM to your tablet over USB, then flash the ROM, wipe dalvik cache, then reboot.

---------- Post added at 10:11 PM ---------- Previous post was at 10:07 PM ----------

We sincerely appreciate your hard work. If there is something the rest of us can do to assist you in the process, please don't hesitate to let us know. I know I'm not the only one willing to lend a hand.
[Fire HD 8 and HD 10 Original Android Development] :
I was using SuperSU before I ran the unlocking/TWRP flashing process and it works fine. Only issue is that with my installation (manual install using this tutorial), I had to set automatic permissions granting. Maybe flashing SuperSU from TWRP would work differently but I'm not sure. The first time I ever Magisk was today and it didn't turn out well (partly my fault for not paying attention to the risks) so I'll just stick to SuperSU for now. Thanks again for your help.

---------- Post added at 11:16 PM ---------- Previous post was at 11:14 PM ----------

I used ADB sideload myself but I guess there isn't much of a difference. I'm still pretty new to the android rooting world and I have quite a complicated device. I'm interested in knowing how this tool works but given the complexity I probably wouldn't understand most of it.
[Fire HD 8 and HD 10 Original Android Development] Dan_firehd:
You may want to try this SuperSU access workaround :

https://xdaforums.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269
[Fire HD 8 and HD 10 Original Android Development] oden3:
With hardware combinations, did you disassemble and short it?
[Fire HD 8 and HD 10 Original Android Development] nujak:
Sounds like he was able to just use the Volume Up + Power Button to boot to TWRP
[Fire HD 8 and HD 10 Original Android Development] tek3195:
My thought wasn't meant to be disrespectful towards you or suggest you go away. I was just thinking that there is a lot more to it than people realize. Stay, stick around, read and you will wind up learning things that you didn't realize yoy were learning. Set your own pace. Other than that , it was... "just a thought".
[Fire HD 8 and HD 10 Original Android Development] oden3:
ah!

TWRP can not start because I accidentally erased the boot loader.

I was able to BootRom mode from handshake.py of aftv2tools, so I can not recover from here?
[Fire HD 8 and HD 10 Original Android Development] ECrispy:
I just bought a Fire HD 10 and it came with Fire OS 5.6.4.0 from Amazon. I have a few questions -

- I have Ubuntu running in a VM in Windows using WSL. I also have a Macbook. Which one should I use to run the scripts?

- once I root and get custom launcher like Nova, can I still use Amazon Prime features? I like those. But I dont want the rest of the bloat.

- I saw this post (https://xdaforums.com/showpost.php?p=79496475&postcount=9) which says you can disable amazon apps without needing root. What does root get you in addition besides custom launcher? Does LauncherHijack work well?
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
neither needs to be running on the metal No vm's no emulation

create a bootable linux usb drive
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Virtual box works well. Tried on my Fire 7 2017.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Thanks for this. I had adopted the often made claim that type two hypervisors were NG on a Windows base. Don't have an immediate need but good to know.
[Fire HD 8 and HD 10 Original Android Development] yuera:
Which distro did you use? VM sounds easier for someone like me that that never used linux :P
[Fire HD 8 and HD 10 Original Android Development] Dan_firehd:
Window 10 with VirtualBox+Ubnutu also works well on my Fire 7 2017 as I have described in details here.

I suppose then that the same Window 10 with VirtualBox+Ubuntu setup will also work well for HD 10 2017(suez) as described in the OP?

= = = = = = =

Edit : The same Window 10 with VirtualBox+Ubuntu setup also works well for HD 10 2017(suez) as described in post #661.
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
Vbox's usb filters can cause issues during the process, the usb filter basically intercepts the usb connection while the vm is running

things that will cause the usb filter to eject and possibly not recover

rebooting the device

plugging an anouther device into the host system

a device driver installing/uninstalling in the background

random issues with the vm or hypervisor being silly on a particular chipset

yes its possible todo it in a vm but making a usb stick and booting from it takes less time and is safer
[Fire HD 8 and HD 10 Original Android Development] Dan_firehd:
For the case of Fire 7 2017, in steps 1 and 2 of my write-up, I included links to get the latest distro for VirtualBox and Ubuntu.

See here.
[Fire HD 8 and HD 10 Original Android Development] Flo655:
Thanks for this tutorial! Successfully unlocked my Fire HD 10 without issues. Quick question though: any reason why the system partition is so small (is it smaller than before)? I can't get the nano version of the open gapps to install.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
The system, when fully expanded, should not be more than 1.7-1.8 GB total. That's the constant, overall system size. Unlocking shouldn't or doesn't touch the system.
[Fire HD 8 and HD 10 Original Android Development] FOLOL2011:
Hello guys

My fire hd 10 has magisk 19.0. Has anyone updated to Magisk 19.2.

Is it safe ?

UPDATE : it works but I updated via TWRP install + wipe dalvik cache (may be not necessary)

The update via M. Manager didn't work well it helped me to download only the 19.2 zip
[Fire HD 8 and HD 10 Original Android Development] tommy_hawk:
For sanity of others trying the steps in 1st post

1. For me, at this step, after plugging the device back in, didn't continue the process. Had to press the power button a couple of secs, the it went on.

After you have confirmed the bricking by typing "YES", you will need disconnect the device and run

Code:

sudo ./bootrom-step-minimal.sh

Then plug the device back in.

2. Also the TWRP was already flashed and the system boots into it after sudo ./fastboot-step.sh .

Running sudo ./step-2.sh gives a notice that is a duplicate action, I just went ahead anyway.

Installed Magisk 19.1 and debloated using one of the guide here too. https://xdaforums.com/hd8-hd10/general/guide-completely-debloat-fire-hd-10-2017-t3919151

Now its a decent spec reasonably priced Nexus 10 not made by Google Hah!
[Fire HD 8 and HD 10 Original Android Development] Dan_firehd:
Success with Window 10 via VirtualBox+Ubnutu

I can confirm that this OP works using Windows 10 with VirtualBox & Ubuntu

The initial state of my tablet is as follows.

HD10 (7th Gen; Suez) was on Amazon OS 5.6.1.0, rooted via MTK-SU:

https://xdaforums.com/hd8-hd10/orig-development/experimental-software-root-hd-8-hd-10-t3904595

with permant root managed by SuperSU:

https://xdaforums.com/showpost.php?p=78991273&postcount=10

and SuperSU access workaround:

https://xdaforums.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269

1. Install VirtualBox from here : https://www.virtualbox.org/wiki/Downloads

2. Follow this instruction to install Ubuntu : https://itsfoss.com/install-linux-in-virtualbox/

3. After successful installtion of VirtualBox+Ubuntu, make sure one has the most up-to-date Ubuntu packages by clicking the "Software Updater" application in Ubuntu.

4. Make sure VirtualBox+Ubuntu can communicate with the HD10 (7th Gen; Suez) when it is plugged into the USB port. I have two USB3 ports and one of them seems to work better. Make sure you know how to pass the USB device from PC to VirtualBox by click-checking “Devices--> USB” on the VirtualBox menu.

5. Set Default accss in SuperSU to "Grant", otherwise the first script "step-1.sh" will stuck on "Testing root access ...."

6. In the Ubuntu "Terminal" application window, type :

7. Download and extract "amonet-suez-v1.1.2.zip" to Ubuntu.

8. In the Ubuntu "Terminal" application window, navigate to the "amonet" folder and start the 1st script by typing:

9. “step-1.sh” script runs successfully and HD10 reboots via factory-reset commanded by the script "step-1.sh".

10. HD10 at initial setup → skip Wifi → Tap “Serial Number” 7 times to enable “Developer Options” → “Enable ADB”, followed by passing the USB device from PC to VirtualBox by click-checking "Devices --> USB" on the VirtualBox menu.

11. In the Ubuntu "Terminal" application window, navigate to the "amonet" folder and continue with the 2nd script by typing:

12. “step-2.sh” script runs successfully and HD10 reboots into TWRP.

13. In TWRP, tap "Reboot" and then "System" to boot into Amazon Fire OS.

14. To boot into TWRP from a powerd-off HD10 : Hold Right-Volume and then Power buttons together untill white “Amazon” logo appears. After seeing white “Amazon” logo, release both buttons.
[Fire HD 8 and HD 10 Original Android Development] Frootz:
Success 5.6.4.0

Thank you. Appreciated the scary bit. :good:
[Fire HD 8 and HD 10 Original Android Development] spalding1028:
THANK YOU!!!! I ran into this and started losing my mind! disconnected and reconnected a couple times and it worked. Even on the VM I used.
[Fire HD 8 and HD 10 Original Android Development] c6z06vette:
Guys:

I have one HD10 7th gen rooted and on TWRP and Magisk, but running into a problem with another HD10 7th gen on 5.6.3.0

When I run ./step-1.sh in adb shell i'm getting this loop error: "mounting /dev/block/loop3 on /system/xbin/ failed: Device or resource busy". It looks I need to mount /system/xbin before I run the script. Please advise the proper command line. Note: It does read this output before the error:

Trying to use mtk-su to get temp root...

Pushing root files

[100%] /data/local/tmp/mtk-su

[100%] /data/local/tmp/minisu.img

[100%] /data/local/tmp/busybox

New UID/GID: 0/0
[Fire HD 8 and HD 10 Original Android Development] c6z06vette:
I'm going to do my own reply. I ended up doing an Amazon firmware upgrading to 5.6.4.0; then I ran the ./step-1.sh script and went through the bootloop downgrade as described in the OP without any hitches. Got the HD10 on Magisk and TWRP. I even ran the Odexed ROM version on XDA. The tablet could only be better if we ran a full out ASOP custom ROM.
[Fire HD 8 and HD 10 Original Android Development] skruff77:
Just did my fire hd10 using VMware and Ubuntu 18. Works just fine.
[Fire HD 8 and HD 10 Original Android Development] McSpidey95:
IMEI recovery

I had unbricked my phone which got bricked due to incompatible twrp recovery. Well it's fixed and I rooted my phone successfully. But the IMEI address has been erased. I tried all the methods in YouTube and all of them failed. Anyone know how to fix this.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Wrong forum. Please search your phone forum.

Thanks.
[Fire HD 8 and HD 10 Original Android Development] siochs:
Fire HD10 FireOS 5.6.1.0 successfull

Used

- a Debian9 live system

- Fire HD10 with FireOS 5.6.1.0 (preveted OTA after first start)

- arm64/mtk-su in amonet/bin

- step-1.sh and then step-2.sh

- flahed latest magisk stable zip in twrp

Everything worked as described in the Guide.

Great work, thank you!
[Fire HD 8 and HD 10 Original Android Development] McSpidey95:
My phone doesn't exist in any forum
[Fire HD 8 and HD 10 Original Android Development] nujak:
Next time, please search for an appropriate forum or use the general forums. Here is a link to The Official XDA Support thread for Android Phones
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
Can Xposed be flashed in any way yet?
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
https://xdaforums.com/hd8-hd10/general/xposed-framework-fire-hd-8-6th-t3549043
[Fire HD 8 and HD 10 Original Android Development] Rongict:
My Amazon Fire HD 10 7th tablet has a logo hanging.

What to do to subdue it.

thank
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Which logo? The amazon logo or the Fire logo?

Check Post #2 for unbricking instructions.
[Fire HD 8 and HD 10 Original Android Development] Rongict:
Fire logo.

---------- Post added at 09:45 AM ---------- Previous post was at 09:40 AM ----------

But Recovery on my amazon fire hd 10 still accessible .
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Well then reinstall ROM and do a factory reset.

You'll have to be more specific what you did that caused the bootloop.
[Fire HD 8 and HD 10 Original Android Development] RNFL:
Question

Can i use my Chromebook OS to unbrick and continue to root kindle or do i need to use PC
[Fire HD 8 and HD 10 Original Android Development] RNFL:
Can i use my chromebook os to do this
[Fire HD 8 and HD 10 Original Android Development] LukasB1:
no need to quote the entire text of the first post
[Fire HD 8 and HD 10 Original Android Development] nujak:
Chrome OS, no (or atleast not that I'm aware of). But, if you can boot a Linux live usb on your chromebook then yes. Instructions for making the USB are somewhere in this thread.
[Fire HD 8 and HD 10 Original Android Development] Kctucka:
[MENTION=7104332]k4y0z[/MENTION] Your other recovery for the HD8 got me thinking. This version of TWRP can successfully backup/restore system, data, and boot with no modifications/workarounds required?

I created a backup, but when I've bricked, I've been hesitant to use it, instead using other methods in TWRP to get out. I'd love to just easily restore instead.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Yes, should work without issues.
[Fire HD 8 and HD 10 Original Android Development] Turkishflavor:
so, no chance with win10? how about mac os?
[Fire HD 8 and HD 10 Original Android Development] eldu69:
It works perfectly with WSL on windows 10.