[ROM][12][OFFICIAL][GUACAMOLE]KOSP 2.2 - OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D

Code:
/*
* DISCLAIMER: Read this carefully
* 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.
*/
{
"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"
}
KOSP is a small project based off AOSP and we intend to improve upon AOSP to provide a stable and better alternative to OEM roms with additional features.
Features
There are some cool features, see for yourself
Truth is I'm just lazy to write a long list of features and we intend to focus on the stability rather than adding a ton of features.
Gapps is included!
Note:
guacamole has dropped sdcardfs
We are enforcing and safety net passes out of the box
What's broken?
You tell me
Bug reporting:
DO NOT report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Do not approach us without any logs for reporting bugs
If it is a random reboot, grab everything from /sys/fs/pstore. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Downloads: GDrive, Sourceforge
Magisk: https://github.com/topjohnwu/Magisk/releases
INSTRUCTIONS
First time installation:
Download the fastboot zip, It ends with -img.zip.
Boot to bootloader
fastboot update --skip-reboot --skip-secondary zipname
Now reboot to recovery
Factory reset in the recovery
Reboot system
Upgrading:
It is recommended to update using updater
Via recovery:
Reboot to recovery
Sideload with ADB (preferred)
Reboot to recovery
Reboot
Via updater app:
Open Settings -> System -> KOSP Updater
Download the ota if available or if you have already downloaded the zip then use it for local upgrade
Install the update
Flash magisk to inactive slot (optional)
(optional) Reboot to recovery if you have anything else to flash
Reboot
Follow us on Telegram
Credit/Thanks:
Google for AOSP
LineageOS
YAAP
DerpFest
MSM-Xtended
And all others we may have forgotten to credit
Special thanks to @npv12 and also to @AnnoyingZlatan for his amazing kernel.
Thanks to @Mohammed_Gabr for making our awesome banner.
Last but not the least, thanks to all our testers, who have helped us to squash many bugs as possible
XDA:DevDB Information
KOSP, ROM for the OnePlus 7 Pro
Contributors: @Joker123##, @npv12
Device maintainer: @npv12
ROM source: https://github.com/AOSP-Krypton
ROM Kernel: Dora kernel
Kernel source: https://github.com/AOSP-Krypton/kernel_oneplus_sm8150
ROM Firmware Required: OOS 11.0.4.1
Android Version: 12
Based On: AOSP
Version Information
Version: 2.2
Status: Beta
Created 2021-10-31
Last Updated 2021-12-18

Reserved

Reserved

Code:
sudo fastboot update --skip-reboot --skip-secondary KOSP-2.0-guacamole-user-OFFICIAL-GAPPS-20211031-1701-img.zip
[sudo] password for username:
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: redacted
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'msmnile'.
Update requires 'OnePlus7Pro'.
fastboot: error: requirements not met!
Edit: zip downloaded from the "GDrive" link. I guess changing
Code:
board=OnePlus7Pro
to
Code:
board=msmnile
in android-info.txt should work?
Edit 2: yes, it worked.

I cannot sideload Magisk with built-in recovery. I keep getting
Code:
Finding update package...
Verifying update package...
E: footer is wrong
Update package veridication took 0.1 s (result 1).
E:Signature verification failed
E:error: 21
Install from ADB completed with status 2.
Installation aborted.
I tried with 23.0 and latest Canary, same. Anyone else?
Edit: patching boot.img works just fine of course, I'm just curious as to why built-in LOS recovery doesn't allow me to sideload any Magisk zip file. Usually it asks if I want to skip the verification check and the process is successful.

When I try to cast to my tv it will immediately go into a reboot. I included a logcat if it helps, I tried to attach a copy of it but I cant seem to get it to stick
https://drive.google.com/file/d/1q4oT4LIYnIRs-KRaOGlyc_WHIsVwVERx/view?usp=sharing

Works great! thanks to the developer!
camera and gallery from stock OOS worked.
google pay probably works, at least it doesn't display any security breaches.
google pay is broken.
for the first assembly, the result is excellent!

Do I have to be on 11.0.3.1?
Can it be a higher version of OOS?

Toutatis_ said:
Code:
sudo fastboot update --skip-reboot --skip-secondary KOSP-2.0-guacamole-user-OFFICIAL-GAPPS-20211031-1701-img.zip
[sudo] password for username:
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: redacted
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'msmnile'.
Update requires 'OnePlus7Pro'.
fastboot: error: requirements not met!
Edit: zip downloaded from the "GDrive" link. I guess changing
Code:
board=OnePlus7Pro
to
Code:
board=msmnile
in android-info.txt should work?
Edit 2: yes, it worked.
Click to expand...
Click to collapse
Can confirm this works for me aswell

Sadly i can't seem to be able to install chrome on this. It's complaining about missing dependencies. Anyone know why this could be? All other stuff works fine. Even stock OOS camera (with all camera's) and Gallery work!
Edit: After a reboot it seems to install fine!

Small little issue. States "Charging Slowly" yet it charges fast. Nothing major. Otherwise so far i'm really impressed. Everything seems to work perfectly including L1 Widevine.

So far so good after the first day, very smooth ROM. The fingerprint sensor feels much faster and accurate than any of the 10 and 11 custom ROMs I've used.
Rand0mGuyy said:
Do I have to be on 11.0.3.1?
Can it be a higher version of OOS?
Click to expand...
Click to collapse
Don't quote me on this but I think it doesn't matter. 11.0.3.1 is required but if you're on 11.0.4.1 it shouldn't be an issue.

When playing the game, switching back to the desktop and returning to the game, there will be abnormalities, broken sound, screen freezes, and dropped frames

en-joy said:
google pay is broken.
Click to expand...
Click to collapse
No, it works. Don't forget to switch NFC on.
Do it using quick switch only! Switch in the settings doesn't work.
Update: sorry, doesn't work.

Fingerprint scanner does not work on AOD. It does when the phone wakes.

Toutatis_ said:
I cannot sideload Magisk with built-in recovery. I keep getting
Code:
Finding update package...
Verifying update package...
E: footer is wrong
Update package veridication took 0.1 s (result 1).
E:Signature verification failed
E:error: 21
Install from ADB completed with status 2.
Installation aborted.
I tried with 23.0 and latest Canary, same. Anyone else?
Edit: patching boot.img works just fine of course, I'm just curious as to why built-in LOS recovery doesn't allow me to sideload any Magisk zip file. Usually it asks if I want to skip the verification check and the process is successful.
Click to expand...
Click to collapse
How to install the magisk root ?I already patch the boot.img with magisk manager, then reboot to bootloader to boot that patched boot.img. after that i've seen the ramdisk is said "no" . then i choose to direct install as alwyas. and its error it say cannot find target image.
edit :
I use command "fastboot flash boot bootpatched.img" instead of "fasboot boot" and use direct install from the app

Dhimas97 said:
How to install the magisk root ?I already patch the boot.img with magisk manager, then reboot to bootloader to boot that patched boot.img. after that i've seen the ramdisk is said "no" . then i choose to direct install as alwyas. and its error it say cannot find target image.
edit :
I use command "fastboot flash boot bootpatched.img" instead of "fasboot boot" and use direct install from the app
Click to expand...
Click to collapse
I don't know, that's exactly what I did too and it worked as expected. I patched the boot.img with Magisk 23.
I guess you cannot sideload it via built-in recovery either, just like me? an alternative method is to flash the zip with apps such as EX Kernel Manager or Franco Kernel Manager (paid apps), I used the former to flash latest Magisk canary and it worked just fine.
Nevermind, you obviously need root for this. Silly me

I cannot install chrome from playstore

Dhimas97 said:
I cannot install chrome from playstore
Click to expand...
Click to collapse
sideload it then. Apkmirror.com

Phantom Thief said:
sideload it then. Apkmirror.com
Click to expand...
Click to collapse
I'll try now..
Thanks for the adivice, i dont know why i click on the install button it keep flash to "intall" after i click it in split seccond
edit : i'm good now, its installed

Related

[ROM][12][OFFICIAL][HOTDOGB]KOSP 2.2

Code:
/*
* DISCLAIMER: Read this carefully
* 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.
*/
{
"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"
}
KOSP is a small project based off AOSP and we intend to improve upon AOSP to provide a stable and better alternative to OEM roms with additional features.
Features
There are some cool features, see for yourself
Truth is I'm just lazy to write a long list of features and we intend to focus on the stability rather than adding a ton of features.
Gapps is included!
Note:
hotdogb has dropped sdcardfs
We are enforcing and safety net passes out of the box
What's broken?
You tell me
Bug reporting:
DO NOT report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Do not approach us without any logs for reporting bugs
If it is a random reboot, grab everything from /sys/fs/pstore. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Downloads: GDrive, Sourceforge
Magisk: https://github.com/topjohnwu/Magisk/releases
INSTRUCTIONS
First time installation:
Download the fastboot zip, It ends with -img.zip.
Boot to bootloader
fastboot update --skip-reboot --skip-secondary zipname
Now reboot to recovery
Factory reset in the recovery
Reboot system
Upgrading:
It is recommended to update using updater
Via recovery:
Reboot to recovery
Sideload with ADB (preferred)
Reboot to recovery
Reboot
Via updater app:
Open Settings -> System -> KOSP Updater
Download the ota if available or if you have already downloaded the zip then use it for local upgrade
Install the update
Flash magisk to inactive slot (optional)
(optional) Reboot to recovery if you have anything else to flash
Reboot
Follow us on Telegram
Credit/Thanks:
Google for AOSP
LineageOS
YAAP
DerpFest
MSM-Xtended
And all others we may have forgotten to credit
Special thanks to @npv12 and also to @AnnoyingZlatan for his amazing kernel.
Thanks to @Mohammed_Gabr for making our awesome banner.
Last but not the least, thanks to all our testers, who have helped us to squash many bugs as possible
XDA:DevDB Information
KOSP, ROM for the OnePlus 7T
Contributors: @Joker123##, @npv12
Device maintainer: @npv12
ROM source: https://github.com/AOSP-Krypton
ROM Kernel: Dora kernel
Kernel source: https://github.com/AOSP-Krypton/kernel_oneplus_sm8150
ROM Firmware Required: OOS 11.0.4.1
Android Version: 12
Based On: AOSP
Version Information
Version: 2.2
Status: Beta
Created 2021-10-31
Last Updated 2021-12-18
Reserved
Woah? Andorid 12 already? Pretty fast. Any screenshots/feature list of the ROM?
Edit: found some in the tg channel, looks cool.
Amazing....thanks so much...
Is nfc payment working fine?
Do I have to install recovery after installing the -img.zip? (Which recovery?)
Hey, so I just wanted to confirm, do I need a custom recovery for this or will the commands in the install instructions flash a recovery, sorry if this is a very basic question!
Ayush Neek said:
Hey, so I just wanted to confirm, do I need a custom recovery for this or will the commands in the install instructions flash a recovery, sorry if this is a very basic question!
Click to expand...
Click to collapse
It'll include Los type recovery for sideloading. Also change txt file in zip to "msmnile" if "fastboot update kosp.zip" doesn't flash due to device mismatched
srizodiac said:
Do I have to install recovery after installing the -img.zip? (Which recovery?)
Click to expand...
Click to collapse
Above
HueyT said:
It'll include Los type recovery for sideloading. Also change txt file in zip to "msmnile" if "fastboot update kosp.zip" doesn't flash due to device mism
Click to expand...
Click to collapse
HueyT said:
It'll include Los type recovery for sideloading. Also change txt file in zip to "msmnile" if "fastboot update kosp.zip" doesn't flash due to device mismatched
Click to expand...
Click to collapse
Do i change the android info text to msmnile or do i change the contents inside?
gillim74 said:
Do i change the android info text to msmnile or do i change the contents inside?
Click to expand...
Click to collapse
Content inside device=msmnile
HueyT said:
Content inside device=msmnile
Click to expand...
Click to collapse
I tried that still failed.
HueyT said:
Content inside device=msmnile
Click to expand...
Click to collapse
This is what stock one says...board=OnePlus7T so i changed it to board=msmnile and it failed.
gillim74 said:
This is what stock one says...board=OnePlus7T so i changed it to board=msmnile and it failed.
Click to expand...
Click to collapse
fastboot update rom.zip
(Coming from oos11)
Make sure u downloaded the img zip:
https://sourceforge.net/projects/kosp/files/A12/hotdogb/KOSP-2.0-hotdogb-user-OFFICIAL-GAPPS-20211031-1628-img.zip/download
Per kosp telegram:
Peeps getting this error with fastboot update:
Checking 'product' FAILED
Device product is 'msmnile'.
"Unzip the zip file. Change the board=whatever_it_is to board=msmnile inside android-info.txt file. Save the file, repack it to the zip and then continue with the same command"
HueyT said:
Per kosp telegram:
Peeps getting this error with fastboot update:
Checking 'product' FAILED
Device product is 'msmnile'.
"Unzip the zip file. Change the board=whatever_it_is to board=msmnile inside android-info.txt file. Save the file, repack it to the zip and then continue with the same command"
Click to expand...
Click to collapse
I did that but it still fails.i just fastboot flashed each partition.do you know what the super_empty img is.thats the only thing that wouldnt flash
gillim74 said:
I did that but it still fails.i just fastboot flashed each partition.do you know what the super_empty img is.thats the only thing that wouldnt flash
Click to expand...
Click to collapse
Skip that and userdata
HueyT said:
Skip that and userdata
Click to expand...
Click to collapse
Ok cool.any way you can share your zip if you gotta to flash through fastboot update command? I wouod really appreciate it!! Did they make a a12 for the 5g mclaren? I know your alot more active than me so i figured id ask.
gillim74 said:
Ok cool.any way you can share your zip if you gotta to flash through fastboot update command? I wouod really appreciate it!! Did they make a a12 for the 5g mclaren? I know your alot more active than me so i figured id ask.
Click to expand...
Click to collapse
https://sourceforge.net/projects/kosp/files/A12/hotdogb/KOSP-2.0-hotdogb-user-OFFICIAL-GAPPS-20211031-1628-img.zip/download
Op7t only

[ROM][13.0]CherishOS-4.2[UNOFFICIAL][Oneplus 8]

{
"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"
}
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS.
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
WHAT WORKS?​Everything.
KNOWN ISSUES:
U tell me?
DO NOT FLASH GAPPS, ALREADY INCLUDED
DOWNLOADS​DOWNLOAD LINKS BELOW:
ROM - Click
TELEGRAM - https://t.me/CherishOS8P
INSTRUCTIONS​First Time Install / Clean Flash
1. Have an unlocked bootloader & be on the latest OOS 12 (C33-C36)
2. Download copy_partitions, vbmeta, recovery, and rom for your device from here
3. Reboot to bootloader
4. fastboot flash recovery recovery.img
- fastboot flash vbmeta vbmeta.img
- fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload copy_partitions.zip
7. adb sideload rom.zip (replace "rom" with actual filename)
8. Format data, reboot to system
Update / Dirty Flash
1. Reboot to recovery
2. adb sideload rom.zip (replace "rom" with actual filename)
3. Reboot to system
SOURCE
Android version: 13.0.0
Security patch level: November 2022
Kernel Source: https://github.com/LineageOS/android_kernel_oneplus_sm8250
NOTE: ROM is now based on OOS12 fw. Do not try to dirty flash from 3.9. Follow fresh install instructions.
Dirty flash is fine if coming from version 4.0
reserved
Awesome!!!
Enjoy op8 peeps!!
another one? less goo!!!! more to test!
Can I flash this using twrp?
ac386 said:
Can I flash this using twrp?
Click to expand...
Click to collapse
Nope.. twrp is not fully functional for A12. Use the recovery mentioned in the thread.
it says package is for instant noodle but expected instantnoodlep
harrysingh87 said:
it says package is for instant noodle but expected instantnoodlep
Click to expand...
Click to collapse
I have updated recovery link in op. Use that
kumar akarsh said:
I have updated recovery link in op. Use that
Click to expand...
Click to collapse
I did, new recovery, but same error
harrysingh87 said:
I did, new recovery, but same error
Click to expand...
Click to collapse
Sorry I had posted wrong one. Try now. This will work
that error gone, now it says update error 21, error code: : kdownloadinvalidmetadatamagicstring
harrysingh87 said:
that error gone, now it says update error 21, error code: : kdownloadinvalidmetadatamagicstring
Click to expand...
Click to collapse
I'm on one plus 8
[email protected] platform-tools % ./adb sideload chs.zip
serving: 'chs.zip' (~0%) adb: failed to read command: Undefined error: 0
harrysingh87 said:
[email protected] platform-tools % ./adb sideload chs.zip
serving: 'chs.zip' (~0%) adb: failed to read command: Undefined error: 0
Click to expand...
Click to collapse
Maybe try using recovery from arrow os thread. I don't know why you are facing this issue. I do not have this device to test but the person who tested the ROM on op8 did not face any issue in sideloading
kumar akarsh said:
Maybe try using recovery from arrow os thread. I don't know why you are facing this issue. I do not have this device to test but the person who tested the ROM on op8 did not face any issue in sideloading
Click to expand...
Click to collapse
ok. will try that too. it only Sideload official rom. all other Roms give error.
harrysingh87 said:
ok. will try that too. it only Sideload official rom. all other Roms give error.
Click to expand...
Click to collapse
ahhh, finally got it. Figured out the mail reason - Macbook was unpacking the zip every time I downloaded. I re zipped all the Roms. now I uncheck that option and all is well. Thanks for timely replies. I posted first time here, but ur response time was awesome. Thanks , loading....
Trying to flash this and getting a message in recovery that it was expecting instantnoodle p but got instantnoodle. I am on an IN2017 it shows as that in device info. Not sure what I'm doing wrong. I am using the linked recovery.
kumar akarsh said:
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS.
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
WHAT WORKS?​Everything.
KNOWN ISSUES:
U tell me?
DO NOT FLASH GAPPS, ALREADY INCLUDED
DOWNLOADS​DOWNLOAD LINKS BELOW:
ROM - click
RECOVERY - click
TELEGRAM - https://t.me/CherishOS8P
INSTRUCTIONS​FLASHING INSTRUCTIONS :-
USE PLATFORM TOOLS FOR ADB AND FASTBOOT COMMANDS
1. Download recovery provided here
2. Reboot to bootloader and flash recovery
'fastboot flash recovery recovery.img'
'fastboot reboot recovery'
3. Select apply update/apply from ADB
4. Connect device to PC
5. Sideload rom.zip
'adb sideload rom.zip'
6 Do Factory reset/format data from recovery
7. Restart to system
*If need to root - sideload magisk V23.0 from recovery (AFTER FIRST BOOT)
SOURCE
Android version: 12.0_r27
Security patch level: January 2022
Kernel Source: https://github.com/Chris-kona-A12/kernel_oneplus_sm8250
ROM Source: https://github.com/CherishOS
CREDITS
@sauaditi & @Swp1996 for support in resolving build issues
Chris for device trees
@tejkumarvusirikala for testing build for oneplus 8
Click to expand...
Click to collapse
no verizon/visible support, beware
please help, when trying to flash Magisk it gives error 21

Development [ROM][13][UNOFFICIAL] ArrowOS 13 for Realme GT Neo2 5G

{
"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"
}
ArrowOS​
Code:
/*
* We are 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 us for messing up your device, We will laugh at you.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
ABOUT
ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.
PayPal: Donate to me
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me (need to be reproducable + include logs)
Be sure to include a log : check how to
HOW TO FLASH
* Reboot to TWRP
* Flash ArrowOS zip with adb sideload or USB OTG
* Flash magisk (optional)
* Format data
* Reboot to system
Tip: Be sure to be on RealmeUI 3 C.09, GDPR C.08 or CN C.10 before flashing this ROM.
DOWNLOADS
Click here to Download
Tip: Use the latest TWRP build for flashing this ROM.
Read our blog article/post about:
* HOW-TO report a bug
GPL compliance:
ROM Source- https://github.com/ArrowOS
Device Source- https://github.com/realme-sm8250-devs
Kernel Source- https://github.com/realme-sm8250-devs/android_kernel_realme_sm8250
Wow
Downloading
will there be a vanilla build?
Awesome
Pro af
Finally
my touch screen doesnt work anymore, please help
edit: nvm i fixed it
Deleted
Im having a strange issue, I have the newest twrp build. everything went well flashed c_04. Flashed arrow os after everything boots runs good. I want to root so i download magisk transfer over my boot image patch it. Reboot back into twrp recovery and file system says 0mb I am unable to mount it. Not sure if I maybe missed a step. After seeing a unmountable filesystem in twrp i can just reboot back into the system fine. I have tried with screenlock password and without, I have also tried to enter my screenlock password into the decrypt data under mount. I used fastboot to flash the boot file and it worked. Still confused a bug maybe?
andrew202 said:
Im having a strange issue, I have the newest twrp build. everything went well flashed c_04. Flashed arrow os after everything boots runs good. I want to root so i download magisk transfer over my boot image patch it. Reboot back into twrp recovery and file system says 0mb I am unable to mount it. Not sure if I maybe missed a step. After seeing a unmountable filesystem in twrp i can just reboot back into the system fine. I have tried with screenlock password and without, I have also tried to enter my screenlock password into the decrypt data under mount. I used fastboot to flash the boot file and it worked. Still confused a bug maybe?
Click to expand...
Click to collapse
You need to format data partition, so that it will be fix that problem.
Extra instructions.
1. Running RMX3370 Global RUI c.04
2. Unlock bootloader, using deeptest app method
3. Make sure you have adb/fastboot platform tools and driver on your computer
4. To use TWRP, get latest found on XDA in RM GT Neo 2 forum, extract the zip since they didn't upload as an img for simplicity and place the img file in the same directory as your adb files
5. Use - adb boot recovery.img
6. Once TWRP is loaded on your phone go to ADB Sideload and slide to activate
7. On computer, make sure to check adb is active using - adb devices
8. If your device lists on command prompt, then go ahead and flash the rom using - adb sideload rom.zip
9. After this you can flash magisk zip (this is optional, I personally didn't)
10. Once this is done, go to Wipe, and Click on Format Data button, type yes and enter it - data will format
11. Then reboot to system
Note, flashing twrp with - adb flash recovery command - does not work from c.04 --- this is why adb boot is used instead.
Nurujjamanpollob said:
You need to format data partition, so that it will be fix that problem.
Click to expand...
Click to collapse
I did that right away after flashing firmware, I can get the data partition to show up if I change the data partition file system and change it back. But soon as I do a reboot it's back to 0mb.
andrew202 said:
I did that right away after flashing firmware, I can get the data partition to show up if I change the data partition file system and change it back. But soon as I do a reboot it's back to 0mb.
Click to expand...
Click to collapse
You may need to try:
Format data partition, right after that, go to twrp menu and choose reboot to recovery option.
If still you see 0 mb, it's due to kernel or rom problem I think.
andrew202 said:
Im having a strange issue, I have the newest twrp build. everything went well flashed c_04. Flashed arrow os after everything boots runs good. I want to root so i download magisk transfer over my boot image patch it. Reboot back into twrp recovery and file system says 0mb I am unable to mount it. Not sure if I maybe missed a step. After seeing a unmountable filesystem in twrp i can just reboot back into the system fine. I have tried with screenlock password and without, I have also tried to enter my screenlock password into the decrypt data under mount. I used fastboot to flash the boot file and it worked. Still confused a bug maybe?
Click to expand...
Click to collapse
That is TWRP bug , officially TWRP still does not supports Android 12 decryption , you wont have this problem if a) ROM is force encryption disabled or b) ROM is below Android 12 like Android 11
In my opinion becuase of lack of kernel source for ANDroid12 for our device by Realme
We should try to use Android 11 ROMS , since everything works in it
andrew202 said:
I did that right away after flashing firmware, I can get the data partition to show up if I change the data partition file system and change it back. But soon as I do a reboot it's back to 0mb.
Click to expand...
Click to collapse
If you are coming from an A12 ROM,
after flashing the new ROM, go to fastboot and do "fastboot -w" to format data.
your newly flashed ROM will boot.
The genius Neo2 devs forgot the crucial detail that people could be coming from A12 and TWRP cant mount partitions to even format data
EisregenHaha said:
my touch screen doesnt work anymore, please help
edit: nvm i fixed it
Click to expand...
Click to collapse
How did you fix it? I'm having the same problem
omgitsvoltpunk said:
How did you fix it? I'm having the same problem
Click to expand...
Click to collapse
Flash newest rui before flashing arrow.
A new ArrowOS update is available to download !
ROM changelog:
• Sync arrow's 12/06/2022 source
Device changelog:
• Build nqnfcinfo
• Import default_volume_tables.xml from my_product
• Label some logging properties on sepolicy
• Move a vendor acdbdata leftover to odm
• Reduce headset volume
• Reset dimlayer HBM + fp press state on error
• Stop building tinymix
• Switch to Oplus libperfmgr and drop QTI perfd
• Switch to Oplus light service
A new ArrowOS update is available to download !
ROM changelog:
• Sync arrow's 16/07/2022 source
Device changelog:
• Add TICK effect in oplus vibrator service
• Build audio amplifier for top speaker
• Cleanup properties
• Drop a few useless Oplus camera services
• Enable properly QTI media c2 service
• Fix 1080p60fps and Netflix crash
• Fix OTP SMS
• Switch to Oplus QTI sepolicy repo
• Track some audio configs from QCOM audio hardware
• Update prebuilt kernel and blobs to RMX3370_11.C.07
• Update touchpanel firmware from odm if newer
• Update wifi tether overlays for hostpot

[ROM][UNOFFICIAL][Guacamole][12] LineageOS v19.1 [Weeklies]

{
"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"
}
All the source code for LineageOS is available in the LineageOS Github repo.
Making a new thread so as to not hijack the build thread from March. Until the official release, I will upload weekly builds as I can. I personally test my builds for a couple of days before I release them, but...
USE THEM AT YOUR OWN RISK. I TAKE NO RESPONSIBILITY FOR YOU BRICKING YOUR PHONE.
Builds:
lineage-19.1-20221003-UNOFFICIAL-guacamole.zip
lineage-19.1-20220912-UNOFFICIAL-guacamole.zip
lineage-19.1-20220905-UNOFFICIAL-guacamole.zip
lineage-19.1-20220828-UNOFFICIAL-guacamole.zip
lineage-19.1-20220823-UNOFFICIAL-guacamole.zip
lineage-19.1-20220808-UNOFFICIAL-guacamole.zip
lineage-19.1-20220731-UNOFFICIAL-guacamole.zip
lineage-19.1-20220725-UNOFFICIAL-guacamole.zip
lineage-19.1-20220718-UNOFFICIAL-guacamole.zip
lineage-19.1-20220711-UNOFFICIAL-guacamole.zip
lineage-19.1-20220704-UNOFFICIAL-guacamole.zip
lineage-19.1-20220626-UNOFFICIAL-guacamole.zip
Recommended Gapps:
NikGapps-full-arm64-12-20220222-signed.zip (w/ Pixel Launcher disabled)
Recommended GCam: (courtesy of Saikat from the OnePlus 7 Pro XML telegram channel)
SGCAM V25 Snapcam_Special.apk
𝚂𝚊𝚒𝚔𝚊𝚝_𝙵𝚊𝚗𝚌𝚢_𝐕4_𝗕𝗧.xml
libgcastartup_8.4_saikat.so
Notes:
Gapps packages are finicky with A12/LineageOS-19.1. If your phone hangs on boot after flashing, it is likely a problem with your gapps package.
Pixel Launcher is completely broken in many A12 Gapps packages. It will crash on boot, and even if you use a different launcher, Recent Apps will be broken. It's a known issue https://issuetracker.google.com/issues/204650736. I recommend not installing Pixel Launcher at all (and I have disabled it in the NikGapps package I link below).
Depending on the last build that you flashed, you may have to switch pre-device from OnePlus7Pro to guacamole in META-INF/com/android/metadata
Flashing Instructions:
First time installation (clean flash):
BACKUP YOUR DATA
Download latest CRDroid recovery (download). Do not use the magisk patched recovery for initial flash (we will add Magisk later).
Reboot to Fastboot
Flash the boot.img in fastboot
Code:
fastboot flash boot boot.img
Boot to recovery
Factory reset
Reboot to recovery
Sideload LineageOS ROM
Code:
adb sideload lineage-19.1-20220626-UNOFFICIAL-guacamole.zip
If you don't want Gapps, then boot to system. You are done.
If you want Gapps:
Reboot to recovery (DO NOT BOOT SYSTEM YET)
Sideload Gapps package (recommend using NikGapps with Pixel Launcher disabled: NikGapps-full-arm64-12-20220222-signed.zip)
Code:
adb sideload NikGapps-full-arm64-12-20220222-signed.zip
Boot to system
If you want Magisk:
Only do this after you have finished installing ROM and Gapps (if desired), and successfully booted into system.
Flash latest Magisk zip from here. (download the apk file, rename from .apk to .zip, and sideload)
Reboot to system
Open the Magisk app and perform a "Direct Install"
Update from previous build of LineageOS 19.1:
BACKUP YOUR DATA
Boot to recovery
Sideload LineageOS ROM
Code:
adb sideload lineage-19.1-20220626-UNOFFICIAL-guacamole.zip
If you had Gapps, reboot to recovery
Sideload Gapps package
Code:
adb sideload NikGapps-full-arm64-12-20220222-signed.zip
Boot to system
If you want Magisk:
Reboot to recovery
Flash latest Magisk zip from here. (download the apk file, rename from .apk to .zip, and sideload)
Reboot to system
Open the Magisk app and perform a "Direct Install"
Download link to your ROM navigates to the NiKGapps package.
Can you fix the download link?
Cmindo said:
Download link to your ROM navigates to the NiKGapps package.
Can you fix the download link?
Click to expand...
Click to collapse
Until the OP can fix their link, here it is from the other thread.
lineage-19.1-20220626-UNOFFICIAL-guacamole.zip
thanks for sharing your los build
Cmindo said:
Download link to your ROM navigates to the NiKGapps package.
Can you fix the download link?
Click to expand...
Click to collapse
Thanks. Should be fixed now.
Unfortunately I still get an error even after editing the metadata to ensure pre-device is set "guacamole".
Error applying update: 21 (ErrorCode::kDownloadInvalidMetadataMagicString)
Any idea on how to resolve this?
Cmindo said:
Unfortunately I still get an error even after editing the metadata to ensure pre-device is set "guacamole".
Error applying update: 21 (ErrorCode::kDownloadInvalidMetadataMagicString)
Any idea on how to resolve this?
Click to expand...
Click to collapse
i didnt faced any problems while sideloading and didnt change any metadata i used boot img from the rom zip
Cmindo said:
Unfortunately I still get an error even after editing the metadata to ensure pre-device is set "guacamole".
Error applying update: 21 (ErrorCode::kDownloadInvalidMetadataMagicString)
Any idea on how to resolve this?
Click to expand...
Click to collapse
Double check that you didn't add any whitespace to the metadata pre-device setting. ROM seems to be working fine for others, so I'm not sure why you're getting that error.
skythian said:
Double check that you didn't add any whitespace to the metadata pre-device setting. ROM seems to be working fine for others, so I'm not sure why you're getting that error.
Click to expand...
Click to collapse
Checked that already, unfortunately that did not help.
Cmindo said:
Checked that already, unfortunately that did not help.
View attachment 5649715
Click to expand...
Click to collapse
Try this build: https://drive.google.com/file/d/1N4Qdo7OSKZkDwrtj3vOK8i5hjs4xzGhK/view?usp=sharing
It has guacamole set to pre-device.
Did you add a newline after the pre-device line?
skythian said:
Try this build: https://drive.google.com/file/d/1N4Qdo7OSKZkDwrtj3vOK8i5hjs4xzGhK/view?usp=sharing
It has guacamole set to pre-device.
Did you add a newline after the pre-device line?
Click to expand...
Click to collapse
Not sure what the difference was but your download worked!
I also ensured there were no line breaks after the pre-device line.
Thanks in any case!
I'm glad it's working now.
Nice to see a fresh new Lineage build for our trusty 7s. I just hope it is better maintained and refreshed than the previous ones. Thank you Skythian et al!
Everything seems to work, including on Verizon. Used core Nikgapps and flashed fine, no issues. Will test run it throughout the day tomorrow and report back on any issues. Thank you!
Trying to uninstall some of the pre-loaded apps via ADB like Camera (using Gcam instead), Recorder, etc.
However using the below command doesn't work for some reason:
adb uninstall -- user 0 com.android.camera2
Any reason why? This command usually works using other roms.
I am using previous build of los 19.1 which is lineage-19.1-20220316-UNOFFICIAL-guacamole along with mindthegapps package.
Can I dirty flash this new build with the same gapps package, will it support?
Edit: Tried it failed and bootloop to recovery. Back to the old build. Followed all instructions, no idea what could've went wrong???
i found little bug with the loaction indicator keep showing in the statusbar even when the location is disabled , the phone services keep getting locations
kpmohamedhussain said:
I am using previous build of los 19.1 which is lineage-19.1-20220316-UNOFFICIAL-guacamole along with mindthegapps package.
Can I dirty flash this new build with the same gapps package, will it support?
Edit: Tried it failed and bootloop to recovery. Back to the old build. Followed all instructions, no idea what could've went wrong???
Click to expand...
Click to collapse
Tried again, with nikgapps and the result is same. Not possible to upgrade from lineage-19.1-20220316-UNOFFICIAL-guacamole ???
Any suggestions pls...
During installation got signature verification warning...
Red message after bootloop to recovery as below
1. Wipe cache
2. Init user0 failed
3. Clean flash rom
kpmohamedhussain said:
Tried again, with nikgapps and the result is same. Not possible to upgrade from lineage-19.1-20220316-UNOFFICIAL-guacamole ???
Any suggestions pls...
During installation got signature verification warning...
Red message after bootloop to recovery as below
1. Wipe cache
2. Init user0 failed
3. Clean flash rom
Click to expand...
Click to collapse
Yes, it's possible to upgrade from the 03/16 version.
You don't need to wipe cache. Signature verification warning is expected for Unofficial builds. Not sure what you mean by Init user0 failed and clean flash rom.
Follow the instructions in OP exactly for upgrading builds. Generally bootloops or hung boots are an issue with the Gapps you are flashing. Try flashing the same Gapps you had previously.
Currently testing newest release. I'll post it tomorrow, assuming I don't find any bugs.

Development [RECOVERY][UNOFFICIAL] TWRP 3.7.0_12-0 for OnePlus Nord 2T [karen]

{
"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:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
What's not working?
See https://github.com/oneplus-karen-ro...s_karen-twrp/issues/1#issuecomment-1272629658
- Using fastboot boot <image> doesn't work, due to a very common MediaTek bootloader bug.
- Backing up Data partition may fail due to possible FBE issue.
- Installing OxygenOS stock OTA zip probably fails, because OnePlus didn't add version numbers to their partititons.
Flash guide:
1. Make sure you have the stock boot.img ready that matches your current OxygenOS version.
There's a list of them on this great guide: How to Root Nord 2T with Magisk without TWRP
Add both boot.img and twrp-3.7.0_12-0-UNOFFICIAL-karen.img to your phone storage, using MTP or adb push for example.
2. Flash the TWRP release to the boot partition.
Code:
fastboot flash boot twrp-3.7.0_12-0-UNOFFICIAL-karen.img
fastboot reboot
3. Once you've rebooted to TWRP, install the stock boot.img
- [Install]
- Toggle [Install Image]
- Choose boot.img in the file browser
- Select partition: Boot
- Swipe, DO NOT REBOOT
4. Next we install the ramdisk.
- Press back
- Choose twrp-3.7.0_12-0-UNOFFICIAL-karen.img in the file browser.
- Select partition: Install Recovery Ramdisk
- Swipe (optional, if you want to root the phone, DO NOT REBOOT).
- If you don't want to root, you can reboot now.
Optional, rooting:
5. Save the repackaged boot for Magisk.
Code:
adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot-with-twrp.img
6. Patching the image to root.
- Reboot the device, to normal OS.
- In the Magisk app, choose install and patch our boot-with-twrp.img image.
- Note the ..../Download/magisk_patched-XXXXXXX.img filename in the logs.
7. Install the rooted boot image.
- First switch to TWRP
Code:
adb reboot recovery
- In TWRP, [Install]
- Toggle [Install Image]
- Choose Download/magisk_patched-XXXXXXX.img in the file browser
- Select partition: Boot
- Swipe
- Reboot! You're (finally) done.
Download:
twrp-3.7.0_12-1-UNOFFICIAL-karen.img
twrp-3.7.0_12-0-UNOFFICIAL-karen.img
Source code:
GitHub - oneplus-karen-roms/android_device_oneplus_karen-twrp
Contribute to oneplus-karen-roms/android_device_oneplus_karen-twrp development by creating an account on GitHub.
github.com
Credits:
@SakilMondal for the TWRP denniz (Nord 2) tree this is largely based on.
@PattasuBalu for testing out alpha builds and troubleshooting.
Information:
TWRP version: 3.7.0_12-1-UNOFFICIAL
Created: 2022-10-09
Last Update: 2022-10-15
Reserved :]
Q&A:
Do you need to repeat the install steps after an OTA update?
Short answer: yes you do.
Longer answer
Can't we install Magisk as a zip from TWRP?
Maybe you can? I just don't recommend it.
And neither does Magisk.
Fantastic work. Congrats and a huge thank you
Thanks for the TWRP, now the question is, what happen when we receive OTA updates?
Why seems not possible to directly flash magisk zip (apk renamed) to patch boot img?
I think is better to add this first Q&A in a FAQ list.
cioce said:
Thanks for the TWRP, now the question is, what happen when we receive OTA updates?
Why seems not possible to directly flash magisk zip (apk renamed) to patch boot img?
I think is better to add this first Q&A in a FAQ list.
Click to expand...
Click to collapse
When you recieve an OTA update you have do the entire process again.
garylawwd said:
Fantastic work. Congrats and a huge thank you
Click to expand...
Click to collapse
Thanks for the kind words. :] Was a fair bit of a learning curve but nothing quite as troublesome as now trying to build a full ROM. No luck on that yet.
cioce said:
Thanks for the TWRP, now the question is, what happen when we receive OTA updates?
Why seems not possible to directly flash magisk zip (apk renamed) to patch boot img?
I think is better to add this first Q&A in a FAQ list.
Click to expand...
Click to collapse
(Added the TL;DRs to the second post)
Do you need to repeat the install after an OTA?
Indeed you will need to repeat the process after an OTA.
With an asterisk. Because in theory you could speed this up if you have root access.
The Magisk app has a feature to "Install to Inactive Slot". And the TWRP app could be doing something similar, but I find it needs some work to be more reliable in doing that :]
So if 1. this becomes an OFFICIAL build, and 2. the TWRP app gets some love. It could be done.
Why can you not install Magisk as an APK?
Maybe you can though? I just don't recommend it.
I'm not a Magisk dev so I might miss the finer details why, but they state this method is no longer recommended and deprecated. So it wasn't on my checklist to try or support it.
I suspect though that the patching script will need to make a load of assumptions about how that recovery environment is set up, while the app would be more reliable.
Small update, https://github.com/oneplus-karen-ro...karen-twrp/releases/tag/3.7.0_12-1-UNOFFICIAL
Update the kernel and dtbo.img to use A.15 version.
Rebuild with upstream patch, that should fix the lpdump utility.
Note: you only really need to update if you're interested in using lpdump in TWRP.
Thanks for the update, what about SafetyNet test after TWRP + Root?
Is there any Magisk module that working 100%?
cioce said:
Thanks for the update, what about SafetyNet test after TWRP + Root?
Is there any Magisk module that working 100%?
Click to expand...
Click to collapse
SafteyNet is working fine. Using Universal SafteyNetFix by kdrag0n and added play services to blocklist on Zygisk.
Will the OnePlus Nord 2T be getting any Custom ROM's being built for it in the future?
ArmashOnXDA said:
Will the OnePlus Nord 2T be getting any Custom ROM's being built for it in the future?
Click to expand...
Click to collapse
I hope that yes It's simillar to previous model, we have the kernel etc. Beanow is doing well job with preparing recovery, so it should works We need to find only someone with skills and free time to prepare e.g. LineageOs for us
Beanow Could you tell me if you will continue working on the reocvery?​
hi,
can I use this twrp to install full ROM zip file?
what is the right order to install:
1. full zip ROM
2. twrp.img
3. magisk patched boot.img
is it ok?
nutfile said:
hi,
can I use this twrp to install full ROM zip file?
what is the right order to install:
1. full zip ROM
2. twrp.img
3. magisk patched boot.img
is it ok?
Click to expand...
Click to collapse
It depends if the rom has ramdisk or not but I've seen techkaran's video and he had ramdisk the rom had ramdisk
Did anybody install a ROM in this device yet? Is is possible to install a ROM from the regular Nord 2?
simongaiteiro said:
Did anybody install a ROM in this device yet? Is is possible to install a ROM from the regular Nord 2?
Click to expand...
Click to collapse
There is not yet a rom but u could flash gsi with dsu sideloader
Stephanizgo said:
There is not yet a rom but u could flash gsi with dsu sideloader
Click to expand...
Click to collapse
Never tried to install a GSI before. Did you already tried it on this phone?
simongaiteiro said:
Never tried to install a GSI before. Did you already tried it on this phone?
Click to expand...
Click to collapse
I tried dsu loader on a different phone and it partialy worked but it's ment for the devs
But it's easy u just unlock the bootloader and download dsu sideloader. Then connect to pc and type some command and dsu will sideload sideload your preferred GSI
Now using DSU side loader with magisk patched boot.img working fine

Categories

Resources