Hi all have got a quick question here. With the new HTC HD2 Rom available from htc site, why can't i download it to my T-mobile phone. It keep telling me that it is not suitable for this device. And is there a way to get around this so i can download the new rom? Need any help i can get please.
buddaking said:
Hi all have got a quick question here. With the new HTC HD2 Rom available from htc site, why can't i download it to my T-mobile phone. It keep telling me that it is not suitable for this device. And is there a way to get around this so i can download the new rom? Need any help i can get please.
Click to expand...
Click to collapse
Wrong thread, should post in ROM section.
You have a branded phone, these are official ROMS for unbranded phones, wayt till TM provides theire new ROM based on an official HTC ROM.
Or HSPL your phone (void warranty) and flash away
Had the same problem and flashed the latest ROM using SSPL. It was quite painless and the HD2 works fine. Do a search for SSPL or HSPL in this forum and all will be explained.
good luck
Why is it necessary to download the new rpm. I have the same problem. Just curious. My phone seems to be working nicely.
Use the below link to get the ROM and then grab a Goldcard and put the ROM on. Or you can follow the HSPL route instead if you prefer.
Will probably invalidate any TMo warranty you may have so be aware.
http://94.136.51.200/download/RomCo...Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe
I start this thread because this question has bother me for a month, since i had the Titan.
We all know that next gen windows Phone will use the NAND Flash Memory. So the first thing i know, there is no Gold Card anymore.
I used to use the Gold Card Technique to install the EU Official Windows Mobile ROM for the Asia HD2, so i am kinda familar with it.
So now i have the HTC Titan from UK , and i am not really pleased with the British Accent on it. So i am looking for the answer if i can install the Official ROM of AT&T version for it, and most important thing: be able to receive the official update for it.
Since it is NAND Flash Memory, and bootloader will cancel the install from the start, i am looking for anyone who have the answer.
And there are many custom ROM out there, but my main concern will it be able to receive the update?
Thanks.
PS: my bad i mean Region, not "religion".
Moved to WP7 Q&A
No questions in the development section please.
I have changed the title for you, dont want any confusion there
Take it easy
O_G
My bad, i just realized it right after i hit the post message button. Thanks for sorting it.
Sent from my Eternity using Board Express XDA
Look like all my question turn out to be impossible to answer :\
Strike_Eagle said:
Look like all my question turn out to be impossible to answer :\
Click to expand...
Click to collapse
Maybe no one here tried it yet. But if I were you, I wouldnt mess my ROM. About custom ROM, that depends. I remember one of DFT that was able to receive update. Dont know about the new ones, but if you do receive updates from MS, you certainly will not receive OEM updates, like HTC releasing the drivers for internet tether.
Hey guys,
Been reading around on here and seen that pretty much everyone has the 2.3.5 with sense 3 update.
My girlfriend recently got a Desire S on T-Mobile UK and she is still on 2.3.3 sense 2.1 with no sign of any sort of update, I have read a few threads round here to try to find an RUU or w/e but I can only find ones that are for other countries or operators.
Can someone point me to an RUU or guide me through obtaining the update?
Any help is greatly appreciated!
Thanks
Ian
Is it s-off or unlocked through HTC Dev. Here are the collection of stock Roms http://forum.xda-developers.com/showthread.php?t=1002506
If the stock ones don't work then look at S-offing your device.
We haven't done anything to it really since she got it, id rather keep it that way to be honest.
Current software version is "1.47.110.3 CL78999 release-keys" is this tmob specific software? Are we more likely to get the sense 3 update if I flashed a WWE RUU?
Thanks
Hi, I'm sorry but I don't know. T-mobile are a joke as far as updates are concerned. I take it you have tried to update through your phone ie, check for updates in settings.
The first thing I do when I get a new HTC is change the T-mobile softare for one of the custom Roms, they are far better and don't have the T-mobile crap on them.
Take a look through the t-mobile forum and you will see there are plenty of pissed off people waiting http://support.t-mobile.co.uk/discussions/index?page=forums&topic=80101915a8144e01337e648aca007a7d
Good luck
Okay, thankyou for taking the time to reply, I will maybe wait a while then look into the HTC DEV unlock method and just flash an untouched 2.3.5 on there
I would give it some consideration, the custom Roms are far more stable in my opinion and give you a lot more options.
Sorry I couldn't help more.
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
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!