Develop Bugs

[ROM][UNOFFICIAL][Android 11] LineageOS 18.1 [joyeuse/miatol][22/01/21]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
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. You can also view the Changelog for a full list of changes & features.
We have progressed to LineageOS 18.1
Flash instructions :
Use latest pbr recovery for miatol, supports decryption - beta available here, https://pitchblackrecovery.com/joyeuse/.
DO NOT - Wipe data!, ONLY FORMAT, otherwise you may hose the phone.
There is a way to fix this without the fastboot factory clean, flash and lock with the official Xiaomi tool, which was forcing you to clean and lock... now available here: https://github.com/Szaki/XiaomiADBFastbootTools
If you hose the phone, use this tool - you need to install JRE though, as the tool is Java base. Put your phone is fastboot, use the tool to download the latest global rom (or whichever). Then go to where its downloaded, extract the .xy/tar file, then go back into the tool and under "image" select the folder INSIDE the folder you just extracted, then select "clean install" and install it. This will flash the majority of imgs but will error out at the end and be unable to create the "user data" partition.
That's okay, because all of the partitions will be setup again, and you can flash any rom you want again. So when its done, and still in fastboot, fastboot flash recovery recovery.img (recovery.img being the latest joyeuse pbr recovery, you renamed to recovery.img and were in that folder in the command prompt, so it will flash that recovery) or use the tool to select that recovery and it will flash it for you and reboot into for you if you like.
(Do this step last, after Magisk, if you want to unencrypt, no worries if you don't unencrypt - PBR recovery will decrypt your data ON THE SECOND TRY OF ENTERING YOUR SCREENLOCK PIN NUMBER...), the new PBR Miatol Beta 10/14/20, fixes this issue, it is now decrypted on the first entry of the phone's lockscreen PIN. Then flash disable_dm-verity_forceencrypt.zip available here for those who want decrypted data partition: https://zackptg5.com/android.php#disverfe and other places as well.
If you are encrypted and decide to unencrypt later, you will need to flash the disable_dm-verity_forceencrypt.zip in miatol recovery, then format data. Store roms, gapps, recoveries (just in case), disable_dm-verity, magisk install and uninstall and all that stuff on the SD card, so you can use them in PBR after you format DATA (the first step after installing PBR miatol recovery), just FYI. Then do the following:
Flash ROM
Flash OpenGAPPS for android 11 nano
Boot into android, make sure its working and install Magisk Manager 8.0.7, then reboot into recovery and install Magisk 21.4 (in recovery, I did not need to extract the boot.img and patch in Magisk Manager, and reboot into recovery to flash the patched boot.img, but your results may be different): https://github.com/topjohnwu/Magisk/releases. If you want to unencrypt (no guarantees its permanent though) you need to format data, THEN FLASH MAGISK, then flash disable_dm-verity (always the last step)- I usually wipe dalvik and cache too.
USE LATEST MIATOL PBR RECOVERY, PLEASE.
SD card issues resolved with the implementation of the EXFat android driver.
Source Code: https://github.com/LineageOS
Kernel Source: https://github.com/Redmi-SM6250 or Stock kernel from Miui
Apologies for the lack of updates, was diagnosed with stage 4 metastatic cancer and this project was not on my priority list anymore...
Update 28/1/21:
Release notes:
LineageOS
Device: Unified (Miatoll)
Developers: ScaryMen1325 & Loptr4
ROM Version: 18.1
Android Version: Android 11
Build date: 22/01/2021
Status: UNOFFICIAL
Changelog:
• Fixed power related issues
• Added useful apps (thanks to Dev: Emulond for that)
• Other fixes and performance improvements
Notes:
• It's 2nd test version, if you found bugs, give log.
• Using loki kernel by default, haven't tested custom kernel.
Download here:
https://drive.google.com/file/d/1M5-cRBfrRdBdNYGzy5G9bOa1Ncf5JkE4/view?usp=sharing
Please note this is a unified release, you should do a clean install unless you're coming from a unified ROM alreadyl.
Will keep you more regularly updated now that I'm out of the hospital....

Perfect will try tonight

Belpek said:
Perfect will try tonight
Click to expand...
Click to collapse
Have you tried it?
How is it? Good for daily?

There are so many Joyeuse LineageOS ROMs I don't even know where to start.

i don't see you mentioned mobile network in bugs section; does it work? i'll try this rom in a couple hours

Tell me please. If phone will be locked with black screen and i say "ok google". Will it work? Or it will work only if screen is unlocked?

sorry if its not much, since i can't do much on this rom. flashed nikogapps, google sign-in succeded but it seems that i cant install anything from play store.
(dumb me forgot to screenshot, it only says "something went wrong" when i try to install an app from play store)
about ok google from lockscreen/screen off, i tried it, also not working. can't confirm about volte since volte still relatively new here and hasn't developed that much.

Why nikgapps? Open gapps nano is recommended.
Sent from my Redmi Note 9 Pro using Tapatalk

Flash it and using it by now, so far so good, sometimes it gets a little freeze but nothing serious, miracast reboots phone so dunno if this is a bug or not, proximity sensor is another one cuz while I was in speaking with my pal screen was on all the time and my ear activated bluetooth and DND
Have nothing to talk about VoLTE cuz in my country is not available.
ANX modules left my phone in bootloop so instead I went for GCam. Flash unofficial opengapps nano and make sure to use Wi-Fi to complete the first run.
Magisk canary works so it can be rooted.
Keep the hard work!
*Sorry if I made some writing mistakes, english is not my native language. Cheers!!

Tried flashing the latest build (02.10.20) using the latest TWRP from the thread you linked but I get the "can't install package over new build" error. Is it required to come from stock miui?

gigahurts said:
...
Newer Build:
https://mega.nz/file/PlkgiSzS#C_tIspgbtGDrweztQ83lADHyEQf4dTkIUiSAqgjVAFk
NOTE: You should be on 11.0.7.0 QJZMIXM (EU) Global firmware for this build. Also, I have a newer build, but its not ready for primetime and has issues with SMS and Call Log enabling permissions.
Oh, and BTW, if you hose your ROM/Phone, just flash vbmeta.img in fastboot to avoid using the factory fastboot img flash, otherwise you many need to wait another 7 days to unlock the bootloader.
...
The dev for this build is: @wight554, all thanks and credit go to him, he is awesome, and I, for one, seriously appreciate this ROM as it works very well for me. It is so snappy and smooth, with a super fast boot time, no reboots and generally pretty frickin AWESOME!
...
Click to expand...
Click to collapse
First of all, thank you guys @gigahurts & @wight554 very much for working on supporting this device :good::good:
Could you pretty please confirm that you intend to continue working on this and maintain this device? I am planning to buy two joyeuse devices for daily usage and I would like to be at least partially sure I can run LineageOS on them. Also do you think the current known issues will be possible to resolve in the near-ish future? :fingers-crossed: Thanks for your reply in advance. All the best.

Swiftor said:
First of all, thank you guys @gigahurts & @wight554 very much for working on supporting this device :good::good:
Could you pretty please confirm that you intend to continue working on this and maintain this device? I am planning to buy two joyeuse devices for daily usage and I would like to be at least partially sure I can run LineageOS on them. Also do you think the current known issues will be possible to resolve in the near-ish future? :fingers-crossed: Thanks for your reply in advance. All the best.
Click to expand...
Click to collapse
hey Swiftor,
We will continue to work on this rom. LineageOS has been around a long time, development has spread across so many devices, however, the hardware of many devices is very similar, so support will continue. The last Redmi Note 8 pro, had a mediatek SOC, and made development difficult until MIUI decided to release its source. The snapdragon platform is very mature and is more easily and readily available to develop roms for. Redmi Note 10 pro has been released in India, and has a slightly better processor 765g vs 730g, but the kernel and hardware are very similar, so I development for this phone and the Note 10 pro should parallel and continue. We are working on submitting an official 18.0 release, but have to have all hardware (and software) fully functional and as close to zero bugs as possible. I predict development to continue as long as Xiaomi continues to release new MIUI roms for this device (and they continue to release roms for phones much, much older than this).
I have updated the first post with a newer release. Let me know if you have any issues and I will try to help.
Thanks for the props too

does magisk 21 work on the latest build? really excited for android 11

So this will not be compatible with curtana devices?

Thanks to all developers for this rom. Installed on Curtana with Magisk canary, I had to use Magisk props to pass safetynet. All seems to be working ok.??

everything is working perfectly and its showing charging rapidly , it was on 88% and showing 10 minutes until full
everything is completely smooth gonna keep it for my daily use

Bantryred said:
Thanks to all developers for this rom. Installed on Curtana with Magisk canary, I had to use Magisk props to pass safetynet. All seems to be working ok.
Click to expand...
Click to collapse
hi! wich props do u use for fingerprint? i can't pass safety on my joyeuse

there're few thing that you need to fix @gigahurts
1) you putting wrong kernel source. its should be this link
2) why would you mirror it when you can get it in his sourceforge

Why is today's build 590MB while all others are 1.1GB?

pwnaz said:
hi! wich props do u use for fingerprint? i can't pass safety on my joyeuse
Click to expand...
Click to collapse
Sorry for the delay, Im on Curtana so dont know if it makes a difference, but I used no. 16 - mi 10 Global(11)
I also had to hide Magisk Manager

Paranoid Android Ruby Beta - Oneplus 7T Pro

We are very excited to announce the release of Paranoid Android Ruby, based on Android 11.
On the first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app, included in our builds.
Our builds are based on the Code Aurora Forum Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Notice
As we are growing on our list of supported devices in each release, we require of a stronger build environment so we can speed up the compilation process for releases. Based on the actual Quartz 4 list, we support over 30 devices, which takes between 2 and 3 days for all the builds to be completed without counting possible compilation issues or rebuild needs, based on our current specs.
We kindly ask all of you that are in position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.
You can donate here
If you'd like to donate to me personally https://paypal.me/ritujbeniwal
Device-specific issues
None as of now.
Note: Custom kernels are NOT supported unless the kernel says it supports PA and GMS is included!
Requirements
My preferred logging format is:
adb logcat -b all -d *:E > logcat-err.log
adb logcat -b all -d > logcat.log
adb shell dmesg > dmesg.log
Instructions
Note: Make sure you have latest OOS flashed beforehand on both the slots.
Note: This will wipe your complete data partition (this includes ALL user data)
1) adb reboot bootloader
2) fastboot update <pa_fastboot_zip>.zip
3) Once the process is completed the device will reboot, press the vol-down button while the phone reboots to boot into recovery
4) Select Factory Data reset and press "Yes" (navigation via volume buttons)
5) Reboot
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Community (Telegram)
Note: This is a slightly modified version of PA and does not represent how official PA will look like.
Download Link: https://sourceforge.net/projects/aospa-extended/files/oneplus7tpro/
Security patch level: June 2021
Device Source code: https://github.com/ritujb/android_device_oneplus_oneplus7tpro
Kernel Source code: https://github.com/timocapa/GaltsGulch-sm8150
Source code: https://github.com/AOSPA
Cheers and #StayParanoid!

Here we go

Can't wait to try this. Used PA way back on my Sammy S3 and my OP3

can you post features of the rom? never used Aospa but I quess it has more features than PA which is pretty basic? thanks for your hard work

Did not work for me, got me into "Crashdump" mode.

Looks it all this wait was totally worth it, was able to boot it up without any issues, everything is working as expected, no crashes or random reboots till now, everything is so smooth and flawless really great word dev.
Thanks a ton for your hard work and the ROM.
Can be used as a daily driver for sure.
Only minor bug I noticed is while charging it shows slow charging but when checking the Ampere its actually dash charging, rest everything seems to be pin point perfect for now.
Update: Vibrate intensity is pretty low/soft, would be great if we could bump it up a bit.
Thank you.
{
"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"
}

Hi,
I'm having trouble successfully installing the ROM. So I was wondering if you maybe could guide/help me through the installation process since when I tried the one you listed, it got me into Qualcomm crashdump mode. Even though, I followed every step to full extend (flashing recovery and so on). But the whole process resulted in me bricking my phone, so I had to bring it back to Oxygen OS using the MSM Tool. So it would be really nice if you could provide me with some installation steps or at least some help.
Kind regards, andr052h

Same here. Followed instructions an stuck in Android Recovery with the following message after doing the Factory Data Reset:-
Cannot load Android System. Your data may be corrupt. etc.
Will reset with MSM and try again

chiiiiiiippppppp said:
Same here. Followed instructions an stuck in Android Recovery with the following message after doing the Factory Data Reset:-
Cannot load Android System. Your data may be corrupt. etc.
Will reset with MSM and try again
Click to expand...
Click to collapse
Did you have latest OOS installed first?

L4WL13T said:
Did you have latest OOS installed first?
Click to expand...
Click to collapse
Yes. Used MSM to get 10.0.13 and then upgraded to 11.0.0.2 HD01BA. Made sure was in both slots. Followed instructions exactly.
Tried 3 times and giving up and going back to PE. Shame as I used to like PA when I had my Note 3 years ago.
Device is HD1913 by the way in case that helps anyone else.

chiiiiiiippppppp said:
Yes. Used MSM to get 10.0.13 and then upgraded to 11.0.0.2 HD01BA. Made sure was in both slots. Followed instructions exactly.
Tried 3 times and giving up and going back to PE. Shame as I used to like PA when I had my Note 3 years ago.
Device is HD1913 by the way in case that helps anyone else.
Click to expand...
Click to collapse
Odd, the only other thing I can think of off the top of my head is to make sure you're flashing using fastbootd and not regular fastboot. Hopefully you'll figure it out, fantastic ROM.

Hows the FOD in this ROM?

Schemes do not work for me it always crash when i click on it so i cant change fonts etc. Any idea?

L4WL13T said:
Did you have latest OOS installed first?
Click to expand...
Click to collapse
did you try to format data then just boot into the system? usually works for me

New update is out for the ROM
June sec patch
Automatic brightness improvements
Battery life improvements
FOD animation
UI improvements

L4WL13T said:
Did you have latest OOS installed first?
Click to expand...
Click to collapse
I can't get this ROM to boot either... I MSM tooled back to 10.0.14, OTA updated and manually updated and also flashed with twrp OOS 11.0.1.1 and followed directions to the T! Either Crash Dumps, or boots back into OOS 11. Does it not work on the OOS 11 Global maybe? I really want to try this ROM! Been trying for almost 3 days now... Any advice is greatly appreciated! I have the HD1910 (Chinese variant) I had the HD0IAA global firmware installed everytime I tried if that helps at all? I also tried fastboot, and fastbootd with 3 different TWRP versions, and the lineage18.1 recovery, and the stock OOS recovery with fastbootd. Also have A and B slot on the 11.0.1.1 firmware. I used the copy partition zip and also manually flashed both slots to no avail...

parag0n1986 said:
I can't get this ROM to boot either... I MSM tooled back to 10.0.14, OTA updated and manually updated and also flashed with twrp OOS 11.0.1.1 and followed directions to the T! Either Crash Dumps, or boots back into OOS 11. Does it not work on the OOS 11 Global maybe? I really want to try this ROM! Been trying for almost 3 days now... Any advice is greatly appreciated! I have the HD1910 (Chinese variant) I had the HD0IAA global firmware installed everytime I tried if that helps at all? I also tried fastboot, and fastbootd with 3 different TWRP versions, and the lineage18.1 recovery, and the stock OOS recovery with fastbootd. Also have A and B slot on the 11.0.1.1 firmware. I used the copy partition zip and also manually flashed both slots to no avail...
Click to expand...
Click to collapse
used latest platform tool
and follow the instructions

jahidinbedod said:
used latest platform tool
and follow the instructions
Click to expand...
Click to collapse
I am using the latest platform tools. At least I thought I was? I'll check again to make sure I have the most updated version. The instructions aren't very clear either. It says to reboot to bootloader with the ADB command. That is regular fast boot. On a post a few down, it is mentioned that the only thing they could think of is to make sure to flash and fastbootd. So which one are we supposed to use? Do we use the stock OOS recovery? The only way I know to flash the newest Android 11 is from the repo thread or flashable zips. I also tried it with the OTA update and the copy partition zip still didn't work from fastbootd and fastboot. Every time I do it I get an error that there is no boot image maybe I need to redownload the ROM?

parag0n1986 said:
I am using the latest platform tools. At least I thought I was? I'll check again to make sure I have the most updated version. The instructions aren't very clear either. It says to reboot to bootloader with the ADB command. That is regular fast boot. On a post a few down, it is mentioned that the only thing they could think of is to make sure to flash and fastbootd. So which one are we supposed to use? Do we use the stock OOS recovery? The only way I know to flash the newest Android 11 is from the repo thread or flashable zips. I also tried it with the OTA update and the copy partition zip still didn't work from fastbootd and fastboot. Every time I do it I get an error that there is no boot image maybe I need to redownload the ROM?
Click to expand...
Click to collapse
idk, i just follow the intruction and its work perfectly on my device
after step 2 on normal fastboot device should be boot automatically to fastbootd for installing rom, just wait until finish
than follow next step, goodluck.
im using window and disable driver signature
dunno ¯\_(ツ)_/¯

jahidinbedod said:
idk, i just follow the intruction and its work perfectly on my device
after step 2 on normal fastboot device should be boot automatically to fastbootd for installing rom, just wait until finish
than follow next step, goodluck.
im using window and disable driver signature
dunno ¯\_(ツ)_/¯
Click to expand...
Click to collapse
I uninstalled my SDK tools and reinstalled them. redownloaded the Rom and started over and it finally worked! Very nice ROM

Development [ROM][Android 12L][UNOFFICIAL][OTA] LineageOS 19.1 for Redmi Note 9 5G and Redmi Note 9T

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1 (S), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
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. You can also view the Changelog for a full list of changes & features.
Downloads:
- Here
Flashing instructions
- Here
Bugs:
- Backlight does not turn off on offline charging
Notes:
- SELinux is enforcing
- SafetyNet passes by default
- Custom recoveries, like TWRP and OFRP, are not supported
- Custom kernels, like Eva Kernel, are not supported
- OTA support is present
- Kernel is prebuilt from stock since Xiaomi has not released the source code for cannon-s-oss (Taken from cannong 13.0.3.0)
Required firmware:
- MIUI 13 based (Up to MIUI 13.0.3.0. MIUI 12.x is not supported)
Sources:
- LineageOS
- Device sources
Telegram group:
- Here
Happy modding!

Reserved

Thank you for awesome work!

tried this, sim card stopped working

jokemaster21 said:
tried this, sim card stopped working
Click to expand...
Click to collapse
Send logs and check the reporting issues section of the guide
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.

LinkBoi said:
Send logs and check the reporting issues section of the guide...
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.
Click to expand...
Click to collapse
where do I find my logs
edit nvm I'll report the problem properly according to your guide

LinkBoi said:
Send logs and check the reporting issues section of the guide...
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.
Click to expand...
Click to collapse
here are the logs
Edit also it keeps bootlooping when I insert an sd card

jokemaster21 said:
here are the logs
Edit also it keeps bootlooping when I insert an sd card
Click to expand...
Click to collapse
See below:

LinkBoi said:
Okay. Try one thing first. Flash from recovery the package that I've attached, it will make your SELinux be permissive.
PS: Consider joining Telegram for more direct communication
Click to expand...
Click to collapse
Also I will need boot logs just to be sure. You can get them by rebooting your device and when you see the bootanimation do the following:
- adb root
- adb shell
- logcat -b all > /cache/logcat-boot.log
Wait a little while and press control+C to stop the process
Afterwards, send me the file from the /cache partition. You can reboot to recovery and use 'adb pull' to grab it in your PC like this:
- adb pull /cache/logcat-boot.log

LinkBoi said:
Also I will need boot logs just to be sure. You can get them by rebooting your device and when you see the bootanimation do the following:
- adb root
- adb shell
- logcat -b all > /cache/logcat-boot.log
Wait a little while and press control+C to stop the process
Afterwards, send me the file from the /cache partition. You can reboot to recovery and use 'adb pull' to grab it in your PC like this:
- adb pull /cache/logcat-boot.log
Click to expand...
Click to collapse
here you go,
btw since I don't have a sim card to use atm I can't use telegram

jokemaster21 said:
here you go,
btw since I don't have a sim card to use atm I can't use telegram
Click to expand...
Click to collapse
Which stock MIUI were you using before flashing LineageOS?

LinkBoi said:
Which stock MIUI were you using before flashing LineageOS?
Click to expand...
Click to collapse
13.0.3.0 I believe. I tried flashing 13.0.2.0, but it kept giving me an error that the SPL would be a downgrade and it wouldn't allow me to flash

jokemaster21 said:
13.0.3.0 I believe. I tried flashing 13.0.2.0, but it kept giving me an error that the SPL would be a downgrade and it wouldn't allow me to flash
Click to expand...
Click to collapse
You should flash 13.0.2.0 from fastboot. You need to download the full fastboot ROM for your specific model and then flash it from fastboot by running flash_all.bat or flash_all.sh (Depending on your OS)

LinkBoi said:
You should flash 13.0.2.0 from fastboot. You need to download the full fastboot ROM for your specific model and then flash it from fastboot by running flash_all.bat or flash_all.sh (Depending on your OS)
Click to expand...
Click to collapse
ok tried flashing it and it said it was successful, but when I tried booting it up it got completely bricked

jokemaster21 said:
ok tried flashing it and it said it was successful, but when I tried booting it up it got completely bricked
Click to expand...
Click to collapse
Check a couple of things:
- If your device powers up in any way, see if you can go into fastboot. If your device, on the splash screen says something like 'vbmeta verification failed, press the power button to continue', just press the power button to proceed (this would be due to AVB checks)
- If your device does not power up, then try plugging it in to your computer and see if it gets detected in any way
If it does, send a screenshot of Device Manager (Windows) or 'lsusb' (Linux)
Also, do you have the Global model or the Chinese one? I assume you got the Chinese one since 13.0.3.0 is not out for Global yet.
Either way, your issues before most likely stem from using newer firmware than the one I recommend.
PS: You should already have some technical knowledge to resolve such issues yourself if you're flashing custom ROMs and also keep in mind that 'bricked' says pretty much nothing (You must be more detailed when mentioning your phone's behaviour, like if it boots but stays on the splash screen, if it boots but stays on the boot animation etc)

LinkBoi said:
Check a couple of things:
- If your device powers up in any way, see if you can go into fastboot. If your device, on the splash screen says something like 'vbmeta verification failed, press the power button to continue', just press the power button to proceed (this would be due to AVB checks)
- If your device does not power up, then try plugging it in to your computer and see if it gets detected in any way
If it does, send a screenshot of Device Manager (Windows) or 'lsusb' (Linux)
Also, do you have the Global model or the Chinese one? I assume you got the Chinese one since 13.0.3.0 is not out for Global yet.
Either way, your issues before most likely stem from using newer firmware than the one I recommend.
PS: You should already have some technical knowledge to resolve such issues yourself if you're flashing custom ROMs and also keep in mind that 'bricked' says pretty much nothing (You must be more detailed when mentioning your phone's behaviour, like if it boots but stays on the splash screen, if it boots but stays on the boot animation etc)
Click to expand...
Click to collapse
it doesn't turn on in anyway, when I plug it into my computer it makes the windows sound that it's connected, but shows nothing on the device manager. it's a brick now

jokemaster21 said:
it doesn't turn on in anyway, when I plug it into my computer it makes the windows sound that it's connected, but shows nothing on the device manager. it's a brick now
Click to expand...
Click to collapse
You can recover anything on MTK anyways. Check mtkclient and this link for more info.

New LineageOS 19.1 Update // cannon and cannong // 27.08.22
Download:
- GitHub Releases
Changelog:
- Fixed minimum brightness issue (Thanks to @ganomin for finding out)
Bugs:
- None that I know of
Notes:
- Selinux is enforcing
- SafetyNet passes by default
- Custom recoveries, like TWRP and OFRP are not supported
- Custom kernels, like Eva Kernel, are not supported
- OTA support is present

LinkBoi said:
You can recover anything on MTK anyways. Check mtkclient and this link for more info.
Click to expand...
Click to collapse
no idea how to use this, too technical for me. maybe I could bring it into a repair shop.

[ROM][UNOFFICIAL][MONTHLY][EAS][R-HALs] Pixel Experience 13 [NORMAL/PLUS] for Xiaomi Mi5

{
"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 Xiaomi Mi 5 [Gemini]
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 features for the proper functioning of the device
Based on Android 13.0
Whats working?
Wifi
Wifi hotspot
RIL
Mobile data
GPS
Sensors
Camera
Flashlight
Camcorder
Bluetooth
NFC/GPAY
Lights
Sound / vibration
Fingerprint
WiFi Display
VoLTE
Double Tap To Wake
Buttons swap
Google Voice Match
SELinux enforcing
Safetynet
DON'T FLASH GAPPS, ALREADY INCLUDED
Download standard version from Android File Host
Download PLUS version from Android File Host
​
Flashing Instructions:
Pre-installation:
Pixel Experience Recovery (Download from here)
First time installation:
Fastboot or flash recovery image
Reboot to new recovery
Click on Factory Reset --> Format data/factory reset
Click on apply update and sideload the zip file or install it using an USB OTG
Enjoy
About Camera App: default camera app is GCAM version SGCAM_8.4.400.42.XXX_STABLE_V35 by Shamim. Everything works fine except 240 fps (1/8) slow motion videos
mandayugana shared his config xml file, which add the specific noise model for Gemini with Shamim GCAM, dowload it from my Github (sgcam-8.4-v35-pe13.xml) or from his post, apply to GCAM following this tutorial and say thanks to him for his great work
XDA:DevDB Information
Pixel Experience, ROM for the Xiaomi Mi 5
ROM OS Version: Android 13
ROM Kernel: Linux 4.4
ROM Firmware Required: MIUI V10.2.2.0.OAAMIXM as minimum target
Based On: AOSP
Source Kernel repo: Link
Gemini device tree repo: Link
Xiaomi msm8996-common repo: Link
Vendor repo: Link
Special thanks to
LineageOS
Pixel Experience
Shamim
xNombre
mandayugana

I'm currently using PixelExperience_gemini_12.1
Is it possible to directly update it via twrp? (I don't have a PC to install PErecovery)

ademuhamad said:
I'm currently using PixelExperience_gemini_12.1
Is it possible to directly update it via twrp? (I don't have a PC to install PErecovery)
Click to expand...
Click to collapse
I haven't tried but could work. Just be sure to format internal storage before rebooting into system

the rom is very laggy, and cpu usage between 50%-100% with nothing open :/

Echidna_Kawaii said:
the rom is very laggy, and cpu usage between 50%-100% with nothing open :/
Click to expand...
Click to collapse
Check what process is eating your cpu in the background, i have no problems at all with cpu usage on screen and with deep sleep

and also this giving Random reboot here :/

Echidna_Kawaii said:
and also this giving Random reboot here :/
Click to expand...
Click to collapse
No one reported random reboots, i never had once in a week of usage. Logs or never happened

-+BB+- said:
I haven't tried but could work. Just be sure to format internal storage before rebooting into system
Click to expand...
Click to collapse
ERROR:1 )l

暗夜很无语 said:
ERROR:1 )l
Click to expand...
Click to collapse
That's why I wrote could, I haven't tried and there are multiple versions of TWRP, if you experience problems flashing the ROM use my recovery

pretty much very stable rom... working everything very smothly...but one issue...after usung 1 or 2 shot with gcam its freeze the cam...and then can't open the gcam anymore...

Unfortunately I can't install it. It would be great if there was a zip file that can be installed with twrp. Thanks for your effort anyway.

after using 2-3 days.. i found some bug
1. after activated vibration mode no vibration icon showing in status bar
2. gcam not working (tried many version)
and after some times phone autometically try to reboot itself but stuck at mi logo.. have to forcefully tap on power button to reboot manually (happened every time i install different version of gcam) i had same issue in lineageOS 19
3. no ota updater option (maybe because its unofficial or i don't know)
4. don't have the option double tab on status bar area to lock screen
5. not showing am/pm in time

İST1907 said:
Unfortunately I can't install it. It would be great if there was a zip file that can be installed with twrp. Thanks for your effort anyway.
Click to expand...
Click to collapse
Could you please post the log of the error during the flash?
mrinfinity0007 said:
after using 2-3 days.. i found some bug
1. after activated vibration mode no vibration icon showing in status bar
2. gcam not working (tried many version)
and after some times phone autometically try to reboot itself but stuck at mi logo.. have to forcefully tap on power button to reboot manually (happened every time i install different version of gcam) i had same issue in lineageOS 19
3. no ota updater option (maybe because its unofficial or i don't know)
4. don't have the option double tab on status bar area to lock screen
5. not showing am/pm in time
Click to expand...
Click to collapse
1 and 5 are AOSP/PE bugs, hopefully will be fixed in QPR2 release
2 don't use Gcam for now, i've fixed hdr+ photos on recent Gcam version in my internal builds but it's still crashing causing a reboot after a minute, i had no time to inspect yet because i was focused on EAS and power HAL port
3 correct, no OTA update app on unofficial builds
4 i'm not 100% sure but if i remember well it's a feature of plus version

@-+BB+-
Thanks for sharing your Mi5 rom with us.
Since Android 12 the Mi5 phone is missing a working TWRP recovery, with support of the fbe encryption. This prevents many users from trying all the new roms, because there is no way to take full backups.
Can you tell me what is the reason?
I would be glad to help the development, but I don't know where to start. If I had someone who can guide me in the process I could do my part. Being part of a team would be ideal.

JackSlaterIV said:
@-+BB+-
Thanks for sharing your Mi5 rom with us.
Since Android 12 the Mi5 phone is missing a working TWRP recovery, with support of the fbe encryption. This prevents many users from trying all the new roms, because there is no way to take full backups.
Can you tell me what is the reason?
I would be glad to help the development, but I don't know where to start. If I had someone who can guide me in the process I could do my part. Being part of a team would be ideal.
Click to expand...
Click to collapse
Unfortunately Pixel Experience doesn't support natively TWRP compiling, and i don't have space on my NVME for another build enviroment. Also as far as i know they did not release yet an Android 13 recovery, they are working right now on it, but i don't know if works. Do you know if TWRP supports FBE on other devices? if TWRP supports FBE then best thing would be compile TWRP in an Android 12 build enviroment with a 4.4 kernel with FBE support. you can use my repos or los repos, it' the same. The only requested changes are a makefile with a basic conf for mi5 and convert the fstab in a compatible version for TWRP
@mrinfinity0007 not fixed yet but probably i've understood what's happening... Could you please try to put selinux in permissive mode and use the camera? You can do with adb:
Code:
adb root
adb shell setenforce 0
adb shell getenforce
The last command checks that selinux is correctly disabled, the output must be 0 or permissive

@-+BB+-
Thank you. Yes, from what I see TWRP supports FBE and A12 on other devices.
But I guess that porting it on our device is not that easy as one could think.
My problem is finding detailed guides to start understanding the process, or at least having a overall view.
Anyway I don't want to post too many OT messages on your thread.

-+BB+- said:
That's why I wrote could, I haven't tried and there are multiple versions of TWRP, if you experience problems flashing the ROM use my recovery
Click to expand...
Click to collapse
Let me try another TWRP version

-+BB+- said:
@mrinfinity0007 not fixed yet but probably i've understood what's happening... Could you please try to put selinux in permissive mode and use the camera? You can do with adb:
Code:
adb root
adb shell setenforce 0
adb shell getenforce
The last command checks that selinux is correctly disabled, the output must be 0 or permissive
Click to expand...
Click to collapse
i don't root my phone? does it work without it?

JackSlaterIV said:
@-+BB+-
Thank you. Yes, from what I see TWRP supports FBE and A12 on other devices.
But I guess that porting it on our device is not that easy as one could think.
My problem is finding detailed guides to start understanding the process, or at least having a overall view.
Anyway I don't want to post too many OT messages on your thread.
Click to expand...
Click to collapse
I will take a look this weekend and let you know because I don't remember where but I'm pretty sure that I read a tutorial for TWRP compiling some years ago
暗夜很无语 said:
Let me try another TWRP version
Click to expand...
Click to collapse
If your goal is to flash the ROM without format the internal memory won't work, you may be able to flash the zip but after the flash you'll be forced to format the internal memory without fbe support
mrinfinity0007 said:
i don't root my phone? does it work without it?
Click to expand...
Click to collapse
Yes it's a root shell, you have root permissions only with ADB, not in your phone. If you want to roll back to selinux enforcing and stop the rooted shell simply reboot the phone, that changes doesn't survive after the reboot

@JackSlaterIV found it, it's old and some things may be slightly different but this is a good tutorial.
Here's the link of the minimal manifest 12.1 is the correct branch but decryption is WIP at the moment, don' t think will work, unless you don't set a password/PIN/pattern, in that way should be fine
@mrinfinity0007 never mind, i've fixed It, Gcam was crashing because it was trying to use hexagon for HDR+, but SELinux was blocking it. Now it's wotking fine even in enforcing mode
PS: i've decided to upload the latest personal build i made, some thing may change because i'm still testing them, but more or less (on device side) this will be the next official release when PE devs will merge QPR2 changes and feb security patch.
Here's the direct link
And here's the changelog:
ROM:
- Synced code with latest PE changes
Kernel
- Ported EAS and set it as default scheduler
- Ported Stune Boost and use it as default
- Fixed almost all compiling warns
- Ported misc optimisations from infinity kernel
- Fixed a bug that could cause the boot to fail (Mi logo --> Black screen --> Mi logo again)
- Misc fixes from upstream
Recovery
- Fixed a bug that could cause the boot to fail (Mi logo --> Black screen --> Mi logo again)
Device Tree
- Ported EAS
- Move to EAS compatible power HAL
- QCOM audio HAL: add missing audio power hints support
- Fixed Google Camera crash when trying to use Hexagon
- Camera: move to Gcam Version MGC_8.1.101_A9_GV2b_ENG big thanks to BSG. Camera can be updated with all APKs released by BSG, just be sure to download the ENG version
- SELinux: fixed all denials
- Ported various improvements from my old 12.1 ROM
- Tuned ZRAM size for 3Gb devices
- Camera: improved camera HAL + misc fixes
- Configure SQLite to operate in MEMORY mode
- Set CFQ as default scheduler
- Added pixel animated wallpapers to build
For more detailed changes take a look at my repos
PS: i cannot test GPAY at the moment because i'm testing other things and i'm running in permissive mode, if someone decide to try the update and use GPAY please let me know if works, i made some changes to sepolicy and i want to be 100% sure that Google pay isn't broken before the official release.

[TESTING] TrebleDroid - Android 13 for SM-A730F/DS

{
"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"
}
A couple of days ago my mom gave me this phone. So, i want a new Android (and kick the s**t out all the bloatware of Samsung). After several tries, i make TrebleDroid vanilla works. And really good! Hell, even shows dual sims!
...And since there's no trace of someone doing this (or a guide), here are the steps. It was trial and error but i did it and it worked. (Sorry for english, i'm a native spanish speaker):
On original firmware:
- Activate OEM unlock in Developer Options
- Enable USB debugging
This is the version I used for Android 13 (at the moment, system-td-arm64-ab-vndklite-vanilla.img.xz from ci-20230510)
Releases · TrebleDroid/treble_experimentations
Scripts to automatically build/CI/Release TrebleDroid GSI - TrebleDroid/treble_experimentations
github.com
Vendor-Quack is required for SaR.
[SAR][Vendor][10][A530F/A530W/A730F] Vendor Quack V2.5 For Galaxy A8/A8+ 2018
Dude did you tried to enable magisk hide from settings? That should pass safety net on all Android 10+ roms :) Hey, i'm succesfully flashed magisk 21.1 beta version with safety net passed on Android R
forum.xda-developers.com
Vendor-Quack_V2.6
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
To load TWRP and change the system to Treble-compatible, instructions here. Download TWRP-jackpot2lte-Treble.img and TrebleCreator-A730F.zip
[GUIDE][TREBLE][A730F] Project Treble Guide for Galaxy A8+ 2018 (18/04/2019)
Project Treble Guide for Samsung Galaxy A8+ Just to make it clear I'm not responsible for whatever damage this could possibly cause to your device. Treble is everywhere, so why shouldn't we join it? I'm proud to announce that Galaxy A8+...
forum.xda-developers.com
ONCE TWRP IS LOADED, THE PHONE SHOULD NOT BE RESTARTED OR IT WILL BE OEM LOCK AND YOU WILL HAVE TO INSTALL THE ORIGINAL FW AND DO THE TRICK TO ELIMINATE THE KG-RMM STATUS:
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
download patch:
https://forum.xda-developers.com/attachments/rmm_bypass_v3_corsicanu-zip.4778435/
YOU MUST LOAD THE PATCH.
In my case to not wait 7 days:
RMM a730f
I commented my experience on my a730f with bit 4, 1.- After flash rom, select a manual date 10 days before the current date. 2.- remove the automatic update option, and select manual download, then restart. 3.- Verify that the phone shows the...
forum.xda-developers.com
1.- After flashing OEM rom, select a manual date 10 days before the current date of the phone.
2.- remove the automatic update option, and select manual download, then restart. Check that developer options is disable.
3.- enter google and samsung account on the phone.
4.- wait 3 hours (in my case, less. 1 hour), enable developer options and there will be the OEM unlock enabled.
With ODIN load TWRP-jackpot2lte-Treble.img (it's version 3.2.3 - 3.3.0 didn't give me good results)
All of the following steps refer to TWRP:
- After installing TWRP without entering the rom, /data must be formatted. After that, reboot into recovery mode using the reboot menu. If /data is not formatted, the partitions will remain encrypted and the rest cannot be wiped.
-------------------------------------------------- -----------------------
From now on, every time you make a change, you must reboot, because without this step, loading anything via TWRP will fail (if you didn't reboot, the rom will not start or froze, or the zip will not load correctly, or you'll see partition access errors on the log). ALL STEPS MUST BE FOLLOWED OR THE SYSTEM WILL REMAIN ON THE ANDROID LOADING SCREEN FOREVER.
-------------------------------------------------- -----------------------
- After reboot, Wipe in /cache,/vendor (if it exists. Otherwise it will be created later),/system,/data,/dalvik. Reboot into recovery mode using the reboot menu.
- Load TrebleCreator-A730F.zip. It will create the partitions for treble. It has an automatic reboot. After the reboot it should show the script and then reboot again and go back to TWRP. If the automatic reboot does not happen and the script screen doesn't show up, you will have to start again from the /data format step. It is vital since the automatic reboot and script screen indicates that the partitions were all correctly loaded.
- Load RMM_Bypass_v3_corsicanu.zip. This is to bypass the OEM lock. It should be done before Vendor-Quack, as the vendor zip encrypts the /vendor partition and makes it inaccessible. Reboot into recovery mode using the reboot menu.
- Load Vendor-Quack_V2.6.zip. Reboot into recovery mode using the reboot menu.
- Finally, the .img of Android 13. One last reboot to recovery and THEN reboot to system.
After this the rom should start without problems. TWRP builds with treble are now LOCKED once booted. When trying to enter recovery, they get frozen at the TWRP boot screen. In order to load gapps, you must load the "latest" version of TWRP (in quotes because TWRP version 3.7.0 does not load since it is larger than the /boot partition. In this case, you must load 3.6.2 ) using Odin and Download mode.
Download TWRP for jackpot2lte
Download TWRP Open Recovery for jackpot2lte
dl.twrp.me
Once the latest version of TWRP is loaded, the zips can be loaded without problems. IN THIS VERSION OF TWRP IT IS SUGGESTED NOT TO MAKE ANY CHANGES. ZIP INSTALLATION ONLY. Surely something will ruin this version of twrp if something is done with it since it does not show the /vendor partition.
Gapps that works: NikGapps. That's it
Go! Get crazy and share the results!
THINGS THAT DONT WORK SO FAR:
- Lantern (with the system doesn't work. If u use flash on camera, WORKS)
- Brightness is very picky. (on settings you'll find "Phh Treble Settings". There are some extra functions disabled -- by default? -- go check and see whats best for u. BUT! Careful, Icarus. Don't mess with stuff u dont know.)
- i don't have a SIM at the moment, so i can't tell if phone works.
- Root? Don't need it. Don't know if it's working.
THANKS TO:
@phhusson for TrebleDroid and Exynos updates, and aaaall his long work!
@prashantp01 for Vendor_Quack, Treble, and the patched TWRPs for this phone.
@corsicanu and all the people behind the KG bypass patch.
@juankp9086 for the guide to reset KG status.
aaand finally the team behind TWRP.

Is this a GSI? If not, you MUST provide the source you used for your kernel, as required by the GPL Policy.
Further, did you base this on someone else's work? You MUST give credit where due, per the Forum Rules.

V0latyle said:
Is this a GSI? If not, you MUST provide the source you used for your kernel, as required by the GPL Policy.
Click to expand...
Click to collapse
Yes. It's a GSI from @phhusson. All vanilla, no modification whatsoever. Kernel is included on Vendor_Quack, a SaR posted here too, from @prashantp01 . All is based on guides and files from this same forum (and all files and sources are linked here), except the steps.
V0latyle said:
Further, did you base this on someone else's work? You MUST give credit where due, per the Forum Rules.
Click to expand...
Click to collapse
No problem. I'll quote everyone involved for making this Done
As for the steps, as i said, it was trial and error. There was no guides or something that i know of (FOR ANDROID 13). I just take a leap of faith based on last good know version working (Android 11) and use that, since Android 12 was no good in some details.

BernoO said:
Yes. It's a GSI from @phhusson. All vanilla, no modification whatsoever. Kernel is included on Vendor_Quack, a SaR posted here too, from @prashantp01 . All is based on guides and files from this same forum (and all files and sources are linked here), except the steps.
Click to expand...
Click to collapse
A GSI does not include a kernel, but since you linked to an established project that already has a published source, everything is good.
Thank you for adding credits.
I don't know if you saw this, but the Magisk installation instructions include details on how to defeat KG/Vaultkeeper.

Did Android 13 worked for you , and did you try setting lock as that seems to cause a bootloop .
If it worked can you tell me how you did it as my phone's seems to bootloop after trying to set a lock (pin,etc) on Android 12 and 13 and I have already tried PixelExperience and LineageOs .

NVM wrong topic

AlphaMaster08 said:
Did Android 13 worked for you , and did you try setting lock as that seems to cause a bootloop .
If it worked can you tell me how you did it as my phone's seems to bootloop after trying to set a lock (pin,etc) on Android 12 and 13 and I have already tried PixelExperience and LineageOs .
Click to expand...
Click to collapse
Can confirm. Since i was just testing, didnt need to lock it. After trying to set a pattern or pin lock (and systemUI crashes), ive reboot and then a soft bootloop (for 3 seconds i can see lock screen, then android boot screen, 3 sec lock screen and so...).
After another reboot, bootloop.
I dont have this issue since lock screen was just sliding.
Another issue: bluetooth is working, but when wireless speakers are on sync, no sound whatsoever. A common fault on several android 13 installations as i can tell.
Remember that @phhusson is adding exynos updates on TrebleDroid, so we should expect (or beg, cant tell ) that more fixes are on the way?

And BTW if Someone needs it the best Roms/GSI for A8+ are TreeUi(S20 Port) , PixelExperience (11) and FusionX(10,maybe) and Don't try Android 12 /13Gsi as they don't work currently.

AlphaMaster08 said:
And BTW if Someone needs it the best Roms/GSI for A8+ are TreeUi(S20 Port) , PixelExperience (11) and FusionX(10,maybe) and Don't try Android 12 /13Gsi as they don't work currently.
Click to expand...
Click to collapse
Thanks!
This guide most of all was because a couple of users were asking if there's a way to run Android 13 on their A8s. So there's an answer for that now. Almost.