The title is wrong. It should be "without s-off".
Hello. Is there any way to debrand the phone completley without s-off? I have done it before, by flashing the unlocked ruu on a s-off M8. But I really dont want to pay 25 dollars for each phone ( I have 2 htc 10's to do), especially since I only want to debrand, nothing else. All I want is stock, with unlocked version feel. Plus I keep getting an ID error (I guess a Sprint network ID from trying to connect) that I can not remove. I have looked at custom roms, but they seem to be only 2, and they are really modded. I dont want mods. I prefer stable, and original.
Thanks for any suggestions.
Find the stock unlocked system image file in the non-sprint HTC 10 forum. Flash that and mission accomplished. No S-off needed. Would be interested to know if carrier aggregation works for you after that - is it part of the rom or is it part of radio configuration.
bootlooper said:
Find the stock unlocked system image file in the non-sprint HTC 10 forum. Flash that and mission accomplished. No S-off needed. Would be interested to know if carrier aggregation works for you after that - is it part of the rom or is it part of radio configuration.
Click to expand...
Click to collapse
Thanks. I will look it up. By carrirer agregation I am guessing you think I am using it for sprint. I forgot to mention that I am using it on att, I just unlocked the sim-lock.
I see. I did as suggested above and went took my sprint 10 to T-Mobile. Carrier Aggregation, volte, and Wi-Fi calling do not work for me. I then did s-off, changed cid, flashed official T-Mobile RUU, flashed my backed up radio, modemst1, and modemst2 partitions to keep sim unlock intact but those features still wouldn't work. Flashed US unlocked RUU then the partitions above and still no dice. My only benefit I can tell from the S-off is that I can and have successfully taken an OTA and suspect I will always be able to unless a radio update is included. Then I will need to reflash my backed up partitions to be back in business.
bootlooper said:
I see. I did as suggested above and went took my sprint 10 to T-Mobile. Carrier Aggregation, volte, and Wi-Fi calling do not work for me. I then did s-off, changed cid, flashed official T-Mobile RUU, flashed my backed up radio, modemst1, and modemst2 partitions to keep sim unlock intact but those features still wouldn't work. Flashed US unlocked RUU then the partitions above and still no dice. My only benefit I can tell from the S-off is that I can and have successfully taken an OTA and suspect I will always be able to unless a radio update is included. Then I will need to reflash my backed up partitions to be back in business.
Click to expand...
Click to collapse
Thanks. I have been searching all morning while waiting for the htcdev.com email. I have not found an official unlocked image I can flash. What would it be called on forums? I have found some, but they say you need s-off to flash. And other roms I have found are outdated, or deodexed. I want just clean, no added apps, and original.
If I knew how to link a post I would. Look in the sprint 10 guides subforum. Look for the thread that starts with [stock]. The most recent RUU was on page 198 of the app thread posted by kisakuku on 5/3.
You will need the 2nd link in the post-the 2ps###.zip one. As it is posted it will not work because you are son. You need to unzip and then you will have a rom.img and a boot.img amongst others. Those are the 2 you need to flash to get to stock. You will flash them using twrp. Select the box for Flash image, not flash zip.
Saw your other thread about losing data. You should not lose data by flashing to a new rom.
I have assumed your sprint 10 was already on nougat prior to all this.
Alternatively, you could just enjoy Viper. I only left trying to do whatever I could think of for volte to work and never went back because I was tired of redownloading and setting up apps, etc.
Thanks. I found the post. I didnt know you could extract the images from the zip and manually flash them. I will test it, hopefully it will work without any issues. Right now I am on a stock deodexed US unlocked rom, and everything seems to work, but no OTAs, and what is worse is that for some reason it randomly crashes when just navigating the homescreen, and reboots.
Related
Hey all. I've got a USCC Electrify M, bootloader unlocked and rooted running twrp 2.?.?> and I have a few questions.
First now that my boot loader is unlocked do I still need to flash using the retail edition files?
Next, If so do I need to use SafeStrap to do it? and is it ok to use safestrap with an unlocked bootloader?
Next, most of the roms are built from the Verizon rom, If I flash these will I break my phone due to bad build.prop, radio, and possibly other files like apn's and whatnot.
and last , if so can I use the stock files from the post at teamuscc to replace the files with the correct ones for USCC, either before or after flashing.
I know this is a tall order, but I'm relatively new to the whole safestrap bootloader thing coming from an Electrify 1 that I managed to unlock after the 2.3.5 unlock lockout, and not too familiar with the whole rom contents thing yet. Once I get a few answers to my other posts I may feel more comfortable just giving it a whirl. I do have a nandroid of where I am now, but don't want to screw anything up that can't be fixed with that.
Thanks for any info.
LTE band 66 service and OTA updating is disabled through the DirtySanta root exploit on the stock build when rooted. I was hoping that there would be a ROM or two for the Canadian version of this device. Need something relatively stable, with nightly updates, and with support for AWS 3/Band 66 connectivity
Any leads are are appreciated. Thanks!
Considering the 915 isn't even a supported device no. If someone has gotten the 915 please let me know.
Until FREEDOM Mobile allows the LG V20 LOCKED bootloader to be UNlocked, there will be no FREEDOM to have a custom ROM anytime soon
That is what I got the T-mobile version with the unlockable bootloader which works great on NON-freedom.
lumberguy1028 said:
LTE band 66 service and OTA updating is disabled through the DirtySanta root exploit on the stock build when rooted. I was hoping that there would be a ROM or two for the Canadian version of this device. Need something relatively stable, with nightly updates, and with support for AWS 3/Band 66 connectivity
Any leads are are appreciated. Thanks!
Click to expand...
Click to collapse
Well i have a theory about getting root and signal on the 915 but it involves losing recovery afterwards. If anyone wants to discuss it let me know
markbencze said:
Well i have a theory about getting root and signal on the 915 but it involves losing recovery afterwards. If anyone wants to discuss it let me know
Click to expand...
Click to collapse
Actually very interested. I have the LGUP tool on Windows with Uppercut drivers installed, so I can unbrick my device even without recovery. Living without a rooted device is causing me extreme stress and trauma.
lumberguy1028 said:
Actually very interested. I have the LGUP tool on Windows with Uppercut drivers installed, so I can unbrick my device even without recovery. Living without a rooted device is causing me extreme stress and trauma.
Click to expand...
Click to collapse
Ok so here's my theory.
Basically we can root and have twrp but the problem is that signal ceases to exist afterwards which we assume is caused by the bootloader. Someone posted that they fixed their signal issues using the hidden menu features. But they didn't elaborate if they were rooted at the time and that was the direct reason for losing it in the first place. Nor have they replied. So that part is unknown. It may or may not be an option. The other question I had was is it just wind users who lose signals or does it affect wind devices that are unlocked but being used on other networks like bell, etc.
Anyway those are the unknown things that I'd like some clarification on. But in the meantime here's a theory I have that may or may not work if the above signal fix doesn't work.
So if the above fixing signal doesn't work via that hidden menu then we should be able to confirm the bootloader is the issue. What that means is that we need to have stock bootloader in order for everything to work.
But you cannot have stock bootloader with twrp unless you've "bumped" your recovery which we cannot do.
So my theory was to follow the whole root method and once your phone is booted up with root and twrp you would extract the stock recovery and stock bootloader from the restore file. Then you would flash them via flashfire which I'm told can be done. I'm told that flashing the bootloader does wipe your device which would eliminate root since it's the systemless method. So in theory you'd be back to pure stock again. That's not what we want to have. So we would have to use an alternative root like phh's root method flashed instead of supersu from twrp during the initial root process here. My theory is that you would be restored to stock again but you would have root at least.
So you would at least be able to tinker just not flash stuff. But I believe you can flash a few things from flashfire and still have root for general tinkering or ad block etc.
Of course there is also the possibility that with the locked bootloader (stock) that your phone may not even boot due to new security features in 7.0
But like I said this is just a theory that may or may not work. I haven't had time to try it because I'm constantly busy working and testing themes but if I do ever get time I would consider trying it if we can confirm that we are able to 100% restore to stock. At least with that confirmation we know that if it doesn't work we can get back to how things were.
Hopefully that makes sense.
markbencze said:
Ok so here's my theory.
Basically we can root and have twrp but the problem is that signal ceases to exist afterwards which we assume is caused by the bootloader. Someone posted that they fixed their signal issues using the hidden menu features. But they didn't elaborate if they were rooted at the time and that was the direct reason for losing it in the first place. Nor have they replied. So that part is unknown. It may or may not be an option. The other question I had was is it just wind users who lose signals or does it affect wind devices that are unlocked but being used on other networks like bell, etc.
Anyway those are the unknown things that I'd like some clarification on. But in the meantime here's a theory I have that may or may not work if the above signal fix doesn't work.
So if the above fixing signal doesn't work via that hidden menu then we should be able to confirm the bootloader is the issue. What that means is that we need to have stock bootloader in order for everything to work.
But you cannot have stock bootloader with twrp unless you've "bumped" your recovery which we cannot do.
So my theory was to follow the whole root method and once your phone is booted up with root and twrp you would extract the stock recovery and stock bootloader from the restore file. Then you would flash them via flashfire which I'm told can be done. I'm told that flashing the bootloader does wipe your device which would eliminate root since it's the systemless method. So in theory you'd be back to pure stock again. That's not what we want to have. So we would have to use an alternative root like phh's root method flashed instead of supersu from twrp during the initial root process here. My theory is that you would be restored to stock again but you would have root at least.
So you would at least be able to tinker just not flash stuff. But I believe you can flash a few things from flashfire and still have root for general tinkering or ad block etc.
Of course there is also the possibility that with the locked bootloader (stock) that your phone may not even boot due to new security features in 7.0
But like I said this is just a theory that may or may not work. I haven't had time to try it because I'm constantly busy working and testing themes but if I do ever get time I would consider trying it if we can confirm that we are able to 100% restore to stock. At least with that confirmation we know that if it doesn't work we can get back to how things were.
Hopefully that makes sense.
Click to expand...
Click to collapse
Im not sure how much you followed with me but... In my attempts to find a return to stock method i reflashed my stock aboot(bootloader). This bricked me. There is no way to use the stock bootloader once its been replaced that i have found.
me2151 said:
Im not sure how much you followed with me but... In my attempts to find a return to stock method i reflashed my stock aboot(bootloader). This bricked me. There is no way to use the stock bootloader once its been replaced that i have found.
Click to expand...
Click to collapse
Thanks for clearing that up. So then my next question was did you attempt that signal fix method and were you using yours on wind or was it an unlocked wind used on another network?
here's the link to this signal fix https://forum.xda-developers.com/showpost.php?p=70328080&postcount=3
and here is a post about someone saying they used it to fix their signal but they wouldn't elaborate on anything else.
https://forum.xda-developers.com/showpost.php?p=70571563&postcount=12
markbencze said:
Thanks for clearing that up. So then my next question was did you attempt that signal fix method and were you using yours on wind or was it an unlocked wind used on another network?
here's the link to this signal fix https://forum.xda-developers.com/showpost.php?p=70328080&postcount=3
and here is a post about someone saying they used it to fix their signal but they wouldn't elaborate on anything else.
https://forum.xda-developers.com/showpost.php?p=70571563&postcount=12
Click to expand...
Click to collapse
Lol Im the dirtysanta dev. I have a LS997. Not a 915.
me2151 said:
Lol Im the dirtysanta dev. I have a LS997. Not a 915.
Click to expand...
Click to collapse
Well I knew you had worked on ds. I wasn't sure however if you had a 915 or not. So then at this point it seems that if that signal fix is in fact valid that it is the only method to get things operational and I would presume it's a stretch given the user who posted about it doesn't seem to have any credibility to go by.
markbencze said:
Well I knew you had worked on ds. I wasn't sure however if you had a 915 or not. So then at this point it seems that if that signal fix is in fact valid that it is the only method to get things operational and I would presume it's a stretch given the user who posted about it doesn't seem to have any credibility to go by.
Click to expand...
Click to collapse
Thanks for this. Yeah DirtySanta may have been developed for LS997, but it seems to work on H915 minus the modem issue.
lumberguy1028 said:
Thanks for this. Yeah DirtySanta may have been developed for LS997, but it seems to work on H915 minus the modem issue.
Click to expand...
Click to collapse
Correct but it's useless to use since the phone doesn't function properly afterwards. If there was a confirmed way to have data and signal working then that would be great but there is nothing confirmed to work yet.
I've just moved to a V20 from a Note 4. All my Note4 ROMS were T-Mobile versions. I believe Rogers/Fido phones are basically the same as T-Mobile, which uses freq. channel 66 as well.
Has anyone tried a T-Mobile (918) ROM on the 915 yet? Might just work...
no root yet for freedom????/
whats the method
whats the method to root the lg h915
diehard2013 said:
no root yet for freedom????/
Click to expand...
Click to collapse
The 'Freedom' name becomes a bit ironic for the LG V20 H915 variant it seems. Not a lot of freedom when one can't unlock and root it. Just got one the other day as somehow my Note 4 stopped functioning as a phone, after a couple of months of fun running through loads of Lineage and other nightlies. Loved that phone, but I'll come to love the V20 I'm sure. Already like it a lot. But root seems essential. I haven't had an unrooted phone for more than a few hours in years. Adaway and just general user control of the file system seems essential. Getting rid of bloatware and such. I mean... I disabled a lot of that nonsense, but it's still there, existing in MY phone, which makes me mad. I want to dump a few custom notification sounds into root directories but can't. It's frustrating. So yeah, commenting to subscribe, and hoping a developer with a V20 in Canada decides to get excited enough to remedy the situation, whenever that becomes possible. Otherwise it seems I'll just have to get used to the odd ad and the other limitations.
GerardSamija said:
The 'Freedom' name becomes a bit ironic for the LG V20 H915 variant it seems. Not a lot of freedom when one can't unlock and root it. Just got one the other day as somehow my Note 4 stopped functioning as a phone, after a couple of months of fun running through loads of Lineage and other nightlies. Loved that phone, but I'll come to love the V20 I'm sure. Already like it a lot. But root seems essential. I haven't had an unrooted phone for more than a few hours in years. Adaway and just general user control of the file system seems essential. Getting rid of bloatware and such. I mean... I disabled a lot of that nonsense, but it's still there, existing in MY phone, which makes me mad. I want to dump a few custom notification sounds into root directories but can't. It's frustrating. So yeah, commenting to subscribe, and hoping a developer with a V20 in Canada decides to get excited enough to remedy the situation, whenever that becomes possible. Otherwise it seems I'll just have to get used to the odd ad and the other limitations.
Click to expand...
Click to collapse
Why Wouldent you just use the secret # in the hidden menu to change bands to get signial. Also you could try searching for exsisting bands that are near by, this dont require the hidden menu.
Sent from my [device_name] using XDA-Developers Legacy app
Not understanding what you are suggesting. I tried lots of hidden menu options to get the SIM recognized in the Note 4, but it appears the slot died on that phone. It just won't be a phone any more, no matter which ROM i flash.
If you mean the LG V20 I'm even more puzzled. How would changing hands help with rooting the phone?
GerardSamija said:
Not understanding what you are suggesting. I tried lots of hidden menu options to get the SIM recognized in the Note 4, but it appears the slot died on that phone. It just won't be a phone any more, no matter which ROM i flash.
If you mean the LG V20 I'm even more puzzled. How would changing hands help with rooting the phone?
Click to expand...
Click to collapse
Oops my bad i was sleeping while i read that. You can fix your sim card reader just use a soder tool. Also there maybe a root for this phone but i don't think it is safe enough yet.
Sent from my [device_name] using XDA-Developers Legacy app
Can anybody help?I am S Off. Unlocked. Rooted. I am currently on Nu Sense Rom. Need to get back to stock for warranty purposes. I try flashing the Verizon zip and get mismatch issues. 7 RU CID FAIL. Thanks for your help.
artpena2323 said:
Can anybody help?I am S Off. Unlocked. Rooted. I am currently on Nu Sense Rom. Need to get back to stock for warranty purposes. I try flashing the Verizon zip and get mismatch issues. 7 RU CID FAIL. Thanks for your help.
Click to expand...
Click to collapse
Did you make a backup of the stock system image before flashing a custom rom? I haven't tried going back to stock any other way, but I'm fairly certain that the only way to RUU back to stock is if you have a completely stock copy of your system image to restore in TWRP.
Out of curiosity, what issue are you having that require warranty service?
I'm also having trouble finding a guide to this; I've bricked phones in the past, or had issues with reverting to sell that ended up costing me 3 hours of troubleshooting.
Basically I've now found that Android Pay is something that I wish to use again; and with the N update for VZW coming out very soon I might as well go back to full stock with my bootloader locked again now that the main reason I went to s-off/unlocked was for N.
Anyone know where the guide is? If there isn't one, I will outline the steps that I think I need to take, but could use some help to make sure I don't jank it up.
1. Get the RUU from the stock ruu thread.
2. Flash said RUU
3. Factory Reset
4. ???
5. Profit?
As you can see, I'm missing the parts where I re-lock the bootloader, change the tamper flag, fix potential LTE problems (I've read that might be an issue), and whatever else might need to be done to full revert it to legit VZW.
If it matters; I have a (rooted) stock backup from 1.85.605.8 I can flash to make this easier, as I recall having to do that for prior HTC phones (I think).
I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.
anderson96007 said:
I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.
Click to expand...
Click to collapse
If its S-off already there is no need for the bootloader to be unlocked.
Thanks
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.
anderson96007 said:
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.
Click to expand...
Click to collapse
The 10 is a little different.
Locked and unlocked work basically the same, and it's my understanding it's suggested to be S-OFF locked from Sunshine crew.
I've been S-OFF locked since release of vzw S-OFF and everything works perfectly.
Hope this helps a little.
Just doesn't work
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve
anderson96007 said:
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve
Click to expand...
Click to collapse
I would leave the phone locked.
If you plan on flashing Venom, and you have already flashed twrp, there really is no need to root the current rom. Just make a backup of it in twrp (just in case) and flash Venom. Just make sure you select the correct firmware that matches the phones firmware in the aroma installer.
OK will give that a shot tomorrow thanks
If you're S-OFF. You shouldn't have any issues flashing the latest N firmware for your device, latest TWRP, and then latest N ViperROM. And since Viper comes pre-rooted, you will only need flash ViperROM.
Get a hold if you need some help, I'll do my best to assist.
Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.
anderson96007 said:
Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.
Click to expand...
Click to collapse
My HTC 10 is S-OFF Locked bootloader, this is what Sunshine crew suggests, and works the same (on the 10, previous devices are different) as unlocked bootloader.
It seems you are in a simple bootloop. Would need recovery log to see more, and Viper devs would be able to understand their stuff better than myself.
I do have suggestion as to what I would do.
You are on 6.0.1, you should update to the latest Nougat 2.41.605.18. Either by flashing the firmware, or flashing the RUU. Read up on encryption with Nougat.
Everything you said you did sounds correct to me. And as are as selecting the correct firmware in Aroma, that is for the fingerprint to work, and can easily be fixed if you accidentally select N instead of MM.
I hope this helps in some way.
Bit of background.
CID: BS_US001
MID: 2PS650000
Original verizon phone that i sent to sunshine for S-off and to unlock from Verizon. Ever since receiving it, almost a year ago, I've never been able to install a custom recovery I gave up on it for months and yesterday tried again. Finally managed to get TWRP. Then I tried to install SuperSU and bootloop. There's always been an issue getting OTAs. The OTA would download, install, and during boot, would give an error or go into bootloop. So, the plan was to finally get a recovery, root it, see about getting the latest OTA etc. Obviously that didn't work out. I feel like there's an issue with the boot sector and has always been. At this point, I just want to wipe and start over but I feel if I don't get this boot sector fixed the phone will never work properly. Any ideas? An RUU will update the OS and maybe fix the bootloop for now, but it won't deal with the OTA or issues with the boot sector that seem to be ever-present. Could use some advice.
I'm also a bit confused about something. This is originally a verizon phone but has been unlocked. When looking for RUUs from HTC should i be looking for the verizon versions or unlocked version?
vijn said:
Bit of background.
CID: BS_US001
MID: 2PS650000
Original verizon phone that i sent to sunshine for S-off and to unlock from Verizon. Ever since receiving it, almost a year ago, I've never been able to install a custom recovery I gave up on it for months and yesterday tried again. Finally managed to get TWRP. Then I tried to install SuperSU and bootloop. There's always been an issue getting OTAs. The OTA would download, install, and during boot, would give an error or go into bootloop. So, the plan was to finally get a recovery, root it, see about getting the latest OTA etc. Obviously that didn't work out. I feel like there's an issue with the boot sector and has always been. At this point, I just want to wipe and start over but I feel if I don't get this boot sector fixed the phone will never work properly. Any ideas? An RUU will update the OS and maybe fix the bootloop for now, but it won't deal with the OTA or issues with the boot sector that seem to be ever-present. Could use some advice.
I'm also a bit confused about something. This is originally a verizon phone but has been unlocked. When looking for RUUs from HTC should i be looking for the verizon versions or unlocked version?
Click to expand...
Click to collapse
You can't take OTAs as long as you have twrp installed or have a modified system partition, which you got after attempting to install SuperSU.
An RUU would restore all partition to a stock state, not just the OS. That's what I would do to get a clean slate, make a stock backup and then root it. Remember that the ruu will wipe your phone so backup your files. You won't find Verizon RUUs on HTC's website, but you can download them from the stock thread here.
Also make sure to fully read the instructions and FAQ posts in the twrp thread, and do the same in the root thread.
Edit: Re-read your post. Since yours is converted to U.S Unlocked, you indeed have to download the latest ruu from HTC's website. Forget about the Verizon ruu.
Tarima said:
You can't take OTAs as long as you have twrp installed or have a modified system partition, which you got after attempting to install SuperSU.
An RUU would restore all partition to a stock state, not just the OS. That's what I would do to get a clean slate, make a stock backup and then root it. Remember that the ruu will wipe your phone so backup your files. You won't find Verizon RUUs on HTC's website, but you can download them from the stock thread here.
Also make sure to fully read the instructions and FAQ posts in the twrp thread, and do the same in the root thread.
Edit: Re-read your post. Since yours is converted to U.S Unlocked, you indeed have to download the latest ruu from HTC's website. Forget about the Verizon ruu.
Click to expand...
Click to collapse
Sorry about the late reply. I was traveling. First off, thanks for your response. I guess my only remaining question then is what RUU do i go for? Unlocked developer? I'm just worried there might be a clash with my CID/MID. It's happened before on a previous phone. At this point, all i really want is to get stock back, make sure it's carrier unlocked, update to Oreo, and then, if I'm feeling lucky, root it, though I might just pass on that. So, would you say unlocked developer RUU is my best bet?
Again, thanks for your help.
vijn said:
Sorry about the late reply. I was traveling. First off, thanks for your response. I guess my only remaining question then is what RUU do i go for? Unlocked developer? I'm just worried there might be a clash with my CID/MID. It's happened before on a previous phone. At this point, all i really want is to get stock back, make sure it's carrier unlocked, update to Oreo, and then, if I'm feeling lucky, root it, though I might just pass on that. So, would you say unlocked developer RUU is my best bet?
Again, thanks for your help.
Click to expand...
Click to collapse
If it's an originally verizon phone which was converted to US Unlocked, then use the latest ruu for unlocked on HTC's website. It won't cause you to lose your carrier-unlocked status. It will take you to latest Nougat version. From there, take the OTA update
Tarima said:
If it's an originally verizon phone which was converted to US Unlocked, then use the latest ruu for unlocked on HTC's website. It won't cause you to lose your carrier-unlocked status. It will take you to latest Nougat version. From there, take the OTA update
Click to expand...
Click to collapse
Well, it worked. I'm currently on Oreo which is awesome. So first off, thank you very much. Not sure why it didn't work last year, but water/bridge etc.
This brings me to one more question. I want to get rid of some bloatware but would rather not do a full root. I've heard Magisk will give me the benefits of root without the security headaches that prevent things like Google Pay from working. You familiar with that? I also need 2 apps that require root. Never worked with Magisk but I have rooted a bunch of times and honestly, I kinda don't feel like doing it again, especially if I can maybe get the best of both worlds with Magisk. I just don't know enough about it. Figured maybe you might.
vijn said:
Well, it worked. I'm currently on Oreo which is awesome. So first off, thank you very much. Not sure why it didn't work last year, but water/bridge etc.
This brings me to one more question. I want to get rid of some bloatware but would rather not do a full root. I've heard Magisk will give me the benefits of root without the security headaches that prevent things like Google Pay from working. You familiar with that? I also need 2 apps that require root. Never worked with Magisk but I have rooted a bunch of times and honestly, I kinda don't feel like doing it again, especially if I can maybe get the best of both worlds with Magisk. I just don't know enough about it. Figured maybe you might.
Click to expand...
Click to collapse
I use Magisk myself. I prefer it to flashing the classic supersu for root.
Install latest twrp (make sure its the latest twrp for the 10), then flash Magisk. Then install Magisk manager app. As simple as that.
Read the instructions here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You rock man. Thanks for all the help.
vijn said:
You rock man. Thanks for all the help.
Click to expand...
Click to collapse
No worries, glad it worked.