yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
I am having issues getting it to turn off from within the os atm

I reflashed the rom not sure what the problem is

edit ok so reboot -p works

must be a rom issue
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Going to try tomorrow, but I managed at one point to get an error asking about gpt again. So I went back and did the steps form your gpt fix and it started with the same can't read emmc errors again.
[Fire HD 8 and HD 10 Original Android Development] Big-A-513:
yes use this guide..... https://xdaforums.com/hd8-hd10/general/xposed-framework-fire-hd-8-6th-t3549043...

i have version 89 installed on my Fire HD 10
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I don't follow you :confused:

You have TWRP, so what's the issue?
[Fire HD 8 and HD 10 Original Android Development] freealta:
I have 5.6.4.0, after answer YES and bricking it, I disconnected the tablet, ran sudo ./bootrom-step-minimal.sh, I plugged it in when it say "Waiting for bootrom", it just sit there, nothing moving.

Update: After repeated unplug and plug, nothing moving. I pressed the power button for a while and it continued.
[Fire HD 8 and HD 10 Original Android Development] cuilidh:
I think the restore from TWRP might have removed TWRP. (I wasn't sure what option to pick).

I guess I don't know what I'm supposed to do afterward.

What do I tell TWRP to do once its in? After that, do I go through step 2?

I'm pretty new to android, not making judgment.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
What exactly did you restore?!

Can you not access TWRP via the button-combination (right Vol-Button + Power)?

That depends on what you want to do...

If you want root, you probably want to install Magisk.
[Fire HD 8 and HD 10 Original Android Development] cuilidh:
I would like root, sure. How can I verify that the restore didnt remove TWRP? It doesn't show up when I reboot.
[Fire HD 8 and HD 10 Original Android Development] cuilidh:
Ok, did magisk and the magisk app manager, but when I do the validation it sayts "ctsProfile: false" in the SafetyNet Check Success. basicIntegrity is true.

I have set "presence force encryption". Anything else I should do?

I did try to follow the instructions in the magisk specific forum, but I guess the props command isn't available for magisck v18.1, only v19+
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
I don't think it's going to pass ctsProfile regardless. Unless you're using banking apps on this tablet, it shouldn't matter.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
There's an Xposed module called 'no device check'. And it still worked so far as I know
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
ctsprofile is from running selinux in permissive

ignore it
[Fire HD 8 and HD 10 Original Android Development] freealta:
Use the pendrivelinux's UUI suggested earlier by sga to easily create a ubuntu persistent usb, ran the scripts including brick and downgrade. Except for the hiccup after bricking, everything worked fine. Installed Magisk, google play store, then Nova as a system app, Titanium to freeze all the Amazon stuff. This tablet is now fantastic all for $100 that I bought last week. Thank you for putting all this together!
[Fire HD 8 and HD 10 Original Android Development] cuilidh:
Where did you get titanium? From the play store, or some apk repo?
[Fire HD 8 and HD 10 Original Android Development] tylerhole:
It's Titanium Backup and it's in the play store.

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Original Android Development] Zöllner-à-Beckett:
Help restore Stock/root-modded-stock FireOS on HD 10 [2017]

I reflashed the stock FireOS 5.6.0.1 [think that was the version I had before rooting] using TWRP; tablet still can't boot into FireOS:

Tablet is stuck on the amazon logo

fire logo doesn't show and the tablet doesn't boot into FireOS

I can always power off or boot into recovery/TWRP

The stock firmware I got was from [TUT] ROOT HD10 (2017), HD8(2016-2017) - EASY SuperSu; it's listed on the 2nd post.

Now, what happened that I need to restore the stock firmware? Well, the following:

Used ubuntu 19.what-ever-is-the-latest installed in a VM to root the tablet

Used suez by k4y0z; the whole process went without a hitch

Thank you k4y0z!

[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 10 2017 (suez)

Installed various apps in preparation for uninstalling most amazon app on the tablet [including google, play store & even a launcher]

From the ubuntu VM I typed adb shell, then su whoami

Welp, got an error; su was missing

Checked bin & sbin folders, and lo & behold, su is missing

At this point I also realized that SuperSU also wasn't installed & apps were running with root whenever they damned well please

Booted into TWRP & flashed SuperSU APK

Then the bootloops [stuck on the FireOS logo] started

After several restart & the same, I booted into TWRP again and wiped cache & DALVIK

But still the same bootloops

Booted into TWRP again, and this time wiped cache, DALVIK, Data & Internal [WOOPS!]

Please give me a break; haven't had to use TWRP/rooting in some 4+ years now, so I forgot quite a lot of stuff

Tried to flash rooted & modded stock 5.6.0.1, TWRP doesn't even recognize the image, so can't flash

Flashed stock 5.6.0.1 using TWRP by renaming the bin to zip

Now the FireOS logo doesn't even show up! It's just stuck at the amazon logo, but I can still get into TWRP
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Edit the updater script. remove all the lines that flash anything aside from the system. Reflash it and reboot. When you're back up and running then run the return to stock script. If you load anything lower than the last version of FireOS, not the one we got a few days ago, then you'll brick it every time. if you want to downgrade again you will have to edit the script and remove all the lines that flash anything aside from the system.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Why post the same long message in two threads?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Why do you keep giving that advice?

Modifying the scripts is not necessary on suez. (And If you modify, boot.img and system belong together)

Just rename the current update-bin to zip and flash it with TWRP-

Also if you want to keep TWRP, don't use the return-to-stock script.

[MENTION=4113171]Zöllner-à-Beckett[/MENTION] also use Magisk not SuperSU!
[Fire HD 8 and HD 10 Original Android Development] Zöllner-à-Beckett:
Help restore Stock/root-modded-stock FireOS on HD 10 [2017]

[MENTION=8165603]DragonFire1024[/MENTION] & [MENTION=7104332]k4y0z[/MENTION]

I did just that & it still didn't work [stuck at the white amazon logo].

As mentioned in my last post, I renamed 5601-update-kindle-40.5.9.5_user_595550320.bin to 5601-update.zip, then flashed with TWRP. Flash was successful, but fireos logo doesn't show & doesn't boot into the OS either.

Matter of fact, after reading your post [& before making this post], I booted into TWRP, wiped all the partitions [including data & internal], then re-flashed the stock 5.6.0.1 again [this was the 4th time I've tried this]. After reboot, tablet was again stuck at the white amazon logo. I left it on for about an hour, then turned it off [as it didn't boot into the fireOS; heck, didn't even show the fire logo].

Is there another way to install the stock firmware?

[MENTION=1464372]GuyInDogSuit[/MENTION] sorry, didn't know which thread was appropriate for my post.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
As said, install the current firmware. 5.6.0.1. is old. The current version is 5.6.4.0 aka 5.3.6.8 you can get it here:

https://fireos-tablet-src.s3.amazon...oGA/update-kindle-40.6.3.6_user_636558520.bin
[Fire HD 8 and HD 10 Original Android Development] Shadow Death:
Also try flashing Magisk instead of SuperSU. I recall with SuperSU you have to set it's default actions to grant but with Magisk you don't have to.
[Fire HD 8 and HD 10 Original Android Development] gortkrael:
Didn't Brick It BUT No Root

Second Post to Your [UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 10 2017 (suez)

Spent time learning VirtualBox and Ubuntu 18.04. I extracted the "amonet-suez-v1.1.2.zip in a directory call "fire". Confirmed ADB recognized my tablet with "adb devices" then ran the first script.

Tablet rebooted into recovery and performed a factory reset.

Here is where I got off in the weeds apparently. No doubt my ignorance but I extracted the "mtk-su_r11.zip" placing the "arm64" into "amonet/bin" and ran "sudo ./step-2.sh" since the instructions for the file stated "The arm64 one is suitable for most devices. The notable device that needs the arm version is the Fire HD 8 2018. The armv7-kernel version is for 32-bit kernels (on 64-bit HW)."

Well the exploit did flash and TWRP did come up. I am very familiar with TWRP and initiated a backup as my first activity. Strangely when I ran a "SuperSU" root check it gave the congratulations message and I thought awesome! Then I tried to install Titanium Pro and got the message that Titanium Pro didn't see root. Blew my mind.

On reflection I should have run a APK like "Sys Info" off Google Play to check my architecture which shows "armeabi-v7a". So now I am thinking I should have used "armv7-kernel" "mtk-su".

Processor Model Name = AArch64 Processor rev 0 (aarch64).

So, I have TWRP installed and all is working well backups, reboot, etc., but no root. I am hesitant to do anything else fearing I'll brick the darn tablet. My tablet is not registered with Amazon. Google Play is installed so the only updates I am receiving are from Google.

Any comments would be greatly appreciated. Your work is sound since others have been very successful, I screwed up somehow.

Respectfully
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
You need to flash Magisk. Remove SuperSU and install Magisk. Either version should work, but I've found only 19 will stick.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Ok so I can get the tablet to boot at the white amazon logo after I run bootrom-step-minimal. For it to work I made sure the screen cable was snug. when it asked I used the brick option to hit enter. Before I did this, I plugged the battery in quickly and hit enter. It goes through the process and asks to reboot to hacked fastboot (fastboot-step.sh) and all goes well and the screen turns on to white amazon logo. No text to say it was in hacked fb mode. After about 20 seconds or more it bootloops back to the white logo.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Is this the brick you are talking about?

Use bootrom-step.sh not bootrom-step-minimal.sh
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I will try the same way I did to get minimal step to work. It was the only way I could get past read emmc fail.
[Fire HD 8 and HD 10 Original Android Development] waternotwords:
These directions no longer work. It looks like even though mtk-su appears to be successful ("New UID/GID: 0/0" is output to the console), the script continues to call mtk-su so that "New UID/GID: 0/0" is output to the console on a continuous loop. Virgin Fire HD 10 (Fire OS 5.6.1.0 first boot, never connected to the internet).
[Fire HD 8 and HD 10 Original Android Development] DB126:
Carefully reread OP and look through some of the more creditable/detailed posts in this thread. Likely find the answer there. Alternatively, look through this thread: https://xdaforums.com/hd8-hd10/orig-development/experimental-software-root-hd-8-hd-10-t3904595
[Fire HD 8 and HD 10 Original Android Development] :
I have not tried this yet, but I have a few questions

Will this work on 5.3.6.4 (version in settings)?

Also I am currently rooted already with supersu and have a lot of mods on /system. Does the reset revert all changes to /system and will it get rid of supersu? How would I get this to work ie reset tablet, then how do I remove supersu to install magisk?
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
you used the wrong mtk-su binary

the hd 10 is 64bit (arm64)

or didn't put the mtksu in the right folder
[Fire HD 8 and HD 10 Original Android Development] diplomatic:
No, that's not it. Both flavors work on that tablet. Especially if it gives you '0/0', then it's all good. Probably just some random glitch with the script. Just quit and try it again.

No, the exploit will not change your system partition since it doesn't require you to download and install the stock firmware. You can install Magisk through TWRP from what I've been told. It may remove SuperSU automatically. Or you can do a full unroot through the SuperSU app.
[Fire HD 8 and HD 10 Original Android Development] :
Thank you. Would it be a good idea to uninstall all root apps before? Since i have viper4android i should probably remove that.

Also does the reset remove root too? And is it better to use the option in supersu to 'switch to another root manager'

Just for clarification in step 3, the bricking bit, how would.we do the bootrom-step-minimal.sh when our tablet is unplugged?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
So if I perform bootrom-step, I can't get it to read emmc, even if I am really quick with plugging in the battery. I've tried other cables and ports and same results. For bootrom-step-minimal, it goes through the while process but will not reboot to fastboot. Just the white amazon logo. Then it will bootloop. Also can't boot to recovery.
[Fire HD 8 and HD 10 Original Android Development] skymera:
My tab has never been updated from 5.6.2.0 but I can't get past the below. I've completed step 1

[root@scott-desktop amonet]# ./bootrom-step-minimal.sh
[2019-04-27 18:15:45.982170] Waiting for bootrom
[2019-04-27 18:15:50.776723] Found port = /dev/ttyACM0
[2019-04-27 18:15:50.815705] Handshake
[2019-04-27 18:15:50.836568] Disable watchdog
b''
b'\x00\x01'
Traceback (most recent call last):
File "main.py", line 192, in <module>
main()
File "main.py", line 82, in main
handshake(dev)
File "/home/scott/Downloads/amonet/modules/handshake.py", line 11, in handshake
dev.write32(0x10007000, 0x22000000)
File "/home/scott/Downloads/amonet/modules/common.py", line 163, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/home/scott/Downloads/amonet/modules/common.py", line 90, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch
[root@scott-desktop amonet]#

EDIT

Nevermind, I just skipped to sudo ./step-2.sh and it worked. TWRP flashed and booted up.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Someone send me or upload build.prop for hd 10 on 5.6.1.0
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
extract it from your rom zip

lmao
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I would if I were able. Not at home right now and don't have a way to extract the .dat
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
A tool I use didn't do it's job right. Instead of adding my edits, it deleted the whole thing. If I rebooted, I'd be done till I got home.
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
.Dumping GPT
tmp-mksh: dd if=/dev/block/mmcblk0 bs=512 count=34 of=/data/local/tmp/gpt.bin: not found
tmp-mksh: chmod 644 /data/local/tmp/gpt.bin: not found
remote object '/data/local/tmp/gpt.bin' does not exist
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Make sure you're in the right directory.
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
BTW this is first script and im in the right directory, I whats crazy is now I cant even get ADB to find my device after running the script a few times.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Looks, like there is an issue with the root-solution (SuperSU?) you currently have installed.

Try unrooting/restoring stock and then try again.

Or try setting up SuperSU to grant all.
[Fire HD 8 and HD 10 Original Android Development] :
Would it be a good idea to uninstall all root apps before? Since i have viper4android i should probably remove that.

Also does the reset remove root too? And is it better to use the option in supersu to 'switch to another root manager' or 'full unroot' before switching to magisk? Also should I uninstall xposed framework and its mods?

Just for clarification in step 3, the bricking bit, how would.we do the bootrom-step-minimal.sh when our tablet is unplugged?
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
So in order to go back to goold old stock, i need to have the hacked boot loader, correct? So I should start with bootrom-step-minimal, etc?
[Fire HD 8 and HD 10 Original Android Development] tylerhole:
Just go into twrp, go to the second page of the main menu and choose hacked fastboot then run return-to-stock.sh

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
I dont have Twrp
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
then your fked

hold vol up while booting until it says recovery in the lower left corner
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
I can not for the life of me get ubuntu/adb to read my device, tried kill and start server command... no luck. I had unrooted and then side loaded the version on amazons web site. Windows can read it on adb and stock just fine. What the flip man oh and i re rooted via the guide
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
try a 2.0 port if you have one
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
no go on that,
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Google 'udev' and '51-android.rules'. you need to add the vendor and product IDs of the tablet into that file if it exists, or create it if it doesn't.
[Fire HD 8 and HD 10 Original Android Development] tylerhole:
Or if that doesn't work try running adb kill-server and adb start-server with sudo. You have both android-tools-adb and android-tools-fastboot installed?

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
niko@ubuntu:~/HD10/amonet$ sudo ./step-1.sh

[sudo] password for niko:

Testing root access...

uid=0(root) gid=0(root) context=u:r:init:s0

PL version: 5 (5)

LK version: 3 (2)

TZ version: 264 (263)

TZ, Preloader or LK are too new, RPMB downgrade necessary (or brick option used)

Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)

YES

Bricking preloader

/system/bin/sh: can't create /sys/block/mmcblk0boot0/force_ro": Permission denied

tmp-mksh: dd if=/dev/zero of=/dev/block/mmcblk0boot0 bs=512 count=8: not found

/system/bin/sh: can't create /dev/block/mmcblk0boot0": Permission denied

Flashing LK

815 KB/s (407012 bytes in 0.487s)

tmp-mksh: dd if=/data/local/tmp/lk.bin of=/dev/block/platform/soc/by-name/lk bs=512: not found

Flashing TZ

929 KB/s (3559424 bytes in 3.738s)

tmp-mksh: dd if=/data/local/tmp/tz.img of=/dev/block/platform/soc/by-name/tee1 bs=512: not found

tmp-mksh: dd if=/data/local/tmp/tz.img of=/dev/block/platform/soc/by-name/tee2 bs=512: not found
[Fire HD 8 and HD 10 Original Android Development] DB126:
Along with a different cable; fastboot communications are more sensitive to wiring irregularities.
[Fire HD 8 and HD 10 Original Android Development] tylerhole:
Aka a pain in the ass sometimes lol

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
Please need help dont have permission according to output I pasted above/
[Fire HD 8 and HD 10 Original Android Development] tylerhole:
Have you tried everything that has been suggested to you?

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
yes, I was able to gain adb connection with rule 51, now I need to fiure out how to fix my permissions. running on administration, can run a shell or go to the other user name in the sudo group?
[Fire HD 8 and HD 10 Original Android Development] garnet&gold:
It looks like you missed some of the instructions on the op.

NOTE: If you are on firmware 5.6.4.0 or newer, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all).

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.

It will then boot into "hacked fastboot" mode.

Then run

Code:

sudo ./fastboot-step.sh
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
no i did just that, when it reboots to flash brick it cant get to the appropriate files it seems.

---------- Post added at 01:04 AM ---------- Previous post was at 01:02 AM ----------

I stay stuck in limbo waiting for the handshake after running minimal.sh
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
try not using sudo (use "sudo su " and then run the script as root)

switch to root and retry

you also may need to clear the adb key on the device
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
OMG It still doing the same thing, when it reboots to flash it does not flash

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

Can this entire process be ran automatically and turned into a .sh or .bat? Im about to break something. Im getting so frustrated
[Fire HD 8 and HD 10 Original Android Development] DB126:
Step away for a day or two. A fresh perspective may offer insights into what went wrong and how to address/fix the problem.
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
I just need to know from someone here how to fix this:

TZ, Preloader or LK are too new, RPMB downgrade necessary (or brick option used)

Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)

YES

Bricking preloader

/system/bin/sh: can't create /sys/block/mmcblk0boot0/force_ro": Permission denied

tmp-mksh: dd if=/dev/zero of=/dev/block/mmcblk0boot0 bs=512 count=8: not found

/system/bin/sh: can't create /dev/block/mmcblk0boot0": Permission denied

Flashing LK

815 KB/s (407012 bytes in 0.487s)

tmp-mksh: dd if=/data/local/tmp/lk.bin of=/dev/block/platform/soc/by-name/lk bs=512: not found

Flashing TZ

929 KB/s (3559424 bytes in 3.738s)

tmp-mksh: dd if=/data/local/tmp/tz.img of=/dev/block/platform/soc/by-name/tee1 bs=512: not found

tmp-mksh: dd if=/data/local/tmp/tz.img of=/dev/block/platform/soc/by-name/tee2 bs=512: not found
[Fire HD 8 and HD 10 Original Android Development] aleks79:
Trying to run ./step-1.sh and it can't find su

amonet-suez-v1.1.2.zip

mtk-su_r12.zip

$ ./step-1.sh

Testing root access...

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

Pushing root files

9026 KB/s (34560 bytes in 0.003s)

10081 KB/s (1048576 bytes in 0.101s)

10202 KB/s (989184 bytes in 0.094s)

New UID/GID: 0/0

New UID/GID: 0/0

New UID/GID: 0/0

New UID/GID: 0/0

I've changed functions.inc to see what adb shell su returns

adb shell su -c id

adb shell su -c id | grep ": 0"

and see the following

/system/bin/sh: su: not found

Can you please help me to understand what have I missed?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
That looks like an issue with your root-solution.

Try setting it to grant all.

If that doesn't work, try unrooting and using mtk-su.

What does

adb shell /data/local/tmp/mtk-su -c "/data/local/tmp/busybox mount /data/local/tmp/minisu.img /system/xbin/"

return?
[Fire HD 8 and HD 10 Original Android Development] aleks79:
Return code 0

here is the list of /system/xbin

chkufsd

dexdump

iwpriv

mkexfat

showmap

sqlite3

start-ufsd

test_system

trapz

vitals_collection_agent

Tried to mount it to different folder and no success as well. Have all files in /data/local/tmp/