Hello guys.
My s8 sm-g950f was brought to me by my customer whom bought d phone, d customer told me, he mistakenly hard reset his device...Now the device is Requesting for Gmail, he said he had tried the email he think he sign in on d device. now device was now stuck in Activation screen...So i taught of bypass it by flashing combination file and stock rom... so i discovered d device was running lastest update BINARY 2 ...so i download COMBINATION FILE from Z3x server with my z3x box, i downloaded the combination file named(COMBINATION_FA70_G950FXXU2ARE1)
And i also downloaded the Stock Rom i needed from UPDATO named(G950FXXU2CRED)
Now after downloading the two files i needed, i flash the combination file as usual, d device boot and work fine with combination file, then i decided to flash my stock rom back to remove the FRP(how i flash the stock rom to remove d frp was == (i was flashing with z3x) Bl; i deselect some img file. Ap ;i select and flash Boot, recovery, system.. I didnt select Cp, but CSC(i use normal csc not home csc and i selected and flash only cache).
After doing of all this my device boot normal and told my data partition was corrupted , i should reset it, i reseted and i know d frp was still there and have not been removed
Then i started flashing combination and stock rom randomly trying to bypass the frp, trying different things, selecting and deselect when flashing combination and stock rom...all of a sudden was unable to flash anything, when i flash either stock rom/combination it fails instant in INITIALIZATION...
this is an image i took when trying to flash with Z3x lasted vs 33.2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i also tried using lastest Odin version but same error failing in INITIALIZATION...(i don have image for that, sorry)
Now the state of my device in Download mode
Now the state of my device is When i put it in download mode(note ;i can only boot to download only, i cant boot to recovery) and try to flash it either with Odin or Z3x box, it fails at INITIALIZATION... and device will start to reboot till battey drains
Here is a video of how it behaves
https://m.youtube.com/watch?v=maswhPWFnko
Guys i did some research and find out that Is OEM and RMM that is d cause why i cant flash anything... I believe Issue has given hard time working, i cant take off my eyes from it, it so challenging that why am asking for help cos is why pass my intellects...
Guys how do i Fix this Problem, any required information needed, am here to provide
Thanks friends for your Reply
sorry i posted d wrong video of how d device is acting...this is d right video
https://m.youtube.com/watch?v=7wO-UG_VzPM
Thanks Guys for your Reply
successnbd said:
sorry i posted d wrong video of how d device is acting...this is d right video
https://m.youtube.com/watch?v=7wO-UG_VzPM
Thanks Guys for your Reply
Click to expand...
Click to collapse
damn,
I have same problem with you.
keep failing on Odin even with the trick click start and 3 bottom at same time.
https://forum.xda-developers.com/galaxy-s8+/help/help-potential-softbrick-g955f-t3747425 read this carefully
Frp bypass fail
S8 SMg950f frp bypass
Successful flashed combination File
Problem in flashing stock rom
Odin log -home csc not work ing
<ID:0/015> Added!!
<ID:0/015> Removed!!
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin engine v(ID:3.1301)..
<ID:0/012> File analysis..
<ID:0/012> skip file list for home binary
<ID:0/012> param.bin
<ID:0/012> userdata.img
<ID:0/012> Home Binary Download
<ID:0/012> Total Binary size: 3800 M
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> NAND Write Start!!
<ID:0/012> SingleDownload.
<ID:0/012> sboot.bin
<ID:0/012> up_param.bin
<ID:0/012> cm.bin
<ID:0/012> boot.img
<ID:0/012> recovery.img
<ID:0/012> system.img
<ID:0/012> modem.bin
<ID:0/012> Transmission Complete..
<ID:0/012> Now Writing.. Please wait about 2 minutes
<ID:0/012> Receive Response from boot-loader
<ID:0/012> modem_debug.bin
<ID:0/012> Transmission Complete..
<ID:0/012> Now Writing.. Please wait about 2 minutes
<ID:0/012> Receive Response from boot-loader
<ID:0/012> cache.img
<ID:0/012> hidden.img
<ID:0/012> RQT_CLOSE !!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Try to use patched odin
Related
Sammobile released S7 Flat 930F oreo firmware to DOWNLOAD Pls see here
https://www.sammobile.com/2018/05/03/you-can-now-download-the-first-galaxy-s7-oreo-firmware/
The lattest G930FXXU2ERE8 BTU firmware download
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/BTU/download/G930FXXU2ERE8/219215/
G930FXXU2ERD5 - Galaxy S7 SM-G930F BTU United Kingdom firmware Download here
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/BTU/download/G930FXXU2ERD5/217727/
ATTENTION: You need the latest version of Odin3 3.13.1. PLS see attachent
Reason: Samsung implemented lz4 compression on partition images and older versions do not support that. Thanks to mentioning. @LGaljo
I just uploaded it in google drive
https://forum.xda-developers.com/showpost.php?p=76408523&postcount=1365
Will this work for s7 flat dual sim?
nikkilku26 said:
Will this work for s7 flat dual sim?
Click to expand...
Click to collapse
yes!
Thank you!
I can't flash it via Odin, i select all the files, it starts but my phone reboots in 1 second and nothing happens, here is my log:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin engine v(ID:3.1101)..
<ID:0/010> File analysis..
<ID:0/010> skip file list for home binary
<ID:0/010> sboot.bin.lz4
<ID:0/010> param.bin.lz4
<ID:0/010> cm.bin.lz4
<ID:0/010> boot.img.lz4
<ID:0/010> recovery.img.lz4
<ID:0/010> system.img.lz4
<ID:0/010> modem.bin.lz4
<ID:0/010> modem_debug.bin.lz4
<ID:0/010> cache.img.lz4
<ID:0/010> hidden.img.lz4
<ID:0/010> Home Binary Download
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> RQT_CLOSE !!
<ID:0/010> RES OK !!
<ID:0/010> Removed!!
<ID:0/010> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Added!!
alcides2 said:
I can't flash it via Odin, i select all the files, it starts but my phone reboots in 1 second and nothing happens, here is my log:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin engine v(ID:3.1101)..
<ID:0/010> File analysis..
<ID:0/010> skip file list for home binary
<ID:0/010> sboot.bin.lz4
<ID:0/010> param.bin.lz4
<ID:0/010> cm.bin.lz4
<ID:0/010> boot.img.lz4
<ID:0/010> recovery.img.lz4
<ID:0/010> system.img.lz4
<ID:0/010> modem.bin.lz4
<ID:0/010> modem_debug.bin.lz4
<ID:0/010> cache.img.lz4
<ID:0/010> hidden.img.lz4
<ID:0/010> Home Binary Download
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> RQT_CLOSE !!
<ID:0/010> RES OK !!
<ID:0/010> Removed!!
<ID:0/010> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Added!!
Click to expand...
Click to collapse
Make sure you're using the latest version of ODIN, which is 3.13.1 and updated for the Oreo 8.0 firmware
Dashkaa said:
Sammobile released S7 Flat 930F oreo firmware to DOWNLOAD Pls see here
https://www.sammobile.com/2018/05/03/you-can-now-download-the-first-galaxy-s7-oreo-firmware/
G930FXXU2ERD5 - Galaxy S7 SM-G930F BTU United Kingdom firmware Download here
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/BTU/download/G930FXXU2ERD5/217727/
Click to expand...
Click to collapse
Please mention that you need latest version of Odin3 3.13.1. Thanks
Reason: Samsung implemented lz4 compression on partition images and older versions do not support that.
The old SamFirm downloader (v. 0.3.6) is still working.
It's much faster than sammobile without premium account and you can even download as binary...
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
I have few stupid questions? Noob
1. Will I trigger knox after installing this?
2. Will I lose all my data ?
3. I'm on AUT csc? What happens when I switch to BTU csc ?
h4xx0rr said:
I have few stupid questions? Noob
1. Will I trigger knox after installing this?
2. Will I lose all my data ?
3. I'm on AUT csc? What happens when I switch to BTU csc ?
Click to expand...
Click to collapse
1. No, you won't, if you install an official ROM.
2. No, but I propose to make a clean install and wipe. (sava data before)
3. CSC is OXA, not BTU. OXA is an international CSC.
Athanatos81 said:
1. No, you won't, if you install an official ROM.
2. No, but I propose to make a clean install and wipe. (sava data before)
3. CSC is OXA, not BTU. OXA is an international CSC.
Click to expand...
Click to collapse
OXA is not a CSC, CSC is BTU but also a Multi-CSC so includes many other CSCs, if your phone was originally one of them, such as XEU, it will default to that CSC, otherwise it should flash BTU
h4xx0rr said:
I have few stupid questions? Noob
1. Will I trigger knox after installing this?
2. Will I lose all my data ?
3. I'm on AUT csc? What happens when I switch to BTU csc ?
Click to expand...
Click to collapse
1) No
2) No but make a backup of the content of the internal memory just in case anything goes south.
3) If AUT is not in the list of BTU (which is a MULTI-CSC) then you should flash using the BL+AP+CP+CSC (instead of HOME_CSC) and that will factory reset your phone. If AUT is included in the BTU csc list then use the HOME_CSC file instead.
Sent from my SM-G930F using Tapatalk
Before flashing, do we have to ACTIVATE PIN in "Secure startup" ???
Flashing with latest odin 3.13.1 I end up stuck on the S7 bootscreen (not even the bootloop). First boot gets into samsung recovery, second reboot just gets stuck on the flash screen.
Also, if I try this and want to return to Android 7, its it possible to downgrade?
Is this global version? i mean if this unlock one? I am from Israel if i am will install it, This will work fine?
forcedv said:
Before flashing, do we have to ACTIVATE PIN in "Secure startup" ???
Click to expand...
Click to collapse
I didn't, but I had PIN & Fingerprint set for lockscreen
Worked on my SM-G930F ZTO - Brazilian using Odin3 v3.13.1
Previous version:
G930FXXU1DQE5
Android 7.0
Odin log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> param.bin
<ID:0/004> modem_debug.bin
<ID:0/004> Home Binary Download
<ID:0/004> Total Binary size: 4065 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
Updating with Odin don't affected my files.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Has anyone in North America tried this firmware?
I am having the worst luck as of late- any firmware I have tried to flash since I reverted to vanilla N refused to flash. (vanilla AT&T BRA1 was successful). I am trying to either revert to my normal home ROM (T-M BRA1 or later) or (if possible) the UK Oreo. I am trying to find out why the spate of failures is happening.
Hence my questions.
1. Is this indeed for S7 Snapdragon (as opposed to Exnyos)?
2. If it is for Snapdragon, has anyone been successful?
3. Has there been a problem specifically with T-M N firmware as of late?
I've been having problems with my phone after the Oreo update. (freezing / bootloops / random restarts)
Already did a factory reset on my phone but the issue was not fixed so I've decided to flash my phone but I'm having problems.
Details
Phone - SM-G935FD - Non Rooted
Software: Odin3 v3.13.1 - Downloaded from https://dl.sammobile.com/Odin3-v3.13.1.zip
Only Auto Reboot and F. Reset Time are ticket - Pit tab not changed. Loaded BL AP CP and CSC/HOME_CSC from firmware below.
Firmware - GALAXY S7 edge / SM-G935FD - PDA G935FXXU2EREM - Downloaded from https://updato.com/firmware-archive-select-model?record=36A47F5A6E2711E89F15FA163EE8F90B
After several retries, ODIN still fails to flash my phone. It gets stuck at system.img
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> modem_debug.bin
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 4200 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hope you guys can help me out. Thanks!
What is the Phone model on the back of ur phone
SM-935what
Is your phone rooted?
Possibilities are that the firmware and your phone are non compatible also send a screenshot of your odin.
You might have the wrong version selected.
Usually if your getting bootloops it's best to flash 1 checkbox at a time.
Make sure the port doesn't say com 3.
Com4 or com7 is OK.
The boxes don't really matter except the boxes u are flashing like the ap cp bl and csc
If your phone is 935fd then it is also compatible with 935f firmware which is more updated latest version is ERG2. Dual sim functuality is the same.
pingufanpoy said:
What is the Phone model on the back of ur phone
SM-935what
Is your phone rooted?
Possibilities are that the firmware and your phone are non compatible also send a screenshot of your odin.
You might have the wrong version selected.
Usually if your getting bootloops it's best to flash 1 checkbox at a time.
Make sure the port doesn't say com 3.
Com4 or com7 is OK.
The boxes don't really matter except the boxes u are flashing like the ap cp bl and csc
If your phone is 935fd then it is also compatible with 935f firmware which is more updated latest version is ERG2. Dual sim functuality is the same.
Click to expand...
Click to collapse
Thanks, my phone is a SM-935FD stock before I tried all of this.
I'm using Com4. In the screenshots I'm trying to flash to older 7.0 firmware.
By one checkbox at a time you mean I can uncheck BL after success right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Would it be ok to flash to SM-G935F firmware even if my phone is carrier locked?
Thanks
dhysics said:
Thanks, my phone is a SM-935FD stock before I tried all of this.
I'm using Com4. In the screenshots I'm trying to flash to older 7.0 firmware.
By one checkbox at a time you mean I can uncheck BL after success right?
Would it be ok to flash to SM-G935F firmware even if my phone is carrier locked?
Thanks
Click to expand...
Click to collapse
You can flash oreo 935f firmware on a 935fd but your phone will still be locked to smart sim.
The only way to unlock your sim imei would be to pay the company around 150 usd on average usually most companies won't do it because of money and people terminating their contracts early.
You will still be able to call and text from your smart Sim.
Just flash the CSC named SMA after installing if you want the smart branding it's not necessary tho.
pingufanpoy said:
You can flash oreo 935f firmware on a 935fd but your phone will still be locked to smart sim.
The only way to unlock your sim imei would be to pay the company around 150 usd on average usually most companies won't do it because of money and people terminating their contracts early.
You will still be able to call and text from your smart Sim.
Just flash the CSC named SMA after installing if you want the smart branding it's not necessary tho.
Click to expand...
Click to collapse
Thanks, I'm downloading the 935f oreo version.
Specifically this one: https://updato.com/firmware-archive-select-model?record=489AC01E8C1E11E89F15FA163EE8F90B
Hopefully it works, will post back here later
Unfortunately it still failed. Anything else I can try?
https://forum.xda-developers.com/showpost.php?p=77167218&postcount=14
ajox said:
https://forum.xda-developers.com/showpost.php?p=77167218&postcount=14
Click to expand...
Click to collapse
Thanks! Tried it but mine fails at the AP part I think.
download lastOdin3_v3.13.1
Fixed this. It was a USB cable issue.
What did you have to do?
dhysics said:
Fixed this. It was a USB cable issue.
Click to expand...
Click to collapse
Hey
I have a similar issue. The process starts and then just freezes, always in the same spot. I haven't even gotten through the BL file yet. At this point I don't mind if I have to completely wipe the phone and start over, I just want it to boot again.
I've tried with 2 different cables, though neither is an "original" cable as that one broke ages ago. Any tips?
Code:
<ID:0/009> Added!!
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 5 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> sboot.bin
<ID:0/009> param.bin
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
dhysics said:
Fixed this. It was a USB cable issue.
Click to expand...
Click to collapse
Hi there
Do you know what cable you used? I am using a mixture of original Samsung cables but not sure if they are for the galaxy s7, probably S5 days.
A few days ago my S7 Edge was acting up and didn't want to launch some of my apps. I decided to reboot the phone. However, the phone got stuck at the black screen with the white Samsung writing/logo on it. After trying to force reboot it I dot an error stating that there was a problem with FRP. I googled and found a tutorial on using Odin3 together with files from Sammobile.
In the tutorial I found they only updated the AP and this worked on my device as well. However once again it got stuck in the boot, in the encoding stage. I then tried to update all the files BL, AP, CP and CSC. This however does not work. I first tried with the "New model" of downloading in parallel but now am trying to download one file at a time.
I put the device in download mode and start the BL stage. This starts off OK and I can see the bar moving on both the device and the laptop, but when it reaches param.bin it stops. After a while I get "Complete(Write) operation failed".
I have tried this multiple times, hoping that putting the device into download mode again might work, or using a different file version from Sammobile. I've also tried 2 different cables, none of which are original Samsung cables as that broke a long time ago.
Please can anyone help?
Log output
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 5 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> sboot.bin
<ID:0/009> param.bin
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wrong stock rom
Kerry87 said:
A few days ago my S7 Edge was acting up and didn't want to launch some of my apps. I decided to reboot the phone. However, the phone got stuck at the black screen with the white Samsung writing/logo on it. After trying to force reboot it I dot an error stating that there was a problem with FRP. I googled and found a tutorial on using Odin3 together with files from Sammobile.
In the tutorial I found they only updated the AP and this worked on my device as well. However once again it got stuck in the boot, in the encoding stage. I then tried to update all the files BL, AP, CP and CSC. This however does not work. I first tried with the "New model" of downloading in parallel but now am trying to download one file at a time.
I put the device in download mode and start the BL stage. This starts off OK and I can see the bar moving on both the device and the laptop, but when it reaches param.bin it stops. After a while I get "Complete(Write) operation failed".
I have tried this multiple times, hoping that putting the device into download mode again might work, or using a different file version from Sammobile. I've also tried 2 different cables, none of which are original Samsung cables as that broke a long time ago.
Please can anyone help?
Log output
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 5 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> sboot.bin
<ID:0/009> param.bin
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hello There!
I hope this helps even if its late
Firstly Download a Firmware here
To download the right firmware, you should check on the build number, A build number should look like this: G935FXXU1DPLT(the 9th digit here is 1), The 9th digit is the Bootloader Version. Download a firmware that has a 8 in the 9th digit on the build number.
Finally flash it using odin
(Quick tip: After Unzipping the firmware zip file, you will see 5 files (AP, BL, CP, CSC, HOME CSC) DONT CHOOSE CSC, CHOOSE HOME CSC, remove the .md5 at AP, BL CP, AND HOME CSC by renaming it, a window will say that the file type will be changed, just press ok. After renaming the 4 files, putting it on odin will just take you 2 secs)
I used to flash phones a lot but our carrier is VZW so our phones have been locked for years and my skills are rusty
The phone is my wife's. It's stock on:
Release date: 04/03/2020
Android™ Security Patch Level: December 2019
Software Version: R16NW.G930VVRSBCTC1
The phone is bootlooping (I've already replaced it with a Pixel 4a) and I'm hoping to rescue it to use as a backup phone.
I downloaded this from Updato:
GALAXY S7 / SM-G930V
8.0.0 Oreo(Android ) /
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
February 25, 19
I see this on the phone:
SW REV CHECK FAIL : [aboot] Fused 11 > Binary 9
[1]eMMC write fail : aboot
In Odin I see this in the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5238 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any advice - just trying to get the phone up and running stock
You're trying to flash firmware with Bootloader 9, but your current Bootloader is 11 (means you got last software upgrade and there's no chance to downgrade Bootloader)... This topic is discussed already several times. Wait for new exploit (if this someday will appear) for root for Bootloader 11
lim-popo said:
You're trying to flash firmware with Bootloader 9, but your current Bootloader is 11 (means you got last software upgrade and there's no chance to downgrade Bootloader)... This topic is discussed already several times. Wait for new exploit (if this someday will appear) for root for Bootloader 11
Click to expand...
Click to collapse
Hi - thanks for the reply - now I know what to read up on and that this phone is probably not going to see action again.
My hunch is that if it suddenly started doing this when nothing new has been installed for over a year that it's a hardware issue anyway.
dsteinschneider said:
Hi - thanks for the reply - now I know what to read up on and that this phone is probably not going to see action again.
My hunch is that if it suddenly started doing this when nothing new has been installed for over a year that it's a hardware issue anyway.
Click to expand...
Click to collapse
Then seems that your phone was arrived to you with latest firmware pre installed... But it's definitely an firmware issue, I have the same now in my hands , so I'm also waiting for the root.
P.S.
What's your issue??? I mean, why you want to downgrade???
Hi,
I know this has been asked a lot but I have looked at countless threads trying to rectify this issue.
I have an S7 Edge (SM-G935F) that at some point black screened itself. After numerous attempts at revival, I have managed to get it to at least display something. From what I'm guessing, something at some point has become corrupted and the phone is now soft-bricked. So what I have been attempting to do is flash stock firmware via odin.
Here is a screen showing it is soft bricked ->
https://imgur.com/a/GLUv8Il
Here is a screen showing its download mode stats ->
https://imgur.com/a/XXp2ut8
On the soft brick screen I have used the FRP hijacker tool to both "fix" softbrick as well as remove FRP. I don't think either were sucessful. However, the S7 did boot into the "Galaxy S7" splash screen and then to an "erasing" and an "installing update" screen. Both processes failed and boot loop with a message describing the failure ("dm-verity verification failed" and "fail to open recovery_cause"), but it seems like progress.
Erasing screen ->
https://imgur.com/a/AUX7ITi
Installing update screen ->
https://imgur.com/a/BNdMd6u
Fail screens ->
https://imgur.com/a/3DBV6lC
Also, the phone refuses to boot into the recovery menu, as if its not even there somehow. Instead, the phone boots into the "Galaxy S7" splash screen then the blue screens linked above. Sometimes it boots into the soft brick screen and sometimes into the splash screen. Its difficult to even get it into download mode as it takes a long time (hence the rubber bands to hold the buttons down) and I think the battery is toast.
I have been using Odin 3.14.4 (and 3.13.1) to try and flash stock firmware. What I have been doing is using Frija to download the latest firmware by entering the model number (SM-G935F) and then the country code. However, I do not know which one the phone is. I have done numerous (free) imei checks and one site stated that it was a United Kingdom/Ireland carrier (XEU) (it is a UK phone) but I have tried XEU, BTC, BTU, VIR and VOD and all firmwares fail to flash at the param.bin part. I have also got the PIT file from the XEU CSC_ which sucesssfully flashed, but it made no difference. I've even tried to flash the BL_ by itself to try and get the recovery menu but it still fails at param.bin. I have ruled out that I am using firmware with an older binary as the phone does not display the red text that it normally does when this is attempted. Something to note is that FRP is on, but I do not know if this makes a difference. I should also mention I have tried some firmware from Sammobile which havent worked either.
Here is a screenshot of the param.bin fail using the VIR firmware (after uninstalling the Samsung USB driver just to rule it out)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Odin log:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 4000 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> param.bin
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im completely stumped now and am in need of advice. I think I have a basic understadning of how Odin works but most of my knowledge has come from attempting to fix this S7. Does the carrier/region even need to match in order for the flash to be sucessful? Does flashing the PIT or BL_ bring back the recovery menu? What are the next steps to fix/flash this S7. Does it seem like there's actually a hardware fault?
I apologise if I dont respond immediately and for the wall of text (I have tried to be thorough). Any help is greatly appreciated, thanks.
I just wanted to add that trying to flash without attatching BL_ causes it to fail at boot.img
Odin log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 3958 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> boot.img
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am having same problem with you. I tried to flash 4-5 firmware but no way. have you found any solution?
Does it show any sign of charging? What happens if you try to flash only CP or CSC? If it consistently fails after a certain number of bytes was transferred, your device could have a broken RAM chip or some other logic board issue, perhaps the flash storage itself is failing.