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!
Related
Each time I boot up my phone it reverts to a previous state no matter what I do. It started 2 nights ago when I was messing with it. I wanted to install another rom and try rom manager. RM gave me an error saying it couldn't do something and fix permissions sometimes worked. I went into CWM touch and did a "fix permissions". I had also just installed CWM touch a few minutes earlier to try it out. I gave up on RM and just tried installing CM9 alpha nightly the usual way. I got the CM9 startup animation, but when the phone starts it's in the same earlier state. I was on AOKP build 28.
I've tried:
Restoring a previous nandroid backup
Reinstalling CMW regular via the Toolkit and fastboot
Fixing permissions (again) via CWM touch
Wiping everything CMW will let me... multiple times.
So far no matter what I do the phone is in the same state. I can install apps, take pictures, etc., but when the phone reboots (it's doing random reboots often) none of them are saved. I think the fix permissions somehow made most or all of my directories read only and the phone is rebooting when the ram is being fully used, but I'm not sure. I remember getting one "read only" error last night, but I was trying so many things the exact moment escapes me. I can boot into CMW regular via the Toolkit as long as I don't flash it.
I have Windows 7 and Ubuntu at my disposal.
edit 1: I may have mounted the /system path before I did a fix permissions if this matters. It tells me /system is read-only.
edit 2: I can't delete anything off of the SDCARD when it's mounted as usb storage in Windows.
While installing the most recent update to my encrypted SG3-L710, the phone restarted and while booting up remained stuck on the blue/white Samsung logo.
-After removing the battery and attempting to get around this several times it appeared that the update had soft-bricked my phone. I was never prompted to put in my passcode to undo the encryption.
-I am able to access CWM Recovery and, being that the only significant thing I would lose are my contacts so I attempted to perform a factory restore which was unsuccessful. It appeared the error indicated it was the /sd_card and /data folders posing the problem.
-I attempted to mount and unmount the /sd_card and /data folders which was unsuccessful, formating them also did not work.
-I downloaded Odin and the PIT file as my last hope. I attempted to flash the stock ROM to the phone and hopefully wipe the old ROM from the system. Odin also encountered problems with the /sd_card and /data and was not able to progress past that point. Now I am attempting it a second time to obtain the specifics and it's stuck on "<ID:0/004> Send lock information...".
Any ideas on how to be able to bypass the encryption and wipe my phone so I can flash a new ROM on this?
I've been working on this problem for almost two days now and I would greatly prefer not having to send my phone into Samsung and spend $100 to do this for me! Thanks ahead of time, bear in mind I'm new to this and might be a bit slow.
Hey; first time on here.
I came across this app, exactly titled "TimeZone Fixer (ROOT)", and was curious about it. Downloaded and played around with it. The thing told me to restart to take on effect, so I did. Phone goes through the reboot process, I enter in my password to unencrypt my device (Yes, I've encrypted my device), then suddenly the boot animation stops abruptly and the phone reboots again by itself
I'm currently running on CyanogenMod 10.2.1 ("cm-10.2.1-jfltetmo.zip" precisely), so my automatic next step was to reflash and start over. I thought it would simply delete all of my encrypted data, but it appears I still have my encrypted data (It still asked me to enter my password for decryption after reflashing).
I'm lost. I think I broke my phone. :crying: Is there any way to recover my phone?
I got it.
All I had to do is boot into recovery mode, go into mounts and storage > format /data and /data/media (/sdcard)
From the mouth of Uncle Ben:
With great power, comes great responsibility.
Click to expand...
Click to collapse
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.
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!