Hello. I installed Pixel Experience (from XDA) on my Redmi Note 10 Pro from Xiaomi about 3 days ago, with Magisk for root. Nothing special and a great experience so far but...
...I just encountered a bugMy phone stopped charging so I had to reboot it to get it to charge. I was worried it was a damaged USB port. Then after 2 minutes of charging, it turned off by itself and rebooted by itself. I had to hard reset it and after 2 minutes it repeated the reboot without asking me !
It is now stucked on this loop : the "G" from Google (black loading screen), then after 2 minutes it says "Starting..." with my wallpaper and after one minute it goes back to the "G".
If I hard reset, I can go my menu, some apps are crashing and in about 1 minute it goes back to the loop.. I also can't charge in if the usb-c cable is not plugged in before the restart.
I can access the TWRP recovery, which is stable so far, but I haven't done a backup yet.
Where doest it come from ? What should I do?
Thanks in advance
Me too
Did you've tried to flash magisk 23 over again?
May use magisk canary debug 23
Laptapper said:
Did you've tried to flash magisk 23 over again?
May use magisk canary debug 23
Click to expand...
Click to collapse
I reflashed it and now it's working fine
Related
I am currently stuck for 45+ minutes at the google reboot splashscreen (4 colorful spinning dots that eventually should turn into the word android once reboot is complete).
I followed an update procedure that I have used many times (last done November 16), although some of the files involved are somewhat old.
Starting from November 16 update for Marshmallow:
1 - Fastboot-Flashed that March 2017 factory image for Marshmallow (yes, there is still a Marshmallow... I dont' want Nougat yet). Flashed all partitions except data and recovery.
2 - Reboot directly into TWRP (I believe it is TWRP 3.0.2... I haven'te changed it recently)
3 - In TWRP: Flash superuser BETA-SuperSU-v2.65-20151226141550 i
4 - In TWRP: Clear space from app/system by deleting foreign language directories (to make room for xposed)
5 - IN TWRP: Flash xposed xposed-v79-sdk23-arm
6 - In TWRP - initiate reboot to system.
7 - As system rebooted, I entered my PIN.
That's where I am now. Note I never saw a screen for "optimizing apps" that was expected. I
Note I never rebooted to android system, so I'm not sure which step caused the problem (it was a method I developed to update quicker although in retrospect rebooting each step to check would be smarter).
I have some ideas of what to do eventually: (retry my flash one step at a time)
BUT, I don't know how to do anything with a phone that is stuck on the splashscreen:
* It does not respond to key combination on/volume-down (which normally goes to fastboot)
* When plugged into pc, it does not respond to fastboot devices
* There is no battery pull option on this phone.
What to do next to get control of my phone... let the battery run out on the splash screen?
Hmmm. Weird. Just held power-on and vol-down and it took me briefly to a different screen (android?) and then promprted for PIN, then back to splashscreen.
I kept pressing that combo and eventually did get into fastboot.
Now I'll flash again.
electricpete1 said:
I kept pressing that combo and eventually did get into fastboot.
Now I'll flash again.
Click to expand...
Click to collapse
Hello. Not sure what caused your problem. Also, i don't use Xposed...
Just a heads up... Your SuperSU is really really old. Just use this one:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Good luck...
The version of SuperSU he used likely was the cause of the bootloop.
5.1 said:
Hello. Not sure what caused your problem. Also, i don't use Xposed...
Just a heads up... Your SuperSU is really really old. Just use this one:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Good luck...
Click to expand...
Click to collapse
I reflashed the system and then flashed newer files:
SR3-SuperSU-v2.79-SR3-20170114223742.zip
xposed-v87-sdk23-arm
(with a reboot between flashing SU and flashing xposed).
Everything booted up fine.
Problem solved.
Thanks for the help!
Aren't you supposed to fastboot boot, not flash the su with marshmallow?
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!
Today I left my phone in a cab and got it back in the evening. But after I got my phone it was stuck in a boot loop (after force restart - power button press and hold - it will go to battery icon and automatically restart after a few minutes and again goes to battery icon). Please see the video to understand the boot loop. Unfortunately, Developer options of the phone were not enabled.
Can boot to recovery but can boot to fastboot.
Can you please help me to boot my phone back to normal or sideload a ROM via adb.
tia
Was able to fix the issue. Followed below steps,
1. Kept phone until the battery fully drains
2. Plugged into the charger and charged the phone up to around 65% while the phone is switched off.
3. Switched on the phone when the cable is disconnected.
4. This time the phone was booted to recovery. No battery logo anymore
5. From recovery, rebooted the phone. But again it was booted to recovery.
6. Wiped all data and rebooted.
7. Phone was booted to MIUI os but had to set up the phone again from the beginning.
jayanath said:
Today I left my phone in a cab and got it back in the evening. But after I got my phone it was stuck in a boot loop (after force restart - power button press and hold - it will go to battery icon and automatically restart after a few minutes and again goes to battery icon). Please see the video to understand the boot loop. Unfortunately, Developer options of the phone were not enabled.
Can boot to recovery but can boot to fastboot.
Can you please help me to boot my phone back to normal or sideload a ROM via adb.
tia
Click to expand...
Click to collapse
Same problem bro, did u resolve it???
I think your battery is empty. Leave it on power for a while and check if its charging. Maybe the charginglevel is too low for booting up.
opg2000 said:
I think your battery is empty. Leave it on power for a while and check if its charging. Maybe the charginglevel is too low for booting up.
Click to expand...
Click to collapse
I hope it was that simple ..it seems probably like a bad update. My gfs phone did the similar today
The digitizer stopped working, I force reset the phone and boom ..recovery mode - Trying everything but it doesn't work. Wipe surely would work but she has pictures and videos so I'm trying to avoid that. Plug it to charging but she remembers it had like 75% of battery ...geez (hoping for a miracle)
EDIT: Probably this happen from the bad xiaomi update, anyway I did wipe the data and as expected it work without an issue, I'll unlock this phone and ditch MIUI (I mean I did it to my phone Xiaomi Mi Mix 2S from day 1 - I hate miui) ..now my gf has a reason to hate it too
A factory reset could be painful, since you would lose everything on the device. I saw a guy tap all over the back of the phone with two fingers, and boom! The Redmi Note 10 Pro boot normally! I tried it on a friend's phone, and it worked.
Hello,I had a kind of a similar thing.
I left my phone to charge and when I was back it seems to be stuck in a boot loop(MIUI14)
Well,I tried to force restart but the same.
Before I go to recovery mode,accidently,I putted the phone in fastboot mode.I restarted it in the try to go to recovery mode but the phone started normally.After boot,it's shows an update compete message,so te problem was from an android security path update whatever.
AlexfxDru said:
Hello,I had a kind of a similar thing.
I left my phone to charge and when I was back it seems to be stuck in a boot loop(MIUI14)
Well,I tried to force restart but the same.
Before I go to recovery mode,accidently,I putted the phone in fastboot mode.I restarted it in the try to go to recovery mode but the phone started normally.After boot,it's shows an update compete message,so te problem was from an android security path update whatever.
Click to expand...
Click to collapse
I have important apps on the phone and I wasnt thinking about a factory reset anyway but hopefully it worked in that way
Hey there folks,
Today morning I have looked into the Magisk app, I think it was in version 24.3, and it said it has an update.
I have pressed on the update, it opened the shell, and patched the relevant ROM, nothing unusual.
Then it rebooted.
Here comes the hassle.
The stock oneplus boot image came in (my phone has a boot animation and an 1+ and android splashscreen before) and I was like waiting.
After 30 secs I thought that it is taking an unusually long time, but maybe its the new module.
A few minutes later I considered that there is something wrong with it, and tried to hardware reboot it, maybe it would solve my problem.
Still nothing
Current situation : My guess is that it got bricked, it is not in bootloop, but probably my patch has failed as it does not boot in
nor adb nor fastboot (while the device is in fastboot mode) detects it from a Win10 powershell/cmd, from which I have had no problem connecting before
Any idea how can I fix it and recover the data from it at least?
I recently installed evolution x on redmi note 11 and noticed that fastcharge didn't work so I installed magisk and im currently using an fast charge module, but whenever I reboot the phone the screen turn on and turn off and then it goes to twrp. it trows the error rescue party.
I already tried to wipe cache, but I dont really want to format all data because teh internet here is not that good and installing all that again is so time consuming. I need a solution please.
EDIT
I wiped the cache dalvik via twrp​
I turned the phone off and let it rest 5 mins​
Turned the phone on and worked normaly​
The phone is working normaly in this moment but im afraid that it would happend again, I need a better soluion than letting the phone rest.
EDIT
I think that it was a version bug, beacuse had version 7.1, so I installed 7.2 and all works perfectly, even with root and fast charge module
Decrypt data in TWRP/OF and remove the broken magisk module directory:
/data/adb/modules/(FAST CHARGE MODULE NAME)/
After that, reboot the phone and you should be fine
hadrbass89 said:
Decrypt data in TWRP/OF and remove this directory:
/data/adb/modules/(FAST CHARGE MODULE NAME)/
After that, reboot the phone and you should be fine
Click to expand...
Click to collapse
the problem is that i really need fast charge, so i turned the phone off and let it rest like 5 mins then i worked normally, I think i could be a cache problem, but thanks for the help!