[Q] Can I downgrade 6.06 to 1.29 with S-OFF - One (M7) Q&A, Help & Troubleshooting

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.

Related

[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] Going back to Stock ATT

hello everyone,
i recently changed my ATT HTC to International version with Mid-PN0710000 and CID- HTC_J15 and i would like to go back to stock ATT, im currently running 4.3, S-OFF,unlocked and HBOOT-1.55.. i should change my CID and MID to ATT and then what ??
biopl said:
hello everyone,
i recently changed my ATT HTC to International version with Mid-PN0710000 and CID- HTC_J15 and i would like to go back to stock ATT, im currently running 4.3, S-OFF,unlocked and HBOOT-1.55.. i should change my CID and MID to ATT and then what ??
Click to expand...
Click to collapse
and then go there: http://forum.xda-developers.com/showthread.php?t=2541082
Best guide on how to return stock.
hope it help
alray said:
and then go there: http://forum.xda-developers.com/showthread.php?t=2541082
Best guide on how to return stock.
hope it help
Click to expand...
Click to collapse
thanks for quick reply.... downgrading Hboot, will it work on any S-off device??
biopl said:
thanks for quick reply.... downgrading Hboot, will it work on any S-off device??
Click to expand...
Click to collapse
yes
But before downgrading hboot, check what RUU are available for ATT. I think there is a 3.xx.502.x RUU that works with hboot 1.55
alray said:
yes
But before downgrading hboot, check what RUU are available for ATT. I think there is a 3.xx.502.x RUU that works with hboot 1.55
Click to expand...
Click to collapse
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2
this RUU.exe should be good ryt ?
biopl said:
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2
this RUU.exe should be good ryt ?
Click to expand...
Click to collapse
yes that's the one and on a side note theirs a decrypted version RUU.zip of it that will work with your current MID and CID with a small alteration to the android-info.txt
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Instructions for Flashing RUU Zip Files:
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
adb reboot-bootloader
Now use these fastboot commands:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
fastboot reboot
**Notes about the RUU.zip method. You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first. If you are running the RUU.zip as base to downgrade all your firmware because you are going to then going to restore a stock Nandroid so the RUU might not be made for your MID, so you may need to edit the android-info.txt inside the ruu.zip to include your MID or CID.
Click to expand...
Click to collapse
clsA said:
yes that's the one and on a side note theirs a decrypted version RUU.zip of it that will work with your current MID and CID with a small alteration to the android-info.txt
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Click to expand...
Click to collapse
i have changed my cid and mid to ATT, now just i need to run RUU.exe ryt ?
biopl said:
i have changed my cid and mid to ATT, now just i need to run RUU.exe ryt ?
Click to expand...
Click to collapse
yes
biopl said:
i have changed my cid and mid to ATT, now just i need to run RUU.exe ryt ?
Click to expand...
Click to collapse
do NOT try going S-On with that hboot version!
nkk71 said:
do NOT try going S-On with that hboot version!
Click to expand...
Click to collapse
i dont plan to
biopl said:
i dont plan to
Click to expand...
Click to collapse
:good::good:
nkk71 said:
:good::good:
Click to expand...
Click to collapse
I don't understand .. the only time it is safe to go s-on is after flashing the signed ruu
why are you saying different ?
Keep in mind I'm on the side of never going s-on for any reason!
clsA said:
I don't understand .. the only time it is safe to go s-on is after flashing the signed ruu
why are you saying different ?
Keep in mind I'm on the side of never going s-on for any reason!
Click to expand...
Click to collapse
hboot 1.55 introduced an interesting patch, when going from S-Off to S-On, after a few reboots it comes back with "tamper detected - rebooting", and then TAMPERED is back in bootloader.
NB: i cannot confirm this to be 100% true, but i've seen more than a few posts that confirm, even after a full signed ruu etc etc etc, this has happened.
only way to avoid it was to go s-on before updating to 1.55 (hence my guide says to downgrade to lowest version)

[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

Htc One AT&T trying to upgrade to lollipop using official RUU - get error 155

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!

Categories

Resources