Database Users

How to install Custom ROM CM 12.1 Lollipop 5.1.1 with Phillz Recovery and Root i9192

Hi, everyone I have recently did Custom ROM CM 12.1 Lollipop 5.1.1 on my Samsung Galaxy S4 Mini I9192. So for complete steps how to do it, Follow the Steps -
Strictly for I9192 Devices
Be noticed that it will void your warranty and your device may get brick during process. Also keep your battery fully charged before doing anything. I am just showing you things to do, in any odd situation YOU ARE RESPONSIBLE for damage.
For all the steps below use genuine USB cable comes with your device.
Start By Installing Phillz Recovery on your device. Here it is how
Download philz_touch_6.48.4-serranodsub_AndroidTunado.tar and Odin
When your phone is full charged, turn it off.
Enter Download Mode by pressing HOME + VOLUME DOWN + POWER KEY.
When download screen will appear open Odin and connect your phone to computer with USB Cable.
You will see your device detected as "COM:*". In Odin, do not change any checkbox settings and click PDA or AP (whatever available) and choose Phillz recovery "philz_touch_6.48.4-serranodsub_AndroidTunado.tar" file.
After choosing file, click Start Button to begin downloading in phone.
Your phone will reboot automatically and Phillz Recovery willl be succesfully installed.
So we are done with custom recovery. Next step is to install CM 12.1 . Again charge your battery if you lose any during Phillz Recovery. For download CM 12.1 and Gapps follow this post - http://forum.xda-developers.com/galaxy-s4-mini/development/rom-cyanogenmod-12-0-s4-mini-duos-gt-t2950526 (Big thanks to @k2wl).
After downloading, paste both .zip files to SDCARD. I recommend to paste both in internal and external memory in case.
Before installing ROM must do a backup of your device, install Nandroid or Titanium Backup from Google Play and get a full backup of your system and data. You need almost 4GB of space in external SDCARD to do so. Don't miss the backup as it will be only way to get you back on working phone if any failure occur. (Copy on computer as well to get secured)
So we are ready to install CM 12.1 yay! (Unlpug USB Cable if connected)
Boot your device into Recovery Mode by pressing HOME + VOLUME UP + LOCK BUTTON
From there wipe the system and clear cache: “wipe data factory reset”, “wipe cache partition” and “wipe dalvick cache”.
From main menu of recovery select “install zip from SD card” and “choose zip from SD card”.
Pick the cm-12.1-20XXXXXX-UNOFFICIAL-serranodsdd.zip file from SDCARD and install it.
When completed, DON'T EXIT/REBOOT, press again install zip from SD Card and choose gapps zip and install it.
When done Reboot your device.
There it come cynogenmod icon on bootup of your OS. Congrats CM 12.1 is installed. You can go to setttings and see version 5.1.1 of android working!
Don't forget to follow changelog of ROM for new nightly infos: http://www.cmxlog.com/12.1/serrano3gxx/#next_build
So follow rest if you want SuperUser in your device. Please note if you don't want superuser and yet Root access you have inbuilt in ROM at Settings >Developer Options > Root. Only follow below if you want SuperUser Application to have control over root access.
Download SuperSU-v2.46.zip file (from attachments) and put in your SD Card.
Again bootup in recovery mode HOME + VOLUME UP + LOCK
Choose "Install Zip from SD Card" and choose SuperSU-v2.46.zip
Install the package
When done reboot the device and you have SuperUser installed
{
"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"
}
Enjoy CM 12.1 with phillz recovery and ROOTED. Keep in mind its just a tutorial. I take no responsibility of ROM or softwares attached. For your info, everything went perfect for me on my I9192. Let me know how your experience went!
Special Thanks to
@k2wl
and everyone who contributed in zip files.

hi, thanks for the post.
even for me, everything went perfect with the installation.
any further updates with your user experience, so far? hows the battery backup ?

ROM Performance as CM12.1 Nightly 3 July
ROM is almost stable and you may not have any trouble with general usage. Calling, Messaging, Wifi, Bluetooth, Radio almost everything is working. Camera quality is same as on stock and with same upto Full HD Recording. UI is more faster (thanks to no bloatware) and new settings for many new lollipop features and developer options. Battery life is same as stock (Falls to 20% after 3h 52min Screen Uptime with moderate usage with games and music playback). I haven't find any difference in battery yet using for 10 days. What I find is needed to improve or buggy are following
Random Force Closes - Few Apps (not all) get closed automatically. I often use a music player (debug version as I am developing it) which automatically closes after some time. (Maybe force close only for debug or non play-store apps, not sure, let me know about your experience) (Seems solved in newer update)
Games are not as fast as Stock Samsung - Heavy games like Asphalt 8 loses frames which is not with stock ROM. Sometimes Clash of Clans too behave a little laggy (once in hundred times).
Earpiece Speaker - I don't know if their is problem in my network provider or phone but 1 in 10 calls I can't hear anything what other person is speaking while connecting headphones give response and normal sound of caller. Tell me if it's same with you or I got problem at connection ?!?!?! Really annoying. (Most probably working 100% in new update as told by @roshanu)
Issues are being detected by @k2wl and improvement is going on everyday. You can upgrade to newer ROM when any comes out.
This post may get outdated anytime when ROM will be improved. To know what are changes in new nightlies, follow ROM Download Link > Changelog
Tell me what are new issues or if any old issues get resolved. Thanks everyone
Thanks to @roshanu for reminding of this post.

I am on July 10 version, installed using CWM recovery. Been two days now. Pretty basic use: no gaming no music.
ROM is stable so far, no force closes.
+1 on the light sensor.
Haven't had any problem with the earpiece speaker.
It seems root access was getting disabled on reboot, not sure. Also there was no SU app after the installation.
So I enabled the root for apps and adb through developer options, then installed the SU app through Play. Working fine now.
Will update new findings, if any...
Do you know if 4G LTE can be enabled on our phone i9192, or even future possibility ??

roshanu said:
I am on July 10 version, installed using CWM recovery. Been two days now. Pretty basic use: no gaming no music.
ROM is stable so far, no force closes.
+1 on the light sensor.
Haven't had any problem with the earpiece speaker.
It seems root access was getting disabled on reboot, not sure. Also there was no SU app after the installation.
So I enabled the root for apps and adb through developer options, then installed the SU app through Play. Working fine now.
Will update new findings, if any...
Do you know if 4G LTE can be enabled on our phone i9192, or even future possibility ??
Click to expand...
Click to collapse
It's good that developers are working on ROM and issues are solved pretty fast. For SU app you have to flash the SU zip file (in attachments) in download mode (by pressing [Volume Down] + [Home] + [Lock]). And sadly 4G LTE depends on chipset and hardware, not on software, so it can never be more than HSPA+ in any update. Do post any issues or any new improvement, it may help developers

[VK810] [altev] [CM13] Invisiblek's Unofficial - Update from Invisiblek post #28

Update from Invisiblek post #28
This thread is only for until/if @invisiblek opens his own thread. If he does, I'll link to his thread and close this one, or transfer the OP to him if he wants.
or How I Learned to Stop Worrying and Love my Tablet Again.
{
"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"
}
Dr. Strangelove or: How I Learned to Stop Worrying and Love the Bomb (1964)
Thanks to:
@invisiblek for building and permission to link to his CM13 builds folder, and all his work to get this to the point it is right now, including getting Mobile Data to work
@Hnk1 for making me aware that the builds had started
Don't expect support from anyone in this thread. Help might come but it's likely that if you're experiencing a problem that @invisiblek is already aware of it, or it's a CyanogenMod issue that all ROMs will have. In the meantime, please feel free to communicate with other CM13 for VK810 users here to confirm/deny the existence of any issues you might have, or discuss any workarounds when possible.
Please mention what build date of CM13 you're on when you're discussing issues.
Installation Notes:
It's smooth as butter.
Flashing this definitely doesn't work with a newer bootloader. I recommend flashing this from TWRP v2.8.7.0 after a fresh flash of the 11A KDZ and downgrading the bootloader in order to install the initial Loki'd version of TWRP v2.7.0.1 and then upgrading to 2.8.7.0, or if necessary, first the 22B TOT and then the 11A KDZ after. All necessary instructions are in my [VK810.4G] [altev] most reliable way to root and install a custom recovery thread. I actually manually downgraded the aboot (bootloader) even though I was on 11A and my instructions at that link specify that downgrading the bootloader further wasn't necessary, so I haven't tested straight from 11A's bootloader.
When I had tried @invisiblek's TWRP v3.0 July 19, 2016 build for the VK810 (the current build that's available), it accessed internal storage just fine - my MicroSD card is formatted ExFAT so that might be the trouble - I haven't tested USB OTG on this build, nor backing up or restoring. This build of TWRP flashed the ROM okay, and looked like it flashed OpenGApps Pico okay, but no matter how many times I tried or even trying to flash OpenGApps Nano, when the ROM was booted the Play Store still wasn't there. Reverted to a known good version of 2.8.7.0, wiped all and fresh flashed ROM and OpenGApps Pico and all's good so far.
I use Slim Zero GApps for Marshmallow (6.x) with this, available at [GAPPS][6.0/5.1/5.0][arm/arm64] Official Slim GApps. @invisiblek uses Open GApps (Pico Package). This tablet uses an ARM processor and CM13 is Android 6.0x.
OTA's work and point to @invisiblek 's newer builds when they're available. If you take OTAs and you had system Xposed installed, you'll have to flash Xposed again.
[*]Root can be enabled without SuperSU by first enabling the "Developer options' in Settings. Do so by going to Settings / About tablet / scroll down and touch "Build number" about 10 times in a row, then you can see "Developer options" in the main Settings menu immediately before the About menu. At the bottom of the first screen of the "Developer options", under "Root access", enable either "Apps only" or "Apps and ADB", for most users' purpose. I believe "Android debugging" (two options down further from the "Root access" in "Developer options") was already enabled.
System Xposed build 86 (sdk23) for Arm processor, and Greenify including the latter's Xposed module appears to work okay. Trying G3TweaksBox (made for stock but might still provide some functionality under CyanogenMod) rotation tweaks doesn't appear to help the rotation issue I'm having. G3TweaksBox's Sound options like "Link Ringtone and Notifications volume", "Force media volume control" and "Auto expand volume panel" all appear to work. Other modules I've tested: Amplify, Battery Home Icon (% text at least for 100% is offset), DirectAPKInstall Module doesn't work (I think it didn't work on stock on this device, it works fine on my VS985 G3), Flat Style Bar Indicators, Marshmallow SD fix, Play Store Changelog, installed but haven't tested YouTube AdAway and YouTube Background Playback. I had attempted Systemless Xposed and it wouldn't flash from TWRP, but it's supposed to specifically require SuperSU v2.76, so I didn't necessarily expect it to work with CM's built-in root. Haven't tried SuperSU yet, but if you do, disable CM's built-in root first.
Do not ask about when anything will be fixed, nor requests for features/new builds etc, or when CM14 (Nougat) or CM26 (Zagnut) will be released.
What's broke (at least on cm-13.0-20160716-UNOFFICIAL-vk810.zip):
Camera
Brightness adjustment (I recommend Lux Auto Brightness or Lux lite by Vito Cassisi and it can be chosen to integrate with CF.Lumen by @Chainfire)
Occasional black screen when you try to wake up the tablet. It's necessary to hold the power button in for 10 seconds or so to force turn it on, then either continue to hold the power button or let go and press again to turn boot the tablet back up. @invisiblek hasn't had this issue on his own VK810 in a while so I need to provide some further testing and reporting once I experience the issue again. I haven't yet tried the GApps that @invisiblek uses just to rule that out although I doubt if that'll make a difference.
Rotation might not work - I haven't tested on the fully "stock" ROM and have a bunch of apps/tweaks installed now so will have to double-check on a fresh flash later. The best app workaround I've found is Rotation Control. This enables you to manually control rotation via icons in the pull down notifications. There's other apps to do the same thing but one of the other highly rated ones didn't work for Reverse Portrait, and the other one didn't have Reverse Portrait at all. At this time I have no idea if the tweaks I made in G3TweaksBox might've improved the "Rotation Control" app's behavior, or if any other settings I have going on might've one of the other apps I tested.
Downloads: [*]http://www.invisiblek.org/roms/cm-13.0/vk810/

Screenshots:
Keep in mind these screenshots are after my tweak apps:
Using Style part of Dark F Material theme:

My process of elimination steps trying to diagnose why I always get 1) sudden black screen and also 2) sudden soft reboots (starts immediately with CM boot animation) and 3) UI restarts.
8/2/2016 morning: wiped Cache, Dalvik/ART and Data flashed the 8/1 build and OpenGApps Pico 8/1 or 8/2 from TWRP v3.0 M5 July 19 build, then booted the ROM and noticed GApps hadn't installed even though it looked like it went through the motions. Repeated attempts to flash GApps both Pico and Bank from TWRP v3.0 had same results. Flashed TWRP v2.8.7.0 by Brian someone and flashed GApps and they installed fine.
Set my Google account up, changed a bunch of settings and I think I enabled CM's root, installed some stuff, was satisfied and then by mid-afternoon I opened my case and found it had black screened.
8/2/2016 evening: Put his TWRP v3.0 July 19 build back on, wiped Cache, Dalvik/ART and Data, flashed the 8/1 build (but not OpenGApps), then wiped internal storage, turned the tablet off, ejected my MicroSD card which is formatted ExFAT, and booted the ROM. I turned WiFi and Mobile Data off but otherwise didn't touch it at all.
8/3/2016 late morning, tablet still hasn't had issue so I put it in Airplane Mode, one of the things I almost have it set to when I'm not using Mobile Data.
8/4/2016 late morning, still no trouble. Connected to unsecured work WiFi, downloaded latest OpenGApps pico and latest stable SuperSU.zip v2.76. Rebooted to TWRP v3.0 M5, flashed SuperSU.zip and the log looked perfect but apparently the ROM won't boot. This TWRP 3.0 M5 build won't read my USB-OTG or a 16 GB FAT32 MicroSD card I put in. Using USB, the PC does access internal storage through MTP in TWRP v3.0 M5, so putting a copy of CM13 on internal storage to flash. Dirty flashed CM13 8/01 build and it's booting okay.
Enabled Developer options and CM's built in root for Apps only. Tomorrow I'll install @Chainfire 's FlashFire and try to use it to flash OpenGApps since when I used TWRP v3.0 M5 to flash OpenGApps, once booted to Android GApps weren't there and I'm trying to avoid going back to TWRP v2.8.7.0 for now.
[*]8/4/2016 mid-afternoon. Interesting but not conclusive observation. My last action late this morning was to enable CM's built in root for Apps only, and just now (four hours later?) I opened my case and found the tablet was having the black screen issue (requiring a power button long press to force off and turn back on). I just re-disabled CM's built-in root, I'm rebooting the tablet again after having changed that setting, and we'll see if it black screens again anytime by tomorrow. If not, I may enable root again and see if it black screen relatively quickly.

One more.

Updated OP with accurate information about @invisiblek 's latest build of TWRP v3.0 for the VK810 as of July 19th, 2016. Summary: seems to work, just possibly not with ExFAT for my MicroSD card, or not with a 128 GB card.
Edited update: This build of TWRP flashed the ROM okay, and looked like it flashed OpenGApps Pico okay, but no matter how many times I tried or even trying to flash OpenGApps Nano, when the ROM was booted the Play Store still wasn't there. Reverted to a known good version of 2.8.7.0, wiped all and fresh flashed ROM and OpenGApps Pico and all's good so far.
Ugh...still got a black screen. I'll try without installing any apps or having or root enabled.

Delete.

I am gonna try this weeked. Any idea which build is the most stable?
Sent from my unknown using XDA-Developers mobile app

lhrt said:
I am gonna try this weeked. Any idea which build is the most stable?
Click to expand...
Click to collapse
I think all the most recent builds are the same - he hasn't made any new commits to GitHub at least not as of yesterday. He tried getting the camera working, but it still doesn't for me, it FCs.
That said, be very careful and slow in setting it up and installing. I don't know why I always have trouble with CM builds on this tablet (sudden black screen requiring a long power button press to force off and back on, sometimes just suddenly it soft reboots - starts immediately with the CM boot logo, not a full reboot). I used the latest build and OpenGApps this time, I had a reasonably full gambit of my apps installed and set up, CM's built-in root enabled in Developer options, but I didn't have Xposed installed this last time and it still went black screen later yesterday.
So I went into full-process-of-elimination mode. I had all the files I needed on internal storage, but also on the MicroSD card, I installed his TWRP v3.0 M5 for the VK810, wiped all again including internal storage this time, and only flashed the ROM. Then I shut down the tablet from TWRP's reboot menu, ejected my MicroSD card which is formatted ExFAT and his TWRP doesn't like anyway, although it's always worked fine itself in both CM and in the stock ROM, and I've left it like that since last evening and it hasn't black screened.
Next I'll probably flash OpenGApps and then leave it sit for a day to see if it does anything. Oh yeah, when i tried flashing OpenGApps from his TWRP I don't think it worked right so I might have to either downgrade to someone else's TWRP v2.8.7.0 or try FlashFire to flash GApps.
I'll continue like this in patient stages so that I can notice when it starts black screening again. I haven't touched any settings in Android yet, not even enabled the built in root. I might flash SuperSU from TWRP instead this time though, once I get around to it.
Good luck! Let us know how it works for you!

Updated the third post with my process of elimination steps and progress. http://forum.xda-developers.com/showpost.php?p=67819877&postcount=3

Interesting but not conclusive observation - I'll add to the third post. My last action late this morning was to enable CM's built in root for Apps only, and just now (four hours later?) I opened my case and found the tablet was having the black screen issue (requiring a power button long press to force off and turn back on). I just re-disabled CM's built-in root, I'm rebooting the tablet again after having changed that setting, and we'll see if it black screens again anytime by tomorrow. If not, I may enable root again and see if it black screen relatively quickly.

So the CM (CyanogenMod) 13 is the same as Android 6.0 Marshmallow?
EDIT:
I just flashed the CM13 Unofficial zip for VK810 in TWRP v2.8.7.0 and my tablet is now stuck in bootloop. It shows the Android for a minute then goes to blank screen.
---------- Post added at 10:09 PM ---------- Previous post was at 09:54 PM ----------
roirraW "edor" ehT said:
Updated OP with accurate information about @invisiblek 's latest build of TWRP v3.0 for the VK810 as of July 19th, 2016. Summary: seems to work, just possibly not with ExFAT for my MicroSD card, or not with a 128 GB card.
Edited update: This build of TWRP flashed the ROM okay, and looked like it flashed OpenGApps Pico okay, but no matter how many times I tried or even trying to flash OpenGApps Nano, when the ROM was booted the Play Store still wasn't there. Reverted to a known good version of 2.8.7.0, wiped all and fresh flashed ROM and OpenGApps Pico and all's good so far.
Ugh...still got a black screen. I'll try without installing any apps or having or root enabled.
Click to expand...
Click to collapse
I got a black screen after I flashed this http://www.invisiblek.org/roms/cm-13.0/vk810/. Is there another solution for this?

kawhayang said:
So the CM (CyanogenMod) 13 is the same as Android 6.0 Marshmallow?
EDIT:
I just flashed the CM13 Unofficial zip for VK810 in TWRP v2.8.7.0 and my tablet is now stuck in bootloop. It shows the Android for a minute then goes to blank screen.
---------- Post added at 10:09 PM ---------- Previous post was at 09:54 PM ----------
I got a black screen after I flashed this http://www.invisiblek.org/roms/cm-13.0/vk810/. Is there another solution for this?
Click to expand...
Click to collapse
Yep.
Doubtfull, another user reported the same problem (in a different thread, unfortunately). You had wiped Cache, Dalvik/ART and Data, right?

roirraW "edor" ehT said:
Yep.
Doubtfull, another user reported the same problem (in a different thread, unfortunately). You had wiped Cache, Dalvik/ART and Data, right?
Click to expand...
Click to collapse
Whenever I wipe the data/cache from TWRP, it wipes the OS because it says afterwards there is no OS installed.
If I follow these instructions, do they also take me to Android 6.0 Marshmallow? http://forum.xda-developers.com/lg...t-install-t3283027/post64577888#post64577888

kawhayang said:
Whenever I wipe the data/cache from TWRP, it wipes the OS because it says afterwards there is no OS installed.
Click to expand...
Click to collapse
I don't know what's going wrong for you. Wiping Cache, Dalvik/ART and Data never wipes the OS on any device for me. You have to wipe those things before booting a new ROM, especially when going from stock LG ROMs to CyanogenMod/non-stock ROMs, or the ROM won't boot or work right.
If I follow these instructions, do they also take me to Android 6.0 Marshmallow? http://forum.xda-developers.com/lg...t-install-t3283027/post64577888#post64577888
Click to expand...
Click to collapse
No. This is the only Android 6.0 I've noticed for the VK810. My thread you referenced deals with stock LG ROMs, and there is no stock Marshmallow for the VK810, only Lollipop 5.0.2 which runs laggy, and is why I'm running 24A KitKat instead.

[/QUOTE] No. This is the only Android 6.0 I've noticed for the VK810. My thread you referenced deals with stock LG ROMs, and there is no stock Marshmallow for the VK810, only Lollipop 5.0.2 which runs laggy, and is why I'm running 24A KitKat instead.[/QUOTE]
This goes to show how different devices act differently. My tab was real laggy on kitkat, but on lollipop it's been pretty smooth. I'm counting on you for some marshmallow action! lol

ryanallaire said:
This goes to show how different devices act differently. My tab was real laggy on kitkat, but on lollipop it's been pretty smooth. I'm counting on you for some marshmallow action! lol
Click to expand...
Click to collapse
Absolutely! (different people's devices acting different with the same model). Of course, I've hardly been using my tablet at all and only have a couple dozen maximum apps installed, and I have severely debloated the stock stuff. Who knows. Make sure and gives thanks to @invisiblek, he's the one developing CM13 for the VK810 - I just created the thread. Since it's not mine is why I created it in the General section and since it's just a pretty much an announcement thread.

roirraW "edor" ehT said:
I don't know what's going wrong for you. Wiping Cache, Dalvik/ART and Data never wipes the OS on any device for me. You have to wipe those things before booting a new ROM, especially when going from stock LG ROMs to CyanogenMod/non-stock ROMs, or the ROM won't boot or work right.
No. This is the only Android 6.0 I've noticed for the VK810. My thread you referenced deals with stock LG ROMs, and there is no stock Marshmallow for the VK810, only Lollipop 5.0.2 which runs laggy, and is why I'm running 24A KitKat instead.
Click to expand...
Click to collapse
I wiped the Cache, Dalvik, and Data and flashed the CM13 Unofficial ROM. It takes me all the way to Starting Preparation/Optimization Completed and reboots and gives me a dark screen and doesn't get past the blue android and gets stuck in boot loop. I am thinking of just upgrading to Lollipop. http://forum.xda-developers.com/lg...10-4g-official-lollipop-5-0-2-35a08-t3113607

kawhayang said:
I wiped the Cache, Dalvik, and Data and flashed the CM13 Unofficial ROM. It takes me all the way to Starting Preparation/Optimization Completed and reboots and gives me a dark screen and doesn't get past the blue android and gets stuck in boot loop. I am thinking of just upgrading to Lollipop.
Click to expand...
Click to collapse
One or two other users had problems with the latest builds too. I had problems with builds from a couple of weeks back, as you can read in this thread, but not that problem. That's part of the trouble with CM, it takes a long time (and effort of the person doing the compiler, or others who submit commits to the device-specific source code) to iron out bugs. People have other troubles with CM13 on the LG G3, too.
I liked stock debloated Lollipop but it would just get so slow for me eventually - I used it for a year or so. I hope it works better for you.

roirraW "edor" ehT said:
One or two other users had problems with the latest builds too. I had problems with builds from a couple of weeks back, as you can read in this thread, but not that problem. That's part of the trouble with CM, it takes a long time (and effort of the person doing the compiler, or others who submit commits to the device-specific source code) to iron out bugs. People have other troubles with CM13 on the LG G3, too.
I liked stock debloated Lollipop but it would just get so slow for me eventually - I used it for a year or so. I hope it works better for you.
Click to expand...
Click to collapse
Is there any other way to get past this when flashing CM13? Sorry, I probably asked this before but I really want to be able to use this on my (VK810) device.

kawhayang said:
Is there any other way to get past this when flashing CM13? Sorry, I probably asked this before but I really want to be able to use this on my (VK810) device.
Click to expand...
Click to collapse
I've told you everything I know about it. I wish it worked better too, but I'm not in control of it, @invisiblek is most likely busy with lots of other things. The only other solution is for you to learn how to compile, debug and fix source code. I've never done any of those things.

Experience : successful Resurrection Remix NEM-L51 - Meticulus's ROM v5.8.5-20171214

Hi all XDA's members and Meticulus's RR ROM contributors,
I would like to share my experience with Meticulus's RR ROM for Honor 5C.
First I tried Elite V6 with no success : bootloop, F2FS or EXT4 nothing to do ; the Elite V7 is available from Christmas but I see that there are bugs to fix for Hassan, so I gave up and restored a backup of my STOCK system.
The restore was not good as my camera and audio no longer worked...
Before I get back to the STOCK update NEM-L51C432B357, I decided to try Meticulus's RR. It was a very good idea as I now have a renamed Honor 5c to hi6250 (...) working with no bug up to now.
LTE OK, SMS OK, GPS OK, SDCARD OK, AUDIO OK, VIDEO OK, GAPPS OK, MTP OK, etc
Adaway OK, Afwall+ OK, Magisk v14 OK
+ Bonus : Evie Launcher working as it was not using with STOCK ROM (icon size issue) !
Many thanks to Meticulus and contributors for sharing this very good work.
---
To be more precise for Honor 5C owners :
DEVICE : HONOR 5C
ROM STOCK BUILD : NEM-L51C432B350
MODDED RECOVERY .. : TWRP-3.1.1-0-hi6250-v5.2.zip
ROM INSTALLED .... : RR-N-v5.8.5-20171214-hi6250-Meticulus.zip
GAPPS INSTALLED .. : open_gapps-arm64-7.1-pico-20171225.zip
---
Steps of my successful installation with SDCARD and no SIM CARD :
1- FASTBOOT the TWRP then reboot to the TWRP RECOVERY
2- Wipe all except external SDCARD
3- Install the ROM
4- Reboot to TWRP RECOVERY
5- Install the GAPPS
6- Reboot to system (RR)
7- During RR Android setup, when asked insert the SIM CARD.
It would perhaps also have been successful with the SIM CARD inserted from the beginning...
---
Questions/feature requests :
- On Resurrection Remix site, I have not found your great ROM why ?
- On XDA Dev, there is no thread "Resurrection Remix For The Honor 5C [METICULUS]" but a "[ROM][7.1.2] Resurrection Remix For The Honor 6x [METICULUS]" one, this is why I put my comments here and in the Elite thread for those like me unable to get Elite V6 or V7 working with their Honor 5C.
- One thing is really missing to me (not found in settings) : the scheduled start/stop that worked very well with the STOCK ROM.
Do you think that this useful feature could be added on a future version ?
- The double TAP for screen wake up, would be a great bonus feature (was not provided in the STOCK ROM).
- Not tested the OTG, I will tell it in this thread.
Thanks again.
---
Meticulus's replies :
1. It is unlikely that any device with a kirin processor will get "official support" for LineagOS and therefore Resurrection Remix. There just isn't enough source.
2. Just because there is no "Honor 5c" thread doesn't mean you should come here and confuse information. It makes the water muddy. There is nothing stopping you from creating a thread in the "Honor 5c General" and post your experienced there.
3. Scheduled device start and sleep is not something I will work on.
4. DoubleTap 2 Wake only works on some P9 Lite's. Other devices with different touchscreens simply do not have the hardware capability.
5. I'm glad you like the ROM but please re-post your experiences in the Honor 5c section. I intend to delete these posts...

Is working dual sim and volte
Is works dual sim and volte

Sim working fine??

What do you think solved the audio issue?
Reverting to Stock Rom backup could have helped somehow.
Renaming it maybe ? And how did you rename it? After installing this rom mine became hi6250.
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Now installed this ResurrectionRemix twrp and rom after seeing this thread.Audio still refuses to work .

thatwasmyfakeacc said:
What do you think solved the audio issue?
Click to expand...
Click to collapse
I had the same problem on my NEM-L51. The problem is (or at least i think it is), that the vendor partition is somehow corrupted.
Short explaination, the vendor partition holds some drivers which are not open source (therefore not in the android kernel) and also aren't shipped in the custom roms (because of copyright stuff). So you always need to have them, if the custom rom depends on them (and most/all of the honor 5c custom roms do so). That's also the reason why you always have to flash the custom rom over your emui5.x and if you screwed your whole system, you first need to flash a backup or get back to emui on a different way before you can flash a working custom rom again.
So that's the explaination part. I installed twrp on my device, took a complete backup, flashed aosp from meticulus, everything worked except of Audio/Videos. Flashed LineageOS from Hassan, everything worked except of audio/video playback. Flashed backup, everything worked except audio/video. WTF. I don't know why, but i believe that the backups made with TWRP were somehow not complete, because flashing all partitions (the backup was over all partitions, triple checked, made new backups from stock) didn't solve audio issues, not even on the stock backup. What I now did was getting back to stock with the dload method, and flashed again directly the lineageos from hassan, which then worked. I had a try before where i first accidentially flashed aosp again, and same problems occured again. Also the now stock backup again didn't work. That's why i think that the TWRP backups for Honor 5c NEM-L51 are somehow not right.
Tl;dr if you have audio/video playback issues, try to get back to stock (make sure those features work on your stock rom) and flash again. If it still doesn't work, custom rom is maybe not compatible with nem-l51 (only experienced that with meticulus roms, hassans work great).
thatwasmyfakeacc said:
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Click to expand...
Click to collapse
Try again with the dload method, maybe use another UPDATE.zip. I had to try it several times, device booted sometimes for ever, and suddenly it worked. No idea why, but maybe try it again.

Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones

stevedat said:
Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones
Click to expand...
Click to collapse
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.

thelous said:
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.
Click to expand...
Click to collapse
Rite, it's just for fun.

shankarjdhv125 said:
Is works dual sim and volte
Click to expand...
Click to collapse
Hi,
Dual SIM not tested, Volte I don't know if it works using my ISP (free.fr) and don't know how to check this.
An advice, don't update Magisk, I have done it on several rr (honor 5c, idol3 5.5), the result was bootloop.

[help][touch not working]

after booting deadman twrp 3.1.1 on los 16.1, touch of my phone is not working, even in twrp..
afte that I flash stock oreo via MI flash tool.. but no result, same problem, touch wrong.. like mad, ,
any fix there >???
please some one help me... plz

I think you should select clean flash again while flashing rom through mi flash tool!

Facing same problem, clean flash did not help. Please reply.

I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.

Bro, how about upgrade to Oreo? Is the touch still fixed?
Fewome said:
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse

Faced the same problem. I played with the firmware and stopped working the touchscreen. This tip rolled back to 7.1,2 helped. The phone began to work.
I updated it after the initial configuration and connection to the network, the phone itself downloaded the update and installed it. Updated to 8.1.0.
Thank you so much for sharing!

Hi, touch, fingerprint and capacitive buttons stopped working after I installed Pixel experience ROM, I rolled back to 7.1.2 using Mi flash tool according to your suggestion (same versions of Miflash and ROM as suggested by you). Still the problem isnt solved, please help.

meet4300 said:
Hi, touch, fingerprint and capacitive buttons stopped working after I installed Pixel experience ROM, I rolled back to 7.1.2 using Mi flash tool according to your suggestion (same versions of Miflash and ROM as suggested by you). Still the problem isnt solved, please help.
Click to expand...
Click to collapse
same problem how did you solved it ?

As my phone was in warranty, I was able to get it solved by replacing motherboard. Booting older versions of TWRP can get the touch working, this is suggestion is still to be tested. Try your luck if you can sort it out. In Pixel experience rom, there is an option of double tap to wake. I think thats the reason this fuss is all about. I think due to a different manufacturer, maybe our screens won't support it.

For those who still did not get touch working after installing stock nougat just unlock bootloader and boot twrp 3.2.1 (strictly never flash it...just hot boot it..... it's the reason ur touch got malfunctioning...)and reboot voila!...ur touch is restored

I still can't seem to get it to work.
Tried nougat and two oreo version but the issue remains.
The touchscreen does work after I boot the device but does not work after it wennt to sleep/lock screen.
The screen does also not work inside twrp
i also tried to install a custom rom via adb shell and twrp but the zip fails (9.0 and lineage)
I hope someone could help me

diocore said:
I still can't seem to get it to work.
Tried nougat and two oreo version but the issue remains.
The touchscreen does work after I boot the device but does not work after it wennt to sleep/lock screen.
The screen does also not work inside twrp
i also tried to install a custom rom via adb shell and twrp but the zip fails (9.0 and lineage)
I hope someone could help me
Click to expand...
Click to collapse
Disable DT2W and voila, fixed.
I don't know what the problem is, but I know how to "fix" it.

diocore said:
I still can't seem to get it to work.
Tried nougat and two oreo version but the issue remains.
The touchscreen does work after I boot the device but does not work after it wennt to sleep/lock screen.
The screen does also not work inside twrp
i also tried to install a custom rom via adb shell and twrp but the zip fails (9.0 and lineage)
I hope someone could help me
Click to expand...
Click to collapse
Same problem. Did you make any progress?

leodoct said:
Same problem. Did you make any progress?
Click to expand...
Click to collapse
I'm in trouble too. Tried Nougat, but didn't work. Any other ideas?
Edit: now I can't reflash anything from Nougat. It just says "Device is locked"

mikla90 said:
I'm in trouble too. Tried Nougat, but didn't work. Any other ideas?
Edit: now I can't reflash anything from Nougat. It just says "Device is locked"
Click to expand...
Click to collapse
Well i found a solution for my case. The problem for me was the version of platform tools i used to lock-unlock boot-loader, boot the system and running any commands install HAL3 etc..
Every installation i did (firmwares, from nougat to oreo and last to pie) was executed with the platform tools latest windows version that boot.img had (14,888KB) size.
The version that my touch screen began to work again is the platform tools r.28.0.1.windows that had the boot.img (34,928KB) size.
When i booted the phone in fastboot mode, i opened platform tools r.28.0.1.windows and run the command "fastboot boot boot.img" the phone rebooted and the touch was working again I think that the boot.img file of this version is the correct to boot the phone normally.
Hope this helps....

fewome said:
i had the same problem with a new mi a1. After installing twrp and flashing lineageos the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When i flashed stock oreo with miflash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download miflash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official nougat rom (not oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with miflash 2017.7.20.0
after this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to oreo. I didn't even check the stock firmware when it arrived, because i didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
thank you sooooo much dude u saved my ********ing assssss!

ash roxx said:
For those who still did not get touch working after installing stock nougat just unlock bootloader and boot twrp 3.2.1 (strictly never flash it...just hot boot it..... it's the reason ur touch got malfunctioning...)and reboot voila!...ur touch is restored
Click to expand...
Click to collapse
Thank You .. You are a lifesaver
:good:

Mi A1 touch responds somewhere on screen
Fewome said:
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
packpunk said:
Bro, how about upgrade to Oreo? Is the touch still fixed?
Click to expand...
Click to collapse
Please let me know if someone have solution. PLZ PLZ PLZ
I flashed latest rom pie/ oreo/naughut...but no luck.
I also hotboot recovery start but still touch lagging.
Plesae let me know if there is any solution.

Dear Xda Members I have Problem with my MI A1
I downgrade it to 7.1
Aflter Flashing clean all and relock its with MI flasher tool, My touch Screen misbehave, I try nought and oreo firmware (above mentions also) but problem cant solve
Please help me

Thanks
[if you install this firmware and make clean and relock so you need to unlock bootloader for OTA update]
Thanks You very much Dear your solution is working well.
I downgrade my cell for some reson from pie, when I clean Install and relock I face touch problem, I try manay official firmware but all wrost,
Then I try your shearing mathod, LOL WoW Its worked, I install this firmware then OTA 8.1 and then OTA 9.0 and then AOSP Ex on my cell now its worked fine!
Fewome said:
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse

[ROM][R][OFFICIAL] LineageOS 18.1 for Xiaomi Mi 8 Lite [platina]

{
"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 11 (R) 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 still includes 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 Gerrit Code Review. You can also view the Changelog for a complete list of changes & features.
Recommended firmware
V12.0.3.0.QDTMIXM
Note: This ROM uses FBE encryption, any current existing recovery won't be able to decrypt data!
Downloads
Here
Flashing instructions
Here
Sources
ROM sources: LineageOS
Kernel sources: Here
Happy modding!

Reserved

Glad to welcome you devs

Hey @SebaUbuntu,
First of all, thank you for your efforts
I've a few things I'm stuck at, you or someone else hopefully can help me with.
I flashed it with a data partition, encrypted from Android 9. As expected, it refused to boot and going back to the recovery my data partition was garbled.
Formatting it let me boot fine. I then was surprised, to see the storage as encrypted again in settings.
Trying a reboot to recovery I can't manage to get in. All Recoveries I tried, are stuck on the splash screen.
I tried the Pitchblack, OrangeFox, TWRP and SkyHawk recoveries, but it's the same with all of them.
Is there a working recovery that is able to decrypt the data?
Additionally, I setup a lockscreen Pin, but never got asked if I wanted a secure boot. So I'm unable to use a custom pin for the encryption key, which makes it somehow pointless to encrypt in the first place.
How can I solve that?
I want to use the phone without GApps. Instead I plan on using MicroG, which needs signature spoofing.
My old way using Riru Core, Riru EdXposed and the XposedModule FakeGapps to enable signature spoofing doesn't work anymore sadly.
Would it be possible to add a signature spoofing patch to your builds?
TL;DR:
- Is there a Recovery, able to decrypt the data partition encrypted from your rom?
- I can't set my lockscreen pin for a 'secure start', is that a bug or desired behaviour? (And if so, why? )
- Could you enable signature spoofing in your builds please?
Regards,
L

@9Lukas5 Have you tried https://files.sebaubuntu.me/Recovery/LineageOS-Recovery/platina/ ?
I had similar issue with my Mi8 dipper when I upgraded from official Lineage 16 to 17. Twrp wouldn't decript, it turned out the /data mounting dev path was different and twrp couldn't find it. I lived with it for a while until twrp got an update. During that time, I had to use sideload to update Lineage OS.

@haoquan thanks for this tip, I'll save this definitely for the next attempt
I've restore my LOS16 setup for now to have a working phone, as my Setup relies on working Signature Spoofing + MicroG^^.
If someone knows a solution for the Signature Spoofing and custom encryption pin, I'd be pleased to try another upgrade.
In the mean time I'll try to compile an updated LOS16 build using the device parts of this rom (hopefully this will work, otherwise I'll have to find Pie compatible device parts first )
L

Thx sir, for u working.

9Lukas5 said:
Hey @SebaUbuntu,
First of all, thank you for your efforts
I've a few things I'm stuck at, you or someone else hopefully can help me with.
I flashed it with a data partition, encrypted from Android 9. As expected, it refused to boot and going back to the recovery my data partition was garbled.
Formatting it let me boot fine. I then was surprised, to see the storage as encrypted again in settings.
Trying a reboot to recovery I can't manage to get in. All Recoveries I tried, are stuck on the splash screen.
I tried the Pitchblack, OrangeFox, TWRP and SkyHawk recoveries, but it's the same with all of them.
Is there a working recovery that is able to decrypt the data?
Additionally, I setup a lockscreen Pin, but never got asked if I wanted a secure boot. So I'm unable to use a custom pin for the encryption key, which makes it somehow pointless to encrypt in the first place.
How can I solve that?
I want to use the phone without GApps. Instead I plan on using MicroG, which needs signature spoofing.
My old way using Riru Core, Riru EdXposed and the XposedModule FakeGapps to enable signature spoofing doesn't work anymore sadly.
Would it be possible to add a signature spoofing patch to your builds?
TL;DR:
- Is there a Recovery, able to decrypt the data partition encrypted from your rom?
- I can't set my lockscreen pin for a 'secure start', is that a bug or desired behaviour? (And if so, why? )
- Could you enable signature spoofing in your builds please?
Regards,
L
Click to expand...
Click to collapse
- This ROM uses FBE, Secure Boot is a FDE thing, the ROM will now "encrypts" always
- See 1
- No, I want to be compliant with LineageOS, I won't add anything additional to what it provides

SebaUbuntu said:
- This ROM uses FBE, Secure Boot is a FDE thing, the ROM will now "encrypts" always
- See 1
- No, I want to be compliant with LineageOS, I won't add anything additional to what it provides
Click to expand...
Click to collapse
Ok, so if I get this right, this is no bug that Android doesn't offer me a secure start anymore setting a lockscreen pin?
Maybe a bit offtopic, but if the storage can be decrypted by a default password that's not changeable, how is the data security provided?
Edit: Google FBE <-> FDE quickly.
So this means, a "secure start" is always provided automatically, if I set some sort of lockscreen security and the personal files will be accessible only after first unlock after a reboot?
Can you confirm if the recovery from your domain @haoquan linked above will work with the LOS18.1 encrypted data?
Regards,
L

9Lukas5 said:
Can you confirm if the recovery from your domain @haoquan linked above will work with the LOS18.1 encrypted data?
Click to expand...
Click to collapse
fyi, LineageOS Recovery doesn't support data decryption

SebaUbuntu said:
fyi, LineageOS Recovery doesn't support data decryption
Click to expand...
Click to collapse
Yeah discovered this by now^^
That means there's no way of making a nandroid backup before altering around with updates, etc right now :/
But huge thanks for bringing up this rom. Thanks to your work and fully linking the device repo's, I were able to make a private build including the MicroG patch which is mandatory for me. So I finally switched from Pie, which was a rather old build by now.
What I found/would give as feedback so far:
- Video recording doesn't work (gives a green imaged video).
Tried with the built in camera and OpenCamera, both are the same.
L

I have stuck to Havoc 3.9 for past few months. Tried the latest Colt OS but on my Mi 8 lite at least it led to very erratic responses on fingerprint sensor, so I switched back to Havoc. Anyone actually used Lineage 18.1 on theirs and offer any feedback please?
Pros/cons vs Havoc pls

Thanks for this room, I see that the effort has been very gratifying.
I have a problem in the use of the camera, it does not allow recording the images
or videos to the internal or external memory, thanks if you can verify and correct this big problem I would be very grateful.

TheDon13 said:
I have stuck to Havoc 3.9 for past few months. Tried the latest Colt OS but on my Mi 8 lite at least it led to very erratic responses on fingerprint sensor, so I switched back to Havoc. Anyone actually used Lineage 18.1 on theirs and offer any feedback please?
Pros/cons vs Havoc pls
Click to expand...
Click to collapse
I'm using it since ~a week. It's fully stable for me so far
Basically everything except video recording works for me.
Android 10 roms had all the same bug blocking me from switching, that I couldn't playback my music sadly (aac, mpeg4-audio container), that's working fine here.
So I can't give you much of a comparison review, other than that
lewismsc said:
Thanks for this room, I see that the effort has been very gratifying.
I have a problem in the use of the camera, it does not allow recording the images
or videos to the internal or external memory, thanks if you can verify and correct this big problem I would be very grateful.
Click to expand...
Click to collapse
What camera do you use? I'm using OpenCamera, set to use Camera2API and take pictures. Just video recording takes a green image all the way through
L

9Lukas5 said:
I'm using it since ~a week. It's fully stable for me so far
Basically everything except video recording works for me.
Android 10 roms had all the same bug blocking me from switching, that I couldn't playback my music sadly (aac, mpeg4-audio container), that's working fine here.
So I can't give you much of a comparison review, other than that
What camera do you use? I'm using OpenCamera, set to use Camera2API and take pictures. Just video recording takes a green image all the way through
L
Click to expand...
Click to collapse
Good afternoon, flash the rom I use the camera that comes with the same rom and install several additional ones and there is no way I can save the photos and videos that I make with this or another camera. I like the rom, but if I can't use the camera, I fail

9Lukas5 said:
I'm using it since ~a week. It's fully stable for me so far
Basically everything except video recording works for me.
Android 10 roms had all the same bug blocking me from switching, that I couldn't playback my music sadly (aac, mpeg4-audio container), that's working fine here.
So I can't give you much of a comparison review, other than that
What camera do you use? I'm using OpenCamera, set to use Camera2API and take pictures. Just video recording takes a green image all the way through
L
Click to expand...
Click to collapse
I used this rom and it seems better than the original rom, it is quite stable, but for me it is essential to use the camera for both photos and videos and voice recording

@lewismsc Do you know which firmware you're on?
I'm using the V10.3.2.0.PDTMIXM right now.
@SebaUbuntu could a too old / too new firmware cause these different experiences and is there a recommend firmware version for your rom?
L

9Lukas5 said:
@lewismsc Do you know which firmware you're on?
I'm using the V10.3.2.0.PDTMIXM right now.
@SebaUbuntu could a too old / too new firmware cause these different experiences and is there a recommend firmware version for your rom?
L
Click to expand...
Click to collapse
It is recommended to use V12.0.3.0.QDTMIXM

Hi all, thanks for all the advice on what is still a very good phone. I have managed to change the firmware to V12.0.3.0.QDTMIXM MIUI via Mi Flash tool, but when I try to send TWRP recovery (tried several) in fastboot, it says its sent the recovery, but there is no root and fastboot does not go back into main TWRP screen. Never had an issue using firmware 10..3.2. I was using Havoc 3.9 custom rom for a good few months. Also tried Orange Fox & PitchBlack with same result.
Keen to try this lineage 18.1 rom, but I'm stuck.
Grateful for any advice please, as MIUI 12 has its limitations. Can't even get Whatsapp notifications at top of screen!
Thanks

After a good few hours over past few days of frustration, I realised I simply need to press Volume Up on phone when entering fastboot reboot command after successfully flashing TWRP recovery (3.3.1 I tried) ...at long last I can restore my backup from 14 Jan of Havoc 3.12 rom !