yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] bibikalka:
Nice approach, and fully works, as in here :D

At some point it was established that versions update, and that what prevents older bootloaders from running:

https://xdaforums.com/amazon-fire/development/unbrick-fire-7-5th-gen-downgrade-t3388747
[Fire HD 8 and HD 10 General] adco:
Any chance this img will work on HD 8 7th gen?
[Fire HD 8 and HD 10 General] Supersonic27543:
Nope. :crying:
[Fire HD 8 and HD 10 General] retyre:
The 5.6.2.0 update.bin for the 2017 HD 10 is up on the Amz page. It's a good bit larger (in file size) than the 5.6.1.0 update. Time permitting, I will upload a FlashFire-flashable prerooted image in a few days.

The bootloader files in 5.6.2.0 have different hashes from those in 5.6.1.0. If you have updated to the 5.6.2.0 bootloader, do not sideload a lower version.

Update: The OP has been updated with the link to a compressed file containing the 5.6.2.0 boot.img and prerooted 5.6.2.0 system.img. If there are issues, please post here. Note: 5.6.2.0 has been updated with some new "Echo" features that use com.amazon.paladin. If disabling com.amazon.firelauncher does not enable your custom launcher, you should disable com.amazon.paladin as well: pm disable com.amazon.paladin).
[Fire HD 8 and HD 10 General] sga999:
retyre, this worked perfectly again! I had previously used this same method to update from 5.6.0.1 to 5.6.1.0. I checked the first few bytes of the LK image, as you described earlier in this thread. The bootloader still indicates 5.6.0.1 (not 5.6.1.0 or 5.6.2.0).

1. Is there any reason to be on a newer bootloader? I know that bricks the device if we downgrade from some versions to earlier versions. But are there positive reasons for updating the bootloader?

2. You mentioned that you changed the build version in the build prop. What is the reason for that?

Thanks for your great work.
[Fire HD 8 and HD 10 General] sga999:
I am having one problem. I use AdAway, and it modifies the hosts file. It was working fine until I just installed 5.6.2.0 with your method. AdAway fails when trying to write its own hosts file into /system/etc. I definitely have root... I have several apps that require root and all of them are working fine. But if I use FX file explorer and try to mount system as read-write, it fails. So that must explain why the hosts file cannot be written. Any idea about what would cause that? Maybe I somehow managed to leave out a step, but everything else seems to be working well.

EDIT: That wasn't quite accurate. I CAN mount /system as read-write but not /system/etc.
[Fire HD 8 and HD 10 General] tekkitan:
If I were to use this 5.6.2.0 image to sideload on my soft-bricked Fire HD 10 instead of the stock Amz image, will it work just fine? I believe it's stuck booting on 5.6.0.1 due to some changes to build.prop.
[Fire HD 8 and HD 10 General] wunderdrug:
Posted to wrong thread. Sorry.
[Fire HD 8 and HD 10 General] xperia709:
Bin file for adb update?

I updated to 5.6.2.0 after rooting 5.6.1.0 and as expected lost root. I updated via ota because I wanted to try it show mode. And while I think it's a great addition I miss root and the tablet is definitely less optimized with the root apps I was using. Can you post a pre rooted version of the bin file so I can flash that using adb push update?
[Fire HD 8 and HD 10 General] tekkitan:
Just re-root it on 5.6.2.0.
[Fire HD 8 and HD 10 General] sga999:
retyre, I'm still having trouble with making /system/etc read-write (as mentioned in Post 25) after flashing your zip file with FF. To learn more, I went back to stock 5.6.1.0 and rooted it. Then I am able to make that folder read-write with FX file explorer. And I am able to use AdAway.

But then I flashed your boot.img and your system.img from your 5.6.1.0 zip file. Both AdAway and FX file explorer fail. So the problem was not introduced with your 5.6.2.0 zip, i.e. the problem occurs with either of your prerooted zip files.

I guess I did not notice the problem with the first prerooted zip because the hosts file was already set up properly. So I did not run AdAway and I did not see the problem. But for some reason, after installing your 5.6.2.0 zip, the hosts file was changed back to the default. So I ran AdAway in order to set up the correct hosts file, and AdAway could not write the hosts file. Then I went further, and I noticed the read-write problem with FX file explorer.

I also posted a couple questions in post 24. No hurry if you are busy or not checking here, but I just wanted to be sure you didn't miss my two posts.
[Fire HD 8 and HD 10 General] retyre:
I usually chalk this down to user error, but I made an exception for you and tested it out myself. I:

-- flashed the boot.img and system.img from the .zip, wiped everything clean, and rebooted;

-- installed SuperSU v2.79 and set default access to Grant; and

-- installed AdAway v3.2 and let it update the hosts file. It did as expected.

So, the system.img is not the issue here. Let me ask the obvious: Are AdAway and FX getting root permissions (i.e., are you sure they're not missing from the SuperSU preferences file and being blocked)?

Regarding your other questions: There really is no need to be on a newer bootloader. If anything, the goal of most device makers is to lock down their devices as much as possible, starting with the bootloader. Enhancements, if any, rest in /system. See this link for an answer to your other question.
[Fire HD 8 and HD 10 General] sga999:
The difference in what you wrote and what I am doing is that I do not wipe anything after I use Flashfire to flash both images. I want to keep all my data as it was. I was assuming that was allowed. At least I didn't read anything about wiping in your description. I'll look again, maybe I missed it. So are you saying that wipe is required and that all apps have to be restored in some other way? I do have an FF backup, but I don't know if restoring the data will work properly. I also could use titanium backup, but obviously I was hoping none of these other steps were necessary. When I do ADB sideload, I am not required to wipe the data.

I have about 15 apps that require root. All of them are working properly except for these two. And in general, FX file explorer is fine. I mean, if I want to look at system, it asked me if I want to do that, and I have to say yes. Then it goes ahead and shows me what is in that folder. It does not fail at that point. It even works when I say I want to make system read-write. But it will not do it for system/etc.

I have never done anything to the SuperSU preferences file. I do not see anything in it related to any of my apps that require root. If I look at the SuperSU logs tab, it shows FX and AdAway and all the other apps that have gotten root. None of them have failed and all have a pound sign next to them.

One thing I read says something about an insecure boot.img and it does not accept a modified /system. Others said that you have to use ADB disable-verity, but that is not allowed without a user debug build. I'm just throwing those things out there, and I know they are probably not very interesting to you.

Since you renamed the OTA apk, I guess you are just making it "stronger" by changing the build prop version. Thanks.

EDIT: AdAway will not even install without having root. After it failed to write the hosts file, I uninstalled it and reinstalled with no problem. If I did not have root, it would disallow the install.. It is only when I try to enable their hosts file that it has trouble.
[Fire HD 8 and HD 10 General] BecauseWhyNot:
I will try this right now. I just soft bricked my Fire HD10 7th gen trying to debloat it. I'll let you know the results by tonight.
[Fire HD 8 and HD 10 General] retyre:
No, wiping is not required. It's a just a way to rule out other issues (e.g., user-configured settings or apps). If it works on a clean system, it's clear that the system.img is not the cause of the problem. It's something else you have introduced outside of the system.img flash (perhaps a setting in /data). It works for me with my custom apps and settings, so (unless others chime in with this problem) I'm fairly certain this is an issue specific to your setup.

For AdAway, rename the hosts file and create a symbolic link to /system/etc/hosts in /data. Is AdAway able to write to it now?

For FX, can you test with another root explorer?

Is SEL permissive or enforcing?
[Fire HD 8 and HD 10 General] sga999:
ES File Explorer has the same problem. The only reason that I'm even talking about a file explorer is because AdAway didn't work. So FX file explorer was just another example of not being able to write to a specific folder. There may be many other folders that I cannot write to, but this is the only thing that is obviously failing for me right now.

SEL is enforcing.

I'm not familiar with creating a symbolic link. So that would take some investigation. I'm probably not understanding the part where you said to rename the hosts file. I cannot write to that folder. So I know you're saying something else.

I think I am tempted to wipe the data and see what happens. If it fails, we certainly won't understand that and can't blame it on my data. If it works, I have no idea what is unusual about my data compared to yours or anyone else's.

---------- Post added at 04:58 PM ---------- Previous post was at 04:47 PM ----------

Is there a way to sideload the 5.6.2.0 bin file without the images folder? I'm trying to not update the bootloader. But I am pretty sure that everything will work fine if I use that standard method instead of yours. As I wrote earlier, I sideloaded 5.6.1.0, rooted, and everything was fine. I did not wipe any data. Then I used this prerooted version and the problem started happening.
[Fire HD 8 and HD 10 General] retyre:
Not sideload, but there's a way to flash the update.bin as a .zip, but you will have to convert the system.new.dat into a system.img and modify the update script to match. Before we go there, flash this in FF and see whether it works with your data setup.
[Fire HD 8 and HD 10 General] sga999:
It has been stuck on the fire logo for about 9 minutes. I don't think it ever takes that long for it to come up. When it starts the optimizing apps part, that does take about 12 minutes for me. But it's not even getting to that. I guess I have to start over with ADB sideload!

Did this flash properly for you? Or maybe you wanted me to try it without you doing it first.
[Fire HD 8 and HD 10 General] super102:
My results

Hi,

I initially flashed with the offline method and it worked great.

I decided to use FF to install your 5.6.2.0 image (my Fire is also already 5.6.2.0). I manually shifted the time with busybox, then I first flashed the boot.img using FlashFire's "Flash firmware package” option. Once that completed, I flashed the system.img (again, using FlashFire's "Flash firmware package”)

OTA.apk is good, I think it has .old on the end. The prop number is good being 987654321.

The issue I’m seeing is that I’ve now installed Nova Launcher and when I try to use Link2SD to convert to system app, I get Failure mount: invalid argument. If I click on Nova Launcher in Link2SD, it says on that page, “Second partition not found”.

Any ideas? I’m not too clear on mounts in Android. I wonder if perhaps you use a memory card and I don’t and that got flashed over?
[Fire HD 8 and HD 10 General] BecauseWhyNot:
[MENTION=1797995]tekkitan[/MENTION]

So I converted the system.new.dat to a flashable .img using URtool (https://xdaforums.com/chef-central/android/tool-extract-repack-dat-img-android-5-8-t3670763)

It bricked my device beyond my level of knowledge. Best buy replaced it no questions asked. The employee didn't seem to care and just issued a refund so I could get another one, so I lucked out. Perhaps I missed something, but I don't recommend it.

One thing to note, though: The bootloader said it was verifying the validity of the ROM via hash, or something of the likes before bricking it. You definitely need to be rooted and FlashFire it from within the OS.
[Fire HD 8 and HD 10 General] sga999:
After your v2 version bootlooped, I waited to see if you had any ideas. Since I didn't hear anything, I investigated more today. I looked at the FF Lastlog, and it showed that many things failed during the flash, all similar to the initial problems I was having, i.e. unable to write, etc. So it makes sense that it would have bootlooped.

So then I realized that I had done the flashing of your new v2 version on top of your prior version....which was already failing with my FX file explorer and AdAway problems! In the meantime, after the bootloop, I had to reflash the original 5.6.1.0 with adb sideload and rerooted, etc. So I realized that now I was in a state where your v2 version might possibly flash successfully.

Yes, it did! And with minimal testing so far, it appears that the problem is fixed. FX file explorer and AdAway seem to be working fine.

So can you tell me what the problem was and/or what you changed to make it work? And do you know the possible reasons that your prior versions (of both 5.6.1.0 and 5.6.2.0) worked with your data but not with mine? (I know you said you had no problem with AdAway writing the hosts file).

I'm also guessing that the link2sd problem that super102 was having (a couple of posts above) might be fixed by this v2 version. But you're the only one who would know that.
[Fire HD 8 and HD 10 General] super102:
Update

It seems to be working for me now. I'll try to recall all that I did.

Wiped from the volume up menu. Same issue.

Sideloaded the base 5.6.2.0 version.

Put system into airplane mode.

Offline rooted.

Left flashfire as a user app.

Changed date with busybox.

Flashed your two files as before.

I am now able to move Nova to a system app with link2.

Interestingly, I don't see busybox as an app now? I believe that's supposed to be included?

Any suggestion how to check if xposed framework is installed? I checked last time and found some sort of xposed conf file. Not in front of my fire right now to check.

Anyway, thanks again for all you do for the community!
[Fire HD 8 and HD 10 General] retyre:
super102: busybox is a binary, not an app. Run busybox from a shell prompt and it should work. To confirm Xposed is working, you will have to install Xposed Installer. I like the Material version (linked in my other thread).

sga999: I have not looked into this, but these are the differences between the first version and v2: v1 completely bypasses Kingo (I convert system.new.dat to system.img, mount it in Ubuntu, inject the su files in the right places with the right permissions, flash the system.img and boot.img in FF, and update the su binary with SuperSU) while v2 pretty much follows the SOP (I convert system.new.dat to system.img and add it to the update .zip, edit the update script to remove all references to the bootloader files and write just boot.img and system.img, flash the update .zip in FF, root with offline Kingo, and update the su binary with SuperSU). Clearly, v2 has to work for everyone given it mirrors what one would normally do to root. I would expect v1 to work just as well; I'm not sure why it didn't in your case. It may have to do with how Kingo mounts and writes its files, but I haven't looked at it. As I wrote earlier, I have not had an issue with v1. I'm still leaning toward something peculiar in your (or my) /data partition, but since v2 works for the two of you, I have updated the link in the OP.

I see a lot of questions about using this prerooted image to adb sideload. Here's a generic response:

-- The only files you can adb sideload are the ones you download from Amz's page (update*.bin). (Note also that the update file has to match your bootloader version.) Any file that has been modified will fail the signature check.
[Fire HD 8 and HD 10 General] DragonFire1024:
I have a question. I did a DD of system to get a system image. I had to reflash stock so after i reroot and what not, I want to flash the image. When I select it, ever root pops up. Do I select or deselect the option to protect recovery? What about the other options?
[Fire HD 8 and HD 10 General] retyre:
I have not tried EverRoot in some time, but when I last checked, it did not work. You should remove that card from FF's actions. In any case, given your system.img is already rooted, I'm not sure you need EverRoot.
[Fire HD 8 and HD 10 General] DragonFire1024:
I don't need it. And it wouldn't allow me to swipe the card off the screen. However I left supersu and setup wizard unchecked and flashed. Everything is perfect. One more question. When you dd to get system image, I copied it to PC. I could then open it as an archive in 7zip, but it would not let me add or delete files or folders. So I can extract it (with symlink errors) and then edit. But how do I make it back into a system.IMG? Also, I was able to find an app, Online Nandroid Backup (got it here on xda) which essentially did the same thing as dd, but the file is system.ext4.win. I can open it and edit it, but how would I make it a system.IMG or use the system.ext4.win to reflash? Thanks for all your work ?
[Fire HD 8 and HD 10 General] retyre:
These are raw images. You can use some of the MTK tools to unpack and repack these images, but anything complicated (e.g., changing permissions or contexts, symbolic linking, etc.) should be done in Linux (mount the raw image in Ubuntu, make your changes, unmount, and flash the modified image using FF). Even if there were Windows-based tools to edit raw images, I wouldn't recommend that.
[Fire HD 8 and HD 10 General] DragonFire1024:
OK. I understand that now. So when a ROM is installed on these, the boot.IMG is the only image. The issue I seem to be having is on a script level. I don't have a log at the moment, but it appears a lot of the commands used on the Fire 7 script, don't work...like 'set_metadata_recursive'. A lot of the symlinks for busybox fail too.
[Fire HD 8 and HD 10 General] chemengire:
boot.img

(1) If the device has the stock 5.6.2 operating system, is it sufficient to only flash the system.img file, or must one also additionally flash the boot.img file?

(2) Does the performance & battery life of the device improve upon flashing these images and then subsequently the disabling of the amazon apk applications?

Please forgive any noob-ness.

Thank you to all the senior members for their work on this ☺️.
[Fire HD 8 and HD 10 General] DragonFire1024:
I can answer number 2. I've been replacing and removing Amazon apps one by one, and rewriting the framework in the process. I find if you do a lot of debloating and replacing of the /system, a reset every now and then cleans up the mess left behind as a result. Apps run cleaner and smoother.
[Fire HD 8 and HD 10 General] chemengire:
Reset

Dear Dragonfire1024,

By "Reset", do you mean a restart or the factory reset option?

Thanks ☺️
[Fire HD 8 and HD 10 General] DragonFire1024:
Factory reset if you know you didn't mess anything up. If you're trying to fix something in the system you messed up, you'll have to reflash firmware. For now, if I'm going to keep trying to build a ROM for this tablet, it will have to be done by flashing a system.IMG in flash fire. I just spent over an hour bookmarking tools that will allow you to extract, edit and repack that raw IMG. So the next several days will be spent doing that and testing the results. Thanks to [MENTION=3497316]retyre[/MENTION] I don't have to start over if I mess up the system. After I reroot, I just flash the last one I dd in flash fire, still have root, and didn't lose my progress. So I can continue relatively close to before I screwed up xD

Edit: the downside of this is, the first ROM, if I can make it, will be for 5.6.0.1. That's what I'm on right now. I haven't decided if I want to go higher because you can't go lower once you do.
[Fire HD 8 and HD 10 General] chemengire:
Thank you, DragonFire1024 ☺

I wonder if it is possible to create Android virtual machines to test & work with...?

Is there a book or guide available that you use for people wanting to understand how Android OS is organised and how it may be modded/hacked? I used to be a Windows.NET software engineer & I know some bash shell commands so it might not be that hard to pick up.

It seems to me the device hardware is adequate but but may be laden with Amazon junk applications and also, effectively, Amazon spyware. The absence of the usual stock Android "Settings" page is a big loss.

In particular, I think the 5 GHz WiFi radio band receiver is especially hobbled relative to the 2.4 GHz reception, which I assume is (maybe deliberately) poor optimisation by the Fire OS software engineers ??
[Fire HD 8 and HD 10 General] alanhuro:
Question about Xposed 5.6.2.0 image

I have been using my tablet Fire 10 HD with current firmware version 5.6.2.0. I want to root my device and after search for solution I ran into this thread. I have been reading all the discussions in this thread but still unsure whether I'm able to use this method to root my device

My current version is 5.6.2.0. I have been using it for 2 months now. Is there anyway I can downgrade this to 5.6.1.0, then root it and upgrade back to 5.6.2.0? Could you please provide me a direction from here?

thanks
[Fire HD 8 and HD 10 General] DragonFire1024:
Downgrading will result in a perma brick for any tablet on 5.6.1.0 or later. You can use the method in the OP or you can use Kingoroot PC. Hopefully the tablet is still on a rootable version of 5.6.2.0. these things 'update' with smaller files and those small updates don't usually change the FireOS version.
[Fire HD 8 and HD 10 General] sga999:
Some other threads talk about a new update. It should be called 5.6.3.x, but others seem to say it is mislabeled as 5.3.6.4. Are you able to create a prerooted version of that? I have a Fire HD 10 7th gen. I'm not sure if that update is available for this model. Thanks.
[Fire HD 8 and HD 10 General] DragonFire1024:
I've just discovered a possible vulnerability that has a good potential to be exploitable. I advise against any updates from here on out until i, or we establish it's extent, if any and what the effects are of this possible vulnerability.
[Fire HD 8 and HD 10 General] sga999:
I hope you make progress on that! But just in case you don't, if it's not too difficult for retyre to create the prerooted files now, it would be great to have that available.
[Fire HD 8 and HD 10 General] retyre:
Shouldn't be difficult ... if the 5.6.3.x update .bin is publicly downloadable. I have searched all over without a hit. If you know the download URL, please post here.
[Fire HD 8 and HD 10 General] adm1jtg:
in all the postings of the 563x or 5364 I have not seen anything about the advantages of this new build... is it faster, smoother, better on memory, have any new features?

Or is this simply a newer is better kinda philosophy?
[Fire HD 8 and HD 10 General] DragonFire1024:
Not many at this point have the newest build. My guess is they are prepping the tablets for 7.0.
[Fire HD 8 and HD 10 General] sga999:
I searched and could not find a link either. I think this new update is mentioned in at least 3 other threads. But maybe no one has actually downloaded it. It's possible that they just let it automatically update their system. I guess we'll have to wait!
[Fire HD 8 and HD 10 General] Snigglez:
-posted in wrong thread, sry
[Fire HD 8 and HD 10 General] bibikalka:
[MENTION=3497316]retyre[/MENTION]

So I got a new HD10, and god bless Target's soul, it had version 5.6.0.0. After Kingoroot, I used your 5.6.2.0 zip to update, and I re-discovered a couple of items that inconvenienced my efforts a bit.

Flashfire appears to be picky how one calls images. It needs files to end in .bin - [boot.bin,system.bin]. The 2nd piece it appears it wanted md5 files even if I am not asking it to verify checksums. It's very easy to make those checksums on Android - [md5 system.bin > system.md5].

So if you do update your package to the newer version, would you take this into account? To recap:

1) give image files extension ".bin"

2) create md5 checksum files

Then I can unpack this in /sdcard/FlashFire/Backups/5.x.x.x , and effortlessly restore it via FlashFire.

Thanks!!!