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
Are there any issues with this known, is there any tests that can be performed on the hardware? When I had WM6.5 I could test various hardware pieces such as the speaker, flash or display.
Non-Rooted
2.2.1
Baseband/32.36.00.28U_4.06.00.12_7
Kernel/[email protected]#1
Build/FRG83D
This is a phone that I bought my friend for his birthday. I have a Samsung Vibrant Galaxy S.
I actually plan to sell mine and get a Nexus One. I really like the phone better then my Vibrant.
If you haven't already, do a factory reset (settings>privacy>factory reset). Since your unrooted it's unlikely it's a software fault.
Second resort, call HTC. Warranty's are device based, not owner based, so if the device is still under warranty you can get a new one
As a last resort, if your warranty is expired, I would root it without unlocking the bootloader. Try a couple different ROM's and kernals and see if you get any results.
I actually had this problem a while back. I was getting FC's every time I tried to access the camera (through any app). I figured I dropped it and broke a connection or something inside. I finally called HTC and they sent me a new one.
I had to restore everything back to stock since it was running CM6. After everything was back to stock, the camera magically started working again (and I reverted to some nandroid backups from months before and the camera still didn't work then). I returned it for a new unit anyway and HTC didn't charge me or say anything.
Hello!
I had purple tint on my old HTC One, so I sent it for repairs under warranty and I got a completely new unit. It was working for a day, but today it couldn't connect to the network. At first I thought it was a HW issue, but I realized that Dialer was crashing with a message: "com.htc.htcdialer is not responding.". That made me think it was a software problem, so I tried doing a factory reset in HBOOT, but now htcdialer is still crashing, and I can't even go through initial setup, it just keeps rebooting when I try to unlock it for the first time. Is there any other way to flash a ROM, without being able to boot the phone?
Everything is completely stock, bootloader is locked and phone is not rooted. I updated it to the latest available version, 4.4.2 with Sense 5.5, I'm unsure what version it exactly is. I would like to keep it stock for at least a couple of days in case there is a hardware failure and I have to send it back to service, but I can do anything if it's necessary.
Thank you very much.
HBOOT image, if it is of any help: http://i.imgur.com/3XKC6Br.jpg?1
Since its completely stock and you just got the phone, I wouldnt bother going through and installing a custom rom, its too much of a hassle and if it ends up being a hardware problem its an even bigger issue.
I'd contact HTC again and see if they can do anything about it, or just send it back again under warranty. Flashing a custom rom in your situation isnt worth it imo.
Bhavpreet said:
Since its completely stock and you just got the phone, I wouldnt bother going through and installing a custom rom, its too much of a hassle and if it ends up being a hardware problem its an even bigger issue.
I'd contact HTC again and see if they can do anything about it, or just send it back again under warranty. Flashing a custom rom in your situation isnt worth it imo.
Click to expand...
Click to collapse
That's exactly what I've been thinking.
I was actually able to get it to go through initial setup between reboots and I was able to install a RUU, a the same thing is happening again, so I'm pretty sure it's HW related. And it still isn't getting any signal. It's a bit of a problem because I have to bring it to a store 150km away, but I'll have to do it :crying:
[email protected] said:
That's exactly what I've been thinking.
I was actually able to get it to go through initial setup between reboots and I was able to install a RUU, a the same thing is happening again, so I'm pretty sure it's HW related. It's a bit of a problem because I have to bring it to a store 150km away, but I'll have to do it :crying:
Click to expand...
Click to collapse
Ahh that sucks. Call them and make some excuse about how you cant come to the store and see if you can ship it to them.
I recently hard bricked my LG G4 and I was given this phone by someone I know. The phone had a cracked lcd which has since been fixed.
I reformatted to phone back to stock firmware, DOK2. And. I followed the instructions in how to root and install twrp to then ultimately install a custom ROM. Got all that and I have a custom ROM and I am rooted. But the phone lags like crazy. I am trying to type now and I am tapping faster than the keyboard actually acknowledges. Also, if I try to watch Netflix or even an embedded video from the browser, the video "hiccups" every 8 seconds or so.
What I have done.
I wiped the entire phone, including internal SD and external. I did this twice and I Odin stock twice. After I tried the custom rom and experienced the lag. I started from square one again. BTW, the lag happens on stock ROM, too. I have tried Ovrdrv and tek hybrid on both I have SU 2.52 installed and I tried beast and emotion kernels. The lag is real. Maybe this phone is designed to work in this manner when compared to my G4,rip.
On a side note, this phone was given to me in not the best shape. I mentioned I changed the LCD, but the phone's back button and fingerprint scanner don't work. It is also missing the stylus, but that's not a big deal for me. The charging port works fine and so does the recent button and both the back and recent light up. At this point I am thinking it's a hardware issue and it's conflicting with the software somehow. I downloaded different keyboards but they all do the same. I can type maybe 5 short words before it freezes for about a second.
Videos playing directly from device also lag like streaming services, but mp3 and music do not lag.
I can't help with the Note, but did you brick the G4, or did it die because of the known hardware issue? Those phones are dropping like flies. I had one that recently fell into a boot loop out of nowhere. AT&T replaced it, no questions asked. LG has acknowledged a hardware issue. Bad connections on the mobo, I think. I sold the new one to buy the Note. Didn't really like the G4 anyway!
How long did you allow to settle before you wrote this post? The phone needs a couple days to settle before it runs optimally. Did you install any apps or mods such as xposed?
Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!