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
Related
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
HTC Europe 1.28.401.7 or HTC Europe 1.20.401.1 RUU
WHICH IS BEST FOR UK usage on cid htc__001 on sim free
and which gets updates first please
geordieboy2011 said:
HTC Europe 1.28.401.7 or HTC Europe 1.20.401.1 RUU
WHICH IS BEST FOR UK usage on cid htc__001 on sim free
and which gets updates first please
Click to expand...
Click to collapse
Hi,
The RUU HTC Europe 1.28.401.7 is best for UK. Install this RUU from the boot loader and change the CID of your phone to HTC_001 if it's on a different carrier. The OTA update works on this RUU and will update it to 1.29XXXXX.
modandroidgoogle said:
Hi,
The RUU HTC Europe 1.28.401.7 is best for UK. Install this RUU from the boot loader and change the CID of your phone to HTC_001 if it's on a different carrier. The OTA update works on this RUU and will update it to 1.29XXXXX.
Click to expand...
Click to collapse
Are you sure? I briefly tried to restore to stock using this, and others, all I got was an error when it tried to flash ... Wouldn't let me install because the version is older than the current UK Sim Free version I'm on ... I might be wrong as I know jack **** about S-Off and changing CID's etc but I know that on my UK Sim Free One, I couldn't restore from any of the RUU's available currently as there wasn't one that matched my version.
I'm on 1.29.401.13 btw ... Oh, still no update btw to 4.2.2 lol
AllAboutTheCore said:
Are you sure? I briefly tried to restore to stock using this, and others, all I got was an error when it tried to flash ... Wouldn't let me install because the version is older than the current UK Sim Free version I'm on ... I might be wrong as I know jack **** about S-Off and changing CID's etc but I know that on my UK Sim Free One, I couldn't restore from any of the RUU's available currently as there wasn't one that matched my version.
I'm on 1.29.401.13 btw ... Oh, still no update btw to 4.2.2 lol
Click to expand...
Click to collapse
Is your device on s-off and is the bootloader unlocked. Your device has to have s-off before you can successfully flash any version of any stock ruu . You will need to change the Cid as well to 11111111 before you can flash any version.
Mine was branded from 3 uk. After setting the device to s-off using instructions from the XDA forum, the bootloader was also unlocked. I didnt need to go through HTC to unlock the bootloader.
I downloaded the european wwe version and the asia wwe versions of the RUU , changed the CID from H3G_001 to 11111111 for all versions and was able to flash these roms to the phone . It even lets you flash a lower version. I then changed the CID FROM 11111111 to HTC_001 for europe and was able to download OTA updates. I even flashed the Asia version and this worked as well with the asia wwe cid.you can only flash these suceessfully if the device is s-off, bootloader unlocked and cid changed to the universal id which is 11111111. Instructiions can be found on this forum.
modandroidgoogle said:
Is your device on s-off and is the bootloader unlocked. Your device has to have s-off before you can successfully flash any version of any stock ruu . You will need to change the Cid as well to 11111111 before you can flash any version.
Mine was branded from 3 uk. After setting the device to s-off using instructions from the XDA forum, the bootloader was also unlocked. I didnt need to go through HTC to unlock the bootloader.
I downloaded the european wwe version and the asia wwe versions of the RUU , changed the CID from H3G_001 to 11111111 for all versions and was able to flash these roms to the phone . It even lets you flash a lower version. I then changed the CID FROM 11111111 to HTC_001 for europe and was able to download OTA updates. I even flashed the Asia version and this worked as well with the asia wwe cid.you can only flash these suceessfully if the device is s-off, bootloader unlocked and cid changed to the universal id which is 11111111. Instructiions can be found on this forum.
Click to expand...
Click to collapse
Cool ... Like I said, I wasn't sure, my phone is S-On btw so that would explain it lol
AllAboutTheCore said:
Cool ... Like I said, I wasn't sure, my phone is S-On btw so that would explain it lol
Click to expand...
Click to collapse
You don't need to s-off to downgrade you can use the toolbox software to run mainver error check (needs root) to trick the phone into thinking its on 1.00 of hoot then you can downgrade with the RUU.
daleski75 said:
You don't need to s-off to downgrade you can use the toolbox software to run mainver error check (needs root) to trick the phone into thinking its on 1.00 of hoot then you can downgrade with the RUU.
Click to expand...
Click to collapse
Always good to learn something! .. I'm on stock, unrooted at mo though and have no plans to change that ... Yet lol
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.
Hi, I'm s-off and CID 11111111 and I'm in Canada, I flashed this
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed and every thing worked perfectly, then I changed my CID to HTC___Y13 to get the latest OTA update, when the update finished downloading I got a message saying that my HTC is running modified software or something like that and for my safty the update will not install.
What wrong here? can't I get the update this way?
Thank you...
nisayramo said:
Hi, I'm s-off and CID 11111111 and I'm in Canada, I flashed this
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed and every thing worked perfectly, then I changed my CID to HTC___Y13 to get the latest OTA update, when the update finished downloading I got a message saying that my HTC is running modified software or something like that and for my safty the update will not install.
What wrong here? can't I get the update this way?
Thank you...
Click to expand...
Click to collapse
at the very least, its because you have a custom recovery. Thats why the OTA failed
Where can I download stock recovery? and if i got it what i did should work in theory right?
If after you've flashed ruu, didn't flash anything .You already have stock recovery!
Other words ,after RUU you at the stock recovery.
What your MID?
"RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed" seems for 0710000 MID.
More likely,the reason of fault OTA - you are unable to meet mid OTA update.
tash2013 said:
If after you've flashed ruu, didn't flash anything .You already have stock recovery!
Other words ,after RUU you at the stock recovery.
What your MID?
"RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed" seems for 0710000 MID.
More likely,the reason of fault OTA - you are unable to meet mid OTA update.
Click to expand...
Click to collapse
Oh, I see thank you for the help.. My MID is PN0712000
You are trying to flash the OTA to htc__y13 cid/0710000 mid on phone with 07120000 mid - it's a bad idea.
What to do?
1) You can change mid, but I strongly DO NOT advise - this is a dangerous procedure.
2) You can flash the RUU for your mid and just wait for the OTA update will come to you - it is good
tash2013 said:
You are trying to flash the OTA to htc__y13 cid/0710000 mid on phone with 07120000 mid - it's a bad idea.
What to do?
1) You can change mid, but I strongly DO NOT advise - this is a dangerous procedure.
2) You can flash the RUU for your mid and just wait for the OTA update will come to you - it is good
Click to expand...
Click to collapse
I'm trying to find An RUU for my MID can you help? and of course thank you..
nisayramo said:
I'm trying to find An RUU for my MID can you help? and of course thank you..
Click to expand...
Click to collapse
What your originally CID?
And more.. just an advise .. under your current condition (after europe RUU) do not going to s-on never.
tash2013 said:
What your originally CID?
And more.. just an advise .. under your current condition (after europe RUU) do not going to s-on never.
Click to expand...
Click to collapse
My Origianl CID is BM___001, and got it s-off for ever
Unfortunately, I don't oriented to the North American operators,and I do not know what is BM .
And therefore can't advise the exact RUU
OK, let's go through the first way, under your current state change your mid to European
type:* fastboot oem writemid PN0710000
Stop stop! Before change mid type here your : fastboot getvar all
tash2013 said:
Unfortunately, I don't oriented to the North American operators,and I do not know what is BM .
And therefore can't advise the exact RUU
OK, let's go through the first way, under your current state change your mid to European
type:* fastboot oem writemid PN0710000
Stop stop! Before change mid type here your : fastboot getvar all
Click to expand...
Click to collapse
BM is Bell Mobility
I did not find your BM RUU from here
http://forum.xda-developers.com/showthread.php?p=39588860
and here
http://www.androidfiles.org/ruu/?developer=M7
Only a nandroid backup ,but I think it is not full stock, at least a stock recovery is missing and I'm afraid something else.
Time you were already flashed by the European RUU, let will change MID to European. And you will be have completely European unbranded phone.
if you decide do it .. print here " fastboot getvar all" (without your imei) I'll check your current state.
Hi 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.