Bricked by flashing wrong bootloader with Odin - Galaxy S 4 Q&A, Help & Troubleshooting

Bricked by flashing wrong bootloader with Odin - Galaxy S 4 Q&A, Help & Troubleshooting

it seems to be that I did it totaly wrong when flashing my phone. I get a bootup: "Firmware upgrade encountered an issue." bla...
What did happend:
I had a custom rom from here (Android 4.3): "PACman v4.3 Build 1 nightly 20130909".
My baseband version was (as far as I can remember): XXUBMF8
I wanted to update to 4.4.2 and at first I tried to update the bootloader and modem with Odin 3.09
For bootloader I used this:
BL_I9505XXUFNAD_481100_REV06_user_low_ship_MULTI_C ERT.tar.md5
For modem I used this:
I9505XXUFNC9_GSM_LTE_Modems.tar
The flash with Odin was succesfull and it restarted. Unfortunately I coulnd find any changes in the settings windows under Android. There was still the old version under baseband (I think XXUBMF8) which was strange for me becaue of the flash. I also checked the baseband with a baseband checker tool and it was the same old version. I trayed the flash process a several time and it was always succesull but with no change in the settings.
Anyway, I flashed than a custom rom:
I9505_Omega_v28_XXUFNC9_md5_7C1D639DBBE5C01FE689DA F3B82406AC.zip
FLash was succesfull and Android started.
Under settings, still old baseband: XXUBMF8.
So I decided to update this (this was my first big mistake)..
I used Odin and flashed again the bootloader
BL_I9505XXUFNAD_481100_REV06_user_low_ship_MULTI_C ERT.tar.md5
And from here I get the error message "Firmware upgrade encountered an issue."
Than - maybe my second big mistake - I tried to flash a stock rom to reset my phone. but I used an downgraded version...
[rom]i9505][xxubmf8][4.2.2] (24.06.2013)
I check also during the flashing process with odin "re-partition" and used the pit file and the 4 other files of this firmware. the flash process didnt go to the end, it interrupted. maybe because of the repartition, it goes more and more wrong...
I can still enter the download mode. But what should I try to flash now?
Is it possible to unbrick in my situation...?
And should I use the pit file "CSB_signed_Fusion3_EUR_0325_V2.pit" or should I leave it (just use the firmware?)
Should I use 1-file or 3-file version for odin?
I would appreciate your help a lot. I need the phone for work tomorrow. It is very important for me. Sorry to hustle and thank you very very much!

tried to flash I9505XXUFNAD. added pit file + 4 files (bl, ap, cp, csc) to odin. but I cant run the flash till the end.
without the pit file it doesnt want to start. i used "CSB_signed_Fusion3_EUR_0325_V2.pit" as pit file.
this is my error log...:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I9505XXUFNAD_481100_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> AP_I9505XXUFNAD_481100_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I9505XXUFNAD_481100_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CSC_OXX_I9505OXXFNA2_549230_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<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> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!

ok...
after hours of searching....: changed the usb slot.... than it managed to flash....

Related

[Q] problem connecting the phone

Hello, first time I sart a thread in this forum so I am a noob to say the least.
for some time ago I flashed my i9000 with odin worked well have had that set up for a while.
yesterday I thought i'd upgrade so and also flash back to stock on the phone.
followed a guide but an actident made the phone unplug the computer.
now I can only go to "download" mode and if I connect to the computer and continue the upgrade it seems to fail to set up the connection to the phone.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9000XXJVP_CL264642_REV03_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9000XXJVP_REV_00_CL1019177.tar.md5 is valid.
<OSM> GT-I9000-CSC-MULTI-OXAJVP.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
and nothing happens for houers. so how do i fix this? thank you in advance.

Phone Failed Odin MF3

Hey guys,
I think I bricked my phone beyond repair! I attempted to use Odin to Restore my phone to MF3 stock using the tar files that were generously provided. During the Odin restore it failed, not sure what exactly happened. I have used the same files to restore the same mf3 phone on two other occasions. Now my phone won't boot to recovery or Odin mode and just says that firmware update encountered an issue. Please select recovery mode in Kies and try again. The Kies recovery never works and I am left with a phone that is a brick. Will bestbuy be able to do anything through the smart tool? Or anything I can do?
Thanks!
Sent from my iPhone using Tapatalk

You could try here...
http://forum.xda-developers.com/showthread.php?t=2360859
or pull the battery, wait a minute, and put it back and see if you can use the correct key combination to get back into download mode and try ODIN again.

Thanks for the suggestions. But nothing seems to kick it out of this Kies recovery mode. I'm sending it back to samsung. Hopefully they can repair or ship me a new device as I am still under warranty.
Sent from my iPhone using Tapatalk

dtruong23 said:
Thanks for the suggestions. But nothing seems to kick it out of this Kies recovery mode. I'm sending it back to samsung. Hopefully they can repair or ship me a new device as I am still under warranty.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Same thing happened to me.. I worked for hours and finally about gave up, but tried flashing the I337 PIT file thru Odin in the Pit option.. It said failed but I pulled the battery and rebooted into recovery then restarted.. Google for the pit file.. It's on my computer but if you can't find it I can upload it for you.. Good luck!
Btw, the screen that says "firmware has encountered an issue" should still be able to be recognized in Odin..
I had to get on my computer anyway, so here is the file I used for the PIT box in Odin 3.09.. Hope it works for you!
https://www.dropbox.com/s/fptxnxsqevjhnt9/SGS-I337_16GB.pit

im having a simular problem. I keep getting this error when i try to use odin to restore back to stock.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl1.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

iammeHD said:
im having a simular problem. I keep getting this error when i try to use odin to restore back to stock.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl1.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Did you do the latest update to MK2?

nerdyblonde said:
Did you do the latest update to MK2?
Click to expand...
Click to collapse
Im not sure what that is, i just wiped my phone and now im stuck at a boot loading screen and i can get recovery/download, and i was told to use odin to flash back to stock

Possibly Soft-Bricked my Device, willing to try anything!

Basically my device is the Samsung Galaxy S7 Edge, obviously. SM-G935A. It is the AT&T version, and I believe I may have soft bricked it. I played with roots and never successfully rooted it before, but now it is most likely soft bricked. I turned off the device, turned it back on, and I got stuck on a frozen AT&T boot logo. I was able to get into Recovery Mode later on and I have factory reset it several times, but each time I do, it loads directly back into Recovery mode. I have tried several different versions of ODIN, and several different ROM's and Firmware's with each version of ODIN and I get errors every single time.
At this point, I'm willing to try anything, so if you suggest something to me, I will give it a shot because I just want my phone back.
Thanks in advance, I appreciate anything.

You need to start by flashing your original rom with odin, then follow tutorials on xda on methods to root your model.

Deano89 said:
You need to start by flashing your original rom with odin, then follow tutorials on xda on methods to root your model.
Click to expand...
Click to collapse
What exactly do you mean by my original rom? If you could provide a link I would really appreciate it.
EDIT: I found an original AT&T rom, and it would not flash correctly. The log is below.
<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> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone: SW REV CHECK FAIL : [aboot]Fused 4 > Binary 2 [1] eMMC write fail: aboot

Same issue here man, i been trying everything with no success. My phone keeps rebooting from the samsung logo. Nothing has been successfully flashed either.

If anyone has any firmware or ROM's or versions of ODIN you could suggest. Original firmware, stock ROM's, custom ROM's, unlocked ones, whatever, please post them and I will try them.

Try flashing all the ROM files apart from BL
Just AP, CP, CSC

*Detection* said:
Try flashing all the ROM files apart from BL
Just AP, CP, CSC
Click to expand...
Click to collapse
I believe I may have tried that last night, however, I didn't save the log. It got me a bit farther, I believe. I will try it again today and post the log this time.
Thanks for the response!

Download Samsung Kies 3 from here:
http://www.samsung.com/uk/support/usefulsoftware/KIES/
Then once you downloaded/installed kies you put your device in Download mode.
In Kies 3 go to the top menu bar and select Tools > Firmware upgrade and initialization.
It will prompt you to enter your device's model name and in the next window it will ask for your Serialnumber (which is on the back of your device (rip dbrand skin) )
After that a download will start in Kies 3 and now you just have to wait for it to download and install.
Good luck!

LennARTpas said:
Download Samsung Kies 3 from here:
http://www.samsung.com/uk/support/usefulsoftware/KIES/
Then once you downloaded/installed kies you put your device in Download mode.
In Kies 3 go to the top menu bar and select Tools > Firmware upgrade and initialization.
It will prompt you to enter your device's model name and in the next window it will ask for your Serialnumber (which is on the back of your device (rip dbrand skin) )
After that a download will start in Kies 3 and now you just have to wait for it to download and install.
Good luck!
Click to expand...
Click to collapse
Will give this a shot now that I know how to use Kies. I installed it last night while I was trying to fix it, and I thought it was just a different driver haha.

Pyroshox said:
Will give this a shot now that I know how to use Kies. I installed it last night while I was trying to fix it, and I thought it was just a different driver haha.
Click to expand...
Click to collapse
Let me know if you fixed the issue you're having!

Pyroshox said:
What exactly do you mean by my original rom? If you could provide a link I would really appreciate it.
EDIT: I found an original AT&T rom, and it would not flash correctly. The log is below.
<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> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone: SW REV CHECK FAIL : [aboot]Fused 4 > Binary 2 [1] eMMC write fail: aboot
Click to expand...
Click to collapse
Download the newest Odin version.
Make sure the re-partition mode is OFF.
Try again with the base firmware from Sammobile

@LennARTpas - I am trying this on a separate computer, but I am getting errors that my device is not supported and that the S/N is incorrect even though I have typed it in several times. Any assistance would be greatly appreciated.
@roba93 - I will be sure to try your method once I am back in the environment to do so.

Pyroshox said:
@LennARTpas - I am trying this on a separate computer, but I am getting errors that my device is not supported and that the S/N is incorrect even though I have typed it in several times. Any assistance would be greatly appreciated.
@roba93 - I will be sure to try your method once I am back in the environment to do so.
Click to expand...
Click to collapse
here!

@LennARTpas - I tried your method, however, the same issue occurred. I got several recurring errors telling me that my device was not recognized by Kies, and when I attempted to submit the S/N, it told me it was incorrect.
@roba93 - I tried your method as well, however, SamMobile does not offer firmware for SM-G935A, so I tried the unlocked version, SM-G935U, and it gave me this log below. If I did not use the correct firmware, if you could point me in the direction of which to use that would be greatly appreciated. I feel as though I'm coming off like a needy n00b, and I don't mean to in any way for future reference.
<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..
<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> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: @*Detection* - I tried your method where I didn't use the BL in ODIN, and I got this 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..
<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..
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Pyroshox said:
@LennARTpas - I tried your method, however, the same issue occurred. I got several recurring errors telling me that my device was not recognized by Kies, and when I attempted to submit the S/N, it told me it was incorrect.
@roba93 - I tried your method as well, however, SamMobile does not offer firmware for SM-G935A, so I tried the unlocked version, SM-G935U, and it gave me this log below. If I did not use the correct firmware, if you could point me in the direction of which to use that would be greatly appreciated. I feel as though I'm coming off like a needy n00b, and I don't mean to in any way for future reference.
<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..
<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> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: @*Detection* - I tried your method where I didn't use the BL in ODIN, and I got this 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..
<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..
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You said that you are using the G935A.
Please try the following firmware: http://downloadmirror.co/1Ksx/G935AUCS4API2.zip
Hope this helps

roba93 said:
You said that you are using the G935A.
Please try the following firmware: http://downloadmirror.co/1Ksx/G935AUCS4API2.zip
Hope this helps
Click to expand...
Click to collapse
I love you so much right now.
I tried this firmware on a separate computer, and didn't try it on my main PC because it wasn't necessary, however, it worked. It went through and flashed correctly, and my phone booted into recovery mode. I had to wipe the cache, and it began setting up the phone like normal.
THANK YOU SO MUCH!

Pyroshox said:
I love you so much right now.
I tried this firmware on a separate computer, and didn't try it on my main PC because it wasn't necessary, however, it worked. It went through and flashed correctly, and my phone booted into recovery mode. I had to wipe the cache, and it began setting up the phone like normal.
THANK YOU SO MUCH!
Click to expand...
Click to collapse
No problem mate
Glad it worked

roba93 said:
No problem mate
Glad it worked
Click to expand...
Click to collapse
Yay it unbricked my phone too!
it is hard to find a guide with all the phone versions/updates, just specific solutions. Well this one magically worked, thank you.
I have a sm-g935a (att) - It would bootloop, after several attempts to recover by flashing various files the phone would give all sorts of errors depending on the version flashed, stop at recovery mode and not go any further, although let me wipe it. hope this helps if you have a similar porblem

Unable to Unroot Verizon Samsung Galaxy S7

*****EDIT*****
I kept at it and decided to restart my computer. The attempt using PrinceComsy and VZW_G930VVRU2APE1 failed. However, using Odin 3.12.3 and G930VVRU4API3_G930VVZW4API3_VZW, I had success!!! I guess the old adage of always restart your computer paid off this time. Thanks.
*****END EDIT*****
Hello all,
I'm newer to this forum. I used the GUIDE: ROOT, install XPOSED, and UNROOT/returning to stock a Galaxy S7 or S7 Edge post (https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039) to root my Verizon Samsung Galaxy S7 in an attempt to recover lost photos and videos (the files just disappeared when the phone got full). I was able to root without issue, including following the recommended next steps and installing xposed. However, now that that adventure is done, I am attempting to unroot to the Verizon stock firmware, all attempts so far have failed.
The original Verizon stock for the S7 was 6.0.1. My first attempt to unroot was using the suggested firmware VZW_G930VVRU2APE1 using Odin3_v3.12_PrinceComsy. I loaded the proper AP, CP, and CSC files in Download mode (ID:COM was blue and showed as 0:[COM6]). After running this, it failed (see log results below). At this point, I was unable to boot the phone (nor could I shut it down) and got a system update failure error screen. I was able to get back to Downloading... and attemped to unroot to G930VVRU4API3_G930VVZW4API3_VZW using Oden 3.12.3. Same errors. I will admit, I attempted adding the BL file on a second try based on another site's recommendations. That failed, too. So now, I'm at a total loss as to what to do, and do not know how to fix this.
Does anyone have any ideas? Thanks much!
Unroot Using Odin 3.12 PrinceComsy to VZW_G930VVRU2APE1 (AP, CP, CSC)
<ID:0/006> 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..
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Unroot Using Odin 3.12.3 to G930VVRU4API3_G930VVZW4API3_VZW (AP, CP, CSC)
<ID:0/006> 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..
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Message on Phone Downloading Screen
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G930V
CURRENT BINARY: Samsung Official
SYSTEMSTATUS: Custom
FAP LOCK: ON
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B4(2, 1, 1, 1, 1) K1 S3
SECURE DOWNLOAD : ENABLE
SW REV CHECK FAIL : [system]Fused 3 > Binary 1
Running on Windows 7 64-bit

Did you do anything else differently after restarting your computer? I keep failing trying to unroot -- I've restarted multiple times but still no cigar

One question about your root, did you root when you had 6.0 or 7.0?

SM-T510 - Trying to recover the os

Hello,
I am a newbie but I have tried reading and researching. Got past a few of my questions but got stuck so looking for some suggestions.
I have a samsung galaxy tab a sm-t510 (2019??) i believe. Its about 2 to 3 years old so the 2019 version would match. Physically looking at the device its smt-510 and it says this on the oden download mode page as well. All i have access to, to verify this. OS is dead. Here is my issue. I got this tab for my nephew and it died. It was low on battery and he just left it for like a month. Since then he said it just stopped working and kept on restarting. Reading online it seems like the battery died to the point where the charging module cant load so it cant change and boot into the os. It just keeps restarting with the error "could not do normal boot invalid Kernel length". I cannot get into the recovery mode and can only get it into the download mode. Reading online says i should just reload the firmware which should fix the issue. So this is what i am trying to do. The region for this device is in canada. Next in the download mode it says secure boot enabled and oem lock on. I cant get into the os to turn these off. I cant find a way to disable these without getting into the OS. My goal is to get it working, custom rom or oem, dont really care. I know if i load an oem firmware these settings should not matter. I've downloaded a few different versions of the oem image (sammobile and using frija).
I keep getting Re-Partition operation failed. when trying to load the image. I have tried v9 which came with the tab and tried latest v11 using frija.
I can see it connect fine and all is good but it seems like i have the wrong image and this is why i keep getting the re-partition failed? I have tried this with Oden 3.09 which has a few check boxes and one is re-partition. its unchecked. Defaults (auto reboot and f. reset time) are only on. I have also tried it with Oden 3.13.3 with same options. Again my goal is to load anything on it to get it working. Any thoughts on options and what i can do to recover this? My theory is i have the wrong image and thats why the oem and secure download is giving me an error but not sure. Any help would be nice.
just to add. if i select the home csc file i get the there is no pit partition error.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_T510XXU2ASK5_CL17420370_QB27658722_REV02_user_low_ship.tar.md5 is valid.
<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> CSC_OMC_OXM_T510OXM2ASK5_CL17420370_QB27658722_REV02_user_low_ship.tar.md5 is valid.
<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> AP_T510XXU2ASK5_CL17420370_QB27658722_REV02_user_low_ship_meta_OS9.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<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> FAIL!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
Thanks,
Mike

Database Users

welcome