I got my HTC One not so long ago, but when i received it, it wouldn't play through my headset (tried several different ones). I downloaded SoundAbout it worked (as a temporary fix), but now some days ago the sound where acting strange. When i turn the volume to full there's almost no sound, I can barely hear it, with both speakers and headset.. I rooted mine, and I'm using Cyanogenmod, I've tried to re-install to stock several times ( and different types of Roms), but nothing works. I heard this is a really common issue for this specific model.. Anyone have any solution?
Sadly, I unlocked the bootloader and customer support says that the warranty doesn't cover it. I got these problems before I unlocked it, but I was stupid enough to unlock it before sending it to repair.
Could anyone help me?
I am sorry to hear about your problem. I have a HTC One and I used several different earphones and headphones and they all worked perfectly fine, but the volume controls do not work, just the play/pause/answer/reject button. I'd suggest relocking the bootloader and sending it back to the company since it seems like a hardware issue rather than a software one, especially since you've tried different ROMs and applications. There are great guides on returning back to stock, and you'd have to use ADB in order to relock the bootloader and remove the TAMPERED flag (if you have a custom recovery installed at the moment).
TarekElsakka said:
I am sorry to hear about your problem. I have a HTC One and I used several different earphones and headphones and they all worked perfectly fine, but the volume controls do not work, just the play/pause/answer/reject button. I'd suggest relocking the bootloader and sending it back to the company since it seems like a hardware issue rather than a software one, especially since you've tried different ROMs and applications. There are great guides on returning back to stock, and you'd have to use ADB in order to relock the bootloader and remove the TAMPERED flag (if you have a custom recovery installed at the moment).
Click to expand...
Click to collapse
Thanks for the answer !
If I relock it, can I send it for repair without paying for it (Does warranty cover it?)
I cannot guarantee it or anything because it works differently in different counties but I'd say if you revert everything back to stock as in bootloader, recovery, Rom and such then you'd have a very high chance of getting it repaired or replaced under warranty. When relocking the bootloader it will say relocked rather than its original locked state, but you can claim you purchased it used like that or something.
EDIT: Actually I just realized that you can revert back to a 'locked' rather than 'relocked' state using ADB, so you should be set. I am going to look for that specific post with instructions on how to do that and get back to you.
Sent from my HTC One using Tapatalk 4 Beta
Related
My camera stopped working. Any attempts to use it (via the camera app, goggles, camera 360, etc) gives me a force close.
I called HTC, and they're sending me a replacement, but if the warranty is void, they will charge me a repair fee once they receive the one I have now.
Since it is most likely a hardware issue and not a software, I've heard of instances of HTC letting it slide, but I don't want to pay up to $200 for a replacement motherboard if that's the problem.
Anyway I can improve my chances? I know the bootloader can't be locked.
Flash everything completely back to stock before sending I guess.
thats what ive heard as well, flash stock recovery, boot, data, system
my first Nexus had an unlocked bootloader. I just flashed the Stock ERD2.1 to it and threw it in the box.
Nothing said about it.
My new one, I did the SD card trick in the bootloader to root it without unlocking the bootloader. I guess now-a-days it is a much simpler process.
I have sent 2 phones with unlocked bootloaders into HTC and i haven't been charged anything. For my third phone i justed the root without unlocking bootloader.
well the camera magically started working again, and I already put in my credit card info and the other one is shipped
since it isn't broken anymore, should I be concerned?
I just got my One a week ago today, and rooted it the first day as well. From last Wednesday to earlier today, I've had no issues at all with it; suddenly, audio is not working at all, either through the headphone jack or speakers. I thought it might be a ROM issue, so I reflashed the ROM clean (PACMan 4.2.2), and it still didn't work. I flashed 2 other ROMs, SlimBean and a Sense 4.2.2 based one, and the audio still doesn't work at all. I've done nothing that could've damaged it; I don't overclock, it's never gotten wet, nothing. Has anyone else had this issue, and know a fix, or do I have to return it to stock and turn it back into Sprint?
Also, another note- earlier today it was getting really hot for no reason- I wasn't running anything that would do that, no OC like I said. I Googled, and many people said it was a common occurrence due to the aluminum body dispelling heat from the internals. It went away after 20 minutes or so, so I figured it wasn't an issue. Could that have done some damage? Thank you for any help in this, I'm really worried since I just got the phone and it's already having issues. I've loved it otherwise so far, and owned 3 other HTC phones, and nothing like this has happened before, so I hope it's just a one time thing.
I don't have the audio issue with any rom I flashed, maybe your device is damaged. You can return it for a new one.
I also have the heat problem...
sent from my m7spr using tapatalk 4
I've been backing up my stuff to get it ready to take back. I hear the blue model's coming to Sprint on the 10th, maybe I can hold out a few more days and pick up one of those
Update- I've been trying all morning to restore to stock, and I'm getting worried now.
I went by this thread http://forum.xda-developers.com/showthread.php?t=2250904 to use that RUU to return to stock. I am trying to relock my bootloader in fastboot, and I get the error "[Err] Command Error!" each time I try. To use the RUU, I need to have a locked bootloader, but I can't get a locked bootloader because of that error. What might be wrong here? I am using the stock USB cable with a USB 2.0 port, Windows 7 32 bit.
Alright, it turns out that was due to a stupid error on my part. I have got my bootloader relocked, but now when I try to flash the RUU, I get the 171 USB Connection error. It'll get stuck on the black HTC screen at that point. What could possibly be wrong now?!?! If anyone has any tips, I can provide as much further information as you may need.
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.
Hi there... new to the forum, but long-time reader, especially over the past two days since I dropped my AT&T HTC M7 (flashed to GPE) on cement and it pretty much died.
I'm out of ideas and could use some help. After the drop, it was stuck in a boot loop, but I was able to get to hboot with volume down. From there, I can access fastboot, but recovery or factory reset options just trigger the boot loop again. During the loop, it shows the Google logo (or HTC logo when flashed to stock) for 15-20 seconds and then reboots. Physical damage to the phone is not too substantial, and I have unfortunately extensive experience opening it up from repeated attempts to fix the purple tint issue with bad modules from eBay, so I checked inside and everything is intact.
Over the past two days I've flashed RUUs and recoveries like crazy, downgraded and upgraded hboot, changed CID, etc. I can oem lock and unlock... fastboot kicks out an error when I do it, but the status in hboot is changed when I reboot into the bootloader. Flashing ROMs and recoveries works like a charm, so does erasing cache. What I mean is that the process works exactly like before in fastboot, and I can see the splash screen logo change, so I know it's taken effect, but NOTHING gets past the boot loop. I am thinking the drop resulted in a corrupt partition, but since I can't get into recovery I haven't been able to find any way to do anything about that. If it was physically broken, it just doesn't seem like I would be able to do everything I can. I initially thought maybe it was a busted/stuck power switch, but that works perfectly navigating hboot menus and nothing ever auto-selects or anything like that, which I would expect.
Aside from the fact that I really like this phone, and that I really don't want to have to pay to replace it, I feel attached to it since I've dismantled it successfully to repair more than once and flashed ROMs many times in the past without issues. I've just run out of ideas, and of course I can't go on much longer without a phone.
Does anyone have any experience with this or hunches I can try out?
placebored said:
Hi there... new to the forum, but long-time reader, especially over the past two days since I dropped my AT&T HTC M7 (flashed to GPE) on cement and it pretty much died.
I'm out of ideas and could use some help. After the drop, it was stuck in a boot loop, but I was able to get to hboot with volume down. From there, I can access fastboot, but recovery or factory reset options just trigger the boot loop again. During the loop, it shows the Google logo (or HTC logo when flashed to stock) for 15-20 seconds and then reboots. Physical damage to the phone is not too substantial, and I have unfortunately extensive experience opening it up from repeated attempts to fix the purple tint issue with bad modules from eBay, so I checked inside and everything is intact.
Over the past two days I've flashed RUUs and recoveries like crazy, downgraded and upgraded hboot, changed CID, etc. I can oem lock and unlock... fastboot kicks out an error when I do it, but the status in hboot is changed when I reboot into the bootloader. Flashing ROMs and recoveries works like a charm, so does erasing cache. What I mean is that the process works exactly like before in fastboot, and I can see the splash screen logo change, so I know it's taken effect, but NOTHING gets past the boot loop. I am thinking the drop resulted in a corrupt partition, but since I can't get into recovery I haven't been able to find any way to do anything about that. If it was physically broken, it just doesn't seem like I would be able to do everything I can. I initially thought maybe it was a busted/stuck power switch, but that works perfectly navigating hboot menus and nothing ever auto-selects or anything like that, which I would expect.
Aside from the fact that I really like this phone, and that I really don't want to have to pay to replace it, I feel attached to it since I've dismantled it successfully to repair more than once and flashed ROMs many times in the past without issues. I've just run out of ideas, and of course I can't go on much longer without a phone.
Does anyone have any experience with this or hunches I can try out?
Click to expand...
Click to collapse
yeah try a new motherboard yours is broken, really it's hardware damage no amount of flashing will fix it
clsA said:
yeah try a new motherboard yours is broken, really it's hardware damage no amount of flashing will fix it
Click to expand...
Click to collapse
Thanks clsA. I'm surprised by that since in my experience a broken motherboard results in a much more substantial and obvious failure, but I guess the point is moot if I can't get into recovery to try anything else.
There isn't much of a market for new motherboards, and my experience with eBay sellers for oem components on this device makes me think trying to replace it there would be a fool's errand. I guess I could buy a used M7, but on the other hand the damn thing has basically been nothing but problems. The defective camera turned to garbage in under a year and one drop killed it? Unless anyone has another suggestion, I guess it's time to cut my losses on this thing. I may feel a sentimental attachment because I've nursed it along so much, but damn... a phone is a phone and this one has been a LOT more problematic than any other one I've had.
Gotta thank you again clsA! Your words of doom made me feel that extra bit wreckless, so I decided if the phone was cooked anyway I might as well tear it down and try whatever I could... firmly reseating cables and squeezing heatsinks, etc. Low and behold, I reassembled and the problem is fixed! I'm not sure what the exact issue was, and I won't be surprised if it comes back at some point down the line, but I'm back up and running tonight and that's a hell of a lot more of a victory than I was expecting.
So... it wasn't a motherboard issue, but it was hardware related.
I should have posted on here when this first happened. I love xda!
placebored said:
Gotta thank you again clsA! Your words of doom made me feel that extra bit wreckless, so I decided if the phone was cooked anyway I might as well tear it down and try whatever I could... firmly reseating cables and squeezing heatsinks, etc. Low and behold, I reassembled and the problem is fixed! I'm not sure what the exact issue was, and I won't be surprised if it comes back at some point down the line, but I'm back up and running tonight and that's a hell of a lot more of a victory than I was expecting.
So... it wasn't a motherboard issue, but it was hardware related.
I should have posted on here when this first happened. I love xda!
Click to expand...
Click to collapse
That's great, I'm glad you were able to fix it
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!