Hello, all.
I've got an EVO 4G LTE running 3.16.651.3 (and pestering the crap out of me to install ...651.4 several times per day). I had been using Wifi Tether with great success after installing SuperSU until - one day, without any changes or updates having been made - the app won't create a hot spot.
I get a message upon starting SU to the effect that "tethering started with errors, check log". Upon exiting the [unsuccessful] tethering mode, I get the message, "Unable to start tethering. Is your device 'rooted'?"
I installed SuperUser some time ago and it kept dropping 'root' so I went to SuperuserSU, then, this happened a few weeks later. It's been several months now, and I've just done without wifi tethering so far. It is a service that has been missed, of course.
I used the TWRP bootloader to perform the installations. S-ON still active, as I don't have the confidence to get to that level of programming (anyone within an hour of Wilmington, DE want a case of beer? :laugh: )
Suggestions gratefully accepted. Thanks in advance.
rteda said:
Hello, all.
I've got an EVO 4G LTE running 3.16.651.3 (and pestering the crap out of me to install ...651.4 several times per day). I had been using Wifi Tether with great success after installing SuperSU until - one day, without any changes or updates having been made - the app won't create a hot spot.
I get a message upon starting SU to the effect that "tethering started with errors, check log". Upon exiting the [unsuccessful] tethering mode, I get the message, "Unable to start tethering. Is your device 'rooted'?"
I installed SuperUser some time ago and it kept dropping 'root' so I went to SuperuserSU, then, this happened a few weeks later. It's been several months now, and I've just done without wifi tethering so far. It is a service that has been missed, of course.
I used the TWRP bootloader to perform the installations. S-ON still active, as I don't have the confidence to get to that level of programming (anyone within an hour of Wilmington, DE want a case of beer? :laugh: )
Suggestions gratefully accepted. Thanks in advance.
Click to expand...
Click to collapse
In my experience dropping root is most often ROM/Install issue. I've never had it be an issue with Superuser or SuperSU. You gave a fair amount of info, but failed to mention specifically which ROM you are on. If your using Titanium Backup or another backup program, do not restore system apps or data. I suggest backing up your apps and full wipe/clean flash. S-off isn't that difficult, like anything else just read through it several times and go for it. It will make life much simpler, at least with flashing your device.
S-OFF:
http://rumrunner.us/
http://moonshine.io/
wolfclan68 said:
In my experience dropping root is most often ROM/Install issue. I've never had it be an issue with Superuser or SuperSU. You gave a fair amount of info, but failed to mention specifically which ROM you are on. If your using Titanium Backup or another backup program, do not restore system apps or data. I suggest backing up your apps and full wipe/clean flash. S-off isn't that difficult, like anything else just read through it several times and go for it. It will make life much simpler, at least with flashing your device.
Click to expand...
Click to collapse
Hey,
Thanks for the guidance. I'm on a stock ROM and don't know that changing that is necessarily a goal unless placing a rooted rom on there helps after doing the root thing successfully.
Here are the particulars of the phone's HBOOT (or whatever it is) screen:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PUT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.12.11.1210
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012,15:46:20
If installing a rooted ROM such as this that I found -
OTA_JEWEL_JB_45_S_Sprint_WWE_3.17.651.4-3.16-651.3_release_334509ls9tpexkjt349evk.zip
...accomplishes the objective of working with Superuser/SuperSU and not being harassed with upgrade requests, then that's fine. Of course, I don't know the first thing about the fellow posting this ZIP file or the file itself.
Is the suggestion to wipe the phone clean, use rumrunner.us (or the other seemingly identical link's version) and then reload apps, or, just reset the phone first/reload apps first and see if that accomplishes the basic root thing?
The help is greatly appreciated.
Peace,
Ted
You can flash the latest stock rooted OTA ROM found in the thread below. It's from a trustworthy source.
http://forum.xda-developers.com/showthread.php?t=2468418
You'll need to use Moonshine to gain S-off. You can hit up the Moonshine thread in Original Development for more info. You'll also need to be on a fairly stock ROM to use it (like the ROM I mentioned above). Afterwards you can flash whatever you like.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You can flash the latest stock rooted OTA ROM found in the thread below. It's from a trustworthy source.
(Link)
You'll need to use Moonshine to gain S-off. You can hit up the Moonshine thread in Original Development for more info. You'll also need to be on a fairly stock ROM to use it (like the ROM I mentioned above). Afterwards you can flash whatever you like.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
NooB alert, sorry: I can flash the above linked, rooted ROM prior to going S-OFF? If so, I'll get right on this.
Thanks, each of you, for your time and contributions.
Yes. I believe you'll need to install the kernel separately from the ROM. Just hit the top link in my sig and scroll down to the section regarding S-on kernel flashing.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Yes. I believe you'll need to install the kernel separately from the ROM. Just hit the top link in my sig and scroll down to the section regarding S-on kernel flashing.
Click to expand...
Click to collapse
Well, thanks to Moonshine and the suggestions to use it, the phone is S-OFF now. It keeps wanting to do a hands-free activation, which sounds suspiciously like a Sprint reprogramming deal. TWRP was already on it, so that's available for installing a rooted ROM, if I understand the process in the correct order of procedures.
I've read and read, yet don't seem to make the connection between flashing a rooted ROM such as this one and a kernel flashing. I gather that a kernel gets the hardware and the software to speak to one another?
If that's the case, I would think a stock rooted rom such as PJ75IMG_3.17.651.4_boot_img_signed.zip would not require that. I really don't feel like messing with the radio package, etc etc etc. Since my phone is not a hobby for me, I'm mostly looking for just making it do a few things I want it to do and then remove boatware, which is why a rooted original has the appeal for the present.
Thanks ten million times for your help, all.
Ooooh!........ Success. Looks like we have root. No successful flash of the rooted ROM, but that can happen in time when we figure it out.
Thanks again, again.
Related
UPDATE: The latest update still is safe. I just installed it and I am still s-off.
UPDATE: The update to Jellybean does not write the secure flag and this method is safe to apply the OTA update with this method and still maintain root access afterwards.
First and foremost, a couple disclaimers.
FIRST, YOU MUST BE S-OFF FOR THIS TO WORK. PLEASE DO NOT TRY THIS IF YOU ARE NOT ALREADY S-OFF.
SECOND, FOR THE OTA UPDATE 1.22.651.3 YOU WILL FOR SURE RETAIN S-OFF. ALTHOUGH HIGHLY UNLIKELY, HTC COULD POTENTIALLY MAKE YOU S-ON IN FUTURE OTA UPDATES. SEE HERE FOR MORE INFORMATION.
To obtain s-off please see this thread: http://unlimited.io/jewel.htm
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out. I don't really theme, mod, or do crazy things with my phone but still want root access. So, I decided since I was s-off, I would give this method a whirl. I am happy to report that I am s-off, with TWRP, fully rooted, and with installing the OTA update. I had a little hiccup but was able to solve that.
So, here is the process. This is kind of a hodge podge of different threads, ideas, devices, and versions of android so if I didn't give you credit, please let me know and I will put you in this thread.
Process for installing a stock recovery. I have already created some stock recovery files so see at the bottom of this post for the zip file that includes the stock recovery. If you wish to use these files, just start with step #10.
IF YOU CHOOSE TO JUST DOWNLOAD THE STOCK RECOVERY AT THE BOTTOM OF THIS POST, SKIP TO STEP #10.
Creating Stock Recovery File Manually
1. Install a stock recovery if you don't already have one.
2. To do so, get the RUU for the version you are running.
3. Run the RUU (don't connect to your phone at all)
4. Navigate to your temp directory on your computer (on windows 7 it is C:\Users\your_user_name\AppData\Local\Temp)
5. Find a folder that looks like it is in the following format "{XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX}" It might help to sort by date modified. The folder should have the current date
6. Inside the folder might be a couple other folders. Navigate through the folder to find a zip that says "firmware" or "rom" (mine said rom)
7. Extract the content to a folder in the same directory called rom
8. Navigate into the rom folder and find two files android-info.txt and recovery_signed.img. Copy those to a directory of your choice.
9. Send those files to a zip folder and name the file "PJ75IMG.zip" without the quotes. Make sure zip is only listed once. If you have file extensions hidden in windows yours will only say "PJ75IMG".
Installing the stock recovery, OTA, and regaining root
10. Place the stock recovery file on the root of your sd card
11. On your phone, head into settings and power and make sure the fastboot option is unchecked
12. Power down phone
13. Once phone is completely shut down, hold the volume down button and press the power on button while keeping the volume down button pressed.
14. It will boot into your hboot (verify it says s-off at the top or don't proceed) and find the file you placed on your sd card and ask you if you want to update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
15. Go to settings>check for updates and check to see if there is an update. Download the update. Once it verifies, click install now. It should install just fine.
16. Once you are up and running, download one of the dirty racun hboots. I used hboot 2.09 img found here. Follow the instructions on the unlimited.io website how to flash the hboot by using fastboot (flashing the zip doesn't seem to be working.
update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
17. Make sure usb debugging is checked under settings>developer options
18. Go download a su zip file. I used this one here and place it on the root of your sd card.
19. Go grab a custom recovery flashable zip (could not find the latest twrp zip) or img (I used TWRP found here. Take the image and place it in your platform tools folder for ADB.
20. Plug in phone while powered on and type in adb devices to make sure you are connected.
21. If you see a device type in
Code:
adb reboot bootloader
22. Your device will boot into your bootloader and you will see fastboot usb (make sure usb debugging was checked if you don't see that).
23. Then type fastboot flash recovery [filename] of the recovery img you downloaded. Once flashed, toggle with the volume up buttons to bootloader and then select recovery. This should boot you into TWRP
24. Once in recovery, install the su zip you downloaded in step 18.
25. Reboot and Enjoy!!!!
You are now rooted with the most current OTA update and all the goodies (radios, PRI, etc.)
This process should hopefully hold true for any future OTA updates if you are S-OFF. The only thing you will have to find is the current RUU to create the stock recovery. If this helped, feel free to thank! Go XDA!
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I don't know. So you don't have to wait at all? Or for the people that aren't accustomed to flashing ROMs or don't care to. I prefer this method for whatever reason and it seems just easier. Personal preference though. The beauty of android and their strong developer network is that it gives the users choices. I can take the OTA update as soon as it comes out and don't have to worry about waiting for anything. Just another method I guess.
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
msimindlessmsi2 said:
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
Click to expand...
Click to collapse
The update firmware is the part that hangs me up. I believe when it was back in the original EVO days that some people were having problems updating their PRI version and it screwed up some things with wimax. That is when I decided I would just accept the OTA to get everything they included in the update and then gain root access through this method.
Again, to each their own. Please try not to clutter up the thread with off topic items. Thanks.
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
im coming from the rezound, i just want the updated firmware! on my rez being s-off i could run ANY firmware ICS, or GB and then go back to whatever rom i was running. im wondering if im s-off, i should b able to do the same thing right.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
The devs state that so that they don't have to spend their valuable time troubleshooting because you didn't flash right. Its always best to do a full wipe, but not always required when flashing an updated version of the same ROM.
1) Nandroid.
2)Wipe Dalvik cache & cache
3) Flash
You retain all data.
If you have issues, then you nand restore and do a full wipe before bugging the devs
bpdamas said:
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out.
Click to expand...
Click to collapse
Lmao! You find that whole process "easier" than waiting for a day? I think it might take the better part of a day to do all that.
Sent from my EVO using xda premium
Thanks for taking the time to do a write-up OP!
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
Agreed.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Definitely agreed.
greyopaque said:
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
Click to expand...
Click to collapse
I know. This is exactly why I root and I can't believe there are so many people against this method. It seems very simple to me and I can have a stock recovery waiting to flash as soon as an OTA update comes out. Oh well.
Thanks for this info. I think I'm like you and not only like the stock experience and its benefits but also prefer diy when possible.
Of course I never seem to stay stock like you but I like doing the steps my self. To each their own is the beauty of android.
Go android!
Sent from my EVO
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
zounduser said:
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Click to expand...
Click to collapse
Very curious on this. Nothing in this method should affect this.
Robbie_G said:
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
Click to expand...
Click to collapse
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Rxpert said:
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Click to expand...
Click to collapse
That's fair, rooting and s-off could also inject malicious code. But so can ROM makers.
I think there's a difference between trying to be safe and being paranoid. If there is a way for someone to make money off of you/steal your identity, eventually they will try. I'm not suspicious of any of the current devs, but it's something we should maybe be more aware of. Look at all the warez Windows out there with malware built in to steal your information.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Totally agree. Its a good thing to learn in my opinion. I broke my Evo 4G, fixed it then rerooted it. Now on the 4G LTE got it rooted with custom rom. Love learning new things plus some of the good things that come with rooting and custom roms are worth it for me.
i need an easier way to do this. please give me instructions on what to do first....back up? how do i back up? unlock? down load regadmod? i feel like there are alot of good videos but they are not in order. regardless...ive watched a crap load and im really frustrated. still my phone works fine. its the same way it came out the box... i updated to the 1.22.651.3 710RD. i want the hot spot man....:silly:
You deserve to be flamed for not reading the forums. Everything is explained in there (admittedly, sometimes it's hard to find).
Regardless, some quick answers for you:
1) You can still root your phone with the OTA update, but only through HTCdev. Unfortunately, that means having to do a full wipe before you can root, which means you can't back up. If you want to root, you'll lose everything.
2) You can tether without rooting using FoxFi. The app itself was removed from the play store, but the "add-on" remains. Look in the add-on's description for a link to the full FoxFi .apk file.
muffinhunter said:
You deserve to be flamed for not reading the forums. Everything is explained in there (admittedly, sometimes it's hard to find).
Regardless, some quick answers for you:
1) You can still root your phone with the OTA update, but only through HTCdev. Unfortunately, that means having to do a full wipe before you can root, which means you can't back up. If you want to root, you'll lose everything.
2) You can tether without rooting using FoxFi. The app itself was removed from the play store, but the "add-on" remains. Look in the add-on's description for a link to the full FoxFi .apk file.
Click to expand...
Click to collapse
What's the cons of Htcdev?
Sent from my EVO using xda app-developers app
I'll quote myself from the Q&A because I think this is the best I've ever explained the difference :
Racer Of All said:
Q: What is the difference between root, S-OFF and an unlocked bootloader?
A: regaw_leinad made an awesome post here that is a billion times better than my explanation. If you have time, read it -- you will learn a lot. Otherwise here's the summed up version:
S-OFF allows complete control over your device, it will grant you access to all NAND protected partitions on your device.
Unlocked Bootloader (through the HTCDev unlock) is a "lite" version of S-OFF, it will allow you to flash a recovery and through it, a custom ROM. Zips that are attempted to be flashed through the bootloader will still need to come from HTC.
Root is not related to the NAND partitions at all, instead it grants you complete control over the OS (Android) itself. It will let you write and edit any file you wish. This lets you run apps like Titanium Backup and Adblock that need to either access or edit system files.
Click to expand...
Click to collapse
If you want to know more check out the link up in the quote, he really goes into detail. Although it's important to note that with the new hboot, it limits what you can flash (for example you can't flash individual radio updates through bootloader anymore). Basically as long as you stay with the htboot your phone came with, there's not much difference. However if someone ever updates your phone on accident and you're S-ON, you're SOL, if you're S-Off you can always go back.
Also, OP it depends what you want to do, if you just want to root then just follow a root guide. If you want to root and S-Off do lazypanda s-off and then root. Backing up (using a nandroid backup) requires a custom recovery which requires either s-off or htcdev unlock. There's a nice compilation of these guides on djR3Z's thread here. Although if you're asking for help on this I recommend you only root the phone (if even that) until you become more knowledgeable about Android and the rooting or bootloader unlocking process. Also, take a peek at the Q&A thread that I put together if you get a chance it should answer quite a few questions.
muffinhunter said:
You deserve to be flamed for not reading the forums. Everything is explained in there (admittedly, sometimes it's hard to find).
Regardless, some quick answers for you:
1) You can still root your phone with the OTA update, but only through HTCdev. Unfortunately, that means having to do a full wipe before you can root, which means you can't back up. If you want to root, you'll lose everything.
2) You can tether without rooting using FoxFi. The app itself was removed from the play store, but the "add-on" remains. Look in the add-on's description for a link to the full FoxFi .apk file.
Click to expand...
Click to collapse
No one deserves to be flamed. I dont blame a single person that posts repeated questions as I try and do search and get conflicting info, confusing info and so many root methods its hard to choose. They don't wanna wreck their phone or waste an hour trying a method that doesn't work.
I am glad to see you helped instead of stopping at the deserve to be flamed. FWIW.
This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
So I rooted my EVO 4G LTE, hurray! I have a number of questions and after some tedious searching I could not find any clear and consise answers. There is just too much info out there, even the rooting was not so easy!
So I have three main issues; 1) Bloatware 2) A stuck OTA update 3) System error messages after each reboot.
Bloatware
Using ESFileExplorer and even TitaniumBackup(free) I attempted to uninstall a number of the apps that came pre-installed and that hog RAM. Each time I reboot they come back, some attempts to uninstall apps have sent the phone straight into reboot and all the apps came right back.
I am not looking to get rid of sense, this phone is a lifeline to my livelihood and its dependability is paramount, so I would like to remain as stock as possible. I just want to free it up so that it runs a bit better and less laggy.
My task manager app shows that 0.89/1.0GB is is use and that is ridicules!
OTA Update
Sometime after rooting (this was a brand new replacement device when I started) the 3.17.651.5 update got downloaded and is now showing up all the time asking to do the actual installation. Is there any way to delete the update files and prevent the message from popping up all the time?
Reboot Error
This is just really a minor nuisance, but while we are at it I figure why not ask. After each reboot since rooting I get a System Error Message saying something like 'the phone experienced an abnormal reboot'. Any way to prevent it from doing that?
Misc
Also, I cannot seem to find any instructions (that are relevant to today, all are from 2012 and early 2013) for allowing the EVO to act as a WiFi hotspot. Any tips?
Thank you all for this great resource and in advance for all your help!
You need to S-OFF. Your system is write protected, which is why when you reboot, the apps return. I'd honestly also recommend updating to the data/media partition layout and then achieving S-OFF with Rumrunner. Once you're S-OFF, everything will work fine, and as a bonus you'll have Sense 5 .
Captain_Throwback said:
You need to S-OFF. Your system is write protected, which is why when you reboot, the apps return. I'd honestly also recommend updating to the data/media partition layout and then achieving S-OFF with Rumrunner. Once you're S-OFF, everything will work fine, and as a bonus you'll have Sense 5 .
Click to expand...
Click to collapse
I just figured the S-OFF out thanks to exhaustive Google searches, now I am seeing your post about partitions and I am not sure what you are talking about.
How do I update partitions? Do I have to do that before I use the rumrunner exploit to gain S-OFF?
webby88 said:
I just figured the S-OFF out thanks to exhaustive Google searches, now I am seeing your post about partitions and I am not sure what you are talking about.
How do I update partitions? Do I have to do that before I use the rumrunner exploit to gain S-OFF?
Click to expand...
Click to collapse
All you have to do is run the 4.13.651.4 RUU. @Magnum_Enforcer has a guide that I believe will assist you.
Captain_Throwback said:
All you have to do is run the 4.13.651.4 RUU. @Magnum_Enforcer has a guide that I believe will assist you.
Click to expand...
Click to collapse
This Post?
This will simply give me JellyBean and Sense 5? Also, will I loose root? Weren't there major problems with this update?
That's the guide he's referring to, yes. Just scroll down to the section on RUU's for more info. Link to the aforementioned RUU is at the bottom of the first post. You will lose root but you can use HTC Dev to unlock and root again, and no, there were not major problems with this update.
Magnum_Enforcer said:
That's the guide he's referring to, yes. Just scroll down to the section on RUU's for more info. Link to the aforementioned RUU is at the bottom of the first post. You will lose root but you can use HTC Dev to unlock and root again, and no, there were not major problems with this update.
Click to expand...
Click to collapse
Aha, but why did HTC pull it then?
Also, will this resolve my stuck 'update pending' issue? And will I loose data? Will my installed TWRP recovery be an issue?
webby88 said:
Aha, but why did HTC pull it then?
Also, will this resolve my stuck 'update pending' issue? And will I loose data? Will my installed TWRP recovery be an issue?
Click to expand...
Click to collapse
It was never pulled, per se, but it was never released to the masses, either. The issue was how Android 4.3 was implemented on this device-that it required a RUU instead of a traditional OTA update, which is somewhat unusual but that's how the update had to be handled due to the internal storage getting re-partitioned. Anything you have on your internal storage you'll need to back up to your computer because it will be lost when the RUU runs. Also, TWRP won't be an issue. Just reinstall the modified version from @Captain_Throwback once you've updated with the RUU (you can click on the TWRP version number in his sig & it will take you to the appropriate link).
Note that there were issues with the initial Android 4.3 updates but they were resolved with the .4 RUU, which is why I don't have links to any of the previous RUU's. The issue was with the roaming option, mostly.
Magnum_Enforcer said:
It was never pulled, per se, but it was never released to the masses, either. The issue was how Android 4.3 was implemented on this device-that it required a RUU instead of a traditional OTA update, which is somewhat unusual but that's how the update had to be handled due to the internal storage getting re-partitioned. Anything you have on your internal storage you'll need to back up to your computer because it will be lost when the RUU runs. Also, TWRP won't be an issue. Just reinstall the modified version from @Captain_Throwback once you've updated with the RUU (you can click on the TWRP version number in his sig & it will take you to the appropriate link).
Note that there were issues with the initial Android 4.3 updates but they were resolved with the .4 RUU, which is why I don't have links to any of the previous RUU's. The issue was with the roaming option, mostly.
Click to expand...
Click to collapse
Ok, I get it. Thanks for taking the time to explain this!
One more question though, I see in your post a link to 4.13.651.4, but I see another thread from @Captain_Throwback here which mentions a Odex or Deodex - what is that? And all those useful mods (battery percentage, camera shutter sound, power menu, 30 step volume etc etc), which should I use?
webby88 said:
Ok, I get it. Thanks for taking the time to explain this!
One more question though, I see in your post a link to 4.13.651.4, but I see another thread from @Captain_Throwback here which mentions a Odex or Deodex - what is that? And all those useful mods (battery percentage, camera shutter sound, power menu, 30 step volume etc etc), which should I use?
Click to expand...
Click to collapse
He has rooted odex & deodexed ROM's based off the RUU. If you want to install any mods you'll need to run the deodexed version.
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
ibma said:
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
They pulled the AT&T update. Soooo....just gotta wait.....
ibma said:
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
I'm just guessing this is a case of autocorrect, and you mean "custom ROM" and not "art room"?
How did the custom ROM get on your phone, did you buy it that way or did someone do it for you?
The update won't install with a custom ROM, its true (at least if any system files have been altered, which is usually the case). Also, it won't install with a custom recovery. Might even send you into a bootloop and render the phone unusable.
If you want to return to a stock condition and get the update, you can either read up and learn, or run the RUU to return to stock (bootloader must be locked or you need S-off). In either case, we can help you, but need specifics on how you want to approach it.
redpoint73 said:
I'm just guessing this is a case of autocorrect, and you mean "custom ROM" and not "art room"?
How did the custom ROM get on your phone, did you buy it that way or did someone do it for you?
The update won't install with a custom ROM, its true (at least if any system files have been altered, which is usually the case). Also, it won't install with a custom recovery. Might even send you into a bootloop and render the phone unusable.
If you want to return to a stock condition and get the update, you can either read up and learn, or run the RUU to return to stock (bootloader must be locked or you need S-off). In either case, we can help you, but need specifics on how you want to approach it.
Click to expand...
Click to collapse
oh the lousy autocorrect got me.
I have no idea what im doing lol, im following a tut to install revolution hd rom and so far everything is working perfect lets see what happens after system reboot.
Can I unroot and relock bootloader after custom rom install done ?
Update: restoring old content phone seems faster with better signal, but before custom rom it had 4g signal now seems only 3g
Now that sucks boomsound enable/disbale in settings is gone!
So is extreme power saving gone from status bar
also 4g signal
Signal will not show 4g or 4glte like AT&T [email protected] [email protected]
You could relock and unroot,but then no reason to flash a custom rom.
Those two settings are in settings. And on the m8 443 euro builds some are reporting lesser [email protected]
There are AT&T ROM's available that are tailored to us AT&T/GSM networks
ibma said:
oh the lousy autocorrect got me.
I have no idea what im doing lol, im following a tut to install revolution hd rom and so far everything is working perfect lets see what happens after system reboot.
Can I unroot and relock bootloader after custom rom install done ?
Update: restoring old content phone seems faster with better signal, but before custom rom it had 4g signal now seems only 3g
Click to expand...
Click to collapse
ibma said:
Now that sucks boomsound enable/disbale in settings is gone!
So is extreme power saving gone from status bar
also 4g signal
Click to expand...
Click to collapse
ibma said:
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
Just use this guide to flash the ruu for 4.4.3. It only works on att m8. MAKE SURE YOU READ THE DIRECTIONS! You just need to relock your boot loader if you are not s-off
http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
ibma said:
I have no idea what im doing lol, im following a tut to install revolution hd rom
Click to expand...
Click to collapse
This is the exact reason I highly discourage following step-by-step tutorials; and/or using toolkits. You are modding the phone with apparently very little understanding of what you are actually doing. Not only is this very risky, as it might result in damage to you phone. But it also leaves you completely unequipped to handle any problems.
My suggestion is to spend a few hours reading the basic information that the folks here have taken the time to compile. This isn't "techie" stuff, this is the basic information and concepts that should be understood before doing any modding of the phone. Quite simply IMO if you don't understand the basics, you have no business rooting/modding the phone.
exad's excellent guide: http://forum.xda-developers.com/showthread.php?p=52484527
FAQs: http://forum.xda-developers.com/showthread.php?t=2711073
Index of AT&T M8 resources: http://forum.xda-developers.com/showthread.php?t=2751432
Index of "international" M8 resources (most apply to AT&T version): http://forum.xda-developers.com/showthread.php?t=2694600
redpoint73 said:
This is the exact reason I highly discourage following step-by-step tutorials; and/or using toolkits. You are modding the phone with apparently very little understanding of what you are actually doing. Not only is this very risky, as it might result in damage to you phone. But it also leaves you completely unequipped to handle any problems.
My suggestion is to spend a few hours reading the basic information that the folks here have taken the time to compile. This isn't "techie" stuff, this is the basic information and concepts that should be understood before doing any modding of the phone. Quite simply IMO if you don't understand the basics, you have no business rooting/modding the phone.
exad's excellent guide: http://forum.xda-developers.com/showthread.php?p=52484527
FAQs: http://forum.xda-developers.com/showthread.php?t=2711073
Index of AT&T M8 resources: http://forum.xda-developers.com/showthread.php?t=2751432
Index of "international" M8 resources (most apply to AT&T version): http://forum.xda-developers.com/showthread.php?t=2694600
Click to expand...
Click to collapse
What i did is i unocked, rooted, then installed twrp, took nanodroid backup and installed custom rom, would it cause any issues if i factory reset the phone ?(will it reset to at&t room that came with the device)
ibma said:
What i did is i unocked, rooted, then installed twrp, took nanodroid backup and installed custom rom, would it cause any issues if i factory reset the phone ?(will it reset to at&t room that came with the device)
Click to expand...
Click to collapse
Again, you need to learn and research more before doing anything. This is another perfect example. Factory reset doesn't do anything to the ROM. All it does is wipe the user data partition, and isn't going to help your case in any way. And trying to make up your own solutions is not a good idea (but at least you thought to ask before trying it).
If the intent is to simply be on the latest 2.23 stock software, just run the RUU. You will need to relock the bootloader before RUU if you are s-on. Also, back up any personal data, as user data will be wiped by RUU.
redpoint73 said:
Again, you need to learn and research more before doing anything. This is another perfect example. Factory reset doesn't do anything to the ROM. All it does is wipe the user data partition, and isn't going to help your case in any way. And trying to make up your own solutions is not a good idea (but at least you thought to ask before trying it).
If the intent is to simply be on the latest 2.23 stock software, just run the RUU. You will need to relock the bootloader before RUU if you are s-on. Also, back up any personal data, as user data will be wiped by RUU.
Click to expand...
Click to collapse
I restored stock recovery and got bavk to att rom RUU is giving me usb error dunno why.
ibma said:
I restored stock recovery and got bavk to att rom RUU is giving me usb error dunno why.
Click to expand...
Click to collapse
Not enough info. What exactly does the error say?
S-on or S-off. Did you relock the bootloader?
Any response if you type (using adb):
adb devices
Improper HTC/ADB drivers or using Microsoft USB 3.0 drivers on USB 3 port on Windows 8.x instead of Intel USB drivers would be my first two guess. The ladder of the two issues would be most likely scenario if RUU communicates with device while booted into Android OS but fails to connect when the device is in fastboot/boot loader mode.
-Sent from a payphone...