Search results

I did try to decrypt within TWRP itself after flashing as well.

Thats what I understand now. Even thoguh the system might not be using anymore. Any way I might access that still FDE-based data for backup purposes?

I did upgrade dirty from 18 to 19 but that was some time ago. I did run 19.1 fine and did no update on the system image. The only thing I did was flash the new recovery version and now I cannot boot anymore.

Hi there. I ran into the exact same issue Tremolo 4 stated updating from v3 to v4 and not being able to boot the system anymore. Apart from a clean flash is there any possible idea to revert the change coming from the recovery update? Same as Tremolo4 I did not update the system image (was on...

Flashing the zip doesn't help. It was indeed no clean install. But several system flashes were fine, only this update from TWRP v3 to v4 leads to the data partition not be able to be mounted anymore even though I switched back. Did the new version change anything regarding partitioning? I want...

That doesn't work actually. Same as system doesn't boot due to "wrong" pin, TWRP cannot mount the data partition. Thus /data/system cannot be accessed and those files cannot be removed. LOS is unable to mount data as well. The recovery log in LOS shows the following: [ 0.000607] 0 /data...

I cannot boot to system in order to remove the pin/pattern because the pin for booting to system is recognized as false after flashing the new V4 Recovery by REIGNZ. It says I have 8 tries left now :-( I tried flashing the V3 Recovery again and the LOS Recovery without changing the result. I...

Updated to the new TWRP version. I cannot decrypt the data in recovery. And now I cannot boot the system anymore, tells me the pin is wrong. Any suggestions?

Greetings. In combination with one of the last builds I reflashed gapps along with it (MindTheGapps-12.1.0-arm64-20220605_112439). Since then I cannot access the play store anymore. It says I'm offline. I tried clearing storage and cache of play store, play services, services framework or even...

Ghost touches appeared for me on 02.19 update and remain with this week's update. It is driving me nuts. For testing, can I simply switch between kernels by flashing them one at a time or do I have to pay attention to anything special? Especially, how can I switch back to the LOS default kernel?

Upgraded from 17.1 official successfully (lineage and gapps flash after dalvik and cache wipe). Had to reflash magisk. No problems so far. twrp 3.5.0, firmware 12.0.3.0.

Same thing happens on my device. Can anybody offer a solution?

Your apps are within the data partition, there is no need to reinstall (except for flashed system apps).

Upgrade with encryption from official 16.0 to 17.1 works flawlessly with twrp 3.3.0.0. Wipe System, Cache, Dalvik Flash FW 10.0.6.0 Flash LOS 17.1 Flash OpenGAPPS for Android 10 Backup is always recommended.

If I want to encrypt the phone my device reboots immediately after hitting 'encrypt phone'. For a very brief time the green android logo is shown. Am I missing something or is encryption not available at this state?

It's the other way around for me. OTA removes Magisk while manual flash triggers its survival script.

Deactivation and reactivation doesn't change anything. I performed a clean install on official release.

The navigation gestures are not working as I have expected with the official rom. Swiping up shows open apps, but a second swipe up does not open the app drawer. Additionally, long pressing the home button does not trigger anything (it should be google assistant by default). I recall being able...

I don't get it. Just updated via OTA after disabling modules. Still, addon.d doesn't run. Can the cause be the twrp version? I'm using 3.2.3-2 official.

To shift the status bar content below the notch area. The functionality LOS unofficial offers.

Nacho Notch does not offer the desired functionality.

I hope

The feature is missing.

Magisk survival doesn't work for me. Have to flash magisk after OTA.

The option is still there but it is lacking the entry "none" in contrast to the unofficial rom. I tried Nacho Notch but I cannot manage to move the content of the status bar below the notch area.

I cannot choose to hide the notch in developer options with the official build. Is this a bug?

Just tested the los updater (yesterdays build). No need to interact with the new twrp within the update process (manual data decription and zip install with OPs custom twrp). Treble support is given (vendor). One thing is bothering me nevertheless. Magisk needs to be reflashed since los updates...

Had the same issue. Solved it by uninstalling magisk manager and flashing magisk again in twrp. Gesendet von meinem Redmi Note 4 mit Tapatalk

Safety Net passes with Magisk (hide enabled) on this rom with unlocked bootloader. Gesendet von meinem Redmi Note 4 mit Tapatalk

I am still using Magisk v12 stable and can confirm SafetyNet working. (currently CoreOnly mode / playstore cache cleared) Gesendet von meinem Redmi Note 4 mit Tapatalk

Although a connection can be established using the sixaxis compatibility checker... (tested with 4.2.2 rom) I assume this also works with this rom.

Controller can't be found unfortunately.

Do I have to raise my post count to 10 before I can post bugs or give feedback on rom related threads? As I recall correctly, I did post in rom threads some time ago. Is this a new "feature"?

I was referencing the steps given by the first post. After flashing the cwm-recovery the reboot triggers an automatic flash of the stock recovery. Thats why it seems the recovery wasnt installed - it actually was but the stock recovery is automatically flashed afterwards. To prevent this enter...

Alternatively you could enter cwm directly (Step 10) when Odin triggers reboot (Step 8) and disable the automatic flash stock recovery while installing the root.zip (Step 9). No need for manually touching those files that way. Greetings ps: first post yay :cyclops: