Database Develop

[SOLVED] Can't flash RUU's?

Sorry for creating a lot of help threads, but things just don't wanna work my way.
Yesterday I wanted to flash a RUU to see exactly how HTC does things and if it's easy or hard. Anyway. I come from a Galaxy S3 and if I wanted to go back to stock from any other rom, I simply flashed a stock rom tar with a program called Odin, but it doesn't seem to be as simple with HTC.
I downloaded a RUU for the Europe region as it seemed the most obvious thing to do, but my CID is Nordic (HTC__Y13). Here's how it went:
Being on a 4.2.2 custom rom:
I tried running the RUU when I was on a 4.2.2. custom rom (InsertCoin 2.0.2), and I fired up the RUU file and followed the instructions. Then it said my phone isn't supported and that I need another RUU file.
Being on a stock odexed 1.29 rom:
I then installed a stock 1.29 rom from Mike1986. and then fired up the RUU. I followed the instructions and it seems the flashing started. It sent me to the RUU mode (the HTC screen) and began the flashing process. It said it wiped the data and that it sent some signature keys, I think. Three minutes later, the RUU window disappeared. I could see the program was still running but the window disappeared. It quickly flashed for about half a second and I could see some text saying that my phone isn't supported, but why the hell did it commence the flashing?
I pulled the cable, long-pressed the power button and let it boot, it hadn't wiped a thing.
Let it be known that before I opened the RUU's, I made sure I was bootloader locked and S-ON (with the revone method).
Is it because I have the Nordic CID and I had a RUU for the European region? If so, I looked anywhere and everywhere for a Nordic RUU but there's none to be found.
Any help is appreciated.

You can only use an RUU which is the same or newer than the firmware on the phone, e.g. if your last official update was 1.29.401.13 you could only use an RUU that version or above UNLESS you're S-OFF, in which case you can use an older one if you have Super CID and a locked/relocked bootloader

EddyOS said:
You can only use an RUU which is the same or newer than the firmware on the phone, e.g. if your last official update was 1.29.401.13 you could only use an RUU that version or above UNLESS you're S-OFF, in which case you can use an older one if you have Super CID and a locked/relocked bootloader
Click to expand...
Click to collapse
So what you're saying, is:
If I acquire Super CID, then flash a Europe RUU and then set my CID back to what it originally was (or maybe even set it to HTC__001) and then reflash the RUU, and it'll work beautifully? I'm S-OFF, btw.

Theshawty said:
So what you're saying, is:
If I acquire Super CID, then flash a Europe RUU and then set my CID back to what it originally was (or maybe even set it to HTC__001) and then reflash the RUU, and it'll work beautifully? I'm S-OFF, btw.
Click to expand...
Click to collapse
Where you S-Off or S-On when you ran the RUU?

bobsie41 said:
Where you S-Off or S-On when you ran the RUU?
Click to expand...
Click to collapse
S-ON with the bootloader locked. I wanted to see if it was possible.
I'm not really looking to revert to unrooted stock, at least not now. I just want to know that it's possible without too much work for when it would be necessary or when I want to try out unrooted stock again. It's always nice to have a fallback.

Theshawty said:
S-ON with the bootloader locked. I wanted to see if it was possible.
I'm not really looking to revert to unrooted stock, at least not now. I just want to know that it's possible without too much work for when it would be necessary or when I want to try out unrooted stock again. It's always nice to have a fallback.
Click to expand...
Click to collapse
As far as I'm aware, you can only run a RUU that is relevant to you device whilst you are s-on and only one that is equal to or above the firmware that you are running.
The only way to return to official un-rooted stock is, again, to run a RUU for your device or install a completely stock nandroid backup of your device or one running the same version as yours.

OK, full example...
You originally get an unbranded One from the EU and you get the OTA to 1.29.401.13. From this point on, with an S-ON/Locked phone with CID HTC__001 you can ONLY flash an RUU which is 1.29.401.13 or higher. This will never change. If you get an RUU from a specific carrier you cannot flash it as it doesn't match your CID.
If you unlock the bootloader, but stay S-ON, you cannot flash an RUU at all - you HAVE to relock the bootloader first but you can still only flash an RUU matching your CID and is the same or newer than your current version.
If you S-OFF and change the CID to 11111111 you can flash ANY RUU you want, even those older than your current version, e.g. 1.28.401.7. You still have to have a locked/relocked bootloader but you can stay S-OFF and flash the RUU. As the only RUU available at the moment for the unbranded One is 1.28.401.7 it means you can flash that and then get the OTA updates in sequence to get to the latest version
Once back at the older version using the RUU you could change your CID back to HTC__001 if you wanted but I don't think it matters

EddyOS said:
OK, full example...
You originally get an unbranded One from the EU and you get the OTA to 1.29.401.13. From this point on, with an S-ON/Locked phone with CID HTC__001 you can ONLY flash an RUU which is 1.29.401.13 or higher. This will never change. If you get an RUU from a specific carrier you cannot flash it as it doesn't match your CID.
If you unlock the bootloader, but stay S-ON, you cannot flash an RUU at all - you HAVE to relock the bootloader first but you can still only flash an RUU matching your CID and is the same or newer than your current version.
If you S-OFF and change the CID to 11111111 you can flash ANY RUU you want, even those older than your current version, e.g. 1.28.401.7. You still have to have a locked/relocked bootloader but you can stay S-OFF and flash the RUU. As the only RUU available at the moment for the unbranded One is 1.28.401.7 it means you can flash that and then get the OTA updates in sequence to get to the latest version
Once back at the older version using the RUU you could change your CID back to HTC__001 if you wanted but I don't think it matters
Click to expand...
Click to collapse
Ah, thanks for the clarification! If I do this (Super CID plus flash the RUU), should I change back to the HTC__Y13 cid or change to something like HTC__001 to get the updates for the Europe region? I heard Europe gets OTA's faster than other regions.
One more thing, why does the bootloader have to be locked? Does the RUU check for this?

Theshawty said:
Ah, thanks for the clarification! If I do this (Super CID plus flash the RUU), should I change back to the HTC__Y13 cid or change to something like HTC__001 to get the updates for the Europe region? I heard Europe gets OTA's faster than other regions.
One more thing, why does the bootloader have to be locked? Does the RUU check for this?
Click to expand...
Click to collapse
If you wish to get ota's you will need to have a cid which is relevant to the RUU you have run. Either of those cid's should work for a x.xx.401.x RUU. Not sure about the bootloader locking for an RUU.

bobsie41 said:
If you wish to get ota's you will need to have a cid which is relevant to the RUU you have run. Either of those cid's should work for a x.xx.401.x RUU. Not sure about the bootloader locking for an RUU.
Click to expand...
Click to collapse
The bootloader doesn't need to be locked to flash a RUU. A guy over at Swedroid flashed a Europe RUU (401 device) (after setting Super CID) coming from a carrier-branded One and the RUU did flash perfectly.
I would of course want OTA's, but the thing is, I heard Europe gets them faster than the Nordic region.

Theshawty said:
The bootloader doesn't need to be locked to flash a RUU. A guy over at Swedroid flashed a Europe RUU (401 device) (after setting Super CID) coming from a carrier-branded One and the RUU did flash perfectly.
I would of course want OTA's, but the thing is, I heard Europe gets them faster than the Nordic region.
Click to expand...
Click to collapse
Not necessarily. As with the s3, releases seem pretty random from country to country in Europe. I had the one x with HTC__001 cid and was one of the last to be updated.
Sent from my Nexus 7 using xda premium

Locked the bootloader and went into fastboot and started the RUU. It is now flashing :victory:
After it's done, I will turn the CID back to HTC__Y13 and reflash the RUU.

Theshawty said:
The bootloader doesn't need to be locked to flash a RUU. A guy over at Swedroid flashed a Europe RUU (401 device) (after setting Super CID) coming from a carrier-branded One and the RUU did flash perfectly.
I would of course want OTA's, but the thing is, I heard Europe gets them faster than the Nordic region.
Click to expand...
Click to collapse
I, personally, would relock the bootloader purely to cover yourself. As for CID, it's up to you. Using HTC__001 might not get it the second an OTA comes out but I'm sure you're patient enough to wait a few days

EddyOS said:
I, personally, would relock the bootloader purely to cover yourself. As for CID, it's up to you. Using HTC__001 might not get it the second an OTA comes out but I'm sure you're patient enough to wait a few days
Click to expand...
Click to collapse
I just want back to stock for a few days. I'm a bit tired of custom roming yet I can't stay away from it!

Theshawty said:
I just want back to stock for a few days. I'm a bit tired of custom roming yet I can't stay away from it!
Click to expand...
Click to collapse
I've done the same with my Nexus 4, and shall do the same with my One when I get it next month. I want S-OFF purely because the only RUU we have is an older than what I'll likely get on my phone. This way I can always go back to stock (unless a newer RUU leaks that is!)

How awfully peculiar, though. After I flashed to stock (the 1.28 something RUU), I got an update to 1.29.401.12. My brother, whom also have a One in the same region as I, has the 1.29.401.16 update (I am four decimals behind him ).
I thought I would get an update to .16, or am I just being too impatient?
I know I had .16 before custom roms though.

I read all, very useful conversation,saved me lot of time
Only a thing i havent understand
Im now S-OFF,unlocked with superCID ( runnind a branded italian rom with (now old)TIM__041(if i rememeber right)cid)
What i need to do to have a stock unbranded european RUU
Do i need to relock bootloader Before flashing or not matters?

Theshawty said:
How awfully peculiar, though. After I flashed to stock (the 1.28 something RUU), I got an update to 1.29.401.12. My brother, whom also have a One in the same region as I, has the 1.29.401.16 update (I am four decimals behind him ).
I thought I would get an update to .16, or am I just being too impatient?
I know I had .16 before custom roms though.
Click to expand...
Click to collapse
.16 was for the M7_U handsets, M7_UL is on .12

EddyOS said:
.16 was for the M7_U handsets, M7_UL is on .12
Click to expand...
Click to collapse
But my little brother and I both have UL devices, and his clearly says UL in the about screens.

Theshawty said:
But my little brother and I both have UL devices, and his clearly says UL in the about screens.
Click to expand...
Click to collapse
Hmmm, perhaps it is down to CID then...I don't know anyone in the UK with anything over .12

[Q] Trying to get the latest OTA update

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.

[Q] Flashing RUU

Okay - time to swallow my man pride and ask for directions...
My current software version is 1.28.61.7 and CID was Orang001 - realising that EE were not going to be releasing the 4.2.2 update anytime soon, I decided to try and follow the advice of you bright chaps...
Following the steps in the:
[Official Chat] thread (past 2): http://forum.xda-developers.com/showpost.php?p=42086559&postcount=2; and
Revone guide: http://forum.xda-developers.com/showthread.php?t=2314582,
I have been able to:
Unlock my device (and turn tamper off);
obtain S-OFF;
Change my CID to HTC__001 (and change it to the SuperCID: 11111111 if required),
All going well so far - now the next step was to run RUU 1.28.401.7 and wait for the OTA - unfortunately this is where I am stuck...
I downloaded the RUU from the following site: http://www.androidfiles.org/ruu/?developer=M7 (as the buggsylawson site appears to be down) and ran it. The RUU seemed to have installed without a hitch - no errors at all, however when I check my software number it is still 1.28.61.7.
Having spent a few hours reading these forums, I finally admit defeat - please help - what should I do next? What is the best way to update, remaining stock and OTA to 4.2.2?
In case it helps, my current kernel version is:
3.4.10 -gddcfb8c
[email protected] #1
SMP PREEMPT
Thank you in advance!
_________________
Update: tried running the RUU again with CID: 11111111 - still stuck on 1.28.61.7

Did u check for OTA?
Sent from my HTC One using xda premium

mathrania said:
Did u check for OTA?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
That's not the point.
To the OP: Change the CID to 11111111 and try to flash the RUU again (if you haven't already). Knowing the kernel is pointless too, the important information is the software build, e.g. 1.28.401.7

EddyOS said:
That's not the point.
To the OP: Change the CID to 11111111 and try to flash the RUU again (if you haven't already). Knowing the kernel is pointless too, the important information is the software build, e.g. 1.28.401.7
Click to expand...
Click to collapse
Thanks for the response, trying this again now - I'll let you know the result.

EddyOS said:
That's not the point.
To the OP: Change the CID to 11111111 and try to flash the RUU again (if you haven't already). Knowing the kernel is pointless too, the important information is the software build, e.g. 1.28.401.7
Click to expand...
Click to collapse
Just finished running the RUU with CID 11111111 - still stuck on 1.28.61.7.
Really quite stumped...

It's pretty much impossible so not sure what's going on!

Clutching at straws here...
Any chance that I don't have the right RUU and it is only updating certain elements?
The RUU downloaded is: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
991 MB from http://www.androidfiles.org/ruu/?developer=M7
If so, where can I get the correct RUU or another for testing?
Thanks

[Q] How to Debrand HTC One

I have a HTC One on the EE network in the UK and I am still currently on Android 4.3 and Sense 5.5, they haven't bothered to release Android 4.4 yet and I have no hope that they will release Sense 6.
So, I would like to know how to go about changing my EE branded phone into an Unlocked International Version so that I can receive OTA updates direct from HTC.
Current CID: ORANG001
Current Hboot: 1.55
Current Software Number: 3.63.61.1
Radio: 4A.21.3263.04
Locked Bootloader with S-On
I would very much appreciate any help you can give.
Thank-You

rh92 said:
I have a HTC One on the EE network in the UK and I am still currently on Android 4.3 and Sense 5.5, they haven't bothered to release Android 4.4 yet and I have no hope that they will release Sense 6.
So, I would like to know how to go about changing my EE branded phone into an Unlocked International Version so that I can receive OTA updates direct from HTC.
Current CID: ORANG001
Current Hboot: 1.55
Current Software Number: 3.63.61.1
Radio: 4A.21.3263.04
Locked Bootloader with S-On
I would very much appreciate any help you can give.
Thank-You
Click to expand...
Click to collapse
first of all you need to unlock your bootloader and s-off your phone, debrand is not possible with s=on
the you would need to change your cid to something like HTC__001 or developer edition cid, one fastboot command required to do this.
and then run the correct RUU for those cid's and your done.
its quite easy to do, the hardest part is getting s-off, however you may be ok on 1.55 hboot, try rumrunner, read the instructions and download the required file here: http://rumrunner.us/

Seanie280672 said:
first of all you need to unlock your bootloader and s-off your phone, debrand is not possible with s=on
the you would need to change your cid to something like HTC__001 or developer edition cid, one fastboot command required to do this.
and then run the correct RUU for those cid's and your done.
its quite easy to do, the hardest part is getting s-off, however you may be ok on 1.55 hboot, try rumrunner, read the instructions and download the required file here: http://rumrunner.us/
Click to expand...
Click to collapse
Do I need custom recovery? If so which is best.
And do I need to have a custom ROM installed to gain s-off or can s-off be achieved on my current EE branded ROM?
Thanks

rh92 said:
Do I need custom recovery? If so which is best.
And do I need to have a custom ROM installed to gain s-off or can s-off be achieved on my current EE branded ROM?
Thanks
Click to expand...
Click to collapse
nope its not required for either, you should be able to s-off on stock rom, if you get an error or for some reason it fails, then you MAY have to flash a custom recovery and custom rom / kernel.
The RUU's will put you back to fully stock anyway in the end.

Seanie280672 said:
nope its not required for either, you should be able to s-off on stock rom, if you get an error or for some reason it fails, then you MAY have to flash a custom recovery and custom rom / kernel.
The RUU's will put you back to fully stock anyway in the end.
Click to expand...
Click to collapse
If the s-off does cause an error or it fails, can this cause my device to get bricked?
And by fully stock do you mean that the RUU turns s-on and locks my boot loader? (just in case I need to send my phone in for repair).
Thanks

rh92 said:
If the s-off does cause an error or it fails, can this cause my device to get bricked?
And by fully stock do you mean that the RUU turns s-on and locks my boot loader? (just in case I need to send my phone in for repair).
Thanks
Click to expand...
Click to collapse
no your phone wont brick
and no the ruu wont turn your phone s-on, you will need to lock your bootloader before running the RUU, but that's one simple command too, but only after s-off.
all you need right now is to make sure you have the drivers installed and that your device is detected in windows both when booted into a rom and on the bootloader screen.

Seanie280672 said:
no your phone wont brick
and no the ruu wont turn your phone s-on, you will need to lock your bootloader before running the RUU, but that's one simple command too, but only after s-off.
all you need right now is to make sure you have the drivers installed and that your device is detected in windows both when booted into a rom and on the bootloader screen.
Click to expand...
Click to collapse
After installing the RUU how would I get s-on?
Thanks

rh92 said:
After installing the RUU how would I get s-on?
Thanks
Click to expand...
Click to collapse
don't s-on, never s-on simple as that.

Seanie280672 said:
don't s-on, never s-on simple as that.
Click to expand...
Click to collapse
Ok, I was just asking in case I needed to send my phone in for repair in the future.

rh92 said:
Ok, I was just asking in case I needed to send my phone in for repair in the future.
Click to expand...
Click to collapse
not really something they will check to be honest, but if you s-on and you've played about with your phone down the line, like flashed a modified firmware or hboot, you will get an instant brick, if your hboot version is too high you will get the tampered flag back, or if you make a mistake along the way and the fix requires s-off, it will be very difficult to get again.

Seanie280672 said:
not really something they will check to be honest, but if you s-on and you've played about with your phone down the line, like flashed a modified firmware or hboot, you will get an instant brick, if your hboot version is too high you will get the tampered flag back, or if you make a mistake along the way and the fix requires s-off, it will be very difficult to get again.
Click to expand...
Click to collapse
So, is the following step by step list correct.
1. Unlock boot loader
2. Get s-off via rumrunner
3. Change CID
4. Lock boot loader
5. Run RUU
And, I am currently on 4.3 and Sense 5.5, so can I go straight to the sense 6 and Android 4.4 RUU, or do I have to install the sense 5.5 and Android 4.4 RUU first.
Thanks

rh92 said:
So, is the following step by step list correct.
1. Unlock boot loader
2. Get s-off via rumrunner
3. Change CID
4. Lock boot loader
5. Run RUU
And, I am currently on 4.3 and Sense 5.5, so can I go straight to the sense 6 and Android 4.4 RUU, or do I have to install the sense 5.5 and Android 4.4 RUU first.
Thanks
Click to expand...
Click to collapse
yup that's the correct order, and you will have to use this RUU as its the only full RUU available, everything else is just OTA's
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe

Seanie280672 said:
yup that's the correct order, and you will have to use this RUU as its the only full RUU available, everything else is just OTA's
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Click to expand...
Click to collapse
And after installing this RUU I can just download Sense 6 via OTA.

rh92 said:
And after installing this RUU I can just download Sense 6 via OTA.
Click to expand...
Click to collapse
yes, just accept the ota's one at a time.

Seanie280672 said:
yes, just accept the ota's one at a time.
Click to expand...
Click to collapse
Thanks for your help

I have an PN07200, how can I get sense 6, which will be the best RUU and CID?.... Thanks!
Enviado desde mi HTC One X+ mediante Tapatalk

is it possible to re-apply the branding?
i.e.
RUU
change cid
OTA with brand change

gwaitsi said:
is it possible to re-apply the branding?
i.e.
RUU
change cid
OTA with brand change
Click to expand...
Click to collapse
yup, change your cid to its original one, and find your service providers RUU and flash it.

[Q] Going back to Sense from GPE

Hi all.
Last week, after i soft bricked my phone (HTC ONE M7 EU with no carrier , bough directly from ) trying to update it to the latest version (i had mine unlocked and rooted to solve previous battery problems), i finally fixed it with the help of an user of this community
I have now an S-off HTC One GPE with 4.4.4 (via OTA update after flashing a RUU zip)
I kinda not like GPE and i think i should back to Sense .
Can anyone point me to the correct RUU thread and/or instructions or presequisites i shoult take account to do this process?
Thanks in advance

diesalher said:
Hi all.
Last week, after i soft bricked my phone (HTC ONE M7 EU with no carrier , bough directly from ) trying to update it to the latest version (i had mine unlocked and rooted to solve previous battery problems), i finally fixed it with the help of an user of this community
I have now an S-off HTC One GPE with 4.4.4 (via OTA update after flashing a RUU zip)
I kinda not like GPE and i think i should back to Sense .
Can anyone point me to the correct RUU thread and/or instructions or presequisites i shoult take account to do this process?
Thanks in advance
Click to expand...
Click to collapse
here are some links, if you're going to use a signed/encryped ruu, then you'll need to downgrade hboot first https://www.androidfilehost.com/?fid=23329332407580580
http://androidruu.com/getdownload.p...31.27_10.31.1131.05_release_310878_signed.exe
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
http://androidruu.com/getdownload.p...50.13_10.33.1150.01_release_316789_signed.zip
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
https://www.androidfilehost.com/?fid=23329332407584993

Thanks. Whats the difference between signed and unsigned?

diesalher said:
Thanks. Whats the difference between signed and unsigned?
Click to expand...
Click to collapse
considering you are s-off,
very little, but even with s-off, you will first need to downgrade hboot to same or lower version than the signed ruu.exe/ruu.zip
on the other hand, a decrypted ruu.zip doesn't have that restriction
a small chart is here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
under Not So FAQ #2

nkk71 said:
considering you are s-off,
very little, but even with s-off, you will first need to downgrade hboot to same or lower version than the signed ruu.exe/ruu.zip
on the other hand, a decrypted ruu.zip doesn't have that restriction
a small chart is here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
under Not So FAQ #2
Click to expand...
Click to collapse
So my process will be...
1. Downgrade hboot to 1.44
2. Change back my cid to HTC__002 (when i flashed the RUU from the GPE i changed it to GOOGL001)
3. Flash the RUU zip
Is that right?

diesalher said:
So my process will be...
1. Downgrade hboot to 1.44
2. Change back my cid to HTC__002 (when i flashed the RUU from the GPE i changed it to GOOGL001)
3. Flash the RUU zip
Is that right?
Click to expand...
Click to collapse
you don't have to go back to hboot 1.44
If your RUU is 4.xx flash a 3.xx firmware first
or 3.xx RUU a 3.xx or 2.xx firmware will work.
you may also need the MID change tool if you changed it also
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634

clsA said:
you don't have to go back to hboot 1.44
If your RUU is 4.xx flash a 3.xx firmware first
or 3.xx RUU a 3.xx or 2.xx firmware will work.
you may also need the MID change tool if you changed it also
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
Click to expand...
Click to collapse
Ok, i'm confused,
The RUU i'g gonna flass is this
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-zip/
I'm not sure what is the version . I have installed a 4.4.4 GPE (via OTA Updates)
What should i do. downgrade the bootloader or not. Flash a firmware or not.
sorry , but i'm a bit newbie and dont want to mess up.

diesalher said:
Ok, i'm confused,
The RUU i'g gonna flass is this
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-zip/
I'm not sure what is the version . I have installed a 4.4.4 GPE (via OTA Updates)
What should i do. downgrade the bootloader or not. Flash a firmware or not.
sorry , but i'm a bit newbie and dont want to mess up.
Click to expand...
Click to collapse
The 1.28.401.7 is Jelly Bean it's equal to a 3.xx.xxx.x RUU
So the Firmware you would want is this http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/2.24.401.8.zip