"dm-vertity failed - need to check DRK" after downgrading from cm13 successfully - Galaxy Note 4 Q&A, Help & Troubleshooting

"dm-vertity failed - need to check DRK" after downgrading from cm13 successfully
Hi this only happens after playing with the EFS Folder as it is needed when you want to dawngrade . i heard that that some tools like ultimatemultitool can fix the prob on s6 but any help on note 4? plz

dm-verity is a checksum on the system partition if any file is touched or deleted on the system partition
the checksum fails and recovery says dm-verity failed
it doesnt mean nothing just flash a full stock image or custom recovery
https://source.android.com/security/verifiedboot/

Related

How to root a S8 G950F Exynos with failed integrity verification without wipe ?

Dear all,
I tried since yesterday to root my S8 Exynos (G950F). My phone is crypted and when I try to root with magisk via TWRP, I have errors to access to datas. When the system boot, I have the error unable to restart your phone. the integrity verification has failed....
Then via TWRP and the shell, I made a copy of the userdata partition on my computer (the crypted partition), then I wiped my phone, I flashed the DM Verify Disabler and then Magisk via TWRP, until then, no problem, I was root but with an empty phone.
There, I uploaded my copy of userdata partition into my S8, I boot the system and always the same error of integrity verification failed...
Now, my phone works always good (I flash the stock ROM via ODIN) but I haven't yet the root.
Is there a way to root the S8 without lost the datas ? A kind of APK or something else ?
Kind regards,
Lau
lolo1410 said:
Dear all,
I tried since yesterday to root my S8 Exynos (G950F). My phone is crypted and when I try to root with magisk via TWRP, I have errors to access to datas. When the system boot, I have the error unable to restart your phone. the integrity verification has failed....
Then via TWRP and the shell, I made a copy of the userdata partition on my computer (the crypted partition), then I wiped my phone, I flashed the DM Verify Disabler and then Magisk via TWRP, until then, no problem, I was root but with an empty phone.
There, I uploaded my copy of userdata partition into my S8, I boot the system and always the same error of integrity verification failed...
Now, my phone works always good (I flash the stock ROM via ODIN) but I haven't yet the root.
Is there a way to root the S8 without lost the datas ? A kind of APK or something else ?
Kind regards,
Lau
Click to expand...
Click to collapse
You need to reflash twrp in odin and boot into recovery (TWRP) before the phone boots the system. Id uncheck auto reset in odin and when its done flashing twrp again boot right into it. From there you want to select to keep the system read only, and then flash the DM Verity Disabler. After thats done flashing, your phone should boot up normally without seeing the integrity failed message. Its important that you boot right into twrp (recovery) after odin flashes it, if not you need to reflash twrp in odin until you successfully get into recovery before it boots your system.
I just tried 2 times this procedure, when I flash the no-verity-opt-encrypt-5.1, I have several error messages like Failed to mount '/data' (Invalid argument) or Unable to recreate /data/media folder or Unable to mount storage and Unable to mount /data/media/TWRP/.twrps.
When I boot up the phone, I have the same error of integrity failed message and I have to flash a stock system and boot img
lolo1410 said:
I just tried 2 times this procedure, when I flash the no-verity-opt-encrypt-5.1, I have several error messages like Failed to mount '/data' (Invalid argument) or Unable to recreate /data/media folder or Unable to mount storage and Unable to mount /data/media/TWRP/.twrps.
When I boot up the phone, I have the same error of integrity failed message and I have to flash a stock system and boot img
Click to expand...
Click to collapse
You have to wipe data otherwise it won't boot, there's no way round this unfortunately
lolo1410 said:
I just tried 2 times this procedure, when I flash the no-verity-opt-encrypt-5.1, I have several error messages like Failed to mount '/data' (Invalid argument) or Unable to recreate /data/media folder or Unable to mount storage and Unable to mount /data/media/TWRP/.twrps.
When I boot up the phone, I have the same error of integrity failed message and I have to flash a stock system and boot img
Click to expand...
Click to collapse
Previous poster is correct. Wipe>Format data>yes> in twrp then you should be good to go.

[SOLVED] [Loop] Your device is corrupt it cannot be trusted and will not boot

Hello,
I have an issue with my brand new G6.
It is in a loop "Your device is corrupt it cannot be trusted and will not boot" , no more recovery available.
What i did:
I unlocked the bootloader and flashed Magisk via TWRP the device displayed that the partition was corrupt and need to be erased.
After that the device was in a loop to twrp, whatever the wipe or ... no system boot.
I read that i had to format the data partition so i adapted a what i found here to my available partitions
https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
the device is now in a constant loop.
Does someone can help me please ?
is there any way to recover it ? download mode ? how ?
Update : I succeed to boot into download mode but LGUP gives me an error while trying to flash
error 0x2000 ... ... cefs::initialize()
docizoc said:
Hello,
I have an issue with my brand new G6.
It is in a loop "Your device is corrupt it cannot be trusted and will not boot" , no more recovery available.
What i did:
I unlocked the bootloader and flashed Magisk via TWRP the device displayed that the partition was corrupt and need to be erased.
After that the device was in a loop to twrp, whatever the wipe or ... no system boot.
I read that i had to format the data partition so i adapted a what i found here to my available partitions
https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
the device is now in a constant loop.
Does someone can help me please ?
is there any way to recover it ? download mode ? how ?
Update : I succeed to boot into download mode but LGUP gives me an error while trying to flash
error 0x2000 ... ... cefs::initialize()
Click to expand...
Click to collapse
Can you boot to TWRP?
Did you make a backup and have access to it? Especially the EFS partition? If you do, restore the EFS partition.
If you can boot to TWRP, try the following:
- wipe everything (the option where you have to type 'yes').
- download lineageOS and flash it. If this is working fine, install whatever ROM you want to install.
no access to twrp anymore , no backup , only access to download mode now
is there a way to flash back twrp or stock recovery from download mode ? boot into fastboot ?
(i know... i have no excuses , but made that so many times without issues ...)
thank you in advance
Maybe you should go in download mode and flash stock Rom with LGUP.
LGUP gives me an error while trying to flash the rom error 0x2000 ... ... cefs::initialize()
Can you flash twrp through lgup or fastboot?
For those that could be in the same situation i finally succeed to flash with LGUP last version but without the 8894DLL
the error was probably coming from the dll.
Cheers and thanks all for the answers
docizoc said:
LGUP gives me an error while trying to flash the rom error 0x2000 ... ... cefs::initialize()
Click to expand...
Click to collapse
It's probably a problem with the DLL, try to extract it from the kdz and input it in Lgup folder (I don't remember where and I'm not home, check the main thread for that) and after that retry flashing
EDIT : well you were faster than my phone glad it worked for you.

[HUGE EFS PROBLEM] - Done full format - EFS is gone // SM-G950F (DBT)

Hey guys ,
I accidentally done an Full format via TWPR before i could make a Backup of the EFS folder...
Obviously i dont have an IMEI now and cant use Mobile services ...
I Tryed Flashing the newest stock rom again and got the error:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE:4 BINARY:3
so uhm ... that wont work at all
I saw some tutorials with an Combination Rom flash but i will still got the BL error and nothing happens..
Are there any ways to Recover my phone?
Could i use the EFS's files of my old A5 2016 SM-510F?
Hitaku said:
Hey guys ,
I accidentally done an Full format via TWPR before i could make a Backup of the EFS folder...
Obviously i dont have an IMEI now and cant use Mobile services ...
I Tryed Flashing the newest stock rom again and got the error:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE:4 BINARY:3
so uhm ... that wont work at all
I saw some tutorials with an Combination Rom flash but i will still got the BL error and nothing happens..
Are there any ways to Recover my phone?
Could i use the EFS's files of my old A5 2016 SM-510F?
Click to expand...
Click to collapse
Device 4 Binary 3 means you are flashing older firmware than what is currently on your phone. You will need to get latest firmware with bootloader 4.
Bootloader version number is the 5th number from the right of the firmware name. The same error will happen if you use combination firmware as well.
spawnlives said:
Device 4 Binary 3 means you are flashing older firmware than what is currently on your phone. You will need to get latest firmware with bootloader 4.
Bootloader version number is the 5th number from the right of the firmware name. The same error will happen if you use combination firmware as well.
Click to expand...
Click to collapse
Hey
so the
G950FXXU4CRI5/G950FOXM4CRI5/G950FXXU4CRI1/G950FXXU4CRI5 firmware should technically work?
Hitaku said:
Hey
so the
G950FXXU4CRI5/G950FOXM4CRI5/G950FXXU4CRI1/G950FXXU4CRI5 firmware should technically work?
Click to expand...
Click to collapse
Yes it should as it is the latest firmware available.
Hitaku said:
Hey guys ,
I accidentally done an Full format via TWPR before i could make a Backup of the EFS folder...
Obviously i dont have an IMEI now and cant use Mobile services ...
I Tryed Flashing the newest stock rom again and got the error:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE:4 BINARY:3
so uhm ... that wont work at all
I saw some tutorials with an Combination Rom flash but i will still got the BL error and nothing happens..
Are there any ways to Recover my phone?
Could i use the EFS's files of my old A5 2016 SM-510F?
Click to expand...
Click to collapse
Did you manage to fix the problem? I have an S7 with a deleted EFS partition and can't use mobile services either
sirs2k said:
Did you manage to fix the problem? I have an S7 with a deleted EFS partition and can't use mobile services either
Click to expand...
Click to collapse
Same.. i have an A520F/DS, deleted EFS, no mobile services and null imei..any ideas on how to solve this?
I have a problem sm-g950f- u12 saying fail to open recovery cause(no such fail or directory)#
#reboot recovery cause is unknown#
Support single-sku
File-based ota
E: failed to mount/efs: invalid argument
Supported API:3
E:failed to mount/efs invalid argument
E: unknown volume for path[/odm]
E: unknown volume for path [/vendor]
Dm-verity verification failed....
E:[libfs_mgr]is_dt_compatible please anyone to help me
I have a problem sm-g950f- u12 saying fail to open recovery cause(no such fail or directory)#
#reboot recovery cause is unknown#
Support single-sku
File-based ota
E: failed to mount/efs: invalid argument
Supported API:3
E:failed to mount/efs invalid argument
E: unknown volume for path[/odm]
E: unknown volume for path [/vendor]
Dm-verity verification failed....
E:[libfs_mgr]is_dt_compatible please anyone to help me

Galaxy S8 Stuck on "Powered by Android" Screen After Android 9 Update.

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

[Hard-breaked] S7 Edge SM-G9350 (G9350ZH Hong-Kong) Only download mode accessible

Hi everyone! Help! Need help! As titled, i have almost tried everything, frp lock is enabled i can't acces to recovery menu and i'm unable to flash TWRP recovery or boot into normal recovery, frp lock blocked everything, i can just access to download mode
Please, I need some help with my SM-G9350 Hong-Kong Galaxy S7 edge on Binary 4
I got custom binary TWRP recovery/boot blocked by frp lock when the device was working fine running custom rom, and then I flashed stock firmware via Odin and all was just fine and Odin succeed pass, but when installing system updates in recovery it was up to 32% then erasing and then it should boot up system, but it didn't it keeps rebooting to recovery with no options at all, just showing the android guy with no command below and then when I hard it to enter in recovery menu it shows a black screen with some lines that says couldn't open recovery cause unknown and no such file directory, and device is busy, and keep doing the same thing, I did same and flashed again with latest firmware but same thing happened, and then I tried to flash TWRP in order to flash a custom rom to boot up system, but Odin fails and says in download mode custom binary recovery blocked by frp lock, known that my device's bootloader is already unlocked and I flashed before this a whole of stuff, now, I can just access to download mode, otherwise I can't do anything else even no adb , there is no a combination file for the Hong-Kong variant G9350ZH, there is only for the Open-China variant G9350ZC which is not combatible with the device, even there are no adb enabled files, if someone has a solution for this, please kindly take care of this problem?
No menu in stock recovery, it's just saying:
#fait to open recovery_cause(No such file directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE=SKU
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
E:[libfs_mgr] Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
I'm having the same and exact problem as in this video with same brand device S7e https://youtu.be/l8-ccufk4Q0 the man could save the device by installing TWRP because frp was off. I can't do the same because I got frp on
I used to play with a whole Frp Remover Tools but nothing helped or worked, and also tried some cracked boxes but unfortunately they seem just like interfaces and didn't work as well
If I ended with frp lock turned successfully off then everything will be easy, installing TWRP then flashing through it no_verity_encryption will solve the issue and the device will boot the system successfully, I need to turn it off, if anyone has a solution please help!
TheDevelopper said:
Hi everyone! Help! Need help! As titled, i have almost tried everything, frp lock is enabled i can't acces to recovery menu and i'm unable to flash TWRP recovery or boot into normal recovery, frp lock blocked everything, i can just access to download mode
Please, I need some help with my SM-G9350 Hong-Kong Galaxy S7 edge on Binary 4
I got custom binary TWRP recovery/boot blocked by frp lock when the device was working fine running custom rom, and then I flashed stock firmware via Odin and all was just fine and Odin succeed pass, but when installing system updates in recovery it was up to 32% then erasing and then it should boot up system, but it didn't it keeps rebooting to recovery with no options at all, just showing the android guy with no command below and then when I hard it to enter in recovery menu it shows a black screen with some lines that says couldn't open recovery cause unknown and no such file directory, and device is busy, and keep doing the same thing, I did same and flashed again with latest firmware but same thing happened, and then I tried to flash TWRP in order to flash a custom rom to boot up system, but Odin fails and says in download mode custom binary recovery blocked by frp lock, known that my device's bootloader is already unlocked and I flashed before this a whole of stuff, now, I can just access to download mode, otherwise I can't do anything else even no adb , there is no a combination file for the Hong-Kong variant G9350ZH, there is only for the Open-China variant G9350ZC which is not combatible with the device, even there are no adb enabled files, if someone has a solution for this, please kindly take care of this problem?
No menu in stock recovery, it's just saying:
#fait to open recovery_cause(No such file directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE=SKU
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
E:[libfs_mgr] Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
Click to expand...
Click to collapse
This isn't good.... Unfortunately I can't help with this matter. I bricked my s7 and ended up exactly like this. I have not been able to recover it. So I gave up. Sorry to be the bearer of bad news.
What happens when you Odin your full firmware package?
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
This isn't good.... Unfortunately I can't help with this matter. I bricked my s7 and ended up exactly like this. I have not been able to recover it. So I gave up. Sorry to be the bearer of bad news.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Thank you man, yea, you're right cause we tried almost everything but unfortunately can't recover it too :/
klabit87 said:
[/HIDE]
This isn't good.... Unfortunately I can't help with this matter. I bricked my s7 and ended up exactly like this. I have not been able to recover it. So I gave up. Sorry to be the bearer of bad news.
What happens when you Odin your full firmware package?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Odin success passed the firmware's packages without problems, and it is the right one @klabit87, actually, there is a chance to recover the phone, I have found a video on YouTube having the same and exact problem as me with same brand device S7e, the man could save the device by installing TWRP because frp was off, I can't do the same because I got frp on https://youtu.be/l8-ccufk4Q0
TheDevelopper said:
Odin success passed the firmware's packages without problems, and it is the right one @klabit87, actually, there is a chance to recover the phone, I have found a video on YouTube having the same and exact problem as me with same brand device S7e, the man could save the device by installing TWRP because frp was off, I can't do the same because I got frp on https://youtu.be/l8-ccufk4Q0
Click to expand...
Click to collapse
I think there are ways around frp though... I could be wrong though.
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
I think there are ways around frp though... I could be wrong though.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
If only it can be turned off, I'll flash TWRP
TheDevelopper said:
If only it can be turned off, I'll flash TWRP
Click to expand...
Click to collapse
I wonder if you could use a custom kernel with dm-verity removed altogether. You could Odin it. No need for twrp. What firmware version is currently installed? I will compile it for you if you want to try it. Maybe try verity will get you to a point where you could remove frp while booted. Is your bootloader still unlocked? As in OEM unlock I mean.
Sent from my Pixel 2 XL using Tapatalk
q​
klabit87 said:
I wonder if you could use a custom kernel with dm-verity removed altogether. You could Odin it. No need for twrp. What firmware version is currently installed? I will compile it for you if you want to try it. Maybe try verity will get you to a point where you could remove frp while booted. Is your bootloader still unlocked? As in OEM unlock I mean.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
When tried to flash TWRP, it says custom binary recovery block by frp lock
And when tried to flash a custom boot that I took from a custom ROM and I Tared it, it says custom binary boot blocked by frp lock, I don't know if frp is related to OEM unlock or not and I don't know why it failed to Odin the boot that I took, the current firmware is CSC1 ..link for appropriated boot.img https://desktop.firmware.mobi/device:454/firmware:19931 if the device will read it as a custom one I don't think it will bypass it so, I would not disturb u if actually the phone will refuse it
But if crom service still off that means the bootloader is unlocked, once running for the first time on the device no need to use it anymore and the bootloader will be unlocked, but I don't know if OEM is enabled and it says in download mode secure download enabled
TheDevelopper said:
q​When tried to flash TWRP, it says custom binary recovery block by frp lock
And when tried to flash a custom boot that I took from a custom ROM and I Tared it, it says custom binary boot blocked by frp lock, I don't know if frp is related to OEM unlock or not and I don't know why it failed to Odin the boot that I took, the current firmware is CSC1 ..link for appropriated boot.img https://desktop.firmware.mobi/device:454/firmware:19931 if the device will read it as a custom one I don't think it will bypass it so, I would not disturb u if actually the phone will refuse it
But if crom service still off that means the bootloader is unlocked, once running for the first time on the device no need to use it anymore and the bootloader will be unlocked, but I don't know if OEM is enabled and it says in download mode secure download enabled
Click to expand...
Click to collapse
Ah ok. You're right it won't flash then. Sounding like a qcom CDMA tool might help. I've seen a couple that allow you to remove frp but I believe it requires entering qshusb mode. But it seems like options just get more and more slim now
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
Ah ok. You're right it won't flash then. Sounding like a qcom CDMA tool might help. I've seen a couple that allow you to remove frp but I believe it requires entering qshusb mode. But it seems like options just get more and more slim now
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yes, playing around a right tool can remove it, searching and testing ..
Edit: @klabit87, all the tools failed
I have same model and same problem. Did you find any solution?
hi, do you have any update? I have the same problem and the same model too
Do anyone still need help in fixing this issue?
I would like you to join me in this experiment to fix your device.
how we start it ?
bawsobb said:
how we start it ?
Click to expand...
Click to collapse
Please PM me then we will first try to fix it and then post a tutorial here on XDA.

Categories

Resources