Database Users

Samsung Galaxy A9 Software Update Faliure

I own a Samsung Galaxy A9
I tried to update the firmware from the original lollypop to (maybe) marshmallow
I failed to update using the software, so i updated using smart switch
It went wrong, the update failed.
Now the blue screen with "An error has occured while updating the device software. Use the emergency recvery function in the Smart Switch PC software" appears..
I tried the emergency recovery but it also failed
The only button combination that worked is the power button + volume down --> It restarted, but the same screen appears
I even tried refresing the software with Odin, but it failed.
The phone says "FRP is enabled, not allow download non-FRP aboot binary"
Odin doesn't work
The samsung customer service in singapore (my country) is not able to help. Would really appreciate it if somebody could help me with this.
-Michael

Are you able to get into bootloader ? If so, you can try using ADB to remove OEM Unlock.. There should be bootloader unlock instructions for Samsung in these forums..
Sent from my SM-A9000 using XDA-Developers mobile app

I take it you tried to update via odin originally.
If you give more details if what part of the flashing process failed we may be able to help.
Was it a particular partition that failed to flash.
A screenshot of the failed flashing process with odin would be helpful.
Also you may be able to remove the blue error screen by flashing the stock recovery with odin.
Extract it from the stock firmware, convert it to a tar archive then flash it with Odin.
Boot to recovery and wipe cache.
That itself may get you booting.
There is also Twrp available for your device which could do the same thing.

I had the same issue.. i fixed it yesterday.. what i did was.. go to developer options.. enable OEM unlock.. download CROM from galaxy apps store.. it gives a warning msg regarding unlocking the device.. that isnt an issue..just press ok.. and it will say ur device is unlocked.. and then try reflashing firmware from ODIN.. and then i did root my A9 and its working pretty nice since yesterday..
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
and also.. if u try to update to marshmallow.. u may get errors.. i assume thats because that is an update from CHINA..NOT from HONGKONG.. i suggest everyone to wait untill hongkong version of Marshmallow is released.. even i flashed marshmallow..had some error and my device was not booting and just booting into recovery with some error like drm something like that.. and then i flashed a hongkong lollipop 5.1.1 version and then my device booted..
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
regarding the FRP locking system. do one thing.. first back up everything.. go to backup and reset option.. do a factory reset.. it will wipe everything so do make sure u backup everything.. it will reboot the device into recovery.. do full factory reset.. reboot again.. finish.. i did this.. FRP LOCK is gone.. am happy
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------
do all the steps as i said.. Insha Allah all your problems and errors will be solved..
Sent from my SM-A9000 using XDA-Developers mobile app

Mikekaipas said:
I own a Samsung Galaxy A9
I tried to update the firmware from the original lollypop to (maybe) marshmallow
I failed to update using the software, so i updated using smart switch
It went wrong, the update failed.
Now the blue screen with "An error has occured while updating the device software. Use the emergency recvery function in the Smart Switch PC software" appears..
I tried the emergency recovery but it also failed
The only button combination that worked is the power button + volume down --> It restarted, but the same screen appears
I even tried refresing the software with Odin, but it failed.
The phone says "FRP is enabled, not allow download non-FRP aboot binary"
Odin doesn't work
The samsung customer service in singapore (my country) is not able to help. Would really appreciate it if somebody could help me with this.
-Michael
Click to expand...
Click to collapse
Pls help me, i bought samsung galaxy A9 SM-A9000 Hong Kong version in singapore. My phone got firmware update error, i try to flash all A9 firmware with odin but still got problem and showing volume size is too big 7372800 < 7979008 , odin: invalid ext4 image. I try to flash with china firmware also. But frp not allowed. Pls help me what should i do. my phone can do downloading mode only. i can't do recovery mode and i don't have back up. Any idea to help me, pls.

mriyaan said:
I had the same issue.. i fixed it yesterday.. what i did was.. go to developer options.. enable OEM unlock.. download CROM from galaxy apps store.. it gives a warning msg regarding unlocking the device.. that isnt an issue..just press ok.. and it will say ur device is unlocked.. and then try reflashing firmware from ODIN.. and then i did root my A9 and its working pretty nice since yesterday..
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
and also.. if u try to update to marshmallow.. u may get errors.. i assume thats because that is an update from CHINA..NOT from HONGKONG.. i suggest everyone to wait untill hongkong version of Marshmallow is released.. even i flashed marshmallow..had some error and my device was not booting and just booting into recovery with some error like drm something like that.. and then i flashed a hongkong lollipop 5.1.1 version and then my device booted..
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
regarding the FRP locking system. do one thing.. first back up everything.. go to backup and reset option.. do a factory reset.. it will wipe everything so do make sure u backup everything.. it will reboot the device into recovery.. do full factory reset.. reboot again.. finish.. i did this.. FRP LOCK is gone.. am happy
Sent from my SM-A9000 using XDA-Developers mobile app
---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------
do all the steps as i said.. Insha Allah all your problems and errors will be solved..
Sent from my SM-A9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have the exact same problem as michael's... The problem is that we cannot enter the ROM at all... It only stuck at either the blue screen, or the odin mode screen. So we cannot disable neither FRP or Oem unlock...
Well in my chase i think the Crom service is already unlocked, but still... When trying to flash with :
China marshmallow : odin process failed even from the beginning (aboot.mbn <-- bootloader)
Hongkong lolipop : odin process failed during system ext4, saying it's too large
---------- Post added at 05:31 AM ---------- Previous post was at 05:30 AM ----------
ashyx said:
I take it you tried to update via odin originally.
If you give more details if what part of the flashing process failed we may be able to help.
Was it a particular partition that failed to flash.
A screenshot of the failed flashing process with odin would be helpful.
Also you may be able to remove the blue error screen by flashing the stock recovery with odin.
Extract it from the stock firmware, convert it to a tar archive then flash it with Odin.
Boot to recovery and wipe cache.
That itself may get you booting.
There is also Twrp available for your device which could do the same thing.
Click to expand...
Click to collapse
When trying to flash with :
China marshmallow : odin process failed even from the beginning (aboot.mbn <-- bootloader)
Hongkong lolipop : odin process failed during system ext4, saying it's too large
Is the TWRP for A9 available? I cant find any.

and remember this.. DO NOT FLASH CHINA MARSHMALLOW AS OF NOW.. it creates a problem.. FLASH ONLY HONGKONG FIRMWARE using the latest odin..
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
y do u need twrp? just flash via odin and its done..
Sent from my SM-A9000 using XDA-Developers mobile app

If odin won't flash and the bootloader is complaining about frp lock.
Then the firmware isn't meant for that device.
If it fails at aboot then it's likely nothing got flashed.
To remove the firmware error warning it's usually enough to flash the stock recovery or twrp with odin.
The stock recovery image can be pulled from the stock firmware and converted to tar with 7-zip then flashed with odin.
Note: twrp wont flash while frp lock is active.

ashyx said:
If odin won't flash and the bootloader is complaining about frp lock.
Then the firmware isn't meant for that device.
If it fails at aboot then it's likely nothing got flashed.
To remove the firmware error warning it's usually enough to flash the stock recovery or twrp with odin.
The stock recovery image can be pulled from the stock firmware and converted to tar with 7-zip then flashed with odin.
Note: twrp wont flash while frp lock is active.
Click to expand...
Click to collapse
"The stock recovery image can be pulled from the stock firmware and converted to tar with 7-zip then flashed with odin."
Which file do you mean by stock recovery image, and how to flash it with odin. I mean like which file should be converted to tar and should i put it into AP slot and then start odin like usual? thanks

jmarcus.w said:
"The stock recovery image can be pulled from the stock firmware and converted to tar with 7-zip then flashed with odin."
Which file do you mean by stock recovery image, and how to flash it with odin. I mean like which file should be converted to tar and should i put it into AP slot and then start odin like usual? thanks
Click to expand...
Click to collapse
Open the md5 firmware archive with 7zip and pull out recovery.img.
Use 7-zip to create a tar archive then flash with odin in AP slot.

ashyx said:
Open the md5 firmware archive with 7zip and pull out recovery.img.
Use 7-zip to create a tar archive then flash with odin in AP slot.
Click to expand...
Click to collapse
First of all thanks for this..
I tried this and able to access the recovery screen..
But still flashing the stock ROM after wipe/factory reset fail.
I found several problems in the recovery screen:
There is "dm-verity verification failed" error
and there is problem about mounting to /system and formating /sbfs thing..
When I tried flashing.. the problem is also always on the same point.. On the system.img.ext4 it failed, saying volume is too large, ODIN : invalid ext4... <-- Always this failure
I dont understand any of this.

jmarcus.w said:
First of all thanks for this..
I tried this and able to access the recovery screen..
But still flashing the stock ROM after wipe/factory reset fail.
I found several problems in the recovery screen:
There is "dm-verity verification failed" error
and there is problem about mounting to /system and formating /sbfs thing..
When I tried flashing.. the problem is also always on the same point.. On the system.img.ext4 it failed, saying volume is too large, ODIN : invalid ext4... <-- Always this failure
I dont understand any of this.
Click to expand...
Click to collapse
As previously stated the firmware is not intended for your device this is why you are seeing these issues.

Hi,
I have removed the blue screen, i tried flashing the stockrom after wipe/factory reset failed. I found several problems in the recovery screen. There is "dm-verity verification failed" error and error during wiping, there is a problem about mounting to / system and formatting/ sbfsthing. i don't understand any of this jargon.
Hope i can get some help for this, please.
Thanks
Mikekaipas said:
I own a Samsung Galaxy A9
I tried to update the firmware from the original lollypop to (maybe) marshmallow
I failed to update using the software, so i updated using smart switch
It went wrong, the update failed.
Now the blue screen with "An error has occured while updating the device software. Use the emergency recvery function in the Smart Switch PC software" appears..
I tried the emergency recovery but it also failed
The only button combination that worked is the power button + volume down --> It restarted, but the same screen appears
I even tried refresing the software with Odin, but it failed.
The phone says "FRP is enabled, not allow download non-FRP aboot binary"
Odin doesn't work
The samsung customer service in singapore (my country) is not able to help. Would really appreciate it if somebody could help me with this.
-Michael
Click to expand...
Click to collapse

Mikekaipas said:
Hi,
I have removed the blue screen, i tried flashing the stockrom after wipe/factory reset failed. I found several problems in the recovery screen. There is "dm-verity verification failed" error and error during wiping, there is a problem about mounting to / system and formatting/ sbfsthing. i don't understand any of this jargon.
Hope i can get some help for this, please.
Thanks
Click to expand...
Click to collapse
Don't worry about /sbfs other Samsung devices get the same warning.
Dm-verity is usually due to a modified system partition or just the wrong firmware.
Wipe issue is likely because of frp lock.

Thanks Ashyx.
Right now when i try turning on my phone, my phone just keeps restarting and the typical welcome screen appears. Nothing further happens.
ashyx said:
Don't worry about /sbfs other Samsung devices get the same warning.
Dm-verity is usually due to a modified system partition or just the wrong firmware.
Wipe issue is likely because of frp lock.
Click to expand...
Click to collapse

Mikekaipas said:
Thanks Ashyx.
Right now when i try turning on my phone, my phone just keeps restarting and the typical welcome screen appears. Nothing further happens.
Click to expand...
Click to collapse
Thanks and my phone also got same issue with mikekaipas

Hi, so anyone out there with any suggestions to remedy the situation? Or will i just have to give up on my phone?

Mikekaipas said:
Hi, so anyone out there with any suggestions to remedy the situation? Or will i just have to give up on my phone?
Click to expand...
Click to collapse
i also already tired to try on my phone; should i buy new A9?

Hi all
I want to flash odin a9000 hong kong version, and I am afraid of this looking this thread
I am on latest hong kong rom 5.1.1., unlocked bootloade by crom , rooted, twrp installed...
So, do I need to afraid of this @steberg @ashyx and other advanced users
thanks

Man... Oh maaaan.....
I have also got this problem with SM-A9000.
via smart switch my firmware detected as china built (BPE2). but the emergency recovery always failed at 100%
then i try ODIN, with china firmware ( i try with the newest & even the oldest & i have tried with both full AP instalation & the single instalation BL, AP, CP, CSC) the result:
"FRP is enabled, not allow download non-FRP aboot binary"
with PIT & Re-partition also fail. only add result:
"FRP is enabled, ignore PIT download"
when i try with HK firmware (either newest & all other) it's better while the full instalation fail.
the single instalation made it for BL, CP & CSC and i got into the boot loop which show black screen
and SAMSUNG GALAXY A9(6) logo and i can access recovery.
But AP instalation always fail ( i have tried PIT also), the screen said
"FRP is enabled, ignore PIT download"
"Volume Size is too big 7372800 < 7979008"
"ODIN : Invalid id ext4 image"
my question? is it really wrong firmware? because the BL, CP & CSC can be installed except the AP because of the system.img.ext4.
because with the China Firmware,none can be installed.
also in my recovery there log:
"dm-verity verification failed
E: failed to mount / system (Invalid argument)"
i tried to install TWRP, but still fail,its said:
"FRP is enabled, not allow download non-FRP aboot binary"
and as last resort i even try to tick "NAND erase all" but i just got the same result as above either with China and HK with PIT, with singular or full installation...
i've been working on this phone for several days and now kinda got confused.
1. i dunno how to disable this FRP (my phone no longer able to boot, so the developer option is out of question) is it possible with odin?
2. or is it because E: failed to mount? but i even try Nand erase all yet still no result.
3. or wrong firmware? i tried it all China and HK with PIT & re-partition, still no result.
4. is there a way to wipe everything and erase this FRP thingi ? ( i have tried to wipe all from recovery too) :crying:

[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.

problems with the G570F help

well first i want to say hello, i will explain my problem how started i wipe efs from my phone via z3x box because I was trying to fix imei, baseband, and no service sim problems. I have an unknown and i'm failed the idea was stupid and i did a reboot and i faced some problems in frp has locked bootloader i think its text is red i downloaded firmware rom stock from sam mobile and did flash on odi, but I downloaded the last version and binary U2, this is the file name G570FXXS2CSH1_G570FOJV2CSI2_TUN then the phone turned on and entered me on the recovery mode and showed me " installing system update " and then the "Erasing" and then he restarted alone and it appeared after him "No Command" I pressed the volume up button and the button power so that I see what I'm wrong, I tried to find my combination binary u2 and i didn't find only binary u1 and i have frp lock ON so i can't install root or TWRP on my phone and also i could not to boot into the system so I searched on google and found a file named "SM-G570F U2 Android 8.0 FIX DRK - dm-verity Failed Frp ON RMM ON.tar"
I knew that this file would fix my problem is " E:[libfs_mgr] Couldn't create verity device!" I'm flash my phone and put this file in the place of BL and also put the AP file system which I think is 2 GB and when he succeeded in the flash process my phone did a restart and showed me the SAMSUNG logo and entered me to the system, but another problem appeared to me, that the touch does not work, I cannot press anything if I hold on the power button, and i'm see RESTART and SHUTDOWN appears to me, but I cannot even click on them. I thought that this problem is from the file that I flashed to the location of BL, perhaps, also I am unable to enter recovery mode unless I flash 4 files again but my question is there is another solution To fix my phone? I want it to come back :crying:
Question: did u download the firmware stock and the same model phone?
Answer: yes, i did
these errors are seen by me when i'm flash firmware stock and then enter me into recovery mode. alone:
BLOB 255 DM VERITY FAILED
In my recovery menu, these lines are shown:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API : 3
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
dm-verity verification failed...
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
WHAT SHOULD I DO?? TO GET BACK ON STOCK?

any admis's or moderator here change my topic to SAMSUNG J5 PRIME?, I did not see it

anyone? HELLO ?

liwahadri1 said:
anyone? HELLO ?
Click to expand...
Click to collapse
Try reflash stock, then TWRP if possible. Otherwise no hope, also stop spamming in your threads, no one will help you with this attitude. Try to maje the thread as short as possible cause no one will want to stay and read all this stuff.

NecromancerViper said:
Try reflash stock, then TWRP if possible. Otherwise no hope, also stop spamming in your threads, no one will help you with this attitude. Try to maje the thread as short as possible cause no one will want to stay and read all this stuff.
Click to expand...
Click to collapse
i have tried before and it will not work
also I did not spam because I saw the topic is dead

liwahadri1 said:
i have tried before and it will not work
also I did not spam because I saw the topic is dead
Click to expand...
Click to collapse
Then your phone is pretty much dead

NecromancerViper said:
Then your phone is pretty much dead
Click to expand...
Click to collapse
what about combination for binary u2?
btw if i flash only system.img on AP and BL file "SM-G570F U2 Android 8.0 FIX DRK - dm-verity Failed Frp ON RMM ON"
i can boot into android but touch not work my question is combination soon out for binary u2?

liwahadri1 said:
what about combination for binary u2?
btw if i flash only system.img on AP and BL file "SM-G570F U2 Android 8.0 FIX DRK - dm-verity Failed Frp ON RMM ON"
i can boot into android but touch not work my question is combination soon out for binary u2?
Click to expand...
Click to collapse
I dont own the phone so... I can't help you past this... sorry