Samsung galaxy s4 mini GT-I9195 bricked without doing anything. - General Questions and Answers

Hi all, my S4 mini won't turn on, while i was messaging, the display shutting down and can't turn on it.
When i connected it to my pc, my pc found new driver: QHSUSB_DLOAD. I searched it on google and i discovered that my phone was bricked without doing anything. So i flashed a sdcard with debrick.img and my phone finally showed:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS. .
BOOT RECOVERY
WRITE 139008 sectors
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME: GT-i9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANT VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION: Enable
So i tried to flash it with Odin and after Odin said:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_shi p_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULT I_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_M ULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So i searched on internet PIT files and i found "CSB_signed_SERRANOLTE_ONEPIT_OPEN_130523.pit", i tried to flash with it and Odin show same thing:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.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>
<ID:0/004> There is no PIT partition.
While on the phone showed:
Code:
PIT FAIL : TOTAL SECTORS 0
ODIN flash read failure
I tried nand flash erase and show me other errors.
I think emmc died, if not, can anyone help me?
if emmc died, how can i install all partition ( bootloader ecc.) on sdcard for start the phone with it?

supergatto said:
Hi all, my S4 mini won't turn on, while i was messaging, the display shutting down and can't turn on it.
When i connected it to my pc, my pc found new driver: QHSUSB_DLOAD. I searched it on google and i discovered that my phone was bricked without doing anything. So i flashed a sdcard with debrick.img and my phone finally showed:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS. .
BOOT RECOVERY
WRITE 139008 sectors
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME: GT-i9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANT VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION: Enable
So i tried to flash it with Odin and after Odin said:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_shi p_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULT I_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_M ULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So i searched on internet PIT files and i found "CSB_signed_SERRANOLTE_ONEPIT_OPEN_130523.pit", i tried to flash with it and Odin show same thing:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.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>
<ID:0/004> There is no PIT partition.
While on the phone showed:
Code:
PIT FAIL : TOTAL SECTORS 0
ODIN flash read failure
I tried nand flash erase and show me other errors.
I think emmc died, if not, can anyone help me?
if emmc died, how can i install all partition ( bootloader ecc.) on sdcard for start the phone with it?
Click to expand...
Click to collapse
here same

Can anyone help me?

@supergatto @espaciox99
I had the same problem with my galaxy s4 (gt-9505) where it didn't want to flash stock rom but I was able to root the phone (with cf autoroot) and also able to flash cwm recovery and flash resurrection remix and it's working fine now. Try it out and tell me if it works (better custom than nothing) and don't forget to press the thanks button .

a. felon said:
@supergatto @espaciox99
I had the same problem with my galaxy s4 (gt-9505) where it didn't want to flash stock rom but I was able to root the phone (with cf autoroot) and also able to flash cwm recovery and flash resurrection remix and it's working fine now. Try it out and tell me if it works (better custom than nothing) and don't forget to press the thanks button .
Click to expand...
Click to collapse
I tried CF-Auto-Root by this http://download.chainfire.eu/425/CF...Auto-Root-serranolte-serranoltexx-gti9195.zip
It says to use PIT file, i tried with it, and show same error of first post.

supergatto said:
I tried CF-Auto-Root by this http://download.chainfire.eu/425/CF...Auto-Root-serranolte-serranoltexx-gti9195.zip
It says to use PIT file, i tried with it, and show same error of first post.
Click to expand...
Click to collapse
Try with this method, it worked for me http://forum.xda-developers.com/showthread.php?t=2364980 good luck.
Don't just say thanks, press the ? button.

a. felon said:
Try with this method, it worked for me http://forum.xda-developers.com/showthread.php?t=2364980 good luck.
Don't just say thanks, press the button.
Click to expand...
Click to collapse
Here the result...
{
"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"
}

supergatto said:
Here the result...
Click to expand...
Click to collapse
This is the only thing I could find, hope it solves your problem bro.
Follow radicspeter's method as it's the one that seems to work. http://forum.xda-developers.com/showthread.php?t=2469375&page=2 Tell us if it works because @espaciox99 has the same problem like you, good luck.

Thanks for reply.
Code:
<ID:0/013> Odin engine v(ID:3.1100)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013>
<ID:0/013> There is no PIT partition.
After used PIT file.
Code:
<ID:0/013> Odin engine v(ID:3.1100)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> FAIL!
<ID:0/013>
<ID:0/013> Re-Partition operation failed.

UP

UP

UP

Your eMMC is definitively bricked, or at least it seems to be.
I didn't find any solution for that on quick, but you could be able to manually repartition your sd card. I see your device is booting from sd card, so maybe you could give a try to plug in the SD into a linux machine and see what it shows you.

xdvs23 said:
Your eMMC is definitively bricked, or at least it seems to be.
I didn't find any solution for that on quick, but you could be able to manually repartition your sd card. I see your device is booting from sd card, so maybe you could give a try to plug in the SD into a linux machine and see what it shows you.
Click to expand...
Click to collapse
I did it, and show 24 partitions like modem, sbl1, sbl2, sbl3, recovery, system, tz, hidden, cache, efs, and others, but if i want boot android with sdcard on my phone, how can i do?
I tried to copy eMMC from another S4 mini GT-I9195 on sdcard with "busybox dd..." command and it show same thing of pics.
Other thing that i tried on my phone with Odin: I tried to repartition eMMC with PIT and CSC and both show same thing of pics.

supergatto said:
I did it, and show 24 partitions like modem, sbl1, sbl2, sbl3, recovery, system, tz, hidden, cache, efs, and others, but if i want boot android with sdcard on my phone, how can i do?
I tried to copy eMMC from another S4 mini GT-I9195 on sdcard with "busybox dd..." command and it show same thing of pics.
Other thing that i tried on my phone with Odin: I tried to repartition eMMC with PIT and CSC and both show same thing of pics.
Click to expand...
Click to collapse
Good, I don't know if you need to install a bootloader but there are couple of videos showing how you can boot from sdcard by modifying the hardware.

xdvs23 said:
Good, I don't know if you need to install a bootloader but there are couple of videos showing how you can boot from sdcard by modifying the hardware.
Click to expand...
Click to collapse
Can you post some video? I didn't find it...

supergatto said:
Can you post some video? I didn't find it...
Click to expand...
Click to collapse
I found this on quick.

xdvs23 said:
I found this on quick.
Click to expand...
Click to collapse
In the video show same thing that i did... Except disassembling the phone. And this doesn't work.

supergatto said:
In the video show same thing that i did... Except disassembling the phone. And this doesn't work.
Click to expand...
Click to collapse
Ok so I don't know if there is any way to fix that. I also had a eMMC brick but on a S3 mini. If you did not install custom software you can send it for repair to samsung. If your warranty is already void you can pay for them to repair it but that would be expensive. You can also look for a eMMC replacement and replace it yourself. That could cost around 40 bucks, depending on what you need to order (dollars or euros).
Your emmc is now write-protected that means you simply can not flash anything. A reason for the brick can be overwriting the same file many times, using poorly developed apps or software / ROMs, daily backups in messaging apps, but also flashing many many many times could potentially make the eMMC to die. That is well-known on Samsung devices.

Is there any way for boot android from sdcard without replacing eMMC?
I found other thread with write protection: enabled but they can flash..
http://forum.xda-developers.com/showthread.php?t=2322185

Related

[q] help required for bricked samsung gt-s6102

My friend has a Samsung GT-S6102 and he tried to flash a custom firmware without pre-rooting the phone. The phone was stuck in bootloop and he gave the phone to me for repair because I have been flashing phones like my Xperia mini pro and Samsung Monte, etc.
However, this is the first time I had to use Odin to do something like this. As per my experience so far, the most difficult part is to find the right firmware for this phone (I require the Indian firmware). So, after lots of brainstorming in the XDA forum I flashed these files (a) BOOT_S5360DDKK1_REV05.tar (b) torino_1205.pit (c) PDA, Phone and CSC files from S6102_DDMC1_ODDMB1_DDMC1. Now after successfully completing the flash process the phone still goes to bootloop and the Samsung Galaxy logo appears upside down (mirror image). I am attaching the screenshot here for your reference. Moreover, I cannot view the download mode because of white screen when I press volume down+home+power keys. But I can still reflash following the steps as it would if it was normal.
Here's the odin flash log.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S6102_DDMC1.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_S6102_DDMC1.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_S6102_ODDMB1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> BcmBoot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.img
<ID:0/008> param.lfs
<ID:0/008> system.img
<ID:0/008> userdata.img
<ID:0/008> BcmCP.img
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> csc.rfs
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Any help would be greatly appreciated. Please note that this phone is not rooted so can't go to CWM either.
So, frustrating... somebody got to have a way to revive this bricked phone.
Can somebody tell me how to root and to flash a custom kernel on an already bricked phone.....?
From the screenshot it shows that the odin version is not correct (Its for galaxy grand)
Try using Odin 3v1.8
For firmwares
Go here
Sent by typing by my fingers
@AMIT
Thank you very much for your reply Amit but I'm afraid that it's not going to work either. I've also used the older version of odin the one that you mentioned but with no luck. My only chances are if I can somehow alter the root permission and flash a custom kernel and then flash a new rom. However, I've searched many forums but nobody knows anything about rooting an already bricked phone.
It's quite easy otherwise to root a phone that's in a working condition. So sad...
Anyways, thanks a lot buddy....
Withe Screen on GT-S6102
Hello people
I'need a little help
I was trying to apply a monster rom to my girlfriend galaxy y duos.
Then it reboot and I could see the Monster boot animation but with the picture all mess up.
Then I enter in to Recovery mode an the menu was also mess up.
finaly I could enter with the odin 3 an flash the CSC_S5360_ODDLK1 pack (3 files)
then After reboot all I have is a with screen.
I can go in recovery menu or download menu, at least that I see, because all I see is a the withe screen
Can somebody help to riveve this brick
Thanks

[Q] HELP please

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 ​

Failed Root Resulting in Problems. Please Help.

So I went to root the phone and I did so with CF Auto Root. I went into Super Su and decided it was not what I was looking for. I was hoping for more of a GUI TWRP system and decided to unroot and factory restore the phone. I'm stressed to the point where i have no memory of how the phone got screwed up at this point. Here is what I do know.
When I power the device on normally it is frozen at the Samsung Galaxy S6 boot page and at the top it says KERNEL REV CHECK FAIL DEVICE 3 BINARY 2. Is this because I have the wrong firmware on the device? Is there any way I can get the bootloader, the firmware and everything else and just restore everything at once? Samsung Smart Switch fails to recover the device and I would absolutely love to do an emergency recovery, but it keeps asking for a code from a previous computer and I have no idea what it's talking about.
Any help would be appreciated.
jblevins1991 said:
So I went to root the phone and I did so with CF Auto Root. I went into Super Su and decided it was not what I was looking for. I was hoping for more of a GUI TWRP system and decided to unroot and factory restore the phone. I'm stressed to the point where i have no memory of how the phone got screwed up at this point. Here is what I do know.
When I power the device on normally it is frozen at the Samsung Galaxy S6 boot page and at the top it says KERNEL REV CHECK FAIL DEVICE 3 BINARY 2. Is this because I have the wrong firmware on the device? Is there any way I can get the bootloader, the firmware and everything else and just restore everything at once? Samsung Smart Switch fails to recover the device and I would absolutely love to do an emergency recovery, but it keeps asking for a code from a previous computer and I have no idea what it's talking about.
Any help would be appreciated.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
There you go..
brenner650 said:
https://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
There you go..
Click to expand...
Click to collapse
I have already done this. It failed. I need help getting into Emergency Recovery. This is just Recovery.
jblevins1991 said:
I have already done this. It failed. I need help getting into Emergency Recovery. This is just Recovery.
Click to expand...
Click to collapse
Is your device SM-G920F?
forumber2 said:
Is your device SM-G920F?
Click to expand...
Click to collapse
It's the sm-g920t.
jblevins1991 said:
It's the sm-g920t.
Click to expand...
Click to collapse
So, your phone should be T-Mobile.
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920T
Region: TMB (write XAR here if your phone is not T-Mobile variant)
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Downlaod" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfrim) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
forumber2 said:
So, your phone should be T-Mobile.
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920T
Region: TMB (write XAR here if your phone is not T-Mobile variant)
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Downlaod" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfrim) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
Click to expand...
Click to collapse
<ID:0/008> Added!!
<ID:0/008> Removed!!
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1203)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> param.bin
<ID:0/008> cm.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
This is the log when I tried your solution. Any ideas?
jblevins1991 said:
<ID:0/008> Added!!
<ID:0/008> Removed!!
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1203)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> param.bin
<ID:0/008> cm.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
This is the log when I tried your solution. Any ideas?
Click to expand...
Click to collapse
Try with another usb cable, another usb port or another PC.
I bought an official samsung charger and fixed it. I think the old charger was disconnecting during the smart switch initialization process.
Any way to fix knox?

S6 Stuck at Logo Screen, flashed new ROM twice with no change

Hello,
A bit of back story first - yesterday, my mother's Galaxy S6 (SM-G920F) suddenly rebooted to the device's logo screen ( the "Samsung Galaxy S6....powered by android" one) and it's been stuck there since. There had been no "tinkering" so to say with the device; debugging was disabled, the bootloader had not been tampered with at all, and all the updates were done through the official android route. The last major update was around a month ago, to Nougat from MM, after which I cleared the cache. The latest update was about 10 days ago, a minor Nougat one, but the cache had not been wiped.
Now down to business. The phone does not turn off at all. Holding the power button and the volume down just reboots it to the same screen. That being such, I cannot access recovery mode. I can however access Download Mode which makes be believe that all hope is not lost.
Using Odin, I attempted to flash a stock ROM, which for this model was Android v5.1.1, and now I understand why that wouldn't work. At this point instead of the logo screen, it showed a blue screen saying something along the lines of "An error has occurred while updating your phone, please use Smart Switch emergency recovery". I had tried to connect to smart switch before but it wouldn't recognize the device. I was saving initialization as a last resort.
I then flashed the most recent MM ROM for this model (which I found on sammmobile) using Odin, having read it was possible to still downgrade, and believing that perhaps Nougat was causing this problem. And it was successful, except the phone now returned to the logo screen. Again, with the same problems as before. And I still couldn't wipe the data and cache because I still couldn't access recovery mode.
Finally I connected the phone to Smart Switch and chose to initialize it. After going through all the steps, and downloading the files, it said it was successful but the phone is still stuck at the damn logo screen. I can still access download mode for what it's worth but I haven't a clue now as to what I should do next.
Any help or suggestions would be greatly appreciated. Thanks.
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920F
Region: PHN
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this Odin (even if you have another one);
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfirm) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
If this method doesn't fix you issue, you have to replace the motherboard then.
no luck
forumber2 said:
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
...
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
If this method doesn't fix you issue, you have to replace the motherboard then.
Click to expand...
Click to collapse
thank you so much for your answer but it does not seem to have worked. I did everything as instructed but I'm not quite sure as to why this is happening exactly. This is the log from Odin, maybe it'll help:
<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> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> userdata.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
(when it said "please wait about two minutes" it actually proceeded to the next step very quickly)
It appears to have loaded successfully but it is still stuck at the logo screen. Could you please explain why this not working would mean I would have to replace the motherboard? Thank you once again
(also I'm running Odin with only "Auto Reboot" and "F.Reset Time" ticked, don't know if that will help)
rayofmoonshine said:
thank you so much for your answer but it does not seem to have worked. I did everything as instructed but I'm not quite sure as to why this is happening exactly. This is the log from Odin, maybe it'll help:
<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> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> userdata.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
(when it said "please wait about two minutes" it actually proceeded to the next step very quickly)
It appears to have loaded successfully but it is still stuck at the logo screen. Could you please explain why this not working would mean I would have to replace the motherboard? Thank you once again
Click to expand...
Click to collapse
Odin log says that there's no problem.
The produce I've wrote above is the last think you can do on new Samsung devices.
forumber2 said:
Odin log says that there's no problem.
The produce I've wrote above is the last think you can do on new Samsung devices.
Click to expand...
Click to collapse
Do you have any idea what could have caused this issue? Would changing the motherboard be guaranteed to fix this and if so, how?
rayofmoonshine said:
Do you have any idea what could have caused this issue? Would changing the motherboard be guaranteed to fix this and if so, how?
Click to expand...
Click to collapse
Replacing motherboard will not help You unless You have a way to program EFS and IMEI information to it.

Samsung galaxy note 10.1 wont start

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

Categories

Resources