[13.0][GSI][ROM][ CURTANA | JOYEUSE | EXCALIBUR][AOSP+GAPPS][25/6/23] - Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke

{
"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"
}
Code:
Disclaimer:
We are not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
What is this?
An AOSP based ROM, with gapps included and gesture support (pocket, hand wave, pickup).
Based on Android 13.0
Tested on Redmi Note 9S (curtana global) on both vendor miui 12 and miui 13
1. If you want to root then copy the stock boot from the latest stock rom into internal and use magisk to patch it, then flash the patched boot in bootloader (fastboot flash boot patched_boot.img)
2. I will try to provide monthly patch updates and fixes as needed, don't ask for ETAs... I usually aim for the 5th of each month or whenever Google releases their patches
3. If you are coming from a previous version, I highly recommend clean flashing, otherwise you will probably have issues
Bugs:
On Android 12 vendor the boot is a bit longer
I don't see any other issues, please report real issues, not feature requests from MIUI or other roms.
Getting fastbootd drivers working on windows:
1. Download these drivers and unzip
2. follow the instructions here to install the unsigned drivers
3. select the windows inf
Steps:
Please follow these steps closely!
For new installs:
1. Unlock bootloader
2. Download vbmeta from here and flash it in fastboot like this:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_note9s.img (IF YOU DONT DO THIS STEP, VOLTE AND OK GOOGLE WONT WORK!)
3. In bootloader enter: 'fastboot reboot fastboot'
4. After we reboot you will see 'fastbootd', enter 'fastboot flash system system.img' (extract the system.img and put it in the folder you're in
5. enter 'fastboot reboot recovery'
6. select format userdata
7. then select reboot to system
To upgrade from previous versions:
1. Reboot to fastbootd (adb reboot fastboot from inside android or fastboot reboot fastboot from bootloader)
2. After we reboot you will see 'fastbootd', enter 'fastboot flash system system.img' (extract the system.img and put it in the folder you're in
3. Reboot
There is now a toggle to add SuperSU on boot in Phh Settings > Misc:
Just enable it and reboot. (Keep in mind it breaks safteynet, if you need to use a banking app, disable it from settings and reboot)
Downloads:
Latest ROM
@phhusson for his work on GSI (donate to this man, he works on dozens of devices), he worked closely with me to get everything working!
Thanks to Peter Cai for getting Bluetooth stack working with a2dp on Android 13! He worked very hard on it and deserves full credit
Enjoy!
P.S.
I am not going to add any custom features from other roms so please don't comment about that!
Source: https://github.com/aosp-tissot
Phh source:Link
XDA:DevDB Information
[GSI][ROM][ CURTANA | JOYEUSE | EXCALIBUR][13.0][AOSP+GAPPS][29/08/22], ROM for the Redmi Note 9 Pro
Contributors
sooti, phhusson, peter cai
Source Code: https://github.com/aosp-tissot
ROM OS Version: Android 13
ROM Kernel: Linux 4.x
ROM Firmware Required: Treble
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2022-08-29
Created 2022-08-29
Last Updated 2022-08-29​

Change Log:
25/5/23:
* Latest trebledroid patches
* Fixed bug that caused safteynet to fail
* Added a patch that allows the device name to be shown to google store but still pass safteynet
4/5/23:
* Fixed bt calls not working
* Latest trebledroid patches
* May Google security patch
13/4/23:
* April security patch
* Latest trebledroid (phh) patches
21/3/23:
* Fixed Auto brightness not working
15/3/23:
* March security patch
9/2/23:
* Feb Security patch
* Latest Phh commits
* Fixed safteynet again
9/1/23:
* Jan security patch
25/12/22:
* Smaller gapps that are more inline with stock pixel
* Smaller image size which should help it work on smaller partitions of other devices
* Fixed IMS not working
* Fixed other props not loading at boot causing voip distortion in calls
* Fixed safteynet not passing when not rooted
11/12/22:
* Dec security patch
09/11/22:
* Merged latest phh and trebledroid patches
* November security patch
05/10/22:
* October google security patch
* Added a ton of fixes for other devices (mi a1 and other non xiaomi devices)
* Fixed xiaomi settings not showing up in treble settings
13/09/22
* Fix netflix not showing up in store (clean google play service & play store data if you are running the previous version, it might take a few minutes to show up)
* Made a better fix for Google hotword not working (Device model will show up properly now instead)
* September security patch
* Fixed permissions issue with GMS that caused crashes
* Updated some outdated prebuilt gapps
30/8/22:
* Fixed overlay to fit our punch hole correctly
* Removed the notch when in landscape

Xxxx

no vendor included...?
plz advise in op that what vendor to use.

vwong said:
no vendor included...?
plz advise in op that what vendor to use.
Click to expand...
Click to collapse
Huh? it's a GSI... you use stock vendor... read the post...

Added a new build:
Fixed the punch hole location and landscape notch showing up

I mentioned in the Android 12 last version that Google pay updated to google wallet and no longer works with contactless payments etc. I did a 'fresh' install of this, in the recovery I removed userdata and such on this device when flashing this new Android 13 version. I believe it's failing safetynet check as Netflix and such isn't showing on google play and when trying to add bank card it's still stating that this device "may be rooted or running uncertified software" I haven't turned on superSU and I haven't attempted to put magisk on this at all or patch the boot image.

McguyverZero said:
I mentioned in the Android 12 last version that Google pay updated to google wallet and no longer works with contactless payments etc. I did a 'fresh' install of this, in the recovery I removed userdata and such on this device when flashing this new Android 13 version. I believe it's failing safetynet check as Netflix and such isn't showing on google play and when trying to add bank card it's still stating that this device "may be rooted or running uncertified software" I haven't turned on superSU and I haven't attempted to put magisk on this at all or patch the boot image.
Click to expand...
Click to collapse
Can you run safteynet check? Are you using magisk? On mine it's all working , a12 vendor fails since google doesn't recognize it as certified but I put 11 vendor props to fix it

sooti said:
Can you run safteynet check? Are you using magisk? On mine it's all working , a12 vendor fails since google doesn't recognize it as certified but I put 11 vendor props to fix it
Click to expand...
Click to collapse
No Magisk at all, what's the best way to do a safetynet check?
I tried a couple safetynet apps and they all return that it is passing with no errors. Yet Netflix still isn't an app that appears in the google play store and trying to add my bank card for contactless payment when it connects to bank still returns the same problem with the uncertified software.

McguyverZero said:
No Magisk at all, what's the best way to do a safetynet check?
I tried a couple safetynet apps and they all return that it is passing with no errors. Yet Netflix still isn't an app that appears in the google play store and trying to add my bank card for contactless payment when it connects to bank still returns the same problem with the uncertified software.
Click to expand...
Click to collapse
I'm not sure sorry... if it passes it passes... sometimes netflix takes time to show up in the store... try clearing your google play store and google services data and try again... on my end everything works

sooti said:
I'm not sure sorry... if it passes it passes... sometimes netflix takes time to show up in the store... try clearing your google play store and google services data and try again... on my end everything works
Click to expand...
Click to collapse
I have been jumping in hoops, I'm not fully sure what Is going on. I keep a document of things as I've been going along so I can revert etc. I tried reflashing this again and same issue with the contactless, so I figured I would try fastboot recovery ROM from MIUI and tried 12.5.8 as that was what I OTA'd to but it was erroring with unable to parse 'super' I tried a few different roms and flashing tools, someone stated it was an issue with the fastboot etc. I just tried flashing 12.5.4 (my previous version) onto it and it's going on now as we speak 'successfully'. No idea what is going on with this 12.5.8. (The odd thing is, the update put it on to 12.5.8.0 (RJZEUXM) which was the version I have and was trying to recovery with.
Unrelated and I know it isn't 'necessary' for this but I came across a TWRP for this device? I didn't think it had TWRP support as their main website doesn't list it under devices. I didn't touch it but I was just curious.
Oh also another further question: IF we were to try Magisk is it still dependant on specific version? Thanks.

McguyverZero said:
I have been jumping in hoops, I'm not fully sure what Is going on. I keep a document of things as I've been going along so I can revert etc. I tried reflashing this again and same issue with the contactless, so I figured I would try fastboot recovery ROM from MIUI and tried 12.5.8 as that was what I OTA'd to but it was erroring with unable to parse 'super' I tried a few different roms and flashing tools, someone stated it was an issue with the fastboot etc. I just tried flashing 12.5.4 (my previous version) onto it and it's going on now as we speak 'successfully'. No idea what is going on with this 12.5.8. (The odd thing is, the update put it on to 12.5.8.0 (RJZEUXM) which was the version I have and was trying to recovery with.
Unrelated and I know it isn't 'necessary' for this but I came across a TWRP for this device? I didn't think it had TWRP support as their main website doesn't list it under devices. I didn't touch it but I was just curious.
Oh also another further question: IF we were to try Magisk is it still dependant on specific version? Thanks.
Click to expand...
Click to collapse
No, magisk works fine, just make sure to use the universal safteynet patch module to pass safteynet with magisk

sooti said:
No, magisk works fine, just make sure to use the universal safteynet patch module to pass safteynet with magisk
Click to expand...
Click to collapse
After flashing this CFW on here again it's still not working with Gpay/wallet. Safetynet passes all fine but still no netflix. I tried patching boot for magisk and redo-ing to test if anything was different, After putting the safetynet on and such it passed everything except for an "!" next to "CTS Profile Matched" but the Gpay/wallet still won't allow, Netflix still no longer there and I see Disney+ also hidden now.
I'm unsure what further to try to get Gpay working, which is annoying but not the end.

Random apps are closing themselves and most importantly my "Waze" app is refreshing itself every 10 seconds making it impossible to use.

McguyverZero said:
Random apps are closing themselves and most importantly my "Waze" app is refreshing itself every 10 seconds making it impossible to use.
Click to expand...
Click to collapse
What device are you using? curtana works fine... sounds like somethings wrong with your flashing... please provide full model details and how you flashed everything

I have Xiaomi Redmi Note 9 Pro ('Global' I THINK) codename: Joyeuse. From 12.1 I used MiFlash to flash 12.5.4.0 Stable.(RJZEUXM) to my device, I then did an OTA update pushing it to 12.5.8.0 (RJZEUXM). I put the device into fastboot (vol down + power) then using platform tools 33.r3, I did the vbmeta flash, then "fastboot reboot fastboot" to go into fastbootD to then flash the system.img provided from the google drive link in OP (dated 30/08/22), I reboot into recovery via fastboot and select the "Wipe data" function, once it is complete I reboot and then begin to setup the phone without copying any data or backups from google drive/cloud.

McguyverZero said:
I have Xiaomi Redmi Note 9 Pro ('Global' I THINK) codename: Joyeuse. From 12.1 I used MiFlash to flash 12.5.4.0 Stable.(RJZEUXM) to my device, I then did an OTA update pushing it to 12.5.8.0 (RJZEUXM). I put the device into fastboot (vol down + power) then using platform tools 33.r3, I did the vbmeta flash, then "fastboot reboot fastboot" to go into fastbootD to then flash the system.img provided from the google drive link in OP (dated 30/08/22), I reboot into recovery via fastboot and select the "Wipe data" function, once it is complete I reboot and then begin to setup the phone without copying any data or backups from google drive/cloud.
Click to expand...
Click to collapse
I'd suggest trying android 11 vendor... That should def work.. but as i said i dont have your issues.. ill try tp push a fix soon

sooti said:
I'd suggest trying android 11 vendor... That should def work.. but as i said i dont have your issues.. ill try tp push a fix soon
Click to expand...
Click to collapse
Just some additional notes as I saw there was a MIUI 13.0.1 available, Attempted to fastboot into MIUI V13.0.1.0.SJZMIXM (global), errored during super and would only bootloop, 12.5.4 or 12.5.8 wouldn't flash with miflash anymore. Worked around this by flashing Orangefox Recovery to flash Orangefox zip followed then by the V13.0.1.0.SJZEUXM ROM itself successfully.
I then decided to try out Pixel Experience as I haven't used it in years.
Pixel Experience uses it's own recovery, flashed the recovery using fastboot, wiped the data through the recovery and then patched the Pixel Experience ROM itself. Google pay seems to be working albeit I have to verify my card with my bank manually right now so hopefully that goes okay (waiting on a response right now)
As a sidenote netflix appears fine in my google play store.
So I'm unsure where the discrepency is, my apologies on posting so much but hopefully some of these help to find the issue to help myself or others in future. Thank you for all the hard work you put into this too

McguyverZero said:
Just some additional notes as I saw there was a MIUI 13.0.1 available, Attempted to fastboot into MIUI V13.0.1.0.SJZMIXM (global), errored during super and would only bootloop, 12.5.4 or 12.5.8 wouldn't flash with miflash anymore. Worked around this by flashing Orangefox Recovery to flash Orangefox zip followed then by the V13.0.1.0.SJZEUXM ROM itself successfully.
I then decided to try out Pixel Experience as I haven't used it in years.
Pixel Experience uses it's own recovery, flashed the recovery using fastboot, wiped the data through the recovery and then patched the Pixel Experience ROM itself. Google pay seems to be working albeit I have to verify my card with my bank manually right now so hopefully that goes okay (waiting on a response right now)
As a sidenote netflix appears fine in my google play store.
So I'm unsure where the discrepency is, my apologies on posting so much but hopefully some of these help to find the issue to help myself or others in future. Thank you for all the hard work you put into this too
Click to expand...
Click to collapse
OK hopefully I fixed the issue and the build that will be uploaded soon will include the following:
* Fix netflix not showing up in store (clean google play service & play store data if you are running the previous version, it might take a few minutes to show up)
* Made a better fix for Google hotword not working (Device model will show up properly now instead)
* September security patch
* Fixed permissions issue with GMS that caused crashes
* Updated some outdated prebuilt gapps
EDIT: Build is being uploaded now

I'm install android 13 GSI Rom in my Samsung Galaxy A70 can't boot direct reboot phone to download mode, Official android 13 AOSP GSI ROM have no issue in my phone boot and working well, but we don't have write permission on AOSP official ROM.

Related

[ROM][OFFICIAL][RIVER][NIGHTLIES] LineageOS 17.1

{
"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"
}
Moto G7
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
*/
Introduction:
This is the Official Lineage OS 16.0 thread for the Motorola Moto G7, codename river.
Join our Moto G7 Development Telegram Group!
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Notes:
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine with SafetyNet patcher modules, though is not supported.)
Download:
LineageOS Updater
XDA:DevDB Information
river-lineageos, ROM for the Moto G7
Contributors
erfanoabdi, SyberHexen
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2019-11-16
Last Updated 2020-08-09
Copy Partitions Zip
- courtesy @ @filipepferraz
Download
Reserved
sim card is not working
currently I use
lineage-16.0-20191118-nightly-river version
XT1962-5 (Europe/Global) model
The phone didn't detect sim card.
It is dual sim model but in any slot, didn't work.
' . ' said:
currently I use
lineage-16.0-20191118-nightly-river version
XT1962-5 (Europe/Global) model
The phone didn't detect sim card.
It is dual sim model but in any slot, didn't work.
Click to expand...
Click to collapse
Did you try removing the sim and put back in while the system is on?
SyberHexen said:
Did you try removing the sim and put back in while the system is on?
Click to expand...
Click to collapse
I did, and tried when power off as well.
The other OS versions (NOV.15, NOV.16) also showed 'No sim' state.
But after I roll back to stock rom, they are working again.
SyberHexen said:
Did you try removing the sim and put back in while the system is on?
Click to expand...
Click to collapse
And I don't know why, but on your unofficial latest Lineage os (lineage-16.0-20191001-UNOFFICIAL-river) , the sim card working well...
but on the official version, didn't work.
' . ' said:
And I don't know why, but on your unofficial latest Lineage os (lineage-16.0-20191001-UNOFFICIAL-river) , the sim card working well...
but on the official version, didn't work.
Click to expand...
Click to collapse
My last build there was with prebuilt vendor.img
This official LOS 16.0 includes a source built vendor.img
install gapps
SyberHexen said:
My last build there was with prebuilt vendor.img
This official LOS 16.0 includes a source built vendor.img
Click to expand...
Click to collapse
does anyone know where I can download the gapps, the android version is 9.1, they don't accept at https://opengapps.org/
alguien sabe donde puedo descargar las gapps, la version de android es 9.1, no aceptan en https://opengapps.org/
I am having issues with installing Lineage OS 16.0 on my G7 (XT1962-1). I'm using the file named lineage-16.0-20191118-nightly-river-signed.zip. I followed the instructions on the https://wiki.lineageos.org/devices/river/install page.
My phone's bootloader is unlocked, Developer Options are configured to allow OEM unlocking, and USB debugging. Motorola firmware version PPOS29.114-134-4 from the US Retail channel was installed. I subscribe to Google Fi.
1. I temporarily booted TWRP 3.3.1-2 using the "fastboot boot twrp-3.3.1-2-river.img" command. The file was downloaded from the TWRP URL for River. I pushed the twrp-installer-3.3.1-2-river.zip to the phone using adb and did an install zip procedure. TWRP was installed to both the a and b slots. I rebooted recovery and TWRP 3.3.1-2 launched normally.
2. In TWRP, I formatted data to remove encryption. I then wiped Dalvik/ART cache and system in the Advanced Wipe menu. I rebooted TWRP as per recommendation when formatting the data partition.
<<edit>> I did install the copy-partitions-ab.zip at this point.
3. I used the adb sideload procedure per the Lineage installation instructions for the ROM file referenced above. The installation appeared to complete normally.
4. I restarted adb sideload to install open_gapps-arm64-9.0-micro-20191119.zip which was downloaded from the opengapps.org site.
This is where things go abnormally. The open-gapps installation script starts to run and then ab-ends with error 64. The architecture doesn't match the installation file. The script reports my phone is arm, not arm64. I think we all know that the G7 hardware is arm64. So, I downloaded the open_gapps-arm-9.0-micro-20191119.zip and tried installing. That attempt generated error 70 (insufficient space in the system partition). I ran a df -k command in a terminal window in TWRP and /system is mounted with almost 3GB of space available.
I was very confused at this point, but I decided to try installing Magisk 20.1 using TWRP zip file install procedure. Interestingly, the magisk install script reported the architecture as arm (not arm64) and completed normally.
I tried to reboot the system, but TWRP warned that no OS was installed. I cancelled the reboot and did a power off.
I'm not new to LineageOS installation, I've been running LineageOS on my Nexus 6 for a couple of years. Please review the steps I've done and let me know what I'm screwing up. Thanks.
Try "fastboot -w" as formatting data in TWRP breaks boot. "No OS" warning in TWRP can be ignored
cou94114 said:
I think we all know that the G7 hardware is arm64. So...
Click to expand...
Click to collapse
Don't have this device yet myself, but to your point, Motorola has been known to put out a 32 build on 64 hardware before, and so the corresponding Lineage build was also 32. The Moto Z Play for instance.
Given your issues, it would be good to have confirmation from the OP as to what is the case with the G7.
　
cou94114 said:
I am having issues with installing Lineage OS 16.0 on my G7 (XT1962-1). I'm using the file named lineage-16.0-20191118-nightly-river-signed.zip. I followed the instructions on the https://wiki.lineageos.org/devices/river/install page.
My phone's bootloader is unlocked, Developer Options are configured to allow OEM unlocking, and USB debugging. Motorola firmware version PPOS29.114-134-4 from the US Retail channel was installed. I subscribe to Google Fi.
1. I temporarily booted TWRP 3.3.1-2 using the "fastboot boot twrp-3.3.1-2-river.img" command. The file was downloaded from the TWRP URL for River. I pushed the twrp-installer-3.3.1-2-river.zip to the phone using adb and did an install zip procedure. TWRP was installed to both the a and b slots. I rebooted recovery and TWRP 3.3.1-2 launched normally.
2. In TWRP, I formatted data to remove encryption. I then wiped Dalvik/ART cache and system in the Advanced Wipe menu. I rebooted TWRP as per recommendation when formatting the data partition.
<<edit>> I did install the copy-partitions-ab.zip at this point.
3. I used the adb sideload procedure per the Lineage installation instructions for the ROM file referenced above. The installation appeared to complete normally.
4. I restarted adb sideload to install open_gapps-arm64-9.0-micro-20191119.zip which was downloaded from the opengapps.org site.
This is where things go abnormally. The open-gapps installation script starts to run and then ab-ends with error 64. The architecture doesn't match the installation file. The script reports my phone is arm, not arm64. I think we all know that the G7 hardware is arm64. So, I downloaded the open_gapps-arm-9.0-micro-20191119.zip and tried installing. That attempt generated error 70 (insufficient space in the system partition). I ran a df -k command in a terminal window in TWRP and /system is mounted with almost 3GB of space available.
I was very confused at this point, but I decided to try installing Magisk 20.1 using TWRP zip file install procedure. Interestingly, the magisk install script reported the architecture as arm (not arm64) and completed normally.
I tried to reboot the system, but TWRP warned that no OS was installed. I cancelled the reboot and did a power off.
I'm not new to LineageOS installation, I've been running LineageOS on my Nexus 6 for a couple of years. Please review the steps I've done and let me know what I'm screwing up. Thanks.
Click to expand...
Click to collapse
try to roll back stock and install again without install 'copy-partition.zip'. I had same problem but after do that I can install it.
With latest rom, sim cards working perfectly and stable!
In particular, the microphone function is greatly improved compared to the manufacturer ROM!
Thanks!
Amazon have an "exclusive" G7 which is dual SIM and cheap for black Friday. I've seen suggestions it ships with bloatware but can be flashed with vendor's standard image. Is this the same as "river" and likely to work with official or unofficial LO 16? It may be the same as the dual sim version mentioned in previous post on this thread?
Slight problem. Im getting an error 70 while installing gapps. And attempting to resize the system partition through twrp does nothing.
This phone has been a pain in the ass with anything like this since I got it. But, I was finally able to get the rom installed and fully booted, But gapps just will not install. Even with Pico, it still says not enough space.
What am i missing? Ive never had a such a problem rooting a phone before I got into motorolas lol
crypysmoker said:
Slight problem. Im getting an error 70 while installing gapps. And attempting to resize the system partition through twrp does nothing.
This phone has been a pain in the ass with anything like this since I got it. But, I was finally able to get the rom installed and fully booted, But gapps just will not install. Even with Pico, it still says not enough space.
What am i missing? Ive never had a such a problem rooting a phone before I got into motorolas lol
Click to expand...
Click to collapse
I had the same issue. It's not the size of the partition, its the order the software is installed and the reboots done during the process. I joined the telegram group for the G7 and found some very helpful information related to the installation of LineageOS 16.0 on the G7. Here are the steps for a clean flash.
Very important - Flash the copy-partitionsAB.zip to replicate the slot A and slot B layout.
- Clean flash:
1) Put the phone in bootloader mode
1.2) Connect phone to PC with a USB cable.
1.3) In a Command prompt window, run "fastboot getvar all".
1.4) Make slot A the active slot "fastboot set_active a".
1.5) Boot TWRP "fastboot boot twrp.img" (use the file name on your PC for the TWRP img file)
1.6) check active slot in Reboot menu - set to A
2) Flash lineage zip
3) Flash twrp installer zip
3.5) Format data while in TWRP.
4) Reboot to bootloader from TWRP.
5) fastboot -w (this will wipe your userdata partition)
6) Reboot to TWRP recovery (it should be installed when you flashed the twrp-installer zip)
6.5) check active slot in Reboot menu - set to A
7) Flash opengapps zip (use the arm64 version)
7.5) Flash magisk zip (optional, only if you want root)
8) Reboot system on slot A
The G7 is my first A/B slot device and I struggled with the configuration. TWRP recovery is part of the boot partition. Installing the lineage zip, then the TWRP installer zip seems to be the required order. Then, rebooting TWRP from the installed image works to install OpenGApps. The active slot is very important, too. Many times during my installation ordeal, I would think that slot a was active, but it was slot b. I installed the copy-partitions zip when we were made aware of no bootloader on slot b a few weeks ago.
Good luck.
To install gapps successfully, reboot twrp after installing lineageos:
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload lineage-16.0-20191122-nightly-river-signed.zip
* adb reboot bootloader
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload open_gapps-arm64-9.0-nano-20191121.zip
In other news: Does NFC work for anyone?
reddich said:
To install gapps successfully, reboot twrp after installing lineageos:
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload lineage-16.0-20191122-nightly-river-signed.zip
* adb reboot bootloader
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload open_gapps-arm64-9.0-nano-20191121.zip
In other news: Does NFC work for anyone?
Click to expand...
Click to collapse
I don't see a step to flash twrp installer. Do you permanently install twrp in your procedure?
Awesome. Thank you guys. Looks like the main problems I was having are not fastboot -w and not rebooting fully into twrp to flash gapps. After flashing the twrp installer and rebooting, I would get a totally different recovery. I've rooted hundreds of phones, but these a/b phones seems to just be a huge pain in the patooty.
---------- Post added at 09:17 AM ---------- Previous post was at 09:08 AM ----------
reddich said:
To install gapps successfully, reboot twrp after installing lineageos:
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload lineage-16.0-20191122-nightly-river-signed.zip
* adb reboot bootloader
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload open_gapps-arm64-9.0-nano-20191121.zip
In other news: Does NFC work for anyone?
Click to expand...
Click to collapse
These phones do not have NFC capabilities.

BlackShark3S ROM or Recovery do you have? [Resolved!]

I know it's out of place, but I'm posting here because it's not registered this device with XDA. Forgive me.
I have a BlackShark 3S, but I can't update it because it broke Recovery.:crying:
Therefore, BlackShark 3S Full OTA or Recovery dump is required.
If you have it, would you please share it?
Thank you for reading.
Try the following:
1. Unlock bootloader (if not already) https://forum.xda-developers.com/t/blackshark-3-3-pro-3s-unlock-bootloader-files.4141537/
2. Download https://pan.ydxby.com/刷机包/黑鲨3/KLEN2009280CN00MQ3.zip?preview
3. Get Fastboot https://developer.android.com/studio/releases/platform-tools
4. Flash my fixed (updated with new bs3 and 3s kernel) TWRP from the attachment (fastboot flash recovery_a *Link to the downloaded TWRP image* and fastboot flash recovery_b *Link to the downloaded TWRP image*)
5. Boot to recovery (fastboot reboot recovery/fastboot boot *Link to the downloaded TWRP image*)
6. (recommended, not necessary) wipe all partitions in TWRP/Factory data reset/format as F2FS (updated it)
7. plug Phone to computer, copy the KLEN2009280CN00MQ3.zip from 2. to internal storage
8. install the zip in TWRP
9. (optional) after install, reboot to fastboot and flash TWRP again (if you don't do that you will have stock recovery)
10. boot the system
Other option:
instead of 2. Find the exact rom you have on your device https://pan.ydxby.com/刷机包/黑鲨3/
4. Extract the payload https://forum.xda-developers.com/t/guide-payload-bin-install-ota-zip-without-twrp.3865319/
5. install the recovery by fastboot flash recovery_a *Link to recovery.img* and fastboot flash recovery_b recovery.img
11. Tell me if sth worked for you so the next one with this problem sees
12. never buy a phone from someone who does not provide official stock ROM downloads/bootloader unlock again.
Sorry xda was not allowing me to upload for whatever invisible reasons. it seems to have worked after 200 attempts but 7z is not allowed (its smaller xda!) so i renamed to .zip. Just rename it back to KLEN2009280CN00MQ3TWRP_3.4.2B_repack.7z and extract it....
Hi @wertus33333
I saw it now.
I'll try it now.
12. never buy a phone from someone who does not provide official stock ROM downloads/bootloader unlock again.
Click to expand...
Click to collapse
That's really true.They also don't provide source code of linux kernel. (You are also mentioned here. https://forum.xda-developers.com/t/...l-and-up-to-date-china-rom-downloads.4197717/)
I was saved because you were there. Thank you.
koumaza said:
...
I was saved because you were there. Thank you.
Click to expand...
Click to collapse
Happy to help. So it worked out?
wertus33333 said:
Try the following:
1. Unlock bootloader (if not already) https://forum.xda-developers.com/t/blackshark-3-3-pro-3s-unlock-bootloader-files.4141537/
2. Download https://pan.ydxby.com/刷机包/黑鲨3/KLEN2009280CN00MQ3.zip?preview
3. Get Fastboot https://developer.android.com/studio/releases/platform-tools
4. Flash my fixed (updated with new bs3 and 3s kernel) TWRP from the attachment (fastboot flash recovery_a *Link to the downloaded TWRP image* and fastboot flash recovery_b *Link to the downloaded TWRP image*)
5. Boot to recovery (fastboot reboot recovery/fastboot boot *Link to the downloaded TWRP image*)
6. (recommended, not necessary) wipe all partitions in TWRP/Factory data reset/format as F2FS (updated it)
7. plug Phone to computer, copy the KLEN2009280CN00MQ3.zip from 2. to internal storage
8. install the zip in TWRP
9. (optional) after install, reboot to fastboot and flash TWRP again (if you don't do that you will have stock recovery)
10. boot the system
Other option:
instead of 2. Find the exact rom you have on your device https://pan.ydxby.com/刷机包/黑鲨3/
4. Extract the payload https://forum.xda-developers.com/t/guide-payload-bin-install-ota-zip-without-twrp.3865319/
5. install the recovery by fastboot flash recovery_a *Link to recovery.img* and fastboot flash recovery_b recovery.img
11. Tell me if sth worked for you so the next one with this problem sees
12. never buy a phone from someone who does not provide official stock ROM downloads/bootloader unlock again.
Click to expand...
Click to collapse
Thanks a lot! Working perfect!
Some comments what I found:
- After flashing ROM, safety net fails, all points
- Rooting without any problem
- Magisk Hide working well for that apps wich doesn't work if detect root
- Smali Patch not working for spoofing in PoGo
- I used this method because after unlock mi BS3S couldn't even once, login into google account, now can login anytime
Still have to find the way to make smali patch works, but at now looks fine
Thanks again
LuigiHacks said:
Thanks a lot! Working perfect!
Some comments what I found:
- After flashing ROM, safety net fails, all points
- Rooting without any problem
- Magisk Hide working well for that apps wich doesn't work if detect root
- Smali Patch not working for spoofing in PoGo
- I used this method because after unlock mi BS3S couldn't even once, login into google account, now can login anytime
Still have to find the way to make smali patch works, but at now looks fine
Thanks again
Click to expand...
Click to collapse
Happy to have helped,
-Maybe safety net fails bcs its CN beta rom
-If you only need location spoof you could try enabling dev options and selecting a mock location app from aurora-/playstore/F-droid no idea if it works with PoGo tho
to further optimize the ROM you could disable some of the bloatware with a magisk system app disabler.
would also be quite interesting if GSI's work (so we would have multilanguage support on nice interfaces with newest CN firmware...) but i filled that 256GB and backups take ages without USB3.0 xD
wertus33333 said:
Happy to have helped,
-Maybe safety net fails bcs its CN beta rom
-If you only need location spoof you could try enabling dev options and selecting a mock location app from aurora-/playstore/F-droid no idea if it works with PoGo tho
to further optimize the ROM you could disable some of the bloatware with a magisk system app disabler.
would also be quite interesting if GSI's work (so we would have multilanguage support on nice interfaces with newest CN firmware...) but i filled that 256GB and backups take ages without USB3.0 xD
Click to expand...
Click to collapse
Hello my friend, you deserved a cold beer
I flashed back KLEN2009280CN00MQ3, flash noverity zip, root magisk, smali patcher + spoofing signature, full Google apps and now everything works perfect, sing in all my accounts, magisk by passing safety net and spoofing PoGo without issues. Really thanks for your help.
One last question, do you know how to lock apps working in background and holding his reference in the notification bar? (Even when you release memory closing apps) it's for the joystick that am using.
Regards
LuigiHacks said:
Hello my friend, you deserved a cold beer
I flashed back KLEN2009280CN00MQ3, flash noverity zip, root magisk, smali patcher + spoofing signature, full Google apps and now everything works perfect, sing in all my accounts, magisk by passing safety net and spoofing PoGo without issues. Really thanks for your help.
One last question, do you know how to lock apps working in background and holding his reference in the notification bar? (Even when you release memory closing apps) it's for the joystick that am using.
Regards
Click to expand...
Click to collapse
nice.
so you want the app to stay active in background? remove it from battery optimizations (not sure if cleaning recents will still clean it but the system won't stop it)
also check the app permissions of the apps you want to keep in notification bar maybe there is an option somewhere
safety net passed in beta
{
"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"
}
And I recommend litegapps
LiteGapps
Download LiteGapps for free. LiteGapps is a custom gapps which is ,small, friendly and complete. LiteGapps is an Custom Gapps for smartphones, tablet, desktop, free and open-source software. by providing complete, stable support and several additional features.
sourceforge.net
It works systemless xD
koumaza said:
And I recommend litegapps
LiteGapps
Download LiteGapps for free. LiteGapps is a custom gapps which is ,small, friendly and complete. LiteGapps is an Custom Gapps for smartphones, tablet, desktop, free and open-source software. by providing complete, stable support and several additional features.
sourceforge.net
It works systemless xD
Click to expand...
Click to collapse
i recommend no gapps most apps "requiring" play services work perfectly without (they are telling different stories tho xD) and there is aurorastore
I've seen it, it's awesome!
Unfortunately, I need a Google Play license, so I'll use both.
And I just tried it, and the app is amazingly complete!
I will now use the aurora store to manage my apps.
Thanks for the post. Just got my BS 3S, i would like to root it and debloat most of the apps. Also is there any way to change the launcher? I tried in the settings, default apps, it says cant set because the launcher that Im trying to use is not allowed my JOYUI, Im trying Nova and Lawnchair 2. Thanks
I tried in the settings, default apps, it says cant set because the launcher that Im trying to use is not allowed my JOYUI, Im trying Nova and Lawnchair 2
Click to expand...
Click to collapse
Try installing and using quickswitch with magisk.
Then you can change the SystemUI native launcher.
Also, CustoMIUIzer is an interesting app so please try it.
koumaza said:
Try installing and using quickswitch with magisk.
Then you can change the SystemUI native launcher.
Also, CustoMIUIzer is an interesting app so please try it.
Click to expand...
Click to collapse
My BS 3S is not yet rooted, can you guide me?
hello can update
Download https://pan.ydxby.com/刷机包/黑鲨3/KLEN2009280CN00MQ3.zip?preview ??
Can't download now
iampatricktan said:
My BS 3S is not yet rooted, can you guide me?
Click to expand...
Click to collapse
I write the method I performed.
First, one thing to keep in mind is that the BlackShark 3 and 3S are partially compatible.
1. Unlock Bootloader.
Follow This Thread.
BlackShark 3/3 Pro/3S unlock bootloader files.
This unlocking method was researched by myself, so I bought two machines to study it. I know that many Chinese can unlock the Bootloader, but they are unwilling to announce it. They charge high unlock fees to unlock for users in need. This is...
forum.xda-developers.com
2. Flash Magisk from TWRP
TWRP-LINK: https://mega.nz/folder/KU8DTZhR#M2YjCHUrmupBkovTam2HtQ
If you don't know what to do for, please ask me.

[ROM][12.1][OnePlus 5/5T] AOSP for OnePlus 5 [07 JULY 2022]

AOSP for OnePlus 5/5T - Android 12
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it!
*/
Most of the information from here can be applied for this ROM.
Introduction
This projects aims to create an upgradable AOSP build system for the Oneplus 5 (Cheeseburger).
No repository from AOSP is changed: no commit over AOSP is at the moment present on the sources for this ROM.
All the changes are provided in separate repositories (HALs, kernel): this allows to upgrade Android with minimal effort, potentially also for future major versions.
Most of the added repositories is provided by LineageOS or CAF, so thanks to them for those repos.
Screenshots are attached.
This ROM is based on the work on Android 11 from here: https://forum.xda-developers.com/t/...-19-september-2021-locked-bootloader.4183691/
As usual, only builds with enforcing SELinux, no root access and 'user Android build flavor' will be posted here.
Known issues
- None that I'm aware of.
Changelog
See second post.
Download
Releases can be found on AndroidFileHost.
OnePlus 5 (Cheeseburger): https://androidfilehost.com/?w=files&flid=328726
OnePlus 5T (Dumpling): https://androidfilehost.com/?w=files&flid=328820
Installation
Backup everything.
The provided zip can be installed using the TWRP recovery: clear data while doing that.
The ROM expects the firmware from OOS 10.0.1: different firmwares are not tested.
The provided recovery allows only flashing signed images: use TWRP if you need to flash GApps or different packages.
Sources
Kernel on github: https://github.com/robertoglandroid/kernel_oneplus_msm8998
ROM sources: https://github.com/roberto-sartori-gl/local_manifests/tree/a12/gl
Telegram discussion group here!
XDA:DevDB Information
AOSP for OnePlus 5/5T, ROM for the OnePlus 5/5T
Contributors
robertogl
Thank you to @T1mb3 and @Maitreya29!
ROM OS Version: Android 12
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2021-10-05
Last Updated 2022-07-07
Changelog
[07/07/2022] aosp12_cheeseburger/dumpling-ota-user-20220707.zip
July2022 Security patches (synced with AOSP android-12.1.0_r10)
[08/06/2022] aosp12_cheeseburger/dumpling-ota-user-20220608.zip
June 2022 Security patches (synced with AOSP android-12.1.0_r8)
[21/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220521.zip
Support f2fs formatted /cache partition
Synced with Lineage 19.1 sources
Minor fixes
Code cleanup
[15/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220515.zip
Add option to apply OTA updates from SettingsExtra
4 files can be installed:
the ROM OTA - put the zip in /sdcard/update.zip
magisk - put the zip in /sdcard/magisk.zip
gapps - put the zip in /sdcard/gapps.zip
decryption zip - put the zip in /sdcard/decrypt.zip
The device will reboot automatically in recovery and apply the updates. Only TWRP can install magisk, gapps or the decryption zip.
Fix crash of the Settings app while configuring fingerprint or PIN lock (during the first setup, or from the Settings page)
Add possibility to enable location indicator in the Development Options
Location indicator is disabled for the Phone Services
[03/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220503.zip
May 2022 Security patches (synced with AOSP android-12.1.0_r5)
Fix issue with Led Manager (SettingsExtra)
[04/04/2022] aosp12_cheeseburger/dumpling-ota-user-20220404.zip
April 2022 Security patches (synced with AOSP android-12.1.0_r4)
Fix slow unlock when fingerprint is used
[13/03/2022] aosp12_dumpling-ota-user-20220313.zip
Fix Settings app crash when opening fingerprint settings
[08/03/2022] aosp12_cheeseburger/dumpling-ota-user-20220308.zip
Android 12L
March 2022 Security patches (synced with AOSP android-12.1.0_r1)
Fix time and date not persisted after a reboot/factory reset
Fix vibration level setting on SettingsExtra
[01/03/2022] aosp12_cheeseburger/dumpling-ota-user-20220301.zip
Sync with Lineage 19 source
Fix issue with sim2 (data works also on sim2 now)
Fix Pocket Mode
Fix 'issue' that was causing some apps to detect root without Magisk
[08/02/2022] aosp12_cheeseburger/dumpling-ota-user-20220208.zip
February 2022 Security patches (synced with AOSP android-12.0.0_r29)
Fix Jio issues with VoLTE calls
[04/01/2022] aosp12_cheeseburger/dumpling-ota-user-20220104.zip
January 2022 Security patches (synced with AOSP android-12.0.0_r26)
Fix alarms not working with default Clock app
[07/12/2021] aosp12_cheeseburger/dumpling-ota-user-20211207-beta.zip
December Security patches (synced with AOSP android-12.0.0_r16)
[02/11/2021] aosp12_cheeseburger/dumpling-ota-user-20211102-beta.zip
November Security patches (synced with AOSP android-12.0.0_r13)
Add separate wifi and cellular data quick settings tiles (as Android 11)
Unified Android 12 tile is still present
[25/10/2021] aosp12_cheeseburger/dumpling-ota-user-20211025-beta.zip
Add f2fs support on /data partition
[20/10/2021] aosp12_cheeseburger/dumpling-ota-user-20211020-experimental.zip
Add support for OnePlus 5T (Dumpling)
Fix data on SIM1 (SIM2 is not working for data in this release)
Enable switch for default mobile data between SIM1 and SIM2 directly in the Android Settings (removed tile: less code to mantain)
Grant permissions to Play Store (and some Google apps) automatically - allow to setup the device and restore a backup at first boot
Fix TWRP not booting after flashing Android 12
Now recovery is not updated/overwritten anymore (no need for the persist_twrp mod or anything - installed recovery is persisted)
Vibration and alarm icons are back in the status bar
[09/10/2021] aosp12_cheeseburger-ota-user-20211009.zip
Fix encryption - Now File Based Encryption is enabled by default
Fix SIM1 sometimes not being recognized at boot
Fix an issue that caused Android to being stuck at boot sometimes (e.g. after flashing it the first time)
Add 'SIM Data Switch' tile to allow switching the default SIM used for mobile data
[06/10/2021] aosp12_cheeseburger-ota-user-20211006-alpha.zip
First release: October 2021 Security Patch (synced with AOSP android-12.0.0_2)
Only known issue is encryption not working
Booting with locked bootloader
This ROM can be booted with locked bootloader.
Not supported at the moment.
For more info, refer to the A11 thread (the information are the same):
[ROM][11.0][OnePlus 5] AOSP for OnePlus 5 [06 OCTOBER 2021][Locked bootloader]
New build in the first post: aosp_cheeseburger-ota-user-20201205.zip Changelog: Add option to enable Call Recording - available in the Settings Extra app Add battery level on the bluetooth icon on status bar (when a bluetooth device reports a...
forum.xda-developers.com
Reserved3
Gapps android 12 here
Added to the OnePlus 5 Index Thread here.
Sources are now available here: https://github.com/roberto-sartori-gl/local_manifests/tree/a12/gl
New release: aosp12_cheeseburger-ota-user-20211009.zip
Changelog:
Fix encryption - Now File Based Encryption is enabled by default
Fix SIM1 sometimes not being recognized at boot
Fix an issue that caused Android to being stuck at boot sometimes (e.g. after flashing it the first time)
Add 'SIM Data Switch' tile to allow switching the default SIM used for mobile data
So, this release fixes encryption: I only plan to support builds with encryption enabled, so if you flashed the first A12 release (without encryption), you'll need to format /data or disable encryption somehow (I don't provide support for this, sorry, but there should be some flashable zips).
This is the last time that formatting /data will be require, I promise!
This also means that if you have my A11 ROM (linked in the first post) you can actually update to A12 without losing any data (app included). But this is still a beta release, so at your risk!
Roms works fine for the most part. I'm not sure if i'm even supposed to test different browsers but chrome and kiwi browser end up crashing when downloading heavy files (> 100Mb)
work on device decrypted and twrp?
hello, there's some problem with the rom and the phone. i accidentaly rebooted in recovery and it stays stuck on logo screen and wont go over, also force rebooting it will always go into twrp and wont boot anyway. tried also to update to lastest recovery verison, but result it'S also the same. any solution or fix for this? p.s.: at the first flash, the rom booted fine.
kitamurt said:
hello, there's some problem with the rom and the phone. i accidentaly rebooted in recovery and it stays stuck on logo screen and wont go over, also force rebooting it will always go into twrp and wont boot anyway. tried also to update to lastest recovery verison, but result it'S also the same. any solution or fix for this? p.s.: at the first flash, the rom booted fine.
Click to expand...
Click to collapse
What logo? Android animation, oneplus logo, or Android recovery logo?
morfances said:
work on device decrypted and twrp?
Click to expand...
Click to collapse
The ROM only supports encrypted /data, but there should be some zip on XDA to manage decryption (I never tested that though).
robertogl said:
What logo? Android animation, oneplus logo, or Android recovery logo?
The ROM only supports encrypted /data, but there should be some zip on XDA to manage decryption (I never tested that though).
Click to expand...
Click to collapse
it stays stuck on twrp logo, but i can go to fastboot mode also and reboot, but the system wont boot anyway. it will only boot automatically into twrp, but i cant make anything since it stays stuck on twrp logo. i followed the steps above, bootlaoder already unlocked, formatted data, then flashed rom and gapps, eventually rebooted.
kitamurt said:
it stays stuck on twrp logo, but i can go to fastboot mode also and reboot, but the system wont boot anyway. it will only boot automatically into twrp, but i cant make anything since it stays stuck on twrp logo. i followed the steps above, bootlaoder already unlocked, formatted data, then flashed rom and gapps, eventually rebooted.
Click to expand...
Click to collapse
What TWRP are you using? TWRP should boot as it should not depend on the OS.
robertogl said:
What TWRP are you using? TWRP should boot as it should not depend on the OS.
Click to expand...
Click to collapse
i'm using the official twrp downloaded from the website, version 3.5.2. what doesn't add up is the reason why the recovery boots and stays stuck on the logo. so it's really weird. i also tried to boot the twrp from adb, giving the command "fastboot boot twrp.img", but the result it's the same.
kitamurt said:
i'm using the official twrp downloaded from the website, version 3.5.2. what doesn't add up is the reason why the recovery boots and stays stuck on the logo. so it's really weird. i also tried to boot the twrp from adb, giving the command "fastboot boot twrp.img", but the result it's the same.
Click to expand...
Click to collapse
Try booting this: https://androidfilehost.com/?fid=10763459528675599801
robertogl said:
Try booting this: https://androidfilehost.com/?fid=10763459528675599801
Click to expand...
Click to collapse
that worked, thx. but seems that the "signed twrp" can't recognize encrypted data, indeed when asking for pattern/pin, even entering it correctly, will say that isn't recognized and therefore data is not recognized. so normal twrp can't be used for flash this kind of rom and gapps?
kitamurt said:
that worked, thx. but seems that the "signed twrp" can't recognize encrypted data, indeed when asking for pattern/pin, even entering it correctly, will say that isn't recognized and therefore data is not recognized. so normal twrp can't be used for flash this kind of rom and gapps?
Click to expand...
Click to collapse
For sure current TWRP cannot decrypt data as they need to be updated to support A12.
But at least you can flash/format things now.
I'm not sure why your TWRP didn't work, the signature should not be important (I shared that because it was already uploaded).
well, thanks for the advice! that said, the bugs i've encountered so far are:
-wifi very buggy, it disconnects after a while and the signal it's very poor, after it's disconnected it can't reconnect to any network. this is solved by rebooting the device
-random crash of systemui, especially when pressing the settings button
-twrp 3.5.2 not booting after flash the rom, only the signed_twrp will work (but not decrypt data) and allow to flash other things
kitamurt said:
well, thanks for the advice! that said, the bugs i've encountered so far are:
-wifi very buggy, it disconnects after a while and the signal it's very poor, after it's disconnected it can't reconnect to any network. this is solved by rebooting the device
-random crash of systemui, especially when pressing the settings button
-twrp 3.5.2 not booting after flash the rom, only the signed_twrp will work (but not decrypt data) and allow to flash other things
Click to expand...
Click to collapse
- The networking is a bit broken apparently, I already had different report of this. We are working on fixing this.
- This happens when you open the settings button from the Quick Settings view, right? It is broken also on A11, it should work only if you have a PIN/fingerprint configured (for some reason).
- TWRP will need to be updated to support A12 encrypted, yes
Of course, thanks for reporting these issues! Always appreciated, as I cannot test everything by myself

[ROM][Android 13][UNOFFICIAL][OTA] LineageOS 20.0 for Xiaomi Mi A2 Lite [daisy]

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
- Selinux is enforcing
- FBE build, don't use twrp for these builds
- Custom kernels are NOT supported
- Read the instructions carefully
Downloads
- Here
Flashing instructions
- Here (Suggestions for improving the guide are welcome)
Sources:
- LineageOS
- Kernel Tree
Happy modding!
Reserved
Good news
Great!
Okay but does it run Crysis?

			
				
Stonks

			
				
I upgraded from 18.1 to 19.1. I just used the 18.1 recovery instead of flashing the 19.1 recovery. It worked fine.
Update: Apparently I spoke too soon. After turning the phone off and on again, it won't boot

			
				
a1291762 said:
I upgraded from 18.1 to 19.1. I just used the 18.1 recovery instead of flashing the 19.1 recovery. It worked fine.
Update: Apparently I spoke too soon. After turning the phone off and on again, it won't boot
Click to expand...
Click to collapse
Yeah, thx for reporting this, apparently i've just uploaded a build with privapp permissions broken
for now you can use some old build i made https://abhiramshibu.tuxforums.com/~saalim/giovanni/daisy/lineage-19.1-20220319-UNOFFICIAL-daisy.zip
i should upload a new one as soon as possible (maybe tomorrow/today)

			
				
Its_Vixano said:
Yeah, thx for reporting this, apparently i've just uploaded a build with privapp permissions broken
Click to expand...
Click to collapse
I poked at it some more. I seemingly cannot start the Lineage recovery anymore? It just ... boots into Lineage after a delay, but Lineage can't boot. I dunno if this is related to privapp or not
All of these do the same thing:
* Hold up when booting
* Hold down when booting then fastboot reboot recovery
* Hold down when booting then fastboot boot lineage-recovery.img
This isn't my daily driver so I'll get creative to try and restore it, or just blow it away
My recovery process:
* Boot into TWRP
* Flash Lineage 18.1
* Boot into (Lineage 18.1) recovery
* Install Lineage 19.1
* Boot into (Lineage 19.1) recovery
* Flash Gapps and Magisk
* Boot into system

			
				
a1291762 said:
I poked at it some more. I seemingly cannot start the Lineage recovery anymore? It just ... boots into Lineage after a delay, but Lineage can't boot. I dunno if this is related to privapp or not
All of these do the same thing:
* Hold up when booting
* Hold down when booting then fastboot reboot recovery
* Hold down when booting then fastboot boot lineage-recovery.img
This isn't my daily driver so I'll get creative to try and restore it, or just blow it away
Click to expand...
Click to collapse
Avoid using the 'fastboot boot' command, somehow it doesn't works
instead flash it directly into the boot partition 'fastboot flash boot lineage-recovery.img' and try to boot into the recovery

			
				
Its_Vixano said:
instead flash it directly into the boot partition 'fastboot flash boot lineage-recovery.img' and try to boot into the recovery
Click to expand...
Click to collapse
That didn't work for me even the first time - which is why I used the Lineage 18.1 recovery to flash the 19.1 zip.

			
				
a1291762 said:
That didn't work for me even the first time - which is why I used the Lineage 18.1 recovery to flash the 19.1 zip.
Click to expand...
Click to collapse
It should work, but sometimes it takes a couple of tries with reboots in between. I did not find a pattern yet, but in general flashing boot and doing the power vol+ combo should be fine. Maybe it's a timing thing, not sure. Try to switch which button you press first maybe, or try to press them at the exact same time. A bit weird, yeah
UPDATE: pressing the + button just a bit earlier seems to be doing the trick for me!

			
				
just done a test build for fixing the privapp permission issues (random bootloops caused by some normal reboots), seems fine here but i don't really trust my self
https://abhiramshibu.tuxforums.com/~saalim/giovanni/daisy/lineage-19.1-20220329-UNOFFICIAL-daisy.zip
report if something will be wrong with it
edit: Apparently it's fine so
New update released (20220329) (Checkout op for download link)
- Sync with latest lineageos changes
- Fix random bootloopos while rebooting

			
				
Its_Vixano said:
New update released (20220329) (Checkout op for download link)
- Sync with latest lineageos changes
- Fix random bootloopos while rebooting
Click to expand...
Click to collapse
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed

			
				
a1291762 said:
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed
Click to expand...
Click to collapse
Yep, that's the right way to update the rom

			
				
I have an old CrDroid rom on the phone
It is time to upgrade to a new and better 18.1 or 19.1 (the more stable is?).
I read the thread, but now I need to know and follow the correct procedure to avoid errors. I use Fdroid and Adway as adblock. Is Magisk necessary? Should the switch between the two A / B partitions always be done during installation or for updates?
Thanks to who will answer

			
				
nabav said:
I have an old CrDroid rom on the phone
It is time to upgrade to a new and better 18.1 or 19.1 (the more stable is?).
I read the thread, but now I need to know and follow the correct procedure to avoid errors. I use Fdroid and Adway as adblock. Is Magisk necessary? Should the switch between the two A / B partitions always be done during installation or for updates?
Thanks to who will answer
Click to expand...
Click to collapse
- Just follow the instructions, everything is written here
- Should be stable enough for daily driving it, sadly i don't use daisy anymore as a 'primary' device
- I also use fdroid and adaway and they don't require root

			
				
a1291762 said:
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed
Click to expand...
Click to collapse
Hi a1291762,
is the above an alternative method to go from Lineageos 18.1 to Lineagos 19.1 or should the original procedure from Its_Vixano be used? If it is an upgrade procedure rather than an update procedure (are those to be expected at all?) can you give a more detailed explanation? I have TWRP 3.5.2_9.2 and Magisk on my phone, however, TWRP should not be used for flashing 19.1 because of FBE build (what's that?). Does your procedure work with fastboot or adb? Whatsoever, though it is not my daily driver I am very happy with my Mi A2 Lite with TWRP and Magisk but I also like playing... (with 75 years).
Thanks for all of your efforts!
grufty47

			
				
grufty47 said:
is the above an alternative method to go from Lineageos 18.1 to Lineagos 19.1 or should the original procedure from Its_Vixano be used?
Click to expand...
Click to collapse
The OP guide seems to be written for people coming from something other than Lineage. The first part of it sets up the Lineage recovery and formats user data.
Since I was coming from Lineage and already had the recovery, I figured I could skip those steps. The OP guide says you can skip formatting data if you're coming from Lineage and I figured the recovery can't have changed too much.
I don't know how much testing was done for a Lineage 18 -> 19 upgrade. It worked for me but I barely had anything installed when I did it. Make backups in case of data loss and all that.
Something I don't understand in the OP guide is the suggestion to use the copy_partitions script. It only seems useful if your phone is somehow in an odd situation where miscellaneous A and B partitions don't match? It can't hurt to run it I guess.
grufty47 said:
can you give a more detailed explanation?
Click to expand...
Click to collapse
My 18->19 upgrade process matches the 19 "OTA" process. Refer to the OP guide for screenshots and details.
1. Boot to recovery
2. Sideload the lineage zip
3. Reboot to recovery (changes the active slot)
4. Sideload gapps
5. Sideload Magisk
The lineage zip is like a "full OTA" for the stock ROM. Flashing it overwrites system, boot and vendor, hence the need to flash gapps and magisk again. But the recovery only supports flashing to the current slot, hence the reboot in the middle.
grufty47 said:
I have TWRP 3.5.2_9.2 and Magisk on my phone, however, TWRP should not be used for flashing 19.1 because of FBE build (what's that?).
Click to expand...
Click to collapse
FBE has to do with encryption. I found this that might help explain it.
https://www.reddit.com/r/LineageOS/comments/hd534a
Booting TWRP 3.5.2_9.2 (fastboot boot twrp.img) shows only garbage names under /sdcard plus a bunch of other places (but not all of /data). So I guess TWRP doesn't support FBE encryption? I'm not sure why that matters for flashing system partitions, but if any of lineage, gapps or magisk expects to write to places covered by FBE then clearly that's not going to work properly under TWRP.
Since you have installed TWRP over the Lineage recovery, you'll have to get a Lineage recovery back on your phone before you can upgrade. Using the provided recovery should work I guess? If not, you could use TWRP to flash the most recent Lineage 18 zip, which will also replace TWRP with Lineage recovery. Part of the reason I attempted the 18->19 upgrade in the first place is because I couldn't get the provided recovery to boot on my phone.
I hope that helps.
Lincoln

			
			
			
			
			
			
			
			
			
			



			

			
		

	
		

			
[ROM][13.0][OnePlus 7T Pro][OFFICIAL] crDroid v9.5 [20230620]
			
			
			
				
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features
Installation/Update Instructions:
From official ROM Android 12 to crDroid 9
From official ROM Android 11 to crDroid 9
From crDroid 8 (or other custom ROM) to crDroid 9
Installing crDroid 9 updates
Sources:​ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8150
Common Device tree: https://github.com/crdroidandroid/android_device_oneplus_sm8150-common
Device tree: https://github.com/crdroidandroid/android_device_oneplus_hotdog
Vendor Common Device tree: https://github.com/crdroidandroid/proprietary_vendor_oneplus_sm8150-common
Vendor Device tree: https://github.com/crdroidandroid/proprietary_vendor_oneplus_hotdog
Download:​crDroid ROM
Recovery Image
OnePlus 7T Pro firmware
GAPPS: Already Included
Known issues:​Tell me
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
crDroid OnePlus 7T Pro (hotdog) Telegram group

			
				
From official ROM Android 12 to crDroid 9
Spoiler: Click to expand...
Pre-installation:
Download latest recovery image and latest crDroid 9 firmware (Download)
Installation:
1) Backup your data to PC, OTG flash drive...
2) Unlock the bootloader (Instruction)
3) Enter to fastboot mode (With the device powered off, hold Volume Up + Volume Down + Power).
4) Flash our recovery in both slot:
Code:
fastboot flash recovery_a <recovery_filename>.img
fastboot flash recovery_b <recovery_filename>.img
5) Reboot to installed recovery
Code:
fastboot reboot recovery
6) Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
7) On recovery main page tap Apply update -> Apply from ADB
Now sideload <rom_filename>.zip using command:
Code:
adb sideload <rom_filename>.zip
If getting message Signature verification failed click Yes. You'll see process stuck on 47%, Don't worry you'll get Success message just wait.
8) Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.

			
				
From official ROM Android 11 to crDroid 9
Spoiler: Click to expand...
Pre-installation:
Download latest vendor firmware, recovery image and latest crDroid 9 firmware (Download)
Installation:
1) Backup your data to PC, OTG flash drive...
2) Unlock the bootloader (Instruction)
3) Enter to fastboot mode (With the device powered off, hold Volume Up + Volume Down + Power).
4) Unpack vendor firmware zip file. We go into the unpacked folder and run the Update-firmware.sh file (if you have Linux installed) or Update-firmware.bat (if you have Windows) from the Administrator account. We follow the instructions of the installer step by step and make sure that everything is done without errors. At the end of the script program, the phone will reboot into recovery mode.
After the first start of recovery, the screen will not perceive pressing the screen. To navigate through the menu, use the volume buttons and the Power button to confirm the selection.
5) Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
6) On recovery main page tap Apply update -> Apply from ADB
Now sideload <rom_filename>.zip using command:
Code:
adb sideload <rom_filename>.zip
If getting message Signature verification failed click Yes. You'll see process stuck on 47%, Don't worry you'll get Success message just wait.
7) Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.

			
				
From crDroid 8 (or other custom ROM) to crDroid 9
Warning:
People ask the question: "Is it possible to update crDroid 8 firmware to crDroid 9 while keeping the data"? Yes it is possible. But, after the update, there may be problems with some programs or the system. Therefore, I highly recommend doing a "clean" install.
Spoiler: Click to expand...
Pre-installation:
Download latest vendor firmware, recovery image and latest crDroid 9 firmware (Download)
Installation:
1) Backup your data to PC, OTG flash drive...
2) Enter to fastboot mode (From system: Restart... -> Bootloader. Or with the device powered off, hold Volume Up + Volume Down + Power).
3) Unpack vendor firmware zip file. We go into the unpacked folder and run the Update-firmware.sh file (if you have Linux installed) or Update-firmware.bat (if you have Windows) from the Administrator account. We follow the instructions of the installer step by step and make sure that everything is done without errors. At the end of the script program, the phone will reboot into recovery mode.
After the first start of recovery, the screen will not perceive pressing the screen. To navigate through the menu, use the volume buttons and the Power button to confirm the selection.
4) (You can skip this step if you decide to save the data) Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
5) On recovery main page tap Apply update -> Apply from ADB
Now sideload <rom_filename>.zip using command:
Code:
adb sideload <rom_filename>.zip
If getting message Signature verification failed click Yes. You'll see process stuck on 47%, Don't worry you'll get Success message just wait.
6) Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.

			
				
Installing crDroid 9 updates
If for some reason OTA update is not possible. The data will be saved.
Spoiler: Click to expand...
Pre-installation:
Download latest crDroid 9 firmware (Download)
Installation:
1) Backup your data to PC, OTG flash drive...
2) Reboot system into Recovery mode (From system: Restart... -> Recovery. Or with the device powered off, hold Volume Down + Power.).
3) On recovery main page tap Apply update -> Apply from ADB
Now sideload <rom_filename>.zip using command:
Code:
adb sideload <rom_filename>.zip
If getting message Signature verification failed click Yes. You'll see process stuck on 47%, Don't worry you'll get Success message just wait.
6) Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.

			
				
Reserved5

			
				
in the next update, if possible, would love to see dolby/opcam
eagerly waiting to install . thanks a lot for andoid 13 <3

			
				
On android 12 when i unlock i am losing widevine L1.
ON android 11 when i unlock it is retained.
Damn the new vendor blobs.
i just flashed back to oos11 and unlocked while retaining widevine L1.
Would it be possible to retain L1 and flash Crdroid 9 when on android 11 without the new vendor blobs?
Is anybody else facing this issue?
iv'e tried 2 upgrade paths. from oos11 and oos12.
Only when unlocking on oos11 i can retain L1.
alternatively is there a way to unlcok bootloader on A12 and retain widevine L1?
thanks so much for your work... been excitedly waiting for crdroid 9.

			
				
Had latest Android 11.
Followed instruction `from Android 11 to crDroid 9`.
Everything went fine except mobile data. Couldn't connect. Wifi only.
I guess there's a problem in a modem.
Any thoughts?

			
				
vsm778 said:
Had latest Android 11.
Followed instruction `from Android 11 to crDroid 9`.
Everything went fine except mobile data. Couldn't connect. Wifi only.
I guess there's a problem in a modem.
Any thoughts?
Click to expand...
Click to collapse
I had the same problem on some rom need to modify point access and change some parameters like delete user/pass, proxy etc..

			
				
Thetimelost said:
I had the same problem on some rom need to modify point access and change some parameters like delete user/pass, proxy etc..
Click to expand...
Click to collapse
ill just stay on crdroid 8 for a bit longer, im rooted and have all my favourite magisk modules. Plus i'm waiting for some crdroid 8 features to get transferred to crdoird 9 (like OOS Camera, dolby atmos, etc.).

			
				
Anyone with auto brightness problem? Mine is going crazy sometimes. Everything is normal and suddenly "boom" - screen is going brighter and I must manually dimm it.

			
				
vsm778 said:
Had latest Android 11.
Followed instruction `from Android 11 to crDroid 9`.
Everything went fine except mobile data. Couldn't connect. Wifi only.
I guess there's a problem in a modem.
Any thoughts?
Click to expand...
Click to collapse
just goto sim settings and reset access points and mobile data will start working. i was going crazy for 2 days thinking something is wrong with ROM.

			
				
===== 20221107 =====
* Added: Allow disabling clipboard overlay
* Added: Hidden network support for hotspot
* Added: Connected devices manager for hotspot
* Added: More DNS providers to private DNS
* Added: Long press to copy wifi password
* Added: Show more APK details on App info screen
* Launcher: some more small changes here and there as well as fixes
* Enable split notification shade in landscape
* Some more improvements to hotspot
* Fixed possible SIM issues with non-dual sim variants
* Removed notification clear all icon/bg styles (useless)
* Added wireguard support
* Reworked bootanimation
* Rebased Updater
* Updater: corrected changelog URL
* Updated Aperture (Camera)
* Updated libcore
* Updated translations
* Many Fixes and Improvements
>> Download link <<
or OTA update
================
Donate for my work

			
				
When I install this my touchscreen stops working. How do I fix this?
Crdroid 8 was working perfectly.

			
				
FalKoopa said:
When I install this my touchscreen stops working. How do I fix this?
Crdroid 8 was working perfectly.
Click to expand...
Click to collapse
You missed the "Firmware" step

			
				
chuckiler said:
On android 12 when i unlock i am losing widevine L1.
ON android 11 when i unlock it is retained.
Damn the new vendor blobs.
i just flashed back to oos11 and unlocked while retaining widevine L1.
Would it be possible to retain L1 and flash Crdroid 9 when on android 11 without the new vendor blobs?
Is anybody else facing this issue?
iv'e tried 2 upgrade paths. from oos11 and oos12.
Only when unlocking on oos11 i can retain L1.
alternatively is there a way to unlcok bootloader on A12 and retain widevine L1?
thanks so much for your work... been excitedly waiting for crdroid 9.
Click to expand...
Click to collapse
is there any way to get widevine L1 working with the A12 vendor blobs?
has anyone suceesfully retained L1 while updating A12 vendor blobs?

			
				
chuckiler said:
is there any way to get widevine L1 working with the A12 vendor blobs?
has anyone suceesfully retained L1 while updating A12 vendor blobs?
Click to expand...
Click to collapse
It's since the oos12 and cos12 CBT came out that I unlock both and I still have widevine L1.
And so are 99% of users.
You are doing something wrong

			
				
Can anyone please tell me if this ROM passes safetynet and banking apps can be used as well?

			
				
After trying all available A13 ROMs for my 7T pro ..... I must say this is the most stable, most fluid ROM with best battery backup.
But PE excels in particular 2 fields i.e. audio(you can easily distinguish between each instrument playing in background) output quality and display calibration(if you have the eyes to see the difference of finer tuning of each spectrum). Though the difference is really negligible.
I think in overall score this ROM beats PE. Soooo fluid I can't believe it !!!
Thanks dev for this awesome stable ROM.
I'll again come back to this ROM in future builds to see if these two fields are also set above par.
Again I can't thank enough for this awesome ROM.

			
			
			
			
			
			
			
			
			
			

			
		

	
	
	



	
	







			

		



		

			
Categories

			
		


		

			
Resources