Search results

Sad news for all of us that love privacy, but an understandable decision. With greatest respect, I commend your determination in sticking at it for so long despite all the complainers, constant changes in the underlying OS and frameworks, lack of collaboration from other project developers, and...

Can someone please help me get my head around what the issue with LineageOS is? I am still on A11/LOS18.1 at this point, I haven't been able to upgrade yet because I am unable to decrypt my data partition, no matter what I do. I was using pattern lock which didn't seem to be supported, so I...

Im using A11 (LOS 18.1). Maybe I will try OFR R11.1_2 and see if it works.

Hmm no luck unfortunately... i did wonder how a pattern might translate but i followed the mapping from that page and it still failed :-/ that guide is for android 6, would be surprising if it still worked i guess

Is there/will there be support for decrypting using unlock pattern instead of PIN or Password? I have LineageOS 18 installed but I cannot update currently because I use an unlock pattern but when I try to decrypt data the only option is to enter a password...

Just wondering, does this recovery support decryption using a pattern? I have PBR installed ATM, and have tried older versions of TWRP and OFR but it seems like they all will only ask for a password when trying to decrypt data...

Does this recovery support decrypting with a pattern, or is there any plan to implement it? I am going crazy trying to update LOS on my phone but it seems like no recoveries will decrypt if you have a pattern for screen lock...

Well, I seem to have solved the problem for now by switching to the latest LSPosed (1.3.5 5551), and maybe also by bumping the ROM to May security patch. Either way XPL now loads properly again. Slightly OT, I cannot get safetynet to pass tho so be aware of that. Even with universal safetynet...

I am getting the "module not running or updated" message in the XPL app, even though I have updated everything: Lineage 17.1 SELinux enforcing Magisk 22.1 Riru 25.4.4r426 EDXposed 0.5.2.2_4683 YAHFA XprivacyLua 1.3.0. EDIT: figured out why thread search was returning no results and found lots...

What's going on with this ROM? In first post it says final version was uploaded, but from recent posts it sounds like development is continuing?

Is selinux enforcing on this ROM?

Politicians?? ...what does that have to do with anything I said?

Is selinux enforcing? What flavour gapps is installed?

How so?

OK, I have been using EdXposed since I upgraded to Oreo, but I only just discovered LSPosed, and I don't really understand why LSPosed was created in the first place or why it seems like there is so much hatred between the different camps... I will say that I haven't really been happy with the...

Is selinux enforcing on this ROM? Also, which flavour Gapps is included (nano,aroma,etc)? Thanks

No you cannot pass safetynet. Magisk may tell you than it passes safetynet but it is basically lying, all it can do is forge local results. A real Safetynet check uses a cryptographicly signed API call to google servers which is physically impossible for a phone with an unlocked bootloader to...

Physically impossible, since android 9 safetynet trips automatically from an unlocked lootloader.

Awesome, installed this yesterday and so far has been smooth and stable. Got Magisk + EdXposed + XprivacyLua all working without hassle. SELinux enforcing too (seems to be rare on ROMs for this device). Just wanted to make sure there would be regular updates before I committed to running this as...

OGHyperion - will this ROM ever get SELinux enforcing?

Everytime I flash this I reboot into TWRP and it's fine, but after I reboot into system then back to recovery I get the stock recovery. I've also tried flashing TWRP, rebooting into TWRP, rebooting into TWRP again, then rebooting to system - still get stock recovery when next booting to...

How often are you planning to release new builds?

So, quick question - given that Nokia HMD has not released any source for this device (bastards!) where did you get this from?

Question about the kernel in this ROM - is it custom compiled or a nokia kernel?

31 May ans still no sign of an update here in Australia.... I do have unlocked bootloader and TWRP installed in the slot B, but OTA should still work AFAIK....

I feel your pain dude. My last phone was a oneplus 5T, which was a great phone until the touch screen just randomly stopped responding one day. The only fix was to reflashing stock, but it kept happening and eventually I gave up. Didn't want to blow hundreds of dollars on another oneplus after...

I decided to have a crack at building my own TWRP using kernel extracted from my current stock boot image (fw400), but unfortunately I have no idea what I'm doing :P So far I have cloned the device tree from https://github.com/TeamWin/android_device_nokia_DDV_sprout and replaced...

https://twrp.me/faq/encryptionsupport.html "Even if your device supports AOSP encryption and decryption, it usually requires custom blob support. The process of figuring this out may take time and may never be done. Some vendors such as Samsung use their own encryption techniques. Without heavy...

So, a couple of things: Linux kernel license is GPLv2. In theory, anyone who uses it is required by the terms to also publish any code they derive from it under the GPL, but the problem is that the only way to enforce this against a non-compliant vendor is court action by the owner of the IP...

Broken wifi is a known issue, mentioned elsewhere in this thread. Basically the Wifi driver won't load because the module is signed with a different key to the binary kernel TWRP is using (extracted from OTAs rather than being compiled from source because Nokia haven't released the code yet - I...

UPDATE - I managed to get Magisk installed using a patched boot image, but the process was very convoluted and I don't look forward to having to repeat it when the next firmware update comes down: 1. Install OTA update - slot B is now active. 2. Install TWRP to boot_a then boot to recovery 3...

Today I have tried installing TWRP on my TA-1196 model and I can confirm that WiFi does not work. I have updated to latest firmware (400 - January security patch) and I have used the most recent TWRP available on the download link - 20200129 (I also tried 20200126 from same directory). The phone...

What happened to the folder for August, doesn't seem to be on sourceforge anymore? Will the recovery from the 2019-09-05 folder work on firmware 130 (august 5 security patch)?

I guess not having decryption working isn't a show stopper - you can always sideload instead.

The factory installed firmware was version 00WW_1_130 with security patch from 2019/08/05. I specifically asked the store assistant to check the date they received their stock and requested one from their oldest batch which they got in August. If you want a phone without the new firmware...

Just got my 7.2 today and managed to unlock bootloader. Planning to stay on stock FW for now but I want to install Magisk for Xprivacylua. I've read this whole thread and it seems like there are a few issues so I wanted to clarify a couple of things before I take the plunge: Regarding issues...

Thanks for this tip, I just picked up one of these today - was able to get the store assistant to confirm the date they recieved them so I knew I would be getting an older one. Got it home and found it had the 1_130 firmware but the OEM unlocking option was disabled. Initially I had no SIM or...

Interesting... you know in all the instances I've read of people having issues with the touchscreen, I can't pin point anything consistent about it. Some people say a reboot helps, but it has never worked for me, neither has wiping cache and davlik. As I said, the only thing that works for me is...

I have been having persistent problems with the touchscreen on my 5T becoming unresponsive at random times for no apparent reason for a while now (see this This thread for more info there). I have found that when the touch screen stops responding, the ONLY thing that will get it working again...

Bugger it... I managed to get to 4 days or so after flashing back to LOS 16.1 / Magisk 19.3 / Edxposed YAFHA / Franco kernel, but it has just crapped out on me again. This time I has tried a slowly-slowly approach, at first running just the stock OS and apps for a few hours, then gradually...

I'm not running OOS now, but I have had the issue occur while I was. I am just re-flashing OOS to get the touchscreen to work again, but actually I can't even get the setup wizard to work once the phone boots (hangs on the "just a sec" screen), so I am usually flashing another custom ROM once...

No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....

I thought I had solved the problem by installing the RenderZenith kernel, which someone on the oneplus forums recommended in the thread there dealing with this issue... but it has resurfaced after a couple of months without issue. Rebooting does not fix the issue for me, I have to flash a stock...

Looking for a new phone to replace my Oneplus 5T. I don't want another Oneplus as the reason I'm ditching the 5T is due to the touchscreen randomly becoming unresponsive such that the only thing that fixes it is flashing back to the stock ROM. LineageOS is my preferred ROM but I am open to any...

Long story short, I am looking for a new custom ROM. I have been using LineageOS for a long time as I had a fairly high degree of trust in their dev team, but recently I have been having an issue where the screen stops responding to touch and the only thing that will fix it is reflashing a stock...

I'm not sure about that, the first time I had the issue appear I was still running oreo, as I mentioned, I hadn't updated anything in months due to the lineage nightlies switching to Pie.... That said, certainly seems like most people who have reported it mentioned upgrading to Pie

I've recently had the same problem, I was still running Lineage 15.1 and had not updated my firmware in months because the official builds switched to 16, then suddenly 2 weeks ago the touch screen stops responding while I was actually using it. Reboots didn't help, clearing cache and flashing...

So I haven't updated since May... checking here seems like quite a few people have been having issues with the recent builds. I don't want to the hassle of dealing with ANOTHER full wipe and reflash after what should be a routine upgrade goes south... am I going to regret it if I update to this...

Yeah I am getting an error saying the folder has been deleted due to ToS violation.

Question - will this work coming straight from Lineage 14.1, or do I need to go back to stock oreo first?