Database Info

How can I get back to the stock rom in AT&T HTC One X

Hello every one,
since HOX from AT&T was sim locked I thought maybe one of the customroms have the ability to unlock the sim but non of them does that.
So now I want to go back to the original "Stock rom" that the HOX from AT&T came with if that possible and how?
I would really appreciate the help.
thanks a lot in advance.

Well unlocking sim has nothing to do with any rom whatsoever.
There are several threads already covering this topic of going back to stock with an RUU
Sent from my HTC One X using Tapatalk 2

Pirateghost said:
Well unlocking sim has nothing to do with any rom whatsoever.
There are several threads already covering this topic of going back to stock with an RUU
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Thanks, but can you guide me to one of these threads related the the HOX, because I was looking for one but I seem not to find them, Sorry

shakash3obd said:
Thanks, but can you guide me to one of these threads related the the HOX, because I was looking for one but I seem not to find them, Sorry
Click to expand...
Click to collapse
Download RUU
Plug phone in
Relock bootloader
Run RUU.exe
That's pretty much it. Its not rocket science.
Sent from my HTC One X using Tapatalk 2

Pirateghost said:
Download RUU
Plug phone in
Relock bootloader
Run RUU.exe
That's pretty much it. Its not rocket science.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I know it's not rocket science, but even before I created this thread, I knew that I need to do what you just said but my problems were the following:
When I was trying to relock the bootloader using the windows command line, I got the following message
< waiting for device >
and that stayed there forever, I mean I was waiting for 2 hours just to make sure wither something working or not but it wasn't doing anything.
I got the previous message when I typed the following command
fastboot oem lock
-------
I thought maybe I need to run the RUU first, then I should relock the bootloader but even doing that ended up with error.
By the way, the RUU I used is
RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17.32.09.12_10.86.32.08L_release_262092_signed
and I am currently downloading
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
and I will see if this one works or not.
I hope you can see that I didn't post this thread without doing some search first but in fact it was the time to ask for help so it is not laziness.
Thanks

waiting for device indicates it doesnt see your phone. are you in fastboot USB when you run the command?
do you have FAST BOOT disabled in the OS (settings, power)
there are a couple of tutorials already available on this exact subject...not sure what it is you are looking for at this point, but it sounds like you need to get your computer to see the device
there is zero need to wait 2 hours for fastboot to show up on computer, it should happen immediately assuming you are actually in FASTBOOT USB mode
remember UNLOCKING the phone with HTCDEV?
you pretty much follow those guidelines to get
fastboot oem lock
to work
then you can run the RUU, any RUU made for your device (CINGULAR RUU is correct)

Help! Desire problem, won't do anything anymore

Hi guys, yesterday i tried to root my desire hd and flash a rom called icecoldsandwich 8.5, i started my phone and it got stuck at the bootlogo from ics. Then i think i deleted it from my sd card and now i can't do anything with my phone. i can enter the boot menu but nothing more.. if i select recovery, i get a red exclamation mark. I hope it can be fixed
thanx

Moved to General Q&A.

just download a ruu that is only for your device but be careful ( branded ones and unbranded)
then just put it in fastboot via bootloader and flash it and it will boot up
Sent from my HTC HD2 using Tapatalk 2

gesange said:
just download a ruu that is only for your device but be careful ( branded ones and unbranded)
then just put it in fastboot via bootloader and flash it and it will boot up
Sent from my HTC HD2 using Tapatalk 2
Click to expand...
Click to collapse
If you read what they posted, they cannot get to the boot menu. I have a RUU program designed to run remotely from my computer over USB that works wonders if I ever have a problem. I could find the stock .img for your phone and send you the program where you would just plug your phone in over USB, run the program, locate your RUU file (which would be included) and your done. Should be back to normal, worked for me when I accidentally bootlooped. PM me for more info. This will require you to re-root your phone.

nicotje123 said:
i can enter the boot menu but nothing more..
thanx
Click to expand...
Click to collapse
Looks like he CAN enter boot menu.... maybe you should read again as well.

snodrog742 said:
Looks like he CAN enter boot menu.... maybe you should read again as well.
Click to expand...
Click to collapse
Sorry, I'm running on little sleep right now and must have missed that. Thanks.

TekGadgt said:
Sorry, I'm running on little sleep right now and must have missed that. Thanks.
Click to expand...
Click to collapse
No worries. Sorry for bit rude response. Hopefully can get him fixed either way.

[Q] Bricked Phone Help Please

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.

[Q] Is there a way to completely wipe HTC One XL?

Ok... so, I'll admit it, I messed up my One X. Was trying to put CM10 on it, got stuck on the blue, circular boot screen. Tried several fixes from the forums, but nothing worked. One attempted fix even ended up writing over TWRP. Now all I can get is HTC boot screen (complete with red wording beneath) and occasionally the CM10 screen. The fastboot screen says "tampered" and "unlocked".
Here's my situation. AT&T is sending another phone. I have to send this one back to them, and I just want to make sure that they can't figure out I was trying to install a third-party ROM. Is there a way to completely wipe the device altogether so that I just won't even try to boot?
If not, I'll just take my chances that they don't know what to look for besides water/physical damage and won't charge me full price for the replacement.
Any help is appreciated.

Your device is in a completely fixable state but ok...if u want to make it so your device doesn't turn on at all flash a Rom called ice cold jelly ...if youother wise the best you can do is have it say relocked and they would know you unlocked the bootloader...

don't flash ICJ, just relock bootloader and ruu.
if you have no physical damage why are you getting a replacement phone?

Did you flash boot.img?
And how about you not ask how to defraud att because you don't know how to flash and fix a botched flash.

schumachermp said:
Ok... so, I'll admit it, I messed up my One X. Was trying to put CM10 on it, got stuck on the blue, circular boot screen. Tried several fixes from the forums, but nothing worked. One attempted fix even ended up writing over TWRP. Now all I can get is HTC boot screen (complete with red wording beneath) and occasionally the CM10 screen. The fastboot screen says "tampered" and "unlocked".
Here's my situation. AT&T is sending another phone. I have to send this one back to them, and I just want to make sure that they can't figure out I was trying to install a third-party ROM. Is there a way to completely wipe the device altogether so that I just won't even try to boot?
If not, I'll just take my chances that they don't know what to look for besides water/physical damage and won't charge me full price for the replacement.
Any help is appreciated.
Click to expand...
Click to collapse
... and this is why we can't have nice things. Thanks, guy.

All I can think is, at least he did not throw it under his car.
It can be salvaged, where as other clown just destroyed it for nothing.
WR
Sent by WR's One XL

omario8484 said:
Your device is in a completely fixable state but ok...if u want to make it so your device doesn't turn on at all flash a Rom called ice cold jelly ...if youother wise the best you can do is have it say relocked and they would know you unlocked the bootloader...
Click to expand...
Click to collapse
Brother, if you can tell me how to fix this thing, I am all ears. I don't want to replace it, but after trying so many different ways to fix it from the forums I just kind of gave up.
If you have any advice, I'd love to hear it!
Thanks for the reply.

schumachermp said:
Brother, if you can tell me how to fix this thing, I am all ears. I don't want to replace it, but after trying so many different ways to fix it from the forums I just kind of gave up.
If you have any advice, I'd love to hear it!
Thanks for the reply.
Click to expand...
Click to collapse
All you had to do is fastboot the boot.img thats inside the zip bro.. Are you familiar with fastboot at all? If not we can walk you through it!
Sent from my One X using Tapatalk 2

InflatedTitan said:
All you had to do is fastboot the boot.img thats inside the zip bro.. Are you familiar with fastboot at all? If not we can walk you through it!
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I did flash boot.img. It just never moved past the CM10 starting animation. And honestly, not super familiar with fastboot three days ago... fairly familiar at this point. But nothing seems to get this thing to work. Please tell me what to do!
(BTW - I only called warranty at the advice of an AT&T employee in the store. I'd love to just fix my phone)

Twrp 2.3.1.0, wipe everything, flash boot.img in fastboot, and flash cm10 and gapps in twrp.

How do I get TWRP back on it?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

schumachermp said:
How do I get TWRP back on it?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Try Goo Manager, go into its settings an select install open recovery script.
WR
Sent by WR's One XL

WarRaven said:
Try Goo Manager, go into its settings an select install open recovery script.
WR
Sent by WR's One XL
Click to expand...
Click to collapse
Ok, great. I've downloaded the TWRP recovery image and the Goo Manager APK... now how do I use Goo Manager on a device that won't boot up?

You can't BC its an app.. Download tarp off the official site, a quick Google search brings it up first shot... Once downloaded, drop the recovery img into your adb and fastboot folder.. Enter fastboot USB on your phone. Now right click on your adb/fastboot folder and choose "open command prompt here"
Once cmd is running, type fastboot flash recovery <---- type in the name of the twrp img you dropped in
Sent from my One X using Tapatalk 2

InflatedTitan said:
You can't BC its an app.. Download tarp off the official site, a quick Google search brings it up first shot... Once downloaded, drop the recovery img into your adb and fastboot folder.. Enter fastboot USB on your phone. Now right click on your adb/fastboot folder and choose "open command prompt here"
Once cmd is running, type fastboot flash recovery <---- type in the name of the twrp img you dropped in
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Woohoo!!! You guys got it going! Running CM10 FTW!
I hope you all don't mind me saying that I FREAKING LOVE YOU ALL. It's true.
Thank you SO much!
Deuces. I'm going to go play with JB.

schumachermp said:
Woohoo!!! You guys got it going! Running CM10 FTW!
I hope you all don't mind me saying that I FREAKING LOVE YOU ALL. It's true.
Thank you SO much!
Deuces. I'm going to go play with JB.
Click to expand...
Click to collapse
I'm happy you got your phone running.

Don't get it all sticky with all that love.

Lol good job bro
Sent from my One X using Tapatalk 2

ECEXCURSION said:
... and this is why we can't have nice things. Thanks, guy.
Click to expand...
Click to collapse
Exactly right! If you screw up your phone, take responsibility for it! Don't make somebody else pay for your failure.
Do you even read before you flash rom's? clear red letters. This could brick your phone or even worst if you dont know what you're doing
Research very much before doing anything, that's how I started

rodpgfx said:
Exactly right! If you screw up your phone, take responsibility for it! Don't make somebody else pay for your failure.
Do you even read before you flash rom's? clear red letters. This could brick your phone or even worst if you dont know what you're doing
Research very much before doing anything, that's how I started
Click to expand...
Click to collapse
Completely agreed. The notion astounds me (and disappoints me also) that the OP was going to send the phone in for a warranty replacement simply because they didn't do the proper research and learning before modding the phone. And when the condition was completely and easily reversible. If the screen comes on with this phone, it can be recovered.

[Q] [Solved] Frequent Signal Drops / RUU Help

So I've read a few things on the forum about signal drops and have tried a few solutions but I wanted to get some additional feedback before I go the ATT:
Just in the past few days, I have had increasingly frequent signal drops. This has become really annoying for me, as it always seems to happen when I am using mobile data or sending a text message. The signal drop is transient and only lasts about 30 seconds before it re-connects to my network. I haven't noticed much correlation with when it actually happens but I have attached a picture just so you all can see how frequent these signal drops are. Happens when phone is asleep or in use. These are the things I have tried:
1) Originally was running KingCobra 1.5 and thought it may have been the ROM so I flashed CM10
2) Flashed radio 2.09 for ATT - this showed no improvement / did not make it worse
3) Wiped cache / Dalvik - no improvement
My next course of action was to go to ATT and get a new SIM card. Is it possible that a faulty SIM over time could cause this? And would replacing the SIM likely help in the experience of this community?
Thanks a lot for the input, and if there is something else I can do that I haven't already tried please let me know!

Faulty SIM is a possibility. Replacing the SIM is a quick, free fix. So its at least good to eliminate as the cause.

redpoint73 said:
Faulty SIM is a possibility. Replacing the SIM is a quick, free fix. So its at least good to eliminate as the cause.
Click to expand...
Click to collapse
Can this sort of thing spontaneously happen? One day the SIM just starts getting derpy?

I've heard of people taking the card tray out and putting a piece of card stock behind their sim to improve contact
Sent from my HTC One XL using xda app-developers app

area51avenger said:
I've heard of people taking the card tray out and putting a piece of card stock behind their sim to improve contact
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Well I got a new SIM from AT&T and I'm still dropping signal. They did say that they just put up LTE towers here where I'm at 2 days ago, which, coincidentally is when I started getting signal drops. I suppose all that is left is for me to RUU? I don't know how to so it should be fun reading up lol

Actually: I made a backup via TWRP before I ever flashed a ROM -- Is there a boot.img of the stock ROM floating around out there that anyone knows about and would this work? That would be a hell of a lot better than having to go through the process of RUU..Or is there any way I could pull it somehow out of the recovery files?
Edit: Could someone enlighten me a little bit on the process of the RUU -- The only thing that is cloudy here is that I am currently running CM10, would I be able to run the executable RUU if I was running a stock odexed/deodexed ROM after re-locking the bootloader? I have looked at this (http://forum.xda-developers.com/showthread.php?t=1814217&highlight=ruu) and the associated guide but this all assumes that I'm already on a stock image right? I've tried doing some reading but I am drawing a blank on the RUU process

TheEmpyre said:
Actually: I made a backup via TWRP before I ever flashed a ROM -- Is there a boot.img of the stock ROM floating around out there that anyone knows about and would this work? That would be a hell of a lot better than having to go through the process of RUU..Or is there any way I could pull it somehow out of the recovery files?
Click to expand...
Click to collapse
This would not be the equivalent of a ruu
Flash a ruu replaces every single file/partition to stock.
Running a backup would just replace system, data, and cache
My opinion would be to ruu, on my previous phone this was the only way to fix data drops of
Sent from my One X using Tapatalk 2

superchilpil said:
This would not be the equivalent of a ruu
Flash a ruu replaces every single file/partition to stock.
Running a backup would just replace system, data, and cache
My opinion would be to ruu, on my previous phone this was the only way to fix data drops of
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I edited my previous post after you posted this but am I able to run an RUU executable if I'm on CM10? Or is this process more complex?

TheEmpyre said:
I edited my previous post after you posted this but am I able to run an RUU executable if I'm on CM10? Or is this process more complex?
Click to expand...
Click to collapse
I had issues with running an ruu actually. Its different with this phone
But you can try backing everything up obviously and running fastboot OEM lock to lock your boot loader
Then put it in hboot not fastboor and hooking it to your computer then running the ruu
It took a few tried to get the program to recognize the phone but it doesn't matter what ROM you are on as long as you are locked
Sent from my One X using Tapatalk 2

superchilpil said:
I had issues with running an ruu actually. Its different with this phone
But you can try backing everything up obviously and running fastboot OEM lock to lock your boot loader
Then put it in hboot not fastboor and hooking it to your computer then running the ruu
It took a few tried to get the program to recognize the phone but it doesn't matter what ROM you are on as long as you are locked
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Ok so to summarize:
1) in bootloader: fastboot oem lock
2) fastboot reboot-bootloader
3) attempt to run the RUU via fastboot USB? I know my computer recognizes my HTC Device if I run "fastboot devices" command
In the case that it totally derps and doesn't recognize what is my recourse? I still have my unlock token bin file which is good, but I wouldn't have an OS to boot into and probably wouldn't be able to flash anything via recovery with a locked bootloader no?
Edit: Forgot that when you unlock bootloader you do it through fastboot with "fastboot flash unlocktoken Unlock_code.bin so ultimately I would be able to re-flash my recovery etc

TheEmpyre said:
Ok so to summarize:
1) in bootloader: fastboot oem lock
2) fastboot reboot-bootloader
3) attempt to run the RUU via fastboot USB? I know my computer recognizes my HTC Device if I run "fastboot devices" command
In the case that it totally derps and doesn't recognize what is my recourse? I still have my unlock token bin file which is good, but I wouldn't have an OS to boot into and probably wouldn't be able to flash anything via recovery with a locked bootloader no?
Click to expand...
Click to collapse
Edit 2, and 3
2) just select boot loader in fast boot
3) attempt to run the RUU via hboot USB
Your recourse would be to unlock again with your unlock token, flash twrp, and either restore a backup or download a stock/rooted ROM and lock and try again
Sent from my One X using Tapatalk 2

superchilpil said:
Edit 2, and 3
2) just select boot loader in fast boot
3) attempt to run the RUU via hboot USB
Your recourse would be to unlock again with your unlock token and either restore a backup or download a stock/rooted ROM and lock and try again
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Sweet I'm gonna give it a try right now -- thanks a lot for the help! And yes I saved my .bin file

TheEmpyre said:
Sweet I'm gonna give it a try right now -- thanks a lot for the help! And yes I saved my .bin file
Click to expand...
Click to collapse
I missed that part in your post and no problem.
Keep us updated, like I said running a ruu was a pain in the butt with this phone.
Sent from my One X using Tapatalk 2

superchilpil said:
I missed that part in your post and no problem.
Keep us updated, like I said running a ruu was a pain in the butt with this phone.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Ok I caught this before doing anything, but hboot USB requires a specific driver? I have no hboot USB mode showing on my bootloader once I select bootloader in the bootloader main screen

TheEmpyre said:
Ok I caught this before doing anything, but hboot USB requires a specific driver? I have no hboot USB mode showing on my bootloader once I select bootloader in the bootloader main screen
Click to expand...
Click to collapse
This is my hopeful assumption, but I would hope the ruu.exe would contain the drivers for hboot USB
I personally haven't had to install any drivers
Nothing pops up stating your computer is installing any drivers or searching?
Sent from my One X using Tapatalk 2

superchilpil said:
This is my hopeful assumption, but I would hope the ruu.exe would contain the drivers for hboot USB
I personally haven't had to install any drivers
Nothing pops up stating your computer is installing any drivers or searching?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I haven't executed any files because I noticed that I only have Fastboot USB...once I exit that and select "Bootloader" then nothing happens and I hear the sound from my PC of a disconnecting device -- So basically I'm confused because you said make sure to execute the RUU when I am in "hboot usb" but I only have "fastboot usb" after I click fastboot in the bootloader....hopefully this makes sense
hboot usb == fastboot usb?

What my screen looks like here before and after selecting bootloader with the power button
Sent from my Nexus 10 using Tapatalk 2

TheEmpyre said:
I haven't executed any files because I noticed that I only have Fastboot USB...once I exit that and select "Bootloader" then nothing happens and I hear the sound from my PC of a disconnecting device -- So basically I'm confused because you said make sure to execute the RUU when I am in "hboot usb" but I only have "fastboot usb" after I click fastboot in the bootloader....hopefully this makes sense
hboot usb == fastboot usb?
Click to expand...
Click to collapse
this is where i had issues, but hboot usb =/= fastboot usb
im trying this myself to see how to get it to recognize it
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
alright, in fastboot run fastboot oem rebootRUU
then run the ruu.exe

superchilpil said:
this is where i had issues, but hboot usb =/= fastboot usb
im trying this myself to see how to get it to recognize it
Click to expand...
Click to collapse
Have you ever tried running the RUU in fastboot usb? Because my computer certainly recognizes my device when its in fastboot usb but as soon as i click it off, it no longer registers my device as connected

TheEmpyre said:
Have you ever tried running the RUU in fastboot usb? Because my computer certainly recognizes my device when its in fastboot usb but as soon as i click it off, it no longer registers my device as connected
Click to expand...
Click to collapse
try my method above, ive tried it with fastboot... the ruu just ignores it
That method should work, the ruu should pick it up and wipe it clean