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
Related
Is this root method like unrevoked forever? Is this at the radio level or just a hacked hboot?
If later on, an OTA gets applied, will the phone still be s-off so I can just flash a recovery again?
Please don't respond 'dont take OTAs', because that's not what I'm asking.
Sent from my PC36100 using XDA App
From what I have read it is at the radio level and OTA's shouldn't affect s-off.
vandon1 said:
Is this root method like unrevoked forever? Is this at the radio level or just a hacked hboot?
If later on, an OTA gets applied, will the phone still be s-off so I can just flash a recovery again?
Please don't respond 'dont take OTAs', because that's not what I'm asking.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
From that page:
What does this do, then?
revolutionary will give you S-OFF either by a patched HBOOT or setting the secureflag to off on the device itself. This behaviour will depending on your particular device. Optionally it will also replace the stock Android recovery with a custom one, which adds many features including “nandroid” backups, the ability to use custom ROMs, and a greater amount of flexibility and customization of your Android phone.
Does this permanently unlock the NAND flash on my phone?
Yes. The default configuration of this tool disables the phone's security, which also disables the NAND locks placed on the storage by the bootloader.
All the info I know about is right there.
I also found this, which I'm not positive if this applies to our method, but I think it does. Interesting none the less: http://alpharev.nl/
From what I understand, S-off will remain no matter what, until you issue a fastboot command that is "fastboot oem setsecureflag3" You can see here : http://forum.xda-developers.com/showthread.php?t=1194053 for a full tut on how to turn it back to S-on. SO yea, it's similar to unrevoked forever, where you're always S-off until you deliberately set it to S-on. Running an RUU doesn't even set it to S-on.
That all said, even though you said "don't tell me not to take OTA", I will remind you anyways, that it's always a sketchy thing, especially if HTC has included a new hboot in that OTA. To each their own though.
Thanks for the info, I missed that on the unrevoked site.
However, if it's S-Off in the radio, doesn't that mean that the hboot won't really matter? On the evo 4g at least, new hboots don't kill the s-off and you could always reflash a recovery from hboot.
I'm just wondering if you can flash a recovery with s-off from a stock hboot.
k2buckley said:
Running an RUU doesn't even set it to S-on.
Click to expand...
Click to collapse
Are you sure? I read this in the AlphaRev FAQ's
As soon as you decide to flash a stock RUU that has a HBOOT update in it, this hacked HBOOT will be overwritten.
Click to expand...
Click to collapse
This is interesting, as I have been wondering how to get S-ON after running Revolutionary, should I need to take my device in for repairs.
What's your take on it?
mattchew86 said:
Are you sure? I read this in the AlphaRev FAQ's
This is interesting, as I have been wondering how to get S-ON after running Revolutionary, should I need to take my device in for repairs.
What's your take on it?
Click to expand...
Click to collapse
I hear "fastboot oem setsecureflag3" works wonders.
Good info. Thanks
Sent from my PG86100 using Tapatalk
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
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
Hello. Never made a thread before and was really hoping I wouldn't have to or would find an answer elsewhere.
Since that didn't work out, here's my problem:
Background: Evo 3d, virgin mobile, unlocked bootloader, s-off, hboot was at 1.50, and I don't remember what the radio was at. I was running CM11 and was quite happy until two days ago when I stopped receiving texts! No clue why, just stopped. Hangouts, etc etc. Called VM and they had no idea why that was happening either. Tried switching roms, reinstalling backups, etc etc. Clean wipes and all. Then I saw someone said they had to [for some reason] reinstall everything stock and then they had messaging back. So that's what I set out to do.
In Between: Used the RUU that I'm fairly certain came with my phone. Everything was good, it erased everything, and "updated system" and signatures. It was almost finished when BAM, popped up with error 152 Image Update Error; right at the very end. Quite disappointing. Tried it multiple times again with the same result. Not sure what to do.
Current: Only screen I can see (looks like shortened bootloader screen) says "***locked***" at the top, hboot 1.57.0000, radio 1.06.00.126, then says openADSP-v02.6.0.2226.00.0217eMMc-boot
Also tried flashing the unlock_code.bin, and while it took it, it changed nothing. One screen I did see very briefly but cannot replicate said that everything was there except system. Not really sure how to take that or what to do. Any and all help would be helpful. As is it sits on the HTC screen with exclamation points in each corner. When unplugged from usb it gives me that above screen. Removing battering and restarting to bootloader still gives the same screen.
Did you run ruu through windows or pg86img.zip?
Sent from my Evo 3D CDMA using xda app-developers app
hossman said:
Did you run ruu through windows or pg86img.zip?
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
Through Windows; the RUU exe.
SammyMak said:
Through Windows; the RUU exe.
Click to expand...
Click to collapse
You can try this
https://www.dropbox.com/s/d4baafpgchgg4ef/ruu-PG86IMG.zip
Put that on the root of your SD card and rename to pg86img.zip
Make sure its the only one there
Boot to boot loader and accept updates
It may reboot itself to bootloader, if it asks to accept again then accept
When its done reboot your phone
Rename or remove the file when done
Hope that helps
Sent from my Evo 3D CDMA using xda app-developers app
So I have my phone working now. I think it was the RUU.exe that I was using. I downloaded a different one from here http://androidruu.com/Shooter/ after much googling. That finally restored it to original VM stock rom etc. I couldn't use your method of placing the zip onto the root of my SD because despite it being there, it wouldn't go through the normal search for the file. I would remove the battery, put it back in, use the button key combo to try and open to bootloader, and it would go but it would be the page with the status and then it would instantly go back to the black screen with HTC logo.
Thank you for your help though!
Also I'm not sure how useful exactly this will be for anyone else, but if you find yourself ruu'd and needing better files...
The hboot ENG 1.04 I got from here: http://forum.xda-developers.com/showthread.php?t=1817513
ALL other downloads of that hboot did not work AT ALL.
I got the updated radio from here: http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html
The hboots on that site however are stock and most likely won't run the custom roms as well, if at all, as 1.04.
SammyMak said:
I got the updated radio from here: http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html
But the hboots on the site aren't helpful fyi
Click to expand...
Click to collapse
Hey, that's my thread. Just curious what you mean by the hboots aren't helpful?
If there is a problem I'm unaware of, I'd be happy to know what it is so I can get it squared away.
hossman said:
You can try this
https://www.dropbox.com/s/d4baafpgchgg4ef/ruu-PG86IMG.zip
Put that on the root of your SD card and rename to pg86img.zip
Make sure its the only one there
Boot to boot loader and accept updates
It may reboot itself to bootloader, if it asks to accept again then accept
When its done reboot your phone
Rename or remove the file when done
Hope that helps
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
thank you!
Brian706 said:
Hey, that's my thread. Just curious what you mean by the hboots aren't helpful?
If there is a problem I'm unaware of, I'd be happy to know what it is so I can get it squared away.
Click to expand...
Click to collapse
I must apologize! I seem to have mis stated that; they are helpful with regards to them being the stock hboots. However in my particular case those stock hboots weren't for me. I'll edit that here in a sec, but if I was going back to full stock I'd definitely use your stock VM hboot and it would be helpful in that case. Hope that makes sense, no disrespect meant!
SammyMak said:
I must apologize! I seem to have mis stated that; they are helpful with regards to them being the stock hboots. However in my particular case those stock hboots weren't for me. I'll edit that here in a sec, but if I was going back to full stock I'd definitely use your stock VM hboot and it would be helpful in that case. Hope that makes sense, no disrespect meant!
Click to expand...
Click to collapse
Thanks for clarifying that! I see what you meant now.
No worries, I didn't take offense or think you were disrespectful; I just wanted to make sure the downloads were working properly!
And for the record, the stock hboots will work just fine with custom roms. Hboot 1.50 for example will be compatible with the same selection of roms as JuopunutBear 1.50.5050. The difference is that JuopunutBear is patched and will allow for extra fastboot commands and allow them to be run on a locked bootloader.
The eng 1.04 hboot allows for extra fastboot commands that the stock hboot cannot. But you can boot any rom out there on the stock hboots. I've used stock 1.50 forever on this device.
Hi, what is about S-OFF for our device?
Anyone have S-OFF?, As he did? Thanks
For S-Off visit here:
http://forum.xda-developers.com/showthread.php?t=2847983
Sent from my HTC Desire 610 using XDA Premium 4 mobile app
That's incorrect information. There is nothing about s-off in that thread and it doesn't exist yet for our phone. That thread is about system write protection, which is something entirely different.
My bad, copied the wrong post
Sent from my HTC Desire 610 using XDA Premium 4 mobile app
I wish we had s-off, it'd make life easier.
Would have been great to s-off with sunshine but i guess our device is not supported
Someone working on s-off for our device?
Jcase and beaups are working on Sunshine S-off version 3.0, which will most likely support our device. It isn't out yet though, but should be soon. Whatever you do, DO NOT post in the sunshine thread asking anything about it.
$ 25 is a lot for a 610 Thanks for reply
Any advantages now that we can s-off with sunshine?
You can remove that ugly htc red text splash screen for starters
ClearD said:
You can remove that ugly htc red text splash screen for starters
Click to expand...
Click to collapse
Having s-off is news to me. @ClearD, did you purchase this? If so how did you implement it? I went to what I think is the thread but didn't see any notice of how to buy it...
Nevermind. Found it here. And the list confirms our phone. I don't think I'll be buying it because I'm not sure what else I can do that I'm not already doing. Good to know its there though.
http://www.androidpolice.com/2015/03/20/sunshine-3-0-released-with-ability-to-unlock-and-s-off-many-motorola-and-almost-all-htc-handsets/
ClearD said:
You can remove that ugly htc red text splash screen for starters
Click to expand...
Click to collapse
Went and removed red text and added a new splash
With it, you can also change the radio. And bootloader I think. And pretty much anything.
I assume just running the app will remove the red message, but can we just run this with our bootloaders already unlocked and rooted?
And is there anything that changes as far as how we update firmware in the future? I noticed some people were waiting for new exploits, meaning root might've been broken by updates so there must be some more info to it. It'd be great if it had a built in way to take otas even if it means automating the lock/return to stock to do this...
Thats the only thing I'm worried about, I'll s-off, do the whole recovery and mods, Lollipop drops and the only way to update is to relock and RUU. Then be stuck unrooted.
KLit75 said:
I assume just running the app will remove the red message, but can we just run this with our bootloaders already unlocked and rooted?
And is there anything that changes as far as how we update firmware in the future? I noticed some people were waiting for new exploits, meaning root might've been broken by updates so there must be some more info to it. It'd be great if it had a built in way to take otas even if it means automating the lock/return to stock to do this...
Click to expand...
Click to collapse
No, you've gotta flash a new splash screen with the command: fastboot flash splash splash.img
Yes, run it unlocked and rooted. That's optimal.
The current way to root should be fine for the life of the phone. Root tool v4 should be finer, actually. Use it instead. It's easier. No root is broken that I'm aware of.
To get an OTA, you will need to relock and ruu, plain and simple. It's always been that way. I don't know if s-off will affect that or not.
phatmanxxl said:
Thats the only thing I'm worried about, I'll s-off, do the whole recovery and mods, Lollipop drops and the only way to update is to relock and RUU. Then be stuck unrooted.
Click to expand...
Click to collapse
And then when you get the update, you unlock again and re root. Then use titanium backup to restore your apps. It's that easy.
ClearD said:
No, you've gotta flash a new splash screen with the command: fastboot flash splash splash.img
Yes, run it unlocked and rooted. That's optimal.
The current way to root should be fine for the life of the phone. Root tool v4 should be finer, actually. Use it instead. It's easier. No root is broken that I'm aware of.
To get an OTA, you will need to relock and ruu, plain and simple. It's always been that way. I don't know if s-off will affect that or not.
***I actually misspoke there...what I meant was the current version of sunshine wasn't working on the latest firmware (not our phone I don't think) and they were going to release a new version shortly.
That fastboot command you gave me...do I need to put a specific splash img in my fast boot folder or does just typing that in fast boot get it done?
Click to expand...
Click to collapse
You have to have a specific splash screen. So, someone with a stock one can pull theirs hopefully and we can reflash that.