Related
I rooted according the directions found here: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ after getting a new Nexus S 4G.
Even after locking the bootloader. It goes to the Android-with-box then to the Exclaimation-point-inside triangle. When I volume-up and power-button from that screen, an "Android Recovery <3e>" comes up...
Does anyone know what might be going on? And how do I get my custom recovery to stick?
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
mikeyinid said:
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Apparently alot of people have this issue, me included. I seen some posts about using root explorer to change the name of the recovery image if it shows up in system /ext. Sounds crazy but I hear it doesn't show up on all phone's. IV come to terms with having to fastboot every time I flash but I'd love to see a fix. Have you tried Amons recovery?
TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Have you flashed recovery through Rommanager when your phone boots up?
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
mbh87 said:
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
Click to expand...
Click to collapse
No, I dont think your wrong bro. It makes sense. Ill test your theory soon.
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
david1171 said:
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
Click to expand...
Click to collapse
I just had CWM, never had any issues. Im not sure what dictates whether that file is there or not. Im guessing that since tony is so quiet though he got it figured out..
whats amazing is i dont have this script and its one of the things holding the one click up :x
also its part of init.rc so technically a new kernel would.. in theory wipe that out...
mikeyinid said:
Have you flashed recovery through Rommanager when your phone boots up?
Click to expand...
Click to collapse
I did flash CWM through Rom Manager. That didn't work the first few times. It stalled...
mikeyinid said:
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
Click to expand...
Click to collapse
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
TonyArmstrong said:
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
mikeyinid said:
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
TonyArmstrong said:
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
Click to expand...
Click to collapse
OCD, I know the feeling lol. What got it to stick?
derekwilkinson said:
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
Click to expand...
Click to collapse
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
TonyArmstrong said:
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
Click to expand...
Click to collapse
well the "make sure it sticks" flashing with rom manager doesn't make any sense. the only way the recovery would be overwritten is if the ROM you flash over writes it or in fastboot
mikeyinid said:
OCD, I know the feeling lol. What got it to stick?
Click to expand...
Click to collapse
Yeah, I'm very anal when it comes to this kind of stuff...I was a developer for a little bit (Java middleware, then on to the front-end stuff) where regression testing was important. Sometimes, it's best to reload things piece by piece to see what breaks what. Then go from there.
I haven't gotten it to stick yet; gonna get some sleep and start over tomorrow. I used fastboot to push the stock boot, bootloader, system, recovery, and userdata IMGs a moment ago, and the phone is back to bone stock.
Ok guys so I have managed to root my i9023 and flash clockwork recovery which was all good, I set about flashing some new roms via rom manager, again, all good.
So now I settle on this cm7 based rom which I love, used anim mod to get some nice transitions, then I used font changer.
All was good, then I decided that the font I was using was a bit ott so I decided to change it again, upon reboot it starts boot looping, bollocks !!!
So I try to get into clockwork recovery, and it seems to have gone back to the stock bootloader, grrrrr
I re flash clockwork, wipe / clear etc... then flash the rom again, but it would not flash, so I went to my backup of stock n flashed that, all good.
I then install rom manager again and flash the rom I liked again, this time no problem, but when it loads up the home button and search button are not working
So i decide on a factory reset, I select wipe everything including sd just to be sure but it comes up "error null"???
So now I wipe the sd manually and then do the reset and it works, ok, I re load everything on from scratch and all is good, but when I installed rom manager it says that clockwork recovery IS NOT installed again
Can anyone here work out from my ramblings WTF is going on???
I dont get why the font changer all of a sudden caused a boot loop, as I had changed font about 15 times with it without issue, also why clockwork recovery will not stick anymore after a reboot, when before it did and I have not changed a thing!
Cheers!!!
Rename install-recovery.sh in system/etc to something else, flash cwm recovery again, this time it'll stick until you install a stock rom again.
Rom manager is causing more problems than it's saving time, hence I don't use it.
Sent from my Nexus S using XDA App
Thanks for the reply, can you go into detail on what exactly I need to do to get clockwork to stick? I still hold noob status!
Thanks!
Also rom manager seems fine, I flashed loads of roms with it with no issue, I also rebooted a few time at least between flashes so I dont get why clockwork suddenly decided to jump ship.
It was the font changer that f&%ked it all up for me, or anim mod (which I wont touch now even tho I miss the wicked transitions).
When using Font Changer, it's better to do a reboot manually instead of selecting Reboot from within the program. That sometimes cause me a boot loop too. But after turning the phone off / on a.k.a. "reboot manually", the phone boots fine.
To elaborate what rentaric said, use Root Explorer and go to /system/etc/, there should be a file named install-recovery.sh. This file is responsible for flashing the stock recovery every time the phone boots. If you rename it to something else e.g. install-recovery.sh.bak then CWM will stick on reboot.
Thanks, but when I get into the /system/etc/ there is not file called install-recovery.sh.
The only .sh in there is init.goldfish.sh
Any ideas???
bump...............
Flash cwm rec and either stock or custom rom.
Stock rom incl the .sh you want.
Sent from my Nexus S using XDA App
I've read on these forums that using Clockwork on the I9023 is a no-go. Serves up incompatible ROMs, etc.
BTW, I'm looking to root my I9023. Can the OP please point me to the method he used.
athani said:
I've read on these forums that using Clockwork on the I9023 is a no-go. Serves up incompatible ROMs, etc.
BTW, I'm looking to root my I9023. Can the OP please point me to the method he used.
Click to expand...
Click to collapse
LINK: http://forum.xda-developers.com/showthread.php?t=1007782
Please read the whole thread, if I had it would have saved me half a night scratching my head...lol
rentaric said:
Flash cwm rec and either stock or custom rom.
Stock rom incl the .sh you want.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yeah I have a custom rom installed, supercm7, but the install-recovery.sh. that I have been told is causing the problem of clockwork disappearing is not in the /system/etc/ folder, so I am asking if there is anything else that could be causing me to have to re flash clockwork via my pc every time I want to change rom?
I will tell you exactly what happens.
1. I go into rom manager
2. download a rom and choose flash rom from sd card
3. it asked if I want to wipe etc, i select yes
4. phone re boots and I get ! with an android
5. I pull the battery, hold volume up n power and boot / connect to my pc
6. re flash clockwork via SDK
7.the phone then load the new rom on its own
Before it would just flash the rom without me having to install clockwork again.
install-recovery.sh is only there if you're using a stock android rom.
"so I am asking if there is anything else that could be causing me to have to re flash clockwork via my pc every time I want to change rom?"
ROM Manager.
It's not a reliable working tool for ME as I'm changing ROMs/kernels on a regular basis and it might not work reliable the one time you need it.
Thanks for that, I may just sack rom manager then.
Its a shame as I flashed several roms with it without issue.
Oh well, loving this supercm7 so gonna stick with it untill an update comes out.
Many thanks to all who have replied, clicking the thanks buttons now!
I had the same problem but i installed a previus recovery and works fine formeforme
Sent from my Nexus S 4G using XDA Premium App
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
yuma80 said:
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
Click to expand...
Click to collapse
The problem with ROM Manager is that it messes up the files when flashing a ROM or any file. It is more advised to use CMW Recovery.
yuma80 said:
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
Click to expand...
Click to collapse
Rom Manager should not be used on the G2x. If you flash a rom and something goes wrong and you can not boot you are dead in the water. Use Nvidia CWM instead.
http://forum.xda-developers.com/showthread.php?t=1056847
Yes thanks. I understand that I shouldn't use ROM Manager, but I want to know what it does and why it doesn't work. For starters anybody know where it writes CWM to?
Worse comes to worse I'm just going to dump /dev/block/mmc* and look for strings or disassemble the apk or something...
yuma80 said:
Yes thanks. I understand that I shouldn't use ROM Manager, but I want to know what it does and why it doesn't work. For starters anybody know where it writes CWM to?
Worse comes to worse I'm just going to dump /dev/block/mmc* and look for strings or disassemble the apk or something...
Click to expand...
Click to collapse
I've always been curious about the details of a 'fake flash' too.. please let us know if you figure out any details.
Rom manager has been around since the original Droid from Verizon. The fake flash you refer to isn't actually a fake flash. It actually flashes CWM recovery. It just doesn't work on this particular phone. I may be wrong on the exact details but the G2x partitions and drivers require the use of NVflAsh to install the CWM. However, there are many phones that once they have been rooted, the user can install Rom Manager and use the Flash Recovery option to install their CWM recovery. There are also times when a particular recovery version (ie.. 5.0.5. Or 4.6.3) works better than another on one particular phone. Rom manager allows users an easy way of flashing between those CWM versions by simply pushing the flash button.
So in summary of a long response... it is only called a fake flash because it looks like it worked on our phone , but in fact it does not. We have to use NVflash to flash our recovery.
If it looks like I'm remotely right ( which I think I am..) hit that thanks button. (Shameless request, I know)
From my understanding, the "fake flash" that ROM Manager does is that it doesn't actually flash CWM like NVFlash does (on the recovery partition) but still puts the CWM files on your SD card saying that you do have it installed (sdcard/clockworkmod) so when you try to flash/install a ROM, it can't put it anywhere. I don't think it will flash anything, but people mess up their devices by wiping data/system and such...
OR...
Maybe it does flash CWM to your device but it has the partition tables all messed up?
One or the other lol, it's just a guess for both options but I believe the first one is right.
I've wondered for a while why rom manager is included in roms for the g2x when it's not advised to use it
Sent from this
DorisTheHeavy said:
I've wondered for a while why rom manager is included in roms for the g2x when it's not advised to use it
Sent from this
Click to expand...
Click to collapse
To rename your nandroid backups .
buru898 said:
To rename your nandroid backups .
Click to expand...
Click to collapse
I never thought about that. I was always unsure what flashing CWM with ROM Manager would do when it's already on my phone using NVFlash.
Since our phones have a dual partition in it. I think it flashes to the internal 1 gig memory so then loading another rom writes over it.
Sent from my LG-P999 using xda premium
OK, I finally had some time to do some poking around. Some of this is guess-work since I was too lazy to verify 100% exactly what it does when you specify that you're running a G2X.
Anyway, in it's settings DB it says this phone's recovery partition is read-only, and there's no flash command set, so I guess it doesn't try to flash it directly. It looks like it's relying on the Google stock recovery image to do the flashing instead, so it downloads a recovery-update.zip to the SD card and writes a script to /cache/recovery and reboots the phone into recovery mode. Google stock recovery would execute the script in /cache/recovery, which says to apply recovery-update.zip, but the actual stock recovery on the phone is either not Google stock, or has been modified; it doesn't bother to execute scripts, it just does a factory-reset (clear /cache, /data, etc) so that's why it doesn't work.
Meanwhile, ROM Manager writes to it's DB that it just flashed CWM version X.Y.Z and happily displays that every time it runs, even though that's not true.
I used NVFlash and moved on with my life.
Hello everyone,
I just bought a Verizon Galaxy S3 and I am in the process of rooting it. Im kinda freaking out because things really arent going that well for me. So far what I've done is root and unlock bootloader. Here is where the problem starts. When I try to reboot into CWM recovery it just boots me into the normal android recovery. Is this normal? every video I have watched shows people manually rebooting straight into CWM. The only way I can get it to work is if I go into EZ recovery and press "Flash" then "Reboot Into Recovery" buttons.
My second area of confusion is regarding the IMEI backup. Is this something everyone does when flashing roms on this phone? I am very confused as to what I'm supposed to do. Do I use the adb or download a terminal app from the play store? If someone could clarify that would be great !
Sorry if these questions are pathetic but this is my first time doing this and it's a learning experience I geuss. Here are the links to the guides I used for what I have done so far.
http://forum.xda-developers.com/showthread.php?t=1762709
http://forum.xda-developers.com/showthread.php?t=1852255
Thanks
I recently saw someone have a problem getting custom recovery persist, and another member pointed out a step you needed to do to get it to stick. I'll see if I can locate that post and add it to this post.
As far as IMEI goes, you only need to back it up once, and then you are good to go. Perform step a followed by step b in the backup thread.
apacseven said:
I recently saw someone have a problem getting custom recovery persist, and another member pointed out a step you needed to do to get it to stick. I'll see if I can locate that post and add it to this post.
As far as IMEI goes, you only need to back it up once, and then you are good to go. Perform step a followed by step b in the backup thread.
Click to expand...
Click to collapse
Alright thanks, so for most people once they flash it once it should stay every time they reboot into recovery? I have probably the noobiest question of all time, what does flashing CWM recovery even do? is it like flashing a rom where it just gets baked in to the OS permanently? Or does it actually provide a backup of data because I thought thats what nandroids were for.
Havent found exactly what I was recalling as far as the recovery problem, but I found something in a thread below this that makes me think maybe your bootloader wasnt unlocked properly. What version (if any) of ez recovery did you use?
Also, flashing CWM (ideally, at least) replaces the stock recovery with the clockworkmod recovery. Then, when you boot into CWM, that is where you make a backup (nandroid) of your current ROM. Once you have backups made you can quickly switch between ROMs by restoring the nandroids.
I hope I understood your question correctly and also answered it properly.
apacseven said:
Havent found exactly what I was recalling as far as the recovery problem, but I found something in a thread below this that makes me think maybe your bootloader wasnt unlocked properly. What version (if any) of ez recovery did you use?
Also, flashing CWM (ideally, at least) replaces the stock recovery with the clockworkmod recovery. Then, when you boot into CWM, that is where you make a backup (nandroid) of your current ROM. Once you have backups made you can quickly switch between ROMs by restoring the nandroids.
I hope I understood your question correctly and also answered it properly.
Click to expand...
Click to collapse
Yes you did, thank you so much. In the tutorial I used it was saying that the newer versions of EZ unlock were having problems so I downloaded version 1.2. How do I proceed if my bootloader was unlocked improperly? Also, I went in to EZ recovery and flashed CWM and made a nandroid backup if this matters.
Thanks so much for your help.
If you used version 1.2 then my point was moot. So you can only get into CWM if you install CWM from ez recovery and then hit reboot into recovery? If you do the hold vol up + home button while powering on it always takes you to stock recovery?
Yep its very weird. Not sure what to do.
Someone else will likely be able to chime in on how to correct this, unfortunately (or fortunately? lol) it hasnt happened to me so I havent had to deal with it. Its not a huge deal so I wouldnt worry about it.
Personally I use TWRP recovery. You can try that and see if it will stick, you can always go back to CWM later. Try it in ez recovery, or Goo manager from the play store (I use goo manager). If you want to try installing it from goo manager, install the app, hit menu, then select install open recovery script.
K cool. So would it hurt me if I just used ez recovery to flash and reboot everytime I need to get into CWM? Also for goo manager does that install the one you were talking about or CWM?
Sent from my SCH-I535 using xda app-developers app
Goo manager is only for TWRP recovery. And as long as the backups are being stored and you can access them the next time you get into CWM, it doesnt matter. Like I said, hopefully someone will be able to tell you how to correct this issue and we will both learn a thing or two from it.
Did you follow Step 12 in Section 2 in the first link you posted?
You have to make sure to go to CWM v6.0.1 in the drop down and install that version of Clockwork Mod Recovery.
I'm not sure if that's the cause of your issue, but you may want to check into that
Yep i did that
Sent from my SCH-I535 using xda app-developers app
Can someone please help D:
Sent from my SCH-I535 using xda app-developers app
Hey guys new here. I've done a fair amount of searching and cant really find anything that describes my problem. Trying to root my AT&T HOX and failed to put CM10 on the drive before unlocking. Now I have TWRP up right now but when I go to mount and then mount USB storage my PC says that this drive needs to be formatted to work correctly. Honestly not sure what I should do here I tried using HASOON2000's all in one kit but couldn't find the data folder for it. So I started following Cursed4Eva's video tutorial. I have already went to HTC Dev and unlocked it. When I'm in the bootloader menu it says "unlocked" "tampered". Basically Im kinda stuck right now as to what I can do to get CM10 on the one x's drive. Sorry for the super noob questions. Thanks in advance!
Okay so I formatted my drive. I'm able to get into TWRP and Bootloader screen, I get stuck in an infinite loop of the HTC screen with a disclaimer on it if I try to turn my phone on normally. Not sure where to go from here. Do I need to put CM10 in a specific folder and then "install" it from TWRP? Really sorry for the newb questions but I thought that I could handle this and apparently I cant.
Inside of TWRP, there should be a Mount menu button that will allow you to mount your phone to your computer. Simply drop the ROM zip anywhere in that directory, unmount the phone, and choose the Install option on TWRP. Select the ROM zip file and see what happens. If you get errors of "unable to mount drive" or the like, you may have to reflash the factory RUU and start over. Did that my first time trying to flash, it's a little sucky.
You can also do this from the fast boot bootloader menu with adp push.
Well I forgot upload boot.img can I just do that right now and "install" it? Will it just install CM10 and I should be good from there? Not sure what the adb push is. I have a folder with the documents, boot.img, adb, adbwinapi.dll, and fastboot.
Okay update I got CWM-SuperSU-v0.96.zip installed so I have root access. I also have TWRP installed. I dont think that I have a Kernal on my phone or if it is then its not working correctly. In my bootloader screen it says **tampared** and **unlocked**
I might need to reflash the factory RUU (I assume Factory ROM?) and try again I guess.
You should just be able to select the entire zip and install that through TWRP. I've been told that if your hboot version is 1.14, you might have to fastboot the boot.img separately. The ROM/Kernel set I used both took care of that for me via Aroma installer, but it's something to keep in mind.
Well Im far to newb for this so I will try to put my phone back to RUU and try again another day! After doing more research I found some people say that TWRP 2.3 doesnt work for the AT&T 2.20 and that you have to use 2.2 TWRP. Can anyone confirm this? Also learned quite a bit from this failed attempt. Please tell me if Im correct, Need to unlock the phone with HTCDev, upload the boot.img via fastboot, install TWRP, mount the "sdcard" flash the rest of the rom? Does this sound correct?
I'm on 2.2 using twrp 2.3.1.0. From what I've read, different roms tend to recommend different recovery apps/versions.
As for the ordering of the install process, I would install the recovery first thing after rooting because you'll need that to flash superuser. A lot of installers will actually use superuser during the installation, so you'll want to make sure that's squared away first.
Sent from my HTC One X using xda app-developers app
So you just load the rom after you have your phone unlocked and the recovery app (TWRP) and SuperSU installed?
I really appreciate the help! Thank you!
Sounds like you got it, hope everything goes well. Good luck!
Sent from my HTC One X using xda app-developers app