Database Users

[Q] Can someone please explain the rooting on this phone to me?

I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.

The K-Zoo Kid said:
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
Click to expand...
Click to collapse
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.

unremarked said:
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
Click to expand...
Click to collapse
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.

The K-Zoo Kid said:
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
Click to expand...
Click to collapse
unlocking the bootloader and rooting are two different things

jblade1000 said:
unlocking the bootloader and rooting are two different things
Click to expand...
Click to collapse
Ahh i have no idea what unlocking the bootloader does then.

The K-Zoo Kid said:
Ahh i have no idea what unlocking the bootloader does then.
Click to expand...
Click to collapse
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.

unremarked said:
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
Click to expand...
Click to collapse
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?

The K-Zoo Kid said:
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
Click to expand...
Click to collapse
Yes, to mod/flash roms you need to unlock the bootloader. It's possible that sometime down the road someone may develop a method of gaining root access on the phone without touching it, but it's unlikely given the fact that we can both unlock and lock the bootloader very easily.
Right now, the answer is... more or less. If you make a NAND backup in Clockwork Recovery/Rom manager of your stock ROM, you can restore back to that, fastboot flash the closest thing we have currently to the stock recovery(check development section for this), then relock the bootloader. This will give the phone all appearances of being stock. Unless Samsung has something deep in the system files tracking the number of times you've unlocked/locked(which I doubt, since I'm sure such a system would have been found by now), you should be good to go.
Most people who have returned the phone to Best Buy have noted that they don't even power on the device or check to see if the bootloader is unlocked or if there's a custom recovery on there. But your mileage may vary.

Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?

I had clockworkmod installed but used rom manager to flash the 2.3.1 update and i've now got the stock bootloader back. I guess the ota update does the same? It would seem that getting back to stock is pretty easy.
Sent from my Nexus S using XDA App

xspyda said:
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
Click to expand...
Click to collapse
My apologies, I posted that before I came to the same understanding regarding the stock recovery.
Like the poster above me mentioned there is a NAND backup of stock 2.3.1 you could restore to which has the stock recovery.
Sent from my Nexus S using XDA App

Thanks for the clarification. I'll do some more reading in the dev section

Thanks a lot, this really helped me out a lot. I will proceed to rooting

So, just want to make sure I have this straight... You unlock the bootloader, load custom recovery, SU, and now phone is rooted. If you lock the bootloader, you lose root?
For me, I'm not big on custom roms since I just don't have time to keep things up to date or participate in the bug process, but I do like to maintain backups with Titanium (my primary reason for rooting). So by locking the bootloader down I will not be able to use Titanium. Furthermore, unlocking the bootloader wipes the device. So is there a reason one would not want to keep the bootloader unlocked? Have I completely misunderstood the system?

I downgraded from the Official AT&T 2.2 update back to 2.1

I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb

I have done this and can confirm that this works
Thanks mate!

I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.

khaytsus said:
I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.
Click to expand...
Click to collapse
I went back to 2.1 because the 2.2.2 version that AT&T released was extremely slow, and my touchscreen would become unresponsive.

andrewishcool95 said:
I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb
Click to expand...
Click to collapse
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?

Gene Poole said:
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?
Click to expand...
Click to collapse
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.

andrewishcool95 said:
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.
Click to expand...
Click to collapse
I'm also very curious about this.

Sounds like the first steps to rooting and downgrading. I'm curious to see if any developers catch this
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.

Gene Poole said:
I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.
Click to expand...
Click to collapse
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?

FroztIkon said:
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?
Click to expand...
Click to collapse
There may be. When I first got my Aria, the rooting procedure involved an HTC signed update that you fooled the hboot into partially loading, then swapped the sdcard with the root package. It involved some complex timing issues where you had to run adb in a loop and plug/unplug the usb cable at appropriate times.
I've been searching the net for that procedure and I can't seem to find the right search terms, or I'm just not looking in the right places or something, but I know that's how I did my Aria before there was an unrevoked plug-n-root.

I have the procedure u are looking for i think...let me know if this is what u were after because i have an archive of saved documents I have copied from forums in the past...GOOD LUCK!
well apparently i haven't posted enough to put the links up in the post

PM me if you want the process...

xerotix said:
PM me if you want the process...
Click to expand...
Click to collapse
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.

econcep said:
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.
Click to expand...
Click to collapse
That process does not work with the new HBOOT. That's why unrevoked doesn't work. Having root access does not unlock NAND.
Currently, the only way known is via hardware tools.

It works. I managed a work around for 2.2.2 update
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.

econcep said:
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.
Click to expand...
Click to collapse
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272

Gene Poole said:
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272
Click to expand...
Click to collapse
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.

econcep said:
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.
Click to expand...
Click to collapse
Perhaps I misread (or we're talking past each other). You do have, in fact, HBOOT 1.02.0000 on your Aria, and managed to write to the system partition?

Yes & No. I'm stuck on couple of things. First the will temporary give me root access but then it locks up saying I don't have busybox. I'm rooted but no s-off. I also noticed when I reboot into recovery I go into CWM 2.5.0.1 but other times it boots into CWM 2.5.0.7. When that happens I loose my unknown source in settings>application. Again, if this is the wrong thread, I really am sorry.
I googled alpharev and some others who have worked on rooting. Found some cached pages from Jan when they were testing to root/s-off the Aria. Basing my work on that and couple of other devices that are similar to the Aria.

How to Root a HTC one (M8) in 2016 For beginners - (first time posting)

I have just recently started my journey into rooting, I've been in research mode for about a week trying to learn as much as I can but it's SO overwhelming trying to keep up with all the old and new techniques - trying to find out what is the best method to use.
Before discovering this place I asked a few questions on reddit and was able to get a cheat sheet on all the terms one needs for rooting:
https://www.reddit.com/r/androidroo...ingroot_considered_true_rooting_where_is_the/
and while browsing Xda I found this short guide:
http://forum.xda-developers.com/htc-one-m8/help/how-to-root-htc-one-m8-android-6-0-t3420748
However both of theses sets of instructions miss out a few starting points.
I've watched a few videos on how to root a htc but they've all been made around the time of the phones release, and as we all know each year things get bigger and better in computing, so new techniques might have arrived. So I wanted to ask here what are the full sets of instructions to root a htc one m8 in 2016, starting from watch software to use to back up your phone, how to unlock the bootloader, etc... and using whatever new rooms and kernels people have been using and would recommend.
My aim is, with your help, to make this post a place beginners can go to learn how to do their first root. thankyou in advance.
My phone:
service provider: Orange/EE (UK)
Android: 6.0 (Marshmallow I think)
HTC sense version: 7.0
Sofware number: 6.12.61.4

I've just rooted my phone unlocking the bootloader yesterday. I haven't gone S-off yet.
I'm coming from Samsung phones so things are a little different for me too. I followed this guide which covers everything you can and will need to gain full root on an m8
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
to get root apps to have all the ability they have elsewhere you need to cover 3 steps
1) unlock the bootloader, which will make some partitions accessible, but writing to the system partition is still blocked apart from via custom recovery (the phone reboots when you try to write into the system partition without "full root").
2) root. fairly obvious what that is.
3) gain S-off, which makes system partition accessible outside of the custom recovery. the phone can be enjoyed the same as any other rooted device at this stage. **this can only be done one way, and that one single way isn't free.**
you want to have all the stages mentioned in that link covered apart from the last firmware guide which is more optional.

How are you getting S-off that isn't free? I had S-off within a week of owning my phone back when it was new, and I'm on Verizon, they are the devil when it comes to modding anything. Have you looked into Sunshine?

hello guys,im looking forward rooting my m8,is there any method to root my phone without void my warranty?(i mean if i unroot my phone will still be on warranty?)

ieatabiscuit said:
How are you getting S-off that isn't free? I had S-off within a week of owning my phone back when it was new, and I'm on Verizon, they are the devil when it comes to modding anything. Have you looked into Sunshine?
Click to expand...
Click to collapse
the "not free" S-off I'm referring to is sunshine, unless things have changed (if they have I'll be delighted).

3mel said:
the "not free" S-off I'm referring to is sunshine, unless things have changed (if they have I'll be delighted).
Click to expand...
Click to collapse
Just rechecked into it to refresh my memory, as I've been S-off so long I forgot the method I had used. It was in the pre-Sunshine days. I used Firewater to get S-off (thought Sunshine sounded odd to me for some reason). Didn't cost me anything but a couple minutes of my time. Hope that helps. I wouldn't want to pay for S-off either, it's not really something that I think many people would want to do...
---------- Post added at 06:53 AM ---------- Previous post was at 06:47 AM ----------
GreiverX said:
hello guys,im looking forward rooting my m8,is there any method to root my phone without void my warranty?(i mean if i unroot my phone will still be on warranty?)
Click to expand...
Click to collapse
If you have a way to revert it and become S-on again (assuming you're S-off also) I would say you could hide the fact it's been rooted by unrooting and removing any root apps, but don't quote me on that. I rooted back when mine was new, and never looked back at the warranty. Now my phone would have had the warranty expire anyway, so it still doesn't matter. When in doubt, assume the warranty to be void upon rooting, but research a way to revert if it's possible. Not like we have to bother with KNOX at least.

only way is USD $25 for sunshine....can't S-OFF it without other ways.

WingZer0n said:
only way is USD $25 for sunshine....can't S-OFF it without other ways.
Click to expand...
Click to collapse
then why does firewater say different?

grrmisfit said:
then why does firewater say different?
Click to expand...
Click to collapse
firewater doesn't work anymore unfortunately. Only way to get S-Off now is sunshine @ USD 25.

3mel said:
I've just rooted my phone unlocking the bootloader yesterday. I haven't gone S-off yet.
I'm coming from Samsung phones so things are a little different for me too. I followed this guide which covers everything you can and will need to gain full root on an m8
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
to get root apps to have all the ability they have elsewhere you need to cover 3 steps
1) unlock the bootloader, which will make some partitions accessible, but writing to the system partition is still blocked apart from via custom recovery (the phone reboots when you try to write into the system partition without "full root").
2) root. fairly obvious what that is.
3) gain S-off, which makes system partition accessible outside of the custom recovery. the phone can be enjoyed the same as any other rooted device at this stage. **this can only be done one way, and that one single way isn't free.**
you want to have all the stages mentioned in that link covered apart from the last firmware guide which is more optional.
Click to expand...
Click to collapse
Hi I can't root mine . Every time I try to get token it says that it's a incorrect file batch path or something like that? Do you know what the problem is?

Nebster7 said:
Hi I can't root mine . Every time I try to get token it says that it's a incorrect file batch path or something like that? Do you know what the problem is?
Click to expand...
Click to collapse
Please stop making new posts in different threads. It won't get your issue fixed any faster. It just confuses those trying to help you, leaving incomplete bits of info here and there. Just stick to one thread, specifically the one where I am already trying to help you.

redpoint73 said:
Please stop making new posts in different threads. It won't get your issue fixed any faster. It just confuses those trying to help you, leaving incomplete bits of info here and there. Just stick to one thread, specifically the one where I am already trying to help you.
Click to expand...
Click to collapse
Sorry. I have my issue fixed now as I just needed to type cmd on the top of the window to get token to unlock bootloader token. Flashed aicp 14.0 working excellent. Much faster, better battery oh only arm 9.0 pico seemed like the best gapps as I tried other ones didn't work. Man it took a lot of searching to do this as things are posted all over the place
---------- Post added at 02:56 AM ---------- Previous post was at 02:38 AM ----------
Nebster7 said:
Sorry. I have my issue fixed now as I just needed to type cmd on the top of the window to get token to unlock bootloader token. Flashed aicp 14.0 working excellent. Much faster, better battery oh only arm 9.0 pico seemed like the best gapps as I tried other ones didn't work. Man it took a lot of searching to do this as things are posted all over the place
Click to expand...
Click to collapse
Just one thing my PC doesn't see my phone now.???

Nebster7 said:
Just one thing my PC doesn't see my phone now.???
Click to expand...
Click to collapse
Meaning what exactly? Doesn't see storage (did you select the option on the phone to allow data transfer?) or adb or fastboot? Booted to the custom ROM, or something else (bootloader, recovery)?
When asking for help, please give as much information as possible. One sentence is really never enough info to go on.

S-OFF is out now, a word about it

For now, S-OFF from SunShine on the htc u11 is temporary. Changes you make while S-OFF will stay, they are not temporary, just the S-OFF flag is. All the same features, with exception of the ability to use custom hboot/aboot. Seriously, aboot patchers, don't bother trying at this point. Once you reboot into Android or Recovery, the device will reset back S-ON.
Changing mid, changing cid, downgrading etc all still work fine. If you want to change it a second time, just run sunshine again.
If/when a forever s-off comes, those with temp s-off will be upgraded at no cost.

jcase said:
For now, S-OFF from SunShine on the htc u11 is temporary. Changes you make while S-OFF will stay, they are not temporary, just the S-OFF flag is. All the same features, with exception of the ability to use custom hboot/aboot. Seriously, aboot patchers, don't bother trying at this point. Once you reboot into Android or Recovery, the device will reset back S-ON.
Changing mid, changing cid, downgrading etc all still work fine. If you want to change it a second time, just run sunshine again.
If/when a forever s-off comes, those with temp s-off will be upgraded at no cost.
Click to expand...
Click to collapse
Thanks man. I been holding off unlocking for a while waiting for this to come.

Many thanks @jcase for explanation. What about 2PZC RUU zip files flashing in case of temporary S-OFF? You know device reboots many times. Can we convert my devices to different variants?
Sent from my HTC U11 using XDA Labs

blueberry60 said:
Many thanks @jcase for explanation. What about 2PZC RUU zip files flashing in case of S-OFF? You know device reboots many times. Can we convert my devices to different variants?
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
It only clears if booting into android or recovery. You can reboot into download/bootloader without clearing it

jcase said:
It only clears if booting into android or recovery. You can reboot into download/bootloader without clearing it
Click to expand...
Click to collapse
Deleted
Sent from my HTC U11 using XDA Labs

@jcase
After getting Temp-S-Off, and later entering the DownloadMode mode, we see "S-Onn" (which is natural for temporary).
In the "OpenDSP" section there is "UNKNOWN".
And in the bootloader flag has changed status to "Modified".
regards
q.

qriozum said:
@jcase
After getting Temp-S-Off, and later entering the DownloadMode mode, we see "S-Onn" (which is natural for temporary).
In the "OpenDSP" section there is "UNKNOWN".
And in the bootloader flag has changed status to "Modified".
regards
q.
Click to expand...
Click to collapse
what's wrong with that? it is the same for me since I unlocked the bootloader. 2 months ago. both unknown and modified.
also can confirm now all works, changed CID twice (don't ask)

velimirchek said:
it is the same for me since I unlocked the bootloader. 2 months ago. both unknown and modified.
Click to expand...
Click to collapse
Same here.
velimirchek said:
changed CID twice (don't ask)
Click to expand...
Click to collapse
Why did you change CID twice?

Kisakuku said:
Same here.
Why did you change CID twice?
Click to expand...
Click to collapse
Because of @tbalden and you
I changed to 060 and then to 622.

Kisakuku said:
Is it safe to flash custom splash images?
Click to expand...
Click to collapse
I'll answer my own question. No issues flashing custom splash images in bootloader (nb0) or download mode (zip with android-info.txt), but obviously can't use recovery-based scripts (no S-OFF in recovery). Splash images made for the 10 work fine, since the screen resolution hasn't changed.

Kisakuku said:
I'll answer my own question. No issues flashing custom splash images in bootloader (nb0) or download mode (zip with android-info.txt), but obviously can't use recovery-based scripts (no S-OFF in recovery). Splash images made for the 10 work fine, since the screen resolution hasn't changed.
Click to expand...
Click to collapse
Thanks, I would have answered you but was sleeping

qriozum said:
@jcase
After getting Temp-S-Off, and later entering the DownloadMode mode, we see "S-Onn" (which is natural for temporary).
In the "OpenDSP" section there is "UNKNOWN".
And in the bootloader flag has changed status to "Modified".
regards
q.
Click to expand...
Click to collapse
OpenDSP should show unknown while s-on, that is normalm. Modified is normal as well, as you have an unlocked modified phone. You can clear that with a ruu most likely

My understanding with S-Off was that the bootloader can be unlocked and relocked without HTC noticing - is that the case?
For what it's worth I've not had a device fail on me over the years, but given their recent change of policy towards unlocking, the the screen issues and etc, I've not placed a custom ROM on this phone incase it does go all wrong and I need the warranty...
Could someone please confirm?

Doughnut said:
My understanding with S-Off was that the bootloader can be unlocked and relocked without HTC noticing - is that the case?
Click to expand...
Click to collapse
Support for S-OFF Locked is coming at some point in the future.

Follow this thread thanks Jcase for your hard work

jcase said:
OpenDSP should show unknown while s-on, that is normalm. Modified is normal as well, as you have an unlocked modified phone. You can clear that with a ruu most likely
Click to expand...
Click to collapse
Nope, flashing RUU and even relocking bootloader it stays modified.

velimirchek said:
Nope, flashing RUU and even relocking bootloader it stays modified.
Click to expand...
Click to collapse
At least on the HTC 10 S-OFF/Inlocked/Modified became S-OFF/Unlocked/Official after flashing a RUU Using the SD card method. It didn't when using an exe. Maybe this needs permanent S-OFF.
Sent from my HTC U11 using XDA Labs

Changed CID to superCID and... and I think there isn't much more that we need to do with S-OFF.
The downside of this method is the possibility to lose the ability go get S-OFF with future updates.

qriozum said:
@jcase
After getting Temp-S-Off, and later entering the DownloadMode mode, we see "S-Onn" (which is natural for temporary).
In the "OpenDSP" section there is "UNKNOWN".
And in the bootloader flag has changed status to "Modified".
regards
q.
Click to expand...
Click to collapse
velimirchek said:
Nope, flashing RUU and even relocking bootloader it stays modified.
Click to expand...
Click to collapse
will look into it

SunShine v3.5.8
Enhanced HTC U11 S-OFF Support

Recovering from Idiocy - Relocked Bootloader with TWRP Recovery and Custom Rom in Pla

I'm posting this here half for help and half as a warning to others. Got burnt tinkering a bit to carelessly.
The story in short: unlocked bootloader, TWRP and Leedroid. Wanted to remove the start up "Unlocked Bootloader" message + possibly gain use of GPay. Googling around XDA stories of both bricked devices and people who had no problems. I figured I'd see what happened if I locked the boot loader and if I had problems I could just unlock it again, right? Wrong. After flashing Leedroid developer options, of course, had defaulted to disabled as well as 'Allow OEM unlock'. So after my device refused to boot, as I half expected it would, it also wouldn't let me un-lock it again, which I didn't expect.
So here I am stuck with a bricked device that has S-On and won't boot (corrupted device message). Only way out is Stock RUU from the original carrier of my device (Telstra, Australia). Unfortunately that seemingly doesn't exist on the internet for gods knows why and because S-ON can't change CID (TELST001) to flash something else.
I do have one half-baked idea that I don't see robustly covered already. I happen to have a second Telstra U11. My thought was to perhaps take that, image it using nandroid and then flash that image onto the bricked device via fastboot. Is that an option, or is that a no-go for some other reason?
Moral of the story: Don't play with fire unless your sure you have a fire extinguisher. And don't try and re-lock your bootloader no matter how much that warning bugs you.
Neil

Does anyone know whether I could nandroid image the stock U11 and use fastboot to flash that image to the soft bricked device?

You may try that, as in theory you can boot into system with original system IMAGE (bit-perfect) and boot image(kernel). And you may also want to s-off your device after successful boot.

TeroZ said:
You may try that, as in theory you can boot into system with original system IMAGE (bit-perfect) and boot image(kernel). And you may also want to s-off your device after successful boot.
Click to expand...
Click to collapse
No permanent S-OFF available, so no point in performing S-OFF as it doesn't save you of such a problem...
Sent from my HTC U12+ using XDA Labs

@TeroZ seems that with the bootloader re-locked any fastboot flash x.img command is rejected by default. Seems you can only flash in RUU mode. Does that make sense to you? That closes the only other alternative to sending it back to the official repairer just to have them rather than me flash the official RUU. What a scam.

5m4r7ph0n36uru said:
No permanent S-OFF available, so no point in performing S-OFF as it doesn't save you of such a problem...
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
I mean you could temporarily soff and change the cid and mid to debrand the phone and have access to usable RUU.

TeroZ said:
I mean you could temporarily soff and change the cid and mid to debrand the phone and have access to usable RUU.
Click to expand...
Click to collapse
I contacted the Sunshine guys and the s-off can only be done from within android (ie not download mode etc) so kills that as an option as well.
HTC won't provide Telstra RUU and also won't allow me to send it to repair center as it was apparently originally a demo device (to my suprise). So short of the Telstra RUU its officially soft bricked. Can't say I've ever been quite this burnt before flashing on ROM's etc. I'm more familiar with computer land and am just not used to the possibility of actually killing your computer via messing around in software (OC'ing is another kettle of fish of course). As long as it boots your fine.
Not so in the android world!
I'm open to trying anything at this point. There really is nothing left to lose.
N

Try contacting Telstra customer service instead and see if they provides ruu.

ngodber said:
I contacted the Sunshine guys and the s-off can only be done from within android (ie not download mode etc) so kills that as an option as well.
HTC won't provide Telstra RUU and also won't allow me to send it to repair center as it was apparently originally a demo device (to my suprise). So short of the Telstra RUU its officially soft bricked. Can't say I've ever been quite this burnt before flashing on ROM's etc. I'm more familiar with computer land and am just not used to the possibility of actually killing your computer via messing around in software (OC'ing is another kettle of fish of course). As long as it boots your fine.
Not so in the android world!
I'm open to trying anything at this point. There really is nothing left to lose.
N
Click to expand...
Click to collapse
Try this thread. Similar sort of issue with bricking. HTC 10 Batch tool was used
https://forum.xda-developers.com/u11/help/help-ruu-firmware-t3716144/post77822986#post77822986