hey guys, i was thinking about the phone and was thinking that there might be a way to actually remove or alter the ***TAMPERED *** warning either via fastboot or using abd shell / dd command and hex edit. i know that we can already modify the CID and other things, but how about the tampered warning? it would be very interesting to try, and to see if anyone actually knows how or of a way to do it. I know already that you would probably need to be s-off, but i can't say for sure.
(i hope i am posting in the right forum. if not, feel free to move me appropriately. thanks!)
I am a bit hesitant to do a full bootloader memory dump, which i know is possible, but if there isn't any risks, one could should me how to actually do that correctly. I am, as of yet, a developer in training. i downloaded the latest Jellybean source from SDK manager and i am going to try to build something for either this phone or for my thunderbolt, which now has the ICS kernel i need to build into jellybean.
cyberkeeper1 said:
hey guys, i was thinking about the phone and was thinking that there might be a way to actually remove or alter the ***TAMPERED *** warning either via fastboot or using abd shell / dd command and hex edit. i know that we can already modify the CID and other things, but how about the tampered warning? it would be very interesting to try, and to see if anyone actually knows how or of a way to do it. I know already that you would probably need to be s-off, but i can't say for sure.
(i hope i am posting in the right forum. if not, feel free to move me appropriately. thanks!)
Click to expand...
Click to collapse
man this is development not general/q&a please move your thread
There is a few threads on this already
Sent
prairiedogn said:
There is a few threads on this already
Sent
Click to expand...
Click to collapse
i looked in search and it revealed nothing so i posted a new thread.
http://forum.xda-developers.com/showthread.php?t=2062890
cyberkeeper1 said:
i looked in search and it revealed nothing so i posted a new thread.
Click to expand...
Click to collapse
Just dig around you'll find alot
sent from recovery
somerandomname1 said:
http://forum.xda-developers.com/showthread.php?t=2062890
Click to expand...
Click to collapse
i was talking about while being s-on. its possible to edit other things in adb shell while s-on using dd and hexalter.exe, so why not the tampered warning? this is different than the s-off thread, so it has merit. i was just wondering if it could be done or if anyone has any ideas how it would be accomplished. someone well versed in "dd" programming.
somerandomname1 said:
http://forum.xda-developers.com/showthread.php?t=2062890
Click to expand...
Click to collapse
The linked utility does indeed require s-off, but it will allow you to change your hboot screen to look 100% stock.
cyberkeeper1 said:
i was talking about while being s-on. its possible to edit other things in adb shell while s-on using dd and hexalter.exe, so why not the tampered warning? this is different than the s-off thread, so it has merit. i was just wondering if it could be done or if anyone has any ideas how it would be accomplished. someone well versed in "dd" programming.
Click to expand...
Click to collapse
If you're s-on, then you might want to try this approach, but be very very careful... Changing the "HTCU" at 0x8404 back to 0x00000000 should change you back to "*** LOCKED ***", which may also remove the "*TAMPERED*" flag. I have not had the need to test this, so let us know if it works for you.
Related
Info:
Make it easy to find the list of radios available for the MyTouch Slide for the S-OFF direct flash method. For an S-ON update.zip method, check the reference section and comments below.
Prerequisite:
Need to have S-OFF
Need to have adb and fastboot setup
Windows: Need to have android drivers installed
Process:
Code:
adb reboot bootloader
fastboot flash radio radio-x.xx.xx.xx.img
fastboot reboot
Download:
Espresso Radio 7.03.35.14
Espresso Radio 7.07.35.02S
Espresso Radio 7.08.35.04S
Espresso Radio 7.09.35.10
Espresso Radio 7.15.35.16
Alternate:
For those without S-OFF, you can still update your radio using the original update.zip method provided by ChiefzReloaded.
Espresso Radio 7.08.35.04S - [UTIL]Newest Slide Radio Update
Espresso Radio 7.09.35.10 - UPDATED... New OTA Radio Update!!
Espresso Radio 7.15.35.16 - [RADIO] Newest Radio from Froyo OTA 1/21/2011
Reference:
[RADIO] Newest Radio from Froyo OTA 1/21/2011
UPDATED... New OTA Radio Update!!
[UTIL]Newest Slide Radio Update
FULL HTC Espresso Dump with Radio, Recovery and Boot!
I couldn't find where I got the other radio from.
Let me know if you have another radio to add, or know of a good 'howto setup fastboot' thread.
Thanks for this thread!!
I don't think you need S-OFF to update the radio.
Sizzlechest said:
I don't think you need S-OFF to update the radio.
Click to expand...
Click to collapse
None of these downloads are in signed packages. They are simply the raw data (as a .img file) compressed with 7zip.
I'm fairly certain the standard S-ON bootloader would not permit a flash of any image through fastboot, especially unsigned images.
If you have S-ON, I think ChiefzReloaded's method might work for you. You can find his thread in a link in the OP.
You mean the standard S-ON bootloader won't allow it right? I've had no problems flashing any raw data (in .img format) with the S-OFF HBOOT.
reukiodo said:
None of these downloads are in signed packages. They are simply the raw data (as a .img file) compressed with 7zip.
I'm fairly certain the standard S-ON bootloader would not permit a flash of any image through fastboot, especially unsigned images.
If you have S-ON, I think ChiefzReloaded's method might work for you. You can find his thread in a link in the OP.
Click to expand...
Click to collapse
Yes, I downloaded the file from this thread: http://forum.xda-developers.com/showthread.php?t=745874 and installed using Rom Manager before I installed S-OFF.
Sizzlechest said:
Yes, I downloaded the file from this thread: http://forum.xda-developers.com/showthread.php?t=745874 and installed using Rom Manager before I installed S-OFF.
Click to expand...
Click to collapse
That's through ROM manager, flashing as an update.zip
This thread has them as raw .img files, the only way to flash them is through an S-Off bootloader, using fastboot.
Thanks for this!
migueltherocker said:
That's through ROM manager, flashing as an update.zip
This thread has them as raw .img files, the only way to flash them is through an S-Off bootloader, using fastboot.
Click to expand...
Click to collapse
Not everyone needs or wants to do S-OFF. However, just about everyone should update their slide's radio. The OP implies the only way to accomplish that is perform S-OFF, which can brick your phone. It should be clearer.
Sizzlechest said:
Not everyone needs or wants to do S-OFF. However, just about everyone should update their slide's radio. The OP implies the only way to accomplish that is perform S-OFF, which can brick your phone. It should be clearer.
Click to expand...
Click to collapse
^^^
Cannot disagree more with this guy.
HebrewToYou said:
^^^
Cannot disagree more with this guy.
Click to expand...
Click to collapse
In what way? That everyone needs S-OFF or that everyone should update their radio?
Sizzlechest said:
In what way? That everyone needs S-OFF or that everyone should update their radio?
Click to expand...
Click to collapse
Everyone who has the know-how to attempt S-OFF should do it.
And the OP doesn't need to be any more clear.
HebrewToYou said:
Everyone who has the know-how to attempt S-OFF should do it.
Click to expand...
Click to collapse
Why? If you want to change your boot animation? If you don't want to have to boot into recovery to change system files? How many times does the average user need to do this?
HebrewToYou said:
And the OP doesn't need to be any more clear.
Click to expand...
Click to collapse
It sure does.
Sizzlechest said:
Not everyone needs or wants to do S-OFF. However, just about everyone should update their slide's radio. The OP implies the only way to accomplish that is perform S-OFF, which can brick your phone. It should be clearer.
Click to expand...
Click to collapse
Clarified in the OP.
Sizzlechest said:
Why? If you want to change your boot animation? If you don't want to have to boot into recovery to change system files? How many times does the average user need to do this?
Click to expand...
Click to collapse
SetCPU set on boot WILL NOT WORK without S-OFF. Flashing a permanent custom recovery WILL NOT WORK without S-OFF. Customizing the size of your MTD partitions WILL NOT WORK without S-OFF. All three of those should be very important to people who own an Espresso.
Sizzlechest said:
It sure does.
Click to expand...
Click to collapse
<snark>
Oh, I must have totally overlooked how your fifteen contributions [your posts to date] to the XDA forums gave you amazing insight into the clarity needed for a reference post such as this.
</snark>
This isn't a how-to post; if you don't understand what this is, this isn't meant for you.
Is it that easy to brick while attempting to S-Off?
I mean if you follow directions and make sure you have a Nandroid backup, you can't really screw it up. Unless the power goes out or something.
Isn't that why we waited so long? So we could get a method that didn't screw a crap load of people over?
Sizzlechest said:
Why? If you want to change your boot animation? If you don't want to have to boot into recovery to change system files? How many times does the average user need to do this?
Click to expand...
Click to collapse
The boot animation is stored in /system/media and does not requite S-OFF. Changing your boot splash, however, does indeed require S-OFF. An example of a user of wanting rw /system partition while running is AdFree, where the app writes to /system/hosts. The other option is to use AdFree with a symlink to /data/data/hosts and manually create a symlink themselves in recovery, but specific instructions are not given so a user would be required to know about symlinks and how to create them from the command line in the recovery shell.
According to some other developers, the direct flash (via S-OFF) method is actually less risky of a brick than an update.zip flash of the radio.
What radio is best? What really is the difference between each? I have what came with cm7. All i know is im tired of toggling airplane mode cuz my radio gets stuck.
Cyanogenmod 7 nightly oc @ 825
HebrewToYou said:
SetCPU set on boot WILL NOT WORK without S-OFF. Flashing a permanent custom recovery WILL NOT WORK without S-OFF. Customizing the size of your MTD partitions WILL NOT WORK without S-OFF. All three of those should be very important to people who own an Espresso.
Click to expand...
Click to collapse
No, those things are important to YOU. Not everyone is running a custom rom, or wants to overclock their phone. However, updating the phone's radio is something everyone would want to do.
The problem is that you assume everyone is as big as a nerd as you. We're not.
HebrewToYou said:
<snark>
Oh, I must have totally overlooked how your fifteen contributions [your posts to date] to the XDA forums gave you amazing insight into the clarity needed for a reference post such as this.
</snark>
This isn't a how-to post; if you don't understand what this is, this isn't meant for you.
Click to expand...
Click to collapse
<snark>Your people skills will get you far. You must be in marketing because you're so in tune with what people really want.</snark>
Thankfully, the OP can accept suggestions without assuming it's an attack on his manhood.
Let's not start a flame war guys...I had to help diffuse the last couple that were on this board before the mods came in and deleted all the bs posts and I don't think anyone here wants that to happen again.
@OP I added a link to this thread to my n00b FAQ, hope you don't mind. If you'd like I could remove it.
If you have unlocked and rooted your DNA you may have noticed things are a bit different that you are probably used to.
In the past, unlocking gave root the ability to write to /system. That is no longer the case.
What does this mean? This means that things like pushing or removing files in adb while booted to android are no longer possible. You have to flash recovery, boot to it, and either mount system and do it there, or flash something.
This includes things like updating the su binary in SuperUser. You must now go get the file and do it yourself.
I have gotten several PMs about this, so I thought I would put it out here.
Please pass it around since most of you will be getting unlock soon.
D
.
dsb9938 said:
If you have unlocked and rooted your DNA you may have noticed things are a bit different that you are probably used to.
In the past, unlocking gave root the ability to write to /system. That is no longer the case.
What does this mean? This means that things like pushing or removing files in adb while booted to android are no longer possible. You have to flash recovery, boot to it, and either mount system and do it there, or flash something.
This includes things like updating the su binary in SuperUser. You must now go get the file and do it yourself.
I have gotten several PMs about this, so I thought I would put it out here.
Please pass it around since most of you will be getting unlock soon.
D
.
Click to expand...
Click to collapse
Thank for the heads-up.
Any idea why its like this? Just curious. Thanks.
dsb9938 said:
What does this mean?...
Please pass it around since most of you will be getting unlock soon.
Click to expand...
Click to collapse
When unlock is released, please write a example guide for steps to follow for normal root things (delete apps, give SU access to an app, do a backup, etc).
I like the sounds of that soon!!!
suzook said:
Any idea why its like this? Just curious. Thanks.
Click to expand...
Click to collapse
Because the phone is still S-On, which prevents any writing to system while booted.
I thought we are getting S-off soon from teamAndIRC?
the_passenger said:
I thought we are getting S-off soon from teamAndIRC?
Click to expand...
Click to collapse
Not S-off
Unlock is the exploit that will be released.
This will allow for temp root
Sent from DNA using Tapatalk2
MePascal said:
Not S-off
Unlock is the exploit that will be released.
This will allow for temp root
Sent from DNA using Tapatalk2
Click to expand...
Click to collapse
It's out: http://forum.xda-developers.com/showthread.php?p=34583031
D
.
I just got a new rezound just now and i would like to know how i can root and get s off and unlock the bootloader and all that jazz, preferably in some sort of order. it came with android 4.0.4
Have you tried searching yet? There are alot of sticky posts on it
mclass55 said:
Have you tried searching yet? There are alot of sticky posts on it
Click to expand...
Click to collapse
search hasnt been working lately, i myself keep getting the gif of the cat reading.
I would like to second the OP question, i think its time for me to root also....
Check the sticky roll-up thread in development to get the basics (the basics never change), then if if you have specific questions, it will be a lot easier to give direction.
rickyjohn said:
search hasnt been working lately, i myself keep getting the gif of the cat reading.
I would like to second the OP question, i think its time for me to root also....
Click to expand...
Click to collapse
Here you go: Link
mclass55 said:
Here you go: Link
Click to expand...
Click to collapse
that was cool i was freaking out for a second :laugh:
mclass55 said:
Have you tried searching yet? There are alot of sticky posts on it
Click to expand...
Click to collapse
they are very confusing and i dont even know where to start.
shrike1978 said:
Check the sticky roll-up thread in development to get the basics (the basics never change), then if if you have specific questions, it will be a lot easier to give direction.
Click to expand...
Click to collapse
I downloaded the htc super tool thing. do i press those things in order 1-10?
i need to unlock the bootloader before i attempt s off and attempt perm root right? why are they out of order?
gabezermeno said:
i need to unlock the bootloader before i attempt s off and attempt perm root right? why are they out of order?
Click to expand...
Click to collapse
Maybe I missed something, but why do you think that's out of order?
You can't flash an alternate recovery until you have unlocked the bootloader. You can't root without a custom recovery. You can't get S-OFF unless you're already rooted with a custom recovery and an unlocked bootloader. So, it would seem to me the proper order is:
1. Unlock the bootloader (via htc dev site).
2. Flash a custom recovery such as Amon Ra, TWRP or Clockworkmod Touch (I prefer the first; Flyhalf has done a decent job porting the other two).
3. Get S-OFF via the Juopunut technique.
Recognize that each of these steps may erase your data and/or your sdcard, so read instructions CAREFULLY. They are meticulously spelled out so that you don't make a mistake. For instance, you need a different sdcard to do the S-OFF trick. If you use the sdcard you usually use, you will erase it. IMost mistakes that arise are from users who don't pay attention somewhere along the way.
Links to all of these things are very easy to find on in the Development Forum, the first sticky roll-up thread. And, yes, you ought to use search....liberally.
hgoldner said:
Maybe I missed something, but why do you think that's out of order?
You can't flash an alternate recovery until you have unlocked the bootloader. You can't root without a custom recovery. You can't get S-OFF unless you're already rooted with a custom recovery and an unlocked bootloader. So, it would seem to me the proper order is:
1. Unlock the bootloader (via htc dev site).
2. Flash a custom recovery such as Amon Ra, TWRP or Clockworkmod Touch (I prefer the first; Flyhalf has done a decent job porting the other two).
3. Get S-OFF via the Juopunut technique.
Recognize that each of these steps may erase your data and/or your sdcard, so read instructions CAREFULLY. They are meticulously spelled out so that you don't make a mistake. For instance, you need a different sdcard to do the S-OFF trick. If you use the sdcard you usually use, you will erase it. IMost mistakes that arise are from users who don't pay attention somewhere along the way.
Links to all of these things are very easy to find on in the Development Forum, the first sticky roll-up thread. And, yes, you ought to use search....liberally.
Click to expand...
Click to collapse
on the thing it says to do them out of order.
gabezermeno said:
on the thing it says to do them out of order.
Click to expand...
Click to collapse
gabezemeno, you might just want to go buy you a i-phone
gabezermeno said:
on the thing it says to do them out of order.
Click to expand...
Click to collapse
Regarding the 2nd step. I suggest flashing Cleanrom before attempting to s-off. Will get you acquainted with the s-on techniques used even before hand. Trust me both s-on & s-off have their advantages over one another. Then you can use CleanRom to obtain s-off as one of the prerequisites is a rooted rom with an unsecured boot(which it has).
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
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.