Database Info

Frequently asked Questions AT&T LG G3 (D850)

[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]LG G3
AT&T D850[/SIZE]​
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: How do I ask a question, so I'm not called a noob?[/SIZE]While you may see many questions asked in the Development section, PLEASE be aware this is not the place for questions.
Remember to use the search found at the top of the forum. There is also a search within each section. Example click on Q&A HERE. In the upper right you will now see two search's. At the top it says Search All Forums and a little further down you will see Search This Forum. Enter your search criteria in the Search This Forum to get info from this section. The search at the top will look through the entire forum.
Please read as much as you can prior to doing anything with your device.
Make sure your question has not been answered in the OP (Opening Post) of each section of Development
Search Q&A for threads that may have been started for a particular rom​
[SIZE=+1]Q2: How do I update my stock firmware?[/SIZE]1) Turn on WiFi or data
2) Go to Menu > Settings > About Phone.
3) Select firmware update​
[SIZE=+1]Q3: What is a ROM?[/SIZE]A rom is like a custom firmware image that is made by a Developer either entirely from scratch, or based off of the official firmware package. Some ROMs contain simple changes like changing icons and adding extra options to things, other more complicated ROMs can change the entire Android experience. Which one you will want to flash, will be entirely up to you. Read carefully, and make sure you understand what you are getting into before you flash.​
[SIZE=+1]Q4: What is a Kernel?[/SIZE]A kernel is the heart of the device's OS. In simplest terms it’s a connection between your apps and your device’s hardware; i.e. the processor, RAM, etc. A custom kernel can dramatically change the way your device’s hardware performs… for the better and/or the worse]​
[SIZE=+1]Q5: What is a Bootloader?[/SIZE]The bootloader is a program code that is executed before the device OS starts up, and that instructs that device to boot “normally”. The bootloader can come locked or unlocked from the manufacture. A unlocked bootloader will allow you to install custom ROMs & Kernels (as well as some other neat things) on your device.​
[SIZE=+1]Q6: What does Root/Rooting mean?[/SIZE]Put simply, Rooting your device allows you, and/or rooted apps, to access parts of the Linux based Android software that is your OS, and that you would otherwise not be able to access. These tasks can be as simple and beneficial as backing up your system setting, or as complicated as installing custom ROMs, Kernels, etc.​
[SIZE=+1]Q7: What is the purpose of rooting my device?[/SIZE]Please bear in mind, rooting can be dangerous and if done wrong "brick" your phone.
Rooting the phone is a decision made by individuals looking to improve upon the Android OS. There are many benefits, however it is done to customize the phone to it's full potential​
[SIZE=+1]Q8: How do I root my LG G3? [/SIZE]Use one of the following methods, for KitKat or Lollipop.
Android version 4.x.x (KitKat)
[ROOT][IOroot] LG G3 4.4.2 Jailbreak
PurpleDrake-Lite!
[Root] Stump Root for LG Devices
Android version 5.x.x (Lollipop)
One click script
[ROM][STOCK][BUMP'd] LG D850 20F Lollipop 5.0.1 (+ extras)
[SIZE=+1]Q9: How do I remove root and return to factory stock. Why would I uninstall root?[/SIZE]The complete "Unroot" method, can be found here"
Removing root is normally a process used for a couple main reasons:
1) You've done something to the device and now it doesn't seem to be working.
2) You need to return the device or send it in for service.​
[SIZE=+1]Q10: What is ADB (Android Debug Bridge) and what is it for?[/SIZE]Please read [GUIDE] ADB Workshop and Guide for everyone. There is much to learn, please view everything in the threads OP​
[SIZE=+1]Q11: How to I enter Download Mode and Recovery?[/SIZE]1) You must switch off the device to start the process.
2) Press and hold the “Volume Up” and connect the USB cable from phone to PC.
3) Use the original USB cable. Other device USB cables may not be detected by the Computer. It is strongly recomended to use the original cable that came with the device.
4) Wait for the driver installation on PC.
5) You will now see the download mode screen on your phone.
6) Done
You can now do any process, such as, install stock ROM through your computer or laptop.
You can return to the normal mode by pressing and holding power button.
DO NOT UNPLUG THE DEVICE while the update process is running. This can damage your device!​
[SIZE=+1]Q12: What is a "logcat" and how do I create one?[/SIZE]For setting up ADB see What is ADB (above) logcat allows us to log what the OS is doing, and possibly offer information if things are not working. its quite simple to create but may be difficult for most to understand. This is a tool a Developer may ask for in detecting issues your device may be encountering.
To use logcat
Code:
adb shell
logcat
To logcat to a certain file do
Code:
adb shell
logcat -d > /sdcard/whatevertexfileyoulike.txt
For a full explanation follow the link in What is ADB​
[SIZE=+1]Q13: Is there an app that will help me create a logcat directly from my phone?[/SIZE]Yes, Apps for logcat can be found in Google play LINK Any one of these apps will work. It is recomended to use one with a good rating. YouTube also has step by step directions on how to use many logcat apps​
[SIZE=+1]Q14: What does odexed and de-odexed mean and what is the difference between the two?[/SIZE]Please read HERE​
[SIZE=+1]Q15: What is a Nandroid backup?[/SIZE]A Nandroid backup is a complete backup of your entire current operating system. It backs up the NAND flash, (this is the hard drive of your device). A Nandroid backup can mean the difference when you install a custom rom or when you play with the roots of your device, and something goes wrong.​
[SIZE=+1]Q16: How do I make a Nandroid Backup?[/SIZE]In order to make a Nandroid backup, you must have a custom recovery installed.
From your phone, enter recovery mode and look for the ‘backup and restore’ click on backup and wait a few minutes until the process is done. It is best to save your Nandroid backups on the external SD card or on the PC to avoid erasing it by mistake. Performing a back up will NOT back up your external sd card and unless you choose to format your external sdcard, this will remain a safe place for this back up​
[SIZE=+1]Q17: How do I restore a Nandroid Backup?[/SIZE]Enter recovery mode again and look for the ‘backup and restore’. Select restore and everything should go back to normal in a few minutes.
If you choose the ‘Advanced Restore’ option, you can select which component of the backup to restore – like the boot, system, data or cache.
Reboot system. Your system is now restored and is exactly same as the time when the backup was made.​
[SIZE=+1]Q18: What is CWM Recovery (ClockWorkMod Recovery) and TWRP (TeamWin Recovery Project)?[/SIZE]They are recovery program's that allows you to backup / restore a full or partial system backup of your device. They also allow you to install flashable .zip files; which is one of the primary installation methods for custom ROMs. They also provides other features such as cache and delvik wiping, battery reset, and other processes. If you are thinking about flashing custom ROMs or just want a really good backup program, it's strongly advised that you to install one of these.​
[SIZE=+1]Q19: Why does my battery drain so quick?[/SIZE]Please see HERE for possible steps that can help​
[SIZE=+1]Q20: What is "Bloatware" (Bloated Software)?[/SIZE]Bloatware is all of the extra software applications that come pre-installed on your device (in addition to vanilla Android)–it can include any kind of application but some of the most notable examples are carrier apps and/or trial apps that you have to pay for after a certain time to keep using it. At best these apps can simply be taking up space on your phone, or at worst it can be running in the background without your knowledge and drain your battery​
[SIZE=+1]Q21: How do I remove "Bloatware"?[/SIZE]Important: You will require root for the following process
Start by making a backup of all apps in your recovery.
Next read this tutorial, How to remove bloatware on AT&T LG G3​
[SIZE=+1]Q22: How do I block "OTA" (Over The Air updates)?[/SIZE]Please follow these simple steps found here​
[SIZE=+1]Q23: What is the best rom for my phone?[/SIZE]While you can ask this as many times as you wish, the only answer is: the one that works best for you! A rule of thumb is to visit a several rom thread's and view what is happening within these rom's. Eventually viewing a few roms will cause the urge to try one that looks good to you.​
[SIZE=+1]Q24 What is the MD5, and what does it do?[/SIZE]It ensures that file's are downloaded correct and complete, in order to avoid issues when installing/using it.​
[SIZE=+1]Q25 What does the term "Bump" mean?[/SIZE]
thecubed said:
A new and easy way to sign boot images for most modern LG phones so they'll boot on any locked phone.
Bump an image once, and flash it to however many phones you please.
Click to expand...
Click to collapse
For a detailed explanation head over to here
Please feel free to offer additional questions w/ answers, you feel may be helpful to others.
** *** **​
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A special thanks to everyone who contributed to the production of this FAQ

Coming from the nexus 5, these were some questions I had right away:
What does "Bumped" mean?
Can we root lollipop and if so, is it the same process? Do we still have to go back to kk to root?
Does anyone have the random dead spots in the digitizer where your touches aren't registered in certain spots for a while?
Great thread man
Sent from my LG-D850 using Tapatalk

DigitalUnderground said:
Coming from the nexus 5, these were some questions I had right away:
What does "Bumped" mean?
Can we root lollipop and if so, is it the same process? Do we still have to go back to kk to root?
Does anyone have the random dead spots in the digitizer where your touches aren't registered in certain spots for a while?
Great thread man
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
All done, except for "spots". I'm not aware of this issue on sock LG G3. If you have further info regarding this, I will gladly post what you find.

I just have a quick question Tony, after flashing a custom rom I plug the usb into my computer from the phone, and my computer doesn't recognize the phone anymore. I just want to drag and drop some music files, but how can I make the computer read the phone again ?
So far I've checked that Im on MTP
Thank you

koc88518 said:
I just have a quick question Tony, after flashing a custom rom I plug the usb into my computer from the phone, and my computer doesn't recognize the phone anymore. I just want to drag and drop some music files, but how can I make the computer read the phone again ?
So far I've checked that Im on MTP
Thank you
Click to expand...
Click to collapse
You should find this tutorial helpful~ [How to fix] Windows 8/8.1 is not detecting my LG G3 device

Unified development section
are we going to get a unified development section? there are just as many and most likely more roms that run on the d850 that are posted elsewhere because they run on multiple versions of the g3. i think it would be a great adition this forum and bring a bunch of new roms in.

is there a d850 stock rom that has hotspot enabaled

What is the procedure for roofing my lg g3 please
---------- Post added at 03:44 AM ---------- Previous post was at 03:40 AM ----------
I am a noob

hi
how can install twrp un order to install custom ROM on LG g3 d855 kitkat 10n rooted with this method https://forum.xda-developers.com/lg...t-lg-firmwares-kitkat-lollipop-t3056951/page5

[MASTER THREAD] Fire HD 8 (2017) (7th Generation)

Hi,
This is a list (incomplete) of all the ROMs, mods, hacks, guides, etc. available for the Fire HD 8 (2017).
This was a root progress discussion thread, and I think there's too much valuable information here to just let it get buried. So, following @Rortiz2's suggestion this thread was transformed to a master thread with the aim of providing a complete guide for anyone wanting to mod their tablet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device Codename: douglas
Specifications:
SoC: Mediatek MT8163
CPU: Cortex-A53 (Quad Core 4x1.3Ghz)
GPU: Mali 720
RAM: 1.5GB
Android: 5.1 (FireOS 5.x.x.x)
Storage: 16/32GB
Includes a MicroSD slot
Battery: 3210mAh
Display: 8"
Front Camera: 2MP
Rear Camera: 2MP
The italicized text below are my comments/clarifications.
The root method was patched in 5.6.4.0 (some versions of 5.6.4.0 still work so you could try) It is advisable to disable OTA updates or unlock the bootloader immediately. It is still possible to unlock by a different method, check the bootloader unlocking thread.
Bootloader Unlock and TWRP:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 8 2017 (douglas)
This is an excellent and complete guide which has everything you need for this. Requires Linux, so you'll have to either install it as dual-boot or use a live system if you are not using it already. You don't need to downgrade if you are on 5.6.4.0.
Rooting:
You can flash Magisk using TWRP after bootloader unlock. Using Magisk is recommended because SuperSU is no longer supported, and Magisk has modules, Magisk Hide, and the root prompt is working (In SuperSU it's not working so you have to always grant root permissions which is a major security loophole)
Rapid Temporary Root for HD 8 & HD 10
This is the first software root method discovered for this tablet and is a really easy and quick method of getting a root shell, and the link has a complete guide on it. Refer here for installing SuperSU for permanent root, and here for an automated script for Windows.
[ROOT] Hardmod Root Your Amazon Fire HD 8 (7th Gen)
This is first root method ever discovered for this tablet and is a hardware root. This link has a complete step-by-step guide, assuming you have some soldering experience.
ROMs:
[ROM][unlocked]Lineage-12.1 for Amazon Fire HD8 2017 (douglas)
The first (and currently only) ROM for this device and it works great!
Miscellaneous:
Amazon Fire Toolbox, I have never tried this but it looks awesome!
Without root:
Removing accounts and viewing Usage Access settings which are hidden.
Debloating guide without root
With root:
A debloating guide made for HD 10, but works fine on the HD 8.
You can install apps as system apps just as on any other device, and you can use the app Link2SD for converting user apps to system apps. Refer to this StackExchange post for a guide on how to install apps as system.
Flashing GApps works well with TWRP, but the 16GB version doesn't have enough space in the system for even the pico version. Probably using pm uninstall on some system apps would work.
General Tips:
To return to stock or recover from a soft brick:
(Don't use this if you have already unlocked your bootloader: if you want just stock FireOS flash it through TWRP, and if complete stock follow the guide in the unlock thread)
(This assumes that you have ADB installed, I would not advise you on how here, there are numerous guides waiting for a Google search. This will erase your data.)
Download your current FireOS or a later firmware version. You can find the latest over at Amazon's website.
Boot to the recovery mode of your tablet, and use the volume and power buttons to select "Apply Update via ADB".
Now connect the tablet to a PC with a USB cabke, open a command prompt or shell on the directory where you downloaded the firmware BIN, enter the command adb sideload X.bin (replace X with the name of the BIN) and wait until finished (DON'T disconnect your device from the PC)
Now select "Wipe Data/Factory Reset" and "Yes" to wipe data (you can skip doing this if you want your data, but note that the tablet may bootloop or complain about corrupted data)
Select "Reboot system now"
The firmware BINs are just renamed ZIP files: you can rename it from .bin to .zip and treat it as such.
Amazon employs an anti-rollback mechanism which could permanently brick your device if you flash an older version through adb sideload. If you really want an older FireOS, you can rename .bin to .zip and flash them through TWRP after unlocking.
The stock launcher AppID is com.amazon.firelauncher, the stock keyboard is com.amazon.redstone, and the OTA update apps are com.amazon.device.software.ota and com.amazon.kindle.otter.oobe.forced.ota.
Again, this list is incomplete, so please suggest any additions in the comments! (don't hesitate to suggest your own work-the target of this thread to be a comprehensive and complete guide on everything about this tablet)
Good luck modding this tablet!

Thread before changing to a master thread (for historical purposes )
NOW WE HAVE AN UNLOCKING METHOD WITH TWRP! THE CONTENT BELOW IS OUTDATED.
Hi,
Now, I'm sick of Amazon's bloat slowing my tablet, and the frustration of not being able to use root apps. Fire HD 10 got rooted, but HD 8 and HD 7 are still in dark. HD 7 users can at least downgrade their devices and hope for a root exploit, but HD 8 users can't. If anyone else wanting to root this tablet and make it super fast, get rid of Fire Launcher, use Xposed, remove bloat, etc., let's collaborate with this!
LATEST RELEASE - Fire OS 5.3.6.4/Fire OS 5.6.3.4
SECURITY PATCH - ???
KERNEL VERSION - 3.18.19
List of possible software root methods:
1.) eMMC overwriting
Thanks to the hardware root method, we have a full eMMC dump so using the loophole in the flash unlock process which causes overwriting partitions next to it, we could overwrite on all the way, flashing original things, to the system partition and then flash a modified system partition.
Additions to the list are welcome!
List of possible exploits
Additions to list are welcome!
1.)CVE-2017-8890
Status: Confirmed possible.
Description: As I think, this is the most exploitable currently. Running the PoC results in 'somewhat unnatural' Use-After-Free s but the PoC fails to orient them to escalate privileges.
Cons: This exploit is based on obsolete IPv4 sockets, unlike it's cousin CVE-2017-9077, which is based on IPv6, but rather the same exploitation as this. That 'may' make this harder to exploit, but of course there's no evidence.
I, really only added this to cons because you should have a con.
2.)CVE-2017-15868
Status: Unsure
Description: NP Hardass said that this vulnerability is present on the source,I haven't explored it yet.
Cons: ¯\_(ツ)_/¯
If you tried these exploits, please notify me in below and I'll update the status. UPDATE: No point on keeping on trying these kernel exploits as no one (please correct me) who knows to write exploits in C comes here anymore. If someone wants to try though I will start maintaining this list again. Come on, let's collaborate on this!!! :laugh:
Thanks!
Download the eMMC dump from here: https://www.androidfilehost.com/?w=files&flid=282721
PS: You can download original kernel sources from Amazon, just search for it.
Original Thread:
Hi,
Now, I'm sick of Amazon's bloat slowing my tablet, and the frustration of not being able to use root apps. Fire HD 10 got rooted, but HD 8 and HD 7 are still in dark. HD 7 users can at least downgrade their devices and hope for a root exploit, but HD 8 users can't. If anyone else wanting to root this tablet and make it super fast, get rid of Fire Launcher, use Xposed, remove bloat, etc., let's collaborate with this!
LATEST RELEASE - Fire OS 5.6.0.1
SECURITY PATCH - 2017/08/01
KERNEL VERSION - 3.18.19*
*a quite old release it is.
List of possible exploits
Additions to list are welcome!
1.)CVE-2017-12762
Status: Unsure
Description: A super likely-to-work great exploit. If you want you can go look at the kernel source (link included below the thread) 3.18.19 for proof, it starts in line 2640. Looks like a stack buffer overflow.
Cons: ASLR may be an absolute game killer in this case. And some skill is required to exploit, very less-known around the internet. And Amazon may have removed the ISDN support up from the roots of kernel, because it's VERY deprecated.
2.)CVE-2017-16939
Status: Unsure
Description: A nice attack vector. A PoC is available in SecuriTeam blogs, which triggers use-after-free. I tried contacting them for some help, but they almost instantly replied that they don't provide support for their reported vulnerabilities. Sad.
Cons: ¯\_(ツ)_/¯
3.)CVE-2017-15868
Status: Unsure
4.)CVE-2017-10661
Status: Unsure
5.)CVE-2017-7541
Status: Unsure
6.)CVE-2017-6074
Status: Unsure
If you tried these exploits, please notify me in below and I'll update the status. Come on, let's collaborate on this!!! :laugh:
Thanks!

I added the link to the vulnerable code, in case anyone was wondering.

I'm glad to see this thread. Since recently rediscovering the potential of an old Fire 6 and rooting it, removing the bloat and Googlizing it, I wanted to get something a little bigger. I just got my 7th gen HD 8 in the mail yesterday and was devastated to see it was 5.4.0.1. I've blocked OTA, deleted the update it had downloaded, installed Google Play et al., and used NoRoot Data Firewall to block all Amazon apps. Unfortunately, I do not have the expertise to contribute much toward an effort to root this device but would like to help in any way. I appreciate seeing others are out there working on it.

if i knew how to develop the exploits i would honestly try these

Thank you so much for making this thread but I hope I never have to come back here and help, but if i get some extra time in the future I do plan on running all my binaries + servers on the tablet as well. Not to mention just looking at that version number made me want to vomit.

[/COLOR]What steps should I take to increase performance on the hd 8 while we wait for root?

rawfullz said:
[/COLOR]What steps should I take to increase performance on the hd 8 while we wait for root?
Click to expand...
Click to collapse
Hello rawfullz!
Try Greenify. You can use a workaround to grant it Usage Access.
1) Download Activity Launcher and Greenify from Play Store.
2) Launch Activity Launcher.
3) Notice the "Recent" text in the task-bar, press it, and select "All" from the drop-down list.
4) Scroll all the way below until you find "Settings", and press it.
5) Again, scroll below until you find "Apps with usage access", and press it.
6) The hidden "Apps with usage access" menu will pop up.
7) Grant Greenify usage access there. (You can turn off usage access for all Amazon apps if you want, to increase performance but it's recommended to leave out "Storage Management" intact, just in case.)
8) Launch Greenify, and continue with the setup.
9) :laugh::laugh::laugh::laugh:
If you ever want to grant any other app Usage Access, do this procedure, but, remember that "Activity Launcher" is kind of dangerous, if you just launch random activities. I learned that the hard way.

REMOVED

Thank you for making this thread, im looking forward to this become real.

What I dont get is you can download the firmware.bin as well as the source code from amazon, Whats the problem devs should be able to root ?

derwoodbones said:
What I dont get is you can download the firmware.bin as well as the source code from amazon, Whats the problem devs should be able to root ?
Click to expand...
Click to collapse
Hello!
Yes, we definitely can get the firmware. But there are some troubles,
1. Amazon devices are not very well known among the community.
2. Devs don't want to spend their time on our devices, even if we root this thing, no custom ROMs because of the locked bootloader.
3. Amazon didn't leave any loopholes on their OS, they are too clever.
And, I don't think that Amazon will open source their firmware until they checked throughly for any exploits.
We'll have to find exploits the rough way. :crying:

Hey, what about the Janus vulnerability? If some dev is reading this, please help us, because it doesn't require the device.

Supersonic27543 said:
Hello!
Yes, we definitely can get the firmware. But there are some troubles,
1. Amazon devices are not very well known among the community.
2. Devs don't want to spend their time on our devices, even if we root this thing, no custom ROMs because of the locked bootloader.
3. Amazon didn't leave any loopholes on their OS, they are too clever.
And, I don't think that Amazon will open source their firmware until they checked throughly for any exploits.
We'll have to find exploits the rough way. :crying:
Click to expand...
Click to collapse
You don't need an unlocked bootloader to flash a ROM.

Take a look at the BT stack with BlueBorne.
Sent from my iPhone using Tapatalk

Supersonic27543 said:
Now, I'm sick of Amazon's bloat slowing my tablet
Click to expand...
Click to collapse
You forgot to add: "and I wanna to fill my tablet by the Google's bloatware (2 times slower than Amazon's), and also add some rootkits and spyware masked as "super-duper tools for young hackars"

Great to see this thread. Hope some devs collaborate and find a way. Can't wait.
Meanwhile, do you guys have any cool mod to try in the tab.
I have installed playstore and adfree iytb YouTube and bunch of usual apps.

Hello!
DragonFire1024 said:
You don't need an unlocked bootloader to flash a ROM.
Click to expand...
Click to collapse
Yes, you don't need an unlocked bootloader to flash a ROM, theoretically, if the ROM is signed by Amazon. But considering custom ROMs, Lineage, Resurrection Remix, Stock Android, is it possible to compile and flash them without an unlocked bootloader? I thought that you need a custom recovery = unlocked bootloader. Thanks!
sensboston said:
You forgot to add: "and I wanna to fill my tablet by the Google's bloatware (2 times slower than Amazon's), and also add some rootkits and spyware masked as "super-duper tools for young hackars"
Click to expand...
Click to collapse
Hah. :laugh::laugh::laugh:
Robius said:
Take a look at the BT stack with BlueBorne.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Great idea, gotta try this! Thanks!
EDIT: Not very confident though. Anyway, likely to work because the security patch of HD 8 is in August.
http://www.androidpolice.com/2017/0...atch-fixes-blueborne-bluetooth-vulnerability/

Someone got a bluetooth adapter handy?

Supersonic27543 said:
Hello!
Yes, you don't need an unlocked bootloader to flash a ROM, theoretically, if the ROM is signed by Amazon. But considering custom ROMs, Lineage, Resurrection Remix, Stock Android, is it possible to compile and flash them without an unlocked bootloader? I thought that you need a custom recovery = unlocked bootloader. Thanks!
Hah. :laugh::laugh::laugh:
Great idea, gotta try this! Thanks!
EDIT: Not very confident though. Anyway, likely to work because the security patch of HD 8 is in August.
http://www.androidpolice.com/2017/0...atch-fixes-blueborne-bluetooth-vulnerability/
Click to expand...
Click to collapse
Ask @ggow how he does it. But you don't need a unlocked bootloader. With root, FlashFire helps to get by the bootloader.

[GUIDE/ODIN/FW/BL] SM-P610 USA/XAR WIFI ONLY: Stock Firmwares + Modded BL WarningText

THIS IS YOUR FIRST WARNING (WILL BE REITERATED PLENTY OF TIMES!) IN BIG RED BOLD LETTERS - THESE FILES ARE FROM/FOR THE USA ("XAR") REGION, SM-P610 WIFI MODEL ONLY!
(with the exception of the Odin utility, as well as possibly the modified boot splash screen, which may work on other variants, though untested and done solely at your own risk - read all the notes!!)​
I already went through the work, so I figured I would share these files for those who also own the same exact tablet. Again, it's for the USA/XAR region Samsung Galaxy Tab S6 Lite WiFi Model ONLY - "SM-P610" / "gta4xlwifi". LTE model is a different variant; do NOT flash the stock firmware files to that device! Also, sorry, I will not support or answer questions for other variants (other than what I will mention in this OP). Downloading firmwares for other variants will be a huge PITA, and I don't have / pay for any "premium" accounts which would allow me to quickly download the huge firmware files. I'm only sharing these I'm posting because I already took the time to acquire and archive them for personal usage, and might as well share them for those who own the same device / variant.
Use these files at your own risk, and only flash if you know what you're doing!! I'm not responsible for any problems user may incur from usage of these files, the usual warnings apply, etc. This device is just a backup / playaround device for me, and so it doesn't get daily usage out of me, nor will I likely be very active on this subforum (sorry! just being honest). Also, I immediately installed LOS on my device anyway, so I don't run stock ROM myself and therefore won't be sharing pre-patched Magisk boot images either. Sorry to those who are used to that from me =)
So anyway... what's in this post?
Odin3 v3.14.4 (version I've been using on this device, and working perfectly fine as of this initial posting)
Stock firmware zips for USA/"XAR" Region SM-P610, WiFi Only
Modified BL file (Odin-flashable), to remove the warning boot text
Odin3 v3.14.4:
I posted this in another thread, but figured I would also link to it here so it's easy to find in one place. This worked perfectly fine for me to root / install TWRP / flash BL files, etc.
Download Link: https://www.androidfilehost.com/?fid=10763459528675582443
Stock Firmware Files:
USA/XAR WIFI ONLY! October 2020 Update - Firmware Version P610XXU2BTJ5
Download Link: https://www.androidfilehost.com/?fid=10763459528675592742
USA/XAR WIFI ONLY! September 2020 Update - Firmware Version P610XXU2BTI3
Download Link: https://www.androidfilehost.com/?fid=10763459528675592159
Firmware files for other variants, see this post. Follow the links, use the resources, consider the context for other variants: https://forum.xda-developers.com/showpost.php?p=83083249&postcount=2
Modified [BL-slot] Odin-Flashable File To Remove Warning Splash Screen Text:
My Thoughts On This...After unlocking the bootloader and flashing non-stock images, we all know we end up with that annoying, ugly splash screen screaming that the device is modified. Most of us modifying our devices understand the security implications involved, and ironically choose to modify our devices to increase security in other ways. Yet, these warning splash screens, in the unfortunate event of possible theft, may very well end up being the reason a more tech-savvy thief is able to break into the device, or find someone who can. So, thanks to users' posts Awesomeslayerg's hint and blascogm's guide, I quickly came up with an Odin-flashable file to change the splash screen, as seen below:
(if the pic doesn't show, probably the imgur link I used is dead, but I also attached it to this post)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know some people may be thinking "why not just remove the PRESS POWER KEY TO CONTINUE line completely and have it stay at the normal boot screen seamlessly the whole time", and the reason I decided not to do this is because it generally wouldn't make the average person suspect the device is modified, and it's still good for us to know that it's at the boot stage where we can hit the power key to skip the ~10 second timeout. It's exactly the same image, so it's still very seamless and stock-like. I even took the time to center the power key text exactly, by the pixel, from left to right and from top bottom relative to the knox and android logos.. ; )
And if it really bothers you that much, follow the guide I linked above and do it yourself. =)
I should also mention that, for our devices, the .bin.lz4 file that needs to be decrypted is actually "up_param.bin.lz4" and not "param.bin.lz4" as suggested in the guide, as it's for a different device. You will need the lz4 utility (check Awesomeslayerg's thread, or google lz4 github) to decrypt the lz4 file to a regular bin file, and then you can extract and/or replace the .jpg files using an archiver program (I recommend 7-zip for this).
The hash checksums for every single file/jpg in each up_param.bin were identical between the September and October firmwares. Therefore, at least as of this posting, the same modified Odin-flashable file will work on either firmware version, and likely future versions until they make any significant changes. I did test this myself too btw. Also, if you look at the structure and contents of the up_param.bin file for yourself, you'll see that they are simply .jpg files containing the screens, backgrounds, and text you're all familiar with when going into bootloader / download mode. Assuming they follow the same file naming structure, I suspect you can probably flash this to other variants, although it will change the text language to English (assuming they localize the bootloader / download mode text per every region; I have no idea about this as I only own US variants). To see what I'm talking about, here's a quick screenshot (better resolution pic, and just in case imgur link dies, also attached to this post):
Now that I (hopefully) tricked you into reading this entire section so that you now have some basic understanding of how it works before proceeding to flashing the warning text removal mod, here are the instructions / link for install:
- Download the .tar file provided below.
- Boot device into Download mode.
- Place .tar file into bootloader [BL] slot in Odin and flash.
Download Link: https://www.androidfilehost.com/?fid=10763459528675592179
To revert back to stock splash screen with warning text, for whatever reason:
Pull the stock up_param.bin.lz4 from the stock firmware file (from the BL****.md5 file within the firmware zip).
- Convert it to up_param.bin uzing lz4 utility.
- Add up_param.bin to an archive as .tar file, uncompressed (recommend using 7-zip).
- Flash the .tar file, which should contain only the stock decrypted up_param.bin file, in Download mode using Odin in the BL slot.
I uploaded my custom jpg's, as well as the stock untouched jpg's, for those that are curious or want to edit them further. Feel free to snag them here: https://www.androidfilehost.com/?w=files&flid=320350
* As we can see, we're only modifying the .jpg files provided by up_param.bin, so it's a relatively harmless process (unlike modifying aboot files in the old days of HTC devices, which if done improperly could literally result in an unrecoverable brick). But even so, please only flash if you know what you're doing and can recover from any potential mistakes or errors.

Not sure if there were any changes since the September / October 2020 firmwares, but here's a new one directly modified from the March 2021 (Android 11) firmware base:
NEWEST DOWNLOAD, BASED ON 2021-03 FIRMWARE:
https://www.androidfilehost.com/?fid=14943124697586346609

And another

Hi,
Thanks for these resources. I'm actually not at these steps yet. I'm having trouble gaining access to the OEM Bootloader Unlock option in developer options. Here are things I've tried already based on what I researched before my attempt.
Android 10 is the current OS installed after unboxing.
1. Disable Automatic Date and time
2. Select a date more than 7 days prior to current date of attempt.
3. Under Settings > About Phone > Software Information. Select/Tap Build Number 7-8 times to unlock Developer Option.
4. Disable Auto Update System (Apply Updates When Device Restarts) - *This was somehow already disabled the first time I entered Developer options*
5. Under Software Updates > Disable Automatic Updates -*This was also already disabled on unboxing and it says Automatically download updates over Wifi. It does not say Automatic Updates*
6. Reboot device and return to Developer Options after booting to OS.
7. The OEM Bootloader Unlock option should appear greyed out at this point. Toggle it to unlock bootloader with consideration that it will wipe the device data.
These are the steps I've found and tried with no success in gaining access to the Bootloader unlock option. I am also certain that my device is the international model SM-P610 with Exynos chipset and Mali-G72 GPU. Something else to note, I did uncheck many default options tied to improving privacy on the device before attempting the steps to gain access to the bootloader unlock option. I do not know if that would make a difference. If you recognize anything wrong with the steps I've tried already, please let me know where I'm going wrong or where I can find the correct way to unlock the bootloader. I've been posting in other threads, but nobody seems to be replying to me. Any help will be appreciated.

Hi
I've flashed your modded file on my PHN (Netherlands), no problems at all working ootb!

Hi. I used blascogm's guide for my P615 with latest firmware for SEC UI 3.1and all are OK! Thanks for all.
Add. I add link . Flash via Odin(BL).
https://androidfilehost.com/?fid=14943124697586347282

i5lee8bit said:
Not sure if there were any changes since the September / October 2020 firmwares, but here's a new one directly modified from the March 2021 (Android 11) firmware base:
NEWEST DOWNLOAD, BASED ON 2021-03 FIRMWARE:
https://www.androidfilehost.com/?fid=14943124697586346609
Click to expand...
Click to collapse
I flashed ths when I'm running lineageos 18.1 annd this is the only mod that worked for me

Thanks for posting your images and linking to the guide, worked perfectly and the images just fit to the pixel <3

Confirmed working as of March 2022. Device is running base P610XXU2DUL9. Thanks for the hard work.

can you make one for SM-P613 model plz?

General [Kernel] StarKissed B2Q [Raccoon City]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This kernel is (currently still very) experimental. Use at your own risk.​
This kernel assumes a few things about you, the user:
1. You have a Samsung Galaxy Z Flip 3
2. You have read all warnings and instructions
3. You are rooted (implying an unlocked bootloader)
4. You have an installation method
5. You have a backup boot image
Releases will be labeled with the commit hash of their source. An unlocked device is recommended for this kernel, but not necessarily required. I am not responsible for any issues or damage caused by installing this kernel, so have a backup ready.
Downloads for : Samsung Galaxy Z Flip3 5G | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
All kernels are released with the possibility of not booting. This should be considered a WIP release. They are provided for review and testing of the included components.
Thank you to everyone that has contributed to kernel development.
Specific credit is provided by maintaining accurate commit history.
Also, big thanks to @beanbean50 for testing the untested releases.
GitHub - StarKissed/starkissed-kernel-b2q
Contribute to StarKissed/starkissed-kernel-b2q development by creating an account on GitHub.
github.com
GitHub - StarKissed/AnyKernel3 at SM-F711B
AnyKernel, Evolved. Contribute to StarKissed/AnyKernel3 development by creating an account on GitHub.
github.com

Current Kernel Improvements
Boeffla Wakelock Blocker v1.1.0
Wireguard v1.0.20210606
Patched SafetyNet commandline
Magisk process detection patch
Disable watermark boosting
Multicolor LED / PlayStation / Nintendo HID
Tuxera ExFAT / NTFS modules
Umbrella Core / Raccoon City [WIP]
Optimization from Kirisakura / StarKissed
raccoon_city (originally written for the Shield Tablet) is a new take on "interactive" by using a combination of low latency timers and the kernel scheduler to scale more aggressively (or less, if configured that way) based on workload, in addition to capping the max inactive frequency. The purpose is to provide a balance between good battery life and performance without handicapping the device.
umbrella_core (originally written for the Note 4 and ported to hundreds of other devices) takes raccoon_city a step further with automation. In addition to the full array of user settings, this governor features a smart mode that will adjust the base values within a set range to further optimize battery and performance.
The difference between these governors and the batterysaver implementation (also available) is the lack of arbitrary caps on max values during normal use. By controlling the workload, this allows better control over when the next frequency is reached, instead of whether it is available at all.
The default configuration idles at a max of about 800 mHz, but can be configured for each cluster, much like most settings.
The original source is provided through the public Samsung source under SM-F711B
Samsung Open Source
opensource.samsung.com
Building / Compiling Custom Kernels
starkissed-kernel-b2q/build at main · StarKissed/starkissed-kernel-b2q
Contribute to StarKissed/starkissed-kernel-b2q development by creating an account on GitHub.
github.com

I haven't finished setting up my phone to back it up, wipe it, and start over with an unlocked bootloader yet. If anyone is feeling really brave and wants to test the builds, though, you are welcome to contact me. Remember that I have absolutely no idea if they will even boot, though.

Temporarily delayed. See below.

I really want to try this but for the life of me I can't get any fastboot commands to work (waiting for any device) flashed every known usb/fastboot driver out there, changed ports/cables etc but no luck, ADB works fine. Is there a way to make it flashable through Magisk or Odin?

beanbean50 said:
I really want to try this but for the life of me I can't get any fastboot commands to work (waiting for any device) flashed every known usb/fastboot driver out there, changed ports/cables etc but no luck, ADB works fine. Is there a way to make it flashable through Magisk or Odin?
Click to expand...
Click to collapse
I've been looking for how to convert it. I missed a couple changes, so I'm trying to wrap those up first.

I have a feeling it will be much like the last few devices where you need to use FKM, EX, etc until such time as custom recoveries exist. I don't see any instances where anyone has converted a modern kernel to Odin (tar) format, which means I doubt there was much success.

@twistedumbrella Probably silly question. I've always wondered if video-out is a hardware or software limitation on this device, since it lack DeX and I can't get any other video signal via USB-c.
Q: In your Kernel, does it allow any video signal from "force desktop mode" or similar via the USB-c or do you think this is total no-go due to hardware limitation?
EDIT: oh wait sorry, I think you actually answered my question in a another thread, although I did not really understood if it was confirmed to be a hardware limitation or not.

Tracking down a couple modules that still need to be made inline. I thought I had converted all of them. Once that's done, we should be good to start releasing builds.
jacobsson said:
@twistedumbrella Probably silly question. I've always wondered if video-out is a hardware or software limitation on this device, since it lack DeX and I can't get any other video signal via USB-c.
Q: In your Kernel, does it allow any video signal from "force desktop mode" or similar via the USB-c or do you think this is total no-go due to hardware limitation?
EDIT: oh wait sorry, I think you actually answered my question in a another thread, although I did not really understood if it was confirmed to be a hardware limitation or not.
Click to expand...
Click to collapse
There is a lengthy discussion on reddit where they found the same results and came to the same conclusions. If no signal is possible, wired video out appears to be missing altogether.
Interesting enough there ARE disabled drivers for it. The only thing I don't know is if they would work. I guess the only real way to find out would be to enable them and find some lucky victi... I mean tester to see if they enable it.

This is going to be interesting...
I have a US unlocked model and rumors are surfacing that this means I cannot unlock the bootloader. It has been stated that this has been the case for many years. This contradicts my experience with the Note 20 Ultra, which was also a US unlocked model with OEM unlock available.
That said, until I can confirm that the bootloader can be unlocked, I am unable to test builds on my own device. I am, however, able to test very similar builds with the same changes on a device with similar hardware.
Assuming Samsung lives up to their history of releasing kernel source that builds out of the box, this should allow building working kernels with only those changes that have been tested on the other device. Please note that the base source is for the European device.
I highly recommend having all data backed up and am Odin restore ready until such time as the kernel has a few confirmations.

Here goes nothing...
starkissed-b2q-b5cf738.zip | by twistedumbrella for Galaxy Z Flip3 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

Thanks for this, it looks very good but how do we flash it (whilst waiting for twrp) I've tried FKM, EX, Flashify, Magisk and Odin but all of them failed

beanbean50 said:
Thanks for this, it looks very good but how do we flash it (whilst waiting for twrp) I've tried FKM, EX, Flashify, Magisk and Odin but all of them failed
Click to expand...
Click to collapse
I guess this isn't a slot device like most of the newer ones. It would make sense not being one, but I didn't want to break anything being wrong. Assuming it had the slots when it didn't only fails. Assuming it didn't have the slots if it did could have caused a bad write. It was better to try with before trying without, since there is no fastboot to flat out check the device directly.
Here is a version without slots. Fingers crossed.
starkissed-b2q-17c6dd2a1e87.zip | by twistedumbrella for Galaxy Z Flip3 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

No luck here, FKM said something about 'Magisk detected no need to ...' but I missed the rest of the log as it rebooted within 2 seconds of flashing. However, it got stuck on the Samsung logo upon rebooting, thankfully and eventually I got into download mode and re-flashed the stock rom and all's well again.

beanbean50 said:
No luck here, FKM said something about 'Magisk detected no need to ...' but I missed the rest of the log as it rebooted within 2 seconds of flashing. However, it got stuck on the Samsung logo upon rebooting, thankfully and eventually I got into download mode and re-flashed the stock rom and all's well again.
Click to expand...
Click to collapse
It should have been telling you magisk was detected, so there was no need to install again. I'll have to look back over everything. The hardest part is not being able to test it locally.

Here's the install log if it's any help ...

beanbean50 said:
Here's the install log if it's any help ...
Click to expand...
Click to collapse
Thanks. I think the issue is a few drivers that didn't inline. They hid them all over and Samsung added fuel to the fire by making individual configuration files for each platform (despite being identical).

ok the kernel is being in testing (or experimental), but who has tested it, noticed improvements in battery life? Thank you

iaio72 said:
ok the kernel is being in testing (or experimental), but who has tested it, noticed improvements in battery life? Thank you
Click to expand...
Click to collapse
we still can't flash it (see the post above your one) but the good news is that we should soon have twrp and a custom rom

Even if the kernel didn't fully boot, the good news is that it froze on the Samsung logo and didn't simply reboot. What that means is that, most likely, it really is as simple as tracking down why these drivers are building as modules and making them inline. I imagine, even with things how they are, that the kernel might boot given enough time. Nobody wants to wait that long, though.

[AQT80] Sprint Slate 8 (Quanta ANS_NKS AQT80) Development Thread (Root, Recovery, etc...)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sprint Slate 8 (ANS_NKS AQT80) 8 Inch Tablet
Files: Google Drive
<Includes dumps of stock boot, recovery, splash. Attempted TWRP 3.6.0 build>
​I recently had one of these ancient tablets come into my possession, and like any good nerd, I set out to hack it as much as possible. Admittedly, I knew that this would be an uphill battle, given the relative unpopularity of this particular slate, limited resources, and nonexistent documentation. However, I have made some progress, which I'll share here for the benefit of the community. Some of the information here was collected from other threads that I found scattered about via Google. <This thread also serves as a subtle "call-to-arms" for anyone who happens to have access to this device and has the ability to assist in testing recoveries and ROMs for this device in the future. I have access to one, currently, and know where I can locate another. My Android development skills are moderate, but limited, as I have next to no experience with custom ROM creation, or low-level Android systems. Mentor-ship would also be appreciated.>
Rooting
Rooting this device can be accomplished with Kingo Root (I downloaded the APK from the offical website, be sure to enable Unknown Sources for APK installation). Once rooted, you can remove Kingo Root and update SuperSU to 2.49. This should give you root access to install EX File Explorer/Root Uninstaller to debloat Gapps/Facebook/Sprint carrier apps, which speeds up the device nicely.
Recovery
I've been attempting to make a working TWRP for this device using this guide and while I have an image that flashes and boots, it has notable issues with touch input that make it unusable for anything important. I've included a link to Google Drive where I've backed-up the most recent bootable image. Once you have root, you can install the Official TWRP app to flash IMG files to recovery. Always be sure to back-up stock recovery before flashing anything. My stock recovery dump has worked for me, but might not work for you. </Disclaimer>
Custom ROMs
<None currently exist. Future plans include a Marshmallow or Nougat-based build that has better app support than Lollipop. Interestingly, the stock app payload includes both Trebuchet Launcher and CyanogenMod File Browser. Perhaps this tablet shipped with an OEM variant of CM12? More investigation is needed.>
Other Info
Other users have reported that running this device as WiFi-only (no SIM card inserted) leaves a constantly-visible NO SIM notification. I was able to remove this by uninstalling the Sprint-provided apps and phone dialer. Also, enabling Airplane Mode and then re-enabling WiFi and Bluetooth will improve performance and battery life noticably.
I've been unable to replace the boot splash, as this device apparently uses a splash partition and I'm not sure what format the image that I dumped might have and how I could replace it. This dump is also included in the Drive link.
Notably, I have had some issue with getting fastboot commands to work properly on this device. Some commands work while others fail at the remote end. I've tried to track down the issue, trying different versions of platform-tools as well as ADB driver packages. In the event that I accidentally break recovery or system, having fastboot working as a failsafe is a key priority.
I've also managed to locate the website for Quanta which lists a slightly-updated variant of this specific device. I have attempted to reach out to them via their contact email to see if they might provide a copy of the stock firmware at release. This might help with porting a newer version of AOSP.
Future Posts will include more details about installed apps and other information, as uncovered.

CAN someone Please Give Me A Good Link or description on how to Get past the FBR on My Slate AQT80 I got it from a homeless guy Audcart Figuei out

I have one of these with Android 5.1.1. It will not update anything using Wi-Fi.
It won't show up in Windows Explorer when USB is set to MTP.
It's currently sitting stuck on the powered by Android screen after I turned it on while holding volume down. Should have used volume up. Will try that after it runs down overnight and I recharge it.
Got it free with a slightly swelled battery. Spent $25 on a new battery so $^&"it I want the damn thing to work. The display is quite nice so it should be good for ebooks at least.

redrew89 said:
View attachment 5499981
Sprint Slate 8 (ANS_NKS AQT80) 8 Inch Tablet
Files: Google Drive
<Includes dumps of stock boot, recovery, splash. Attempted TWRP 3.6.0 build>
​I recently had one of these ancient tablets come into my possession, and like any good nerd, I set out to hack it as much as possible. Admittedly, I knew that this would be an uphill battle, given the relative unpopularity of this particular slate, limited resources, and nonexistent documentation. However, I have made some progress, which I'll share here for the benefit of the community. Some of the information here was collected from other threads that I found scattered about via Google. <This thread also serves as a subtle "call-to-arms" for anyone who happens to have access to this device and has the ability to assist in testing recoveries and ROMs for this device in the future. I have access to one, currently, and know where I can locate another. My Android development skills are moderate, but limited, as I have next to no experience with custom ROM creation, or low-level Android systems. Mentor-ship would also be appreciated.>
Rooting
Rooting this device can be accomplished with Kingo Root (I downloaded the APK from the offical website, be sure to enable Unknown Sources for APK installation). Once rooted, you can remove Kingo Root and update SuperSU to 2.49. This should give you root access to install EX File Explorer/Root Uninstaller to debloat Gapps/Facebook/Sprint carrier apps, which speeds up the device nicely.
Recovery
I've been attempting to make a working TWRP for this device using this guide and while I have an image that flashes and boots, it has notable issues with touch input that make it unusable for anything important. I've included a link to Google Drive where I've backed-up the most recent bootable image. Once you have root, you can install the Official TWRP app to flash IMG files to recovery. Always be sure to back-up stock recovery before flashing anything. My stock recovery dump has worked for me, but might not work for you. </Disclaimer>
Custom ROMs
<None currently exist. Future plans include a Marshmallow or Nougat-based build that has better app support than Lollipop. Interestingly, the stock app payload includes both Trebuchet Launcher and CyanogenMod File Browser. Perhaps this tablet shipped with an OEM variant of CM12? More investigation is needed.>
Other Info
Other users have reported that running this device as WiFi-only (no SIM card inserted) leaves a constantly-visible NO SIM notification. I was able to remove this by uninstalling the Sprint-provided apps and phone dialer. Also, enabling Airplane Mode and then re-enabling WiFi and Bluetooth will improve performance and battery life noticably.
I've been unable to replace the boot splash, as this device apparently uses a splash partition and I'm not sure what format the image that I dumped might have and how I could replace it. This dump is also included in the Drive link.
Notably, I have had some issue with getting fastboot commands to work properly on this device. Some commands work while others fail at the remote end. I've tried to track down the issue, trying different versions of platform-tools as well as ADB driver packages. In the event that I accidentally break recovery or system, having fastboot working as a failsafe is a key priority.
I've also managed to locate the website for Quanta which lists a slightly-updated variant of this specific device. I have attempted to reach out to them via their contact email to see if they might provide a copy of the stock firmware at release. This might help with porting a newer version of AOSP.
Future Posts will include more details about installed apps and other information, as uncovered. canc
redrew89 said:
View attachment 5499981
Sprint Slate 8 (ANS_NKS AQT80) 8 Inch Tablet
Files: Google Drive
<Includes dumps of stock boot, recovery, splash. Attempted TWRP 3.6.0 build>
​I recently had one of these ancient tablets come into my possession, and like any good nerd, I set out to hack it as much as possible. Admittedly, I knew that this would be an uphill battle, given the relative unpopularity of this particular slate, limited resources, and nonexistent documentation. However, I have made some progress, which I'll share here for the benefit of the community. Some of the information here was collected from other threads that I found scattered about via Google. <This thread also serves as a subtle "call-to-arms" for anyone who happens to have access to this device and has the ability to assist in testing recoveries and ROMs for this device in the future. I have access to one, currently, and know where I can locate another. My Android development skills are moderate, but limited, as I have next to no experience with custom ROM creation, or low-level Android systems. Mentor-ship would also be appreciated.>
Rooting
Rooting this device can be accomplished with Kingo Root (I downloaded the APK from the offical website, be sure to enable Unknown Sources for APK installation). Once rooted, you can remove Kingo Root and update SuperSU to 2.49. This should give you root access to install EX File Explorer/Root Uninstaller to debloat Gapps/Facebook/Sprint carrier apps, which speeds up the device nicely.
Recovery
I've been attempting to make a working TWRP for this device using this guide and while I have an image that flashes and boots, it has notable issues with touch input that make it unusable for anything important. I've included a link to Google Drive where I've backed-up the most recent bootable image. Once you have root, you can install the Official TWRP app to flash IMG files to recovery. Always be sure to back-up stock recovery before flashing anything. My stock recovery dump has worked for me, but might not work for you. </Disclaimer>
Custom ROMs
<None currently exist. Future plans include a Marshmallow or Nougat-based build that has better app support than Lollipop. Interestingly, the stock app payload includes both Trebuchet Launcher and CyanogenMod File Browser. Perhaps this tablet shipped with an OEM variant of CM12? More investigation is needed.>
Other Info
Other users have reported that running this device as WiFi-only (no SIM card inserted) leaves a constantly-visible NO SIM notification. I was able to remove this by uninstalling the Sprint-provided apps and phone dialer. Also, enabling Airplane Mode and then re-enabling WiFi and Bluetooth will improve performance and battery life noticably.
I've been unable to replace the boot splash, as this device apparently uses a splash partition and I'm not sure what format the image that I dumped might have and how I could replace it. This dump is also included in the Drive link.
Notably, I have had some issue with getting fastboot commands to work properly on this device. Some commands work while others fail at the remote end. I've tried to track down the issue, trying different versions of platform-tools as well as ADB driver packages. In the event that I accidentally break recovery or system, having fastboot working as a failsafe is a key priority.
I've also managed to locate the website for Quanta which lists a slightly-updated variant of this specific device. I have attempted to reach out to them via their contact email to see if they might provide a copy of the stock firmware at release. This might help with porting a newer version of AOSP.
Future Posts will include more details about installed apps and other information, as uncovered.
Click to expand...
Click to collapse
do you have another link to the files your drive account doesnt work
Click to expand...
Click to collapse

I've also come across one recently and would be more than happy to help you test ROMs or recovery custom images.

I have one of these, would love to have a newer Android version with no bloatware and ignore the cellphone radio.