Related
So in this guide or tutorial i'll show you how to patch boot.img so it doesn't fails to boot.
what you'll need
Python (We're using a python script to unpack/repack)
This python script https://github.com/liudongmiao/bootimg
Text editor (notepad++) for windows is a good thing
Patience
Now if you have python installed navigate to the folder where your bootimg.py & boot.img exist
now open cmd or terminal depending on what system you're using. and enter:
python bootimg.py --extract-bootimg
python bootimh.py --extract-ramdisk
Now we need to disable dm-verity and such
To disable system check change: ro,barrier=1 wait,verify > ro,barrier=1 wait
it is recommended to do this to all partitions u want to be able to modify later.
now you can also remove dm-verity executable and is not needed and it most likely will cause your boot.img to fail.
There's probably need to patch se policy file as well so you could use phh zip to do this.
And thats it. Post 2 is to add superuser access but it'll be later
How to swap from phh to chainfire supersu
Open init.environ.rc and add
export PATH /su/bin:/sbin:/vendor/bin:/system/sbin:/system/bin:/su/xbin:/system/xbin
Above bootlogo
Now download the two zips and extract su folder to root of ramdisk
And the sbin to sbin folder but don't remove any files!
Now if u have trouble with remount system as rw you need to edit the fstab and remove the verify on its partition. Now just repack ramdisk and then repack boot and you should be done
LastStandingDroid said:
So in this guide or tutorial i'll show you how to patch boot.img so it doesn't fails to boot.
what you'll need
Python (We're using a python script to unpack/repack)
This python script https://github.com/liudongmiao/bootimg
Text editor (notepad++) for windows is a good thing
Patience
Now if you have python installed navigate to the folder where your bootimg.py & boot.img exist
now open cmd or terminal depending on what system you're using. and enter:
python bootimg.py --extract-bootimg
python bootimh.py --extract-ramdisk
Now we need to disable dm-verity and such
To disable system check change: ro,barrier=1 wait,verify > ro,barrier=1 wait
it is recommended to do this to all partitions u want to be able to modify later.
now you can also remove dm-verity executable and is not needed and it most likely will cause your boot.img to fail.
There's probably need to patch se policy file as well so you could use phh zip to do this.
And thats it. Post 2 is to add superuser access but it'll be later
Click to expand...
Click to collapse
Sorry, which tool do you use in order to extract boot img from UPDATE.APP?
And after unpack and repack ramdisk and boot is it normale that the new boot.img is smaller than the "original" boot.img?
Thanks, I'm trying to patch honor 5c boot image in order to root it.
Huawei Firmware Extractor will unpack the UPDATE.APP.
LastStandingDroid said:
So in this guide or tutorial i'll show you how to patch boot.img so it doesn't fails to boot.
what you'll need
Python (We're using a python script to unpack/repack)
This python script https://github.com/liudongmiao/bootimg
Text editor (notepad++) for windows is a good thing
Patience
Now if you have python installed navigate to the folder where your bootimg.py & boot.img exist
now open cmd or terminal depending on what system you're using. and enter:
python bootimg.py --extract-bootimg
python bootimh.py --extract-ramdisk
Now we need to disable dm-verity and such
To disable system check change: ro,barrier=1 wait,verify > ro,barrier=1 wait
it is recommended to do this to all partitions u want to be able to modify later.
now you can also remove dm-verity executable and is not needed and it most likely will cause your boot.img to fail.
There's probably need to patch se policy file as well so you could use phh zip to do this.
And thats it. Post 2 is to add superuser access but it'll be later
Click to expand...
Click to collapse
In which file we have to edit this line "ro,barrier=1 wait,verify > ro,barrier=1 wait". I have infinix smart 5 x657b. I extracted the boot file and from some instructions on google, I opened fstab file. But there is nothing like that line.
hassansuriya said:
In which file we have to edit this line "ro,barrier=1 wait,verify > ro,barrier=1 wait". I have infinix smart 5 x657b. I extracted the boot file and from some instructions on google, I opened fstab file. But there is nothing like that line.
Click to expand...
Click to collapse
There is a way to remove dm-verity and forceencrypt by just flashing a file in twrp.
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
CHECK_123 said:
There is a way to remove dm-verity and forceencrypt by just flashing a file in twrp.
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
Click to expand...
Click to collapse
but there is not any version of twrp recovery for my device. From where should I download it?
hassansuriya said:
but there is not any version of twrp recovery for my device. From where should I download it?
Click to expand...
Click to collapse
I found this "auto twrp recovery porter"
Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek
If you wish to root your Mediatek Android phone, we'd dropped a guide on rooting using Magisk and stock boot.img at https://www.hovatek.com/forum/thread-21427.html , no custom recovery is required. Se
forum.hovatek.com
I dont know if it would work, you should try
You may have to sign up to get the andorid 9 and 10 version of the tool
Hi All,
I am interested in any ROM, preferably based on LOS, that has no GAPPS pre-installed?
Is there any such? nougat, oreo, and whatever P is... doesn't matter.
A follow-up question for the more technically advanced than I: why is this such a problem for PH1? I believe the PIXEL phones also have A/B partitions, and are supported by LOS
Thanks!
lleo_ said:
Hi All,
I am interested in any ROM, preferably based on LOS, that has no GAPPS pre-installed?
Is there any such? nougat, oreo, and whatever P is... doesn't matter.
A follow-up question for the more technically advanced than I: why is this such a problem for PH1? I believe the PIXEL phones also have A/B partitions, and are supported by LOS
Thanks!
Click to expand...
Click to collapse
The number of developers fixing issues on the pixel vs this phone is astounding...
rignfool said:
The number of developers fixing issues on the pixel vs this phone is astounding...
Click to expand...
Click to collapse
I do recognize that, but given similarities between devices, would not be possible to adopt the work done by those developers. Granted that I ask this with the knowledge of a noob.
To follow up are you saying that there is no such as GAPPS-less ROM for PH1?
lleo_ said:
I do recognize that, but given similarities between devices, would not be possible to adopt the work done by those developers. Granted that I ask this with the knowledge of a noob.
To follow up are you saying that there is no such as GAPPS-less ROM for PH1?
Click to expand...
Click to collapse
There are... But they come and go as far as updates and such...
The demand is for Google... And moar features without losing Google...
Now... What you can do/try is wander over to the Project Trebble area... I would assume that you will find a plethora of development...
You're gonna be wading in some unknown territory... And it'll be a mystery as to what works... And whether it's fixable... Good luck
EDIT: or... You can magisk yourself... And try NanoMod... I think that disables a ton of Google stuff and puts FOSS stuff in it's place...
Sir! Thank You for your post. At first I thought it was a joke, but I learned something today. The concept and related work of project Treble bypassed me. I have already a GApps-less LOS on my Ph1. Again thanks!
Don't know if this applies, but lots of ppl are successfully running GSIs on the Essential.
Maybe some of them are GAPP-less?
@lleo_ another thing you can always do, is run Stock Android and Debloat it and run it Gapp Free, just like any custom rom...
As they say YMMV (Your Mileage May Vary), and I found Stock Oreo to be more stable on the Essential, so I debloated it, made it Deodex and patched for Signature Spoofing and of course Gapp Free. I still have the Gboard, Contacts, Messeges, and Phone, but these can be removed and replaced easily, any and everything Google can be taken out.
See the screen shot...
DoR3M3 said:
@lleo_ another thing you can always do, is run Stock Android and Debloat it and run it Gapp Free, just like any custom rom...
As they say YMMV (Your Mileage May Vary), and I found Stock Oreo to be more stable on the Essential, so I debloated it, made it Deodex and patched for Signature Spoofing and of course Gapp Free. I still have the Gboard, Contacts, Messeges, and Phone, but these can be removed and replaced easily, any and everything Google can be taken out.
See the screen shot...
Click to expand...
Click to collapse
Hey can you explain how to debloat, is there a script for it. How do you patch it and deodex it.
Thanks
arjunv said:
Hey can you explain how to debloat, is there a script for it. How do you patch it and deodex it.
Thanks
Click to expand...
Click to collapse
These steps below, you're probably going to wonder, why do I need to Deodex and Signature Spoof just to debloat? Good point, you don't, but then you can only get so far away from Google in your system by not doing this. The point to this method is to have Signature Spoofing support in Android, where you can better utilize microg support, to have it as the alternative instead of Google.
The Deodex and Nanodroid-patcher support, only need to be performed if you are running Stock Android, or a ROM that has not been Deodex and doesn't support Signature Spoofing. This also doesn't have to be done, if you still want to run the Google Services/Framework.
If you only want to Debloat, then follow the Debloat section below.
For the Deodex, YMMV (Your Mileage May Vary), but it's been working great for me, so here goes!
I did this on Stock Oreo 8.1.0 which has both odex and vdex files in /system/framework, so I followed the VDEX method mentioned below.
This is going to be easy if you're a Linux User/Geek, if you are running Windows and have never done anything like this, and if you have both odex and vdex files on your phone in /system/framework, then I can do this for you if you want, unless you want to get into learning this.
If you want me to, then in TWRP, click Mount and click on System at the top to mount it and then run this command in the command prompt, I'm assuming you have adb/fastboot installed...
adb pull /system/framework framework If that doesn't work, it typically ends up being, adb pull /system/system/framework framework
I'm assuming your device is arm64, so then look in the directory; framework/oat/arm64/ or /arm, and attach the services.vdex file and I'll patch it for you.
Deodex & Signature Spoofing
1. Check /system/framework, do you see both .odex and .vdex files?
2. If you have both .odex and .vdex files follow the guide under VDEX, if you only have .odex files, then follow the ODEX section. Don't be confused by the guide as only having either services.vdex or services.odex. You are looking to see if all the files are one or the other or both.
https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md
3. If you have both files and need to follow the VDEX method in Windows, then you'll need cygwin as stated on the vdexExtractor Github, and install zlib-devel from the cygwin installer. cygwin as stated on the site is a collection of GNU and Open Source tools, this allows you to compile the vdexExtractor source in Windows into the running program.
https://www.cygwin.com/
4. If you have to do the ODEX method the baksmali.jar and smali.jar are already built, there's a download for them on the GitHub page, and you'll need to have Java JRE installed.
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
Whether I'm patching it, or you follow one of the methods I've described, once this is done, you'll need to download the latest NanoDroid-patcher. This is what patches the Deodex ROM to apply signature spoofing support.
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928 - Stable Download (Nanolx)
Be sure to also grab NanoDroid-fdroid if you don't have F-droid installed. You might want to also grab NanoDroid-microG while you're at it, if you want to go for a real system Google Debloat too, but any concerns, or issues, please post on Setialpha's NanoDroid post for any microg support.
As soon as you're done with the Deodex steps, at the bottom the tutorials clearly state; unmount /system and flash the NanoDroid-Patcher, so uncheck System that you checked before in Mount, and now install/flash NanoDroid-patcher, TWRP > Install
If the device is not rooted, then make sure to root it with Magisk. Personally I find it best with the Essential to now boot to the bootloader, then boot back into TWRP. In TWRP flash NanoDroid-fdroid if you grabbed it, then the boot.img and then Magisk, then boot into the System.
Debloating Apps Systemlessly
1. Open Magisk Manager - Downloads - search for Debloater, then you should see Debloater (Terminal Emulator).
2. Reboot
3. Now you'll need a terminal emulator in Android because Debloater (Terminal Emulator) runs from the command line, it doesn't have a GUI. I recommend using Termux, it's a very powerful terminal emulator with lots of things going on about it. If you didn't install F-Droid as I mentioned before, then you should of noticed on the NanoDroid download link NanoDroid-fdroid, download this and flash/install it in TWRP.
4. Now with F-Droid, open it, go to Settings and turn on Expert mode and check Privileged Extension, then close and reopen F-Droid. Next, search for and install Termux.
5. Open Termux and at the command prompt type su for superuser access. On a side note, if you don't know, or have never used Termux, press and hold Vol UP on the phone and tap q on the keyboard which will give you some short cut options. But you'll want to go online to their Wiki and learn about the power of Termux.
6. Now simply type debloat and remove what you want. Remember if you make a mistake, you have Option 4 to reinstall what you removed by mistake.
That's all there is to Deodex, Signature Spoof Patching and Debloating apps systemlessly in Android.
If the VDEX/ODEX methods don't work for some strange reason, then you'll want to explore using SuperR's Kitchen to Deodex the rom, and most people recommend you get the donate version for better features and support.
https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Good Luck
DoR3M3 said:
These steps below, you're probably going to wonder, why do I need to Deodex and Signature Spoof just to debloat? Good point, you don't, but then you can only get so far away from Google in your system by not doing this. The point to this method is to have Signature Spoofing support in Android, where you can better utilize microg support, to have it as the alternative instead of Google.
The Deodex and Nanodroid-patcher support, only need to be performed if you are running Stock Android, or a ROM that has not been Deodex and doesn't support Signature Spoofing. This also doesn't have to be done, if you still want to run the Google Services/Framework.
If you only want to Debloat, then follow the Debloat section below.
For the Deodex, YMMV (Your Mileage May Vary), but it's been working great for me, so here goes!
I did this on Stock Oreo 8.1.0 which has both odex and vdex files in /system/framework, so I followed the VDEX method mentioned below.
This is going to be easy if you're a Linux User/Geek, if you are running Windows and have never done anything like this, and if you have both odex and vdex files on your phone in /system/framework, then I can do this for you if you want, unless you want to get into learning this.
If you want me to, then in TWRP, click Mount and click on System at the top to mount it and then run this command in the command prompt, I'm assuming you have adb/fastboot installed...
adb pull /system/framework framework If that doesn't work, it typically ends up being, adb pull /system/system/framework framework
I'm assuming your device is arm64, so then look in the directory; framework/oat/arm64/ or /arm, and attach the services.vdex file and I'll patch it for you.
Deodex & Signature Spoofing
1. Check /system/framework, do you see both .odex and .vdex files?
2. If you have both .odex and .vdex files follow the guide under VDEX, if you only have .odex files, then follow the ODEX section. Don't be confused by the guide as only have either services.vdex or services.odex. You are looking to see if all the files are one or the other or both.
https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md
3. If you have both files and need to follow the VDEX method in Windows, then you'll need cygwin as stated on the vdexExtractor Github, and install zlib-devel from the cygwin installer. cygwin as stated on the site is a collection of GNU and Open Source tools, this allows you to compile the vdexExtractor source in Windows into the running program.
https://www.cygwin.com/
4. If you have to do the ODEX method the baksmali.jar and smali.jar are already built, there's a download for them on the GitHub page, and you'll need to have Java JRE installed.
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
Whether I'm patching it, or you follow one of the methods I've described, once this is done, you'll need to download the latest NanoDroid-patcher. This is what patches the Deodex ROM to apply signature spoofing support.
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928 - Stable Download (Nanolx)
Be sure to also grab NanoDroid-fdroid if you don't have F-droid installed. You might want to also grab NanoDroid-microG while you're at it, if you want to go for a real system Google Debloat too, but any concerns, or issues, please post on Setialpha's NanoDroid post for any microg support.
As soon as you're done with the Deodex steps, at the bottom the tutorials clearly state; unmount /system and flash the NanoDroid-Patcher, so uncheck System that you checked before in Mount, and now install/flash NanoDroid-patcher, TWRP > Install
If the device is not rooted, then make sure to root it with Magisk. Personally I find it best with the Essential to now boot to the bootloader, then boot back into TWRP. In TWRP flash NanoDroid-fdroid if you grabbed it, then the boot.img and then Magisk, then boot into the System.
Debloating Apps Systemlessly
1. Open Magisk Manager - Downloads - search for Debloater, then you should see Debloater (Terminal Emulator).
2. Reboot
3. Now you'll need a terminal emulator in Android because Debloater (Terminal Emulator) runs from the command line, it doesn't have a GUI. I recommend using Termux, it's a very powerful terminal emulator with lots of things going on about it. If you didn't install F-Droid as I mentioned before, then you should of noticed on the NanoDroid download link NanoDroid-fdroid, download this and flash/install it in TWRP.
4. Now with F-Droid, open it, go to Settings and turn on Expert mode and check Privileged Extension, then close and reopen F-Droid. Next, search for and install Termux.
5. Open Termux and at the command prompt type su for superuser access. On a side note, if you don't know, or have never used Termux, press and hold Vol UP on the phone and tap q on the keyboard which will give you some short cut options. But you'll want to go online to their Wiki and learn about the power of Termux.
6. Now simply type debloat and remove what you want. Remember if you make a mistake, you have Option 4 to reinstall what you removed by mistake.
That's all there is to Deodex, Signature Spoof Patching and Debloating apps systemlessly in Android.
If the VDEX/ODEX methods don't work for some strange reason, then you'll want to explore using SuperR's Kitchen to Deodex the rom, and most people recommend you get the donate version for better features and support.
https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Good Luck
Click to expand...
Click to collapse
Thank you so much for a detailed post
DoR3M3 said:
@lleo_ another thing you can always do, is run Stock Android and Debloat it and run it Gapp Free, just like any custom rom...
As they say YMMV (Your Mileage May Vary), and I found Stock Oreo to be more stable on the Essential, so I debloated it, made it Deodex and patched for Signature Spoofing and of course Gapp Free. I still have the Gboard, Contacts, Messeges, and Phone, but these can be removed and replaced easily, any and everything Google can be taken out.
See the screen shot...
Click to expand...
Click to collapse
Stoked to see two things here...1.) the answer to the question I was searching for about running my Essential with no gapps...and 2.) your choice in file explorers!
Installing Lineage
Few quick things.
Since the 8T does not have a single unified guide like FunkWizard did for other OnePlus devices, I'm adding some things that are likely important, but don't necessarily have to do with installing LOS.
This will be similar to my 6T installing Lineage guide. However the 8T is a newer device, and new to me. Expect it to change and get updated as things change. I'll add in pictures like the 6T guide soon.
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. If you use Windows, remove "sudo" from the commands (this is for Linux).
I am using a Global 8T, and have only tested these methods on such.
Make Sure OOS is Updated1. Start fresh, and make sure OOS is up to date.
This should be self explanatory. Go to settings, and system, check for updates. Download and install any system updates OOS has to make sure you have the latest firmware on your device.
Unlock the Bootloader2. Unlock the Bootloader
sudo fastboot flashing unlock
For this step you will need fastboot. 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. That will install most of the stuff we need, but really old versions of fastboot and adb. You must update fastboot to install LOS. Time to open up a terminal:
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
Next you need to make sure OEM unlocking is enabled. If you haven't tapped on the build number and enabled devloper options, do this now. enabling USB debugging for the moment, would also be helpful.
Now would be a good time to back everything up. The phone will get wiped.
Place the phone in fastboot mode. You can do this using the advanced reboot menu or ADB, or the key combinations (all key combos listed below for reference):
Volume Up + Power while turning on will boot to fastboot. (<-- Don't believe this works on the 8T)
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.
If you enabled USB Debugging in the terminal window, type (the phone will pop up a warning asking you to allow USB debugging, make sure you allow this):
sudo adb reboot bootloader (<-- This command will make the phone restart to the bootloader / fastboot)
Once there type the command below. Your phone will be wiped. Make sure you backed up any important information. Use the volume buttons to select unlock, and press the power button.
sudo fastboot flashing unlock
Backing up Persist / EFS3. Backing up the persist partition and EFS backup.
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/modemst1.bin
dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/modemst2.bin
Hopefully you never need a backup of your persist paritition or EFS backup. However if anything ever happens you'll be glad you have it. The EFS contains the IMEI, so it is unique to every device. You can do this at any point as long as you have root. The easiest way, epsecially for those not want to root their device is to use the broken TWRP. I got this TWRP and a bunch of my initial rooting information from @Mpolo87 's Guide OnePlus 8T EasyRoot. It is an excellent guide. The TWRP is in step 4. This is not the way you need to root LOS though. Download this TWRP.
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 recovery.img * <-- Sends that TWRP image to the phone to be booted temporarily. Only boot this, never run the command "flash".
With this TWRP loaded it is normal that the screen will be blank and just briefly flash the TWRP logo screen. All we need to do is use the terminal window on the PC. Run these commands:
sudo adb shell
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/modemst1.bin
dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/modemst2.bin
exit
sudo adb pull /sdcard/persist.img /home/mint/Desktop
sudo adb pull /sdcard/modemst1.bin /home/mint/Desktop
sudo adb pull /sdcard/modemst2.bin /home/mint/Desktop
It is important to use ADB to pull the files off of the device after creating them. They won't be accessible after you restart. Also if you are using a live Linux distro (USB) the files do not remain on the USB after you restart / power off. So you need to place these files on another hard drive or USB. The persist.img should be ~ 32MB the Modems should be ~ 2MB each. Once you have the files you can run
sudo adb reboot bootloader
Installing Lineage4. LOS 18.1 Thread
Quick Common questions:
Gapps are not included, you must sideload them if you want them. Personally I use NikGapps, LOS Recommends MindtheGapps.
Official LOS 8T Download Link
Download the latest build, and the recovery image from the link above.
You must have a current version of fastboot / adb to successfully install this. (Update method mentioned previously in this guide) To install Lineage it is as simple as the instructions listed on the LOS site.
From the terminal:
sudo adb reboot bootloader
sudo fastboot flash recovery lineage-18.1-20210506-recovery-kebab.img
Now reboot in recovery. Doesn't matter how you get there. You can use the volume keys to change the options in the bootloader, you can use volume down and power, etc. Once in Lineage Recovery we need to run the copy partitions zip. The link for this is on the LOS install page. However here is a direct link. In LOS recovery choose:
- Apply Update
- Apply from ADB
From the terminal on the PC
- sudo adb sideload copy-partitions-20210323_1922.zip
LOS recovery will warn you about the zip not being signed, flash this anyways. Hit the back button, choose advanced, and then reboot to recovery. It is now time to actually install LOS. In LOS Recovery:
- Factory Reset. (You did backup everything right?)
- Press Format data / factory reset.
- From the main LOS Recovery menu, Apply Update
- Apply from ADB
From the terminal on the PC
- sudo adb sideload lineage-18.1-20210506-nightly-kebab-signed.zip
If you want to install Gapps or Magisk, you must reboot to recovery. Go to advanced and choose reboot to recovery before install anything else. If you are only installing LOS you are ready to reboot to system now.
Optional, Gapps5. Sideloading Gapps.
For Android 11 I've been using NikGapps:
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.)
Remember you need to reboot to recovery once after installing LOS (as mentioned above). This does not mean you need to let LOS boot, just reboot to recovery, so that it switches slots.
In LOS recovery choose:
- Apply update
- Apply from ADB
Now in the terminal on the PC:
- sudo adb sideload NikGapps-core-arm64-11-20210501-signed.zip
- Remember between each zip file you must again hit apply from ADB.
- sudo adb sideload NikGapps-Addon-11-SetupWizard-signed.zip
LOS recovery will warn you about the zip not being signed, flash this anyways.
If you get a warning about them not being signed, choose flash anyways. If you are going to flash Magisk, move to the next section. If you don't need Magisk, reboot to system.
Very Optional, Magisk5. Sideloading Magisk.
All the devices I've tested with Android 11 have worked fine since Magisk 21.2. At this point I don't see a reason to still run the Canary builds unless you want to for some reason.
Download Magisk: [urlhttps://github.com/topjohnwu/Magisk/releases]Magisk GitHub Link[/url]
This will be flashed in LOS recovery. To get to recovery you can use the ADB (if you enable USB debugging), key combination, or the advanced restart menu, doesn't matter.
In LOS recovery choose:
- Apply update
- Apply from ADB
Now in the terminal on the PC:
- sudo adb sideload Magisk-v22.1.zip
If you get a warning about them not being signed, choose flash anyways. We should be ready to reboot to the system now.
Very Optional, Passing Safety Net6. Magisk Required.
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. My 8T passes saftey net, just choosing the 8T and Android 11 fingerprint. Also keep in mind some fingerprints will require Force basic key attestation to pass.
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:
Very Optional, Ad Blocking7. Root required.
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.
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.
You will need to use a root file explorer to copy this hosts file to /system/etc/ and replace the file that is there. I used Solid Explorer for this.
Updating Lineage
Updating Lineage is pretty much the same as installing it, just without the reset or wipe. First reboot to Lineage recovery. Doesn't matter how you get there. You can use the advanced reboot menu, or the adb.
Couple things to remember:
You will need a PC for this.
Fastboot / ADB must be updated for this to work, otherwise you will have problems.
Apply Update --> Apply From ADB
- sudo adb sideload lineage-18.1-20210506-nightly-kebab-signed.zip
If you use Gapps or Magisk, you also need to sideload these. Once again you still need to reboot recovery. Hit the back button, choose advanced, and then reboot to recovery.
Apply Update -> Apply from ADB (This must be done between each zip file)
- sudo adb sideload NikGapps-core-arm64-11-20210501-signed.zip
- sudo adb sideload NikGapps-Addon-11-SetupWizard-signed.zip
- sudo adb sideload Magisk-v22.1.zip
If you get a warning about them not being signed, choose flash anyways.
Then reboot to system. If you were using a hosts file for adblocking you will need to put that back as well when it boots. This gets replaced during the update.
Cliff Notes
Hopefully you've backed up EFS and persist partition.
Fastboot and ADB must be current version. You will have issues if they are old.
If you are using Windows remove "sudo" from the commands. This is for Linux only.
Once you install Gapps you need to continuing installing Gapps. If you want to go without Gapps after installing them, do a clean install.
Installing Lineage
sudo adb reboot bootloader
sudo fastboot flash recovery lineage-18.1-20210506-recovery-kebab.img
Apply Update --> Apply From ADB
- sudo adb sideload copy-partitions-20210323_1922.zip (assuming this is a new install) (you can skip wiping data if you are updating)
Reboot to Recovery (This option is in the Advanced Menu of LOS Recovery)
Choose factory reset, and format data (assuming this is a new install) (you can skip wiping data if you are updating)
Apply Update --> Apply From ADB
- sudo adb sideload lineage-18.1-20210506-nightly-kebab-signed.zip
If you want to sideload Gapps / Magisk you must reboot recovery now (This option is in the Advanced Menu of LOS Recovery). If you are only installing Lineage, you are ready to reboot to system.
In LOS recovery choose:
- Apply update
- Apply from ADB
Now in the terminal on the PC:
- sudo adb sideload NikGapps-core-arm64-11-20210501-signed.zip
- sudo adb sideload NikGapps-Addon-11-SetupWizard-signed.zip
- sudo adb sideload Magisk-v22.1.zip
If you get a warning about them not being signed, choose flash anyways. We should be ready to reboot to the system now.
Updating Lineage
Using LOS Recovery:
Apply Update --> Apply From ADB
- sudo adb sideload lineage-18.1-20210506-nightly-kebab-signed.zip
If you use Gapps or Magisk, you also need to sideload these. Once again you still need to reboot recovery. Hit the back button, choose advanced, and then reboot to recovery.
Apply Update -> Apply from ADB (This must be done between each zip file)
- sudo adb sideload NikGapps-core-arm64-11-20210501-signed.zip
- sudo adb sideload NikGapps-Addon-11-SetupWizard-signed.zip
- sudo adb sideload Magisk-v22.1.zip
If you get a warning about them not being signed, choose flash anyways.
Then reboot to system. If you were using a hosts file for adblocking you will need to put that back as well when it boots. This gets replaced during the update.
Woah, this is awesome, moving from my old Note 5 to a OP8T very soon (Currently in shipping, I'll have it in hand in a week or so if all goes well, very excited). This will be my first time poking around with Oneplus, or any new device for that matter (I've never dabbled in the AB system and stuff yet) and a guide like this is exactly what I need. Thank you so much!
Guide is updated, with update instructions, and cliff notes. I updated to the new build today. No issues.
For adblock you should add Adaway in there for an easier/safer option. You also get automatic host file updates then too
Very nice sir, very nice indeed!
Are these commands the same for windows?
I have been out of development for a long time. Last roms I built was Windows mobile 5. Probably around 2009. I must admit I'm a little lost in all the new terminology.
I have a T-mobile 8T+5G and SIM is unlocked and waiting on Boot loader unlock token to arrive tomorrow.
If anyone is interested in helping hold my hand through install, root etc I will gladly give a tip for your time. I have windows and and fastboot working. PM me for contact information.
bobsbbq said:
Are these commands the same for windows?
I have been out of development for a long time. Last roms I built was Windows mobile 5. Probably around 2009. I must admit I'm a little lost in all the new terminology.
I have a T-mobile 8T+5G and SIM is unlocked and waiting on Boot loader unlock token to arrive tomorrow.
If anyone is interested in helping hold my hand through install, root etc I will gladly give a tip for your time. I have windows and and fastboot working. PM me for contact information.
Click to expand...
Click to collapse
It is the same commands for windows. Just need to install the proper fastboot and adb binaries and drivers for windows (can easily be found by searching).
bobsbbq said:
Are these commands the same for windows
Click to expand...
Click to collapse
Just remove "sudo" from them. The distro I'm using requires fastboot / ADB to be run as root. Sudo obviously won't work and isn't needed in Windows. Everything else is the same.
Could you add "Revert Back to OOS from Lineage Guide" too ? Just in case people want to restore OOS !
rohanhole said:
Could you add "Revert Back to OOS from Lineage Guide" too ? Just in case people want to restore OOS !
Click to expand...
Click to collapse
This I should probably mention as this device doesn't really have an easy way to return back to stock at the moment. At least without using the MSM Tool, that I know of? At the moment you will need to use the MSM tool.
MSM / Unbrick Tool Thread <-- Instructions / Guide Included in that thread. * Remember using this tool will wipe your data, and it will relock your bootloader.
Also that is the regular 8T thread, TMobile users wanting the TMobile version would use the TMobile Thread.
jwarrior319 said:
For adblock you should add Adaway in there for an easier/safer option. You also get automatic host file updates then too
Click to expand...
Click to collapse
I'm not sure about safer? Again I'm making some assumptions I guess... I've never used Adaway, always used a hosts file. For what it's worth there is an adway add on in the NikGapps addon folder. At some point maybe I'll try and test this.
OhioYJ said:
This I should probably mention as this device doesn't really have an easy way to return back to stock at the moment. At least without using the MSM Tool, that I know of? At the moment you will need to use the MSM tool.
MSM / Unbrick Tool Thread <-- Instructions / Guide Included in that thread. * Remember using this tool will wipe your data, and it will relock your bootloader.
Also that is the regular 8T thread, TMobile users wanting the TMobile version would use the TMobile Thread.
I'm not sure about safer? Again I'm making some assumptions I guess... I've never used Adaway, always used a hosts file. For what it's worth there is an adway add on in the NikGapps addon folder. At some point maybe I'll try and test this.
Click to expand...
Click to collapse
Another way to revert back to OOS is to use the payload dumpster tool with a full ota zip and flash all the images. There's a thread already with instructions on that.
Edit: https://forum.xda-developers.com/t/guide-convert-tmo-to-global-eu-or-other-variant.4188491/
Under manually in post 1
jwarrior319 said:
Another way to revert back to OOS is to use the payload dumpster tool with a full ota zip and flash all the images. There's a thread already with instructions on that.
Edit: https://forum.xda-developers.com/t/guide-convert-tmo-to-global-eu-or-other-variant.4188491/
Under manually in post 1
Click to expand...
Click to collapse
I figured this might be possible, but I hadn't tried yet. Very helpful. MSM should always be a last resort.
I had already rooted and flashed the LOS ROM. I forgot to come back to this guide. I did not back up the persist and modem files. Is it too late for that now?
bobsbbq said:
I had already rooted and flashed the LOS ROM. I forgot to come back to this guide. I did not back up the persist and modem files. Is it too late for that now?
Click to expand...
Click to collapse
I don't think linage touch these paritions (at least not the persist one), but I might be wrong. In either case I would take a back up of persist and the modems now, as a backup from now is probably better than no backup if you get any problems later on.
Is there supposed to be F-Droid and Micro-G in the base LOS Rom? I don't have either. Sorry still trying to get use to this.
bobsbbq said:
Is there supposed to be F-Droid and Micro-G in the base LOS Rom? I don't have either. Sorry still trying to get use to this.
Click to expand...
Click to collapse
No it is not.
Got LOS installed, still does fastboot loop. Sideloaded Magisk 21.4, failed. Can't get past fastboot....hasn't booted to LOS even once
.
Anyone? No sense in trying it again until there's some feedback.
Device is NOT bricked. Can still reinstall the ROM, just will not boot to LOS...
Success!
You have to use r31.0.0 platform-tools
Linux users run commands as ROOT & add ./ before fastboot (./fastboot)
Using TWRP/unlock from [UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 3 and Fire TV Stick Lite (sheldon/p) with successfully installed OpenGapps on my Fire Stick Lite.
Needed files:
Open Gapps (Arm, 9.0, tvstock/tvmini)
gapps-config.txt (Attached Below) and edit as needed
These are the steps (guidance only! Some common sense is helpful!) if needed:
Boot into TWRP following the link attached
adb push <Download Location>/gapps-config.txt /sdcard/
adb push <Download Location>/open_gapps-arm-9.0-tv****-********.zip /sdcard/
adb shell
sheldonp:/ # twrp install /sdcard/open_gapps-arm-9.0-tv****-********.zip
sheldonp:/ # reboot or adb reboot
Install a custom launcher(Leanback on Fire recommended) and use Launcher Manager to disable stock launcher so Playstore becomes accessible
To pass Safetynet: use Magisk, Universal SafetyNet Fix and MagiskHideProps (I recommend MiBox S device fingerprint). YASNAC should return a pass!
Not working:
Google Search Voice (probably needs someone more advanced then me to figure it out)
Cast Receiver (Don't work on unregistered devices)
Android TV Launcher/TV remote (probably some accounts issue?)
To do:
Create a Magisk Module with stock Android TV boot animation
Compile tweaks/props that may be useful
Feel free to ask for help/comment!
Nice guide, thanks
Haven't had time to try it, but hopefully soon
Has anyone been able to use v4afx on 13? It keeps asking to install the drivers.
Basically you have to remove everything from V4A first like in Magisk and the app itself. After the reboot you do the installation process again with Magisk but do not open V4A yet.
Put the attached file into /data/adb/modules/ViPER4AndroidFX and overwrite it if necessairy.
Now reboot and it should work with legacy mode on.
To make it work, v4a must "patch" audio_effects.xml file, but there is a problem, because earlier androids up to OOS11 have it stored in /vendor/etc, and it patched it without problem. OOS12 and 13 have that file too in this location, but it's generic file, don't contain Dolby Atmos, Nokia Ozo processing, Dolby VQE (message enhancer), and system don't use it...
From OOS 12, oneplus decided to store and use this file in /odm partition, exactly in /odm/etc.
V4a don't have possibility to patch it, that's why it tries to install "driver" again and again.
One more info.
mount -o bind /vendor/etc/audio_effects.xml /odm/etc/audio_effects.xml from post-fs-data.sh will replace that file in odm, and yes, it will work, but it also will kill your Dolby Atmos, OZO processing, VQE, because this file in /vendor/etc don't contain them.
Thanks for the input. I will give it a shot.
Idk if u have looked thoroughly, but I made a guide to install V4A: https://forum.xda-developers.com/t/...tall-viper4android-for-oneplus-8-pro.4388799/
Instead of using these weird files and workarounds to install V4A...
I would suggest downloading DDC and kernel files which can be found on my XDA thread.
Just download them and extract the .zip file only
Then download, install V4A repackaged, reboot and done
Try installing V4A repackaged: https://github.com/programminghoch10/ViPER4AndroidRepackaged/releases
The weird file you're referring to is from dorimanx himself.
[APP] [FIX] 100% working Viper4Android for Android 10-11-12 devices
If you are someone like me who encountered countless problems while installing Viper4Android on your Android 10 or 11 device and have no idea what to do then you are in the right place. Just download and install the apk from the attachment below...
forum.xda-developers.com