Related
As the title implies, i wanted to give XT1562_LUX_RETASIA_DS_6.0.1_MPD24.107-70 a shot. Flashing works fine. I can boot the system, SIMs and WLAN work. TWRP 3.0.2-r3 works.
What doesn't work is supersu. I tried 2.62 and 2.76 both, it installs in system mode, then gets stuck while booting. 2.76 on the "M powered by android" boot image, before the "globe" animation started, and 2.62 after the globe animation. I wiped cache/dalvik, tried not wiping it, no-go. Just restarting the MXP doesn't help either.
Are there more things i could try, is anyone using that firmware yet? Which supersu? Do i have to factory reset before using supersu maybe?
Booting into recovery immediatly after flashing in fastboot doesn't work, as the internal sd cannot be mounted by twrp unless the system booted once.
It needs to be systemless, mate
http://forum.xda-developers.com/showpost.php?p=66735900&postcount=126
I have also flashed the same firmware using rsd lite.Then flashed twrp-lux-2.8.7-r4 through adb.After that just flashed supersu 2.62 normally and everything is working fine.I do not know what is systemless root and how it is done.But the normal flashing has worked for me.
situ1962 said:
I have also flashed the same firmware using rsd lite.Then flashed twrp-lux-2.8.7-r4 through adb.After that just flashed supersu 2.62 normally and everything is working fine.I do not know what is systemless root and how it is done.But the normal flashing has worked for me.
Click to expand...
Click to collapse
Um, I'm a noob so may I ask what i systemless?
minimale_ldz said:
It needs to be systemless, mate
http://forum.xda-developers.com/showpost.php?p=66735900&postcount=126
Click to expand...
Click to collapse
Thank you, i had been looking for this. The stupid blogs i googled regarding systemless only said supersu would choose it automatically if it had to. WELL APPARENTLY NOT
@HerySean
Unlike a "system" root the "systemless" approach does not actually modify your rom. It does some trickery while booting to achieve the same. Advantage: There won't be any bootloops ever, if a problem occurs you just won't have root. Also stuff like google pay. Disadvantages: A factory wipe will wipe a systemless root.
AtomicStryker said:
Thank you, i had been looking for this. The stupid blogs i googled regarding systemless only said supersu would choose it automatically if it had to. WELL APPARENTLY NOT
@HerySean
Unlike a "system" root the "systemless" approach does not actually modify your rom. It does some trickery while booting to achieve the same. Advantage: There won't be any bootloops ever, if a problem occurs you just won't have root. Also stuff like google pay. Disadvantages: A factory wipe will wipe a systemless root.
Click to expand...
Click to collapse
Oh I get it, thanks, the same thing I did back then to my Xperia C
Are there more steps to this? The systemless root seems to work fine, i boot, but the supersu app claims the device is not rooted....
btw, does it bring a new baseband? edit: doesn't seem so new actually
After several attempts 2.62 worked after all, in system mode even. I don't even know.
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
I just got my unlocked G5 Plus (XT1687) today and I've unlocked the bootloader and installed TWRP and SuperSU.
However, SuperSU seems to be randomly losing root access. It works for a little while, but then I'll get an error in SuperSU about root undetected and I have to reboot back into TWRP and reflash SuperSU. This has happened 3 times so far today.
Has anyone seen this issue in the stock rom? Is there some security process stealthily running in the background that deletes the su binary on a regular basis? I'm running build number NPN25.137-33.
Edit: SuperSU is running in systemless mode
I rooted mine using the Toolkit here yesterday and that afternoon it acted like i lost root. Root checker would say i didn't have root and just constantly flash that it was trying to get permission. I restarted it and it's been fine ever since.
I tried rebooting and it restores root temporarily, but I'm still losing it constantly (no set time interval, but I've seen it lost within a few minutes of a restart). Getting really annoying.
Would flashing one of the modified stock kernels potentially help this?
Hi,
I've the same problem. XT1685
Already done:
- reflash stock
- reflash updated stock
- reflash SuperSu 2.82 SR3 and SR4
Ever the same, after some (short) time the root is lost.
Unrooted from SuperSu app and installed Magisk 14.0: loses root after some moments!
Edit: after some reboots now its working. The root is maintained from 2 days. So Magisk 14.0 works.
Hi.
Here another confirmation. My XT1687 loses root rights once in a while. I’d say it’s about every 3rd day or so.. Simple reboot brings root rights back.
Config:
Build: NPN25.137-83
Kernel: 3.18.31-ElementalX
Root: Magigk 14.0
EDIT: When checking Magisk App I found out that Magisk crashed each time I started Superuser. So, I deinstalled Magisk and re-installed again. No problem ever since.
Always remember to un-optimize Magisk- (or SuperU-) App in battery options! "Boeffla-Doze-Control" also helps to avoid apps from falling asleep.
On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su
Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD
No root losses anymore
Just_a_fan said:
Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD
Click to expand...
Click to collapse
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...
G5 Plus Mate said:
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...
Click to expand...
Click to collapse
Like I said, installing Magisk returns an error.
Nevertheless, after I ran the command from @highwaystar2699 and canceled the battery-optimization of SuperSU I've got still root after already 5 days of using the phone.
So, thanks for your help, for now =)
I have no ideas that you can solve your problem ...
What I got interested in your post(#8) is "I also uninstalled SuperSU over apps on Stock Rom".
If there is no mistake in my memory, SuperSU have an "unroot" menu, which should be used to uninstall SuperSU.
Did you uninstall by using "unroot" menu?
In any case, I am not sure how to recover the state of your g5plus.
I will not be able to help you. sorry.
highwaystar2699 said:
On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su
Click to expand...
Click to collapse
How and where to run this code? Fastboot or adb terminal?
sudiptoc19 said:
How and where to run this code? Fastboot or adb terminal?
Click to expand...
Click to collapse
Just boot into TWRP and open the terminal (you can find it under "advanced" or "tools", not completely sure right now) and run that command. Maybe you should check where the mentioned su-folder is located right now on your phone, 'cause in my case it was at a different location.
@highwaystar2699: Yeah, afterwards I also realized that unroot-option
So maybe I have to unroot with that option and retry to install magisk. I will try that maybe, if I should loose root again. Or when the next update comes. (I'm a little afraid about that. Sounds difficult to OTA-update after rooting your G5 Plus...)
Either way: Thanks for your help! If I try something, I will report about it here
Super SU working for G5 plus. I don't think so. It has some problems. Bootloops are frequent.
Sooooo, hello again all! @highwaystar2699: I lost root again after one hour when I had to reboot the phone so I just thought about: "Why don't give it a try now?"
So I flashed the superSU again in TWRP to get root, startet the SuperSU app and choose "Unroot". I was asked if I want to unroot because of an OTA update, which I answered with "no". The app closed and root was gone.
I rebooted into recovery and tried to install the magisk 16.0 zip aaaaaaannnnd...
...got Error 1 again.
At the point "Unmounting partitions", TWRP says
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v16.0.zip'"
Now I'm back to superSU again. Damn, I don't know whats wrong here =(
Short edit for @Yeshu_bablu: Yes, after installing superSU, you've got 2 to 3 bootloops. But only the first time. After it's installed, the phone boots normal.
So, according to you... Which is better? SuperSU or Magisk?
SuperSU is obsolete, twrp you need latest version 3.2.1.0 or higher number if updated.
Once twrp installed you can install the rom of your choice with or without gapps package of your choice.
Then you can install magisk 16.3 for root and modules if wanted.
Yeshu_bablu said:
So, according to you... Which is better? SuperSU or TWRP?
Click to expand...
Click to collapse
SuperSu is root, TWRP is recovery, 2 different things.
[email protected] said:
SuperSu is root, TWRP is recovery, 2 different things.
Click to expand...
Click to collapse
I'm sorry, SuperSu or Magisk?
Short update and big thanks to @highwaystar2699 and @Wolfcity.
After I completely lost root with SuperSU, I tried to install Magisk but failed everytime with already known Error 1.
But finally, after I got a stock boot.img and flashed it and instantly (!) installed Magisk after flashing the boot.img, the phone startet normal and now I've got root without problems.
FIY: When I only flash the boot.img and don't root it in TWRP, the phone keeps bootlooping.
So, to give @Yeshu_bablu an answer: Magisk is better. SuperSu only make problems with Moto G5 Plus. Magisk works like a charm.
Hi guys im having an odd issue, as you read my keyboard is gone after flashing latest magisk version on my Huawei P9 lite
My step by step was:
1) unlocked bootlader, everything went smooth
2) installing Elite TWRP, fine too (it didnt ask for encryption password when it start)
3) flashed latest magisk from TWRP and made a clear cache, reboot phone
4) when system started it asked for "Type password to decrypt storage" i assumed that is asking for the pin, but my problem starts when i touched to start writing my password... no keyboard appear to write it! :.(
5) rebooted to try again but still no keyboard, re-flashed magisk using the terminal commands
echo KEEPVERITY=false>>/data/.magisk
echo KEEPFORCEENCRYPT=false>>/data/.magisk
6) no luck, there´s still no keyboard.
Device specs:
Model: VNS-L23
Compilation: VNS-L23C52
EMUI: 5.0.3
Android: 7.0
im out of ideas now, can anyone give me a hand to fix it? it will be appreciated!
Thanks again
matias.simonetti said:
Hi guys im having an odd issue, as you read my keyboard is gone after flashing latest magisk version on my Huawei P9 lite
My step by step was:
1) unlocked bootlader, everything went smooth
2) installing Elite TWRP, fine too (it didnt ask for encryption password when it start)
3) flashed latest magisk from TWRP and made a clear cache, reboot phone
4) when system started it asked for "Type password to decrypt storage" i assumed that is asking for the pin, but my problem starts when i touched to start writing my password... no keyboard appear to write it! :.(
5) rebooted to try again but still no keyboard, re-flashed magisk using the terminal commands
echo KEEPVERITY=false>>/data/.magisk
echo KEEPFORCEENCRYPT=false>>/data/.magisk
6) no luck, there´s still no keyboard.
Device specs:
Model: VNS-L23
Compilation: VNS-L23C52
EMUI: 5.0.3
Android: 7.0
im out of ideas now, can anyone give me a hand to fix it? it will be appreciated!
Thanks again
Click to expand...
Click to collapse
install older magisk.
RyotaGamer said:
install older magisk.
Click to expand...
Click to collapse
Thanks i will try that, should i flash a clean stock rom and start the process again or just install the older version of magisk over the latest already installed?
thanks again for your help!
matias.simonetti said:
Thanks i will try that, should i flash a clean stock rom and start the process again or just install the older version of magisk over the latest already installed?
thanks again for your help!
Click to expand...
Click to collapse
use magisk uninstaller in TWRP and install older magisk.
RyotaGamer said:
use magisk uninstaller in TWRP and install older magisk.
Click to expand...
Click to collapse
thanks already restored system and unlock it again, im about to flash twrp.
should magisk v17 do the trick?
matias.simonetti said:
thanks already restored system and unlock it again, im about to flash twrp.
should magisk v17 do the trick?
Click to expand...
Click to collapse
install 19.2 first. if device still locked, install older version from you installed.
and, don't overwrite magisk. you should run uninstaller before install magisk.
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