Mod edit: THREAD CLOSED on request of OP.
Has anyone taken the full update then pushed twrp then installed twrp and the magisk.
I just did this after the update and if twrp is flashed alone the ROM boots. If I flash magisk 19.3 the ROM boots to lock screen then reboots to recovery. Is there a new magisk needed to fix this, or is it something I might have done. I have updated this way 3 times so far
Did you flash the magisk uninstaller in twrp before flashing the rom update?
__NBH__ said:
Did you flash the magisk uninstaller in twrp before flashing the rom update?
Click to expand...
Click to collapse
No never had. I let my phone flash the full ROM not ota. Reboot all works fine
Reboot to fastboot
Fastboot boot twrp
Flash twrp installer.
Flash magisk.
Reboot.
I didn't uninstall no limits Rom, and that may be the cause I guess. Have done it this way 3 times so far but didn't have this problem ever the way I have done it
toolhas4degrees said:
No never had. I let my phone flash the full ROM not ota. Reboot all works fine
Reboot to fastboot
Fastboot boot twrp
Flash twrp installer.
Flash magisk.
Reboot.
I didn't uninstall no limits Rom, and that may be the cause I guess. Have done it this way 3 times so far but didn't have this problem ever the way I have done it
Click to expand...
Click to collapse
I downloaded 9.0.15 via OTA, rebooted in twrp without installed It. After flashed zip I flashed twrp zip and rebooted in system. After that I rebooted in twrp and installed magisk but puff, when I rebooted in system, it turned off so I did from beginning but before I uninstalled magisk and It worked.
lorenzomeini56 said:
I downloaded 9.0.15 via OTA, rebooted in twrp without installed It. After flashed zip I flashed twrp zip and rebooted in system. After that I rebooted in twrp and installed magisk but puff, when I rebooted in system, it turned off so I did from beginning but before I uninstalled magisk and It worked.
Click to expand...
Click to collapse
But before you uninstalled it worked...? I don't follow
toolhas4degrees said:
But before you uninstalled it worked...? I don't follow
Click to expand...
Click to collapse
Judging from the way he uses his verbs, "before I uninstalled it" means, "this time I uninstalled it BEFORE updating."
I think he is saying to uninstall Magisk before updating. Maybe it would be best to uninstall your No Limits ROM first, this time around, since it doesn't seem to be working, even though it has in the past.
I got lucky--mine worked just fine for me, but I came from an OxygenOS ROM prior to the upgrade, and forgot to uninstall Magisk.
The upgrader told me that I would lose root and I did, but it's too easy to put it back in, and the update runs like a dream.
pbergonzi said:
Judging from the way he uses his verbs, "before I uninstalled it" means, "this time I uninstalled it BEFORE updating."
I think he is saying to uninstall Magisk before updating. Maybe it would be best to uninstall your No Limits ROM first, this time around, since it doesn't seem to be working, even though it has in the past.
I got lucky--mine worked just fine for me, but I came from an OxygenOS ROM prior to the upgrade, and forgot to uninstall Magisk.
The upgrader told me that I would lose root and I did, but it's too easy to put it back in, and the update runs like a dream.
Click to expand...
Click to collapse
You say right man
pbergonzi said:
Judging from the way he uses his verbs, "before I uninstalled it" means, "this time I uninstalled it BEFORE updating."
I think he is saying to uninstall Magisk before updating. Maybe it would be best to uninstall your No Limits ROM first, this time around, since it doesn't seem to be working, even though it has in the past.
I got lucky--mine worked just fine for me, but I came from an OxygenOS ROM prior to the upgrade, and forgot to uninstall Magisk.
The upgrader told me that I would lose root and I did, but it's too easy to put it back in, and the update runs like a dream.
Click to expand...
Click to collapse
I came from oos also 9.0.1.4 was updated from oos in oos... but no limits is a magisk module
pbergonzi said:
Judging from the way he uses his verbs, "before I uninstalled it" means, "this time I uninstalled it BEFORE updating."
I think he is saying to uninstall Magisk before updating. Maybe it would be best to uninstall your No Limits ROM first, this time around, since it doesn't seem to be working, even though it has in the past.
I got lucky--mine worked just fine for me, but I came from an OxygenOS ROM prior to the upgrade, and forgot to uninstall Magisk.
The upgrader told me that I would lose root and I did, but it's too easy to put it back in, and the update runs like a dream.
Click to expand...
Click to collapse
I came from oos also 9.0.1.4 was updated from oos in oos... but no limits is a magisk module
just when i try to flash magsk and reboot i have issue. gonna try a dat wipe after i back my gar up
Related
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.
DirtyHennessy said:
I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.
Click to expand...
Click to collapse
Thanks! I will try that.
Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Have you made sure to update your radio, bootloader and vendor to the most recent version? Make sure to also try flashing twrp again but do everything through fastboot flash commands on your pc.
Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Flash root in TWRP before your first boot into the stock rom. On Nougat 7.0+, stock recovery replaces TWRP on boot if you do not. This solves both of your problems. When you clean flash and install a custom rom, with or without root, TWRP will remain. If you just use stock unrooted, then you should flash root before first boot each month when you update.
Sent from my Nexus 5X using Tapatalk
SuperSu 2.80 & 2.81 broke root for most phones - including mine. I had to flash 2.79 SR3 to get root again. Chainfire released 2.82 this morning but I haven't tried it yet.
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
If you boot to twrp first time mount system and use the filemanager to delete recovery-from-boot.p under system. Use magisk instead of supersu for root.
So I'm trying the Magisk root mode instead of SuperSU. This is my first time messing with Magisk.
I flashed the lastest OOS version and flashed the Magisk zip.
I went to the dowload modules section and installed a bunch of modules without rebooting immediatly. After all installed I rebooted and to my surprise, the phone didn't boot. It stays in the 1+ logo forever.
What have I done wrong? Installed wrong modules? Should I reboot after each module installed?
I flashed the ROM back, wiped cache and dalvik and flashed Magisk again and still the phone isn't booting..
EDIT: Flashed the ROM again without Magisk or SuperSU and it booted, but somehow I lost the TWRP recovery!
Great now it will wipe my phone to install the TWRP recovery again..
These are my favorites so far, I am so happy with them
gonsa said:
So I'm trying the Magisk root mode instead of SuperSU. This is my first time messing with Magisk.
I flashed the lastest OOS version and flashed the Magisk zip.
I went to the dowload modules section and installed a bunch of modules without rebooting immediatly. After all installed I rebooted and to my surprise, the phone didn't boot. It stays in the 1+ logo forever.
What have I done wrong? Installed wrong modules? Should I reboot after each module installed?
I flashed the ROM back, wiped cache and dalvik and flashed Magisk again and still the phone isn't booting..
EDIT: Flashed the ROM again without Magisk or SuperSU and it booted, but somehow I lost the TWRP recovery!
Great now it will wipe my phone to install the TWRP recovery again..
Click to expand...
Click to collapse
It won't wipe your phone if you simply run it in fastboot and flash the TWRP recovery. The only reason it wipes the first time is because you had to do an oem unlock, which is already done now. The only time you will have to wipe your whole phone from now on is if you decrypt, and with ROMs starting to work with encryption, that shouldn't need to be done.
For the boot loop, my guess is a bad module.
To get the phone working again, you did the correct thing in flashing the stock zip without Magisk. The only thing you needed to do right after that was flash TWRP recovery image again through TWRP to overwrite the stock recovery. Then you would boot up, uninstall the modules, and reflash Magisk.
The only Magisk module I use is the stock Google Dialer/Contacts mod.
chazarss said:
These are my favorites so far, I am so happy with them
Click to expand...
Click to collapse
Wow. Didn't knew there are so many modules just for OP5. Guess it's time to root.
Does using doze for Google play services causes any notification issues? Delay etc.
naturist said:
Wow. Didn't knew there are so many modules just for OP5. Guess it's time to root.
Does using doze for Google play services causes any notification issues? Delay etc.
Click to expand...
Click to collapse
None any issue, just flash and relax
ArkAngel06 said:
It won't wipe your phone if you simply run it in fastboot and flash the TWRP recovery. The only reason it wipes the first time is because you had to do an oem unlock, which is already done now. The only time you will have to wipe your whole phone from now on is if you decrypt, and with ROMs starting to work with encryption, that shouldn't need to be done.
For the boot loop, my guess is a bad module.
To get the phone working again, you did the correct thing in flashing the stock zip without Magisk. The only thing you needed to do right after that was flash TWRP recovery image again through TWRP to overwrite the stock recovery. Then you would boot up, uninstall the modules, and reflash Magisk.
The only Magisk module I use is the stock Google Dialer/Contacts mod.
Click to expand...
Click to collapse
thank you for your explanation. I managed to install the TWRP recovery again. what's happening now is I flash the ROM and it boots. I flash Magisk and it doesn't boot. I flash the ROM again and then SuperSU and it works. What I think is happening now is when I flash Magisk it might load the modules that don't work and it won't boot. Is there a way to know if the modules are installed in the background?
What I did now was flash the Magisk uninstaller and flashed the SuperSU and it's working.
Check out this guide I wrote!
https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727
Im_Mattgame said:
Check out this guide I wrote!
https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727
Click to expand...
Click to collapse
I llaughed out loud when I read the "Flash Stock Recovery - Step 7/ Ponder for a minute at how useless it is"
You guide is good but not for my situation. I can boot, just not with Magisk. The thing was, I installed a lot of Magisk modules all at once, like Viper4Android, Emoji one module, and a bunch of more. Then rebooted and it bootlooped.
Would like to get center clock on the status bar. Is there a module that does this?
the_rooter said:
Would like to get center clock on the status bar. Is there a module that does this?
Click to expand...
Click to collapse
Substratum is your answer to that question. I haven't tried any full themes since our recovery is still a working mess it seems, so I'm worried about backups. But the Ozone Substratum module works well. I just made my clock centered with small date and am/pm. Persists through dirty flashes too.
the_rooter said:
Would like to get center clock on the status bar. Is there a module that does this?
Click to expand...
Click to collapse
This will do it
https://forum.xda-developers.com/oneplus-5/themes/v3-1-ozone-substratum-module-oos-t3627336
gonsa said:
thank you for your explanation. I managed to install the TWRP recovery again. what's happening now is I flash the ROM and it boots. I flash Magisk and it doesn't boot. I flash the ROM again and then SuperSU and it works. What I think is happening now is when I flash Magisk it might load the modules that don't work and it won't boot. Is there a way to know if the modules are installed in the background?
What I did now was flash the Magisk uninstaller and flashed the SuperSU and it's working.
Click to expand...
Click to collapse
I haven't had to mess around with uninstalling Magisk modules, but I assume the method to uninstall a module would be to
Flash system zip
Flash TWRP recovery
Boot into phone
Run the Magisk manager app without actually having Magisk installed
Uninstall or disable the modules
Then install Magisk
gonsa said:
I llaughed out loud when I read the "Flash Stock Recovery - Step 7/ Ponder for a minute at how useless it is"
You guide is good but not for my situation. I can boot, just not with Magisk. The thing was, I installed a lot of Magisk modules all at once, like Viper4Android, Emoji one module, and a bunch of more. Then rebooted and it bootlooped.
Click to expand...
Click to collapse
Ah okay I see, then yeah it is maybe an incompatibility issue with one of the modules, mind listing all of them, I'll try and figure out which one is causing the Bootloop ?
chazarss said:
These are my favorites so far, I am so happy with them
Click to expand...
Click to collapse
Where I can find those zips?
FloyderE said:
Where I can find those zips?
Click to expand...
Click to collapse
just google it man
gonsa said:
So I'm trying the Magisk root mode instead of SuperSU. This is my first time messing with Magisk.
I flashed the lastest OOS version and flashed the Magisk zip.
I went to the dowload modules section and installed a bunch of modules without rebooting immediatly. After all installed I rebooted and to my surprise, the phone didn't boot. It stays in the 1+ logo forever.
What have I done wrong? Installed wrong modules? Should I reboot after each module installed?
I flashed the ROM back, wiped cache and dalvik and flashed Magisk again and still the phone isn't booting..
EDIT: Flashed the ROM again without Magisk or SuperSU and it booted, but somehow I lost the TWRP recovery!
Great now it will wipe my phone to install the TWRP recovery again..
Click to expand...
Click to collapse
Keep in mind that everytime you update your phone it will also install stock recovery. So you'll need to re-install twrp after every oos update.
I have no module installed but I use other apps that needs root.
Btw can anyone comment on atmos or viper4android, does your phone/headphone sound any better?
chazarss said:
None any issue, just flash and relax
Click to expand...
Click to collapse
How big of a difference on battery have you noticed using this doze Google play services module?
sl___ said:
How big of a difference on battery have you noticed using this doze Google play services module?
Click to expand...
Click to collapse
Not realy I can't say that really can fell
chazarss said:
These are my favorites so far, I am so happy with them
Click to expand...
Click to collapse
So for the YouTube no ads, which one did you use, generic or Vance or black Vance?
Aldo for the arise module, do you have a link? I can't find it searching. Thanks.
i am using black version, so far soo good
Arise comes with magisk module in latest version from here https://www.androidfilehost.com/?w=files&flid=176171 but it is little complicated to install. but you can follow here for instuctions http://www.droidviews.com/install-arise-magnum-opus-sound-mod-android/
Ok, why the f. did I get "installation failed" when installing OTA following this guide?
I followed the guide, I hit uninstall and "restore images" in magisk, it restored the stock image and when I tried running feb ota, I got "installation failed", why?
Also, why did my device get in a bootloop by just fully uninstalling magisk?
I had unlocked bootloader with systemless root, with no TWRP, never booted it, never flashed it, only fastboot commands I ran were oem unlock and boot patched_boot.img. I never touched system partition (on purpose), never installed anything other than a bunch of magisk modules, safetynet was always working, if it matters.
PSA FOR GOOGLE VISITORS:
Do not fully uninstall magisk after you get "installation failed", I got a bootloop and had to flash flash_all_except_storage.bat from mi a1 stock rom using miFlash (bottom right to select it, don't flash_all if you want your data).
Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....
Azeemkwow said:
Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....
Click to expand...
Click to collapse
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.
Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.
Alanjameson99 said:
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.
Click to expand...
Click to collapse
Thanks...now that's what I'm planning to do...install official rom through miflashtool
RavinduSha said:
Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.
Click to expand...
Click to collapse
Does the 'save user data'-option also preserve the apps installed?
Thanks!
Tiemichael said:
Does the 'save user data'-option also preserve the apps installed?
Thanks!
Click to expand...
Click to collapse
Yes it saves all user data including settings, apps and app data
I had the same issue. I used the tool linked below and the steps:
- Unlock Bootloader
- Flash Stock ROM
- Download ROM (and wait for that to happen)
- Keep UserData (and wait again)
- Lock Bootloader
After that I was able to install the update, then re-install Magisk and camera tweaks.
https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
The guide mention in OP had worked for me for at least 3 updates including the major one from nougat to oreo with any issue. Be aware that mounting system partition as read AND WRITE brakes OTA. You don't even need to change anything just mounting it will brake it. That could easily happen using a root file explorer or a hosts file based add blocker if Magisk is not properly set (systemless hosts support toggle in Magisk settings).
I am in need of assistance.
I am using a OnePlus 8 Pro (EUR)
After using stock magisk rooted OOS 10 for quite a while I updated to OOS 11 and rooted it again.
All goes well until an hour or 2 have been passed.
After those 2 hours my banking apps won't show anything more than a blank screen. Some apps won't open or start freezing on launch. All with Magisk Hide enabled.
Strangely enough, Magisk manager still says that I'm passing safetynet.
I have tried to root my OP8Pro on OOS 11 several times but I will get these problems eventually. Sometimes combined with a bootloop.
Has anyone else also had this. And if so, is there a way to fix this? I would be glad if I can root my phone again.
Help will be appreciated.
ps: I am aware that this thread has to be moved somewhere else.
I really don't know what's causing the issue you're having but I highly recommend to do a backup and then factory reset, it could fix all the issues
I was having reboot and freeze issues. I had to follow the unbrick method for a full clean slate, have been good since aside from some rogue apps lol
Sounds like you've booted the magisk patched IMG and then not made it permanent by installing directly afterwards.
Apps can begin to fail after turning on systemless in magisk. You are meant to reboot which would inadvertently disable root if you haven't installed directly after booting like I said
If you have 100% installed directly and it survives a reboot then it is more than likely your boot IMG, reobtain another and patch it with the latest magisk beta. Then boot it then install directly.
Reboot to see if it's taken.
Then go systemless and magisk hide.
Then reboot.
dladz said:
Sounds like you've booted the magisk patched IMG and then not made it permanent by installing directly afterwards.
Apps can begin to fail after turning on systemless in magisk. You are meant to reboot which would inadvertently disable root if you haven't installed directly after booting like I said
If you have 100% installed directly and it survives a reboot then it is more than likely your boot IMG, reobtain another and patch it with the latest magisk beta. Then boot it then install directly.
Reboot to see if it's taken.
Then go systemless and magisk hide.
Then reboot.
Click to expand...
Click to collapse
Ok, I will try it out, thanks!
Apexrajang said:
Ok, I will try it out, thanks!
Click to expand...
Click to collapse
Very welcome sir
some of my bank apps only work with private dns, for some reason, otherwise they show random bugs about "slow connection" or whatever
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