Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
wrong forum mate...if you go to this link, they might be able to help you there
http://forum.xda-developers.com/forumdisplay.php?f=1431
hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
onlinemoon said:
hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
Click to expand...
Click to collapse
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
i have same problem. can you fix it now?
adesos said:
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
i have same problem. can you fix it now?
Click to expand...
Click to collapse
Well done for not reading the thread and realising you were asking the question in the *wrong forum*!
Hey man I have the same problem and my phone is also from UAE. Did you figure it out??
Sorry posting here.
WTF are these guys for real? This thread should have been deleted the day it was started!!
This is posted in wrong section.
**Reported**
Thread Closed​
This forum is for the galaxy note, please post in the correct forum​
So the issue i am having is the phone is in constant boot loop, while it is pixalated only on the upper have of the screen. i have tried the 3 button combo; the vol + and power; vol - and power. What happened was, i was in recovery mode looking to update the kernel for the serendiptiy 6.4 rom i had. After it installed from my sd, I rebooted the phone and hasn't booted up right since.
Here are some specs and extra info:
Carrier: AT&T
Phone: Samsung Galaxy S sgh-i897
Rom: Serendipity 6.4
Experience: Semi-advanced
any good help is greatly appreciated. Please help. And yes i have looked everywhere on the forums for a similar case and have found nothing.
You didn't look hard enough.
http://forum.xda-developers.com/showthread.php?t=1827927
thanks but thats not the issue i am having, here is a video i took showing what i mean. I have a youtube video but i cant upload it since i am new to the forum.
Can you get into download mode?
No, it just loads a rotating spindle for as long as i hold the combos together. then when i let go it goes to the at&t screen, except only the lower half of the screen. if that makes any sense.
/watch?v=1QprRJ1D0SU
Ok I understand now. I think it's possible get download mode back using a windows program, I don't know how myself though. If I find an old thread that explains it I'll post a link. Hopefully someone else can jump in and help.
---------- Post added at 11:39 PM ---------- Previous post was at 11:32 PM ----------
I found this, apparently a usb jig can fix your phone.
http://forum.xda-developers.com/showthread.php?t=1804980
http://www.youtube.com/watch?v=Rdn5GoRjhn0&feature=youtube_gdata_player
Ok thats what i am trying to look for also. Oh and when i plug it in to my computer, the computer does not recognize the phone. Is that as simple as downloading my phone drivers?
Yes download the drivers.
try this
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Download_Mode
and
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Soft-Bricked
Wow that is almost the exact same thing i did. Well i will give it a good ol american try, and follow up when that part finally arrives.
yup the jig did the trick, thank you.
ok, so my tab decided to be a pain in the arse today. when i try to power it on, run it in download mode or in recovery mode the samsung galaxy tab 8.9 screen shows up then the screen either shuts off or flickers and then shuts off before it can load up.
what options do i have to overcome this? i am rooted running JB.
tia.
skim234 said:
ok, so my tab decided to be a pain in the arse today. when i try to power it on, run it in download mode or in recovery mode the samsung galaxy tab 8.9 screen shows up then the screen either shuts off or flickers and then shuts off before it can load up.
what options do i have to overcome this? i am rooted running JB.
tia.
Click to expand...
Click to collapse
Yeah, same thing happened to me today I read that it is something to do with the bootloader, which can cause the tab to be bricked if not done right, so I'm going to try the ASOP JB instead see if that does the same thing.
---------- Post added at 09:17 AM ---------- Previous post was at 08:47 AM ----------
MikeMcGrathXmen said:
Yeah, same thing happened to me today I read that it is something to do with the bootloader, which can cause the tab to be bricked if not done right, so I'm going to try the ASOP JB instead see if that does the same thing.
Click to expand...
Click to collapse
Nope Dosen't work still the same when I install the AOSP (spelt it right this time), any pointers here would be great, I do want to try and fix this, I've been waiting for ages for the official ICS, but couldn't wait any longer so spent some time looking on how to do this and was amazed at the speed of JB, but the screen keeps flickering after standby. Anyone know step by step guide to fix this? Any help would be greatly appreciated. thanks Mike
Recently I got caught in a downpour and my phone was in my pocket. My work email requires security restrictions that wipe the phone after 6 failed unlock attempts. The water caused the phone to think it was trying to be unlocked which then initiated the wipe. During that, the phone then shutoff completely mid wipe. Now, the phone turns on but more often then not there is no display. I can tell it's booting because it will disconnect and reconnect to odin, and I can flash stock firmware but there is no display. What I don't understand is, randomly the screen comes back. But as soon as the device is turned off, it won't come back.
The phone is disassembled and I have access to the battery if needed.
Primary question: Is there anything firmware related that can cause the display not to function at all or is it more likely a hardware issue?
Any tips or suggestions?
I also hv almost same problem with galaxy s6. But in mine case it just don't display anything for some hour. After that it works like charm. During weakend when i'm home there is no problem but elese when i'm at work problem happens.
---------- Post added at 10:19 AM ---------- Previous post was at 10:18 AM ----------
Your case looks to me water damage.. some components on Morherboard are fride or something like that.
Hello,
I have a big problem : after a bad flash of firmware or ROM, my Moto X don't want to turn on anymore.
When I plug in to the wall stock charger, I saw a green light but it disappears quickly.
When i plug into the computer, it appears like an HID device 5 secondes, then disappears, then appears, etc.
After reading a lot of topic here, I saw that a factory cable could be the solution.
I bought one online and I just received it.
The differences I saw with this cable : on the wall charger, now, the green light is still present, it doesn't disappear like the other cable.
The other difference is that it appears in the device manager of my computer like an "Unknown USB Device (Device Descriptor Request Failed)".
I tried the fastboot devices, and it doesn't recognize it.
I tried to install the qhusb load, but Windows won't let me saying that the previous driver is already the best.
And no matter what button I pushed, in no matter the order, the screen won't never turn on.
If someone could help me, I would be very very very very happy
(I only hope it's not dead )
Thank you !!
I have a Moto X XT1058 that is hard bricked, it would not turn on, not even the green light.
I followed this tutorial, and managed to get the device into the bootloader, but can't still manage to flash a ROM.
---------- Post added at 12:31 AM ---------- Previous post was at 12:30 AM ----------
galabean said:
I tried to install the qhusb load, but Windows won't let me saying that the previous driver is already the best.
Click to expand...
Click to collapse
I had to look for a different installer than the one provided in the tutorial, it was a .exe installer, not through device manager.
I think I have the installer in my downloads, if you want the one that worked for me, send me a private message or give me your email to send you a google drive link with the file.
I don't know if I can share it through here.