Develop Bugs

[ROM][Lineage 16.0 Unofficial][Pixel 2 XL/Taimen][06-09-19]

Hi all. Since I haven't gotten any word as to when there will be official support, I wanted to go ahead and share a build of Lineage OS 16.0 for our Pixel 2 XL/Taimen. It's a completely stock build. If it's working for enough people, then I'll continue to provide builds until/unless we get official support. If you find an error, please try to post logs via logcat to aid in fixing it (better yet to submit it to the Lineage OS team directly as well).
{
"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"
}
Steps for First Install:
Flash latest google image
Boot using the latest version of TWRP: https://dl.twrp.me/taimen/twrp-3.2.3-1-taimen.img.html
Wipe cache and data
Flash latest ROM .zip file
Flash the TWRP installer: https://dl.twrp.me/taimen/twrp-pixel2-installer-taimen-3.2.3-1.zip.html
Reboot to recovery
Flash OpenGapps (Android 9.0, ARM 64, probably nano): https://opengapps.org/ or MindTheGapps: https://androidfilehost.com/?fid=3700668719832237178
If desired, flash a custom kernel
If desired, flash Magisk
Reboot and hopefully enjoy
Steps for Updates:
Follow steps 4- 10 above. You can skip steps 1 - 3 (latest Google image, booting with TWRP .img, wiping) and optionally 7 (flashing Gapps).
Latest ROM, 06-09-19:
Download
Old Releases:
Old Download
I usually like to provide updates every ~2 weeks or month to keep up with security updates and/or anything else important. Thanks for trying and God bless .
Special thanks to @draymond1987, @RaymanFX, and all the other developers for their continued hard work.
View changelog up to build date
/.repo/local_manifests/roomservice.xml is attached

A quick note: If you seem to get stuck on the Gapps setup wizard, you can touch each corner of the screen, going clockwise, starting in the top left corner, to skip it. I've seen the data transfer tool have issues lately. You can uninstall it and continue afterwards.

Any known bugs?

pimpdaddy00 said:
Any known bugs?
Click to expand...
Click to collapse
I had an issue at some point where it would shut off when unplugged, but I don't know if it was just something about how my phone is setup. The other thing I encountered was the setup wizard getting stuck before (but fixed after removing the data transfer tool manually later). I'm hoping to see someone else have it working as I know at some point I was able to boot without issue, other than Magisk possibly not working without flashing another custom kernel. Getting any feedback from logs would helpfully tell me what changed and possibly where to fix it at that point.

I checked the channelog and noticed a few minor changes that seemed nice. Overall, I just hope Active Edge gets working in future ROMs lol. Though I know it's difficult. Good job on this!

Can't even get this to boot.

LLStarks said:
Can't even get this to boot.
Click to expand...
Click to collapse
Do you see the lineage OS logo and then blank screen or very shortly after? I've been facing an issue where it looks like com.qualcomm.qti.telephonyservice stops due to not loading a reference properly if I'm not charging. Thanks for letting me know you've had issues.

I could never get past the Lineage logo. Initial boots are usually long, but it would just crap out and reboot to whatever recovery I put in.

LLStarks said:
I could never get past the Lineage logo. Initial boots are usually long, but it would just crap out and reboot to whatever recovery I put in.
Click to expand...
Click to collapse
Good news all! It looks like the boot issue and modem service failure is fixed. I installed it on my phone and it seems to be stable. Sorry for any/all frustration with the previous build. Hopefully all who have been waiting can use it now:
https://androidfilehost.com/?fid=11410963190603877722

calsurferpunk said:
Good news all! It looks like the boot issue and modem service failure is fixed. I installed it on my phone and it seems to be stable. Sorry for any/all frustration with the previous build. Hopefully all who have been waiting can use it now:
https://androidfilehost.com/?fid=11410963190603877722
Click to expand...
Click to collapse
Thanks a bunch! Flashing now!

Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?

tranna said:
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
Click to expand...
Click to collapse
Could try flashing a different gapps package. I always used the mini

tranna said:
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
Click to expand...
Click to collapse
I think I went to app info and told it to force stop. If it's on the data transfer utility, I just told it to uninstall (as it seemed to be the culprit for me). I think I either reset/restarted or continued with the pixel setup after that. Either way, just getting to the data transfer utility from within setup or on the apps list and uninstalling it was the trick for me.

Trying this out today for the first time. WiFi calling isn't working, UK EE. Got google apps nano working but had to force quit the setup a few times. Otherwise its looking really nice, thanks!

Hi again all. I just wanted to let all of you who are using this ROM know that I'm planning on updating it very soon. I've been waiting for Google to release security patches for this month, but if I don't see them soon then I'll build with the latest Lineage OS changes anyhow.

On the 2nt or 3rd post is said to tap all for corners of the screen clockwise from top left and it will skip setup, then go into apps and uninstall the data transfer tool. When you do that it will let you move forward with the setup and still let you transfer anyway you want. Hope this helps.

It's amazing! I like it! Thank you so much

Hi again. Here's the latest build of the sources as of today:
https://androidfilehost.com/?fid=11410963190603892886
Something to note is that when I installed it, I simply went to recovery, flashed the new ROM .zip, then flashed the TWRP installation zip again. After that, I rebooted to recovery and installed Magisk again.
For some reason once I booted, the google play store was missing (even though previously having installed OpenGapps along with the previous ROM version). I went back to recovery, reflashed OpenGapps, and it was back again (along with having to go through setup once again, including removing the data transfer tool). Some of the apps (mostly Google's) wouldn't open correctly until I uninstalled and reinstalled them again). My Google account also wasn't present, so I had to add it back as well.
If you come across that same problem, these steps should work, otherwise you might want to just try a fresh install (wiping the old cache and data while in recovery). For anyone who comes up with an easier solution, could you please be sure to share what you did? Everything is still working fine afterwards, but it was just annoying to have to uninstall and add things back. I didn't use the latest OpenGapps, so that might have just been my problem.

I'm unable to complete the setup, since the setup always crashes after adding a google account. It will ask me if I want to select a backup from the cloud or skip, and any option I pick will crash the setup. As a result, Pixel Launcher will not work (maybe that's another issue entirely?) other than that, rom works.

Was wondering if anyone had had any problems with the now playing? I get a pixel ambient services keeps stopping when I ask the assistant but it will tell me the song name. But now playing seams to not work at all. I did try uninstalling the ambient services and reinstall it with no change.

[ROM][10] Lineageos 17.1 [Official] Pixel 3a "Sargo"

Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org

Horninho10 said:
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
Yes, it runs nice and smooth, I was recently on LOS.

The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?

pojr said:
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
Click to expand...
Click to collapse
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.

MoistPicklez said:
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
Click to expand...
Click to collapse
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10

pojr said:
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
Click to expand...
Click to collapse
Test it out if you're interested, but A11 ROMs are likely around the corner. I bet we'll get a build or two of something else down the road. Cheers!

I've personally had GPS issues (while using OpenGapps Pico) with the official release. Hoping A11 builds fix it.

Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).

I seem to have overcome my GPS woes! My installation process was the following:
Install the last Android Q factory image
Flash LOS boot, go to recovery
Factory reset
Install update > adb sideload LOS zip
Very important(?) - go back to main menu, advanced, reboot to recovery
Install update > adb sideload opengapps pico zip > yes, install anyway
Sign in to your Google account during the initial setup process
Test GPS with an app (Google Maps, Waze, OSMAnd, Pokémon Go... )
The only issue I seem to have now is that the Google Fi app doesn't seem to get that my Fi service is ESIM based, and prompts me to order a physical SIM card, but playing with the mobile service settings seems to have gotten my service set up anyway.
EDIT: After talking with Google Fi support, going to Settings > System > Reset Options > Reset Wi-Fi, mobile & Bluetooth, check erase downloaded SIMs, then trying to activate Google Fi again in the app, it worked.

In addition to the helpful tips from @Mokura3rd. My two cents: I had some gps issues as well, but didn't test it to great extent. Here's a description of my (rather weird issue):
When I first installed Lineageos (jan16 - my previous comment), Google maps and Gps status were able to find gps signal (and quicky), but strava didn't find any gps signal (it didn't even ask for permission, which I granted manually - to no avail).
Some time after the first OTA update, I checked strava again. And it worked without issue. So there might have been merged some bugfixes that fixed gps issues on recent builds.

guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?

pojr said:
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
Click to expand...
Click to collapse
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.

MoistPicklez said:
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
Click to expand...
Click to collapse
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"

pojr said:
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
Click to expand...
Click to collapse
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)

MoistPicklez said:
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
Click to expand...
Click to collapse
did not realize we got a new twrp version. thats a step in the right direction. with that said, that info is good to know. i'm a lazy ass and prolly not gonna test out lineage os until it gets on 11 lmao.

For whoever needs it. I sure did after a derped update last week!
tl;dr install update, disable all modules before booting, get the latest recovery image and patch it, install with fastboot. long version below, just in case.
How To OTA With Magisk, Painlessly:
Open updater and download the OTA.
Press install and let it do its thing, but DON'T REBOOT YET.
Go to Magisk and disable all your modules.
Okay, you can reboot now. It might take longer than usual, it's a system update.
Open Magisk and note that it's no longer installed, don't panic.
Download the recovery image matching your update from here: https://download.lineageos.org/sargo
Open Magisk and patch the img you just downloaded.
Copy the magisk_patched_(random).img to a folder on your computer where you're able to access fastboot.
Reboot your phone to bootloader: either by the advanced power menu, enabled in developer settings, or by restarting and holding Volume Down while the phone boots up.
Open up your terminal/commandline/etc where you moved the image file.
Type the command "fastboot flash boot magisk_patched_*****.img", where the last part is the random string that got generated in the patching process. Press Enter.
After the command finishes, use the volume keys to scroll through the bootloader menu until you see "Start". Press the power button.
Your phone should reboot back to the OS, you can now go back to Magisk and re-enable your modules at your leisure.

So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##

harryharryharry said:
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
Click to expand...
Click to collapse
Just go into app settings and kill now & disable. I noticed that if you installl gapps, get rooted, setup the phone you prefer. Backup with google backup....use the lineage recovery to do a factory reinstall. Once you recover all the sim issues, installation issues simply stop.

nylar357 said:
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
Click to expand...
Click to collapse
The kernel issues might be because they're targeted toward Android 11, and LOS 17.1 is based on Android 10.

harryharryharry said:
[...] First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). [...]
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications.[...]
Click to expand...
Click to collapse
It happened to me the same way. I am in the German T-Mobile network. I also disabled 'SIM Manager'.
Unfortunately, I do not receive any 'missed call'-SMS in case the mobile phone was in flight mode.
I think the app could have something to do with it because everything fits on the ISP side. So far, I haven't found an option to reactivate the App in the settings. Apparently it's some kind of hidden app. Can someone help please?
EDIT: There is a "hidden" "System-apps" option in the app settings. Unfortunately the error still occurs.

Question What's the best way to install latest chinese beta?

Greetings!
I'm currently using the latest Stable rom for global (12.5.1), I'm rooted and I have TWRP, everything is working fine.
Don't ask me why lol, but I want to install the latest chinese beta (miui_ALIOTH_21.6.2_6d346564dd_11.0, https://xiaomifirmwareupdater.com/miui/alioth/weekly/21.6.2/), I copy the file to internal storage, boot into twrp, flash it, clean cache and reboot.
After those steps, the phone reboots and it enters in a semi-bootloop on the poco logo. The phone restarts a few times (like 5-6) and after that, it boots succesfully.
When it boots, it boots into the stable rom (12.5.1) and not the recently flashed chinese beta (21.6.2), does anyone knows why this happen? D=
Also as extra info, my device is global, so, there's no issue if I try to install a chinese beta, right?
Have an awesome day! =D

i'm probably not of much use here, but as no-one else has replied i'll tell you...!
i had the same issue but it was a while ago now, so i can't actually recall how i rectified it (sorry). but i think i either flashed the rom, then before booting to system, factory reset in twrp by typing 'yes'. then boot to system...
or, i flashed both slots, a and b with the rom zip. in twrp go to reboot, then you can see which slot is active. flash rom, then reboot to other slot in twrp. after changing to alternative slot i think i then, as i always do when changing slots in twrp, rebooted twrp itself to be sure alt slot is deffo active. then flash rom to alt slot. then, after both slots are flashed, factory reset typing 'yes' then boot to system...
like i say, sorry if that's a bit vague, i really can't recall the remedy. good luck

reg66 said:
i'm probably not of much use here, but as no-one else has replied i'll tell you...!
i had the same issue but it was a while ago now, so i can't actually recall how i rectified it (sorry). but i think i either flashed the rom, then before booting to system, factory reset in twrp by typing 'yes'. then boot to system...
or, i flashed both slots, a and b with the rom zip. in twrp go to reboot, then you can see which slot is active. flash rom, then reboot to other slot in twrp. after changing to alternative slot i think i then, as i always do when changing slots in twrp, rebooted twrp itself to be sure alt slot is deffo active. then flash rom to alt slot.
like i say, sorry if that's a bit vague, i really can't recall the remedy. good luck
Click to expand...
Click to collapse
Let me try that!
Also, and just to clarify, I want to flash the latest chinese beta because I want to use Arrow OS without any issues.
As I said, I'm currently running the latest stable MIUI, and If I flash Arrow OS on top of it, I face a looooooot of random crashes/reboots, to the point that I can't do anything on it.
Nothing fails when I use the stable beta, so I don't really know why this is happening. D=

Kimbaroth said:
Let me try that!
Also, and just to clarify, I want to flash the latest chinese beta because I want to use Arrow OS without any issues.
As I said, I'm currently running the latest stable MIUI, and If I flash Arrow OS on top of it, I face a looooooot of random crashes/reboots, to the point that I can't do anything on it.
Nothing fails when I use the stable beta, so I don't really know why this is happening. D=
Click to expand...
Click to collapse
i'm in that exact boat, running arrowOS with 21.6.2 XiaomiEU flashed before hand. i had my first and only rr today, not sure what caused it. no biggy though, i can live with one... but i have had a few audio issues. it's a bit weird, but audio over bluetooth cuts out every few seconds... until, and this is the odd part, i launch whatsapp and make a video call (found out by chance). after that bluetooth audio works fine. needs repeating after each reboot.
i didn't complain/report the rr or audio issue as i'm not using an early build of miui as a base ie 12.03 etc.

reg66 said:
i'm in that exact boat, running arrowOS with 21.6.2 XiaomiEU flashed before hand. i had my first and only rr today, not sure what caused it. no biggy though, i can live with one... but i have had a few audio issues. it's a bit weird, but audio over bluetooth cuts out every few seconds... until, and this is the odd part, i launch whatsapp and make a video call (found out by chance). after that bluetooth audio works fine. needs repeating after each reboot.
i didn't complain/report the rr or audio issue as i'm not using an early build of miui as a base ie 12.03 etc.
Click to expand...
Click to collapse
I'm gonna try flashing the latest firmware, as someone sugested on the Arrow OS thread, maybe (and hopefully) that'll fix bluetooth and proximity sensor issues.

Kimbaroth said:
I'm gonna try flashing the latest firmware, as someone sugested on the Arrow OS thread, maybe (and hopefully) that'll fix bluetooth and proximity sensor issues.
Click to expand...
Click to collapse
I'm interested in hearing your experiences.
I am still wondering if flashing a Chinese firmware on arrowos is really a good idea, even tho some ppl reported that it works fine.

4Style said:
I'm interested in hearing your experiences.
I am still wondering if flashing a Chinese firmware on arrowos is really a good idea, even tho some ppl reported that it works fine.
Click to expand...
Click to collapse
I flashed the pack for the lates fw, and I got some random reboots the first 2-3 times it booted, but after that it seems to be steady.
I can confirm that the proximity sensor issue is aaaaaaalmost gone, it stills fails but way less that before. The blutooth issues I still haven't tested em yet (I need to get into my car to do that).
So, yeah, it's safe to flash the latets fw: https://xiaomifirmwareupdater.com/firmware/alioth/weekly/21.6.2/
=)

Hello,
I am planning on getting the Chinese Rom as well, however, I am still waiting for my bootloader to unlock, about 72 hours left.
So what I got from the comments up there is you can flash the Chinese rom even if you are on Poco F3 and it is for Redmi k40 but you have to install the latest firmware first and that's it? Do you need to do something else first?
Not to mention the TWRP of course!
Apologies since I am kind of new to this thing
Thanks

sty2009 said:
Hello,
I am planning on getting the Chinese Rom as well, however, I am still waiting for my bootloader to unlock, about 72 hours left.
So what I got from the comments up there is you can flash the Chinese rom even if you are on Poco F3 and it is for Redmi k40 but you have to install the latest firmware first and that's it? Do you need to do something else first?
Not to mention the TWRP of course!
Apologies since I am kind of new to this thing
Thanks
Click to expand...
Click to collapse
You don't have to install the latest fw in order to get a working chinese rom install, but the latest fw always contains tweaks and stuff for many internal components (i.e. wifi, bluetooth, proximity sensors, etc), so yeah, that's recommended.
And yeah, you need to flash TWRP first, buuuuuut as reg66 said, you need to flash it on both of your phone slots (A and B), that way everything will work without issues. =)

hmm... just realised the weekly China (xiaomi EU) that i downloaded is different. didn't check your link in OP...
mine is xiaomi.eu_multi_HMK40_POCOF3_21.6.2_v12-11.zip from here
i usually check here xiaomi.eu for updates. if i were only flashing stock roms, i would only use the exact rom for my model/device ie poco f3 from here. other than that, for latest roms i would stick with xiaomi.eu roms...
anyway, i'll shut up now lol, i am a bit worse for wear and just waffling!!!

我使用的改名法，成功更新系统。
----------
MOD EDIT: English Translation Below
The name change method I used successfully updated the system.

丶铭丿昱 said:
我使用的改名法，成功更新系统。
----------
MOD EDIT: English Translation Below
The name change method I used successfully updated the system.
Click to expand...
Click to collapse
Does anyonw know what's the rename method?

Kimbaroth said:
Does anyonw know what's the rename method?
Click to expand...
Click to collapse
as a guess it's where you download the latest zip and rename it to 'update.zip' then put it in folder called 'downloaded_rom' and then update from settings or perhaps wait for prompt if set to auto update. can't say for sure though, haven't tried this method.
actually, just read, you can also rename the rom to update.zip and put in root of storage, then update via stock recovery... but again, i've not tried this method
EDIT: so there's no need to rename the zip. under settings, click on about phone/miui version and click the version multiple times until you get a message saying 'extra update features available' or something like that. click on the three dot menu on top right corner and click choose update package. navigate to your downloaded incremental update which from 12.0.3 global to 12.5.1 can be found here

reg66 said:
EDIT: so there's no need to rename the zip. under settings, click on about phone/miui version and click the version multiple times until you get a message saying 'extra update features available' or something like that. click on the three dot menu on top right corner and click choose update package. navigate to your downloaded incremental update which from 12.0.3 global to 12.5.1 can be found here
Click to expand...
Click to collapse
This is how I updated from 12.0.3 to 12.5.1, but only works from global to global (or same region to same region), if you try global to chinese, it doesn't work. =(

If CN ROM has a fastboot version u can use MiFlash tool (for safeness). Or TWRP for recovery ROM.

Kimbaroth said:
You don't have to install the latest fw in order to get a working chinese rom install, but the latest fw always contains tweaks and stuff for many internal components (i.e. wifi, bluetooth, proximity sensors, etc), so yeah, that's recommended.
And yeah, you need to flash TWRP first, buuuuuut as reg66 said, you need to flash it on both of your phone slots (A and B), that way everything will work without issues. =)
Click to expand...
Click to collapse
can you please guide how to flash latest chinese beta 21.7.13 here through TWRP and which TWRP is recommended and how to flash it on both of phone slots (A and B)?

Just intall Xiaomi.eu weekly ?
Why bother with an ad- and "analytics" infested unmodified china rom ?

The "Semi-bootloop" happened, because the bootloader detected that after a few trials Slot A is simply not bootable, so it switched to Slot B.
{
"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"
}

Development [ROM] PixelExperience [UNOFFICIAL] [12.1.0] [raven]

{
"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"
}
PixelExperience for Google Pixel 6 Pro[raven]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher mod, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.1
Whats working?
Everything I believe
Known issues
Not sure, none so far
DON'T FLASH GAPPS, IT IS ALREADY INCLUDED
Download
Install instructions
From custom recovery
** If not already installed, please download vendor_boot.img & flash via fastboot ( fastboot flash vendor_boot "location to downloaded file" ), then select boot recovery in fastboot after flash in finish.
vendor_boot.img
1. Factory Reset
2. Apply Update via ADB, sideloading the downloaded file
3. Reboot to bootloader
4. Apply Magisk Boot ( Patched Magisk Boot v25.2 )
5. Start
Donate
Not needed but always welcomed
Keep in touch
Telegram channel
PixelExperience blog
Android OS version: 12.1
Kernel Source

Awesome to see PE on the 6 Pro! Any chance it becomes Raviole or if there will be a Pixel 6 Oriole build as well?

Pixel-ception right there, experiencing Pixel on a Pixel lol

Always wanted to get a pixel experience on my pixel!

device and kernel source ?
@alvin14
​

Can someone who's tested this post a couple of screenshots of any special settings this might have over stock? I mostly want to compare those against DerpFest that was released a couple of days ago and to avoid flashing again since we don't have a way to backup and restore a rom at this point. Unless - could Slot B be used to dual boot two different roms?

Ulyaoth said:
Can someone who's tested this post a couple of screenshots of any special settings this might have over stock? I mostly want to compare those against DerpFest that was released a couple of days ago and to avoid flashing again since we don't have a way to backup and restore a rom at this point. Unless - could Slot B be used to dual boot two different roms?
Click to expand...
Click to collapse
Currently, you cannot dual boot multiple roms. I remember with OP6T, there was a guy/gal that provided us with a recovery that allowed dual boot for two different roms. It was a wip, but functioned pretty well. Can't recall the Dev's name.
Concerning screenshots of custom settings, I'm sure it's similar to other Pixel Experience roms for other devices. I can't provide any, because I'm not using this particular custom rom at the moment.

@alvin14 Please check your PM inbox. Thank you.
-Regards: Badger50

@alvin14, to sideload you'll need to provide both the boot.img and vendor_boot.img, otherwise we can't use adb sideload since stock recovery will reject it and it's looking pretty unlikely we'll get twrp anytime soon. For those of us who are technically minded, grabbing the 2 .img files I mentioned isn't too hard, but I'm guessing there's some who likely can't.
Also, you might want to provide your kernel source as per XDA rules like the mod has likely PMed you about. This thread will likely get removed/locked and your links taken down if you don't.

Sorry, have not done this since the S4. Kernel source added, forked from PE-Raven. Other files added as well. Not much options added to pixel experience, I personally prefer stock android which i did some development on about 8 years ago. Just light modifications added, very stable.

alvin14 said:
Sorry, have not done this since the S4. Kernel source added, forked from PE-Raven. Other files added as well. Not much options added to pixel experience, I personally prefer stock android which i did some development on about 8 years ago. Just light modifications added, very stable.
Click to expand...
Click to collapse
For the vendor_boot.img to even boot recovery, you need the boot.img from your build as well. Stock boot.img won't work in almost all cases of custom roms.
Appreciate the work, and newer devices are kind of a pain to know what to do. So I feel ya there.

dragynbane222 said:
For the vendor_boot.img to even boot recovery, you need the boot.img from your build as well. Stock boot.img won't work in almost all cases of custom roms.
Appreciate the work, and newer devices are kind of a pain to know what to do. So I feel ya there.
Click to expand...
Click to collapse
Boot not needed. After flashing vendor_boot via fastboot you can select boot bootloader and it goes straight in. Magisk Boot is also provided should anyone still need the boot image.

Ulyaoth said:
Can someone who's tested this post a couple of screenshots of any special settings this might have over stock? I mostly want to compare those against DerpFest that was released a couple of days ago and to avoid flashing again since we don't have a way to backup and restore a rom at this point. Unless - could Slot B be used to dual boot two different roms?
Click to expand...
Click to collapse
Isn't most things backed up online lately? Before every custom ROM flash, backup your data to Google & restore after flash. Don't really use much apps however I would believe they all offer online backup via Google. Signing back into everything should be a breeze since your passwords are also backed up wether to Google or whichever backup app used for that with auto sign in activated.

alvin14 said:
Isn't most things backed up online lately? Before every custom ROM flash, backup your data to Google & restore after flash. Don't really use much apps however I would believe they all offer online backup via Google. Signing back into everything should be a breeze since your passwords are also backed up wether to Google or whichever backup app used for that with auto sign in activated.
Click to expand...
Click to collapse
Yeah but there's still things that are either not backed up or not restored. For example call logs and device settings are backed up but they've never successfully restored on any of my devices. Then there are things like the pixel launcher home screen layout, signing in to apps, setting my ringtone etc., setting up a multilingual keyboard and so on. The ideal scenario for me is to be able to switch roms without wiping data, but I need to have a backup fallback or else it's going to take me hours of tweaking and setting management to be comfy(not to mention any ROM-specific settings that have crazy amounts of time-consuming customizations)

Ulyaoth said:
Yeah but there's still things that are either not backed up or not restored. For example call logs and device settings are backed up but they've never successfully restored on any of my devices. Then there are things like the pixel launcher home screen layout, signing in to apps, setting my ringtone etc., setting up a multilingual keyboard and so on...
Click to expand...
Click to collapse
I had to comment here because this is both true and not true. The backups seem to work, however, they usually don't restore ALL of said data when you restore from a backup onto a wiped phone. Oddly enough, when I wiped my phone yesterday and updated to the final Android 13 beta build (A13B4.1), I was able to restore my data and it kept all of my settings intact... So, not only did I get all of my apps back (and put onto the home screen in the correct locations), but I also got my home screen wallpaper set again; I got my QS tile's arranged how I had previously customized them and I got my other settings restored to how they were...
I'm not entirely sure why this occured, however, with a few past beta updates I had lost all of the settings that I had mentioned... I would usually only get my apps restored (without them being placed on the home screen at all)...
One thing to note is that I happened to do this update differently than a bunch of my previous updates. I did this update manually over adb instead of using the Android Flash Tool site. Of course, take this with a grain of salt as I'm not entirely sure if this is what made my backup restore yesterday so perfect. But my only thought is that by doing the update manually, you won't be missing out on any of the fastboot commands that may be dismissed via the Android Flash Tool

Wifi calling is missing in action..

yyz71 said:
Wifi calling is missing in action..
Click to expand...
Click to collapse
I don't have that feature in my country so I never looked into that.
Thanks will look into it.

alvin14 said:
I don't have that feature in my country so I never looked into that.
Thanks will look into it.
Click to expand...
Click to collapse
Thanks great ROM

BMHater12 said:
Pixel-ception right there, experiencing Pixel on a Pixel lol
Click to expand...
Click to collapse
dex2grigg said:
Always wanted to get a pixel experience on my pixel!
Click to expand...
Click to collapse
Awesome contribution! For all you give to the community i would like to buy you both lunch!
What is it exactly that trolls eat by the way?

NippleSauce said:
I had to comment here because this is both true and not true. The backups seem to work, however, they usually don't restore ALL of said data when you restore from a backup onto a wiped phone. Oddly enough, when I wiped my phone yesterday and updated to the final Android 13 beta build (A13B4.1), I was able to restore my data and it kept all of my settings intact... So, not only did I get all of my apps back (and put onto the home screen in the correct locations), but I also got my home screen wallpaper set again; I got my QS tile's arranged how I had previously customized them and I got my other settings restored to how they were...
I'm not entirely sure why this occured, however, with a few past beta updates I had lost all of the settings that I had mentioned... I would usually only get my apps restored (without them being placed on the home screen at all)...
One thing to note is that I happened to do this update differently than a bunch of my previous updates. I did this update manually over adb instead of using the Android Flash Tool site. Of course, take this with a grain of salt as I'm not entirely sure if this is what made my backup restore yesterday so perfect. But my only thought is that by doing the update manually, you won't be missing out on any of the fastboot commands that may be dismissed via the Android Flash Tool
Click to expand...
Click to collapse
I recommend Swift Backup. I've been using it for quite awhile and it backs up everything!! Call logs, messages, apps and their data. You can backup to the device and transfer to pc for safe keeping or you can even have the option to backup and restore from the cloud. You can also do what I do and get a OTG cable and backup and restore right from that which is much faster.

Development [ROM][UNOFFICIAL][raven/oriole/bluejay] LineageOS 20.0 for the Pixel 6 Pro/6/6a

{
"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 20.0 for the Pixel 6 Pro (raven), Pixel 6 (oriole), and Pixel 6a (bluejay).
Known issues:
NOTE: This is an early-stage build, and may not be the most stable. It's more stable than it was when I starting building.
The status bar is mis-aligned to the left by a few pixels, but this does not cause any usability issues, fortunately.
If you have issues receiving calls (i.e. calls go to voicemail often), flash stock, lock the bootloader, unlock it, and then flash my ROM. Relocking and unlocking usually fixes a corrupted baseband.
If you wish to pass SafetyNet, you may need MagiskHidePropsConfig with a stock fingerprint for your device. MHPC has the raven/oriole 12 (not 12L/13) fingerprints which may or may not work. Read updated section below
You tell me.
Passing SafetyNet/Play Integrity:
As an update, for some reason, this ROM only needs the Displax SafetyNet Fix and Shamiko (or DenyList) on top of Magisk in order to pass SafetyNet/Play Integrity, which is a nice bonus. While I daily drive a Pixel 7 (running my P7 Lineage build), Netflix shows in the Play Store with DSNF/Shamiko on oriole.
Flashing instructions:
Spoiler
Be sure you're on the latest stock 13 and have an unlocked bootloader. You may also be able to flash from GrapheneOS, CalyxOS, or another ROM.
Go into fastboot mode (turn off phone and then Power + Volume down)
Make sure you have the adb/fastboot tools
Run fastboot flash --slot all boot boot.img
Run fastboot flash --slot all vendor_boot vendor_boot.img
Boot into recovery
Press Factory Reset and confirm
Go to Apply Update -> Apply from ADB
Run adb sideload LOS_BUILD (Replace LOS_BUILD with your LOS ZIP file)
To add GApps, go to Advanced -> Reboot to Recovery -> Apply Update -> Apply from ADB
Run adb sideload GAPPS_BUILD (Replace GAPPS_BUILD with your GApps ZIP file, repeat this step if you want Magisk)
Press Reboot System Now
Download:
Pixel 6 Pro (raven)
Pixel 6 (oriole)
Pixel 6a (bluejay)
MindTheGApps
Sources:
Kernel
Device trees
Vendor

ChangeLog:
2022/11/18:
Yet again, new builds.
Update SafetyNet/Play Integrity section, apparently it's super easy to pass this check with my ROM, and I did nothing.
2022/11/10:
Long time, no see. I have a new build for oriole. Will upload raven and bluejay shortly. UPDATE: raven and bluejay are also uploaded.
A lot of stability issues are fixed, at least on oriole. Mainline LOS has made huge differences.
It should be usable as a daily driver, although I daily drive a Pixel 7 (which I will also build for, in another thread).
2022/10/23:
Okay, sorry for flip flopping, this ROM is not discontinued. The main reboot issue is gone. If you have issues coming from stock, try flashing GrapheneOS and then this LOS build.
New builds for oriole, raven and bluejay.
I am discontinuing this ROM, a lot of people had issues, so I decided to not continue public builds further. When LOS becomes more stable on raviole/bluejay, I may restart builds unless LOS becomes official by then.
2022/10/20:
New build, yay!
2022/10/14:
Rebuilt for bluejay/oriole/raven on a fresh tree. Some people have reported issues on the 20221013 build. If you had issues try my new 20221014 build. If you still have issues, I will probably "discontinue" this build.
2022/10/13:
Re-built, mainly for Pixel 6 Pro (raven) flashing issues)
Move from AFH to self-hosted mirror. AFH sucks, but I fortunately have symmetrical Gigabit at home.
2022/10/12:
Initial build

Reserved 2.

Reserved 3.

hey mate, unable to access the file to download it, screenshot below
Cheers

spyderr said:
hey mate, unable to access the file to download it, screenshot below
Cheers
View attachment 5733339
Click to expand...
Click to collapse
Try the new links. I accidentally gave the links for my use instead of public use. Sorry for this.

neelchauhan said:
Try the new links. I accidentally gave the links for my use instead of public use. Sorry for this.
Click to expand...
Click to collapse
No Dramas, thanks for your work.

The 20121012 zip will not open. The previous zips open.

taisau said:
The 20121012 zip will not open. The previous zips open.
Click to expand...
Click to collapse
Which one, raven, oriole, or bluejay?

neelchauhan said:
Which one, raven, oriole, or bluejay?
Click to expand...
Click to collapse
raven. the same problem from multiple download locations. also, the boot files result in boot loops, where the previous worked.

getting "adb sideload lineage-20.0-20221012-UNOFFICIAL-raven.zip
serving: 'lineage-20.0-20221012-UNOFFICIAL-raven.zip' (~0%) adb: failed to read command: No error" after getting the verification signature failure option.

Sorry for that. Try my new downloads.
They're not on AFH, since AFH is garbage. I am using my home Gigabit connection for the new downloads.
Also, if a USB 3.0 port is giving issues, try a USB 2.0 port on your computer

neelchauhan said:
Sorry for that. Try my new downloads.
They're not on AFH, since AFH is garbage. I am using my home Gigabit connection for the new downloads.
Also, if a USB 3.0 port is giving issues, try a USB 2.0 port on your computer
Click to expand...
Click to collapse
I usually go directly for the 2.0 port because 3.0 for whatever reason gives me an issue. And where are you hosting them? I can't see anything other than AFH
Edit: nvm I see it was updated will try again.
edit EDIT: Can confirm it is now flashing, AFH didn't have the 20221013 build and thats why i was having issues. thank you so much for bringing lineage 20! I feel giddy like a school girl flashing this! Brings me back to the days of cyanogenmod RIP.
EDIT EDIT EDIT: Can confirm device is boot looping, actually says device is corrupt and the recovery cant mount system for gapps so gapps fails. Thus upon just flashing with your steps and you keep pressing the power button, the device just hangs at the white google screen.

okay tried boot and vendor boot from rice droid and it did NOT says device was corrupted. however flashing gapps with lineage build 20222013 says cant mount system and fails to flash and then bootloops.

Twiggy000b said:
okay tried boot and vendor boot from rice droid and it did NOT says device was corrupted. however flashing gapps with lineage build 20222013 says cant mount system and fails to flash and then bootloops.
Click to expand...
Click to collapse
I've been here before.
First, go back to stock, upgrade to a beta build, and then back to the public build.
Then try flashing my ROM. You need my boot.img and vendor_boot.img, don't use the RiceDroid boot/vendor_boot since each ROM may be different.
Apparently multiple people are having issues, will ingestivate

I noticed a few people are having issues. Can you try going back to stock, flashing my boot.img and vendor_boot.img, a factory reset, and then flashing the ROM?
I forgot the factory reset step, my bad.
If that doesn't work, there is some help here on Reddit:
https://www.reddit.com/r/LineageOS/comments/u6g2w2
Basically what Reddit said is after booting LOS but before GApps, boot once, then go back to recovery, factory reset and flash GApps.

neelchauhan said:
I noticed a few people are having issues. Can you try going back to stock, flashing my boot.img and vendor_boot.img, a factory reset, and then flashing the ROM?
I forgot the factory reset step, my bad.
If that doesn't work, there is some help here on Reddit:
https://www.reddit.com/r/LineageOS/comments/u6g2w2
Basically what Reddit said is after booting LOS but before GApps, boot once, then go back to recovery, factory reset and flash GApps.
Click to expand...
Click to collapse
i have tried all the steps and still having the same issue.

Glad to see Lineage 20 on the 6 Pro. Will definitely flash when I am home from work Saturday and report back on how it goes. Hopefully these little glitches with flashing are ironed out by then. Thank you for this neelchauhan.

On the oriole build everything boots and sets up fine as long as I'm plugged to the computer. As soon as I unplug the phone reboots to recovery saying corrupt data and can't start system. This happened on the 12th and 13th builds

Sadly,
This site can’t be reached​mirror.neelc.org took too long to respond.