yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
I'm not complaining, disparaging your work or mean any disrespect whatsoever. I'm just trying to be thorough and see if I can make this work. I understand that there will be frustrations and failures along the way. I willingly took the risk that I'd brick my Fire and, if I do, that's on me.

These are the same four steps in the same order listed that I've now done 6 times using the latest version of Magisk and Magisk Manager available at the time and a fresh copy of FireOS 5.3.6.4 that I got directly from Amazon. Each time, Magisk shows that it's installed, but it hasn't installed correctly. When I install Magisk Mgr, it doesn't do the SafetyNet check, some menu choices don't work and modules can't be installed as they all report that /data/magisk wasn't properly installed. The last two times were with Magisk 18.1 and Magisk Manager 7.1. Plus, from a Terminal window, including the one in TWRP, running su or sudo commands report "no such command", using "ls" returns permission denied on most directories, even those with "drwxrwx--x" permissions, and using "rm" returns permission denied for a file I pushed to /data/local/tmp. Finally, when I tried to do a Factory Reset from the Fire Settings last night, it did nothing. Each time I tried, the screen went black for a couple of seconds, then returned to the previous Settings page. These are the reasons that I concluded that something hasn't worked correctly, for whatever reason, and drove my desire to totally restore the Fire to stock before trying it all again.

While researching last night, I ran across something that I hadn't considered. I had a mismatch between the versions of ADB running on my Windows host PC and the one distributed with Ubuntu 18.1. I've corrected it by downgrading ADB on my PC to the same version in Ubuntu. Could this have caused issues such as the ones I'm experiencing ?
[Fire HD 8 and HD 10 Original Android Development] Michajin:
I had the same issue with frakework-res.apk. If i copied it to the directory and overwrote it, it would screw everything up and i had to go flash stock back. I downloaded the manual update from amazon, renamed it from a .bin to a .zip and installed VIA TWRP. I copied my current framework to a different directory then pasted in the modified framework. Everything was crashing during this but after a reboot, gravity (xposed) had full control of the power menu. I would recommend making a backup with twrp if you are modifying.
[Fire HD 8 and HD 10 Original Android Development] Wall.swe:
I used Ubuntu since I'm a total Linux newbie ?

---------- Post added at 05:51 PM ---------- Previous post was at 05:47 PM ----------

I'm glad that I could be helpful!

I used Ubuntu since I'm a Linux newbie ?
[Fire HD 8 and HD 10 Original Android Development] frankieuk:
Same, im shocked how easy it was!! thankful for the guide!.
[Fire HD 8 and HD 10 Original Android Development] Yamaraj:
k4y0z,

Thank you for this wonderful work. Working perfectly on Fire HD 10.

However, there is a problem with another HD 10. It is stuck on the Enter PIN/Password screen after restoring to stock and trying to unlock again. It attempts to factory reset the tablet but nothing happens. Cannot boot into stock recovery either. I would appreciate any help.

Steps:

1. Rooted Fire HD 10 with mtk-su

2. unlocked it successfully

3. Needed to return to stock for some reason

4. Notice the error in bold. Everything else seemed fine until now.

5. Then onto unlocking it again...

6. Now it boots into the Enter PIN/Password screen. Enter anything and it says "Corrupt Encryption." The pin/password you have entered is correct, but unfortunately your data is corrupt....blah blah.

7. Factory Reset button boots into the same PIN/Password screen. Rinse, wash, repeat.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Couldn't have said it better. I had a really awesome windows setup that I did amazing things with. As all these things progressed, I found it easier and easier to use Linux. It takes some time to learn no doubt, but it does make things a lot easier.

I prefer Kali Linux for more recreational use and research. I'm most familiar with that distribution. Arch is pretty awesome. But if you want to build anything related to Android, Ubuntu is what you need, and I currently use Ubuntu 14.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I didn't take it that way, all good :)

Did you also wipe system?

SafetyNet will not work without google-play services installed.

There is no sudo on android.

su should work when Magisk and MagiskManager is installed.

If you don't get a prompt, check the Superuser tab in MagiskManager.

There is no su in TWRP, as in TWRP you are always root.

I'm not sure, why factory reset doesn't work, that seems to be a bug in FireOS.

That shouldn't be an issue.

I have uploaded a corrected version of return-to-stock.

Try if you can still access adb.

If that doesn't work, I'm afraid you might have to open the device and do the unbrick-procedure.
[Fire HD 8 and HD 10 Original Android Development] cobyman7035:
no toolkit for this tablet? i just got this, so now i have both the 8in and 10inch version...10inch is much snappier and better rez! too bad that toolbox doesn't have autoroot option yet! i dont have linux
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
If rooting the stock firmware with SuperRs Kitchen is as easy for the HD 10 as it was for the Amazon Fire 7, ford, then from here on out every piece of firmware amazon spits out can be rooted using it.
[Fire HD 8 and HD 10 Original Android Development] Yamaraj:
Can't access adb. Trying the short-n-unbrick method, but ...

Ubuntu 18.04.02 LTS in VMware running on Windows 10, system ThinkPad W550s.

UPDATE: unbricked(?); haven't checked yet.

What helped:

Output:

Now a million dollar question is, where do I go from here? GPT says boot_x and recovery_x partitions exist, so what do I do next to get a functional, unlocked system? This is fun, but I would rather not waste any more time on this tablet than I have to.
[Fire HD 8 and HD 10 Original Android Development] Yamaraj:
Latest updates:

1. sudo ./fastboot-step.sh - success, booted into TWRP

2. No /data or /storage found; installed Amazon image from sdcard, /data and /cache errors, partitions not found

3. Rebooted, TWRP bootloops trying to format /cache; power cycled the tablet, successfully booted into FireOS.

4. sudo ./return-to-stock.sh

5. Sideloading Amazon update bin package. Bloody slow. If it's successful, I'm going to unlock it again. Fingers and toes crossed.

6. SUCCESS!

Thanks to [MENTION=7104332]k4y0z[/MENTION] and [MENTION=3497316]retyre[/MENTION]
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Yeah, updating via sideload is a long, slow process.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Glad you got it solved, but why did you to "return-to-stock" AGAIN?

You already had TWRP and were unlocked after doing the unbricking.
[Fire HD 8 and HD 10 Original Android Development] Yamaraj:
Thanks to these:

Magisk wasn't flashing successfully either, so in the spirit of true scientific method I thought of starting from scratch before putting the tablet together. And it worked.

Donated a small amount. Thank you. :)
[Fire HD 8 and HD 10 Original Android Development] DB126:
An increasingly rare mindset; good call (even if there are other workarounds).
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
When I couldn't get either of your restore scripts to work, I decided to carefully perform these four steps again. As per all the other times, everything seemed to work with no errors or other issues although Magisk still wouldn't install modules giving the response that "/data/magisk has not been properly installed". In spite of that, I just kept going as if everything was ok. I blocked OTA updates, installed Google Services and Play Store, blocked Amazon ads, and installed apps that I wanted, including Titanium. I changed the settings in all these apps to my liking and tested them to ensure they were working as they had before I startedg the [Unlock][Root][TWRP] process.

I was able to use all the other features in Magisk, including Titanium showing up in SuperUser, except install modules. I ran the SafetyNet check and found that ctsProfile was failing, so did research on how to mitigate. One of the recommendations was to use the Magisk Hide settings to mark Google apps. Making changes to Magisk settings requires a reboot to make them active, so after making all the changes I needed at the moment, I allowed the reboot. After the system came back up, I opened Magisk Manager to find a red check next to "Magisik is not installed." ! See attached for screenshot (Sorry, I haven't learned how to embed resizable image in text).

I used the Install button which gives me two methods, Download Zip Only and Patch Boot image file. I chose to download and it briefly flashed a line at the bottom showing it was downloading, then another showing where the file was stored. It didn't appear to do the install, so I clicked Install again and it just starts over. I rebooted into TRWP and installed the original file I got from Github without error. After reboot, opened Magisk Manager and it shows Magisk still uninstalled. So this time, I chose the Patch option. The process seems to complete successfully and the Fire reboots. Open Magisk Manager and it shows Magisk still uninstalled. Reboot to TWRP and Install the version from using the Install button and reboot. Open Magisk Manager and it shows Magisk still uninstalled. I've tried every way I can think of to get Magisk to install and get no errors or indications of problems, yet after the reboot it's still not installed.

At this point, this is the only major issue I have after performing [Unlock][Root][TWRP]. I'm out of ideas, where do you suggest I look next ?
[Fire HD 8 and HD 10 Original Android Development] Fr0stbyteX:
Do apps like Netflix, that try to fail with unlocked bootloaders, work with this mod installed? I would love to have TWRP installed, but don't want to lose Netflix.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Netflix works fine on all mine.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Just got home from work. And my fresh, new HD 10 had already arrived, 5.6.1.0 :)

---------- Post added at 06:10 PM ---------- Previous post was at 06:02 PM ----------

Get ready. Changes are coming. First, If this works, every piece of firmware for this tablet is going to get rooted. Second, this software has the potential to eliminate the need to download the entire Android source code to 'build' a rom. Given Google has released a generic system image for every sdk from 19, to I believe oreo, this tool can make porting a rom, a day you can spend walking in a park.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Have you tried uninstalling magisk, using the unistaller zip from TWRP, and deleting the app? I used 18.1 zip and 7.1 app. Not sure if the newer versions had issues.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Have you given time tested/stable/reliable SuperSU 2.82 SR5 a whirl? While Magisk is the only (major) root manager under active development there's something to be said for the maturity of the old guard, especially on Lollipop based ROMs.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I would generally agree with you and understand why you chose this path.

In this case, I want to make it clear though, that since both unlocking and restoring to stock modify the GPT, there is always a small risk of bricking involved..

As long as you have a working TWRP (or root-access via the OS), there is always a better method of recovery.

In this case, it is expected, to have issues with /data after the unbricking, since fastboot-step erases userdata.

Maybe I should make this more clear.

To fix that, you can use the Format Data option in TWRP (although it should fix itself on the first boot)

Thank you, that is very much appreciated :)

As is mentioned in the OP, you should never update/install Magisk through MagiskManager, allways use TWRP for that.

You can still use MagiskManager to download the ZIP (And that's all that chosing the option "Download ZIP Only" in MagiskManager does), but you have to install it manually in TWRP.

The same goes for modules that modify the boot-image, they have to be installed in TWRP.
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
Yes, I had done this before and it worked well. However, I wanted to have an unlocked and rooted tablet along with Netflix and banking apps. I use my tablet as a mini-laptop when traveling and am trying to duplicate that freedom and functionality.

---------- Post added at 08:54 PM ---------- Previous post was at 08:05 PM ----------

Aw nuts, my bad again ! My old brain isn't what it used to be, but I have done all the installs that were in zip files in TWRP with reboots between each. I've tried the Sideload in TWRP, but it also requires the files to be zip. Not too sure what the difference between Install and Sideload are in TWRP.

I ran the uninstall of Magisk in TWRP, rebooted, then ran the install of Magisk 18.1 in TWRP and rebooted. No errors in either. Next, I sideloaded the Magisk Manager 7.1 and just to be safe, rebooted. Opened the Manager, but Magisk is still showing that it's not installed. I had expected this to fix the issue I created by doing the install patch through Magisk. I know Magisk is not your application, but do you know how I can discover what part of it is missing, misconfigured or not running ?

While I'm no stranger to this kind of device modification, I am several decades past my prime. I truly appreciate your patience with helping me get it figured out.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
I think I would factory reset from TWRP and start over, always make a back up with the base system you want installed. Then tweak on things, so then you can go back. I am not sure about the worries about magisk CTS falling. Mine fails and it doesn't prevent any apps from working. I'm a novice and maybe I'm missing something though. It actually sounds you found a way to hide magisk from itself?
[Fire HD 8 and HD 10 Original Android Development] Michajin:
I did update to magisk 7.1.1 and beta 19.0. I had to reboot and it crashed one time. But looks stable now. The wifi wouldn't connect until I rebooted. Looks like it's ok...
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Anyone looking for easy disabling of Amazon apps, I am using package disabler from the play store. Easier than having to do the ADB and computer hookup. Anyone disabling things though need to make sure they have a good back up to fix a screw up. Good luck! Using disable with give you options, uninstall can have issues trying to get it back installed.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
That is back on the store again? I had no idea. Nice!
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
So we can't touch the boot.img? It just needs to be changed altogether? I've read in the HD 8 threads that you can change out the zimage (assuming a compatible other exists) . Are we able to do something similar?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Also the offline rooting and unlock went all the way through on the first shot straight out of the box. Not a single thing went wrong. No errors. The whole process took no more than 20 minutes or so to complete. Honestly I have to say TWRP looks so beautiful on it.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Nice, man. Congrats. Looking forward to seeing what you and k4y0z and co. come up with.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Why would you think that?

You can do what you wan't with the boot-image, since signatures aren't checked.

You only have to make sure they go to the right partitions (boot_x/recovery_x).

Although if you use TWRP, that will take care of it for you.

TWRP uses a self-compiled kernel/zImage BTW (check with uname -a)
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
Yeehaw ! I finally got it all to work and have an unlocked, rooted, stable, fully loaded and very functional tablet thanks to you, topjohnwu and TWRP. Plus, I now have a full backup stored on my removable SD card that can be flashed back into place in less than 4 minutes. To show my appreciation, I've made donations to each of you. Enjoy. :good::good::good:
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Thanks. I misread then. I'm going to link a tool when I get home. I talked to the dev a few weeks ago and sent him a boot img. The tool I was using is windows based, but his tool supports and PROPERLY unpacks and repacks Amazon boot images. I just couldn't understand how to use the tool at the time.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
You don't need any special tools to unpack amazon boot images.

All you need is abootimg

sudo apt install abootimg
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Yes, for unpack you don't need any special tool. If you are in linux use abootimg as k4y0z said and if you are in windows you can use AndIMGTool.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
And what about repacking?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I'm a sucker for tinkering. So I was playing around in TWRP. I like to see what I can't see when things like this change in a device. I was playing in the terminal and ran ps just to see what was running in recovery. Much to my surprise there were a dozen or more processes running. Would this be normal for a device in recovery mode? I'll post a process list when I get home.
[Fire HD 8 and HD 10 Original Android Development] mileyrock:
does this work with hd8 2017?
[Fire HD 8 and HD 10 Original Android Development] tylerhole:
Does you not even read the first 2 sentences of the OP?

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
lawl
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Ok so I've been experimenting all morning. I'm not happy with the results and unfortunately it's not good news.

1) In regards to a rom, port or etc, there is no script issues anymore. But I still cannot successfully flash the system partition...unless it's again, a stock, unmodified amazon.zip. I've tried the SuperR tool which worked magnificently on the fire 7 ford, but on the 10, hangs at the orange fire logo no matter what I do. I have tried a zip with and without unpacking the boot.img. I tried flashing a system.img in fasboot, but that errored out too, though it may have to be a sparse image as it gave me sparse header errors.

2) I have 6 different SuperSU zips available. Not a single one would flash the device...again orange fire logo. Magisk flashes without a problem and everything boots.

3) I hate to say it but I don't think we will get a custom rom unless we totally replace the kernel. Maybe [MENTION=7104332]k4y0z[/MENTION] can debunk this real quick or give some kind of insight...and i really do hope to be wrong on this one. Because now, I'm at a total loss of ideas.

---------- Post added at 04:59 PM ---------- Previous post was at 04:56 PM ----------

Let me try one more thing

---------- Post added at 05:33 PM ---------- Previous post was at 04:59 PM ----------

Sorry [MENTION=7104332]k4y0z[/MENTION] jumped the gun a little. I'm glad I tried my last idea. Look out everyone...pre-rooted, optimized stock rom coming up ;)
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Just trying random things, without doing any debugging what isn't working (adb logcat kernel-log etc) is probably not the quickest process.

Yeah, amazon seems to have messed up fastboot for flashing system, didn't get it working either.

Why even use SuperSU if Magisk works well?

Custom roms should totally be possible, but as said it might require some proper debugging.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Yes, we can flash a ROM but It needs to be compiled from source.

Enviado desde mi SM-G975F mediante Tapatalk
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Got it. Optimized stock ROM posted. I was right. It will only flash .dat. More specifically sparse data. The tool also creates a system.img I presume in the same format (sparse). There are options for others. I have not tried the system.img as I'm getting right to work setting this thing up for now. What a difference a few optimizations make.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Sweet! Reading the thread now!
[Fire HD 8 and HD 10 Original Android Development] Sc4r3Crow:
Any chance flashing rom without linux stuff?
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Read the thread.
[Fire HD 8 and HD 10 Original Android Development] tylerhole:
You. Are. The. Man! Hell yes bro, nice!

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
I linked it a few posts back. Everything seems to work so far, except my home WiFi. Hotspot works though. Let me know how it goes with yours.
[Fire HD 8 and HD 10 Original Android Development] tylerhole:
Firing up my laptop right now to go scope it [emoji106]

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Original Android Development] sgnah:
How can I modify FireHD10-2017 booting logo(Amazon) use other logo.bin

How can I modify FireHD10-2017 booting logo(Amazon) use other logo.bin

I see the Fire HD10 2017 had unlock and root,thanks to suez.

I want to modify FireHD10-2017 booting logo (Amazon and fire logo ). because of root ,I had modify bootanimation.zip to modify fire logo.

but there is not logo.bin in FireHD10-2017's update.zip,How can I modify Amazon fastboot's logo use other logo.bin????thanks anynone tell me.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
First, please don't quote whole OP posts like that.

Second, "suez" is not the developer that came up with this, it was k4y0z and others who helped out (see OP credits). It is the "codename" of this tablet you hold in your hands.

Third, we've only just begun with development on this device. Nothing's been touched in regards to boot splash.... yet. Though now that you've brought it up, I don't doubt that someone could figure out how.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Well mine did work. And then it stopped and didn't work again. I haven't tried anywhere else besides home yet. I have an idea if the issue but I'll have to look at it tomorrow. It can't be a WiFi firmware issue, if it works elsewhere. I wonder if it should be turned on first, like location services when installing the play store. I wonder if wiping the system had an effect on it too. I would say go back to real stock (if you know how to flash a amazon bin by changing it to a zip) and then flash the optimized ROM without wiping the system. It's also possible (this is most likely) something in the boot.img was messed with. That can probably be fixed by replacing the boot.img in the zip, with the stock one. Since rooting doesn't take place until the ROM is installed, it won't effect root. I'll look at it all when I get home. but if anyone experiments with any of these and it works, let me know.

---------- Post added at 06:57 AM ---------- Previous post was at 06:52 AM ----------

Should be simple...should be. Boot into hacked fastboot and open adb window, connect tablet to pc and put your logo of choice in the same folder as adb. Type in adb window:

fastboot flash logo nameoflogo.bin

That's the usual way it has been done across countless devices for years. But doesn't mean it's the same here.