So my Phone is the G935P It's currently Rooted and here is some other info about the phone
Software Version: G935PVPU4BQAA (7.0 Sprint)
Now there is something weird going on when ever i enter the stock recovery I can see at the bottom dm-verity error ...
But im still able to boot the phone ...
I tried looking around on Google and Xda for the past few days and i can't seem to find anything about it does anyone know why it's showing dm-verity error ... and still letting me boot the phone
The full screen when i boot to recovery on my s7 edge looks like this
Code:
[B][COLOR="Yellow"]Android Recovery[/COLOR][/B]
[COLOR="Yellow"]samsung/hero2qltespr/hero2qltespr[/COLOR]
[COLOR="Yellow"]7.0/NRD90M/G935PVPU4BQAA[/COLOR]
[COLOR="Yellow"]user/release-keys[/COLOR]
[COLOR="Yellow"]Use volume up/down and power.[/COLOR]
[COLOR="Blue"]Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Mount /system
View recovery logs
Run graphics test
Power off[/COLOR]
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
Can anyone explain why it shows dm-verity error...
(and before anyone asks if i know what dm-verity is Yes i know what it is it's the function of the kernel that prevents unauthorized flashing unless the packaged is signed by the factory)
Hi, I have a S8+ and I'm having a BIG problem. I tried to put the stock ROM in my S8+, and now it shows the message: failed to mount /efs (invalid argument) in recovery after reboot, after odin says "PASS"... So I select the option "Reboot System Now", and Samsung Logo appear and nothing happens after this. Stuck!
I have OEM Locked and can't enter in the OS... Help!
Once when I had TWRP I backup my EFS. I have this archives, but I don't know how to zip then to Flash in Odin... (look at attach files).
Help!!!
MatheusPimentel said:
Hi, I have a S8+ and I'm having a BIG problem. I tried to put the stock ROM in my S8+, and now it shows the message: failed to mount /efs (invalid argument) in recovery after reboot, after odin says "PASS"... So I select the option "Reboot System Now", and Samsung Logo appear and nothing happens after this. Stuck!
I have OEM Locked and can't enter in the OS... Help!
Once when I had TWRP I backup my EFS. I have this archives, but I don't know how to zip then to Flash in Odin... (look at attach files).
Help!!!
Click to expand...
Click to collapse
I received similar error failed to find /misc partition on recovery...however the ODIN said PASS..
I had to install TWRP and install custom OS couldn't get the ODIN to succeed.
Hi guys I own an S8, SM-G950F. The previous software I was on was Android 8 U2 (can't remember exact one). I flashed the new DBT Android 9 software via ODIN (using CSC, not home CSC). However the phone stays in the "Powered by Android" screen and does not go any further.
I can go into the Samsung recovery mode and have tried wiping both the cache and data/factory reset but this seems to make no difference. As an alternative I have tried flashing the Android 8 files (with bootloader U4), which is successful in ODIN but shows "No command" when booting.
USB debugging was also turned on before applying this update.
Other info:
FRP Lock: Off
OEM Lock: Off
RP SWREV: B:4 K:3 S:3
Any ideas what I could do?
Thanks.
Try Flash Same Firmware Reigon You have own in prev Version
MA7MOD_GSM said:
Try Flash Same Firmware Reigon You have own in prev Version
Click to expand...
Click to collapse
Thanks for your reply. I have tried this although it does not work as the boot loader version is now at V4, whereas the previous software I had was V2. I have tried flashing other Android 8 software with boot loader V4 but it goes into the “No command” state where I can’t access the recovery, only download mode is available.
hs102 said:
Thanks for your reply. I have tried this although it does not work as the boot loader version is now at V4, whereas the previous software I had was V2. I have tried flashing other Android 8 software with boot loader V4 but it goes into the “No command” state where I can’t access the recovery, only download mode is available.
Click to expand...
Click to collapse
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory
I think you Flash worng Firmware send download mode photo
MA7MOD_GSM said:
I think you Flash worng Firmware send download mode photo
Click to expand...
Click to collapse
Firmware was fine not sure what the issue was.
Got around it by flashing latest TWRP and no verity and it loaded successfully.
Thanks
same as me. loaded twrp and no ver opt and magestic but thats all cool but all i want is official with no root or anything. why wont my damn phone boot without all the crap. this method will not allow any kind of ota. same issue when i flas pie via odin except it even worse. cant get to boot
hs102 said:
Firmware was fine not sure what the issue was.
Got around it by flashing latest TWRP and no verity and it loaded successfully.
Thanks
Click to expand...
Click to collapse
after TWRP your fone boot working ... because I have the same issue Samsung warranty center told me to replace the motherboard
hs102 said:
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory
Click to expand...
Click to collapse
I also am seeing the same message in recovery mode. Also in odin mode(download mode) there is extra lines of text. Although in saying this the s8 boots and seems to function as per usual. The storage used from stock firmware is 12.4 GB... Is this normal??
All I am wanting to know is "is this normal for the exynos galaxy s8 running One UI, android 9" ?
or Did I Download a dodgy Rom?
Kdom81 said:
I also am seeing the same message in recovery mode. Also in odin mode(download mode) there is extra lines of text. Although in saying this the s8 boots and seems to function as per usual. The storage used from stock firmware is 12.4 GB... Is this normal??
All I am wanting to know is "is this normal for the exynos galaxy s8 running One UI, android 9" ?
or Did I Download a dodgy Rom?
Click to expand...
Click to collapse
Same here.
https://forum.xda-developers.com/galaxy-note-8/help/weird-message-recovery-e-libfsmgr-t3936625
Did you arrive to any conclusion?
Hey I have the same problem as well... I can't flash twrp because I have oem locked and I can't boot into my because it keeps restarting and getting stuck at some point, and the recovery is saying:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory
How can I fix this?
Is there any update on this? I have the same issue as post #11 on a Samsung A8 sm-a530w.
Any help would be much appreciated.
I've got the same issue on a G950F.
I bought new (sealed, G950FXXU5DSFB), and tried to flash combination file G950FXXU5ASF1 . This did not work. (no boot).
So I flashed what I thought was stock rom matching CSC.
(AP_G950FXXU5DSFB_CL16290088_QB24491245_REV00_user_low_ship_meta_OS9.tar )
The phone boots and operates fine, except for the same message you guys are getting in recovery, as well as a message about no OTA updates.
---------- Post added at 05:54 PM ---------- Previous post was at 05:54 PM ----------
I've got the same issue on a G950F.
I bought new (sealed, G950FXXU5DSFB), and tried to flash combination file G950FXXU5ASF1 . This did not work. (no boot).
So I flashed what I thought was stock rom matching CSC.
(AP_G950FXXU5DSFB_CL16290088_QB24491245_REV00_user_low_ship_meta_OS9.tar )
The phone boots and operates fine, except for the same message you guys are getting in recovery, as well as a message about no OTA updates.
Any news about this? for me I bought used Galaxy Note 8 it was Korean N950N Converted to N950FD, I wanted to Install TWRP and ROOT but I kept getting Failed to Mount Preload error in TWRP and read smwhere its because of messed up partition so not knowing what official firmware it came with I flashed the carrier firmware which phone's IMEI info got me also it was closest to old converted FD baseband now I bypassed this nonsense via twrp but there is not even proper root to install any other custom ROM help me solve this or kindly help me find solution to Failed to mount /preload in twrp
techyrock said:
Any news about this? for me I bought used Galaxy Note 8 it was Korean N950N Converted to N950FD, I wanted to Install TWRP and ROOT but I kept getting Failed to Mount Preload error in TWRP and read smwhere its because of messed up partition so not knowing what official firmware it came with I flashed the carrier firmware which phone's IMEI info got me also it was closest to old converted FD baseband now I bypassed this nonsense via twrp but there is not even proper root to install any other custom ROM help me solve this or kindly help me find solution to Failed to mount /preload in twrp
Click to expand...
Click to collapse
Same problem but my phone s8 g950n korean, Failed to mount /preload, heres what i did to solve my problem:
- MOUNT everything in TWRP Without SDCard
- WIPE everything but NOT SDCard
- FORMAT DATA
- FACTORY RESET
- Reboot Recovery
after that no more Failed to mount /preload in twrp
- Flash Custom ROM
- Rooted my device by Flashing Magisk v20.4
nmx87 said:
Same problem but my phone s8 g950n korean, Failed to mount /preload, heres what i did to solve my problem:
- MOUNT everything in TWRP Without SDCard
- WIPE everything but NOT SDCard
- FORMAT DATA
- FACTORY RESET
- Reboot Recovery
after that no more Failed to mount /preload in twrp
- Flash Custom ROM
- Rooted my device by Flashing Magisk v20.4
Click to expand...
Click to collapse
There was some very simple fix for this mate I don't recall what worked for me, ever since I have change several phones I am on S10 5G right now, so It was just once a faced it and now I dont even remember lol what was it that fixed it for me, I think maybe different TWRP or I flashed Stock Rom the full rom with CSC and everything, just remember don't touch the partitions it was a simple fix of some sorts
hs102 said:
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory
Click to expand...
Click to collapse
Hello Everyone!
I have the same problem with Galaxy Note 8 / SM-N950F
Is there a solution for this??
Please need help, please please.
Thank you
Hello,
im new to this Forum. I try my best to give all the information i have.
What happened?
I tried to install the project /e/ os on my axon 7 mini. First I unlocked my phone with tuliptool in edl mode. I found the twrp recovery-image for my device in this guide (https://www.getdroidtips.com/root-twrp-zte-axon-7-mini-magisk/#Download-Files) flashed it with tuliptool to the recovery partition and it worked. But it broke my stock android rom. I only can boot intro twrp - i cant boot android (only shows zte android title screen). Then i installed the unofficial /e/ port for my device with twrp and it worked. Then i thought i could unroot my phone with tuliptool (i dont know why atm i thougt it will be a good idea) so i ran tupliptool lock unlock and my device was locked again. Now i only can access twrp so i undo the locking. After wiping the data partition with twrp, /e/ startet again. Then i thought that wiping the data partition would solve the issiue with not loading /e/ while locked, therefore i gave it an other try. Locking my phone again, wiping partition with twrp and... nothing. So i gave up and wanted to use my phone again so i unlocked it again.
Whats the problem?
Now I only can access twrp, but it wont show the menu. It just autostarts a script and there are no buttons. The script failes after ~10 seconds and the device crashes (error message below). It trys to boot up but fails, so it loads into recovery -> starts twrp -> runs this script -> crashes and so on. Now i cant do anything. It reboots all the time.
What can I do?
As said, twrp starts but with no menu. I have access to edl mode so i rewrote the recovery partition. This does not change anything. I can access my device with adb while it loads twrp. I have a time window about 10-15 seconds until it reboots. Fastboot does not work. (Not available or locked on Axon 7 mini?) If i try "adb reboot bootloader" my phone just reboots into android (well it did before flashing, now its stuck in the loop.) From searching this forum i think i should reformat the partitions, but i dont know how because i dont have access to the twrp menu. If you need more informations like a dump or something, tell me how to do it.
The Error:
As i dont know how i could dump it from my phone to my PC, i had to manual type the Error here...
$Begin
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
...done
Unable to mount storage
Successfully decrypted with default password.
Updating partition details...
...done
Unable to mount storage
Unable to mount '/data' (Invalid argument)
Full SELinux support is present.
wipe_data_via_recovery
Unable to mount /data/media/TWRP/.twrps
Running Recovery Commands
Failed to mount '/data' (Invalid argument)
Formatting Cache using make_ext4fs...
Done processing script file
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
$end
This runs fast until "Done processing script file". There it waits for ~3 Seconds. Then the last two lines show up and it crashes immediately.
Ok i found a solution - it worked for me but i dont know why. Its not intuitive but hey, its a workaround.
The problem was twrp couldnt startup anymore because the data partition was currupted (not confirmed, but i guess it was currupted). If you follow any guide, they tell you to go to wipe data inside of twrp and wipe (and reformat) the partition. This wont work in this case, because the corrupted partition causes twrp to crash. Its the script in the post above.
To fix this i used adb while twrp was starting up
Code:
adb shell recovery --wipe_data
This alone wouldnt solve the issue, but it will buy some time. After twrp loads again, you will see the main menu of twrp for a couple of seconds. The time you have on the menu is very limited (5 seconds max) before the script that will crash twrp starts executing. In this time window i managed to set twrp to write mode and initiated the wipe of /data. If you get this far, both scrips (wipe data and open recovery script) will execute, the screen will switch between both of them very fast. After a few seconds it will crash again, but the wipe data script could reformat the data partition properly. After this twrp will work like normal.
I don't know if this problem is specific to my device or model. I dont know if this is recreatable. Im glad i fixed it after five long days, im not willing to sacrifice my device again. I dont know if this is a twrp bug or what happened exactly. If anyone had a clue or needs more informations i will provide them. At least I found a workaround.
I've had my leg h870 rooted for a few years now and I have the bliss 12.4 ROM installed, I'm now trying to update to 12.8 via twrp but it won't allow me to mount /data.
I keep getting the error "could not mount /data and unable to find crypto footer"
I have formatted data in twrp and rebooted into recovery, this allowed me to access the /data partion but once I've booted into system and go back into recovery it won't allow me to mount /data again with the same error I've also tried factory reset via the system but this also won't work.
Does anybody know anything I can do to fix this issue?
twrp is broken, lg bridge worked for me (restock via update error fix)