Hey everybody, Im a little confused about a few things, and thought I'd ask a couple of questions. I'm still fairly noob to all of this. I used to have an hd2 that I managed to put nandrom android on and eventually got fairly proficient with flashing roms. My phone broke and I was without for a year or so. Now I have an Evo3d, and I want to get back into the smartphone scene a bit. I understand that with the hboot 1.50, it is difficullt to root the phone. I have seen a few tutorials on different methods, but they all seem to be multi tutorials thast try to cover rooting, flashing roms, kernbels, recovery, etc. I just want to root the phone to begin with. Could anyone point me to a decent simple tutorial on just rooting the phone? I'm a one step at a time sorta person when I want to learn about a new subject, and I get kinda bogged down with having to learn too many new things at once with most of the tutorials I have managed to find. I'd really appreciate any help, as I would like to learn more about all of this, but like I said, I like to take baby steps.
Thanks Everyone,
Mike
It's easy just follow this guide.
http://forum.xda-developers.com/showthread.php?t=1239821
Ok, so Im doing this, and after a little fussing with the downloads, It seemed to be working. I'm doing the htc unlock, I get the identifier token, I receive my e-mail with unlock_code.bin. I download it and place it in the c:\android folder, then when I type "fastboot flash unlocktoken Unlock_code.bin, I get an error message stating that remote is not allowed. Any ideas what this means, or what I might be able to do about it?
Thanks,
Mike
nvm. it mysteriously worked after trying it a few more times.
Ok now. So I'm inching along with this. I've gotten as far as typing "fastboot flash recovery recovery.img" and the thing just pauses. it says "sending 'recovery' (5068 KB)..." and I get a flashing cursor. I let it run once for 4 minutes with no response. Now I'm letting it run for ten minutes to see what happens. Anybody have any ideas? I really appreciate it. p.s. I'm pretty sure I have usb debugging checked. If it doesn't work this time, that's the first thing I'll check. Anybody know if I should have fastboot checked on?
Got through that! For some reason, I didn't have htc sync running on my laptop. Good thing to remember in the future, I guess! Now I am awaitinf titanium back up to finish, then it's on to a new, custom rom!!! I'll be back with a status update, Im sure. wish me luck.
Related
I rooted my Eris a long time ago to 2.1 using the popular method of sticking the PB00IMG in the root of the sdcard, and starting the phone up using down volume+end. So now I’m running the bootleg 2.1; okay.
I followed all the directions on this familiar page of How To Root Your HTC Eris on thefuzz4.
I even got to the point where I’d typed in all the lines of code, and everything seemed to go well. But when it came time to restart my phone into recovery mode, use Amon’s Recovery and all that jazz, it just came up with the ! inside of the triangle, with a little picture of a phone next to it. I have no idea what I did wrong, I have no idea how to get it to work, nothing. I’m admittedly very new to this whole thing, but I just need help please!
The whole goal in doing it anyway is so I can downgrade my phone back to totally stock Android 1.5, so as to just have a clean phone and naturally upgrade to the OTA 2.1 that’s being released. I really don’t care about if any information gets wiped on my phone, so really ANY solution to getting my phone back to 1.5 or up to the OTA 2.1 with no trace of the ROM would be accepted.
I’ll pretty much do anything at this point, because god knows, I won’t figure it out.
Are you sure that you didn't install the non-root leak?
If you have root, you should have a # in front of the command line.
If you have a $ instead, try running the "su" command and press allow on your phone.
I’m definitely sure it’s rooted. I saw the #, and made sure that I did. I just can’t figure out how to get away from this 2.1 root.
I’m mean, I’ll pretty much do anything, even start from scratch to get this to work. I’m just totally at loss and need someone’s help.
use the tutorial on theunlockr it worked for me the fuzz didnt
the unlockr is garbage.
Use this guide, specifically step 3 (III)
http://forum.xda-developers.com/showthread.php?t=647707
Post back if you still can't figure it out. Don't miss or alter ANY step!
I finally got it to work. I downloaded Terminal Emulator from the market, and flashed the recovery image from the phone itself without having to use the SDK. It was actually way easier.
Now I’m running 1.5 again! Kind of funny that’s what all of this work was for. Now the only question is if I’ll still get the OTA 2.1 if I still have Amon’s installed….
Hey guys I recently got the Amaze (2 days ago). When I got it, it was on GB but I went to T-mobile to get a new sim and the guy updated my phone to ICS. Now ive tried rooting it but it does not work, i tried with the all tool kit program and the one click root. IS their anything I am doing wrong? Also do I have to be in recovery mode or can I be at the home screen? Debugging is on.
The only thing I can tell your doing wrong is your not reading enough. There is an Amaze Bible. There are How To Root Tutorials. It's been asked multiple times.
I haven't used All In One (AIO) Tool Kit but I think there's a Tutorial.
Sorry..its just frustrating coming to a forum and everyone ask the same thing over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over......you catch my drift?
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
pakakid said:
Hey guys I recently got the Amaze (2 days ago). When I got it, it was on GB but I went to T-mobile to get a new sim and the guy updated my phone to ICS. Now ive tried rooting it but it does not work, i tried with the all tool kit program and the one click root. IS their anything I am doing wrong? Also do I have to be in recovery mode or can I be at the home screen? Debugging is on.
Click to expand...
Click to collapse
If you searched the word "root" in my thread, there are many posts mentioning that it does not work and I said I was gonna eventually fix it.
On other terms, flash this in recovery
Try the tool kit again, note that you have to install a custom recovery before trying to root via the tool kit, once you have a custom recovery, boot into recovery then hit the root option, it should ask you to press enter once you're in recovery, do this and you shall be rooted.
Dark Nightmare said:
Try the tool kit again, note that you have to install a custom recovery before trying to root via the tool kit, once you have a custom recovery, boot into recovery then hit the root option, it should ask you to press enter once you're in recovery, do this and you shall be rooted.
Click to expand...
Click to collapse
As mentioned below, this might not be working for everyone. It pushed all the files for me but did not result in root. Flashing the superuser zip linked below is what finally worked for me.
hasoon2000 said:
If you searched the word "root" in my thread, there are many posts mentioning that it does not work and I said I was gonna eventually fix it.
On other terms, flash this in recovery
Click to expand...
Click to collapse
Double0EK said:
The only thing I can tell your doing wrong is your not reading enough. There is an Amaze Bible. There are How To Root Tutorials. It's been asked multiple times.
I haven't used All In One (AIO) Tool Kit but I think there's a Tutorial.
Sorry..its just frustrating coming to a forum and everyone ask the same thing over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over......you catch my drift?
Click to expand...
Click to collapse
On a separate note,
I very much appreciate the help that can be received here and there quite a few tutorial threads. The problem I think some people have, including me, is that what is written doesn't always make sense to those who don't live and breathe android. I'm fairly tech savvy (have built computers, know basic bash scripting, and have spent excessive amounts of time troubleshooting and hacking in Linux) but instructions like "flash stock RUU in hboot" don't make much sense until you've spent a lot of time reading.
Hasoon's tool is very close to what is needed. Hopefully whatever issue there is with the root option can be fixed. Or maybe it's just a matter of better understanding of how to use it.
droidux said:
As mentioned below, this might not be working for everyone. It pushed all the files for me but did not result in root. Flashing the superuser zip linked below is what finally worked for me.
On a separate note,
I very much appreciate the help that can be received here and there quite a few tutorial threads. The problem I think some people have, including me, is that what is written doesn't always make sense to those who don't live and breathe android. I'm fairly tech savvy (have built computers, know basic bash scripting, and have spent excessive amounts of time troubleshooting and hacking in Linux) but instructions like "flash stock RUU in hboot" don't make much sense until you've spent a lot of time reading.
Hasoon's tool is very close to what is needed. Hopefully whatever issue there is with the root option can be fixed. Or maybe it's just a matter of better understanding of how to use it.
Click to expand...
Click to collapse
That's why we have an amaze bible thread bro, we have every and anything about the amaze from the simplest term broken down and explained, that includes but not limited to hboot, s-off, fastboot, bootloader, etc. Check it, you'll be glad you did.
droidux said:
As mentioned below, this might not be working for everyone. It pushed all the files for me but did not result in root. Flashing the superuser zip linked below is what finally worked for me.
On a separate note,
I very much appreciate the help that can be received here and there quite a few tutorial threads. The problem I think some people have, including me, is that what is written doesn't always make sense to those who don't live and breathe android. I'm fairly tech savvy (have built computers, know basic bash scripting, and have spent excessive amounts of time troubleshooting and hacking in Linux) but instructions like "flash stock RUU in hboot" don't make much sense until you've spent a lot of time reading.
Hasoon's tool is very close to what is needed. Hopefully whatever issue there is with the root option can be fixed. Or maybe it's just a matter of better understanding of how to use it.
Click to expand...
Click to collapse
Google is your friend. I taught myself many things from Google before I asked a question. If I am TRULY stuck, I'll ask a question.
Look at the threads I made, I rarely ask a question because I found it from Google.
You can learn a lot by yourself and just searching stuff online. Not that hard lol
hasoon2000 said:
Google is your friend. I taught myself many things from Google before I asked a question. If I am TRULY stuck, I'll ask a question.
Look at the threads I made, I rarely ask a question because I found it from Google.
You can learn a lot by yourself and just searching stuff online. Not that hard lol
Click to expand...
Click to collapse
I completely agree. I've taught myself tons about programming and such using Google, but you also have to have enough background knowledge to know what to look for and recognize when you find it. I've mostly asked questions here but it wasn't until I did a lot searching and trying things. Eventually, when something doesn't work you can stop and ask a question or keep messing around. In the later case, you either brick the phone or become one of the experts (after bricking the phone ).
Problem with google is that it often points to a thread here which invariably results in someone new asking a question that's been asked before. Happens in all forums.
Dark Nightmare said:
That's why we have an amaze bible thread bro, we have every and anything about the amaze from the simplest term broken down and explained, that includes but not limited to hboot, s-off, fastboot, bootloader, etc. Check it, you'll be glad you did.
Click to expand...
Click to collapse
I did.
Ok, you know, today I got my phone, I had been waiting forever, I got it and within 2 hours I screwed it up. I have followed and followed many forums and posts on how to fix this, and I am just.. lost. So please i need your help, I am seriously stressing out, and I know I shouldnt, but this is my first android phone. I am shot right now.
I had unlocked the bootloader, and then I tried to root it, then it rebooted and went into bootloop mode or whatever it is.
I still cannot figure out how to use this Hasoons2000's OX+ AIO kit. So I am just leaving it alone.
Ok the PC doesn't recognize it as a storage device, but the fastboot does recognize it, as I have executed a few commands, like reboot or something, just to test that it works.
My phone is ATT but I am in Russia so there is no sending this anywheres. All I want to do is reboot the OS and have it work again, I dont care what mod or stock rom it is, I just really need some direction here.
I know something about RUU, ATT RUU, Fastboot, some other stuff, I have like 5 pages on XDA pulled up and I cant figure this out.
What is the CMW or TWRP or whatever it is called? How do I flash a zip or an img to the phone? I really just want my phone on again.
Yes Ive done stupid noob stuff, but you learn. So please I am kindly asking for any assistance,
No need to stress. Its fairly hard to brick your phone, good way to learn quick also is to screw with it.
Just need the right guide and I think this will help you since u have fastboot access hopefully. Its a pain rebuiling so read everything so u only have to do it once.
Remember these guides are for different phones so don't use the ruu or recovery links, user my links below.
Your phone is:
AT&T(Evitare)
This guide:
http://forum.xda-developers.com/showthread.php?p=30863908
Or this guide:
http://forum.xda-developers.com/showthread.php?p=27301573
This is for another phone so you need to choose an ATT ruu from here for step 1:
Your phone is a HTC One X+ for AT&T(Evitare)*
http://www.androidfiles.org/ruu/?developer=EvitaRE
More info here for custom recoveries etc which is cwm and twrp for deploying roms, backing up your current installed Rom and general tools for fixing or enhancing your phone, displayed prior to your phone booting into android:
http://forum.xda-developers.com/showthread.php?p=37778531
Sent from my HTC One X+ using xda premium
somemadcaaant said:
No need to stress. Its fairly hard to brick your phone, good way to learn quick also is to screw with it.
Just need the right guide and I think this will help you since u have fastboot access hopefully. Its a pain rebuiling so read everything so u only have to do it once.
Remember these guides are for different phones so don't use the ruu or recovery links, user my links below.
Your phone is:
AT&T(Evitare)
This guide:
http://forum.xda-developers.com/showthread.php?p=30863908
Or this guide:
http://forum.xda-developers.com/showthread.php?p=27301573
This is for another phone so you need to choose an ATT ruu from here for step 1:
Your phone is a HTC One X+ for AT&T(Evitare)*
http://www.androidfiles.org/ruu/?developer=EvitaRE
More info here for custom recoveries etc which is cwm and twrp for deploying roms, backing up your current installed Rom and general tools for fixing or enhancing your phone, displayed prior to your phone booting into android:
http://forum.xda-developers.com/showthread.php?p=37778531
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
thank you very much I really appreciate your help. I finally figured out the ruu.exe thing, I didnt know they had to be the same numbers, ex 1.15.xxx.xx or whatever.
You see what happened originally was that I unlocked the bootloader, easy pie, but I tried to root it and that is when it started looping. Maybe I didnt understand something, but I seemed to have messed up right there.
Is there really any reason to root? I mean yeah there is super user, but doesnt bootloader help with that a bit? I know BL is for flashing custom roms and all.
May I ask how to flash a custom rom? I really want all of this ATT stuff off of my phone, I really dislike it.
Yes I know I can search, here, google etc. And maybe I should, but I end up getting so many different results, and here and there, and this and that. It really is just easier to talk to one single person who knows what they are doing. So if you could help me, I would again extend my appreciation.
Also I have the android revolution for ox+, and I dont know if it is.. you know.. THE BEST or not. Dont know what to do.
And yes, you live and learn, took me forever with iphones, then I realized hacking and roms and stuff were completely different from iphone. So new game new story.
Ok guys...here it goes.
I've had a long night of feeling like the biggest idiot to walk the Android planet. I just bought this phone off someone, and have done rooting/custom ROM installing before. But I messed up, and now I feel like I'm an idiot & screwed because I'm just so lost now. I love learning, but I feel like I'm in such a hole. Here's what happened:
I used "All In One Kit" to install "TWRP 2.6.0.0", and like anybody, I wanted to install a custom ROM after getting all the rooting done. So I went searching for CW10.1, and tried to install it. Kept getting "Failed" every time I tried to install CW10.1 with "TWRP", so I started googling why. Well, it said I had to install the boot.img with the whole "fastboot" process where I use the command "fastboot flash boot boot.img". So I did that...and man was that a mistake.
My phone after, would just stay stuck at the boot screen. So I didn't panic, and I went into "TWRP" and tried to restore from the backup I did, before I started trying to install a custom ROM...but the same thing happened. Fast forward 2 hours and now I feel like I've screwed myself. I thought "TWRP" backed everything up, but for all I know, my moronic self might have unchecked "Boot". So I believe I need to "fastboot" the correct/original boot.img, so the phone will boot normally, but I have no idea where to find it. I've tried looking, but I'm more finding the issue is solved by using RUU. Which I REALLY don't mind doing at all, but I'm scared now since there are so many different ones, and I can't figure out which one is the right one to use. My night has taken such a crappy turn, I'm afraid if I RUU once wrong, I will be in an even bigger mess, than trying to reach out to you guys first. It's crazy how comfortable I was doing all this, and now I feel like I shouldn't have ever tried.
Here is the phone info I can provide that is hopefully helpful:
The phone is an HTC One X+ AT&T USA
EVITARE_UL PVT SHIP S-ON RL
HBOOT: 1.40.0000
CPLD-None
MICROP-None
RADIO-SSD: 2.14.55.01
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
Dec 28 2012, 22:18:14
And I believe it was at 4.2.1 software...but I'm not 100% on that and don't know how to make sure.
Please guys, if anybody can help, I need it. I appreciate your time in reading this, even if you cannot help. I believe I either just need a stock boot.img for my phone, or linked the correct RUU (assuming I'm right in that will fix it and revert me back to having a phone again). Any questions feel free to ask me. I'm going to try to sleep now.
krayzed896 said:
Ok guys...here it goes.
I've had a long night of feeling like the biggest idiot to walk the Android planet. I just bought this phone off someone, and have done rooting/custom ROM installing before. But I messed up, and now I feel like I'm an idiot & screwed because I'm just so lost now. I love learning, but I feel like I'm in such a hole. Here's what happened:
I used "All In One Kit" to install "TWRP 2.6.0.0", and like anybody, I wanted to install a custom ROM after getting all the rooting done. So I went searching for CW10.1, and tried to install it. Kept getting "Failed" every time I tried to install CW10.1 with "TWRP", so I started googling why. Well, it said I had to install the boot.img with the whole "fastboot" process where I use the command "fastboot flash boot boot.img". So I did that...and man was that a mistake.
My phone after, would just stay stuck at the boot screen. So I didn't panic, and I went into "TWRP" and tried to restore from the backup I did, before I started trying to install a custom ROM...but the same thing happened. Fast forward 2 hours and now I feel like I've screwed myself. I thought "TWRP" backed everything up, but for all I know, my moronic self might have unchecked "Boot". So I believe I need to "fastboot" the correct/original boot.img, so the phone will boot normally, but I have no idea where to find it. I've tried looking, but I'm more finding the issue is solved by using RUU. Which I REALLY don't mind doing at all, but I'm scared now since there are so many different ones, and I can't figure out which one is the right one to use. My night has taken such a crappy turn, I'm afraid if I RUU once wrong, I will be in an even bigger mess, than trying to reach out to you guys first. It's crazy how comfortable I was doing all this, and now I feel like I shouldn't have ever tried.
Here is the phone info I can provide that is hopefully helpful:
The phone is an HTC One X+ AT&T USA
EVITARE_UL PVT SHIP S-ON RL
HBOOT: 1.40.0000
CPLD-None
MICROP-None
RADIO-SSD: 2.14.55.01
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
Dec 28 2012, 22:18:14
And I believe it was at 4.2.1 software...but I'm not 100% on that and don't know how to make sure.
Please guys, if anybody can help, I need it. I appreciate your time in reading this, even if you cannot help. I believe I either just need a stock boot.img for my phone, or linked the correct RUU (assuming I'm right in that will fix it and revert me back to having a phone again). Any questions feel free to ask me. I'm going to try to sleep now.
Click to expand...
Click to collapse
i think installing an international ROM on an AT&T device was the downfall here
you need to install a ROM here for an example, by following the instructions given:
http://forum.xda-developers.com/showthread.php?t=2098218
leefear said:
i think installing an international ROM on an AT&T device was the downfall here
you need to install a ROM here for an example, by following the instructions given:
http://forum.xda-developers.com/showthread.php?t=2098218
Click to expand...
Click to collapse
No you are completely right. This is where I messed up, and everything went bad. My only problem is I'm not sure how to get the ROM on my device. Every time I try "ADB Sideload", it says it's starting...and then...that's it. I can cancel it, but it never actually goes through with the side load. What should I try to do in this case, so I can get the ROM loaded?
And thank you for your quick response, it's greatly appreciated!
krayzed896 said:
No you are completely right. This is where I messed up, and everything went bad. My only problem is I'm not sure how to get the ROM on my device. Every time I try "ADB Sideload", it says it's starting...and then...that's it. I can cancel it, but it never actually goes through with the side load. What should I try to do in this case, so I can get the ROM loaded?
And thank you for your quick response, it's greatly appreciated!
Click to expand...
Click to collapse
assuming you have the htc driver installed for your device, adb commands should work, can you test with adb devices that should list your phone, if not get your htc drivers installed and make sure you have latest adb on your pc
move NAMEOFROM.zip to adb folder and use the sideload option in twrp and sideload rom and should work
and don't forget to flash the boot.img provided
question rolermi
leefear said:
assuming you have the htc driver installed for your device, adb commands should work, can you test with adb devices that should list your phone, if not get your htc drivers installed and make sure you have latest adb on your pc
move NAMEOFROM.zip to adb folder and use the sideload option in twrp and sideload rom and should work
and don't forget to flash the boot.img provided
Click to expand...
Click to collapse
I definitely have the drivers installed, mostly because they were required as part of rooting with "All in One" tool. I never installed anything for ADB, I simply assumed it was just used as an option in "TWRP", so I'll go download that. Thank you, and I will update with my results!
Ok, posting an update!
Thank you for your response, as this fixed my problem! I will sum up my problem/fix in this reply, in case anybody is also trying to fix the same problem.
I have at HTC One X+ for AT&T
I was in a boot loop, after I had successfully rooted my phone with TWRP. I used "fastboot" method to change the boot.img, and lost my original in the process. Stuck only being able to boot to the system, or recovery, I needed a way to fix my boot problem. The suggested method worked flawlessy. I downloaded Android SDK, installed Platoform-Tools from the SDK Manager. Opened up ADB in ADT>SDK>Platform-Tools and followed the necessary steps for "pushing a ROM with ADB" I had found. I used the recommend link above for ViperXL+. I was able to push the ROM in, boot into recovery, and finally install a proper ROM. I then did the "fastboot" method to install the ROM ViperXL+'s boot.img (As a side note your .zip might show up as "sideload" and not the ROM title for the .zip I didn't know this, and thought it somehow lied to me is 100% completion, until I tried selecting "sideload" to install, which I didn't believe to have seen before. And sure enough it was the ROM)
Now my phone boots sucessfully, and I have a custom ROM. THANK YOU so much for your help, big kudos to leefear for explaining what I needed to do, and linking me the ROM. I appreciate it so much man!!!
krayzed896 said:
Ok, posting an update!
Thank you for your response, as this fixed my problem! I will sum up my problem/fix in this reply, in case anybody is also trying to fix the same problem.
I have at HTC One X+ for AT&T
I was in a boot loop, after I had successfully rooted my phone with TWRP. I used "fastboot" method to change the boot.img, and lost my original in the process. Stuck only being able to boot to the system, or recovery, I needed a way to fix my boot problem. The suggested method worked flawlessy. I downloaded Android SDK, installed Platoform-Tools from the SDK Manager. Opened up ADB in ADT>SDK>Platform-Tools and followed the necessary steps for "pushing a ROM with ADB" I had found. I used the recommend link above for ViperXL+. I was able to push the ROM in, boot into recovery, and finally install a proper ROM. I then did the "fastboot" method to install the ROM ViperXL+'s boot.img (As a side note your .zip might show up as "sideload" and not the ROM title for the .zip I didn't know this, and thought it somehow lied to me is 100% completion, until I tried selecting "sideload" to install, which I didn't believe to have seen before. And sure enough it was the ROM)
Now my phone boots sucessfully, and I have a custom ROM. THANK YOU so much for your help, big kudos to leefear for explaining what I needed to do, and linking me the ROM. I appreciate it so much man!!!
Click to expand...
Click to collapse
hey buddy, glad you got it working, nothing worse than a broken phone! glad i could help! now, hit that thanks button!
ooh, my 200th post!
leefear said:
hey buddy, glad you got it working, nothing worse than a broken phone! glad i could help! now, hit that thanks button!
ooh, my 200th post!
Click to expand...
Click to collapse
Congrats on the 200th post! Sorry, very new to using the forums. I hit thanks on all your posts in the topic! :good:
Hi,
i have the same problem but it's a non LTE version HOX+ can someone advise on another ROM that will work in the same way?
[SUMMARY] - If you're bored or find this kind of thing funny you could read this post from the bottom up and watch a noob go from freaking out, to learning how to troubleshoot then finally resolving his issue... all of this just by reading the FAQ thread and following some advice found there. I've learned my lesson... read XDA *before* trying to flash a new ROM.
[SOLVED] - Solution was to flash the boot.img from stock ROM. Once I did that the phone rebooted and went into the typical device setup. Now I guess I can update my ROM.
[FIRST UPDATE]
Turns out a lot of exactly what I was looking for is on the FAQ page (first bullet in Q15, no less). Trying what I found there. Please don't blast me with, Maybe you should have read the FAQ... I've been all over the place trying to find something that would work quickly... I only have one phone and I commute into Philly for work so I need a working phone... Now that I've found the XDA HTC ONE X + FAQ, I think I'll be fine. Thanks for the great site... so much info on here to read... good for long train rides.
[ORIGINAL POST]
Hi, I ran into a problem trying to flash CM to my HOX+ (AT&T). I followed the instructions here (wiki.cyanogenmod.org/w/Install_CM_for_enrc2b), but that was for the International version, not the AT&T... Dumb? Guess so, I don't know much about the difference, but it's what happened. I've tried to connect to the phone (per the instructions on the wiki) to adb push the ROM I want to flash, but I keep getting the device not found error. The instructions warn of possible driver error on the PC, but I haven't found a driver yet that will allow me to connect. I can get into recovery (CWM-based Recovery v6.0.2.7) but with no ROM on the sdcard I have nothing to flash and can't figure out how to get the file onto the device. The wiki should probably mention putting the ROM on the device prior to going through the HTC unlock steps, just in case, but maybe they assume a more cautious user than I am. I've tried to flash from sideload, but don't know if that is even possible?
Can someone point me in the right direction, or start asking questions to help me figure out what my next step is? Just want to get back to a working phone...
Thanks!
Signature?