Putting this here so people who want/need it can find it.
MD5 is on the download page.
http://d-h.st/bQF
thanks man! anything on kernel source?
dsb9938 said:
Putting this here so people who want/need it can find it.
MD5 is on the download page.
http://d-h.st/bQF
Click to expand...
Click to collapse
its possible to find for international Ruu?
Will this ruu work to get the phone back to s-on and back to stock?
droidrev71 said:
Will this ruu work to get the phone back to s-on and back to stock?
Click to expand...
Click to collapse
If you do it properly, these files will get you back to full on stock, yes.
dsb9938 said:
If you do it properly, these files will get you back to full on stock, yes.
Click to expand...
Click to collapse
Thank you. I'll do a search on instructions after lunch
Edit: do i Fastboot oem rebootruu then Fastboot the zip in the link?
droidrev71 said:
Thank you. I'll do a search on instructions after lunch
Edit: do i Fastboot oem rebootruu then Fastboot the zip in the link?
Click to expand...
Click to collapse
Pretty sure it's something like that, but please find a good guide, I have never done it myself and I don't want you to screw up your phone.
afsandiego said:
thanks for this..
a few more questions..
How do I actually use it?
does this pretty much turn s-on and locked the bootloader and remove the twrp?
Click to expand...
Click to collapse
dsb9938 said:
Pretty sure it's something like that, but please find a good guide, I have never done it myself and I don't want you to screw up your phone.
Click to expand...
Click to collapse
..
scotty1223 said:
anyway,you can flash it just like described for the radio:
-place phone in fastboot,open cmd. file must be in your adb/fastboot working directory
-enter:
fastboot erase cache
fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error after after flashing hboot,radios or other firmware. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot. should also rescue you if for some reason the file wont flash)
-reboot back to the OS
fastbooot reboot
Click to expand...
Click to collapse
I used this instruction with the RUU file on this thread and I was able to get back to stock but bootloader is still Unlocked and S-OFF.
Anyone knows how to turn back S-ON?
afsandiego said:
I used this instruction with the RUU file on this thread and I was able to get back to stock but bootloader is still Unlocked and S-OFF.
Anyone knows how to turn back S-ON?
Click to expand...
Click to collapse
Just Flip the Flag. You can use Scott1223's Thread on changing the flag.
It doesn't Lock the device again but it does report locked on the Bootloader fastboot mode. This has been enough for warranty reasons for Verizon.
http://forum.xda-developers.com/showthread.php?t=2540004
I have GUI for Verizon/Sprint versions on Stock Rom.
http://forum.xda-developers.com/showthread.php?t=2618407
Thanks,
DeadPhoenix said:
Just Flip the Flag. You can use Scott1223's Thread on changing the flag.
It doesn't Lock the device again but it does report locked on the Bootloader fastboot mode. This has been enough for warranty reasons for Verizon.
http://forum.xda-developers.com/showthread.php?t=2540004
Click to expand...
Click to collapse
Can you please stop telling people it does not lock the bootloader. I have quoted the text below in reply to you at least once before. Setting the flag back to "Locked" does tell the bootloader to be locked. It is not just displaying locked. Someone is going to try to modify something thinking their bootloader isnt truly locked after accomplishing the below when it is.
scotty1223 said:
not sure what youre asking. locked is locked... this leaves the "lock status" flag that tells hboot wether to be unlocked or not, in a locked state,just as it came out of the box.
if you mean "does the lock status flag need to tell hboot to be locked in order for the fingerprint scanner to work" then the answer is yes. hex editing hboot to make the unlocked banner read "locked" does absolutely nothing functionally. whatever partition controls the fingerprint scanner is looking at the lock status flag itself,and could care less what hboots banner reads
Click to expand...
Click to collapse
Jiggity Janx said:
Can you please stop telling people it does not lock the bootloader. I have quoted the text below in reply to you at least once before. Setting the flag back to "Locked" does tell the bootloader to be locked. It is not just displaying locked. Someone is going to try to modify something thinking their bootloader isnt truly locked after accomplishing the below when it is.
Click to expand...
Click to collapse
Let's attack this from another angle.
S-OFF = Secure Bootloader = Accessing Partitions normally not accessible (i.e. Radio and Hboot partition access) Flips the Hex code of the Bootloader Flag to Unlocked
Bootloader Flag = Bootloader hex code used by internal device partitions to determine device hardware compliance and functionality.
First off s-off does NOT equal unsecure bootloader (which Im assuming is what you meant). They are separate and distinct. You must s-off to be able to unlock the bootloader.
---------- Post added at 10:53 AM ---------- Previous post was at 10:49 AM ----------
Moved to correct thread.
http://forum.xda-developers.com/showthread.php?t=2540004
Jiggity Janx said:
First off s-off does NOT equal unsecure bootloader (which Im assuming is what you meant). They are separate and distinct. You must s-off to be able to unlock the bootloader.
---------- Post added at 10:53 AM ---------- Previous post was at 10:49 AM ----------
Moved to correct thread.
http://forum.xda-developers.com/showthread.php?t=2540004
Click to expand...
Click to collapse
If you would like to discuss further please take this to PM.
This is a dev forum and discussions like this should happen in the thread to which it pertains. I cant be the only one that will want to know this very important piece of information and its background. Scotty has noted he will reply later time permitting. I am ok with being wrong based on my understanding and information provided but this needs to be out there.
This is not complicated. There is a locked/unlocked flag, and a secure/insecure flag for S-Off.
They are not the same. You need to turn both to get back to stock.
I have not tried going back to S-On, but I do lock/unlock frequently.
The fingerprint scanner stops working when unlocked, and I cannot fastboot flash certain things to test when locked.
As for how you get either of these to be in either state, yes, that is a topic for another thread.
Is it possible for me to use the Verizon RUU to convert my Sprint One max to Verizon stock software similar to how people are able to convert the HTC one to Google Play edition?
Hopefully they want delete this thread.
Also what does it mean when you say decrypted.
dsb9938 said:
This is not complicated. There is a locked/unlocked flag, and a secure/insecure flag for S-Off.
They are not the same. You need to turn both to get back to stock.
I have not tried going back to S-On, but I do lock/unlock frequently.
The fingerprint scanner stops working when unlocked, and I cannot fastboot flash certain things to test when locked.
As for how you get either of these to be in either state, yes, that is a topic for another thread.
Click to expand...
Click to collapse
I'm by no means am a developer, but this is accurate. I had the HTC Incredible and sold it on Craigslist a few years later. To restore it to complete stock, I had to use the Stock RUU, lock the bootloader, and turn S-On. However, I've heard of some people buying a brand new device with S-Off from the factory. Both of my HTC devices were S-On. I used rumrunner to S-Off my One Max and Revoked to S-Off my original Incredible.
With that said, is there a guide/tool to turn S-On with our One Max? Just for information purposes.
TappEd from my Note II
Check out my website for encouragement....
www.projectintercession.blogspot.com
Related
I'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Watercycle said:
I'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Click to expand...
Click to collapse
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
a.mcdear said:
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
Click to expand...
Click to collapse
unguarded or super user? and thank you i didn't know about that =)
Watercycle said:
unguarded or super user? and thank you i didn't know about that =)
Click to expand...
Click to collapse
Sueperuser not unguarded
this is the most rediculous process ever! (currently trying to wire trick) I'VE USED 2 DARN TYPES OF WIRE AND A PAPERCLIP AND NONE OF THEM DO ANYTHING
oh god, whew... i was running around the house making a wire out of everything...
but after trying the paperclip for like the 8th time (which took a half hour to find) it seems to have worked
S-off is the most stressful android activity ever >XO
thanks you two <3
You did use the ics jb hboot right? Make sure you can see the sd card? And don't unlock your phone again. You would need to s-on then s-off again for it to say locked. I just woke up and saw your new posts, its been a long day but I see you got help. Welcome to the club, glad it finally worked.
sent from my Clean Rezound
I used the Hboot that came with 3.14 Ruu, if S-off took the "relocked" away then i'm happy, if it didn't, oh well, but I was unlocked when I started the process =o
As long as you don't unlock it after s-off, it will be locked again ( although it says "juopunutbear" instead of "locked" if you're using their modified boot. Just flash a stock one and it will say locked)
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The patched hboot adds some advanced fast boot commands. However everything will work without the patched hboot. You don't need it its just nice to have
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
ericsignals said:
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
Click to expand...
Click to collapse
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Forgot to add that part when I typed the adb part ....thanks for correcting me.:thumbup:
Sent from my Rezound
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Watercycle said:
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Click to expand...
Click to collapse
Yes, but there are ways around that
I personally just package my own ph98img.zips if I need to flash a kernel or recovery after doing something dumb
Sent from my ADR6425LVW using Tapatalk 2
If you want to add the JB Hboot, it is very simple. You can go to their site and just download the most recent hboot. You must know if you are ICS or GB. But go here: http://unlimited.io/hboot-downloads/ and download the right one, either vigor ics or vigor gb. Put that in the folder where you had put the original controlbear program and follow these instructions:
To flash the JuopunutBear hboots
Put the phone in fastboot mode, connected to the pc and enter the following commands
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
Thats all there is to it and you can now benefit from the JB Hboot.
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Yes you need to be unlocked. It's part of the prerequisites. Please read then reread the thread in general "s-off with instructions...it's official". Understand how to avoid problems and fix them if they arise. It's very easy but it's like people half ass reading the instructions recently. Don't be that person.
sent from my Clean Rezound
th3rapist said:
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Click to expand...
Click to collapse
You have to unlock befor you s off, afterwards it's redundant to do so. But some people have
Sent from my ADR6425LVW using Tapatalk 2
doubleshot, ruby ICS, vigor ICS, holiday ICS, pyramid ICS?
which one? haha
I don't mind don't 1 more small flash that will probably be necessary in the future as long as it doesn't screw my current rom up
Hey,
I have a Telus Amaze 4G and I have lost my radio. Phone says it has an unknown Baseband/IMEI. Not sure where I went wrong/ lost my radio but this is a run down of what I've done to my handset so far:
- Rooted
- Flashed CWM recovery.
- Flashed EnergyRom.
- Sent phone to HTC because of suspected warranty issue. (Wouldn't Charge)
- Phone returned un-repaired from HTC.
- Charged battery externally, phone finally booted.
- Replaced CWM with 4EXT.
- Ran the Telus GB RUU exe from windows.
- Did the OTA ICS from the phone.
- Attempted upgrade to SpeedRom, failed because the OTA had failed, didn't realize this until the next around, this is where I think it went wrong. Had done a full wipe of all partitions, except SD from 4EXT in the process.
- Re-applied original Telus GB RUU.
- Re-applied Telus ICS OTA. this is when I realized I had no radio. I had not put in my SIM-Card since the phone was returned from HTC so not exactly sure when it stopped working but the OTA had installed correctly this time.
- Re-rooted.
- Did the wire-trick and obtained S-OFF.
- Flashed the latests JP hboot.
- Used fastboot to flash several radio.img files from various TMO and Telus RUUs, nada.
- Flashed the T-Mobile ICS RUU via hboot, still no radio.
- Extracted the rom from the Telus GB RUU and applied that via hboot, still no radio.
The only thread I could find where someone had mentioned the missing baseband on an amaze 4g, the only suggested fix was to reflash a stock, GB rom but that didn't work. Now I am at a loss at to what I could try next.
Any suggestions would be greatly appreciated.
found this thread fro you maybe that will help you get a idea http://forum.xda-developers.com/showthread.php?t=1627565
Jay_Rulen said:
found this thread fro you maybe that will help you get a idea http://forum.xda-developers.com/showthread.php?t=1627565
Click to expand...
Click to collapse
He means the built in antenna radio software drivers. Your best call would be warranty replacement, probably a bad chipset issue.
Dark Nightmare said:
He means the built in antenna radio software drivers. Your best call would be warranty replacement, probably a bad chipset issue.
Click to expand...
Click to collapse
Not cool.... so Telus/HTC already know that I've had third party software on my handset after I returned it the last time. If I was to reverse *everything* I've done, do you think I could get it back to a point in which they would still honor the warranty?
Thanks!
inluck said:
Not cool.... so Telus/HTC already know that I've had third party software on my handset after I returned it the last time. If I was to reverse *everything* I've done, do you think I could get it back to a point in which they would still honor the warranty?
Thanks!
Click to expand...
Click to collapse
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Okay, I can totally do all that. One last question though, when my phone was last returned to HTC, they discovered I had 3rd party software on the phone and refused to look at it any further, do you think this will have an effect on a second return?
inluck said:
Okay, I can totally do all that. One last question though, when my phone was last returned to HTC, they discovered I had 3rd party software on the phone and refused to look at it any further, do you think this will have an effect on a second return?
Click to expand...
Click to collapse
I can't say, just keep your fingers crossed that it doesn't.
Dark Nightmare said:
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Know off the top of your head how to remove the *RELOCKED* from the bootloader?
inluck said:
Know off the top of your head how to remove the *RELOCKED* from the bootloader?
Click to expand...
Click to collapse
How did you lock the bootloader? Manually or via hasoons tool? Did you s-on as yet or still s-off?
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
How did you lock the bootloader? Manually or via hasoons tool? Did you s-on as yet or still s-off?
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
I had extracted the rom.zip from the Telus GB RUU and flashed it to the handset from hboot. This removed the jp hboot and put it back to stock.
I then booted into fastboot and issued these commands from the cli:
fastboot.exe oem lock
fastboot.exe oem writesecureflag 3
So to answer your questions, manually and I am now S-ON.
I get the feeling I need to issue those commands from the jp hboot instead of the stock. Am I right?
inluck said:
I had extracted the rom.zip from the Telus GB RUU and flashed it to the handset from hboot. This removed the jp hboot and put it back to stock.
I then booted into fastboot and issued these commands from the cli:
fastboot.exe oem lock
fastboot.exe oem writesecureflag 3
So to answer your questions, manually and I am now S-ON.
I get the feeling I need to issue those commands from the jp hboot instead of the stock. Am I right?
Click to expand...
Click to collapse
You should've made sure the bootloader said locked first -_-, oh well, unless you wanna s-off again, hope they don't make an issue out of it. Why did you put exe at the end of fastboot? You did it before s-on, it should say locked, odd.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
You should've made sure the bootloader said locked first -_-, oh well, unless you wanna s-off again, hope they don't make an issue out of it. Why did you put exe at the end of fastboot? You did it before s-on, it should say locked, odd.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
It said relocked, I wasn't sure at which point that was supposed to disappear/changed.
I'll S-OFF again once the thing gets another charge.
I have a feeling it was because I was in the stock GB hboot and not the modified jb hboot.
Don't want to leave anything for them to complain about.
inluck said:
It said relocked, I wasn't sure at which point that was supposed to disappear/changed.
I'll S-OFF again once the thing gets another charge.
I have a feeling it was because I was in the stock GB hboot and not the modified jb hboot.
Don't want to leave anything for them to complain about.
Click to expand...
Click to collapse
It's not the hboot. I gotta find the s-on thread, since you have to be on a stock bootloader before you s-on. I probably missed something.
Sent from an Amaaaaaazing place :-D
http://forum.xda-developers.com/showthread.php?t=1647728
I just remembered another trick as well, when you s-off the device, it relock your bootloader but it says "locked" not relocked, therefore when you s-off, do not flash the jb hboot when they ask you if you wanna flash it, then simply s-on via the fastboot command, voila!
Sent from an Amaaaaaazing place :-D
hey yall i used the htc dev method to unluck the sprint 3d however when i do the flash recovery img in fastboot i get a failed remote not allowed- i have done this on other phones with no issue but i have tried every recovery.img with no luck . i also tried the PG86IMG but it just says either main version older or PARSING . ant help is MUCH appreciated.
ganjamatik said:
hey yall i used the htc dev method to unluck the sprint 3d however when i do the flash recovery img in fastboot i get a failed remote not allowed- i have done this on other phones with no issue but i have tried every recovery.img with no luck . i also tried the PG86IMG but it just says either main version older or PARSING . ant help is MUCH appreciated.
Click to expand...
Click to collapse
What exactly does your bootloader say? It sounds like it is not unlocked.
If you relocked to run the RUU.exe or take the OTA update it may not be locked now.
ramjet73
ramjet73 said:
What exactly does your bootloader say? It sounds like it is not unlocked.
If you relocked to run the RUU.exe or take the OTA update it may not be locked now.
ramjet73
Click to expand...
Click to collapse
its shows UNLOCKED and hboot 1.58 s-on
ganjamatik said:
its shows UNLOCKED and hboot 1.58 s-on
Click to expand...
Click to collapse
Hmmm...
Well, you won't be able to flash PG86IMG.zip files from the bootloader with S-ON unless thay are signed by HTC so that's probably your problem there.
The "remote not allowed" is usually an indication the bootloader is locked. Make sure your phone is in "fastboot usb" mode in the bootloader, then issue the following commands:
fastboot devices
fastboot flash recovery recovery.img (where "recovery.img" is the file name of your custom recovery)
What responses do you get?
ramjet73
it shows my device listed and then says the same remote not allowed-
Did you check usb debugging in your phone's settings first? Also if you have htc sync on your pc you may want to unistall it also. Some programs do interfere with fastboot.
ganjamatik said:
it shows my device listed and then says the same remote not allowed-
Click to expand...
Click to collapse
Can you try those fastboot commands again and copy and paste the actual output from the commands into this thread? Sometimes there is something in that which might give us a clue as to what the problem is.
Edit: Never mind. I saw you posted again in the other thread so you can wait for a response over there. Make 100% sure your bootloader is unlocked because sometimes flashing the unlock bin file doesn't take and the phone doesn't show the unlock option if you upgraded to ICS via the OTA. If nothing else works I would suggest relocking the bootloader and starting over with the RUU.exe, per the instructions in my root and S-OFF guide.
ramjet73
From the other thread
mpgrimm2 said:
My guess is that you are not really unlocked (Screenshot?) or you are not using a compatible recovery file/filename.
Have a look at the HTC Unlock Guide in my signature to see if anything stands out that you are overlooking.
Even if you get a recovery going, I'm not sure what your ultimate goal is here. You should continue this in one thread, specifically your Remote Not Allowed thread.
Click to expand...
Click to collapse
Go with Ramjet's suggestion if you don't figure it out.
can someone take a look at this and tell me if this device is truly unlocked. it says s-off, but there is no **UNLOCKED** banner at the top of the bootloader.
been through a world of crap with this device and dont want to do it again. Thanks in advance
drlzanej said:
can someone take a look at this and tell me if this device is truly unlocked. it says s-off, but there is no **UNLOCKED** banner at the top of the bootloader.
been through a world of crap with this device and dont want to do it again. Thanks in advance
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1889438&page=3 take a look at this
In other words with s-off an unlocked bootloader is irrelevant unless you still want to flash a recovery through fastboot. You can flash twrp recovery bootloader method, gain root and flash 4ext recovery through the app (highly recommended). Also should you need to have your phone serviced, it is essential to have your phones bootloader in "locked" state.
drlzanej said:
can someone take a look at this and tell me if this device is truly unlocked. it says s-off, but there is no **UNLOCKED** banner at the top of the bootloader.
been through a world of crap with this device and dont want to do it again. Thanks in advance
Click to expand...
Click to collapse
This almost seems like a troll thread lol, The OP is a senior member, with hundreds of thanks and has something to do with Bad Seed Customs, And has an S-off'd device, Asking such a sily question lol
It's all good though, Knowledge for the community [=
drlzanej said:
can someone take a look at this and tell me if this device is truly unlocked. it says s-off, but there is no **UNLOCKED** banner at the top of the bootloader.
been through a world of crap with this device and dont want to do it again. Thanks in advance
Click to expand...
Click to collapse
You can't really tell from the bootloader screen with the engineering hboot installed.
All the custom bootloaders (ENG, Revolutionary, JBear) hide the locked/unlocked/relocked status on the first line of the bootloader screen since they enable the fastboot commands that would normally require unlocking the stock bootloaders. There are two ways to determine the current status:
1. Flash a stock bootloader (1.4, 1.5, 1.58)
2. Run the "query_bootloader.zip" script from this post in recovery
A lot of users get confused about the difference between unlocking the bootloader (hboot S-OFF) and gaining radio S-OFF. I was confused myself until the light went on as explained in this post. It used to be that the only way to get the stock "locked" status back after doing the htcdev unlock was to do the wire trick, but now you can "flash" the "lock_bootloader.zip" file from the post linked in the #2 option above which uses a modified version of update-binary to reset the flag in the firmware.
ramjet73
Can't_Live_Without_My_Evo said:
This almost seems like a troll thread lol, The OP is a senior member, with hundreds of thanks and has something to do with Bad Seed Customs, And has an S-off'd device, Asking such a sily question lol
It's all good though, Knowledge for the community [=
Click to expand...
Click to collapse
ok thatbeing said, Let me clarify. The device is my wifes which i rooted and unlocked and handed over to her to do with what she will and havent really looked at it since so whatever she done to it , I have no idea. She borked something at some point so i decided I was going install another rom. was going to install an ICS rom, went to flash the firmware and found the bootloader in the state it was in. The last time i looked at that boot loader it said **REVOLUTIONARY**(I think it was revolutionary I dont remember) anyway, It wasnt the way it was before. So not being very familiar with this device Im not a person who will idioticaly flash something without asking first. Thank you for your reply tho.
ramjet73 said:
You can't really tell from the bootloader screen with the engineering hboot installed.
All the custom bootloaders (ENG, Revolutionary, JBear) hide the locked/unlocked/relocked status on the first line of the bootloader screen since they enable the fastboot commands that would normally require unlocking the stock bootloaders. There are two ways to determine the current status:
1. Flash a stock bootloader (1.4, 1.5, 1.58)
2. Run the "query_bootloader.zip" script from this post in recovery
A lot of users get confused about the difference between unlocking the bootloader (hboot S-OFF) and gaining radio S-OFF. I was confused myself until the light went on as explained in this post. It used to be that the only way to get the stock "locked" status back after doing the htcdev unlock was to do the wire trick, but now you can "flash" the "lock_bootloader.zip" file from the post linked in the #2 option above which uses a modified version of update-binary to reset the flag in the firmware.
ramjet73
Click to expand...
Click to collapse
Thank you sir for your response, Exactly what I was looking for. Later,,,,,,
unable to lock bootloader
ramjet73 said:
You can't really tell from the bootloader screen with the engineering hboot installed.
All the custom bootloaders (ENG, Revolutionary, JBear) hide the locked/unlocked/relocked status on the first line of the bootloader screen since they enable the fastboot commands that would normally require unlocking the stock bootloaders. There are two ways to determine the current status:
1. Flash a stock bootloader (1.4, 1.5, 1.58)
2. Run the "query_bootloader.zip" script from this post in recovery
A lot of users get confused about the difference between unlocking the bootloader (hboot S-OFF) and gaining radio S-OFF. I was confused myself until the light went on as explained in this post. It used to be that the only way to get the stock "locked" status back after doing the htcdev unlock was to do the wire trick, but now you can "flash" the "lock_bootloader.zip" file from the post linked in the #2 option above which uses a modified version of update-binary to reset the flag in the firmware.
ramjet73
Click to expand...
Click to collapse
guys will the same work on my htc desire v , i am unable to reset from relocked to locked. i need to apply for warranty as my phone gets restarted every now and then and the htc service center guys are telling that i have void the warranty
I was previously on the original HBOOT (first one) and S-Off.
I did NOT have the "TAMPERED" flag on my phone.
After upgrading to latest release I am on the latest HBOOT but now it's also flagged as "TAMPERED".
My understanding is being S-off a way to remove this should exists.
I've never done the HTC unlock as have always been S-Off.
Is it possible to get this removed on latest release without being 100% stock?
I know on some phones like the One you can modify a flag in one of the partitions.
I am on a stock rom just rooted so beyond seeing that flag it's not obvious I am rooted.
Thx
See this post
http://forum.xda-developers.com/showthread.php?p=50112366
Captain has included this mod l
Sent from my EVO using xda app-developers app
JManekia said:
See this post
http://forum.xda-developers.com/showthread.php?p=50112366
Captain has included this mod l
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Nope, he says:
Q8: My bootloader says "TAMPERED" after flashing the firmware. How to fix?
A: Just ignore it. It's no big deal.
Someone did a mod to remove the developer text but that's it. My understanding is the flag doesn't reside in the HBOOT directly but in some other area of the phone?
Run a RUU. It will remove the *TAMPERED* status. Your phone will remain unlocked, and it be displayed as such.
If you don't have easy access to a PC, one of the easiest solutions is to download the VipeRUU zip to your phone, extract the rom.zip to your ext SD, rename it to PJ75IMG.zip, and flash it through the bootloader. The next time that you reboot into the bootloader after the process is completed, then TAMPERED should be gone.
I'm just speculating, but maybe you removed the tampered status before by using the Regaw Bootloader Customizer, which only edits the bootloader info, and doesn't actually change anything for the phone itself. It's only a cosmetic change.
aarsyl said:
Run a RUU. It will remove the *TAMPERED* status. Your phone will remain unlocked, and it be displayed as such.
If you don't have easy access to a PC, one of the easiest solutions is to download the VipeRUU zip to your phone, extract the rom.zip to your ext SD, rename it to PJ75IMG.zip, and flash it through the bootloader. The next time that you reboot into the bootloader after the process is completed, then TAMPERED should be gone.
I'm just speculating, but maybe you removed the tampered status before by using the Regaw Bootloader Customizer, which only edits the bootloader info, and doesn't actually change anything for the phone itself. It's only a cosmetic change.
Click to expand...
Click to collapse
That's what I did - noticed after the 4.3 RUU that it went from "Unlocked/Tampered" to just "Unlocked." I kinda want to also modify the "Unlocked" text as I did before with Regaw's tool, I'll have to look into whether it will work.
SilverZero said:
That's what I did - noticed after the 4.3 RUU that it went from "Unlocked/Tampered" to just "Unlocked." I kinda want to also modify the "Unlocked" text as I did before with Regaw's tool, I'll have to look into whether it will work.
Click to expand...
Click to collapse
There's a reason why I didn't suggest using that tool. You kinda need to MAKE SURE that you know your bootloader status. If you activate S-On twice in a row, that baby's definitely gonna brick. I rather know what my bootloader is supposed to say, because I'm really the only person looking at it. What difference will it really make?
aarsyl said:
There's a reason why I didn't suggest using that tool. You kinda need to MAKE SURE that you know your bootloader status. If you activate S-On twice in a row, that baby's definitely gonna brick. I rather know what my bootloader is supposed to say, because I'm really the only person looking at it. What difference will it really make?
Click to expand...
Click to collapse
Well that's why I said I'd have to look into it. I assumed it wouldn't work with the new HBOOT, and I guess I don't care one way or the other. But for anybody else reading this, don't try it.
On the other hand, I climb mountains because they're there. If I want it to say "Hacked" instead of "Unlocked" and I can do it without screwing things up, I might do it just to screw with the guy who buys it from me down the road.
bryanu said:
I was previously on the original HBOOT (first one) and S-Off.
I did NOT have the "TAMPERED" flag on my phone.
After upgrading to latest release I am on the latest HBOOT but now it's also flagged as "TAMPERED".
My understanding is being S-off a way to remove this should exists.
I've never done the HTC unlock as have always been S-Off.
Is it possible to get this removed on latest release without being 100% stock?
I know on some phones like the One you can modify a flag in one of the partitions.
I am on a stock rom just rooted so beyond seeing that flag it's not obvious I am rooted.
Thx
Click to expand...
Click to collapse
comment withdrawn after further investigation.
redm1st said:
Originally for Hboot 2.09 but should work for Hboot 2.10. (don't quote me on that though)
Click to expand...
Click to collapse
Please don't anyone on the 2.10 HBOOT flash this! Please remove this attachment.
EDIT: This post is what I mean. You have to understand what the Bootloader Customizer actually does (which is explained in the thread) and know that flashing this would bork all the things. This is literally a 2.09 HBOOT. The 2.10 HBOOT is what accommodates the new partition layout, so flashing this will break that and prevent the device from booting up. The issue is the signed boot.img. That's why you see the tampered flag. I assume you're not using my stock rooted? You updated directly from RUU, and then rooted it manually? The signed boot.img sees unsigned recovery img and throws up that tampered flag. It's not going to affect the working of the device, so why worry about it? You can flash the boot image from my stock rooted if you want it to go away.
Captain_Throwback said:
Please don't anyone on the 2.10 HBOOT flash this! Please remove this attachment.
EDIT: This post is what I mean. You have to understand what the Bootloader Customizer actually does (which is explained in the thread) and know that flashing this would bork all the things. This is literally a 2.09 HBOOT. The 2.10 HBOOT is what accommodates the new partition layout, so flashing this will break that and prevent the device from booting up. The issue is the signed boot.img. That's why you see the tampered flag. I assume you're not using my stock rooted? You updated directly from RUU, and then rooted it manually? The signed boot.img sees unsigned recovery img and throws up that tampered flag. It's not going to affect the working of the device, so why worry about it? You can flash the boot image from my stock rooted if you want it to go away.
Click to expand...
Click to collapse
I flashed everything from your post.
I just want the word Tampered gone, don't care if it's done officially or just visually through some other mod.
I currently am S-Off, Locked and says Tampered.
bryanu said:
I flashed everything from your post.
I just want the word Tampered gone, don't care if it's done officially or just visually through some other mod.
I currently am S-Off, Locked and says Tampered.
Click to expand...
Click to collapse
Do a nandroid and then unlock your bootloader.
Captain_Throwback said:
Do a nandroid and then unlock your bootloader.
Click to expand...
Click to collapse
So I have "Tampered" because I am not unlocked?
Take this from a guy who has had 6 replacement phones and 4 of them hard bricked. QualcomDownload Mode. Lol.
Anyways I wanted to get rid of the tampered flag so I did what shouldnt be done and used the One's tool with aroma and only chose to remove rltampered flag.
It worked.
Note that that was my other phone before I hard bricked it but that was because I messed up my EFS folder.
Im not saying that anyone should use it. Do at your own risk I sure did and I just used it on my replacement evo after doing soff.
Sent from my EVO using Tapatalk
chemjb said:
Take this from a guy who has had 6 replacement phones and 4 of them hard bricked. QualcomDownload Mode. Lol.
Anyways I wanted to get rid of the tampered flag so I did what shouldnt be done and used the One's tool with aroma and only chose to remove rltampered flag.
It worked.
Note that that was my other phone before I hard bricked it but that was because I messed up my EFS folder.
Im not saying that anyone should use it. Do at your own risk I sure did and I just used it on my replacement evo after doing soff.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I had already given up and just installed terminal emulator on my phone and ran the following as su:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
that got rid of it properly without requiring any flashing, fake boot loader modifications etc.
@bryanu: just for my own education, what does that actually do when you type that in terminal. Meaning, I know you said it removes the "tamper" word, but how does it do it. If it is to lengthy to answer, no problem. Just wondering... Thanks!
Sent from my EVO using Tapatalk 2
puhiniho said:
@bryanu: just for my own education, what does that actually do when you type that in terminal. Meaning, I know you said it removes the "tamper" word, but how does it do it. If it is to lengthy to answer, no problem. Just wondering... Thanks!
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
It resets the flag that controls that showing or not essentially.
bryanu said:
I had already given up and just installed terminal emulator on my phone and ran the following as su:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
that got rid of it properly without requiring any flashing, fake boot loader modifications etc.
Click to expand...
Click to collapse
Worked like a charm ,
Thanks