Venom XL ROM Random Reboots and Signal Issues - AT&T, Rogers HTC One X, Telstra One XL

Hi All,
Firstly sorry as I know this must be covered somewhere, i just seem to keep going around in circles as to what I need to do to resolve the random reboots and signal issues I am experiencing after flashing the 4.2.0 Team VenomXL ROM.
From what I have read I need to update my HBoot as im currently on 1.14.002
My understanding is i need to be SuperCID, S-Off etc before I can update the HBoot and Radio.?
I have a Telstra HTC one XL with the following:
Tampered
Unlocked
EVITA PVT SHIP S-ON XL
HBOOT 1.14.0002
RADIO- 0.20os.32.09.15
OpenDSp-V29.1.0.45.0622
eMMC-boot
Jun 11 2012.14: 36.28
TWRP 2.3.1.0
My CID is TELST001
Am i correct in needing to SuperCID first then (Tried a program but exploit didn't work)
I have tried a handful of different app's and different methods but cant seem to get any further.
Even tried the CleanROM instead but couldn't get past boot screen even after flashing new Boot.img
Any help would be greatly appreciated!
Thanks again

Smitti086 said:
Hi All,
Firstly sorry as I know this must be covered somewhere, i just seem to keep going around in circles as to what I need to do to resolve the random reboots and signal issues I am experiencing after flashing the 4.2.0 Team VenomXL ROM.
From what I have read I need to update my HBoot as im currently on 1.14.002
My understanding is i need to be SuperCID, S-Off etc before I can update the HBoot and Radio.?
I have a Telstra HTC one XL with the following:
Tampered
Unlocked
EVITA PVT SHIP S-ON XL
HBOOT 1.14.0002
RADIO- 0.20os.32.09.15
OpenDSp-V29.1.0.45.0622
eMMC-boot
Jun 11 2012.14: 36.28
TWRP 2.3.1.0
My CID is TELST001
Am i correct in needing to SuperCID first then (Tried a program but exploit didn't work)
I have tried a handful of different app's and different methods but cant seem to get any further.
Even tried the CleanROM instead but couldn't get past boot screen even after flashing new Boot.img
Any help would be greatly appreciated!
Thanks again
Click to expand...
Click to collapse
I would say yes, you need to update your hboot and radio to the latest htc update, which can be found in the One Android Development forum, yes you'll need SuperCID and S-Off to do that, it's just a rule of thumb to have those taken care of anyway. Good luck!

TWRP version is extremely outdated, so that is likely why CleanROM won't install properly. Update to the current version (2.7).
However, CleanROM 7 will give you the same problems (random reboot and signal drops) as the Sense 5 base is the issue. You need to update the entire firmware package, not just the hboot (the radio is likely the root cause). And to do that, you needs s-off, as you have already figured out.
You need to use the hex edit method in order to get SuperCID on your version: http://forum.xda-developers.com/showpost.php?p=41640260&postcount=2
Apps or toolkits for this phone will likely fail to get SuperCID, as they are intended for the AT&T version (since SuperCID is needed on the AT&T version just to unlock bootloader). Since they look for the AT&T CID, they don't find it on your device, and the process fails.
After SuperCID, you may use Facepalm to s-off. Alternately, you can use Rumrunner or Firewater to s-off, as these methods do NOT require SuperCID as a prerequisite. All these methods can be found on my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
I would say start with Rumrunner, as its likely the easiest solution for your specific case.
Once you have s-off, you can use Turge's instruction to install the 2.15 firmware: http://forum.xda-developers.com/showpost.php?p=45072132&postcount=1

I'd say the easiest solution is the following:
1. Get s-off via Rumrunner.
2. Get SuperCID by issuing this fastboot command:
Code:
fastboot oem writecid 11111111
3. Update to the 2.15 firmware package found in the first post of this thread.
This is the easiest method because it means you don't need to mess around with hex editing your CID to get SuperCID. The Rumrunner s-off method is very easy and over you have s-off getting SuperCID is as simple as using the command I mentioned. From there updating your firmware is a piece of cake and you should suffer no more problems.
Sent from my Evita

Thankyou
Thank you soo much guys! All sorted up and running! Thanks again!

Good news. Please hit the thanks button on any posts you find helpful on XDA, it's how we show our gratitude here.
Sent from my MID-1040

Related

S-Off with HBOOT 2.00.0002?

Hi all,
I just got a new Desire S curtisy of O2 in the uk and noticed the HBOOT of 2.00.0002 which is not listed by the Revolutionary 0.4Pre4.
I was just wondering if there was another way or unless im missing somehing obvious.
Thanks in advance
You need to downgrade and then use revolutionary.
Details in my signature...
Edit: a quick search in the forums would have answered all your doubts...
Swyped from a primed Desire S
Cheers mate, Just found it :/
Man, these capcha's are SO annoying. WHy the hell on every post someone does? It's just annoying!
ANyways, Back on topic, I'm trying download HTCDEV for 'all other supported phones' from here:
http://htcdev.com/bootloader/
The problem is, It doesnt download. ANd when i change it to another option it still does sweet FA.
Is there anywhere else download this, Specificully, the all other phones option?
THanks for help and heres to the next annoying captcha
EDIT: A reboot sorted that problem out. Weird, but fixed
Well, I followed this guide:
http://forum.xda-developers.com/showthread.php?t=1525100
My phone now says
***UNLOCKED***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Its gone from locked to unlocked but isnt it meant to say S-OFF, not S-ON?
THe main problem though is i've loaded REAPER 2.2 Mod with the 2.21 upgrade but it seems to get stuck on a boot loop while booting up
Any idea's?
SOrry for noob questions, I've never done this myself as i got a friend to do it before. ANd thanks for the help
Dude, you have just unlocked the boot loader.
HTC dev unlock process will not give you S-off, also can cause some warranty issues (don't be disheartened)
Now you need to download a custom recovery and flash it via fastboot.
I would recommend 4ext touch.
Then flash any custom ROM. The guide should have all the details.
Swyped from a primed Desire S
suku_patel_22 said:
Dude, you have just unlocked the boot loader.
HTC dev unlock process will not give you S-off, also can cause some warranty issues (don't be disheartened)
Now you need to download a custom recovery and flash it via fastboot.
I would recommend 4ext touch.
Then flash any custom ROM. The guide should have all the details.
Swyped from a primed Desire S
Click to expand...
Click to collapse
I've done that, i used 4EXT_Recovery_v2.2.7_RC5.zip and thats ok. I cleared caches, Changed from 3EXT to 4EXT and then installed REAPER 2.2 then used update 2.2.1 over the top.
So i have 4EXT Recovery installed! I installed the ROM (off SDCARD) with this program and when i reboot it goes into a Boot Loop graphic and stays there.
4EXT Recovery Touch is just a touchscreen version of the one i used no?
fastboot flash boot boot.img
RolF2 said:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I've just done that and it works
Seem to find the answer myself after asking but i think i got the jist of this now.
Thanks for the help
Enjoy flashing.
try ICS and sense 4.0 lite. Its awesome.
HTC Desire HD stuck at Hboot
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Se 7 2011, 19:06:24
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Note: All buttons are not responding. Please help! Thanks!
1) You're in a wrong forum. This is Desire S, not Desire HD.
2) One of your buttons (VolDown) is stuck. Physically. Fix it.
I tried S-OFF my
unlocked (VIA htcdev)
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.50.24_M
eMMC-boot
CID VODA102 (GERMANY)
Got this RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.exe and tride to downgrade but no luck for me.
I want to try change HBOOT to 7.00.1002 and radio to 20.76.30.0835U_3831.19.00.110 bc I got FC com.android.phone with Unofficial "Nightly" CM11.0 (all 3 versions-Thanks developers for working on them).From what I see who have this HBOOT and radio they don't have FC like I do.Can I get exact guide sto S-OFF or anything to get this done?
Have you tried this guide?
http://forum.xda-developers.com/showthread.php?t=1318919
Thank you.With that guide I downgraded my hboot by installing RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed and revolutionary S-OFF.Flashed recorvery 4ext touch 1.0.0.6 RC1 and flashed Unofficial "Nightly" CM11.0 [20140228] by devil-kin and everything works.No FC com.android.phone.I can select 2G or 3G without problem.I will try tomorrow to change hboot to 7.00.1002 and radio to 20.76.30.0835U_3831.19.00.110 but for now CM11 works without problems.
Update: After reboot got FC com.android.phone.Switched to 3G and reboot and works good.Tomorrow will try new hboot and radio.
Success in flashing new hboot and radio.Having some issues with CM11 so I restored CM10.2.
suku_patel_22 said:
You need to downgrade and then use revolutionary.
Details in my signature...
Swyped from a primed Desire S
Click to expand...
Click to collapse
Hi, in your signature not details, please tell me how i can downgrade HBOOT
I tried htcdev but my rom version is 2.10.401.8 and not listed on there
Is it now possible to S-OFF a Desire S since the revolutionary site is no longer active ? I can unlock the bootloader via HTCDEV but I'd like to get S-OFF if possible ?
CRJ343 said:
Is it now possible to S-OFF a Desire S since the revolutionary site is no longer active ? I can unlock the bootloader via HTCDEV but I'd like to get S-OFF if possible ?
Click to expand...
Click to collapse
According to this thread the URL has changed: http://rev.alpharev.nl/
Implications of running an older HBOOT
Stevolk said:
According to this thread the URL has changed: http://rev.alpharev.nl/
Click to expand...
Click to collapse
Maybe a slightly naive question......but I obviously need to downgrade my HBOOT to achieve S-OFF on the phone via the Rev method.
Can I restore my HBOOT version back to 2.00.0002 without running another RUU through it or is there another method.
My MIUI ROM works OK under 2.00.0002 should expect problems if it it runs under an earlier version ?

Super CID, S-off/on questions

Forgive my noobness, Its been ages since I've had a HTC device to play with. I've been reading and just wanted to clarify my findings with some recent answers.
1. T-mobile ONE S, H-boot 2.15, and TMOB010 CID. 3.14.531.17 710rd.
I attempted to get Super CID, but it wouldnt stick. was trying to S-off via facepalm method, as Moonshine stated a different version required.
So my findings are its not possible, is that correct? Thats kinda leaning towards both super CID, and S-off
2. I got PacMan on the device, and am gonna update to the newest, am curious if I have to flash the boot.img after updating?
Again, I have read, and searched. If I missed something that's already around please let me know as I'm not looking to get spoonfed due to laziness.
HTC introduced a write protection for mmcblk0p4 with its 2.15.0000 (2.15.4444) bootloader. So these devices can't get SCID a 'regular' way. If there is a way to flash a working RUU version for moonshine, I don't know. You'll have to read again for these things in the moonshine/facepalm threads.
And yes on an s-on device you should always flash the kernel separately with 'fastboot flash boot boot.img'.
--- edit
e.g. check out post #4 here
rootrider said:
HTC introduced a write protection for mmcblk0p4 with its 2.15.0000 (2.15.4444) bootloader. So these devices can't get SCID a 'regular' way. If there is a way to flash a working RUU version for moonshine, I don't know. You'll have to read again for these things in the moonshine/facepalm threads.
And yes on an s-on device you should always flash the kernel separately with 'fastboot flash boot boot.img'.
--- edit
e.g. check out post #4 here
Click to expand...
Click to collapse
My phone is from Cincinnati Bell carrier and it was with 2.15.0000 hboot, but I did s-off because mmcblk0p4 was writable, so it is good to test is it writeable or not.

[Q] Need Help Getting SuperCID with MID/CID Mismatch

Hi! First time posting in this amazing community...
I have an HTC One S (T-Mo). I was fooling around with it and flashed it with HTC_Europe 3.16 firmware. I didn't realize that the device was SuperCID already, and flashing changed the CID to HTC__001. (CRAP)
It's also S-ON (double CRAP)...
So here I am:
-I can't Facepalm because I can't get SuperCID.
-I can't Moonshine because the CID is HTC__001 and doesn't match the MID (T-Mobile), so neither the Europe nor T-Mo RUUs work...
So - how can I get the device back to SuperCID or T-Mo US CID...? Currently running Philz CWM and Cyanogenmod 10.0...
Thanks!
helpful_onlooker said:
Hi! First time posting in this amazing community...
I have an HTC One S (T-Mo). I was fooling around with it and flashed it with HTC_Europe 3.16 firmware. I didn't realize that the device was SuperCID already, and flashing changed the CID to HTC__001. (CRAP)
It's also S-ON (double CRAP)...
So here I am:
-I can't Facepalm because I can't get SuperCID.
-I can't Moonshine because the CID is HTC__001 and doesn't match the MID (T-Mobile), so neither the Europe nor T-Mo RUUs work...
So - how can I get the device back to SuperCID or T-Mo US CID...? Currently running Philz CWM and Cyanogenmod 10.0...
Thanks!
Click to expand...
Click to collapse
AFAIU it all depends on the xxx after the 3.16. in the version of the firmware, which method is likely to work with your device.
helpful_onlooker said:
Hi! First time posting in this amazing community...
I have an HTC One S (T-Mo). I was fooling around with it and flashed it with HTC_Europe 3.16 firmware. I didn't realize that the device was SuperCID already, and flashing changed the CID to HTC__001. (CRAP)
It's also S-ON (double CRAP)...
So here I am:
-I can't Facepalm because I can't get SuperCID.
-I can't Moonshine because the CID is HTC__001 and doesn't match the MID (T-Mobile), so neither the Europe nor T-Mo RUUs work...
So - how can I get the device back to SuperCID or T-Mo US CID...? Currently running Philz CWM and Cyanogenmod 10.0...
Thanks!
Click to expand...
Click to collapse
I was able to change to supercid with the same config as you have ( 3.16.401.8 and origo cid HTC__001) so it should for you. If you'll manage to supercid just get s-off useing facepalm metod. Worked for me.
Sent from my HTC One S
if you got the xxxxxxx.9 it wont work indeed.
but on the xxxxxxxx.8 supercid/facepalm method should work, i did this myself back then.
since hboot didnt change going from .8 to .9, it might be possible to reflash the ruu to get back on .8 (as you did before i presume).
but if the ota going to .9 did change something permanent its a bust.
I believe the RUU I tried flashing was HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L...
-If I go the Facepalm route, I have to SuperCID. I can't because I am unable to change mmcblk0p4 (write-protection, I'm guessing. I did take the JB OTA from T-Mobile at one point...)
-If I go the Moonshine route, the device crashes when Moonshine tries the ADB test (reboot from bootloader). This happens using the ville_3.16.661.4 and ville_3.14.531.11 versions...
Possible solutions:
1. Downgrade hboot to an earlier version without write-protection on mmcblk0p4 so I can SuperCID -> Facepalm. I'm currently on hboot 2.15 - is this possible?
2. Flash a ROM of a firmware supported by Moonshine - anyone have that?
rialsolk pecans
UPDATE: I apologize for the double post, but I was able to S-OFF using Moonshine.
What I used:
ViperROM 2.1
TWRP 2.3.3.0
Windows 7 Pro x64
Moonshine - HTC One S Telus Windows 3.16.661.4
I currently have hboot 2.15. Thanks for looking!

Can't get Supercid nor S-OFF on HTC One S.

Please help me, I'm desperate.
- I want to install MaximusHD ROM.
- I have HBOOT 2.15.
- I unlocked bootloader via HTCDev.
- I have CM10.1 running on my phone.
I tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
This: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
I haven't even tried using the facepalm method because I can't get supercid.
After I followed all the steps correctly, I run command "fastboot oem readcid" and still get the T-MOB010 CID.
I repeated the whole process 3 times, making perfectly sure I didn't make any mistake and still, can't get supercid 11111111.
I tried using moonshine method too, but when I run distiller.exe at the end it says read and try again or something. So I just cant get S-OFF or supercid.
Please tell me how can I get MaximusHD Rom working on my phone! Please! :/
Is there anyone who can help me S-off my HTC device?
Sent from my One S using xda app-developers app
rolo143 said:
Is there anyone who can help me S-off my HTC device?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Im in the same boat, Ive found my partition is write protected and cant find any other method to do it, I have tried both moonshine (my device isnt supported) and facepalm (protected partition) methods. Ive given up and stuck with MagioRom, which is like MaximusRom, but not so stable currently, but saying that the last RC5 of Magio is stable for me so far.
rolo143 said:
Please help me, I'm desperate.
- I want to install MaximusHD ROM.
- I have HBOOT 2.15.
- I unlocked bootloader via HTCDev.
- I have CM10.1 running on my phone.
I tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
This: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
I haven't even tried using the facepalm method because I can't get supercid.
After I followed all the steps correctly, I run command "fastboot oem readcid" and still get the T-MOB010 CID.
I repeated the whole process 3 times, making perfectly sure I didn't make any mistake and still, can't get supercid 11111111.
I tried using moonshine method too, but when I run distiller.exe at the end it says read and try again or something. So I just cant get S-OFF or supercid.
Please tell me how can I get MaximusHD Rom working on my phone! Please! :/
Click to expand...
Click to collapse
Hi,
can you provide a log (or screenshots) of all the commands you enter and the files you push / pull?
Have you tried Moonshine S-OFF?
I can't. I didn't take screenshots, but believe me, I follow exactly the steps in the above mentioned thread to get supercid. But it just didn't stick. I keep getting T-MOB010 cid.
I think there's nothing I can do because my phone isn't supported by moonshine (I think) and my hboot is 2.15
Anyway I want to try MagioROM. Is it stable now or will it give me constant reboots?
Sent from my One S using xda app-developers app
Try to install official RUU to your phone. Before that you need reblocked your bootloader. After installation unlocked bootloader again and try get S-OFF.
Sent from my HTC One S using XDA Premium 4 mobile app
Malexion said:
Try to install official RUU to your phone. Before that you need reblocked your bootloader. After installation unlocked bootloader again and try get S-OFF.
Click to expand...
Click to collapse
+1 on Malexion's suggestion.
Being on HBOOT 2.15 is not enough. For Moonshine to work, you need to be on one of the supported firmwares listed at the top of the Moonshine OP:
3.14.531.11 (T-MOB)
3.16.666.9 (BM)
3.16.111.10 (TMO_DE)
3.16.661.4 (Telus)
Click to expand...
Click to collapse
If you have an RUU available for your carrier that's on one of those, it can be done..
I'm on T-Mobile US, and had accepted the OTA JB update to 3.14.531.17 before deciding to go for S-OFF. That little OTA update from .11 to .17 apparently includes some cute write protection that doesn't allow for SuperCID (among other things). As with you then, Facepalm was out of the question for me.
So I turned to Moonshine, which worked after jumping through the right hoops:
Downloaded supported RUU
Verified that RUU matched my carrier, HBOOT and baseband
Locked bootloader
Flashed RUU (in my case, I was going back to 3.14.531.11 (T-MOB))
Unlocked bootloader (you'll need to get a new unlock key from htcdev)
Ran Moonshine
Moonshine worked on the first try for me, but from reading the posts, it's clearly not as easy for everyone (especially on Windows for whatever reason).
Hopefully that helps, but happy to provide more info if you have questions.
Good luck!
---------- Post added at 10:23 PM ---------- Previous post was at 10:17 PM ----------
rolo143 said:
I tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
Click to expand...
Click to collapse
Also, forgot to mention that Moonshine does not require SuperCID. I never had it and still don't. (If Moonshine S-OFF works for you, it's easy to get SuperCID if you really need it -- which I don't, so I haven't bothered yet).
T-Mobile
I'm also on T-Mobile and I wish I saw your post before I "upgraded" from .11 to .17. Quick question for you, because I just got this phone and don't know a whole lot about it. I've heard that HTC and/or Google released a jelly bean update that was horrible on the battery, and had to follow up with an update.
Is the .11 update the battery draining bad update? Is the battery drain problem something that can be fixed via a rom, rather than the update?
I guess that was more than one question, but any answers would be much appreciated. Also, if you could comment on your battery life since moving down to .11....
Yes, the .11 OTA was the first JB rollout for this phone, and the .17 OTA was released soon after to correct the battery drain issue.
I was only on the older .11 firmware for a few days before I flashed a new ROM, but it seemed pretty brutal. I'm still new to flashing ROMs, though, and I've read that it can take a new ROM a little time to optimize battery life... Not sure if that also applies to RUUs.
But it was bad enough that I would recommend only flashing the .11 firmware if you intend to switch to another ROM.
Anyhow, I flashed AOSPA 3+ a few days later and love it. A stable port, fast and fun to play with the hybrid engine. Battery life on PA has been good so far, seems on par or better than the .17 firmware in my case.
Hope that helps!
---------- Post added at 02:08 AM ---------- Previous post was at 01:50 AM ----------
Clarification: I would only bother with the older firmware as an interim step to (a) getting Moonshine S-OFF before flashing a new ROM, or (b) going back to stock and eventually the later .17 version via OTA.
(If you ever go back to stock, be *very* careful to read up on proper procedure before ever allowing a carrier OTA once you've played around with your phone... There are one or two cases where a carrier OTA is an instant brick scenario if you don't take the proper precautions).
When I type on cmd command:
"fastboot getvar all"
this is what appears:
Code:
version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.13.50.05.31
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT242W420470
imei: 359902047827302
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: T-MOB010
battery-status: good
battery-voltage: 3964mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0
Now, from here... Can someone please tell me how to find my corresponding RUU file? How can I install it? Do I need S-OFF for that? Please help... I don't really understand how can I achieve S-OFF in my HTC One S and I read a LOT of guides already.... Just don't know what can I do so I can install MaximusHD Rom and stick with it.
@rolo143: I'll pull together my exact steps for you when I'm in front of my computer again... In the meantime, to stay safe I would remove your serial number and imei from your last post.
Flashing the RUU so you can run Moonshine S-OFF
1: VERIFY ADB/FASTBOOT ENVIRONMENT & HTC DRIVERS ARE WORKING
Boot phone into fastboot mode (boot into bootloader, select "fastboot" from hboot menu).
Connect to PC (phone will now show "fastboot USB" highlighted), open command prompt and enter:
fastboot devices
It should return "[serial number] fastboot" if it's working properly.
You've already entered fastboot getvar all to get the info you need to get the correct RUU.
Click to expand...
Click to collapse
2: MAKE A NANDROID BACKUP
Use your custom recovery (TWRP or ClockworkMod) to make a backup of your device.
Put a copy of your nandroid onto your PC for safe keeping.
Click to expand...
Click to collapse
3: DOWNLOAD THE APPROPRIATE RUU
I got my RUU from this xda thread:
Since you're not S-OFF and SuperCID, you have to use an RUU that matches your carrier, hboot and baseband (radio).
Based upon your fastboot getvar all results...
Your carrier: T-MOB010 (cid) = TMUS (T-Mobile US carrier) ... I used this cid list to double-check this.
Your current hboot: 2.15, which will work with the JB 3.14.531.11 RUU you're going to flash, so you're good there.
Your current radio: 1.13.50.05.31.
I downloaded the matching RUU (you'll be using the same that I did):
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release... (truncated rest of filename).
Happily, this RUU is one of the four firmware versions supported by Moonshine S-OFF.
Click to expand...
Click to collapse
4. LOCK BOOTLOADER
Put phone into bootloader mode, connect to PC, open command prompt and enter:
fastboot devices
If it shows your serial number again, then enter:
fastboot oem lock
Your bootloader will now be locked and the phone may reboot back into bootloader. Leave the phone connected to the PC.
Click to expand...
Click to collapse
5. RUN THE RUU
Leave phone in fastboot mode (if it rebooted to bootloader you may need to select "fastboot" again). You should see "Fastboot USB" highlighted on the phone.
On your PC, run the RUU (.exe) that you downloaded. Give it a few minutes after you run it, as it took mine a while to actually look like it was doing anything.
Once it finally loads, you'll get a window that gives you a series of instructions. Follow them and then let it do it's thing.
Do NOT unplug your phone from the PC (I wouldn't touch the thing, frankly) until it reboots the phone automatically.
Once your phone reboots to system, it'll be running 3.14.531.11 Jellybean!
Click to expand...
Click to collapse
5. MOONSHINE S-OFF
Revisit the Moonshine S-OFF thread and follow the instructions very deliberately. Now that you're on a supported firmware, it should work.
---- EDIT ---- After you successfully run the RUU, you'll need to unlock your bootloader again before running Moonshine. You won't be able to use your old unlock .bin file, so you'll need to request a new one via htcdev. If you want to brush up on that, follow the unlock instructions on this xda tutorial thread.
Good luck!
Click to expand...
Click to collapse
Good post
When I did moonshine, I eventually put mint linux on a laptop just to get it to work. Where there is a will there is a way.
Thanks... I've learned a ton over the last few months from everyone being so supportive here. Want to give back a little where I can.
I tried and tried to set up Ubuntu Linux, but I simply could not get it to play nicely with my MacBook Pro. For my new Android obsession, I'm running Windows through Parallels, and I didn't want to use that for Moonshine since they don't officially support VMs. But the Ubuntu install on my particular hardware just kept throwing up too many roadblocks. Thankfully, I was able to pretty carefully manage my HTC driver setup on the Mac and in the VM, and once I figured out the right combo, my adb/fastboot connections have been rock solid. So I took a deep breath and gave Moonshine a go through Parallels, and it took on the first try. Go figure, after all of my toying around with Linux.
super cid
hi
my one s ville is for TIM Italya operator
when i want to perform super cid ,my cid is TIM--401
I change it to 11111111 but it doesnt work and my cid again is TIM--401
WHAT should i do for super cid my phone????
2k10GT said:
Flashing the RUU so you can run Moonshine S-OFF
Click to expand...
Click to collapse
Great post and thank you for the effort to write the detailed instructions. I was able to successfully do the moonshine s-off
rolo143 said:
Please help me, I'm desperate.
- I want to install MaximusHD ROM.
- I have HBOOT 2.15.
- I unlocked bootloader via HTCDev.
- I have CM10.1 running on my phone.
I tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
This: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
I haven't even tried using the facepalm method because I can't get supercid.
After I followed all the steps correctly, I run command "fastboot oem readcid" and still get the T-MOB010 CID.
I repeated the whole process 3 times, making perfectly sure I didn't make any mistake and still, can't get supercid 11111111.
I tried using moonshine method too, but when I run distiller.exe at the end it says read and try again or something. So I just cant get S-OFF or supercid.
Please tell me how can I get MaximusHD Rom working on my phone! Please! :/
Click to expand...
Click to collapse
If it works in windows moonshine I did this tutorial but in spanish to help all who have problems to make the soff
http://www.taringa.net/posts/celulares/17401702/Como-hacer-soff-en-HTC-one-s-3-14-531-17RD.html
2k10GT said:
Flashing the RUU so you can run Moonshine S-OFF
Click to expand...
Click to collapse
Thanks for that concise summary. It helped me when I finally decided to get around to get S-OFF on my phone (flashing boot.img with every ROM switch/update/downgrade/etc. got tiresome).
Hello everybody!
I am can't get SuperCID in my HTC One S. In this time i have in phone root, unlock from htcdev and it's all. Trying with adb command receive T-MOB010 Cid, Moonshine after 3'd reboot stopping in '.........' in Fastboot. This '.......' points I am wait for 30 min and after disconnecting phone it still writing in comp screen. RUU from TMOB supported by Moonshine is installed to phone. What I wrong doing. *wall*. Help me, please!
> tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
Wait. You do not have to have SuperCID to get S-OFF.
Try moonshine. Some of us couldn't get S-OFF any other way. Also, I had to use an Ubuntu Live CD - Windows didn't work for me no matter what I tried. It kept getting stuck at "..........."
When I used the Ubuntu live CD it went right through.

[Q] Trying to return to stock - multiple problems

Hello,
I'm having a nightmare trying to return my HTC One X to stock.
Here is my phone info:
CyanogenMod version 11-20140907-NIGHTLY
Android Version 4.4.4
Baseband 0.24p.32.09.06_10.130.32.34L
Kernel 3.4.82-g585943f [email protected] #1
Bootload info
EVITA PVT SHIP S-ON RL
HBOOT -2.14.0000
Radio 0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
My ultimate goal is to return to stock.Unforunately I made a vital error awhile ago and wipe everything including my nandroid. I did have a copy on my pc but for whatever reason TWRP would not recognize it.Therefore I first wanted to try to get S-off so I could then just RUU back or flash a stock at&t rom.
I tried rumrunner and I followed the steps and it seemed like it should have worked but it still showed S-on. Reading through the posts it was suggested to be on 4.1 or below. I then tried to install MDOB v1. However, it installed but there was no touchscreen function. Searching through the forums for touchscreen downgrading firmware all answers seemed to lead to one thread in the sticky which is now deleted.​
Do you have the at&t model? What is your CID?
Transmitted via Bacon
Oh shoot forgot that sorry. AT&T and CID 11111111
tommyphammy said:
Oh shoot forgot that sorry. AT&T and CID 11111111
Click to expand...
Click to collapse
Try Facepalm s-off instead
http://forum.xda-developers.com/showthread.php?t=2155071
Transmitted via Bacon
Thank you! I actually tried that before but I now realized I forgot to allow adb root access.

Categories

Resources