Hello i have a Galaxy s3 i9300gsmh (Dutch) grey lines on screen / no pit partition.
Samsung kies does not recognize phone, it says phone does not respond!
Odin recognises but does not flash anything..........
phone auto turns on when plugin cable, also charges the battery but no charging screen is displayed.
it does not boot up, when turning on grey lines white screen no sound, no vibration, only downloadmode works, but i am not able to flash anything......
I have 4 pit files, none of them flash. I tried allot of firmwares but only getting the message no pit partition and when selecting a pit file:
In download mode Product name is empty
Custom binary download: no
Current binary: samsung official
System status: Custom
Odin when trying to flash with .pit file:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Removed!!
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
Odin when trying to flash anything without .pit file:
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Heimdall flash error:
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Anybody knows how to fix this ?
I tried differt cables, other laptop, about 30 different roms, Repair firmware, 4 pit files, samsung drivers, heimdall drivers
Did the phone work before?
Where did you get the roms?
The missing product name in download mode is not good and may require a JTAG service to fix the phone.
Could be a buggered phone but try another heimdall or try odin.
Make sure the cable you use is high quality, usually a manufacturer issued cable is best.
Make sure the usb port isn't a shared port (single port side on laptops) (motherboard on desktops).
Make sure you're not using Windows 10. Best results are with xp.
Make sure your efs is good.
Make sure you have the correct firmware/files for the device.
Beamed in by telepathy.
This happend because i flashed it wrong, my brother gave me the phone, and android was dead on it, it would not map anything,
So i flashed root on it and twrp, and cwmtouch but i could not flash the phone with those recoverys strange enough..... It said 0 mb internal memory
And factory restore also did not changed anyhthing......
But flashing the recovery worked....
Was stuck on samsung logo, then i flashed it with selecting the wrong flash file in odin KIES_HOME_I535VRBMB1_861013_REV09_user_low_ship_NOWIPE.tar
It was a succesfull flash (Took 20 minutes) but offcourse the wrong flash file, after that those grey lines...........
Im using windows 7, allready tried flashing with xp on virtual machine.
Tried from my server.....
Tried 10 cables
With odin 3.07 he keeps hanging GET pit for mapping , further allready tried all other odin versions,
I dont know what the right firmware is, but i downloaden from sammobile multiple versions for the i9300....
Without selecting repartitioning, it says no pit partion, with selecting all failes.....
If someone has a link to the right firmware would be nice, but i think i allready have it.
Pit file would also be welcome, i tried the mx.pit, i9300.pit , GT-I9300_mx_20120329, M0_20120220, GT-I9300_mx_20120322 ( Dont know wich one is the right one)
Think i screwed it up by flashing the wrong file on it.....
Is there nothing to shortcircuit ? so it will flash/reset or anything ?
Is there other software to flash without having a box ?
Or any silly tricks ? freezing the phone or something?
Can try everything so tips are welcome before i break it into 2 pieces
shivadow said:
Could be a buggered phone but try another heimdall or try odin.
Make sure the cable you use is high quality, usually a manufacturer issued cable is best.
Make sure the usb port isn't a shared port (single port side on laptops) (motherboard on desktops).
Make sure you're not using Windows 10. Best results are with xp.
Make sure your efs is good.
Make sure you have the correct firmware/files for the device.
Beamed in by telepathy.
Click to expand...
Click to collapse
I also think the missing product name is the problem, so the chip does not know what to do..
I dont have jtag, boxer are to expansive, there needs to be a solution without using boxes or jtag.
Maybe other software to flash, does not matther if it dies for ever... so willing to try everything....
audit13 said:
Did the phone work before?
Where did you get the roms?
The missing product name in download mode is not good and may require a JTAG service to fix the phone.
Click to expand...
Click to collapse
Local phone repair shop? they usually have boxes and probably won't charge you so much for taking the phone back to life if its only soft bricked
If its pit then the chances are it's a dead device. Sometimes you can get pit errors if your setup isn't right. Using a vm isn't always reliable as translation must occur between the 2 operating systems. You should try a dual boot or an xp machine.
If no joy then you can call it a dead phone.
Beamed in by telepathy.
similar situation but product name says GTI9300
Hi guys,
i've a similar situation where the phone shows white and grey lines on the display, I cannot go on recovery mode, just on download mode using a jig usb, but when I try to flash anything with Odin, I get the "No PIT file" error.. tried several PIT files and firmware(both stock and custom rom's) but with no success... I guess that as long as I can see the product name, the phone is not totally dead, am I right?
I found this post here:
https://forum.xda-developers.com/galaxy-s3/general/galaxy-s-iii-gt-i9300-hard-brick-fix-t1916796
and I have a good S3 borrowed from a friend, although I don't want to mess up his while trying to fix mine...
Any suggestion is highly appreciated, thanks!
Have you tried using different USB cables and USB 2.0 ports?
You Better Replace Logic Board
I am 100 percent sure this is SUDDEN DEATH SYNDROME. Because I too was affected today I replaced my logic board.
audit13 said:
Have you tried using different USB cables and USB 2.0 ports?
Click to expand...
Click to collapse
yes, different USB ports, different cables, even different laptops with different operating systems... still no joy
Karthij said:
I am 100 percent sure this is SUDDEN DEATH SYNDROME. Because I too was affected today I replaced my logic board.
Click to expand...
Click to collapse
The SDS was fixed by upgrading the phone to Android 4.1.2 or later version, wasn't it? Plus on many forums it's indicated that as long as the product name on download mode is not empty, the phone can be recovered via software
Tried flashing without the pit file?
yep, it doesn't work as there is no PIT partition
Try flashing the Odin version TWRP and see if you can enter into TWRP after flashing.
audit13 said:
Try flashing the Odin version TWRP and see if you can enter into TWRP after flashing.
Click to expand...
Click to collapse
Tried that too, but unfortunately it's impossible to flash anything into the device.. I took it to a repair shop and they said the only way is to replace the motherboard but actually it's not worth it
Inviato dal mio ONE A2003 utilizzando Tapatalk
The damaged memory chip explains why all recovery methods you tried would not work. You did everything right and everything you could.
steponch said:
yes, different USB ports, different cables, even different laptops with different operating systems... still no joy
The SDS was fixed by upgrading the phone to Android 4.1.2 or later version, wasn't it? Plus on many forums it's indicated that as long as the product name on download mode is not empty, the phone can be recovered via software
Click to expand...
Click to collapse
Believe Me The Chip is Damaged It already have bug and physically it is damaged. So we cannot do any software related tweaks for fixing them unless we REPLACE eMMC chip OR whole LOGIC Board.
It is simple For replacing board i done it myself only
20 USD //
Related
Hey I've searched for more help but I am stuck.........
So i got a samsung fascinate for verzion.
Ran the 'One click root' ,... I have superuser
currently on DI01 and want to get to DL09
I am now trying to install clockworkmod ....
following directions from here http://forum.xda-developers.com/showthread.php?t=788099
:::
Put phone into download mode.
-Turn off phone
-Pull battery
-Press vol down button while plugging into computer
-Should show a yellow triangle
Open odin on pc
-Odin should show a yellow bar with a com port showing that it detects your phone
Click "PDA" button and select the CWMrecovery.tar you downloaded earlier
Click start
I keep getting this error
<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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I have rebooted my PC, tried different clockwork files [CWMrecovery.tar and CWMRecovery_DJ05_DL09.tar.md5]... searched here, read a lot of instruction, searched google and other fourms but I can not find any thing on the 'Can't open the serial(COM) port' error
i have tried with Debugging mode turned off and get the same error.
....anyone have any ideas to help?
I have flashed many roms, radios and programs to my current phone so I don't feel I am a complete noob, but this is frustrating me...I like to think I can figure most things out and this temporarily kicked my butt....and I don't like it
.
hhp_211 said:
Hey I've searched for more help but I am stuck.........
So i got a samsung fascinate for verzion.
Ran the 'One click root' ,... I have superuser
currently on DI01 and want to get to DL09
I am now trying to install clockworkmod ....
following directions from here http://forum.xda-developers.com/showthread.php?t=788099
:::
Put phone into download mode.
-Turn off phone
-Pull battery
-Press vol down button while plugging into computer
-Should show a yellow triangle
Open odin on pc
-Odin should show a yellow bar with a com port showing that it detects your phone
Click "PDA" button and select the CWMrecovery.tar you downloaded earlier
Click start
I keep getting this error
<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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I have rebooted my PC, tried different clockwork files [CWMrecovery.tar and CWMRecovery_DJ05_DL09.tar.md5]... searched here, read a lot of instruction, searched google and other fourms but I can not find any thing on the 'Can't open the serial(COM) port' error
i have tried with Debugging mode turned off and get the same error.
....anyone have any ideas to help?
I have flashed many roms, radios and programs to my current phone so I don't feel I am a complete noob, but this is frustrating me...I like to think I can figure most things out and this temporarily kicked my butt....and I don't like it
.
Click to expand...
Click to collapse
Have you tried a different USB port? Also re-installing the drivers might work.
Hope it helps, Good luck.
Your drivers up to date?
Sent from my SCH-I500 using XDA App
Check the file you are trying to odin. I all but guarantee that you have a corrupt file on your hands.
EDIT:
To be a tad more specific:
Download the odin patch again two more times. Either make sure you can unpack the tar, check the corresponding md5sums, or simply look at the file byte sizes to see if two are identical. Odin really freaks out if you give it bad files.
That is a good thing! Far better that than flash bad data to your pda.
Swyped w/ XDA App. When in doubt, mumble.
uslacson1 said:
Have you tried a different USB port? Also re-installing the drivers might work.
Hope it helps, Good luck.
Click to expand...
Click to collapse
zachsx said:
Your drivers up to date?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hey thanks for quick responses.
I currently have the 'Samsung_Mobile_USB_Driver_V1.3.550.0_SCH-i500_Fascinate.msi' Driver installed
I believe I had installed SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe before when I was trying to get it rooted.
I have not yet tried a different USB port... I will and get back to you...
soba49 said:
Check the file you are trying to odin. I all but guarantee that you have a corrupt file on your hands.
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
I have downloaded 3 different times both files, so I don't know ????
different USB port ... same result...
<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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
soba49 said:
Check the file you are trying to odin. I all but guarantee that you have a corrupt file on your hands.
EDIT:
To be a tad more specific:
Download the odin patch again two more times. Either make sure you can unpack the tar, check the corresponding md5sums, or simply look at the file byte sizes to see if two are identical. Odin really freaks out if you give it bad files.
That is a good thing! Far better that than flash bad data to your pda.
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
When you say odin patch I guess you mean the 'CWMrecovery.tar'
I can unpack it and I have a 'recovery.bin' and a 'zImage' inside the file.
both 5081 KB in every 'CWMrecovery.tar' that I have.
Weird. My old copy from Nov. 26 is 9.93MB (10,414,130 bytes). It contains zImage and recovery.bin, each 5,202,168 bytes. I must be wrong, then.
EDIT:
Just for sake of good practice, I did look up the md5 for that file and I did download it again, and they do match. There are a lot of ways to get MD5s, I used a program called digestIT 2004 to generate it.
http://goo.gl/HELdr
ecfeb7b1633786c1ae9dfb276bfeb231 CWMrecovery.tar
I had no problems downloading it, the hosting is good. It's highly unlikely that I was right about resolving your Odin error.
Sorry I can't be more helpful. I did this once way way back when and had no issues. I did have an issue with a modem.bin packed in a tar later on, and the errors looked a lot like what you are getting now, so I assumed it was the same problem. Thanks for humoring me, and good luck.
I'm a nub.. help..
So I've been trying to follow directions here, but I feel I'm missing something very simple... I cant even get this restore started, it keeps telling me "Invalid Image Type" when i select the CWMrecovery.tar file?? help??
it could be that Kies, or other application that uses USB connection is active.
HI all,
Running Cyanogen nightly build and my phone froze yesterday while I was using an app (think it was twitter, but that should be fairly irrelevant). When I rebooted, it got stuck on the "Samsung Galaxy SIII" screen (and it sits there for hours).
I can't boot into recovery (home + vol up + power = the Samsung logo flashes up for a few seconds, then reboots), I can boot into Download but can't do anything from there:
From heimdall my output is:
Code:
sudo heimdall flash --recovery recovery.img
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
And from Odin (on windows) I get:
"File analysis
SetupConnection
Initialization....
Get PIT for mapping
There is no PIT partition
All threads completed (succeeded 0 / failed 1 )"
Is there any way out of this hole?
Have access to Odin? If so, following may help:
http://widefide.com/mobile/galaxy-s3-boot-problem-solution
found via: http://forum.xda-developers.com/showthread.php?p=29240858
Thanks for the reply. I have Odin on a borrowed laptop, so I tried that.
I get:
"SetupConnection...
Initialization....
Set PIT file...
DO NOT TURN OFF TARGET
.
Re-Partition operation failed
All threads completed (succeed 0 / failed 1 )"
If it's not recoverable, is it worth sending the phone back to the Carphone Warhouse (UK) to get it repaired/replaced. Can they tell it's been rooted if it won't even boot up?
Fair enough, worth asking.....
Given that you've tried more than basics, I hope for your sake you've not got nand corruption (seems to be S3 failure-du-jour), unlikely to recover from that.
The only good news is that if you are suffering that same problem (see SGS Sudden death thread) then your phone innards (or specific parts) will be replaced regardless of rooting, they simply don't care. Many xda members reporting the same thing.
Unsure what CPW will say but if you've exhausted the self-help options Samsung repair centre may be a good bet (you could always phone and explain what happened and what you tried since, they should realise you're technically capable and not bother checking the simple stuff). I was advised by 3 to go straight to the local Samsung repair (said they'd be faster), I do hope you've got one local to you.
At least there is a 2-year Samsung warranty on hardware.
thedigger said:
Thanks for the reply. I have Odin on a borrowed laptop, so I tried that.
I get:
"SetupConnection...
Initialization....
Set PIT file...
DO NOT TURN OFF TARGET
.
Re-Partition operation failed
All threads completed (succeed 0 / failed 1 )"
If it's not recoverable, is it worth sending the phone back to the Carphone Warhouse (UK) to get it repaired/replaced. Can they tell it's been rooted if it won't even boot up?
Click to expand...
Click to collapse
Is Re-Partition unchecked in ODIN?
I've tried both with it checked and unchecked. Neither works.
sorry dude ur device seesm about to dead
http://forum.xda-developers.com/showthread.php?t=1993044
its better to get replace under warranty
Sorry to say that it is a hardware issue. Literally motherboard is dead.
I faced that 2weeks ago... Im rooted and i sent back to samsung service centre... They replaced it free without question asked.
Sent from my GT-I9300 using xda app-developers app
thedigger said:
HI all,
Running Cyanogen nightly build and my phone froze yesterday while I was using an app (think it was twitter, but that should be fairly irrelevant). When I rebooted, it got stuck on the "Samsung Galaxy SIII" screen (and it sits there for hours).
I can't boot into recovery (home + vol up + power = the Samsung logo flashes up for a few seconds, then reboots), I can boot into Download but can't do anything from there:
From heimdall my output is:
Code:
sudo heimdall flash --recovery recovery.img
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
And from Odin (on windows) I get:
"File analysis
SetupConnection
Initialization....
Get PIT for mapping
There is no PIT partition
All threads completed (succeeded 0 / failed 1 )"
Is there any way out of this hole?
Click to expand...
Click to collapse
Hey thedigger, sorry for gravedigging this thread, but have you found any solution to this problem? Since yesterday I'm having the exact same issue as you describe here, and I'm starting to fear I'm SOL.
Thanks in advance.
roddds said:
Hey thedigger, sorry for gravedigging this thread, but have you found any solution to this problem? Since yesterday I'm having the exact same issue as you describe here, and I'm starting to fear I'm SOL.
Thanks in advance.
Click to expand...
Click to collapse
Search PIT problems .
jje
Hmm weird i read about this PIT problem more than several times already where the phone just without a warning seems to reboot and then it`s stuck at the bootlogo and it`s not flashing properly through Odin. I wonder what`s causing this to happen.
Facing the same problem
roddds said:
Hey thedigger, sorry for gravedigging this thread, but have you found any solution to this problem? Since yesterday I'm having the exact same issue as you describe here, and I'm starting to fear I'm SOL.
Thanks in advance.
Click to expand...
Click to collapse
i am facing same problem on s3. did you find any solution?
Thanks.
praveen145 said:
i am facing same problem on s3. did you find any solution?
Thanks.
Click to expand...
Click to collapse
Wow. What a blast from the past!!
I did get mine fixed, but it involved sending the phone off to Samsung for a motherboard replacement (it was still in the warranty period).
If you google "Galaxy S3 sudden death", you'll get tens of thousands of posts explaining what the problem is. I believe, in a nutshell, it's because the firmware was configured incorrectly and rather than writing blocks randomly across the NAND chip, it overwrote the same blocks continiously and "wore out" the solid state chip. They fixed all handsets under warranty at the time, and issued a patch to all handsets which supposedly fixed the problem.
There's a huge thread on this issue elsewhere on XDA Devs : http://forum.xda-developers.com/galaxy-s3/general/ultimate-gs3-sudden-death-thread-t1993044 - you may find that someone has a workaround, but my guess would be that it's beyond economic repair.
[Q] SII (Vodafone NL) with "Download mode" only, stuck on NAND Write Start!!
Hi all,
I have a SGS II from Vodafone NL that was not vendor locked, unfortunately I don't know more about it as I didn't care about firmware, kernel and the such. The phone is 2y 9m old. It all started with a low battery reboot, battery was at 0% and while plugged in was restarting shortly after boot, some too demanding applications that wanted to do their thing immediately after boot. This happen 2 or 3 times, on one of the boots I saw the android updated (green robot with spinning mesh), it was really short and I recall something about updating one file or so. Didn't pay much attention, the phone booted up properly when the battery reached 1%. After a few hours in which I used the phone a few times I found the phone shutdown and on boot I had the boot logo loop. Not knowing what to do I went into "Recovery mode" (Vol up + Home + Power) and issued a factory reset. It did something and I didn't pay much attention to it. There were a lot of errors related to /system /cache and something else that was not accessible. I was thinking that the on-board emmc might have died or at least part of it is. After the factory reset the phone has only the battery logo and "Download mode" (Vol down + Home + Power) only. I don't know what kernel I had nor what OS version it was on, I've updated via Kies some time ago, autumn 2013 maybe.
I've downloaded from sammobile:
I9100BULPG_I9100VDFLP9_I9100BULP8_HOME.tar.md5 Feb 2013 Ver 4.1.2
I9100BULPG_I9100VDFLP9_I9100BULP8_HOME.tar.md5 Sep 2012 Ver 4.0.3
When trying to upload them with Odin 1.85, 3.04 and 3.07 they fail at "NAND Write Start!!" with no other error message, just the normal succeed 0 / fail 1 which I find kinda dumb. Tell me what the error was, the device surely has said something or it timed out. I've tried this on 2 different computers both with Windows7.
After all this failed I tried flashing:
Siyah-s2-v4.1.5.tar
Same error from Odin but something changed in the "Download mode", now it says "CUSTOM BINARY DOWNLOAD: YES (1 counts)", before it was 0. The current binary is still saying Samsung official. The phone is still not booting and the "recovery mode" is still not there.
My questions:
Is there any way I can connect to it via adb and maybe have a shot at looking at it's disk layer? Saw that dd can be used within the adb shell IIRC. I do have some linux/unix filesystem recovery experience.
I saw that they use the .PIT file to change the sector allocation and avoid the damaged parts of the emmc. In order to do that I need to somehow give it a booting kernel. Is there any way of doing that? Maybe boot another device that can attach the emmc.
Should I try heimdall? Can it connect to the device even in "download mode"? I need to install one linux machine for this as I have only windows and BSDs around.
Is there any way for me to reliably find out the model of phone I have?
Are there any other things I can try to recover it or can I consider it's emmc dead?
Thank you.
Pit files can help ...as u already knw..
No pit file flashing doesn't needs working recovery..
U can flash pit file by odin itself...
Did u tried flashing a pit file?
andrei693 said:
Is there any way for me to reliably find out the model of phone I have?.
Click to expand...
Click to collapse
Sticker on phone chassis under battery.
doctor_droid said:
Pit files can help ...as u already knw..
No pit file flashing doesn't needs working recovery..
U can flash pit file by odin itself...
Did u tried flashing a pit file?
Click to expand...
Click to collapse
Haven't tried a pit file as I thought that I need to know which part must be taken out from the sector allocation first. Is it just trial and error?
If yes, which pit files should I try?
Thanks.
MistahBungle said:
Sticker on phone chassis under battery.
Click to expand...
Click to collapse
On the sticker I have:
Model: GT-I9100
SSN: -I9100GSMH
FCC ID: A3LGTI9100
IMEI and S/N
Don't know what to make out of these tough.
Why ? It's pretty self explanatory. It says you have an I9100, so you have an I9100. The rest of that stuff on the sticker is irrelevant.
So...if you do decide to flash a PIT, make sure it's an I9100 PIT or you'll definitely end up with a 116gm plastic paperweight.
MistahBungle said:
Why ? It's pretty self explanatory. It says you have an I9100, so you have an I9100. The rest of that stuff on the sticker is irrelevant.
So...if you do decide to flash a PIT, make sure it's an I9100 PIT or you'll definitely end up with a 116gm plastic paperweight.
Click to expand...
Click to collapse
I found this thread with PIT files http://forum.xda-developers.com/showthread.php?t=1667886, but as I said, I'm clueless as which of the I9100 models this is and which archive should I chose, don't really remember if 8GB/16GB/32GB, plus there is a i9110g there. I know this sounds ignorant but I was with my phone, will not happen in the future.
Also there is this link: http://forum.xda-developers.com/showthread.php?t=1823918, which is supposed to be a partition scanner but I find it confusing. In my case I can't flash anything on the phone so it seems impossible to use the scanner, is that correct? Are there cases in which parts of your emmc can die but you'll still be able to boot a kernel or have/use "recovery mode"?
Status update.
I tried to flash Siyah-s2-v5.0.1.tar with both Odin 3.07 and 1.85.
3.07 said the same error immediately after NAND Write Start!! I had to close Odin, remove battery and upon restart the phone has the triangle present but only download mode works. It incremented the CUSTOM BINARY DOWNLOAD and CURRENT BINARY has changed to CUSTOM.
<ID:0/006> Added!!
<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> zImage
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
1.85 just stayed for ~20 min on "NAND Write" and had to close it myself. Again had to remove battery has phone was not rebooted by Odin. Again the "BINARY DOWNLOAD" counter was increased. The phone still has "download mode" only and the triangle present on normal start.
I don't understand why Odin fails to reboot the phone and returns error upon writing.
I'm still a bit reluctant to use PIT files as I still don't know for sure which one to chose. Keeping it as a last resort tough.
Will try different kernels and I'm still searching for a bootloader to try and write, maybe somehow I can get it to "recovery mode" so I can use adb to see the partitions it has. Can't find any link for this.
I didn't backup EFS partitions and this is my biggest concern in using PIT files. If I understood correctly writing a new PIT file will delete all partitions. Is it possible then to still recover the device?
If anyone has any ideas ...
andrei693 said:
Status update.
I didn't backup EFS partitions and this is my biggest concern in using PIT files. If I understood correctly writing a new PIT file will delete all partitions. Is it possible then to still recover the device?
If anyone has any ideas ...
Click to expand...
Click to collapse
Here' s the bible, did you read it? http://forum.xda-developers.com/showthread.php?t=1457458
Every single word there is important.
Also http://forum.xda-developers.com/showthread.php?t=2345831 has some good tips, but you might have already read it
Here's my experience with a very similar problem: i got the same Odin error, nothing could be written and eventually decided to flash PIT file... Result: phone HARD bricked, no download mode anymore. I suppose the PIT file flashing failed as all of the rest.
IT's the last resort as, if it fails, your phone wil be completely dead (at least for the software part), no charging anymore, no download mode, and you will either need to revive it with a JTAG or change the motherboard.
SO before doing it, try and try everything slowly and using your mind.
Now going back to my problem, it was an emmc hardware problem, even JTAG riff box couldn't revive it (errors pointed to hardware fault) and i had to change the mainboard. I bought a phone with broken display for around 50$ and replaced my mainboard. In a service center you will likely be asked at least 150$.
Hi all,
A classmate of my son has a bricked GPS 4.2 (YP-GI1CW/XEN). Another classmate tried to root it. But it got wrong.
By reading and searching guides here, i have rooted some htc phones and succesfully tried several roms, so i offered to take a look.
I did not know this player before and i dont know what happened to it. The only think my son has heard is: someone rooted it, installed a rom, made it empty again, searched for the right software (rom), but could not find it.
When we got the phone it only showed the logo of galaxy S2. There is no sd-card inside.
I spend hours of reading, finding the download mode (3-button), odin, heimdall, kies etc.
Tried everything, but can't get it done
Could anyone please help me?
Download method works
The 3-button method works and gets the player in download mode.
Info on screen: (WITHOUT usb connection!)
Odin mode
Product name: YP-GI1
Custom binary download: yes (13 counts)
Current binary: custom
downloading....
do not turn off target!!
Click to expand...
Click to collapse
I tried and maybe did stupid things
I have tried heimdall and kies. Kies does not see the player. Heimdall does, but it did not work or i could not work with it.
Installed and uninstalled Heimdall following their textfile.
I unstalled Kies also. Cleaned up my computer. Updated java. Used ccleaner. etc. Removed unused devices, with 'device remover'
Once or twice i clicked the "re-partition" in odin. With or without PIT-file. Now I read, that this could brick your phone. :silly:
I tried all tabs, now i know i should only use the PDA-tab.
I might have done more stupid things.
I found "one-click" in http://forum.xda-developers.com/showthread.php?t=1153310
It took me a while before seeing that not all things where good for this player type. When rooting htc, a wrong rom won't brick your phone, so i did not take it too seriously.
I tried 1 or 2 roms, before seeing that they where for other player versions.
I tried the GalaxyPlayer-Bootloader.zip from http://forum.xda-developers.com/showthread.php?t=1386669
Now i see it is specially for player 5.0.
Here i also used the partition file.
At last i did:
Installed samsung usb drivers again: "SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0.exe"
From: http://forum.xda-developers.com/showthread.php?t=961956
When connecting the player to the computer (while already in download mode), windows start 'downloading' the samsung drivers again...
Dont know why and if this can be a problem.
Tried ADB in command, but 'adb devices' does not give a list, but odin seems to work at first.
Odin (3 v3.07) recognizes it and says:
<ID:0/010> Added!!
and: "0:[com100]"
Now in Odin I first uncheck ALL checks like: repartition, auto reboot and refresh time and the others.
I did try the "NAND ERASE" option. Erasing looks to hang, but at last Odin comes back and gives a fail on flashing.
Between every odin try, I remove the battery, unconnect usb and restart the download mode, then connect again, then start Odin again.
Now I tried 3 roms/kernels:
- CWMStockGI1 kernel.tar (http://forum.xda-developers.com/showthread.php?t=2198444)
- yp-gi1cw.factoryfs.rooted.tar (http://forum.xda-developers.com/showthread.php?t=1884071)
- yp-gi1cw.kernel.stock.tar (http://forum.xda-developers.com/showthread.php?t=1884071)
Odin responds when flashing:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<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> normalboot.img
<ID:0/010> NAND Write Start!!
Click to expand...
Click to collapse
Then nothing.....
On unconnecting:
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
Click to expand...
Click to collapse
I am out of options
Please help. :crying:
Stop before you actually brick it!!!
STOP EVERYTHING RIGHT NOW!!! First thing's first, this is a samsung device and not a HTC device. You screw up flashing this with the wrong device rom and you are screwed. right now, you are lucky in that the state of the device is currently in the state of what is called a softbrick or download only. you need to get stock files for this exact device, preferably able to be used with odin. then after that you can focus on rooting the device. honestly, dont touch the device right now, post a fourm under q and a asking for who has stock recovery files for a 4.2 international version, (i am guessing that you have the international version due to what your location is set as.) once you get those, then flash them with odin. then once it is working again, you can use this exploit to root it.
http://forum.xda-developers.com/showthread.php?t=1312859&highlight=rooting
good luck.
Thanks for your reply.
I was indeed aware that i should not touch the player, until i got feedback
Though I am a bit suprised that flashing a wrong rom could get me into a hard brick.
I will look for the recovery software you mentioned or ask for it.
joly said:
Thanks for your reply.
I was indeed aware that i should not touch the player, until i got feedback
Though I am a bit suprised that flashing a wrong rom could get me into a hard brick.
I will look for the recovery software you mentioned or ask for it.
Click to expand...
Click to collapse
in terms of the recovery images, your going to need to ask someone with a 4.2 to get them off of theirs and send them to you. odin and hemidall are avaiable in the galaxy player all in one forum at the top of the development page.
interms of the wrong image hard bricking a device, it is possable with samsung devices (i've done it once before and have learned to be carefull). Most samsung galaxy player roms not only contain the rom, but also a kernel. if a kernel that was not made for your device is flashed on to it. it might as well be a hard brick because with out a jtag box, you will never get it working again.
I hope you are able to obtain the files and i wish you the best of luck.
I will give this a last chance before I am throwing this piece of junk out of the window.
Galaxy S3 i9300 doesn't turn on at all. Stuck on logo.
Recovery mode (VOLUME UP) doesn't work at all. Shows white and black screen. Before that used to be stuck at DOWNLOAD MODE forever.
Custom mod (VOLUME DOWN) works.
I am connecting it to the PC, it is recognized.
I don't manage to do anything with ODIN.
Trying ODIN 2.10, tried also older one's. Newer one has different fields for some weird reason.
It shows that the phone is connected: 0:[COM3]
I am loading the PDA file and clicking START, it says NO PIT FILE found.
What pit file? no one talks about any PIT file anywhere. Everyone just says to load the PDA file.
If I click on START again it will say <ID:0/003> SetupConnection.. endlessly.
Tried to load some PIT file I found for S3, of course that fails also.
in Kies it connects endlessly.
Any other ideas?
Thanks
Are you using the original Samsung USB cable and a USB 2.0 port? Try Odin 3.07: https://www.google.ca/url?sa=t&rct=...168421&usg=AFQjCNEdxqAS5QWImOPDJboTA_V3D5S9eA
audit13 said:
Are you using the original Samsung USB cable and a USB 2.0 port? Try Odin 3.07: https://www.google.ca/url?sa=t&rct=...168421&usg=AFQjCNEdxqAS5QWImOPDJboTA_V3D5S9eA
Click to expand...
Click to collapse
I think so, but i will try with another cable and report back.
The link you provided doesn't work.
Thanks
Hmm, try this: http://d-h.st/hSj
I tried another cable and nothing changed. Both should be original, yes. Besides how is it related to the PIT error?
Exactly the same on this version also. (I am trying without PIT file)
Without a data cable that is compatible with Odin, Odin can't read the partition information table in the phone.
Pull your battery, replace then try again, it should then work
Sent from my A0001 using Tapatalk
racky29 said:
Pull your battery, replace then try again, it should then work
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I probably did it around 50 times in the past couple of hours, when I was playing with Odin.
audit13 said:
Without a data cable that is compatible with Odin, Odin can't read the partition information table in the phone.
Click to expand...
Click to collapse
I just tried with a 3rd cable. It doesn't seem to be the issue.
What is the exact error message in Odin? You can copy and paste the log here.
I know that I would get pit errors when I would used random USB cables to flash s2, s3, s4, note 2, note 3, etc. Going back to a short, original, Samsung USB cable always worked for me.
Before pasting, I have to choose just the PDA and that's it, right?
No need to provide the PIT file?
Yes, flash stock ROM in pda. Pit file isn't needed unless you need to partition the memory.
I tried with a 4th cable now.
I get the same error.
Could it be that i am using the wrong PDA or something?
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Re-Partition was not selected. Tried it on 1.85
Another confusion is that I have downloaded 2 firwmares from different sites (both claiming it's official) and they have completely different sizes:
1. International-GT-i9300-StockRecovery.tar - 5521KB
2. GT-I9300_Boot_Recovery.tar - 870KB
Now I am downloading a 3rd one:
PRO-I9300XXALF5-20120620165344.zip - 740.23 MB
What size should be??
whatever61 said:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Re-Partition was not selected. Tried it on 1.85
Click to expand...
Click to collapse
Try with Odin 3.07 and use the original Samsung USB cable.
It's same on all versions and all cables.
I don't think a version or a cable is the problem.
All I can say is that I would sometimes get the same error when flashing s2, s3, s4, s5, note 2, note 3, and note 4 until I used a short, original, Samsung USB cable on a USB 2.0 port with Win7 x64.