Hi!
I've spent a few hours researching these topics but I still feel a bit unstable. If I get it right, you can use the HTCdev method to unlock your bootloader safely, but doing so will make you unable to relock it flawlessly. Using the Sunshine method gives you an opportunity to S-off while keeping the bootloader locked.
1.) Using the Sunshine S-off LOCKED method, can you "re-S-on" to make your device look factory new? (In other words: can you revert the changes completely?)
2.) I've read that S-off-ing is only required to install firmwares and for other "high-level" purposes. Could you please tell me a few situations / examples where S-off-ing would come handy (and an unlocked bootloader wouldn't be enough)?
3.) How can you install software updates while being in "S-off LOCKED" or just simply bootloader unlocked mode?
4.) Do you think Nougat will make any differences regarding the Sunshine method?
I'm planning to do one of the 2 methods after the official EU release of Android N.
Thank you in advance!
1-Yes. But s-on is not recommended unless you really really need it.
2-For example,I'm s-off unlocked.Changed my Europe device's Cid and Mid to US Unlocked version,flashed latest Nougat RUU.exe.Wanted to go back to Viper 3.5 MM,Flashed US unlocked MM RUU.exe,Changed mid cid,Flashed a stock MM European MM 1.90 rom,flashed Viper,upgraded firmware to 1.95 through fastboot.And that's it.I was back in the beginning.2 days later,saw the root came out,changed mid-cid,flashed RUU.exe just like that,and stock N again.Then applied root,here I am.If I wasn't s-off,in some place on this process,I believe I would be bricked,hard or soft,but bricked.
3-You can get the updates normally when s-off locked/unlocked through the OTA.
4-You should s-off while you're still on MM,because afaik sunshine isn't compatible with N yet.
ordeniz said:
1-Yes. But s-on is not recommended unless you really really need it.
2-For example,I'm s-off unlocked.Changed my Europe device's Cid and Mid to US Unlocked version,flashed latest Nougat RUU.exe.Wanted to go back to Viper 3.5 MM,Flashed US unlocked MM RUU.exe,Changed mid cid,Flashed a stock MM European MM 1.90 rom,flashed Viper,upgraded firmware to 1.95 through fastboot.And that's it.I was back in the beginning.2 days later,saw the root came out,changed mid-cid,flashed RUU.exe just like that,and stock N again.Then applied root,here I am.If I wasn't s-off,in some place on this process,I believe I would be bricked,hard or soft,but biricked.
3-You can get the updates normally when s-off locked/onlocked through the OTA.
4-You should s-off while you're still on MM,because afaik sunshine isn't compatible with N yet.
Click to expand...
Click to collapse
Thanks for the fast anwser!
So the software updates only cause trouble when the bootloader is unlocked, regardless of being in s-off or s-on mode?
If I S-off now, will I be able to upgrade to N and keep the "S-off LOCKED" state?
bence.szij said:
Thanks for the fast anwser!
So the software updates only cause trouble when the bootloader is unlocked, regardless of being in s-off or s-on mode?
If I S-off now, will I be able to upgrade to N and keep the "S-off LOCKED" state?
Click to expand...
Click to collapse
No,not updates.Downgrades may cause serious problems if you are not s-off.
Yes,you keep the s-off locked.
ordeniz said:
No,not updates.Downgrades may cause serious problems if you are not s-off.
Yes,you keep the s-off locked.
Click to expand...
Click to collapse
Thank you very much!
ordeniz said:
1-Yes. But s-on is not recommended unless you really really need it.
2-For example,I'm s-off unlocked.Changed my Europe device's Cid and Mid to US Unlocked version,flashed latest Nougat RUU.exe.Wanted to go back to Viper 3.5 MM,Flashed US unlocked MM RUU.exe,Changed mid cid,Flashed a stock MM European MM 1.90 rom,flashed Viper,upgraded firmware to 1.95 through fastboot.And that's it.I was back in the beginning.2 days later,saw the root came out,changed mid-cid,flashed RUU.exe just like that,and stock N again.Then applied root,here I am.If I wasn't s-off,in some place on this process,I believe I would be bricked,hard or soft,but bricked.
3-You can get the updates normally when s-off locked/unlocked through the OTA.
4-You should s-off while you're still on MM,because afaik sunshine isn't compatible with N yet.
Click to expand...
Click to collapse
I've been curious about this, does the MID matter? Europe is 2PS62000 and US is 2PS65000. I didnt know if there were hardware differences beyond radio ones, and whether or not that would create problems for European models outside of US?
Well,I read on the forum (don't remember which thread) someone having a problem because he forgot to type 1 zero in the mid.I mean it would be same if you change cid but not mid.And since it is really easy to change ,I changed them both.
Related
Hi folks,
I have just bought a new UK HTC One M8 on Vodafone after having problems with my Canadian HTC One which didn't have the compatible LTE frequency for UK.
Anyhow.. I understand to debrand I need to S-OFF first, change CID to HTC__001 and then flash a stock firmware.
Just need some help with the following:
Do I need to do something to the MID? (if so, what should it be for stock UK unlocked/unbranded version?)
Can the debrand be done without rooting the device as Firewater requires the phone to be rooted (if no, is it a temp root? so I can use the bank apps etc)
Is there a method to S-OFF without root?
What's the best firmware to flash so I can get the future OTA?
Thanks in advance.
Regards
Just need some help with the following:
Do I need to do something to the MID? (if so, what should it be for stock UK unlocked/unbranded version?)
Can the debrand be done without rooting the device (if no, is it a temp root? so I can use the bank apps etc)
Does the firewater method permanently root the phone?
What's the best firmware to flash so I can get the future OTA?
Click to expand...
Click to collapse
1) Shouldn't have to change MID. The MID should be 0P6B1000 which I think the Vodafone UK phone already is, seeing as it's European.
2) You'll probably need root to get Sunshine S-OFF to work***
3) Firewater method doesn't work anymore period. You'll have to use Sunshine it's $25 but it'll get the job done(Hopefully your device is supported then, as Sunshine doesn't work for some devices) and it's the only way to get S-OFF. I think there is a temp root available for it... check at thread. SunShine for modern Motorola & HTC devices
4) Of course the WWE International Firmware x.xx.401.x. As long as you run with the 401, any Asian WWE or 1540(Developer Edition, needs change of MID) you'll stay up to date directly through HTC.
BerndM14 said:
1) Shouldn't have to change MID. The MID should be 0P6B1000 which I think the Vodafone UK phone already is, seeing as it's European.
2) You'll probably need root to get Sunshine S-OFF to work***
3) Firewater method doesn't work anymore period. You'll have to use Sunshine it's $25 but it'll get the job done(Hopefully your device is supported then, as Sunshine doesn't work for some devices) and it's the only way to get S-OFF. I think there is a temp root available for it... check at thread. SunShine for modern Motorola & HTC devices
4) Of course the WWE International Firmware x.xx.401.x. As long as you run with the 401, any Asian WWE or 1540(Developer Edition, needs change of MID) you'll stay up to date directly through HTC.
Click to expand...
Click to collapse
Cheers mate, this is very useful.
I will read up on Sunshine and go from there.. My banks app wont work on a rooted phone therefore I wasn't keen to root the phone.
I have downloaded 1.54.401.5-Firmware (Thanks to SoLdieR9312) is it the right one? thinking if I flash this rom and the OTA brings it up to date.
How about the messages on HBOOT, will it say tampered. I understand there are fixes here but want to make sure whether root is required again to check apply the fix.
scotcruz said:
Cheers mate, this is very useful.
I will read up on Sunshine and go from there.. My banks app wont work on a rooted phone therefore I wasn't keen to root the phone.
I have downloaded 1.54.401.5-Firmware (Thanks to SoLdieR9312) is it the right one? thinking if I flash this rom and the OTA brings it up to date.
How about the messages on HBOOT, will it say tampered. I understand there are fixes here but want to make sure whether root is required again to check apply the fix.
Click to expand...
Click to collapse
Yeah you'll need root access to reset the flags, it gets done through the shell and will need root privileges.
[how to] lock/unlock your bootloader without htcdev(s-off required) To make the bootloader show "Locked" instead of "Relocked" if you lock it again. Needs root.
[how to] remove your "tampered" banner Will make Software status "Official" and not "Modified". Needs root.
Yeah you can use any 401 firmware you like. Going to an earlier version is a nice way to test if the OTAs are working like it should.
Banking app ... Probably flippin' Barclays again
Fantastic mate.. really appreciate your help..
will keep posted..
Sunshine payment is via PayPal so get the phone going first and then after you've debranded the phone you can set it up again unrooted
Hey guys,
First post and thread, unfortunately. May have been done before, so sorry if that's the case (and if it is I guess a quick link can clear this confusion up!)
I've got a tmobile HTC One M8 running Android 4.4.4 with an unlocked boot loader, clockworkmod 6.0.4.8 with s-on.
New android update is out and while I'm not necessarily keen on updating it, the icon is annoying. As well, I originally rooted the phone for some apps and sorts that I don't even use and I'm mainly interested in just bringing the phone back to a stock recovery so I can unroot it.
Tried using the RUU posted but I believe due to the s-on and unlocked boot loader, it doesn't work for me. Step one is an error on it.
What can I do here to bring the phone back to stock recovery? I'm not 100% I made a backup before I put cwm on it. May have but for arguments sake let's say I didn't.
Any and all help is appreciated. thanks so much everyone.
Metilinos said:
Tried using the RUU posted but I believe due to the s-on and unlocked boot loader, it doesn't work for me. Step one is an error on it.
Click to expand...
Click to collapse
RUUs run fine with s-on, and I don't know why folks keep posting that it doesn't.
But you do however, need to relock the bootloader (since you are s-on) to run the RUU. Its absolutely mandatory (with s-on), and almost certainly why the RUU fails. THe RUU also needs to match your CID (but if you are properly trying a T-Mob RUU on a T-Mob version M8, that is not the issue), and further you cannot "downgrade" or run an older version RUU (older hboot) than what is on the phone.
But again, unlocked bootloader alone will make the RUU fail.
I haven't really seen a whole lot of s-off since firewater hasn't worked any longer. I kind of figured the unlocked bootloader was an issue as well. Mobile right now and working so not a whole lot I can do. Basically make sure the CID matches the RUU and relock the bootloader and I should be good to go? I picked up the T-Mobile RUU and I have a tmobIle M8, I didn't really think to check the CID, I just mainly assumed the failed run was from other sources.
Metilinos said:
I haven't really seen a whole lot of s-off since firewater hasn't worked any longer. I kind of figured the unlocked bootloader was an issue as well. Mobile right now and working so not a whole lot I can do. Basically make sure the CID matches the RUU and relock the bootloader and I should be good to go? I picked up the T-Mobile RUU and I have a tmobIle M8, I didn't really think to check the CID, I just mainly assumed the failed run was from other sources.
Click to expand...
Click to collapse
As long as you have the right carrier RUU, the CID will also match. I assume T-Mobile US? As there is also T-Mobile in Europe.
As long as its right carrier (CID) and not trying to run an older version RUU, the unlocked bootloader is the only problem.
Yes T-Mobile US.
I'll have to double check the RUU, I'm pretty sure I grabbed it off here from a different thread, but like you said, the unlocked bootloader obviously was an issue.
In the case, and I'm assuming it's rare, that it could be that, is there an easy way to tell whether or not I have the most current RUU?
Thanks a bunch, really appreciating the help. I've been kind of at a standstill with this and haven't really tried much in fear of killing the phone.
Metilinos said:
In the case, and I'm assuming it's rare, that it could be that, is there an easy way to tell whether or not I have the most current RUU?
Click to expand...
Click to collapse
Do you mean its rare to run the wrong version RUU? If so, I'd say no, its not rare at all. Folks are often not aware of the version requirement (with s-on, this requirement is bypassed with s-off) and try to run an "old" RUU.
All the T-Mob US RUUs are posted here: http://forum.xda-developers.com/showthread.php?t=2714456
3.32 is Android 4.4.4
4.20 is Android 5.0
3.32 is what I have at the moment. With android 5 coming over the air a week or so ago for myself and 4.4.4 being on the phone when I got it just a couple months back, that's what I guess I was insinuating by rare. But thank you a bunch for your help. Again it's very much appreciated. Obviously got myself in a little over my head here.
Greetings- I have an M8 running CM12 (nightly)
main 4.20.666.1
hboot 3.19.0.0.0000
S-On
CM12 nightly
twrp2.6
SuperSU
I'm hoping to restore to upgrade but the *$$*%*$ S-On issue won't allow me to. My original recovery is corrupt/gone and I just wonder if anyone has any (good) ideas?
Tried Firewater and got the PIE error.
You guys are doing a great job here- I've learned alot lurking and hope to continue...
cheerss
Superflous said:
I'm hoping to restore to upgrade but the *$$*%*$ S-On issue won't allow me to.
Click to expand...
Click to collapse
What exactly are you trying to do, that you think s-on is preventing? Unless I'm missing something, I don't think there is anything you are trying to do, that would be impeded by s-on.
Superflous said:
My original recovery is corrupt/gone and I just wonder if anyone has any (good) ideas?
Click to expand...
Click to collapse
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Superflous said:
Tried Firewater and got the PIE error.
Click to expand...
Click to collapse
Firewater was discontinued by the developer 6 months ago (online service, so no longer works).
Sunshine is the only current s-off method, if you really need s-off (not clear that you do).
redpoint73 said:
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Click to expand...
Click to collapse
Already moved my stock recovery collection to here : http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
All in one place and easier to find I guess.
ckpv5 said:
Already moved my stock recovery collection to here : http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
All in one place and easier to find I guess.
Click to expand...
Click to collapse
Certainly great to have it in one place, and thanks for doing so!
redpoint73 said:
What exactly are you trying to do, that you think s-on is preventing? Unless I'm missing something, I don't think there is anything you are trying to do, that would be impeded by s-on.
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Firewater was discontinued by the developer 6 months ago (online service, so no longer works).
Sunshine is the only current s-off method, if you really need s-off (not clear that you do).
Click to expand...
Click to collapse
tx for recovery link, sorry if it wasn't explained right but i want to restore my phone back to Bell firmware and lollipop . I spoke with the Root ninja via email ans Sunshine won't work on my phone(their words). I have tried to install the "firmware_M8SD_4.20.666.1_Modified_Bell_Canada.zip" but it fails and locks me up in the blue CM head until I reset, then reverts back to CM12. I'm just getting into this but if I understand correct you need S-off to flash firmware. If this isn't right I would sure appreciate the path to the correct way to put my phone back to original. Tx for you help
Superflous said:
I have tried to install the "firmware_M8SD_4.20.666.1_Modified_Bell_Canada.zip" but it fails and locks me up in the blue CM head until I reset, then reverts back to CM12. I'm just getting into this but if I understand correct you need S-off to flash firmware.
Click to expand...
Click to collapse
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
redpoint73 said:
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
Click to expand...
Click to collapse
'
so then I'm looking for a stock ROM from the carrier for firmware 4.20.666.1
tx again Redpoint
redpoint73 said:
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
Click to expand...
Click to collapse
As a followup- tx for taking the time to explain- I have set the phone back to stock and happy to have learned some.
You are one of the good ones'
Cheers
Superflous said:
As a followup- tx for taking the time to explain- I have set the phone back to stock and happy to have learned some.
You are one of the good ones'
Cheers
Click to expand...
Click to collapse
You're very welcome. Glad to see it worked out well for you.
Please click the "Thanks" button for any posts you found helpful.
Hi guys, I got the HTC 10 bell variant at a good price and since is my back up phone I'm trying to put it to the test to change it from bell variant to the US variant, I was reading a lot of threads but im confused, , I unlocked the bootloader, I instaled the twrp, now how do i change the CID ??mine shows 666, and I want to change it to 617 , do I have to have S-OFF?? or I can do that with S-ON since the Bootloader is unlocked , will I get the OTA updates for the 617 after i change it?? (btw i dont want to chage it to 401 international because im afraid i will loose the band 4 LTE )
I'm with bell and changed to us unlocked. There might be a way to do it without s-off like maybe super cid. But to install ruu.exe you need s-off. You will get ota but to apply all you need is to reinstall stock recovery.
Sent from my HTC 10 using Tapatalk
You can't change your CID and flash the Unlocked version without S-OFF.
Thanks guys for your replays ,btw nitramus can u pls add a step by step how I did it??I'm new with the HTC
Since you're at the cid part just look for the thread for changing cid and flash ruu. And look at the thread with all the backups for all the versions or stock rom. You will have all you need, latest available rom with ota. To prevent any problems as soon as your phone is ready to use after ruu and you logged in to you account apply ota right away, then flash supersu and have fun.
Sent from my HTC 10 using XDA-Developers mobile app
But first do I have to take s-off??I mean to change from s-on to s-off
nutzuTo said:
But first do I have to take s-off??I mean to change from s-on to s-off
Click to expand...
Click to collapse
Yes to convert your phone to U.S Unlocked you'd have to S-off to be able to change your CID. You gotta pony up the 25 USD, which is worth it in my opinion if you're gonna use the 10 as your main phone and tinker with it for a year or two.
Basically follow the steps from this guide, and when it comes to flashing an RUU use the Unlocked one you can download directly from HTC.com
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-drand-convert-htc-10-to-t3374593
BTW it's very fitting that Bell's CID is 666
Tarima said:
Yes to convert your phone to U.S Unlocked you'd have to S-off to be able to change your CID. You gotta pony up the 25 USD, which is worth it in my opinion if you're gonna use the 10 as your main phone and tinker with it for a year or two.
Basically follow the steps from this guide, and when it comes to flashing an RUU use the Unlocked one you can download directly from HTC.com
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-drand-convert-htc-10-to-t3374593
BTW it's very fitting that Bell's CID is 666
Click to expand...
Click to collapse
OK did that so I have S-off, I changed the CID on the cmd , and than I flashed with RUU_PERFUME_WL_M60_SENSE80GP_NA_Gen_Unlock_1.53.617.5 than update to the latest ones that they pop up to update, nice Thank you ,btw if i want to change S-on will impact the updates or should i keep it S-off??
Personally I don't bother to change back but if security is important for you then maybe. Later depending if you want to change things again depending on what you do you might still need s-off.
Sent from my HTC 10 using XDA-Developers mobile app
nutzuTo said:
OK did that so I have S-off, I changed the CID on the cmd , and than I flashed with RUU_PERFUME_WL_M60_SENSE80GP_NA_Gen_Unlock_1.53.617.5 than update to the latest ones that they pop up to update, nice Thank you ,btw if i want to change S-on will impact the updates or should i keep it S-off??
Click to expand...
Click to collapse
If you are rooted and/or have a custom recovery, you can't use the official OTAs. You'll need the stock and never rooted ROM (it has to have an unmodified system partition), and also the stock recovery to flash it.
The easiest (and often quicker way than waiting for an official OTA) is to just flash a firmware.zip package in either fastboot or by the rename/SD card method.
I recommend the ones on this thread. You can find both Full Stock .zips there, that will wipe your phone (because they contain the boot.img), and No-Wipe .zips that won't wipe your phone (obviously) as they have the boot.img (kernel and ramdisk) removed, and also contain the latest TWRP recovery versions instead of the stock recovery.
nutzuTo said:
OK did that so I have S-off, I changed the CID on the cmd , and than I flashed with RUU_PERFUME_WL_M60_SENSE80GP_NA_Gen_Unlock_1.53.617.5 than update to the latest ones that they pop up to update, nice Thank you ,btw if i want to change S-on will impact the updates or should i keep it S-off??
Click to expand...
Click to collapse
To add regarding future OTA updates, if you want them directly from HTC you'll also have to remove SuperCID, if you have it. Just having a stock/unmodified system and recovery isn't enough.
And I agree, just keep S-off unless you're making a warranty claim.
Tarima said:
To add regarding future OTA updates, if you want them directly from HTC you'll also have to remove SuperCID, if you have it. Just having a stock/unmodified system and recovery isn't enough.
And I agree, just keep S-off unless you're making a warranty claim.
Click to expand...
Click to collapse
I was hoping someone might have the official stock firmware including recovery, from bell? I have to send my phone in for warranty repair. I have my stock system backed up and am on firmware 121.666... I have s-off and boot loader locked status. I have super cid 11111111. Any help will be reciprocated. Thank you for any help.
Salem's galaxy said:
I was hoping someone might have the official stock firmware including recovery, from bell? I have to send my phone in for warranty repair. I have my stock system backed up and am on firmware 121.666... I have s-off and boot loader locked status. I have super cid 11111111. Any help will be reciprocated. Thank you for any help.
Click to expand...
Click to collapse
Hey, did you get this figured out?
I have a stock backup in my recovery, might work. Might not lol..
Was thinking of going US since Bell still has not pushed an update out..
I updated my HTC 10 to the brand new 7.0. It seems either Google or HTC has totally broken the long pause conference call pin feature in android. (This is where you dial a number and a conference pin separated by a semi-colon like XXXXXXXXXX;XXXXX) The popup asking me if I want to send the Pin number disappears after about 3 or 4 seconds way before the "Beep" when i need to send the pin.
Total deal breaker for me, since I make conference calls ALL day and I'm not going to revert to writing pin numbers on my hand while i'm in the car so I can dial them at the beep.
I desperately need to go back to Android 6.0.
I have lots of flashing, unlocking, and custom rom experience, but this device has some strange quirks like breaking the radio if you decrypt the file system...
Do I just need to use an android 6.0 RUU?
Will there be any issues due to encryption, 7.0 firmware, or anything else I need to be careful of when downgrading?
I am wondering too about downgrading procedure...
I want to know if it is safe using ruu.
I want to convert my international Htc 10 to developer unlocked and flash ruu so I can receive the nougat it's just to try it out.
Can I reverse this?
Looking forward to that answer.
If you're s-off it should be ok I think. But without s-off, downgrading firmware using an official RUU is not possible
sardelisp said:
I am wondering too about downgrading procedure...
I want to know if it is safe using ruu.
I want to convert my international Htc 10 to developer unlocked and flash ruu so I can receive the nougat it's just to try it out.
Can I reverse this?
Looking forward to that answer.
Click to expand...
Click to collapse
I was on Viper 3,5. I converted my cid-mid to us unlocked and installed latest US UNLOCKED MM RUU.exe successfuly. Then I checked the firmware and took the official OTA,upgraded to Nougat successfuly. So I guess you can have Nougat,too.
Now I am on Nougat US Unlocked S-off cid BS_US001 mid 2PS650000 . I am wondering if I could revert to MM with the RUU.exe I have. Do I have to change to Supercid or do anything else,or just the RUU.exe would do the trick?
ordeniz said:
I was on Viper 3,5. I converted my cid-mid to us unlocked and installed latest US UNLOCKED MM RUU.exe successfuly. Then I checked the firmware and took the official OTA,upgraded to Nougat successfuly. So I guess you can have Nougat,too.
Now I am on Nougat US Unlocked S-off cid BS_US001 mid 2PS650000 . I am wondering if I could revert to MM with the RUU.exe I have. Do I have to change to Supercid or do anything else,or just the RUU.exe would do the trick?
Click to expand...
Click to collapse
I downgraded back to 6 from 7 with no issues
gillim74 said:
I downgraded back to 6 from 7 with no issues
Click to expand...
Click to collapse
You were like me?
ordeniz said:
You were like me?
Click to expand...
Click to collapse
Yeah
gillim74 said:
I downgraded back to 6 from 7 with no issues
Click to expand...
Click to collapse
And when you say you downgraded..
Were you S-Off? (I'm not and since you said you were like ordeniz, I assume you were?)
Were you on the official 7 OTA (with firmware upgraded) or a custom rom built on 7 but without the firmware upgrade? (Again, if you were like ordeniz then you had the official OTA.)
I just wanted to be clear, and not make any assumptions.
x51 said:
And when you say you downgraded..
Were you S-Off? (I'm not and since you said you were like ordeniz, I assume you were?)
Were you on the official 7 OTA (with firmware upgraded) or a custom rom built on 7 but without the firmware upgrade? (Again, if you were like ordeniz then you had the official OTA.)
I just wanted to be clear, and not make any assumptions.
Click to expand...
Click to collapse
I am s-off converted my htc 10 to us unlocked as its the verizon variant upgraded to nougat didnt reallly like it so i downgrade back to 1.96
Tarima said:
If you're s-off it should be ok I think. But without s-off, downgrading firmware using an official RUU is not possible
Click to expand...
Click to collapse
gillim74 said:
I am s-off converted my htc 10 to us unlocked as its the verizon variant upgraded to nougat didnt reallly like it so i downgrade back to 1.96
Click to expand...
Click to collapse
OK. Thanks to all.
Guess I need to S-Off. (I hope sunshine works on 7.0) or I'm pretty well screwed.
x51 said:
OK. Thanks to all.
Guess I need to S-Off. (I hope sunshine works on 7.0) or I'm pretty well screwed.
Click to expand...
Click to collapse
As of now i dont think sunshine does
The sure thing I know is that you need to be rooted to be s-off. If sunshine will succeed you will know it when the sunshine app check your system. Download the app and before in app purchase a licence will tell you if you have successfull s off.
incallui.apk
Would someone be so kind as to upload a copy of InCallUI.apk from a 6.x Rom.
It's located in
/system/priv-app/InCallUI