I can't get any ROM to work on my EVO LTE

[wingzero186]

I have successfully unlocked my bootloader and flashed the twrp 2.6.0.0 recovery I backed up the old stock rooted ROM and first tried CM10 jewel direct from cyanogen and the phone was stuck on the boot screen for 20 min the first time then I rebooted and tried again and it set for 30 min the second time I tried CM10.1_4.2.2_Modded_IrocEvo_jewel_20130720 still didn't work same issue but this time it is stuck in a boot loop it does at least get to the boot animation well I wiped again and tried Ouroboros_Build_One and still the same issue I don't understand why the ROM's won't boot and for anyone that looks at this no I did not S-OFF my phone is still S-ON I unlocked the bootloader with the htc dev


What am I missing please any help would be appreciated

I really want to get cm10 to work, before I upgraded to the EVO LTE I had a standard photon that was perma locked so I really don't want to be stuck there again

 

[shadowxaero]

I'm going to assume the boot img isn't flashing correctly because your s on. So go s off it will save you a bunch of headaches

and this is the wrong section from this kind of post. Should be in the q and a.

Sent from my EVO using XDA Premium 4 mobile app

 

[generalmofo]

Go s-off bro.

Sent from my EVO using Tapatalk 4

 

[Threevo]

You're supposed to flash twice bro.
Flash the rom, it'll get stuck on bootloop .. Then flash the ROM again without wiping anything. And you're all good.

Most asop Roms and the new miui won't work tough, the touchscreen won't work because thw new firmware isn't compatible with those Roms

Sent from my EVO using xda app-developers app

 

[Magnum_Enforcer]

You're supposed to flash twice bro.
Flash the rom, it'll get stuck on bootloop .. Then flash the ROM again without wiping anything. And you're all good.

Most asop Roms and the new miui won't work tough, the touchscreen won't work because thw new firmware isn't compatible with those Roms

Sent from my EVO using xda app-developers app

Not totally true. The method of flashing the ROM zip twice mainly works with ROM's that have an S-on kernel installer built in. Typically with AOSP ROM's the kernel has to be flashed using fastboot commands (or Flash Image GUI). Also, any AOSP ROM using the newer 3.4 kernel is compatible with the newest firmware.

OP, hit the link in my sig. I have a guide on how to flash kernels while S-on that should be fairly easy to follow. In the grand scheme of things, though, you should consider getting S-off, as already suggested.

Sent from my EVO using XDA Premium 4 mobile app

 

[wingzero186]

I'm going to assume the boot img isn't flashing correctly because your s on. So go s off it will save you a bunch of headaches

and this is the wrong section from this kind of post. Should be in the q and a.

Sent from my EVO using XDA Premium 4 mobile app

Well I can't find the boot.img file it was not part of the rooting download I got
I tried to go S-OFF I have software 3.16 and hboot 2.09 so I tried moonshine and it keeps giving errors and runs for like 45 min before giving the error :crying:
I am using win 7 so any other suggestions as to how I would get S-OFF so the kernel flashes correctly

 

[decayer177]

Most asop Roms and the new miui won't work tough, the touchscreen won't work because thw new firmware isn't compatible with those Roms

Sent from my EVO using xda app-developers app

Is that still the case? Either TWRP 2.5 works with firmware 3.15 (w/o breaking touch panel) or CM/MIUI now works with firmware 3.16 because I have been going between sense and CM 10.2 without firmware upgrading/downgrading for quite awhile now. I'll check my firmware version later on today, phones too close to dying atm

Sent from my EVO using xda app-developers app

 

[Magnum_Enforcer]

Is that still the case? Either TWRP 2.5 works with firmware 3.15 (w/o breaking touch panel) or CM/MIUI now works with firmware 3.16 because I have been going between sense and CM 10.2 without firmware upgrading/downgrading for quite awhile now. I'll check my firmware version later on today, phones too close to dying atm

Sent from my EVO using xda app-developers app

The newer 3.4 kernel is compatible with the newest firmware, so any AOSP ROM with that kernel doesn't require downgrading the touch panel driver in order to work properly.

Sent from my EVO using XDA Premium 4 mobile app

---------- Post added at 12:36 PM ---------- Previous post was at 12:30 PM ----------

Well I can't find the boot.img file it was not part of the rooting download I got
I tried to go S-OFF I have software 3.16 and hboot 2.09 so I tried moonshine and it keeps giving errors and runs for like 45 min before giving the error :crying:
I am using win 7 so any other suggestions as to how I would get S-OFF so the kernel flashes correctly

The boot.img is in the ROM you downloaded. On your computer, double-click the ROM zip file and you will see it. You can then right-click on the boot.img then extract it to your ADB tools folder and flash it via fastboot. If you need a ROM to get you up and running try flashing MeanBean. It's a Sense ROM with the kernel installer built in.

As far as getting Moonshine to work, you'll have to be more specific regarding the errors you're getting.

Sent from my EVO using XDA Premium 4 mobile app

 

[shadowxaero]

Well I can't find the boot.img file it was not part of the rooting download I got
I tried to go S-OFF I have software 3.16 and hboot 2.09 so I tried moonshine and it keeps giving errors and runs for like 45 min before giving the error :crying:
I am using win 7 so any other suggestions as to how I would get S-OFF so the kernel flashes correctly

What error is it giving exactly?

Sent from my EVO using XDA Premium 4 mobile app

 

[wingzero186]

I don't get an error number the cms prompt says error restart exe and this happens after it has the phone reboot into the bootloader again it runs for 20-30 minutes then says error restart

Sent from my EVO using xda app-developers app

 

[wingzero186]

ok after flashing the boot.img from cm10 I got the rom to boot but the touch pad is not working I am going to bet it is the touch pad drivers while being S-ON is there and way to downgrade the touchpad drivers and later I will give a screen shot of the moonshine error for you guys so I might be able to get a little farther on that front as well

 

[Magnum_Enforcer]

ok after flashing the boot.img from cm10 I got the rom to boot but the touch pad is not working I am going to bet it is the touch pad drivers while being S-ON is there and way to downgrade the touchpad drivers and later I will give a screen shot of the moonshine error for you guys so I might be able to get a little farther on that front as well

Sounds like you flashed the older version that utilizes the 3.0 kernel. If you flash one of the newer nightly versions or from IRC, they have the newer 3.4 kernel that's compatible with the newest touch panel driver, so the downgrade isn't necessary.

Sent from my EVO using XDA Premium 4 mobile app

 

[wingzero186]

OK I got a nightly to work and it is very smooth now I am going to attempt to use moonshine to go S-OFF now that I have this working what other benefits do you get from s off other than not having to flash the kernel separate and radio access

Sent from my EVO using xda app-developers app

 

[Magnum_Enforcer]

OK I got a nightly to work and it is very smooth now I am going to attempt to use moonshine to go S-OFF now that I have this working what other benefits do you get from s off other than not having to flash the kernel separate and radio access

Sent from my EVO using xda app-developers app

Hit the link in my sig and read the portion regarding S-off:thumbup:

Sent from my EVO using XDA Premium 4 mobile app

 

[wingzero186]

Here is the issue I keep getting the phone restarts both times before hand and then just stops at test 3

 

[wingzero186]

Well I tried moonshine on a different win 7 PC and it worked and now I am S-OFF

So the next thing I tried was to flash mean bean and I still had to use fastboot to flash the boot img to get the rom to work I thought once you had S-OFF you didn't have to do that anymore I have TWRP 2.6.0.0 so as far as I know I have the latest recovery just wanted a reason as to why I still had to do this

 

[Magnum_Enforcer]

Well I tried moonshine on a different win 7 PC and it worked and now I am S-OFF

So the next thing I tried was to flash mean bean and I still had to use fastboot to flash the boot img to get the rom to work I thought once you had S-OFF you didn't have to do that anymore I have TWRP 2.6.0.0 so as far as I know I have the latest recovery just wanted a reason as to why I still had to do this

No reason for you to have to fastboot flash the kernel once you're S-off. What happened when you flashed the ROM once you were S-off?

 

[Sloth]

Well I tried moonshine on a different win 7 PC and it worked and now I am S-OFF

So the next thing I tried was to flash mean bean and I still had to use fastboot to flash the boot img to get the rom to work I thought once you had S-OFF you didn't have to do that anymore I have TWRP 2.6.0.0 so as far as I know I have the latest recovery just wanted a reason as to why I still had to do this

I suggest downgrading twrp to v 2.4.1.0 I think 2.6.0.0 is still a little buggy
Click the link in my sig to downgrade

 

[Magnum_Enforcer]

I suggest downgrading twrp to v 2.4.1.0 I think 2.6.0.0 is still a little buggy
Click the link in my sig to downgrade

It's not buggy

Sent from my EVO using XDA Premium 4 mobile app

 

[Sloth]

It's not buggy

Sent from my EVO using XDA Premium 4 mobile app

It is on the One haha.