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
Related
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
Yes, it worths at least for myself. I have hboot 1.50 too and i rooted fast with no problems.
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
More than likely, yes. Most users who follow the guides don't seem to have issues.
The HTC unlock method changes the dynamics a bit from previous common and accepted methods. Many "new" users become between old and current guides.
As far as I've seen, there are only three limitations to hboot 1.5, compared with early "compromised" versions using the AlphaRevX revolutionary method.
1) Kernel is not able to be flashed from recovery mode. Work arounds include: flashing from normal Android mode, my app is great for that, Flash Image GUI. Loading the custom recovery from fastboot. Flashing the kernel from fastboot. Using the "dumlock" method with TWRP.
2) Unable to selectively flash radio images
3) Unable to selectively flash intial splash screens
If I'm missing anything, I'm sure somebody else can post up.
None of those seem like deal breakers to me. Thanks for the fast replies.
It's kind of a ***** just because you have to do a few extra steps but if you know what your doing you won't screw it up.
Yarr. I think I'm going to keep stock for probably just a bit longer. Maybe 1.5 S-Off wont be a problem then. Not bored of it yet, and coming from HTC Hero the thing is a dream.
Root is the way to go Get rid of bloat Also adb isn't hard I always fastboot boot recovery.img and wipe flash no issues
Should I start a new thread on this? I tried to root my HBoot1.5 with 2.17.651.5. When I have went through the HTC unlock process it stays locked. I tried to install the 2.08 version through the original RUU, but it keeps failing. Not sure where I should go from there.
ls3mach said:
Should I start a new thread on this? I tried to root my HBoot1.5 with 2.17.651.5. When I have went through the HTC unlock process it stays locked. I tried to install the 2.08 version through the original RUU, but it keeps failing. Not sure where I should go from there.
Click to expand...
Click to collapse
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
xcpefrmreality said:
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
Click to expand...
Click to collapse
That is what he needs to do to fix .
Sent from my PG86100 using xda premium
DjNawo said:
Yarr. I think I'm going to keep stock for probably just a bit longer. Maybe 1.5 S-Off wont be a problem then. Not bored of it yet, and coming from HTC Hero the thing is a dream.
Click to expand...
Click to collapse
You have Hboot 1.5 with S-off?
G.Newton said:
You have Hboot 1.5 with S-off?
Click to expand...
Click to collapse
No he doesn't from what he said he is stock and asking if he should root
xcpefrmreality said:
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
Click to expand...
Click to collapse
Much obliged!
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
I think some people just got ahead of themselves flashing wrong files. I got a bit worried too first go round after coming from a.Transform.
In my signature I've got a guide/flashing notes that are a bit more updated than some of the stickied threads that may help clear some things up.
Sent from my PG86100 using Tapatalk
What root did you use
Sent from my EVO 3D using XDA Premium
[/COLOR]
Yoyodude1124 said:
What root did you use
Click to expand...
Click to collapse
I used the HTC Unlock (zedomax's video), CWM Recovery, Su 3.07 zip, BusyBox (market), all layed out here:
[Guide] My Hboot 1.50 HTC Unlock/recovery/rom/kernel flashing notes http://forum.xda-developers.com/show....php?t=1495358
Hey thanks again. Yeah I have the newest update, so i would need to get the 2.17 that xcp mentioned. Also, thanks for the guide above.
I have a rooted and S-on Evo. The RUU keeps failing, even after I unrooted via the Superuser app.
Keep getting “ERROR [155]: UNKNOWN ERROR” and then it says it can not update the phone.
And then “Please get the correct ROM update utility and try again.”
I am definitely using the correct RUU version. 1.22.651.3.
Also I have tried two different computers and two different USB cables.
Does anyone know how to get this thing working?
if you updated to the latest OTA update; that usually updates your radios and your Hboot which means the old RUU won't work because it has an OLDER HBoot and radios. Your gonna have to wait till the new OTA becomes available as an RUU to be able to go back to stock.
if you didn't take the OTA 2.13 and you are still on 1.22 then try putting your phone on Fastboot and try it that way.
Edit: Ok so it looks like the latest RUU has been uploaded. Look here http://www.filefactory.com/f/b6eb73c80cc97030/
Thanks, I will try fastboot.
However, as I said in the OP, I am on the same version (1.22.651.3) as the RUU I am using...
ronnienyc said:
I have a rooted and S-on Evo. The RUU keeps failing, even after I unrooted via the Superuser app.
Keep getting “ERROR [155]: UNKNOWN ERROR” and then it says it can not update the phone.
And then “Please get the correct ROM update utility and try again.”
I am definitely using the correct RUU version. 1.22.651.3.
Also I have tried two different computers and two different USB cables.
Does anyone know how to get this thing working?
Click to expand...
Click to collapse
I ran into the same error 155 issue.
I found the solution and it's quite simple. In the instructions to unroot, they forget to mention that you MUST relock your bootloader (instructions below). Once you relock it, then you can run the RUU for 1.22.651.3.....after that, take the stock OTA update.
http://www.theandroidsoul.com/how-to-re-lock-htc-one-x-bootloader/
It helps to have HTC Sync installed too
Sent from my EVO using Tapatalk 2
Is there another site with the new ruu?
Sent from my EVO using Tapatalk 2
running "fastboot oem lock" yields "waiting for device," and this stays on the screen forever. It doesn't work...
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Hypeo said:
It helps to have HTC Sync installed too
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Correct - this is an important step too. HTC Sync must be fully installed, drivers and all.
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
ronnienyc said:
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Click to expand...
Click to collapse
Congrats!
That's my plan, except I'm keeping the stock ROM. If you find a way to Root, let me know - I tried RegawMOD, but I could not get it to work
ronnienyc said:
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Click to expand...
Click to collapse
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
ronnienyc said:
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Click to expand...
Click to collapse
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
Rxpert said:
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
Click to expand...
Click to collapse
I suggest no OTA as well!
Rxpert said:
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
Click to expand...
Click to collapse
That's not always true, and almost all new major releases come with a new hboot. In fact I can't remember any updates on my 0g evo, evo 3d, and evo LTE, that didn't come with a new hboot. The fact of the matter is, people that are s-on and hboot 1.15 won't be able to upgrade their radios and firmware unless they take the ota or run the ruu. This update makes the phone fly and is worth it.
On the other post, regaw mod does work with unlocking and installing twrp, you will have to install a rooted rom afterwards though because regaw mod fails at the rooting step.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
The fact of the matter is, people that are s-on and hboot 1.15 won't be able to upgrade their radios and firmware unless they take the ota or run the ruu. This update makes the phone fly and is worth it.
On the other post, regaw mod does work with unlocking and installing twrp, you will have to install a rooted rom afterwards though because regaw mod fails at the rooting step.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
Sweet this is actually the point where I'm at. HTC Dev unlocked, s-on, hboot 1.15 and rocking twrp. I've been trying to parse through all of the numerous posts on a method to go ahead and install the ota updates. I actually believe I'm 2 down as I haven't updated ever and I got the phone @ launch. I recall reading somewhere that just going back to the stock recovery is a viable option if I want to go w/ the ota updates. I don't really have any interest in different ROMs (I scratch that itch w/ my evo 3d).
tl;dr Whats the least painful way to install the OTA updates post HTC Dev unlock, s-on, twrp recovery, and hboot 1.15?
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
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've had my Evo LTE since launch. Ran many many ROM's. Was on CM11 for quite some time and then all the sudden in my pocket it went into a bootloop. But, not a normal bootloop. It will boot all the way into android, I can unlock the screen sometimes even use it for a while then reboot. Many times it will get to the lockscreen only and then reboot, it will do his cycle indefinitely. I know this type of bootloop usually indicates a kernel/ROM mismatch, but all the ROM's I've been using since this started are the kernel included with the ROM and no customizations. I've done the ViperUU, I've re-flashed firmware. Wiped absolutely everything, except external sdcard. Sometimes it will run for a few hours before it starts again, and sometimes it start rebooting immediately. I'm at the end of my knowledge of what other steps to take. Those of you with mad skills, I petition your expertise please!
What version of cm were you using? Deck's build or nightlies?
Sent from my EVO
numel007 said:
What version of cm were you using? Deck's build or nightlies?
Sent from my EVO
Click to expand...
Click to collapse
Decks!
After it glitched I tried PA, Omni, and stock. Same issue on all.
wolfclan68 said:
Decks!
After it glitched I tried PA, Omni, and stock. Same issue on all.
Click to expand...
Click to collapse
You might want to try a RUU for your current firmware... It might be time for a refresh for your phone, then unlock, root and s-off again...
Sent from my SPH-L900 using Tapatalk
jocarog said:
You might want to try a RUU for your current firmware... It might be time for a refresh for your phone, then unlock, root and s-off again...
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Agreed. I would RUU with the most recent OTA and go from there. If you're S-off you'll still be S-off once you run the RUU. Afterwards, I'd stay stock for a few days and see how the phone acts. If the issue persists you most likely have a hardware issue somewhere. If everything runs okay afterwards you can unlock your bootloader again, install a custom recovery and flash a ROM.
Here is the link to the 3.17 RUU:
http://www.htc.com/us/support/htc-evo-4g-lte-sprint/news/
Sent from my HTC EVO 4G LTE
jocarog said:
You might want to try a RUU for your current firmware... It might be time for a refresh for your phone, then unlock, root and s-off again...
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
FinZ28 said:
Agreed. I would RUU with the most recent OTA and go from there. If you're S-off you'll still be S-off once you run the RUU. Afterwards, I'd stay stock for a few days and see how the phone acts. If the issue persists you most likely have a hardware issue somewhere. If everything runs okay afterwards you can unlock your bootloader again, install a custom recovery and flash a ROM.
Here is the link to the 3.17 RUU:
http://www.htc.com/us/support/htc-evo-4g-lte-sprint/news/
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I didn't realize the HTC RUU was available. I thought ViperUU was the only one. I will give that a shot. Thanks guys! I will report the results.
jocarog said:
You might want to try a RUU for your current firmware... It might be time for a refresh for your phone, then unlock, root and s-off again...
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
FinZ28 said:
Agreed. I would RUU with the most recent OTA and go from there. If you're S-off you'll still be S-off once you run the RUU. Afterwards, I'd stay stock for a few days and see how the phone acts. If the issue persists you most likely have a hardware issue somewhere. If everything runs okay afterwards you can unlock your bootloader again, install a custom recovery and flash a ROM.
Here is the link to the 3.17 RUU:
http://www.htc.com/us/support/htc-evo-4g-lte-sprint/news/
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Posting results as promised. The HTC RUU seems to have fixed the problem, haven't had a reboot since the RUU 3 days now. However during this process I was without a phone for 6 days, I picked up an LG G2. This phone kicks. Got it at Best Buy out the door for $48, CRAZY cheap for such a phone. I guess I'll be getting rid of my EVO.
wolfclan68 said:
Posting results as promised. The HTC RUU seems to have fixed the problem, haven't had a reboot since the RUU 3 days now. However during this process I was without a phone for 6 days, I picked up an LG G2. This phone kicks. Got it at Best Buy out the door for $48, CRAZY cheap for such a phone. I guess I'll be getting rid of my EVO.
Click to expand...
Click to collapse
I'll take it, lol. I need a working test device.
I'd like to test and see if an older RUU works with the new Sense 5 ROM setup
Sent from my EVO LTE
FinZ28 said:
I'd like to test and see if an older RUU works with the new Sense 5 ROM setup
Sent from my EVO LTE
Click to expand...
Click to collapse
Of course that would be the first thing I'd test . Just can't do it on my everyday/work device.