Develop Bugs

T-Mobile G2 RUU update

http://support.t-mobile.co.uk/RUU_Hero_T-Mobile_UK_2.73.110.26_release_signed_NoDriver.zip

It seems to be a older build, 110 vs 405
also once installing im having issues using flashrec to installed a patched recovery image

How does It differ to a normal 2.73 Rom?

lloydsparkes said:
It seems to be a older build, 110 vs 405
Click to expand...
Click to collapse
No it isn't - the 2.73 is the build number, the rest just indicates operator and region.
Regards,
Dave

Hi, whats the radio version in this ROM?
Thanks

Interesting that this update arrives at the same time t-mobile are rolling out Android 1.6 OTA to USA G1 owners ...
Could this update be Sense UI on top of Android 1.6?

Its not, its a 1.5 system

I can confirm issues with flashrec.
Installing custom recovery from adb shell is not working either..

download now also available here:
http://forum.xda-developers.com/showthread.php?p=4525584

Just installed.
Firmware 1.5
Baseband version 63.18.55.06FU_6.35.07.08
Kernel version 2.6.27-00078c992
Build number: 2.73.110.26 CL#69351 release-keys
Software version: 1.0.0.A6288

Radio version: 63.18.55.06FU_6.35.07.08
Cheers,
BS...

extracting the rom images
lloydsparkes said:
I
also once installing im having issues using flashrec to installed a patched recovery image
Click to expand...
Click to collapse
as i suspected it might, sounds like it ships a kernel that fixes the one-click-root hole, and it replaces the recovery rom image.
Anyone know how to extract the rom images from that windows executable?
i want to mess about a bit and install only parts of it from linux.
Searching the forums the closest i can find is a suggestion of using winrar, but i had someone try that on their windows box and it doesnt work.
or as a fall back, does anyone know if someones managed to do a nandroid backup of a freshly upgraded g2. (after rooting it the hard way presumably)

Paul @ Modaco twittered that he'd root and repack the T-Mobile UK update on Thursday (i.e. tomorrow).
Regards,
Dave

I have extracted the Rom Images
Run the RUU then leave it running
then Start-> Run -> %TEMP%
then look through the folders untill you find one with adb in (search) this has a rom.zip file.

So the radio rom is 63.18.55.06FU_6.35.07.08.
But isn't this version supposed to freeze T-Mobile UK HSDPA?!

wywywywy said:
isn't this version supposed to freeze T-Mobile UK HSDPA?!
Click to expand...
Click to collapse
'supposed' is an odd word to use.
I don't know how many people have reported the freezing on HSDPA, however I have not had any.
I only installed the new radio earlier today, but I'm not having eny problems with HSDPA, I even downloaded a 200mb file and whatched the whole process just to see if it hung.
It didnt.
I do not know for sure whether the signal is better, but it's definately not worse.
I'll post again tomorrow when I've tested out the signal and internet a bit more.

hi, when i try to flash this rom i've got this message "erreur 131: erreur client id"????
somebody can help me???
thank you guys;-)

i think that means it is not meant for your device...do you have a t-mobile branded uk hero?

foxmeister said:
Paul @ Modaco twittered that he'd root and repack the T-Mobile UK update on Thursday (i.e. tomorrow).
Regards,
Dave
Click to expand...
Click to collapse
Just got to wait for this then......

lloydsparkes said:
Just got to wait for this then......
Click to expand...
Click to collapse
If you've already applied the T-Mobile UK update via the RUU, you're probably out of luck, as it seems it replaces your recovery image with one that can't currently be replaced.
Regards,
Dave

[ROM] Official G2/DZ shipped ROMs

Now,I have collected most original/official RUU.exe files for Desire Z and
Vision/G2 TMOUS zip files for the Users,Devs or Mods.
Uploaded all to "shipped-roms.com":
LINK http://shipped-roms.com/index.php?category=android&model=Vision
So we have all files collectively and don`t need to look for it.
Files which are available:
RUU_Vision_HTC_WWE_1.82.405.1_R_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_168383_signed.exe
RUU_Vision_Orange_FR-B2B_1.85.73.2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_170528_signed.exe
RUU_Vision_HTC_ARA_1.83.415.2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_168396_signed.exe
RUU_Vision_Hutch_AUS_1.85.861.3_Radio_12.28h.60.140f_26.06.02.27_M_release_172438_signed.exe
RUU_Vision_BellMobility_WWE_1.34.666.1_Radio_12.28b.60.140e_26.03.02.18_M2_release_154437_signed.exe
RUU_Vision_HTC_WWE_1.72.405.2_R_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163285_signed.exe
RUU_Vision_HTC_WWE_1.72.405.2_Radio_12.28e.60.140f_26.04.02.17_M2_release_160660_signed.exe
PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
Vision_TMOUS_1.12.531.0_Radio_12.18.60.05P_26.01.00.17_M2_144460.zip
RUU_Vision_hTC_Asia_WWE_1.34.707.3_Radio_12.28b.60 .140e_26.03.02.18_M3_release_154628_signed.exe
RUU_Vision_HTC_Egypt_1.72.466.4_Radio_12.28e.60.140f_26.04.02.17_M2_release_160882_signed.exe
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe
RUU_Vision_HTC_WWE_1.22.405.1_Radio_12.26.60.1301_26.02.00.24_M2_release_151197_signed.exe
RUU_Vision_HTC_WWE_1.31.405.1_Radio_12.28a.60.140e_26.03.02.08_M_release_153504_signed.exe
RUU_Vision_HTC_WWE_1.34.405.4_Radio_12.28b.60.140e_26.03.02.24_M_release_155297_signed.exe
RUU_Vision_hTC_Asia_HK_CHT_1.34.708.3_Radio_12.28b .60.140e_26.03.02.18_M2_release_154602_signed.exe
RUU_Vision_hTC_Asia_India_1.34.720.3_Radio_12.28b. 60.140e_26.03.02.18_M2_release_154620_signed.exe
RUU_Vision_hTC_Asia_TW_1.34.709.3_Radio_12.28b.60. 140e_26.03.02.18_M2_release_154597_signed.exe
RUU_Vision_HTC_WWE_1.34.405.3_Radio_12.28b.60.140e_26.03.02.18_M2_release_154596_signed.exe
Click to expand...
Click to collapse

Theres no place like 127.0.0.1

Jobehonda said:
Theres no place like 127.0.0.1
Click to expand...
Click to collapse
everybody has 127.0.0.1
I guess he wants to use it as placeholder for the real IP...

I know garbage i was making a reference to theres no place like "home" or in this sense, 127.0.0.1 i didnt have the heart to tell him any other way. lol
http://www.thinkgeek.com/tshirts-apparel/unisex/generic/5d6a/

Hm,using this programm:
http://downstairs.dnsalias.net/homeftpserver.html
How you can get access,have done something wrong

How'd you host the files on my own computer
Also you need to give us an IP address we can access outside of your LAN, dont give us a number starting with 127, 10, or 192, those are all local. I recommend DynDNS or No-IP for dynamic IP updaters. if you need help PM me
I PM'd you

Test again:
Server: gani.dyndns-home.com
Port: 21 (if needed)

UPDATE:
All files now available at "shipped-roms.com".

Missed
RUU_Vision_HTC_WWE_1.34.405.3_Radio_12.28b.60.140e_26.03.02.18_M2_release_154596_signed.exe
Now added too

Deserves a bump.
Thanks, I've been using this thread quite often (I stupidly delete ROM's after I extracted stuff I need so I need to re-download them once the extraction business is on again... ). Having to look for it on page 3 or 4 is horrible so here we go, I get it back on the front page.

Link no longer works.

Link from first post? (shipped-roms.com)
I have no problems!

Can someone please explain to me and I'm sure others would appreciate, what is all the wwe ruu tmous stuff mean. I look at that list and barely have a clue what I should be flashing if I want the latest, what belongs to what provider etc. Also if your s off aren't there quite a few of these that if you flash you will semi brick?
I have tried finding a breakdown of all this info and had no such luck. If someone does not feel like explaining all that can u just tell me the latest tmobile released rom and if its safe to flash with s off and eng bootloader? Thank u.
Sent from my HTC Vision using XDA Premium App

does anyone here have the original belgian rom RUU?
Either 1.72.1100.x or 1.83.1100.x

I just got a replacement G2 and noticed i have a version number not listed in this thread
I have:
1.22.531.5 CL277427
Wondering before i root, if I can make an image or copy the rom into a zip file for anyone???

xsteven77x said:
Can someone please explain to me and I'm sure others would appreciate, what is all the wwe ruu tmous stuff mean.
Click to expand...
Click to collapse
WWE = World Wide English (?), means about as much as "global release". A version of a ROM which is released to one could say "unbranded" devices coming from HTC directly, intended for worldwide use. No G2, no Vodafone, just pure HTC.
RUU = Rom Update Utility, a Windows OS executable file which flashes a ROM onto your device, partially or fully. A so called "official RUU" is usually a ROM updater coming from HTC, still in it's untouched state, unmodified, means no root pre-included, no locks removed, no traps defused, just pure HTC.
TMOUS = T-Mobile USA. Questions?
I look at that list and barely have a clue what I should be flashing if I want the latest
Click to expand...
Click to collapse
Technically quite incorret but it will do as an explanation: we all have the same devices, they are just distinguishable by the software put on them. Since the hardware is the same, all devices worldwide will run every "Vision" ROM there is. So basically, as normal in IT, take the one with the highest number and youre good to go 1.34 is older than 1.72 is older than 1.84 is older than (...). The stuff after 1.34.xxx is for the "release/sales region" a ROM is intended for. 405 for example is more or less western europe, so ROMs released for the german/austrian/swiss/whatever market are 1.xx.405.z ROMs.
what belongs to what provider etc.
Click to expand...
Click to collapse
Doesn't matter, a Vision is a Vision. A "provider ROM" just means it will have some provider specific junk loaded as opposed to a "clean" HTC ROM. Exception: G2 vs DesireZ. G2 is "pure" Android (with T-Mo junk) where as DesireZ get Sense from HTC.
Also if your s off aren't there quite a few of these that if you flash you will semi brick?
Click to expand...
Click to collapse
Semi brick? If you got a semi brick unbrick it by flasing something which works. Beauty of flashing HTC devices. Ever heard of locked Motorola bootloaders? A pain in the hole, and very much at that...
...and if its safe to flash with s off and eng bootloader?
Click to expand...
Click to collapse
S-OFF and ENG Bootloader means your device is basically (very stupid things to do excluded) bomb proof. In this combination there is almost always a way to get it back to a working state. One thing I would consider: I'd take a modified, pre-rooted ROM, an "official" ROM might close a loophole used to root and crack and hack the device.
Mikey1022 said:
Wondering before i root, if I can make an image or copy the rom into a zip file for anyone???
Click to expand...
Click to collapse
You'd need a custom recovery for that. And without ROOT you can't load a custom recovery. Hmm... you could temp-root, put recovery on, factory reset (wipe temp root stuff off device), pull a backup, and then perm-root. This way you'd get a quite clean backup. Anyone disagree?

I'm not able to download a single file, either download never starts or it just stops randomly at any point during the download have not been able to download more than 50mb

This may be obvious but which country is AUS as in RUU_Vision_Hutch_AUS_1.85.861.3_Radio_12.28h.60.14 0f_26.06.02.27_M_release_172438_signed.exe ?

Australia....
Desire Z - with XDA Premium

Thank you, ok so what is XDA premium?

[Q] Questions about curious debranding results

Last night I managed to de-brand my HTC Wildfire from Vodafone to HTC Generic firmware downloaded from shipped-roms.
The procedure seems to be a success, but I noticed something really weird - my Vodafone ES rom was version 2.24, while the HTC one is version 2.22. I checked for an update from the phone after that but no updates were available.
Is this the latest official version? (I know of some cases where companies change the version number just because they added their own apps/logos in the phone)
The procedure I followed was:
Install HTC Sync
Create a Gold Card
Downloaded the latest WWE rom I found on shipped-roms (RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe)
Ran the installer and waited for it to finish
Thanks in advance for any replies.
P.S. using gold card doesn't root my phone right? (I don't want it to be rooted at this point, so I thought I'd ask)

It's normal. All different carrier branded ROM's have their own version numbers, and the WWE ROM has the lowest build number among these (i.e . 2.22), Most probably, since it was the first one to be released.
And no, you are not rooted, so don't worry about it.

3xeno said:
It's normal. All different carrier branded ROM's have their own version numbers, and the WWE ROM has the lowest build number among these (i.e . 2.22), Most probably, since it was the first one to be released.
And no, you are not rooted, so don't worry about it.
Click to expand...
Click to collapse
Oh pretty neat I guess.
Any recommendations on which ROM should I keep?
In the past I was always advised to use stock firmware on smartphones, but not sure about the case with modern ones.

Since you don't want to have root at this point of time, you will have to stick with the Stock ROM. If it works fine for your needs, I would say go for it, but, if you feel the need to experiment / mod, then definitely give ROMs like Cyanogenmod 7 and other Gingerbread a try. Or, if so inclined, you can go for Sense based ROMs as well, which look and feel like the Stock ROM, but with various tweaks, improvements, features and optimizations.

S-Off might be difficult - but maybe we can work around

Hi,
nobody knows me, thats just fine . What I m currently doing is I m trying to find out if there´s a suitable software-way to work around that messy S-Off problem.
Whats the idea?:
The idea is quite simple, the current hboot 1.31 already supports all branded devices.
Seriously?
Yea, seriously.
If you unpack the current hboot and open it using a text-editor like Windows editor you´ll find the following lines
NORMAL RECOVERY_UPDATE_RADIO RECOVERY_UPDATE_HBOOT RECOVERY_UPDATE_ZIP RECOVERY_UPDATE_COMBO HTCBL BOOTPROFILING SDUPDATE RECOVERY_MANUAL POWERTEST RECOVERY_POWERTEST OFFMODE_CHARGING RECOVERY_OFFMODE_CHARGING MFGKERNEL MFGKERNEL_DEBUG MFGKERNEL_58 SECURITY_RESET REBOOT_BOOTLOADER POWER_DOWN HBOOT_USB FACTORYRESET SYSINFO IMGCRC NORMAL_DIAG RAMDUMP2EMMCDUM RAMDUMP2USB RAMDUMP2SD 9KRAMDUMP 9KRAMDUMP2SD MODEMPATHON MODEMPATHOFF LOGGERSETTING LOGGERON LOGGEROFF LOGGERTOINTERNAL LOGGERTOSD DIAG MODEM_CALIBRATION Dopod-China DOPOD701 Open-Channel HTCCN701 CT HTCCN702 CU HTCCN703 CMCC-TD HTCCN704 TMUS T-MOB010 TMD T-MOB101 TMA T-MOB102 TMNL T-MOB003 TMCZ T-MOB004 TMUK T-MOB005 TMHR T-MOB006 TMH T-MOB007 TMSK T-MOB008 Era T-MOB009 TMMK T-MOBL11 VODA-UK VODAP001 VODA-Germany VODAP102 VODA-Italy VODAP405 VODA-SFR VODAP203 VODA-Spain VODAP304 VODA-Netherland VODAPE17 VODA-Ireland VODAP019 VODA-Greece VODAP006 VODA-Portugal VODAPD18 VODA-Swisscom-WWE VODAP015 VODA-Swisscom-DE VODAP110 VODA-Swisscom-FR VODAP212 VODA-Swisscom-IT VODAP416 VODA-Australia VODAP021 VODA-New-Zealand VODAP022 VODA-Mobilkom VODAP120 VODA-Proximus VODAP024 VODA-TR VODAPM27 ORANGE-French ORANG202 ORANGE-UK ORANG001 ORANGE-ES ORANG309 ORANGE-BE ORANG012 ORANGE-PO ORANG008 ORANGE-CH-FRA ORANG203 ORANGE-CH-GER ORANG104 ORANGE-SK ORANG006 ORANGE-PL ORANGB10 ORANGE-AT ORANG113 GOOGLE GOOGL001 TELEF-Spain TELEF301 TELUS TELUS001 DCM DOCOM801 ATT CWS__001 Brightstar-SPA BSTAR301 Brightstar-PTB BSTAR502 VIRGIN-UK VIRGI001 O2-UK O2___001 HTC-Czech HTC__C24 HTC-Denmark HTC__F08 HTC-Norway HTC__H10 HTC-Sweden HTC__G09 HTC-Poland HTC__B25 HTC-Russia HTC__A07 HTC-Turkey HTC__M27 HTC-GCC HTC__J15 HTC-Australia HTC__023 HTC-Singapore HTC-FRA HTC__203 StarHub-Singapore VODA-Africa-South AirTel-India TIM-Italy TIM__401 H3G-Italy H3G__402 Optus-Australia OPTUS001 Hutch-Australia HUTCH001 SMC-Voda-HK SMCVD001 Chunghwa-Taiwan CHT__601 Rogers ROGER001 HTC-EastEurope HTC__032 HTC-GER HTC__102 HTC-ITA HTC__405 HTC-Dutch HTC__E11 HTC-Nor HTC__Y13 HTC-WWE HTC
You see - all there.
So, Vodafone and all the others can stopp telling is their branded devices are not yet supported - bull****.
So, I´m trying to find a way to edit files in a way that the installer believes the currently plugged device is supported - even in case its got a totally different CID.
Dunno if this will work in any possible way...but hey, at least a try.
Regards
*Edit: If anyone found an HOX RUU from Asia for JB - that would be quite helpful.

Of course it supports every single HTC One X, regardless of CID, but:
If you change any file the signature will be broken, will not work. If you look at the header of the zip file in a hex editor, there is a 256-byte long signature that no one knows how to decrypt.
(I'm talking about the firmware.zip)

tomascus said:
Of course it supports every single HTC One X, regardless of CID, but:
If you change any file the signature will be broken, will not work. If you look at the header of the zip file in a hex editor, there is a 256-byte long signature that no one knows how to decrypt.
(I'm talking about the firmware.zip)
Click to expand...
Click to collapse
Well...yea...so I tried to change some files in the temp folder of windows during the installation - and that worked. Dunno what I can make of that but I ll keep u updated. So much for now:
Current version: 2.xxx
Version to install: strange asian signes
Ok.
Finished - device not bricked.
I keep working
*Update: Hmpf...not working the way I hoped it would. I can install using the stock ruu with hboot 1.31....but its still not starting :/

I don't mean to be a downer, and good on you for giving it a go. But this has already been tried long ago.
Any modification you make will break the signature. The only way to get around it is to decrypt the signature so we can sign whatever zip files we want. Then we could flash an S-OFF HBOOT.

Illux said:
Well...yea...so I tried to change some files in the temp folder of windows during the installation - and that worked. Dunno what I can make of that but I ll keep u updated. So much for now:
Current version: 2.xxx
Version to install: strange asian signes
Ok.
Finished - device not bricked.
I keep working
*Update: Hmpf...not working the way I hoped it would. I can install using the stock ruu with hboot 1.31....but its still not starting :/
Click to expand...
Click to collapse
hello your hox has the cid VODAAP102???
you can make a small guide on how to do?

Sentinel196 said:
I don't mean to be a downer, and good on you for giving it a go. But this has already been tried long ago.
Any modification you make will break the signature. The only way to get around it is to decrypt the signature so we can sign whatever zip files we want. Then we could flash an S-OFF HBOOT.
Click to expand...
Click to collapse
Why is everyone so quick to shut down new attempts to achieve S-Off? The Church of Xmoo will only get you so far, especially when Xmoo doesn't even have a HOX any more.
Sent from my HTC One X using Tapatalk 2

Exactly 1 person attempting something is better than everyone just keeping quiet and whining about no S-Off.

New attempts with old techniques is not new attempts, it's confirming what we already know.
I'm not sure anybody would complain about new threads with new information or actual progress.

Exactly.
All I'm saying is that this idea has already been tried and verified as not working, and pointing this out so no-one wastes time trying something old when they could be trying something new.

Well he is trying .. Let him do it. No one can directly go to advance mathematics until he learns the basics.

Forget the zip file...
The 'new' bootloader is signed, and the 'existing bootloader' will verify the signature on the phone itself, before reflashing itself.
Sadly, and 'hack' on the PC side is wasted... a fully intact 'signed' package has to be sent to the phone/device.
The zip is irrelevant, it's opened by the RUU and the contents sent to the device in individual signed packages.
The procedure goes like this:
RUU / PC unpacks the zip.
The components of the zip are sent one by one to the phone ... i.e. Bootloader, Recovery, ROM etc.
Some of those components, particularly bootloader are signed, and the signature is checked on the phone.
You can change the files as much as you like on the PC... modifying the ROM image should still work (but of course, you'll create a corrupt ROM).
If you try to change the bootloader package (which is signed) then it will be rejected by the phone. A single byte change will result in an entirely new checksum / signature.
To generate the correct signature you need two things....
1) The algorithm for generating a new signature for the modified file
2) The 'key' which is used to encrypt the data (top secret!)
Statistically, it would take many years to 'brute force' guess the key, and you'd probably ruin your handset flashing it so many times too.
They key isn't likely to be leaked.
So, there's another way:
HTC allow some service centers to reflash the devices, but this requires special hardware and software that's not easy to replicate and hasn't been leaked yet. The presence of this hardware will 'permit' full reflashing of the device, and therefore S-OFF.

Have you guys see this?
--see below--

farhanito said:
Have you guys see this?
http://forum.xda-developers.com/showthread.php?p=5
Click to expand...
Click to collapse
broken link

Sentinel196 said:
broken link
Click to expand...
Click to collapse
arrgh, sorry.. darn tapatalk
http://forum.xda-developers.com/showpost.php?p=34888895&postcount=57
it's about Flash Image GUI by joeykrim

Based on my understanding, it simplifies the "fasboot flash recovery/boot" commands. Anything else I've missed?
Sent from my HTC Desire S using xda app-developers app

Skanob said:
Based on my understanding, it simplifies the "fasboot flash recovery/boot" commands. Anything else I've missed?
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
It doesn't look like it's helping with the OP's objective....

Not s-off, i know...
But the possibility of flashing kernels without fastboot and plugging to a computer is nice enough i think..
Sent from my HTC One X using Tapatalk 2

I wish I knew how to link a post from another discussion area. There is a Russian dev in HTC DNA General who's posted subject S-Off Is Possible While its specific to the Snapdragon CPU and consensus is his claim is legit and to be made available soon, on pg 5, the dev mentions he's getting a HOX to try and get S-Off. Important point here is another dev taking an interest in a HOX. So someone here can kindly point out to him the challenges already attempted.
Sent from my Desire HD using xda app-developers app

Y2KoaS said:
I wish I knew how to link a post from another discussion area. There is a Russian dev in HTC DNA General who's posted subject S-Off Is Possible While its specific to the Snapdragon CPU and consensus is his claim is legit and to be made available soon, on pg 5, the dev mentions he's getting a HOX to try and get S-Off. Important point here is another dev taking an interest in a HOX. So someone here can kindly point out to him the challenges already attempted.
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
Here you go. He says the method for achieving s-off on the DNA will work on a rate of 80% on the hox too. Sounds....strange. Anyways, heres the link to his post and thread.
http://forum.xda-developers.com/showthread.php?p=34960158
http://forum.xda-developers.com/showthread.php?t=2026033
-----------update-----------
Nevermind, he is talking about the At&t one x.
Sent from my HTC One X using xda premium

So close, but so far.
Sent from my HTC One X using Tapatalk 2

HTC 10 official nougat 2.41.401.4 RUU file

Hi guys...here is official htc link for pme wwe version of nougat 7.0 (2.41.041.4):
https://t.co/3LHINTyhIm

Hi, thanks a lot. Where did you find it? Are you sure it is truely 401.4 ruu and not the 401.3 diffused officially by htc?

It has already been shared here. And yes it is official 401.4, as it has been shared by an HTC official on Twitter.

Phoinix said:
Hi, thanks a lot. Where did you find it? Are you sure it is truely 401.4 ruu and not the 401.3 diffused officially by htc?
Click to expand...
Click to collapse
don't you trust me?

ali nz said:
don't you trust me?
Click to expand...
Click to collapse
I'm sorry, don't you misunderstand me, i've only pasted the link on an italian forum and immediately someone asked sources and more info, so i think to ask you.

Hello, can we get updates later when we did the original installation?

4yhan said:
Hello, can we get updates later when we did the original installation?
Click to expand...
Click to collapse
Yes ofcourse!
If you don't modify your system and don't install custom recovery you are a fully stock user and always get newest updates and can install them easily!

i tried to install and it showed me 2.41.401.3!

ali nz said:
Hi guys...here is official htc link for pme wwe version of nougat 7.0 (2.41.041.4):
https://t.co/3LHINTyhIm
Click to expand...
Click to collapse
Ah, this is the one that Graham Wheeler offered?
Unshortened:
http://dl3.htc.com/application/[email protected]_79.07_F_release_495903_signed_2.exe
You can check that when you copy the LINK from his profile you receive this shortened URL the thread initiator posted. Feel free to try yourselves! But i would personally prefer to use the original than something another user uploaded to some mirror. And i prefer to use original links, since it is more likely they are not manipulated.
https://twitter.com/wheelergd/status/830164169253068800
This RUU is working fine for me. I have it installed. CID is 34.
I tried the early 2.41.401.3 that was provided for UK!
And this one 2.41.401.4 that was provided for the rest of EU containing the fixes for NL.
AFAIK the ".3" Is the very very same build.
Just the ".4" containing some special fixes for NL region only.
And the people from UK are still on ".3". since they do not need this. So if you are on ".3" and live in the UK you can stay there.
If you know that your devices destiny was initially to receive the ".4" update since you live in NL and your device is going crazy, loosing IMEI and other stuffs and want to enter this special path again, go for it. I did it. And i live with WIPING my PHONE twice. But that is:
- My free time.
- My problem.
- Not yours.
And on top of all this i am very happy that Mr. Wheeler is offering this chance to me. Because i see some more benefits having a FULL signed STOCK RUU around. Because i owned a HTC phone in my life that i totally bricked. And there was no RUU available for it. And with this fine offer by him i have one now. Meaning i do not have to wait 4 weeks or so to get my phone recovered. I can just take this RUU and bring it back to life. Just in special circumstances.
And for me this means: "I did not need to do this, since even the ".3" worked for me in the very same manner. But i wanted to be on the originating path again, after trying the early release that UK received."
If you live in the UK and have the ".3" you will definitively not need to flash this. There is no need to flash anything. It was told that both will receive OTA in future.
And noone said you have to flash anything. Why do you stress yourselves with this?
Here some details about the ".3":
https://forum.xda-developers.com/showpost.php?p=70951262&postcount=2681
And the .4 that you find in this thread just containing the fixes for NL on top of this!
And once again: There is absolutely no force that you have to flash anything. You can just sit back and wait for OTA.
Maybe if the thread initiator would want to add more information, what this is originating of. It might prohibit questions about the question what this is for question.
AND PLEASE DO CORRECT ME ABOUT WHAT IS WRONG!

revealed said:
Ah, this is the one that Graham Wheeler offered?
Unshortened:
http://dl3.htc.com/application/[email protected]_79.07_F_release_495903_signed_2.exe
You can check that when you copy the LINK from his profile you receive this shortened URL the thread initiator posted. Feel free to try yourselves! But i would personally prefer to use the original than something another user uploaded to some mirror. And i prefer to use original links, since it is more likely they are not manipulated.
https://twitter.com/wheelergd/status/830164169253068800
This RUU is working fine for me. I have it installed. CID is 34.
I tried the early 2.41.401.3 that was provided for UK!
And this one 2.41.401.4 that was provided for the rest of EU containing the fixes for NL.
AFAIK the ".3" Is the very very same build.
Just the ".4" containing some special fixes for NL region only.
And the people from UK are still on ".3". since they do not need this. So if you are on ".3" and live in the UK you can stay there.
If you know that your devices destiny was initially to receive the ".4" update since you live in NL and your device is going crazy, loosing IMEI and other stuffs and want to enter this special path again, go for it. I did it. And i live with WIPING my PHONE twice. But that is:
- My free time.
- My problem.
- Not yours.
And on top of all this i am very happy that Mr. Wheeler is offering this chance to me. Because i see some more benefits having a FULL signed STOCK RUU around. Because i owned a HTC phone in my life that i totally bricked. And there was no RUU available for it. And with this fine offer by him i have one now. Meaning i do not have to wait 4 weeks or so to get my phone recovered. I can just take this RUU and bring it back to life. Just in special circumstances.
And for me this means: "I did not need to do this, since even the ".3" worked for me in the very same manner. But i wanted to be on the originating path again, after trying the early release that UK received."
If you live in the UK and have the ".3" you will definitively not need to flash this. There is no need to flash anything. It was told that both will receive OTA in future.
And noone said you have to flash anything. Why do you stress yourselves with this?
Here some details about the ".3":
https://forum.xda-developers.com/showpost.php?p=70951262&postcount=2681
And the .4 that you find in this thread just containing the fixes for NL on top of this!
And once again: There is absolutely no force that you have to flash anything. You can just sit back and wait for OTA.
Maybe if the thread initiator would want to add more information, what this is originating of. It might prohibit questions about the question what this is for question.
AND PLEASE DO CORRECT ME ABOUT WHAT IS WRONG!
Click to expand...
Click to collapse
Will it work on any region's HTC 10 ? I'm from SEA and my CID is 60. I read somewhere that this RUU is only for WWE devices (CID 01 I think).

RohinZaraki said:
Will it work on any region's HTC 10 ? I'm from SEA and my CID is 60. I read somewhere that this RUU is only for WWE devices (CID 01 I think).
Click to expand...
Click to collapse
What is your current software version?
Στάλθηκε από το HTC 10 μου χρησιμοποιώντας Tapatalk

RohinZaraki said:
Will it work on any region's HTC 10 ? I'm from SEA and my CID is 60. I read somewhere that this RUU is only for WWE devices (CID 01 I think).
Click to expand...
Click to collapse
401 for EU unlocked, CID034.

Ivanovic said:
What is your current software version?
Στάλθηκε από το HTC 10 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
1.95.400.3

RohinZaraki said:
1.95.400.3
Click to expand...
Click to collapse
No you can't. This RUU is for the 401 region
Στάλθηκε από το HTC 10 μου χρησιμοποιώντας Tapatalk

HTC 10 Nougat 7.0 v2.41.401.4 RUU
https://drive.google.com/file/d/0BzJZhsfT65ZLZlZ2cEhmYzljWms/view?usp=sharing

RohinZaraki said:
1.95.400.3
Click to expand...
Click to collapse
Seriously....how did you ever get your RC status ? By NOT reading. Logically when you are an RC you would know what to look at and what to know about basic Android and it's flashing behavior .... right ? Just to clarify this, i am genuinely confused ?
I told you this about 5 days ago already ?!

https://drive.google.com/file/d/0BzJZhsfT65ZLQ2I5YVYwaGtteTQ/view?usp=sharing
2PS6IMG_PERFUM[email protected]61229_89.09_F_release_693552_signed

I live in The Netherlands and I have version 2.42.709.3.This does not work in the Netherlands (my HTC 10 was purchased in the US).
How can I install version 2.41.401.4?
And do I first have to make a backup?
Thanks for the answer(s)

hanniolo said:
I live in The Netherlands and I have version 2.42.709.3.This does not work in the Netherlands (my HTC 10 was purchased in the US).
How can I install version 2.41.401.4?
And do I first have to make a backup?
Thanks for the answer(s)
Click to expand...
Click to collapse
Buy sunshine to s-off the device then convert to wwe 2.41.401

revealed said:
Ah, this is the one that Graham Wheeler offered?
Unshortened:
http://dl3.htc.com/application/[email protected]_79.07_F_release_495903_signed_2.exe
You can check that when you copy the LINK from his profile you receive this shortened URL the thread initiator posted. Feel free to try yourselves! But i would personally prefer to use the original than something another user uploaded to some mirror. And i prefer to use original links, since it is more likely they are not manipulated.
https://twitter.com/wheelergd/status/830164169253068800
This RUU is working fine for me. I have it installed. CID is 34.
I tried the early 2.41.401.3 that was provided for UK!
And this one 2.41.401.4 that was provided for the rest of EU containing the fixes for NL.
AFAIK the ".3" Is the very very same build.
Just the ".4" containing some special fixes for NL region only.
And the people from UK are still on ".3". since they do not need this. So if you are on ".3" and live in the UK you can stay there.
If you know that your devices destiny was initially to receive the ".4" update since you live in NL and your device is going crazy, loosing IMEI and other stuffs and want to enter this special path again, go for it. I did it. And i live with WIPING my PHONE twice. But that is:
- My free time.
- My problem.
- Not yours.
And on top of all this i am very happy that Mr. Wheeler is offering this chance to me. Because i see some more benefits having a FULL signed STOCK RUU around. Because i owned a HTC phone in my life that i totally bricked. And there was no RUU available for it. And with this fine offer by him i have one now. Meaning i do not have to wait 4 weeks or so to get my phone recovered. I can just take this RUU and bring it back to life. Just in special circumstances.
And for me this means: "I did not need to do this, since even the ".3" worked for me in the very same manner. But i wanted to be on the originating path again, after trying the early release that UK received."
If you live in the UK and have the ".3" you will definitively not need to flash this. There is no need to flash anything. It was told that both will receive OTA in future.
And noone said you have to flash anything. Why do you stress yourselves with this?
Here some details about the ".3":
https://forum.xda-developers.com/showpost.php?p=70951262&postcount=2681
And the .4 that you find in this thread just containing the fixes for NL on top of this!
And once again: There is absolutely no force that you have to flash anything. You can just sit back and wait for OTA.
Maybe if the thread initiator would want to add more information, what this is originating of. It might prohibit questions about the question what this is for question.
AND PLEASE DO CORRECT ME ABOUT WHAT IS WRONG!
Click to expand...
Click to collapse
How can I install 2.41.401.4? I've got version 2.41.709.3 and installed. My htc10 coming from the USA and I live in the Netherlands.
So I need version 2.41.401.4.
Thanks for the answer!
---------- Post added at 12:24 PM ---------- Previous post was at 12:14 PM ----------
Mr Hofs said:
Buy sunshine to s-off the device then convert to wwe 2.41.401
Click to expand...
Click to collapse
How exactly do you mean?