Hi All,
I just received a brand new Galaxy Note II from T-Mobile.
When I put in the battery, the phone automatically start up. After the initial setup, everything else seem to function normally.
When I tried to shutdown the phone (hold power button for ~3 sec and seelct "Shut down"), it would shut down and restart again by itself.
I tried factory reset, but that does not help.
I hope I don't have to send it back to T-Mobile, and wait for a new one,
Any ideas???
Thank you in advanced.
junks2010 said:
Hi All,
I just received a brand new Galaxy Note II from T-Mobile.
When I put in the battery, the phone automatically start up. After the initial setup, everything else seem to function normally.
When I tried to shutdown the phone (hold power button for ~3 sec and seelct "Shut down"), it would shut down and restart again by itself.
I tried factory reset, but that does not help.
I hope I don't have to send it back to T-Mobile, and wait for a new one,
Any ideas???
Thank you in advanced.
Click to expand...
Click to collapse
If you have not rooted it or flashed custom firmware on it, I would advise sending it back so that you get a device in very good condition.
You don't want to be stuck with a faulty device from day one. If you are able to get to a local T-Mo store, you probably should go there and see if they can give you another one in its place.
junks2010 said:
Hi All,
I just received a brand new Galaxy Note II from T-Mobile.
When I put in the battery, the phone automatically start up. After the initial setup, everything else seem to function normally.
When I tried to shutdown the phone (hold power button for ~3 sec and seelct "Shut down"), it would shut down and restart again by itself.
I tried factory reset, but that does not help.
I hope I don't have to send it back to T-Mobile, and wait for a new one,
Any ideas???
Thank you in advanced.
Click to expand...
Click to collapse
could be a fault with ur external sd card.....remove it before u attempt to shut down the phone.
Hey man just exchange the phone. A specially you from T-Mobile
Thanks guys. I will exchange the phone then.
Can I just bring it to the store and exchange it or I have to send it back? I am stuck at work now and cannot call TM.
Also, what about the rebate? Should I send the rebate using the new phobe or the old one?
Will my rebate still be valid?
Darn, what a pain!
I had a similar issue with my first note, it was caused by a short in the usb port, probably caused by moisture in my case at least, you try and examine the port and if you spot anything odd.
Swyped, from my finger to your face, on my Samsung Galaxy Note II
Hey all you people with HTC 10. I just had to get a replacement 10. Out of nowhere my 10 just rebooted to the boot loader screen and the screen would show the boot loader for maybe a quarter of a second then it would turn off. It would repeat this cycle every 5 seconds. Would not respond to any combination of button presses.
My 10 was completely untouched.
I'm not sure what happened, but I'm starting this thread to maybe find some answers. Maybe it was a lemon or something else happened
anyone have any ideas?
I have the same problem...
I don't find issue...
I'm triing to change it with my buyer...
Yaum92300 said:
I have the same problem...
I don't find issue...
I'm triing to change it with my buyer...
Click to expand...
Click to collapse
The phone just had a software update pushed to it so hopefully that fixed the bug. I really don't want to replace phones a third time since getting it just so takes a little bit for me but yeah fingers crossed.
Good luck getting a replacement phone, sometimes it can be hard to.
srsparky32 said:
The phone just had a software update pushed to it so hopefully that fixed the bug. I really don't want to replace phones a third time since getting it just so takes a little bit for me but yeah fingers crossed.
Good luck getting a replacement phone, sometimes it can be hard to.
Click to expand...
Click to collapse
Thank you for your answer.
I also think that is a blind software update that cause the problem, but there is no solution to uninstall or find it...
My phone is now off, but if i try to on it(with charge or not, usb to cpu, volume down+power,etc), boot loop again.
Only the logo HTC is different when i use volume down+power, but no recovery mode available...
Quote:
Originally Posted by srsparky32
The phone just had a software update pushed to it so hopefully that fixed the bug. I really don't want to replace phones a third time since getting it just so takes a little bit for me but yeah fingers crossed.
Good luck getting a replacement phone, sometimes it can be hard to.
Thank you for your answer.
I also think that is a blind software update that cause the problem, but there is no solution to uninstall or find it...
My phone is now off, but if i try to on it(with charge or not, usb to cpu, volume down+power,etc), boot loop again.
Only the logo HTC is different when i use volume down+power, but no recovery mode available...
Anyone find an answer? Mine is doing the same,no recovery mode at all, just continues to reboot.
My Verizon HTC 10 tale of woe, after 3 weeks of awesomeness.
Got a new HTC 10 on August 3. I get an SD card, format it as internal storage and it worked fine until ...
Monday, August 22: I noticed that the soft buttons on either side of the fingerprint scanner weren't responding to touches. Decided to reboot the phone, thinking something was stuck in either the software or hardware, and a reboot usually fixes these types of things. However...
The phone went into a reboot loop: for several seconds it displayed a white background with a green HTC in the middle and the text "Powered by Android" at the bottom (called the 'white HTC screen' from now on), then went black for several seconds. Then the cycle repeats, and repeats, and repeats.
Did some looking around online and found a couple of potential useful button combinations: power/vol_down gets into recovery mode (except for me it displays a black background with a grayscale HTC logo in the middle (called the 'black HTC screen' from now on), followed by a black screen, displaying each for about a second or so (a faster cycle than the white HTC screen loop above.)
Also, the power/vol_down/vol_up combination gets into the bootloader menu, but not reliably. Sometimes the phone shows the bootloader menu (choices are Reboot/Reboot to bootloader/Download mode/Recovery mode/Powerdown)for a fraction of a second, then goes to the black screen and starts another reboot loop. It usually takes 2 to 4 attempts before I can stay in the bootloader menu.
Both the Recovery and Download menu options show the black HTC screen for several seconds, followed by the white HTC screen reboot loop. No useful options or other text at all. Reboot to bootloader reboots to the bootloader menu, reliably. Reboot goes directly to the white HTC screen reboot loop, and Powerdown powers down the phone.
If the phone is powered off (by the method above) and then plugged in to the charger, it displays a rectangle with a lighning bolt inside it (powered-off-and-charging display) for a few seconds, then the screen goes black and we go into the white HTC screen reboot loop.
Called Verizon support, explained the above to them, they send me a new phone which will arrive in 2 days. It does.
Wednesday, August 24: New phone arrives. I put my sim and SD cards in it, power it on, set it up, and start downloading apps. After I have a number of apps installed I take a break from that and format the SD card as internal storage. While this is going on (or maybe after it completed), the phone stops responding to the two soft buttons like the last phone did. This time, the phone rebooted itself after I fiddled with it for a little while, and it ended back up in the white HTC screen reboot loop. Argh!
Called Verizon support, fiddled around with the phone some more, and they said they would overnight me another replacement phone (waived overnight surcharge).
Thursday, August 25: I ship phones #1 and #2 back. Phone #3 did not arrive. I call Verizon, it turns out that the overnight order was never approved. It gets approved, I request Saturday delivery (it was too late to go out Thursday as the warehouse had closed).
Friday, August 26: I get a tracking number out of Verizon's system, check the Fedex tracking information and it's listed as Overnight, weekday delivery. I call Verizon again, they admit the screwup and send me another phone (#4) overnight, Saturday delivery (it's early in the day so there should be no problem getting the phone to Fedex in time for an overnight delivery.)
I check Verizon's system, get the new tracking number, check Fedex. Phone #4 is marked as second-day air, delivery on Tuesday. I call Verizon back, they can't change anything with Fedex after pickup. Looks like I'm getting 2 phones, one on Monday and the other on Tuesday. I get a bill credit for the time I am without a phone and all shipping charges are waived.
Monday, August 29: Phone #3 arrives. Put the SIM in but not the SD card, it's DOA with the white HTC reboot loop out of the box. I call Verizon, nothing useful. I get a new SIM card from the local Verizon store on the off chance that the problem is a bad SIM card. I have another phone coming tomorrow.
Wednesday, August 31: Phone #4 arrives, didn't have time to do anything with it until today. The phone comes up (with the new SIM), I start installing apps, and I then get a 'Firmware update available, download?' popup. I say yes, and then agree to the reboot when prompted. The display shows the 'unpacking' dialog, percent-complete goes up to 100%, then the phone reboots. White HTC screen reboot loop.
Call Verizon, this time they put me through to HTC support. They have me download something called 'HTC Sync Manager' (HSM from now on). While fiddling with HSM and the phone I somehow get it to boot successfully (but have never repeated this feat), it came up with the pre-firmware-upgrade version but the need-a-fingerprint-to-unlock configuration (and maybe other settings) has been lost. Looks like the phone isn't physically damaged at all, but something is messing up the bootloader. The HTC rep tries to get me to send the phone to HTC (with a 10-or-so day turnaround), I say no as Verizon is sending me phones with about 2-day delivery. I then retry the firmware download, get back in the white HTC screen reboot loop and never succeed in getting the phone to boot to Android again.
From my searching around on the Internet, it looks like HTC came out with an update on 8/15, maybe Verizon's OTA pushing of this update is causing the problem? No way to confirm, but it would explain why my phone was fine for 3 weeks, then kablooie across multiple phones.
The Verizon rep suggested taking the phone to the local Verizon store, maybe they can flash the phone with new firmware using tools not available to us mere mortals. Try it, no they can't do that.
Thursday, September 1: I ship phone #3 back. Order a Samsung S4 from Amazon so I'll have a working phone. 2-day delivery with Amazon Prime, and USPS delivers on Saturday. I need to take a break from spending my evenings on the phone with Verizon.
Saturday, September 3: The S4 arrives. It needs a different sized SIM card, but the local Verizon store has closed already. Call Verizon to try to see if they can do anything on the 'firmware update went bad' tack, maybe with a way to initiate a firmware download from the bootloader menu. No luck, but there's a new firmware update dated 08/31 that should fix the problem. He overnights me another phone (#5), estimated arrival is Wednesday due to Labor Day, and gives me a callback number so he can help me with downloading the firmware from the computer after getting the phone to its homescreen doing as little setup as possible.
Sunday, September 4: Go to a wedding. Make it to the Verizon store (in suit&tie) 1/2 hour before they close. They need the phone in order to activate the SIM. Drive home, get phone, drive back, get a working SIM. After 13 days, I have a working phone again.
TO BE CONTINUED....
The first installment wasn't "A New Hope", maybe this one is "HTC Strikes Back".
Wednesday, September 7: New phone (#5) arrives. Verizon tech support is busy tonight, don't get a call back from Verizon so I call them. Activate the HTC SIM, put it in the phone, and did a minimum config on the phone to get it to the homescreen. Connect the phone to the computer, put USB in software download mode, enable USB debugging. HTC Sync says 'No phone connected', driver installation popup complains about an unknown USB device but says several other HTC-ish USB devices are OK. Try disconnecting and reconnecting several times, no change. Sometimes get a 'virtual CDROM connected, run this installer or view files' popup, one time I copied its contents to the computer. During all this the Verizon rep forwarded me to HTC for assistance, but nobody answered. After a few minutes of dead air I got thrown into a satisfaction survey, I answered with 'would not recommend', 'unsatisfactory' and 'did not resolve my problem' responses. Dialtone.
Called Verizon back, had to wait again. During the wait I uninstalled HTC Sync Manager and HTC Driver Installer, reinstalled them (via the software on the virtual CD image) with the phone disconnected, then reconnect the phone. No 'unknown USB device' errors this time, but HTC Sync Manager still doesn't see the phone. Verizon rep suggested enabling USB Tethering. This produced a few more successful USB driver install popups but nothing helpful. Next suggestion is doing the OTA update (need to enable wifi so it doesn't eat my data allowance).
Download completes. Soft buttons on either side of the fingerprint scanner stop working (like before) even though touching the screen still works. I keep the Verizon rep updated as to the rapidly deteriorating state of the phone. He suggests a poweroff and poweron, I say it's gonna die if things go as they have but he says to do it anyways. I do, and the phone is in the reboot loop like all the others.
Verizon rep tries to call HTC tech support but they are closed. He'll call be back at 5:30 EDT to continue.
TO BE CONTINUED....
wow, its a real shame to have a device die on you but 5 is a catastrophe, really interesting writing though . it seems to me that the firmware update screws things up but then again many Verizon users have the phone with no similar problems whatsoever, would really like to be updated with any new information regarding the issue as it peaked my interest. sorry i cant help .
dpeterson said:
Wednesday, September 7: New phone (#5) arrives. Verizon tech support is busy tonight, don't get a call back from Verizon so I call them. Activate the HTC SIM, put it in the phone, and did a minimum config on the phone to get it to the homescreen. Connect the phone to the computer, put USB in software download mode, enable USB debugging. HTC Sync says 'No phone connected', driver installation popup complains about an unknown USB device but says several other HTC-ish USB devices are OK. Try disconnecting and reconnecting several times, no change. Sometimes get a 'virtual CDROM connected, run this installer or view files' popup, one time I copied its contents to the computer. During all this the Verizon rep forwarded me to HTC for assistance, but nobody answered. After a few minutes of dead air I got thrown into a satisfaction survey, I answered with 'would not recommend', 'unsatisfactory' and 'did not resolve my problem' responses. Dialtone.
Called Verizon back, had to wait again. During the wait I uninstalled HTC Sync Manager and HTC Driver Installer, reinstalled them (via the software on the virtual CD image) with the phone disconnected, then reconnect the phone. No 'unknown USB device' errors this time, but HTC Sync Manager still doesn't see the phone. Verizon rep suggested enabling USB Tethering. This produced a few more successful USB driver install popups but nothing helpful. Next suggestion is doing the OTA update (need to enable wifi so it doesn't eat my data allowance).
Download completes. Soft buttons on either side of the fingerprint scanner stop working (like before) even though touching the screen still works. I keep the Verizon rep updated as to the rapidly deteriorating state of the phone. He suggests a poweroff and poweron, I say it's gonna die if things go as they have but he says to do it anyways. I do, and the phone is in the reboot loop like all the others.
Verizon rep tries to call HTC tech support but they are closed. He'll call be back at 5:30 EDT to continue.
TO BE CONTINUED....
Click to expand...
Click to collapse
I just had the same thing. Soft keys stopped working>Rebooted>Bootloop.
Very strange. Anyone else hear of this?
Are these issues hitting the "unlocked" version or the Verizon version? Could it be a CDMA issue?
I was debating picking up an HTC 10 due to having to return my Axon 7 because WiFi caused it to reboot constantly.
Wow just a few days ago the same exact happened to my 10. I happened to have an iphone 6s so after trying all day from the bootloader to reboot to recovery I decided to just sell the 10 in swappa boneyard. I bought it second hand from craigslist so didn't bother trying to contact htc directly assuming they wouldn't help since I didn't have an original purchase order. I put up a post here but never checked back to see if anyone replied with any solutions. Good luck. Seems like there's several people who experienced the same exact behavior. Such a shame.
The Firmware Menace
[ These are all stock Verizon HTC 10 phones (LTE/CDMA), not rooted, not unlocked or anything. All but the first were either dead-on-arrival or died attempting an over-the-air firmware update. ]
Thursday, September 8: Verizon actually calls me back this time, we try a number of things, none of which are different from what I've already tried and none of which work. They send me a new phone (#6).
Friday, September 9: I send phone #4 back.
Monday, September 12: Phone #6 arrives. I send phone #5 back. I leave phone #6 alone for the time being, I desperately need a break from spending my evenings on the phone with Verizon support.
Friday, November 18: I see that Verizon has a new version of the HTC firmware out and I decide to give phone #6 a try. Maybe the new firmware won't break the phone. I plug the phone into the charger (it's been powered off for 2 1/2 months), and it shows a battery charge level of 0%. I set it aside and do other things.
A while later I notice the occasional <bzzzt> sound. I identify the source as the phone, and see that it's in the reboot loop. (the phone vibrates momentarily when it displays the white HTC screen.) Another DOA phone.
Monday, November 28: I get around to calling Verizon and give them the 'firmware update went bad, replacement phone was DOA story, they immediately offer to replace the phone. Hopefully it'll have the November firmware pre-loaded. We'll see.
Thursday, December 1: Phone #7 arrives. DOA with the reboot loop. Called Verizon. They offered to send me another replacement phone (what's the point!), and then tried to get me to use an upgrade / get on device payments to get a different phone. NO WAY NO HOW! At this point I should get a no-cost exchange to a similarly-priced different model phone, not "throw away the $600-ish you spent on the HTC-10 and buy another phone".
I had to suggest contacting HTC support (they didn't think of it!), which they did. I explained what the phone was doing to the HTC rep, and he suggested I send my phone in for service. At this point what do I have to lose, they should send the phone back with the latest firmware. At worst, I'm right where I started (a non-working HTC 10). HTC is going to email me shipping instructions.
Midnight at the Cliffs of Insanity
Friday, December 2: Phone #6 goes back to Verizon, phone #7 goes to HTC to be repaired.
Monday, December 19: Phone #7 returns from HTC. Same problem. Phone charges normally at first, but goes into the boot loop immediately upon poweron.
There's no explanation of what they did, just a 'shipped from warehouse' receipt in the box. HTC's "track this return" page gives no details either.
Left a description of the problem (sent back a phone with a reboot loop problem, got back a phone with a reboot loop problem) on HTC's Facebook page.
Checked the serial number of the phone from HTC versus the serial number of the last phone Verizon sent me. They're different, it looks like they just sent me a new phone rather than reflashing the one I sent them.
Tuesday, December 20: Saw a response from HTC. In brief, try reloading the firmware with HTC Sync Manager or try contacting HTC Support.
Tried HTC Sync Manager. It never recognized the phone as being connected (in the bootloader menu, boot-to-download mode -> reboot loop, boot-to-recovery mode -> reboot loop, reboot -> reboot loop from both the bootloader menu and from poweron.) This is the same as previous attempts.
Contacted HTC Live Support, had to wait less than a minute (good). Explained the problem to them (including the 'sent a phone in for repair, it came back broken the same way' part). Blew past the 'did you try diagnosing the problem' phase in 3 1/2 minutes, and they want me to send the phone back to them. This time they'll create an escalation for the repair, hopefully this'll provide more visibility into what is going on and avoid another "didn't do anything to repair, shipped a different, just-as-broken phone". They also said that they would manually test any phone before sending it to me to make sure it has the latest Verizon firmware and boots successfully into Android. The proof will be in the booting.
Wednesday, December 21: Phone #7 goes back to HTC.
Another One Bites The Dust
Friday, January 6:
Phone #7 comes back from HTC (same serial number). Boots up (no sim, no SDcard) fine. Insert sim, reboot, still OK. Switch service to the phone, it works. Latest Verizon firmware is 1.85.605.9, the phone is at 1.85.605.8. Load some apps, start using it. Put in an SDcard, format as internal storage, everything is good so far. Everything is working as expected.
Saturday, January 7:
The phone works great for most of the day. Late in the day I get a notification about a firmware update, which I defer. A couple hours later I notice that the soft buttons on either side of the home button/fingerprint sensor had stopped working. (just like the original problem with phone #1). Found a way to force the lights to be on when the phone is on (someone said that this fixes the 'soft buttons don't work' problem, but I think it was just a 'soft buttons don't light up when you want them to be lit' problem. Found the setting in Settings, buttons light up but are still unresponsive.
Reset the phone (DIDN'T install the firmware update), back in the infamous reboot loo, same symptoms as before. Tried removing the SD card and SIM card (A Reddit comment thread said this worked for some people), no help.
same problem here.. looks like there is not any solution.. right?
sublimesed said:
I just had the same thing. Soft keys stopped working>Rebooted>Bootloop.
Very strange. Anyone else hear of this?
Click to expand...
Click to collapse
I am experiencing the same problem since today. The phone has the latest update installed. (not rooted, bootloader locked)
Its so disappointing ! I'm in India but I bought this phone from middle-east on December 2016 and I have to sent it back there for warranty claim which will not happen very soon.
Have anyone found a solution for this problem ??
My only solution when this happened to me was do the Boot Recovery reboot and recover/reset phone. Press Volume-Down and Power button together for at least 30 sec. You have to wait. A black screen with gray HTC will show up. Only let go once you see this screen (not before). Select boot to bootloader, then boot to recovery. Then do factory reset.
Its happening to unlocked versions also, i bought mine from Sydney unlocked and it just happened to me. IM freaking out i dont know what to do!!
Someone please help if they have a solution
GRETEL GT6000 Infinite boot
Hi everyone,
I recently bought a GRETEL GT6000 for it's awesome battery,
sadely this phone is hard to root.
I try many & many solutions but no one root the phone and now my phone is in infinite boot with message "Orange state you're device has been unlocked and can't be trusted Your device will boot in 5 seconds"
I can't connect to adb or fastboot, I can't boot in recovery (volume up and power), in fact I can't do anything.
I try to pull of the battery but it didn't change nothing.
The last thing I was doing before this, is to flash a custom recovery.img (made with both official rom and a TWRP rom).
I'm hopeless & I'll be glad if somenone have an idea to share it here.
Ricardo