Related
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Theshawty said:
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Click to expand...
Click to collapse
Hi! It just happened to me today! In the morning I was using the phone - calling someone.
Then put it into my pocket, went to work, and there it was already at the boot page, and staying there when resetting.
Tried to flash with odin, and I get the same error message as your friend.
I had a stock 4.0.4 rom, never touched anything on the phone yet.....
Any idea from someone?
edit:
as i9000 has linked to newer firmware with everything in post bellow, so just use that.
http://forum.xda-developers.com/show....php?t=1825272
niches said:
Hi! It just happened to me today! In the morning I was using the phone - calling someone.
Then put it into my pocket, went to work, and there it was already at the boot page, and staying there when resetting.
Tried to flash with odin, and I get the same error message as your friend.
I had a stock 4.0.4 rom, never touched anything on the phone yet.....
Any idea from someone?
Click to expand...
Click to collapse
Return under warranty .
jje
JJEgan said:
Return under warranty .
jje
Click to expand...
Click to collapse
yeah, problem is I bought it from amazon.de so I have to send it then via Post :S
tumult said:
full firmware flash with pit, bootloader, tz, etc..
hooe the link still works, if not i can make mirror tomorrow
also check in Odias thread in original android development if pit for 16 & 32 is same, but as far as i remember it is.
ps. i have flashed this firmware (without pit, but it is safe to download , no viruses, etc).
hope it helps
Click to expand...
Click to collapse
Thanks, I'll try it when I arrive home from celebrating the 253rd birtday of Mr. Guiness
Theshawty said:
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Click to expand...
Click to collapse
All ROMs have full set images of partitions and may be flash with pit and repartition, pit - attached...
http://forum.xda-developers.com/showthread.php?t=1825272
as i9000 said:
All ROMs have full set images of partitions and may be flash with pit and repartition, pit - attached...
http://forum.xda-developers.com/showthread.php?t=1825272
Click to expand...
Click to collapse
edit: i was wrong, all partitions are there.
when you say full partition, you mean sboot.bin and tz.img also? sorry, don't think so , but if so good to know.
that's why i posted link above, that was only full firmware I could find.. but maybe it's just me.
tumult said:
when you say full partition, you mean sboot.bin and tz.img also? sorry, don't think so , but if so good to know.
that's why i posted link above, that was only full firmware I could find.. but maybe it's just me.
Click to expand...
Click to collapse
You can watch attached screen, 9 images:
sboot.bin
param.bin
tz.img
boot.img
recovery.img
system.img
cache.img
hidden.img
modem.bin...
You upload link of ROM full service ROM for Russia...
Why swedish man csc ser, russian location?
all the more so very old...
as i9000 said:
You can watch attached screen, 9 images:
sboot.bin
param.bin
tz.img
boot.img
recovery.img
system.img
cache.img
hidden.img
modem.bin...
You upload link of ROM full service ROM for Russia...
Why swedish man csc ser, russian location?
all the more so very old...
Click to expand...
Click to collapse
and i said sorry if i missed it .. anyway, i will delete my link then as yours are uptodate.
tumult said:
and i said sorry if i missed it .. anyway, i will delete my link then as yours are uptodate.
Click to expand...
Click to collapse
should not be deleted link, and the Russian people attend the xda forum ...
tumult said:
edit:
as i9000 has linked to newer firmware with everything in post bellow, so just use that.
http://forum.xda-developers.com/show....php?t=1825272
Click to expand...
Click to collapse
this is all great, but I think that does not work, I have met with this diagnosis: "there is no pit partition"
INTERNAL MMC IS DEAD... ((((
I'm having a similar problem. Except mine is a GT-I9300. Odin gives me this error.
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
TinyGrasshopper said:
I'm having a similar problem. Except mine is a GT-I9300. Odin gives me this error.
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hey all, I have exactly the same error message. Running cm10 and my phone just froze, after re-boot i'm stuck on boot screen, no recovery and can only enter download mode....HELP!!!!
Someone reported that they had success with flashing the CF-Root to gain CWM recovery back and then flashing DarkyROM from it. But I don't know if that is even true.
PjotrFias said:
Someone reported that they had success with flashing the CF-Root to gain CWM recovery back and then flashing DarkyROM from it. But I don't know if that is even true.
Click to expand...
Click to collapse
thanks for the reply, i tried it but to no avail :crying:
Where did it stop? The first part?
PjotrFias said:
Where did it stop? The first part?
Click to expand...
Click to collapse
yeah i got the no pit message, tried flashing the pit file but won't do it...
I've just received this error on my phone too, Has there been any progress on solutions to this?
Another problem is that I can get into download mode and my system status is "Custom", How will this effect a return to manufacturer?
alot of replies with this errors lately...u guys used any custom FW ?
After try to recover my S3 ('cause i get a brick the typical problem that Samsung screen and then nothing happend, i put my cell into download mode and then try to flash only with PDA file i got the next error "There is no pit partition" ), following this steps from another post
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
i take the
4.1.2
I9300XXELLA_KOR_MULTI_FACTORY
i got a new message from Odin
see image1 in attachements
Now i don't know what to do... just i know is a little hope 'cause it can start a downloading mode...
So Please HELP!
there is the problem
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What i need to do...!!! PLEASE HELP
Same problem
GaboBigale said:
there is the problem
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What i need to do...!!! PLEASE HELP
Click to expand...
Click to collapse
Got the same problem man, if you resolve it first, let me know.:good:
Same problem
lumogox said:
Got the same problem man, if you resolve it first, let me know.:good:
Click to expand...
Click to collapse
got this same problem also, please, anyone? any help?
pit file missing
you have to download pit file so it can create a partition. download it and flash it together with the tar file of your desired firmware. i had the same problem but it couldn't create a partition as it is full bricked and i sent it for a warranty
re-partition fails
panais86 said:
you have to download pit file so it can create a partition. download it and flash it together with the tar file of your desired firmware. i had the same problem but it couldn't create a partition as it is full bricked and i sent it for a warranty
Click to expand...
Click to collapse
thanks for the replay, unfortunately i have already tried that, it fails every time i am trying to re-partition.
echoen99 said:
thanks for the replay, unfortunately i have already tried that, it fails every time i am trying to re-partition.
Click to expand...
Click to collapse
try to flash only the .PIT file.
you have nothing to loose
nand problem
echoen99 said:
thanks for the replay, unfortunately i have already tried that, it fails every time i am trying to re-partition.
Click to expand...
Click to collapse
try this link
http://www.droidevelopers.com/f363/...-files.html?11722-Download-OPS-amp-PIT-files=
if you have a problem as well then probably you have a problem with nand so you have to send it for warranty as well
Thanks for all the replys, i will check and update
Thanks
Sent from my GT-I9300 using Tapatalk 2
stuck same problem
hi
i have a smasung galaxy s3 international I9300
i think i soft bricked it cause i can go into download mode but when i swithch on the phone it gives me a screen
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
how i reached here was i flashed my phone with 3-4 roms got bit stuck and then removed my battery in the middle of a reboot there here i was
so i used ur RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
pls help
mlijfu said:
hi
i have a smasung galaxy s3 international I9300
i think i soft bricked it cause i can go into download mode but when i swithch on the phone it gives me a screen
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
how i reached here was i flashed my phone with 3-4 roms got bit stuck and then removed my battery in the middle of a reboot there here i was
so i used ur RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
pls help
Click to expand...
Click to collapse
What ROM and what Kernel did you use before it happened (Kernel version is also important)? And what did you mean with you got stuck? Details are important when you are dealing with cases like this.
I saw this kind of screen before, some guy had the same problem. However he couldn`t fix himself. Ever heard of Sudden Death?
Scarface1991 said:
What ROM and what Kernel did you use before it happened (Kernel version is also important)? And what did you mean with you got stuck? Details are important when you are dealing with cases like this.
I saw this kind of screen before, some guy had the same problem. However he couldn`t fix himself. Ever heard of Sudden Death?
Click to expand...
Click to collapse
thanks for the reply
CyanogenMod 9 stable version with its own kernel
i installed it and the gapps with it then when the phone rebooted it got stuck at lock screen then i reebooted it again but it was taking a bit long time at samsung logo so i took off the battery and there the phone became like this
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
i can go into download mode
ODIN MODE
Product name:
custom binary download:no
currant binary: samsung official
system status : custom
as u can see product name is blank
with odin i tried ti flash stock Samsung firmware - it wanted some pit
so i used RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
mlijfu said:
thanks for the reply
CyanogenMod 9 stable version with its own kernel
i installed it and the gapps with it then when the phone rebooted it got stuck at lock screen then i reebooted it again but it was taking a bit long time at samsung logo so i took off the battery and there the phone became like this
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
i can go into download mode
ODIN MODE
Product name:
custom binary download:no
currant binary: samsung official
system status : custom
as u can see product name is blank
with odin i tried ti flash stock Samsung firmware - it wanted some pit
so i used RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
Click to expand...
Click to collapse
This is half sds. Needs to go to a service centre and have the motherboard swapped probably
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
This is half sds. Needs to go to a service centre and have the motherboard swapped probably
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
will a Samsung Galaxy S III JTAG Brick Repair help me ?
mlijfu said:
will a Samsung Galaxy S III JTAG Brick Repair help me ?
Click to expand...
Click to collapse
No one has been successful with that method yet. The issue will be that the wear levelling bug has wiped out your eMMC and it needs replacing.
Have a read in the general forum of the "ultimate SDS thread" or whatever its called. There is also my "important - are you covered" thread stuck at the top of general.
So thats the sudden death ? Were you on 4.1.2 before you bricked?
Sent from my GT-I9300 using xda app-developers app
KayKrate said:
So thats the sudden death ? Were you on 4.1.2 before you bricked?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
before rooting was on what ever the latest firmware was
i did not use triangle away
i was using paranoid android 4.2.2
then went to cmod9
so i think i am screwed
CM9 has no SDS fix.
All you can do is try and get warranty repair if you're still in warranty. Otherwise pay for a Mobo repair / replacement.
Someone posted a how to to fit a new eMMC and the cost of the eMMC was cheap, but the effort was a lot.
People gotta take care what firmware to flash :/ Stock 4.1.2 is safe , I used DFG and didnt get any freeze for like a week so my phone's stable now ... maybe samsung come up with a new firmware which makes your phone explode or ruin our devices ... Who knows >.< ?
rootSU said:
CM9 has no SDS fix.
All you can do is try and get warranty repair if you're still in warranty. Otherwise pay for a Mobo repair / replacement.
Someone posted a how to to fit a new eMMC and the cost of the eMMC was cheap, but the effort was a lot.
Click to expand...
Click to collapse
will this help i know its not for s3 but still as am desperate
1. ://forum.xda-developers.com/showthread.php?t=1670651
2. ://forum.xda-developers.com/showthread.php?p=26428986
3. //forum.xda-developers.com/showpost.php?p=26285877&postcount=12
just wanted to know from an expert will one of then work for me?
Dear XDA'ers,
I know their are a lot of topics on this problem, but I can't seem to find the answer.
The first thing I tried was going into recovery mode and doing a factory reset. That did not do the trick.
After that I wasn't able to get into recovery mode anymore, so I went online and searched some topics.
I downloaded a stock S2 ROM and flashed it through ODIN, but it kept failing.
From searching topics it seemed like my S2 suffered from NAND rw corruption.
And nothing fixed, so eventually I went to flash the bootloader. This was the first flash that was succesfull and it got me back to the samsung home screen. Then I tried to flash a new 3 part stock ROM, but it is not working, it keeps getting stuck at this point.
Any one that can talk me through this? Have not a lot of experience with this, so please try to keep it simple for me.
Thanks in advance
If the NAND is really stuffed, motherboard replacement. There is no other fix. Or you could search for Hopper8's 'Odin troubleshooting' thread & keep trying the stuff in the thread over & over & over.
Up to you.
MistahBungle said:
If the NAND is really stuffed, motherboard replacement. There is no other fix. Or you could search for Hopper8's 'Odin troubleshooting' thread & keep trying the stuff in the thread over & over & over.
Up to you.
Click to expand...
Click to collapse
but if that would be stuffed. I shouldn't be able to flash a bootloader should I?
You're the one who mentioned NAND corruption.
If the NAND really is corrupted, then that's the fix. And no, 'successfully' flashing a bootloader (or anything) does not necessarily mean the phone is easily fixable. 'Success' in Odin without the phone working/booting normally isn't success at all.
As per my previous post, find the thread (which really is the reference of these things here), try the stuff in it, see if you can fix it.
If not, you know what to do.
same problem bootlooping
hi guys i am currently having the same problem, i successfuly flashed the JB stock firmware but it's still keep bootlopping..my combo button doesnt work so i am using USB JIG to go into donwload mode, i can even go to recovery mode..hoping for some can link me or provide with FULL PACKAGE, meaning it has a PIT file, BOOTLOADER, CSC, PDA AND PHONE..I think this will be my last resort, so if anyone having this file im looking for plz plz plz direct mo to tha..thnaks
yes u have emmc corruption I have fixed it
but my fix was for data partition your problem is the kernel partition ill make a fix for your phone and inform u soon
Sent from my GT-I9100 using xda premium
follow my guide
http://forum.xda-developers.com/showthread.php?t=2400535
but instead of using the data fix pit as mentioned in the guide use the attached kernel fix pit file the rest of the steps are the same
Sent from my GT-I9100 using xda premium
iamtalha said:
follow my guide
http://forum.xda-developers.com/showthread.php?t=2400535
but instead of using the data fix pit as mentioned in the guide use the attached kernel fix pit file the rest of the steps are the same
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
No luck .
Stuck at NAND WRITE:
Log:
<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!!
Hey guys, recently got mugged for my new S5 and was given a unlocked, bootloop'd S3 i9300 international galaxy s3 (Im from Canada). My buddy told me he had dropped it from about knee high onto carpet when it started having some issues with restarting randomly. He attempted to root it to solve the problems and ended up getting it stuck in a bootloop without the possibility of entering recovery mode. However the phone does go into download mode, so I'm assuming this is a fixable semi brick?
Anyways I started doing my research and found out I should try and reflash the stock firmware using Odin. I found a firmware which I beleive to be the right one, and tried to use Odin.
I got the following message;
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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So I have no idea what this means, as every guide I've seen has said not to touch the PIT button etcetc
I'm not sure if this is helpful, but the writing in download mode is as follows : Odin Mode * Product Name (Blank) * Custom Binary Download : No * Current Binary : Samsung Official * System Status : Custom.
That's about all of the info I have, and seeing how this is the only phone I can afford right now any help would be very much appreciated. Thanks guys.
AlexD73 said:
Hey guys, recently got mugged for my new S5 and was given a unlocked, bootloop'd S3 i9300 international galaxy s3 (Im from Canada). My buddy told me he had dropped it from about knee high onto carpet when it started having some issues with restarting randomly. He attempted to root it to solve the problems and ended up getting it stuck in a bootloop without the possibility of entering recovery mode. However the phone does go into download mode, so I'm assuming this is a fixable semi brick?
Anyways I started doing my research and found out I should try and reflash the stock firmware using Odin. I found a firmware which I beleive to be the right one, and tried to use Odin.
I got the following message;
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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So I have no idea what this means, as every guide I've seen has said not to touch the PIT button etcetc
I'm not sure if this is helpful, but the writing in download mode is as follows : Odin Mode * Product Name (Blank) * Custom Binary Download : No * Current Binary : Samsung Official * System Status : Custom.
That's about all of the info I have, and seeing how this is the only phone I can afford right now any help would be very much appreciated. Thanks guys.
Click to expand...
Click to collapse
Have you tried more than one stock firmware. Where is the phone originally from? I'm not able to find and Canadian firmware.
Darke5tShad0w said:
Have you tried more than one stock firmware. Where is the phone originally from? I'm not able to find and Canadian firmware.
Click to expand...
Click to collapse
I was using UK stock firmwares, but I am unable to flash any firmwares at all successfully due to the error above. It wont go father then the "No Pit".
This try
http://www.ibtimes.co.uk/install-i9300xxugna5-android-4-3-stock-firmware-galaxy-s3-1434726
AlexD73 said:
I was using UK stock firmwares, but I am unable to flash any firmwares at all successfully due to the error above. It wont go father then the "No Pit".
Click to expand...
Click to collapse
Heres the link to the rescue firmware. All the info you gave me says you have pit problems.
This is an emergency firmware that will ever fix or brick the phone but the phone was given to you and you have nothing to lose.
http://forum.xda-developers.com/showpost.php?p=30087735
Darke5tShad0w said:
Heres the link to the rescue firmware. All the info you gave me says you have pit problems.
This is an emergency firmware that will ever fix or brick the phone but the phone was given to you and you have nothing to lose.
http://forum.xda-developers.com/showpost.php?p=30087735
Click to expand...
Click to collapse
The 4.3 download doesn't have the PIT file in it though, I'm guessing that's the important part? Edit *** repartition failed with the 4.1.2
AlexD73 said:
The 4.3 download doesn't have the PIT file in it though, I'm guessing that's the important part? Edit *** repartition failed with the 4.1.2
Click to expand...
Click to collapse
The pit file is in the rescue firmware file. That's the whole point of the rescue firmwares.
I'm sorry I can't help you any further. I'm not going to provide you a pit file etc as I have no knowledge with them or used them.
Sounds to me like it is bricked.
Good Luck.
The power button is stuck, try to flick it some times and it should stop the bootloop. i drop mine when i was getting it out of my pocket last week and same thing happen, the smd switch got stuck and eventually i broke it down trying to get it lose again.
Hello guys!
I am new here, nice to meet all you guys. I have a huge problem with my S3 and I hope it can be fixed without having to replace the motherboard. Last week a flashed the 24th December nightly of CM14. I did a clean flash through my recovery (TWRP) and everything was working fine until two days ago when I found my phone stuck with the CM logo. I removed the battery and tried to switch it on again after reinserting it: it only showed the "Galaxy SIII" logo and couldn't boot. Now, my phone is still in this state. I can go into download mode (and it correctly shows the model number) and I have full access to the twrp recovery. However, the recovery says "no OS installed" and shows an internal memory of 0mb. It is impossible to do a full wipe as it can't mount any partition (only the recovery partition). Using Odin, I can't flash ANY rom I tried so far... I think it's a soft break as I have full access to the recovery, with a full funcioning touch screen and vibration. Is there a way to fix it? Any help? When I'm home I will give you more details and even post some photos of the error messages I get from Odin and the recovery.
Happy new year to everyone and thanks for your help.
trufogio said:
Hello guys!
I am new here, nice to meet all you guys.
Spoiler
I have a huge problem with my S3 and I hope it can be fixed without having to replace the motherboard. Last week a flashed the 24th December nightly of CM14. I did a clean flash through my recovery (TWRP) and everything was working fine until two days ago when I found my phone stuck with the CM logo. I removed the battery and tried to switch it on again after reinserting it: it only showed the "Galaxy SIII" logo and couldn't boot. Now, my phone is still in this state. I can go into download mode (and it correctly shows the model number) and I have full access to the twrp recovery. However, the recovery says "no OS installed" and shows an internal memory of 0mb. It is impossible to do a full wipe as it can't mount any partition (only the recovery partition). Using Odin, I can't flash ANY rom I tried so far... I think it's a soft break as I have full access to the recovery, with a full funcioning touch screen and vibration. Is there a way to fix it? Any help? When I'm home I will give you more details and even post some photos of the error messages I get from Odin and the recovery.
Happy new year to everyone and thanks for your help.
Click to expand...
Click to collapse
You should try to flash a Factory formatting firmware and remapping the partitions with Pit file using Odin. If this doesn't work... There's nothing else to do
TapaStalking
Where can I find the right factory formatting firmware and pit file? I have an International version of GSIII bought in Italy (16gb). In case it doesn't work, will replacing the motherboard do the job? The thing I still don't get is how can the internal memory be damaged if I have full access to the recovery? The recovery is stored in the internal memory, isn't it?
Are you Italian? If so, take a look at this... http://www.androidiani.com/forum/showthread.php?t=344896
TapaStalking
Yes, I am! Thanks, I'll have a look at that link.
Ok, I've tried flashing a PIT file to repartition through Odin and this is what I got:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
When I switch it on I can still go in download mode and recovery, but nothing has changed. I will try now to download a factory formatting firmware.
EMMC brick bug claims another device. Nothing can be done other than replacing the EMMC chip in a specialised repair shop. Or buy another motherboard (i know you're against it, but sh*t happens, yo).
西村大一 said:
EMMC brick bug claims another device. Nothing can be done other than replacing the EMMC chip in a specialised repair shop. Or buy another motherboard (i know you're against it, but sh*t happens, yo).
Click to expand...
Click to collapse
But if the EMMC chip is bricked, how can I still enter into recovery mode? Isn't the recovery stored in the EMMC like any other partition? Am I missing something? I mean, If I couldn't go into recovery I would agree with you, the EMMC would have broken. But as I DO enter into recovery (and can read some files) looks like another problem... If I am wrong, please explain how it works because I'm a little bit lost
I had researched before posting and hadn't found anything helpful, that's why I asked here. There is no need to be rude as this forum is here to offer help between all members of the community
trufogio said:
Ok, I've tried flashing a PIT file to repartition through Odin and this is what I got:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
When I switch it on I can still go in download mode and recovery, but nothing has changed. I will try now to download a factory formatting firmware.
Click to expand...
Click to collapse
Why "added" come later then repatriation operation... I think you should try and try.... Maybe you can change Odin version too. Don't give up just after one try
TapaStalking
ivano949 said:
Why "added" come later then repatriation operation... I think you should try and try.... Maybe you can change Odin version too. Don't give up just after one try
TapaStalking
Click to expand...
Click to collapse
Thanks, I will try!! Anyway if it keeps failing, I found a new gs3 motherboard for just 20 euros...if it's not too difficult to replace I think I will buy it.
trufogio said:
Thanks, I will try!! Anyway if it keeps failing, I found a new gs3 motherboard for just 20 euros...if it's not too difficult to replace I think I will buy it.
Click to expand...
Click to collapse
That's difficult for nothing. Done this summer on my sweet S3, there are tons of tutorial in youtube.... The only thing is wishing new motherboard is OK and don't have a locked imei.... Think at this... Maybe is just time to have a new (and newer) phone
TapaStalking
Are you using the original Samsung USB cable and USB 2.0 ports?
audit13 said:
Are you using the original Samsung USB cable and USB 2.0 ports?
Click to expand...
Click to collapse
yes, I am! I tried several times but it fails every single time... I think I'll buy a new motherboard, 20 euros is a great price. I already have a newer phone (galaxy s6) but I need this s3 to be back to work in order to use it with my secondary sim card Anyway, If you think about installing CM14 nightlies, they are not stable at all at the moment.
trufogio said:
I had researched before posting and hadn't found anything helpful, that's why I asked here. There is no need to be rude as this forum is here to offer help between all members of the community
Click to expand...
Click to collapse
I am not intending to be rude, I even explained what EMMC Brick bug means as a way to educate you and the ones that search the forums for explanations, but since you got my post deleted because you thought i was trying to be rude, well yeah, okay. That's why I hate people.
Please keep it respectful in here, and respect each others opinions..
Here's a thorough read for you guys : XDA Rulesforum.xda-developers.com/announcement.php?a=81
Regards
Vatsal,
Forum Moderator.