Problem mi A2, stuck at phone is starting - Xiaomi Mi A2 / 6X Questions & Answers

Hi,
I have a problem with mi A2, I think it's related with some app I install. I have magisk with some modules (no problem with that since phone boots ok after install each module). I restore all apps with Titanium backup and it's fine after severals reboots but after a time, I reboot the phone and it stucks at "phone is starting". I removed all apps from settings menu (i can go to settings) but no luck... so i have to wipe data in order to fix the problem.
Modules i have installed: magisk systemless hosts, audio modification library and gcam pixel 3 enabler (or somethink like that). Last app I installed before reboot it was a gcam but i don't think that app caused the problem.
Anyone has that problem in the past?
BR.

Related

Losing root after some time, Magisk v11 + MagiskSU

pretty much title.
sometimes i lose root twice a day, sometime 3day without lose, reboot/reflash magisk fix it
Same here
Enviado de meu LG-D295 usando Tapatalk
Just experienced the same issue. After installing some modules and rebooting
I am experiencing the same thing.. but when or how I don't know... I just take reboot and again root will be back. Might be some other app like clean master or auto killing apps kills magisk services???
I had the issue too, but it stopped when I disabled MagiskHide. That of course is only a solution if you don't actually need it.
Not being an expert, I never found a way to debug the issue or contribute otherwise.
I can confirme. Also when MagiskHide is on, I experience random reboots, which is bigger problem. Any fix for it?
Karls0 said:
I can confirme. Also when MagiskHide is on, I experience random reboots, which is bigger problem. Any fix for it?
Click to expand...
Click to collapse
Just a thought: have you added any system apps/processes to the Hide list?
No, i didn't. I don't use android pay, and i don't think that hiding root may be necessary for any other system app. When I turn MagishHide I have maybe 1 min before reboot. All was fine first few hours after installation, before first root losing.
If it will help, I'm on AOSP 6.0 custom ROM. My device is i9505. What's interesting it happens only if mobile data is on. Wi-fi doesn't do any troubles.
I will throw my experience into this thread as well. I am running Magisk 11.1 with DarkRom on my Nexus 5. Everything seems to work very smooth outside of randomly loosing root. I don't have to reflash, just reboot and it comes back. I do have MagiskHide enable for Android Pay. I also have the AppSystemizer model installed to covert Action Launcher 3 to systems. No random reboots, but loosing root is annoying. I may try to disable MagiskHide and see if that solves the root drop issue. Android Pay is handy though.
Ok Folks my 2 cents in regards to this trouble, i have did some work in reproducing this Magisk Root Loss.
say i have few apps like 1) SafetyNet Sample: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en & 2) RootChekerPro app and both these apps are hided them from root using MagiskHide.
So when i launch Magisk Manager app and checked safetynet Status and then opened app1 (safetynet Sample) ran the test and then immediately did Forcestop the Magisk manager app and launched back Magisk Manager app boom the root is lost and did a reboot everything is back fine again.
I've been trying to find the cause of this issue for a couple of weeks. This is what works for me so far
1. Open Magisk Manager when root is working (either immediately after rebooting or after disabling Magisk Hide).
2. Does Magisk BusyBox and Magisk Hide.
3. Reboot
4. Enable Magisk Hide, but keep Magisk BusyBox disabled.
5. Reboot
Check if root disappears anymore.
I think Magisk Hide is causing the issue, disabled the Magisk Hide and the root stays.
It may also be releated with GApps package - it could explain why some people have this issue with losing root/stability but others no. You can try with smaller package (picko/nano).
Magisk 11.5 seems to fix the issue for me
craigacgomez said:
Magisk 11.5 seems to fix the issue for me
Click to expand...
Click to collapse
No, it's just randomly occurring.
I was having the same problem with 11.1 and flashed the 11.5. It doesn't fixed.
Then flashed the ROM and 11.1 again the root is still there.
I don't know what exactly triggers the root to hide but there is something going on.
works on first flash of 11.1, then the next reboot breaks it again. uninstalling and reinstalling magisk fixes it again until the next reboot
I switch on MagiskHide only when I need it. So far it's quite good option, doesn't require any reboots.
did more testing, I don't lose root at all when I have MagiskHide disabled. Deleting /magisk/.core/magiskhide in recovery returns root.
Mostly a "me too" post. Issue still occurs on 11.6.
I tried replacing MagiskSU with SuperSU. But still the issue remains.

Raiffeisen Twint (https://play.google.com/store/apps/details?id=ch.raiffeisen.twint)

Hi everyone,
I am using the application Raiffeisen Twint (version 1.2.16.0, https://play.google.com/store/apps/details?id=ch.raiffeisen.twint) on my Magisk's rooted Google Pixel (Android 8.0, Nov. 2017) without problems for a while, but since Magisk 14 versions, the application stopped working and the application reports that root is detected.
I have successfully updated to Magisk 14.5 (from 14.2), but root is still detected by the application, even with Magisk Hide activated for the application and the Magisk Manager package moved to a random name (could also be related to the updated application).
I have cleared the data of the application several times and it doesn't help and root is still detected by the application...
Anyone has a idea?
Thanks for your answers!
Like I said in the Magisk support thread, I can hide Magisk from that app just fine (on Magisk v14.5 beta)...
You don't happen to have any other mods that might trigger an app looking for root (like Xposed)? Can your device pass SafetyNet? Have you previously been rooted with any other root method and do you have any remnants of that left (root management apps, etc)? Do you have any apps that are known to be used for questionable purposes. By "questionable purposes" I mean getting access to paid features without paying, etc. Not necessarily that you use the app for this, but that the app might be used in such a manner... Etc, etc, etc. Every little detail might count.
Hi Didgeridoohan,
Thanks for helping me!
I do not have any mods installed in Magisk and also no Xposed. My device is passing SafetyNet!
I have performed a factory reset last week and since that I only rooted my device with Magisk 14.2, so no other rooting applications used. For details, I have unlocked bootloader, TWRP recovery installed and developer options and USB debugging activated.
My settings in Magisk are:
I have following applications installed on my device:
https://pastebin.com/pmt4jBMV
Do you see any applications with "questionable purpose"?
I get this message in the application:
Thanks a lot!
At a quick glance everything looks ok...
I did some experimenting with the other Raiffeisen apps you have installed, in case they also detect root and "tell" on you. At least one of them did detect root, but from what I could see it didn't make any difference for Twint.
I also tested installing a few of the root apps you had installed (in case the app looks for certain known apps), but that didn't make any difference either. I could still successfully hide root.
My guess is that it's something along these lines tough. That it's using another app or detecting a root app. You could start experimenting with that. Clearing data for the other Raiffeisen apps and adding them to MagiskHide and also removing root apps. Try disabling USB debugging and developer options as well (didn't make difference for me, but worth a shot).
Simple. Change name of package from settings in Magisk Manager, then MAKE SURE you add twint app to magisk hide list, then ERASE DATA of twint app, change package name once again and run twint. Working with Magisk 14.5. Screens if u want available. Or video.
Hi Didgeridoohan, Hi Mamama07,
Thanks for your help, but sadly none of your suggestions did worked... until the update of the application released yesterday, to fix problem related to rooted devices! [emoji3]
Thanks anyway again for your help! [emoji106]
I had the same problem (with BCV Twint) and after a few tries, changing Magisk Package Name worked!

Problem after uninstll riru core & Edexposed

Yesterday I decide to uninstall riru-core and Edexposed to see if in this way my banking app will work, but after that the system reboot and it stay stuck on the boot sequence.
I manage to start in safe mode but I don't have any icon.
I thought it was a problem of magisk so I reflashed the boot image but after it the system restarted but again no home screen, many of the apps works if I call them through Hey Google, but not all.
So I did a complete reinstall of the system with HuRupdater but again no icon.
I think that unistalling riru-core changed something in the launcher of my Huawei phone, does somebody know what can have changed.
I have a P10 lite with magisk 20.4.
Reapplying Magisk and the two riru modules I have unistalled changes nothing.
Even if the phone is connected on the line and can receive message on WhatsApp when on wi-fi if I try to call the telephone doesn't ring and who is calling receive the free tone.

Greenify for magisk bootloop

I need small help. I got bootloop on my Xiaomi mi note 10 lite. Something like year ago I had rooted it (after couple days of trying a lot of metods) and I after that I started to use it. By time I have been using few Magisk modules and now I wanted to try some battery savers. I had install GPU Turbo boost and I reeboted my phone. After that I had install Greenify magisk module and reeboted again. Then my phone hangs on bootloop that always finish with Mi recovery 3.0. I can go into fastboot but I dont have TWRP installed. I had enter safe mode but I dont know can I go into settings/apps/magisk and clear data (or uninstall whole magisk) without causing more problems. Is there a way to remove the module somehow without removing magisk?
You need to enter twrp and select the module causing the card machine to be deleted in the twrp advanced options, file management and data / ADB / modules directory
https://lanzoui.com/b03c2iqbi Password: han
This is the self-help brick rescue module generator made by our domestic great God. After you choose to set it, click OK to automatically brush it into the mask manager! However, you cannot select a language! You can translate screenshots by yourself! The general description of the function is to find that the card machine module regrets trying the boot mode several times. If it still fails to boot after reaching the number set above, all modules will be automatically disabled to achieve the boot effect
ruffpl said:
I need small help. I got bootloop on my Xiaomi mi note 10 lite. Something like year ago I had rooted it (after couple days of trying a lot of metods) and I after that I started to use it. By time I have been using few Magisk modules and now I wanted to try some battery savers. I had install GPU Turbo boost and I reeboted my phone. After that I had install Greenify magisk module and reeboted again. Then my phone hangs on bootloop that always finish with Mi recovery 3.0. I can go into fastboot but I dont have TWRP installed. I had enter safe mode but I dont know can I go into settings/apps/magisk and clear data (or uninstall whole magisk) without causing more problems. Is there a way to remove the module somehow without removing magisk?
Click to expand...
Click to collapse
Module Issues:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Check from the section "Disabling/uninstalling modules manually". Maybe this will help
Thanks all for help I got it working. I read that all I need to do is just restart phone from safe mode and when phone will boot magisk will be disabled and it worked . I had open magisk app,removed module, flashed magisk boot image and its ok for now. Only problem that still exists is with some modules - when I want to install zip file I got extract error.
Safe mode has side effects. It's better to uninstall and install! After putting on the mask, brush in the automatic brick rescue module provided by me, and you can do it at will
If you don't understand, open the application, click the three vertical bar options on the right and directly click to confirm the default!

Magisk Zygisk + LSPosed Zygisk = black screen after boot

Hey,
I updated my Magisk v23 do Magisk v24.1 yesterday. I noticed that hiding root from apps doesn't work for me and LSPosed modules don't work either. I looked to see if LSPosed offers a module that works on Zygisk. As it turned out there is such a module, they have been working on such a version of LSPosed for months. Module I uploaded, it worked for some time. After a while I noticed that Google Pay does not want to use my card (it sees root). I installed the Universal Safetynet Fix module in Magisk. I restarted my OnePlus 7 Pro, then cleared the Google Services data, and poriously added the payment card. I was greatly surprised as I did another reboot to make sure all changes were applied. The phone booted, the boot process took a very long time compared to how it has always booted. At the end of the bootation I felt two vibrations and that was it. The boot process ended and there was a black screen. There was no Launcher, status bar or anything else visible. The only thing I noticed was 3 options in the white window after holding down the power button - a white window and 3 options: Lock, Restart and Power off.
I've tried for hours different tricks - uninstalling Magisk, getting rid of TWRP, flashing the official ROM in TWRP (without Magisk) and nothing worked. The effect is the same every time. To sum up, I regret that I updated Magisk to v24.1. I think that Zygisk mode and modules are still very underdeveloped. The whole situation caused me to lose all the data in the application. The only recovery is copying files via TWRP. I personally have no idea how to get out of this situation to keep a working system.
i no have install LSPosed Zygisk
just install Safetynet Fix module Zygisk,and use Zygisk Black list,and change Magisk app name( i have install stub-release.apk this apk)
my all bank app can't detected Magisk,and work fine
google pay too
rf9992003 said:
i no have install LSPosed Zygisk
just install Safetynet Fix module Zygisk,and use Zygisk Black list,and change Magisk app name( i have install stub-release.apk this apk)
my all bank app can't detected Magisk,and work fine
google pay too
Click to expand...
Click to collapse
Exactly this, bank apps can't detect the new zygisk, at least for now, just hide magisk app, delete TWRP folder and use SNF zygisk module and the black list
hi
MisiekDP said:
Hey,
I updated my Magisk v23 do Magisk v24.1 yesterday. I noticed that hiding root from apps doesn't work for me and LSPosed modules don't work either. I looked to see if LSPosed offers a module that works on Zygisk. As it turned out there is such a module, they have been working on such a version of LSPosed for months. Module I uploaded, it worked for some time. After a while I noticed that Google Pay does not want to use my card (it sees root). I installed the Universal Safetynet Fix module in Magisk. I restarted my OnePlus 7 Pro, then cleared the Google Services data, and poriously added the payment card. I was greatly surprised as I did another reboot to make sure all changes were applied. The phone booted, the boot process took a very long time compared to how it has always booted. At the end of the bootation I felt two vibrations and that was it. The boot process ended and there was a black screen. There was no Launcher, status bar or anything else visible. The only thing I noticed was 3 options in the white window after holding down the power button - a white window and 3 options: Lock, Restart and Power off.
I've tried for hours different tricks - uninstalling Magisk, getting rid of TWRP, flashing the official ROM in TWRP (without Magisk) and nothing worked. The effect is the same every time. To sum up, I regret that I updated Magisk to v24.1. I think that Zygisk mode and modules are still very underdeveloped. The whole situation caused me to lose all the data in the application. The only recovery is copying files via TWRP. I personally have no idea how to get out of this situation to keep a working system.
Click to expand...
Click to collapse
Hello, were you able to solve this?
maycomathias93 said:
hi
Hello, were you able to solve this?
Click to expand...
Click to collapse
No. You have this same problem (phone not turning on)?
yes, the only solution in this case is to run uninstall magisk and install again without lsposed. For now use edxposed without safetynet (sorry for my google translate english)
Man, I solved this problem, going from Android 9 (custom ROM where I had the problem) to 10 (also custom ROM). I hope it helps you, greetings.

Categories

Resources