[Q] Do I need SuperCID? - One (M7) Q&A, Help & Troubleshooting

Hello there
A few ago I used revone's guide in order to go S-OFF and it worked. I have a few questions regarding RUUs and OTAs:
1) If there's an RUU that is NOT for my device (say my device is international and the RUU is for Asia or Europe, for instance) and my device is S-OFF, can I still install it and would it work properly?
2) My CID is HTC__J15 and we always receive OTA updates LAST (at least that's how it was on my HTC One X), if I change the CID to HTC__001, for instance, which is Europe, will I be able to receive the updates just as they do over there? And if I do change the CID, which RUU should I install in order to be stock? And would I have to change to S-OFF and be unrooted?
3) If my device is S-OFF, CID HTC__001 and I am running TrickDroid 7.5.0 and I hear of an OTA update available for HTC__001, for instance 4.2.2 JellyBean, would I have to install stock ROM and stock recovery, which is basically what an RUU does?
4) What is the benefit of SuperCID? If you can install any RUU with being S-OFF only.
Thank you very much.

Related

[SOLVED] Can't flash RUU's?

Sorry for creating a lot of help threads, but things just don't wanna work my way.
Yesterday I wanted to flash a RUU to see exactly how HTC does things and if it's easy or hard. Anyway. I come from a Galaxy S3 and if I wanted to go back to stock from any other rom, I simply flashed a stock rom tar with a program called Odin, but it doesn't seem to be as simple with HTC.
I downloaded a RUU for the Europe region as it seemed the most obvious thing to do, but my CID is Nordic (HTC__Y13). Here's how it went:
Being on a 4.2.2 custom rom:
I tried running the RUU when I was on a 4.2.2. custom rom (InsertCoin 2.0.2), and I fired up the RUU file and followed the instructions. Then it said my phone isn't supported and that I need another RUU file.
Being on a stock odexed 1.29 rom:
I then installed a stock 1.29 rom from Mike1986. and then fired up the RUU. I followed the instructions and it seems the flashing started. It sent me to the RUU mode (the HTC screen) and began the flashing process. It said it wiped the data and that it sent some signature keys, I think. Three minutes later, the RUU window disappeared. I could see the program was still running but the window disappeared. It quickly flashed for about half a second and I could see some text saying that my phone isn't supported, but why the hell did it commence the flashing?
I pulled the cable, long-pressed the power button and let it boot, it hadn't wiped a thing.
Let it be known that before I opened the RUU's, I made sure I was bootloader locked and S-ON (with the revone method).
Is it because I have the Nordic CID and I had a RUU for the European region? If so, I looked anywhere and everywhere for a Nordic RUU but there's none to be found.
Any help is appreciated.
You can only use an RUU which is the same or newer than the firmware on the phone, e.g. if your last official update was 1.29.401.13 you could only use an RUU that version or above UNLESS you're S-OFF, in which case you can use an older one if you have Super CID and a locked/relocked bootloader
EddyOS said:
You can only use an RUU which is the same or newer than the firmware on the phone, e.g. if your last official update was 1.29.401.13 you could only use an RUU that version or above UNLESS you're S-OFF, in which case you can use an older one if you have Super CID and a locked/relocked bootloader
Click to expand...
Click to collapse
So what you're saying, is:
If I acquire Super CID, then flash a Europe RUU and then set my CID back to what it originally was (or maybe even set it to HTC__001) and then reflash the RUU, and it'll work beautifully? I'm S-OFF, btw.
Theshawty said:
So what you're saying, is:
If I acquire Super CID, then flash a Europe RUU and then set my CID back to what it originally was (or maybe even set it to HTC__001) and then reflash the RUU, and it'll work beautifully? I'm S-OFF, btw.
Click to expand...
Click to collapse
Where you S-Off or S-On when you ran the RUU?
bobsie41 said:
Where you S-Off or S-On when you ran the RUU?
Click to expand...
Click to collapse
S-ON with the bootloader locked. I wanted to see if it was possible.
I'm not really looking to revert to unrooted stock, at least not now. I just want to know that it's possible without too much work for when it would be necessary or when I want to try out unrooted stock again. It's always nice to have a fallback.
Theshawty said:
S-ON with the bootloader locked. I wanted to see if it was possible.
I'm not really looking to revert to unrooted stock, at least not now. I just want to know that it's possible without too much work for when it would be necessary or when I want to try out unrooted stock again. It's always nice to have a fallback.
Click to expand...
Click to collapse
As far as I'm aware, you can only run a RUU that is relevant to you device whilst you are s-on and only one that is equal to or above the firmware that you are running.
The only way to return to official un-rooted stock is, again, to run a RUU for your device or install a completely stock nandroid backup of your device or one running the same version as yours.
OK, full example...
You originally get an unbranded One from the EU and you get the OTA to 1.29.401.13. From this point on, with an S-ON/Locked phone with CID HTC__001 you can ONLY flash an RUU which is 1.29.401.13 or higher. This will never change. If you get an RUU from a specific carrier you cannot flash it as it doesn't match your CID.
If you unlock the bootloader, but stay S-ON, you cannot flash an RUU at all - you HAVE to relock the bootloader first but you can still only flash an RUU matching your CID and is the same or newer than your current version.
If you S-OFF and change the CID to 11111111 you can flash ANY RUU you want, even those older than your current version, e.g. 1.28.401.7. You still have to have a locked/relocked bootloader but you can stay S-OFF and flash the RUU. As the only RUU available at the moment for the unbranded One is 1.28.401.7 it means you can flash that and then get the OTA updates in sequence to get to the latest version
Once back at the older version using the RUU you could change your CID back to HTC__001 if you wanted but I don't think it matters
EddyOS said:
OK, full example...
You originally get an unbranded One from the EU and you get the OTA to 1.29.401.13. From this point on, with an S-ON/Locked phone with CID HTC__001 you can ONLY flash an RUU which is 1.29.401.13 or higher. This will never change. If you get an RUU from a specific carrier you cannot flash it as it doesn't match your CID.
If you unlock the bootloader, but stay S-ON, you cannot flash an RUU at all - you HAVE to relock the bootloader first but you can still only flash an RUU matching your CID and is the same or newer than your current version.
If you S-OFF and change the CID to 11111111 you can flash ANY RUU you want, even those older than your current version, e.g. 1.28.401.7. You still have to have a locked/relocked bootloader but you can stay S-OFF and flash the RUU. As the only RUU available at the moment for the unbranded One is 1.28.401.7 it means you can flash that and then get the OTA updates in sequence to get to the latest version
Once back at the older version using the RUU you could change your CID back to HTC__001 if you wanted but I don't think it matters
Click to expand...
Click to collapse
Ah, thanks for the clarification! If I do this (Super CID plus flash the RUU), should I change back to the HTC__Y13 cid or change to something like HTC__001 to get the updates for the Europe region? I heard Europe gets OTA's faster than other regions.
One more thing, why does the bootloader have to be locked? Does the RUU check for this?
Theshawty said:
Ah, thanks for the clarification! If I do this (Super CID plus flash the RUU), should I change back to the HTC__Y13 cid or change to something like HTC__001 to get the updates for the Europe region? I heard Europe gets OTA's faster than other regions.
One more thing, why does the bootloader have to be locked? Does the RUU check for this?
Click to expand...
Click to collapse
If you wish to get ota's you will need to have a cid which is relevant to the RUU you have run. Either of those cid's should work for a x.xx.401.x RUU. Not sure about the bootloader locking for an RUU.
bobsie41 said:
If you wish to get ota's you will need to have a cid which is relevant to the RUU you have run. Either of those cid's should work for a x.xx.401.x RUU. Not sure about the bootloader locking for an RUU.
Click to expand...
Click to collapse
The bootloader doesn't need to be locked to flash a RUU. A guy over at Swedroid flashed a Europe RUU (401 device) (after setting Super CID) coming from a carrier-branded One and the RUU did flash perfectly.
I would of course want OTA's, but the thing is, I heard Europe gets them faster than the Nordic region.
Theshawty said:
The bootloader doesn't need to be locked to flash a RUU. A guy over at Swedroid flashed a Europe RUU (401 device) (after setting Super CID) coming from a carrier-branded One and the RUU did flash perfectly.
I would of course want OTA's, but the thing is, I heard Europe gets them faster than the Nordic region.
Click to expand...
Click to collapse
Not necessarily. As with the s3, releases seem pretty random from country to country in Europe. I had the one x with HTC__001 cid and was one of the last to be updated.
Sent from my Nexus 7 using xda premium
Locked the bootloader and went into fastboot and started the RUU. It is now flashing :victory:
After it's done, I will turn the CID back to HTC__Y13 and reflash the RUU.
Theshawty said:
The bootloader doesn't need to be locked to flash a RUU. A guy over at Swedroid flashed a Europe RUU (401 device) (after setting Super CID) coming from a carrier-branded One and the RUU did flash perfectly.
I would of course want OTA's, but the thing is, I heard Europe gets them faster than the Nordic region.
Click to expand...
Click to collapse
I, personally, would relock the bootloader purely to cover yourself. As for CID, it's up to you. Using HTC__001 might not get it the second an OTA comes out but I'm sure you're patient enough to wait a few days
EddyOS said:
I, personally, would relock the bootloader purely to cover yourself. As for CID, it's up to you. Using HTC__001 might not get it the second an OTA comes out but I'm sure you're patient enough to wait a few days
Click to expand...
Click to collapse
I just want back to stock for a few days. I'm a bit tired of custom roming yet I can't stay away from it!
Theshawty said:
I just want back to stock for a few days. I'm a bit tired of custom roming yet I can't stay away from it!
Click to expand...
Click to collapse
I've done the same with my Nexus 4, and shall do the same with my One when I get it next month. I want S-OFF purely because the only RUU we have is an older than what I'll likely get on my phone. This way I can always go back to stock (unless a newer RUU leaks that is!)
How awfully peculiar, though. After I flashed to stock (the 1.28 something RUU), I got an update to 1.29.401.12. My brother, whom also have a One in the same region as I, has the 1.29.401.16 update (I am four decimals behind him ).
I thought I would get an update to .16, or am I just being too impatient?
I know I had .16 before custom roms though.
I read all, very useful conversation,saved me lot of time
Only a thing i havent understand
Im now S-OFF,unlocked with superCID ( runnind a branded italian rom with (now old)TIM__041(if i rememeber right)cid)
What i need to do to have a stock unbranded european RUU
Do i need to relock bootloader Before flashing or not matters?
Theshawty said:
How awfully peculiar, though. After I flashed to stock (the 1.28 something RUU), I got an update to 1.29.401.12. My brother, whom also have a One in the same region as I, has the 1.29.401.16 update (I am four decimals behind him ).
I thought I would get an update to .16, or am I just being too impatient?
I know I had .16 before custom roms though.
Click to expand...
Click to collapse
.16 was for the M7_U handsets, M7_UL is on .12
EddyOS said:
.16 was for the M7_U handsets, M7_UL is on .12
Click to expand...
Click to collapse
But my little brother and I both have UL devices, and his clearly says UL in the about screens.
Theshawty said:
But my little brother and I both have UL devices, and his clearly says UL in the about screens.
Click to expand...
Click to collapse
Hmmm, perhaps it is down to CID then...I don't know anyone in the UK with anything over .12

HTC Europe 1.28.401.7 or HTC Europe 1.20.401.1

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

OTA update failing because of modified software?

Hey there
For some reason the OTA (1.29.401) failed and told me that I may be running modified software, however I tried the OTA update AFTER relocking the bootloader and flashing a RUU so then everything is stock! I am S-OFF, however, could that be the issue? The CID is HTC__001. Originally it was HTC__J15 but I changed it because J15 doesn't receive OTA updates except like three months after everyone else.
Thanks!
MID?
TarekElsakka said:
Hey there
For some reason the OTA (1.29.401) failed and told me that I may be running modified software, however I tried the OTA update AFTER relocking the bootloader and flashing a RUU so then everything is stock! I am S-OFF, however, could that be the issue? The CID is HTC__001. Originally it was HTC__J15 but I changed it because J15 doesn't receive OTA updates except like three months after everyone else.
Thanks!
Click to expand...
Click to collapse
Not sure, but I think both you're CID and MID have to match what is in the OTA for it to work.
And you need stock recovery for OTAs to install.
I do have stock recovery, however I believe that yes, my CID and MID don't match since my device came with CID HTC__J15 and MID PN071100 whereas European devices come with HTC__001 and MID PN071000. That's definitely it, right?
sorry but did you fix this ?? I'm facing the same problem here!

[Q] How to completely go back to stock state?

EDIT: To make a long story short: Does my device have to be S-ON to be able to perform OTA updates? Does my Model ID have to match the CID? Like if my Model ID is PN0711000 and CID HTC__J15 and I decide to change CID to HTC_A07 in Russia, do I have to change Model ID as well to whatever it is they use in Russia?
Hello there
Just before someone chimes in with "Read tutorials or Google", I read just about every popular tutorial there is, including several here on XDA.
I understand that there are a couple of days to go back to stock, but only one of them is available to me: Installing a RUU.
My device is international, unlocked and came with CID HTC__J15 and MID PN0711000. The region is Middle East (Egypt).
We are always the latest to receive any OTA updates, I know because I came from a HTC One X before the Galaxy SIII. I decided I'd go S-OFF and SuperCID (after installing several custom ROMs) in order to go back to stock. I installed this RUU:
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
I was told that just about any .401 (WWE) RUU should work. I installed it when I had SuperCID (111111) but then I changed my CID to HTC__001. I then found an OTA update to 1.29.401 (229MB) and I downloaded it, but after it was done downloading it gave me this message:
Your device has been modified. Software updates are not available.
I do not understand how that came to be? I installed a RUU therefore I have stock recovery and I changed CID to HTC__001 so I should be eligible for OTA updates for that specific region, could it be that my device is S-OFF or is there maybe a CID/MID mismatch?
Thank you
You have to have stock recovery as well.
When s-off you can flash any ruu you like.
Sent from my HTC One
I am super CID and I flashed RUU. I then changed CID to HTC__001 and tried to perform OTA update to 1.29 and it said your software is modified. I do have stock recovery, by the way. So if it isn't because of S-OFF, could it be a Model ID thing?
Try changing cid back to original.
Sent from my HTC One
---------- Post added at 11:32 PM ---------- Previous post was at 11:24 PM ----------
Did you: fastboot oem lock
Sent from my HTC One
Yes, I did lock the bootloader using ADB and now it says "Locked".
I changed CID to HTC__A07 and am trying the update.
Is there a way to find out if your device status says stock or modified? I remember there was something like that before.

[Q] UK OTA after changing CID to HTC__Y13 to receive early update.

I'm in the UK & have a sim free HTC One.
So I changed my CID to HTC__Y13 to enable me to get the 4.2.2 OTA early then changed it back to HTC__001 & sadly used Revone to S-ON again. I have no English (United Kingdom) setting in the system language, probably because the update wasn't meant for a uk phone, so my thought was to go back to the 1.28.401.7 RUU then update properly now the UK OTA is out. Obviously I can't do this because I have a 1.54 hboot & can't S-OFF again to flash the RUU.
What method can I use to be able to downgrade the hboot to 1.44, S-OFF & flash the 1.28 RUU? Can I unlock bootloader via HTCDev, flash a custom rom with a 1.44 hboot then go back to stock, lock bootloader, S-OFF then flash to RUU? I don't want to try this & wipe my phone if it won't work.
Anyone else figured a way to do it?
Cheers
Tim
From my understanding, there is no way of altering H-boot without S-off. I'm sure someone will cracking 1.55 in the future.
Sent from my HTC One using xda premium
drspikes said:
From my understanding, there is no way of altering H-boot without S-off. I'm sure someone will cracking 1.55 in the future.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
This is correct.
The update WAS for your phone, if a phone is x.xx.401.x in the UK and x.xx.401.x in the Netherlands they get the same OTA
Can you still change your CID? I read someone who lost S-Off but was still able to change to superCID (11111111)
Sent with desire from My One
If you aren't afraid to experiment.
That is simple for information, when my phone had leaked 2.17.401.1 ROM from here http://forum.xda-developers.com/showthread.php?t=2224752
and
firmware from 2.17.401.1 RUU
from here (second post)
http://forum.xda-developers.com/showthread.php?t=2182823
My phone had HBOOT 1.54 and I without problems received S-OFF using alternate revone binary v0.2.1-wlj.
So , you can try this way
1) Unlock booloader
2) Flash latest custom recovery (I had TWRP)
3) Make nandroid backup your system
4) Flash 2.17.401.1 ROM
5) Try to get S-OFF using revone v0.2.1-wlj
I DO NOT guarantee success! If you do it, it is your risk!

Categories

Resources