Related
So, all yesterday, I was having problems getting service anywhere I went. Towards the end of the day I got no service anywhere. So... put my phone on the charger all night, woke up and... Nothing.
Phone wont turn on, battery pull won't work, can't get into bootloader. Orange light turns on when I plug into charge.
I was running the stock HTC ROM with a couple programs installed. Google maps, iContact and Soft Key Changer. Thats it. Had no problems until now.
I called the company I got if from said bring it back they will get me a new one (just got it last Sunday). I can't get Activesync to see the phone so reflash is not a possibility.
They won't be able to turn it on at the store, this thing is gone. But if someone somewhere sees its a new ROM when they send it back (if they can get it on), am I screwed? I think I'd just say the guy in the store did it cause he had is last...
from what I understand you void the warranty by using a different rom.
xconradx said:
So, all yesterday, I was having problems getting service anywhere I went. Towards the end of the day I got no service anywhere. So... put my phone on the charger all night, woke up and... Nothing.
Phone wont turn on, battery pull won't work, can't get into bootloader. Orange light turns on when I plug into charge.
I was running the stock HTC ROM with a couple programs installed. Google maps, iContact and Soft Key Changer. Thats it. Had no problems until now.
I called the company I got if from said bring it back they will get me a new one (just got it last Sunday). I can't get Activesync to see the phone so reflash is not a possibility.
They won't be able to turn it on at the store, this thing is gone. But if someone somewhere sees its a new ROM when they send it back (if they can get it on), am I screwed? I think I'd just say the guy in the store did it cause he had is last...
Click to expand...
Click to collapse
Try a different battery or a different charger first.
brynwall said:
from what I understand you void the warranty by using a different rom.
Click to expand...
Click to collapse
Thats what I understand too. However, you can't get the thing on, no connections - nothing. They won't be able to tell at the dealer for sure. And I think in this state it goes to the junk pile cause I can't get any connection on it period.
From my dealing with Cingular and having to exchange my 8125/Wizard, they always include the statement regarding voiding your warranty if you load unauthorized rom images on your phone.
That being said, I have sent back many bricked 8125's for various reasons (none of which were bad rom images), and I never had an issue with them actually noticing that I had a custom rom loaded on it.
Of course every carrier is different, but judging from my experiences, I think you'll be fine.
NotATreoFan said:
From my dealing with Cingular and having to exchange my 8125/Wizard, they always include the statement regarding voiding your warranty if you load unauthorized rom images on your phone.
That being said, I have sent back many bricked 8125's for various reasons (none of which were bad rom images), and I never had an issue with them actually noticing that I had a custom rom loaded on it.
Of course every carrier is different, but judging from my experiences, I think you'll be fine.
Click to expand...
Click to collapse
Cool, thanks man. I think I'll be fine too. I feel that the issues has nothing to do with the ROM, as the ROM has been working fine for a few days now with no glitches except for the service problem yesterday. I wont mention the ROm of course, but the thing does not turn on in any way whatsoever. The only thing that happens is when you plug in the power you get a orange light up top.
Thanks for your help, I'm glad they haven noticed even on working phones with different roms.
It sounds like it could be as simple as a power issue. Either charger or battery.
But I had the same thing happen to a Razor once. Bricked at the bootlloader screen and would not take a charge from that point on. My carrier (AT&T) had told me the device was beyond repair (translation: they had no clue at the store). Ended up having to borrow a charged battery to re-flash the device.
Haha, I bricked a razr once too, and was able to revive it with via a number of things (barely). I was trying to change the boot screen. Those phones are fun to mess with - at least you could get into the boot loader most of the time even if it was near death.
I'll try a different battery when I get to the store.
I went to the store just now, they changed the battery and... nothing she tried my battery in a new phone and it worked, so the battery is fine, but my phone is f*cked.
I am replaceing tomorrow.
Hi everybody,
a friend of mine got his HTC One (black) yesterday and rooted it. He flashed a proper custom ROM on it which I and another one of my work buddy use as well without any issues (InsertCoin). No further flashes done, no other custom kernels, no S-Off, no SuperCID. Just unlocked Bootloader and custom ROM.
He let the device run dry yesterday evening so it shut off itself automatically. He put it on his charger, the phone turned on, he did some surfing and installing apps from the market and set up his alarm. The phone charged over night and he was also able to switch off the alarm this morning.
He got ready for work, got into his car and wanted to switch on the screen on the one for some good tunes. But the screen stayed black.
When I arrived at work, he was a little upset and panicked a little. I thought I was able to recover the device.
After plugging it in to my work computer, the device manager just shows a unknown device called "QHSUSB_DLOAD" so I went to google and looked it up..
Weird thing is: QHSUSB_DLOAD wasnt seen yet on the HTC One (M7) as far as I can see it and it was pretty bad on the HTC One S. It means "Qualcom High Speed USB Download Mode" and on the One S as well as on the Nexus 4 this devices showed up after the bootloader got damaged or the device got stuck in that mode for good.
When plugging the device in (USB / Wall charger) the charging LED doesnt turn on at all, the capacitive buttons dont start to blink while holding down the power button as well.
This thing seems to be gone for good.
But aint it the way that we dont even have any access to the bootloader if its not an official update from HTC? Signature check and stuff? Since the device was rooted, no OTA updates were able to arrive at all. He told me that he didnt try to flash anything after we flashed the custom ROM.
Any advice on that?
Did you even try booting the device first thru hboot/bootloader or holding the power button to force a restart? If you did try connecting the device while on QHSUSB_DLOAD and execute a compatible RUU on your PC. RUU uses android's download mode to flash the ROM so it should be repaired by an RUU.
Already tried, no luck. Tells me the device has not been found.
I am sorry to hear that, man, but from the looks of it your friend now has a paperweight. I'd take it to an HTC service center and hear what they have to say regarding this; of course it will no longer be covered under warranty, but maybe they can fix it for you for a price or something.
Are you sure RUU can't find the phone? If it can't then I guess only a JTAG box can fix it so either send it to HTC for repair or have someone who knows JTAG fix it.
Try4Ce said:
Already tried, no luck. Tells me the device has not been found.
Click to expand...
Click to collapse
I saw this issue on my friend's GS3 once. It was hard bricked and there was no way to recover from what I read (at least on the GS3). I know I saw a thread somewhere here in this forum about the same issue and someone linked to a Sensation thread where there was a way to fix it but I'm not sure if it would apply to the One
Same problem - but the phone magically fixed itself!
I had the exact same problem with my HTC One as described in OP...
My alarm went off in the morning and I set off for work, my battery was low but I thought that I would just charge it when I got to work. I was playing a game (Dungelot) whilst waiting for my bus and was receiving pop up messages about low battery. When it got to 4% left I decided that I would finish the level then close the game down, but as I was just about to finish, the phone went blank...I assumed that I had naturally used up all the battery life and although peeved that I had probably lost my progress in the game, wasn't too bothered.
I got to work and plugged my phone in to charge on my computer. The computer wanted to search for QHSUSB_DLOAD drivers but I thought this must be what it does when my phone isn't switched on and it finds the device. I cancelled the search prompt and tried to switch my phone on...nothing happened.
I tried for the rest of the day, trying to force shut down the bricked phone by holding power in for 30 secs, trying to power into boot mode etc...everything! But the phone would not switch on and the only response I got from it was a little orange LED every now and again and the QHSUSB_DLOAD prompt.
After googling the prompt - I found myself here and REALLY began to sh*t my pants! I've only had the phone less than a month and felt I was tech-savvy enough to flash my phone with a new ROM (Android Revolution HD) to try and get rid of some of the bloatware. I had flashed a new ROM successfully a coupld of weeks before and everything had been fine up that point.
I went home depressed but throught i'd try to plug my phone into a proper mains charger rather than my work's old USB cable (that came with my previous HTC Desire Z) I was going to try a long night of searching the net to try and find a way where I could at least recover the photo's, Zoe's and vids of my new born son but had such a headache that I gave up and went for an early night.
I was woken unexpectedly the next morning by my phone alarm going off! I stopped the alarm and the home just went to Home screen as normal! I don't know how or why these events happened...whether it was the flashed ROM, the game I was playing, the battery running out before the phone could shut down properly, the old USB cable in my work not charging but detecting the device or a combination of all of those, but so far, the phone jumped back into life with the alarm after being charged in the mains all night!
Thought i'd share as it may just help someone else out there who encounters this!
Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
Also, its not unheard of. I've seen it happen a few times in these forums.
Sent from my HTC One using XDA Premium 4 mobile app
I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app
lampel said:
I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.
same here
Any idea how to fix it?
Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
Jtag or send it to HTC is the only way.
Sent from my HTC One using Tapatalk
My Solution
Had the same Problem.
My Solution was to Download "HTC One (M7) Toolkit" and force Fastboot.
Pushed Power and Volume Down until Screen was Flashing.
Took about 2 minutes and the Phone was rebooting.
I have no idea what was happening. I have no idea if this helps or works for others. But its worth trying.
Sorry for my bad english.
Try4Ce said:
Any advice on that?
Click to expand...
Click to collapse
CoryTallman said:
Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Click to expand...
Click to collapse
bkmenon said:
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.
Click to expand...
Click to collapse
Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
This is some kind of mode that is enabled when you hold power on button when the device battery is completely drained. i.e. when you try to turn device on it will not boot up (Special I was connected to usb cable via PC to charge my phone NEXUS 4 when I get into this mode). I saw a similar mode where nvflash commands are executed something like APX(can't recall correctly) with Tegra 4 device (that time also I was connected with a usb cable and charging the tablet when it was completely drained!). A simple solution to quit this issue is DO not Panic and let the device get a little charge. After that boot normally with the power button. In case if it didn't try other modes to enter such as recovery or fastboot reboot commands if your device is getting recognised..
QHSUSB DLOAD means its a hard bricked phone, No amount of messing about with it will fix it, Send it to a service centre, it will probable have to have the motherboard replaced..Sorry
My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..
danielr18 said:
My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..
Click to expand...
Click to collapse
What do you mean by "force"? What did you do exactly?
My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.
danielr18 said:
My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.
Click to expand...
Click to collapse
mine spent the night carrying on waking took the charger and the green light for continued access, tried to turn it on but could not. After reading your response, I tried to hold the power button for longer. After 15 seconds the phone rang and the light came on, everything works perfect so far
Today while I was updating firmware phone gone to QHSUSB_DLOAD mode.
I am guessing it's end of road. :crying:
Hiya, Remember this thread? http://forum.xda-developers.com/htc-one/help/htc-one-m7-stuck-boot-loop-t3028651/page1
Well, we got it working and everything. We used twrp to flash cyanogen mod snapshot (cm-11-20141112-SNAPSHOT-M12-m7.zip) and then flashed gapps right after (gapps-kk-20140606-signed). Everything went fine and the phone was stable. This morning we ended up putting in my friends SIM card. It worked for a moment and then the data stopped working. Stumped we made a call and found out the device was blocked. This deactivated my friends SIM. We do a IMEI Search on Swappa and the phone comes up as reported stolen. Well bummer. At least the phone still works. Well later in the day, my friend starts to use the phone generally on his WiFi and starts to have issues when he installed Facebook and tried to open it, the phone started to lag and he decided to reset the phone. It booted back up fine, then started to lag again. Something about Google now I think popped up and then the phone froze again. he restarted the phone. he got to the HTC logo and it froze. He restarted it again, and now it won't boot. I can say the battery was at about 15% when this did happen. I've had the phone connected to my portable charger all day. I am not sure what to do. I've tried the bright light trick and that didn't work. Any suggestions?
CloudHD said:
Hiya, Remember this thread? http://forum.xda-developers.com/htc-one/help/htc-one-m7-stuck-boot-loop-t3028651/page1
Well, we got it working and everything. We used twrp to flash cyanogen mod snapshot (cm-11-20141112-SNAPSHOT-M12-m7.zip) and then flashed gapps right after (gapps-kk-20140606-signed). Everything went fine and the phone was stable. This morning we ended up putting in my friends SIM card. It worked for a moment and then the data stopped working. Stumped we made a call and found out the device was blocked. This deactivated my friends SIM. We do a IMEI Search on Swappa and the phone comes up as reported stolen. Well bummer. At least the phone still works. Well later in the day, my friend starts to use the phone generally on his WiFi and starts to have issues when he installed Facebook and tried to open it, the phone started to lag and he decided to reset the phone. It booted back up fine, then started to lag again. Something about Google now I think popped up and then the phone froze again. he restarted the phone. he got to the HTC logo and it froze. He restarted it again, and now it won't boot. I can say the battery was at about 15% when this did happen. I've had the phone connected to my portable charger all day. I am not sure what to do. I've tried the bright light trick and that didn't work. Any suggestions?
Click to expand...
Click to collapse
If the phone is stolen do the right thing and hand it in to the police!I would say this is Karma
CloudHD said:
Hiya, Remember this thread? http://forum.xda-developers.com/htc-one/help/htc-one-m7-stuck-boot-loop-t3028651/page1
Well, we got it working and everything. We used twrp to flash cyanogen mod snapshot (cm-11-20141112-SNAPSHOT-M12-m7.zip) and then flashed gapps right after (gapps-kk-20140606-signed). Everything went fine and the phone was stable. This morning we ended up putting in my friends SIM card. It worked for a moment and then the data stopped working. Stumped we made a call and found out the device was blocked. This deactivated my friends SIM. We do a IMEI Search on Swappa and the phone comes up as reported stolen. Well bummer. At least the phone still works. Well later in the day, my friend starts to use the phone generally on his WiFi and starts to have issues when he installed Facebook and tried to open it, the phone started to lag and he decided to reset the phone. It booted back up fine, then started to lag again. Something about Google now I think popped up and then the phone froze again. he restarted the phone. he got to the HTC logo and it froze. He restarted it again, and now it won't boot. I can say the battery was at about 15% when this did happen. I've had the phone connected to my portable charger all day. I am not sure what to do. I've tried the bright light trick and that didn't work. Any suggestions?
Click to expand...
Click to collapse
As the guy says above, however if it is your phone, then get in touch with your network operator and ask them whats going on, the phone has been IMEI blocked by the network and theres nothing you can do to get it working again, you cant even flash a rom as during setup it checks IMEI, and will just reboot loop when it fails to register.
shepppster said:
If the phone is stolen do the right thing and hand it in to the police!I would say this is Karma
Click to expand...
Click to collapse
Seanie280672 said:
As the guy says above, however if it is your phone, then get in touch with your network operator and ask them whats going on, the phone has been IMEI blocked by the network and theres nothing you can do to get it working again, you cant even flash a rom as during setup it checks IMEI, and will just reboot loop when it fails to register.
Click to expand...
Click to collapse
I would turn it in to the police. You know, it's just the fact that this phone didn't come from somewhere local, it came from about 5 states away. On top of that, I was reading some articles and found out that sometimes the network will mark it as stolen and block the IMEI since the original owner did not pay their bill. I bought this phone from ebay. I still have to get my money back, and I need to give the seller a chance to respond, as maybe this is all a misunderstanding. I called the network. They couldn't look up the IMEI or anything for them to contact the original owner. I was told that to get it unblocked the owner of the phone would have to call and report it as not stolen. Also, seanie, are you saying due to the IMEI block, the phone is acting like it is?
CloudHD said:
I would turn it in to the police. You know, it's just the fact that this phone didn't come from somewhere local, it came from about 5 states away. On top of that, I was reading some articles and found out that sometimes the network will mark it as stolen and block the IMEI since the original owner did not pay their bill. I bought this phone from ebay. I still have to get my money back, and I need to give the seller a chance to respond, as maybe this is all a misunderstanding. I called the network. They couldn't look up the IMEI or anything for them to contact the original owner. I was told that to get it unblocked the owner of the phone would have to call and report it as not stolen. Also, seanie, are you saying due to the IMEI block, the phone is acting like it is?
Click to expand...
Click to collapse
The IMEI block would explain it not booting fully into a rom, but are you saying it not charging either ?
If you brought it from ebay I would file a case myself if it was me with paypal and explain what the fault was, paypal will just give you his address to send it too, send it registered post, as soon as it arrives and you have proof of that, paypal will give you your money back, the seller wont get a say in it, ive done it myself before where a seller has sold me faulty goods without me knowing.
Seanie280672 said:
The IMEI block would explain it not booting fully into a rom, but are you saying it not charging either ?
If you brought it from ebay I would file a case myself if it was me with paypal and explain what the fault was, paypal will just give you his address to send it too, send it registered post, as soon as it arrives and you have proof of that, paypal will give you your money back, the seller wont get a say in it, ive done it myself before where a seller has sold me faulty goods without me knowing.
Click to expand...
Click to collapse
Yes, it's not charging either. The reason I haven't gone to paypal yet is I want to give seller time to try and resolve the problem. My friend really wanted this phone. On top of that, WE FIXED THE PHONE! It was broken originally. If it does turn out to be the imei being the problem and the seller gets it back, gets the imei unblocked and it works, he can sell the phone for more. It may not be working now, but I don't feel it's fair for me to get what I bought it for back. That's why I am taking a different route.
CloudHD said:
Yes, it's not charging either. The reason I haven't gone to paypal yet is I want to give seller time to try and resolve the problem. My friend really wanted this phone. On top of that, WE FIXED THE PHONE! It was broken originally. If it does turn out to be the imei being the problem and the seller gets it back, gets the imei unblocked and it works, he can sell the phone for more. It may not be working now, but I don't feel it's fair for me to get what I bought it for back. That's why I am taking a different route.
Click to expand...
Click to collapse
the charging problem could be a few different possibilities, I would try the cheapest option first, the charger and the lead, failing that, you will have to think about things like the charging port or the battery itself, not an easy job being sealed units.
Seanie280672 said:
the charging problem could be a few different possibilities, I would try the cheapest option first, the charger and the lead, failing that, you will have to think about things like the charging port or the battery itself, not an easy job being sealed units.
Click to expand...
Click to collapse
Of course. I don't have any other micro-usb cables. I guess I'll have to wait till later. What I can say is that that I want to confirm the phone will not boot a custom rom if the imei is blocked? Also, I'll note this issue occured after I called ATT to ask them about the phone now that I think about it.
Hi all,
I was wondering if anyone is able to help me out with my HTC one M7. My phone has been out of commission since Monday night and I'm all out of options on what to do, I've even tried doing a factory reset as a last resort but that didn't seem to work as it looked like the process just stalled.
Here's a bit of background of what happened: Monday night I charged my phone through the wall outlet and went to have dinner, I came back to check on the phone and it was off. I thought that was odd so when I tried turning it back on I would only ever be able to get to the white HTC logo screen. I'm able to get into fastboot and recovery but after googling solutions and trying the options people have mentioned, it still isn't working. I'm not very tech oriented so I wouldn't know how to flash ROMs or anything like that...soooo, I'm hoping someone is able to explain steps in I'm able to understandr. I don't even know flashing ROMs is possible at this point since whenever I plug it into my PC, the drivers aren't recognized by Windows and says 'failed to install drivers'.
Any help is very much appreciated!! (I signed up to the forum in order to write this and seek help lol)
I haven't done ANY customization to the phone everything is all stock from my service provider so I'm really baffled at how this sudden fail could have happened. There was no OTA update either.
rina__anir said:
Hi all,
I was wondering if anyone is able to help me out with my HTC one M7. My phone has been out of commission since Monday night and I'm all out of options on what to do, I've even tried doing a factory reset as a last resort but that didn't seem to work as it looked like the process just stalled.
Here's a bit of background of what happened: Monday night I charged my phone through the wall outlet and went to have dinner, I came back to check on the phone and it was off. I thought that was odd so when I tried turning it back on I would only ever be able to get to the white HTC logo screen. I'm able to get into fastboot and recovery but after googling solutions and trying the options people have mentioned, it still isn't working. I'm not very tech oriented so I wouldn't know how to flash ROMs or anything like that...soooo, I'm hoping someone is able to explain steps in I'm able to understandr. I don't even know flashing ROMs is possible at this point since whenever I plug it into my PC, the drivers aren't recognized by Windows and says 'failed to install drivers'.
Any help is very much appreciated!! (I signed up to the forum in order to write this and seek help lol)
I haven't done ANY customization to the phone everything is all stock from my service provider so I'm really baffled at how this sudden fail could have happened. There was no OTA update either.
Click to expand...
Click to collapse
If your warranty is still valid take it to service
donkeykong1 said:
If your warranty is still valid take it to service
Click to expand...
Click to collapse
Unfortunately it's not, I've had the phone for a little over 2 years now. Seriously contemplating just using a loaner phone in the meantime while I wait for the new Nexus ...
rina__anir said:
Unfortunately it's not, I've had the phone for a little over 2 years now. Seriously contemplating just using a loaner phone in the meantime while I wait for the new Nexus ...
Click to expand...
Click to collapse
Did you try factory reset from bootloader?
donkeykong1 said:
Did you try factory reset from bootloader?
Click to expand...
Click to collapse
Yes, I did. It flashed to the screen with 2 green arrows in a circle and 1 downward green arrow with a progress bar at the bottom but nothing happens during this period. I left the phone like that for about 30 mins just to see if anything would happen and nothing did.
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!