Boot loop and recovery logs - Samsung Galaxy A50 Questions & Answers

Hello!
Samsung Galaxy A50 (Android 11, A505FMPUS9CUK2).
I have boot loop after entering my password.
Full recovery logs: https://cloud.mail.ru/public/RST8/SPGeyWEsg
1. How can I save all data on phone? I don't have connet to usb.
2. What's going with the phone?

Related

[Q] stuck on boot screen after installing CyanogenMod 10.1 BETA (Build 4)

Hi,
I have a Samsung i8150 and tried to install the CyanogenMod 10.1 BETA (Build 4). After following the instructions and installing the ROM and gapps the phone gets stucked at the boot screen of cyanogenmod. Unfortunately, the backup does not work (phone stops at booting as well). So I do not have any possibility to copy another rom-image to the device.
*Any ideas?
Thanks.
chrimat said:
Hi,
I have a Samsung i8150 and tried to install the CyanogenMod 10.1 BETA (Build 4). After following the instructions and installing the ROM and gapps the phone gets stucked at the boot screen of cyanogenmod. Unfortunately, the backup does not work (phone stops at booting as well). So I do not have any possibility to copy another rom-image to the device.
*Any ideas?
Thanks.
Click to expand...
Click to collapse
If you can enter to recovery (cwm) , reboot to recovery then go to mounts and storage then mount usb storage and w8 for the pc to recognize your external sd-card then save put any rom-image you want to flash. Just don't forget to make a clean installation.
Note: CWM 6.0.5.0 has that option, idk know if yours got that too so kindly check it.

Redmi 1S stuck at mi logo : How to recover data?

Hi everyone,
My Redmi 1S bailed out on me and is now stuck at the boot logo. I need to recover my data, before I flash a rom onto it.
Can someone please share a way by which I can access and recover my data from the boot screen / recovery mode / fastboot screen.?
Quick update : I tried Mi Flash but my phone is not getting detected
Please help
Thanks a ton in advance.
If you have a custom recovery like TWRP, you boot to recovery and use the built in file explorer or ADB to pull files out to the memory card or otg pendrive. If you don't have TWRP installed, then boot to fastboot and install TWRP first.

Wileyfox Swift stuck/boot loop

Hi all.
I have a phone stuck in boot loop. It's a stock ROM, Android 7.1.2 (January 2018) but I dont have exact image reference (Wileyfox/switf/crackling 7.1.2/N2G48B/eeea277114 from recovery mode) . Secure boot is still enabled and phone is locked, but I have the unlock schema
When the phone boots, it stucks approximately 2 seconds after the lock screen. The screen then turns off and it reboots after a few minutes. If I am fast enougth, I sometimes have time to unlock but it freezes immediately after, and reboot after a while.
It started after the phone has been turned off. The last application installed is the GEEV application. Maybe it's the cause, or maybe the phone is full.
What I tried:
As stated in Facebook Wileyfox post ( unable to post full url: officialwileyfox/posts/1844545742523409),
I can access the safe mode (vol down at Wileyfox logo), but it does not change anything, it still stucks and I can not deactivate the last application installed.
I can access the bootloader and recovery mode, but I cannot access it via adb / fastboot (linux), I suppose because I cannot enable acces in devolopper mode in phone setting. I tried to update an older image from SD card, but the phone refused to downgrade to an older image.
I also tried to wipe cache partition.
Photo and contacts are backup, only SMS are not backup and I would like to access it.
Do you have any suggestion to access user partition or unblock the phone wihout wiping user data?
Thanks
If you can reach recovery mode there should be a phone reset option that can clear the apps.
Here are recovery mode choices:
-Reboot system
-Reboot to booloader
-Apply update from ADB
-Apply update from SD card
-Wipe data/factory reset
-Wipe cache partition
-View recovery logs
-Run graphics test
-Power off
I already tried wipe cache partition without result.
But I didn't try wipe data as this will also wipe SMS, won't it?
SMS should be saved to the cloud and restored when you enter your gmail account after the reset.
No it's not saved, that's why I need to access the phone if there is a way
If you can unlock the bootloader you could install twrp recovery which has an mtp mode which would give you access to your files. Suspect unlock bootloader will not be available to you.

Redmi Note 5 Pro Not Rooting

Hello There,
I have Redmi Note 5 Pro with unlocked bootloader. But unable to root it no matter what.
Let Me Explain The Situation.
1. After flashing TWRP, it asks for "decryption password" which is nowhere to be found on internet. But in order to decrypt it i had to format the phone. GOOD Now Storage is Detected in TWRP.
2. But if i boot phone in System and again boot it in Recovery then TWRP is replaced with Stock Recovery.
1 & 2 are in INFINITE LOOP now.
3. So OTG...... OTG is not even recognizing by TWRP, but OS is detecting it.
4. TWRP "Enable MTP" also not working.
So Let Me Know If I am Forgetting Something.
Please Help Me To Root IT.
PS : I have past experience of Rooting/ Flashing rom / Unlocking Bootloader etc.
I guess the main problem you're having is that your phone keeps replacing TWRP with the stock recovery once you boot into system. I've had same problem on different devices. To prevent this from happening you should not boot into system immediately after flashing twrp, rather you should boot directly into twrp recovery (try "fastboot boot recovery.img" command after flashing twrp - I'm assuming that your twrp img is saved as "recovery.img") and flash Magisk before booting into system. By flashing Magisk before booting into system your phone would no longer replace twrp, and then your phone would be rooted as well. At least that worked for me.
And also use orangefox rather than twrp on this phone

TWRP logo bootloop and inability to install system

Hello,
I have a strange problem with Galaxy A5 2017 after installing twrp + lineage 18.1. I will explain the problem in sub points.
1) in January on stock software I installed (according to instructions from XDA forum) root, twrp (via ODIN) and bypass with memory decryption. Then I installed Lineage 18.1, Gapps, Magisk and debloater on it to remove unnecessary apps.
2) The phone worked fine until mid-April. Some update was installed and the phone died.
3) The phone wouldn't boot up after the update and only the TWRP logo was looping (logo kept flashing).
4) the phone couldn't boot up, but after I found the only way to get the system to boot up was to enter command "adb reboot bootloader" from windows console. The system booted, but after another reboot unfortunately it was the same thing - the TWRP logo was looping.
5) I managed to upload Lineage Recovery via ODIN, but unfortunately this didn't change anything. Phone was booting to recovery only (but it was working). I tried to update via ADB Sideload from recovery - also without success. Interestingly, the only way to fix it was to fully format with the system partition from recovery and re-upload the system. This worked, and Lineage booted into the android interface, but on the next reboot I unfortunately only had the Lineage loading logo visible for 10-15 minutes - then a reboot into recovery. I had to repeat the formatting and re-upload the system.
6) Interestingly, when I used the combination - lineage recovery, full format, twrp 3.6.1 (via ODIN) - TWRP booted normally and I could install LineageOS. The system would only boot once, and after the next reboot the TWRP logo would loop again.
7) The last problem I noticed is that if I load Lineage system, gaaps package and magiska via TWRP or Lineage Recovery, the system will never boot - either it will loop the logo (if using Lineage Recovery) or the phone will not load the system, it will reset and loop the TWRP logo indefinitely (if using TWRP recovery).
Does anyone know a solution how to restore the phone? Will it still work or for example NAND memory is dead and nothing can be done? Best regards

Categories

Resources