Disable encryption in LineageOS20 - LineageOS Questions & Answers

Hello,
I flashed the latest Lineage recovery and LineageOS20 on my Google Pixel 5, and I'd like to disable encryption on the data partition. Is there an ADB command I can run, or file I can flash to achieve this? I also have Magisk 26.1 flashed.
I use this phone for a development project and encryption is getting in the way.
Thanks!

I'm surprised no one knows.
I wanted to go the TWRP route of formatting the data partition, but I can't get TWRP to boot when running Android 13. I need to be on Android 12 to boot TWRP successfully, but being on Android 12 means I can't flash LineageOS20 (requires Android 13), a real catch 22.
Otherwise, does anyone have a link to the latest LineageOS19.1 for Redfin? The link is broken on the LineageOS website and I can't locate that zip file on any other website.

Related

[GUIDE] Flash (almost) ANY GSI rom on Realme Q. RM5P should work too!

Original thread.
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software. *This is not entirely true for Realme devices since bootloader unlock or custom rom flash via TWRP or fastboot does not void your warranty but rooting does.
* So I heard. But that's question of detail.
* Same statement for XDA.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Update.:
As you already know development on realme devices suck beacuse of ****ty or incomplete sources, lack of developers interest and biggest reason is lack of community support.
Our man here @BabluS is a legendary developer of Asus Zenfone Max M1 Pro and is willing to compile stable ROMs for our device. But, he needs some donations to buy the device. He has already compiled Android 10 (PE) for our device which is 99% stable. To continue this tremendous work he needs to have the device in hand.
Reasons To Donate:
1. Official PixelExperience ROM
2. Official POSP ROM
3. Will maintain & provide public Device Trees/Sources (So anyone can compile ROMs)
4. More development for realme 5 Pro
Name : Baswanth Madhav Saladi
Donate Using UPI: [email protected]
Donate using Paypal : [email protected]
Send screenshots of payment to @orgasmtron
We have to reach 6-7k in total out of which we have collected 2.6k..
Keep donating & get closer to stable custom ROM experience. Kudos!
All the donations will be public.Anyone can view and verify them.All details will be transparent.
NOTE:
We will update money collection daily evening. All details will be transparent.
List of Donators will get updated here
CLICK HERE TO CHECK!
Has anybody got Android 10 working properly?
tonibm19 said:
Has anybody got Android 10 working properly?
Click to expand...
Click to collapse
Yes. Method is same.
greenys' said:
Yes. Method is same.
Click to expand...
Click to collapse
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
tonibm19 said:
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
Click to expand...
Click to collapse
Dunno. As I said I never tried Android Q. But I presume fingerprint is missing and I'm quite sure no 48mp camera is present either.
What GSI File for Realme 5 Pro
what type GSI Image for Realme 5 pro, A or AB type?
Tegarcs142 said:
what type GSI Image for Realme 5 pro, A or AB type?
Click to expand...
Click to collapse
AB. On Android 9 and above you must use AB variant. It doesn't matter whether or not does your device use seamless updates. If you try to flash A only variant your device won't boot.
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Tegarcs142 said:
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Nice. Which twrp did you use?
greenys' said:
Nice. Which twrp did you use?
Click to expand...
Click to collapse
3.3.1-0
Tegarcs142 said:
... So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Hi, can you please tell me what option you clicked for resizing the system partition?
the steps you did.
I tried doing that but don't find the option in TWRP.
For better experience with using gsi make sure to check Screenshot resolution if it's lower than our Device
Change Resolution :
1) download termux app
https://play.google.com/store/apps/d...?id=com.termux
2) run commands:
su
wm size 1080x2340
3) reboot*device
Enjoy better experience with gsi
greenys' said:
Original thread.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Click to expand...
Click to collapse
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Tarikooo said:
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Click to expand...
Click to collapse
Wth no. Idk. It's not even a gsi related thing. I have no idea sorry.
hi guys i tried flashing havoc 3.0 gsi, and it works great. which one gapps should i use?
Does fingerprint and face unlock work?
This method worked on global rm5p.
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Salmankapuas said:
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Click to expand...
Click to collapse
Don't bother with miui. Only aosp or caf.
i flashed GSI rom, pixel, OxygenOS but the system cannot boot, only stuck on boot loading screen, is that normal?? how do i fix it?

System partition is too small to install Google GSI system

Hi There!
I come to you with a request for help. Well, I wanted to install the GSI system straight from the Google website, but during the installation it turns out that my system partition is definitely too small.
Is there any way to properly install the IMG image straight from the Google site? Probably should enlarge the system partition, just HOW? I need the help of experts, and I know that at the XDA Forum I will find them.
Below you will need information:
- My device is Google Pixel XL (marlin),
- My phone supports Treble A and B updates,
- The system I wanted to install was the beta GSI Android 11 straight from the Google website,
- The recovery I used when trying to install the system: twrp-3.4.0-0-marlin.img from TWRP site,
- I also tried to install the system using CMD with ADB and fastboot,
- I have fastboot unlocked on my device,
- Information about too small partition also occurs when trying to install GSI Android 10,
- My device does not support fastbootd,
- LineageOS ZIP packages work normally and install without any errors,
- Updates from ADB sideload also load smoothly,
- Here is the link from where I got GSI Android 11 and 10: https://developer.android.com/topic/generic-system-image/releases#android-gsi-11,
I'm trying this also, credited the error to the system partition on marlin being 2gb and the system img on Google GSI being 2.1gb.
I know there's also an AOSP GSI which i downloaded from the same Google website and the image is 1.3gb if I'm not mistaken. I was able to flash this but phone wont boot. It will just bootloop on the Google with white background image and that's it.
I also tried downgrading to Android 8.1 factory image since I heard that another user got GSI Android 11 working coming from 8.1 but after trying this way I got the same bootloop error.
Solution
I was able to install Android 10 GSI on my Pixel, this method should work. You just need to reflash Android 9, see: https://forum.highonandroid.com/t/how-to-flash-android-10-gsi-roms-on-pixel-or-pixel-xl/217
I spent hours trying to figure this out but worked.

Fairphone 4 - Root

Here's a quick guide for rooting your Fairphone 4.
DISCLAIMER
I'm not the author of this method, merely sharing the informations that can be found on fairphone community forums.
All credit goes to hirnsushi from fairphone community forum.
I will not be held responsible for any damage caused by this operation, flashing your device always implies a risk of manufacturing your very own plastic brick.
PREREQUISITES
- Unlocked bootloader
- Computer with adb & fastboot
- Magisk app installed on your device
- FP4's official stock boot.img
HOW TO ROOT
1. Copy the boot.img file on your device's internal memory
2. Patch the boot.img file using Magisk -> Installation -> Patch a file
3. Transfer the patched boot.img back to your computer
4. Reboot to fastboot: Power + vol up from off device OR adb reboot bootloader
5. Boot from the patched img by running: fastboot boot patched_boot.img where patched_boot.img is actually replaced with the path and name of your patched file
DO NOT FLASH THE PATCHED IMG. BOOT ONLY.
6. Your device will take much much more time to boot than usual, be patient.
7. Once booted, open Magisk, run a direct Install and reboot.
You are now rooted.
This will break your ability to use Google Pay. Though a workaround is described below.
[OPTIONAL]- PASS SAFETYNET AND GPAY CERTIFICATION
1. Download and enable the following Magisk mod:
- Riru module
- Riru’s universal SafetyNet’s fix 2.1.2
- SQLLite for ARM aarch64 devices
- GPay SQLLite Fix 2.5
2. Enable Magisk hide and hide Magisk from the following packages:
- Google Play Store
- Google Pay
- Google Play Services
3. Now the part that is very important to follow otherwise it will not work :
- Put your phone in Airplane mode
- Clear all data from:
Google Play
Google Pay
Google Play Service: remember, clear ALL data, not just cache, even for this one
- Reboot
- Toggle Airplane mode off
You should now have a rooted device that can be used to pay for groceries. How cool is that.
If Pay app states device is not certified, there is high chances you did not follow exactly the described steps.
I really like a rooted phone as always. I will wait till there is a way to reinstall the standard ROM. Then it will be safe for me to try.
I'm on the latest update and not able to unlock the bootloader. I enabled OEM unlocking in developer options and rebooted to bootloader. On the first screen it says "Device status: Locked" and doesn't react on any fastboot command. When I enter recovery and start fastboot, each command will fail (command not present in this implementation). Any hints?
Finally managed to unlock the bootloader. The trick was to use an USB2.0 port on my PC.
I live in US so don't have one in my hands yet. Has anyone done a .QCN dump of the phone yet? Do you program the phone with Firehose EDL? Are there qualcomm drivers? I have so many questions.
I tried it with the latest boot.img avaliable here ('cause I have the A.094 ROM version on my phone)
Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation
code.fairphone.com
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
And that works perfectly, that's my daily driving phone, and no problems
Generally speaking I can only but encourage you to register and browse the fairphone forum as there are much much more resources, guides and activity around the fairphone 4 than on xda.
I'm using latest magisk 24.1 and todays OTA fails. I tried with Zygisk on and off. In the magisk app under install there is a install to new slot thing but I feel like that's supposed to be used if it don't fail. will I brick my phone if i click it?
edit:
found this on fp forum
Fixing OTA after rooting
Because my FP is rooted, I couldn’t install the update right away. Message: Couldn't update, installation problem The problem is that the boot partition gets modified when you root your phone and this prevents the OTA package from installing. It’s described well on Quora. This is how I was...
forum.fairphone.com
citroniais said:
I tried it with the latest boot.img avaliable here ('cause I have the A.094 ROM version on my phone)
Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation
code.fairphone.com
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
And that works perfectly, that's my daily driving phone, and no problems
Click to expand...
Click to collapse
My Build-Number say I am on:
FP4.FP3R.A.099.20220112
So it seems my Bootloader version should be A.099 but there is no file like this:
https://storage.googleapis.com/fairphone-source/FP4/A.099-boot.img
Is it okay to take a older boot img or another?
Latest seems to be
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
and before that:
https://storage.googleapis.com/fairphone-source/FP4/A.091-boot.img
yes I used 094 to root 099 yesterday, just don't flash the 094 or the modded 094.
I'm using latest magisk and safetynet-fix-v2.2.1, GPay.SQLite.Fix.v2.5, SQLite for ARM aarch64 devices.
Thomas.swe said:
yes I used 094 to root 099 yesterday, just don't flash the 094 or the modded 094.
Click to expand...
Click to collapse
okay, so you are on a magisk-boot-v-A.094? I thought Magisk, run a direct Install then is only able to patch your current running patched-A.094 boot.
Am I wrong?
I have rooted 099 with latest magisk 24.1 you only boot with the 094 versions to root the 099.
Thomas.swe said:
I have rooted 099 with latest magisk 24.1 you only boot with the 094 versions to root the 099.
Click to expand...
Click to collapse
Yes that it true, you are have root now.
But I think you are on the bootloader version A.094.
the 099 came from OTA so why whould bootloader be 094?
Thomas.swe said:
the 099 came from OTA so why whould bootloader be 094?
Click to expand...
Click to collapse
I am just thinking that you are on 094. Perhaps I am wrong.
But in step 5 you boot the patched 094 img and with this 094 boot image you run the direct magisk install on step 7. If I a not wrong magisk used the current running boot-image. So magisk patched your 094.
Perhaps I am wrong, I am not sure.
EDIT:
You are right @Thomas.swe Sorry for confusing.
See here: https://forum.fairphone.com/t/fp4-root-access-is-possible-maybe-a-bit-risky/76839/144
EDIT2:
@Eznaa does "our device will take much much more time to boot than usual, be patient." mean more than 20 minutes?
EDIT3:
No I used the wrong bootloader. Iode OS has its own bootloader-image upsi
I had root working using this method on A.116-boot.img. I then uninstalled Magisk, did an OTA (to A.128), did "Install Magisk to inactive Slot" (as I successfully did in older OTA updates), but it bootloops. If I `fastboot flash boot A.128-boot.img` it boots normally, but as expected, without root.
I tried an `adb wait-for-device shell magisk --remove-modules` to make sure no Magisk modules are causing the bootloop. I am on Magisk 25.1, btw.
Do you have any idea what could cause the Magisk-patched image to bootloop?
Hi,
Did you try to patch A.128 and boot on it ?
fastboot boot [image]
Please note : the best way to find an answer about any issue related to Fairphone is in the "Fairphone Community Forum" : forum.fairphone.com - The Fairphone users are not using that much XDA
I am thinking of buying Fairphone 4 and need magisk. Can anyone answer a question about the installation instructions above? Magisk website says to flash the magisk patched boot image but here the instruction is to first boot from the magisk patched image, not flash it, and then once booted run a direct install from the magisk app. What is the reason for this extra step?
Just a heads up. Root/Unlock voids FairPhone warranty unfortunately. Only reason I haven't bought this phone.

Question Installation of LineageOS for MicroG does not work

Hi all, after have lost hours and hours traying to install the latest LineageOS for MicroG, I made a facotry reset of the Oneplus 9 Pro (to Android 11), than updated de devices to the latest update (incl. Android 12 and all avaiable updates) and THAN trayed to install LineageOS for MicroG following strictly the Manual of LineageOS (link). It seams to be perfect, until the first start of LIneageOS. I see the first setup screen (Welcome to LineageOS), on the left corner "Emergency call) and on the right the START button, but the screen doesent react andt on the upper right corner I see an empty battery icon. What can I do?? I'm at the end of my knowledge.
In a step of Installing LineageOS (without MicroG) it is necessary to install the dtbo and vendor boot partitions. Maybe the problem is here?
What I have installed:
- dtbo.img (20220823)
- vendor_boot.img (20220823)
- lineage-19.1-20220820-microG-lemonadep-recovery.img
- lineage-19.1-20220824-microG-lemonadep.zip
In Recovery I see "Version 19.1 (20220824)" is installed.
PS: The volume up and down button works...
(unwanted post)
enoironline said:
Hi all, after have lost hours and hours traying to install the latest LineageOS for MicroG, I made a facotry reset of the Oneplus 9 Pro (to Android 11), than updated de devices to the latest update (incl. Android 12 and all avaiable updates) and THAN trayed to install LineageOS for MicroG following strictly the Manual of LineageOS (link). It seams to be perfect, until the first start of LIneageOS. I see the first setup screen (Welcome to LineageOS), on the left corner "Emergency call) and on the right the START button, but the screen doesent react andt on the upper right corner I see an empty battery icon. What can I do?? I'm at the end of my knowledge.
In a step of Installing LineageOS (without MicroG) it is necessary to install the dtbo and vendor boot partitions. Maybe the problem is here?
What I have installed:
- dtbo.img (20220823)
- vendor_boot.img (20220823)
- lineage-19.1-20220820-microG-lemonadep-recovery.img
- lineage-19.1-20220824-microG-lemonadep.zip
In Recovery I see "Version 19.1 (20220824)" is installed.
Click to expand...
Click to collapse
boot is equivalent to recovery
you must be on lastest official firmware
there are also spare firmware you can flash to get aligned
Psk.It said:
boot is equivalent to recovery
you must be on lastest official firmware
there are also spare firmware you can flash to get aligned
Click to expand...
Click to collapse
How can I be on latest official firmware? Before installing LIneageOS for MicroG I installed all possible Updates of the stock Version of Oneplus, than during the installation process I installed the two vendor-files as described in the manual. Do you have links to the spare firmware or better Installation guides?
enoironline said:
How can I be on latest official firmware? Before installing LIneageOS for MicroG I installed all possible Updates of the stock Version of Oneplus, than during the installation process I installed the two vendor-files as described in the manual. Do you have links to the spare firmware or better Installation guides?
Click to expand...
Click to collapse
If you installed C62 (or latest version for your device) you should be OK
(you can try reading other rom theads, some have the link to spare firmware)
for set-up, i prefer taking dtbo, vendor_boot and boot images from payload.bin file already in the rom.zip (using payload_dumper tool)
once "preliminary set-up" is done, reboot to recovery, then format data and sideload the rom
if you need extra flashing (magisk, kernel, what else) reboot recovery and sideload it
Psk.It said:
If you installed C62 (or latest version for your device) you should be OK
(you can try reading other rom theads, some have the link to spare firmware)
for set-up, i prefer taking dtbo, vendor_boot and boot images from payload.bin file already in the rom.zip (using payload_dumper tool)
once "preliminary set-up" is done, reboot to recovery, then format data and sideload the rom
if you need extra flashing (magisk, kernel, what else) reboot recovery and sideload it
Click to expand...
Click to collapse
that is certainly purposeful, but much too difficult for my most modest knowledge.
Ironically, I installed the normal LineageOS without MicroG in the meantime (to be able to use the device) and it works reasonably stable. As soon as I know what I have to install additionally when, I'll probably do again first a factory reset to the original operating system of oneplus, all updates and then I try it again with lineageos for microG. Remains to be seen what else I need to install and when :-/ It's frustrating to cannot follow an official Installation guide without having souch issues.
I can't understand why it has to be so difficult and full of detours that one can't do it if one doesn't have in-depth knowledge. Really a pity.
enoironline said:
that is certainly purposeful, but much too difficult for my most modest knowledge.
Ironically, I installed the normal LineageOS without MicroG in the meantime (to be able to use the device) and it works reasonably stable. As soon as I know what I have to install additionally when, I'll probably do again first a factory reset to the original operating system of oneplus, all updates and then I try it again with lineageos for microG. Remains to be seen what else I need to install and when :-/ It's frustrating to cannot follow an official Installation guide without having souch issues.
I can't understand why it has to be so difficult and full of detours that one can't do it if one doesn't have in-depth knowledge. Really a pity.
Click to expand...
Click to collapse
unfortunately official lineage build does not support signature spoofing, this means you need gapps (Nick gapps is the most used , you can check-out also mind-gapps)
crDroid and riceOS are a couple of roms that allow signature spoofing, you will be abile.to run micrpG on those
about payload_dumper just google it, it's a tool for unpagkage images from the a rom file
about increase of complications, we all must thank you Google 1st and OnePlus (or Oppo) in second place
Psk.It said:
for set-up, i prefer taking dtbo, vendor_boot and boot images from payload.bin file already in the rom.zip (using payload_dumper tool)
once "preliminary set-up" is done, reboot to recovery, then format data and sideload the rom
if you need extra flashing (magisk, kernel, what else) reboot recovery and sideload it
Click to expand...
Click to collapse
I'm looking right now, interesting. You wrote, you prefer taking dtbo, vendor_boot AND Boot Images from payload.bin. When to load dtbo and vendor_boot is describet in the installation guide of lineageOS, but when do you use/install the from you mentioned boot image?
enoironline said:
I'm looking right now, interesting. You wrote, you prefer taking dtbo, vendor_boot AND Boot Images from payload.bin. When to load dtbo and vendor_boot is describet in the installation guide of lineageOS, but when do you use/install the from you mentioned boot image?
Click to expand...
Click to collapse
Instead of recovery
basically:
dump payload
flash btbo
flash vendor_boot
(someone suggest to reboot in fastboot)
flash boot
from fastboot menu go to recovery
finally sideload the zip
enoironline said:
Hi all, after have lost hours and hours traying to install the latest LineageOS for MicroG, I made a facotry reset of the Oneplus 9 Pro (to Android 11), than updated de devices to the latest update (incl. Android 12 and all avaiable updates) and THAN trayed to install LineageOS for MicroG following strictly the Manual of LineageOS (link). It seams to be perfect, until the first start of LIneageOS. I see the first setup screen (Welcome to LineageOS), on the left corner "Emergency call) and on the right the START button, but the screen doesent react andt on the upper right corner I see an empty battery icon. What can I do?? I'm at the end of my knowledge.
In a step of Installing LineageOS (without MicroG) it is necessary to install the dtbo and vendor boot partitions. Maybe the problem is here?
What I have installed:
- dtbo.img (20220823)
- vendor_boot.img (20220823)
- lineage-19.1-20220820-microG-lemonadep-recovery.img
- lineage-19.1-20220824-microG-lemonadep.zip
In Recovery I see "Version 19.1 (20220824)" is installed.
Click to expand...
Click to collapse
Hey just wanted you to know that I had the exact same problem, I posted about it here:
https://www.reddit.com/r/LineageOS/comments/wyr4v9
and after a few failed attempts I basically had to hose and reset to stock with MSM (which was hard since I don't have a Win computer, but that's a solution for another day).
I think the other poster is right, you do need to flash firmware first before installing. Have you tried this? I'll try it tonight and report back, as I need to get this running before Monday.
hyve9 said:
Hey just wanted you to know that I had the exact same problem, I posted about it here:
https://www.reddit.com/r/LineageOS/comments/wyr4v9
and after a few failed attempts I basically had to hose and reset to stock with MSM (which was hard since I don't have a Win computer, but that's a solution for another day).
I think the other poster is right, you do need to flash firmware first before installing. Have you tried this? I'll try it tonight and report back, as I need to get this running before Monday.
Click to expand...
Click to collapse
Actually I have the plan to go back to Stock with MSM, than reinstall all updates of the original Oneplus 9 Pro, than reinstall the actual version of LineageOS MicroG (20220824) after dumping payload and flashing dtbo, vendor_boot and boot like psk.lt wrote.
wondering what you will accive.
Psk.It said:
Instead of recovery
basically:
dump payload
flash btbo
flash vendor_boot
(someone suggest to reboot in fastboot)
flash boot
from fastboot menu go to recovery
finally sideload the zip
Click to expand...
Click to collapse
I'm trying to dump payload. I installed the latest Python version, than downloaded payload_dumper from this link , done what described on the website and now in cmd I have the Message:
File "C:\Users\X\Desktop\Payload_dumper\payload_dumper.py", line 67
<title>payload_dumper/payload_dumper.py at master · vm03/payload_dumper · GitHub</title>
SyntaxError: invalid character '·' (U+00B7)
Do I understand it right, that the script of the tool has an error? Do you have a link of a Payload_dumper Tool that works and from where I can download it? I also found this link and in the text you can download the Tool from here , but I do not trust 100% this sources :-/
enoironline said:
I'm trying to dump payload. I installed the latest Python version, than downloaded payload_dumper from this link , done what described on the website and now in cmd I have the Message:
File "C:\Users\X\Desktop\Payload_dumper\payload_dumper.py", line 67
<title>payload_dumper/payload_dumper.py at master · vm03/payload_dumper · GitHub</title>
SyntaxError: invalid character '·' (U+00B7)
Do I understand it right, that the script of the tool has an error? Do you have a link of a Payload_dumper Tool that works and from where I can download it? I also found this link and in the text you can download the Tool from here , but I do not trust 100% this sources :-/
Click to expand...
Click to collapse
I made It! Using the tool from this website (link to the tool) I was able to extract all files. Now I can start.
Last LineageOS for MicroG Version (20220824) finaly INSTALLED (what a fight!).
Many thanks to Psk.lt and hyve9 for your help!
A quick guide for newbes like me:
Install on a PC:
- adb
- the last qualcolm driver ect
- python
download on the PC:
- MSN Tool to go back to stock OS
- payload Dumper Tool (THANK YOU PSK!!!)
- the newest LineageOS for MicroG Version
On the Oneplus 9 Pro:
- With MSN Tool back to Stock OS
- Install all possible Updates (in my device it was C61!)
- Install Oxygen Updater from an app Store or apk
- Install the REALLY last Update for your device (in my Case C62)
- download the last LineageOS for MicroG Version (.zip)
- open the .zip file and copy out the payload.bin file
Than like Psk.lt wrote, with the Payload Dumper dump the payload-file and extract btbo, vendor_boot and boot files
Safe the following files under adb
- btbo
- vendor_boot
- boot
- the lineageOS for MicroG file
Start with the installation like described in the LineageOS guide, but
- use the own btbo and vendor_boot files
- for recovery, insted of using the recovery-file from LineageOS for microG, use the boot file (extractet with Payload dumper)
- finally sideload the LineageOS for MicroG file (.zip)
End
A question: in the future can I use the oxygen Updater under LineageOS for MicroG to install all the newest updates, or does it work only if using the stock OS?
enoironline said:
A question: in the future can I use the oxygen Updater under LineageOS for MicroG to install all the newest updates, or does it work only if using the stock OS?
Click to expand...
Click to collapse
you should use embedded updater (settings - system - update) but you will not be able to copy the zip if you don't have root
If you want backup the updated zip, you should sideload via pc
enoironline said:
Last LineageOS for MicroG Version (20220824) finaly INSTALLED (what a fight!).
Click to expand...
Click to collapse
Let me know how you are liking it, im debating it or CRDroid.
ajolly said:
Let me know how you are liking it, im debating it or CRDroid.
Click to expand...
Click to collapse
I'm using LineageOS with MicroG since the End of last year and had never real problems, only the installation progress is complicated (if you follow only the official installation guides of LineageOS and from LOS-MicroG). Last week I had LineageOS without MicroG installed and I must say, I did not really missed the MicroG functions, maybe because the apps I'm using do not need necessarely the functions of MicroG / would mainly need the messaging function, but can still run and function without. It dipend what you want to accive with the OS, if you want to be compleetly G-free under LineageOS, than you have to change at your own a few more things like DNS setting, systemwebview... I can't compare LinOS-MicroG with CRDroid, beacause I never used it.
What I do not like in V 19.1 vs 18.X is the bigger format of the quick setting tiles. I know that it's possible to change it, but I have to find out how to do it in the simplest way.
A function that I miss in LineageOS (for MicroG) is a Sandbox function like in Graphene, but using Shelter helps, even if not as good as a Sandbox.
What I really don't like is the fact, that LineageOS for MicroG doesn't ships Updates with the firmware, and their Installation Guide is not really helpful (do what is described by LineageOS... and it's not really what you have to do).
What I really like is how long the battery life lasts, at least with V18 and it has surely to do with my user's habits. Now to find out how it will be under V19.1.
Over all: I like it and do not want to replace it (for now).

Development [RECOVERY][3.7.0_12-8][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support

This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too.
As always I'm not responsible for any bricked device or data loss resulting from the use of this TWRP builds. You use this at your own risk.
For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
Permanent installation is not possible with TMO stock ROM installed.
Installation overwrites all boot partition changes done previously (e.g. by Magisk or custom kernel). So you have to reflash all zips that change the boot partition after TWRP is installed.
For permanent installation, you have three options depending on your current system.
1. Option for rooted devices:
Download the twrp-installer zip
Flash it with Magisk manager or some other kernel flash utility
Reflash your custom kernel and Magisk.apk if previously installed (see example of how to install with Magisk manager below). Or alternatively flash zips in TWRP.
Don't reboot
Rename downloaded Magisk.apk to Magisk.zip
Open Magisk app
Select Modules tab
Click "Install from storage"
Select Magisk.zip
2. Option for users with other custom recoveries but without root:
Download the twrp-installer zip
Reboot to recovery
Flash it with "adb sideload twrp-installer*.zip"
Reboot to recovery
Reflash your custom kernel and Magisk.apk if previously installed
3. Option is universal:
Download boot.img
Reboot to bootloader
Run "fastboot boot boot.img" with the TWRP boot image on your PC
Go to Advanced > Flash Current TWRP
Reflash your custom kernel and Magisk.apk if previously installed
Try without installation:
Download boot.img
Reboot to bootloader
Run "fastboot boot boot.img" with the TWRP boot image on your PC
Uninstall:
Just flash the boot partition with your current ROMs boot image with the following steps.
Replace "YOUR ROM BOOTIMAGE" with the filename of the extracted boot image of your current ROM.
Reboot to bootloader
Run "fastboot flash boot_a YOUR ROM BOOTIMAGE"
Run "fastboot flash boot_b YOUR ROM BOOTIMAGE"
Alternatively you can flash your currently installed OTA zip, which overwrites boot on the unused slot, but not on the currently used one.
TWRP Updates:
Download and flash the twrp-installer zip
After that reflash your custom kernel and Magisk if previously installed
ROM Updates:
Please follow the official update instructions for your ROM!
If they give an option to update via recovery you have to substitute adb sideload commands with zip installations. Also use the "Automatically reflash TWRP after flashing a ROM" option, if you are going to install a ROM zip to preserve TWRP installation.
In case your ROM does not provide a recovery update instruction you can try to update via recovery but you are on the safe side if you follow the official instructions. They always have a reason for their particular update instructions!
Instructions that work for me (on LOS based ROMs):
Flash ROM zip with "Automatically reflash TWRP after flashing a ROM" checked
Flash your previously installed zips (custom kernel, Gapps, Magisk, etc)
Reboot to system
If Gapps packages keep crashing:
Reboot to TWRP
Flash Gapps again
Reboot to system
For OOS updates should work out of the box, but if you have issues you can follow these steps (I haven't tested them):
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
About backups/restore:
Restore data only WITHOUT pin/pattern set.
If you restore a backup made from another ROM, then the currently installed, you may have to format data. So please manually copy all contents from /sdcard to a PC or flash drive.
Backups can be made with or without pin/pattern set. It is always good practice to copy your backups to your PC or an USB drive. Also after you restored your data partition you have to reboot to system and do a second reboot to get a working system.
To make first boot faster and eliminate the need to reboot again, additionally use the step mandatory for OOS users.
If you want to copy your backup to PC, but it doesn't show up, flash change_backup_selinux_context.zip, which is available in download folder.
For OOS users:
When data is restored, you have to delete "/data/system/users/0/package-restrictions.xml" before rebooting to system.
In case you restore a backup with pin/pattern set or have some other issues I have a guide that works for me:
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
How to use MTP, adb and fastbootD:
Windows:
Install official Google USB drivers and select the right USB drivers. For MTP and adb, the WinUSB driver is sufficient on Windows 11. For fastbootD, Google drivers (Android Bootloader interface) has to be chosen.
You may have to select WinMTP for MTP and Google USB drivers for adb, if you run Windows 10.
To use adb on Windows, MTP has to be disabled with "Mount->Disable MTP" in TWRP.
Steps for choosing a specific driver (no the exact wording):
Connect phone in specific mode
Open device manager
Right click on phone either under "Android device" or "USB device", depending on mode
Select "update driver"
Select 2. option "browse my computer"
Select "pick from available drivers"
Pick driver according to above description
Linux:
Intall the fastboot and adb packages for your distribution
Set udev rules. There might be a package for your distro or use this gh repo: https://github.com/M0Rf30/android-udev-rules
Add user to the group used in udev rules. Most common are "plugdev" and "adbusers"
Source Code:
TWRP: https://github.com/TeamWin/android_bootable_recovery
Kernel: https://github.com/nilz3000/kernel_oneplus_sm8350-twrp
Device Tree:
https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
https://github.com/nilz3000/android_hardware_oplus
Bugs:
Permanent installation alongside TMO stock isn't possible
Error message regarding vendor_dlkm in fastbootD for OOS users (just cosmetic and not problematic)
In case you notice anything else please let me know.
If you encounter any bug, please give me description with logcat.txt and recovery.log output attached. You can copy those to your data folder in TWRP, if you go to Advanced->Copy Logs.
Thanks to:
@Nebrassy for the original device tree
@osm0sis for the zip installer
TWRP team
LineageOS
Thank you for this! Will try tomorrow.
Ah man this is dope. Thank you bud!!!
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...
vipinpvarghese said:
Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...
Click to expand...
Click to collapse
Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.
der_akinator said:
Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.
Click to expand...
Click to collapse
You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?
vipinpvarghese said:
You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?
Click to expand...
Click to collapse
Yes, but it was the same ROM I reinstalled after wipe.
der_akinator said:
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Click to expand...
Click to collapse
der_akinator said:
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Click to expand...
Click to collapse
Sorry i forgot about recovery log
EugenStanis said:
Sorry i forgot about recovery log
Click to expand...
Click to collapse
recovery.log
Zippyshare.com - Free File Hosting
www1.zippyshare.com
Anyone tested it with stock OOS13?
der_akinator said:
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by most Android 12 and 13 ROMs.
As always I'm not responsible any bricked device or data loss resulting from the use of this TWRP version. You use this at your own risk.
For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
Get your rom's vendor_boot image. For most ROMs this can usually be downloaded. For OOS based ROMs you can get it for example by extracting it from the official payload.bin with payload-dumper-go. A third universal option, if you have root, is to use the command "dd if=/dev/block/by-name/vendor_boot_SLOT of=/sdcard/vendor_boot.img" on your device. This writes the vendor_boot image to your sdcard folder, but you have to substitute SLOT with either a or b, depending on your currently active slot.
Reboot to bootloader.
Run "fastboot flash vendor_boot vendor_boot.img" with the TWRP vendor_boot image.
Run "fastboot boot boot.img" with the TWRP boot image.
Go to Advanced > Flash Current TWRP.
After that is done, if you were using a custom kernel, reflash it now.
If you were using magisk, reflash it now.
Reboot to bootloader.
Run "fastboot flash vendor_boot vendor_boot.img" with the ROM vendor_boot image from step one.
In the case you just want to test TWRP without installation, please skip steps 5-7.
Permanent installation works fine for me with crdroid 13 and magisk installed. I have not tested any other ROMs or custom kernels. After permanent installation you can at any time reboot to recovery without reflashing vendor_boot. During a ROM update use the "Automatically reflash TWRP after flashing a ROM" option in the install zip menu to preserve TWRP.
Source Code:
TWRP: https://github.com/TeamWin/android_bootable_recovery
Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8350
Device Tree:
https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
https://github.com/LineageOS/android_hardware_oplus
Bugs:
Please let me know. I have not encountered anything major yet.
Thanks to:
Nebrassy
TWRP team
LineageOS
Click to expand...
Click to collapse
For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.
Update
Hi everyone,
I just uploaded a new build. It fixes some missing firmware files and kernel module loading.
USB OTG, vibration and battery status is now working.
Download:
29.11.22 - Google Drive
drive.google.com
EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.
Here is a link to the github issue, maybe it helps you solving the problem.
createTarFork() process ended with ERROR: 255 when trying to back up data with multiple users · Issue #1373 · TeamWin/Team-Win-Recovery-Project
Yes, I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ (Oneplus 6) Yes, I am running the latest version of TWRP (3.2.3-1) Yes, I have read the FAQ (https://twrp.me/FA...
github.com
tnchng said:
For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.
Click to expand...
Click to collapse
I use C.63 and have not tested with other firmware versions.
der_akinator said:
Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.
Click to expand...
Click to collapse
Strange, i have never ever in my life used multiuser

Categories

Resources