[GSI][UNOFFICIAL][11] Pixel Experience & Pixel Experience Plus - Moto G 5G ROMs, Kernels, Recoveries, & Other Devel

{
"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"
}
Pixel Experience for GSI
&
Pixel Experience Plus for GSI
What is this?
Pixel Experience is an AOSP based ROM with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Their 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 11
What is working?
Almost everything
Known issues
Same issues of Phh's AOSP
Download
Github
Telegram
Pixel Experience
Phh Treble
Translation
Help with project translation
Blog
Pixel Experience
Donate
jhenrique09
phhusson
AndyYan
eremitein
ponces​
Build author: ponces
Source code: PixelExperience
Device source code: device_phh_treble
ROM developer: jhenrique09
Contributors: Pixel Experience Team, phhusson, AndyYan and eremitein - all credits should go to them

Deleted

Sorry if noob, but which .img file am I flashing for this device? And does the .img include everything the typical .zip file ROMs include? system.img is one of like 10 files that get flashed. Thank you!

Vonsk said:
Sorry if noob, but which .img file am I flashing for this device? And does the .img include everything the typical .zip file ROMs include? system.img is one of like 10 files that get flashed. Thank you!
Click to expand...
Click to collapse
arm64 ab to system, but don't try to flash it. Our device uses super.img so just linking to a GSI is not really useful. No idea why this was posted.

So, does that mean we SHOULD NOT use this rom? Was about to flash it with TWRP.
And, if it's "bunk", why not have this lost removed?

I flashed it on my device but I had to also flash vbmeta as well. No issues for now. I'll link the thread where I got the vbmeta image from in a few minutes.

Here's the link:
[Guide] How to flash a Generic System Image on the Moto G Stylus
After a couple weeks of on and off searching the internet, I finally got a couple GSI ROMs from the treble forum to boot up; so I'm posting this guide in hopes it saves somebody else all the searching A couple things to note: You and only...
forum.xda-developers.com
EDIT: I'm looking into giving this a try, hopefully I won't hit a wall with the image not being signed by Google. Would be awesome to be able to dual boot both stock and GSI. https://developer.android.com/topic/dsu

GCPDetective said:
Here's the link:
[Guide] How to flash a Generic System Image on the Moto G Stylus
After a couple weeks of on and off searching the internet, I finally got a couple GSI ROMs from the treble forum to boot up; so I'm posting this guide in hopes it saves somebody else all the searching A couple things to note: You and only...
forum.xda-developers.com
EDIT: I'm looking into giving this a try, hopefully I won't hit a wall with the image not being signed by Google. Would be awesome to be able to dual boot both stock and GSI. https://developer.android.com/topic/dsu
Click to expand...
Click to collapse
Please let me know how it goes.
I joined the 5G group on Telegram and there happens to be a couple other roms imma try out

MattchuBlean420 said:
Please let me know how it goes.
I joined the 5G group on Telegram and there happens to be a couple other roms imma try out
Click to expand...
Click to collapse
Just to clarify, Pixel Experience already runs nicely for me, I only have issue with the Pixel Camera app port. What I was referring to giving a try was attempting to install Pixel Experience via Dynamic System Update for a dual boot experience.

GCPDetective said:
Just to clarify, Pixel Experience already runs nicely for me, I only have issue with the Pixel Camera app port. What I was referring to giving a try was attempting to install Pixel Experience via Dynamic System Update for a dual boot experience.
Click to expand...
Click to collapse
Waitwait. We can dual boot?!

MattchuBlean420 said:
Waitwait. We can dual boot?!
Click to expand...
Click to collapse
Yeah, I've been dual booting Stock Android 11 and 12 with DSU for a week now. The issue is, as far as I can tell, is that only signed images (from Google or an OEM) are compatible with DSU. Now if that maybe means being able to run a custom rom as your main OS and using Stock for DSU (As the stock image would be signed) remains to be seen as I haven't given it a try.

Also Motorola G 5G KIEV has hidden charging / notification LED, but it is not avaiable with standard software.

halentech said:
Also Motorola G 5G KIEV has hidden charging / notification LED, but it is not avaiable with standard software.
Click to expand...
Click to collapse
I almost forgot about that. I noticed it too when I had the phone in EDL mode.

GCPDetective said:
I flashed it on my device but I had to also flash vbmeta as well. No issues for now. I'll link the thread where I got the vbmeta image from in a few minutes.
Click to expand...
Click to collapse
Hey @GCPDetective would you happen to be able to write up a guide on getting Pixel Experience running? I've followed all the steps to unlock the bootloader, flashed the vbmeta.img and now im just hitting a wall when flashing the Pixel Experience image, it stops and says there is no directory or file when writing system_a. and then immediately fails

Figured it out forgot to unzip the image file *faceplam*

sapplegater01 said:
Hey @GCPDetective would you happen to be able to write up a guide on getting Pixel Experience running? I've followed all the steps to unlock the bootloader, flashed the vbmeta.img and now im just hitting a wall when flashing the Pixel Experience image, it stops and says there is no directory or file when writing system_a. and then immediately fails
Click to expand...
Click to collapse
would you be able to make a guide for it? should i go about using TWRP (unofficial) to try and flash vbmeta? or should i use fastboot commands?
edit: sorry for such a noob question, I am extremely new to all this.

My moto does not connect to service when I flash pixel experience, forget about 5G
Does anyone know why?

GCPDetective said:
Just to clarify, Pixel Experience already runs nicely for me, I only have issue with the Pixel Camera app port. What I was referring to giving a try was attempting to install Pixel Experience via Dynamic System Update for a dual boot experience.
Click to expand...
Click to collapse
So you were able to flash a system img on a super a/b device? Why not share any helpful information as to how you achieved that? I've been able to do it successfully but only once and not with this ROM. It was about a year ago and data/telephony was a known bug so without being able to use the phone and data I ended up ditching the GSI about an hour after finally getting it installed. I think TWRP was what enabled me to really get it going but I could be wrong.

sapplegater01 said:
Hey @GCPDetective would you happen to be able to write up a guide on getting Pixel Experience running? I've followed all the steps to unlock the bootloader, flashed the vbmeta.img and now im just hitting a wall when flashing the Pixel Experience image, it stops and says there is no directory or file when writing system_a. and then immediately fails
Click to expand...
Click to collapse
My guess is he didn't actually achieve the flash lol

cuzimthatnerd86 said:
So you were able to flash a system img on a super a/b device? Why not share any helpful information as to how you achieved that? I've been able to do it successfully but only once and not with this ROM. It was about a year ago and data/telephony was a known bug so without being able to use the phone and data I ended up ditching the GSI about an hour after finally getting it installed. I think TWRP was what enabled me to really get it going but I could be wrong.
Click to expand...
Click to collapse
Plenty of tutorials in the guides section for this device. I used those tutorials plus the vbmeta image I linked to in my previous posts.
cuzimthatnerd86 said:
My guess is he didn't actually achieve the flash lol
Click to expand...
Click to collapse
I did and it looks like others in this thread were successful as well. Only thing I haven’t got working is BT but others seem to have gotten it working successfully. You’re on your own from here though because according to you I’m a liar, so you should ignore everything I just said. Good luck

Related

[ROM][10.0][RMX1971] Pixel Experience [OFFICIAL][AOSP]

{
"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 Realme 5 Pro [RMX1971]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
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 10.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
Nothing
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Pixel Experience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
Android OS version: 10.0.0_r27
Security patch level: February 2020
Device Source code: https://github.com/bablusss/device_realme_RMX1971
Source code: https://github.com/PixelExperience
​
Difference between this and the other Pixel Experience?? Is this going official near time soon?
Is this working on Realme Q?
saurav_xdadev said:
Difference between this and the other Pixel Experience?? Is this going official near time soon?
Click to expand...
Click to collapse
Bruh... Just let it go. Official means nothing to us end users. For devs official means they would've to dedicate themselves to that one ROM, become part of the official PE site and dev group and keep it updating even if they don't really want to. I think it means responsibility. So don't keep asking 'official when!?' for a dev is dedicated enough towards one ROM will take on official too. If not they won't.
saurav_xdadev said:
Difference between this and the other Pixel Experience?? Is this going official near time soon?
Click to expand...
Click to collapse
Official doesn't mean it's stable, just a tags bruh, they can update without Official
Hey there. Tested out the other PE version here on XDA, but that bootlooped after 2 weeks of usage (apparently a problem with most custom OSes). Does this fix the bootloop issue? Havoc OS recently pushed a patch that fixes said problem
greenys' said:
Bruh... Just let it go. Official means nothing to us end users. For devs official means they would've to dedicate themselves to that one ROM, become part of the official PE site and dev group and keep it updating even if they don't really want to. I think it means responsibility. So don't keep asking 'official when!?' for a dev is dedicated enough towards one ROM will take on official too. If not they won't.
Click to expand...
Click to collapse
viethoang18 said:
Official doesn't mean it's stable, just a tags bruh, they can update without Official
Click to expand...
Click to collapse
I didn't mean to be rude. Just as to know why there are two threads for the same rom.
I'll be more than happy to have any roms having no bugs at all and be unofficial rather than having bugs and be official. Peace :good:
Nice! tho fingerprint hardware becomes unavailable at times, and TWRP can read the internal memory as it becomes encrypted
saurav_xdadev said:
I didn't mean to be rude. Just as to know why there are two threads for the same rom.
I'll be more than happy to have any roms having no bugs at all and be unofficial rather than having bugs and be official. Peace :good:
Click to expand...
Click to collapse
Sure thing. Me too.
It's good rom. All functions work well for me! But wifi doesn't connect automatically.
bahuy2003 said:
It's good rom. All functions work well for me! But wifi doesn't connect automatically.
Click to expand...
Click to collapse
It will work only if linked to a know location. Kind of trade off.
How do you flash this rom from stock non rooted ColorOS.
JominatorX said:
How do you flash this rom from stock non rooted ColorOS.
Click to expand...
Click to collapse
Yes you can!
1. Unlock bootloader.
2. Flash recovery over fastboot mode.
3. Download rom and copy it into sdcard (not internal memory).
4. Put your device into recovery mode.
5. Flash rom from sdcard
6. Format data (factory reset).
7. Come back fastboot mode and flash vbmeta.img
8. Reboot system.
So that's, you didn't need to root your mobile.
---------- Post added at 04:11 PM ---------- Previous post was at 04:09 PM ----------
clavicle said:
It will work only if linked to a know location. Kind of trade off.
Click to expand...
Click to collapse
Yes, that's right. I think this rom is the best from custom roms.
How does user update OTA with this Custom ROM if the new version is available? Must flash again and cannot do it through the phone directly?
Thanks for your detailed guide! One last request tho where can I find a compatible vbmeta.img that I can flash to avoid recovery destroyed error.
one question: how can I upgrade to this version from the previous PE such like the 17/01/2020 version by @BabluS?
@Orgasmtrron
There is this double tap to wake bug in this rom. No matter how your toggle is selected to in the settings, the Tap to Wake feature is always on. This is leading to battery drain too.
Another, can the wifi fix be incorporated? The wifi will not reconnect after switching it off, even though I have activated the option of wifi scanning and set the location to on. It still wouldn't reconnect automatically. You always have to manually turn the wifi on.
Thanks.
JominatorX said:
Thanks for your detailed guide! One last request tho where can I find a compatible vbmeta.img that I can flash to avoid recovery destroyed error.
Click to expand...
Click to collapse
Vbmeta.img
https://drive.google.com/file/d/1-vk6rZJg-u53jMQZGC_gnb6Rhi5KXNC0/view?usp=drivesdk
my questions to those testers who have tested the current official version(PixelExperience_RMX1971-10.0-20200227-0250-OFFICIAL.zip)
1) anyone tried gcam with all 4 back cameras (including macro and wide cameras) work in this rom ?
2) which version of gcam is stable for this rom?
3) is auto call recording feature available?
So far the rom is so stable, but the ram management is bad, I barely can't open 4 apps together and they load many of the times.
Sent from my Realme 5 Pro using Tapatalk

[ROM][OFFICIAL][11][OnePlus Nord N10/billie] Pixel Experience [AOSP]

{
"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 OnePlus Nord N10 [billie]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, 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 11
Whats working?
RIL
Mobile Data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Lights
Sound/vibration
WIFI
NFC
Default 90hz refresh rate
Known issues
Adaptive Brightness
DT2W
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Join Telegram SUPPORT GROUP
Flash instruction
Pre-requisites:
* You are familiar with helping yourself out of awkward situations. You won't defame or complain at the developer of this ROM for your misfortunes.
* You are familiar with using fastboot
* Bootloader unlocked
* You have created a backup of your ROM & data
* !!!CLEAN FLASH RECOMMENDED!!!​
Spoiler: Instruction
Download the ROM and recovery image​
Boot into bootloader adb reboot bootloader​
Flash the recovery image fastboot flash recovery recovery.img​
Do a factory reset in recpvery​
Reboot into recovery fastboot reboot recovery​
Go to Apply update and choose Apply from ADB​
Sideload the rom adb sideload rom.zip​
​
​
A special thanks to @churchner420 who donated me the device!
Thx to @KakatkarAkshay who helped me!
Android OS version: 11.0.0_r32
Security patch level: March 2020
Build author: Billaids / Telegram
Device Source code: https://github.com/Billaids/device_oneplus_billie
Kernel Source: https://github.com/Billaids/kernel_oneplus_sm6350
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Thanks for sharing! Is SELinux enforcing ?
Billaids said:
Flash the recovery image fastboot flash recovery recovery.img​
Click to expand...
Click to collapse
Does this automatically default to the current boot partition? I think there is no recovery partition. Wouldn't it be enough to fastboot boot the recovery, so the current kernel is not overwritten? (second partition set can remain unchanged as backup)
downloading, thanks
Very nice Rom, installed it and it works. One thing I couldn't find is an option to switch to 90Hz? Is it possible to get it to 90Hz?
EDIT: Found a way " adb shell settings put system min_refresh_rate 90.0 " does the job.
Nice Rom, keep up the good work. Thank you a lot!
Finally we are gifted with the boon of roms for this phone. Praise be!
But for real though thank you so much.
If've tesed the Rom a little bit, two things, first the Statusbar is a little bit to high and scrolling is a little bit stuttery (maybe something to do with scrolling cache?).
Other than that very smooth and stable rom.
MH190102 said:
If've tesed the Rom a little bit, two things, first the Statusbar is a little bit to high and scrolling is a little bit stuttery (maybe something to do with scrolling cache?).
Other than that very smooth and stable rom.
Click to expand...
Click to collapse
Both and a lot more will be fixed in the next update. Meanwhile the refresh rate is set to 60hz hence your phone feels stuttery. That can be fixed with the following adb command: adb shell settings put system min_refresh_rate 90.0
churchner420 said:
Both and a lot more will be fixed in the next update. Meanwhile the refresh rate is set to 60hz hence your phone feels stuttery. That can be fixed with the following adb command: adb shell settings put system min_refresh_rate 90.0
Click to expand...
Click to collapse
Yeah, its the first build and for that its running pretty good, as you can see above I've allready fixed the refresh rate at 90Hz with this command, still some stutters but its ok.
Really looking forward for the next update, love the Rom.
MH190102 said:
Yeah, its the first build and for that its running pretty good, as you can see above I've allready fixed the refresh rate at 90Hz with this command, still some stutters but its ok.
Really looking forward for the next update, love the Rom.
Click to expand...
Click to collapse
Yepe too oh yes ok I didn't see it was you. The stuttering probably is because of the kernel not being polished 100%. Will prbably be a lot better in the next update
Tried flashing this ROM today, wifi still doesn't work after rebooting multiple times. re flashing yields the same result. Anyone else having this problem?
Generic123. said:
Tried flashing this ROM today, wifi still doesn't work after rebooting multiple times. re flashing yields the same result. Anyone else having this problem?
Click to expand...
Click to collapse
I completed the setup without wifi and once I got to the Homescreen, I rebooted the device and wifi was working.
Is this ROM for the 5G? If so is it for the unlocked version?
creativetrendz said:
Is this ROM for the 5G? If so is it for the unlocked version?
Click to expand...
Click to collapse
5G should work
Generic123. said:
Tried flashing this ROM today, wifi still doesn't work after rebooting multiple times. re flashing yields the same result. Anyone else having this problem?
Click to expand...
Click to collapse
try to flash boot.img from stock rom
after booting the stock boot.img the roms runs nicely I am happy to st modifying this device
Can you say if the next update for this awsome Rom is comming soon?
Billaids said:
try to flash boot.img from stock rom
Click to expand...
Click to collapse
Late reply, but flashing the stock boot.img doesn't appear to fix things on my end. Will go back to oxygenOS for now. Hope that the next update makes the ROM more stable.
Hello Sir, I bought the OnePlus NORD N10 5G phone last week and wanted to use it for direct streaming with my new Hearing AIds. In the System/Accessibility menu, i ticked Hearing Aids Compatibility and paired my hearing Aids devices and they showed up as connected. Alas, no sound in my aids! They still come out from the loudspeaker even if I press the volume button and change the output to Hearing Aids. I know that ASHA (Audio Streaming for Hearing Aids) works well on PIXEL 3 and 4. Is it implemented in your ROM? I don't want to void my guarantee if there is no hope that it ill work. Thanks for your answer.
vakwa42 said:
Hello Sir, I bought the OnePlus NORD N10 5G phone last week and wanted to use it for direct streaming with my new Hearing AIds. In the System/Accessibility menu, i ticked Hearing Aids Compatibility and paired my hearing Aids devices and they showed up as connected. Alas, no sound in my aids! They still come out from the loudspeaker even if I press the volume button and change the output to Hearing Aids. I know that ASHA (Audio Streaming for Hearing Aids) works well on PIXEL 3 and 4. Is it implemented in your ROM? I don't want to void my guarantee if there is no hope that it ill work. Thanks for your answer.
Click to expand...
Click to collapse
As far as I know unlocking your Bootloader on a OnePlus-Phone doesn't void your guarantee.
Help pls, not sure what I am doing wrong. I have a Oneplus Nord N10 5G and have once again had to rely on the MSM Dowload Tool at billie8_14_O.01_201121 to recover the situation!
Like on all my phones of past nearly 10 yrs, rooting is the best option for me. I wonder when TWRP will be available?
I managed to install the custom recovery as above but adb sideloading the PixelExperience_billie-11.0-20210306-2121-BETA-UNOFFICIAL.zip doesn't work for me. It crashes out about halfway thru saying it was expecting to receive file for the N10, which it is.
Just to clarify this Pixel zip file is for the Build Number Oxygen OS 10.5.7 BE86AA and after?? Thanks all for any advice/pointers

[OFFICIAL] LineageOS 18.1 for the Moto Z2 Force

{
"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 Z2 Force
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 Z2 Force.
Join our Moto Z2 Force Discord!
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.
nash
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
The EQ Apps for Audio Mods (eg. JBL2 App) won't work, and will crash.
Ultrasonic Proximity Sensor doesn't work -- No support present in the OSS Audio HAL. If it was written in, it wouldn't be used by anything in LineageOS, as the normal proximity sensor works fine.
Audio Mods have no alarm or notification audio through them.
Camera Mods don't (and won't ever) work.
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.
Official Lineage OS builds for nash ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Code:
Technical details on our Treble implementation:
Treble is enabled with VNDK30, and VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_msm8998
How did you find this? I got an alert that lineage 18 came out but went to the website less than five minutes ago and it wasn't available for nash yet ?
*Edit* I just checked again it's not available for download even though it's listed ..weird
PrivyetCyka said:
How did you find this? I got an alert that lineage 18 came out but went to the website less than five minutes ago and it wasn't available for nash yet ?
*Edit* I just checked again it's not available for download even though it's listed ..weird
Click to expand...
Click to collapse
Am the developer - and it is building on official servers tonight, check back in 24 hours.
npjohnson said:
Am the developer - and it is building on official servers tonight, check back in 24 hours.
Click to expand...
Click to collapse
Oh awesome. Thank you for the hard work ! Glad to see roms still being made for this phone
Just flashed on my t-mobile device from recovery. My phone is bricked. The battery life on my z2 force was getting old anyway so I am probably going to have to get a new phone if I can't fix it.
If you have a t-mobile device DO NOT FLASH FROM RECOVERY!!!
I fixed it! Please make sure to flash lineage from your computer when you are updating to a new version of lineage... NP Johnson makes this clear in his instructions. Unfortunately it has been awhile since I have flashed a rom onto a phone and I forgot that step...
here is how I did it
fastboot flash boot_b recovery-nash.img
factory reset your phone
flash the lineage zip from your computer using adb sideload lineage 18.1 nightly
Very good upgrade, thanks for the hard work and making this real
Thank you for not letting our device die
Thanks a ton for keeping our device up to date! I see that the efficiency mode is working for the battery mod, amazing!!
The clock app is not working and I think usb tethering is not working.
Vibration is not working
Firstly, THANKS FOR THIS!
I get the following error when opening the Camera app: dlopen failed: library "libmcf-jni.so" not found.
HDR mode is missing and you still can't save to SD - otherwise seems to work OK
Install steps taken:
1. adb sideload lineage-18.1-20210401-nightly-nash-signed.zip
2. Reboot into the newly-updated 18.1 recovery
3. adb sideload MindTheGapps-11.0.0-arm64-20210328_143848.zip
Since I was updating from 17.1 with Google Apps, I did not perform a factory reset per the upgrade instructions here: https://wiki.lineageos.org/devices/nash/upgrade
Was this wrong? Should I have done a clean install?
Big_Brother_Is_Watching said:
Just flashed on my t-mobile device from recovery. My phone is bricked. The battery life on my z2 force was getting old anyway so I am probably going to have to get a new phone if I can't fix it.
If you have a t-mobile device DO NOT FLASH FROM RECOVERY!!!
Click to expand...
Click to collapse
Flashing from recovery is fine - so long as you can see the zip, it's no problem. Not sure where your problem hit.
But thank you for ultimately flowing the guide and using your PC, it just raised and more seamless.
vivebatu said:
Thanks a ton for keeping our device up to date! I see that the efficiency mode is working for the battery mod, amazing!!
Click to expand...
Click to collapse
Yup! And will from here on out
Big_Brother_Is_Watching said:
The clock app is not working and I think usb tethering is not working.
Click to expand...
Click to collapse
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
Manuelmartad said:
Vibration is not working
Click to expand...
Click to collapse
It works, your motor may have died.
wyldwilly said:
Firstly, THANKS FOR THIS!
I get the following error when opening the Camera app: dlopen failed: library "libmcf-jni.so" not found.
HDR mode is missing and you still can't save to SD - otherwise seems to work OK
Install steps taken:
1. adb sideload lineage-18.1-20210401-nightly-nash-signed.zip
2. Reboot into the newly-updated 18.1 recovery
3. adb sideload MindTheGapps-11.0.0-arm64-20210328_143848.zip
Since I was updating from 17.1 with Google Apps, I did not perform a factory reset per the upgrade instructions here: https://wiki.lineageos.org/devices/nash/upgrade
Was this wrong? Should I have done a clean install?
Click to expand...
Click to collapse
dlopen, HDR, and save to SD: all expected and WIP. Working on them
npjohnson said:
Yup! And will from here on out
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
It works, your motor may have died.
dlopen, HDR, and save to SD: all expected and WIP. Working on them
Click to expand...
Click to collapse
Noice/Thanks!
Oh, I'd like to report that my Mophie external battery seems to be working better than it did in 17.1.
wyldwilly said:
Noice/Thanks!
Oh, I'd like to report that my Mophie external battery seems to be working better than it did in 17.1.
Click to expand...
Click to collapse
That's efficiency mode and proper battery mod support for ya! Haha.
npjohnson said:
Yup! And will from here on out
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
It works, your motor may have died.
dlopen, HDR, and save to SD: all expected and WIP. Working on them
Click to expand...
Click to collapse
no, its not working i tried it on;stock and it works well
Wifi is not working, everything else looks fine. No using cellular (no chip in device). Any ideas?
idelgador said:
Wifi is not working, everything else looks fine. No using cellular (no chip in device). Any ideas?
Click to expand...
Click to collapse
sounds like a persist issue - did you ever flash pie firmware?
npjohnson said:
sounds like a persist issue - did you ever flash pie firmware?
Click to expand...
Click to collapse
Is that related to a previous flash of pie? :O

[OFFICIAL] LineageOS 18.1 for the Google Pixel 3a XL

{
"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"
}
Google Pixel 3a XL
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 Google Pixel 3a XL.
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.
bonito
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.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9
Going to try it now.
Thank you!
npjohnson said:
​
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Click to expand...
Click to collapse
syntax error Are we talking about the Kernel being bundled?
ssurell said:
syntax error Are we talking about the Kernel being bundled?
Click to expand...
Click to collapse
What? No, firmware, like modem, bootloader, etc.
Question:
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
So are you saying if we root there is no support? As most of us coming from stock would at least need root temporarily to restore all our apps.
Can anyone confirm if root even works on this build. I woudnt see any reason not but would like to know cause of the above reason.
UPDATE: Decided to just go for it and everything is working great so far. Took a little work to get google apps working instead of the included aosp ones (phone calendar and contacts) and a bt more work to get it to pass safteynet but its all working 100% now. Also tested this build with both ex kernel and mvk and they both seem to work just fine as well. Will report back if anything changes as have only been running it.a few hours but so far no issues or complaints at all.
Great job LOS team
What is the official way to obtain root access? or is there one any more?
cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
Based on the above statement i quoted sounds like root is not "officially" supported at all. That said to get root i followed the process by which you patch a boot image file with magisk manager. Making it pass safteynet net took additional steps.
If you need more details on either process just post back and i can be more detailed
adm1jtg said:
If you need more details on either process just post back and i can be more detailed
Click to expand...
Click to collapse
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
cliffordd said:
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
Click to expand...
Click to collapse
sent you a private
cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
i flashed the version of Magisk (v21.4) via the LineageOS recovery using the adb sideload and just updated to v22 via the app. I haven't had any issues with root since installing.
First off, I want to say thank you for all the hard work on these builds.
I have came across one issue that isn't working for me, but might not be something everyone else uses a lot. My "squeeze" for Assistant isn't working, but I can change it to take a screenshot of any other option, except the Assistant. Am I doing something wrong or is there another settings need to activate for it to work?
Thanks!
Really want to try this, but can't "fastboot boot twrp.img" or "fastboot flash boot twrp.img" in Android 11 to backup my partitions. What's the point of Android OS if I can't backup my system? I can boot into Lineage OS Recovery, enable adb, figure out the partition names, dd the partitions from shell or pull with adb? But good grief, kinda ridiculous if you ask me.
Haven't been able to use twrp since Android 9 far as i know
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Nevermind, user error.
ssurell said:
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Click to expand...
Click to collapse
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
npjohnson said:
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
Click to expand...
Click to collapse
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
ssurell said:
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
Click to expand...
Click to collapse
weird - we don't have MTG builds for 17.1 though, sadly.
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
ssurell said:
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
Click to expand...
Click to collapse
Why do you want encryption disabled?
It's hardware backed, and FBE, so very little gain from running unencrypted...
"Trust" has nothing to do with encryption, it can be on, off, trust just reports it to the user.
Why do you want TWRP? Lineage Recovery does the job just fine. What do you mean "/data (formerly userspace)"? That statement doesn't make much sense.
Regardless of all the above, the disabel force encrypt zip, followed by `fastboot -w` to format userdata ought to do it - but be warned, if you set a PIN, Android (AOSP, not a lineage thing specifically) will re-encrypt you... hence there being no point.

[ROM][OFFICIAL][mata][12L] StatiXOS v5.1

{
"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"
}
StatiXOS for Essential PH-1 (mata)
What is StatiXOS?
StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal while providing quality of life improvements and up to date security patches.
Spoiler: Known Issues
Some minor Launcher bugs (thanks AOSP)
SElinux Permissive
Spoiler: Download StatiXOS Here!
Primary
SourceForge Mirror
Spoiler: How To Flash
1. Download the image
2. Reboot your Essential Phone to bootloader and plug it in to your computer
3. Now open up your Terminal (macOS and Linux) or Command Prompt (Windows) and download the firmware from the links below.
4. Once downloaded, type in fastboot -w to make sure your /data is formatted
5. Now type in fastboot update <location of the firmware>, things will be automated from this point on.
6. Profit!
Spoiler: Stay in touch with our Telegram channels!
Official Chatroom
Official Releases & Announcements Channel
​
Prerequisite firmware: Latest stock Android 10
Android version: 12.1.0
Linux Kernel Version: 4.4.205
Source code: GitHub
Code Review: Gerrit
Trying it now thank you for the work and dedication!
I flashed this firmware and everything is fine. But when I flashed magisk, the screen seemed to move a little to the right. The screenshot is OK, but it can be seen in the photo.
Before flash Magisk
Code:
adb shell wm size
Physical size: 1312x2560
After flash Magisk
Code:
adb shell wm size
Physical size: 1376x2560
btbochs said:
I flashed this firmware and everything is fine. But when I flashed magisk, the screen seemed to move a little to the right. The screenshot is OK, but it can be seen in the photo.
Click to expand...
Click to collapse
This issue showed at one or two latest StatiXOS Android 11 builds for mata, after installing Magisk. According to Anay, one the team devs, it could be related to "the kernel thinks you’re in recovery, so it shifts the whole framebuffer 64 pixels".
The fix was to use a kernel from previous builds not affected or to wait until the issue can be fixed with StatiXOS Android 12, because Android 11 builds were EOL.
Currently in use, the problems found are that the night light mode is invalid, and the hot spot is opened, setting the password, and others' connection fails
if magisk is not supported, what is the alternative for rooting the rom? thank you.
Does Google pay work with this?
On statix A11, how to update/flash from los recovery
I noticed that, even in previous versions of statixos 4.x, there is a wifi performance gap. On the aosp version, for example, the test is passed with about 300mbps in download, while on statixos it is around 100mbps. Have you also noticed this?
digitalsimon said:
I noticed that, even in previous versions of statixos 4.x, there is a wifi performance gap. On the aosp version, for example, the test is passed with about 300mbps in download, while on statixos it is around 100mbps. Have you also noticed this?
Click to expand...
Click to collapse
Yes
Vi7eta said:
Yes
Click to expand...
Click to collapse
There are possible fixes, maybe from next releases?
Someone have idea about what cause this gap?
Deleted
I love this ROM and am very appreciative of the work you've done to keep my favorite phone off all time going. Magisk compatibility would be a nice addition. And maybe a pixel launcher version that allows the 2X2 grid pattern and super large icon folders on the desktop. Old people approved. Good work.
jeddy877 said:
I love this ROM and am very appreciative of the work you've done to keep my favorite phone off all time going. Magisk compatibility would be a nice addition. And maybe a pixel launcher version that allows the 2X2 grid pattern and super large icon folders on the desktop. Old people approved. Good work.
Click to expand...
Click to collapse
is it that good? I've been wanting to install it but I fear of bugs and battery issues (since my battery is already trash because of age)
Mario3DS said:
is it that good? I've been wanting to install it but I fear of bugs and battery issues (since my battery is already trash because of age)
Click to expand...
Click to collapse
It is fast. I haven't noticed a difference in battery life. Chrome doesn't work. I use the browser. Even the 360 mod works. The screen and battery are really easy to replace. I did it on the PH-1 here. My white one is stock and it's is a little tired. The ROM probably fully works on Verizon. I switched to Visible and it only partially works. It fully works on my Mint SIM.
jeddy877 said:
It is fast. I haven't noticed a difference in battery life. Chrome doesn't work. I use the browser. Even the 360 mod works. The screen and battery are really easy to replace. I did it on the PH-1 here. My white one is stock and it's is a little tired. The ROM probably fully works on Verizon. I switched to Visible and it only partially works. It fully works on my Mint SIM.
Click to expand...
Click to collapse
Does the rom has any customization options in setting? would you provide some SC for it,tnx
ali.sbi said:
Does the rom has any customization options in setting? would you provide some SC for it,tnx
Click to expand...
Click to collapse
It doesn't really have any customization options other than the normal A12 stock ones. I also noticed yesterday that I can no longer flash boot images or even restore it to stock firmware. The AB partitioning seems to be gone. Love the ROM but there should be a way to leave it. I may have just not figured it out yet.
jeddy877 said:
It doesn't really have any customization options other than the normal A12 stock ones. I also noticed yesterday that I can no longer flash boot images or even restore it to stock firmware. The AB partitioning seems to be gone. Love the ROM but there should be a way to leave it. I may have just not figured it out yet.
Click to expand...
Click to collapse
I haven't used this rom yet but as far as I know, a rom can't remove the A/B partitioning on a device
This awesome ROM is flashed just like flashing the stock firmware using flashall.bat. When I try reflashing the stock firmware, it says NO NO. The size of some file is too large. If I try to flash just any boot image, including the one from this ROM, to _a or _b in fastboot... It says AB partitioning is not supported by this device.

Categories

Resources