Search results

As stated in the OP you quoted, your device has dm-verity. You will not be able to force the system read write, without unlocking the bootloader. Follow this post to achieve permanent root/bootloader unlock...

I flashed this zip, recommended by another user in one of the Suez threads: https://forum.xda-developers.com/devdb/project/dl/?id=13100

https://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294 This thread has some good info on getting driver's set up correctly. Helped me out when I had a similar issue. Obviously you'd use the correct firmware for your device instead.

Vendor is currently being used by the Lineage Builds, so it helps to back that up when switching ROMs. It's unnecessary for FireOS though.

The sleepywifi app is a good call, much easier to change back and forth. Yeah, I added percentage, couldn't find the circle. Which version of EdXposed is working best for you? And the SD card was used as removable storage previously. I've noticed that issue before in cards that were used as...

Thanks for the ROM! It's very snappy and responsive. This is definitely about as stable as LOS 14.1. I have a bunch of comments/observations which may or not make sense, as I have never used stock Oreo or LOS 15.1, only Samsung's rendition. -As stated previously, Prime Video doesn't work...

I didn't think you could do that without ability to modify system partition? Never tried though.

Magisk can be installed to obtain Bootless Root, if you follow the linked instructions. It's relatively permanent, but Root doesn't start at boot, so there may be some issues with modules there. The other limit is that you can't modify the system partition since the bootloader is locked, and...

Done! Thanks for the great work.

Does it recognize your other devices in fastboot mode? If I recall correctly WLS doesn't work with fastboot. Something related to USB devices without storage. I'd try booting Ubuntu using a USB stick with persistent storage.

Did you update all of the repositories the post calls out? Also, how are you accessing Ubuntu? Lastly, I'm sure you've checked this, but make sure it is a Douglas.

Have you tried messing with Chrome's permissions? I've had issues in the past until I manually went into the settings, and enabled google account + some other permissions for Chrome, and then restarted. Sometimes it just takes time for whatever reason.

https://forum.xda-developers.com/showpost.php?p=81024051&postcount=88

https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 Install it via Magisk, open a terminal emulator, run "props", and follow the instructions. Choose the fingerprint of known devices that pass these checks. I typically go with the Nexus 7 2012 for my fire tablets.

Yup that works. You can also download the .zip directly to the tablet.

Using this method only disables the packages for user 0. They are still active at a system level, and are capable of restoring themselves. Amazon has always done this. You could potentially run a startup script with init.d script support, or run it however often the packages restore. adb...

I don't believe there is any recovery software for these. Opening the device shouldn't be too bad, and is probably your best bet. The other option is to try and flash a recovery image via Fastboot. That's how I'd do it on other devices, but i'm not sure how it'll work on the Fire without...

Sounds like you wiped your recovery, as booting to the orange logo usually means a soft brick (which is fixable via flashing firmware in recovery). In this case, with no recovery, it'll be a bit more tricky, as you'll likely need to take the device apart. Try following the method below...

Not sure if this is US only, but they're currently on sale for 100 bucks, with or without Prime!

Just something I wanted to share about OMX: I noticed I'd been having issues using the Live Display (blue light filter) and playing videos on certain apps. Once I turned on Live Display, the video would go black. Flashing the 14.1 OMX fix from the Suez Lineage 14.1 thread fixed that issue. I'd...

These devices tend to lag if you add GApps, without debloating FireOS. The 10 is definitely quicker than the 8 though. I would recommend at the very least, debloating FireOS (there are guides on this forum on how and what to remove). The other alternative is to install Lineage. These devices...

You were unable to get root with mtk-su, as your firmware had it patched. Downgrading using the method you did, will brick the device. You'll need to run the unbrick procedure, which involves taking the device apart. It will also give you TWRP, so you can flash the ROM. Also please move all...

I've used this thread by DB126 himself with good success: https://forum.xda-developers.com/amazon-fire/general/root-advanced-tuning-t3711462 I'd also recommend this apk for modding parameters: https://forum.xda-developers.com/android/apps-games/approot4-0-ka-mod-reborn-v18-t3714105 My...

This is the link to the test build from August 26th: http://github.com/mt8163/android_device_amazon_karnak/releases/download/1.7/lineage-16.0-20190826-UNOFFICIAL-karnak.zip I haven't seen any later releases on github.

I didn't realize they messed with cores and frequencies and still called it the same SoC? Just curious, what's your source for MT8163?

You are running the newest firmware, with mtk-su patched. The OP method will not work. You will need to follow the method in either post 2 or post 50.

Isn't that the same SoC as the HD8?

There's a new Fire 10 coming out, with an Octacore processor, USB-C charging, and FireOS based on Pie: https://arstechnica.com/gadgets/2019/10/amazons-new-fire-hd-10-tablet-costs-149-and-charges-via-usb-c/ I most certainly don't need any more fire tablets in my life, but this does look pretty...

Are the volume buttons reversed for anyone else?

This would only apply to FireOS. If you're running Lineage, why would you even bother with this?

Someone should check if the old kingoroot method for the HD10 still works: https://forum.xda-developers.com/hd8-hd10/general/hd-10-2017-offline-rooting-t3734860 May be the best way to root and unlock on the HD 10 until k4y0z figures out the software unlock, though he is pretty quick :laugh:

I don't think you're doing anything wrong. Your post just reminded me of a similar problem I was having with a different app, so I posted a logcat for review. Try reproducing your error and take a logcat.

I've been having no issues with those apps, but Instagram has been crashing on me. Logs reveal an out of memory error.

It's 636559820.

Had a friend running stock check. They received an update on September 13th :( Still 5.6.4.0.

That's a flagship level feature on a budget device :p

Rortiz2 congratz on getting it to work. I don't have my tablet for a few days, but am looking to forward to trying it out. Also based on the above quote, the ROM is 64 bit?!? That's awesome. Is there a plan to make the Karnak ROM 64 bit in the future?

Thhe operating info should give the build number, that corresponds to the version. I'll show an example later when I have access to my tablets. And yeah the HD 10 stock ROM is some odd combo of 32 bit and 64 bit. However, running ggow Lineage ROM provides a full 64 bit ROM, so things work more...

If you're not rooted, download DevCheck: https://www.apkmirror.com/apk/flar2/devcheck-system-info/devcheck-system-info-2-39-release/ Open the app and navigate to the System tab. Scroll down until you get to "Operating System." From there, you will see the option for fingerprint and build...

Hahaha glad it's not just me... I'm undecided between troll or not.

5.4.0.0 is super old, mine are from 5.3.6.4. Your best bet is to reload the firmware at this point. You'll save yourself a lot of headache.

The newest firmware for devices running FireOS 6 has apparently patched mtk-su, so it may not work, depending on the device.

Settings > Device Options > System Updates

Here are the APK files:

So do you need to open the case to run this exploit on the newest firmware, or can you just brick to install older lk/preloader, and go from there?

FYI: https://forum.xda-developers.com/showpost.php?p=80164459&postcount=162

You need to check the device screen and click allow USB debugging from this computer

Everything went super smooth. Many thanks for this, and all your unlocks. Also, I was able to flash my flashfire system and usedata backups in TWRP with no issues.

Are you guys clean flashing or dirty flashing? I'd imagine if the issue was fixed in the newest build, you'd want to clean flash it.

I tested for about an hour last night, and didn't find much that you haven't already reported. I did sometimes need to exit and reopen Play Store for apps to download, or they'd get stuck. It also did not recognize my SD Card without asking to reformat/wipe it. I guess that's sdcardfs...