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
Related
Hi, I need your help guys, this is the problem:
I have a G9287, in last G9287ZHU2BPE1 6.0.1, stock kernel, rooted with flashed BETA-SuperSU-v2.74 and with twrp-3.0.2-0-zenltezt.
Suddenly it started to behave weird after installing some quick boot programs from play store. So I tried to recover it with a TWRP nandroid backup. And it failed, it said after that:
EXTRACTTARFORK () Process ended with ERROR: 255
I tried doing twice with same results.
So I decided to install original firmware again with Odin. All the Odin process went OK, so it rebooted and started to "installing system update" it went for a while and count some percentage up to 32% and then some more "installing system update" and after a while it went twice to Samsung start screen, it did this bootloop twice and the it went to Samsung Recovery with this legend:
E: failed to mount /preload (Invalid argument)
Supported API: 3
I tried again with Odin and also with Smart Switch with same results.
I tried Samsung Recovery wipe data.
I also tried TWRP wipe, first full "advanced wipe" and after same results, "format data"
Then tried Odin again and same resuts. Incomplete "installing system update" with Odin and Smart Switch.
So I went to download mode and with Odin flashed twrp-3.0.2-0-zenltezt with success
and then flashed Audax_Plus_M_v6.0 with complete success again.The ROM opens perfectly as expected. But only shows one not working SIM signal.
My problem is that I can not stay in this custom ROM since it doesn't support dual sim as my version is. Also there is no custom ROM that I know for G9287 version.
So, because of this, I then went again to Smart Switch to try to intall last firmware version. And get same results, an incomplete system update with same legend in Samsung Recovery.
I have googled all the legends I have gotten, with no conclusive results.
So, I am asking for your advice. Thanks in advance.
Anyone with more knowledge and experience than me, I am a noob, I have keept trying , with same negative results. Audax installs and works perfectlly, samsung firmware still the same, Odin flashes perfectly and ends succesfully and then starts "installing system update" makes a count to 32%, says "erasing" and after some second with system update ,again, shows the dead android and an exclamation and then goes to samsung recovery showing:
Supported API: 3
# MANUAL MODE #
-- Appliying Multi-CSC...
Applied the CSC-code : BRI
Successfully applied multi-CSC.
And if I reboots same results again and again.
I'm now with TWRP 3.0.2-2, I have wiped and full format all partitions.
pmorales said:
And it failed, it said after that:
EXTRACTTARFORK () Process ended with ERROR: 255
Click to expand...
Click to collapse
Hey, this is ''no free storage in your phone'' failure I get this error many times while restoring, make sure you have more free space than back up size. I couldnt read your post completely, just in case if you restore old LP data etc, it may cause some issues.
Also have faced E: un/mount th?ng before, wipe all excluding internal» helped me in this case. Good luck.
Hello guys,
I need extremely technical help as no longer know what to do.
I have a Galaxy S7 Edge device, which installed the rom BobCat and everything went well until then.
Later I decided to install another rom to test KingRom that left me unsatisfied, because I thought it had some bugs. Had the TWRP 3.0.0 recovery and decided to upgrade to 3.0.2, everything went well.
At one point I do not remember when or how if was when install back, downgrade to TWRP3.0.0, I do not remember if it was via Odin or TWRP, it happens that the installation stopped halfway. Then unplug the device, restarted in recovery mode and got the following message "E: falied to mount EFS (Invalid Argumen)", I could not restart the device (Boot Loop, and stucked at Samsung Logo) except in Recovery Mode, which also made to stay without IMEI number and Serial Number.
I googled until I came to this tutorial:
http://forum.xda-developers.com/s7-e...ssues-t3379516
I followed all the steps explained, I back up EFS_backup and RADIO_bakcup partitions.
Installed FACTORY BINARY G935, everything went well. After restarted, already had the correct IMEI number but still did not present the S / N.
After all that, i tried to install Stock Firmware via Odin, from here started the problems that could not solve.
In the first attempt Odin stucked in "System" (also used the PIT file with the same CSC ... .i do not know if I was right using PIT?). Restarted the device forcibly, entered the stock Recovery, did a complete wipe and always get this message "E: falied to mount System (Invalid argument), I returned to install Factory Binary, then reboot in Recovery and the same message no longer appeared.
Again I try to install the Stock Firmware and Odin always stucks in System, or NAND writing, or Partition, etc. I've tried various Stock Firmware, with and without PIT files, always without success.
Only Factory Binary that successfully installs. The TWRP via Odin also but when device restarts to enter Recovery Mode always get the message at the top of the display:
"Recovery image signature check Fail"
"Reboot to avoid Warranty bit set."
1. Does the partitions are in good shape? how can I check it?
2- I did good or bad using PIT file?
3- Does the problem is running Windows XP through a Virtual Machine?
4 What else can I do?
In all actions used and am using a Macbook 4.1, OsX Lion 10.7.5, Odin 3.11 Windows XP Professional 32bit through Oracle VM VirtualBox 3.4.38
Device:
Galaxy S7 Edge (SM-G935F) CSC = SWC SwissCom
1st Original Firmware: (I guess was 1?) G935FXXS1APG5_G935FVFG1APF3_SWC
Need help Please
Thank you so very much!
Hey guys,
I tried to root my gf's S5 with CF-AutoRoot's package. I got this for the specific version which I double-checked
Included in the package was Odin and the image with an "installer".
Everything was fine, device detected in Odin, selected image in AP and let it rip... Except I got an error after it was in the process, under UDC start, can't remember exactly as I had restarted the device with the loading bar at like 30% of the way... it stated something dev_state
After I restarted, I got the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I would've thought it was going to be pretty straight forward and decided not to do a backup but I'm so getting killed if I'm going to lose the data!!!
Any insight? thanks
I tried to get Samsung Kies for the recovery but under the list of devices requiring emergency recovery it won't detect it...
I managed to retry the Odin flash with the same outcome.
The error message is unsupport dev_type if that makes any sense to someone
Well issue seems to have fixed itself by flashing latest TWRP... The Odin flash went smooth and phone booted normally...
must've been something off with the AutoRoot
It's a long story but I soft bricked my G928F.
I bought it off Gumtree in the U.K and it had an frp lock on it, the seller stated that she had wiped it off so would not take it back. I had a read around and it seemed that Wondershare Dr. Fone would take off the frp lock........it didn't, rather it messed up the stock recovery. When attempting to enter recovery I get the following message and am stuck in a bootloop:
No Support SINGLE - SKU
Supported API: 3
dm-verity error
failed code: 0x02
E: failed to mount /cache (invalid argument)
While Odin will recognise the phone Smart Switch will not so I am unable to use the emergency recovery procedure.
I have read similar posts where it implies Smart Switch is the last resort but in my case that doesn't seem to be an option
Can anyone suggest a way to recover the phone or do I throw it in the bin? Any help appreciated
meohmy said:
It's a long story but I soft bricked my G928F.
I bought it off Gumtree in the U.K and it had an frp lock on it, the seller stated that she had wiped it off so would not take it back. I had a read around and it seemed that Wondershare Dr. Fone would take off the frp lock........it didn't, rather it messed up the stock recovery. When attempting to enter recovery I get the following message and am stuck in a bootloop:
No Support SINGLE - SKU
Supported API: 3
dm-verity error
failed code: 0x02
E: failed to mount /cache (invalid argument)
While Odin will recognise the phone Smart Switch will not so I am unable to use the emergency recovery procedure.
I have read similar posts where it implies Smart Switch is the last resort but in my case that doesn't seem to be an option
Can anyone suggest a way to recover the phone or do I throw it in the bin? Any help appreciated
Click to expand...
Click to collapse
Flash this using odin :
https://drive.google.com/uc?id=1tg9hJOCquyfuyROYtgpxyVKNbuidzdL8&export=download
Then, you will be able to flash latest version normaly, and also your will remove frp lock.
Thanks for that, I will flash it when I get home and report back.
Didn't work for me, the combination file gave an 'md5 error! Binary is invalid' message when loading into Odin, while renaming to .tar the flash failed.
firmware update start
Single download
sboot bin
param.bin
FAIL
Thanks for your suggestion though.
I tried installing firmware G928FXXS5CRH1 (VOD) but it failed at hidden system image, I removed that file and created a .tar which flashed successfully but the phone rebooted
to recovery initially but still showed a dm-verity error. I deleted the cache and then factory reset which appeared to also complete successfully but the phone would not boot up.
I then tried flashing the hidden sys image on its own but that failed and the phone went to the Smart Switch error recovery page, Smart Switch will not recognise the phone so will not allow access to the emergency recovery facility.
Still trying though if anyone has any idea's.
Hi there,
Im in the same boat. It had the verity error too.
BUT:
For me it worked to flash the 4-part firmware of the G928FXXS5CRH1 via Odin then.
The device boots again, without the verity error
It had Android 5.1 before, when I could flash the COMBINATION ROM and use it just fine.
(but it was a Android 7 combination ROM) :/
After flashing Android 7 debranded (G928FXXS5CRH1) in 4-parts (BL, AP, CC and CSC file) the FRP lock is still there of course,
but the phone is booting again without the verity error.
COMBINATION ROM will no longer let me flash it, though.
https://forum.xda-developers.com/s6-edge-plus/help/g-928f-verity-0x02-modem-bin-fail-t3886122
The download I did via the tool "samfirm" use chk32 and decrypt on downloading !
"SM-G928F_1_20180828170540_5avji4munw_fac"
Thanks for the reply, I fixed it myself in the end. I spent 2 days over Xmas until I eventually tried the solution that you have suggested. I eventually found a 4 part software. AS to the FRP lock, be it good luck or persistence, I managed to get rid of that as well using Samsung FRP Tool.
meohmy said:
Thanks for the reply, I fixed it myself in the end. I spent 2 days over Xmas until I eventually tried the solution that you have suggested. I eventually found a 4 part software. AS to the FRP lock, be it good luck or persistence, I managed to get rid of that as well using Samsung FRP Tool.
Click to expand...
Click to collapse
Hell Friend, Not sure If you could get this message, If yes, Kindly help me., I am facing the same issue with my Samsung Galaxy Note 5 (N920G/I) but could not find 4 parts FRP unlock firmware. Do let me know If anyone finds one.
Thanks!
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.