hello i'm a noob
my s3 with cyanogenmod had no problem in the last 7 months
today my phone reboots continuously, i enter in recovery mode and try to wipe cache partition or wipedata/factory reset but they both fail
it tell me
formatting /cache
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
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
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
cache wipe complete
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
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
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
please help me
I looked for someone with the same problem but haven't found anything, I apologize if there was another post like
sorry for bad english
please hell pe
i've tried to flash the stock rom but odin say that the process failed
rom stock with pit (i've tried 3 different pit file i've founded) but always the process failed
i've tried a factory korean rom (with bootloader, csc and modem) but failed
i don't know what to do...please someone help me
odin stucks on get pit for mapping...any ideas? please
tmaius7 said:
odin stucks on get pit for mapping...any ideas? please
Click to expand...
Click to collapse
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGOE1_I9300ITVGOE1_I9300XXUGNB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
@tmaius7: using a PIT-file only makes sense with 3part firmware. Did you use it?
If you did and can still reach recovery, try Arter's low format
rp158 said:
@tmaius7: using a PIT-file only makes sense with 3part firmware. Did you use it?
If you did and can still reach recovery, try Arter's low format
Click to expand...
Click to collapse
i tried, but when i flash stock firmware
nand write start
failed
everytime
i think emmc is broken and i'm thinking about changing motherboard. a friend of mine has a s3 NEO with broken display...can i use his motherboard?
a s3 NEO (i9301) motherboard is compatible with my s3 NOT NEO (i9300)?
@tmaius7: of course not!
I have same the promlem too and i cant fix it
metrosuksual said:
I have same the promlem too and i cant fix it
Click to expand...
Click to collapse
Have you tried flashing stock rom? If yes and it doesn't work try to flash philz cwm touch recovery and then wipe cache, it seems to work for me if i cant mount a partition. If it still doesn't help make efs backup and re-pit your phone (get proper pit file first)
McXred said:
Have you tried flashing stock rom? If yes and it doesn't work try to flash philz cwm touch recovery and then wipe cache, it seems to work for me if i cant mount a partition. If it still doesn't help make efs backup and re-pit your phone (get proper pit file first)
Click to expand...
Click to collapse
Thank you for the answer.
The Problem was fixed
1. I took "AROMA Filemanager" and copied my user's files from integral sd card to external sd card
2. Dowloaded official firmware for i9300
3. It had instaled firmware with "Odin" and was logo stopped after restart
4. I Had entered to the recovery and wiped data/factory reset. This time the process was successful!
5. Next the off.firmware was dowloaded normal.
Related
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?
Hello,
I had a GT-i9300 running custom ROM temasek V95. Today morning suddenly the display went off and I couldn't access my phone. On trying to restart the phone got stuck on the samsung screen and hasn't gone past it. I have clockworkMod recovery v.6.0.4.6 installed on my phone and when I open it it says the following:
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
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
So, basically I can't do anything in the recovery. I have tried flashing with the SD card being out and in but has made no difference. I can get into download mode and have tried both Odin and heimdall but none of them work.
When I tried Odin and tried to flash stock ROM it just fails and says the following:
<ID:0/004> Added!!
<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> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I tried Heimdall and tried to flash stock ROM, it says "failed to confirm end of file transfer sequence" every time and I never get a blue progress bar showing that it is transferring. I have tried almost everything but the fact that I can get into download mode suggests me that there's still hope.
Looking at all the help I could find online, I believe the problem is with the recovery and not the actual ROM. I have tried flashing a different recovery but that hasn't made any difference either
Can anyone suggest me a way out of this? This is really frustrating and I would like to know if the phone is definitely bricked or not Looking forward to your suggestions.
Please need HELP!
Your emmc chip is either corrupt or broken. Try flashing the rescue firmware from general forum, including the pit.
If that doesn't work then you need a new motherboard.
Rescue firmware flash did not work
boomboomer said:
Your emmc chip is either corrupt or broken. Try flashing the rescue firmware from general forum, including the pit.
If that doesn't work then you need a new motherboard.
Click to expand...
Click to collapse
Tried rescue firmware including PIT. Did not work. Same problem with NAND write fail. Looks like I have to bid goodbye to this phone now.
Hello all,
I tried to search on internet and open a post on another forum to fix my problem but i had no success
Last friday I saw that my phone had a black screen and i was surprised because i didn't use it since the morning. I pressed the power button to turn it off or turn it on if it was already off and it's stuck on the "Samsung Galaxy SIII I-9300" logo without having any mood to go past that point.
I tried to remove the battery and put it in again.
I tried to let the battery run out of charge and charge it again for a bit.
I tried to remove the sd card.
Nothing solved it.
The phone can get into recovery and download mode.
In recovery mode there are some alerts at the bottom saying that "Can't mount /cache/recovery/command, /cache/recovery/log, /cache/recovery/last_log" and "Can't open /cache/recovery/log, /cache/recovery/last_log"
If i try to wipe or format cache i get an error: "format_volume: make_extf4fs failed on /dev/block/mmcblk0p8"
If i try to wipe Dalvik Cache nothing happen.
If i try to mount or format any of the /efs, /system, /cache, /preload, /data. it just gives me an error saying "error mounting /XYZ" or "error formatting /XYZ" with XYZ the various names.
My phone has ClockworkMod recovery v6.0.4.3 and a version of cyanogenmod (it's rooted).
The only thing i didn't try is to wipe data and factory reset. I want to keep this as the last resort.
I read online that it could even be an hardware problem so even a wipe data and a factory reset shouldn't work.
In any case i wonder if it's possible to recover any of the internal folders. I have made a backup two months ago but in the mean time I added phone numbers (that i haven't saved), photo, video and messages.
The download mode is recognized by Odin3 but since flashing another rom could cause a data loss, even in this case it's not what i'm trying to do.
If there's a way to use Odin3 as a data recovery tool, i'd be happy to know that.
If anyone has any idea i'm glad to hear them. Thanks in advance for any answer
Bumping it.
I tried to use adb to pull out the sdcard data, but since it can't mount it i had no success.
I'm tempted to flash a rom with odin without wiping data/factory reset, but i still am in doubt cause of a random data loss.
My priority is to recover most of the files in the phone. I even tried to backup on the external sdcard but even in this case it cannot mount /sdcard.
Please help!
Manuel.95 said:
Bumping it.
I tried to use adb to pull out the sdcard data, but since it can't mount it i had no success.
I'm tempted to flash a rom with odin without wiping data/factory reset, but i still am in doubt cause of a random data loss.
My priority is to recover most of the files in the phone. I even tried to backup on the external sdcard but even in this case it cannot mount /sdcard.
Please help!
Click to expand...
Click to collapse
What does it say when you cannot mount /sdcard?. I don't remember CWM but TWRP does include a file manager. I've just tried it and it can browse /sdcard right away. If CWM doesn't include a file manager perhaps as a last resort you could try flashing TWRP with Odin and then try accessing the internal memory from there.
andrescm said:
What does it say when you cannot mount /sdcard?. I don't remember CWM but TWRP does include a file manager. I've just tried it and it can browse /sdcard right away. If CWM doesn't include a file manager perhaps as a last resort you could try flashing TWRP with Odin and then try accessing the internal memory from there.
Click to expand...
Click to collapse
The "mounts and storage" menu has the folder inside the /sdcard (/efs, /system, /cache, /preload, /data). If i go to the "backup and restore" menu, any option refer to the /sdcard (backup to /sdcard, restore from /sdcard etc.) and every option simply show "E:Can't mount /sdcard", nothing else. I tried to see the log but it seems there's nothing regarding the /sdcard or it cannot load the log properly.
I could try to flash TWRP but it shouldn't erase my data right?
Manuel.95 said:
The "mounts and storage" menu has the folder inside the /sdcard (/efs, /system, /cache, /preload, /data). If i go to the "backup and restore" menu, any option refer to the /sdcard (backup to /sdcard, restore from /sdcard etc.) and every option simply show "E:Can't mount /sdcard", nothing else. I tried to see the log but it seems there's nothing regarding the /sdcard or it cannot load the log properly.
I could try to flash TWRP but it shouldn't erase my data right?
Click to expand...
Click to collapse
You will only write the recovery partition, nothing else. Here's a tutorial, you will be able to use the Odin method only. The latest version 2.8.6.1 works fine, I've been using it for about two months now.
https://twrp.me/devices/samsunggalaxys3internationalexynos.html
andrescm said:
You will only write the recovery partition, nothing else. Here's a tutorial, you will be able to use the Odin method only. The latest version 2.8.6.1 works fine, I've been using it for about two months now.
Click to expand...
Click to collapse
I tried but had no success. As i said the phone seems to be correctly recognized by odin but when i tried to flash TWRP it fails somehow.
Code:
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1100)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Manuel.95 said:
I tried but had no success. As i said the phone seems to be correctly recognized by odin but when i tried to flash TWRP it fails somehow.
Code:
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1100)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I am having similar issues..........my research points to me that its a hardware issue....emmc is gone !
tharmor said:
I am having similar issues..........my research points to me that its a hardware issue....emmc is gone !
Click to expand...
Click to collapse
Uhm, i reached that research too. So there's no hope...all data are lost and i can't even recover my phone?
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