Related
Well today I tried to just do the IPL and SPL flash from the tmobile rom. Apparently, thats a bad thing. Thank god for Warranty. Bricked it almost instantly. That will be the last time I try that.
Nope -- sorry. Warranty won't cover bricking/flashing your phone with anything other than an official ROM.
Your best bet is to try to get it back into bootloader and reflash. If that can't be done, you've acquired a really expensive paperweight.
nottoosmart said:
Well today I tried to just do the IPL and SPL flash from the tmobile rom. Apparently, thats a bad thing. Thank god for Warranty. Bricked it almost instantly. That will be the last time I try that.
Click to expand...
Click to collapse
Define "brick". You aren't saying what it does or doesn't do (ie: what exactly happened to make you say its bricked). You also haven't said if its CID unlocked (I assume it is since your sig seems to indicate you were running WM6). You also aren't saying if this is a G3 or G4 device (the IPL/SPL you list in your sig would indicate G3, but you have to be sure of that).
Try turning the phone off (if it still powers on and off. Or remove the battery if you can't get it to turn off, then put the battery back in once its off). Then plug in the USB cable, press and hold the camera button, then press the power button to turn it on (with the camera button still pressed). If you get the rainbow screen with the USB indicator in the lower left, you can then try using that to downgrade to a 2.x ROM (T-Mobile 2.26 shipping one is good) or all the way back down to the Button 1.05 ROM.
Provide more details and one of the gurus may be able to assist. And details of exactly what you did to get to the point you are at would be very helpful too (either to assist you, or to help others learn not to do whatever it is that you did if it is truly "bricked").
It will not turn on. It is a hardware issue. And according to HTC within the warranty, the only issue they will not cover is any physical damage caused to phone. I had it boot to os then it just turned off. Never to turn back on again.
Basically I extracted the IPL/SPL from the TMobile 2.26 os. Tried just flashing those but I dont think i set them correctly in the nk file. As for power, It gets none. So i cant even get it to turn on.
Its a G3 fully unlocked. Ive been working on writing my own version of WM6. I might wait now after this little deal.
Well, after getting my replacement today, I tried to power it up and it wouldnt. Took the new phone and battery to Service center. Apparently what happened is that the battery shorted out and killed the phone. Battery was covered under accessories warranty. So hopefully tomorrow i will be up and running.
OH MY GOD I WAS TRYING TO GET MY PHONE BACK TO FACTORY DEFAULD AND IT WENT TO SWITCH THE PHONE INTO BOOTLOADER AND IT SAID IT WAS A COMMUNICATIONS ERROR AND THE 8125 NEVER CAME BACK ON , THE CHARGER LIGHT DOESNT COME ON IF I PLUG IT IN TO THE WALL CHARGER, BUT IF I TAKE THE BATTERY OUT THE SCREEN WILL GO WHITE FOR A SHORT SECOND AND THE CHARGER LIGHT WILL FLICKER
DO YOU THINK ATT WILL TAKE IT BACK I HAD IT 6 DAYS AND IT WAS HARD SPL 2
Srry for my bad english
You should have a 30 day warranty on the device from store you purchased it from. If not, just contact HTC support if the device will not boot.
so just make up some excuse to send it to att
Be careful when trying to lie to AT&T or T-Mobile. If your device is CID unlocked then your warranty is void. They may not realize this at first but once they dis-assemble the device for refurbishment they will and they may be able to trace it back to you so just be really careful.
can you get into bootloader mode?
are you sure the battery was charged enuff to reboot again?
try changing the battery if you have another fully charged one adn try to get into bootloader ode if you can then youre fine dude
dharvey4651 said:
Be careful when trying to lie to AT&T or T-Mobile. If your device is CID unlocked then your warranty is void. They may not realize this at first but once they dis-assemble the device for refurbishment they will and they may be able to trace it back to you so just be really careful.
Click to expand...
Click to collapse
Don't try to scare of people!
I exchanged my MDA three times no problem for CID unlocked half years ago! it will not void your warranty!
cgigate said:
Don't try to scare of people!
I exchanged my MDA three times no problem for CID unlocked half years ago! it will not void your warranty!
Click to expand...
Click to collapse
A friend of mine screwed up a G4 8125 he had (I tried to warn him about not flashing anything he found) after he had CID unlocked and flashed some rom from another website (it wasn't from here). He sent the phone in to Cingular telling them that the phone had quit working. They sent him a replacement with no questions asked. About 1 month later he received his old phone back with a letter stating his warranty had been voided due to software upgrades they had found he had done, and he had a charge on his next bill for $399 for the replacement phone they had sent him. He fought Cingular for a couple of months over it, but they held firm to what they had found had been done, and last I knew he finally just paid the bill (over time).
So, I'm glad you were able to do exchanges with T-Mobile, but I know first hand someone that got burned trying to do this, and Cingular did know what had been done. Its not an urban legend, or a story just to scare people. Using tools here will void your warranty. I think in most cases the carriers will not determine this (Like yourself, another friend of mine that I put Crossbow Unloaded on his phone, had issues, and Cingular replaced it with no issues), but it does happen...
mfrazzz said:
A friend of mine screwed up a G4 8125 he had (I tried to warn him about not flashing anything he found) after he had CID unlocked and flashed some rom from another website (it wasn't from here). He sent the phone in to Cingular telling them that the phone had quit working. They sent him a replacement with no questions asked. About 1 month later he received his old phone back with a letter stating his warranty had been voided due to software upgrades they had found he had done, and he had a charge on his next bill for $399 for the replacement phone they had sent him. He fought Cingular for a couple of months over it, but they held firm to what they had found had been done, and last I knew he finally just paid the bill (over time).
So, I'm glad you were able to do exchanges with T-Mobile, but I know first hand someone that got burned trying to do this, and Cingular did know what had been done. Its not an urban legend, or a story just to scare people. Using tools here will void your warranty. I think in most cases the carriers will not determine this (Like yourself, another friend of mine that I put Crossbow Unloaded on his phone, had issues, and Cingular replaced it with no issues), but it does happen...
Click to expand...
Click to collapse
Thank you.
I do not lie to people or try to scare them... I am merely looking out for people. Fortunately when I received my handset exchange, I had a G4 that was not CID unlocked and I just put the original firmware back on it before sending it in since it was hardware reasons that I sent it back.
now im scared and dont know what to do the battery was fully charged
i was trying to frlash the original rom and the phone bombed when it went to bootloader,
No need to be scared. I was just looking out for your wallet.
Are you using Vista? Vista cannot talk to your device in bootloader mode.
Also, I highly doubt your device is really bricked. It takes something really stupid to brick your device. Unless you flashed a G3 IPL/SPL to a G4 device or vice versa, your device cannot be permanently bricked. There's got to be a way to fix it.
List all information about your device... service provider, model of phone, IPL/SPL, Whether you think it is a G3 or G4, and a history of everything you did to your phone since you started messing with it.
Hopefully with all of that information, we can figure out what you did wrong to cause this and hopefully find a solution.
Try to get back into boot loader.
Pull the battery out, then put it back in
Hold camera button and press the power button.
It should take you to a rainbow screen (bootloader mode)
If it does, then you are ok. No harm no foul...
Then try and reflash the latest Cingular 2.25 release available from HTC's website
If it does not turn on, then you probably toasted the battery or the mainboard. HTC has a long warranty on hardware issues. They dont cover the battery, but AT&T will, if the phone replacement does not get your phone back up. This is what happened to me. All you have to do is tell them you plugged the phone into charge (which you were doing without even knowing it) and then the phone went dead, never too boot again.
Thats exactly what I told them, with my CID unlocked G3. They replaced and I was all good.
Everyone has a diffrent tale to tell so take the advice as just that. Someone elses experience. Hope this helps.
Its a 8125 g4 the hard spl cingular not sim unlocked the phone's light flickers when i take the battery out i purchased the refurb one and i was reading att's website it said somethin about they will charge you the online price well its only 80 bucks just in case
i knew i shouldve traded with my neice for her G3 , I ordered three 1 g4 and 2 g3's
i Was going to tell them exactly that but i wanted to check here because u guys r smart by the way i charged it this morn and went to flash it back to factory and it bombed do you think the battery is dead
Ok, so enough with the horror stories (my intent wasn't to scare you, but just make it clear, I have seen AT&T back charge someone, so you (and others) can understand the risks)...
Now, lets see if we can recover this device for this guy...
First thing first. Pull the battery out of the phone and leave it out for an hour (or more).
Next - Pull your SIM card out. Make sure the contacts are clean on the card. Put the SIM card back in and make sure its seated well.
Now, put the battery back in. Try to turn on the phone (I doubt it works, yet, but lets give it a shot). If by chance the phone does turn on (most likely to the bootloader mode, then hook up the USB cable and try flashing the Official rom for this device.
If it doesn't turn on (what I expect), then pull the battery again and leave it out for 15 mins. While the battery is out, try to turn on the phone once. This is just to discharge any charge that may be in the device.
After 15 mins, put the battery back in and DO NOT TRY TO TURN IT ON. Now, get your AC wall charger for your phone, and plug your phone in. Again, do NOT try to turn it on yet, just plug it in. Let it stay hooked up to the wall charger for 1 hour without doing anything else to the phone. I'm hoping that at some point during this time, the battery charge light may come on. If the light does come on then let it charge up.
If the charge light still doesn't come on, then leave it plugged in and try to turn on the phone. I'm hoping by this time it will work. If it doesn't then you may have to do a search on these forums for JTAG and look at the hardware option of getting your phone back (I've never done a JTAG operation so I can't help you with it. In the Wizard forum there were discussions of this last winter / spring where someone rescued their bricked phone.
Hope this helps...
just waitin and hopes this works if it does how can i repay you? Free computer software (not Warez) a legit purchased program
the-equinoxe said:
Usage:
-connect your device
-Start hard_SPL-G4.exe
-Push the "Check DOC" button
-> The tool now checks whether your device is truly a G4, if not, it will give you an error and stops.
-> after this a dos box pops up, and it loads the softSPL to your device, to enable hard-SPL flashing.
-> then a Rom Update Utility will start, ONLY proceed if your screen is white!
-Proceed with the upgrade, it will only take a minute.
After reboot the IPL version is : 2.21.0001 and the SPL is 2.21.olip
Now you have Hard SPL
You can flash the ROMs with the RUU in the ROM package, should you have trouble with upgrading, try Mun's RUU (thanks for the tip Boto).
So no need to downgrade before upgrade anymore.
But don't flash ROMs containing IPL/SPL.
_____________________________________________________________________
As I have mentioned before in this post:
You shouldn't try to update ROM's with IPL/SPL after HARD SPL.
BUT: If you want to update IPL/SPL for G4 after hard SPL, do as following:
-disassemble ROM with IPL/SPL of your liking
Usage: typho5.exe -x nk.nbf
-reassemble the ROM or IPL/SPL with NKnbftool.
Make shure you only use G4 IPL/SPL for your G4, those are the IPL_2 and SPL_2 files created by typho5.exe.
-copy the nk.nbf you just created to SOFT SPL Folder
-start Soft SPL and flash the IPL/SPL.
You will lose the hardSPL though!
Typho5.exe and nknbftool are available in most kitchens.
Click to expand...
Click to collapse
I already did most of the work for you. Linked below is the Official AT&T IPL/SPL 2.25.0001 in nk.nbf format with SoftSPL. Just download from the megaupload link below and use SoftSPL to flash the new IPL/SPL. This will remove HardSPL and you should be able to restore the AT&T Official Rom.
REMOVE HardSPL
EDIT:: I know this is not much help to you now, but should you be able to get your device to turn back on, this is what you're going to need to do.
look man I had experienced a problem if it is like yours I can tell you what I did to solve it?
I had a problem in I-mate jamin G3 after upgrading with a wrong rom It doesn't work
If i connect the device to the charger it lights with the 3 color screen
but if i connect it to the usb it flicker with no connection to activesync.
I went to the service center and they told me I have to replace the mainboard
this meant that about 400 $ in my country.
I searched this forum until I found a thread guided me to resolve my problem without changing my device's board.
abc12345 said:
OH MY GOD I WAS TRYING TO GET MY PHONE BACK TO FACTORY DEFAULD AND IT WENT TO SWITCH THE PHONE INTO BOOTLOADER AND IT SAID IT WAS A COMMUNICATIONS ERROR AND THE 8125 NEVER CAME BACK ON , THE CHARGER LIGHT DOESNT COME ON IF I PLUG IT IN TO THE WALL CHARGER, BUT IF I TAKE THE BATTERY OUT THE SCREEN WILL GO WHITE FOR A SHORT SECOND AND THE CHARGER LIGHT WILL FLICKER
DO YOU THINK ATT WILL TAKE IT BACK I HAD IT 6 DAYS AND IT WAS HARD SPL 2
Srry for my bad english
Click to expand...
Click to collapse
I read somewhere on this forum that if you want to flash in bootloader mode, you have to switch off USB connection in ActiveSync, go into bootloader mode and then connect the phone to the PC. After that flash your original ROM.
I also had an issue that my wizard battery would not charge. I used an third party USB wall charger, that wasn't good enough... I had to use the HTC wall charger to recharge the battery, it has a little more power.
got a tmobile mda, i think i bricked my phone, it doesnt even turn on to boot screen or the 3 color screen after i pushed those 3 buttons..what should i do? thx in advance
Most of time is the battery problem. Try to find another battery and see what happen..
dunno, but i was flaashing my phone before that, it didnt die for no reason, i think i flash it a wrong rom or something, do u think i bricked my phone/?
Its hard to say.What rom did u used?? What PDA do u have?? Did u flashed it with battery on 50% or less?? Try to get in bootloader mode.
3-buttons? To get into the 3-color bootloader screen should only take 2 buttons. Press and hold camera button. Then use stylus and press then release RESET button. Bootloader screen should show up after 3-5 seconds, then release the camera button.
GnatGoSplat said:
3-buttons? To get into the 3-color bootloader screen should only take 2 buttons. Press and hold camera button. Then use stylus and press then release RESET button. Bootloader screen should show up after 3-5 seconds, then release the camera button.
Click to expand...
Click to collapse
tried that few times, but doesnt boot up, but i dont its the battery, do u guys think its the hardware after i flashed it.
If you are absolutely certain it's not the battery, then it's possible it could be bricked for good.
However, if you had it in bootloader mode very long, a dead battery is very likely. The phone won't charge in bootloader mode. I don't think it'll charge with a bad OS flash either.
Someone once claimed he connected a battery directly to a USB port to charge it. You could always give that a shot.
Probably most importantly is which ROM did you use? Is your phone a G3 or G4? If it's a G3 ROM with IPL/SPL in it, then yes you will permanently brick a G4 phone with that. If it's just an OS by itself without IPL/SPL, it's almost impossible to permanently brick it.
If it's permanently bricked, I think the only shot you have is to reflash it with a JTAG which would involve disassembling the phone.
i flashed my phone many times before and tried many roms and they all worked fine, i have g4 phone by the way, cuz i can read chinese so went and downloaded and rom called english asian rom so hope i could read chineses on my phone, then while i was fllashing it i found that that it wasnt wm6 it was made in 2006, but was too late, after it was done flashing it, the isp nubmer was different from lsp version, for ex:isp says 2.26.xx then lsp says (2.21.xx i with "i" at the end) so i reflashed it back using love rom to wm5 but it doesnt boot up the screen stays at 3 color so i removed the battery see if it can reboot normally then it doesnt turn on ever...
by the way waths jtag can u post a link for me in the forum or its a website, do i have to pay anything?
Hmmm, strange, wizard_love should be okay for the G4. I think if I were you I would try charging the battery (or buy an inexpensive external battery charger) before worrying about JTAG. I don't know if anyone has found JTAG or SPI (similar to JTAG but fewer pins) on the Wizard, but I can tell you that using it is not for the faint hearted!
Here is how JTAG is done on an iPAQ:
http://openwince.sourceforge.net/jtag/iPAQ-3600/
It's a lot of work just to connect the JTAG, and if the JTAG points have never been documented, it's even more difficult (almost impossible) to find them yourself.
lol, it looks so complicated. well any way i think i bricked it, sigh what can i do without it....plz help if u had the same problem that im having, really want my mda back. ty for ur helps GnatGoSplat
GnatGoSplat said:
Hmmm, strange, wizard_love should be okay for the G4. I think if I were you I would try charging the battery (or buy an inexpensive external battery charger) before worrying about JTAG. I don't know if anyone has found JTAG or SPI (similar to JTAG but fewer pins) on the Wizard, but I can tell you that using it is not for the faint hearted!
Here is how JTAG is done on an iPAQ:
http://openwince.sourceforge.net/jtag/iPAQ-3600/
It's a lot of work just to connect the JTAG, and if the JTAG points have never been documented, it's even more difficult (almost impossible) to find them yourself.
Click to expand...
Click to collapse
If i buy a new battery and it worked, but the rom already changed my SPL number but not IPL version do u think i can still flash it back to normal rom by using love rom wizard
I think you will need a G4 ROM with IPL and SPL in it to get it completely back to normal since it sounds like maybe that Chinese ROM changed one of those. That is assuming when you said "ISP" you meant either IPL or SPL? Usually the OEM ROMs are best for that.
But after the very last flash you performed, you did see the 3-color screen? That would indicate the bootloader was still working. Maybe it's really bricked, but I would think if the only thing you did to completely kill it off was remove the battery, then it must just be a dead or weak battery.
GnatGoSplat said:
I think you will need a G4 ROM with IPL and SPL in it to get it completely back to normal since it sounds like maybe that Chinese ROM changed one of those. That is assuming when you said "ISP" you meant either IPL or SPL? Usually the OEM ROMs are best for that.
But after the very last flash you performed, you did see the 3-color screen? That would indicate the bootloader was still working. Maybe it's really bricked, but I would think if the only thing you did to completely kill it off was remove the battery, then it must just be a dead or weak battery.
Click to expand...
Click to collapse
yeah i the 3 color screen was there after last flash, with different either ips or spl version differ from each other, then i didnt no what to do so i took the battery out and plugged it back in then it wouldnt turn on.. but battery was fully charged when i last flahed it..
After the last flash but before the 3-color screen, did it do a full reboot showing splash screen, etc?
Did you try a hard reset (top 2 buttons, then reset)?
after i flashed it, it stays on that 3 color screen(that was love rom) and doesnt boot up or anything so i didnt no how to do a hard reset back then so i just took the battery out insted of reset it, oh actually i tried soft reset and it doesnt turn off so then i took the battery out
-also after i flashed to that chinese rom i figured something was wrong so i falshed back using love rom right after cuz it wasnt going to boot, but love rom didnt seem to work, stays at 3 color screen
heres what i did : ran love rom-->flashed chinese rom-->didnt boot-->ran love rom-->doesnt boot-->tried soft reset-->took the battery out--> doesnt charge or on.
Tried connecting my kaiser to 2 different pc's and it won't get detected. The device will charge but activesync won't pick it up. Also its not listed in device manager! I tried disabling/renabling advanced network functionality as well has soft reset the device several times. I'm on the verge of hard reseting BUT when i put my device in bootloader mode it only says serial.. will not say USB as its supposed to
any help would be appreciated.. i'm on death v4 rom btw.
thanks in advance!
fone_fanatic said:
The device will charge but activesync won't pick it up.
Click to expand...
Click to collapse
Can you get an activesync connection via Bluetooth? When you inspect the extUSB connection can you see anything which looks wrong (such as a wire sticking out/in more than the others? What happened preceding this problem?
If you hard reset the device I don't see the relevance of the bootloader. It'll just restore the original image from where it's tucked away in the devices ROM. If it was working fine straight after you installed the ROM thats on it now and doesn't work after a hard restore then that points towards a hardware failure. If you have to go down the path of restoring to a different (original) ROM for returning purposes, there are ways of doing this with a microSD card - although I've not tried. I think the wiki would help there.
bluetooth activesync is working, i did a hard reset and nothing. Flashed to romeos via microsd and now its acting all strange.
After it completed the flash from microsd, i soft reset the device and it rebooted backinto bootloader.. i removed the microsd and soft reset several times and it kept going to bootloader. I attempted to hard reset as well and same thing, would go to bootloader. Removed the battery for a couple minutes and still same thing. Plugged it into USB with it off and it turn on by itself and go straight to bootloader. Unplugged the USB cable, took out the battery and put it back in, then plug the USB cable back in and this time the orange light came on as if charging and it finally booted up. The above has happened to me previously on my hermes but that was when the battery was extremely low, my battery level is currently at 97%!
now its booted into the freshly flashed rom and still same thing... charging but not being recognized by the PC... i've checked the usb port on the device and everything looks fine.
I'm lost at what to do now....
This might be a stupid reply but I had the same problem. My cable was busted so you could try another cable.
I am in the same situation here
Tried it with 3 different PCs with 3 different cables.
It's charging, Active sync pickes it up and trying to connect but fails to connect.
The only think I can come up with, I used new charger in the car. May be it killed the port
Is there any way to find out for sure?
i tried 2 cables with 2 different pcs... its only charging it and the computer won't detect the device at all. Nothing under usb in device manager.. even in bootloader, it only says serial not usb. I've downgraded to a shipped AT&T rom and Radio through the storage card but i still need to downgrade the SPL before i attempt to get a warranty exchange. IS that possible to do with through microsd yet?
I'm having the same issue. The usb port charges the phone fine with the USB cable, but teh computer does not detect the device. I also tried the headphones and they work fine as well. Help!
Update: I just tried a different usb cable, and now the computer recognizes the device, but as an unknown device.!!!!!
fone_fanatic said:
bluetooth activesync is working, i did a hard reset and nothing. Flashed to romeos via microsd and now its acting all strange.
After it completed the flash from microsd, i soft reset the device and it rebooted backinto bootloader.. i removed the microsd and soft reset several times and it kept going to bootloader. I attempted to hard reset as well and same thing, would go to bootloader. Removed the battery for a couple minutes and still same thing. Plugged it into USB with it off and it turn on by itself and go straight to bootloader. Unplugged the USB cable, took out the battery and put it back in, then plug the USB cable back in and this time the orange light came on as if charging and it finally booted up. The above has happened to me previously on my hermes but that was when the battery was extremely low, my battery level is currently at 97%!
now its booted into the freshly flashed rom and still same thing... charging but not being recognized by the PC... i've checked the usb port on the device and everything looks fine.
I'm lost at what to do now....
Click to expand...
Click to collapse
Have you tried these steps?
http://www.microsoft.com/windowsmobile/en-us/help/synchronize/activesync-usb.mspx
ajay6780 said:
Have you tried these steps?
http://www.microsoft.com/windowsmobile/en-us/help/synchronize/activesync-usb.mspx
Click to expand...
Click to collapse
Thanks for that suggestion but still no dice
The computer isn't detecting the device at all! Usually when a usb device is plugged in you can go to device manager and look under USB and see it there, but its not showing up. I've scanned for hardware changes several times and nothing.
I've now tried on 3 different computers (2 pc's and 1 mac) with 2 different USB-MiniUSB cables and nothing!!
i guess i'll just go to the at&t device support center tomorrow and hope they'll replace it on the spot and notice that i've changed the SPL...
can i ask for the people that are having this problem to do the following.
With your device unplugged from the PC open device manager. (Right click My Computer -> Properties -> Hardware (3rd tab) -> Device manager) Then expand the last tab (Universal Serial Bus Controller) and plug in your device.. if it doesn't show up then click actions -> scan for hardware changes..
I just want to make sure if your computer is detecting your device or not..
just an update with my situation. i went into the att device service center today and told them my problem... the guy behind the counter had no clue what he was doing. he just looked at it like a monkey for minutes then swapped it out for a new one. no questions asked even though it was hard spl'd, cid unlocked, and sim unlocked.
but now this device's vibration is really weak and i lost my invsishield protection on the front (kept the battery cover and my ppctechs scren protector)
Busted? or just won't work
Hi all,
I have been coming to these forums for a little while and only posted a couple of times. I felt this was important. I was having the same problem. Tried the cables, resets, ROM changes the works. I have had my at&t tilt htc 8925 for 36 days when I reported the problem to them. But it actually started about 10 days before. At&t tech support was very rude and accusatory when it came to them "helping" me. I, like probably all owners of a phone like this treat it like gold. It is very important to me. So when I contacted tech support and was told it was probably abuse or I had "buyers remorse" (I don't want to return the phone I just want it fixed!?)
The best they can do and they do not budge on this is for me to return the phone for an exchange. BUT, and this is a BIG AT&T but, the phone they exchange it with is refurbished. Something someone has returned. I do not want a phone that has been returned. I want mine fixed. "This is my phone, there are many like it but this one is mine" Know what I mean? When I bought the phone the guarantee was "we'll just replace it with a new phone" and I like 1000's of others did not ask if that "new phone" was refurbished. It is. Now advocates will tell you as they did me, refurbished is actually BETTER than new. Huh? Then why aren't all phones sold refurbished ones? And if they are so great, take mine back, give me one of those "crappy" new phones and give mine to someone who wants a sweet refurb. I am outraged by the whole mess.
I have searched forums and complaint sites. The bad usb port problem is NOT an isolated incident. There are a lot of people with the same "it charges but won't sync" problem. This is a known problem they refuse to address. Their stand, send in for refurb.
Personally I would like to see a recall fix class action against at&t. It can be fixed but they just don't want too. I thought I would be relatively safe buying for a huge company. They spend millions on advertising to simply leave their customers twisting in the wind after 30 days. Very bad business.
That's the rant. So I decided that if the warranty was useless anyway I'd take a shot at it myself before sending out for repair myself. There is a place in California PPC Tech http://www.pocketpctechs.com/main.asp?area=home that will fix the usb for $79 and ship it back to you in a few days. They seem to be reputable and a lot of people are opting to fix this problem themselves.
How did I fix mine? by altering the mini usb end of the sync cable. I tried other cables and connectors but I think it has something to do with the contact points. The only way mine would work was if I plugged it in, wiggled it slowly and with a little bit of pressure at times, around until the screen brightens. That means it has made a connection, then don't move. Hold very still. It took both my hands. Wait for what seems like 2 mins and it would start to sync. Based on this. my repair (before I send it to California for repair, which I may end up doing anyway) is make sure the plug on the phone is straight and not damaged. If you can get the phone to sync this way you may be able to crimp the mini end of the usb very very slightly to make the connection you are manually doing by wiggling it around. It took a lot of small tweaking but it now syncs about 29 out of 30 times. That's about as good as it gets.
So good luck to us all. If you can't get it to work yourself send it out west to PPC Tech. In this economy the phone companies like at&t better start getting their customer service back on track before they have no customers to service, It has happened to the biggest before. Wake up AT&T! The days of the business model of massive turnover and new signups is coming to an end as people tighten their belts. Treating current and future users poorly is a sure fire way to put yourself out of business.
here is my gift to you all..
http://forum.xda-developers.com/showthread.php?t=362679
read this post and check EVERY SINGLE LINK in the first post...i had this issue and i ended bending my usb plug every which way until finally i broke the plastic seperator off and in turn smashing the second pin from the left on the top off (the one in charge of activesync) over and over until it broke...i didnt really care i could still flash by sd but then i smashed the + power pin and so i was on the phone with att for many many hours explaining to them that its a known issue to users but not to the company and they finally sent me a replacement..i should have just searched my butt off before trying to deal with a problem/fox it myself (yes i dissasembled it and soldered the pin back on and it broke off multiple times causing me to dissasemble it many many times and smashing it again and i ended up getting alcohol on the water damage void pad which i replaced) learn from me...if you ever have ANY problems that are significant..dont try fixing JUST GET A REPLACEMENT...who cares if its a refurb..if the refurb sucks then send it back until they send you a new kit...after 5 returns you get a new kit soo just keep sendin back them refurbs until your happy
oh and to make it easy on yourself because if you tell att you have a usb problem its NOT covered under warranty and will take you many many hours like me to convince them otherwise (which someone eventually will understand because certain people ARE familiar with this problem at ATT it just depends who you get and how many times youve been elevated in support)..what you need to do is IF YOU CAN return your spl back to stock (if you manage to get a long enough connection with activesync) but if not dont worry too much att doesnt really check spl just that you have the shipped rom on there so load the shipped rom (found on here) on your sd and flash back and just make up some excuse that it isnt working right and youl get a replacement or if you can get the spl revrted jus throw your device in bootloader by a failed flash (pull the usb out during flash) and say its stuck in the funny colored screen lol
jaysjob, i've been dealing with ppctechs for a long time (probably since '03-'04) they're very reputable and highly recommended. They actually got the contract to be the authorized repair center for I-Mate about a year ago.
But why would you pay $79 for something where u can get a complete replacement? Yah it might be a refurb but my device that i turned in was all scratched up from drops.. the images on the start, ie, and messaging buttons by the d-pad had scratched off.. and now the device i got looks brand new (i actually think it is a new one but i never asked if it was a refurb or not)
pazookie, what your saying is true.. always take advantage of the warranty if you have it. If you dont and you want to repair it yourself, know what your doing! I'm very handy and have done many lcd replacements and other various repairs on cellphones (nokias, HTCs, sony ericsson, samsung, motorola, u name it!)
My little brother has the n82 and he bought the black case, I told him to wait for me and i'd help him do it but he got impatient and he thought it was gonna be a simple swap. He ended up breaking his LCD doing it which set him back $80!
anyways i'm happy now with a new device but i'm gonna go back tomorrow and get it replaced again because the vibrate is extremely weak!
fone_fanatic said:
jaysjob, i've been dealing with ppctechs for a long time (probably since '03-'04) they're very reputable and highly recommended. They actually got the contract to be the authorized repair center for I-Mate about a year ago.
But why would you pay $79 for something where u can get a complete replacement? Yah it might be a refurb but my device that i turned in was all scratched up from drops.. the images on the start, ie, and messaging buttons by the d-pad had scratched off.. and now the device i got looks brand new (i actually think it is a new one but i never asked if it was a refurb or not)
pazookie, what your saying is true.. always take advantage of the warranty if you have it. If you dont and you want to repair it yourself, know what your doing! I'm very handy and have done many lcd replacements and other various repairs on cellphones (Niki's, HTCs, sony ericsson, samsung, motorola, u name it!)
My little brother has the n82 and he bought the black case, I told him to wait for me and i'd help him do it but he got impatient and he thought it was gonna be a simple swap. He ended up breaking his LCD doing it which set him back $80!
anyways i'm happy now with a new device but i'm gonna go back tomorrow and get it replaced again because the vibrate is extremely weak!
Click to expand...
Click to collapse
Hi fone
Thanks for the reply.
Yes, I agree with you. If the phone has something else that is messed up like you were saying a scratched screen or buttons. It's just that I am as careful as I can be to keep the phone in nice condition just to send it back for maybe one that someone didn't take the same care of.
Mine works good now. I think it has something to do with when I crimped the cable end. It make a tighter fit. I think that may be the key to mine and others problems. For sure it is becoming more and more clear that there is a design flaw whether att wants to acknowledge it or not.
Thanks for your input about PPC too. If I do end up having to fix it that's probably the way I'll go if that is still the only thing wrong. Otherwise it's in for the warranty as you suggested. I KNOW I'm not that smart.
Im having this same issue and it is definately not a cable problem.
tayloryork said:
Im having this same issue and it is definately not a cable problem.
Click to expand...
Click to collapse
if u think its a hardware problem then take it to a service center. The guys there just follow step by step guides on how to diagnose phone issues. For me he saw a crack in the usb jack on my device and just replaced it. If you send it in to HTC i think theres a higher risk of them figuring outu the device is hard spl'd and wont honor your warranty.
tayloryork said:
Im having this same issue and it is definately not a cable problem.
Click to expand...
Click to collapse
taylor, I'm not saying it is a cable problem. I am saying it is a hardware port problem. I "fixed" mine, probably temporarily, by crimping my usb cord so that it holds more firmly in the port. I did say if you have the same problem and you use the same test I did ie: move it slightly, Gently, not like others I have heard stories of where they ram it from side to side until it snaps off, that you might be able to do what I did. I thought others with the same problem might be able to use this workaround until at&t figures out it is not an isolated incident with thousands of people having the same problem thats all. Hope this helps.
jj
I had a similar problem. Phone would charge fine, but windows didnt even recognise anything was plugged in. Interestingly the bootloader changed to USB when the cable was connected, and Serial when unplugged.
As it turns out (thanks Flying Kiwi for suggesting the obvious I had overlooked) the middle top pin was recessed too much into the plastic guide, so I stabbed it a bit with a scapel and all is well.
So it seems that the Serial/USB section of the bootloader cant even be trusted.
Hello XDA-Forum,
i am new here, so you dont know me. Therefore i have to mention at least one thing about me: I never ask for help. Especially not regarding electronic Devices and Computer Systems. I always found my answers without asking.
Now i do ask for help. Do the math, its a serious problem . As i am used to solve my problems before asking for help, i have much to tell before anyone could add to what i already know about this problem (although i have to admit that i am pretty new to the Smartphone World). And as sure as i know that no one here wants to read another "Phone broken, HELP!" Thread, so sure i know that not everyone has the time or patience to read my ramblings (i actually wrote a rant too, but decided not to include it here ). So i prepared a summary, and you can see at a glance (almost) if you could help me at all.
Short Story:
My HTC One is Hard Bricked, and beyond my ability to repair - stuck in QHSUSB_DLOAD mode, no access to partitions, no booting under dead screen. It seems i have to send it in for repairs, but i dont like that(well who does?). I researched the problem, tried every solution i could find - no result! if you happen to know a solution, please read the long story to learn what i have tried so far, and if your solution is something completely new (something i didnt try) - PLEASE tell me ASAP before i send it in for repairs.
So, i tried everything i know of and came to the conclusion: it is beyond repair, at least for me. But as this is against everything i believe in (well not everything but i hope you get the point ) i want to find some other Solution if not for me ( as i need my Phone to be working again soon) then at least for the next one facing the same problem. Again: read the long story, or at least the last part, to know what i am asking for... Basically i want to collect all information regarding this problem and find a solution if possible.
Oh and i would prefer technical answers (even if i might have to learn more to understand them) over answers that suggest "Dont bother, you are a noob, you wouldnt understand, just send it in". If you are about to give such an answer, rethink and do something else .
Long Story (Part 1 - What happened):
31/12/2013: My HTC One suddenly stopped working. Until then it worked just fine since i bought it in July 2013. It happened without any apparent cause or any hint of what went wrong, during everyday use, no water involved, no falling, nothing that i could identify as cause. I pressed the power button to wake the phone as always - but the screen stayed black. At first i thought the battery could be empty, but i checked it only 5 minutes before, and it said 32%... still i thought the power indicator could be buggy. Since then it never showed any lifesign again though. It wont start, it wont charge.
I researched about this, and it seems that others had the same problem, and on several different devices. I think i found almost every Qualcomm based device, but mostly the problem was caused by flashing, so this can not be the same problem. If i remember correct, i found HTC One, HTC One S, HTC Desire C, HTC Sensation, Nexus 4/7, Samsung Galaxy S3/S4 and maybe some more, with the same issue i have - Device suddenly went black and got stuck in QHSUSB_DLOAD mode without apparent cause. Many people get at least a lifesign from the LED tough ( be it blinking occasionally, or staying on all the time, or blinking after pressing certain buttons) - i dont.
Long Story (Part 2 - What i tried):
I found several tips on how to revive a device in this state, most recommending something like "press power and one(or both) volume button(s) for XX seconds/minutes" sometimes with the addition to do this under a bright light bulb.
I tried holding the power button, power + vol. down, power + vol. up, power + vol. up + vol. down, for {10,20,30 seconds, or 1,1.5,2,3,5,10 minutes} (countless times), and the same under a light bulb (i doubt this makes any difference as i already did some resets previously, outside in pitch black darkness long before the phone died).
Some recommended to plug it in to charge and dont touch it for 3,8,12 hours - i did that. i tried charging with wall plug and via USB at laptop (for short periods and for 1,3,4,6,8,12,18 hours without touching it).
At the moment i try to leave it off the charger for some days (the weekend and probably some days after) hoping that it will eventually loose all charge and does some sort of reset after that. I doubt it will work, or even be enough time for discharging (as i doubt that it actually USES power in this state) but dont know what else to try before sending it in.
The charging-led stays off when plugged in and there is no response at all from the device. Except when i plug it in at the laptop, Windows recognizes it as QHSUSB_DLOAD. And under Linux i get the Qualcomm device too - no partitions though. If i press power for 10 seconds while connected, it reconnects - so the power button is working. QPST recognizes it as "Q/QCP-XXX (Download)". Is this normal or should it recognize the phone model even in download mode? I tried to get some information through QPST but it tells me the phone needs to be in DIAG mode - which i obviously cant activate on the phone itself. Other than that no life sign at all( also no recognition by adb and fastboot - so its not booting under a dead screen as someone suggested somewhere - dont remember where).
Everyone who had gone as far as i did in trying to revive the phone just gets this last answer "JTAG, or send it in for repair".
Long Story (Part 3 - What i learned):
As i understand it, the Qualcomm Processor switches to this state (QHSUSB_DLOAD) in case there is a severe problem. But i want to know exactly WHAT problem can cause this? And if there is ANY way of convincing the processor to switch to some other state without opening the device?
I dont know JTAG, i never heard of it before this research, so please correct me if i am wrong, i did just a brief research on JTAG and found it too complex to grasp in one or two days i will delve into it at a later time. Here is my first few-minutes-glance at JTAG: it is some sort of standardized hardware-debugging protocol built into many chips, and also the Mainboard or Processor or both in modern Smartphones and Tablets. One would need to open the device and solder the connection cables of a "JTAG-Box" to specific contacts on the Phones Mainboard, is that right? or is there a plug? (I think i found some people using a plug and some using solder iron... i dont remember properly.) When a JTAG-Box is connected to a JTAG-enabled chip, it can issue debugging-commands and/or queries to check (and/or modify?) the functionality of the chip. I found some mentions of JTAG via USB without explanation, is this a way to issue JTAG commands without JTAG-Box over USB Cable? (would be very convenient) Or is it just a way to connect the JTAG-Box via USB to the Computer?
You might ask, if i researched it, i should have every answer, so why am i posting this? Right, i got SOME answers. Now, i know...:
1) ... that am not the first one, nor the only one with this particular Problem. And not even my phone model is the only device with this problem. It might be, all Qualcomm powered devices are possible candidates for a sudden-brick-syndrome.
2) ... some ways to revive a Phone in this state (none working for mine).
3) ... if all reviving tricks fail - JTAG or Repair-service.
4) ... that JTAG needs an opened device (or does it? JTAG via USB maybe?)
5) ... that my phone is not entirely dead: at least the processor can still (sort of) communicate with the PC in Qualcomm High Speed USB - DownLOAD mode.
6) ... no one knows (or tells) what the cause is (or could be) for this problem. The only answers i got are: "There are many possible causes." and "It could be a Software problem" (HTC Support) and finaly "No one can tell without analyzing the device" (HTC and Carrier Support) - Sure no one can definitely tell what EXACTLY is wrong with THIS device... but someone could know what COULD be wrong (What the KNOWN causes are), and just tell me.
Long Story (Part 4 - What i want to know):
Well... I could(/should?) just give in and send my phone in for repairs and hope for warranty. But i did unlock the bootloader through HTCDev (had no other option for unlocking due to HBOOT 1.44) and suspect, they might use this fact to refuse warranty and charge me for repairs, which i might not be able to afford right now. Further, i am feeling absolutely helpless in doing so, and i am NOT used to feel helpless facing ANY sort of problem with ANY electronic device! It is NOT a nice feeling! And i want to change that! Even if it will be too late for me, as i have to get my phone back soon and will probably send it in this week for that reason, i want to find a Solution, that anyone could use to solve this Problem without even contacting the Service, if it is possible to find such a Solution. That is the reason i am posting this, and here is what i want to know:
1) EVERY Story about devices stuck in QHSUSB_DLOAD mode.
1a) IF they where revived and HOW.
1b) What was the cause?
1c) If they could not be revived...
- ... and had to be replaced by a new device: what did the repair team tell what exactly was broken? if they told you anything at all.
- ... and needed replacing parts: WHAT parts where replaced?
- ... ANY hint of what caused the defect?
1d) WHEN did it happen? (while flashing seems to be the most common scenario, but i and some others had it happen during everyday use)
2) What exactly is possible to do in QHSUSB_DLOAD mode (probably using QPST)? and what isnt? f.e.:
2a) Pulling any data from the phone without switching to DIAG mode?
2b) Getting ANY information about the phone? (IMEI,CID, etc... Hardware components - i guess it would need a switch to DIAG mode?)
2c) Switching to DIAG(or any other) mode ONLY using the PC and USB connection? (if possible, how?)
2d) Pushing any Data to the device
As i understand it, that is the purpose of this mode(is that correct?), but:
2e) What data can be pushed? Bootloader? System Image? .... i think some CPU firmware is delivered with QPST, correct?
2f) Is it possible to convert an existing System Backup so that it can be flashed with QPST? (i understand QPST needs files in IntelHEX format to push them? Or is that just the CPU Firmware?)
2g) QPST recognizes my phone as "Q/QCP-XXX (Download)". Is this normal or should it recognize the phone model even in download mode?
3a) If i get no Partitions in Linux while the QHSUSB_DLOAD device is recognized, could this be an indicator for an Hardware failure?
3b) Does it mean, at least the flash memory is fried? (my guess)
3c) Could i tell if the Mainboard was fried by NOT even getting a QHSUSB_DLOAD device? Or can it still be the Mainboard?
3d) Can i tell anything from these facts (Getting QHSUSB_DLOAD device recognized but no partitions)? other than "its a hard burned brick" obviously...
4a) Which kind of HARDWARE failure could create this state?
4b) and how could that happen during normal use in a device that is only 6 months old, and in good condition? 5a) What kind of SOFTWARE failure could cause it?
5b) while it is running? (every day use / not flashing) 6) IF i send it in:
6a) Will they be able to access my data?
6b) Can they tell (by JTAG maybe) if it was rooted,flashed, had an unlocked bootloader?
6c) And the hardware is dead, will they just replace the fried parts? or replace the Phone with a new one? (not really important but nice to know )
7a) Is it possible to use ANY type of JTAG commands/queries/(whateveritiscalled) WITHOUT opening the device? (via USB)
7b) Without a JTAG-Box? (already existing software simulating a JTAG-Box) 8) What kind of Information can be gathered by JTAG? f.e.:
8a) Working state of hardware components?
8b) Access to files on flash memory? 9) What kind of modifications/commands can be made/issued by JTAG? (depends on the device/chip attached i assume?)
I know i could just buy a JTAG-Box and learn everything about JTAG to answer some of these questions myself. But i did not find time for learning about something completely new (new for me) yet, and i dont have the money at the moment to just buy a JTAG-Box without knowing how to, and if i will use it (dont even know how much it is...). I will certainly NOT open my 660€ phone, probably breaking the screen and whatever in the process, because of its DONT-OPEN-ME-Design(nice looking, but in some cases inconvenient), and make it a test-dummy for my first JTAGing steps. So it would be nice if someone with some experience in that matter, could give me a brief overview of the possibilities and uses of a JTAG-Box - AND if there is some way to simulate one.
And finally i would like to get into contact with people who might have a clue of the possible causes for this problem, and the ability and willingness to work on a solution. I did find some WIP Unbricking Projects also working on a solution for QHSUSB_DLOAD related issues, but all of them where Model-specific (and mostly for cases where a specific flashed software was the cause) and none for the HTC One (M7)... Although i would like to have a general solution for every device and cause, i doubt there would be any Model-specific Project if it was POSSIBLE at the moment to provide a general one. It would be nice though, if we could at least TRY to make one(some people probably are already trying). But i assume (from what i read) that the existing unbricking projects still need access to the internal storage. So, no access to storage = hardwarefailure & not unbrickable by software?? Even if thats the case and my phone is realy beyond (sofware)repair, i would still like to get answers to my other questions!
If you did read all of this - Congratulations! Have a coffee and a break
I am sorry for:
- noob questions (if there are any left besides the JTAG related - i cant tell anymore)
- annotations and supplements in braces (it can be annoying, i always squeeze in some thoughts somewhere)
- forcing you to read this wall of text, probably full of spelling and grammar errors (i am tired and somewhat tense)
- bad English (not my native language, and... i am tired)
OMG this post is incredibly long. I'll give you a short answer.
Yout phone is hard bricked and MAYBE a JTAG may fix it, BUT the phone needs to be opened, which with this phone is pratically impossible to be done, furthermore you need smb with experience on those things.
If you weren't soing anything to your phone(s-off, hboot flash, ruu, etc) than probably the motherboard is dead. I have seen this happen a lot of times with this phone, probably because of not genuine charger/faulty. You SHOULD sebd your device for repair definitely, I'm 99.9% sure no one will notice it's HTC dev unlocked, cause it doesn't turn on. A lot of users have sent their and had no problems. Good luck!
Sent from my HTCONE using Tapatalk
Very interested in the actual answer, and the reason, subscribed.
Sent from my iPod touch using Tapatalk
elvisypi said:
... MAYBE a JTAG may fix it, BUT the phone needs to be opened, which with this phone is pratically impossible to be done, furthermore you need smb with experience on those things...
Click to expand...
Click to collapse
Thats why i wont just try it... not on this phone, and not before i know more about JTAG.
elvisypi said:
...If you weren't soing anything to your phone(s-off, hboot flash, ruu, etc) than probably the motherboard is dead...
Click to expand...
Click to collapse
Well, the phone is (was) s-off, rooted, and running ARHD 40.3 + TWRP 2.6.3.3 - but i did this long before it died and never had problems during the process, or while using the device.
elvisypi said:
...probably the motherboard is dead. I have seen this happen a lot of times with this phone, probably because of not genuine charger/faulty...
Click to expand...
Click to collapse
I mostly used the HTC plug which came with the phone for charging. Although i didnt use the original cable, because it broke shortly after i got it. Sometimes i used a USB-Battery-Pack to charge the phone on-the-go. Could any of this be the Cause?
elvisypi said:
...I'm 99.9% sure no one will notice it's HTC dev unlocked, cause it doesn't turn on. A lot of users have sent their and had no problems. Good luck!
Click to expand...
Click to collapse
So, they cant just JTAG it (or do something similar) and it will turn on again? Obviously not if the motherboard is fried... but is it possible that it isnt, and they can? I will send it in nontheless, but i would like to understand what is possible, and find the cause aswell as a solution.
oh and thank you!
MarvThor said:
Thats why i wont just try it... not on this phone, and not before i know more about JTAG.
Well, the phone is (was) s-off, rooted, and running ARHD 40.3 + TWRP 2.6.3.3 - but i did this long before it died and never had problems during the process, or while using the device.
I mostly used the HTC plug which came with the phone for charging. Although i didnt use the original cable, because it broke shortly after i got it. Sometimes i used a USB-Battery-Pack to charge the phone on-the-go. Could any of this be the Cause?
So, they cant just JTAG it (or do something similar) and it will turn on again? Obviously not if the motherboard is fried... but is it possible that it isnt, and they can? I will send it in nontheless, but i would like to understand what is possible, and find the cause aswell as a solution.
oh and thank you!
Click to expand...
Click to collapse
Hi, just wondering if you had any updates to your story?
I have a HTC One in basically the same situation - it totally died on my wife in the middle of her using it. The battery was at over 50% and we have never even dev unlocked it or flashed ROMs or recovery etc. No lights come on when charging, tried all manner of the power, power+vol key combos etc, tried the bright light as well, nothing gets it to come alive. Plugging into the computer does recognise the HSUSB_DLOAD low level qualcomm device but as yet I havent been able to get drivers to allow it to be recognised. I am taking it to a place on the weekend that says they have JTAG box and may be able to help. I would send it away for warranty replacement but it's my wife's phone and she hadnt backed up the photos on it for a few months and we have a 20 month old son, so we are trying everything possible to retrieve the data off it. Lesson learned, will be putting in place backup regime on our phones from now on!
Will let you know if any joy comes from the JTAG process
Reading your recent comments it is interesting to note that we do have an external power brick (IO Gear 11,000 mAH unit) that we sometimes have charged the phone on. Potentially we even used the 2.1A output from this power brick rather than the 1.0A output on occasion.
Sorry, i totally forgot about this Thread over all the other things in the last weeks (Starting a Business, moving to a new Place.. etc).
scarecrow420 said:
Hi, just wondering if you had any updates to your story?
Click to expand...
Click to collapse
Yes, i sent it in for repairs, and got it back two weeks later. They had to replace the Mainboard and some other Parts(plus some they broke during Repairs), i could not get any information about the possible causes other than "there are many"... It was covered by the warranty though.
I dont think they could get any data from the Phone.
scarecrow420 said:
Will let you know if any joy comes from the JTAG process
Click to expand...
Click to collapse
I would appreciate that
scarecrow420 said:
Reading your recent comments it is interesting to note that we do have an external power brick (IO Gear 11,000 mAH unit) that we sometimes have charged the phone on. Potentially we even used the 2.1A output from this power brick rather than the 1.0A output on occasion.
Click to expand...
Click to collapse
If the cause is indeed the power brick, i will have to check mine again (measure its output). It is supposed to have 5.0V 1.0A output only, which is the same that the HTC Charger is labeled with.
Well, good luck with your Phone! But if your Phone is as dead as mine, i am afraid you probably wont get those Photos back...
-
Ok, i got my phone back without trouble - but i am still researching (when i have got the time ) the causes and a possible solution for this problem. So, if anyone has any information that could be helpful: please post it here!
Hi guys! Sorry for my bad english but i'm italian. My HTC One gone in QHSUSB_DLOAD mode 3 times (it's not a joke) and i've still it in my hands
This is my configuration now: (today my phone entered in QHSUSB_DLOAD mode)
Firmware = 4.19.401.8 (Darkbootoader)
ROM = SkyDragon v12.0
Kernel = ElementalX 13.0
PVS = 5
Today when tried to turn on the screen with doble tap it do nothing, screen was completly black and same thing when i hold the power button with vol down. After i plug in USB (it was a normal nokia cable) cable and hold power + vol. down for about 20 seconds (there wasn't LED or blinking button, anything) it's boot into bootloader:highfive:
I suppose (because every time my phone bricks when i do too Undervolting) it has "hangry" of energy and it boots up anymore if i don't give him an "help". The same thing when i had the MIUI with the same undervolting
Maybe is too much Undervolting the reason of hard brick, did you undervolt your CPU like me?
Did you find out any answer?
Where you able to bring it back to life?
Did you send it back to HTC for repairs? How did it go?
Would this work?
http://unlimited.io/qhsusbdload.htm
Dredead said:
Would this work?
http://unlimited.io/qhsusbdload.htm
Click to expand...
Click to collapse
third time.
To make a long story short (like you did in the OP), I have to same problem
The cause: flashing newer firmware version. All the symptoms are exactly the same. When I get home from work today I will try these 2 things, they are a little variation of what I already tried:
http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
http://www.androidlegend.com/how-to-use-adb-fastboot-commands-with-your-android-device/
I don't have much hope that I can fix it myself and am already in contact with HTC though. The main problem is that I'm in Argentina and I bought the phone in Germany..
You didn't find any other possible fixes, right?
Hi, I Have Same Problem Since A Month With My HTC One M7 32GB
I Got this phone as a Gift From USA HTC one M7. My Phone Just got hanged on lockscreen when i try to restart it, it turns off but did not turn on,no single light is turning on, no screen light or notification, no recovery or download mode. its like a brick piece. i tried all charging tricks such as USB PC ,Wall Charger for Hours, Orignal Charger and rest things, i cannot send phone to USA , i am in qatar, what should i do, any guys who experienced such problem and how did they solved it and, what will be the cost if no warranty. any help ? thanks in advance. :crying:
till22 said:
To make a long story short (like you did in the OP), I have to same problem
The cause: flashing newer firmware version. All the symptoms are exactly the same. When I get home from work today I will try these 2 things, they are a little variation of what I already tried:
http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
http://www.androidlegend.com/how-to-use-adb-fastboot-commands-with-your-android-device/
I don't have much hope that I can fix it myself and am already in contact with HTC though. The main problem is that I'm in Argentina and I bought the phone in Germany..
You didn't find any other possible fixes, right?
Click to expand...
Click to collapse
Hi, how did this go? I just bricked mine doing the same thing... upgrading firmware. I can't get it to respond to any of the suggested methods. What sucks is that the firmware update dialog in fastboot looked good to me. Sucks...
mkclarke said:
Hi, how did this go? I just bricked mine doing the same thing... upgrading firmware. I can't get it to respond to any of the suggested methods. What sucks is that the firmware update dialog in fastboot looked good to me. Sucks...
Click to expand...
Click to collapse
The link to the fix is on page one
http://forum.xda-developers.com/showthread.php?t=2770684
clsA said:
The link to the fix is on page one
http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Cool, thanks! I wonder if a vm running linux would work. All my machines are windows. Not sure how the vm would handle the usb connection. I'll have to see what I can figure out.
I just used an ubuntu boot CD when I did it
Sent from my HTC One using Tapatalk 4
clsA said:
I just used an ubuntu boot CD when I did it
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Yes! I just thought of that after I posted. I think I still have an ubuntu live CD around here somewhere...
Thanks!
I'll be damned! This worked! I just popped in the latest Ubuntu liveCD and went to town. My phone is now up and charging. Once it's at 100%, I'll try pushing TWRP recovery to it and restoring my last backup.
Thanks again for sending me to that link!
---------- Post added at 10:42 AM ---------- Previous post was at 09:59 AM ----------
Done and done... pushed TWRP and restored my last backup. It's as if it were never bricked! And it also updated my kernel, which is what I was trying to do in the first place.
Just for future reference for anyone coming across this thread, there are two distinct types of bricks being discussed here.
The first results from a borked firmware update. In this case, everything works on the hardware side, it's just that the phone can't boot because the firmware is messed up. This is usually fixable using Dexter's method.
The second, and the problem experienced by the OP, is more serious and is hardware related. I have seen this occur with multiple HTC models. Something related to power management on the motherboard dies so that the phone no longer can no longer get power to start up. When this happens, the phone will typically have shut down without warning despite having a good battery charge. I have never seen or heard of a fix for it beyond returning it for warranty repair.
htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0