Hello,
I had purchased the GS2 I9100G.
I was unaware that it was a G, and unaware of all the I9100 vs. I9100G difference
I wanted to root the device, I selected a rooted Kernel Image (zImage) but that was appropriate for I9100.
Back then, the phone hung at the Galaxy S2 Screen with the exclamation mark [Indicating the custom ROM, no big deal], but thing is the battery stopped charging.
Now I restored the phone, with its full phone capabilities (2g/3g), wifi etc...
Yet When I plug it in the Main or on USB it tries to charge then states "BATTERY Disconnected"
I rooted the device and went through /data/log to the kernel_recovery_log.txt
it says "Invalid Battery"
The Battery, yet, is the standard Lithium 1650mAH and it can charge on other phones. The charger is providing power till the metal pins (that the battery connects to, verified by a voltmeter).
Can Anyone Assist me in solving this? Appreciate a lot
Frederick84-lb said:
Hello,
I had purchased the GS2 I9100G.
I was unaware that it was a G, and unaware of all the I9100 vs. I9100G difference
I wanted to root the device, I selected a rooted Kernel Image (zImage) but that was appropriate for I9100.
Back then, the phone hung at the Galaxy S2 Screen with the exclamation mark [Indicating the custom ROM, no big deal], but thing is the battery stopped charging.
Now I restored the phone, with its full phone capabilities (2g/3g), wifi etc...
Yet When I plug it in the Main or on USB it tries to charge then states "BATTERY Disconnected"
I rooted the device and went through /data/log to the kernel_recovery_log.txt
it says "Invalid Battery"
The Battery, yet, is the standard Lithium 1650mAH and it can charge on other phones. The charger is providing power till the metal pins (that the battery connects to, verified by a voltmeter).
Can Anyone Assist me in solving this? Appreciate a lot
Click to expand...
Click to collapse
Seems like the battery is faulty. Have you checked if it stores charge?
hey, it does store charge indeed. I'm recharging it in other phones to use it meanwhile. It is embarassing since even the Samsung local support suspected a hw problem: they changed the IT Power CHIP and yet the problem persisted.
Personally I do not think it is a Hardware problem but rather a software issue
I have the same think with my own one (I9100G).
When the problem appear, i restart the device or turn it off to charge the battery.
I have several other bugs with this s2 i9100g.
As a matter of fact, the real problem was that support somehow messed with the phone's hardware without informing me. You only get such sort of problems in Lebanon. They changed the main board for free just to conceal their first mistake. I didnt mind after all )) I will close this thread now that I know what was the problem. But overall, a wrong firmware or Kernel cannot brick a Galaxy S2. Whatever you do on the software level, you can always restore it.
Frederick84-lb;23213055 But overall said:
Yes but you may need a JTAG service that costs money .
Restore means being able to boot to download mode soft bricked phone may lose boot to download mode so no way out of that .
jje
Click to expand...
Click to collapse
You can still boot to download using the USB JIG. And the USB JIG can be hand made.
Jig doesn't work every time. Plenty of instances of people on here being unable to get into download mode via usual method, and jig failing due to bootloader being corrupted/phone borked/etc.
As JJE said, phone can still be 'damaged' due to a flash gone wrong, and at the end of the day, Samsung won't fix this under warranty. You'd need to have it JTAG'd by a third party repairer. Either way you end up paying in these scenarios, if you don't want to go down the 3rd party JTAG route, Samsung will fix it if you pay them.
Frederick84-lb said:
You can still boot to download using the USB JIG. And the USB JIG can be hand made.
Click to expand...
Click to collapse
Man, I dunno if you got wot I meant: I had explicitly corrupted a kernel of a 9100G by using that of a 9100.
You wont see the download mode (android robot at all anymore). All you get is "Firmware Upgrade Encountered". Even when you plug in the Jig, "Firmware Upgrade Encountered" Screen remained. I concluded that this is also download mode, as much unusual as can be. Odin could see the phone, and I flashed a proper 9100G PDA and fixed things. You might have another perspective, but so far i considered that nothing worse could happen ))
Frederick84-lb said:
Man, I dunno if you got wot I meant: I had explicitly corrupted a kernel of a 9100G by using that of a 9100.
But overall, a wrong firmware or Kernel cannot brick a Galaxy S2. Whatever you do on the software level, you can always restore it.
Thats what you said and that was wrong .
Reason i pointed that out was dont want to go around giving some users that have not got a clue the false impression that a wrong firmware or kernel cannot brick a galaxy they can and do and USB jig does not work on later bootloaders .
jje
Click to expand...
Click to collapse
Related
Hi,
I tried flashing the phone with Clockwork. Part of the way through the flash it started writing in large letters going off the screen (weird text) then screen turned off, and back on to the installation progress, and then it shut off. No response from anything.
I did a battery pull after 10 mins to try to get the phone into recovery, but the phone does not respond to any combination of keys, battery pulls, and connecting the phone to the PC does nothing. The computer does not see the phone, the USB controller in hardware management does not refresh and show anything when connecting while holding both volume keys, and I have tried everything I could google.
There are no lights on the phone when pressing power, or any combination of recovery keys. Screen is permanently off.
Is there a way to force the phone to boot into any mode to get any recovery?
Thanks for the info.
The T-Mobile Vibrant and the Bell Vibrant are not the same and are quite incompatible actually. Did you flash something for the T-Mobile Vibrant instead? That could be your problem. If so, you'll need to be more careful in making sure it works on the "Bell Vibrant" since most of the stuff here is only tested on the US TMO Vibrant. The big letters are pretty common / normal when flashing a ROM kernel, modem, etc. It would help to know what OS version, ROM name / version you were running before and what filesystem (RFS, EXT2, EXT4). You might also mention what you tried flashing and the version of the Clockwork you were using if you can remember.
Even though you say it doesn't respond to charging, does that mean when you plug it into the "Wall Outlet" as well as the "Computer"? They have been known to produce different results. If you can get it to show the Green battery charge screen, there's a good chance you'll be fine.
Have you seen / read this thread before? - http://forum.xda-developers.com/showthread.php?t=848737
Failing that, you might wish to try the USB JIG method to try to see if that will get you into "Download Mode".
I was trying to flash from Stock 2.1 to Axura2259VE. Not sure what File System.
Only tried charging on computer with no response. will try a dedicated usb charger.
I was using the latest version of Clockwork as of today (Updated from app store, Jan 5).
I will put the jig together tonight if possible.
The phone is a GT-I9000M if that helps.
"If your phone screen is always black, that is it does not display the white Galaxy S/Samsung/AT&T logo when you switch it on, then sorry, this jig will not help you."
http://forum.xda-developers.com/showthread.php?t=819551
So, the Jig will not work for my situation. Anything else I can do? The phone was bought on classifieds and only bricked when updating.
Yes, that's the proper model # for the Canadian Vibrant. The US Vibrant is T959. I'm not sure Axura2259VE for T959 is compatible with the Bell Vibrant as the developer (Master) only owns a US model AFAIK. Try the dedicated charger that came with the phone plugged into a wall outlet with no extensions in between. Mind you, I've not troubleshooted a Bell Vibrant before so I don't know how it differs.
The Filesystem is RFS when stock, EXT2 if you applied the OCLF lagfix from RyanZA (not recommended) and EXT4 if you're running VooDoo. By asking about the filesystem, I was just wondering whether you had a lag fix installed / in-use before flashing. Does any of this apply to you?
I have installed lag fix following the tutorial from the app store, but it was for the intent of rooting the phone, which was already rooted. nothing else was run in the application unless it runs the lag fix by default. doubtful. I do not think it was applied.
Phone not under warranty because i bought it from classifieds. Hoping to get it fixed myself so will try to assemble the 301k resistance between pins 4 and 5 and try it tonight.
Any other ideas?
I really don't know what else to suggest to you. However, installation of the lagfix was unnecessary to have obtained root access on the phone. Rooting and Lagfixing are separate processes. If it was both rooted and lag fixed then which app from the Market did you use to apply the lagfix? Did you disable the lagfix before flashing?
RyanZA's OCLF 2.0.
I had it installed, never ran the lag fix, so I do not think this is the case here.
Thanks alot for the replies. I will post results tonight.
eugenek5 said:
I was trying to flash from Stock 2.1 to Axura2259VE. Not sure what File System.
Only tried charging on computer with no response. will try a dedicated usb charger.
I was using the latest version of Clockwork as of today (Updated from app store, Jan 5).
I will put the jig together tonight if possible.
The phone is a GT-I9000M if that helps.
Click to expand...
Click to collapse
The latest Axura flashes the bootloader to your phone. I suspect this is what the problem is and why you are unable to recover from it. I know absolutely nothing about the Bell Vibrant, but flashing a bootloader will affect how you get into recovery/download mode [I THINK]. You could try entering download mode the way U.S. Vibrant owners do, but I'm not sure if it will help. Sorry I don't have any helpful information, just thought I'd note the possible cause for your grief.
Interesting. I hadn't realized that or looked to see if that was the case. That definitely makes sense. Bootloader bricks are the hardest to recover from IMO (if you can at all). At least, in the future the OP should be able to tell if any rom if going to update the bootloader if it contains an "SBL.bin" in the package.
What?!? I'm suprised a ROM was packaged with the bootloader. To me flashing the bootloader is risky business. I'm not sure there's a way a consumer can recover from a failed bootloader
silow said:
What?!? I'm suprised a ROM was packaged with the bootloader. To me flashing the bootloader is risky business. I'm not sure there's a way a consumer can recover from a failed bootloader
Click to expand...
Click to collapse
I haven't flashed the new Axura because of the inclusion of the bootloader [SBL.bin] and truth be told I was shocked when I saw it in there.
So you guys are saying that the Jtag way does not work? I am sitting here trying to connect 2x150K resistors to pin 4-5 and it is not doing anything.
eugenek5 said:
So you guys are saying that the Jtag way does not work? I am sitting here trying to connect 2x150K resistors to pin 4-5 and it is not doing anything.
Click to expand...
Click to collapse
This method is to help you get into download mode if you are "hardware locked". In your case you have the wrong bootloader on your phone. At this point there is not much you can do yourself. The bootloader will need to be reflashed and as far as I know that's only possible with external equipment rigged into your phone.
I think other people were able to recover from the same incident. they just went to a phone technician(i don't know what do call that) and they just flashed a bootloader to your phone and it wil be flashed back to stock.
hey i'm not sure about this because i have only read about it and i really can't remember where because a lot of bricks already happened here.
Sent from my SGH-T959 using XDA App
Hard brick and fix not working
SO...
My vibrant is bricked, and I have my brother's vibrant to reference. (GT-I9000M)
This is a hard brick, with nothing showing up on the screen.
I have ordered the JIG thinking this would solve the boot issue, but with no luck.
I have tried the following:
- Up/Down - USB - Battery - Release keys
- Up/Down/Power - USB - Battery - Release keys
- JIG - Battery
- Battery - JIG
- USB - Up/Power/Menu - Battery
- USB - Down/Power/Menu - Battery
I have confirmed that the second vibrant that is working fine boots from the JIG successfully. I have also confirmed that the battery is working fine and tested on the other phone.
Cause: Battery pull on unsuccessful flash.
Please help! This phone has been bricked for 2 weeks and I want it back to working. I am out of ideas!
I had my phone hard bricked literally 4 days ago. I called T-Mobile and now I'm typing to you from the new phone. Call and see if the phone is still under warranty. If not then you'll have to pay Samsung themselves to fix the issue for you. I don't know what they'll charge, but I'll assume no more than $60 since its a software issue.
Sent from my SGH-T959 using XDA App
OuncE718 said:
I had my phone hard bricked literally 4 days ago. I called T-Mobile and now I'm typing to you from the new phone. Call and see if the phone is still under warranty. If not then you'll have to pay Samsung themselves to fix the issue for you. I don't know what they'll charge, but I'll assume no more than $60 since its a software issue.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Bought from Classifieds so not sure if it is covered. I have contacted repair places around Toronto.
Any advice would be awesome.
Not sure if there are differences for Download mode but the I9000 forum might be better than the US Vibrant forum.
eugenek5 said:
Bought from Classifieds so not sure if it is covered. I have contacted repair places around Toronto.
Any advice would be awesome.
Click to expand...
Click to collapse
I bought mine off craigslist from a private seller. Its worth a try. The most they'll say is no. Just don't say you rooted your phone.
Sent from my SGH-T959 using XDA App
Hey,
I've recently bought Galaxy S2.
It had problems with Android 2.3.3 and batter drain so I decided to upgrade to 2.3.4. I followed the instructions and I had to re-partition. Rebooted my phone into download mode, set re-partition option, PDA and clicked start (as said in the guide). It started doing stuff but after ~40-50 minutes there was no progress - it was stuck at "SET PARTITION". After an hour and 20 minutes still nothing and the phone started heating. So I unplugged the USB and removed the battery. Left it to heat down and tried to start recovery/download mode. It couldn't even start. As if it's really dead
How could you know for sure if a phone is bricked? What should I do know?
Is there anything I can try to see if I can bring it back to life or I should go to my provider and ask him to fix it?
I would be really grateful for any suggestions
Thanks in advance,
tftd
You have a bricked phone, you will need to buy another one.
I don't know which instructions you have been following, but it is not the ones here.
Over here, we tell people not to click 2 things. CLEAR EFS, and REPARTITION.
Clear EFS, kills the IMEI, and REPARTITION kills the phone.
Since the bootloader sits in the partition, you don't have bootloader, so no download mode either.
Yup, as the poster before me mentioned; your phone is totally hardbricked. Only way to fix it is through a jtag (requires some advanced hardware) or to send it to samsung on warrantee. Thats why they say not to play with pit files/partitions in the guides.
There is someone on youtube that can fix your device since he has the necessary tools, go to youtube and search for sgs2 jtag, you should find his video where he demonstrates the process, or you can do what the other posters said.
I'm on my phone using the xda application so I can't post the link for you.
Sent from my GT-I9100
Well from what i have read, bricking is really hard even if u check repartition.
Anyway iam a noob,but just search youtube and forums iam sure u will find something.
LiFE1688 said:
You have a bricked phone, you will need to buy another one.
I don't know which instructions you have been following, but it is not the ones here.
Over here, we tell people not to click 2 things. CLEAR EFS, and REPARTITION.
Clear EFS, kills the IMEI, and REPARTITION kills the phone.
Since the bootloader sits in the partition, you don't have bootloader, so no download mode either.
Click to expand...
Click to collapse
Now that's something I shall remember for the rest of my Android Phone life.
I sent my phone to customer service and hope they can fix it.
@achillies400 that dude is trained in small electronics (youtube/com /watch?v=zN7le4GmxZs) I saw what he does but I'm from Bulgaria and I'm not quite sure if the phone would get to USA and back to Bulgaria in one piece ...
For all the people coming after me:
DUDES! DON'T EVER RE-PARTITION! NEVER EVER!!!!!!
Thank you all for giving suggestions and helping me! Pretty much appreciated!
tftd said:
Hey,
I've recently bought Galaxy S2.
It had problems with Android 2.3.3 and batter drain so I decided to upgrade to 2.3.4. I followed the instructions and I had to re-partition. Rebooted my phone into download mode, set re-partition option, PDA and clicked start (as said in the guide). It started doing stuff but after ~40-50 minutes there was no progress - it was stuck at "SET PARTITION". After an hour and 20 minutes still nothing and the phone started heating. So I unplugged the USB and removed the battery. Left it to heat down and tried to start recovery/download mode. It couldn't even start. As if it's really dead
How could you know for sure if a phone is bricked? What should I do know?
Is there anything I can try to see if I can bring it back to life or I should go to my provider and ask him to fix it?
I would be really grateful for any suggestions
Thanks in advance,
tftd
Click to expand...
Click to collapse
MobileTechVideos have a jtag maybe they can repair.
Otherwise sent your device to an Samsung ServiceCenter!
looks like your simplest solution is the Jtag.
Is the samsung service centre offering a free repair? or are there any costs involved?
netchip said:
MobileTechVideos have a jtag maybe they can repair.
Otherwise sent your device to an Samsung ServiceCenter!
Click to expand...
Click to collapse
Yeah.. Still that's not an option for the moment - I live in Bulgaria .. :/
dullah said:
looks like your simplest solution is the Jtag.
Is the samsung service centre offering a free repair? or are there any costs involved?
Click to expand...
Click to collapse
Weelll... I hope it's free... though I'm prepared for a bill..
I didn't tell them I was flashing the rom... I told them it was heating up and suddenly it stopped working. Hope that's convenient enough
Check this link out.Its a list of places where you can get your phone jtaged incase it happens again.Near the bottom there is a contact for your country.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
okay, I hope it all works out
my phone has a busted up screen guys, claiming on house insurance, if i was to Clear EFS, kills the IMEI, and REPARTITION kills the phone. that would make it unbootable right??
I wouldnt give up jet
I ended up in quite a simular situation, i failed during flashing another pir, witch resulted in a non bootable phone with none ability to charge the battery. I tried to charge the battery elsewhere and was actually able to detect the phone in odin(none visual respons on the phone but stil). there should be a hope of reflashing it from here. could anyone explain why the screen goes blank even if its in downloadmode? is it related to imei/rom?
I would try this before sending in the phone. I talked to some guys in a norwegian servicecetre. If they are not able to connect it via usb to a pc and flash it they probably just change the motherboard!(EXPENCIVE) JTAG didnt seem to be the sollution of choice. changing the motherboard was rarely the sollution,but apperantly one customrom ****ed up both bootloaders(rom and imei) witch made them helpless reflashing it.
I bricked my phone because repartition was checked
I bricked my phone because I checked repartition. DO NOT CHECK BOX NEVER EVER EVER.
I sent back to t mobile and just said it would not turn on or charge and they repaired it free.
Since I have had my phone repaired I have flashed lots of custom roms with no major problems. Difference I have never once since clicked repartition and I made a backup of my EFS folder using Galaxy s unlock from android market also unlocked my s2 no probs
If you can detect it in Odin. Usually it is always able to be fixed.
But you may have to use someone else's full backup dump. But they may not want to give you their efs information of their phone.
Look online for galaxy s3 boot-loader etc.
This is for future people that need help
I'm not the first to ask this, I know, but the circumstances are very strange and I'm very desperate:
I've been running stock ICS (LPB) for while now and have not changed anything significant recently. Last night, I was reading a book on Google Play Books when the phone suddenly rebooted to the Samsung splash screen but no further. I took out the battery and attempted to restart and nothing. It will not charge, switch on, or enter download mode or recovery. I've tried it with another battery.
I thought these S2's were supposed to be virtually impossible to "hard brick" unless you did something really stupid? I can't find anyone who this has happened to while in normal use of the phone.
Any suggestions or am I really looking at sending the phone back to Samsung (who probably won't repair under warranty)?
Anyone who helps me fix it myself without the aid of Samsung or a jig will be rewarded!
TIA,
Dave
Contact Samsung. If your phone isn't responding to a battery you know is working and has charge, and you're not interested in using a jig (unlikely to do anything anyway), it's a hardware fault.
Dude calm down your phone will be repaired . When it comes to warranty i cant really comment on it as ur live in UK , in India the service center guys dont even know what the f**k ROOT is.
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
oinkylicious said:
Contact Samsung. If your phone isn't responding to a battery you know is working and has charge, and you're not interested in using a jig (unlikely to do anything anyway), it's a hardware fault.
Click to expand...
Click to collapse
May be something is wrong with the motherboard
dave_uk said:
I'm not the first to ask this, I know, but the circumstances are very strange and I'm very desperate:
I've been running stock ICS (LPB) for while now and have not changed anything significant recently. Last night, I was reading a book on Google Play Books when the phone suddenly rebooted to the Samsung splash screen but no further. I took out the battery and attempted to restart and nothing. It will not charge, switch on, or enter download mode or recovery. I've tried it with another battery.
I thought these S2's were supposed to be virtually impossible to "hard brick" unless you did something really stupid? I can't find anyone who this has happened to while in normal use of the phone.
Any suggestions or am I really looking at sending the phone back to Samsung (who probably won't repair under warranty)?
Anyone who helps me fix it myself without the aid of Samsung or a jig will be rewarded!
TIA,
Dave
Click to expand...
Click to collapse
As said no jig = Samsung and take your chance with warranty . No point asking XDA who will say use jig to get to download mode if possible as its the cheapest repair .##
jje
oinkylicious said:
Contact Samsung. If your phone isn't responding to a battery you know is working and has charge, and you're not interested in using a jig (unlikely to do anything anyway), it's a hardware fault.
Click to expand...
Click to collapse
Sadly this is the only conclusion I can come to but I guess I'm just in denial and trying to find any way to avoid sending it back to Samsung for 2-3 weeks!
If it had only held out until they released the S3, it wouldn't be so bad!
dave_uk said:
I'm not the first to ask this, I know, but the circumstances are very strange and I'm very desperate:
I've been running stock ICS (LPB) for while now and have not changed anything significant recently. Last night, I was reading a book on Google Play Books when the phone suddenly rebooted to the Samsung splash screen but no further. I took out the battery and attempted to restart and nothing. It will not charge, switch on, or enter download mode or recovery. I've tried it with another battery.
I thought these S2's were supposed to be virtually impossible to "hard brick" unless you did something really stupid? I can't find anyone who this has happened to while in normal use of the phone.
Any suggestions or am I really looking at sending the phone back to Samsung (who probably won't repair under warranty)?
Anyone who helps me fix it myself without the aid of Samsung or a jig will be rewarded!
TIA,
Dave
Click to expand...
Click to collapse
hardware; probably charge controller is fried, go to samsung customer center or call and they will fix it; you probably wont even have any personal files missing
Thanks people. Found a Samsung Service Centre near me with a turnaround of 1-2 days so not too bad after all...providing they don't notice my download counter!
D
Hi,
I think I may have bricked my phone somehow.
I have an international Samsung galaxy S3 I9300.
I'm using SiyahKernel S3 v1.7rc1 for dual-boot.
ParanoidAndroid 2.51 as primary ROM and Stock Samsung JB as secondary.
I have used the battery mod that comes with the kernel to speed up charging.
Here's what happened:
I have been using this setup for quite some time without any problems, but I have noticed lately that the phone have been rebooting automatically a few times. I didn't think too much about it. Annoying, but didn't happen often. Yesterday I put my phone on charging before I went to bed, and the phone was on. When I woke up the phone had turned off (alarm didn't go off either, so I missed work..) and the green charging notification light was stuck on permanently. I couldn't turn on the phone, it didn't react at all. I took out the battery to reset it, put it back in and tried again. The charging light was gone, but still couldn't turn it on. No sign of life.
I tried my battery in a friends phone and it worked fine. Also tried his battery in my phone, but no change. So seems the battery is not the problem. I have tried to keep the battery out for some time, holding buttons to drain all power, but no change.
It doesn't respond to any cable being plugged in either (USB or charging), so can't flash anything.
I'm lost here really. The phone doesn't respond to anything any more so I have no idea what to do to fix it. And I'm guessing if I send it back for repair they're not going to accept it as it's not stock. Would really appreciate any help.
Hi,
Are you able to put your phone in download mode at least? It happened with my old Galaxy S and the only thing worked was download mode.
If download mode is possible, try to flash a new rom via odin and than install siyah kernel to remove the 2nd rom partition.
Good luck.
Cheers
ramsorriso said:
Hi,
Are you able to put your phone in download mode at least? It happened with my old Galaxy S and the only thing worked was download mode.
If download mode is possible, try to flash a new rom via odin and than install siyah kernel to remove the 2nd rom partition.
Good luck.
Cheers
Click to expand...
Click to collapse
No, can't enter download mode either
You're boned....
Unless you can enter download mode or CWM theres nothing to be done....
Send it to a Samsung Service center.
Overdriving the battery charging circuit comes with a cost. That is it and now your phone is FUBAR.
Have you tried shouting at it loudly and calling it a few names? You're out of luck, it seems (needs returning to Samsung) but at least it'll make you feel better!
Simonetti2011 said:
Send it to a Samsung Service center.
Overdriving the battery charging circuit comes with a cost. That is it and now your phone is FUBAR.
Click to expand...
Click to collapse
Hmm that sucks. Back to my iPhone 1 then
But will they not be able to see that It's not stock firmware on it?
Kryten2k35 said:
Have you tried shouting at it loudly and calling it a few names? You're out of luck, it seems (needs returning to Samsung) but at least it'll make you feel better!
Click to expand...
Click to collapse
I'm usually a calm person, but I'll try that shouting and see if it makes me feel better. Don't have the money for a new S3 so shouting will have to do.
star85 said:
Hmm that sucks. Back to my iPhone 1 then
But will they not be able to see that It's not stock firmware on it?
Click to expand...
Click to collapse
If they can't boot the phone, they'll simply replace the defective board, restore your original IMEI, wipe your phone and send it back to you.
At least that is what has happened to other users whose phones had the same fault as yours, and for the same reasons.
I guess your phone is still under warranty, isn`t it? If so, just get it repaired under warranty and let this be a lesson that nothing comes free, including fast-charging the battery.
Simonetti2011 said:
If they can't boot the phone, they'll simply replace the defective board, restore your original IMEI, wipe your phone and send it back to you.
At least that is what has happened to other users whose phones had the same fault as yours, and for the same reasons.
I guess your phone is still under warranty, isn`t it? If so, just get it repaired under warranty and let this be a lesson that nothing comes free, including fast-charging the battery.
Click to expand...
Click to collapse
This ^
Plus, the phone is knackered, so you don't have anything to lose by trying, really!
Man: had this happen to me today as well, and now that I notice, I see LOTS of similar reports.
FWIW: Most people weren't "fast charging" their phones; there's clearly just a hardware fault somewhere.
What was your official stock firmware you were running?
Sent from my GT-I9300 using xda app-developers app
Simonetti2011 said:
If they can't boot the phone, they'll simply replace the defective board, restore your original IMEI, wipe your phone and send it back to you.
At least that is what has happened to other users whose phones had the same fault as yours, and for the same reasons.
I guess your phone is still under warranty, isn`t it? If so, just get it repaired under warranty and let this be a lesson that nothing comes free, including fast-charging the battery.
Click to expand...
Click to collapse
Thanks for your help. Yes it's still under warranty.
Hi
This morning I took my phone off charge and for some reason it wouldn't switch on and the blue LED was flashing, thinking it'd just crashed I removed and re-inserted the battery but this had no effect. I have since tried the phone with two other batteries, tried to boot it into recovery mode and also download mode and also plugged it into a PC but nothing has worked. The phone has showed no signs of life (no blue LED flashing since I removed the battery this morning) through all of these processes but I have noticed the battery has been warming up.
I tried calling Samsung to get the phone repaired but alas it's now out of its 2 year warranty so I will have to pay to get it repaired. As I've been due an upgrade for a while I will get this rather than paying for it to be repaired.
But just in case has anyone any ideas of any thing else I could try to revive the phone? I heard about the USB jig method but wasn't sure if it'd be any use in my situation?
The phone is isn't rooted and running 4.3 Jelly Bean.
Any advise appreciated.
Zammo76 said:
Hi
This morning I took my phone off charge and for some reason it wouldn't switch on and the blue LED was flashing, thinking it'd just crashed I removed and re-inserted the battery but this had no effect. I have since tried the phone with two other batteries, tried to boot it into recovery mode and also download mode and also plugged it into a PC but nothing has worked. The phone has showed no signs of life (no blue LED flashing since I removed the battery this morning) through all of these processes but I have noticed the battery has been warming up.
I tried calling Samsung to get the phone repaired but alas it's now out of its 2 year warranty so I will have to pay to get it repaired. As I've been due an upgrade for a while I will get this rather than paying for it to be repaired.
But just in case has anyone any ideas of any thing else I could try to revive the phone? I heard about the USB jig method but wasn't sure if it'd be any use in my situation?
The phone is isn't rooted and running 4.3 Jelly Bean.
Any advise appreciated.
Click to expand...
Click to collapse
If you cannot get into recovery or download mode there is not alot of hope im sorry.
Sounds like sds and the emmc chip has died.
You could try a jig as they are only a few dollars but personally I would take the upgrade.
I thought as much. I've ordered a USB jig anyhow, its only £2 so im not to bothered if it doesnt work.
The annoying thing is that when I bought the phone and there was the scare surrounding sudden death syndrome I got an app that checked my emmc chip and it said it was susceptible. However I thought the issue was fixed with a firemware update, so I never tried to get it exchanged (not that I think my carrier or Samsung would have allowed me to do this).
Zammo76 said:
I thought as much. I've ordered a USB jig anyhow, its only £2 so im not to bothered if it doesnt work.
The annoying thing is that when I bought the phone and there was the scare surrounding sudden death syndrome I got an app that checked my emmc chip and it said it was susceptible. However I thought the issue was fixed with a firemware update, so I never tried to get it exchanged (not that I think my carrier or Samsung would have allowed me to do this).
Click to expand...
Click to collapse
The fix stopped the rom etc from corrupting it all at once and give the device longer life but as its a hardware issue its still able to die.
Darke5tShad0w said:
The fix stopped the rom etc from corrupting it all at once and give the device longer life but as its a hardware issue its still able to die.
Click to expand...
Click to collapse
Ah right, out of curiosity were Samsung allowing people with the susceptible emmc chips to exchange the phone?
Zammo76 said:
Ah right, out of curiosity were Samsung allowing people with the susceptible emmc chips to exchange the phone?
Click to expand...
Click to collapse
Im not fully sure, atleast in my country no, only if it failed within the warranty period.
Ok thanks. Im thinking of buying a smashed s3 off of ebay and switching its main board with my phones one. Providing its emmc's chip is ok would this fix my phone?
Provided the smashed phone works fine otherwise then of course.
As an update on this.
I decided to try my luck and wrote a letter to Samsung complaining that despite taking really good care of my phone and through no fault of my own it stopped working, just 2 months out of warranty. I told them that I suspected it to be the emmc chip as this had been identified as a problem with S3's manafactured at the time I bought mine but my carrier (EE) had refused to replace it even though I had ran an app that said my phone had the susceptible chip.
Samsung amazingly agreed to repair my phone free of charge and yesterday I got it back, fully working!
The fault that was listed on the paper work was:
Replacement faulty Ic/ Pa/ Filter
I'm not really sure if that another name for the emmc chip? But regardless I'm very greateful for Sasmung excellent customer service.
Glad it worked out for you, have you run the insane chip test on your new motherboard?