sudden bootloop after restart. i disabled all of magsik modules but MM and still can't get in. i haven't flashed any other zips. the mobile was 15% i'm not sure if that related. i'm on a trip and i don't know what could possible by the reason. any suggestions ?
Related
Hi,
I have been using xposed on my Galaxy S5(klte) with AICP (MM) for some time now and xposed has worked flawlessly with it. Today I tried to look something up on my phone but when I pressed the home and/or the power button the screen didn't come on. I didn't think much of it and restarted. The phone booted up but only to the screen where it says "Starting apps..." and then just didn't respond anymore. So I decided to wipe cache and system and install AICP and the newest open gapps again. That worked fine and I was able to use my phone. I then flashed xposed arm23 v87 again. After it prepared all the apps the phone stopped at "Starting apps..." again.
Can anybody tell me what I am doing wrong or what I should try next?
/edit:
After I disabled xposed (touch /data/data/de.robv.android.xposed.installer/conf/disabled) the phone boots without a problem but I would like to somehow use xposed anyway, of course
Does anybody know how I could debug this? Is there a startup-logfile for xposed? I know it worked with that exact version of that rom for three month until yesterday morning and I didn't change anything.
Ok, it was amplify. Sorry for that.
So recently i bought note 5 N920T T-mobile variant and after few days i encounter a weird problem that i can't figure out what exactly is going on.
Once a sudden my phone freeze and touch screen stop responding then phone goes black screen and a strong white led light turn on while screen is black.
Then after pressing 3button together volume down+home+power the phone reboot normally
Then after few seconds again and again same thing happens.
I was on stock rooted 6.0.1 marshmallow rom with arter kernel permissive since i bought this device.
Things i tried
Factory reset from twrp (didn't change a thing)
I flashed stock rom marshmallow and nougat both via odin (got worse now more freezing and rebooting can't even complete setup )
Again tried flashing 4 files recovery firmware BL+AP+CP+CSC via odin this time with PIT FILE re-partition checked in odin. everything Pass smoothly without errors in odin but again freezing black screen on setup. (same issue)
Tried factory reset+wipe cache after flashing (still same)
At last i tried flashing custom rom "kongloi s8 port final repacked" from twrp after clean wipe it worked finally now no reboots or blackscreen freezing nothing everything works perfect for 2 days.
Then i thought now my phone is fixed so why not try stock again.then again same problem came back.
1 thing i realize that when i run custom kernel specifically a permissive kernel my phone runs without issues.
currently stuck with khongloi rom s8 port this is the only rom working on.my device and cant go back to marshmallow.
I am looking on Google and xda constantly from many days but can't find correct answer.
So please please someone point me out what is this issue
Sorry for the long post TIA
Sooooooo..... I have a problem. I am using AOSPK, and everything went very well, I was very happy with my new custom ROM. The Equalizer App kept crashing, so I installed Viper4android. That didn't really work, so I tried to fix it by installing APKs, Magisk Modules, which all resulted in the driver not being enabled. But then I stumbled across this thread here on XDA and there was a Module for Magisk I could flash which supposedly fixed the Error, but of course, that didn't work. As usual, I removed it with Magisk and rebooted it.
Now. The thing is, I am pretty much stuck on an endless Bootloop. I already had a Bootloop once, but those always led me back to TWRP. To get out of the AOSPK Kraken loading GIF, I had to let it like that overnight and let it drain its battery. Now, this morning I plugged the Phone in and tried again, but it didn't work. I let the battery drain itself again, but It only took like 10 minutes as it was plugged in for a short time. I only now found out I can press on Power + VolDown to force reboot.
I would REALLY love some help here, how do I get out of this mess? Do I plug into a PC and try to boot to TWRP? What do I do next? Please explain to me step by step, I am really in a sticky situation right now.
UPDATE: I can get into TWRP, not what? I wiped chache and dalvik, did nothing. What now?
Hi. I am also using Kraken rom. Check out this post if you want.
[GUIDE] Go back to stock - Galaxy S10 series
Hi 🙂 So you have bricked your Samsung S10 series handset and you need it fixed. Sometimes we try to modify our phones and it goes wrong, fret not it can be restored. DOWNLOADS Frija Microsoft Visual C++ 2008 Microsoft Visual C++ 2010 Phone...
forum.xda-developers.com
puul said:
Sooooooo..... I have a problem. I am using AOSPK, and everything went very well, I was very happy with my new custom ROM. The Equalizer App kept crashing, so I installed Viper4android. That didn't really work, so I tried to fix it by installing APKs, Magisk Modules, which all resulted in the driver not being enabled. But then I stumbled across this thread here on XDA and there was a Module for Magisk I could flash which supposedly fixed the Error, but of course, that didn't work. As usual, I removed it with Magisk and rebooted it.
Now. The thing is, I am pretty much stuck on an endless Bootloop. I already had a Bootloop once, but those always led me back to TWRP. To get out of the AOSPK Kraken loading GIF, I had to let it like that overnight and let it drain its battery. Now, this morning I plugged the Phone in and tried again, but it didn't work. I let the battery drain itself again, but It only took like 10 minutes as it was plugged in for a short time. I only now found out I can press on Power + VolDown to force reboot.
I would REALLY love some help here, how do I get out of this mess? Do I plug into a PC and try to boot to TWRP? What do I do next? Please explain to me step by step, I am really in a sticky situation right now.
UPDATE: I can get into TWRP, not what? I wiped chache and dalvik, did nothing. What now?
Click to expand...
Click to collapse
Hi, don't know if it's too late but I did have the same problem before and all I did was boot into TWRP. When you wipe make sure to check everything from Dalvil to Internal Storage and format data as well. Also if you are going to install Magisk try to do it after your phone boot into os otherwise it will stuck in bootloop again. I hope that's can help!
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Matsilagi said:
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Click to expand...
Click to collapse
Vbmeta means Android Verified Boot.
Vbmeta is default for all android devices and it was made by Google.
It is not specific made by Xiaomi.
Android Verified Boot 2.0
https://source.android.com/security/verifiedboot/avb
What changes did you do when you fixed the app issue?
Couldn't do any, just tried to boot into recovery, then got into that bootlooop cycle, couldn't reach anything.
Managed to get into EDL and SP Flash Tool mode, however, im a bit confused on what i need to flash to get it back to life with stock MIUI or atleast boot to main system to use ADB.
My IMEI is fixed on the phone stickers so i can reasily recover that aswell, any help is appreciated.
EDIT: Now i just need help flashing as it seems, what do i need to do to properly re-flash / re-boot the phone without losing IMEI and that sorta stuff? I plan on switching back to Pixel Plus UI again so, it isn't an issue.
EDIT2: Completely fixed, followed VD's guide on EDL/Mediatek Bypass method and flashed a normal GLOBAL rom, all was fixed, no IMEI lost.
so i've been experience miui randomly reboot ̶4̶ ̶̶t̶i̶m̶e̶s̶ 5 times on today. i always use my phone for daily like social media, music, reading etc, but i've do little modified system
19.12.2021 rooted phone V12.5.1.0.RKSIDXM using magisk 22.1
11.01.2022 install LSposed + Core Patch
what i experience is my phone randomly reboot, it show POCO logo and Unlocked logo. then phone turn off and reboot again, before it show poco logo there a vibration came from phone. i also tried to force into fastboot mode but it keep turn off in fastboot mode.
so how i can boot to homescreen ? ̶a̶f̶t̶e̶r̶ ̶p̶o̶c̶o̶ ̶l̶o̶g̶o̶,̶ ̶w̶h̶e̶n̶ ̶p̶h̶o̶n̶e̶ ̶t̶u̶r̶n̶ ̶o̶f̶f̶ ̶i̶ ̶h̶o̶l̶d̶ ̶p̶o̶w̶e̶r̶ ̶b̶u̶t̶t̶o̶n̶ ̶t̶i̶l̶l̶ ̶i̶t̶'̶s̶ ̶s̶h̶o̶w̶ ̶m̶i̶u̶i̶ ̶t̶e̶x̶t̶ ̶a̶n̶i̶m̶a̶t̶i̶o̶n̶,̶ ̶a̶n̶d̶ ̶e̶v̶e̶r̶y̶t̶h̶i̶n̶g̶ ̶i̶s̶ ̶f̶i̶n̶e̶.̶ it's not work, just hope it can boot to home screen
i wonder if everyone who used this phone have this kind experience, i might going to service center if this happend again
U can try Disable magisk modules via adb
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com
wetito said:
U can try Disable magisk modules via adb
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com
Click to expand...
Click to collapse
okay so everything was fine till i write this reply, there no random reboot anymore. in case if random reboot happend again, i will try your advice. anyway thanks
This was happening to me any time the Xbox app tried to send a notification. Phone would just reboot.
Still happens even with latest version. Have disabled notifications for that app and it's fine now. Those notifications weren't important anyway.
Strange one but could be similar for you if you are getting a vibrate before reboot like a notification trying to come through?
AnUrbanPenguin said:
This was happening to me any time the Xbox app tried to send a notification. Phone would just reboot.
Still happens even with latest version. Have disabled notifications for that app and it's fine now. Those notifications weren't important anyway.
Strange one but could be similar for you if you are getting a vibrate before reboot like a notification trying to come through?
Click to expand...
Click to collapse
vibrate sign on my phone simillar in condition where phone in off and turn on the phone will have vibrate sign before show poco boot up. when it happend i dont see any strange my notification beside download, social media, and games notification