Related
Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.
You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.
Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin
Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.
Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.
Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.
I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.
"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.
Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.
15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.
On Friday night, My phone was in the breast pocket of a blazer that got very damp in an unexpected downpour. The phone continued to work on Friday night as far as I recall (I wasn't using it much, but I'm pretty sure I did use it some). When I woke up on Saturday morning, it appeared to be off and wouldn't turn on. I pulled and replaced the battery and still got nothing. I put it on the charger, but I had to run out, and I ended up being gone all day.
When I came home, the power button still wouldn't turn on the device. I pulled the battery and replaced it, and the Google screen came on, then the CM10 boot animation. When it got to the pin screen, however, the screen wouldn't respond to me entering my pin. Then, after a minute, the screen turned off, and the power button wouldn't turn it back on. I did a battery pull. Again, replacing the battery brought up the google screen, the CM10 boot animation, and the pin screen. But, again, the screen was unresponsive, and the power button did nothing when the screen went off.
I took it apart and left it alone all day Sunday. On Monday morning, I tried again and got the same results. I went and picked up a bag of white rice yesterday and left it in there last night and all of today. Still, I've got the same outcome. Buttons and screen are unresponsive.
So I'm left with a couple of questions:
First, is there anything else that can be done? This seems to me to be water damage. Does anyone have any suggestions for possible solutions?
And second, I keep getting text messages. Is there any way to pull those messages using the Toolkit or adb or anything (I'm pretty inexperienced with adb)?
Any help would be great. I'm stuck in China without a phone right now, which is a pain in the butt. I'd like to revive this, and I don't want to go track down a new phone until I know this one is sunk. Thanks for your help.
install android-sdk
run adb server on the host
connect your device to pc (feed it naked drivers manually found on dev section, if you're on windows and device manager shows unknown device)
type: adb devices
q: do you see your device listed? (should be lots of numbers and letters)
if it doesnt even recognizes that it has been plugged in, then your usb connection went down the drain, nothing else you can do
My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2
ejchis said:
My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)
bk201doesntexist said:
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)
Click to expand...
Click to collapse
And you would expect this to resolve the screen and buttons being unresponsive? This is interesting. Is it possible to pull my messages beforehand?
Sent from my Nexus 7 using Tapatalk 2
Hi everyone,
first off, I've spend days now trying to find a fix. If I've missed anything, I'm sorry, it wasn't for lack of trying.
Here's the situation: I have acquired an HTC One X earlier this year which has worked quite flawlessly. I went ahead and unlocked the bootloader and installed a custom recovery. However, since I handed the phone off to my not-so-techy sister I did not use a custom ROM, and after the HTC update failed with the custom recovery I reversed that as well. The device should now be stock everything with unlocked bootloader.
After a few months my sister encountered heavy problems, though. She described them as battery related (wouldn't turn on correctly) and eventually she moved to a new phone. Now I have gotten the device back and I am trying to fix it. After charging it I managed to have it boot once. However, I but it to the side and wanted it to load some more. Ever since then the screen doesn't come on. The charging LED seems to work fine (eventually switched from red to green, too, indicating that the device is fully charged) and the button backlight still works, too. Most significantly though, the device is recognized as MTP device in Windows: I can access all the data in the storage without problems.
I have read that there is an issue with the HTC One X and the display connector so eventually I went ahead and took the device apart. It's lying in front of me now in pieces, but I still couldn't get the screen to come alive. The obvious conclusion would be to buy a new screen but the device doesn't feel like it's worth the investment. Besides, I would like to know for sure that it's the screen before I do anything.
So I turn to you guys and ask if you have any idea how I could access the phone via my computer. I tried to boot it up in bootloader mode but due to the strange standby methods HTC is using and not seeing anything on the screen I haven't been able to do that yet: Whenever I connect my USB cable it's recognized as MTP device, not ADB. Debugging seems to be deactivated so that doesn't seem to be an option. Does anyone have any idea how I could get the phone to talk to my computer (i.e. get into the bootloader or ADB screencast for sure)? With my Galaxy S I could simply plug in this dummy micro USB and would be sure to end up in download mode.
Any help is appreciated!
tl;dr: HTC One X screen is dead but LEDs work, is recognized as MTP device. How to make it talk to the computer?
Thanks,
rien
Alright, sometimes just posting stuff like this helps already. I was now finally able to get the phone into fastboot (apparently) and it's reacting to the fastboot commands. I suppose the next step is to load CWM and connect via adb. This way I can at least do a factory reset.
Does anyone have any ideas regarding the original issue with the screen? Especially since it does seem to work occasionally. And doesn't show any fragments...
Can I enable USB debug mode from within the recovery to work in the system?
Last night I tried turning on my Pixel C only to see a screen saying enter android password ive never seen this screen before so i figured i would try my Google password and i got a second message saying "the password you entered is correct but unfortunately your hard drive is corrupted and you will have to factory reset your device" or something along those lines so i hit factory reset where the open android appears and it had text in the bottom saying something like erasing hard drive i left it like that since i had somewhere to go and when i came back the pixel c was completely dead so i connected it to the charger and tried turning it on and it would boot to the google logo then the four dots and just reboot all the time i was not able to even leave it turned off i did try factory resetting the pixel through android manager but still had the same problem. has anyone else experienced this problem? i have contacted google and they are sending me a replacement just wondering if anyone knows whats wrong with it and why it messed up like this
yes, i am aware of the screen and the factory reset erase sequence. but the reset sequence occured while full charge and plugged into a pc . if the battery on yours was near discharged during the erase sequence it might have completely discharged before completing the factory reset which usually results in somewhat unknown issue. best to plug it in to charger before erase sequence if this happens again. good to hear that another unit is on its way.
xm0is3sx said:
Last night I tried turning on my Pixel C only to see a screen saying enter android password ive never seen this screen before so i figured i would try my Google password and i got a second message saying "the password you entered is correct but unfortunately your hard drive is corrupted and you will have to factory reset your device" or something along those lines so i hit factory reset where the open android appears and it had text in the bottom saying something like erasing hard drive i left it like that since i had somewhere to go and when i came back the pixel c was completely dead so i connected it to the charger and tried turning it on and it would boot to the google logo then the four dots and just reboot all the time i was not able to even leave it turned off i did try factory resetting the pixel through android manager but still had the same problem. has anyone else experienced this problem? i have contacted google and they are sending me a replacement just wondering if anyone knows whats wrong with it and why it messed up like this
Click to expand...
Click to collapse
Exactly the same thing happened to me, it was fully charged back then and after I reset the tablet it went in to boot loop. I got the new replacement now and it is working better now
damjan006 said:
Exactly the same thing happened to me, it was fully charged back then and after I reset the tablet it went in to boot loop. I got the new replacement now and it is working better now
Click to expand...
Click to collapse
Tell us please, how the replacement device. Because I am from Russia and I detail it is important to find out how things are going.
dkryder said:
yes, i am aware of the screen and the factory reset erase sequence. but the reset sequence occured while full charge and plugged into a pc . if the battery on yours was near discharged during the erase sequence it might have completely discharged before completing the factory reset which usually results in somewhat unknown issue. best to plug it in to charger before erase sequence if this happens again. good to hear that another unit is on its way.
Click to expand...
Click to collapse
im guessing the battery was around 80% when it decided to mess up so i think it got stuck formatting the hard drive and just died from there
damjan006 said:
Exactly the same thing happened to me, it was fully charged back then and after I reset the tablet it went in to boot loop. I got the new replacement now and it is working better now
Click to expand...
Click to collapse
any guess why this happened to yours? im thinking it might have to do with the magnets inside the pixel C i did stick it on the fridge to see if it was pretty strong (dumb yeah i know) lol it did work fine while stuck to fridge but messed up a few hours after that
This just happened to me. Here is the sequence of events that led up to it.
1. Fully charged and unplugged it. ( I did pull the unit off the keyboard as it was propped up but this shouldn't affect the storage right? )
2. It did a random reboot after taking it off the charger.
3. It asked for my password in a "pre-boot" screen
4. The message I get is : "Decryption unsuccessful" "The password you entered is correct but unfortunately your data is corrupt.
"To resume using your tablet you need to perform a factory reset. When you set up your tablet after this reset you'll have an opportunity to restore any data that was backed up to your google account."
jlcutler said:
This just happened to me. Here is the sequence of events that led up to it.
1. Fully charged and unplugged it. ( I did pull the unit off the keyboard as it was propped up but this shouldn't affect the storage right? )
2. It did a random reboot after taking it off the charger.
3. It asked for my password in a "pre-boot" screen
4. The message I get is : "Decryption unsuccessful" "The password you entered is correct but unfortunately your data is corrupt.
"To resume using your tablet you need to perform a factory reset. When you set up your tablet after this reset you'll have an opportunity to restore any data that was backed up to your google account."
Click to expand...
Click to collapse
thats the same message i got also after turning on the display I also have a keyboard and took it off to put the tablet on the fridge and put it back on the keyboard afterwards and it still worked fine until i turned the screen off and tried to turn it on later
jlcutler said:
This just happened to me. Here is the sequence of events that led up to it.
1. Fully charged and unplugged it. ( I did pull the unit off the keyboard as it was propped up but this shouldn't affect the storage right? )
2. It did a random reboot after taking it off the charger.
3. It asked for my password in a "pre-boot" screen
4. The message I get is : "Decryption unsuccessful" "The password you entered is correct but unfortunately your data is corrupt.
"To resume using your tablet you need to perform a factory reset. When you set up your tablet after this reset you'll have an opportunity to restore any data that was backed up to your google account."
Click to expand...
Click to collapse
yup, this has happened to mine several times but except for one time, i just pressed vol dn & power to get to the options screen and rebooted. so i did not have to reset but one time. but mine has not died yet. i also think the magnets might be causing this and some other issues
I've just had the same thing this morning and I'm in the process of a truly awful conversation with Google support during which I had to explain to them what "stuck in a bootloop" meant...
I've had this one since a week after launch, working fine - I assume there weren't any recent updates that changed any of the memory partitions?
You guys could always try to unlock your bootloader from fastboot and reflash the stock images.
PriyanPhoenix said:
I've just had the same thing this morning and I'm in the process of a truly awful conversation with Google support during which I had to explain to them what "stuck in a bootloop" meant...
I've had this one since a week after launch, working fine - I assume there weren't any recent updates that changed any of the memory partitions?
Click to expand...
Click to collapse
God I hate dealing with non-technical customer service reps, the devs from Dolphin Browser didn't understand portrait vs landscape, I ended up stopping the conversation because I'd rather beat my head against the wall. Same thing goes for Wizards of the Coast and Magic 2015, I asked then why all my data on my tablet didn't sync to the cloud since it was using Google Play games so I could continue the game on my phone and they just kept on saying "It's not meant for phones so that's why it doesn't work" even though it actually worked perfectly on my phone, they also kept calling me by the wrong name, even after multiple corrections.
Sent from my Pixel C using Tapatalk
I have the EXACT same problem on my 32GB píxel c, i am returning it.
Enviado desde mi XT1039 mediante Tapatalk
Same here
Okay, same boat here. Just received my Pixel C two days ago. Pretty neat to use, put always fully charged. Several unresponsive(freeze) occurs to me, especially when I tried Lens Blur feature in Google Camera. But overall I'm pretty satisifed with the experience and design.
Today I got onboard of a airplane. I guess it's after X ray security check machine... then I opened the tablet it prompted me with password. And the following with sort of "your drive is corrupt but we can restore it from Google backup" things. I clicked next (it's fully charged by now) and the looping restart begins. I can't even turn it off until I find the vol down + power trick to enter the recovery menu. But right now it's completely unusable. I think I'll request a order returning when I'm back...
I've just had the same experience on a third Pixel C, this time after about a week. I think this time I'm just going to demand a refund. They've failed to send me a single working device and don't seem to have any fix for this. I can't go through a continual process of RMA-ing and losing any data not yet backed up indefinitely.
What country are you guys from for those of you having issues? I'm in the USA and bought mine as soon as it launched and haven't had a single issue with it, meanwhile I see a bunch of people are having random QA issues which seems to be pretty odd.
Sent from my Nexus 6 using Tapatalk
I'm in the UK. I bought at launch so I'm well outside the 30-day window, but I've gone through three different units. On the plus side, they agreed to a refund with no hassle at all so I assume this isn't an isolated issue. Thanks to Amazon Prime I'm already setting up a Sony Xperia Z4 and, whilst I'd still prefer stock Android and the Pixel C 's aspect ratio, I'm actually pretty impressed with it so far...
Same thing here.
Did your replacement function?
Some premium tablet
Screw Google for not sending a USB C to USB A 3.0 cable so I could at least attempt a ADB factory flash.
God I hate dealing with non-technical customer service reps,
Click to expand...
Click to collapse
You know "boot loop" isn't a technical term right??
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