[Question] Pixel Experience 12+ on my Redmi 9 is rebooting on lock screen. - Redmi 9 / Poco M2 Questions & Answers

Hello, it's my first post on this forum so sorry If I made this thread in the wrong place.
I have been trying to install PE 12 (plus edition) using official PE site (https://download.pixelexperience.org/lava).
After many attempts to do so, I ended up installing different TWRP recovery images and wiping everything from my phone.
Then I've tried installing official recovery image from site and I've installed ROM by adb sideload and it worked.
First boot wasn't a problem, but from start phone would sometimes crash when attempting to turn it on (or, attempting to unlock lock screen. I can write my PIN, but then rebooting happens). When it wouldn't crash (it's not happening every time) everything would be working as long as I don't turn it off. I don't know what is causing that behaviour.
Would reinstallation help or is it hardware problem (not enough RAM etc.), or lack of swap partition?
PS: Updating every app on phone doesn't help, as well as removing lock screen (no PIN etc.).
Update: I have installed different ROM from sourceforge dedicated to my phone version (galahad). It is android 11. Works 100% fine.

Related

Data Partition always destroyed after turning off phone

Hello there.
I have a Huawei P9 (EVA-L09) with an unlocked bootloader and a custom ROM.
Since a few days I started experiencing something completely weird.
Every time I happen to turn off my phone (often only because the phone had gotten quite warm and I want it to cool down then) I then land in the boot animation and get stuck there. After forcefully rebooting the phone from there (about half of an hour) I held the Volume Up key for three seconds during the warning screen and eRecovery told me about the Data Partition to be badly damaged and it would be recommended to recover it.
There are two ways I can do from here (and also did):
First way is to let it recover using eRecovery, connect to my wireless connection, however the phone always tells me that there was a problem getting the package info for my phone. (Does Huawei stopped supporting the P9 eventually?)
The second way is to run TWRP and reinstall the custom ROM (In my case RROS 5.8.5 for my P9) and to never turn my phone off again. However this isn't always possible to keep it on since it also could happen that I'm not at home and my battery suddenly died.
Installing the stock ROM (or a custom ROM based on a stock ROM) however doesn't work. The stock ROM itself simply won't get installed, neither over the dload method or TWRP or fastboot and a custom ROM based on the stock ROM results in having my phone simply getting a black screen when locking it and then I need to reboot it to use it again.
What can I do? Could it be that my flash memory could be corrupted or something could have happened with one of the partitions of the phone?
Greetings.
EDIT: I managed to install a stock firmware using this link right here.
After the stock firmware was installed, doing a factory reset and wiping the cache every problem I mentioned above this edit vanished.

stock rom lockscreen problems

Hi, this is my first post and im having problems with my A6.
I tried to install TWRP wich mostly worked fine, but i didnt follow the tutorial correctly wich left my device boot looping at the boot-logo (i didnt install the zip files needed),
so i thought i soft-bricked my device and i downloaded correct stock rom versions from [cant post outside link because im new, but it would go here]
and installed it with Odin3.
This has worked fine and i restored it again, but for some reason if i set the lockscreen protection (like PIN or Fingerprint) it first wont work (but it shows changed in settings)
and when you reboot the device it soft-bricks at the lockscreen and keeps showing the samsung logo then lockscreen for 1 second and samsung again etc. (this wont brick if i dont set any protection)
I have tried a lot of things like installing TWRP again and clearing cache but none seem to fix the problem (other than doing a factory reset).
so im asking here if someone has a clue to what is happening?
EDIT: i will try to install a older version and try to update it with the official updater and i will report back shortly
Results: It did fix my problem with the lockscreen but if i flash TWRP and install Magisk it wont work again
EDIT2: apparently if i wait long enough at the lockscreen-bootloop(atleast couple of minutes) it will grant me access but the protection still doesnt work
EDIT3: Im using Android 9 and i noticed that this is probably the cause, but i didnt find a updated version

Phone stuck in bootloader screen after enabling encryption

I recently installed the latest Arrow OS 10 sanders version on my phone, everything was working fine so I decided to encrypt it as I needed to install some apps from my work. I did it in the Security options in the OS, not using TWRP in recovery mode.
It's been 3 hours since the phone is stuck in the bootloop screen, it already rebooted alone once but nothing else. What should I do? Keep waiting more time or what?
Thanks!
Hello,
same over here:
If I use lineageOS (lineage-17.1-20200720-UNOFFICIAL-sanders.zip - see https://forum.xda-developers.com/showpost.php?p=83100891&postcount=24), the phone gets stuck in bootloader screen when encrypting the phone (I let it run for 12 hrs). The same applies to HavocOS.
If I use EvolutionX (EvolutionX_4.6_sanders-10.0-20200810-0503-OFFICIAL.zip - https://forum.xda-developers.com/mo...nt/rom-evolution-x-4-0-moto-g5s-plus-t4031813), the phone gets into a reboot loop, once I order it to encrypt.
I've also tried an earlier version of lineageOS (lineage-17.1-20200105-UNOFFICIAL-sanders.zip), which used to work since February 2020 - with encryption but without any hazzle.
Any ideas on that?
I've tried it with
twrp-sanders-r20.img (twrp-3.2.1-r21) and twrp-3.4.0-0-sanders.img (twrp-3.4.0).
What is also strange: even if I format the system/data partitions, the phone still has the Microsoft Exchange services installed (I installed them during this entire mess, since I'm required to use it for company access). I thought, I should have been removed by formatting the phone... not?
Thanks a lot.
kniffte

LineageOS 16 to 18.1 resulted in boot loop or unstable behavior; no WiFi or cellular

I upgraded my Moto X4 from LineageOS 16 to the latest 18.1 build by following these instructions. When I rebooted, the phone was stuck on the boot screen with the green circles. I installed the latest version of TWRP and reinstalled the 18.1 image. Sometimes the phone stay in the loop, but usually it was get the the home screen.
However, it still doesn't work. Sometimes the phone reboots shortly after arriving on the home screen. Sometimes it has WiFi turned off and is on airplane mode. In that case, it seems stable until I turn either of those on, and then it reboots. Running an app might also cause it to reboot. The touchpad buttons at the bottom of the phone also become unresponsive.
I tried installing the latest LineageOS 17.1 build, and that just stays in the boot loop too.
Like a first rate noob, I didn't make a backup of the v16 installation before the upgrade. I have a backup of the OEM rom that I made in 2019, when I first put LineageOS on the phone, but I'm worried about erasing my data.
I appreciate all suggestions. One thing I considered doing, but have not figured out how to do, is to look through the logs to find out what is making the phone reboot from the home screen. "adb logcat" might be the answer.
Another question I have: Does each "slot" have its own recovery? I think that's the case, and I think I have the newest TWRP in both slots.
kalbfled said:
I upgraded my Moto X4 from LineageOS 16 to the latest 18.1 build by following these instructions. When I rebooted, the phone was stuck on the boot screen with the green circles. I installed the latest version of TWRP and reinstalled the 18.1 image. Sometimes the phone stay in the loop, but usually it was get the the home screen.
However, it still doesn't work. Sometimes the phone reboots shortly after arriving on the home screen. Sometimes it has WiFi turned off and is on airplane mode. In that case, it seems stable until I turn either of those on, and then it reboots. Running an app might also cause it to reboot. The touchpad buttons at the bottom of the phone also become unresponsive.
I tried installing the latest LineageOS 17.1 build, and that just stays in the boot loop too.
Like a first rate noob, I didn't make a backup of the v16 installation before the upgrade. I have a backup of the OEM rom that I made in 2019, when I first put LineageOS on the phone, but I'm worried about erasing my data.
I appreciate all suggestions. One thing I considered doing, but have not figured out how to do, is to look through the logs to find out what is making the phone reboot from the home screen. "adb logcat" might be the answer.
Another question I have: Does each "slot" have its own recovery? I think that's the case, and I think I have the newest TWRP in both slots.
Click to expand...
Click to collapse
Hello,
I have come here from.
Actually upgrading from an older Android to newer Android is almost never very smooth, and hence should be avoided if possible, but if you have done so and currently experiencing boot or device operation problems, then:
1: Open TWRP, and go to 'Wipe'.
2: check ONLY 'cache' and "Dalvik / ART Cache", and uncheck the rest, then proceed by swiping the trigger which reads "Swipe to Wipe".
3: Wait for 3 seconds.
4: Reboot to system.
5: If the system boots now, then reply with written "Solved", else the issue.
Thank you...
Thank you very much for replying. I followed your instructions for both slots on my phone, but neither shows any improvement. The 18.1 slot continues to get to the home screen and then reboot as soon as I try to do anything (or randomly before that); the 17.1 slot continues not to get past the green circles screen.
Although the Lineage website no longer hosts builds for v16, I was able to download the last signed v16 nightly build from Archive.org and to verify the signature using these instructions. I booted to TWRP sideload mode and ran `adb sideload <v16 build>`. Now that isn't working either! It seems to loop at the circles screen for a while. Then it gives me a message about being unable to boot and asks if I want to do a factory reset. I did not try a factor reset because I think that erases my data.
I resolved the issue by following the full installation instruction for Moto X4. I tried it with versions 18 and 17 first, but the rebooting problem continued. Fortunately, it worked this time when I put version 16 on the phone again.
I have version 16 on mine and I don't have the will to try to update. Migrating from version 15 to 16 the first time gave me issues and troubleshooting woes and I don't wish to repeat that process. Pie works good enough for me, F it. Just wish it would receive security updates still, but the devs are done with it.

Phone randomly shows boot animation on custom rom

Hi everyone! I have been suffering with this problem for 2 full days on my S10 (SM-G973F/DS) and now i just have absolutely no idea how to fix it, so I thought it was worth writing about it here.
On stock, I used one old and outdated application that made user certificates system certificates, but which worked. Having tried it on EvolutionX 5.9.1 (Android 11), it brought the phone into a bootloop. I didn’t have a backup and because in order not to go through the installation process on a new one again, I decided that I would try to delete the folders from the data partition ONLY, but after half a day of attempts, nothing happened and I started to install the rom from scratch, but then weird things began to happen: after reinstallation/factory reset, boot animation randomly started (check attached video), which either went into an endless boot, or loaded the system back, but then if boot animation started on loading then this loading become endless, and the buttons (in the system) "Reboot to recovery", "Reboot to bootloader" and etc simply turning off the phone without booting into the recovery or bootloader, and if this happened, then somewhere in 2 minutes after turning it off.
I think i tried almost everything: re-installation according to the instructions, re-installation according to the way I did it before, I even tried to install the stock, and after the recovery again and then rom, but absolutely nothing changes, I cannot use custom rom if it is up to this worked fine and everything started on the same version as I was trying to install like before, I even tried to download the rom installation file again, not installing magisk-patch in boot, installing multidisabler, even find my old backup for TWRP that has every partition, but absolutely nothing changes, maybe someone knows how to fix it?
Thanks in advance!
P.S Stock rom works perfectly (android 11), but i want to use custom anyway (also android 11)

Categories

Resources