Red warning text after relocking bootloader - HTC 10 Questions & Answers

So, I unlocked by bootloader and went s-off in order to turn my HTC 10 into the US Unlocked version, so that I could get Nougat. Everything went well, I unlocked it using HTC dev, installed TWRP, flashed super su, installed Sunshine, went S-OFF, changed CID and MID, relocked, used the RUU.exe to get Nougat.
But now, even when the bootloader is relocked, I still get that red warning text that appears when the phone is booting up. Is it normal? Back on my old M8, relocking the bootloader took out the red text, as far as I remember. I tried to go back to S-ON, but the command failed.
Is there any way to get rid of that red text?

something like this?
http://forum.xda-developers.com/htc-10/development/bad-sprouts-hidden-red-text-aboots-t3397548 you need something like this just follow it step by step

Yes, that text. But there is no firmware for the Nougat version I have on my HTC right now, and returning to Marshmallow to get rid of that text would pretty much cancel the thing I made this for from the beginning.

TheMadKing said:
So, I unlocked by bootloader and went s-off in order to turn my HTC 10 into the US Unlocked version, so that I could get Nougat. Everything went well, I unlocked it using HTC dev, installed TWRP, flashed super su, installed Sunshine, went S-OFF, changed CID and MID, relocked, used the RUU.exe to get Nougat.
But now, even when the bootloader is relocked, I still get that red warning text that appears when the phone is booting up. Is it normal? Back on my old M8, relocking the bootloader took out the red text, as far as I remember. I tried to go back to S-ON, but the command failed.
Is there any way to get rid of that red text?
Click to expand...
Click to collapse
Hi, just a bit of warning when using the modified aboot, flashing this carelessly will result in an unrecoverable brick, search for the Sneakyghost thread for flashable zips, he explains very well why he dropped support for them, too many bricks.
http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520/page112
This is an example of someone bricking their phone:
http://forum.xda-developers.com/htc-10/help/htc-10-brick-t3521251
For your particular case, I think I read somewhere that changing the MID could cause the red text to appear, but I'm not 100% sure on that, in my case I only changed the CID for the US unlocked one and left the MID the same, I don't have the red text and I'm on Nougat, S-Off and unlocked, so relocking is not necessary to get rid of it.
I have seen the red text but only flashing a different kernel, running the Nougat RUU got rid of it.
Just my 2 cents, maybe it's not worth to have a brick just to get rid of some text you only see when rebooting.

ReaperHack said:
Hi, just a bit of warning when using the modified aboot, flashing this carelessly will result in an unrecoverable brick, search for the Sneakyghost thread for flashable zips, he explains very well why he dropped support for them, too many bricks.
http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520/page112
This is an example of someone bricking their phone:
http://forum.xda-developers.com/htc-10/help/htc-10-brick-t3521251
For your particular case, I think I read somewhere that changing the MID could cause the red text to appear, but I'm not 100% sure on that, in my case I only changed the CID for the US unlocked one and left the MID the same, I don't have the red text and I'm on Nougat, S-Off and unlocked, so relocking is not necessary to get rid of it.
I have seen the red text but only flashing a different kernel, running the Nougat RUU got rid of it.
Just my 2 cents, maybe it's not worth to have a brick just to get rid of some text you only see when rebooting.
Click to expand...
Click to collapse
Well, I surely didn't want to risk that, so I did what you mentioned. Yeah, the problem might have been from the MID. I changed it back, and flashed the RUU with the original software I had, locked the bootloader, and the text is gone. Thanks!

Related

[Q] S-On Tampered Locked Secruity Warning

I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags. Can't find an encrypted RUU or figure out how to encrypt the one I have to get this rolling again, can anybody give me a clue or anything on how to go about doing this or getting this thing functional again?
You can get the ruus at the bottom of this post. http://forum.xda-developers.com/showthread.php?p=46506621
cmlusco said:
You can get the ruus at the bottom of this post. http://forum.xda-developers.com/showthread.php?p=46506621
Click to expand...
Click to collapse
Yes, it always says:
FAILED (status read failed (too many links))
Probably because its 2.10 RUU and mine is on 3.11?
Yeah an s-on phone wont allow you to flash an ruu version older than the one already on the phone. And unfortunatley, we do not have the newest ruu available yet.
So there's nothing I can do but wait? I was pretty sure I had everything flashed back to stock but once I turned S-ON it wouldn't let me go past the bootloader. My phone's sound completely stopped working so I was going to take it in to get it taken care of, but I guess I can't do anything at all now.
You can probably still flash the RUU if you get the correct one i would assume. I've reset the tampered flags before also. I always made it a point to flash the older RUU's before flipping s-on for a warranty return, because it is so much easier to get s-off in case I mess something up, so not sure how being on that newer firmware is going to play out.
ccarr313 said:
You can probably still flash the RUU if you get the correct one i would assume. I've reset the tampered flags before also. I always made it a point to flash the older RUU's before flipping s-on for a warranty return, because it is so much easier to get s-off in case I mess something up, so not sure how being on that newer firmware is going to play out.
Click to expand...
Click to collapse
Yeah I'm just keeping an eye open and checking for the latest RUU. First time getting into this stuff, so lesson learned. Just sucks I'm without a phone even just to text/apps until then.
I have the same issue
GrayFalcon11 said:
Yeah I'm just keeping an eye open and checking for the latest RUU. First time getting into this stuff, so lesson learned. Just sucks I'm without a phone even just to text/apps until then.
Click to expand...
Click to collapse
I was S-Off and unlocked and rooted, I was trying to flash back to stock for a warranty exchange. Now I'm Locked, S-On and flagged Tampered and stuck in the bootloader. I'm on 3.11.605.10 as well. I only have 4 days left to send this back to verizon.. Any suggestions? or I'm I butt ****ed with no lube.
keith7120 said:
I was S-Off and unlocked and rooted, I was trying to flash back to stock for a warranty exchange. Now I'm Locked, S-On and flagged Tampered and stuck in the bootloader. I'm on 3.11.605.10 as well. I only have 4 days left to send this back to verizon.. Any suggestions? or I'm I butt ****ed with no lube.
Click to expand...
Click to collapse
What happen? I have 3 days left to send back to Verizon and I'm still s-off and unlocked and I don't wanna mess it up.
Do an older ruu.
Lock bootloader using fastboot.
Go s-on using fastboot.
Do a signed ruu.
cmlusco said:
Do an older ruu.
Lock bootloader using fastboot.
Go s-on using fastboot.
Do a signed ruu.
Click to expand...
Click to collapse
Why 2 ruu?
Probably not really needed, but just to be sure the phone got wiped out.
Let Me Make sure I understand
cmlusco said:
Probably not really needed, but just to be sure the phone got wiped out.
Click to expand...
Click to collapse
Can I or can I not flash an older RUU?
How do I get a hold of a signed RUU? Is it the one that says decrypted?
Will this at least allow me to wipe the phone to where it does not say tampered?
I could have sworn I have tried these RUU's but I get a remote signature error.
No if you are s-on you can not flash an ruu which is an older version than the phone is currently on.
The signed and decrypted (not signed) ruu's can be found at the bottom of the second post of santods rom radio kernel thread in development. http://forum.xda-developers.com/showthread.php?p=46506621
In order to remove the tampered flag you would need to get s-off again. I believe there is a new exploit for 4.2.2 http://forum.xda-developers.com/showthread.php?p=51481200, if you want to go that route.
Remote sig error is because you were trying to flash an unsigned ruu while s-on.
oh well
cmlusco said:
No if you are s-on you can not flash an ruu which is an older version than the phone is currently on.
The signed and decrypted (not signed) ruu's can be found at the bottom of the second post of santods rom radio kernel thread in development. http://forum.xda-developers.com/showthread.php?p=46506621
In order to remove the tampered flag you would need to get s-off again. I believe there is a new exploit for 4.2.2 http://forum.xda-developers.com/showthread.php?p=51481200, if you want to go that route.
Remote sig error is because you were trying to flash an unsigned ruu while s-on.
Click to expand...
Click to collapse
Welp, a couple seconds in the microwave solved my dilemma. I hope. It won't come back on.
Next question, my replacement device has 4.4.2 on it. Will the current S-off tools work to flip it from S-on to S-off?
keith7120 said:
Welp, a couple seconds in the microwave solved my dilemma. I hope. It won't come back on.
Next question, my replacement device has 4.4.2 on it. Will the current S-off tools work to flip it from S-on to S-off?
Click to expand...
Click to collapse
Yup, just follow the directions on the WeakSauce thread. -> http://forum.xda-developers.com/showthread.php?t=2699091
eman7131 said:
Yup, just follow the directions on the WeakSauce thread. -> http://forum.xda-developers.com/showthread.php?t=2699091
Click to expand...
Click to collapse
Thanks, I'm now S-Off
how would i go about going S-On in fastboot? my fiance device was thought to be returned to stock but we found out that it says Relocked but still says S-Off and when we try to use Firewater it stops after we say Yes cause for some reason its already showing S-off but the bootloader is actually locked.
Stuck Bootloader
Hi i need help. I am stuck in bootloader with s On and relocked. Ive read everything and no go. Please help any one

Returning to Stock T-MOB101

Hi everybody,
I've been reading a lot of stuff since now but still have some unanswered questions.
I want to return to completely stock as for insurance or warranty purposes.
I originally got an german HTC One M8 with T-MOB101 cid.
I unlocked the bootloader as the temp-root variant did not work for me, s-off'ed, changed cid to Supercid and flashed ViperRom.
But now I have to send it in to insurance company because my display glass broke after dropping my htc one off about 1 Foot...:crying:
So how would be the optimal procedure to get as close to completely stock?
I know that after reverting everything the bootloader would still say relocked.
So my idea was to:
1. get an original T-MOB101 NAND backup and restore it (beforehand restore T-MOB101 cid)
2. flashing stock recovery
3. Removing Tampered (http://forum.xda-developers.com/showpost.php?p=51700320&postcount=1)
4. Setting Locked (http://forum.xda-developers.com/showthread.php?t=2708571)
5. play over an OTA firmware.zip
This would lead me to a stock rom with OTA capability, but would still show me the red warning as well as S-OFF.
As an alternative I read about hex edited hboots to get rid of the red warning or even Mask S-off as s-on.
However in the according thread i could not make out an hboot corresponding to the T-MOB101 CID. So I tried it on my own after having a look at stock and modified hboots.
I edited my own hboot according to those modification but am too scared to flash it as it could hard brick my phone....
So I ask you guys, am I on the right way and what would you do ?
Greetz F4t4l!tY
F4t4l!tY said:
Hi everybody,
I've been reading a lot of stuff since now but still have some unanswered questions.
I want to return to completely stock as for insurance or warranty purposes.
I originally got an german HTC One M8 with T-MOB101 cid.
I unlocked the bootloader as the temp-root variant did not work for me, s-off'ed, changed cid to Supercid and flashed ViperRom.
But now I have to send it in to insurance company because my display glass broke after dropping my htc one off about 1 Foot...:crying:
So how would be the optimal procedure to get as close to completely stock?
I know that after reverting everything the bootloader would still say relocked.
So my idea was to:
1. get an original T-MOB101 NAND backup and restore it (beforehand restore T-MOB101 cid)
2. flashing stock recovery
3. Removing Tampered (http://forum.xda-developers.com/showpost.php?p=51700320&postcount=1)
4. Setting Locked (http://forum.xda-developers.com/showthread.php?t=2708571)
5. play over an OTA firmware.zip
This would lead me to a stock rom with OTA capability, but would still show me the red warning as well as S-OFF.
As an alternative I read about hex edited hboots to get rid of the red warning or even Mask S-off as s-on.
However in the according thread i could not make out an hboot corresponding to the T-MOB101 CID. So I tried it on my own after having a look at stock and modified hboots.
I edited my own hboot according to those modification but am too scared to flash it as it could hard brick my phone....
So I ask you guys, am I on the right way and what would you do ?
Greetz F4t4l!tY
Click to expand...
Click to collapse
To tell you the truth, I don't think the insurance company will care about any software mods. Different story if you had to send it in to HTC.
GermanGuy said:
To tell you the truth, I don't think the insurance company will care about any software mods. Different story if you had to send it in to HTC.
Click to expand...
Click to collapse
Well, actually I would agree, but as they turn on the phone and a red warning pops up I could think of any crazy reason why they would deny the repair or exchange ^^.
Whatever that reason might be that would result in a broken glass caused by the software
Does the red text dissappear if I return S-ON, officially relock bootloader, stock recovery and cid?
F4t4l!tY said:
Well, actually I would agree, but as they turn on the phone and a red warning pops up I could think of any crazy reason why they would deny the repair or exchange ^^.
Whatever that reason might be that would result in a broken glass caused by the software
Does the red text dissappear if I return S-ON, officially relock bootloader, stock recovery and cid?
Click to expand...
Click to collapse
The only way to get rid off the red text is with a modifed HBOOT.
GermanGuy said:
The only way to get rid off the red text is with a modifed HBOOT.
Click to expand...
Click to collapse
Well ok, I feared that. You're not accidently fit in Hex-Editing ?
As I said, I already backed up my hboot and edited it as the other hboots I founds with the wrong cid. But I'm afraid of flashing it without anyone else who knows something about hexediting took a second look at it.
Also does the hboot get overwritten by a NAND backup? So if I'll restore I would have to modify that hboot and not the one I'm currently at?
F4t4l!tY said:
Well ok, I feared that. You're not accidently fit in Hex-Editing ?
As I said, I already backed up my hboot and edited it as the other hboots I founds with the wrong cid. But I'm afraid of flashing it without anyone else who knows something about hexediting took a second look at it.
Also does the hboot get overwritten by a NAND backup? So if I'll restore I would have to modify that hboot and not the one I'm currently at?
Click to expand...
Click to collapse
Sorry, have not done hexediting in a while. Hboot is part of firmware, does not get overwritten by restore backup.
Alright but thanks anyway.
If there is someone out there who could help, i would appreciate that .
Thx in advance!
F4t4l!tY said:
Alright but thanks anyway.
If there is someone out there who could help, i would appreciate that .
Thx in advance!
Click to expand...
Click to collapse
First you should flash the stock rom then stock recovery.This will remove your red text.then you should flash ruu.I would suggest not to change your cid.
Also if you are comfortable you can change your cid to supercid,mid to wwe mid then flash wwe fw and its recovery then flash the ruu.This will convert your phone to international htc with s-off and super cid and you will be able to take ota and you will have full 100% warranty.
Hey Jyotirdeb,
thanks for your input.
But there is still the problem, that I have to come to T-MOB101 firmware and not the WWE. Furthermore as far as I have read, the red text will only disappear if I flash stock recovery, stock ROM AND S-ON again. At least without a modified HBOOT.
Other problem is, that there are as far as i know no RUUs available for the M8 up to now. Correct me if I'm mistaken. At least I didn't find one, especially for cid T-MOB101.
F4t4l!tY said:
Hey Jyotirdeb,
thanks for your input.
But there is still the problem, that I have to come to T-MOB101 firmware and not the WWE. Furthermore as far as I have read, the red text will only disappear if I flash stock recovery, stock ROM AND S-ON again. At least without a modified HBOOT.
Other problem is, that there are as far as i know no RUUs available for the M8 up to now. Correct me if I'm mistaken. At least I didn't find one, especially for cid T-MOB101.
Click to expand...
Click to collapse
It is true that you have to be on stock rom and stock kernel.But you dont have to be s-on you can be s-off.And yes as far as I know there is EU ruu (unbranded) maybe you have to wait for hTC to release Ruu for other variant.I am sorry I cant be of more help.
Hmm, strange thing, as I actually read it again that there must be s-on and everything stock, to get rid of it, but nevermind.
Really, where could I get that RUU from? As far as I know only the Sprint or Verizon Variant does have a RUU not the International One.
Furthermore would I need the RUU from T-Mobile as the release it with their branding, not HTC.
F4t4l!tY said:
Hmm, strange thing, as I actually read it again that there must be s-on and everything stock, to get rid of it, but nevermind.
Really, where could I get that RUU from? As far as I know only the Sprint or Verizon Variant does have a RUU not the International One.
Furthermore would I need the RUU from T-Mobile as the release it with their branding, not HTC.
Click to expand...
Click to collapse
"Hmm, strange thing, as I actually read it again that there must be s-on and everything stock, to get rid of it, but nevermind."
If you have an s-on device you can change bootloader status to relocked but if you have soff device you can change bootloader stats to locked so you will get 100% warranty.I dont know about version or sprint but the ruu is available for unbranded EU model.
hi guys
i don t find the recovery stock of my htc one m8 cid tmob101 firmware 3.32.111.3 .
you can help me? thx
glesius said:
hi guys
i don t find the recovery stock of my htc one m8 cid tmob101 firmware 3.32.111.3 .
you can help me? thx
Click to expand...
Click to collapse
The site is in german... use google chrome to translate.
You'll find everything you need to restore T-MOB101 M8.
http://www.handy-faq.de/forum/htc_o...ne_m8_firmwaresammlung_ruus_otas_backups.html
harri2cool said:
The site is in german... use google chrome to translate.
You'll find everything you need to restore T-MOB101 M8.
http://www.handy-faq.de/forum/htc_o...ne_m8_firmwaresammlung_ruus_otas_backups.html
Click to expand...
Click to collapse
Actually, on that site there is a RUU for unbranded phones only. For T-MOB101 they have a nand backup and firmware. I'm still thinking whether I want to use that. That is, I have a similar issue as the OP, I mean, I want to reinstall Android, although I'm completely stock, unrooted, etc. It's just that the Lollipop update screwed everything up and I'm hoping that reinstalling will fix it. Unfortunately, for CID T-MOB101 no RUU is available. So, I either have to use the backup and then flash firmware, for which I have to root and install custom recovery first, or I have to wait till HTC comes up with Android 5.1.

[Q] Back to stock from NuSense

Need to take my Verizon One M7 in for a replacement. Reception is killing me (keep dropping to 1X or weak 3G in outlying areas), calls drop more than they don't, and even getting mms generic errors. Tried multiple ROM's, multiple radios, stock recovery/ROM/reset, new SIM card...nothing works.
I did notice something though - when I first got this phone, they had trouble initializing the SIM in the store...thought nothing of it until I went to the corporate store for a replacement SIM and they couldn't get the replacement to activate from the phone...I am thinking I have bad hardware.
The guy was cool (he looked my stats up and was shocked at the dropped calls) but made a point to tell me it was likely behaving badly due to being rooted...would rather walk in with a plain vanilla phone and let them replace it or let me out of my extension and I will go back to my trusty ReZound, because this thing is useless as a phone as-is.
How do I get back to pure stock so I can take this in for a replacement?
ROM is NuSenseSIX-KitKat_m7vzw_RC7.4_071714
Radios from 4.10.605.3_NoBootImg_firmware
TWRP 2.7.08
Rooted (and hboot) using Firewater (have the red warning 'this is only for internal HTC use..." on the boot splash screen)
the_Damaged_one said:
Need to take my Verizon One M7 in for a replacement. Reception is killing me (keep dropping to 1X or weak 3G in outlying areas), calls drop more than they don't, and even getting mms generic errors. Tried multiple ROM's, multiple radios, stock recovery/ROM/reset, new SIM card...nothing works.
I did notice something though - when I first got this phone, they had trouble initializing the SIM in the store...thought nothing of it until I went to the corporate store for a replacement SIM and they couldn't get the replacement to activate from the phone...I am thinking I have bad hardware.
The guy was cool (he looked my stats up and was shocked at the dropped calls) but made a point to tell me it was likely behaving badly due to being rooted...would rather walk in with a plain vanilla phone and let them replace it or let me out of my extension and I will go back to my trusty ReZound, because this thing is useless as a phone as-is.
How do I get back to pure stock so I can take this in for a replacement?
ROM is NuSenseSIX-KitKat_m7vzw_RC7.4_071714
Radios from 4.10.605.3_NoBootImg_firmware
TWRP 2.7.08
Rooted (and hboot) using Firewater (have the red warning 'this is only for internal HTC use..." on the boot splash screen)
Click to expand...
Click to collapse
fastboot ruu would be the easiest way.
once ruu is complete you can write secure flag back to s-on and it will be 100% stock.
synisterwolf said:
fastboot ruu would be the easiest way.
once ruu is complete you can write secure flag back to s-on and it will be 100% stock.
Click to expand...
Click to collapse
Thanks synisterwolf...two questions:
1 - I assume one of these would be what I want for a full RUU (not 100% sure which one)?
(from http://forum.xda-developers.com/showthread.php?t=2485319)
2.10.605.1 Decrypted RUU
2.10.605.1 Signed RUU
Odexed Full Rom (4.10.605.3 4.4.2 Sense 6.0)
2 - I found this guide...if I use the updated RUU, is the rest of this process still valid?
http://forum.xda-developers.com/showthread.php?t=2475216
the_Damaged_one said:
Thanks synisterwolf...two questions:
1 - I assume one of these would be what I want for a full RUU (not 100% sure which one)?
(from http://forum.xda-developers.com/showthread.php?t=2485319)
2.10.605.1 Decrypted RUU
2.10.605.1 Signed RUU
Odexed Full Rom (4.10.605.3 4.4.2 Sense 6.0)
2 - I found this guide...if I use the updated RUU, is the rest of this process still valid?
http://forum.xda-developers.com/showthread.php?t=2475216
Click to expand...
Click to collapse
guide is correct but use this link for RUU:
http://forum.xda-developers.com/showthread.php?t=2765784
the one you posted is a rom that you flash in recovery and not a full RUU
Be sure to follow the "lock bootloader" instructions before you ruu. There is a command either done in adb with root or recovery flashable zip to get "locked" instead of "relocked". As you see above, it requires you to either be rooted our have custom recovery, so do it before ruu and s-on after ruu completes.
Side note: ruu will wipe the whole phone, so be sure to copy your pictures, music, etc to a PC before ruu.
Edit: I recommend the signed 2.x.x.x ruu as it is fully stock. The new one linked above is rooted, so you would have to unroot and all that after you ruu.
Sent from my HTC6500LVW using XDA Free mobile app
Thanks guys...any chance one of you has a link to the signed fully stock RUU?
edit: (or is that the one I found above on santod's thread that says it's signed? I am guessing signed means fully stock, not rooted, etc?)
the_Damaged_one said:
Thanks guys...any chance one of you has a link to the signed fully stock RUU?
edit: (or is that the one I found above on santod's thread that says it's signed? I am guessing signed means fully stock, not rooted, etc?)
Click to expand...
Click to collapse
Correct, the one from santods thread. Signed
means it has been signed and encrypted by HTC.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Correct, the one from santods thread. Signed
means it has been signed and encrypted by HTC.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Makes sense...never needed to use an encrypted one before on my DINC or ReZound, so I wasn't up to speed on the differences. Appreciate the guidance on this.
Will also give it a day on stock (keeping s-off) to see if it actually helps...though I suspect it won't.
the_Damaged_one said:
Makes sense...never needed to use an encrypted one before on my DINC or ReZound, so I wasn't up to speed on the differences. Appreciate the guidance on this.
Will also give it a day on stock (keeping s-off) to see if it actually helps...though I suspect it won't.
Click to expand...
Click to collapse
You don't "need" to, but it is always the better option if it is available.
Sent from my HTC6500LVW using XDA Free mobile app
Thanks for the help...
I did get the stock (signed, encrypted) RUU to load...had to back-rev my firmware using santod's post first, but otherwise all went as expected.
After a few updates OTA, I have been on the 4.4.2 for a couple of days - still cruddy signal at my house, so I plan ot s-on and head into the local corporate store to see what's next.
Will post on the other thread for the folks looking for the right RUU link.
Uzephi said:
You don't "need" to, but it is always the better option if it is available.
Click to expand...
Click to collapse
Speaking of better option...want to make sure I avoid a "tampered" issue...
I left my One s-off after the RUU, and updated OTA to latest to see if that helped my issue (it did not).
To go s-on, am I ok to do it now, or do I need to flash back to an older RUU first? Not sure if Verizon built something into a newer update that may catch the flag change.
No. Verizon has no control on that deep of the inner workings of an HTC. Only way to trip a "Tampered" state is messing with the system partition, radio, etc without being s-off. Turning s-off to s-on with everything stock will not trip that flag.
Edit: in my experience with HTC bootloaders, (I have had an Inc, Rezound, DNA, and this m7) they all are different in certain ways. The Inc never had a "Tampered" tag, to my knowledge. The Rezound had "tampered" tripped when a custom recovery was flashed while s-on. We had a special way of utilizing "fastboot boot recovery" command to prevent the tampered from ever being tripped. I didn't have my DNA long enough to worry about "tampered". And to get bootloader unlock for this phone, it did s-off so tampered wasn't tripped for me.
So how are HTC bootloader different by device? When my Inc had to be rooted, it didn't have a "locked" or "unlocked" flag, only s-on/off. The Rezound had to be s-off if you wanted to flash everything of a Rom in recovery (or utilize HTC dumlock or "fastboot boot recovery" command from bootloader) otherwise after a Rom install, tampered would trip and the boot.img wouldn't be flashed and you would have to go to bootloader to flash the boot.img or do the workaround in parentheses... For the DNA and m7, you don't need s-off to flash boot.img in recovery. I do notice on stock bootloader (I have the faux hboot) it will check if radio, hboot, and recovery are stock or not and I think this is what s-on checks for when tripping tampered. (Before I flashed the faux hboot it showed everything green except recovery since I have TWRP and not stock)
For any inaccuracies you can correct me and I will fix. This is from my own experiences with these devices and how they work.
TL/DR: all HTC model bootloader are different, but one thing never changes, if you are completely stock s-off and run the command "fastboot oem writesecureflag 3" it will not trip tampered.
Sent from my HTC6500LVW using XDA Free mobile app

This is a test device ? ?

After running stock ruu's, and gone through the phone setup, on the last "HTC page" there is a paragraph at the bottom, in red, that says "bla bla bla this is a test device".
What's that all about ?
There's 2 M8's in the house and both are legit UK handsets and both have red text on set up.
Cheers
Edit.... Think I found the answer. Is it due to the fact that both handsets are s-off ?
10rdan said:
After running stock ruu's, and gone through the phone setup, on the last "HTC page" there is a paragraph at the bottom, in red, that says "bla bla bla this is a test device".
What's that all about ?
There's 2 M8's in the house and both are legit UK handsets and both have red text on set up.
Cheers
Edit.... Think I found the answer. Is it due to the fact that both handsets are s-off ?
Click to expand...
Click to collapse
No. It is because you have an unlocked bootloader.
But since you are S-Off, you can get rid of it with a modified hboot.
Go to this thread to find out how.
xunholyx said:
No. It is because you have an unlocked bootloader.
But since you are S-Off, you can get rid of it with a modified hboot.
Go to this thread to find out how.
Click to expand...
Click to collapse
It's not the red text on the splash screen I'm meaning. It's the red text on last page, I think, when going through the set up of the phone after its booted.
I don't have red text on splash screen when running stock, I only get that after flashing a custom recovery.
It is because your s-off. Being s-off trips a flag in your OS. When going through the testing phase before these phones get shipped to the public they are s-off and Tell HTC is enabled to help with errors and crashes. If you were to go back to s-on Tell HTC would be able to toggle again and the red text on the last part of setup would disappear. It's nothing to worry about.
LarryBoyG said:
It is because your s-off. Being s-off trips a flag in your OS. When going through the testing phase before these phones get shipped to the public they are s-off and Tell HTC is enabled to help with errors and crashes. If you were to go back to s-on Tell HTC would be able to toggle again and the red text on the last part of setup would disappear. It's nothing to worry about.
Click to expand...
Click to collapse
OK, thanks. After a bit of searching I thought it was to do with being s-off.

Quick RUU Question, need to bring my phone back to TMO

I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?
Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.
Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!

Categories

Resources