I got error 152 and after unplugging battery, Desire won't boot up. In fact, in won't do anything. What now?
You need to provide more details mate
Sent from my CM7.1 Desire using XDA Premium App
What kind of details you require?
Are you sure when running RUU you had Stock hboot?
Do you have 4 exclamation marks in each corner when starting phone?
Yep. I even used downgrade HBOOT.
So, I've opened ticket in live-chat. After few seconds, I was connected. After 30 minutes, I got "Thanks for contacting HTC customer support. Your issue is being reviewed".
So much for support...
Anyone? Anything?
Sorry i have no idea, never heard of this error before.
It failed to flash most of the components. It flashed HBOOT and radio I think. The rest showed Fail-PO. I was following on-screen step for repair this error, which included removing and inserting battery. From that point Desire is completely dead. Even connecting it to AC won't light up LED.
COMPLETELY dead? as in won't even turn on? if that's the case youre screwed. If by completely dead you mean a black HTC screen with 4 [!] triangles, once in each corner then it's not dead and can be fixed, you just have to flash the correct RUU. I did it to my phone and managed to fix it from that..
EDIT: sorry, you just posted that right before I pressed reply
Lol? I just received answer from HTC support:
"We do not support installation of illegal software!"
WTF is this ****? Since when is RUU illegal?
Illegal shouldnt be taken litetally, rather if you rooted your phone you've breached their conditions
Sent from my CM7.1 Desire using XDA Premium App
First off, the said literally illegal. Second, RUU is official software. And third, warranty only applies for hardware.
I used to work at a phone warranty centre mate. They mean illegal in terms of the warranty.
Warranty covers hardware but includes software, the fact that you rooted your phone suggests that you installed unauthorized third party software which voids the warranty. Third party software can have adverse effects on the hardware, for example overclocking the CPU can damage it. Therefore they do not support phones that have been modded.
Look at the warnings on ROM download pages, they say 'you have now voided your warranty'
Enough info for you?
Maybe do some research before you make false claims next time.
Sent from my CM7.1 Desire using XDA Premium App
So when widgets are failing in official ROM, it's not their business to fix it, but if they were failing in custom ROM, it's their business to take my warranty away? Cool!
Anyway, I got it working again.
If you're having serious software issues on a stock handset it should be covered under warranty. But yes, unfortunately the moment you root your phone and install ROM you void the warranty and nothing is covered. There are warnings about that all over the place before you do any Modding. Anyway I'm glad to hear you got it working again mate.
Sent from my CM7.1 Desire using XDA Premium App
Guess what: It died this morning. AGAIN! What kind crap I bought... ?
What happened:
After successful resurrection everything was working OK. That is until I turned it off last night and since the morning it's playing dead.
Have you tried to do again the procedure that got it working? This may sound silly, but if that works, maybe an option is to not let it discharge and not remove the battery as it seems that's when you run into trouble. At least until you can research the cause of the problem and fix it properly.
Sent from my CM7.1 Desire using XDA Premium App
The thing is I dunno what I did. At first I thought it was because I changed SD cards. But this didn't work this time, so it either was something else, or total accident, which is more likely. If I won't be able to revive it tomorrow, I'll send it back for repair. Thank God I have stock ROM inside.
Related
i tried updating my radio to the newest one...so i clicked it...looked away and i had a gray screen then the phone turned off....now it wont power back on at all...not even in recovery...and when plugged into a/c power i dont even get the amber light...what the hell should i do....thanks
What do you mean, you clicked it? Which of the two radio versions? Were you in recovery, ROM Manager, etc..? More detail!
kris54241 said:
i tried updating my radio to the newest one...so i clicked it...looked away and i had a gray screen then the phone turned off....now it wont power back on at all...not even in recovery...and when plugged into a/c power i dont even get the amber light...what the hell should i do....thanks
Click to expand...
Click to collapse
are you rooted or stock? this happened to me once, but it seems that i had a bad rom install. i was able to boot into recovery mode and just restore my nandroid backup of the previous rom. hope this helps.
if you're not even getting the charging light, you're most probably bricked. sorry man.
RIP to your Evo.
i downloaded the newest radio like 7.28,,,then was in rom manager and selected the radio to install from sd card,,,clicked ok...i looked away for maybe 10 seconds and then i saw an all gray screen...then it powered off...now i cant get it to turn on...yes i was rooted...
kris54241 said:
i downloaded the newest radio like 7.28,,,then was in rom manager and selected the radio to install from sd card,,,clicked ok...i looked away for maybe 10 seconds and then i saw an all gray screen...then it powered off...now i cant get it to turn on...yes i was rooted...
Click to expand...
Click to collapse
I know may sound stupid but remove battery for a minute or so and try again... was your batt low when u started the update? May just have to wait for a bit of charge b4 it will turn back on...not sure if this will help but hopefully it will. Best luck to ya.
no...battery was nearly fully charged...and battery has been out for about 20 minutes...im thinking its bricked...anyone got any ideas? also...what do can i say when i take it into sprint..
I Think its bricked :/
But about your phone if it is bricked, i would say i lost it and keep the battery and sd and pay insurance to get a new one.
its hundred bucks for a new one...i was installing a htc radio,,,thinking its covered under manufactured warranty,,,also got 2 batteries for 8 dollars so not a great deal lol
My friend who is a manager at a store said that now that its legal to root a phone its still covered under warranty so is try takin it in
Sent from my PC36100 using XDA App
spencelk said:
My friend who is a manager at a store said that now that its legal to root a phone its still covered under warranty so is try takin it in
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
soo...the manufacture warranty isnt void?
spencelk said:
My friend who is a manager at a store said that now that its legal to root a phone its still covered under warranty so is try takin it in
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yea its legal and your friend is probably a cool dude and don't care and will warranty them but unfortunately they don't have to honor the warranty if user changes / modifies software that was not ota or provided by HTC or Sprint. Use at your own risk.
I would'nt tell them you tried messing with the software. I would just say you woke up this morning tried to turn on the phone and it would not turn on. Tell them you turn your phone off every night when you go to bed, keep it simple.
It's void if they know about it. That's what they said on g4 atots when they did the special on jailbreaking and rooting. But will they know if it don't turn on? I assume they (htc) would just flash new software on it and give it out as refurbished.
alright thanks guys...but it was the htc software lol...new radio update...idk,,maybe that dont count since someone had to extract it.,..but thanks guys
Its a long shot but wait a couple days for the update to come out and tell them you tried to update and it did that......
Sent from my PC36100 using Tapatalk
Yes, it is legal via an exemption to the DMCA to root/jailbreak a phone - HOWEVER, if you break the phone by doing this, it isn't going to be covered under the warranty. The warranty still only covers normal use, and hacking, however legal, isn't normal use. Sorry dude. Magnusson Moss Warranty Act, look it up. Warranty doesn't cover when you break the thing yourself, only when a manufacturer / latent defect causes a failure.
It really depends on which sprint store you go to. I always go to a 3rd party Sprint repair shop near my house. I had a rooted hero to 2.1; when the evo came out i bought one and took the hero to the sprint shop to update to the official 2.1 version to give to my dad. When they tried updating it, the phone would never fully boot so they gave us a brand new one. yes they new it was rooted and had a custom rom, i had talked to them that day and before about it and they didnt care.
anyway, best of luck in this situation. If you dont have a cool sprints guys than i would take sprink's advice and say you woke up and it wouldnt turn on. if there is no damage, what can they do?
^ Good luck with that...legal or not, he screwed the phone up. Not a warranty issue...
Just seen this thread they might be able to help you out.
http://forum.xda-developers.com/showthread.php?t=735686
Same thing happened to me...
I tried to restart my Evo today and the same thing happened. I took it to the Sprint store and the tech there said that the power button actually failed, and that they had to ship me a replacement. From what he was saying this has happened on a few of the Evos.
Ouch brick. Bring it back play stupid. I bet the issue was using rom manager to flash a radio. A radio isnt a ROM its the MOST IMPORTANT piece of code the phone has and a sure fire way to brick it if you mess it up. I wouldnt use rom manager other than to boot into recovery
Hi guys, I have a problem with my Desire, but cannot find anyting about that kind of problem in xda-developers or internet.
Here is the video with the strange effect http://www.youtube.com/watch?v=XRqpW-pRNWI
The problem is that it occurs at random times.
Have you ever seen that kind of problem, is it the display or the motherboard?
No and prob to do with the connection most likely. Send it to HTC.
Wow, thats heavy, did you try to reflash whole android? It kinda seems to be a sw fault. But if you have, then another question would be if you have dropped the phone, if yes, prepare yourself cca 85£ if not, then warranty should apply...
Anyway, you will need to send it for repair
Sent from my HTC Desire using XDA App
Zheiko said:
Wow, thats heavy, did you try to reflash whole android? It kinda seems to be a sw fault. But if you have, then another question would be if you have dropped the phone, if yes, prepare yourself cca 85£ if not, then warranty should apply...
Anyway, you will need to send it for repair
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
No its not droped. I play very nicely with this device, it is "Desire" after all.
I tried the original rom, the efect is the same. This happens even at bootloader.
I have a doubt that the phone was not brand new when I received it with missing foil. The phone was purchased from internet from local store.
This was happened a few week ago, after it was returned from service they said that the display is twisted
Now the probleam apears again.
Anyway, now the display is completely dead - i see only black screen with slim lines with different colors. Tomorow I'll visit the store again, but I don't know how to prove that it's not my fault.
That might be dificult, keep your receipt and in case shop refuses to fix it in warranty, then Id go directly to HTC hoping it wasnt opened and tampered with...
Sent from my HTC Desire using XDA App
Hey guys.
Maybe somebody could help me with my problem. I debraned my DHD from T-mobile some month ago... rooted it, installed Bootloader, Rom Manger and Clockwork recovery...
all works fine... then i installed Leedroid 2.3.2.. all worked fine, system was stable.
Then some weeks ago, i noticed, that my touchscreen doenst work anymore... I turned the phone off, took the accu out w8 some mins, rebooted over CW.. then it wokred again...
today i got a phonecall, wanted to take it... again... no reaction from the touchscreen or the keys down.... i tried all today, wiped all data, did a recovery, installed new ROM's.. nothing worked.. the volume buttons and the power button did work... i dunno what to do anymore?
i already flashed a RUU over it... still the same
Maybe anbdy got some ideas?
Greetz
Sounds like a hardware fault to me.
Sent from my Desire HD using XDA App
Has to be Hardware Related, if it was anything to do with the Software than there would have been more than one instance of this error, which I have never seen nor heard off, but also wiping the phone should fix the problem, also given the pattern the phone followed if working then breaking, it deffinatley sounds like a temperamental fault. Hope I helped.
Sent from my Desire HD using XDA App
Yep, a long winded version of exactly what I said. ;-)
Sent from my Desire HD using XDA App
so what i should try now ?
Pr3muToS said:
so what i should try now ?
Click to expand...
Click to collapse
Depending on where you bought it from, contact HTC or your Carrier, however if you bought it from a shop that sells phones on behalf of a Carrier then you will have to take it to there.
So basically what I'm saying is, contact the place where you got the phone from, it has a 12 month warranty which means all Desire HD's to date are still covered.
Sorry, I don't know what country you are from, but in the UK we have a shop called 'The Carphone Warehouse', they sell phones on a selection of different networks, and they sell you an unlocked phone, with the carrier SIM in. In this case, you would contact the shop, NOT the carrier, as it's the shops phone? Sorry if I have confused you.
Well lucky for you, you can revert the phone back to stock without needing to use the touchscreen. Make sure you flash a official ROM and do ENG S-ON before sending it in for repair.
ErOR22 said:
Well lucky for you, you can revert the phone back to stock without needing to use the touchscreen. Make sure you flash a official ROM and do ENG S-ON before sending it in for repair.
Click to expand...
Click to collapse
Software modifications no longer void warranty, its still android.
Hey guys,
writing to you because of a friend's wildfire s (Unbranded!, Software Version was: 1.33.401.2)
She told me that the phone became very slow and so on, so I told her it would be good to update to newest software (if that would not pleasure her, we could try a costum rom).
So I tried it via OTA, but the phone kept telling me it was up to date for days.
So I thought why not updating it the old method via RUU. I grabbed "RUU_Marvel_S_HTC_Europe_2.13.401.2_Radio_47.23a.35.3035H_7.53.39.03M_release_225747_signed.exe" somewhere from the internet, did everything as described there and the update went flawlessly, it told me from 1.33.401.2 to 2.13.401.2 as expected
I got the message that the flash was successful and that the phone needs to reboot. So did it, but now it's just dead.
The only thing it does is flashing the screen up (it's still black, just the backlight's on) and then it switches of again - that happens in circles, on and on - nothing more, no splash screen, no chance to get into bootloader.
It seems like its totally smashed up? I really don't know why regarding the fact that the flash went flawlessly and that everything seemed to fit to me (or did I chose the wrong RUU? - Dont think so )
What will be the next steps? I think there's nothing more I can do, it's HTC's time now or not? Do they repair such devices/cases under warranty?
Thank you guys for your help and please don't forgive me my bad english, it's late here in Germany
DN41
I don't recall anyone recovering from this. It looks like the ruu didn't run properly and flashed a bad/corrupt radio If you have warranty, i suggest you go claim it
Problem is, hat about one week ago i changed her digitizer because it was broken. Doing that, i had To remove
The void-sticker.
We all Here know that The issue is Not related to my work (Yes? D) but What will htc do? I guess they wont do anything and just send it back with void warranty? :/
DN41
Sent from my icecold Desire HD using XDA
They will say that you have to replace the motherboard and will charge for it
Mh thats Bad...how much will it be?
Sent from my Desire HD using XDA
Don't know. Never done that before
Ok thank you mate.
Let's see what they gonna tell me...I really don't know what has happened cause I did that many times before on my other devices like the hd2, dhd, td and so on.
Man, this is so weird.
I've stumpled upon some ebay offers for jtag bootloader repair for about 30-40€ - this should work as well I think, did you make any experience with that in the past?
Thanks a lot mate, your help is greatly appreciated.
DN41
DN41 said:
Mh thats Bad...how much will it be?
Sent from my Desire HD using XDA
Click to expand...
Click to collapse
i went many times service center for repairing my wfs.motherboard will be charged up to 99-115 €.but its india's price i dont how much in your country.in short its very costly more than half on phone's price.
So its definetly Not Worth IT lets wait what htc will Tell me.
Thanks for your answer.
DN41
Sent from my Desire HD using XDA
First off my device is unlocked and rooted but that is it and I did that weeks and weeks ago when the latest android patch came out.
It has been working fine but I had a sleep over with the kids last weekend and they like to play with it as usual. After they left, hours later I noticed the device showing the google start screen like it was stuck there. I tried to get it into the boot loader or recovery and nothing. Now it appears dead, no lights, etc.
I tried charging and tried using the volume and power thing, etc to no avail. When connected to the pc I am gettng the dreaded QHSUSB_Dload thing.
#First question is there a fix for this? I have searched every where and have yet to find anything substancial other than the volume thing which is not working.
# second question is can I rma this or will it not be accepted due to it being rooted? There is no way I can bring it back to stock without accessing the bootloader.
#last question - If I cannot rms it can I take it apart and do something to repair it or is there anything I can do?
Thanks guys. This really sucks. i have never had an issue up until now and this thing is totally stock besides being rooted and unlocked.
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2381582
That will not work with a hard brick. I cannot get into bootloader or adb.
Sent from my Nexus 4 using xda app-developers app
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Thanks for the outpouring of support here. :banghead:
I think it is clear I'm screwed.
Pretty unbelievable as I'm all stock except for recovery.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd try to send it back for repair. What do you have to lose?
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I understand that, but right now you have a $200 paper weight. So why not gamble on the s/h for the rma?
I think you are misunderstanding what I am saying.
Google basically makes you pay for a replacement. Upon inspection they refund the money. If they do not refund the money then I am out the full cost.
I could find that reasonable if I was playing around or something but I have kept my devices all stock ever since the latest version came out except for unlocking and rooting.
I guess the other option would be to find someone to do a jtag repair and I could only find one guy and I don't think he touches Nexus 7s. Not sure though but waiting for him to reply. This sucks! My device was perfect and I loved it.Great battery, no touch screen issues. Not a single issue and then all of a sudden this. i really cannot understand what caused it.
Thanks for the reply. I really figured there would be others this happened too but everyone gets Hard Brick mixed up with soft brick and every hard brick post I read is not a hard brick. Hard Brick = F#cked :crying:
I gotcha. I thought you paid to send it back & then you had the option to pay to fix it if it wasn't covered by warranty.
That could be through Asus directly but not sure.
I think though if they go to repair it they will see the unlocked boot loader. That voids the warranty
Sent from my Nexus 4 using xda app-developers app
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
dkryder said:
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
Click to expand...
Click to collapse
Yeah, if you know an RMA is a very very very poor shot / don't want to try it. I guess a tear down is your second best bet.
You should check out Adam Outler's tear down videos if you feel you might be able to take this on. I'll link Outler's videos below. They MAY help you in deciding if you want to go through with it (and what you may expect to see).
http://www.youtube.com/watch?v=RMzi4K_PwPs (Transplant Nexus 7 Boards)
http://www.youtube.com/watch?v=QOFpY1nXFew (Nexus 7 Unboxed the XDA way)
Thanks guys.
I finally got an email back from those guys that do Jtag repairs and he said it was a hardware issue but I am not sure if he understood my issue.
I do not think taking it apart and unplugging the battery will work here if the bootloader is corrupt. I am going to try to let the battery go completely dead though and then try to do the volume/power key thing to see if there is any chance.
I do not know much about this but what I read is that if the bootloader is stopped somehow while loading it can become corrupt in some cases and you cannot do anything without it and there is a device specific key involved. That is why only someone with some specific software can fix it. I thought this key as called Jtag but again, I do not know much about this. The Jtag guy said it was hardware.
Man, I have an Hp touchpad that I got years ago. I installed Android on it years ago and have it overclocked it to over 1700mhz and that thing is still going strong. The kids even dropped it and it has a crack in the screen and it still will not die. Here I have a Nexus only a few months old fully stock except for root and unlock and it is dead. Kills me especially after the way I always stand up for the Nexus line. Still loving my Nexus 4 though and it is well over a year old. Oh well, if that one goes like this one I am jumping off a high bridge. :laugh:
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
whoamanwtf said:
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
Click to expand...
Click to collapse
First off, I am not sure what is wrong with it which is why I am posting here. I stated numerous times that I do not know much about this.
And yes, I know this that rooting and unlocking voids the warranty. I also know that it is my fault for doing it but I have been doing it for around 3 years now and have used various roms and kernals in the paqs and have never had an issue. Perhaps it is a hardware issue. I just do not think this issue was caused by me.
In terms of the kids playing with the device. They play games, things like that. The desktop is locked and they have no access to settings or anything. When I said messing with it I just meant playing games though sometimes they open new games and leave the old ones running. I do not know how that would cause this.
There was no ota or update.
I am not sure what you are saying about LG.
And again, I am not angry with Google or Asus. My point was that this issue was most likely not caused due to rooting or unlocking and an ota would not cause a dhsusb issue even if it did go bad.Lets try to remember that nearly everyone here roots, unlockes and installs roms, etc. I have done so as well but not on this device. This one I wanted to keep pretty much vanilla but I wanted to be able to use Titanium back up, etc. And also, I rooted and unlocked months ago when I first got the device and had to root again when the latest version came out which was awhile ago.
In terms of fixing I have not found a solution for this. I do not know if it is a hardware issue or a software issue. That is why I am posting here. I am looking for some information from people who know this stuff. I know nothing but what I have read and so far I have read many different things. I am here to learn.
OK so here is what I meant with the G2..
I had a stock/rooted/TWRP G2 and half asleep accepted an OTA Update, when it does this it downloads the update into a partition that the device checks before booting. Because I had the custom recovery obviously the update failed but it left that code in the boot partition that would now allow me to even get into download mode. See this post here for how it was fixed http://forum.xda-developers.com/showthread.php?t=2582142
I am not sure if this would be the same problem or how to go about fixing it because of the device difference, but maybe it could help? I didn't mean to come off as a ****, just far too many people like to get into their devices and void the warranty then blame everyone else.
It is really not difficult to pull the back cover off and unplug the battery, I suggest doing this it could very well help just be careful not to crack the back while pulling it off, a credit card/ID and a butter knife should do the trick without leaving marks.
No worries. I appreciate the help.
I agree with you totally.
Sent from my Nexus 4 using xda app-developers app