First android phone it's a AT&T One X, i'll be using it on the Bell network. Got a good deal on Kijiji and I didn't ask enough questions apparently, lol.
The phone is clearly not stock, took me several hours to piece that together. I get it, I'm a noob. I can tell it's running Cleanrom 4.5. I want to get it back to something close to stock. I plan to learn all about rooting/roms but I want to do it from a vanilla phone so that I get to actually do it myself.
I googled and found a tutorial (link). I deleted the 'su' file and superuser.apk. I followed the rest of the steps and it didn't seem to do anything, just rebooted back into cleanrom.
I kept googling and now I'm following this guide: http://forum.xda-developers.com/showthread.php?t=1859714
I guess i'm going to flash from an RUU now ? My CID is 11111111, so I've read that means I have superCID and any RUU will work. I want to get to JB eventually, so can I just flash direct to the Europe 3.14 JB from HTCRUU? Or go with one of the ICS versions?
Am I doing this right?
No no no!
Edit: still writing but wanted to say don't flash that ruu
If you want completely stock you need to use fast boot and boot into hboot and run fastboot OEM lock
(You may need to search around to learn how do that)
Then run this ruu. http://beta.androidfilehost.com/?fid=9390077933525139511
Sent from my One X using Tapatalk 2
that is for the wrong phone
only place you should look at is here AT&T, Rogers HTC One X, Telstra One XL
Its good your asking the questions now if you want to go completely stock run an ruu which means relicking the bootloader and running it ill link you to some guides in a sec
---------- Post added at 07:43 AM ---------- Previous post was at 07:43 AM ----------
Oh and like others said don't use that ruu! We have the one XL
cleanrom 4.5 is pretty good and close to stock but adds quick settings, debloated, power menu and some other tweaks. i would keep it how it is and just learn about how custom roms work. you can learn how to use twrp in its current state and maybe learn how to use some root apps.
just so you know your phone is the evita not the endeavoru.
Thanks for the replies.
I haven't tried flashing anything yet so don't worry. I'm taking it slow.
I've already been into fastboot. Figured that out because it was a required step in the guides I said I was trying to use. I have all the drivers installed and I'm able to talk to the phone via fastboot at the comand prompt.
LOL, thanks for letting me know my phone is Evita. I guess I can delete the 600mb RUU I downloaded
I'm a little unclear about HBOOT vs. fastboot. I can get into the bootloader and go to the fastboot USB mode... is this analogous to HBOOT?
So my steps right now are:
1) Download correct RUU, Evita 2.20 ICS - I've also seen people discussing 1.85 vs 2.20, why chose one over another?
2) fastboot oem lock
3) Install RUU while phone is in bootloader mode
That right?
I would strongly suggest to slow down, and learn more about what root is and means, before going back stock. Root is just a change in permissions. You gain absolutely nothing by unrooting, and lose quite a bit. You lose the ability to do all sorts of mods to your phone, flash custom ROMs, use apps that require root like Adaway and Titanium Backup (and many others), remove carrier bloatware, activate tethering, and much more.
People have gone through great pains to find root methods for our device (and other Android devices). Many come on here looking for these root methods, for the awesome benefits that root means. I've seen very few, if any, people before you that have said "crap I accidentally got a rooted device, and don't want root". Think about that one for a while.
Plus, CleanROM 4.5 is already based on a more updated firmware version than any of the official AT&T RUUs. Plus it includes a lot of cool features and optimizations. Again, going from CleanROM to stock is a step backwards, not forwards, and you are gaining nothing, and losing quite a bit. Another thing about CleanROM, is that it is devoid of the AT&T bloatware (and there is a lot). Keep in mind that on the stock AT&T ROM, the bloat is not removable without root, so you are stuck with quite a few crappy apps that you will never use. That alone is a huge reason to have a rooted device. Also bear in mind that stock AT&T does not allow tethering (unless you have a data plan that allows it) and has other stock HTC apps (like FM radio) disabled. These cannot be enabled unless you have root.
Another thing, is that you will not get Jellybean any faster on stock than rooted. While its true that rooted, this phone will not be able to take the OTA when it rolls out (hasn't happened yet). But a stock rooted JB firmware will almost certainly be posted here on XDA, that is safely flashable on a rooted device. This often happens within a couple days of the OTA starting to roll out, if not faster. Sometimes even before the OTA, as sometimes the official RUUs get leaked before the OTA. All it takes is for a dev to get his hands on the files, apply root, and upload it here. Learning how to flash such a file to your device is very simple. Not much more than: download the file to your phone, boot into recovery, and press "install". So yet again, stock gains nothing over being rooted.
While its true that root is not for everyone. But if you've already found this place, and learned what things like RUU, bootloader, and fastboot are, then you probably already know more than most folks do about Android. You may feel in over your head, but it really just takes a few hours of reading to learn the fundamentals. And with that knowledge, you can do so much more with your phone than you can without root.
redpoint73 said:
I would strongly suggest to slow down, and learn more about what root is and means, before going back stock. Root is just a change in permissions. You gain absolutely nothing by unrooting, and lose quite a bit....
Click to expand...
Click to collapse
I appreciate the advice, thanks. To be clear, eventually I will probably bring the device back to where it is now. I've used linux before so I have an understanding of the permissions system and the added benefits of root.
My goal here is to get the phone back to stock so that I can learn the rooting/flashing process from the start, not the end. I understand why that might seem counterintuitive but I'm a very hands on person and I'll learn more of the theory by walking through the process than reading about how somebody else hacked this device to get where it is now.
Sure I'm making extra work for myself but I know what im getting into.
Sent from my HTC One X using xda app-developers app
echoboomer said:
I appreciate the advice, thanks. To be clear, eventually I will probably bring the device back to where it is now. I've used linux before so I have an understanding of the permissions system and the added benefits of root.
My goal here is to get the phone back to stock so that I can learn the rooting/flashing process from the start, not the end. I understand why that might seem counterintuitive but I'm a very hands on person and I'll learn more of the theory by walking through the process than reading about how somebody else hacked this device to get where it is now.
Sure I'm making extra work for myself but I know what im getting into.
Click to expand...
Click to collapse
You should have said so from the start, then. This pretty much negates everything I just typed above.
Its admirable that you want to learn the process from scratch, and its the opposite attitude of most n00bs here.
My advice, as another mentioned above, is stick to XDA, and don't follow instructions from random Googled sites. Most of those sites don't clearly delineate between our phone (Snapdragon S4) and the international (Tegra3) version, and following instructions for the international version is a great way to brick your phone.
Other than that, lock the bootloader, run the RUU, and have fun. Also check your hboot version. If its anything but 1.14, don't run the 2.20 RUU. You will want the 1.73 or 1.85 RUU instead, as the 2.20 RUU will update the hboot to 1.14, which plugs the holes by which boot.img and radios can be flashed from recovery. Unless you want to create ever MORE work for yourself, as the hboot can be downgraded using a Linux computer, lol!
Be sure to check out my index thread, as most anything you will need is here: http://forum.xda-developers.com/showthread.php?t=1671237
Thanks, sounds like I'm on the right track.
Also check back to my OP, I did say that I wanted to learn the whole process but I wanted to do it from stock. sorry you typed all that out but in sure it will help some other noob down the line.
Last thing, 1.85 vs 2.20?
Sent from my HTC One X using xda app-developers app
ChummyDays said:
2.20 has the new hboot, and that means that you have to extract the boot.IMG out of the ROM and flash it through fast boot. With 1.85 you just flash the ROM.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Cool thanks, I found a tutorial last night on how to extract boot.IMG from the ruu exe. I think I'm good to go.
Sent from my HTC One X using xda app-developers app
You might be confused. You shouldn't have to pull a boot.img from an RUU typically, only from a custom ROM zip. And only if you are on boot 1.14.
Sent from my HTC One X using xda app-developers app
Probably confused. Here's what I see in the boot loader.
***
Tampered
Unlocked
Evita PVT Ship S-ON RL
HBOOT-1.09.0000
Radio-0.19as.32.09.09_L
OpenDSP-v28.1.0.32.0504
eMMC-boot
***
Sent from my HTC One X using xda app-developers app
echoboomer said:
HBOOT-1.09.0000
Click to expand...
Click to collapse
This is what you want to see, and why you need to be sure to use the 1.85 RUU.
Related
<Collaboration><Dev><Ideas> HTC Evo 2.3.3 Gingerbread Root Collaboration.
* I love the color orange.HTC Evo 2.3.3 Gingerbread Root Collaboration
The Lowdown on Everything
FASTBOOT
HTC's RUU releases basically run the adb reboot bootloader code, reconnect to the phone, verify the version and run a series of fastboot commands to install the contents of the PC36IMG (detailed below). In the same way it may be possible to run fastboot commands from command prompt with the SDK installed if you can time it just right in the flashing process, or not. The bootloader can be quite picky when it comes to letting anyone or anything flash anything lower than the version on the phone, or unsigned.
Click to expand...
Click to collapse
PC36IMG
The PC36IMG is what is flashed in the bootloader. The contents of the zip include the radio, system, and more. As long as S-ON is present the bootloader won't flash any PC36IMG that isn't signed by HTC themeselves, however with S-OFF you can flash custom PC36IMGs as well as downgrade, because the bootloader doesn't check the firmware version to see if it's newer or not. If someone was however to be a sneaky awesome ninja and steal HTC's secret sauce then we could simply sign any PC36IMG we wanted to and fake a newer version in the android info txt.
Click to expand...
Click to collapse
RECOVERY
From my understanding the stock recovery references alot with the bootloader to check for most of the same checks it looks for in the PC36IMG, but in the update.zip HTC includes for updates. The stock recovery won't flash anything but signed HTC update.zips either, which again you need the special sauce to sign. Custom recoveries like Amon RA or Clockwork remove the security and don't reference with the bootloader (since your phone has to be S-OFF anyways to flash a custom recovery.) A custom recovery is the key in flashing customs roms and kernels, if you can achieve it with the security on (S-ON) the you won't even have to worry about achieving S-OFF. However, that's near impossible due to the security in the bootloader HTC implements with updates. Which is why the bootloader has to be cracked to install anything.
Click to expand...
Click to collapse
RUU
The RUU is an official tool HTC puts out so people can reflash there phone with a stock firmware just like if it is brand new and your turning it on for the first time. The files included inside of the RUU frontend include the PC36IMG which is essentially what is flashed in the process, but in a fancy way I guess you could put it. The same security applies to the RUU, you can't downgrade versions without S-OFF because the bootloader still checks the version on the phone currently to see if it can flash the PC36IMG or not (when security is on [S-ON] )
Click to expand...
Click to collapse
APKS
I'm sure alot of you know of applications such as Visionary or Z4Root, they both use common exploits to root your phone in a simple application, first temp root then permanent root. They push the approiate resources, Superuser, su, busybox, set the permissions for everything to run, and clean up everything in the blink of an eye thanks to simple scripts. The same thing is still quite possible with any exploit, the exploit just has to be found in the software. You find the exploit you gain root. You have root you can do almost anything to your phone, but S-OFF still plays a role in everything with what you can and cannot flash. Sigh. I know right..
Click to expand...
Click to collapse
Our Mission
The whole purpose of this thread is to collaborate on possible ways to obtain S-OFF and/or root on 2.3.3, either update. We are community, thus we must act like one, and not bash each other for trying. If you have a truthful idea or any questions feel free to post them. You never know, you could very well help with rooting the latest update. This has gone on far to long it's been almost 2 months and no root. This is our time to free each other from the chains of security because we all like to be dangerous sometimes.
Click to expand...
Click to collapse
Possible Rooting Ideas
What Works What Doesn't
I encourage everyone to try previous rooting methods, and methods to obtain S-OFF and experiment as much as they feel comfortable with, you never know what you might find. We could be overlooking something.
Click to expand...
Click to collapse
There is no right or wrong answer only better ones than others. Please do not bash users, or slander them for there ideas, everyone has a right to post, but please stay on topic. /end
Am I missing something?
Sent from my PC36100 using XDA Premium App
lil_bono said:
Am I missing something?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Just give me a few, I'm still typing.
<done></done>
<words>I'll be back on tomorrow, I'm going to go lay down and talk to my friend. Feel free to comment with any ideas. I, myself, am looking into and working very hard to achieve S-OFF and root for the 2.3.3 update, it will come in time. That's just the key; time.</words>
What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.
ill jsut post a small snippet of thanks for thaking this initiative, i dont know about android os myself one bit, so i can hardly contribute, but would there be a way to "fool" the hboot or Ruu version number ?
either fooling the hboot into thinking the ruu one is trying to flash ( to downgrade of course) is a higher version one, or to somehow change the RUU itself to report a different version number? i realize this may sound incredibly stupid as my programming knowledge is very limited, but jst throwing it out there...
once again, thanks for taking this initiative for the evo 4g community
I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...
This should take off
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671
skatrwannabe3 said:
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671
Click to expand...
Click to collapse
Hey, great idea. Just so you know, there is no "bounty" on rooting the ota. I dont even know where that term came from. I just started a thread to say that I am desperate for root, I will pay for someone to figure it out. I never asked anyone or expected anyone else to throw money in on it too. It has since grown into a 600+ dollar pot, and I think that its a good thing. The people that take the time to root it should get a pat on the back.
On topic: I see a bunch of people saying to downgrade, isnt temp root gonna come before that? Shouldnt temp root be the thing to focus on first?
I'm not much of a programmer but ill brick my phone as many times as needed lol
Sent from my PC36100 using XDA App
github said:
What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.
Click to expand...
Click to collapse
I've personally never been the leader of a rooting or S-OFF project before, but my knowledge of Android on a whole is pretty vast. I do develop roms and kernels as well as themes and apps for Android in general, so I guess I'm pretty qualified?
fldash said:
I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...
Click to expand...
Click to collapse
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.
Who rated the thread bad?
bubby323 said:
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.
Click to expand...
Click to collapse
but does the RUU update the hboot itself?
the point is , older hboots and android software are already rooted, if we can get back to those , the end result is the same, we get root, then upgrade using a stock rooted rom, problem solved
bubby323 said:
What Works What Doesn't
Click to expand...
Click to collapse
My recent failures attempts while on 4.24 S-On:
Amon_Ra Recovery PC36IMG.zip flashed from Hboot
Signed 3.70 PC36IMG.zip flashed from Hboot
Signed 4.24 PC36IMG.zip flashed from Hboot (it loads/updates, but is basically a factory reset)
3.70 RUU exe
UnrEVOked3
some chucklehead
bubby323 said:
Who rated the thread bad?
Click to expand...
Click to collapse
Eh, I put in a 5 star vote to make it up, also to show the uselessness of voting.
Has anyone looked at the contents of a PC36IMG.zip? I am still decompliling one, but its a fun task to decipher all of the code. Another thing I need is for someone to tell me which files I should be looking for as far as HTC signing. What I would like to do is maybe strip it from the stock one, and insert it into a custom image.
Sent from the land of motorcycles!
I bought this phone over eight month ago. I have been patiently waiting for the over-the-air Jellybean update, and it is STILL not here. I understand that it is only a few days away because it was just released for Rogers users in Canada, but I just terminated my account with AT&T. They charge me $120 a month for the lowest amount of minutes with 5gb of data. I bought an unlock code off of eBay for about $1.50 and I have a T-Mobile sim due to come in on Tuesday. During this time of service interruption I plan on rooting my phone to flash custom ROMs. My phone is on firmware version 2.20/4.0.4. I am running Mac OS X. I know there are tons of tutorials on how to do this, but NOTHING is working for me. Would someone mind helping me out here. Useful links, definitions, etc?
-Are you using the right guide ( NOT one X )
-Do you have any experience with flashing etc.?
-What methods have you tried?
-What version is your hboot / os / fw etc.?
IMO, stock ain't that great. But I can understand the hesitation to go down the modding route.
Read some more, clearly post your sw versions and the rom/s you are trying to install with failure symptoms ( after googling ) and people will help you.
Good Luck!
gururug said:
-Are you using the right guide ( NOT one X )
-Do you have any experience with flashing etc.?
-What methods have you tried?
-What version is your hboot / os / fw etc.?
IMO, stock ain't that great. But I can understand the hesitation to go down the modding route.
Read some more, clearly post your sw versions and the rom/s you are trying to install with failure symptoms ( after googling ) and people will help you.
Good Luck!
Click to expand...
Click to collapse
1.) I would love to post a link to the guide I have been using on youtube, but I do not have enough posts to do so yet. I used a guide on youtube that gave a tutorial on Windows, then Linux, then Mac OS X. I was able to successfully root/change my CID to 111111. The guide only went that far, then I tried to unlock the bootloader on htcdev.com, but the tutorial they give was only for Windows, and I am not so savvy on Mac OS X. I gave up and left it at that. This morning I did a factory reset on my phone, so when I use CID getter, it says my CID has been set back to the stock CID, but when I tried to do the same method on Windows, it is telling my that my CID has already been change... Yes it has already been changed, but it has been change BACK too!
2.) No, I have been using iPhones since their initial release date. If it matters, I have successfully jailbroken every iPhone I have owned, and am pretty savvy with this sort of stuff, I just don't know where to take off.
3.) The only method that I have tried, and that I know of is the XFactor exploit. It goes as far as recovering twice, but when it tries to recover the CID, it says it has already been changed. I tried to run the unlock_code.bin or w/e, but it just says "waiting for device."
I am running stock ICS 4.0.4, firmware 2.20 on AT&T. When I boot in to bootloader it says:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19AS.32.09.11_2
eMC-boot
Jun 11, 2012.14:36:28
If you know any other methods of changing my fricken CID, I would be the happiest person EVER.
Alright well I can't help you with the CID part but I can tell you that once you do get root access, dont flash a rom butbinstead downgrade your hboot from 1.14 to 1.09. This can easily be achieved by using the Jewel/Evita tool kit in the Android Devolpement topic. You want to do this because on hboot 1.14 you cannot change/flash the boot partition (also radio partition) when in recovery mode. In 1.09 you can. This makes flashing a hell of alot easier. Good luck!
Sent from my HTC One XL using xda premium
Scozzar said:
I beg to differ. I am running on 1.14 and I have absolutely no problems with flashing roms. I would think it might be riskier to downgrade hboot than to just flash a ROM. Flashing a ROM really isn't all that difficult IF you know what you're doing.
Click to expand...
Click to collapse
I tend to agree. Some say the JET tool (to downgrade hboot) is not that hard. And I haven't done it myself (and don't need to as I'm on 1.09). But my understanding is that you have to soft brick the phone in order to get it into Qualcomm download mode, to do the downgrade.
---------- Post added at 03:32 PM ---------- Previous post was at 03:29 PM ----------
ryangunnip said:
1.) I would love to post a link to the guide I have been using on youtube, but I do not have enough posts to do so yet.
Click to expand...
Click to collapse
I would advise against randomly searching for guides on Youtube or other places, and sticking to the guides here on XDA. At the least, other sources are not well organized, and can get you flashing something meant for the Tegra3 version of the One X, which can get you in a lot of trouble.
Sorry I should have clarified. I was talking about the kernel.
Sent from my HTC One XL using xda premium
I'm running over 2.2 too. The only Rom ove got to work is viper. 3.1.0 is damn good bar some lower battery life.
Install latest twrp, flash boot and clear caches and install zip from recovery.
I suspect you have taken a dodgy path playing with a level lower than you have to, on the bright side, your phone still works and you learnt something!
Sent from my HTC One XL using xda app-developers app
thanks
Hello community!! I have been reading through the site for a couple of days now, and I'm still confused which rooting method to use since the At&t, and Rogers are mixed together. Sometimes the techniques used are interchanged, sometimes not. Well my question, or problem is is that I am trying to root the Rogers HTC OneX, running the latest installed updates, which are;
Android version
4.1.1
HTC Sense version
4+
Software/build numer
3.17.631.2
HTC SDK API level
4.63
Kernel version
3.4.10-g240d4d5
I'm trying to achieve root because I want to remove bloatware from my phone.I do not know how to achieve root to do this, I don't mind temporary root, aslong as it keeps the changes I made during that root session. I've read around, and some of the posts that are relevant to my problem are outdate by almost 7 months, with users claiming they're having problems with the method given, and these links were directed from a page that was only edited a couple days ago, so it's a bit confusing, especially when At&t, and Rogers are always jumbled around interchangeably. Anyways,I'd love up-to-date instructions on how to succesfully root this phone. Do I need to unlock the bootloader first? If I have to unlock the bootloader, fine(I know..HTCDev), would someone also provide me a way to unroot aswell, and lock the bootloader back up for a smooth stock startup, incase I want to sell the phone some day? My goal is to get root, remove bloatware, and be able to restore to stock when needed.
This wonderful community's posts also helped me root my Rogers Samsung Galaxy S3!!!
Sent you a pm a little bit ago good job asking questions.
http://forum.xda-developers.com/showthread.php?p=33189590
Here is the oneclick method.
Now as for your software this could be tricky... This may or may not work cause you have the latest build from htc. The latest exploit developed is for 2.20. I cant think of any issues of trying this. I just simply may not take. Use at your own risk kind of thing though.
Sent from my HOX w/CM10.1
When i first started all this even after reading tones of posts i was so CONFUSED but all well its fine!
The one suggested above me might be confusing for you just use this!
http://forum.xda-developers.com/showthread.php?t=1957193
Go to that site Download the SDK from the site they provide you then
http://forum.xda-developers.com/showthread.php?t=1859478
Go here and follow the How to Unlock the Bootloader (When your on HTC DEV.com skip to number 8 Just go to the SDK folder and press shift + right click in the folder click open Command windows here. and then follow the steps from 8) Make sure you are in Fastboot mood by turning off you phone then when its off hold Power + Volume down until the screen comes up and click bootloader then your good!
subarudroid said:
Sent you a pm a little bit ago good job asking questions.
http://forum.xda-developers.com/showthread.php?p=33189590
Here is the oneclick method.
Now as for your software this could be tricky... This may or may not work cause you have the latest build from htc. The latest exploit developed is for 2.20. I cant think of any issues of trying this. I just simply may not take. Use at your own risk kind of thing though.
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
I tried running that program(TOOL] HTC One X (Evita) All-In-One Toolkit V2.1 [1-22-2013] [PERM), but my CID keeps coming back ROGER001, instead of 11111111, therefore the included exploit does not work, But if I manually unlock it through HTCdev, can I resume the steps through that program? Thanks!!
PS: I found out my hboot version is 1.94.000
I unlocked my bootloader through the HTCdev site successfully. Now i'm stuck on actually granting myself root. I've used a couple of files thrown around here, but nothing seems to work. Even temporary root that keeps changes. Anyone?
Once you are bootloader unlocked. Install twrp I believe you need 2.3.3.1 on your firmware and then flash a superuser zip
Sent from my VENOMized HoxL
rrowe1980 said:
I unlocked my bootloader through the HTCdev site successfully. Now i'm stuck on actually granting myself root. I've used a couple of files thrown around here, but nothing seems to work. Even temporary root that keeps changes. Anyone?
Click to expand...
Click to collapse
On the second Site i sent you scroll down abit and you will see How to install TWRP custom recorvery do that and then you will be good. after that download SuperUser ZIp and install it ( once again scroll down on the page and look how to install a custom ROM) for the Custom ROM part there are better tutorials that you can find on this site but yeah.
subarudroid said:
Sent you a pm a little bit ago good job asking questions.
http://forum.xda-developers.com/showthread.php?p=33189590
Here is the oneclick method.
Click to expand...
Click to collapse
X-Factor exploit is not needed for the Rogers version (or any other carrier aside AT&T). And as the OP found out, don't think it works on his version, anyway.
For all other variants (besides AT&T) just unlock the bootloader via HTCDev.com, install TWRP custom recovery, and flash SU or a rooted ROM.
Good to know. Thanks! I hate att more every day. im moving to canada
Sent from my HOX w/CM10.1
So, I may have unlocked the bootloader for nothing! I also realized my hboot version was 2.14, NOT 1.94 like I thought. Will there be any harm in trying to flash TWRP, and root anyhow? Will this brick my device, or simply not take? If TWRP installs, and I push SU, and then I get undesired glitchy results, can I restore back to stock, or atleast an original Ruu? Thanks
You got is easy! Just flash recovery and superuser and your golden.
Sent from my HOX w/CM10.1
Then you get to enjoy all the sense based jb roms you can find.
Sent from my HTC One XL
954wrecker said:
Then you get to enjoy all the sense based jb roms you can find.
Sent from my HTC One XL
Click to expand...
Click to collapse
Not very many sadly
Better than nothing, better than stock
Sent from my HTC One XL
954wrecker said:
Better than nothing, better than stock
Sent from my HTC One XL
Click to expand...
Click to collapse
You are 100% right !
Hi there i have excatly same phone with excat software versions and everything and like you, i hate to be slave of Rogers and their useless apps all around in myphone. If you could achive the rooting your phone, would you please write the steps so i can fallow them. Your help is greatly appriciated in advance,
Thank you
moonchildproject said:
Hi there i have excatly same phone with excat software versions and everything and like you, i hate to be slave of Rogers and their useless apps all around in myphone. If you could achive the rooting your phone, would you please write the steps so i can fallow them. Your help is greatly appriciated in advance,
Thank you
Click to expand...
Click to collapse
I told him the steps read on page one. I helped him and it was solved.
Hello,
I got the htox first day out was super excited, was happy with stuck for awhile and then rooted and unlocked on 1.82 (one click made it easy) and unlocked on the dev site. I ran for a long time on KingKang ROM 4.1 and just recently started geting bored and wanted to upgrade more. I have been bouncing around on 4.2.2 Roms like liquidsmooth/xylon (Btw thx azn and Rohan), but I am noticing all these different things saying S-OFF required. I have wiped everything off the phone and tried diff kernels but always seem to have more issues then everyone else (Screen on in calls, FC, Random reboots). Thinking I missed something? Do I need to update to S-OFF everything talks about 2.22 and OTA for S-OFF? My bootloader screen is saying EVITA PVT SHIP S-ON RL. sorry if this is poorly put together
Was I supposed to update to 2.20 then push ota and s-off? or is there a way to s-off on older versions. How do I see what version I was on prior to my root I want to make sure it was 1.82.
Don't update if your rooted unless you have s-off
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
Have you attempt s-off yet? Might he a good idea.
Sent from my One X using xda premium
I would not s-off or do anything else to your phone until you have a better handle on what you're doing. It's obvious from that post that you lack a good understanding of these changes you want to make (not surprising since you one-clicked).
S-off is just a security setting, not something you install or update to. It's not dependent on software version. You need to read up on what it means, since it removes almost all restrictions on changes you can make. Good if you know what you're doing, dangerous if you don't.
These random issues you're experiencing seem to occur when running Jelly Bean roms on older firmware. I was on 1.82 and had the same reboot issues. I ran the 3.18 ruu and it cleared things up--but you must be s-off before doing it or you may brick your phone.
What iElvis said.
S-off just means "security off" or that all security checks are bypassed. That is all. Its not going to magically fix any random bugs, in and of itself.
I've also had the phone since release, until very recently have been S-on, and flashed many a custom ROM with none of the issues you describe for the most part (only a few random reboots which were very probably a ROM issue). Its more likely due to kernel mismatches, issues with the ROM itself, or possibly other user error (improper wiping before flashing the ROM).
This is one of those instances, if you don't know what it is, you probably shouldn't be doing it. So at a minimum, do your homework and read up.
I suggest leaving a stock rom with root to do s-off without problems.
iElvis said:
I would not s-off or do anything else to your phone until you have a better handle on what you're doing. It's obvious from that post that you lack a good understanding of these changes you want to make (not surprising since you one-clicked).
S-off is just a security setting, not something you install or update to. It's not dependent on software version. You need to read up on what it means, since it removes almost all restrictions on changes you can make. Good if you know what you're doing, dangerous if you don't.
These random issues you're experiencing seem to occur when running Jelly Bean roms on older firmware. I was on 1.82 and had the same reboot issues. I ran the 3.18 ruu and it cleared things up--but you must be s-off before doing it or you may brick your phone.
Click to expand...
Click to collapse
Do you really notice a difference since 3.18? I mean the 4.2.2 ROMs I been on run pretty good, although not flawless. I been on 1.85 and been wanting to try the latest, just worried about the touchscreen outcome. I know there's a tut on downgrading touchscreen but I always ask myself if its necessary... Don't fix what isn't broken right lol...
But if you genuinely think it cleared up a few things I might give it a go..
Sent from my One X using Tapatalk 2
So I have been rooting for awhile (since my 8525) I just don,'t remember anything to do with the soff. I am no expert was just hoping there was an thread someone could point me to about it' I read the article above but once again it is geared towards 2.20 not 1.82
Sent from my One X using xda app-developers app
Touretts said:
So I have been rooting for awhile (since my 8525) I just don,'t remember anything to do with the soff. I am no expert was just hoping there was an thread someone could point me to about it' I read the article above but once again it is geared towards 2.20 not 1.82
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
S-OFF has nothing to do with software or hboot verison. It's a security flag. S-ON means security checks are done prior to/during RUU and flashing of some things.
S-OFF means no security checks are done, flash whatever you want.
Sometimes just because something is changed and a security check is done, for example, if your CID is different from what the RUU you are running expects it to be, your phone bricks.
For the record, the amount of phones you've rooted has nothing to do with knowledge or experience as most phones are crazy easy to root and technically require no knowledge to do so and it's very possible not to brick while remaining ignorant. Your chances of bricking are much lower if you understand what you are doing and every phone is different any way. so.. yeah.
S-off is specific to Android and specific to HTC devices (and certain ones at that). There are several threads in the this (AT&T One X) forum that discuss what s-off means, and what it enables you to do, so just do a search a read up.
I can see this ending badly.
OK I didn't know it was HTC only. I will read more than ty.
Sent from my One X using xda app-developers app
InflatedTitan said:
Do you really notice a difference since 3.18? I mean the 4.2.2 ROMs I been on run pretty good, although not flawless. I been on 1.85 and been wanting to try the latest, just worried about the touchscreen outcome. I know there's a tut on downgrading touchscreen but I always ask myself if its necessary... Don't fix what isn't broken right lol...
But if you genuinely think it cleared up a few things I might give it a go.
Click to expand...
Click to collapse
It depends on what you mean by "not flawless." Don't do it if you just want to be "smoother." I did it out of frustration with the 10+ random reboots I was getting every day because of the wifi bug. That was cleared up. My phone has been running very smoothly, but if you decide to do it, be sure you understand the touchscreen firmware thing.
S-off in a nutshell allows you to flash kernels via recovery instead of using fast boot. And if your gonna try and get s-off you need to be somewhat familiar with adb. If you don't know what I'm talking about then you probably shouldn't attempt it.
sent from my jellybammed one x
After reading countless threads about RUUing or OTAing to the 3.18 Jellybean software, I think I know what everything means. But just to be safe, I want to confirm some things before I try anything. I have never been on a stock firmware other than when I got my phone, and it came on the 2.20 ICS software.
1. I used the SuperCID method to unlock my bootloader. I've read that having SuperCID will screw up the update to jellybean. But, I've also read that having s-off will bypass the CID check when updating, making the update work normally.
My phone has a CID of 1111111 (SuperCID), and is also s-off. Does this mean if I flash back to a stock ICS rom and OTA up to jellybean, everything will be alright? After all of the info I've sifted through, my personal answer is 'yes, everything will work.'
2. If I do proceed with an update to JB, will I still have S-off and/or a root? I've looked at the facepalm s-off thread under the Original Development section, and see no mention of a compatibility or incompatibility with Jellybean. This is the first HTC device I've ever owned, so I'm not as familiar with s-off as some of you may be. I did find this from searching the s-off thread... http://forum.xda-developers.com/showthread.php?p=38197741
If I recall correctly, I was running Viper XL when I s-off'd. It was a jellybean firmware at that time, probably built from the jellybean stock firmware. My personal answer to the question is 'yes, I will still be s-off, but I still don't know about a root.'
As far as a root goes, I'm at a loss of what to look for. I don't see a thread dedicated to a jellybean root, but then again, I'm not as well rounded with troubleshooting as others.
Sent from my HTC One XL using Tapatalk 2
S-off will stick until you manually undo it. Whether you ruu, flash roms, whatever. Only way to lose s-off is to do fastboot oem setsecurityflag 3. Root is software so it's set within the rom. All the custom roms have root by default. With an unlocked bootloader any rom that doesn't have root can have root by flashing su. Consider root as having administrator on windows. If you don't have windows installed there's no administrative access to have right? Hence it doesn't stick but is built into the roms you flash.
S-off eliminates security checks so you you can ruu, flash anything and there won't be any checks that say hey, this isn't the right device or hey, this bootloader is unlocked, you can't ruu..
Just make sure not to flash anything not intended for the evita.
Hopefully this makes sense.
If you have any other questions, do not hesitate to ask.
Sent from my HTC One X using xda app-developers app
exad said:
S-off will stick until you manually undo it. Whether you ruu, flash roms, whatever. Only way to lose s-off is to do fastboot oem setsecurityflag 3. Root is software so it's set within the rom. All the custom roms have root by default. With an unlocked bootloader any rom that doesn't have root can have root by flashing su. Consider root as having administrator on windows. If you don't have windows installed there's no administrative access to have right? Hence it doesn't stick but is built into the roms you flash.
S-off eliminates security checks so you you can ruu, flash anything and there won't be any checks that say hey, this isn't the right device or hey, this bootloader is unlocked, you can't ruu..
Just make sure not to flash anything not intended for the evita.
Hopefully this makes sense.
If you have any other questions, do not hesitate to ask.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks, this pretty much answered all of my questions so if I just wanted a rooted stock rom, I would just follow the steps in the root guide that involve pushing and installing the su binary, and ignore the extra ones that involve changing the CID?
I can't seem to find any links to stock rooted for ICS (it's a preference to me over JB, sorry ) anymore. My thoughts were to run the 2.20 RUU and root it, which seems like a valid option based on your response
Sent from my HTC One XL using Tapatalk 2
Ics is obsolete. If you really want stock rooted Ics.
You're correct.
Run an ics ruu
Flash twrp, flash su
Sent from my HTC One X using xda app-developers app
tyessen said:
My phone has a CID of 1111111 (SuperCID), and is also s-off. Does this mean if I flash back to a stock ICS rom and OTA up to jellybean, everything will be alright? After all of the info I've sifted through, my personal answer is 'yes, everything will work.'
Click to expand...
Click to collapse
If the goal is JB, then I'd recommend the JB RUU, rather than the OTA. RUU is a much cleaner and problem-free install.
'yes, everything will work' is a bit too presumptive to me. You can never be sure that everything will be okay. Modding your phone always has its risks, even under the safest of circumstances. But S-off will prevent the particular case of a (virtually guaranteed) brick caused by installing the RUU or OTA with SuperCID + S-on.
redpoint73 said:
If the goal is JB, then I'd recommend the JB RUU, rather than the OTA. RUU is a much cleaner and problem-free install.
'yes, everything will work' is a bit too presumptive to me. You can never be sure that everything will be okay. Modding your phone always has its risks, even under the safest of circumstances. But S-off will prevent the particular case of a (virtually guaranteed) brick caused by installing the RUU or OTA with SuperCID + S-on.
Click to expand...
Click to collapse
I didn't mean everything as in it will be right out of the box, no errors or problems by that, sorry. I meant that the flash/RUU would complete successfully and I would be running a stock firmware again.
And like I said, I've never ran the official JB firmware, so I'll give it a try and see how the battery holds out. I know ICS had a much better life than other JB custom roms out there, but then again, custom means extra (most of the time).
So, maybe I'll just head straight for the jellybean RUU instead. My only concern is that the h-boot would update, and that sets off a little flag in my head with s-off problems (even though it was confirmed it would stay in place until I manually went back to s-on).
Sent from my HTC One XL using Tapatalk 2
tyessen said:
I didn't mean everything as in it will be right out of the box, no errors or problems by that, sorry. I meant that the flash/RUU would complete successfully and I would be running a stock firmware again.
Click to expand...
Click to collapse
Again, I would never assume that everything will be "completely successful". Even running the RUU under safest of circumstances has its risks. People have bricked their phones running the RUU with a completely stock device. However, its very unlikely.
S-off removes the particular issue of a near automatic brick if you have SuperCID and S-on. There should be no other particular high risk factors, that are currently known and within your control (which is what I think you are trying to get at). You will most likely be okay. But its impossible to remove all risk. Anything that updates hboot and radio has the risk of bricking the device, if it everything does not go exactly right. But aside from being sure you don't mess with the phone or computer while its flashing, its just an unlikely random event, outside of your control.
tyessen said:
And like I said, I've never ran the official JB firmware, so I'll give it a try and see how the battery holds out. I know ICS had a much better life than other JB custom roms out there, but then again, custom means extra (most of the time).
Click to expand...
Click to collapse
I would not jump to the conclusion that ICS has better battery life JB (custom or otherwise). I'd say that quite a few people have had better battery life on JB. There are lots of variables at play. Simply RUUing to the newer radio might improve your battery life. Or might even make it worse.
Battery life is always better experienced for yourself, rather than taking for granted what you read from others.