Yesterday I successfully updated (reflashed) my S10E from Lineage OS 18.1 to 19. Because I did not like the Android 12 look I reflashed the latest LineageOS 18.1. After rebooting the phone got stuck in a bootloop. I could still access TWRP. I tried wiping caches and system. I tried reflashing, but after flasing is done a lot of /data/... (permission denied) errors are displayed and the phone is still in a bootloop when rebooting. I also tried repairing the file system. It says that repairing is done, but after flashing the rom I still get /data/... (permission denied) errors, resulting in a bootloop after reboot.
I don't know what happened. Any ideas what went wrong and how I can fix this?
Related
I attempted to flash the MOAR rom 8.0.0, and I first flashed the ML1 radio beforehand, then I reset like normal after flashing a new rom.
Waited 15 minutes at the Samsung Galaxy S3 logo and did a battery pull, second boot got me into the rom which then had a system UI error and reset, it was then perpetually stuck on the logo, no amount of waiting would get past it.
Then i attempted to restore my old rom from backup, but while going into TWRP this mysterious message appeared that never happened before:
Updating partition details...
E:error opening '/data/media/0/Android/obb'
E:error: I/O error
E:error opening '/data/media/0/Android/obb'
E:error: I/O error
I can't wipe anything as somehow everything on my phone has become read-only, and installing a new rom has no effect, even rooted ADB can't push files to the internal memory, any ideas on how to fix?
Update:
Nevermind, fixed the problem by using TWRP to do a complete format, phone now works fine, I didn't find anyone with the same problem as me using a search, so leaving this thread might be a good idea for future searches.
I wanted to root my device, 930F with Oreo installed. I flashed TWRP 3.2.3 with Odin, and had Magisk at my internal storage root directory.
When I restarted the device TWRP was gone, so I flashed it again with Odin and starting TWRP it asked if it could make modifications to be permanent, I allowed the modifications. When I tried installing Magisk, I couldn't find it as my whole internal storage didn't show anything (encryption maybe?)
And then I tried restarting without having done the root but now it just boot loops at the Galaxy logo.
What should I do?
Update:
I copied Magisk to my micro SD and was able to install it with TWRP. After restarting the phone did pass the part where it was boot looping, but it stops at:
----------
"Verification Failed
Unable to restart your device. the integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
----------
This is the dm-verity that I have read about? Is there a way to not need a factory reset?
I've seen this thread: https://forum.xda-developers.com/galaxy-s7/help/to-magisk-data-encryption-s7-t3667007
Tried flashing with TWRP the TIMA tweak and verity disabler, but still had the same error.
Anyone have any ideas or should I just clean install the stock firmware back?
https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
I used the guide above, TWRP booted fine, then installed the SuperSU zip file and rebooted. That got me to a black "Verification failed" screen. I rebooted to TWRP and in the log I noticed that it couldn't mount /data. So I googled it and followed this guide:
https://www.youtube.com/watch?v=T-7neHzSIvc
Repairing data threw an error. I still went ahead and changed the partition to exFat and it said it was done but it kept loading and eventually threw an "e: recv error on uevent". So I rebooted TWRP and it didn't start at all anymore. It doesnt get past the first twrp screen, it doesnt get to the swipe right part.
Reinstalling TWRP didnt work. I've tried other older versions as well, same problem.
RazvanPaun said:
https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
I used the guide above, TWRP booted fine, then installed the SuperSU zip file and rebooted. That got me to a black "Verification failed" screen. I rebooted to TWRP and in the log I noticed that it couldn't mount /data. So I googled it and followed this guide:
Repairing data threw an error. I still went ahead and changed the partition to exFat and it said it was done but it kept loading and eventually threw an "e: recv error on uevent". So I rebooted TWRP and it didn't start at all anymore. It doesnt get past the first twrp screen, it doesnt get to the swipe right part.
Reinstalling TWRP didnt work. I've tried other older versions as well, same problem.
Click to expand...
Click to collapse
Install TWRP again, then any rom which is already rooted with magisk. Or install TWRP then a Rom and root after with magisk, also you don't have to install TWRP and root at the same time.
Ignore the "recv error" it means nothing, just a quirk of TWRP sometimes. Don't bother with Supersu, magisk works better.
try this TWRP: https://mega.nz/#!tMVCBYrB!Bcvd2tGuvvRfpCPdWvpGwy53f25Oe5qe_zCOSLX_-rA
or this: https://mega.nz/#!xEdWwYQZ!IdTYbSyUzDptG-ArdvDZt1_hKG5qBbwP3P-mkcJCelo
Can you still get into download mode? If so try a full odin flash of stock firmware.
odin flash back to stockrom
then use this tutorial :
https://www.youtube.com/watch?v=uYYyxWH3xew
it worked perfect for me and also has decryption module
Is there apps like sgs screenbooster for better sensitivity??also who use sgs?any reccomended settings for this app??
Hello,
My phone(Samsung galaxy s8) just had a crash and is stuck on the blue screen with "Installing update". After several seconds the screen goes away and boots straight into the recovery mode.
The log that i see in the recovery is :
Fail to open recovery_cause(No such file or directory)
Failed to mount /efs
Unknown volume for path /odm
dm-verity verification failed
I tried to install the stock firmware (I cant link to the webpage but im 100% sure its the correct one) but it wont boot and goes to the "Installing update" again and after that to the recovery.
I tried installing twrp but it wont install due a FRP lock. i read that you should wipe your data and factory reset. Also tried that but again no succes.
Can someone please help me.
Thanks in advance
nickglas said:
Hello,
My phone(Samsung galaxy s8) just had a crash and is stuck on the blue screen with "Installing update". After several seconds the screen goes away and boots straight into the recovery mode.
The log that i see in the recovery is :
Fail to open recovery_cause(No such file or directory)
Failed to mount /efs
Unknown volume for path /odm
dm-verity verification failed
I tried to install the stock firmware (I cant link to the webpage but im 100% sure its the correct one) but it wont boot and goes to the "Installing update" again and after that to the recovery.
I tried installing twrp but it wont install due a FRP lock. i read that you should wipe your data and factory reset. Also tried that but again no succes.
Can someone please help me.
Thanks in advance
Click to expand...
Click to collapse
I'm going to take a guess here, you had the device rooted and then you tried to apply an OTA stock update while the device was rooted? Tyically, stock OTA updates can't be applied to devices that have been rooted because the updates require the device to have an unmodified system partition(no root) and they require stock recovery instead of custom recovery. There are "some" devices that can apply stock updates while rooted, but those are few and far between.
If that is what you did, you need to do some searching for repairing failed OTA updates on rooted devices.
Sent from my SM-S767VL using Tapatalk
Hey lads, forgive me im new here and frankly quite distressed so forgive me for not finding the right forum for this.
So, i have successfully managed to brick my phone in a stupid and ignorant attempt to flash a custom rom. I cant boot to Android, no matter how many times I reboot, it always boots to fastboot. I can access recovery tho, I have PixelExperience recovery installed. When booting to recovery i get a error message:
E: Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: no such file or directory
E: Failed to bind mount /mnt/staging/emulated/media/0 on/storage/emulated: No such file or directory
I did a factory reset before flashing the rom, is that related to it?
Also out of pure desperation I ran fastboot w command, though that seemingly changed nothing. Though im not sure if the error message occured before or after the wipe.
How do I fix this?
throwawaybrickedphone said:
Hey lads, forgive me im new here and frankly quite distressed so forgive me for not finding the right forum for this.
So, i have successfully managed to brick my phone in a stupid and ignorant attempt to flash a custom rom. I cant boot to Android, no matter how many times I reboot, it always boots to fastboot. I can access recovery tho, I have PixelExperience recovery installed. When booting to recovery i get a error message:
E: Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: no such file or directory
E: Failed to bind mount /mnt/staging/emulated/media/0 on/storage/emulated: No such file or directory
I did a factory reset before flashing the rom, is that related to it?
Also out of pure desperation I ran fastboot w command, though that seemingly changed nothing. Though im not sure if the error message occured before or after the wipe.
How do I fix this?
Click to expand...
Click to collapse
hey i have the same issue, did you find a solution