Dirty Flashed Lineage 14.1 us996 on Verizon vs995 = Success - LG V20 Questions & Answers

So I've been really wanting something with the February security updates to patch the PNG vulnerability. So I bought a used (like new) vs995 on eBay for ($109) .. downgraded it and unlocked the bootloader. Yesterday I flashed Lineage OS 14.1 for it but today I see they released all the new Lineage 14.1 roms for the v20 but they deleted the vs995 section (The last update it had was December 2018).
So I downloaded the us996 rom unzipped it and in META-INF\com\google\android\updater-script
replaced everything on this line that said us996 with vs995 this way, it wouldn't bomb out when trying to flash it via TWRP saying it's incompatible.
Before
assert(getprop("ro.product.device") == "us996" || getprop("ro.build.product") == "us996" || abort("E3004: This package is for device: vs995; this device is " + getprop("ro.product.device") + ".");
Click to expand...
Click to collapse
After
assert(getprop("ro.product.device") == "vs995" || getprop("ro.build.product") == "vs995" || abort("E3004: This package is for device: vs995; this device is " + getprop("ro.product.device") + ".");
Click to expand...
Click to collapse
I rezipped it with 7zip, dirty flashed it and after about 10 mins or so the boot process had finished.
All of the following works
Making calls
Receiving calls
Text messaging
Mobile Data (Speed tested it and was only getting 1.8 - 2 megs, the bar says LTE, so not sure if it's a signal issue since I don't really know what normal is seeing as I don't use mobile data hardly at all.
Camera
Wifi
Bluetooth

yeah, the vs995 and us996 are 99% identical, only difference seems to be in the software and bootloader, and maybe tiny modem differences ( but the vs995 and us996 modem seem to be the most similar to each other). Also, lineage 15.1, although still unofficial, is pretty stable and has everything working that lineage 14 does ( and can be dirty flashed from 14.1 as long as you also flash to-x86cpu.zip which is in the same place as the 15.1 downloads and updated google apps ) (although the IR blaster might not work consistently until you flash gamma kernel)

Phoenix591 said:
yeah, the vs995 and us996 are 99% identical, only difference seems to be in the software and bootloader, and maybe tiny modem differences ( but the vs995 and us996 modem seem to be the most similar to each other). Also, lineage 15.1, although still unofficial, is pretty stable and has everything working that lineage 14 does ( and can be dirty flashed from 14.1 as long as you also flash to-x86cpu.zip which is in the same place as the 15.1 downloads and updated google apps ) (although the IR blaster might not work consistently until you flash gamma kernel)
Click to expand...
Click to collapse
I was going to go that route, but it still had security updates from December 2018. I'm not even really concerned with Root, I just want security updates. Now I'm aware there is security with other aspects of a phone such as a modem and other firmware. But at a minimum, I would like the latest Android Security updates.

Related

Sense 3D App Switching Theme to CM9 KF?

Just saw this over in the general Android forum:
[MOD] [ICS] [CM9 only] Advanced Multitasking for CM9 / HTC Sense Like
Someone compiled the project for CM9 and is verified as working on a Galaxy S. I may get brave enough tonight to give it a shot on my KF running the latest Energy ROM...after a full backup, of course.
Boo...FAIL. I knew it was a longshot.
Tried using TWRP to flash it, then tried CWM, as well. Both fail on the model asserts in the "updater-script":
Code:
assert(getprop("ro.product.device") == "galaxysl" ||
getprop("ro.build.product") == "galaxysl" ||
getprop("ro.product.device") == "GT-I9003" ||
getprop("ro.build.product") == "GT-I9003");
So there appears to be a model specific failsafe built into the installer script. I guess I'll try deleting the reference and see if anything scary happens. LOL.

LineageOS Official support for T-Mobile

As the title implies, there is official nightly support for Tmobile variants on the LineageOS website located here: https://download.lineageos.org/h918
I will say though I ran into an annoying ass TWRP bootloop after trying to let lineage do an update from settings on TWRP 3.0.2.1 >> BE WARNED << Just download updates from the website and do updates manually in twrp and all will be fine.

Problem in start Lineage 15 Unofficcial

Hello for all,
Today I tried install this version:
https://www.androidfilehost.com/?fid=817550096634798271
I had the first problem, ins't possible check the model number (Ex. XT1640), so I fix this excluding these lines:
assert(getprop("ro.product.device") == "athene" || getprop("ro.build.product") == "athene" ||
getprop("ro.product.device") == "athene_f" || getprop("ro.build.product") == "athene_f" ||
getprop("ro.product.device") == "xt1621" || getprop("ro.build.product") == "xt1621" ||
getprop("ro.product.device") == "xt1622" || getprop("ro.build.product") == "xt1622" ||
getprop("ro.product.device") == "xt1625" || getprop("ro.build.product") == "xt1625" ||
getprop("ro.product.device") == "xt1626" || getprop("ro.build.product") == "xt1626" ||
getprop("ro.product.device") == "xt1640" || getprop("ro.build.product") == "xt1640" ||
getprop("ro.product.device") == "xt1641" || getprop("ro.build.product") == "xt1641" ||
getprop("ro.product.device") == "xt1642" || getprop("ro.build.product") == "xt1642" ||
getprop("ro.product.device") == "xt1643" || getprop("ro.build.product") == "xt1643" ||
getprop("ro.product.device") == "xt1644" || getprop("ro.build.product") == "xt1644" || abort("E3004: This package is for device: athene,athene_f,xt1621,xt1622,xt1625,xt1626,xt1640,xt1641,xt1642,xt1643,xt1644; this device is " + getprop("ro.product.device") + ".");
After this I can flash normally, but the system don't started only keep in Moto logo.
Could you help please? I'm very, very ansious to try Oreo in my G4+.
Thanks in advanced!
Best regards,
Rodrigo Possi
I take it you wiped cache, data and Dalvik in TWRP before attempting to boot?
You may have to be patient otherwise, as LineageOS Oreo builds for our device is still in alpha stage, and though rahulsnair and Dreamstar and others are working on builds, in my view it's not ready for general usage yet from what I've seen.
echo92 said:
I take it you wiped cache, data and Dalvik in TWRP before attempting to boot?
You may have to be patient otherwise, as LineageOS Oreo builds for our device is still in alpha stage, and though rahulsnair and Dreamstar and others are working on builds, in my view it's not ready for general usage yet from what I've seen.
Click to expand...
Click to collapse
Yes, I did a clean install.
Well, the only way is awaiting... Can you share the links of Rahulsnair and Dreamstar? I know that have bugs (this is normal to happen), but I'm very interesting in try and I'd like help if posssible.
possi.rodrigo said:
Yes, I did a clean install.
Well, the only way is awaiting... Can you share the links of Rahulsnair and Dreamstar? I know that have bugs (this is normal to happen), but I'm very interesting in try and I'd like help if posssible.
Click to expand...
Click to collapse
Here's a handy post by strongst listing some of the current developments in progress with Oreo: https://forum.xda-developers.com/showpost.php?p=73657782&postcount=3
https://forum.xda-developers.com/showpost.php?p=73688028&postcount=2013 shows that Dreamstar and rahulsnair have managed to get L-OS 15 to boot, but as you can see, there's currently no mobile signal/RIL (no baseband detected), which is proving an issue for Invicta too (though Silesh managed to get Wi-Fi working ). https://forum.xda-developers.com/showpost.php?p=73690763&postcount=2016 is the most recent post from rahulsnair saying that the builds are still alpha (so subject to potential major/show stopping bugs) and will release when ready.
As I understand it, development is progressing (and pretty impressively, given that Oreo was released only a couple of weeks ago), and being based on Nougat, since Oreo source code isn't available for Moto devices at the moment. As for testable builds, keep an eye on those threads for testable builds...
possi.rodrigo said:
Yes, I did a clean install.
Well, the only way is awaiting... Can you share the links of Rahulsnair and Dreamstar? I know that have bugs (this is normal to happen), but I'm very interesting in try and I'd like help if posssible.
Click to expand...
Click to collapse
I would recommend to wait until a build is public and tested by a dev and not to install something you found on Afh with no description of current development stage. Nobody can help you atm...

Fingerprint in 9.0

So i tried to put a fingerprint lock on a 9.0 ROM but it seems it doesnt work. How to fix this?
Same here
It used to work in LOS 15. Is there anything that changed from 15 to 16? How to get fingerprint working again?
Lineage OS 16 works fine for me and unlocks with fingerprint. Have you tried that?
The fingerprint won't work with LineageOS 16 if you are using a baseband from Android Kitkat (ie: BNG3, BNJ1, ...).
There is a discussion about this in the project's gitlab page:
https : / / gitlab.com/LineageOS/issues/android/issues/241
The strange thing is I swear I saw a screenshot showing off LineageOS 16 when it was released for the SCL23 shows firmware BNG3, so the developer that took that screenshot also didn't have the fingerprint working.
The terrible thing about this is that Kitkat was the last baseband that could be sim-unlocked, so now we have to choose between running an old version of android / having a fingerprint sensor that works / being sim locked.
lameventanas said:
The fingerprint won't work with LineageOS 16 if you are using a baseband from Android Kitkat (ie: BNG3, BNJ1, ...).
There is a discussion about this in the project's gitlab page:
https : / / gitlab.com/LineageOS/issues/android/issues/241
Click to expand...
Click to collapse
I followed the instructions and am now on Baseband G900FXXU1CQK3 which is the latest for Germany (DBT). The sensor still doesn't work
Any further ideas?
bigtreiber said:
I followed the instructions and am now on Baseband G900FXXU1CQK3 which is the latest for Germany (DBT). The sensor still doesn't work
Any further ideas?
Click to expand...
Click to collapse
Anybody got a working fingerprint sensor in LOS16?
bigtreiber said:
Anybody got a working fingerprint sensor in LOS16?
Click to expand...
Click to collapse
I'm still looking for a solution ...
Fingerprint Scanner S5 LineageOS 16.0
bigtreiber said:
I followed the instructions and am now on Baseband G900FXXU1CQK3 which is the latest for Germany (DBT). The sensor still doesn't work ...
Click to expand...
Click to collapse
Which instructions?
Did you update only the baseband or also the other firmwares & bootloader that are included in these packages?
All the modem/bootloader combos in S5 Odin Flashable Modem & Bootloader are matched pairs from stock Samsung firmwares.
Note that you need to swipe down starting from the bottom of the screen like in the screenshot.
If your fingerprint scanner is still not working you could flash the most recent stock Samsung firmware for your S5 to rule out a hardware problem.
The fingerprint scanner works fine on my Galaxy S5 G900M LineageOS 16.0 klte build 2019-07-05 + Open GApps Pico + LineageOS AddonSU.
***

[FIX][GSI][TWRP] Mi Max 3 ROMs

What is this topic about?
I've spent quite some time writing fixes for GSIs to work properly on our Mi Max 3.
As part of that, we now have a list of easily flashable fully working Mi Max 3 ROMs to pick from.
This topic will be used to keep track of all fully working ROMs and of course to host the latest set of GSI patches / flash templates.
Available ROMs:
These have been tested and confirmed fully working (sans ROM-specific bugs).
AOSiP
Build date: 2019-05-14
Patch date: 2019-05-17
Flashing guide:
Unlock your device's bootloader.
Flash nijel8's modded TWRP recovery.
Pick and download one of the available ROMs.
Reboot into TWRP recovery and flash your ROM of choice.
Go into TWRP's wipe menu and "factory reset" your device (aka. slide the bar).
Flash Gapps (Opengapps / Bitgapps) if your ROM of choice requires / you want it.
Reboot your phone and set it up to your liking.
How can I get my ROM of choice listed here?
Download the TWRP package template from here!
Grab a GSI of your choice and unpack the system image (if it is compressed).
Rename the unpacked system image to system.img and place it inside the system folder inside the template zip file.
Rename the resulting zip file accordingly, flash it, test it, and after you've confirmed everything's working fine, upload and share it.
How do I enable DT2W (double-tap to wake)?
Create a file named "enable_dt2w" (without the quotes) in your device's internal storage.
Reboot your device.
Changelog:
2019-05-17
Changed cpusets to 0-7 (UX gains)
Set rendering thread to schedule as FIFO (UX gains)
Updated AOSiP to its latest (2019-05-14) build
2019-05-10
Swapped firmware & vendor base to stable 10.3.1.0
Updated AOSiP to its latest (2019-05-07) build
2019-05-01
Added two touchscreen-related properties to build.prop
2019-04-30
Updated the kernel to ResurrectedKernel 5.0 (brings a whole bunch of new governors)
Changed default little core governor to alucard
Changed default big core governor to darknessv5
Updated AOSiP to its latest (2019-04-29) build
2019-04-22
Fixed a mistake on my end that made the screen flicker on brightness changes (sorry guys)
Updated the kernel to ResurrectedKernel 4.1 (kcal support!)
Updated AOSiP to its latest (2019-04-22) build
2019-04-21
Fixed the device fingerprint issue (Magisk users should now be CTS-verified by default again)
Added AptX & AptX HD Bluetooth support
Removed DotOS & PixelExperience from the rooster because the WiFi HotSpot function wasn't working properly in them
2019-04-12
Added addon.d support (which means dirty-flashes won't lose their Gapps, Magisk, etc. anymore)
Tested and added Pixel Experience to the roster
2019-04-10
Added ResurrectedKernel (Unlocks 1.8GHz on Little Core / 2.0GHz on Big Core)
Tweaked Governor to utilize ResurrectedKernel's frequency range fully
Updated DotOS bundle to latest build
Repacked all bundles with latest patch
Dropped "Minimal Package" support as its no longer maintainable in tandem with ResurrectedKernel
It ended up with the lags (AOSIP).
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Germano1980 said:
It ended up with the lags (AOSIP).
Click to expand...
Click to collapse
Where's the lag Germano? Works fine for me.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
Stuck how? If you have "unlock" trouble, as in, your PIN won't let you in, use the "Remove lockscreen" option inside TWRP to remove your previous lockscreen data.
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
MrColdbird said:
Where's the lag Germano? Works fine for me.
Click to expand...
Click to collapse
Before installing their zip, they had some lags in screen transitions and to slide and open apps. Now, everything got more fluid and faster. It was great ... until voLTE is working (and my operator informed me that my device was not compatible with haha).
---------- Post added at 19:14 ---------- Previous post was at 19:07 ----------
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
What vendor is your device on? Many GSI's only start at a particular vendor (Oreo or Pie).
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
Make sure the GSI you picked supports Pie vendors.
Not every GSI does... and the ones that are still stuck on Oreo vendors are... troublesome, to say the least.
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
The last time I had problems in booting the GSI roms I did the following:
1- I reinstalled the latest global version of Miui Oreo via miflash (Beware of ARB)
2- Logged in the Mi account, enabled the USB debugging and installation by ADB settings to install the TWRP
3- I installed TWRP (nijel8's modded), formatted the data and then installed xiaomi.eu
4- I configured the device and made a backup of xiaomi.eu
5- As I already had the files, I installed AOSIP, without deleting the system, just cleaning the data of xiaomi.eu
6- After the boot, I installed the gapps and magisk.
I never had any problems installing GSI's on my device.
When I was in Miui Oreo, I tested some roms that only boot the Oreo vendor (Bootleggers, PixelDust among others), but I think with the Oreo vendor they spend a little more battery life.
(hope this helps you)
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Masacci0 said:
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Click to expand...
Click to collapse
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Skyllery said:
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Click to expand...
Click to collapse
So if i install this rom https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/ i'm ok and without arb? I get confused because on the image they say mi max 3 has arb, if they mean the official 10.2 has arb, why even put the image in the .eu version? It just confuses people.
So i go with this rom reach setup screen, recovery and install the gsi rom?
Jesenican said:
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Click to expand...
Click to collapse
Try the xiaomi.eu versions from last month based on installing AOSiP. Today I tried with the versions of this month and did not boot.
I am having the exact same issue. I followed the guide and installed the latest xiaomi.eu 9.3.7 beta and boot no problem then i flash gsi .img and it gets stuck at MI Logo and wont go any further. I have tried latest xiaomi.eu beta, stable, last months, month before that. All xiaomi.eu boot fine without issue but as soon as I flash any gsi .img it gets stuck at MI Logo screen? Am I doing something wrong?
Also the gsi i am using is latest pixel experience arm64 A only.
Any help would be greatly appreciated.
Same. I tried 3 different GSI roms and kept being stuck on the mi logo... :'(
only aosp gsi works, still getting android.process.media and bluetooth crashes
Edit: instead of com.android.media it was android.process.media
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
jngiag said:
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
Click to expand...
Click to collapse
You're my hero! That did the trick. ;D
So can i normaly flash older xiaomi.eu version without fear of ARB?
OP post updated with a new package.
Changelog:
Tweaked the governor to boost properly and use the 1.6 / 1.8GHz maximum little / big frequencies. (Everything's even smoother now~)

Categories

Resources