Related
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Sounds like a DOA. Really bad luck.
If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse
If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.
Was it bnib?
mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?
Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.
I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.
Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head
P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?
badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts
I have a G1 running stock 1.6, and this just happened randomly. One day I can hear everything out of the back speaker such as notifications and music, and the next, nothing... I need to know if I need to replace the speaker, or if re-flashing my device would hopefully fix this. It still vibrates for the notifications and I get the LED flashes, I just don't hear anything. And all the volumes are all the way up. Also, if I do factory reset from the settings, would it go back to stock 1.6, or would it go to 1.1?
If you're running stock, chances are your speaker just went out. I don't think they're replaceable without replacing the whole motherboard. I actually tried to Google this for a friend and all my efforts yielded no fruit other than motherboard swapping. It's probably easier to just buy a new G1 or upgrade with T-Mobile or service provider. You can also check to see if you have warranty with T-Mobile or your service provider.
Edit: No, a factory reset will not downgrade Android. It will erase all apps and set all settings back to factory default.
Also, Android version tree is as such:
1.5 - Cupcacke
1.6 - Donut
2.1 - Eclair
2.2 - Froyo
3.0 - Gingerbread (unreleased)
Well, the thing is, I haven't been with T-Mobile in over a year cuz I owe them $400, but I still use it for everything else through my wifi. I've had it since Feb. '08. And I know what the versions are, but when the G1 first came out, it had 1.1 and I'm pretty sure it doesn't have a "code name" like the other releases. I mentioned it cuz when I've rooted my device, I had to go to 1.1 temporarily. Also, I took the back off my G1 (the one you have to screw off) and the speaker is right there, so I think it is replaceable without replacing motherboard. And I found out about the factory reset, I went and did it, but I forgot that I need to connect with my Google account so I have to wait for my brother to get here so I can use his SIM card.
This is my second SGS with this problem and I am trying to determine if it is common or if I am just monumentally unlucky.
During normal use the bottom soft keys (menu and back) will become non-functional. One will stay lit and one will go out, but both will cease to work. Everything else on the phone is still responsive, sometimes the keys 'revive' themselves after a short period of time, other times I need to lock the phone to get them back.
I got this phone (a replacement) on the 6th, and this started on the 12th and has been happening more and more often ever since. Has anyone else seen this or have an idea what it may be? Or is this phone is destined to be my 2nd DOA in a month?
Here is a video showing the problem: '
you tube.com/watch?v=1s-wqWsHaIs
That is definitely not normal behaviour.
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
hol17 said:
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
Click to expand...
Click to collapse
FYI: Samsung support told me to return my phone.
It is almost like one of the soft keys gets stuck 'down', because it is the same behavior if you just hold down one of the keys. Mine seems to happen more when bluetooth is on and it comes and goes in spurts; good for an hour, bad for an hour, etc.
ETA: I am sure now that the soft keys are getting 'stuck down'. I have seen it 3 times now where I would press the left soft key and the light on the key will remain out, then after a second or so the quick search screen comes up and the left soft key light is still out.
any solution to this problem? i seem to have a slightly different issue
this just happened to me recently everything was working fine until this morning when i tried to press the menu and back buttons it wouldnt work, although the buttons light up and is registering my actions when i press them the light turns off and let go is lit up again.
could this be a software issue or something conflicting with my lednotification mod?
please reply ^_^
I've got the exact same issue with my soft keys getting stuck too. Just started a couple days ago, phone's less than a month old. I was also told to take my phone in for repairs.
Oh one tech support guy told me that Froyo might fix it... I'm kinda hoping for that, seeing as how this issue isn't exactly 100% reproducible for the warranty service department
I have the same problem its almost like the soft key is being held down, anyone find a fix for this?
Add me to the list
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
robcarey said:
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
Click to expand...
Click to collapse
Lock it back and go again.
I know this post it's a bit old, but i was harvesting the web looking for an answer to my problem that seems to be the same posted here.
I have a i9000T with eclair 2.1 and soft keys get stuck now and then. I couldn't find a way to reproduce this behaviour.
Recently (yesterday) i flashed a new 2.3.3 firmware hoping this curse to end. The problem seems to persist, but in some situations that i asume for a bad flashing (i didn't repartition neither wipe the phone before flash).
Anyway, can anybody tellme if this is a software or hardware issue? I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
cknu said:
I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
Click to expand...
Click to collapse
Only one way to find out mate.
You need to flash a 2.1 rom that consists of 3 files. 512 pit and re-partition.
Should get you back on track again.
I did flash it again with the 2.3.3 JVH, a few moments ago. Also did a repartition and wipe data and cache. It seems nice, but in a few minutes the same happend. Now, when i press the menu button it takes a nice screenshot of the phone. xD
I need to flash to a 2.1 version? Why is this? I thought flashing with any rom will work.
Thanks.
Solution to this problem!
Hey all - I found a solution to this problem - I can confirm this has fixed the problem on TWO phones for me - read the whole thread as this fix doesn't like custom firmwares, but works fine with all the regular FWs I've downloaded.
Works perfect - and simple fix!
http://forum.xda-developers.com/showthread.php?t=869492
^^^
Do not do this unless you have a i9000m. You will break your buttons.
electrotune1200 said:
^^^
Do not do this unless you have a i9000m. You will break your buttons.
Click to expand...
Click to collapse
Too bad i didn't see this before
I have I9000T used this 2663 method and now my soft buttons doesn't work anymore...
Didn't find a clear solution in the forums so i want to ask, like i said my phone is a I9000T with official 2.2.1 (UBPJA) rooted using SuperOneClick and unlocked editing the nv_data.bin file.
I was thinking on doing a hard reset to get back to the factory defaults but i see many ways of doing it that it gets confusing... i see peolple doing it through the privacy menu but i think that only erase data and doesn't restore anything OS wise, also see other people doing it using volume + home + power and selecting later clear storage, i think this is the same that the option in the privacy menu, and finally i see some people typing this code *2767*3855# what is the proper way to get back to the original OS in my case?
Thanks in advance...
Firstly, may I apologise, I know this has been covered, I've trawled the internet for hours but just can't seem to get an answer.
I recently updated my UK, unlocked Galaxy S to Froyo via the registry hack, all was fine (ish). Because Froyo had been delayed in the UK and wasn't as great when it was running on my phone I thought it would be safer to revert back to 2.1 and wait until the official UK release came out (I know some will ask me why I did this, I just felt that Froyo was held back for a reason and I couldnt get an answer as to if I could update to the UK version if I already had the Scandinavian one). So I did the reg hack again and was offered 2.1. Everything seemed to go smoothly until the phone rebooted after downloading from Kies. Now the phone's animation starts then the flashing S symbol displays for an extended time. After that, the screen goes black. If I touch the two touchscreen buttons they stay on but do not go off. If I hold the power button the phone turns itself off and when the phone is powered off and I plug it into my PC with a USB, the battery charging sign comes on.
The phone was rooted and I did have the OCLF on but uninstalled that and un-rooted before changing the firmware so it was back to stock.
Before I get 20 people telling me to put the phone in download/recovery mode I must tell you that I can't. My phone has never been able to do it. I've tried every single way and button order suggested. I'm not the only one who's phone won't do it either so it's not just me. The only way I ever saw recovery mode on my phone was when I used the one click root on the PC.
I'm at a total loss. Debugging was turned off because Kies won't let you do anything with it turned on and so ADB recovery is out also.
Please help if you can.
Many thanks,
Ryan
Boot to download mode, do a repartition with Odin and 512 pit flash, remove battery and boot again to download mode and then do a odin firmware flash to which ever firmware you want.
thanks intratech but I can't boot the phone into recovery or download mode (sorry should have stated that). Believe me, I have tried every combination. I did a lot of research and discovered that there are quite a few people for whom that feature was disabled.
if the 3 button combo is not working on your phone, you should not do these risky stuff actually
take a look at this thing
http :/ / forum.xda-developers.com/showthread.php?t=819551
remove spaces
thanks Noobproof. I remember coming across that thread last night. Although I consider myself ok with software, soldering and slicing just isn't my forte. I haven't got a clue about soldering, etc. I've just come back from the Carphone Warehouse (Samsung suggested I go there as they are the service centres listed on the Samsung UK website). The engineer had the phone for half hour and said that the "board was faulty". Haven't got a clue what he meant by that, unless he meant the internal SD which a few people have had go on them. Anywho, he told me to ring Samsung and send it in for a repair. I did that and need to send my phone special delivery to a company called regenersis in Scotland.
I knew rooting and flashing custom roms was a risk, that's why I never touched Odin,etc. I used Kies to upgrade to Froyo and Kies to downgrade back to Eclair. You would think that sticking to official Samsung software would be safe. I must admit, when it was going well I loved my Galaxy but more and more I'm starting to wish I'd opted for the Iphone.It just seems that there have been so many glitches and bugs, I mean, why should there ever be a need for lag fix in the first place? I often found myself keeping my fingers crossed when downloading simple apps as that was usually touch and go!
Feeling a bit deflated now. Was hoping some clever boffin had designed a software solution that would recognise the phone and force it into download/recovery mode.
Ah well, thanks for taking the time to respond anyway.
Best wishes,
Ryan
You know i was very happy when i for the phone for the first time and while i was doing a research (i live in turkey and there is no stock android market here) i came along this forum. And i have learned that i havent got the 3 button combo. I downloaded the 3 button fix abd took the phone to samsung centre.
They told me that they cannot flash it and i made a huge fight then they accepted and i have my 3 buttons. Never give up your phone. I dont think the internal sd is faulty it is just corruppted if you can access the recovery menu you could fix it. Any way you have to find a service centre that has an anyway jig box other a jtag box otherwise they will have to replace the motherboard. Good luck
Sent from my GT-I9000 using XDA App
I had the same problem all i did was use a different firmware .. didnt choose anything in pitfile and did not check on repartition but checked only F reset and Auto reboot and flashed my phone and voila it booted perfectly fine
Hope it helps others with black screen problem after booting
thanks
mike
I had the same problem too. This method really works.
Wysłano z GT-I9000 z użyciem Tapatalk
Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign
^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.
I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.
A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.