Related
First one. I am a Noob, nice Video by the way. And I have searched all over this forum and between thinking I had a regular HTC ONE X, and then finding the AT&T One X Page, It just got all confusing for me. Here is my issue.
I have a AT&T HTC One X, Its great, It was on 1.85 Version, I had used the 1.85 Method to Root the Device, but I could not Unlock it, but that was ok, because all I needed was Wifi Tethering, and Titanium Backup. Then the OTA update game. and of course like a Noob, I clicked yes, Not thinking...
Now the bootloader still says that the phone is Tampered. and Locked. (it never said unlocked., I know that is not possible yet for the AT&T HTC One X) And of course the Check Root app says I am not rooted, and Wifi-Tethering does not work anymore, etc.
If its suppose to be back to normal now, since i did the OTA update, why does it still say Tampered?
And is there any way to Re-Root at the stage I am at, or do I have to wait till the next rooting option becomes available?
Thanks for suffering through this Noobs questions. Hopefully someone is nice enough to help out. Or at least explain it to be. I am fine if I have to wait and then Re-Root it later. I'm not not sure if I am still good.
Flash at&t ruu to remove tampered flag.
Unfortunately if you never unlocked there is no way to root your phone now. As stated, you can run an RUU to remove the tampered flag but there's no need, don't worry about it. Just sit tight until a new root exploit is found.
_MetalHead_ said:
Unfortunately if you never unlocked there is no way to root your phone now. As stated, you can run an RUU to remove the tampered flag but there's no need, don't worry about it. Just sit tight until a new root exploit is found.
Click to expand...
Click to collapse
I think they mean you need this... http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Thanks for the quick responses, I assumed as much, in having to wait for the new 2.20 Rooting Method. Now the link above that he posted, the RUU, I just need to download that, and run it. (I tried running an RUU a few weeks back because I thought, "Oh maybe I can run the 1.85 RUU, and revert back to 1.85 And then Re-Root.) So, run the RUU, and then it will remove the Tampered flag, but it will also erase all data currently on phone, if I am not mistaken?
And is the above RUU, the proper one for the AT&T HTC One X phone that I have?
And btw I am a little pissed that other countries got a 32gb version. Guess I should blame AT&T for that one...
thruxus said:
Thanks for the quick responses, I assumed as much, in having to wait for the new 2.20 Rooting Method. Now the link above that he posted, the RUU, I just need to download that, and run it. (I tried running an RUU a few weeks back because I thought, "Oh maybe I can run the 1.85 RUU, and revert back to 1.85 And then Re-Root.) So, run the RUU, and then it will remove the Tampered flag, but it will also erase all data currently on phone, if I am not mistaken?
And is the above RUU, the proper one for the AT&T HTC One X phone that I have?
And btw I am a little pissed that other countries got a 32gb version. Guess I should blame AT&T for that one...
Click to expand...
Click to collapse
I yanked that link from the HTC website for the AT&T phone. As for the tampered thing, I don't know... Couldn't hurt. You'll probably lose your data.
http://www.htc.com/us/support/htc-one-x-att/
thruxus said:
First one. I am a Noob, nice Video by the way. And I have searched all over this forum and between thinking I had a regular HTC ONE X, and then finding the AT&T One X Page, It just got all confusing for me. Here is my issue.
I have a AT&T HTC One X, Its great, It was on 1.85 Version, I had used the 1.85 Method to Root the Device, but I could not Unlock it, but that was ok, because all I needed was Wifi Tethering, and Titanium Backup. Then the OTA update game. and of course like a Noob, I clicked yes, Not thinking...
Now the bootloader still says that the phone is Tampered. and Locked. (it never said unlocked., I know that is not possible yet for the AT&T HTC One X) And of course the Check Root app says I am not rooted, and Wifi-Tethering does not work anymore, etc.
If its suppose to be back to normal now, since i did the OTA update, why does it still say Tampered?
And is there any way to Re-Root at the stage I am at, or do I have to wait till the next rooting option becomes available?
Thanks for suffering through this Noobs questions. Hopefully someone is nice enough to help out. Or at least explain it to be. I am fine if I have to wait and then Re-Root it later. I'm not not sure if I am still good.
Click to expand...
Click to collapse
Actually a bootloader unlock was easy with 1.85 by just getting SuperCID, but since you OTA'd to 2.20 without unlocking your bootloader you now are stuck with a non-rootable, non-unlockable phone for the time being.
It still says Tampered because you rooted in the first place. Run the 2.20 RUU that was posted and it will get rid of the tampered flag. You will want to back up the contents of your SD card first.
Also, please post questions in Q&A, not in general. If you read the huge NOOB post in every section it says this.
I have bought my HTC Explorer just 2 weeks ago. I'd really love to have root access to it. But I do not want to spoil my HTC 2 year warranty...
So I have 2 questions.
First, I hear that unlocking the bootloader voids your warranty. But I hear mixed opinions about whether or not it is possible to gain root access without unlocking the bootloader. Is it impossible, or just not YET possible? I hear people talking about an exploit in HTC One that allows it or something... ( wwwmodacocom/topic/353986-testing-rooting-your-one-x-without-unlocking-the-bootloader-windows-mac-linux/ )
Second, let's say it is impossible to root without unlocking. Is it possible for me to backup my current phone data so that after unlocking the bootloader, I can restore the phone to it's previous state? With "it's previous state" I mean that it looks like my phone was never unlocked or rooted, so I can send it for warranty repairs if needed. Is RUU what I need, or more?
Any help would be appreciated. I don't want to wait 2 years to root my phone!!! :crying:
believe me i rooted my phone in a week after i bought it after surfing info on net before buying it and who cares for warranty i can now do whatever i want like new roms etc....
Wouldn't do
I care, because I always have little money on me. I want to be able to repair my phone fast when needed.
Besides, I'm not into flashing ROMs. Sense 3.5 looks good to me. I'm more into replacing system apps with my own apps, replacing HTC ringtones with my own, expanding internal memory, ect.
And really, if you can save both your warranty, and get your phone rooted, isn't that the best?
ya its our wish bt not possiible btw care your phone so much that you may not need to go to service centre
root it don't worry nothing wrong will happen enjoy the world of android without limitations or boundry
nik007rock said:
ya its our wish bt not possiible btw care your phone so much that you may not need to go to service centre
root it don't worry nothing wrong will happen enjoy the world of android without limitations or boundry
Click to expand...
Click to collapse
Thank for your input, but it's not quite the answer I'm looking for. It's a matter of opinion whether rooting is worth voiding your warranty. I'd like to have a more fact based answer.
Is it really not possible to root without unlocking boot loader?
And how about my second question? Can I undo rooting like it never happened?
The thing is, you cannot root your phone, without unlocking the bootloader, then you wont have warranty, however in this thread > http://forum.xda-developers.com/showthread.php?t=1816836 the OP says, that he knows the way, of locking the bootloader again. Locking the bootloader is important thing to do, if you have to use your warranty, rooting is not the issue, the tricky part is, for now I havn't seen anyware that you lock your bootloader and it says LOCKED, there is just a standart way that says RE-Locked, this won't do the trick. My idea is, PM the OP in the thread, if he can help you, root it, if he can't and you are afraid to brick your device, don't root it and stay with stock rom. I hope that's the answer what you looked for.
shortyoko said:
The thing is, you cannot root your phone, without unlocking the bootloader, then you wont have warranty, however in this thread > http://forum.xda-developers.com/showthread.php?t=1816836 the OP says, that he knows the way, of locking the bootloader again. Locking the bootloader is important thing to do, if you have to use your warranty, rooting is not the issue, the tricky part is, for now I havn't seen anyware that you lock your bootloader and it says LOCKED, there is just a standart way that says RE-Locked, this won't do the trick. My idea is, PM the OP in the thread, if he can help you, root it, if he can't and you are afraid to brick your device, don't root it and stay with stock rom. I hope that's the answer what you looked for.
Click to expand...
Click to collapse
Yeah, thanks. That's helped a lot. Just one more question though.
Can I make a 'screenshot' of my current system? A backup of all the data on the phone, including app settings, system settings and even the original ROM perhaps. Do you need to be rooted for that? If yes, then what can you backup without being a superuser?
That was more than one question isn't it...
Without a root, no or atleast I don't know how. Without superuser you can backup files on sd card, like pics and stuff.
hi
im not sure on the explorer but on the one X the fast boot comand
fastboot oem re lock will re lock the boot loader and then we can get the original stock recovery re add it via fast boot command and then flash the orignal RUU via the pc and most of the service guys at least in India are not all that much a techie and wont really chek so mostly ur phone will get warranty service
this is just the info i got by reading in the forum :laugh:
haree said:
hi
im not sure on the explorer but on the one X the fast boot comand
fastboot oem re lock will re lock the boot loader and then we can get the original stock recovery re add it via fast boot command and then flash the orignal RUU via the pc and most of the service guys at least in India are not all that much a techie and wont really chek so mostly ur phone will get warranty service
this is just the info i got by reading in the forum :laugh:
Click to expand...
Click to collapse
Thanks, but I live in Malaysia. I never went for warranty repair before, but just in case, I need to lock the bootloader in a way that is will say "LOCKED" instead of "RELOCKED", because IF they were to check, the latter voids the warranty. I think your method will make it say RELOCKED, no?
I've browsed the web, and this site, and although I've found a few (very few) that talk about making the bootloader say LOCKED, they all say it's risky, and meant for other phones than the explorer... Except for the link shortyoko gave me. That one is work in progress. :fingers-crossed:
P.S.
Your reply would be a lot easier to read if you use full stops instead of using 4 "and"s. Just saying...
Bump
The site mentioned above is so far a dead end as the OP has gone missing.
Is there no one else that knows how to lock the bootloader of the explorer without saying "relocked"?
Another thing. What other methods besides using HTCdev can you use to safely (read:minimum risk) unlock the bootloader of the explorer?
Djalaal said:
The site mentioned above is so far a dead end as the OP has gone missing.
Is there no one else that knows how to lock the bootloader of the explorer without saying "relocked"?
Click to expand...
Click to collapse
Not sure, but maybe with something like memory addresses or something else.
Djalaal said:
The site mentioned above is so far a dead end as the OP has gone missing.
Another thing. What other methods besides using HTCdev can you use to safely (read:minimum risk) unlock the bootloader of the explorer?
Click to expand...
Click to collapse
I think it should be possible to unlock bootloader without HTCDev, you just send them the "code" and they send you unlock_code.bin. There should be something like keygen. If it isn't created now, maybe in future it will be.
Just using the programmer's logic .
Making the bootloader say Locked instead of ReLocked isnt as easy as it sounds..
And I just had the HTC service center replace my phone.. I hard bricked it playing around with revolutionary(a tool to get S-OFF in HTC)..
And they just replaced it.. Just like that.. No hassle of Unlocked or Locked or Relocked.. Thats the situation in India..
And rooting is matter of perpective.. Some people see fit to do it, others dont.. Rooting is safe.. If you follow the instructions to the letter..
If you decide to go for rooting, HTCdev.com is the best way to go.. If there was anything wrong with the method at HTCdev website, then they wouldnt put it there.. So its thoroughly tested by a lot of users, and the company..
As far as making the bootloader say Locked instead of Relocked, i believe XDA will come up with a way sometime in the future..
A screenshot of your current system is possible, but not a screenshot that can trick HTC into keeping your warranty.. And as the Moderator, Mr. Haree said, the command "fastboot oem relock" will relock your bootloader, but you wont get your warranty back in any case.. Atleast right now..
And one last thing.. As awesome as Sense is, it gets really old and boring after some time.. And I assure you, you are missing out on soo much by not rooting.. ICS, JB, AOSP, AOKP, modded versions of these ROMs, customized Sense ROMs, lot of options to customise your phone any way you want, you can make your phone your own.. People will see your phone, and say "This is <insert your name>'s phone, without a doubt!!'
Again, its a matter of perspective..
You never know, in the two years that you have your warranty(on paper if you root), there is a very high possibility that some way, to reclaim your warranty, will come up for our Explorer..
Hope this helped oot..
Peace.. V
bhargz16 said:
And I just had the HTC service center replace my phone.. I hard bricked it playing around with revolutionary(a tool to get S-OFF in HTC)..
And they just replaced it.. Just like that.. No hassle of Unlocked or Locked or Relocked.. Thats the situation in India..
Click to expand...
Click to collapse
Dude, I think you are our hope to get s-off to our device, because you can anytime give your device back to warranty service. And looks like they doesn't care about bootloader state .
Sent from my HTC Explorer A310e using xda app-developers app
zgintasz said:
Dude, I think you are our hope to get s-off to our device, because you can anytime give your device back to warranty service. And looks like they doesn't care about bootloader state .
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
In a perfect world, I'd say hell yeah!!
But I dont know squat about anything..
I'm still learning.. Lot of reading left to do yet..
bhargz16 said:
Making the bootloader say Locked instead of ReLocked isnt as easy as it sounds..
And I just had the HTC service center replace my phone.. I hard bricked it playing around with revolutionary(a tool to get S-OFF in HTC)..
And they just replaced it.. Just like that.. No hassle of Unlocked or Locked or Relocked.. Thats the situation in India..
And rooting is matter of perpective.. Some people see fit to do it, others dont.. Rooting is safe.. If you follow the instructions to the letter..
If you decide to go for rooting, HTCdev.com is the best way to go.. If there was anything wrong with the method at HTCdev website, then they wouldnt put it there.. So its thoroughly tested by a lot of users, and the company..
As far as making the bootloader say Locked instead of Relocked, i believe XDA will come up with a way sometime in the future..
A screenshot of your current system is possible, but not a screenshot that can trick HTC into keeping your warranty.. And as the Moderator, Mr. Haree said, the command "fastboot oem relock" will relock your bootloader, but you wont get your warranty back in any case.. Atleast right now..
And one last thing.. As awesome as Sense is, it gets really old and boring after some time.. And I assure you, you are missing out on soo much by not rooting.. ICS, JB, AOSP, AOKP, modded versions of these ROMs, customized Sense ROMs, lot of options to customise your phone any way you want, you can make your phone your own.. People will see your phone, and say "This is <insert your name>'s phone, without a doubt!!'
Again, its a matter of perspective..
You never know, in the two years that you have your warranty(on paper if you root), there is a very high possibility that some way, to reclaim your warranty, will come up for our Explorer..
Hope this helped oot..
Peace.. V
Click to expand...
Click to collapse
Yeah, that helped.
And yeah, I just realized the greatness of custom ROMs. There are many benefits of rooting I know, the most important one to me right now is the ability to create more space for apps. That internal memory is really lacking on the explorer...
I realize that a way to lock the bootloader might be created before I need to send it for repairs (if ever), although I am not sure what the chances are. That's why I'm now looking into how to unlock it.
The thing is, I don't want to use HTCdev, not because it doesn't work, but for the following two reasons.
I live in Malaysia, and I believe they WILL check the bootloader. But just in case they won't check it, my warranty stays intact (on paper).
HOWEVER, I've read on multiple threads (of other android phones) that unlocking your phone using HTCdev will alert HTC that you have rooted it, and it will automatically void your warranty (on paper). No hope for warranty repairs there, even if they don't check bootloader.
I've also read on threads (of other android phones) that attempt locking the bootloader (without it saying relocked), that it doesn't work for phones that have been unlocked using HTCdev.
That's why I ask if there is another way to do it for the explorer.
Djalaal said:
Yeah, that helped.
And yeah, I just realized the greatness of custom ROMs. There are many benefits of rooting I know, the most important one to me right now is the ability to create more space for apps. That internal memory is really lacking on the explorer...
I realize that a way to lock the bootloader might be created before I need to send it for repairs (if ever), although I am not sure what the chances are. That's why I'm now looking into how to unlock it.
The thing is, I don't want to use HTCdev, not because it doesn't work, but for the following two reasons.
I live in Malaysia, and I believe they WILL check the bootloader. But just in case they won't check it, my warranty stays intact (on paper).
HOWEVER, I've read on multiple threads (of other android phones) that unlocking your phone using HTCdev will alert HTC that you have rooted it, and it will automatically void your warranty (on paper). No hope for warranty repairs there, even if they don't check bootloader.
I've also read on threads (of other android phones) that attempt locking the bootloader (without it saying relocked), that it doesn't work for phones that have been unlocked using HTCdev.
That's why I ask if there is another way to do it for the explorer.
Click to expand...
Click to collapse
You've read correctly.. There's actually two stages to unlocking your phone.. Rooting comes after unlocking.. Unlocking your bootloader and radio.. What the HTCdev website does, is unlock the bootloader.. There is no way to unlock radio for our phone yet.. And thats because this phone is relatively new..
For more info on this, just google 'What is S-OFF'... You'll find all the info you need..
Also, there's this thing called an XTC Clip.. It turns your phone to S-OFF.. A piece of hardware, it is.. A 1 time use XTC clip costs around 70 US$..
Not compatible with Explorer yet..
And also, this just in.. HTC phones unlocked from the official HTCdev website, turned to S-OFF, have been successfully Locked and S-ONed.. LOCKED.. Not RELOCKED... So they got their warranty back.. I believe they were HTC EVO 3Ds...
And there are a lot of theories flying around, for ideas regarding S-OFF or Locking instead of RElocking.. You can find them all here on XDA..
Most of them in the HTC Wildfire S forum..
And also, as long as you have S-ON, it is impossible to hard brick your phone, because all the changes that you make to the partitions, are lost on reboot.. So no error sticks.. Unless you are crazy enough like me, to try some other phone's gold card into your Explorer..
So, you wont be needing your warranty, unless you damage your phone physically, as it is not possible to (soft)damage an HTC without S-OFF..
Everybody else.. If I'm wrong in this somewhere, please correct me..
---------- Post added at 04:49 AM ---------- Previous post was at 04:44 AM ----------
HTC phones are hauntingly complicated..
I've tried unlocking the bootloader on my explorer, downloaded the files and followed the process but somewhere along the line something goes wrong.
1. What is the RUU?
I noticed on the tut. That I used the first time, it said nothing about it. Once it didn't work I tried a different tut. It mentioned flashing the RUU to update. But on that tut. On the htc.dev sight it gave that option, on the one I used that wasn't an option. Is changing the RUU mandatory and if so how?
2. Which file needs to be extracted, in the beginning there are three files that have to be pasted in a folder that I have to create. I did that and when I open the window to give the commands I notice that on the tut. It shows as admin/user: but mine reads user/user: what did I do wrong? I can't get passed that point. Any help will be appreciated. I'm anxious to root my ex. And start modifying. Thanks fellas!:what:
Sent from my HTC Explorer using xda app-developers app
daddybux said:
I've tried unlocking the bootloader on my explorer, downloaded the files and followed the process but somewhere along the line something goes wrong.
1. What is the RUU?
I noticed on the tut. That I used the first time, it said nothing about it. Once it didn't work I tried a different tut. It mentioned flashing the RUU to update. But on that tut. On the htc.dev sight it gave that option, on the one I used that wasn't an option. Is changing the RUU mandatory and if so how?
2. Which file needs to be extracted, in the beginning there are three files that have to be pasted in a folder that I have to create. I did that and when I open the window to give the commands I notice that on the tut. It shows as admin/user: but mine reads user/user: what did I do wrong? I can't get passed that point. Any help will be appreciated. I'm anxious to root my ex. And start modifying. Thanks fellas!:what:
Sent from my HTC Explorer using xda app-developers app
Click to expand...
Click to collapse
An RUU is Rom Update Utility.. Its given out by the company in the form of updates over the stock Rom.. As far as I know, an RUU isnt required for htc explorer yet..
To unlock the bootloader, you need two commands.. ADB and Fastboot.. Download this package..
http://forum.xda-developers.com/attachment.php?attachmentid=992962&d=1333997171
It has ADB and fastboot.. so you dont need to download the whole sdk.. Also, download htc sync for drivers..
After that, follow the instructions given on the htcdev website.. and if everything goes properly, you'll hve an unlocked bootloader..
shortyoko said:
The thing is, you cannot root your phone, without unlocking the bootloader, then you wont have warranty, however in this thread > http://forum.xda-developers.com/showthread.php?t=1816836 the OP says, that he knows the way, of locking the bootloader again. Locking the bootloader is important thing to do, if you have to use your warranty, rooting is not the issue, the tricky part is, for now I havn't seen anyware that you lock your bootloader and it says LOCKED, there is just a standart way that says RE-Locked, this won't do the trick. My idea is, PM the OP in the thread, if he can help you, root it, if he can't and you are afraid to brick your device, don't root it and stay with stock rom. I hope that's the answer what you looked for.
Click to expand...
Click to collapse
You can do it but no dev( with that knowledge) is interested to look in our small Pico
Example
Wildfire s bootloader can be controlled without HTCdev
There is a software by which you can unlock relock and show locked also !!!
Sent from my HTC Explorer A310e using xda premium
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.
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
I've had some problems with my rooting, and want to start fresh by returning the whole phone to stock. I already know how to relock and unlock the bootloader and root my phone, but the problem I'm trying to understand is getting back to complete stock. My phones is S-On and the current ROM version is 2.26.401.3. I've seen that If you relock the bootloader and run the RUU the problem is solved. However, I can't use the RUU as the HTC Dev website has older versions and of course using an older ROM version doesn't work at all. How do I return the system and recovery back to what they were? I've been looking for hours, and I'm afraid that If I keep messing with this phone I will brick it.
What could work is if I found the boot.img, system.img and recovery.img files that I could fast boot over, but I tried that before using someone elses files and It messed things up.
This is the very similar procedure I followed but with my Wildfire S instead. http://www.youtube.com/watch?v=1g5gEf2wgS4
Much help appreciated