Hi there my phones just been in for repair comes back fine and within a day headphone jack and call speaker decided to die on me. Basicaly i can only hear somoeone on the phone through loud speaker and the headphone jack just not registering headphones inserted.
I at first thought it was the rom ect. cyanogenmod 7 RC1 btw but i soon found out it wasnt .
I believe that i have to take it into for repair again but the problem is i cannot connect my phone to my pc to use the RUU. tried on a few computers as well. It just won't detect it i have tried putting htc sync on/off and all other drivers still no luck. I dowgraded it last time using the bootloader which worked but this time it doesnt.
could someone please help thankyou
You tried booting to Hboot and plugging in your USB there?
thanks for reply
yeah i have pal, h boot fast boot u name it,, i had this problem before i had it repaired first time, basically i came accross this by accident from previous downgradng put in my goldcard which had downgrade files, bootloaded it and funily enough it worked put me back onto stock. i get an error now saying it's too old or something, u have any links for other downgrade or any other ideas thankyou
all good
Well ive got it back to stock, basically i extracted the rom from the RUU, wiped phone, installed the rom from my goldccard using Bootloader ,, so send it in, still got my hardware issues but least my warranty isnt void ..
Related
Been routed for months and running Warm 2.2 and lou #4 with no problems.. Some how today my phone automatically went from s-off to s-on and now i cant get my sd card to mount or the phone to properly boot on without having the usb connected.. Anyone help please!! Hooking it up to the computer also wont read the sd card....
ancora76 said:
Been routed for months and running Warm 2.2 and lou #4 with no problems.. Some how today my phone automatically went from s-off to s-on and now i cant get my sd card to mount or the phone to properly boot on without having the usb connected.. Anyone help please!! Hooking it up to the computer also wont read the sd card....
Click to expand...
Click to collapse
Sounds like what happend to incubus...
any idea what he did to possibly fix the issue?
ancora76 said:
any idea what he did to possibly fix the issue?
Click to expand...
Click to collapse
Think he is exchanging his phone on insurance policy.
there has to be a way to go back to s off either with an emulator or something i hope...
ancora76 said:
there has to be a way to go back to s off either with an emulator or something i hope...
Click to expand...
Click to collapse
Probably not. If you cant get your SD card to mount, then you probably screwed.
damn, same problem!!
Yeah, i couldnt get s off because sd wouldnt mount to be able to flash anything, nor would ir mount with the pc to able to flash ruu or anything.
Spending $90
Let me know if you figure it out.
Did you guys do/change anything RIGHT before it happened? Just wondering so maybe we can avoid it happening to anyone else.
I did nothing other then do a nan backup...
ancora76 said:
Been routed for months and running Warm 2.2 and lou #4 with no problems.. Some how today my phone automatically went from s-off to s-on and now i cant get my sd card to mount or the phone to properly boot on without having the usb connected.. Anyone help please!! Hooking it up to the computer also wont read the sd card....
Click to expand...
Click to collapse
I've had this happen twice now, two diff. phones. sucks... I don't know what causes it, but you need to call Verizon and get a refurb. Make sure to pull the rom.zip from the most recent RUU file (from nov.) and rename it to PB31IMG.zip and you will be un-rooted and back to stock w/o repercussions of losing warranty.
also when not connected to power, does it do the vibrate three times then blinking green notification light until battery pull?
ACD168 said:
I've had this happen twice now, two diff. phones. sucks... I don't know what causes it, but you need to call Verizon and get a refurb. Make sure to pull the rom.zip from the most recent RUU file (from nov.) and rename it to PB31IMG.zip and you will be un-rooted and back to stock w/o repercussions of losing warranty.
Click to expand...
Click to collapse
but bootloader isnt reading anthing from sd card so i wouldnt be able to flash that
Thats exactly what happened to me on Sunday. I had to get a new phone. If you notice the adb drivers aren't working, or mine weren't. I was thinking it was just a bad usb port but why would it go back to s-on. Mine did exactly same thing.
nfiniti9 said:
Thats exactly what happened to me on Sunday. I had to get a new phone. If you notice the adb drivers aren't working, or mine weren't. I was thinking it was just a bad usb port but why would it go back to s-on. Mine did exactly same thing.
Click to expand...
Click to collapse
what rom were you using?
Well I was using reengineered and switched to magnolia. I unplugged the usb cable right before hitting reboot after flashing. It never booted up. I went through everything, even flashed back to RUU. When I went in to flash RUU I noticed I was s-on. I hadn't done anything that should do that. I was about to give up (already called verizon) when I plugged in the data cable, I had tried the power cable (i have 1 usb plugged into ac adapter and 1 into computer) but it didnt change anything. Soon as I plugged it into the data cable and powered the phone on, it booted up fine. I did managed to get it to reboot unplugging the usb cable while it was on. Once it just rebooted, once it went to the 5 vibrates/led flash error thing. Once I got it working it would work fine (except for usb/sdcard) until I plugged in the usb cable again. Would charge fine on ac though. I didn't notice the sdcard thing until later when I couldn't set any options in handcent. Somehow I just don't feel its just a bad usb port.
I still have my old phone, going to send it back tomorrow if you want to know anything.
nfiniti9 said:
Well I was using reengineered and switched to magnolia. I unplugged the usb cable right before hitting reboot after flashing. It never booted up. I went through everything, even flashed back to RUU. When I went in to flash RUU I noticed I was s-on. I hadn't done anything that should do that. I was about to give up (already called verizon) when I plugged in the data cable, I had tried the power cable (i have 1 usb plugged into ac adapter and 1 into computer) but it didnt change anything. Soon as I plugged it into the data cable and powered the phone on, it booted up fine. I did managed to get it to reboot unplugging the usb cable while it was on. Once it just rebooted, once it went to the 5 vibrates/led flash error thing. Once I got it working it would work fine (except for usb/sdcard) until I plugged in the usb cable again. Would charge fine on ac though. I didn't notice the sdcard thing until later when I couldn't set any options in handcent. Somehow I just don't feel its just a bad usb port.
I still have my old phone, going to send it back tomorrow if you want to know anything.
Click to expand...
Click to collapse
it's very strange that you have 5 vibrates, I've read everywhere and I seem to be the only one who have had this happen on two diff phones, getting 3 vibrates... it boots to the splash screen then instead of boot animation it vibrates 3 times, blank screen and green flashing notification light only remedy to pull the battery. I found that it would boot up only with usb or wall power, and I was able to take the ROM.zip from the nov. update RUU and rename it to PB31IMG.zip since it's signed and got me back to stock splash, recovery ect. and since I was turned to S-ON ( dunno how). weird.
My situation is the same with the 5 vibrate and then blinking light until i remove the battery. I cant get the phone to start up at all i keep going to recovery.
ACD168 said:
it's very strange that you have 5 vibrates, I've read everywhere and I seem to be the only one who have had this happen on two diff phones, getting 3 vibrates... it boots to the splash screen then instead of boot animation it vibrates 3 times, blank screen and green flashing notification light only remedy to pull the battery. I found that it would boot up only with usb or wall power, and I was able to take the ROM.zip from the nov. update RUU and rename it to PB31IMG.zip since it's signed and got me back to stock splash, recovery ect. and since I was turned to S-ON ( dunno how). weird.
Click to expand...
Click to collapse
ok, i was finally able to get stock android back on. So im getting somewhere at least.
I had to reformat my sd, rename my rom.zip to PB31IMG.zip and put it back on there. And now im at least back to stock. Now i gotta see if i can re root it.
its crazy that after getting the rom and recovery etc... back to stock, it still wants to vibrate 5 times if i unplug usb.
incubus26jc said:
its crazy that after getting the rom and recovery etc... back to stock, it still wants to vibrate 5 times if i unplug usb.
Click to expand...
Click to collapse
Trust me bro I feel your pain I had two phones do this, a blown speaker, one had the green noti light go out, first brand new one had the camera lens pushed in. even with all the problems I love the phone. just get it back to stock like you have, call 1800-922-0204, push 0, push 0, enter your account password and tell the rep whats up. get new phone. if you bought with amoled, thats what youll get. I should know Ive gone through 4 in the past week. I've brought back 2 boxes last week and I have 3 more to bring back tmw, at one point I had three incredibles sitting in my room. I have two batteries to send back too. man I can't wait to upgrade to the Thunderbolt. Every one of these refurbs it's something else. the last one with the green light blown out, that trackpad was PERFECT it hurts to loose that, this one is a little pushed in, but what can you do, not too mention the back door wasn't creaky at ALL, and on this on its sooooo looose. I just can't win. so this one needs cardboard behind the battery and its still not as good a fit as the last refurb... not too mention who knows if the cardboard isn't good?
Hi,
I was flashing a new CM7 theme on my 2 weeks old DZ (with CM7 RC 2 running fine) but the phone got stuck at the CM bootscreen. I tried rebooting multiple times by repeatedly pushing the power button and holding it. After a few failed attempts I pulled out the battery, and after putting the battery back in and trying to power it on the phone did nothing. No matter which buttons I pushed or held in.
I tried plugging it in to the power adapter, but the Power LED's don't even go on (neither the orange or the green one). The battery was at approx. 60% when I rebooted into recovery to install the theme zip, so there should be enough power left in the battery.
When I plug the DZ onto my PC (Windows 7 OS, with eclipse and Android SDK installed and working), the PC looks for a QHSUSB_DLOAD driver. I tried looking for the device through ADB but it doesn't see it.
Please help me guys, I've had the device for only two weeks now.
PS: I'm a noob
Oh dear, that doesn't sound promising. Good luck!! We feel for you.
Anyone knows what steps to undertake to maybe revive the phone. I don't think it's totally dead since it's somehow still being detected by my PC. I just can't find that so called QHSUSB_DLOAD driver.
If I can just somehow get it to connect to ADB then I might be able to get into Hboot or recovery.
Have you checked http://developer.android.com/sdk/win-usb.html ?
Perhaps, donno for sure, it could help you
HLeenders said:
Have you checked ***** ?
Perhaps, donno for sure, it could help you
Click to expand...
Click to collapse
I hadn't, but already had these drivers on my PC. And before it got bricked my DZ connected fine with the PC (I flashed it using ADB and had setup Hboot and recovery). My PC just can't seem to find any drivers for this so called QHSUSB_DLOAD. It doesn't matter wich folders I choose to look for drivers. Nothing is available through internet either.
im having the same problem ... i tried several times but no luck... no LED... but u shud try pulling off the battery then put it in then press volumeUP+power button ..it will vibrate and red LED will start blinking .. i dont knw wat is it .. i connected it to PC ....windows asked for qualcom MSM driver .... i dont knw wat to do ..nd how to get bootload loader bak :S
if it does this, send it back to HTC.
the eMMC chip has failed (an unfortunately reasonably common situation, happened to me twice so far)
They'll fix it regardless of what roms you had on it etc. (unless you've done some hardware mods) i sent it in with cyanogen mod and s-off, they fixed it anyway
hope this helps!
Lol, I thought my topic died.
Since you guys revived it, might as well tell you what happened. I contacted T-Mobile and sent the Desire Z in for repair and it got repaired for free since I'd only had for two weeks back then .
After I got it back I rooted it and restored a NAND backup and everything 's been working fine since then.
they repaired it or they replaced it ?
desirezbilal said:
they repaired it or they replaced it ?
Click to expand...
Click to collapse
They repaired it.
ok thats great
i have 1 stupid question, can you tell me did they open your phone or not
noboby solved this problem?
hello
basically i was on miui rom last week and the phone charger stopped working.
so now i have to turn the phone off to charge it
but when it is off and charging i can turn the phone on and it will continue charging
also my bluetooth stopped working (wont turn on)
i ran my ruu and the problems still remains. i have contacted htc via email and since the phone is only 2 months old im guessing they will replace it under warrenty.
but i want to fix it because it was rooted b4 and they might find out it rooted.
If you run your stock ruu then it is not rooted anymore.
but is there any other way of fixing the problems without sending it back because this is my only phone
Silly Question, but have you tried doing a factory reset as this often clears problems & is easily overlooked as a solution.
I think your phone is faulty, better to send it back to htc before the warranty runs out ^^
reaper7881 said:
hello
basically i was on miui rom last week and the phone charger stopped working.
so now i have to turn the phone off to charge it
but when it is off and charging i can turn the phone on and it will continue charging
also my bluetooth stopped working (wont turn on)
i ran my ruu and the problems still remains. i have contacted htc via email and since the phone is only 2 months old im guessing they will replace it under warrenty.
but i want to fix it because it was rooted b4 and they might find out it rooted.
Click to expand...
Click to collapse
You using latest radio?
Edit forget that, you back stock now, seen you switched to MUIU latest GB RoMs need lastest radio.
fixed it . it was jus a simple usb brick
cheers anyway peeps
I was running Leedroid on my Desire and all was fine.
I seen these Sense 2.1+3.0 ROMS and decided to give one a go.
I tried to get into recovery before doing anything to take a NAND Backup, but it just refused to go into recovery. I finally got it in there and tried to apply to update.zip but it kept saying something could not be found, I forgot what, and failed after 10 tries.
I booted mu phone up and I'd lost all my data. It's like the phone had been wiped.
I tried reseating the SD Card and checking it was all ok, but then I got stuck in a bootloop. In the mean time, my Alienware Laptop decided to die, followed by my backup Dell laptop! lol
I messed around for ages trying to get various things to work, but couldn't do it. In the end, I downloaded the old root method and flashed Cyanomod 7 which seemed to work and I got it booted, but I couldn't mount the SD card and it would rarely pick up that the USB was connected.
I then flashed AceSMod007 which also seemed to go well minus 2 things.
The first, Text messages seem to show my contacts picture, but also it only shows their Number rather than the contact name. This is VERY annoying and I can't find a way to resolve it.
The second issue, and possibly the most worrying is that it won't pick up USB connection AT ALL. This includes when it's plugged into the Wall to charge.
I tried the USB Brick fix, but that didn't work at all.
I shutdown the phone, removed the battery, plugged in the charger, inserted the battery and booted up the phone and it started charging, but as soon as I unplugged the charger and put it in again, same problem.
I'm currently trying another ROM to see if that resolves the issue, but I suspect that it won't tbh.
Has anyone came across this before and/or knows how to fix it?
Other things I've tried:
Wiping all data, cache and Battery data.
Using different USB cables
Thanks
UPDATE:
Flashing a different ROM didn't seem to resolve it.
Quick update.
I flashed Insertcoin rom onto the phone and it's resolved my text message issue.
Also, when I plugged the phone into the PC, it didn't give me any options for mount SD or anything like that, but said it was charging. However, an hour later and the battery had only gone down.
Since charging by USB has always been slow for me, I plugged in into the wall socket for an hour but it wouldn't pick up that I'd plugged it in. I turned the phone off and I got the LED to say it's charging.
Left it, then booted it up and still has the same battery level.
I don't expect it's the battery otherwise it would pick up fine when plugging into the PC.
Could be an usb brick:
http://forum.xda-developers.com/showthread.php?t=691639
Cheers mate, but as I mentioned, I've tried the USB Brick fix a couple of times and still experiencing the same issues.
Can you switch on blue tooth? Does it stay on?
Sent from my HTC Desire using XDA Premium App
Actually, no. Its says Turning On... Then just goes back to off.
you DO have USB-Brick
you gotta fix it
if S-OFF do:
fastboot oem enable qxdm 0
fastboot oem eraseconfig
if S-ON there are a few threads on xda on how-to do it, if you still get no USB-connectivity you just didnt do it right
good luck
Ah, I did try it a few times. I'll just keep trying then.
Cheers
Are you S-Off or S-On and are you still ROOTED?
This thread for USB Brick
See for my post here
if you are S-off or tried to flash a RUU and lost ROOT!
This thread has a flasher with built in USB Brick fix
I'd already followed the USB Brick guide and it didn't help.
Now, is I were to have missed the step that says to run '/data/flash_image misc /data/mtd0.img', I'd be a bit of a tit.
So let's just say that I tried the guide again and now I have full USB functionality back
I was going to S-OFF my phone, but I'll hopefully get a Sensation soon and I don't want to fubar anything in the mean time.
Thanks for the help and pointers though guys. It's nice to be a member of some forums that aren't full of people who want to cry at you for not understanding everything 100%.
Cheers again
just use the thanks button
glad we (or at least I) could help.
Hi, good day, I have a big problem since I'm a loser,so I managed a couple of idiocy.Normally my work cell phone, then I installed the wrong rom, I corrected it using the RUU, but then I dropped the phone in the tub: D and unfortunately I soon turned on and since then my phone booted into the bootloader, the cell phone does not respond using Power etc. Note that they don't work for me for a long time the buttons for the sound. Please help necessary Now I'm trying to give the RUU program me, but reports that the mobile phone is not connected via USB and when I turn to the bootloader, so it reports an error that I don't have a cell phone and it is packed with nabíjim all day and is charged. Please help
Wosatko said:
Hi, good day, I have a big problem since I'm a loser,so I managed a couple of idiocy.Normally my work cell phone, then I installed the wrong rom, I corrected it using the RUU, but then I dropped the phone in the tub: D and unfortunately I soon turned on and since then my phone booted into the bootloader, the cell phone does not respond using Power etc. Note that they don't work for me for a long time the buttons for the sound. Please help necessary Now I'm trying to give the RUU program me, but reports that the mobile phone is not connected via USB and when I turn to the bootloader, so it reports an error that I don't have a cell phone and it is packed with nabíjim all day and is charged. Please help
Click to expand...
Click to collapse
The USB plug must have been affected, or the motherboard. I don't know what else you could do except start replacing phone parts, or getting a new phone.