Related
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 everybody on my first post in xda, i need your help, it is why i am here, i have a Htc One X of 16GB but with tegra 3, don't have Lte and it say that is from europe in the hardware info (Have HTC logo, don¡t company logo or at&t logo)(yoigo get that one to me, is free sim) and then i don't know if that one is at&t, evita, if is the XL, or simply one x international, i am just now
i was searching for how to root that one (and if possible flash that one) yesterday and today, i have linux installed, ubuntu 13.10, and all what i try to do fail or didn't work. (believe me, i read a long number of post and download a long number of files and try some different methods typing on the console.
I need your help to root my phone, i will accept to unlock bootloader, to edit hex, to flash 20 files, to downgrade my phone, and to burn my face (preffer to don't do it) if neccesary.
How can i do it?
All possible util data from my device:
Resume (Fully updated with the official software)
USB Depuration mode: On.
Android 4.2.2
Sense 5
Software Version 4.18.401.2
Kernel 3.1.10-g7f360be
Compilation number 4.18.401.2 CL231174 (i was touch that 7 times then i am supposed developer)
Hboot 1.72
What is perfect to me?
My final purppose is flash cyanogenmod 10.2.1, if can't do want to simply get root access.
(Other possibility to me is flash that one: http://forum.xda-developers.com/showthread.php?t=2640571
(i am not noob (of all) i was rooted some devices and flash two devices and don't have problem to try the harder method if someone know how to do what i want to do)
THANKS for the helper and sorry if my english isn't perfect!!
I think that the terga 3 is the international version
Sent from my HTC Butterfly s using Tapatalk
phonegeekjr said:
I think that the terga 3 is the international version
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
Thanks, but, then how can i root? i can't found help on the forum or on google...
First you are in the incorrect forum. Second once you are in the correct forum, search before posting. There are many ways to root. Just find one
Sent from my HTC Butterfly s using Tapatalk
phonegeekjr said:
I think that the terga 3 is the international version
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
i search and read, i found how to root and flash (and i understand and stand all) but don't work for me, i try to unlock bootloader but fail, i have my Unlock_code.bin, but can't charge that one (last step), i get a command not found problem, you are a senior user, just the user that i am searching to help me, probably you know long more that me but i know to RTFM, i first search the solution here (at&t and international one x forum) then on google, then on tons of sites, but yet don't found the solution, unlock the bootloader is supposed to be easy, the problem on that can be that i am using ubuntu 13.10 and not a windows... (it is why i was writing my pc SO)
thanks for you, but need personal help with that.
Please try to help me with an usual problems list, some ideas, some howto or almost redirect me to the correct link where someone have a similar problem that was solver, because, i can't found that.
Thanks other time , but sorry because don't is usefull to me search (i am yet searching) :crying:
We can't help you here, you need to ask in the right forum.
Sent from my Evita
Tegra3 is not the EVITA, its the ENDEAVORU.
To verify, you can boot into hboot and you will either see EVITA or ENDEAVORU.
For ENDEAVORU, its pointless to ask here. Any advice we give you would fail and possibly even brick your phone. You need to go here: http://forum.xda-developers.com/htc-one-x
redpoint73 said:
Tegra3 is not the EVITA, its the ENDEAVORU.
To verify, you can boot into hboot and you wier see EVITA or ENDEAVORU.
For ENDEAVORU, its pointless to ask here. Any advice we give you would fail and possibly even brick your phone. You need to go here: http://forum.xda-developers.com/htc-one-x
Click to expand...
Click to collapse
Hi I have a EVITA I just bought new two weeks ago, I updated with tha official rom downloaded from HTC support site, because I'm outside US. Then yesterday I updated with the official 4.2.2 and now I'm looking how to root this phone but I did not get nay post fro rooting this one running 4.2.2. I need to use the hotspot that it comes locked from at&t. Any idea, any help please??
---------- Post added at 08:40 AM ---------- Previous post was at 08:29 AM ----------
timmaaa said:
We can't help you here, you need to ask in the right forum.
Hi I have a EVITA I just bought new two weeks ago, I updated with tha official rom downloaded from HTC support site, because I'm outside US. Then yesterday I updated with the official 4.2.2 and now I'm looking how to root this phone but I did not get nay post fro rooting this one running 4.2.2. I need to use the hotspot that it comes locked from at&t. Any idea, any help please??
Click to expand...
Click to collapse
erickoncr said:
Hi I have a EVITA I just bought new two weeks ago, I updated with tha official rom downloaded from HTC support site, because I'm outside US. Then yesterday I updated with the official 4.2.2 and now I'm looking how to root this phone but I did not get nay post fro rooting this one running 4.2.2. I need to use the hotspot that it comes locked from at&t. Any idea, any help please??
Click to expand...
Click to collapse
You should have done some research before you installed the update, it patched the last exploit which means there's no way for you to unlock the bootloader or get root. You'll hav to wait and see IF a dev bothers to crack it on this device which is getting old now.
timmaaa said:
You should have done some research before you installed the update, it patched the last exploit which means there's no way for you to unlock the bootloader or get root. You'll hav to wait and see IF a dev bothers to crack it on this device which is getting old now.
Click to expand...
Click to collapse
Can I downgrade yo 4.1.1 and unlock the bootloader? I did not knew this patched
erickoncr said:
Can I downgrade yo 4.1.1 and unlock the bootloader? I did not knew this patched
Click to expand...
Click to collapse
No. This is why you wait and read before ANY OTA or RUU
Sent from my One X using Tapatalk
pandasa123 said:
No. This is why you wait and read before ANY OTA or RUU
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
Any idea or suggestion to unlock the hotspot. I just need the hotspot unlocked I don't need to be root or superiser. I just need the hotspot unlocked, I have tried with Foxfi but it just allow to tether by usb. Any idea for this? Thank you
No you can't without unlocking the unlocking the bootloader and rooting. It's a fairly well established (and discussed) fact that official updates patch root exploits, that's why it pays to research before doing something like that.
Sent from my Evita
timmaaa said:
No you can't without unlocking the unlocking the bootloader and rooting. It's a fairly well established (and discussed) fact that official updates patch root exploits, that's why it pays to research before doing something like that.
Sent from my Evita
Click to expand...
Click to collapse
Well I am just a normal phone user. I am not that expert on android facts. I did not know about this. So I have to wait to a coming solutions for this 4.2.2? Thanks
erickoncr said:
Well I am just a normal phone user. I am not that expert on android facts. I did not know about this. So I have to wait to a coming solutions for this 4.2.2? Thanks
Click to expand...
Click to collapse
If a dev has interest trying, he will find a way. But the thing is, most devs won't have interest. So sit tight and maybe send a bounty
Sent from my One X using Tapatalk
pandasa123 said:
If a dev has interest trying, he will find a way. But the thing is, most devs won't have interest. So sit tight and maybe send a bounty
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
I am not expert on this. Where can I send or contact a dev? Thanks you
erickoncr said:
I am not expert on this. Where can I send or contact a dev? Thanks you
Click to expand...
Click to collapse
You can't. If a dev wants to do it he will do it without any need for encouragement.
Sent from my Evita
erickoncr said:
Can I downgrade yo 4.1.1 and unlock the bootloader? I did not knew this patched
Click to expand...
Click to collapse
When its answered on here there is no method to unlock the bootloader, this includes downgrading. If there was a downgrade method, you would have been directed to that. Downgrading is not allowed on Android without root.
---------- Post added at 11:09 AM ---------- Previous post was at 11:07 AM ----------
erickoncr said:
Well I am just a normal phone user. I am not that expert on android facts. I did not know about this.
Click to expand...
Click to collapse
By buying a phone from a source other than your carrier, and also asking to mod the phone to work beyond its intended features (even though WiFi hotspot is intended to work on just about any carrier version except AT&T) you put yourself out of the category of "normal phone user" and it also means you have to do the proper research. Not knowing is no excuse.
I have a quick question about the Verizon variant of the HTC One M8. I just received my HTC One from Verizon. I quickly set to rooting and gaining S-Off. I was able to use Firewater and Weaksauce to gain root and S-Off really easily. Now, I am looking into flashing a different ROM, and here is where I am getting confused. I am wanting to use an AOSP ROM. However, there are very few AOSP builds in the Verizon HTC One forum. I did a bit of digging and I found that Cyanogenmod merged their releases into one device, uniquely named m8. So, my question: Will ROMs developed for just the HTC One M8 work for my Verizon M8? I don't want to flash a ROM and end up screwing something up (of course, I have made a stock rooted backup, but knowing my luck, something will happen and I will be SOL).
stompysan said:
I have a quick question about the Verizon variant of the HTC One M8. I just received my HTC One from Verizon. I quickly set to rooting and gaining S-Off. I was able to use Firewater and Weaksauce to gain root and S-Off really easily. Now, I am looking into flashing a different ROM, and here is where I am getting confused. I am wanting to use an AOSP ROM. However, there are very few AOSP builds in the Verizon HTC One forum. I did a bit of digging and I found that Cyanogenmod merged their releases into one device, uniquely named m8. So, my question: Will ROMs developed for just the HTC One M8 work for my Verizon M8? I don't want to flash a ROM and end up screwing something up (of course, I have made a stock rooted backup, but knowing my luck, something will happen and I will be SOL).
Click to expand...
Click to collapse
It MUST say that it is compatible. Some roms say "for all variants" which means all versions of the phone.
stompysan said:
I have a quick question about the Verizon variant of the HTC One M8. I just received my HTC One from Verizon. I quickly set to rooting and gaining S-Off. I was able to use Firewater and Weaksauce to gain root and S-Off really easily. Now, I am looking into flashing a different ROM, and here is where I am getting confused. I am wanting to use an AOSP ROM. However, there are very few AOSP builds in the Verizon HTC One forum. I did a bit of digging and I found that Cyanogenmod merged their releases into one device, uniquely named m8. So, my question: Will ROMs developed for just the HTC One M8 work for my Verizon M8? I don't want to flash a ROM and end up screwing something up (of course, I have made a stock rooted backup, but knowing my luck, something will happen and I will be SOL).
Click to expand...
Click to collapse
Wow, you're quite lucky to gain Firewater with a brand new device this late after it being fixed on new M8's. To answer your question, not all ROM's developed for the non carrier M8 will work on the carrier M8's (Verizon in this case), some will such as Cyanogenmod but not all. Usually the developers will say whether or not your carrier version (Once more, Verizon in this case) is compatible with their ROM, sometimes they don't but you can almost always find out by reading further into the thread as almost always someone else has asked. Oh and thank you's to @Quadrider10 for this part here(about it saying it's compatible), usually if it doesn't say it is compatible then it isn't but as I said you can always confirm it via replies to the thread or asking yourself.
Onto Cyanogenmod in specific, yes it will work perfectly on your device. I've personally tried it myself and honestly it is quite stable to be a "nightly". Anyways yeah it works and you'll be fine, just as always insure you have a working backup just incase.
Quadrider10 said:
It MUST say that it is compatible. Some roms say "for all variants" which means all versions of the phone.
Click to expand...
Click to collapse
That's what I thought, but I figured I would ask.
S1L3nTShaDoWz said:
Wow, you're quite lucky to gain Firewater with a brand new device this late after it being fixed on new M8's. To answer your question, not all ROM's developed for the non carrier M8 will work on the carrier M8's (Verizon in this case), some will such as Cyanogenmod but not all. Usually the developers will say whether or not your carrier version (Once more, Verizon in this case) is compatible with their ROM, sometimes they don't but you can almost always find out by reading further into the thread as almost always someone else has asked. Oh and thank you's to @Quadrider10 for this part here, usually if it doesn't say it is compatible then it isn't but as I said you can always confirm it via replies to the thread or asking yourself.
Onto Cyanogenmod in specific, yes it will work perfectly on your device. I've personally tried it myself and honestly it is quite stable to be a "nightly". Anyways yeah it works and you'll be fine.
Click to expand...
Click to collapse
You have no idea how shocked I was that it worked. I installed Sunshine and it took me to the payment screen, so I thought I would give it a shot. Took about two minutes and it threw up that beautiful "You are now S-Off" message. Reboot to bootloader and sure enough, it worked. It did prompt me to update on my first boot, but I declined it. I am assuming I either got old stock or Verizon was just being extra lazy.
Anyway, thanks again for the quick responses. Going to give CM11 a shot!
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.
Greetings....
Assembling a list of all RUU/firmware threads so that users no longer have to dig to find what's needed. Support for each will be found in the linked thread itself while general questions like "which one is applicable to my situation?" can be handled in this thread.
If you are S-ON
Your options are somewhat limited.. naturally.
RUU (4.4.2, 4.4.3, 4.4.4, 5.0.1, 6.0) in EXE/ZIP format
- http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
If you are S-OFF
RUU 6.0 zip thread
- http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972
RUU 5.0.1 (comes pre-rooted (EXE/zip support)
- http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
RUU 4.4.4 (comes pre-rooted) (EXE/zip support)
- http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914
RUU 4.4.3 (comes pre-rooted) (zip support)
- http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
RUU 4.4.2 (comes pre-rooted) (zip support)
- http://forum.xda-developers.com/showthread.php?t=2727831
Firmware only
4.4.3/4.4.4/5.0.1 Stock Recoveries, Stock kernels (boot), Stock ADSP, and many more....
- http://forum.xda-developers.com/showthread.php?t=2723159
4.4.2/4.4.3/4.4.4 Radios
- http://forum.xda-developers.com/verizon-htc-one-m8/development/radios-0-89-20-0222-t2824882
Note.... If you are needing to go back to locked and S-on for warranty purposes but are too leery to do it yourself, help is available via pm. Don't let your s/lock status from getting proper hardware RMA'S!
If you have bricked one beyond fixing and can't get it replaced, please consider donating it rather than throwing it in a desk drawer, shooting it, or whatever other crazy idea comes to mind. I can almost always put a bricked phone to good use.
Anyone who would like to use fastboot/adb for this device please use the following version fastboot/adb. It's HTC's own version. It works on pc's with less ram and it automatically breaks up a single zip into pieces for transfer. It also reflashes automatically if needed.
USE IT!
https://www.androidfilehost.com/?fid=95784891001612150
https://www.androidfilehost.com/?fid=95784891001612150
Looks good bro.
Great job!
Sweet! Thanks bro =]
Nice! I admit that the firmware was confusing for me on this phone, but thanks to dottat's posts, I figured it out.
This clears things up a lot and should help quite a few people.
Thanks!
xdadevnube said:
Nice! I admit that the firmware was confusing for me on this phone, but thanks to dottat's posts, I figured it out.
This clears things up a lot and should help quite a few people.
Thanks!
Click to expand...
Click to collapse
What was so confusing?
You are the MAN dottat!! Thanks!
Tigerstown said:
What was so confusing?
Click to expand...
Click to collapse
I managed to figure out the firmware largely due to dottat. There were multiple threads of various age, some with seemingly conflicting advice. This goes for most device forums I follow. There was no authoritative resource, IMO, until this thread.
The search feature was key, I am pretty thorough before embarking in firmware upgrades.
xdadevnube said:
I managed to figure out the firmware largely due to dottat. There were multiple threads of various age, some with seemingly conflicting advice. This goes for most device forums I follow. There was no authoritative resource, IMO, until this thread.
The search feature was key, I am pretty thorough before embarking in firmware upgrades.
Click to expand...
Click to collapse
@xdadevnube what could I do better in my OP of Vzw m8 firmware thread? I would like your input if you have ideas that would help make it easier for new comers to Xda? I would gladly make positive changes to my op to make it a easier an smoother experience. So feel free to tell me your ideas you/anyone might have that would help everyone..thanks I appreciate it.
Tigerstown said:
@xdadevnube what could I do better in my OP of Vzw m8 firmware thread? I would like your input if you have ideas that would help make it easier for new comers to Xda? I would gladly make positive changes to my op to make it a easier an smoother experience. So feel free to tell me your ideas you/anyone might have that would help everyone..thanks I appreciate it.
Click to expand...
Click to collapse
Your OP does contain the required information and instructions, so I can't really complain. One thing that could be helpful is to list the bootloader version info for each firmware release. You listed the most recent one right at the top of the thread, so at least it is easy to tell whether a given device is on the latest firmware or not. Because your thread is the main firmware thread, perhaps it would be best if the OP were organized into sections for 4.4.2, 4.4.3, and 4.4.4. It could be clarified which partitions are modified in the process, and whether the radios are affected. Install instructions could be put in their own spot.
These are only ideas! Also, your thread should probably be stickied. Thanks for all you do.
xdadevnube said:
Your OP does contain the required information and instructions, so I can't really complain. One thing that could be helpful is to list the bootloader version info for each firmware release. You listed the most recent one right at the top of the thread, so at least it is easy to tell whether a given device is on the latest firmware or not. Because your thread is the main firmware thread, perhaps it would be best if the OP were organized into sections for 4.4.2, 4.4.3, and 4.4.4. It could be clarified which partitions are modified in the process, and whether the radios are affected. Install instructions could be put in their own spot.
These are only ideas! Also, your thread should probably be stickied. Thanks for all you do.
Click to expand...
Click to collapse
hey whats up. I have made major changes to my firmware thread will you go check it out an let em know if i made it user friendly :highfive:
Firmware flash
Hello everyone. I am new to this Forum. I've only been here a few days. I have an Unlocked/S-Off Verizon HTC One M8 that I recently purchased from Ebay. I had a little trouble for a while when I first got it as it was running 4.4.2 and I took the OTA update to 4.4.3 and it messed up the phone. I didn't know it was Unlocked/S-Off'd. And the seller said it wasn't rooted any more. Well so now that I know it is even after running the Verizon RUU, I was wondering if I need to upgrade the firmware one upgrade at a time (meaning 4.4.3 and then 4.4.4)? Or can I jump to a 5.01 Lollipop ROM? I have TWRP installed and I used Flashify to install it. I'm hoping to use Flashify more for installing zips. Any help/suggestions would be greatly appreciated. Thank you....oh and I'm loving this M8!!!!
Tigerstown said:
hey whats up. I have made major changes to my firmware thread will you go check it out an let em know if i made it user friendly :highfive:
Click to expand...
Click to collapse
Looks good to me.
den_hart said:
Hello everyone. I am new to this Forum. I've only been here a few days. I have an Unlocked/S-Off Verizon HTC One M8 that I recently purchased from Ebay. I had a little trouble for a while when I first got it as it was running 4.4.2 and I took the OTA update to 4.4.3 and it messed up the phone. I didn't know it was Unlocked/S-Off'd. And the seller said it wasn't rooted any more. Well so now that I know it is even after running the Verizon RUU, I was wondering if I need to upgrade the firmware one upgrade at a time (meaning 4.4.3 and then 4.4.4)? Or can I jump to a 5.01 Lollipop ROM? I have TWRP installed and I used Flashify to install it. I'm hoping to use Flashify more for installing zips. Any help/suggestions would be greatly appreciated. Thank you....oh and I'm loving this M8!!!!
Click to expand...
Click to collapse
Rom and firmware are to separate things. You can flash straight to 4.4.4 firmware and then flash a lollipop Rom or any custom Rom.
Sent from my HTC6525LVW using Tapatalk
Firmware Updates
dottat said:
Rom and firmware are to separate things. You can flash straight to 4.4.4 firmware and then flash a lollipop Rom or any custom Rom.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Hello dottat. Thank you for replying to my question(s). Yes I know that a ROM is different than firmware. I was just wondering if I had to upgrade my firmware one update at a time or if I could just jump from 4.4.2 to say 5.0 or 5.01 so that if I wanted to I could put a custom ROM on my M8. I'm not actually sure how high the firmware upgrades go. I've only seen 4.4.4 as the highest so far.
den_hart said:
Hello dottat. Thank you for replying to my question(s). Yes I know that a ROM is different than firmware. I was just wondering if I had to upgrade my firmware one update at a time or if I could just jump from 4.4.2 to say 5.0 or 5.01 so that if I wanted to I could put a custom ROM on my M8. I'm not actually sure how high the firmware upgrades go. I've only seen 4.4.4 as the highest so far.
Click to expand...
Click to collapse
You can go straight to 4.4.4 and get crack flashing. No L firmware yet as we don't have L official.
Sent from my HTC6525LVW using Tapatalk
update process on factory unlocked VZW M8 used with GSM
Hi!
I am getting a verizon factory unlocked model and i am going to use it on a GSM network in india.Since its factory unlocked there should be no issues with the network. .however i had some doubts about the software updates. .so will i be able to receive and install updates normally without resorting to rooting the phone. .some people reported that they had an issue installing the update where it said that they have to be on CDMA or something like that. .Will i be able to overcome such issues by connecting to wifi?Is someone could shed a little light on how the update process works when used abroad with a GSM carrier it would be great!Thank you so much in advance!
balag59 said:
Hi!
I am getting a verizon factory unlocked model and i am going to use it on a GSM network in india.Since its factory unlocked there should be no issues with the network. .however i had some doubts about the software updates. .so will i be able to receive and install updates normally without resorting to rooting the phone. .some people reported that they had an issue installing the update where it said that they have to be on CDMA or something like that. .Will i be able to overcome such issues by connecting to wifi?Is someone could shed a little light on how the update process works when used abroad with a GSM carrier it would be great!Thank you so much in advance!
Click to expand...
Click to collapse
You will always be able to install the s-on ruu from here. The problem is that the latter versions of software while sim unlocked have proven very difficult to use on some carriers because you can no longer edit apn. You have to chose from pre-provided apn and thats only if they show up with your SIM card inserted.
You would be really wise to s-off the phone even if you don't root it as this would be the only way to downgrade if you ended up not having a workable situation on the newer software.