Related
You can unlock your htc legend at HTC DEV.
Once the new file is installed and the phone is s-off, how do I re-root the phone?
Exactly! Also my question! They want you to upgrade your Bootloader which will disable you from rooting (all methods I've heard of require old versions Bootloader).
Any solution before we dive into this WONDERFUL UNLOCKED REALM?
Hi, just signed up to HTC dev to see what's going on with bootloader unlock, I started the procedure but told me it wants to delete everything on my phone, bugger that.
This is HTC official root method, it says you can load custom rom's and change the recovery but it is still s-on to protect the radio and sim lock (network).
Now if u are not already rooted then its gonna make it hard, esspecialy to backup, however we still have revolutionary temp root to backup with titanium.
For those already rooted, I'm not sure if there is any advantage, except you can flash custom recovery, we have fakeflash so not much point IMO.
Oh, just realised it gives unrestricted access to /system folder so that might make it worth while after all..
Sent from my HTC Legend using XDA App
Deleted, no longer relevent
Do we have to go back to stock before running this or can it be run with a custom ROM installed?
smilingguy07 said:
Do we have to go back to stock before running this or can it be run with a custom ROM installed?
Click to expand...
Click to collapse
Good question. I suspect it might only work with unrooted legends.
If that is the case its gonna be a big hassle, but not impossible.
Sent from my HTC Legend using XDA App
wow wow wow WOOOW!!! I didn't expected this!!!!! I will unlock my bootloader and install the clockwork recovery ASAP!
For rooted legend you can make a nandroid, install the RUU, install a recovery (the .img recovery from the rom manager site) and restore the nandroid
Do you plan on doing it on yours?
I noticed that there is also a wifi security update out for the legend too,
The bootloader unlock is 3.15.405.5, and the wifi fix is 3.15.405.6, so I guess it has to be in that order or the bootloader unlock wont run.
Good,Now my phone has hboot unlocked, but is there a way to disable the security flag and finally get SOFF now ?
Stevenstrike,
Did you install that update on top of your cm custom rom?
Any problems at all?
No
Just find a HTC stock rom for your legend, then update the rom via OTA if needed, then try to apply the hboot update, after that use the htcsupertoolv3 to gain perm root, and if you want, flash cwm fastboot to access cwm as recovery.
Thanks,
Are you applying their Wifi security fix as well?
http://forum.xda-developers.com/showthread.php?t=1497357
smilingguy07 said:
Thanks,
Are you applying their Wifi security fix as well?
http://forum.xda-developers.com/showthread.php?t=1497357
Click to expand...
Click to collapse
Never heard of that, besides my radio is already 7.13.35.05, so i think i dont have to apply this.
Edit : Link to gain Perm Root http://forum.xda-developers.com/showthread.php?t=1432074 (link is for wildfire S but also work for Legend)
and link to flash CWM : http://forum.xda-developers.com/showthread.php?t=1244371&highlight=cwm ( then do a fastboot flash recovery <recoveryFile>.img )
Ah ok, I see that the Bootloader unlock is software version 3.15.405.5, security update is 3.15.405.6, does that make a difference or is it purely the radio that matters?
smilingguy07 said:
Do you plan on doing it on yours?
I noticed that there is also a wifi security update out for the legend too,
The bootloader unlock is 3.15.405.5, and the wifi fix is 3.15.405.6, so I guess it has to be in that order or the bootloader unlock wont run.
Click to expand...
Click to collapse
Edit:- Now Hboot 1.02
Not at the moment, I am already rooted & happy with what I have ATM. I can do everything I need via recovery and android commander. Might give it a go at a later date.
Sent from my HTC Legend using XDA App
I still says S-ON but you can do anything that requires r/w permission on /system.
Tested with SU update, BusyBox installation, host write with AdAway.
Gees this is complicated, almost as hard and confusing as rooting hboot 1.01 in the first place.
I have downloaded the hboot 1.02 update, I'm wondering if you can just do that on its own on a rooted phone?
I just worry that it might do some real damage if you do, cause I don't think we can go back to 1.01 or other hboot later.
Sent from my HTC Legend using XDA App
Sorry your screen shot is too small to see.
cyRq said:
I still says S-ON but you can do anything that requires r/w permission on /system.
Tested with SU update, BusyBox installation, host write with AdAway.
Click to expand...
Click to collapse
Sent from my HTC Legend using XDA App
Yhm...
You've got to click on it and...baaaam! It gets bigger
Hello all, I tried searching but if I missed the thread please point me to it. I was able to unlock the bootloader using HTC Dev but I cant seem to install TWRP. Am I missing a step or something? I am running an HTC Evo 4G LTE on 3.17. I tried putting the PJ75IMG.zip in the root of the sd card but when restarted in the bootloader it read it and said main version is older. I tried using goomanager to download and install but that didnt work either. Am i doing something wrong here? Thanks in advance guys (and girls)!
fastboot flash it PJ75IMG.zip will only work if you are S-OFF
Put the .img file in the folder you are using to run the commands from.
fastboot flash recovery nameofrecovery.img
OK. So fastboot is the best method. Then I can install super user correct? I dont HAVE to install a ROM if i dont want to correct? I can just run stock root? If I wanted to install a ROM would I need to be S-OFF? or could I install one while still being S-ON? It has been quite some time since I rooted a phone. Last phone was the Samsung Epic 4G. What a terrible phone. Thanks and sorry for so many questions.
quattroa430 said:
OK. So fastboot is the best method. Then I can install super user correct? I dont HAVE to install a ROM if i dont want to correct? I can just run stock root? If I wanted to install a ROM would I need to be S-OFF? or could I install one while still being S-ON? It has been quite some time since I rooted a phone. Last phone was the Samsung Epic 4G. What a terrible phone. Thanks and sorry for so many questions.
Click to expand...
Click to collapse
I personally use fastboot to install twrp then when you want/need to update twrp you can fastboot flash again or use goomanager from the playstore.
You can install SuperSU and run stock rooted or flash a custom rom which has superuser added
As for flashing roms you can flash them while s-on it's just more work because you have to fastboot flash the kernel/boot.img then flash the rom.
I always recommend S-OFF as it will save you the extra steps in flahing roms and also if you mess something up you can flash an older RUU if the most current RUU is not available.
@FinZ28 has a great guide explaining how to flash the kernel/boot.img
OK, so now the question becomes what method for S-OFF should I use? I would like to be able to make it look like I never rooted the phone if need be if at all possible. I heard good things about rumrunner for 3.17. am i correct that this would be the best method or is there a better one? again sorry its been too long and this is my first HTC root.
quattroa430 said:
OK, so now the question becomes what method for S-OFF should I use? I would like to be able to make it look like I never rooted the phone if need be if at all possible. I heard good things about rumrunner for 3.17. am i correct that this would be the best method or is there a better one? again sorry its been too long and this is my first HTC root.
Click to expand...
Click to collapse
Since you are on 3.17 rumrunner is the only method you can use
OK so first install TWRP then SU then S-OFF? also i factory reset my phone the other day and now on some apps I have this weird menu bar at the bottom. it happens on my facebook app and bank app. it doesnt show up in Kik or play or sms apps. any ideas? i would like to remove that
quattroa430 said:
OK so first install TWRP then SU then S-OFF? also i factory reset my phone the other day and now on some apps I have this weird menu bar at the bottom. it happens on my facebook app and bank app. it doesnt show up in Kik or play or sms apps. any ideas? i would like to remove that
Click to expand...
Click to collapse
Yes unlock your bootloader if you have not already
Install twrp
Flash SU
Then S-OFF(make sure you read all the pre-requisetes before starting rumrunner
As fo the weird menu it may disappear if you flash a custom rom
Ok so I came across another issue. I cant seem to get busybox to install. I would like to install cyanogenmod 10 and qbking mentions needing s-off to do so. Is that correct? It is a bit of a pain being on 3.17 but I guess there isnt much I can do. Any advice for installing busybox? Thanks again
I successfully installed Busybox on 3.17 last night. As far as having to be S-off to flash CM, no, you don't have to be, but it makes life easier. Hit the top link in my sig and read my Hboot guide if you haven't already done so.
Sent from my HTC EVO 4G LTE
I read your hboot guide. Very informative. Rumrunner requires busybox and for whatever reason I cannot install busybox. Could you possibly eexplain what choices you made that worked? I tried installing to bin and xbin. Should I install to a custom location instead? If so where should I? I would like to be s-off and have cyanogen lol. Thanks again guys!
quattroa430 said:
I read your hboot guide. Very informative. Rumrunner requires busybox and for whatever reason I cannot install busybox. Could you possibly eexplain what choices you made that worked? I tried installing to bin and xbin. Should I install to a custom location instead? If so where should I? I would like to be s-off and have cyanogen lol. Thanks again guys!
Click to expand...
Click to collapse
I'm not really sure what to tell you since I was already S-off when I installed it. Where did you read that it was required prior to running Rumrunner?
Sent from my HTC EVO 4G LTE
It was on the pocketables website. search "rumrunner HTC EVO 4g LTE" everytime I seem to try to install busybox my phone crashes.
Are you running just the stock rooted factory rom?
You could try Captain_Throwbacks 3.17 rooted rom or SharkieRom 3.17
Try this. Its a TWRP flashable zip of the latest Busybox (v1.20.2). See if that straightens things out with your issue. Make sure you have a backup handy just in case.
https://www.dropbox.com/s/g16xuqbzbmzz8yz/busybox-signed.zip
You can use a file manager like Root Explorer and go to /system/xbin/ and look to make sure you see the Busybox file. If it's there you're good to go:thumbup: (I did not develop the Busybox file-I simply took the file and make it into a flashable zip. Big thanks to Rootlinux for showing me how it's done).
Sent from my HTC EVO 4G LTE
FinZ28 said:
Try this. Its a TWRP flashable zip of the latest Busybox (v1.20.2). See if that straightens things out with your issue. Make sure you have a backup handy just in case.
https://www.dropbox.com/s/g16xuqbzbmzz8yz/busybox-signed.zip
You can use a file manager like Root Explorer and go to /system/xbin/ and look to make sure you see the Busybox file. If it's there you're good to go:thumbup:
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Worked like a charm. Busybox is installed right where you said it should be. Now to run rumrunner and gain s-off. Thank you guys for all the help and support thus far!
quattroa430 said:
Worked like a charm. Busybox is installed right where you said it should be. Now to run rumrunner and gain s-off. Thank you guys for all the help and support thus far!
Click to expand...
Click to collapse
Glad it worked for you:thumbup:
Sent from my HTC EVO 4G LTE
S-OFF Issue
Ok now I can't seem to gain S-OFF using rumrunner. I downloaded the correct version for the EVO 4G LTE and I am running native Ubuntu 13.10 32bit. It works for a while until it gets to the pouring stages
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
YesDo you understand the implications of this warning?
(Yes/No)
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
yes
Type 'Yes' or 'No'
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (21/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (21/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
pouring (1)...
WTF: What are you doing?
Idk what I am doing wrong here. I couldnt even get it to work right using windows so I had to break out the laptop.
It gets to that point every time then fails and reboots the phone.
Software version: 3.17.651.4
Android Version: 4.1.1
Kernal Version: 3.4.10-gf5d846c
Is there anything else needed to help figure this out? Tis getting a wee bit frustrating. Can I S-OFF off if i flash cyanogen or any other rom?
Tried running Captain_Throwbacks stock rooted 3.17 and got the same result at the same exact point while running rumrunner. Going to try Sharkie next. Any tips are greatly welcomed!
Don't have much to offer since I haven't used Rumrunner. Having said that, make sure you're using a USB 2.0 port and not 3.0, and that you're using a fairly stock Sense ROM. Also make sure that you're phone is recognized with both ADB & Fastboot. Seems most of the issues I've seen have to do with the connection. If it fails, try try again. You also might want to check out the Rumrunner thread in original development.
Just a thought, but have you looked at your bootloader and made sure that you're still S-on? Reason I ask is because on Moonshine the "WTF: What are you doing?" message actually meant that the process was successful. Not sure if Rumrunner is the same.
Sent from my HTC EVO 4G LTE
So while in process of s-off once I got to the part when you "fastboot oem rebootRUU" that went through. But right after trying to flash a zip im stuck looking at the blk HTC screen. I was given a "<Failed <remote: 99 unknown fail>". Now its just stuck.
I've been trying to figure out what happened but just have no where else to turn. Please lend a hand.
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
aarsyl said:
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
Click to expand...
Click to collapse
It's not a full RUU in the normal sense. It's the one for Facepalm.
To the OP, did you gain SuperCID prior to running those commands? If not, then the process will fail. You should simply be able to hold the power button down & reboot your phone. Also, as stated above, list your device info so we can make sure you're using the right S-off exploit.
Sent from my HTC EVO 4G LTE
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
z3r0t0l0rEnCe said:
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
Click to expand...
Click to collapse
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
aarsyl said:
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
Click to expand...
Click to collapse
This is odd to me, because I ran rumrunner at least 3 times using just my stock ROM (no custom kernel or anything), and it worked fine every time. I guess the new version of rumrunner added some limitations to make it more generic.
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
z3r0t0l0rEnCe said:
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
Click to expand...
Click to collapse
No, don't. If it fails, don't force it. Reflash TWRP 2.6.3 (not the kit kat version), and try to flash again.
@Captain_Throwback: Yes, I didn't remember needing a custom kernel when I used Dirty Racun, but rumrunner needs it now. Keep in mind that rumrunner isn't for this device exclusively. Maybe that's the purpose of the custom kernel.
i'd wager you're trying to flash files that aren't recovery flashable, then lying to the people who are trying to help you.
i got it running again using capt stock rooted rom. attempting rumrunners s-off again now that i got this part working.
Are you using a custom kernel?
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
now s-off and updated rumrunners hboot. now onto flashing roms finally.
Thank you all that helped me with my stupidness and not reading directions.
Last post. I can't say it enough that you must read read read when it comes to directions. If I would of followed directions as directed I would of never ran into the issues I did. It was a learning experience.
One thing for sure that I took from this experience is adb and directions. I've learned a lot in the last 24hrs alone.
I'd like to thank Capain_throwback and everyone in the irc for the help and you all here that assisted me.
Sent from my EVO using XDA Premium 4 mobile app
Hi,
Can someone help me please. I am looking for a rom for my AT&T US, HTC One M8. I'm running 4.4.2, Hboot 3.16, Radio 1.16..., and 1.58.502.1 firmware.I have the 3.4 kernel. I am unlocked, TWRP latest custom recovery, and rooted with SuperSU. I am S-On. I can't S-Off and can't update my Firmware. I need it to work in the US, so what rom can I flash that will work. When I go to Dev sites every rom I see only has the 4.4.3/4.4.4 versions with the new Firmware, for my device. When I try to flash .zip's through TWRP, Aroma gives me a success, but it auto reboots and I get stuck in boot loop... I am able to recover the stock image, but can't get a custom rom to stick. I have watched hours of videos and read hundreds of pages of threads. HELP
Thank You,
-Shane
HitShane said:
Hi,
Can someone help me please. I am looking for a rom for my AT&T US, HTC One M8. I'm running 4.4.2, Hboot 3.16, Radio 1.16..., and 1.58.502.1 firmware.I have the 3.4 kernel. I am unlocked, TWRP latest custom recovery, and rooted with SuperSU. I am S-On. I can't S-Off and can't update my Firmware. I need it to work in the US, so what rom can I flash that will work. When I go to Dev sites every rom I see only has the 4.4.3/4.4.4 versions with the new Firmware, for my device. When I try to flash .zip's through TWRP, Aroma gives me a success, but it auto reboots and I get stuck in boot loop... I am able to recover the stock image, but can't get a custom rom to stick. I have watched hours of videos and read hundreds of pages of threads. HELP
Thank You,
-Shane
Click to expand...
Click to collapse
There are 4.4.2 roms still available but your best bet is pay the $25 for sunshine s-off utility that way you can update your firmware and run whatever rom/kernel you want.
If you've tried the flash various ROMs, and they all won't boot, then the problem is not what ROM, but something else.
adb erase cache
Then, flash recovery again. Possibly re-download recovery, to make sure the file is not corrupt.
redpoint73 said:
If you've tried the flash various ROMs, and they all won't boot, then the problem is not what ROM, but something else.
adb erase cache
Then, flash recovery again. Possibly re-download recovery, to make sure the file is not corrupt.
Click to expand...
Click to collapse
^^ I did that when I rooted the phone. I used the HTCDev to unlock it. I used Fastboot and adb in cmd from my PC to install TWRP and the Recovery file and clear the cache. Should I reflash recovery again???
I have wiped and tried factory resets before installing a rom. The problem is that I can't find the download link for an old rom for my specific phone. I need the 1.58.502.1 version (Don't I ?), so that I don't have to change my Firmware through S-OFF... When I find a rom that did make one that would work on my device, they have already updated the OP download link with their latest version to run with the updated AT&T 4.4.3/4.4.4 and 2.22.1540.3.
* I have the newest TWRP installed with the 24MB Recovery.img. I have SU installed with privileges. The phone passes rooted tests. Phone is S-ON... *
iRunLinux said:
There are 4.4.2 roms still available but your best bet is pay the $25 for sunshine s-off utility that way you can update your firmware and run whatever rom/kernel you want.
Click to expand...
Click to collapse
^^I have seen even sunshine fail with the latest devices from AT&T.
?----->Does anyone have a good link to a rom that will run on my; AT&T HTC One M8 running 4.4.2 & 1.58.502.1, (1.16.21331931.LA11G)? It was bought a month ago from an AT&T store...
Thank You,
-Shane
HitShane said:
Should I reflash recovery again???
Click to expand...
Click to collapse
I just told you to adb wipe cache and flash recovery again. Why are you asking me this? A lot of issues with TWRP not flashing ROMs can be solved by wiping cache and flashing again (probably just a bad initial install).
HitShane said:
I need the 1.58.502.1 version (Don't I ?), so that I don't have to change my Firmware through S-OFF...
Click to expand...
Click to collapse
Any ROM that is not 2.xx Sense based.
I haven't checked every single thread/link, but most (if not all) 1.54 and 1.58 based Sense ROMs on my Index thread seem to be working:
http://forum.xda-developers.com/showthread.php?t=2751432
This also includes the stock rooted 1.58 ROM, if you wish to go that route.
HitShane said:
^^I have seen even sunshine fail with the latest devices from AT&T.
Click to expand...
Click to collapse
You sure? I haven't seen sunshine fail for anybody, much less AT&T, which hasn't had their software updated for sometime now. Regardless of how new the device is, its still the same 1.58 software, which is 3 months old at this point.
firewater, on the other hand is known to fail for more recent AT&T versions.
918
redpoint73 said:
I just told you to adb wipe cache and flash recovery again. Why are you asking me this? A lot of issues with TWRP not flashing ROMs can be solved by wiping cache and flashing again (probably just a bad initial install).
Any ROM that is not 2.xx Sense based.
I haven't checked every single thread/link, but most (if not all) 1.54 and 1.58 based Sense ROMs on my Index thread seem to be working:
http://forum.xda-developers.com/showthread.php?t=2751432
This also includes the stock rooted 1.58 ROM, if you wish to go that route.
You sure? I haven't seen sunshine fail for anybody, much less AT&T, which hasn't had their software updated for sometime now. Regardless of how new the device is, its still the same 1.58 software, which is 3 months old at this point.
firewater, on the other hand is known to fail for more recent AT&T versions.
Click to expand...
Click to collapse
So for instance on your Index, I followed the link to ViperOneM8 1.6.0. This takes you to the Dev page for that rom. I follow the page to downloads that directs me another page. Along the way I find out that it looks like ViperOneM8 1.8 is the last update before 2.xx. The download page only has the most recent ViperOneM8_2.2.0.zip, or they offer the OTA increments of each previous version. Those aren't large enough to be the whole rom. How do I find the legacy full roms?
-Shane
HitShane said:
So for instance on your Index, I followed the link to ViperOneM8 1.6.0. This takes you to the Dev page for that rom. I follow the page to downloads that directs me another page. Along the way I find out that it looks like ViperOneM8 1.8 is the last update before 2.xx. The download page only has the most recent ViperOneM8_2.2.0.zip, or they offer the OTA increments of each previous version. Those aren't large enough to be the whole rom. How do I find the legacy full roms?
Click to expand...
Click to collapse
I think you picked one of the few (maybe the only one) that doesn't link to an actual 1.xx ROM. Just pick any other one.
EDIT: Oh, wait InsertCoin also. Will update the Index to show those as 2.22 ROMs.
Devs usually don't keep their legacy versions posted. Most you can do is ask if another member has the zip.
redpoint73 said:
I think you picked one of the few (maybe the only one) that doesn't link to an actual 1.xx ROM. Just pick any other one.
EDIT: Oh, wait InsertCoin also. Will update the Index to show those as 2.22 ROMs.
Devs usually don't keep their legacy versions posted. Most you can do is ask if another member has the zip.
Click to expand...
Click to collapse
Thank you for all of the information. I guess the roms develop faster than I can get a phone for them It baffles me that a version for each baseline of a current device isn't listed. I guess I should flash back to the most current stock rom and wait for the OTA from AT&T. I might try the S-Off for $25, but I have seen a lot of chatter about newly bought M8 ATT devices not working. Something about them having a patch from HTC...
-Shane
Hi all,
I want to apologize now if this is in the wrong section, I am very new to this forum. I recently want to install Cyanogenmod onto my HTC One M8, I got that to work. I created a backup on TWRP before installing cyanogen and I ended up not enjoying cyanogenmod. I restored my backup and I still have Superuser installed. I don't think it installed correctly to begin with because I get the error "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" I tried to uninstall the app by going into to root explorer and deleting it from there. Once I do that, I get the error "Superuser.apk cannot be deleted because the file system is read-only." I also went on root checker, and confirmed my phone isn't rooted. This is the toolkit I used to "root":
http://forum.xda-developers.com/showthread.php?t=2699065
Now I just want to get my phone back to original stock, just like it was before I did anything. I am also clueless on what S-OFF and S-ON are.
BTW: I also could relock the bootloader with the same tool linked above, I don't know if that could help or not.
Thank you
Do you have the AT&T version of the M8?
Were you on Lollipop when you unlocked the bootloader and tried to root?
Notice the toolkit has not been updated in over a year, and you can bet there are going to be problems (especially if you were on Lollipop).
I suggest staying away from this and other toolkits. The steps are easy to perform "manually" using fastboot, etc. Plus, the toolkit being outdated is going to cause you major headaches.
Answer the questions I posed above, and we can go from there.
redpoint73 said:
Do you have the AT&T version of the M8?
Were you on Lollipop when you unlocked the bootloader and tried to root?
Notice the toolkit has not been updated in over a year, and you can bet there are going to be problems (especially if you were on Lollipop).
I suggest staying away from this and other toolkits. The steps are easy to perform "manually" using fastboot, etc. Plus, the toolkit being outdated is going to cause you major headaches.
Answer the questions I posed above, and we can go from there.
Click to expand...
Click to collapse
I do have the ATT version of the M8 and I was on lollipop (5.0) at the time. thanks for the update
xChaosLegion said:
I do have the ATT version of the M8 and I was on lollipop (5.0) at the time. thanks for the update
Click to expand...
Click to collapse
Its not completely clear what you've done to cause SuperSU to show up on the stock ROM. You've either:
1) Restored your stock Sense ROM while keeping app data (from CM12), which is not recommended, or
2) You tried to root before you made the stock Sense TWRP backup.
If #1 above, try either factory reset; or restore TWRP backup making sure to restore system, boot.img, and data (assuming all those were originally backed up).
If #2, the toolkit tried to root using a very old version of SuperSU that is known to not work on Lollipop (need around SuperSU 2.44 or newer). In which case, you were probably never actually rooted to begin with (note that root is not needed to flash custom ROMs).
If the intent is to be on the stock ROM, but have root: Make sure you have current version TWRP. Fastboot flash the latest TWRP version 2.8.7 from here: https://dl.twrp.me/m8/
Then download the current version SuperSU 2.46 from the following link. Boot into TWRP, and install the SuperSU 2.46 zip: https://download.chainfire.eu/696/SuperSU
Alternately, if you really want to return to full stock (no root, get rid of SuperSU completely), you can relock the bootloader (not required if s-off) than run the 4.28 AT&T RUU. But note, the RUU will wipe the phone (including internal storage).
redpoint73 said:
Its not completely clear what you've done to cause SuperSU to show up on the stock ROM. You've either:
1) Restored your stock Sense ROM while keeping app data (from CM12), which is not recommended, or
2) You tried to root before you made the stock Sense TWRP backup.
If #1 above, try either factory reset; or restore TWRP backup making sure to restore system, boot.img, and data (assuming all those were originally backed up).
If #2, the toolkit tried to root using a very old version of SuperSU that is known to not work on Lollipop (need around SuperSU 2.44 or newer). In which case, you were probably never actually rooted to begin with (note that root is not needed to flash custom ROMs).
If the intent is to be on the stock ROM, but have root: Make sure you have current version TWRP. Fastboot flash the latest TWRP version 2.8.7 from here:
Then download the current version SuperSU 2.46 from the following link. Boot into TWRP, and install the SuperSU 2.46 zip:
Alternately, if you really want to return to full stock (no root, get rid of SuperSU completely), you can relock the bootloader (not required if s-off) than run the 4.28 AT&T RUU. But note, the RUU will wipe the phone (including internal storage).
Click to expand...
Click to collapse
I can lock the bootloader from the same toolkit? Or is that a bad idea? If its possible then, how do I run the 4.28 ATT RUU? I don't mind it being wiped. I installed TWRP, then installed supersu, made backup, installed cyanogen, then restored using TWRP.
Sorry, I was on work travel last week and not able to visit XDA.
xChaosLegion said:
I can lock the bootloader from the same toolkit? Or is that a bad idea?
Click to expand...
Click to collapse
I would personally recommend stopping the use of the toolkit for anything. What part of my previous post is not clear?
redpoint73 said:
I suggest staying away from this and other toolkits. The steps are easy to perform "manually" using fastboot, etc. Plus, the toolkit being outdated is going to cause you major headaches.
Click to expand...
Click to collapse
Relocking the bootloader is a single fastboot command, and you don't need a toolkit for that: fastboot oem lock
If you don't know how issue fastboot commands, time to read and learn. And knowledge is a far more useful "tool" than any toolkit program you can fine.
xChaosLegion said:
If its possible then, how do I run the 4.28 ATT RUU? I don't mind it being wiped.
Click to expand...
Click to collapse
The RUU is mostly automated and self-explanatory. Just connect the phone to PC (Windows 7 or 8.1 recommended, Win8 and especially 10 are known to cause issues) and run the RUU executable (after you download it, obviously) and it will launch and guide you through the rest.
xChaosLegion said:
I installed TWRP, then installed supersu, made backup, installed cyanogen, then restored using TWRP.
Click to expand...
Click to collapse
You were never properly rooted to begin with, due to outdated version SuperSU. You can probably just flash SuperSU 2.46 to properly root. You can RUU to "full stock" if you want to be sure. But I'm pretty sure just flashing the correct version SuperSU will fix your "root" issue.
redpoint73 said:
You were never properly rooted to begin with, due to outdated version SuperSU. You can probably just flash SuperSU 2.46 to properly root. You can RUU to "full stock" if you want to be sure. But I'm pretty sure just flashing the correct version SuperSU will fix your "root" issue.
Click to expand...
Click to collapse
Do I just flash the new version of SuperSU or do I have the find a way to uninstall the previous verison and then reinstall SuperSU?
xChaosLegion said:
Do I just flash the new version of SuperSU or do I have the find a way to uninstall the previous verison and then reinstall SuperSU?
Click to expand...
Click to collapse
Just install the new SuperSU. It will overwrite the old apk app as needed.