Hey,
I am having a bootloop after a pretty normal Android usage. All I did was:
browsing Internet, moving some photos, deleting file, moving some videos to Shelter (workprofile)
using Instagram inside Shelter, uploading a video
then I rebooted (in order to update my shelter file directory), and I suddenly got a system message that my workprofile was locked and requested my security code, I entered it several times but the workprofile including all shelter apps and files stayed inaccessible, it would keep requesting the code
so I rebooted again and since then the phone gets stuck at the Redmi logo, then boots into twrp recovery
I am running crDroid 9.2 on a Redmi Note 8. I have been running that system for at least two months now, only minor issues (never a bootloop). I was not really messing with any system settings/files.
Booting into TWRP, I am not being asked for decryption of the data, so maybe the system is even corrupt on that level... What can I do
I am running latest twrp 3.7.0-12.1
Do you have any ideas of what could be the least invasive procedure to fix this bootloop (i.e. without losing any data)?
Thanks in advance!
Related
Hey,
I wanted to create an nandroid backup in TWRP and got error 255 in the process.
I got the log of the failed update:
cloud.directupload.net/dfZq
So i searched for a solution, and the internet said that i should remove the file wich causes backup to fail. The logs said it was '/system/app/AndroidPay'
This is a file, not a folder.
So i removed the file, keeping an backup of it, booted into TWRP and the backup still failed.
To my surprise the boot into OxygenOS fails now. It shows the Oneplus Powerd by Android logo, turns black and reboots into twrp. Recovery and Bootloader seems to work fine.
So I connected my device with my computer and tried to get the file back to '/system/app' using adb.
I tried 'adb push AndroidPay /system/app' and it seems to be transferred succesfully, however the boot into oxygenOS is still not working.
I think it can be fixed by formatting the device and flash OxygenOS new to it, but I really don't wanna do that.
General Information:
Oneplus 3
OxygenOS 3.3.4
Rooted
Xposed Installed
No custom kernal
TWRP 3.0.2-0
File wich may be broken: cloud.directupload.net/dfZs
Is there an easyer way than resetting my whole phone to get it to work ?
I'm sorry for language mistakes or maybe leaving relevant information.
Thank you for help
I've had same problem today, my solution is restore "System" part (only system) from old backup, it saved my data and OP3 works fine after that
Wipe system, then flash OOS and it should work fine. If it doesn't Im afraid you need to do a full clean install since it isn't system related then.
I'm sure this is something stupid I did during the initial rooting & bootloader unlocking. Everything works fine on my OP3 except if I flash ROM updates (i.e; new LineageOS updates in my case) - after installation the phone no longer accepts my PIN and I end up having to to a factory wipe & reinstall of apps etc.
If it's related I also always see a 'dm verify is not started in enforcing mode' screen before the OS boots, whenever the phone is restarted (not after ROM flashing, just whenever I do a restart)
Any suggestions would be much appreciated.
Thanks,
Steve
steveharman said:
I'm sure this is something stupid I did during the initial rooting & bootloader unlocking. Everything works fine on my OP3 except if I flash ROM updates (i.e; new LineageOS updates in my case) - after installation the phone no longer accepts my PIN and I end up having to to a factory wipe & reinstall of apps etc.
If it's related I also always see a 'dm verify is not started in enforcing mode' screen before the OS boots, whenever the phone is restarted (not after ROM flashing, just whenever I do a restart)
Any suggestions would be much appreciated.
Thanks,
Steve
Click to expand...
Click to collapse
In Twrp's file manager, go into /data/system and delete the following files. This will get rid of the screenlock, but you will have to add a new one once you are booted in to the ROM.
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
You may not have all of them, but don't worry.
About the DM-verity issue, nothing bad will happen. If you really want to get rid of it, you can try the méthode from here https://forum.xda-developers.com/oneplus-3/how-to/fix-easy-method-removing-dm-verity-t3544339
P.S. Lineages sucks... IMO
Brilliant - thanks for the information!
Steve
I have OnePlus 3 with OxygenOS 5, unencrypted and rooted with Magisk. In recovery, TWRP cannot access /sdcard. With ADB, when I try to get a shell into /sdcard, I get "I/O Error". When I system boot, it goes into bootloop half the time.
Except those two problems, I get random reboots, almost five per day. I have those problems since a few days, and I did not do any updates at this time.
When I succeed to boot, I am able to access my data in /sdcard.
I had a few problems with my LCD screen that was not responding, but the problem disappeared by itself.
Any idea what I can do? Could it be weirdly related to my previous touch screen problem? Thanks!
I've a Moto Z Play, I've been using /e/ OS for a few months and it worked quite well. Today the phone froze while I was using it. I rebooted and since then it's stuck on /e/ logo (= boot loop).
I was not updating system, I was just using phone
I can enter in TWRP recovery, use adb shell, etc..
I already did cache and dalvik cache wipe, and rebooted without SIM nor SDcard and it didn't work
I managed to dump boot log (
Code:
adb shell cat /sys/fs/pstore/console-ramoops > ./boot-loop-kernel-log.txt
) but I can't understand what is failing
I uploaded my logs here: drive.google.com/open?id=1ekTRe_dWSLKq8TmLqa26uae0SOE9uccy , sorry I can't post the link because I'm a new user.. but url is complete. There are 3 files:
Number 1: I let the phone reboot several times, the log is 150 seconds.
Log number 2: I switched to recovery as soon as I detected the phone rebooted, so log is only 30 seconds. The phone makes a small vibrations at every reboot. However the screen always shows the /e/ OS logo.
Log number 3: again I let the phone reboot several times.
Perhaps some hardware might be failing.. perhaps the camera or the GPS.. On this forum I saw a post of somebody stuck in loop because of screen temperature calibration fail, he deleted a file (that doesn't exist on my device) and solved the problem; but my problem is that I can't understand boot log, I can't understand what is going wrong. :crying:
[SOLVED] I solved the issue
I solved the issue. I went to TWRP and did a simple wipe. I didn’t want to do this because I was going to loose all my apps and configs, and actually I lost them, but at least device is usable again.
Dear XDA-Developers, after installing August 2020 update for my Pixel 2 XL and possibly applying incorrect Magisk bootloader version, my phone doesn't boot anymore and is constantly stuck in bootscreen animation.
What I have tried so far to no result:
- Re-flashing both May 2020 (previous working version) and August 2020 without -w flag to preserve my data that I would ideally like to recover.
- Side-loading May 2020 and August 2020 OTA versions through TWRP
- Creating and booting from Magisk-core only image as per guide called "How to Create & Boot from a Magisk Core-Only Image to Fix a Bootloop Without Custom Recovery" (since I cannot post links in here).
While unpacking and repacking Magisk-core image I noticed that "BOARD_OS_PATCH_LEVEL 2020-05" indicating that I might have had the wrong version applied to it.
So looks like my only hope is finding magisk_patched.img file for August 2020 Pixel 2 XL (image-taimen-qq3a.200805.001) and trying to patch it to disable Magisk upon startup. Would anybody be so kind to post one here?
I have also tried to make data backup using TWRP, but it fails mounting /data partition and shows that it's 0 Mb.
Any other ideas to how to save the phone without wiping all the data would be greatly appreciated.
Thank you all very much for whatever suggestions you might have to help me!
hencrow said:
So looks like my only hope is finding magisk_patched.img file for August 2020 Pixel 2 XL (image-taimen-qq3a.200805.001) and trying to patch it to disable Magisk upon startup. Would anybody be so kind to post one here?
Click to expand...
Click to collapse
Magisk doesn't touch the bootloader, only modifying the boot image. Given your description of the issue, I don't believe Magisk to be the culprit here. Based upon personal experience, flashing a stock image using flash-all.bat, whether the -w flag is present or absent, totally removes Magisk as the stock boot image overwrites the modified version created by Magisk.
It's clear though that you have an issue, but how much of it is brought about by misconceptions and incorrect knowledge is unknown and at this point irrelevant. So what do you do now? Try backing up your data using the instructions here. But be prepared for the very real possibility that you have already lost all your data, and only a stock ROM install with the -w flag present will restore the device to working order.
Strephon Alkhalikoi said:
So what do you do now? Try backing up your data using the instructions URL. But be prepared for the very real possibility that you have already lost all your data, and only a stock ROM install with the -w flag present will restore the device to working order.
Click to expand...
Click to collapse
Thanks for getting back. I'm a little confused how can adb backup can work though if the only thing I can boot into is TWRP and even it fails to decrypt /data partition (it just shows "Could not mount /data and unable to find crypto footer" upon startup).
And with my very limited Android debugging experience wondering if things are really that hopeless that it's not possible to simply copy and decrypt user data partition or there aren't even any logs from failed Android boot attempts that can be looked at to at least diagnose the issue.
hencrow said:
Thanks for getting back. I'm a little confused how can adb backup can work though if the only thing I can boot into is TWRP and even it fails to decrypt /data partition (it just shows "Could not mount /data and unable to find crypto footer" upon startup).
And with my very limited Android debugging experience wondering if things are really that hopeless that it's not possible to simply copy and decrypt user data partition or there aren't even any logs from failed Android boot attempts that can be looked at to at least diagnose the issue.
Click to expand...
Click to collapse
It may not work, and in fact it probably won't, especially if TWRP can't mount the data partition. That's why I said you should be prepared for the very real possibility that you have lost all your data. As for getting logs to diagnose the issue, the only certain way to get a catlog is to record the logcat from the device on your PC as you boot it, via USB Debugging. Something that likely will not be of much help now, given what you have tried doing to resolve the issue.
At this point, in your position I would simply cut my losses and install a factory image and let it wipe the data. Once you are back up and running, you want to get into the habit of backing up app data. There are many apps that can do this, but regardless of the app used, backing up the app data to internal storage or to a location like Mega or Dropbox will make life easier if you ever encounter this again.
An update if anybody is wondering what happened - flashing Android 11 Beta 3 brought the phone back to life with all the data intact. All versions of Android 10 haven't even reached the booting stage where adbd was started and showed no logs.