Related
I took battery out to change SIM card and now it won't start.
I get text "Touch Diamond" on the black screen and when it comes to Radio version etc. (red text i corner) it restarts!?!
I tried hard reset but it doesn't help.
Plz help I need my baby back!
Tnx
Try this
I found solution for this problem. If your diamond won't boot go to bootloader mode and upgrade your radio hxxp://modmydiamond.info/index.php?option=com_content&task=view&id=15&Itemid=26 and after that your dimond worked fine without loosing data.
or
forum.xda-developers.com/showthread.php?p=5514067#post5514067
I have the same problem. After a lockup when trying to get the internet sharing to work the phone just keeps rebooting.
I tried to flash a new radi version (from bootloader mode). Everything went OK, but the phone still won't start.
Whats next step? Hard reset?
i have the same problem - i believe it´s battery related
Try leaving your device off for a bit and pull the battery. Then re-insert the battery and plug your device into the ac adapter/charger and charge it for at least 30min. Then turn it back on and see if it continues. Like the previous poster said, you could have a bad battery. Otherwise, flash the shipped rom and then see if it still does it. Then flash back to your custom rom.
Hi I tried using the search function but I think it's disabled at the moment. The screen on my friends droid always stops responding. And since it's locked theres no way to use the phone. Restarting the phone / a battery pull doesn't solve it. It just stays non responsive. The screen is still working sort of, I can see the battery charge moving and when texts are received they display at the top. But when I call her phone from mine the screen stays at the lock screen. Any help would be greatly appreciated. My friend is stressing over this so I'm trying to help her out.
Hi, I am having the same problem. I tried uninstalling some applications from a custom recovery, and even doing a factory reset didn't solve anything. I also tried booting without the SD card, without any luck. Actually I'm thinking about taking it to Motorola to have it repaired or replaced, cause I have no idea left about anything possible to try.
Hey guys,
I updated my galaxy s to a custom ROM yesterday.. Battery started draining and phone was heated all the time it was turned on.
As it was discharging very quick, I plugged in the charger, phone was heated up and I suddenly got a whole green screen on phone.
I removed out battery instantly, I let it cool.. again inserted the battery and started. I got the same green display. I tried to put phone in recovery or download mode, I am getting same green display everytime I start phone.
Phone is working flawlessly as I can get phones and message tones, even touch is working. I can hear lock and unlock sound when I slide my finger over phone screen. Only thing is display is not working.
Now, What should I replace? is Digitizer working? Will samsung cover this under warranty (I've installed custom ROM on my phone) if not what will be total cost of repairs?
I dont know what might be wrong but maybe you can tell us what custom rom caused this issue so we can avoid it ?
not sure on a solution, but if you flash a standard ROM using Odin, then you can return it to Samsung and tell them that after updating to Froyo using Kies you have this problem.
as the firmware on the phone will be the official firmware then i cant see any reason why your warranty wouldn't cover it [thats what i did anyway]. just make sure you flash the phone,modem and csc files to totally restore to stock.
BTW this may also sort you problem.
Matt
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
Hello, I've had my G Watch R for not quite a full week so far and I've really enjoyed it. Two days ago, I believe that I let the battery die so I placed it on the charger before going to bed. When I woke in the morning i grabbed the watch off the charger without looking at it. Just before i stepped out the door i noticed that it wasn't waking up and It wouldn't even power on. I ran back and slapped it on the charger thinking that it would be more than charged by lunch time. Thats when i noticed the apparent boot issue you can see in the video attached. It hasn't been dropped at all and I have the basic apps installed; facer, watchmaker etc. At this point, Is there anything that I can try short of sending it back?
I've left it on the charger for 24+ hours, it gets slightly warm and stays in the boot loop. As soon as its taken off the charger it has no visible charge and refuses to respond to anything. I purchased it through amazon, so I'm thinking it shouldn't be an issue for me to return it...
http://youtu.be/GgF3iXAhTTI/
Sorry i tried to embed the video but the youtube link for xda seems to be breaking the url somehow
So I have already initiated the return process with amazon and it should be pretty painless. I have almost 3 weeks to send it back, so if anyone has any tips/tricks or ideas I'm more than open to try them....The watch is 100% stock as far as firmware or root is concerned.
Any luck with this? I just got back an RMA for a broken touch sensor, I don't want to have to RMA it again.
try to see if you can get in to the bootloader, and restart the watch from there
i have notice when i charge the watch from empty (so thewatch boots up while charging) it causes problems, usually boot loops as well
I just watched the video (should've done this before hijacking the thread, sorry) and it seems like I'm having a different issue. Instead, mine does the android boot animation, the goes to "Starting Apps" and counting ("x of y Apps"; the y value seems to be different every time), then "Staring Apps" with no count, then it says "Powering Off" and shuts off. But I will post my experience in case someone else with my issue finds this thread.
I'm back up & running today. I got it into the bootloader last night and put it on the charger before I went to sleep (to avoid battery rundown by bootlooping while it charges). I woke up this morning to it bootlooping again. I'm guessing that it restarted itself sometime during the night. I took it off the charger and let it sit for a while (it was pretty warm, so I figured it would be better to let it cool down before trying anything else). I tried to restart it again after about a half hour, but it still only got to "Starting Apps" before shutting off. I reflashed the stock boot, recovery & system images found here: Stock Boot, Recovery and System for G Watch R . I restarted it and completed the initial pairing process (due to wipe when I unlocked it in order to flash system image) and it is now working.
I don't know if what I did actually fixed anything or if it just decided to start working, but I will post again if something happens again. If you don't see any more replies from me, then all is still OK.
EDIT 6/22/15 9:53 pm EDT: No good, see below.
To workaround the bootloop while charging, you can boot into recovery (swipe 10 to 4 a clock while Logo is shown, select and press okay to recovery), than charge battery for a while, after that, you can boot to as normally to AW-system and charge to fully battery!
You can charge with USB on PC, it's work fine for me.
scidon37 said:
I just watched the video
I don't know if what I did actually fixed anything or if it just decided to start working, but I will post again if something happens again. If you don't see any more replies from me, then all is still OK.
EDIT 6/22/15 9:53 pm EDT: No good, see below.
Click to expand...
Click to collapse
So your gwatch r started doing the same thing again? I have the same problem and it won't connect to the computer via fastboot or adb. How did you get on with the RMA? I cant send mine back due to voided warranty. Still hoping for a solution.
Have you tried taking it off the charger and booting it? Also are you running custom software?
bricked watch
atmosphrericks said:
So your gwatch r started doing the same thing again? I have the same problem and it won't connect to the computer via fastboot or adb. How did you get on with the RMA? I cant send mine back due to voided warranty. Still hoping for a solution.
Click to expand...
Click to collapse
Ever find a fix for this? I've been searching like mad the last few weeks. :/
biohazard1150 said:
Ever find a fix for this? I've been searching like mad the last few weeks. :/
Click to expand...
Click to collapse
So i took off the back plate, and found that the spring contact pins inside the watch weren't making good connections to the connect points on the inside of the back plate. Be careful, they are fragile, but you want to bend them out slightly. If you can source parts, get a new contact pin module.
After this, i was able to connect my watch and flash over stock firmware.
I can't guarantee this is what is happening with yours, but let us know if it does work.
I've scince broken the screen and can't find where to get parts!
atmosphrericks said:
So i took off the back plate, and found that the spring contact pins inside the watch weren't making good connections to the connect points on the inside of the back plate. Be careful, they are fragile, but you want to bend them out slightly. If you can source parts, get a new contact pin module.
After this, i was able to connect my watch and flash over stock firmware.
I can't guarantee this is what is happening with yours, but let us know if it does work.
I've scince broken the screen and can't find where to get parts!
Click to expand...
Click to collapse
I still haven't found a fix. My charging works fine, but no PC connection. The bootloader/fastboot wont come up, no logo or anything. I'm sure the EMMC chip is fried, it sounds like many are seeing this issue, some with a black screen and some with a snowy screen. I've had several galaxy phones do the exact same so I'm doubting it can be fixed without going to the manufacturer which mine came from redflagdeals and LG wont service the random online store purchases
I had to take the back off and clean and adjust the contacts that make contact through the back panel. Then I could connect via fastboot.
ouranos2k said:
You can charge with USB on PC, it's work fine for me.
Click to expand...
Click to collapse
This solved my problem. As soon as I plugged it into my PC it booted just fine
ouranos2k said:
You can charge with USB on PC, it's work fine for me.
Click to expand...
Click to collapse
This works for me too! Thank you!
Sent from my SM-N920C using Tapatalk