Hi, what is about S-OFF for our device?
Anyone have S-OFF?, As he did? Thanks
For S-Off visit here:
http://forum.xda-developers.com/showthread.php?t=2847983
Sent from my HTC Desire 610 using XDA Premium 4 mobile app
That's incorrect information. There is nothing about s-off in that thread and it doesn't exist yet for our phone. That thread is about system write protection, which is something entirely different.
My bad, copied the wrong post
Sent from my HTC Desire 610 using XDA Premium 4 mobile app
I wish we had s-off, it'd make life easier.
Would have been great to s-off with sunshine but i guess our device is not supported
Someone working on s-off for our device?
Jcase and beaups are working on Sunshine S-off version 3.0, which will most likely support our device. It isn't out yet though, but should be soon. Whatever you do, DO NOT post in the sunshine thread asking anything about it.
$ 25 is a lot for a 610 Thanks for reply
Any advantages now that we can s-off with sunshine?
You can remove that ugly htc red text splash screen for starters
ClearD said:
You can remove that ugly htc red text splash screen for starters
Click to expand...
Click to collapse
Having s-off is news to me. @ClearD, did you purchase this? If so how did you implement it? I went to what I think is the thread but didn't see any notice of how to buy it...
Nevermind. Found it here. And the list confirms our phone. I don't think I'll be buying it because I'm not sure what else I can do that I'm not already doing. Good to know its there though.
http://www.androidpolice.com/2015/03/20/sunshine-3-0-released-with-ability-to-unlock-and-s-off-many-motorola-and-almost-all-htc-handsets/
ClearD said:
You can remove that ugly htc red text splash screen for starters
Click to expand...
Click to collapse
Went and removed red text and added a new splash
With it, you can also change the radio. And bootloader I think. And pretty much anything.
I assume just running the app will remove the red message, but can we just run this with our bootloaders already unlocked and rooted?
And is there anything that changes as far as how we update firmware in the future? I noticed some people were waiting for new exploits, meaning root might've been broken by updates so there must be some more info to it. It'd be great if it had a built in way to take otas even if it means automating the lock/return to stock to do this...
Thats the only thing I'm worried about, I'll s-off, do the whole recovery and mods, Lollipop drops and the only way to update is to relock and RUU. Then be stuck unrooted.
KLit75 said:
I assume just running the app will remove the red message, but can we just run this with our bootloaders already unlocked and rooted?
And is there anything that changes as far as how we update firmware in the future? I noticed some people were waiting for new exploits, meaning root might've been broken by updates so there must be some more info to it. It'd be great if it had a built in way to take otas even if it means automating the lock/return to stock to do this...
Click to expand...
Click to collapse
No, you've gotta flash a new splash screen with the command: fastboot flash splash splash.img
Yes, run it unlocked and rooted. That's optimal.
The current way to root should be fine for the life of the phone. Root tool v4 should be finer, actually. Use it instead. It's easier. No root is broken that I'm aware of.
To get an OTA, you will need to relock and ruu, plain and simple. It's always been that way. I don't know if s-off will affect that or not.
phatmanxxl said:
Thats the only thing I'm worried about, I'll s-off, do the whole recovery and mods, Lollipop drops and the only way to update is to relock and RUU. Then be stuck unrooted.
Click to expand...
Click to collapse
And then when you get the update, you unlock again and re root. Then use titanium backup to restore your apps. It's that easy.
ClearD said:
No, you've gotta flash a new splash screen with the command: fastboot flash splash splash.img
Yes, run it unlocked and rooted. That's optimal.
The current way to root should be fine for the life of the phone. Root tool v4 should be finer, actually. Use it instead. It's easier. No root is broken that I'm aware of.
To get an OTA, you will need to relock and ruu, plain and simple. It's always been that way. I don't know if s-off will affect that or not.
***I actually misspoke there...what I meant was the current version of sunshine wasn't working on the latest firmware (not our phone I don't think) and they were going to release a new version shortly.
That fastboot command you gave me...do I need to put a specific splash img in my fast boot folder or does just typing that in fast boot get it done?
Click to expand...
Click to collapse
You have to have a specific splash screen. So, someone with a stock one can pull theirs hopefully and we can reflash that.
Related
Future of this rom and me - https://plus.google.com/u/0/100983447046094793882/posts/7YtTFWWgT1C
Hope this helps people others comming sooon i have slow internet
Let's hope that nobody will be needing these with the exception of obtaining S-OFF and ROM production.
I added some tags for you too.
All ruus released enjoy
md5's for the ruu's added so enjoy but remeber you need to htc relock your boot loader before you can restore
Have you are anyone tested the relock? Frrom what I remember on previous ones I thought you could not relock like the nexus one.
But basically relock then flash these thru bootloader and you are back to the way has came out the box?
M9x3mos said:
Have you are anyone tested the relock? Frrom what I remember on previous ones I thought you could not relock like the nexus one.
But basically relock then flash these thru bootloader and you are back to the way has came out the box?
Click to expand...
Click to collapse
yep you got it and me and binary both tested the relock scripts they are good to go
xboarder56 said:
yep you got it and me and binary both tested the relock scripts they are good to go
Click to expand...
Click to collapse
I tested that script on an unbiased Windows 7 machine.
Unbiased means that it had nothing but the drivers installed. No adb or fastboot files.
I wanted to clean it up and make it look better but x was in a hurry to release it for whatever reason.
Well clean up and I will reupdate it
Sent from my HTC Amaze 4G using xda premium
xboarder56 said:
Well clean up and I will reupdate it
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
Nah. It's it's not broke, don't fix it.
Lol ok
Sent from my HTC Amaze 4G using xda premium
more various roms/ruus coming wendsday
more ruu's released
Sorry for sounding like a n00b and redundancy but just wanted to make sure I understand this right before I make any changes on device.
The relocker posted by xboarder and binary, does that completely reverse the HTC bootloader unlock done the HTC dev site?
Assuming it does, that does mean we can get the regular updates to device again?
Sorry again if is redundant but just want to make sure there is a 100% way of returning to stock software very much like my vibrant / g2 / hd2
TheArtiszan said:
Sorry for sounding like a n00b and redundancy but just wanted to make sure I understand this right before I make any changes on device.
The relocker posted by xboarder and binary, does that completely reverse the HTC bootloader unlock done the HTC dev site?
Assuming it does, that does mean we can get the regular updates to device again?
Sorry again if is redundant but just want to make sure there is a 100% way of returning to stock software very much like my vibrant / g2 / hd2
Click to expand...
Click to collapse
yes it will let you do updates again if you follow the guide
I've tried installing this via hboot both unlocked and relocked and it doesn't actually do anything. it checks the image then just goes back to hboot. Any Idea what I'm doing wrong?
I am trying to get my Telus Amaze back to stock. I have re locked the phone it says so in the hboot menu. I have downloaded the RRU for Telus and it is on the root of my SD card. When I boot into hboot I see the progress bar in blue on the right hand side, then it goes into yellow verifiying, then it just stops no option to install the update.... It just isn't working.. any thoughts?
gmarcoux said:
I've tried installing this via hboot both unlocked and relocked and it doesn't actually do anything. it checks the image then just goes back to hboot. Any Idea what I'm doing wrong?
Click to expand...
Click to collapse
I am in the same boat. Let me if you figure it out.
hello to every one, can anyone help me with installing the stock rom?
the problem is that after i relock my phone & put the RUU file in the root folder ( with root explorer), i turn of, got in to the bootloder and nothing happened.
what do i need to do from here?
Sent from my HTC_Amaze_4G using XDA App
So, if I were to flash the 1.26 or 1.35, I wonder if I'd get working WiFi calling? Anyone that is still on 1.36.531.4, does your WiFi calling still work?
Some great news.. the evo view 4g is now officially unlockable from HTC via htcdev.com. hope to see some magic happen now
Sent from my Nexus S 4G using Tapatalk
This belongs in general.
Thx for info ThoughtHalo, the skilled dev above me (globatron) actually brought us to the dev game in HC before HTC.. That's the greatness of XDA, were always ahead of the game.
So what does this mean for us with stock GB looking to go to HC but want root?
It means now you should be able to flash a recovery and install a superuser zip
this still sucks compared to s-off. really wish HTC would stop shafting it's loyal customers so hard. It's like they want us to buy galaxy tabs :-(.
at least all of the updaters have a way to root now.
contradude said:
this still sucks compared to s-off. really wish HTC would stop shafting it's loyal customers so hard. It's like they want us to buy galaxy tabs :-(.
at least all of the updaters have a way to root now.
Click to expand...
Click to collapse
It means more than that, they've given us a way to roll back to GB, which in turn means that OTA updaters can get S-OFF after all.
It means now we can also just fastboot flash everything regardless of what firmware we are on which is even better.
Indirect said:
It means now we can also just fastboot flash everything regardless of what firmware we are on which is even better.
Click to expand...
Click to collapse
If you rollback to GB and S-OFF then yes, otherwise you are way off the mark, it doesn't even come close to allowing you to do that.
With an unlocked bootloader, you should be able to flash new recoveries and other things...unlocked from HTC is the same as S-off. It allows the flashing of unsigned firmware. Unless this device is unlike every other device I've had from HTC, I'm pretty sure I'm correct.
Although since I never had to use it on any of my devices (Never had something like Evo 3D) then I might be incorrect. However, based off my thoughts as an unlocked bootloader means you can flash new recovery, boot, and OTA updates that are unsigned / have broken signatures.
If you're happy with it fine, but you're misinformed. It's really not the same as S-OFF at all as many including myself have already explained. I can't be bothered with repeating the explanations again.
I apologize for being mistaken but provide information so I can be correct in the future
Sent by breaking the sound barrier
Indirect said:
I apologize for being mistaken but provide information so I can be correct in the future
Sent by breaking the sound barrier
Click to expand...
Click to collapse
Well one difference I know about between soff and htc unlock is that you have to fastboot flash kernels and recoveries you cant flash them through cwm when the device is only htc unlocked, however you can get fastboot to flash them, at least thats how it is on the evo 3d.
mark920 said:
Well one difference I know about between soff and htc unlock is that you have to fastboot flash kernels and recoveries you cant flash them through cwm when the device is only htc unlocked, however you can get fastboot to flash them, at least thats how it is on the evo 3d.
Click to expand...
Click to collapse
10 points for mark
flashing radios;custom(or stock) RUUs when unlocked; downgradability (not blocked on stock view hboot this time);but the s-off hboot protects itself from getting replaced so no nasty OTA surprises;bypassing CID restrictions, there are a few more but they are probably of no interest to most people.
EDIT: Yeah, also forgot HTC unlock erases your DRM keys.
That's good news... I'd assume I need to be back to the stock RUU S-ON to unlock it? As I already have the Rev. S-Off on my View now.
If it's not going to break it then I'll just go have it unlock it now.
globatron said:
10 points for mark
flashing radios;custom(or stock) RUUs when unlocked; downgradability (not blocked on stock view hboot this time);but the s-off hboot protects itself from getting replaced so no nasty OTA surprises;bypassing CID restrictions, there are a few more but they are probably of no interest to most people.
EDIT: Yeah, also forgot HTC unlock erases your DRM keys.
Click to expand...
Click to collapse
But all root apps work right? And you can still flash radios and custom RUUs through the bootloader, correct? And taking OTA's isn't smart when rooted either way. So what are the consequences of losing the DRM keys?
GadgetMonger said:
But all root apps work right? And you can still flash radios and custom RUUs through the bootloader, correct? And taking OTA's isn't smart when rooted either way. So what are the consequences of losing the DRM keys?
Click to expand...
Click to collapse
Correct, you can root and all apps will work, Wrong; go read, can't do radios or RUUS, Normally it's perfectly fine with a stock recovery and a protected hboot.
DRM keys are not really a problem unless you bought from watch or some other built-in thing like that.
Honestly, I couldn't care less which people do, but unlock is a pain for developers to deal with and frustrating when flashing roms. But I dislike incorrect statements like saying S-OFF and unlock are the same thing.
While its a "half assed s-off through fast boot, its still technically an s-off. Just not proper. So they aren't the same, just similar. They aren't however what people WANT on their devices.
Sent by breaking the sound barrier
Indirect said:
While its a "half assed s-off through fast boot, its still technically an s-off. Just not proper. So they aren't the same, just similar. They aren't however what people WANT on their devices.
Sent by breaking the sound barrier
Click to expand...
Click to collapse
Do this. Unlock with the HTC method then boot to bootloader. You will notice that your device is telling you that it is unlocked but still s-on. As far as I know s-on means exactly that and not "half assed" s-off. I dont think you're understanding the difference.
No I understand the difference. S-off means the entire device is no longer secured at all. You can flash anything from the device. With unlock, you can only flash using fast boot and you can't flash certain things like radios etc. Only kernels, recovery, and downgrading RUU's
Therefore, its a "halfassed" s-off
Sent by breaking the sound barrier
I was previously on the original HBOOT (first one) and S-Off.
I did NOT have the "TAMPERED" flag on my phone.
After upgrading to latest release I am on the latest HBOOT but now it's also flagged as "TAMPERED".
My understanding is being S-off a way to remove this should exists.
I've never done the HTC unlock as have always been S-Off.
Is it possible to get this removed on latest release without being 100% stock?
I know on some phones like the One you can modify a flag in one of the partitions.
I am on a stock rom just rooted so beyond seeing that flag it's not obvious I am rooted.
Thx
See this post
http://forum.xda-developers.com/showthread.php?p=50112366
Captain has included this mod l
Sent from my EVO using xda app-developers app
JManekia said:
See this post
http://forum.xda-developers.com/showthread.php?p=50112366
Captain has included this mod l
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Nope, he says:
Q8: My bootloader says "TAMPERED" after flashing the firmware. How to fix?
A: Just ignore it. It's no big deal.
Someone did a mod to remove the developer text but that's it. My understanding is the flag doesn't reside in the HBOOT directly but in some other area of the phone?
Run a RUU. It will remove the *TAMPERED* status. Your phone will remain unlocked, and it be displayed as such.
If you don't have easy access to a PC, one of the easiest solutions is to download the VipeRUU zip to your phone, extract the rom.zip to your ext SD, rename it to PJ75IMG.zip, and flash it through the bootloader. The next time that you reboot into the bootloader after the process is completed, then TAMPERED should be gone.
I'm just speculating, but maybe you removed the tampered status before by using the Regaw Bootloader Customizer, which only edits the bootloader info, and doesn't actually change anything for the phone itself. It's only a cosmetic change.
aarsyl said:
Run a RUU. It will remove the *TAMPERED* status. Your phone will remain unlocked, and it be displayed as such.
If you don't have easy access to a PC, one of the easiest solutions is to download the VipeRUU zip to your phone, extract the rom.zip to your ext SD, rename it to PJ75IMG.zip, and flash it through the bootloader. The next time that you reboot into the bootloader after the process is completed, then TAMPERED should be gone.
I'm just speculating, but maybe you removed the tampered status before by using the Regaw Bootloader Customizer, which only edits the bootloader info, and doesn't actually change anything for the phone itself. It's only a cosmetic change.
Click to expand...
Click to collapse
That's what I did - noticed after the 4.3 RUU that it went from "Unlocked/Tampered" to just "Unlocked." I kinda want to also modify the "Unlocked" text as I did before with Regaw's tool, I'll have to look into whether it will work.
SilverZero said:
That's what I did - noticed after the 4.3 RUU that it went from "Unlocked/Tampered" to just "Unlocked." I kinda want to also modify the "Unlocked" text as I did before with Regaw's tool, I'll have to look into whether it will work.
Click to expand...
Click to collapse
There's a reason why I didn't suggest using that tool. You kinda need to MAKE SURE that you know your bootloader status. If you activate S-On twice in a row, that baby's definitely gonna brick. I rather know what my bootloader is supposed to say, because I'm really the only person looking at it. What difference will it really make?
aarsyl said:
There's a reason why I didn't suggest using that tool. You kinda need to MAKE SURE that you know your bootloader status. If you activate S-On twice in a row, that baby's definitely gonna brick. I rather know what my bootloader is supposed to say, because I'm really the only person looking at it. What difference will it really make?
Click to expand...
Click to collapse
Well that's why I said I'd have to look into it. I assumed it wouldn't work with the new HBOOT, and I guess I don't care one way or the other. But for anybody else reading this, don't try it.
On the other hand, I climb mountains because they're there. If I want it to say "Hacked" instead of "Unlocked" and I can do it without screwing things up, I might do it just to screw with the guy who buys it from me down the road.
bryanu said:
I was previously on the original HBOOT (first one) and S-Off.
I did NOT have the "TAMPERED" flag on my phone.
After upgrading to latest release I am on the latest HBOOT but now it's also flagged as "TAMPERED".
My understanding is being S-off a way to remove this should exists.
I've never done the HTC unlock as have always been S-Off.
Is it possible to get this removed on latest release without being 100% stock?
I know on some phones like the One you can modify a flag in one of the partitions.
I am on a stock rom just rooted so beyond seeing that flag it's not obvious I am rooted.
Thx
Click to expand...
Click to collapse
comment withdrawn after further investigation.
redm1st said:
Originally for Hboot 2.09 but should work for Hboot 2.10. (don't quote me on that though)
Click to expand...
Click to collapse
Please don't anyone on the 2.10 HBOOT flash this! Please remove this attachment.
EDIT: This post is what I mean. You have to understand what the Bootloader Customizer actually does (which is explained in the thread) and know that flashing this would bork all the things. This is literally a 2.09 HBOOT. The 2.10 HBOOT is what accommodates the new partition layout, so flashing this will break that and prevent the device from booting up. The issue is the signed boot.img. That's why you see the tampered flag. I assume you're not using my stock rooted? You updated directly from RUU, and then rooted it manually? The signed boot.img sees unsigned recovery img and throws up that tampered flag. It's not going to affect the working of the device, so why worry about it? You can flash the boot image from my stock rooted if you want it to go away.
Captain_Throwback said:
Please don't anyone on the 2.10 HBOOT flash this! Please remove this attachment.
EDIT: This post is what I mean. You have to understand what the Bootloader Customizer actually does (which is explained in the thread) and know that flashing this would bork all the things. This is literally a 2.09 HBOOT. The 2.10 HBOOT is what accommodates the new partition layout, so flashing this will break that and prevent the device from booting up. The issue is the signed boot.img. That's why you see the tampered flag. I assume you're not using my stock rooted? You updated directly from RUU, and then rooted it manually? The signed boot.img sees unsigned recovery img and throws up that tampered flag. It's not going to affect the working of the device, so why worry about it? You can flash the boot image from my stock rooted if you want it to go away.
Click to expand...
Click to collapse
I flashed everything from your post.
I just want the word Tampered gone, don't care if it's done officially or just visually through some other mod.
I currently am S-Off, Locked and says Tampered.
bryanu said:
I flashed everything from your post.
I just want the word Tampered gone, don't care if it's done officially or just visually through some other mod.
I currently am S-Off, Locked and says Tampered.
Click to expand...
Click to collapse
Do a nandroid and then unlock your bootloader.
Captain_Throwback said:
Do a nandroid and then unlock your bootloader.
Click to expand...
Click to collapse
So I have "Tampered" because I am not unlocked?
Take this from a guy who has had 6 replacement phones and 4 of them hard bricked. QualcomDownload Mode. Lol.
Anyways I wanted to get rid of the tampered flag so I did what shouldnt be done and used the One's tool with aroma and only chose to remove rltampered flag.
It worked.
Note that that was my other phone before I hard bricked it but that was because I messed up my EFS folder.
Im not saying that anyone should use it. Do at your own risk I sure did and I just used it on my replacement evo after doing soff.
Sent from my EVO using Tapatalk
chemjb said:
Take this from a guy who has had 6 replacement phones and 4 of them hard bricked. QualcomDownload Mode. Lol.
Anyways I wanted to get rid of the tampered flag so I did what shouldnt be done and used the One's tool with aroma and only chose to remove rltampered flag.
It worked.
Note that that was my other phone before I hard bricked it but that was because I messed up my EFS folder.
Im not saying that anyone should use it. Do at your own risk I sure did and I just used it on my replacement evo after doing soff.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I had already given up and just installed terminal emulator on my phone and ran the following as su:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
that got rid of it properly without requiring any flashing, fake boot loader modifications etc.
@bryanu: just for my own education, what does that actually do when you type that in terminal. Meaning, I know you said it removes the "tamper" word, but how does it do it. If it is to lengthy to answer, no problem. Just wondering... Thanks!
Sent from my EVO using Tapatalk 2
puhiniho said:
@bryanu: just for my own education, what does that actually do when you type that in terminal. Meaning, I know you said it removes the "tamper" word, but how does it do it. If it is to lengthy to answer, no problem. Just wondering... Thanks!
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
It resets the flag that controls that showing or not essentially.
bryanu said:
I had already given up and just installed terminal emulator on my phone and ran the following as su:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
that got rid of it properly without requiring any flashing, fake boot loader modifications etc.
Click to expand...
Click to collapse
Worked like a charm ,
Thanks
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Need to wait for hboot to be modded to have that removed
Wonders_Never_Cease said:
Need to wait for hboot to be modded to have that removed
Click to expand...
Click to collapse
Ah okay thanks. Wasnt sure if Hboot was universal or if it was by build.
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Wonders_Never_Cease said:
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Click to expand...
Click to collapse
I'm on build 2.22.401.5 running VenomOne rom, S-Off, rooted all the good stuff. Will your hboot mod work for mine?
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Wonders_Never_Cease said:
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Click to expand...
Click to collapse
OK and I can just install either one of those hboots over my existing one and it wont brick my phone or is this more to this?
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Wonders_Never_Cease said:
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Click to expand...
Click to collapse
Found it, thanks man. Gonna mess with it a little later.
CavyS said:
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Click to expand...
Click to collapse
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
thinkhope said:
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
Click to expand...
Click to collapse
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
CavyS said:
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
Click to expand...
Click to collapse
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
redpoint73 said:
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
Click to expand...
Click to collapse
It was just easier for me to fallow a set of instructions going step by step than jumping around just to avoid 1 easy step.
thinkhope said:
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah still works, you might of read that Firewater for some people doesnt work on 4.4.3. For me Firewater worked and I'm S-Off for some people it doesnt and you have to use Sunshine in that case.
thinkhope said:
So the toolkit still works??
Click to expand...
Click to collapse
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
redpoint73 said:
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
Click to expand...
Click to collapse
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Click to expand...
Click to collapse
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
redpoint73 said:
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
Click to expand...
Click to collapse
I definitely did have the evita. Had to alter the cid to make htc dev believe it was a different phone or something like that, if I remember correctly.
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Well, sounds easy enough. I will be attempting later tonight after work. Thanks for all of your help. If it's OK, mind if I PM you if something goes wrong?
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Click to expand...
Click to collapse
S-off is needed to flash radio, hboot, SIM unlock, and some other things. But not for root or to flash ROMs. Pretty much similar to how things were on the EVITA; with the exception that boot.img will flash automatically along with the ROM (not possible on most hboots on the EVITA, and had to be flashed manually with fastboot).
It sounds like you are already on the "official" 2.23 software (Android 4.4.3) by OTA? If so, you don't need to update firmware (radio, hboot, etc.) as the OTA already updated it. Otherwise, s-off is needed to flash the firmware manually; which is pretty much required for any 2.xx Sense based custom ROMs (otherwise there will be serious bugs like very long boot times, broken WiFi, Bluetooth). While s-off is not strictly needed to flash the ROM (it will flash correctly) things just won't run right if firmware is outdated. This is the only reason you would "need" to have s-off for flashing ROMs. AOSP and GPE ROMs won't suffer this issue.
But if you are already on the new OTA, this isn't an issue for flashing any ROM. You can verify by looking at the hboot version and baseband. If you are on hboot 3.18 and baseband 1.19; your firmware is up to date, and won't be an issue for running any ROMs.
thinkhope said:
mind if I PM you if something goes wrong?
Click to expand...
Click to collapse
I actually prefer you just posting to the forums. Either to an existing relevant thread, or start a new one if a relevant one does not already exist.
Couple reasons for this:
- Info given to you can help others reading the forums, and benefit the community as a whole instead of being hidden away in PM
- You can get help from more than just one user. I don't claim to even remotely know everything, and often its helpful to have more than one set of eyes on a problem (especially the tougher ones). And I might not even be online to help.
In particular for the 2nd point: my wife and I are going to be having a baby, with scheduled induction tomorrow (Sept. 5) unless it happens by itself sooner. So I won't be available to help you when that happens, anyway!
In any case, good luck!
http://dl3.htc.com/application/RUU_M8_UL_K443_SENSE60_ATT_MR_Cingular_US_2.23.502.3_Radio_1.19.213311491.A22G_20.51A.4198.01L_F_release_387305_signed_2.exe from http://www.htc.com/us/support/htc-one-m8-att/news/
t5620 said:
http://dl3.htc.com/application/ruu_m8_ul_k443_sense60_att_mr_cingular_us_2.23.502.3_radio_1.19.213311491.a22g_20.51a.4198.01l_f_release_387305_signed_2.exe from http://www.htc.com/us/support/htc-one-m8-att/news/
Click to expand...
Click to collapse
sweet thank you!
Andrew149 said:
sweet thank you!
Click to expand...
Click to collapse
you are welcome.
Remember that for the ruu to work you need to relock the bootloader and have stock recovery. and unroot. it works with S-OFF so no need to S-ON
t5620 said:
you are welcome.
Remember that for the ruu to work you need to relock the bootloader and have stock recovery. and unroot. it works with S-OFF so no need to S-ON
Click to expand...
Click to collapse
Umm I've never needed to lock my boot loader with s off to ruu 4.4.2. Are you sure?
Andrew149 said:
Umm I've never needed to lock my boot loader with s off to ruu 4.4.2. Are you sure?
Click to expand...
Click to collapse
Bootloader lock only needed for s-on.
Wow, same day RUU as the OTA? Unbelievable!
Andrew149 said:
Umm I've never needed to lock my boot loader with s off to ruu 4.4.2. Are you sure?
Click to expand...
Click to collapse
I'm not 100% sure.. but ,I always re-lock the bootloader just in case
How can I install this with S-on? Couldn't get S-off because firewater is broken for me.
My phone is rooted and the bootloader is unlocked. How can I lock the bootloader without S-off?
iArtisan said:
How can I install this with S-on? Couldn't get S-off because firewater is broken for me.
My phone is rooted and the bootloader is unlocked. How can I lock the bootloader without S-off?
Click to expand...
Click to collapse
you could try Sunshine to get S-OFF it cost $25 dollars but it can S-OFF your device.
But I think that you do not need to be s-off to run the RUU, if you want to easily relock the bootloader use tthe HTC One 2014 (M8) All-In-One Toolkit http://forum.xda-developers.com/showthread.php?t=2699065 its the easiest way
Can I use this to go from Google Play Edition back to stock Sense assuming I change my CID back to AT&T?
I am S-OFF and Bootloader Unlocked and obviously ATT branded.
Yes
Sent from my HTC One_M8 using XDA Free mobile app
So for the people who been running this ruu for a few weeks have you found any bugs?
Andrew149 said:
So for the people who been running this ruu for a few weeks have you found any bugs?
Click to expand...
Click to collapse
X2. Would like to know as well. Thanks.
Andrew149 said:
So for the people who been running this ruu for a few weeks have you found any bugs?
Click to expand...
Click to collapse
no bugs so far but battery life isn't that great as with the last FW although there is no battery drain like with the OTA but I'm not impressed with the battery performance
Sent from my HTC One_M8 using XDA Free mobile app
I have my phone set up like I want it. Stable, everything works. Running 4.4.2 rooted, unlocked, twrp recovery, etc. All the apps I want. So on and so forth.
Will nandroid backup made now work after I run this ruu? Basically update the os and then recover everything the way I have it set up now?
Sorry for asking what seems, even to me, a basic beginners question.
Question
lostangelintx said:
I have my phone set up like I want it. Stable, everything works. Running 4.4.2 rooted, unlocked, twrp recovery, etc. All the apps I want. So on and so forth.
Will nandroid backup made now work after I run this ruu? Basically update the os and then recover everything the way I have it set up now?
Sorry for asking what seems, even to me, a basic beginners question.
Click to expand...
Click to collapse
In short...No. First off, you can't install the 4.4.3 update if you have a TWRP recovery installed. You have to have the stock recovery in order to do the update. But...for the sake of argument, you did the update and...then re-rooted and restored your nandroid. You would in effect overwrite the update and put yourself back to where you started (if that makes any sense).
My advice would be to install a custom ROM that containes the 4.4.3 update already...or put a stock recovery back on your phone and do the update. There is a nice all-in-one update you can run right off the sdcard using Hboot. I did it and it was flawless.
Either way, you'll most likely be setting up your phone again but that really shouldn't be too bad. Take some screenshots so you will remember just how you had things.
Hope this helps and good luck.
Scott
lostangelintx said:
I have my phone set up like I want it. Stable, everything works. Running 4.4.2 rooted, unlocked, twrp recovery, etc. All the apps I want. So on and so forth.
Will nandroid backup made now work after I run this ruu? Basically update the os and then recover everything the way I have it set up now?
Sorry for asking what seems, even to me, a basic beginners question.
Click to expand...
Click to collapse
I have to ask, if you went through all that trouble, why would you ever want to run ATT software? You could have easily converted to Dev Edition and never looked back.
hack14u said:
I have to ask, if you went through all that trouble, why would you ever want to run ATT software? You could have easily converted to Dev Edition and never looked back.
Click to expand...
Click to collapse
I can't answer for the OP, but coming from the factory unlocked version and having tried various firmwares and ROMs (including Dev), the ATT RUU is the only one that gives me true LTE speeds.
Scott, could you point me towards that update using Hboot?
scott500 said:
In short...No. First off, you can't install the 4.4.3 update if you have a TWRP recovery installed. You have to have the stock recovery in order to do the update. But...for the sake of argument, you did the update and...then re-rooted and restored your nandroid. You would in effect overwrite the update and put yourself back to where you started (if that makes any sense).
My advice would be to install a custom ROM that containes the 4.4.3 update already...or put a stock recovery back on your phone and do the update. There is a nice all-in-one update you can run right off the sdcard using Hboot. I did it and it was flawless.
Either way, you'll most likely be setting up your phone again but that really shouldn't be too bad. Take some screenshots so you will remember just how you had things.
Hope this helps and good luck.
Scott
Click to expand...
Click to collapse
Sure thing... Here it is..
http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486