Related
Hi everybody... I hope there's some smart people out there.
I've used this thread to downgrade (or try to) the RUU to an older HBOOT, so that the bootloader could get unlocked using revolutionary.
Everyhing was going smoothly until the install of new RUU. It stopped at 22 % without any reason and made an error. Now I'm stuck at the HTC logo, still S-ON and nothing has been done - other than bricking my phone.
Anybody got a great idea what to do know?? Just to make it work again?
Thanks.
rundownshorty said:
Hi everybody... I hope there's some smart people out there.
I've used this thread to downgrade (or try to) the RUU to an older HBOOT, so that the bootloader could get unlocked using revolutionary.
Everyhing was going smoothly until the install of new RUU. It stopped at 22 % without any reason and made an error. Now I'm stuck at the HTC logo, still S-ON and nothing has been done - other than bricking my phone.
Anybody got a great idea what to do know?? Just to make it work again?
Thanks.
Click to expand...
Click to collapse
you might want to try factory reset, Boot the phone holding down the volume + power and then factory reset. This worked for me, when my phone went on continuous loop and with HTC screen and my operators logo.
let me know how you go, and i would wait for a better solution for getting root on the newer versions rather than carrying an expensive paperweight.
cheers!
rundownshorty said:
Hi everybody... I hope there's some smart people out there.
Click to expand...
Click to collapse
Sorry for being rude, but the smart people are usually reading Guides before downgrading
hi every body
pleas i need your help
i have a trophy device when i power on my device boots normally then stops at black screen windows phone and restart alone
http://forum.xda-developers.com/attachment.php?attachmentid=996940&stc=1&d=1334157187
i do reset and try a new room but the problem is not resolved
Note that my device is unlocked by XTC clip
http://forum.xda-developers.com/attachment.php?attachmentid=996941&stc=1&d=1334157187
pleas i need your help
i,m sorry because my English is not very good
thanx
I'm not familiar with XTC clips or the effects they may have on the phone, but there are some things you could try.
Can you hard-reset the phone? This requires holding a few different buttons at power-on (look it up) but it's possible.
Can you boot the phone to Update/Recovery mode, and try restoring a Zune backup that you made previously? Press and hold the Camera button while starting the phone, then connect it to the PC and start Zune.
Do *not* attempt a custom ROM; SPL 4.6 will break if you try to use RSPL/HSPL. However, you could try using the CAB sender (if you can get to update mode) to downgrade the phone, and then flash a custom ROM instead (since you can obviously get to bootloader mode).
GoodDayToDie said:
I'm not familiar with XTC clips or the effects they may have on the phone, but there are some things you could try.
Can you hard-reset the phone? This requires holding a few different buttons at power-on (look it up) but it's possible.
Can you boot the phone to Update/Recovery mode, and try restoring a Zune backup that you made previously? Press and hold the Camera button while starting the phone, then connect it to the PC and start Zune.
Do *not* attempt a custom ROM; SPL 4.6 will break if you try to use RSPL/HSPL. However, you could try using the CAB sender (if you can get to update mode) to downgrade the phone, and then flash a custom ROM instead (since you can obviously get to bootloader mode).
Click to expand...
Click to collapse
thank you very much
The problem existed before i used the xtc tool
i mack hard reset but problem not solved
i don,t have backup on zune
any help pleas
thank you again
Try re-flashing a stock ROM. There are links to many ROMs on the XDA-Developers Wiki; just go to the page for your device and there should be a link for ROMs.
Other than that, the only other advice I can offer is to replace your phone under warranty, as it's obviously not working...
have you tried a stock rom?>
HTC has some limitations on flashing custom rom
If it still doesn't work,i;m afraid u need to use some special tools (Y-line?goden card?I really don;t know how to translate these thing,my English is much poor than you)
thank you very much
i tried a lot of stocks ROM i,ll try again
pleas if you have another way tell me these way
The only other thing I can think of to try is downgrade your bootloader, install HSPL, and flash a custom ROM. However, if flashing a stock ROM didn't fix it, I doubt this will.
At a guess, you have a hardware defect - possibly bad RAM, for example - that is causing the phone to crash at a certain point during bootup. I suggest that you just get it replaced, if at all possible.
GoodDayToDie said:
The only other thing I can think of to try is downgrade your bootloader, install HSPL, and flash a custom ROM. However, if flashing a stock ROM didn't fix it, I doubt this will.
At a guess, you have a hardware defect - possibly bad RAM, for example - that is causing the phone to crash at a certain point during bootup. I suggest that you just get it replaced, if at all possible.
Click to expand...
Click to collapse
thank you very very very much for your your interest in my proplem
i,l try hardwere Solutions
I have a HTC Sensation and i have flashed my phone several times with no problems. I have used other HTC too and flashed them as well.
When i wanted to flash my phone from Virtuous Inquisition (ICS) to Android Revolution HD (ICS) and i bumped into a problem as many other has as well. I would like to send away my phone to someone that could help me fix this since i have tried so many things and im out of ideas. What i most would like to do with the phone is to bring it back to factory default since the volume down button is broken and there is still waranty for this phone.
So if someone can fix this phone via ADB that would be great. I have tried to flash it myself and do all the things in my power via ADB to fix it but with no luck.
Is there anyone who can help me. I would prefere someone in southern part of sweden or denmark. Anywhere arround the Öresund area.
See it as an experiment/challenge to get the phone fixed. I consider it to be bonus if the phone can be revived and sent back to repair the hardware under the waranty.
I will of course give some reward for the person who can help me fix this phone in form of money or something. This will be discussed before i send it over to you.
Thanks in advance, and i hope there is someone out there that is intererested in this challenge.
So are you still rocking a custom ROM now ??
Download the correct RUU for your region, (if your SuperCID use any) and that will restore the phone back to stock.
Once completed, Use ADB to reboot recovery, fastboot, change CID to whatever RUU you used. Then use the code to turn S-ON (cant remember what it is) You could leave S-OFF and deny all knowledge of what it is. I doubt they would suspect much if the only mod is S-OFF.
Hey!
About a week ago, after rebooting my device, the softkeys at the bottom of my screen stopped working as they´re supposed to do. When i tried to press a button, nothing happened. However, if i would press slightly above the actual button it worked fine.
But now (after flashing other roms in order to fix it), even that wont work anymore. In addition, when in Recovery(TWRP), a line of about half a centimeter at the bottom of the screen above the Softkeys is unresponsive too, preventing me from navigating back etc.
Don´t know if thats a possible cause but this happened some days after I installed a Rom with Sweep2wake for the first time. Worked fine until the problem appeared.
Things I tried yet: Flashing several different Roms(Cm9,Cm10,IceColdSandwich,FalloutEvolution,Andromadus), Factory Reset, Calibration (didn´t expect it to work but worth a try ^^),Using the Search-Function.
Specs: Unlocked SAGA PVT Ship S-ON Rl
Hboot 2.00.0002
Rom i used when the Problem appeared is Cm10.
If any additional Informations(Logcats,whatever) are required, just ask.
Help of any kind would be really appreciated!
Thank you very much and have a nice Weekend.
As long as you are S-On, you should maybe send it back to HTC if you have the warranty, since it is more of a hardware problem than a software problem (maybe the sensors are not in the right place). But before you do that you should change the hboot version to 0.98, since they can see that you unlocked your bootloader and the warranty would be gone. And you also should backup your data, so that you have a fallback positon,
Thanks for your reply!
I forgot to mention that I unlocked it via htc-dev. I didnt change the Hboot-Version, so why would you advise me to change Hboot?
PS.: Ordered at amazon,so thats where i would send it back to.
The reason you should downgrade hboot version is that they can't see if you unlocked it via htcdev or not. Normally if you would unlock it via htcdev you can see that the bootloader is unlocked and there is no way to put it into previous state (you can only put it into relock, but your warranty would be still gone). So I advise you to downgrade the hboot version to 0.98.00000 and flash a stock Rom, since HTC only accept stock Roms, S-On and locked bootloader.
P.S: You instantly get locked bootloader as soon as you downgrade and lose your S-off, just follow the steps in the Android Development section carefully
P.P.S: Does anyone know where the Desire S gets repaired when you send it back to Amazon?
Sent from my HTC Desire S using xda app-developers app
Is it actually possible that this has something to do with Sweep2wake? Just wondering, because this problem appeared while using a ROM with Sweep2wake for the first time.
EDIT:
I just activated visual touch feedback to see what happens when i touch the softkeys or the screen at the bottom 0,5 cm. The "visual touch response point" always appears centered at the top of the area not working. I made a picture with my old e71, very sorry for the horrible quality and my mad Paintskills . Pink arrows leads to the visual touchfeedbacl, green one to where i actually touched the screen.
EDIT2: Forgot, the picture, but im actually not able to post the link due to my low post count..
Isn´t that a sign that it is not hardware related?
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