Hello everyone
I apologize if you think this looks like a duplicate question but I could not find exact same features about my problem.
I've been trying to fix my phone for 2 days now so I thought I could ask for help to see if there is anything to do for my phone.
What happened just before :
I was using cyanogenmod 13 nightly and updated. It worked like a charm even fixing the camera.
I plugged it on the wall to charge and left my apartment. Sadly a storm went for 15 min before I got back to my apartment.
From this time, the phone was stuck on S3 logo.
What works right now :
I can go into download mode, the phone is recognized by computer
Info displayed are : odin mode / Product name : GT-I9300 / Custom binary download : yes (3 counts) / Current binary : custom / System status : custom
I can access recovery, I use TWRP 3.0.0-2
Touch is working well, but like other people I've got the mount error about storage, 0mb is displayed for any storage, and can't wipe or format data to fix it.
I can charge the battery as usual
What I tried to fix :
I tried using odin to flash custom rom, then stock rom 1 file from sammobile (several), even pit re-partition checking right boxes, sadly message is always :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried to use Heimdall too, with 3 different zadig drivers, I could download my pit several times, but could not flash : most of the times there was no response, handshake error, libusb error or protocol fail.
I tried several cables, and several usb plugs. Phone is always recognised by computer but can never transfer.
I tried to flash from micro sd card via twrp, but the 0mb displayed error prevented me from accessing the card.
I feel that my phone could still work, but I need advices on what to try next, and of people could diagnose the state of my phone, I might have forgotten some steps I completed, and really hope someone can help me try something new or tell me what's wrong with it.
Thanks in advance for your help, feel free to ask for any info I might have forgotten to write here.
Sun of rays from south of France, take care,
Emy -`ღ´-
Bump
Can somebody make a diagnosis about the state of the phone?
Do I need to change the motherboard?
Any help appreciated !
@eyrtv, you can try to repartition by flashing 4part-firmware with PIT-file.
You can flash alone system.img, sboot.bin. ect using odin? Did command make_ext4fs /dev/block/mmcblk0p9 ect. work for you ?
Dead nand imo if 16gb
Use last twrp
https://www.androidfilehost.com/?fid=24499762636003755
try to flash with this firmware sir.
rp158 said:
@eyrtv, you can try to repartition by flashing 4part-firmware with PIT-file.
Click to expand...
Click to collapse
Hey, thanks for yout suggestion
Already tried that sadly
asadnow2k said:
https://www.androidfilehost.com/?fid=24499762636003755
try to flash with this firmware sir.
Click to expand...
Click to collapse
Hey thanks for the suggestion
I downloaded this firmware, but now here is another problem, my phone stayed for 1 month + in my drawer with the battery in... My phone did not charge, for 2 minutes the screen reacted and I thought it was ok, then I tried to trun it on too soon, now does not charge at all... Im going to let it charge for hours now, and hope it will react...
If works than fine or try to get a test with new battery
Sent from my iPhone using Tapatalk
Related
Hey guys
I got the notification that a new update is available for my stock GT-I9300 (Vodafone New Zealand) a few days ago. When I clicked on install it complained because I was on mobile data and so I decided to wait until I am at home. But when I got within range of a wifi it must have automatically downloaded and installed the update, because the next time I pulled the device out of my pocket it was stuck at the initial boot screen.
I have since tried to do a firmware recovery through Kies, which downloaded the firmware and then failed to install it saying that it does not know the device or something along those lines (I unfortunately did not save a screenshot of the exact message). Then I tried Odin, which simply fails with the log output below. I know that this is a ROM for the UK, but I haven't found a ROM for NZ yet and thought that it might work anyway.
The status printed when I go into the recovery mode is a bit strange:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Why is there no product name and why is the system status "custom"? I have only had the phone for three weeks and I have not rooted or flashed it yet.
Any suggestions would be much appreciated
Odin output:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLFB_I9300OXABLFB_I9300XXLFB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015>
<ID:0/015> There is no PIT partition.
<ID:0/015> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Nuld said:
Hey guys
I got the notification that a new update is available for my stock GT-I9300 (Vodafone New Zealand) a few days ago. When I clicked on install it complained because I was on mobile data and so I decided to wait until I am at home. But when I got within range of a wifi it must have automatically downloaded and installed the update, because the next time I pulled the device out of my pocket it was stuck at the initial boot screen.
I have since tried to do a firmware recovery through Kies, which downloaded the firmware and then failed to install it saying that it does not know the device or something along those lines (I unfortunately did not save a screenshot of the exact message). Then I tried Odin, which simply fails with the log output below. I know that this is a ROM for the UK, but I haven't found a ROM for NZ yet and thought that it might work anyway.
The status printed when I go into the recovery mode is a bit strange:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Why is there no product name and why is the system status "custom"? I have only had the phone for three weeks and I have not rooted or flashed it yet.
Any suggestions would be much appreciated
Odin output:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLFB_I9300OXABLFB_I9300XXLFB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015>
<ID:0/015> There is no PIT partition.
<ID:0/015> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
download original firmware for galaxy i9300 and flash through odin
that will take you through
or download any rom ZerOne or foxhound they are really nice roms and flash via cwm
vegeta1 said:
download original firmware for galaxy i9300 and flash through odin
that will take you through
or download any rom ZerOne or foxhound they are really nice roms and flash via cwm
Click to expand...
Click to collapse
I am trying to install the original firmware through Odin, but I always get the error message shown at the end of my original post. When I try it a second time directly after it failed, then it does not complain about the PIT but instead fails to connect to the COM port:
<ID:0/011> SetupConnection..
<ID:0/011> Can't open the serial(COM) port.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I have gone through the process of taking out the battery, reinserting it, going into download mode, connecting it to all USB ports on my laptop and trying to flash several times now, always with the same result
I am currently downloading another ROM (I9300XXALF6_I9300ITVALF1_ITV). Maybe that'll work...?
Nuld said:
I am trying to install the original firmware through Odin, but I always get the error message shown at the end of my original post. When I try it a second time directly after it failed, then it does not complain about the PIT but instead fails to connect to the COM port:
<ID:0/011> SetupConnection..
<ID:0/011> Can't open the serial(COM) port.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I have gone through the process of taking out the battery, reinserting it, going into download mode, connecting it to all USB ports on my laptop and trying to flash several times now, always with the same result
I am currently downloading another ROM (I9300XXALF6_I9300ITVALF1_ITV). Maybe that'll work...?
Click to expand...
Click to collapse
Doesn't look like your computer found your phone, remove/reinstall the USB drivers. You can use KIES, click troubleshoot connection, it will reinstall them.
Hope that helps,
-CC
P.S> Make sure ODIN is not open when you run KIES and make sure KIES isn't open when you run ODIN.
clockcycle said:
Doesn't look like your computer found your phone, remove/reinstall the USB drivers. You can use KIES, click troubleshoot connection, it will reinstall them.
Hope that helps,
-CC
P.S> Make sure ODIN is not open when you run KIES and make sure KIES isn't open when you run ODIN.
Click to expand...
Click to collapse
Odin says "<ID:0/011> Added!!" (or some other port of course) whenever I connect the phone, doesn't that mean that it detected the phone?
I actually did the troubleshoot connection in Kies yesterday and it reinstalled the driver. I have since removed Kies (not the driver) from my computer, as I thought that this might be the reason why Odin fails.
Ok I am getting really desperate, I have spent a large part of the weekend trying to get this to work and still no luck. Any further suggestions would be highly appreciated
I have re-installed the USB driver a few times now and Kies is not installed to make sure that there are no conflicts between ODIN/Kies. I have also found a ROM for Vodafone NZ (I9300XXALE8_I9300VNZALE4_VNZ) which is where I got the phone.
ODIN detects when I plug the phone into my computer, but fails with the following:
<ID:0/011> Get PIT for mapping..
<ID:0/011>
<ID:0/011> There is no PIT partition.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
What is the cause for this error and do I need a PIT file and do a re-partition to fix it?
Is it normal that when in download mode, the product name shown on the phone screen is empty?
Thanks!
Your partition table is corrupted. No point trying to fix.
Quickly send to samsung to reflash your phone.
So there is no way I can fix this myself (without risking to make things worse)?
I am not a happy Samsung customer right now, all this time wasted because I installed an official over the air update and who knows how long it'll take to get it fixed...
Thanks for your replies.
Nuld said:
So there is no way I can fix this myself (without risking to make things worse)?
I am not a happy Samsung customer right now, all this time wasted because I installed an official over the air update and who knows how long it'll take to get it fixed...
Thanks for your replies.
Click to expand...
Click to collapse
You are in a position now where further repairs by yourself are even more likely to end up with no warranty .
Phone broke during official update return under warranty .
Flashing other firmwares risks invalidating warranty .
jje
guys i have rooted galaxy s3 i was trying to instal chainfire 3d to my phone just installed and pushed the button that says install driver and restart it istalled drivier and restarted but phone stucks at galaxy s3 logo how can i go to recovery whiout opening the phone so i can flash new rom or something help me out please i am flashing recovery to phone but cant open it
archeuscaine said:
guys i have rooted galaxy s3 i was trying to instal chainfire 3d to my phone just installed and pushed the button that says install driver and restart it istalled drivier and restarted but phone stucks at galaxy s3 logo how can i go to recovery whiout opening the phone so i can flash new rom or something help me out please i am flashing recovery to phone but cant open it
Click to expand...
Click to collapse
Off the phone. Then press power button + volume up + home button
Sent from my GT-I9300 using xda app-developers app
Dear all there is a good news for all of you about SIII product name blank now it can be consider under warranty as Samsung policy.
Hello everybody!
First of all, I'm not sure about my english skills...please have mercy on me :fingers-crossed:
Here I go:
I got my S3 in August/Sept with a T-Mobile Branding. My first action was getting it rootet and flashed with an official Samsung Rom just to get rid of the branding.
Two days ago I woke up to my charging S3 only showing the "Samsung..." Bootlogo. Removed the battery, nothing changed. Tried the Volume up-HomeButton-PowerButton Combo and it only resulted in a blinking logo (the logo disappears for a few seconds). The only thing I have access to is the Download-Mode.
What I tried since then:
Flashing a new one-part-rom with Odin, this was the result:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noshi p.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> sboot.bin
<ID:0/003> NAND Write Start!!*
<ID:0/003>*
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Same with a three-part-rom.
Then I tried to downgrade the bootloader with ADB. But I don't get the drivers (Universal-Naked-Drivers) running. The S3 shows up as "unknown device" at the device manager but it doesn't want to be updated with the right drivers. PdaNet also refused to install USB-Drivers.
It's like they don't recognize the S3.. Perhaps I don't have USB-Debugging enabled? I'm not sure about this, because this brick just happened from one day to another.
I installed and uninstalled the "normal Samsung USB-Driver for mobile phones" often while trying to get the other drivers running. When installed, the S3 showed up in the device manager as one of the USB-Controllers.
Installed Kies for a factory reset but it didn't recognize the S3..
This shows up in Download-Mode:
ODIN*MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
I guess it's no sudden death because it shows the product name? Also I have no idea why it has three flash counts, I just flashed it once seven month ago.
Since I never updated to Jelly Bean the S3 was running on ICS 4.0.4
Edit:
Next steps I tried:
Flashing with an older version of Odin (v.1.85) But also failed at <ID:0/003> Complete(Write) operation failed
Flashing CF-Root v.6.4 to get the recovery mode back. Failed at <ID:0/003> Complete(Write) operation failed
Flashing Resurrection Odin CheckRom EvoHD v.4. Failed at <ID:0/003> Complete(Write) operation failed
Repartition with 20120329.pit and mx.pit. Failed at <ID:0/003> Complete(Write) operation failed
I'd still appreciate any kind of help or feedback!
It sounds like partial nand failure or simple partition corruption. Search here in q&a for solutions to repartition, but if that fails then your nand is probably toast.
try flashing a pit file
not sure if it will help but..
connect it to computer..when it fails to install drivers..Turn off and Pull battery out for few secs restart..
sometimes this helps to reinstall drivers..not sure in your case of a bootloop though?
Thanks for your answers!
I tried to repartition with a PIT-File but it didn't work.
At first I tried the GT-I9300_mx_20120329.pit with this 3-part-rom:
CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md5 is valid.
MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noship.tar.md5 is valid.
But the same error appeared.. also the error appeared so fast I don't think there happened a repartition at all?
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Second try was 3-part-rom recommended with the mx.pit-File:
CODE_I9300XXALEF_611327_REV00_user_low_ship.tar.md5 is valid.
MODEM_I9300XXLEF_REV02_REV04_CL1147871.tar.md5 is valid.
CSC_OXF_I9300OXFALEA_613742_REV00_user_low_ship.tar.md5 is valid.
With the same result...
It's always the same error, again and again...
Any further ideas?
you are done
Only two answers one wrong PIT or partition damaged .
Two Nand damaged see how much will a new motherboard cost .
jje
Thanks again!
With the GT-I9300_mx_20120220.pit-File I got my S3 responding for the first time since it died. It showed the blue loading-bar, but it didn't move at all and Odin stopped at <ID:0/004> NAND Write Start!!
Tried this rescue-version http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 with mx.pit but of course it didn't work..
you are done
Click to expand...
Click to collapse
seems like you're right, unfortunately..
But if you have ANY idea what I could try, please post it.
Are you sure it's a NAND damage or could it be a bootloader problem? I found this thread: http://forum.xda-developers.com/showthread.php?t=1916796 but I don't understand what they are talking about yet.
Update:
I couldn't find a solution and send it to a Samsung repair service and it was repaired under warranty. Don't know why exactly..they didn't need to because of my flash-counter. There was a letter in the package that said the mainboard was replaced and that's all!
Anyways, thanks for the help!
Can be closed!
Possible Solution
xylakant said:
Update:
I couldn't find a solution and send it to a Samsung repair service and it was repaired under warranty. Don't know why exactly..they didn't need to because of my flash-counter. There was a letter in the package that said the mainboard was replaced and that's all!
Anyways, thanks for the help!
Can be closed!
Click to expand...
Click to collapse
I had a similar problem, my phone just froze in the middle of a phone call, had to pull out battery, and when i tried to turn it on, it wouldn't pass the second "SAMSUNG" logo, just stayed there forever, with the blue light (Official JB 4.1.2 - not rooted)... Anyway, after 3 days of trying, downloaded bunch of firmwares, but all of them gave me the infamous "Complete(Write) operation failed". This is how I MANAGED to revive my i9300 16Gb Int:
1.Open ODIN, load ONLY the pit file corresponding to your phone (In my case i9300 16Gb Int'l - GT-I9300_mx_20120220.pit), check "Repartition" and "F.Reset Time" and hit "Start".
- If this step goes OK (All threads completed. (succeed 1 / failed 0))
2. Click on the "Reset" button in Odin (or close and re-open it), in PDA select "recovery-cwm-touch-6.0.1.2-i9300.tar", make sure only "F.Reset Time" and "Auto Reboot" are checked, and flash it. If everything goes OK, you should now have CWM instead of Stock recovery.
3. Take any microSD card, any size, and put THIS file on the root of the microSD using a card reader or whatever you prefer - but be careful, copy the zip as it is - do not unzip it.
4. Insert the memory card in the phone, enter recovery*, and select "Install zip from External Storage" and choose the file you put on the root of the card (by the way, it's a 4.0.4 downgrade bootloader), it should flash in a second, the phone will restart, and that's it!
5. Download and flash 4.0.4 Stock FW using Odin (i used "I9300XXBLH1_OXEBLF1.zip"), everything should go OK, and the phone will be bootable again.
*(my phone didn't wanted to enter recovery the old fashioned way using 3-button combo, but i managed to enter recovery from charging mode, by connecting the charger on a switched off phone, and as soon it starts charging press Vol Up + Home + Power, and when the FIRST Logo (Galaxy S III GT-I9300) appears, let go of the power button, keep pressing the Vol Up + Home, and it enters recovery).
ATRAC3 said:
1.Open ODIN, load ONLY the pit file corresponding to your phone (In my case i9300 16Gb Int'l - GT-I9300_mx_20120220.pit), check "Repartition" and "F.Reset Time" and hit "Start".
- If this step goes OK (All threads completed. (succeed 1 / failed 0))
Click to expand...
Click to collapse
Odin Stuck at "Set Partition" ^^
"<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
Help ?
Did you give it the pit file? Pit is really a last resort AFTER you've ruled out sending for repair
Sent from my GT-I9300 using Tapatalk 4
I have the pit file and Checked the Box ^^
MrFraggii said:
I have the pit file and Checked the Box ^^
Click to expand...
Click to collapse
Correct PIT file ??? for your phone ??
Flashing PIT 99% kill the phone .
You require a service centre .
Warranty will depend upon their report .
jje
Have the right Pit file ^^ But odin Stuck at Set mapping
MrFraggii said:
Have the right Pit file ^^ But odin Stuck at Set mapping
Click to expand...
Click to collapse
Where can you download these 16, 32 or 64 .pit files ? I couldn't find them anywhere ...
If you start playing with PIT files you will end up with a dead phone and at best have to buy a new motherboard .
They might be found on sammobile
jje
JJEgan said:
If you start playing with PIT files you will end up with a dead phone and at best have to buy a new motherboard .
They might be found on sammobile
jje
Click to expand...
Click to collapse
Thanks for the lead, I will look for them on Sammobile.
But Please, this is the only answer I could reald along my searches "do not mess with .pit file". That does not answers the "where" and "which file" questions. I think people know playing with .pit files is touchy and they have a reason to ask for it.Stop being their mother and just answer the question accurately !
tris16 said:
Thanks for the lead, I will look for them on Sammobile.
But Please, this is the only answer I could reald along my searches "do not mess with .pit file". That does not answers the "where" and "which file" questions. I think people know playing with .pit files is touchy and they have a reason to ask for it.Stop being their mother and just answer the question accurately !
Click to expand...
Click to collapse
Your sense of entitlement is awe inspiring, if you searched and read you would find many people who flashed pit files to fix just a soft brick and then had to pay for a new motherboard.
So no, we won't help people wreck their phones.
Pit Files
tris16 said:
Where can you download these 16, 32 or 64 .pit files ? I couldn't find them anywhere ...
Click to expand...
Click to collapse
This is where i got mine.
http://forum.xda-developers.com/showthread.php?p=30547929
GS II i9100
Note: Warranty is already expired
Before I write anything further, I have been trying to get the most I can out of this thread: http://forum.xda-developers.com/showthread.php?t=1457458
Sadly, I can't seem to wrap my head around this problem, so here goes:
Yesterday I've found out, that the new CM11 came out. Of course I went off to download it, put it in my phone and started to install it through recovery (I had siyah at that time). Well, it failed, must've been corrupt or something, since I got the error status 7. Anyways, while exiting the install screen, siyah asked me, if I want to repair something, because something may have gotten corrupt (Sorry, can't remember the exact thing). Being the sloppy person I am, I clicked yes.
Five minutes later, after going back to stock firmware, because apparently during the install something did go corrupt, and the phone wouldn't boot, only play the boot sound, I've read, that I need the newest CWM for CM11 to work.
Another five minutes later I'm staring at this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-i9100.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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I've tried changing computers, kicking KIES out through the window, using different USB slots and cables, but to no avail. It just keeps throwing this error at me every time I try to install anything through Odin. The strangest part is, though, that the phone is working perfectly fine.
What could be the problem, and if it is possible, how do I fix it?
Another quick note would be my counter in the download screen of my SII. It's 12 (yeah, I know, I kept forgetting about it, but now, since I'm unable to install anything through Odin, I can't even root the phone and reset the damn thing)
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
andrewwright said:
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
Click to expand...
Click to collapse
And apparently, this is now happening:
Baseband version - XXMS2
Build - XWLSS
I think I may have messed it up a little...
Please close the thread
This thread can be closed.
Should anyone need this:
After losing patience spending hours on the phone I have decided to JTAG it... Ant it worked. The phone is running like a charm now.
My phone: SPH-L710 Sprint Galaxy S3
This is what my ODIN says after trying to flash with stock ROM.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
This is what is on the top left corner in the DL mode.
"ODIN MODE
PRODUCT NAME: SPH-L710.
CUSTOM BINARY:Custom
SYSTEM STATUS:Custom
QUALCOM SECUREBOOT: ENABLE
Warranty Bit: 1
Bootloader AP SWAEV: 2
SW REV CHECK FAIL : Fused 2 > Binary 1"
Here's my story:
My phone was displaying "No error" in Google Play Store. So I factory reset my phone but it didn't resolve my problem. So I flashed a stock ROM and it failed. My device was 4.4.2 ROOTED before flashing a lower version. (Cannot remember the version number though.) Now it displays, "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." My phone, however, DOES go into Download mode but not the recovery mode. I tried to flash multiple times but ODIN kept on failing. I tried multiple USB cables, different USB ports, computers, and reinstalled USB drivers, etc. However ODIN keeps on failing. I tried to recover it through KIES but it will not detect my device. I am thinking about sending this into Mobiletechvideos.com but I heard some devices could not be restored because of EMMC failure. Do you think my device's emmc failed? (I spent 200 bucks on this and do not wanna buy another one )
Soooo..
Is there anything I can do before I send it into mobiletechvideos.com for 50 bucks?
I've tried this http://forum.xda-developers.com/showthread.php?t=1840030 but it didn't work because I couldn't find Sprint bootchain. Does anyone have one for Sprint?
I'm also trying to use this method http://forum.xda-developers.com/showthread.php?t=2369125 but do you think it will work? (I don't have a SD card so I can't try just yet.) It was meant for hardbricked people. But mine is not completely bricked. It turns on and goes into DL mode.
** I've just noticed some signs of hardbrick. WITHOUT my battery and I hook my phone up to my PC with a USB cable, it shows that Red LED light and vibrates. Doesn't turn on though. WITH the battery, it turns on and goes into DL mode. Is my phone hard bricked?**
SUMMARIZED QUESTIONS:
1) Is my phone hard bricked?
2) Do you think JTAG can fix my phone? My phone may be in Read only state. Wouldn't that prevent the JTAG method?
3) Will the SD card method work?
4) Does anyone have Sprint bootchain? (I think my phone might be at Read Only state)
5) What are some signs of EMMC failure? I would really hate it if my phone had EMMC failure -_-
6) Did my phone brick because my phone was rooted and I flashed unrooted Sprint Stock ROM?
PLEASE PLEASE help me. Donations will be considered! (Really, I'm desperate to get my phone fixed. T_T )
Thank you alot in advance. Please leave replies if you need more information.
You have posted in the wrong forum, anything you flash from here will hard brick it.
Report your own post and ask a moderator to move it for you.
Fail at nand write is usually a dead emmc chip, try flashing full firmware with a pit as last resort.
As long as you can get into D/L mode, then you're fine. If you can get into D/L mode and your phone can turn on, it isn't hardbricked.
Try using this file (in case you're wondering, it's the 4.4.2 stock ROM). If it doesn't work on Odin 3.xx, try using it on Odin 1.85. I had the same problem, too.
Sent from my SPH-L710 using XDA Free mobile app
Hello, and excuse my poor English.
I got my hands over a white S3 GT-I9300 running 4.1.2 (I9300XXELLA), the phone was suffering some annoying failures (certain built-in apps crashes after the keyboard is displayed and the phone app dial freezes after you press the call button thus the device make the call), did the wipe/data&cache, factory reset using the settings menu and OTA updates, this last one keeps saying the phone couldn't connect to check updates after several wipes/attempts.
So I followed this tutorial www[dot]android[dot]gs/install-official-xxugna8-android-4-3-jb-on-galaxy-s3-i9300/ (pretty much the same procedures as I re-flashed one of my previous phones, a Galaxy S Duos so I was kinda confident) but instead of the XXUGNA8 update I downloaded the Argentinian variant I9300UBUGNK1_I9300UVOUGNK1_ARO, followed all the steps in the tutorial and ODIN flashed successfully, the phone insta-rebooted for less than one second and stuck there (always rebooting in loop, showing the "Samsung Galaxy S3 GT-I9300" logo for less than one second), tried pulling out the battery, no luck. I can't access the recovery either but can enter in download mode. Also tried the KIES method but after asking the S/N it says "the model information that you have entered cannot be verified, the device initialization cannot proceed."
Tried to flashing it again using the same steps and files but got a NAND write error once and I stopped after that, now I am downloading the XXUGNA8 version at 50kb/s from samsung-firmware page since I started getting a 502 bad gateway error from sammobile's page.
What did I wrong? Can someone point me the necessary steps to repair this phone if there is a fix?
Here's the re-attempt log from ODIN 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBUGNK1_I9300UVOUGNK1_I9300UBUGNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it appears as follows:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Any help would be more than welcome.
Regards.
I'm not a robot
dckmnn said:
Hello, and excuse my poor English.
I got my hands over a white S3 GT-I9300 running 4.1.2 (I9300XXELLA), the phone was suffering some annoying failures (certain built-in apps crashes after the keyboard is displayed and the phone app dial freezes after you press the call button thus the device make the call), did the wipe/data&cache, factory reset using the settings menu and OTA updates, this last one keeps saying the phone couldn't connect to check updates after several wipes/attempts.
So I followed this tutorial www[dot]android[dot]gs/install-official-xxugna8-android-4-3-jb-on-galaxy-s3-i9300/ (pretty much the same procedures as I re-flashed one of my previous phones, a Galaxy S Duos so I was kinda confident) but instead of the XXUGNA8 update I downloaded the Argentinian variant I9300UBUGNK1_I9300UVOUGNK1_ARO, followed all the steps in the tutorial and ODIN flashed successfully, the phone insta-rebooted for less than one second and stuck there (always rebooting in loop, showing the "Samsung Galaxy S3 GT-I9300" logo for less than one second), tried pulling out the battery, no luck. I can't access the recovery either but can enter in download mode. Also tried the KIES method but after asking the S/N it says "the model information that you have entered cannot be verified, the device initialization cannot proceed."
Tried to flashing it again using the same steps and files but got a NAND write error once and I stopped after that, now I am downloading the XXUGNA8 version at 50kb/s from samsung-firmware page since I started getting a 502 bad gateway error from sammobile's page.
What did I wrong? Can someone point me the necessary steps to repair this phone if there is a fix?
Here's the re-attempt log from ODIN 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBUGNK1_I9300UVOUGNK1_I9300UBUGNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it appears as follows:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Any help would be more than welcome.
Regards.
Click to expand...
Click to collapse
Hey brother I also had similar problem today midnight here in india . and i also tried several methods to restore my phone.
i tried kies also but but it required full rom package to download ,as my internet speed is slow I tried other method and it worked. I am very happy now :victory:
just connect your GT-I9300 in download mode. use odin 3.07. download CF-Auto-Root-m0-m0xx-gti9300.tar.md5 file that we normally use for rooting. Select pda in odin select CF-Auto-Root-m0-m0xx-gti9300.tar.md5 and click start.
Its just recovery related problem. my entire data is there as it is in my phone.
Hit thanks If I helped you
I'll try it as soon as I can, and let you know if it worked.
For now thanks for the help!
dckmnn said:
I'll try it as soon as I can, and let you know if it worked.
For now thanks for the help!
Click to expand...
Click to collapse
I flashed back to stock yesterday after 2 years of Custom - just felt like it!!
I too got stuck on Samsung logo immedidately after my carrier logo appeared for a couple of seconds.
Tried reflashing again twice - again with Odin - same result
Then I had a thought - why not boot into recovery mode and do a factory reset . I did this, the phone rebooted and immediately it went through 'normal' set up procedure.
Worth a try.
Homer
homer timpson said:
Then I had a thought - why not boot into recovery mode and do a factory reset . I did this, the phone rebooted and immediately it went through 'normal' set up procedure.
Worth a try.
Homer
Click to expand...
Click to collapse
That though is written in the sticky's.
homer timpson said:
I flashed back to stock yesterday after 2 years of Custom - just felt like it!!
I too got stuck on Samsung logo immedidately after my carrier logo appeared for a couple of seconds.
Tried reflashing again twice - again with Odin - same result
Then I had a thought - why not boot into recovery mode and do a factory reset . I did this, the phone rebooted and immediately it went through 'normal' set up procedure.
Worth a try.
Homer
Click to expand...
Click to collapse
Sorry for the late response! The phone wasn't able to enter recovery, only download mode.
Another not robot here
[UPDATE]
I sold the phone "as is", I got it cheap and sell it almost at the same price so any mod can mark this thread as "Solved".
Easy come, easy go they say.
Regards.