Develop Bugs

[9][OFFICIAL][WEEKLY] CarbonROM | cr-7.0 [taimen]

{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! These builds are experimental and can contain Bugs (as listed above). Make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Download
Join the CarbonROM Discord server
Meet us on Telegram
Homepage
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Google Pixel 2 XL
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2019-04-09
Last Updated 2019-08-28

Fyi your post isn't loading on the XDA app.

gforceriders said:
Fyi your post isn't loading on the XDA app.
Click to expand...
Click to collapse
Shows up fine on the XDA labs app :good:

Badger50 said:
Shows up fine on the XDA labs app :good:
Click to expand...
Click to collapse
After you posted now it's working lol. Strange man strange. Carry on with flashing peeps.

Rock on brother! Be flashing this next week when back from my cruise!!

What gapps do you recommend for this ROM. It has been a while since I ran carbon.

gforceriders said:
Fyi your post isn't loading on the XDA app.
Click to expand...
Click to collapse
gforceriders said:
After you posted now it's working lol. Strange man strange. Carry on with flashing peeps.
Click to expand...
Click to collapse
Haha, weird things.
encephalon9986 said:
What gapps do you recommend for this ROM. It has been a while since I ran carbon.
Click to expand...
Click to collapse
I recommend OpenGapps.
Flashing procedure is
Flash Carbon
Flash TWRP
Reboot to recovery (this switches slots, it's important)
Flash GApps
Done

is anyone else having trouble with Gboard themes on this ROM? If I pick a gradient theme it just hangs and crashes.
I flashed this with Mini gapps first and had a hard time getting through setup, tried again with pico with more success.

Edmontonchef said:
is anyone else having trouble with Gboard themes on this ROM? If I pick a gradient theme it just hangs and crashes.
I flashed this with Mini gapps first and had a hard time getting through setup, tried again with pico with more success.
Click to expand...
Click to collapse
I flashed the micro package and can't even get past checking for updates. The data transfer tool keeps just keeps crashing.
Edit: Tried flashing the pico package instead and now device health services keeps crashing.

Has anyone tried razorloves' MindTheGapps package?
https://androidfilehost.com/?fid=1395089523397912604

Myself5 said:
Haha, weird things.
I recommend OpenGapps.
Flashing procedure is
Flash Carbon
Flash TWRP
Reboot to recovery (this switches slots, it's important)
Flash GApps
Done
Click to expand...
Click to collapse
How to flash if I only want twrp temporary? Same way?

omair2005 said:
How to flash if I only want twrp temporary? Same way?
Click to expand...
Click to collapse
Leave out the "Flash TWRP" part and replace "reboot to recovery" with "reboot to bootloader and boot the twrp image"

Not judging but simply confused...
I see people not wanting to install twrp and it just makes no sense to me why I would want to limit my options and functionality.
It's been like almost a year since twrp had been totally stable for me with no decryption or touch issues.
Again, what is it folks are afraid of??

I'm digging how clean and fast this ROM is. Hopefully you get your server issues resolved soon.

Trying this out again! Carbon was the first ROM I've ever used on my Pixel 2 XL and absolutely loved the experience.

Edmontonchef said:
I'm digging how clean and fast this ROM is. Hopefully you get your server issues resolved soon.
Click to expand...
Click to collapse
So do I... We already have a new host because we're fed up with the old one. Currently waiting for the old one to finally answer our support ticket and bring the server back on so we can move our data to the new server and can call it a day with the old host.

Has anyone tried installing NanoDroid with this?
I went from factory image -> flash rom -> flash twrp -> reboot recovery -> flash magisk -> flash full nanodroid.zip
This leads to a bootloop until it boots back into recovery

When I try to set up any password, it does not let me proceed after the second test. Confirm gets grayed out

Bilge656 said:
Has anyone tried installing NanoDroid with this?
I went from factory image -> flash rom -> flash twrp -> reboot recovery -> flash magisk -> flash full nanodroid.zip
This leads to a bootloop until it boots back into recovery
Click to expand...
Click to collapse
The issue here would be magisk. You usually need to boot to the system at least once before you can sucessfully flash Magisk. Don't know the reasons but it's seems to be an ongoing theme on A/B devices. Same happens on my OP6 and 6T

Myself5 said:
The issue here would be magisk. You usually need to boot to the system at least once before you can sucessfully flash Magisk. Don't know the reasons but it's seems to be an ongoing theme on A/B devices. Same happens on my OP6 and 6T
Click to expand...
Click to collapse
So theoretically I need flash the rom in 'A,' flash magisk on 'B', boot into the system once, reboot recovery into 'B,' and then install nanodroid?
Edit: Well I ignored Magisk and rebooted to recovery to install nanodroid after rom installation and it booted back into recovery unfortunately.

[PIE]TomaHawk Project - take your privacy back!

Don't like sharing secrets with Google, but still want to use their apps like Play Store/YouTube and others?
AOSP Roms are not stable enough for everyday use or missing some stock functionality?
Do you want a device for everyday use that simply works and don't disturb with unnecessary functionality?
Do you want to get more juice out of your XZP?
If yes -> follow this:
TomaHawk Project
{
"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"
}
Extremely debloated stock ROM without Google Apps
Awesome performance, stability and battery life.
Most of the apps containing words "backup", "logging", "monitor", "smart" and other that may leak your personal data have been removed.
This ROM converts your G8141 to G8142, buy yourself a microSD slot for G8142 and use your XZP with 2 simcards.
Read more about NanoDroid here
You gonna need:​
TWRP
Rom base from here
TomaHawk Rom, GDrive mirror
NanoDroid, NanoDroid-Pather, Nanodroid-SetupWizard from here
Magisk 19.3
Installation:​
Install base with NewFlasher (your phone will be formatted)
Boot right into TWRP, flash Tomahawk_Project and Magisk 19.3
Reboot and run the wizard
Boot back to TWRP , run NanoDroid SetupWizard, then NanoDroid, then patching
You may update magisk now
Bugs:​Sony Messenger gives FC for less than a second, but works.
Use QKSMS for example and disable it.
All the questions regarded installation of NanoDroid or working of apps related to Google should be asked in Nanodroid topic! If you installed other addons such as ExistenZ don't report bugs here either.
About me:
I am a cyber security specialist and a custom rom developer who concerned about data that we share with nobody knows who. I using android since 2011 , mostly Sony Devices. I have my own view on how perfect android phone looks like and I am happily sharing my results with you.
If you want to support me and my goal of making affordable and usable secure communications feel free to support me.

Addons:
Digital wellbeing
Services.jar (in case patcher fails, tested with ExistenZ)
TWRP

Hi thx for your share and guide
I get error in flash. My device is G8188(not daul) and i flash the CE Oreo unlock the bl . Then i flash this (i got G8142)my device lost imei and baseband. so i cant use sim
And also i wanna got pie. Hope your reply.

9264 said:
Hi thx for your share and guide
I get error in flash. My device is G8188(not daul) and i flash the CE Oreo unlock the bl . Then i flash this (i got G8142)my device lost imei and baseband. so i cant use sim
And also i wanna got pie. Hope your reply.
Click to expand...
Click to collapse
Not sure about the details for G8188 (which I think is the Japanese variant). If your device is not the dual-SIM variant, you need to flash G8141 firmware.
And I'm not really sure about how to deal with a device that's lost its IMEI and baseband.

9264 said:
Hi thx for your share and guide
I get error in flash. My device is G8188(not daul) and i flash the CE Oreo unlock the bl . Then i flash this (i got G8142)my device lost imei and baseband. so i cant use sim
And also i wanna got pie. Hope your reply.
Click to expand...
Click to collapse
Try to flash only system image from this rom. use modem and the rest from your latest stock like modem and etc. Sorry for long reply

great work!
looks a little complicated, But i will try ..
thanks for share it!

Please explain more steps 5 and 8 ..Where can I find them ?

CRNO said:
Please explain more steps 5 and 8 ..Where can I find them ?
Click to expand...
Click to collapse
Updated rom, now installation is more simple

Beta test is closed.

I will try it when I'm back home , thx for your work and your time

Stable version is up!

Is there a stable oreo version? Well done when i do DRM backup finally i will try this out

digiscales said:
Is there a stable oreo version? Well done when i do DRM backup finally i will try this out
Click to expand...
Click to collapse
Well, I experimented with oreo,because I like it more than pie, but it's not that stable yet. There are some mystical bugs and bootloops, that doesn't make any sense at all to me.
If there will be demand for Oreo version, I will consider making it.

Doom Slayer said:
Stable version is up!
Click to expand...
Click to collapse
Nice. I was using NanoDroid with the China ROM but it wasn't fully compatible, especially that the contacts sync adapter wasn't working. I'll give this a try once I'm back in the house. Thanks.

hi, need to mention to use aroma twrp. when using normal twrp the NanoDroid SetupWizard will freeze

hangneko21 said:
hi, need to mention to use aroma twrp. when using normal twrp the NanoDroid SetupWizard will freeze
Click to expand...
Click to collapse
try use Twrp v3.2.1.0, was working with me

hangneko21 said:
hi, need to mention to use aroma twrp. when using normal twrp the NanoDroid SetupWizard will freeze
Click to expand...
Click to collapse
Try one of those:
https://www.androidfilehost.com/?w=files&flid=304126

I protected the Project with a company.
So no one would even dare sell or spoil it.
But I gonna make services for a living, so don't get me wrong.
You can say it's cheap advertisement, but change the perspective and see the bigger picture.
I gonna bring privacy back and I need your help to do it.

Doom Slayer said:
I protected the Project with a company.
So no one would even dare sell or spoil it.
But I gonna make services for a living, so don't get me wrong.
You can say it's cheap advertisement, but change the perspective and see the bigger picture.
I gonna bring privacy back and I need your help to do it.
Click to expand...
Click to collapse
Thanks

@Doom Slayer your rom link says no mirror please fix it.

Firmware/Vendor Confusion + General Questions about ROMs and Android

Hello all,
A few months back I unlocked my Mi 9 SE and rooted it using TWRP+Magisk, so fine so good. I then wanted to go on and install a custom ROM, but every time I tried, I just got my phone stuck in a bootloop and had to reflash MIUI using the scripts provided by Xiaomi (MiFlash/ .flash_all). After that, I decided I would not try meddling with ROMs again until had a better understanding of the (basic) underlying workings of this stuff.
After doing some research on my own I got answers to some of my confusion, but a lot remain, which is why I'm now trying my luck here. Maybe there is a "beginner's guide" of sorts somewhere on this forum, but so far I haven't been lucky in finding any. So, if any more experienced "flasher" or maybe even developer could clarify some things for me, and perhaps others, that would be great!
Firmware/Vendor
Firstly, the thing that has confused me since the beginning is the concept of firmware/vendor. I understand that the firmware of Xiaomi phones can be found easily on the internet and that it contains some amount of proprietary software such as drivers. However, while in some flashing instructions it is clearly indicated to "flash fw" after wiping, in others this is not mentioned at all. Is this because some ROMS already contain those drivers and others don't?
Then comes the question of "vendor". Again, some guides mention this, some don't, and on the site http://xiaomifirmwareupdater.com/, where one can find the fw, there is also a section for "vendor" files. So my question here is: what is the difference between vendor and firmware, and is either of them necessary before installing ROMS?
General Questions
From all of this, the way I picture the contents of an android phone are, from low to high level:
Bootloader (like the BIOS on a computer) ==> Firmware (Basic proprietary drivers) ==> Kernel ==> Rest of the OS (Implicit question: how correct is this picture?)
The kernel, from what I gather, is included in the flashable images of most ROMS, and the devs in turn use either the stock kernel from Xiaomi of some custom one like Kowalski's.
Question: What is the distinction between the firmware and the kernel? Since both are, in the beginning, made by Xiaomi, why are they separate things if they serve a similar purpose (drivers and Hardware/Software communication)?
Also, "bonus question" (just out of curiosity): I've heard that the only way to actually hard-brick your phone (other than hardware damage) is to somehow mess up the bootloader (kind of like corrupting the BIOS on a computer). How could this happen?
ROM Build
Finally, a few questions if any ROM dev stumbles upon this post, since apart from the practical aspects I'm also curious about the way a ROM is actually ported to a specific device, say our beloved little grus. Again, I'll just say what I understood so far and you guys can then correct me. From what I read in the building instructions for LineageOS on other devices, the way to proceed is to get the source code of the ROM itself by cloning the repo and then adding device-specific code (Kernel, device tree and Vendor Blobs) before proceeding to actually build the Image. My questions are, apart from if this is correct:
- How intercompatible are these components? Is a device tree specific to a certain kernel? To a certain ROM? Could one use, say, the kowalski DT with the stock kernel from Xiaomi?
- Again, what is the difference between "vendor blobs" and the "vendor" files mentioned above?
I know this is a very long post and I'm asking a lot of unrelated questions, but I hope that if someone takes the time to read through it and answer at least some parts of it, this could be useful in the future not only for me but also any other beginner trying to get into custom ROMS on Xiaomi phones. Cheers!

Wouldn't agree with your firmware definition (although you probably consulted like Wikipedia - their definition is more like for embedded systems like remote controllers or so)
Download Xiaomi Fastboot firmware from:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Its tgz file, hence to unpack, you have to un-gzip and un-tar (you can use 7-zip on Windoze or MiXPlorer to do everything on your phone), open Images folder and look how many img files it contains.
Besides like System, Vendor, etc, it even contains image for Recovery (Recovery is not part of Android, you separately boot to Android, Recovery or Fastboot - the last is part of Bootloader).
Manufacturer can even push new Bootloader via the firmware OTA (I recall how Huawei pushed new bootloader.img in 2018 via its OTA updates, to invalidate the previous merhods for unlocking Bootloader, making it 'almost' impossible to unlock the new Bootloader)
Consider firmware as the opposite of hardware, it's all firm software on your phone: Bootloader, Recovery, Android - all except your user apps, settings and Data you will install to Data or Internal memory.
Firmware also does not overwrite some specifical info related to your particular phone like IMEI(s), Widewine L1 cert (hence if you dropped to L3 by installing custom ROMs, you cannot recover L1 by reflashing the full firmware)
And Kernel is just the Android kernel (as inherited from Linux kernel), similarly like Windows OS has its own kernel

Thanks for your reply, I think that there is a misunderstanding: What I'm talking about when I say Firmware is this thing: (taken from the site you referenced). This is a small (~70mb) zip archive that contains no images, only binaries. I'm NOT talking about the whole Xiaomi ROM, which is indeed a large tgz and contains all the images you mention.
{
"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"
}
To clarify, what confuses me in flashing guides is (example from evolution x rom) the line where it says "Flash FW & BB", or sometimes just "flash fw"

lachesis197 said:
Thanks for your reply, I think that there is a misunderstanding: What I'm talking about when I say Firmware is this thing: (taken from the site you referenced). This is a small (~70mb) zip archive that contains no images, only binaries. I'm NOT talking about the whole Xiaomi ROM, which is indeed a large tgz and contains all the images you mention.
View attachment 5181291
To clarify, what confuses me in flashing guides is (example from evolution x rom) the line where it says "Flash FW & BB", or sometimes just "flash fw"
View attachment 5181295
Click to expand...
Click to collapse
Don't really now what does it mean in the context of installation guide for the given custom ROM
Under Mi 9T/Redmi K 20 ROMs subforum, there are tons of threads, each one for a particular custom ROM.
For most of them there are also Telegram channels
IMO, you can better clarify by asking there, where the ROM users are subscribed and actively participating

Hello, I Have a Samsung galaxy s9 Exynos. I have rooted it with magick. Now i want to use evolution Rom but when I am trying to flash with TWRP it is showing--
Vendor Image on the device is NOT compatible
Expected Version: 29_ETFS
You can download it from mega.NZ/FM/F9VHHALY.
what to do. can Someone help?

Manglesh____ said:
Hello, I Have a Samsung galaxy s9 Exynos. I have rooted it with magick. Now i want to use evolution Rom but when I am trying to flash with TWRP it is showing--
Vendor Image on the device is NOT compatible
Expected Version: 29_ETFS
You can download it from mega.NZ/FM/F9VHHALY.
what to do. can Someone help?
Click to expand...
Click to collapse
You missed the Forum - this is for Xiaomi Mi 9 SE - do you really want a Xiaomi user to guide you about flashing your Samsung and to brick your phone

zgfg said:
You missed the Forum - this is for Xiaomi Mi 9 SE - do you really want a Xiaomi user to guide you about flashing your Samsung and to brick your phone
Click to expand...
Click to collapse
thank for telling man i really missed ,anyways the problem is solves now.

@lachesis197 I'm in the same spot you where 1,5 years ago.
It seems in the Android customization community most info to be found is of the sorts "to get this, do this". But very little of why something works the way it does. Very little explanations of what it all means.

hagekic548 said:
@lachesis197 I'm in the same spot you where 1,5 years ago.
It seems in the Android customization community most info to be found is of the sorts "to get this, do this". But very little of why something works the way it does. Very little explanations of what it all means.
Click to expand...
Click to collapse
Here I am about a year later after you! It seems so hard to find 'curated' info. All this info is all over the place.

[ROM][Unofficial] Galaxy S9 Starlte and Star2lte crDroid 7.6

{
"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:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
step 1: Unlock BL
step 2: Flash TWRP and format data
step 3 Flash ROM, Gapps and Magisk
step 4 Reboot
step 5 Done
Update installation:
step 1 Flash ROM
step 2 Reboot
Do not wipe anything
Download:
Galaxy S9: Download
Galaxy S9 Plus (UNTESTED): Download
Known issues:
voLTE, Samsung proprietary apps, Screen Mirroring
Visit official website @ crDroid.net
crDroid S9/+/Note 9 Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Credits go to:
The crDroid team: Website Github
Synt4x93: Github @Synt4x.93
Lineage os team: Website Github
Big thanks to DeinMathelehrer for helping me get everything up and running: Github @hisoka_simp

Epic! I'l try this on my star2lte and let you know.

CustomOsLover said:
Epic! I'l try this on my star2lte and let you know.
Click to expand...
Click to collapse
So, I'm waiting for 5 mins now. It doesn't boot for now

Nice it's working, hope you continue to work on custom Roms

CustomOsLover said:
So, I'm waiting for 5 mins now. It doesn't boot for now
Click to expand...
Click to collapse
UPDATE: it's working now. Might had some problems with my GAPPs

CustomOsLover said:
Epic! I'l try this on my star2lte and let you know.
Click to expand...
Click to collapse
Thankyou!

I've been using this for a day now and I gotta admit, it's so smooth and reliable for now, nothing to argue about! I absolutely love this rom! Thanks for creating this for the S9(+) Hope we'll get more ROMs like this

CustomOsLover said:
I've been using this for a day now and I gotta admit, it's so smooth and reliable for now, nothing to argue about! I absolutely love this rom! Thanks for creating this for the S9(+) Hope we'll get more ROMs like this
Click to expand...
Click to collapse
Perfect thank you so much. I am glad it works. I need a screenshot of it working though to get the dev's approval. His rules not mine. So just dm me a screenshot in xda of it working please, so I can get it validated. (Screenshot of About Phone > Android Version in settings would be best)
Also a word of warning, I may be unable to create a rom for crdroid S (android 12), as I have no idea how to make rom sources. I just know how to compile roms with preexisting sources. So unless someone builds android 12 lineage os or something for the s9 and s9 plus, then the road may end here for this rom unless someone else picks it up.

hisoka_simp said:
Nice it's working, hope you continue to work on custom Roms
Click to expand...
Click to collapse
Thanks for ur help. I might, but I also have a lot of other things to do.

CustomOsLover said:
UPDATE: it's working now. Might had some problems with my GAPPs
Click to expand...
Click to collapse
Yah, sry I don't use gapps, I try to avoid them as much as possible. So I didnt test that.

Linusrg1 said:
Perfect thank you so much. I am glad it works. I need a screenshot of it working though to get the dev's approval. His rules not mine. So just dm me a screenshot in xda of it working please, so I can get it validated. (Screenshot of About Phone > Android Version in settings would be best)
Also a word of warning, I may be unable to create a rom for crdroid S (android 12), as I have no idea how to make rom sources. I just know how to compile roms with preexisting sources. So unless someone builds android 12 lineage os or something for the s9 and s9 plus, then the road may end here for this rom unless someone else picks it up.
Click to expand...
Click to collapse
Here you go:

CustomOsLover said:
Here you go:View attachment 5312933
Click to expand...
Click to collapse
thankyou

@Linusrg1 I'm currently on crDroid 7.2, on the S9; can I update to 7.6 just by flashing the rom through twrp? Will that create any side effects maybe? Like losing data and such? I cba to make a backup as it's very high in size.

kidi said:
@Linusrg1 I'm currently on crDroid 7.2, on the S9; can I update to 7.6 just by flashing the rom through twrp? Will that create any side effects maybe? Like losing data and such? I cba to make a backup as it's very high in size.
Click to expand...
Click to collapse
Thats what I did and it worked fine. If not make a data backup then start off clean.

Linusrg1 said:
Thats what I did and it worked fine. If not make a data backup then start off clean.
Click to expand...
Click to collapse
I mean you sure it won't mess up with magisk manager and tasker? Since I'm just flashing the rom itself and not re-rooting?
EDIT: I've lost root, and it messed up with google apps, as in they were force closing. I've patched the boot.img for magisk to work again as in to re-gain root, and flashed google apps .zip, it seems ok for now. Also it seems it takes a second for the animation to pass through and to be able to enter the pin code on the lock screen after swiping, why's that?

kidi said:
I mean you sure it won't mess up with magisk manager and tasker? Since I'm just flashing the rom itself and not re-rooting?
EDIT: I've lost root, and it messed up with google apps, as in they were force closing. I've patched the boot.img for magisk to work again as in to re-gain root, and flashed google apps .zip, it seems ok for now. Also it seems it takes a second for the animation to pass through and to be able to enter the pin code on the lock screen after swiping, why's that?
Click to expand...
Click to collapse
Because you need to wipe system data cache and dalvik cache flash the rom and then flash data again.

Linusrg1 said:
Because you need to wipe system data cache and dalvik cache flash the rom and then flash data again.
Click to expand...
Click to collapse
It's all okay now, except I found the culprit to the 1-second delay for the animation to step in to enter the pin; when you set up face unlock, that bug appears. When you don't use face unlock but just pin/fingerprint combo, it doesn't have that delay when you swipe on the lock screen to enter pin.

I have the SM-960F/DS version of starlte, which I believe has the Exynos chipset, while the American version has the SnapDragon. Does anyone know if this ROM will have any issues on the SM-960F/DS or does the chipset not matter for the ROM?

DangerousDays said:
I have the SM-960F/DS version of starlte, which I believe has the Exynos chipset, while the American version has the SnapDragon. Does anyone know if this ROM will have any issues on the SM-960F/DS or does the chipset not matter for the ROM?
Click to expand...
Click to collapse
well, for starters, Snapdragon models mostly can't unlock the bootloader. But yes, the exynos models with the latest bootloader (you can install dev base first and then flash this, if you're uncertain) should run this with no problem.

lordsolrac2 said:
well, for starters, Snapdragon models mostly can't unlock the bootloader. But yes, the exynos models with the latest bootloader (you can install dev base first and then flash this, if you're uncertain) should run this with no problem.
Click to expand...
Click to collapse
Sorry, I am somewhat new to the custom ROM scene. Can you explain to me how to check if I have the latest bootloader, what is the dev base and where I can get it?

Question Keeping Stock Camera App, Throwing out Google Analytics (boot.img, Magisk, Debloater?)

Hello community,
I have no programming experience whatsoever but I am interested in having my Oneplus 9 Pro degoogled because I value my privacy.
Installing a Custom ROM is not an option yet because I don't seem to have found a Camera app that is as satisfying as the stock one (I especially like its Pro mode).
My friend suggested installing Magisk and Debloater, delete all Google services and stay with the Stock rom. So I unlocked the bootloader, booted into fastboot, booted TWRP. I flashed an official firmware Update (Oxygen OS 11.2.10.10.LE15AA), it loaded up to 47% and then showed an Error. I pushed some buttons until I was stuck in a Fastboot-Loop. Luckily I soon found a thread and tried out "fastboot --set-active=b" which solved the issue by booting into Oxygen OS 11.2.10.10.
I would like to understand what happened - I guess I tried to flash an update that was not full and somehow got mixed up with the slots, but the Update was installed anyway on the other slot which I was able to access with changing active slots - but I don't really know.
Anyway, what I really like to know is if anyone has any suggestions for me how to move on from here.
I downloaded the Magisk App but wasn't able to install it properly as I wasn't able to extract the boot.img. I tried with Python 3.8 and payload dumper on my Mac but the command "pip install -r requirements.txt" doesn't work (neither does python -m pip install -r requirements.txt or putting ./ in front of it - it always answers with "no such file or directory").
I also couldn't flash it with TWRP as I don't have the zip file and I heard conflicting opinions about that confused me.
Can somebody help me with a guide for dummies? Or maybe even come up with a different solution for my need to access the Stock Camera App but not having Google Tracking involved in any of my phone activities.
Thank you, this will be highly appreciated!

lai.sha said:
Hello community,
I have no programming experience whatsoever but I am interested in having my Oneplus 9 Pro degoogled because I value my privacy.
Installing a Custom ROM is not an option yet because I don't seem to have found a Camera app that is as satisfying as the stock one (I especially like its Pro mode).
My friend suggested installing Magisk and Debloater, delete all Google services and stay with the Stock rom. So I unlocked the bootloader, booted into fastboot, booted TWRP. I flashed an official firmware Update (Oxygen OS 11.2.10.10.LE15AA), it loaded up to 47% and then showed an Error. I pushed some buttons until I was stuck in a Fastboot-Loop. Luckily I soon found a thread and tried out "fastboot --set-active=b" which solved the issue by booting into Oxygen OS 11.2.10.10.
I would like to understand what happened - I guess I tried to flash an update that was not full and somehow got mixed up with the slots, but the Update was installed anyway on the other slot which I was able to access with changing active slots - but I don't really know.
Anyway, what I really like to know is if anyone has any suggestions for me how to move on from here.
I downloaded the Magisk App but wasn't able to install it properly as I wasn't able to extract the boot.img. I tried with Python 3.8 and payload dumper on my Mac but the command "pip install -r requirements.txt" doesn't work (neither does python -m pip install -r requirements.txt or putting ./ in front of it - it always answers with "no such file or directory").
I also couldn't flash it with TWRP as I don't have the zip file and I heard conflicting opinions about that confused me.
Can somebody help me with a guide for dummies? Or maybe even come up with a different solution for my need to access the Stock Camera App but not having Google Tracking involved in any of my phone activities.
Thank you, this will be highly appreciated!
Click to expand...
Click to collapse
Never mind - I just found it here: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-c-65.4252373/
I'm stil open for better solutions if someone has them!

Hey there!
Loading up to 47% and then throwing an error is actually quite normal, it should still succeed.
Anyway, some intelligent person was able to manage to move the stock OOS cam to custom ROM's. I'm currently running Nameless which is Android 12 which has the OOS cam.
Since you asked for a non-gapps build, you should look for a 'pristine' or 'vanilla' build. I know out of the top of my head that StagOS has builds like this, but you can also search the forums yourself. If the title of the ROM says [OOS Cam] then the stock camera app is included.
You can also use ADB to debloat (remove) all google stuff from your phone. This is a guide which could be helpful: https://forum.xda-developers.com/t/...bloating-thread-for-the-s20-u-series.4089089/
This way, you can keep the same stock software without having to go through the hassle of installing a custom ROM

GolovaRaoul said:
Hey there!
Loading up to 47% and then throwing an error is actually quite normal, it should still succeed.
Click to expand...
Click to collapse
Oh thank you, that is very satisfying to know. Why is that?
GolovaRaoul said:
Anyway, some intelligent person was able to manage to move the stock OOS cam to custom ROM's. I'm currently running Nameless which is Android 12 which has the OOS cam.
Click to expand...
Click to collapse
Are you thinking of this one: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/ That's the 7 Pro App, which is crashing on my friend's phone on Lineage OS in macro mode
GolovaRaoul said:
Since you asked for a non-gapps build, you should look for a 'pristine' or 'vanilla' build. I know out of the top of my head that StagOS has builds like this, but you can also search the forums yourself. If the title of the ROM says [OOS Cam] then the stock camera app is included.
You can also use ADB to debloat (remove) all google stuff from your phone. This is a guide which could be helpful: https://forum.xda-developers.com/t/...bloating-thread-for-the-s20-u-series.4089089/
Click to expand...
Click to collapse
Great, thank you! As I got Magisk running, I prefer the debloater as I can play with it without Laptop access
GolovaRaoul said:
This way, you can keep the same stock software without having to go through the hassle of installing a custom ROM
Click to expand...
Click to collapse
Thank you for all your help!

lai.sha said:
Oh thank you, that is very satisfying to know. Why is that?
Are you thinking of this one: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/ That's the 7 Pro App, which is crashing on my friend's phone on Lineage OS in macro mode
Great, thank you! As I got Magisk running, I prefer the debloater as I can play with it without Laptop access
Thank you for all your help!
Click to expand...
Click to collapse
Eeehm I don't know why it gets stuck at 47%. It's a common issue, you can google it and you'll find lots of results
{
"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 mean these ROM's for example. Maybe some of these ROMs in the list also have the OxygenOS cam but I don't know. They are pre-built into the ROM so you don't need to do anything, just install the ROM and you should have the OxygenOS cam also

GolovaRaoul said:
Eeehm I don't know why it gets stuck at 47%. It's a common issue, you can google it and you'll find lots of results
View attachment 5742135
And I mean these ROM's for example. Maybe some of these ROMs in the list also have the OxygenOS cam but I don't know. They are pre-built into the ROM so you don't need to do anything, just install the ROM and you should have the OxygenOS cam also
Click to expand...
Click to collapse
Interesting, I thought that maybe that's what you meant but I wasn't sure if it just means "compatible" with...
Thank you so much, I guess it's time to play