Database Develop

Debranding Bell Incredible S to WWE?

Hey I just want to make sure of a few things before I try this... I saw the thread below but it doesn't saying anything about being able to downgrade later on. I have a Bell incS with the stock 2.3.3 version 2.28.666.3. My phone is not rooted or S-Off but I have made a gold card and was going to flash the WWE RUU 2.30.405.1 to get rid of the bloat. Is it as simple as that? Would it be possible to downgrade back to the original Bell 2.28.666.3 RUU later if I needed warranty with the gold card or not? Also any issues to worry about with debranding like radio/wifi problems or anything else? Thanks

patrick92260 said:
Hey I just want to make sure of a few things before I try this... I saw the thread below but it doesn't saying anything about being able to downgrade later on. I have a Bell incS with the stock 2.3.3 version 2.28.666.3. My phone is not rooted or S-Off but I have made a gold card and was going to flash the WWE RUU 2.30.405.1 to get rid of the bloat. Is it as simple as that? Would it be possible to downgrade back to the original Bell 2.28.666.3 RUU later if I needed warranty with the gold card or not? Also any issues to worry about with debranding like radio/wifi problems or anything else? Thanks
Click to expand...
Click to collapse
If you don't have S-OFF on your BM IncS, then you won't be able to flash the WWE 2.30.405.1 RUU because that ROM is for the S710E model (model id PG321300) and the BM Incs is a S710A model (model id PG321200) and it will fail with 'wrong model id' error.
If you go ahead and S-OFF, then you can take the WWE 2.30.405.1 RUU and extract the ROM.zip and modify the android-info.txt file in the ROM.zip to change the model id. After that process, you would copy the modified ROM.zip file to the root of your SD card and rename it PG32IMG.zip. Then boot into HBOOT and it will find the PG32IMG.zip file and ask if you want to apply the update. You will then have an unbranded, unrooted IncS. The second advantage of S-OFF is that it will allow you to reflash the BM 2.28.666.3 RUU.

I'm looking at doing the same thing. Wondering if patrick92260 has had any success. I have the Virgin IS and want to debrand it as its loaded with useless BELL apps. Will be attempting this myself, let you know how it goes.
Q: First question is, now that I have the .exe of RUU. How do I go about getting the ROM.zip file.
Figured it out on my own, but for others who are curious.
A:Windows > Run > %TEMP%
Then list by 'last modified folder' and it should be the first one there.

I decided not to debrand the phone because of the different model ID for the Canadian IncS. If you debrand the phone to a WWE RUU it most likely won't ever be able to get an OTA update because when it's tries to update the phone's model ID will still be different. If there is no RUU for that new update then you'll probably be stuck with what you have.
Maybe if the IncS ever gets an actual radio S-Off I will try it.
If you still tried to debrand it though, how did it go?

patrick92260 said:
I decided not to debrand the phone because of the different model ID for the Canadian IncS. If you debrand the phone to a WWE RUU it most likely won't ever be able to get an OTA update because when it's tries to update the phone's model ID will still be different. If there is no RUU for that new update then you'll probably be stuck with what you have.
Maybe if the IncS ever gets an actual radio S-Off I will try it.
If you still tried to debrand it though, how did it go?
Click to expand...
Click to collapse
Just a point of clarification. When I debranded my Bell IncS, I put the original WWE GB 2.12.405.7 ROM on it. I then received the OTA notification that 2.30.405.1 was available, so even though you won't get a Bell OTA, you do get the WWE unbranded OTAs.

tpbklake said:
Just a point of clarification. When I debranded my Bell IncS, I put the original WWE GB 2.12.405.7 ROM on it. I then received the OTA notification that 2.30.405.1 was available, so even though you won't get a Bell OTA, you do get the WWE unbranded OTAs.
Click to expand...
Click to collapse
Hmm maybe I'll go ahead and give it a try then. You didn't have any issues upgrading to the WWE OTA or have problems once it was debranded? I ask just because I know if you debranded the original Desire it would kill the WiFi and I think it caused reception issues.

patrick92260 said:
Hmm maybe I'll go ahead and give it a try then. You didn't have any issues upgrading to the WWE OTA or have problems once it was debranded? I ask just because I know if you debranded the original Desire it would kill the WiFi and I think it caused reception issues.
Click to expand...
Click to collapse
I have not had any issues of debranding my Bell IncS with the WWE roms.
The OTA downloaded fine, but like all OTAs, it checks to make sure you have a stock version of the previous ROM, in this case 2.12.405.7. If you have ClockworkMod installed, the OTA will fail because that isn't the stock recovery. I could have flashed the stock recovery and ran the OTA, but I choose to take the 2.30.405.1 RUU and make a rooted version of it using dsi's XDA Android kitchen and ended up flashing that.

Debranding went smoothly. Flashed the WWE just fine after editing the file.
Then went ahead and installed 4EXTRecovery and Virtuous Unity over that though.
Whether doing the debranding helped or not, I'm not sure. Either way I'm down to just essential apps in this rom, no bloatware.
As for OTA updates, who cares really. If you're on this forum, you've got enough knowledge to flash yourself and not have to wait for OTA updates to arrive.

Original Bell Incredible S rom
Any one have the OEM "stock" rom/radio/kernel from Bell in case of warranty?
I did not think about this when I flashed mine and it would be great in case the hardware fail..
everything is working perfectly fine right now so it's just a "in case" question.

neurobrake said:
Any one have the OEM "stock" rom/radio/kernel from Bell in case of warranty?
I did not think about this when I flashed mine and it would be great in case the hardware fail..
everything is working perfectly fine right now so it's just a "in case" question.
Click to expand...
Click to collapse
Yes, the shipped Bell Mobile stock Gingerbread RUU can be found here:
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed.
http://www.filefactory.com/file/cc9d...657_signed.exe
Thanks to football for posting the shipped ROMs in the Development section.

The file is gone.

tpbklake said:
Yes, the shipped Bell Mobile stock Gingerbread RUU can be found here:
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed.
http://www.filefactory.com/file/cc9d...657_signed.exe
Thanks to football for posting the shipped ROMs in the Development section.
Click to expand...
Click to collapse
justaway2 said:
The file is gone.
Click to expand...
Click to collapse
Use the link that is in this thread (must have been a bad copy and paste):
http://forum.xda-developers.com/showthread.php?t=1033922

I need this file
tpbklake said:
Use the link that is in this thread (must have been a bad copy and paste):
http://forum.xda-developers.com/showthread.php?t=1033922
Click to expand...
Click to collapse
I need this file. Can you please update the link? Point me to it.

digitzgal said:
I need this file. Can you please update the link? Point me to it.
Click to expand...
Click to collapse
Go to the site HTCDEV.com and you can download the final ICS RUU.

Followup question
Thanks a tonne for responding.
I''ve an HTC Incredible S, it was at Bell's stock version, RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed. I followed this guide(http://forum.xda-developers.com/showthread.php?t=2118187) to root, install recovery-clockwork-5.0.2.0-vivo.img and soff my phone. I did not install any custom images on it.
In order to unroot and install the HTC OTA update/RUU:
Can I directly run this zip from HTC site and will it work? OR do I need to follow some other procedure to downgrade my phone to the default image(v2.3) and then upgrade to v4.0 ?
I found this v4.0 for Incrediable S for NAM (Canada) listed on HTCDEV site. Nothing else v2.3 or anything for Bell is listed there.
Incredible S
HTC
NAM (Canada)
RUU
N/A
v4.0 374.4 MB
4.14.405.2

digitzgal said:
Thanks a tonne for responding.
I''ve an HTC Incredible S, it was at Bell's stock version, RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed. I followed this guide(http://forum.xda-developers.com/showthread.php?t=2118187) to root, install recovery-clockwork-5.0.2.0-vivo.img and soff my phone. I did not install any custom images on it.
In order to unroot and install the HTC OTA update/RUU:
Can I directly run this zip from HTC site and will it work? OR do I need to follow some other procedure to downgrade my phone to the default image(v2.3) and then upgrade to v4.0 ?
I found this v4.0 for Incrediable S for NAM (Canada) listed on HTCDEV site. Nothing else v2.3 or anything for Bell is listed there.
Incredible S
HTC
NAM (Canada)
RUU
N/A
v4.0 374.4 MB
4.14.405.2
Click to expand...
Click to collapse
No, if you have BlackRose S-OFF, you will not be able to flash the 4.14.405.2 RUU. There is a link in my signature that is a stock, rooted ROM based on this RUU that you can safely install. I would recommend that along with poondog's kernel that is also linked in my signature.

Followup
Thanks tpbklake,
I didn't perform Step11, to install Blackrose.
I followed, Step 1, Skipped 2. Couldn't follow Step3, since I had bootrom HBOOT 1.13.0000, I could never get the OEM identifier token. Then I directly performed Step 9 to get revolutionary soff. Then I followed Step 4,5 to install clockwork recovery and root my phone. Then I performed Step 6. That's it. No other steps or flashing of custom rom.
Can I go ahead with the 4.0 RUU from HTCDev?

digitzgal said:
Thanks tpbklake,
I didn't perform Step11, to install Blackrose.
I followed, Step 1, Skipped 2. Couldn't follow Step3, since I had bootrom HBOOT 1.13.0000, I could never get the OEM identifier token. Then I directly performed Step 9 to get revolutionary soff. Then I followed Step 4,5 to install clockwork recovery and root my phone. Then I performed Step 6. That's it. No other steps or flashing of custom rom.
Can I go ahead with the 4.0 RUU from HTCDev?
Click to expand...
Click to collapse
No. Run the blackrose tool. (Make sure you have CM7 or another rooted ROM for this). Fully run it so that now, in the bootloader, instead of Revolutionary, You should see Blackrose. Then run the tool again but this time select Uninstall Blackrose and at the end of that, you should have HBOOT 1.13.0000. Relock bootloader and then run the RUU.
Or you can just use tbpklake's stock rooted ROM. That was built off the lateset WWE RUU I believe.

072665995 said:
No. Run the blackrose tool. (Make sure you have CM7 or another rooted ROM for this). Fully run it so that now, in the bootloader, instead of Revolutionary, You should see Blackrose. Then run the tool again but this time select Uninstall Blackrose and at the end of that, you should have HBOOT 1.13.0000. Relock bootloader and then run the RUU.
Or you can just use tbpklake's stock rooted ROM. That was built off the lateset WWE RUU I believe.
Click to expand...
Click to collapse
Thanks I can't use rooted ROM for a test I am doing.
So keep following the previous guide(http://forum.xda-developers.com/showthread.php?t=2118187) to perform Steps 10,11 for flashing CM7 and Blackrose. Then re-run Blackrose utility to uninstall it. Then lock the bootloader and run RUU from htcdev. Correct?
How do I lock the bootloader again?

digitzgal said:
Thanks I can't use rooted ROM for a test I am doing.
So keep following the previous guide(http://forum.xda-developers.com/showthread.php?t=2118187) to perform Steps 10,11 for flashing CM7 and Blackrose. Then re-run Blackrose utility to uninstall it. Then lock the bootloader and run RUU from htcdev. Correct?
How do I lock the bootloader again?
Click to expand...
Click to collapse
Ok now I'm just freaking confused. What are you trying to do?? Are you trying to root?? Or what??

[Q] Can go back to ruu but can't get OTA updates

I downgrade my phone using the downgrade script and i can install roms, s-off and s*on again. Everything fine but getting OTA's. Even I use the Sense 2.1 roms, when I try to check updates it says "no update found" as I noticed I don't have any way to go back my first shipped rom. (Stickied post didn't have original turkish rom, I tried lots of them)
How can I get OTA updates again? I know this is not a big problem but I want to know it anyway.
I noticed the "CID" thing and I think problem is CID itself. Because my CID and RUU differences.. I didn't find any detailed explanation about it. For ex. Is it can be reverted if I change the CID? What is the best CID for the getting updates first? Or are there any other method for OTA?
Sorry if I miss anything.

Any thoughts?

Özgürce said:
Any thoughts?
Click to expand...
Click to collapse
Yes it is probably due to the fact that you are running a RUU that doesn't match your CID and region.
Unless you have SuperCID with a value of 11111111, you will only get notifications when your RUU and CID are correct for a region.

[Q] How to downgrade to a hboot older than 1.25 [Solved]

Is there anyway to downgrade to older version of hboot?
Now, i am on hboot 1.25.My phone is thailand region.
I cant install stock ruu.i have 140 error all the time.
I think RUU is too old but i dont know where to find a newer version.
I download ruu from stickied topic in development forum.
http://forum.xda-developers.com/showthread.php?t=1317895
I think that is the only ruu for thailand region. Anyone can help?
Many thanks.
Btw, my phone is still s-on and i think i cant s-off because i still want a warranty(that is why i am trying to go back to stock rom). Please help.
Sorry for my English. I am not good at English(I am Thai).

KazumaSaruwatari said:
Is there anyway to downgrade to older version of hboot?
Now, i am on hboot 1.25.My phone is thailand region.
I cant install stock ruu.i have 140 error all the time.
I think RUU is too old but i dont know where to find a newer version.
I download ruu from stickied topic in development forum.
http://forum.xda-developers.com/showthread.php?t=1317895
I think that is the only ruu for thailand region. Anyone can help?
Many thanks.
Btw, my phone is still s-on and i think i cant s-off because i still want a warranty(that is why i am trying to go back to stock rom). Please help.
Sorry for my English. I am not good at English(I am Thai).
Click to expand...
Click to collapse
There are only 2 versions of Hboot -> 1.25 and 1.28, there are no official older versions, maybe beta or engineering ones that were not released publicly.
You can S-OFF with unprotected Hboot, but this is not needed for you, check your CID from your phone and flash the according RUU for it, if not, take this tool and flash the S-OFF for 1.25 and after that you can flash any RUU you want as it bypasses that (as far as i know), after the RUU flashing, the HBOOT will be overwrited as well, so you will end up with a stock, locked, S-ON device with the region-stock ROM of your choice, hope this helps

Lexmazter said:
There are only 2 versions of Hboot -> 1.25 and 1.28, there are no official older versions, maybe beta or engineering ones that were not released publicly.
You can S-OFF with unprotected Hboot, but this is not needed for you, check your CID from your phone and flash the according RUU for it, if not, take this tool and flash the S-OFF for 1.25 and after that you can flash any RUU you want as it bypasses that (as far as i know), after the RUU flashing, the HBOOT will be overwrited as well, so you will end up with a stock, locked, S-ON device with the region-stock ROM of your choice, hope this helps
Click to expand...
Click to collapse
I just did what you say.
I S-OFF my phone.
I relock bootloader.
Then, I install RUU. It seems to run smoothly but in the end error 140 came up and my phone is S-ON again with still old custom rom.
What should I do?

KazumaSaruwatari said:
I just did what you say.
I S-OFF my phone.
I relock bootloader.
Then, I install RUU. It seems to run smoothly but in the end error 140 came up and my phone is S-ON again with still old custom rom.
What should I do?
Click to expand...
Click to collapse
Well, as far as i know, you unlock the bootloader again, S-OFF, and after that you flash the RUU, i didn't install any RUU's until now, you should check the guide from stona15 that can be found here, There are more details about what to do and what you want.
Hope this helps

RUU

Hi guys, i just want to be on the safe side before doing anything like S-off, so i wonder how do i find which RUU is made for my phone model ? i have tried searching but didn't get anywhere.

http://forum.xda-developers.com/showthread.php?p=39588860
No offense but you didn't look very hard. Its in a sticky in the dev thread
Once you s-off (which is ridiculously easy for this device) you can use any RUU. Good luck and enjoy
Sent from my One using Tapatalk 2

Anicane said:
Hi guys, i just want to be on the safe side before doing anything like S-off, so i wonder how do i find which RUU is made for my phone model ? i have tried searching but didn't get anywhere.
Click to expand...
Click to collapse
You haven't said what OS you're on or what Hboot you have, S-Off might not even be an option, nor might an RUU if you are on a 2.24 base with Hboot 1.54 ... A little more info would help to make sure you are given the best, most accurate advice.

AllAboutTheCore said:
You haven't said what OS you're on or what Hboot you have, S-Off might not even be an option, nor might an RUU if you are on a 2.24 base with Hboot 1.54 ... A little more info would help to make sure you are given the best, most accurate advice.
Click to expand...
Click to collapse
I haven't updated my phone to this new Hboot 1.54, i am still on with the old one, i have read not to update if i want S-Off. The reason i want this is because if suddenly i had to return my phone to a service or something, i don't want to void my warranty. If i am not wrong when you S-Off, you can reverse it also.

Anicane said:
I haven't updated my phone to this new Hboot 1.54, i am still on with the old one, i have read not to update if i want S-Off. The reason i want this is because if suddenly i had to return my phone to a service or something, i don't want to void my warranty. If i am not wrong when you S-Off, you can reverse it also.
Click to expand...
Click to collapse
Cool, yes, you are correct, S-Off can be reverted ... It's also worth noting that if you S-Off now, you'd be able to upgrade to Hboot 1.54 and still maintain S-Off. The problem lies with those, like me, who are on the 1.54 Hboot but haven't gone S-Off ... We're now stuck until a solution is available, although I didn't want to go S-Off so it's not really a problem.
If you go S-Off btw you can flash any RUU from any region and change your Cid/Mid, although I can't help you on the whole RUU when S-Off process as I've never run one, nor been S-Off as I previously mentioned lol.

I still can't find which RUU is for my phone, is there anyway to find ? is it via CID or any other way ?

What software build are you on at the moment? So to Settings>About phone>Software information and post the version, e.g. 2.24.401.8

EddyOS said:
What software build are you on at the moment? So to Settings>About phone>Software information and post the version, e.g. 2.24.401.8
Click to expand...
Click to collapse
It is 1.29.401.16

Anicane said:
It is 1.29.401.16
Click to expand...
Click to collapse
There is an RUU ZIP for that somewhere but I can't find it. I'm sure someone has a link to it somewhere!

EddyOS said:
There is an RUU ZIP for that somewhere but I can't find it. I'm sure someone has a link to it somewhere!
Click to expand...
Click to collapse
I didn't find an actuall 1.29.401.16 RUU, but there is some zips, which i am kinda not interested. But i found 1.29.401.12 OTA's . So i want to know if it is possible to flash the 1.29.401.12 and let the Htc one update itself ? and than do an S-on if i wanted to return it to a service ?

Anicane said:
I didn't find an actuall 1.29.401.16 RUU, but there is some zips, which i am kinda not interested. But i found 1.29.401.12 OTA's . So i want to know if it is possible to flash the 1.29.401.12 and let the Htc one update itself ? and than do an S-on if i wanted to return it to a service ?
Click to expand...
Click to collapse
The 1.29.401.16 ZIP is the RUU but in ZIP format so it's the same thing. Basically in the RUU.exe there is a ZIP called ROM.zip - this is what is the actual ROM and is flashed via the RUU in fastboot mdoe. It's fine and it's the one you want as there is nothing else available for your phone

EddyOS said:
The 1.29.401.16 ZIP is the RUU but in ZIP format so it's the same thing. Basically in the RUU.exe there is a ZIP called ROM.zip - this is what is the actual ROM and is flashed via the RUU in fastboot mdoe. It's fine and it's the one you want as there is nothing else available for your phone
Click to expand...
Click to collapse
Well, i am thinking of a scenario which i don't know is possible or not, so here it goes. Since i want to be on the safe side, how about i take a nandorid back of the stock, and than if i wanted to returen to stock, simply flash an RUU like 1.29.401.16, and than simply recover the nandroid backup over it, and update if i wanted to ? Is it possible ?
The only problem is that i don't know how to remove the custom recovery when it restore the nandorid back, and update 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