Related
I have been able to create a method of unlocking ANY unlockable hboot, on any device (as far as i can tell)
The method works on S-on, stock recovery devices. As of right now im linking to a specific device, however, if you only use the unlock youll be fine. I need testers from other HTC devices.
My first thread: http://forum.xda-developers.com/showthread.php?p=24370319#post24370319
If you like this, find it helpful, or want to support me please donate. Just follow these directions.
1) Be Logged-In to PayPal
2) Go to: https://www.paypal.com/[email protected]
2a) If that didnt work and fill out the E-Mail please, use [email protected] and select the way your sending as a GIFT
3) Enter the amount you want to give, Select personal, and Gift
4) Hit Continue and follow any of PayPal's Steps
5) Make sure that if asked, the receiving user DOES NOT Have to be verified.
I can confirm this works for MetroPCS Widfire S A510c hboot 1.10.0000. It unlocked my bootloader just fine. No steps required from HTCDev.
Many thanks Simon! Keep up the great work.
Great news!
But it's not full S-OFF, is it?
Not yet. This sets you up for it. Soon an soff will be out the developers of it need kernel help and I'm tryin to help them get it working
Sent from my HTC_A510c using Tapatalk
simonsimons34 said:
Not yet. This sets you up for it. Soon an soff will be out the developers of it need kernel help and I'm tryin to help them get it working
Sent from my HTC_A510c using Tapatalk
Click to expand...
Click to collapse
..well when s-off is out? Really dont unerstand for what is your "unlocking utility" then?
This utility allows you to unlock your bootloader without HTCDev, thus saving your warranty
Simon is working on getting universal S-OFF with some other devs. Will take a few, but he'll get it.
bobdamnit said:
This utility allows you to unlock your bootloader without HTCDev, thus saving your warranty
Simon is working on getting universal S-OFF with some other devs. Will take a few, but he'll get it.
Click to expand...
Click to collapse
with the option 1 of his tool "Bootloader Unlock CDMA ONLY" ??
That I'm not too sure about. I was told it was universal but needed testing. Simon and I have confirmed it working on several CDMA HTC Wildfire S's. (The only HTC phones we have access to, currently.)
I would say wait for Simon to confirm it should work on GSM HTC phones. I only helped with the code, so I don't know much about the mechanics of the utility.
Sorry.
according the .bat file all the stuff seems to be specific to the wildfire. So I don't undersand why simon is asking us to test it on other devices ?
geek78 said:
according the .bat file all the stuff seems to be specific to the wildfire. So I don't undersand why simon is asking us to test it on other devices ?
Click to expand...
Click to collapse
Because this method should work on ANY HTC phone with ANY hboot. We are asking you to try it so it can be confirmed. (Confirmed on Marvelc only so far.)
If you know batch, you can absolutely modify it to your liking.
Also, if you had read the original post:
Simonsimon34 said:
As of right now im linking to a specific device, however, if you only use the unlock youll be fine. I need testers from other HTC devices.
Click to expand...
Click to collapse
If you read the .bat file you can see that this can't work on another device
geek78 said:
If you read the .bat file you can see that this can't work on another device
Click to expand...
Click to collapse
S-OFF, no. That onlly works on CDMA Widlfire S. Unlock, yes. That should work on ANY HTC device, no matter what the batch file is calling. (It will still perform as it is supposed to.)
I helped write the batch file dude.
bobdamnit said:
S-OFF, no. That onlly works on CDMA Widlfire S. Unlock, yes. That should work on ANY HTC device, no matter what the batch file is calling. (It will still perform as it is supposed to.)
I helped write the batch file dude.
Click to expand...
Click to collapse
...can you attach the batch file here?
j4n87 said:
...can you attach the batch file here?
Click to expand...
Click to collapse
No I cannot. Since I am not claiming to be the author (only helped him a bit), I will not post their work. If Simon wants to release it, I'm sure he will.
I will however, give you a hint. Download the exe and run it. Leave it open and check your temp files. The batch file is in there somewhere.
Also, guys, give it a shot. At best, it works. At worst, it doesnt, and you still have a locked bootloader.
GUYS I will tell you how it works soon heck ill make its own release if you guys arnt suited with it. I just need to know if option one works. It uses a temp root pulls your misc img and modifys YOUR misc. This then flashes removes temp root and you have an unlocked bootloader. Just make sure your bootloader is up to date. There is nothing specific in the unlock
Sent from my HTC_A510c using Tapatalk
simonsimons34 said:
GUYS I will tell you how it works soon heck ill make its own release if you guys arnt suited with it. I just need to know if option one works. It uses a temp root pulls your misc img and modifys YOUR misc. This then flashes removes temp root and you have an unlocked bootloader. Just make sure your bootloader is up to date. There is nothing specific in the unlock
Sent from my HTC_A510c using Tapatalk
Click to expand...
Click to collapse
...well tried it on my HTC One X. no joy.
At least its says still "Locked" in bootloader.
Can you make sure no errors were thrown when temp rooting ? Or errors at all. Sometimes it tries to push too soon. Also can you try downgradeing to the lowest possible
Sent from my HTC_A510c using Tapatalk
simonsimons34 said:
Can you make sure no errors were thrown when temp rooting ? Or errors at all. Sometimes it tries to push too soon. Also can you try downgradeing to the lowest possible
Sent from my HTC_A510c using Tapatalk
Click to expand...
Click to collapse
..the HTC One is even not officially out in most countrys.
Theres nothing to downgrade.
Oh its because of the way I temp root. They must of patched it.
Sent from my HTC_A510c using Tapatalk
Any more news?
Hi, I realize I will get a lot of flame for this, but how do I know if my AT&T One X is S-off?
See, I'm trying to flash this custom boot screen from here (http://forum.xda-developers.com/showthread.php?t=2173665) and the requirements say I must be S-off and have an unlocked bootloader.
I know for sure my bootloader is unlocked (via the HTCDev method). I also read some places that S-off means your bootload is locked? So kind of confused here.
Thanks very much XDA geniuses!!!!
toughtrasher said:
Hi, I realize I will get a lot of flame for this, but how do I know if my AT&T One X is S-off?
See, I'm trying to flash this custom boot screen from here (http://forum.xda-developers.com/showthread.php?t=2173665) and the requirements say I must be S-off and have an unlocked bootloader.
I know for sure my bootloader is unlocked (via the HTCDev method). I also read some places that S-off means your bootload is locked? So kind of confused here.
Thanks very much XDA geniuses!!!!
Click to expand...
Click to collapse
Reboot into boot loader. It'll either say S-On or S-Off.
Okay, I've done that and it says I'm S-On.
What are the benefits of S-Off and any cons? Thanks given
System write protection is turned off. Reduces chance of bricking with ruu and allows you to change things like hboot and splash screen without the need for them to be signed. It's good to have if you're knowledgeable enough to read and follow instructions.
Sent from my One X using xda app-developers app
toughtrasher said:
Okay, I've done that and it says I'm S-On.
What are the benefits of S-Off and any cons? Thanks given
Click to expand...
Click to collapse
No need to flash boot.img
Less vernerable to brick etc...
There's really no disadvatage of gaining soff, so why not?
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Thug_4_Life said:
No need to flash boot.img
Less vernerable to brick etc...
There's really no disadvatage of gaining soff, so why not?
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
There is one disadvantage. S-OFF stands for Security Off. Security Off disables security checks, verifying your hboot, software version, CID, etc. If you flash something that you're not supposed to to the emmc partitions or something not designed for evita, you will brick.
exad said:
There is one disadvantage. S-OFF stands for Security Off. Security Off disables security checks, verifying your hboot, software version, CID, etc. If you flash something that you're not supposed to to the emmc partitions or something not designed for evita, you will brick.
Click to expand...
Click to collapse
Lol I remember what happened when I flashed Sense5 rom specifically for Evo 4g lte.
Sent from my HTC One X using xda app-developers app
S-off if you need it... If not play it safe.
Sent from my HTC One X using xda app-developers app
Thug_4_Life said:
No need to flash boot.img
Less vernerable to brick etc...
There's really no disadvatage of gaining soff, so why not?
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
exad said:
There is one disadvantage. S-OFF stands for Security Off. Security Off disables security checks, verifying your hboot, software version, CID, etc. If you flash something that you're not supposed to to the emmc partitions or something not designed for evita, you will brick.
Click to expand...
Click to collapse
For some reason, these two just seem to coincide the hell out of each other someone explain
T4L, I've followed the steps on that thread you pointed me to, but I'm stuck on step 7, inputting this to the command prompt:
adb shell chmod 744 /data/local/tmp/soffbin3
See, I read one of the posts in there that says I can use the files from Hassoon's all in one tool and just point the command prompt there, however when I type in "adb shell chmod 744" itdoesn't do anything. Then when I type in anything else after "adb shell chmod 744" it says error: cannot find device.
What do?
toughtrasher said:
For some reason, these two just seem to coincide the hell out of each other someone explain
T4L, I've followed the steps on that thread you pointed me to, but I'm stuck on step 7, inputting this to the command prompt:
adb shell chmod 744 /data/local/tmp/soffbin3
See, I read one of the posts in there that says I can use the files from Hassoon's all in one tool and just point the command prompt there, however when I type in "adb shell chmod 744" itdoesn't do anything. Then when I type in anything else after "adb shell chmod 744" it says error: cannot find device.
What do?
Click to expand...
Click to collapse
What rom are you using? a root access request pops up on your phone screen after, did you grant root?
exad said:
What rom are you using? a root access request pops up on your phone screen after, did you grant root?
Click to expand...
Click to collapse
I am using CleanROM 6 R2. It didn't pop up anything after step 7
toughtrasher said:
I am using CleanROM 6 R2. It didn't pop up anything after step 7
Click to expand...
Click to collapse
pastebin your cmd please
Make sure you're plugged into a USB 2 port, not USB 3. Anytime I get that error, it's cause I forgot to plug it in the right one.
Sent from my One X using xda app-developers app
Thanks for all your responses, guys! Really appreciate it.
I've succesfully got s-off thanks a lot to beaups! Very great person.
Now for some theming...
http://rumrunner.us/instructions/
http://rumrunner.us/downloads-2/
?
Sent from my HTC One mini using xda premium
INVICTUS79 said:
?
Sent from my HTC One mini using xda premium
Click to expand...
Click to collapse
It's a .bat file that s-off your one mini, I've used it myself
Sent from my HTC One mini using XDA Premium 4 mobile app
Can you install paid apps on custom rom if you are s-off ?
can you please explain why do I need to s-off mine?
thx
RSchris said:
Can you install paid apps on custom rom if you are s-off ?
Click to expand...
Click to collapse
I'm pretty sure you can install it in custom rom or any rom. And s-off doesn't have anything to do with that.
abzboi said:
I'm pretty sure you can install it in custom rom or any rom. And s-off doesn't have anything to do with that.
Click to expand...
Click to collapse
Thank you. But today you can't install paid apps on Magio R3 and SolidRom. Magio R4 will fix the problem, according to the dev.
RSchris said:
Can you install paid apps on custom rom if you are s-off ?
Click to expand...
Click to collapse
No that's a kernel issue
edimonoarfa said:
can you please explain why do I need to s-off mine?
thx
Click to expand...
Click to collapse
Its a HTC security measure which stops your ability to change the system example with s-on you can't update superSU binary, can't delete system apps and can't install busy box
Sent from my HTC One mini using XDA Premium 4 mobile app
CONdemmedNORmal said:
No that's a kernel issue
Its a HTC security measure which stops your ability to change the system example with s-on you can't update superSU binary, can't delete system apps and can't install busy box
Sent from my HTC One mini using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well being able to delete system apps is a kernel thing.
S-off will allow you to flash Rom from recovery without having to fastboot kernel also allows you to write to any blk so in the future when HTC updates your firmware you won't have to go back to stock and take the ota you can flash new firmware useing fastboot. This is a blessing from the android gods. You should do it before HTC closes the exploit
Sent from my HTC One S using Xparent Red Tapatalk 2
CONdemmedNORmal said:
Its a HTC security measure which stops your ability to change the system example with s-on you can't update superSU binary, can't delete system apps and can't install busy box
Sent from my HTC One mini using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you
I've tried several times to s-off mine but always ended up to fail.
First, when it tried to update, it said "something stinky", i don't now if it was a success or not
Second, pouring til 8 times, ended with "wait 30 seconds, pray and boot"
Is something wrong? I think i fulfill everyting needs before
CONdemmedNORmal said:
Its a HTC security measure which stops your ability to change the system example with s-on you can't update superSU binary, can't delete system apps and can't install busy box
Sent from my HTC One mini using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's incorrect, s-off, or security off, has nothing to do with system write protection, which is what you're referring to.
S-off gives you the ability to write low-level unsigned files to your device, such as bootloaders, splash images, etc.
The two are completely different things, and you can have one without having the other.
I'm on hboot 2.21, stock odex stock rom 4.4.2 rooted but for some reason, renove or rumrunner doesn't work for me. Rumrunner gets stuck on 8 out of 40 or something after rebooting. Renove gives me -1 or -2 error and doesn't s-off, can anyone tell me what's wrong? I've followed the instructions perfectly, even flashed the recommended rom..
Sent from my HTC One mini using Tapatalk
CNexus said:
That's incorrect, s-off, or security off, has nothing to do with system write protection, which is what you're referring to.
S-off gives you the ability to write low-level unsigned files to your device, such as bootloaders, splash images, etc.
The two are completely different things, and you can have one without having the other.
Click to expand...
Click to collapse
Not now there has been more development no, but this was the case with the m4 to start with, you couldnt do anything to the system without it, for example deleting a system app no matter what you done to delete it would just cause the phone to instantly reboot and the app still be there, i know this personally from experience with my own phone, thats why i said this.
CONdemmedNORmal said:
Not now there has been more development no, but this was the case with the m4 to start with, you couldnt do anything to the system without it, for example deleting a system app no matter what you done to delete it would just cause the phone to instantly reboot and the app still be there, i know this personally from experience with my own phone, thats why i said this.
Click to expand...
Click to collapse
Regardless, you're still not talking about the right thing. That has nothing to do with being S-ON/S-OFF. That's system write protection which is totally different.
CNexus said:
Regardless, you're still not talking about the right thing. That has nothing to do with being S-ON/S-OFF. That's system write protection which is totally different.
Click to expand...
Click to collapse
yes i know its different things BUT you couldnt write or delete from the system properly without s-off when development for the m4 FIRST started look through a few other threads you'll see what im saying is true so stop going on about something you obviously havent looked into properly, just because thats not the case now or not the case for other phones DOESNT mean it wasnt before, like i said i know from personal experience, that comment was posted months ago trying to give someone else info and is now irrelevant so whats the point in even bringing it back up now?????
Edit: unless your just trying to be picky because i didnt word it to your satisfaction so ill rewrite it here for you......
to update superuser/superSU, delete system apps or do anything to modify the system s-off was required to achieve this otherwise the system would just reboot and the changes that was attempted to be made wouldnt be accepted by the system.
happy??
CONdemmedNORmal said:
yes i know its different things BUT you couldnt write or delete from the system properly without s-off when development for the m4 FIRST started look through a few other threads you'll see what im saying is true so stop going on about something you obviously havent looked into properly, just because thats not the case now or not the case for other phones DOESNT mean it wasnt before, like i said i know from personal experience, that comment was posted months ago trying to give someone else info and is now irrelevant so whats the point in even bringing it back up now?????
Edit: unless your just trying to be picky because i didnt word it to your satisfaction so ill rewrite it here for you......
to update superuser/superSU, delete system apps or do anything to modify the system s-off was required to achieve this otherwise the system would just reboot and the changes that was attempted to be made wouldnt be accepted by the system.
happy??
Click to expand...
Click to collapse
Obviously yesterday was "months ago"
And I've looked into this to know what I'm talking about. System write protection is in the kernel and has absolutely nothing to do with S-OFF, no matter the device and the M4 is/was no different.
CNexus said:
Obviously yesterday was "months ago"
And I've looked into this to know what I'm talking about. System write protection is in the kernel and has absolutely nothing to do with S-OFF, no matter the device and the M4 is/was no different.
Click to expand...
Click to collapse
so me and everyone else that couldn't do anything to do with system writing, no matter what kernel without s'ing-off are liers??
and by months ago i mean the comment of mine you first commented on
Edit: besides i never said s-off and s-w-p was the same thing, i mearly said that at the time s-off was required for the ability to have the ability of writing to the system as at the time there wasnt any custom kernels which could achieve this, well stock kernels anyways due to lack of the release of the source code, but i cant be bothered to respond to you anymore all its doing is spamming the thread needlessly, i know what im on about due to like i said dealing with it myself.
Ergo Proxy said:
I'm on hboot 2.21, stock odex stock rom 4.4.2 rooted but for some reason, renove or rumrunner doesn't work for me. Rumrunner gets stuck on 8 out of 40 or something after rebooting. Renove gives me -1 or -2 error and doesn't s-off, can anyone tell me what's wrong? I've followed the instructions perfectly, even flashed the recommended rom..
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
bump
nitrox1 said:
bump
Click to expand...
Click to collapse
I'd try firewaters universal s-off tool. If this or any other s-off tool isn't working.
Sent from my HTC0P4E1 using Tapatalk
xXminiWHOOPERxX said:
I'd try firewaters universal s-off tool. If this or any other s-off tool isn't working.
Sent from my HTC0P4E1 using Tapatalk
Click to expand...
Click to collapse
Tried, rumrunner,revone, firewater nothing. Does moonshine work?
Sent from my HTC One_M8 using XDA Premium HD app
i got this pm and i thot it was worth everyone to see. while i do not recomend turning any device s on,a verizon device that is not unlockable via htcdev is of much more importance,as the only thing that can rescue it is a new enough,signed RUU.
it really is not worth the risk,i promise.
nicholi2789 said:
scotty1223 said:
nicholi2789 said:
Hey there, Sorry to bother you with a PM like a noob, but I just have a quick question for you. I have just received a Certified like new replacement M8 from Verizon because my original one had a manufacturer defect. My original one was S-OFF, rooted, with custom recovery and the latest firmware (1.55.605.2) from Verizon. I'm trying to get it back to as close to stock as possible so Verizon doesn't try and say I modified it and mak me pay for it. I already un-rooted it, flashed stock recovery, and took the latest OTA so my radios match my software version. Then I followed this thread: http://forum.xda-developers.com/showthread.php?t=2708571
to re-lock the bootloader and set the lock status flag. It says locked again in fastboot.
The only thing I have left is the S-OFF that displays in fastboot. I'm trying to find a way to reset that, or at least modify it so it shows S-ON. That way if by some weird chance a Verizon employee boots it to fastboot it will show completely stock and S-ON.
Now i've found this thread: http://forum.xda-developers.com/showthread.php?t=2475216 for resetting the S-OFF flag. I posted in it and asked if it would work on the M8 and nobody could give me an answer. XDA member brymaster5000 told me to ask you and that you could provide an answer.
So finally, my question is, will this fastboot command "fastboot oem writesecureflag 3" work to set my M8 back to S-ON? I know it works on the M7 but nobody can tell me for sure on the M8.
Thanks alot for your time.
Nick
Click to expand...
Click to collapse
I would very strongly recommend that you do not turn s on. Phones came s off ,so leaving out that way is not an issue.
Turning s on may open a can of worms that you cannot recover from,and then you're paying for a phone for sure.
As long as your stock rom, recovery and locked you're good to go
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
What do you mean phones came s-off? Verizon sent people m8s that already were s-off? It just seems like a super obvious indication that the device was modified. Your not the first person that has said that going back to s-on is a bad idea, so I will listen and not tempt fate. But iam curious, What can happen by doing that command that could cause such problems? And don't stock RUUs return you to s-on? Or do they just reset everything else but s-off?
Click to expand...
Click to collapse
before any phone is released,batches are sent off to testers and these devices are always s off. i have owned several factory s off devices,and there is no way of proving the phone you have did not come this way. further, large phone resellers are able to use factory htc diagnostic files to clear security data(sim lock,s off,cid/mid),wich again is a legitimate reason a phone is s off.finding s off in the bootloader is not by any means a "super obvious" indication of having been messed with.
turning the phone s on could cause the tampered flag to reset(we dont completely understand all the things that trip it) or you could end up locked into bootloader with a security warning if the boot,system or recovery are not stock enough. either of these things ARE super obvious indicators that you have messed with it,and tried to hide it.
in the case of the security warning,the only course of action is to:
1)run a signed ruu(wich must meet many criteria since youre now s on)
or
2)re-unlock the bootloader. as you know,using htcdev to unlock is not possible with vzw
an ruu does not change/update the partition where the secutity flag lives and thus will NOT turn you s on.
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
wtoj34 said:
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
thunderbls said:
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
Click to expand...
Click to collapse
You have missed the point... If you are locked into the bootloader with a security warning and s-on, you can not use weak sauce and firewater
Sent from my HTC One VX using Tapatalk
People need to realize that verizon reps and techs see hundreds of phones, they don't know the details of every device. The security and bootloader status is obvious to us because it's our device and we know everything about it. To a samsung person they won't know WTF your talking about.
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
scotty1223 said:
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
Yes, I misinterpreted the comment as general ease of use which makes me look like an idiot given the reason for the response.... my apologies and note to self read xda after nap lol.
l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
scotty1223 said:
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
Click to expand...
Click to collapse
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
l7777 said:
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
Click to expand...
Click to collapse
I agree completely.
Sent from my HTC One using Tapatalk
scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
dottat said:
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
How do you reset tampered?
scotty1223 said:
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
Paulb787 said:
How do you reset tampered?
Click to expand...
Click to collapse
Search this forum for a thread. I'm at work, I can't link it at the moment
Sent from my HTC One VX using Tapatalk
scotty1223 said:
So far, no m8 ruus yet. Hopefully some start popping up.
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
nicholi2789 said:
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
Click to expand...
Click to collapse
I didn't mean to embarrass you. They were good questions I thot everyone should read. I should have asked you,and can edit them if you wish.
Sent from my HTC PG09410 using Tapatalk 2
scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Nah I wasn't really embarrassed. Haha. I just meant that it's slightly embarrassing that I knew so little about HTC devices, but not a big deal or anything. You were right to post it though, there is some good information there that will do lots of people good.
dottat said:
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Definately a great rescue resource. I just want to make sure that folks understand that since it is unsigned,it will do them no good if they are s on,and stuck in bootloader with a security warning.
As you said,they must stay s off to benefit.(further supporting the point of this thread- don't turn s on)
Sent from my HTC PG09410 using Tapatalk 2
I was going to relock/S-On my defective M8 before returning it. I didn't have time though, and ended up just sending back only wiped and un-rooted, although I don't think /system was 100% stock. VZW sent me a text:
VZW FREE MSG: Thank You! The defective device you recently returned has been received by Verizon Wireless.
Click to expand...
Click to collapse
That was several weeks ago, haven't heard a thing since. I'm assuming they didn't care it was unlocked, or they are very slow at processing the devices.
I was annoyed at having to look at the red text after flashing the recently released MM firmware so I thought I would share this modified hboot.img where I removed it.
A faux hboot was also requested which falsely shows locked & s-on. It's unclear what exactly people want this for but I discourage using this to sell or return a phone under the false pretenses of it being bone stock, locked, s-on. There are steps you can take to properly achieve that.
These have been tested with fastboot (RUU mode) but the sdcard method (0p6bimg.zip on the root of removable storage) should work just fine.
Downloads
6.21.605.3 hboot with red text removed
https://www.androidfilehost.com/?fid=24438995911975964
6.21.605.3 faux hboot with red text removed, locked, s-on
https://www.androidfilehost.com/?fid=24457741883932708
Credits
Shout out to @Tigerstown for a little bit of hand holding and for being a generally cool dude.
These were made by starting with the firmware files posted by @dottat found here:
http://forum.xda-developers.com/verizon-htc-one-m8/development/stock-m-firmware-nand-recovery-t3330972
Directions
boot into bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
wait for flashing process to complete
fastboot reboot-bootloader
fastboot reboot
profit
Glad to see you got it. I'll go ahead and close my thread and link them here.
Very appreciated guys!
Sent using XDA One
Will this work by placing file in SD ext and changing file name to 0P6BIMG?
eriknors said:
Will this work by placing file in SD ext and changing file name to 0P6BIMG?
Click to expand...
Click to collapse
Yeah, exactly how I always flash them
Any chance a faux locked bootloader can be made? They come in handy when needing to show a vzw rep ur phone to prove its "stock"
eriknors said:
Any chance a faux locked bootloader can be made? They come in handy when needing to show a vzw rep ur phone to prove its "stock"
Click to expand...
Click to collapse
Maybe. I'm curious to look into this as well. No promises as this seems at least a little more involved and the last thing I'm gonna do is brick my (or someone else's) phone just for the sake of satiating my budding curiosity.
Sweet. Thanks.
This is always the first thing I'm looking for after a firmware update. Thank you!
Sent from my m8wl using Tapatalk
THIS!!
v1ral said:
THIS!!
Click to expand...
Click to collapse
Evocm7 said:
This is always the first thing I'm looking for after a firmware update. Thank you!
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
schneid said:
Sweet. Thanks.
Click to expand...
Click to collapse
Looking like people are very happy you contacted me to help you do your own. Now everyone wins...nice contribute to community
cntryby429 said:
Maybe. I'm curious to look into this as well. No promises as this seems at least a little more involved and the last thing I'm gonna do is brick my (or someone else's) phone just for the sake of satiating my budding curiosity.
Click to expand...
Click to collapse
If your interested in doing this I'm more then willing to help you, if you even need it.
eriknors said:
Any chance a faux locked bootloader can be made? They come in handy when needing to show a vzw rep ur phone to prove its "stock"
Click to expand...
Click to collapse
Added faux locked s-on noredtext hboot to OP.
Working Perfect...!!!
Thank you... :highfive:
Does this work on all variants? I have an international GSM and want to give it to HTC to get a new battery. That red screen might get them un s-offing me.
I have a question...
What did you do to make it work through the SD card method, I am trying to change my splash screen without using ADB.
v1ral said:
I have a question...
What did you do to make it work through the SD card method, I am trying to change my splash screen without using ADB.
Click to expand...
Click to collapse
It's simply a matter of zipping up the file(s) you want flashed that have been named correctly alongside an android-info.txt file that matches you phone. If you download one of the firmware files I linked to you can see what the correct filenames are. I think the splash screen are named splash1.<something>.
The android-info.txt file doesn't actually say anything about the other files alongside it to be flashed. It serves as a sort of validation check that the whole zip is meant for the phone. My zips only contain the hboot while the ruus have like 15 files but the android-info.txt files are identical.
A proper android-info.txt file + correctly named files + being zipped = sd card OR RUU mode flashable.
Will this work on a S-ON device ? I kinda wanna get rid of the red text at boot...but my device is S-ON
dodgedroid said:
Will this work on a S-ON device ? I kinda wanna get rid of the red text at boot...but my device is S-ON
Click to expand...
Click to collapse
No it will not. How did you end up with the red text but s-on? Is it a vzw device?
Nope, it's Internation GSM variant
dodgedroid said:
Nope, it's Internation GSM variant
Click to expand...
Click to collapse
An unlocked bootloader only gives you access to flash unsigned files to a few partitions like boot (kernel) and system, probably another one or two.
S-off is required to flash unsigned files to other partitions like hboot. Not to mention, the files in this thread are specific to the vzw hboot so even if you could flash them I wouldn't recommend it.