Database Develop

[Firmware][Leak]Huawei P8 B380 - GRA-L09C432B380

Firmware B380 (FULL) for Huawei P8 (GRA-L09) was leaked:
http://www.huaweiblog.de/handys/huawei-p8/#firmware
Installation via dialer method works fine. Google Patches from Sept 1st, 2016.
Source: huaweiblog.de

changelog?

Some mirrors since Huawei Blog's download link is going slow:
https://www.amazon.com/clouddrive/s...f2IFsMnJuzpUixhGC6?ref_=cd_ph_share_link_copy
http://gofile.me/3oK5Y/sFoSqBBEN
Just in case you forgot here are the update instructions:
Download GRA-L09C432B380FULL.zip
Extract the archive
Move the extracted "update.app" file into a folder named "dload" in the root of your SD card.
Using the dialer, dial * # * # 2846579 # * # *
Select the "Software Upgrade" and start the update from the SD card
After the update, the P8 restarts and performs the first boot optimizations
Here's the changelog converted from German using Google Translate:
This update addresses issues related to news and the presentation of the user interface are fixed and improves system security and stability using the latest security patches from Google.
[Fixes] The problem is that some text messages sometimes can not be sent over a 4G network has been resolved. The problem is that the display does not flash when in standby mode enters a message has been resolved. The problem is that some elements be the user interface displayed incorrectly has been fixed
[Optimization] Device security was Improvement using the latest security patches from Google.
[Update Notes] 1 Before you upgrade, make sure your phone is not rooted and has sufficient space. If problems with updating occur, call the customer service hotline. 2 To improve compatibility with Android 6.0, update third-party apps in the Google Play Store to their latest versions. 3 Your home screen layout may change slightly. 4 In this update, no personal data will be deleted. However it is recommended to back up important data before updating.
Click to expand...
Click to collapse

ml_taz said:
Firmware B380 (FULL) for Huawei P8 (GRA-L09) was leaked:
http://www.huaweiblog.de/handys/huawei-p8/#firmware
Installation via dialer method works fine. Google Patches from Sept 1st, 2016.
Source: huaweiblog.de
Click to expand...
Click to collapse
wipes Internal storage?

AD2076 said:
wipes Internal storage?
Click to expand...
Click to collapse
No

Does anyone tried this yet?
Is it stable enough (cm nightlies are stable enough for me) for daily use?
Any problems rooting or reinstalling TWRP after the update?
Thanks

ml_taz said:
Installation via dialer method works fine. Google Patches from Sept 1st, 2016.
Click to expand...
Click to collapse
I have TWRP installed and this method doesn't work. Should I try the update with phone attached to PC (when attached it uses recovery2 which is still the stock one)?

AD2076 said:
I have TWRP installed and this method doesn't work. Should I try the update with phone attached to PC (when attached it uses recovery2 which is still the stock one)?
Click to expand...
Click to collapse
you need stock recovery to install updates, also, you can not have root before flashing

I unrooted completely but I don't have the stock recovery.

AD2076 said:
I unrooted completely but I don't have the stock recovery.
Click to expand...
Click to collapse
You need to extract it from your current MM rom and reflash it
Sent from my GRACE using Tapatalk

Does anyone successfully flashed this???? I don't want to brick my phone
Sent from my HUAWEI GRA-L09 using XDA Labs

ionutzpaul61 said:
Does anyone successfully flashed this???? I don't want to brick my phone
Sent from my HUAWEI GRA-L09 using XDA Labs
Click to expand...
Click to collapse
I went from stock, unrooted B370 to B380. No problems to report.

desertflyer said:
I went from stock, unrooted B370 to B380. No problems to report.
Click to expand...
Click to collapse
I'm also unrooted b370..... I will download the firmware tomorrow morning and i will try it... Thanks for your answer
Sent from my HUAWEI GRA-L09 using XDA Labs

Problem -- Music folder
Flashed B380, everything is fine. One thing that drives me crazy -- on inernal memory, there is a Music folder that appeared after update, with some songs on it, and it cannot be deleted, nor folder nor files... Tried it from file manager, windows, adb (permission denied)... Still, folder and file permissions look fine... Any ideas, please?

Why is everyboday asking if someone tried and if it works fine?! I wrote in the OP that I tried and it works fine.
B380 seems to be very smooth.

Already flash this rom and so far so good but too bad all my themes and fonts collection in HWThemes folder (internal storage) is wiped.
New features found so far :
- Display network speed
- Users mode (option to set as owner or guest)
- Huawei ID now working (not new features but before this i can't access it, at least where i live)

it says Vollversion..what does mean this?

silvano2 said:
it says Vollversion..what does mean this?
Click to expand...
Click to collapse
https://translate.google.com/#auto/en/Vollversion

GodzillaMonster said:
https://translate.google.com/#auto/en/Vollversion
Click to expand...
Click to collapse
yes got it..and btw great battery improvement

silvano2 said:
yes got it..and btw great battery improvement
Click to expand...
Click to collapse
Yeah it's true!

Root galaxy S10 (July security patch update)

hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.

You didnt do it right. I would suggest youtube the magisk rooting process

Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead

Cristian-104 said:
hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.
Click to expand...
Click to collapse
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.

TheUndertaker21 said:
Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead
Click to expand...
Click to collapse
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).

Jannomag said:
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).
Click to expand...
Click to collapse
OH that's a known issue then?
I need my custom rom and twrp lol

TheUndertaker21 said:
OH that's a known issue then?
I need my custom rom and twrp lol
Click to expand...
Click to collapse
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)

Jannomag said:
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)
Click to expand...
Click to collapse
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon

TheUndertaker21 said:
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon
Click to expand...
Click to collapse
It's easy to flash it, even without running system.

Hi everyone, I'm still ASD4 and basically haven't update since because everything is a hassle these days. Now I thought maybe it's time to update, but keep reading things like this and camera, wifi bootloops problems etc.
Are these issues a real thing? or just some individual cases where it happens?

It's real like a $2 dollar bill.

bininga59 said:
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.
Click to expand...
Click to collapse
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.

FlatOutRU said:
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.
Click to expand...
Click to collapse
I have already made. As I said, I unlock the bootloader and lock (developer option or download mode) as I want,> prenormal <does not go away.

Did a root today without issues on my S10 with ASG8

ru_dimka said:
Did a root today without issues on my S10 with ASG8
Click to expand...
Click to collapse
everything works? twrp installed? magisk etc.?

chieco said:
everything works? twrp installed? magisk etc.?
Click to expand...
Click to collapse
There is no twrp for ASG8. Others stuff works well!

ru_dimka said:
There is no twrp for ASG8. Others stuff works well!
Click to expand...
Click to collapse
I'm always afraid that I install something or make a small change and end up in a bootloop... I wish twrp and everythign work just fine like before and I could make a backup after installing a rom and doing the most basic stuff.

Since this is the first post that comes on Google for "only official released binaries" "s10".
I had this problem again and again, and it seems that it was caused by one of the reboot not being done with the correct timing with the 3 buttons.
The thing I was missing was after flashing the patched AP files (and the other files).
When you restart, keep the 3 buttons pressed until you see the blue screen and then release only power (keep vol up + bixby) to get into reset mode.
I think I didn't keep them pressed long enough.
If the device restarts, keep pressing the 3 buttons (never let it restart without pressing them).
Once the factory wipe has been done: Restart with the 3 buttons, and keep them pressed until 1 to 2 sec after the screen that asks you to press the power button to continue.

Android 11 Release - Finally!

Exciting to see android 11 come to our OP7 series!
Can someone who doesn't mind being a guinea pig test the update out? I am currently on a third party ROM (i do prefer OEM) however i had to go that route since my usb to audio splitter didn't work after 10.X.X.X update here since November. Was wondering if someone who doesn't mind could update to this latest, and test it out. https://www.xda-developers.com/oneplus-7-7-pro-7t-7t-pro-stable-oxygenos-11-android-11/
Regards,
Travis

i would love to do it but no file for the 7 pro yet

There aren't files for 7 series, only for 7T and 7T Pro.
I've read something about problems with Camera app, so they turned off distributing update. Still waiting

Global version is on Oxygen Updater now.
Nothing for EU yet.
Official Global Link : https://otafsg1.h2os.com/patch/amaz...1.P.35_OTA_0350_all_2103221240_0ebe9c8a78.zip
Android File Host Mirror : https://www.androidfilehost.com/?fid=2188818919693770547 (MD5 : 3ec7940e9e50032b540ceaf2a3364f85 )
Pack with rooted boot image and instructions for Global : https://www.androidfilehost.com/?fid=2188818919693770594 ( MD5 : b24c7463ef9a78ab0ae7ae708dc46c37 )
I've extracted all the image files but AFH is still being a pile of crap, FTP uploads won't work and web uploads keep stopping or not completing, uploaded mirror to Dropbox for now, will try to get it uploaded to AFH asap.
Pack with all extracted images for Global version : (TEMP Dropbox Link) https://www.dropbox.com/s/nwfo6433wdkkkk3/Default-OxygenOS11-Final-Images_Global.zip?dl=0

Is it true AOD is missing??
I will keep Beta 4 if this is true

vegetaleb said:
Is it true AOD is missing??
I will keep Beta 4 if this is true
Click to expand...
Click to collapse
AOD was in the labs, labs is not included in the stable release ring (probably never will be) as it's supposed to be test software.

djsubterrain said:
AOD was in the labs, labs is not included in the stable release ring (probably never will be) as it's supposed to be test software.
Click to expand...
Click to collapse
Can someone try this trick to enable AOD on stable OOS 11?
[ROOT/Magisk] Enable Always on Ambient Display on Oxygen OS 11 Beta 1
Contrary to what OnePlus have said, the code for the Always on Ambient Display is in the first beta of Oxygen OS 11. All you have to do is enable the feature, which is disabled in the "OPFeatures" framework. This is very simple, and can be done...
forum.xda-developers.com

Installed and working stable for me. No problems observed with camera, messaging etc. AOD is irrelevant to me - won't miss it. Battery seems to be stable too - no indication of excessive power usage. Will update if I see anything. BTW, I am stock non-rooted.

Can we return nanroid if 11 is buggy ?

zelenko said:
Can we return nanroid if 11 is buggy ?
Click to expand...
Click to collapse
There will possibly be a rollback link provided if OnePlus ever make an actual thread for the release, there isn't one at the moment.
OK, I'm mistaken, there is actually a thread now :
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
No rollback link though so you'd likely need to do a full flash which would probably wipe the phone.

Has anyone rooted yet? And if so, which version of majisk did you use?

Hi, I tried rooting with the patched boot.img linked above but it fails to boot twice then enters recovery. Also tried patching the img myself using the latest magisk 22.0 app but it gave the same behavior. I use the command: fastboot flash boot magisk_patched.img to flash.
Anyone know what's up ?
EDIT: after the failed boot I have a "BOOT REASON" menu in recovery giving this message:
Code:
--------------------------------
Boot Reason : RescueParty
--------------------------------
Unable to parse kernel log. For more debug information,
adb pull /mnt/vendor/op2/rbr_log
or pull op2.img
Trying the adb command in recovery tells me it's unauthorized and I had to give access from the phone (which isn't possible it seems). Doing the adb pull with the system booted gives:
Code:
adb: error: failed to stat remote object '/mnt/vendor/op2/rbr_log': Permission denied
EDIT 2: After a backup and clean wiping the userdata magisk seems to work now.

From OxygenOS 11 Open Beta 4
to OxygenOS 11
without losing your data.
1.) Download and install OxygenOS 11
2.) Download keep_data.apk
You need to install it after the update was installed but before you restart.
After the apk is installed, run the application, click "KEEP DATA".
You should now be able to restart the phone without losing your data
P.S.
All your applications
and data remain intact

vegetaleb said:
Can someone try this trick to enable AOD on stable OOS 11?
[ROOT/Magisk] Enable Always on Ambient Display on Oxygen OS 11 Beta 1
Contrary to what OnePlus have said, the code for the Always on Ambient Display is in the first beta of Oxygen OS 11. All you have to do is enable the feature, which is disabled in the "OPFeatures" framework. This is very simple, and can be done...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, that does put the option back into the display settings, but just like before it gets lost in reboot unless you add that sh file

btvolta said:
Has anyone rooted yet? And if so, which version of majisk did you use?
Click to expand...
Click to collapse
Coming from ob4, I reflashed magisk to the inactive slot in the app after the upgrade was complete but before I rebooted the phone. After the reboot, I tapped on the magisk app and it said it needed additional files. After it downloaded and installed the additional files the phone rebooted and my root works fine. I started with magisk 22.

I am on 10.3.7 rooted with magisk. Before starting, a few questions. Is it possible to upgrade to 11 without losing data and retaining root? If not, is there a magisk for 11. What is the safest way to upgrade? Also, is there twrp for 11? Any help would be greatly appreciated.

Fresh install from factory reset. Screen still wigs out on FHD. Unlocking causes everything to be gigantic and have to hard reset. So no change for me from beta 4 to stable 11.

djsubterrain said:
Global version is on Oxygen Updater now.
Nothing for EU yet.
Official Global Link : https://otafsg1.h2os.com/patch/amaz...1.P.35_OTA_0350_all_2103221240_0ebe9c8a78.zip
Android File Host Mirror : https://www.androidfilehost.com/?fid=2188818919693770547 (MD5 : 3ec7940e9e50032b540ceaf2a3364f85 )
Pack with rooted boot image and instructions for Global : https://www.androidfilehost.com/?fid=2188818919693770594 ( MD5 : b24c7463ef9a78ab0ae7ae708dc46c37 )
I've extracted all the image files but AFH is still being a pile of crap, FTP uploads won't work and web uploads keep stopping or not completing, uploaded mirror to Dropbox for now, will try to get it uploaded to AFH asap.
Pack with all extracted images for Global version : (TEMP Dropbox Link) https://www.dropbox.com/s/nwfo6433wdkkkk3/Default-OxygenOS11-Final-Images_Global.zip?dl=0
Click to expand...
Click to collapse
I read the instructions in the zip file. My question is do we install the magisk and boot image before or after we install the update?

So I'm stuck in a boot loop after taking the OTA.

There is a Eu version of Android 11, I woke up with notification )

Google play store system update stuck on January patch?

Hi, when i reverted back to android 11 from android 12 beta 1 my play store system update is stuck on January patch. How do i get to the latest security patch? i've checked for update but nothing happens.

Is this after the June update? Mine is currently on May 1st after the June update. If unlocked I would try dirty flashing a full image. If locked, sideload the latest OTA via recovery.

I'm having the same issue since the first android 12 preview,when downgrading to android 11, google play system update stuck at January,i tried many ways but no luck.

Same here with Pixel 4

gm007 said:
I'm having the same issue since the first android 12 preview,when downgrading to android 11, google play system update stuck at January,i tried many ways but no luck.
Click to expand...
Click to collapse
Did you try flashing the full image and allowing a data wipe (fresh install). I'm guessing you tried dirty flashing it already. @2WildFirE

v12xke said:
Did you try flashing the full image and allowing a data wipe (fresh install). I'm guessing you tried dirty flashing it already. @2WildFirE
Click to expand...
Click to collapse
I said everything
I had to ask also in Google pixel community https://support.google.com/pixelpho...gle-play-system-update-stuck-at-january?hl=en

Yes I tried all tips, Google Support doesn't know to help.
It's an downgrade issue when come from 12

2WildFirE said:
Yes I tried all tips, Google Support doesn't know to help.
It's an downgrade issue when come from 12
Click to expand...
Click to collapse
When you reflash your phone using a full image, it wipes and formats your partitions, returning it to out of the box condition. That is the sole purpose of unlocking the bootloader and flashing a full factory image. There is nothing residual after flashing this way, so it cannot be a downgrade issue. I also agree the Google Pixel community is totally useless and laughable.

I suspect it is a server problem, it seems as if the pixels are still marked as beta and are therefore not getting an update.

2WildFirE said:
I suspect it is a server problem, it seems as if the pixels are still marked as beta and are therefore not getting an update.
Click to expand...
Click to collapse
I suspect people don't want to lose their data by properly wiping & restoring their phone to its factory state.

U don't know how often I did a full factory image flash.
But nothing worked!

v12xke said:
When you reflash your phone using a full image, it wipes and formats your partitions, returning it to out of the box condition. That is the sole purpose of unlocking the bootloader and flashing a full factory image. There is nothing residual after flashing this way, so it cannot be a downgrade issue. I also agree the Google Pixel community is totally useless and laughable.
Click to expand...
Click to collapse
I met the same issue with 4a5g. I tried flashing 5 times but issue still come. Google play services system update will automatically display 1 jan 2021 when i log in google account ( the account i was enroll to using android 12beta via OTA, but i've cancelled android 12beta)
I think issue need to be resolve by google or we can use other google account.

After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May

2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
So that mean, we need to enroll pilot update 12beta again via OTA or flashing, right?

2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
Strange how it is behind. I thought new beta versions came out after the general release so they could roll the new security release into the beta. This would mean A12 beta would also be current. But I also haven't been running the betas for a couple years. Interesting.

2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
Please share your solution with android 11.

Sorry mate, no solution for Android 11 yet.
Only works so with Android 12 Beta
So thinking if Android 12 goes out live for all, our problem is solved.

The solution on Android 11 is to simply install the "Main components" APK from APK mirror
It's basically you're just updating manually.
Main components APKs - APKMirror
Main components APKs - APKMirror Free and safe Android APK downloads
www.apkmirror.com

2WildFirE said:
Sorry mate, no solution for Android 11 yet.
Only works so with Android 12 Beta
So thinking if Android 12 goes out live for all, our problem is solved.
Click to expand...
Click to collapse
There is a solution check my post.

Alexisnotfrommars said:
There is a solution check my post.
Click to expand...
Click to collapse
This isn't a solution. It only change the date not more or less!

Development [CLOSED] PIXEL EXPERIENCE PIXEL 5A BARBET ANDROID 13 BETA UNOFFICIAL NOV. 7, 2022

October security patch.
You MUST be on Android 12 to use this!!!!!
If your already on Android 13, you can not go back to Android 12, so don't try flashing this!!!
Your bootloader must also be unlocked to install custom firmware.
To do this, reboot to bootloader and type the following: fastboot flashing unlock
The custom kernel of this ROM hides the unlocked bootloader. The device will pass Safetynet and the Play Store will report the device as certified. Based on this, root, magisk and the modules are not needed to pass device certification.
This is based on the Android Open Source Project. It includes various proprietary hardware-specific code.
All the source code is available in the Github repo here.
Basic requirements​
Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
Thanks go to Github and Pixel Experience for their source code and device specific code. I couldn't have built this without it!!!
The ROM uses the Pixel Experience source code, device specific code. I made other minor changes and used compression to lower the file size of the ROM, creating more space in the internal storage with minor reduction in performance. Updated every week with minor changes.
GAPPS ARE ALSO INCLUDED WITH THIS ROM
DO NOT DOWNLOAD OR FLASH GAPPS ON THIS ROM!!!!!
DOWNLOAD RECOVERY FLASHER HERE
DOWNLOAD ROM HERE
#1 REBOOT TO BOOTLOADER
#2 FACTORY RESET: fastboot -w
#3 Have all the recovery flasher files in the same folder
Simply double click on flash.bat to install recovery
#4 REBOOT TO RECOVERY THEN ADB SIDELOAD
adb sideload PixelExperience_barbet-13-20221107-BETA-UNOFFICIAL.zip
#5 REBOOT TO SYSTEM
#6 REBOOT TO RECOVERY AGAIN IF YOU WISH TO ROOT AND ADB SIDELOAD
adb sideload magisk.apk
#7 REBOOT TO SYSTEM
Screen call and Google assistant works.
If you are already on this ROM, you can dirty flash updates without wiping data. Simply set to inactive slot in bootloader. Reboot to bootloader then
fastboot --set-active=other
Then repeat all steps except #2
YOU MUST WIPE WHEN COMING TO THIS ROM THE FIRST TIME!!!

Hello, thanks for for new custom rom. Can you please post screenshots with which customizations available in this ROM? For example double tap on status bar to go sleep, etc?

[email protected] said:
Hello, thanks for for new custom rom. Can you please post screenshots with which customizations available in this ROM? For example double tap on status bar to go sleep, etc?
Click to expand...
Click to collapse

Thank you.

Installed this rom with gapps and magisk, everything working fine.

[email protected] said:
Installed this rom with gapps and magisk, everything working fine.
Click to expand...
Click to collapse
how is the FP sensor, does phone have slow unlock when you are not using AOD? Google introduced that stupid bug in March, and they still didn't fix it.

predragiPredrag said:
how is the FP sensor, does phone have slow unlock when you are not using AOD? Google introduced that stupid bug in March, and they still didn't fix it.
Click to expand...
Click to collapse
Works very quick, much more quicker than latest stock

[email protected] said:
Thank you.
Click to expand...
Click to collapse
Thanks for the info. Any bugs let me know.

I'm having a issue right now getting the updates pushed through the updater. For now you can manually update without wiping by the following method until I get it fixed. Reboot to bootloader and check what your active slot is. Switch to opposite slot by the following. Example, active slot is b. fastboot --set-active=a Reboot to recovery and sideload update file. Reboot to recovery and sideload Gapps file. Reboot to system. You will then have to reboot to recovery to sideload magisk and root again. Updates are always installed in opposite slot or you will be stuck at bootanimation. This will hopefully be temporary until I get the issue resolved.

TheSayaMan said:
I'm having a issue right now getting the updates pushed through the updater. For now you can manually update without wiping by the following method until I get it fixed. Reboot to bootloader and check what your active slot is. Switch to opposite slot by the following. Example, active slot is b. fastboot --set active=a Reboot to recovery and sideload update file. Reboot to recovery and sideload Gapps file. Reboot to system. You will then have to reboot to recovery to sideload magisk and root again. Updates are always installed in opposite slot or you will be stuck at bootanimation. This will hopefully be temporary until I get the issue resolved.
Click to expand...
Click to collapse
Hello, if there some critical updates, or fixes? I think everything working fine on current ROM.

[email protected] said:
Hello, if there some critical updates, or fixes? I think everything working fine on current ROM.
Click to expand...
Click to collapse
Ok thank you. Someone sent me a personal PM saying that phone calls were dropping for no reason and all text messages were not being received to their phone. I can't seem to see any issue from the logcat they sent me. Any truth to this from you or anyone else? I am using this myself and don't have such issues. Maybe it's carrier related. I have Verizon. I will check with him and see what carrier he is using. I will give him the benefit of doubt.

TheSayaMan said:
Ok thank you. Someone sent me a personal PM saying that phone calls were dropping for no reason and all text messages were not being received to their phone. I can't seem to see any issue from the logcat they sent me. Any truth to this from you or anyone else? I am using this myself and don't have such issues. Maybe it's carrier related. I have Verizon. I will check with him and see what carrier he is using. I will give him the benefit of doubt.
Click to expand...
Click to collapse
Hello, I haven't such issues. I use 2 sims, 1 esim and 1 sim, everything working fine with SMS and calls.

TheSayaMan said:
I'm having a issue right now getting the updates pushed through the updater. For now you can manually update without wiping by the following method until I get it fixed. Reboot to bootloader and check what your active slot is. Switch to opposite slot by the following. Example, active slot is b. fastboot --set active=a Reboot to recovery and sideload update file. Reboot to recovery and sideload Gapps file. Reboot to system. You will then have to reboot to recovery to sideload magisk and root again. Updates are always installed in opposite slot or you will be stuck at bootanimation. This will hopefully be temporary until I get the issue resolved.
Click to expand...
Click to collapse
Hello, do you plan to release Android 12.1, as I understand this linage is Android 12

[email protected] said:
Hello, I haven't such issues. I use 2 sims, 1 esim and 1 sim, everything working fine with SMS and calls.
Click to expand...
Click to collapse
Great, thanks!!!

[email protected] said:
Hello, do you plan to release Android 12.1, as I understand this linage is Android 12
Click to expand...
Click to collapse
This is 12.1. If you look in System, it will show Lineage 19.1

TheSayaMan said:
This is 12.1. If you look in System, it will show Lineage 19.1
Click to expand...
Click to collapse
No, for me it says, Android version 12
Lineage version 19-20220504-UNOFFICIAL-barbet

[email protected] said:
No, for me it says, Android version 12
Lineage version 19-20220504-UNOFFICIAL-barbet
Click to expand...
Click to collapse
The file name is irrelevant. Look in System, updater.

I didn't install latest your update, maybe because of it, it using Android 12?

TheSayaMan said:
The file name is irrelevant. Look in System, updater.
Click to expand...
Click to collapse
So you see, there Android is 12

[email protected] said:
So you see, there Android is 12
Click to expand...
Click to collapse
Lineage 19.1 is same as Android 12.1