Database Info

[Recovery] Official TWRP for the Xiaomi Mi MIX (lithium)

Team Win Recovery Project 3.0.2-0
This is for the Xiaomi Mi MIX only, do not flash on other models!
WARNING: As of Android Marshmallow, factory boot images have dm-verity enabled, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
For official stock/dev firmware: http://teamw.in/devices/xiaomimimix.html
For (slightly newer) firmware: https://build.nethunter.com/test-builds/twrp/xiaomi/twrp-3.0.2-0-rc1-eu-lithium.img
For (the latest EU) firmware: https://build.nethunter.com/test-builds/twrp/xiaomi/twrp-3.0.2-0-rc2-eu-lithium.img
(touchscreen will not respond if not matching firmware)
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
You must first unlock your device. To do this, follow the instructions on the MIUI forums. (tedious, I know)
{
"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"
}
Extract adb & fastboot to your computer.
Download TWRP for Xiaomi Mi MIX (lithium).
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Power] buttons while your device reboots.
Once you're in fastboot mode, you're ready to flash TWRP. To do this, run these commands in order:
fastboot flash recovery twrp.img
fastboot boot twrp.img
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 - Official release on twrp.me
v3.0.2-0-rc1 - Initial release candidate and first XDA build
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
There's absolutely none that I know of. Rejoice. You even have working hardware encryption!
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (Official): https://github.com/TeamWin/android_device_xiaomi_lithium (android-6.0)
Device tree (Development): https://github.com/jcadduono/android_device_xiaomi_lithium (android-6.0)
Kernel: Unavailable (waiting on Xiaomi source release, using MIUI stock binary for now)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
Thank you to @wolfgart for requesting device support and reporting feedback on my initial builds.

Great Work
Now Xiaomi MI MIX is the greatest device we can have atm

@jcadduono @wolfgart Wolfgart request your help just because in Italy I've already published italian rom with my recoveryas you see from here
http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=999961
http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=1000010
But your official support is obviously better than mine. I follow you in a lot of thread so I know your great work:good::good: Very happy for this

development is starting , great work OP

agriculture said:
development is starting , great work OP
Click to expand...
Click to collapse
Best device now has best TWRP ever made before.
tnx @jcadduono

Looks like it won't be showing up on twrp.me until 3.0.3 or 3.1.0 depending on what's next. There's a few incompatibilities in the device tree and I'd prefer to wait it out till then. Ex. 3.0.2 doesn't support f2fs or ntfs on omnirom trees right now, but our current source does. If I made an official release neither would be supported.
Update: Official release made on newer TWRP build tree.

Wow, a thousand thanks.

I flashed the recovery, but the touch screen was not working, I can't do anything in the recovery, anyone know what's wrong?

mega00 said:
I flashed the recovery, but the touch screen was not working, I can't do anything in the recovery, anyone know what's wrong?
Click to expand...
Click to collapse
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
mega00 said:
Wow, a thousand thanks.
Click to expand...
Click to collapse
don't quote the entire thread opener.... edit your post and remove it, if you need to make adjustments use the edit button, don't make another post immediately after your own

jcadduono said:
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
I am on stock rom and using the stock rom version TWRP, the touch screen just don't work.
To be more clear, I am on dev rom 6.11.10 (MIUI8), do I have to change to stable rom V8.0.8.0.MAHCNDI (MIUI8) to make it work?
Update: Yes, I changed to stable rom and it works.
Click to expand...
Click to collapse

mega00 said:
jcadduono said:
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
I am on stock rom and using the stock rom version TWRP, the touch screen just don't work.
To be more clear, I am on dev rom 6.11.10 (MIUI8), do I have to change to stable rom V8.0.8.0.MAHCNDI (MIUI8) to make it work?
Click to expand...
Click to collapse
you have to flash CN Stable rom V8.0.8.0.MAHCNDI (MIUI8) and use original TWRP for it and if you want Cross-Flash your CN rom with International one Here too .
When you are on International rom up&running you can flash over the EU TWRP .
As explained from @jcadduono this is the only solution for the moment until XIAOMI release his Kernel stuff officially
Click to expand...
Click to collapse

Thanks to the devs for such fast development on this great phone ...
I personally coming from lg so xiaomi is completely new for me ...
I understand the usual steps unlocking bootloader..flashing twrp ...and finally root ....
I don't have the phone yet but when it comes is running the same stock rom for everybody if I'm not wrong?...
What is that with the different roms?...
And how do i know wich twrp have to install?
Thanks again and sorry for the #noob# guestions....
Sent from my LG-D855 using XDA Free mobile app

cultofluna said:
Thanks to the devs for such fast development on this great phone ...
I personally coming from lg so xiaomi is completely new for me ...
I understand the usual steps unlocking bootloader..flashing twrp ...and finally root ....
I don't have the phone yet but when it comes is running the same stock rom for everybody if I'm not wrong?...
What is that with the different roms?...
And how do i know wich twrp have to install?
Thanks again and sorry for the #noob# guestions....
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
cause Stock kernel still was not relased you have to simply flash EU Rom using stock TWRP and after you done you have to change to TWRP EU to make it working again .
We are waiting official sources from Xiaomi

just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?

knives of ice said:
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
Click to expand...
Click to collapse
I waited about 4 hours after submitting the application, 2 weeks is a maximum estimation.

knives of ice said:
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
Click to expand...
Click to collapse
you have to wait few minutes or at last 24 hours to receive sms unlock approve

:good::good:

wolfgart said:
you have to wait few minutes or at last 24 hours to receive sms unlock approve
Click to expand...
Click to collapse
I am facing the unlock stuck at 50% issue while trying to unlock the bootloader on this phone? any ideas? Thank you.

does anyone know if using TWRP manager will work to install TWRP after you have unlocked?

jim380 said:
I am facing the unlock stuck at 50% issue while trying to unlock the bootloader on this phone? any ideas? Thank you.
Click to expand...
Click to collapse
you have to Log On with your MIUI account on device too and the retry to unlock
---------- Post added at 07:43 AM ---------- Previous post was at 07:42 AM ----------
knives of ice said:
does anyone know if using TWRP manager will work to install TWRP after you have unlocked?
Click to expand...
Click to collapse
it works ! I can confirm. And it works using Flashify too

[RS988][RECOVERY][OFFICIAL] TWRP 3.3.1-0 for LG G5 RS988 [05/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"
}
Thank you @shunjou for helping RS988 to go official!
This is the official support thread for TWRP for RS988.
Installation from Stock:
**If your bootloader isn't already unlocked, go to the LG Developer website. You'll need to create an account. You can get the necessary ADB and fastboot tools from the Android SDK Platform Tools.**
If you wish to flash a stock ROM, you MUST flash a root .zip such as SuperSU to disable dm-verity and storage encryption! If you later decide to install a custom ROM, and didn't disable dm-verity on stock, you will have to COMPLETELY FORMAT your internal storage. Don't risk it.
1. Reboot into the bootloader with the command "adb reboot bootloader" and issue the command "fastboot flash recovery twrp-x.x.x-x_rs988.img", replacing "twrp.x.x.x..." with the location of the TWRP image on your drive.
2. Once it is done writing the image and says "finished," detach all power sources and remove the battery. This step is important—if you reboot into the system instead, TWRP will be overwritten by the stock recovery.
3. Reinsert the battery. Then start the phone, holding down both the Volume Down and Power button. When the LG logo appears, quickly release and re-press the Power button, continuing to hold Volume Down. This should bring you to a Factory Data Reset screen.
4. Confirm "Yes" on the two prompts (don't worry, no data will be deleted—we've overwritten the stock recovery) and you will be in TWRP.
Make sure to follow these steps as written, and make backups if necessary. You wouldn't want to risk saying "Yes" and actually wipe your data, right?
Click to expand...
Click to collapse
Working:
It works. If there are any problems, report them here.
Click to expand...
Click to collapse
Downloads:
Builds may be downloaded from the TWRP website.
Production builds: twrp.me/lg/lgg5rs988.html.
Test builds will depend on the current version of TWRP. For example, for v3.2.3.0 : http://build.twrp.me/twrp-3.2.3-0-rs988.img
Click to expand...
Click to collapse
XDA:DevDB Information
[OFFICIAL] TWRP 3.3.1-0 for LG G5 RS988, Tool/Utility for the LG G5
Contributors
NextDroid, shunjou
Source Code: https://github.com/TeamWin/android_device_lge_rs988
Version Information
Status: Stable
Created 2018-06-14
Last Updated 2019-06-11

Reserved?

Encryption not working for Linage 15.1

If you wish to flash a stock ROM, you MUST flash a root .zip such as SuperSU to disable dm-verity and storage encryption! If you later decide to install a custom ROM, and didn't disable dm-verity on stock, you will have to COMPLETELY FORMAT your internal storage. Don't risk it.
Click to expand...
Click to collapse
@NextDroid, Can you elaborate on this a little more? I'm not sure I fully understand.
Do you mean if you're on a stock ROM, you should root your device by flashing a root .zip file (magisk/supersu) to disable dm-verity and storage encryption before you install a custom ROM?
I just unlocked the bootloader and installed this version of TWRP on my RS988. I also installed x86cpu's unofficial 15.1 lineageOS ROM.
What I did was:
1. Unlock the bootloader
2. Installed TWRP
3. *Flashed SuperSU zip
4. Installed LineageOS/Gapps
*I think I may have flashed the wrong file for SuperSU because I tried flashing the same SuperSU .zip file after installing LineageOS and it didn't appear to do anything. Apps weren't giving me root access and there was no SuperSU app in my app drawer. I fear that my device wasn't actually rooted before installing LineageOS. Am I screwed? What do you mean that you will have to format your internal storage?
The SuperSU zip file I flashed was: UPDATE-SuperSU-v2.82-20170528234214
Sorry, I'm not the most educated in this kind of stuff. But everything as of now seems to be working fine. TWRP functions properly. I have since installed magisk and my device appears to be properly rooted. LineageOS 15.1 is working with no issues so far.

djskribbles said:
@NextDroid, Can you elaborate on this a little more? I'm not sure I fully understand.
Do you mean if you're on a stock ROM, you should root your device by flashing a root .zip file (magisk/supersu) to disable dm-verity and storage encryption before you install a custom ROM?
I just unlocked the bootloader and installed this version of TWRP on my RS988. I also installed x86cpu's unofficial 15.1 lineageOS ROM.
What I did was:
1. Unlock the bootloader
2. Installed TWRP
3. *Flashed SuperSU zip
4. Installed LineageOS/Gapps
*I think I may have flashed the wrong file for SuperSU because I tried flashing the same SuperSU .zip file after installing LineageOS and it didn't appear to do anything. Apps weren't giving me root access and there was no SuperSU app in my app drawer. I fear that my device wasn't actually rooted before installing LineageOS. Am I screwed? What do you mean that you will have to format your internal storage?
The SuperSU zip file I flashed was: UPDATE-SuperSU-v2.82-20170528234214
Sorry, I'm not the most educated in this kind of stuff. But everything as of now seems to be working fine. TWRP functions properly. I have since installed magisk and my device appears to be properly rooted. LineageOS 15.1 is working with no issues so far.
Click to expand...
Click to collapse
Hey @djskribbles,
As I prefaced them, these instructions only apply when you wish to flash a stock ROM. This implies that you are coming from a custom ROM. The current LG stock ROMs, when flashed, encrypt the internal storage, and TWRP is currently not able to decrypt it. This is why one should flash Magisk to disable storage encryption beforehand.
Also, you'll be better off if you use Magisk instead of SuperSU. Flash Magisk before LineageOS, because the script used to flash it automatically wipes the /system partition, which is where SuperSU, for example, makes its changes to enable root access.

NextDroid said:
As I prefaced them, these instructions only apply when you wish to flash a stock ROM. This implies that you are coming from a custom ROM. The current LG stock ROMs, when flashed, encrypt the internal storage, and TWRP is currently not able to decrypt it. This is why one should flash Magisk to disable storage encryption beforehand.
Click to expand...
Click to collapse
Actually, decryption should be working for stock now since the last builds. At least that's what was confirmed by someone that made me realize that building with omni 8 broke the old decryption fix. I think someone else mentioned cm14.1 worked too, so any nougat rom should be fine.
The issue now, as mentioned by x86cpu above, is that decryption isn't working with oreo roms. This seems common for a large number of devices (eg 1, 2, 3). It looks like codeworkx's fix for the zl1 here might resolve it, though I haven't tried it since I'm not currently able to test decryption myself.

shunjou said:
Actually, decryption should be working for stock now since the last builds. At least that's what was confirmed by someone that made me realize that building with omni 8 broke the old decryption fix. I think someone else mentioned cm14.1 worked too, so any nougat rom should be fine.
The issue now, as mentioned by x86cpu above, is that decryption isn't working with oreo roms. This seems common for a large number of devices (eg 1, 2, 3). It looks like codeworkx's fix for the zl1 here might resolve it, though I haven't tried it since I'm not currently able to test decryption myself.
Click to expand...
Click to collapse
All right, that's great to hear! I'll admit, I wasn't sure when I made that second comment... it had been a while since I'd heard anything on stock encryption.
I actually just finished cooking up a fix for Oreo encryption from work on the G6... I'll head over to zl1 if it doesn't work out.
We'll see what happens... --fingers crossed--

On the website the only TWRP version is 3.2.1-0. Is this different from the unofficial version I'm currently running? Has the wrong battery percentage bug been rectified?

Awkydee said:
On the website the only TWRP version is 3.2.1-0. Is this different from the unofficial version I'm currently running? Has the wrong battery percentage bug been rectified?
Click to expand...
Click to collapse
The latest unofficial build is the same as the official in terms of functionality. The battery life percentage should now display accurately.

NextDroid said:
The latest unofficial build is the same as the official in terms of functionality. The battery life percentage should now display accurately.
Click to expand...
Click to collapse
Yippie! Flashing now!

can i lock back the bootloader later to install oficial oreo when it comes?
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev

bmanuelangel said:
can i lock back the bootloader later to install oficial oreo when it comes?
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Click to expand...
Click to collapse
Are you referring to stock? Hopefully you won't need to re-lock the bootloader. When a .kdz package is published, hopefully @Unscedeo will make one of his COMPLETE INSTALLERS for it, and you could just flash it.

Hmm, I ought to keep up with this thread a bit more...
I've made some updates today and created a test build. Here is the link for anyone who wishes to test: http://build.twrp.me/twrp-3.2.3-0-rs988.img

Hello NextDroid, I noticed that the 3.3.1-0 version TWRP has been released.
According the the release's changes information provided by the TWRP website for the release:
https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html said:
* Fix selinux issues during formatting - dianlujitao
...
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Click to expand...
Click to collapse
I have noticed that while using x86cpu's UNOFFICIAL LineageOS-15.1 for G5 (lineage-15.1-20190516-X86CPU-rs988.zip) build, the SELinux status is usually "Enforcing", by sometimes changes to "Permissive". Do you think that the change would be due to the formatting bug corrected by this new TWRP build? If so, can a fix be applied after the buggy formatting from a previous TWRP release has happened and in such a way as to not have to reinstall the operating system? Are TWRP backups done raw, file-based, or differently?

Ascii3 said:
Hello NextDroid, I noticed that the 3.3.1-0 version TWRP has been released.
According the the release's changes information provided by the TWRP website for the release:
I have noticed that while using x86cpu's UNOFFICIAL LineageOS-15.1 for G5 (lineage-15.1-20190516-X86CPU-rs988.zip) build, the SELinux status is usually "Enforcing", by sometimes changes to "Permissive". Do you think that the change would be due to the formatting bug corrected by this new TWRP build? If so, can a fix be applied after the buggy formatting from a previous TWRP release has happened and in such a way as to not have to reinstall the operating system? Are TWRP backups done raw, file-based, or differently?
Click to expand...
Click to collapse
That is a good question. Actually, I am not sure. If you are willing to research that, report your findings to us here I'm interested to know.
I have been very busy for the past couple of months, but the G5 hasn't left my mind... I use it every day I'll see when I can update TWRP and my other builds.
Thanks for keeping us updated, @Ascii3!

NextDroid said:
That is a good question. Actually, I am not sure. If you are willing to research that, report your findings to us here I'm interested to know.
Click to expand...
Click to collapse
Maybe, if I have some time, myself. It is looking like something for August 2019.
NextDroid said:
I have been very busy for the past couple of months...I'll see when I can update TWRP and my other builds.
Click to expand...
Click to collapse
I am glad to see that you your are still around.
NextDroid said:
Thanks for keeping us updated, @Ascii3!
Click to expand...
Click to collapse
Sure.

Ascii3 said:
Are TWRP backups done raw, file-based, or differently?
Click to expand...
Click to collapse
I can and shall answer this question that I posed before:
TWRP allows for both RAW and file-based backups. Usually, however, the GUI provides few items for RAW backup; there is typically a backup option for "System Image" which is a RAW backup.
@NextDroid - I noticed that more recent versions of your TWRP do not have the System Image backup option despite it being in your older TWRP 3.2.3-0 build. The System Image backup functionality from TWRP 3.2.3-0 seemed to work OK. Did you deliberately exclude the "System Image" backup option? I the option missing for good reason?

Development is still alive for honor 6x

the development for honor 6x and oreo gsi roms is stopped but only phusson is keep developing oreo gsi rom aosp 8.1 v31. last update was may 3 2019. he did a great job our device. os is complete pure stock,battery backup is amazing and he fixed battery charging speed now device will charge at the speed of stock.
there is two types of firmwares available one is with gapps and root other is without gapps and no root.
first i have tried with gapps version there is no bugs. the only bug is headphones without mic is not detecting. lesser audio switch apk solved that problem.
then i have flased the one without gapps. which is amazing. phone works at its peaks performance, charges faster and drains slower. fingerprint navigation is also improved like if we swipe down it shows notification pannel if we do swipe down again it will expand notification pannel and phone complete navigation can be controlled.
i have flashed cyclox kernel and did over clock for pubg. now pubg runs with smoothes equalls to iphone. i have never got pubg this much smooth, easily wiped out a squad with 7 kills.
without gapps version themed like kitkat and it performance like we are using kitkat on our device.
RAM management is also excellent. it can keep more apps in the memory without killing them.
if we want our device to keep receive google security updates with stable os this is best option.
Download link: https://github.com/phhusson/treble_experimentations/releases/tag/v31
click on assets to get download links.

Can't unlock bootloader
Hi.. My bootloader is locked and honor has closed their official bootloader unlocking service. So what should I do to unlock bootloader unofficially..?

[email protected] said:
Hi.. My bootloader is locked and honor has closed their official bootloader unlocking service. So what should I do to unlock bootloader unofficially..?
Click to expand...
Click to collapse
you need buy dc unlocker to unlock bootloader.
i don't any unofficially ways except this one.
https://forum.xda-developers.com/honor-6x/how-to/guide-unbrick-honor6x-boot-fastboot-t3904381
but this is very risky. i think in this guide we flash stock rom via dload so you bootloader will lock again.
before flashing stock rom this board software install emui 2.0 on honor 6x. with unlocked frp and bootloader. at this point if we managed to get twrp then we can install emui 5 or emui 8 via huru. huru doesn't lock bootloader so we can flash gsi roms. but the problem is we don't have twrp designed for emui 2.0

Ramesh006 said:
you need buy dc unlocker to unlock bootloader.
i don't any unofficially ways except this one.
https://forum.xda-developers.com/honor-6x/how-to/guide-unbrick-honor6x-boot-fastboot-t3904381
but this is very risky. i think in this guide we flash stock rom via dload so you bootloader will lock again.
before flashing stock rom this board software install emui 2.0 on honor 6x. with unlocked frp and bootloader. at this point if we managed to get twrp then we can install emui 5 or emui 8 via huru. huru doesn't lock bootloader so we can flash gsi roms. but the problem is we don't have twrp designed for emui 2.0
Click to expand...
Click to collapse
Thanks for this. Some people say that DC unlocker is Risky. I also had mailed honor about this. Here's what they replied. So should i do it or not..
{
"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"
}

[email protected] said:
Thanks for this. Some people say that DC unlocker is Risky. I also had mailed honor about this. Here's what they replied. So should i do it or not..
Click to expand...
Click to collapse
Give it a try. if you are lucky you will get bootloader unlock for free.
Dc unlocker is safe. i have used it two times to unbrick my device. without any knowledge about dc unlocker I have managed to repair my device within 1 hour. we need buy hcu client for honor devices.

Ramesh006 said:
the development for honor 6x and oreo gsi roms is stopped but only phusson is keep developing oreo gsi rom aosp 8.1 v31. last update was may 3 2019. he did a great job our device. os is complete pure stock,battery backup is amazing and he fixed battery charging speed now device will charge at the speed of stock.
there is two types of firmwares available one is with gapps and root other is without gapps and no root.
first i have tried with gapps version there is no bugs. the only bug is headphones without mic is not detecting. lesser audio switch apk solved that problem.
then i have flased the one without gapps. which is amazing. phone works at its peaks performance, charges faster and drains slower. fingerprint navigation is also improved like if we swipe down it shows notification pannel if we do swipe down again it will expand notification pannel and phone complete navigation can be controlled.
i have flashed cyclox kernel and did over clock for pubg. now pubg runs with smoothes equalls to iphone. i have never got pubg this much smooth, easily wiped out a squad with 7 kills.
without gapps version themed like kitkat and it performance like we are using kitkat on our device.
RAM management is also excellent. it can keep more apps in the memory without killing them.
if we want our device to keep receive google security updates with stable os this is best option.
Download link: https://github.com/phhusson/treble_experimentations/releases/tag/v31
click on assets to get download links.
Click to expand...
Click to collapse
Hi Ramesh006,
thanks for this info. Very excited!
I've some (no, a lot ) questions before try it:
- The correct image for the Honor 6X is this one: system-arm64-aonly-gapps-su.img.xz?
- The root type is Magisk o SuperSU?
- Have you flashed the rom by fastboot or recovery? And in that case, what recovery, Twrp V2 from Elemental thread? Sadly this recovery can't see encrypted partitions :/
- Do I have back to OREO stock or can I flash from another GSI rom?
Thanks again for information sharing!
cheers!

spiritwashere said:
Hi Ramesh006,
thanks for this info. Very excited!
I've some (no, a lot ) questions before try it:
- The correct image for the Honor 6X is this one: system-arm64-aonly-gapps-su.img.xz?
- The root type is Magisk o SuperSU?
- Have you flashed the rom by fastboot or recovery? And in that case, what recovery, Twrp V2 from Elemental thread? Sadly this recovery can't see encrypted partitions :/
- Do I have back to OREO stock or can I flash from another GSI rom?
Thanks again for information sharing!
cheers!
Click to expand...
Click to collapse
Yes arm 64 a only. you can use with gapps or without gapps.
Root is magisk.
i have flashed it via fastboot.
you can flash from other gsi rom but you need to do factory reset via stock recovery after flashing.
after factory reset i have flashed elemental v2 twrp recovery.
im using arm 64 a only without gapps and su so i have flased magisk 19.1 via twrp and it was working.
then i have flashed p20pro hauwei stock camera via twrp and it was working.
Link for camera
https://forum.xda-developers.com/hu...uawei-p20-pro-camera-app-treble-roms-t3798767
then i have flashed james dsp via magisk which is almost looks like viper4android and working.
substratum theme engine works superb we can add or remove any theme without any problems.
titanium backup is not working so we can use oandbackup. which free and work as same as titanium backup.
standby time is great overnight drain is only 1%
finally every month we receive new security updates.

Ramesh006 said:
Yes arm 64 a only. you can use with gapps or without gapps.
Root is magisk.
i have flashed it via fastboot.
you can flash from other gsi rom but you need to do factory reset via stock recovery after flashing.
after factory reset i have flashed elemental v2 twrp recovery.
im using arm 64 a only without gapps and su so i have flased magisk 19.1 via twrp and it was working.
then i have flashed p20pro hauwei stock camera via twrp and it was working.
Link for camera
https://forum.xda-developers.com/hu...uawei-p20-pro-camera-app-treble-roms-t3798767
then i have flashed james dsp via magisk which is almost looks like viper4android and working.
substratum theme engine works superb we can add or remove any theme without any problems.
titanium backup is not working so we can use oandbackup. which free and work as same as titanium backup.
standby time is great overnight drain is only 1%
finally every month we receive new security updates.
Click to expand...
Click to collapse
Sounds good!
Do I have to flash stock recovery before flashing gsi or flashing the system image do the job?
Tomorrow, time permitting, I will try to flash this great work!
Thanks again for info.

spiritwashere said:
Sounds good!
Do I have to flash stock recovery before flashing gsi or flashing the system image do the job?
Tomorrow, time permitting, I will try to flash this great work!
Thanks again for info.
Click to expand...
Click to collapse
you have to manually flash stock recovery. you can flash it anytime before or after flashing os. system don't flash stock recovery.

Ramesh006 said:
you have to manually flash stock recovery. you can flash it anytime before or after flashing os. system don't flash stock recovery.
Click to expand...
Click to collapse
Thanks!

Hello,
My 6x (BLN AL20) has unlocked bootloader and Is actually running PixysOs which is discontinued and actually has no BT working (switching loc. services off won't help in connecting my smartwatch).
Is BT working with this Rom?
Any tutorial on how to proceed for flashing this rom starting from an unlocked device with PyxyOs and Askuccio's TWRP?
Thanks in advance.
Andrea.

Sephiroth79 said:
Hello,
My 6x (BLN AL20) has unlocked bootloader and Is actually running PixysOs which is discontinued and actually has no BT working (switching loc. services off won't help in connecting my smartwatch).
Is BT working with this Rom?
Any tutorial on how to proceed for flashing this rom starting from an unlocked device with PyxyOs and Askuccio's TWRP?
Thanks in advance.
Andrea.
Click to expand...
Click to collapse
Bluetooth is working fine for me. im using ducasso zest Bluetooth speaker. i didn't know about smart watch connection.
installation is simple. flash stock recovery via twrp or fastboot then flash system.img via fastboot then do factory reset via stock recovery. after that you can use either elemental twrp or askuccio twrp to flash magisk,camera etc.

Ahem. any hope to have a more detailed (step by step) tutorial?
Thanks.

wierd issue
Ramesh006 said:
the development for honor 6x and oreo gsi roms is stopped but only phusson is keep developing oreo gsi rom aosp 8.1 v31. last update was may 3 2019. he did a great job our device. os is complete pure stock,battery backup is amazing and he fixed battery charging speed now device will charge at the speed of stock.
there is two types of firmwares available one is with gapps and root other is without gapps and no root.
first i have tried with gapps version there is no bugs. the only bug is headphones without mic is not detecting. lesser audio switch apk solved that problem.
then i have flased the one without gapps. which is amazing. phone works at its peaks performance, charges faster and drains slower. fingerprint navigation is also improved like if we swipe down it shows notification pannel if we do swipe down again it will expand notification pannel and phone complete navigation can be controlled.
i have flashed cyclox kernel and did over clock for pubg. now pubg runs with smoothes equalls to iphone. i have never got pubg this much smooth, easily wiped out a squad with 7 kills.
without gapps version themed like kitkat and it performance like we are using kitkat on our device.
RAM management is also excellent. it can keep more apps in the memory without killing them.
if we want our device to keep receive google security updates with stable os this is best option.
Download link: https://github.com/phhusson/treble_experimentations/releases/tag/v31
click on assets to get download links.
Click to expand...
Click to collapse
wierd issue, after installing the rom is randomly presing home, im using the one with root and gapps
edit: and now im getting encrypt erros saying im need to wipe but i do that and keep telling me the same
edit2: well i feel kind of stupid XD the random things was a gesture on the print sensor but still dont know why only the gapps and rooted works on my phone, and how did you make the james dsp work mine stop working every time

Link for stock recovery?

Stuck in reboot loop....uff

Ramesh006 said:
Bluetooth is working fine for me. im using ducasso zest Bluetooth speaker. i didn't know about smart watch connection.
installation is simple. flash stock recovery via twrp or fastboot then flash system.img via fastboot then do factory reset via stock recovery. after that you can use either elemental twrp or askuccio twrp to flash magisk,camera etc.
Click to expand...
Click to collapse
I was hoping to get some steps for overclocking the device.
1. Which rom version (gapps/non-gapps) u used?
2. What version of CycloX kernel did u use?
3. What are the settings you're using in the kernel?

Is VoLTE working in them?

mohit.cr.07 said:
Is VoLTE working in them?
Click to expand...
Click to collapse
VoLTE wont work on any lineage or gsi rom

goldenevil47 said:
I was hoping to get some steps for overclocking the device.
1. Which rom version (gapps/non-gapps) u used?
2. What version of CycloX kernel did u use?
3. What are the settings you're using in the kernel?
Click to expand...
Click to collapse
v31 without gapps
kernel version 05. 001 stock 039
just go to 27 page on cyclox kernel and copy the overclock command then give su rights on terminal emulator or termix then paste the commnad and press enter. to check if kernel activated go to root folder honor cfg kernel check overclock is 1. if you reboot your device you need to do it again.

[ROM][10][UNOFFICIAL] lineage-17.1 for Pixel 4a (sunfish)

{
"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, which is designed to increase performance and reliability over stock android for your device. This is a straightforward port of the device tree for flame (Pixel 4) to sunfish (Pixel 4a).
Downloads:
sunfish (Pixel 4a) rom (v2): https://mega.nz/file/zG4UVTQB#ZXLw_qULzC8-an-MEdxdAvUMhmIa5qLI6YG54Feh2z0
410b3f523795d9d1481d183309adb170 lineage_sunfish-qd3a.200805.001-rel-v2.zip
sunfish (Pixel 4a) rom (v1, broken, do not install): https://mega.nz/file/jXRB2a4B#a5Dcf9T6emWAwvAj3oFvofkI0la0zf7vj5KIMn-yQaM
MD5: 86743134c3032a030d35195d44f02e1b lineage_sunfish-qq3a.200805.001.zip
This is not a recovery-installable zip! Please read below for how to install this image
Prerequisites:
Like the TWRP build for this device, this ROM build is only known to be compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.
Instructions:
1. Flash the vbmeta.img file in the included zip (fastboot flash vbmeta vbmeta.img)
2. Reboot into fastbootd (fastboot reboot fastboot)
3. Run fastboot update -w lineage_sunfish-qd3a.200805.001-v2.zip
(If you do not have a working fastbootd, extract boot.img from the update zip and flash it from the bootloader first)
Working:
- Camera
- Fingerprint
- Wi-Fi
- Bluetooth
- Sound
- Mobile data (tested with T-Mobile only)
Not tested:
- Google apps (should work fine, but you never know)
Changelog/Source Code:
sunfish device tree: https://github.com/liamwhite/android_device_google_sunfish
sunfish kernel tree: https://github.com/liamwhite/android_kernel_google_sunfish
Credits:
Many thanks to all LineageOS team members and all the contributors out there in the community.
Android version: 10
Kernel version: 4.14.117

Sorry if this a dumb question but couldn't we use the same boot image used in derpfest and superior os to sideload the rom?
just asking because that's how I flashed a lineage test build.

thank you sir my devices 4a .. build number RP1A200720.010 this rom dont work....

Edmontonchef said:
Sorry if this a dumb question but couldn't we use the same boot image used in derpfest and superior os to sideload the rom?
just asking because that's how I flashed a lineage test build.
Click to expand...
Click to collapse
posıtıve said:
thank you sir my devices 4a .. build number RP1A200720.010 this rom dont work....
Click to expand...
Click to collapse
Like the TWRP build for this device, this ROM build is only compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.
The Derpfest build uses the newer firmware and I don't think it would be compatible. You could certainly try, though.

liamwhite said:
Like the TWRP build for this device, this ROM build is only compatible with older firmware. I only tested QD4A.200805.003, but .001 would likely work as well. If you have a newer version, you will need to downgrade at least the bootloader and radio first. I recommend installing the QD4A.200805.003 firmware image from Google, as that's what I tested with.
The Derpfest build uses the newer firmware and I don't think it would be compatible. You could certainly try, though.
Click to expand...
Click to collapse
I'm no expert but my guess is that it won't work because the sideloaded versions, Dirty Unicorns, Derpfest, and Superior have the boot.img inside a payload.bin file so that recovery wouldn't recognize this. But then again, what do I know?

TheSayaMan said:
I'm no expert but my guess is that it won't work because the sideloaded versions, Dirty Unicorns, Derpfest, and Superior have the boot.img inside a payload.bin file so that recovery wouldn't recognize this. But then again, what do I know?
Click to expand...
Click to collapse

I can't install this. I keep getting a error that the device is corrupt and can't be trusted and may not work properly. Does not boot. Followed instruction to a T. Flashed to another rom. Also confirmed that flashing through du or twrp recovery does not work as I stated previously.

TheSayaMan said:
I can't install this. I keep getting a error that the device is corrupt and can't be trusted and may not work properly. Does not boot. Followed instruction to a T. Flashed to another rom. Also confirmed that flashing through du or twrp recovery does not work as I stated previously.
Click to expand...
Click to collapse
If this is what you're seeing, it typically means either the bootloader wasn't unlocked or verity was still enforcing. I am not sure how this could have broken considering I didn't take any special steps besides unlocking my bootloader before flashing the update image, and I even reflashed the phone to factory first before applying it and it still worked.
I added a MD5 of the zip image I flashed to the OP.

liamwhite said:
If this is what you're seeing, it typically means either the bootloader wasn't unlocked or verity was still enforcing. I am not sure how this could have broken considering I didn't take any special steps besides unlocking my bootloader before flashing the update image, and I even reflashed the phone to factory first before applying it and it still worked.
I added a MD5 of the zip image I flashed to the OP.
Click to expand...
Click to collapse
I'm sure it's not broken. Probably a issue with my phone. I'm getting a error in the bootloader about debug policy enabled, not in list. I know that's not normal because my wife has the same phone and hers doesn't say that. And I have no idea what or how to change verity. My bootloader is unlocked.

Same error here, getting corrupt error then it sticks to google logo

nixromancer said:
Same error here, getting corrupt error then it sticks to google logo
Click to expand...
Click to collapse
Yea this was tested on the tmobile brand. I'm assuming this does not work on the google store unlocked version. I give up.

TheSayaMan said:
Yea this was tested on the tmobile brand. I'm assuming this does not work on the google store unlocked version. I give up.
Click to expand...
Click to collapse
For what it's worth, I purchased my phone from the play store online. I didn't buy a T-Mobile branded version.
Board: sunfish MP1.0(NA)
Bootloader: s5-0.2-6539975
Baseband: g7150-00018-200701-B-6643937
Secure boot: PRODUCTION
NOS production: yes

liamwhite said:
For what it's worth, I purchased my phone from the play store online. I didn't buy a T-Mobile branded version.
Click to expand...
Click to collapse
any idea how to check if verity is enforcing and how to change it. Did a search, can't find anything.

Hmm, it seems like my bootloader was more up-to-date than I realized. The one I am running is actually the one from the RP1A factory image, not sure how/when it updated, because I definitely downgraded it first to get TWRP booting.

liamwhite said:
Hmm, it seems like my bootloader was more up-to-date than I realized. The one I am running is actually the one from the RP1A factory image, not sure how/when it updated, because I definitely downgraded it first to get TWRP booting.
Click to expand...
Click to collapse
Your going completly around what I asked. I'm done with this. Moving to another thread.

Stay away from this, it changes your file system to raw and is a complete waste of time.

I rebuilt my entire source tree, reflashed the Pixel system images and reproduced the corrupt device warning. Picking through the changes, it didn't work because I had inadvertently flashed vbmeta.img on my build but not included it in the zip. I've posted an updated version of the zip and provided new instructions for how to flash this, because Lineage's fastboot does not allow flashing the vbmeta partition (you have to first flash it from the bootloader).
I tested again with a clean wipe, reset to Pixel factory image QD4A.200805.003 and this time it worked without a problem. The android-info.txt will now ensure that you are using the right bootloader when flashing, so that issue should go away too.

Cool I'll give it a try tomorrow
TheSayaMan said:
Stay away from this, it changes your file system to raw and is a complete waste of time.
Click to expand...
Click to collapse
What does this mean

nixromancer said:
Cool I'll give it a try tomorrow
What does this mean
Click to expand...
Click to collapse
This doesn't work. That's what it means. If you want to waste about an hour of your life flashing this then having to flash back to stock or another custom rom than be my guest. This was posted by a new member, not a developer at all. I messed around with this quite awhile and no one is reporting success except the one that started this thread.

TheSayaMan said:
This doesn't work. That's what it means. If you want to waste about an hour of your life flashing this then having to flash back to stock or another custom rom than be my guest. This was posted by a new member, not a developer at all. I messed around with this quite awhile and no one is reporting success except the one that started this thread.
Click to expand...
Click to collapse
The fact that I messed up and didn't realize I had to include the vbmeta.img file in the first zip is my fault, and I totally own that. It isn't able to be flashed in Lineage's fastbootd ("file not found", presumably it's missing a devfs node) so I accidentally excluded it from the image I shipped, not realizing it was mandatory.
Yes, I'm new to this forum, but I'm not new to building Lineage and I've done it many times before. I have serial UARTs for my phones. I'm posting this build here because I'm excited to be the first to get stable lineage running on the 4a, with the full list of vendor blobs and such (see my posted device tree), and this is the first time I've ported Lineage to a new board. It took me a week of tiring work bootstrapping the board, getting the first serial output, getting into recovery, and then finally figuring out that the kernel modules were missing before getting a full boot.
I was annoyed that the flashable zip generated by mka bacon doesn't include the required modules, and in my testing applying it never worked (they were always excluded from the vendor parition, even after multiple makefile changes), which is why I decided to make an ad-hoc flash method using a fastboot update zip, which reliably worked. That was the primary source of the error here. I won't make that mistake again.
I know you're frustrated that the first image I provided didn't work, but I have looked into it, reproduced your issue, and fixed it (and it ironically was only missing one 4K file needed to make it work).

Development [ROM][UNOFFICIAL][cheetah/panther] LineageOS 20.0 for the Pixel 7 Pro/7

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 20.0 for the Pixel 7 Pro (cheetah) and Pixel 7 (panther).
Known issues:
NOTE: This is an early-stage build, and may not be the most stable. It works fine for me as a daily driver on a Pixel 7 (panther), however.
The status bar is mis-aligned to the left by a few pixels, but this does not cause any usability issues, fortunately.
Dual eSIM doesn't work (yet), but stock is probably affected too until the feature drop
You tell me.
Install Instructions:
Spoiler
Be sure you're on the latest stock 13 build and have an unlocked bootloader. You may also be able to flash from GrapheneOS, CalyxOS, or another ROM.
Go into fastboot mode (turn off phone and then Power + Volume down)
Make sure you have the adb/fastboot tools
Run fastboot flash --slot all boot boot.img
Run fastboot flash --slot all init_boot init_boot.img
Run fastboot flash --slot all vendor_boot vendor_boot.img
Run fastboot flash --slot all vendor_kernel_boot vendor_kernel_boot.img
Boot into recovery
Press Factory Reset and confirm
Go to Apply Update -> Apply from ADB
Run adb sideload LOS_BUILD (Replace LOS_BUILD with your LOS ZIP file)
To add GApps, go to Advanced -> Reboot to Recovery -> Apply Update -> Apply from ADB
Run adb sideload GAPPS_BUILD (Replace GAPPS_BUILD with your GApps ZIP file, repeat this step if you want Magisk)
Press Reboot System Now
Update Instructions:
Spoiler
Download the latest ZIP
Reboot to recovery
Flash the latest ZIP
Reboot to recovery
If you previously installed it, flash GApps and Magisk
Reboot to system
Passing SafetyNet/Play Integrity:
For some reason, this ROM only needs the Displax SafetyNet Fix and Shamiko (or DenyList) on top of Magisk in order to pass SafetyNet/Play Integrity, which is a nice bonus. As of 11/17, I was able to use GPay with this ROM if you use Magisk, Shamiko, and Displax SafetyNet Fix.
Download:
Pixel 7 Pro (cheetah)
Pixel 7 (panther)
Official MindTheGApps
UPDATE: LineageOS has "experimental" builds for Pixel 7 (and 6) here. They aren't technically mine, but I'm also the reason Google Tensor GKI kernels build there . Fortunately GPay still works with the experimental builds.
Sources:
Kernel
Device Trees
Vendor

ChangeLog:
2022/11/26:
Updated build to 2022/11/27 (arrgh, UTC/PST differences)
2022/11/16:
Initial build for cheetah/panther.
Is stable (for me at least) on a Pixel 7, your experience may vary however

Reserved 1

Reserved 2

Excited and excellent news. Thank you for your time and patience to bring something for a cheeta.

thanks for sharing

Ahhh Yeah! you rock man! I am dropping everything to get this installed now!! Thank you so much!
oh do you know if this build includes the google photos unlimited storage baked in? I Had It with SparkOS on my pixel 6 pro, and its a lifesaver! I guess Ill find out as soon as i get it running. Thank you again!

Heck ya! Finally! I have experience flashing lineage os. Thanks! Hope the battery life is great.

It did not recognize my sim card as the mobile data was greyed out. I had to revert back to stock rom and did everything correctly as you explained how to install it.

UltimateGamer83 said:
It did not recognize my sim card as the mobile data was greyed out. I had to revert back to stock rom and did everything correctly as you explained how to install it.
Click to expand...
Click to collapse
Are you on eSIM or physical SIM? Pro or non-Pro? Which carrier/country? Do you have a T-Mobile or AT&T variant?
On a unlocked non-carrier variant Pixel 7, this ROM recognizes my T-Mobile US eSIM, and also a Verizon MVNO (US Mobile) physical SIM.

MrNegative370 said:
Ahhh Yeah! you rock man! I am dropping everything to get this installed now!! Thank you so much!
oh do you know if this build includes the google photos unlimited storage baked in? I Had It with SparkOS on my pixel 6 pro, and its a lifesaver! I guess Ill find out as soon as i get it running. Thank you again!
Click to expand...
Click to collapse
I don't use Google Photos since I use Nextcloud and am not sure, but it should work since unlike official LOS builds, the ROM fingerprint is the same as stock (also similar to how Play Integrity passes).

MrNegative370 said:
Ahhh Yeah! you rock man! I am dropping everything to get this installed now!! Thank you so much!
oh do you know if this build includes the google photos unlimited storage baked in? I Had It with SparkOS on my pixel 6 pro, and its a lifesaver! I guess Ill find out as soon as i get it running. Thank you again!
Click to expand...
Click to collapse
No lineageos doesnt have this feature. Use the Pixelify.apk and you are good to go.

gapps doesnt have android 13? how do i get gapps after i flash lineageos?

my google playstore doesnt work, tried reflash gapps 3 times.

gapps : https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-T/08-Sep-2022/

SynGreis said:
gapps doesnt have android 13? how do i get gapps after i flash lineageos?
Click to expand...
Click to collapse
The GApps link does show A13 to me, it's the MindTheGapps-13.0.0-arm64-20221025_100653.zip file you need to download and flash for GApps.

SynGreis said:
gapps doesnt have android 13? how do i get gapps after i flash lineageos?
Click to expand...
Click to collapse
You have to reboot to recovery before you install GApps. If you just flash GApps after Lineage without rebooting to recovery, you won't get GApps.
This is an issue with A/B partition devices (basically all modern Android phones).

tried it again. reinstalling from scratch. i have a pixel 7 pro factory unlocked model straight from google.com. i have the bootloader unlocked with oem. my carrier is att with phsyical sim. so it is indeed working this time. maybe the first time didn't work because i forgot to factory reset.

UltimateGamer83 said:
tried it again. reinstalling from scratch. i have a pixel 7 pro factory unlocked model straight from google.com. i have the bootloader unlocked with oem. my carrier is att with phsyical sim. so it is indeed working this time. maybe the first time didn't work because i forgot to factory reset.
Click to expand...
Click to collapse
That's your issue, if you don't factory reset then it obviously won't work.
Well, sometimes I forget it too .

Can you install gcam after? And is it working properly?