Related
Hello there. I´m worried because my Evo 3D CDMA won´t boot or charge at all. The red light is not turning on. All happened apparently with no reason, I left the phone there a few minutes, then it was dead. Maybe if I tell what I did before can help...
I had installed a few minutes ago the Virus ROM 3.0, I flash roms almost every 3 days, so I´m used to it. So, it worked fine after installation. I began to play a few games, when the battery died. I conected it to the charger, waited a few minutes and turned it on again (still plugged to the charger), it started normally. Then I had to answer a phone call, when I got back, the phone was dead!! "Maybe the charger got disconected" I thought. But the charger was fine, I tried many different chargers and nothing.
The red light is not turning on.
I´ve tried many different buttons combinations (camera+power), etc. I can´t get into fastboot (power+volume down). I´m S-ON HBOOt 1.5. So there is no CWM. I have to use windows CMD every time I need to flash Something.
Can this be a battery issue (considering that when the phone died it had about 3% of battery), or is it a fried motherboard, perhaps? It had happened before, but I removed the batttery for a few minutes and It worked.
But I´m scared because the phone is brand new, and it has less of two months of average using. And don´t tell me to go to Sprint service since I´m in El Salvador and I got the phone at eBay.
Any help would be appreciated. Thanks.
My fiest EVO 3d did this, the guy told me that it was a lemon. I got a instant replacement, not sure if its in the discovered mode by a dev,
Pull the battery, unplug charger, then battery back in and try turn on.
Sent from my PG86100 using XDA App
mariosaigon said:
Hello there. I´m worried because my Evo 3D CDMA won´t boot or charge at all. The red light is not turning on. All happened apparently with no reason, I left the phone there a few minutes, then it was dead. Maybe if I tell what I did before can help...
I had installed a few minutes ago the Virus ROM 3.0, I flash roms almost every 3 days, so I´m used to it. So, it worked fine after installation. I began to play a few games, when the battery died. I conected it to the charger, waited a few minutes and turned it on again (still plugged to the charger), it started normally. Then I had to answer a phone call, when I got back, the phone was dead!! "Maybe the charger got disconected" I thought. But the charger was fine, I tried many different chargers and nothing.
The red light is not turning on.
I´ve tried many different buttons combinations (camera+power), etc. I can´t get into fastboot (power+volume down). I´m S-ON HBOOt 1.5. So there is no CWM. I have to use windows CMD every time I need to flash Something.
Can this be a battery issue (considering that when the phone died it had about 3% of battery), or is it a fried motherboard, perhaps? It had happened before, but I removed the batttery for a few minutes and It worked.
But I´m scared because the phone is brand new, and it has less of two months of average using. And don´t tell me to go to Sprint service since I´m in El Salvador and I got the phone at eBay.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
I saw some tread about rom manager app causing sudden death.did you have it?what kernel were you on?
Sent from my HTC EVO 3D X515m using xda premium
josephnero said:
I saw some tread about rom manager app causing sudden death.did you have it?what kernel were you on?
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
No, I didn´t have that app, and I had Chad Goodman´s Anthrax Kernel V2...
mariosaigon said:
No, I didn´t have that app, and I had Chad Goodman´s Anthrax Kernel V2...
Click to expand...
Click to collapse
Might be the battery man... I would swap to another battery.
reaper24 said:
Might be the battery man... I would swap to another battery.
Click to expand...
Click to collapse
I hope it is only the battery, because it´s not expensive... But do you think I should try charging the battery manually? You know, some people say it´s a good way to restore a battery,,,,
maybe the battery or bricked phone
reaper24 said:
Might be the battery man... I would swap to another battery.
Click to expand...
Click to collapse
How did you activate it? Did you download a GSM version of the rom or a CDMA one.....
reaper24 said:
How did you activate it? Did you download a GSM version of the rom or a CDMA one.....
Click to expand...
Click to collapse
Actually we have CDMA in El Salvador too... The rom installed fine, and was running fine, the phone died while.. let me remember... Ah, I was installing a Chainfire 3D plugin, but I had never problems with Chainfire in any rom before, so the big deal is,
1) Is it a faulty battery? I remember once, the battery died the red light started blinking. Maybe the battery is bad.
2) Is it hard bricked? or soft bricked?
3) If it is bricked, is there a way to restore it?
mariosaigon said:
Actually we have CDMA in El Salvador too... The rom installed fine, and was running fine, the phone died while.. let me remember... Ah, I was installing a Chainfire 3D plugin, but I had never problems with Chainfire in any rom before, so the big deal is,
1) Is it a faulty battery? I remember once, the battery died the red light started blinking. Maybe the battery is bad.
2) Is it hard bricked? or soft bricked?
3) If it is bricked, is there a way to restore it?
Click to expand...
Click to collapse
I doubt it was bricked due to the phone wouldn't boot at all when you got it.. Did you update the radios or software when you got it? I know the latest software for CDMA is 2.17 virus R75 to R80 3.0 eternity is based and built off it...
My guess is the battery is shot I would try that you can find them cheap..... So the red light doesn't come on at all when you plug it in with the battery in the phone..?
You would really have to spank a phone to brick it... If the hardware isn't broken you should be able to restore a bricked phone... That takes skill and alot of reading....
What other chargers did you try? Could be the usb cord is bad or the charger... Battery could be no good. Last thing it could be is a bad charger port... Maybe..
reaper24 said:
I doubt it was bricked due to the phone wouldn't boot at all when you got it.. Did you update the radios or software when you got it? I know the latest software for CDMA is 2.17 virus R75 to R80 3.0 eternity is based and built off it...
My guess is the battery is shot I would try that you can find them cheap..... So the red light doesn't come on at all when you plug it in with the battery in the phone..?
You would really have to spank a phone to brick it... If the hardware isn't broken you should be able to restore a bricked phone... That takes skill and alot of reading....
Click to expand...
Click to collapse
I got the phone brand new. I have
1) Unlocked bootloaders via HTC metod
2) Installed tons of roms (I`m a flashaholic)
3) Never installed an incorrect ROM or kernel.
And yes, no light at all when I plug the phone to the charger. it`s totally dead.
UPDATE
I have discovered something about a RUU. check it out:
"This is a link to the Evo stock RUU and a description of what it does. It isn’t anything that wasn’t available already online, I just like providing a central location to get everything.
What is this?
RUU is the way that our phones are flashed at the factory. It flashes all the factory images on to your phone.
What can I do with it?
You can use this to “unroot” your phone before sending it in for warranty work.
Use it to flash back to stock if you are having any random issues on your phone that you can’t fix.
It can 100% flash your phone back to how it came from the factory. As long as your phone turns on at all (even if it’s not booting) then you should be able to save it by using this.
This means your phone is virtually unbrickable, unless you go flashing a radio or SPL or something that you shouldn’t.
How do I use it?
Download the file below and run the exe.
What else do I need to know?
This will set your phone back to 100% bone stock.
You don’t need to run this unless you are trying to return your phone to stock. You won’t get anything special from running it."
IF I RUN THIS PROGRAM, IS IT POSSIBLE I CAN GET MY PHONE BACK TO LIFE?
mariosaigon said:
I got the phone brand new. I have
1) Unlocked bootloaders via HTC metod
2) Installed tons of roms (I`m a flashaholic)
3) Never installed an incorrect ROM or kernel.
And yes, no light at all when I plug the phone to the charger. it`s totally dead.
UPDATE
I have discovered something about a RUU. check it out:
"This is a link to the Evo stock RUU and a description of what it does. It isn’t anything that wasn’t available already online, I just like providing a central location to get everything.
What is this?
RUU is the way that our phones are flashed at the factory. It flashes all the factory images on to your phone.
What can I do with it?
You can use this to “unroot” your phone before sending it in for warranty work.
Use it to flash back to stock if you are having any random issues on your phone that you can’t fix.
It can 100% flash your phone back to how it came from the factory. As long as your phone turns on at all (even if it’s not booting) then you should be able to save it by using this.
This means your phone is virtually unbrickable, unless you go flashing a radio or SPL or something that you shouldn’t.
How do I use it?
Download the file below and run the exe.
What else do I need to know?
This will set your phone back to 100% bone stock.
You don’t need to run this unless you are trying to return your phone to stock. You won’t get anything special from running it."
IF I RUN THIS PROGRAM, IS IT POSSIBLE I CAN GET MY PHONE BACK TO LIFE?
Click to expand...
Click to collapse
Your phone would have to be on like in Hboot or in a rom....And need to fastboot flash stock recovery... or make it a zip file to do....
Also you would have to relock your phone.. Once it was relocked you could run this...
I am only going off what I have seen haven't had to relock my phone to throw stock on it... I have seen some guides in the dev section to do it.. But the phone has to be on to get the sucker to work,,,,
My guess is the battery is no good... If it's brand new I don't know why the charger port would be bad in it... I would try another battery first man...
reaper24 said:
Your phone would have to be on like in Hboot or in a rom....And need to fastboot flash stock recovery... or make it a zip file to do....
Also you would have to relock your phone.. Once it was relocked you could run this...
I am only going off what I have seen haven't had to relock my phone to throw stock on it... I have seen some guides in the dev section to do it.. But the phone has to be on to get the sucker to work,,,,
My guess is the battery is no good... If it's brand new I don't know why the charger port would be bad in it... I would try another battery first man...
Click to expand...
Click to collapse
OK, before I commit suicide I will try to get a new battery (I`ll have to buy it at eBay, since no once else has this phone here) That should be the only solution. Thanks for you time. I´ll let you know what happened as soon the battery comes (a month, maybe)
mariosaigon said:
OK, before I commit suicide I will try to get a new battery (I`ll have to buy it at eBay, since no once else has this phone here) That should be the only solution. Thanks for you time. I´ll let you know what happened as soon the battery comes (a month, maybe)
Click to expand...
Click to collapse
Reallly that sucks I would look around do you guys have a sprint store....?
What do the battery contacts look like on the battery ? Still a goldish color or do they have some black burns lines to them? Try to take a eraser on a pencil and wipe the contacts down and plug the battery back in talking about the battery don't use it on the prongs where the battery plugs in at .....
Worth a shot man lol I have done this in the past......
reaper24 said:
Reallly that sucks I would look around do you guys have a sprint store....?
What do the battery contacts look like on the battery ? Still a goldish color or do they have some black burns lines to them? Try to take a eraser on a pencil and wipe the contacts down and plug the battery back in talking about the battery don't use it on the prongs where the battery plugs in at .....
Worth a shot man lol I have done this in the past......
Click to expand...
Click to collapse
haha, it`s just that it`s so stressing having a $340 brick. I tried the eraser wiping trick but It didn`t work. Maybe I`ll have a friend manually charging the battery.
I´m going to sleep for now.
Thanks again
mariosaigon said:
haha, it`s just that it`s so stressing having a $340 brick. I tried the eraser wiping trick but It didn`t work. Maybe I`ll have a friend manually charging the battery.
I´m going to sleep for now.
Thanks again
Click to expand...
Click to collapse
I know the feeling lol That sucks,,,, Hope it works out for ya man..
Happened to me before. Try leaving it on charge for 8 hrs or so and remove the battery and replace every so often. BTW I got it on virus eternity as well. Also, I would get an extended battery to kill two birds with one stone if the previous method doesn't work.
Sent from my Quad core thingamabober with dat XDA Premium
Hello guys, I'm experimenting the same issue! It was working like a charm, then I left without simcard in airplane mode, but with wifi on.
When out from wifi coverage, it turned off (maybe because of the battery drain) and can't bring it back to life!
This is just incredible, I can't believe there is no way to wake up it.
I'm trying to charge with its charger, with PC connection and nothing happens: red light for a little while and everything off again after a couple of seconds ... I'm getting nervous :-(
I don't think the phone is bricked or a bad battery. When you plug the charger in, turn the light off in the room and see if the phone charging led is very dim. Sometimes when my battery is very low and I put it in the charger it does this. The other scenario is that the phone may be in download mode which I doubt. If it is then you can follow the last steps from the hboot 1.50 downgrade guide.
Sent from my PG86100 using xda premium
I just skimmed the posts so sorry if I missed it, but...
Have you tried "adb reboot recovery" just to see what happens?
Hi,
Recently installed Cyanogenmod on my new Galaxy S2, I couldn't get the stable version to install and after googling several threads on XDA recommended using a nightly build so I went ahead and downloaded the latest one at the time (April 19th release). All was fine, a couple of small bugs but nothing I couldn't work around. The only thing really bothering me was being unable to add a Facebook account.
Yesterday I decided to update to the latest version to see if that release had addressed the Facebook issue. It wouldn't allow me to connect to Wi-Fi, or add a Google account so I restored a backup from a couple of days before and thought nothing of it. Last night when I plugged my phone in it wouldn't charge, I thought I'd knocked the plug out of the wall and I was tired so I just went to sleep. I woke up this morning and my phone was dead and I can't do anything to get it to charge. I have checked the charger with another phone and it's working fine.
I have borrowed someone else's battery and I am able to turn on the phone, but nothing I have tried so far will get it to recognise a charger. I have tried:
resetting battery stats in CWM
resetting cache (both Dalvik and normal)
restoring to an earlier backup
reinstalling CM9 (the 19th April release that worked for me before)
finally restored my phone to stock using my initial backup, but still no joy
After all the above the problem continues. The really odd thing is that it will charge via USB from my PC, or at least it displays a charging animation - no change in battery level reading after 45 mins. It plays the USB plugged/unplugged sound on the PC and phone around every 30 seconds. So after all that my questions are:
1/ Is this a likely to be a Cyanogenmod issue or a hardware fault that coincidentally developed at the same time?
2/ Any suggestions to fix this?
Please let me know if you need any more info, thanks in advance for help.
Diberlee
[EDIT] I'm unable to get the phone to connect to the PC in download mode, I can get into Odin on the phone but it won't connect to the PC.
m8 post in cm9 thread,ull get good help.....if ur not on cm9 then flash again stock rom or c with diffrent usb cable.
After a full factory reset this issue sorted itself out. Guess the simplest solution is sometimes the best =)
Thanks for taking the time to read all the same.
diberlee said:
After a full factory reset this issue sorted itself out. Guess the simplest solution is sometimes the best =)
Thanks for taking the time to read all the same.
Click to expand...
Click to collapse
Yes and a point to bear in mind many user go down the long and winding road just to get to starting point of factory reset .
jje
Well, first of all, I should start by greeting the community, as this is my first post. So, yeah, hey everybody, been reading the forum for quite a while now, and it's been of a great help
Now, to the problem - this morning I noticed that my sgs2 had turned itself off. I didn't suspect the phone to be bricked or something as this happens from time to time when using custom roms. I tried turning it back on, it booted up, showed my kernels logo (DorimanX, not sure for the version though), so I put my phone in my pocket. After half an hour or so, I wanted to make a call, but I noticed that my sgs2 still hadn't booted up. So I tried restarting my phone using the power button, but instead of restarting it just turned off and I hadn't been able to turn it on since - it's bricked
I've heard of phones getting bricked while flashing a new rom or kernel, but never had I thought it could happen on simply booting up...
I did some research on bricked SGS2 and here's what I have done so far:
I've tried booting up in recovery/download modes, but that doesnt work.
I've tried soft/hard resetting my phone - still no luck.
I've also tried making an USB Jig, didn't work though. I'm not quite sure if my self-made jig works in the first place, as I did mess up the micro usb connector pretty bad while soldering resistors to pins. I'll try that one again with a different jack later and will keep you updated on weather it worked or not.
So, my question is, if my second try at making a USB Jig fails, is JTagging my only chance on reviving the phone? I guess that a MOBO change would probably help.
Another question is, if JTagging is my only chance, wouldn't it be easyer to just replace the bricked NAND chip? Then again, even though I have all kinds of soldering equipment accessible and also have the skills to do it, I have no idea where it's located on the mobo... Some info on that would also be much appreciated.
I havent flashed a new rom for quite a while now, last time I did it was when the latest version of Resurrection Remix was released.
My CPU wasn't overclocked - it was underclocked to 1GHz.
I was using DorimanX kernel.
Thanks in advance
jankanolv said:
Well, first of all, I should start by greeting the community, as this is my first post. So, yeah, hey everybody, been reading the forum for quite a while now, and it's been of a great help
Now, to the problem - this morning I noticed that my sgs2 had turned itself off. I didn't suspect the phone to be bricked or something as this happens from time to time when using custom roms. I tried turning it back on, it booted up, showed my kernels logo (DorimanX, not sure for the version though), so I put my phone in my pocket. After half an hour or so, I wanted to make a call, but I noticed that my sgs2 still hadn't booted up. So I tried restarting my phone using the power button, but instead of restarting it just turned off and I hadn't been able to turn it on since - it's bricked
I've heard of phones getting bricked while flashing a new rom or kernel, but never had I thought it could happen on simply booting up...
I did some research on bricked SGS2 and here's what I have done so far:
I've tried booting up in recovery/download modes, but that doesnt work.
I've tried soft/hard resetting my phone - still no luck.
I've also tried making an USB Jig, didn't work though. I'm not quite sure if my self-made jig works in the first place, as I did mess up the micro usb connector pretty bad while soldering resistors to pins. I'll try that one again with a different jack later and will keep you updated on weather it worked or not.
So, my question is, if my second try at making a USB Jig fails, is JTagging my only chance on reviving the phone? I guess that a MOBO change would probably help.
Another question is, if JTagging is my only chance, wouldn't it be easyer to just replace the bricked NAND chip? Then again, even though I have all kinds of soldering equipment accessible and also have the skills to do it, I have no idea where it's located on the mobo... Some info on that would also be much appreciated.
I havent flashed a new rom for quite a while now, last time I did it was when the latest version of Resurrection Remix was released.
My CPU wasn't overclocked - it was underclocked to 1GHz.
I was using DorimanX kernel.
Thanks in advance
Click to expand...
Click to collapse
What happens when you plug the charger. Does it charge?
pasanjay said:
What happens when you plug the charger. Does it charge?
Click to expand...
Click to collapse
I guess the battery is charging, as it heats up, but I don't see the charging animation. Also my PC won't see that a USB divice of any kind is connected.
jankanolv said:
I guess the battery is charging, as it heats up, but I don't see the charging animation. Also my PC won't see that a USB divice of any kind is connected.
Click to expand...
Click to collapse
order an usb jig and try. If it does not work send it to a repair center
Very similar happened to me a couple of days ago. Sgs2 crashed and wouldn't boot. I was also running dorimanx kernel, under clocked at 1ghz.
Originally I managed to get to download mode (not recovery mode). Kernels wouldn't flash via odin. I also tried using samsung kies to flash stock without success.
I tried the solution for nand bricked phones in this forum, however, this appears to have hard bricked the phone, since it failed to flash and now the phone does nothing (other than get hot when it is plugged in.) Nothing shows on screen. The PC does not recognise the device.
None of the threads I've read seem to offer a solution to this - any ideas? I guess I need to try a service centre, but thought I'd mention since I had same configuration as jankanolv, which of course may just be a coincidence...
birdr said:
Very similar happened to me a couple of days ago. Sgs2 crashed and wouldn't boot. I was also running dorimanx kernel, under clocked at 1ghz.
Originally I managed to get to download mode (not recovery mode). Kernels wouldn't flash via odin. I also tried using samsung kies to flash stock without success.
I tried the solution for nand bricked phones in this forum, however, this appears to have hard bricked the phone, since it failed to flash and now the phone does nothing (other than get hot when it is plugged in.) Nothing shows on screen. The PC does not recognise the device.
None of the threads I've read seem to offer a solution to this - any ideas? I guess I need to try a service centre, but thought I'd mention since I had same configuration as jankanolv, which of course may just be a coincidence...
Click to expand...
Click to collapse
Sounds familliar, lol. Anyways, did you use USB Jig to get to download mode? Or you just managed to boot it up on it's own?
I am really confused right now, because I'm pretty sure this can't be a hard brick as nothing has went wrong while flashing something on the device - it just bricked itself...
I've just get in the forum a few minutes ago only to find somoene with this symptoms, and i wasn't in here for too long and voilá...
Since yesterday my SGII, with no problems to this date, went in reboot mode for a few times.
I have no clue what is going on, but im sure something is.
i'll wait to see if theres anyone else complaining about it.
cheers
Hmm... Looks like a lot of people are getting this "brick" lately.
Maybe we all used some kind of app that bricked the phone on bootup?
Well, I tried to make another Jig, didn't work... This time though, I screwed my resitors up...
Another thing - is it really relevant to have exactly 301kOhm resistance between pins 4 and 5? As far as I know, it just kind of short circuits some pins on MOBO, which tells the phone to boot up in download mode. But I might be wrong...
Btw, sorry for the double post.
Same Problem
Hi,
I just face the same problem today,
now my S2 not working and just heat up.
this only happened after the original update done to my S2 - Android 4.1.2 - 2 days ago.
any help please
heat up....near the rear camera heat up?
Sent from the little guy
Mine gets hot near the camera. Nothing shows on screen.
In answer to jankanolv's questions:
- originally I could get to download mode via pressing home/power/volume down. (Not any more following failed flash). I've not tried a USB jig.
- my crash which started the situation occurred while I was listening to tune in radio pro app.
Well guys....near camera heating + no boot/dl/recovery = claim warranty saying that you factory reset the phone, 4.0.4 was laggy.
Sent from the little guy
was going to post a thread asking for help for what appears to be a similar problem
mine got stuck in a bootloop after pulling the battery, tried flashing new software in recovery then tried through odin but kept failing, now its bricked.
does nothing, wont go into either download or recovery mode so looks like its off to the service centre with it.
ahmadmetwally said:
Hi,
I just face the same problem today,
now my S2 not working and just heat up.
this only happened after the original update done to my S2 - Android 4.1.2 - 2 days ago.
any help please
Click to expand...
Click to collapse
Yessss! good to know I'm not the only one facing this issue.
I posted a thread about this yesterday but it is all the way down in page 3 already:
http://forum.xda-developers.com/showthread.php?t=2192996
I tapped on the "sync" toggle on the notification shade and my phone just turned itself off.
Recovery and download mode were accessible though.
Thanks for the help.
I went to Samsung to get them to fix based on the factory reset while on stock 4.04 premise, but they were having none of it, and wanted to charge me to investigate the problem. Once out of warranty period, it seems it doesn't matter if their software can brick your phone!
I found a local phone fixing service in Hong Kong which investigated, diagnosed as a motherboard failure (which I suspect my problem genuinely was given how firmware flashes were failing), and replaced + fitted for 700hkd, (approx 90usd). The guy did it in front of me within 10 mins. "Andy Telecom" in Mongkok, on +852 9237 9237 in case someone else has the same issue locally.
Well, outta warranty...that's another story. You only get 1-2 years to brick your device
Glad you had it fixed for 90 bucks, some service centers charge around 150.
Sent from the little guy
Well, I finally managed to make a working USB Jig, tried it on Galaxy Ace, worked like a charm.
What confuses me right now, is that my sgs2 has drained all the battery, even though it was switched off for about 2 days. I'm charging the device right now, and I will keep you updated on weather my jig works..
Sorry for double-posting again on an old thread, just wanted to let you guys know - I took the phone to warranty service and they changed the mobo. I didn't have to pay anything and everything is working normally. Of course all data on sd card is now lost for good, lol.
So if you hard brick your device so badly it even won't respond to usb jig and you still have your warranty active, don't bother trying to revive your phone - just take it to warranty service
I guess they couldn't see the odin download count so they cant void my warranty, he he he ]
Hello everyone...
I'm a new member, but certainly not new to this great forum! Unfortunately, though, my first post is to report - and ask for help with - a little disaster!
Okay, so, without further ado, here's how it went down.
I had flashed both phones with ICS earlier, but wanted to get them back to the factory ROM. Having bought yet another U, I found out that the original GB ROM for phones sold in Saudi Arabia is st25i_6.0.b.3.188, as opposed to .184, which I had also flashed the phones with after I had some issues with the aforementioned ICS.
So, last night I located and downloaded the .188 kernel and flashed it using the flashtool. As it usually happens, the flashtool window seemed to go all black, as though the application had hung on me, which wasn't the first time this had happened. I just gave it some time as I normally do and then disconnect the phone, and that never caused any problems. To my surprise, though, when I first started the phone and checked the "about phone" tab in settings, it turned out that the installed version was .184!
So, again, I attempted to reflash the thing, this time being sure to remove all other kernels from the firmware folder within the flashtool. I then just let it do its thing and went off to bed (bad idea!).
In the morning, though, the phone simply wouldn't start. If I hook it to either the computer or the charger, the LED near the front camera will light up red, indicating that the battery is being charged, but nothing else. I can't even boot into recovery mode!
So, now what can I possibly do (besides buying a new one, that is)?
sjanzeir said:
Hello everyone...
I'm a new member, but certainly not new to this great forum! Unfortunately, though, my first post is to report - and ask for help with - a little disaster!
Okay, so, without further ado, here's how it went down.
I had flashed both phones with ICS earlier, but wanted to get them back to the factory ROM. Having bought yet another U, I found out that the original GB ROM for phones sold in Saudi Arabia is st25i_6.0.b.3.188, as opposed to .184, which I had also flashed the phones with after I had some issues with the aforementioned ICS.
So, last night I located and downloaded the .188 kernel and flashed it using the flashtool. As it usually happens, the flashtool window seemed to go all black, as though the application had hung on me, which wasn't the first time this had happened. I just gave it some time as I normally do and then disconnect the phone, and that never caused any problems. To my surprise, though, when I first started the phone and checked the "about phone" tab in settings, it turned out that the installed version was .184!
So, again, I attempted to reflash the thing, this time being sure to remove all other kernels from the firmware folder within the flashtool. I then just let it do its thing and went off to bed (bad idea!).
In the morning, though, the phone simply wouldn't start. If I hook it to either the computer or the charger, the LED near the front camera will light up red, indicating that the battery is being charged, but nothing else. I can't even boot into recovery mode!
So, now what can I possibly do (besides buying a new one, that is)?
Click to expand...
Click to collapse
This has all signs of a low battery problem ... plug in your phone to the charger for half an hour and wait ..... pull it out and it should boot .. Post your findings in any case :good:
Bhargav4591 said:
This has all signs of a low battery problem ... plug in your phone to the charger for half an hour and wait ..... pull it out and it should boot .. Post your findings in any case :good:
Click to expand...
Click to collapse
:good: Thanks dude! It fired up on its own as soon as I plugged it into the charger! I just charged up the batter to full 100%, and I'm about to try to reflash it for the third time. What I don't get, though, is why the battery got drained when the phone had been plugged into the laptop all night! There was about 82% of charge left in the battery when I first plugged it into the machine.
I'll report back again after reflashing. Thanks again.
sjanzeir said:
:good: Thanks dude! It fired up on its own as soon as I plugged it into the charger! I just charged up the batter to full 100%, and I'm about to try to reflash it for the third time. What I don't get, though, is why the battery got drained when the phone had been plugged into the laptop all night! There was about 82% of charge left in the battery when I first plugged it into the machine.
I'll report back again after reflashing. Thanks again.
Click to expand...
Click to collapse
Glad it worked out . :laugh:
Charging via usb is very slow and if you've left something like wifi on all night then there's no doubt that it you're battery is gonna die
Any way , why GB ? The .89 ICS is supposedly awesome . Haven't tried it myself but, I've heard rave reviews from all the people who have.
Bhargav4591 said:
Glad it worked out . :laugh:
Charging via usb is very slow and if you've left something like wifi on all night then there's no doubt that it you're battery is gonna die
Any way , why GB ? The .89 ICS is supposedly awesome . Haven't tried it myself but, I've heard rave reviews from all the people who have.
Click to expand...
Click to collapse
Yeah, that's probably it. I had this (obviously misguided) idea to try to get the phone back to the exact way it was out of the box, and then wait (and wait, and wait...) for Saudi Arabia's turn for the ICS update. Now I know better, thanks to you and all the other helpful folks over here!
sjanzeir said:
Yeah, that's probably it. I had this (obviously misguided) idea to try to get the phone back to the exact way it was out of the box, and then wait (and wait, and wait...) for Saudi Arabia's turn for the ICS update. Now I know better, thanks to you and all the other helpful folks over here!
Click to expand...
Click to collapse
He he ... no worries mate . Glad to have helped .. BTW ... JB for Xperia U out =D [If you haven't seen the dev section that is] ... Bugs present but the Devs are working tirelessly ... expect the fastest Rom for U yet =D
Bhargav4591 said:
JB for Xperia U out =D [If you haven't seen the dev section that is] ... Bugs present but the Devs are working tirelessly ... expect the fastest Rom for U yet =D
Click to expand...
Click to collapse
Ohhhhh... me wanty! I'll check that out next and see how it goes. Thanks again, buddy!
Hi there,
For a few days now I have been experiencing random reboots of my phone and I've always just thought that it was the ROM I was on (Omega) as I did not update it for a time (Not too long). Now the phone has decided to keep rebooting and I have installed a recovery of a stock ROM. It also won't turn on sometimes and when it does it just shows a picture of a battery when plugged into a charger. Sometimes it shows charge and sometimes it says there is no charge at all. It also turns itself off sometimes when plugged into a charger. I am not sure whether this is SDS? Any ideas to save my S3?
Cheers,
Jon
Jon.W said:
Hi there,
For a few days now I have been experiencing random reboots of my phone and I've always just thought that it was the ROM I was on (Omega) as I did not update it for a time (Not too long). Now the phone has decided to keep rebooting and I have installed a recovery of a stock ROM. It also won't turn on sometimes and when it does it just shows a picture of a battery when plugged into a charger. Sometimes it shows charge and sometimes it says there is no charge at all. It also turns itself off sometimes when plugged into a charger. I am not sure whether this is SDS? Any ideas to save my S3?
Cheers,
Jon
Click to expand...
Click to collapse
Try changing the battery. Confirmed to be working by some users.
Questions go in the q&a forum. Report your own post and ask a moderator to move it for you.
Flash a full stock firmware with odin and factory reset, if still the same then it's hardware.
Sent from my GT-I9300 using Tapatalk
Have you even thought about it possibly being your battery? I've had problems with my battery in the past and just replacing it has fixed most issues.
boomboomer said:
Questions go in the q&a forum. Report your own post and ask a moderator to move it for you.
Flash a full stock firmware with odin and factory reset, if still the same then it's hardware.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
doverjosh8 said:
Have you even thought about it possibly being your battery? I've had problems with my battery in the past and just replacing it has fixed most issues.
Click to expand...
Click to collapse
Flashed a stock ROM, unrooted as well. Problems still occurred and now trying a factory reset. If that doesn't work then I will try a new battery. If all else fails it may have to go back to Samsung as I'm still under warranty.
You should have really tried replacing your battery before anything. It seems like that's the problem