Hello,
I installed LineageOS 15.5 on my Galaxy S7(Herolte). But now I wan't to go back to the stock rom but I can't flash it with Odin due to the download secure mode activated.
So I can flash TWRP with Odin but not the official rom...
Thank you very much for your help
Use the latest version of ODIN (3.12.7 for Nougat, 3.13.1 for Oreo)
Secure download is normal and won't affect flashing
*Detection* said:
Use the latest version of ODIN (3.12.7 for Nougat, 3.13.1 for Oreo)
Secure download is normal and won't affect flashing
Click to expand...
Click to collapse
I still have the issue...
Screenshot of Odin : http://prntscr.com/jesqq8
(Same isue on both versions)
Try checking the "Re-partition" option in ODIN, possible Lineage has changed the partition sizes
*Detection* said:
Try checking the "Re-partition" option in ODIN, possible Lineage has changed the partition sizes
Click to expand...
Click to collapse
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..
<ID:0/005> Odin engine v(ID:3.1203)..
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> param.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)
Still don't work with Odin 3.12.7 and the lastest 7.0 firmware available in my country
On my Download Mode screen I have those informations :
Code:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G930F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FAP LOCK: OFF
Secure Download : Enable
WARRANTY VOID: 1
...
Thank you for your time and the help you provide !
princecomsy odin mybe? sorry for the name, i forgot btw just google it
maXDAmn said:
princecomsy odin mybe? sorry for the name, i forgot btw just google it
Click to expand...
Click to collapse
Same result...
Try different USB cable and USB port on the PC, or a new PC
*Detection* said:
Try different USB cable and USB port on the PC, or a new PC
Click to expand...
Click to collapse
It worked on my desktop computer, dunno why, probably a driver issue... Thanks ! Now I'm on the official Oreo rom ! :victory:
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 have a Verizon branded Samsung Galaxy S7 Edge. I rooted the phone. Later, I was trying to make some adjustments to the radio antennas and the phone hard bricked. I cannot factory reset or anything like that. I believe the bootloader is locked because I cannot load anything from the SD card or any other options.
I have tried re-flashing to the stock ROM using QPST Configuration, but it fails every time saying that the "Write failed" (as in no write access).
Part of the issue was that my phone would not be recognized in the COM port of the device manager; this was the problem that was not allowing me to make the radio adjustments. When I tried to get around this, that is when the phone bricked.
Are there any methods to re-flash a Verizon branded phone that is bricked and has this write access issue?
Thank you!
shrouwoods said:
I have a Verizon branded Samsung Galaxy S7 Edge. I rooted the phone. Later, I was trying to make some adjustments to the radio antennas and the phone hard bricked. I cannot factory reset or anything like that. I believe the bootloader is locked because I cannot load anything from the SD card or any other options.
I have tried re-flashing to the stock ROM using QPST Configuration, but it fails every time saying that the "Write failed" (as in no write access).
Part of the issue was that my phone would not be recognized in the COM port of the device manager; this was the problem that was not allowing me to make the radio adjustments. When I tried to get around this, that is when the phone bricked.
Are there any methods to re-flash a Verizon branded phone that is bricked and has this write access issue?
Thank you!
Click to expand...
Click to collapse
Greetings and welcome to assist. If your pc does not recognise your phone I fear you may be stuck, you can try kies emergency firmware recovery it may detect your phone
Good Luck
Sawdoctor
More Info Regarding Failed ROM Flash
When usinng Odin to try to flash the device with a stock ROM, I get the following errors.
<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> 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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
shrouwoods said:
When usinng Odin to try to flash the device with a stock ROM, I get the following errors.
<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> 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> 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
Have you tried kies emergency firmware recovery yet?
Sent from my SM-N930F using Tapatalk
I got a J7 BoostMobile and then i installed TWRP and a custom ROM but that custom rom dont recognize my SIM Card so now that i want to flash Stock from ODIN i cant and this is the log, if somebody could help me
please!
<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.1203)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> aboot.mbn
<ID:0/010> sbl1.mbn
<ID:0/010> rpm.mbn
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Boost Mobile J727perx
and in the phone its says
SW REV CHECK FAIL: [about] Fused 3 > Binary 1
[1| eMMC write fail : ABOUT
That's a security message from the bootloader (ABOOT)
RSDoTTo said:
I got a J7 BoostMobile and then i installed TWRP and a custom ROM but that custom rom dont recognize my SIM Card so now that i want to flash Stock from ODIN i cant and this is the log, if somebody could help me
please!
<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.1203)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> aboot.mbn
<ID:0/010> sbl1.mbn
<ID:0/010> rpm.mbn
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Boost Mobile J727perx
and in the phone its says
SW REV CHECK FAIL: [about] Fused 3 > Binary 1
[1| eMMC write fail : ABOUT
Click to expand...
Click to collapse
You're installing an older firmware over a newer one and it won't let you downgrade bootloader or the ABOOT which is the first partition it tries to flash. I would avoid trying to do it any further cause you might brick your device. Find the latest Odin tar if you can or wait for one to be released if it isn't already public. I think there's also a way to modify the stock tar to remove the modem and aboot image so it only updates the system and recovery which is what you're probably looking to do.
anthonykb said:
You're installing an older firmware over a newer one and it won't let you downgrade bootloader or the ABOOT which is the first partition it tries to flash. I would avoid trying to do it any further cause you might brick your device. Find the latest Odin tar if you can or wait for one to be released if it isn't already public. I think there's also a way to modify the stock tar to remove the modem and aboot image so it only updates the system and recovery which is what you're probably looking to do.
Click to expand...
Click to collapse
You know where can i do that? Thanks for the answer bro!
Virgin mobile Galaxy j727P
RSDoTTo said:
You know where can i do that? Thanks for the answer bro!
Click to expand...
Click to collapse
Here is the new firmware !
https://www.androidfilehost.com/?w=files&flid=232519
peter couniaz said:
Here is the new firmware !
https://www.androidfilehost.com/?w=files&flid=232519
Click to expand...
Click to collapse
I install the 4 files with ODIN, i have Lineage ROM so i think ineed to wipe first?
I'm new to this forum so if anything I need to correct please tell me.
So I have a Samsung Galaxy J3 Prime (Unlocked) and I'm using Odin v3.13.1. I used odin to flash TWRP from this link:https://forum.xda-developers.com/galaxy-j3-2017/development/ecovery-root-twrp-3-1-1-1-samsung-t3709987and I sadly messed up and bricked it . I go to get the new/stock firmware from https://www.sammobile.com/firmwares/galaxy-j3/SM-J327U/XAA/ here and I download and extract I go to flash it and it gives me this error.
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..
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 2757 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> sboot.bin
<ID:0/005> param.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have all the drivers installed correctly and on the device, I get the error SW REV. CHECK FAIL. DEVICE: 3, BINARY: 1. If anyone can help would be greatly appreciated.
RESOLVED
BrickMaster420 said:
RESOLVED
Click to expand...
Click to collapse
It's rather ignorant to simply post resolved as it helps no one in the future with a similar issue.
To anyone else, the issue would have been a firmware revision issue.
A more up to date revision 3 firmware was required.
Hi so found a guide on magisk on how to root s8+, but the version of twrp they used didnt accept touch input, so had to reboot the phone. I then flashed the latest twrp for that phone from the twrp website, but then when I went to wipe the data from twrp it said it couldnt mount some folders.
Anyway, so figured I should just wipe and start again. Downloaded latest stock firmware, loaded up the 4 files in Odin. if I use home_csc, the flashing process finishes in like 5 seconds saying successful, it should take longer since it needs to flash ap etc too but it doesn't seem to do that (but odin still says successful).
If I flash the normal CSC file instead, odin get stuck on "set partition"
<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> cache.img.lz4
and just stays here
Can someone help?
EDIT: i think it eventually failed
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Try to boot into recovery mode and factory reset again, and then instead of downloading the latest firmware, try to find a older firmware for you device and see if you can flash that
ignore this post please
Nameless Foe said:
Try to boot into recovery mode and factory reset again, and then instead of downloading the latest firmware, try to find a older firmware for you device and see if you can flash that
Click to expand...
Click to collapse
I am downloading the firmwares before the date of purchase as I don't believe I updated since then, god I wish I didn't rush into things
hassanhassan said:
I am downloading the firmwares before the date of purchase as I don't believe I updated since then, god I wish I didn't rush into things
Click to expand...
Click to collapse
I'm sorry this happened to you. I hope finding an older firmware will allow you to boot back into your device
Nameless Foe said:
I'm sorry this happened to you. I hope finding an older firmware will allow you to boot back into your device
Click to expand...
Click to collapse
thanks, will check it out and let you know, it was a backup phone that I wanted to play around with so I'm not that put out.
hassanhassan said:
thanks, will check it out and let you know, it was a backup phone that I wanted to play around with so I'm not that put out.
Click to expand...
Click to collapse
Oh well thats good lol. Good thing its not your daily driver
I tried again with older roms and have the same issue, if I use home csc it flashes in two seconds and the phone bootloops.
if I use the normal csc it gets stuck on set partition and here
<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> 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> sboot.bin.lz4
EDIT: I tried different vrsions of odin, 13.1 worked
hassanhassan said:
I tried again with older roms and have the same issue, if I use home csc it flashes in two seconds and the phone bootloops.
if I use the normal csc it gets stuck on set partition and here
<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> 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> sboot.bin.lz4
EDIT: I tried different vrsions of odin, 13.1 worked
Click to expand...
Click to collapse
Glad to hear you got it figured out? When you used older Odin, where you able to use latest firmware ?