Related
Hi,
I have an HTC Fuze. Currently i have WM 6.5 on it and i have no clue what my stock att rom version was. I have the warranty that covers practically everything like water damage and me just dropping the phone. I am concerned that ATT will be able to tell my rom version even if the phone is broken. If the phone breaks and it will not turn on is there a way for them to tell my rom version? If they can tell can anybody help point me in the right direction for the right stock rom. Thanks.
Swirlycurly said:
Hi,
I have an HTC Fuze. Currently i have WM 6.5 on it and i have no clue what my stock att rom version was. I have the warranty that covers practically everything like water damage and me just dropping the phone. I am concerned that ATT will be able to tell my rom version even if the phone is broken. If the phone breaks and it will not turn on is there a way for them to tell my rom version? If they can tell can anybody help point me in the right direction for the right stock rom. Thanks.
Click to expand...
Click to collapse
If you do a insurance claim on the device you pay the deductible and get a new device, they do not check rom info at all. Sometimes you are not even required to return device.
you can rent a wood chipper at home depot.
They DO REQUIRE you to return the fuze. I would flash the at&t stock back on there. It will also wipe out your personal info on it too. I would flash it if ya can, it take like 5 min of your time, just to save a bunch of hassle and potentially causing your ins. claim to be voided since you modded the phone.
I used to work at ATT, they do not require you to return it under certain circumstances. Its usually for insurance returns though.
For example, how would you return a phone if it was stolen?
Most mobile dealers hire people that don't even know what a ROM is in the first place. Ive seen devices taken back that clearly say "SECURITY UNLOCKED" across the top of the boot loader, and thats the screen the phone is stuck on (obviously a bad flash that the n00b didnt know how to fix). Ive even known people to take back water damaged phones and get a customer service rep that didn't even check the LDI to see if it was pink, but gave out a new phone.
Hey guys...As a few of you know, my phone met its demise last night for (seemingly) no reason. I had recently backed up my ROM through Rom Manager and tried out a few themes from the market.
Anyways, when I plugged my phone into my computer, I see that it tried to install some drivers and then I see "QHSUSB_DLOAD" as my phone.
Ive noticed that all TRULY bricked phones (not just the sensation) all have this "QHSUSB_DLOAD" in common. No one has yet to figure out what this is or how to fix this.
Tmobile chalked it up to hardware failure and has a new (likely refurbished ) on its way.
I think we need to figure out what the heck this is. A few mentioned a connection between Rom Manager, CWM, and QHSUSB_DLOAD. I, for one, will make dang sure that Rom Manager stays off my phone...Any other ideas?
Until this is worked out, its VERY likely that rooting COULD randomly cause the dreaded true brick, QHSUSB_DLOAD style.
Matt
Just swayed my decision on wether to root or not.
So does it turn on? You are a bit unclear about your situation. Does it charge, when you charge it. And does the PC recognize it when you connect it to the PC?
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it is crapping out or more likely something corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware (since kernel source for this phone is incomplete this IS possible) or it's just bad luck. Voltage tweaks can have a long term detrimental effect on hardware.
Hey guys, it is dead as a door knob.
http://forum.xda-developers.com/showthread.php?t=1321110
That ought to sum things up...
Im sure its bricked...I just want to look more into this as I have yet to find a single case where this was solved. It just gets pushed aside since no one knows.
Behold_this said:
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it crapped out or more likely you corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware since kernel source for this phone is incomplete this IS possible. Voltage tweaks can have a long term detrimental effect on hardware.
Click to expand...
Click to collapse
I was using cm7, build 9 and fauxs kernel build 8. I dont do UVing or OVing and have kept the CPU speed to 1.18Ghz.
My computer told me that it failed to install whatever it felt it needed.
So this is known? Am I correct in thinking that this is a 100% brick then, or is there anything, save from tearing it open, that can be done to fix it?
Although I have a new one coming, Id like to get to the bottom of this for everyone else.
Matt
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found are motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Behold_this said:
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found at motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Click to expand...
Click to collapse
Someone could get an XDA style Nobel prize for coming out with something that could fix this phone when this happens.
Im guessing that is what a JTAG does? Would be great once warranty time is over!
I am suspicious this could be another build quality issue with HTC...Day one with this phone had the same sort of thing happen, but it eventually booted. Perhaps this was just waiting to happen?
Or, I wonder if it is related to CWM and Rom Manager? This seems to be a RARE occurance considering how many people flash the above mentioned ROM and kernel without this happening. The last thing I did before charging was backing up in Rom Manager.
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Behold_this said:
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Click to expand...
Click to collapse
Okay, how about this...I intend to S-off and reinstall CWM the SECOND I get my new phone. LOL...Should I erase my ROMs+kernels from the SD card and start over from scratch, or can I just boot up again like nothing happened?
I guess its safer to start over, huh?
EDIT: I have been reading over stories involving a hard brick and QHSUSB_DLOAD. It seems it ALL came from SD card partitioning in CWM. I was also in recovery that day restoring my ROM when I accidentally touched the screen and the phone rebooted. (After restoring) I thought it was just rebooting recovery. I wonder if something else happened? The phone booted up fine and worked for some time after. The last thing done was charging the phone via wall charger, seeing it was done, and then unplugging.
Matt
it may not be necessary, but I would. I'd just redownload all the software I plan on loading from the start and give it a clean slate, but that's just me. Also be very careful with resorting apps and data since we really don't know the total cause of your issue. All in all you probably won't have to deal with this again as long as you minimize your risk.
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
vitusdoom said:
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
Click to expand...
Click to collapse
Im the alien!
Yea, I never saw this happening to me. I read carefully before I do anything and have never tried anything fancy.
Im guessing that QHSUSB_DLOAD lets you know the phone is fully erased and waiting for something to be flashed the elite way? (From the factory via their gadgets). To date, NO ONE has recovered from this.
Man Id love to be the one to recover! I crapped myself when I saw QHSUSB_DLOAD mentioned on my computer. Its the kiss of death.
I also have to wait till next week to get my replacement despite me opting for the fastest most $$$ method of shipping. UPS Express is the fastest and will take till monday (which means tuesday since no one will be around to sign for it).
Ugg..
Matt
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
vitusdoom said:
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
Click to expand...
Click to collapse
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone.
Maybe I will get lucky and get a phone free of dust as well! I was waiting on calling in that care package for later...Oh well.
Matt
Oooh nice! so the device really has a black screen and that message appeared on driver installation on you computer.
most of the people in the net just mentions that this driver is missing. If the driver is missing, maybe it did really get corrupted(software because of rom-manager not pointing to this ) but yeah, could also be hardware failure. did it say on your computer that it was installing some drivers for that QHSUSB_DLOAD? and it failed? what about HTC? did you see anything from HTC about this?
vitusdoom said:
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone
Click to expand...
Click to collapse
this is the EXACT problem im having! on my tmobile SGS2
not sure if this has already been mentioned but what do you guys think of this?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/
Hey guys,
I'm in the same situation too.... I've been flashing hundreds of roms and all kind of software on a lot of different android phones...but this is the first time ever I came across something like that where I feel that this is the end of it!!!! I made a mistake...by not paying attention flashing an HD2 rom to my sensation!!! You know some time s**t happens... and here we go...I got a completely dead bricked sensation with nothing i can do, even I've been searching and reading for 2 days with no luck what so ever...so I guess no one is able to find a solution for this issue yet!!!!Which is too bad: confused: .I wish I was able to find some solution to this problem so I can get my phone back to life and help every one else who might end up with this issue. Because I think a lot of people might be in this situation!!!. I tried every thing I can possibly do with m y knowledge and the results was all dead ends. I just hope that this issue will be taken to the next level by some one...like all the other phones that it can be unbricked...so why not the sensation!!!?. Any one can come up with and ideas for this please help us as a community to get pass by this dead end on our Htc sensations.
Guys i have absolutely same problem with my sensation, i believe there must be a way how to bring our phones back to life. Im sure that on my phone its just software problem caused by backing to s-on(got bricked right after adb rebootbootloader). So if some1 find out how to unbrick, PLEASE post it. I dont want to solve it by warrany, because its little far for me :-(
Hey, today I accidently hardbricked my 3D(yeah accidently, cause I messed up Phones). Now I have to send it to service. Anybody else had to do the same? Did LG always repair or change your Phone? Just asking cause I want to know if sending it to service makes sense. Honestly, I think it wouldn't be easy even for LG to make the Phone working again.
Not so bad
it's hard to say forsure, but if you were a tech and were judged on how many phones you fixed per hour, would you spend a lot of time figuring out whether the owner bricked it by being stupid or just try to fix it?
I mean a smashed screen is easy to spot and say "not our fault" but digitally that's not so easy.
Secondly, they have access to tools that you don't. I'm sure they have test-beds and internal connections that allow them to restore firmwares easier, or for that matter, replace main boards.
...but I don't know, I don't have direct experience with LG.
Yeah that's what I also think. I'm sure they have access to programs to which I do not, but that's exactly the strange thing. I read that many users with a hardbricked Optimus 3D got a new main board or a new Phone. So if they are able to restore the firmware, why would they change the hardware? The only answer I can give myself is that they don't really care about whose fault it really is and because of that they don't check.
GentlyCriminal said:
Yeah that's what I also think. I'm sure they have access to programs to which I do not, but that's exactly the strange thing. I read that many users with a hardbricked Optimus 3D got a new main board or a new Phone. So if they are able to restore the firmware, why would they change the hardware? The only answer I can give myself is that they don't really care about whose fault it really is and because of that they don't check.
Click to expand...
Click to collapse
Hey brate,
Why don't you take a chance? You have a paperweight anyway. Try, if it works, bingo. If it doesn't, you still have your paperweight. Don't waste another minute and send it for repair.
Zdravo from Vienna
f.
Zdravo kollegah
I already sent it to LG, I'm sure it will work. I just asked because I was thinking all the time about changing phone. But I think they won't even check
aii pozdrav iz salzcburga
On my skyrocket from AT&T I was having an issue with the battery indicator getting stuck at 100%.
I updated the phone to the latest OTA update, no root or anything on this phone, all completely stock.
After update phone info is as follows:
Model Number: SAMSUNG-SGH-I727
Android Version: 2.3.6
Baseband Version: I727UCLA3
Kernel Version: 2.6.35.11
Build Number: GINGERBREAD.UCLA3
After I did the update the battery indicator has not come back (awesome right?, not so fast.)
Now I have an issue with call quality, my best attempt at describing it is like the ear piece sounds blown out, it kind of has a vibrate when people talk, Its not just one persons phone either, its any call I get/place.
I'm not sure if I should try a factory reset, revert back to 2.3.5?, Go to AT&T for a new one.
If anyone has had this issue and knows how to fix it please post. I apologize ahead of time if this is already posted somewhere, I looked for a few hours on google and couldn't find it anywhere. Also even if you don't know how to fix it, could you please post if your having the same issue so I know I'm not alone and have some ammo if I do have to go to AT&T.
Visit AT&T Store
Of course I'm 4 days outside my 30 day trial period so I would have to get a replacement mailed to me if I can't get it to work.
Lady I spoke with there was very nice (as always) but didn't have any idea what to do (as always) and advised I try and factory reset it. What the hell, mine as well.
Also got her to tell me that if I root and custom rom it and it still dosn't work I can still RMA it. So she went against what all their documentation says so now I can do what I want
Figure ill factory reset first, if that dosn't work I'll ODIN it back to the original 2.3.5 if possible.
Ill keep updating this thread though incase anyone else has a similar issue.
albeemichael said:
Of course I'm 4 days outside my 30 day trial period so I would have to get a replacement mailed to me if I can't get it to work.
Lady I spoke with there was very nice (as always) but didn't have any idea what to do (as always) and advised I try and factory reset it. What the hell, mine as well.
Also got her to tell me that if I root and custom rom it and it still dosn't work I can still RMA it. So she went against what all their documentation says so now I can do what I want
Figure ill factory reset first, if that dosn't work I'll ODIN it back to the original 2.3.5 if possible.
Ill keep updating this thread though incase anyone else has a similar issue.
Click to expand...
Click to collapse
Haha, just because she said that doesn't mean anything. Read the contract, that trumps what some lady says. Anyways, you can flash back to stock and warranty it, so it doesn't matter what anyone says
Absolutely Right
xcrazydx said:
Haha, just because she said that doesn't mean anything. Read the contract, that trumps what some lady says. Anyways, you can flash back to stock and warranty it, so it doesn't matter what anyone says
Click to expand...
Click to collapse
As the title says you absolutely correct. Lady probably didn't have a clue lol.
I called their warranty support line and am going to drive to their wallingford exchange place.
I was talking with my father before I called and figured if I went in and said get a manager, and told him/her if I don't have a new phone in my hand in 10 minutes, your losing a customer in 10 minutes, I bet I would get my phone
Regardless I'm getting a replacement, I did try the factory reset, didn't work. Also tried downgrading the device to 2.3.5 stock, and this also did not work.
Think its hardware, the static is only on the ear piece. Speaker phone, head phones, and bluetooth do not have the issue so I think its a odd coincidence
To anyone that may have been checking on this, it seems I got a rare case, there was actually a hardware problem on my device. Just a coincidence that I noticed it right after an update, I took it to the Customer Service place AT&T has in Wallingford, CT and the lady tried to re-flash the phone (what she said was standard procedure, she HAS to with every issue.) This didn't work so she gave me a new one.
All in all, only bad part of the experience was that it happened at all. New phone is working great.
Glad tohear that you got this taken care of.
Sent from my SAMSUNG-SGH-I727 using xda premium
I know this is being discussed all over but I want to know if anyone has figured out how to fix it on Tf300t. I know buying a new board has to be bogus and this happens when the bootloader is erased. I have tried everything I could think of and no matter what i do or how many times its flashed. Flashing makes no change whats so ever. The hole thing is wiped no recovery but i do have fastboot.even though is says the flash was successful it does not take. I can put it in apx mode but its not detected in adb. Any suggestions beside returning it to asus are welcome. If asus can re flash it then somebody somewhere has to know how to fix it.
I just emailed asus to see if they know of a way to fix it, I know its pointless but I figured I would give it a shot, better than doing nothing.
Has the same problem. seem it´s bricket.
Fastboot as coomand but it doeant working to flash anything
How out of all the people who have had this problem that no one who knows how to fix it. If anyone knows please help out the thousands of people who have this problem and are fooled by Asus into thinking it has to be sent in to be repaired or buy a new mainboard. Its not a hardware problem its data related. Deleating stuff from a devices does not break the hardware it just needs to be written back to it.
Im in a battle with asus as we speak tryng to find a soulutions. Will let you know if i get a fix for it.
Im also in a battle with Asus there telling me there sorry they have not made software to flash there tf100 tf300 and tf700 tablets and that I have to pay for them to fix it. This is realy stupid that a huge company like Asus can't make software to flash there own tablets. If they tell me something I will post it here and thanks for letting me know Im not the only one fighting with Asus.