Hi all. Well, i have a Samsung Galaxy S3 mini (i8200), wich it was given to me to fix it.
I want to clarify that i don't know how did the phone came into this state, i mean, i don't know if the user tried to flash a new rom or what, the thing is that the phone, right now, when i turn ON, it gets stuck on Samsung logo.
I can only enter the download mode.
I can't enter Recovery mode
I've tryed so many things. I've tryed to flash the stock rom (downloaded from Sammobile) with ODIN, but it always shows this error:
<ID:0/026> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8200XXUAOA2_I8200OXAAOA2_I8200XXUAOA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/026> Odin v.3 engine (ID:26)..
<ID:0/026> File analysis..
<ID:0/026> SetupConnection..
<ID:0/026> Initialzation..
<ID:0/026> Get PIT for mapping..
<ID:0/026> Firmware update start..
<ID:0/026> timh.bin
<ID:0/026> NAND Write Start!!
<ID:0/026> obm.bin
<ID:0/026> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
(I've tryed with differents Odin versions, 3.04, 3.07 , 3.09 , also with different USB ports, and a different PC)
I add a quote i read:
The Problem: Sometimes when you flash a ROM (TouchWiz or AOSP), there is a risk of the /system and /data partitions not wiping correctly thus leading them to be formatted with R/O permissions rather than R/W. This makes it impossible for the phone to boot up because no data can be written. Not even a typical ODIN flash back to stock or rooted stock will fix this. Using CWM to flash another ROM will yield the same no boot results. Furthermore, the stock recovery will not work and it becomes impossible to perform a factory reset. Sound frustrating? It is.
So, i read also, that a pit file its supposed to fix my issue ( this rewrites the PIT tables with the proper permissions).
I get the pit file, and i tried... the results:
<ID:0/026> Added!!
<ID:0/026> Removed!!
<ID:0/026> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8200XXUAOA2_I8200OXAAOA2_I8200XXUAOA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/026> Odin v.3 engine (ID:26)..
<ID:0/026> File analysis..
<ID:0/026> SetupConnection..
<ID:0/026> Initialzation..
<ID:0/026> Set PIT file..
<ID:0/026> DO NOT TURN OFF TARGET!!
<ID:0/026> Get PIT for mapping..
<ID:0/026> Firmware update start..
<ID:0/026> timh.bin
<ID:0/026> NAND Write Start!!
<ID:0/026> obm.bin
<ID:0/026> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
So, why i keep trying and keep giving an opportunity to this phone?, if im correct, its not a hard brick because i still can enter the Download mode, and in PRODUCT NAME, it still saying GT-I8200 , so, i still have hope.
Im looking for some help, i need help to fix this, im sure im missing something. What can i do?
Thanks in advance.
i have a problem
Sasaoy said:
Hi all. Well, i have a Samsung Galaxy S3 mini (i8200), wich it was given to me to fix it.
I want to clarify that i don't know how did the phone came into this state, i mean, i don't know if the user tried to flash a new rom or what, the thing is that the phone, right now, when i turn ON, it gets stuck on Samsung logo.
I can only enter the download mode.
I can't enter Recovery mode
I've tryed so many things. I've tryed to flash the stock rom (downloaded from Sammobile) with ODIN, but it always shows this error:
<ID:0/026> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8200XXUAOA2_I8200OXAAOA2_I8200XXUAOA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/026> Odin v.3 engine (ID:26)..
<ID:0/026> File analysis..
<ID:0/026> SetupConnection..
<ID:0/026> Initialzation..
<ID:0/026> Get PIT for mapping..
<ID:0/026> Firmware update start..
<ID:0/026> timh.bin
<ID:0/026> NAND Write Start!!
<ID:0/026> obm.bin
<ID:0/026> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
(I've tryed with differents Odin versions, 3.04, 3.07 , 3.09 , also with different USB ports, and a different PC)
I add a quote i read:
The Problem: Sometimes when you flash a ROM (TouchWiz or AOSP), there is a risk of the /system and /data partitions not wiping correctly thus leading them to be formatted with R/O permissions rather than R/W. This makes it impossible for the phone to boot up because no data can be written. Not even a typical ODIN flash back to stock or rooted stock will fix this. Using CWM to flash another ROM will yield the same no boot results. Furthermore, the stock recovery will not work and it becomes impossible to perform a factory reset. Sound frustrating? It is.
So, i read also, that a pit file its supposed to fix my issue ( this rewrites the PIT tables with the proper permissions).
I get the pit file, and i tried... the results:
<ID:0/026> Added!!
<ID:0/026> Removed!!
<ID:0/026> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8200XXUAOA2_I8200OXAAOA2_I8200XXUAOA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/026> Odin v.3 engine (ID:26)..
<ID:0/026> File analysis..
<ID:0/026> SetupConnection..
<ID:0/026> Initialzation..
<ID:0/026> Set PIT file..
<ID:0/026> DO NOT TURN OFF TARGET!!
<ID:0/026> Get PIT for mapping..
<ID:0/026> Firmware update start..
<ID:0/026> timh.bin
<ID:0/026> NAND Write Start!!
<ID:0/026> obm.bin
<ID:0/026> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
So, why i keep trying and keep giving an opportunity to this phone?, if im correct, its not a hard brick because i still can enter the Download mode, and in PRODUCT NAME, it still saying GT-I8200 , so, i still have hope.
Im looking for some help, i need help to fix this, im sure im missing something. What can i do?
Thanks in advance.
Click to expand...
Click to collapse
I have the same problem.
I installed several ROM. Finally, I wanted to go back to the Stock ROM and I could not. Error in the memory. Odin stops in the middle of the wash and the phone oběvují different red numbers. He gets into Download Mode, but it does not install it. or I do not get Recavery. I found a tutorial on repairing large S3, but I need my stuff on S3 Mini (GT-I8190). If someone finds something, or would even help it would have been nice. Thank you.
http://forum.xda-developers.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558
Hello,
I had the exact same problem,
messed with R W permissions,
So you should try Heimdall,
I managed to read my PIT file, so it is somehow alive,
but could'nt write a new PIT file on the phone,
I stopped searching and ended buying an old (but working) motherboard for my phone.
But you should really continue, and give it a try.
Related
Dear all,
I found a new firmware on sammobile site and thought to upgrade my Galaxy note from:
N7000JPLPD_N7000OJPLP7_N7000XXLPT_HOME.tar.md5
to:
N7000JPLR8_N7000OJPLR8_N7000XXLRK_HOME.tar.md5
(Both of them for Pakistan)
First I used Odin 1.83 to flash but after about 20% the Odin turned red indicating 'Fail'
Then I searched the web and (I know it's my fault) somewhere downloaded Odin 1.85, checked all the fields on Odin, like "Re Partition- Autoboot-F reset time"
I check them all and then another mistake.... used the same MD5 file in all 3 'PDA, PHONE, CSC" and flashed again.
And also used the PIT file which was in the Odin 1.85's folder.
Now I can enter the download mode but if I try to flash the new ROM, it goes upto 20% and says something like this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPLR8_N7000OJPLR8_N7000XXLRK_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> hidden.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And If I flash the older ROM it says like:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPLPD_N7000OJPLP7_N7000XXLPT_HOME.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> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> cache.img
<ID:0/008> NAND Write Start!!
<ID:0/008> factoryfs.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help
sulemani1 said:
Dear all,
I found a new firmware on sammobile site and thought to upgrade my Galaxy note from:
N7000JPLPD_N7000OJPLP7_N7000XXLPT_HOME.tar.md5
to:
N7000JPLR8_N7000OJPLR8_N7000XXLRK_HOME.tar.md5
(Both of them for Pakistan)
First I used Odin 1.83 to flash but after about 20% the Odin turned red indicating 'Fail'
Then I searched the web and (I know it's my fault) somewhere downloaded Odin 1.85, checked all the fields on Odin, like "Re Partition- Autoboot-F reset time"
I check them all and then another mistake.... used the same MD5 file in all 3 'PDA, PHONE, CSC" and flashed again.
And also used the PIT file which was in the Odin 1.85's folder.
Now I can enter the download mode but if I try to flash the new ROM, it goes upto 20% and says something like this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPLR8_N7000OJPLR8_N7000XXLRK_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> hidden.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And If I flash the older ROM it says like:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPLPD_N7000OJPLP7_N7000XXLPT_HOME.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> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> cache.img
<ID:0/008> NAND Write Start!!
<ID:0/008> factoryfs.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help
Click to expand...
Click to collapse
Hi friend just try flashing to GB and then to any other.
Use company cable for data transfer, try with another usb port and i hope it must get cleared.
Press THANKS if it helped you
Thank you my friend, but could you guide me where to find GB? And what GB actually is? The older 2.3.6 Ginger bread?
sulemani1 said:
Thank you my friend, but could you guide me where to find GB? And what GB actually is? The older 2.3.6 Ginger bread?
Click to expand...
Click to collapse
GB actually is the older 2.3.6 Ginger
you find GB in sammobile site
If it's failing at factory.fs then you could be in longer term trouble, let us know.
Sent from my GT-N7000 using xda premium
dude... try this,,
just pull out the battery. wait for 10 secs.. reinsert. go back to download mode.. use odin 1.85 and just select the tar.md5 fine in pda section.. donot check repartion.. dont use pit file.
PS: if odin is stuck once.. u cannot continue from there.. the phone needs a reboot for another try
I read somewhere saying that flashing pit file must be accompanied by bootloader or your device might brick.
Sent from my GT-N7000 using xda premium
nokiamodeln91 said:
dude... try this,,
just pull out the battery. wait for 10 secs.. reinsert. go back to download mode.. use odin 1.85 and just select the tar.md5 fine in pda section.. donot check repartion.. dont use pit file.
PS: if odin is stuck once.. u cannot continue from there.. the phone needs a reboot for another try
Click to expand...
Click to collapse
Thanks friend.
I did it. Im ok now.
Thanks to all of you who helped me here.
EDIT: Rebooted my computer and phone and it flashed fine. Thank you for all the help. I'm off to explore the world of custom roms.
Finally decided to root my phone and install CM9 from GB 2.3.6 with the LA4 Kernel. Downloaded everything I needed as per Post 3 of this thread. Accidentally flashed the newer kernel instead of the pre rooted ROM.
Realizing my mistake, I tried flashing the correct ROM and PC Odin gives me a failure. The phone won't boot, it just stays stuck on the Galaxy Note N7000 Logo with an exclamation mark at the bottom.
Check if you have cwm (power+home +volume up) If so then flash this get the standard version, then go advanced options and reboot recovery...
After that do all wipes data/cache/Dalvik cache then flash the cm9 for n7000,then flash cm9 GApps then reboot...
After the system boots to android set it up and download triangle away and use it to get rid of the yellow triangle
If you don't have cwm then download a stock GB rom and flash it via odin... Start from scratch
Cheers
Tapatalking on my GT-N7000
what is the error pc odin giving you?
Don't quite remember anymore since it was from this morning. All I recall is the little box on the top left going red.
Could I try replicating the problem or do I risk damaging my phone?
odin won't damage the phone. As above poster said check if you have cwm, else use Odin again
nokiamodeln91 said:
odin won't damage the phone. As above poster said check if you have cwm, else use Odin again
Click to expand...
Click to collapse
No, I don't have CWM so I've been downloading a stock rom since I saw that post should take an hour with glorious third world internet. In the meantime should I fish out that error message you requested or is it not worth it at this point?
If you need all data back and everything to be working I would recommend you to flash back the same ROM you had earlier using odin.
Go back to Square 1.
Then root it from Dr Ketan's post.
as you downloading the rom. you are going to use Odin again. Let know the error
Yeap, another fail while using PCOdin.
Going to install samsung USB drivers from the file in this thread and get rid of Kies.
Here's the stuff from the little window.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLA4_N7000OXALA4_N7000XXLA4_HOME.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> factoryfs.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/007> Added!!
Edit: Tried again after reinstalling drivers. Still no go.
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLA4_N7000OXALA4_N7000XXLA4_HOME.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
great
Hi all,
Before I return this device back to Samsung i wanted to check here if anyone had similar Problems or can possibly help with this.
I've never had the Luxury of personally using this Device, the Original Owner bought it and during the OTA it appears something went wrong. Rather than returning it to Samsung directly (they have a notoriously bad reputation of turn around time here) she asked me to have a look at it
Originally it was stuck in a Bootloop of The Intro of the boy looking through the telescope and appearing with the Samsung logo in a recurring Bootloop. Kies (the terrible software it is) is stuck at the connecting screen and doesn't move further than that.
To the jist;
I cant enter Recovery Mode, it takes me directly to the "downloading" screen. I can however boot manually into the Downloading mode. I've tried reflashing the stock recovery with Odin but still won't allow me to get into it, it boots to download mode before I even get a chance to do anything else.
I've tried multiple full firmware's from samsung-updates/sammobile and all drop me back to the same screen (with Odin)
Naturally, I will turn this in to Samsung and wait the time that it takes to have it repaired/replaced for her. I just wanted to know if anyone had any great ideas i could go through before going ahead with this
Thanks in advance
kartoffelpower said:
Hi all,
Before I return this device back to Samsung i wanted to check here if anyone had similar Problems or can possibly help with this.
I've never had the Luxury of personally using this Device, the Original Owner bought it at Duty Free here in Dubai and during the OTA it appears something went wrong. Rather than returning it to Samsung directly (they have a notoriously bad reputation of turn around time here) she asked me to have a look at it
Originally it was stuck in a Bootloop of The Intro of the boy looking through the telescope and appearing with the Samsung logo in a recurring Bootloop. Kies (the terrible software it is) is stuck at the connecting screen and doesn't move further than that.
To the jist;
I cant enter Recovery Mode, it takes me directly to the "downloading" screen. I can however boot manually into the Downloading mode. I've tried reflashing the stock recovery with Odin but still won't allow me to get into it, it boots to download mode before I even get a chance to do anything else.
I've tried multiple full firmware's from samsung-updates/sammobile and all drop me back to the same screen (with Odin)
Naturally, I will turn this in to Samsung and wait the time that it takes to have it repaired/replaced for her. I just wanted to know if anyone had any great ideas i could go through before going ahead with this
Thanks in advance
Click to expand...
Click to collapse
What's the screen you get on Odin? What does it say?
robb13 said:
What's the screen you get on Odin? What does it say?
Click to expand...
Click to collapse
Hi Robb,
Thank you for the reply,
Odin is fine, it flashes without any issues but upon restarting without booting into any special mode, it comes up immediately with "downloading... do not turn of target!!"
When I flash with what i presume would be the correct firmware i get an error (it's bought in Dubai so i figured it was the XSG firmware)
When using the "official XSG" from samsung-updates (zip file EK-GC100_XSG_1_20121121162346) which extracts to GC100XXALK6_GC100OJVALK1_GC100XXALJG_HOME.tar i get this error;
Code:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GC100XXALK6_GC100OJVALK1_GC100XXALJG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> system.img
<ID:0/016> NAND Write Start!!
<ID:0/016> boot.img
<ID:0/016> cache.img
<ID:0/016> hidden.img
<ID:0/016> recovery.img
<ID:0/016> modem.bin
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
However if i flash with GC100XXALJF_GC100OXAALJF_GC100XXALJG_HOME.tar it is successful but after rebooting, its stuck in download mode,
here from Odin;
Code:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GC100XXALJF_GC100OXAALJF_GC100XXALJG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> boot.img
<ID:0/016> NAND Write Start!!
<ID:0/016> cache.img
<ID:0/016> hidden.img
<ID:0/016> modem.bin
<ID:0/016> recovery.img
<ID:0/016> system.img
<ID:0/016> RQT_CLOSE !!
<ID:0/016> RES OK !!
<ID:0/016> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/016> Removed!!
<ID:0/016> Added!!
When i boot into download mode/recovery mode myself i'm presented with;
"Odin Mode"
Product Name: EK-GC100_EUR_XX
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
kartoffelpower said:
Hi Robb,
Thank you for the reply,
Odin is fine, it flashes without any issues but upon restarting without booting into any special mode, it comes up immediately with "downloading... do not turn of target!!"
When I flash with what i presume would be the correct firmware i get an error (it's bought in Dubai so i figured it was the XSG firmware)
When using the "official XSG" from samsung-updates (zip file EK-GC100_XSG_1_20121121162346) which extracts to GC100XXALK6_GC100OJVALK1_GC100XXALJG_HOME.tar i get this error;
Code:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GC100XXALK6_GC100OJVALK1_GC100XXALJG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> system.img
<ID:0/016> NAND Write Start!!
<ID:0/016> boot.img
<ID:0/016> cache.img
<ID:0/016> hidden.img
<ID:0/016> recovery.img
<ID:0/016> modem.bin
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
However if i flash with GC100XXALJF_GC100OXAALJF_GC100XXALJG_HOME.tar it is successful but after rebooting, its stuck in download mode,
here from Odin;
Code:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GC100XXALJF_GC100OXAALJF_GC100XXALJG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> boot.img
<ID:0/016> NAND Write Start!!
<ID:0/016> cache.img
<ID:0/016> hidden.img
<ID:0/016> modem.bin
<ID:0/016> recovery.img
<ID:0/016> system.img
<ID:0/016> RQT_CLOSE !!
<ID:0/016> RES OK !!
<ID:0/016> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/016> Removed!!
<ID:0/016> Added!!
When i boot into download mode/recovery mode myself i'm presented with;
"Odin Mode"
Product Name: EK-GC100_EUR_XX
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Click to expand...
Click to collapse
This might help (again, this is why my thread should be a sticky) http://forum.xda-developers.com/showthread.php?t=2086636
Flash the firmware that fails on modem.
Let it fail. Turn off and boot into download mode again.
Then root the camera via odin with the root method Adam gave us.
That flash should go all the way 100%
After this, the camera should work again.
Try it, let us know if it helped.
robb13 said:
This might help (again, this is why my thread should be a sticky) http://forum.xda-developers.com/showthread.php?t=2086636
Flash the firmware that fails on modem.
Let it fail. Turn off and boot into download mode again.
Then root the camera via odin with the root method Adam gave us.
That flash should go all the way 100%
After this, the camera should work again.
Try it, let us know if it helped.
Click to expand...
Click to collapse
Thanks Robb, i've given it a try but it reboots back into Download Mode again
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GC100XXALK6_GC100OJVALK1_GC100XXALJG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> system.img
<ID:0/016> NAND Write Start!!
<ID:0/016> boot.img
<ID:0/016> cache.img
<ID:0/016> hidden.img
<ID:0/016> recovery.img
<ID:0/016> modem.bin
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/016> Removed!!
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-gd1-gd1xx-ekgc100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> recovery.img
<ID:0/016> NAND Write Start!!
<ID:0/016> cache.img
<ID:0/016> RQT_CLOSE !!
<ID:0/016> RES OK !!
<ID:0/016> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/016> Removed!!
<ID:0/016> Added!!
I even did a further step of removing modem.bin from the failed tar and repackaging it and reflashing, still returns back to downloading mode.
I do however now have Custom Binary Download: Yes
Downloading Adam's suggested JellyBean 4.1.1 build:GC100XXALK1 and will see if that works for me.
Have you tried getting into recovery?
Sent from my GT-N7100 using Tapatalk 2
RavenY2K3 said:
Have you tried getting into recovery?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I wish i could enter recovery but it no longer works, it takes me straight into downloading mode (even when using the Recovery mode combo when turning the camera on). This download mode is slightly different from the Download Mode launched with the combination, it only shows the Android Avatar + Downloading.... do not turn off target !!. (No odin, no flash counters, etc)
kartoffelpower said:
I wish i could enter recovery but it no longer works, it takes me straight into downloading mode (even when using the Recovery mode combo when turning the camera on). This download mode is slightly different from the Download Mode launched with the combination, it only shows the Android Avatar + Downloading.... do not turn off target !!. (No odin, no flash counters, etc)
Click to expand...
Click to collapse
What about trying to reflash just the recovery alone, stock that is and see if it kicks it into booting into it, to try a wipe perhaps, I've got the stock recovery if you want to give it a try?
Sent from my GT-N7100 using Tapatalk 2
RavenY2K3 said:
What about trying to reflash just the recovery alone, stock that is and see if it kicks it into booting into it, to try a wipe perhaps, I've got the stock recovery if you want to give it a try?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I tried the stock recovery recovery-stock-bll7-EKGC100 without any luck. Now after recent reflashing the camera boots to a white screen rather than downloading mode.I can still boot to download mode with the combination, the flashing counter has been reset but now also i can't flash ANYTHING onto it, got some new nifty error
Code:
<ID:0/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017>
<ID:0/017> There is no PIT partition.
I tried using the PIT file from Adam over at thispost but it throws me
Code:
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Set PIT file..
<ID:0/017> DO NOT TURN OFF TARGET!!
<ID:0/017>
<ID:0/017> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Having some fun with this device, will return it after the weekend if nothing works out, happy to any suggestions though
Thanks to everyone for the help so far
Sounds completely FUBAR, how did you clear the counter or did it do on it's own/by accident? haha.
Sent from my GT-N7100 using Tapatalk 2
RavenY2K3 said:
Sounds completely FUBAR, how did you clear the counter or did it do on it's own/by accident? haha.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, now that i can't flash roms at all withotu a valid PIT this camera has definitely reached its point where I will be turning it in to the Service center after the weekend.
The Counter Reset itself, i'm guessing once the partitions disappeared it took the count with it too ;-P
kartoffelpower said:
The Counter Reset itself, i'm guessing once the partitions disappeared it took the count with it too ;-P
Click to expand...
Click to collapse
Well..... Every cloud and all that haha
Sent from my GT-P7500 using Tapatalk HD
My GC2 EK-GC200 has same issue
I cant flash any firmware on my GC2, odin alway failed on system.img ... Please give me PIT file of Samsung EK-GC200
You will have to ignore my lack of knowledge on this, still don't play around with phones much , but anyway.
Recently iv been using a custom Rom of 4.4 Kitkat cyanogen mod Unofficial.
It was working fine, nothing wrong.
If found my phone this morning stuck in a bootloop, so i threw it into recovery and had a look, iv now apparently go 0mb of storage, unable to mount any system, data etc.
Iv tried taking it back to stock with Odin, but no joy as it cant seem access it.
Im unable to flash a new ROM from extSD, it just fails.
Any suggestions, and if u want more info just say
Need more information like where does Odin fail .
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305ZHALI7_I9305TGYALI6_I9305ZHALI1_HOME.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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Is a copy from the odin text output
Damaged Nand you need a new motherboard .
Hi,
I got myself a Samsung Galaxy SM-T900.
it originally would boot up into GREY battery icon and then apparently switch off although I could see the backlight was dimly on.
( So may have battery or USB charging port problems as well)
It was reporting a custom rom state so I thought I would put it back to stock and actually managed to flash it with Odin 3.10 ( which worked i.e. reported GREEN)
Rom file is T900XXSBPL3_T900OXABOH4_HOME.tar.md5 from Sam Mobile.
Although I got a GREEN light from Odin.... on tablet boot up, the tablet reported " Firmware upgrade encountered an issue...……….in Kies and try again"
Kies (2.6) would not connect to the tablet, nor could I do an emergency firmware recovery as no device comes up in the device list.
So I decided to reflash the stock rom with Odin 3.10 which was a bad move. For some unknown reason it stopped flashing at about halfway.
So I restarted the flash and now always get stuck on
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T900XXSBPL3_T900OXABOH4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin engine v(ID:3.1005)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> SingleDownload.
<ID:0/013> sboot.bin
<ID:0/013> NAND Write Start!!
<ID:0/013> FAIL!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Could someone please help... I am a casual ROM updater and just follow instructions , but now I am completely stuck.
Thanks
Hi,
Could someone please point me to the PIT file for this SM-T900 UK ROM i.e. BTU
T900XXSBPL3_T900OXABOH4_HOME.tar.md5 from SamMobile for SM-T900
I suspect its in there, but I think I may have corrupted my partitions, so need a PIT file...… I think?
Thanks