Database Develop

Error while updating firmware

Hello,
While using Sygic navigation dad's galaxy ace (S5830i) got frozen, I restarted it by pushing the power button for a few seconds, but the phone didn't start up, just showing the samsung logo animation again and again... i tried to use recovery mode but it says it "failed to mount /data (invailed agrument).
So I thought i reinstall the original software, that I found on sammobile.com, but while I was installing it, some kind of error happened:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830iXXLA4_S5830iOXXLA2_RST_S5830iXXLA2_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> sbl.bin
<ID:0/005> BcmCP.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone is rooted, all drivers are installed on my pc.
I used more than one versions of Odin, including the version offered by sammobile.com (this is what you can seen on the screenshot)
Im so faithless about the phone now... :crying:
ps: i wasnt able to insert a link because its my first post, so see the screenshot attached.

Hi
valaky said:
Hello,
While using Sygic navigation dad's galaxy ace (S5830i) got frozen, I restarted it by pushing the power button for a few seconds, but the phone didn't start up, just showing the samsung logo animation again and again... i tried to use recovery mode but it says it "failed to mount /data (invailed agrument).
So I thought i reinstall the original software, that I found on sammobile.com, but while I was installing it, some kind of error happened:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830iXXLA4_S5830iOXXLA2_RST_S5830iXXLA2_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> sbl.bin
<ID:0/005> BcmCP.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone is rooted, all drivers are installed on my pc.
I used more than one versions of Odin, including the version offered by sammobile.com (this is what you can seen on the screenshot)
Im so faithless about the phone now... :crying:
ps: i wasnt able to insert a link because its my first post, so see the screenshot attached.
Click to expand...
Click to collapse
Hi there. How's the problem? I also got the same problem, flashing a firmware from sammobile and failing to flash it even if I use the .pit file i found on other threads. But you still have a chance. Download the Pda.tarhere and place it in the PDa section. do not use any pit file. it worked for me, I soft bricked my s5830i several times already and the PDA.tar works like a charm. I got it from here thanks to ickyyy

valaky said:
Hello,
While using Sygic navigation dad's galaxy ace (S5830i) got frozen, I restarted it by pushing the power button for a few seconds, but the phone didn't start up, just showing the samsung logo animation again and again... i tried to use recovery mode but it says it "failed to mount /data (invailed agrument).
So I thought i reinstall the original software, that I found on sammobile.com, but while I was installing it, some kind of error happened:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830iXXLA4_S5830iOXXLA2_RST_S5830iXXLA2_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> sbl.bin
<ID:0/005> BcmCP.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone is rooted, all drivers are installed on my pc.
I used more than one versions of Odin, including the version offered by sammobile.com (this is what you can seen on the screenshot)
Im so faithless about the phone now... :crying:
ps: i wasnt able to insert a link because its my first post, so see the screenshot attached.
Click to expand...
Click to collapse
S5830i only accepts a three file odin installation method. The .PDA file mentioned in the second post is also valid, but its an older firmware for s5830i. Please checkout this thread http://forum.xda-developers.com/showthread.php?t=1822109 to install latest firmware downloaded and made compatible for odin. Details are in the thread. I hope this helps and if it does don't forget the thank button

[Q] Odin 1.85 falshing fail

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.

[Fixed] First time rooting, accidentally flashed wrong ROM what to do from this point

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

[Q] Soft brick (Only Download Mode) | Stuck on Logo - HELP!

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.

Odin firmware flashing always fails

I have a Galaxy note 10.1 running kitkat 4.4.2 (GT-N8000)
Yesterday i was browsing the internet when suddenly the device decided to shut down and went on a restart boot loop where it would show the "Samsung galaxy note 10.1" screen for a while and then reboot and re-show the same screen
i have tried entering recovery mode but the tablet keeps restarting without end the only thing i can access is download mode
So recently i tried flashing using Odin but when ever i try to flash any file it shows this error
Code:
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried flashing a stock recovery so i can try and wipe the current data
I have tried to download multiple stock roms from jelly bean to kitkat which all ended up failing
I have tried flashing the tablet with a "Repair rom" which contains the BL AP CSC and Modem files
i think that if i can still access the download mode that there is some hope to recover?
Any solutions?
Thanks in advance.
If i posted this in the wrong section forgive me i have just started out