Related
Hi Guys,
Finally after playing with a lot of roms I decided to go back to stock. I was flashing back to stock using the RUU exe from HTC and something went wrong. Phone is now stuck in RUU mode whenever you turn on. Have access to fastboot but when I try to boot recovery etc getting remote not allowed. Any suggestions other then paying $450 aus for new board?
Thanks
well if you got fastboot then you got hboot. which is good. i am pretty sure you can run a stock .nbh and get reverted allllll the way back to total stock just like removing root. im not to sure but look into those options. if you can do that then you should be able to reroot and not have a $450 shinny brick. i bet someone will respond with a better answer after this is posted lol!
I don't know if this is a standard solution, however I had the same problem for the past few day, and I tried everything and as I am updating from HTC RUU I held the action ( track ball ) button pressed and it did the upgrading . . . I'm not going to try again, but that is what happened.
Hope that helps.
Cheers,
Andre
First of all thanks for this great forum !!!!
This will be my first post. I have to thank all developers to get the sensation s-off.
I made a stupid mistake with the eng hboot. I played a little round and typed
"fastboot oem fdisk erase_emmc.
Now Phone is completly dead and bricked. Can not power on and no charging.
But it must be possible to bring the sensation back to life. I downloades QPST an drivers and see, that the device is in download mode.
I tried cdma workshop and DFS CDMA Tool too.
Can somebody make a dump with QPST and backuo the nv file and firmware image to unbrick the sensation.
Please no commands why I have done this. I said it before. I have no second sensation to try it by myself.
Has anyone an idea ??? (without to send it back or jtag flash)
Thank you for any help.
Kindly regards Woody01
Sorry for bad English
Send me the commands and i do it for you!
No comment on what you have done
I'm sorry man, but we can't help you. Once you erase something like that, it's over for that device. If i'm reading correctly, the internal sd card is completely wiped, no recovery, no HBOOT, no / (original mount point). The thing that bothers me, if you didn't know what it did, why would you run that command? That is idiocy at it's finest. The only thing you could do is send it back for a warranty replacement, since it's bricked like that, they won't able to tell you ever rooted or flashed anything. If you do send it back, play dumb, say you woke up one day after charging it all night and it just wouldn't turn on any longer. Once you get your replacement, do not install the ENG HBOOT, it isn't for noobs for this exact reason.
Download mode could be a mode where it wait for flash ... keep it off until someone comes with ideas....
Thank you for your answers but I expectet such replies.
It must be possible to bring it back. In QPST you have the ability to flash back the Multi-Image file. But i am missing the the phon image hex and boot hex. I think if someone make a backup from the Multi-Backup and NV file we could unbrick it.
For the Galaxy S someone wrote at tool (One click unbrick). There will be everything restored. (partition, boot, etc).
Is someone interestet to help me trying this ????
Kindly regard Woody01
I say again tell me how i do it .... backing up should be no problem for a device
@xtcislove
First of all you must dwonload QPST (I found it by google). I have version 2.7 buil 355.
You need the QHSUSB Drivers. I found the drivers on google. I think the phone must be in diag mode. Use QPST Software download. There is an option backup. There you can backup the firmware. It will be restored as an qcn file.
To restore the NV File you can try DFS CDMA Tool. There is an option to read the NV file. At that point I could write the file from Wildfire. I could delete it too. I used the free version 3.2.0.0
For Diag mode you need the HTC Diag driver.
It is possible for me to upload these files here in forum and is it allowed ???.
Thank you
Be careful with the NV file. There is your imei and serial number. It would be nice if someone send the file with edited imei and serial.
I need the hex files for QPST. Some wrote in the www something about CDMA-Workshop to get the hex dump.
Kindly regards Woody01
Sry i cant edit my imei etc out ...
and with 3 posts i dont trust you really ... sry i think u should ifnd someone
@ xtcislove
I understand you and is absolutly O.K . I would not send the NV file with my emei and serial too. (only the file with editet imei and serial)
I hope someone is interestet and crazy to unbrick the device and help me.
Kindly regards Woody01
Get a warranty replacement and don't even S-Off your phone. You obviously can't handle it.
In curious, why were you doing what you were doing?
Sent from my HTC Sensation Z710e using XDA Premium App
WorldWide60 said:
In curious, why were you doing what you were doing?
Click to expand...
Click to collapse
Haha i was wondering the exact same thing
I have similar situation. my phone won't boot, no LED anywhere.
what i stupidly did was, i tried to reinstall the stock ROM and between shuffling the screens around i skipped one step. that step was actually opening the stock ROM and running it and following the commands. so i tried to unroot and S-on without selecting a ROM to flash...... now i'm screwed.
i checked my SD card in my old phone and all the data is still there. will that make a difference. or am i helpless?
massasshadows said:
I have similar situation. my phone won't boot, no LED anywhere.
what i stupidly did was, i tried to reinstall the stock ROM and between shuffling the screens around i skipped one step. that step was actually opening the stock ROM and running it and following the commands. so i tried to unroot and S-on without selecting a ROM to flash...... now i'm screwed.
i checked my SD card in my old phone and all the data is still there. will that make a difference. or am i helpless?
Click to expand...
Click to collapse
I have my sensation bricked...it's dead with screen black...someone has a solution? Thanks to anyone
Bricked mine too (Yes, very stupid indeed)
aramis73 said:
I have my sensation bricked...it's dead with screen black...someone has a solution? Thanks to anyone
Click to expand...
Click to collapse
I was stupid enough to brick mine too by an S-OFF -> S-ON transition . No solution I guess? I e-mailed three different repair centers, but no response yet. I wonder if it is possible at all to flash the Sensation's bootloader without a functional USB connection.
For other phones it can be done by a JTAG interface, but this is very delicate job which I can't do myself.
For now I consider it bricked. I bought some Apple stocks (AEX ING Sprinters Long, Dutch stock market) and will let these pay (I'm already there after today) for the new Sensation that I bought already. If it is repairable after all I will sell one of them again. I'm not going for a warranty return. Beside the fact that it is possibly detectable that I voided the warranty by touching the bootloader, it is my own mistake that I have to pay for....
By the way I have been looking for more people who killed their HTC Sensation, but I could only find you two guys and a german who is mentioned in this thread as well.
Please keep in touch!
choas2009 said:
I was stupid enough to brick mine too by an S-OFF -> S-ON transition . No solution I guess? I e-mailed three different repair centers, but no response yet. I wonder if it is possible at all to flash the Sensation's bootloader without a functional USB connection.
For other phones it can be done by a JTAG interface, but this is very delicate job which I can't do myself.
For now I consider it bricked. I bought some Apple stocks (AEX ING Sprinters Long, Dutch stock market) and will let these pay (I'm already there after today) for the new Sensation that I bought already. If it is repairable after all I will sell one of them again. I'm not going for a warranty return. Beside the fact that it is possibly detectable that I voided the warranty by touching the bootloader, it is my own mistake that I have to pay for....
By the way I have been looking for more people who killed their HTC Sensation, but I could only find you two guys and a german who is mentioned in this thread as well.
Please keep in touch!
Click to expand...
Click to collapse
I'm actually doing the whole return process. Since mine is so badly inoperable, I'm hoping that after they inspect it they will be able to give me a new one. I was able to S-On the phone (as far as i know) during the process so if they are able to read it, it should be cool. If anything i'll either be turned down or have to pay for a new one.
Planning on blaming it on the over night charging + the 2.3.4 update they released the day i bricked it haha. It's all just a game of chance.
i did it too my friend , some mistake S-off ---> s=on transition , do you have any solutions
Hello everyone, I'm a noob and this my first post. I had been reading blogs for years now on all sort of advice and solutions, so yes this is my first reply or post on any blogs. I usually find the answer I'm looking for so posting anything was unnecessary. Now I really need help. I screwed up some how. I was attempting to turn S back to ON because my device was not taking the new update, and by doing so bricked my phone (wont power on. I'm guessing I had restored a rom and not original back up which xl VipeR lx had warned about in his instructions. I have SD with su-2.3.6.3-efgh-signed.zip on it. Can someone please help I really should had not rooted my phone because I dont have the knowledge. I can take instructions very well (was Soldier in the U.S Army for 8 years (2 years in Iraq). So if some one would please give me instruction on how to fix this, I would really appreciate it.
Is there any solution ?
Thanks !
Would this tool allow me to make a backup of my phone that can be restored if ever it is bricked? In other words, would it make my phone nearly unbrickable? I mean, there is very little chance of my phone being bricked, I make sure I know exactly what command does before I execute it. I realised I have spent most of my days in the last couple of weeks reading XDA and thinking about my soon to be gf in Hong Kong XD. I just worry that when flashing a firmware file I may be left with a brick, or even get one of those bricks people speak of that just happens randomly. I really don't want to lose my phone, it means so much to me lol. I just get so worried with these things....
What I'm trying to ask is, a partition backup created with this tool can be flashed to the phone with what functioning partitions? ie do you need a working radio partition or not? working hboot? Cause what I'm scared most about is flashing a bad radio and creating a phone that can not get into hboot... i'm also scared about getting a random brick which at the moment seems to be unfixable.
Mind you, it would make a pretty impressive paperweight....
EDIT: found this guide... can someone explain what NV items are? A small understanding of this may allow me to make a backup using this tool that could then be used to unbrick sensations... I couldn't find what NV items are... I also found this....
Hello everybody
My appologize if such kind topic is already posted but there is too much topic and I couldn't find relative information.
so, briefly I'll try to explain what was happened.
Month ago I've bought brand new HTC Desire S. Phone was bougt in Dubai, S-ON, Android 2.3.3
During update from android market (few games and facebook application, I clicked update all) my phone freezen, no reply at all.
I got desicion to remove battery and put it back. I've done it and phone switched on on white screen with HTC logo...that's all
Unfortunatelly, there is no any HTC customer service in our country, so I had to show my phone for another specialist. He recognized that boot file on my phone was corrupt, re-installed it. next step is to re-installe the software and here we met with problem.
no any software can be installed. I've used different software for different regions, but all of them were unsuccessful. initially it were shown two type of mistake
sometimes CID incorrect and sometimes Main version is older
we desided to install goldcart, so after installation is going ok, but again phone freezen on updating screen during bootloader update.
for info I've tried to install application from computer through the fastboot usb and through the memory card as well...both attepmts failed.
Does anybody can help me? Please consider that I'm not so perfect on such kind device and detailed explanation will highly appreciated. thanks in advance.
try install this RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.0 85AU_3805.06.02.03_M_release_199476_signed
from a windows PC while your HTC screen on bootloader
download this RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.0 85AU_3805.06.02.03_M_release_199476_signed from here http://forum.xda-developers.com/showthread.php?t=1002506
That sounds like the fried eMMC chip. You updated all on the market and pulled the battery out. You'll have to find someone who can open the phone up and replace the chip (beat you to it Ben!)
Sent from my HTC Desire S using XDA Premium App
S-ON + warranty = HTC Service repair
Adidas108 said:
S-ON + warranty = HTC Service repair
Click to expand...
Click to collapse
+1
return under warranty and get a replacement!
unfortunatelly, there is no sertificated HTC service in our country, so I need to send my phone to the Dubai..
Well the same exactly happened to me but luckily I was S-OFF & had Clockwork Recovery so everything was okay. I though that the eMMC chip was fried but I made a factory reset using Clockwork & it was solved.
I think you could just install a RUU that's certified from HTC, I would suggest that you download the WWE & If you tried that already try to access the the recovery screen (Vol Down + Power). If you couldn't access it then sorry, you're bricked.
Please reply with the results.
Can I also suggest that you rename your thread title to that it's a bit more meaningful and relevant to the problem that you're suffering, you do this by editing post #1 and using advanced edit.
to be honest I'm not so good in HTC...so fare problem not solved...but there is no any problem to get enter to the boot menu...if you pressing power with holding VOL down key phone goes to boot menu...
several people tried to solve the problem, but one of the restriction is S-ON mode...don't know what to do
I've had this problem for a while where while I'm using the phone, the touchscreen and softkeys fail. For now I've just been putting it into wakelock and unlocking it again, however its getting to a point where I can't use the phone anymore.
ROMs it's happened on: CM7.1, CM7.2 and MIUI ICS 2.4.27 (proxuser port)
Kernel: The standard one, I haven't changed that
Something that could cause the issue is the Korean IME from Google (I have that installed as its the best Korean Keyboard out there for the time being)
Pretty sure this is a hardware problem, if so I'll flash it back to stock and S-ON it and get vodafone to replace the phone for me (or try to as the case may be)
If anyone could give advice or a fix that'd be really handy.
Thanks for any help/advice given in advance.
GideonB234 said:
I've had this problem for a while where while I'm using the phone, the touchscreen and softkeys fail. For now I've just been putting it into wakelock and unlocking it again, however its getting to a point where I can't use the phone anymore.
ROMs it's happened on: CM7.1, CM7.2 and MIUI ICS 2.4.27 (proxuser port)
Kernel: The standard one, I haven't changed that
Something that could cause the issue is the Korean IME from Google (I have that installed as its the best Korean Keyboard out there for the time being)
Pretty sure this is a hardware problem, if so I'll flash it back to stock and S-ON it and get vodafone to replace the phone for me (or try to as the case may be)
If anyone could give advice or a fix that'd be really handy.
Thanks for any help/advice given in advance.
Click to expand...
Click to collapse
No fix. Have had exactly the same kind ot issue on a friend's Desire S,which needed replacement. Don't hesitate about restoring S-On and sending it back to HTC. That's the best course of action to take if you're under warranty...
Sent from a Desire S still looking for a good replacement.
Ah, I got my phone basically a year ago next week so I'm not sure if that means its not in warranty anymore.
Its working better now if I don't type really fast, but it is definitely a hardware problem then?
Sent from my Transformer TF101 using XDA Premium HD app
how to back to s-on?
How to get back to s-on? i have the same problem and still have guarantee.
I installed RUU rom but i still s-off.
H-boot version: 6.86.1002
aarnoldaas said:
How to get back to s-on? i have the same problem and still have guarantee.
I installed RUU rom but i still s-off.
H-boot version: 6.86.1002
Click to expand...
Click to collapse
Read the INDEX. Link in my signature. It has all necessary thread links for you to get back to S-On. Read about it and see if you get a hang of it. Then ask questions in the respective threads. Much easier that way than repeating everything all over again. 90% of your questions will be answered while reading the comments, and also some that you haven't thought of yet.
Cheers.
I think I'll hold out until I can get my hands on a Galaxy S or something similar (and then put MIUI on that and sell this phone or something)
Thanks for the help anyways
I'll tag this as solved (if I can)
Earlier today I tried to update my HTC One X's firmware to 3.18 in order to install the latest cyanogenmod nightlies. First, I was confused at why the latest cyanogenmod nightly would not flash so after looking it up and figured out I needed to update the firmware but to do that I would have to relock the bootloader. Second, I had issues trying to relock the bootloader, eventually got that (did not know adb was updated). Third, after believing my nightmare was over, I quickly decided I would try to flash the latest evita ruu, which completed without any errors and I clicked finish. (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed) straight from HTC's website. Finally, after a few minutes I noticed that my phone did not have a notification led, nor was it booted into the lovely (opinions may differ) HTC sense 4.1.
That is the story of how my phone got to the state it is in. The state being no lcd in any way, no notification led, but I can still hear the phone being plugged into windows and can hear it shut down and turn on (with the windows usb sounds) when holding the power button and pressing it as if it worked and I was doing a hard reboot(about a 10 second press to shut down and get the usb disconnected noise). (Tried both adb devices and fastboot devices neither showed a device). Never have I seen this before and if I can get it working hopefully I will never see it again. Hopefully XDA's member's genius can make up for my stupidity. (most likely my fault being too hasty and skipping a step :silly.
Any questions about what I did or how I did it. Please ask!
Hey bud,
sorry about your troubles. I myself have just updated to ruu 3.18 and hboot 2.14 in order to flash the xylon rom. I'm not an expert at this: I'm just another person trying to get the best (vanilla) experience from his phone! Here's a couple things I noticed in my 9 hour trial & tribulation in going from 3.17 ruu + 1.09 hboot to the latest updates:
my pc also did not read my phone on a couple of occasions. Some parts of the process, I believe you have to be on your regular screen and the phone will reset into fastboot on its own. Later on, I had relocked my bootloader before I was supposed to, and was unable to write much. I just went back to step 1 and re-did everything (had to dig up a thread on unlocking my bootloader via htcdev).
my best friend helping through this was the hold power + vol down button. i kept going to stock recovery & rebooting my phone OR into fastboot and see which place I was supposed to be at.
as for your LCD being completely dead...I haven't come across that issue. The closest thing was when I was in RUU mode and there was only an HTC logo on the screen.
if you'd like, pm me and I can msg you the xda threads I used to get through it. I'm not sure how to approach the dead LCD, but I hope it all pans out for you.
I just wanted to share my experience, as a non-dev nor extremely savvy techie, I feel your pain brother.
Its not that the lcd is dead (unless it died after the ruu flash finished along with the notification led), more like it just wont turn on, along with the notification led, Where it would usually be on when plugged in, it just no longer turns on. Anyway thanks for your sympathy, I managed to jam the nano sim into my HTC arias micro sim slot without an adaptor (cyanogenmod 7 is its latest), so yeah at least I have a phone for the time being XD.
You flashed 3.18 with supercid and s-on. If you have supercid you need s-off before ruu to 3.18.
Sent from my HTC One XL using xda app-developers app
In other words, if you RUU'd with SuperCID and s-on, you're probably bricked.
Sent from my Evita
So far, from what you guys have posted, i'm out of luck on fixing the brick by myself. I do not know if either of these are an option so, again, fix my stupidity. First, I found a hard brick repair (mobiletechvideos, can't post link yet :/) which I have seen mentioned on the website a few times so I want to know if it can fix my brick and if the repair is worth trying. Second, is replacement from at&t/ HTC an option? Of course if anyone wants to comment a fix on my first post please do .
Starfrog6 said:
So far, from what you guys have posted, i'm out of luck on fixing the brick by myself. I do not know if either of these are an option so, again, fix my stupidity. First, I found a hard brick repair (mobiletechvideos, can't post link yet :/) which I have seen mentioned on the website a few times so I want to know if it can fix my brick and if the repair is worth trying. Second, is replacement from at&t/ HTC an option? Of course if anyone wants to comment a fix on my first post please do .
Click to expand...
Click to collapse
Jtagg is probably the best option, if you're within a year you can try sending it to HTC, if they figure out how you bricked, which is possible, they will charge you ~$200USD to replace the board.
Good luck.
If you ran the RUU with SuperCID and S-on, its bricked. JTAG is likely your only option to get the phone running again. You can look into the unbricking thread in General, and the JET tool in Development. But to my knowledge, nobody has been able to unbrick from this condition (SuperCID + S-on + RUU or OTA), short of JTAG. Yes, Mobiletechvideos has been mentioned on here as on JTAG option. Can't vouch for them personally, but others on here might be able to.
If you phone is less than a year old, you can likely get a warranty replacement from AT&T. Ethically, its a bit of a gray area IMO. I'm usually not crazy about people making warranty claims for failure to read, and as a result of you having modded the phone (which SuperCID is). But in reality, it shouldn't typically be expected for RUU plus SuperCID to brick the phone (past RUUs have run fine with SuperCID).
HTC is typically less forgiving about warranty issues. So no reason to try with them over AT&T. AT&T will pretty much honor the warranty for anything but obvious physical damage. They don't care if the phone has been modded, or bootloader unlocked (not that they would even be able to tell in your phone's current condition).
http://forum.xda-developers.com/showthread.php?t=2181929
I was bricked too.
I tried to relocking my bootloader and flashing the offficial jellybean without doing S-OFF first and bricked mine. I tried everything here at XDA with no luck. I gave up and sent it back to HTC and they had it back to me running the official jellybean update in 2 weeks. and without any charge. I even got it back on my birthday. It is running smooth and fast with no lag at all.
HTC One X+ AT&T Version
Hello there,
I tried updating my phone from Android Version 4.1.1 to the latest Android 4.2.2
But after installing my phone has stuck in the HTC logo and its bricked.
Please advice me for further proceedings.
My phone details :
Updated ROM image from 1.15.502.1 to 2.15.502.1
***RELOCKED***
EVITARE_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.73.0000
CPLD-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-BOOTMODE: disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
Sep 30 2013,17:16:15
I have installed the RUU file which you have shared in the link above.
Please help me I need my phone in the working condition.
You're in the wrong forum. This is the HTC One XL forum, you want the HTC One X+ forum.
But, have you actually attempted to run an RUU from this section? Any RUU you find in this section is not for your device.
Sent from my Evita