yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Don't want to spend money on the dock since it's basically a contact charging-enabled "case" in itself, that doesn't have a cover like the one I already have (a "smart cover" which doubles as a folding stand, and using Show Mode with that would suffice for my uses). A Google search says I should be able to enable Show Mode by swiping down the notification shade and tapping the quick setting button for it, but I don't see it. Weird.
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
I don't think it's done a full rollout to all HD 10s yet.
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Wait, what? It's a new feature?

I have the Show Mode options in the settings, actually.
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
I am on 5.6.1.0. I don't have it thankfully. I think it was added on 5.6.2.0 then fully implemented on later versions thereafter.
[Fire HD 8 and HD 10 Android Development] bibikalka:
Is there any advantage to using this Rom?

Also, if this is still essentially a fully stock rom, why factory reset at all? It will still write the same config files, and all.
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
Well there's no custom Rom yet. Also deodexed. It's just a lot smoother and significantly less chance of a googling from uninstalling system apps.
[Fire HD 8 and HD 10 Android Development] bibikalka:
Why would it be "a lot smoother"? Any technical reason, or a mere placebo effect perhaps?
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Nope, seems more stable and smooth to me.

One minor issue. Is anyone else able to copy files to the SD card via MTP? Haven't been able to do that since before unlocking the bootloader.

EDIT: Seems to only be a specific file. Could be something to do with the size. It's almost 3GB. Damn h.264-encoded movies. Behemoth sizes. Why the hell isn't everyone using HVEC/h.265 these days?
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
The fire 7 Ford has an issue where you can't access the storage while the tablet is in twrp. This HD10 however, perfect. The only down side is not being able to flash a system.img in fastboot. I'm hoping it's just a fluke and I just don't know what I'm doing. I've never had this trouble on other devices. Even unlocked, we still have to overcome Amazon's butchering.

In regards to a rom, it's going to have to be done slowly. In other words, modify a few files, delete or add a few, build a zip and flash. Repeat that process until the only thing left to port are the important files. If I go all out and delete and readd all apps and framework etc, it will likely not flash as what's happened before. Getting close though in debloating as I can regularly the Android welcome screen to appear, but fails to complete the setup and loops back to the welcome screen. Still have to figure out what ties into that. So long as I stick to small portions until built it should flash
[Fire HD 8 and HD 10 Android Development] beachmiles:
Thats what it says on Amazons site. The show dock is almost better than wireless charging because the dock has magnets that sort of lock the to the thin case it comes with that snaps on the fire. So you never need to worry about being on the wireless charging sweet spot, and it keeps the device from getting knocked off easy. On the previous 5.6.1.0 release the charging would not activate on the dock, but something in 5.6.2.0 enables the power to flow.
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
Yeah now I'm pissed....fire stick and tv just got full miracast support. https://www.androidpolice.com/2019/...stick-4k-picks-up-miracast-display-mirroring/
[Fire HD 8 and HD 10 Android Development] coilmaster949:
First, thanks to DragonFire1024 and GuyInDogSuit for helping me get started on this root & rom flash.

1. Finally, I got rooted & bootloader unlocked by https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639 and now running dragonfire1024's 5.6.2.0 - WIFI DHCP is not working - which this thread folks know.

2. But something I found - that ads kept coming back...so I passed those 3-4 OTA and ad disabling commands again thru ADB and now it seems to have worked. Seems pretty wierd though if debloated rom had already managed that- not sure how those packages showed up. Did amazon re-install those ?? Not sure if others have seen this.

Anyway, pls. see attachd creenshot - u'll see that on 2 commands, it says package not found (my guess being that its disabled in rom already) but on others it actually disabled only after I ADB those commands.

3.Maybe GuyInDogSuit can chime in - at this point, if I want to get working WIFI DHCP - I guess I shd. go back to TWRP, wipe all, but then flash which ROM? and then disable selectively most bloatware using that google sheets link you pointed.

4. Is Alexa handsfree better than Google- if so, can I keep Alexa on this just for asst. but have her open up websearches etc. in all google side of things? To do this, what all minimum packages shd. I leave on.

5. Finally, whats the best cleaner software on Fire HD - DU speed booster? that my son can use weekly to keep it running at good speed.
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
1. Is the static IP address option not viable? I could help you set that up.

2. I found that asking Amazon customer service directly about disabling the ads was more effective. They will happily do it for free in most cases. Plus, it's permanent.

3. You COULD go back to regular stock. It would disable root, however, so you would need to flash Magisk again in TWRP.

4. That, I do not know. There IS a method to enable fully-working Google Assistant on this forum, though.

5. There is no need for something like that. SD Maid is good, if you want to free up storage space from uninstalled apps, that is.
[Fire HD 8 and HD 10 Android Development] coilmaster949:
1. Is the static IP not viable?

- Static is working fine at home. Only downside I can imagine, when my 9yr old goes to friend's house and tries to connect to their wifi ? Will be an issue unless DHCP works ?

3. You COULD go back to regular stock. Then u need to flash Magisk again in TWRP.

- Could you pls. point me which complete/ latest/greatest stock ROM shd. I use and also Magisk file? And are steps below the correct order.

A. reboot to TWRP - wipe all 4 system, data, cache , dalvik.

B In TWRP install ROM file

C. Install Magisk, then reboot to TWRP - Wipe Cache and Dalvik only

D. Reboot to system - turn on airplane mode. turn on ADB debug and unknown sources

E. ADB into and run 3-4 commands to stop OTA updates, KSO

F. reboot system - install NOVA launcher and google play +3 other play related apps.

G. ADB into and disable fire launcher

I'll check out SD maid - Do u have any recommendation for a light and thorough 1 button residual task killer for andoid - something that quickly closes most unneeded background apps/windows. I wish android came up with better (rule based) task and background task mgmt.- current method of just pushing apps behind and letting them hog system resources is a pretty giant waste in my opinion.
[Fire HD 8 and HD 10 Android Development] tylerhole:
Pretty much every consumer wifi router's IP address is 192.168.1.1 (sometimes 192.168.0.1) Subnet 255.255.255.0 and if it's not a custom setup router it will dish out IP addresses of 192.168.1.2-192.168.1.154+ (or 192.168.0.2-192.168.0.154+). Unless the router is setup differently then what the defaults tend to be, have your kid just set a static IP of something like 192.168.1.34 or something and it should hopefully work.
[Fire HD 8 and HD 10 Android Development] DB126:
Android resource management algorithms are actually quite sophisticated and far better than simply killing processes at random. Relevant issues:

- low-end hardware

- 4 year old Android base

- puny resources (ram)

Background tasks are likely not the primary issue although no doubt contribute to sluggishness. See posts on expanding vram via a *small* static swap file and accompanying adjustments to swappiness setting. Certainly no pananica but more effective than mowing down processes that will likely respawn a short while later.
[Fire HD 8 and HD 10 Android Development] coilmaster949:
unfortunately 192.168.0.1 is not that uncommon, though 1.1 is more frequent- and thats where crux of matter is.

---------- Post added at 08:19 PM ---------- Previous post was at 08:16 PM ----------

Thats a great point, I didnt think about- gotta read up on it though. Not sure how that behaves on Fire 10- Could you pls. link one of the post u refer to "See posts on expanding vram via a *small* static swap file and accompanying adjustments to swappiness setting."
[Fire HD 8 and HD 10 Android Development] tylerhole:
I wasn't saying it was uncommon and I understand what the issue is, but as of now when running this firmware your only option is to guess, keep your fingers crossed and get lucky.

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
Well I added a .conf file the DHCP folder. I looked on several different devices and all the files are the same across all of them. No effect when added and the system logs aren't very helpful. So at least we narrowed it down to what the problem is not: not drivers, I looked at other amazon tablets. Doesn't appear to be a .conf. it could be a prop or a setting data base. Might even be the wifilocker app. It does have to do with credential verification or uploads.
[Fire HD 8 and HD 10 Android Development] tylerhole:
Well at least there's something else we can put in the "not the issue" column. I grabbed a log earlier and have sent it to a couple people to see if they could help figure out the issue. I'll let you know as soon as I know if anything is found.

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
What about the newer firmwares?
[Fire HD 8 and HD 10 Android Development] tylerhole:
It was suggested to me by 1 person that it could just be the firmware. Some versions just simply do not want to work without issues after being deodexed. Only way to test said theory (to an extent because who knows, maybe none will work right) would be to do the same to the other ones that you've done to these 2 and see what kind of results we get.

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
Things should never be odexed in the first place. It can be argued both ways until the cows come home. Usually it's the other way around, in my experience. Sigh I'm stumped.
[Fire HD 8 and HD 10 Android Development] tylerhole:
Usually but not always. Short of giving all the different ones a try who can say that this isn't the case? Same person who suggested that also said it definitely looks like a framework issue, but I'm waiting on a response from someone else more knowledgeable in that area. I'll let ya know what I find out from people and keep digging around myself in the meantime.

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Why is anything ever odexed?
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
Supposedly, amongst other reasons, for the same reasons to deodex, save a bit of space, ram etc. However, it is also a way to 'freeze' settings and values, making it harder to modify apks for example. In my opinion, but not an expert one, I think odex files are worse than overlays and they are severely abused. I don't see a reason for EVERY SINGLE APP to be odexed. Also the odex files don't get removed when you delete an app, unless they are in a folder within the apk folder. Amazon did a one over literally, moved the framework odex files to a directory one over. In other words it was impossible to deodex everything without a custom recovery. I was doing it one file at a time.

Rom and kernel update: I spent a lot of time trying to compile a kernel or modify it. I think I got the hang of it, but I will be e to experiment more tomorrow. I tried 3 kernels. Mt8173, droid Razr m and a galaxy tab3 lite. The Amazon source, gives me a kernel image. So at least we can do some modifications. In fact, it was the only one of the three to produce an image. The razr m gets about 50% and errors out. Will try another source.

Dhcp. In settings database editor, the dhcp init service fails. It tries, I extended the amount of tries to 10. It just shuts down after that. So it's likely in an init file either in the root directory, or system/etc. Somewhere in one of those is a dhcp variable (line in the script) that is commented out with a #. I have briefly looked at a few files but nothing yet. We find that line, I can fix it easily in the boot.img.
[Fire HD 8 and HD 10 Android Development] DB126:
Yes, those foolish Google Engineers have it all wrong favoring the 95-98% of users who are not hacks and will use the device as intended. Not to mention optimizing performance on a highly resourced constrained platform. Fools, I say, fools!! :rolleyes:
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
As I said earlier to each their own on this one.
[Fire HD 8 and HD 10 Android Development] DB126:
Not a matter of opinion. Facts are facts. No dispute deodexed ROMs are nicer for the minute base that messes with stock configs. The vast majority of everyday users benefit from the improvements odexing brings with no downside.
[Fire HD 8 and HD 10 Android Development] speaker1264:
This firmware just isn't working for me. Does anyone know where I can download the unmodified version of 5.6.1.0?
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
https://xdaforums.com/hd8-hd10/general/tut-fire-hd-10-7th-gen-2017-root-box-t3726443

2nd post. Mind explaining what's "not working"?

[MENTION=7104332]k4y0z[/MENTION] and [MENTION=8165603]DragonFire1024[/MENTION], correct me if I'm wrong, but it's theoretically possible to update to the latest and still be able to root, right? So 5.6.3.4 is root-able? Any benefit to doing that? Besides having working DHCP?
[Fire HD 8 and HD 10 Android Development] speaker1264:
I just can't get wifi to work anymore. Also, if I do upgrade my version of Fire OS, is it possible to downgrade back down later without bricking my device? I wasn't sure if TWRP allowed you to do that or not.
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Did you try the static IP settings?

Right now, downgrading isn't advised.
[Fire HD 8 and HD 10 Android Development] speaker1264:
That worked, lol... thanks. I think I'll stay on 5.6.1.0 unless I find there's a good reason to upgrade.
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
You can still update yes but you have to reroot. You can remove the lines in the script so it doesn't flash anything except the system partition. I don't know if there's a way to keep root, but reroot yes. I haven't looked at the latest firmware yet.
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
I am curious to see what you can do with the newest firmware.

Not sure what the newer versions do, but I like to be on the latest, lol.
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
How do you do that? Extract it like a zip?
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
It's not as easy as it sounds. I'm actually shocked the firmware even flashes after a deodex, given almost any other time I remove an app or change something the Rom doesn't install properly. Everything looks to have flashed, but never boots. So if any kind of ported Rom comes of this, it will take a lot of time to piece together. I Also notice upon recompile, the tool adds some of the removed apps and files back into the rom via the system.omg it makes by default. I think that's what screws everything up. The Amazon apps can't run without their permissions so they crash everything before it starts. It also doesn't help the size of the system image and it partition never seem to be the same. The .dat is smaller than the system.img. The directory measures too big of it calculates from that.
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
change .bin to .zip. Open as an archive with 7zip. Drag the script out. Edit it and drag it back in. Remove any lines from the script that flash anything aside from system and remove the line flashing boot.img.
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Is there any real benefit to updating though?
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
As soon as I can get my hands on the fire TV latest firmware, we'll see. They just got full support for the original Miracast via mtk. If I can find the props in their kernel, I can probably hack it into our tablets.
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Ah, sweet! I won't have much use for that, but it sounds cool.
[Fire HD 8 and HD 10 Android Development] k4y0z:
As long as you have TWRP you can root any firmware.

Any benefit from using an outdated firmware I ask?
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Just haven't figured out how to update yet, lol. Just need to flash only the system, I guess.
[Fire HD 8 and HD 10 Android Development] k4y0z:
Just rename the update-bin to .zip and install through TWRP.

Then reinstall Magisk.
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
Only one more to go for latest firmware. Besides I don't think people want to intentionally brick to fix and repeat. I gotta get the fire tv and stick source. If it's as simple as I think, I can get miracast running...now that I can modify the boot.img at will. I just need to see what's under the hood. If I had an HD 8, 2016 source...
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
It won't overwrite the boot.img or recovery?
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
Have to remove the line flashing recovery. Boot.img doesn't matter if you haven't customized it or what not.
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
Ok so did some reading and there might be some light at the end of the tunnel regarding dhcp. I added a prop to build.prop

ro.mtk_dhcpv6c_wifi=1

It was set to 0. Now I'm still static, but these popped up after

dhcp.wlan0.dns1=0.0.0.0
dhcp.wlan0.dns2=0.0.0.0

It's better then the one before that said 'failed.'
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Oh, makes sense since you're flashing Magisk again anyway.
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
I'm going to play with the kernel today. It's been the only one that will build successfully. I am hoping there isn't a module restriction. If so, we'll be better off making boot.img from scratch or porting to lineage.
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
FireOS 5.3.6.4

update-kindle-40.6.2.6_user_626533320

Changelog: "This free software update includes general improvements and performance enhancements."

DAT STABILITY.

So I change the extension to .zip, pull the script, and delete all lines flashing anything but the system, correct? Then copy it back in, and flash in TWRP? That's it? Which file is the actual script though? The "updater-script" in META-INF\com\google\android\?
[Fire HD 8 and HD 10 Android Development] k4y0z:
No reason to modify anything.

Yes it will overwrite boot.img as it should, that's why you need to reinstall Magisk.

TWRP will not be overwritten
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
Yes on the zip, script. When I get home I'm going to post a guide on 'rooting' your own boot.img permanently and making adb insecure. That way you can just carry over the boot.img provided there are no massive changes.

BTW [MENTION=7104332]k4y0z[/MENTION] I just took a look at the boot partitions. I giggled while SMH. Please tell me that's the second 'hidden' bootloader?
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
Ok so I have an idea. I'll look over the .bin and see if I can readd the odexed Wi-Fi file and rebuild. Unfortunately it's not something as simple as flashing a tiny zip.
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
Actually good to know.
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Sometimes when I tap the back button to go back to the desktop, from certain apps like Discord, I get this screen. What, how, and why? I have Alexa, Alexa Cards, and Alexa Shopping all disabled.

Anyone try different Magisk modules? Which ones work best with this ROM? Which ones don't?
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
Never seen it before.
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Magisk won't flash for some reason. TWRP says it was successful, though.

Figured it out. v18.1 stable doesn't install, but v19.0 beta does.
[Fire HD 8 and HD 10 Android Development] k4y0z:
Not sure, what you are talking about.

There is no "hidden" bootloader.

I have actually mentioned that a few times before.

Recovery is flashed on first boot and is created from the boot.img, but that will fail because it is looking at the wrong boot-partition.

Therefore TWRP is safe.

As for the rest TWRP takes care that preloader/lk/tz won't be overwritten during the update.

---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------

That's strange, Magisk 18.1 works fine for me.

Did you also install the MagiskManager apk?
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
Look in root directory, fstab_mt8173. Lk and lk2
[Fire HD 8 and HD 10 Android Development] k4y0z:
There is only one LK on HD10 the LK2 line is probably some leftover from development.
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
So I thought too. But it's not what it seems. If you compare it to the mounts (cat proc/partitions) everything is in order but there is one extra. 0boot0 and or 0boot1. All this time I thought you saw this. If you dd it, there's no joke...ever hear of beefdeed?
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
A little off track, but an example of one of my achievements here, and part of why I like to do what I do with devices. This was actually what got me started on the Amazon tablet addiction. It's a small, overlooked feature and all I wanted was to unlock it. Most of my hacks came as a result of unlocking this one little thing. The Daydream screensaver. when I unlocked it in the framework, I was able to unlock 80% of what I brought you. It's little pleasures like this that keep me going.
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Yeah, it was already installed and kept saying Magisk wasn't installed, that there was an update and latest was 18.1. Very odd.
[Fire HD 8 and HD 10 Android Development] tylerhole:
I had the same problem when I flashed 5.6.2.0. I could flash Magisk 100 times in TWRP and it would still say the same thing and no matter what version of Magisk manager I used said same thing. But then flashed 19 and it was and still is all good.

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Very weird. Previously, I had already had v19 installed before the update. I don't recall flashing that, but meh. Whatever. It was working fine then, and is still working fine now.
[Fire HD 8 and HD 10 Android Development] tylerhole:
On 5.6.1.0 18.1 definitely worked for me out the box. Very strange its not on 5.6.2.0 and that it won't seem to install at all.

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
I don't know if I accidentally flashed v19 after the .20 update, but yeah, it was working fine and already installed for me. I DID have to flash it to 19 after .34 though.
[Fire HD 8 and HD 10 Android Development] DragonFire1024:
It worked on the modified firmware?
[Fire HD 8 and HD 10 Android Development] GuyInDogSuit:
Yeah. v18.1 works, and 19 does too, I believe. I'm fairly certain I had 19 working on your .20 build.
[Fire HD 8 and HD 10 Android Development] tylerhole:
18.1 and 19 both worked on 5.6.1.0 but only 19 works on 5.6.2.0

Sent from my SM-G9650/DS running stang5litre Pie ROM