Related
http://www.htcdev.com/bootloader/
Select the Option "All other Supported Models" and follow the instructions.
After this process, your device show "*** UNLOCKED ***" and "SHIP S-ON"
blubbers said:
http://www.htcdev.com/bootloader/
Select the Option "All other Supported Models" and follow the instructions.
After this process, your device show "*** UNLOCKED ***" and "SHIP S-ON"
Click to expand...
Click to collapse
...better wait for a time like revolutionary for a real S-OFF method.
Wonder how people can to this htc unclock without worries about their warranty.
I will wait for Revolutionary personally. More flexibility to flash radios, hboots, etc.
EDIT: And kernels (boot.img)
Confirmed. Unlock works.
SHIP S-OFF RL
I understand that unlocking your device via htcdev.com will irreversibly void your warranty, but is that also the case, if I unlock my device with the stuff from the revolutionary team ?
I never had a device, which could be unlocked that way. My first two android phones were Motorolas and they could always be converted back to stock, for sending them in for repairing or for selling them.
thedoginthewok said:
I understand that unlocking your device via htcdev.com will irreversibly void your warranty, but is that also the case, if I unlock my device with the stuff from the revolutionary team ?
I never had a device, which could be unlocked that way. My first two android phones were Motorolas and they could always be converted back to stock, for sending them in for repairing or for selling them.
Click to expand...
Click to collapse
You probably can still revert completely back to stock, the point is that if you use htcdev.com they've got a record of the phone being unlocked (even if you return it to stock again), whereas if you do it yourself then revert it they wouldn't know it had been unlocked in the first place.
That sounds great, thank you.
Thank you !
Like the other I prefer another method...
i will also wait for revolutionary^^
luckily there is temp root so i can delete the crap i dont use
cant wait for it to come so i can flash the first coredroid beta on it^^
Temp Root isnt working...
If we use the htcdev.com or revolutionary HTC will find out that the phone was unlocked!
moom999 said:
If we use the htcdev.com or revolutionary HTC will find out that the phone was unlocked!
Click to expand...
Click to collapse
No. Revolutionary is reversible. But htcdev does keep a record forever. However, that doesn't screw you out of every single warranty like many think. Only a small number of software issues, otherwise you still have warranty. We will see how long many of you will wait for revolutionary before you cave in and unlock through htcdev lol. All of us vivid users never got anything other than htcdev unlock. All the devs working on s off told us that HTC made it a hell of a lot harder to crack the newer phones.
Sent from my HTC PH39100 using xda premium
About htcdev unlock. They log your imei and serial number, yes. BUT the only thing you'll get after that is the posibility to unlock your device. Once we get Revolutionary s-off and then the ability to s-on again, how will they know if you really used the possibility to unlock your device? There's a final warning so no evidence you finally used it
Hopefully revolutionary team may be able to use the htc unlock method
Any way I just unlock it now using htcdev
Because I want it to try the temp-root to see if it will work with unlocked but did not work.
As I understood with unlocking using htcdev I still have the warranty for the hardware or I just lost all the warranty?
So just confirming that the htcdev unlock does not let the temp root work?
slapshot30 said:
No. Revolutionary is reversible. But htcdev does keep a record forever. However, that doesn't screw you out of every single warranty like many think. Only a small number of software issues, otherwise you still have warranty. We will see how long many of you will wait for revolutionary before you cave in and unlock through htcdev lol. All of us vivid users never got anything other than htcdev unlock. All the devs working on s off told us that HTC made it a hell of a lot harder to crack the newer phones.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Being on the rezound I agree. And also the fact that before my rezound I sent back a dinc2 completed rooted because of hardware problems and had no issues.
Sent from my ADR6425LVW using xda premium
robt772000 said:
So just confirming that the htcdev unlock does not let the temp root work?
Click to expand...
Click to collapse
Yes, confirmed
moom999 said:
As I understood with unlocking using htcdev I still have the warranty for the hardware or I just lost all the warranty?
Click to expand...
Click to collapse
That's right, you still got most of your warranty intact..
HTCDEV.com said:
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
Click to expand...
Click to collapse
So; in some cases, not all, where the damage is caused by unlocking warranty will not be valid.
if the temp root doesnt work after the htcdev unlock why would you then wanna use it and tell them what you did^^
I've got permaroot working with an unlock by htcdev. Wai for mike to update his thread
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.
Hi.
Today I tried to root my HTC One M8 and found the HTC One Toolkit [M8] (actual version)
So I installed the driver of ADB and and HTC.
But if I click on HTC Dev Unlock I get the message "HTC One Toolkit [M8]"
I use Android 4.4.3 and USB-Debugging is on.
Can anyone help me?
Whity0815 said:
Hi.
Today I tried to root my HTC One M8 and found the HTC One Toolkit [M8] (actual version)
So I installed the driver of ADB and and HTC.
But if I click on HTC Dev Unlock I get the message "HTC One Toolkit [M8]"
I use Android 4.4.3 and USB-Debugging is on.
Can anyone help me?
Click to expand...
Click to collapse
No offense against the guys that write these toolkits to make it "easier" but, stay away from it if you can, you don't really learn anything by using these toolkits.
That said,
Try and unlock the bootloader manually, as shown once when you sign up to htcdev.com and follow their instructions to get bootloader unlocked. OR
You can go for Sunshine S-OFF ($25) it roots, unlocks bootloader and gives S-OFF all-in-one.
http://theroot.ninja/
Sunshine Thread on xda
BerndM14 said:
No offense against the guys that write these toolkits to make it "easier" but, stay away from it if you can, you don't really learn anything by using these toolkits.
That said,
Try and unlock the bootloader manually, as shown once when you sign up to htcdev.com and follow their instructions to get bootloader unlocked. OR
You can go for Sunshine S-OFF ($25) it roots, unlocks bootloader and gives S-OFF all-in-one.
http://theroot.ninja/
Sunshine Thread on xda
Click to expand...
Click to collapse
It technically only temp-roots. You still have to fully root using a custom recovery or adb push. However, once the bootloader is unlocked, that is fairly simple.
I would actually suggest that as an upgrade, though. It would be nice if, at the tail end of the process, Sunshine would offer to permanently root the phone.
Hi.
Now I unlocked the bootloader manually and installed twrp as custom recovery. After this I installed SuperSU over twrp to get root.
*//
All works fine, but I have a little problem.
Now i cant take screenshots. If I try, I get the message that no screenshot can be taken because the app can´t save them.
Does anyone have some ideas how I can fix it?
//*
Fixed "Created a folder called screenshot1 and delete the other screenshot folder. Once it is deleted remove the "1" so it still only Screenshot."
Additionally, I want to make the SD-Card writeable for all apps, has someone a link to tutorial?
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.
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