How to get rid of lockscreen lag SM-A520F - Samsung Galaxy A3, A5, A7 (2017) Questions & Answe

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

Related

No camera on MMB29K?

I just flashed the Factory Image MMB29K (flash-all.bat then reinstalled TWRP and SU manually). Now the camera doesn't work (see attachment below). I did check the MD5 and it matched.
Any help is greatly appreciated.
Very odd. If I do not install TWRP (I have tried both 2.8.7.0 and 2.8.7.2) or SU (Beta 2.52) the camera works fine. Or maybe it's the version of the modified boot image (Chainfire's mdb08i) that's not compatible.
Disregard. Found another thread with a discussion of the same issue. The problem is with the old mdb08i boot image.
In case anyone is experiencing the same issue please see this post:
The way I just rooted 2 5x's was, I unlocked the bootloader, flash-all on the MMB29K update, reinstalled TWRP, and then installed Super SU v2.61. You don't have to use a modified boot, that version of Super SU does the modifying for you. Just make sure to read the directions - I got caught in a boot loop trying to install 2.61 over a modified boot (essentially I did the process backwards the first time.) Recovered, and did both phones just fine. Camera works great.
How is that systemless root - any problems so far? I was feeling lazy so stuck with the old fashioned version - haven't had time to read up on the new method.
The only problem I have had so far (and I had the same problem on system root as systemless) is when I boot into TWRP, it brings up the pattern lock. The problem is, sometimes it doesn't recognise my touch on the pattern, so I can't get it to mount the Data partition. When that happens, I either have to flash whatever I was going to flash using USB-OTG (luckily I bought one of these, and got it the same day the phone arrived) or keep re-booting into system, then back into recovery until I get it to work. Might be able to take the pattern off before I go into recovery, but that'd be a pain - and I think I'd have to re-do fingerprints every time, too.
Danariel - thanks for the reply. I think I'll wait until the next go around of updates before trying out the systemless root. Feeling extremely lazy right now.

[bricked device] OP3 shows yellow screen

Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.
Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
EDIT: I see that Puddi Puddin beat me to it.
Puddi_Puddin said:
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.
Click to expand...
Click to collapse
tnsmani said:
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
Click to expand...
Click to collapse
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
tnsmani said:
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
Click to expand...
Click to collapse
I am using the newest (twrp-3.1.1-2-oneplus3.img) but the problem is that I can't see anything in recovery or elsewhere :/
Peybro said:
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
Click to expand...
Click to collapse
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence
Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post
Puddi_Puddin said:
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence
Click to expand...
Click to collapse
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
Renosh said:
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post
Click to expand...
Click to collapse
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on
Peybro said:
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on
Click to expand...
Click to collapse
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
I can give it a try later (and in the future when everything works again) but I do not think (at least I can't imagine) that the problem I have comes from recovery.
I know the reason!
I found other people who also had a static screen and they said they could fix it by pressing the screen back on its contacts...
I did so and it worked!... A bit... For a few minutes...
So the static definitely wasn't the result of rooting and stuff but the repair company's fault.
I hope they accept their mistake and fix it. Thx for everyone here trying to hel me!
P.S.
tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
And as soon as I can I will try this TWRP
-------------------------------- Edit: --------------------------------
(Just in case people get same problem)
[after Mega Unbrick Method 2 finally worked (I put the stock zip in the tool's folder)]
This morning I restarted the phone just because and I could see what was going on on the phone - but the display was still crazy with yellow tint and colorful stripes etc.). After setup it asked me to download & install newest stock rom; I did and after reboot everything was fine again....
Don't know what happened here but it seems to work again.

[Q] Root Issues - Are these known? Are there fixes?

I purchased my Pixel 2 XL from the Google store. I had just upgraded to the 8.1 OTA a few days before when i came across this video and used it to root my phone:
https://youtu.be/nFD9sa-WdUM
Here's the basic steps i took:
Unlock dev options and turn on OEM Unlocking
Boot to stock recovery
Go to his highonandroid site and download TWRP 3.1.1 beta2 (img and zip), an outdated fastboot.zip, magisk 14.5, and the USB drivers which i didnt download because my computer is already recognizing my device just fine.
Extract the fastboot files to a new folder and copy the twrp img file to the fastboot folder.
In CMD, unlock the bootloader with fastboot and reboot phone.
Connect phone as storage device, copy over twrp zip file and magisk 14.5 zip files to root folder on the phone, reboot into recovery
Use fastboot to boot the twrp image that we copied to fastboot folder to get into twrp
Unhook the USB cable, set TWRP to read only, install TWRP, hit home button, then install Magisk and reboot
Once booted up, get into Magisk, download proprietary software, run checks and done.
Once this was done, my fingerprint scanner and wifi no longer worked. I could turn wifi on but it would never find anything. I also received the error when rebooting the phone that says "There's an internal problem with your device. Contact your manufacturer for details." When this message is on the screen, if i dont touch the phone and the screen times out, it flickers really bad and never actually shuts off until i unlock it and hit the OK button.
So i decided to give it another go and ran into some big issues. I figured that i used 8.0 instructions on 8.1 and there was enough things different that it caused problems, so i used this link to reroot:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
I went through the first 10-15 pages and the last 10-15 pages and did some searches on the thread and never found any of my issues, but found that a lot of people used different sets of steps and pretty much everything was successful as long as you didnt miss anything and used the most updated stuff. So i did, i went to googles website and downloaded the newest SDK with fastboot, adb, and all that good stuff, as well as the newest 8.1 image (there was a newer version but it had a carrier label on it so i didnt get that one), and the newest magisk and twrp.
I flashed 8.1 and the phone wouldnt boot, nor would it get into TWRP anymore, so i had to use fastboot to boot the twrp image and reinstall the recovery and magisk but it still wouldnt boot. I ran through several different steps and eventually got it to boot up with recovery working. Its the newest 8.1 image, the newest magisk, and the newest twrp, and since then magisk has updated a couple times.
Now on to my issues!
I still get the "Internal problem" popup when booting
I get a lot more random reboots
Sometimes random things just wont work, like streaming plex to my tv or loading an app or something on an app and i have to reboot and it works fine
I've seen numerous times that the "Internal problem" thing is just a mismatch between the system and vendor build.prop files. I dont know what exactly is mismatching between the two but i've tried reflashing them and all sorts of things and nothing ever fixes it.
Does anyone know if there's a fix to any of these three issues, or if maybe looking at my steps i clearly did something wrong? I'm willing to do the whole thing over again if there's a good suggestion, but once i flashed the 8.1 image and went that route, i rerooted successfully 4 times total before i quit doing it again just because of that internal problem popup, i kept figuring something went wrong or i did something wrong. I had no security or anything set before rooting or flashing or anything, and each time i reflashed the operating system, but when i flashed the OS, i had to extract the system file because i would constantly get an error that it was too big and it failed to truncate it, so i've always had to manually install it by first copying it to my phone and installing it through TWRP. Its been an adventure, but these problems suck!
PMad said:
...Its been an adventure, but these problems suck!
Click to expand...
Click to collapse
It's called training. For the error, you just need to fastboot flash the stock dtbo.img. This was fixed on the 15.1 version of Magisk so you shouldn't have that problem anymore. I can tell you that rooted, kernel and a few root apps and I have never had ANY random reboots, so one of your apps is causing it or you didn't start from a completely blank slate. Run your phone in Safe Mode for a while to see if you stop the reboots 100%. If so, one of your apps is the cause. If you still get reboots in Safe Mode, you're gonna need to re-install. I suggest using the instructions on the Google web page where you got the full image. (and try to distill your posts down a little, ffs)
v12xke said:
It's called training.
Click to expand...
Click to collapse
Every new phone is a new adventure, they are all the same but unique at the same time!
v12xke said:
For the error, you just need to fastboot flash the stock dtbo.img.
Click to expand...
Click to collapse
I'll give this a shot! Thank you!
v12xke said:
This was fixed on the 15.1 version of Magisk so you shouldn't have that problem anymore.
Click to expand...
Click to collapse
15.1 is the version i'm on now but nothing has changed. Which issue was this supposed to fix?
v12xke said:
I can tell you that rooted, kernel and a few root apps and I have never had ANY random reboots, so one of your apps is causing it or you didn't start from a completely blank slate.
Click to expand...
Click to collapse
My concern here is that my settings and apps are literally exactly the same as before root, except for magisk, its my only new app, which would lead me to believe that something Magisk is changing is causing the problem, or something else is happening that i'm not realizing yet.
v12xke said:
Run your phone in Safe Mode for a while to see if you stop the reboots 100%. If so, one of your apps is the cause. If you still get reboots in Safe Mode, you're gonna need to re-install. I suggest using the instructions on the Google web page where you got the full image.
Click to expand...
Click to collapse
The reboots are typically 1 reboot every 1 to 3 days, so its not a terrible issue but its happening and it shouldnt. For flashing the OS, after the first failure when trying to install it, those are the only instructions i've used, but i get that error when trying to install the OS that says something about how it failed to truncate the system.img file and so it wasnt installed, so my work around was to copy the file to the phones root folder, install the 8.1 image then immediately go and manually install the system.img file in twrp since its the only thing that fails, but i still have issues. What is this truncate issue?
v12xke said:
(and try to distill your posts down a little, ffs)
Click to expand...
Click to collapse
I agree! hahaha i just wanted to be clear and include all the details, otherwise everyone would have asked me question after question that i could have just included. It ends up being long, a lot happened!
I'll give that dtbo.img a shot and see what that clears up, then if there's issues with rebooting still i'll try safe mode for a few days and see what that does.
Thank you v12xke! (how do you pronounce that? haha)
PMad said:
...I'll give that dtbo.img a shot and see what that clears up, then if there's issues with rebooting still i'll try safe mode for a few days and see what that does.
Thank you v12xke! (how do you pronounce that? haha)
Click to expand...
Click to collapse
Your dtbo.img got patched by Magisk somewhere along the line and that is why the OS is throwing the error. Extract that img file from the full Google image and fastboot flash it, and the error will go away. There is a long thread around HERE on random reboots you should read. The v12xke is a car (Jaguar E-Type) I once owned.
v12xke said:
Your dtbo.img got patched by Magisk somewhere along the line and that is why the OS is throwing the error. Extract that img file from the full Google image and fastboot flash it, and the error will go away. There is a long thread around HERE on random reboots you should read. The v12xke is a car (Jaguar E-Type) I once owned.
Click to expand...
Click to collapse
So i just tried to do this and ran into one of the issues i had when originally trying to root it... I get into TWRP and it will not take any button presses, like the touch screen has become a screen (minus the touch). Is there a fix for this or do i just need to install TWRP before i use it each time it does this?
PMad said:
So i just tried to do this and ran into one of the issues i had when originally trying to root it... I get into TWRP and it will not take any button presses, like the touch screen has become a screen (minus the touch). Is there a fix for this or do i just need to install TWRP before i use it each time it does this?
Click to expand...
Click to collapse
1. You don't use TWRP to flash dtbo.img, you fastboot it while the phone is in bootloader mode.
2. TWRP works just fine if you install it and leave it installed. Make sure you are using 3.2.1-0 (img and zip).
v12xke said:
1. You don't use TWRP to flash dtbo.img, you fastboot it while the phone is in bootloader mode.
2. TWRP works just fine if you install it and leave it installed. Make sure you are using 3.2.1-0 (img and zip).
Click to expand...
Click to collapse
I was getting into TWRP to create a backup of everything and it popped up asking for my password, and i remembered reading that we have to get rid of all of our security before making a backup, so i tried to hit buttons to cancel it and nothing worked, i had to hold the power button. So i eliminated all of my security and went back thinking it was a 1 time issue but it happened again, it took me straight to the main menu but nothing would work. I'm using 3.2.1-0 like you mentioned and i cant press any buttons. I'd like to back everything up before flashing this or anything else.
PMad said:
I was getting into TWRP to create a backup of everything and it popped up asking for my password, and i remembered reading that we have to get rid of all of our security before making a backup, so i tried to hit buttons to cancel it and nothing worked, i had to hold the power button. So i eliminated all of my security and went back thinking it was a 1 time issue but it happened again, it took me straight to the main menu but nothing would work. I'm using 3.2.1-0 like you mentioned and i cant press any buttons. I'd like to back everything up before flashing this or anything else.
Click to expand...
Click to collapse
You don't need a backup before re-flashing the STOCK dtbo (or boot) partitions, haha. READ UP.

[Magisk] Root for the Galaxy S10 Series

Here comes official Magisk support for the Galaxy S10!
Let's get Magisk to kick start the development of these Samsung devices!
Link to Instructions
Carefully read through everything in the page linked above! Follow the instructions closely so you don't end up bricking your device
Technical Details
Google enforces all devices that ships with Android 9.0 to use system-as-root in part of "Project Treble", so Samsung finally introduced their own "flavor" of the implementation. More details regarding system-as-root can be found in the official Google dev site. Samsung is using the A-only system-as-root setup, meaning that its boot image will only contain the kernel binary without ramdisk included. Similar setup has already been deployed on many new devices, and the solutions for those devices are rather simple: add a new ramdisk section into the boot image and hexpatch the kernel to always use ramdisk as rootfs. However in Samsung's case, the bootloader simply does not load anything other than the kernel binary to the memory, meaning no matter what we do the kernel will always use the system partition as root directory. This leaves us no option but to install Magisk onto the recovery partition.
Installing to the recovery partition have its own issues: first is that a service called "flash_recovery" will run when the system starts up, which will restore the recovery image back to stock on startup. This is unacceptable because not only does it uninstall Magisk in the process, the data encryption key will also be changed due to fact that Samsung's data encryption keys are tied to the bootloader status and boot/recovery image signatures, and thus causing the device unable to boot in following reboots unless factory reset. The solution to this problem is to simply repack the boot image to remove the binary integrity and also the signature of the partition. The second issue is that since Magisk and recovery shares the same partition, how can we actually boot into recovery? (e.g. to factory reset your device, or have custom recovery co-exist with Magisk) Fortunately a solution that detects button key presses is introduced, which details are already provided in instructions.
To make matters even worse, Samsung introduced a "VaultKeeper" service, which adds another "lock" on top of the OEM lock of the bootloader. By default the service will "relock" the bootloader after data is wiped. Only after the initial setup will it verify the OEM lock option and changes the bootloader state accordingly. If you are running custom firmware with stock system, DO NOT try to wipe data or else you might end up bricking your device due to vaultkeeper locking your bootloader up, which will eventually lead to bootloader refusing to boot because unofficial partitions are detected.
For custom ROM developers, the first few things you would want to remove is VaultKeeper to protect your users from bricking their devices. For stock ROM users, just make sure to always boot to Magisk after a data wipe, or never power off your device before finishing the initial setup and verify OEM lock is enabled.
thx
Yay.
The best day of my life!!
Can I ask, when we install Magisk what sammy stuff will be broken? I understand Knox will be tripped but what 'features' will still be available.
Does the fingerprint still work for instance
Amazing work though, well done buddy
Fantastic!
I hope people carefully read those instructions!
ok, who's trying it first on an European S10+ ?
..
Amazing! Is this for unlocked Snapdragon too?
S9 Exynos not install
On S9 the installation does not give error, but on restart Magisk is no longer installed.
ooonea said:
On S9 the installation does not give error, but on restart Magisk is no longer installed.
Click to expand...
Click to collapse
I'm aware of this issue
cant even boot into download mode with the way you have given... is there a step missing?
ahh, turn the phone off, USB connected and press Bixby and Volume Down.
Fix?
topjohnwu said:
I'm aware of this issue
Click to expand...
Click to collapse
Will you fix it?
A couple of questions:
1. What will happen if I boot from boot partition after installing magisk? What steps will be needed to recover from that?
2. Why final wipe after installing magisk is needed?
ooonea said:
Will you fix it?
Click to expand...
Click to collapse
What an odd question... obviously.
I got some questions about Safetynet
1. Is Safetynet still passing with this method when you boot to system with magisk?
2. Also if you boot to system without pressing any button, so system without magisk, is Safetynet passing or failing?
Thanks for your hard work.
Download Mode doesn´t work for mee
is there a step missing?
Memento_Mori said:
Download Mode doesn´t work for mee
is there a step missing?
Click to expand...
Click to collapse
The cable must be in too
Thanks,
I have one question, after install Magisk can I still install OTA update ?
tiho5 said:
The cable must be in too
Click to expand...
Click to collapse
I know, but it doesn´t work for me too

Encryption / Twrp

Hi,
Some weeks ago I've got a LG V20 and followed some tutorials I found (without reading enough) to install LOS 17.1 with Twrp, Magisk and Viper4Android.
Then I was so dumb to enable LOS' encryption...now the problems start: I cannot install OTA Updates anymore. Twrp says "Decryption failed, cannot mount".
So...in short...how do I get updates now?
Some hours ago I installed LOS' recovery - but it also seems to be not working as expected: when I select " install update" in Lineage, it reboots into recovery - and thats it. No update is installed automatically as Twrp did normally. Can I use this with my already installed Magisk etc and encryption turned on at all? Or do I def need to use Twrp?
It would be very cool if someone here could help to get the decryption in Twrp work...that would be the best way for all and future users in my opinion.
However, I am stuck now with an encrypted phone, installed Magisk - and do not really know how to get an update of LOS the best way.
Many thanks already for every help
Ms0206 said:
Hi,
Some weeks ago I've got a LG V20 and followed some tutorials I found (without reading enough) to install LOS 17.1 with Twrp, Magisk and Viper4Android.
Then I was so dumb to enable LOS' encryption...now the problems start: I cannot install OTA Updates anymore. Twrp says "Decryption failed, cannot mount".
So...in short...how do I get updates now?
Some hours ago I installed LOS' recovery - but it also seems to be not working as expected: when I select " install update" in Lineage, it reboots into recovery - and thats it. No update is installed automatically as Twrp did normally. Can I use this with my already installed Magisk etc and encryption turned on at all? Or do I def need to use Twrp?
It would be very cool if someone here could help to get the decryption in Twrp work...that would be the best way for all and future users in my opinion.
However, I am stuck now with an encrypted phone, installed Magisk - and do not really know how to get an update of LOS the best way.
Many thanks already for every help
Click to expand...
Click to collapse
There are many v20 variants. Are you sure, you selected the correct version? In your case i would start with a clean installation following the official lineageOS guide.
kurtn said:
There are many v20 variants. Are you sure, you selected the correct version? In your case i would start with a clean installation following the official lineageOS guide.
Click to expand...
Click to collapse
Yes, I am sure...its a Vs995.
The way youre asking is interesting and I wonder a bit why...it implicates to me that either Twrp should work with encrypted LOS 17.1 - or Lineage its recoverymode with Magisk, Viper / my installed stuff.
I'll now take a look into the official LOS guide...
Edit: i don't get it. I assume sideload through Twrp does not work (encryption !). Recoverymode of LOS does not even ask for the password so I assume it also does not work with encryption turned on. Or does it? If so, how??
Is there any readme/wiki for the LOS-recoverymode?
Again, my device is encrypted. Magisk and other things are installed.
So how to update without any available recoverymode that is able to decrypt?
Ms0206 said:
Yes, I am sure...its a Vs995.
The way youre asking is interesting and I wonder a bit why...it implicates to me that either Twrp should work with encrypted LOS 17.1 - or Lineage its recoverymode with Magisk, Viper / my installed stuff.
I'll now take a look into the official LOS guide...
Edit: i don't get it. I assume sideload through Twrp does not work (encryption !). Recoverymode of LOS does not even ask for the password so I assume it also does not work with encryption turned on. Or does it? If so, how??
Is there any readme/wiki for the LOS-recoverymode?
Again, my device is encrypted. Magisk and other things are installed.
So how to update without any available recoverymode that is able to decrypt?
Click to expand...
Click to collapse
Your data Partition is encrypted. Sideload does not touch data partition. Follow the guide
As if I didn't know it before, following the official guides producing the same errors as using Twrp.
I tried so many things...using official recovery does not install OTA automatically.
Sideload producing the same errors as using Twrp - "Magisk addond.d failed, cannot find Magisk binaries, reflash OTA Form decrypted recovery or reflash Magisk".

Categories

Resources