Develop Bugs

mobile installer application popup restarting phone?

About once a week, not really sure on the frequency, (if I notice the popup) it says it rebooting the phone with two toggles on the bottom of the box. (box and lettering all in black and white) Your choice on the toggles is reboot or later. Today I push later and it it popped up twice more. But on the third time, there was not toggles and was doing a count down for reboot.
Anyway, before it rebooted, I pulled down the notifications and and found the notification and did a long press on it and then went into info. I then it looked like I was in settings with two choices there. (when on this settings, there was not back button to see were I was at in settings) To block notifications with on or off and the other doing something with quite mode. I turn off notifications and minimized the box. After it rebooted, the box was still minimized until wanted to bring it back up in the screen, it disappears. Anyone know what this is??? or know how to figure out what's doing it?
Stock Sprint Note 4 running 5.1.1 software Ok1 with hotspot hack (why I'm not running current software)

Open root browser and see if you have this folder: /carrier/ItsOn
If so, you may also have this file in dalvik (i think that's the proper location for Lollipop but you could search keyword itson) : /data/dalvik-cache/carrier @itson@[email protected]@classes.dex
If your ROM is fully stock, you may have another folder at /system/vendor/ItsOn. If so, look inside that folder for resource zip. Extract that zip and look in the folder and file install locations then browse to those in your phone's folders and delete all that correspond to that mapping.
If you have those, delete all you find and reboot. Hopefully that cures the random reboots.
If this applies, ItsOn has a bootstrapper that tries to install itself. If you have a custom kernel, it cannot complete this process but will try repeatedly to complete that failed setup process, prompting you continually reboot. If you were to factory reset, the prompts would most likely be more persistent.
If you flash a stock tar, then flash custom ROM and don't wipe internal memory, ItsOn remains unless developer has a script in place to remove that from root of your carrier folder.
Sent from my SM-N910P using Tapatalk

Thanks for the info. Phone is not rooted, bone stock with the exception of the hotspot hack.
Only thing I found using File Viewer under Root (/) folder /system/vender/Itson. And it shows nothing is in there and one year old.
I believe all this started when I upgrade Lollipop about one year ago. Was rooted at the time and wanted the newer android. Then I found out I did not need to root to get the hotspot working.

btb601 said:
Thanks for the info. Phone is not rooted, bone stock with the exception of the hotspot hack.
Only thing I found using File Viewer under Root (/) folder /system/vender/Itson. And it shows nothing is in there and one year old.
I believe all this started when I upgrade Lollipop about one year ago. Was rooted at the time and wanted the newer android. Then I found out I did not need to root to get the hotspot working.
Click to expand...
Click to collapse
OK. Check ItsOn status next. Goto /data/local/tmp and look for ItsOn log. It shouldn't get added on boot if you've removed it but last successful bootstrapper log will be present, unless deleted.
FWIW, I don't have random reboots on rooted phone. When I had them, ItsOn was the culprit. I usually clean install, wiping internal memory before and after stock tar but didn't coming from Lollipop.
What I noticed was that ItsOn showed in hidden menu ##data# as NetworkSystemProvider. See before and after wiping internal memory screenshots. I suspect this carried over from Lollipop. Perhaps yours did too?
{
"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"
}
Sent from my SM-N910P using Tapatalk

I could not find /data/local/tmp and look for ItsOn log, but I did get into data and the NetworkSystemProvider is there. Got into in and hit button for more settings and little window say "intent sent."
Also under more settings it says two things,
Module 1 is insmoded
Module 2 is insmoded
And at the top, it has a green icon for on button and a blacken icon for the off button. It will not let me do crap there.
Since it's stock, I have done nothing to it. Can't remember how I did the update. My guess since it was rooted, I had to flash OK1 myself but I don't see my stock download from Samsung. I have major memory issues, way more than I should at my age and I have no idea on how I did things......LOL And not even sure what Itson is, only thing I found with quick search a sprint software to add software and updates easily. That would explain the random downloads and install I did not do.
So now what, I need to root my phone to make this go away? Oh, and thanks again for your help. Don't go out or your way to dig further. I'm wanting to upgrade to MM but don't know much about it (rootable or hotspot wise).

The way I got rid of it was to wipe data and internal memory, flash marshmallow stock tar and wipe both again and flash a ROM that has it removed. Dunno but maybe it works the same way with a TWRP backup if you prefer stock with hotspot only?
I can't confirm there's another method or if that's your problem. But my random reboots are gone. FWIW, my log was inactive but had an existing log that dated months back. I only had a few random reboots until I did a factory reset to see if that would help. Once I did that, the reboots were much more frequent. Some boots were resulting in immediate request to reboot again. I had to do something at that point.
I couldn't tell you if updating to marshmallow makes it better but you could still could go back to Lollipop if it didn't.
I dunno if you need to root to make it go away but I can tell you there is hotspot mods for marshmallow. You can go back to Lollipop if you don't like marshmallow.
Sent from my SM-N910P using Tapatalk

Thanks again, guess I'll give marshmallow a try here real soon. Maybe even try a custom rom, never played with any of those. But I getting to where I'll have to do something soon. I feel it's picking up the pace. Then again, new Notes will be coming out soon. We'll see what Samsung brings us. Thanks again.

btb601 said:
Thanks again, guess I'll give marshmallow a try here real soon. Maybe even try a custom rom, never played with any of those. But I getting to where I'll have to do something soon. I feel it's picking up the pace. Then again, new Notes will be coming out soon. We'll see what Samsung brings us. Thanks again.
Click to expand...
Click to collapse
I've had this happen before and the only way I was able to get rid of it was to flash a completely stock tar and let the device provision itself thru initial setup. Others have had luck with the removal of ItsOn, but this has happened on ROMS where ItsOn wasn't even present.

ianmb said:
I've had this happen before and the only way I was able to get rid of it was to flash a completely stock tar and let the device provision itself thru initial setup. Others have had luck with the removal of ItsOn, but this has happened on ROMS where ItsOn wasn't even present.
Click to expand...
Click to collapse
Thanks, I do just that when I decide where to go from here.

[OFFICIAL] LineageOS 18.1 for the Moto G7

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto G7
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Moto G7.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
river
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_sdm632

I've heard that some people, including myself, have had issues with upgrading to 18.1 on some devices because it results in a broken lock screen. Is this an issue with 18.1 on the G7? I just want to make sure before I upgrade.

NTGDeveloper said:
I've heard that some people, including myself, have had issues with upgrading to 18.1 on some devices because it results in a broken lock screen. Is this an issue with 18.1 on the G7? I just want to make sure before I upgrade.
Click to expand...
Click to collapse
In my case, at the moment it is working well, I am still testing it.
You should try to report the bug:
"Find any? Report them according to this guide"

NTGDeveloper said:
I've heard that some people, including myself, have had issues with upgrading to 18.1 on some devices because it results in a broken lock screen. Is this an issue with 18.1 on the G7? I just want to make sure before I upgrade.
Click to expand...
Click to collapse
Only on really really old devices like bacon , etc.

npjohnson said:
Only on really really old devices like bacon , etc.
Click to expand...
Click to collapse
Thanks for letting me know. I decided to go with a clean flash anyway just because I think my encryption on my data partition was preventing boot and restoring from a 17.1 nandroid backup broke the system completely. So far, the ROM is very good and I'm happy that I'm now on Android 11!

I flashed this the other night and the ROM seems to be working well. I have a question about updating the Lineage OS recovery though. I am used to flashing via TWRP, but decided to go with the Lineage OS recovery this time. In TWRP if I want to update TWRP itself, I would download the twrp-XYZ-123.img to the device, and flash the image in TWRP. I cannot see this option anywhere in the Lineage Recovery UI. Do I have to do it in ADB like the initial install of the ROM? Is there another way to update the recovery? Is it even necessary to do the recovery update (I can't find a changelog for the Lineage OS Recovery on the lineage site), I don't want to bother with an ADB recovery flash every week if nothing is actually changing in the recovery image.

PMDPhD said:
I flashed this the other night and the ROM seems to be working well. I have a question about updating the Lineage OS recovery though. I am used to flashing via TWRP, but decided to go with the Lineage OS recovery this time. In TWRP if I want to update TWRP itself, I would download the twrp-XYZ-123.img to the device, and flash the image in TWRP. I cannot see this option anywhere in the Lineage Recovery UI. Do I have to do it in ADB like the initial install of the ROM? Is there another way to update the recovery? Is it even necessary to do the recovery update (I can't find a changelog for the Lineage OS Recovery on the lineage site), I don't want to bother with an ADB recovery flash every week if nothing is actually changing in the recovery image.
Click to expand...
Click to collapse
Why aren't you using the .zip? Because the linage recovery doesn't do .IMG files I would guess. The .zip is on the twrp , also the .zip can be flashed with magisk

One thing I'm starting to hate about 18.1 is they dropped the option to Kill App by holding back button in developer settings. This may actually be a deal breaker for me, I dont think I can make it without this feature.. Shiat!

Droid4200 said:
Why aren't you using the .zip? Because the linage recovery doesn't do .IMG files I would guess. The .zip is on the twrp , also the .zip can be flashed with magisk
Click to expand...
Click to collapse
I am very new to Lineage OS Recovery. Always used the .IMG files with TWRP. I don't know how to flash a recovery in Lineage Recovery at all, and could not find any instructions anywhere. I did not know I could flash a recovery as a .Zip. I also just realized that my initial question is kind of moot because there is an option in the built in updater in Lineage OS 18.1 to flash both the update and recovery, so my Lineage OS Recovery is already the latest version from 4-4-21, and I won't have to figure out how to flash it. Though it would be useful to know in general.

PMDPhD said:
I am very new to Lineage OS Recovery. Always used the .IMG files with TWRP. I don't know how to flash a recovery in Lineage Recovery at all, and could not find any instructions anywhere. I did not know I could flash a recovery as a .Zip. I also just realized that my initial question is kind of moot because there is an option in the built in updater in Lineage OS 18.1 to flash both the update and recovery, so my Lineage OS Recovery is already the latest version from 4-4-21, and I won't have to figure out how to flash it. Though it would be useful to know in general.
Click to expand...
Click to collapse
Yes the zip makes it so much easier now. If you use the lineageos built in update process you will lose TWRP, download the zip and you can very quicky just reboot to recovery after a lineageos update, then install the twrp.zip . you will lose root so you just reinstall majisk(if you use majisk, it'll keep your modules and settings). There may be a twrp retain script, but I haven't messed with them yet, the reinstall of twrp and majisk is pretty fast (plus I'm used to doing it the old way, sort of like you with the .IMG)

Mostly seems pretty good. Broke "LawnChair2" launcher, but, that seems to be a problem of LawnChair going dormant; Hyperion is working o-k so far as a replacement, with some hassles converting. The OK Google voice activation for Assistant still doesn't work and I can't find any fixes, but that was true on 17.1 also. I *hate* the zooming wallpaper effect, makes it very hard to exactly position wallpaper vs. icons. That is an Android 11 "feature" though, so no getting around it...

Hi there. I upgraded 17.1 to 18.1 recently. Seems working fine on first day until I installed vanced app (i think).
Now, every time the screen go off and when it back on, i see glitches and bad palette color. And can't fix it without a reboot (and then when the screen go off the screen glitches comes back)
Maybe is related with Vanced and microG, any one has this issue too?

TomOehser said:
Mostly seems pretty good. Broke "LawnChair2" launcher, but, that seems to be a problem of LawnChair going dormant; Hyperion is working o-k so far as a replacement, with some hassles converting. The OK Google voice activation for Assistant still doesn't work and I can't find any fixes, but that was true on 17.1 also. I *hate* the zooming wallpaper effect, makes it very hard to exactly position wallpaper vs. icons. That is an Android 11 "feature" though, so no getting around it...
Click to expand...
Click to collapse
New issue - seems I get into a situation where the notification light and a notification sound are coming without any notifications - even if "use notification light" is disabled... mystified at what is doing this so far, trying to figure it out. Also, Lawnchair mysteriously seems to be working...

FoxShadow said:
Hi there. I upgraded 17.1 to 18.1 recently. Seems working fine on first day until I installed vanced app (i think).
Now, every time the screen go off and when it back on, i see glitches and bad palette color. And can't fix it without a reboot (and then when the screen go off the screen glitches comes back)
Maybe is related with Vanced and microG, any one has this issue too?
Click to expand...
Click to collapse
The display glitches with the messed up color palette might be the same bug from 17.1. To fix that I had to change the Color mode from Saturated to Boosted and it stopped.
Settings > Display > Advanced > Color
Might be a different path in Android 11, though.
Basically if the inverted color thing happens again, going to that setting and switch it to a different Color type will reset the colors back to normal without restarting. After doing that once or twice it hasn't happened after. Again, on 17.1, can't speak to 18.1 yet.

Working fine after a week of daily use. Upgrade from 17.1 was simple by following the instructions.
The only issue I had was with Magisk. When I installed version 22.0 after upgrading successfully to 18.1, the device would get stuck on the LineageOS boot logo. After removing all modules using adb ("adb wait-for-device shell magisk --remove-modules", then boot the device), things got back to normal. Reinstalling the modules in Magisk did not create any more issues.
Overall, a very good ROM. Thanks for the effort of creating and maintaining it.

I have an issue with "Do Not Disturb" schedules not turning off. They turn on fine but are still running the following day after the supposed end-time. I'm getting round it with Tasker, so it's not a big deal.
Thanks for maintaining the ROM and updating to version 11.

PMDPhD said:
I flashed this the other night and the ROM seems to be working well. I have a question about updating the Lineage OS recovery though. I am used to flashing via TWRP, but decided to go with the Lineage OS recovery this time. In TWRP if I want to update TWRP itself, I would download the twrp-XYZ-123.img to the device, and flash the image in TWRP. I cannot see this option anywhere in the Lineage Recovery UI. Do I have to do it in ADB like the initial install of the ROM? Is there another way to update the recovery? Is it even necessary to do the recovery update (I can't find a changelog for the Lineage OS Recovery on the lineage site), I don't want to bother with an ADB recovery flash every week if nothing is actually changing in the recovery image.
Click to expand...
Click to collapse
much easier - Updater app in Settings, three dot menu, "Update recovery alongside OS"

kelue said:
The display glitches with the messed up color palette might be the same bug from 17.1. To fix that I had to change the Color mode from Saturated to Boosted and it stopped.
Settings > Display > Advanced > Color
Might be a different path in Android 11, though.
Basically if the inverted color thing happens again, going to that setting and switch it to a different Color type will reset the colors back to normal without restarting. After doing that once or twice it hasn't happened after. Again, on 17.1, can't speak to 18.1 yet.
Click to expand...
Click to collapse
Thank you! I will try that next time. I had to go back to 17.1 by now, that never happend to me on 17.1

FoxShadow said:
Thank you! I will try that next time. I had to go back to 17.1 by now, that never happend to me on 17.1
Click to expand...
Click to collapse
For me, if it happens, it happens shortly after booting, then a quick reset by changing the color setting will fix it, and it won't happen again until the next reboot. I noticed it happen once after plugging the charger in a minute or so after boot so maybe it's hardware related, I don't know.

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.