[Q] Stock everything but S-OFF. Still under warranty? - One (M8) Q&A, Help & Troubleshooting

No joke I was sitting on my computer desk with my phone in front of me and I hear a sharp "DINK" and look down and saw my phone was cracked. Needless to say I was rather upset because I treat this phone very well.
I found there is a free one time screen replacement and I sent in for that but if the phone is root at all they will not fix it without charging you the full price even though root has nothing to do with the damn screen cracking.
I have gone back to full stock img and bootloader but want to keep S-OFF as other have recommended they keep it that way.
Does anyone know if S-OFF voids my warranty?

murf43143 said:
No joke I was sitting on my computer desk with my phone in front of me and I hear a sharp "DINK" and look down and saw my phone was cracked. Needless to say I was rather upset because I treat this phone very well.
I found there is a free one time screen replacement and I sent in for that but if the phone is root at all they will not fix it without charging you the full price even though root has nothing to do with the damn screen cracking.
I have gone back to full stock img and bootloader but want to keep S-OFF as other have recommended they keep it that way.
Does anyone know if S-OFF voids my warranty?
Click to expand...
Click to collapse
I'm from europe and s-off didn't void my warranty. Go back to stock and leave it s-off. Just lock bootloader...

Onem8 said:
I'm from europe and s-off didn't void my warranty. Go back to stock and leave it s-off. Just lock bootloader...
Click to expand...
Click to collapse
So you are recommending to flash the "recovery.img" and then lock the bootloader using ADB?
Or would you recommend trying to find the full firmware for sprint and flashing that and then locking the bootloader and uninstalling SuperSU?
Thank you,

murf43143 said:
So you are recommending to flash the "recovery.img" and then lock the bootloader using ADB?
Or would you recommend trying to find the full firmware for sprint and flashing that and then locking the bootloader and uninstalling SuperSU?
Thank you,
Click to expand...
Click to collapse
Origenal firmware, stock recovery, stock rom, no supercid but your region cid. Everything Stock and then lock your bootloader, after that uninstall superSU.
Lock bootloader : http://forum.xda-developers.com/showthread.php?t=2708571
Writecid : http://forum.xda-developers.com/showthread.php?t=2317536

Related

[Q] gf's htc one x screen has gone yellow

Hello, as above really, her screen has a yellow streak advertise the charger edge of screen.
3 mobile have offered to look at it and/or replace it.
Is flashing the factory 3uk ruu sufficient ??? Its rooted cos she hated the default software.
Thanks for any advice.
Yes, flashing the ruu would take the phone back to full stock. However, after relocking the bootloader, the bootloader will say ***Relocked*** So chances of warranty being void are still there!
Well lets hope for the best! Just make sure you run the correct RUU!
vin4yak said:
Yes, flashing the ruu would take the phone back to full stock. However, after relocking the bootloader, the bootloader will say ***Relocked*** So chances of warranty being void are still there!
Well lets hope for the best! Just make sure you run the correct RUU!
Click to expand...
Click to collapse
Thanks mate

[Q] Urgent Need to revert back to stock for warranty service

Ok so I have installed arhd and want to revert back to stock for warranty service
I made a Nandroid backup before unlocking the bootloader
Please guide me through the process
specs:-
cid-11111111
hboot-1.36
s-off
U can't get completely to stock. You have to install your main version RUU after locking the bootloader, but u will face the problem where the bootloader says 'relocked' instead of 'locked'
Sent from my HTC One X using xda premium
So will I be able to get warranty service or not
I don't think so dude.
Sent from my HTC One X using xda premium
Can anyone else confirm this fact?
You can easily return to stock and run any ruu because you have s-off
with s-off you can also LOCK the bootloader instead of relocked, so lock it and send it for warranty
Depends on what is the problem with Your HOX. If they need to replace Your motherboard then You gonna pay for it. HTC official policy... I'm from Poland and I sent it for repair 3 times. Everytime they needed to replace motherboard. And they did it two times even with relocked bootloader (don't know why, maybe they always repair phones with broken autorotation? common issue with hox. coz it was the case with first and second repair). 3rd time I got problem with screen backlight and bang - ~$300 . I tried contacting with HTC Poland and HTC Taiwan but same answer. If bootloader was unlocked and motherboard needs to be replaced You need to pay for it. Any other issue with any other part and they fix it for free. So hard to tell really. You may be lucky What is Your issue with HOX? You may also consider burning down the motherboard... They will not be able to tell if You had bootloader unlocked... But it's kinda cheating... I just read somewhere that some dude did it and they replaced his motherboard for free
Stefan0vic said:
You can easily return to stock and run any ruu because you have s-off
with s-off you can also LOCK the bootloader instead of relocked, so lock it and send it for warranty
Click to expand...
Click to collapse
These are good news, am thinking of selling my phone and getting s-off HOX.
Sent from my HTC One X using xda premium
Stefan0vic said:
You can easily return to stock and run any ruu because you have s-off
with s-off you can also LOCK the bootloader instead of relocked, so lock it and send it for warranty
Click to expand...
Click to collapse
Can you explain how to lock bootloader
I have a nandroid backup can I use that for restoring my phone
Please explain
Thanks for everyone that helped really appreciate all replies
And I just realized that putting "urgent" in my title of the thread does not mean that my question is more important than others
Any help will be appreciated
An s-off hox also can show relocked only.

T-mobile M8 best method to prepare for warranty exchange

I posted this over in the T-Mobile M8 forums but didn't get any answers. Since the T-Mobile forums don't get much attention, I figured I would try over here in the M8 general forums...
I've got the fuzzy lens problem and I want to get the phone replaced (preferably via T-Mobile but I'll go directly to HTC if I have to). I know you can scratch off the coating on the lens and get some camera improvement but I'm not interested in that solution.
My goal: Return the phone to completely stock condition. No root, locked bootloader and preferably S-ON. I've read a few stories where HTC insisted on replacing the motherboard (with an additional full price fee) because the device was S-OFF and I don't want to go there.
Background: I used firewater to S-off the phone as soon as I got it (it was running 1.12 at the time). I have flashed the Harmon Kardon audio stuff (http://forum.xda-developers.com/showthread.php?t=2737498). I have turned off the tamper flag (http://forum.xda-developers.com/showthread.php?t=2708565). I am running the Stock+ rom which is based on 1.57 (http://forum.xda-developers.com/showthread.php?t=2716843).
My plan:
1) Reset my bootloader to locked (http://forum.xda-developers.com/showthread.php?t=2708571)
2) Wipe the phone and restore my very first nandroid backup I made with TWRP. That will get me back to unrooted 1.12 firmware but without the stock bootloader and still S-OFF. Staying with 1.12 will allow me to S-OFF again with firewater if it comes to that. If some kind of emergency came up, I'd hate to spend $25 on sunshine for a one time use on a phone that is going back to HTC forever.
3) Install the stock bootloader that matches 1.12 firmware. Not sure how to do this yet. I'm afraid I won't be able to achieve this with a locked bootloader and no root.
4) Verify everything is back to stock.
5) Set the phone back to S-ON (http://forum.xda-developers.com/showthread.php?t=2758818)
6) Run the 1.57 RUU (http://forum.xda-developers.com/showthread.php?t=2714456)
7) Proceed with the warranty exchange.
I'm not sure running the RUU is 100% necessary, but I figure it's the best bet I have to make the phone completely stock.
Questions: Is this a sane plan? Am I doing anything in the wrong order? Are there any steps that won't work because I've lost root or unlocked bootloader? Am I setting myself up for a brick anywhere?
There is a thread about doing this on a EU M8 (http://forum.xda-developers.com/showthread.php?t=2735235) but I can't tell what, if any, modifications need to be done for the USA T-Mobile version of the M8. There is talk about having to flash a firmware file twice or risk a hard brick when setting S-ON. Do I need to be worried about any of that?
Generally, when you lock bootloader, it says relocked, so they can tell. Maybe reflashing bootloader will work
Sent from my HTC One V using XDA Free mobile app
tzzeri said:
Generally, when you lock bootloader, it says relocked, so they can tell. Maybe reflashing bootloader will work
Click to expand...
Click to collapse
Thanks for the reply. This thread (http://forum.xda-developers.com/showthread.php?t=2708571) appears to give a way to avoid the relocked indicator and shows the proper "locked" text in the screenshot, so I think I am good there.
Any other advice?
I had a similar problem, only I did remove the coating. I wasn't rooted though, haven't seen the need to do so YET. I went into the store and showed the rep there what the problem was, mine wouldn't focus at all anymore. And they sent me a "new" (read refurbished) device, while I held on to mine. I was at the 4 month mark of having the phone and I didn't have insurance on it. No hoop jumping for me at all. If this happens again anytime soon I might have to fight to switch to a different phone. This is just ridiculous. I love the phone but the camera problems are insane for the price of this device. I also told them the problems popped up after I upgraded to 4.4.3 which they did but that's probably just a coincidence.
Sent from my HTC One_M8 using XDA Free mobile app
Gargamel1 said:
I had a similar problem, only I did remove the coating. I wasn't rooted though, haven't seen the need to do so YET. I went into the store and showed the rep there what the problem was, mine wouldn't focus at all anymore. And they sent me a "new" (read refurbished) device, while I held on to mine. I was at the 4 month mark of having the phone and I didn't have insurance on it. No hoop jumping for me at all. If this happens again anytime soon I might have to fight to switch to a different phone. This is just ridiculous. I love the phone but the camera problems are insane for the price of this device. I also told them the problems popped up after I upgraded to 4.4.3 which they did but that's probably just a coincidence.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Wait, you removed the coating and then went into t-mobile? I would think they would say no to a warranty exchange since you tried to do it yourself first. Get rid of the coating that is.
Sent from my HTC One_M8 using Tapatalk
I thought so also but figured it was worth a try. I did a pretty decent job removing it, and unless the person is fully aware of the issue and some of the diy fixes they won't notice.
Sent from my HTC One_M8 using XDA Free mobile app
Success
UPDATE: T-Mobile gave me a warranty replacement to fix the camera lens problem. I did get the old phone back to completely stock with locked bootloader and S-on before sending it back.
I found it was easiest to use the sunshine installer to gain temp root. You don't need to pay anything since you stop before it goes through the whole S-Off process. Just run the APK and select temp root. When sunshine shows you the next screen, you can exit out and still have root. (http://theroot.ninja/)
In the end I didn't bother with the old nandroid and keeping the exploitable version. I also had the order messed up in my initial post. Here is what worked for me:
1) factory reset the phone (in TWRP I did advanced wipe and also wiped internal storage). This step kills root. Rebooted the phone and verified it was back to factory defaults. Go through the setup wizard and skip all the steps. I couldn't find a way to bail out without going through every step in the wizard.
2) flashed stock recovery (the bootloader was unlocked and the phone was S-Off). Root is not necessary for this since it is done in fastboot. (http://forum.xda-developers.com/tmo...l/ota-recovery-ruus-firmware-dumps-t-t2852107). Rebooted the phone.
3) achieved temp root using sunshine APK
4) locked the bootloader (required before running the RUU). You must have root since you need a SU # prompt in the shell. (http://forum.xda-developers.com/showthread.php?t=2708571). I rebooted again for good measure but it's probably not necessary.
5) reset the phone back to completely stock using the latest 2.22.531.5 RUU. This step does not require root. I found it was easiest to put the phone into fastboot mode before running the RUU. (http://www.htcdev.com/devcenter/downloads)
6) Once the phone booted back up, I looked over everything and made sure it is all completely stock. Checked HBOOT said locked (not relocked) and dis not say tampered.
7) OPTIONAL - set S-On. Again root is not required since this is a fastboot command. (http://forum.xda-developers.com/showpost.php?p=52823014&postcount=2)
My actual process wasn't this streamlined. I ended up doing the RUU a couple of times because I didn't flash the stock recovery first and I didn't think the RUU installed the stock recovery right. Turned out I just didn't know what the stock recovery looked like (it was very confusing since I had never actually used a HTC stock recovery).
Thanks to the authors of the various threads I pulled info from. They are the real MVP's.

Locking Bootloader

hi,
i have to return my phone guarantee because the speaker and jack input doesnt work.
i have already unroot device, flash stock recovery, (i was all the time s-on), flash stock rom and trying to lock bootloader but i cant make it LOCKED (it's RELOCKED). i was looking for any "how to" but im blind ...
can anyone help with making my bootloader LOCKED ?
pangapz said:
hi,
i have to return my phone guarantee because the speaker and jack input doesnt work.
i have already unroot device, flash stock recovery, (i was all the time s-on), flash stock rom and trying to lock bootloader but i cant make it LOCKED (it's RELOCKED). i was looking for any "how to" but im blind ...
can anyone help with making my bootloader LOCKED ?
Click to expand...
Click to collapse
are you s off?
no, im sON
Only way to put it back totally stock is to be S-off.
Magnum_Enforcer said:
Only way to put it back totally stock is to be S-off.
Click to expand...
Click to collapse
yeah, i dont even think about paying 25$ to s-off...
and i have one more problem: i got "Software status : Modified", i want it Official (Original), do i need s-off to make it ?
i was searching some threads and i found that flashing RUU can solve this problem but i can find RUU from my carrier (Plus, Poland)
Just a thought... 25 dollars to s-off could save you getting charged for your repair if they see you're "relocked" and deny your warranty. ?
Darth said:
Just a thought... 25 dollars to s-off could save you getting charged for your repair if they see you're "relocked" and deny your warranty.
Click to expand...
Click to collapse
i know but its a "mechanical" issue not the software so they should reapir it even bootloader is unlocked ;P but i want be sure they'll do it without any problems
is possible to make Software Status : Official from Modified ?
(S-ON)
Is 25$ s-off way , can be use multiply on my device ?
You'll need S-OFF to completely return to stock with no tampering signs.... But, if they don't send you back your same device , you would need to purchase Sunshine again unfortunately. Or stay s-on.
Sunshine license is for one device only.
If they send same unit back, yes, it will work again.
But switching back to s-on is really not necessary when you send it in. I've sent mine in with s-off and many others have without issue. But that's your call. ?

To clip, or not to clip...have some questions

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

Categories

Resources