My Redmi 5 Stucks in boot animation (in comic sans xD)
First of all, sry for my bad english. I'm from Spain and my english can be much better.
Hello Devs!!
I have a problem in my Redmi 5, i have unlocked the bootloader and rooted it (with Magisk), then i install EdXposed and a lot of
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That is a list with all my apps wich uses root or Xposed
AdAway
Greenify
LP
JasiPatcher
GameGuardian
Kali NetHunter
Youtube Vanced
CustoMIUIzer
Gravity box
Link2SD
NetCut
RootEssentials
Root Checker (one of the million that there are in playStore)
Root Uninstaler
TitaniumBackup
XDA Labs
The problem is, sometimes, not very often, when i restart my phone stucks in the boot animation (custom) and don't do anything, sometimes the Boot animation finish but Android don't boot. maybe u are thinking: "LEAVE MORE TIME TO BOOT"
30 MinutesI leave it too boot 30 mins and then, i try to restart and.... SURPRISE
BOOTS NORMALY
If someone can help me or have same problem, U know what to do :laugh::good:.
I get this too. It may be a ROM-related issue. I've only started experiencing it after the October update for the Pixel Experience ROM.
Horfax said:
I get this too. It may be a ROM-related issue. I've only started experiencing it after the October update for the Pixel Experience ROM.
Click to expand...
Click to collapse
same with me, but not during bootanimation. the phone is stuck on lockscreen. the screen will turn off and won't respond. the screen will turn on after a few minutes but it still won't respond. i'm on latest pixel experience official. i haven't installed any modification, didn't even root the phone.
I exactly had this problem in miui 10 with edxposed. Fortunately it hasn't happened yet in miui 11. But everytime i restart my phone, i scare to face that ...
Related
Hello,
I've got a weird problem with my M4
I've got the phone for over 2 years, it's the E2303 version. It worked perfectly normal until at some point it started randomly crashing (Note: the phone wasn't rooted at this point and it had Android 5.0 26.1.A.3.111 (carrier version)). The crash looks like this: the phone freezes for like 2-3 seconds not responding to any input, then the screen goes black, then it boots up normally. However it isn't rare for it to crash like that, then while booting up crash again in the same way, repeat a couple of times. In System incidents it's counted as just 1 incident. I also noticed that sometimes after successfully booting up after crash wi-fi, mobile transfer or airplane mode are switched on/off, not as before the crash.
I thought the problem would go away so I waited a bit, but it kept on crashing. Sometimes it can go for a few days without crashing, sometimes it crashes a few minutes after last crash.
I've tried fixing the phone using PC Companion (it also updated it to 6.0) - didn't help. I've tried flashing a stock 5.0 ROM using Flashtool (same as before: 26.1.A.3.111, but a non-carrier version) - also didn't help. Also I've got the phone rooted by now. I don't know about bootloader, the service menu tells me Bootloader unlock allowed: No, even though I've got the OEM unlocking switched on in the Developer options (I'm not that tech savvy in case of phones and I'm getting lost a little bit).
I've got some screenshots here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I hope there is a way to fix this phone, this crashing is starting to get a little annoying...
Any help would be really appreciated
Install twrp. Download latest stock rom. Format phone by wiping cache, system and data in twrp wipe option. Install flashtool and use it to install latest stock rom. Watch a tutorial on youtube How to install latest stock rom through twrp
Let me start by saying I am not rooted no twrp just plain stock , with locked bootloader. Also EU version.(V12.0.8.0.QJGEUXM)
A few months ago I downloaded the Android 11 Rom V12.0.6.0.RJGEUXM through the phone even though I am not on any trial program.
It installed easily on my phone , some people have had to use other methods...so I read.
Anyhow , I thought it was way too buggy and needed to downgrade.( Even after the the 2 other upgrades to V12.0.7.0.RJGEUXM. This is what I did to rollback if someone else is in the same boat.
I had to wait 3 days to unlock my bootloader,
Then I used the MiTool to select the ROM I wanted.
The problem then is the bootloader is still unlocked after you flash the new ROM, you need to use ADB command " OEM lock" to relock then phone , it should erase everything then go back stock. I am still learning with this Xiaomi device so I had to learn this from different sources and hope it helps somebody else out.
Soz if this is common knowledge or wrong part of forum!
thanks for the info but why did you downgrade did android 11 lags the phone or what
aymen peter said:
thanks for the info but why did you downgrade did android 11 lags the phone or what
Click to expand...
Click to collapse
1) WiFi issues and random reboots, when the phone booted (on its own accord) on reboot the wi fi took quite a few minutes ( over 5 minutes sometimes longer) to get back online.
2) The speaker volume seemed too quiet for video and calls.(on at full volume most of the time).
3) Not so polished, sometimes would be a bit laggy other times not.
At the minute Android 11 for the Poco is still Beta, I am sure these problems will get resolved. The moral of story ... Wait for OTA instead of forcing updates.
i used xiaomi flash tool to flash fastboot rom and selected this to keep unlocked bootloader
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well, it's a bit of a long story, so I'll try to be as short as possible.
Last year, and after hours of searching on the internet, I found the solution for "Custom binary blocked by frp lock" on this forum (here and here). Both methods promised to fix the lock without erasing my data, but I decided to try the second one (it consists of reinstalling only the boot image with Odin).
Fortunately it worked for me on the first try, and since this method was not well known on the internet, I decided to make a video tutorial to help those who had the same problem and wanted to keep their data.
The fact is that, unfortunately, this method didn't work for everyone, and in many cases it generated bootloops or black screens of death.
And my question is: does anyone know what could be the cause of this?
I tested it on SM-J710MN and SM-G532M, both running Android Marshmallow, and the bootloops/black screens occurred on devices running Android 6, 7, 8 and (I guess) 9 and 10.
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
jwoegerbauer said:
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
Click to expand...
Click to collapse
Thanks for answering.
Maybe I did not express myself in the correct way, but actually I was referring to the block that does not even allow to boot the device and only shows words in red, as seen in this image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But beyond that my question is about why does the bootloop or black screen happen after flashing the boot.img file? Does it have to do with a different/incompatible version of Android/binary/csc or something like that?
Hi, first time playing vith custom ROMs
I've SIM unlocked and unlocked bootloader of my old XPERIA XZ1.
I followed this tutorial https://www.getdroidtips.com/lineage-os-18-1-sony-xperia-xz1-compact/ in order to install Lineage OS 18.1 using TWRP
So I've downloaded all the software, images, drivers and such... then used adb and fastboot to flash TWRP.
When I finally managed to boot with TWRP my screen looked like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The display appears to be somewhat broken or misconfigured, with a smaller version of the display on the top left corner of the screen and everything else is RGB snow.
Touchscreen is responding on the non broken part of the screen only. It looks like this as soon as the screen turns on, even before Xperia booting sequence.
I couldn't manage to install Lineage properly either. I got stuck in a weird boot loop. Taking up to minutes to boot with the lineage loading animation and a black screen. I was able to interact with the parameter tab but could open any app or do anything else.
Then I decided to restart from scratch and reinstalled a stock ROM with Sony Xperia Flash Tool, following this tutorial https://www.getdroidtips.com/sony-xperia-xz1-stock-firmware/
Now I have a working Android system running on the phone but it didn't fix the screen.
It doesn't detect my SIM card either.
This isn't my main phone so it doesn't really matter to me if SIM doesn't work, but i'd like to fix the screen.
It might have something to do with the fact that I've tried to flash a Lineage ROM made for Sony Xperia XZ1 Compact. Mine is not a compact, but there was no official ROM for my specific model. This was the closest match and I thought this should be OK. I was SO wrong, lol
I couldn't find another thread with the same screen glitch, but I highly doubt it to be unique. I'm probably just using the wrong keywords.
Any hint would be greatly appreciated
Thanks !
Ok, so i got this random Huawei P20Lite right?
Back isnt pealed off, works fine, no damages.
BUT WAIT... About Works Fine... It Wont really boot up into The OS!!!
Somethimes shows this really weired Image when pluged in and charging the phone, or randomly:
A green Screen with a Red Square on Top and a Blue one Down.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not My Picture
It will then boot up and greed you with A:
Again, not my Picture.
Acording to Huawei, You have to Use HiSuite to recover it.
1. Put the Phone into Fast Boot. AND conect to PC
2. Open HiSuite on Your PC and click on Recovery mode or whatever its called.
3. i donk know i forgot.
anyways, i get this nice little message
(In translated, this means That: Your Device doesnt support System Recovery.
Bro wth
Anyways, our phone story doesnt end there...
I tried doing it without the Computer.
using eRecovery!!! not surprising i know...
Still, it was stuck on booting animation trying to enter eRecovery.
According to Huawei, "this message is displayed when a system file is replaced or modified, or the system is manually updated to an unofficial version". They were responding to another user with the same issue as mine.
I think that this is the Issue. Still, the instructions to fix it, dont work. (as tested above.)
Tutorials show the eRecovery method without the PC.
Here are some info i found:
Another Guy having the same issue:
i forgot the link but someone else on XDA Had the same issue.
please help!!!
hello sir did you have any luck resolving this issue (I've purity much looked every were but I had no chance)