So recently i bought an HTC One S with an S3 processor which its country is of Asia. I am currently at europe. I still am on Android 4.0.3 and there doesnt seem to be an update for my phone. Now i know that 4.0.4 and also JB are rolling out, but not for my device. Is there anything I can do to solve this ?
Thanks :laugh:
I live in a country where HTC sell the S3 processor only. I had my cousin sent me HOS from US, big difference.
You might want to trade for an S4 though.
In the meantime you can search the development forum and look for an S3 ROM.
Not many but there are some.
Sent from my HTC One S using xda app-developers app
Help
Thanks for your fast reply !
Kindly note that i am noob in this. Kindly tell me what is HOS and ROM. Also if i root the phone will i be able to get some updates ?
Thanks alot and Happy new year !
TRRusty said:
Thanks for your fast reply !
Kindly note that i am noob in this. Kindly tell me what is HOS and ROM. Also if i root the phone will i be able to get some updates ?
Thanks alot and Happy new year !
Click to expand...
Click to collapse
HOS stands for Htc One S and a Rom is basically an operating system for your device that is nothing like stock, has tweaks here and there things that stock doesnt, and if you root you will.still be able to receive updates but you have to relock the phone and some other things I can't remember then you can apply the update, basically you can't apply update to a rooted phone its just gonna give you and installation error then reboot your phone I think but that's basically it for your questions, hopefully it was helpful to you
T-Mobile HTC one s
Htc one S
Thanks for the information !
A friend told me that if i root the phone i can change my firmware from Asia to Europe where i live so that i can recieve updates accordingly to my phone. Is this true ?
Also is there a detailed noob instructions for me to follow and learn more about rooting the phone and installing customs ROMS etc. ?
Thanks
TRRusty said:
Thanks for the information !
A friend told me that if i root the phone i can change my firmware from Asia to Europe where i live so that i can recieve updates accordingly to my phone. Is this true ?
Also is there a detailed noob instructions for me to follow and learn more about rooting the phone and installing customs ROMS etc. ?
Thanks
Click to expand...
Click to collapse
If you root, you can manually install all sorts of fun stuff. I think if you want to remain as close to stock and receive "official" updates, super cid is something you might wanna read about. There's a thread in the Dev Section by Torxx that I used to root my S4 you might wanna look over and see if that's for you. Make sure everything you decide to do is compatible with your S3 first though.
Edit: there's also another guide in the general section
echo en Android
Evil-Monkey said:
If you root, you can manually install all sorts of fun stuff. I think if you want to remain as close to stock and receive "official" updates, super cid is something you might wanna read about. There's a thread in the Dev Section by Torxx that I used to root my S4 you might wanna look over and see if that's for you. Make sure everything you decide to do is compatible with your S3 first though.
Edit: there's also another guide in the general section
echo en Android
Click to expand...
Click to collapse
Thanks friend. I will search in the forums and take a look about what to do and how to change my firmware. I still need to learn stuff about android and root.
Still am on everything stock on 4.0.3 and looking to change my Firmware from Asia to Europe. Further assistence would be AWESOME
So, I've read several times about how to root non-AT&T phones with the new JB OTA (3.17) already installed...phones like the Rogers HOX I purchased with the OTA pre-installed (3.17.631.2).
However, I also came across a post talking about how this method worked but when he tried to flash a different ROM his phone was bricked. (Of course I can't find this now).
So, for those of you who have tried rooting a 3.17 phone, can you please post:
(1) Whether you were successful -- I admit, I'm a bit scared, because all the phones I've previously rooted have used fancy exploits!
(2) What ROMs you have flashed successfully -- of the very few threads I've found about rooting 3.17, it seems that everyone is choosing Viper and not trying others...
(3) Whether you experienced problems with certain ROMs
(4) Whether you've downgraded the touch firmware, and whether this resolved any issues
(5) Any other advice you can give!
Please please please note that I am NOT talking about the AT&T update and I am NOT referring to the bricks people are encountering when they accept that OTA. This is about 3.17, NOT the AT&T-exclusive 3.18.
I'm hoping this info will be added to 1 of the sticky posts on this forum...because what's there is American-centric...
skittleys said:
So, I've read several times about how to root non-AT&T phones with the new JB OTA (3.17) already installed...phones like the Rogers HOX I purchased with the OTA pre-installed (3.17.631.2).
However, I also came across a post talking about how this method worked but when he tried to flash a different ROM his phone was bricked. (Of course I can't find this now).
So, for those of you who have tried rooting a 3.17 phone, can you please post:
(1) Whether you were successful -- I admit, I'm a bit scared, because all the phones I've previously rooted have used fancy exploits!
(2) What ROMs you have flashed successfully -- of the very few threads I've found about rooting 3.17, it seems that everyone is choosing Viper and not trying others...
(3) Whether you experienced problems with certain ROMs
(4) Whether you've downgraded the touch firmware, and whether this resolved any issues
(5) Any other advice you can give!
Please please please note that I am NOT talking about the AT&T update and I am NOT referring to the bricks people are encountering when they accept that OTA. This is about 3.17, NOT the AT&T-exclusive 3.18.
I'm hoping this info will be added to 1 of the sticky posts on this forum...because what's there is American-centric...
Click to expand...
Click to collapse
You can just unlock the bootloader from HTC Dev. I think, and I could be wrong, that only AT&T isn't allowing bootloader unlock. I know for a fact Rogers and Telus can just unlock through HTC DEV and once bootloader is unlocked you can flash TWRP.
If someone bricked flashing a rom, it was not designed for his/her phone. Probably for the international one X which is oh so common.
Since you have 3.17, you would need to downgrade your Touchscreen Firmware in order to use AOSP roms but sense roms will work fine. To downgrade your touchscreen firmware you would first need S-OFF but as SuperCID works only on AT&T phones with certain firmwares you would need to manually change your CID to 11111111
HTC Dev, supercid, soff, downgrade firmware.
Then flash anything.
I know what the procedure is, I'm just a bit worried about what could happen after because of that 1 post that I read.
exad, I wondered if it that ROM was designed for the wrong phone, but confirmed that it wasn't. I do suspect that it was because of the touch firmware, but again, I've never actually seen anyone say that they've rooted from 3.17 and installed a ROM other than Viper...hence my worry...because I prefer ROMs that aren't based on Sense.
I see that you're both outside the USA. Did you root the 3.17 version, or did you do it earlier and never installed the OTA?
skittleys said:
I know what the procedure is, I'm just a bit worried about what could happen after because of that 1 post that I read.
exad, I wondered if it that ROM was designed for the wrong phone, but confirmed that it wasn't. I do suspect that it was because of the touch firmware, but again, I've never actually seen anyone say that they've rooted from 3.17 and installed a ROM other than Viper...hence my worry...because I prefer ROMs that aren't based on Sense.
I see that you're both outside the USA. Did you root the 3.17 version, or did you do it earlier and never installed the OTA?
Click to expand...
Click to collapse
Outside the USA you don't need super cid you can HTC DEV unlock so it's not the same. We can root any firmware.
You can't brick flashing a rom unless you're flashing a rom for the wrong phone, aosp roms won't work with the touchscreen update you'd need to downgrade it. If you're not an idiot, you won't brick.
I really don't understand your fear.. Viper is just fast, smooth and customizable. you'll be fine running other roms except AOSP until you downgrade the touchscreen firmware.
I feel like this thread is going around in circles.
If you have a rogers HOX, htc dev unlock and flash twrp. It's crazy simple.
I can't read.
Dacra said:
I can't read.
Click to expand...
Click to collapse
You and me both buddy, and I've been here for 4 years. Ugh!
Sent from my HTC One X
exad said:
I feel like this thread is going around in circles.
Click to expand...
Click to collapse
Yes, I feel like it's going around in circles too. Of course, that could be because you aren't addressing the questions I actually asked!
I know the procedure, I know what the limitation is in the US, I know about flashing ROMs and making sure they're for your specific phone before doing so. Like I already said, I'm not at all new to Android hacking. What I don't know is whether anyone has successfully rooted and flashed a ROM starting from a 3.1x OTA and its accompanying changes like the new bootloader. After all, we don't really know what changes HTC's made. For all we know, installing a ROM not based on 3.xx (like an AOSP-based ROM) causes issues beyond the touchscreen problem. These worries are compounded by the fact that the only post I've seen where someone tried to flash an AOSP-based ROM was a failure. I've yet to see someone say they've had success, which is why I started this thread in the first place. Because while I do assume that someone in this large user base has done it, in my line of business, acting on assumptions in the absence of even some weak evidence for that assumption and where there's documentation to suggest otherwise gets you fired, sued, and stripped of your licence.
So, let me ask my main question yet again—in fact, the ONLY question I asked in my last post—and hopefully it's clear this time:
Have you or anyone else rooted your HOX for the first time starting from an official HTC 3.17 ROM with its accompanying changes in the bootloader etc. and been successful? And if so, were you or that person able to successfully flash and use an AOSP-based ROM?
Sent from my HTC One X using xda app-developers app
I did. I have a Telus HOXL that was on the OTA Jellybean.
I SIM unlocked the phone (unnecessary but I wanted to use it on Bell). Then I HTCdev unlocked the bootloader. Flashed TWRP, rooted, SuperCID'd then s-off'ed. Finally I downgraded my touchpanel firmware.
However, I haven't installed an AOSP ROM yet since ViperXL has been working so great.
skittleys said:
Yes, I feel like it's going around in circles too. Of course, that could be because you aren't addressing the questions I actually asked!
I know the procedure, I know what the limitation is in the US, I know about flashing ROMs and making sure they're for your specific phone before doing so. Like I already said, I'm not at all new to Android hacking. What I don't know is whether anyone has successfully rooted and flashed a ROM starting from a 3.1x OTA and its accompanying changes like the new bootloader. After all, we don't really know what changes HTC's made. For all we know, installing a ROM not based on 3.xx (like an AOSP-based ROM) causes issues beyond the touchscreen problem. These worries are compounded by the fact that the only post I've seen where someone tried to flash an AOSP-based ROM was a failure. I've yet to see someone say they've had success, which is why I started this thread in the first place. Because while I do assume that someone in this large user base has done it, in my line of business, acting on assumptions in the absence of even some weak evidence for that assumption and where there's documentation to suggest otherwise gets you fired, sued, and stripped of your licence.
So, let me ask my main question yet again—in fact, the ONLY question I asked in my last post—and hopefully it's clear this time:
Have you or anyone else rooted your HOX for the first time starting from an official HTC 3.17 ROM with its accompanying changes in the bootloader etc. and been successful? And if so, were you or that person able to successfully flash and use an AOSP-based ROM?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
There's no limitations with non-aT&T one x. They allow you to unlock bootlader regardless of software. You need to S-OFF after and then downgrade Touchscreen Firmware to run AOSP, there won't be any issues running AOSP.
These questions could have been easily answered with just a little bit of research on your part.
Okay, installed LiquidSmooth and it's working so AOSP ROM's are fine.
Sent from my HTC One X using xda app-developers app
ChronoReverse said:
I did. I have a Telus HOXL that was on the OTA Jellybean.
I SIM unlocked the phone (unnecessary but I wanted to use it on Bell). Then I HTCdev unlocked the bootloader. Flashed TWRP, rooted, SuperCID'd then s-off'ed. Finally I downgraded my touchpanel firmware.
However, I haven't installed an AOSP ROM yet since ViperXL has been working so great.
.....................
Okay, installed LiquidSmooth and it's working so AOSP ROM's are fine.
Click to expand...
Click to collapse
Thanks, ChronoReverse!
exad said:
There's no limitations with non-aT&T one x. They allow you to unlock bootlader regardless of software. You need to S-OFF after and then downgrade Touchscreen Firmware to run AOSP, there won't be any issues running AOSP.
These questions could have been easily answered with just a little bit of research on your part.
Click to expand...
Click to collapse
Again, you're telling me things I already know and completely ignoring the questions I actually asked and the points I already made.
I know you can unlock the bootloader regardless of the current ROM...that doesn't necessarily mean that you can then go and flash any ROM designed for this phone but developed with different bootloaders and expect it to work. Plus, the bootloader was just one example of the many changes.
As I've said in each and every one of my posts, I already know the procedure, including for downgrading the firmware. Saying "there won't be any issues running AOSP" is a very bold statement, considering that I've yet to find evidence of anyone having actually done that (until this thread, that is). Again, theoretical vs. actual experience is a huge distinction.
And no, the questions I have asked aren't easily answered with a little research, since I did a LOT of research and found nothing. Something I have reiterated numerous times. The non-existent questions you are answering can be found with a tiny bit of research, and I already found them, which is why I didn't ask them in the first place.
How bout you unlock your bootloader and flash whatever rom you want?
skittleys said:
Thanks, ChronoReverse!
Again, you're telling me things I already know and completely ignoring the questions I actually asked and the points I already made.
I know you can unlock the bootloader regardless of the current ROM...that doesn't necessarily mean that you can then go and flash any ROM designed for this phone but developed with different bootloaders and expect it to work. Plus, the bootloader was just one example of the many changes.
As I've said in each and every one of my posts, I already know the procedure, including for downgrading the firmware. Saying "there won't be any issues running AOSP" is a very bold statement, considering that I've yet to find evidence of anyone having actually done that (until this thread, that is). Again, theoretical vs. actual experience is a huge distinction.
And no, the questions I have asked aren't easily answered with a little research, since I did a LOT of research and found nothing. Something I have reiterated numerous times. The non-existent questions you are answering can be found with a tiny bit of research, and I already found them, which is why I didn't ask them in the first place.
Click to expand...
Click to collapse
Don't be a ****. I answered your question. You're just not understanding.
S-OFF UPGRADE TO LATEST SOFTWARE, DOWNGRADE TOUCHSCREEN. RUN WHATEVER ROM YOU WANT WITH NO ISSUES. AOSP, SENSE, SENSE BASED SENSELESS. WHATEVER YOU WANT, NO INCOMPATIBILITIES. FFS.
You're assuming there are meaningful hardware differences in this phone across carriers. In fact, there are not.
People have successfully run 3.17 based roms on 3.18 carrier phones and vice versa. The differences are minor and superficial and pertain entirely to carrier branding. The 2.14 hboot is the same across all carriers.
I understand your concern, but you're trying to create an issue where none exists.
Not trying for a useless post but damn pointless topic...
Sent from my HTC One XL using xda app-developers app
Well that wasted about eight minutes and I am still confused.
Sent from my HTC One X using xda premium
iElvis said:
You're assuming there are meaningful hardware differences in this phone across carriers. In fact, there are not.
People have successfully run 3.17 based roms on 3.18 carrier phones and vice versa. The differences are minor and superficial and pertain entirely to carrier branding. The 2.14 hboot is the same across all carriers.
I understand your concern, but you're trying to create an issue where none exists.
Click to expand...
Click to collapse
I know that. That's not what I was worried about. When I mentioned 3.18 in my first post, it was only to make it clear that I wasn't yet another AT&T user who'd just flashed the OTA. What I was worried about was ROMs that were developed using the older hboots...and I wasn't so much worried about the bootloader being different in the first place, it was just an example of the changes that occurred with the OTA that won't simply be overridden with a factory reset/rooting/flashing a new ROM/whatever.
exad said:
Don't be a ****. I answered your question. You're just not understanding.
S-OFF UPGRADE TO LATEST SOFTWARE, DOWNGRADE TOUCHSCREEN. RUN WHATEVER ROM YOU WANT WITH NO ISSUES. AOSP, SENSE, SENSE BASED SENSELESS. WHATEVER YOU WANT, NO INCOMPATIBILITIES. FFS.
Click to expand...
Click to collapse
31ken31 said:
Not trying for a useless post but damn pointless topic...
Click to expand...
Click to collapse
Venomtester said:
Well that wasted about eight minutes and I am still confused.
Click to expand...
Click to collapse
You know, you guys are being awfully mean to someone who just wanted a straightforward answer to something she couldn't find the answer to. Outside of this thread, I challenge you to search for and find a post wherein someone's even implied that they upgraded to the 3.xx RUU, fully unlocked/rooted their phone, and flashed a non-Sense-based ROM. Don't just go clicking to a post you already know exists. Search for it. You'll find that search is fruitless. In fact, until this thread a couple of weeks ago, there was no such thread even for Sense-based ROMs. And finally, there was the aforementioned post I found from someone who'd successfully rooted and installed ViperXL but bricked his phone when flashing an AOSP-based ROM. With all that in mind, can you understand my lack of confidence? Can you understand why I started this thread instead of just going ahead with it? And then can you maybe stop criticizing someone who actually bothered to research her issue before posting and discovered nothing but a lack of information?
Your question was answered in the first response but you dragged it out saying that it wasn't. I spend day and night on the forum giving free help, by choice, mind you, the least you could do is read and take the advice that is given, instead of wasting everyone's time with sillyness and appreciate the time that people spend answering your questions.
This forum is not intended for people who don't understand what they are doing. Devs are doing this stuff for themselves, not you, they choose to share it with you and if you are not familiar with this kind of thing or are weary of risk. DONT ROOT YOUR PHONE.
Sent from my One X using xda app-developers app
Hello Im thinking on get a M8 but before I want to make sure that the phone still able to be root it and also if ill be able to run roms like PA thats ia not showing here but is showing on the maig thread for M8, thanks for your help
juancaperez2000 said:
Hello Im thinking on get a M8 but before I want to make sure that the phone still able to be root it and also if ill be able to run roms like PA thats ia not showing here but is showing on the maig thread for M8, thanks for your help
Click to expand...
Click to collapse
Yes, you can still ROOT/S-OFF all M8 models using Sunshine I believe. You can also install most if not all of the ROM's available for it, including PA. To my knowledge most of the ROM's in the main M8 section are compatible with the carrier versions of the phone and if they aren't then they say so somewhere in the threads, someone can correct me on the "most of" part if i'm wrong.
S1L3nTShaDoWz said:
Yes, you can still ROOT/S-OFF all M8 models using Sunshine I believe. You can also install most if not all of the ROM's available for it, including PA. To my knowledge most of the ROM's in the main M8 section are compatible with the carrier versions of the phone and if they aren't then they say so somewhere in the threads, someone can correct me on the "most of" part if i'm wrong.
Click to expand...
Click to collapse
Thanks for you quick response.
I was finally able to S-off with sunshine and now I want to upgrade the firmware, but im pretty lost on this, does anyone have a video or any tips on how to upgrade the firmware? I would really appreciate it.
nervana1 said:
I was finally able to S-off with sunshine and now I want to upgrade the firmware, but im pretty lost on this, does anyone have a video or any tips on how to upgrade the firmware? I would really appreciate it.
Click to expand...
Click to collapse
There's an entire thread in the dev section dedicated to it. You have two options. One requires a pc and the other does not.
saw the post but it doesnt really help as there are tons of different files, and coming from a brand new 4.4.2phone im lost.
nervana1 said:
saw the post but it doesnt really help as there are tons of different files, and coming from a brand new 4.4.2phone im lost.
Click to expand...
Click to collapse
Download and run the exe on the first post here. http://forum.xda-developers.com/showthread.php?t=2883845
That will put you on latest stock software and firmware. Then flash whatever recovery you want and then venom.
I have a Verizon S3 unlocked, no root, totally stock android 4.4.2 with baseband yudne1 and build kot49h.i535vrudne1
Want to confirm if I can install CM13 nightly. Everything I read indicates I need to root and update recovery and all that good stuff but it is not possible on 4.4.2
Just want to confirm if anything has changed in the past year with a new process. Forums have a lot of old guides so I would appreciate a quick yes or no. if yes, any link to a stable procedure would really be appreciated.
Thank you in advance. XDA is awesome and the people on this forum are some of the best.
Thanks,
ARiK
arikinthecity said:
I have a Verizon S3 unlocked, no root, totally stock android 4.4.2 with baseband yudne1 and build kot49h.i535vrudne1
Want to confirm if I can install CM13 nightly. Everything I read indicates I need to root and update recovery and all that good stuff but it is not possible on 4.4.2
Just want to confirm if anything has changed in the past year with a new process. Forums have a lot of old guides so I would appreciate a quick yes or no. if yes, any link to a stable procedure would really be appreciated.
Thank you in advance. XDA is awesome and the people on this forum are some of the best.
Thanks,
ARiK
Click to expand...
Click to collapse
No it currently cannot run CM13 or any version of CM. Only via safestrap with the 3 options stock, Paul pizz and Superlite
Sent from my Nexus 6
arikinthecity said:
I have a Verizon S3 unlocked, no root, totally stock android 4.4.2 with baseband yudne1 and build kot49h.i535vrudne1
Want to confirm if I can install CM13 nightly. Everything I read indicates I need to root and update recovery and all that good stuff but it is not possible on 4.4.2
Just want to confirm if anything has changed in the past year with a new process. Forums have a lot of old guides so I would appreciate a quick yes or no. if yes, any link to a stable procedure would really be appreciated.
Thank you in advance. XDA is awesome and the people on this forum are some of the best.
Thanks,
ARiK
Click to expand...
Click to collapse
Hey!
As @ShapesBlue says, if you took the OTA to 4.2.2 then you are locked. HOWEVER, there is a method developed by the typical enterprising XDA member that "Downgrades" the firmware by flashing part of the boot loader/firmware but leaves the crucial bit intact that doesn't brick the phone. Sort of a hybrid firmware flash. I believe it's supposed to open the phone up to flashing TWRP and non-stock custom ROMs. I know someone who used it and it worked on CM12.1 last year, but he also had some trouble after awhile (don't know if that was related to this procedure or not) and made an error later that bricked his phone, permanently it seems.
What isn't mentioned in that OP, at least the last time I looked, was that after doing this procedure, if you flash the firmware recommended in the CM12 and CM13 thread OP's, you will overwrite the partition that is spared in his zip file. Then you will be dead! He does explain exactly what partitions are flashed by telling you how to make the zip file. The updater-script I expect is not touched. Looking at it or in the other files you'll need to do this process will show you what's written where, but they have the partitions names. You can go into the CM12.1 thread OP on XDA for our phone and by clicking on the "d2vzw ROM Extras" link you can find all kinds of stuff, plus a few different partition tables that tell you how your phone is setup. There is other info in the OP itself about this and other topics related to flashing CM as well. (I'm the OP )
WARNING! Don't go into this haphazardly though. I would read through that thread thoroughly and see what if any success people are reporting, and ask questions. You don't want to ruin your phone!
It's in the "Android Development" forum in the root forum for our phone.
Report back on what you end up doing.:good: