Related
UPDATE: With all of the newer rooting and S-Off methods, and new hardware and firmware revisions, this thread may or may not help with your specific case if trying to unroot and go back to unrooted stock. I originally wrote this based of of the very first root methods known for the Launch EVO. There is a good chance that this method will still work, but there could definitely be something unaccounted for in your own specific case, so tread with caution. It is very doubtful that anything in this tutorial will result in your EVO becoming a fancy-schmancy paperweight, but if something goes afoul, you could have a nice headache to deal with...
Ok guys. There is a lot of partial and mis-information floating around out there about how to UN ROOT if you have to send your phone back for replacement, or you want the official unrooted OTA 2.2.
OLD NEWS!!!---> NEWER METHODS AVAILABLE TO ACTUALLY FIX PRI DOWNGRADE> SEARCH!!!! EDIT your PRI to show 1.40, thanks to sturmen for the pointer, and Calkulin for the method: http://forum.xda-developers.com/showpost.php?p=7267559&postcount=66
This assumes you are full root, S-Off. Note, this is not tested with simple root but should work (EDIT, Simple Root is basically Toastcfh's method, so you simple root users should be set), only with Toastchf's root method and nand unlock.
After reading every thread on the forum here, I think I finally found a fool proof way to do it. All the info was out there, but in several places and each one was missing something.
1) Before you start clicking and flashing and running RUUs, Check your HBoot build. You need to have the 0.76.2000 from Toastcfh's method #2. If you have 0.79.0000 (whatever) go to step 2 below. If you're getting Bootloader errors when running an RUU, I can almost guarantee that you don't have the correct HBOOT. If you somehow still have 0.76.2000 from previous modding, proceed to step 3.
2) Toast's Nand Unlock method. Found here: http://forum.xda-developers.com/showthread.php?t=701835
EDIT: The more I think about it, I think you can just run Simple Root to re-attain the .76 HBOOT and engineering build. It would eliminate the need for any adb, and SHOULD produce the same results. Just run the RUU after you run and complete simple root. See notes in BLUE below too!
THIS STEP IS 100% NECESSARY IF YOU HAVE THE .79 HBOOT version!!!...Do step #2 in Toast's thread, just like you did when you originally unlocked NAND (OR YOU SHOULD BE ABLE TO JUST RUN SIMPLE ROOT AGAIN...UNconfirmed, but should work methinks...). Not 100% sure which steps are necessary, but I do know you need to do steps #1 (Well, #1 is Nandroid Backup, so proceed at own risk if you skip) and #2 again. Make sure after you flash the Flash_Image, and the mtd-eng through adb, that you then load the PC36IMG.zip (Engineering Build), onto the root of your SD card, and boot into HBOOT, and let it install (just like you did when rooting). I didn't bother to flash the Recovery image at the end of step 3, but I don't think it would hurt if you're nervous about losing a custom recovery image in case this method for some reason does not work. It has come to my attention that flashing the engineering build (the PC36IMG from Toast's thread)through fastboot, might be as crucial as simply having the .76 HBOOT version. It at least is a surefire way to make sure you can run an RUU on top of it. There are probably other builds/roms that will work and allow you to run the RUU, but this one is confirmed, so don't skip that step!
3) If you have the 0.76.2000 HBOOT (can be checked by powering down, and booting by holding VOL down and Power), then you can go ahead and boot into the rom, and proceed with downloading the RUUs found here: http://shipped-roms.com/shipped/Supersonic/
Go ahead and download the first one (at least). I think the others are optional to "upgrade" but why should we care. We just want to go back to unrooted stock.
4) Make sure you have the latest version of HTC Sync installed, found here: http://www.htc.com/uk/SupportViewNews.aspx?dl_id=933&news_id=627
Install, and let it do it's thing. Will probably have to restart your PC when complete. Not even 100% sure this is necessary, but it won't hurt. It's basically for the HTC drivers from what I understand.
5) Run the RUU from your pc while your evo is in the phone loaded state of the Rom, (not the bootloader) with the phone connected through USB and have HTC sync selected. Even if it doesn't connect to HTC sync on your PC, you should be ok.
If you get a USB error after the screen goes black with the HTC LOGO, don't touch the phone. Exit the RUU via the EXIT button when given the option.
6) Run the RUU again and see what happens. The Error could happen 1 more time, but just exit again, and run RUU one last time.
7) Thank everyone here at XDA that our EVOs are so badass...I'm certinly not a dev, but these devs work hard for us to have the baddest ass phone there is right now.
Any problems, let me know. I assume your errors are the same ones I was getting, and it's all because of the wrong HBOOT.
I really take no credit for this, as I'm just compiling information in a tut....
Thanks op.
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
arozer said:
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
Click to expand...
Click to collapse
You might be correct, but I couldn't get the FROYO OTA to show up in any of the roms I was using.
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
sturmen said:
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
Click to expand...
Click to collapse
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
EDIT: Yess! See below and in OP!
Bang3r said:
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
Click to expand...
Click to collapse
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
sturmen said:
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
Click to expand...
Click to collapse
That would be cool, but I'm not too worried about that part. Phone is going back tomorrow!
Well, worry even less! Special thanks to Calkulin!
thankssssss
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
I'm getting error 155 running Ava Froyo and trying to go back.
blix1337 said:
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
Click to expand...
Click to collapse
Yes, you are correct, but so am I. This is exactly what step 2 in the OP does (which is a link to Toastcfh's thread about the engineering build).
tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
Ok. RE-read the OP. Everything is there. Check your HBOOT version by booting to the bootloader. If you have .79, you need to re-flash the engineering build before the RUU will work (Step 2 in the OP to get HBOOT to .76). You cannot run the RUU on top of AVA froyo or any froyo, or any rooted custom 2.1 for that matter if you don't have the proper HBOOT (Which I believe you cannot have if you are running any custom rom). Flash to the engineering build, then the RUU.
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
joypunk said:
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
Click to expand...
Click to collapse
Yes you can still REroot VIA those methods. As long as you don't do a FROYO OTA or manually flash the UNROOTED Froyo...there is no ROOT method for FROYO yet.
It returns completely to UNROOTED stock, except for the PRI, which there is a fix for on the 1st page.
And incidentally (and I just figured this out last night) Simple Root is Toast's method, just automated...
EDIT: I think that you could even UNROOT and RUU to 1.3x (whatever it is), then use the ROOTING methods that were in place before the official 1.47 OTA rooting methods. But, I just did simpleroot last night on top of 1.47, and it is freaking SIMPLE....1 click for root...1 click to flash recovery.
tpdtopcop said:
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
Click to expand...
Click to collapse
This is what were trying to show you on Androidcentral as well. Glad you are set!
tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
As long as you have .76 HBOOT flash back to an earlier rom...one that has a 1.32 base. Then use the 1.32 RUU or 1.47 RUU. You should be set. Make sure you have completed step 2 in OP.
Yes. I have .79, thanks!
Sent from my PC36100 using XDA App
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.
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.
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.
I have a one SV on cricket (US)
K2_PLC_CL (s-on) still
Ok so it was all stock from store. Tan I did this in order:
1.) Unlocked bootloader from HTC dev...
2.) (flashed) Installed CMW v6.0.2.8 via ADB
3.) MADE BACKUP with CWM
4.) Rooted by flashing a zip via CMW (worked great)
5.) tried moonshine.io for s-off tried twice. Failed
-program (distiller) closed after saying "moonshining 1...2...3...to 10)
-now on boot it gets to "Htc
I booted into CMW and retored that backup i had before any rooting or s-off etc... but it still hangs :silly:
Should I try the hboot option to restore? (I thought CMW backup was like a complete nand backup. Which should be bullet proof right?)
Thanks for looking guys! I have no communication as of now I just want to make calls at least
This is my first android device and I always like getting to know my devices from the inside, the iphone BS was too much haha. I gues i dont really need s off or super cid if it means no phone. but why not if it works.
Did you have ICS or JB, when you have tried S-off?
Please remember, as long as you are S-on you must flash the boot.img with fastboot commands (also, if you are restoring a backup and you did a full wipe)! If you have a cwm backup, boot.img should be inside of your backup folder.
Did you wipe everything before your restore? Maybe fragments of moonshine still there.
Did you try TWRP recovery?
[HTC oneSV boot hang, FIXED] THANKS!!
LOL I had no idea the boot.img had to to be manually flashed, thank you very much it work s great now!
This time I cleared/wiped data AND cache. it still hanged and wont boot. Than I re tried using CWM again to restore (still hangs). than I flashed boot.img THAT DID THE TRICK after "fastboot reboot".
BTW major fail on my part; I was rooting and moonshining for JB it turns out I have ICS (i forgot to update) now that you mentioned it hehehe
I had 4.0.4 sense 4.1. I think that is why everything went to hell...
Alright Ill try moonshine after the update to JB 4.1.2 if that fails than Ill try the facepalm.
One last question; if i do update to JB 4.1.2 and achieve s-off could I use that CMW backup to always go back to ICS 4.0.4? (just incase I ever wanted to get SUPER CID and get JB 4.2.2) I wonder if super cid works with k2-PLC-cl.... Ill try it when I get find the funds a better phone to risk a brick
-Thank you sir!
Ok, lets bring a bit light into these darkness:
- Facepalm S-Off only works, as long as you did not achieve the JB update!
- You can restore a ics cwm backup, also when you are on JB and S-Off, but
- Restoring ics from a backup is not the same, as you where on ics before the update.
Thats because of the updated hboot (ics-> hboot 1.0; jb-> hboot 2.0). In hboot 2.0 the Supercid/Facepalm exploit is fixed. You can still get Supercid under hboot 2.0, but you must do moonshine S-Off before.
So, at all you must think about, what you want and whats the best way to get, before updating to jb.
If this was to difficult to understand, ask again and i will try my best to explain it for you to understand.
Ok
Hum they creators of these phones really enjoy making puzzles for us don't they...
Alright so my options are:
1.) [stay on ICS]
-get super cid
-facepalm for s-off
(can I still update to JB after this and still have super cid and s-off? But that would install hbot2 wouldnt it? so....)
I think I want method 2↓
2.) [update to JB]
-use moonshine to get s-off
-some how get super cid? (I dont really need super cid but it would be nice to know I have it just in case)
-profit
//edit//(ohh yes, once on JB hboot v2, if i have s off and on hboot2 could I go back to hboot1 along with ICS should i need to)
Any ways thank you again
1. Right, you can update and both will stay.
2. Right, after S-Off you should be able to change SuperCid. But it should be said, that its a very risky operation and phone can be bricked very easily if you are doing something wrong.
And for your edit: You can restore a ics backup, but without a RUU it is difficult to bring back hboot 1. Only a backup of it will solve this. Recoveries usually don't backup hboot.
SV ICS super cid
I know this thread : http://forum.xda-developers.com/showthread.php?t=2264322
says to do super cid on original stock, but could I just go ahead and HEX my cid with my ICS that is unlocked/rooted/custom-recovery?
Do I have to un-do all of that to change the CID? or is that just good technique? [im also on cricket ics 4.0.4 if it matters, k2_plc_cl]
Thank you very much! I wish to change my cid right now but ill wait and see what you say if it saves me from a brick
than I'm off to s-off for all the goodies that follow haha.
I don't think, that this will be important, because SuperCid is located in a partition which has nothing to do with root or recovery.
alrighty than
haha wrong link in previous post I meant this one: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
WHEN HTCDEV UNLOCKS YOUR DEVICE YOU MUST START FROM SCRATCH!!!
Click to expand...
Click to collapse
I was reading his link and somehow posted your link, Ill use your link actually now that I read it... I thought it wouldn't matter, better safe than sorry. Ill try it out and see how it goes.
Thanks for helping
Questions about hexing CID
old.splatterhand said:
I don't think, that this will be important, because SuperCid is located in a partition which has nothing to do with root or recovery.
Click to expand...
Click to collapse
Alright its late and I'm not going to flash it yet ill wait to see what you make of this:
I have used hxd many times for xbox/psp/etc so i know how it works... it found 3 instances of my CID
(some info omitted as the 'x' char)
Code:
maincid=CRICK001xx.xx.cidlist=CRICK001.xx.xx.rid=105.xx.xx.modelid=PL8xxxxxx.xx.xx.report=com.xx.xx.skulist=1xxx.xx.xx.taskid=30xxxx.xx.xx.mainsku=1xxx.xx.onecid=1.xx.cwkey=CRICK001.ro.com.google.clientidbase=android-htc //more stuff after........
Im assuming only the first instance "maincid=CRICK001" needs to be 11111111
(or should all 3 instances of "CRICK001" be changed to 11111111)
Ill give it a go after work tomorrow when Im confident that my modifications wont render my phone as a door stop.
I need to buy you a beer, but the donation is in german, ill have to translate it when I get done
Gain_Medium said:
Alright its late and I'm not going to flash it yet ill wait to see what you make of this:
I have used hxd many times for xbox/psp/etc so i know how it works... it found 3 instances of my CID
(some info omitted as the 'x' char)
Code:
maincid=CRICK001xx.xx.cidlist=CRICK001.xx.xx.rid=105.xx.xx.modelid=PL8xxxxxx.xx.xx.report=com.xx.xx.skulist=1xxx.xx.xx.taskid=30xxxx.xx.xx.mainsku=1xxx.xx.onecid=1.xx.cwkey=CRICK001.ro.com.google.clientidbase=android-htc //more stuff after........
Im assuming only the first instance "maincid=CRICK001" needs to be 11111111
(or should all 3 instances of "CRICK001" be changed to 11111111)
Ill give it a go after work tomorrow when Im confident that my modifications wont render my phone as a door stop.
I need to buy you a beer, but the donation is in german, ill have to translate it when I get done
Click to expand...
Click to collapse
At this point i only can tell you about my guide and the picture inside. To be honest, i only noticed only one cid, together with imei. So maybe this helps you.
Edit:
Please, really be careful if your file/block is different than in my guide!
I'm on mobile and can't look at your code completely.
My guide for sure works for k2u & k2ul cause i did it myself at two different phones but i don't know, if cricket has changed more and i don't want your phone bricked.
Edit2:
I really not sure, if changing CID will work. Maybe you'll try the S-Off step by Moonshine after update to JB, would be better than a bricked phone!
You must also think, what do i profit from SuperCID?
K2u & k2ul can be unbranded this way, maybe they also profit from earlier updates.
But you can't use k2u/l Software on US phones, different network, so this point is useless for you. And i don't think, cricket will release their updates earlier for phones with SuperCID.
Just my two cents, now its on you to make your decision...
What i also want to say, i had help the first time i did.
It was @jmz who helped me, maybe he reads that and know more about cricket cid.
I think ill give it a go
I actually tried to contact him and others, but since im so new I can't send PMs (they send but nothing is in my sent box. link it never happened) so I guess unless JMZ stumbles upon this thread thats it.
As for me I don't think it would brick my phone (like a real brick) if all else I could just boot into recovery and flash back my backup stuff right?
Or if i screw up would it not even allow recovery / shell? Although a brick would permit me to buy a better popular phone
If i try it all post more details on it for other cricket users.
This is modifying the bootloader. If you do something wrong, the phone wont boot. Not in recovery, not in OS, bricked.
PS. @Gain_Medium
If you write a xda username with an @ before, the one will be notified, the he is mentioned somewhere
Side note: I don't believe that there is any reason for super cid on a cricket us carrier, unless you plan on traveling to Europe, Asia, or anywhere out of the continent.
Yes, it's cool to have accomplished superCID. But there is really no benefit here in the US, if you plan on maybe using a different service plan provider, you'll still need to unlock your SIM, even if you do achieve superCID without bricking.
Good luck with your decision. I hope to read your updates on what you have chosen. And how everything goes for you.
THESE ARE ONLY MY THOUGHTS AND OPINIONS. NOT TRYING TO SWAY YOU AWAY FROM ATTEMPTING ANYTHING.
but please research superCID for cricket mobile and see what you find.
Pros vs Cons