Hey there,
i need some help please.
First things first.I never flashed my S3 and i never heard of Odin and Odin mode on my S3 until sunday.
On sunday i woke up and turned on my S3 and saw that it got stuck in a boot loop.
So i searched for solutions and found a post in which clearing the cache in the android recovery system would help.
So i took out the battery, put it back in and pressed the 3 buttons to get in the system.
I was shocked when i saw red text everywhere(E:failed to mount /efs(no such file or directory);E:failed to mount /system(no such file or directory) and so on)
So i searched again and found out that you may save your phone by flashing with Odin or try an emergency recovery via Kies.
I tried to do it with KIES but it was not recognizing my S3. It also didn't recognized it via Initialising by Model name and Serial number.
Also tried to deinstall and reinstall everything with no results.But the Name of the ROM was shown there so i started to search for it on sammobile.
i found it and tried to flash it. But it didnt work. Same with other Odin Versions.
I tried 3.07,3.09,3.10 and 3.10.7 but i always get the same error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNG3_I9300DBTGNG2_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I dont know what to do. I read that you can also do it with .pit files but that this should be the last option to try.
I would appreciate some help or if i can't do anything , at least some clarity htat i need to get me a new one.
I don't know if this Information is helpful but here are the infos from Odin mode:
Product name: GT-I9300
Custom binary download: No
Current binary: Samsung Official
System status: Official
If no one can help me, i thank you though for reading this.
Vehaboman said:
Hey there,
i need some help please.
First things first.I never flashed my S3 and i never heard of Odin and Odin mode on my S3 until sunday.
On sunday i woke up and turned on my S3 and saw that it got stuck in a boot loop.
So i searched for solutions and found a post in which clearing the cache in the android recovery system would help.
So i took out the battery, put it back in and pressed the 3 buttons to get in the system.
I was shocked when i saw red text everywhere(E:failed to mount /efs(no such file or directory);E:failed to mount /system(no such file or directory) and so on)
So i searched again and found out that you may save your phone by flashing with Odin or try an emergency recovery via Kies.
I tried to do it with KIES but it was not recognizing my S3. It also didn't recognized it via Initialising by Model name and Serial number.
Also tried to deinstall and reinstall everything with no results.But the Name of the ROM was shown there so i started to search for it on sammobile.
i found it and tried to flash it. But it didnt work. Same with other Odin Versions.
I tried 3.07,3.09,3.10 and 3.10.7 but i always get the same error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNG3_I9300DBTGNG2_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I dont know what to do. I read that you can also do it with .pit files but that this should be the last option to try.
I would appreciate some help or if i can't do anything , at least some clarity htat i need to get me a new one.
I don't know if this Information is helpful but here are the infos from Odin mode:
Product name: GT-I9300
Custom binary download: No
Current binary: Samsung Official
System status: Official
If no one can help me, i thank you though for reading this.
Click to expand...
Click to collapse
Instead of clearing cache from stock recovery,do a factory reset then go into download mode i try again with Odin.
Sent from my Nexus 4 using Tapatalk
Stevica Smederevac said:
Instead of clearing cache from stock recovery,do a factory reset then go into download mode i try again with Odin.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Tried it.No success.
This is the log i get when i do the the factory reset:
--Wipe data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Formatting /cache...
E:/format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
Data wipe complete.
E:failed to mount /cache (Block device required)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Block device required)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Block device required)
E:Can't mount /cache/recovery/last install
E:Can't open /cache/recovery/last install
E:failed to mount /cache (Block device required)
The log in Odin stays the same.
Vehaboman said:
Tried it.No success.
This is the log i get when i do the the factory reset:
--Wipe data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Formatting /cache...
E:/format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
Data wipe complete.
E:failed to mount /cache (Block device required)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Block device required)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Block device required)
E:Can't mount /cache/recovery/last install
E:Can't open /cache/recovery/last install
E:failed to mount /cache (Block device required)
The log in Odin stays the same.
Click to expand...
Click to collapse
I don't want to say outloud but it's not good. I think it's time to look for a replacement phone.(i hope i am wrong)
Sent from my Nexus 4 using Tapatalk
Stevica Smederevac said:
I don't want to say outloud but it's not good. I think it's time to look for a replacement phone.(i hope i am wrong)
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Kk. Thank you for your time and replies Stevica I'll watch this thread to see if more people have the same opinion.Just to be sure.
I wish you a nice day
Vehaboman said:
Kk. Thank you for your time and replies Stevica I'll watch this thread to see if more people have the same opinion.Just to be sure.
I wish you a nice day
Click to expand...
Click to collapse
I think you are down to repartitioning the device with a suitable pit file. The way I see it, it could have been a glitch that corrupted the NAND partitions.
Depending on how ODIN works (I don't know programming), it could spit out this error if it finds no partition(s). That would not necessarily mean nothing can be written to the NAND at all.
So then you might be able to get it back working by rebuilding those partitions with the pit file. But with the corrupted EFS I doubt you can revive it to the point where you can use cell connections again...
But then again, after rebuilding the partitions, could be possible with the KIES method which might work after that... (who knows how that black magic works with the serial number and all...)
I think it's worth a shot. Just for reference, I used pit flashing once on my GT-i9000. Worked flawlessly.
Hawaiihemd said:
I think you are down to repartitioning the device with a suitable pit file. The way I see it, it could have been a glitch that corrupted the NAND partitions.
Depending on how ODIN works (I don't know programming), it could spit out this error if it finds no partition(s). That would not necessarily mean nothing can be written to the NAND at all.
So then you might be able to get it back working by rebuilding those partitions with the pit file. But with the corrupted EFS I doubt you can revive it to the point where you can use cell connections again...
But then again, after rebuilding the partitions, could be possible with the KIES method which might work after that... (who knows how that black magic works with the serial number and all...)
I think it's worth a shot. Just for reference, I used pit flashing once on my GT-i9000. Worked flawlessly.
Click to expand...
Click to collapse
Thank you for your reply Hawaiihemd You gave me new hope. Can you eventually help me to find the right pit file? Since i read that using the wrong files can be devastating.
Vehaboman said:
Thank you for your reply Hawaiihemd You gave me new hope. Can you eventually help me to find the right pit file? Since i read that using the wrong files can be devastating.
Click to expand...
Click to collapse
I'd use the pit file from here if I were you: http://forum.xda-developers.com/showpost.php?p=52911794&postcount=2
Interesting thread over all by the way... Good luck. :good:
Hawaiihemd said:
I'd use the pit file from here if I were you: http://forum.xda-developers.com/showpost.php?p=52911794&postcount=2
Interesting thread over all by the way... Good luck. :good:
Click to expand...
Click to collapse
thank you how long does it usually take to get further than "Get PIT for mapping.."?
Ok.I tried every USB port and Odin stops always at "Get PIT for mapping..".
Do you guys have some ideas what else i could try?
Vehaboman said:
Ok.I tried every USB port and Odin stops always at "Get PIT for mapping..".
Do you guys have some ideas what else i could try?
Click to expand...
Click to collapse
Have you made sure that KIES is not running sth. in the background?
I suggest uninstalling KIES (including all drivers), reboot, reinstall drivers from here, reboot and then try again running ODIN as administrator.
Hawaiihemd said:
Have you made sure that KIES is not running sth. in the background?
I suggest uninstalling KIES (including all drivers), reboot, reinstall drivers from here, reboot and then try again running ODIN as administrator.
Click to expand...
Click to collapse
Did as you suggested but still stuck at Get PIT for mapping :crying:
Do i have to use another Firmware with the PIT file?
Currently i'm using the 4.3 DBT Firmware.DO i have to download an older one?
Btw thank you so much for helping me Hawaiihemd^^
Vehaboman said:
Did as you suggested but still stuck at Get PIT for mapping :crying:
Do i have to use another Firmware with the PIT file?
Currently i'm using the 4.3 DBT Firmware.DO i have to download an older one?
Btw thank you so much for helping me Hawaiihemd^^
Click to expand...
Click to collapse
You're welcome.
AFAIK should work with every firmware for the specific device. Would you please add another post with a screenshot of your odin settings and the odin log as text? I just want to check something for confirmation. But I don't want to keep your hopes up... I think your S3 is dead.
Hawaiihemd said:
You're welcome.
AFAIK should work with every firmware for the specific device. Would you please add another post with a screenshot of your odin settings and the odin log as text? I just want to check something for confirmation. But I don't want to keep your hopes up... I think your S3 is dead.
Click to expand...
Click to collapse
Alright hopefully this will be displayed^^
and here is the text log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNG3_I9300DBTGNG2_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
Vehaboman said:
Alright hopefully this will be displayed^^
and here is the text log:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNG3_I9300DBTGNG2_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
Click to expand...
Click to collapse
First of all thanks for posting this. I'm sorry to say but my knowledge about this stuff has come to an end.
As I said before, I do not know how ODIN works behind the scenes. It just seemed logical to ME(!), that if nothing could be written to the NAND it should crash at "setting the pit file" instead of "getting pit for mapping". Maybe right, maybe wrong, no idea. I haven't seen an ODIN documentation as of yet but someone out there has to know what it does exactly... the programmer at least.
So, sorry mate, I have nothing more contructive to contribute. I hope someone can point to a documentation of some sort or can provide any more insight in any other way.
Hawaiihemd said:
First of all thanks for posting this. I'm sorry to say but my knowledge about this stuff has come to an end.
As I said before, I do not know how ODIN works behind the scenes. It just seemed logical to ME(!), that if nothing could be written to the NAND it should crash at "setting the pit file" instead of "getting pit for mapping". Maybe right, maybe wrong, no idea. I haven't seen an ODIN documentation as of yet but someone out there has to know what it does exactly... the programmer at least.
So, sorry mate, I have nothing more contructive to contribute. I hope someone can point to a documentation of some sort or can provide any more insight in any other way.
Click to expand...
Click to collapse
I gotta thank you for sticking here and trying to help me Thanks again for your time and effort
Related
Odin fails with a ROM offical or custom... A Kernal flashes with a pass. Is this bricked? I can enter download mode ok, but not upload to recovery?
The Odin log:
<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> Firmware update start..
<ID:0/017> boot.bin
<ID:0/017> NAND Write Start!!
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any advice would be greatly recieved!
Thanks
Interesting... When flashing the ROM, do you have a .PIT file + ticked Re-partition in ODIN? If not, try that.
Here's the download for stock firmware, straight from SamFirmware (XXKI3, Open Europe, 2.3.5) : http://hotfile.com/dl/130600047/b70801e/I9100XXKI3.rar.html
Phistachio said:
Interesting... When flashing the ROM, do you have a .PIT file + ticked Re-partition in ODIN? If not, try that.
Click to expand...
Click to collapse
I have found a PIT file ~ u1_02_20110310_emmc_EXT4.pit I don't know where it came from though? it exists in a folder on my desktop where Odin is placed. Do you think that will be safe?
I've never flashed with Re-partition ticked in odin. I've read that is dangerous. Is this defo safe to do?
Thanks
mwatson said:
I have found a PIT file ~ u1_02_20110310_emmc_EXT4.pit I don't know where it came from though? it exists in a folder on my desktop where Odin is placed. Do you think that will be safe?
I've never flashed with Re-partition ticked in odin. I've read that is dangerous. Is this defo safe to do?
Thanks
Click to expand...
Click to collapse
Yes, it is dangerous when you don't know what you're doing. Be VERY careful when around .PITs.
But I have soft bricked my GSII 3 times, and I have flashed KH3 recovery package thrice, WITH the .PIT. The .PIT is just to be as fresh and stock as possible.
Download the package I gave you. But also, what are you trying to flash?
Just to be safe, don't use the .PIT that you "found". The name's the same as in the pack I gave you, but better than than sorry
Phistachio said:
Yes, it is dangerous when you don't know what you're doing. Be VERY careful when around .PITs.
But I have soft bricked my GSII 3 times, and I have flashed KH3 recovery package thrice, WITH the .PIT. The .PIT is just to be as fresh and stock as possible.
Download the package I gave you. But also, what are you trying to flash?
Click to expand...
Click to collapse
I was trying to flash stock
GT-I9100_XEU_I9100XWKF3_I9100XXKE7_I9100XEUKD1.TAR in PDA
I'm just downloading the file you posted. Will this package include the PIT?
Thanks for your help!
mwatson said:
I was trying to flash stock
GT-I9100_XEU_I9100XWKF3_I9100XXKE7_I9100XEUKD1.TAR in PDA
I'm just downloading the file you posted. Will this package include the PIT?
Thanks for your help!
Click to expand...
Click to collapse
Anytime
Yes, it will include the .PIT, aswel as MODEM, CODE and CSC (which should be multi).
Also, just to make sure, uninstall KIES. It may interfere on the flashing process + it's useless
Phistachio said:
Anytime
Yes, it will include the .PIT, aswel as MODEM, CODE and CSC (which should be multi).
Click to expand...
Click to collapse
9 mins to go till the file has downloaded...
So just to be sure i need to flash the PIT, Modem, Code and CSC all together with re-partition ticked?
mwatson said:
9 mins to go till the file has downloaded...
So just to be sure i need to flash the PIT, Modem, Code and CSC all together with re-partition ticked?
Click to expand...
Click to collapse
Yes Do you know where to place each one of them? Let's hope it doesn't end up hard bricked
But before you do ANYTHING, can you go into recovery mode (vol. up+home+power)? If so try to wipe user data and cache.
If that doesn't work, try to normally turn on, and if it bootloops, remove the battery.
PS : I am not liable to any damage that may occur Although I've tested myself and all went OK (With KH3, but it's mainly the same thing )
yeah i know where to put them. I can't enter recovery though. It just loops on boot screen. Will this be a problem if i can't wipe data?
Downloaded file asking for a password?
mwatson said:
yeah i know where to put them. I can't enter recovery though. It just loops on boot screen. Will this be a problem if i can't wipe data?
Click to expand...
Click to collapse
Nope, because the .PIT + Re partition will do the job
ok.. neraly there.. Downloaded file asking for a password?
mwatson said:
ok.. neraly there.. Downloaded file asking for a password?
Click to expand...
Click to collapse
I believe it is samfirmware.com
Good luck!
Bugger failed again!
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100-CSC-MULTI-OXAKI3.tar.md5 is valid.
<OSM> MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5 is valid.
<OSM> CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> cache.img
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I guess this is just good for spare now... or a paperweight!
mwatson said:
Bugger failed again!
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100-CSC-MULTI-OXAKI3.tar.md5 is valid.
<OSM> MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5 is valid.
<OSM> CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> cache.img
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I guess this is just good for spare now... or a paperweight!
Click to expand...
Click to collapse
Now this is weird... I have never seen a flash failed when using a .PIT...
I'm sorry to say this, but I think your GSII is hard bricked... Try to flash another 2 times, the same thing.
What it seems is that the NAND got corrupted somehow... And isn't letting ODIN flash properly...
Just tried another couple of times and still no good.
Obrigado pela vossa ajuda. Feliz Ano Novo!
mwatson said:
Just tried another couple of times and still no good.
Obrigado pela vossa ajuda. Feliz Ano Novo!
Click to expand...
Click to collapse
The last thing that comes to mind is... To flash a stock kernel (preferably KI3 Stock Kernel) from Intratech's thread. If successful, flash the the recovery package again. If unsuccessful, as a last resort, flash the old bootloader provided in his thread aswell (follow his instructions!), and if successful, flash the KI3 package I gave you again. That may screw up the GSII's mind and make it work
As it is unfortunately hard bricked, I'm giving out all options that come to my mind
De nada ! I wish you a joyful new year aswell
In a less confusing manner :
1. Flash KI3 Stock Kernel from Intratech'a thread.
2. Flash Recovery package
3. If recovery package is not flashed, re flash the stock kernel
4. Flash old bootloader provided in the same thread
5. If it boots, then yay. If not :
6. Re flash the recovery package.
With that "guide", I want to exploit the fact that you can root a kernel, so if you root a stock kernel, you get lucky...
Also, are you sure you put the stuff in the right place? .PIT -> PIT, Code -> PDA, Modem -> Phone, CSC -> CSC and ticked Re-partition, Auto Reset and F.Timer reset (irst 3)
Yep.. thats what i did.. Screen shot for you in case you can spot anything? Defo kies not running as you can see from the screen shot.
The phone still goes into download mode though?
Use a different USB port on your PC. Try to use one of the Ports on the rear of your case and not the ones on the front or top of the case.
Sleepycat3 said:
Use a different USB port on your PC. Try to use one of the Ports on the rear of your case and not the ones on the front or top of the case.
Click to expand...
Click to collapse
Tried different ports. Still no luck.. During the flash process is tries to boot the goes to fail.
It not like i can send this back as it has a count of 7 custom downloads.
thanks
Hello. Firstly i bought my galaxy s2 two month ago. Well my phone gave me some errors. I think its about some system application then my imei number deleted. Well this time i searched some answer for this problem and i found this site. i checked some thread and i like this site. Everyones polite and have real knowledge about somethink.
Now i root my phone with one click root. Then use GSII_Repair app from market then my imei come again.( In descrition = If your sim card not detected, no signal or your efs folder blocked on read_only) But after that my phone start gave same errors, imei deleted and stuck at s2 logo when start or try open recovery mod. I try root again cause of i unroot before. When i flash with insecure kernel and odin 1.85 ( i take from this site, same from first used ) its stuck in nand write. I remove from pc and try several times try another rom, kernel, stock rom...
After that flash with bootloader its stuck in nand write. Then flash with xwki4 kernel its pass. as i read, i need flast it with repartition and pit file. For this i flash with recovery file ( have modem, code, csc, pit ) then again stuck in nand write. At the and when i try to open phone or recovery, i see error about firmware. Download mode still work. Odin still detect my phone. I try heimdall but it doesnt detect my phone. So im so tired, sorry about spelling etc. So its hard brick or not. Thanks for everyone.
[GUIDE] Fix an unflashable or soft bricked GSII.
Thanks for your answer but i already use this method it stuck. This didnt solve my problem.
Try to flash a 2.3.3 firmware.Also change your com port and try a different one.If you dont have recovery it sounds like you need to repartion (pit file) but thats a dangerous thing to do with a faulty phone.A 2.3.3 firmware will have the old 4 file package but thats something you must choose to do at your own risk.
i will try but im sure it doesnt solve my problem. I think my device dont let write anything on memory.
Now when i chance my com port it stuck in
<ID:0/021> Added!!
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Initialzation..
<ID:0/021> Get PIT for mapping..
<ID:0/021> Firmware update start..
<ID:0/021> boot.bin
<ID:0/021> NAND Write Start!!
<ID:0/021> cache.img
Try another pc or usb slot.
Sent from my GT-I9100 using xda premium
Try it now i can flash it with kernel, bootloader ( still cant with pit file), i see my batery indicator, when i try to open recovery menu phone dont mount efs file. I dont understand odin say
<ID:0/021> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5 is valid.
<OSM> GT-I9100-CSC-MULTI-OXAKI3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Initialzation..
<ID:0/021> Set PIT file..
<ID:0/021> DO NOT TURN OFF TARGET!!
It might be a long shot but try and flash this via Odin and see what happens.
http://forum.xda-developers.com/showthread.php?t=1095274
Once again at your own risk.
After flash with pit file ( after a several try. also code, modem,csc ) i see some error in recovery mode.
Appling Multi-CSC
E:failed to mouth /efs ( Invalid argument)
E: multi_csc:Can't mount /efs
Multi-csc applied failed.
What does it mean?
Tearael said:
After flash with pit file ( after a several try. also code, modem,csc ) i see some error in recovery mode.
Appling Multi-CSC
E:failed to mouth /efs ( Invalid argument)
E: multi_csc:Can't mount /efs
Multi-csc applied failed.
What does it mean?
Click to expand...
Click to collapse
Right so now I imagine the flash has worked and you have a firmware?!.
The first E:fail about efs is because your imei number is corrupt or wiped and is found in your efs folder.To check type *#06# on your phone and if you imei is blank or not the same as the one behind the baterry then thats why.
The second E:fail about CSC (country sales code) will most likely be related to the first.If you are able to access the market then download Nitrality.It has an option to open the CSC list to change to your region.This will factory reset your phone.If you cant access the market you could flash a custom ROM with a multi CSC package but this doesnt make much sense until you get your original IMEI number back.This number controls everything.You could search here for restore methods or contact XDA member ODIA who can restore it for you for a donation.Apart from that its a service centre job.If you have a warranty then flash your countries stock ROM and say KIES screwed it up and see if they will do it for free,but if not,best bet would be ODIA although there are alot of restore methods floating around.Some work some dont.Its a case of try and try again....and another...and again.
Hello, I do not remember what was the solution I came(I had exactly the same problem) but I can only encourage you and tell you that I had to try many methods and attempts but finally with a lot of patience it works. Good luck..and if you find the way to fix it,it will be nice if you'l share it here in your thread.
Hi, so my galaxy s2 is simply stuck at the boot screen now and refuses to start up. I'll try to list down in as much detail as i can what i did to help you help me
Things i did before this happened:
1) I was on a nightly build of cm9 which was working fine
2) Attempted to upgrade to the latest stable version of cm9
3) Flashed the cm9 zip through cwm in recovery mode
4) Rebooted the system
5) Application optimization thingy got stuck at some application 104
6) I kinda fell asleep, leaving the phone to run until it drained all 80% of the battery on that optimization thingamajig
7) Woke up and realized that starting up the phone won't go past the boot screen
Things i tried after it happened:
1) Booted into cwm recovery and attempted to wipe the cache, but after a few minutes of getting stuck there, the phone just restarted itself and went back to the boot screen.
2) Booted into cwm recovery and attempted to do a wipe data/factory reset but the same thing happened like the cache wipe
- not sure if this means anything as well but when i go into recovery mode of CWM, the following messages appear
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
3) Downloaded the stock rom DXLP9 (from http://forum.xda-developers.com/showthread.php?t=1075278) and attempted to flash it through Odin but that failed.
- the following are the messages printed by Odin
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_SIN_I9100DXLP9_I9100OLBLP9_I9100DXLP9.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> boot.bin
<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!!
I had to wait about 15minutes before the "Complete(Write) operation failed." message came out.
So i poked around looking for a solution but being the utter noob that i am, have not tried anything else for fear of ending up with an expensive paper weight.
It'll be great if anyone can help me access my situation or guiding me in any additional steps to determine my current situation so that i can apply the correct solution. But of course, solutions are more than welcome
Do you know if you have faulty emmc chip on board? This look like nand error after wiping. Cache partition unreadable.
Have you tried to flash with repartition?
i9.0.1.3k galaxy imperator
i'm not sure about what an emmc chip is so i wouldn't know if it's faulty.
By flash with partition, does it mean that i simply check the repartition option when flashing in odin? Cause i read a few guides which state that if the zip file only contains a single file and not the separate modem and code files, not to check the repartition option. So should i go ahead and try it still?
Still trying to learn as i go along so sorry for the noobness
Better to learn before starting.
Sent from my GT-I9100 using xda premium
that is indeed true but i believe the situation has to do more with learning from mistakes?
just found out about the faulty emmc chip issue, but is there any way to determine if it is faulty since i am unable to run any apps that check it?
mylittleponies said:
just found out about the faulty emmc chip issue, but is there any way to determine if it is faulty since i am unable to run any apps that check it?
Click to expand...
Click to collapse
Do you still gave access to cwm recovery?
Swyped from my Galaxy SII
yes i do, but it seems that any operation i perform on it causes the phone to restart and get stuck at the samsung boot screen.
attempting to mount USB storage results in the error Unable to write to ums lunfile (No such file or directory)
CWM recovery v6.0.1.1
mylittleponies said:
yes i do, but it seems that any operation i perform on it causes the phone to restart and get stuck at the samsung boot screen.
attempting to mount USB storage results in the error Unable to write to ums lunfile (No such file or directory)
CWM recovery v6.0.1.1
Click to expand...
Click to collapse
1.What steps have you taken, that failed in CWM recovery?
2. Do you mind upgrading to ICS?
Swyped from my Galaxy SII
not so sure about what you mean by steps taken. attempting to wipe cache, wipe data factory reset, or installing zips from the internal SD will cause the phone to restart automatically and get stuck at the samsung logo boot screen. All these occurred after flashing the latest stable version of cyanogenmod9 which loaded to the part where it tried to "optimize app 104 of 127" or something. it apprently got stuck there until the phone battery ran out and after that i've never gotten past the samsung boot screen anymore.
i'm okay with using ICS, honestly anything goes right now as long as i can see my beloved home screen again haha
just need some advice, would a flash with repartition using a pit file be recommended for such a situation?
Hi Guys.
I uninstalled some apps on my rooted I9300 and went to bed. When i woke up, the boot logo was stuck.
The only thing i can access is Download-mode (Volume-down + Home + Power).
I think the only way to get my phone up and running again, is through Odin (please correct me if I'm wrong)
What i have tried to resolve the issue:
- Tried downloading stock firmware from Sammobile.com and adding it in Odin v1.85, v3.04 and v3.07: Result: There is no PIT partition. v3.07 stopped at "SetupConnection.."
- Tried downloading rescue firmware here: http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6. The package included Bootloader, PDA, PHONE and CSC files. Tried running them through Odin, first with "Re-Partition" unticked - Failed. Then i tried with "Re-partition" ticked, and got this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXDLJ4_368423_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXDLID_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_BTU_I9300OXADLJ4_368423_MULTI_user_low_ship.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
- I tried downloading KIES, to check if my phone connected, but it doesn't.
I just need to access CWM recovery so i can install a ROM, but when I hold Volume Up + Power, it shows the boot logo after a while and it stays there..
Im fairly new to Android, but I hope you guys have some tips for me.
This thread looks like a similar problem
http://forum.xda-developers.com/showthread.php?t=1785481
maatsby said:
This thread looks like a similar problem
http://forum.xda-developers.com/showthread.php?t=1785481
Click to expand...
Click to collapse
I can't find a solution in this thead. The firmware i downloaded from Sammobile.com did not include a .pit file, just one large tar.md5 file.
When using this in Odin i get the "There is no PIT partition" error.
nubz2k said:
I can't find a solution in this thead. The firmware i downloaded from Sammobile.com did not include a .pit file, just one large tar.md5 file.
When using this in Odin i get the "There is no PIT partition" error.
Click to expand...
Click to collapse
What's inside the tar file? Can you extract it and put each of the separate bits in to their own boxes in odin?
---------- Post added at 10:44 PM ---------- Previous post was at 10:41 PM ----------
You said you're keen to just get in to recovery, can u flash a recovery in odin and then use adb commands to get there? adb reboot recovery
http://forum.xda-developers.com/showthread.php?t=1796062
maatsby said:
What's inside the tar file? Can you extract it and put each of the separate bits in to their own boxes in odin?
You said you're keen to just get in to recovery, can u flash a recovery in odin and then use adb commands to get there? adb reboot recovery
Click to expand...
Click to collapse
Tried flashing Recovery-clockwoork...-i9300.tar now, but it keeps saying that there is no PIT partition
<ID:0/003> Added!!
<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>
<ID:0/003> There is no PIT partition.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
As far as I know, there is no point to adb without a recovery to boot?
What's inside the tar file? Can you extract it and put each of the separate bits in to their own boxes in odin?
Click to expand...
Click to collapse
Just a bunch of folders. Nothing looks like something i can put in Odin's boxes.
JJEGAN:
Can't extract the PIT file with Heimdall
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
Click to expand...
Click to collapse
nubz2k said:
Just a bunch of folders. Nothing looks like something i can put in Odin's boxes.
JJEGAN:
Can't extract the PIT file with Heimdall
Click to expand...
Click to collapse
Probably supposed to flash the three parts dont know i steer clear of Pits .
jje
JJEgan said:
Probably supposed to flash the three parts dont know i steer clear of Pits .
jje
Click to expand...
Click to collapse
The rescue firmware i downloaded included 3 parts + PIT file, but when i try to flash just the 3 parts, without the PIT, it fails.
Giving up! I've read through countless forums, and no one has a solution as long as the "Re-Partition operation failed." error shows in Odin.
RMA'ing the phone tomorrow.:crying:
Try firmware initialzation within KIES. You will be prompted for the model and serial number and voilá!!!! New
Flashing going under it's way!!!
Sent from my GT-I9300 using xda premium
worf_1977 said:
Try firmware initialzation within KIES. You will be prompted for the model and serial number and voilá!!!! New
Flashing going under it's way!!!
Click to expand...
Click to collapse
My device isn't recognized by KIES while in downloading mode. Is it supposed to? I've tried downloading the drivers, different cables and pc's.
Got any tips on how to get KIES to detect my phone?
Try re installing USB Drivers for samsung phones...
Sent from my GT-I9300 using xda premium
worf_1977 said:
Try re installing USB Drivers for samsung phones...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Tried it. The drivers are installed. Odin and Heimdall detects it, but KIES doesn't.
Then try to follow firmware initialization steps, and then, and only then, connect the phone... It will look for your terminal in download mode and update it.
Sent from my GT-I9300 using xda premium
worf_1977 said:
Then try to follow firmware initialization steps, and then, and only then, connect the phone... It will look for your terminal in download mode and update it.
Click to expand...
Click to collapse
Tried it. KIES downloads the firmware and fails at apx 69% telling me that "firmware initialization failed".
send it in
Already packed and ready for shipment.
Update:
The service department stated that they had to replace the mainboard on my phone.
I don't know if they noticed that the device was rooted and had a custom ROM, but it was covered by warranty and they are sending it back with no charge
How lucky you are then!!! Congrats and enjoy the new phone, whenever arrives
Sent from my GT-I9300 using xda premium
This is my first thread, so hello!
Me and my sister both have a S5839i, and my sisters just randomly bricked, and it is on a boot loop.
I have tried EVERYTHING online- recovery mode, downloading firmware with odin...you name it.
I have used the totoro_0623.pit file, and on Odin, it said it passed. But then trying with all the other firmware, it didn't work.
Yes, I am using the right version of Odin, and I don't have Kies running at the same time as Odin.
This is what happens when I put S5839IBULL1_S5839IVD2LH1_VD2.tar.md5 into the PDA section in Odin. This is the Germany Vodafone firmware, someone else posted in the forums. I have tried the UK one with the 3 network (what my region and network is) , but that doesn't work either, and comes up with the same thing in Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5839iBULL1_S5839iVD2LH1_S5839iBULK1_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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> BcmCP.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I just stupid, and have missed something, or is there another way? Please note : The phone is not modded in anyway, not even rooted, but the warranty has run out.
Thankyou
KizzleKat said:
This is my first thread, so hello!
Me and my sister both have a S5839i, and my sisters just randomly bricked, and it is on a boot loop.
I have tried EVERYTHING online- recovery mode, downloading firmware with odin...you name it.
I have used the totoro_0623.pit file, and on Odin, it said it passed. But then trying with all the other firmware, it didn't work.
Yes, I am using the right version of Odin, and I don't have Kies running at the same time as Odin.
This is what happens when I put S5839IBULL1_S5839IVD2LH1_VD2.tar.md5 into the PDA section in Odin. This is the Germany Vodafone firmware, someone else posted in the forums. I have tried the UK one with the 3 network (what my region and network is) , but that doesn't work either, and comes up with the same thing in Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5839iBULL1_S5839iVD2LH1_S5839iBULK1_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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> BcmCP.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I just stupid, and have missed something, or is there another way? Please note : The phone is not modded in anyway, not even rooted, but the warranty has run out.
Thankyou
Click to expand...
Click to collapse
Get the official firmware needed on Sammobile.com, you need an account on there. Don't worry it's free. Flash it as PDA on Odin. Make sure your phone is in download mode (volume up+volume down+power). If it boots, the boot animation might start looping. From theres you can access recovery (volume up+power+home). In recovery you wipe data and wipe cache and select reboot. It should work.
Sent from my GT-I8190N using Tapatalk
Hi
Don't panic !
Is not a brick, but Odin doesn't support one file (PDA) package.
You need to use Odinatrix to create a 3 files firmware or download a 3 files firmwares
Galaxy_Ace_Love said:
Hi
Don't panic !
Is not a brick, but Odin doesn't support one file (PDA) package.
You need to use Odinatrix to create a 3 files firmware or download a 3 files firmwares
Click to expand...
Click to collapse
Odin 3.07 supports one file package
Humm...
iamareebjamal said:
Odin 3.07 supports one file package
Click to expand...
Click to collapse
I used Odin 3.07, and that worked... but when the phone loaded and installed - it said "Failed to mount /data (invalid argument)" and continued to boot loop. I thought by installing the firmware and re-partitioning it would fix that :/
KizzleKat said:
I used Odin 3.07, and that worked... but when the phone loaded and installed - it said "Failed to mount /data (invalid argument)" and continued to boot loop. I thought by installing the firmware and re-partitioning it would fix that :/
Click to expand...
Click to collapse
Format the data
Put the pit file and tick Repartition. And then flash with Odin.
And you have to use Cooperve pit, not Totoro, it's for SGY
Yeah, I have ticked the re-partion and stuff. Apparently totoro works with Ace as well? All the tutorials say that...
I will still try though
Edit: Tried and still no luck....
Sent from my GT-S5839i using xda app-developers app
KizzleKat said:
Yeah, I have ticked the re-partion and stuff. Apparently totoro works with Ace as well? All the tutorials say that...
I will still try though
Edit: Tried and still no luck....
Sent from my GT-S5839i using xda app-developers app
Click to expand...
Click to collapse
Follow these Guidehttp://forum.xda-developers.com/showthread.php?t=1840645
Sent from my GT-S5830i using Tapatalk 2