I tried to root my EVO 4g LTE, and ran into a problem. I unlocked the bootloader correctly, then flash TWRP. TWRP recovery was not unresponsive to touch. With fear that i might i might screw up the phone, i relocked the bootloader.Ive come to the conclusion that i flashed the wrong version of TWRP for the device. I should have rooted before the OTA update. Ive been waiting for the new ruu for the longest, but screw it. I hate sense. Can anyone help me possibly with the completion of rooting? I am S-on,which i know is a pain.
What version of TWRP did you install, and what software and baseband are you on?
The advice is free....the bandwidth, not so much
FinZ28 said:
What version of TWRP did you install, and what software and baseband are you on?
The advice is free....the bandwidth, not so much
Click to expand...
Click to collapse
Im on software 3.16.651.3. I think i flashed TWRP 2.3.3.0 at the time
You need to be running at the very least TWRP version 2.4.1.0. if you were on the 3.16 OTA prior to root. If so, it also means you got the upgraded touch panel drivers, which are not compatible with the version of TWRP you installed.
The advice is free....the bandwidth, not so much
If you don't like sense you are screwed unless you go through the steps to gain s-off. The 3.16 software included new touch panel drivers that are incompatible with all of the aosp roms out there. The only roms you will be able to install are roms based on 3.16. In order for you to downgrade the touchpanel drivers you will have to get s-off first and then you will be able to install aosp roms after downgrading the touchpanel firmware.
cruise350 said:
If you don't like sense you are screwed unless you go through the steps to gain s-off. The 3.16 software included new touch panel drivers that are incompatible with all of the aosp roms out there. The only roms you will be able to install are roms based on 3.16. In order for you to downgrade the touchpanel drivers you will have to get s-off first and then you will be able to install aosp roms after downgrading the touchpanel firmware.
Click to expand...
Click to collapse
Am i able to s-off this software version? Last time i tried, there wasn't a way to s-off the newest software.
drobe005 said:
Am i able to s-off this software version? Last time i tried, there wasn't a way to s-off the newest software.
Click to expand...
Click to collapse
Yes. You can use Dirty Racun or Facepalm.
The advice is free....the bandwidth, not so much
You should give sense a go,there are some really good sense roms out there(even if not on xda
Sent from my EVO using xda premium
FinZ28 said:
Yes. You can use Dirty Racun or Facepalm.
The advice is free....the bandwidth, not so much
Click to expand...
Click to collapse
even with 3.16.651.3 software? i just dont want to brick it. and do i have to unlock the bootloader again?
drobe005 said:
even with 3.16.651.3 software? i just dont want to brick it. and do i have to unlock the bootloader again?
Click to expand...
Click to collapse
Yes, absolutely
Edit: Here is the link to Facepalm. Supposed to be very easy to run. Just read and understand what you're doing.
http://forum.xda-developers.com/showthread.php?t=2163013
The advice is free....the bandwidth, not so much
FinZ28 said:
Yes, absolutely
Edit: Here is the link to Facepalm. Supposed to be very easy to run. Just read and understand what you're doing.
http://forum.xda-developers.com/showthread.php?t=2163013
The advice is free....the bandwidth, not so much
Click to expand...
Click to collapse
Dont i need to be rooted first? if so, this is the problem i was having from my first question.
drobe005 said:
Dont i need to be rooted first? if so, this is the problem i was having from my first question.
Click to expand...
Click to collapse
Read the instructions, but typically, no. My understanding is that you can run S-off, flash recovery and then flash a rooted ROM and you are all set. The problem you had before was that you needed to use a newer version of TWRP, that's all
The advice is free....the bandwidth, not so much
I just did the facepalm s off this morning and I only hit 2 snags. The first was a driver issue which I adressed and I made a thread for it when I finished the other was the CiD. After running the first 2 commands I realized the $ was already # which means my phone somehow already had the correct CiD. I ended up having to skip that step and also the first command says "adb reboot bootloader" and I always got the responce "device not found" so instead I ran "fastboot reboot-bootloader" I don't know why but my guess is because the driver tool I used sets my device up as an adb android device so maybe its always running commands as adb. To finally achieve s off I ended up running all the commands that say "adb" without actually putting in "adb" I am by no means a developer or expert so please research this solution and talk to someone with developing experience first so you don't end up foundation building materials in your hand. Also I am using the latest version of twrp that I could find as of yesterday and running the viper 4g Rom. The avatar cm10 Rom would not work. I just got my phone a few days ago and they did all the updates before they would hand it over so it was all updated as well. I did have it rooted before doing s off though. If have driver issues though check my post from earlier. Its the only one on my profile lol
Sent from my EVO using xda premium
FinZ28 said:
Read the instructions, but typically, no. My understanding is that you can run S-off, flash recovery and then flash a rooted ROM and you are all set. The problem you had before was that you needed to use a newer version of TWRP, that's all
The advice is free....the bandwidth, not so much
Click to expand...
Click to collapse
Great thank you! and its perfectly fine for me to go through he same process of unlocking the bootloader again, and then flashing the newest version of twrp over the version i have? I tried searching this info in the threads but couldn't find it. Note: i never RUU'd since there isnt one out yet. i just relocked my bootloader after the touch screen wasnt working due to me flashing the wrong version of twrp.
drobe005 said:
Great thank you! and its perfectly fine for me to go through he same process of unlocking the bootloader again, and then flashing the newest version of twrp over the version i have? I tried searching this info in the threads but couldn't find it. Note: i never RUU'd since there isnt one out yet. i just relocked my bootloader after the touch screen wasnt working due to me flashing the wrong version of twrp.
Click to expand...
Click to collapse
PM me if you need some help
drobe005 said:
Great thank you! and its perfectly fine for me to go through he same process of unlocking the bootloader again, and then flashing the newest version of twrp over the version i have? I tried searching this info in the threads but couldn't find it. Note: i never RUU'd since there isnt one out yet. i just relocked my bootloader after the touch screen wasnt working due to me flashing the wrong version of twrp.
Click to expand...
Click to collapse
Just unlock and update your version of TWRP to at least 2.4.1.0 and you'll be golden
I still suggest going S-off at some point, because it makes life easier in the end.
The advice is free....the bandwidth, not so much
Related
Listen up people, there seems to be an epidemic going on in the EVO LTE forums and it's called the Jelly Bean RUU. There are now at least 10 people on these forums that have tried to flash the latest ruu in an attempt to upgrade their phone to Jelly Bean from ICS. This method has totally [email protected]#ed up their phones. The ones that have done this have ended up with hboot 2.09 and that's it. The radios, firmware, and rom remain on what ever they were before the attempt and no way to re-flash. All subsequent attempts at fixing this situation fail. If you want to upgrade, the proper way to do this is re-lock your phone and take the ota, do not run the ruu. There are at least 3 threads from people with this problem and several posts in other threads asking for help. Don't become the next victim.
Sent from my A500 using Tapatalk
cruise350 said:
Listen up people, there seems to be an epidemic going on in the EVO LTE forums and it's called the Jelly Bean RUU. There are now at least 10 people on these forums that have tried to flash the latest ruu in an attempt to upgrade their phone to Jelly Bean from ICS. This method has totally [email protected]#ed up their phones. The ones that have done this have ended up with hboot 2.09 and that's it. The radios, firmware, and rom remain on what ever they were before the attempt and no way to re-flash. All subsequent attempts at fixing this situation fail. If you want to upgrade, the proper way to do this is re-lock your phone and take the ota, do not run the ruu. There are at least 3 threads from people with this problem and several posts in other threads asking for help. Don't become the next victim.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Wish I'd seen this sooner. I got hit too.
There is a possible fix found here http://forum.xda-developers.com/showthread.php?t=2097150
bigdaddy619 said:
There is a possible fix found here http://forum.xda-developers.com/showthread.php?t=2097150
Click to expand...
Click to collapse
I did the relock method but im stock on hboot screen? Any ideas?
lexcoupe2100 said:
I did the relock method but im stock on hboot screen? Any ideas?
Click to expand...
Click to collapse
Have you tried to fastboot unlock again using HTC dev.com? If you can, do that, then fastboot a recovery, then installed a rooted rom...I believe that may work, its been a while. Also for those wanting to upgrade from ICS to JB with full firmware, just install a JB rom and then download firmware for 3.15. I did so and ended up with hboot 2.09, updated radio, etc...or like said, s-off and take the ota.
Sent from my EVO using xda app-developers app
So, I totally effed up, and then found this thread after the fact... (facepalm...) I had originally ran the 3.15 RUU, and then proceeded to keep updating MeanBean, all the way through the rebase to 3.16. So now, I've ended up with:
S-ON
MeanBean 3.07
HBOOT 2.09.0000
RADIO 1.12.11.0809
FIRMWARE 3.16.651.3
PRI Version 2.45_003
I'm guessing this isn't supposed to look like this, because everyone else has Radio 1.12.11.1210 with the new 3.16 firmware... My plan was to relock, flash a stock rom, take the OTA, then unlock again.... But, I figured i'd come here and ask if this was a bad idea, if it would brick my phone, or if anyone had a better suggestion... Any thoughts?
I would get S-off, then flash the 3.16 update. Screw all the locking, unlocking and re-rooting
The advice is free....the bandwidth, not so much
FinZ28 said:
I would get S-off, then flash the 3.16 update. Screw all the locking, unlocking and re-rooting
The advice is free....the bandwidth, not so much
Click to expand...
Click to collapse
I didn't realize i could safely S-off with the new HBOOT.... It would seem my fingers have been far from the pulse of the xda community lately... Thank you for the info, I will go do some research..
Mockingbird946 said:
I didn't realize i could safely S-off with the new HBOOT.... It would seem my fingers have been far from the pulse of the xda community lately... Thank you for the info, I will go do some research..
Click to expand...
Click to collapse
Yep. Dirty Racun and Facepalm both work with the new Hboot.
The advice is free....the bandwidth, not so much
FinZ28 said:
Yep. Dirty Racun and Facepalm both work with the new Hboot.
The advice is free....the bandwidth, not so much
Click to expand...
Click to collapse
I'm thinking about buying another Evo just to try FacePalm hahaha
Sent from my PoS MoPho
I'm thinking about buying another Evo just to try FacePalm hahaha
Sent from my PoS MoPho
Click to expand...
Click to collapse
I have a coworker who wants me to root his LTE. I might try it then, assuming he ever gets the phone to me
The advice is free....the bandwidth, not so much
Will it help?
I'm s-off, and I'm having RIDICULOUS issues with the phone boot-looping right now. The only time I get past the boot animation is when I run the most recent CM nightly, and even then I only get to the wifi screen before it reboots. Do you think flashing the RUU again will help? I'm willing to go all the way back to near-stock (except for losing S-Off), so anything that'll help I'll try.
Thanks!
I wouldn't RUU due to bootloops. What recovery version are you using? Maybe it's just not wiping well.
From my Evo LTE, yup.
RE:
scottspa74 said:
I wouldn't RUU due to bootloops. What recovery version are you using? Maybe it's just not wiping well.
From my Evo LTE, yup.
Click to expand...
Click to collapse
I'm using TWRP 2.4 and I'm doing a full wipe every time (reset, system, both caches). Am I missing something? I cannot, for the life of me, figure out what the deal is. No other ROMs I've flashed even make it past the boot animation. I figured it must be the kernel, so I went back to CM. It get farther, but locks and reboots when setup tries to turn on Wifi.
Any thoughts?
Edit: thinking about downgrading TWRP. What say you?
I would try downgrading TWRP. 2.3.3 or 2.3.1 seem to be the most stable. Unless you have the new tp IMG, I think you need the latest TWRP if you do, (I could be wrong, I don't follow either too closely, as I always use older proven firmware and recovery). That's said, if S-off , tp can be downgraded.
From my Evo LTE, yup.
scottspa74 said:
I would try downgrading TWRP. 2.3.3 or 2.3.1 seem to be the most stable. Unless you have the new tp IMG, I think you need the latest TWRP if you do, (I could be wrong, I don't follow either too closely, as I always use older proven firmware and recovery). That's said, if S-off , tp can be downgraded.
From my Evo LTE, yup.
Click to expand...
Click to collapse
I downgraded to 2.3.3, wiped, ran the Superwipe .zip, and reflashed the CM nightly. I got as far as the homescreen (after I skipped setting up wifi and a Google account) before it locked and rebooted. I really think something is making the data and/or wifi receiver (whatever that part or parts may be) to get too hot, and the phone resets as a safety measure (maybe?). Could this be a kernel issue?
I've tried posting in the help forum to no avail. I would really rather be using my EVO than my Opti S, but I guess the good news is that I'm not out of luck (for service) completely. I REALLY hope it's not a hardware thing.
I had no problem doing the 3.15 RUU to get s-off. Downgraded touchpanel after to flash decks 3.4 had serious lag about a week later. Flashed bk to meanbean 3.09
Sent from my EVO using Tapatalk 2
Hey guys i gota semi bricked EVO LTE on the 3.16 SW i was wondering if anyone can help me fix. I tried to root it and thats what caused this issue. I did the bootloader unlocked, loaded TWRP recovery, then installed SU, then it wouldn't turn on, would only flash to sprint screen.
I have tried to to a full wipe / factory - didn't work
i have tried to load the 3.15 RUU - does not work (it just shows loading the rom forever)
i have tried to load it through fastboot via Ulimited.IO (it just freezes during the loading of the SW)
what else can i try? I seems like everytime the phone tries to take a ROM it will just not respond.
thanks
OK your on the latest firmware I think 3.16 and if your s-on that means you have the new touch panel driver which limits what ROMs will work on your device.
You need to download a ROM with a s-on installer included or pull the boot IMG from the ROM and flash via fast boot because you can't flash kernels easily when your S-ON .You also will need a rom that's compatible with the latest fw. AFAIK most of the sense ROMs will be good to go, I really don't know which ones cause I'm s-off and don't have the tp driver problem.
If you need more info there's s thread stickied in Q&A called "don't panic" that will answer most of questions
Once your up and running you should go about getting S-Off.
SENT FROM MY LTEVO
corcgaigh said:
OK your on the latest firmware I think 3.16 and if your s-on that means you have the new touch panel driver which limits what ROMs will work on your device.
You need to download a ROM with a s-on installer included or pull the boot IMG from the ROM and flash via fast boot because you can't flash kernels easily when your S-ON .You also will need a rom that's compatible with the latest fw. AFAIK most of the sense ROMs will be good to go, I really don't know which ones cause I'm s-off and don't have the tp driver problem.
If you need more info there's s thread stickied in Q&A called "don't panic" that will answer most of questions
Once your up and running you should go about getting S-Off.
SENT FROM MY LTEVO
Click to expand...
Click to collapse
thanks for the info. So i need to get a rom with s-on installer and flash it via fastboot flash zip xxxxxx.zip? But i'm not even sure if i'm rooted. I did install the SU in there, it said okay, but now i cant access the recovery. only fastboot. would this damage the phone in anyways?
thanks
right now its showing
**tampered***
** relocked **
** security warning**
Jewel PVT SHIP S-ON RL
HBOOT - 2.09
RADIO - 1.12.11.1210
OpenDSP - V31.1.0.45.0815
emmc- Boot
oct 18 2012
I just tried to flash MeanBean v309 on it via fastboot and it didn't work? is it because the file is too big? I am pretty sure the bean mean is a S-on ROM
Looks like u need to unlock again. Use the same command as the last time
"Fast boot OEM unlock" or whatever it is. Flash twrp recovery thru fast boot. Once you have twrp installed flash a rooted ROM to gain root.
SENT FROM MY LTEVO
corcgaigh said:
Looks like u need to unlock again. Use the same command as the last time
"Fast boot OEM unlock" or whatever it is. Flash twrp recovery thru fast boot. Once you have twrp installed flash a rooted ROM to gain root.
SENT FROM MY LTEVO
Click to expand...
Click to collapse
took your advice, re-unlocked it and installed TWRP recovery on it, and now i get recovery, but i cant use it because the touch screen does not work so i'm in the process of trying to find a CMW recovery instead and try to install a newer rom.
truwrxtacy said:
took your advice, re-unlocked it and installed TWRP recovery on it, and now i get recovery, but i cant use it because the touch screen does not work so i'm in the process of trying to find a CMW recovery instead and try to install a newer rom.
Click to expand...
Click to collapse
Do not use CMW. It was abandoned a long time ago for our phones. Something about it screwing up partitions. Install a new version of TWRP. 2.4 or higher. And Venom rom has an s-on installer for sure. Other roms might have one but I'm not sure which ones. Stay away from CMW.
The s-on installer is just an installer added to the ROM zip so that you don't have to flash the boot.img seperately. Just get a working version of TWRP and flash Venom (or other s-on friendly rom). That should work.
tilltheend714 said:
Do not use CMW. It was abandoned a long time ago for our phones. Something about it screwing up partitions. Install a new version of TWRP. 2.4 or higher. And Venom rom has an s-on installer for sure. Other roms might have one but I'm not sure which ones. Stay away from CMW.
Click to expand...
Click to collapse
ahh okay thanks, i'll give it a shot and report back.
truwrxtacy said:
ahh okay thanks, i'll give it a shot and report back.
Click to expand...
Click to collapse
thanks guys so i got it working! i appreciate everyones help! I ended up loading a new TWRP recovery, and loading the new Meanbean and it works now.
I have one last question, does this mean i can only install roms compatible with 3.16 now? The only reason i went through all of this was because i wanted ICS on it. The new JB diag drivers dont work, and the only way i can make the diag drivers work is to downgrade to ICS. If i try to downgrade will i mess it up again?
thanks
truwrxtacy said:
thanks guys so i got it working! i appreciate everyones help! I ended up loading a new TWRP recovery, and loading the new Meanbean and it works now.
I have one last question, does this mean i can only install roms compatible with 3.16 now? The only reason i went through all of this was because i wanted ICS on it. The new JB diag drivers dont work, and the only way i can make the diag drivers work is to downgrade to ICS. If i try to downgrade will i mess it up again?
thanks
Click to expand...
Click to collapse
Yes, you are stuck on 3.16 roms. Anything below and your touchscreen won't work. I highly recommend going for s-off. Makes everything so much easier. The only other option is to use babyracun from unlimited.io then ruu to 3.15. But if you're doing that you might as well go for s-off.
tilltheend714 said:
Yes, you are stuck on 3.16 roms. Anything below and your touchscreen won't work. I highly recommend going for s-off. Makes everything so much easier. The only other option is to use babyracun from unlimited.io then ruu to 3.15. But if you're doing that you might as well go for s-off.
Click to expand...
Click to collapse
Agreed. I did babyracun and then Facepalm afterwards. Worked great on Windows 7 64bit of which isn't supported by the developers, of course
Delakit said:
Agreed. I did babyracun and then Facepalm afterwards. Worked great on Windows 7 64bit of which isn't supported by the developers, of course
Click to expand...
Click to collapse
Which is what this guy should do since he doesn't have ubuntu and probably doesn't want to use a live disc.
thanks alot guys, i was not aware of the babyracoon. I'll give that a shot.
thanks
i have a question about baby racoon, as it does not have a separate thing for it.
So do i download baby racoon and run all the adb commands, and then run face palm, then ruu?
or do i download baby racoon and run all the adb commands, and ruu then face palm?
sorry i'm a noob
truwrxtacy said:
thanks alot guys, i was not aware of the babyracoon. I'll give that a shot.
thanks
i have a question about baby racoon, as it does not have a separate thing for it.
So do i download baby racoon and run all the adb commands, and then run face palm, then ruu?
or do i download baby racoon and run all the adb commands, and ruu then face palm?
sorry i'm a noob
Click to expand...
Click to collapse
Do steps 6-9 on unlimited io. That will leave your phone at stock 3.15. Then go and find out what facepalm requires and continue with that.
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
I was pretty sure that I had screwed my EVO beyond my ability to recover it. It's pretty noob level stuff, but I haven't been root since my OG EVO - and things were simpler then. Using the WinDroid tool I was able to easily unlock, twrp, and superuser my phone. Moonshine failed 30 or 40 times, so I was not able to achieve S-OFF, but I flashed an AOSP rom anyway and poof - screwed up my phone. I spent the entire day in TWRP / fastboot /flashing stock **** to get my phone working again. At one point in the process I lost the ability to mount usb so I was particularly screwed at that point. I eventually gave in and formated sdcard, then was able to push a stock rom, flashed that a few times, and also a superuser.zip and eventually I was back to running stock 3.17. I've learned something today - I think I'm better off just waiting until December when we get 4.3 and Sense 5 from HTC... Gah - what a day.
Anyway, thank you to the innumerable posts that pointed to the Don't Pank Q&A and elsewhere on the forums. Searching + reading = solution, most of the time. Also, if you (noob to semi-noob) have already OTA updated to 3.17 don't try to S-OFF until a developer has solved this problem, because you are (probably) going to screw it up (and fail).
:good:
SimianJones said:
I was pretty sure that I had screwed my EVO beyond my ability to recover it. It's pretty noob level stuff, but I haven't been root since my OG EVO - and things were simpler then. Using the WinDroid tool I was able to easily unlock, twrp, and superuser my phone. Moonshine failed 30 or 40 times, so I was not able to achieve S-OFF, but I flashed an AOSP rom anyway and poof - screwed up my phone. I spent the entire day in TWRP / fastboot /flashing stock **** to get my phone working again. At one point in the process I lost the ability to mount usb so I was particularly screwed at that point. I eventually gave in and formated sdcard, then was able to push a stock rom, flashed that a few times, and also a superuser.zip and eventually I was back to running stock 3.17. I've learned something today - I think I'm better off just waiting until December when we get 4.3 and Sense 5 from HTC... Gah - what a day.
Anyway, thank you to the innumerable posts that pointed to the Don't Pank Q&A and elsewhere on the forums. Searching + reading = solution, most of the time. Also, if you (noob to semi-noob) have already OTA updated to 3.17 don't try to S-OFF until a developer has solved this problem, because you are (probably) going to screw it up (and fail).
Click to expand...
Click to collapse
Has anyone on 3.17 tried DirtyRacun + BabyRacun for S-OFF? Everyone is saying Moonshine doesn't work, but if BabyRacun works, S-OFF would still be possible using any of the 3 existing methods.
Captain_Throwback said:
Has anyone on 3.17 tried DirtyRacun + BabyRacun for S-OFF? Everyone is saying Moonshine doesn't work, but if BabyRacun works, S-OFF would still be possible using any of the 3 existing methods.
Click to expand...
Click to collapse
Having thoroughly butt-fudged my phone last week, I am going to refrain from experimenting (at least until after I take comps in January).
SimianJones said:
Having thoroughly butt-fudged my phone last week, I am going to refrain from experimenting (at least until after I take comps in January).
Click to expand...
Click to collapse
Maybe if I get bored, I'll experiment with it.
And down the rabbit hole I go . . .
Got BabyRacun to work (after a hex edit to the file) to downgrade my mainver to 3.15.651.16, but the 3.15 RUU won't run. So . . .
I'm going to flash the 3.15 ROM manually through fastboot (boot.img & system.img) and then try DirtyRacun to see if it works. If that doesn't, I may try the 3.15 firmware package and see if that helps.
Alright, so here's where I am. I was able to downgrade my firmware successfully using the 3.16 extended firmware zip from Haus, and now it's just a matter of flashing 3.16 stock rooted so I can Moonshine. At least I proved it could be done, even if it wasn't easy. I believe Moonshine is going to be updated for it to work with 3.17 anyway, so this may have just been an opportunity for me to be reminded of all the crazy stuff I used to do to try and get S-OFF to work, lol.
Captain_Throwback said:
Alright, so here's where I am. I was able to downgrade my firmware successfully using the 3.16 extended firmware zip from Haus, and now it's just a matter of flashing 3.16 stock rooted so I can Moonshine. At least I proved it could be done, even if it wasn't easy. I believe Moonshine is going to be updated for it to work with 3.17 anyway, so this may have just been an opportunity for me to be reminded of all the crazy stuff I used to do to try and get S-OFF to work, lol.
Click to expand...
Click to collapse
But you still do not effectively have S-OFF with 3.17, right? I think you can flash the 3.17 radios separately, though, but I think there might be other stability fixes to sense that you would be lacking. Thanks for experimenting though.
JJW
SimianJones said:
But you still do not effectively have S-OFF with 3.17, right? I think you can flash the 3.17 radios separately, though, but I think there might be other stability fixes to sense that you would be lacking. Thanks for experimenting though.
JJW
Click to expand...
Click to collapse
Huh? Yes, I have S-OFF. What would I be lacking? I re-updated to the 3.17 firmware after S-OFF, and then flashed the 3.17 stock rooted. What fixes would I be missing?
At any rate, I'm running CM10.2 anyway.
Captain_Throwback said:
Huh? Yes, I have S-OFF. What would I be lacking? I re-updated to the 3.17 firmware after S-OFF, and then flashed the 3.17 stock rooted. What fixes would I be missing?
At any rate, I'm running CM10.2 anyway.
Click to expand...
Click to collapse
Ah, I thought that reflashing the 3.17 rooted stock rom would have pushed S-ON. Again thanks for looking at this.
SimianJones said:
Ah, I thought that reflashing the 3.17 rooted stock rom would have pushed S-ON. Again thanks for looking at this.
Click to expand...
Click to collapse
No, flashing a ROM won't put you back S-on. The fact is that Captain was able to find a way to downgrade from 3.17 S-on and still get S-off, which was the ultimate goal in his experiment. Much like back when people downgraded from Hboot 1.15 or 1.19 and used Lazy Panda to gain S-off prior to the Dirty Racun method being available.
Sent from my HTC EVO 4G LTE
I would like to start out with saying that I am not new to rooting/roms but a lot has changed since I went to iOS. I have TWRP accessible and I can push files to my /sdcard/
I have tried several rooms but all of them fail to install.
Can someone please tell me the steps I need to take to go back to either stock or have another ROM working? (RUU fails as well, however it does detect the phone)
Any help is appreciated and trust me I spent hours reading threads so not just posting this for an easy way out.
chirayu said:
I would like to start out with saying that I am not new to rooting/roms but a lot has changed since I went to iOS. I have TWRP accessible and I can push files to my /sdcard/
I have tried several rooms but all of them fail to install.
Can someone please tell me the steps I need to take to go back to either stock or have another ROM working? (RUU fails as well, however it does detect the phone)
Any help is appreciated and trust me I spent hours reading threads so not just posting this for an easy way out.
Click to expand...
Click to collapse
First, this should probably be in the Q&A section
Second, gonna need WAY more info about your phone. I assume you're rooted? S-off or S-on? What hboot version are you on? What version of TWRP are you currently using? What ROM are you on now? What RUU are you trying to use? Gonna have to give a little bit for us to work with.
Edit: Your signature also says you have the Evo Shift? Are you on the write forum?
Greenfieldan said:
First, this should probably be in the Q&A section
Second, gonna need WAY more info about your phone. I assume you're rooted? S-off or S-on? What hboot version are you on? What version of TWRP are you currently using? What ROM are you on now? What RUU are you trying to use? Gonna have to give a little bit for us to work with.
Edit: Your signature also says you have the Evo Shift? Are you on the write forum?
Click to expand...
Click to collapse
I apologize for posting this in the wrong forum, like I was saying I haven't been here in a while and signature is outdated by about 6 years
Heres the info
TWRP v2.7.1.0
S-ON
HBOOT-2.10.0000
RADIO-1.13.11.1105
I had the last leaked RUU installed before I attempted flashing a custom ROM
Thank you for your reply!
chirayu said:
I apologize for posting this in the wrong forum, like I was saying I haven't been here in a while and signature is outdated by about 6 years
Heres the info
TWRP v2.7.1.0
S-ON
HBOOT-2.10.0000
RADIO-1.13.11.1105
I had the last leaked RUU installed before I attempted flashing a custom ROM
Thank you for your reply!
Click to expand...
Click to collapse
Is your goal to flash another ROM or to go back to stock?
If you're going to be trying to flash another ROM I'd highly recommend running rumrunner and getting s-off. Otherwise there are a lot of hoops you'll need to jump through in order to flash ROMs (for starters, you'll need to flash the kernel separately).
Code:
Greenfieldan said:
Is your goal to flash another ROM or to go back to stock?
Click to expand...
Click to collapse
Whichever one is faster, I just want the phone up and running again.
So it's not running at all now? I'm assuming you can boot into bootloader and recovery but nothing else, right? You can run an RUU while in fastboot if I recall, which will give you at least a usable phone. That's also probably the fastest thing to do.
After that I'd highly recommend using rumrunner to get s-off. Otherwise flashing new ROMs will be a bear.
Greenfieldan said:
So it's not running at all now? I'm assuming you can boot into bootloader and recovery but nothing else, right? You can run an RUU while in fastboot if I recall, which will give you at least asable phone. That's also probably the fastest thing to do.
After that I'd highly recommend using rumrunner to get s-off. Otherwise flashing new ROMs will be a bear.
Click to expand...
Click to collapse
RUU fails with errors and it gets stuck at "HTC" screen
Do you have HTC Sync installed on your computer?
Greenfieldan said:
Do you have HTC Sync installed on your computer?
Click to expand...
Click to collapse
Ah, I think something else made me delete it.
That'll do it. You need to have HTC Sync and all of the necessary drivers to run the RUU
Greenfieldan said:
That'll do it. You need to have HTC Sync and all of the necessary drivers to run the RUU
Click to expand...
Click to collapse
Thank you! giving that a try now
greenfieldan said:
that'll do it. You need to have htc sync and all of the necessary drivers to run the ruu
Click to expand...
Click to collapse
error [155]: Uknown error
chirayu said:
error [155]: Uknown error
Click to expand...
Click to collapse
D'oh! I bet your bootloader is still unlocked. It needs to be relocked before running the RUU.
Fastboot command 'fastboot oem lock' ought to do the trick.
Greenfieldan said:
D'oh! I bet your bootloader is still unlocked. It needs to be relocked before running the RUU.
Fastboot command 'fastboot oem lock' ought to do the trick.
Click to expand...
Click to collapse
You're a life saver! at least you can bet I have rooting/unrooting down for this EVO. Just like the old times
Moved to Q&A forum