Hello, recently I refleshed the latest stock rom using odin.
Previously I had magisk installed with xposed.
Root and xposed seem to be gone, but saftynet still fails.
Basic integrity is false and cts mismatch is thrown.
So I would like to know how can I go back to stock completly, wipe everything and reinstall stock rom.
Odin flash does not seem to delete user data.
Might there be something on the data partition left over that triggers safety net ?
I solved it by myself.
It seems that even though the system was stock the saftynet somehow remembered that the device was modified in the past so that's why it still failed.
After a factory reset safetynet is happy.
I think I will leave root alone for now as I don't really need it.
Related
I have root all verified and supersu installed correctly & twrp custom recovery. However I tried installing a sound mod but just reboots & nothing. Same with dpi changer.
Is there some file that is somehow protecting any changes to be made even though I have root access?
Many Thanks In advance.
Duncan1982 said:
I have root all verified and supersu installed correctly & twrp custom recovery. However I tried installing a sound mod but just reboots & nothing. Same with dpi changer.
Is there some file that is somehow protecting any changes to be made even though I have root access?
Many Thanks In advance.
Click to expand...
Click to collapse
Maybe install busybox from Ericsson
Thanks I have busy box installed, this is very odd it is like there is a security file blocking everything despite root.
Xblast works as I have the clock centred and circle battery.
I am Experienced in root, and haven't stumbled upon this before.
Was thinking it was 4.4.4 but others are having success.
Hmmmm baffled.
Maybe has something to do with the security settings?
Install if you like the Wanam module and check if Disable Secure storage is disabled.
Thats all i can think about for now.
Nope nothing, even tried changing secure storage value to false and upon hitting save it reboots and nowt.
I give up can't think of anything oh it could be AEA Kernel that perhaps is causing the problem?
The only way to find out if its the kernel you flashed. Re-flash the stock-kernel
Thanks for getting back, Yeh back to stock and same problem. Maybe for some reason only have partial root, can't see that as supersu is there and functional and I have twrp custom recovery. Hmmmmm the mind boggles lol.
Reasonably experienced root user and for the life of me I can't sus what's up.
Tried refreshing the AEA Kernel and it won't even do that now.
Not that it's important, was just after a sound mod & changing the Dpi down to 560. Tried both it won't change.
Some security thing is preventing this but what could it be?
With some 4.4.4 ROMs on the note 2, there were problems with getting "full" root using twrp. I don't know if this is relatedn but the symptoms sound similar. Solution there was to use philz recovery (which isn't an option here), or for some Roms to flash an older version of supersu in twrp and then update after starting. Could be worth a shot.
Did you make sure to open the SuperSU app after rooting and update the binary? Are you SELinux permissive?
If you are having issues, download the recovery version of SuperSU, install it, then make sure to open the app so it updates.
You could also disable SELinux through the build.prop. Having a kernel that is SELinux permissive doesn't matter if you still have everything enabled in the build.prop
Code:
(SELinux disable)
ro.build.selinux=0
(KNOX disable)
ro.config.tima=0
ro.config.knox=0
If none of that has helped, it is recommended you restore to stock and root again, making sure that reactivation lock is disabled before attempting to perform the root portion.
Hi All,
I had obtained root via CF-Autoroot and was using it with xposed for the last few weeks without issues. I took the lunge and tried to install phh super su, magisk systemless root. so the nightmare begins for me and i'm hoping it's an easy fix!
My system is still encrypted (I believe because TWRP can't see the system) SD card is fine. I've wiped my device a few times already and am hoping I don't need to wipe it again(prior to this setup).... So currently it's running fine without root access (How I hate android without root!!!)
- I've tried flashing Supersu zip in TWRP and it's failed - I believe it's not supported yet for encrypted devices.
-I've tried using the original CF-Autoroot method I used initially.
Both methods, it boots up straight away (no optimising apps) and after installing supersu app from playstore, it says no binaries found.
What are some ways I can inject root without wiping my device?
Please help me! Thankyou!
Maybe go back to the start and flash original FW through Odin and start from scratch, so you have a fresh phone to work with.
dwarfer66 said:
Maybe go back to the start and flash original FW through Odin and start from scratch, so you have a fresh phone to work with.
Click to expand...
Click to collapse
That's my plan when I get home tonight. I want to flash the original firmware file my phone started with (I'm assuming it won't delete anything?) and then run through the root steps again.. if it doesn't work, I'll wipe my phone and make sure I get rid of encryption this time..
kevinwu128 said:
That's my plan when I get home tonight. I want to flash the original firmware file my phone started with (I'm assuming it won't delete anything?) and then run through the root steps again.. if it doesn't work, I'll wipe my phone and make sure I get rid of encryption this time..
Click to expand...
Click to collapse
I think you will only lose stuff if you do a system reset after installing the original FW.
I only have had to do that on my tab S not my Edge after coming from a custom rom as I got slow down.
Resolved: flashed original rom and obtained root with cf-autoroot.
If someone has detailed instructions for magisk systemless root and xposed, it'd be much appreciated.. i want to have the option to use android pay or play pokemon go if i wanted. Thankyou
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??
hey all!
I'm a newb....
I have a rooted 6p with the factory image installed, twrp recovery.
I don't recall doing a backup before rooting.....yeah I know not smart....didn't know what the heck I was doing in this process....never rooted a phone.
I installed Magisk......then in my infinite wisdom installed supersu
the phone for the most part works fine, but I am having a problem running frida, it complains about magisk hide. I have removed all the magisk modules...
I am hoping I can some how clean up this phone and completely remove magisk.....and get frida running.
am I toast without a backup?
what is the best way to completely remove and uninstall magisk.
tried to run magisk install again and also magisk uninstall gives me error 1, which I see there are videos for dealing with on youtube...though haven't gone done that rabbit hole
I am quite comfortable using adb
I see bits of magisk all through the file system, just not sure if I should be deleting as I might be getting myself into more trouble.
TIA
Well if you don't mind starting fresh (backing up all your data) as this would erase everything and set your phone back to "factory stock" on the latest official version from google and its as easy as clicking one batch file to get things sorted. You may have messed up some stuff permanently on your system partition by installing/uninstalling two incompatible root solutions etc.
Link: https://developers.google.com/android/images#angler
Direct link to latest file: https://dl.google.com/dl/android/aosp/angler-opm7.181205.001-factory-b75ce068.zip
Then you just plug your phone in and run the 'flash-all.bat' file.
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