Hey guys,
I'm trying to help a friend with a phone he bought off someone.. He told me it wouldn't power on.
note: I'm by no means an expert myself
But if I tried holding the volume up rocker and power and I get a screen with 7 lines of red text.
RST_STAT = 0x1
PMIC_IRQ1 = 0x3
PMIC_IRQ2 = 0x0
PMIC_IRQ3 = 0x0
PMIC_IRQ4 = 0x0
PMIC_STATUS1 = 0x80
PMIC_STATUS2 = 0x0
From this point the phone only responds by powering off by holding the power button.
However, I can get it into download mode by pulling the battery, holding the volume rocker down, plugging it into the computer, then reinserting the battery.
I tried to flash back to stock by using the files found in the following thread:
http://forum.xda-developers.com/showthread.php?t=923712
s1_odin_20100512.pit in "PIT"
T959TLJL3-REV03-ALL-low-CL763100.tar.md5 in "PDA"
T959TLJL3_FROYO_Phone-CL763100.tar in "PHONE"
SGH-T959D-CSC-TLSJL3.tar.md5 in "CSC"
Unfortunately every time I try and run ODIN it fails at Kernel... My ODIN log, reads as follows:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> zImage
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried one other version of ODIN, but with that, I couldnt even get it to recognize the phone.
Not sure what my next step should be in hopes to help unbrick this phone... any help in this regard would be much appreciated.
Thanks in advance.
any ideas at all?
First off, are you positive it's a Telus phone if your friend bought it off someone? If so, and you've tried multiple versions of Odin and it hasn't worked, that's the only reason I can think of that it wouldn't work other than your phone being completely bricked.
The phone may be dead... I did a little research, and most people could flash once they managed to get into download mode (http://forum.xda-developers.com/archive/index.php/t-773006.html) but if that fails too, you may be out of luck.
I'm quite positive it's a Telus, as it has a Telus logo on the face of the phone..
The exact model of the phone is SGH-T959P... and I've only tried two versions of ODIN V1, and V1.3.
From my understanding... If I can get into Download mode, and have ODIN recognize the phone... then there's still a glimmer of hope.
I tried running ODIN with the separate file parts; PIT, PDA, PHONE, CSC... and I noticed that the only process it fails on is PDA, everything else goes through just fine.
Not sure what to make of that just quite yet, but I'm hoping someone may know whats up with this thing.
Anyways thanks for your response man, I appreciate it.
I am having the same exact problem, you where most likely trying to flash a T959V or t959t firmware on the phone. You need to find the stock t959p ( Looked everywhere and couldnt find) Some needs to upload a dump file. There is no forum for the t959p
enrygie said:
I am having the same exact problem, you where most likely trying to flash a T959V or t959t firmware on the phone. You need to find the stock t959p ( Looked everywhere and couldnt find) Some needs to upload a dump file. There is no forum for the t959p
Click to expand...
Click to collapse
hmm, yea, that's probably it.
Have you tried requesting it in the android development section?
I do not have a high enough post count to do so, as of yet.
OtterBoxing said:
Hey guys,
I'm trying to help a friend with a phone he bought off someone.. He told me it wouldn't power on.
note: I'm by no means an expert myself
But if I tried holding the volume up rocker and power and I get a screen with 7 lines of red text.
RST_STAT = 0x1
PMIC_IRQ1 = 0x3
PMIC_IRQ2 = 0x0
PMIC_IRQ3 = 0x0
PMIC_IRQ4 = 0x0
PMIC_STATUS1 = 0x80
PMIC_STATUS2 = 0x0
From this point the phone only responds by powering off by holding the power button.
However, I can get it into download mode by pulling the battery, holding the volume rocker down, plugging it into the computer, then reinserting the battery.
I tried to flash back to stock by using the files found in the following thread:
http://forum.xda-developers.com/showthread.php?t=923712
s1_odin_20100512.pit in "PIT"
T959TLJL3-REV03-ALL-low-CL763100.tar.md5 in "PDA"
T959TLJL3_FROYO_Phone-CL763100.tar in "PHONE"
SGH-T959D-CSC-TLSJL3.tar.md5 in "CSC"
Unfortunately every time I try and run ODIN it fails at Kernel... My ODIN log, reads as follows:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> zImage
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried one other version of ODIN, but with that, I couldnt even get it to recognize the phone.
Not sure what my next step should be in hopes to help unbrick this phone... any help in this regard would be much appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Make sure you are flashing with the right files otherwise this brick issue is looks like for a JTAG .
ORT-JTAG Supports Telus T959P
Best Regards
Oz
OtterBoxing said:
The exact model of the phone is SGH-T959P... and I've only tried two versions of ODIN V1, and V1.3.
Click to expand...
Click to collapse
Stop right there. You're trying to install the stock froyo files from Fascinate 3g+ (T959D)
Your friend has the Fascinate 4g (T959P)
I don't think anyone has yet to dump and create the odin-flashable files for stock froyo for the Fascinate 4G.
Related
Hi all,
Firstly, I apologise if this is the wrong forum to post this question but with so many forums it's very hard to know which is the right one! I hope I've found it.
I've been reading around and researched how to root my Galaxy S II. In the Phone --> About my phone is 2.6.35.7-I9100 BVKG3-CL344296 so I downloaded CF-Root-SGS2_XX_OXA_KG3-v4.1-CWM4.zip which appears to be the right kernel for what I'm doing. I've downloaded Odin v1.85 and launched the phone in download mode.
All seemed to be going well and Odin saw the phone. I put the above file in the PDA section and left all the check boxes alone. I pressed Start and the little green bar got bigger with 'KERNEL' in the text box above. I got the following in the message area:
<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> zImage
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
The phone rebooted and now it is stuck on the very first screen with the yellow warning sign. I have tried to put the stock kernel back on, Kernel_I9100BVKG3.TAR, but it makes no difference. The phone is currently bricked.
Can anyone help?
Cheers,
Richard.
Did you put the .ZIP file into the PDA section?
You have to extract the .ZIP, so you get a .tar file, it's that .tar file you need to put into the PDA section.
Put your phone into download mode and try flashing said .tar file with Odin again.
Thanks for the reply, HellcatDroid.
I actually managed to figure out what was going on following that post. I had a sneaking suspicion that the USB ports on my computer weren't acting right so I tried flashing the phone again on one of my laptops and it worked straight away.
Just goes to show that you can research all the likely causes and outcomes and ultimately find out that it's something that you really wouldn't expect normally.
I appreciate your offer of help, though.
horsemanuk said:
Hi all,
Firstly, I apologise if this is the wrong forum to post this question but with so many forums it's very hard to know which is the right one! I hope I've found it.
I've been reading around and researched how to root my Galaxy S II. In the Phone --> About my phone is 2.6.35.7-I9100 BVKG3-CL344296 so I downloaded CF-Root-SGS2_XX_OXA_KG3-v4.1-CWM4.zip which appears to be the right kernel for what I'm doing. I've downloaded Odin v1.85 and launched the phone in download mode.
All seemed to be going well and Odin saw the phone. I put the above file in the PDA section and left all the check boxes alone. I pressed Start and the little green bar got bigger with 'KERNEL' in the text box above. I got the following in the message area:
<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> zImage
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
The phone rebooted and now it is stuck on the very first screen with the yellow warning sign. I have tried to put the stock kernel back on, Kernel_I9100BVKG3.TAR, but it makes no difference. The phone is currently bricked.
Can anyone help?
Cheers,
Richard.
Click to expand...
Click to collapse
I think you have put clockworkmodmod on the phone and a custom kernel, that is why a yellow triangle shows up. I suggest that you should put the phone into recovery mode. It is the same key actions as download mode but you press the up volume button instead of the down button.When you have that up and running you will have options to install file from sdcard, mount, wipe delvik cache and other things. If you have this, in orange colour, then pull your battery out to switch off phone.
Your phone is not bricked.
It depends which country you live in to download the correct system.
Get back on here with the info and I will progress with you.
Sent from my GT-I9100 using XDA Premium App
Problem is already solved, bud.
Hi guys...
I think I have a bootloop issue that I can't resolve. I know I know... but hear me out!
Mine is a UK I9100 on Orange/T-Mobile. I have previously rooted my stock 2.3.3 SG2 without issue. The other day I flashed the official firmware to get 2.3.4 and all went well, except it removed my root access. So I went about rooting it again... except somewhere along the line I screwed it up...
So now I have a phone that won't enter recovery mode. It just sits at the SGS2 logo with the yellow ! triangle in it. It WILL go into download mode however... so I've been attempting to flash some kernels.
I head over to "[READ THIS] Got a Boot Loop? Don't post a New Thread!" as my first port of call. I head over to http://forum.xda-developers.com/showthread.php?t=1113928 and scroll down to Orange, and then the UK. I'm a little unsure which of the 3 downloads to pick (BVKE2, BVKG3 or BVKJ4) as I thought I had KI4... I could been mistaken though.
I download GT-I9100_ORA_I9100BVKJ4_I9100ORAKJ4_I9100BVKJ4.rar, extract the tar, enter download mode, start Odin 1.85, put the file in PDA, connect the phone and hit start.
This is what I get:
<ID:0/005> Added!!
<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)
Can anyone please tell me what I'm doing wrong? My custom binary download is currently reading 23... I'll apologise now if this has already been covered, but I've spent a good number of fruitless evenings of trying, searching, reading and I'm frustrated as hell.
[EDIT] I've also been through the "[GUIDE] Fix an unflashable or soft bricked GSII" guide but that didn't resolve my issue either.
Hi,
Hoping someone can help me, i've searched for a couple of days for answers and tried out suggestions and followed procedures but not getting anywhere so could do with some direct help I think.
Handset details:
Galaxy S3 not locked to any UK network nor does it have any network specific software on it.
Not had any modifications done other than normal OTA software updates and is currently running ICS.
Problem:
Woke up one morning to find the handset frozen on the black & white splashscreen after it being fine the night before and still having plenty of charge. Now won't respond to powering off, just goes blank then returns to splashscreen, only way is to remove battery. Will not respond to normal reset method (vol up + home + power) but will enter download mode (vol down + home + power) and connect to PC.
Attempted solutions:
Have downloaded Odin3 v3.07 along with various firmware .tar files and followed the procedure to reflash the handset but it fails everytime at the 'NAND write' stage.
*Kies is not running at the same time as Odin3
*All drivers are installed and working correctly
*All different USB ports have been tried
*Only have the one USB cable to use
*All settings on Odin3 are correct with regards to checkboxes, etc.
The following is what appears in the message box after each failed attempt: (the <OSM> stages all complete fine)
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialization..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> Boot.img
<ID:0/006> NAND write start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be much appreciated as I am completely at a loss as to why this has happened considering i've done nothing to the handset with regards to rooting, etc. and I don't really want to send my handset away for repair if I can help it.
Thanks in advance.
Nand fail = service centre repair .
jje
Thanks for the reply, I had a bad feeling that it would need sent away
Any ideas as to why the handset should just stop working all of a sudden? I could understand it if I had tried to install some dodgy software or otherwise mess about with it but there's been no tinkering, no liquid ingress, nothing.
Service center for u buddy.. sorry
Sent from my GT-I9300 using xda premium
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
Hello, guys. First of all sorry for my english, but I need help.
I am here because I dont know what to do, I have tried everything without success. Let me explain: I have a S3 GT-I9300, I have had it since 2013 and I have gone through everything with it: brick, several rom, resets, etc. On saturday I woke up and my phone was in a boot loop, but I said ''bah, I can fix it in 20 mins'', but as you can see I couldnt do it. First of all, NAND write start error appeared, I havent seen that error before, then partition errors appeared too.
I can enter to dowload mode and it says GT-I9300 in product name, I can enter to recovery but I cant do anything there
I have tried to flash the same stock rom that I always have, it is an emergency firmware that I have used like 5 times, so.... It is weird that it cannot fix this up. I also have tried with Sammobile's firmware, with and without pit, in 3 usb ports and with 2 usb cables and always the same result: FAIL.
I hope you can help me, buying another phone in my country is difficult.
It can be a hardware issue on emmc of the phone if failed after so many different tries
dusterphil said:
It can be a hardware issue on emmc of the phone if failed after so many different tries
Click to expand...
Click to collapse
And what can I do about it?
What is the Odin error? Post the Odin log.
audit13 said:
What is the Odin error? Post the Odin log.
Click to expand...
Click to collapse
This is one of those:
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping...
Then it does not do anything (in this case I used 4 files + pit, and those files and pit are the ones that I have always used)
The other one is this:
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
This was the first error that appeared. (this is with sammobile's firmware)
The sboot.bin file is the bootloader. It's probably failing to flash for one or more of the following reasons:
the bootloader in the phone is newer than the bootloader in the ROM being flashed;
the ROM is not for the phone being flashed;
need to try a different USB cable;
need to try a different USB port; and/or
the memory chip in the phone is damaged.
Borked nand. If the rom and cable are known to be good and 2 pc's fail then dead nand. It's unfortunate but it happens.
Beamed in by telepathy
I think the phone is dead, it have faught a lot in this years. Thank you anyways
jeanavila_ said:
I think the phone is dead, it have faught a lot in this years. Thank you anyways
Click to expand...
Click to collapse
It's time for you to get a new model