Related
HTC Europe 1.28.401.7 or HTC Europe 1.20.401.1 RUU
WHICH IS BEST FOR UK usage on cid htc__001 on sim free
and which gets updates first please
geordieboy2011 said:
HTC Europe 1.28.401.7 or HTC Europe 1.20.401.1 RUU
WHICH IS BEST FOR UK usage on cid htc__001 on sim free
and which gets updates first please
Click to expand...
Click to collapse
Hi,
The RUU HTC Europe 1.28.401.7 is best for UK. Install this RUU from the boot loader and change the CID of your phone to HTC_001 if it's on a different carrier. The OTA update works on this RUU and will update it to 1.29XXXXX.
modandroidgoogle said:
Hi,
The RUU HTC Europe 1.28.401.7 is best for UK. Install this RUU from the boot loader and change the CID of your phone to HTC_001 if it's on a different carrier. The OTA update works on this RUU and will update it to 1.29XXXXX.
Click to expand...
Click to collapse
Are you sure? I briefly tried to restore to stock using this, and others, all I got was an error when it tried to flash ... Wouldn't let me install because the version is older than the current UK Sim Free version I'm on ... I might be wrong as I know jack **** about S-Off and changing CID's etc but I know that on my UK Sim Free One, I couldn't restore from any of the RUU's available currently as there wasn't one that matched my version.
I'm on 1.29.401.13 btw ... Oh, still no update btw to 4.2.2 lol
AllAboutTheCore said:
Are you sure? I briefly tried to restore to stock using this, and others, all I got was an error when it tried to flash ... Wouldn't let me install because the version is older than the current UK Sim Free version I'm on ... I might be wrong as I know jack **** about S-Off and changing CID's etc but I know that on my UK Sim Free One, I couldn't restore from any of the RUU's available currently as there wasn't one that matched my version.
I'm on 1.29.401.13 btw ... Oh, still no update btw to 4.2.2 lol
Click to expand...
Click to collapse
Is your device on s-off and is the bootloader unlocked. Your device has to have s-off before you can successfully flash any version of any stock ruu . You will need to change the Cid as well to 11111111 before you can flash any version.
Mine was branded from 3 uk. After setting the device to s-off using instructions from the XDA forum, the bootloader was also unlocked. I didnt need to go through HTC to unlock the bootloader.
I downloaded the european wwe version and the asia wwe versions of the RUU , changed the CID from H3G_001 to 11111111 for all versions and was able to flash these roms to the phone . It even lets you flash a lower version. I then changed the CID FROM 11111111 to HTC_001 for europe and was able to download OTA updates. I even flashed the Asia version and this worked as well with the asia wwe cid.you can only flash these suceessfully if the device is s-off, bootloader unlocked and cid changed to the universal id which is 11111111. Instructiions can be found on this forum.
modandroidgoogle said:
Is your device on s-off and is the bootloader unlocked. Your device has to have s-off before you can successfully flash any version of any stock ruu . You will need to change the Cid as well to 11111111 before you can flash any version.
Mine was branded from 3 uk. After setting the device to s-off using instructions from the XDA forum, the bootloader was also unlocked. I didnt need to go through HTC to unlock the bootloader.
I downloaded the european wwe version and the asia wwe versions of the RUU , changed the CID from H3G_001 to 11111111 for all versions and was able to flash these roms to the phone . It even lets you flash a lower version. I then changed the CID FROM 11111111 to HTC_001 for europe and was able to download OTA updates. I even flashed the Asia version and this worked as well with the asia wwe cid.you can only flash these suceessfully if the device is s-off, bootloader unlocked and cid changed to the universal id which is 11111111. Instructiions can be found on this forum.
Click to expand...
Click to collapse
Cool ... Like I said, I wasn't sure, my phone is S-On btw so that would explain it lol
AllAboutTheCore said:
Cool ... Like I said, I wasn't sure, my phone is S-On btw so that would explain it lol
Click to expand...
Click to collapse
You don't need to s-off to downgrade you can use the toolbox software to run mainver error check (needs root) to trick the phone into thinking its on 1.00 of hoot then you can downgrade with the RUU.
daleski75 said:
You don't need to s-off to downgrade you can use the toolbox software to run mainver error check (needs root) to trick the phone into thinking its on 1.00 of hoot then you can downgrade with the RUU.
Click to expand...
Click to collapse
Always good to learn something! .. I'm on stock, unrooted at mo though and have no plans to change that ... Yet lol
Hi, I'm s-off and CID 11111111 and I'm in Canada, I flashed this
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed and every thing worked perfectly, then I changed my CID to HTC___Y13 to get the latest OTA update, when the update finished downloading I got a message saying that my HTC is running modified software or something like that and for my safty the update will not install.
What wrong here? can't I get the update this way?
Thank you...
nisayramo said:
Hi, I'm s-off and CID 11111111 and I'm in Canada, I flashed this
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed and every thing worked perfectly, then I changed my CID to HTC___Y13 to get the latest OTA update, when the update finished downloading I got a message saying that my HTC is running modified software or something like that and for my safty the update will not install.
What wrong here? can't I get the update this way?
Thank you...
Click to expand...
Click to collapse
at the very least, its because you have a custom recovery. Thats why the OTA failed
Where can I download stock recovery? and if i got it what i did should work in theory right?
If after you've flashed ruu, didn't flash anything .You already have stock recovery!
Other words ,after RUU you at the stock recovery.
What your MID?
"RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed" seems for 0710000 MID.
More likely,the reason of fault OTA - you are unable to meet mid OTA update.
tash2013 said:
If after you've flashed ruu, didn't flash anything .You already have stock recovery!
Other words ,after RUU you at the stock recovery.
What your MID?
"RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed" seems for 0710000 MID.
More likely,the reason of fault OTA - you are unable to meet mid OTA update.
Click to expand...
Click to collapse
Oh, I see thank you for the help.. My MID is PN0712000
You are trying to flash the OTA to htc__y13 cid/0710000 mid on phone with 07120000 mid - it's a bad idea.
What to do?
1) You can change mid, but I strongly DO NOT advise - this is a dangerous procedure.
2) You can flash the RUU for your mid and just wait for the OTA update will come to you - it is good
tash2013 said:
You are trying to flash the OTA to htc__y13 cid/0710000 mid on phone with 07120000 mid - it's a bad idea.
What to do?
1) You can change mid, but I strongly DO NOT advise - this is a dangerous procedure.
2) You can flash the RUU for your mid and just wait for the OTA update will come to you - it is good
Click to expand...
Click to collapse
I'm trying to find An RUU for my MID can you help? and of course thank you..
nisayramo said:
I'm trying to find An RUU for my MID can you help? and of course thank you..
Click to expand...
Click to collapse
What your originally CID?
And more.. just an advise .. under your current condition (after europe RUU) do not going to s-on never.
tash2013 said:
What your originally CID?
And more.. just an advise .. under your current condition (after europe RUU) do not going to s-on never.
Click to expand...
Click to collapse
My Origianl CID is BM___001, and got it s-off for ever
Unfortunately, I don't oriented to the North American operators,and I do not know what is BM .
And therefore can't advise the exact RUU
OK, let's go through the first way, under your current state change your mid to European
type:* fastboot oem writemid PN0710000
Stop stop! Before change mid type here your : fastboot getvar all
tash2013 said:
Unfortunately, I don't oriented to the North American operators,and I do not know what is BM .
And therefore can't advise the exact RUU
OK, let's go through the first way, under your current state change your mid to European
type:* fastboot oem writemid PN0710000
Stop stop! Before change mid type here your : fastboot getvar all
Click to expand...
Click to collapse
BM is Bell Mobility
I did not find your BM RUU from here
http://forum.xda-developers.com/showthread.php?p=39588860
and here
http://www.androidfiles.org/ruu/?developer=M7
Only a nandroid backup ,but I think it is not full stock, at least a stock recovery is missing and I'm afraid something else.
Time you were already flashed by the European RUU, let will change MID to European. And you will be have completely European unbranded phone.
if you decide do it .. print here " fastboot getvar all" (without your imei) I'll check your current state.
Hi i can't flash ruu
phone CID is HTC__J015 i think this cid is for Europe . i downloaded many ruu for Europe but all of them have a image error.
help me
pourya-man said:
Hi i can't flash ruu
phone CID is HTC__J015 i think this cid is for Europe . i downloaded many ruu for Europe but all of them have a image error.
help me
Click to expand...
Click to collapse
Is the RUU match with CID for your phone? AFAIK, you will need to relock your phone in order to use RUU.
xDelCrOsSen said:
Is the RUU match with CID for your phone? AFAIK, you will need to relock your phone in order to use RUU.
Click to expand...
Click to collapse
i relocked it but have rom image error
please give me HTC__J015 ruu link
pourya-man said:
i relocked it but have rom image error
please give me HTC__J015 ruu link
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
If your current version is already higher than this one then it won't work, please check md5 and file size before running
Hi all, I was just wondering if I should run the RUU ZIP or EXE if I am on S-OFF.
I currently have the 6.06.401.1 firmware along with the stock 6.06.401.1 rom. I need to return to the stock 1.29.707.1 for my HTC__044 before taking the latest OTA to Android Lollipop.
So far, I have used my S-OFF to change my bootloader to *LOCKED* and flashed stock recovery and stock rom for the 6.06.401.1.
I currently have both the 1.29.707.1 RUU EXE and ZIP. Which one should I use? I read that I need to have the 1.44 Hboot but I currently have the 1.54 Hboot.
Halp?
uhm, what? this is nonsense , the lastest available RUU is "4.19.401.9" which must be flashed under hboot 1.56 ... there is no need to go to initial release of android 4.1!
WARNING!!! YOU MUST FLASH HBOOT 1.56 BEFORE APPLYING 4.19.401.9 RUU
RUU: http://d-h.st/KmT
+There is no need to LOCK your bootloader to get an OTA update... Mine is always unlocked and never had a problem with OTA's
+RUU's work only under S-OFF
Androidian10 said:
Hi all, I was just wondering if I should run the RUU ZIP or EXE if I am on S-OFF.
I currently have the 6.06.401.1 firmware along with the stock 6.06.401.1 rom. I need to return to the stock 1.29.707.1 for my HTC__044 before taking the latest OTA to Android Lollipop.
So far, I have used my S-OFF to change my bootloader to *LOCKED* and flashed stock recovery and stock rom for the 6.06.401.1.
I currently have both the 4.20.707.1 RUU EXE and ZIP. Which one should I use? I read that I need to have the 1.44 Hboot but I currently have the 1.54 Hboot.
Halp?
Click to expand...
Click to collapse
you can use the RUU you have fine 4.20.707.1, you'll just have to make sure your cid and mid match first, and also just flash the 4.20.707.1 firmware first, this will put you on the correct HBOOT and system files for the RUU, no need to lock your bootloader with s-off.
or you can skip all of that and just flash the 7.19.401.2 RUU right now as your phone is as your already on the 6.xx.401.x firmware.
you don't really have any reason to back flash.
Seanie280672 said:
you can use the RUU you have fine 4.20.707.1, you'll just have to make sure your cid and mid match first, and also just flash the 4.20.707.1 firmware first, this will put you on the correct HBOOT and system files for the RUU, no need to lock your bootloader with s-off.
or you can skip all of that and just flash the 7.19.401.2 RUU right now as your phone is as your already on the 6.xx.401.x firmware.
you don't really have any reason to back flash.
Click to expand...
Click to collapse
But I can't seem to find a 4.20.707.1 RUU. I only have the 1.29.707.3 firmware. I need a region specific one because I need to trade my phone in.
Could you point me in the direction of a 4.20.707.1 RUU zip?
Also, is it safe to OTA update if I flash back to 1.29 with S-OFF?
Edit: Crap I made a typo in my OP, I mean that I have the 1.29 RUU EXE and ZIP right now.
Androidian10 said:
But I can't seem to find a 4.20.707.1 RUU. I only have the 1.29.707.3 firmware. I need a region specific one because I need to trade my phone in.
Edit: Crap I made a typo in my OP, I mean that I have the 1.29 RUU EXE and ZIP right now.
Could you point me in the direction of a 4.20.707.1 RUU zip?
Also, is it safe to OTA update if I flash back to 1.29 with S-OFF?
Click to expand...
Click to collapse
I thought you said you had the 4.20.707.1 RUU
if not then you'll have to use the 1.29.707 one that you have, you'll just have to flash the 1.44 hboot first or the firmware that matches the RUU.
Seanie280672 said:
I thought you said you had the 4.20.707.1 RUU
if not then you'll have to use the 1.29.707 one that you have, you'll just have to flash the 1.44 hboot first or the firmware that matches the RUU.
Click to expand...
Click to collapse
Yeah I had a typo.
So yeah, I have both the EXE and ZIP RUU.
I'm thinking that the ZIP RUU has the 1.44 hboot no?
Also, most importantly, can I take official OTA updates while I am S-OFFed?
Androidian10 said:
Yeah I had a typo.
So yeah, I have both the EXE and ZIP RUU.
I'm thinking that the ZIP RUU has the 1.44 hboot no?
Also, most importantly, can I take official OTA updates while I am S-OFFed?
Click to expand...
Click to collapse
yes you can take OTA's whilst s-off, do not go s-on at any point.
I would also say try the RUU.zip first.
Seanie280672 said:
yes you can take OTA's whilst s-off, do not go s-on at any point.
I would also say try the RUU.zip first.
Click to expand...
Click to collapse
Righto. Will report back again.
I hope the guy at the store doesn't go into the bootloader when I trade my m7 in. Even then I already set the flag to locked so I think he'll miss that S-OFF portion.
Androidian10 said:
Righto. Will report back again.
I hope the guy at the store doesn't go into the bootloader when I trade my m7 in. Even then I already set the flag to locked so I think he'll miss that S-OFF portion.
Click to expand...
Click to collapse
cid and mid need to match the ruu your flashing first.
Seanie280672 said:
cid and mid need to match the ruu your flashing first.
Click to expand...
Click to collapse
Already checked with fastboot getvar all.
Seanie280672 said:
cid and mid need to match the ruu your flashing first.
Click to expand...
Click to collapse
Actually, problem. :/
I have a matching CID which is HTC__044 but the modelid is PN0714000.
The RUU's android-info has a matching CID of HTC__044 but a modelid of PN0711000.
What now?
Androidian10 said:
Actually, problem. :/
I have a matching CID which is HTC__044 but the modelid is PN0714000.
The RUU's android-info has a matching CID of HTC__044 but a modelid of PN0711000.
What now?
Click to expand...
Click to collapse
unlock your bootloader, flash twrp recovery and change your mid, are you sure your using the RUU for the M7_UL as that looks a lot like the M7_U mid too me, can you give me a link for the RUU's you downloaded please.
---------- Post added at 11:05 AM ---------- Previous post was at 10:57 AM ----------
here you go, do this instead, this is going to be a bit backwards and forwards.
Unlock your bootloader, and flash TWRP recovery, then use the mid change tool to change your mid to the correct one.
https://www.androidfilehost.com/?fid=23622183712469376
next copy this guru reset file to your internal storage and flash it, select no to stock radio and no to stock recovery: http://www.htc1guru.com/2013/11/guru-reset-3-63-707-4-stock-rom/
now lock your bootloader
and finally flash the matching firmwqare from here: http://d-h.st/BWu this will put stock recovery and stock radio on your phone.
Seanie280672 said:
unlock your bootloader, flash twrp recovery and change your mid, are you sure your using the RUU for the M7_UL as that looks a lot like the M7_U mid too me, can you give me a link for the RUU's you downloaded please.
Click to expand...
Click to collapse
I actually ran the RUU. It's now stuck on waiting for device after the usual flush after 90 hboot pre-update.
I changed the modelid in the android-info.txt since it was decrypted.
Anyone help me?
My computer can't see the device anymore after flashing the hboot!
Androidian10 said:
Anyone help me?
My computer can't see the device anymore after flashing the hboot!
Click to expand...
Click to collapse
if your using windows 8 or higher then that's the problem, HBOOT 1.44 doesn't work with it, there is a fix around here somewhere by @clsA but ive never had to use it myself.
trouble with changing the android-info text file is all of the OTA's will fail due to you having the wrong mid on your phone, you'll have to change your phones mid as soon as possible.
Seanie280672 said:
if your using windows 8 or higher then that's the problem, HBOOT 1.44 doesn't work with it, there is a fix around here somewhere by @clsA but ive never had to use it myself.
trouble with changing the android-info text file is all of the OTA's will fail due to you having the wrong mid on your phone, you'll have to change your phones mid as soon as possible.
Click to expand...
Click to collapse
Ok, I have changed to an old Windows 7 laptop and tried doing the fastboot flash zip again. After I press enter, nothing happens at all. Not a single code at all. Just a blinker.
Edit: Started moving again. Phew. I almost had a heart attack.
So now do I do the fastboot writemid command?
Androidian10 said:
Ok, I have changed to an old Windows 7 laptop and tried doing the fastboot flash zip again. After I press enter, nothing happens at all. Not a single code at all. Just a blinker.
Edit: Started moving again. Phew. I almost had a heart attack.
So now do I do the fastboot writemid command?
Click to expand...
Click to collapse
to change the mid you need to use the mid change tool I posted a link to it earlier, install it inside twrp recovery then select the mid you require from the list it gives you.
Seanie280672 said:
to change the mid you need to use the mid change tool I posted a link to it earlier, install it inside twrp recovery then select the mid you require from the list it gives you.
Click to expand...
Click to collapse
It's okay now. I found a matching mid RUU for my phone.
But my question now is should I go S-ON to remove the red "This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings" warning? Or just leave it S-OFF and hope that the techies at the store doesn't notice it?
More questions
I have done all the OTAs now so should I do the fastboot oem writesecureflag 3 as the final step before putting the phone aside to trade it in?
Androidian10 said:
More questions
I have done all the OTAs now so should I do the fastboot oem writesecureflag 3 as the final step before putting the phone aside to trade it in?
Click to expand...
Click to collapse
no, leave it s-off, if you turn it back s-on now you will get the tampered flag back.
Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,
BorisZX6R said:
Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,
Click to expand...
Click to collapse
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Thank you for your time and response. I will think about what RUU is best for me. I am currently on the T-Mobile network with this phone and so far there is no indicator that will change anytime soon. I will try and post my response.
Thank you again!
alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!
BorisZX6R said:
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!
Click to expand...
Click to collapse
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!
BorisZX6R said:
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!
Click to expand...
Click to collapse
Yes, supercid is 11111111 so your CID isn't a problem. Just make sure that your MID also match the ruu you want to use (or change it if needed). If you MID is still the original, it should be PN0712000 so you can either use an AT&T or Developer Edition RUU (x.xx.1540.x). Otherwise if you want to use the WWE version (x.xx.401.x) You'll have to change your MID to PN0710000.
alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
It worked. For a moment the output in the command window seemed like it was giving errors (unfortunately it was very late and I did not copy the output) but in the end I realized it updated the hboot and I was able to flash a different RUU.
Thank you for all your help!