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
Related
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?
Hi Guys,
I'm trying to get a 'stable' rom for a phone I've given to my daughter (Evita / Telstra one XL).
I've tried a heap of things, tried to s-off, change radio files etc... Anyway, current status is that it's been unlocked, s-on, and I have twrp.. I'm using KickDroid XL v4.0.0 ROM, looks great, but the phone keeps on rebooting... Also loosing 3G signal, so have to reboot it quite a few times a day to resolve. (tired another rom, same problem, loss of 3g signal and multiple reboots during the day)
I'm sure it's got to do with the radio file, but can't seem to fix that. I've read 'so much!' information, but really confused now. I've tried to supercid it, unsuccessfully, tried to find the all-in-one toolking (bt it looks like its been removed)..
So, this is what I have when I boot it:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.11.0000
RADIO-0.23a.32.09.29
OpenDSP-v28.1.0.32.0504
eMMC-boot
Jun 7 2012,13:10:34
TWRP recovery
2.6.3.0
htc one xl
Evita
Any help in how to (or if I should) get the radio/hboot up to hopefully resolve the loss of 3G?
I'm no expert, but not that dumb either. I follow instructions from the start, but most of the time it gets stuck half way (ie, when doing supercid, boots to the HTC logo, but won't go any further)..
Any help really appreciated.
The problem is not that the ROM is unstable, the ROM is perfectly stable if you meet the requirements. The problem is your current firmware version. You need to update to the 2.15 firmware package. It does state that very clearly in the "You Need" section in the beginning of the Kickdroid thread. Please search/research properly before posting in future, it's part of the XDA rules. This issue has been discussed extensively in every single Sense 5 ROM thread, plus this is probably the 100th thread like this in our Q&A section.
Sent from my Evita
Why are you even giving your daughter a rooted/modded phone at all? Unless she has an understanding of what root means, its not a good idea. Does she even need anything except a bone stock phone?
thanks timmaaa, I appreciate you taking the time out to reply.
I'll do some more checking on firmware 2.15... I've honestly read about 5 hours last weekend on various threads... some lead to dead ends (it toolbox), some I can't get to work (supercid)... I tried this a couple of months ago, and almost bricked it, but managed to get twrp working...
Redpoint73, are you asking why give her a phone, or why a rooted phone? The answer to the first one is that she is 11, and catches the bus to and from school. The phone is used in an emergency. I've rooted it to give her some new features, and because it was locked with Telstra and that is not the carrier we are using anymore (much cheaper options here than Telstra), so I needed to get rid of the firmware...
Overall, I appreciate any help. I actually run 5 forums (car related), and I fully understand noob's coming on and asking the same question week after week. Our forums have a lot less posts than this one (< 200,000), but we still have members, week in-week out, answering the same questions because they like to help, and because sometimes there is too much information out there to sift through, especially when somebody is willing to point you in the right direction with a friendly smile
duplicate post, (sorry, hit save twice!)
jnrdavo said:
Redpoint73, are you asking why give her a phone, or why a rooted phone? The answer to the first one is that she is 11, and catches the bus to and from school. The phone is used in an emergency. I've rooted it to give her some new features, and because it was locked with Telstra and that is not the carrier we are using anymore (much cheaper options here than Telstra), so I needed to get rid of the firmware...
Click to expand...
Click to collapse
Its pretty clear from my post that it was root/mod that I was referring to. Root has nothing to do with Subsidy (SIM) Lock, and the firmware has little to do with the carrier you are on (I've been using the German T-Mobile stock ROM for a while now, despite being on AT&T).
Of course its up to you to decide what you do with the phone. But you should consider (if you haven't already) the security risk of giving a rooted device to a user that knows little or nothing about such things. Even more so for s-off, which is necessary for the solution that timmaaa suggested.
My question has less to do with exactly "who" the phone is for. But more to the point, when people come on here saying they are modding the phone for "someone else" (be it mom, third cousin, or whatever), if that person isn't doing it for themselves, its pretty questionable whether they need such mods at all.
ok, thanks redpoint73..
I understand where you are coming from, and appreciate your comments.
Now, anybody else like to point me in the right direction (to a link to get the latest firmware, or a compatible one working)?
jnrdavo said:
Now, anybody else like to point me in the right direction (to a link to get the latest firmware, or a compatible one working)?
Click to expand...
Click to collapse
You serious? timmaaa already told you where to find it.
Since I'm feeling charitable right now, here it is, complete with step-by-step instructions (only need to follow Posts #2 and 4): http://forum.xda-developers.com/showthread.php?t=2485865
The original thread where Turge posted his firmware package (see under "OPTIONAL", s-off is required before doing this): http://forum.xda-developers.com/showpost.php?p=45072132&postcount=1
Or just install the Beastmode kernel (S-off not required): http://forum.xda-developers.com/showthread.php?t=2165880
thanks mate. I appreciate the charity, I really do I'm trying not to be a nob.. I'm actually having another go this morning... I've got win 8.1 (yeah, I know) so trying to get the latest driver to work is a pain.... Just trying x_factory windows, backups up twice, but then doesn't run the next command (to change CID)...
Anyway, thanks again. I'll persist on...
Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.
iceterminal said:
Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.
Click to expand...
Click to collapse
I gotchu my friend ;D http://www.htc.com/us/support/htc-one-mini-att/news/ That is the ruu for the htc one mini
abzboi said:
I gotchu my friend ;D That is the ruu for the htc one mini
Click to expand...
Click to collapse
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!
iceterminal said:
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!
Click to expand...
Click to collapse
Ah I read that it will work too if it is fastboot which is why you were suggesting it. I'm wrestling with fastboot drivers and windows 8.1 so it is recognized so I dualbooted into ubuntu which can communicate via fastboot so I'm hoping WINE will run and flash the RUU .exe
So I ended up rebuilding an older laptop to Windows 7 and ran the RUU executable and it looked promising at first with the updater recognizing the device and displaying what software version and stuff.... but then when it rebooted into hboot with it's process, the update failed.. not sure if it matters but it was "updating" from the same version as the current version. I was hoping this would be a fresh install. So now I'm looking into maybe doing a fastboot oem unlock and flashing a rom myself. Not sure if this will help me get the phone back from the dead, but going to do some more reading and exploring. If anyone has some shots-in-the-dark they would like to offer, I'm up for trying them.
I hope you would be able to fix it.
Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.
iceterminal said:
Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.
Click to expand...
Click to collapse
Have sent you a PM re your issue.....
Re flashing recovery without fastboot (locked bootloader), it can be done, but only, as far as I know, via the phone os using CWM manager or Flashify (which is a cool app!)
wanted to close the loop on this thread that nelvinchi and I literally tried everything we could think of to bring the phone back to life with no avail. Much respect out to nelvinchi for taking his time to help me out! We've determined that the device has a faulty memory chip and cannot be recovered...
Mine just did the same thing and I can't get through to anything I need help also if you have found a solution
Help my
provided you solve a problem with one htv mini.my I have the same problem, please help me
Okay....so I need to twiddle around with my trusty old HOX in order to solve the constant rebooting issues. (I also want to jump ship off of the memory-heavy Viper Venom that's on it to just straight CM or something similarly light weight)
To do that I've got to update the firmware.
And to do that... first I have to identify what bloody firmware I have so that I use the correct updating method and don't brick my one and only device.
I'm not a total noob... I've been working on a beginner/moderate level with Android for 3 years now... I can get around ADB (typos not withstanding) reasonably well, push commands, get to hboot, know fastboot and such... but I am just not finding the specific answers I need right this moment to get this work done. So if Someone can point me in the proper direction, I would be muchly appreciative.
Right Now my bootloader screen says the following
Tampered
Unlocked
Evita PVT Ship S-ON RLHboot 1.09.0000
Radio 0.20os.32.09.10_2
OpenDSP-v31.1.0.45.0815
eMMC-boot
Click to expand...
Click to collapse
So, who can tell me which firmware version contains Hboot1.09? Once I know that, I can start the process of SuperCID and S-OFF to make these updates. Barring that, anyone who can point me to a one-click unlock tool would be great too... the ones I find on the first few pages of the forum all recommend firmware newer than what I know is installed on here according to the above into, and I am leery to use them for risk of bricking my one and only phone.
Your current firmware is actually irrelevant, you need not worry about that at all. All you need to do is get s-off, which should be a sinch. Because you don't have SuperCID (I'm assuming from your last paragraph) you really only have one option, which is the Rumrunner method. It should work with Viper installed, if not it has a good success rate with the Kickdroid ROM.
Rumrunner S-off
Sent from my Evita
So I did have SuperCID... a readCID command demonstrated that.
and thanks to your assuaging my fears, timmaaaa, I was able to flash to 2.15 without a problem.
the problem now... is even after pushing TWRP every way I know how, I can't get into recovery, even with fastboot erase cache. ugh I feel like yanking my hair out.
but at least the phone hasn't randomly slowed down or rebooted since flashing the new firmware. (and the pesky double-reboot that made flashing it such a core in the first place is fixed too)
::edit:: gonna spend the next hour redownloading the venom ro so I can push the boot.img file, maybe that will fix things.
Did you check the md5 of the recovery download?
Sent from my Evita
timmaaa said:
Did you check the md5 of the recovery download?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did. I also tried to install it via a few onboard solutions like goo.im. no go. it says it's been installed, fastboot insists the phone is unlocked and s-off; but it boots to the flash screen, tries to load recovery, fails, and reboots to the rom.
I am going to assume that the unlock is fubar somehow and start from scratch by installing 2.20 and using the HTC unlock, and go from there.
now if only damned downloads didn't take 5 hours on my slow rural connections... thank you isp conglomeracy.