looking to flash back to stock 8.0 Oreo How do I tell what region the phone is from?? I've found a couple but not sure which is the correct one to flash. pls help new to samsung.. I know the region has to do with a 3 digit code just not sure where to find it??
blake .l said:
looking to flash back to stock 8.0 Oreo How do I tell what region the phone is from?? I've found a couple but not sure which is the correct one to flash. pls help new to samsung.. I know the region has to do with a 3 digit code just not sure where to find it??
Click to expand...
Click to collapse
Hey, open your Dialer and enter *#1234#
Your CSC code follows right after your Model nr.
For me it's A750FN"OXM" where OXM refers to my CSC.
Fatal_Scythe said:
Hey, open your Dialer and enter *#1234#
Your CSC code follows right after your Model nr.
For me it's A750FN"OXM" where OXM refers to my CSC.
Click to expand...
Click to collapse
Unless im just looking wrong or missed it i cant find anything to match? here what mine shows when i type in the code you provided:
AP: A750GUBU2BSC7
CP: A750GNUBU2BSC7
CSC: A750GOWO2BSC7
Model: SM-A750G/DS
blake .l said:
Unless im just looking wrong or missed it i cant find anything to match? here what mine shows when i type in the code you provided:
AP: A750GUBU2BSC7
CP: A750GNUBU2BSC7
CSC: A750GOWO2BSC7
Model: SM-A750G/DS
Click to expand...
Click to collapse
Yours seems to be an Multi-CSC, which is "OWO"
I traced down my software that's installed on the phone right now and it matches 2 other software's I've found. The first one is Columbia (COO) and the second is Panama (TPA). So I'm wondering if I would be able to flash either one???
Fatal_Scythe said:
Yours seems to be an Multi-CSC, which is "OWO"
Click to expand...
Click to collapse
*traced down my software that's installed on the phone right now and it matches 2 other software's I've found. The first one is Columbia (COO) and the second is Panama (TPA). So I'm wondering if I would be able to flash either one???
Any ideas??
blake .l said:
Any ideas??
Click to expand...
Click to collapse
If possible, choose the one which comes closest to your Phone Carrier. If neither of them are, you'll probably have to try out both.
Fatal_Scythe said:
If possible, choose the one which comes closest to your Phone Carrier. If neither of them are, you'll probably have to try out both.
Click to expand...
Click to collapse
I figured the Panama (TPA) would be the one to go with. in the software service provider section it had (TPA) in several places. i tried flashing through Odin but it keeps failing, not sure what im doing wrong?? any ideas
blake .l said:
I figured the Panama (TPA) would be the one to go with. in the software service provider section it had (TPA) in several places. i tried flashing through Odin but it keeps failing, not sure what im doing wrong?? any ideas
Click to expand...
Click to collapse
Okay, what errors do you get?
Fatal_Scythe said:
Okay, what errors do you get?
Click to expand...
Click to collapse
<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/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5686 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> param.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
blake .l said:
<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/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5686 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> param.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hmm... Does your Phone as well display some sort of Error Message when the param.bin Error occurs?
For example "SW. REV. Check FAIL" ? If yes, then you'll most likely have to try another rom, if possible the most recent firmware.
Fatal_Scythe said:
Hmm... Does your Phone as well display some sort of Error Message when the param.bin Error occurs?
For example "SW. REV. Check FAIL" ? If yes, then you'll most likely have to try another rom, if possible the most recent firmware.
Click to expand...
Click to collapse
I've not really noticed as far as an error on the phone. I'll try again and check. I do have the current firmware on it right now Android 9 Pie, What i'm trying to do is downgrade back to 8.0 Oreo so I can Root with Magisk. The bootloader is ofcourse unlocked. just trying to get root to get rid of unwanted apps etc...
blake .l said:
I've not really noticed as far as an error on the phone. I'll try again and check. I do have the current firmware on it right now Android 9 Pie, What i'm trying to do is downgrade back to 8.0 Oreo so I can Root with Magisk. The bootloader is ofcourse unlocked. just trying to get root to get rid of unwanted apps etc...
Click to expand...
Click to collapse
Well here seems to be the Error, upgrading to Pie of course also upgrades the Bootloader / Binary, that's why a Downgrade can be pretty hard to achieve because it won't let you install older Firmwares, maybe that's why the param.bin error occured in first place.
What you can do is to unpack the 8.0 Firmware, delete the sboot.bin file, repack and flash again, maybe it'll work.
Fatal_Scythe said:
Well here seems to be the Error, upgrading to Pie of course also upgrades the Bootloader / Binary, that's why a Downgrade can be pretty hard to achieve because it won't let you install older Firmwares, maybe that's why the param.bin error occured in first place.
What you can do is to unpack the 8.0 Firmware, delete the sboot.bin file, repack and flash again, maybe it'll work.
Click to expand...
Click to collapse
Thanks for the info, i'll give it a try..
blake .l said:
Thanks for the info, i'll give it a try..
Click to expand...
Click to collapse
I keep getting an error with the file when i add it to odin, md5 error binary invalid. i've attached the file that has the sboot.bin you think if you can find the time try to delete sboot.bin and repack?? not sure if its something im doing or that it just isn't going to work.. by the way its a 4 part file AP, BL, CP, CSC im assuming that BL is the only file that has the sboot.bin in it?
blake .l said:
I keep getting an error with the file when i add it to odin, md5 error binary invalid. i've attached the file that has the sboot.bin you think if you can find the time try to delete sboot.bin and repack?? not sure if its something im doing or that it just isn't going to work.. by the way its a 4 part file AP, BL, CP, CSC im assuming that BL is the only file that has the sboot.bin in it?
Click to expand...
Click to collapse
If it's just the md5 checksum error, you can rename the ROM.tar.md5 file to ROM.tar, leaving the md5 out. It'll give you a pop-up saying the File eventually will be unusable but here you can just click on yes.
Yeah sure, I'll do and reupload your file when I'm done, should only take a few minutes. ^^
Alright here you go, I unpacked the file, kicked out the sboot file aswell removed the .md5 extension, and then repacked
Fatal_Scythe said:
Alright here you go, I unpacked the file, kicked out the sboot file aswell removed the .md5 extension, and then repacked
Click to expand...
Click to collapse
Thanks for the help, I tried the file and it fails at param.bin still. I get this error on the phone (Flash Fail/SW REV.CHECK FAIL! DEVICE:2 BINARY1) I'm beginning to wonder if its even possible to downgrade at all and if so its probably above my skill level. I dont know if it be possible to contact Samsung to get the revert file to revert back or not. i've seen the file to revert back for the A750GN online but not sure if it would work or not... Any thoughts or advice?
blake .l said:
Thanks for the help, I tried the file and it fails at param.bin still. I get this error on the phone (Flash Fail/SW REV.CHECK FAIL! DEVICE:2 BINARY1) I'm beginning to wonder if its even possible to downgrade at all and if so its probably above my skill level. I dont know if it be possible to contact Samsung to get the revert file to revert back or not. i've seen the file to revert back for the A750GN online but not sure if it would work or not... Any thoughts or advice?
Click to expand...
Click to collapse
Hmm.. Alright, this Error, like I already mentioned - means that the Device is simply preventing you from installing an older Firmware.
But yeah, actually, a Downgrade still should be possible, a while ago I used to experiment with this stuff, and I actually managed to downgrade my old S6 Edge from latest 7.0 Nougat to 6.0.1 Marshmallow (I also managed to even go back to 5.0 Lollipop xD) I will edit your provided BL File later when I get home, this time with both the sboot aswell as the param.bin removed, this should (hopefully) solve the Issue.
Related
I'm sorry if I'm not doing this right, its my first time posting here, but I need help.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything
You flashed the wrong model ROM to the wrong model S7 ?
Maybe that's why you bricked it
Benaiah1287 said:
I'm sorry if I'm not doing this right, its my first time posting here, but I need help.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything
Click to expand...
Click to collapse
What error is Odin giving you when you try to flash fw?
vegoja said:
What error is Odin giving you when you try to flash fw?
Click to expand...
Click to collapse
Thanks for responding
<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.1203)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> persist.img.ext4
<ID:0/005> Home Binary Download
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update 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)
Benaiah1287 said:
Thanks for responding
<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.1203)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> persist.img.ext4
<ID:0/005> Home Binary Download
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update 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)
Click to expand...
Click to collapse
Ok are flashing the latest 930v fw and what fw were you on when trying to flash the 930u fw
vegoja said:
Ok are flashing the latest 930v fw and what fw were you on when trying to flash the 930u fw
Click to expand...
Click to collapse
I'm not sure, I appreciate you helping me so much!
Benaiah1287 said:
I'm not sure, I appreciate you helping me so much!
Click to expand...
Click to collapse
Ok if your phone is saying anything like binary 3>1 when Odin fails that means you are using older firmware that won't flash to your upgraded bootloader. I'll upload the fw I have to mega if I can get my pc to cooperate and I'm happy to help if I'm able to i know the struggles of Odin problems
vegoja said:
Ok if your phone is saying anything like binary 3>1 when Odin fails that means you are using older firmware that won't flash to your upgraded bootloader. I'll upload the fw I have to mega if I can get my pc to cooperate and I'm happy to help if I'm able to i know the struggles of Odin problems
Click to expand...
Click to collapse
You are the best!
Just so I learn, may I ask: If the fw I'm trying to flash is the latest, how could it be older than the fw which was already on my phone?
Hope that made sense.
EDIT
Thank you so much! After a full day trying to figure this out I found this post http://forum.xda-developers.com/att-galaxy-s7/how-to/g930uueu4api3-firmware-download-t3481159 like five minutes ago. Those files worked!
14th most frustrating day of my life man.
Benaiah1287 said:
You are the best!
Just so I learn, may I ask: If the fw I'm trying to flash is the latest, how could it be older than the fw which was already on my phone?
Hope that made sense.
EDIT
Thank you so much! After a full day trying to figure this out I found this post http://forum.xda-developers.com/att-galaxy-s7/how-to/g930uueu4api3-firmware-download-t3481159 like five minutes ago. Those files worked!
14th most frustrating day of my life man.
Click to expand...
Click to collapse
Awesome I just now got the files uploaded been meaning to for awhile anyway so u helped me stop procrastinating
I rooted my S7 and it deactivated my cellphone service. I searched the internet for solution and there were absolutely none. I decided to flash it back to the stock firmware. Odin didn't work and I accidentally unplugged the phone and now it won't boot up. I can put it in download mode but it's not being detected by ADB. My computer does detect as a Samsung Device though. When I try to use the stock firmware with Odin it says : <ID:0/004> 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/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
When I try to use SmartSwitch it says Unsupported Device. I'm desperate just to get my phone to work again so any help is greatly appreciated!
Has anyone figured out a solution to this? Having the same issue.
Did you try with smartswitch on your pc emergency recovery you will need your serial key
Phantom162 said:
Did you try with smartswitch on your pc emergency recovery you will need your serial key
Click to expand...
Click to collapse
I also have the same problem, and I tried the smart switch method, however when entering my serial number I was told I had the wrong serial number. I double checked multiple times and I always input it correctly.
I dont have any idea for this when mine is soft bricked il always do this!!! Are you sure you enter the exact sn number mine sn number its on sticker on the box!!!
You can try stock firmware on updato
are you using a Windows computer?
lightstryk said:
Has anyone figured out a solution to this? Having the same issue.
Click to expand...
Click to collapse
The issue was that the stock firmware I was trying to flash to was out of date. I used the up to date firmware and my phone is now fine. I was freaked out for at least 2 days about my phone thought, I'm never trying to root it again.
Jetirk said:
The issue was that the stock firmware I was trying to flash to was out of date. I used the up to date firmware and my phone is now fine. I was freaked out for at least 2 days about my phone thought, I'm never trying to root it again.
Click to expand...
Click to collapse
That's what i said when i hard bricked my first phone , i will never even root my phone again!
And what did i do one week after i bought new device? I flashed ROM, don't be worried, bricking will always happen, it is the part of whole experience :angel: :laugh:
Hi all,
Been out of the rooting game for some time. Got my Sprint S8 the other day and decided I wanted to take the plunge. Things did not go so well using SamFail Cyborg pre-rooted ROM.
I am trying to flash back to stock firmware via Odin (G950USQU1AQJH from updato.com), but I receive the below Odin fail:
<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> Erase...
<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> abl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is AQJH a flashable stock firmware, or is it an OTA? Can anyone confirm what I should be flashing to recover my device, and a download link if possible? I read in a separate thread that true stock firmware ends in AQC9 - but I cannot find that fimrware version anywhere. TIA!
UPDATE: I'm a dope, I was not running Odin as admin, which is why I could not flash anything and everything. RUN ODIN AS ADMIN, FELLOW DOPES!!!!!
Let me know. Cross your fingers!
Sent from my SM-G955U1 using Tapatalk
Goddly said:
Let me know. Cross your fingers!
Sent from my SM-G955U1 using Tapatalk
Click to expand...
Click to collapse
Samfail failed as everything else has, fairly quickly. Log:
<ID:0/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Erase...
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> NON-HLOS.bin
<ID:0/007> abl.elf
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Onto the firmware suggested in the other thread. Looking pretty grim...
So if the SamPWND 4 firmware files do not work you do the following:
flash G955USQU2BQK5 (from Sammobile/updato/etc)
After if you wish you can try Oreo from firmware science but you need BQK5 in this case to Oreo (zip update)
TopShelf10 said:
Samfail failed as everything else has, fairly quickly. Log:
<ID:0/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Erase...
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> NON-HLOS.bin
<ID:0/007> abl.elf
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Onto the firmware suggested in the other thread. Looking pretty grim...
Click to expand...
Click to collapse
It's failing at Boot...
I'm pretty sure flashing the AQK2 will flash. You'll have a working ROM. At least.
Sent from my SM-G955U1 using Tapatalk
He needs Sprint version.....
Goddly said:
He needs Sprint version.....
Click to expand...
Click to collapse
I thought the non carrier ones handle all, anyway the spirit version would be even a better bet indeed
rudimenta said:
I thought the non carrier ones handle all, anyway the spirit version would be even a better bet indeed
Click to expand...
Click to collapse
With the issues he's having.... Lol I'd try Sprints version...
Sent from my SM-G955U1 using Tapatalk
Goddly said:
With the issues he's having.... Lol I'd try Sprints version...
Sent from my SM-G955U1 using Tapatalk
Click to expand...
Click to collapse
Ok, all downloaded. And I should use regular Odin for this, right?
TopShelf10 said:
Ok, all downloaded. And I should use regular Odin for this, right?
Click to expand...
Click to collapse
Also, which settings should I check off in odin?
Ok so I flashed AQK2 via regular Odin (it did not come with a userdata file). I checked auto-reboot, freset time, nanderase, and bootloader update. It failed very quickly, citing error "FAIL! Model dismatch fail". Log:
<ID:0/007> 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/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Erase...
<ID:0/007> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
TopShelf10 said:
Also, which settings should I check off in odin?
Click to expand...
Click to collapse
Regular settings, regular odin should work
rudimenta said:
Regular settings, regular odin should work
Click to expand...
Click to collapse
No-go, failed very quickly "model dismatch fail", see my above comment for log.
what phone you have, seems like you are flashing the wrong firmware. You have a galaxy s8plus right?
TopShelf10 said:
No-go, failed very quickly "model dismatch fail", see my above comment for log.
Click to expand...
Click to collapse
Ok.
Sent from my SM-G955U1 using Tapatalk
rudimenta said:
what phone you have, seems like you are flashing the wrong firmware. You have a galaxy s8plus right?
Click to expand...
Click to collapse
Sprint US S8 G950U (snap)
TopShelf10 said:
No-go, failed very quickly "model dismatch fail", see my above comment for log.
Click to expand...
Click to collapse
Use the modded Odin
I assume your right clicking, and running Odin as admin right?
After you extract the image (if you have to) remove the .md5 from the end.
Sent from my SM-G955U1 using Tapatalk
TopShelf10 said:
Sprint US S8 G950U (snap)
Click to expand...
Click to collapse
Make sure your firmware starts with G950 and not G955 in that case!
If thats correct try the modded odin like above post, if that doesn't work try this firmware G950USQU2BQK5 (unknown version) from sammobile firmware section and use the regular odin, just unpack and don't change any thing just load.
Goddly said:
Use the modded Odin
I assume your right clicking, and running Odin as admin right?
After you extract the image (if you have to) remove the .md5 from the end.
Sent from my SM-G955U1 using Tapatalk
Click to expand...
Click to collapse
WOOOOOOOOO!!!!! IT......IS.............ALIIIIIIIIIVE! Was not running as admin, and not removing .MD5 (like I said, been out of the rooting game for a while running Blackberry)
Not in the clear yet though...it will boot to the welcome/start screen and then immediately power down on its own to display the battery charging display with no percentage or animation. This is great progress though!! I can reboot into recovery, and did perform a factory reset, however that did not help.
TopShelf10 said:
WOOOOOOOOO!!!!! IT......IS.............ALIIIIIIIIIVE! Was not running as admin, and not removing .MD5 (like I said, been out of the rooting game for a while running Blackberry)
Not in the clear yet though...it will boot to the welcome/start screen and then immediately power down on its own to display the battery charging display with no percentage or animation. This is great progress though!! I can reboot into recovery, and did perform a factory reset, however that did not help.
Click to expand...
Click to collapse
Lol. Well... You just screwed yourself into a new boot loader... [emoji23]
ALWAYS ALWAYS RUN AS ADMIN!
I'll bet you anything you could have flashed the Rom had you ran Odin in admin.... smh...
Sent from my SM-G955U1 using Tapatalk
---------- Post added at 10:49 PM ---------- Previous post was at 10:45 PM ----------
TopShelf10 said:
WOOOOOOOOO!!!!! IT......IS.............ALIIIIIIIIIVE! Was not running as admin, and not removing .MD5 (like I said, been out of the rooting game for a while running Blackberry)
Not in the clear yet though...it will boot to the welcome/start screen and then immediately power down on its own to display the battery charging display with no percentage or animation. This is great progress though!! I can reboot into recovery, and did perform a factory reset, however that did not help.
Click to expand...
Click to collapse
Try reflashing using regular Odin...
RUN AS ADMIN!
Man, I wish we would have waited to flash a U2 BL.
That should have been the ABSOLUTE LAST RESORT.
I would have pointed out Admin rights at some point. Lol
Sent from my SM-G955U1 using Tapatalk
I have this gear s2 stuck in download mode and when I try to flash the firmware on it with Odin (I have already soldered the USB cable on the pins), I get "Re-Partition operation failed" what I can do?
Huh
Kirito821 said:
I have this gear s2 stuck in download mode and when I try to flash the firmware on it with Odin (I have already soldered the USB cable on the pins), I get "Re-Partition operation failed" what I can do?
Click to expand...
Click to collapse
What pins. I got tthe same problem as you m8
notupus said:
What pins. I got tthe same problem as you m8
Click to expand...
Click to collapse
The pins on the motherboard
https://i2.wp.com/electrovo.co.uk/w...msung_s2.jpg?fit=991,707&ssl=1&resize=350,200
Ok
So how did you connect the pins? I cn try on mine to see what works.
notupus said:
So how did you connect the pins? I cn try on mine to see what works.
Click to expand...
Click to collapse
USB cable with the end cutted off and after stripping the wires (usually the colors of the wires are Black=GND, Red=VCC, White=RX or Data + and Green=TX or Data -), I putted some solder on the wires (not too much) and then soldered them on the pins following the same color as the picture that I sent earlier
If re-partition blbla... then something is wrong with PIT (partition.pit)...
A.
You have SM-R720X... Live Demo Unit
Check Back Cover/Rear Case...
B.
You have wrong Firmware on device... so wrong PIT
You can dump PIT from device...
C.
You use wrong Firmware...
So which Firmware you have tried?
Filename and/or Link?
D.
You could flash without PIT... so without CSC for tests...
Combination Firmware have PIT insdie tooo...
So again question...
Filename and/or Link to identify what you are trying...
Best Regards
adfree said:
If re-partition blbla... then something is wrong with PIT (partition.pit)...
A.
You have SM-R720X... Live Demo Unit
Check Back Cover/Rear Case...
B.
You have wrong Firmware on device... so wrong PIT
You can dump PIT from device...
C.
You use wrong Firmware...
So which Firmware you have tried?
Filename and/or Link?
D.
You could flash without PIT... so without CSC for tests...
Combination Firmware have PIT insdie tooo...
So again question...
Filename and/or Link to identify what you are trying...
Best Regards
Click to expand...
Click to collapse
A.
Mine is only SM-R720 without the X at the end
B.
I don't remember what firmware is on device
How can I dump PIT?
C.
I tried R720XXU2BPA4/R720OXA2BPA4 and R720XXU2FRC1/R720OXX2FRC1
Both firmware: https://mega.nz/#F!6MNFkIBA!4e-4_3EFb8aaw20KV01kaw!DQ9iACiS (from this thread https://forum.xda-developers.com/gear-s2/general/gear-s2-r720-frimware-collection-t3857938)
D.
Same error even without CSC
In Odin you see something like GET PIT or SET PIT...
SET PIT means writing...
GET PIT means using PIT from device without writing...
Somewhere is Thread where users wrote about dead eMMC... maybe also in worst case scenario...
Dump PIT...
A.
As Tool I know only cr. Z3X Samsung Tool...
B.
You could sniff USB via Tools... during Odin use...
C.
If Download wireless is alive...
You can sniff via few Commands...
Ehm... At the moment limited time... to search Links for you...
Is this your SM-R720 ?
And you saw it alive?
Or you have this only seen in half dead condition?
Oh, btw... did you tried Combination Firmware?
D.
https://forum.xda-developers.com/gear-s2/general/r720-r732xxu2eqj2-r720xxu2aoj2-firmware-t3760719
Collection of Combination Firmwares...
E.
If next time Odin attempt...
Copy and Paste Odin output... is only text... or make Screenshot...
Best Regards
adfree said:
In Odin you see something like GET PIT or SET PIT...
SET PIT means writing...
GET PIT means using PIT from device without writing...
Somewhere is Thread where users wrote about dead eMMC... maybe also in worst case scenario...
Dump PIT...
A.
As Tool I know only cr. Z3X Samsung Tool...
B.
You could sniff USB via Tools... during Odin use...
C.
If Download wireless is alive...
You can sniff via few Commands...
Ehm... At the moment limited time... to search Links for you...
Is this your SM-R720 ?
And you saw it alive?
Or you have this only seen in half dead condition?
Oh, btw... did you tried Combination Firmware?
D.
https://forum.xda-developers.com/gear-s2/general/r720-r732xxu2eqj2-r720xxu2aoj2-firmware-t3760719
Collection of Combination Firmwares...
E.
If next time Odin attempt...
Copy and Paste Odin output... is only text... or make Screenshot...
Best Regards
Click to expand...
Click to collapse
I can't access Wireless Download because when I try to go in reboot menu the screen glitch and then boot on Download Mode
I only have seen this in half dead condition
Bought it some weeks ago in the hope to repair it
I tried the Combination Firmware but fails to install
Log from Odin:
<ID:0/004> 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..
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 908 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT:
I retried with only BL and AP (R720XXU2BPA4), this time says that there is no PIT partition
Log from Odin:
<ID:0/004> Added!!
<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> 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/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1214 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
https://forum.xda-developers.com/gear-s2/general/fail-to-hard-softreset-t3746359
https://forum.xda-developers.com/gear-s2/help/gear-s2-wont-perform-factory-reset-t3737448
Here you can find...
Some """write protection""" hints... eMMC...
No idea if Hardware or Software related...
If you have in Reboot menu...
Upload
You could try to use RDX Tool:
https://forum.xda-developers.com/showpost.php?p=72110199&postcount=45
Please try Combination Firmware... this is Service Factory stuff... maybe it helps...
Next attempt is to force Odin... to use PIT...
Which Odin Version you use?
Best Regards
adfree said:
https://forum.xda-developers.com/gear-s2/general/fail-to-hard-softreset-t3746359
https://forum.xda-developers.com/gear-s2/help/gear-s2-wont-perform-factory-reset-t3737448
Here you can find...
Some """write protection""" hints... eMMC...
No idea if Hardware or Software related...
If you have in Reboot menu...
Upload
You could try to use RDX Tool:
https://forum.xda-developers.com/showpost.php?p=72110199&postcount=45
Please try Combination Firmware... this is Service Factory stuff... maybe it helps...
Next attempt is to force Odin... to use PIT...
Which Odin Version you use?
Best Regards
Click to expand...
Click to collapse
Tried flashing Combination Firmware with Odin 3.12.3 and Odin 3.13.1 but nothing, it always fails
For outdated SM-R720/SM-R732 no need of newest Odin...
https://forum.xda-developers.com/showpost.php?p=72049726&postcount=100
Try to find Tutorial to set PIT manually...
RE-PARTITION
PIT you can take from CSC or inside Combination Firmware...
Best Regards
Edit 1.
My fault...
https://forum.xda-developers.com/showpost.php?p=72098729&postcount=114
Seems I have successfully used Odin 3.12.3
adfree said:
For outdated SM-R720/SM-R732 no need of newest Odin...
https://forum.xda-developers.com/showpost.php?p=72049726&postcount=100
Try to find Tutorial to set PIT manually...
RE-PARTITION
PIT you can take from CSC or inside Combination Firmware...
Best Regards
Edit 1.
My fault...
https://forum.xda-developers.com/showpost.php?p=72098729&postcount=114
Seems I have successfully used Odin 3.12.3
Click to expand...
Click to collapse
Tried with PIT set manually but it fails both Combination Firmware and R720XXU2PBA4
Log from R720XXU2PBA4:
<ID:0/004> 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/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Log from Combination Firmware(R720XXU2AOJ2):
<ID:0/004> 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..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Kirito821 said:
Tried flashing Combination Firmware with Odin 3.12.3 and Odin 3.13.1 but nothing, it always fails
Click to expand...
Click to collapse
If you want I can send you my motherboard for you to try in. So you can troubleshoot to see if it is your mobo or something else. I'll send you a stripped wire too so you do not have to use your own.
When I was trying flashing again, the watch fallen from the desk and for instinct I grabbed the cable and the pad for GND and RX broke up
Thank you for your time and help in troubleshooting adfree :good:
And thanks notupus for the thought in helping me :good:
Kirito821 said:
When I was trying flashing again, the watch fallen from the desk and for instinct I grabbed the cable and the pad for GND and RX broke up
Thank you for your time and help in troubleshooting adfree :good:
And thanks notupus for the thought in helping me :good:
Click to expand...
Click to collapse
So gnd is the metal part and i'l looking for rx
Long time ago I have ripped off my Gold pad for Data -
http://forum.gsmhosting.com/vbb/12484681-post5.html
The white point in my Picture...
Best Regards
Someone please compile a zip file and maybe a pcb dezign with pogo pins
I'm also stuck with 'Re-Partition operation failed'. Did anyone find a solution for this problem?
I have a problem, I tried to unbrick my GEAR S2 720 and now it says "Firmware upgrade encountered an issue. Please select recovery mode in KIES & try again". I tried unpluggin the battery, but same problem. I think it will be bricked 4ever
My phone; Galaxy S7 (SM-G930F) Exynos.
Stupidly tried to revert phone back to stock without doing enough research first! now phone seems to be bricked!. could have hard bricked it this time!!.
I started by first uninstalling root then thought it might be a good idea to use smart switch for first time to sort software out. really BAD IDEA now phone bricked. first time using smart switch
Now when I start phone all i get is,
( An error aoccured while updating the device software. Use the Emergency recovery function in the smart switch PC software)
but when i try and that all I get is " This function does not support your device" I wish trhey said that when I open the bloody software but it let me start !!!! now I can't get phone back.
I can get another screen which is ( Warning A custome OS can cause critical problems blar blar blar Press volume up key to continue or down to restart) screen. I tried to download a stock rom and use Odin to install it at that screen but it fails every time it sees it in odin and after applying all the lines and starting it it fails after img installing. Not sure I have right stock rom.
Can any one please help I need a link to this phones original stock rom so I can return it to its old self so i can update the software and then perhaps root it to remove bloatware.
I had [ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 installed worked ok untill i noticed an issue with net. it had really bad network speeds on both wifi and phone network so needed to revert it.
can anyone please point me in right direction to stock rom and perhaps give a detailed way out of this mess!.
I want to install my original stock rom and update it then root that rom and debloat it.
any help here would be greatfully recieved.
thanks
Go to https://www.sammobile.com/firmwares/ and select your country and your device.
hedgehog99de said:
Go to https://www.sammobile.com/firmwares/ and select your country and your device.
Click to expand...
Click to collapse
Thanks for replying
I have been there but was unsure what to choose!
I'm assuming I choose (BTU) but there are a few options to choose under United Kingdom
is BTU the right one. do you know how I can check!.
Thanks again.
Update: downloaded that version used Odin but it still fails! I get this in Odin,
<ID:0/004> 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/004> Odin engine v(ID:3.1401)..
<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: 4004 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!.
Would really appreciate some help on how to proceed I.
Hi, I don't know if this solution can help you. But it can give you a clue.
I think there is an Odin problem with the .lz4 compression format. You should unzip the official firmware packages, unzip them with 7-zip and pass them to .tar
Here you can see how to do:
In principle it should work.
You already know that when you do this kind of thing you have a risk. But you can try.
Logeate said:
Hi, I don't know if this solution can help you. But it can give you a clue.
I think there is an Odin problem with the .lz4 compression format. You should unzip the official firmware packages, unzip them with 7-zip and pass them to .tar
Here you can see how to do:
In principle it should work.
You already know that when you do this kind of thing you have a risk. But you can try.
Click to expand...
Click to collapse
I fully understand and know what you mean I know its a bit risky but no worries buddy and thank you for replying very much appreciated I will certainley give that a try good idea. I was on the verge on buying a new phone any way so no loss really but it was a good little phone and would love to use it for my grand child for kids youtube. been way behind upgrades for some time now and was kind of coerced by family to join the dark side! because there are some benifits android just can't match and I'm missing out on with my grandkids
I bit my lip and bought the fruit from Eve :/ I'm now a sinner and traitor lol being a windows man like for ever .
again many thanks for your help I will update this thread to let you know the outcome fingers crossed cheers buddy