Yesterday my fiancée performed some updates from the market. Shortly after her phone turned off.
Now when trying to turn it on the phone gets stuck on the white screen with the green HTC logo.
I have tried booting it in to fast mode by turning it on with the volume down button held and then selecting fastboot.
This allowed me to try and flash the O2 ROM back to the phone. It find the software version on the phone (which is slightly newer than the ROM I have downloaded).
The next stage is "Rebooting in to bootloader" this is where it just comes to a stop, the fastboot menu freezes and the phone doesn't do anything.
Does anyone have any ideas? Much appreciated.
Is ur phone rooted or stock? U could try a factory reset...
Sent from my HTC Desire S using XDA Premium App
It's totally stock other than being unlocked.
If I try a Factory Reset from the HBOOT screen it just locks up. Is there another way?
If I try recovery it turns off, comes up with Green arrows in a circle, vibrates 5 or 6 thimes, then does nothing.
Hope your phone will comes up,try to flash ruu
Sent from my HTC Hero using XDA Premium App
zhaominghao said:
Hope your phone will comes up,try to flash ruu
Sent from my HTC Hero using XDA Premium App
Click to expand...
Click to collapse
I've tried to flash the RUU already haven't I? By downloading the O2 ROM.
richard_ha said:
It's totally stock other than being unlocked.
Click to expand...
Click to collapse
When you say unlocked, I'm assuming that you mean network unlocked and not S-OFF (via XTC clip)?
I'm afraid that I'd be tempted to return the device from where you bought it and attempt to get a repair/replacement unit.
Sorry that I was unable to help anymore.
ben_pyett said:
When you say unlocked, I'm assuming that you mean network unlocked and not S-OFF (via XTC clip)?
I'm afraid that I'd be tempted to return the device from where you bought it and attempt to get a repair/replacement unit.
Sorry that I was unable to help anymore.
Click to expand...
Click to collapse
Hi yes, network unlocked and not S-OFF
It seems to be like the bootloader has become corrupt some how.
I'll start making arrangments with HTC, thank you.
If anyone else has any ideas or suggestions let me know.
Related
Hello, I have a question
I had on my sensation a custom rom
But i wanted back on a stock rom.
So now, i flashed a PG58IMG,but I have not thought about it that I no longer have root.
I've successfully instaled it, but when I start the mobile phone now I'm just the htc logo and no further.
So guys, anyone can help me with my problem.
I Think he bootloader is broken
I recommend going on youtube to find a solution, just search "how to get back to stock rom" or something like that, i am sure something will pop up, and see where you went wrong, if you did, or google it
Taker18 said:
Hello, I have a question
I had on my sensation a custom rom
But i wanted back on a stock rom.
So now, i flashed a PG58IMG,but I have not thought about it that I no longer have root.
I've successfully instaled it, but when I start the mobile phone now I'm just the htc logo and no further.
So guys, anyone can help me with my problem.
I Think he bootloader is broken
Click to expand...
Click to collapse
A sure way for going back to stock is flashing a RUU. You'll still be s-off and you need to check that the RUU is compatible with your cid.
Sent from my Kindle Fire using Tapatalk
ar4l said:
A sure way for going back to stock is flashing a RUU. You'll still be s-off and you need to check that the RUU is compatible with your cid.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Yea, but i can"t start my Sensation
Taker18 said:
Yea, but i can"t start my Sensation
Click to expand...
Click to collapse
Pull out the battery, insert it, get into bootloader by pressing and holding vol down + power button hold them until you'll get into bootloader. Connect to a computer, change on fastboot mode and You are ready to flash a RUU
So I bricked my phone...
I have searched around the other threads with bricked devices but none of them had that worked for me. I am rooted and unlocked so I cant flash a RUU.
I can get into bootloader, it says fastboot but when I try fastboot oem Lock or any other command it says waiting for device and doesnt seem to do anything. (I can see the bootloader screen and the red FASTBOOT sign on my phone)
I can get into my recovery (TWRP V.2.1.8.1) but my SD seems to have disappeared, it wont mount to phone and I can not see it on file manager. Which means no backups or ROMS to reinstall. It also will not mount to my PC in recovery.
Since fastboot isnt working I cant flash new boot recovery or relock bootloader. I can completely stuck
If there is a way with adb (never used it so would need more detailed instructions).
If i try boot into ROM it just shows splash then loops.
Hadcook said:
So I bricked my phone...
I have searched around the other threads with bricked devices but none of them had that worked for me. I am rooted and unlocked so I cant flash a RUU.
I can get into bootloader, it says fastboot but when I try fastboot oem Lock or any other command it says waiting for device and doesnt seem to do anything. (I can see the bootloader screen and the red FASTBOOT sign on my phone)
I can get into my recovery (TWRP V.2.1.8.1) but my SD seems to have disappeared, it wont mount to phone and I can not see it on file manager. Which means no backups or ROMS to reinstall. It also will not mount to my PC in recovery.
Since fastboot isnt working I cant flash new boot recovery or relock bootloader. I can completely stuck
If there is a way with adb (never used it so would need more detailed instructions).
If i try boot into ROM it just shows splash then loops.
Click to expand...
Click to collapse
assuming you're using Windows. Is HTC sync running? If so kill it.
If you can get to boatloader, you should be able to see the phone in windows. It's kind of a failsafe.
gunnyman said:
assuming you're using Windows. Is HTC sync running? If so kill it.
If you can get to boatloader, you should be able to see the phone in windows. It's kind of a failsafe.
Click to expand...
Click to collapse
Your a genius...
I never shut HTC sync as soon as I did that I could OEM lock and now I am running the RUU.
Thanks for the quick reply and help.
Hadcook said:
Your a genius...
I never shut HTC sync as soon as I did that I could OEM lock and now I am running the RUU.
Thanks for the quick reply and help.
Click to expand...
Click to collapse
No problemmo.
You're only bricked (as far as I know) if you can't get to the bootloader.
gunnyman said:
No problemmo.
You're only bricked (as far as I know) if you can't get to the bootloader.
Click to expand...
Click to collapse
My other one x doesn't boot. Just stays in QHSUSB :banghead: I have warranty on the way for it. Still trying to figure out how to get boot back on it
Sent from my HTC One X using xda premium
dkirchik said:
My other one x doesn't boot. Just stays in QHSUSB :banghead: I have warranty on the way for it. Still trying to figure out how to get boot back on it
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
how did it get in QHSUSB? Is what someone said about pwr/vol UP true?
dkirchik said:
My other one x doesn't boot. Just stays in QHSUSB :banghead: I have warranty on the way for it. Still trying to figure out how to get boot back on it
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Have you tried oem refurb in fastboot. I think that's the command.
Sent from my HTC One X using xda premium
kleeman7 said:
Have you tried oem refurb in fastboot. I think that's the command.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I can't boot into fastboot.
Sent from my HTC One X using xda premium
You shouldn't need to, there was a post in s-off saying it could be ran from dload mode. From what I read.
beaups said:
I tried the pg1fs. sig check failure. As a matter of fact doing "fastboot flash aksldjflkadsfjdlsk pg1fs.img" causes the same error, so something is in the img that causes sig check or any flash attempt except recovery is sig checked. Fastbook oem refurbish puts out a lot of interesting text, then reboots into recovery and looks for something (doesn't say what).on sd card (I tried copying IMG's to internal and external sd, no luck). Interesting thing about refurb command is it seems particularly "excited" about the fact that we have super CID - run it yourself and see, no harm is done (data, etc.). one recovery boots you can screw around with volume and power keys to see the text.
Click to expand...
Click to collapse
Sent from my HTC One X using xda premium
Sent from my HTC One X using xda premium
Phone is officially dead.
RUU'ed and it completed install without problems but phone still boot loops
Which RUU did you run? Did you try running it again? Can you still boot into the bootloader? If so what does it say at the top?
Sent from my HTC One X using xda app-developers app
I relocked boot loader and ran the AT&T 1.85 ruu
Basically I now have the phone booting up, but when sense loads I can do very little on it, like text or call. As soon as I try do something more like browse the web the phone freezes and reboots. The back get warm and won't turn on immediately. I want to say the second core is shorting which is why as soon as it clicks in it freezes. Or at least what my limited knowledge would suggest.
Guessing I'm done and will be using dumb phone for 6 months
The phone has a 1 year warranty call customer service and get a new one.
Doesn't the fact that I used htc dev unlock void that warranty? And I never got my phone from AT&T so they won't help obviously.
I thought that was the whole reason some people didn't want to use htc dev unlock because it voids that warranty and they won't help because the phone was rooted and boot loader unlocked? Has anyone tried to get a replacement from htc after unlocking?
You might void it says. Hardware defects are covered. AT&T covers the phone for 1 year regardless of where you bought it. Call them.
Hadcook said:
Phone is officially dead.
RUU'ed and it completed install without problems but phone still boot loops
Click to expand...
Click to collapse
reinstall STOCK recovery (unlock BL again first if needed)
relock BL if you unlocked in step 1
factory reset
RUU
profit.
beaups said:
reinstall STOCK recovery (unlock BL again first if needed)
relock BL if you unlocked in step 1
factory reset
RUU
profit.
Click to expand...
Click to collapse
Woooooaaahhhh stock recovery? Doesn't the ruu do that? If not where could I find the stock recovery?
I thought once you have ruu you can factory reset...
gunnyman said:
You might void it says. Hardware defects are covered. AT&T covers the phone for 1 year regardless of where you bought it. Call them.
Click to expand...
Click to collapse
I doubt AT&T would help, I bought the phone out of contract from best buy they would be getting screwed. I'll try contact htc after 4th of July
They will help. They take care of phone warranty for you. You still pay for service . This warranty is part of why you pay them.
I never thought it'd happen to me..
Anyways.
I'm on Virgin Mobile in Canada, just recently unlocked my bootloader and rooted.
The process was bumpy but ultimately successful..ish.
I couldn't actually flash any roms. Not sure if it was because of the bumpy root process,
but every rom would just bootloop and I'd have to restore and deal with HTC Sense.
Great.
I had downloaded a Liquid [somethingorother] ROM from my PC and flashed it, with blind hope.
It was looping, as I half-expected.
I had this crazy idea that my roms were looping because I had neglected to press the "Perm Root" button
on the AIO root tool I had used.
Ecstatic, I rushed up and pressed that button as soon as I could.
The process went off without a hitch, but the next time I tried to boot something odd happened.
Every time I boot the HTC splash screen stating "this is for development purposes only.. etc" pops up.
-the one that would pop up when entering the bootloader - EVERY TIME.
I tried to restore but this splash screen still shows up, then loops on the HTC ONE screen....
AAAAAND that's where I'm at now. I attempted to factory restore from the bootloader, which would
erase my backups and whatnot. I don't know how infamous this issue is but I am unable to mount my storage.
Plenty other people seem to have this issue.
So, is there anything I can do?
You should try to run an RUU, then report back.
Sent from my HTC One S using Xparent Blue Tapatalk 2
invasion2 said:
You should try to run an RUU, then report back.
Sent from my HTC One S using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I'm actually trying to find one now. I haven't been able to find one for Bell/Virgin wild on the interwebs.
I'm trying to find the mysterious RUU section on the painfully slow HTCdev website..
anyone have a link or something?
http://forum.xda-developers.com/showthread.php?t=1543588
Sent from my HTC One S using Xparent Blue Tapatalk 2
The most common reason for ROMs hanging on boot splash or looping is that you failed to fastboot flash the boot image that comes with the ROM.
The good news is if you can detect the phone in your computer, your phone isn't bricked.
That message you mentioned is normal for all of us flashers
I bet you didn't notice the "tampered" flag or you would have freaked out even more
Sent from my HTC One S
I need help please. I flashed the rom following the instructions and my phone boots but the screen remains all black. I hear a sound when it boot and nothing else. I am trying to reach recovery but I haven't been able by holding volume down + power. Any help please?
---------- Post added at 11:08 AM ---------- Previous post was at 10:58 AM ----------
Never mind I got it fixed. It was all because the boot img wasn't in place yet.
Sorry to beat a dead horse but i think i bricked my phone ! I to have a virgin mobile canada HTC One S but i can't find the ruu for virging mobile I Tried bell and it didn't work thus screwing up my phone. please pleaase please i need help I just got this phone yesterday.
lilsammy11 said:
Sorry to beat a dead horse but i think i bricked my phone ! I to have a virgin mobile canada HTC One S but i can't find the ruu for virging mobile I Tried bell and it didn't work thus screwing up my phone. please pleaase please i need help I just got this phone yesterday.
Click to expand...
Click to collapse
your in the wrong section. If you have the one v from virgin mobile, which code name is primo not ville check here http://www.filefactory.com/f/0eafb9c43276c308/ for ruu and section go here for support http://forum.xda-developers.com/forumdisplay.php?f=1551
or here http://htcruu.com/?dir=Primo
puertoblack2003 said:
your in the wrong section. If you have the one v from virgin mobile, which code name is primo not ville check here http://www.filefactory.com/f/0eafb9c43276c308/ for ruu and section go here for support http://forum.xda-developers.com/forumdisplay.php?f=1551
or here http://htcruu.com/?dir=Primo
Click to expand...
Click to collapse
no please help me. I am positive it is a One S I bought it yesterday from Virgin mobile in Canada. It says one s on the box it doesn't have the hump the one v has on the bottom. I am totally lost and don't know what to do The Bell mobility ruu didn't work for it and it seems like a virgin mobile ruu is none existant
lilsammy11 said:
no please help me. I am positive it is a One S I bought it yesterday from Virgin mobile in Canada. It says one s on the box it doesn't have the hump the one v has on the bottom. I am totally lost and don't know what to do The Bell mobility ruu didn't work for it and it seems like a virgin mobile ruu is none existant
Click to expand...
Click to collapse
Does the your computer recognize the one s
Sent from my Galaxy Nexus using xda premium
lilsammy11 said:
no please help me. I am positive it is a One S I bought it yesterday from Virgin mobile in Canada. It says one s on the box it doesn't have the hump the one v has on the bottom. I am totally lost and don't know what to do The Bell mobility ruu didn't work for it and it seems like a virgin mobile ruu is none existant
Click to expand...
Click to collapse
don't know what to tell you if you got it from virgin mobile i just checked there site http://www.virginmobileusa.com/shop/cell-phones/android-phones/ and they selll the V series. did you buy it form there store/site ? or second hand?
soljafree said:
Does the your computer recognize the one s
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes I think It does because I've tried to use the bell ruu about 5 times and it'll start but then I'll get error 155 a little while into it
puertoblack2003 said:
don't know what to tell you if you got it from virgin mobile i just checked there site http://www.virginmobileusa.com/shop/cell-phones/android-phones/ and they selll the V series. did you buy it form there store/site ? or second hand?
Click to expand...
Click to collapse
Try virginmobile.ca . But yes I just wanted to say I really appreciate you guys's help
lilsammy11 said:
Yes I think It does because I've tried to use the bell ruu about 5 times and it'll start but then I'll get error 155 a little while into it
Try virginmobile.ca . But yes I just wanted to say I really appreciate you guys's help
Click to expand...
Click to collapse
ahhhh i see. ok man your DONE!! becasue that error 155 means that your bootloader is unlocked. and to flash the ruu you would have to relock. but you said you're brick nothing happens to your device?
puertoblack2003 said:
ahhhh i see. ok man your DONE!! becasue that error 155 means that your bootloader is unlocked. and to flash the ruu you would have to relock. but you said you're brick nothing happens to your device?
Click to expand...
Click to collapse
ohhhhh that makes sense, and I think I'm bricked. I'm pretty sure I can run adb commands though. maybe I should try oem lock again command again? this is exactly what the top says
***TAMPERED***
***RELOCKED***
*** Security Warning***
I should point out that when I start the ruu the screen actually goes to a black screen with "htc" on it and that's it. and I tried to lock it again via abd and it says its already locked
---------- Post added at 05:27 AM ---------- Previous post was at 05:15 AM ----------
Ok I should also say that when ever I restart phone it goes right into bootloader. I'm guessing because ruu erased everything ? should i maybe unlock boot loader, root, download stock rom and then try rue again?
lilsammy11 said:
ohhhhh that makes sense, and I think I'm bricked. I'm pretty sure I can run adb commands though. maybe I should try oem lock again command again? this is exactly what the top says
***TAMPERED***
***RELOCKED***
*** Security Warning***
I should point out that when I start the ruu the screen actually goes to a black screen with "htc" on it and that's it. and I tried to lock it again via abd and it says its already locked
---------- Post added at 05:27 AM ---------- Previous post was at 05:15 AM ----------
Ok I should also say that when ever I restart phone it goes right into bootloader. I'm guessing because ruu erased everything ? should i maybe unlock boot loader, root, download stock rom and then try rue again?
Click to expand...
Click to collapse
It it says relocked and its not OEM software on there that's y u keep rebooting into boot loader had that happen on a vivid I had. Try reflashing the ruu
Sent from my Galaxy Nexus using xda premium
Man, I never read anything good anywhere in these forums lol. This phone is so awesome as is, I really don't think it is worth the trouble unlocking and rooting and all. Maybe it is cause only the bad gets posted but there seems to be a lot of it. This phone is definitely meant for the normal person who cares nothing about flashing it seems. I would love to be able to just root it for root-required apps, themes and Volume wake and/or slide to wake but it seems to be more trouble than it's worth.
Cyanogenmod 10 makes this phone 10 times the awesome.
soljafree said:
It it says relocked and its not OEM software on there that's y u keep rebooting into boot loader had that happen on a vivid I had. Try reflashing the ruu
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry I don't quite understand, should I try to getting stock back ? Or just continue to try and get the ruu to work ?
LibertyMonger said:
Man, I never read anything good anywhere in these forums lol. This phone is so awesome as is, I really don't think it is worth the trouble unlocking and rooting and all. Maybe it is cause only the bad gets posted but there seems to be a lot of it. This phone is definitely meant for the normal person who cares nothing about flashing it seems. I would love to be able to just root it for root-required apps, themes and Volume wake and/or slide to wake but it seems to be more trouble than it's worth.
Click to expand...
Click to collapse
Yea I found that out to late, I actually screwed up the phone and somehow saved myself by getting on CM10 then I realized how much I love stock and wanted to go back and now i'm here stuck on bootloader -.-
lilsammy11 said:
Sorry I don't quite understand, should I try to getting stock back ? Or just continue to try and get the ruu to work ?
Yea I found that out to late, I actually screwed up the phone and somehow saved myself by getting on CM10 then I realized how much I love stock and wanted to go back and now i'm here stuck on bootloader -.-
Click to expand...
Click to collapse
Unlock your phone again. Change your CID to HTC__001. Then run an unbranded RUU.
Sent from my locked, tampered ville
I recently got the One X because I became to impatient for the One X+.
After flashing cm10 on it I decided to try and flash back to stock to see if i could return it to ATT because i was within 14 days.
I accidentally bricked my phone by deleting my system from the recovery and now I cant boot into recovery.
It turns on but goes as far as the "HTC quietly brilliant 'this build is for development purposes...'" screen and stops.
I can turn the phone off and on but it gets stuck at this screen.
I've tried button combos to get into recovery and I've tried adb and the one x tool kit.
I've also tried the recovery from the RUU OTA update but no dice.
Any way to fix this?
Ectosock said:
I recently got the One X because I became to impatient for the One X+.
After flashing cm10 on it I decided to try and flash back to stock to see if i could return it to ATT because i was within 14 days.
I accidentally bricked my phone by deleting my system from the recovery and now I cant boot into recovery.
It turns on but goes as far as the "HTC quietly brilliant 'this build is for development purposes...'" screen and stops.
I can turn the phone off and on but it gets stuck at this screen.
I've tried button combos to get into recovery and I've tried adb and the one x tool kit.
I've also tried the recovery from the RUU OTA update but no dice.
Any way to fix this?
Click to expand...
Click to collapse
Which ruu were you using?
Did you relock your boot loader before running ruu?
Sent from my One X using xda app-developers app
Myrder said:
Which ruu were you using?
Did you relock your boot loader before running ruu?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I used "htc_one_x_RUU_2.20.502.7_att_us_08022012" to revert back to stock because i was originally on 2.20.
I did not relock my boot loader before running RUU.
Ectosock said:
I used "htc_one_x_RUU_2.20.502.7_att_us_08022012" to revert back to stock because i was originally on 2.20.
I did not relock my boot loader before running RUU.
Click to expand...
Click to collapse
There is your problem.
Fastboot oem lock
Type that into your fastboot cmd window to ruu
Sent from my One X using xda app-developers app
Myrder said:
There is your problem.
Fastboot oem lock
Type that into your fastboot cmd window to ruu
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
still no dice
error: device not found or < waiting for device >
One thing though is the phone shows up in my device manager as Android but is an unknown and does not have the drivers.
I have the usb drivers, and android SDK installed so I dont know what drivers it is missing.
Okay I can get into the bootloader but im still getting no ADB connection
[EDIT]
from the bootloader i went into fastboot USB and relocked the bootloader
RUU is running!
Ectosock said:
Okay I can get into the bootloader but im still getting no ADB connection
[EDIT]
from the bootloader i went into fastboot USB and relocked the bootloader
RUU is running!
Click to expand...
Click to collapse
Glad you're back up and running.
I wonder if att will even take back his phone because of the relocked status, why do you want the one x + so much? You just said you couldn't wait so you tampered with it and changed your mind, but I mean the one x + is only a second faster.. you can just overclock HTC one x anyways. But I'm glad you phone is back.
Keep the Xl.
WR
Sent from my HTC One X
WhatTheAndroid? said:
I wonder if att will even take back his phone because of the relocked status, why do you want the one x + so much? You just said you couldn't wait so you tampered with it and changed your mind, but I mean the one x + is only a second faster.. you can just overclock HTC one x anyways. But I'm glad you phone is back.
Click to expand...
Click to collapse
WarRaven said:
Keep the Xl.
WR
Sent from my HTC One X
Click to expand...
Click to collapse
64gb plus better battery is enough for me to switch.
Also can the store employees actually tell if it was bootloader tampered? The last time I traded in my stock flashed Samsung Captivate for return all they did was a factory reset and took it back.
Though, better battery life is questionable.
WR
Sent from my HTC One X
They can just go into fastboot if they wanted to and just deny your return. I doubt they will do that. Although it would suck if the phone malfunctions on the next person and he returns it back to att and I guess that would be suspicious but I think your fine. I guess more space is nice on a phone but I don't think I have used that much space on my laptop haha, mabye 50 gigs of bloatware and some music and some fps games. I was just wondering why the switch. Oh and did the ruu go as planned? Oh and also if you decide to get insurance for your phone you should think about squaretrade...they protect against a lot..drops spills..and if you factory reset to stock Rom they will fix it even though you may have rooted..and they will pay you the no commitment price if they can't fix it.(drops,spills,etc)
Here in Los Angeles and surrounding cities the ATT reps are now trained to get into the boot loader to check for a tampered and unlocked device. A few months ago they were not but many devices have come back where someone screwed it up and returned it.
WhatTheAndroid? said:
They can just go into fastboot if they wanted to and just deny your return. I doubt they will do that. Although it would suck if the phone malfunctions on the next person and he returns it back to att and I guess that would be suspicious but I think your fine. I guess more space is nice on a phone but I don't think I have used that much space on my laptop haha, mabye 50 gigs of bloatware and some music and some fps games. I was just wondering why the switch. Oh and did the ruu go as planned? Oh and also if you decide to get insurance for your phone you should think about squaretrade...they protect against a lot..drops spills..and if you factory reset to stock Rom they will fix it even though you may have rooted..and they will pay you the no commitment price if they can't fix it.(drops,spills,etc)
Click to expand...
Click to collapse
The RUU worked perfectly and I returned it with no hassle; they didn't even factory reset it in front of me.
I now have the One X+ and I'm glad i switched. It runs so well I don't think I'll need a custom rom for a while.
Hi, everyone
Yesterday I tried to root my HTC ONE X. Unfortunately, the phone got stuck in TWRP. I haven't used this recovery before but the touch didn't work and neither did the keys. When I pushed the power button appeared a screen saying swipe to unlock but it won't work either. I'm not completely sure how I got rid of TWRP screen and relocked the phone now it is stuck in fastboot mode. What's more I can't find the proper version of the RUU, my phone is 3.18.401.1 and CID is 032. And like it wasn't bad enough now my battery is low and I can't do anything neither unlock it again, nor install the proper RUU(which I can't find anyway)
funh0use said:
Hi, everyone
Yesterday I tried to root my HTC ONE X. Unfortunately, the phone got stuck in TWRP. I haven't used this recovery before but the touch didn't work and neither did the keys. When I pushed the power button appeared a screen saying swipe to unlock but it won't work either. I'm not completely sure how I got rid of TWRP screen and relocked the phone now it is stuck in fastboot mode. What's more I can't find the proper version of the RUU, my phone is 3.18.401.1 and CID is 032. And like it wasn't bad enough now my battery is low and I can't do anything neither unlock it again, nor install the proper RUU(which I can't find anyway)
Click to expand...
Click to collapse
Do you have the the Evita?
Sent from my Carbon-ize Evita using xda-developers app
No, it's the endeavour
No wonder. Wrong thread dude. At the top, type in HTC one x. And do not click on AT&T.
Sent from my Carbon-ize Evita using xda-developers app
funh0use said:
No, it's the endeavour
Click to expand...
Click to collapse
Ouch, be thankful it didn't perma brick your phone
Sent from my HTC One X using xda premium