(im no expert on anything really :- I dont know anything on roms, adb and whatnot)
I've been reading loadsssss of guides and posts etc. on rooting, and basically what I've gathered for this hboot version 2.00.0002, you first have to downgrade and then use the revolutionary to get S-OFF. So to downgrade you have to use zergrush which is in this thread; http://forum.xda-developers.com/showthread.php?t=1399331
I want to know is this the only way & the best way of downgrading? and if it is, how do I exactly use the misc-version (I understood you need to download this and when I click the link the guy provided to get it, it tells me what it does and it has attachments - misc version 1 and misc version 2 which you can download)
Do I just download one?
And after downloading this and zergrush - do I have to place them in a particular area because when using the cmd prompt/terminal you have to type ;
[adb push zergRush /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/misc_version] As posted by mtothearkus
*so surely when typing these it will locate the downloads that you placed in that area for it to work?
- And also you need a RUU - whatever that is :L
-the link posted in the thread to get the unbranded one doesn't work.
So what do I exactly do......
lets say everything works fine and I downgrade to 0.89something. Do I then go straight to the revolutionary thing, or do I have to unlock my bootloader?
Do I need to unlock bootloader right from the start using HTCdev?
I HAVE NO IDEA!!!!
So if you can help it will be much appreciated.
sorry for this long and confusing message.
As with many others, your problems come from not reading the guide thoroughly.
Step 3 says:
run the Terminal (Windowsbutton + R --> cmd) and change into the folder where the files are (change folder with 'cd')
Click to expand...
Click to collapse
The part that you were looking for is bold and underlined.
Then you go to google.com and look for Desire S RUU, and see what you find. Or try to find a dedicated thread here with all RUUs gathered (which will most likely be in which section? You can probably guess). And if you don't understand, what it is - you go to google.com, write "what is ruu", and read what it is.
Since I did not need to downgrade, I cannot tell you how to do that. I'm sure you'll be fine if you follow the guides here correctly.
But I did s-off my phone, so I can tell you for sure that you don't have to use htcdev in any way. Just ignore it. If you downgraded your bootloader, you can s-off using revolutionary and then install recovery like 4ext touch. And that is all. You can flash roms now. But be sure you always make a backup from recovery before you change anything on your phone (flashing etc.)
Sent by my fingers to your head.
You'll find that most of the links that you require will be in whats referred to as the INDEX and don't worry about needing reassurance or having to ask questions, as you must be confident in what you are doing as the device isn't cheap to replace.
I feel that you've done whats important and have at least attempted to read the guides available.
Best thing to do IMO (although not the easiest) is to downgrade your HBoot, then S-OFF with revolutionary, then flash ENG HBOOT and then happily use whatever custom ROM you want!
i think the best way is downgrid and then s-off and root your device.
Welcome to xda-devs, turkmyster.
IIRC you need the misc-version to 'fool' the RUU into installing a stock ROM with an older, AlphaRev-compatible HBOOT.
For RUUs, look at the thread that lists Desire S/Saga RUUs somewhere in this forum. It's there, and you'll likely find an RUU for your region and device there.
For downgrading your HBOOT, this method by shadi22 worked for me nicely: http://forum.xda-developers.com/showthread.php?t=1443636
And remember, Do not unlock you boot loader using HTC-dev, otherwise the above mentioned method won't work. Have you unlocked the bootloader, then just lock it again using the command: "fastboot oem lock".
Related
Ok, so I can't find a compatible boot.img to flash via cmd in bootloader to restore my 2.3.5 original nandroid backup.
All I want to do is return to stock rom after which I will attempt downgrade and s-off because I'm tired of the restrictions and I couldn't care a less about my warranty etc.. I'll use either zerg rush or taco root depending on my software version which atm I have no idea of obviously..so I know to downgrade it's a different story..
Currently S-ON, HBOOT 2.00.0002 HTC UNLOCKED, REAPER 3.0(CM7) ROM Installed. 4EXT Recovery.
I have downloaded a compatible RUU which in my case is
RUU_Saga_S_HTC_Thailand_2.15.1113.2_Radio_20.4801.30.0822U_3822.10.08.04_M_release_226808_signed.exe
Checked by running fastboot getvar main-version: C:\WINDOWS\system32>fastboot getvar version-main
version-main: 2.15.1113.2 (and) CID HTC__058
So that is equal to what I have now on the phone (I also have another older RUU with hboot 98.00.000 for use with S-OFF'ing later...)
So becaue the RUU version is the same as my original can I just run the INSTALLER and let it do it's thing? And do I need to relock my bootloader first?
I have been reading and searching guides for hours, but nothing is clear to me, my wife is at my throat as well saying I've married my PC *you've probably heard it*
Has anyone done this before?
To save you some unnecessary steps:
1) Change the misc_version (look it up, it's a step in downgrading guide) under your current ROM (I assume you're rooted).
2) Lock the bootloader.
3) Flash the older (0.98 bootloader) RUU.
The correct answer for Jack_R1.
[GUIDE] Official HBOOT 2.00.0002 Downgrade to OLD HBOOT thanks Skanob
Some extra optimizations on the guide that bring it to my short version:
1. If you're using the correct RUU for your region - you can skip GoldCard step.
3,4. You don't have to flash stock rooted ROM if you know that you can reboot to bootloader and run the RUU while in fastboot mode. Your phone might not load the OS after locking the bootloader on non-stock firmware, but it won't matter, since all you need is fastboot.
If you're not familiar enough with what things do - follow the guide exactly, don't take shortcuts.
Now I have:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.04.02.01_M
eMMC-boot
Mar 10 2011, 14:58:38
I still didn't understand how things worked and was up another 4 hours mucking around, in the end after succeeding, I can't believe how easy it was.
I never even knew what zergrush and tacoroot were for exactly or which misc version number i should use.
In the end I went back to stock rom, unlocked again using my original token, flashed recovery and then Superuser. After that I didn't need zergrush etc to gain temp root(obviously), just changed misc version, rebooted, revolutionary to s-off and 'Bob's your Uncle'. Now I guess I should learn about the things I can do with s-off...(apart from not needing to fastboot flash boot.img every rom change)
I will elaborate on the things that confused me for others later, but right now, I'm off to work.
Thanks again Jack,
Now you might discover that unless you made some steps you didn't list, S-OFF won't work for you, and you'll still have to flash boot.img manually. If you didn't relock the bootloader and flash the RUU, that is. But I assume you did, and just skipped it on the list of things.
Zergrush or tacoroot are means to get temporary root - which is no good, since it doesn't stick after reboot, but it allows you this one time to change misc_version to allow downgrade. And any misc_version would do, as long as it's below the one you're flashing for downgrade. On MT4G, we usually set it for 1.00.000, that way you can't go wrong.
Glad you made it.
Embarrassingly, I do have problems still. After relocking and flashing the older RUU(HBOOT 0.98.000) successfully, I used Revolutionary to S-OFF. During the process the software asked me if i wanted to install clockwork Recovery, to which I answered 'no'. After that I tried to manually flash 'ext recovery' which I had before, so then I can flash 'Superuser.zip', but get an error message, I'm not sure why?
So I don't have root.
I'm at work now, when I get home all I can try is flash clockwork and see if that works.
*EDIT* Successfully flashed recovery-clockwork-5.0.2.0-saga.img and then superuser, perhaps the version of 4EXT recovery wasn't compatible or something...!? I can't be sure.
Restored Nandroid of previous Reaper 3.0, all is well.
My device used to be S-OFF hboot 6.98.0002.
but now is S-OFF Hboot 7.00.1002.
look : [HBOOT] | 29-05-2012 | 7.00.1002 | Reengineered 2.00.002
kyeeliu said:
My device used to be S-OFF hboot 6.98.0002.
but now is S-OFF Hboot 7.00.1002.
look : [HBOOT] | 29-05-2012 | 7.00.1002 | Reengineered 2.00.002
Click to expand...
Click to collapse
Thanks for the lead kyeeliu, but I have little idea what that can provide, I heard upgrading HBOOT can S-ON your phone again as well. Although I'll have a read and try to garner what I can...
My phone upgraded, but the S-OFF.
Because our mobile phone software unlock.If you use the official RUU upgrade will become S-ON.
We use modified HBOOT, there is no problem.
I currently use, and indeed as vampire36 said, the flash ROM no problem.
My Experience with S-OFF
First of all I want to thank Jack_R1 for his input and wisdom, even though I didn't really understand some things he mentioned, it all made sense in the end) as well as kyeeliu for his comments.
At first I didn't really trust many guides enough to follow possibly bricking my phone. I see too many people[READ:Beginners] with opinions and problems because some guides are not explained from a beginner point of view often offering instructions but little in the way of explanations for steps...., but in all fairness, this is also due to inexperience, or the users own failure to to make sure they followed everything correctly. Such is life...All in all happy to HAVE Guides, we can't really complain, just feel lucky ppl take time to write. And writing in DEPTH is bloody tiring when you hate typing as I do...
I believe NOONE should be attempting, however, to mess with their phone's inner workings until they've tried their best to assimilate all the information they can[ie:SEARCH]. I know it's time consuming and frustrating sometimes, but that onus is on you when you chose to 'take the plunge' so to speak..
I read for so many hours, wading through a disorganised sea of excited opinions READ:misinformation, good advice and hidden gems, but I was unable to discern what was best simply because I only had opinions and a sense of logic to dissasemble everything. In the end I followed a guide HERE by Skanob, it worked A-OK!
So this this is my Story of how I S-OFFED my Phone. By NO means extraordinary, :laugh:
Desire S - S-ON - HBOOT 2.00.0002 - CM7 ROM[Reaper 3.0]
*Note: I nandroid restored my original rooted rom first*
First of all the RUU. Noobspeak: It's just a version of your phones operating system in installer format, just like Windows XP is different[read:updated] to Windows 7, so is 1 RUU from another. Some are branded (have the carrier's logo) some are not (unbranded) Mine in particular was unbranded.
First you need to find out YOUR phones RUU, so to do this reboot your phone into Bootloader - Fastboot and then open command prompt on your PC and navigate to where you have adb and fastboot files located (I have copies of these files in windows\system32\ folder. When there type C:\WINDOWS\system32>fastboot getvar all. In this list of information look for these:
INFOversion-main: '2.15.1113.2' (and) INFOcidnum: 'HTC__053'
version-main is your phones current operating system version CID is your particular phones region(eg: HTC__058 = Thailand)
So This was my phone's current RUU:
RUU_Saga_S_HTC_Thailand_2.15.1113.2_Radio_20.4801.30.0822U_3822.10.08.04_M_release_226808_signed.exe
My current version has HBOOT 2.00.0002. I will need to downgrade this number to 98.00.000. I can do this by installing an older RUU that has HBOOT (98.00.000) I didn't know WHICH RUU that was so I just looked for an older RUU done by checking my current version_main '2.15.1113.2' and looking for something lower. I found: [RUU_Saga_HTC_Thailand_1.35.1113.2_Radio_20.28d.30.0805U_3805.04.02.01_M_release_183327_signed.exe]
I wasn't sure which HBOOT was inside (silly me) so i ran the installer just letting the first screen open up (which extracts all the files from the RUU to temp) and going NO further.. After that I went to 'Run' and typed in %temp% and looked for a recent folder with a long name which had the contens of the installer extracted. Amongst these files I found 'rom.zip' I opened it and inside could see the HBOOT file version 98.00.000_'other numbers'. This was my ticket :highfive: lol...
Now because my stock ROM was already rooted and I had previously flashed recovery all I needed to do was the -Modify the version of your phone- step in Skanob's Guide: (obviously I downloaded the attached misc_version file and as instructed created a new folder on C: called 'downsaga' and dropped misc_version inside)
Code:
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
This part of the code
Code:
./misc_version -s [COLOR="Blue"]1.27.405.6[/COLOR]
sets your phone to accept any RUU with a higher version than that number. I had no idea which number to put there exactly so I used 1.27.405.6 as well, noting it was lower than the RUU version I was going to install[1.35.1113.2] So it would be accepted.
Later Jack_R1 advised me to put 1.00.000 instead, and as he stated, "you can't go wrong". :good:
After setting the new version, I Re-locked my phone via command again using fastboot oem lock. I do not need root privileges anymore as I have already changed my misc_version [lower version] And the RUU installation needs phone to be relocked again before proceeding.
After that it's simply connect your phone to the PC and run the installer:
[RUU_Saga_HTC_Thailand_1.35.1113.2_Radio_20.28d.30.0805U_3805.04.02.01_M_release_183327_signed.exe]
I now had HBOOT 98.00.000. After that, a trip to http://revolutionary.io/ to S-OFF, and flash recovery file. If you choose during the S-OFF process to not install recovery you can do it manually afterwards as I did(I used recovery-clockwork-5.0.2.0-saga.img, because for some reason I got an error trying to flash 4EXT_Recovery_v2.2.7_RC5 which I previously had) Then I simply dropped Superuser-3.0.7-efghi-signed.zip on my SDCARD and installed via recovery, all done. Nandroid restore of my CM7, and that was it...
I remember many weeks ago just trying to achieve root was bewildering, trying superoneclick and 1 or 2 others methods that also failed me. Only to find all i had to do was flash a recovery file in fastboot, then install superuser. ... all the time I wasted...lolz.. thx to n0elite for that http://forum.xda-developers.com/showthread.php?t=1525100
On a side note: Please think again before reporting an error, and retrace your footsteps first. I have seen people reporting errors in forum such as: can't re-unlock my phone(yes, with the same Unlock_code.bin) simply because they were unwittingly in HBOOT instead of FASTBOOT, etc....
Now I'm well aware I could have done 'this or done 'that' etc differently and saved time etc..blah blah, and opions are welcome. I did not ,however, write this as a step-by-step Guide. Only as my personal experience, and yes, to many seasoned members minds I may have over explained, but this is because your so 733T and obviously I'm a slow learner perhaps, but I was mind-boggled so tried to write this from my own perspective as a 'virgin' flasher.
Peace!
twIIce
ok, THAT I can understand. Thanks a million!!!
yeeeeeeee, I've made it!!!
it was soooo simple! thank you mate!!!
Ok as soon as some one reads the title they would be thinking another thread by a noob. I may be a noobb but after having many android devices and installing many custom ROMs its hard act like a noob. But i am really frustrated with the complications that are involved in getting the S OFF on HTC Sensation.
I have gone through all the possible posts on achieving the S OFF but with no luck at all Now can some one please help me here????
Ok now my phone is running Hboot version 1.18 and i have tried the revolutionary method some 10 times and i also looked in to this tool as well http://forum.xda-developers.com/showthread.php?t=1668276 but still cant get S OFF. I have few questions for which i have searched all over the web only to find different answers.
Do i need both S OFF and Unlock on the phone to install a custom ROM? And also do i need the S OFF first to do the super CID? Because i thought if i can at least have the super CID i can run a different RUU and have ICS. But again failed to achieve CID it says HTC_038 instead of 11111.
I have read in several places that i need the latest 3.32 firmware to install a ICS ROM. So i am yet to figure out how on the earth can i install the 3.32 firmware.
I have unlocked my phone using HTC Dev website and i have also rooted the phone. I have installed the CWM but not able to flash a custom ROM. So should i have first done the S OFF and then unlock it or can i still S Off on the phone with the boot loader unlocked?
So in case if i have to re lock the device then do the S OFF , can some one give a link to the latest RUU?
Or can some one help me find a way to S OFF???? Thanks for any help.
shri080 said:
Ok as soon as some one reads the title they would be thinking another thread by a noob. I may be a noobb but after having many android devices and installing many custom ROMs its hard act like a noob. But i am really frustrated with the complications that are involved in getting the S OFF on HTC Sensation.
I have gone through all the possible posts on achieving the S OFF but with no luck at all Now can some one please help me here????
Ok now my phone is running Hboot version 1.18 and i have tried the revolutionary method some 10 times and i also looked in to this tool as well http://forum.xda-developers.com/showthread.php?t=1668276 but still cant get S OFF. I have few questions for which i have searched all over the web only to find different answers.
Do i need both S OFF and Unlock on the phone to install a custom ROM?
I have read in several places that i need the latest 3.32 firmware to install a ICS ROM. So i am yet to figure out how on the earth can i install the 3.32 firmware.
I have unlocked my phone using HTC Dev website and i have also rooted the phone. I have installed the CWM but not able to flash a custom ROM. So should i have first done the S OFF and then unlock it or can i still S Off the phone with the boot loaded unlocked?
So in case if i have to re lock the device then do the S OFF first can some one give a link to the latest RUU?
Or can some one help me find a way to S OFF???? Thanks for any help.
Click to expand...
Click to collapse
1.SOFF is pretty simple for you ..don't know what actually caused you the problem as you havent mentioned what error happened when trying SOFF process
now when you said you tried revolutionary you might have zerg root failed error
if thats the case
kgs tool would have solved the issue ...but you are saying that failed too (which normally wont happen)
that says that you tried kgs tool with unlocked bootloader and having cwm recovery also root ..to SOFF which wont work
(the alternative to by pass the zerg root error revolutionary has a prerequisite which is to have everything completely stock )
now ...the question comes how to do SOFF then
kgs tool has already given the solution (YOU read all the guides and searched all over the world ..but forgot to read the second post in the kgs tool guide )
as i am a good man and i feel like helping a blind person ...i'll tell you where
in the second post of the thread you've linked
TIPS sub section - 6th point ..please foolw the post there ..to make SOFF work
now regarding the other questions
1.no way you can flash a firmware unless you are SOFF
2.once you got SOFF via revolutionary ..dont even bother about HTC-dev unlock ...as the bootloader provided by revolutionary after SOFF(engineering-bootloader) ..is much much better than the HTC-DEV unlocked bootloader
3.After SOFF best guide for you to flash ICS rom is this (post #1 and post #2)
Thanks a lot for you quick reply. really appreciated !! I am not a complete blind though well i tried restoring the recovery image back to stock then tried the kgs tool but it again failed. The only thing i had not tried was to do the factory reset after restoring the stock recovery. I extracted the stock recovery.img by running the Indian RUU. But i dont know if it makes any difference if i flash the recovery image attached in that post. Let me try that too Thanks again for taking time to reply !!!
shri080 said:
Thanks a lot for you quick reply. really appreciated !! I am not a complete blind though well i tried restoring the recovery image back to stock then tried the kgs tool but it again failed. The only thing i had not tried was to do the factory reset after restoring the stock recovery. I extracted the stock recovery.img by running the Indian RUU. But i dont know if it makes any difference if i flash the recovery image attached in that post. Let me try that too Thanks again for taking time to reply !!!
Click to expand...
Click to collapse
can you please elaborate the error you got when you did SOFF ....screenshot will do too ..if you tell us the exact error you got ..you might get perfect solution
until then it will be shot in the dark
PS: regarding the blind comment ..dont take it seriously ...its meant to be sarcastic thats all
I know what this error is. [ Failed to get root & taco root also fails. Happens on an unlocked bootloader ]
Please come over to the help channel: #helpmenow.
Once there, ping me by typing my name.
ok i also had some issues to S-OFF my sensation with HBoot 1.18
now here what i did to successfully S-OFF the device and root it..
1st Download Tacoroot (as you already told that revolutionary isnt working for you) :- http://db.tt/PxZRO0d1
then switch on your sensation and connect your HTC to your PC in Charger Mode and Enable USB Debugging.. [ Remember to install HTC Drivers ]
now open adb and type the commands [ dont forget to keep the tacoroot.bin file on your adb folder ]
Code:
adb push tacoroot.bin /data/local
adb shell chmod 755 /data/local/tacoroot.bin
adb shell /data/local/tacoroot.bin --setup
The phone will reboot to recovery.
Press Volume Up, Volume Down and Power.
Reboot.
Press the Power button once if the screen remains blank (dark).
Wait for boot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin --root
The phone will reboot.
Run Revolutionary and now try to S-OFF your mobile using revolutionary.
Once Revolutionary is successful, reboot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin –undo
now once its done install recovery and continue flashing your rom.
This tut i found on XDA by a member .. Thanks to him :
Code:
http://forum.xda-developers.com/showpost.php?p=23482010&postcount=29
[SOLVED]
deepsaha007 said:
ok i also had some issues to S-OFF my sensation with HBoot 1.18
now here what i did to successfully S-OFF the device and root it..
1st Download Tacoroot (as you already told that revolutionary isnt working for you) :- http://db.tt/PxZRO0d1
then switch on your sensation and connect your HTC to your PC in Charger Mode and Enable USB Debugging.. [ Remember to install HTC Drivers ]
now open adb and type the commands [ dont forget to keep the tacoroot.bin file on your adb folder ]
Code:
adb push tacoroot.bin /data/local
adb shell chmod 755 /data/local/tacoroot.bin
adb shell /data/local/tacoroot.bin --setup
The phone will reboot to recovery.
Press Volume Up, Volume Down and Power.
Reboot.
Press the Power button once if the screen remains blank (dark).
Wait for boot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin --root
The phone will reboot.
Run Revolutionary and now try to S-OFF your mobile using revolutionary.
Once Revolutionary is successful, reboot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin –undo
now once its done install recovery and continue flashing your rom.
This tut i found on XDA by a member .. Thanks to him :
Code:
http://forum.xda-developers.com/showpost.php?p=23482010&postcount=29
Click to expand...
Click to collapse
Tacoroot did not work for him. It was something else.
In some phones, tacoroot causes the phone to get stuck on the HTC screen.
The phone can't be temp rooted that way.
This happens usually only in HTC dev unlocked phones that had custom recovery installed and then flashed stock recovery before tacoroot.
Sent from my HTC Sensation XE with beats audio
PS: anyone who wants to know how to make this work -
Root your phone by installing su.
Modify local.prop to get root prompt by default in shell.
ohh i see , i didn't have that problem but once i was stuck in boot loop after i upgraded the firmware to install ics but it was fixed after i installed a custom ICS rom..
This is for International hTC One XL/Evita - Hboot 2.14 & firmware 3.17 (Orange UK)
If you own AT&T One X please look elsewhere, this guide is not for your phone
There is an abundance of information scattered in these forums and not all root methods/exploits work universally due to variation in firmware builds and Hboots.
I had to read a lot of threads to figure out how to S-off my Orange UK One XL with Hboot 2.14 and firmware build 3.17.
I was only interested in attaining S-off but had to start with HTCDev bootloader unlocking which I didn't really want to do but none of the known root exploits worked on my firmware.
I am sharing this hoping it would help others avoid taking pills for headaches when pursuing this noble quest
AIM:
Provide a short guide to others with similar device and configuration on where to start and simple clear steps to follow with needed links.
PREREQUISITES:
1. latest htc drivers for your Windows PC/laptop if you have one of those. Check here.
2. a working adb environment preferably from latest Android SDK, if you don't have this already set up please check here.
3. "USB debugging" must be checked under Phone settings>Developer options
4. an original htc USB cable is strongly recommended.
5. phone charged at above 50%
6. basic knowledge of using command prompt (cmd) in Windows and adb commands.
STEPS:
So in my case the steps were:
[1] Unlock bootloader through htcdev.com
[2] Flash/install TWRP recovery
This is done manually. All-In-One Toolkit didn't work for me BTW.
1. download latest TWRP recovery for One XL/Evita from here
2. you can rename file for easier command prompt typing later, like TWRP5.img
3. place file recovery file in your adb/fastboot folder
4. connect phone in fastboot mode to PC, make sure it displays fastboot USB on phone before you proceed.
5. start command prompt from within fastboot folder by right clicking inside folder and choosing "open prompt here", type following command:
Code:
C:\yourFastbootFolder> fastboot flash recovery TWRP5.img
Not a bad idea to test your recovery by making a nandroid backup before proceeding to next step.
[3] Flash a custom rom (root)
All custom roms are rooted by definition. If you chose e.g. ViperXL like I did remember to flash boot.img extracted form same rom zip afterwards, otherwise bootloop!
You can of course flash a SuperSU zip instead to gain root but I don't see the point.
[4] SuperCID
This is the simplest way that I found accidentally during my endless searches, all credit goes to @beaups for this one and @Austempest for sharing :good:
1. connect phone to PC in Android mode (mode where you can use phone)
2. Run the following command from command prompt (CMD):
Code:
C:\>adb shell
To enter adb shell, then enter following commands after each other:
Code:
# su
# echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
3. Reboot to bootloader and hopefully you'll see 11111111 as your CID ...... yes
[5] S-Off
Now that your are rooted with SuperCID you can just follow @beaups simple steps for S-Off found here Facepalm S-Off
That is it.... you broke your shackles :laugh:
I am not a dev and for sure not taking credit for other people's work, merely giving back and hoping this assists clarify stuff and save some time.
Cheers!
the one clicks would not work for you because you dont have an att one x so the supercid exploit doesnt work on our phones
all phones go through htcdev.com to unlock, att phones just need supercid first.
you should make a not in your guide that this guide wont work for at&t phones.
exad said:
the one clicks would not work for you because you dont have an att one x so the supercid exploit doesnt work on our phones
all phones go through htcdev.com to unlock, att phones just need supercid first.
you should make a note in your guide that this guide wont work for at&t phones.
Click to expand...
Click to collapse
Thanks for this important reminder, note added in red on top!
You mentioned one click is only for AT&T phones, I guess you mean All-In-One Toolkit by hason2000, you see even in the tool's thread it's not stated explicitly that tool works only for AT&T, while the respective threads for these exploit state that it's for AT&T One X not negating other international versions!
Most guides/tools are for North America and some Australia but very few for Europe which BTW only recently came on board with 4G/LTE.
So figuring out, especially for noobs, what is what with all these international variations for one device and huge amount of information, while searching doesn't always provide an answer is a tedious task and can end up miserably :crying:
I hope it's in order to add some info for European Evitas
guys kindly don't quote whole post(s), thanks
Only AT&T Phones are different in the case of unlocking/rooting because they can't use HTCDEV. Every other onexl is the same for unlocking/rooting.
Great guide, thanks you! it worked !
Now i'm stuck at the next step. ha :crying:
i cant get root, because my touchscreen not functional after flashed a custom rom. i had success until step 3, i cant proceed to step 4 as i cant use my touches when the rom loaded. i didnt have any back up. i already searched around to dgrade my touchscreen firmware, but it needs root. im stuck here, i can flash custom cwm recovery, install custom rom but cant touch screen. the default cm10.1 dont have android debugging enabled by default, i cant enable it cos i cant touch the screen. if i restore to stock ruu, i can touch screen n all works, but i had a problem sync google contacts.
The reason im getting my hands on custom rom is bcos my stock XL(Asian version) will neve sync google contacts properly, i tried to flash JB stock RUU, but its same. then, i started to tamper my fon with unlocking bootloader via htcdev, flash cwm(twrp mess on my sdcard storage). i had experience on older htc devices but its my 1st time on the htc one series. right now, im on evita s-on, unlocked bootloader, hboot 2.14, cwm recovery(twrp mess on my sdcard storage), not-super CID. I 'm left with a non-touchable cm10.1, i can flash any rom that supports s-on. tried to relock bootloader but i cant flash stock ICS ruu.flashing stock JB RUU is ok. my target now is to s-off n superCID.
i can :
flash RUU 3.17, running a stock RUU 3.17.
unlock bootloader
flash custom recovery(twrp mess with my internal storage)
i cant :
root my device on stock rom
touchscreen wont work on custom rom
any help will b greatly appreciated.
Do not make multiple posts about the same thing. It is strictly against XDA rules.
sorry, may i know how to delete it? i click on edit/delete but cant see any options to delete my post.
You cannot
Sent from my One X using xda app-developers app
sir how to back or normal cid help me
sir how to back or normal cid help me i have a one x its allredy super cid how get back normal cid
Fastboot oem writecid whateveryourcidwas
This will only work once with s-on after supercid but will work as many times as you want if s-off.
Sent from my One X using xda app-developers app
ignore this post. found a relevant thread
How to upgrade bootloader to 2.14
So what if you are not on HBoot 2.14?
EDIT:
Warning: It is not a good idea to upgrade only the bootloader if you intend to flash the latest CM10 builds! Avoiding RUU and unlocking again out of laziness will probably get you in trouble afterwards. RUU is definitely the safer way. You'll find a good collection of ROMs here
http://forum.xda-developers.com/showthread.php?t=2119610
and the tutorial for upgrading RUU on a previously modded phone here
http://forum.xda-developers.com/showthread.php?p=26260005
I found these threads which helped me SuperCID, S-Off and finally upgrade the HBoot of my already rooted evita.
First you need the superCID from this post:
http://forum.xda-developers.com/showthread.php?p=42351491
Next Step S-Off:
http://forum.xda-developers.com/showthread.php?t=2155069
Then RegawMOD the appropriate bootloader from this thread and flash:
http://forum.xda-developers.com/showthread.php?t=1786498
The procedure was easy once I had found the appropriate threads on XDA
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
Sent from my HTC One XL using xda app-developers app
New CM10 and derivates require HBoot 2.14
exad said:
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
Click to expand...
Click to collapse
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
ernstlustig said:
exad said:
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
Click to expand...
Click to collapse
That's exactly why you should not do it that way. You may get issues along the way as a result of the software not properly utilizing your hardware. This is why you're supposed to update hboot. What you did is more like tricking it into thinking you updated the firmware.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
ernstlustig said:
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
Click to expand...
Click to collapse
As exad said, CM 10 didnt want you to update just the hboot it wanted you to flash 3.18 RUU or equal to get updated firmware.
The requirement to install 3.18 RUU is listed as a requirement for CM. The hboot is what is checked but things like radio, adsp and wcnss are what actually needed to be updated, which you have not updated.
All you have successfully done is beaten the basic check for if you flashed the 3.18 RUU without actually doing what you were told to do.
How did you get s-off? i have a rogers version
salt204 said:
How did you get s-off? i have a rogers version
Click to expand...
Click to collapse
Links to XDA threads updated. (Sorry.) Please look again.
Has anyone tried successfully to write SuperCID into hboot 2.15 S-On devices?
as the instructions is for hboot 2.14, and I would like to S-Off the device with hboot 2.15 and it is S-On.
I have tried the hex with adb method, but it doesn't work.
I hope I'm in the right place. I can't connect at all to the PC since I flashed the AOKP_jb_mr1_build4 ROM. The PC says can't find device driver.
Also, I would love to update to newer builds, requiring a newer hboot version I gather, but not quite sure as to how to go about that, and deal with s-on. I only want to do what has to be done to get the latest AOKP ROM builds. Any advice would be greatly appreciated...
I am using HTC one x, Evita, rooted, (not sure about supercid, I think so), s-on, hboot 1.14, and trwp 2.6+.
Even though I've had my phone a year, I'm still quite the noob when it comes to all this. Heavy forum reading...re-reading. I'm looking for any definitive help on getting me set up on the last steps here.
Sent from my One X using xda app-developers app
Newer builds do require an upgrade but it's not just the hboot that needs upgrading, it's the firmware as a whole which needs upgrading. The firmware does contain the hboot as a component and it is also usually identified by the hboot version number that it contains, I guess that's why there's a common misconception that it's just the hboot you need to upgrade.
Anyway, what you need to do is run the 3.18 RUU which will give you the 2.14 firmware modules. In order to run the RUU you'll first need s-off otherwise you'll end up with a brick. In order to get s-off you need to be sure you have SuperCID, without SuperCID the s-off process won't work. I know this all seems like a lot of work but it's a pretty easy process. Not having s-off at this stage is a stupid hindrance, without it you basically cannot flash any current ROM because they all require some kind of update (which itself requires s-off).
PS. You're not quite in the right place, in future please post questions in the Q&A section. I'll ask for this thread to be moved there.
Sent from my Evita
timmaaa said:
PS. You're not quite in the right place, in future please post questions in the Q&A section. I'll ask for this thread to be moved there.
Sent from my Evita
Click to expand...
Click to collapse
Done and title changed:good:
Thanks. Trying to find noob-proof instructions to accomplish all you mentioned. But I do appreciate being pointed in the right direction. Its good to know definitively what I need to do, now just gotta get down the how lol...
Sent from my One X using xda app-developers app
Ok, I'll make it a bit easier on you. The easiest way for you to get it done will be to follow these steps:
Flash a Sense 4 Android 4.1 ROM with root. It cannot be Sense 5 Android 4.2 though. You'll find plenty in our development section.
Determine whether you have SuperCID or not. Boot into bootloader and connect to your PC then issue this fastboot command:
Code:
fastboot oem readcid
If it shows up as 11111111 or 22222222 you have SuperCID and can continue to the s-off step. If it shows up as anything else you don't have SuperCID, in that case you van use this method to obtain SuperCID:
http://forum.xda-developers.com/showthread.php?t=2212737
Once you have SuperCID you can get s-off by following this guide:
http://forum.xda-developers.com/showthread.php?t=2155071
So now you should have s-off, which means you can run the 3.18 RUU. You'll find it here:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
All you need to do is connect your phone to your PC, run the RUU exe program and follow a few prompts. Make sure no other programs are running and make sure screen saver/hibernation is turned off. Also make sure HTC Sync is uninstalled (leave divers installed) because it gets in the way.
When the RUU is complete you will have a stock ROM and stock recovery on your phone (your bootloader will remain unlocked and you'll still have s-off though) so you'll need to flash TWRP recovery again. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can flash any aosp ROM you want.
Sent from my Evita
Thanks...
Thanks for all the help. I was SuperCID, I achieved S-Off, i think. It says s-off on bootloader, but when I was entering the final 3 commands, the second one said error, I resubmitted it, and it went thru. Now it says S-Off. So is everything cool there?
I am a little concerned as to how terrible sounding running the RUU 3.18 can be. Am I cool to go now with no problems forseen?
Thanks for your responses btw. Very Helpful
Also, do I connect to PC in bootloader, or up and running rom, while running RUU?
If you are s-off running the ruu is entirely safe
Sent from my VENOMized HoxL
Everything went smooth today. I am running s-off, and hboot 2.14. Instructions worked perfectly. Thanks to everyone that helped me.
Sent from my One X using xda app-developers app
:thumbup:
Sent from my Evita
I would like to put my phone back to stock, I currently have Cyanogenmod on there, rooted, unlocked bootloader and a custom recovery. I am wanting to sell my phone so I need to know how to put it back to stock. Any help is appreciated
I am s-on
unlocked bootloader
HBOOT 2.00.0002
4ext recovery
deadphone99 said:
I would like to put my phone back to stock, I currently have Cyanogenmod on there, rooted, unlocked bootloader and a custom recovery. I am wanting to sell my phone so I need to know how to put it back to stock. Any help is appreciated
I am s-on
unlocked bootloader
HBOOT 2.00.0002
4ext recovery
Click to expand...
Click to collapse
Basically, just follow a 2.00.002 to 0.98.00000 downgrade guide involving using htcdev, such as this one, starting from the step where you push misc_version onto the device (you're already rooted and unlocked).
Obviously, if you don't want to S-OFF, you don't have to run Revolutionary.
You will need to use a RUU, you will need to re-lock your bootloader immediately before the RUU step. If you're not sure about how to choose a RUU, please see the relevant section of my guide in my signature.
If you want to sell the device as a 2.00.002 (you meanie! xD) then you can apply a newer RUU than for 0.98.0000, just don't put on ICS D:
paulie-uk said:
Basically, just follow a 2.00.002 to 0.98.00000 downgrade guide involving using htcdev, such as this one, starting from the step where you push misc_version onto the device (you're already rooted and unlocked).
Obviously, if you don't want to S-OFF, you don't have to run Revolutionary.
You will need to use a RUU, you will need to re-lock your bootloader immediately before the RUU step. If you're not sure about how to choose a RUU, please see the relevant section of my guide in my signature.
If you want to sell the device as a 2.00.002 (you meanie! xD) then you can apply a newer RUU than for 0.98.0000, just don't put on ICS D:
Click to expand...
Click to collapse
I get permission denied when trying to change the misc_version number, any ideas?
EDIT: I just sorted it
deadphone99 said:
I get permission denied when trying to change the misc_version number, any ideas?
Click to expand...
Click to collapse
You need to run misc_version as root, use su to gain root in your terminal for when you issue the command. You may need to interact with a permission request on the phone screen.
If you have an old adb on your computer and your rom is android 4.x, you might need to get a newer adb for it to work properly (some security stuff was changed).