Hello,
First thanks to any for all help I'm sure I'll receive. Im pretty sure of what I need to do but I'm a resident physician and can't afford to not have a phone by making a stupid mistake.
So I currently have supercid, am unlocked and rooted with boot loader 1.14. To update basically any roms or my current AOKP ROM I need 2.14. To get 2.14 I need to S-off, relock boot loader and run the 3.18 ruu, and reflash recovery.
Is this correct? The only other I'm confused of is relocking the bootloader, and them unlocking it again.
Thanks for any help.
Sent from my One X using XDA Premium 4 mobile app
You only need s-off to run the 3.18 RUU, locking the bootloader isn't necessary and only creates more work afterwards. So all you need to do is go here and get s-off, then you can download the RUU from here and run it. Your unlocked bootloader and s-off status will survive the RUU process but you will need to install TWRP recovery again afterwards.
Sent from my Evita
Thank man
Sent from my One X using XDA Premium 4 mobile app
No problems.
Sent from my Evita
timmaaa said:
You only need s-off to run the 3.18 RUU, locking the bootloader isn't necessary and only creates more work afterwards. So all you need to do is go here and get s-off, then you can download the RUU from here and run it. Your unlocked bootloader and s-off status will survive the RUU process but you will need to install TWRP recovery again afterwards.
Sent from my Evita
Click to expand...
Click to collapse
Will /SD survive the process as well? I have TWRP 2.6.00 on /SD at the root level and have been able to access it from the bootloader.
Thanks again, Timmaaa!
Your sd card shouldn't be wiped during the RUU process but you might want to make a backup just in case.
Sent from my Evita
how do I root again after RUU? do I just need to flash recovery image?
Just flash recovery and then a rooted ROM.
Sent from my Evita
thanks man. appreciate your help.
I've tried and have only been able to obtain unlocked boot loader and root no super cid or s-off ... I'm not sure what I'm missing ...
Sent from my HTC One X using Tapatalk[/QUOTE]
Sent from my HTC One X using Tapatalk
What are your bootloader details and which SuperCID method are you using?
Sent from my Evita
timmaaa said:
What are your bootloader details and which SuperCID method are you using?
Sent from my Evita
Click to expand...
Click to collapse
I finally was able to get it work I'm s-off know
Sent from my HTC One XL using Tapatalk
timmaaa said:
You only need s-off to run the 3.18 RUU, locking the bootloader isn't necessary and only creates more work afterwards. So all you need to do is go here and get s-off, then you can download the RUU from here and run it. Your unlocked bootloader and s-off status will survive the RUU process but you will need to install TWRP recovery again afterwards.
Sent from my Evita
Click to expand...
Click to collapse
This might be a dumb question but how do u run the 3.18 RUU? Do i plug my phone via usb and then run it? What do i do?
It's an exe file, so all you need to do is open it in Windows while your phone is connected in fastboot mode, then just follow the prompts. Make sure HTC Sync Manager is uninstalled, make sure no other programs are running, make sure screen saver/hibernation is turned off.
Sent from my Evita
Related
I cannot boot into ROM, but stuck at Bootloader. And I'm relocked.
The only thing I have is Fastboot USB.
I would like to RUU into a Stock ROM. How to do so?
Well ruu should be pretty self explanatory. If you are in the boot loader just run the ruu. Since you are relocked shouldn't take much work. Are you s-off? Why not just grab an AT&T ROM and flash it over. Sure it will be rooted, but delete the super user app
Sent from my Carbon-ize Evita using xda-developers app
Yeah, I just figured it. RUU was some executable file. I thought it was more complicated. No I'll just leave it like this and not S-Off, thanks. Apparently I'm not more than 30% battery though. But how do I see the battery from the Bootloader screen?
I dont believe you can. Only from recovery. Just let it charge for about 20-30 mins and you should be good
Sent from my Carbon-ize Evita using xda-developers app
If you have supercid and s-on running a ruu will brick your phone just a warning
Sent from my HTC One X using Tapatalk 2
How do I check if I have SuperCID or not?
And apparently the device name is GT-9100 which seems wrong...?
There is command in fastboot I think it is fastboot get cid but not sure do you have a att phone
Sent from my HTC One X using Tapatalk 2
Nope, I do not. I do not need to worry about that then.
No you should be ok att phones are the only ones that had to change there cids to unlock bootloader
Sent from my HTC One X using Tapatalk 2
Fastboot oem readcid
Sent from my One X using xda app-developers app
exad said:
Fastboot oem readcid
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Thanks couldn't remember what it was
Sent from my HTC One X using Tapatalk 2
Oh no! Can anyone please help me?
None of the RUUs work.
I'm Asian and I tried all:
1.88.707.2 ( Error 170, bad USB )
2.23.707.2 ( Error 170 )
This is the only one that I could select ROM and upgrade.
3.17.707.1 ( Less than 30% error is result of previous fail, so reboot. Actual Error 155 )
And I'm S-ON
hboot 1.09
radio 0.17a.32.09.16_2
OpenDSP - What's this and is it useful for my situation?
eMMC - boot
Apr 2 2012, 21:08:21
I think probably I can only install 3.17 RUU is because my last working ROM was CM10.1. After that I tried Sense ROMs but many failed hence I thought of doing Relock and RUU.
Is there any other thing I can do in my bootloader state? I tried Factory Reset.
Is it possible I attain S-OFF from here and flash recovery and flash OTA from there?
Or even better yet, can I try doing OTA from this state?
Aerodeath said:
And I'm S-ON
hboot 1.09
radio 0.17a.32.09.16_2
OpenDSP - What's this and is it useful for my situation?
eMMC - boot
Apr 2 2012, 21:08:21
I think probably I can only install 3.17 RUU is because my last working ROM was CM10.1. After that I tried Sense ROMs but many failed hence I thought of doing Relock and RUU.
Is there any other thing I can do in my bootloader state? I tried Factory Reset.
Is it possible I attain S-OFF from here and flash recovery and flash OTA from there?
Or even better yet, can I try doing OTA from this state?
Click to expand...
Click to collapse
I thought if you ran the ruu with s on you could brick...just obtain s off and then run the ruu
Sent from my Carbon-ize Evita using xda-developers app
I can't successfully S-OFF because I can't get into Android, stuck at bootloader.
And I'm not on AT&T, I don't need superCID and I can't change it to 11111111 either...
My CID is HTC__044
version-main is 1.88.707.2
Bootloader relocked
hBoot now 2.14?!
RUU_Evita_UL_hTC_Asia_WWE_1.88.707.2_R3_Radio_0.17a.32.09.16_2_10.88.32.17L_release_263455_signed should work but it didn't...
Never mind, everything seems to be working now.
It seemed that my hboot was too low to attempt RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed and Running as Administrator helped too.
Aerodeath said:
I can't successfully S-OFF because I can't get into Android, stuck at bootloader.
And I'm not on AT&T, I don't need superCID and I can't change it to 11111111 either...
My CID is HTC__044
version-main is 1.88.707.2
Bootloader relocked
hBoot now 2.14?!
RUU_Evita_UL_hTC_Asia_WWE_1.88.707.2_R3_Radio_0.17a.32.09.16_2_10.88.32.17L_release_263455_signed should work but it didn't...
Never mind, everything seems to be working now.
It seemed that my hboot was too low to attempt RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed and Running as Administrator helped too.
Click to expand...
Click to collapse
I'm telling you this because I don't want you to go through what I did.
I'm on a telus one x, did not need super cid to unlock my bootloader. I relocked and flashed stock recovery, ran RUU. The RUU completed successfully but my phone was a full brick. Only JTAG would have saved it.
If you want to RUU, re-unlock your bootloader, flash recovery, flash stock rooted sense rom, hex edit your CID to 11111111 and S-OFF, then RUU. It's a lot safer now that you've unlocked your bootloader and rooted.
exad said:
I'm telling you this because I don't want you to go through what I did.
I'm on a telus one x, did not need super cid to unlock my bootloader. I relocked and flashed stock recovery, ran RUU. The RUU completed successfully but my phone was a full brick. Only JTAG would have saved it.
If you want to RUU, re-unlock your bootloader, flash recovery, flash stock rooted sense rom, hex edit your CID to 11111111 and S-OFF, then RUU. It's a lot safer now that you've unlocked your bootloader and rooted.
Click to expand...
Click to collapse
It's okay, I was running an international One XL, and luckily RUU was smooth, now the problem is solved and my phone has been sold and changed hands .
I've been running AOSP ROM's on my evita for a while now, but apparently with the 3.4 kernel you now need hboot 2.14 or higher and mine's at 1.09. My phone was unlocked with S-ON, but I did "fastboot oem lock" this morning because I read that it's necessary for an RUU. I downloaded the 2.20 RUU and tried to run the installer but I always get an Error [170] USB Connection Error. I have the HTC and adb drivers installed successfully and have tried to run the RUU as admin in both Sense and fastboot (bootloader). I'm a bit stumped and would really like to get AOSP back on my phone.
You need to S-off first.
Sent from my HTC One X using xda premium
tlazarus said:
You need to S-off first.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Should I use facepalm for that then?
EDIT
I got s-off, but still no go. Still the error 170.
I know on my old Incredible I was able to rename the rom.zip from the RUU as PB99IMG.zip and put it on the root of my sdcard. Then in hboot it would detect it and ask to flash it. This isn't happening on my evita though. Is there a way to do that, or is that only for older htc devices?
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Venomtester said:
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Where can I find this error log? It did see my device, I did that command (which ended at the black htc screen) and I ran the RUU again but I still get the error 170. I'm also using this RUU http://bugsylawson.com/index.php/fi...320911-2-101053225l-release-271865-signedexe/
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Venomtester said:
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It is that size, though I may try the link you gave.
EDIT
Okay, I think I found out what I've been doing wrong. I found this link http://forum.xda-developers.com/showthread.php?t=2119610 and it turns out that the file I've been trying does NOT include the 2.14 hboot that I need. The one I need is the latest JB release, but someone said that if you flash it with superCID and S-ON that it will brick your device. I have superCID but S-OFF, does anyone think that will brick my device? Should I flash the RUU with the 1.09 hboot (which I'm running) first, and then flash the newest RUU? Also, it looks like the link I provided offers flashable OTA's of each update. Would those work/be recommended for TWRP?
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Venomtester said:
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
dshoe said:
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
Click to expand...
Click to collapse
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
31ken31 said:
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
dshoe said:
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
Click to expand...
Click to collapse
Just make sure you are s-off before running ruu or risk a brick..
Sent from my HTC One XL using xda premium
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
For what it's worth, I was on stock 2.20, got s-off and unlocked bootloader with superCID, and ran the 3.18 RUU with no problems. I didn't need to relock or anything.
knanda said:
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
Click to expand...
Click to collapse
You can go ahead and run the RUU. No real risk because you're s-off. Maybe make a backup though.
Sent from my Evita
Hi everyone,
This is my very first post and I'll admit I am a NOOB.
As I've searched XDA and Google for my questions, I am really at a loss and thought I would pose my question(s) to the community.
I have a Rogers HTC One X(Evita) running CM 10.0, I am currently S-ON, with TWERP 2.3.1
I would like to install the latest CM but it would seem my HBOOT (1.11) needs to be upgraded.
My first question is if my CID is Roger001 is this similar to being SuperCID?
If so, which firmware is recommended? Which is the latest HBOOT I should upgrade to?
I guess this brings me to my next question, what exactly do I need to be able to upgrade my HBOOT?
I've seen a few walkthroughs but none mention Roger001 as CID and I'd rather not risk bricking my phone.
If you need any other information, please let me know.
Any assistance is greatly appreciated.
You definitely need to update your phone in order to flash the latest cm ROM. But, with your phone in its current state you'll brick it. You don't have SuperCID (11111111), you'll definitely need to get that first, then get s-off, then you can RUU up to the latest. Links to everything you need are in this thread.
Sent from my Evita
Thanks Tim.
I'll give that a whirl and let you know how it turns out.
Another silly question, what exactly is RUU?
Sent from my One X using xda app-developers app
RUU stands for ROM Update Utility. It basically takes your phone back to being completely stock, including recovery. The beauty of being s-off when you run an RUU is the s-off status survives the process, and so will your unlocked bootloader. So all you need to do when it's finished is flash TWRP again via fastboot, then flash your ROM via TWRP.
Sent from my Evita
Ahh
That makes perfect sense!
If I wanted to stay stock, I could?
Sent from my One X using xda app-developers app
Yeah there's nothing stopping you. Then if you change your mind it's as simple as following the steps I mentioned before.
Sent from my Evita
I haven't had a chance to try anything as of yet but I've been doing some reading, could I use the One X Att all-in-one kit 3.0.1 to obtain SuperCID as well S-Off?
I tried another apparently popular program yesterday but it didn't work, as my CID is still Roger001.
Thanks!
Sent from my One X using xda app-developers app
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Yes!
timmaaa said:
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Spoke too soon.. :S
asarrecchia said:
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Click to expand...
Click to collapse
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
asarrecchia said:
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
Click to expand...
Click to collapse
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
timmaaa said:
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps from the link you gave me, under the RUU section, as there was a guide on how to install an RUU for Rogers HTC One X.
It said to relock the phone, so, I did.
ARWizard was part of the guide.
The weird thing is, I didn't flash CM, I flashed the Rogers RUU, so, I'm not even sure how CM10 is even on my phone.
I can get to the Bootloader but I can't launch TWERP and my windows PC now doesn't recognize my phone, it says installing drivers but never does. I had HTC Sync installed in hopes that it would help, it didn't.
Is my only option to do a Factory Reset in Hboot? I've read ill lose all my info on the SD card.
Thanks
Which RUU did you run? Something has gone wrong.
Sent from my Evita
timmaaa said:
Which RUU did you run? Something has gone wrong.
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps in the below thread to help me flash the RUU
http://forum.xda-developers.com/showthread.php?t=1658929&nocache=1
I went to this site to get the Stock image:
http://forum.xda-developers.com/showthread.php?p=37227608
It's 3.17.631.2
OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip
I really do appreciate the help, by the way.
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
timmaaa said:
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
Click to expand...
Click to collapse
I am 2.14 HBOOT and S-off.
The problem is that while my Windows PC recognizes my phone, it doesnt load the drivers and therefore, I cant send any ADB commands.
I am not even able to go into TWERP.
How will I be able to run the AT&T if I cant push any ADB commands from my PC?
You don't need any adb commands to run an RUU, but you do need the pc to recognize the phone. I'd try uninstalling all drivers, then installing them again to see if it helps.
Sent from my Evita
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files, evita ones get the name pj83img.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
If you follow the "or" method for flashing the zip it actually should work. The better correct answer is once s-off to download/install the latest ruu available that you want and ota up from there.
twistedddx said:
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
Click to expand...
Click to collapse
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
timmaaa said:
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
Click to expand...
Click to collapse
Thanks guys.
I'll try uninstalling the phone drivers and reinstall them, hopefully, it'll allow my PC to see my phone.
Worse case scenario, if my computer doesn't load the drivers for my phone, what are my options?
What if I select factory reset from HBOOT?
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Bump
Sent from my One S using XDA Premium 4 mobile app
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
bump
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
evrycard said:
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
Click to expand...
Click to collapse
He probably cannot downgrade from *.17 to *.11.
I don't know what parts of the firmware moonshine needs. But you could try downgrade using a OTA or Nandroid.
Same here
I'm pretty much stuck with a One-S Bootloader unlocked with S-on.
I can't find a way to get S-Off. Just googling and throwing prayers in the sky someone develops a way.
pyrocide said:
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
Click to expand...
Click to collapse
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
havikx said:
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It took me 5 hours total to begin finding all req's and trying the above method, finding it not to work, redoing the RUU *.17 and getting BACK on CM10.2 and having a phone to make calls with. The method above took maybe 20-30 minutes of double checking and making sure i didn't miss something.
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
tivofool said:
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
Click to expand...
Click to collapse
PM'd him for more info. Thanks!
So I was having problems getting s-off as well, eventually I got it done, but it was definitely a big trial and error process.
What I ended up doing was:
1) Get the 3.14.531.11 RUU from http://www.androidruu.com/index.php?developer=Ville (make sure you get the TMOUS one) This link is also provided in the first post in the Android development section
2) I ended up using Moonshine S-Off (http://forum.xda-developers.com/showthread.php?t=2325590) but I needed to use it in conjunction with running it on Ubuntu. Luckily I had a spare hard drive lying around. If you don't, I believe you can run it through the CD as well as long your burn the Ubuntu.iso on a disc. Plug in your phone to the computer and let it do its magic
3) From there, if you wanted to, you can change to SuperCID. Since you have s-off by then, you can change it from the fastboot usb in the bootloader with the line fastboot oem writecid 11111111 (double check, i'm just writing off the top of my head)
4) Then install roms and etc through the usual custom recovery
Note. I tried the Maximus HD, yes it was nice, but it didn't allow me to utilize my phone as a hotspot, so I ended up using the Dark Jelly rom instead. So far it's been very nice. The hotspot works, but the tethering portion is still unavailable. Just my two cents.
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
i can say that this worked for me as well. i didn't relock bootloader before installing the 3.14.531.11 ruu though. still worked for me. also installed moonshine on windows. ( guess i'm lucky )
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
You saved me so much time. Thanks!
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
I do not understand meet all the requirement and I run it step by step and still gets stuck in step 3 moonshine I need urgent help, thanks
pyrocide said:
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Click to expand...
Click to collapse
Test... click here
http://forum.xda-developers.com/showthread.php?t=2569755
[Q]Hboot/Firmware update 2.15 to 2.16 et al.
Sorry wrong thread.
Hi guys I think I know how to do it but any help or advise is always appreciated. This is what I know:
1.- I downloaded RUU from: http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
2.- Phone Information: Android 4.1.1, HTC Sense 4+, Software Version 3.18.502.6 710RD, BaseBand 0.24p.32.09.06_10.130.32.34L Hboot version 2.14.
3.- Phone is not rooted, not boot loader unlocked, supercid'ed or nothing.
So as far as I know I just need to install HTC Sync for dab and fast boot drivers and after that connect phone with debug enabled, run RUU utility and wait for finish update?
Thanks in advance
If you ever want to unlock your bootloader do not take that update, it has patched the latest root exploit. I'd suggest unlocking your bootloader, installing TWRP recovery, installing Superuser or SuperSU to get root, getting s-off, all before considering running the RUU. If you don't do this before taking the update you may never be able to unlock the phone.
Once you've done all that you can leave the bootloader unlocked and still run the RUU. This way you can experience the update but already have the freedom of an unlocked bootloader.
Sent from my Evita
luis4ever said:
So as far as I know I just need to install HTC Sync for dab and fast boot drivers and after that connect phone with debug enabled, run RUU utility and wait for finish update?
Click to expand...
Click to collapse
Just follow the instruction on the following webpage under "Manual system update instructions":
http://www.htc.com/us/support/htc-one-x-att/news/
HTC Sync is required, but fast boot drivers are not required, and I don't believe USB debugging is required either.
Once you run the RUU executable, it will walk you through step-by-step. Also be aware this will wipe the data partition (but not the "virtual SD" partition). So backup your data accordingly. I'd also backup what is on the virtual SD, just to be safe.
As timmaaa mentioned, the new RUU and OTA updates close the existing exploits, so if you have any desire to mod the phone in the future, its highly recommended to SuperCID, unlock bootloader, S-off before running the RUU.
redpoint73 said:
Just follow the instruction on the following webpage under "Manual system update instructions":
http://www.htc.com/us/support/htc-one-x-att/news/
HTC Sync is required, but fast boot drivers are not required, and I don't believe USB debugging is required either.
Once you run the RUU executable, it will walk you through step-by-step. Also be aware this will wipe the data partition (but not the "virtual SD" partition). So backup your data accordingly. I'd also backup what is on the virtual SD, just to be safe.
As timmaaa mentioned, the new RUU and OTA updates close the existing exploits, so if you have any desire to mod the phone in the future, its highly recommended to SuperCID, unlock bootloader, S-off before running the RUU.
Click to expand...
Click to collapse
So, what you both recommend is:
Follow timmaaa thread to get supercid and then unlock boot loader via HTC Dev and after that run rumrunner to get S-OFF?
If that's correct I have a question, can I run a RUU with S-OFF and Supercid? Do I have to relock bootloader in fastboot to run?
luis4ever said:
So, what you both recommend is:
Follow timmaaa thread to get supercid and then unlock boot loader via HTC Dev and after that run rumrunner to get S-OFF?
If that's correct I have a question, can I run a RUU with S-OFF and Supercid? Do I have to relock bootloader in fastboot to run?
Click to expand...
Click to collapse
Yes that's right. You need to use the 3.18 root method to get SuperCID, then you can unlock your bootloader. Once you unlocked your bootloader you can install TWRP recovery which will allow you to install root. Once you have root you can get s-off.
The only way you can safely run an RUU with SuperCID is if you have s-off, if you run an RUU with SuperCID and s-on you'll brick your phone. You don't need to relock the bootloader.
luis4ever said:
So, what you both recommend is:
Follow timmaaa thread to get supercid and then unlock boot loader via HTC Dev and after that run rumrunner to get S-OFF?
Click to expand...
Click to collapse
I clearly stated: "if you have any desire to mod the phone in the future, its highly recommended to SuperCID, unlock bootloader, S-off before running the RUU"
So I'm not sure why you are asking what I recommend.
If you want further clarification: If you ever want to root, or install custom ROMs on the phone, then you should SuperCID, unlock the bootloader, S-off before running the RUU.
If you intend to keep the phone stock, and never root or install custom ROMs, then its okay to run the 5.18 RUU.
luis4ever said:
If that's correct I have a question, can I run a RUU with S-OFF and Supercid? Do I have to relock bootloader in fastboot to run?
Click to expand...
Click to collapse
Yes, you can. And you should be able to do so with the bootloader unlocked.
Also, be aware that running past Jellybean RUUs with SuperCID and S-on will brick the phone. Its not known whether this still holds true for 5.18 RUU, but I'd assume it does, and never run the RUU with SuperCID and S-on. Simply get S-off first.
There isn't a reason not to get s off either. Super easy with rumrunner and from there use fastboot oem writecid
Sent from my One X using Tapatalk