HELLO! I'm noob on this site so I am 100% that I'm posting on wrong forum or something like that so don;t shout at me
I have a headachke problem... I have GT-s5300 (samsun galaxy pocket) and i can;t flash anything with odin *I'm not noob on that Evrytime I try to flash Odin fails by saing Complete(write) operation failed or it get's stuck o settup connection. If you need more info just write in comments.
WERY IMPORTANT: I'm FROM LITHUANIA SO MY ENGLISH IS NOT BAD BUT NOT PERFECT SO SORRY FOR THAT. Hope sombody could help me
ODIN 1.85
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_s5300_xxlj4.tar.md5 is valid.
<OSM> MODEM_s5300_xxmd1.tar.md5 is valid.
<OSM> CSC_s5300_Oxflh4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ODIN 1.85/ ODIN 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_s5300_xxlj4.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> MODEM_s5300_xxmd1.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_s5300_Oxflh4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
Have u installed the proper drivers for your device? Or kies ?
Hit thanks rather than typing it now Free
Thank you for respones No kies on my PC cuoze I now it can interruopt ODIN flashing progress USB DRIVERS ARE FINE but I forgot to mention that I can't mount my sdcard where is system's backup so I think i might be bricked my phone (again)
Sorry again for bad ENGLISH
Aurimazs said:
HELLO! I'm noob on this site so I am 100% that I'm posting on wrong forum or something like that so don;t shout at me
I have a headachke problem... I have GT-s5300 (samsun galaxy pocket) and i can;t flash anything with odin *I'm not noob on that Evrytime I try to flash Odin fails by saing Complete(write) operation failed or it get's stuck o settup connection. If you need more info just write in comments.
WERY IMPORTANT: I'm FROM LITHUANIA SO MY ENGLISH IS NOT BAD BUT NOT PERFECT SO SORRY FOR THAT. Hope sombody could help me
ODIN 1.85
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_s5300_xxlj4.tar.md5 is valid.
<OSM> MODEM_s5300_xxmd1.tar.md5 is valid.
<OSM> CSC_s5300_Oxflh4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ODIN 1.85/ ODIN 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_s5300_xxlj4.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> MODEM_s5300_xxmd1.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_s5300_Oxflh4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
Click to expand...
Click to collapse
go to recovery mode wipe data factory reset, clear cache, dalvik cache and install again in odin
make sure you have downloaded a correct firmware
I can't clear dalvik cache cuose i can't go to sdcard or apply update i can only wipe data and cache. If you can cuold you find me PHILIPHINES GT-s5300 stock rom couse I think that was before becuose im trimg to SEB rom with Lithuanian language.
SORRRY FOR BAD ENGLISH
Aurimazs said:
Thank you for respones No kies on my PC cuoze I now it can interruopt ODIN flashing progress USB DRIVERS ARE FINE but I forgot to mention that I can't mount my sdcard where is system's backup so I think i might be bricked my phone (again)
Sorry again for bad ENGLISH
Click to expand...
Click to collapse
Are you sure the drivers are ok?
Try installing kies..
The odin error seems familiar, chances are that, you might not have been in download mode while flashing
Or that your drivers are incomplete.
BTW please post the link to the thread which you actually followed.
Hit thanks rather than typing it now Free
Ok i'll try to install it... I look threw lots of forums and trheads looking for something new but nothing worked. It even maybe be my usb plug(i fogot at the moment how it's called in ENG so if I'm wrong don't mention it ) because it's for Galaxt ACE not for GT-s5300
Aurimazs said:
I can't clear dalvik cache cuose i can't go to sdcard or apply update i can only wipe data and cache. If you can cuold you find me PHILIPHINES GT-s5300 stock rom couse I think that was before becuose im trimg to SEB rom with Lithuanian language.
SORRRY FOR BAD ENGLISH
Click to expand...
Click to collapse
you need temporary cwm to wipe dalvik cache download temporary cwm and clear from that
I know I can't go to CWM because I cant apply update form sdcard on recovery
After Installing KIES tried to flash again with ODIN
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_s5300_xxlj4.tar.md5 is valid.
<OSM> MODEM_s5300_xxmd1.tar.md5 is valid.
<OSM> CSC_s5300_Oxflh4.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> boot.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Still the same
Aurimazs said:
I OSM> All threads completed. (succeed 0 / failed 1) Still the same
Click to expand...
Click to collapse
1) First you need to use correct version of Odin3 , use only Odin 1.87 with PIT download from here always use fresh Odin, Before flashing do a battery pull and power button press for a min first. than enter download mode. fully charge battery, before flashing
2) what to do when you have setup connection problems Look at My Android Solutions (link below) or any other problem
3) download correct version of ROM for your region, most likely Poland from here
4) follow flashing procedure when using PIT (tick repartition) should be auto ticked, NEVER interrupt flashing,
Check this out! Links to useful Guides and " Banned " Documentaries
Check this out! Links to useful Guides and " Banned " Documentaries
Ok I'll try that ,but why can't I use my real region and shuold I use Poland Plus or just Poland at the momment I'm trying Poland Stock ROM as soon as over I will respond
Aurimazs said:
Ok I'll try that ,but why can't I use my real region and shuold I use Poland Plus or just Poland at the momment I'm trying Poland Stock ROM as soon as over I will respond
Click to expand...
Click to collapse
you can use any region that is closest to you for network coverage to work for you. , as I think Lithuania is not supported
Check this out! Links to useful Guides and " Banned " Documentaries
I'm trying right now But i bought this phone with Lith language included still thanks
THIS IS WAT I GOT Now looking forward to yor soliutions my problems are 3; 8; 11
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5300XXMD1_S5300OXXMD1_RST_S5300XXMD1_HOME.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> 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> Sbl.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
None of soliutions didn't help still can't flash :crying:
Aurimazs said:
THIS IS WAT I GOT No looking forward to yor soliutions my problems are 3; 8; 11
Click to expand...
Click to collapse
ok, this phone is fairly new as its earliest ROM, is 2.3.6 and 2012 series, so is your phone still under warranty? if so you should let Samsung solve it for free.
otherwise
1) you can connect it to KIES and see what is its response, ( does it have any updates?
2) you don't have recovery , right? so try flashing a stock kernel from here use ,tar for Odin flash, untick reboot and remove battery after flash, to enter recovery mode by combo keys, than you can flash CWM as update following above guide and enter CWM to flash custom ROM
Check this out! Links to useful Guides and " Banned " Documentaries
Okey so the below soliutions didn't work Kies always says connecting and after a few minutes it's says connect device
Now with warranty I didn't found until when warranty overs but I had already when then a 8 months ago(I guess) with almost the same problem, but right now it's already 1 year and 1d when i bought it so i think warranty is gone
If you don't have anything to offer for my I want to ask is there other flashers than odin if not how would it cost to repair my phone
OMG!!!!!!!!!! I found out what was wrong. you see i was trying to flash my SGP and it again got stuck on Setup conection so i opened task manager on Win7 and I spotted this :3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In ENG it mean USB DEVICE UNKNOWN
SO PLEASE HELP ME TO SOLVE IT ALREADY HIT THANK TO ALL OF YOU
Aurimazs said:
Okey so the below soliutions didn't work Kies always says connecting and after a few minutes it's says connect device
Now with warranty I didn't found until when warranty overs but I had already when then a 8 months ago(I guess) with almost the same problem, but right now it's already 1 year and 1d when i bought it so i think warranty is gone
If you don't have anything to offer for my I want to ask is there other flashers than odin if not how would it cost to repair my phone
Click to expand...
Click to collapse
no only odin is there for samsung to unbrick phone
if you can enter recovery mode you can use cwm or twrp
Aurimazs said:
In ENG it mean USB DEVICE UNKNOWN )
Click to expand...
Click to collapse
First, in Europe, I think Samsung warranty is for two years, so check that, where you bought your phone.
Second, unknown device or USB connection problems can be solved by following this
Third when using Odin3, KIES must be killed by Opening task manager on your PC and close these : Kies.exe , KiesTrayAgent.exe, and KiesPDLR.exe or it will cause setup connection errors in Odin
Fourth, try the stock ROM again with the PIT file or just the stock kernel to get 2e recovery
Fifth, you can use Heimdall to flash ( but you must know how to unpack your ROM for doing this) or you can try the many other flashers in MY Android Collections under recovery tools using ADB to connect and flash
Check this out! Links to useful Guides and " Banned " Documentaries
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
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 ?
So... I screwed up badly. I'm a noob and I was trying to get root access on my S7. I first followed this guide on the xda forums to step 15. While following this I had issues writing \data for the backup so I changed the partition from EXT2 to EXT3 fixing the issue. Then I was advised by someone that I shouldn't be following such an outdated guide and he sent me this one. But instead of going through the whole thing I only went from the part where I install the newest TWRP and everything worked. After a reboot on the the phone I booted into android and it was like after a factory reset with everything fine. I set some stuff on the phone up but didn't enable OEM unlock. Then the phone couldn't boot android with the FRP error. So I tried installing the stock firmware from here and that kept failing. Now whe I try to boot regularly instead of the samsung bootscreen with the FRP Lock error I get a light blue screen telling me to use the smart switch but ss didn't help me (it recognizes the phone and that something is wrong but the integrate fix option doesn't recognize the phone).
In odin I get this error when trying to flash the stock rom I linked to (Odin v 3.13) :
<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: 4043 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> 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)
I can get my phone to currently only boot into the download mode and the broken boot mode where it tells me to use smart switch
If anyone has any idea on what I could do to to somehow restore the phone or to get it to a semi functioning state I'd be very grateful.
I'm currently downloading a stock rom from another website: https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/AUT/#SM-G930F 2020-03-26 edition and will try it out once it's downloaded.
[EDIT] No luck with the different ROM, still the exact same issue.
Snapdragon or exynos?
SM-G930F=exynos more roms etc.
eg. Galaxy S7 G930U is = snapdragon USA version
mb. u try flash exynos rom having snap device?
GeloXD said:
Snapdragon or exynos?
SM-G930F=exynos more roms etc.
eg. Galaxy S7 G930U is = snapdragon USA version
mb. u try flash exynos rom having snap device?
Click to expand...
Click to collapse
nope, I have an exynos chip in my phone, but thanks for the suggestion
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
I am trying to get my samsung galaxy note 10.1 going again. Its fault condition is that it starts to boot gets the the carriers splash screen drops that off and just sits there with samsung displayed accross the screen. I downloaded/installed the samsung usb drivers. It connects to odin v3.14 ok with the blue indication. I downloaded the correct model and region file matching my model gt-n8020 (for carrier optus) zip file and unzipped it. it has AP BL and CSC dot md5 files. when I put the pad into download mode and run odin it errors. Would really appreciate if you can take a look at the log file errors and help with any ideas. thanks
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start.. <ID:0/008>
NAND Write Start!! <ID:0/008> SingleDownload.
<ID:0/008> boot.img
<ID:0/008> FAIL! <ID:0/008>
<ID:0/008> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1)
usually you will need 4x files, but that's not the error. as this outdated tablet is end of life try older version of Odin3 v3.10. you can also try heimdall frontend or cmd line tool. But consider it's simply emmc weared-out.
BL_*.tar.md5
AP_*.tar.md5
CP_*.tar.md5
CSC_*.tar.md5
aIecxs said:
usually you will need 4x files, but that's not the error. as this outdated tablet is end of life try older version of Odin3 v3.10. you can also try heimdall frontend or cmd line tool. But consider it's simply emmc weared-out.
BL_*.tar.md5
AP_*.tar.md5
CP_*.tar.md5
CSC_*.tar.md5
Click to expand...
Click to collapse
thankyou for the suggestion & info. I will try heimdell too. It fails under odin very quickly so I wonder if it has a valid comms link even though odin displays a link. Is there any way of monitoring the odin data packets I wonder?
check Odin3 folder for logfile
ok then thankyou
I checked the odin folder, no log file in there? The only log file I can see is the log tab in the application.
iank1000 said:
thankyou for the suggestion & info. I will try heimdell too. It fails under odin very quickly so I wonder if it has a valid comms link even though odin displays a link. Is there any way of monitoring the odin data packets I wonder?
Click to expand...
Click to collapse
iank1000 said:
thankyou for the suggestion & info. I will try heimdell too. It fails under odin very quickly so I wonder if it has a valid comms link even though odin displays a link. Is there any way of monitoring the odin data packets I wonder?
Click to expand...
Click to collapse
When I download the config files for my device I see an AP_ a BL_ and CSC_ files but dont see a CP_ file ?
CP_ is for modem/baseband updates maybe not included in OTA update. download full firmware from samfw.com
ok thanks will do
Thought I would try odin once more
Downloaded Config files from Samfw.com
Fails per log output 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..
<ID:0/009> Odin engine v(ID:3.1303)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 1746 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009>
<ID:0/009> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this is not Odin3 v3.10. try again with Odin3 v3.10.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I went looking for v3.10 but on thier website the oldest was v3.13.1. I will look around again for v3.10 odindownloader site lists v3.10.7 .6 and .5 so will try .5
unfortunately there is no official trustworthy download site for Odin3. you can get old version here.
Odin3 v3.13.1
Odin is a utility software developed and used internally by Samsung which can be used to flash a Custom Recovery firmware image (as opposed to the Stock recovery firmware image) to a Samsung Android device. It is also used as a way of unbricking...
forum.xda-developers.com
same result
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N8020XXUDNK1_CL3268618_QB2949266_REV00_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_N8020XXUDNK1_CL3268618_QB2949266_REV00_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_OPS_N8020OPSDNL1_CL3268618_QB3510213_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
extract pit file from CSC, enable checkbox Re-partitioning, select pit file in it's own slot, flash together with BL AP (CP) and CSC (not sure about CP is missing, tough)
WARNING: double check pit file matches your phone model!
TRY AT OWN RISK (random guide)
https://technastic.com/odin-nand-erase-samsung
thanks will try & advise. really appreciate the help
extracted pit file from csc file.
selected bl ap & csc file
under pit option selected pit file
same result failed
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N8020XXUDNK1_CL3268618_QB2949266_REV00_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_N8020XXUDNK1_CL3268618_QB2949266_REV00_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_OPS_N8020OPSDNL1_CL3268618_QB3510213_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
you can try heimdall
yes have been on that track. yet to overcome the missing .dll file at run time despite trying a few installs & work arounds to install
Microsoft Visual C++ 2010 runtimes. will have another go tomorrow
why not just use linux? you can also run in WSL