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.
Related
I rooted and unlocked stock RUU (1.73 something). Then I fastboot oem lock the device. So the bootloader is locked. THen I begin to flash 1.85 and the window has been displaying the "Sending" dialougue for half an hour. What should I do now? I think the RUU isn't working.
ce12373 said:
I rooted and unlocked stock RUU (1.73 something). Then I fastboot oem lock the device. So the bootloader is locked. THen I begin to flash 1.85 and the window has been displaying the "Sending" dialougue for half an hour. What should I do now? I think the RUU isn't working.
Click to expand...
Click to collapse
It took forever. I think because of super cid.
gunnyman said:
It took forever. I think because of super cid.
Click to expand...
Click to collapse
Thanks for the reply. I was just flashing, but a power outage hit my computer while the file was "sending". I freaked out, but luckily the phone still works still on 1.73. Are there any things I need to do before the 1.83 that I didn't do before? I'm going to try it again. The taste of custom ROMs is too good to live without (I came from an Atrix (awesome devs))
ce12373 said:
Thanks for the reply. I was just flashing, but a power outage hit my computer while the file was "sending". I freaked out, but luckily the phone still works still on 1.73. Are there any things I need to do before the 1.83 that I didn't do before? I'm going to try it again. The taste of custom ROMs is too good to live without (I came from an Atrix (awesome devs))
Click to expand...
Click to collapse
You might want to flash from a laptop. Losing power is the last thing you want to do during a flash and could potentially brick it if it were to fail.
Sent from my HTC One X using xda premium
Double post
ECEXCURSION said:
You might want to flash from a laptop. Losing power is the last thing you want to do during a flash and could potentially brick it if it were to fail.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah, luckier this time. Finally finished flashing. Took about 2 or three hours. Maybe more. I feel so happy those nervous breaths are finally over! Thanks for all of your time.
It took me 10min to flash, but the whole process took me all day. My goal was achieve root and unlocked status and it was a success.
Guide:
http://forum.xda-developers.com/showpost.php?p=26540652&postcount=117
I checked all the other bricked threads and none have the same problem as me.
My HTC ONE X will not boot and or charge. I cannot get access to the bootloader or recovery.
My HTC ONE X had it's bootloader unlocked via the rogers htc-dev method. I also installed clockwork recovery. It is rooted also but you prob figured that already...
I pulled a bonehead move by flashing the MIUI rom the international one x by changing the update script to flash onto my phone. After it flashed it looked like it worked. When I left recovery and shut the phone off it would not turn back on.
I called AT&T they said they will switch it for me when they get a shipment but I want to keep this phone because the boatloader is unlocked and they might patch the rogers method.
Thanks in advanced.
P.S. I know how to use adb and other tools such as RUU and they did not work.
Have you tried holding the power button for 10 seconds to reset it? You should see the 3 lights below flashing.
Ouch.... Another loss for htc sales
Sent from my HTC One X using xda premium
you cant get to hboot? 0.o
First of all, you should be able to get to H-Boot by holding volume down when turning it on.
Second of all, this is why they lock the bootloader in the first place.
-sassafras
Reply
equlizer said:
Have you tried holding the power button for 10 seconds to reset it? You should see the 3 lights below flashing.
Click to expand...
Click to collapse
No nothing happens even with the charging adapter plugged in.
kevina90 said:
you cant get to hboot? 0.o
Click to expand...
Click to collapse
Nope
sassafras_ said:
First of all, you should be able to get to H-Boot by holding volume down when turning it on.
Second of all, this is why they lock the bootloader in the first place.
-sassafras
Click to expand...
Click to collapse
H-Boot key combo is not working.
I have been flashing roms since the samsung moment, I built and modified roms on my EVO and ported roms from other phones to the EVO. I always had recovery to fall back onto to get my phone booting again. Even when I had the Xperia Play that required a PC to boot recovery I was still able to get the phone to work. This phone is strange that is will not even turn onto H-boot/Bootloader.
jfn0802 said:
H-Boot key combo is not working.
I have been flashing roms since the samsung moment, I built and modified roms on my EVO and ported roms from other phones to the EVO. I always had recovery to fall back onto to get my phone booting again. Even when I had the Xperia Play that required a PC to boot recovery I was still able to get the phone to work. This phone is strange that is will not even turn onto H-boot/Bootloader.
Click to expand...
Click to collapse
I like to play with my phones and this one is so finicky I'm scared to do too much.
I bricked one myself.
gunnyman said:
I like to play with my phones and this one is so finicky I'm scared to do too much.
I bricked one myself.
Click to expand...
Click to collapse
Im glad I have my iPhone to fall back on but it is really annoying that I cannot even get the bootloader to load. I only had it 3 days and already broke it.
Thank God the dude at AT&T cannot get into the bootloader also to see that is was tampered with so they are giving me a replacement.
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
jfn0802 said:
Im glad I have my iPhone to fall back on but it is really annoying that I cannot even get the bootloader to load. I only had it 3 days and already broke it.
Thank God the dude at AT&T cannot get into the bootloader also to see that is was tampered with so they are giving me a replacement.
Click to expand...
Click to collapse
Where do they have them in stock? I need to replace mine (screen issue) and can't find any around here.
powerwagon said:
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
+ 1
Sent from my HTC One X using xda premium
powerwagon said:
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
+2
Honestly, not trying to call you stupid or something, but did you really think it was going to run on this phone when it was meant for another one? The GPU and CPU are completely different...
Anyway, I'm glad AT&T is replacing it for you. Hopefully if someone else bricks the same way then they will be able to get a replacement as well.
so you are smart enough to use adb, an RUU, unlock your bootloader, root, flash roms.......but you aren't smart enough to see the hundreds of posts saying that the international roms don't work on our phones??
lol
Coming from a phone that is virtually unbrickable (Captivate), I'm quite curious about how you managed to get it into this state. What exactly did you flash? Did the package contain both the system image and bootloaders for the tegra3 one x?
Just pull the batte..... oh
jmattp said:
Just pull the batte..... oh
Click to expand...
Click to collapse
+1 for when I drowned my first one and it was stuck in a boot loop. I know it could have been saved if the battery would have been taken out.
Sent from my HTC One X
modest_mandroid said:
Coming from a phone that is virtually unbrickable (Captivate), I'm quite curious about how you managed to get it into this state. What exactly did you flash? Did the package contain both the system image and bootloaders for the tegra3 one x?
Click to expand...
Click to collapse
My EVO was unbrickable too, I flashed a rom that was designed for the international version. It only contained system and other basic rom stuff, nothing that was crazy.
No idea why you wouldn't be able to boot into recovery then. I hope all HTC handsets aren't like this..
Sent from my SGH-I897 using XDA
I went to flash some things...and now it's stuck in the qualcomm download mode? How the hell do I get out of it??
You can't, you're screwed
I had this on my old Sensation, it stands for Qualcomm High Speed USB
Basically what's happened is your phone has lost the drivers for the chip set and needs them re-installed, as far as I'm aware, no-one has managed to find a way to do it.
Hope its still under warranty mate, I think its the only way you'll get it sorted
Sent from my GT-I9100 using xda premium
redrumsilence said:
You can't, you're screwed
I had this on my old Sensation, it stands for Qualcomm High Speed USB
Basically what's happened is your phone has lost the drivers for the chip set and needs them re-installed, as far as I'm aware, no-one has managed to find a way to do it.
Hope its still under warranty mate, I think its the only way you'll get it sorted
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
You're kidding, right? Well I installed the drivers for that, and it's now recognized by my computer, but there's nothing I can do? At all?
What exactly did you do to cause this?
Sent from my HTC One X using Tapatalk 2
random1204 said:
You're kidding, right? Well I installed the drivers for that, and it's now recognized by my computer, but there's nothing I can do? At all?
Click to expand...
Click to collapse
When it happened to me, I found the QHSUSB drivers and installed them, my computer recognised my Sensation, but nothing else.
I scoured XDA, Google, all sorts, I couldn't find anything, I just sent mine in under insurance and got a new one
Sent from my GT-I9100 using xda premium
Your not screwed. Pmed
Sent from my HTC One X using xda premium
Galaxy s3 Tmobile in same state
18th.abn said:
Your not screwed. Pmed
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Hey do you have any info on this mode? I would love to have some kind of info as to a course of action, even though this is for a different model...
18th.abn said:
Your not screwed. Pmed
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
i to am stuck in this mode. i flashed clockwork recovery (gsm) on my at&t one x thinking it was for our phone since it wasnt there the last time i checked. after i did a reboot the phone never came back on.
rob219 said:
i to am stuck in this mode. i flashed clockwork recovery (gsm) on my at&t one x thinking it was for our phone since it wasnt there the last time i checked. after i did a reboot the phone never came back on.
Click to expand...
Click to collapse
Is it completely dead and unresponsive? Just flashing the wrong recovery shouldn't kill your phone. I've done it myself a couple of times by accident, and fixing it was just a matter of flashing the right one.
Sounds like you actually flashed the wrong rom. Doing that can kill your bootloader, which will put you in QHSUSB mode. There is a way out that's been discussed, but I can't find it at the moment. It involves pushing a new hboot onto your phone and I believe requires Linux.
iElvis said:
Is it completely dead and unresponsive? Just flashing the wrong recovery shouldn't kill your phone. I've done it myself a couple of times by accident, and fixing it was just a matter of flashing the right one.
Sounds like you actually flashed the wrong rom. Doing that can kill your bootloader, which will put you in QHSUSB mode. There is a way out that's been discussed, but I can't find it at the moment. It involves pushing a new hboot onto your phone and I believe requires Linux.
Click to expand...
Click to collapse
it wasnt a rom. it was definetly the clockwork recovery in rom manager. it said gsm next to htc one x and its a new one so i was stupid enough to flash it. i did a reboot and it was dead. i already talk to at&t about it and there sending me a new one.
rob219 said:
it wasnt a rom. it was definetly the clockwork recovery in rom manager. it said gsm next to htc one x and its a new one so i was stupid enough to flash it. i did a reboot and it was dead. i already talk to at&t about it and there sending me a new one.
Click to expand...
Click to collapse
That's interesting, because I did (almost) the same thing. When I first unlocked my HOX, I installed ROM Manager and accidentally flashed the Samsung GSII recovery. I was able to fix it just by going back to bootloader and adb flashing the correct version.
iElvis said:
That's interesting, because I did (almost) the same thing. When I first unlocked my HOX, I installed ROM Manager and accidentally flashed the Samsung GSII recovery. I was able to fix it just by going back to bootloader and adb flashing the correct version.
Click to expand...
Click to collapse
just found out the one x international recovery flashes on the partition that on our phones is the boot loader partition. could be fixed inside of linux, but i didnt get into how.
I had the same problem with the QHSUSB Download it turns out my phone had a really drained battery so how I managed to fix it was had it plugged into my computer and let the lights flash until i got a solid amber light. after about 15 minutes, I turned it on and it worked fine!
on my tablet i pressed for a really long time the power button and then it started up
it enters almos allways in qualcomm download mode when the battery is depleated.
you revived a dead thread to say something about your tablet?
I'm going to go revive some too now
Sent from my HTC One XL using Tapatalk 2
DvineLord said:
you revived a dead thread to say something about your tablet?
Click to expand...
Click to collapse
Someone can find my reply useful, compared to you and the other troll that did not say anything useful.
Same situation for me .. i flashed TWRP, backedup my rom, flashed a new rom and reboot. black screen, no light, unresponsive .. this same message shows up on my windows machine "QHUSB_LOAD no driver found"
atombone said:
Same situation for me .. i flashed TWRP, backedup my rom, flashed a new rom and reboot. black screen, no light, unresponsive .. this same message shows up on my windows machine "QHUSB_LOAD no driver found"
Click to expand...
Click to collapse
I'm guessing you flashed an international ROM on your One XL. That will do it.
iElvis said:
I'm guessing you flashed an international ROM on your One XL. That will do it.
Click to expand...
Click to collapse
Its a One X (ATT) but your probably right. I downloaded it from ONEXROOT.com. just strange to me that because i flashed a rom it screws the bootloader. ugh... sucks
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.
So My phone is constantly freezing and rebooting in apps every 5-15 minutes and I am going to try going back to stock and seeing if this occurs. My question is do i have to wipe my current rom? Or do i only have to fastboot oem lock and run ruu? Help would be appreciated. Think it is getting worse..
WhatTheAndroid? said:
So My phone is constantly freezing and rebooting in apps every 5-15 minutes and I am going to try going back to stock and seeing if this occurs. My question is do i have to wipe my current rom? Or do i only have to fastboot oem lock and run ruu? Help would be appreciated.
Click to expand...
Click to collapse
Yes, just run fastbook oem lock and then run the ruu. Make sure that you have the latest drivers from HTC (use htc sync if you can). Good luck!
For ruu grab the appropriate one .... Relock your bl like you Saud and run the ruu from you bl mode ...no need to wipe anything the ruu will do that for you
Skeeterdrums said:
Yes, just run fastbook oem lock and then run the ruu. Make sure that you have the latest drivers from HTC (use htc sync if you can). Good luck!
Click to expand...
Click to collapse
and i run the command in fastboot on my htc one x? ive did it once before.
WhatTheAndroid? said:
and i run the command in fastboot on my htc one x? ive did it once before.
Click to expand...
Click to collapse
Yessir head over to gunnymans thread in general forum to clear any confusion that remains
phone is going haywire.....Not being detected..rebooting every second..cant even get into an app...got into twrp and going to charge it ill 70 and restore to a better backup then hopefully ruu...thanks for the help
WhatTheAndroid? said:
phone is going haywire.....Not being detected..rebooting every second..cant even get into an app...got into twrp and going to charge it ill 70 and restore to a better backup then hopefully ruu...thanks for the help
Click to expand...
Click to collapse
Usually, the phone doesn't get detected if the drivers aren't up to date. Is it rebooting even from bootloader? You should be able to install everything from there, hopefully meaning restarts aren't an issue.
HTC One X using CleanRom 5.1 with BeastKernel 4.4
Skeeterdrums said:
Usually, the phone doesn't get detected if the drivers aren't up to date. Is it rebooting even from bootloader? You should be able to install everything from there, hopefully meaning restarts aren't an issue.
HTC One X using CleanRom 5.1 with BeastKernel 4.4
Click to expand...
Click to collapse
finally got it recognized and successfully ruu'd.It was very odd, like the phone was progressively getting worse for some reason.i am not not getting rebooted on stock rooted so it had to do something with my settings on the rom..like i said i under clocked and overclocked it, hot rebooted it, wiped cashe and dalvik...nothing was working and it finally just kept rebooting and freezing at home screen..Maybe a bad successful flash lol.. im not really sure.. or flashing over a bad flash had something to do with it..I might wait till jellybean comes out.
Have you tried to simply factory reset?
i personally like ruu'ing. i should do the same soon just to clean house. in the end it's pretty easy to get fluent on this phone.
i would say immediately after unlocking bootloader to ruu. i noticed some differences in the 1.85 to 2.20 ota vs the 2.20 ruu. it will also clean up any mess that might of been left on the phone. im also pretty ocpd =)
also htc sync imo is useless, i just use the standalone htc drivers haven't had any issues with them.
OP... What rom/kernel combo were you running?
Only time I've seen another phone go that nuts is when my cousin flashed rohans kernel in viper lol
Sent from my One X using Tapatalk 2
InflatedTitan said:
OP... What rom/kernel combo were you running?
Only time I've seen another phone go that nuts is when my cousin flashed rohans kernel in viper lol
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Viper and beastmode. My phone was going nuts....froze at the start screen 3 times and reset it self into a bootloop, then went back to freezing when start screen appeared..one of the times all I could see is the notification bar but I couldn't drag it Down. Lots of other crazy stuff happened on it as well...to much to tell. But I heard cleanrom is pretty stable, do I have to wipe stock rooted(no custom Rom yet) trying to find a good one and do I have to flash boot IMG if I'm on 1.14 or is it Included in the cleanrom installer? Might try elemental with cleanrom..see how that works out.