Related
Due to WiFi issues on the release day OS, I took the 1.22 OTA and screwed root. I knew it would happen but the fixes outweighed the issues. I waited to see if root would be achieved via Regaw or the like since I didn't want to lose any of my configuration. Now... Sense 4.1 was just too tempting to pass up and since I wasn't rooted anyways, I went for it.
I decided to attempt root and start from scratch anyways as I was having random app issues and some bloat problems.
The root method from HTC Dev worked flawlessly on the new new OTA and I was able to load TWRP and SuperUser via fastboot (instructions can be found by searching as I did).
So now here is the question: where does this leave me as far as flashing ROMs... Obviously I am aware that I am S-On and know those limitations. My issue is if and where any limits may apply now that I am HBOOT 1.19. Will I be stuck with only 2.13 ROMs that we're built based on the new HBOOT or can I flash any Rom based on 2.13 (or even older revisions)? I cant risk bricking so I am asking to be cautious as well as your answers providing any new users coming in with new phones running the latest OTA.
Thanks
Why did HTC update hboot 1.15? Because they discovered an exploit flaw that we could gain S-OFF with, which is FAR better than being on HTC Dumlock. If you are not concerned with obtaining S-OFF via LazyPanda and the like, this should not be a concern.
Also, being on the new hboot means that backwards compatibility to ROMs that are not based on the new OTA could become an issue.
Sent from my LTEVO via XDA Premium
New h boot for you only means that you won't be able to get s-off for a very long time probably since nobody has figured out how to even s-off h boot 1.15 yet. You shouldn't have an issue flashing any rom from my understanding as long as it's through recovery.
Edit : I would listen to Michael on this one regarding ROMs sounds like he knows more lol.
Sent from my EVO using xda app-developers app
natefuhr said:
Due to WiFi issues on the release day OS, I took the 1.22 OTA and screwed root. I knew it would happen but the fixes outweighed the issues. I waited to see if root would be achieved via Regaw or the like since I didn't want to lose any of my configuration. Now... Sense 4.1 was just too tempting to pass up and since I wasn't rooted anyways, I went for it.
I decided to attempt root and start from scratch anyways as I was having random app issues and some bloat problems.
The root method from HTC Dev worked flawlessly on the new new OTA and I was able to load TWRP and SuperUser via fastboot (instructions can be found by searching as I did).
So now here is the question: where does this leave me as far as flashing ROMs... Obviously I am aware that I am S-On and know those limitations. My issue is if and where any limits may apply now that I am HBOOT 1.19. Will I be stuck with only 2.13 ROMs that we're built based on the new HBOOT or can I flash any Rom based on 2.13 (or even older revisions)? I cant risk bricking so I am asking to be cautious as well as your answers providing any new users coming in with new phones running the latest OTA.
Thanks
Click to expand...
Click to collapse
Yes, you will be stuck flashing 2.13 roms with the 2.13 kernel. However, you can use one of the workaround methods (fastboot, flash image gui, twrp dumlock) to flashing an older kernel, and then flash roms based on a previous OTA base.
A ROM doesn't include an HBoot though, so there shouldn't be ROM/HBoot compatibility issues, right?
No, you can flash whatever version of android you want
Rxpert said:
No, you can flash whatever version of android you want
Click to expand...
Click to collapse
I don't think that's quite right (I could be wrong though).
If he wants to flash a JB-based ROM, he will definitely have to flash the boot.img separately via one of the workarounds mentioned.
If he wants to move between Sense-based ROMs, he *might* be OK. But he will not get any tweaks the dev may have made to the kernel included with his respective ROM.
I was referring to the question above me that asked about ROMs interfering with hboots
Having an old ROM on a new hboot won't cause issues.
Naturally, you need to have a working kernel for your ROM. So yes, you'll need to make sure you have the right kernel.
If he goes from any ROM to a ROM on a different base you'll have to install the correct kernel. . But I don't think that's what he was asking
Sent from my EVO using Tapatalk 2
Got it. I thought you were replying in general.
natefuhr said:
Due to WiFi issues on the release day OS, I took the 1.22 OTA and screwed root. I knew it would happen but the fixes outweighed the issues. I waited to see if root would be achieved via Regaw or the like since I didn't want to lose any of my configuration. Now... Sense 4.1 was just too tempting to pass up and since I wasn't rooted anyways, I went for it.
I decided to attempt root and start from scratch anyways as I was having random app issues and some bloat problems.
The root method from HTC Dev worked flawlessly on the new new OTA and I was able to load TWRP and SuperUser via fastboot (instructions can be found by searching as I did).
So now here is the question: where does this leave me as far as flashing ROMs... Obviously I am aware that I am S-On and know those limitations. My issue is if and where any limits may apply now that I am HBOOT 1.19. Will I be stuck with only 2.13 ROMs that we're built based on the new HBOOT or can I flash any Rom based on 2.13 (or even older revisions)? I cant risk bricking so I am asking to be cautious as well as your answers providing any new users coming in with new phones running the latest OTA.
Thanks
Click to expand...
Click to collapse
I'd like to re-root after taking the OTA and I've searched all over for the instructions on how to load TWRP and SuperUser via fastboot, but can't find it. Can you assist?
Thanks
Rxpert said:
I was referring to the question above me that asked about ROMs interfering with hboots
Having an old ROM on a new hboot won't cause issues.
Naturally, you need to have a working kernel for your ROM. So yes, you'll need to make sure you have the right kernel.
If he goes from any ROM to a ROM on a different base you'll have to install the correct kernel. . But I don't think that's what he was asking
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Correct me if I'm wrong, but, a ROM includes a Kernel, so when you flash a ROM you're swapping kernels.
The only kernel incompatibility would be if you flashed a ROM then flashed a Kernel, then you have to be careful.
If anybody is absolutely certain that this isn't the case and not just guessing, let me know and I'll stand corrected.
pbarrett said:
Correct me if I'm wrong, but, a ROM includes a Kernel, so when you flash a ROM you're swapping kernels.
The only kernel incompatibility would be if you flashed a ROM then flashed a Kernel, then you have to be careful.
If anybody is absolutely certain that this isn't the case and not just guessing, let me know and I'll stand corrected.
Click to expand...
Click to collapse
That's true for 1.12, since it allows you to flash kernels through recovery. The newer versions don't. That's the reason for using the fastboot or dumlock workarounds. That being said, I haven't heard anyone confirm yet that these methods still work on 1.19...I'm interested to know.
Sent from my EVO LTE
I've been waiting for s-off forever, then it finally came but long story short gf saw update (hboot 1.15) and accepted and I'm wondering since there's still no s-off, and this is a very silly question but I've never used Dev unlock, is nandroid backup possible in case something does go wrong
om4 said:
I've been waiting for s-off forever, then it finally came but long story short gf saw update (hboot 1.15) and accepted and I'm wondering since there's still no s-off, and this is a very silly question but I've never used Dev unlock, is nandroid backup possible in case something does go wrong
Click to expand...
Click to collapse
From what I can tell... No. You have to run HTC Dev first in order to get to where you can load a recovery program at which point you will have already had to wipe your phone to factory defaults.
It's unfortunate and the main reason I waited so long to unlock this way but as previously stated, Sense 4.1 was too hard to pass on
om4 said:
I've been waiting for s-off forever, then it finally came but long story short gf saw update (hboot 1.15) and accepted and I'm wondering since there's still no s-off, and this is a very silly question but I've never used Dev unlock, is nandroid backup possible in case something does go wrong
Click to expand...
Click to collapse
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
PsiPhiDan said:
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
no, I let her take my phone for the weekend. she went camping with her her family and I dont feel comfortable knowing shes out in the middle of no where without a phone. her phone was disconnected because she lost her job 2 months ago and Im not about to pay $135 on top of my own bill
PsiPhiDan said:
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Hell, I don't even let my girlfriend use my phone unless she asks nicely and I always keep an eye on her.
SoraX64 said:
Hell, I don't even let my girlfriend use my phone unless she asks nicely and I always keep an eye on her.
Click to expand...
Click to collapse
Mine doesn't even know how to use my phone...it's "confusing". IPhone ftw
Sent from my EVO LTE
pbarrett said:
Correct me if I'm wrong, but, a ROM includes a Kernel, so when you flash a ROM you're swapping kernels.
The only kernel incompatibility would be if you flashed a ROM then flashed a Kernel, then you have to be careful.
If anybody is absolutely certain that this isn't the case and not just guessing, let me know and I'll stand corrected.
Click to expand...
Click to collapse
Yes, every ROM includes a kernel.
But Hboot 1.15 and above do not let you flash things to the boot partition in recovery. The kernel goes in the boot partition. So you can't flash kernels normally through recovery.
If your on a sense ROM and flash an AOSP rom, the phone wont boot
If your on an AOSP ROM and flash a sense ROM, the phone wont boot
If your on an old base and flash a new base, the ROM will have issues (if it even boots)
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-wip.html
PsiPhiDan said:
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Next, we are going to hear crap like, "my pet hamster ate my nandroid thumb drive."
Sent from my LTEVO via XDA Premium
Do I need to update radios? What is the benefit of updating radios, RUU's, etc.
Sent from my Infected Rezound using xda app-developers app
gleggie said:
Do I need to update radios? What is the benefit of updating radios, RUU's, etc.
Sent from my Infected Rezound using xda app-developers app
Click to expand...
Click to collapse
latest RUU is 4.03.605.2 which i think has 2.22.10.0801r, 2.22.10.0803r
with 2.27 Hboot which you can check by going into bootloader
im not a radio genius. So someone correct me if I'm wrong
but check the rest of your "about phone section" for RUU information
4.03.605.2 is the newest radio just google i and you will find it. I use this one and I think it has more stable 4G signal,
Be advised that 4.03.605.2 is a Leak. Since you are s-on if you flash the global leak you will not be able to take any official OTAs.
I would use the official RUU which will update you and then take the OTA that just came out a couple weeks ago. Find the RUU here:
http://androidfiles.org/ruu/?dir=Vigor
It's the top one, 3.14.605.12
Then if you are not happy with your reception you can always go up to the global leak if you want, you just can't go back down to a lower version without s-off.
Before you do this back up everything you need as this will wipe your phone and put it to factory stock.
You need to relock your phone to run it:
fastboot oem lock
And then you'll need to unlock again and flash Amon Ra before flashing a custom ROM again.
Question about "build"
feralicious said:
Be advised that 4.03.605.2 is a Leak. Since you are s-on if you flash the global leak you will not be able to take any official OTAs.
I would use the official RUU which will update you and then take the OTA that just came out a couple weeks ago. Find the RUU here:
http://androidfiles.org/ruu/?dir=Vigor
It's the top one, 3.14.605.12
Then if you are not happy with your reception you can always go up to the global leak if you want, you just can't go back down to a lower version without s-off.
Before you do this back up everything you need as this will wipe your phone and put it to factory stock.
You need to relock your phone to run it:
fastboot oem lock
And then you'll need to unlock again and flash Amon Ra before flashing a custom ROM again.
Click to expand...
Click to collapse
So, this build number is confusing me. This is what I presently have and I'm not sure how I got here
Baseband 2.22.10.0801 /....803
Hboot 2027
Build 1.11.401.110
Seems like everyone else with this radio combo is on build 4.03 or something like that.
Is there any advantage to me upgrading to that build? I am S-Off and hate the prospect of relocking or having my internal SD wiped if I don't have to go through that.
Build number has nothing to do with firmware. It's set by the ROM. You're already on the global firmware.
shrike1978 said:
Build number has nothing to do with firmware. It's set by the ROM. You're already on the global firmware.
Click to expand...
Click to collapse
Thanks. I can sleep now.
Is there a rooted version of the RUU? I'm relatively new to locking and unlocking my device so I'm not sure if I'm ready to do all that by myself. (a friend helped me root my device in the past)
gleggie said:
Is there a rooted version of the RUU? I'm relatively new to locking and unlocking my device so I'm not sure if I'm ready to do all that by myself. (a friend helped me root my device in the past)
Click to expand...
Click to collapse
Ruu takes away root when you flash it. But you can re root in custom recovery
Sent from my ADR6425LVW using xda app-developers app
bunchies said:
Ruu takes away root when you flash it. But you can re root in custom recovery
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Ok thanks, I thought i read somewhere that there are custom RUU's that are built specifically for root users but i guess not.
Oh I've never heard of that befor. You may be thinking of the option of downgrading hboot for s-off users
Those are flashed the same way like ruu's
Sent from my ADR6425LVW using xda app-developers app
I'm just learning that there is a new OTA. Whatever the case, I have not received it yet but am curious as to how I should handle it. This phone still confuses me a bit when it comes to unlocking etc.
Currently I am S-On, Rooted and running Shrike's PAC-Man rom. I kinda been lazy about staying up to date with everything and just got in my routine of flashing new releases.
Now i'm reading about this update and new hboot versions and wondering what I should be doing now. Should I accept the update in my current status or should I be doing something else to update? What about my hboot version, i'm still at 2.25. Should I be updating that myself or just take the OTA to handle it. My apologies if this is a redundant question.
braveally said:
I'm just learning that there is a new OTA. Whatever the case, I have not received it yet but am curious as to how I should handle it. This phone still confuses me a bit when it comes to unlocking etc.
Currently I am S-On, Rooted and running Shrike's PAC-Man rom. I kinda been lazy about staying up to date with everything and just got in my routine of flashing new releases.
Now i'm reading about this update and new hboot versions and wondering what I should be doing now. Should I accept the update in my current status or should I be doing something else to update? What about my hboot version, i'm still at 2.25. Should I be updating that myself or just take the OTA to handle it. My apologies if this is a redundant question.
Click to expand...
Click to collapse
First, the updated wont be pushed to you because you aren't on a sense rom, and i think the AOSP has the OTAkill.apk but i would need to look for it.
Second, the update is a good thing. not only does it have a new hboot but it has new radios, firmware and other goodies for the phone.
if you were to do the update, i wouldnt wait for VZW to push it. there is a zip that is in the development forum that you may flash to get the benefits of the update.
if you go down this route it will make the phone 100% stock. You would have to do the dev unlock with token and flash a recovery to get back to root status.
if you were to do this you also need to back up internal sd card just in case.
EDIT: Here are the steps you would take if you wanted to update the phone.
http://forum.xda-developers.com/showpost.php?p=40831457&postcount=59
credit goes to brenuga give him all the thanks you can.
synisterwolf said:
First, the updated wont be pushed to you because you aren't on a sense rom, and i think the AOSP has the OTAkill.apk but i would need to look for it.
Second, the update is a good thing. not only does it have a new hboot but it has new radios, firmware and other goodies for the phone.
if you were to do the update, i wouldnt wait for VZW to push it. there is a zip that is in the development forum that you may flash to get the benefits of the update.
if you go down this route it will make the phone 100% stock. You would have to do the dev unlock with token and flash a recovery to get back to root status.
if you were to do this you also need to back up internal sd card just in case.
EDIT: Here are the steps you would take if you wanted to update the phone.
http://forum.xda-developers.com/showpost.php?p=40831457&postcount=59
credit goes to brenuga give him all the thanks you can.
Click to expand...
Click to collapse
Thanks and thank you brenuga. That clears things up for me.
Is there a better S-Off method? In S-Off and don't want to lose root again and have to lock the bootloader
Sent from my ADR6425LVW using xda app-developers app
sk8bert12 said:
Is there a better S-Off method? In S-Off and don't want to lose root again and have to lock the bootloader
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Flash this in HBOOT. Only will work for s-off people
http://forum.xda-developers.com/showpost.php?p=40767819&postcount=33
sk8bert12 said:
Is there a better S-Off method? In S-Off and don't want to lose root again and have to lock the bootloader
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You can be S-OFF and still get the OTA, you just have to be pure stock, or you can flash the files in the thread which Flyhalf posted below.
On my last Rezound, I flashed the updated hboot and radios while already S-OFF, rooted and running Nils' ROM. On my current ROM, I got the OTA downloaded while still pure stock, then unlocked bootloader, flashed Amon Ra, rooted, then got S-OFF. Obviously, if there are any subsequent OTA's, I'll have to wait for a flashable.
Flyhalf205 said:
Flash this in HBOOT. Only will work for s-off people
http://forum.xda-developers.com/showpost.php?p=40767819&postcount=33
Click to expand...
Click to collapse
Thanks for the link/post. But what does this exactly do to an S-Off Rezound? Will this update/install just the HBOOT/Radios?
I'm on Ineffabilis Deus v1.2 ICS 4.0.3. I believe this might have been from the leaked global ruu.
DigiDave said:
Thanks for the link/post. But what does this exactly do to an S-Off Rezound? Will this update/install just the HBOOT/Radios?
I'm on Ineffabilis Deus v1.2 ICS 4.0.3. I believe this might have been from the leaked global ruu.
Click to expand...
Click to collapse
That was from the Global Leak. But the zip will just update firmware such as hboot and radio and few other stuff
I'm s-off. If I flash the latest RUU (whatever it is), then get the new global OTA update, I will retain my s-off-ness, correct? I'll just have to re-root and flash a recovery?
rsage said:
I'm s-off. If I flash the latest RUU (whatever it is), then get the new global OTA update, I will retain my s-off-ness, correct? I'll just have to re-root and flash a recovery?
Click to expand...
Click to collapse
No zip file of any kind will get you back to s-on. you must use fastboot to write to the secure flag. FYI
I am using a T-mobile HTC One. It was previously rooted. I restored to stock by using the RUU from HTC. I unlocked the bootloader so I currently have unlocked S-on. My HBOOT Ver is: 1.44.0000. Radio Version is 4A.17.3250.20. Am I screwed or can I still get S-OFF? I have tried Revone but it's not working. Any Ideas?
toaks said:
I am using a T-mobile HTC One. It was previously rooted. I restored to stock by using the RUU from HTC. I unlocked the bootloader so I currently have unlocked S-on. My HBOOT Ver is: 1.44.0000. Radio Version is 4A.17.3250.20. Am I screwed or can I still get S-OFF? I have tried Revone but it's not working. Any Ideas?
Click to expand...
Click to collapse
Sorry dude, pretty much screwed until they find a work around for the .11 update. I made the mistake of accidentally S-On and forgetting to lock instead of relocking my bootloader (wanted to return for warranty purposes). After that I've tried pretty much everything from downgrading to the stock ROM using customs ROMS trying to edit RUU's to work with my phone (Do not try this, easiest way to brick your very expensive phone) Nothing works as of now, Htc and t-mobile screwed us by not giving us the Stock RUU they knew what they were doing. But yes you have to wait.
*NOTE* On the otherhand i did learn that i didn't need to lock my bootloader to return it for warranty purposes the guy at the t-mobile store replaced it right there for me no questions asked. But the replacement i got came with the updated .11 ROM which means no S-Off for me still.
Damn. That's what I was afraid of. I just kept reading that as long as you had 1.44 h-boot it was still possible, but that doesn't appear to be the case. Well thanks anyway for responding.
Sent from my HTC One using XDA Premium HD app
Wait I thought you could s-off with that hboot i thought 5xxx was unable to s-off
You can s-off hboot 1.44 as long as you haven't taken the latest tmobile ota or used the tmobile ruu, they patched whatever it was that allowed us to s-off in the latest version
Sent from my HTC One using Tapatalk 4 Beta
Can we downgrade?
If we go back to .8, can we S-OFF? I want to take this thing to GPE, but need S-OFF.
Tylormde said:
If we go back to .8, can we S-OFF? I want to take this thing to GPE, but need S-OFF.
Click to expand...
Click to collapse
Take a look at http://forum.xda-developers.com/showthread.php?t=2314582&page=469
Lots of info there. Some of it conflicting but in a nutshell, no if you've taken the .11 update from T-Mobile.
i would wait till revone or moonshine get a fix on it.
Or go the HTC dev way
Sent from my HTC One using xda app-developers app
cenedbs assiduous
Tylormde said:
If we go back to .8, can we S-OFF? I want to take this thing to GPE, but need S-OFF.
Click to expand...
Click to collapse
I have tried this and was unsuccessful. Luckily I was able to run the RUU and it was fine again but it won't achieve S-OFF
You can downgrade from .11 to .8 using a custom ruu. Google " downgrade from .11 to .8 rootzwiki" and you'll find it.
Sent from my HTC One using Tapatalk
Ok guys not to sound stupid but I've rooted plenty of phones and have had pretty much every top tier phone. I've rooted all my android phones. I just don't understand the s-off portion of it all. I have s-off and currently rooted. What advantage do I have over someone that doesn't have s-off? I got my one already rooted so I never went through the process. I guess that's why I'm confused. I'm used to Samsung phones.
When the update comes next week should i just wait for a rooted version of it? I'm assuming so.
Sent from my HTC One using Tapatalk
S-OFF basically allows you to do 2 main things you couldn't otherwise pertaining to Roms and such:
1- flash unsigned RUUs. You can flash custom firmware that don't belong to your device. IE: you can flash the newest 4.3 firmware prior to 4.3 releasing for the T-Mobile One.
2: get yourself out of a jam. Here's a great example. Let's say you flashed the stock GPE recovery and ROM. Your S-ON. You wanted the full GPE experience. Your phone took the newest update. It will flash 1.54 Hboot and update the boot loader to the black GPE version although you are S-ON and not running the GPE device. Without S-ON your SOL if you needed to go back to stock for whatever reason because the HBoot can't be rolled back on S-ON.
Its a good protection to have in your back pocket IMO
Sent from my HTC One using Tapatalk
So that would explain how I am able to flash Roms from the international version. Well I guess I better be careful with any RUUs that are to come. I need to figure out how I'm going to update when the tmobile One's 4.3 update comes this week.
Sent from my HTC One using Tapatalk
Jjday7 said:
So that would explain how I am able to flash Roms from the international version. Well I guess I better be careful with any RUUs that are to come. I need to figure out how I'm going to update when the tmobile One's 4.3 update comes this week.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
So once S-OFF is achieved, can flashing any RUU set it back to S-ON? If so, how can that be avoided?
I have a tmobile phone flashed with launch WWE firmware; don't care about WiFi calling or any carrier bloat, but did want the 1700 HSPA+. I'm thinking of clean flashing to latest Tmobile RUU to get the supposed LTE reception improvements, then going from there to back to launch WWE and to latest WWE (to try to retain settings).
zaos said:
So once S-OFF is achieved, can flashing any RUU set it back to S-ON? If so, how can that be avoided?
I have a tmobile phone flashed with launch WWE firmware; don't care about WiFi calling or any carrier bloat, but did want the 1700 HSPA+. I'm thinking of clean flashing to latest Tmobile RUU to get the supposed LTE reception improvements, then going from there to back to launch WWE and to latest WWE (to try to retain settings).
Click to expand...
Click to collapse
No you would have to purposely set it back to s-on, an RUU won't do it. Would you be doing the tmobile Thu then installing WWE Rom ? Or flashing WWE RUU? Cause the ruu would just reset everything XP
Sent from my HTC One using Tapatalk
grim489 said:
No you would have to purposely set it back to s-on, an RUU won't do it. Would you be doing the tmobile Thu then installing WWE Rom ? Or flashing WWE RUU? Cause the ruu would just reset everything XP
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'm thinking:
Full backup with twrp
Flash ruu
Restore backup with twrp
Apply WWE update
Oh yeah then that should work just wanted to make sure :thumbup:
Sent from my HTC One using Tapatalk
grim489 said:
Oh yeah then that should work just wanted to make sure :thumbup:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks. It does seem a bit like voodoo magic but I want to avoid any possible issues that people in the radio only thread have reported.
use rumrunner to achirve s-off. thats the only way then use revone to reset tamper
toaks said:
I am using a T-mobile HTC One. It was previously rooted. I restored to stock by using the RUU from HTC. I unlocked the bootloader so I currently have unlocked S-on. My HBOOT Ver is: 1.44.0000. Radio Version is 4A.17.3250.20. Am I screwed or can I still get S-OFF? I have tried Revone but it's not working. Any Ideas?
Click to expand...
Click to collapse
use rumrunner to achieve s-off then use revone to reset tampered flag on your bootloader.
I have an HTC One M8 AT&T Branded but it has 4.4.2 on it and i wanna flash viperrom 3.2.1 but it requires androids 4.4.4 software. im S-ON, 3.16 Bootloader with 1.58.502.1 Software number. Baseband Version is 1.16.21331931.LA11G_20.31A.4145.02L. im just looking to Update from 4.4.2 to 4.4.4 but i cant seem to find out how. Any help would be great.
Perfect.
Unlock your bootlooader if you haven't already, fastboot flash recovery (TWRP/PHILZ),root using the chosen custom recovery,make a backup before or after root.
Go here http://theroot.ninja/ for Sunshine
S-OFF cause that's what your going to need to update as far as 4.4.4
Orrrr just wait a few days for the ATT 4.4.4 build to be released (ETA 29th) and then youll have 4.4.4 without having to do anything.
Wonders_Never_Cease said:
Orrrr just wait a few days for the ATT 4.4.4 build to be released (ETA 29th) and then youll have 4.4.4 without having to do anything.
Click to expand...
Click to collapse
That's a better idea for sure.
I haven't noticed if Sunshine has an update that works with 4.4.4 yet.
Are you S-OFF ?
What are the advantages/disadvantages of S-OFF so the OP knows what he might be missing.
Do you know when the Sunshine update will be?
Yup,no [email protected],[email protected],there are plenty of posts about advantages and disadvantages...my point of view is simple,it is not needed for the novice,ive seen too many mess things due to lack of knowledge. My usage of it is for switching between att and developer ROM's to get latest updates. Outside of that I dont mess with conversions,to risky for a 6-700 device. My advice is stick to htc dev unlocked bootloader and wait for official update.
jball said:
That's a better idea for sure.
I haven't noticed if Sunshine has an update that works with 4.4.4 yet.
Are you S-OFF ?
What are the advantages/disadvantages of S-OFF so the OP knows what he might be missing.
Do you know when the Sunshine update will be?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Yup,no [email protected],[email protected],there are plenty of posts about advantages and disadvantages...my point of view is simple,it is not needed for the novice,ive seen too many mess things due to lack of knowledge. My usage of it is for switching between att and developer ROM's to get latest updates. Outside of that I dont mess with conversions,to risky for a 6-700 device. My advice is stick to htc dev unlocked bootloader and wait for official update.
Click to expand...
Click to collapse
Cool thank you
Im not S-OFF but hell ill wait for the 29th to roll around and see if i have an update. Can you link me to the info stating its around the 29th?
darkninja908 said:
Im not S-OFF but hell ill wait for the 29th to roll around and see if i have an update. Can you link me to the info stating its around the 29th?
Click to expand...
Click to collapse
I didn't Google for to long but I haven't found concrete links that state the exact date .how many times have we been promised a date and watch it pass by anyways.
May I ask if you've modified any other device before this one?
I'm not trying to push,but S-OFF might be in your future and will not halt an OTA from installing.
The version your on is easily exploitable using "Sunshine" unless you take the soon to be 4.4.4 update.
Nobody knows when Sunshine will have an update even with the team working on it as we speak.
Wont be much on Google @date,came from somewhere else. And nothing is ever "concrete" with software,especially with carrier branded software.
jball said:
I didn't Google for to long but I haven't found concrete links that state the exact date .how many times have we been promised a date and watch it pass by anyways.
May I ask if you've modified any other device before this one?
I'm not trying to push,but S-OFF might be in your future and will not halt an OTA from installing.
The version your on is easily exploitable using "Sunshine" unless you take the soon to be 4.4.4 update.
Nobody knows when Sunshine will have an update even with the team working on it as we speak.
Click to expand...
Click to collapse
jball said:
I didn't Google for to long but I haven't found concrete links that state the exact date .how many times have we been promised a date and watch it pass by anyways.
May I ask if you've modified any other device before this one?
I'm not trying to push,but S-OFF might be in your future and will not halt an OTA from installing.
The version your on is easily exploitable using "Sunshine" unless you take the soon to be 4.4.4 update.
Nobody knows when Sunshine will have an update even with the team working on it as we speak.
Click to expand...
Click to collapse
I have Rooted, and flashed multiple ROMS to my old M7 before. Nothing crazy.
I as well have the same build, unlocked bootloader, flashed custom recovery. Will I have to return to stock recovery using 1.58.502.1 RUU and to get the OTA update to 4.4.4??
I'm trying to get the latest Android Revolution ROM for 4.4.4 but realized I was in a bit of a pickle. I'd like to take the path of least resistance on this one - any advice would be super appreciated. Thanks!
pmoser16 said:
I as well have the same build, unlocked bootloader, flashed custom recovery. Will I have to return to stock recovery using 1.58.502.1 RUU and to get the OTA update to 4.4.4??
I'm trying to get the latest Android Revolution ROM for 4.4.4 but realized I was in a bit of a pickle. I'd like to take the path of least resistance on this one - any advice would be super appreciated. Thanks!
Click to expand...
Click to collapse
I'd say wait till tomorrow to see if an OTA update will roll out.
Or if you just can't wait for the ability to flash what you desire than I would go S-OFF and flash a non At&t firmware that you need to allow a smooth function of mentioned ROM.
Im restoring back to default AT&T ROM and such and will post weather the update has been pushed or not. i sure hope it has
**Update** Still no update, i got the " Current Software is up to date, You may check again in 23 Hours 59 Mintues.
darkninja908 said:
Im restoring back to default AT&T ROM and such and will post weather the update has been pushed or not. i sure hope it has
**Update** Still no update, i got the " Current Software is up to date, You may check again in 23 Hours 59 Mintues.
Click to expand...
Click to collapse
You can check as many times as you like by setting your time manually ahead and your phone/device won't know the difference.
Check as many times as you like but it will remain the same,you should get a notification when it's time
So if you don't have s-off you can't update to 4.44 Sense ROMS with AT&T? I'm on Slim Rom and sound quality stinks. I want the new Android Revolution but i've read wi-fi and such doesn't work. Clarification plz?
war eagle said:
So if you don't have s-off you can't update to 4.44 Sense ROMS with AT&T? I'm on Slim Rom and sound quality stinks. I want the new Android Revolution but i've read wi-fi and such doesn't work. Clarification plz?
Click to expand...
Click to collapse
Correct .
S-OFF allows you to change your CID witch will allow you to ruu Dev Edition 4.4.4 so everything runs smoothly
I've not looked on this thread in a while. I am S-off and unlocked and my cid is 11111111 but I have never updated firmware so that I can run a 4.4.4 rom. Is it correct that I flash a RUU (guess it's not called flashing when it comes to a RUU). How do I know which RUU to post - I found this one here: http://forum.xda-developers.com/showthread.php?t=2757462 (http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe)
Will I loose root or anything (other than wiping my data) when running the ruu.
jball said:
Correct .
S-OFF allows you to change your CID witch will allow you to ruu Dev Edition 4.4.4 so everything runs smoothly
Click to expand...
Click to collapse
karatche said:
I've not looked on this thread in a while. I am S-off and unlocked and my cid is 11111111 but I have never updated firmware so that I can run a 4.4.4 rom. Is it correct that I flash a RUU (guess it's not called flashing when it comes to a RUU). How do I know which RUU to post - I found this one here: http://forum.xda-developers.com/showthread.php?t=2757462 (http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe)
Will I loose root or anything (other than wiping my data) when running the ruu.
Click to expand...
Click to collapse
I'll just say that if it's a stock ruu than it's most likely without root and it will wipe as if it came out of the box.if its a full ruu than it will come with the updated firmware as well witch should allow you to flash 4.4.4 Roms and still run smoothly.
What I did around 5:00am this morning was restore my Dev edition backup I had along with the stock recovery so I could take the Dev edition lollipop official update and now I have lollipop firmware to use with my stock GPE 5.0.1 lollipop ROM/backup .
Sweetness
karatche said:
I've not looked on this thread in a while. I am S-off and unlocked and my cid is 11111111 but I have never updated firmware so that I can run a 4.4.4 rom. Is it correct that I flash a RUU (guess it's not called flashing when it comes to a RUU). How do I know which RUU to post - I found this one here: http://forum.xda-developers.com/showthread.php?t=2757462 (http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe)
Will I loose root or anything (other than wiping my data) when running the ruu.
Click to expand...
Click to collapse
Yes, running/flashing the 4.4.4 Dev Edition RUU will update you to that appropriate firmware. But, what you linked is not Dev Edition, its a stock AT&T RUU. And its not 4.4.4 either, its 4.4.2, which is probably where you already are.
What you want is the 3.28.1540 RUU linked here: http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
RUU will wipe the phone, install stock ROM (meaning root will be lost) and stock recovery.
But I also think its overkill to run an RUU just to update firmware, if that is the intent. My suggestion is to just run the firmware linked in the following post (which also has great instructions for doing so): http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
The above method shouldn't overwrite the current ROM and user data. But backup anything important before flashing firmware, just in case.
Side note, "flash" is a fairly generic term, and as the RUU flashes stock ROM among other things, the term "flash" is appropriate IMO.
So can I just load the firmware file and flash thru fastboot? Is it This one?
3.28.1540.5 Firmware only unmodified (Latest 4.4.4 Update,S-OFF REQUIRED)
http://goo.gl/tyhRRZ
redpoint73 said:
Yes, running/flashing the 4.4.4 Dev Edition RUU will update you to that appropriate firmware. But, what you linked is not Dev Edition, its a stock AT&T RUU. And its not 4.4.4 either, its 4.4.2, which is probably where you already are.
What you want is the 3.28.1540 RUU linked here: http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
RUU will wipe the phone, install stock ROM (meaning root will be lost) and stock recovery.
But I also think its overkill to run an RUU just to update firmware, if that is the intent. My suggestion is to just run the firmware linked in the following post (which also has great instructions for doing so): http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
The above method shouldn't overwrite the current ROM and user data. But backup anything important before flashing firmware, just in case.
Side note, "flash" is a fairly generic term, and as the RUU flashes stock ROM among other things, the term "flash" is appropriate IMO.
Click to expand...
Click to collapse