Database Info

permroot for S-off MyTouch 4G Slide

How i got perm root on my MT4GS (does not give S-off just permroot of an S-off device)
YOU NEED TO HAVE A S-OFF device!
1)Start off with a fresh install of the TMO 1.28 ROM
2)Used temp root from MT4GSROOT.zip Thanks TeamWin for the temproot method Here is thread for orgnial files)
open MT4GSROOT\ADB (on pc)
Make sure that you have USB debugging turned on (on phone) and drivers installed to PC
Run Fre3voMT4gS.bat (from MT4GSROOT\ADB)
3)check in ternimal ((on phone) need to install from market)) and see if you have root (I got permission denied)
4)ran superonclick with Gingerbreak exploit (thanks CLShortFuse for making this tool) (on pc) - S1C thread
open MT4GSROOT and click on Superoneclick.exe
change exploit to Gingerbreak
hit root
Installed busybox when asked by S1C
Run Su test and looked on phone and Superuser asked for permission
5)Tried opening a app that uses root (root explorer) and SU FC on me
6)go to market and make sure you had latest version Installed (i had an update I needed)
7)Update binary when opening SU for the first time
Allow the SU app SU priviliages (funny I know)
8)Open a root app (root explorer again) and SU asked for permission
Test for permroot
turned off fastboot
deleted a system/app file (in this case htcfmwidget and htcfmwidge.obex) -using the r/w option in root explorer
Rebooted phone and reopened root explorer and looked for removed files and they were not there
None of the tools that I included were made by me they were made by the people I thanked. I just wrote the script for the tools to work. go to their threads and thank them.
Disclaimer I am not responsible for breaking your phone, melting it, or anything that may happen when doing this. Remember this is your choice
I have been able to use Root explorer, Titanium backup, terminal emulator and was able to remove APKs from the system folder that I do not want.

This is awesome!
So how did you get s-off? Did it ship that way?

raycaster3 said:
So how did you get s-off? Did it ship that way?
Click to expand...
Click to collapse
Mine was shipped s-off ordered online
Sent from my HTC Sensation Z710e using XDA App

crackeyes said:
Mine was shipped s-off ordered online
Click to expand...
Click to collapse
That's awesome that we've acheived perm root already.
If you don't mind me asking, did you do the preorder process from t-mobile?
I am extremely interested in this, but I hate preorders

crackeyes said:
Mine was shipped s-off ordered online
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Killer. Mine is being shipped the 27th. I can't wait to give this a try. Now all we need is miui for this phone and we're all set! Haha
Sent from my demonSPEED Glacier

raycaster3 said:
Killer. Mine is being shipped the 27th. I can't wait to gibe this a try. Now all we need is miui for this phone and we're all set! Haha
Sent from my demonSPEED Glacier
Click to expand...
Click to collapse
Oh no, I just realized he is probably talking about the DoubleShot.
For some reason I have a feeling that the delay for T-Mobile USA customers is due to HTC installing a S-On bootloader

poormanq45 said:
That's awesome that we've acheived perm root already.
If you don't mind me asking, did you do the preorder process from t-mobile?
I am extremely interested in this, but I hate preorders
Click to expand...
Click to collapse
I didn't preorder I acquired at a meet and greet where they gave me place to get it
Sent from my HTC Sensation Z710e using XDA App

Please don't ask for ETA's people would start coming in MT4GS section soon It come's with stock 2.3.4 so all we need is a custom ROM & were fine . I will be creating a TouchWiz 4.0 ROM w/Sense w/ MIUI icon's .
raycaster3 said:
Killer. Mine is being shipped the 27th. I can't wait to give this a try. Now all we need is miui for this phone and we're all set! Haha
Sent from my demonSPEED Glacier
Click to expand...
Click to collapse

No S-OFF on retail devices folks.
P

I cant get to get my computer to find it, is asking for the driver.... I try but I need the drivers it only appears as android phone on the management.
Update the driver comes on the original SD card, i swapped it which I didn't realized till now
Update 2: After finding the driver I still cant get root access.... anyone done it already?

waiting89 said:
I cant get to get my computer to find it, is asking for the driver.... I try but I need the drivers it only appears as android phone on the management.
Click to expand...
Click to collapse
Install htc sync but make sure it is not running
Sent from my HTC Sensation Z710e using XDA App

I got it working and follow the step of rooting, but I still dont get any root access...

is it possible to extract the s-off boot-loader from a device with s-off already? My understanding of these procedures is rudimentary at best, but if my understanding is correct, the boot-loader is a specific partition on the device, if someone with an s-off device could copy that image to their computer or just a folder on their sd-card, it should be possible then to share that with others who could then write that image to their boot-loader partion using fastboot. or can you not use fastboot until s-off is achieved? i hate that i always forget these things once i have my device running the way i want it to.

shizenyasuya said:
is it possible to extract the s-off boot-loader from a device with s-off already? My understanding of these procedures is rudimentary at best, but if my understanding is correct, the boot-loader is a specific partition on the device, if someone with an s-off device could copy that image to their computer or just a folder on their sd-card, it should be possible then to share that with others who could then write that image to their boot-loader partion using fastboot. or can you not use fastboot until s-off is achieved? i hate that i always forget these things once i have my device running the way i want it to.
Click to expand...
Click to collapse
The Stupid Noob wants to know...
What the heck is "S-off"??

shizenyasuya said:
is it possible to extract the s-off boot-loader from a device with s-off already? My understanding of these procedures is rudimentary at best, but if my understanding is correct, the boot-loader is a specific partition on the device, if someone with an s-off device could copy that image to their computer or just a folder on their sd-card, it should be possible then to share that with others who could then write that image to their boot-loader partion using fastboot. or can you not use fastboot until s-off is achieved? i hate that i always forget these things once i have my device running the way i want it to.
Click to expand...
Click to collapse
In order to flash the s-off bootloader you would have to have a eng bootloader. to put that on you would need s-off dont you love loop 22
As for s-off it means you can flash what ever you want to your device and it will not check to see if HTC signed it and approved it for you

thanks for that works great!!!!!!!!! also mine is from a retail store same day it came out

is it possible to build a PG59IMG file and pack the S-Off hboot into there?? possibly use HexEdit to make sure the version numbers match so that the phone will think it's just a factory reset/update file??

DJAeroX26 said:
is it possible to build a PG59IMG file and pack the S-Off hboot into there?? possibly use HexEdit to make sure the version numbers match so that the phone will think it's just a factory reset/update file??
Click to expand...
Click to collapse
I think just by making that one hexedit you instantly invalidate the sign on the the zip. Mainly because hashing the new file would give you a different result.
This mechanism actually prevents OTA updates from flashing if the file was changed due to (for example) corruption.
Not entirely sure but I think it's how it works.
That being said I was wondering what would happen if someone with an S-OFF hboot were to dump it and someone with S-ON would simply DD the right partition after achieving temp root.
On any normal computer that process would work. Wondering what secret HTC things happen under the hood though.

Akujin said:
I think just by making that one hexedit you instantly invalidate the sign on the the zip. Mainly because hashing the new file would give you a different result.
This mechanism actually prevents OTA updates from flashing if the file was changed due to (for example) corruption.
Not entirely sure but I think it's how it works.
That being said I was wondering what would happen if someone with an S-OFF hboot were to dump it and someone with S-ON would simply DD the right partition after achieving temp root.
On any normal computer that process would work. Wondering what secret HTC things happen under the hood though.
Click to expand...
Click to collapse
There's only one way to find out.
Sent from a Western Union telegram.

Akujin said:
I think just by making that one hexedit you instantly invalidate the sign on the the zip. Mainly because hashing the new file would give you a different result.
This mechanism actually prevents OTA updates from flashing if the file was changed due to (for example) corruption.
Not entirely sure but I think it's how it works.
That being said I was wondering what would happen if someone with an S-OFF hboot were to dump it and someone with S-ON would simply DD the right partition after achieving temp root.
On any normal computer that process would work. Wondering what secret HTC things happen under the hood though.
Click to expand...
Click to collapse
Oh ok. Thanks for clarifying that. I thought it would work because last time I did a warranty exchange, I had to return to stock but I had an ENG hboot and I was scared of bricking by using a factory image, so I took the factory image zip, unpacked it, "injected" the original hboot (which I hex edited to match the version number so that it'll take it as an update) and rezipped it and named it PC10IMG.zip. and yea I have a G2 but I want this phone :]
Sent from my T-Mobile G2 using XDA App

[Q] Returning a Desire S to S-ON

Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.

schnidex said:
Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.
Click to expand...
Click to collapse
Go to shippedroms and download the RUU for your phone. Although why you'd want to return to stock is beyond me?

You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.

schnidex said:
You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.
Click to expand...
Click to collapse
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?

olyloh6696 said:
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?
Click to expand...
Click to collapse
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
kartkk said:
do a nandroid backup & also set up your adb beforehand
setting up adb saved me from possibly bricking my device a few times
try this guide
Click to expand...
Click to collapse

ben_pyett said:
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
Click to expand...
Click to collapse
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Sent from my HTC Desire S using XDA Premium App

olyloh6696 said:
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Click to expand...
Click to collapse
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.

ben_pyett said:
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.
Click to expand...
Click to collapse
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?

olyloh6696 said:
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?
Click to expand...
Click to collapse
If the ruu runs successfully to competition I believe that it will return the device do that it's identical to stock
Swyped from HTC Desire S using XDA Premium

After many, many hours of trying to figure out what the hell half the terminology about Android actually means and wondering whether or not I would brick my phone..
..I'm now back to S-ON. It's been a pretty horrible experience all in all. Yes, it's easy when you know how but knowing how has been through trial and fortunately not much error.
From being on 6.98.1002, I used the Jorgen method in Ben's link above to get to 0.98.0000. I should note that when my phone was first supplied, I was on 0.98.0002 and very worried that the earlier software wouldn't work - but I tried it anyway, and it did. However, I was still S-OFF.
I then re-installed my stock network ROM using the RUU. This kept me on 0.98.0000 but put the phone to S-ON. I flashed the branded ROM that the phone was shipped with thinking that this would take me to 0.98.0002 but to my surprise it didn't. Otherwise though, the phone is now stock condition again.
So I then tried to update OTA to the problematic software which caused me all this grief in the first place - and it appears my network have withdrawn it. And rightly so, pending a fix.

schnidex said:
Ben, I've seen elsewhere you've said:
"If you load the latest RUU you may end up updating the HBOOT so that it can't be downgraded."
..in which case, Houston, we may have a problem. The latest HTC non-branded ROM (1.47...) gives you HBOOT 6.98.1002.
Click to expand...
Click to collapse
You're right, I'm afriad that this is an area where I'm no expert, But HBOOT = 6.98.1002. = Alpharevx = so you've not upgraded it simply failed to downgrade (which is slightly better- I think )
I notice that there are a couple of guides, allow I've obviously not tried either of them both are in the [GUIDE] A Complete Tutorial for the Beginners and Others sticky
The second guide looks quite complex and not for beginners...
Although I've just spotted a note within the second guide which says says
Note 2: RUU 1.46 or greater can not be downgraded as yet, since gingerbreak does not work on these RUUs.
So Opps....a full nights sleep may shed some more light on this.....and hopefully so sound advice from someone who has already performed this task.
Good luck. (I'll back online in the morning) - but, only really able to answer easier questions and not unfortunately not provide you with a solution.....but I'll do what I can!

Alternate way to restore your phone to S-ON and stock
If your attempts are unsuccessful, there's another potential way to go S-ON.
http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2
Maarten

[htc] unlocking utility

I have been able to create a method of unlocking ANY unlockable hboot, on any device (as far as i can tell)
The method works on S-on, stock recovery devices. As of right now im linking to a specific device, however, if you only use the unlock youll be fine. I need testers from other HTC devices.
My first thread: http://forum.xda-developers.com/showthread.php?p=24370319#post24370319
If you like this, find it helpful, or want to support me please donate. Just follow these directions.
1) Be Logged-In to PayPal
2) Go to: https://www.paypal.com/[email protected]
2a) If that didnt work and fill out the E-Mail please, use [email protected] and select the way your sending as a GIFT
3) Enter the amount you want to give, Select personal, and Gift
4) Hit Continue and follow any of PayPal's Steps
5) Make sure that if asked, the receiving user DOES NOT Have to be verified.

I can confirm this works for MetroPCS Widfire S A510c hboot 1.10.0000. It unlocked my bootloader just fine. No steps required from HTCDev.
Many thanks Simon! Keep up the great work.

Great news!
But it's not full S-OFF, is it?

Not yet. This sets you up for it. Soon an soff will be out the developers of it need kernel help and I'm tryin to help them get it working
Sent from my HTC_A510c using Tapatalk

simonsimons34 said:
Not yet. This sets you up for it. Soon an soff will be out the developers of it need kernel help and I'm tryin to help them get it working
Sent from my HTC_A510c using Tapatalk
Click to expand...
Click to collapse
..well when s-off is out? Really dont unerstand for what is your "unlocking utility" then?

This utility allows you to unlock your bootloader without HTCDev, thus saving your warranty
Simon is working on getting universal S-OFF with some other devs. Will take a few, but he'll get it.

bobdamnit said:
This utility allows you to unlock your bootloader without HTCDev, thus saving your warranty
Simon is working on getting universal S-OFF with some other devs. Will take a few, but he'll get it.
Click to expand...
Click to collapse
with the option 1 of his tool "Bootloader Unlock CDMA ONLY" ??

That I'm not too sure about. I was told it was universal but needed testing. Simon and I have confirmed it working on several CDMA HTC Wildfire S's. (The only HTC phones we have access to, currently.)
I would say wait for Simon to confirm it should work on GSM HTC phones. I only helped with the code, so I don't know much about the mechanics of the utility.
Sorry.

according the .bat file all the stuff seems to be specific to the wildfire. So I don't undersand why simon is asking us to test it on other devices ?

geek78 said:
according the .bat file all the stuff seems to be specific to the wildfire. So I don't undersand why simon is asking us to test it on other devices ?
Click to expand...
Click to collapse
Because this method should work on ANY HTC phone with ANY hboot. We are asking you to try it so it can be confirmed. (Confirmed on Marvelc only so far.)
If you know batch, you can absolutely modify it to your liking.
Also, if you had read the original post:
Simonsimon34 said:
As of right now im linking to a specific device, however, if you only use the unlock youll be fine. I need testers from other HTC devices.
Click to expand...
Click to collapse

If you read the .bat file you can see that this can't work on another device

geek78 said:
If you read the .bat file you can see that this can't work on another device
Click to expand...
Click to collapse
S-OFF, no. That onlly works on CDMA Widlfire S. Unlock, yes. That should work on ANY HTC device, no matter what the batch file is calling. (It will still perform as it is supposed to.)
I helped write the batch file dude.

bobdamnit said:
S-OFF, no. That onlly works on CDMA Widlfire S. Unlock, yes. That should work on ANY HTC device, no matter what the batch file is calling. (It will still perform as it is supposed to.)
I helped write the batch file dude.
Click to expand...
Click to collapse
...can you attach the batch file here?

j4n87 said:
...can you attach the batch file here?
Click to expand...
Click to collapse
No I cannot. Since I am not claiming to be the author (only helped him a bit), I will not post their work. If Simon wants to release it, I'm sure he will.
I will however, give you a hint. Download the exe and run it. Leave it open and check your temp files. The batch file is in there somewhere.
Also, guys, give it a shot. At best, it works. At worst, it doesnt, and you still have a locked bootloader.

GUYS I will tell you how it works soon heck ill make its own release if you guys arnt suited with it. I just need to know if option one works. It uses a temp root pulls your misc img and modifys YOUR misc. This then flashes removes temp root and you have an unlocked bootloader. Just make sure your bootloader is up to date. There is nothing specific in the unlock
Sent from my HTC_A510c using Tapatalk

simonsimons34 said:
GUYS I will tell you how it works soon heck ill make its own release if you guys arnt suited with it. I just need to know if option one works. It uses a temp root pulls your misc img and modifys YOUR misc. This then flashes removes temp root and you have an unlocked bootloader. Just make sure your bootloader is up to date. There is nothing specific in the unlock
Sent from my HTC_A510c using Tapatalk
Click to expand...
Click to collapse
...well tried it on my HTC One X. no joy.
At least its says still "Locked" in bootloader.

Can you make sure no errors were thrown when temp rooting ? Or errors at all. Sometimes it tries to push too soon. Also can you try downgradeing to the lowest possible
Sent from my HTC_A510c using Tapatalk

simonsimons34 said:
Can you make sure no errors were thrown when temp rooting ? Or errors at all. Sometimes it tries to push too soon. Also can you try downgradeing to the lowest possible
Sent from my HTC_A510c using Tapatalk
Click to expand...
Click to collapse
..the HTC One is even not officially out in most countrys.
Theres nothing to downgrade.

Oh its because of the way I temp root. They must of patched it.
Sent from my HTC_A510c using Tapatalk

Any more news?

[Q] How root RUU 1.85

Im update to 1.85 and now i can't root my phone, help me please...

Currently there is no 1.85 root method..
I'm stuck in the same boat [and theres NO big flags saying "Upgrading to 1.85 means no root unless you do this first!"] and modified my CID from 11111111 [superCID] to the stock one so yeah. We'll either have to wait for the bootloader unlock // A force CID Method // and-or a root method to bypass the 1.85 issue or until a new update comes out with its own method(s).
Some people have had luck doing this though;
http://forum.xda-developers.com/showthread.php?t=1671396
By following the 12th step and attempting to use HTCDev.com.

I've tried everything to no avail on 1.85. Other ICS exploits such as Mempodroid have also been patched.
HELP!

TKTAB911 said:
Currently there is no 1.85 root method..
I'm stuck in the same boat [and theres NO big flags saying "Upgrading to 1.85 means no root unless you do this first!"] and modified my CID from 11111111 [superCID] to the stock one so yeah. We'll either have to wait for the bootloader unlock // A force CID Method // and-or a root method to bypass the 1.85 issue or until a new update comes out with its own method(s).
Some people have had luck doing this though;
http://forum.xda-developers.com/showthread.php?t=1671396
By following the 12th step and attempting to use HTCDev.com.
Click to expand...
Click to collapse
...

TKTAB911 said:
...
Click to expand...
Click to collapse
I was agreeing with you... I was also just saying that instead of waiting around, I've tried all of the other ICS exploits to see if anything was overlooked.

TKTAB911 said:
theres NO big flags saying "Upgrading to 1.85 means no root unless you do this first!"
Click to expand...
Click to collapse
True, the thread in which the RUU is posted has no such warning. But my index thread (sticky at the top of Development) is your friend. I even put it in boldface:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502 Warning: Can only be rooted if SuperCID before running this RUU. Details here
Also, as a rule, never update to a new official firmware, until you have done thorough research on whether a root method exists or still works. Its fairly common for new official ROMs to break existing root methods.

Root 1.85
crazydai said:
Im update to 1.85 and now i can't root my phone, help me please...
Click to expand...
Click to collapse
Could we try to reinstall RUU 1.73... or 1.82...? I have not attempted this but wondering if we could do that then root and so on?
Thanks,
David

djcortes said:
Could we try to reinstall RUU 1.73... or 1.82...? I have not attempted this but wondering if we could do that then root and so on?
Thanks,
David
Click to expand...
Click to collapse
I've tried doing this to no avail. I've tried both. I've even extracted the rom.zip and tried to replace it but I still the get the 140 bootloader error.

robertatl said:
I've tried doing this to no avail. I've tried both. I've even extracted the rom.zip and tried to replace it but I still the get the 140 bootloader error.
Click to expand...
Click to collapse
Well that blows!
thanks for answering the question though

robertatl said:
I've tried doing this to no avail. I've tried both. I've even extracted the rom.zip and tried to replace it but I still the get the 140 bootloader error.
Click to expand...
Click to collapse
What about replacing System.IMG inside of the %temp% folder with System.IMG from 1.82 with the /data/local/tmp exploit?

mbaran said:
What about replacing System.IMG inside of the %temp% folder with System.IMG from 1.82 with the /data/local/tmp exploit?
Click to expand...
Click to collapse
hmm.. I would be willing to try this but would need some guidance with the exploit.
meaning how to do it!
-David

djcortes said:
hmm.. I would be willing to try this but would need some guidance with the exploit.
meaning how to do it!
-David
Click to expand...
Click to collapse
I don't even know if it's possible, but when you start the RUU in windows it extracts it's whole working set of data to %temp% on Windows.
No idea if one System.IMG could be substitutes for the other, since it's all signed.

djcortes said:
hmm.. I would be willing to try this but would need some guidance with the exploit.
meaning how to do it!
-David
Click to expand...
Click to collapse
I just tried that exploit as well but it fails due to permission denied error

redpoint73 said:
True, the thread in which the RUU is posted has no such warning. But my index thread (sticky at the top of Development) is your friend. I even put it in boldface:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502 Warning: Can only be rooted if SuperCID before running this RUU. Details here
Also, as a rule, never update to a new official firmware, until you have done thorough research on whether a root method exists or still works. Its fairly common for new official ROMs to break existing root methods.
Click to expand...
Click to collapse
You did put a warning in the thread, but it's misleading and lead me to be stuck in stock 1.85. May I suggest that you re-word it "Can only be rooted if SuperCID -> Unlocked -> Relocked" so other people don't get confused. I set up SuperCID but did not unlock, and that's what screwed me.

red3gunner said:
You did put a warning in the thread, but it's misleading and lead me to be stuck in stock 1.85. May I suggest that you re-word it "Can only be rooted if SuperCID -> Unlocked -> Relocked" so other people don't get confused. I set up SuperCID but did not unlock, and that's what screwed me.
Click to expand...
Click to collapse
Can't you just unlock the bootloader now, since you already have SuperCID?
If not, that's news to me, and the reason my index thread is worded the way it is.

Yes, that worked! Thanks, sorry for the noobism.

red3gunner said:
Yes, that worked! Thanks, sorry for the noobism.
Click to expand...
Click to collapse
Ha, no worries! I was confused there for a second.

[Q] Moonshine S-Off Help

Could some one please help me with Moonshine S-Off process. I have been trying for 3 days now with no luck to s-off. I have checked that my firmware version is correct and i have followed the instructions explicitly. Every time ending with the same results error and please read
Thanks in advance

rompup said:
Could some one please help me with Moonshine S-Off process. I have been trying for 3 days now with no luck to s-off. I have checked that my firmware version is correct and i have followed the instructions explicitly. Every time ending with the same results error and please read
Thanks in advance
Click to expand...
Click to collapse
What steps are you taking?
Unlocked? Firmware?

mjsheldon4 said:
What steps are you taking?
Unlocked? Firmware?
Click to expand...
Click to collapse
Thanks for the reply. Sorry I should have been more specific. My phone has the latest t-mobile us update firmware version 3.14.531.11 i'm running the stock t-mobile rom. Bootloader is unlocked using htc dev
Steps; I uninstalled sync from my computer and extracted moonshine in the same folder where i have adb, fastboot installed. I tested adb commands to ensure the computer could communicate with the phone then I ran the distiller.exe and i can only get just past where it checks for updates (which is does successfully) then it fails. I read somewhere in a forum to freeze htc sync on the phone and i have tried this with still no luck. I have even tried deleting the apk with no result. I'm not sure what i am doing wrong but obviously something as others seem to have no problems. I have tried this on two different computers now with the same result.
Thanks again for your help

HTC Sync is the biggest obstacle. What step are you failing. There are 3 steps for testing. I could not get past 2nd and finally decided to tun in Linux. I had installed Linux Mint v14 on second hd but do not use much. It come handy this time. Went trough with no errors. The Ubuntu have program called "wubi" (I think) that will let you install linux alone with windows. You can uninstall latter as any programs. The moonshine web site have version for linux. Some users experience success in Windows by freezing the Sync. Unfortunately, you can not uninstall without being s=off.
In developer section, there is moonshine thread. See if you can get more info there.

One of the very first things that moonshine checks for is to verify that USB debugging is turned On. I see that you have tested the adb but just wanted to make sure that the USB debugging it active.
Sent from my HTC One S using xda premium

mjsheldon4 said:
One of the very first things that moonshine checks for is to verify that USB debugging is turned On. I see that you have tested the adb but just wanted to make sure that the USB debugging it active.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I am sure USB debugging is active but i cannot even get to the steps everyone speaks of. When I get home i have a linux machine set up i will try. Thanks for all your help.

This looks like a good place for my question.. I'm running moonshine and I love it. I'm just wondering for future reference, will I need to take any additional special steps before returning to stock via RUU. I already know about stock recovery and kernels and what not, just wondering if i will need to do anything specifically with moonshine before reverting to stock. Thanks!