To clip, or not to clip...have some questions - Verizon HTC One (M9)

Hi all -
Had this HTC One M9 stock for about a month now. I've been reading and reading and reading, and have the big itch to root, but also have some questions I'm hoping folks can answer that I'm a bit confused about. So I'll just get right to my questions.
I've had android phones for years, and I get the general concept of this stuff, but is this clip method so different, in that if I haven't done it before I pose a significant risk of bricking my phone or struggling to figure out the process if I've never done this method?
Does the clip method just get me S Off, or can it unlock the bootloader too?
Should I just use clip to S Off and follow instructions in this thread to unlock bootloader (http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036)?
Can I return this phone to 100% stock if I need warranty service? From what I can gather from the unlock bootloader thread above, I can lock and unlock, and I assume with clip I can S on. Is there a way to flash image to OEM stock, and is there any other Knox-like things I need to worry about that I can't trip back?
I believe I read I can install TWRP recovery, but how do I do that once I have S Off and unlocked bootloader?
My goal is really just to flash a custom rom. I don't know I want to change all the in depth things that I think I'm reading I can do with S off. Is it possible, or does it make sense, to S off, unlock bootloader (which I think is all I need for TWRP and to load ROM), then S on again?
I know obv people are sending their phones to folks to S off, but there's a few reasons I'm thinking about the clip method (please correct any misunderstanding):
I can get clip for just under $100. Comparatively if I send it off, I'd probably do a $30 donation plus fast shipping both ways...I'm already over half the cost of the clip.
If I need the clip to return phone to true stock, I'd like that have that ability myself.
I know there's a few highly recommended people on here, but I'm still uneasy about sending a $600 phone to someone I don't know.
If the process is easy enough, I could try and recoup the money by doing a few phones in my area.
I'm mysteriously not seeing many website recommendations for the clip.
Sorry for the 1001 questions, but thank you SO much in advance for anyone that can offer advice!!!

crackface said:
Hi all -
Had this HTC One M9 stock for about a month now. I've been reading and reading and reading, and have the big itch to root, but also have some questions I'm hoping folks can answer that I'm a bit confused about. So I'll just get right to my questions.
I've had android phones for years, and I get the general concept of this stuff, but is this clip method so different, in that if I haven't done it before I pose a significant risk of bricking my phone or struggling to figure out the process if I've never done this method?
Does the clip method just get me S Off, or can it unlock the bootloader too?
Should I just use clip to S Off and follow instructions in this thread to unlock bootloader (http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036)?
Can I return this phone to 100% stock if I need warranty service? From what I can gather from the unlock bootloader thread above, I can lock and unlock, and I assume with clip I can S on. Is there a way to flash image to OEM stock, and is there any other Knox-like things I need to worry about that I can't trip back?
I believe I read I can install TWRP recovery, but how do I do that once I have S Off and unlocked bootloader?
My goal is really just to flash a custom rom. I don't know I want to change all the in depth things that I think I'm reading I can do with S off. Is it possible, or does it make sense, to S off, unlock bootloader (which I think is all I need for TWRP and to load ROM), then S on again?
I know obv people are sending their phones to folks to S off, but there's a few reasons I'm thinking about the clip method (please correct any misunderstanding):
I can get clip for just under $100. Comparatively if I send it off, I'd probably do a $30 donation plus fast shipping both ways...I'm already over half the cost of the clip.
If I need the clip to return phone to true stock, I'd like that have that ability myself.
I know there's a few highly recommended people on here, but I'm still uneasy about sending a $600 phone to someone I don't know.
If the process is easy enough, I could try and recoup the money by doing a few phones in my area.
I'm mysteriously not seeing many website recommendations for the clip.
Sorry for the 1001 questions, but thank you SO much in advance for anyone that can offer advice!!!
Click to expand...
Click to collapse
OK...so when you s-off it's completely reversible and does not require a clip or card to revert. Just some simple commands. If you have a clip the best bet is to s-off and then use the adb command to unlock. The clip can unlock but it uses the HTC Dev method which let's HTC know what you've done.
Once s-off you leave it s-off. You definitely do not want to turn it on while on a custom rom. Some system write protection is turned on/off by the s flag and boot loader lock status. There's no such thing as Knox on HTC. Using already posted commands you can simply lock the boot loader, flash an ruu (like Odin image) and turn s back on.
What I normally do is s-off, then unlock via the adb command. Flash twrp. Flash supersu. Flash rom.
If you don't understand all of this and why it works this way you probably should NOT be meeting local folks to work on their phones. Sometimes things go wrong and you would be stuck in a really bad situation.
Sent from my Nexus 6 using Tapatalk

dottat said:
OK...so when you s-off it's completely reversible and does not require a clip or card to revert. Just some simple commands. If you have a clip the best bet is to s-off and then use the adb command to unlock. The clip can unlock but it uses the HTC Dev method which let's HTC know what you've done.
Once s-off you leave it s-off. You definitely do not want to turn it on while on a custom rom. Some system write protection is turned on/off by the s flag and boot loader lock status. There's no such thing as Knox on HTC. Using already posted commands you can simply lock the boot loader, flash an ruu (like Odin image) and turn s back on.
What I normally do is s-off, then unlock via the adb command. Flash twrp. Flash supersu. Flash rom.
If you don't understand all of this and why it works this way you probably should NOT be meeting local folks to work on their phones. Sometimes things go wrong and you would be stuck in a really bad situation.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Makes sense, and loud and clear on the advice on doing others' phones. Thank you so much....

Keep in mind that any clip/javacard will mark the device, so HTC will know that you had S-OFF anyway (if you ever return it for warranty).
Sent from my Nexus 5 using Tapatalk

efrant said:
Keep in mind that any clip/javacard will mark the device, so HTC will know that you had S-OFF anyway (if you ever return it for warranty).
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Says who? Was never a problem for me. You actually have a harder time on a non-vzw HTC since you have to go through HTC Dev which registers in their system anytime you call in that you have strayed from stock.
I have warrantied many phones that were Java card s-offed. Properly returned to stock they will pass everytime.
Sent from my Nexus 6 using Tapatalk

dottat said:
Says who? Was never a problem for me. You actually have a harder time on a non-vzw HTC since you have to go through HTC Dev which registers in their system anytime you call in that you have strayed from stock.
I have warrantied many phones that were Java card s-offed. Properly returned to stock they will pass everytime.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Says someone who reverse-engineered the process, and who I believe.
I'm not saying it will be a problem, only that it could, if HTC decides to get picky. (I have never RMA'd anything ever so I certainly can't speak from experience. )
Yes, I agree that if you use HTC Dev to unlock, it makes it more of a problem than using a javacard (although there's nothing preventing a non-Verizon device from using a javacard - - your comment sort of implies non-Verizon HTCs need to go the HTC Dev route).
Sent from my Nexus 5 using Tapatalk

efrant said:
Says someone who reverse-engineered the process, and who I believe.
I'm not saying it will be a problem, only that it could, if HTC decides to get picky. (I have never RMA'd anything ever so I certainly can't speak from experience. )
Yes, I agree that if you use HTC Dev to unlock, it makes it more of a problem than using a javacard (although there's nothing preventing a non-Verizon device from using a javacard - - your comment sort of implies non-Verizon HTCs need to go the HTC Dev route).
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yep...second part of my comment pertains to the unlocking of a boot loader. It's probable that a higher number of non-vzw HTC phones use software methods to s-off. Of all of the phones I have s-offed using a card, 90% were vzw. I unlock all boot loaders using adb. Most of the folks out there who do card s-offs use supercid and dev unlock afterwards. I never really understood why when you can do it without letting HTC know. The built in boot loader unlock method on the clip also uses HTC Dev. Since all vzw HTC phones are banned from dev we have to s-off first.
Sent from my Nexus 6 using Tapatalk

dottat said:
Says who? Was never a problem for me. You actually have a harder time on a non-vzw HTC since you have to go through HTC Dev which registers in their system anytime you call in that you have strayed from stock.
I have warrantied many phones that were Java card s-offed. Properly returned to stock they will pass everytime.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
True dat - I am one helped by @dottat to return to s-on, locked, and stock for a warrantee replacement. No problem.

dottat said:
I unlock all boot loaders using adb. Most of the folks out there who do card s-offs use supercid and dev unlock afterwards. I never really understood why when you can do it without letting HTC know.
Click to expand...
Click to collapse
Out of curiosity, once you have S-OFF using your javacard, how do you unlock the bootloader using dd when you don't have root? Or how do you get root?
Sent from my Nexus 5 using Tapatalk

efrant said:
Out of curiosity, once you have S-OFF using your javacard, how do you unlock the bootloader using dd when you don't have root? Or how do you get root?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Depends on the device. On m9 you simply flash twrp (don't need to be unlocked on m9 to do so) and then use adb shell in twrp. On the m8, I have twrp packaged up that it will flash in ruu mode with a locked bootloader. Then same as above.
In twrp, adb shell is root already....no need to su.
Sent from my Nexus 6 using Tapatalk

dottat said:
Depends on the device. On m9 you simply flash twrp (don't need to be unlocked on m9 to do so) and then use adb shell in twrp.
Click to expand...
Click to collapse
Thanks! I had no idea you didn't need to be unlocked to flash the recovery partition. Is it only recovery, or do you have fastboot access to other partitions as well while locked?

efrant said:
Thanks! I had no idea you didn't need to be unlocked to flash the recovery partition. Is it only recovery, or do you have fastboot access to other partitions as well while locked?
Click to expand...
Click to collapse
If I am not mistaken, you won't have fastboot access to \system or \sp1 (splash screen) without bootloader unlock, but you CAN have access to \system within a ROM if you are rooted, even if the bootloader is locked.

hgoldner said:
If I am not mistaken, you won't have fastboot access to \system or \sp1 (splash screen) without bootloader unlock, but you CAN have access to \system within a ROM if you are rooted, even if the bootloader is locked.
Click to expand...
Click to collapse
Thanks. So to confirm, with S-OFF and a locked bootloader on an M9, you have fastboot access to all partitions other than system and sp1??

efrant said:
Thanks. So to confirm, with S-OFF and a locked bootloader on an M9, you have fastboot access to all partitions other than system and sp1??
Click to expand...
Click to collapse
Why don't you want to bootloader unlock? if you're already S-OFF you can do it in adb shell. Don't hold me to what partitions are fastboot accessible with bootloader locked. I've always had an S-OFF unit with bootloader unlocked. Some partitions aren't writable in fastboot even with bootloader unlocked, although they can be flashed by aboot with an appropriate zip file. For instance, I have a custom splash screen on both my test M9 and my own M9. I keep my test M9 system partition unwritable to ease taking OTA's on the device, but my own M9 runs Fluent.

hgoldner said:
Why don't you want to bootloader unlock? if you're already S-OFF you can do it in adb shell. Don't hold me to what partitions are fastboot accessible with bootloader locked. I've always had an S-OFF unit with bootloader unlocked. Some partitions aren't writable in fastboot even with bootloader unlocked, although they can be flashed by aboot with an appropriate zip file. For instance, I have a custom splash screen on both my test M9 and my own M9. I keep my test M9 system partition unwritable to ease taking OTA's on the device, but my own M9 runs Fluent.
Click to expand...
Click to collapse
It's not that I don't want to unlock. I'm just insatiably curious as to how things now work with HTCs. (Last HTC I owned was 5 years ago.)
Sent from my Nexus 5 using Tapatalk

efrant said:
It's not that I don't want to unlock. I'm just insatiably curious as to how things now work with HTCs. (Last HTC I owned was 5 years ago.)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The M9 is very different from any prior HTC handset. Instead of an hboot which contains fastboot access, it uses an aboot which is very limited in what it can do, that leads to either a "download" mode or a "recovery mode." Only download mode supports fastboot, and only for some partitions. Some things, like splash screens, can only be flashed in aboot from a properly compiled zip file. Some things can only be flashed in download mode via fastboot. I don't believe \system can ever be flashed on an M9, only altered in recovery or via a rooted system (actually, it can if you are installing a fresh custom ROM). And I believe more changes are afoot in HTC handsets in that regard.
With my M8, Rezound and Incredible, you unlocked bootloader and you got S-OFF. Okay, it was a little more complicated on the Rezound because of that infernal "wire trick," but still, you could fastboot write to any partition once you unlocked bootloader and were S-OFF. That is decidedly different on the M9, and the Verizon variant is locked down even tighter.

hgoldner said:
If I am not mistaken, you won't have fastboot access to \system or \sp1 (splash screen) without bootloader unlock, but you CAN have access to \system within a ROM if you are rooted, even if the bootloader is locked.
Click to expand...
Click to collapse
System part is the other way around while locked on this phone.
Write protected in os ....accessible via twrp.
Boot loader lock flag controls system rw on this phone. On the m8 it was the s flag.
Sent from my Nexus 6 using Tapatalk

Related

[Q] rumrunner / s-off without a working OS

It's been awhile since I've messed around with Android bootloaders, but my buddy just came to me with a seemingly fried HTC One that has been stock since it was purchased. I'm trying to help him out.
We can get to the bootloader, but that is it. No OS will load, and the factory reset option does nothing. I read up on unlocking the bootloader via HTCDev, but as I'm sure you're all aware, that no longer works (MID Error 160) due to Verizon patching the exploit.
I discovered the following XDA development thread: http://forum.xda-developers.com/showthread.php?t=2473644 , but I am not allowed to post on that thread because I don't have enough posts!
It's a little bit over my head, as I'm not familiar with the rumrunner / s-off process. However, it seems that I will need to follow those steps if I want to unlock the bootloader with the hope of flashing a ROM and resurrecting the phone.
My question is this: with the current state of this phone not being able to load any OS / ROM, and having a locked bootloader, is there any possibility I can unlock the bootloader and get a ROM flashed? Is it possible I'm overthinking this? Is there a way to simply flash the stock ROM again since that is seemingly nowhere to be found? Or is this phone simply bricked? Since I can get to the bootloader, I would imagine there is some light at the end of the tunnel.
Thanks for any help you guys can give. If someone wants to offer their assistance to me directly and take the issue off the message boards, I'll gladly PayPal you 20 USD if you have a solution!
Hope everyone is having a Happy New Year.
Just to clarify, the bootloader is locked and I have S-ON.
It seems I am in a bind, because I cannot flash any stock ROM or recovery with a locked bootloader. And I cannot unlock my bootloader because Verizon has blocked the standard exploit using HTCDev.
Hey buddy, what you need is a signed ruu which is the factory version of the os that comes with the phone. The signed part means that you can flash it with locked bootloader. Here Ya go
http://forum.xda-developers.com/showthread.php?p=46506621
Just ask me if you have any questions. You will need to have the htc drivers and fastboot and adb installed of course.
Would that work if I wanted to return to 4.2 from 4.3, locked and s-on? I was too nieve and took the 4.3 update
Sent from my HTC6500LVW using xda app-developers app
tdwpkidd said:
Would that work if I wanted to return to 4.2 from 4.3, locked and s-on? I was too nieve and took the 4.3 update
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Haha I wish.
Chilidog said:
Hey buddy, what you need is a signed ruu which is the factory version of the os that comes with the phone. The signed part means that you can flash it with locked bootloader. Here Ya go
http://forum.xda-developers.com/showthread.php?p=46506621
Just ask me if you have any questions. You will need to have the htc drivers and fastboot and adb installed of course.
Click to expand...
Click to collapse
Thanks so much for your reply. I've got the HTC drivers and the Android SDK loaded, and I used the fastboot tool when trying to unlock the boot loader using HTCDev.
Just to clarify, am I simply looking to download the signed RUU at the bottom of the second paper in that thread? Then flash it? Is that all? A lot of the other instructions in that thread seem irrelevant to my situation. If you could just point me in the right direction as to what I need to do with that RUU file, I'd appreciate it.
jmattia said:
Thanks so much for your reply. I've got the HTC drivers and the Android SDK loaded, and I used the fastboot tool when trying to unlock the boot loader using HTCDev.
Just to clarify, am I simply looking to download the signed RUU at the bottom of the second paper in that thread? Then flash it? Is that all? A lot of the other instructions in that thread seem irrelevant to my situation. If you could just point me in the right direction as to what I need to do with that RUU file, I'd appreciate it.
Click to expand...
Click to collapse
If you took the 4.3 update you will need the 4.3 ruu which I haven't seen yet....so if locked and s-on you are screwed. Now depending on how far they took the flashing and since you say its a sprint phone you might be able to HTC Dev unlock and at least get something booted until s-off is achieved on 4.3.
Sent from my Nexus 7 using Tapatalk
@jmattia Check your PM.

Selling / trading in an S-off phone

I am looking to sell or trade in my m8 (with mazuma mobile, envirophone) etc, however, even though I have reinstalled stock unrooted software and recovery etc, I still get a message when I am setting up the phone that it is a "test device".
Does anyone know how I can get this of this? If not, will it cause any issues during the trade in process?
My device is officially unlocked via htc, and s-off via sunshine.
Cheers
Stewart
Sent from my LG-H815 using Tapatalk
There is a process to return s on then relock bootloader, however, why? I'd rather buy a phone in your state anyway.. Most people on swappa would too I think
Sent from my HTC One_M8 using Tapatalk
yea swappa makes more sense unless you need the money fast from the trade in/sell
I would tend to agree. S-off is getting harder as time goes on. Leave it S-off and maybe just relock the bootloader. If the buyer is into ROMs, they will appreciate how easy it will be to unlock the bootloader. If they aren't, they will never notice it is S-off.
Ok, thanks, so how would I go about re locking the boot Loader?
Sent from my iPad using Tapatalk
StuMcBill said:
Ok, thanks, so how would I go about re locking the boot Loader?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2708571
Since you are S-off, you can actually lock, rather than "relock".
Hey StuMcBill,
Please share more details about your M8. And your terms/preferences for an exchange.

Brand New M8 Shipped with S-OFF

I got my HTC One M8 about a month or more ago switching from my Xperia Z2, and of course, the first thing I had to do with it was root it. Since I had to unlock the bootloader first, I went into bootloader mode and saw the info on the top of the screen. As expected, it says LOCKED, but the funny thing is, it says S-OFF instead of S-ON. Is there any way that this can happen to brand new phones? How can I make sure I am S-OFF, other than going into bootloader mode? I want to convert my phone to GPE but don't want to brick it in the process. Thanks :good:
Schwaggmeister said:
I got my HTC One M8 about a month or more ago switching from my Xperia Z2, and of course, the first thing I had to do with it was root it. Since I had to unlock the bootloader first, I went into bootloader mode and saw the info on the top of the screen. As expected, it says LOCKED, but the funny thing is, it says S-OFF instead of S-ON. Is there any way that this can happen to brand new phones? How can I make sure I am S-OFF, other than going into bootloader mode? I want to convert my phone to GPE but don't want to brick it in the process. Thanks :good:
Click to expand...
Click to collapse
You got lucky, I traded in my m8 for the nexus 6 and left it s-off for the next person that gets it ^^
If it says S-OFF in bootloader you are indeed S-OFF. There's an adb shell/terminal command to unlock the bootloader if you don't want to go through htcdev, although htcdev is safer. But either way, once you bootloader unlock you can convert to gpe if you want or whatever you wanna do.
Sent from my Nexus 6 using Tapatalk
I wonder if the phone was returned the point of sale, repackaged, and shipped to you? Perhaps the previous owner relocked the bootloader but left the phone S-OFF.
HolyAngel said:
You got lucky, I traded in my m8 for the nexus 6 and left it s-off for the next person that gets it ^^
If it says S-OFF in bootloader you are indeed S-OFF. There's an adb shell/terminal command to unlock the bootloader if you don't want to go through htcdev, although htcdev is safer. But either way, once you bootloader unlock you can convert to gpe if you want or whatever you wanna do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah, I already unlocked bootloader, rooted a long time ago, but I'm not sure if this phone is brand new because it did come with the wrapping around it and not a scuf or scratch was found on the phone, however the sticker sealing the box was already cut, but I presume it's just my uncle checking that all the parts are there because he was the one who got the phone for me since he works at a pretty big shop where they sell phones . Either way, thanks, also great ROMs you're doing for the M8 :good:
WorldIRC said:
I wonder if the phone was returned the point of sale, repackaged, and shipped to you? Perhaps the previous owner relocked the bootloader but left the phone S-OFF.
Click to expand...
Click to collapse
Bootloader wasn't relocked. If it was it would say **RELOCKED**, but mines said **LOCKED**.
Schwaggmeister said:
Bootloader wasn't relocked. If it was it would say **RELOCKED**, but mines said **LOCKED**.
Click to expand...
Click to collapse
It is very easy to make it say "locked" instead of "relocked" since the device has S-OFF.
Schwaggmeister said:
Is there any way that this can happen to brand new phones?
Click to expand...
Click to collapse
Yes, I've seen reports of this happening from time to time. It pretty rare, but it does happen.

Problems with Bootloader unlock

I have a Verizon M9 running 2.6.605.15. I have a clip, and was able to S-Off the device with MUCH help from the xtc2clip people. For the life of me I cannot unlock the bootloader on this device. Every time I run the clip I get a communications error 3, and even the xtc2clip people have never seen it happen. So I'm stuck at this point. Anyone have this issue with the clip, or not being able to unlock the bootloader? Any help would be appreciated!
If you've s-off'd the device already, you won't use the clip to unlock the bootloader, this can be done with adb commands.
See this thread: http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
Fix for bootloader problem
PrizmaticSmoke said:
If you've s-off'd the device already, you won't use the clip to unlock the bootloader, this can be done with adb commands.
See this thread: http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
Click to expand...
Click to collapse
I let the updates go through before I Tried to unlock the bootloader, and it wouldn't kick out the block of numbers to paste into the htcdev site. So I RUU'd back to the starting rom, and it worked fine. IDK if that helps.
SigLover21 said:
I let the updates go through before I Tried to unlock the bootloader, and it wouldn't kick out the block of numbers to paste into the htcdev site. So I RUU'd back to the starting rom, and it worked fine. IDK if that helps.
Click to expand...
Click to collapse
Why on earth would you do HTC Dev and effectively notify HTC you are s-off and now unlocked when you could have simply unlocked and never had to wipe?
Sent from my Nexus 6 using Tapatalk
That worked perfectly, thanks! I thought it had to be easy....

Finally upgrading to Nougat... running into some odd problems.

I simply want to upgrade to 7. I had put it off before the holidays, and now I finally can sit down and do this.
First, I have a SIM-unlocked US HTC 10, on build 1.96.617.2. I am currently S-off, with a locked bootloader, rooted, etc.
The first thing that perplexed me was that I couldn't boot into bootloader (or anything) from ADB. It just rebooted to the OS. I thought maybe I needed to quickly flash the old TWRP (for MM), but then I recalled I had locked my bootloader when I did S-off 5 months ago.
So my first question... is there a way to unlock bootloader without going through all the brain damage through HTC? WIth the HTC One (M8), someone had figured out you could get an ADB shell, get su, then enter:
Code:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
I would never presume that this would work on the 10 as the partitions are likely different..
SO my first question is whether anyone knows if there is a simple way to unlock the bootloader without going through HTC and getting the token, etc.?
Secondly, I think to avoid all possible problems, I am just going to back up internal storage and run the RUU 2.28.617.8 (exe) to upgrade (will flash custom roms after this). Since I am S-off, I know that after I upgrade, I can just flash the new TWRP (3.03 Unoffficial) that Captain Throwback, nkk71 and others worked very hard to create. However, what I am completely new and unfamiliar with is attaining root...
I know it will sound strange, but I have no idea what Magisk is (well I understand what it does roughly), but from some threads I have read that only a systemless root is attainable, and other places I have seen that dm_verity needs to be disabled in the kernel ramdisk. I have only used SuperSu since 2011, and I feel a bit befuddled. I thought Chainfire created a new SuperSu for that disabled dm_verity... However, I see that some do not use SuperSu... Can someone give me some advice on the differences (if there are any) between using Magisk (and phh?) or SuperSu to manage root?
Thank you very much in advance!!!
Syntropic
EDIT: Addendum question... I am on TMO. Would it be wiser to flash the recent TMO nougat RUU on my Sim-Unlocked HTC 10??
[Note: I asked this question a few weeks ago...but as I couldn't upgrade before the holidays, I wanted to ask again just to be sure.]
OK... I need some help. please.
Well.... I unlocked the bootloader with my old unlock_code.bin which was obviously stupid because I didn't realize that I needed a locked bootloader to run the RUU. I cannot lock the RUU because I don't know the encryption password.... (I know my screen pattern but that is it).
Just to confirm, I started to run the RUU, but it is prompting me with ERROR[170] USB Connection ERROR. But the USB connection was working fine 10 minutes ago. I am therefore assuming this is because my bootloader is now unlocked. Howver I do not know how to relock the bootloader from TWRP. But it seems odd because I am s-off...so can someone confirm that this is actually what the problem is??
I opted to upgrade using the RUU.exe because I thought it would cause the least amount of potential problems—PLUS I figured that since I was sacrificing all my data anyway, why would I need to know passwords for encryption???
Can someone assist me? I am a bit over my head... However, I have both RUU exe and zip files, and have decrypted them to get firmware and boot images.
Further, if someone does respond to this, I would also really appreciate what I need to do after flashing the new TWRP... I thought this would really be my only question... (see first post), but I seemed to have forgotten everything about rooting this phone the first time.
Again, I would really appreciate instructions on how to solve this problem... I have everything backed up... So I just want to run this RUU (and then root it after I flash TWRP).
Thank you in advance!!!!!!
Thank you
syntropic said:
OK... I need some help. please.
Well.... I unlocked the bootloader with my old unlock_code.bin which was obviously stupid because I didn't realize that I needed a locked bootloader to run the RUU. I cannot lock the RUU because I don't know the encryption password.... (I know my screen pattern but that is it).
Just to confirm, I started to run the RUU, but it is prompting me with ERROR[170] USB Connection ERROR. But the USB connection was working fine 10 minutes ago. I am therefore assuming this is because my bootloader is now unlocked. Howver I do not know how to relock the bootloader from TWRP. But it seems odd because I am s-off...so can someone confirm that this is actually what the problem is??
I opted to upgrade using the RUU.exe because I thought it would cause the least amount of potential problems—PLUS I figured that since I was sacrificing all my data anyway, why would I need to know passwords for encryption???
Can someone assist me? I am a bit over my head... However, I have both RUU exe and zip files, and have decrypted them to get firmware and boot images.
Further, if someone does respond to this, I would also really appreciate what I need to do after flashing the new TWRP... I thought this would really be my only question... (see first post), but I seemed to have forgotten everything about rooting this phone the first time.
Again, I would really appreciate instructions on how to solve this problem... I have everything backed up... So I just want to run this RUU (and then root it after I flash TWRP).
Thank you in advance!!!!!!
Thank you
Click to expand...
Click to collapse
I'm not really sure what went wrong in your sequence of events but since you're s-off I think you should be able to flash that ruu.
In either case have you tried running an ruu zip from your sd card instead of using the ruu.exe?
You're s-off? But you have a locked bootloader? I've never heard of that being possible. On your DM screen it says s-off and it says locked? I've heard of people bricking their pixels by unlocking the bootloader, locking it and trying too unlock again.
GutterParrot said:
You're s-off? But you have a locked bootloader? I've never heard of that being possible. On your DM screen it says s-off and it says locked? I've heard of people bricking their pixels by unlocking the bootloader, locking it and trying too unlock again.
Click to expand...
Click to collapse
It's a sunshine feature.
After successful s-off it sets bootloader back to locked. It's easier to go back to stock.
I don't understand why to tried to unlock your HTC 10? With s-off it doesn't matter if the bootloader is locked or unlocked.
Maybe you should try the RUU.zip variant. After that flash TWRP and SuperSu.
Sent from my HTC 10 using XDA Labs

Categories

Resources