Related
Has anyone been able to get magisk to work appropriately? I attempted and the magisk apk kept fc'ing. I read about LG devices needing a boot.img "bump". Is this true or has anyone got it working in their own way?
There Is no root method for variants that don't have a unlocked bootloader. You would know this if you read the forums before asking
Sent from my VS995 using Tapatalk
mrtruckincowboy said:
There Is no root method for variants that don't have a unlocked bootloader. You would know this if you read the forums before asking
Click to expand...
Click to collapse
So, quite frankly, if you read, another user has it working. Further more, with the TMO variant, I do have an unlocked bootloader. Root application works with magisk, however the APK itself fc's.
I thought cowboys were polite ; )
I misread your post thought you were the typical person asking for a update on root I apologize.
Sent from my VS995 using Tapatalk
Thats what you get for not reading posts Cowboy... Smh...
I have the H918/tmo and I was able to get magisk running with phh's superuser. I'm kinda iffy on magisk-hide, as i had issues with it initially ( random reboots with it enabled). I turned off magisk hide for about a week, then turned it back on last night with no reboots since.. but haven't tested it with apps.
After running the easy recowvery + root script, i got rid of SuperSU. I believe all i did was a Full Unroot in the options, with no changes to the recovery. (I also may have done a format /data when rebooting to recovery again, but i dont recall fully, so take that into consideration if it didnt work at first (followed by the no-verity-opt-encrypt zip).)
After getting rid of SuperSU/su binary, what i remember doing was:
1 ) Flash magisk v9.zip -> reboot to system to make sure it boots, then adb reboot recovery.
2 ) Flash phh's superuser r266-2.zip -> reboot to system
3 ) install magisk manager via apk, and phh's superuser via playstore.
4 ) test out root.
has anyone been able to get Phh's superuser to work on the Sprint v20 / LS997 ?? If so, how? Thanks in advance.
If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.
HiddenKnight said:
Has anyone been able to get magisk to work appropriately? I attempted and the magisk apk kept fc'ing. I read about LG devices needing a boot.img "bump". Is this true or has anyone got it working in their own way?
Click to expand...
Click to collapse
ive got 1 working and 1 in testing that uses magisk and phh.
the phh superuser seems to be casusing the systemui to force close often when in hide mode and the random reboots and loss of service, otherwise it was working fine.
but yeah, just flash version 10.2 on your current rom and see what happens!
btw this was on DEC sec patch, on oct builds i never tried it, but this is latest DEC sofware, didnt even use rootswitch
slayerh4x said:
If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.
Click to expand...
Click to collapse
Is this the App you used?
https://forum.xda-developers.com/android/apps-games/play-pokemon-root-switch-method-patched-t3483179
remix435 said:
Is this the App you used?
https://forum.xda-developers.com/android/apps-games/play-pokemon-root-switch-method-patched-t3483179
Click to expand...
Click to collapse
I am using the one from this rom thread;
https://forum.xda-developers.com/v20/development/h819-nrd90m-modded-stock-rom-t3503658
Just follow the directions in the OP and you'll be g2g.
slayerh4x said:
If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.
Click to expand...
Click to collapse
Tried RootSwitch w/ SuperSU. Didn't pass SafetyNet if that's what you were referring to.
Tried it again last night. Had the 1st 3 options turned on. Soon as I opened Android Pay my phone hot booted and got stuck on the VZW splash screen. Had to pull the battery. Won't try that again with supersu.
I have a VS995 this is how I got my phone to finally take magisk and pass the safetynet check. I'm running software version VS99513A I performed dirty santa to get unlocked bootloader and root access. Now I tried to uninstall supersu threw the app and I got a failed message. I tried going into recovery and flashing the supersu unistaller and that would fail. I tried flash magisk v12.0 and keep getting error message. I got stock in twrp recovery several times and used LGUP and flash either VS99512A KDZ or the VS99513A KDZ. Am not a developer but it seemed as if the boot.img won't take by the magisk zip. Those where my failed attempts for about a week or two. Now on to the success story
Performed Dirty Santa on software version VS99513A. I decide to flash modstock kernaI update v1.1 because it seem to work well with a stock rooted VS995. I flashed busy box in recovery and downloaded the app and also downloaded quick reboot so I could reboot into recovery easier. After reading @poixninja thread on modstock kernal - stocked with goodies he mention flash a boot.img that was patched with magisk. So I but the phone into fastboot mode and flashed his boot.img onto the phone with cmd (command prompt). I think I might have tried to uninstall supersu threw the app and I think it didn't work after flash the boot.img. So I put the phone into recovery mode the to wipe and then to advance wipe and clear dalvik and cache. After that I went to install and flashed the supersu unistaller and it took. After flashing I wipe the cache that twrp ask after most flashes. I then rebooted into recovery to make sure my twrp was not affected because I had and issue with that in previous supersu unistaller attempts. Rebooted ito twrp recovery then rebooted into system. I think whenever I flashed the verzion logo stayed up longer than normal but the phone fully started up. I clicked on supersu and it said no root access. Turned of the phone and did the steps to get to recovery mode. Once in I first wiped dalvik and cache. Then I flashed magisk unistaller and it went threw with no issue. I wiped dalvik and cache then rebooted into recovery. After getting into recovery I rebooted to system.
Sidenote: I recommend after wiping supersu and flashing magisk unistaller. Once you boot up install magisk apk. I didn't install the apk until after I flashed the magisk v12.0 in recovery. I noticed when I reboot the magisk icon was on the phone but when I clicked it it said go to playstore to download. I had the magisk manager apk on my SD card so I just installed it. The install to longer than normal I think it was because I didn't install it prior to flash the zip in recovery. I didn't get a chance to verify it yet.
Once the phone boot and I installed the magisk app manager I open it up and got green checks for installed magisk v12 and properly rooted. I went to setting and turned on enable busy box, magisk hide, and systemless. But when I clicked safetynet I got cts mismatch. Did some research and read on other XDA magisk thread that it maybe because of custom roms, modified kernals and possible supersu somewhere on the system. The only root accessible apps I had installed during this process was busybox and quick reboot. I did notice the first time I ran quick reboot after getting magisk it did give it root access then it did after I opened it again.
I decide to uninstall quick reboot and busy box. I uninstalled both apps. I rebooted into recovery mode the manual way. First thing I did was wipe dalvik and cache. Then I flashed busy box uninstaller. When the flash was running I say in the command lines that it found supersu. Which I thought was odd so I also flashed supersu unistaller. I rebooted into recovery wipe dalvik and cache and flashed uninstall magisk. Then reboot into recovery. I ran busy box uninstaller one more time to see if it would pick up supersu again and the command lines did not mention it. I flashed back magisk v12.0 rebooted into recovery. Then rebooted into system
Opened magisk went to setting to turn on enable busy box, magisk hide and systemless. Check safetnet and failed I found a magisk XDA thread that talks about common issue. It said I had to check magisk core only mode. Once I did that he requested a reboot which I did. Once back up I first cleared in app manager under show system I cleared all data for google play store, google play service for instant app, google play services. I opened magisk clicked safetynet check and I passed it. I went to search for netflix in play store and it pop up I installed it and it working fine so far. I tried logging into snapchat and I got threw.
Hope this maybe help full to anyone having issues
https://forum.xda-developers.com/v20/development/kernel-modstock-kernel-stock-goodies-t3563887 (boot img and modstock v1.1)
https://forum.xda-developers.com/showpost.php?p=71154562&postcount=4 (Magisk common issues)
Easier than that...?
sentra10550 said:
I have a VS995 this is how I got my phone to finally take magisk and pass the safetynet check. I'm running software version VS99513A I performed dirty santa to get unlocked bootloader and root access...
...
...Hope this maybe help full to anyone having issues
Click to expand...
Click to collapse
If I may be so bold, I played around with the rooting process on mine (I have a VS995 on 13A, too), and found a much easier (and possibly cleaner?) way to do this. Of course, the way I'm about to suggest would require a full KDZ to stock and a factory reset...
Here's mine:
Follow this thread:
https://forum.xda-developers.com/v20/how-to/lgv20-vs995-verizon-aio-post-06-19-2017-t3624326
Note: For noobs: After step 13, it's a bit misleading, because it doesn't boot DIRECTLY into TWRP, but boots to the white-screen "stock" recovery. The trick is to tell it "Yes" to both reset prompts. (It doesn't actually reset your stuff.) After this, it will take you to the TWRP menu.
When you get to step 14E, DO NOT FLASH SuperSU!
Instead, flash the ReStock zip.
After flashing ReStock, follow step 14G, and then flash Magisk 13.3 (latest stable, haven't tested others) from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I tried this out of order a couple of other times and ended up either having Magisk not following through with install, or developing issues installing certain apps. (Either getting a -504 error from Play Store, or having valid APKs reply that they were "corrupt" when directly installing.)
Of course, all of the stereotypical disclaimers apply-- YMMV, and I'm not responsible if you brick your device, yadda yadda...
No offense, intended, sentra10550. While I'm glad you managed to get things working, the directions were a bit convoluted and I hope my humble findings might help yourself, in the future(?), and any others that may have a VS995.
Good luck, everybody!
)O( NeoHiPPy )O(
Think I'll wait until an easier method comes out for the VS995 to run Magisk lol..
I was UNABLE to do full unroot on my V20 from SuperSu settings menu. It would say "uninstallation failed"
I tried running UPDATE-unSU.zip from TWRP and it did not help. Magisk keeps on complaining about modified boot file.
I am unlocking boot loader, trying to flash Magisk in TWRP instead of SuperSu as per DirtyStanta root method instructions.
I will also flash restock 1.3 right after to stop static and vibration issue.
If it works, ill update my post.
---------- Post added 21st February 2018 at 12:28 AM ---------- Previous post was 20th February 2018 at 11:48 PM ----------
Ok i got it working. It was easier then i thought it would be.
These are the steps i did the very first time i got into TWRP after bootloaded unlock process as per DirtySanta rooting instructions.
Entered TWRP
DID NOT format data>yes
Installed Restock1.3 and Magisk.zip
Wipe cache and dalvik. Says Failed to wipe Dalvik (dont know why but what ever)
Reboot.
Result: Asking for unlock password 9 attempts left. So i have to Format Data>Yes
Re-entered TWRP
Format Data>yes
Reboot.
Root works. No SuperSu needed.
Conclusion:
You have to format DATA not for the root to work, but to be able to get into the phone. If there was a way to bypass that, there would be no need to factory reset to root. Root method would not require you to wipe the phone.
How ever, some apps that i use still do not support systemless root. They fail to do their work such as removing system apps. I cant remove any of my system apps for some reasons. I get "failed" messageevery time.
I was told i need modules for Magisk, but i have yet understood what that even means.
Other apps that use root, work fine. Such as AdAway.org
Hey everyone,
I`m running LineageOS on my phone and am rooted using SuperSU which seems to work, according to Rootchecker and the feww apps I use, which make use of root privileges.
But I`m not entirely happy with my current situation, since it seems that more and more apps don`t tend to work with my rooted phone. So what are my ways out of this?
Can I easily unroot my phone, while keeping LineageOS?
Is there a working alternative to SuperSU, which would enable me to stay rooted on LineageOS without reflashing the OS and use Banking-Apps?
I`ve heard of Magisk, but I am unsure of how to switch over from my current state and I`am not sure whether or not it would solve my problems
Thanks for any help in advance!!
Magisk
You just have to go to SuperSU, then Full Unroot, then download Magisk 13.3 and flash it from TWRP. After that you should have Magisk Manager, if for some weird reason you don't, install it via apk
Then you just go to the settings, tick MagiskHide, then go back and open the side panel, MagiskHide - select the apps that you want Magisk to hide itself from
So I tried to do what you said.
I did the full unroot in the SuperSu App,
My phone rebooted
I shut it down again and booted into recovery
Tried flashing Magisk
But it failed, apparently due to my Boot image being patched by another program and told me to go with stock image
What do I do now? And will I lose any data by doing so? Thank you so much for any help!
Weird, but you can simply dirty flash LineageOS (the same one that you have now, or an update, doesn't matter) and it should let you install Magisk.
I did what you said and installed a delta update using LineageOS Downloader. Had to manually flash it in TWRP since I had no root permissions anymore. But I was able to install Magisk like a charm! Now I have to questions:
1. How do I update Magisk? Using the app?
2. Do I have to flash it again everytime I'm updating LOS?
Thanks for the great help so far!
And what exactly are those moduls? Should I be messing with them?
If updates come they will appear on the status bar and you can download them, and they'll install with the phone on. after that you have to (not quick) reboot your phone.
and about the modules, seriously? what do you think??
I received my OP6T this past Tuesday and I absolutely love the phone. It was super easy to get TWRP installed after unlocking (easy since mine was purchased outright from OP).
My only problem is that I play Pokémon Go with my son. And it detects Magisk no matter how I tried to hide it from the app.
Is it not possible to flash TWRP without Magisk? I'd like to eventually try different kernels, but I just don't understand how everything appears to require Magisk.
This is my first OP device as well as the first device I've had with the A/B slots.
Any ideas would be greatly appreciated so I can unlock the phone to its full potential and still play a game I enjoy playing with my son.
Hi,
TWRP and magisk are not directly related, other than the need for twrp to flash magisk
In order to get rid of magisk you can just download the magisk Uninstaller (you can get that from the official magisk thread) - just be aware that of course any Magisk mods will be lost...
One caveat, though: this only works if you have an unmodified system partition (so you never acknowledged changes to system partition in twrp) - if you did you need root to be able to boot the system!
Cheers, Axel
Gesendet von meinem LYA-L29 mit Tapatalk
So I'm assuming I accidentally modified my system. Using Magisk Uninstaller from the app made it so the phone only booted into recovery until I flashed Magisk. Zip again.
On another attempt after resetting up the phone it seems that the Uninstall from the app succeeded but my phone would not boot for a good 15 minutes. Just a black screen nothing else. But after it turned on Magisk was gone and I didn't lose anything.
The twrp file to remove Magisk failed every time saying to use the one from the Magisk dashboard.
Is there an easy-ish way to get a stock system partition? Or will I have to use the tool to return the phone to stock and start over?
Magisk Props Module <- Have you tried this Magisk module? I don't play Pokemon go but I was able download it and open it. (I don't know at what point it detects root).
It actually was even easier ? in the settings menu and click hide magisk and it renames itself to something random and works fine!
after uptade magisk my phone stuck in fastboot . i cant go to recovery . what i can do ?
phone is over or i can fix it ?
Open Magisk Github, and try to find a solution in the Magisk Troubleshooting
You say you "updated Magisk". Since you didn't describe how, supposidely you did by flashing Magisk through TWRP or by Direct method from Magisk app/mngr
Unfortunately, those two ways are most risky. If anything goes wrong (if you don't have TWRP backup) you cannot go back to the previous working configuration
It takes just few minutes more to extract and patch the boot.img and to flash it. If anything goes wrong, you flash the original unpatched boot.img or boot.img that was patched by your older Magisk and you are back in business.
To fix the bootlop now, it will take more than few extra minutes for extracting, patching and flashing the image every time when installing and updating Magisk
zgfg said:
Open Magisk Github, and try to find a solution in the Magisk Troubleshooting
You say you "updated Magisk". Since you didn't describe how, supposidely you did by flashing Magisk through TWRP or by Direct method from Magisk app/mngr
Unfortunately, those two ways are most risky. If anything goes wrong (if you don't have TWRP backup) you cannot go back to the previous working configuration
It takes just few minutes more to extract and patch the boot.img and to flash it. If anything goes wrong, you flash the original unpatched boot.img or boot.img that was patched by your older Magisk and you are back in business.
To fix the bootlop now, it will take more than few extra minutes for extracting, patching and flashing the image every time when installing and updating Magisk
Click to expand...
Click to collapse
I did update magisk by direct method from the app. Now i am in a bootloop. I always had and still have the teamwin recovery project. Can you help me how to get out of this bootloop without losing my data?
Add me on discord for live support :
SneezeOnYou2#8507
AC420 said:
I did update magisk by direct method from the app. Now i am in a bootloop. I always had and still have the teamwin recovery project. Can you help me how to get out of this bootloop without losing my data?
Click to expand...
Click to collapse
You should better have updated Magisk by patching the boot.img, then flashing (from Fastboot or TWRP) - in that case, if you have bootloop you simply flash back your previously patched img that used to work
I cannot know what went wrong. Maybe, there is a module that is no more compatible and causing the bootlop:
- Reboot to TWRP, Advanced, File Manager and navigate to /data/adb/modules
Each folder corresponds to one module.
Add an empty file named: disable (exactly as that) to each folder/module (or only to those modules you suspect they might be causing the bootloop).
Once you disabled the critical module, you can boot to system and from Magisk app further manage your modules.
Or, from TWRP flash to Boot the original boot.img extracted from your OTA zip file.
When you reboot to system, there will be no Magisk but next time you install Magisk it will find and activate old modules, probably causing again the bootloop
Or, download Magisk apk, rename to uninstall.zip and flash from TWRP to fully uninstall Magisk (and all its modules, everything)
Recommending first method, but you see the other two options as well
zgfg said:
You should better have updated Magisk by patching the boot.img, then flashing (from Fastboot or TWRP) - in that case, if you have bootloop you simply flash back your previously patched img that used to work
I cannot know what went wrong. Maybe, there is a module that is no more compatible and causing the bootlop:
- Reboot to TWRP, Advanced, File Manager and navigate to /data/adb/modules
Each folder corresponds to one module.
Add an empty file named: disable (exactly as that) to each folder/module (or only to those modules you suspect they might be causing the bootloop).
Once you disabled the critical module, you can boot to system and from Magisk app further manage your modules.
Or, from TWRP flash to Boot the original boot.img extracted from your OTA zip file.
When you reboot to system, there will be no Magisk but next time you install Magisk it will find and activate old modules, probably causing again the bootloop
Or, download Magisk apk, rename to uninstall.zip and flash from TWRP to fully uninstall Magisk (and all its modules, everything)
Recommending first method, but you see the other two options as well
Click to expand...
Click to collapse
Connect me pls on discord fkr me its like chinese now it would be easy if you tell me live what to press on the teamwin mode. The reason i update magisk was because i had a module to block ads but suddenly it didnt work so i opened magisk and i saw the update and did the direct update like how i always updated my magisk before.
AC420 said:
Connect me pls on discord fkr me its like chinese now it would be easy if you tell me live what to press on the teamwin mode. The reason i update magisk was because i had a module to block ads but suddenly it didnt work so i opened magisk and i saw the update and did the direct update like how i always updated my magisk before.
Click to expand...
Click to collapse
I don't use discord and I have work and private life
I gave you directions that if you knew just basic things about flashing and File mngr in TWRP, about using Magisk, etc, would be nite than enough to follow directions
Most annoying users are those who install'nuclear bomb' like Magisk, do updates, etc, but never spent their time to learn (when things work and it's easier) how to use, read the Instructions (available by one click to Github from Magisk app), etc, and then when (sooner or later) get a brick, cry for somebody to guide them to click here, there, etc.
You can still use PC and google and fill the gaps from my instructions to what/how you must click here and there
Sorry to be brutal but I really don't have time
zgfg said:
I don't use discord and I have work and private life
I gave you directions that if you knew just basic things about flashing and File mngr in TWRP, about using Magisk, etc, would be nite than enough to follow directions
Most annoying users are those who install'nuclear bomb' like Magisk, do updates, etc, but never spent their time to learn (when things work and it's easier) how to use, read the Instructions (available by one click to Github from Magisk app), etc, and then when (sooner or later) get a brick, cry for somebody to guide them to click here, there, etc.
You can still use PC and google and fill the gaps from my instructions to what/how you must click here and there
Sorry to be brutal but I really don't have time
Click to expand...
Click to collapse
Its not that i didnt look up on youtube about flashing in revovery mode. When i did search for more information i get those videos of people in india talking their own language. Np if you dont have time and on other topic someone said that they wint use discord because it wont be public for someone else with the same problem but i was gonna make photos with the steps i did for fixing it. The thing is i cant find the uninstall. File or the older version of twrp. Skip i wont takr your time good luck with your private life
And about the installing nuclear bomb thing... magisk has the direct install option which is the nuclear bomb button (sometimes) the reason why my phone got into bootloop is a module which isnt working anymore its called energized its for blocking ads. I saw that it didnt work... before it worked fine i thought maybe i need to update magisk but thats why it went into the bootloop. I managed to delete the module through twrp mode and here this is for you
AC420 said:
And about the installing nuclear bomb thing... magisk has the direct install option which is the nuclear bomb button (sometimes) the reason why my phone got into bootloop is a module which isnt working anymore its called energized its for blocking ads. I saw that it didnt work... before it worked fine i thought maybe i need to update magisk but thats why it went into the bootloop. I managed to delete the module through twrp mode and here this is for you
Click to expand...
Click to collapse
You don't need to delete modules (some of them, like V4A might be complicated to install again) - just disable them through still the working Magisk app before you go for updating
Or patch and flash the image instead of taking Direct install. There might be other reasons to cause bootloop, not just incompatible modules.
If it bootloops when you flash the newly patched img, just flash your old img, previously patched by the older Magisk version, that used to work for you
As simple as that - and no bootloops, no emergency help needed, etc
zgfg said:
You don't need to delete modules (some of them, like V4A might be complicated to install again) - just disable them through still the working Magisk app before you go for updating
Or patch and flash the image instead of taking Direct install. There might be other reasons to cause bootloop, not just incompatible modules.
If it bootloops when you flash the newly patched img, just flash your old img, previously patched by the older Magisk version, that used to work for you
As simple as that - and no bootloops, no emergency help needed, etc
Click to expand...
Click to collapse
I am surei have the older backup in my internal storage of my phone but i dont know from where to recover that and on the internet they say everything and i am scared to make it worse than it is. I didnt use the phone for a long time because my lcd got a short circuit and i replacet it. On internet they say this bootloop problem can occure when you skip some updates some say to install a program on pc then go in download mode and fix with the program but i unpluggrd my pc and tv because me and they got too old for eachother.
Now i am just trying different things what i see on youtube and twrp says this: check picture.
AC420 said:
I am surei have the older backup in my internal storage of my phone but i dont know from where to recover that and on the internet they say everything and i am scared to make it worse than it is. I didnt use the phone for a long time because my lcd got a short circuit and i replacet it. On internet they say this bootloop problem can occure when you skip some updates some say to install a program on pc then go in download mode and fix with the program but i unpluggrd my pc and tv because me and they got too old for eachother.
Now i am just trying different things what i see on youtube and twrp says this: check picture.
Click to expand...
Click to collapse
I've had this ****, i just used abd to flash a new twrp img and dirty flashed the ROM after it flashed magisk back on again, only problem I got was safety new which idk how I solved but I think was using lsposed
Dear comunity,
I really need your help with this. I have a OP6T and finally updated to the android 11. Before the update, I removed magisk (it was giving me some errors from time to time and I wasn't using the root for anything) through TWRP and then I just updated to the latest OOS through OTA. Everything went smoothly until today, when I went to a store and tried to pay using google pay an error appeared and it seems I have no longer the device certified by the play protect.
What did I miss during the update? Is there any workaround?
Thank you in advance!
I would try wiping and installing the latest oos through twrp instead of ota
I just did this to have everything stock again. Since I installed via OTA, didn't I loose the twrp recovery? Wiping are you referring to a complete clean install? I'm not quite prepared for that :|
igoigo said:
I just did this to have everything stock again. Since I installed via OTA, didn't I loose the twrp recovery? Wiping are you referring to a complete clean install? I'm not quite prepared for that :|
Click to expand...
Click to collapse
I don't understand why it would not be certified after ota update. You can try uninstalling updates for play services and play store maybe that will help. Or there might be magisk files that persisted. Could try to root with magisk again and uninstall it using the magisk app. Just ideas for ya cause I really don't know for sure. But I do know for sure even with stock oos you can still boot a twrp and use it even if you dont make it permanent. So you could use twrp to delete magisk or anything that would be throwing off the safety net. Could also try a safety net checking app to narrow down the problem depending if it passes or not. I just suggested clean install because there may be conflicting device names or whatever from going from custom to ota update. Hope it helps
Brettroth said:
I don't understand why it would not be certified after ota update. You can try uninstalling updates for play services and play store maybe that will help. Or there might be magisk files that persisted. Could try to root with magisk again and uninstall it using the magisk app. Just ideas for ya cause I really don't know for sure. But I do know for sure even with stock oos you can still boot a twrp and use it even if you dont make it permanent. So you could use twrp to delete magisk or anything that would be throwing off the safety net. Could also try a safety net checking app to narrow down the problem depending if it passes or not. I just suggested clean install because there may be conflicting device names or whatever from going from custom to ota update. Hope it helps
Click to expand...
Click to collapse
Thank you for the suggestions. I installed root checker and it didn't detect any root. I was thinking on installing again TWRP to then install/uninstall magisk. But I can try to check the safety net, its strange indeed, I have everything working without any problems, even the google or bank apps.
When I uninstalled magisk I had to do it through TWRP because my magisk manager that was in "hide mode" woulnd't open because it was constantly crashing. As you said, probably there is some remnant files from magisk left.
EDIT: I run the safety checker and it found a problem with "CTS profile matched", any idea what is this?
igoigo said:
Thank you for the suggestions. I installed root checker and it didn't detect any root. I was thinking on installing again TWRP to then install/uninstall magisk. But I can try to check the safety net, its strange indeed, I have everything working without any problems, even the google or bank apps.
When I uninstalled magisk I had to do it through TWRP because my magisk manager that was in "hide mode" woulnd't open because it was constantly crashing. As you said, probably there is some remnant files from magisk left.
EDIT: I run the safety checker and it found a problem with "CTS profile matched", any idea what is this?
Click to expand...
Click to collapse
Basically has 2 different ID's probably from going custom to ota update. That's why I suggested clean install. Anytime going from one rom to another clean install is needed.
@Brettroth the thing is, I was/am in the stock rom, the only thing I had "custom" was the magisk (which I uninstalled before update) and TWRP recovery :|
igoigo said:
@Brettroth the thing is, I was/am in the stock rom, the only thing I had "custom" was the magisk (which I uninstalled before update) and TWRP recovery :|
Click to expand...
Click to collapse
Sorry I thought you were on custom
igoigo said:
@Brettroth the thing is, I was/am in the stock rom, the only thing I had "custom" was the magisk (which I uninstalled before update) and TWRP recovery :
Click to expand...
Click to collapse
You should be able to just dirty flash the oos from twrp then. Should fix any mismatched id's
I will try the dirty flash through twrp
Brettroth said:
You should be able to just dirty flash the oos from twrp then. Should fix any mismatched id's
Click to expand...
Click to collapse
Finally got some time during my holidays to try this, but now I'm facing some problems. I tried to fastboot flash the TWRP version that you suggested in another thread but the recovery can't read my storage due to encryption. Do you have any suggestion?
igoigo said:
Finally got some time during my holidays to try this, but now I'm facing some problems. I tried to fastboot flash the TWRP version that you suggested in another thread but the recovery can't read my storage due to encryption. Do you have any suggestion?
Click to expand...
Click to collapse
This will decrypt android 12
Brettroth said:
This will decrypt android 12
Click to expand...
Click to collapse
But I'm with in Android 11 stock ROM (11.1.2.2) will it work?
igoigo said:
But I'm with in Android 11 stock ROM (11.1.2.2) will it work?
Click to expand...
Click to collapse
Yeah it should. The other twrp should have worked also with a11. You might have corrupted your data. Probably need to wipe data by typing yes to fix.
How can I have corrupted my data by just flashing the recovery? Can't I flash the stock boot.img?
EDIT:
I was able to flash the stock boot.img and everything is working now. Starting again, what do you suggest, boot TWRP and then instal zip and flash OOS+TWRP? My problem is, which TWRP version should I boot and flash, since the one I tested gave this problem.
Hi, my case is a bit different as i havent used magisk and i have a difderent phone, but my solution to "device is not play store certified" which was showing in play store, about section was as follows:
Enable Developper mode (setting/about/software info/click 7 times or so on "build number")
A developer menu appears in settings at the bottom, within it i disabled "OEM Unlocking".
Restarted phone checked, was still not certified, cleared data for "google play services" and "google play store", restarted, and voila.
Hope it helps