• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [AT&T] New rooters discussion

chief113 said:
Yes I did restart.
Click to expand...

Hmm... Try installing HTC sync as well? It's not very good for anything but it should put the drivers on your computer again. Then plug it in, go to the USB icon in your notification tray, click it, set it to disk drive, and make sure USB debugging is enabled, and look to see if you can see it in your file browser on your computer
 
Sorry if this is starting the thread all over, but I'm not technically savvy at all... however, after reading about the jellybean update, hearing about it's advantages over ICS, and seeing that apparently AT&T is not going to accommodate it's HTC One X users by allowing us to have it, I am starting to feel like I should take matters into my own hands. Like I started out saying though, I'm not technically savvy - I don't know what "flashing a kernel" is and what "aokp" means. So, I am willing to take the time to read the websites about these things, but I saw rumors floating around the AT&T forums that there's some kind of security update coming that will prevent rooting so I'm trying to learn quick before I get stuck (if that's possible that AT&T could somehow prevent rooting).
Any advice on how to do it without having to know a bunch of technical jargon and what to do to keep the phone as close to stock as possible but still get the JB update?
 
mjvala780 said:
Sorry if this is starting the thread all over, but I'm not technically savvy at all... however, after reading about the jellybean update, hearing about it's advantages over ICS, and seeing that apparently AT&T is not going to accommodate it's HTC One X users by allowing us to have it, I am starting to feel like I should take matters into my own hands. Like I started out saying though, I'm not technically savvy - I don't know what "flashing a kernel" is and what "aokp" means. So, I am willing to take the time to read the websites about these things, but I saw rumors floating around the AT&T forums that there's some kind of security update coming that will prevent rooting so I'm trying to learn quick before I get stuck (if that's possible that AT&T could somehow prevent rooting).
Any advice on how to do it without having to know a bunch of technical jargon and what to do to keep the phone as close to stock as possible but still get the JB update?
Click to expand...

Read up on xda. I'll post the relevant links after I get off work, but it's not that hard really. And if you want something close to stock (with sense) viperXL is a great sense 4+ (and android 4.1) based ROM to run. I am running it right now and i think it's great.
 
Could it possibly be because I extracted the toolkit to D drive instead of C drive? I'm just reading over the instructions again.
 
After your computer loads up, open my toolkit and connect your phone to the computer. Your phone should now be recognized.

Now, click 2. Register at HTCDev. Register with a VALID email address and LEAVE the web browser open.

Now, under the commands section of my toolkit, press Boot into Bootloader.

You should have a nice, white, shiny screen that says FASTBOOT USB.

On the part where it says "Your phone should now be recoginized." How do I know if it's recoginized????
 
chief113 said:
After your computer loads up, open my toolkit and connect your phone to the computer. Your phone should now be recognized.

Now, click 2. Register at HTCDev. Register with a VALID email address and LEAVE the web browser open.

Now, under the commands section of my toolkit, press Boot into Bootloader.

You should have a nice, white, shiny screen that says FASTBOOT USB.

On the part where it says "Your phone should now be recoginized." How do I know if it's recoginized????
Click to expand...

You should be able to see the phone in your file manager if you put the phone in mass storage/disk drive mode.
 
I actually got past that part. Now I am at the part where you have to copy your Token ID, and every time I do it it says:

Error 160: MID not allowed
 
Hi sorry for the delay in my reply... I thought I'd replied via tapatalk but evidently I didn't :confused:

Umm sometimes just leaving it plugged in for a while works. That's how EP had to do it at one point.

But, at this point, you can just get the update from AT&T themselves...
 
You must log in or register to reply here.
Back
Top Bottom