since the current s-off method is not resetting the "lock status" flag,i thot there would be a need for this.
i happened across this thread inthe gsm evo 3d forum: http://forum.xda-developers.com/showthread.php?t=1970252 and found it to work on the HOXL,rezound,inc 4g,sensation 4g,cdma evo 3d,MT4GS,Amaze 4g,one s,droid DNA,and prolly several others.
this does NOT mean you can unlock your bootloader without going thru htcdev. all this means,is that if your bootloader is unlocked after s-off,you can get rid of the relocked watermark and get back to 100% locked prior to s-on for legitimate warranty purposes.
ive always been unlocked. for S&Gs,i dumped mmcblk0p3 and found the described "HTCU" at 0x8404. changed it to 0x00000000 and voila! back to locked
afterward,relfashed my origianl mmcblk0p3,wich brought me back to unlocked with no getting or flashing tokens.
this is NOT a patched or hex edited hboot.again,this is ONLY to get back your original ***locked*** status.
*this is for s-off phones only
2 ways to do it:
1)old school
this assumes you to have drivers,adb/fastboot,a hex editor,a fair understanding about what youre doing,and the ability to follow directions on the linked thread
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>[COLOR="Red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3[/COLOR]
dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 9.519 secs (3481858 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb pull /sdcard2/mmcblk0p3[/COLOR]
2292 KB/s (33143808 bytes in 14.116s)
[COLOR="Blue"]*modify mmcblk0p3 with a hex editor[/COLOR]
c:\mini-adb_vigor>[COLOR="Red"]adb push mmcblk0p3mod /sdcard2/mmcblk0p3mod[/COLOR]
2478 KB/s (33143808 bytes in 13.059s)
c:\mini-adb_vigor>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3[/COLOR]
dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 18.937 secs (1750214 bytes/sec)
[email protected]:/ #[COLOR="red"] exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\mini-adb_vigor>
2)noob friendly
-download the appropriate zips,place on sd card.
-boot to recoverywipe cache/dalvik
-flash in recovery. i recomend to run query first,to make sure its working. tested on my personal HOXL,one s,amaze,jetstream,rezound,inc 4g,sensation,MT4GS,and gsm evo 3d. tested by castlebravo on DNA.
query:query_bootloader.zip
query_bootloader.zip f335f78f9f46469c823da0c671026de5
unlock:unlock_bootloader.zip
unlock_bootloader.zip f335f78f9f46469c823da0c671026de5
lock:lock_bootloader.zip
lock_bootloader.zip f335f78f9f46469c823da0c671026de5
a little bit of explanation. yes,the md5s are all the same. its the same file,just named differently. the script behaves based on the name of the zip. i knew if i only included 1 download and instructed folks to change the name there would be confusion,so this is my attempt to keep it simple. feel free to download one file and just change the name to make the other zips.
it also works to make your phone relocked if for some reason you want it that way(rename relock_bootloader.zip). i didnt include a zip for that because i figued there would be no demand.
before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after:
sure,i could have easily faked the above photos,but i dint.
again,all credit goes to s trace on the above thread,be sure to click the thanks button on his post. all i did was remove the device check per his instruction. DO NOT flash on other devices without checking for the proper location of the lock flag first.
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
enjoy
special thanks
-BC for originally dumping mmcblk0p3 for me to know this was worth exploring for dna
-CastleBravo for testing and suport on the original test thread,as well as the pics you see here
-treadwayj for dumping mmcblk0p3 from his still locked dna.
-brian for unlocking his bootloader,then dumping mmcblock0p3 to make sure it would work for cdma evo3d phones too
-brian and donb for fearless testing of the zip files on evo3d cdma
mine
Cool. Way faster than running ruu and unlocking again. Nice find
Sent from my VENOMized HoxL
very useful haha thx!
Can this be used to remove tampered text or just to change locked status?
liamstears said:
Can this be used to remove tampered text or just to change locked status?
Click to expand...
Click to collapse
Tempered can be eliminated by flashing a new hboot or running an ruu
Sent from my ADR6425LVW using Tapatalk 2
scotty1223 said:
Tempered can be eliminated by flashing a new hboot or running an ruu
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Flashing a new hboot doesn't work, ruu does but wondered if this would be a quicker way of doing it, need to find out what the ruu does to remove it and make a simple way of doing it I suppose
Reflashing same hboot may not work,flash a different one then your current one back. When s on you get tampered from a custom recovery or boot image. When s off those checks are not done,so you won't see it again after you get rid of it.
Running an ruu is easy and a good way to make sure your firmware is matching.
Sent from my ADR6425LVW using Tapatalk 2
scotty1223 said:
Reflashing same hboot may not work,flash a different one then your current one back. When s on you get tampered from a custom recovery or boot image. When s off those checks are not done,so you won't see it again after you get rid of it.
Running an ruu is easy and a good way to make sure your firmware is matching.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
When my phone was stock (1.77), I got tampered simply by rooting the phone with whatever popular adb script that was at the time. So it said Tampered and Locked for a couple months until I finally got the courage to HTCDev unlock and flash TWRP.
Sent from my HTC One X using xda app-developers app
I suppose the phone is still unlocked just showing the locked text? thanks!
mrjayviper said:
I suppose the phone is still unlocked just showing the locked text? thanks!
Click to expand...
Click to collapse
No this is the way to truly set back the locked flag
You're s-off so you don't need an unlocked boot loader
Sent from my One X using Tapatalk 2
mrjayviper said:
I suppose the phone is still unlocked just showing the locked text? thanks!
Click to expand...
Click to collapse
No! As I said in the first post,this not a hex edited hboot,it is reverting you back to stock,out of the box,honest locked. You can unlock or lock at anytime by flashing the appropriate zip.
Edit: dint notice the reply by superchilpil
Sent from my HTC PG09410 using Tapatalk 2
mmcblk0p3 on my phone is around 130MB. is this normal? what exactly is this partition? thanks!
Ok just to verify before I do this. This can be flashed in TWRP right? Flash the query first than the lock? Thanks!
EDIT NVM i just flashed it and it works
Sent from my HTC One X using Tapatalk 2
performed the trick on my phone using "old style" method and worked perfectly.
mrjayviper said:
mmcblk0p3 on my phone is around 130MB. is this normal? what exactly is this partition? thanks!
Click to expand...
Click to collapse
Sounds about right. The codebox is from wen I did my resound,don't compare size to that.
Sent from my HTC PG09410 using Tapatalk 2
superchilpil said:
No this is the way to truly set back the locked flag
You're s-off so you don't need an unlocked boot loader
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Wait don't need unlocked for anything anymore...?
Sent from my HTC One X+ using xda app-developers app
meatwad0222 said:
Wait don't need unlocked for anything anymore...?
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
You can be unlocked if you still wish to fsdtboot flash recveries.
but no... you do not need unlocked with s off. There are other ways to skin the cat as far as installing recoveries,radios,splash image,etc.
Sent from my HTC One XL using Tapatalk 2
hey scotty i could really use your help!
my phone is messed up and i need to send it in under warranty, im currecntly rooted, s off, with twrp and bootloader showing tampered/unlocked.
i need to get my phone back to exactly stock for att warranty.
my question is other then using this tool what else will i have to do? (which ru should i flash? do i need to remove root?, change cid back? etc)
basically
what else do i need to do to get back to completely stock, and what order do i need to do it in?
i would be grateful if you could help me!!!
(also, nice avatar btw. used to love that show).
Not at my PC ATM,but in a nutshell:
1 flash lock zip
2 run most current att ruu
3 change cid
4 turn on secureflag
Use this thread for reference:
http://androidforums.com/showthread.php?t=691213
Just use a one x ruu and change to att cid(CWS__001)
Hope that helps
Sent from my ADR6425LVW using Tapatalk 2
Related
Ok so I have a one s tmobile us.
I have re-locked and reverted it all back to stock hoping the last update was jelly bean.
And after all that and getting the OTA, well to say the least i was pissed to see it wasnt.
So now here we go.
I did all the reading i could find.
I am going to
UNlock, reroot, and then s-off and super cid to the HTC_001.
then hope that if what i read is right i can do a check software update.
And it will pull down the HTC jelley bean right?
Or what do I need to do?
I'm not worried about warranty since i use family mobile which is walmart t-mobile who dont offer me a warranty any since i brought my own phone.
Also question 2 is will I have any radio or wifi issues by doing any of this presuming I read right and all I have to do is the 4 steps i mentioned above.
Thank you for any input on the question.
I will gladly donate to you for some help in getting it done.
I don't use wifi calling so i dont care about that feature and i live here in the us.
Thank you again.
Tim
Unlock the bootloader and then reroot in the exact same way that you did previously. Then you will need to SuperCID. This involves pulling a file called mmcblk0p4, hex editing partition 210's 5th to 12th characters to HTC__001. Do the following in cmd:
adb shell
su
dd if=dev/block/mmcblk0p4 of=/sdcard
exit
adb pull /sdcard/mmcblk0p4
Look in your adb folder and find the file. Hex edit it with the above instructions. If your CID is not where I originally said it was, then just look for T-MOB010 and overwrite it. Then you need to save the file with MOD at the end, to make sure that you can revert if it goes tits up. Make sure the file is the exact same size as the original. Then you need to tell the phone that the modded file is the new one. Push the modded file onto the SD Card through ADB. Then type:
adb push mmcblk0p4MOD/sdcard
adb shell
su
dd if=/sdcard/mmclbk0p4MOD of=/dev/block/mmcblk0p4
exit
adb reboot bootloader
When rebooted, type:
fastboot oem readcid
You should get cmd telling you that it is HTC__001. Successful. If not, just repeat the process (although, if you **** it up, you probably will have a brick)
You do not need to S-Off to get the OTA update. S-Off has no impact on OTA whatsoever. If you really want to S-Off, then Google "FacePalm S-Off HTC One S"
Just reboot your phone, go into settings, about phone, software updates, check now. The 4.1.1 OTA should be there.
Sent from my One S using xda premium
Thank you im doing it as we speak. Only reason I was going to S-off is when i try to do it using the one click it said you need s-off so im trying your way as I type.
dd if=dev/block/mmcblk0p4 of=/sdcard
/sdcard: cannot open for write: Is a directory
1|[email protected]:/ # dd if=dev/block/mmcblk0p4 of=/sdcard
dd if=dev/block/mmcblk0p4 of=/sdcard
/sdcard: cannot open for write: Is a directory
1|[email protected]:/ #
Sorry, you have to put another forward slash at the end of the file location, should have added that, sorry
Sent from my One S using xda premium
Help!!
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tim>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard
dd if=/dev/block/mmcblk0p4 of=/sdcard
/sdcard: cannot open for write: Is a directory
1|[email protected]:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard/
dd if=/dev/block/mmcblk0p4 of=/sdcard/
/sdcard/: cannot open for write: Is a directory
1|[email protected]:/ #
I got it but heres the weird thing my cid reads as HTC_0010? did I need to put 1 under score or 2 underscores for the cid? HTC_001 or is it HTC__001
dd if=/dev/block/mmcblk0p4/ of=/sdcard/
Try that. If that doesn't work, put mmcblk0p4 on the end of sdcard.
Sent from my One S using xda premium
Ok so
HTC__001
it has to be 8 characters its 2 underscores. seperating the HTC and the 001
Ok so heres what i did,
I unlocked again using the onclick newest one.
Then using One click again I changed recovery to the TWRP for S4 of course.
Then finished rooting by install all su binaries.
Changed cid so it now shows HTC__001.
But when i went to the software updates button just now it didnt pull the JB 4.1.1
Grrrrr.
Do i need to change the rom to a different rom?
im on 2.35.531.12 710RD factory tmobile rom.
Do i need to change something else to get my HTC JB 4.1.1 whatever it is?
Try running at HTC__001 RUU. You'll have to relock beforehand though.
Sent from my One S using xda premium
Shoot wouldnt know where to find the us htc__001 ruu do you?
If you Google HTC One S RUUs you should get two or three pages that offer them
Sent from my One S using xda premium
i just don't know which one to use for me . I'm on tmobile network and i am in the us can you possbly point me in the right direction? also you have paypal?
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
So i dont know if this the newest one and if i will have radio or wifi issues with it...
Hey thanks a lot. Your post helped me as well... Thank you.
Sent from my One S using xda premium
It is the newest one (JB is a hint if you look through the name). And yes, there are radio issues. A few people (including me) have got issues with connecting to 3G or HSPDA/HSPA. It will upload data fine but does not download. You have to connect to GPRS, EDGE or HSPDA+/HSPA+.
Sent from my One S using xda premium
Kyle thanks man,
So after all is said and done.
I did do S-off and i dont regret it as I am hboot 1.4
Anyway I changed my cid too 11111111 but then when i was eading and reading and reading and reading i saw that using 11111111 is a guaranteed BRICK!!
So I used the HTC__001 and still had no luck to get the ruu to run. Ill post the ruu log file here but more or less it is *****ing about signature.
If im not mistaken, If i was able to get it to install i can always flash my radio thus fixing any wifi issues.
I did get the trickdroids newest 9.0 to load and then flashed the 9.1 update
Then i flashed the wifi partitions with no issues.
But im curious of what cid you have and where you live that you were able to get that ruu to work for you?
I love s-off though now i can flash any radio, any hboot and so on.
As a side note before the wifi partitions flash wifi would not work kept getting authentication erro.
After connects immidiately, has better range then my stock tmous 2.35.12 whcih was the newest with all updates.
And i get a full 24mbit steady on heavy downloads.
I am curiously wanting to see how the wwe would run but HTC__001 keeps giving bad sgnature error.
Tim2246 said:
But im curious of what cid you have and where you live that you were able to get that ruu to work for you?
Click to expand...
Click to collapse
Maybe this is the answer to your problem
( running latest wwe ruu on your tmobus phone)
http://forum.xda-developers.com/showthread.php?p=39724350
Sent from my VILLE using xda app-developers app
Welcome to moonshine s-off for the HTC One SV . Developed by Fuses, beaups, and Hyuh. Enjoy.
1.) make sure htc sync is uninstalled
2.) make sure adb and fastboot drivers are working
3.) make sure htc sync is uninstalled
4.) if you are having problems with fastboot, try a usb 2.0 port.
5.) make sure htc sync is uninstalled
6.) make sure other programs that interfere with adb and fastboot are uninstalled (PDANet, Kies, etc.)
7.) make sure htc sync is uninstalled
8.) if you use a third party firewall, be sure to grant access to distiller.exe as it checks for updates
9.) MAKE SURE HTC SYNC IS UNINSTALLED
10.) YOU MUST UNZIP THE ARCHIVE BEFORE RUNNING DISTILLER. DO NOT JUST TRY TO RUN IT FROM THE ARCHIVE.
Downloads available at: http://moonshine.io
beaups said:
Welcome to moonshine s-off for the HTC One SV .
Click to expand...
Click to collapse
Thanks for posting this here and your great work all around!
:good:
I guess it's only for ICS, isn't it?
szympro said:
I guess it's only for ICS, isn't it?
Click to expand...
Click to collapse
No, jelly bean (only for boost mobile is ics).
You have to look at the Software Number.
For ics you can use Supercid and Facepalm S-off (except boost mobile).
All devices now supported
Boost (k2_cl) cricket (k2_plc_cl) gsm lte(k2_ul) and gsm only (k2_u)
All one Sv users can install this, it only takes five minutes. Boost mobile is still in testing, but it fully works.
Thanks beaups and fuses. Without them this wouldn't be possible at all.
Sent from my HTC One SV
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The moon has shine on me tonight.
Thank you, very much. Took me quite a few times to get the correct criteria
Like to thanks oldsplatterhead for his stock rom.
Thanks again.
P.s when HTC releases 4.2 obviously a new hboot will come with it, wonder if moonshine s-off can be carried over? Guess it's too early to ask.... but I have faith it will be cracked.
Sent from my HTC One SV using xda premium
It should be permanent
Sent from my HTC One SV
hi all, this is my first post in one SV forum. s-offed my new device (k2_ul) with moonshine.io few days ago, it all went well and quick.
thanks, moonshine! i'll make a donaton in few days.
Install custom roms
Hi, is there a change that something can go wrong using this method? Because I have used it after htc dev-unlock an rooting, and have S-off, but my phone doesn't install a custom rom. I understand that you have to be S-off to be able to install custom roms, right?
Smellie2 said:
Hi, is there a change that something can go wrong using this method? Because I have used it after htc dev-unlock an rooting, and have S-off, but my phone doesn't install a custom rom. I understand that you have to be S-off to be able to install custom roms, right?
Click to expand...
Click to collapse
If you see, that you are S-Off, you should be S-Off, i think.
And you don't need to be S-Off to flash custom Roms, you also can flash with S-On, but you need to flash boot.img with fastboot then.
As i have seen your phone info, you have hboot 2, that means you had already jb installed. So why do you want to use the stock, odexed rom instead?
old.splatterhand said:
If you see, that you are S-Off, you should be S-Off, i think.
And you don't need to be S-Off to flash custom Roms, you also can flash with S-On, but you need to flash boot.img with fastboot then.
As i have seen your phone info, you have hboot 2, that means you had already jb installed. So why do you want to use the stock, odexed rom instead?
Click to expand...
Click to collapse
I want that because my phone acts weird. It doesn't remember whether I want to use my launcher or Sense, if I put a widget on my homescreen the next day there's a grey area where the widget was, etc. So I thought if I can install a stable rom that might be over.
Smellie2 said:
I want that because my phone acts weird. It doesn't remember whether I want to use my launcher or Sense, if I put a widget on my homescreen the next day there's a grey area where the widget was, etc. So I thought if I can install a stable rom that might be over.
Click to expand...
Click to collapse
Have you tried to do a factory reset?
Sounds a little bit like a default (with data partition).
old.splatterhand said:
Have you tried to do a factory reset?
Sounds a little bit like a default (with data partition).
Click to expand...
Click to collapse
No, I haven't done that. I can with a guide root my phone and tablet, but I don't know what happens when I do something like that. Do I have to get rooted then again, or doesn't that change all that stuff like rooting and unlocking?
Smellie2 said:
No, I haven't done that. I can with a guide root my phone and tablet, but I don't know what happens when I do something like that. Do I have to get rooted then again, or doesn't that change all that stuff like rooting and unlocking?
Click to expand...
Click to collapse
It doesn't change unlocking or S-Off. It deletes all user data, all you brought to your phone (not external sd, internal sd i'm not sure), but not things in system.
It sets the software itself to the point where the phone came to you.
Worked perfect!! Nice job.
Stallion34 said:
Thx for the answer...
I followed your suggestion but moonshine gives me an adb failure during the proccess...
I want to S-off my device and then try your custom JB rom...
Click to expand...
Click to collapse
You are already on JB, so there is no real profit for you, cause mine is not modded.
Here a quote from another forum (thanks to wetbiker):
wetbiker7 said:
Make sure you have removed HTC sync from you computer. Also, make sure USB debugging is enabled in developer settings on your phone.
If you have HTC sync, make sure that you reboot the pc and the phone so that everything is reset and the files are completely removed from the pc.
Unzip the Moonshine zip that you downloaded and place it in a folder. With your phone fully booted, plug in USB and connect to pc. Click on the distiller and follow the prompts. Also, make sure you have a good charge on your phone because it'll take it between 5 and 10 minutes.
Also, if you are running a custom kernel, you will need to reinstall it after you have finished with Moonshine.
Edit: disable anti-virus and run the distiller as administrator.
Hope this helps.
Click to expand...
Click to collapse
ERROR: run distiller again and READ
what do i miss? i fastboot flashed splatterhand's stock boot.img for k2u...
edit: SOLVED... you shall not use customized roms
Checking for updates......
Please wait....
Test 1: Rebooting into bootloader
Waiting for fastboot (7/60)
Waiting
Test 2: Booting device
Waiting for ADB (27/60)
Device detected.....................
[************************************************************]
Test 3: Rebooting into bootloader (again)
Waiting for fastboot (7/60)
Waiting for ADB (38/60)
Waiting for device
Moonshining (1)......................................
Moonshining (2).............................
Moonshining (3)..................................
Moonshining (4).........
Waiting for ADB (34/60)
Waiting for device
Powering off device, UNPLUG your device, then press VOL-DOWN & Power to enter hboot
All Done, hope you enjoyed the Moonshine!
Click to expand...
Click to collapse
Ok my device is S-Offed too with this fantastic tool !!
thanks a lot !!!
Hi,
I just wonder why every second step in the instruction is this:
beaups said:
make sure htc sync is uninstalled
Click to expand...
Click to collapse
Hi.
Quick question, I'm trying to help someone back in France with this.
If you're on JB (official OTA update) and do this procedure, will you :
- keep your data as they were just before ?
- keep your rom as it was before (ie : will you be able to install the next OTA updates without any trouble) ?
In one word : does this process just does S-OFF or does it change anything else ?
Thanks a lot !
M
Link To Main Thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.
Reserved
Reserved.
S-Off with no wire trick???? That's just AMAZING! KUDOs MAN!
I know haha... Would try it but weekends and his friends coerced me to do... Took the plunge and never looked back
Sent from my SGH-M919 using Tapatalk 4
Will be great for those who are still s-on.
WeekendsR2Short said:
S-Off with no wire trick???? That's just AMAZING! KUDOs MAN!
Click to expand...
Click to collapse
I'm under the assumption the wire-trick is still needed, but the toolkit has jbear built in, so you would go through the same steps but all files/tools/etc needed to go from stock to s-off is included in this one kit
But correct me if I'm wrong as I haven't tried this yet, just going off of what I know about this phone and how the emmc power cycles
Sent from my Nexus 4 using Tapatalk 2
butch87402 said:
I know haha... Would try it but weekends and his friends coerced me to do... Took the plunge and never looked back
Sent from my SGH-M919 using Tapatalk 4
Click to expand...
Click to collapse
It really was worth the temporarily quickened pulse & respiration rate though wasn't it? Almost like a little roller coaster. LOL
---------- Post added at 07:50 PM ---------- Previous post was at 07:38 PM ----------
demkantor said:
I'm under the assumption the wire-trick is still needed, but the toolkit has jbear built in, so you would go through the same steps but all files/tools/etc needed to go from stock to s-off is included in this one kit
But correct me if I'm wrong as I haven't tried this yet, just going off of what I know about this phone and how the emmc power cycles
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
No corrections necessary, my friend. That makes better sense. Just kinda caught me offguard. Still sounds like one heck of an accomplishment. Can't wait to get a little time to play around with it.
Has the S-Off function been confirmed? Is the wire trick still required? Either way looks like a nice tool!
I have never done the "wire trick". When I originally got my phone, it had the HBOOT 1.45.0007, I did S-OFF with Revolutionary, rooted, unlocked, and all was well. When the newer radio (11.59.3505.20_2) came out that also updated the HBOOT to 1.45.0013, I was told it would revert my phone to S-ON, but I don't think it did. It did update the HBOOT to 1.45.0013. I then had to relock the phone, go to HTCDEV and use the HTC unlock tool, then I re-rooted the phone. So, I've been HBOOT 1.45.0013, with radio 11.59.3504.20_2, and I'm S-OFF, unlocked, rooted, without ever doing a "wire trick".
I think OP should really have a writeup to explain what the different buttons do, and what exactly they are installing.
Fuzi0719 said:
I have never done the "wire trick". When I originally got my phone, it had the HBOOT 1.45.0007, I did S-OFF with Revolutionary, rooted, unlocked, and all was well. When the newer radio (11.59.3505.20_2) came out that also updated the HBOOT to 1.45.0013, I was told it would revert my phone to S-ON, but I don't think it did. It did update the HBOOT to 1.45.0013. I then had to relock the phone, go to HTCDEV and use the HTC unlock tool, then I re-rooted the phone. So, I've been HBOOT 1.45.0013, with radio 11.59.3504.20_2, and I'm S-OFF, unlocked, rooted, without ever doing a "wire trick".
Click to expand...
Click to collapse
Wow, to the best of my knowledge this isn't possible as the s-off part part of the .07 would be due to a patched hboot, that just ignores the security flag checks. Flashing another bootloader would erase the old one which means erase the patch. Radio s-off is much lower level and flashing firmware would not return to s-on no matter the firmware flashed. So correct me if I'm wrong here, but isn't the rev hboot just a patched bootloader? Just doesn't make sense how flashing a new bootloader and unlocking the phone would keep the radio secure flags turned off...
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
Wow, to the best of my knowledge this isn't possible as the s-off part part of the .07 would be due to a patched hboot, that just ignores the security flag checks. Flashing another bootloader would erase the old one which means erase the patch. Radio s-off is much lower level and flashing firmware would not return to s-on no matter the firmware flashed. So correct me if I'm wrong here, but isn't the rev hboot just a patched bootloader? Just doesn't make sense how flashing a new bootloader and unlocking the phone would keep the radio secure flags turned off...
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I don't know the technical details. I just know that my phone originally had 1.45.0007, now has 1.45.0013, and it is S-OFF and unlocked. I never did any "wire trick". When the new radio came out, there was lots of discussion about what to do to maintain S-OFF. I followed those discussions intently. I'm sure if I went back through the archives here on XDA I'd see where it was done, but I don't have the patience for that right now.
Some day I may dig through the old threads so I can wrap my head around this, seems strange to me but thanks for the reply. [/OT]
Is there anyone one out there that's unrooted or interested in bring their phone back to stock and test this all out?
Sent from my Nexus 4 using Tapatalk 2
WindyCityRockr said:
This is a GUI program built using C# in Visual Studio 2013 that takes advantage of ADB and Fastboot commands and puts them into an easy-to-use toolkit. I will be continually developing it and trying out new features, so feel free to request any features you may want. Keep in mind that I am only 16 and have only been coding in C# since June, so I may not be able to implement every requested feature, and if it is possible, I may require assistance from our more skilled members. Any and all criticism is welcome, from the handling of a certain function to the misalignment of a button. I'm a neat freak myself, so no issue is too small! I hope you enjoy the toolkit! :fingers-crossed:
This toolkit uses the WinDroid HTC One X+ Toolkit as a base, so most features are universal besides the recoveries and S-OFF functions. If there is a feature, function or command that is more specific to the myTouch 4G Slide that would improve the toolkit, please let me know! :fingers-crossed:
FEATURES
Attain S-OFF
Drag and Drop Files
Full Bootloader Unlock
Flash Custom Recovery
Flash Custom Kernel
Flash System, Data and Radio Images
Gain Permanent Root
Install Busybox
Sideload ROM's
Push and Pull Files
Install and Uninstall APK's
Full Backup and Restore
Get Logcats
Relock Bootloader
Write SuperCID
Flash Stock RUU
Custom ADB and Fastboot Commands
and many more!
DOWNLOAD
Download: WinDroid HTC myTouch 4G Slide Toolkit.zip - 21.98 MB
CHANGELOG
v1.0
Initial Release!
FUTURE FEATURES
AndroidLib Support (Tried, but won't work. Help?)
Wireless ADB
More robust Fastboot options
Make a recommendation!
CREDITS
WindyCityRockr (Me)
QuantumCipher (Original Inspiration and Guide)
Sandix (Additional C# Coding)
iamareebjamal (ADB Guide)
demkantor (Fastboot Guide)
Click to expand...
Click to collapse
Any mirrors? DevHost is down right now...and I'm dying to see if this is the answer to finally get S-OFF for my Doubleshot
If not then I'll just wait. :/
Dr.Gonz0 said:
Has the S-Off function been confirmed? Is the wire trick still required? Either way looks like a nice tool!
Click to expand...
Click to collapse
I should have looked closer, I am seeing there's a button for each different method. Duuuhhhh Still a great looking tool!
Major update to version 2.0! Check it out and let me know what you think! :highfive:
So does it require a wire trick to achieve S-OFF with this tool or not? I'm already S-off, just wondering if that will be even more easy than the wire trick for those lazy ones who's still s-on?
SKAm69 said:
So does it require a wire trick to achieve S-OFF with this tool or not? I'm already S-off, just wondering if that will be even more easy than the wire trick for those lazy ones who's still s-on?
Click to expand...
Click to collapse
Because the S-OFF methods here are based off of the current methods, most people will still need to do the wire trick.
Sent from my HTC One X+ using XDA Premium 4 mobile app
WindyCityRockr said:
Because the S-OFF methods here are based off of the current methods, most people will still need to do the wire trick.
Sent from my HTC One X+ using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, anyways it's pretty easy to do.
This really is a great tools,
Thank you for your works man, really appreciate it...nice :highfive:
Hi This is my third Post in XDA.
is my tutorial for those like me that had many problem and read enough tutorials all a failure to make the htc one s S4 s-Off and more with this version 3.14.531. 17RD I did with Moonshine guarantee them that if they do such as this will have successes I hope to serve you very helpful!
I take NO responsibility of anything is of my authorship I did under my results, if they do the steps well will have no problems.
To begin!
This is my mobile and this is the requirement
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note before you start:
first I had this version 3.14.531.17RD lower this version 3.14.531.11
As:
Download this official RUU from here
http://www.androidruu.com/getdownload.php?file=Ville/RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
Then I closed the bootloader (bootloader) wrote: fastboot oem lock then right click on my downloaded RUU run as administrator I followed the step and ready.
But first of all: this was my mistake, I had installed htc sync uninstall you make the process of with moonshine and runrunner soff again and again and always the same problem, look
Moonshine
Runrunner
As you can see in the pictures above were more 40 min and nothing just bla bla bla as runrunner left me this error, knowing I had that first make the soff to superCID the problem was the HTC sync no matter if uninstall you the is waste that was my mistake until I decided to format my pc from scratch.
VERY IMPORTANT
If you have not installed the HTC SYNC manager pass to step 2
Step 1: Download and install Your Uninstaller! Pro 7.5.2013.02 DC 13.11.2013 from here
http://www.vdownload.us/programs/18603-your-uninstaller-pro-v75201302-dc-13112013.html
Delete Full HTC SYNC Manager
Step 2: install SDK from here (If you have it installed just upgrade to most recent)
http://developer.android.com/sdk/index.html#download
Step 3: install Java from here (If you already have it installed, go to step 5)
http://java.com/es/
Step 4: install only the driver for HTC (NOT HTC SYNC) from here (be sure to have it)
http://forum.xda-developers.com/showthread.php?t=2217396
Step 5: Once updated SDk enters: sdk/platform-tools: / opened my window command with shift + right click and wrote: fastboot getvar all then the enter key, so they can see the info of my HTC One s tmobile S4
Step 6: Download Moonshine from here
http://moonshine.io/
(the file name is moonshine_ville_3.14.531.11.zip-20.0mb) is for the main of your mobile version 3.14.531.11 once downloaded extracted it copied the 5 files as shown in the picture into the folder: sdk/platform-tools
Step 7:in the mobile remove the selection of Fast boot, enable USB debugging, and remove the safety (Nothing pattern, PIN).
Step 8: connect the cable in the mobile USB make sure this synchronized, write adb devices if shown the serious beginning with HT... Already this synchronized
Step 9: double click on the executable distiller.exe let you see in the photo, this process has a duration close 5 minutes and restarts from 4 to 5 times, wait until you finish see photo
I did this with the stock recovery, nothing TWRP or CWM see photo
Once finished restart several times this is the result!
Step 10: super cid already applied from here
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
This is all! I have my sense 5 installed Rom from here
http://forum.xda-developers.com/showthread.php?t=2445392
and here is the sense 5 on my tmobile S4 see
Another ROM with SENSE 5 download from here
http://forum.xda-developers.com/showthread.php?t=2524717
Comment and leave points I hope that this will serve you! that will save many time effort and sacrifice, next up.
Sorry for my bad English
So you have just reposted the instructions that can be found in both moonshine and rumrunner op's?
Sent from my HTC One S using Xparent Red Tapatalk 2
rc420head said:
So you have just reposted the instructions that can be found in both moonshine and rumrunner op's?
Sent from my HTC One S using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Remember, I try with moonshine and rumrunner and failure see the first pictures of the post as well as all had many problems to be Soff and more with this version 3.14.531. 17RD I am the author of this post and so it was that work for me and I want to share with everyone having problems with soff, if were steps correctly will have success like me
Hey man. I had the same problem as you where rumrunner wouldn't work and I had the same version as you. But I did as you did step by step and I finally got S-Off and then I also did SuperCID.
My question how in the end did you get rid of the moonshine S-Off at the top and got the "TAMPERED.....LOCKED" back??
theonlysamiam said:
Hey man. I had the same problem as you where rumrunner wouldn't work and I had the same version as you. But I did as you did step by step and I finally got S-Off and then I also did SuperCID.
My question how in the end did you get rid of the moonshine S-Off at the top and got the "TAMPERED.....LOCKED" back??
Click to expand...
Click to collapse
It relocked your bootloader, just unlock it using htcdev.com, only way to get rid of the moonshine writing is to flash a different hboot.
Sent from my HTC One S using Xparent Red Tapatalk 2
rc420head said:
It relocked your bootloader, just unlock it using htcdev.com, only way to get rid of the moonshine writing is to flash a different hboot.
Sent from my HTC One S using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
That's what I was thinking so I tried to unlock the bootloader with the unlock bin file that I got from htcdev.com when I first originally unlocked and rooted my phone but it failed. Do I need to do the htcdev.com process again and attain another unlock bin file?
And as for the hboot, is there a major difference between 2.15 and 2.16??
theonlysamiam said:
That's what I was thinking so I tried to unlock the bootloader with the unlock bin file that I got from htcdev.com when I first originally unlocked and rooted my phone but it failed. Do I need to do the htcdev.com process again and attain another unlock bin file?
And as for the hboot, is there a major difference between 2.15 and 2.16??
Click to expand...
Click to collapse
Yes get New bin file.
2.16 pros
1.sd is now 12gb
2.can run newest sense software
Cons
1.cant mount SD while in recovery
2.cant run roms made for 2.15
Basically if your a sense guy upgrade to 2.16 if you find yourself using cm mostly best to stay on 2.15. There are a few cm builds that are for 2.16 but most use 2.15.
But we're way off topic so pm if you have more questions about 2.16 or upgrading.
To OP sorry for the thread highjack now back on topic
Sent from my HTC One S using Xparent Red Tapatalk 2
theonlysamiam said:
Hey man. I had the same problem as you where rumrunner wouldn't work and I had the same version as you. But I did as you did step by step and I finally got S-Off and then I also did SuperCID.
My question how in the end did you get rid of the moonshine S-Off at the top and got the "TAMPERED.....LOCKED" back??
Click to expand...
Click to collapse
It is very easy, once again to unlock the bootloader with HTCDEV follow the step and ready...
I Relocked my HTC ONE M8 watching this video titled "How to Unroot the HTC One M8 Complete Guide". At the time didn't know "M8 All In One Kit" was block by Verizon but everything seem to go so smooth just like video. When I went back to bootloader to see if "S-OFF" change back to "S-ON" and it did but RADIO and OpenDSP showed "INVALID_VER_INFO", while OS is blank.
I would show a picture of my bootloader but at the time can't because being new user can't post links.
My version is 1.55.605.2
My Recovery: Stock
Here's Bootloader Picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anyone give me feedback about my situation?
Heroxgxdeal said:
Can anyone give me feedback about my situation?
Click to expand...
Click to collapse
does it boot?
Sent from my SM-T320 using Tapatalk
Heroxgxdeal said:
I Relocked my HTC ONE M8 watching this video titled "How to Unroot the HTC One M8 Complete Guide". At the time didn't know "M8 All In One Kit" was block by Verizon but everything seem to go so smooth just like video. When I went back to bootloader to see if "S-OFF" change back to "S-ON" and it did but RADIO and OpenDSP showed "INVALID_VER_INFO", while OS is blank.
I would show a picture of my bootloader but at the time can't because being new user can't post links.
My version is 1.55.605.2
My Recovery: Stock
Click to expand...
Click to collapse
Im guessing you may need to RUU... but somewhere I read you need to be SOFF for that...
dottat said:
does it boot?
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
yes it does
Heroxgxdeal said:
yes it does
Click to expand...
Click to collapse
Ok so from here what are you looking to do ? Sell it? Return it ? Why did you back to a on?
sandm4n said:
Im guessing you may need to RUU... but somewhere I read you need to be SOFF for that...
Click to expand...
Click to collapse
Yeah you need to be S-OFF for RUU, I was wondering if Firewater doesn't work for me anymore because of Radio, etc is missing from bootloader.
dottat said:
Ok so from here what are you looking to do ? Sell it? Return it ? Why did you back to a on?
Click to expand...
Click to collapse
I was going wait for 4.4.3 OTA to come on M8 (Verizon) then sell it to friend, knowing nothing was wrong with the phone.
Heroxgxdeal said:
I was going wait for 4.4.3 OTA to come on M8 (Verizon) then sell it to friend, knowing nothing was wrong with the phone.
Click to expand...
Click to collapse
Try to s off again. There's nothing wrong with you selling it to a friend with it s offed
..Being S-On.. you are stuck in the sense that we do not have a signed RUU for you to flash.
Your best bet is to try to re S-OFF your device, if you are able to do this, you can simply run the RUU, fix your device, and then go back to S-ON.. if you want, and then keep, sell it, what ever.
If you can't get it to S-OFF...
you may be stuck
andybones said:
..Being S-On.. you are stuck in the sense that we do not have a signed RUU for you to flash.
Your best bet is to try to re S-OFF your device, if you are able to do this, you can simply run the RUU, fix your device, and then go back to S-ON.. if you want, and then keep, sell it, what ever.
If you can't get it to S-OFF...
you may be stuck
Click to expand...
Click to collapse
Sorry for the late response, i'll try to re S-OFF my device and tell you if it worked. Wish me luck
andybones said:
..Being S-On.. you are stuck in the sense that we do not have a signed RUU for you to flash.
Your best bet is to try to re S-OFF your device, if you are able to do this, you can simply run the RUU, fix your device, and then go back to S-ON.. if you want, and then keep, sell it, what ever.
If you can't get it to S-OFF...
you may be stuck
Click to expand...
Click to collapse
After doing the Adb method for couple times to get S-off, I had no success. I did get to paste the last command " /data/local/tmp/firewater" few times but it never progress to "Agree to Terms and Conditions you are prompted with" part.
Do you have any tips you can tell me to use adb method/weaksauce method.
Heroxgxdeal said:
After doing the Adb method for couple times to get S-off, I had no success. I did get to paste the last command " /data/local/tmp/firewater" few times but it never progress to "Agree to Terms and Conditions you are prompted with" part.
Do you have any tips you can tell me to use adb method/weaksauce method.
Click to expand...
Click to collapse
Honestly, you have to post way more specifics for us to be able to chime in....
Best would be to take screen shots of your cmd window so we can see the commands you put in and the return.
In lieu of that, post your specific commands, which option in the firewater instructions you followed etc.
The more specific , the better....
I went to S-ON and had the same issue.
What I did was keep the device with S-ON and flashed the firmware.zip from the OTA. Since its signed you can flash it while being S-ON.
This didn't fix it so I decided to send it back to VZW with the invalid version in hboot.
The last thing I wanted to do though was to get the developer options out of settings. So I turned off developer options and then cleared the data on Settings.
So now that developer options was hidden again I just let the device charge to 100%.
I figured I'd check the versions in hboot one last time and to my surprise it was correct.
I'm not sure what fixed it but I went from S-OFF to S-ON with invalid versions displaying to S-ON with valid versions displaying.
berndblb said:
Honestly, you have to post way more specifics for us to be able to chime in....
Best would be to take screen shots of your cmd window so we can see the commands you put in and the return.
In lieu of that, post your specific commands, which option in the firewater instructions you followed etc.
The more specific , the better....
Click to expand...
Click to collapse
Sorry for the late response, this time I got all the way to first bottle open that you can see below. Whats next that I can do?
C:\Android>adb reboot
C:\Android>adb wait-for-device push firewater /data/local/tmp
2625 KB/s (4522136 bytes in 1.682s)
C:\Android>adb shell
[email protected]_m8wl:/ $
C:\Android>adb shell
[email protected]_m8wl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8wl:/ $ su
su
[email protected]_m8wl:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 8.0.6.26 ===========================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
yes
yes
Type 'Yes' or 'No'
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********
[email protected]_m8wl:/ #
Heroxgxdeal said:
Sorry for the late response, this time I got all the way to first bottle open that you can see below. Whats next that I can do?
C:\Android>adb reboot
C:\Android>adb wait-for-device push firewater /data/local/tmp
2625 KB/s (4522136 bytes in 1.682s)
C:\Android>adb shell
[email protected]_m8wl:/ $
C:\Android>adb shell
[email protected]_m8wl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8wl:/ $ su
su
[email protected]_m8wl:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 8.0.6.26 ===========================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
yes
yes
Type 'Yes' or 'No'
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********
[email protected]_m8wl:/ #
Click to expand...
Click to collapse
You could try the Sunshine method to S-Off your device or you could read through my previous post in this thread.
I had this same issue and somehow was able to get the version info to display correctly.
scuccia said:
You could try the Sunshine method to S-Off your device or you could read through my previous post in this thread.
I had this same issue and somehow was able to get the version info to display correctly.
Click to expand...
Click to collapse
I'm going to try the Sunshine method after I get the $25 payment to pay for the license. I can't flash anymore because i'm on stock recovery, I wanted to know what you meant by
scuccia said:
then cleared the data on Settings.
Click to expand...
Click to collapse
. Do you mean factory reset?
Heroxgxdeal said:
Do you mean factory reset?
Click to expand...
Click to collapse
No, I went into App Manager, opened up the settings application and clicked on clear data. I then let the phone charge to 100%.
I also flashed the firmware.zip RUU from the OTA. You can do this while you're locked and S-On because its signed by HTC.
I have no idea what fixed it but I would try flashing the firmware.zip and then boot up into Android and let it sit for a while.
If that doesn't work then you could try clearing data on Settings and let it sit for a while again. I don't think that will do anything though, that's just what I did.
I'm finally S-OFF again using the Sunshine method,thank you very much to everyone that help me.