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

Flashing a RUU?

Hello there
These are the current stats of my device:
ROM: TrickDroid 7.5.0
CID: superCID 11111111
S-OFF
Recovery: TWRP 2.5.0
Bootloader: Unlocked
If I want to flash a RUU, I understand that just about ANY RUU will work because I have Super CID, but I want to know if there certain prerequists to flashing a RUU? Like for instance would I have to relock bootloader, set it to S-ON, flash stock recovery first, etc?
I'll probably be flashing either one of those:
RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A .14.3250.13_10.33.1150.01_release_311678_signed.exe
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Thanks

TarekElsakka said:
Hello there
These are the current stats of my device:
ROM: TrickDroid 7.5.0
CID: superCID 11111111
S-OFF
Recovery: TWRP 2.5.0
Bootloader: Unlocked
If I want to flash a RUU, I understand that just about ANY RUU will work because I have Super CID, but I want to know if there certain prerequists to flashing a RUU? Like for instance would I have to relock bootloader, set it to S-ON, flash stock recovery first, etc?
I'll probably be flashing either one of those:
RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A .14.3250.13_10.33.1150.01_release_311678_signed.exe
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Thanks
Click to expand...
Click to collapse
You should be able to flash the ruu the way you are. The only differences between your phone and mine when I flashed the brightstar ruu is the Rom I was on and I had relocked my bootloader. S-off will be retained after the flash but twrp will be replaced with the stock recovery. If it fails to flash you can try it again after relocking the bootloader but I don't think it's necessary.

Thank you very much. I won't need the bootloader to be unlocked anyhow in order to receive OTA updates so I might as well relock it and not flash a custom recovery. I do not need to be S-ON in order to receive OTA updates, right? Just locked bootloader, RUU, stock recovery and the proper CID (like HTC__001, for instance)? And while S-OFF, is changing CID from 111111 to HTC__001 as easy as using one command like
Code:
fastboot oem writecid 11111111
?

TarekElsakka said:
Thank you very much. I won't need the bootloader to be unlocked anyhow in order to receive OTA updates so I might as well relock it and not flash a custom recovery. I do not need to be S-ON in order to receive OTA updates, right? Just locked bootloader, RUU, stock recovery and the proper CID (like HTC__001, for instance)? And while S-OFF, is changing CID from 111111 to HTC__001 as easy as using one command like
Code:
fastboot oem writecid 11111111
?
Click to expand...
Click to collapse
Your pretty much spot on... Keep in mind that for otas your model id needs to be right for the ruu you flash as well as the cid. For example my phone is a US AT&T model has the same model id for the US dev version. So I just needed to be sure to flash the US dev ruu (brightstar) and then set the correct cid (bs_us001) and life is good. Problem is I don't personally know the model id or cid for the ruus you intend to flash. The good news is you can find your model id as well as change it if you need to. The threads to do this are pretty easy to find I'll get a link if you need me too. And to confirm "fastboot oem writecid ********" is what ya need... The asterisks are of course whatever cid you intend to write.
---------- Post added at 03:35 PM ---------- Previous post was at 03:14 PM ----------
http://forum.xda-developers.com/showthread.php?t=2269317&highlight=+model+id+
You can find your model id by doing this in this thread if you need to

Thank you so much for your reply. So from what I understood, in order to go back to stock, I'd have to flash a RUU that will be compatible with my Model ID, correct? I do know what my model is, and it is PN0711000 if I am not mistaken (I have it saved on a text file somewhere), but the problem is that I will not know which model ID I need and for which RUU. And by the way, if something ever goes wrong with my device after returning it to full stock but with a different Model ID, wouldn't HTC be able to figure that out and void my warranty? Sorry for the 20 questions I am very new to this. I appreciate your help.

TarekElsakka said:
Thank you so much for your reply. So from what I understood, in order to go back to stock, I'd have to flash a RUU that will be compatible with my Model ID, correct? I do know what my model is, and it is PN0711000 if I am not mistaken (I have it saved on a text file somewhere), but the problem is that I will not know which model ID I need and for which RUU. And by the way, if something ever goes wrong with my device after returning it to full stock but with a different Model ID, wouldn't HTC be able to figure that out and void my warranty? Sorry for the 20 questions I am very new to this. I appreciate your help.
Click to expand...
Click to collapse
Just replied to you in another thread lol... Um if that's your model id I believe... Emphasis on believe... That matches the Europe ruu and possibly the Asia one too. Maybe someone who knows for sure will pop in here and confirm. As far as the warranty stuff if there is no ruu for you specific carrier then make a fresh nandroid backup of the stock Rom and with s-off can be made like it was when you bought it.

Yeah I just saw your post there, thank you lol. Unfortunately I was stupid enough not to make a Nandroid Backup of my stock ROM before I went ahead and flashed a custom one.

viperlox said:
Just replied to you in another thread lol... Um if that's your model id I believe... Emphasis on believe... That matches the Europe ruu and possibly the Asia one too. Maybe someone who knows for sure will pop in here and confirm. As far as the warranty stuff if there is no ruu for you specific carrier then make a fresh nandroid backup of the stock Rom and with s-off can be made like it was when you bought it.
Click to expand...
Click to collapse
The MID for UK RUU is PN0710000

Rex2369 said:
The MID for UK RUU is PN0710000
Click to expand...
Click to collapse
Thank you so much. So MID PN0710000 and CID HTC__001. Correct?

TarekElsakka said:
Thank you so much. So MID PN0710000 and CID HTC__001. Correct?
Click to expand...
Click to collapse
Yeah that is correct.

[Q] HTC One debranding

Hi all, just wondering if someone with some knowledge can help assist me debranding my HTC One. I came from Samsung devices, and knew the ins and outs of rooting, flashing roms etc, but HTC devices seems so over complicated after reading through various forums.
All I want to do is debrand my Vodafone HTC One, and install the international uk firmware, and be able to receive ota updates in future.
I have been reading about changing Ruu, changing CID, and im just baffled by everything, although slowly starting to gain some knowledge.
Please I would appreciate if someone could give me the correct procedure to do this, do I need to unlock the bootloader before doing it? Already registered on HTCDEV website, just havnt unlocked bootloader yet.
I have spent hours reading info, and my head is practically going round in circles lol.

What do you mean by debranding? Do you mean putting a custom Rom on it?
Edit: I missed a section of what you said. I believe you have to unlock the bootloader, turn security off, and get Super CID.
Sent from my HTCONE using xda premium

Sent from my SPH-L900 using xda app-developers app

Thank you, So I need to unlock bootloader, get s-off, then install supercid. Then all I do is install the international stock rom? and I will receive ota updates?

I believe so, but you must have the international stock recovery on too for the OTA updates to work.
Sent from my HTCONE using xda premium

honda1979 said:
Hi all, just wondering if someone with some knowledge can help assist me debranding my HTC One. I came from Samsung devices, and knew the ins and outs of rooting, flashing roms etc, but HTC devices seems so over complicated after reading through various forums.
All I want to do is debrand my Vodafone HTC One, and install the international uk firmware, and be able to receive ota updates in future.
I have been reading about changing Ruu, changing CID, and im just baffled by everything, although slowly starting to gain some knowledge.
Please I would appreciate if someone could give me the correct procedure to do this, do I need to unlock the bootloader before doing it? Already registered on HTCDEV website, just havnt unlocked bootloader yet.
I have spent hours reading info, and my head is practically going round in circles lol.
Click to expand...
Click to collapse
All the following is dependant on having an hboot of less than 1.54. If you are already on hboot 1.54, you will not yet be able to s-off and follow this process until an exploit is found for the 1.54 hboot. To check this, turn off your device and restart it whilst holding the volume down button. The information will be displayed.
1 Get S-Off http://forum.xda-developers.com/showthread.php?t=2314582
2 Install super cid : fastboot oem writecid 11111111
3 Run RUU 1.28.401.7 http://forum.xda-developers.com/showthread.php?t=2207874
4 Change cid to generic : fastboot oem writecid HTC__001
You will now receive ota updates to 2.24.401.1

honda1979 said:
Thank you, So I need to unlock bootloader, get s-off, then install supercid. Then all I do is install the international stock rom? and I will receive ota updates?
Click to expand...
Click to collapse
Run revone, unlocked bootloader and s-off
change CID to HTC__001 or 11111111
run RUU for international M7 i would start with PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio_4A.14.3250.13_10.33.1150.01_release_318486_signed_2_4
once this is on the phone you should get all the OTA releases bringing you up to date.

bobsie41 said:
All the following is dependant on having an hboot of less than 1.54. If you are already on hboot 1.54, you will not yet be able to s-off and follow this process until an exploit is found for the 1.54 hboot. To check this, turn off your device and restart it whilst holding the volume down button. The information will be displayed.
1 Get S-Off http://forum.xda-developers.com/showthread.php?t=2314582
2 Install super cid : fastboot oem writecid 11111111
3 Run RUU 1.28.401.7 http://forum.xda-developers.com/showthread.php?t=2207874
4 Change cid to generic : fastboot oem writecid HTC__001
You will now receive ota updates to 2.24.401.1
Click to expand...
Click to collapse
Thanks for that info mate. I just checked and im on hboot 1.54, which means I wont be able to do this at the moment. Was that RUU you state an exe file? I guess I don't have to root or install any custom recovery to do this? First I need to wait on an exploit for sboot 1.54 to get s-off. Also it might be easier for me going down the custom rom route?

honda1979 said:
Thanks for that info mate. I just checked and im on hboot 1.54, which means I wont be able to do this at the moment. Was that RUU you state an exe file? I guess I don't have to root or install any custom recovery to do this? First I need to wait on an exploit for sboot 1.54 to get s-off. Also it might be easier for me going down the custom rom route?
Click to expand...
Click to collapse
Until s-off is achieved for hboot 1.54, your only choice is custom roms. This should be fine as you are already updated to the latest firmware through Vodafone.
Sent from my HTC One using xda premium

bobsie41 said:
Until s-off is achieved for hboot 1.54, your only choice is custom roms. This should be fine as you are already updated to the latest firmware through Vodafone.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Ok cheers. I thought that I needed to be S-Off before I could install any custom rom, but I could root and install custom recovery with s-on?

honda1979 said:
Ok cheers. I thought that I needed to be S-Off before I could install any custom rom, but I could root and install custom recovery with s-on?
Click to expand...
Click to collapse
Yes

needbyna mechanism
bobsie41 said:
Yes
Click to expand...
Click to collapse
Ok, now here goes lol. My understanding so far is that in order to install any stock ruu I must first get s-off. As im running stock Vodafone firmware, the CID must match this firmware. If I get s-off, I will be able to install any CID and stock rom, as long as they match one another. and as im on hboot 1.54 just now, supercid wont work yet, so s-off is a no no at the moment. I can still root and install a custom firmware though.

changing CID

Hi all, I was on cid HTC__332 but then i got SuperCID since HTC__332 was slow on updates, now i want to go back to stock, can i get Taiwan CID instead of my original CID since Taiwan is fast on updates, so can i write Taiwanese CID HTC__621 instead of my original stock CID? any help will be much appreciated , thanks

muhammad.uzi1994 said:
Hi all, I was on cid HTC__332 but then i got SuperCID since HTC__332 was slow on updates, now i want to go back to stock, can i get Taiwan CID instead of my original CID since Taiwan is fast on updates, so can i write Taiwanese CID HTC__621 instead of my original stock CID? any help will be much appreciated , thanks
Click to expand...
Click to collapse
You can change to whatever CID you have but you MUST have same software version as your CID to receive OTA...
That means:
fastboot getvar cid = adb shell getprop ro.cid

kotag82 said:
You can change to whatever CID you have but you MUST have same software version as your CID to receive OTA...
That means:
fastboot getvar cid = adb shell getprop ro.cid
Click to expand...
Click to collapse
ok so i have one question, im on CID HTC__621 (CID for Taiwan) and MID PNO711000 (also for Taiwan/Asia region) , i'm planning to flash stock recovery, and relock my bootloader after installing Stock Taiwanese ROM, will i be able to get OTA's then? i downgraded my Hboot too , to match the stock rom base, will i get OTA's by relocking bootloader after installing stock rom? Please note that HTC__621 is not my original CID, my original was HTC__332, thanks

muhammad.uzi1994 said:
ok so i have one question, im on CID HTC__621 (CID for Taiwan) and MID PNO711000 (also for Taiwan/Asia region) , i'm planning to flash stock recovery, and relock my bootloader after installing Stock Taiwanese ROM, will i be able to get OTA's then? i downgraded my Hboot too , to match the stock rom base, will i get OTA's by relocking bootloader after installing stock rom? Please note that HTC__621 is not my original CID, my original was HTC__332, thanks
Click to expand...
Click to collapse
you don't need to relock bootloader as you S-OFF to receive/apply OTA but completely stock is a MUST including stock recovery

kotag82 said:
you don't need to relock bootloader as you S-OFF to receive/apply OTA but completely stock is a MUST including stock recovery
Click to expand...
Click to collapse
ok so the fact that HTC__621 isnt my ORIGINAL cid and that i changed to it from HTC__332 wont cause any trouble with the OTA and firmware, right?

muhammad.uzi1994 said:
ok so the fact that HTC__621 isnt my ORIGINAL cid and that i changed to it from HTC__332 wont cause any trouble with the OTA and firmware, right?
Click to expand...
Click to collapse
It should not be any problem, if any I will help you. What CID you have now? if possible stay with supercid

kotag82 said:
It should not be any problem, if any I will help you. What CID you have now? if possible stay with supercid
Click to expand...
Click to collapse
i have HTC__621 now, i had SuperCID before but i'm returning to Taiwanese stock ROM as i had some issues with the custom ROM's , i'll holla at you in this thread if i need any help, thanks and i have model id PN0711000 , and i downgraded my hboot, now i'm downloading Guru's stock Reset ROM 2.24.709.1 , after installing this ROM , i'll update to the corresponding firmware , then relock my bootloader, i will however keep s off

muhammad.uzi1994 said:
i have HTC__621 now, i had SuperCID before but i'm returning to Taiwanese stock ROM as i had some issues with the custom ROM's , i'll holla at you in this thread if i need any help, thanks and i have model id PN0711000 , and i downgraded my hboot, now i'm downloading Guru's stock Reset ROM 2.24.709.1 , after installing this ROM , i'll update to the corresponding firmware , then relock my bootloader, i will however keep s off
Click to expand...
Click to collapse
bear in mind you need to downgradeto unlock bootloader again via revone, locked/unlocked bootloader check are skipped as you s-off, I'm receiving and applying OTA with unlocked bootloader without any problems

kotag82 said:
bear in mind you need to downgradeto unlock bootloader again via revone, locked/unlocked bootloader check are skipped as you s-off, I'm receiving and applying OTA with unlocked bootloader without any problems
Click to expand...
Click to collapse
so you mean that if i have s off, i can receive OTA without locking bootloader?
EDIT: i am now on OS 2.24.709.1 with hboot 1.54, unlocked and s off , running stock taiwanese 4.2.2 ROM, i receive OTA update to 4.3 and it downloads fine too, but when i choose to install it , the phone boots up into recovery, the progress bar goes halfway and then i get a red exclamation mark icon and i have to restart my phone, can you tell me what i'm doing wrong?when i press power button and volume up and down simultaneously to get the menu in recovery, i see error "cannot mount sd card, fail 1 times" upto 4 times and also there is a Tamper flag on the recovery menu , my bootloader is unlocked but Tampered and i'm on hboot 1.54

muhammad.uzi1994 said:
so you mean that if i have s off, i can receive OTA without locking bootloader?
EDIT: i am now on OS 2.24.709.1 with hboot 1.54, unlocked and s off , running stock taiwanese 4.2.2 ROM, i receive OTA update to 4.3 and it downloads fine too, but when i choose to install it , the phone boots up into recovery, the progress bar goes halfway and then i get a red exclamation mark icon and i have to restart my phone, can you tell me what i'm doing wrong?when i press power button and volume up and down simultaneously to get the menu in recovery, i see error "cannot mount sd card, fail 1 times" upto 4 times and also there is a Tamper flag on the recovery menu , my bootloader is unlocked but Tampered and i'm on hboot 1.54
Click to expand...
Click to collapse
did you run RUU? how come you have Tampered? Did you flash custom 2.24.709.1 firmware or original signed one? Can you attach updater-script from OTA (META-INF\com\google\android)

kotag82 said:
did you run RUU? how come you have Tampered? Did you flash custom 2.24.709.1 firmware or original signed one? Can you attach updater-script from OTA (META-INF\com\google\android)
Click to expand...
Click to collapse
i flashed the original signed one https://www.dropbox.com/s/u57lqm3alw05h3q/updater-script.rar and here it is

[Q] Need help figuring out how to update

I have an ATT M7. I am on T-Mobile. The phone is now unlocked. It is still running Android 4.3.
ATT software update doesn't find any updates - presumably because I need an ATT sim in there.
So how can I upgrade this to 4.4 and later 5.0?
Thanks!

808phone said:
I have an ATT M7. I am on T-Mobile. The phone is now unlocked. It is still running Android 4.3.
ATT software update doesn't find any updates - presumably because I need an ATT sim in there.
So how can I upgrade this to 4.4 and later 5.0?
Thanks!
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number

808phone said:
I have an ATT M7. I am on T-Mobile. The phone is now unlocked. It is still running Android 4.3.
ATT software update doesn't find any updates - presumably because I need an ATT sim in there.
So how can I upgrade this to 4.4 and later 5.0?
Thanks!
Click to expand...
Click to collapse
convert the phone to Developers Edition
http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
http://forum.xda-developers.com/htc-one/general/stock-rom-reset-developer-edition-t2915170
Thanks @alray

So I did more reading and yes developer edition or change CID and MID to T-Mobile
All require S-OFF.
So I need to unlock boot loader, install TWRP, S-OFF. etc?
This is the blue Best Buy version ATT - but ATT just unlocked it.
M7_UL PVT SHIP S-ON RH
HBOOT 1.55
Radio-4T.20.3218.13

808phone said:
So I did more reading and yes developer edition or change CID and MID to T-Mobile
All require S-OFF.
So I need to unlock boot loader, install TWRP, S-OFF. etc?
This is the blue Best Buy version ATT - but ATT just unlocked it.
M7_UL PVT SHIP S-ON RH
HBOOT 1.55
Radio-4T.20.3218.13
Click to expand...
Click to collapse
thats why I asked for your fastboot getvar all, unlock your bootloader and use rumrunner to s-off, do not take any updates until you get s-off as it gets harder the higher HBOOT you have.

Seanie280672 said:
thats why I asked for your fastboot getvar all, unlock your bootloader and use rumrunner to s-off, do not take any updates until you get s-off as it gets harder the higher HBOOT you have.
Click to expand...
Click to collapse
S-OFF now by using sunshine. I do have ADB and Fastboot working from my previous use with HTC One S.

808phone said:
OK, I believe I am S-OFF, just used sunshine.
Click to expand...
Click to collapse
well from there you can either follow clsA link and change to developer edition, which will require changing cid, mid and flash the RUU, dev edition gets the quickest updates, although its very touch and go at the moment as to whether the M7 is going to get anymore updates, or you can do the same with the latest T-mo RUU which is here: http://www.htc.com/us/support/htc-one-t-mobile/news/ that will also require you to change your cid and mid, after doing that follow the manual instructions on the HTC site, download link for the RUU is at the bottom.

Thanks!

Seanie280672 said:
well from there you can either follow clsA link and change to developer edition, which will require changing cid, mid and flash the RUU, dev edition gets the quickest updates, although its very touch and go at the moment as to whether the M7 is going to get anymore updates, or you can do the same with the latest T-mo RUU which is here: http://www.htc.com/us/support/htc-one-t-mobile/news/ that will also require you to change your cid and mid, after doing that follow the manual instructions on the HTC site, download link for the RUU is at the bottom.
Click to expand...
Click to collapse
808phone said:
Thanks!
Click to expand...
Click to collapse
at&t phones already have the required MID to flash the dev edition ruu (pn0712000) Only need to change the cid

alray said:
at&t phones already have the required MID to flash the dev edition ruu (pn0712000) Only need to change the cid
Click to expand...
Click to collapse
Darn it. Read this too late. OK, I changed CID to T-MOB010 and MID to PN0713000.
At this point, do I just run an RUU at some point? Hope it works.

808phone said:
Darn it. Read this too late. OK, I changed CID to T-MOB010 and MID to PN0713000.
At this point, do I just run an RUU at some point? Hope it works.
Click to expand...
Click to collapse
Yes this one >> http://www.htc.com/us/support/htc-one-t-mobile/news/

clsA said:
Yes this one >> http://www.htc.com/us/support/htc-one-t-mobile/news/
Click to expand...
Click to collapse
I used Sunshine to get S-OFF. Everywhere I read, it says I need to have the boot loader locked to apply the RUU. However, while contacting the sunshine authors, they told me that despite what I have read, I don't have to relock. Is this true?

808phone said:
I used Sunshine to get S-OFF. Everywhere I read, it says I need to have the boot loader locked to apply the RUU. However, while contacting the sunshine authors, they told me that despite what I have read, I don't have to relock. Is this true?
Click to expand...
Click to collapse
no you dont need to lock as your s-off, unlocked is fine.
locked / relocked for flashing firmware or RUU's is only required for s-on users and limited to 1 step forward or current only.

So now the ruu times out on sending.......
So I extracted the rom.zip. If I flash it from twrp since it has a recovery image in it, will it overwrite twrp?
I'm assuming yes and then I would have to fast boot twrp back again.
Is this correct? Thanks

Gave up and installed Maximus HD. Works fine. Just wanted to be on 5.0 to test things.

808phone said:
Gave up and installed Maximus HD. Works fine. Just wanted to be on 5.0 to test things.
Click to expand...
Click to collapse
Anyone know what the first part of this means? (unaligned ruu)
Where would I get this????
> Use an unaligned ruu or a matching hboot ruu