Database Develop

Nexus - repair centre HTC

Hi,
I'm going to sent my Nexus one to the HTC repair centre, because he's been having this annoying random reboots.
My nexus has an unlocked bootloader, with a rooted custom rom. Is this going to be a problem for HTC? I mean, did I lost my warranty?
Because the problem is a hardware problem (I guess), so it has nothing to do with the custom rom...
Is there any possibility to lock the bootloader again and make the device look like how it looked when I bought it?
Thanks in advance!

are you sure this is a hardware problem? these kind of reboots are not uncommon with custom roms, have you tried chaing roms or kernels and seeing if that fixed it?

guybanda said:
are you sure this is a hardware problem? these kind of reboots are not uncommon with custom roms, have you tried chaing roms or kernels and seeing if that fixed it?
Click to expand...
Click to collapse
I've changed the kernels a few times. An I had the reboots on CM7 and on Miui.
Those roms are pretty stable I guess? And I haven't heard others complaining about reboots.
the reboots occur really randomly. Sometimes after a phone call, sometimes while browsing, sometimes while taking a picture. Sometimes I take my phone out of my pocket and it has rebooted, so I have to type in the PIN-code...
I tried factory reset and a clean install, with/without a2sd. with stock kernel, or with another kernel...
I don't know what to do anymore

After you flash any of these ROMs do your restore via titanium backup or similar because it happened to me once that every time I tried to open angry birds (weather it was normal seasons or beta) it would try to start then it would crash and it was no in the market and every time I would go to download it the phone would start the download then right before the install (when it hit 100%) it would go back to the cyanogen mod boot logo (I was running cyanogen obviously) so maybe it is something in your data that is screwing up and it keeps getting restored with titanium.

When you say a clean install, does this include MANUALLY wiping the /system partition?
Anyway, to your original question, unlocking your phone does void the warranty, that being said, HTC is usually good about replacing phones when it is a true hardware defect and keeping it as a warrantied repair. Most likely, when you get your phone back (if they don't replace it with a new one), it will be locked again with the stock OS on it.
But, your warranty is void, so HTC does not have any legal requirement to fix it under warranty. I am just telling you what I have noticed from other people's experiences.

bassmadrigal said:
When you say a clean install, does this include MANUALLY wiping the /system partition?
Anyway, to your original question, unlocking your phone does void the warranty, that being said, HTC is usually good about replacing phones when it is a true hardware defect and keeping it as a warrantied repair. Most likely, when you get your phone back (if they don't replace it with a new one), it will be locked again with the stock OS on it.
But, your warranty is void, so HTC does not have any legal requirement to fix it under warranty. I am just telling you what I have noticed from other people's experiences.
Click to expand...
Click to collapse
Yes, I manually wipe everything.
Ok, thanks for the answer.
Since the warranty is void, does it still matter with which rom I give them the phone?
If they see a non-rooted stock rom, maybe they won't think the problem is caused by a custom rom?

Probably not. For any hardware problem, I'd bet the first thing they are going to do is flash a completely stock ROM to verify it isn't some software bug.
It is just easier than trying to troubleshoot. I don't even know how many of them would turn it on and let the phone boot up as that takes away a lot of time depending on how many phones they service in a day.

Hi!
I have the same problem and I could assure you guys that's a Hardware issue!!!
Probably the same as the HTC Desire!
From my personal experience I've sent my Nexus One 2 times and the assistance resend it to me simply reinstalling Froyo 2.2! I've sent the phone another time and, actually, I already have to do it back!
So, my Nexus is away since 2 months, counting all the 3 times!
I hope this time HTC have completely repaired my device. But still waiting for it...
NOTE:
I have an unlocked bootloader too, and you know that there's no way (actually) to re-lock the bootloader.
So the only thing that I do, before send the device to assistance, was to install the original Rom (Froyo or Gingerbread doesn't matter) and the original Recovery!
Obviously you must Wipe ALL (cache, partition, etc), to not encounter some kind of error's.
For the unlocked bootloader question, I don't think HTC void the warranty, because the Nexus One IS a Developer's Phone!!!
So it might be OPEN!
I'll post back later when I have my Nexus back with me.
Sincerely,
Matthew

Iperzampem0 said:
Hi!
For the unlocked bootloader question, I don't think HTC void the warranty, because the Nexus One IS a Developer's Phone!!!
So it might be OPEN!
Click to expand...
Click to collapse
While it is a developer phone, when you go to unlock the recovery, it does state that it voids your warranty. But I think HTC is decent enough to realize when it is a hardware issue that they are willing to still honor their warranty. I know a lot of people who got their power button repaired with unlocked bootloaders, because HTC knows it is a valid defect. BUT... they are not required to honor the warranty as it is void the minute you unlock your phone.

Where can I find the stock recovery?
I'm afraid this is also going to happen with my nexus, that they send him back, but the problem is still there. I'va read it happens to al lot of people :S
It's not even sure they can reproduce the problem. It's not like the phone is rebooting every 5 minutes...
about the reboots:
I've read a alot about it on the forums. And it seems that lots of android devices have this problem. Does anyone knows what might cause these reboots?
Maybe it has something to do with heat, which damages the motherboard?

den_breacker said:
Where can I find the stock recovery?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=709340
Does your warranty center not support the advanced exchange? In the US, you can have them send you a new phone (while holding $520 of yours in reserve)... once you get the new phone, you send the old one back and they release your funds.
If you are that worried about it, I suppose you could just brick your phone yourself by screwing up a radio flash. That will prevent the phone from even booting, but I wouldn't/couldn't ever recommend doing this.

Tomorrow HTC is coming to pick my phone up
Hopefully they can fix the problem.
I've put the 2.3.4 OTA rom on the phone
Thanks for all the advice!

Restore phone to factory

I have an N7000 running Cyanogenmod 10.1 with Clockworkmod.
I've got an issue with the power button. Earlier it was rebooting itself. lf over the slightest press and now it's doing nothing at all. Luckily the phone is on so I haven't lost access to it.
I'll need to return the phone to the repair centre under warranty but because I've rebooted it then it may not be valid, despite this being a hardware issue.
Is there a way to restore the phone to Samsung Factory firmware.? I have done it before but with a different phone, I believe I used something called Odin which was a download able app.
Hopefully someone can help.
Cheers.

mattburley said:
I have an N7000 running Cyanogenmod 10.1 with Clockworkmod.
I've got an issue with the power button. Earlier it was rebooting itself. lf over the slightest press and now it's doing nothing at all. Luckily the phone is on so I haven't lost access to it.
I'll need to return the phone to the repair centre under warranty but because I've rebooted it then it may not be valid, despite this being a hardware issue.
Is there a way to restore the phone to Samsung Factory firmware.? I have done it before but with a different phone, I believe I used something called Odin which was a download able app.
Hopefully someone can help.
Cheers.
Click to expand...
Click to collapse
You mean rooted and not 'rebooted'?
http://forum.xda-developers.com/showthread.php?t=1424997&highlight=odin

vish91 said:
You mean rooted and not 'rebooted'?
http://forum.xda-developers.com/showthread.php?t=1424997&highlight=odin
Click to expand...
Click to collapse
Indeed - apologies.
I'll give that a go. Hopefully that'll do the trick.
Cheers.

Red Triangle Stock Sense 6 update

Just received the stock update to Sense 6. I am in Canada, on Telus, fully stock.
When the phone boots into the recovery to flash the update, I am getting a red triangle and the error is unexpected contents in settings.apk
Any suggestions on how to get this update working other than hard resetting before the update?
Thanks.

Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.

SaHiLzZ said:
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
Click to expand...
Click to collapse
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?

mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
Not heard of a problem while updating. You are special.

What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?

mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Great idea!

mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Did your problem solved?

Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....

mfpreach said:
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
Click to expand...
Click to collapse
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port

alray said:
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
Click to expand...
Click to collapse
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?

mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
hi, we have similar issues although mine is the soundhound_freemium.apk instead of settings.apk, I hope that you will get your issue settled and also update me and the rest of us who are having the issues here. good luck and thanks! (do check out my thread which I've just posted like 5 minutes back!)

Do not install sense 6 upgrade
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
I posted about my issue in another thread. In case people want to read what's been going on i'll repost it here.
Kg810 said:
So I performed the Sense 6 upgrade a couple days ago, update went through fine, yesterday morning my phone started acting all weird (sluggish, random reboots, bunch of apps reporting errors, etc) and battery was draining fast.
I probably rebooted my phone 10 times, 5 times normally by just the power button and the remaining times through the light trick, power button and volume button. Once my phone finally got back to normal, I was typing on whatsapp and then suddenly it froze.
It froze for a couple minutes and then it turned off. I believe the battery was at 39%. I plugged the phone into my work computer and it would make the USB connection sound, then after a few seconds it would display drivers failed to install followed by 3 subtle sounds similar to the connection sound. So right away I checked Device Manager and it displayed QHSUSB_DLOAD.
Currently my phone has been charging all night, currently it is being charged at work and there has been no sign of life.
I've tried putting it in the freezer, the light trick, the laptop connecting/disconnecting trick, and the go ole punching the phone trick. None of them have worked.
The phone is definitely not charging at this point as it is stone cold when I hold it or touch the wall charger.
Any ideas what I can do? I don't want to contact Rogers and have to send it in. I've got so many songs, videos and pictures I have yet to backup.
Any help and/or suggestions welcome.
Click to expand...
Click to collapse

Kg810 said:
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
Click to expand...
Click to collapse
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
---------- Post added at 05:23 PM ---------- Previous post was at 05:22 PM ----------
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
if you have a win7 computer, then use that one.

alray said:
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
Click to expand...
Click to collapse
Maybe I wasn't clear.
Tuesday night before I went to bed I performed the upgrade.
Wednesday morning, is when the issues started occuring.
Today is May 29th, Tuesday was May 27th, which is 2 days ago, hence why I said I performed the upgrade a couple days ago.
From the time I performed the install Tuesday night to Wednesday morning when I got into work, there was nothing done to the phone. The only thing that was done was the Sense 6 upgrade.
So you're trying to tell me that the upgrade has nothing to do with it?

Kg810 said:
So you're trying to tell me that the upgrade has nothing to do with it?
Click to expand...
Click to collapse
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence

alray said:
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
Click to expand...
Click to collapse
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.

Kg810 said:
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Click to expand...
Click to collapse
Anyway, your only way out of this qhsusb brick is to send your phone for repair.
Sorry

mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
facing same problem with you. my problem haven't fix. from malaysia

akasi91 said:
facing same problem with you. my problem haven't fix. from malaysia
Click to expand...
Click to collapse
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?

kuzumitaiga said:
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
Click to expand...
Click to collapse
6xxmb.

Unresponsive screen (top and bottom)

Sometimes when I unlock the screen, and try to swipe down the notification bar, it doesn't respond to the touch command. Bottom part becomes dull too. Keyboard gets crazy: press "q" and "a" appears.
Been reading on the Motorola forum, and in the US, people return their phones to get a new replacement, at least that's what tech support is doing. But in my country (El Salvador) cust service s+cks!
Has anybody had this issue? Did anybody solve it? My phone is still with the stock ROM and hasn't been rooted yet.

Lochrecan said:
Sometimes when I unlock the screen, and try to swipe down the notification bar, it doesn't respond to the touch command. Bottom part becomes dull too. Keyboard gets crazy: press "q" and "a" appears.
Been reading on the Motorola forum, and in the US, people return their phones to get a new replacement, at least that's what tech support is doing. But in my country (El Salvador) cust service s+cks!
Has anybody had this issue? Did anybody solve it? My phone is still with the stock ROM and hasn't been rooted yet.
Click to expand...
Click to collapse
I faced the same problem at starting I cleared my cache and done a factory reset after that doesn't face the problem again.

sumit227 said:
I faced the same problem at starting I cleared my cache and done a factory reset after that doesn't face the problem again.
Click to expand...
Click to collapse
I've done it, but didn't work at all!
Sent from my XT1063 using Tapatalk

Lochrecan said:
Sometimes when I unlock the screen, and try to swipe down the notification bar, it doesn't respond to the touch command. Bottom part becomes dull too. Keyboard gets crazy: press "q" and "a" appears.
Been reading on the Motorola forum, and in the US, people return their phones to get a new replacement, at least that's what tech support is doing. But in my country (El Salvador) cust service s+cks!
Has anybody had this issue? Did anybody solve it? My phone is still with the stock ROM and hasn't been rooted yet.
Click to expand...
Click to collapse
Have you tried custom ROM ???

Devesh25 said:
Have you tried custom ROM ???
Click to expand...
Click to collapse
No way!
It's because phone is under hardware warranty. Carrier doesn't get responsibility for the software, though. And just because of that, I can't get a new phone with them, nor can I modify phone's ROM, as it nulls any kind of warranty.
This is the post on the Motorola forum.
https://forums.motorola.com/posts/52124a8edc

If you have warranty you don't have to solve anything, just send back your phone and get a replacement.
They must replace or repair the phone..

Lochrecan said:
I've done it, but didn't work at all!
Sent from my XT1063 using Tapatalk
Click to expand...
Click to collapse
That works for me. Maybe problem is resolved by installing custom rom but I think you have to replace your phone.

sumit227 said:
That works for me. Maybe problem is resolved by installing custom rom but I think you have to replace your phone.
Click to expand...
Click to collapse
I might give it a shot. What ROM have you installed?

Lochrecan said:
I might give it a shot. What ROM have you installed?
Click to expand...
Click to collapse
I'm not using any rom currently. But there is titan prime rom in development section you can try that.

And what If it's a hardware issue? You install custom rom and if the problem still remain than you can't send it back, because you don't have warranty anymore.
I think the first step is sending back the phone.

zman01 said:
And what If it's a hardware issue? You install custom rom and if the problem still remain than you can't send it back, because you don't have warranty anymore.
I think the first step is sending back the phone.
Click to expand...
Click to collapse
Definitely, you have a point there. But I suspect it's not hardware since it's just a ramdom behavior. I haven't done either step though.

Seriously annoying problem after lollipop upgrade

I have the HTC one m7,stock/unrooted. Im not sure if this problem is because of a bug or a setting that needs to be changed. When the screen is off I'm somehow able to turn the screen back on by pressing either volume button. This becomes annoying when I have it in my front pocket when I'm working and I take out my phone to check a message and see that the screen was on the whole time. Then when I double tap the home button to see my recent apps, I notice that random apps are open including the camera and sometimes it would call/text random people. If you are wandering how it is sitting while in my pocket, the power button is @ the top,so the only keys being pressed is the volume rocker. Before lollipop I never had this issue. I have already tried a factory reset (not a app issue) and clearing system cache to no avail. Another thing I've noticed I'd when I'm on the home screen with the phone unlocked I'm able to use it in landscape mode. If anyone can give me a permanent solution to this problem I'd greatly appreciate it.

This is very odd since the problems you're telling is actually a feature of some custom roms. I'd suggest you to backup your internal storage and RUU.

lerenturk said:
This is very odd since the problems you're telling is actually a feature of some custom roms. I'd suggest you to backup your internal storage and RUU.
Click to expand...
Click to collapse
Im guessing by a Ruu you mean a factory reset?

racingmatt1 said:
Im guessing by a Ruu you mean a factory reset?
Click to expand...
Click to collapse
Yes but not the one you make on the phone. You download the RUU tool to factory reset the phone, it should fix your problem.

lerenturk said:
Yes but not the one you make on the phone. You download the RUU tool to factory reset the phone, it should fix your problem.
Click to expand...
Click to collapse
Where can I get the Ruu tool and what the difference between it and a factory reset on the phone itself?

racingmatt1 said:
Where can I get the Ruu tool and what the difference between it and a factory reset on the phone itself?
Click to expand...
Click to collapse
RUU will wipe entire OS and reflash it. Phone factory reset wont work if some of your system files are corrupt or missing. You can find them on android developement section prior to your variant