Bootloop issue - Treble-Enabled Device Questions and Answers

Hi
How is everybody?
I am encountering an issue with my MotoG9 (Guamp) device. I am running Pixel Experience 12.1 (https://github.com/ponces/treble_build_pe/releases/tag/v412-plus) with Magisk Version 26.1. It was running smoothly until today, when it went into a bootloop. No new modules or apps had been installed, the bootloop started after a died battery while I was watching YouTube.
How can I solve this issue please?
The TWRP recovery is encrypted and asking for a password (PIN) which I have tried the PIN i use to unlock the phone without any benefit.

Have you tried booting into safe mode? By holding down the volume down during boot (not before boot) you can boot into safe mode, which will automatically disable all magisk modules on the next reboot. On the lock screen it will say "safe mode" in the bottom left.

Related

"com.android.systemui has stopped" bootloop -- Help fixing?

I have a LG G3 with rooted stock rom running xposed.
So I pulled my phone out of my pocket today only to see the Verizon boot logo in effect. I was thinking "that's weird, guess my phone needed to reboot? Strange." But the only problem is it never stopped. It will only boot up to the lock screen and occasionally it will display an error message telling me the systemui has stopped. Then about 10 seconds later, it reboots itself. It continues this process until I pull the battery.
I've tried booting into safe mode, no luck. It doesn't even actually boot into safe mode (it doesn't say safe mode in the bottom left corner.)
I tried wiping the cache, no luck.
I don't want to just do a factory reset because that hasn't seemed to help anyone else with this issue as far as I've seen. I have not found any helpful information on how to fix this problem.
My question is, what do I do? I feel lost on this subject. Normally I've always been able to diagnose problems on my own, but not in this situation.
I have all my apps and data backed up to Titanium Backup on my SD card.
Any suggestions?
Xposed is more than likely the cause. Boot into TWRP and open a terminal, then type the commands as shown in the OP of this thread to bypass it...
How to Disable Xposed on Lollipop when stuck in Bootloop
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816

Flashed Magisk systemless xposed and is now stuck in bootloop

Im on h815 android 6.0.
As the title says i tried to install magisk xposed and when the phone rebooted it got stuck in a bootloop.
I have tried to go to TWRP with adb but the phone doesn't respond nor does it want to boot into twrp.img with fastboot.
It doesnt respond when i try to boot into TWRP with hardware buttons either. What makes this even more difficult is that as soon as the phone gets power it tries to boot and doesn't want to stay off.
When i looked at it with LGUP (didn't do anything because that would probably be my last resort) It did show up as in standby on COM4.
Im quite sure i have have a system backup on the phone it's just that i can't get into TWRP.
Any help appreciated!

[GUIDE][ROOT][Magisk v20/v19.3] Samsung Galaxy A50 ( Update 12.11.2019 )

Magisk v20 worked stable on Galaxy A50 but If you want to use Magisk v19.3 you can patch and downgrade it using Magisk Manager - Custom Channel Update https://www.youtube.com/watch?v=vcF0pfdQyW8
-----------------------------------------------------------
Complete Guide for Rooting Samsung Galaxy A50 using Magisk v20 / v19.3 ( tested on SM-A505F ):
* Download the firmware Galaxy A50 (SM-A505F).
* Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5. Copy AP tar file and MagiskManager apk to your phone.
* Install Magisk Manager on your phone.
* In Magisk Manager: Install → Install → Select and Patch a File
* Select the AP tar file. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar. Copy magisk_patched.tar the tar file to your PC
* Enter Download Mode : Turn Power Off. Press and hold Volume Up key + Power Key,* When Samsung Logo appears release Power Key only, keep pressing Volume Up key until Android Recovery Mode Appears.
* Select Wipe data / Factory reset, Select Reboot to bootloader.* Connect your Samsung Galaxy to PC using USB Cable.
*Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do. Checked "Auto Reboot" and "F. Reset Time" only in options.
* Magisk is now successfully flashed to your device and Rebooting!
* After the device is booted up, do the usual initial setup. It need more time and patient.
* Connect the phone to Internet copy Magisk Manager apk to your phone and Install it
* Open Magisk Manager. It will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
* Done! You can use Root Checker to check it, Enjoy!
New video Install and Root with Magisk v20 / v19.3 https://youtu.be/ILvgki0pFHE
To prevent loosing magisk root after reboot. Reboot the phone from Magisk or Fully Power Off, you can watch this video https://youtu.be/Ea8s16usBOM
Rooting with TWRP+Magisk ( ASH2 baseband version only ), you can watch this video https://youtu.be/kYwJAKBzX1E
well donw
thanks i rooted latest stock F2 firmware
it works
FYI: To prevent loosing magisk root after reboot. Reboot the phone from Magisk or Fully Power Off, you can watch this video https://youtu.be/Ea8s16usBOM
Oh I wish I could get magisk on my phone. Unfortunatly I can't find the firmware, for my phone, anywhere on the internet (A505W). Will do directly once I can!
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Edit: It kept rebooting in any way. Used the factory reset at the end. Booted it up once without root. Set up Wifi and google account. Tried to reboot in root mode and voila: stuck in bootscreen with red letterd 'custom binnary not allowed'. Can't startup, can't go to recovery, can't flash the magisk patched zip (same red letters). Flashed stock rom and wait for the possibility to flash magisk patched again.
Edit 2: Booting in the stock rom probably registers something to let u flash something else again. Magisk patched flashed again. Booted normally, magisk up to date and working. Just gonna install fake gps, smali and magisk hide app again. Not in the mood to test reboot then again. It probably fails again. But i can spoof again for now.
Edit 3: After trying some more things, I think the conclusion is: U can only use Root mode once with this, until it reboots.
I wonder if I'm the only one with this.
jarno389 said:
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Click to expand...
Click to collapse
Have you attempted to change your IMEI recently?
Ertogrul said:
Have you attempted to change your IMEI recently?
Click to expand...
Click to collapse
Nope, the only thing i want root for is spoofing with gps joystick.
jarno389 said:
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Click to expand...
Click to collapse
I have tried everything but failed, I have tested on some device but it's only happen to A50
will this work with a505gn?
redymedan said:
I have tried everything but failed, I have tested on some device but it's only happen to A50
Click to expand...
Click to collapse
That's seem pretty unstable as it is right now. Was tempting to try this on my A505W, but I'm reluctant now.
Now I'm just wondering why the heck my root is still active with 2 random reboots. Last 20 runs the random reboots made it lose root and got stuck with constant rebooting.
When i started the recovery of samsung backup, it rebooted again (3rd time) (again root is somehow still active). Screw it, gonna forget about the backup and keep it like this. I think the random rebooting seems to happen often when installing much apps.
jarno389 said:
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Edit: It kept rebooting in any way. Used the factory reset at the end. Booted it up once without root. Set up Wifi and google account. Tried to reboot in root mode and voila: stuck in bootscreen with red letterd 'custom binnary not allowed'. Can't startup, can't go to recovery, can't flash the magisk patched zip (same red letters). Flashed stock rom and wait for the possibility to flash magisk patched again.
Edit 2: Booting in the stock rom probably registers something to let u flash something else again. Magisk patched flashed again. Booted normally, magisk up to date and working. Just gonna install fake gps, smali and magisk hide app again. Not in the mood to test reboot then again. It probably fails again. But i can spoof again for now.
Edit 3: After trying some more things, I think the conclusion is: U can only use Root mode once with this, until it reboots.
I wonder if I'm the only one with this.
Click to expand...
Click to collapse
Read my First post, I have updated it for fixing lost magisk root after reboot
I cannot pass through the flashing of image modified by Magisk. During the flash some red text appears on top saying that custom binary (VBMETA) blocked ... then there is a front camera, so I can not read it all and then "Lock" word. The flashing stops and odin waits forever. The only thing I can do is to interrupt and then reflash the whole firmware with odin since it ends up at the "error has occured while updating the device software".
My device is SM-A505FN, firmware XEZ-A505FNXXU1ASE3, OEM unlocked, tried Magisk Manager 7.3.2.
(w) said:
I cannot pass through the flashing of image modified by Magisk. During the flash some red text appears on top saying that custom binary (VBMETA) blocked ... then there is a front camera, so I can not read it all and then "Lock" word. The flashing stops and odin waits forever. The only thing I can do is to interrupt and then reflash the whole firmware with odin since it ends up at the "error has occured while updating the device software".
My device is SM-A505FN, firmware XEZ-A505FNXXU1ASE3, OEM unlocked, tried Magisk Manager 7.3.2.
Click to expand...
Click to collapse
Flash whole stock rom. Boot and login. Connect to wifi. Wait few minutes. Flash magisk rom again.
(w) said:
I cannot pass through the flashing of image modified by Magisk. During the flash some red text appears on top saying that custom binary (VBMETA) blocked ... then there is a front camera, so I can not read it all and then "Lock" word. The flashing stops and odin waits forever. The only thing I can do is to interrupt and then reflash the whole firmware with odin since it ends up at the "error has occured while updating the device software".
My device is SM-A505FN, firmware XEZ-A505FNXXU1ASE3, OEM unlocked, tried Magisk Manager 7.3.2.
Click to expand...
Click to collapse
You need to unlock the bootloader from Download Mode, Watch this video https://youtu.be/o1xZ-E3jhUg
redymedan said:
You need to unlock the bootloader from Download Mode, Watch this video https://youtu.be/o1xZ-E3jhUg
Click to expand...
Click to collapse
Oh, thanks, I was not able to find this trick, there are lot of infos everywhere and it's hard to find out. Thanks. So both volumes holding and plugin cable.
Thanks again
redymedan said:
Solved: Lost Magisk Root After Reboot
To prevent loosing magisk root after reboot. Reboot the phone from Magisk or Fully Power Off, you can watch this video https://youtu.be/Ea8s16usBOM
Click to expand...
Click to collapse
So what would happen if, by a mistake of mine, my battery dies. Do I have to reflash magisk again and factory wipe everytime? Or is the problem occur only with the "reboot" function of android since it work while fully powering it off.
AliasGprime said:
So what would happen if, by a mistake of mine, my battery dies. Do I have to reflash magisk again and factory wipe everytime? Or is the problem occur only with the "reboot" function of android since it work while fully powering it off.
Click to expand...
Click to collapse
Mine is still rooted since friday. It sometimes reboots randomly. Then i have to reset with volume down and power button or else is keeps restarting. Root is still active then. Battery also died yesterday. Could start up with power key only and root is still active. I still don't understand why but im good.
(I used the root mode function with volume up and power key till logo popsup only once after the flashing of magisk patcher to let it install magisk manager. )
I'm still wondering if I'm the only one with random reboots or constant reboots
Worked great for my SM-A505G.
In summary, after installing Magisk:
(Powering up normally) → (System with NO Magisk)
(Volume UP + Power) → (Splash screen) → (Release all buttons) → (System with Magisk)
(Volume UP + Power) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
Hi there,
Yesterday I rooted my A505W (Canadian Variant) and got random reboots like almost every one else. It got so bad, I decided to go back to un rooted stock. Before flashing stock firmware I took a look in build.prop file, hoping I might find something that does not belong there after rooting. And I think I found it. At the very end there is line like this:
ro.expect.recovery_id=0xf1dee4214a6ffec6b8
2cec9a13222d4f34c7fd10000000000000000
000000000
Comment it out to lool like this:
#ro.expect.recovery_id=0xf1dee4214a6ffec6b8
#2cec9a13222d4f34c7fd10000000000000000
#000000000
Wanted to delete it, but it was enough to comment it out whit #
Since last night I don’t have any reboots, it looks like commenting it out did the trick. So try it for yourself an see if it helps.
One more thing, if you need to reboot your device do not do it from Magisk, because it will keep rebooting, just power down and boot with the key combination. As I said since last night I have no random reboots.

Flashed Multifunctions, Now Im stuck on google logo with loading bar under

Hello!
I'm on a Pixel 2XL (Obviously) and I just flashed the multifunction module.
(There were no errors so I assumed I would boot in just found)
Now as I booted up after I rebooted, I'm stuck on the google logo with a loading bar under, This is fine most of the time because I know it's doing something root related like starting up services and/or flashing a module.
Now I'm stuck here while I'm typing this comment, I don't have my computer as its broken, I don't have TWRP either, or any recovery service,
Is this normal? Or should I Be Worried?
Still no reply...
Nicster205 said:
Still no reply...
Click to expand...
Click to collapse
Try booting in Safe Mode (it will disable all your Magisk Modules), then boot up normally and uninstall that module that seems to be causing your problems.

Installing magisk creates bootloop

Hi,
I have an unlocked 6,1, that currently has lineage 18 ( official ) flashed.
I am trying to install magisk with no luck.
If I adb into bootloader, i can then ''fastboot flash boot twrp.img''
If i then reboot , I get twrp.
If I then flash Magisk zip ( latest ), and reboot, it doesn't boot back into lineage.
Sometimes I get a bootloop ( lineage animation ), and sometimes it just sticks on android one.
I have to keep pressing volume and power buttons until eventually, I get back to download mode.
From there, I can either try to factory reset, or worst still, reflash lineage.
Any ideas what I am doing wrong?
As an aside, in case it is relevant ,one thing I have noticed is, after powering off, when I plug power in, I dont get a battery charging sign - never have with lineage - instead I get a blank screen. I also can't get to stock recovery from the battery charging screen using VOL up/POWER.
Srangely, if I flash stock using OST ( offline), I get the battery charging screen ?
Many thanks in advance
Pootler

Categories

Resources