Just bought this refurbished phone and flashed it to pageplus. Got every thing working on the phone with the stock rom (4.1.1)
Unlocked the boot loader, rooted. But did not do take the necessary steps for S-OFF.
The current status is as below
s-on
hboot-1.15.000
twrp recovery installed
Now when i flashed a CM 11/10.2 roms from the below link with the provided gapps i got stuck on the splash screen on reboot.
http://forum.xda-developers.com/show....php?t=2151105
In the process i erased my stock rom back up too.
I did wipe the dalvik, data and system before flashing the rom. I tried the CM 11 and 10.2 roms and their gapps from the above link.
Not sure what i missed while flashing.
Now i am able to get to twrp screens but not sure what to do to get past the splash screen when i reboot. Any guidance is much appreciated.
Being that you are S-on, you will need to flash the kernel separately. Either via fastboot or an app called flash image GUI. This step is necessary for any AOSP ROM but not for sense based, S-on friendly ROMs.
EVOlved human
Hit the top link in my sig for more info.
Sent from my EVO LTE
Thank you atheistevofreak and FinZ28.
That gives me a couple of options to try. Will update how it went once it try these later today.
FinZ28 - I have read the s-on section of your post and that gave me some hope. Thank you for the great write up. I will dig to understand more on kernel flashing. Your post does have some pretty good information on that too.
You're quite welcome:thumbup:
If I were you, I'd look into the Facepalm S-off method. It's actually quite simple and very beneficial to do.
Sent from my EVO LTE
FinZ28 said:
You're quite welcome:thumbup:
If I were you, I'd look into the Facepalm S-off method. It's actually quite simple and very beneficial to do.
Sent from my EVO LTE
Click to expand...
Click to collapse
Sure FinZ28 - That will be the next step once i get this up and running.
atheistevofreak said:
Being that you are S-on, you will need to flash the kernel separately. Either via fastboot or an app called flash image GUI. This step is necessary for any AOSP ROM but not for sense based, S-on friendly ROMs.
EVOlved human
Click to expand...
Click to collapse
Got the meanbean rom installed as you suggested. Every thing is up and running. The meanbean thread had some good information on how to do this for S-ON phones. Thanks a lot.
When you're ready to take the plunge and get S-off, take a look at my post in the link below:
http://forum.xda-developers.com/showthread.php?p=48339416
I wrote another, more detailed guide on how to use Facepalm but at the moment I can't locate the post.
Sent from my EVO LTE
Related
So I've been trying to flash custom ROMs the past few days, and almost all of them end in bootloops. Even the two Stock-Rooted ROMs I found resulted in boot loops, regardless of how wipes & re-flashes I performed. The only ROM that I got to stick was Stock w/ Goodies... What's going on? I'm thouroghly confused. Would being S-OFF fix this?
Thanks in advance
bjb_nyj101 said:
So I've been trying to flash custom ROMs the past few days, and almost all of them end in bootloops. Even the two Stock-Rooted ROMs I found resulted in boot loops, regardless of how wipes & re-flashes I performed. The only ROM that I got to stick was Stock w/ Goodies... What's going on? I'm thouroghly confused. Would being S-OFF fix this?
Thanks in advance
Click to expand...
Click to collapse
Try either viper rom or mean bean rom, both have instructions and a s-on kernel installer, just read the first 4 posts and follow the instructions to the dot... Good luck!
Sent from my EVO using xda app-developers app
jocarog said:
Try either viper rom or mean bean rom, both have instructions and a s-on kernel installer, just read the first 4 posts and follow the instructions to the dot... Good luck!
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Thank you for the quick reply.
So is being S-ON the reason for this problem? Why is that?
Also, is it worth the trouble of me getting S-OFF? I don't want to brick my phone, and apparently that's possible with Rancun?
bjb_nyj101 said:
So I've been trying to flash custom ROMs the past few days, and almost all of them end in bootloops. Even the two Stock-Rooted ROMs I found resulted in boot loops, regardless of how wipes & re-flashes I performed. The only ROM that I got to stick was Stock w/ Goodies... What's going on? I'm thouroghly confused. Would being S-OFF fix this?
Thanks in advance
Click to expand...
Click to collapse
tl:dr version - No, but do it.
You don't NEED to be S-Off, but I STRONGLY suggest you do go S-Off. I was dev unlocked for a long time and it was a pain in my pants to do almost anything.
First things first, are you making sure to wipe everything before you flash? You need to make sure to wipe system, restore, and wipe caches before you flash. Every time, S-On or S-Off. No. Matter. What.
If you don't want to go s-off and that doesn't work, use an app called Flash Image GUI. It's a dollar and works wonders. I have no affiliations with the app or the dev, but it made my life a lot easier when I would flash. What you would do is browse for a kernel image (your rom), check Kernel Image, make sure the two boxes are checked at the bottom and flash the image. When that was done, you have to boot into your recovery and install your kernel again after wiping.
That worked for me every time.
mstrblueskys said:
tl:dr version - No, but do it.
You don't NEED to be S-Off, but I STRONGLY suggest you do go S-Off. I was dev unlocked for a long time and it was a pain in my pants to do almost anything.
First things first, are you making sure to wipe everything before you flash? You need to make sure to wipe system, restore, and wipe caches before you flash. Every time, S-On or S-Off. No. Matter. What.
If you don't want to go s-off and that doesn't work, use an app called Flash Image GUI. It's a dollar and works wonders. I have no affiliations with the app or the dev, but it made my life a lot easier when I would flash. What you would do is browse for a kernel image (your rom), check Kernel Image, make sure the two boxes are checked at the bottom and flash the image. When that was done, you have to boot into your recovery and install your kernel again after wiping.
That worked for me every time.
Click to expand...
Click to collapse
Yup, I'm definitely wiping every time.
So with Flash Image GUI, I flash my ROM with the app, reboot to recovery, then flash the ROM again?
You should get S-OFF to make your life easier, it's free and the easiest way is facepalm... Everything is in the original development thread, is real easy, and yeah your headache/bootloops are due to the need of flash the kernel separately, with S-OFF the process is easier and in one step... Venom team also has a kernel installer for s-on and it's free... Mean bean includes it for free but you have to follow the special instructions for s-on in the OP, good luck!
Sent from my EVO using xda app-developers app
I'm going to make this a lot easier than everyone else has been. No offence people.
DO YOU WANT TO BE HAPPY!? ARE YOU HAVING PROBLEMS IN THE BEDROOM!? IS WORK GETTING YOU DOWN!? FEAR NO LONGER!!!! WITH THE BEST DEVELOPERS ON THIS PLANET HERE TO PROVIDE YOU WITH ALL THE TOOLS YOU NEED TP SATISFY YOUR EVERY NEED! I PRESENT TO YOU: just S-OFF dude.
Enjoy.
Delakit said:
I'm going to make this a lot easier than everyone else has been. No offence people.
DO YOU WANT TO BE HAPPY!? ARE YOU HAVING PROBLEMS IN THE BEDROOM!? IS WORK GETTING YOU DOWN!? FEAR NO LONGER!!!! WITH THE BEST DEVELOPERS ON THIS PLANET HERE TO PROVIDE YOU WITH ALL THE TOOLS YOU NEED TP SATISFY YOUR EVERY NEED! I PRESENT TO YOU: just S-OFF dude.
Enjoy.
Click to expand...
Click to collapse
LOL you made me laugh... Get S-OFF or keep s-on and read a lot to get it to work... Is just an extra step on every single flash...
Sent from my EVO using xda app-developers app
bjb_nyj101 said:
Yup, I'm definitely wiping every time.
So with Flash Image GUI, I flash my ROM with the app, reboot to recovery, then flash the ROM again?
Click to expand...
Click to collapse
Yep - and in recovery just flash it like you would normal app wiping everything if I remember correctly.
Mnstrblueskies responses and verbage are confusing the situation. I'm fairly literate about this and his posts are making my head spin.
If you are S-on, the kernel doesn't get flashed. You need to use flash image GUI app or fastboot to flash the kernel (i.e.boot.IMG) before or after flashing ROM. Preferably before, I suppose. Or use the HTC dumlock feature in TWRP (I'm not real familiar, but instructions are in their op/thread) (I'm S-off).
The easiest way to update firmware/radios will require S-off. If you're already on the latest OTA (3.16), you'll have the latest touch panel drivers and will only be able to use sense 3.16 based ROMs, no AOSP or older sense. This can be remedied by getting S-off and downgrading your TP drivers.
Good luck
Sent from my EVO using xda premium
I think I've done it this time. I was able to unlock the bootloader and also able to put TWRP recovery onto the phone. The mistake I made was trying to flash MIUI to the phone without backing anything up, so here I am and have been for the last 4 hours trying to figure out how to get my phone to boot into a ROM of any sort to try and S-OFF using the FacePalm method.
I honestly don't know what I should do at this point. I can still enter recovery and flash ROMs. Just, none of them actually load. The only time I can get any of them to load is when I flash it via recovery, then flash the boot.img via fastboot. However, when I do it this way, my touch screen within the ROM no longer works. So I can't press or do anything, to give my phone super user permissions. I'm really frustrated and just want to fix my phone. Can anyone offer some help or advice so I can try and fix this sometime between now and my death?
Thank you in advance.
cdboss said:
I think I've done it this time. I was able to unlock the bootloader and also able to put TWRP recovery onto the phone. The mistake I made was trying to flash MIUI to the phone without backing anything up, so here I am and have been for the last 4 hours trying to figure out how to get my phone to boot into a ROM of any sort to try and S-OFF using the FacePalm method.
I honestly don't know what I should do at this point. I can still enter recovery and flash ROMs. Just, none of them actually load. The only time I can get any of them to load is when I flash it via recovery, then flash the boot.img via fastboot. However, when I do it this way, my touch screen within the ROM no longer works. So I can't press or do anything, to give my phone super user permissions. I'm really frustrated and just want to fix my phone. Can anyone offer some help or advice so I can try and fix this sometime between now and my death?
Thank you in advance.
Click to expand...
Click to collapse
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
certain putesbi
FinZ28 said:
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thank you for your reply and help.
I'm running HBOOT 2.09 to be exact. I'm also running TWRP 2.5, so I'm good there as well. Right now I can't boot into a ROM appropriately to achieve S-OFF. I tried creating a Ubuntu Live CD and the Kernel got messed up I guess when putting it on the disc. That was another frustration of mine, lol. I can't achieve the FacePalm method because I can't boot into a ROM to adb shell as super user, since it physically needs to be accepted on the phone.
I'm going to read what you suggested, though, perhaps that will give me the answer.
Edit: I'm going to go with your suggestion of flashing a ROM that's made for 3.16, and see if my touch panel works so I can S-OFF and flash whatever I want. I'll let you know how that goes.
cdboss said:
Thank you for your reply and help.
I'm running HBOOT 2.09 to be exact. I'm also running TWRP 2.5, so I'm good there as well. Right now I can't boot into a ROM appropriately to achieve S-OFF. I tried creating a Ubuntu Live CD and the Kernel got messed up I guess when putting it on the disc. That was another frustration of mine, lol. I can't achieve the FacePalm method because I can't boot into a ROM to adb shell as super user, since it physically needs to be accepted on the phone.
I'm going to read what you suggested, though, perhaps that will give me the answer.
Click to expand...
Click to collapse
What ROM are you trying to run? If it isn't based on software version 3.16 it WON'T WORK.
Sent from my EVO using xda premium
FinZ28 said:
What ROM are you trying to run? If it isn't based on software version 3.16 it WON'T WORK.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Just edited my post. I'm an idiot and didn't completely read your post. My apologies. I'm in the process of getting Viper4G at the moment, to try and achieve S-OFF.
cdboss said:
Just edited my post. I'm an idiot and didn't completely read your post. My apologies. I'm in the process of getting Viper4G at the moment, to try and achieve S-OFF.
Click to expand...
Click to collapse
I was able to get into Viper, tried doing the FacePalm S-OFF and it wasn't successful, for whatever reason. However, at least I'm better off than I was before. Any suggestions from here? I really want to get MIUI on this and not really feeling up to installing Ubuntu tonight.
If not, I really want to thank you. At least I'm able to use my phone again, lol.
cdboss said:
I was able to get into Viper, tried doing the FacePalm S-OFF and it wasn't successful, for whatever reason. However, at least I'm better off than I was before. Any suggestions from here? I really want to get MIUI on this and not really feeling up to installing Ubuntu tonight.
If not, I really want to thank you. At least I'm able to use my phone again, lol.
Click to expand...
Click to collapse
You're going to have to go the Dirty Racun route, unfortunately
Sent from my EVO using xda premium
FinZ28 said:
You're going to have to go the Dirty Racun route, unfortunately
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Guess I'll have to try and make another Live CD. I have no interest in dual booting a copy of Ubuntu at the moment, lol.
Thanks for the help.
FinZ28 said:
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I now was able to get S-OFF. What exactly do I do to downgrade those drivers and flash a ROM that I want?
cdboss said:
I now was able to get S-OFF. What exactly do I do to downgrade those drivers and flash a ROM that I want?
Click to expand...
Click to collapse
If you want to downgrade your touch panel, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1704612
The above thread links to here:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
The touch panel you want to downgrade to is located under the 3.15 firmware, so just follow the directions posted in order to downgrade.
Sent from my EVO using xda premium
FinZ28 said:
If you want to downgrade your touch panel, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1704612
The above thread links to here:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
The touch panel you want to downgrade to is located under the 3.15 firmware, so just follow the directions posted in order to downgrade.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Awesome, thank you. I was able to get the ROM I wanted on here and looks like everything is good to go. Appreciate the help, FinZ28.
cdboss said:
Awesome, thank you. I was able to get the ROM I wanted on here and looks like everything is good to go. Appreciate the help, FinZ28.
Click to expand...
Click to collapse
You're welcome
Sent from my EVO using xda premium
So while in process of s-off once I got to the part when you "fastboot oem rebootRUU" that went through. But right after trying to flash a zip im stuck looking at the blk HTC screen. I was given a "<Failed <remote: 99 unknown fail>". Now its just stuck.
I've been trying to figure out what happened but just have no where else to turn. Please lend a hand.
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
aarsyl said:
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
Click to expand...
Click to collapse
It's not a full RUU in the normal sense. It's the one for Facepalm.
To the OP, did you gain SuperCID prior to running those commands? If not, then the process will fail. You should simply be able to hold the power button down & reboot your phone. Also, as stated above, list your device info so we can make sure you're using the right S-off exploit.
Sent from my HTC EVO 4G LTE
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
z3r0t0l0rEnCe said:
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
Click to expand...
Click to collapse
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
aarsyl said:
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
Click to expand...
Click to collapse
This is odd to me, because I ran rumrunner at least 3 times using just my stock ROM (no custom kernel or anything), and it worked fine every time. I guess the new version of rumrunner added some limitations to make it more generic.
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
z3r0t0l0rEnCe said:
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
Click to expand...
Click to collapse
No, don't. If it fails, don't force it. Reflash TWRP 2.6.3 (not the kit kat version), and try to flash again.
@Captain_Throwback: Yes, I didn't remember needing a custom kernel when I used Dirty Racun, but rumrunner needs it now. Keep in mind that rumrunner isn't for this device exclusively. Maybe that's the purpose of the custom kernel.
i'd wager you're trying to flash files that aren't recovery flashable, then lying to the people who are trying to help you.
i got it running again using capt stock rooted rom. attempting rumrunners s-off again now that i got this part working.
Are you using a custom kernel?
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
now s-off and updated rumrunners hboot. now onto flashing roms finally.
Thank you all that helped me with my stupidness and not reading directions.
Last post. I can't say it enough that you must read read read when it comes to directions. If I would of followed directions as directed I would of never ran into the issues I did. It was a learning experience.
One thing for sure that I took from this experience is adb and directions. I've learned a lot in the last 24hrs alone.
I'd like to thank Capain_throwback and everyone in the irc for the help and you all here that assisted me.
Sent from my EVO using XDA Premium 4 mobile app
The phone is rooted and unlocked. Other info:
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.13.11.0830
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012 15:46:20
I have this: d-h.st/SUc version of TWRP installed (2.6.3.0).
I was following this video: youtube: v=OANqKp0tguE
After the ROM and GAPP installed I rebooted the phone and then the "HTC quietly brilliant" white logo screen looped infinitely.
Other things tried:
At some point after I got back into TWRP recovery I hit factory reset which wiped my SDCard and made it unmountable.
I fixed the unmount issue by formatting the drive on my computer (Win7 x64). I, again, loaded the CM11 Kitkat and the GAPPS back on the SDCard and tried to re-install it.
It seemed to install successfully but it said at the end "Unable to mount to '/cache' ".
Rebooted, infinite boot loop again. Went back in to recovery and wiped.
Found the stock rooted ROM, installed, and booted back in to the default OS.
So my questions is, how do I install Kitkat properly to the device? Or any custom ROM? Any help or advice would be greatly appreciated!
Thank you.
You have to install the kernel separately from the ROM since you're S-on. Hit the top link in my sig for more info. Also, make sure you're using the right recovery (the one posted in the CM11 thread, not on the TWRP site).
You should look at using the Rumrunner method to gain S-off on your phone.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You have to install the kernel separately from the ROM since you're S-on. Hit the top link in my sig for more info. Also, make sure you're using the right recovery (the one posted in the CM11 thread, not on the TWRP site).
You should look at using the Rumrunner method to gain S-off on your phone.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Wow that first link is so informative! Thank you
Is there a significant risk of turning s-on to off? Does it make loading ROMs easier if I have S-Off?
I assume with my version I can only use rumrunner?
rwind said:
Wow that first link is so informative! Thank you
Is there a significant risk of turning s-on to off? Does it make loading ROMs easier if I have S-Off?
I assume with my version I can only use rumrunner?
Click to expand...
Click to collapse
You're welcome
"Significant risk" no. Risk, yes, but then again there is risk in everything in life. A little research and knowledge will help you have a better understanding of S-off versus S-on. It makes ROM flashing very simple, as all you have to do when S-off is flash the ROM zip once and that's it-no fooling with flashing the kernel separately, among other things. It allows a multitude of other things, also.
To answer your last question, yes, Rumrunner is the method you'll need to use being on the latest Hboot/firmware version.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You're welcome
"Significant risk" no. Risk, yes, but then again there is risk in everything in life. A little research and knowledge will help you have a better understanding of S-off versus S-on. It makes ROM flashing very simple, as all you have to do when S-off is flash the ROM zip once and that's it-no fooling with flashing the kernel separately, among other things. It allows a multitude of other things, also.
To answer your last question, yes, Rumrunner is the method you'll need to use being on the latest Hboot/firmware version.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I got rumrunner installed and working, tried installing CM11 Kitkat and everything went smooth and simple. Thank you!
You mentioned something about the TWRP, how do I know which version to get?
Use the version posted in the OP for the CM 11 thread.
Sent from my HTC EVO 4G LTE
Hey guys, I seem to have ran into a few problems while trying to flash a custom rom on my evo 4g lte. Being that I was unable to flash two different roms i decided to go back to stock via the ruu.exe.To root, I unlocked bootloader with htcdev.com and proceeded to root with twrp. While trying to undo I then relocked the boot loader but when the ruu gets to around 93% it fails and gives me an error code. I currently dont have a rom to flash to nor have a recovery to flash anything. When at the bootloader screen i have ''Tampered'', ''Relocked'', and ''Security Warning''. Also I have S-On.
Any help or information is greatly appreciated. I need my phone back lol. I used to flash all the time with my old evo and never got stuck like this before.
Some more information might be useful. List your Hboot version and radio (baseband) version. Really, you should be able to unlock your bootloader again and push a recovery to your phone, at which time you should be able to flash a ROM.
If that doesn't work, hit the top link in my sig and go to the last post in the thread. Hit the link and follow the instructions on how to manually install from the bootloader.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Hit the top link in my sig, and go to the last post in the thread. Hit the link for the 3.17 RUU and follow the instructions on how to manually install it from the bootloader. What happens when you try to enter recovery from the bootloader?
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I am downloading now. I wasnt able to find this version but it is newer than the one I had. When i go to recovery it just goes right back to the bootloader. The error code I was receiving was 140. Btw, I really do appreciate you helping me out!!
FinZ28 said:
Some more information might be useful. List your Hboot version and radio (baseband) version. Really, you should be able to unlock your bootloader again and push a recovery to your phone, at which time you should be able to flash a ROM.
If that doesn't work, hit the top link in my sig and go to the last post in the thread. Hit the link and follow the instructions on how to manually install from the bootloader.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
hboot version=2.09
Radio=1.13.11.0830
Im going to try to unlock the bootloader again and flash a stock rom. Is there only certain types of roms i can use with twrp?
kaintcme187 said:
hboot version=2.09
Radio=1.13.11.0830
Im going to try to unlock the bootloader again and flash a stock rom. Is there only certain types of roms i can use with twrp?
Click to expand...
Click to collapse
You can flash any ROM with TWRP so long as it's for the EVO LTE. Having said that, since you're S-on you'll have to install the ROM kernel separately from the ROM itself. Read the guide in the top link in my sig for more info. There are a few ROM's that are easy to flash while S-on (MeanBean being one of them).
Sent from my HTC EVO 4G LTE
I never had to flash the kernel separately. Just did the normal wipe then flash and after it booted up it would go into a bootloop and I would reboot into bootloader then flash the rom again with it wiping
Took the red pill. HTC evo 4G LTE evilution red pill.
gstanke said:
I never had to flash the kernel separately. Just did the normal wipe then flash and after it booted up it would go into a bootloop and I would reboot into bootloader then flash the rom again with it wiping
Took the red pill. HTC evo 4G LTE evilution red pill.
Click to expand...
Click to collapse
That only works with Sense roms that are equipped with the S-On Kernel installer. If you are coming from the OG Evo, you should know that flashing on this device is not the same at all. You certainly need to read before you act, otherwise you might brick your device. I've been stuck in recovery before from the same problem.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel