Hello, Today my friend gave me his I9300 to fix because it could not startup. What is happening: when I press power button I see first galaxy s3 welcome screen and then its shutdown or restarts and give again this first screen or it just froze on it. So first I flashed via odin latest CWM, then I tried to flash slimbean ROM 4.4. Try to do as written in instructions, first wipe, format, then flash, but when I try to flash phone just restarts and freeze on that first startup screen... Thats all... But intresting part is that when my friend took his phone to cutomer service to repair it, because he bought new phone like in 2013 december, they said that motherboard is bad, it just burned out because he downloaded some bad programs and that cause motherboard failure... But my friend always download his apps from playstore, so I think that is impossible to cause motherboard failure by playstore apps... And custom services not repairing it for free, they asking like almost 200USD in my country to repair it... So my friend just gave me his phone to try to fix... Any ideas?
PS when I tried flash via odin stock 4.3 I got error:
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> __XmitData_Write
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And I get BIG RED "FAIL" :/
I tried once again flash via odin, now it when successfuly BUT... When phone restarts and appears android icon with filling up blue bar it just go like 1/3 and freeze, then restarts and again android icon and at 1/3 it just freeze.
I tried again flash CWM and flash slimbeans 4.4 ROM, now it just flashed good, then I reboot phone and still... It is going restarting nonstop... Does it really coud be that motherboard burned ?
Flash full stock rom with odin then boot into recovery and factory reset.
Probable that efs or other partition is corrupt.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Flash full stock rom with odin then boot into recovery and factory reset.
Probable that efs or other partition is corrupt.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
I tried again flash stock via odin but no luck. This time when flash is passed and I get android icon with filling bar, this time it when fully and then froze and phone restarts, but now when I try to power it up after first welcome screen I get lying down android with red triangle and after some time phone shutdowns... And I cant get into stock recovery I get that android with red triangle..
When I try again flash stock via odin, sometimes I get FAIL when writing system sometimes it goes success but still cant power it on
Still trying to boot it but no luck... One time it looks almost wanted to startup because I was able to hear sound of welcome and logo starts showing but froze on very few frames of logo and then restarts....
scorpio1991 said:
Still trying to boot it but no luck... One time it looks almost wanted to startup because I was able to hear sound of welcome and logo starts showing but froze on very few frames of logo and then restarts....
Click to expand...
Click to collapse
Has a last resort try Rescue Firmware Recovery >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 <<
tallman43 said:
Has a last resort try Rescue Firmware Recovery >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 <<
Click to expand...
Click to collapse
Thank you very much for your post, I will try it ASAP
I tried 4.1.2 version but I get FAIL on odin while trying write system... I am going to try 4.3, maybe it works
I also tried 4.3 version, flashing via odin was successful but still froze on android icon with filling blue bar or make bar full then restarts phone and again shows that android icon with filling bar ... I do not know what else I can do
I read that maybe flashing 4.0.4 might help but I could not find working download link...
Flashed stock 4.0.4 but still, forever restarts, come up to android with filling bar and then restarts after some time :/ I dont know what else I can do...
up
If rescue firmware failed then emmc chip is probably toast, new motherboard required.
Sent from my GT-I9300 using Tapatalk
Where I can get new motherboard? And is it very difficult to change it?
Related
Hello everyone!
First of: I'm not sure if this is the right section, if not move.
Second of: thanks for the help you give, hope you can help me too.
I got a problem with my S3.
I was running Cyano10 Nighty (not the last one, i just update once a week) and in the last days my phone started to reboot randomly once in a while.
Today my phone start to reboot again, but it get stucked at the SG3 logo. I coudn't turn it off so i unpluged the battery. I tryed to reboot it again and nothing heppened, still stucked at the logo.
I tryed to run into CWM and then apply a recovery but I wasn't able to go into CWM. I can only make the phone run into Download mode.
I tryed to run Odin and apply some random firmware just to see if it woud work but when i plug in my S3 in donwload mode odin couldn't see it (and the whole Pc couldn't see it too).
I tryed to install kies first to get the driver, it didn't work.
I installed the S3 Toolkit and then installed the driver from here, it didn't worked.
so i'm asking: What can i do? I don't know if the phone must be functional while trying to install the drivers. Whereas i can find another S3 and finish the driver's installation, but then will Odin work?
Any suggestion is appreciate, Thanks for the help!
EDIT: I've noticed that when i put the phone on charge on screen appear a stuck battery logo, it doesn't get green and the grey spin doesn't spin.
Also in donwload mode i read this: (not sure if this can help)
Product name:
Custom binary download: No
Current binary: Samsung official
System status: Custom
Does this mean 100% no warranty?
bigallo said:
Hello everyone!
First of: I'm not sure if this is the right section, if not move.
Second of: thanks for the help you give, hope you can help me too.
I got a problem with my S3.
I was running Cyano10 Nighty (not the last one, i just update once a week) and in the last days my phone started to reboot randomly once in a while.
Today my phone start to reboot again, but it get stucked at the SG3 logo. I coudn't turn it off so i unpluged the battery. I tryed to reboot it again and nothing heppened, still stucked at the logo.
I tryed to run into CWM and then apply a recovery but I wasn't able to go into CWM. I can only make the phone run into Download mode.
I tryed to run Odin and apply some random firmware just to see if it woud work but when i plug in my S3 in donwload mode odin couldn't see it (and the whole Pc couldn't see it too).
I tryed to install kies first to get the driver, it didn't work.
I installed the S3 Toolkit and then installed the driver from here, it didn't worked.
so i'm asking: What can i do? I don't know if the phone must be functional while trying to install the drivers. Whereas i can find another S3 and finish the driver's installation, but then will Odin work?
Any suggestion is appreciate, Thanks for the help!
EDIT: I've noticed that when i put the phone on charge on screen appear a stuck battery logo, it doesn't get green and the grey spin doesn't spin.
Also in donwload mode i read this: (not sure if this can help)
Product name:
Custom binary download: No
Current binary: Samsung official
System status: Custom
Does this mean 100% no warranty?
Click to expand...
Click to collapse
I've seen Product name being empty before... I think it was something to do with a bad flash.
And, I'm assuming you used TA... but there's probably no warranty seeing the product name is wiped and it's "custom".
xSpeced said:
I've seen Product name being empty before... I think it was something to do with a bad flash.
And, I'm assuming you used TA... but there's probably no warranty seeing the product name is wiped and it's "custom".
Click to expand...
Click to collapse
What do you mean with TA?
I've flashed the CM10Nighty trought CWM, but i was using it since a long time.
The phone was correctly working and then i found it stucked on logo. No flash between the "working phase" and the "stucked on logo phase".
It was working and then stuck, but i didn't do nothing in between.
bigallo said:
What do you mean with TA?
I've flashed the CM10Nighty trought CWM, but i was using it since a long time.
The phone was correctly working and then i found it stucked on logo. No flash between the "working phase" and the "stucked on logo phase".
It was working and then stuck, but i didn't do nothing in between.
Click to expand...
Click to collapse
What happens when you try to boot into CWM?
Looks like you may have a corrupted NAND and need a new motherboard.
Only way to know, is if you try to flash it in Odin you'll get a PIT error.
If that's the case, then they should fix it under warranty
Mika83AC said:
What happens when you try to boot into CWM?
Click to expand...
Click to collapse
Notthing, if i hold VolumeUp+Home+Power the phone doesn't turn on, neither on logo screen
holdz said:
Looks like you may have a corrupted NAND and need a new motherboard.
Only way to know, is if you try to flash it in Odin you'll get a PIT error.
If that's the case, then they should fix it under warranty
Click to expand...
Click to collapse
I can't use Odin cause when i plugin the phone (in download mode) Odin and the whole PC can't see it. I have win8, i don't know if that's a problem for Odin or something.
Is there a way to check if i have driver/odin/any working without using the phone?
Is there a way to check if i have driver/odin/any working without using the phone?
By plugging another SGS3 in is all .
jje
I'm new to the Samsung platform wrt flashing/rooting etc and hope to revive my sister's galaxy s2 which suddenly stopped working. I did read some of the stickies and guides for unbricking etc, but I have some questions.
Some information that might be relevant:
It is a GT-I9100 phone which has previously (about 3 weeks ago) been successfully updated to the latest 4.1.2 rom using Kies (the end consumer way). The phone has never been rooted or flashed with other firmwares/kernels (it is completely stock).
While using the phone, it suddenly stopped responding (screen froze), had to pull out the battery to power it off.
After removing the battery the phone is stuck at the static Samsung Galaxy S2 bootlogo,
It does enter downloading mode, but it does not enter recovery mode (it should load a samsung recovery environment?)
Q:
With the above described symptoms, what is the first thing I should try, preferably without loosing warranty*?
I guess the answer will be by trying to flash 'a' stock rom using Odin.
If so, which version of the stock rom do I need when the HIDSWVER is unknown? Can I check the HIDSWVER somehow when the phone is in this state? The phone was purchased at Vodafone in the Netherlands.
I currently have downloaded I9100XWLSN_I9100XXMS2_I9100OXXLS8_NEE.zip, Not sure if I should use this one, and if this flashing a rom using Odin is the best way to start recovering this dead s2. I would really appreciate some suggestions
I've read something about the eMMC bug. Could this be related?
*the device is still in warranty but at the Vodafone store they say we would risk paying 36 euro for an unrepaired device because of some visual damage. For this reason I would first try to unbrick the device myself.
If u can get into recovery, a factory reset would have solved the issue.
Since u only have download mode, and you don't want to lose warranty, ur only option is to flash a stock firmware via Odin.
The firmware u downloaded will do.
Also read about eMMC Brickbug issue on 4.0.4 to know what it is.
"To err is human, to forgive is divine"
Sent from my SGS II
Its a soft brick. Flashing the odin package you download should do the trick. Once the phone has booted up successfully, perform a factory reset because flashing the odin package does NOT wipe the phone's data.
I just started flashing the rom as suggested.
(using oding bundled with the rom package, samsung drivers installed)
Unfortunately it fails to do so:
Code:
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Next thing to try is probably to flash a kernel as described in [GUIDE] Fix an unflashable or soft bricked GSII (I9100G/M/P/T VERSION INCLUDED)?
Should I use the provided ICS recovery files from the guide's OP when the phone is on 4.1.2?
Okay, tried flashing the kernel (unsuccesfull, fails to write).
Then tried repartitioning using a pit file, even that fails
I think this s2 has a hw fault. Now the download count is at 2, and instead of the static bootloader I get firmware update failure message.
Any way to get download count back at 0 for warranty in this state?Edit: Ok, searching for 300k ohm for usb jig
Other things I can try?
Otherwise this s2 is going to be a screen donor for another s2.
U have a NAND corruption it seems.
See this thread and the excellent post by @MistahBungle on stuff to do when Odin flash fails:
http://forum.xda-developers.com/showthread.php?t=2255936
"To err is human, to forgive is divine"
Sent from my SGS II
immortalneo said:
U have a NAND corruption it seems.
See this thread and the excellent post by @MistahBungle on stuff to do when Odin flash fails:
http://forum.xda-developers.com/showthread.php?t=2255936
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
Thanks for pointing to that checklist I actually already tried most of that list, except trying another usb cable.
Unfortunately, it still won't flash anything, it keeps freezing/failing when it tries to write a kernel/rom/pit file.
I've now tried:
- different versions of odin, all started as administrator, on:
- 2 different windows machines, both without kies being installed, using the Samsung USB drivers
- 3 different USB cables, which are known to work for data transfer
- validating the files-> jup are valid
Its a hard(ware/2fix) (soft) brick
edit: Added screenshots. Only when flashing the bootloader I get a progressbar @ the S2 screen, but Odin hangs for about 5 minutes at half of the Sbl.bin and then I get the 'Complete(Write) operation failed.' message again, progressbar still visible on S2 screen at about 5%.
Tutti-frutti said:
Thanks for pointing to that checklist I actually already tried most of that list, except trying another usb cable.
Unfortunately, it still won't flash anything, it keeps freezing/failing when it tries to write a kernel/rom/pit file.
I've now tried:
- different versions of odin, all started as administrator, on:
- 2 different windows machines, both without kies being installed, using the Samsung USB drivers
- 3 different USB cables, which are known to work for data transfer
- validating the files-> jup are valid
Its a hard(ware/2fix) (soft) brick
edit: Added screenshots. Only when flashing the bootloader I get a progressbar @ the S2 screen, but Odin hangs for about 5 minutes at half of the Sbl.bin and then I get the 'Complete(Write) operation failed.' message again, progressbar still visible on S2 screen at about 5%.
Click to expand...
Click to collapse
try att 'ODIN v1.83' and see
Sun90 said:
try att 'ODIN v1.83' and see
Click to expand...
Click to collapse
Didn't tried that version yet, however ,still no luck:
1. flashing stock jb rom (PDA) -> Stuck at BOOT in white [email protected] (boot.bin in odin log). No progress bar @ S2 screen. After 10 minutes I closed odin, rebooted phone in download mode
2. Then I tried flashing Siyah s2 v5.0.1 kernel -> Stuck @ zImage, see screenshot 'siyah-kernel.jpg'. No progress bar @ S2 screen. After 5 minutes I closed odin, rebooted phone in download mode. Download count increased with 1.
3. Then I tried flashing rom from the ICS recovery package (from the unbrick guide) -> same result as 1 ^^
Should I now try flashing a partition image table? Got one from a corrupt nand flash guide with stock and patched PITs (trying to find the link...)
Tutti-frutti said:
Should I now try flashing a partition image table? Got one from a corrupt nand flash guide with stock and patched PITs (trying to find the link...)
Click to expand...
Click to collapse
Which firmware are u trying to flash? Try a 3 part firmware (that comes as 3 files for phone, pda and csc).
Keep PIT files and re-partitioning as a laaaaast resort.
"To err is human, to forgive is divine"
Sent from my SGS II
immortalneo said:
Which firmware are u trying to flash? Try a 3 part firmware (that comes as 3 files for phone, pda and csc).
Keep PIT files and re-partitioning as a laaaaast resort.
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
I have tried to flash original stock jb firmware for nordic countries (I9100XWLSN from this thread), and the rom in the ICS recovery package (I9100XXLPH.zip) as instructed in the unbrick guide, being a 4 part firmware (bootloader/pda/phone/csc).
Only did try flashing pda and bootloader. I don't think flashing a phone/csc image would fix the odin write issue.
Try this:
http://forum.xda-developers.com/showthread.php?p=40708546
Sent from the little guy
gastonw said:
Try this:
http://forum.xda-developers.com/showthread.php?p=40708546
Sent from the little guy
Click to expand...
Click to collapse
Tried that on yet another other computer with another usb cable. No luck, won't start writing.
Eventually I tried re-partitioning, also hung, unplugged it after 10 minutes and.... *hard bricked*. But it was probably already dead because of defective nand. I don't think it had anything to do with the more common issues with using odin.
I've replaced the pcb from a damaged S2, now running slim bean 4.2.
Anyway, thanks for all suggestions.
Tutti-frutti said:
Tried that on yet another other computer with another usb cable. No luck, won't start writing.
Eventually I tried re-partitioning, also hung, unplugged it after 10 minutes and.... *hard bricked*. But it was probably already dead because of defective nand. I don't think it had anything to do with the more common issues with using odin.
I've replaced the pcb from a damaged S2, now running slim bean 4.2.
Anyway, thanks for all suggestions.
Click to expand...
Click to collapse
Thanks for sharing.
Please add [SOLVED] to the title of ur post then.
"To err is human, to forgive is divine"
Sent from my SGS II
Sent from the little guy
Lol
After all things I tried, I was actually relieved I had finally bricked it (although it was already sort of dead )
+ finally replaced my good old desire phone with an s2 because of the screen-donating-bricked-s2
Stuck at samsung logo
Stuck at samsung logo
running on siyah kernel v6.5b on Samsung galaxy s2 jb 4.1.2
tried to install alliance mod rom v8 and ended up at Samsung logo
tried factory reset and also the wipe cache partition dint work erased the dalvik cache too plus tried factory reset and
install a fresh stock rom the odin just gets hung and task manager marks it as not responding.what do i do now??
I have access to root..
Have i Bricked this phone??
So you can access recovery.
Sent from the little guy
Had the same problem, seemed like a NAND corruption to me on my phone since the progress bar on the main boot logo screen was slow and was stuck half the way, which otherwise used to slide pretty quickly, indicating that the phone is having trouble reading from its NAND flash.
Before the corruption I was running RootboX 4.1 with Dorimanx Kernel 9.38.
Was all prepared to do the ODIN flashing with latest firmware for my country, kernel and possibly a PIT flash with repartition , if in case else would have failed.
However to my skeptic mind a pretty safe suggestion read here somewhere on a thread, appealed for a while, and I was amazed to see the power of hunches.
Someone reported to have restored back his set, by SIMPLY taking the battery out and leaving it naked overnight. I did the same thing last night, and guess what, sipping the morning tea, I inserted the battery again and VOILA, its ALIVE....its ALIVE.....like any other FRANKENSTEIN defying all boundaries of logic.
So someone else in the same fix, should try it at first before jumping in the ODIN waters.
Lets see for how long does it lives, which TOUCHWOOD should be for a long time, till i save enough to a buy the S4 or Note3.
Cheers.
HyperEscape said:
Someone reported to have restored back his set, by SIMPLY taking the battery out and leaving it naked overnight. I did the same thing last night, and guess what, sipping the morning tea, I inserted the battery again and VOILA, its ALIVE....its ALIVE.....like any other FRANKENSTEIN defying all boundaries of logic.
Click to expand...
Click to collapse
sorry for thread revival, but resorting to this now that flashing stock rom and litening rom have both failed. was running stock 4.1.2 when phone ground to a halt then froze; after pulling battery the phone got stuck at the galaxy s ii logo screen. odin flash succeeded but same problem at reboot. phone gets preettty hot if i leave it stuck at the logo
phone was acting strangely for the past few days, no software changes and battery started depleting about 2-3 times faster than usual.
if leaving the battery out overnight doesn't fix it, am i hard-bricked?
Today Evening i went out with my friends, and we took few photos on my mobile.. After that my friend gave my mobile by stating it got stucked. I looked into it, yes it got stucked.. Then i forced it to restart.. it could not start, stucked on bootscreen. so i simply removed the battery and put the mobile into my pocket. once after i reached my home, i started the mobile.. again it got stucked in bootscreen. Then i gone into recovery mode and flashed the same rom (neatrom v4.7) on it from my sd card. Then it got booted, after sometime again it restarted automatcally and stucked on bootscreen. This time i could not even get into recovery mode.. so i downloaded the official stock firmware to install via download mode. Then i tried to flash through odin. it did not got flashed or anything happened for nearly half an hour. so i removed the usb cable from the laptop, immediately phone screen got off.. when i tried to switch on or get into download mode.. my phone does not responds, it is dead. i tried many ways like removing battery and inserting charger while pressing on power button then inserting the battery at the same time. what did i wrong? help me plzzz friends.. what should i do now to get back my mobile?
You plugged out your phone from PC while downloading from Odin?!?!?You completely bricked your device now.Maybe it couldn't flash the kernel or the firmware...Now phone is of course dead.You need to buy a new motherboard.BTW,what firmware did you flash?Do you have I9100 or other variant?
When you flashed a stock ROM, did you flash a pit file as well?
If no, get a jig so you can get to Download mode.
Sent from the little guy
GamingDj said:
You plugged out your phone from PC while downloading from Odin?!?!?You completely bricked your device now.Maybe it couldn't flash the kernel or the firmware...Now phone is of course dead.You need to buy a new motherboard.BTW,what firmware did you flash?Do you have I9100 or other variant?
Click to expand...
Click to collapse
I tried to flash this firmware "Base Firmware: I9100XWLSS (4.1.2)" from http://forum.xda-developers.com/showthread.php?t=1544487
i have I9100
gastonw said:
When you flashed a stock ROM, did you flash a pit file as well?
If no, get a jig so you can get to Download mode.
Sent from the little guy
Click to expand...
Click to collapse
no bro i did not flash a pit file.. i just flashed the md5 file from the firmware zip on pda. the flashing did not occur, it was got stopped in cache.img step.. i have waited for long.. it was showing same status. that's y i removed the cable from it.
Kumarankav said:
no bro i did not flash a pit file.. i just flashed the md5 file from the firmware zip on pda. the flashing did not occur, it was got stopped in cache.img step.. i have waited for long.. it was showing same status. that's y i removed the cable from it.
Click to expand...
Click to collapse
Your initial problem of bootloop could have been easily solved, I don't know what the other people do but when I gave my custom rom installed phone to my brother for a couple of days his friends played with it walla.. Bootloop.. Fix as usual was easy, a cache and dalvik wipe fixed it otherwise a nuke script and a flash would have worked.
But pulling the cable out before flashing is completed or unless terminated by the app itself is a bad thing to do, really bad...
Sent from my GT-I9100 using xda app-developers app
Service centre. You're paying.
I took my mobile to samsung service center, they checked and told that i need to change the motherboard.. which costs Rs.8500..
Kumarankav said:
I took my mobile to samsung service center, they checked and told that i need to change the motherboard.. which costs Rs.8500..
Click to expand...
Click to collapse
Maybe you can buy another on eBay,then you'll just give it to them to replace.Or change it yourself.Both ways you'll save money
Just get a jig and try.
Sent from the little guy
My GT-I9300 international galaxy S3 decided yesterday to brick itself, all of a sudden its stuck at the boot screen (white samsung ... text).
Tried to reboot into recovery but no go, when i hold the buttons it just continues to reboot and reboot, only showing the white text.
Tried to reboot into download and that worked, i though fhew, i got a berak and not all is lost.
In download mode it says current binary Samsung official even though i rooted and changed rom...
Product name is blank, Custom bin download is no, status is custom.
Tried to recover with kies but it complains that it cannot install new firmware (after it downloads the firmware, extracts, and all instruction followed).
Tried with odin (several original roms with my region and the one from kies) but with no luck, odin complains "There is no PIT partition.".
Tried to repartition with GT-I9300_mx_20120329.pit but then it does SET pit and hangs on "Get PIT for Mapping".
Is there any chance to save my phone ? I'm getting really desperate here.
Product name blank = sds. Only samsung service Centre can repair
Sent from my GT-I9300 using Tapatalk 4 Beta
try this
phenixdoc said:
My GT-I9300 international galaxy S3 decided yesterday to brick itself, all of a sudden its stuck at the boot screen (white samsung ... text).
Tried to reboot into recovery but no go, when i hold the buttons it just continues to reboot and reboot, only showing the white text.
Tried to reboot into download and that worked, i though fhew, i got a berak and not all is lost.
In download mode it says current binary Samsung official even though i rooted and changed rom...
Product name is blank, Custom bin download is no, status is custom.
Tried to recover with kies but it complains that it cannot install new firmware (after it downloads the firmware, extracts, and all instruction followed).
Tried with odin (several original roms with my region and the one from kies) but with no luck, odin complains "There is no PIT partition.".
Tried to repartition with GT-I9300_mx_20120329.pit but then it does SET pit and hangs on "Get PIT for Mapping".
Is there any chance to save my phone ? I'm getting really desperate here.
Click to expand...
Click to collapse
Hm, it worked for me once , try connecting it to odin in downlode mode and try installing cmd form there, it should work and help you get your phone back. Since original rom is not working. If that wont work then i am not sure. i need to get a better understand of what you did to it,for the phone to go into brick mode.
a_akash said:
Hm, it worked for me once , try connecting it to odin in downlode mode and try installing cmd form there, it should work and help you get your phone back. Since original rom is not working. If that wont work then i am not sure. i need to get a better understand of what you did to it,for the phone to go into brick mode.
Click to expand...
Click to collapse
No offence, but it's pointless. He has no product name. He needs a replacement Motherboard. It's nothing to do with anything he did.
rootSU said:
Product name blank = sds. Only samsung service Centre can repair
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks, gave it away to a shop, they're gonna try to hardware flash it (JIT/JIP ? i wasn't really listening).
Hello guys,
my friend's GT-I9300 was running stock rom. It has never been touched with root/custom roms.
One day he started his phone but it didn't and doesn't boot. After pressing the power button, it only shows a complete white screen. It shows not even the Samsung boot logo.
I can't access the stock recovery, but I can access the downloade mode. So I tried to flash the newest original firmware, but it failed. Odin shows the following error:
"There is no PIT partition".
I tried flashing with an one-parted firmware and with an three/four-parted one, but the result is the same. I tried different USB ports, different computers, older versions of odin...
So, is there any hope Maybe flashing a pit-file somehow?
Does it sound like a sudden death? There is unfortunately no warranty anymore
Thank you very, very much in advance! :good:
beginnerteur said:
Hello guys,
my friend's GT-I9300 was running stock rom. It has never been touched with root/custom roms.
One day he started his phone but it didn't and doesn't boot. After pressing the power button, it only shows a complete white screen. It shows not even the Samsung boot logo.
I can't access the stock recovery, but I can access the downloade mode. So I tried to flash the newest original firmware, but it failed. Odin shows the following error:
"There is no PIT partition".
I tried flashing with an one-parted firmware and with an three/four-parted one, but the result is the same. I tried different USB ports, different computers, older versions of odin...
So, is there any hope Maybe flashing a pit-file somehow?
Does it sound like a sudden death? There is unfortunately no warranty anymore
Thank you very, very much in advance! :good:
Click to expand...
Click to collapse
Looks like complete emmc failure does the screen look like this >> http://forum.xda-developers.com/galaxy-s3/help/problem-white-screen-black-lines-rain-t2467459 << if so I have seen many posts like this and not seen any resolved with a software solution.:crying: I suggest taking it to service for repair.
Try the dead boot recovery thread, search general forum, that will tell you if the motherboard is toast.
tallman43 said:
Looks like complete emmc failure does the screen look like this >> http://forum.xda-developers.com/galaxy-s3/help/problem-white-screen-black-lines-rain-t2467459
Click to expand...
Click to collapse
Thank you for helping! No, the screen is completely white. There are no stripes. See attachment.
boomboomer said:
Try the dead boot recovery thread, search general forum, that will tell you if the motherboard is toast.
Click to expand...
Click to collapse
Thank you very much! Do you mean this thread http://forum.xda-developers.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558 ?