• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [CDMA] Evo turns off after boot

jakd

Newbie
Just got this evo 3d last night, but I've had the og evo for a year and I've rooted countless of them. It worked great on stock, I unlocked with htcdev and tried flashing the Nocturnal Venom rom. I'm s-on but I flashed the boot.img separately with fastboot.

As soon as it got to the homescreen, it shut down and rebooted. Over an over. So I tried flashing the ZR3D rom. It looks really cool, but it also shuts off as soon as it boots (once the statusbar appears).

So that makes me think... is there something I'm doing wrong? There is 11% battery left on the device, and I've tried it plugged in.

Thanks for reading, and thanks ahead for your input.
 
mmm now that I think of it, I was on 2.89. Is it because I'm going down to 2.17 while s-on? I flashed the kernel from fastboot, not sure if there's a difference.
 
TWRP, recovery-twrp-shooter-1.1.1.img. I just flashed MeanROM and it seems to be working great. Maybe it was because I went down to 2.17, but if so I would like to understand it. MeanROM is 2.89 but uses the 2.17 kernel. I'm curious.
 
You also may want to try 4EXT recovery, it works really well with the 3VO, it also has smart flash for S-ON which is a real nice feature.
 
the 3d is extremely confusing since for some reason some devs choose to base their roms on older firmware,some on newer :mad:

your best bet,is to double check that the rom your attempting to flash is compatible with the hboot that youre running. bootloops when trying to mismatch firmware and software are a common result.

id also recomend to make efforts to become s-off,so that you can easily change firmware to suit the rom you wish to run. :)
 
mmm now that I think of it, I was on 2.89. Is it because I'm going down to 2.17 while s-on? I flashed the kernel from fastboot, not sure if there's a difference.

Maybe it was because I went down to 2.17, but if so I would like to understand it. MeanROM is 2.89 but uses the 2.17 kernel. I'm curious.

i realized i didnt really answr this that well..

the kernel doesnt really matter as far as the bootloops are concerned. the kernel does need to match the rom,but the boot loop prollem is actually caused by an incompatibility with ICS and the the older hboots,and GB and newer hboots. some critical mountling points were changed for ICS,and thus,the ICS hboot cant boot a GB rom,or vice versa.

the confusion and prollems arise when rom devs modify the mount points for their ICS/JB rom to work with a GB hboot. you now have the same prollem as if you were trying to boot a GB rom- i.e.,incorrect mount points.

some devs have created their roms to work with the new hboot,so you just need to pay attention in the roms OP to know what hboot you need to be on.

on software build 2.89,you should have hboot 1.58,wich is the ICS hboot.
 
Back
Top Bottom