Related
It seems like the only way to S-Off Vivid required some wire trick. I never done something like that b4...
What do I miss if I leave it S-ON? I already unlock bootloader, custom recovery and rooted.
Thanks anyone for answering.
Apart from being able to flash radios (to the best of my knowledge there aren't any custom/better ones for the vivid, yet), there are kernals being built that require s-off. And with s-off you can flash roms/images that are unsigned to the phone, regardless of what carrier or region you're in; other words, you can flash whatever Rom you like so its imperative that everything about the Rom you're installing is read and understood to avoid confusion and ultimately, a bricked device... That's pretty much it in a nutshell. I hope that cleared it up for you
Sent from my HTC Velocity 4G using xda premium
g33mt4z said:
Apart from being able to flash radios (to the best of my knowledge there aren't any custom/better ones for the vivid, yet), there are kernals being built that require s-off. And with s-off you can flash roms/images that are unsigned to the phone, regardless of what carrier or region you're in; other words, you can flash whatever Rom you like so its imperative that everything about the Rom you're installing is read and understood to avoid confusion and ultimately, a bricked device... That's pretty much it in a nutshell. I hope that cleared it up for you
Sent from my HTC Velocity 4G using xda premium
Click to expand...
Click to collapse
First part about radios is wrong. You need an ENG HBOOT to do it, which we still don't have. Sure, S-Off lets us flash custom HBOOTs, but we're still not there yet.
Second part about kernels requiring it is also wrong. You can always flash kernels as a fastboot flash boot boot.img, then CWM the modules in. It's always been the case, and is not changing with AOSP or any of that stuff. AOSP doesn't require S-Off, neither does Sense 4, neither does any preexisting nor future kernel.
Third part about unsigned ROMs is partially wrong. You can flash other regions' RUU updates with the superCID. Still doesn't let you do custom ROMs themselves; for that, the unlocked bootloader process is still valid, and you will need some form of recovery (CWM, WCX, TWRP, etc).
Aus_Azn said:
First part about radios is wrong. You need an ENG HBOOT to do it, which we still don't have. Sure, S-Off lets us flash custom HBOOTs, but we're still not there yet.
Second part about kernels requiring it is also wrong. You can always flash kernels as a fastboot flash boot boot.img, then CWM the modules in. It's always been the case, and is not changing with AOSP or any of that stuff. AOSP doesn't require S-Off, neither does Sense 4, neither does any preexisting nor future kernel.
Third part about unsigned ROMs is partially wrong. You can flash other regions' RUU updates with the superCID. Still doesn't let you do custom ROMs themselves; for that, the unlocked bootloader process is still valid, and you will need some form of recovery (CWM, WCX, TWRP, etc).
Click to expand...
Click to collapse
Actually my kernel does require s-off now if you want to keep it up to date. If you are fine using a less feature rich and possibly unstable s-on version of it then that's fine
Sent from my HTC PH39100 using xda premium
Thank you everyone for replying.
So this is what I get:
with S-OFF,
1) I can flash hboot (boot.img)
2) Within recovery (CWM or alike), I can flash Custom ROM zip that has build-in kernel
Is that correct?
BTW, is there SuperCID for Vivid yet?
Thanks again,
RayYung said:
Thank you everyone for replying.
So this is what I get:
with S-OFF,
1) I can flash hboot (boot.img)
2) Within recovery (CWM or alike), I can flash Custom ROM zip that has build-in kernel
Is that correct?
BTW, is there SuperCID for Vivid yet?
Thanks again,
Click to expand...
Click to collapse
1. HBOOT is not a boot.img, it's an .nb0 file (the bootloader itself). boot.img is a kernel.
2. Yes.
3. Yes, it's 11111111 like most other HTC devices.
Thanks Aus_Azn,
I guess I mixed up hboot and kernel....
I know 11111111 is THE SuperCID for all device but is there a SuperCID hack for Vivid yet?
Hello, Iam noob in rooting and there is sooo much information about that, so my head goes burn, my simple question is only - can you recommend me the most easiest way to root my Incredible S? I want to install new ROM. Version Hboot 2.00, android 2.3.5 and never S-OFF, rooted. I have to downgrade HBOOT? Thank you so much
Oh look it's first sticky on the forum! Just a simple read through the first page of the forum might help just sayin'.
Anyways, this seems to be the easiest way to root...it's definitely easy to understand even if you have few to minimum understanding of rooting and flashing.
Incredible2011 said:
Oh look it's first sticky on the forum! Just a simple read through the first page of the forum might help just sayin'.
Anyways, this seems to be the easiest way to root...it's definitely easy to understand even if you have few to minimum understanding of rooting and flashing.
Click to expand...
Click to collapse
I have problem and I hope you can help me my question:My phone is s off,but I have never use custom recovery and custom rom and I have never do root,my version is 2.3.5 hboot:2.0000 I want to root my phone but I dont want to do that with unlocked method.How can I root my phone,I say again My phone is already s off.and I wantto use this method.
hasi56 said:
I have problem and I hope you can help me my question:My phone is s off,but I have never use custom recovery and custom rom and I have never do root,my version is 2.3.5 hboot:2.0000 I want to root my phone but I dont want to do that with unlocked method.How can I root my phone,I say again My phone is already s off.and I wantto use this method.
Click to expand...
Click to collapse
Since you are already S-OFF, then you should be able to flash ClockworkMod recovery in FASTBOOT USB mode. Once you have CWM installed, you can make a 'nandroid' backup of your current ROM, apps and settings. Then you can flash the latest and greatest version of su-3.0.x.zip to gain root.
This will leave your current ROM, apps and settings intact.
tpbklake said:
Since you are already S-OFF, then you should be able to flash ClockworkMod recovery in FASTBOOT USB mode. Once you have CWM installed, you can make a 'nandroid' backup of your current ROM, apps and settings. Then you can flash the latest and greatest version of su-3.0.x.zip to gain root.
This will leave your current ROM, apps and settings intact.
Click to expand...
Click to collapse
Thank you,so I can root my phone with any expression(s off method) even though my phone h boot version is 2.ooooo(but my phone is already s off) am I right? and I dont understand,is there new root old root advantageous root,I havent heard that,I knew rooting is fixed
??
hasi56 said:
Thank you,so I can root my phone with any expression(s off method) even though my phone h boot version is 2.ooooo(but my phone is already s off) am I right? and I dont understand,is there new root old root advantageous root,I havent heard that,I knew rooting is fixed
Click to expand...
Click to collapse
Since you have permanent S-OFF, you don't have to worry about whether to unlock HBOOT 2.00.0000 or downgrading to run Revolutionary, etc.
You should be able to flash ClockworkMod recovery, you could flash HBOOT 1.13, flash a new radio, etc.
You just need to get familiar with using FASTBOOT USB mode and all of the options that fastboot.exe can do.
I am speaking from experience. I have a permanent S-OFF IncS and even after I run the Android 2.3.5/Sense 3.0 RUU and it upgraded my HBOOT to version 2.00.0000, I was able to flash ClockworkMod recovery and install su-3.0.x.zip and root the ROM. I have also since reflashed back to HBOOT 1.13.
tpbklake said:
Since you have permanent S-OFF, you don't have to worry about whether to unlock HBOOT 2.00.0000 or downgrading to run Revolutionary, etc.
You should be able to flash ClockworkMod recovery, you could flash HBOOT 1.13, flash a new radio, etc.
You just need to get familiar with using FASTBOOT USB mode and all of the options that fastboot.exe can do.
I am speaking from experience. I have a permanent S-OFF IncS and even after I run the Android 2.3.5/Sense 3.0 RUU and it upgraded my HBOOT to version 2.00.0000, I was able to flash ClockworkMod recovery and install su-3.0.x.zip and root the ROM. I have also since reflashed back to HBOOT 1.13.
Click to expand...
Click to collapse
I understanda a lot of thingss Im grateful to you,but you said you could flash hboot 1.13 what is our purpose by doing this processing?
hasi56 said:
I understanda a lot of thingss Im grateful to you,but you said you could flash hboot 1.13 what is our purpose by doing this processing?
Click to expand...
Click to collapse
With HBOOT 1.13, ClockworkMod recovery is able to flash a custom ROM in one step. With HBOOT 2.00.0000, after you flash a custom ROM in ClockworkMod, you manually have to extract and flash the boot.img file in the custom ROM's zip file. In other words it is easier to flash custom ROM's with CWM and HBOOT 1.13 than it is with HBOOT 2.00
tpbklake said:
With HBOOT 1.13, ClockworkMod recovery is able to flash a custom ROM in one step. With HBOOT 2.00.0000, after you flash a custom ROM in ClockworkMod, you manually have to extract and flash the boot.img file in the custom ROM's zip file. In other words it is easier to flash custom ROM's with CWM and HBOOT 1.13 than it is with HBOOT 2.00
Click to expand...
Click to collapse
Thank you very very much,apolgize me i have one more question i want ti root my cell phone after ics.can i do same thing your root Expression after ics ?
hasi56 said:
Thank you very very much,apolgize me i have one more question i want ti root my cell phone after ics.can i do same thing your root Expression after ics ?
Click to expand...
Click to collapse
The only option you have right now for ICS is to run a custom ROM from the Development section and all of those are already rooted.
If you are talking about the official ICS OTA/ROM from HTC, we will have to wait and see if it will be rootable or not.
Once again since you have a permanent S-OFF on your phone, you shouldn't have to worry about. If you install the official ICS ROM and you lose root, you should be able to reflash CWM and then install su-3.0.x.zip to gain root.
tpbklake said:
The only option you have right now for ICS is to run a custom ROM from the Development section and all of those are already rooted.
If you are talking about the official ICS OTA/ROM from HTC, we will have to wait and see if it will be rootable or not.
Once again since you have a permanent S-OFF on your phone, you shouldn't have to worry about. If you install the official ICS ROM and you lose root, you should be able to reflash CWM and then install su-3.0.x.zip to gain root.
Click to expand...
Click to collapse
Thank you very very very much,you helped me a lot,
My phone is htc inc s,i use original rom,but i did root i bought a new sensation xe's beats audio headphones and i want tk use beats mod in my phone when i use headphone like sensation xe,is this imposibble i hop i can tell my question
hasi56 said:
My phone is s off,but I have never use custom recovery and custom rom and I have never do root,my version is 2.3.5 hboot:2.0000
Click to expand...
Click to collapse
Stupid question, how did you achieve s-off with hboot:2.0000? As I understand, Revolutionary doesn't yet support hboot:2.0000?
alexbk66 said:
Stupid question, how did you achieve s-off with hboot:2.0000? As I understand, Revolutionary doesn't yet support hboot:2.0000?
Click to expand...
Click to collapse
No a stupid question because the answer isn't very obvious, but the is a sticky post in the General forum that describes a process where you can downgrade the ROM and HBOOT to a version that Revolutionary does support.
Check here:
http://forum.xda-developers.com/showthread.php?t=1373697
or here:
http://forum.xda-developers.com/showthread.php?t=1705913
Is it necessary to s-off for installing custom roms? is it more safe to install the roms and kernels like we do in one-x?
thx
kami2k said:
Is it necessary to s-off for installing custom roms? is it more safe to install the roms and kernels like we do in one-x?
thx
Click to expand...
Click to collapse
no its not necessary to S-OFF for installing custom ROMs, all you need is unlocked bootloader and custom recovery (TWRP/CWM):good:
and yes its totally safe to install roms and kernels without PC unlike on One X :laugh:
just flash 'em from recovery
The only benefit to S-OFF is you have a get out to get back to stock if you need to as you can flash one of the early RUUs that leaked. If HTC released RUUs to the public there would be no need to have S-OFF unless changing the splash screen is important to you
EddyOS said:
The only benefit to S-OFF is you have a get out to get back to stock if you need to as you can flash one of the early RUUs that leaked. If HTC released RUUs to the public there would be no need to have S-OFF unless changing the splash screen is important to you
Click to expand...
Click to collapse
S-OFF is needed I think if you want to change HBOOT or downgrade OS versions for ex from 4.2.2 to 4.2.1, but how about correct CID and S-ON again?
EddyOS said:
The only benefit to S-OFF is you have a get out to get back to stock if you need to as you can flash one of the early RUUs that leaked. If HTC released RUUs to the public there would be no need to have S-OFF unless changing the splash screen is important to you
Click to expand...
Click to collapse
So without S-OFF, I can't go back to stock ROM after installing custom ROM, right?
What about before installing a custom ROM, I create a backup with TWRP, can I use this backup to return to stock?
htcm7 said:
So without S-OFF, I can't go back to stock ROM after installing custom ROM, right?
What about before installing a custom ROM, I create a backup with TWRP, can I use this backup to return to stock?
Click to expand...
Click to collapse
Yes. You would only need s-off if an ruu isn't available for your cid.
Sent from my HTC One using XDA Premium 4 mobile app
If you have to ask then no....
S-OFF often introduces more problems then it's worth, especially when your not very experienced. It is a great tool to fix stuff when you really screw up, but it also allows a lot more control then most people can handle. If you so S-OFF then just remember to never S-ON unless you are already back 100% stock.
Sent from my HTC One using Tapatalk 4
Anyway if you are on the HBOOT 1.54 you wont be able to S-OFF...
htcm7 said:
So without S-OFF, I can't go back to stock ROM after installing custom ROM, right?
What about before installing a custom ROM, I create a backup with TWRP, can I use this backup to return to stock?
Click to expand...
Click to collapse
You will be able to go back to stock if you can get hold of the original recovery as well as using your backup (for the love of God make a backup!!!). S-OFF means you can use one of the rare publicly-leaked RUUs to get back to stock
EddyOS said:
You will be able to go back to stock if you can get hold of the original recovery as well as using your backup (for the love of God make a backup!!!). S-OFF means you can use one of the rare publicly-leaked RUUs to get back to stock
Click to expand...
Click to collapse
Sorry, not sure if i understand your information correctly.
What do you mean by 'get hold of the original recovery'?
If I backup stock ROM using TWRP and when I want to go back to stock, can I just restore my backup without a use of RUU?
htcm7 said:
Sorry, not sure if i understand your information correctly.
What do you mean by 'get hold of the original recovery'?
If I backup stock ROM using TWRP and when I want to go back to stock, can I just restore my backup without a use of RUU?
Click to expand...
Click to collapse
Yes but you wouldn't be able to install OTA updates without the original recovery image
so only if u want ruu u do s-off otherwise no reason......
S-OFF allows you to flash an RUU earlier than your current build, e.g. I can flash the 1.28.401.7 on top of my current 2.24.401.8 whereas without S-OFF I wouldn't be able to
but if a new rom came with new built u can install that, who needs s-off then?
As I originally said, you don't need S-OFF if you have no need to go back to stock. If you need to send the phone to HTC for repair, having S-OFF means you can get the phone back to 100% stock and showing 'locked' as opposed to 'relocked' so they won't know you've ever done anything to the phone.
Otherwise you're taking a chance on HTC refusing the repair
Hi everyone,
I recently switched from my Galaxy Nexus to the HTC One. Coming from a nexus device, the general rooting procedure seems to be a bit more complicated on the one. After browsing the web for a few hours, a couple of things are still not completely clear and I would appreciate any help as I do not intend to break a recently bought 550€ device So thanks in advance.
Rooting, flashing roms and kernels, and installing a custom recovery works after unlocking the device with htcdev.com. I do not need S-Off for those things. Is this correct?
When it comes to returning the device to stock for let's say, a warranty-related issue, is this also possible with S-On? If this is the case, how would I do that as I mostly found guides to return to stock that require S-Off? I'm currently on hboot 1.54 so S-off is not an option right now.
Also, if I lock the bootloader again (which should work with fastboot oem lock I assume?) I read somewhere that it will say Relocked instead of Locked. Out of experience, would this be a problem if I need to send the device in?
Tl;dr: Rooting, flashing roms and kernels, installing a recovery is possible after unlocking the bootloader with htcdev.com. Can I also return the device to stock if I need to send it in with S-On or does that require S-Off?
Thank you.
Any help is appreciated.
All the rooting, etc. can be done with just an unlocked bootloader. It's the downgrading that required S-OFF
EddyOS said:
All the rooting, etc. can be done with just an unlocked bootloader. It's the downgrading that required S-OFF
Click to expand...
Click to collapse
That's quite pleasant news, thank you. Can I also return it to stock for warranty-related issues with S-on? And what do you mean with downgrading and why would I do that?
As there is no RUU available for anything over 1.29.401.16, being S-OFF gives the option of using an older RUU to get the phone back to 100% stock and then you can get the OTA updates to get to the latest version again. If you're S-ON you can only restore a nandroid backup (which I would say a million times to do before flashing a new ROM), restore the stock recovery and then relock the device
b0ld said:
That's quite pleasant news, thank you. Can I also return it to stock for warranty-related issues with S-on? And what do you mean with downgrading and why would I do that?
Click to expand...
Click to collapse
Well first thing you should do when you unlock your bootloader is do a nandroid backup of your stock rom. that way you can flash it back if you ever want to return to stock; so you won't need to look endlessly for an RUU or other backup, which may or may not exist.
However, once you do unlock and install custom recovery your bootloader will say:
*** UNLOCKED ***
*** TAMPERED ***
and if you re-lock your bootloader, it will only go back to *** RELOCKED ***, it will never go back to *** LOCKED *** (unless you're S-Off with revone)
I'm not sure about the TAMPERED, as there are some conflicting reports, some say TAMPERED will go away once you flash stock recovery, and others say it will not go away.
So for warranty issues it really depends on your country and/or repair center, some will "overlook" the unlocked/relocked status if it's a hardware defect and either repair or send you a new one, but then again there are some that will blame the fault on you, saying that unlocking and flashing custom roms was the cause of the malfunction.
We don't have warranty where I live so I can't really help there. You could post your carrier and country, and see what other people have experienced.
Thank you all, this has been really helpful. What happens in case I brick my device while having S-On? Would you say that S-off is really important or doesn't it really matter at all if I don't care for OTA updates? And can I obtain S-Off if I am already rooted and on a custom Rom if it should ever be available for hboot 1.54?
I'll post my information as you suggested.
Country: Austria
Carrier: 3, but I don't think that matters as I bought the device unlocked.
b0ld said:
Thank you all, this has been really helpful. What happens in case I brick my device while having S-On? Would you say that S-off is really important or doesn't it really matter at all if I don't care for OTA updates? And can I obtain S-Off if I am already rooted and on a custom Rom if it should ever be available for hboot 1.54?
I'll post my information as you suggested.
Country: Austria
Carrier: 3, but I don't think that matters as I bought the device unlocked.
Click to expand...
Click to collapse
With S-On you can do pretty much everything (custom ROMs, even Radios). The only thing you won't be able to flash is the firmware. You would either need to find a signed firmware for your CID and MID, or if an OTA comes in your country (which includes newer firmware), you would have to flash back to stock + stock recovery, relock your bootloader, accept the OTA then unlock again and restore whatever custom ROM you were using. (not that difficult)
Anyway, from what I've seen so far, most ROMs are not being dependent on any specific firmware version. Are you already on 2.24 firmware? I think that's the currently official version.
And with S-On, it's very hard to brick your device as you can't mess with the hboot which is the main reason for bricks.
Thanks for the quick reply. In this thread it is stated that after flashing s nandroid backup without s-off it might result in problems like the touchscreen not working. (1st post) http://forum.xda-developers.com/showthread.php?t=2358738
Is this always the case?
That is if you flash a 4.1.2-based nandroid when you have the 4.2.2 FW. If you flash your own one (which is why you should ALWAYS make a backup before doing anything else) you should have no issues
What if I flash a 4.3 custom rim and decide to flash my current 4.2.2 stock nandroid?
That'll be fine as you won't be on the 4.3 FW (as you can't flash FW when S-ON)
b0ld said:
What if I flash a 4.3 custom rim and decide to flash my current 4.2.2 stock nandroid?
Click to expand...
Click to collapse
Firmware version is not tied to ROM version, even if you run a 4.3 ROM, your firmware will still be 2.24 (from 4.2.2). And since you're S-On you can't flash any unsigned firmware. So no worries.
EDIT: EddyOS was faster
That's good news.
Why would I need a newer firmware then (probably noob question)? Would it also be possible to flash the official htc stock 4.3 rom with sense once it's released? And is it possible to get s-off once the bootloader is unlocked etc.?
If i understand correctly, even with s-on I can do pretty much anything, and if I should screw up something, flashing my nandroid backup will resolve it?
b0ld said:
That's good news.
Why would I need a newer firmware then (probably noob question)? Would it also be possible to flash the official htc stock 4.3 rom with sense once it's released? And is it possible to get s-off once the bootloader is unlocked etc.?
If i understand correctly, even with s-on I can do pretty much anything, and if I should screw up something, flashing my nandroid backup will resolve it?
Click to expand...
Click to collapse
1- Newer firmware can (should ) have improvements (performance, stability, battery) over previous ones, e.g. the firmware 2.24 showed significant improvement of the touch drivers, but after 2.24 firmware I haven't seen any noticeable remarks from other threads.
2- Once the official 4.3 stock OTA rolls out, you will be able to get it after you restore your phone to stock (ie stock rom from your backup + stock recovery + relocked)
3- You won't be able to get S-Off (even with unlocked bootloader) until a new exploit is found (if ever )
4- with s-on you can flash back your original backup, or any custom rom, kernel, radio. the only thing is your phone will show ***UNLOCKED***/***RELOCKED*** and ***TAMPERED*** in the bootloader.
Thanks again, very informative! One (hopefully) last question (for now), do I have to flash the boot.img seperately when flashing a new rom on the PC with s-on or can I jhst flash the .zip, just like on the nexus?
Boot.img flashes with the ROM as a Nexus does, only the One X needed to flash the boot.img manually after a ROM
b0ld said:
Thanks again, very informative! One (hopefully) last question (for now), do I have to flash the boot.img seperately when flashing a new rom on the PC with s-on or can I jhst flash the .zip, just like on the nexus?
Click to expand...
Click to collapse
boot.img usually comes in the zip of the ROM, no need to flash separately.
EDIT: EddyOS does it again :laugh:
So, long story short: The only thing that's different from the nexus is that the bootloader will say "relocked" or "tampered". I can still receive OTAs as soon as I flash the nandroid backup I made after flashing the custom recovery. I can still switch between 4.2 and 4.3 ROMs if I'd like to. I can basically do anything with S-On besides modifying system files (which I do not intend to). I could even receive the next firmware updates (the ones after the current 2.24) if I restore my nandroid, restore the original recovery image, and relock the bootloader. There are no "real" downsides for me if I stay S-On as I can return everything to stock anyway. Is this correct?
b0ld said:
So, long story short: The only thing that's different from the nexus is that the bootloader will say "relocked" or "tampered". I can still receive OTAs as soon as I flash the nandroid backup I made after flashing the custom recovery. I can still switch between 4.2 and 4.3 ROMs if I'd like to. I can basically do anything with S-On besides modifying system files (which I do not intend to). I could even receive the next firmware updates (the ones after the current 2.24) if I restore my nandroid, restore the original recovery image, and relock the bootloader. There are no "real" downsides for me if I stay S-On as I can return everything to stock anyway. Is this correct?
Click to expand...
Click to collapse
Yep sounds right :good:
If you had S-Off then you could remove the tampered and unlocked/relocked signs, and you could mess around (upgrade & downgrade) unsigned firmwares.
With S-On you have to stick with the official OTAs.
nkk71 said:
If you had S-Off then you could remove the tampered and unlocked/relocked signs, (...)
Click to expand...
Click to collapse
If there should ever be a method of getting S-Off with hboot 1.54, it makes no difference if I root it right now and install a custom rom, as I can relock and restore everything again. Right?
I have S-on, custom recovery and unlocked boot loader on my m7. I changed providers to T Mobile from ATT. I would like to get the WiFi calling features, etc but so far have been unable to flash a T Mobile RUU. I assume because the CID is an AT&T one. I have attempted to S-off the device (1.56 boot loader) in order to change the CID, it failed. Any advice for getting the device onto the stock t mobile Rom?
dave328 said:
I have S-on, custom recovery and unlocked boot loader on my m7. I changed providers to T Mobile from ATT. I would like to get the WiFi calling features, etc but so far have been unable to flash a T Mobile RUU. I assume because the CID is an AT&T one. I have attempted to S-off the device (1.56 boot loader) in order to change the CID, it failed. Any advice for getting the device onto the stock t mobile Rom?
Click to expand...
Click to collapse
Have you tried rumrunner and firewater they are supposed to work on 1.5X hboot. Read through both of their threads to see what others have done to achieve S-Off. Without S-Off, I don't think you will be able to change.
majmoz said:
Have you tried rumrunner and firewater they are supposed to work on 1.5X hboot. Read through both of their threads to see what others have done to achieve S-Off. Without S-Off, I don't think you will be able to change.
Click to expand...
Click to collapse
Thanks I have read both and tried both methods without any luck. I installed the viperrom but still don't see any options for WiFi calling. Maybe that is CID dependent as well
dave328 said:
Thanks I have read both and tried both methods without any luck. I installed the viperrom but still don't see any options for WiFi calling. Maybe that is CID dependent as well
Click to expand...
Click to collapse
I don't think WiFi-calling has been implemented in Sense 6 custom roms except for stock T-Mobile. AHRD has v36.1 and SkyDragon has v20 which is KK with Sense 5.5. I had a thought, if you could return to stock AT&T using an older RUU which would have a lower hboot. Then you could try to get S-Off. It is the round about way to do it but it might work. One note the RUU you are going to flash/run has to have an hboot equal to or lower than its hboot. nkk71's SuperGUIDE to returning 100% back to stock has a lot of information and links on how to accomplish it.
majmoz said:
I don't think WiFi-calling has been implemented in Sense 6 custom roms except for stock T-Mobile. AHRD has v36.1 and SkyDragon has v20 which is KK with Sense 5.5. I had a thought, if you could return to stock AT&T using an older RUU which would have a lower hboot. Then you could try to get S-Off. It is the round about way to do it but it might work. One note the RUU you are going to flash/run has to have an hboot equal to or lower than its hboot. nkk71's SuperGUIDE to returning 100% back to stock has a lot of information and links on how to accomplish it.
Click to expand...
Click to collapse
That is a great idea. I had semi-attempted that but did not put as much effort into it as I should have. I will definitely try that. But I am wary that to downgrade I will still need super CID and s-off.
majmoz said:
I had a thought, if you could return to stock AT&T using an older RUU which would have a lower hboot. Then you could try to get S-Off.
Click to expand...
Click to collapse
@dave328
Well, downgrading require S-OFF
so you can't downgrade to achieve s-off
http://forum.xda-developers.com/showpost.php?p=49832723&postcount=388
with S-ON you can only flash signed firmware and ruu with same or higher version
Sorry I lead you wrong, @alray is correct. Here is something I found in @nkk71 thread under "Not so FAQ #2". It explains a lot.
majmoz said:
I don't think WiFi-calling has been implemented in Sense 6 custom roms except for stock T-Mobile.
Click to expand...
Click to collapse
InsertCoin has working T-mobile wifi calling on sense 6...
at least their 2.xx versions, I have not tested 3.0 yet, but I read it's in there.
mike-y said:
InsertCoin has working T-mobile wifi calling on sense 6...
at least their 2.xx versions, I have not tested 3.0 yet, but I read it's in there.
Click to expand...
Click to collapse
I will look into that thank you.
Could I do a nandroid restore of a T-mobile Rom that had earlier h-boot? Or at least to get onto stock t-mobile software with the nandroid?
dave328 said:
I will look into that thank you.
Could I do a nandroid restore of a T-mobile Rom that had earlier h-boot? Or at least to get onto stock t-mobile software with the nandroid?
Click to expand...
Click to collapse
once you have a custom recovery (like TWRP), you can make a nandroid of your stock rom. Then you can try out any of the other roms of your choosing and aways restore your nandroid if you don't like them.
You may be able to also restore an old backup, but if it was made with a different recovery, it doesn't always work.
mike-y said:
once you have a custom recovery (like TWRP), you can make a nandroid of your stock rom. Then you can try out any of the other roms of your choosing and aways restore your nandroid if you don't like them.
You may be able to also restore an old backup, but if it was made with a different recovery, it doesn't always work.
Click to expand...
Click to collapse
Thanks. I would need to find a stock T-Mobile HTC One Rom made with TWRP or CWM. I can switch recoveries easily enough. Maybe that could work. Any idea where I could find a nandroid zip file like that?
check the development section of the forum. there are a couple of threads that have stock roms in .zip format to flash in TWRP or CWM
for example:
http://forum.xda-developers.com/showthread.php?t=2353812
http://forum.xda-developers.com/showthread.php?t=2499452