I've successfully rooted some of my previous androids, and currently have a rooted LG tablet. Today I was trying to root my Galaxy S7 and I bricked it and couldn't figure out how to unbrick it. I was following this guide devs-lab .com/root-Samsung-galaxy-s7-s7-edge.html. Everything looked like it worked Odin said pass but my phone got stuck in a boot loop. I tried to root it with a tar.md5 from a different site but it failed. When I put it into recovery mode it showed a big circle said "Installing updates" and then it went to a black screen showing the droid with a red caution sign and said "No command". From there I was able to get into the recovery menu and I tried wiping the cache and that didn't work, I then tried the factory reset and that didn't work. I then downloaded the "Stock_DeOdexed_Debloated" ROM from here and tried to sideload it using adb but that failed saying "E:footer is wrong. E:Signature verification failed" I tried to install it from the SD card but got the same message. In the recovery menu it said "No Support SINGLE-SKU, Supported API:3, # MANUAL MODE #, -- Appling Multi-CSC..., Applied the CSC-code : TMB, Successfully applied multi-CSC., Successfully verify for dmverity hash tree". I downloaded a stock firmware zip file I found on a different site and flashed the files inside using Odin and got my phone back up and running. I can’t figure out how to attach files so I've included links to the stock firmware I used as well as the version of Odin I used.
Stock firmware - downloadmirror. co/Urs/G930TUVU4APK1_G930TTMB4APK1_TMB.zip?download_token=20ae1b122f8519d6cfc69c0ef013b3f4c6856d15149bdc46bc3bcfecfb91ee1f
Odin - dropbox. com/s/go43hspdcbg9rld/Odin3_v3.12.5.rar?dl=0
brick s7 edge
gilbojr said:
I've successfully rooted some of my previous androids, and currently have a rooted LG tablet. Today I was trying to root my Galaxy S7 and I bricked it and couldn't figure out how to unbrick it. I was following this guide devs-lab .com/root-Samsung-galaxy-s7-s7-edge.html. Everything looked like it worked Odin said pass but my phone got stuck in a boot loop. I tried to root it with a tar.md5 from a different site but it failed. When I put it into recovery mode it showed a big circle said "Installing updates" and then it went to a black screen showing the droid with a red caution sign and said "No command". From there I was able to get into the recovery menu and I tried wiping the cache and that didn't work, I then tried the factory reset and that didn't work. I then downloaded the "Stock_DeOdexed_Debloated" ROM from here and tried to sideload it using adb but that failed saying "E:footer is wrong. E:Signature verification failed" I tried to install it from the SD card but got the same message. In the recovery menu it said "No Support SINGLE-SKU, Supported API:3, # MANUAL MODE #, -- Appling Multi-CSC..., Applied the CSC-code : TMB, Successfully applied multi-CSC., Successfully verify for dmverity hash tree". I downloaded a stock firmware zip file I found on a different site and flashed the files inside using Odin and got my phone back up and running. I can’t figure out how to attach files so I've included links to the stock firmware I used as well as the version of Odin I used.
Stock firmware - downloadmirror. co/Urs/G930TUVU4APK1_G930TTMB4APK1_TMB.zip?download_token=20ae1b122f8519d6cfc69c0ef013b3f4c6856d15149bdc46bc3bcfecfb91ee1f
Odin - dropbox. com/s/go43hspdcbg9rld/Odin3_v3.12.5.rar?dl=0
Click to expand...
Click to collapse
i have the same problem on my s7 dge. i havent find the solution yet. im desperate mine is from tmobile
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 guys, i am trying to fix a bricked S8, i am able to boot into Download Mode and Recovery mode (wiped everything there).
I've already flashed Oreo and Pie Roms but the device wont boot.
When i boot into recovery mode i get this message:
Fail to open recovery_cause ( no such file or directory)
[...]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
dm-verity verification failed.
and stuff like "firmware info was not valid"...
Can anyone help? Don't want to root it at this moment, because the phone has warranty. If i can't fix it by myself i will send it to Samsung
Backstory:
Received the message "Custom binary blocked by FRP lock" when restarting my phone. I had a custom ROM installed so this was probably why, but I had flashed no-verity-opt-encrypt previously so I don't know why I randomly got this message.
Tried to flash the latest Android 8.0.0 stock firmware from sammobile, successfully flashed through Odin but when the phone boots it keeps looping into recovery, followed by "No command".
When I try to access the recovery settings by pressing power+up it comes with:
fail to open recovery_cause(No such file or directory)#
Reboot Recovery Cause is [UNKNOWN]# No Support SINGLE-SKU
Along with a bunch of lines saying failed to mount /system and dm-verity failed.
I've tried flashing many different stock ROMs but only the factory binary combination ROM is able to boot up. Therefore, I cannot turn off FRP lock. I am struggling to find out why, even though Odin successfully flashed the whole stock BL, AP, CP and CSC, the recovery cannot be opened.
Any ideas would be greatly appreciated.
Edit: Managed to fix it through a YouTube video by Mr.Lee
Try downgrading to nougat or marshmallow. That should remove FRP.
Sent from my SM-G935FD using Tapatalk
I've tried but I cannot find any marshmallow/nougat version which does not result in a SW REV CHECK FAIL error, my kernel only accepts Oreo or higher it seems.
Hello
I rooted my TAB 2 P5100 with "CF-Auto-Root-espresso10rf-espresso10rfxx-gtp5100.tar.md5" through Odin 3.0.7.
It all finished OK and As i Check through Root Checked it says that my device is Rooted and it still has the latest original Android version 4.2.2
As I go to install any possible ROM I can find through SDCARD I recieve the error displayed in the title.
E:signature verification failed
I read a bit around and I wast to add that I do not have the option to toggle off verification mode.
Any help PLS
Thank you
Ujku80
NVM, it was easier than what i thought.
Download TWRP.zip and place it on the SD card
install TWRP fropm Google APP
Open it and tell it to install the TWRP.zip into recovery.
shut down and start to recovery - which starts to TWRP
after that is very easy.