If figure that this would be the place to ask these questions considering that there is no general HTC forum on this board and that I expect a decent amount of conversation about hboot and S-OFF to converge here. My questions are about the boot process and the specifics about how the RTOS that operates the baseband runs on HTC's new devices.
1: I have learned that on most phones, the baseband processor and the application process boot and operate independently of each other. If I am correct, HTC is using Qualcomm's Snapdragon SoC in its newest devices, which includes a higher level of integration between the baseband and application processors. They may even be indistinguishable as far as I know. hboot is not verified by the hardware but verifies any updates to itself, as far as the Flyer is concerned. Knowing that S-OFF allows for the loading of custom radio firmware implies that hboot verifies the baseband's software, and therefore is the absolute root of trust of trust on HTC's devices. What mechanism allows the baseband software and the Linux kernel to run side-by-side without interfering with the other's processes? The only way I can see this working is if a hypervisor is running on the device or the baseband has more privileges.
2: Revolutionary changes S-ON to S-OFF whereas Unrevoked could only patch one of the bootloaders (I think) to ignore secuflag because secuflag was inaccessible. This appears to contradict the statement in the above paragraph that hboot is the root of trust and loads both the baseband firmware and the application firmware. Which is it or is there something I am missing?
3: What is the difference between hboot and the SPL (Secondary Program Loader, I believe. Think HSPL.)?
Sent from my DROID2 GLOBAL using XDA App
I am bumping this thread.
Another bump.
And another one.
Your best bet would be asking Agrabren on twitter. He's been working on getting S-OFF before we got Revolutionary to give the S-OFF. If you look at he EVO 3D forums, there was a lot of chatter and PDF files on how everything was linked together. Since the EVO 3D and Sensation are pretty much the same except the Ram and 3D features, it's the same work.
Edit:There was also an PDF file with the schematics of everything on the motherboard and how everything connected, what booted what. I'll try to find it and I'll private message it to you and post on this thread.
Also, on HTC devices as far as I know, the Radio is the trust of everything, It controls everything on the device. Ever since the G2 was released (this is when they introduced some heavy duty locks and wasn't easy as previous devices), I've also been following up on how everything is controlled on these phones. During the 2 months that it took devs to gain S=OFF, I've read IRC logs and tried everything and got a good idea of how everything works.
But here's what I know. Once the radio is S=OFF then we have *COMPLETE* control over our phones. With the bootloader S=OFF and radio S=OFF, we can still flash recovery, different ENG bootloader but cannot flash any unsigned radio images.
When the phone boots up though, I know the first thing that is booted is the radio, then bootloader, kernel, and OS. (I might have missed one or two more things that's also booted and checked).
The bootloader also checks kernel, and system partition if they are signed with HTC's private keys. If the system partition is changed on a device with S=ON, the system will be changed the way it was back from the factory, this is the reason we have temp root.
Also the baseband has it's own processes in Android and Android will never allow you to modify the radio while it's booted.
Through my conversations with globatron, I was under the impression hboot was the root of trust.
Does anyone else care to comment?
Edit: I have seen some custom radios for HTC's Android phones. What the mechanism is, I don't know.
Yes,I'm follow u
Sent from my HTC Sensation XE with Beats Audio using Tapatalk
that's an interesting question.. i'll have to follow and do some research on it myself
That's more in-depth than I know. What I *do* know is that the s-off flag is kept in the NVRAM. Who reads it and uses it? Probably the radio first.
EDIT: Definitely the radio first, because if you flash an ENG bootloader then go back to S-ON, it bricks the device.
Is that because the radio boots first?
Yes, as agabren pointed out, the radio sets the security keys. If you have a S-off radio then you're pretty much free.
That's also why most devs attack the radio first to gain FULL control of the device.
Even if the bootloader sstates its locked, only the bootloader is, not the radio.
The radio is the most important. The best thing you could do is search for the G2 s-off irc logs. There's a website (I forgot) by a dev that mapped out everything. How everything works on HTC devices. I'll try to find it.
Sent from my HTC Sensation Z710e using XDA App
I has been hoping that hboot was first. I don't like the baseband-application architecture. I don't like designs with two or more independent systems. Just a matter of taste (as dumb as that sounds).
I have another question: does the radio boot hboot or are the two processes started separately at boot time?
Sent from my DROID2 GLOBAL using XDA App
xdviper said:
Yes, as agabren pointed out, the radio sets the security keys. If you have a S-off radio then you're pretty much free.
That's also why most devs attack the radio first to gain FULL control of the device.
Even if the bootloader sstates its locked, only the bootloader is, not the radio.
The radio is the most important. The best thing you could do is search for the G2 s-off irc logs. There's a website (I forgot) by a dev that mapped out everything. How everything works on HTC devices. I'll try to find it.
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Hi,
I own a HTC Sensation, but the bootloader shows UNLOCKED, S-ON and hboot 1.23.0000. I wanted to get the S-OFF. Can you help me? Or wait for the new issue in the Revolutionary?
Thanks
djnero666 said:
Hi,
I own a HTC Sensation, but the bootloader shows UNLOCKED, S-ON and hboot 1.23.0000. I wanted to get the S-OFF. Can you help me? Or wait for the new issue in the Revolutionary?
Thanks
Click to expand...
Click to collapse
Start a new thread. I am really sick of replies that have nothing to do with the topic.
djnero666 said:
Hi,
I own a HTC Sensation, but the bootloader shows UNLOCKED, S-ON and hboot 1.23.0000. I wanted to get the S-OFF. Can you help me? Or wait for the new issue in the Revolutionary?
Thanks
Click to expand...
Click to collapse
You need to flash an older h boot, 1.17, however, if you used HTC unlock method I am not sure about s off using Revolutionary, it used to not be possible. IDK, maybe it's changed now.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Does the NVRAM reside on a separate chip?
Related
I want to downgrade my desire S to be able to use revolutionary.
Can I use this method? (http://forum.xda-developers.com/showthread.php?t=1399331)
My Desire has the following specifications:
- 2.3.5
- Hboot 2.000.002
- 2.10.401.8
What version do I download the RUU? 2.10.401.8?
If this method does not work what happens? The phone continues to work the same way?
Thanks
Fredericosilva said:
I want to downgrade my desire S to be able to use revolutionary.
Can I use this method? (http://forum.xda-developers.com/showthread.php?t=1399331)
My Desire has the following specifications:
- 2.3.5
- Hboot 2.000.002
- 2.10.401.8
What version do I download the RUU? 2.10.401.8?
If this method does not work what happens? The phone continues to work the same way?
Thanks
Click to expand...
Click to collapse
I really wish you wouldn't do that. Switching indiscriminately between HBOOT versions is one possible way (if something goes wrong) to convert your Desire S to one very expensive paperweight. Most new ROMs require the newer HBOOT. Guaranteed you won't be staying long on the old HBOOT. But if you insist, a brief glimpse at the Dev section should satiate your curiosity.
Saipro said:
I really wish you wouldn't do that. Switching indiscriminately between HBOOT versions is one possible way (if something goes wrong) to convert your Desire S to one very expensive paperweight. Most new ROMs require the newer HBOOT. Guaranteed you won't be staying long on the old HBOOT. But if you insist, a brief glimpse at the Dev section should satiate your curiosity.
Click to expand...
Click to collapse
So what you recommend to do root and install a new rom? The only way I have to s-off is downgrade hboot, for now...
Fredericosilva said:
So what you recommend to do root and install a new rom? The only way I have to s-off is downgrade hboot, for now...
Click to expand...
Click to collapse
Ok. Downgrade. But it's as easy as pushing the appropriate HBOOT to your device via ADB. If you've downloaded the appropriate HBOOT, you're almost there. It's as easy as using this tested & trusted method
Saipro said:
Ok. Downgrade. But it's as easy as pushing the appropriate HBOOT to your device via ADB. If you've downloaded the appropriate HBOOT, you're almost there. It's as easy as using this tested & trusted method
Click to expand...
Click to collapse
I believe it's not that easy. Engineering HBOOT (or any HBOOT for that matter) can't be flashed without S-OFF, since HTCDev-unlocked bootloader won't accept that flash, from ADB or any other source - the writes just won't go through, they'll be cached by eMMC and lost upon reboot.
So, as the OP says, he has no choice but to downgrade.
OP, there's a sticky in Development section, ROMS/RECOVERY/ROOT/HBOOT/etc. Please read it instead of posting, and you'll discover 3 guides (at least).
Jack_R1 said:
I believe it's not that easy. Engineering HBOOT (or any HBOOT for that matter) can't be flashed without S-OFF, since HTCDev-unlocked bootloader won't accept that flash, from ADB or any other source - the writes just won't go through, they'll be cached by eMMC and lost upon reboot.
So, as the OP says, he has no choice but to downgrade.
OP, there's a sticky in Development section, ROMS/RECOVERY/ROOT/HBOOT/etc. Please read it instead of posting, and you'll discover 3 guides (at least).
Click to expand...
Click to collapse
Well, that could be. But a few people seem to have done it via ADB. What really puzzles me is the number of people who unlock their phones using HTCDEV. It's unbelievable!
It seems much easier and less intimidating than S-OFF guides.
And then they're getting stuck, because they usually don't understand a thing in what they did. And then they come and open endless threads "Ok, I unlocked with HTCDev, now what do I do". Oh well, such is life...
mr
how to root evo 4g
Jack_R1 said:
I believe it's not that easy. Engineering HBOOT (or any HBOOT for that matter) can't be flashed without S-OFF, since HTCDev-unlocked bootloader won't accept that flash, from ADB or any other source - the writes just won't go through, they'll be cached by eMMC and lost upon reboot.
So, as the OP says, he has no choice but to downgrade.
OP, there's a sticky in Development section, ROMS/RECOVERY/ROOT/HBOOT/etc. Please read it instead of posting, and you'll discover 3 guides (at least).
Click to expand...
Click to collapse
Hmm confusing this root is....
Hmm been reading for a week now, I have the same Hboot and RUU and I'm a bit puzzeled.
I don't want to go the HTCDev way, because of the limitations afterward.
I have an unbranded Desire S, S-on and locked, with Hboot 2.00.0002.
- When I understand it right there is no other way then a downgrade right?
- This downgrade has to be done with Zergrush (although I thought it didn't work for 2.3.3 and above?) to gain temp root, then the misc_version to fool the phone so we can use the older RUU (not sure which one to take though, the oldest WWE?)
Now I could s-off through AlpaRev, but I have a question or two there as well
- I want to work with the Engineering Hboot (seems to be better?), can I do this directy via AlphaRev Iso, or do I need to flash/push it later? What would be the advantage over using the Alpharev one?
- Similar question, but now about the recovery that comes with Alpharev (CWM). I prefer 4EXT, can I bake that in in one go, or do I rather use the 4EXT installer from the market afterward?
Feel free to comment on my noobness, but on my desire it was a lot easier.
Don't want to end up with a paper weight.
Cheers
May the force be with you...
Edit: quoted the wrong post...
You sound very well informed and have done your research well, something to be commended.
Downgrade hboot, soff with revolutionary then afterwards fast boot flash eng hboot
Eng hboot is better IMO, as provides you more options
Swyped firm ym Desire S unsig XAD Permuim
ben_pyett said:
You sound very well informed and have done your research well, something to be commended.
Downgrade hboot, soff with revolutionary then afterwards fast boot flash eng hboot
Eng hboot is better IMO, as provides you more options
Swyped firm ym Desire S unsig XAD Permuim
Click to expand...
Click to collapse
Thanks for the boost of confidence, I'm no cmd line hero, hence the hesitation.
I used mainly terminal emulator to push recovery, hboot were easy as well with the right zip.
Could you comment in further detail about my RUU question and tell me if it is possible to add EXT4 install with Alparev?
Is this btw also a downgrade of the os and radio? I.o.w. does this process leave me with an old radio and os (2.3.3 without 3.0 sense)?
I understood as well that the hboot 0.98.0000 and 0002, work only with RUU containing 2.3.3?
Does this engineering boot work with 2.3.5 and above?
What confuses the hell out of me is the need to relock the phone, wasn't the whole idea not the direct opposite?
Why this need to relock?
Again, cheers for the help, on the old desire this was all quite easy obtained by just reading and a lot less command line code..
germsandbugs said:
Thanks for the boost of confidence, I'm no cmd line hero, hence the hesitation.
I used mainly terminal emulator to push recovery, hboot were easy as well with the right zip.
Could you comment in further detail about my RUU question and tell me if it is possible to add EXT4 install with Alparev?
Is this btw also a downgrade of the os and radio? I.o.w. does this process leave me with an old radio and os (2.3.3 without 3.0 sense)?
I understood as well that the hboot 0.98.0000 and 0002, work only with RUU containing 2.3.3?
Does this engineering boot work with 2.3.5 and above?
What confuses the hell out of me is the need to relock the phone, wasn't the whole idea not the direct opposite?
Why this need to relock?
Again, cheers for the help, on the old desire this was all quite easy obtained by just reading and a lot less command line code..
Click to expand...
Click to collapse
Yes once downgraded you will be on 2.3.3 and sense 2.1.
Did it myself a week back. Don't want sense 3.or 3.5. Perfectly happy with sense 4 and go back to 2.1 for camera.
Coming to the hboot.
you should definitely flash an eng-hboot, which is good on case you need warranty.
I would recommend you to go for the old eng hboot 0.98 as it had a larger cache memory. So should stay on 0.98 unless facing issues.
I don't think you need to relock again. That would be needed only if you need to go for warranty
If you follow the steps listed, out should be straight forward. Let me know if you need any help.
Swyped from a primed Desire S
I've searched (both xda and external sites) and I've read through many threads but I still don't have clear answers to these questions so I'd appreciate any help anyone can provide. I'm an Atrix user so I'm assuming a worst-case scenario mindset in order to properly weigh my options before upgrading.
1. What issues would HOX users face if the devs are never able to achieve S-OFF?
I think the normal behavior for S-ON is that you are not able flash kernels or radios. However, the devs have currently figured out a way to flash kernels on the HOX despite the lack of S-OFF. Similarly, there may also be a way to flash radios despite the lack of S-OFF too but this has not yet been achieved. I think S-OFF also lets a user resize partitions but I'm not sure why this would be a huge issue. Is this all more or less correct?
2. 1.85 devices can have their bootloaders unlocked once a new root exploit is found for that firmware, right?
My concern is that I'll get a 1.85 and be permanently stuck with an AT&T/HTC ROM.
This all comes down to the HOX vs. SGS3 for me. I really prefer the HOX but I'm not willing to risk being stuck with the AT&T ROM. Of course, this could be moot because we don't yet know whether or not AT&T will be able to convince Samsung to make an exception to their bootloader policy like they were able to do with HTC.
Thanks again for your help.
I think AT&T phones are being shipped with 1.73 right now which is capable of being rooted. Someone correct me if I'm wrong.
Yes if the htc has 1.73 it can be rooted. Then the cid can be changed to unlock the bootloader through htc dev. After that you lock the bootloader back and upgrade to 1.85. Then you re unlock the bootloader and install cwm and after installing cwm flash SU for root on 1.85. As for Samsung EHH..
1. As far as I know all you've stated is correct, if a dev wants to pop in to correct me by all means you can. There are some kernels that are "flashable" not neccessarily stable though just because of the lack of a source code. And the DCM by viperboy is pretty awesome.
2. Yes they will be able to. Most people are stuck on 1.85 because they were too eager and updated before any development. They're not really all to blame it's just human nature. But as far as I know there is no current development for root because the method from 1.73> to root> to CWM is getting the primary focus. Phones as of right now are being shipped with 1.73 IF you can even get your hands on one. It's hard because of all the customs issues.
Both phones will be excellent and both will get great development. I've just been an HTC guy so I like the HOX. However if you want "right now development" the GS3 might be a better choice in all honesty depending on what AT&T decides on the BL. But HOX development is moving along quite nicely. My phone kicks ass!
Thanks, everyone.
@Shaddy-Z
So in your opinion the lack of progress in obtaining root for 1.85 is mainly due to a smaller current need and not because of some new or challenging hurdle? Would you expect a new method to pop up once a majority of phones begin shipping with 1.85? What would you put the odds at? I know this is not apples to apples but I have residual skepticism carried over from the Atrix bootloader affair. The devs were basically thwarted/defeated and the unlock was only achieved as a result of an anonymous/unsanctioned leak.
Just saw this post: http://forum.xda-developers.com/showthread.php?t=1693624 It appears they are shipping now with 1.85...
You do not need s-off to flash kernels. You can flash them through fastboot just fine, as long as you have an unlocked bootloader. You just can't flash them through recovery until we have s-off. I really don't think s-off is even needed. It would be nice to have but it doesn't stop you from doing anything except flashing radios. I was in the same situation when I was using the Vivid. I didn't even s-off my Vivid when the tool was released because I didn't need it.
pside15 said:
You do not need s-off to flash kernels. You can flash them through fastboot just fine, as long as you have an unlocked bootloader. You just can't flash them through recovery until we have s-off. I really don't think s-off is even needed. It would be nice to have but it doesn't stop you from doing anything except flashing radios. I was in the same situation when I was using the Vivid. I didn't even s-off my Vivid when the tool was released because I didn't need it.
Click to expand...
Click to collapse
Actually they have found a way to.flash kernels and radios in recovery.
Sent from my HTC One X using xda premium
In this thread it is mentioned that everything can be flashed though custom recovery now http://forum.xda-developers.com/showthread.php?t=1639972&page=99
so s-off is not limiting us anymore
So... No need for s-off now then? :thumbup:
Sent from my HTC One X 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 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,
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