Root [International Tegra 3] HTC One X will not enter recovery mode

The failed usb master mode error when you enter the bootloader is because the cable is connected. Remove the cable and try all things again

When in recovery your device will no longer be recognised even though you have drivers installed

1) On your Windows desktop, Go to your Control Panel then Device Manager.
2) You should see Android Phone under Other Devices with a Yellow ! mark on it.
3) Right click on it and choose "Update Driver Software"
4) Choose "Browse my computer", then "Let me pick from a list."
5) If you see categories, select "Android Device", then select "Android ADB Interface".
6) The driver will install and you can now run the update with ADB.

Welcome to the forums!

Did you get the recovery from here?

http://www.modaco.com/topic/353009-...ch-recovery-for-the-htc-one-x-stock-download/

Because if so, that's very old and as you can see from that thread, is prone to the problems you describe.

I don't recall if they ever got CWM working properly for the One X.

You may be better off with TWRP, it's what I used with mine.

http://teamw.in/project/twrp2

Unless you need CWM for some reason?

Adb needs a different driver from fastboot, I wouldn't worry about that part at the moment.

I may be out for the rest of the day, that ought to get us started.

See above.

And if it's that, don't flash a kernel if it came from the same place advising you to use that recovery.

Glad you're making progress!

You want to proceed very cautiously ok.

Think of your kernel like glue and here's where it sits logically -

(hardware) <-> (kernel) <-> (rest of operating system, apps, etc etc, SOFTWARE)

Roms for your phone come in two types - Sense and Senseless (the latter being CM, AOSP, etc etc).

That link contains both and you never want to mix up the two types.

~~~~~~~~~~~~~~

As for the rest - I question the thing about wifi not working - it did for me on 4.2.2 so I really wonder if you simply got a bad download/install somewhere along the way.

If I were in your shoes, I would start by installing a good Sense rom and see if that fixes the problem.

You mentioned you have the One X, I would go with - http://forum.xda-developers.com/showthread.php?t=2087443

But if you have the One X+ then you want - http://forum.xda-developers.com/showthread.php?t=2122390

See if that helps.

If things improve but you still have trouble, you can re-install your stock kernel - take the rom image (zip file from whichever link), unzip on your PC and extract the file: boot.img

Place that right in the folder with your fastboot. Get to fastboot usb mode and then say on your PC -

fastboot flash boot boot.img

^^ Make a note of that, you're going to follow that general process for flashing kernels, unless told otherwise by a specific kernel dev.

Viper typically uses the stock kernel.

However, without x-ray vision, I wouldn't predict that it's the kernel or some other part of the rom that broke your wifi. What fixes one guy might break the next, so I say go for the whole solution.

If you want to try a CM rom, no problem - but it's best to anticipate that you'll always want to do that steo above to ensure that you really did get the kernel flashed.

If you move further and get s-off you never need to worry about that.

If you bootloop after a rom install, that's your solution, usually the bootloop is caused by a boot.img flash failure (and btw - the boot.img contains the kernel in a rom).

And before you do anything else -

Go into TWRP and do a nandroid backup.

That's the backup button, accept the defaults of (boot, system, data) and don't overthink that part - just do.

Ok to compress the backup, ok to rename it if you want - ok to leave both as is.

But - rule one for you right now - never flash anything without making a nandroid backup of where you were at when the flashing starting. It's your lifeline.

Nandroid backups can suck up storage quickly on your phone - no big deal - copy to your PC (drag and drop folder under TWRP) and then delete from phone if needed, to save space, AFTER the successful flash of whatever.

^ There - flash installation 101 plus the evening course.

Above all - anything goes wrong - don't panic. Panic is the mind killer and leads to more mistakes. Without panic, most everything is quickly fixable by retracing steps, asking for help.

We've all been where you are, you're among friends.

Yep - in the sdk-tools folder, there's an md5 checksum utility - use it on the rom zip, compare the value to the one listed on the download site. Exact details on the tool are in my Mini-SDK post, you have the link.

If the numbers are different, you have a bad download, try again.

That's the right size, here's the md5 sum -

MD5 Sum: 912392b2a6c0bf0289264e1cbff774d2

OK, probably found the issue -

Have to read the first several posts there carefully.

You have to flash a TWRP modification to install that version of the rom, and they have their own way for flashing the kernel.

Check it out.

Sorry, I didn't think to check - I'm on another HTC at the moment with a modified TWRP, so that sort of thing is no big deal.

Hello Matthew,
I had tried to root my phone (HTC One X +) with CM 10.2, but I ended up in a boot loop, will you be able to help me with this by providing the links of the boot.img, recovery.img and the ROM that you are using. if you can give me a step by step instructions It will be very helpful.

Rakesh

rake8h said:

Hello Matthew,
I had tried to root my phone (HTC One X +) with CM 10.2, but I ended up in a boot loop, will you be able to help me with this by providing the links of the boot.img, recovery.img and the ROM that you are using. if you can give me a step by step instructions It will be very helpful.

Rakesh

Click to expand...

Take the CM rom zip you used to your pc, and extract the boot.img file from it - place into same folder as fastboot on your pc.

Put phone in FASTBOOT USB mode and in command window where fastboot is say -

fastboot flash boot boot.img

After it says OKAY -

fastboot reboot

EarlyMon said:

Take the CM rom zip you used to your pc, and extract the boot.img file from it - place into same folder as fastboot on your pc.

Put phone in FASTBOOT USB mode and in command window where fastboot is say -

fastboot flash boot boot.img

After it says OKAY -

fastboot reboot

Click to expand...

Hello EarlyMon,
I had done this already, I had took the boot.img from the CM rom zip into the pc and then I did fastboot flash boot boot.img from cmd, after this the problem started, I was stuck at htc quietly brilliant. I'm not sure what I should do now.

Rakesh

OK, so I can see you're already pretty smart at this (well done my friend), so can you enter into recovery and see your mounted file systems?

If not, let's try the 2.8.4 TWRP that worked for @Matthew Smith from -

http://dl.twrp.me/enrc2b/

That's for the international One X+, not the USA AT&T version.

Please fastboot flash that, see if you can get into recovery from there.

Please also provide the information from the top of your FASTBOOT screen - s-on status, bootloader version, etc etc.

Also Rakesh, I hate to frustrate you but we have a time difference so I may not be able to help very long tonight (it's getting late for me) but please be patient, I won't abandon you - just maybe we have to continue tomorrow as well ok.

Hello EarlyMon,
I am really glad that you are helping me out with this, by the time you were replying me I had surfed and found about TWRP and now have Flashed twrp-2.8.6.0-enrc2b.img through Fastboot. Now im inside the TWRP SCREEN.
What should I do next?
Regards Rakesh

Does it let you see any nandroid backups you made?

Can you see your last rom zip installer file from it?

I didn't take any backup, but yes I can see the cm-10.2.1-enrc2b.zip file that I used.

Using fastboot I also found a way to copy files to the phone's storage.
What should I do next?