Related
ok seems theres an official update from HTC for our rogers phones anyone try it yet http://www.htc.com/ca/SupportDownloadList.aspx?p_id=270&act=sd&cat=2
Ooooh, eeenteresting....
Code:
Why is updating the software on your device recommended?
The ROM software update posted below provides several key enhancements for your HTC Dream:
-Improves the overall device functionality and stability
-Enables correct SMS timestamp [B]<<<<<<<<<<!!!!![/B]
-Enables Chinese character display for POP3 HTML Emails
-Corrects E-mail client exchange Issues
yes can it be timestamp fix heaven? lol.. just wondering if this is going to work for rooted or non 32a magic.. or both
The update pages says "HTC Magic (Rogers)" but when I stick in my S/N it says: Sorry, this software download is not suitable for your device. Bummer since my phone and box say HTC Rogers on them.
pcm2a said:
The update pages says "HTC Magic (Rogers)" but when I stick in my S/N it says: Sorry, this software download is not suitable for your device. Bummer since my phone and box say HTC Rogers on them.
Click to expand...
Click to collapse
ditto :/
i just got the S/N from the box as I didnt want to remove the battery.
yeah i noticed it also.. comes up when you select Rogers Magic.. but if you noticed in the notes.. some of which also posted above.. it says enhance dream isssues... will try my s/n and let you know
you can get the files from the rogers support page.. i used this link to get there http://www.androidincanada.ca/news/update-rogers-htc-dreammagic-android-timestamp-problem/
I have the direct link here:
http://downloads.rogers.com/wireless/products/htc/magic/RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe
Be careful as this update will more than likely install a Perfect SPL on your device. You will need to re-root your device after installing this. Could be a painful process.
I'm going to wait for somebody who knows what they're doing to remove the important bits from this update.
Cheers!
my thoughts exactly.. the way they have been putting the perfect spl on devices that didnt have it.... I tried it ( im running Jacheroski 2.7.4r2) and it didnt even recognize my phone. I was reading on the HTC site that you need HTC sync software first... thought that was for hero.. anyways.. have to run out for a bit will check back later... on a side note.. if this actually unroots your phone and puts the rogers apps back on .. couldnt someone tweak this up date and make it a restore rom?
I can confirm that it installs a 'Perfected SPL'.
Version 1.33.0010 to be exact.
Proceed with caution! I read through some posts on how to root these devices with 1.33.0010 and I really wouldn't want to have to do that.
I haven't installed the ROM image, and I won't.
After running the RUU (before you even click Next or accept the terms), you can find rom.zip in "%TEMP%\{F313B180-FF83-48A8-B925-E14312A5AFCB}\{50F2F878-636A-496F-A7CB-544C067E0C4B}"
I'm sorry if this isn't being asked in the correct place but as this thread is already discussing the new ROM update I was hoping that someone here could please tell me whether or not this ROM update would SIM relock a SIM unlocked Rogers Magic phone?
I am asking because I should be recieving my new unlocked Rogers Magic (that I am going to be using on AT&T) any day now and while I wouldn't mind updating it with the new ROM I really don't want to go through the expense and hassle of having to SIM unlock it when part of the reason I bought the one I did on ebay is because it is already SIM unlocked. Thanks in advance for any information on this.
coscom said:
I'm sorry if this isn't being asked in the correct place but as this thread is already discussing the new ROM update I was hoping that someone here could please tell me whether or not this ROM update would SIM relock a SIM unlocked Rogers Magic phone?
I am asking because I should be recieving my new unlocked Rogers Magic (that I am going to be using on AT&T) any day now and while I wouldn't mind updating it with the new ROM I really don't want to go through the expense and hassle of having to SIM unlock it when part of the reason I bought the one I did on ebay is because it is already SIM unlocked. Thanks in advance for any information on this.
Click to expand...
Click to collapse
I really doubt it will. I don't know exactly how SIM unlocking works, but this update shouldn't touch those settings.
Why run the Rogers update with all of it's restrictions and crappy software? Download and install any one of the dozens of better ROMs available in this forum.
First let me admit that I am a total NOOB with Android and even the idea of flashing custom ROMs on cellphones (the phone I am upgrading from is an 8525 and had an 8125 before that and the only time I remember flashing either was updating the official ROM to 6.0 off of HTC's site). I guess this makes me a little behind the times but my idea of customizing was installing programs like Pockets Plus and then Mobile Shell 3 because I'm not a programmer and was a little intimidated about cooking the ROMS.
That said I was thinking of running the stock ROM atleast for a little while to get an idea of just what I like and don't like about it and then being more knowledgeable when I research what ROM I should upgrade to? Is there a list of the ROMs and what their customizations are for the Rogers version? Do you have any advise on what ROM's I should look at and what the differences are?
I'm afraid that I will be somewhat overwhelmed with the number of choices to be made. Besides, I use my phone on my job so I can't risk it having issues or having to reinstall everything on a regular basis so continually flashing it with new ROM's as they come out may not be a logical solution for me. I think I'd rather end up with something stable and able to use all the programs, etc that I need for work and play. Anyways, any advice you can provide would be greatly appreciated.
Your best bet would be to start off by running the ROM that it comes with. If you've got problems with timestamps in the ROM, use a program called ChompSMS.
Read this forum, look for information on the 32A HTC Magic. That's the version you are getting. Learn as much as you can without changing your phone at all. Once you've got enough information start by 'rooting' your phone, then play around with some custom ROMs.
Lots to learn around here. Make sure you use the search function.
The following link was made by skittleguy to try to combine all compatible roms for Rogers. There have been quite a few changes to most of these ROMS but you can go to each original thread and read up on different ROMs and their advantages and disadvantages. I believe most of the original threads are being updated from time to time, but you can always just do a search for the name of the ROM.
http://forum.xda-developers.com/showthread.php?t=534464&highlight=repository
Personally if you want one that is stable and has all of its features working, I would go with Cyanogen's ROM v4.0.2 with Amon_RA'sv1.0.1 kernal. It is based of off MyTouch 3G. The link is below:
http://forum.xda-developers.com/showthread.php?t=544854
Having said that, there is one feature that I miss on this ROM, which is the smart dialpad.
T-mobile
Tsanger said:
The following link was made by skittleguy to try to combine all compatible roms for Rogers. There have been quite a few changes to most of these ROMS but you can go to each original thread and read up on different ROMs and their advantages and disadvantages. I believe most of the original threads are being updated from time to time, but you can always just do a search for the name of the ROM.
http://forum.xda-developers.com/showthread.php?t=534464&highlight=repository
Personally if you want one that is stable and has all of its features working, I would go with Cyanogen's ROM v4.0.2 with Amon_RA'sv1.0.1 kernal. It is based of off MyTouch 3G. The link is below:
http://forum.xda-developers.com/showthread.php?t=544854
Having said that, there is one feature that I miss on this ROM, which is the smart dialpad.
Click to expand...
Click to collapse
Is this official rom update compatible with tmobile sapphire?
Thanks
Disregard found the answer on the HTC website.
Not compatible for Tmobile.
Anyone out there have a suggestion on what to do to a out of the box Sapphire from T-mobile?
Thanks
david636 said:
Is this official rom update compatible with tmobile sapphire?
Thanks
Disregard found the answer on the HTC website.
Not compatible for Tmobile.
Anyone out there have a suggestion on what to do to a out of the box Sapphire from T-mobile?
Thanks
Click to expand...
Click to collapse
don't tmobile use 32B? i am fairly certain this is for 32A only.
How about nordic Magics :O
They are 32a... When will we see it >_<
My Desire is unbranded (not by me), so I don't get the OTA upgrades. I currently have 1.47.401.4 stick rom with sense 2.1 I would like to try a custom ROM to obtain sense 3.x. I prefer something close to the HTC stock rom.
I found some interesting ROMS in the dev forum, however most threads about roms do not mention if the new HBOOT is required or if the old HBOOT will also work. I currently have HBOOT 0.98.2000 (ENG).
No
10char.
Does upgrading to the new hboot makes any sense at all? According to their signatures many people in this forum have upgrade to their hboot. What's the advantage?
trifonius said:
Does upgrading to the new hboot makes any sense at all? According to their signatures many people in this forum have upgrade to their hboot. What's the advantage?
Click to expand...
Click to collapse
There is no advantage , in fact disadvantages.....
So don't bother upgrading yet.
I don't think it will ever be really required. Unless HTC decided to really put Sense on a Mc'Donalds diet of Tripple-Double-Quater Pounders ;-).
Could go either way though, the phone very rarely hits the 300mb cache quota, so I guess it could go either way.
ben_pyett said:
There is no advantage , in fact disadvantages.....
So don't bother upgrading yet.
Click to expand...
Click to collapse
Thanks for the replies. I am more confident now to try a custom rom on my DS.
Hi Guys,
I am running my phone on android 2.3.5 and hboot version 2.00.00.2. I was exploring on the net, how to root android but could just find that the hboot version on htc desire s has to be 0.98.0000 which is suported on revolution.io website. Is there any other way to s-off my phone to go for rooting.
Thanks in advance for your help.
Sent from my HTC Desire S using Tapatalk
unlock your bootloader via htcdev site
and than just flash superuser from recovery
Hi guys, I don't mean to hijack the thread, but just to avoid making an unnecessary one, I thought I'd ask my question here.
I've been looking at htcdev, and I understand that it doesn't officially support the ds, but it works. It's probably a stupid noob question, but assuming I select 'desire' on HTC's drop down menu, how imperative is it that I get the exact RUU? There isn't one listed for my provider (o2 uk). Googling, and searching on a few forums has turned up nothing, but my software details are:
2.3.5 with sense 3.0
Soft. Num. 2.10.401.8
I was under the impression the 3 digit string pertained to the provider, and o2 tends to use x.xx.701.x.
Is it completely necessary to find a specific RUU, or is the region the only real important factor? Would the HTC eu one be suitable?
Thanks in advance for your help guys. Never got.round to rooting my old desire, but 'upgraded' to the s before I realised it wasn't as easy to root!
Sent from my HTC Desire S using XDA App
Scrap that.....found it! Must've been search result blind in the end! Sorry for the interruption guys!
Peas.
Sent from my HTC Desire S using XDA App
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
Hi everyone!
Just bought a new HTC One SV which is branded by Vodafone Spain. I unlocked the phone by using an unlock code and now I want to install a stock ROM, either world or european ROM, but I can't seem to find anything for 4.2.2.
Would greatly appreciate any help!
LE: Apologies, but I forgot to mention that the phone is S-ON.
Nihtilan said:
Hi everyone!
Just bought a new HTC One SV which is branded by Vodafone Spain. I unlocked the phone by using an unlock code and now I want to install a stock ROM, either world or european ROM, but I can't seem to find anything for 4.2.2.
Would greatly appreciate any help!
LE: Apologies, but I forgot to mention that the phone is S-ON.
Click to expand...
Click to collapse
Welcome to the community, please, for future reference, refer all questions you may have over at 'HTC One SV Q&A, Help & Troubleshooting'.
Your phone is currently stock right now, so may I ask why you would want to install another stock Rom?
Sent from my C525c using Tapatalk
Modding.MyMind said:
Welcome to the community, please, for future reference, refer all questions you may have over at 'HTC One SV Q&A, Help & Troubleshooting'.
Your phone is currently stock right now, so may I ask why you would want to install another stock Rom?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Apologies, noted.
The phone is branded by Vodafone and has tons of apps that I'll never even touch. Just want to put a stock ROM, without any other 3rd party apps. Moreover, after 4.2.2 was released for this model had to wait a bit over two months to get the update.
Nihtilan said:
Apologies, noted.
The phone is branded by Vodafone and has tons of apps that I'll never even touch. Just want to put a stock ROM, without any other 3rd party apps. Moreover, after 4.2.2 was released for this model had to wait a bit over two months to get the update.
Click to expand...
Click to collapse
Ah, so in lamen terms, you want a Rom which has been made by another Individual, but has already removed all the bloatware. Is this correct?
Sent from my C525c using Tapatalk
Modding.MyMind said:
Ah, so in lamen terms, you want a Rom which has been made by another Individual, but has already removed all the bloatware. Is this correct?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
No. In other words I want a stock HTC ROM, which isn't branded.
Nihtilan said:
No. In other words I want a stock HTC ROM, which isn't branded.
Click to expand...
Click to collapse
Its the same thing, unbranded phones, from my experience, do not contain a bunch of bloatware (unwanted apps) which normally comes from the company provider after given to them by HTC. If from HTC directly, its strictly what they produce and offer without the extras from other companies. I looked at @old.splatterhand index, and I see only two Roms available which are 4.2.2. Now whether they come with or without the bloatware I cannot say, as I have a K2_CL device. Though, I do believe that the 4.2.2 K2_UL does not contain any bloatware from going off the top of my head - because o have used it before in the past to adapt it for use on our K2 variant.
old.splatterhand, you are more familiar in this area than myself since I focus more on Boost and Cricket. Feel free to chime in and correct me where correction is due buddy.
Sent from my C525c using Tapatalk
We need to be more clear, what @Nihtilan exactly wants.
The 422 roms (k2u & k2ul) are both unbranded, no provider apps and something like this.
They can be flashed also S-On, but firmware files are also needed to flash, if the device wasn't on 422 already.
Or the other way is a completely unbrand:
S-Off -> SuperCID -> hboot downgrade -> EU unbranded RUU.
old.splatterhand said:
We need to be more clear, what @Nihtilan exactly wants.
The 422 roms (k2u & k2ul) are both unbranded, no provider apps and something like this.
They can be flashed also S-On, but firmware files are also needed to flash, if the device wasn't on 422 already.
Or the other way is a completely unbrand:
S-Off -> SuperCID -> hboot downgrade -> EU unbranded RUU.
Click to expand...
Click to collapse
Thanks for the reply, and yea, I didn't bother to include the firmware info because he had already mentioned that he received the 4.2.2 update even though it took him a while to get it. I figured it would had been too much info and probably would have caused some confusion. I appreciate the timely response.
Sent from my C525c using Tapatalk
Modding.MyMind said:
...I didn't bother to include the firmware info because he had already mentioned that he received the 4.2.2 update even though it took him a while to get it...
Click to expand...
Click to collapse
Lol, i overlooked it, otherwise i would not mention it, too lol
old.splatterhand said:
We need to be more clear, what @Nihtilan exactly wants.
The 422 roms (k2u & k2ul) are both unbranded, no provider apps and something like this.
They can be flashed also S-On, but firmware files are also needed to flash, if the device wasn't on 422 already.
Or the other way is a completely unbrand:
S-Off -> SuperCID -> hboot downgrade -> EU unbranded RUU.
Click to expand...
Click to collapse
That's exactly what I want to do.
I would like to put either a 4.2.2 World or Europe unbranded RUU.
How do I do that? Is it possible without S-OFF?
PS: Apologies for the late reply.
LE: I remember when I had a Wildfire S, when I unbranded the phone I just had to create a gold card and put the RUU on it and it was very easy. I reckon things have changed a bit in the meantime..
So thats the way to go: S-Off -> SuperCID -> hboot downgrade -> EU unbranded RUU.
And no chance without S-Off.
Use the search (inside the HTC ONE SV Forum) with the words "hboot downgrade". There should be many results that describe the way more detailed.
This might be a noob question, but what's the difference between K2_U, K2_UL, etc.? Also, could you please direct me to some threads? Had a look through quite a few and I'm not really sure where to start.
Thank you.
LE: Ok, did a bit of research and my phone is K2_U. Also, I couldn't find S-OFF for 4.2.2.
Get S-Off with http://rumrunner.us (Universal version).
Get SuperCid with fastboot command:
Code:
fastboot oem writecid 11111111
Go to this thread, read and follow the instructions there.
All done!
Thank you very much for your help!
You're welcome.
Glad, that it worked for you.