Develop Bugs

How to get rid of lockscreen lag SM-A520F

After updating to android n the lockscreen has become incredibly laggy. Is there anyway (root or no-root) to fix this?

Kudret Davudov:
Flash latest firmware then wait for the blue android screen that says installing updates etc etc...
After that screen immedietly boot into download mode and flash twrp then restart and again immedietly boot into twrp
Just dont let phone boot into android
With this trick you should get /data decrypted so no needed to wipe and not need for no verity no encrypt patch because it lags your phone

ChARCOOL said:
Kudret Davudov:
Flash latest firmware then wait for the blue android screen that says installing updates etc etc...
After that screen immedietly boot into download mode and flash twrp then restart and again immedietly boot into twrp
Just dont let phone boot into android
With this trick you should get /data decrypted so no needed to wipe and not need for no verity no encrypt patch because it lags your phone
Click to expand...
Click to collapse
Ah, okay. I might wait off a bit because I've just recently flashed my phone, and it's kinda a pain in the ass, especially since apparently I have no idea how titanium backup works lol.

ChARCOOL said:
Kudret Davudov:
Flash latest firmware then wait for the blue android screen that says installing updates etc etc...
After that screen immedietly boot into download mode and flash twrp then restart and again immedietly boot into twrp
Just dont let phone boot into android
With this trick you should get /data decrypted so no needed to wipe and not need for no verity no encrypt patch because it lags your phone
Click to expand...
Click to collapse
Hi,
I followed this through the final instructions (bold) wihtout the phone booting into android (rebooted into download once the blue install screen finished). I wasn't sure what I needed to do in TWRP once I rebooted there, so I tried flashing su-config and an sbin 2.82 sr5 supersu install - then rebooted finally into android, and the unlock lag was back.
what needs to be done once twrp flashed and user has rebooted immediately into twrp?
[edit - further experimenting suggests supersu 2.82 versions all cause pattern unlock lag, while 2.79 does not but cannot be hidden via suhide]
thanks, sure I am missing something obvious here.

DullPeon said:
Hi,
I followed this through the final instructions (bold) wihtout the phone booting into android (rebooted into download once the blue install screen finished). I wasn't sure what I needed to do in TWRP once I rebooted there, so I tried flashing su-config and an sbin 2.82 sr5 supersu install - then rebooted finally into android, and the unlock lag was back.
what needs to be done once twrp flashed and user has rebooted immediately into twrp?
[edit - further experimenting suggests supersu 2.82 versions all cause pattern unlock lag, while 2.79 does not but cannot be hidden via suhide]
thanks, sure I am missing something obvious here.
Click to expand...
Click to collapse
Unfortunately supersu has built-in no verity patch, that is why you still get lock screen lag. I use magisk and it works perfect for me with no lags

ChARCOOL said:
Unfortunately supersu has built-in no verity patch, that is why you still get lock screen lag. I use magisk and it works perfect for me with no lags
Click to expand...
Click to collapse
thanks. I am surprised this isn't a more common complaint - do you know if there are recent samsung models with 7.0 that don't have this issue? It seems like anyone with an affected model that tries to run suhide, for example, would run into this immediately.
alternately, does this create the same problem on 6.0?
EDIT - this thread suggests maybe (not verified) it wasn't a problem on nougat 7.1.1 as well https://forum.xda-developers.com/galaxy-j7/how-to/approach-to-rooting-7-1-1-t3709414
I have posted there to try to verify.

I just rooted my phone again with magisk using my method and i didn't got verity error and there is no lock screen lag

ChARCOOL said:
I just rooted my phone again with magisk using my method and i didn't got verity error and there is no lock screen lag
Click to expand...
Click to collapse
thanks. i have rooted with magisk recently and didn't have a lag error either - but the app I need to use for this claims to requre supersu, and in fact seems to not like magisk at all.
also regardless of the 7.1.1 question, neither of the possible phones have a 7.1.1 available.
still looking for a 3rd way to handle this and get suhide, but looks grim for now. maybe simply moving up to the latest 7.0 firmware (my current build is a u2 build from ~~october, so haven't put the U3's on due to what I read about locking the bootloader etc) would fix it. It just seems to be an uncommon problem and that makes me think that there is some way to use a samsung with 7.0 with supersu 2.82 without this issue. Otherwise the number of questions about it from samsung users should be overwhelming.
do you know if it is disabling dm verity, or disabling forced encryption, that is causing the lag? if it is dm verity, would re-enabling dm verity via adb be a work-around? (I dug around for a script to enable verity and encrypt, no dice so far).
thanks for your help.

ChARCOOL said:
Unfortunately supersu has built-in no verity patch, that is why you still get lock screen lag. I use magisk and it works perfect for me with no lags
Click to expand...
Click to collapse
follow-ups to your method -
why is it necessary to let the blue install screen process run before booting back to download to install twrp? if one just goes from download firmware and reboots to download immediately, what changes?
i played around with the no-verity-no-encrypt issue (both with the patch and with aroma su config) and it appears the no-encrypt is what is leading to the lag.
one drawback I am running into with the method above (flash firmware, run blue install screen, download-twrpflash, then immed. to recovery, then install in my case aroma & 2.82su is that i cannot mount data again in twrp once android has loaded, but that seems to be expected as it is not fully decrypting (even though it isn't encrypted, as I understand it?)

DullPeon said:
follow-ups to your method -
why is it necessary to let the blue install screen process run before booting back to download to install twrp? if one just goes from download firmware and reboots to download immediately, what changes?
i played around with the no-verity-no-encrypt issue (both with the patch and with aroma su config) and it appears the no-encrypt is what is leading to the lag.
one drawback I am running into with the method above (flash firmware, run blue install screen, download-twrpflash, then immed. to recovery, then install in my case aroma & 2.82su is that i cannot mount data again in twrp once android has loaded, but that seems to be expected as it is not fully decrypting (even though it isn't encrypted, as I understand it?)
Click to expand...
Click to collapse
Its working so well for me and you need to go to download mode after blue install because it installs csc and cleans old stuff that is why you need to do it if you don't want broken phone

How long after flashing superSU zip does first boot take?

First time messing with this phone
followed the instructions for unlocking bootloader, installing TWRP, and rooting here: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
Successfully unlocked bootloader, flashed TWRP, but now hung up on SuperSU.
Flashed SuperSU VV2.82 zip from http://www.supersu.com/download in TWRP
Wiped dalvik and cache
reboot
Now it's been about 10 minutes. Blank screen and blue LED.

Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first

l3ones said:
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
Click to expand...
Click to collapse
I did, three times.
I ended up flashing the latest complete OTA to get it back to being able to boot.

Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.

Macusercom said:
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Click to expand...
Click to collapse
was on the latest stock OTA, which was 8.0.0
Flashed Mgisk after flashing the latest OTA, and everything is working swimmingly

Exact Same thing happened to me last night.
And I lost my internal sdcard.
Eventually flashed stock recovery didn't do anything different so flash twrp again and got sdcard back.
It was a strange one.
Now I'm waiting for an update or the right file for root.

Maybe this has something to do with Keymaster?

So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?

Use codeworkx dumpling TWRP, dirty flash your ROM, boot it once, then reboot to recovery and flash Magisk 15.3. Should be all you need.
For Nougat, I think it's better to flash Magisk 14, on some ROMs.

New apps
Great information provided by many users. I have just joined this group and read many experts advice. Thanks

Latest SuperSU (beta 2.85 i believe) don't work on OP5T Oreo update (stable or Open Beta). Don't know why, but I had to use Magisk. ANd I must say, I'm pretty happy with it, too!

Elfomze said:
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Click to expand...
Click to collapse
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/

Kunjuuuz said:
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Click to expand...
Click to collapse
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though

The latest SuperSu does not work with 8.1 for us and some other (or all other) 8.1 phones.
And... SuperSu is no longer in development.
Rumor has it a slightly older SuperSu version works in 8.1 but I never got around to trying it and forget the version # now.
And Lineage has not released a SuperSu/superuser for 8.1 yet.
It bums me out because I want that Magisk alternative.
Not a fan of Magisk yet.

Elfomze said:
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
Click to expand...
Click to collapse
Locking the bootloader, wiping, and unlocking the bootloader again fixed the issue for me.

Lineage OS 15.1 and encryption

Hi everyone,
I would like to know if I can use device encryption in Lineage OS 15.1.
I currently have TWRP 3.2.2-0 installed on my Samsung Galaxy S5 Plus (kccat6).
Can TWRP 3.2.2-0 decrypt Lineage OS ?
By the past, I have seen many posts on forum, telling that they had trouble with the encryption or when they wanted to update LineageOS (which is currently in Nightly phase... so where updates can be important).
Thank you in advance for your answers !

Yes you can, but you have to update your TWRP to the latest version (3.2.3-0), they fixed the automatic installing of OTA zips on encrypted devices

Thanks lucaslbbh. So I made it. I was astonished to see that the process lasted only 9 min... Unfortunately, my phone was unable to start after that (bootloop).
I came back to TWRP, entered my password and restored my Nandroid backup.
Surprinsgly, it kept the encryption : I have to enter my PIN for each startup, and when I want to enter in TWRP. In the security menu, it's said it's encrypted.
Is it possible ?

oldbear3 said:
Thanks lucaslbbh. So I made it. I was astonished to see that the process lasted only 9 min... Unfortunately, my phone was unable to start after that (bootloop).
I came back to TWRP, entered my password and restored my Nandroid backup.
Surprinsgly, it kept the encryption : I have to enter my PIN for each startup, and when I want to enter in TWRP. In the security menu, it's said it's encrypted.
Is it possible ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
This guide was only tested with Nougat but it says the ROM has to be unrooted when encrypting /data. Maybe that's your prob?

Bootloop after magisk v20.4 installation

HI everybody.
It does many years that I wanted to try to root my phone: I love new technology but I become old : perhaps is it the reason for which root my phone finally doesn't seem as easy as it is said everywhere !
As we are at home due to the COVID-19, I thougt that is was the perfect moment to try this week (I began last tuesday).
As i'm a newbie, I read many tutos, pages to understand and to be "sure" not to do mistakes.
I've installed TWRP and it works fine.
I did a backup in TWRP (data, system, manufacturer, modem, EFS and boot).
The only problem, after TWRP installation, was that the smartphone never booted in recovery mode with TWRP: I always had stock root.
To have twrp recovery, I always had to use adb in fastboot.
I searched a long time and never managed to fix this.
I considered it was not a real problem because it was easy to have TWRP with adb.
At this moment, I wanted to install LineageOS but after many searches, I realized that there was no LineageOS rom for the Mi Max 3.
I decided to install the last issue of magisk to really root my phone since the TWRP doesn't root itself the phone.
I installed Magisk v20.4 and troubles began.
I had a bootllop...
It does hours and hours (night and day) I spend to find a fix but without success.
Most of tutos refers to "old" issues of uninstaller or uninmod.
I think I've done many things as:
- Re-install Magisk v20.4
- Install "officiel" Magsisk V20.4 uninstaller (I got an error 1)
- Install different modules remover (I always got errors 1): uninmod_Magisk_v4
- Install Magisk Manager for Recovery v5 202004170 which is very recent (I always got error 1)
- I obviously tried to restore my backup with no success
- I read the page of katterpanne to fix the bootloop, but the mentionned tools refer to "obsolete" versions of magisk manager and uninstaller
The only zip package which didn't cause an error 1 was the magisk_module_remover of edzamber (for magisk 19 and higher) but it is a little old and surely doesn't "fit" to magisk v 20.4 and it didn't work. At least, if i reboot, TWRP warns that there is no installed OS.
I feel desperate and my knowledges are limited.
I don't know how to uninstall manually, if I don't find any suitable uninstaller/remover zip package, this magisk.
Perhaps that all I done has really uninstall/remove magisk but how can I check that ?
Why so many error 1 in TWRP ?
Haw can I check, from TWRP, if my phone is rooted ?
According to you, what should I do: install a version of Magisk lower than V20.4 (even v19.x) or try to install a rom ?
I suppose that I had to install a custom ROM since I've no OS but my phone seems no rooted since Magisk caused a bootloop.
Finally, if there is no suitable LineageOS for the Mi Max 3, which custom ROM can I use (I have no particular expectations: just remove the xiaomi apps).
I apologize for all these questions and this long topic but I hope having replies and help to fix my issue.
I can't believe thet my phone is condemned, dead... I really appreciate this Mi Max 3.
Thanks by advance for your lights.
Best regards.

You can flash back to stock ROM with MiFlash.
Download the fastboot ROM from here:
https://forum.xda-developers.com/mi-max-3/how-to/rom-official-recovery-fastboot-roms-mi-t3827503
How to flash with MiFlash:
https://www.the***********.com/install-miui-fastboot-rom-using-miflash-tool-xiaomi/
Edit: Somehow i can't post the link, just Google "Install MIUI fastboot ROM".

OnePlus 7t root and TWRP recovery

So it's been awhile since I've had a phone I cared to get into installing root and custom stuff but I just bought a 7t and am trying to get it all working. I have the bootloader unlocked and the latest version of TWRP flashed but every time I'm in TWRP it shows up as 0mb and can't mount the storage. I tried "fastboot format userdata" in adb and it worked for one boot cycle but once I rebooted TWRP after that I was back to the 0mb and can't mount storage (I also still cannot format storage from TWRP before anyone tells me to try that) so what gives? What am missing?

You're missing the search functionality of the forum.
TWRP does not currently support reading data partition when encrypted by OOS. It does work, however, for custom ROMs, as long as you don't use a PIN, but a pattern. It also does not support formatting data partition, regardless of the ROM you're using.

morphvale said:
You're missing the search functionality of the forum.
TWRP does not currently support reading data partition when encrypted by OOS. It does work, however, for custom ROMs, as long as you don't use a PIN, but a pattern. It also does not support formatting data partition, regardless of the ROM you're using.
Click to expand...
Click to collapse
Well that's disappointing. So it sounds like there's really not too much point to it then. So I'm assuming there's a guide on how to install root and magisk via fastboot commands?

Again, you're missing the search functionality.
You can see it on the home page of the 7T, under ONEPLUS 7T GUIDES, NEWS, & DISCUSSION, third topic right now..

morphvale said:
Again, you're missing the search functionality.
You can see it on the home page of the 7T, under ONEPLUS 7T GUIDES, NEWS, & DISCUSSION, third topic right now..
Click to expand...
Click to collapse
Still leaving trouble using the search function to find what I want but I'll figure it out. So is it worth installing a custom rom on this phone or should I just try and root the phone on the stock OS? I'm very new to this phone and everything that goes along with it.

Justin541 said:
Still leaving trouble using the search function to find what I want but I'll figure it out. So is it worth installing a custom rom on this phone or should I just try and root the phone on the stock OS? I'm very new to this phone and everything that goes along with it.
Click to expand...
Click to collapse
@Justin541 - If you need any help just PM me. Ill get you going.. As long as your bootloader is unlocked, the rooting process is easy. All you have to do is:
- Install magisk manager (here)
- Download a patched boot.img from here(try to find the boot.img that matches the build your on, all though it probably doesnt matter)
- Boot into bootloader (adb reboot bootloader) and BOOT(dont flash) the patched boot.img (fastboot boot patched_boot.img)
- When phone is booted, open up magisk manager and do a direct install. Booting the patched boot.img is what you gives you a temporary root to be able to install magisk.