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.
Related
First off, I've gone through thread after thread hoping to find an answer, but simply have not.
I rooted my phone back in July and don't remember which method I used. I need to get my phone back to stock for warranty (I have a dead strip on my screen) and before I thought, I used SU to get back to S-On, but now I can't get back to stock.
I've tried to run various RUU's, more specifically regaw's version among others, but I haven't had any success. Every time I run an RUU it says that my phone is not connected to my computer. I've also downloaded the PJ75IMG and tried that method as well, but nothing happens.
Phone: Evo 4g LTE
HBOOT: 1.12.000
ROM: UR/EVO 4G LTE SIX
SilverJaw said:
First off, I've gone through thread after thread hoping to find an answer, but simply have not.
I rooted my phone back in July and don't remember which method I used. I need to get my phone back to stock for warranty (I have a dead strip on my screen) and before I thought, I used SU to get back to S-On, but now I can't get back to stock.
I've tried to run various RUU's, more specifically regaw's version among others, but I haven't had any success. Every time I run an RUU it says that my phone is not connected to my computer. I've also downloaded the PJ75IMG and tried that method as well, but nothing happens.
Phone: Evo 4g LTE
HBOOT: 1.12.000
ROM: UR/EVO 4G LTE SIX
Click to expand...
Click to collapse
Do you have HTC Sync installed? I know that has been a issue for myself, if so uninstall that, and you will need to run the RUU for the Firmware you have. Also I have downloaded mine from this website. http://shipped-roms.com/index.php?category=android&model=Jewel
lloydw82 said:
Do you have HTC Sync installed? I know that has been a issue for myself, if so uninstall that, and you will need to run the RUU for the Firmware you have.
Click to expand...
Click to collapse
I don't have HTC Sync installed. How do you know which RUU will work for which firmware?
Sent from my EVO using xda app-developers app
In your settings under about -> Software Information -> More -> Baseband Version.... That will be the RUU you will Run, i had the same issue with my old EVO 3D
lloydw82 said:
In your settings under about -> Software Information -> More -> Baseband Version.... That will be the RUU you will Run, i had the same issue with my old EVO 3D
Click to expand...
Click to collapse
Got the correct firmware, started the process no problem. Now I've got an Error [155]: Unknown and that's as far as it'll take me. I've tried multiple times, and nothing happens. When the phone is supposed to restart it just sits there as if nothing happened to it at all. The RUU instructed me to restart the phone and do the recovery through the program. Once through, it says that I should now try to start the RUU again. and the same thing happens. Am I missing something here?
When running the RUU, are you getting a 155 Error Code?
Yeah, the Error 155 keeps coming up.
Sent from my EVO using xda app-developers app
SilverJaw said:
Yeah, the Error 155 keeps coming up.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Is your bootloader relocked?
lloydw82 said:
Is your bootloader relocked?
Click to expand...
Click to collapse
I have S-On but it still shows "tampered" and "unlocked."
Sent from my EVO using xda app-developers app
SilverJaw said:
I have S-On but it still shows "tampered" and "unlocked."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
you HAVE to relock your bootloader inorder to run the RUU
Follow these steps
http://forum.xda-developers.com/showthread.php?t=1655832
lloydw82 said:
you HAVE to relock your bootloader inorder to run the RUU
Follow these steps
http://forum.xda-developers.com/showthread.php?t=1655832
Click to expand...
Click to collapse
Yep, that's the problem I was having. Once I relocked the bootloader the RUU ran smooth as butter. Took a little while so make sure you have enough battery/have it plugged in.
kidstechno said:
Yep, that's the problem I was having. Once I relocked the bootloader the RUU ran smooth as butter. Took a little while so make sure you have enough battery/have it plugged in.
Click to expand...
Click to collapse
Glad i could help you. I had those same issues so it was just in my knowledge. Now i am S-OFF and love it so far.
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
I have an HTC rezound that was unlocked and rooted by HTC dev method. It has the 2.28.0000 hboot and every ruu I find and try to use tells me hboot failed because mine is to new. I have searched for 2 days on this subject and the reason I am returning to stock is because I can't get into diag mode to flash to cricket. When I enter ##diag it says no network. ##program does nothing either. If anyone could point me in the right direction it would be appreciated.
Sent from my Galaxy Nexus using xda app-developers app
jhr5474 said:
I have an HTC rezound that was unlocked and rooted by HTC dev method. It has the 2.28.0000 hboot and every ruu I find and try to use tells me hboot failed because mine is to new. I have searched for 2 days on this subject and the reason I am returning to stock is because I can't get into diag mode to flash to cricket. When I enter ##diag it says no network. ##program does nothing either. If anyone could point me in the right direction it would be appreciated.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
All ruu's posted here dont work....pm me...i have all the needed files...and i'll guide you through this....your big error that your doing is your going to need to relock the bootloader before doing anything...leaving it unlocked will cause a soft brick
I already relocked the bootloader and it still failed. I am not a total noob flashed lots of radios, hboots, built sense ROMs. This one has me stumped though.
Sent from my Galaxy Nexus using xda app-developers app
jhr5474 said:
I already relocked the bootloader and it still failed. I am not a total noob flashed lots of radios, hboots, built sense ROMs. This one has me stumped though.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
ok an ruu is an exe file not a zip....again i have the files if needed and can show you how...also what you may not be doing whille running the ruu is placing the phone in bootloader then press the fastboot tab...once it says fastboot usb then run the ruu.exe
He is S-ON guys.
jhr5474 said:
I already relocked the bootloader and it still failed. I am not a total noob flashed lots of radios, hboots, built sense ROMs. This one has me stumped though.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
and yes you must be s-off to do this thanks @Flyhalf205
REV3NT3CH said:
and yes you must be s-off to do this thanks @Flyhalf205
Click to expand...
Click to collapse
So, the OP cannot do the full RUU thing.
Can't he just do a factory reset and then boot to one of the custom recoveries and re-flash the latest OTA?
cheers,
john
No op's links have broken software...I have the needed files on my dropbox and media fire account...and no all factory reset does is wipe all data and setting for ROM...and may cause custom ROMs to not boot...ota is only achievable if on stock ROM and there is an update...however I have all those proper files too
Sent from my R3D D347H 4.3 using xda app-developers app
Got it.
One last question, though, since I'm not that savvy...
REV3NT3CH said:
ota is only achievable if on stock ROM and there is an update...
Click to expand...
Click to collapse
...I didn't upgrade to the latest OTA from a previous OTA---I was on the Global Leak---and I installed the ROM found here with absolutely no problems after manually upgrading the firmware to the latest, which is what the OP is on. Fwiw, that ROM still appears to be available via the link in Post 1 of that thread.
cheers,
john
jrredho said:
Got it.
One last question, though, since I'm not that savvy...
...I didn't upgrade to the latest OTA from a previous OTA---I was on the Global Leak---and I installed the ROM found here with absolutely no problems after manually upgrading the firmware to the latest, which is what the OP is on. Fwiw, that ROM still appears to be available via the link in Post 1 of that thread.
cheers,
john
Click to expand...
Click to collapse
that isnt a pure stock ota bud...thats a rom made with includes from it and rooted
This might sound stupid, but your objective here really is to get stockish, correct? With your HBoot you could use this ROM:
http://forum.xda-developers.com/showthread.php?t=2260154
Just make sure to flash boot.img afterwards via fastboot. This is as close to pure stock (only root added) as you can get without S-Off or other trickery. It should suffice for the requirements of the OP.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I've been trying to deal with this problem over in the liquidsmooth thread, but it's clear now that my problems are not related specifically to the rom and that thread isn't really the place for it.
I've lost all cell connectivity. Calls, texts, data, everything. The liquid rom had been working for me for over a week. I've reverted to previous roms both with new flashes and using restore files. I've tried a different recovery. Every time, it acts like I don't have a sim card.
I was suspecting that my sim might be bad, but back on the liquidsmooth thread, it was suggested that I need to RUU back to stock and start over. I'd be willing to do that except the only way suggested was really complicated. I'm S-on and it included ubuntu and the wire trick to get s-off, which I'm hesitant to do. I searched and found another thread with instructions to run an RUU while still s-on, and it seems like it would have worked except that my hboot is newer than the RUU used, and I've been unable to find a newer one.
I tried flashing the stock rom above and flashing the stock recovery that I had from when I first rooted several months ago. It still thinks I don't have a sim card, but otherwise it booted fine until I re-locked to bootloader. Then it wouldn't boot anymore. I guess it still knows that those versions of hboot, the recovery, and the rom don't quite go together.
Is there an RUU that will work with hboot 2.28 to "un-root" my phone without downloading a second operating system and performing surgery on my phone? Are the correct stock rom and recovery out there that I can flash and re-lock? Is there a way to know if that is actually the problem if if it is just my sim card? Are there any other ideas to get my phone functioning again?
Please help!
vigor pvt ship s-on rl
hboot-2.28.0000
radio-2.23.10.0123r/2.23.1.124r
OpenDsp-v1.4.6.0.7708.00.0507
eMMC-boot
Sep 20 2012,17:40:22
There is no RUU for your hboot, need to s-off...
If your SIM is bad, get a new one from Verizon.
Also, is the battery cover on?
Sent from my ADR6425LVW using Tapatalk
mjones73 said:
There is no RUU for your hboot, need to s-off...
If your SIM is bad, get a new one from Verizon.
Also, is the battery cover on?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
On that note... Are using a stock battery cover? Some aftermarket ones are questionable at best. Also, try another SIM, Verizon will replace it free.
Sent from my Nexus 4 using XDA Premium 4 mobile app
acejavelin said:
On that note... Are using a stock battery cover? Some aftermarket ones are questionable at best. Also, try another SIM, Verizon will replace it free.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried using a friend's good sim card and it didn't work. Yes, I'm using the stock battery cover. I guess I'll have to do s-off so I can RUU back to stock.
Ugh . . . This has become so much more than I ever intended to get myself into
amschmid said:
I tried using a friend's good sim card and it didn't work. Yes, I'm using the stock battery cover. I guess I'll have to do s-off so I can RUU back to stock.
Ugh . . . This has become so much more than I ever intended to get myself into
Click to expand...
Click to collapse
You didn't answer my question, is it on the phone while you're testing your connection. Dumb question I know, antenna's are in it though and I've caught people leaving it off and not getting a signal then wondering why...
mjones73 said:
You didn't answer my question, is it on the phone while you're testing your connection. Dumb question I know, antenna's are in it though and I've caught people leaving it off and not getting a signal then wondering why...
Click to expand...
Click to collapse
Sorry, I missed that part of the question. We did it pretty quick, but I think I did put the battery cover. Also, it's not just getting no signal, there is an icon in the notification bar and a big message on the lock screen says I have no sim card at all. That has never happened before, even with the battery cover off. As I look back I realize I failed to mention that important detail. I guess it still couldn't hurt to try a brand new sim card before taking the plunge into s-off. Even if that isn't the problem, at least I'll know for sure, and as you pointed out, its easy and free.
From Mo Versi w/HTC:
Thank you for your support on HTC EVO 4G LTE 4.3 + Sense 5MR update. Below is the link for the final software release that includes support on Win8. Please note the following as this is an RUU update (side load):
*
It is our responsibility to caution you that not all claims resulting or caused by installing this software may be covered under warranty.*Please understand that you will not be able to return your device to the original state or earlier software, and going forward your device may not be held covered under the warranty for all claims resulting from installing this software. HTC bears no responsibility if your device is no longer usable afterwards. We strongly suggest that you do not install this software unless you are confident that you understand the risks involved and the potential consequences both to your device and to your warranty.
*
In order to install the SW, double click the RUU file with your device connected to the PC. The upgrade process will take approximately 20 minutes. Please do not unplug the device from the PC.
*
Download link here
*
Thanks,
Mo
----------------------
EDIT: The official link has been taken down. If you would still like to download the RUU anyway, I have uploaded it here and here.
NOTE: For those having issues updating via the RUU (drivers, Windows 8.1, etc), see this post for an alternative install method.
NOTE 2: There is an updated RUU (4.13.651.4) which was released to some testers from HTC. The update fixes the data roaming issue. It hasn't been released officially, but there is a download link for it here and a mirror here.
Excellent! Thanks Captain
Interesting, I don't think I've ever seen an official update that voided your warranty before.
Should I be worried that it's been stuck on the "sending" screen (on the PC, Windows 7) and the phone on the HTC logo for over 30 minutes?
---------- Post added at 11:47 PM ---------- Previous post was at 11:29 PM ----------
jporter12 said:
Should I be worried that it's been stuck on the "sending" screen (on the PC, Windows 7) and the phone on the HTC logo for over 30 minutes?
Click to expand...
Click to collapse
I restarted it, and it's going this time. No idea what the deal was, but it's working now! Loaded and first booting.
It works,the only thing is supersu. I have to fine one that works with 4.3.
Sent from my EVO using XDA Premium 4 mobile app
djmadclass said:
It works,the only thing is supersu. I have to fine one that works with 4.3.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure what SuperSU has to do with this RUU, but you should be able to flash SuperSU fine (as long as you're using the recovery from my thread).
So to clarify (sorry if this is a stupid question), but will this keep root? Just have to flash SU after? I'm rooted and s-off right now with custom ROM.
Deathalo said:
So to clarify (sorry if this is a stupid question), but will this keep root? Just have to flash SU after? I'm rooted and s-off right now with custom ROM.
Click to expand...
Click to collapse
This is an official RUU from HTC. You will lose root and custom recovery. You'll have to flash the custom TWRP from my thread or Philz's modified CWM, and then you can flash SuperSU for root. Make sure your bootloader is unlocked after running this though - otherwise you won't be able to write permanently to /system.
Thanks, captain. I figure it out. I used the modified twrp.
Sent from my EVO using XDA Premium 4 mobile app
Can anyone using this RUU comment on if their bootloader is still unlocked after?
Still on hboot 1.12.2222 (I think) and can probably figure out flashing supersu through TWRP after I flash TWRP.
Captain, can you link your thread? I've only used your zips for flashing firmware bits, radios, etc.
Thank you,
Skid
Skid71 said:
Can anyone using this RUU comment on if their bootloader is still unlocked after?
Still on hboot 1.12.2222 (I think) and can probably figure out flashing supersu through TWRP after I flash TWRP.
Captain, can you link your thread? I've only used your zips for flashing firmware bits, radios, etc.
Thank you,
Skid
Click to expand...
Click to collapse
My bootloader stayed unlocked the entire time. My thread is in OG Dev. If you flash the RUU, you'll only need a recovery.
I'm experiencing a weird problem with the update. HTC beats audio doesn't enable unless I do the refresh on the blink homescreen or if I disable it, and enable it via settings. Once it goes to another track, it turns off again despite showing the icon that means it is on. I have to repeat the said steps to get it on again. This is using the HTC music app, and Google Play music app. Anyone aware of this? This is all stock with the new RUU.
Sent from my EVO using Tapatalk
c3T said:
I'm experiencing a weird problem with the update. HTC beats audio doesn't enable unless I do the refresh on the blink homescreen or if I disable it, and enable it via settings. Once it goes to another track, it turns off again despite showing the icon that means it is on. I have to repeat the said steps to get it on again. This is using the HTC music app, and Google Play music app. Anyone aware of this? This is all stock with the new RUU.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I believe that's a known issue.
Captain_Throwback said:
I believe that's a known issue.
Click to expand...
Click to collapse
Okay, thank you. I tried searching on Google, and I did not find anything. Will they address this, or is it unlikely?
Sent from my EVO using Tapatalk
c3T said:
Okay, thank you. I tried searching on Google, and I did not find anything. Will they address this, or is it unlikely?
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Well they knew about it before giving us the final version and they didn't fix it. That suggests to me that it's unlikely to be fixed.
Thanks for this, downloaded and I'm gonna give it a shot, I'd like to root after, but I'm a bit confused, Where do I get the modified twrp? and also a little help on how to flash it cause it's been a while I flash something to my evo and with all the keeping up with my note 2, well I feel like new to the htc evo again.
Thanks!
kbrn said:
Thanks for this, downloaded and I'm gonna give it a shot, I'd like to root after, but I'm a bit confused, Where do I get the modified twrp? and also a little help on how to flash it cause it's been a while I flash something to my evo and with all the keeping up with my note 2, well I feel like new to the htc evo again.
Thanks!
Click to expand...
Click to collapse
Look for my thread in OG Dev.
Will my phone stay S-off after taking this RUU?
Sent from my EVO using xda app-developers app
JManekia said:
Will my phone stay S-off after taking this RUU?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Yes.
i thought i read somewhere that needed to relock bootloader, so i did, caused me lots of problems trying to flash ruu. it wouldnt complete ruu, got some htc_fastboot.exe errors, had to restart ruu 3-4x...finally decided to unlock bootloader again and give it a go. completed, no issues so far, all is good again. now shows only unlocked, not tampered unlocked as before ruu
Few issues I've gotten my self into and would like some input
I rooted and attempted to install cyanogen and it failed every time knowing now that the partitions are wrong is why but I advance wiped and and was stuck
I cant get the ruu to run my system is 7 64 bit
I realy want the XXX.ing that runs in hboot but can't find it
I want to run the ruu or the img to restore it and then start from the top if I can
Thank you
weirdfate said:
Few issues I've gotten my self into and would like some input
I rooted and attempted to install cyanogen and it failed every time knowing now that the partitions are wrong is why but I advance wiped and and was stuck
I cant get the ruu to run my system is 7 64 bit
I realy want the XXX.ing that runs in hboot but can't find it
I want to run the ruu or the img to restore it and then start from the top if I can
Thank you
Click to expand...
Click to collapse
To run the RUU from Windows 7 64 bit, be sure to install latest HTC sync manager and connect phone to finalize driver installation. Then try again.
It ain't nothing but a G thing baby... Lg G3 LGSL990
Evolution_Freak said:
To run the RUU from Windows 7 64 bit, be sure to install latest HTC sync manager and connect phone to finalize driver installation. Then try again.
It ain't nothing but a G thing baby... Lg G3 LGSL990
Click to expand...
Click to collapse
I assumed that if the phone rooted and adb and fastboot work than the drivers were installed? Some times the ruu comes up and ask me to install with recomended settings
Htc ruu won't work without sync manager, period.
Sent from my EVO using XDA Premium 4 mobile app
weirdfate said:
I assumed that if the phone rooted and adb and fastboot work than the drivers were installed? Some times the ruu comes up and ask me to install with recomended settings
Click to expand...
Click to collapse
Also, if your bootloader is already unlocked, you will have to relock it for RUU to work.
It ain't nothing but a G thing baby... Lg G3 LGSL990
Gonna try to load sync manager to dusting off my netbook to give that a go with 32 bit co
fizbanrapper said:
Htc ruu won't work without sync manager, period.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Actually, I don't have HTC Sync installed, and it surely works for me. Sync manager allows for the drivers to be installed.
Now having issues getting s-off! Any idea?
weirdfate said:
Now having issues getting s-off! Any idea?
Click to expand...
Click to collapse
Some more info would be helpful. What ROM are you on? What Hboot do you currently have, and what is your radio (firmware) version?
It's important to provide as much information from the start so we can help you. There are currently five ways to gain S-off on the HTC EVO 4G LTE depending upon what software/firmware you currently have.
Magnum_Enforcer said:
Some more info would be helpful. What ROM are you on? What Hboot do you currently have, and what is your radio (firmware) version?
It's important to provide as much information from the start so we can help you. There are currently five ways to gain S-off on the HTC EVO 4G LTE depending upon what software/firmware you currently have.
Click to expand...
Click to collapse
Ya that would help wouldn't it
Software 3.17.651.5 710RD
Factory rooted rom (flashed su 2.01 zip)
Hboot 2.09 0000
I tried rum runner and it gets to about 10 runs and stops
I did realize I don't have busybox but the installers crash and the phone reboots
Firewater
Sent from my EVO using XDA Premium 4 mobile app
fizbanrapper said:
Firewater
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ill need to check this one out. Thank you
no dice! still s-on
if it is of any concern my s-on shows RL after it?
Why don't you just do the RUU back to factory stock and try it from the beginning? It seems like it might save you some time over trying to troubleshoot what is actually wrong.
Try rumrunner again. That's what finally worked for me one time. Rumrunner didn't take the first time and it didn't make a difference running it a second or third time. Firewater didn't work either, but I had success when I went back to rumrunner.
My worthless theory is that, for whatever reason, RR wasn't able to complete a specific critical step, but that FW was able to handle it. But then FW encountered issues on a subsequent step. Going back to RR worked because, this time, FW already took care of the task that RR couldn't do the first time around.
Of course I don't have a stack of evo's sitting around waiting to be s-offed, so I didn't get much of a chance to test my theory. I seem to remain s-off now even after ruu.
Remember to wipe well. It will help prevent a stinky ROM as well as awkward social situations.
I ruu to the one that had sence 5 and then rooted and ran Firewater (2 TIMES) and I'm good! Thank you for all your help