Database Users

2.1 sucks...how can I get 1.5 back?

Not sure what they did on this thing. I thought 2.1 was supposed to IMPROVE performance...and add some BT functionality.
I got no BT improvement. Instead, I got:
1. Random reboots
2. Slow/crashing Navigation
3. Useless voice recognition on Navigation
4. Random phone calls placed when fiddling with BT
5. Slow opening notifications
6. WIFI won't turn on
I could go on and on...
Sprint says I can't go back to 1.5, but I'm sure there's a way to do it.
HELP PLEASE! I'm rooted, if that helps.
Greg

theres noway. your H-Boot has been updated. thats the end of it. 1.5 just wont work anymore.
Sent from my Hero CDMA using the XDA mobile application powered by Tapatalk

troublestylist said:
HELP PLEASE! I'm rooted, if that helps.
Click to expand...
Click to collapse
Yes it does. Just find a 1.5 ROM for CDMA hero. However, before most of our devs moved on to the EVO almost all of them stop developing 1.5 and moved to 2.1
I would suggest trying out some 2.1 ROMs and see what you like.
If you are rooted you should have put a recovery on your phone that you can get to by pressing home and turning on your phone. The first thing you will want to do is make a nandroid backup in case you don't like things. Then stick a ROM on your sdcard. Select all the wipe options except for battery and rotate and then flash a new ROM.

Id try wiping and reloading a 2.1 rom. I never had any of those problems when I went to 2.1.

I'm running the latest DamageControl and can honestly say I am not having any of those issues. I say you should try using a different ROM.

centran said:
Yes it does. Just find a 1.5 ROM for CDMA hero. However, before most of our devs moved on to the EVO almost all of them stop developing 1.5 and moved to 2.1
I would suggest trying out some 2.1 ROMs and see what you like.
If you are rooted you should have put a recovery on your phone that you can get to by pressing home and turning on your phone. The first thing you will want to do is make a nandroid backup in case you don't like things. Then stick a ROM on your sdcard. Select all the wipe options except for battery and rotate and then flash a new ROM.
Click to expand...
Click to collapse
I didn't root until I got 2.1, so I surmise the 1.5 is gone, right?
derekwilkinson said:
I'm running the latest DamageControl and can honestly say I am not having any of those issues. I say you should try using a different ROM.
Click to expand...
Click to collapse
RegawMOD was also recommended. Any reason why to pick one or the other?
Thanks for all the help. Sad that unpaid and unsupported independent developers can do this job better than HTC.
In a best case world, I'd be able to get ad hoc networking to work. I followed the directions but didn't have any success. My ultimate goal was to enable my Hero to display photos wirelessly from my computer. Many programs do it the other way around.
Originally I thought BT would be the easiest wireless protocol, but it seems pretty weak for that sort of data transfer. So 802.11 seemed a better solution...but for some reason Android folks decided to cripple the OS from recognizing ad hoc networks. Odd.

troublestylist said:
I didn't root until I got 2.1, so I surmise the 1.5 is gone, right?
Click to expand...
Click to collapse
You can still flash 1.5 ROMs. You just can't flash the 1.5 RUU.

Great...
Tried Damagecontrol 2.09, did a clean wiped install, and everything seemed fine. Didn't seem much faster, but whatever.
Too bad I waited until I was at work to reboot. Now it's in a bootloop, and I'm stuck at work with no phone.
Sprint sent me a new phone. Once I confirm it's got 1.5, they can have this 2.1-infected POS back.

troublestylist said:
Tried Damagecontrol 2.09, did a clean wiped install, and everything seemed fine. Didn't seem much faster, but whatever.
Too bad I waited until I was at work to reboot. Now it's in a bootloop, and I'm stuck at work with no phone.
Sprint sent me a new phone. Once I confirm it's got 1.5, they can have this 2.1-infected POS back.
Click to expand...
Click to collapse
Look... there's a good chance your new Hero WILL have 2.1 on it. If it does, just root it and install a custom 1.5 rom.

troublestylist said:
Tried Damagecontrol 2.09, did a clean wiped install, and everything seemed fine. Didn't seem much faster, but whatever.
Too bad I waited until I was at work to reboot. Now it's in a bootloop, and I'm stuck at work with no phone.
Click to expand...
Click to collapse
This might mean you simply didn't wipe everything before you flashed the new ROM. Always perform a full wipe before flashing new ROMs.
Take the battery out of your phone. Put it back in and reboot to Recovery (hold Home and press Power). Then select the Wipe option, and go down that list and wipe every single category (I do them each twice just to make sure).
Then go back to the main menu and flash the ROM again. That should probably solve any bootloop problems.
(I don't know if it works exactly this same way with the rooted 2.1 RUU [I'm still on rooted 1.5], so if any of the above is wrong, anybody please correct it...)

HeroMeng said:
Look... there's a good chance your new Hero WILL have 2.1 on it. If it does, just root it and install a custom 1.5 rom.
Click to expand...
Click to collapse
Yeah, I was thinking about that. If so, I might as well keep MY phone and install a 1.5 ROM on it. Less work, and they can have their "new" phone back.
chromiumleaf said:
This might mean you simply didn't wipe everything before you flashed the new ROM. Always perform a full wipe before flashing new ROMs.
Take the battery out of your phone. Put it back in and reboot to Recovery (hold Home and press Power). Then select the Wipe option, and go down that list and wipe every single category (I do them each twice just to make sure).
Then go back to the main menu and flash the ROM again. That should probably solve any bootloop problems.
(I don't know if it works exactly this same way with the rooted 2.1 RUU [I'm still on rooted 1.5], so if any of the above is wrong, anybody please correct it...)
Click to expand...
Click to collapse
Wow, so working with this ROM is like dealing with my kids. I have to tell it everything twice No thanks. Not worth the hassles.
2.1 doesn't do anything better that I can see. I'll deal with wired tethering considering how rarely I use it. The Navigation on 1.5 works better, or at least the voice recognition does.
Why exactly are you still using 1.5??? What custom 1.5 ROM would you guys recommend? Any that have ad hoc networking built in so I don't have to hack it myself?

Any that have ad hoc networking built in so I don't have to hack it myself?[/QUOTE]
Pretty sure all of them do.
Sure wish we could get WPA working for us....stupid kernel.

troublestylist said:
Wow, so working with this ROM is like dealing with my kids. I have to tell it everything twice No thanks. Not worth the hassles.
Click to expand...
Click to collapse
You don't have to do them all twice, I was just saying that I do to make sure -- personal preference. Considering how those wipe options only take like 1 second each, there is no "hassle" of which you speak. Adds maybe an extra 4 to 5 seconds to your day at most.
troublestylist said:
Why exactly are you still using 1.5??? What custom 1.5 ROM would you guys recommend? Any that have ad hoc networking built in so I don't have to hack it myself?
Click to expand...
Click to collapse
I'm not still on a 1.5 ROM, I just haven't yet updated my phone to stock 2.1 using the can't-ever-go-back-again 2.1 RUU. What I meant is that I still have the 1.5 root, but I have been using 2.1 ROMs over top of that for at least a couple months now. I think all these 2.1 ROMs are much faster than 1.5 ever was. Slow speed and lag were my biggest annoyances in stock 1.5.
We probably won't be able to answer all your questions or remove all your doubts. You won't know completely until you try some of them yourself.

If you look in the Wiki there are several 1.5 Roms out there that you can use. However, there are some apps that will only work with 2.1. Once your rooted you can flash any ROM from 1.5 or 2.1. You might also consider an AOSP rom which doesn't have Sense UI. But as I stated in another thread yesterday, most people end up adding apps to try and emulate certain characteristics of Sense UI. I don't like vanilla android, but it is supposed to be faster.
Here are all of the ROMs available. If you want a 1.5 Rom I would suggest Gumbo 1.5c, Modaco 2.2, or Fresh 1.1.

Thanks all. I honestly can't imagine how anyone could find 2.1 faster than 1.5, but I guess maybe once I'll reload 1.5, it may remind me. The "other half" of the people are (like me) saying the CPU can't handle the extra 2.1 features.
I never found 1.5 slow for anything other than phone calls. Now, those are WORSE, and the lag time to do anything else now exists, where it didn't before.
I ran DC all day, and it was just as annoying as the stock ROM. Maybe a little better in places, worse in others.
I guess I'm running "basic" stuff compared to all you guys running heavy apps or something.

Pancake 1.5 running now...refreshingly smoothly Yea, a bit of the glitz is gone, but wow, no lag.
And I have a Navigation program back that has a functional voice recognition. I hesitate to update because I'm not sure how far the revs go under 1.5. I don't want the new version back and I don't know if it's 2.1-only.

Clockwork 3.0.0

Can any give me a link to the newest cw recovery?
Sent from my HTC Vision using Tapatalk

fliint said:
Can any give me a link to the newest cw recovery?
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
http://mrcellphoneunlocker.com/recovery.img

Download it from the RomManager.

Thanks
Sent from my HTC Vision using Tapatalk

its not on the rom manager, (yet)

gnunixguy said:
Download it from the RomManager.
Click to expand...
Click to collapse
Rom manager doesn't list 3.0, only 2.5.1.4 as being the latest

ROMmanager is 3.0.0.2 the recovery has not changed since november 10.
There's nothing wrong with cwm. Maybe one will come with GB.
vision

Does this recovery fix the "off issue" what's new in it?

PlatinumMOTO said:
Does this recovery fix the "off issue" what's new in it?
Click to expand...
Click to collapse
Support for ext4 file systems, that GB uses. If you're using any Android 2.2 based ROM, stay with CWM 2.5.1.3.
Sent from my HTC Desire Z using XDA App

AllWin said:
Support for ext4 file systems, that GB uses. If you're using any Android 2.2 based ROM, stay with CWM 2.5.1.4.
Sent from my HTC Desire Z using XDA App
Click to expand...
Click to collapse
For latest mine says 2.5.1.3

omarsalmin said:
For latest mine says 2.5.1.3
Click to expand...
Click to collapse
Sorry, that was a typo. Fixed.

i see what you mean... and i just installed 3.0.0 and its my color - orange
-- this is just for the gingerbread build by RHCP I am crazy because I am flashing gingerbread to my phone right now. i think ive gone insane.

androidcues said:
i see what you mean... and i just installed 3.0.0 and its my color - orange
-- this is just for the gingerbread build by RHCP I am crazy because I am flashing gingerbread to my phone right now. i think ive gone insane.
Click to expand...
Click to collapse
let us know the results? did your g2 survive?

can anyone let us know if any problems have been discovered with this so far?

warsng said:
let us know the results? did your g2 survive?
Click to expand...
Click to collapse
Yes it did --- I kinda jumped into it and did not really heed Cyanogen's big fat warnings... (reckless flashing) and I couldnt get gapps to flash -- the stuff from rhcp's CM7 thread -- but I got gingerbread going -- then I got distracted all night...woke up this morning trying to make the phone shape up for work -- that was a #fail and the battery seems horrible (then again by no means was it a proper battery test) -- so I decided to restore and that involved new drivers..(for some reason my SDK at work couldnt find the phone so I had to reinstall a fresh SDK (which i named gbSDK)... then found the current recovery at mybrainhurts.com and erased 3.0.0 and fastbooted the froyo recovery back in and restored. easy pie --
gingerbread is a whole 'nother game -- i just hope theres a way to go back and forth between froyo and GB (and eclair/cupcake/donut) without having to fastboot erase and fastboot flash relevant recoveries.
I am sure folks want to know if the new one fixes the "off" mode...and the answer is - i dont know. I didnt check. i kind of hope not because its a feature rather than a bug. theres no quick way to get to recovery when the phone is off. (on to fboot then to hboot then to recovery is too much work)

Is it even worth it to upgrade at this point in time? I'm a bit worried as it seems to be working pretty damn good with what I'm doing now. No partitions on my SD card because I don't care to put apps on it (it's not the fastest class card anyway).

androidcues said:
Yes it did --- I kinda jumped into it and did not really heed Cyanogen's big fat warnings... (reckless flashing) and I couldnt get gapps to flash -- the stuff from rhcp's CM7 thread -- but I got gingerbread going -- then I got distracted all night...woke up this morning trying to make the phone shape up for work -- that was a #fail and the battery seems horrible (then again by no means was it a proper battery test) -- so I decided to restore and that involved new drivers..(for some reason my SDK at work couldnt find the phone so I had to reinstall a fresh SDK (which i named gbSDK)... then found the current recovery at mybrainhurts.com and erased 3.0.0 and fastbooted the froyo recovery back in and restored. easy pie --
gingerbread is a whole 'nother game -- i just hope theres a way to go back and forth between froyo and GB (and eclair/cupcake/donut) without having to fastboot erase and fastboot flash relevant recoveries.
I am sure folks want to know if the new one fixes the "off" mode...and the answer is - i dont know. I didnt check. i kind of hope not because its a feature rather than a bug. theres no quick way to get to recovery when the phone is off. (on to fboot then to hboot then to recovery is too much work)
Click to expand...
Click to collapse
what exactly happened when you flashed the gapps?
at least it didn't fry your g2. i think i might give it a go once i hear a few more success stories. my main worry atm is the ext4 issue. i guess i could just wait until rc1 i guess.
by 'off mode', are you referring to s-off?

warsng said:
what exactly happened when you flashed the gapps?
at least it didn't fry your g2. i think i might give it a go once i hear a few more success stories. my main worry atm is the ext4 issue. i guess i could just wait until rc1 i guess.
by 'off mode', are you referring to s-off?
Click to expand...
Click to collapse
I read the rhcp cm7 thread and i needed to unmount system before flashing the gapps. Thats why gapps failed because i didnt read!
By Off i meant how cw doesnt let the phone turn off when charging... i hope cw 3.0 lets us keep that feature.
Ill probably give it another go this weekend...it works its just if you wanna go back to froyo you need to replace recoveries manually..not a big deal but frankly gingerbread isnt all that more exciting than froyo. I feel i have what i need.in Froyo..the gb keyboard...the gb market... and thats fine with me.
vision

androidcues said:
I read the rhcp cm7 thread and i needed to unmount system before flashing the gapps. Thats why gapps failed because i didnt read!
By Off i meant how cw doesnt let the phone turn off when charging... i hope cw 3.0 lets us keep that feature.
Ill probably give it another go this weekend...it works its just if you wanna go back to froyo you need to replace recoveries manually..not a big deal but frankly gingerbread isnt all that more exciting than froyo. I feel i have what i need.in Froyo..the gb keyboard...the gb market... and thats fine with me.
vision
Click to expand...
Click to collapse
appreciate the info , thanks.

Erase Recovery option
Call me naïve, but if people are making full-blown builds with an image recovery and everything from the CM gingerbread source (which includes the Clockwork Mod recovery 3.0.0 image if I'm reading the source properly), could you just go into ROM Manager, go into Settings, and check the "Erase Recovery" option to allow it to erase the recovery between flashes?
I would test this myself, but I need to go home and make myself fresh builds of CM7 and CM6.2 to try swapping/flashing back and forth between. I can report back once I get around to it later this afternoon.
If I understand that option correctly, applying a full flash of these alpha builds of CM7 should write the new recovery image (v3.0.0.0), and if you need to switch back to CM6, you should be able to just reflash a full build of 6.1.1/6.2 back and it will restore the older recovery image (v2.5.1.8 according to the latest froyo version).
EDIT: Negate that thought. Not sure how you would go about forcing the recovery image flash while in recovery. I got to research this a little more...

What's the use of roms now if recovery is flaky?

I know they are two different things that one relies on the other to work. I understand that rom devs are usually different people than those working on the recovery program.

You gotta start somewhere...

2.5.x.x recovery in the root thread works enough that you can flash roms with no issues.

I don't know if there's a new version of recovery yet. What I meant by flakiness was the issue that some were having, including me, that the phone would always boot into recovery if it was off and you were trying to charge it.

herbthehammer said:
I don't know if there's a new version of recovery yet. What I meant by flakiness was the issue that some were having, including me, that the phone would always boot into recovery if it was off and you were trying to charge it.
Click to expand...
Click to collapse
That's a known issue with ALL clockwork recoveries and there probably will NEVER be a fix.

This may be the case but since the evo and epic used cwm recovery, the shift is the first phone I've experienced this snafu with. Maybe I was just lucky in the past. And yeah, I'm impatient for it to be fixed. I gotta chill out.

Why are you charging with the phone powered off anyway?

Compusmurf said:
Why are you charging with the phone powered off anyway?
Click to expand...
Click to collapse
because bump charging makes unicorn for reals

Compusmurf said:
Why are you charging with the phone powered off anyway?
Click to expand...
Click to collapse
It charges about 10 times quicker.

cloverdale said:
It charges about 10 times quicker.
Click to expand...
Click to collapse
Definitely

So is this recovery causing all the issues that are happening after root? Like the heating up/lag/low quadrant scores?
I'd like to root just to be able to remove things and use wireless tether, but honestly the phone works fine for me right now.

Recovery
You don't actually need to flash the CWM 3.0 recovery. I too like to charge my phone while it's turned off, and after reading about that bug, I just set up my phone to fastboot boot the CWM from preludedrew. What that does is it loads the new custom recovery, but without over-writing the original. From there you can follow the directions to install the custom ROM.
I'm running Evervolv, and so far it seems to be pretty great. Of course you don't get 4G and the camera is buggy still, but you can take pictures and the wifi actually goes faster now.

Then what's the best rom and recovery out for the shift?
Sent from my HTC Vision using XDA App

Quick question guys, since were on the topic of recovery idk if this is the correct "recovery" or not, I came from the evo so its not much different for me but when I did a nandroid backup for my evo I would select backup/restore and select backup google proprietary system files or something like that, I don't get that option with my shift, I just get backup, is that the same?

Compusmurf said:
That's a known issue with ALL clockwork recoveries and there probably will NEVER be a fix.
Click to expand...
Click to collapse
This is not the case with my EVO 4G. I can charge the phone when it's off without the recovery booting up. This is the case with CWM 3.0/2.6.X.X

Where can I download the recovery for the shift?
Sent from my HTC Vision using XDA App

ClockworkMod Touch Recovery For Shift

Now available for the Evo Shift, go try it out and let us know what ya think about it!

If it aint broke, don't fix it.

VICODAN said:
If it aint broke, don't fix it.
Click to expand...
Click to collapse
I don't care I would still like a ICS touch recovery for the shift that works with rom manager.

I saw this a couple of days ago. I wouldn't mind getting it.
Sent from my PG06100 using Tapatalk

Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G

notsointeresting said:
Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G
Click to expand...
Click to collapse
Yeah according to koush's twitter he just "hacked" touch into cwm recovery so I'm sure he'll work on it more. Twrp is a nice recovery and koush is a really good recovery developer so I'm sure he'll make it better if possible. It's funny after finding out about twrp 2.0 being in development before it was even released I asked koush if it was possible to have touch in cwm. Now we're getting it lol.

notsointeresting said:
Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G
Click to expand...
Click to collapse
Using it on my NS4G and honestly I like it better than TWRP. Everything being larger is reassuring, in TWRP I was always nervous because there was such a small area to select. With the items being so close in TWRP I always wanted my volume keys to work so I could make fine maneuvers and in CWM Touch they do. So you can use it just like regular CWM or with touch. Nice if you mess up your touch screen. And of course it also works with ROM Manager. I downloaded it from the site but I may actually donate the $2 for it too.

Touch recovery has just become available on my SHIFT!!! CHECKIN' IT OUT NOW, VERY COOL!
Let Me Put My Shift In U

letmeputdatipin said:
Touch recovery has just become available on my SHIFT!!! CHECKIN' IT OUT NOW, VERY COOL!
Let Me Put My Shift In U
Click to expand...
Click to collapse
I know I tested it for him last night but it's not stable. I wouldn't purchase it quite yet. Download it from the site and test it out. It will boot into recovery for about 5-10 secs format your cache then reboot to system/rom. Strange bug. It would be nice if someone else could confirm this.

sparksco said:
I know I tested it for him last night but it's not stable. I wouldn't purchase it quite yet. Download it from the site and test it out. It will boot into recovery for about 5-10 secs format your cache then reboot to system/rom. Strange bug. It would be nice if someone else could confirm this.
Click to expand...
Click to collapse
I just flashed it through fastboot and haven't seen that issue. I'm actually in the process of making a backup
Edit: Weird thing.. made a backup and rebooted, everything was gone. It brought my ROM completely back to barebones.. even gapps were gone. Restoring with Touch now to see what happens.
Sent from my Android powered Tenderloin

crump84 said:
I just flashed it through fastboot and haven't seen that issue. I'm actually in the process of making a backup
Edit: Weird thing.. made a backup and rebooted, everything was gone. It brought my ROM completely back to barebones.. even gapps were gone. Restoring with Touch now to see what happens.
Sent from my Android powered Tenderloin
Click to expand...
Click to collapse
Hmm, well I did fastboot erase recovery before flashing, not sure if that has anything to do with it. What recovery did you flash this on top of, just the previous cwm recovery? You can also report bugs to him on irc freenode #koush

sparksco said:
Hmm, well I did fastboot erase recovery before flashing, not sure if that has anything to do with it. What recovery did you flash this on top of, just the previous cwm recovery? You can also report bugs to him on irc freenode #koush
Click to expand...
Click to collapse
Yeah I was coming from the previous version of cwm. I just did a restore and everything is fine. Ill probably mess with it a little later when I have some free time.
Sent from my Android powered Tenderloin

I'm not at my pc to try fastboot again but I did flash the previous cwm recovery and it works fine. Then I flashed the new touch recovery with the flash_image command in terminal emulator and I'm getting the same results as before. This is really annoying me because I would like to get this recovery working and I don't know WTH is going wrong here. Maybe it's the new firmware update? I doubt it. Anyways hope to here from more people that try this out.
Edit: when I get a chance later I'll flash with fastboot without running the fastboot erase recovery command and see how it goes.

I must have got lucky... I used joey krim's GUI Flash App and flashed it over the top of the prior clockwork mod recovery... I'll spend a little time tonight trying to replicate...
Sent from my PG06100 using Tapatalk

Well just used the touch recovery to flash my first ROM and had no issues. Maybe my first experience was fluke.
Anyway, liking this recovery so far.

I'm gonna be using GUI flash like Drob since its just easier for me

question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?

jrny99 said:
question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?
Click to expand...
Click to collapse
I'm nit sure about that (although I feel it should be .zip but probably wrong), but you could use Flash Image GUI from the Market or use fastboot from your PC. You'd just stick the .img file in the same folder as fastboot, cd there and type "fastboot flash recovery whateveryounamedit.img". Personally I like Flash Image, works well for flashing kernels too.

jrny99 said:
question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?
Click to expand...
Click to collapse
Yeah, just to reiterate what J-Ice already said... don't rename the img, just flash through fastboot.

I can confirm this is not working for at least one other person on the latest firmware update via twitter messaging...I've tried GUI, fastboot, flash_image, all same results.

ICS Emulator?

I have an interesting problem/challenge I know if anyone knows the answer it will be here. I would like my Mytouch to play nice with Citrix at work and my understanding is that I need ICS to get that done. This is (was) my first android device I had left stock and I really liked the way sense operated. I rooted it and got S=off and flashed several (like 10) ICS roms and either hated them (without sence) or no camera. Finally just went back to GB. Running RoyalMint and love it. Since I only need ICS to log onto the VPN for work is there a ICS solution - I mean I guess I could flash everytime I need to log on but that seems silly. Maybe an emulator app?

I think there is an app in the play store called boot manager that lets you partition your sd card and let you dual boot. FYI all AOKP, AOSP, and MIUI have working camera for ics.

Thank you
I will try both of those options. Working with the HTC has been difficult about 50% of the ROMs I have tried have failed to flash so the dual boot maybe my best bet.

hmsulli said:
I will try both of those options. Working with the HTC has been difficult about 50% of the ROMs I have tried have failed to flash so the dual boot maybe my best bet.
Click to expand...
Click to collapse
Roms have failed to flash for you? You have got a problem buddy

hmsulli said:
I will try both of those options. Working with the HTC has been difficult about 50% of the ROMs I have tried have failed to flash so the dual boot maybe my best bet.
Click to expand...
Click to collapse
Use 4EXT Recovery to perfom a FULL wipe. If you don't wipe correctly you'll have a bad time. Kind of like in real life.
Good luck with Boot Manager + ICS. Be sure sure enable large boot.img.