yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Mine did that with my phone's hotspot. Didn't work, then suddenly did for ten minutes, then stopped working, then worked again, then off again. Rinse and repeat.

I wouldn't know where to start. Change a bin to a zip? You've lost me there. Hope you figure it out though.

Anyone try any of the modules for Magisk? I'm curious what works and what to avoid (causes bootloops or errors)?
[Fire HD 8 and HD 10 Original Android Development] Michajin:
I just changed the .bin to .zip and it worked just fine.

I have installed youtube vanced and gravity box. I did some slights mods with the status bar and changing the framework to have advanced boot options. It is pretty safe to try mods as long as you have a current backup.
[Fire HD 8 and HD 10 Original Android Development] lemmeinyo:
Hello, and thanks for the work on this device! This thread inspired me to buy one :D

Unfortunately, I am having trouble running the tools. Step1.sh didn't work on either of my linux mint computers. I did finally get it to run on a Debian virtual machine (seemed to work/reset tablet), but Step2.sh just hangs with no output, and no effect on the tablet. I'm at a loss about where to go from here. Does anyone have a suggestion?

I started this process with a fresh-out-of-the-box fireHD10. I placed the 64bit mtksu as mentioned in the op.

Edit: Nevermind, haha. It was an Ubuntu virtual machine that worked for step 1, but I did just get a Debian machine to successfully run step 2. Currently in TWRP :) Thanks again.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
I don't think it uses the 64-bit one. Iirc, I put both in the bin folder and things worked fine. Using Ubuntu 18.10 x64.
[Fire HD 8 and HD 10 Original Android Development] lemmeinyo:
Hmm, it wasn't obvious to me which one was needed (I assumed 64), and with all the trouble I was having, I did swap them a few times! Maybe I ended up landing on the other one accidentally? How did you put them both in the bin folder? You must have had to rename one of them.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Whoops, my mistake. I seem to be mis-remembering things here. Make sure you're putting the binary in the correct bin folder, and you're running the commands from the folder with the scripts in it. What does your folder structure look like? What errors are you getting, if any? Also, what distro, build, version, etc?

I used a persistent USB live Linux build of Ubuntu 18.10 x64, which I can help you set up if needed. In fact, I think a lot of people would benefit from having those instructions here as well. Someone linked to a page earlier regarding this. We could add it to the OP. What do you think, [MENTION=7104332]k4y0z[/MENTION]?
[Fire HD 8 and HD 10 Original Android Development] coilmaster949:
Hi folks, I was on another and jumped here by topdog recomendation! hope to get clarity for noobs like me...so here's what I understand but still have some gaps. Maybe someone can quickly edit this/ and OP can also use it to add as a step by step for other noobs.

1. Create a bootable Ubuntu USB thru link above, then reboot PC into USB's Ubuntu environment. Then connect Fire HD 10 to PC .

2. :confused: Which app do I open or where command prompt/ where exactly in ubuntu do I fire these commands? Do some files need to be downloaded (from where) before doing these like python, docs2unix etc?

"sudo apt update

sudo add-apt-repository universe

sudo apt install python3 python3-serial android-tools-adb android-tools-fastboot dos2unix

Then follow rest of steps in the OPs post, which will complete with TWRP flash and boot into TWRP.

3. From where/ how shd. I best install Magisk -

4. What commands to execute where to disable OTA now?

5. Then follow https://xdaforums.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603 and then Nova launcher and that completes it..Right?
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
1. Correct. You're on the right track.

2. Sorry, I guess the OP doesn't mention this, but you'll need to enter the commands in the Terminal app.

First run those three commands, then plug in your tablet and run "adb devices" with USB debugging enabled. It should ask for perms on your tablet screen as it does with Windows. Grant permission, then run the scripts as per the instructions.

3. IF you are on FireOS 5.6.2.0 or lower, you can install a pre-rooted ROM. Once you have TWRP installed, you can reboot back into Windows on your PC, then jump to THIS thread and grab a pre-rooted ROM from the first post (I recommend v5.6.2.0), and copy it to your internal storage and install it via TWRP per the instructions. Easy peasy. Wipe and such, too. When you reboot, it'll have Magisk already installed. IF you are on a NEWER firmware, do NOT install that ROM just yet. Instead, grab the latest stable Magisk from HERE, and flash in TWRP. To reboot into TWRP, run the command "adb reboot-recovery." The Fire HD 10 does not have advanced reboot options by default.

4. You will not need to execute any commands as OTA is disabled on DragonFire1024's ROM. IF, however, you can't install it as you're on a newer firmware, then run these commands:

ADB shell
su
pm disable com.amazon.kindle.kso
pm disable com.amazon.kindle.otter.oobe.forced.ota
pm disable com.amazon.settings.systemupdates
pm disable com.amazon.device.software.ota

The first one disables "Kindle Special Offers," the app that presents ads on your lockscreen.

The other three disable the system update/OTA apps.

Another neat trick is that you can talk to Amazon and ask them nicely to disable the special offers ads on your device. They'll usually happily comply. Saves you $15.

Either way, once you're rooted, follow the steps to install Google Play Store services, turn off, power on, and go from there to install Nova and so on. I've attached Launcher Hijack as well, you'll need that to switch to Nova Launcher. When you run it for the first time, scroll down to "home button" or something of that nature, and enable the accessibility service for that. Every time you update Nova Launcher, you'll be presented with the launcher selection screen again. Not a huge deal though.
[Fire HD 8 and HD 10 Original Android Development] coilmaster949:
Alright my friend, lemme get started with this guide and I'll know more (bottlenecks) when I go thru steps.

I hope I can count on paramedics :D like urself and others standing by in case undesired results happen. If all goes well, I'll update as a guide for others to follow.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Good luck, and have fun!
[Fire HD 8 and HD 10 Original Android Development] Yamaraj:
Or,

1. You can install Google Play Store

2. Launcher and keyboard of your choice [important], and

3. Script Manager or any app that can run scripts

Then either type these commands in adb shell or execute the script file on the tablet itself (as superuser).

pm disable amazon.alexa.tablet
pm disable com.amazon.advertisingidsettings
pm disable com.amazon.ags.app
pm disable com.amazon.alexa.externalmediaplayer.fireos
pm disable com.amazon.avod
pm disable com.amazon.calculator
pm disable com.amazon.client.metrics
pm disable com.amazon.cloud9
pm disable com.amazon.cloud9.kids
pm disable com.amazon.csapp
pm disable com.amazon.dcp
pm disable com.amazon.dee.app
pm disable com.amazon.device.backup
pm disable com.amazon.device.software.ota
pm disable com.amazon.dp.contacts
pm disable com.amazon.dp.fbcontacts
pm disable com.amazon.firelauncher
pm disable com.amazon.geo.client.maps
pm disable com.amazon.kcp.tutorial
pm disable com.amazon.kindle
pm disable com.amazon.kindle.kso
pm disable com.amazon.kindle.otter.oobe
pm disable com.amazon.kindle.otter.oobe.forced.ota
pm disable com.amazon.kindle.personal_video
pm disable com.amazon.kindle.unifiedSearch
pm disable com.amazon.kor.demo
pm disable com.amazon.mp3
pm disable com.amazon.parentalcontrols
pm disable com.amazon.photos
pm disable com.amazon.photos.importer
pm disable com.amazon.platform
pm disable com.amazon.platformsettings
pm disable com.amazon.pm
pm disable com.amazon.precog
pm disable com.amazon.recess
pm disable com.amazon.redstone
pm disable com.amazon.settings.systemupdates
pm disable com.amazon.socialplatform
pm disable com.amazon.tahoe
pm disable com.amazon.tcomm
pm disable com.amazon.unifiedsharefacebook
pm disable com.amazon.unifiedsharegoodreads
pm disable com.amazon.unifiedsharesinaweibo
pm disable com.amazon.unifiedsharetwitter
pm disable com.amazon.vans.alexatabletshopping.app
pm disable com.amazon.venezia
pm disable com.amazon.weather
pm disable com.amazon.webapp
pm disable com.amazon.webview
pm disable com.amazon.whisperlink.core.android
pm disable com.amazon.windowshop
pm disable com.amazon.zico
pm disable com.android.calendar
pm disable com.android.contacts
pm disable com.android.deskclock
pm disable com.android.email
pm disable com.android.music
pm disable com.android.onetimeinitializer
pm disable com.android.protips
pm disable com.audible.application.kindle
pm disable com.goodreads.kindle
pm disable com.kingsoft.office.amz
pm disable jp.co.omronsoft.iwnnime.languagepack.zhcn_az
pm disable jp.co.omronsoft.iwnnime.mlaz

You won't need Launcher Hijack at all.

Attached: debloat.sh (removes most of Amazon stuff) and rebloat.sh (enables everything, obviously), zipped.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Ok so I was moving the tablet I bricked a week or so ago and decided to give it another go at fixing. Long story short, it's revived. I have no explanation other than power. I had unplugged the battery and forgot to plug it back in. When I did I shorted the point and it went right to bootrom, ran through the script without a hitch and booted to TWRP when it was done. I theorize that whatever caused this tablet to get into preloader, was reset when the power reserves was spent. In other words the battery had been totally dead before this worked. Very bizarre. I wonder if the same can be said of the other bricked one I have.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
I hope so! Now you have a dev unit (or two if the other starts working, too) and a daily driver!
[Fire HD 8 and HD 10 Original Android Development] coilmaster949:
So are u suggesting this...

1. Follow steps 1 thru 3 in GuyInDogSuit post above

4. Then install google play with play services. Then install launcher (nova) from play store.

5. Install "script manager by devwom" frm playstore.

6. Then:confused: where in script manager do I specify to execute as superuser for "executing ur script "debloat.zip"?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Either mtk-su should work.

Glad you got it solved, although I don't see how the battery could have anything to do with it, since it should be disconnected anyway when doing "bootrom-step.sh".
[Fire HD 8 and HD 10 Original Android Development] Yamaraj:
Yes. But only if you want to get rid of almost everything Amazon related, including their App Store, Kindle, Prime Video, Audible etc.

This is probably off-topic, but anyway. Use a USB cable to connect the tablet to your PC, then either extract the zip and copy the files to your tablet or copy the zip directly to tablet and extract using some tool, then launch SM, browse to where debloat.sh is, select it, enable "Su" (second button from left, next to Fav), select "is script" and click on run. Voila!

Do not forget to install a launcher and a keyboard (preferably gboard) before these steps, because the script disables the default Fire launcher.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
I would suggest running that rebloat.sh script, and not doing anything like that again. The tablet's Amazon ecosystem is fragile enough as it is. Just run the first disable command I posted earlier to disable KSO (Kindle Special Offers). OTA should already be disabled. Make sure Nova is your default launcher, and you should be good to go. If you're feeling brave, you CAN disable some apps yourself, just refer to THIS guide.

I don't see Fire Launcher on there, though. That should be safe to disable, I believe, as long as you have a replacement. Commands for that are:

adb shell
su
pm disable com.amazon.firelauncher

Yes. Static IP is the fix.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Set advanced WiFi hotspot options to static IP.
[Fire HD 8 and HD 10 Original Android Development] Yamaraj:
We have digressed enough from the original post, but I feel it important enough to point out that the problem may actually be the ROM, not the script. I have taken extra care in curating the list of apps and services to disable and all three Fire HD 10s are running absolutely well. Nary a problem in the last five days with dozens of different apps installed on each of them. I tried both the scripts again just for the heck of it, with zero issues.
[Fire HD 8 and HD 10 Original Android Development] coilmaster949:
thanks...that works to get a WIFI lock (thru static)

But how do I fix this DHCP Wifi locking issue?

if noone has been able to fix it before, at some point I'll prolly need to return this tablet and exchange with new one while I have time.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
It's not the tablet, it's a known issue with the ROM. A fix is being worked on. In the mean time, static IP should work well enough.
[Fire HD 8 and HD 10 Original Android Development] coilmaster949:
thanks...so I'll proceed with next steps.

Assume camera files etc. on this ROM are exactly same as stock - so the still and video quality will be just like Unrooted stock HD10?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I don't really get the point of the "optimized" ROM.

It's based on an outdated stock ROM, and apparently has issues with WiFi.

Why not just use the stock ROM and customize it to your liking?

Also please move further discussions about the ROM in the ROM-Thread.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Exactly and thank you.
[Fire HD 8 and HD 10 Original Android Development] coilmaster949:
ok- will move to ROM thread
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
To each their own and individuals should ultimately be left with making their own decision. I chose the outdated rom, because for the time being, that's where most of us ended up after unlocking. Secondly i wasn't sure it was even going to boot given the amount of tools, scripts and zips I have tried in the past 2years. I won't say how many times I passed up this tool too. The Wi-Fi issue really isn't an issue per se. I have spent a few hours today looking over the stock rom before extraction, after and upon completion of the build. I've found nothing yet. However, a setting does not make its presence known when I installed my framework and settings apks like it usually does. In developer options, an option usually appears right at the top, that has to do with 'checking DHCP' which is set to check only certain content by default. It should be checked to always, but the toggle hasn't appeared yet. If it's something inside the kernel, then I am lost. If it were a driver or firmware issue, Wi-Fi just wouldn't Work. But despite it being static IP, this is by far the best Wi-Fi connection I've ever had on these tablets.

I am still looking for the cause, but I suspect it's something quite simple and will probably kick ourselves of we find it. On another note, I have located the kernel tree for the HD 10 and Fire 7. Google actually has them on their site: HD 10: https://android.googlesource.com/kernel/mediatek/+/refs/heads/android-mtk-3.18 and the Fire 7: https://android.googlesource.com/ke...ds/android-mediatek-sprout-3.10-lollipop-mr1. This could be a time saver.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I haven't experienced any issues with WiFi on 5.6.3.0/5.3.6.4 stock ROM.

The kernel-sources you linked to are just the generic mediatek sources.

They will likely be missing drivers.

I have linked to working amazon-kernel sources for the HD10.

There are also working amazon-sources for the ford on my github, allthough they are a bit outdated.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I'm having a lot of trouble with the mt8173 7.0 source. It's probably mostly me, but it's just not in proper order and is a headache. Now that we are unlocked, perhaps the kit I have and linked to in the past, is now in order. I'm hoping Amazon just picked the kernel clean and didn't restrict anything. I tried to compile a kernel for my xt907 and I couldn't add any additional modules on the stock kernel. Im also aware the likelihood of having all the drivers is slim. Sigh mediatek. At least we have something to work with. I have owned a few burn-a-phones before that didn't make sense at all. Be lucky we aren't stuck with an endless array of overlays for the overlays. When I say overlays, every app and activity had at least one overlay to accompany it.
[Fire HD 8 and HD 10 Original Android Development] sga999:
I used this method to create a persistent USB drive with Ubuntu desktop version 18.0 4.2 LTS. However, it does not seem to be persistent. I have copied a file to the desktop or to other folders. But if I choose either restart or power off and boot the Ubuntu USB drive back up, the file is no longer there. And none of the sudo commands persist. Is there some other way I am supposed to shutdown in order to make this work? I definitely gave it the persistent option when running the install procedure given in that link. Apologies for the question, but I haven't used Ubuntu.

EDIT: More detail, nothing persists. Not my wifi-connection, not the date and time, etc. Was the Ubuntu version that I installed an incorrect one? My laptop has a 64-bit processor.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Please move this OT monolog to one of the ROM centric threads.
[Fire HD 8 and HD 10 Original Android Development] Wall.swe:
I also used Ubuntu 18.04. LTS and my installation became persistent. I have tried it several times and every time I get a persistent installation(it remembers WiFi etc.). Did you do all the steps in the guide? Have you tired to redo the procedure?
[Fire HD 8 and HD 10 Original Android Development] sga999:
Yes, I tried it several times, all of them failed. The documentation seemed to say that when booting Ubuntu, there would be a menu which would allow me to pick the persistent way. I do get some sort of a menu, but persistent is not on it.

I am using a 16GB USB drive. And when it asks how much of it I want to use for persistent, I moved the slider to the maximum for that size drive, which is 4090GB. Is that similar to your setup?
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
What did you use to create the drive? LiLi (Live Linux USB Creator)? And yes, the 4096 MB is the standard max setting. That is 4 GB.
[Fire HD 8 and HD 10 Original Android Development] sga999:
Yes, I used the tool that was mentioned in the link that you referred to, I.e. Lili. My size was 4090 because that's the max the slider would allow.

I went ahead with this procedure of installing TWRP, despite the fact that I couldn't get this to be persistent. I'll be trying to figure that out in the next few days, but at least I got the important part done.

---------- Post added at 07:33 PM ---------- Previous post was at 07:26 PM ----------

That thread refers to the Fire HD 8 2018. Is there an equivalent for the Fire HD 10 2017, i.e. for SDK 23? I'm talking about the part in post 2 about installing Xposed.
[Fire HD 8 and HD 10 Original Android Development] bibikalka:
You know, I ran into some systemless Xposed issues recently, and I would recommend following this old approach instead:

https://xdaforums.com/hd8-hd10/general/xposed-framework-fire-hd-8-6th-t3549043

You will have Xposed sitting in /system, and that is known to work without issues. Magisk, on the other hand, can be systemless.

FYI, I had some weirdness like this on an Mtk phone: https://github.com/rovo89/XposedBridge/issues/200
[Fire HD 8 and HD 10 Original Android Development] DB126:
Systemless Xposed is akin to managing a barrel of monkeys. Good for awhile then weirdness strikes. Eventually most give up or revert to a traditional install. Well, at least those that value stability over the daily hack.
[Fire HD 8 and HD 10 Original Android Development] sga999:
Thanks. But I had tried that old approach before asking about the way in your recent link. But maybe I will try again soon.
[Fire HD 8 and HD 10 Original Android Development] speaker1264:
Does this exploit allow us to install any version of Fire OS from TWRP without the risk of bricking the device, including downgrading? If so, then is there any real reason to disable OTA updates?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I am not prepared for magisk. I need to learn more about it. For me, and the work I do across many devices at any time, /system works better. Magisk is not for a device that I use for experiments in the system. With that said, I was unaware of how cool it is. It brings back the fun of rooting, while keeping it serious at the same time. That's why these modules are so cool because of the Quality of the work that goes into them, while keeping it real, and fun.

---------- Post added at 09:15 PM ---------- Previous post was at 09:14 PM ----------

The simple answer: no.
[Fire HD 8 and HD 10 Original Android Development] sga999:
A new software update was just downloaded to my Fire HD 10. The device software OTA APK was already renamed, and I also had changed the build version number in build.prop. With those changes, I had assumed that the update would not even download, but it did. So were those two changes just for stopping it from installing, but not stopping it from downloading?

Anyway, I have already accomplished the procedure in this thread for installing TWRP (and I was already rooted with mtk-su). I'm wondering about how to proceed. If I rename this update to have an extension of zip, can I just flash it in twrp? I think there are no worries about the bootloader files. But will root be gone?

EDIT: I was writing that while another post came in above. It mentions downgrading and the risks involved. Since I would not be downgrading, I believe that is not an issue when installing this update. But I still want to know about the status of root once it is installed.
[Fire HD 8 and HD 10 Original Android Development] speaker1264:
So what is the best method to disable OTA updates after this? I was able to use SU to disable them, but not uninstall them. I was afraid that they would turn back on after a restart or something. I know you have the custom firmware that disables them, but I don't really like having to set a static IP to get wifi to work.

edit: I just went with the disable option, hopefully it works good enough. I mean, I guess there really isn't a reason not to update, but who knows.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
I would like to know this too. I was sure that running the "pm disable" commands should do it, but the update seems to have restored the OTA apps. I DO know now, though, that the best thing to do before flashing any updates, is to disable or completely delete your WiFi hotspot info before continuing, so that it can't update when it reboots. Gives you time to disable the damn OTA stuff in the mean time. In my case, when I flashed 5.6.3.4, it gave me a message about the new hands-free Alexa, then showed the orange Fire screen "checking for updates... downloading updates," but then didn't install anything. Whew. Don't know WHAT the update was, but for sure, I'm glad it didn't proceed.

As far as OTAs go, there was another method of disabling them that I read up on. Renaming the "otacert.zip" file in /system/etc/security, seems to bork updates as well. I don't know if it can be restored via flashing an update, possibly. So it's best to disable WiFi before doing so as I mentioned above.