Related
Hi,
About 1,5 months ago I received my first Android phone, a Galaxy Nexus.
I have unlocked the bootloader, rooted it en eventually installed Clockwork Mod Recovery following guides on this excellent forum! Everything went perfectly and it ran very smoothly in that state for about half a month up until yesterday.
I didn't have any custom roms installed, so I received the notification for the Android 4.0.2 update, it failed because of Clockwork Mod which I later found out. So I set about to manually install it, I downloaded the image from the google site and placed it in my home directory on my Phone, when I then wanted to restart to start in recovery mode it didn't do anything.
I tried getting the battery out and in, sim card out and in, recharging it,...
It does nothing, not even a small vibration signaling the phone is trying to start.
Anyone has any ideas to fix it, or might it be possible to send it back to the shop ( even though it is rooted etc. ?)
Thanks in advance,
Exatto
You need to get the stock images and flash using Odin or the ADB/Fastboot method. After which the phone will return to stock. Then you can root and do what you like. Lots of guieds on here on how to do it. Good luck.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
By the way if you send back a rooted phone they will tell you to take a jump. Rooting voids the warranty.
No response at all? A real brick?
Sent from my Galaxy Nexus using xda premium
Can you get into download mode? If you can you can use any of the methods above to sort it.
I don't think there is a real brick. There are restore images. Extremely hard to brick a nexus...borderline impossible.
Yeah I have never heard of a "real" bricked Nexus.
jd1001 said:
Can you get into download mode? If you can you can use any of the methods above to sort it.
Click to expand...
Click to collapse
No, that's the point. I can't get in any modes. It does't react at all. I think it might be a hardware fault, a friend suggested it might be due to a short circuit battery.
I just followed this guide (http://forum.xda-developers.com/showthread.php?t=1419170) to update, using method 1, having clockwork mod installed. And when I shut it down to restart in recovery mode it suddenly stopped reacting. I have had this before, but then taking the battery in and out fixed everything. Now it doesn't anymore.
Cool, well if removing the battery for a few minutes doesnt sort it then you should be able to return it because the carrier won't be able to tell if it is rooted if they can't turn it on.
When you charge it do you get the charging battery icon when you press the power button?
stkiswr said:
I don't think there is a real brick. There are restore images. Extremely hard to brick a nexus...borderline impossible.
Click to expand...
Click to collapse
But I can't do anything with a restore image when I can't even get it started, let alone be recognized by my computer?
P.S.: Sorry for the late reply, but apparently I still have to wait 5 minutes in between posts.
Can you see the charging battery icon when the phone is off and plugged into the wall?
jd1001 said:
Cool, well if removing the battery for a few minutes doesnt sort it then you should be able to return it because the carrier won't be able to tell if it is rooted if they can't turn it on.
When you charge it do you get the charging battery icon when you press the power button?
Click to expand...
Click to collapse
No, not a charging sign. I hope I can return it, but what if the battery is faulty and they just pop a new one in and then see that it is rooted?
Thanks for the help.
Could well be a dead battery dude, if you have a mate with a Nexus you could try yourself first. I know what you mean about the guy in the shop seeing the unlocked bootloader if he tried a different battery but you may be lucky in that he might not know what it is or you could just grab the phone and leg it ha ha
I hope it gets sorted and be sure to post here what happens. Take it easy.
jd1001 said:
Could well be a dead battery dude, if you have a mate with a Nexus you could try yourself first. I know what you mean about the guy in the shop seeing the unlocked bootloader if he tried a different battery but you may be lucky in that he might not know what it is or you could just grab the phone and leg it ha ha
I hope it gets sorted and be sure to post here what happens. Take it easy.
Click to expand...
Click to collapse
Thanks, hope it get's sorted out. Have to send the phone back, because it was imported, so no chance of legging it
Will post the outcome.
As promised the followup:
Luckily they didn't notice my GN was rooted etc. as today I received a brand new one after I sent the broken one in to an official Samsung repair center
I did test some things before I sent it in though, a friend just bought a new one and we tested if my battery worked in his phone (it didn't) and we tested his working battery in my phone (it didn't work either), so something was definitely very screwed up.
Haven't got any idea of what went wrong eventually as the repair service didn't offer any details, although I am off course glad I got a brand new one.
Think I just borked by AT&T Galaxy S3, and yes it is completely my fault. This is probably a dead end, buy I figured I'd ask as a last resort.
I've got a lot of experience rooting and flashing ROMS and flashing custom recoveries and was rushing a proceedure when the problem occurred. I was trying to flash the CWM touch recovery using the instructions here: http://forum.xda-developers.com/showthread.php?t=1739426
I tried to do all this through my phone using Terminal Emulator and typed in the portion "mmcblk0p18" one letter off from what I should have (I think I typed in "mmcblk0p08" ... sick sinking feeling my stomach right now). The code went through as I started to power down the phone as I was looking at the code I wrote. Noticed the mispelled line of code right as the screen was powering off. Now my phone is completely unresponsive, after I rebooted. The phone does not power on, cannot boot into recovery mode, and worst of all seemingly will not boot into download mode. I've had boot loops before and am familiar with how to traditionally boot into Download mode via POWER + Vol Down + Home Button and used Odin to flash a fix.
Are there any other options, short of taking it to a repair shop, that I can try? I'm guessing it's completely bricked, but I just wanted to see if there were any options I was missing that are worth trying.
About to start calling repair shops to see if they can take a look at it as well.
Warranty replacement. Just say you don't know why it won't turn on. I did this after dropping my rooted phone and they asked no questions.
On the phone now, I'll let you know if they're able to assist with troubleshooting or otherwise.
I did the same thing.... I had insurance through att reported the phone lost... I repeat lost not stolen.. Got a replacement in 2 days brand new white and used that to pull the stock rom and flash it to my old phone. The then turned around and sold the replacement phone
Sent from my SGH-I747M using xda premium
That doesn't make sense why the phone won't even turn on, were you trying to flash on a low battery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Mphill46 said:
That doesn't make sense why the phone won't even turn on, were you trying to flash on a low battery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I agree that it doesn't make sense. It's behaving almost as if the battery is just flat out dead. I have a spare battery, but when I tried that one it made no difference. I plugged the phone into a couple of different chargers while the AT&T rep was helping me troubleshoot and the charging light wouldn't turn on. The phone was not responding to anything at all, no matter what we tried.
They declared it hardware failure and are sending a replacement, as part of the original warranty. It did not have any physical damage, scratches, no water damage, etc.
Let this be a lesson to others: Be very very VERY careful with ADB and read your commands carefully. Those warnings about bricking your phone are real and shouldn't be taken lightly. I've rooted 6 devices and flashed what I'd estimate as over 60 ROMs over all my Android devices. I let my guard down and rushed things, and really my carelessness is all to blame at this point.
I need help my galaxy nexus is not turning on. At first it would start charging when connected to a charger and i was able to turn on my phone(although it would not go past the google screen) but as soon as i disconnected my charger the phone would turn off(even though battery was nearly full).I performed all the wipes but it was of no help.My phone then stopped even charging.Now I cant even get it into recovery mode.
I would apreciate any and all help you can offer
Have you already tried swapping the battery ? Because I once was in a similar situation and changing the battery worked for me.
Zanera said:
Have you already tried swapping the battery ? Because I once was in a similar situation and changing the battery worked for me.
Click to expand...
Click to collapse
the battery is fine i have tried another battery but it didnt work
Not so long ago i tried to be the boss and took another guy's i9000 to install CM10 for him, i nailed it, it installed and it was working perfectly fine, then after several reboots the phone got stuck in a bootloop, then it got stuck in recovery, then it got stuck on the samsung logo, and then it just died.(stopped charging) like having literally a brick in your hand, no response.
If you've done alot of mods to the phone I'm guessing something inside died, get your phone to warranty and say you cant turn it on, they'll just change the motherboard and give you the phone back, if you had any custom roms they will never know.
my phone has no warranty that i could claim so my only option is to somehow fix my gnex
CoDe LaZaRuS said:
my phone has no warranty that i could claim so my only option is to somehow fix my gnex
Click to expand...
Click to collapse
Well as i said, you have probably damaged physically some component on the motherboard, it needs to be changed so you can't fix it, find a Service that fixes android devices and tell em it doesn't boot nor makes a reaction at all, they'll prolly say they will change the motherboard if they have one and thats it.
*Edit*
I remember there was a thing called "jtag" that was able to debrick devices broken in such ways. But Rarely do services have them.
Try fastboot, download mode or omap
Sent from my Galaxy Nexus using XDA Premium HD app
So my phone running CM 10.1, turned off randomly. So I tried to reboot but kept getting stuck on the Samsung boot logo. I rebooted to CWM recovery mode, wiped cache and dalvik and rebooted which I thought would fix the problem somehow which it did. However, when it said "Android upgrading, optimizing apps", my phone lost battery (thought the phone charger was plugged in). When I plugged it in the outlet properly this time, I got through the battery charging logo. But when I tried turning it on afterwards, nothing. The phone doesn't respond when I tried to turn it on. Took the battery off, placed it back and when I plug it into the outlet, there is no more battery charging logo and I can no longer reboot. How can I fix this? Somehow, the phone might be trying to continue to turn on but is not responding when I try to actually turn it on. When I plug the charger, take off the battery, unplug and replug charger, the battery charging led lights up for 5 minutes (which is weird cause I disabled the indicator led when charging in the system settings). I allowed it to be plugged in to the charger overnight and when I checked this morning, nothing. No symptoms that it was charging; no heat on the phone. Is not being able to charge a symptom of a bricked phone. I have yet to try using another battery.
If you can't power on or get to DL mode or anything and none of the buttons respond it could be a hard brick
Check here:
http://forum.xda-developers.com/showthread.php?t=2369125
Sent from my SPH-L710 using xda app-developers app
I checked at a Sprint store and the device they have couldn't make a reading off my battery meaning it was most likely dead. I'm gonna try with a new battery and hopefully my phone isn't actually bricked.
Best of luck sir
Sent from my SPH-L710 using xda app-developers app
Ah, just my luck. A Sprint representative placed another battery on it (I didn't see it though) and told me that the phone still won't turn on and told me he can open and check the phone if I pay. So, I think it is hard bricked. :crying: How did I brick it? Ugh..I'm just dismayed on the information and data I lost. What are my options? I heard Mobiletechvideos.com does a jtag brick repair with an option for internal sd card recovery?
bonsly16 said:
Ah, just my luck. A Sprint representative placed another battery on it (I didn't see it though) and told me that the phone still won't turn on and told me he can open and check the phone if I pay. So, I think it is hard bricked. :crying: How did I brick it? Ugh..I'm just dismayed on the information and data I lost. What are my options? I heard Mobiletechvideos.com does a jtag brick repair with an option for internal sd card recovery?
Click to expand...
Click to collapse
I had to get a JTAG when I flashed a wrong kernel. Although when I got it back I had lost nothing still had custom ROM and recovery and all my data and apps were there. If its hard bricked its because something happened to the bootloader
Sent from my SPH-L710 using xda app-developers app
IDontKnowMang said:
I had to get a JTAG when I flashed a wrong kernel. Although when I got it back I had lost nothing still had custom ROM and recovery and all my data and apps were there. If its hard bricked its because something happened to the bootloader
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
How can I know if I need a JTAG or my phone need an eMMC Chip Repair Replacement. What if my phone experienced a sudden death. If it's the latter, it's expensive as the website lists it for $150, almost the price of a new two-year contract phone.
Oh well, I'll send it in anyways for a jtag. Hopefully they can fix it.
bonsly16 said:
How can I know if I need a JTAG or my phone need an eMMC Chip Repair Replacement. What if my phone experienced a sudden death. If it's the latter, it's expensive as the website lists it for $150, almost the price of a new two-year contract phone.
Oh well, I'll send it in anyways for a jtag. Hopefully they can fix it.
Click to expand...
Click to collapse
Its kind if hard to say if this was a brick or not. Usually sudden death is out of the blue, as far as I know the only way to achieve a hard brick is flashing a bad or international zip file
What's 150$ though? The emmc or the jtag
Sent from my SPH-L710 using xda app-developers app
I just experienced a similar problem as OP, and I didn't even flash a new ROM or international ROM. Since January, I've been using the ICS version of FreeGS3, stock kernel.
http://forum.xda-developers.com/showthread.php?t=1748818
I haven't flashed any new ROM's since January 2013 and have not experienced any problems until now.
This morning, however, when I woke up, I discovered that my Sprint S3 was stuck on the "Samsung Galaxy S III" logo. I pulled the battery and powered up, and it got stuck on the same logo again. I repeated this process several times and the same thing happened. After looking at some XDA threads, I went into recovery and decided to wipe cache and dalvik to see if that fixed anything. Again, the phone booted up and got stuck on the "Samsung Galaxy S III" logo again.
However, when I tried to boot into recovery again, I wasn't able to do so. I tried several times without any luck. I decided to see if I could put the phone into download mode. I did, and it was successful. I didn't do anything just yet because I needed to research more fixes before seeing what needed to be done. I put the phone into download mode several times without doing anything, but then later, the phone itself wouldn't power on.
No matter what combination of buttons I pressed, the phone simply wouldn't power on. I even tried other batteries which I knew were fully charged. When I put the phone on the charger or plug it into my PC, no charging lights light up. However, when I pull the battery an plug the phone into my PC, the charging light lights up and it the PC seems to try to install drivers. However, despite the charging light lighting up with the battery pulled, but phone plugged into the PC, I still can't get the phone to power on at all and therefore can't get into recovery or download mode.
It's similar to the problem the person in this video is having where he uses a jig to get back into download mode.
http://youtu.be/FdrdWqaXUBE
I have a jig on the way, so hopefully that helps fix my problems, but I don't really understand how the phone got bricked in the first place; First it was soft bricked when it got stuck on the "Samsung Galaxy S III" logo, but I was still able to get into recovery and download mode. Then, it was hard bricked when it wouldn't even power on to get into recovery or download mode. Did it get hard bricked because I went into download mode too many times? What might have caused it to be soft bricked. The thread for my ROM is now closed, so I don't know where else to ask these questions. I'll update you as I try to fix this problem. Any other suggestions are welcome.
Your device is not bricked your device doesn't even have a software failure. What you are describing is SDS sudden death syndrome.
Your power button has failed. It's defective and the manufacturer knows it. It fails at the motherboard not the physical button itself. Since you where able to get into download mode I suggest you return the device to stock unrooted, do a triangle away function and take it to Sprint. They usually repair of exchange it for you.
Have a great day!
edfunkycold said:
Your device is not bricked your device doesn't even have a software failure. What you are describing is SDS sudden death syndrome.
Your power button has failed. It's defective and the manufacturer knows it. It fails at the motherboard not the physical button itself. Since you where able to get into download mode I suggest you return the device to stock unrooted, do a triangle away function and take it to Sprint. They usually repair of exchange it for you.
Have a great day!
Click to expand...
Click to collapse
Hmm...I suggest you are talking about the other poster since I am not able to power it on at all (Recovery nor Download mode). I don't have insurance nor have warranty, I don't think Sprint would be able to fix it without me paying an incredibly huge amount. I was hoping that my data would be recovered but now that you mention the possibility of sudden death syndrome, there's no way I can recover the data if it is. A sudden death syndrome would require a replacement of the eMMC which is rather costly.
@bonsly16 My apologies yes my reply was to Lawyerman... But you do have an alternative option, http://forum.xda-developers.com/showthread.php?p=43724690 many have had success and in many cases everything was there for them.
Have a great day!
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
kiwi32 said:
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
Click to expand...
Click to collapse
is it possible that the LCD went bad?? when you plug it into charge does it react (lcd or vibrate?) I would also suggest trying out a known battery. could be that if it is the original battery that it is so dead that I got "spikey" and finaly just died.
hope it is that simple
kiwi32 said:
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
Click to expand...
Click to collapse
If she wasn't trying to flash anything, doesn't sound like a brick which, to my understanding, results from software failures. The procedure posted in the thread applies when you are trying to recover from a brick caused by firmware failure from attempting to flash the wrong bootloader so I'd be doubtful if it would help you here. This could be a specific hardware failure which is not unheard of with equipment like this. Also sounds like it gave warning of the gradual failure. When you plug it into a charging outlet, does it show any sign of life - a light or vibration? If it's an LCD failure, it probably wouldn't affect charging or recognition by your PC. If there is no sign of life at all even with different batteries, you may want to try a professional repair service as I presume exercising the warranty is not an option in view of the firmware history.
Hi,
Thanks for the replies.
I did try different batteries. The phone does not vibrate or react at all even when plugged in which does not suggest an LCD failure.
I guess you are right,it must be a hardware failure. I'm quite suprised,I thought these phones were well buit and resistant.Oh well.
She's getting a Nexus 5 now.
Thanks for the help !