Database Develop

[NO ROOT] How to Install TWRP & custom ROM without root on Galaxy S5 G900

Hello!
This thread is to teach you how to flash TWRP, along with a custom ROM on your T-Mobile Galaxy S5 WITHOUT root!
DISCLAIMER:
Read the whole thread at least one before trying!
Anything you do to your device is your own decision. I am not forcing you to do this. If you screw something up during the process, that isn't my fault.
Custom ROMs can sometimes be unstable. PLEASE make sure you are downloading the correct file for your device model.
Tampering with your device's firmware, including custom recoveries, ROMs, or rooting your device WILL VOID THE WARRANTY.
Flashing a custom ROM WILL DELETE YOUR DATA. Consider backing up your apps, photos, videos, files, etc. online or to an external storage.
Before we start, we need to download a few things.
*Do not download anything with Safari! Safari unzips zip files, but we want them to stay zipped. DO NOT RE-ZIP THE FILE YOURSELF!!! It will not be zipped in the correct format!*
1. Odin v3.12.3: (Odin)
2. The TWRP recovery tar file: (TWRP)
3. Your custom ROM zip file. (There are many ROMs out there, but Lineage is a pretty good one: (Lineage OS klte) Choose the most recent release.) IMPORTANT: Make sure you download this to your phone's internal/external storage to an easily accessible location.
4. A GApps package. This is required if you want to be able to download apps from the Google Play Store. Go to the Open GApps page and choose ARM, and Android 7.1. You shouldn't need anything more that micro. IMPORTANT: This file also goes onto your phone's internal/external storage.
5. Your device drivers. Most of the time, Windows will automatically install the required drivers once you put in the device, but in the case this doesn't happen, try googling your devices model number and "windows drivers." Follow the process to install.
Alright, with that out of the way, let's install TWRP.
1. With your phone unplugged, boot into "Download mode." Power off your device. Then hold down the Power, Home, and Vol- buttons until you see a warning pop up.
2. Accept the warning by clicking Vol+.
3. Run the Odin exe file we downloaded earlier. (You may have to unzip the file first.)
4. Go to Options and disable auto reboot. Go back to the Log tab.
5. Plug your device into the computer. You should see Odin say "ADDED!" on the side.
6. Click "AP" and locate the TWRP recovery tar file we downloaded earlier.
7. Once you select the file, click "Start."
8. When finished, it should say "PASS" at the top. This is where you unplug your phone and remove the battery.
9. Wait 10 seconds before putting the battery back in.
10. Try booting into recovery by holding down the Power, Home, and Vol+ buttons. If it reads "Team Win Recovery Project" at the top, then congrats! You've successfully flashed TWRP! If it says at the top "stock recovery," try the whole process again from step #1.
Now we can flash your custom ROM!
1. This is where we wipe your phone's data. Click on "Wipe." Then Swipe to factory reset.
2. After you have wiped your device, click on "Install"
3. Now navigate to the ROM zip file and select it.
4. Click on "Add more zips"
5. Navigate to the GApps zip file and select it.
6. Swipe to install. This can take some time, so grab a cup of coffee and maybe check out my Youtube channel?
7. The moment of truth: click on Reboot, then System. The first boot can take a minute. If it doesn't show up after 5 minutes, remove the battery and try wiping and flashing again.
CONGRATULATIONS!! You've installed a custom ROM! Enjoy! :laugh:
EXTRA:
If you want to enable root on your Lineage OS device, you must flash an additional file first.
1. Go to this link and download the first su (arm) file and save it to an easily accessible location.
2. Boot into recovery mode once again by powering off your device, then pressing and holding Power, Home, and Vol+ until TWRP appears.
3. Click on install.
4. Select the su zip file we downloaded earlier.
5. Swipe to install.
6. Once it is installed, boot back into system.
7. Navigate to developer options in settings.
8. Scroll down to"Root Access" and change it to either Apps, or Apps and ADB.
Awesome, now you have root!
Thanks for the help:
[url]https://forum.xda-developers.com/tmobile-galaxy-s5/general/root-how-to-root-sm-g900t-firmware-t3358190[/URL]

I did not work for me, when I go recovery mode it shows:
Could not do normal boot
Odin mode.
I'm definitely not an pro at this, so can anyone help me please

Worked perfectly on the latest stock OTA!

Doesn't work for me. When I reboot in recovery ode, instead of TWRP loading I get a generic Android Recovery screen with a few options - reboot system now, reboot to bootloaded, apply update from ADB apply update from SD card, wipe data/factory reset, wipe cache partition, mount /system, view recovery logs, power off. Now sure how to proceed....

bradmccoy said:
Doesn't work for me. When I reboot in recovery ode, instead of TWRP loading I get a generic Android Recovery screen with a few options - reboot system now, reboot to bootloaded, apply update from ADB apply update from SD card, wipe data/factory reset, wipe cache partition, mount /system, view recovery logs, power off. Now sure how to proceed....
Click to expand...
Click to collapse
We’re you sure to unplug and remove the battery? This is essential to ensure the phone powers down. If you just power down the phone will reset the recovery to avoid TWRP. You have to remove any power source to force a shutdown before it can reset. Please feel free to respond and I’ll be happy to help to the best of my abilities!

Thank you so much for this tutorial. It worked perfectly in my SM-G900MD, and it's easier than the method suggested by the Lineage OS page itself. :good:

Thanks, these steps worked just fine on an SM-G900T, and were very easy to follow.

Thank you! This worked beautifully.
Only thing that didn't work the first time is, is that it told me to download the Gapps Android 8.1 file instead of 7.1.

I hear people talking of unlocking the bootloader in order to install a custom ROM. Why haven't you mentioned that in this article?

Had the "FAIL! (Auth)" problem with flashing TWRP with Odin.
It seems that after I have disabled Reactivation Lock (the standard feature that requires activation of the phone with Samsung account) it helped to succeed flashing TWRP.

Hi All,
Thanks for a great and useful guide. Whilst it says this can be achieved without root, which is fantastic... It doesn't mention anything about tripping Knox or not?? I assume this will trip the Knox counter, won't it ?? Or do this method bypass that ??
Thanks, Lister

adult supervision needed for Samsung S5 Lineage 17 install
Hi, I'm good with adb and fastboot, running Linux with the commandline Odin4. I can get the phone to the warning screen about the danger of installing other Roms. How do I proceed? What are the commandline options to use to flash the LineageOS 17 with odin4 ? The Odin4 help file isn't very helpful.

Could not do normal boot
I am not an expert at this and I am having the same issue as The Verg
I have a message at the top "Could not do normal boot" same as him
I've been at this for 2 days now I'm just about at my ends wit
My phone is a Samsung S5 Active model SM-G870W
and I can easily rooted it or reinstall the stock file and put it back to original
and I've done that hump time but this TWRP file I just can't install it
to update this phone to a more recent software and basically install
an S8 or S9 software in it (mind you version 9 Pie would be OK0
and make this old phone a real beast.
I read somewhere about the OEM button which does not exist on this phone
whatever explanation they are giving to unlock it and make the button appear
all of a sudden is bs in my book.
Now please help me with this phone and the other guy by the same token
Is there another way I can get into this phone and wipe it clean and
boot it with thru the abd file or access the sd card or the internal
storage of the phone.
How can I add a picture of my phone to this thread

[GUIDE][Z2 FORCE XT1789-05] Bootloader/TWRP/Custom ROMs/Root/Dirty flashing/Unbrick

First, thanks to @Uzephi and @41rw4lk for helping me to use/recover my phone. Please, read and do not underestimate the guides: our phone is tricky! We have two system partitions (slot a and b) to allow stock updates on-the-fly. This complicates the normal flashing process and if you do not follow the steps, you may bootloop. Use these guides at your own risk!
Reading this page is a good beginning to understanding the A/B partitioning scheme and how Motorola Z2 Force works:
1) Our phone has A/B partitioning, so flashing Magisk/XPosed is different
2) It does not support Project Treble (faster stock updates)
3) It does not a recovery partition, so flashing TWRP is different
Note also that the RSD Lite from Motorola has issues with Windows 10 and you’ll need to manual flash firmware if you bootloop (see Process E below). Other way is directly flashing from Qualcomm EDL mode (Emergency Download Mode) from which users can perform various tasks like unbricking, unlock bootloader, and installation of any custom ROMs.
Right now, this guide has 5 parts (maybe we can dual boot our phone in the future). If you just want to use a rooted stock ROM, please, search for other guides here on xda. These guides were written (and tested) using a Motorola Z2 Force XT1789-05 phone (Brazil), although most of it should work for other variants if you download and use proper firmware files for these other phones. For other models, better if you follow Uzephi’s guide.
A. Opening bootloader
B. Preparing the phone to move into custom ROMs (AOSP) + TWRP recovery
C. Flashing a custom AOSP ROM + rooting
D. Dirty flashing AOSP ROM updates
E. Recovering from bricks or returning to stock
F. Oreo ROM features comparison table
If you want to move your Motorola Z2 Force to Project Treble ROMs, please, check this guide.
Here is a list of the ROMs that are waiting for you.

A. Opening bootloader
With enough battery in your phone (80%), you can follow the Motorola official guide which steps are:
1. Backup everything you need. Your phone will be reseted including the internal sdcard.
2. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the Settings). Go to Developer Options, click the OEM unlock option to enable it. Also enable USB debugging.
3. Install the Motorola drivers in your computer, but (in my personal experience) not the Android SDK suggested in the official guide. Instead, extract these adb/fastboot files in a blank folder of your computer.
3.1) Do not use other adb/fastboot binaries: I cannot guarantee they will work.
3.2) You need to use a USB 2.0 port of your computer. Some users report that USB 3.0 will also work.
4. Open a command line window in the adb/fastboot folder (step 3), reboot the phone into the bootloader (see adb command below or press power + volume down buttons). Plug the phone on computer (see 3.2 above). Test the connection and run the command to get the code for unlocking:
Code:
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data
You’ll get:
Code:
(bootloader) Unlock data:
(bootloader) <code 1>
(bootloader) <code 2>
(bootloader) <code 3>
(bootloader) <code 4>
(bootloader) <code 5>
5. You’ll need to join 5 codes and, after logging into your own Motorola account, check by clicking the button “Can my device be unlocked” (step 6) by Motorola here. Read the text: your warranty will be void if you go ahead. Consider if you have enough knowledge, time and money to deal with a troublesome (or bricked) device. Although, it’s not that easy to hard brick this phone (see process E below).
Code:
<code 1><code 2><code 3><code 4><code 5>
6. You’ll receive back an email with the code to unlock your bootloader (if it is available for your model). Then you’ll run the following command:
Code:
fastboot oem unlock <code 1><code 2><code 3><code 4><code 5>
7. You’ll receive a warning that all your data would be erased (see step 1 above) and need to re-run the same command to confirm. At this point, your bootloader should be unlocked. As an Android restriction, each time you boot the phone you’ll see a warning. Do nothing, wait for 5 seconds and the phone boots normally. Some users bother with this warning and try to get rid of it.

B. Preparing the phone to move into custom ROMs (AOSP) + TWRP recovery
Requirements: unlocked bootloader (see guide A) and no security lock: disable PIN, gestures and fingerprinting (because TWRP cannot read the locked/cryptographed data of the phone). Enough battery in your phone (80%).
If you do not prepare your phone to custom ROMs and if you do not have both bootloaders of the phone in the same Android version of the ROM you’ll flash, you’ll hard brick the phone and lose also the access to the bootloader! You’ve been warned: follow the guide!
Note: if you hard brick, I suggest you be prepared to follow the Unbrick Qualcomm mobiles with Step-by-step guide or the Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 guide, but I never tested them myself. You can also use Qualcomm Flash Image Loader (QFIL) tool.
1. Backup everything you need. Your phone will be reset including the internal sdcard.
2. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the Settings). Go to Developer Options and enable USB debugging.
3. Install the Motorola drivers and the adb/fastboot files.
3.1) do not use other adb/fastboot binaries: we cannot guarantee they will work.
3.2) you need to use a USB 2.0 port of your computer. Some users report that USB 3.0 will also work.
4. Download the firmware of the same Android major version of the future ROM you’ll install (Oreo for Oreo ROMs, for instance). When (and if) we move to Android P, most probably we will need to follow this guide again.
- Retail (XT1789-05) (Europe/Brazil).
- Other models (branded): ATT, Sprint, T-Mobile (TMO), USC, Verizon.
- Note: NPXS26 versions stand for Nougat and OPXS27 for Oreo. You do not need Nougat versions for anything.
5. Extract the zip contents to a blank folder in your computer.
6. Download the FlashAll_XT1789-05.zip file, extract the content and move all files to the same firmware folder (step 5 above). Be sure to overwrite any file (if needed).
7. Run the Preparation.bat file there to generate the flashfile.bat file that will send the commands to the phone. Credits: the original preparation files were from RootJunky (can be downloaded here) and include more options that we do not need for our purpose here. Also, it includes adb/fastboot binaries that could not work with our phone.
8. Reboot the phone into the bootloader (see adb command below or power + volume down buttons). Open a command line window in the firmware folder (step 5 above), test the connection and execute the flashfile.bat file generated on step 7.
Code:
adb devices
adb reboot bootloader
fastboot devices
flashfile.bat
Never ever unplug the device from the USB 2.0 port while flashing the firmware. This could cause a hard brick and your device will be dead.
9. There is a pause at the end. You should review if everything went fine (or even click on the menu of the command line window, select all and copy&paste the contents in a .txt file for further help/revision).
10. Reboot your phone into the system (ROM) and do a quick configuration (remember that everything will be deleted when you install TWRP further…).
11. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging.
12. Download both the .img and .zip file of the TWRP recovery from the official site. It's the same file for all models/variants of Z2 Force phone. Put the files into our firmware folder (step 5 above). Copy the .zip file to the phone internal card. Note: versions older than 3.2.2-2 does not support PIN/Password/Fingerprint, so disable them before proceed. Most probably, ROMs before July 20th, 2018 cannot be flashed in older TWRP.
13. Now boot (not flash) the TWRP .img file using a command line window in the same firmware folder (step 5 above):
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot <TWRP file name>.img
14. Only now that you’re inside TWRP temporarily flash the TWRP .zip file you’ve saved into the phone (step 12 above).
15. Reboot into TWRP (use the main reboot menu in TWRP).
16. Now, you should reboot again into bootloader: inside TWRP, go to Reboot menu and choose Bootloader.
17. Now you will wipe all user data via bootloader. This is necessary to use an AOSP ROM when you come from stock. Using a command line window in the same firmware folder of your computer (step 5 above), run the following commands:
Code:
fastboot devices
fastboot -w
18. Now you can reboot the phone into System using the buttons volume up/down to navigate and confirming with the Power button. You’ll be with stock ROM and TWRP. If you want to move to a custom AOSP ROM, do a quick configuration: into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging and go to the proper guide (Process C).

C. Flashing a custom AOSP ROM + rooting
1. Requirements:
1.1 Motorola drivers.
1.2 Our custom adb/fastboot files (others may not work!).
1.3 USB debugging enabled into the Developer Options.
1.4 If you're using TWRP older than 3.2.2-2, disable disable PIN/gestures/fingerprinting. Also, most probably, ROMs after July 20th, 2018 cannot be flashed in older TWRP.
1.5 An USB 2.0 port of your computer (some users report that USB 3.0 will also work).
1.6 Two Oreo bootloaders (process B above).
1.7 Permanent TWRP
1.8 Enough battery in your phone (80%).
2. Download the AOSP ROM you want and move the .zip files to the phone. Right now, we have:
2.1 Dirty Unicorns: no need for Gapps. Official and Weeklies can be dirty flashed interchangeably. RC has a different signature. Support on Google+ page. More about DU kernel.
2.2 Lineage OS 15.1. MindTheGapps needed. OpenGapps not compatible yet. XDA thread.
2.3 Mokee: Gapps needed. Take care: online guides assume that you already have an AOSP ROM, TWRP and rooted device.
Deprecated (?)
2.4 AOSiP: no need for Gapps. XDA thread.
2.5 Invictrix. Gapps are built in. XDA thread
3. Choose the root method and download the .zip files: Magisk (suggested) or LineageOS SU Addon. Move the .zip files to phone. Note: if you bootloop on Magisk, most probably you’re flashing a wrong/different version of Magisk or you did not reboot between flashing ROM/Gapps and Magisk. Note: SuperSu is deprecated.
4. Reboot into TWRP:
Code:
adb reboot recovery
Then flash the ROM. It will be flashed in two steps only in the “other” slot. We have two slots, A and B. Our phone can be upgraded on-the-fly because the update is always applied to the slot not booted, the “other” slot. Then, immediately, flash the .zip TWRP or you will lose it.
5. Go to Reboot menu of TWRP and reboot into bootloader. Then, in the folder with adb/fastboot binaries (see 1.2 above), you need to wipe data (including sdcard) with the following commands:
Code:
fastboot devices
fastboot -w
6. Now you need to reboot the phone into System using the buttons volume up/down and confirming with the Power button (or typing fastboot reboot into the command line windows). You’ll be with an AOSP ROM and TWRP.
7. Once into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging if you intend to dirty flash ROM updates.
8. Reboot into TWRP again, flash Magisk (your settings and modules will be preserved). Note: if you bootloop on Magisk, remember it is mandatory to reboot between ROM flash (step 4 above) and GApps/Addon flash due to verity/slot-swap logic.
9. A good place to read what is not working is in the section known problems of LineageOS.

D. Dirty flashing AOSP ROM updates
1. If you follow all the processes above, you can dirty flash updates because you have:
1.1 Motorola drivers installed.
1.2 Specific adb/fastboot files for our phone and an USB 2.0 port in a Windows computer (some users report that USB 3.0 will also work).
1.3 Unlocked bootloaders (Process A above).
1.4 Permanent TWRP running and TWRP .zip file placed inside your phone and ready to be flashed again.
1.5 An AOSP ROM already running.
1.6 Developer Options and USB debugging enabled.
1.7 If you're using TWRP older than 3.2.2-2, disable disable PIN/gestures/fingerprinting. Also, most probably, ROMs after July 20th, 2018 cannot be flashed in older TWRP.
1.8 Enough battery in your phone (80%)
2. Download your ROM .zip update, copy it into the phone sdcard and reboot your phone into TWRP. See download links here.
3. Within TWRP you should flash (install) things in the following order:
3.1 ROM update .zip file. Remember that, at this time, the update will be flashed int the other slot and inside phone you’ll have both the system before update (in the booted slot) and updated ROM in the other slot.
3.2 TWRP .zip file (step 1.4 above) once again (do not skip this step or you’ll bootloop!).
4. Reboot to System: if you skip this step, you’ll bootloop.
5. Reboot into TWRP again, flash Magisk (your settings and modules will be preserved) or LineageOS SU Addon .zip file. Note: if you bootloop on Magisk, most probably you’re flashing a wrong/different version of Magisk. I suggest v16.0 and, after you got rooted with 16.0, you can update. It is mandatory to reboot between ROM flash (step 4 above) and GApps/Addon flash due to verity/slot-swap logic.
Note: SuperSu is deprecated.
6. Wipe Dalvik/ART cache: go to Wipe menu of TWRP > Advanced Wipe > Dalvik/ART Cache only.
7. Reboot your phone into System (ROM) will use the “other” slot, the one with the updated ROM.
8. You can use XPosed installer app (and reboot).
9. Now you can add your PIN, fingerprint, gestures back until next flashing.

E. Recovering from soft bricks or returning to Stock
If you’re reading this is because you already unlock your bootloader (see guide A) and anything went wrong, but you still can boot your phone into bootloader. Plug your phone and get enough battery (even if you do not see any charging signal).
1. Install the Motorola drivers and the specific adb/fastboot files for our phone. Remember, follow the rules because our device is tricky!
1.1) Do not use other adb/fastboot binaries: we cannot guarantee they will work.
1.2) You need to use a USB 2.0 port of your computer (some users report that USB 3.0 will also work).
2. Download the latest firmware for your model:
- Retail (XT1789-05) (Europe/Brazil).
- Other models (branded): ATT, Sprint, T-Mobile (TMO), USC, Verizon.
- Note: NPXS26 versions stand for Nougat and OPXS27 for Oreo. You do not need Nougat versions for anything.
3. Extract the zip contents to a blank folder in your computer.
4. Download the FlashAll_XT1789-05.zip file (it should work for other Motorola Z2 Force models as well), extract the content and move all files to the same firmware folder (step 2 above). Be sure to overwrite any file (if needed).
5. Run the Preparation.bat file there to generate the flashfile.bat file that will send the commands to the phone. Credits: the original preparation files were from RootJunky (can be downloaded here) and include more options that we do not need for our purpose here. Also, it includes adb/fastboot binaries that could not work with our phone.
6. Reboot the phone into the bootloader (see adb command below or power + volume down). Open a command line window in the firmware folder (step 5 above), test the connection and execute the flashfile.bat file generated on step 5.
Code:
adb reboot bootloader
fastboot devices
flashfile.bat
Never ever unplug the device from the USB 2.0 port while flashing the firmware. This could cause a hard brick and your device will be dead.
7. There is a pause at the end. You should review if everything went fine (or even click on the menu of the command line window, select all and copy&paste the contents in a .txt file for further help/revision).
8. Reboot your phone into system (ROM) and do not forget, later, to enable the Developer Options and USB debugging again.
Note: if you hard brick, I suggest you be prepared to follow the Unbrick Qualcomm mobiles with Step-by-step guide or the Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 guide, but I never tested them myself. You can also use Qualcomm Flash Image Loader (QFIL) tool. Maybe these Latest 2017 Qualcomm Diag QD-Loader Windows 10 Drivers signed will help you.

F. Oreo ROM features comparison
This is a table for Oreo ROM features comparison for Motorola Z2 Force - nash.
I would like to receive feedback and updates from the users, as I can't keep changing from one ROM to another and they get new features, updates, improvements, etc.
I consider Lineage OS 15.1 our stock ROM regarding to customization. So, it's not listed there.
Legend:
Code:
X = Feature present
XX = ROM excels in this particular feature (in my opinion).

If you want to move your Motorola Z2 Force to Project Treble ROMs, please, check this guide.
Here is a list of the ROMs that are waiting for you.

I came back to stock ROM. the problem is that it gets stuck in the initial configurations of the android trying to find a wifi network, to continue the configuration, without success, because I see in fastboot that the baseband is unknown, and I also can not install any rom, or recovery image because I have the following message in fastboot: FLASHING_LOCKED. and since I can not get past the initial android settings, I also can not unlock the developer options to enable OEM unlocking. now I'm standing in a rom that does not leave the initial configuration, it does not connect to any network and a fastboot that does not let me install anything. and I also tried the recovery mode and even tried to install an update via sideload, without success. I do not know what else to do if you can give me a light.

renanjones said:
I came back to stock ROM. the problem is that it gets stuck in the initial configurations of the android trying to find a wifi network, to continue the configuration, without success, because I see in fastboot that the baseband is unknown, and I also can not install any rom, or recovery image because I have the following message in fastboot: FLASHING_LOCKED. and since I can not get past the initial android settings, I also can not unlock the developer options to enable OEM unlocking. now I'm standing in a rom that does not leave the initial configuration, it does not connect to any network and a fastboot that does not let me install anything. and I also tried the recovery mode and even tried to install an update via sideload, without success. I do not know what else to do if you can give me a light.
Click to expand...
Click to collapse
I see two possible scenarios:
1. Your bootloader is locked (yet) (see guide A).
2. Your in a "false locked" situation that, maybe, could be solved by resetting data via recovery or in bootloader (with the command: fastboot -w).

Great tutorial, but I did not get 4g in any of the roms, only 3g

Gutto said:
Great tutorial, but I did not get 4g in any of the roms, only 3g
Click to expand...
Click to collapse
I got 4G in any ROM... AOSIP, DU or Invictrix...
Are you using a branded (carrier) phone? If not, maybe you should return to stock (to recover any changes on partitions).

Technical said:
I got 4G in any ROM... AOSIP, DU or Invictrix...
Are you using a branded (carrier) phone? If not, maybe you should return to stock (to recover any changes on partitions).
Click to expand...
Click to collapse
My cell phone and Sprint, I did every process that you indicated, but not 4G

So I followed the instructions as noted, as soon as I got to the root installation part, it started throwing a "cannot mount /system" error. I thought a reboot would solve the issue, but now I think I'm bricked. Can't boot into anything, all I can do is plug my phone in and listen to it keep disconnecting every 10 seconds or so. The phone had booted up fine prior to starting the installation process, and I don't see how just a bad ROM install is preventing me from getting into either bootloader or recovery. Any advice?
For clarity, i'm unable to use QBOOT to do anything since after it hits the "powered on" state I'm assuming it's in, it just resets and does the same thing over and over again

shalpp said:
So I followed the instructions as noted, as soon as I got to the root installation part, it started throwing a "cannot mount /system" error. I thought a reboot would solve the issue, but now I think I'm bricked. Can't boot into anything, all I can do is plug my phone in and listen to it keep disconnecting every 10 seconds or so. The phone had booted up fine prior to starting the installation process, and I don't see how just a bad ROM install is preventing me from getting into either bootloader or recovery. Any advice?
For clarity, i'm unable to use QBOOT to do anything since after it hits the "powered on" state I'm assuming it's in, it just resets and does the same thing over and over again
Click to expand...
Click to collapse
Have you tried holding vol dwn + pwr btn to force it into bootloader mode? If you can get there, then you can use the keys to get to recovery and try a factory reset. If that don't work, go back to bootloader mode and try flashing back to stock. Might double check that the battery has plenty of charge.

41rw4lk said:
Have you tried holding vol dwn + pwr btn to force it into bootloader mode? If you can get there, then you can use the keys to get to recovery and try a factory reset. If that don't work, go back to bootloader mode and try flashing back to stock. Might double check that the battery has plenty of charge.
Click to expand...
Click to collapse
I'm unable to get the phone out of qboot (or whatever it's called). I've tried using a blank-flash but all that happens is device restarts as made evident by the "device disconnect" sound playing every few seconds. The phone had around 80% when I started the process. Should I just let it die and try loading into BL after a few hours of this thing power cycling itself?

shalpp said:
I'm unable to get the phone out of qboot (or whatever it's called). I've tried using a blank-flash but all that happens is device restarts as made evident by the "device disconnect" sound playing every few seconds. The phone had around 80% when I started the process. Should I just let it die and try loading into BL after a few hours of this thing power cycling itself?
Click to expand...
Click to collapse
It's weird that it is power cycling like that. Have you tired unplugging the phone and booting? Whether it's recovery, bootloader, qboot; you need to get to one place or the other if possible because power cycling won't allow you to do anything. If you can get a stable boot in any mode I would suggest moving your cable to another port so any corruptions aren't a factor anymore. I don't think a drain will resolve anything, but I've never heard anyone mention power cycling like that.

41rw4lk said:
It's weird that it is power cycling like that. Have you tired unplugging the phone and booting? Whether it's recovery, bootloader, qboot; you need to get to one place or the other if possible because power cycling won't allow you to do anything. If you can get a stable boot in any mode I would suggest moving your cable to another port so any corruptions aren't a factor anymore. I don't think a drain will resolve anything, but I've never heard anyone mention power cycling like that.
Click to expand...
Click to collapse
Power cycling is just an assumption since regardless of whatever port its in it keeps an endless loop of connect, disconnect". Basically after rebooting the device after attempting to install the ROM is when it went black and started not doing anything other than connect, disconnect

shalpp said:
Power cycling is just an assumption since regardless of whatever port its in it keeps an endless loop of connect, disconnect". Basically after rebooting the device after attempting to install the ROM is when it went black and started not doing anything other than connect, disconnect
Click to expand...
Click to collapse
When it's trying to connect do you have a pop up on your pc showing what it sees the phone as? Does it say nash fastboot, or 9008, Z2? That might give some idea of where it's failing.

41rw4lk said:
When it's trying to connect do you have a pop up on your pc showing what it sees the phone as? Does it say nash fastboot, or 9008, Z2? That might give some idea of where it's failing.
Click to expand...
Click to collapse
It appears as Qualcomm 9008
It only starts the loop after starting a blankflash. That's about the only response I get out of the device, otherwise it does absolutely nothing, no combination of buttons do anything
Edit: Confirmed connect/disconnect on another machine with the same driver configuration

s10 galaxy g973f no boot after flash magisk patched firmware

Ieudhd

i donloaded diud

Hello Sams10, did you make the bootloader before or not as explained in the tutorial.
You said your flasher with odin more detail would be welcome, how did you do there according to your comment your flashed directly in download mode without having done the manipulation for the bootloader and then did what.

bootloader unlocked and kg checking

every instructions for s10 is outdated including the lineage os website and youtube i have checked all

heimdalll latest 1.4.2 doesnt work with samsung s10.

19.9.2022 on latest android firmware new zealand firmware custom rom doesnt work , only europe and americas will work

Hello Sams10, already a little politeness because I said hello to you, you post 4 times without saying hello.
I don't understand the unlock bootloader ok then S10 is good s10 exynos or 5 G, I followed John Wu's tutorial as explained in the magisk thread on this forum no problem.
You have well modified in magisk AP of the official rom then trafer on your pc with adb pull then odin 3.14.4 flash the 4 files BL-AP patched-CP Home CSC.

g973F exynos, not 5g, u must be americas europe firmware , vodafone nz firmware probably doesnt work

this is my current download mode
my screen is cracked thats the purple lines and dead pixel on top left

Not work

Hello Sams10, you start in dowload mode you flash with odin 3.14.4 the official firmware the one mark in my signature me AUT or XEF lash the 4 BL-AP-CP-CSC files it will restart as on the first day. Then install magisk 25.2 you transfer AP on your S10, you modify with magisk you will have a file in internal memory in dowload magisk_patchedxxxx.tar you transfer it with ADB on the pc which in adb must give this adb pull /sdcard/Download/magisk_patched-25200_G3e9K.tar
once transferred ok you put yourself in dowload mode and you put the file BL -AP patched -CP -home CSC you start you let it restart and you open magisk to activate zygisk then you install the modules you will find here https://forum .xda-developers.com/t/discussion-magisk-the-age-of-zygisk.4393877/
instalation look here from john Wu https://topjohnwu.github.io/Magisk/install.html
read the instruction part, then when you have finished and root I will send you the file to remove the warning message at start-up ok

I use ap magisk patched and CSC , not home CSC when I flashed and had boot loop

Does it have to be an adb pull for the patched firmware from Android , I just use file transfer on windows to transfer the magisk patched ap file from the s10 to the windows

Try with home CSC as john wu says you have to do adb from s10 to pc with adb windows not send all.

Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files.

John Wu says CSC not home csc because he want to erase firmware data

Hello Sams10, yes you made a backup of your data before with smart switch or others. For me it worked if you follow the present tutorial look on my tutorial
1- The bootloader follow explanation Use vol down + vol up + USB cable plugged into a PC to boot the phone into download mode;
Long press vol up then confirm that you want to unlock the bootloader (this is only needed once);
* Please note that all your data will be erased, including internal memory, and the phone will restart!!
5- Let the phone start normally, go through the configuration and connect to the Internet (wireless or mobile data) in order to unlock
6- Make sure OEM Unlock is enabled in Developer Settings.
2- Once reboot install magisk 25.2 APK.
3- Download the official firmware on Samobile.com or frija you will find this on the forum.
4- Transfer the official firmware AP to the smartphone.
5- Open magisk recovery mode choose corrective mode choose the AP download press "let's go."
6- Once the modification is finished in the root directory, download a patched_magiskxxxx.img.tar file if found.
7- Transfer it with adb pull like this adb pull /sdcard/Download/patched_patched.magiskxxxx.img[.tar] you can rename it "patched_magisk.img.tar"
8- Put your smartphone in download mode Use vol down + vol up + usb cable connected to a PC to start the phone in download mode, briefly press vol up to
confirm that you want to enter download mode;
9- Open Odin latest version placed 4 files following BL-AP magisk patched.img.tar-CP-home CSC leaves auto start checked in odin option.
10- It will restart open magisk activated Zygisk restart install safetynet modules - shamiko-hidemagisk prop config-busybox nk-lposed see on this page https://forum.xda-developers.com/t/discussion-magisk-the-age -of-zygisk.4393877/
message #3-#6 to #9.
11- Install foxmagiskmodulemanager the catalog of modules for magisk here https://github.com/Fox2Code/FoxMagiskModuleManager/releases
12- Once rooted the security message for the removed open Odin place UP-param.tar in AP and flashed. See attached file
Up_param.tar download link on my mega here to know for S10 exynos for S10e- S10+ versions see 5G I don't know if it works.

Is this normal I have to wait about 30 minutes after power off to try get into download mode??

Maybe something is broken the phone like doesn't turn off properly or something, have to wait sometimes one hour

[GUIDE] Installing Lineage 18.1 (& more) [X00H] [X00I]

In this guide, i'm going to be a bit straightforward on how to install LOS 18.1 on your X00H/X00I device.
For the process, you need:
Your X00H/X00I device;
The following must be unlocked (if you didn't, you can follow the howto over my post);
A rooted phone/tablet with Magisk (any ADB & Fastboot tool is fine, but i suggest using this for simplicity);
In case you have none of the above, even a PC or Laptop with ADB and Fastboot binaries installed will suffice;
If you're on Windows, you can get the installer over GitHub;
If you're on Linux, hop into your package manager and install them via terminal (the following example will be for Debian/Deb-based/Ubuntu/Ubuntu-based distros. If you're on Arch, Fedora, etc.: just search for "fastboot" by using the respective pkg manager's search flag, then install it basing from the name it's repo gives):
Code:
sudo apt install fastboot
An USB cable (should come into the device's box, also must be capable of data transfering);
If you're going to do the process via a rooted device, the Asus device should come in it's packaging with an OTG adapter (be sure to attach the following to the rooted device);
PBRP (Pitch Black Recovery Project) for the device- OG post can be checked here;
Latest version for X00H;
Latest version for X00I;
If your device is an X00I, you can alternatively get TWRP instead;
The Android 9 Beta update (you MUST have the device updated to that version, else you'll risk the device to be bricked- for more info, check the OG post by Seba);
If you want to flash it via stock recovery, you can get the file over ASUS' site on the device;
Download for the X00H;
Download for the X00I;
If you have already flashed a custom recovery on your device, you can get the "custom recovery flashable zip"over SebaUbuntu's site;
.zip file for the X00H;
.zip file for the X00I;
Tiny discalimer on the flashable .zip above: once installed, your device's recovery will be replaced to stock (in other words, you'll lose the custom recovery);
The Lineage OS 18.1 rom and recovery (credits to @miya0405 for finding the site);
ROM and LOS Recovery for the X00H;
ROM and LOS Recovery for the X00I;
If you have all of the things required in the list, let's go!
--------------------------------------------------------------
Installing the Android 9 Beta​Stock Recovery method:​
Download the Android 9 Beta over ASUS' site (any device is fine, even using the phone itself);
Put an SDCard inside the device;
Move the .zip file inside the SDCard;
Turn off the device;
Boot into recovery (do Power + Vol.up combo- if your device's unlocked, tap on the volume button and select "Recovery" by pressing on the power button to confirm);
Select "Update from sd card";
Select the .zip file you've downloaded;
Wait for the update to install;
After updated, go back and select "Power off";
Custom Recovery Method:​
Download the Android 9 Beta flashable .zip over SebaUbuntu's site;
Put an SDCard inside the device;
Move the .zip file inside the SDCard;
Turn off the device;
Boot into recovery;
Select "Install";
Select the "External Memory" storage;
Search for the .zip file inside the SDCard;
Tap on it and install it, unchecking everything;
Swipe to continue and let the .zip file install;
The recovery will print you text on the progress (also gives advice on what to do after install);
Reboot to system;
Power off the device;
----------------------------------------------------------------
Unlocking the device:​Just a tiny reminder if you haven't yet, check my guide about it: then, resume from this point and proceed;
----------------------------------------------------------------
!!A word of advice!!​Don't install PBRP recovery just yet!
If you'll pick PBRP instead of the LOS recovery as the custom recovery of choice, flashing LOS 18.4 with it should make Lineage 100% unbootable and stuck in a bootloop!
Don't reboot back to PBRP if bootloops happen:
neither don't fix the "Cache" partiton with it, else it'll cripple more Lineage and redirect the boot to recovery or fastboot/bootloader!
TL;DR: Don't do my same mistake and flash the recovery partition with the wrong recovery (on the bright side, the device will still be salvageable).
----------------------------------------------------------------
Flashing Lineage Recovery:​Before proceeding, do the following firsthand:
Be sure to have the ADB & Fastboot binaries installed;
Your device rebooted to fastboot/bootloader mode (any method is acceptable);
Must have downloaded the recovery for your specific model (links are on the "required" list);
The device must be connected to the host machine (if you're using a rooted phone, be sure to have the OTG adapter connected to it first);
Rooted Android Device Method:​
Open the "ADB & Fastboot"tools of your choice;
Whether it is a terminal or the app i've suggested earlier: this portion will purely give instructions if you have the app;
If you're going to do the process via terminal, then jump to the "Linux Method" instead;
If it is the first time you open the tool, it should ask for root perms.- allow them;
Tap on the top right corner of the UI;
Tap on "Fastboot";
Tap on "Refresh";
Go to the "Partition" title, next to it you should see a dropdown menu;
Select "recovery";
Tap on the "Flash" button;
A file manager should open: search where the lineage recovery is (typically you can find it in the "Download" folder. The file should be called "recovery.img");
After selected, the app will automatically flash the recovery for you;
Disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
Linux Method:​
Open the terminal (use the shortcut CTRL+ALT+T to open it, preferrably);
Do the following:
Code:
lsusb
# This checks if your asus device is connected proper to the machine
# If it is, lsusb should output something around a "Google" or "Qualcomm" device on the ID Bus
cd Downloads
# If you have put a different language locale, cd into the Downloads folder with it's localized name
ls
# List for the files inside the folder. You should see a file called 'recovery.img' inside
fastboot devices
# Tell fastboot to check if any device on bootloader/fastboot mode is connected
fastboot flash recovery recovery.img
# Gives fastboot the instruction to flash the .img file to the desired device's partition, which is the recovery in this case
After done flashing, disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
Windows Method:​GUI Method:​
Simply use the "Latest ADB Launcher"executable located on the desktop of your PC;
Just make sure to flash the recovery partition with the "recovery.img" file;
Terminal Method:​
Navigate with the File Explorer;
Go to your Downloads folder and find for a file called "recovery.img";
Cut and paste it to where the ADB and Fastboot tools are installed at;
Click on your mouse's right button;
Select "Open terminal here" over the contextual menu;
A terminal should pop-up (Command Prompt, that is);
Type in the following:
Code:
fastboot devices
fastboot flash recovery recovery.img
Wait for the recovery to flash on the device;
After done so, disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
------------------------------------------------------------
Installing Lineage OS 18.1:​Before proceeding, do the following firsthand:
Your device must be turned off;
Must have deleted the Android 9 Beta .zip file from the SDCard, for avoiding accidents;
Download the Lineage file off of the "required" list's links for your specific model;
Put the downloaded .zip file on an SDCard;
Insert the SDCard inside the device's slot;
Boot up into recovery mode;
Select with the volume keys "Apply Update" > "Apply from sdcard" and confirm with the power button;
Select the LineageOS .zip file;
Confirm with the power button;
Let the rom install by the recovery;
After install, navigate to the back button with the volume keys;
Select "Factory reset" > "Format cache partition";
The recovery will ask you the following:
Code:
Format Cache?
THIS CAN'T BE UNDONE!
Select "Yes";
Go back;
Select "Reboot system now";
First bootup will take some while, but you'll be greeted by the setup screen in no time.
Congratz, now your device has Lineage OS installed!
-------------------------------------------------------------------
Extras/FAQ Section:​Q: Is it possible to get root priviledges on the device?​A: Sure! There are different ways to apply root on the ROM, but feel free to pick whichever method you like:​
Rooting your device by picking it's 'boot.img' (exactly located on the folder of the respective model) over SebaUbuntu's Lineage site and patch it with an already-rooted device that has the Magisk companion app installed (requires no recovery patching, but it is required to boot the asus device in fastboot mode and patch the boot partition);​
Downloading the Magisk companion app over it's GitHub page, rename the .apk file by replacing '.apk' to '.zip' via file manager, patch PBRP over the recovery partition (with one of the methods listed over 2 titles above this one), and install the 'magisk.zip' file like you could usually do on any other device with custom recovery;​
If you use an X00I device, you can preferrably install TWRP from here instead of PBRP;​
After applied root on the device, patch back on the device the Lineage recovery- just for avoiding any inconvenience if you want to factory reset the device;​
Q: My device has Lineage installed, but the bottom buttons don't work. Is there a way to enable a virtual navbar?​A: Yep, but it's a bit of a tricky process. You must have either apps like Terminal Emulator or Termux installed for making this work- as an extra, you could get other keyboards like BeHe Keyboard or Hacker's Keyboard: but that is only if you've picked Terminal Emulator as your choice.​For direct instructions, follow this (you must be inside the terminal app of your choice and already gave storage perms to it firsthand):​
Code:
su
mount -o rw,remount /
vi /system/build.prop
# After come this far, go to the bottom of the build.prop file by scrolling with the touch screen
# On your keyboard, press the I key. This should make vi enter into INSERT mode
# When done so, add the following line on the build.prop file
qemu.hw.mainkeys=0
# For getting out of INSERT mode, find on your keyboard or terminal UI the ESC button
# For quitting and saving the file on vi, type the following
:wq!
# This should make vi quit and save the modifications to the build.prop file
# For rebooting the device straight from the terminal, just type in
reboot
# The device should immediately reboot, and upon unlocking: the virtual navbar should appear
Q: Can it be possible installing MicroG on the device?​A: You can! Every method for installing MicroG perfectly works on this ROM;​
Q: I have MicroG installed on my device, but i want to apply signature spoofing for extra functionality. Is this possible?​A: Sadly, due to the tinkering i've done on my side: the ROM gets a meltdown when modifying the 'services.jar' file is involved (root or non-root). If you follow some guides online (despite being few), the ROM, regardless of what you do or which method you follow: ​it will end up in a bootloop (or, to be more specific, the SystemUI starts to become picky);​
------------------------------------------------------------------
Credits:
miya0405 (for the lineage site)
SebaUbuntu (for the LOS rom, recovery, and PBRP recovery)
Erwin Abs (PBRP Recovery)
aaaaaaziskurnia (TWRP recovery for the X00I)
You, for dedicating your time on reading this long guide!

[GUIDE][ROOT] Unlocking and Improving Your Lenovo ThinkSmart View (CD-18781Y)

Improving Your Lenovo ThinkSmart View (Custom Recovery, Root, Play Store, Custom Webview)​Huge credit to @deadman96385 on how to flash your Lenovo Thinksmart View device and providing access to the firmware files! Credit to @WhyPartyPizza on reddit for the adb enable steps. And also, credit to @Xi07 on providing a way to install TWRP and demonstrating that it is possible to get the Play Store working. And also credit to @garnir4ik on showing us that we can root the device.
The point of this guide is to organize all the information we have on the device and provide a way to make the device more usable (especially since some of the software on the device is outdated).
The guide covers how to:
Install TWRP (optional) and Magisk (recommended) on the device
Install microG and the newest version of the Google Play Store (Magisk required)
Update Webview (needed for Home Assistant)
I'm still trying to figure out how exactly to do certain things on this device so feel free to leave any new information you find!
Installing TWRP (optional) and Magisk (required for Play Store)​Quick Blurb:​To install TWRP, you will need to flash new firmware onto your tablet. However, since there's currently no way to use the device with the bootloader unlocked, a lot of the features used in TWRP are unusable. It might still be good to install TWRP in case someone finds a way to modify the device to better utilize TWRP.​​To install Magisk, it will be much easier to do it by flashing new firmware. However, it is also possible to install Magisk without flashing new firmware. I will include the steps to do this below these.​Steps:​
Download and install the Qualcomm drivers from here
Download and install QPST from here
Download the firmware from this thread (Credit to @deadman96385). I used the 200628.084 version for reference.
Extract the firmware to a folder that you can easily access, like on your desktop.
If you want to install TWRP, download the recovery.img file attached to this post. (Credit to @Xi07)
Open the folder that you extracted the firmware to. In the image folder, replace the recovery.img file with the one you downloaded.
If you want to install Magisk, download the boot.img file attached to this post.
Open the folder that you extracted the firmware to. In the image folder replace the boot.img file with the one you downloaded.
Download the firehose/rawprogram file from @deadman96385's post and flash the package using the instructions provided by @deadman96385. I've included them here for your convenience:
Spoiler: Expand Here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8953_ddr.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram_unsparse.xml and then the patch0.xml when prompted.
Remove the cover on the USB-C port on the bottom right of your device
Plug the USB-C cable into your computer
Unplug the power from the device
Hold vol+ and Vol- and then plug the power into your device (Smart Plugs can make this easier)
If the text at the top of the QFIL application mentions qdloader move on to next step. If it says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you most likely didn't install the drivers properly.
Click the Download Button to begin flashing your device
Once complete it should automatically reboot but sometimes it doesn't so you need to replug your device.
If you get the dreaded "Sahara" error when flashing your device, you may be waiting too long to flash. The device must be flashed moments after it is booted into EDL mode (powering on with Vol + and Vol - held down). Once you plug in your device, hit download the moment the port is recognized at the top of QFIL.
You can also try disabling driver signing (I'm not sure if this makes a difference). To do so:
Spoiler: Expand Here
Open a command prompt as an Administrator.
Run
Code:
bcdedit /set testsigning on
and restart your device
Your computer should say it's in Test Mode (bottom right corner). To disable driver signing, follow the same steps but run
Code:
bcdedit /set testsigning off
instead.
Thanks to HowToGeek's article for the information.
From here, you can go ahead and follow the original method from @deadman96385 for breaking into the device.
Spoiler: Expand Here
When it boots up select Teams (Others seems to try and network boot/download files and fails)
Go through the setup wizard until you get to the Microsoft Teams (Language > Wifi > Bluetooth > Teams)
Select the Gear Icon in the top right of the teams page
Select the "About" settings option
Tap on "CD-18781Y.200628.084" under firmware version a bunch of times rapidly until a prompt comes up saying developer unlocked.
If your usb c cable is plugged, in unplug and replug it in.
You will now have ADB access.
Download your desired Launcher and use the following command to install it:
Code:
adb install APK_FILE_NAME.apk
You will then need to send this adb command to select a new default launcher:
Code:
adb shell am start -a android.intent.action.MAIN -c android.intent.category.HOME
I would recommend getting a navigation bar app. I've attached the one I used to this post.
You can also technically install Magisk without reflashing your device.
Spoiler: Expand Here
Install the Magisk app (use the Magisk APK)
Enable OEM unlocking in Developer Settings
Unplug the device. Hold Vol- and plug in the device to boot into fastboot mode.
In command prompt, execute
Code:
fastboot devices
to make sure the device is discovered. If a device is not listed, you may need to go into Device Manager > Other Devices > Android device with question mark. Right click > Update Drivers > Browse My Local Drivers > Let me pick from a list > Change to Fastboot Drivers.
Code:
fastboot oem unlock-go
This will unlock your bootloader.
Unplug the device. Hold Vol- and plug in the device to boot into fastboot mode.
In command prompt, navgiate to the directory where your Magisk boot.img is downloaded. Run
Code:
fastboot flash boot boot.img
After the boot.img is flashed, you need to lock your bootloader to be able to boot back into the device. If you're not in fastboot mode, you can once again unplug the device. Hold Vol- and plug in the device to boot into fastboot mode.
Run either of the 2 commands to lock the bootloader. You can restart the device and boot into the device once you are finished.
Code:
fastboot oem lockfastboot flashing lock
Steps for Google Play Store and Custom Webview will be in the next post (to reduce clutter).

Installing MicroG and the Newest Version of the Google Play Store (Magisk Required)​
Download and install the MicroG Services Core and Services Framework Proxy from the MicroG site.
Install the Magisk app (use the Magisk APK). When you open the app, it should say the version of Magisk installed next to "Installed."
On your Android Device go to Settings > Connected Devices > USB > File Transferring Mode.
Download the NanoDroid-patcher.zip file, BusyBox.zip, and terminal_systemizer.zip. Do not unzip these files. Drag and drop these devices onto your Android device.
In Magisk > Modules > Install from storage, find the .zip files and install all 3 Modules. The NanoDroid-patcher module in particular may take awhile so be patient.
Install the apk of Google Play Store of your choice.
Install Termux. In Termux, issue the command
Code:
su
A superuser popup should show up. Make sure to allow Termux Superuser access. If you miss clicking on it, you can allow access in the Magisk App > Superuser.
Code:
systemize
Follow the dialog prompts to systemize Google Play Store to /system/priv-app
Restart the device.
Open the microG settings app. Register the device in Google device registration. In Self-Check, click on each setting (the words, not the checkboxes) and enable them all. Pay particular attention to System spoofs signature being checked off.
Restart the device again if you want. Google Play Store should be working fine now (may need to clear it's App Data first if it's not working).
Installing Custom Webview (Magisk Required)​Some apps such as HomeAssistant won't function without an up to date System Webview. As this tablet is running a quite old version Webview version, this causes these apps to not work. Luckily, there's a Magisk Module to fix that.
Download the Webview_Manager zip file and drag and drop it onto your device. Install it using Magisk. You will need to watch it install as it requires some input on which Webviews you want to install.
After restarting the device, navigate into Settings > System > Developer options > Webview implementation. You should now be able to change your Webview to a updated version.
Note, you may need to unplug and replug in the device after the first restart of installing Webview.

Reserved 2

Chewie610 said:
Download the firehose/rawprogram file from @deadman96385's post and flash the package using the instructions provided by @deadman96385. I've included them here for your convenience:
Spoiler: Expand Here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8953_ddr.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram_unsparse.xml and then the patch0.xml when prompted.
Remove the cover on the USB-C port on the bottom right of your device
Plug the USB-C cable into your computer
Unplug the power from the device
Hold vol+ and Vol- and then plug the power into your device (Smart Plugs can make this easier)
If the text at the top of the QFIL application mentions qdloader move on to next step. If it says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you most likely didn't install the drivers properly.
Click the Download Button to begin flashing your device
Once complete it should automatically reboot but sometimes it doesn't so you need to replug your device.
Click to expand...
Click to collapse
A slightly easier way that may work I haven't validated on the thinksmart specifically is using qfil's partition manager tool. It allows you to dump, erase, flash individual partitions, that way you can flash just the one you want without having to deal with a full qfil flash. Finish all original steps up to 10. Instead of clicking download do the following instead:
Navigate to the top menu: Tools -> Partition Manager -> OK. If all goes well, you will be greeted with a dialog listing all partitions in ~5s. If this is not the case even after a full minute, try re-entering EDL/9008 mode.
Once the partition list is loaded, you can perform the following actions on partitions by right clicking a partition and then clicking 'Manage Partition Data'.
'Erase' (Clear the partition)
'Read Data...' (Dump the partition)
'Load Image...' (Flash the partition)
Click to expand...
Click to collapse
This is also a great way of backing up partitions from your device. The dumped partition can be found in C:\Users\%USERNAME%\AppData\Roaming\Qualcomm\QFIL\COMPORT_##. Note that the name of the file is the raw file locations so you will need to rename the imgs as you go.