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.
Related
hey guys, had the gs2 a few months now and decided to root it tonight.
plan back fired. stuck with the samsung logo and the ! symbol.
original info:
GT-I9100
2.3.3
I9100NEKF2
2.6.35.7-I9100XWKF4-CL280512
[email protected]#2
Gingerbread.XWKF4
Click to expand...
Click to collapse
CF-Root-SGS2_ZS_OZS_KF4-v4.0-CWM4
is what i tried to flash this with (odin).
Went through all the steps. flashed, blue bar came across. said success in ODIN. Phone rebooted but wont get past the ! screen.
have tried flashing with I9100XWKF4_Kernel and tried reflashing with CF-Root-SGS2_ZS_OZS_KF4-v4.0-CWM4, Both result in same issue (phone stuck on boot screen with ! symbol).
Any ideas on where ive gone wrong? or possibly a way to resolve this?
Thanks again
rossonza
can you enter download or recovery mode? (volume up + home + power // volume down + home + power)
If you can go in recovery, wipe data/cache factory reset + wipe cache + advanced and wipe dalvik cache.
Mount usb storage and put in your internal memory a rom (like batista or villain rom or checkrom your choice, i use batista) flash that one and reboot.
If you can only go in download mode, try to flash the lite'ning 6.1 (KH3) rom, be sure to DONT check repartition (that will brick your phone).
The lite'ning already contains root (no need to use cf-root before) so if you can enter download mode, it's a good choice to "unlock" (hopefully it works) your phone.
i can get into download mode still but cant get into recovery (never could?)
downloading that rom now. big download :S
Well, the rooting process didnt worked well if you cant even enter recovery (that comes with the rooted kernel).
Keep me informed if you can fix the problem.
I forgot to tell you, you can also flash from download (maybe you prefer) a stock original rom (from this forum, S2 Android Original Development) so you get back to the stock rom (without root).
im downloading both the custom liteneing rom and the stock firmware. Ill let you know how it goes.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Litening_Rom_v6-1.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> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Litening wont flash.
<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> Sbl.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
GT-I9100_H3G_I9100XWKF4_I9100NEKF2_I9100H3GKF1
That's not looking bright.
Im sure it can be fixed since you can enter dw mode and Odin finds / connect at the phone.
Try with the stock one, if also that one isnt working, you need a more experienced advice from a "veteran" of the forum
Stock not flashing either, both failed :S
really hope i havnt destroyed this phone. nexus one was a breeze to root.
phone gets into download mode no issues and ODIN picks it up.
rossonza said:
i can get into download mode still but cant get into recovery (never could?)
downloading that rom now. big download :S
Click to expand...
Click to collapse
If (never could?) means also on stock firmware then this was the first mistake.You need to try and flash your original FW (or another from XDA if your phone is unlocked) to get recovery.Without it you wont root or install ROMs.
http://www.multiupload.com/N5RWCXT1LJ
i imagine youve already got it but stick it in pda and try it.It might take a few trys but give it few goes.I had an i9000 jtaged that came back without recovery mode and it took me a few failed attempts before it finally passed and rebooted with recovery and then your away laughing.
and if it continues to fail? jig and return to samsung? or will this be covered under my 3 contract..
If your download count (download mode) is set to 0, it is covered by your warranty.. if it's more than 0, you need a jig to set it to 0.
Kinda strange problem you got here, phone is not bricked (since odin find it and you can access dw mode) but looks like it refuse any kind of firmware.
Anyone else a suggestion? im sure big names of the forum can help out a bit here...
rossonza said:
and if it continues to fail? jig and return to samsung? or will this be covered under my 3 contract..
Click to expand...
Click to collapse
Heres the problem with the return idea.If the symbol on the screen is the classic "PHONE...!...PC" icon then its a semi-bricked icon and if your bin counter is at 0 then samsung are your better choice but 3 might not be abligated to take it back as this sign clearly means a PC-Phone connection problem and not a software problem alone.If the icon on your screen is a big yellow triangle with the ! inside then samsung can refuse to take the phone back even if your bin counter is at 0 cos this is a special warning sign put but samsung to see if you have been screwing with your phone outside of your warranty.If its the big yellow one then keep trying to flash and if nothing works then pay 30 or 40 bucks to get a jtag done.Because you can get into download mode I see no reason at the moment why it wont flash Use the firmware from XDA dont forget.IT worked for me with their PDA flashes and not the samfirmware files with pit files.Dont use pit files and try a more reciente FW if your phone is unlocked as i said ealier.If you want try the samfirmware file that gives you the 3 files instead of one(without pit but use odin 1.85 from here http://forum.xda-developers.com/showthread.php?t=1075278
PDA/PHONE/CSC and see what happens.give everything a try.
try this if you want.Its XWKE1 multi CSC H3GKD4 from May.Thought it might help cos its an H3G brand firmware like on your phone.If it works then yourll get back recovery and then can flash what ever you want again.Worth a try.BUT use Odin from XDA (1.85) and no pit file and dont tick re-partition.PDA/PHONE/CSC
password is samfirmware.com
http://hotfile.com/dl/119477273/436e381/I9100XWKE1_H3GKD4_NEKD5.rar.html
rossonza said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Litening_Rom_v6-1.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> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Litening wont flash.
Click to expand...
Click to collapse
You can't flash a custom rom with odin.
You need CMW.
That's why failed.
Red_Vex said:
You can't flash a custom rom with odin.
You need CMW.
That's why failed.
Click to expand...
Click to collapse
Wrong, Lite'ning package is a ODIN package, not a clockworkmod package, i did flash the rom 3-4 times in the last 2 months with odin.
keep trying to flash, but its failing. may be a gonner :S i always read that its not bricked if you can get to download mode. guess this is wrong?
im getting no phone to PC error. so is all ok?
Download mode shows current binary as custom
6 counts of flashing the device.
rossonza said:
keep trying to flash, but its failing. may be a gonner :S i always read that its not bricked if you can get to download mode. guess this is wrong?
im getting no phone to PC error. so is all ok?
Download mode shows current binary as custom
6 counts of flashing the device.
Click to expand...
Click to collapse
Download mode does not mean its bricked or not bricked it just means on a bricked phone you stand a chance of recovery but that depends upon a number of factors the principle one in all this flashing is the user .
It may that multiple flashings have messed up or that the wrong firmware has been flashed .
My steps would be .
One reset rom counter with USB jig to clear for warranty.
Two Recovery mode Mounts and storage Format data cache system dalvik and sd card .
Power off boot to download mode and flash a full stock rom via Odin .
Do not use any firmware you have already used .
jje
recovery mode isnt available so cant mount.
anyone else care to input?
cooza said:
Heres the problem with the return idea.If the symbol on the screen is the classic "PHONE...!...PC" icon then its a semi-bricked icon and if your bin counter is at 0 then samsung are your better choice but 3 might not be abligated to take it back as this sign clearly means a PC-Phone connection problem and not a software problem alone.If the icon on your screen is a big yellow triangle with the ! inside then samsung can refuse to take the phone back even if your bin counter is at 0 cos this is a special warning sign put but samsung to see if you have been screwing with your phone outside of your warranty.If its the big yellow one then keep trying to flash and if nothing works then pay 30 or 40 bucks to get a jtag done.Because you can get into download mode I see no reason at the moment why it wont flash Use the firmware from XDA dont forget.IT worked for me with their PDA flashes and not the samfirmware files with pit files.Dont use pit files and try a more reciente FW if your phone is unlocked as i said ealier.If you want try the samfirmware file that gives you the 3 files instead of one(without pit but use odin 1.85 from here http://forum.xda-developers.com/showthread.php?t=1075278
PDA/PHONE/CSC and see what happens.give everything a try.
try this if you want.Its XWKE1 multi CSC H3GKD4 from May.Thought it might help cos its an H3G brand firmware like on your phone.If it works then yourll get back recovery and then can flash what ever you want again.Worth a try.BUT use Odin from XDA (1.85) and no pit file and dont tick re-partition.PDA/PHONE/CSC
password is samfirmware.com
http://hotfile.com/dl/119477273/436e381/I9100XWKE1_H3GKD4_NEKD5.rar.html
Click to expand...
Click to collapse
Thanks that firmware fails, Whats a JTAG?
i dont mind paying to get this fixed if thats what it comes to.
cheers
Why not try to re-install the drivers?
I got problem flashing the rom, but rectified it after re-installing the drivers.
May help u.
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
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
.pit file needed, Samsung Galaxy SHV-E210k 16GB, stuck on "Nand write start"
my galaxy s3 is stuck. it still can go to download mode by pressing volume down+home+ power button.
but in recovery mode it says "E: Failed to mount / system no such file or directory"
and when i tried to flash official rom with odin it says failed after Nand Write Start... please help me anyone i am very upset.
hence i have searched for pit file for my samsung galaxy s3 (SHV-E210k) 16 GB but i could not find this file so please help me, anyone who have pit file for this device or who is able to extract pit from running device.
What file is failing to flash? The Odin log may help determine the problem?
Tried using different USB cables and USB ports?
Screenshot added and odin log.
audit13 said:
What file is failing to flash? The Odin log may help determine the problem?
Tried using different USB cables and USB ports?
Click to expand...
Click to collapse
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> E210KKTUKOA1_E210KKTTKOA1_E210KKTUKNK4_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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please help.
The sboot.bin file is the bootloader. It's not flashing because the bootloader is not for your phone, the bootloader in the ROM is older than the bootloader in the phone, you need to try different USB cables, or different USB ports.
A pit file will not help because Odin is able to get the proper partition information from the phone.
audit13 said:
The sboot.bin file is the bootloader. It's not flashing because the bootloader is not for your phone, the bootloader in the ROM is older than the bootloader in the phone, you need to try different USB cables, or different USB ports.
A pit file will not help because Odin is able to get the proper partition information from the phone.
Click to expand...
Click to collapse
Should i download the other version of firmware or only i have to try bootloader file?
I have already tried different cables and USB ports.
I have also tried to flash Philz recovery it give error after " Nand Write Start ",
I cannot reset data from recovery mode because it says unable to mount no such file or directory.
please tell me the right steps to follow.
Download the latest ROM for the phone from updato.com or sammobile.com.
Recovery mode
audit13 said:
Download the latest ROM for the phone from updato.com or sammobile.com.
Click to expand...
Click to collapse
In recovery mode these errors are showing.
Can you tell me about that why these error are coming and why my mobile can't mount all storage like system, cache, recovery.
It's possible that the memory chip inside the phone is damaged.
If you can't flash a stock ROM using Odin, you can try finding a cell repair shop that can flash the ROM using a jtag cable or Octopus box.
audit13 said:
It's possible that the memory chip inside the phone is damaged.
If you can't flash a stock ROM using Odin, you can try finding a cell repair shop that can flash the ROM using a jtag cable or Octopus box.
Click to expand...
Click to collapse
Ohh ok
Stuck logo on olleh on s3 Korean
Hi everyone my galaxy s3 Korean set stuck on logo. I flash two official firmware from updato.com with odin but still stuck on logo . Plz help me out.
Amrit thapa4012 said:
Hi everyone my galaxy s3 Korean set stuck on logo. I flash two official firmware from updato.com with odin but still stuck on logo . Plz help me out.
Click to expand...
Click to collapse
After flashing the stock ROM, are you booting into recovery to perform a factory wipe?
hi any luck with this? i have my phone having similar issues with this failed to mount on all directories. any help will do.
First of all sorry for bad english
I cannot flash anything because of this error and also when i press the power button it says: ''Firmware upgrade encountered an issue.Please select recovery mode in kies and try again'' i think pit partition is also problem. I was using custom ROM and i cannot open recovery mode neither help me guys it is the error log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELLB_I9300OJVELL3_I9300XXELLA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
SOLUTION:
I solve the problem i just simply renew the phone's root and then flashed a firmware now there is no problem and thanks for the reply
If you have "re-partition" ticked in odin, untick it.
Are you absolutely sure that the firmware you're flashing is correct for that variant?. Have you tried recovery via kies?.
If yes to all then you might have to find a pit file and flash it because it is trying to re-partition the nand, could be corrupt.
shivadow said:
If you have "re-partition" ticked in odin, untick it.
Are you absolutely sure that the firmware you're flashing is correct for that variant?. Have you tried recovery via kies?.
If yes to all then you might have to find a pit file and flash it because it is trying to re-partition the nand, could be corrupt.
Click to expand...
Click to collapse
Yes i tried to untick it but then it couldnt find pit file.
I'm certain that i downloaded the right firmware. And i tried with 3 other firmware as well.
I tried kies but i couldnt do it because it couldnt connect the phone.
And lastly i tried 4 other pit files but result is same where can i find the right pit file i think it is the problem. By the way last night i could flashed twrp recovery but i couldnt open it. When i tried to it open twrp it opened download mode. And it is the important part: i could not FLASHED AGAIN just happened once odin always keep stuck at "set partition" with "GET MAPPING FOR PIT..." step.
Try a pit file WITH the firmware in odin and see how far that gets..
Read post #1 here: https://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
shivadow said:
Try a pit file WITH the firmware in odin and see how far that gets..
Read post #1 here: https://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
Click to expand...
Click to collapse
Thank you but i solved it.
Guillotine35 said:
SOLUTION:
I solve the problem i just simply renew the phone's root and then flashed a firmware now there is no problem and thanks for the reply
Click to expand...
Click to collapse
Hai, can you tell me how to renew phone root?
iki_sure said:
Hai, can you tell me how to renew phone root?
Click to expand...
Click to collapse
You just have to root phone here it's explanation:
https://forum.xda-developers.com/showthread.php?t=2499904
Guillotine35 said:
Thank you but i solved it.
Click to expand...
Click to collapse
How did you solve it?
aki001 said:
How did you solve it?
Click to expand...
Click to collapse
hi Brother i am getting same issue can you tell me how you fix this issue partitino error
masu222 said:
hi Brother i am getting same issue can you tell me how you fix this issue partitino error
Click to expand...
Click to collapse
same error - Tab A 2016 - SM-T580.
I would be grateful for any help here .. i unticked & ticked the re-partition but same result
samsung sm-T580 pit partition error in odin
I try to update my sm-t580 to android 9.0 by using firmwere . I was did with odin flash. After that my tab is not start normaly. I plug my charger and my tab show boot screen and say invailed kernel length. There is no recovery mode only download mode is ok. But when i try to flash any firm were like 6.0 ,7.0 or 8.0 odin failed with massage there is no pit partition.:crying: Help me out plz .
bornoamit said:
I try to update my sm-t580 to android 9.0 by using firmwere . I was did with odin flash. After that my tab is not start normaly. I plug my charger and my tab show boot screen and say invailed kernel length. There is no recovery mode only download mode is ok. But when i try to flash any firm were like 6.0 ,7.0 or 8.0 odin failed with massage there is no pit partition.:crying: Help me out plz .
Click to expand...
Click to collapse
wrong thread, search in the section for your device
I have this problem too!
guillotine35 said:
first of all sorry for bad english
i cannot flash anything because of this error and also when i press the power button it says: ''firmware upgrade encountered an issue.please select recovery mode in kies and try again'' i think pit partition is also problem. I was using custom rom and i cannot open recovery mode neither help me guys it is the error log:
<id:0/004> added!!
<osm> enter cs for md5..
<osm> check md5.. Do not unplug the cable..
<osm> please wait..
<osm> i9300xxellb_i9300ojvell3_i9300xxella_home.tar.md5 is valid.
<osm> checking md5 finished sucessfully..
<osm> leave cs..
<id:0/004> odin v.3 engine (id:4)..
<id:0/004> file analysis..
<id:0/004> setupconnection..
<id:0/004> initialzation..
<id:0/004> set pit file..
<id:0/004> do not turn off target!!
<id:0/004>
<id:0/004> re-partition operation failed.
<id:0/004> added!!
<osm> all threads completed. (succeed 0 / failed 1)
<id:0/004> removed!!
<id:0/004> added!!
solution:
i solve the problem i just simply renew the phone's root and then flashed a firmware now there is no problem and thanks for the reply
Click to expand...
Click to collapse
hey i have this problem i used so many firmwares but its says every time re-partition faild!
And sometimes says pit faild! There is no pit partition... I want to know how did u do renew root?
My phone just stucked in downloading do not turn off target!
I just had that ODIN Re-Partition Error, when this happens you are flashing with the wrong country file for your device. You need to reboot into your recovery mode & check those 13 Letter & Numbers above in Recovery Mode eg:
1: The Model Of The Device = Samsung SM-A217M
2: A217MUBU5BUA3 is the Baseband Version number & letters found above in
Recovery mode or in Settings = About = BaseBand Version.
3: Type that same number A217MUBU5BUA3 in Google Search & you will get
the correct country from the result to go to either links to download the
correct country firmware, the one with samfw is the better link to use.
4: Download & apply each file as usual & START. You will see it applying the
firmware with no Re-Partition Errors. It reboots & all is good now. Let me
know if it worked for you, it did for me.
http://www.sammobile.com or http://samfw.com
Nakaiman said:
I just had that ODIN Re-Partition Error, when this happens you are flashing with the wrong country file for your device. You need to reboot into your recovery mode & check those 13 Letter & Numbers above in Recovery Mode eg:
1: The Model Of The Device = Samsung SM-A217M
2: A217MUBU5BUA3 is the Baseband Version number & letters found above in
Recovery mode or in Settings = About = BaseBand Version.
3: Type that same number A217MUBU5BUA3 in Google Search & you will get
the correct country from the result to go to either links to download the
correct country firmware, the one with samfw is the better link to use.
4: Download & apply each file as usual & START. You will see it applying the
firmware with no Re-Partition Errors. It reboots & all is good now. Let me
know if it worked for you, it did for me.
http://www.sammobile.com or http://samfw.com
Click to expand...
Click to collapse
This solution worked for me. I had the re-partition error with four different stock firmwares. Finally I used device info app to check my baseband and bootloader number. I then used those numbers to search for my exact firmware. Flashing this new firmware worked for the very first attempt. A big thanks.
Guillotine35 said:
Thank you but i solved it.
Click to expand...
Click to collapse
how did you solved can you write solution here please it would help others
awais786327 said:
how did you solved can you write solution here please it would help others
Click to expand...
Click to collapse
I updated the thread long time ago man , you can read my solution under this topic's first message.