Develop Bugs

[GUIDE][HOW TO] Root Xperia ZL 5.0.2

PROBLEM: ZL LockedDualRecovery is causing bootloop (DO NOT USE IT IN PRFCreator)
Downloads
PRFCreator
FTF LOLLIPOP XPERIA ZL 10.6.A.0.454
SuperSU.Zip
ZL LockedDualRecovery (Flashable).zip
Requirements[LB/UB]
Have ROM 10.5.1.A.0.292 INSTALLED with ROOT and ZL LockedDualRecovery (Installer).zip
Instructions
1 - Open PRFCreator and Select the items that were downloaded above: .FTF (Lollipop), SuperSU.Zip, ( NO )ZL LockedDualRecovery. Ticks all the boxes like the picture! E Click Create!
{
"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"
}
2 - After Create flashable-signed.zip move to the memory of the Xperia ZL! (Watch has to be "signed" the file name if flashable.zip may have been an error sign for lack of java probably).
3 - Turn it off Turn and enter the Recovery
4 - In philz Recovery or TWRP Recovery Do it!
* Format Data
* Wipe Cache
* Wipe Dalvik
* Factory reset
5 - Last step Install ROM.zip you moved to the Memory.
Note: Pay attention to PRFCreator can not occur errors make sure to have java installed.
PORTUGUESE
Downloads
PRFCreator
FTF LOLLIPOP XPERIA ZL 10.6.A.0.454
SuperSU.Zip
ZL LockedDualRecovery (Flashable).zip
Requisitos [LB/UB]
Tenha a ROM 10.5.1.A.0.292 INSTALADA com ROOT e ZL LockedDualRecovery (Installer).zip
Instruções
1 - Abra o PRFCreator e Selecione os itens que foram baixados acima: .FTF (Lollipop), SuperSU.Zip, ZL LockedDualRecovery. Marque todas as caixas igual a imagem! E Clique em Create!
2 - Após Criar mova flashable-signed.zip para a memoria do Xperia ZL! (preste atenção tem que ficar "signed" o nome do arquivo se ficar flashable.zip pode ter ocorrido um erro ao assinar por falta do java provavelmente).
3 - Desligue o aparelho, Ligue e entre no Recovery
4 - No Philz Recovery ou TWRP Recovery Faça isso!
*Format Data
*Wipe Cache
*Wipe Dalvik
*Factory reset
5 - Ultimo passo Instale a ROM.zip que você moveu para a Memoria.
OBS: Preste atenção no PRFCreator não pode ocorrer erros assegure-se de ter o java instalado.
Click to expand...
Click to collapse

Is a rule in Xda the English language, i speak spanish, portuguese is out of limits to me...

Very Good.
Sent from my D5833 using XDA Free mobile app

How you install the recovery? You don't need the root access for that?

Sorry, I have done the correction.
murphy46 said:
Is a rule in Xda the English language, i speak spanish, portuguese is out of limits to me...
Click to expand...
Click to collapse
Sorry, I have done the correction.

You need the rom .292 or .283 with root and installed dualrecovery...
nemerio said:
How you install the recovery? You don't need the root access for that?
Click to expand...
Click to collapse
You need the rom .292 or .283 with root and installed dual recovery or recovery...

Tested this method got me into bootloop.
Anyone here can report if it is working?

Abadeer said:
Tested this method got me into bootloop.
Anyone here can report if it is working?
Click to expand...
Click to collapse
The bootloop is because of the XZ Dual recovery isn't it?

Can we flash using Cyanogen Recovery? Getting "Signature Verification Failed..."
*EDIT* Nevermind, I'm a dummy, the ZIP has to say -signed on it. Flashing now!

Yes Functional.
Abadeer said:
Tested this method got me into bootloop.
Anyone here can report if it is working?
Click to expand...
Click to collapse
Please send me print the "LOG" in PRFCreator
Yes Functional. It is possible that you do not have java installed then the ROM.ZIP was not signed

Murilo Barbosa said:
Yes Functional. It is possible that you do not have java installed then the ROM.ZIP was not signed
Click to expand...
Click to collapse
No, I have, but yet got me in bootloop but I rooted it my own way.

Abadeer said:
No, I have, but yet got me in bootloop but I rooted it my own way.
Click to expand...
Click to collapse
Give me Logs in PRFCreator

hi! can we make this without recovery? because i think that will cause bootloop, have you try this? im on locked BL

do not use the DualRecovery in PRFCreator to avoid bootloop
Jaycel0820 said:
hi! can we make this without recovery? because i think that will cause bootloop, have you try this? im on locked BL
Click to expand...
Click to collapse
Do not use the DualRecovery in PRFCreator to avoid bootloop! Thanks:good:

Murilo Barbosa said:
Do not use the DualRecovery in PRFCreator to avoid bootloop! Thanks:good:
Click to expand...
Click to collapse
Is there any working recovery?

So using OTA kills root this time again?

DoubleYouPee said:
So using OTA kills root this time again?
Click to expand...
Click to collapse
Yes .I tried coming from 4.4.2 (root)-->4.4.4 (root survived)-->5.0.2 (root lose)

Hey guys, is the problem with dual recovery a conflict with the PRFcreator or does it stem from the dual recovery files being outdated??

Xposed Framework and Xperia Xposed (LP) - WORKING!!
Steps:
1. Flash Pre-rooted fw without dual-recovery, but SuperSU (booted till home screen)
2. Flash (fastboot) @Gustavo RD78's Advanced KK Stock Kernel (unlocked BL only) - (He is working on new advanced stock kernel for lollipop)
3. Enter TWRP Recovery and flash BusyBox-v1.23.1-Stericson.zip (Stericson) to get working busybox
4. Power Off device (DO NOT REBOOT)
5. Flash original 10.6.A.0.454 kernel with FlashTool (excluding everything but kernel)
6. Boot device till home screen
7. Repeat step 2
8. Enter TWRP Recovery and flash xposed-sdk21-arm-20150430.zip (alpha 4)
9. Power Off device (DO NOT REBOOT)
10. Repeat step 5
11. Repeat step 6
12. Install XposedInstaller_3.0-alpha2.apk
13. Done!!
.

pointblank_limited said:
Hey guys, is the problem with dual recovery a conflict with the PRFcreator or does it stem from the dual recovery files being outdated??
Click to expand...
Click to collapse
I can only guess it's the recovery... If you have a properly rooted stock LP ROM, installing XZDR the usual way with a PC installer also consistently results in a bootloop, even though the install finishes successfully with no problems. Speaking of proper root, the method from this thread works great, unlike Kingroot, which didn't work for me at all (seems like you are rooted, but you are not; can't mount /system as r/w).
I have been looking for ANY working recovery for ZL on 5.0.2 with locked BL. So far, found nothing...

RevengeOS 4.0-R [11] for Realme X [OFFICIAL] [RMX1901]

{
"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"
}
DISCLAIMER:-
Flash at your own risk, i am not responsible for bricked devices. Read all the instructions carefully.
​
RevengeOS is a beautiful custom ROM based on AOSP and designed to be stable, fast and easy to use.
All the source code for RevengeOS is available on RevengeOS Github repo.
What's Working :
EVERYTHING
KNOWN BUGS :
You tell me with proper logs!
Flashing Instructions :-
MUST BE ON RUI OR FLASH THE RUI FW
INDIAN-VARIANT
CHINESE-VARIANT
Copy Rom.zip,GApps,and the patched magisk
Reboot to Recovery
Wipe Dalvik,Cache,System,Data and vendor
Flash Rom and reboot to system then reboot to twrp flash magisk.
Flash the Audio patch (must) AUDIO-PATCH
Reboot To System.
Wait for few minutes and ENJOY the ROM.
Downloads :
ROM : {Mod edit}
GApps : Link
Patched magisk : Link
For Cts pass below is the attachment
Source :
ROM : RevengeOS
KERNEL : GitHub
Credits :
RevengeOS
Special Thanks to har**** jain , kaderbava ,sagar and viralbanda !
Rom OS Version : 11 R
Rom Kernel : Linux 4.x
Rom Firmware Required : RUI Firmware
XDA:DevDB Information
RevengeOS 4.0-R [11] for Realme X [UNOFFICIAL] [RMX1901], ROM for the Realme X
Contributors
hypercleric
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: RUI
Version Information
Status: Alpha
Created 2020-09-19
Last Updated 2020-09-19

Reserved
NOW OFFICIAL
* Added Smart wake (@skpawar1305)
* Proximity completely fixed ! (@dev_harsh1998)
* Fixed offline charging
* Added Vooc charging
*Added 3 finger ss
* Added blur (check developers settings)
* Added Ambient gestures
(check Display )
* Improved Ram management & stability.
*Accent working
* More improvements.

Reserved

Thanks for the ROM. Can you please post screenshots. Would be really helpful.

So, has anyone tried this ROM? Any feedback?

Great. Thank you very much

[email protected] said:
Great. Thank you very much
Click to expand...
Click to collapse
How's the experience?

Maya-Senpai said:
So, has anyone tried this ROM? Any feedback?
Click to expand...
Click to collapse
I Had problems with gapps, It tells me that google protect doesn't protect my phone so no gapps worked but I did't install magisk, idk maybe was for that

Echaeos said:
I Had problems with gapps, It tells me that google protect doesn't protect my phone so no gapps worked but I did't install magisk, idk maybe was for that
Click to expand...
Click to collapse
thank you for the reply, I shall wait for the more stable version comes out

I'm not on realme UI now.
So,if I want to try this ROM ,I should go into twrp and flash the "ColorOS7_Firmware_RMX1901.zip" first ?
then do I need reboot or just Wipe Dalvik,Cache,System,Data and vendor and flash this rom?

xdaprae said:
I'm not on realme UI now.
So,if I want to try this ROM ,I should go into twrp and flash the "ColorOS7_Firmware_RMX1901.zip" first ?
then do I need reboot or just Wipe Dalvik,Cache,System,Data and vendor and flash this rom?
Click to expand...
Click to collapse
I think you must install first RUI (chinese o indian version) than wipe and install the rom with gapps and other if you need it

{Mod edit: Quoted OP removed}
Some of the apps like Messenger and Chrome freezing sometimes.The rest is pretty good.
I can see battery improvement,gaming improvement and it kinda feels nice to use.
Although haven't figured out how to take screenshots yet cause three finger drag or pressing the buttons doesn't seem to work.
Idk why but this is the only custom rom I can use.The rest doesn't boot on my Chinese variant.
So having a new experience was nice.Thank you and everybody else who helped to create it.
---------- Post added at 01:33 AM ---------- Previous post was at 01:31 AM ----------
xdaprae said:
I'm not on realme UI now.
So,if I want to try this ROM ,I should go into twrp and flash the "ColorOS7_Firmware_RMX1901.zip" first ?
then do I need reboot or just Wipe Dalvik,Cache,System,Data and vendor and flash this rom?
Click to expand...
Click to collapse
Mate you need nothing else.
Just go to TWRP 3.4.0.0
Wipe Cache,Dalvik,Vendor,Data,System
Flash the rom
Factory Reset
That's it
---------- Post added at 01:36 AM ---------- Previous post was at 01:33 AM ----------
Echaeos said:
I Had problems with gapps, It tells me that google protect doesn't protect my phone so no gapps worked but I did't install magisk, idk maybe was for that
Click to expand...
Click to collapse
Well it's piece of cake.
Just get the Device ID app, Copy the 15 digit framework code from GSF ID section and paste that code on Google's registry.
There's a tons of tutorial out there for it.
I am using Pico opengapps on this rom and seems to work awesome.
---------- Post added at 01:37 AM ---------- Previous post was at 01:36 AM ----------
Maya-Senpai said:
thank you for the reply, I shall wait for the more stable version comes out
Click to expand...
Click to collapse
Well it's piece of cake.
Just get the Device ID app, Copy the 15 digit framework code from GSF ID section and paste that code on Google's registry.
There's a tons of tutorial out there for it.
I am using Pico opengapps on this rom and seems to work awesome.

If you can't install another rom is because you don't have the official firmware [10]
RyanCr7 said:
Some of the apps like Messenger and Chrome freezing sometimes.The rest is pretty good.
I can see battery improvement,gaming improvement and it kinda feels nice to use.
Although haven't figured out how to take screenshots yet cause three finger drag or pressing the buttons doesn't seem to work.
Idk why but this is the only custom rom I can use.The rest doesn't boot on my Chinese variant.
So having a new experience was nice.Thank you and everybody else who helped to create it.
---------- Post added at 01:33 AM ---------- Previous post was at 01:31 AM ----------
ANSWER:
Yo tambien no podia instalar otra rom en la variante china, pero descubri que era por que la rom que tenia estaba en android 9, cogi y flashe la rom original de la version china y actualice a android 10, despues de eso ya pude instalar cualquier rom.
Click to expand...
Click to collapse

SuperBryanPro said:
RyanCr7 said:
Some of the apps like Messenger and Chrome freezing sometimes.The rest is pretty good.
I can see battery improvement,gaming improvement and it kinda feels nice to use.
Although haven't figured out how to take screenshots yet cause three finger drag or pressing the buttons doesn't seem to work.
Idk why but this is the only custom rom I can use.The rest doesn't boot on my Chinese variant.
So having a new experience was nice.Thank you and everybody else who helped to create it.
---------- Post added at 01:33 AM ---------- Previous post was at 01:31 AM ----------
ANSWER:
Yo tambien no podia instalar otra rom en la variante china, pero descubri que era por que la rom que tenia estaba en android 9, cogi y flashe la rom original de la version china y actualice a android 10, despues de eso ya pude instalar cualquier rom.
Click to expand...
Click to collapse
My problem was with the recovery.Changed the recovery to OrangeFox Beta and everything works fine now.
Click to expand...
Click to collapse

Changelog / 10-10-2020
THANKS

Changelog / 10-10-2020
use google dailer and make it default

I'm trying the rom again, now gapps works well, I found problems with Gps, I'm in Italy and I'm on chinese version I don't know if this is useful

hypercleric said:
use google dailer and make it default
Click to expand...
Click to collapse
Is this the latest beta? The one that was shared in Telegram group?

rebooting to recovery!!
im being rebooted to recovery mode . I tried flashing boot.img from fastboot mode. bt that didn work too . Almost all custom roms are giving this same issue . PLease helpp

prince_jr said:
im being rebooted to recovery mode . I tried flashing boot.img from fastboot mode. bt that didn work too . Almost all custom roms are giving this same issue . PLease helpp
Click to expand...
Click to collapse
Go to wipe - format data - write yes
Do this while flashing every rom
Phone will boot

Why there is no updater after 2020 specially Security Patch..??

@hypercleric THREAD CLOSED as not compliant with GPLv2 and download link removed.
Please check your conversaions and advise the moderators team when ready to provide a workable link to kernel source.

Unofficial TWRP Recovery 3.5.2_9-0

on https://github.com/gokur20/twrp_xiaomi_lotus_-Mi-Play-/releases you can the TWRP compiled for our Xiaomi Mi Play.
It works with fw_lotus_miui_MIPLAYGlobal_V11.0.10.0.OFIMIXM_1600406463_8.1 and my be with other versions.
Instructions:
in fastboot mode:
fastboot flash recovery TWRP--lotus-20210930-Unofficial_v1.0.img
fastboot reboot
Click to expand...
Click to collapse
at the startup press and hold VolUp to enter in TWRP.
Note: If Android starts, the stock recovery will override TWRP.
To avoid that You need to patch boot.img with Magisk.
You can send file with adb command to sdcard with:
adb push <nome file> /external_sd
Click to expand...
Click to collapse
What does not work: mtp and crypto.
If you have suggestions to make decrypt feature working or comments, you are wellcome.

Any screenshot for this?

{
"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"
}
Device tree: https://github.com/gokur20/twrp_xiaomi_lotus_-Mi-Play-
Kernel tree: Prebuilt
Stock Android 8.1.
Installed LineageOS 16 GSI.
The device should use Full Disk Encryption (ro.crypto.type=block)
I have added TW_INCLUDE_CRYPTO := true in BoardConfig.mk and encryptable=/dev/block/platform/bootdevice/by-name/metadata flag in fstab because fstab in vendor partition has forcencrypt=/dev/block/platform/bootdevice/by-name/metadata flag and now the recovery asks for password but neither default_password and pin lock work. If You try to format data when you restart system data partition will be encrypted again.

gokur20 said:
View attachment 5445003View attachment 5445001View attachment 5445009View attachment 5445011View attachment 5445007
Árvore de dispositivos: https://github.com/gokur20/twrp_xiaomi_lotus_-Mi-Play-
Árvore do kernel : Pré-construído
Estoque Android 8.1.
LineageOS 16 GSI instalado .
O dispositivo deve usar Full Disk Encryption (ro.crypto.type=block)
Eu adicionei TW_INCLUDE_CRYPTO := true em BoardConfig.mk e encryptable=/dev/block/platform/bootdevice/by-name/metadata flag em fstab porque fstab na partição do fornecedor tem forcencrypt=/dev/block/platform/bootdevice/by- flag name/metadata e agora a recuperação pede senha, mas nem default_password e pin lock funcionam. Se você tentar formatar os dados ao reiniciar, a partição de dados do sistema será criptografada novamente.
Click to expand...
Click to collapse
O Majisk mais recente funciona nesse método ou não?
gokur20 said:
on https://github.com/gokur20/twrp_xiaomi_lotus_-Mi-Play-/releases you can the TWRP compiled for our Xiaomi Mi Play.
It works with fw_lotus_miui_MIPLAYGlobal_V11.0.10.0.OFIMIXM_1600406463_8.1 and my be with other versions.
Instructions:
in fastboot mode:
at the startup press and hold VolUp to enter in TWRP.
Note: If Android starts, the stock recovery will override TWRP.
To avoid that You need to patch boot.img with Magisk.
You can send file with adb command to sdcard with:
What does not work: mtp and crypto.
If you have suggestions to make decrypt feature working or comments, you are wellcome.
Click to expand...
Click to collapse
Does the latest Majisk work in this method or not?

Hey man, thanks for sharing TWRP. It works!
I've been trying to flash some GSI images (Android 11 and 10) but I was unable to boot.
You've mentioned on the thread you were able to install LineageOS 16. Which version was it?
I grabbed the last release from LineageOS 16 and surprisingly was the only ROM which started booting up for me, but keeps bootlooping. Which release date is yours?
Thanks again

Here's the newest version compiled by 4pda member:
twrp-lotus-0.1.2 - Google Drive
drive.google.com
There are 2 designs - stock and material.
MTP doesn't work and most likely never will.
Only way to send data is through adb (push or sideload) and of course using memorycard or OTG (USB flashdrive).
In case of bootloop to TWRP flash remove_encryption_Mi_Play.zip
or if you prefer manually copy file fstab.mt6765 to vendor/etc/ and give it 0644 permissions.
It is advisable to reboot to recovery from adb, not button combo.
In case of /system not mounting automatically, enter this command to terminal:
mount - o remount, rw /system
Original thread:
Xiaomi Mi Play - Обсуждение - 4PDA
Xiaomi Mi Play - Обсуждение, Смартфон, 5.84
4pda.to

Thanks. I really would like to install a newer Android, otherwise I'll rollback to stock ROM. I'll give it a try on Pixel Experience and LineageOS 18 GSIs.
Which is The lastest compatible custom img you know that is possible to install on this device?
Alright. I'm rebooting to recovery/bootloader through adb commands since my VOL- button has broken. Thanks for the input.

Hi, i tried to install TWRP on my Mi Play.
Got all the per-requisites : MU account , phone unlocked.
I rebooted to bootloader and see the fastboot logo then type :
Code:
fastboot flash recovery TWRP--lotus-20210930-Unofficial_v1.0.img
fastboot reboot
the result of the flashing :
No error during flashing.
The phone reboot, then I immediately hold the volume UP button, and it is stuck to the "MI mi.com" logo and "unlocked" at the botton, and nothing happens.
Holding the power button reboot to android.
Did I miss a step ? Thanks for you help !

xodeax said:
reboot, then I immediately hold the volume UP button, and it is stuck to the "MI mi.com" logo and "unlocked" at the botton, and nothing happens.
Holding the power button reboot to android
Click to expand...
Click to collapse
I don't remember exactly but try holding Vol+ even before reboot command. So there's no chance that you were too late by fractions of nanosecond.
Or maybe you quit too early? Give it at least a minute or two with button held.

[OFFICIAL] LineageOS 20 for OnePlus 5 (cheeseburger)

{
"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"
}
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to do a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on cheeseburger.
Downloads
Download LineageOS 20
Source code
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
The device specific source code can be found in the LineageOS Github repo.
OnePlus 5 device tree
OnePlus MSM8998 kernel
Bug reports:
Please submit bugs and other errors in this thread
Donate to support development:
Donate via PayPal to vware
Contributors
Georg Veichtlbauer
And of course all LineageOS & Android contributors
OS Version: Android 13
Kernel: Linux 4.4.302
Version Information
Status: Stable
Created 2022-09-17
Last Updated 2022-12-31

Major Changes (December 4):
- Kernel updates
- SELinux improvements

I would like to say that the new version (0928) is causing system UI crash. I'm coming from version 0907, which worked correctly, and I can't generate any logs as after booting the screen keeps turning on and off and I can't unlock the phone. Sometimes the phone reboots and not even in safe mode the phone works. I formatted data and cache via recovery (TWRP) and also via fastboot, but the problem remains.

that's concerning indeed - there were no such troubles in internal testing. i uploaded a new version (10-05), please try that and let me know how it went!

qsnc said:
that's concerning indeed - there were no such troubles in internal testing. i uploaded a new version (10-05), please try that and let me know how it went!
Click to expand...
Click to collapse
Yes, 10-05 build is working great, thank you very much

At the moment i use the latest official LineageOS 19.1.
Can i install this as an upgrade, and than when the official will be released i upgrade to that without any configuration or data loss?

do not upgrade if you're on the official build, better to wait for this to go official. as things stand, it won't take very long anyway.

I was going to flash the new release. Should I wait for it or can I flash? I am still on MSMX and have powered ON my OP5 after almost 6 months now.

Does this rom support signature spoofing?

update now live, plenty of changes yet again. see post #1 and #2
give it a good whirl and try to find problems!

Is the clock running? (when operating WITHOUT WLAN and WITHOUT MOBILE DATA)
Or does LOS 20 forget the time every time it restarts?
LOS 19 forgets the clock and always starts at 03:44 is it the same here?

i was not even aware of this issue. now that i am, yes, it is actually fixed!
also, when you update to the latest official 19.1 (that means: next week, oct 31), it will be fixed as well.

Thanks for the great work!

qsnc said:
i was not even aware of this issue. now that i am, yes, it is actually fixed!
also, when you update to the latest official 19.1 (that means: next week, oct 31), it will be fixed as well.
Click to expand...
Click to collapse
So, basically 2 weeks release cycle, right mate? Also, LOS20, and not 19.1, right?

official releases (on download.lineageos.org) are weekly. and no, i meant 19.1, as 20 is not official just yet. i added the fix, but you'll only get it on the next release.
it seems lineage 20 is not far off now though

I am very new to A13, but can someone please guide me how to allow Notifications for some apps? I am on this build, and I can not get the app to get access.
Edit: This is happening with almost every app. :-(

Ignore. I finally found the solution.

qsnc said:
i was not even aware of this issue. now that i am, yes, it is actually fixed!
also, when you update to the latest official 19.1 (that means: next week, oct 31), it will be fixed as well.
Click to expand...
Click to collapse
I just tested the FIX from the clock in LOS 19. Thank you for the great work. My dashcam no longer needs a hotspot which I ran automatically using Gmaps. THANK YOU VERY MUCH

updated build is now live -- see first post
Badtz-Maru said:
I just tested the FIX from the clock in LOS 19. Thank you for the great work. My dashcam no longer needs a hotspot which I ran automatically using Gmaps. THANK YOU VERY MUCH
Click to expand...
Click to collapse
you are welcome!

qsnc said:
Introdução
Se você não conhece o LineageOS e deseja ler sobre os antes de instalá-lo, você pode dar uma utilização no site oficial .
Características
Individualidade
Segurança
Longevidade
Instalação:
Se você não estiver disponível no sistema operacional padrão, primeiro de uma recuperação personalizada. Você pode obter a recuperação recomendada no link oficial de instruções de instalação abaixo.
Se você estiver vindo de fábrica ou outras ROMs, faça uma redefinição de fábrica.
Como sempre, certifique-se de instalar esta ROM de backup.
Instruções mais medidas em:
Instale o LineageOS no cheeseburger .
Transferências
Baixar Lineage OS 20
Baixar Recuperação de Linhagem
Código da fonte
Todo o código-fonte do LineageOS está disponível no substituto do LineageOS Gith . E se você quiser contribuir com o LineageOS, visite o Gerrit Code Review .
O código-fonte específico do dispositivo pode ser encontrado no Github do LineageOS.
Árvore de dispositivos OnePlus 5
Núcleo OnePlus MSM8998
Relatório de erros:
Envie bugs e outros erros neste tópico
Doe para o desenvolvimento:
Doe via PayPal para vware
Contribuintes
Georg Veichtlbauer
E, claro, todos os contribuidores do LineageOS e Android
Versão do SO: Android 13
Kernel: Linux 4.4.302
Versão informação
Situação: Estável
Criado 2022-09-17
Última atualização 2022-11-01
Click to expand...
Click to collapse
Gcam work?

[ROM][OFFICIAL][ginkgo][13] crDroidAndroid v9.x

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
gapps (Download from here)
First time installation:
Boot recovery
Format Data, Wipe system
Install ROM
Install gapps (Optional)
Reboot
Update installation:
Boot recovery
Install ROM
Install gapps (Optional)
Reboot
NOTE: If all the flashing process succeeds the terminal output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error which is also fine.
Sources:
ROM: https://github.com/crdroidandroid
Device sources: https://github.com/crdroidandroid
Download:
ROM https://crdroid.net/ginkgo/9
Changelog: https://raw.githubusercontent.com/c..._vendor_crDroidOTA/13.0/changelog_ginkgo.txt
Known issues:
* You tell me
Visit official website @ crDroid.net
DarkJoker360 Telegram Updates
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

Reserved

only ginko? not willow?

willow - Not boot, constalty reboot.

Although I haven't tried it myself yet, but if this changelog is true then it should work...

Just installed and i see that there is no fingerprint unlock :|

For some reasons, OP doesn't talk about it here but in the telegram channel he make it clear that this is an experimental build. not yet official. So flash for testing purposes only.
NOTES
* crDroid source code is still WIP, please don't report missing customizations or rom side issues
* It will be official once we officially launch 9.x version
* crDroid Bootanimation temporary disabled as it is currently broken globally for low ram devices
Click to expand...
Click to collapse

mzcl-mn said:
Although I haven't tried it myself yet, but if this changelog is true then it should work...
View attachment 5722271
Click to expand...
Click to collapse
This changelog is from 12L

Estoy probando esta rom de android 13 en un redmi note 8T, y hasta ahora funciona todo bastante bien y es muy rapida.
Lo que no funciona son los ajustes de crdroid.
Solo lo digo, no por quejarme sino para que el constructor de esta estupenda rom lo tenga en cuenta para futuras versiones.
llevo tiempo usando las diferentes versiones de Crdroid y estoy encantado con ellas.
Seguid asi.
Mod translation:
I'm testing this android 13 rom on a redmi note 8T, and so far everything works pretty well and it's very fast.
What doesn't work is the crdroid settings.
I'm just saying it, not to complain but so that the builder of this great rom takes it into account for future versions.
I have been using the different versions of Crdroid for a long time and I am delighted with them.
Keep going.

Ahora toca esperar a las versiones oficiales y poder instalar las gapps correspondientes para tenerlo operativo a 100X100
Mod translation: Now it's time to wait for the official versions and be able to install the corresponding gapps to have it operational at 100X100

New crDroidAndroid 13.0 v9.x update
Changelog
* Synced with latest crDroid v9.x source code
* Merged October 2022 security patches
* Switch to LineageOS Aperture camera

thanks @DarkJoker360 for your great work! we really appreciate it.
is this still experimental or already suitable for daily driving? does twrp decryption work?

gothmog123 said:
thanks @DarkJoker360 for your great work! we really appreciate it.
is this still experimental or already suitable for daily driving? does twrp decryption work?
Click to expand...
Click to collapse
I just tried to update, but had to clean flash, because of said encryption. Or if anyone has reliable recovery I'd be happy to use it.

Thanks for your great work!.
We really appreciate it.

So far I like it best from all the 13 ROMs I've tried. I think I've found a little bug, does anyone else's statusbar clock hide itself even if auto-hide is disabled?

LeppeRMessiaH said:
So far I like it best from all the 13 ROMs I've tried. I think I've found a little bug, does anyone else's statusbar clock hide itself even if auto-hide is disabled?
Click to expand...
Click to collapse
This bug for me too =(

Anyone else having trouble getting edit rights for the microsd card?

Rom is now official

Those who flashed this please share your feedback.
How is camera?
Is mic working in VoIP apps like Telegram, Whatsapp etc.
How is battery consumption?

bahtsiz_bedevi said:
Those who flashed this please share your feedback.
How is camera?
Is mic working in VoIP apps like Telegram, Whatsapp etc.
How is battery consumption?
Click to expand...
Click to collapse
Everything works and everything is amazing. Battery management is genius. I never thought Android could be this good.