Related
I flashed the latest SuperSU zip with TWRP to a MotoG 2015 with the latest Lineage. After that, I noticed that there is a native SuperSU for Lineage, which I would prefer to use.
I was not able to find a "remove" package so I uninstalled the SuperSU app from the launcher. Now I'm not sure if that really removed everything from the system because I installed it in the first place by flashing it with TWRP.
My question is, can I safely install the native SuperSU (by flashing with TWRP) or do I have to remove any files from the former SuperSU manually?
There's a full unroot option in the app. Reinstall from the Play store and run that...
Or if you have any issue with the unroot option in the app, you can always flash the unSU Script zip from here.
Didgeridoohan said:
There's a full unroot option in the app. Reinstall from the Play store and run that...
Click to expand...
Click to collapse
You're right, I did not see that before. Works pretty good, now I've installed the native SuperSU and everything works fine. Thank you.
Whatever I do google just wont let me purchase anything.
When I try direct carrier billing it tells me that my account is risky.
When I try to use my credit card it tells me the card's been declined.
How do I know my account or phone has been blocked by google play?
It's because I went as far as using my laptop and creating a google account on it and then registering my credit card on the google play account via chrome and it worked!
I linked the new account that's has been linked to my credit card to my phones playstore and it still wouldn't allow me to buy in app purchases.
Is there anyway to reset my phone so google can let me make in apps again? Would a factory reset work?
I
blitzball said:
Whatever I do google just wont let me purchase anything.
When I try direct carrier billing it tells me that my account is risky.
When I try to use my credit card it tells me the card's been declined.
How do I know my account or phone has been blocked by google play?
It's because I went as far as using my laptop and creating a google account on it and then registering my credit card on the google play account via chrome and it worked!
I linked the new account that's has been linked to my credit card to my phones playstore and it still wouldn't allow me to buy in app purchases.
Is there anyway to reset my phone so google can let me make in apps again? Would a factory reset work?
Click to expand...
Click to collapse
Is this really a phone issue or issue with your Google account - have you eg tried from another Android phone with the same Google acc?
If you think it is phone issue, you didn't specify firmware you are running
- if stock, its full build name (to see also are you on MM, N or O)
- or some custom ROM
Is it rooted and how
- old, no more updated/supported SuperSU
- or Magisk
If Magisk, which version and does SafetyNet passes (all green)?
Btw, in Playstore, does it pass Play Protect, and in its Settings (last item) is Device Certified?
zgfg said:
I
Is this really a phone issue or issue with your Google account - have you eg tried from another Android phone with the same Google acc?
If you think it is phone issue, you didn't specify firmware you are running
- if stock, its full build name (to see also are you on MM, N or O)
- or some custom ROM
Is it rooted and how
- old, no more updated/supported SuperSU
- or Magisk
If Magisk, which version and does SafetyNet passes (all green)?
Btw, in Playstore, does it pass Play Protect, and in its Settings (last item) is Device Certified?
Click to expand...
Click to collapse
Both the phone and the account tbh. I tried said account on my laptop and it ran into the same error my phone had ran into - which is the inability to link any sort of credit card to it.
Even tried removing all my accounts, wiping playstore and all of the other google related apps of their data, and then making a fresh new account. It worked for maybe ten or fifteen minutes which was weird and then the account started having the error the previous accounts did.
Emui 5.0.1
Android 7.0
Build is an L19B393
It's rooted
Supersu
Yep it passes play protect and it's certified.
blitzball said:
Both the phone and the account tbh. I tried said account on my laptop and it ran into the same error my phone had ran into - which is the inability to link any sort of credit card to it.
Even tried removing all my accounts, wiping playstore and all of the other google related apps of their data, and then making a fresh new account. It worked for maybe ten or fifteen minutes which was weird and then the account started having the error the previous accounts did.
Emui 5.0.1
Android 7.0
Build is an L19B393
It's rooted
Supersu
Yep it passes play protect and it's certified.
Click to expand...
Click to collapse
Even if Play Protect passing, it automatically sends info about your (rooted) configuration to Google, so better disable it.
What about SafetyNet?
There are dedicated and more detailed checkers but you can also find it in some Root checkers like
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
With SuperSU you might need SuHide to pass SafetyNet, but that's why Magisk is better, it knows how to hide root and to pass SafetyNet
zgfg said:
Even if Play Protect passing, it automatically sends info about your (rooted) configuration to Google, so better disable it.
What about SafetyNet?
There are dedicated and more detailed checkers but you can also find it in some Root checkers like
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
With SuperSU you might need SuHide to pass SafetyNet, but that's why Magisk is better, it knows how to hide root and to pass SafetyNet
Click to expand...
Click to collapse
Yeah my phone fails at the SafetyNet check. Is there a guide on how to go from Supersu to Magisk?
blitzball said:
Yeah my phone fails at the SafetyNet check. Is there a guide on how to go from Supersu to Magisk?
Click to expand...
Click to collapse
You can Google but installation of Magisk for Huawei is specific (at least for Oreo, maybe also for Nougat).
First you need to get rid of SuperSU:
- Use its Uninstall/Remove root option and then reboot
- It should clean the Boot and System partitions from SuperSU changes
- If you made root changes in Data partition, you will need Factory Reset from Recovery
It will be safer that you also flash the clean7stock Boot partition:
- Download FullOTA update.zip from Firmware Finder, corresponding to your current firmware
- Unzip, open update.app in Huawei Update Extractor (PC app) and extract Boot.img
- Flash Boot.img in Fastboot or TWRP
(Ideally, you should reinstall stock firmware if you have had issues when installing SuperSU and left some mess in System from that time)
Second, about the installation of Magisk you can read this post (more info about Magisk in that thread):
https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
In short, you need to:
- Install latest Magisk Manager v6.01 (find it eg from the XDA Magisk thread above) and open it
- It will ask to install Magisk v17.1, decline and then check-in Preserve Force Encryption option
- Then click to install Magisk but instead of Direct Install take the option to patch Boot partition
- Navigate to the stock boot.img file (instructions above how to get it)
- Patched Boot will be saved to Downloads on Internal mem
- Flash that patched Boot, reboot, open Magisk Manager and let it complete the Magisk v17.1 installation
- Reboot, open Magisk Manager and trigger SafetyNet checking, allow it to install the needful
zgfg said:
You can Google but installation of Magisk for Huawei is specific (at least for Oreo, maybe also for Nougat).
First you need to get rid of SuperSU:
- Use its Uninstall/Remove root option and then reboot
- It should clean the Boot and System partitions from SuperSU changes
- If you made root changes in Data partition, you will need Factory Reset from Recovery
It will be safer that you also flash the clean7stock Boot partition:
- Download FullOTA update.zip from Firmware Finder, corresponding to your current firmware
- Unzip, open update.app in Huawei Update Extractor (PC app) and extract Boot.img
- Flash Boot.img in Fastboot or TWRP
(Ideally, you should reinstall stock firmware if you have had issues when installing SuperSU and left some mess in System from that time)
Second, about the installation of Magisk you can read this post (more info about Magisk in that thread):
https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
In short, you need to:
- Install latest Magisk Manager v6.01 (find it eg from the XDA Magisk thread above) and open it
- It will ask to install Magisk v17.1, decline and then check-in Preserve Force Encryption option
- Then click to install Magisk but instead of Direct Install take the option to patch Boot partition
- Navigate to the stock boot.img file (instructions above how to get it)
- Patched Boot will be saved to Downloads on Internal mem
- Flash that patched Boot, reboot, open Magisk Manager and let it complete the Magisk v17.1 installation
- Reboot, open Magisk Manager and trigger SafetyNet checking, allow it to install the needful
Click to expand...
Click to collapse
I have a TWRP backup of the stock boot.img. Would that work? It's in a .win format though and there are two files not sure how to convert them into .img.
Here's the exact names of the files:
boot.emmc.win
boot.emmc.win.md5
blitzball said:
I have a TWRP backup of the stock boot.img. Would that work? It's in a .win format though and there are two files not sure how to convert them into .img.
Here's the exact names of the files:
boot.emmc.win
boot.emmc.win.md5
Click to expand...
Click to collapse
TWRP backup that can be restored through TWRP (Restore option in TWRP)
zgfg said:
TWRP backup that can be restored through TWRP (Restore option in TWRP)
Click to expand...
Click to collapse
Thanks man. I'll go ahead and install magisk
zgfg said:
TWRP backup that can be restored through TWRP (Restore option in TWRP)
Click to expand...
Click to collapse
Dude so I installed it with no problems but I still can't pass safety net
blitzball said:
Dude so I installed it with no problems but I still can't pass safety net
Click to expand...
Click to collapse
As I wrote above, restore-reinstall + Factory reset complete stock firmware to get rid of SuperSU
With clean stock SafetyNet passes.
If it doesn't pass, you don't have clean and don't wastw time installing Magisk - first you must have clean basis
zgfg said:
As I wrote above, restore-reinstall + Factory reset complete stock firmware to get rid of SuperSU
With clean stock SafetyNet passes.
If it doesn't pass, you don't have clean and don't wastw time installing Magisk - first you must have clean basis
Click to expand...
Click to collapse
It's working now dude. I passed the safetynet! I still have one issue though... Even though I passed it, Netflix is still not available on my google playstore.
blitzball said:
It's working now dude. I passed the safetynet! I still have one issue though... Even though I passed it, Netflix is still not available on my google playstore.
Click to expand...
Click to collapse
Don't know, not using NetFlix. Make sure that PlayProtect and Device Certified pass in Playstore
zgfg said:
Don't know, not using NetFlix. Make sure that PlayProtect and Device Certified pass in Playstore
Click to expand...
Click to collapse
I have Netflix now. It's weird though cause only after maybe ten or twenty minutes did it show up in my store. Still can't buy anything though google still detects my phone for some reason. Thanks anyways.
I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?
@rovo89
@topjohnwu
https://www.didgeridoohan.com/magisk/MagiskHelp
I have added much more information.
Reinstall firmware???
LoneWolfz said:
Reinstall firmware???
Click to expand...
Click to collapse
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?
535iu said:
I'm going to do it today. Will I lose data if I install SYSTEM.img via Fastboot?
Click to expand...
Click to collapse
No maybe but i suggest you to backup all your data etc. just to be safe
Hello everyone and my apologies for my terrible English (I did this with the help of Google Translator) since I cannot find reliable information in my language (Spanish).
I just bought a Redmi 9T model M2010J19SG (4/64 GB, Android v10, MIUI v12.0.5, unmodified) and I would like to be able to restore some applications, as they were configured on my previous mobile (Galaxy S4 GT-I9500 Android v4.4.2 , rooted), for this I tried to use Titanium Backup Pro that I have been using for a long time for my backups and restorations but the Redmi does not allow it because I am not a root user on that phone.
Someone could help me, step by step, on how to install the appropriate TWRP on my Redmi 9T, to then be able to install and use the Magisk to root the phone and be able, using the Titanium, to restore those applications that interest me so much.
Thanks
First, unlock the bootloader by following this guide: https://romprovider.com/unlock-bootloader-redmi-9-power/?amp
Wait for 7 days max, and then try going to the fastboot mode and unlock it again. Do not log out your MIUI account on the device otherwise the timer would reset. Feel free to use the device while waiting, you wouldn't want to wait in the fastboot mode, do you? Hahaha jkkk
And then go to this post to download OrangeFox recovery: https://forum.xda-developers.com/t/...dmi-9-power-redmi-note-9-4g-redmi-9t.4263407/
And here, look for the fastboot instruction, follow that to flash OrangeFox to Redmi (DO NOT do the zip instruction, it wouldnt work on the stock MIUI recovery): https://wiki.orangefox.tech/en/guides/installing_orangefox
STAY ON THE RECOVERY ONCE YOU HAVE FLASHED IT!!!
Do not reboot to the system, if you accidentally do, just reflash the OrangeFox recovery as MIUI have already replaced it with the stock recovery.
Anyways after that, you should have a working recovery, now using a computer go to Magisk github release page, download the version 23 zip file: https://github.com/topjohnwu/Magisk/releases
While still on recovery, connect your Redmi 9T to the computer using cable, it will show up as MTP device. Just copy over the magisk file I mentioned to the Redmi. I forgot you can actually download this and copy before unlocking your bootloader so you won't have to later.
Locate the magisk file in OrangeFox and then flash it. VOILA you're done! Reboot to system.
==
BACKUP YOUR FILES AND APP DATA!!! In case something goes wrong. I do not guarantee this would work. Feel free to get help though...
To uninstall magisk, duplicate the magisk zip then rename it to uninstall.zip - flash in the recovery as usual.
I know a simple thing but, use a pin code or a password so you would be able to unlock the /data partition in OrangeFox. You would see the unlock screen right away after booting to the recovery, just enter your code or password and you're good to go.
Sorry that no one answered you, i don't know perhaps right now you could have already figured out how to, but nonetheless this would be a reference to those who are about to do the same thing as you wanted.
I forgot you said TWRP, im sorry.
Anyway the TWRP link: https://forum.xda-developers.com/t/recovery-3-5-a10-twrp-unnoficial-for-lime-redmi9t-beta.4233045/
The general steps are more or less the same. That post also contains instructions how to flash TWRP. Feel free to ask questions if you need help.
AJPuzonThank you, thank you and thank you very much for the explanation. I will follow your recommendations and when I finish I will report the results.
Also gonna put this here while I still remember:
It's very likely that the phone will fail SafetyNet once Magisk is installed. Hence no banking apps will work and you cant install apps that require Safetynet (they will be hidden) So here's what I did on mine to pass it again:
1. Go to Magisk settings (should be at the top right cog icon), turn on MagiskHide.
Now go back, tap the shield icon below (Superuser requests) MagiskHide is now visible, go to that. Tap Google Services and it will expand, check all the additional items under it.
- do this for all the other google apps that you have installed.
2. Go to Magisk settings again and the turn on Hide Magisk. Name it to whatever you want. Reopen Magisk using the new program name that you assigned it to. Reboot.
3. And then go ahead and clear the App Data of both Google Play Services and Google Play Store. Reboot
Additional steps for custom roms:
1. Go to modules (4th option below) and then install MagiskHide Props Config. Now reboot.
2. Go to Play Store and then install a terminal application. (Material Terminal is what I use in this case).
3. Open the terminal app, type props then press enter, after follow the instructions to find your device in the list, change your device fingerprint to that. Reboot once done.
4. Again clear the app data of Google Play Services and Google Play Store, and reboot.
Hi
I installed LineageOS 20 on OnePlus 9 with the instructions on official wiki. Then I root my phone with Magisk. I install Magisk by sideloading the Magisk ZIP file and then install the apk as it's been explained in this video. Now I can't update the OS with updater in system settings. I find this guide that explained I need to uninstall and restore images in magisk then update my phone and reinsatall magisk before reboot. But magisk didn't create a backup during installation.
I followed this instructions to fix magisk stock backup does not exist
I create a backup with this guide and lineageos boot.img file and I can now restore images in magisk but I get the same error when trying to install the updates. I noticed that there is also dtbo in backup function and I did the same thing for backing up dtbo.img and it doesn't solve the problem. Is there anything I'm missimg. Should I use vendor-boot.img instead of boot.img?
mtuxz said:
Hi
I installed LineageOS 20 on OnePlus 9 with the instructions on official wiki. Then I root my phone with Magisk. I install Magisk by sideloading the Magisk ZIP file and then install the apk as it's been explained in this video. Now I can't update the OS with updater in system settings. I find this guide that explained I need to uninstall and restore images in magisk then update my phone and reinsatall magisk before reboot. But magisk didn't create a backup during installation.
I followed this instructions to fix magisk stock backup does not exist
I create a backup with this guide and lineageos boot.img file and I can now restore images in magisk but I get the same error when trying to install the updates. I noticed that there is also dtbo in backup function and I did the same thing for backing up dtbo.img and it doesn't solve the problem. Is there anything I'm missimg. Should I use vendor-boot.img instead of boot.img?
Click to expand...
Click to collapse
I just learned that Magisk doesn't work after an OTA update. What I do is I normally update, uninstall Magisk, boot into Lineage Recovery, sideload the Magisk .zip file via ADB, reboot, and finish setting up Magisk through the app. There are other ways to do this, but this method works well and doesn't need anything special. Works for me!
Alteratively, look here.
mtuxz said:
Hi
I installed LineageOS 20 on OnePlus 9 with the instructions on official wiki. Then I root my phone with Magisk. I install Magisk by sideloading the Magisk ZIP file and then install the apk as it's been explained in this video. Now I can't update the OS with updater in system settings. I find this guide that explained I need to uninstall and restore images in magisk then update my phone and reinsatall magisk before reboot. But magisk didn't create a backup during installation.
I followed this instructions to fix magisk stock backup does not exist
I create a backup with this guide and lineageos boot.img file and I can now restore images in magisk but I get the same error when trying to install the updates. I noticed that there is also dtbo in backup function and I did the same thing for backing up dtbo.img and it doesn't solve the problem. Is there anything I'm missimg. Should I use vendor-boot.img instead of boot.img?
Click to expand...
Click to collapse
ethical_haquer said:
I just learned that Magisk doesn't work after an OTA update. What I do is I normally update, uninstall Magisk, boot into Lineage Recovery, sideload the Magisk .zip file via ADB, reboot, and finish setting up Magisk through the app. There are other ways to do this, but this method works well and doesn't need anything special. Works for me!
Alteratively, look here.
Click to expand...
Click to collapse
I was exactly looking for this for my SM-T290, which also runs LineageOS 20. I think it is the most easy to deinstall Magisk root from the Magisk Manager, apply the update and then reinstall it. I think this also works with TWRP???
Minionguyjpro said:
I was exactly looking for this for my SM-T290, which also runs LineageOS 20. I think it is the most easy to deinstall Magisk root from the Magisk Manager, apply the update and then reinstall it. I think this also works with TWRP???
Click to expand...
Click to collapse
I'm installing an update right now. I would imagine it works with TWRP as well, but I only recently started using it.
I realize that this may be a late reply, however, there is no need to do any of these convoluted processes.
Here is what I do, flash the Magisk as a .zip in Lineage recovery once and set everything up. Once the Magisk install is working you can apply OTA updates normally without Magisk and root being removed. On my OnePlus 7 Pro which is an A/B device I just install the OTA and hit reboot with Magisk seamlessly persisting and nothing else being required to preserve or reinstall it. The reason that this works is because the Magisk.zip installs an addons.d script which automatically runs after OTA updates and takes care of Magisk for you.
I installed many Lineage OS 20 OTAs and I never had to touch Magisk at all, it is always installed and working with no intervention whatsoever. Keep in mind that this will only work on A/B devices with Lineage recovery (which you should all be using anyway).
droidman1992 said:
I realize that this may be a late reply, however, there is no need to do any of these convoluted processes.
Here is what I do, flash the Magisk as a .zip in Lineage recovery once and set everything up. Once the Magisk install is working you can apply OTA updates normally without Magisk and root being removed. On my OnePlus 7 Pro which is an A/B device I just install the OTA and hit reboot with Magisk seamlessly persisting and nothing else being required to preserve or reinstall it. The reason that this works is because the Magisk.zip installs an addons.d script which automatically runs after OTA updates and takes care of Magisk for you.
I installed many Lineage OS 20 OTAs and I never had to touch Magisk at all, it is always installed and working with no intervention whatsoever. Keep in mind that this will only work on A/B devices with Lineage recovery (which you should all be using anyway).
Click to expand...
Click to collapse
Well, I came to the fact I have a problem with TWRP. It uses OpenRecoveryScript for OTA updates and should also run addon.d scripts after it (Magisk uses this to survive an OTA). The only problem is that the scripts should run after the OTA flash, but for me, it doesn't. So I need to manually reflash Magisk and Gapps after installing an update. My data is encrypted, but I edited the addon.d script to flash the ZIP from the external SD card.