[VK810] [altev] [CM13] Invisiblek's Unofficial - Update from Invisiblek post #28 - G Pad 8.3 General

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.

Related

[Q] About Defy+ & CM11

I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS
System + data + cache wipe, use core gapps 2-26. If you encounter issues, then again install rom after full wipe, but don't install gapps immediately. Reboot, and delete unwanted system apps to free up space, and then flash gapps and wipe cache
No easy way to backport safestrap (replacement for boot menu)
Sent from my MB526 using Tapatalk
johnaddams83 said:
I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS
Click to expand...
Click to collapse
do not use standard gapps..system partition not big enough to store standard gapps..install core gapps

New User - CyanogenMod Questions

Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
dude...I just got the N6P and ran CM13 within hours. This is what I did...
unlocked the bootloader
downloaded the lastest (MTC19X) image off of https://developers.google.com/android/nexus/images and unpacked it into the C:\Program Files (x86)\Android\android-sdk\platform-tools folder
ran the flash-all.bat
fastbooted TWRP
installed CM13. (didn't wipe internal storage)
installed arm64 open Gapps pico
BAM!!!
right now running stock kernel. it's cool. I'm PrivacyGuard-ing the hell out of all my apps (turned off START AT BOOT and KEEP AWAKE for almost every downloaded app), though, so battery is OK
also using Kernel Adiutor but underclocking values for the CPUs doesn't seem to stick
So it likely worked for you since you had flashed the newest vendor.img first. Apparently there are compatibility issues with certain features that cause them not to work (such as WiFi) if you're using an older one.
chaoticyeshua said:
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
Click to expand...
Click to collapse
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
kaufikauf said:
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
Click to expand...
Click to collapse
Very much so. I appreciate it!
Has anyone encountered the constant popup of the Select Sim Card message? I'm using project fi and I am still unable to find a solution to this issue.

Need help getting LineageOS to be stable (15.1 UNOFFICIAL, hltevzw, TWRP 3.3.0)

I have an SM-N900V (Note 3, Verizon variant, hltevzw).
Detailed timeline:
- I flashed it back to firmware OB6 using Odin 3.09.
- I rooted it using ArabicToolApp.
- I used this tool to unlock the bootloader
- I installed a build of LineageOS 14.1 for hlte
- It didn't recognize the SIM so I did a dirty flash of this build of LineageOS 15.1 for hltetmo on top (hltetmo actually has different hardware than hlte, and the correct one for SM-N900V)
- Messed around with the APNs until it recognized and connected to Verizon's network. I DO have functioning SMS and LTE data, but I have not tested phone calls yet
- Messed around some with SuperSU in system- and systemless-mode. Bricked my device more times than I could count, then unbricked over and over using SuperSU's impeccable installer. Messed around with this quite a bit
- Also messed around with Xposed some. The OS is too unstable to run Xposed Installer correctly, so I uninstalled it
- Removed SuperSU, installed Magisk. Phone now passes SafetyNet
So, my phone now runs 8.1 and a Lineage build from 9 days ago. Cool. But, if I was satisfied I wouldn't be making this post. There are multiple instances of the same kind of "app freeze" - App screen freezes, sometimes it'll go completely black. Interactivity doesn't work, obviously, the app is completely frozen. Hold Back to kill doesn't work (Application Killed toast shows, but nothing happens). ANR (when it comes up) Close doesn't work. Home button works and brings me away from the app, but it's still there. Swipe away in Overview doesn't actually kill the app. Even in App Info, Force Stop doesn't work. The app is forever frozen. Tapping the icon from the launcher no longer does anything, it doesn't even bring up the app. The app is permanently crashed and inaccessible until a reboot.
Issues:
- Sometimes when booting the phone will not recognize the SIM until a reboot. As in, "No SIM" message and everything
- Sometimes it will get stuck at boot, I have foxy-boot installed, so I can see the logs. I don't remember what it was all about, if it comes up again I'll update the post
- Google Chrome sometimes crashes when trying to download a file. I've gotten my phone to self-host before, but this issue always seems to come back, and when it does Google Chrome ALWAYS crashes when trying to download a file. App Freeze
- Netflix installs and logs in but freezes at the "can't connect to service (-9)" message. App Freeze
- Certain apps like NativeScript Playground get stuck at the splash screen. App Freeze
- Xposed Installer did this when opening the Settings, whether Xposed was installed or not. App Freeze
- F-Droid also sometimes crashes, although it's somewhat arbitrary, I can't reproduce it reliably. App Freeze
I have tried reflashing the ROM, flashing Xposed uninstaller, reinstalling Magisk, none of it seems to work. I have TWRP 3.3.0 so I can do pretty much anything that doesn't involve the SD card (the SD card is probably broken in hardware, it's so read-only that Android and TWRP both can't write to it at all, but they can both read the same half-broken filesystem).
I fear that this OS is just too unstable for the phone and there's nothing I can do. I sincerely hope this is not the case.
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
terminator911 said:
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
Click to expand...
Click to collapse
I did a clean installation of RR 6.0.0 (Android 8.1) and it works a lot better than LineageOS did, with even more configuration options. I really really hate Pie and its gesture-based gimmicks (Screw you Google for copying more of Apple's bad design decisions), so I assumed Oreo would be more stable, but the ROM I installed still has crashing apps. Google Chrome still won't download most things (I've gotten it to download before), trying to change the accent color crashes the 'LineageOS Settings' app, and F-Droid is seriously messed up, but most other things are stable, including the Verizon network which required no pesky APN setup.
I'm on the OB6 bootloader/modem, is that a problem? I doubt that would be an issue, but I can always back up and reflash via Odin. The cool thing is that I installed a patch to TWRP which backs up /data/media along with everything else, after installing the custom ROM. So, really, I can do anything and be perfectly fine. There's, AFAIK, no way to ruin the phone unless something exploits the eMMC brick bug.
If there's another ROM you'd recommend me install, I'd be happy to try it out. I would really like to have a stable OS on here, where Chrome will work and download files. I'd also love Camera2 API since the phone has the chip for it (Snapdragon 800), but none of the ROMs I have support it and there's been no discussion online other than some years-old threads with no answers. I know there have been some articles online listing Note 3 as a phone that'd support Camera2 API with a software update. Would updating the bootloader/modem do anything on that front?
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
terminator911 said:
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
Click to expand...
Click to collapse
Excuse me but custom ROMs don't have "the Samsung Internet browser". Additionally the modem shouldn't cause app crashes (if it does, correct me please).
I might try the Nougat ROM. Bluetooth calls don't matter to me, but stability does. I just kinda really like Oreo and all its customization options but it may be too new for this old phone from 2013. It still works as a phone though, Messages and phone calls work fine, so I may just deal with it.
I use Open Camera, and I've tried multiple Camera2 API enablers. The phone has a Qualcomm Snapdragon 800 and the necessary links (in hardware, between the camera/other things) to support Camera2, but nobody seems to have tried it. Probably because the Verizon Note 3 is really locked down, and can only be rooted on a special version of the samsung ROM, and can only be bootloader-unlocked via the eMMC brick bug... There are Magisk modules for Camera2 on Exynos-based devices, but none for the Verizon Note 3 AFAIK.
I just found out that RR 7 officially supports `hltetmo`, but RR 6 doesn't. That's kinda sad, I hate Pie, but I might try it...
I've had the SEPL stuff before, that's the one that can't be rooted. I suppose I didn't consider upgrading again after I unlocked my bootloader. I'll try SEPL1 firmware again, but with a custom ROM...
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
terminator911 said:
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
Click to expand...
Click to collapse
Yeah but, data and calling worked fine on the LineageOS and RR roms, so there's no reason to update the modem.
Besides, I flashed SEPL1 6 times using Odin (multiple times by flashing, rebooting directly into download mode and flashing it once more) and it doesn't want to update. Still on OB6. On the latest (official Pie) RR rom, data worked on first boot but doesn't work anymore (I'm going to mess around with the data settings until it works), but I have no reason to believe that my phone needs a modem update to function.
I did, many times, make calls to various phone numbers and they all worked flawlessly. SEPL1 is therefore not needed if that's all it does.
And I do know about all the Resurrection Remix versions: One is Nougat from their archive, one is the Oreo version I had installed just yesterday before flashing Pie, and the other one is Pie which is now officially supported.
I am currently working on getting RR7 to work, it's only crashed a few times, and I don't even remember what those times were (I think it was using the Back button in Overview/Recents at the same time as the Overview button?)
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
terminator911 said:
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
Click to expand...
Click to collapse
"pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot"
So...
- Reboot phone into Download mode
- Pull battery while in Download mode
- Flash thingy
- Reboot back into Download mode
- Flash thingy again
? That will be very difficult to do with my dodgy charging cable that doesn't like being repositioned...
I do that without pulling the battery, but I could try it with.
I'm downloading the full SEPL stock image to flash. Once that's done, I'll flash it, reflash TWRP, restore my backup, and see if the baseband has updated.
And no, never dirty flashed the ROM. Always completely wiped data, system, cache and everything. I always backup first. I currently have 3 backups: Lineage OS (before installing RR), RR6 (Oreo), and RR7 (right now before that stock image I'm going to flash).
My external SD card is nonfunctional and read-only with some trash files from the previous phone.
I flashed the stock SEPL ROM. Baseband still didn't change. Restored from backup, SIM now works. Network is detected, SMS and data both work reliably on all reboots.
I will mention that I did brick my phone by using Odin to erase the eMMC, but I fixed that from TWRP, and now everything works flawlessly. There are still some app crashes, but most things are very stable. Camera2 API still nonexistent, which is sad because I got used to it on my old phone, but I shouldn't hope for it.

UNOFFICIAL LineageOS 17.1 "SeLinux enforce mode" (Samsung Galaxy S6 - SM-G920F)

UNOFFICIAL LineageOS 17.1 "SeLinux enforce mode" (Samsung Galaxy S6 - SM-G920F)
Note:================
Tested ==> Samsung S6 (SM-G920F)(Zerofltexx)
========================
LineageOS is an operating system for smartphones, tablet computers, and set-top boxes, based on Android with mostly free and open-source software
All the source code for LineageOS is available in the LineageOS Github Repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
I've built this operating system with select userdebug .
It's unnoficial LineageOS17.1 for Galaxy S6 (ZEROFLTEXX)(SM-G920F).
I strongly recommend to perform a backup of your current rom before installation.
Tested ==> Samsung S6 (SM-G920F)(Zerofltexx)
SeLinux run in enforce mode,
also you can opt to have SeLinux run in permissive mode.
Installation process from stock rom
01. Boot into the download mode.
02. flash TWRP with Odin (comes in AP). The hooks at Auto Reboot and F. Reset Time out.
03. disconnect USB cable after flash, battery out and in again.
04. boot into recovery -> Allow Modifications
05. Advanced Wipe: Dalvik/ART Cache, System, Data, Internal Storage, Cache (lasts a while)
06. install -> select lineage image, then add more zips and gapps, then flash
07. patching system image unconditionally runs through with progress bar
08. Open Gapps are flashed, progress bar runs through
09. when done, tap reboot system, Swipe to install TWRP app (or not, if you don't need it)
10th reboot
11. Lot 17.1 boots. (quite a while ^^)
12. type through the facility
13. ready
Download:
==> tajaribsoft-en.blogspot.com/2020/09/unofficial-lineageos-171-samsung-galaxy.html
Because i'm new , i can't create link
Hi gapps included in ur ROM?
And can I install other boot.img files? I have tried that.
I know it won't work but a question..
Still will download and test..
---------- Post added at 07:25 AM ---------- Previous post was at 06:32 AM ----------
Almost everything works except Volume control while calling the same problem on 17.1 ROMs but everything else works fine I can just adjust volume from my file I'll just patch it with profile text lol thanks.. Very nice work ??????☎?
Yup this is my other account here.
and only on my laptop..
But i managed to get my favourite Kernel to be installed thanks to this beautiful work and kernel i installed is enforced and my ( favourite Kernel )
is pemissive so it depends on kernel and i don`t give a f... nice work man.. Thanks..
I can`t say thank you enough because i have tried other roms to get my thing install`d lol THANK YOU..
Are there any issues with audio on incoming or outgoing calls? Did you manage to get both the front and back cameras working? Most other custom roms have a combination of issues there.
EDIT: I just noticed Johannes did mention a call volume issue
add support 925f zeltexx pls
AnErare said:
Are there any issues with audio on incoming or outgoing calls? Did you manage to get both the front and back cameras working? Most other custom roms have a combination of issues there.
EDIT: I just noticed Johannes did mention a call volume issue
Click to expand...
Click to collapse
It has that same sound software problem.
But I think everything else is working. I try to restore boot from my previous backup it works but (sim not showing).
I try to restore other backup stuff but, of course did not working.
But it amazing i can use other kernel just by restoring from backup
They might be better ways to use other Rom's kernel.
I will use it like that soon without any possibility to have Sim card
I like my kernel lol..
This phone ( I ) use is near death so let end it Battery life with that Kernel I use... Lol
I'll test permissive only file download soon and try to restore boot from backup. And see
Or I should try to install Boot.img from the zip
Edit: It didn't work but first with enforcing SE always boot up no matter what i restore from my backup boot/cache/data/efs. I didn't test other rom enough yet.
And I will test more soon for fun..
Btw.. I got 3 mods installed on my backup so I'm gonna have to test new install's from all rom's and re-test from all over.. Or from start lol..
I want to know you guy's have any mods to make system faster or battery-friendly mods
I have added some text to build.prop and installed 3 mods I think. Maybe not all installs patches:
First for Fullscreen Gesture (Q) from Magisk modules.
Because my ROM is old and I removed some system apps.
And then I install kernel mod from this site. Lol (kTweak) it can be seen from Magisk
And 1 patch from here XDA post few days ago
And my build.prop tweak it looks funny:
ro.min_pointer_dur=0
ro.max_pointer_dur=40
wifi.supplicant_scan_interval=9000000000
windowsmgr.min_events_per_sec=0
windowsmgr.max_events_per_sec=60
debug.sf.nobootanimation=1
logcat.live=disable
ro.media.enc.jpeg.quality=100
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.mot.eri.losalert.delay.delay=1000000000
ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
persist.android.strictmode=0
ro.config.nocheckin=1
That it if I didn't forget something
And make Settings less cpu hog or how to say make it CPU friendly lol .
1 more thing I have edited Sound mixer from System files
You can search it on my comments on my other account Johannes Davidsen
On Enezusun's 17.1 Lineage Os Multitarget rom
I couldn't post attachment's so I have to copied text
That all.
Here, there are 3 sections i think : https://forum.xda-developers.com/showpost.php?p=83187603&postcount=310
This ROM has still the sound volume issues, but camera is working here, right?
This one https://github.com/enesuzun2002/lineageos-ota/releases (28. Feb build) has working call volume and also working cameras, right?
The 13. April build of it has sound issues again and fast battery drain?
It's hard to keep track of what's working in each ROM build and what's not.
About Enes ROM
0x0rbit said:
This ROM has still the sound volume issues, but camera is working here, right?
This one https://github.com/enesuzun2002/lineageos-ota/releases (28. Feb build) has working call volume and also working cameras, right?
The 13. April build of it has sound issues again and fast battery drain?
It's hard to keep track of what's working in each ROM build and what's not.
Click to expand...
Click to collapse
Why don`t you test them by yourself sometimes same device have different problem with same rom and it is very confusing..
For me all of them have working camera and all of them have, calling sound software problem that i just fix by editing sound file..
Have a nice day..
And yes cam is working on this new august build,
same on sound problem too
---------- Post added at 08:13 AM ---------- Previous post was at 08:02 AM ----------
AnErare said:
Are there any issues with audio on incoming or outgoing calls? Did you manage to get both the front and back cameras working? Most other custom roms have a combination of issues there.
EDIT: I just noticed Johannes did mention a call volume issue
Click to expand...
Click to collapse
For me cam is working, only problem i so is the same software problem when trying to lowèr volume on calling or say on earpiece i`ll just replace sound file with the file i already have edited but it is very low.
You can test it i have commented on Enesuzun`s rom i think it started on page: 31 or 32 there are 3 comment sections i use for text
Here: https://forum.xda-developers.com/ga...ageos-17-1-t4053959/post83187603#post83187603
good
Nice work. Thanks for that selinux enforcing rom. Unfortuately I cannot enable encryption. After set in security settings the boot in a bootloop.
schlombie said:
Nice work. Thanks for that selinux enforcing rom. Unfortuately I cannot enable encryption. After set in security settings the boot in a bootloop.
Click to expand...
Click to collapse
I have exactly the same problem. And are there any other things to do to make the device even more secure? Some Modules ?
bemek01 said:
I have exactly the same problem. And are there any other things to do to make the device even more secure? Some Modules ?
Click to expand...
Click to collapse
My dirty trick to enable encryption was, I installed e rom for the device. Enabled encryption without a pin direct after the installation.
Than I installed the 17.1rom without format data. Only wipe system, data and the caches. The rom boot up allready encrypted.
I only set a pin and thats it.
hello or a little problem with the download link, just don't have the link, can you try s create a link on mega or google drive ???
to another thing i wanted to say, i am surprised that you are creating a rom for android 10 with the SElinux Enforcing, i wanted it a lot to increase the security, but the problem of this that lead to lose some battery, however i am interested to try this rom on my samsung galaxy s6 SM-920F i just have to understand where the link lol.
in my opinion, however, thanks to the rom with the SElinux Enforcing maybe this rom could become official if you want, and put on the lineage os website, but honestly I don't know how it works, this is just my opinion
I wanted to say another thing, that second it was better to do lineage os 16.1 because it is much more stable for this device, in fact existing official resurrection remix with android 9 that I use that not a bug, or tried official evolution x with android 10 but the problem of the wi fi that turns off and that you can disable it on the lock screen, and this and these 2 are a big problem, and that problem also exists in the lineage os 17.1 of another creator, everything to see if in the future when there will be lineage os 18.1 for this device with android 11 maybe the wi fi and lock screen security will work prevent you from turning off the wi fi from the lock screen
i am using google translator, hope the translation is right
schlombie said:
Than I installed the 17.1rom without format data. Only wipe system, data and the caches.
Click to expand...
Click to collapse
A wipe basically formats a partition, so what exactly do you mean, that you wiped the encryption too?
I'm sure this ROM doesn't support whatever encryption /e/ may support that you're suggesting.
But maybe I've got this all wrong
schlombie said:
My dirty trick to enable encryption was, I installed e rom for the device. Enabled encryption without a pin direct after the installation.
Than I installed the 17.1rom without format data. Only wipe system, data and the caches. The rom boot up allready encrypted.
I only set a pin and thats it.
Click to expand...
Click to collapse
Thanks. It works for me.
I have one problem with this rom. Bluetooth headphones don't work. I can connect to the phone but the conection is unstable and stop working. it something like: connected, not connected , connected, not connected each 10 seconds or so.
Sorry for my English thanks a lot for your attention.
gerardomare said:
Thanks. It works for me.
I have one problem with this rom. Bluetooth headphones don't work. I can connect to the phone but the conection is unstable and stop working. it something like: connected, not connected , connected, not connected each 10 seconds or so.
Sorry for my English thanks a lot for your attention.
Click to expand...
Click to collapse
Someone please can explain to me step by step how do this trick for enable encryption ?
I've tried 6 times and nothing works maybe I'm misleading something.
Hi, i just wanted to ask how you compiled lineageos for the s6. I tried to compile los 17.1 with the files provided by enesuzun and have massive problems with lunch detecting the files. Many are missing and even if i collect all it just acts weird. Since enes provided many working images these file should work to compile, don't they? Do you know any good tutorial? Most of them are only either for official builds or completely new unsupported devices.
Thank you in advance.
Chasbrot
What gapps? opengapps is provided for 10.0 only...
I have LOS 16.0 from enes but wanted to give it a try.
After wiping (system, cache, data) and installing this rom with opengapps 10.0 and magisk zips,
the reboot stucked in boot loop.
szazs89 said:
What gapps? opengapps is provided for 10.0 only...
I have LOS 16.0 from enes but wanted to give it a try.
After wiping (system, cache, data) and installing this rom with opengapps 10.0 and magisk zips,
the reboot stucked in boot loop.
Click to expand...
Click to collapse
For LOS 16, which is Android 9, you have to use the OpenGApps for Version 9. You can download them at the OpenGApps Project Homepage.
Try one step at a time when flashing or try the newest version from enes.
Chasbrot said:
For LOS 16, which is Android 9, you have to use the OpenGApps for Version 9. You can download them at the OpenGApps Project Homepage.
Try one step at a time when flashing or try the newest version from enes.
Click to expand...
Click to collapse
Oh, I mean: what gapps does this ROM (17.1) need? (with opengapps 10.0 I got into bootloop)

[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 !

Categories

Resources