Related
Hello all, I'm new to this site and I've never rooted a phone. Actually, the Eris is my first smartphone. I've read a lot of forums about rooting the Eris and from what I understand I shouldn't have installed the 2.1 ota update. I bought this phone soon after they were released so maybe I have a 1.47 hboot? I'm unsure how to check this, but if so does this mean I can root using the 1.5 method?
I just bought a class 6 8GB microsd card with the hopes of installing a custom rom, overclocking, and installing apps2sd. Now I'm getting very discouraged because it seems 2.1 can't currently be rooted.
Hopefully a senior user can help me out. Please put your response in lamens terms. I've seen some other forums where junior users are getting bashed for asking stupid questions so I'm putting it out there....please don't bash me for this one.
http://forum.xda-developers.com/showthread.php?t=684049
everything you need and more. To answer your next question. As long as your phone was never updated with leak, the process for root of 1.5 and 2.1 are the same.
happy rooting!
Thanks Spencer! If I root using the method at that page will I be able to flash other roms or will I be stuck with this 2.1 ROM? I'd like to install the evileris rom and (again I'm a newbie) I don't want to end up stuck like the people who installed the leaked 2.1.
you should be able to flash a custom rom to the phone as i believe you have to first load a custom recovery image to it. i could be wrong though just a guess.
SDK Not Working?
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Ok, maybe this is my problem...
Before the root, I could go into device manager from my computer and I got a yellow exclamation mark. After the root, I cannot find it. I can click on portable devices and it shows an Android Phone so I'm guessing my computer doesn't recognize it anymore. If that's the case I probably need to update the driver for SDK to work, but I need to find the device for that to work. I have USB debugging on. Any help is appreciated.
If it says android phone with no exclamation point that means it is recognized. Its when there is an exclamation point that means it is not recognized. I probably won't be able to help you further because I'm a rooting noob (I've only rooted my Eris and I had no problems) but I am a computer expert and I would suggest rebooting your computer and then trying it again... unless you already have.
-------------------------------------
Sent via the XDA Tapatalk App
joshw0000 said:
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Click to expand...
Click to collapse
What exactly do you mean when you say "I can't get the command prompts to work"?
joshw0000 said:
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Click to expand...
Click to collapse
Ok, calm down its not the end of the world, i ran into the same problem. What we need for us to help you, is at what point are you in trying to root your phone. Do you have SDK installed and updated?
I'm following the how to root instructions. I've completed I: Gaining Root and made it to 9. In II: Prerequisites. Java and SDK are both saved and extracted on my c: drive. I downloaded the USB drivers package in #6 of II. USB debugging was enabled and the phone was set to charge only. When I opened device manager on my pc, their was no yellow exclamation like the instructions indicated. I clicked on "Android Phone" and attempted to update the drivers found in SDK but Windows said they were up to date. I moved on to step III. Flashing a Custom Recovery and saved the zip file to my SD (should I save that to my c: drive?). I extracted it to tools in Android SDK and attempted to use the command prompt in SDK. It was unresponsive. It did not recognize my phone. I'm unsure if it does that automatically, if I need to take action, or if I should use the pc command prompt.
I went back to #9 of II and tried to troubleshoot. I tried every way I could think of to get the exclamation mark to show up in device manager so I could update the USB drivers. I hooked up my wife's unrooted Eris and it had the exclamation. I restarted my phone, restarted my computer, reflashed PB00IMG.zip and still had no luck.
Anybody had this probem? Any suggestions?
I have been reading the http://forum.xda-developers.com/showthread.php?t=1006368&highlight=mac+osx thread (DesignGear's aRoot script, edited to run on Mac OS X)
My phone is connecting fine in USB debugging mode. The script runs but it doesn't seem to be working quite right. There are many files failing to copy.
Here is what I get when I run the script...
Getting temporary root access...
861 KB/s (585731 bytes in 0.664s)
Mounting /system as read/write ...
Cleaning up onclickroot mess ...
Rooting your device ...
failed to copy '/Volumes/Documents/Android/aRootMac_fix/bin/su' to '/system/bin/su': Read-only file system
Installing Superuser app ...
878 KB/s (196521 bytes in 0.218s)
Installing sqlite3 ...
failed to copy '/Volumes/Documents/Android/aRootMac_fix/bin/sqlite3' to '/system/bin/sqlite3': Read-only file system
Enabling sideloading ...
Enabling tethering ...
Enabling init.d support ...
failed to copy '/Volumes/Documents/Android/aRootMac_fix/bin/install-recovery.sh' to '/system/etc/install-recovery.sh': Read-only file system
failed to copy '/Volumes/Documents/Android/aRootMac_fix/bin/00remount' to '/system/etc/init.d/00remount': No such file or directory
Rebooting ...
Press any key to continue...
Then it reboots.
Superuser is installed, but I don't know if the process is successful or not. I'm also not sure what to do next.
This is my first post here and my first attempt at rooting, though its my third android device.
Thanks for your help in advance.
Nick
Depending on the software version of your Atrix.... aRoot doesn't work anymore.
(The part that is likely to be failing is psneuter, which was fixed by motorola a few software revisions ago)
You can check by opening SuperUser.apk and click on 'check su version' and if it fails, you don't really have root.
I too, am an OS X user.
As far as I know there is no way that actually works to flash your phone from OS X.
And I don't think there is any way to root anymore without flashing. (somebody can correct me if I am wrong)
I installed windows XP on a boot camp partition and installed RSDLite and moto-fastboot and unlocked/installed alternate ROMS.
http://forum.xda-developers.com/showthread.php?t=1136261 is probably where you should start.
dragula53 said:
As far as I know there is no way that actually works to flash your phone from OS X.
And I don't think there is any way to root anymore without flashing. (somebody can correct me if I am wrong)
Click to expand...
Click to collapse
Actually, for flashing this is not true. sbf_flash works fine.
OP, you should do a search for that. I'm on an MB Pro OS X 10.7.1. In fact, it worked where my Vista 64 bit machine + RSD lite wouldn't. I've used it several times to unlock the boot loader (IHOP_Bell.sbf). It worked flawlessly. After that, flash clockwork mod with moto-fastboot-osx64 or 32, and then you can just look for a ROM to install from cwm that is already rooted... which most of them are.
Based on the command line output, remounting the system partition for read/write failed, probably due to the "getting temporary root" step failing also. This means you don't have root because su wouldn't be copied over properly. aRoot is for 2.2.1... What version are you on?
Thank you both for you reply's.
I tried to check SU version and nothing happens, so I guess it's not rooted.
Also I checked my android version and I'm on 2.2.2 so I guess aroot's not for me.
I will try the RSD lite option next I guess..
Thanks again
Nicholox said:
Thank you both for you reply's.
I tried to check SU version and nothing happens, so I guess it's not rooted.
Also I checked my android version and I'm on 2.2.2 so I guess aroot's not for me.
I will try the RSD lite option next I guess..
Thanks again
Click to expand...
Click to collapse
Really, the RSD lite option? Why would you go to all the trouble of bootcamp and Windows when you could do it all on your current OS? Even some Windows users will tell you how frustrating it is to get RSD lite working on some machines. Works great on my netbook with Win7 Starter, but my main Win Vista 64 bit wouldn't do it no matter what.
For OS X, you just need:
sbf_flash
moto-fastboot-osx
Use the International Pudding thread as a guide to unlocking your bootloader. Once you've done that, the subject of root is almost moot because most ROMs are already rooted, you only need to install superuser.
Yeah I guess you're right I would prefer to do it on in OSX. I do already have a windows partition setup though, but I would rather not use windows if oI don't have too. It's just that in your earlier post the process sounded more complicated compared to the RSDLite option, which I have also already read a little bit about.
I have downloaded the files, but I'm not quite sure where to go from there. From what I can gather I need to unlock the bootloader first. But what do I do with the sbf_flash?
Thanks again
Nicholox said:
Yeah I guess you're right I would prefer to do it on in OSX. I do already have a windows partition setup though, but I would rather not use windows if oI don't have too. It's just that in your earlier post the process sounded more complicated compared to the RSDLite option, which I have also already read a little bit about.
I have downloaded the files, but I'm not quite sure where to go from there. From what I can gather I need to unlock the bootloader first. But what do I do with the sbf_flash?
Thanks again
Click to expand...
Click to collapse
Okay, well first of all, you need to flash the unlockable bootloader:
1. Turn off your phone, then hold the down volume button and tap the power button. The phone will start up with a cycling menu that initially says, "fastboot".
2. Press volume down several times until it says, "rsd". This is the mode you want to be in.
3. Press volume up to select this mode.
4. Open up Terminal, cd to where your files are and type:
Code:
./sbf_flash IHOP_Bell.sbf
5. Reboot your phone and hold down the volume button again. This time you want to be in "fastboot", so when it comes up, press volume up.
6. From Terminal, type:
Code:
./moto-fastboot-osx64 oem unlock
Use the 64 bit or 32 bit version of the commands depending on your system. If you're on Lion or have a pretty new computer, it'll be the 64 bit one.
It will tell you to type in that command again, but this time along with the id they've provided. Take a look at the screenshots in the Pudding thread, they basically show this step, but in a Windows command prompt. It's the same thing.
7. Reboot your phone:
Code:
./moto-fastboot-osx64 reboot
Now you can flash clockwork mod onto the recovery partition with moto-fastboot-osx also. The ORFR 2.3.4 thread has some good examples and instructions on general flashing. The gobstopper threads also have some recovery files and instructions you could use to start off. Once you've got recovery installed, you're pretty much in the clear. You can softbrick your phone, but with recovery it's easy to get back to a working state.
Good luck!
Hey thanks Maledyris, this is great. I had some trouble finding the IHOP_Bell.sbf but I have it now.
I also found the ORFR 2.34 system and webtop images, what is the difference between these and the HKTW files, which should I use?
I'm hoping that putting Gingerbread on this phone will improve my signal strength (I read this somewhere online). If it doesn't I would like the option of returning it and getting a different phone with proper reception. How much of this can be undone? should I need to?
when I unrared IHOP_Bell.rar I got intl-fix-try1.sbf
Is that right?
Sorry this is my first time and I'm totally noob and a bit nervous.
Hey one more question, I saw another post of yours from march and it said you'd gone back to 2.2.2....what are you running now??
Cheers,
Nick
Nicholox said:
when I unrared IHOP_Bell.rar I got intl-fix-try1.sbf
Is that right?
Sorry this is my first time and I'm totally noob and a bit nervous.
Click to expand...
Click to collapse
Well, I did it weeks ago, and back then it was actually called IHOP_Bell.sbf. It's possible the poster re-uploaded with a fixed version... Did you get it from International House of Pudding thread? If you did, that's the right one.
Nicholox said:
Hey one more question, I saw another post of yours from march and it said you'd gone back to 2.2.2....what are you running now??
Cheers,
Nick
Click to expand...
Click to collapse
Yeah, I'm currently on stock 2.2.2. I'll have time this week, so I'll probably play around with some of the newer ROMs people have been putting out. Before this, I had to go back because of stability and battery problems
Nicholox said:
Hey thanks Maledyris, this is great. I had some trouble finding the IHOP_Bell.sbf but I have it now.
I also found the ORFR 2.34 system and webtop images, what is the difference between these and the HKTW files, which should I use?
I'm hoping that putting Gingerbread on this phone will improve my signal strength (I read this somewhere online). If it doesn't I would like the option of returning it and getting a different phone with proper reception. How much of this can be undone? should I need to?
Click to expand...
Click to collapse
Ah, uhh... I'm not sure about the whole undoing part for you. I'm on Bell, and Bell has packages under the gobstopper threads to go between stock 2.2.2 and the alpha 2.3.4. I don't know if anyone has made the same type of thing for Telstra? Someone who's on Telstra could look at the images that were created for the Bell 2.2.2 stock cwm recovery and do the same for Telstra. I think it would depend on your carrier whether they care if you've unlocked your boot loader and changed the firmware? I've never tried to return my phone, but I bet they don't check. You never know though.
If reception and the radio is your main concern, I would probably see if I could just flash the radio instead of trying to flash full ROMs. It would be less of a noticeable change if you did decide to return it. I don't have suggestions on that though, you'd have to do a search. I don't quite remember anymore, but I think I flashed either the Orange or Telstra radio ages ago before we had an unlocked bootloader. It was fairly quick and painless. I had done it with RSD lite and win7 before I knew sbf_flash existed.
maledyris said:
Really, the RSD lite option? Why would you go to all the trouble of bootcamp and Windows when you could do it all on your current OS? Even some Windows users will tell you how frustrating it is to get RSD lite working on some machines. Works great on my netbook with Win7 Starter, but my main Win Vista 64 bit wouldn't do it no matter what.
For OS X, you just need:
sbf_flash
moto-fastboot-osx
Use the International Pudding thread as a guide to unlocking your bootloader. Once you've done that, the subject of root is almost moot because most ROMs are already rooted, you only need to install superuser.
Click to expand...
Click to collapse
Awesome. I wasn't aware that there were OS X versions now. I flashed very early on though, and never checked again.
And if you are looking for newer ROMs, I highly recommend Ninja ROM, which is my favorite of the bunch that still retain all of the Blur applications.
... Or CM7 pre-beta 2, which breaks the camera in most apps that use it. Pre-beta 1 ruined my battery life, but beta 2 is just fine. If you go this route and still want to use the camera, Angel Camera on the market works.
Thanks again Maledyris,
I did get it from the international house of Pudding thread so it must be the right one.
I found this thread http://forum.xda-developers.com/showthread.php?p=16853634#post16853634
They are talking about the motorola defy.... do you think that 2.2.2 will work with the Atrix too?
Dragula, can you give me some links for those ROM's you're talking about? I would like to use the camera still I think!!
cheers!!
ok heres the latest, my Atrix has gone in for a repair. It had some serious reception issues and after a week of arguing with telstra they're going to have a go oat repairing. it. Basically it show lower signal strength than many other phone. If you're here Aus you'll know Atrix is supposed to be "blue tick" well this one certainly wasn't.
Anyway my rooting plans are on hold till I get the phone back...
any chance of those links dragula?
Are you still around Maledyris?
I got my phone back and it's no different, so I'm ready to get started. I've read through your instructions again, and tried to find an answer elsewhere in the forum, but I'm still confused about how to flash CWM recovery the bootloader is unlocked. There seems to be so many files and I'm not sure which are ok for my telstra atrix.
I saw I can download CWM from the market, is that what I need to do next? but you said flash CWM so I'm guessing not the market...
I've downloaded recovery-en-goapk-0630-1029.zip but I'm not sure exactly what to do with it??
Thanks again,
nick
Hi Nicholox;
I am in he same boat as you. I am about to get my first Android Phone (looking at the Atrix) and have been doing some serious reading about bootloaders/rooting and ROMS.
How did you unlock your bootloader?
Now to answer your question on CWM. From what I have read you can download and install ROM Manager from the App Market and then use the ROM Manager to install CWM.
I am pretty sure thats right. Someone please correct me if I am wrong.
Just check out these intructions from Maledyris... I'm not sure if my phone will boot up to access the market after flashing the sbf and unlocking it. anyone know the answer to this?
maledyris said:
Okay, well first of all, you need to flash the unlockable bootloader:
1. Turn off your phone, then hold the down volume button and tap the power button. The phone will start up with a cycling menu that initially says, "fastboot".
2. Press volume down several times until it says, "rsd". This is the mode you want to be in.
3. Press volume up to select this mode.
4. Open up Terminal, cd to where your files are and type:
Code:
./sbf_flash IHOP_Bell.sbf
5. Reboot your phone and hold down the volume button again. This time you want to be in "fastboot", so when it comes up, press volume up.
6. From Terminal, type:
Code:
./moto-fastboot-osx64 oem unlock
Use the 64 bit or 32 bit version of the commands depending on your system. If you're on Lion or have a pretty new computer, it'll be the 64 bit one.
It will tell you to type in that command again, but this time along with the id they've provided. Take a look at the screenshots in the Pudding thread, they basically show this step, but in a Windows command prompt. It's the same thing.
7. Reboot your phone:
Code:
./moto-fastboot-osx64 reboot
Now you can flash clockwork mod onto the recovery partition with moto-fastboot-osx also. The ORFR 2.3.4 thread has some good examples and instructions on general flashing. The gobstopper threads also have some recovery files and instructions you could use to start off. Once you've got recovery installed, you're pretty much in the clear. You can softbrick your phone, but with recovery it's easy to get back to a working state.
Good luck!
Click to expand...
Click to collapse
ok this doesn't seem to be going so well. I finally psyched myself up to unlock my atrix and i'm stumped at the first step.
Nicks-MBP:Atrix Nicholox$ ./sbf_flash int-fix-try1.sbf
-bash: ./sbf_flash: Permission denied
Why do I get a permission denied when I try to flash bell IHOP?
thanks,
Nick
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?
So guys, I'm new to this and thought I would jump in at the deep end.
I unlocked my HTC One X+ easily and set about rooting.
I've got TWRP installed but it keeps telling me it needs to install superuser before it can root.
I have totally wiped the phone, how come if Im not rooted?
How do I get an OS and indeed the kernel or ROM onto the phone?
Its and International OX+, I've got the right kernel... what do I need to do?
It was locked to O2 if that makes a difference
I followed the instruction in Hasson but then wiped the OS
I know its a simple procedure but can someone walk me through it please
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
eskimosound said:
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
Click to expand...
Click to collapse
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
dan_alexandre said:
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
Click to expand...
Click to collapse
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
eskimosound said:
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
Click to expand...
Click to collapse
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
dan_alexandre said:
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
Click to expand...
Click to collapse
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
eskimosound said:
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
Click to expand...
Click to collapse
I see, the easiest ways would be to use a custom rom now. For example, the one you already got the kernel from(android revolution hd)
To root you dont need to install a kernel... just to flash the supersu zip. Using a custom rom's kernel with stock rom might not be a good idea.
Another simple way would be to restore stock rom back to start and try rooting again, this time reading everything carefully
So the two easiest ways i think:
1) flash a custom rom following the instructions they provide in the initial posts for that rom
2) run the o2 correspondent RUU to restore stock rom (you'd need to relock the bootloader), also reading carefully posts in the forum about restoring to stock
Without getting into too much detail, these are the simplest options.
All the info required to do these are on these forums
Aaarrghhh, its driving me insane as I knew it would, just like XP, Vista Seven and Eight!!!
So Im back to being up all night learning..
Well have installed SDK correctly but device is not seen, no serial, nothing.
I can get it to fastboot though, however I don't know any commands so I cant get it to work
Windows 7 keeps moaning about an mpt file which I downloaded and dont know where to extract it to
All I need to do is copy a few files to the phones sd card and install them right?
Whys that so difficult?
I don't know the difference between a rom an ruu and a boot image, in that I don't know where they should all be placed.
Why cant twrp copy and paste from pc...
So Hassooon works sort of but still none the wiser.
Am following tutorial but fastboot commands are not working
Still cant find right driver.....
So CMD lines not working 100%
So am downloading drivers in sdk manager
And how do I flash the supersu zip?
Still no luck with driver, im on windows 7 32bit
OK I cant push using adb it cant find the file or directory,
Hassooon cant detect the phone as cant windroid universal
I dont think the phone is rooted even though i have twrp on it.
Thus can I have wiped the os?
If not can i restore it?
No I didnt make a backup rom..
mmm a zip on the phone doesnt load in bootloader, count that be my os?
Guys, im stranded in the water here...
On boot im getting...
Failed to open usb master mode
[Preload] Failed to open usb master mode
loading PM35IMG.zip image...
Failed to open usb master mode
please plug off usb
Whats PM35IMG.zip?
Is that the OS?
Am I saved?
Is it easy to get that file to unzip and load?
Can anyone help?
So now I need the right RUU.....
2.17.206.3
Is there anyone out there that can help please?
So have managed to install superuser and root my phone, all instructions for doing this were wrong including Hassoon, had to have the phone in System screen to do it, not bootloader or recovery.
Now cant get adb to push file to sdcard...
Man alive, how to make something very easy, sound very difficult.
Would any of you experts care to help?
Just trying to install a ROM.zip to Root and place the boot img in right place.
Well, the instructions are dire but after 10 days of persistance have installed Android Revolution HD 8, finally my phone is up and running better than the bloated os that came with the phone so, you can call this thread resolved.