yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
Thanks! It appears to have gotten root now. I'll try the steps on the main page now :) Cheers!
[Fire HD 8 and HD 10 Original Android Development] drakulaboy:
a big thanks to the author of the topic, this old stuff now got installed android 9, root and twrp, a new life for a thing with 2 GB RAM :D
[Fire HD 8 and HD 10 Original Android Development] pascal009:
Interesting. The last Fire OS firmware for the suez was 5.7.0.0, which is based on Android 5.1.1 (Lollipop). Could you point us to the Android 9 ROM you used? I might consider playing with it on one of my Fire HD 10 7th Gen. Is your Android 9 a 32-bit or 64-bit architecture? I know that while the CPU on this tablet is 64-bit the userspace is still 32-bit and you can't install arm64-v8a apks on it.

Thank you
[Fire HD 8 and HD 10 Original Android Development] pascal009:
Greetings,

A new version of Magisk (25.0) has been released recently

Release Magisk v25.0 · topjohnwu/Magisk

Another major release! A lot of the changes aren't visible at the surface, but v25 is actually a really substantial upgrade! MagiskInit Rewrite A significant portion of magiskinit (the critical sof...

github.com

In the words of its developer it is "Another major release! A lot of the changes aren't visible at the surface, but v25 is actually a really substantial upgrade!"

Can one of the experts here on the forum tell whether it is safe to flash this new version over the previous one (24.3) on the TWRP'ed

and rooted giza?

Your opinion is greatly appreciated.

pascal009
[Fire HD 8 and HD 10 Original Android Development] Mlinko6:
Dear All,

I have a following problem. I've managed to get the root access on my fire hd 10 7gen tablet:

check done

sched_setaffinity: Function not implementedmadviseThread() done

procselfmemThread() done

[*] exploited 0x7f78dce000=f97cff8c

end!!!!!!!

<WSRoot><Exploit>0</Exploit></WSRoot>

<WSRoot><Done>0</Done></WSRoot>

shell@suez:/ $ su

root@suez:/ #

When I try to install the supersu - eu.chainfire.supersu_2.82-SR5-282_minAPI9(nodpi)_apkmirror.com.apk

then I get this error:

C:\platform-tools>adb install "eu.chainfire.supersu_2.82-SR5-282_minAPI9(nodpi)_apkmirror.com.apk"

Performing Push Install

eu.chainfire.supersu_2.82-SR5-282_minAPI9(nodpi)_apkmirror...ile pushed, 0 skipped. 13.5 MB/s (6352731 bytes in 0.448s)

pkg: /data/local/tmp/eu.chainfire.supersu_2.82-SR5-282_minAPI9(nodpi)_apkmirror.com.apk

Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]

Would anyone know how to fix this? I can see the icon on the tablet but if start the program it just crashes back to the main "window".

Thank you for your help!

KR

Rok
[Fire HD 8 and HD 10 Original Android Development] pascal009:
Hi,

What exactly did you use to root your tablet? Judging by the piece of the code above

shell@suez:/ $ su

root@suez:/ #

your device already have the SU access. What was the point of installing SuperSU?

BTW, did you go through all the necessary steps described at the top of this thread?

pascal009
[Fire HD 8 and HD 10 Original Android Development] fasnis:
Has anyone managed to unlock/root Hd 10 2017 with Fire OS 5.7.0?
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
Scroll up to the May 20th post I made, its all there.
[Fire HD 8 and HD 10 Original Android Development] pascal009:
I also did it with HD 10 7th Gen running 5.7.0.0 back in April, I think...
[Fire HD 8 and HD 10 Original Android Development] ryny24:
I'm going nuts opening my tablet several times. Do you guys update TWRP from 3.2.3-0 as included in this binary to the latest available in the LOS thread version 3.6.1-9.2?

The TWRP 3.2.3 seems to have a problem with USB storage for me. I've tried many many sticks, none work. I did an ADB PUSH with the suez twrp 3.6.1 and did an update in TWRP, but this completely corrupts my recovery and I have to unbrick again to get back.

If you don't update TWRP, how can you load the OS images without USB?

Thank you.
[Fire HD 8 and HD 10 Original Android Development] cellist:
Did you try to "adb sideload" the OS image, so you transfer it via cable instead of using an USB storage device?
[Fire HD 8 and HD 10 Original Android Development] ryny24:
Yes, that is how I installed LOS 12. But I typically like to install the latest TWRP and use USB, leaving sideload as a last resort. I assume I can't do that on this device. :/
[Fire HD 8 and HD 10 Original Android Development] nathanzachary:
Well, I bricked my tablet and can't seem to get anything to display on the screen any longer. I would greatly appreciate some help. When I plug it in, it shows up in lsusb:

$ lsusb | grep MT6227
Bus 007 Device 046: ID 0e8d:0003 MediaTek Inc. MT6227 phone

but it doesn't stay that way indefinitely, and eventually disappears with dmesg showing the disconnect:

[1755854.330741] usb 7-3: new full-speed USB device number 46 using xhci_hcd
[1755854.464885] usb 7-3: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[1755854.464889] usb 7-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[1755894.040452] usb 7-3: USB disconnect, device number 46

I have tried the bootrom-step.sh script, but it just hangs at 'Waiting for bootrom' and never displays anything else.

I was running 5.7.0.0, and used the instructions to get SuperSU installed (by using adb to install the APK). I then ran the 'step-1.sh', confirmed that I wanted to brick the device by typing 'YES' , but alas, that's when I got the black screen, and I tried to continue with the 'bootrom-step-minimal.sh' but didn't get any sign of life. :(

Thank you preemptively for your help.

EDIT: I think that the device is bootlooping as lsusb shows the device for ~40 seconds, then it goes away and takes ~24 seconds to come back. That cycle repeats endlessly when the device is plugged in via USB.
[Fire HD 8 and HD 10 Original Android Development] pascal009:
It looks you have to remove the back cover to disconnect the battery before executing "sudo ./bootrom-step-minimal.sh".

See my post https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/page-75#post-86690371 and the 2 following posts...
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
I have two kinds of these Fire tablets, the 7 inch ones and the 10 inch one.

On the 7 inch ones I would have to take the back off and ground out the clk pin I think it was while executing the script, you need 3 hands. Anyway I managed to do those fine.

The 10 inch ones I realized you don't, you run the Waiting for bootrom command, and literally hold the power button down on the tablet for a good 5-10 seconds and the command starts running. No need to take the back off, plus I think on the 10 inch tablets there are ground shields around everything makes it really messy unless you can hot air them off or something.

Try just holding the power button on the 10 inch tab, while the script on the shell says "waiting for boot rom" I think a lot of these guides could possibly use some extra verbiage when it comes to how to's but that's just me.

Good luck, hopefully that's all it is.
[Fire HD 8 and HD 10 Original Android Development] pascal009:
Thank you for suggesting an alternative to opening the case (a very difficult and prone to damaging something step for me).

I have another Fire HD 10 (7th Gen) I plan on working on. I will try your advice when I do.
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
Sure sure, good luck.
[Fire HD 8 and HD 10 Original Android Development] nathanzachary:
Thank you for those details. Unfortunately, I still didn't get anything when trying to run bootrom.sh. It just hangs at "Waiting for bootrom". I'm open to any alternative suggestions, and thank you again for your help.
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Short the special point, connect usb (without running scripts) and check lsusb while keeping the short...

If you get a rock-stable mtk phone message as long as you keep the short, then the bootrom-step should work fine. If you see preloader, the short wasn't steady. If you get just nothing, i.e. no message at all while shorted, you may got a device with a patched bootrom, i.e. =unbrickable.
[Fire HD 8 and HD 10 Original Android Development] AlexForTheWin:
Is Lineage 16 too big for Suez?

I was able to flash Lineage 14 + Android 7 Gapps just fine.

But Lineage 16 + Android 9 Gapps gives an insufficient space error.

I think I've removed all the amazon bloat... wiped the system partition from TWRP. Don't see any amazon packages installed anymore.

Is there something I'm missing? Is there a smaller android 9 OS that's compatible?
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
Check out the last post here

https://xdaforums.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/page-31#post-87114469

keep lots of tabs open! :)
[Fire HD 8 and HD 10 Original Android Development] AlexForTheWin:
Just what I'm looking for! Thank you!
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
You bet, Perhaps the actual guide should be updated?? everyone likes flowcharts. Generally speaking, if I try a guide and struggle with it, I could rewrite it so other people don't struggle.
[Fire HD 8 and HD 10 Original Android Development] AlexForTheWin:
Installing an OS might be out of the scope of the original guide. I think it'd be best to create another thread and ask k4y0z to link it.
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
Sure! I think if I understood his question it was more of a , combining the new rooting method with the existing guide. But not to the point of installing an additional OS, however I mean technically ADB sideloading something after TWRP installed is a one liner so ... I guess I wouldn't exactly see it as being that out of scope.

In my professional job, I have to explain technical things a lot to non technical people so it helps to be a little more verbose in the writing to help eliminate a lot of back and forth people might have. Writing is free and there typically isn't a word limit while explaining things to people.
[Fire HD 8 and HD 10 Original Android Development] cellist:
Worked like a charm for me yesterday ;-) - been on 5.7.0.0 as well.

No need to install SuperSU, it is okay just to have su-state confirmed,

then go on and repeat "sudo ./step-1.sh" etc.
[Fire HD 8 and HD 10 Original Android Development] rb2k:
Btw, since a few people had the same "RuntimeError: read fail" issue when bootrom-step-minimal tries to check the GPT: At least for me that read was just a bit flaky and I was able to add a retry to successfully move on. Some details over here:

https://xdaforums.com/t/2017-fire-hd-10-unbricking-from-anti-rollback.3896616/page-7#post-87190855

Oddly I retried about 15-20 times before, so it seemed to be relatively consistent.
[Fire HD 8 and HD 10 Original Android Development] jmandawg:
How did you root 5.7.0.0?
[Fire HD 8 and HD 10 Original Android Development] cellist:
Apologies for the delayed reply ... you can check retyre's post for the process from step 1 to step 9 (confirming root access), alternatively you could also check the slightly more elaborate write-up here. After that I was able to continue with ./step-1.sh, bricking, getting into hacked fastboot mode and so forth.
[Fire HD 8 and HD 10 Original Android Development] drakulaboy:
hi, after i bricked the tablet with wrong firmware i dissasembled it and followed the unbrick tutorial then flashed this https://xdaforums.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/

flashed Magisk-v22.0

and MindTheGapps-9.0.0-arm64-20180809_192137.zip for Google Apps
[Fire HD 8 and HD 10 Original Android Development] Flash1993:
This might be a dumb question but I am new to this. How do you verify your root with this procedure? Should I be seeing something on Magisk app?

NEVERMIND! I downloaded SuperSU Root Checker from the Google Play Store and I am rooted. THANK GOD!

But am I able to update to the most current FireOS without Bricking my device?
[Fire HD 8 and HD 10 Original Android Development] pascal009:
If you are talking specifically about Fire HD 10 Gen 7 (suez) the answer is yes. You can update your device to the latest FireOS version available for it, 5.7.0.0, by flashing the .bin (renamed to .zip) via TWRP. I did it on my 2 suez tablets without a hiss.

With any other device it depends on many variables. You'd have to research it or you can brick your device.
[Fire HD 8 and HD 10 Original Android Development] Flash1993:
Awesome, thank you! Do you by chance know why I have issues with installing Magisk Modules? It says its a invalid zip file.
[Fire HD 8 and HD 10 Original Android Development] pascal009:
Did you per chance check the "Zip Signature Verification" checkbox before flashing? I had a problem flashing the genuine Magisk itself (not the modules) with that checkbox checked.
[Fire HD 8 and HD 10 Original Android Development] Flash1993:
Is it supposed to be checked when flashing Magisk with TWRP or no?
[Fire HD 8 and HD 10 Original Android Development] pascal009:
It is obviously a safety measure to protect against zips tampered with. You decide to check if you want to be cautious.

My point was it complained even with the authentic Magisk. Magisk flashed nicely after I unchecked the box.
[Fire HD 8 and HD 10 Original Android Development] Flash1993:
Could the file for Magisk be in the wrong folder? I ran it from my downloads folder in TWRP.
[Fire HD 8 and HD 10 Original Android Development] pascal009:
For all I know the recommended locations are "/" or the root of SD Card, but I don't think there is a mandatory location for the zips.
[Fire HD 8 and HD 10 Original Android Development] frankynerd:
hey there. i have bricked my hd 10 suez while installing lineageos from this thread

[ROM][testing][suez] Lineage-16.0 [05 JULY 2022]

Disclaimer /* * I am not responsible for bricked devices, dead SD cards, thermonuclear war, * or you getting fired because the alarm app failed. * Please do some research if you have any concerns about features included * in the products you find...

xdaforums.com

i was able to enter hacked fastboot and installing twrp. installing the rom was successful too.

and i think from that point everything did go wrong.

for installing opengapps pico i had to use the cleaning script from this thread.

https://xdaforums.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/page-34#post-87282103

after that i could install the gapps pico.

after reboot i stuck in a boot loop at the amazon logo. no chance to enter fastboot or adb, just preloader. gpt was damaged and i was able to repair via bootrom-step.sh.

here i post lusb, first without and secend with testpoint.

without: Bus 002 Device 003: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader

with testpin: Bus 007 Device 002: ID 0e8d:0003 MediaTek Inc. MT6227 phone

please can anyone help me restoring this device?
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Thats fine. (y)

Short the tablet and do the OPs unlock again. As soon as twrp comes up, 'format' data, wipe cache and install whatever rom you like. I would skip flashing gapps until you know that the tablet boots fine with lineageOS.
[Fire HD 8 and HD 10 Original Android Development] frankynerd:
OMG it is alive again!!! thank you @Sus_i

LOS 16 is running with play store out of the box.

again. THANK YOU!
[Fire HD 8 and HD 10 Original Android Development] blue-screen:
Lineage 16 is big and I could not add gapps until I resized the system partition with the semi-scary open-heart surgery:

https://xdaforums.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/post-87269729

Even when I did that, TWRP formats the partition to the smaller size when wiping and installing, don't know why. You have to resize2fs the system partition after the Lineage install and before the gapps install. I don't know if this is a TWRP issue of if the Lineage image has a fixed size (I assume the latter)

So, after you resize the partition, wiple the cache and user data (reformat), install Lineage with TWRP, and then

resize2fs /dev/block/mmcblk0p13

(It may ask you to run e2fsck first - I did it before and after.)

Once the installed image is resized to fill the partition, you can add gapps.

A less scary approach: use the script in this post to debloat the image:

https://xdaforums.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/post-87282103

I never understood why the system partition was so small.
[Fire HD 8 and HD 10 Original Android Development] Flash1993:
Is it necessary to downgrade my device if I am using this guide to root:

3ch01c.github.io/how-to-setup-amazon-fire-hd10.md at master · 3ch01c/3ch01c.github.io

Tools and guides for doing software development, data analytics, online privacy, and other things. - 3ch01c.github.io/how-to-setup-amazon-fire-hd10.md at master · 3ch01c/3ch01c.github.io

github.com

and then use this one to finish things? I ask because I can't get my device to downgrade.

FIGURED IT OUT ONCE AGAIN AFTER POSTING IN THIS THREAD!! I am now on 5.6.4.0.
[Fire HD 8 and HD 10 Original Android Development] PowSniffer0110:
How did you figure out how to downgrade? I just pulled mine out the box and its on 5.6.9.0

It wants to install 5.7.0.0 but I am not allowing it and keeping Wi-Fi off until I can figure it out.

Also, is there a way to do this process thru windows, and not a Linux environment? I cant find my other laptop with linux on it! HELP! Lol
[Fire HD 8 and HD 10 Original Android Development] Flash1993:
Scroll to the bottom of the linked guide.
[Fire HD 8 and HD 10 Original Android Development] jpage4500:
I spent a while getting everything to work and I think I'm 99% there.. I had to open up the tablet which was the hardest part but my tablet is now booting into TWRP!

However, no matter what I do, I'm unable to load a new OS. I've tried lineage 12 and 14 from the threads here and they seem to install just fine. But, when the tablet reboots it always goes into recovery mode (TWRP).

Has anyone else had a similar problem? I did make sure I did an advanced wipe, factory reset, etc. I tried several different combinations there. I also tried with and without gaaps - just trying to get an OS working at this point!

I know I'm close and maybe this question belongs more in one of the lineage threads.. but, I feel like there's something else that I'm missing which this thread's users would know

thanks!
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
You did a 'format data' ?
[Fire HD 8 and HD 10 Original Android Development] jpage4500:
Yep, just tried it again as well. I had to re-upload lineage 14 to /sdcard and then installed it which went well.

Then, a system reboot and it goes back to the TWRP screen again.
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Thats a bit odd. Cache is wiped too, isn't it?

Take a look into the twrp log, maybe you see something in it...
[Fire HD 8 and HD 10 Original Android Development] psi78:
Besides wiping the partitions and formatting data, you could also try to repair all possible partitions (Cache, System, Data) in TWRP before installing anything: Wipe - Advanced Wipe - Select Partition - Repair or Change File System - Repair File System

File system should be ext4
[Fire HD 8 and HD 10 Original Android Development] jpage4500:
FWIW I figured this out and wanted to post an update just in case it happens to someone else. I noticed the volume buttons appeared stuck. Turns out when i put the tablet back together I must have mis-aligned something so pressure was being put on the volume buttons at all time -- which forced TWRP to start on boot

Once I removed the case LineageOS booted just fine!!
[Fire HD 8 and HD 10 Original Android Development] spikked27:
I have an HD8 (douglas) with LineageOS 14.1 installed but have lost TWRP, when rebooting into recovery the tablet just restarts all the way to the home screen, when trying to fastboot flash twrp again I get a message that it can't be done on locked HW, assumed I had lost unlock so I tried to use this tool but get the message that it only works on "douglas" and I'm "cm_douglas" which comes from LineageOS. Any idea how I can get twrp back??? Appreciate any help!
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Maybe better if you ask in the douglas unlock thread...

https://xdaforums.com/t/unlock-root...-8-2017-douglas.3962846/page-39#post-87512599

Anyways, you can try the boot_fastboot script from amonet folder (run with sudo and connect the tablet in powered off state) and if you get into 'hacked fastboot mode' flash the twrp image... You can also do the unlock again.
[Fire HD 8 and HD 10 Original Android Development] ProjectRoot:
What you need:

A Linux installation or live-system

Where to get that? its not included in the guide
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
GitHub - amonet-kamakiri/fireiso: ISO with patched kernel for kamakiri and amonet

ISO with patched kernel for kamakiri and amonet. Contribute to amonet-kamakiri/fireiso development by creating an account on GitHub.

github.com

Use rufus to flash it to an usb storage stick.

Rufus - Create bootable USB drives the easy way

Rufus: Create bootable USB drives the easy way

rufus.ie
[Fire HD 8 and HD 10 Original Android Development] ProjectRoot:
i found out that the flashdrive malfunctions and cant properly copy the files, thanks for trying, i dont have another one and unfortunately cant afford another one either
[Fire HD 8 and HD 10 Original Android Development] nowaranowara2006:
My naim is nowara
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
You can do the same (without an usb storage) in a virtual machine, like VMware, just a few downloads and then boot the live iso image in the VM. Though it's a bit harder to connect the device, since you will need to choose if the device connects to the guest or the host system, but it will work too.
[Fire HD 8 and HD 10 Original Android Development] ProjectRoot:
I didnt found the software you mentioned but i found another, called Oracle VM Virtual Box, i will give it a try
[Fire HD 8 and HD 10 Original Android Development] ProjectRoot:
sorry for double post, yes it kinda works but no idea which version of linux to install, theres tons of options, i tried the fireiso part, but the sudo apt, gives errors saying no apt command and stuff like that.....
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Go to Linux Mint at https://linuxmint.com/ download it & burn it to a USB memory stick, then boot your laptop from the USB memory stick & run it as a Live/demo *without* installing it to your laptop.

Last time I tried, Ubuntu wasn't suitable (can't recall the reason) but Linux Mint worked perfectly for the job.

(And VirtualBox is far simpler to use than VMWare)
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Fire ISO terminal runs already as root and there is no need to run the apt command, because the fire ISO is set-up for amonet, i.e. ready to use...
[Fire HD 8 and HD 10 Original Android Development] kovren:
I rooted my Suez (or so I thought), tried to install Magisk, and it got stuck in a bootloop. I can access Amazon recovery.

When I try to run the bootrom scripts,

I get the "Serial protocol mismatch" error,

which I assume is from my Fire OS version not being downgraded properly.

I was on Fire OS 5.7.0.0.

Can I adb sideload the 5.7.0.0 update to kinda reset all of this? I tried searching for this update, but 5.6.2.0 or so was the highest I could find. Amazon itself only has up to 5.3.7.3.

At a bit of a loss.

Edited:

Per psi78's comment, I decided to go ahead and just flash the newest firmware on Amazon's webpage. It worked fine. Was then able to reroot and follow this guide to get TWRP installed. Thanks.
[Fire HD 8 and HD 10 Original Android Development] psi78:
Amazon mixed up the version numbers, 5.3.7.3 is actually the newest FireOS for suez, 5.6.2.0 is an older version. So you could adb sideload 5.6.2.0 and root then i think.