Related
Special thanks to @funkyboy1281, @lentm, @macboy3000 for helping getting this work. As far as I can tell, this is the easiest and most straight forward instruction set for getting Android Pay to work on the latest version of Pure Nexus, Chroma, or OMNI Rom
Clean Flashing
Download the appropriate Rom.
Pure Nexus DiscussionChroma DiscussionOMNI (no link available, sorry)
Download Pure Nexus Dynamic Gapps 2-3-16 (Very important, you cannot use 15-3-16 or later). Yes, even if you use Chroma or OMNI, these Gapps should work for you. Link
Download the unSU script for completely unrooting before installing systemless root. Link
Download SuperSU 2.68 (or higher) Link || Discussion
Advance wipe in recovery all but internal storage
Install the ROM, gapps, and unSU
Optional: Install custom kernel
In TWRP, under advanced, go to terminal and type the following:
Code:
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Note: You may also do this using ADB in recovery (adb shell, and then enter the same commands. This is much easier in my opinion, and is the method I used.
Flash 2.68 beta in TWRP
Fully reboot, go through initial device setup
Verify in SuperSU that you cannot install SU to the system. This will verify that we are using the systemless root option
Download SafetyNet Helper and make sure it passes
Install Android Pay and profit!
Dirty Flashing
Verify that SafetyNet still passes in Android.
Verify in Android that /data/.supersu is still present and contains the appropriate options (see clean flashing). You may also verify in recovery by going to terminal commands and entering in:
Code:
cat /data/.supersu
Install the updated ROM (do not reinstall gapps unless your ROM builder specifically tells you to do so. Pure nexus does not require a reflash)
Optional: Install unSU. This was not necessary on PureNexus, but I cannot be sure for other roms. It shouldn't hurt anything to flash.
Optional: Install custom kernel
Install SuperSu 2.68 (or higher)
Check SafetyNet Helper and make sure it still passes
FAQ
Q. Can I still install and use AdAway?
A. Yes. You must first install something in recovery before installing AdAway. See the discussion Thread. You should be installing v3.1 of the app after you install the recovery zip.
Q. Can I still use V4A?
A. Yes. I do not use this however, but it has been reported that nothing special needs to be done.
Q. Can I change the screen density?
A. We have not found a way to do this without tripping Safety Net
..
@skaforey thanks for this thread! Might want to note in the OP that Wiping Data erases the internal storage. Some people may not know that.
MrBrady said:
@skaforey thanks for this thread! Might want to note in the OP that Wiping Data erases the internal storage. Some people may not know that.
Click to expand...
Click to collapse
Noted, thank you! Still hoping some of the lucky folks that have it working can help us out here.
Has anyone found a way to adjust the screen density while keeping Android Pay functional?
MrBrady said:
Has anyone found a way to adjust the screen density while keeping Android Pay functional?
Click to expand...
Click to collapse
You (should) be able to change the density through adb using
Code:
adb shell wm density DPI
with dpi being what you want, or if you have root you can do that from a terminal emulator, just remove the adb shell part.
I tried the 2nd method without formating data in different combos to no avail, still hesitant to wipe my internal sdcard, it shouldn't be that hard man, will follow this thread
anyone know other aosp ROMs that have AP working outside of pure nexus?
Sent from my Nexus 6 using Tapatalk
Following the steps in the top most instructions in the OP...
1) Pure Nexus 3/8 does not have root out of the box, so the Unroot step was not needed.
2) TWRP did not show any files/folders in the /su directory, so the Terminal command didn't work. I booted up the device and did it through the Terminal there instead and then rebooted.
After that, loaded up Android Pay and it says "Android Pay can't be used".
Running SafetyNet reports....
SafteyNet request: success
Response validation: success
CTS profile match: false
Tried different methods, not working for me.
1. Download Pure Nexus 1/03/16 or newer (Layers), the latest PN GApps, UnSU, the latest SuperSU.
2. Backup any important data.
3. Boot into TWRP and wipe everything including internal storage
4. Format data.
5. reboot TWRP with USB-OTG that has fines necessary.
6. Flash Pure Nexus.
7. Flash GApps.
8. Flash UnSU.
9. In terminal I saw I still had a folder /supersu so I deleted that.
reboot. Setup phone with google account. Did not have it restore apps, but did have it restore basic setup from google.
Install Safetynet helper
Still fail CTS Profile Match
Don't know what the people are doing different, but not working for me.
Are you using the PN-Gapps or others?
The updated-unsu is what date?
Thanks!
The only way I have gotten AP to work is from a stock image based ROM. It doesn't seem to work with AOSP ROMs like Pure Nexus.
For example, I am currently running Tupac's debloated stock ROM with Cataclysm MOD, Viper4Android and AdAway ad blocking. Android Pay works fine, as long as you follow the SU steps listed in the OP of this thread.
What I did to get AP to work was removing these lines from updater-script located in META-INF > com > google > android
Code:
ui_print("Flashing SuperSU..");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");
ui_print(" ");
and removed the supersu folder inside the zip file. I then installed my custom kernel and systemless supersu. After that, I set the permissions for bin folder inside su to 751 using a root explorer and deleted xbin_bind.
@macboy3000 what kernel and what version of SuperSU did you use, ? I tried your method, ROM booted fine but safetynet test failed...
this is how I did it
unzip ROM
edit code out
delete supersu folder
zip ROM
advance wipe everything but internal
flash ROM
flash pn gapps
flash elemental kernel
flash supersu
boot into android, delete xbin_bind
reboot system
permissions on bin folder were already 751, so didn't need to change
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
@macboy3000 what kernel and what version of SuperSU did you use, ? I tried your method, ROM booted fine but safetynet test failed...
this is how I did it
unzip ROM
edit code out
delete supersu folder
zip ROM
advance wipe everything but internal
flash ROM
flash pn gapps
flash elemental kernel
flash supersu
boot into android, delete xbin_bind
reboot system
permissions on bin folder were already 751, so didn't need to change
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Weird...I'm using SuperSU 2.67 and I'm also using Elemental kernel.
macboy3000 said:
Weird...I'm using SuperSU 2.67 and I'm also using Elemental kernel.
Click to expand...
Click to collapse
Did you format data? I'll give it a shot with 2.67, I used 2.68
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
Did you format data? I'll give it a shot with 2.67, I used 2.68
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I formatted everything except internal storage before installing.
macboy3000 said:
What I did to get AP to work was removing these lines from updater-script located in META-INF > com > google > android
Code:
ui_print("Flashing SuperSU..");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");
ui_print(" ");
and removed the supersu folder inside the zip file. I then installed my custom kernel and systemless supersu. After that, I set the permissions for bin folder inside su to 751 using a root explorer and deleted xbin_bind.
Click to expand...
Click to collapse
Well I tried this and still no luck
I even tried flashing the modified ROM, gapps, and never flashing SuperSU at all (so my rom wasn't rooted at all), and SafetyNet still gives me a red screen. I really wish I knew what was triggering this for some and how others can make it work.
I tried again using 2.57 SuperSU and Elemental X and still fails. Would someone that got it working be able to post a more detailed log of exactly what steps you're using and exactly what files you're flashing.
MrBrady said:
The only way I have gotten AP to work is from a stock image based ROM. It doesn't seem to work with AOSP ROMs like Pure Nexus.
For example, I am currently running Tupac's debloated stock ROM with Cataclysm MOD, Viper4Android and AdAway ad blocking. Android Pay works fine, as long as you follow the SU steps listed in the OP of this thread.
Click to expand...
Click to collapse
This has been my experience as well !
jcrompton said:
This has been my experience as well !
Click to expand...
Click to collapse
Got Android Pay working with Tupac's debloated stock ROM too! Thanks!
Is it possible to change DPI and keep Android Pay working?
lentm said:
Got Android Pay working with Tupac's debloated stock ROM too! Thanks!
Is it possible to change DPI and keep Android Pay working?
Click to expand...
Click to collapse
Not that I have found, unfortunately. Even via just ADB commands.
Installing Lineage
Few quick things.
LOS 18.1 is now official so the guide will now just be covering that.
I also want to address a common question, you can use Windows for this process. I prefer Linux, and Fastboot just works in Linux without driver issues. If you have Fastboot and ADB working in Windows already feel free to use that if you want.
Frequently asked Questions:
This looks like a lot of work, is there an easier way to install? Try the LOS Wiki Method.
Using TWRP 3.5.2_9-01. Start off Fresh. Install OOS using the Fastboot ROM.
Start off with a fresh install of OOS. You need the latest version of OOS 10. I typically use a the fastboot ROMs for this as it will do both slots for me at once. (Alternatively you can use TWRP and install the ZIPs and do it twice to get it on both slots, or my least favorite, the MSM Tool if you want. Doesn't matter how OOS ends up on both slots, as long as it ends up on both slots.)
I use Linux, and honestly I feel like it's easier and more reliable for fastboot and ADB so that's what I'm including here in these steps. It's easy to boot from a USB.
To create a bootable Linux flash drive you can use Unetbootin, which you can download for free here (Your other option would be to burn the ISO straight to a DVD and skip the unetbootin step):
https://unetbootin.github.io/
For Linux, I'm using Linux Mint Cinnamon, You can download for free here:
https://www.linuxmint.com/download.php
Then run unetbootin (yours will look a little different, I'm running it in Linux):
{
"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"
}
Point it to the Linux ISO, and tell it where an empty flash drive is. It will erase everything on the flash drive. Afterwards you can load whatever you want on the flash drive. However be aware when booting Linux from this drive you can't access what is on the drive (at least not by normal methods).
After this has successfully completed, reboot the PC, and boot from the USB drive. Your PC will boot into Linux (turning off the PC and removing the USB drive will make it boot up like normal again).
Next we need to install fastboot and adb. You need to open up the "start menu" and open the "synaptic package manager". You can find this stuff in the menus, however the easiest way to get to these items is to just start typing the name of the item. See below:
Search fastboot, click the boxes, choose install. Then search for ADB, click the boxes, choose install and then click apply. It's that easy it will download everything that's needed and install.
Time to open up a terminal:
Just to make sure we don't run into any problems we need to update adb and fastboot. In the terminal run these commands to update fastboot and adb (this is downloading them directly from Google).
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
sudo cp platform-tools/adb /usr/bin/adb
sudo cp platform-tools/fastboot /usr/bin/fastboot
You will also need the appropriate fastboot ROM. Fastboot ROMs available in this thread. The catch being that thread is no longer updated. So we will need to make our own fastboot rom. To do this we need two things:
1. The stock rom zip (OP Site).
2. Payload dumper. I've yet to get the one from the GitHub link to work, so I've been using the one from this Article. Direct Download Link
You need to extract the payload.bin file from the stock rom zip. Extract the payload_dumper files as well, and place everything in the same folder. Payload_dumper requires python3. Open up Synaptic again, search for python3.6 and install it. Now open a terminal so we can extract the images from the payload.bin.
Navigate to the location of payload_dumper and your payload.bin file. In my case my commands are:
cd Desktop <-- switches to the Desktop folder
cd payload_dumper <-- switches to the payload_dumper folder on the Desktop
python3 payload_dumper.py payload.bin <-- runs the payload_dumper "program" and extract the images from the payload.bin
Now would be a good time to back everything up. The phone will get wiped. Extract the fastboot images to a folder that is easy to find. I would recommend the Desktop.
Now it's time to flash all those images we just extracted using payload dumper. Place the phone in fastboot mode. You can do this using the advanced reboot menu, ADB, or the key combinations (all key combos listed below for reference):
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
You can flash the images one by one or use a script. My script is available here. Flashing the fastboot ROM should look something like this:
That image explained:
cd Desktop <-- Switched the directory to the Desktop the default directory when you open up the terminal is the /home directory.
cd flash <-- I put my fastboot images in a folder called flash. This stuff is case sensitive. My folder was all lowercase.
sudo fastboot devices <-- Is just checking to see if my PC can see my phone, and making sure it's in fastboot. Sudo is necessary for this distro, as both fastboot and ADB must be run as root.
sudo sh FlashThese.sh <-- Tells the terminal to run my script, since the script contains fastboot commands it must be run as root.
At the end you should get something like this:
Then just choose start form Fastboot (If you were previously on a custom ROM go straight to recovery and wipe everything). Not booting and getting dumped off at the OnePlus recovery screen is nothing to worry about. Choose your language of choice, Wipe data and cache, Erase everything (Music, pics, etc), This can not be undone, continue. After that the phone will boot. Once booted enable developer options, advanced reboot, and reboot to fastboot.
2. Installing TWRP.
First step is to boot the correct TWRP image. Grab the current TWRP from the official site. You need both files, the img file, and the installer. Once again from the terminal:
The image explained:
cd Desktop <-- Switched the directory to the Desktop the default directory when you open up the terminal is the /home directory.
sudo fastboot devices <-- Is just checking to see if my PC can see my phone, and making sure it's in fastboot. Sudo is necessary for this distro, as both fastboot and ADB must be run as root.
sudo fastboot boot twrp-3.5.2_9-0-fajita.img * <-- Sends that TWRP image to the phone to be booted temporarily. Only boot this, never run the command "flash".
Once in TWRP the phone should show up as a media device so you can copy files to it. Copy the TWRP installer over to it. Choose Install from the TWRP menu and navigate to where you placed the TWRP installer. Press on it, and swipe to confirm flash. When it is done hit the back button until you are back out to the main menu.
From the main menu choose reboot, and choose Recovery:
The first time you try and reboot the official version of TWRP it will ask you if you want to install the TWRP app. Do NOT install the app. In the settings you can disable this prompt. Your other option is just uncheck both boxes at the screen you see below when you get to it, and then click the button that says do not install. Do use the slider. At that point the phone will reboot as to recovery as you selected.
Now that you are back in TWRP that is now installed, time to wipe the phone. From the main menu choose Wipe. Swipe the factory reset slider at the bottom. Then hit back. Next hit Format Data. Type Yes to Continue. Hit back to continue. Keep hitting back till you get to the main menu.
Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. So go back into the reboot menu, choose reboot to recovery again (swipe to allow modifications if it asks). You must do this after formatting data.
3. Install Lineage
Links:
Lineage 18.1 XDA Thread
Official 6T Lineage Downloads
The phone should still be in TWRP at this point. You now need to copy Lineage to the phone. From TWRP's main menu choose install. Then navigate to your ROM .zip location and click on it. Then swipe to confirm flash.
Lineage will replace TWRP, so you need to reflash TWRP as well. Run the TWRP installer again. If it's not on the phone, just copy it over again real quick. On A/B devices ROMs get flashed to the opposite slot. Things like Gapps, Magisk, etc get flashed to the current slot. We need Lineage on both slots, so it must be flash again. Flashing it twice only needs to be done the first time as we need to get rid of OOS. For updates it just gets flashed once. After the TWRP installer has run, back out to the main menu, and choose reboot, then recovery:
Once back in TWRP flash Lineage again. From TWRP's main menu choose install. Then navigate to your ROM .zip location and click on it. Then swipe to confirm flash.
Now run the TWRP installer again. Back out to the main menu, and reboot to recovery.
4.Optional, Gapps
Links:
NikGapps <-- For Lineage 18.1 (Use the R Folders for Android 11. I recommend the "Core" version. I also tested Basic though if you want that level of Gapps. I strongly recommend you grab setup wizard out of the R Addons Folder, I used the regular setup wizard, not the pixel one.)
MindTheGapps <-- It's worth mentioning here Lineage recommends MindTheGapps for 18.1. Take your pick. I personally use NikGapps as I can use a "leaner" Gapps package.
Now that your phone is back in TWRP for the last time before booting up Lineage, it's time to install Gapps if you want them. This step is optional. Same as the other steps here, go to install, choose your OpenGapps package, Then navigate to your .zip location and click on it. Then swipe to confirm flash.
5. Very Optional, Magisk
These steps are very optional. However this is how I, root, pass safety net, and get a various apps to appear in the Play store.
Flash Magisk in TWRP. For Magisk 23, you now have to rename the Magisk.apk to Magisk.zip. Then flash it in TWRP. If you wanted to uninstall it, you rename it to uninstall.zip. If you already had an older version of Magisk installed, make sure you do not have it hidden / nenamed when installing Magisk 23 for the first time. Restore the original package before installing 23.
Magisk <-- Flash this right after Gapps.
These items are add-ons are flashed in Magisk after the first boot (Don't flash these in TWRP anymore):
MagiskHide Props Config
Busybox
To flash modules in Magisk press the puzzle piece icon. Then choose install from storage. Now just choose your addons. After flashing the icons it will have a reboot icon at the bottom. You can reboot or you can press back and flash another. After you are done reboot.
You will also need a Terminal Emulator. I personally use:
Terminal Emulator for Android
Once all these are installed the first step is setup Magisk. Under Magisk go to settings:
In version 20.4+ Magisk Hide is no longer on by default. So make sure the Magisk Hide, Hide Magisk from various forms of detection switch is flipped. Then press Hide Magisk Manager. This will bring up a box for you to choose a random name for the Magisk Manager, type whatever you want here. You can leave it Manager if you wish, but I typically change this.
Now open Magisk again. It will ask you to download it again, click ok, then manually open the app again as it says. Now we need to open Magisk hide. This is now under the shield icon, then click the arrow at the top:
These are the apps you don't want to know that you have root. Less is better. You can cause instability problems by just choosing everything. My general rule of thumb is, Google, steaming video, music, and payment apps get selected. In my experience if I come across an app that needs it and I didn't select it, I just clear cache and/or data and re-open the app and it works. There are some big multiplayer apps that ban hardware / people, so do your research (don't ask me, I don't play those games).
Next time to change the device fingerprint using MagiskHide Props Config Module. We do this using the terminal emulator. In the terminal emulator, type "su" to gain root privileges. Then type props to run the module:
Now it's just following the menus. Choose option 1 - Edit device finger print. (type 1, hit enter)
After this you will see a menu of devices. It doesn't matter what device you pick really. If you want apps / Google to think you have a OPPO or Samsung pick one of those Fingerprints. However there's a bit more to passing Safety-net than that. Since Google has changed how things work not all those fingerprints that used to work will work now. Also now you may get an error when you turn on the phone because of the security dates. The OP6T Android 10 fingerprint has no issues at this point, so use that if you want:
After choosing the fingerprint you want, it will ask you if you want to reboot. Choose yes. After rebooting, you may need to clear the cache from the play store for some apps to appear in it. You should now pass safety net. Check this in Magisk:
6. Very Optional, Ad Blocking with a Host File.
You can block many things with a hosts file, most popular would be ads. I've been use StevenBlack's host file which is a compilation of several hosts files. This is located on Github:
https://github.com/StevenBlack/hosts (Scroll down you'll see the options of what you can block)
Direct link to the hosts file I use. This will block Adware / Malware.
Unfortunately for quite some time now on this device you can no longer just use a root browser to swap the hosts file. The easiest way is to use TWRP.
First we have to make the hosts file. The hosts file must use unix / linux line endings. If you are using linux, don't worry about this, just create the file. If you are using Windows, the easiest thing to do is use Notepad++ (Free).
Notepad++ Downloads
Next one other caveat. The hosts file is quite large. I've never had much luck copy and pasting it from any other browser than Firefox (Windows or Linux), but however you get it into Notepad++ is not a big deal.
Once in you have the hosts file into Notepad++ go to Edit, EOL Conversion, and Choose Unix (LF).
Now save the file as "hosts" no ending. This does mean under file type you will need to change it to All File types *.*. Move this hosts file to your phone. Then reboot to recovery. From the main TWRP menu, choose mount. Then mount system:
Hit the back button and go to the advanced menu. Choose File Manager:
You will find your hosts file under /sdcard, wherever you placed it. In my case I placed it in a folder called ROMs. Once you locate it, press and hold it for a moment, and relase. Then choose copy file:
At this point you need to tell TWRP where you want to paste the hosts file. It belongs in the /etc folder. The only hic-cup here is depending on what you were doing in TWRP this could be (on this device) /system/etc or /system/system/etc (you will see similar folders to the image below if you are in the right place). Once you are there, press "paste?" button in the lower right corner:
After this just swipe to confirm:
You can now reboot the device, and your hosts file should now be in place. Your ad block should now be active for all apps as it's global for all connections.
7. Reboot to system.
Updating Lineage
1. Flash Lineage.
Reboot to recovery. You can use the advanced reboot menu, or Volume Down + Power while turning the phone on. Don't wipe anything. From TWRP's main menu choose install. Then navigate to your ROM .zip location and click on it. Then swipe to confirm flash.
Lineage will replace TWRP, so you need to reflash TWRP as well. Run the TWRP installer again. After the TWRP installer has run, back out to the main menu, and choose reboot, then recovery:
2. Optional, Gapps (if you installed them once you must continue to install them or do a clean install)
Links:
NikGapps
Now that your phone is back in TWRP for the last time before booting up Lineage, it's time to install Gapps if you want them. This step is optional. Same as the other steps here, go to install, choose your OpenGapps package, Then navigate to your .zip location and click on it. Then swipe to confirm flash.
3. Reboot to system.
Last updatedSince I don't want people to have to wonder if these instructions are current, I am going to periodically test and update this post with my results. Please note I'm testing with a 6T, TMobile 6Ts are different. You can generally assume previous versions of LOS and OOS were also tested, but if you are unsure feel free to ask in this thread.
Last tested with:
OOS 10.3.7 and LOS 17.1 12-31 with TWRP 3.4.0-2
OOS 10.3.11 and LOS 18.1 05-27 with TWRP 3.5.2_9-0
This method has also been tested with:
OOS 10.3.3 and Omnirom 5-24 MicroG and Omnirom 5-24.
Cliff Notes
*TWRP 3.5.0_9-0+ Must be used with LOS 18 / 18.1
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery (This step wipes the device, make sure you backed everything up!)
- Factory Reset. (This is the slider at the bottom, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else)
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Flash Gapps (Optional)
- Flash Magisk (Optional) (Remember for ver 22 the Magisk.apk gets renamed to Magisk.zip, can also be renamed to uninstall.zip for uninstalling)
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
After this you should be able to update Lineage as normal.
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Optional, but if you flashed them once you have to keep flashing them.)
- Flash Magisk. (Optional)
- Reboot to system.
- No loss of data, or anything.
Thanks for the guide, able to flash los 17.1 successfully.
How to go back to OOS?
Does anyone have a guide on how to go back to OOS after flashing Lineage according to Lineage's instructions?
fordjonathan said:
Does anyone have a guide on how to go back to OOS after flashing Lineage according to Lineage's instructions?
Click to expand...
Click to collapse
Back up your data, use Step 1 of these instructions. That will put OOS back on your phone.
MSM Tool, always my least favorite option, but always an option.
MSM Tools for Regular 6T (TMobile uses a different one)
installed 17.1!
OhioYJ said:
Installing Lineage...
Click to expand...
Click to collapse
Massive thanks for your instructions!
- at first, I tried upgrading from LOS 16.0 to LOS 17.1. I followed the instructions on the wiki, but it landed me in the qualcomm crashdump mode.
- after that I ran into your instructions, and tried to follow your update guide, but it didn't help (not very surprising I guess, but I haven't had much to lose at this point ).
- after that, I just followed your fresh install guide (i.e. flashing the fastboot room and starting from scratch), followed every step and it worked!
I wonder if it's worth updating lineage OS wiki and pointing to your instructions? There is bunch of people in this thread, who also bricked the phone into crashdump, so perhaps it could help to prevent it for someone else.
Updating to LOS 17.1 ?
Dasseem said:
Thanks for the guide, able to flash los 17.1 successfully.
Click to expand...
Click to collapse
Initially I had problems with updating LOS, so I returned to Stock. As more people attempted to install LOS, and this fine Original Poster "Ohio" offered such excellent, and detailed instructions, I have been running LOS 16 since February.
However, I have not updated it, since I have had Zero Issues.
But to clarify, you used this method to update to LOS 17.1 ?
- coming from LOS 16 - without first returning to a fast-boot ROM ?
Did you up-date GApps accordingly during this Flash ?
Thank You, in advance, for any assistance!
:good:
barguybrady said:
But to clarify, you used this method to update to LOS 17.1 ?
- coming from LOS 16 - without first returning to a fast-boot ROM ?
Click to expand...
Click to collapse
Hi, I updated my previous reply to make it a bit more clear!
Yep, I was on LOS 16. Haven't had any issues, but figured why not update if I'll have to do it eventually
So I downloaded 17.1 and used the wiki instructions, which messed the phone up
Ended up flashing fastboot rom and starting from scratch, flashed gapps and magisk according to OhioYJ's instruction and it worked.
Flashing method
barguybrady said:
But to clarify, you used this method to update to LOS 17.1 ?
- coming from LOS 16 - without first returning to a fast-boot ROM ?
Did you up-date GApps accordingly during this Flash ?
Thank You, in advance, for any assistance!
:good:
Click to expand...
Click to collapse
I was using carbon ROM previously, had to move to OOS latest for flashing the lineage 17.1, believe it needs to be done if you are coming from pie, people know better correct me if I am wrong here.
As Karlicoss mentioned, it's better to follow the method posted by Ohio.
OhioYJ said:
Cliff Notes Versions
Installing Lineage
- Install fastboot ROM boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk if you use Magisk. Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone may restart once, then Lineage will start up and all will be good.
Updating Lineage
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (Optional If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
Click to expand...
Click to collapse
Updating failed for me, as it shows everything encripted once I reboot the second time to recovery on slot B...
badpanda said:
Updating failed for me, as it shows everything encripted once I reboot the second time to recovery on slot B...
Click to expand...
Click to collapse
Usually this means you didnt format data, or you are using an old version of TWRP. Did you do a clean install?
I just tried it on my phone, was running 4-12 build, using 3.3.1-32 TWRP, updated to the 4-14 build, using 4-14 Gapps (nano), everything went smoothly here.
OhioYJ said:
Usually this means you didnt format data, or you are using an old version of TWRP. Did you do a clean install?
I just tried it on my phone, was running 4-12 build, using 3.3.1-32 TWRP, updated to the 4-14 build, using 4-14 Gapps (nano), everything went smoothly here.
Click to expand...
Click to collapse
No, no clean install. Just wanted to update to today's newest build os.
bump...
Thanks a lot for your guide. Very helpfull.
I'm using it with /e/ rom.
installing android 10 roms
I followed exactly as it was written. Same issues arose for me. After the phone is off then turned on no LTE. It makes phone calls and also text stuff. HOWEVER when you take out and reinsert sim LTE is enable. What is the problom?????????
sickpoppy said:
I followed exactly as it was written. Same issues arose for me. After the phone is off then turned on no LTE. It makes phone calls and also text stuff. HOWEVER when you take out and reinsert sim LTE is enable. What is the problom?????????
Click to expand...
Click to collapse
Just cycling airplane mode doesnt work? This isn't a TMobile 6T is it? You are in Sim slot 1? You maybe better asking in the LOS thread, and provide log it not working and then it working when you reinsert it. Im not quite sure whats going on there.
OhioYJ said:
Usually this means you didnt format data, or you are using an old version of TWRP. Did you do a clean install?
I just tried it on my phone, was running 4-12 build, using 3.3.1-32 TWRP, updated to the 4-14 build, using 4-14 Gapps (nano), everything went smoothly here.
Click to expand...
Click to collapse
So this means you do have to always format data for every single update??
---------- Post added at 09:07 PM ---------- Previous post was at 09:05 PM ----------
sickpoppy said:
I followed exactly as it was written. Same issues arose for me. After the phone is off then turned on no LTE. It makes phone calls and also text stuff. HOWEVER when you take out and reinsert sim LTE is enable. What is the problom?????????
Click to expand...
Click to collapse
Change your sim card to the other slot...
---------- Post added at 09:11 PM ---------- Previous post was at 09:07 PM ----------
@OhioYJ So for an update you boot to recovery flash LOS latest version then flash twrp again and then reboot to recovery second time then format data to possibly decript encrypted system and, transfer files both gapps and magisk to device and then install gapps and magisk, lastly just reboot to system?
reply
yes it is a tmobile but it was flashed to global. TWRP is the version you are using. downloaded the lastest ROM. Weird it finds LTE at first then like I said when then phone shuts off LTE doesnt work til I take sim out.
badpanda said:
So this means you do have to always format data for every single update??
Click to expand...
Click to collapse
No that would be ridiculous. Not necessary at all. You have something else going on, but I dont know what. My update procedure is exactly as listed on the OP, on two 6Ts, two different carriers.
sickpoppy said:
yes it is a tmobile but it was flashed to global. TWRP is the version you are using. downloaded the lastest ROM. Weird it finds LTE at first then like I said when then phone shuts off LTE doesnt work til I take sim out.
Click to expand...
Click to collapse
A TMobile "converted" to global does not equal a global 6T. Logs posted in the LOS thread, may help out other TMobile users? The TMobile 6Ts introduce all sorts of quirks, and Im afraid I dont have any experience with them, so hopefully another TMobile user will be able to help.
None of this is my work, just the steps to get it to run for me.
The steps are fairly step by step and some seem redundant, but they work. I had lots of failures.
Start with TWRP and Magisk Installed
Note: This will process will complete erase device, so make sure google backup is up to date and using titanium (or something else) for any other backups.
Download the following files and copy to sdcard
Device ID
Device ID.apk | by xda-developers.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Nikgapps
https://sourceforge.net/projects/nikgapps/files/Config-Releases/NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip/download
Force Decrypt
Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip | by Droidwin for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
TrebleGSI Image (Make sure to extract image from xz file)
https://sourceforge.net/projects/treblerom/files/crDRom11/2021.05.21/crdrom-v308-210521-arm64-bvZ-lite.img.xz/download
Latest Magisk APK (Make sure to change extension to .zip)
Reboot to recovery
Goto Wipe
Format Data
Advanced wipe - Select System and wipe
Install cdrom-c306-210428-arm64-bvz.img to system
Reboot recovery
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Reboot system
Press and hold power button when Eye icon shows up. Select restart - Recovery
Goto Wipe
Format Data
Reboot recovery
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip
Reboot system
Click start
Skip Mobile network
Select and login to wifi
On Copy apps & data click next
Select a backup from cloud
Enter PIN
When you get "This device isn't Play Protect certified" select "Got It"
Click More and accept through google services
Select Face unlock + PIN
Enter PIN twice
Setup Face lock
Click Done
Click Next
Click Skip
Click Start
Ignore Play Protect errors
Setup sdcard as portable storage
Install Device+ID.apk from sdcard
Open Device ID and accept permissions
On PC goto https://www.google.com/android/uncertified/ and enter GSF.
Wait 2 minutes - PLEASE!!!
Reboot
Goto Settings - Accounts
Add your google account.
Either restore from account setting or wait to be prompted to finish setup. This will restore apps, contacts, etc.
When Setup complete run Magisk and complete its setup.
In Magisk, enable MagiskHide and Hide Google Play Store
Run safetycheck. It should fail.
Load module MagiskHide Props Config
Reboot
From terminal window (I use TermUX),
Run:
su
props
Select 1
Enter fingerprint value: Lenovo/LenovoTB-X606F/X606F:10/QP1A.190711.020/TB-X606F_USR_S300177_2103041623_V9.56_BMP_ROW:user/release-keys
b to go back
4 for custom props
n for new custom prop
Property: ro.build.version.security_patch
Value: 2021-02-05
e to exit
Reboot
Go to magik and rerun safetycheck. It should pass and restricted apps now available in store (Disney, Netfilx, etc.)
Update apps in Play Store
Setup tablet to your preferences
Good Luck.
Oddities:
Tablet is unencrypted. You can reencrypt, but TWRP will not be able access data partion.
Must re-register GSF everytime you wipe data.
SafteyCheck fails ctsProfile. - Thread updated with info to fix
More to come as I explore the ROM
Tired it myself and works great. It can be also used with other project treble roms but some features might be broken for example face unlock. I would also add that sometimes the message "This device isn't...." might still appear in Google play, because of that you have to clear cache for this app.
Thanks for writing this up @snickle ! I followed your instructions, DRM Info shows Widevine L1, and disney+ and discovery+ install, but they won't play. "something went wrong", etc.
I just installed the latest android 11 phh-aosp arm64-gapps gsi on top of a fully working, Magisk-rooted,, stock android 10 system, by installing a new gsi system image, and leaving all other partitions, including data, alone. Nothing was wiped. I also removed the android lock screen in TWRP by installing a lockscreen remover zip. Other than the fact that you have to reinstall Magisk.zip, you don't have to do a thing. It just works.
Do you have widevine L1? Are you able to play Disney+ or discovery+? I'm having lots of issues that seem to be codec related
I don't use those apps, so I can't comment on how phh-aosp would handle them. I do know that phh-aosp is the most fully developed gsi available, so it might be worth trying.
snickle said:
None of this is my work, just the steps to get it to run for me.
The steps are fairly step by step and some seem redundant, but they work. I had lots of failures.
Start with TWRP and Magisk Installed
Note: This will process will complete erase device, so make sure google backup is up to date and using titanium (or something else) for any other backups.
Download the following files and copy to sdcard
Device ID
Device ID.apk | by xda-developers.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Nikgapps
https://sourceforge.net/projects/nikgapps/files/Config-Releases/NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip/download
Force Decrypt
Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip | by Droidwin for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
TrebleGSI Image (Make sure to extract image from xz file)
https://sourceforge.net/projects/treblerom/files/crDRom11/2021.05.21/crdrom-v308-210521-arm64-bvZ-lite.img.xz/download
Latest Magisk APK (Make sure to change extension to .zip)
Reboot to recovery
Goto Wipe
Format Data
Advanced wipe - Select System and wipe
Install cdrom-c306-210428-arm64-bvz.img to system
Reboot recovery
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Reboot system
Press and hold power button when Eye icon shows up. Select restart - Recovery
Goto Wipe
Format Data
Reboot recovery
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip
Reboot system
Click start
Skip Mobile network
Select and login to wifi
On Copy apps & data click next
Select a backup from cloud
Enter PIN
When you get "This device isn't Play Protect certified" select "Got It"
Click More and accept through google services
Select Face unlock + PIN
Enter PIN twice
Setup Face lock
Click Done
Click Next
Click Skip
Click Start
Ignore Play Protect errors
Setup sdcard as portable storage
Install Device+ID.apk from sdcard
Open Device ID and accept permissions
On PC goto https://www.google.com/android/uncertified/ and enter GSF.
Wait 2 minutes - PLEASE!!!
Reboot
Goto Settings - Accounts
Add your google account.
Either restore from account setting or wait to be prompted to finish setup. This will restore apps, contacts, etc.
When Setup complete run Magisk and complete its setup.
In Magisk, enable MagiskHide and Hide Google Play Store
Run safetycheck. It should fail.
Load module MagiskHide Props Config
Reboot
From terminal window (I use TermUX),
Run:
su
props
Select 1
Enter fingerprint value: Lenovo/LenovoTB-X606F/X606F:10/QP1A.190711.020/TB-X606F_USR_S300177_2103041623_V9.56_BMP_ROW:user/release-keys
b to go back
4 for custom props
n for new custom prop
Property: ro.build.version.security_patch
Value: 2021-02-05
e to exit
Reboot
Go to magik and rerun safetycheck. It should pass and restricted apps now available in store (Disney, Netfilx, etc.)
Update apps in Play Store
Setup tablet to your preferences
Good Luck.
Click to expand...
Click to collapse
Greetings!
I was able to use these same steps to install Lineage OS 18.1 with no problem. I retrieved rom from:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
No issues with features so far (camera works, wifi works, even gestures seem to work).
Thank you so much for sharing your steps. It's much appreciated!
ZorgonPeterson said:
Greetings!
I was able to use these same steps to install Lineage OS 18.1 with no problem. I retrieved rom from:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
No issues with features so far (camera works, wifi works, even gestures seem to work).
Thank you so much for sharing your steps. It's much appreciated!
Click to expand...
Click to collapse
Did you pass security checks?
i am having trouble passing them with LineageOS 18.1
snickle said:
When Setup complete run Magisk and complete its setup.
In Magisk, enable MagiskHide and Hide Google Play Store
Run safetycheck. It should fail.
Load module MagiskHide Props Config
Reboot
From terminal window (I use TermUX),
Run:
su
props
Select 1
Enter fingerprint value: Lenovo/LenovoTB-X606F/X606F:10/QP1A.190711.020/TB-X606F_USR_S300177_2103041623_V9.56_BMP_ROW:user/release-keys
b to go back
4 for custom props
n for new custom prop
Property: ro.build.version.security_patch
Value: 2021-02-05
e to exit
Reboot
Go to magik and rerun safetycheck. It should pass and restricted apps now available in store (Disney, Netfilx, etc.)
Update apps in Play Store
Setup tablet to your preferences
Good Luck.
Click to expand...
Click to collapse
I used the above fingerprint, I even tried the fingerprint from a stock install (which is the same by the way) and it still fails CTS safety check. I rebooted after adding the fingerprint. Everything worked great up to this part.
I used the crdrom that has gapps embedded (I think it was the bgZ version). Could that be an issue?
I wish there was a full rom for this tablet, but I do not have enough experience building these to build one from scratch.
dpn982 said:
I wish there was a full rom for this tablet, but I do not have enough experience building these to build one from scratch.
Click to expand...
Click to collapse
I tried building Lineage 18.1 using the device tree, vendor, and kernel repos I found on GitHub for this tablet and it failed building the kernel. Admittedly, I'm not good with such things or troubleshooting the errors but maybe someone around here can.
First of all thanks for these steps...
Just a quick report that I was able to use them to do a clean install of LineageOS 19 (Android 12) using Andy Yan's GSI Build:
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
lineage-19.0-20211106-UNOFFICIAL-treble_arm64_bvS-vndklite.img.xz
And using NikGapps for android 12 GAPPS:
NikGapps - Browse /Releases/NikGapps-S/18-Oct-2021 at SourceForge.net
A Custom Google Apps Package that Suits Everyone Needs!
sourceforge.net
NikGapps-core-arm64-12-20211018-signed.zip
For bleeding edge stuff I can say it is running VERY smoothly. I figured I would try the latest thing and then downgrade to Android 11 or even 10, but so far 12 is running so well, I think I will leave it. Pretty big design evolution for Android.
Just a question from someone who's had a break from xda.
This rom is a universalrom for the chip, not a specific tablet? or a jump of point?
sixshooterz said:
I tried building Lineage 18.1 using the device tree, vendor, and kernel repos I found on GitHub for this tablet and it failed building the kernel. Admittedly, I'm not good with such things or troubleshooting the errors but maybe someone around here can.
Click to expand...
Click to collapse
can you share your steps and sources?
I'd love a lineage for the tp-x606f and if i have to build myself the initially i could not find other thatclickbait for this tab & lineage
This is a generic for the chip. Not my work, I just figured out the steps to get it to work on our tablets. I don't know where source is. I just download updates from sourceforge
scottyrick2 said:
I just installed the latest android 11 phh-aosp arm64-gapps gsi on top of a fully working, Magisk-rooted,, stock android 10 system, by installing a new gsi system image, and leaving all other partitions, including data, alone. Nothing was wiped. I also removed the android lock screen in TWRP by installing a lockscreen remover zip. Other than the fact that you have to reinstall Magisk.zip, you don't have to do a thing. It just works.
Click to expand...
Click to collapse
Is there anyone who has tried this way to flash phh or another Rom? It seems much less tricky than the proposed one on this thread.
aftnoon2 said:
Is there anyone who has tried this way to flash phh or another Rom? It seems much less tricky than the proposed one on this thread.
Click to expand...
Click to collapse
With new version of twrp, it has gotten easier. Magisk has changed also. I am out of town but will update op when I return next week
I'd like to try to flash Phh 11 Rom. Which one is good for my TB-X606F? Those with vdlnklite or without? Floss or no Floss?
This is a new world of flashing to me, sorry for this questions.
snickle said:
None of this is my work, just the steps to get it to run for me.
The steps are fairly step by step and some seem redundant, but they work. I had lots of failures.
Start with TWRP and Magisk Installed
Note: This will process will complete erase device, so make sure google backup is up to date and using titanium (or something else) for any other backups.
Download the following files and copy to sdcard
Device ID
Device ID.apk | by xda-developers.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Nikgapps
https://sourceforge.net/projects/nikgapps/files/Config-Releases/NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip/download
Force Decrypt
Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip | by Droidwin for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
TrebleGSI Image (Make sure to extract image from xz file)
https://sourceforge.net/projects/treblerom/files/crDRom11/2021.05.21/crdrom-v308-210521-arm64-bvZ-lite.img.xz/download
Latest Magisk APK (Make sure to change extension to .zip)
Reboot to recovery
Goto Wipe
Format Data
Advanced wipe - Select System and wipe
Install cdrom-c306-210428-arm64-bvz.img to system
Reboot recovery
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Reboot system
Press and hold power button when Eye icon shows up. Select restart - Recovery
Goto Wipe
Format Data
Reboot recovery
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip
Reboot system
Click start
Skip Mobile network
Select and login to wifi
On Copy apps & data click next
Select a backup from cloud
Enter PIN
When you get "This device isn't Play Protect certified" select "Got It"
Click More and accept through google services
Select Face unlock + PIN
Enter PIN twice
Setup Face lock
Click Done
Click Next
Click Skip
Click Start
Ignore Play Protect errors
Setup sdcard as portable storage
Install Device+ID.apk from sdcard
Open Device ID and accept permissions
On PC goto https://www.google.com/android/uncertified/ and enter GSF.
Wait 2 minutes - PLEASE!!!
Reboot
Goto Settings - Accounts
Add your google account.
Either restore from account setting or wait to be prompted to finish setup. This will restore apps, contacts, etc.
When Setup complete run Magisk and complete its setup.
In Magisk, enable MagiskHide and Hide Google Play Store
Run safetycheck. It should fail.
Load module MagiskHide Props Config
Reboot
From terminal window (I use TermUX),
Run:
su
props
Select 1
Enter fingerprint value: Lenovo/LenovoTB-X606F/X606F:10/QP1A.190711.020/TB-X606F_USR_S300177_2103041623_V9.56_BMP_ROW:user/release-keys
b to go back
4 for custom props
n for new custom prop
Property: ro.build.version.security_patch
Value: 2021-02-05
e to exit
Reboot
Go to magik and rerun safetycheck. It should pass and restricted apps now available in store (Disney, Netfilx, etc.)
Update apps in Play Store
Setup tablet to your preferences
Good Luck.
Click to expand...
Click to collapse
is this the complete procedure of establishing a custom ROM ?
I followed the guide by installing the latest version of the CrDroid, everything went fine except the verification of the CTS, I've already tried with Magisk but it doesn't seem to work, any ideas? Thanks in advance
{
"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"
}
Hello everyone and my apologies for my terrible English (I did this with the help of Google Translator) since I cannot find reliable information in my language (Spanish).
I just bought a Redmi 9T model M2010J19SG (4/64 GB, Android v10, MIUI v12.0.5, unmodified) and I would like to be able to restore some applications, as they were configured on my previous mobile (Galaxy S4 GT-I9500 Android v4.4.2 , rooted), for this I tried to use Titanium Backup Pro that I have been using for a long time for my backups and restorations but the Redmi does not allow it because I am not a root user on that phone.
Someone could help me, step by step, on how to install the appropriate TWRP on my Redmi 9T, to then be able to install and use the Magisk to root the phone and be able, using the Titanium, to restore those applications that interest me so much.
Thanks
First, unlock the bootloader by following this guide: https://romprovider.com/unlock-bootloader-redmi-9-power/?amp
Wait for 7 days max, and then try going to the fastboot mode and unlock it again. Do not log out your MIUI account on the device otherwise the timer would reset. Feel free to use the device while waiting, you wouldn't want to wait in the fastboot mode, do you? Hahaha jkkk
And then go to this post to download OrangeFox recovery: https://forum.xda-developers.com/t/...dmi-9-power-redmi-note-9-4g-redmi-9t.4263407/
And here, look for the fastboot instruction, follow that to flash OrangeFox to Redmi (DO NOT do the zip instruction, it wouldnt work on the stock MIUI recovery): https://wiki.orangefox.tech/en/guides/installing_orangefox
STAY ON THE RECOVERY ONCE YOU HAVE FLASHED IT!!!
Do not reboot to the system, if you accidentally do, just reflash the OrangeFox recovery as MIUI have already replaced it with the stock recovery.
Anyways after that, you should have a working recovery, now using a computer go to Magisk github release page, download the version 23 zip file: https://github.com/topjohnwu/Magisk/releases
While still on recovery, connect your Redmi 9T to the computer using cable, it will show up as MTP device. Just copy over the magisk file I mentioned to the Redmi. I forgot you can actually download this and copy before unlocking your bootloader so you won't have to later.
Locate the magisk file in OrangeFox and then flash it. VOILA you're done! Reboot to system.
==
BACKUP YOUR FILES AND APP DATA!!! In case something goes wrong. I do not guarantee this would work. Feel free to get help though...
To uninstall magisk, duplicate the magisk zip then rename it to uninstall.zip - flash in the recovery as usual.
I know a simple thing but, use a pin code or a password so you would be able to unlock the /data partition in OrangeFox. You would see the unlock screen right away after booting to the recovery, just enter your code or password and you're good to go.
Sorry that no one answered you, i don't know perhaps right now you could have already figured out how to, but nonetheless this would be a reference to those who are about to do the same thing as you wanted.
I forgot you said TWRP, im sorry.
Anyway the TWRP link: https://forum.xda-developers.com/t/recovery-3-5-a10-twrp-unnoficial-for-lime-redmi9t-beta.4233045/
The general steps are more or less the same. That post also contains instructions how to flash TWRP. Feel free to ask questions if you need help.
AJPuzonThank you, thank you and thank you very much for the explanation. I will follow your recommendations and when I finish I will report the results.
Also gonna put this here while I still remember:
It's very likely that the phone will fail SafetyNet once Magisk is installed. Hence no banking apps will work and you cant install apps that require Safetynet (they will be hidden) So here's what I did on mine to pass it again:
1. Go to Magisk settings (should be at the top right cog icon), turn on MagiskHide.
Now go back, tap the shield icon below (Superuser requests) MagiskHide is now visible, go to that. Tap Google Services and it will expand, check all the additional items under it.
- do this for all the other google apps that you have installed.
2. Go to Magisk settings again and the turn on Hide Magisk. Name it to whatever you want. Reopen Magisk using the new program name that you assigned it to. Reboot.
3. And then go ahead and clear the App Data of both Google Play Services and Google Play Store. Reboot
Additional steps for custom roms:
1. Go to modules (4th option below) and then install MagiskHide Props Config. Now reboot.
2. Go to Play Store and then install a terminal application. (Material Terminal is what I use in this case).
3. Open the terminal app, type props then press enter, after follow the instructions to find your device in the list, change your device fingerprint to that. Reboot once done.
4. Again clear the app data of Google Play Services and Google Play Store, and reboot.
First of all this is not my work is just tried this rom and its preety stable. Thanks to developers @phhusson @Magendanz
DESCLAIMER :use it your own risk.
So finally this rom booted on galaxy tab SM-T515 everything thing is working with small bugs as mentioned below.
Download files given below:
Bugs :
1)voLTE: not working tried phh treble settings to solve the issue but no luck.
Other networks, data calling works perfectly
2)MTP: mtp not working but you can transfer files after booting device in TWRP mode
3)audio not recording in videos use open camera app and go to settings and set default audio as a source.
4)For Linageos 19 android 12 twrp internal storage nonaccesible so to restore back to stock ROM just falsh latest Odin firmware using
ODIN app
Reverting to Samsung oneui:
For Linageos 19 android 12 twrp internal storage nonaccesible so to restore back to stock ROM just falsh latest Odin firmware using
ODIN app
Download firmware using this app:
Download link for Android/Linux/Mac/Windows:
Releases · zacharee/SamloaderKotlin
Contribute to zacharee/SamloaderKotlin development by creating an account on GitHub.
github.com
Linageos18.1 user restore your oneui backup using twrp or use ODIN firmware.
Except these you can check and tell me I didn't found anything till now
Download this gsi fileonly this is compatible)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/lineage-18.1-20211010-UNOFFICIAL-treble_a64_bvS-vndklite.img.xz/download
Download arm 32 android 11 gapps :
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Linageos 19 android 12Gapps included)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/lineage-19.0-20220114-UNOFFICIAL-treble_a64_bgS.img.xz/download
Download magisk zip:
https://dl.magiskapp.com/MagiskZip/Magisk-v23.0.zip
If you gets device certification error follow this post:
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
XZ file extractor android app:
GZ & XZ Extract - File Opener - Apps on Google Play
Extractor tool for tar, tar.gz, gz, gz2 & xz files. Just few taps for result
play.google.com
Process :
1)Download all files given first extract xz file gsi file using xz extractor you gets img file.
2)Now transfer gsi.img, gapps and magisk file in tablet.
3)boot tablet to TWRP MODE
4)Now first select wipe >advance wipe>select system> slide
5) now go back click install click install img you will see your file click on it and select system partition and enter.
6) now we have to install gapps but we need to first resize system partition so
First click mount and mount system Partation now go to wipe>advance wipe>select system >clcik repair >click resize
7)now click install and. Select gapps and flash.
8)now go back install magisk and hit reboot.
After reboot you may face device certification error so to solve this go to magisk and install magisk hide props configuration module and reboot your phone.
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
MagiskHide Props Config v6.1.2 Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again. If anyone feels like taking over...
forum.xda-developers.com
Follow this video i will update thread soon
Android 11 Linageos 18.1
Android 12 lineageOS 19
How's the battery life?
works offline charge?
Pinage said:
How's the battery life?
Click to expand...
Click to collapse
Best battery life
Spawacz_Reduktor said:
works offline charge
Click to expand...
Click to collapse
Yes
@pankspoo
Have you tried LOS 19? I saw your video on aosp 12 build but from your video it seems that it sucks! Lineage I feel will be miles better than aosp so if you can try and get back it'll be really helpful!
Sukrith said:
@pankspoo
Have you tried LOS 19? I saw your video on aosp 12 build but from your video it seems that it sucks! Lineage I feel will be miles better than aosp so if you can try and get back it'll be really helpful!
Click to expand...
Click to collapse
Yes same time but that has grafix shutter issue same like gsi
pankspoo said:
Yes same time but that has grafix shutter issue same like gsi
Click to expand...
Click to collapse
There seems to be a new build, can you maybe try? It's based on 6th November build.
Sukrith said:
There seems to be a new build, can you maybe try? It's based on 6th November build.
Click to expand...
Click to collapse
Ok
In January I installed 17.1 using this ROM. Do I need to go through the whole process of resizing the partition, since I already did it for 17.1?
Never mind! I went ahead and installed it following the instruction . It works, thanks!
bedwere said:
Never mind! I went ahead and installed it following the instruction . It works, thanks!
Click to expand...
Click to collapse
Are you happy with this ROM?
Krekle said:
Are you happy with this ROM?
Click to expand...
Click to collapse
Yes, it's very stable.
I have one issue and some questions.
When using a Bluetooth Headset, I have no sound in apps like Jitsi. Mic on the Bluetooth Headset is working in Jitsi, the others can here me. When using e.g. youtube in Chromium I can hear sound via the Bluetooth Headset.
I checked "Force-disable A2DP offload" and restarted, still the same.
Any Ideas?
And some Questions:
- Is magisk only needed for root? I don't need to root, do i still have to install magisk?
- in twrp I can't mount the system partition, so I cant fix it, but the rom is working. So how to mount system?
- I don't want gapps, is it ok to use the roms without gapps? so eg this one ...treble_a64_bvS.img ?
- in the description downloadlinks you are using: 18: treble_a64_bvS-vndklite but 19: treble_a64_bgS, so should one use vndklite for 18 but not for 19? Or also for 19? What is better? ...
Regards
This is confirmed to work on the T-510? Curiosity will brick the tab, like it kills the cat....
Shawnashley said:
This is confirmed to work on the T-510? Curiosity will brick the tab, like it kills the cat....
Click to expand...
Click to collapse
Yep. It works. I previously had the latest Nexus rom flashed on my SMT-510, so in TWRP I just flashed Lineage 19.1 to system, formatted data, rebooted and it loaded successfully. With Magisk 24.1. It all runs surprisingly well. No issues so far other than no USB file transfer or ability to mount System partition.
HansMampf said:
I have one issue and some questions.
When using a Bluetooth Headset, I have no sound in apps like Jitsi. Mic on the Bluetooth Headset is working in Jitsi, the others can here me. When using e.g. youtube in Chromium I can hear sound via the Bluetooth Headset.
I checked "Force-disable A2DP offload" and restarted, still the same.
Any Ideas?
And some Questions:
- Is magisk only needed for root? I don't need to root, do i still have to install magisk?
- in twrp I can't mount the system partition, so I cant fix it, but the rom is working. So how to mount system?
- I don't want gapps, is it ok to use the roms without gapps? so eg this one ...treble_a64_bvS.img ?
- in the description downloadlinks you are using: 18: treble_a64_bvS-vndklite but 19: treble_a64_bgS, so should one use vndklite for 18 but not for 19? Or also for 19? What is better? ...
Regards
Click to expand...
Click to collapse
I can only answer some of your questions:
- Magisk is only used for root. It's not required.
- Mounting /system in TWRP or in a File explorer doesn't seem to be possible.
- GApps is built in to roms with "...bgS.img.xz". For vanilla roms without gapps download the "...bvS.img.xz"file.
- For LOS 19, I flashed treble_a64_bgS and didn't have an issue. I can't comment on the vndklite version or what it's used for since I never tried it.
betacrypt said:
Yep. It works. I previously had the latest Nexus rom flashed on my SMT-510, so in TWRP I just flashed Lineage 19.1 to system, formatted data, rebooted and it loaded successfully. With Magisk 24.1. It all runs surprisingly well. No issues so far other than no USB file transfer or ability to mount System partition.
Click to expand...
Click to collapse
Any idea about success of I am running Megadanz 11.0 ROM?
Shawnashley said:
Any idea about success of I am running Megadanz 11.0 ROM?
Click to expand...
Click to collapse
It's a good rom and works very well. I was using it before I upgraded to LOS19.1.
Hey there!
I Installed this a couple of weeks ago, but has to reinstall nexus stock 11.0 pretty quickly, as after spending an evening trying to fix issues, it just wouldn't work.
Issues:
1) App crashes are constant. I cannot open Chrome, YouTube, Google Podcasts, Twitter - they all crash to launcher. - Cache, dalvik and data was cleared, still nothing
2) Gesture Navigation is missing - is it meant to be?
3) Magisk installs successfully,, but is then not recognised by the app, meaning no modules. - Is that normal?
Does anyone have any idea on how I could fix these issues, so I can install again?
Many thanks