yashsingh1/xdaforums huggingface dataset:
[Fire General] Technocian:
So I got one with 5.3.3, but it was so cheap I'm willing to live with it. I know root isn't available (yet, or never will be, well see), but what can I do on this OS version to make it more erm... palatable?

I was thinking:

-Install Play Store

-Install and run Nova Launcher as default launcher

-Kindly ask Amazon to remove lock screen ads

Anything else we can do? I know I can't uninstall most of the default apps without causing issues on the system.
[Fire General] DB126:
Could install a software firewall in an attempt to block OTA updates and other Amazon downloads. Not sure it's worth the effort and overhead (tablet and your time) given it won't improve the user experience.

As an aside, earlier today a previously unknown user claimed success rooting several 5th gen devices running FireOS 5.3.3.0. Still trying to replicate/verify those claims. Watch this thread for updates.
[Fire General] Technocian:
Anyone know how to load PDFs and have it show up under the Kindle app? I've tried adding it to every related folder in my Internal Storage, but the only thing that the Kindle app shows are purchased books. On stock Android, you can just add the PDFs to the kindle folder and there's an option to sideload content in the settings that is missing now.
[Fire General] DragonFire1024:
If your device's bootloader isn't unlocked, you can't sideload anything. As for the Kindle app, does it already allow PDFs? I never been in the app nor have I ever used it.
[Fire General] DB126:
Believe poster was referencing option to import content from another location (eg: internal storage) when using the term "sideload".
[Fire General] Technocian:
Yes, that's what I meant. When I add PDFs to my device through USB it shows up in the Documents app, but not the Kindle app like how it would on any other Android device.

Also, now that we've established that 5.3.3 rooting was a troll post, I honestly don't mind the stock OS that much. I'm a guy that ALWAYS roots, installs a custom kernel, and overclock my devices to get the most out of them.

I had Amazon turn off the lock screen ads by simply emailing them and asking, moved all the Amazon apps I didn't need into a folder and deleted their cache so they wouldn't auto load anything, and then I installed Google Play Store. I've kept my installed apps to a minimum (only added Chrome, YouTube, Netflix, and SwiftKey). This thing runs perfectly fine.

Well worth the 25 bucks so far.
[Fire General] drasnah:
I'm not following removing the ads by emailing 'them' and asking them? Serious question here, because I was just about to attempt rooting 5.3.3 by trying to downgrade the firmware to 5.3.1. *was going to test it on another kindle thats fairly broken first, because i suspect it will brick*

All i really want is those d*mn ads gone and to be able to run google play apps, because just getting .apk's doesnt seem to want to work on anything with these latest fire updates.

I really appreciate any help you can post here, and I bet others may need it as well.

You guys have a really cool community here; its much appreciated.
[Fire General] Technocian:
Just email amazon customer support. You can do it online or you can do it on your tablet. Pull the notification drawer down, there will be a help shortcut for you to tap, hit call/email for help, on the next screen it'll ask for your phone number, but if you look into the upper right there's an option to email them instead. Do that, ask them kindly to turn it off. Viola.

They respond fast, within a few hours. If you can't figure it out on your tablet just go on their website and look up their contact email.
[Fire General] drasnah:
I am totally amazed. I assumed I was stuck forever with those lock ads unless I rooted.

Thanks!
[Fire General] DB126:
Yes it will (brick) - guaranteed. Glad you found another method to eliminate those pesky ads.
[Fire General] DragonFire1024:
I've been exploring every inch of my HD 8. Here's what I don't get. One of the most popular exploits, Dirty Cow, was supposedly patched correct? Thats one big reason for non root. Another is the addition of Selinux which essentially toggles the SU permissions with a flip of a switch.

I have a rooted Droid Razr M. I have been adding tweaks to the build.prop for a day or two when I haven't been exploring possible root options for this tablet. It just occurred to me to take a look at the HD 8 build.prop. According to the prop, Selinux is disabled:

ro.kernel.zio=38,108,105,16

#ro.kernel.qemu=1

#ro.kernel.qemu.gles=0

ro.boot.selinux=disable

Secondly, I very well could be reading this wrong, but according to 'Droid Examiner' the Kernel was compiled BEFORE the exploit was patched?!?!? See attached screenshot)

So can I ask what exactly is the problem?

I did more digging and found out my Fire 8 HD has a Kernel version that has NOT been patched with a fix for dirty cow.

Kernel/Linux Version: 3.18.19

OS: 5.3.3.0

So what would stop this exploit from working? I legit don't know.
[Fire General] BeeWall:
Some devices just aren't vulnerable. Also, they could have backported the fix. It says the kernel was compiled March 3rd, 2017.

Not sure about SELinux, maybe they have other ways of stopping access?
[Fire General] DragonFire1024:
There arr only certain versions of the kernel that are patched and supposedly mine isn't one of them. I think the date refers to when the OS updated.

Unfortunately I am still learning and haven't been able to run any scripts as I am still not sure how to. So I can't test any of them.
[Fire General] DB126:
Very likely Amazon nuturlized the exposure via some means that didn't involve recompiling the kernel. Don't put too much stock into that 2014 stamp.
[Fire General] crazyates:
This. This is technically only Android 5.1.1, but it's been patched by Amazon many times over. All the usual exploits that would work on a stock Lollipop don't seem to work on our Fires.
[Fire General] DragonFire1024:
Oh I don't. It's too close to call. I would have to do a factory reset to see if it changes at all. If I can't some how come up with some way to root or hack this thing, I may just do that so I can activate an app and make is 'DEVICE_OWNER' so it can pretty much put a stop to at least a few of the most irritating apps. After all the jumble of accounts and weird profiles in my Activity Launcher findings, I doubt I will ever actually be able to 'sign out' of or release all accounts from this thing.

---------- Post added at 10:07 AM ---------- Previous post was at 10:04 AM ----------

I have a few ideas I am working on. I have to do a bit more research though, before I take any actions. I just hope I'm not the only one out there trying! :P
[Fire General] DB126:
A factory reset will do nothing aside from erase your personal data as it does not touch the system partition. Nor will you be able to alter device owner (for the purpose of stopping system apps) on an unrooted device. As for others working on root solutions folks familiar technical working of Android have already taken a sniff and moved on to more fertile ground. Hefty bounties offered by Google in the past year have sealed up many exposers due to sloppy coding. Took Amazon a little longer to catch up. The days of easy rooting are behind us.
[Fire General] DragonFire1024:
I never thought for a second this would be easy. Definitely fun trying though. Well at least it is for me as I haven't screwed up too much yet.

Apparently there is a way to make an app DEVICE_OWNER. You have to make sure all accounts connected to the ownership or registration of your device are signed out and removed. The best way to do that is a factory reset. Then supposedly you can take these steps (see app description):

Will it work? No idea. But I've really been putting off trying.

---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------

Also according to Google:
[Fire General] kazeron2003:
I can install app from Google store, but I can't run them.

Hi, I have just purchased a new Kindle Fire 7. I installed the Google Play Store, and I can install apps from Google Play Store also. BUT I can't run those apps.

May someone please helps me slove this problem? Do I need to root my Fire or I lack some install files?

How can I run apps from my google play store? :rolleyes::rolleyes:
[Fire General] DragonFire1024:
Make sure you installed all 4 apks. Account Manager, Framework, Play store and Play Services.

---------- Post added at 09:10 AM ---------- Previous post was at 09:08 AM ----------

Install in this order: Account Manager, Framework, Play Services, Play store.
[Fire General] DragonFire1024:
Possible root method. Not sure if it works or if it applies to just the Fire 8. Thought I would let you guys here know though: https://xdaforums.com/hd8-hd10/general/root-method-t3619242
[Fire General] chwiejak:
Hi, did you tried this method?
[Fire General] DragonFire1024:
I haven't yet. I just had a possibly brilliant idea that I want to try first. I may try it today.
[Fire General] DragonFire1024:
this is an old method. I am not sure for what Fire version or model. I need to know the number for the USB driver. Would be something like 0x1949 (which is the VID listed like the one the link tells you to add). So I did try it, and got nothing. I had to update the ADB set for superoneclick too.
[Fire General] DragonFire1024:
I keep getting this notification from Kingroot. I click on it but it doesn't tell me anything. This is the first time I was able to screenshot it as it usually disappears after a few seconds.
[Fire General] DB126:
KingRoot is borderline malware. It is only recommended for those intending to immediatlely wipe their device and install a custom ROM although some use it as a permanent FireOS root solution. Risky choice IMO.

I understand your primary device is a 6th gen HD 8 (not sure why you continue to post in the 5th gen forum) running an unrooted build of FireOS. Given there are remnants of a failed rooting attempt I'd take steps to refresh/reload FireOS.
[Fire General] DragonFire1024:
Because I have both devices. Also because most of what I'm trying to do relates to both. I also don't use my fire 7 really.

I'm thinking of restoring anyways. Given the fact I can't find anyone willing, or no one will come forward, to help with my idea that could get us root. That's all I want to do is get what we all want.
[Fire General] DB126:
Probably best to post in the HD 8 forum if that's your primary. Despite aesthetic and ROM similarities the devices are not identical - especially when it comes to root. So far a simple launcher exploit (stretching definition of that term) and Play Store installation are the only items of shared interest.
[Fire General] TimSC1:
Stack Clash

Can the Stack Clash vulnerability be applied to 5.3.3.0? It seems to affect most recent Linux versions.
[Fire General] DragonFire1024:
Never heard of it. Links?
[Fire General] der-mali:
Hallo,

just a remark: my Fire Tablet 2015 has been updated to Fire OS 5.4.0.0 this week.

Regards,

Thomas
[Fire General] TimSC1:
I'm too new a user to post links, unfortunately. The Stack Clash vun was publicly reported on 19th June on the qualys.com blog and has since been reported on many other news outlets. It is a privilege escalation bug in Linux and several BSDs. The recent release of Fire OS 5.4.0.0 came out it early June, so it might be vulnerable as well.
[Fire General] DB126:
Vulnerability = weakness

Exploit = something takes advantage of weakness
[Fire General] chwiejak:
So it could be way to root 5.3.3?
[Fire General] DragonFire1024:
Someone has already made a script. If you know what to do from here, go for it. I don't have a clue. This was posted a few hours ago BTW. I think it's the first one. I cannot find any reference to it having been tested yet.

---------- Post added at 06:03 AM ---------- Previous post was at 05:58 AM ----------

Here is a link where the company who found it, describes how they used it to gain root...even on **ANY** SELinux enabled devices.
[Fire General] DB126:
A little far fetched IMHO. Proof of concept and carefully crafted lab exploits don't equate to practical solutions. List of caveats is lengthy. If there was/is creditable threat the overly dramatic click-bait driven media will be all over it.
[Fire General] chwiejak:
Any progress with rooting?:)
[Fire General] rorytmeadows:
Prodding our contributors? Not cool. Be patient.
[Fire General] chwiejak:
Hello,

Is there any news wirh unlock 5.3.3?

Thanks
[Fire General] supesman:
current version of fire 7

The current version of amazon fire 7 is 5.4.0.0

---------- Post added at 12:56 AM ---------- Previous post was at 12:47 AM ----------

to update amazon fire

Swipe down from the top of the screen and then tap Settings.

Tap Device Options, and then tap System Updates.

If you have the latest software update, it should look like this: Your device is running Fire OS 5.4.0.0.

---------- Post added at 01:00 AM ---------- Previous post was at 12:56 AM ----------

Swipe down from the top of the screen and then tap Settings.

Tap Device Options, and then tap System Updates.

If you have the latest software update, it should look like this: Your device is running Fire OS 5.4.0.0.
[Fire General] DB126:
You asked the same question earlier this month. Rest assured there will be plenty of forum activity if a root exploit is found for those running FireOS 5.3.2.1 or higher.
[Touch Cruise ROM Development] J Fortes:
Help. How can I activate the Letter Recognizer Input Method in Cruise? It doesn't even show as an option. Thank you
[SuperSU] infinatious:
I am trying out the Android O Developer Preview on my lovely Nexus 5X and cannot get SuperSU to work. Is there any way to get SuperSU to work on Android O Developer Preview 1?

EDIT: Looks like Chainfire is working on it. Oh goody.
[SuperSU] crisis_trustee:
Try, try! :laugh:
[SuperSU] ijustyce:
me too, nexus 6p, can anyone help
[SuperSU] imknown:
Wait just like we tasted the M&N?
[SuperSU] JimSmith94:
Chainfire says he's working on it in his beta thread.
[SuperSU] SilverFlash:
Well well, guess there is gonna be another root war in late August or early Sep lol
[SuperSU] ijustyce:
for 5x and 6p users , please see https://xdaforums.com/showpost.php?p=71561057&postcount=9345
[SuperSU] imknown:
It works, ty.

:D
[SuperSU] StakMak99:
Thanks, Finger's Crossed.... I'M GOING IN.......
[General Questions and Answers] davidhk129:
Hi, I just bought a DZ09 smartwatch. No complaints.

But, I cannot see from settings or anywhere to find out the status of the battery.

So how do I know WHEN to recharge ?

Thank you.
[ZTE Axon 7 Questions & Answers] mvortex3710:
Looking at the 7.1.1 leak post, it seems that a few people have experienced this too but after both clean flashing and dirty flashing 7.1.1 over 7.0.0 I've noticed Dolby Atmos has stopped functioning correctly. I can turn it on and hear a difference but none of the in-app settings appear to work (although I can toggle them) and the equalizer doesn't move at all.

Has anyone had this problem and managed to fix it?

Kind regards

James
[ZTE Axon 7 Questions & Answers] joaste:
I had the exact same thing. I just flashed back to 6.0, mainly because of battery life which is slightly better. Atmos works again.

I also had the Wi-Fi icon in quick settings that would not turn off even though Wi-Fi was off.

A few too many weird things that indicated that 7.1.1 is not big free.

Neither is 6.0 of course. No battery stats? How did they screw that up?
[Google Pixel Questions & Answers] Benjamin1966:
Has anyone tried to connect a monitor to a Pixel? I'm seeing monitors on Amazon that connect via usb and usb powered. It would be great to watch a movie with my pixel and a external monitor. I searched the forum without any luck.
[Android General] dimitris1967:
Please help...can I make a update samsung i8260 and error nand ...
[Samsung Galaxy S7 Edge Questions and Answers] shorty76:
Hello somebody here know why the fast charging is not working on a Samsung Galaxy S7 Edge
[Samsung Galaxy S7 Edge Questions and Answers] peachpuff:
Are you using the original charger?
[Samsung Galaxy S7 Edge Questions and Answers] shorty76:
Yes
[Samsung Galaxy S7 Edge Questions and Answers] peachpuff:
Try a different cable maybe.
[Samsung Galaxy S7 Edge Questions and Answers] RanSauce:
Check in your battery settings, there should be a Enable Fast Charging Toggle there... you can check if its off... otherwise, I'll get on to searching for another fix
[Galaxy Note 4 Accessories] Bruno Rodrigues:
Hello,

Anyone had any luck in buying or testing one cheap MHL cable with mhl 3.0 specification? I've bought one e-bay but it was a fake one, only 2.0 specification sold as a 3.0.

The fake one: http://www.ebay.com/itm/142239281666?_trksid=p2057872.m2748.l2649&ssPageName=STRK:MEBIDX:IT

I have a 2.0 mh cable but the major disadvantage is that my Note 4 discharges at a faster rate than the 500mA of the 2.0 specification is capable of.

The original Samsung is on the expensive side. I'm avoiding that one.

Any ideas in how to connect it to a TV with quality and hassle free? Some sort of dock maybe?

Thank you and best regards.
[Galaxy Note 4 Accessories] theantilag:
You can try miracast adapter and while you transmit you can charge the phobe
[Galaxy Note 4 Accessories] Bruno Rodrigues:
Thanks theantilag,

I've already tried that. It not very convenient because the sound lags and is not suitable to play games. Neverthless I use it often to show pictures.
[Magisk] ahrion:
Deprecated - Use the New ViPER4Android v2.7:

GO TO THE THREAD LINKED ABOVE. You don't need to flash any zips. Just install it as a regular apk, allow it to install the drivers, and you're good to go.

For magisk users: I made a zip on the repo that includes the original vdc's and my profile converter (will convert your old profiles to the new and better format).

For rootless users: I made a zip to install drivers and such

Zips can be found here

ALL SUPPORT QUESTIONS FOR 2.7 SHOULD BE AT THE THREAD ABOVE.

This is ViPER4Android FX and Xhifi Unity installers

These installers utilize my Unified installer that can install on Magisk OR System if Magisk is not detected (with

Pixel

support).

Credits of Originality:

- @zhuhang (Official Thread)

- @Osm0sis

- Viper's Audio (Official blog)

- @ViPER520

- @Team_DeWitt

Special Instructions:

If you already know which original v4a you want to use, just add 'old' for 2.3.4.0, 'mid' for 2.4.0.1, 'new' for 2.5.0.5, or 'mat' for material to the zipname prior to flashing.

If you already know if you want it installed as a user or system app, add "uapp" for user app or "sapp" to system app to zipname.

If you already know if you want to apply the libstdc++.so lib workaround, add "lib" or "nlib" to zipname (note that there are some devices that are already known to require it and so they'll apply workaround regardless of choice)

If you already know if your device/rom requires the v4a open/close/fc audioserver workaround, add "ocw" to zipname. Otherwise, add "nocw" to zipname

To skip volkeys (if your device isn't compatible with them), add "novk" to the zipname. Note that if you don't specify the above, defaults will be applied which are: sapp, new

Make sure there are no spaces in the zipname

Audio Mod Troubleshooting Guide

Downloads

XDA:DevDB Information

ViPER4Android FX Legacy/XHiFI [Unity], App for the XDA Community Apps

Contributors

ahrion, Zackptg5

Version Information

Status: Stable

Current Stable Version: v4.4

Stable Release Date: 2019-08-11

Created 2019-01-18

Last Updated 2020-01-01
[Magisk] huaiyue:
great!
[Magisk] kartikb:
Hi, tried your two modules you've posted on my Nexus 6P stock ROM. March update. Both causing bootloop and using the uninstaller provided doesn't help. Have to use mount Magisk then go to file explorer in TWRP recovery and delete the modules from Magisk folder.
[Magisk] ahrion:
Hmm. This is probably a kernel or magisk limitation with your rom. Are you running 11.6? Try to run it without the deep_buffer Remover because this is probably what bootloops your phone. It's only necessary when you've NEED it, otherwise it may cause adverse effects. Just install V4A and see if it works.

Currently magisk still has limited boot.img compatibility which causes so.e mods to not work properly or bootloops when it's not the mod itself.
[Magisk] kartikb:
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.

Thanks anyway..
[Magisk] ahrion:
Magisk limitation. [MENTION=4470081]topjohnwu[/MENTION] is always improving magisk. I do recommend may e trying another kernel for your device which may help compatibility.
[Magisk] Didgeridoohan:
Gave this module a go, and: it's a no go... Will not boot on my Nexus 6 running Vanilla ROM 7.1.1_r26, Franco Kernel r65 and Magisk v.11.6 - MagiskSU.

After flashing uninstaller the device still doesn't boot. Had to manually remove audmodlib from /magisk in TWRP to make it boot again. And it's in audmodlib the problem is. I did a quick test where I removed audmodlib after installation (kept v4afx in place) and it booted right up (with a non-functioning module, obviously).

Attaching installation and uninstallation recovery logs. Unfortunately I'm not at a computer with ADB, otherwise I would have captured a logcat of boot for you. Maybe later...
[Magisk] ahrion:
The only real thing in audmodlib is could be is service.sh or system.prop otherwise it would be the vendor file, which would mean that for some reason 11.6 is bugged for vendor file mounting. Try installing and remove those ONLY and and see if it fixes it.

If that fixes it then it's one of those two. And if you're cool can you see which one it is exactly.
[Magisk] Didgeridoohan:
There has been an issue with vendor mounting in Magisk, but I believe that was for devices with separate vendor partitions (Nexus 6P, Nexus 5X, etc). I haven't seen any commits on GitHub about it though (although I haven't been keeping that close attention), so I don't know if it's been fixed.

I did find the culprit though: it's system.prop. With that file removed from /magisk/audmodlib my device booted up just fine.
[Magisk] Seyaru:
If you wanna try this is my module for Nexus phones. I use this in my Nexus 5X Stock and PureNexus

https://www.androidfilehost.com/?fid=529152257862713260

Sry ahrion for use your thread
[Magisk] ahrion:
You are literally advertising your mods in everyone's threads. Stop this and make your own thread.

This is a magisk forum, not a system mod forum.
[Magisk] ahrion:
I will remove it with next release. Thank you man. This **** only started happening with 11.6. this was the reason Atmos was boot looping as well so I removed system.prop in Atmos.

Can you do me a favor and remove a few lines to see if it's just the specific lines? I think that certain lines don't play nice with your phone.

Remove the first part, low power audio tweaks, reboot and see if it works. If it doesn't then that's the culprit. If not then remove the first two on the other audio tweaks.
[Magisk] kartikb:
Hi there, thanks for the suggestion. I've tried it already and it didn't work. Asked for drivers to be installed when I opened the app after installing the module and restarting the phone.
[Magisk] ahrion:
Enable permissive.

Turn off audiofx
[Magisk] kartikb:
I'll try again when I get a chance to. Thanks for the suggestion.
[Magisk] ahrion:
[UPDATED] ViPER4Android FX <2.5.0.5>

v1.1:

- Updated to Audio Modification Library (Magisk) v1.1

This should fix the boot loop issues seen in only Magisk v11.6

Download: Link - Mirror

Previous Changelogs (Unified installer):

V1.0:
- Initial release
- Smali edits to automatically enable storage permissions
- Audio Modification Library v1.0 is included
- Unified installer that will install mod for both Magisk and System
- Pixel support included
- Magisk Template v3 support
[Magisk] ahrion:
Try 1.1.
[Magisk] kartikb:
Thanks, I'll give it another go and report back.

Update: my phone reboots into Android fine now however it doesn't process audio on phone speaker.
[Magisk] ahrion:
Flash my deep buffer remover. Look in the magisk forum.
[Magisk] Gigobaito:
Mind sharing your profile?