Develop Bugs

[ROM][unOFFICIAL] LineageOS 15.1 for Nexus 6P (angler)

{
"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, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki.
Important Info
To flash this rom you need TWRP 3.2.0-0 or newer. https://twrp.me/huawei/huaweinexus6p.html
Make sure you have the radio & bootloader img's installed from the stock oreo 8.1 OPM7.181205.001 Dec 2018 factory image.
They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
radio & bootloader img's: https://androidfilehost.com/?w=files&flid=286833
Those img's can be flashed with fastboot command.
Note: There's an issue happening to some angler users on custom oreo roms. The first boot after flashing rom your sim card might not be detected. It's easy to fix. Just go to lockscreen security settings and change it to 'none' and then reboot. Then you can change it back to whatever you want. This only happens one time when you first flash oreo.
Download Links
rom: https://download.lineageos.org/angler
Note: LineageOS servers no longer make 15.1 builds for any devices. You can use my unofficial builds here. My older builds are here.
Note#2: if you want to switch from an official build to my unofficial builds, follow instructions here.
google apps (optional): https://wiki.lineageos.org/gapps.html (Use arm64 / 8.1)
root su addon (optional): https://download.lineageos.org/extras Note: Use arm64 15.1 zip. After installing the su addon, you can enable root in developer options.
Instructions
If updating from old unofficial to newer unofficial, follow the steps below:
1. if you don't already have them installed, flash the newest radio and bootloader img's linked above.
2. boot into twrp and flash the rom zip.
Reboot & enjoy.
NOTE: if you previously flashed gapps and/or the su addon, there's no need to flash them again. They will be automatically re-installed during rom zip installation.
NOTE2: if you want to switch from an official build to my unofficial builds, follow instructions here.
If coming from a different rom:
1. if you don't already have them installed, flash the newest radio & bootloader img's linked above. also make sure you have the newest twrp, linked above.
2. boot into twrp and wipe system & data & cache.
3. flash rom & gapps & su addon zips (gapps & su zips are optional).
Reboot & enjoy.
Weather Provider Addon (Optional)
For those that like the lineage cLock widget, here's the OpenWeather apk you need to get weather info.
https://download.lineageos.org/extras
Grab the one for version 16.0. It also works with 15.1.
Note: You'll need an api key from OpenWeather.
LineageOS Stats
https://stats.lineageos.org/
Credits
Many thanks to my fellow LineageOS team members and all the contributors out there in the community. :good:
LineageOS device maintainers:
sam3000, razorloves
Source Code:
Device tree: https://github.com/LineageOS/android_device_huawei_angler/tree/lineage-15.1
Kernel tree: https://github.com/LineageOS/android_kernel_huawei_angler/tree/lineage-15.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_huawei/tree/lineage-15.1
Android version: 8.1.0 Oreo
Kernel version: Linux 3.10.73

Wooh! First!
Sent from my Nexus 6P using XDA Labs

Hey Razor. I used to be on your builds a couple of years ago in the old hammerhead and looking forward to flash your work again when 15.1 is out, this time on angler. Cheers! :fingers-crossed:

Any bugs? Is it suitable for daily driver? Just tired to wait for official build and want to flash as fast as possible. )

Thanks Razorl!!!!!

Error 7 -- make sure to flash the new twrp recovery if you face this issue!!

i42o said:
ERROR 7
Click to expand...
Click to collapse
Try reading the big bright red letters at the top, under "IMPORTANT INFO"

razorloves said:
Try reading the big bright red letters at the top, under "IMPORTANT INFO"
Click to expand...
Click to collapse
haha. Yeah my bad bro, my bad. got it tho, thanks!

Says no SIM card
Clean flash following instructions, TWRP 3.2, latest bootloader/radio/vendor, flashed vendor -> rom -> gapps. Otherwise no errors.
Any suggestions?

telefantastik said:
Says no SIM card
Click to expand...
Click to collapse
Forgot to mention in the first post. This has been happening on many custom ROMs.
An easy fix is to go to security settings and change screen lock to swipe or none, then reboot. That will remove the device protection that caused the no sim problem.
After the reboot, the problem is fixed and won't happen anymore. Then you can go back into security settings and change it back to whatever screen lock option you want.

razorloves said:
Forgot to mention in the first post. This has been happening on many custom ROMs.
An easy fix is to go to security settings and change screen lock to swipe or none, then reboot. That will remove the device protection that caused the no sim problem.
After the reboot, the problem is fixed and you can go back into security settings and change it back to whatever screen lock option you want.
Click to expand...
Click to collapse
It's weird though. I have unlock protection and got no issue when flashing this.
Can it also be related to your carrier or something?

ChemoNL said:
I have unlock protection and got no issue
Click to expand...
Click to collapse
Its not just caused by unlock protection. I posted details on the issue in my 14.1 thread about a month ago.

razorloves said:
Forgot to mention in the first post. This has been happening on many custom ROMs.
An easy fix is to go to security settings and change screen lock to swipe or none, then reboot. That will remove the device protection that caused the no sim problem.
After the reboot, the problem is fixed and won't happen anymore. Then you can go back into security settings and change it back to whatever screen lock option you want.
Click to expand...
Click to collapse
Awesome, it worked! Thanks

For those interested...
Another new version of twrp came out yesterday. 3.2.1-0
Here's the changelog for it https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
You can download it here: https://twrp.me/huawei/huaweinexus6p.html
Here's the changelog for 3.2.0-0 that came out last week, incase you missed it.
https://twrp.me/site/update/2017/12/01/twrp-3.2.0-0-released.html

Thank you for new thread and ROM.
:fingers-crossed::fingers-crossed::fingers-crossed:

Hi, looking to potentially begin using custom ROMs on my 6P to help combat some battery and performance issues I get. With future updates, do I have to keep manually flashing the radio, etc firmware or can I just OTA/DL zip of lineage and flash? Seems like a bit of a pain :/

domacikolaci said:
Hi, looking to potentially begin using custom ROMs on my 6P to help combat some battery and performance issues I get. With future updates, do I have to keep manually flashing the radio, etc firmware or can I just OTA/DL zip of lineage and flash? Seems like a bit of a pain :/
Click to expand...
Click to collapse
Hi, once a month you need to flash the new vendor for security updates
Google release them once a month (usually the first tuesday of the month)
However when you flash an update that does not require new vendor, you don't need to flash it
edit: just realised you're also from Melbourne, hi

Just have installed the last unofficial in my Angler, coming from another custom rom ( with Nougat). All good. Plan to stay here. Thanks !

Anyone having problems with the phone shutting down saying 0% battery when in reality you still have plenty of battery left? Just did a clean install and it happened after only installing chrome and whatsapp.

Apoena said:
Anyone having problems with the phone shutting down saying 0% battery when in reality you still have plenty of battery left? Just did a clean install and it happened after only installing chrome and whatsapp.
Click to expand...
Click to collapse
Have you been living under a rock for the past year? Lol jk. But see here http://www.androidpolice.com/2016/1...toff-problem-and-its-becoming-a-safety-issue/
tldr; blame Google and Huawei. And get yourself a free replacement or free upgrade.
http://www.androidpolice.com/2017/0...exus-6p-owners-pixel-xl-warranty-replacement/

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.

[MULTIPLE_ROMS_+_RECOVERIES][UNOFFICIAL][Android-11] d1q

{
"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"
}
Proudly Presents
Another Exclusive Release
Supported Model
*Snapdragon Only*
D1Q
Note 10
Recoveries
Batik Recovery
Dark Recovery
Nusantara Recovery
OrangeFox Recovery
PitchBlack Recovery
RedWolf Recovery
SkyHawk Recovery
TWRP Recovery
Roms
AICP
AospK
Arrow
Awaken
Baikal
CandyRom
Carbon
ExthmUi
Contributors
Thanks to @jrkruse & @afaneh92 & @klabit87 & @PizzaG
Device Downloads
Note 10 Downloads
Recovery Device Trees
Device Source
Rom Device Trees
Device Source
A-Team Website
A-Team Supported Devices
TeleGram Live Support
A-Team Digital Solutions​

Updates
4-27-2021: Added Aosip
5-3-2021: Updated TWRP, OrangeFox, PitchBlack & SkyHawk Recoveries
5-7-2021: Removed AosIp as it wouldn't boot, Fixed Telegram Link
5-22-2021: AICP reuploaded & AospK Added
5-23-2021: CandyRom Added
5-30-2021: Awaken Added, Arrow Added, Carbon Added
5-31-2021: ExthmUi Added
6-4-2021: Baikal Added

How do I install this exactly? I have a N970U Rooted with unlocked Bootloader (Thanks again Elliwigy). I crossed my fingers and installed it through TWRP, lol. According to TWRP it installed just fine but I then had a bootloop after wiping and rebooting, cool boot animation though, lol. I let it bootloop for a good 15 minutes twice. I then flashed this and still had root and unlocked bootloader so no harm done. Thanks to "bklyn_syed"
SM-N970U/U1/W Android R ROM
Disclaimer: Your warranty is now void. I am not responsible if you use this and brick your device or if your device blows up, implodes. Follow the instructions and you should be good. This is stock ROM with modifications. I do not own this...
forum.xda-developers.com

Gregbmil1 said:
How do I install this exactly? I have a N970U Rooted with unlocked Bootloader (Thanks again Elliwigy). I crossed my fingers and installed it through TWRP, lol. According to TWRP it installed just fine but I then had a bootloop after wiping and rebooting, cool boot animation though, lol. I let it bootloop for a good 15 minutes twice. I then flashed this and still had root and unlocked bootloader so no harm done. Thanks to "bklyn_syed"
SM-N970U/U1/W Android R ROM
Disclaimer: Your warranty is now void. I am not responsible if you use this and brick your device or if your device blows up, implodes. Follow the instructions and you should be good. This is stock ROM with modifications. I do not own this...
forum.xda-developers.com
Click to expand...
Click to collapse
which rom good sir? New booting batch is building and going up tonight. I apologize, took me a bit to get my whole infrastructure set up, tested and bugs worked out.

The Candy Rom and AICP Rom both flash in TWRP fine but then it boots to Download mode only. I'm on N970U. I've had root on other phones before but this is my first unlocked bootloader so I'm new to flashing custom roms. Is flashing it in TWRP with all default settings not the way to do it?
Thanks.

Gregbmil1 said:
The Candy Rom and AICP Rom both flash in TWRP fine but then it boots to Download mode only. I'm on N970U. I've had root on other phones before but this is my first unlocked bootloader so I'm new to flashing custom roms. Is flashing it in TWRP with all default settings not the way to do it?
Thanks.
Click to expand...
Click to collapse
sounds like you may have missed a step. Did you flash the AIO package after unlocking bootloader? Also did you wipe data? That is needed. Roms are tested booting, enjoy...

AIO package? Does not ring a bell so I assume that I didn't, lol. I will search for it, thank you!
I was not given a chance to wipe data before it went into Download mode. I went back to recovery manually and wiped but still would boot straight into Download

Gregbmil1 said:
AIO package? Does not ring a bell so I assume that I didn't, lol. I will search for it, thank you!
I was not given a chance to wipe data before it went into Download mode. I went back to recovery manually and wiped but still would boot straight into Download
Click to expand...
Click to collapse
They have them for the unlockaed devices on Telegram in the Samsung Unlocked Channel. You still have some security going, that's why the roms aren't booting. Hop on telegram and llok me up, I can add you to the group or look on here for it. Should be a package by @jrkruse

PizzaG said:
They have them for the unlockaed devices on Telegram in the Samsung Unlocked Channel. You still have some security going, that's why the roms aren't booting. Hop on telegram and llok me up, I can add you to the group or look on here for it. Should be a package by @jrkruse
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...ooth-and-fix-safetynet.4257737/#post-84784411

This did the trick, thank you!

Hello, nice to see snapdragon support four note10. Thank you very much.
Is there any information if the s-Pen is working in any/all of the roms?

Thanks for the great work.
Is there any plan to support for newer android versions? Really hoping to see android 12/12.1 on this snapdragon variant but no one makes it, and I don't have the ability and knowledge to bake it too...

Rocky7842 said:
Thanks for the great work.
Is there any plan to support for newer android versions? Really hoping to see android 12/12.1 on this snapdragon variant but no one makes it, and I don't have the ability and knowledge to bake it too...
Click to expand...
Click to collapse
not with the current state of ims and broken service. There is a beta test release of los 19 on Telegram but suffers from the same ims issues

Question installing custom rom through payload?

I've been looking around for roms for this model and tried out a few but I noticed some roms aren't just where you can fastboot install the zip. some roms have a big file named payload in the zip so the usual fastboot install doesn't work. so my question is how do you install a rom with the payload in it? I switched from galaxy devices to the pixel so this is new to me

bjf189 said:
I've been looking around for roms for this model and tried out a few but I noticed some roms aren't just where you can fastboot install the zip. some roms have a big file named payload in the zip so the usual fastboot install doesn't work. so my question is how do you install a rom with the payload in it? I switched from galaxy devices to the pixel so this is new to me
Click to expand...
Click to collapse
payload.bin is used in OTA updates (flashed using ADB).
Most ROMs have installation instructions so it's best to follow these. Most (if not all) custom Pixel ROMs require you to be on July Stock build and to wipe in recovery mode before flashing.
There are 2 ways to flash ROMs on Pixels: through fastboot or ADB side loading via recovery mode.
Check the instructions listed by the developer.

Alekos said:
payload.bin is used in OTA updates (flashed using ADB).
Most ROMs have installation instructions so it's best to follow these. Most (if not all) custom Pixel ROMs require you to be on July Stock build and to wipe in recovery mode before flashing.
There are 2 ways to flash ROMs on Pixels: through fastboot or ADB side loading via recovery mode.
Check the instructions listed by the developer.
Click to expand...
Click to collapse
I'm aware of the installation instructions the devs supply but only rom on xda I found was evolution and its been discontinued. the other roms I found were through telegram which Most do not supply instructions as far as I could see. I was looking into the hentai rom (strange name) or the sparkOS to try out but I'm stumped on the whole installation bit

bjf189 said:
I'm aware of the installation instructions the devs supply but only rom on xda I found was evolution and its been discontinued. the other roms I found were through telegram which Most do not supply instructions as far as I could see. I was looking into the hentai rom (strange name) or the sparkOS to try out but I'm stumped on the whole installation bit
Click to expand...
Click to collapse
You need to be very careful about installing full operating systems from unknown sources. You never know what is going to be hidden in there.
What you really should be doing is either compiling yourself from source, or using builds from well recognized suppliers with full source available, and with full REAL IDENTIFICATION available for those responsible for it. GrapheneOS, for example.

96carboard said:
You need to be very careful about installing full operating systems from unknown sources. You never know what is going to be hidden in there.
What you really should be doing is either compiling yourself from source, or using builds from well recognized suppliers with full source available, and with full REAL IDENTIFICATION available for those responsible for it. GrapheneOS, for example.
Click to expand...
Click to collapse
I came across the evolution rom here on xds to see it was discontinued but the thread lead me to find telegram that had numerous devs on it with the rom list for the pixel that included grapheneOS. I've noticed many devs here use telegram as well for roms and communications. I would think that in this case, it all seems legit

bjf189 said:
I'm aware of the installation instructions the devs supply but only rom on xda I found was evolution and its been discontinued. the other roms I found were through telegram which Most do not supply instructions as far as I could see. I was looking into the hentai rom (strange name) or the sparkOS to try out but I'm stumped on the whole installation bit
Click to expand...
Click to collapse
if you're looking for a custom ROM, I'd suggest you try Derpfest or Zephyrus. Both are listed in this forum and have great reviews. Installation instructions are provided for both (just flash via fastboot).
Every ROM available for Pixel 6 have installation instructions available. I've yet to see one without. There are more than 10 ROMs available. I suggest you join the telegram pixel 6 chat group and get some guidance there.

bjf189 said:
I'm aware of the installation instructions the devs supply but only rom on xda I found was evolution and its been discontinued. the other roms I found were through telegram which Most do not supply instructions as far as I could see. I was looking into the hentai rom (strange name) or the sparkOS to try out but I'm stumped on the whole installation bit
Click to expand...
Click to collapse
Hentai OS no instructions? In the channel or group, you can call for user guides then the bot will share a pdf. I'm using Hentai OS for few weeks now.
I'm now with bootloader locked since they also provide custom avb key to relock bootloader and still enjoying volte,vowifi in unsupported region). future update is yes through adb sideload while the phone in recovery mode

{
"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"
}

bjf189 said:
I came across the evolution rom here on xds to see it was discontinued but the thread lead me to find telegram that had numerous devs on it with the rom list for the pixel that included grapheneOS. I've noticed many devs here use telegram as well for roms and communications. I would think that in this case, it all seems legit
Click to expand...
Click to collapse
HERE doesn't make ANYTHING "legit". This is just a web forum, nothing is verified for safety.

Question [NEW ONEPLUS USER] - Happy to be amoung you.

Hello everyone, I just bought the OnePlus 9 Pro 5G LE2123 Dual SIM 12GB+256G. Due to my inexperience, I ask for considerations in reference to a possible procedure for obtaining Root + TWRP permissions. ​I also ask if obtaining root permissions invalidate the warranty with some alleged counter (for example samsung knox counter). ​In the previous smarphone ( samsung galaxy note 9 ) I corrupted the EFS IMEI file by mistake and I don't want to repeat the same mistake. Thanks to all the Admins of the topic for your attention, as I can't help but be happy to be part of your oneplus family ​​
{
"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"
}

[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com

Thank you so much my friend

Congratulations on your OnePlus 9 Pro! Enjoy!!

You are phenomenal, I am reading the best guide indicated above and it is perfect and very clear in its explanation. ​I have only three questions: ​
To possibly send it to assistance, would it be enough to just lock the bootloader and flash the original boot? ​
Is it essential to have twrp recovery? ​
What bekup operation should I do to avoid stumbling into some errors ( ex. EFS IMEI)? ​
​Thank you for your time.​

pronegate said:
You are phenomenal, I am reading the best guide indicated above and it is perfect and very clear in its explanation. ​I have only three questions: ​
To possibly send it to assistance, would it be enough to just lock the bootloader and flash the original boot? ​
Is it essential to have twrp recovery? ​
What bekup operation should I do to avoid stumbling into some errors ( ex. EFS IMEI)? ​
​Thank you for your time.​
Click to expand...
Click to collapse
Use the MSM tool to get back to stock.
I don't install TWRP, but boot it in temp mode for flashing etc.
SwiftBackup app for backing up apps and data, call logs and sms. Messed up data, MSM tool to factory and restore with SwiftBackup. Copy internal storage to PC for it's backup.....

Thanks friend
Other questions
In your experience, do you recommend staying on OOS 13 or immediately flashing some of the custom roms you recommend?
Before flashing the new custom rom, which partition should I wipe?
Once the new custom rom is installed, for ota updates is the same procedure with magisk to maintain root permissions?
Thank you for your time @TheGhost1951.​

pronegate said:
Thanks friend
Other questions
In your experience, do you recommend staying on OOS 13 or immediately flashing some of the custom roms you recommend?
Before flashing the new custom rom, which partition should I wipe?
Once the new custom rom is installed, for ota updates is the same procedure with magisk to maintain root permissions?
Thank you for your time @TheGhost1951.​
Click to expand...
Click to collapse
As for custom roms, it is just a matter of choice. I have seen people that are happy and seen some that have had problems. As for me I prefer stock because it is made specifically for your phone. Less chance of problems. If you install a custom ROM it is usually advisable to go into recovery and factory reset. That is the wiping that is talked about. Finally, go back and read the link I gave you on keeping root. Read it until you have a clear picture as to what you need to do...

TheGhost1951 said:
As for custom roms, it is just a matter of choice. I have seen people that are happy and seen some that have had problems. As for me I prefer stock because it is made specifically for your phone. Less chance of problems. If you install a custom ROM it is usually advisable to go into recovery and factory reset. That is the wiping that is talked about. Finally, go back and read the link I gave you on keeping root. Read it until you have a clear picture as to what you need to do...
Click to expand...
Click to collapse
Thank you for your time @TheGhost1951 ​

pronegate said:
Thank you for your time @TheGhost1951 ​
Click to expand...
Click to collapse
You are most welcome. Like I said, staying with stock roms are more trouble free. They are made for your phone. Custom roms are ok for the most part, but I have seen too many in the forums trying to run a custom ROM and having too many problems or it doesn't have everything the stock ROM has to begin with. On the OnePlus 9 Pro, there is one more little nugget I can offer the will give you full root that Magisk is short on. Once you are rooted with Magisk, send me a PM and I will clue you in on it....

Oh, by the way, you need to disable driver signing on windows PC from this link https://www.techpout.com/disable-driver-signature-enforcement/ and then search for and install latest OnePlus and Qualcomm USB drivers and install them. This way you can connect your phone to PC in ADB, Fastboot and EDL modes for maintenance tasks!

TheGhost1951 said:
You are most welcome. Like I said, staying with stock roms are more trouble free. They are made for your phone. Custom roms are ok for the most part, but I have seen too many in the forums trying to run a custom ROM and having too many problems or it doesn't have everything the stock ROM has to begin with. On the OnePlus 9 Pro, there is one more little nugget I can offer the will give you full root that Magisk is short on. Once you are rooted with Magisk, send me a PM and I will clue you in on it....
Click to expand...
Click to collapse
I INSTALLED THE DRIVERS AS GIVEN IN YOUR GUIDE
I WAIT VERY HURRY FOR THE ARRIVAL OF MY ONEPLUS 9 PRO. I WILL UPDATE YOU AS SOON AS I HAVE NEWS

I would recommend first testing Oxygen OS software, I thinks it is not necessary for most users to tinker with custom roms.
In some time you will discover if your needs are covered with official soft or not, I know Oxygen Os is not what it used to be, it is nor good nor bad, it just was so much better before merging with Oppo because it had its own dev team and they actually did care about users, now they pretend to but ignore important matters, just answer silly questions in their forums but always abstract and tasteless...
You can always root your phone and stay in Oxygen Os but with benefits of magisk, you can tinker with it staying in Oxygen OS, but beware, you need to dome some certain things in order to "trick" some sensitive apps to root, like banking, when it detects your phone is rooted some functions may not work for "safety reasons", read magisk tutorial and enable saferynet, magisk hide deny list and you will be good to go, pretty easy for certainly experienced user, if not feel free to ask, we all will be happy to help!

pronegate said:
You are phenomenal, I am reading the best guide indicated above and it is perfect and very clear in its explanation. ​I have only three questions: ​
To possibly send it to assistance, would it be enough to just lock the bootloader and flash the original boot? ​
Is it essential to have twrp recovery? ​
What bekup operation should I do to avoid stumbling into some errors ( ex. EFS IMEI)? ​
​Thank you for your time.​
Click to expand...
Click to collapse
When you have your phone in edl and recognized by the msm tool, you can press F8 and choose partitions to back up. Take a backup of modemst1/2, efs/persist and while you're in there, grab boot_a so you can inject magisk into that boot image for root.
After you select the partitions you want, press read back and they will be saved to C:\ - with the partitions backed up, even if you do manage to break something the msm tool can't fix, you'll have the originals to put back in place.
The password is oneplus, one word all lowercase.
I don't use twrp anymore but that's your choice. I also stay on oos11. Some stay on 11, some go to 13, some go custom rom. It just depends on what you want and need from your phone. For now, we have the last OnePlus phone with real custom rom support as the newer OnePlus phones don't have public msm tools for flashing or recovering from brick state