OK so many of u might know this thing
I rooted the phone... did an OTA Update. BAM phone not booting up
Still in the same condition tried all kinds of software/hardware techniques. Before trying the PIT file i thought that I might give it to Samsung and ask what they say (My frnd's frnd works there)
So he said this
"Ur phone has a Processor problem, There is no problem with the Partition on ur SD Card. I can change the Processor for u but its a 20% chance that it might work. A Motherboard replacement for Rs. 27,000 will only do it [bought the phone for Rs. 55,000]"
So here is my status:
I'm waiting for the phone to come back and I'll take it and try the PIT file thing
My device is a U.K Unbranded Pebble Blue and rooted. Sometimes goes into the Recovery. Almost about 1 in 10 attempts it goes there and 1 in 5 attempts it is actually stable in it. Other wise it just gets back to the GT-i9300 logo.
So!
2 people say that my device should be flashed with the "mx.pit" file. These guys were experts. I mean 1000+ on the Thanks bar.
1 person says that it shud be "...029.pit" format. He did it on his own. Same device as mine but just that his was White in colour. ONLY DIFFERENCE
I need Answers on the following:
1. Is my phone really having the processor problem? Cuz if it was then it shudnt hav booted up in the first place (I thnk?)
2. WHICH PIT SHOULD I GO FOR. ALSO I'M HAVING A BAD TIME FINDING THE 3-PART FIRMWARE FILE.
3. Flashes OK in the Odin. Like it should on ANY S3. Doesn't gives me errors or anything. But it seems like it doesn't really affect it at all. Its still the same. WHATS THE CULPRIT IN THIS PROBLEM?
4. When I go to the Recovery mode (when stable) I can't mount the SD Card? :/
On going to the "Install Zip from SD Card" it says "cannot mount Sd Card". So i think it is the PIT Problem.
He does says "We are trying everything on our par. Even we're doing what we aren't supposed to be doing to a normal person's S3. (frnd u know)."
So what should I do?
I KNOW ITS A LONG THREAD. BUT DO READ IT CAREFULLY :/ :/
THANKS I REALLY NEED SOME HELP...
How did you manage to do an ota update with a rooted phone....usually a message comes up with something like (phone is modified, update cancelled) so how you managed to do that i dont know!....firmware files for the S3 only come as 1 .tar file because thats all thats needed, in terms of the .pit i suggest you search the stickies....theirs bound to be something in their. But im still baffled as to how you managed to do an ota update on a rooted phone :s
Sent from my GT-I9300 using xda premium
AusafSal said:
. did an OTA Update. BAM phone not booting up
>>>> Not with root . You need to flash stock via Odin .
I can change the Processor for u but its a 20% chance that it might work.
>>>>That sounds nonsense if the CPU is changeable and is the problem its only a 20% chance of working ????
2 people say that my device should be flashed with the "mx.pit" file. These guys were experts. I mean 1000+ on the Thanks bar.
>>>> 1000 thanks does not make an expert in PIT files .
>>> PIT is deadly do not flash a wrong PIT .
I need Answers on the following:
1. Is my phone really having the processor problem? Cuz if it was then it shudnt hav booted up in the first place (I thnk?)
>>>>Samsung Service would need to answer that question .
He does says "We are trying everything on our par. Even we're doing what we aren't supposed to be doing to a normal person's S3. (frnd u know)."
So what should I do?
>>. Take the phone back under warranty to a Samsung service centre with trained staff .
jje
Click to expand...
Click to collapse
JJEgan said:
AusafSal said:
. did an OTA Update. BAM phone not booting up
>>>> Not with root . You need to flash stock via Odin .
I can change the Processor for u but its a 20% chance that it might work.
>>>>That sounds nonsense if the CPU is changeable and is the problem its only a 20% chance of working ????
2 people say that my device should be flashed with the "mx.pit" file. These guys were experts. I mean 1000+ on the Thanks bar.
>>>> 1000 thanks does not make an expert in PIT files .
>>> PIT is deadly do not flash a wrong PIT .
I need Answers on the following:
1. Is my phone really having the processor problem? Cuz if it was then it shudnt hav booted up in the first place (I thnk?)
>>>>Samsung Service would need to answer that question .
He does says "We are trying everything on our par. Even we're doing what we aren't supposed to be doing to a normal person's S3. (frnd u know)."
So what should I do?
>>. Take the phone back under warranty to a Samsung service centre with trained staff .
jje
Click to expand...
Click to collapse
Saying that....if hes rooted his phone, theyll pick up on that and void his warranty....
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I can change the Processor for u but its a 20% chance that it might work. A Motherboard replacement for Rs. 27,000 will only do i
Click to expand...
Click to collapse
Either someone mistranslated it from another language or they are trying to rip you off.
It's VERY,VERY hard to replace the soldered CPU on the logic-board and I'm sure your CPU and logic board are fine.
Usually motherboard replacements are executed whenever they have no clue what's wrong and don't want to search the issue.
There is no problem with the Partition on ur SD Card.
Click to expand...
Click to collapse
Your SDcard has nothing to do with the issue at all. The only problem is your internal storage (which is an SSD, not an SDcard)
Your partitions might be corrupted.
Please define "phone not booting up". It if's stuck in a bootloop, try removing the SDcard and booting the phone to CWM recovery,
and formatting all usual partitions, then running ext2fs on the internal partition.
(Tip: if you have data on it, you can usually skip the formatting and only run ext2fs, that way you usually won't lose any files but the chance of the phone booting again is lower)
d4fseeker said:
Either someone mistranslated it from another language or they are trying to rip you off.
It's VERY,VERY hard to replace the soldered CPU on the logic-board and I'm sure your CPU and logic board are fine.
Usually motherboard replacements are executed whenever they have no clue what's wrong and don't want to search the issue.
Your SDcard has nothing to do with the issue at all. The only problem is your internal storage (which is an SSD, not an SDcard)
Your partitions might be corrupted.
Please define "phone not booting up". It if's stuck in a bootloop, try removing the SDcard and booting the phone to CWM recovery,
and formatting all usual partitions, then running ext2fs on the internal partition.
(Tip: if you have data on it, you can usually skip the formatting and only run ext2fs, that way you usually won't lose any files but the chance of the phone booting again is lower)
Click to expand...
Click to collapse
The Internal memory is generally called an internal 'SD Card', so no need to be picky
Just use the recommended PIT and pray to god, if anything goes wrong just get it to the service center and behave like a blonde, seriously.. be dumb.
Skander1998 said:
The Internal memory is generally called an internal 'SD Card', so no need to be picky
Just use the recommended PIT and pray to god, if anything goes wrong just get it to the service center and behave like a blonde, seriously.. be dumb.
Click to expand...
Click to collapse
What a useless reply .
jje
Try flashing FULL ROM (PDA, PHONE, MODEM, PIT)
GR0S said:
Try flashing FULL ROM (PDA, PHONE, MODEM, PIT)
Click to expand...
Click to collapse
Did you not read the post above....flashing a .pit is not good and he could end up doing more damage than good....fool!
Sent from my GT-I9300 using xda premium
If phone cant boot, maybe filesystem is damaged. TS should completly reflash everything (that will recreate partition table)
---------- Post added at 08:20 PM ---------- Previous post was at 08:17 PM ----------
OTA can't break hardware (I believe), so this is software problem. In the worst case JTAG station will be needen
GR0S said:
Try flashing FULL ROM (PDA, PHONE, MODEM, PIT)
Click to expand...
Click to collapse
I would not send it for warranty repair if your able to boot into recovery - samsung will void warranty for good.
If you can go into downloader mode then I would do the above with a stock rom and PC odin. - preferbably the one that was shipped with ROM or last official update (for UK XXBLG8)
the PIT file determines the partitioning tables so will be needed. I don't know the standard size and type for SGS3 as not done on sgs3 (but have on other devices) - you'll have to research it; look in some of the stickies in general and development section. (this is better and make you more confident then being told and just relying on that. the stickies have somewhat silent agreement behind them. )
I am no expert but have been flashing long time with some breaks which have always been fixed by odin and repartition with PIT. AT the least it may fix it at the most it will completely kill it but less chance of samsung figuring out that you rooted it.
It is unlikely to be processor problem - even 20% processing power is ~ 300mhz quad i.e.1100mhz which should boot the system just take a while.
THANKS alot guys who replied. really helps me out
I've been going into the market for like 2 months now. Searching for something. I even changed the Internal SD but that didnt do the thing. I know its a Software problem and the only thing I haven't tried is the PIT file.
About the Processor thing. he says that "there is 20% chance of it being OK after that". Sorry if I mistyped that. and yeah i wont do that thing as the processor is very hard to replace. i have no idea how he will do it. but he really has fixed S3's in the past with doing this.
and the phone was with Samsung Service Center. My friend's close friend works there. He also tried everything. He is the one stating the Processor Problem
As for the condition.
The phone just boots up to the GT-i9300 and then reboots to there again... and again... and again.
goes to download mode NO PROBLEM!
Flashes the ODIN files either root or Home.tar with NO PROBLEM too. but it doesn't gives ANY errors. and still it doesn't do anything to it. Still gets stuck in the Bootloop.
If u guys need any more details regarding this. Do tell. please!
Plus:- I've too checked in the Stickies. NO ONE has this problem in which ODIN flashes fine but the software fails to do anythng good. it does WRITE on the Internal SD but doesn't do anything good. I can say that because when I root it. It sometimes goes into the Recovery.
AusafSal said:
I even changed the Internal SD
Click to expand...
Click to collapse
What exactly does that mean?
speedyjay said:
How did you manage to do an ota update with a rooted phone....usually a message comes up with something like (phone is modified, update cancelled) so how you managed to do that i dont know!....firmware files for the S3 only come as 1 .tar file because thats all thats needed, in terms of the .pit i suggest you search the stickies....theirs bound to be something in their. But im still baffled as to how you managed to do an ota update on a rooted phone :s
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Mine is also rooted with Samsung stock Rom and managed to ota update but had to reinstall cf-root again to install super user and cwm.
Sent from my GT-I9300T using xda premium
GUYS! My only way out is to flash a PIT File with 3 part file. I can't find the FULL ROM of it. Mine is U.K - BTU
16GB Pebble Blue unbranded GT-i9300
Just tell link me the file please! Then if it doesn't work I will give it off for Mother Board replacement since its the ONLY way out. And it doesn't really matter if I do the wrong one (but still I would really wish the PIT file would fix it) they will JUST REPLACE THE MOTHERBOARD!!
AusafSal said:
GUYS! My only way out is to flash a PIT File with 3 part file. I can't find the FULL ROM of it. Mine is U.K - BTU
16GB Pebble Blue unbranded GT-i9300
Just tell link me the file please! Then if it doesn't work I will give it off for Mother Board replacement since its the ONLY way out. And it doesn't really matter if I do the wrong one (but still I would really wish the PIT file would fix it) they will JUST REPLACE THE MOTHERBOARD!!
Click to expand...
Click to collapse
We don't have the file search sammobile.com or ask on their forum .
jje
I think BTU is general CSC code for all of uk.
Last official UK was BLG8
See here http://www.sammobile.com/firmware/?page=3&model=GT-I9300&pcode=BTU&os=1&type=1
Faryabs stock ROM thread hotfile links are down
---------- Post added at 02:46 PM ---------- Previous post was at 02:27 PM ----------
http://widefide.com/mobile/galaxy-s3-boot-problem-solution
try the pit from this link also has the procedure
AbuYahya said:
I think BTU is general CSC code for all of uk.
Last official UK was BLG8
No thats wrong .
---------- Post added at 02:46 PM ---------- Previous post was at 02:27 PM ----------
jje
Click to expand...
Click to collapse
JJEgan said:
AbuYahya said:
I think BTU is general CSC code for all of uk.
Last official UK was BLG8
Click to expand...
Click to collapse
No thats wrong .
---------- Post added at 02:46 PM ---------- Previous post was at 02:27 PM ----------
jje
Click to expand...
Click to collapse
so what was it ?
Related
YES, I KNOW THAT ALL QUESTIONS GO IN THE Q&A FORUMS BUT ITS HERE TO GET THE DEVELOPERS. SINCE I HAVEN'T FOUND ANY PERSON THAT CAN HANDLE SUCH SITUATION. (Please read ahead to take note of the problem clearly)
Please think of this as to help me (and other people who made these dead like this one). Don't comment "Questions go in the Q&A forum you friggin' NOOB". I know all of this stuff!!!!!
How it happened??:-
Rooted the phone using CF Root 6.4. Working "Perfectly"!
Did an OTA update (0.17MB) accidently. Encountered Random Reboots after then.
Then it won't boot at all
Stuck at the "GT-i9300" logo.
I HAVE THE NANDROID BACKUP BUT WON'T GO INTO THE RECOVERY SO ITS USELESS (is there any way to do it without the Recovery??)
Current situation:-
No Recovery. Tried Re-flashing the Official ROM and Re-rooting it. Either doesn't shows up or when shows up stays for 2 seconds and then goes to the GT-i9300 Logo.
Download mode is PRESENT.
Charges with NO PROBLEMS. Shows the Battery Logo going up and the Blue LED comes on too.
It once gave an error saying : "E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
It also gave a similar one in the above but with some other error. I didn't noticed it.
Odin Flashes WITHOUT any errors(no errors within the Odin). Writes the Firmware completely but unable to proceed due to some unknown reason.
I have tried these:-
Changed the NAND Memory Chip. Still the exact same problem. (Partition problem or something?)
J-Tagged it. No use!
Flashed all the Official ROMs via Odin.
Re-Rooted it. No use. Recovery isn't stable. Keeps rebooting after 2 seconds to the GT-i9300 Logo.
Please take this Question very seriously. Since its not just me with the same problem. There are many many other people with the same problem and with no solutions. Isn't this the main reason of XDA-Developer? Or is it just ROMs, Themes or Kernels? A person would be more happy if he gets his/her phone repaired instead of lying there on the desk and keeping those papers in there place and stop them being blown away from the fan!
For the moderators:- I know this isn't in the rules of the XDA to post a Question in the Android Development Section but this is here to summon all the ROM Developers and the Kernel Tweakers. Thank You for your valuable time!
Flash FULL ICS rom with .pit file
AusafSal said:
YES, I KNOW THAT ALL QUESTIONS GO IN THE Q&A FORUMS BUT ITS HERE TO GET THE DEVELOPERS. SINCE I HAVEN'T FOUND ANY PERSON THAT CAN HANDLE SUCH SITUATION. (Please read ahead to take note of the problem clearly)
Please think of this as to help me (and other people who made these dead like this one). Don't comment "Questions go in the Q&A forum you friggin' NOOB". I know all of this stuff!!!!!
How it happened??:-
Rooted the phone using CF Root 6.4. Working "Perfectly"!
Did an OTA update (0.17MB) accidently. Encountered Random Reboots after then.
Then it won't boot at all
Stuck at the "GT-i9300" logo.
I HAVE THE NANDROID BACKUP BUT WON'T GO INTO THE RECOVERY SO ITS USELESS (is there any way to do it without the Recovery??)
Current situation:-
No Recovery. Tried Re-flashing the Official ROM and Re-rooting it. Either doesn't shows up or when shows up stays for 2 seconds and then goes to the GT-i9300 Logo.
Download mode is PRESENT.
Charges with NO PROBLEMS. Shows the Battery Logo going up and the Blue LED comes on too.
It once gave an error saying : "E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
It also gave a similar one in the above but with some other error. I didn't noticed it.
Odin Flashes WITHOUT any errors(no errors within the Odin). Writes the Firmware completely but unable to proceed due to some unknown reason.
I have tried these:-
Changed the NAND Memory Chip. Still the exact same problem. (Partition problem or something?)
J-Tagged it. No use!
Flashed all the Official ROMs via Odin.
Re-Rooted it. No use. Recovery isn't stable. Keeps rebooting after 2 seconds to the GT-i9300 Logo.
Please take this Question very seriously. Since its not just me with the same problem. There are many many other people with the same problem and with no solutions. Isn't this the main reason of XDA-Developer? Or is it just ROMs, Themes or Kernels? A person would be more happy if he gets his/her phone repaired instead of lying there on the desk and keeping those papers in there place and stop them being blown away from the fan!
For the moderators:- I know this isn't in the rules of the XDA to post a Question in the Android Development Section but this is here to summon all the ROM Developers and the Kernel Tweakers. Thank You for your valuable time!
Click to expand...
Click to collapse
Download *.tar file from sammobile. As you have download option live, you can flash the same with help of Odin (for ICS)
Flash A Stock ICS ROM with Odin.
Get them from Sammobile or from a thread with stock rom collections.
Even get an Galaxy S3 .pit file for odin.
That will fix it.
Just to keep you happy, Most Samsung Devices are unbrickable. As long as it boots, even if its in bootloop it can get fixed with odin.
Keep us updated.
Sorry, even questions like this go into the Q&A, that's where the devs are, aswell..
Anyway, go to this website and create an account.
Download latest JB/ICS ROM and get a .pit file. Open Odin and flash away..
Done, your phone is working again..
Moved to Q/A, there is no reason to post this in the development section.
That is the problem!! No one in the Q&A section answered like u guys have :/
All I get told was "give it to the Service Center".
Anyway! Which PIT file should I flash. A Procedure would be nice. My Last firmware was 4.0.4 don't know the number.
Ohk so I found it from the Nandroid Backup. It was I9300XXBLG8 I also found something written as IMM76D
But this was before the OTA update. Can someone tell me about the .pit file for it?
Which .pit file should I use?
bump?
AusafSal said:
bump?
Click to expand...
Click to collapse
Changed the NAND Memory Chip how have you changed on board components .
Isn't this the main reason of XDA-Developer?
Nope its not a fix my phone forum .
JJEgan said:
Changed the NAND Memory Chip how have you changed on board components .
Isn't this the main reason of XDA-Developer?
Nope its not a fix my phone forum .
Click to expand...
Click to collapse
I gave it to a person here in the phone market. He also J-tags it. He had a spare broken motherboard. he changed the NAND Flash Memory Unit by himself. He said it is in the same condition as it was before. So no problem to the NAND Flash Memory Unit is done.
Suggest that you join sammobile as posted and use stock firmware .
Sammobile has a forum and you may get more information regarding a PIT file there .
jje
JJEgan said:
Suggest that you join sammobile as posted and use stock firmware .
Sammobile has a forum and you may get more information regarding a PIT file there .
jje
Click to expand...
Click to collapse
Hey! I didn't noticed its JJE!
I remembered u helped me alot in the previous Threads I made!
I downloaded the U.K version. Which is the one I had according to the Nandroid Backup I made.
I opened the "system.ext4.tar" by WinZip.
Saw a CSCVersion.txt file.
It had written "I9300OXABLG8" on it.
Also in the "build.prop" file (Opened by Notepad) I saw I9300XXBLG8 written aswell.
So I downloaded that one.
So I have only one Question:
Which PIT File should I put? :/
I see 5 of them :-
GT-I9300_mx_20120220.pit
GT-I9300_mx_20120322.pit
GT-I9300_mx_20120329.pit
M0_20120220.pit
mx.pit
Which one?
should be the last one...
Why don't you just spare yourself numerous headaches by sending the phone in for repair? Just say it died on you or something.
Theshawty said:
Why don't you just spare yourself numerous headaches by sending the phone in for repair? Just say it died on you or something.
Click to expand...
Click to collapse
No warranty bro! And I'll try tomorrow
btw If I do a wrong pit file. what are the consequences? :/
Mine is the 16GB one of United Kingdom. Non-Branded GT-i9300
AusafSal said:
No warranty bro! And I'll try tomorrow
btw If I do a wrong pit file. what are the consequences? :/
Mine is the 16GB one of United Kingdom. Non-Branded GT-i9300
Click to expand...
Click to collapse
Anyone??
AusafSal said:
Anyone??
Click to expand...
Click to collapse
Wrong Pit possible brick .
jje
AusafSal said:
No warranty bro! And I'll try tomorrow
btw If I do a wrong pit file. what are the consequences? :/
Mine is the 16GB one of United Kingdom. Non-Branded GT-i9300
Click to expand...
Click to collapse
If you flash the wrong pit file or if the pit file fails to flash, you might destroy your nand memory. The pit file is the partition table, hence you should be very careful.
Theshawty said:
If you flash the wrong pit file or if the pit file fails to flash, you might destroy your nand memory. The pit file is the partition table, hence you should be very careful.
Click to expand...
Click to collapse
Ok so Im gonna give it to the Samsung Service Center first thing. I don't wanna completely Eff up my device :/
Gonna take the phone from the person I gave to and hope to God that the NAND change has made that flash counter to Zero :/
Just as the Subject says. Only for knowledge purposes (though my phone is bricked :/ )
I get absolutely NO ERRORS while flashing ANY firmware for that matter through Odin. Though my phone is U.K Unbranded I9300XXBLG8.
It should boot-up but doesn't :/
Can't get into Recovery either. Not even a glimpse of it.
Stuck at the i9300 logo :/
Anyone care to help me and answer the following questions?
1. When is flashing a PIT File suitable? At what error u should do it?
2. Do I have a Bootloader/Recovery Problem or something?
3. Will J-Tagging help it?
4. Can someone tell me what is causing this problem? I haven't seen anyone with this problem yet. The firmware as well as CF Root flashes successfully (in Odin)... though the phone shows no positive results.
5. Should I go for PIT or J-Tagging or something else? I don't wanna risk it. All I know is that u should only flash a PIT file when u get the "Get PIT for Mapping" error. And J-Tagging is when the phone doesn't boots up. (I may be wrong)
Anyone with some suitable knowledge please drop by and help me.
Or someone who had this problem before.
My phone is a GT-i9300
CSC Version: I9300OXABLG8
Last Firmware was XXBLG8.
Pebble Blue non-branded and 16gb version.
THANK U
don't panic!
You should be able to fix it by just flashing a stock firmware with Odin
---------- Post added at 04:27 PM ---------- Previous post was at 04:25 PM ----------
you could also try removing the battery for a few minutes and then reinsert and try voting recovery again
Only go for a pit file, if you're planning to flash-lock the device, or repartition it, for that matter.
Don't panic, if your device is bricked, it's not, actually
You f***ed up your boot partition..
Goto sammobile.com/firmware, register, download latest U.K. firmware and then you should be good to go. Then you can root it and everything. DW about your SD, it'll stay as it is..
Hope I could help!
LG familyguy59/Beatsleigher
familyguy59 said:
Only go for a pit file, if you're planning to flash-lock the device, or repartition it, for that matter.
Don't panic, if your device is bricked, it's not, actually
You f***ed up your boot partition..
Goto sammobile.com/firmware, register, download latest U.K. firmware and then you should be good to go. Then you can root it and everything. DW about your SD, it'll stay as it is..
Hope I could help!
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
Yes I have a question about that. I'v been looking for the 3 part firmware. I couldn't find it there :/
I have flashed the exact same firmware u r telling.
Btw ur the only one who has said that doing the PIT file will not risk my S3 :/
AusafSal said:
Yes I have a question about that. I'v been looking for the 3 part firmware. I couldn't find it there :/
I have flashed the exact same firmware u r telling.
Btw ur the only one who has said that doing the PIT file will not risk my S3 :/
Click to expand...
Click to collapse
Lol. Why do you think that is?
CyanogenModded very skankily via XDA app. Skanky, indeed
AusafSal said:
Yes I have a question about that. I'v been looking for the 3 part firmware. I couldn't find it there :/
I have flashed the exact same firmware u r telling.
Btw ur the only one who has said that doing the PIT file will not risk my S3 :/
Click to expand...
Click to collapse
Flashing a pit is risky, and interruption could lead to hard brick, however if you do it right then all will be good, I used to flash with pit on the s1 regularly as it was a necessity coming from cm to gb, or something along those lines.
Just make sure you know what you are doing
PROGRESS!!!!!!!!!!
OK i think my phone is alive. I managed to get it into the CWM Recovery. But there seems to be one little problem. That I can't mount my SDCard. Even tried mounting in the "Mounts and Storage" Option. Im kinda hopeful but I don't know what to do now
Tried Factory/Data Resetting but that didn't do any good. Have i Effed my SDCard or something??? :/ :/
AusafSal said:
That I can't mount my SDCard.
Click to expand...
Click to collapse
any specific error messages about that in cwm?
Personally i used .pit with no issues. My story was that i changed the original partition layout and flashed stock .tar after that. CWM was functional but couldn't mount anything. So i just grabbed a .pit and flashed stock together with .pit - all fine.
And regarding the "interruptions" during .pit flashing - it was the same speed as flashing without .pit, at least for me.
If in your case it's simple filesystem corruption, connecting over adb and launching fsck on the messed up partitions should provide some results.
If you have Warranty use that and only do the below if you are desperate enough to buy a new motherboard or is going to trash your phone.
MistahBungle said:
Be very careful about using this method. This is to be used as a last resort only & if you have no warranty or no chance of blagging a warranty fix/replacement.
Do not attempt this if you have a simple case (the majority of the time) of 'Odin doesn't work'. These can almost always be fixed with perseverance & honesty about trying all possible steps to fix it repeatedly.
Click to expand...
Click to collapse
Very Important : If the first step(emmc_find_brick_start) if it doesn't freeze the recovery your problem is something else, so just go find another solution and leave this procedure alone. There's a note included(it was there from the moment this guide was created) above the first step which tells people to use the emmc_scan_all_partitions_once which basically does the same thing.
Major Disadvantages : You will loose space on the internal sdcard as the bricked sectors are repartioned, ie. Since the damaged blocks are removed by repartioning you can loose huge amount of memory space ranging from 100's of mb to more than 8gb, according to the amount of corrupted block's you have or by the position of the damaged blocks.
Further explanation : read this http://forum.xda-developers.com/showthread.php?p=42588924
Note : The brick scanning scripts are all just read operation so freezing mid flash is not gonna further brick the device, as there isn't any form of write operation.
This guide is for the eMMc brick situation where you will generally or somehow be able to go into download and recovery mode but whatever the rom maybe your phone doesnt boot into the OS.
CREDITS:ALL CREDITS GO TO hg42 FOR HIS WORK. (Please refer to the second post for the original thread and if you could buy him a beer for his work)
DISCLAMIER: I OR ANYBODY ELSE RELATED WONT TAKE RESPONSIBILITY FOR WHATEVER HAPPENS TO YOUR PHONE
hg42 also can generate pit files for other gt-i9100 variants you will need to send him your model specific pit files.
Note : Read the complete guide once to get an idea before attempting.
skip the following if you already have a custom kernel and cwm.
First and foremost lets get rid of the troublesome kernel which got you into this mess(the stock ics 4.0.4 kernel is still dangerous),so flash a custom kernel containing CWM or Siyah 5.0.1 tar, via Odin
The link for Siyah 5.0.1 For GT-i9100
Download and copy the first four files attached into sd card(via some other phone or a card reader)
Note :When I usually say run or flash something in recovery, it refers to using the option install via sd card.
Note:Flash 120824-151927-emmc_scan_all_partitions_once file to check wether you are actually effected by the brick bug and has got bricked blocks,if the procedure freezes you probably have bricked partition on your phone else if the flash completes successfully your problem is something else and this guide is not for you.Also you dont need to worry about the flash because its a fake flash just to find the bricked block(its called edify script).
Now hopefully you can boot into the CWM recovery,so boot into the recovery(Volume-Up + Home + Power)
1. From recovery flash 120824-151927-emmc_find_brick_start.
The program will start scanning the memory and will freeze at a particular value, consider "1000"(Remember you must note and use the value which you get).
You will have to turn off the phone now.
2. Get back into recovery and run 120824-151927-emmc_find_brick_end.
Again the program Will start running and will freeze at a value,consider at "3000"("Note the value you get here too").
Note: so if the values gotten are 1000 and 3000 you will have to select the pit file which will patch a brick between "a value lesser than 1000 and greater than 3000".
Note:Because of the repartioning you will loose space on your internal memory, this space contains the bricked blocks and hence removed from use by repartioning,so be carefull in selecting pit files select files as close as to your values.
3. Now download the correct zip file according to your type of phone 16gb or 32 gb
Note : This is the memory specified on the box of your phone and is not reffering to your external memory.
Download the zip file from the attachment according to your model type.
Note:For the sake of this guide i am using the 16gb version.(Use the correct one as per your model)
Now make sure that you went to download mode and is running Odin after the above steps.
4. Now unzip pits-i9100_16GB.zip and select the pit file which contains the value 1000 and 3000, which will be i9100_16GB_u1_02_20110310_emmc_EXT4--patched--brick-between-00713-and-03128-MB--DATAFS-moved-by-02304-MiB.pit
Note : Use the values which you got and select the appropriate file. Don't be an idiot and use the above file carelessly.
5. Then put the phone into download mode and using Odin flash the patched pit file which you unzipped in the above step.
Note :You must tick repartion and select pit file via pit option.
Note :You will lose data from internal memory while changing partition structure.
6. Disconnect the phone from the computer and go back into Recovery and pray and flash 120824-151927-emmc_scan_all_partitions_once
7. If the flashing freezes again you still have bricked blocks on your phone,if it completes successfully, hurray your phone is gonna recover.
8. Now perform an internal sd format (yes you will have to lose your data if you did'nt backup) and all the data/cache/dalvik wipe, to free your phone from clutter and to avoid any filesystem issue due to the repartioning.
Note:You have to perform all three wipes
9. And now install a rom of your choice(I recommend custom roms are better even though you can use stock roms).
10. Reboot and hopefully your phone will be fine again.
Note: 120824-151927-emmc_scan_all_partitions_infinitely is similar to 120824-151927-emmc_scan_all_partitions_once but its not neccessary you run this as its just the same operation but goes on infinitely checking.
Note : The above procedure might work for phone's having bricked or corrupted block's on their internal memory for other reasons other than the eMMc bug.
If anybody finds that there something wrong with the above guide please notify it in a post or PM me immediately.
Thanks to,
hg42 - for his impressive guide for recovery from eMMc on n7000, and all his valuable suggestions,please refer below post
Sun90 - for pointing out better layout suggestions (thanks a lot, i didnt know that the website version looked so ugly)
Using GT - I9100
Just hit the damn help button if I helped you.
This is the original thread by hg42, i won't recommend noobs to read this as it will confuse "you", and it is actually written for another model, but you could just thank him there or better still if you could buy him a beer you should go there
http://forum.xda-developers.com/showthread.php?t=1667886
Also note that I have made some changes to make the procedure as easy as possible and the safest, if you think otherwise please recommend it below.
The above method probably also works for the 8GB i9100g version of Samsung Galaxy S2 the pit files to be used are attached
NOTE VERY IMPORTANT: If any body wants hg42's updates(to all the pit files and zip files) which he will probably will do at certain time's you must visit his link directly, i would try my best to update the files here also for the Gt-i9100.
Just remember ...You can bump thread after 24hr....
Good guide dude.
Merry christmas and Happy new year
Paulius
Maybe you could post the link of the guys guide your "recycling".
theunderling said:
Maybe you could post the link of the guys guide your "recycling".
Click to expand...
Click to collapse
Surely I will do it, well the original post is for an other model actually and I didn't want the reader to get confused, will post the link to the actual post in the reserved post below my original post.
Edit : The original thread's link is posted in the second post, if you are able to provide any feedback I would appreciate it.
Using GT - I9100
Just hit the damn help button if I helped you.
Thanks , that helped me a lot , but I have a problem my phone enters random freeze many times , but it works fine after restart
any help ?
mm_farahat said:
Thanks , that helped me a lot , but I have a problem my phone enters random freeze many times , but it works fine after restart
any help ?
Click to expand...
Click to collapse
Sorry for the late reply but I think freezing issues are mostly related to the custom rom or because of the kernel.
Did you run the scan all partition zip file? If it completed successfully you don't have bricked section anymore if it fails you will have to do all the above *sigh* again
Sent from my GT-I9100 using xda app-developers app
Be very careful about using this method. This is to be used as a last resort only & if you have no warranty or no chance of blagging a warranty fix/replacement.
Do not attempt this if you have a simple case (the majority of the time) of 'Odin doesn't work'. These can almost always be fixed with perseverance & honesty about trying all possible steps to fix it repeatedly.
MistahBungle said:
Be very careful about using this method. This is to be used as a last resort only & if you have no warranty or no chance of blagging a warranty fix/replacement.
Do not attempt this if you have a simple case (the majority of the time) of 'Odin doesn't work'. These can almost always be fixed with perseverance & honesty about trying all possible steps to fix it repeatedly.
Click to expand...
Click to collapse
I will be quoting this into the main post, just to make it scarier, people with small problems shouldn't mess with this (but technically if there's no corrupted block, after doing step 1 the user won't be able to obtain a freeze which shows the possible start point, thereby validating the absence of bricked blocks, but I don't think everybody will have the sense to understand that,)
Edit : Edited OP to make it safer, users without corrupted block's will hopefully understand what I mentioned as "very important" in the beginning.
Sent from my GT-P6200 using xda app-developers app
Further explanation for the guide :
This thread was originally generated, by keeping in mind about the brickbug caused by emmc_cap_erase command line, but basically people can get bricked blocks(corrupted memory block's) without triggering the brickbug (Odin flash interruption, like pulling cable mid flash, and possibly several other way's) in that case also if the user can access cwm this method will be possibly very effective than blind flashing of pit files. (The original author hg42 was able to boot into Android after triggering the brickbug, but sudden crashes and force close made him realize that he still got bricked blocks which were causing the problem).
The only danger(and it really is very dangerous) involved is the flashing of pit files (as any normal pit files if it fails, it can further create more bricked blocks or even render the phone completely unbootable) as there will be major repartioning done.
Sent from my GT-I9100 using xda app-developers app
@ KBML The OP looks kinda messy from here.
The title could also cause confusion as it's supposed to bring a dead device from the dead.
We hardly see cases where somebody has a corrupted nand and is unable to enter recovery.
Some guys might flash this with because of a bootloop.
Scare them a little more, like highlighting the loss of 4 gb after trying this method, or something.
Sent from my GT-I9100 using xda app-developers app
gastonw said:
@ KBML The OP looks kinda messy from here.
The title could also cause confusion as it's supposed to bring a dead device from the dead.
We hardly see cases where somebody has a corrupted nand and is unable to enter recovery.
Some guys might flash this with because of a bootloop.
Scare them a little more, like highlighting the loss of 4 gb after trying this method, or something.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Great idea gastonw I will do that (I think one of the pit removes more than 8gb) please do suggest further improvements if needed, as to reduce further confusion.
Edit: Done all possible changes, I am wondering if I should insert a red alert signal this thread is potentially dangerous to all noobs.
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
Sorry for the late reply but I think freezing issues are mostly related to the custom rom or because of the kernel.
Did you run the scan all partition zip file? If it completed successfully you don't have bricked section anymore if it fails you will have to do all the above *sigh* again
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply,
when I run "120824-151927-emmc_scan_all_partitions_once.zip" it completes successfully but if I run "emmc_find_brick_start.zip" or "emmc_find_brick_end.zip" the device freezes in the same place !!
other question : which custom rom (will be stable) do you suggest to install on my device ?
Thanks
mm_farahat said:
Thanks for your reply,
when I run "120824-151927-emmc_scan_all_partitions_once.zip" it completes successfully but if I run "emmc_find_brick_start.zip" or "emmc_find_brick_end.zip" the device freezes in the same place !!
other question : which custom rom (will be stable) do you suggest to install on my device ?
Thanks
Click to expand...
Click to collapse
emmc_scan_all_partions_once skips the corrected sectors(ie because the bricked blocks are present in the disk(eMMc), but removed from the used partitions (hence the loss in storage space)), but the other two will scan without skipping any blocks, more exactly
emmc_scan_all_partions_once scans all your partions only, any unused or non partitioned blocks are not scanned.
"emmc_find_brick_start.zip" or "emmc_find_brick_end.zip" scans through every block always(even the bricked one's), so its natural it freeze's again at the same position.
Since a rom installation will only go directly to the partitions you are technically safe to install any Rom you wish. Just be careful not flash any pit files anymore as a new pit flash might include the bricked blocks back into the partitons rendering everything useless and possibly bricking your phone for good.
Hi,
My S2 is dead, can't start recovery nor start (boot installed rom).
The phone starts and I am able to start download mode but nothing else.
I am unable to push in the stock PIT file or anything else with ODIN it doesnt matter if I use older versions of ODIN.
Any ideas guys?
Ps. this just suddenly happened I think... might have flashed something... but from what I know it just died.
^^^^
For starters, stop mucking around with PIT's right now unless you want a permanently busted phone ?
You are nowhere near the stage where you need to start flashing PIT's; this is an absolute last resort where you're looking at motherboard replacement regardless of whatever you do (I.E you have nothing to lose).
Go to Hopper8's 'Odin troubleshooting' thread stickied in General & go through the troubleshooting steps (all of them if necessary & also multiple times if necessary) methodically.
If after trying all that stuff for a few days, then you can try flashing a PIT.
Thanks a lot
according to your guide i have to get into recovery..
but in my situation i can't access the recovery.
only download mode...
what to do?
^^^
1) Do not double post. You know which thread I'm talking about. You should know a lot better having been here for 4 yrs :-/
2) You don't even have an I9100, do you ?
MistahBungle said:
^^^
1) Do not double post. You know which thread I'm talking about. You should know a lot better having been here for 4 yrs :-/
2) You don't even have an I9100, do you ?
Click to expand...
Click to collapse
yes i do.
UPDATE EDIT: I have had some progress since my original post. Could you please read my latest posts, maybe you could help me out
Samsung S3 GT-I9300 purchased in the UK.
Its my sisters mobile and i think its soft bricked. She told me it just happened and she done nothing. I received the phone in stock condition.
The phone was orignally stuck solid on the first startup title screen and would not go any further. This is what i have done so far:
1. booted the phone into recovery mode which shows E:failed to mount /efs (invalid argument)
2. wiped cache partition
3. wiped data/factory reset
4. Installed Odin3-v3.04 and downloaded I9300XXDLIB_I9300OXFDLI1_I9300XXDLIB_HOME.tar
5. Connected phone to Odin and flashed the above .tar file which completed sucessfully.
The phone rebooted and it still got stuck on the first startup title screen.
I then looked for a different version and downloaded I9300XXEMF1_I9300EVREMF1_I9300BVEMF1_HOME.tar
this version also installed sucessfully onto the phone after repeating what i had previously done.
The phone reboots and now gets past the first title screen to the animated samsung logo but then keeps looping the animation.
The blue led in top left corner is on and is pulsing from dim to bright constantly while it loops.
Getting a little progress with the 2nd version i kept this on and patched CF-Auto-Root-m0-m0xx-gti9300.tar ontop of it.
Still the same looping when it gets to animated samsung logo
I dont know if this would of helped but i then tryed downloading the NV Generator to make a new IMEI file but cant get
the phone to respond to NV reader writer program.
Iv downloaded Adb and tryed to push the IMEI file onto the phone but it fails with error E: Signature Verification Failed
Im a beginner and this is the first time iv tryed to fix a phone and iv hit a brick wall and not sure now if im wasting my time.
can anyone help me get to the next stage?
Restore your backed up EFS would be the first step .
Do you actually have an I9300 as the NV tool is for a different phone
jje
Does your phone have a cwm or twrp now that u cf rooted it? If u do..then just flash a new rom over it after a clean wipe..(not stock) hopefully your phne should reboot to the new rom..otherwise ill think of another way..put the files into the extmem card using a card reader..or take a tar file of the new rom and flash it after clean wipe..works for me everytime i f up
JJEgan said:
Restore your backed up EFS would be the first step .
Do you actually have an I9300 as the NV tool is for a different phone
jje
Click to expand...
Click to collapse
I don't have a backed up EFS. its my sisters phone. with no backed up EFS is the phone unfixable then?
ardensedvirens said:
no backed up EFS is the phone unfixable then?
Click to expand...
Click to collapse
Correct, needs Service centre repair
Kalyan_121 said:
Does your phone have a cwm or twrp now that u cf rooted it? If u do..then just flash a new rom over it after a clean wipe..(not stock) hopefully your phne should reboot to the new rom..otherwise ill think of another way..put the files into the extmem card using a card reader..or take a tar file of the new rom and flash it after clean wipe..works for me everytime i f up
Click to expand...
Click to collapse
is cwm and twrp options in the recovery menu? where do I look to see?
the recovery menu only shows:
Android system recovery <3e>
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
sorry if this is not what you meant. im not sure what cwm and twrp is short for.
rootSU said:
Correct, needs Service centre repair
Click to expand...
Click to collapse
really? dam. how much would it cost to fix this problem?
JJEgan said:
Do you actually have an I9300 as the NV tool is for a different phone
jje
Click to expand...
Click to collapse
Yes I have I9300. I tried this after watching a video on youtube of a guy doing it for a Samsung s3. I cant post video link yet until I have 10 posts. sorry.
ardensedvirens said:
Yes I have I9300. I tried this after watching a video on youtube of a guy doing it for a Samsung s3. I cant post video link yet until I have 10 posts. sorry.
Click to expand...
Click to collapse
Samsung S3 can be like a dozen different phones, i9300 is one of them.
Glebun said:
Samsung S3 can be like a dozen different phones, i9300 is one of them.
Click to expand...
Click to collapse
Ahh yes I get you now. sorry lol.
what if I get a backup /efs from another phone. would I be able to mount it via sd card, then edit the efs to suit my phone so its not a clone of the phone iv got it from?
iv just flashed ODIN_CheckROM_V4_XXBLG8
it gives alot more options to fiddle around with. I think I could fix this phone to be honest if I keep looking into it.
OMG!! after installing the rom I just posted the phone has booted up and im in
I don't know what to do now.
is the efs fixed? should I make a backup?
how did this fix the phone?
ardensedvirens said:
Ahh yes I get you now. sorry lol.
what if I get a backup /efs from another phone. would I be able to mount it via sd card, then edit the efs to suit my phone so its not a clone of the phone iv got it from?
Click to expand...
Click to collapse
you won't be getting any help with that here since it can be used for illegal activities
---------- Post added at 11:20 PM ---------- Previous post was at 11:19 PM ----------
ardensedvirens said:
is the efs fixed?
Click to expand...
Click to collapse
you tell us - is the IMEI back?
make ioudedi
Glebun said:
you won't be getting any help with that here since it can be used for illegal activities
---------- Post added at 11:20 PM ---------- Previous post was at 11:19 PM ----------
you tell us - is the IMEI back?
Click to expand...
Click to collapse
Ok sorry I didn't know, I just thought it was just a missing folder that could be copyed.
the phone has now booted up
[Resurrection Edition] CheckROM EvoHD™ V4 [ODIN ROM]
this is what I flashed and it seems to have fixed it?
can anyone explain what has happened, I would like to understand what this rom was able to do that the others I flashed before couldn't.
if it booted it doesn't mean that EFS is okay
Glebun said:
if it booted it doesn't mean that EFS is okay
Click to expand...
Click to collapse
do you know what I could do from here to fix the efs?
should I try and pull anything from the phone onto my computer now that its booted?
when I goto status it says IMEI unknown
I know my imei number is behind the battery, how do I register it?
the fact that it booted changes nothing.
you can't repair the EFS if you don't have a backup
what is EFS? is it a folder? a file?
can anyone else explain a little more?
it is a folder.
to explain a little more - you need a new motherboard because every EFS folder is device-specific
I cant get the phone to connect to my wifi. Kies is not picking up the phone either.
is there a way I can download apps to my pc and load them onto the phone? I would like to try and get root explorer installed to see if there is an efs folder.
i tried EFS PRO. it has generated an efs.img file, is it useful?
this is what i done to get it, im not sure if its correct. can anyone tell me?
i went into Backup and selected Device Filter: International Variants
i ticked the block device box and clicked the backup button.
the operation was successful and it created the zip file with the efs.img inside it.
i have pulled this zip from the phone using QtADB_0.8.1_
does anybody know if this file can be used to fix the problem? or has it made a backup of a corrupt efs folder?
When I try to install stock rom over odin (or custom recovery) always apear text NAND WRITE START FAILD! I trying to install PIT file but same message apear!Any advice on that problem!Thx
Post the Odin log because this log will help diagnose the problem.
Make sure you're using a USB port on the motherboard that isn't a shared port (must be on the motherboard for pc and the single port on a laptop (not the side with 2 ports)).
Use the original Samsung cable that came with the phone or another high quality cable from another device manufacturer.
Use the correct drivers. You can usually install kies and uninstall on the it keeping the drivers.
Put the phone in download mode BEFORE connecting the phone to the pc to ensure the correct drivers are loaded.
Check the md5 hash of the firmware you are using. It must match the original.
Load the firmware into AP/PDA field of odin. If you need to use a .pit file you must load the pit file AND the firmware file into odin and select the "repartition" check box.
If you still encounter issues you can call time on it as it will be dead.
If you feel like investigating you can flash a firmware in sections and see which one fails and that will give you some idea of which part of the nand is corrupt.
shivadow said:
If you still encounter issues you can call time on it as it will be dead.
Click to expand...
Click to collapse
Hi Man! I read something similar from you in another thread. could you elaborate a bit more, why do you think these phones are dead? Im starting to think that too, but I trying to find confirmation...
My phone started to do weird things 2 months ago. I install a stable rom, 5 file stock ROM in odin (AP, BL, CP, CSC, PIT), or debloated stock etc. Everthing is OK for a few days or weeks.
Then my apps stop responding, or force close, even base apps. then the phone basically "falls apart", and bootloops
all i could do is keep flashing clean roms in odin so I can use it for a few weeks (or days).
but today I couldnt do it anymore.
only DL mode and TWRP started but TWRP doesnt see most partitions, cant even mount the external SD card.
Code:
blah-blah
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
odin says this, basically always some repartiton fail or write operation fail message
tried a lot of combinations, 1 and 5 file roms, with or without PIT, even tried nand erase, bootloader update and efs clear options as a last ditch effort...
are you saying too, that this is the eMMC dying? and what could cause it?
---------- Post added at 01:26 AM ---------- Previous post was at 01:10 AM ----------
shivadow said:
the nand is corrupt.
Click to expand...
Click to collapse
sorry in the meantime I found you in another thread
would you say this too to my phone?
https://forum.xda-developers.com/showpost.php?p=76148578&postcount=6
Flash the latest stock as a single tar file in Odin, not separate files.
I don't recommend a pit file until you have tried all different USB cables and USB ports.
The reason the phones die is because solid state memory is flawed, android is flawed and the software that is produced on a daily basis is flawed because android itself is flawed..
Since when has "losing all your personal belongings" been an acceptable fix because from what I remember there were days gone by that if you encountered such issues where the only remedy is to have a full on clean out of your history you were entitled to compensation.
Would you throw away all your photographs because you wanted to change the album cover?.
So the moral of the story is clear. Don't have your life stored in digital format if you want to keep it safe as one day, for definite, your phone, tablet, pc or whatever else will definitely crap out on you and leave you in the lurch. We live in a consumer world so electronics are cheaply built with components becoming exponentially cheaper and poorer quality with the people becoming ever greedier for a bigger profit margin and will wring every penny out of a total failure.
I hope that explains the situation a tad..
audit13 said:
Flash the latest stock as a single tar file in Odin, not separate files.
I don't recommend a pit file until you have tried all different USB cables and USB ports.
Click to expand...
Click to collapse
man i tried that, many ways...
like 40 different combinations.
but of course it doesnt help that theres no rescue firmware for the 9305, only the 9300
at least i couldt find one that is meaningfully recent.
so i could only try my providers 2015 and 16 or so 1 file firmware.
yes i waited for pit or nand erase options until i exhausted the more mild options...
but FYI odin tick the repartition option automatically if you add the 4file+pit firmware so i kinda feel it meant to be done that way.
ill do 1 more run in the weekend and post if magically something happens beyond fail.
---------- Post added at 12:52 AM ---------- Previous post was at 12:47 AM ----------
shivadow said:
Don't have your life stored in digital format if you want to keep it safe
I hope that explains the situation a tad..
Click to expand...
Click to collapse
i didnt do that i keep a very clean phone.
everything is in the cloud or on the ext sd.
i just want a working phone so I can call people lol
or a verdict that my phones dead.
kbuss said:
man i tried that, many ways...
like 40 different combinations.
but of course it doesnt help that theres no rescue firmware for the 9305, only the 9300
at least i couldt find one that is meaningfully recent.
so i could only try my providers 2015 and 16 or so 1 file firmware.
yes i waited for pit or nand erase options until i exhausted the more mild options...
but FYI odin tick the repartition option automatically if you add the 4file+pit firmware so i kinda feel it meant to be done that way.
ill do 1 more run in the weekend and post if magically something happens beyond fail.
---------- Post added at 12:52 AM ---------- Previous post was at 12:47 AM ----------
i didnt do that i keep a very clean phone.
everything is in the cloud or on the ext sd.
i just want a working phone so I can call people lol
or a verdict that my phones dead.
Click to expand...
Click to collapse
Hang on a sec.. You say its a i9305.. You can't flash i9300 firmware to a i9305 as they are totally different phones. It is probably the reason you're getting pit errors.
You MUST try a stock i9305 firmware.
shivadow said:
Hang on a sec.. You say its a i9305.. You can't flash i9300 firmware to a i9305 as they are totally different phones. It is probably the reason you're getting pit errors.
You MUST try a stock i9305 firmware.
Click to expand...
Click to collapse
man please no.
of course I flash the correct FW
its just the 9305 forum section is dead in this thematic, theres no information there about these problems.
I always flash 9305 FW
BTW one of the problems that theres no "rescue FW" for it, so I cant really try that.
its easier for normal s3 owners.
basically I adressed You because I saw you wrote several posts in this eMMC matter.
but thx anyway.
im enroute for s7 or oneplus 5t now
maybe in the future i try to revive my 9305 w a donored motherboard just for fun.
but based on what you say, its possible that most of these phones will get a faulty memory in the future, so there will be no donors either.
or you change the motherboard for a donored one and that dies too in a few months...
opinions?
kbuss said:
man please no.
of course I flash the correct FW
its just the 9305 forum section is dead in this thematic, theres no information there about these problems.
I always flash 9305 FW
BTW one of the problems that theres no "rescue FW" for it, so I cant really try that.
its easier for normal s3 owners.
basically I adressed You because I saw you wrote several posts in this eMMC matter.
but thx anyway.
im enroute for s7 or oneplus 5t now
maybe in the future i try to revive my 9305 w a donored motherboard just for fun.
but based on what you say, its possible that most of these phones will get a faulty memory in the future, so there will be no donors either.
or you change the motherboard for a donored one and that dies too in a few months...
opinions?
Click to expand...
Click to collapse
The problem isn't emmc. Android is buggered from basic. I recently found out that android is flawed and that is most likely the reason that all phones right across the board fail.