[Q] Strange CID and Stock update help please? - HTC One X

Hi there.
I'm new to the forum but have lurked and used some of the great information and tools that are available here.
So firstly, thank you.
Now.
I bought my One X in China (Where I live), in around August. It seems as though the one I got isn't a regular One X and because of that I'm having some problems.
A month and a half or so ago I installed an AOKP Rom which I've had some pretty intense bugs with, such as the the phone restarting whenever I toggle WiFi on or off. Because of that, I finally attempted to return to stock today. After a while, I found some success. I restored my nandroid backup, reflashed the stock recovery and relocked the bootloader. Happy that I was back to normal, I went to download the Jelly Bean OTA update, but kept having errors when doing so. (The green bar would reach about 1/3 of the way and then a red triangle showed up.) I've tried to troubleshoot and in doing so have found out that my CID is "11111111", so I have no idea what to make of it. All i could find was that this is some kind of superCID, but if it's preventing me from installing an OTA update then how do I go around this?
Is it possible to change my CID to something more accessible? This is the international Tegra 3 model by the way.
Additionally, the HBOOT screen shows that my phone is "ENDEAVORU PVT SHIP S-OFF RL". Is this normal?
Any answers would be extremely appreciated. Thank you.

You're really lucky actually, because a lot of people want exactly your phone - SuperCID and S-OFF. You cannot flash OTAs on a SuperCID phone iirc, but you can unlock the bootloader and flash something else

Hi, there are fastboot commands to change your cid if you are s-off but I am not sure why you would want to.
With s-off you can just go and flash the 1.39 hboot from mikes thread (link from his arhd thread OP)
I have same setup as you and have been wondering what actually is stock for me if I ever needed it. I don't have a nandroid from when I got the phone and I guess that s-off and super cid means I could pick any one ? But which.
Sent from my HTC One X

Thanks for the replies. I guess i have a better understanding now of what these things all mean.
So I gather if I want to get the stock Jellybean ROM I have to flash it myself?
Eh, that's kind of a pain but I guess it's not too bad. Do I go about it in the same way that anyone else would or will there be a variation based on the situation of my phone?
Thanks

I reckon someone with an s-on would gladly swop with you if its a pain you have the most flexibility as it is.
Flash whichever update you like without worrying about the cid matching. That's the magic of super cid. Then because you are s-off you also have the option to downgrade if that ever took your fancy.
There are many guides on how to do this written far better than I could so just search the forum.
Enjoy
Sent from my HTC One X

I see.
I've had a look around and I'm still a little confused to be honest.
Because I'm S-Off and have SuperCID, does that mean I can just choose a Jellybean OTA Update, download it, install it and upgrade the HBOOT?
Everything will be the same as if I upgraded OTA?
Sorry for being so useless.

Don't hang me for this info, see it more as a pointer to more info to search on
What i have read before is that you can write yourself a CID and update the hboot with a firmware from that CID. then you can run any software out there......
Do not run a ruu, it might mess up your s-off to s-on

When I get to my pc I will write up what I did with a link.
I did as Mr Hofs said but I did not need to change my cid from super to do it.
I have never tried an ruu.
Sent from my HTC One X

Ok so first i read this and watched his youtube vid http://www.flow-wolf.net/2012/10/htc-one-x-perfect-guide-for-beginners.html
Check video here http://www.youtube.com/watch?v=AQasxRPopSM he works with an S-Off
I started on HBoot 1.12 i believe
Then I got my unlock token handy (one from htcdev) and made sure fastboot working etc
Then did a nandroid (which i subsequently deleted but hey i tried to do the right thing )
Then I got the latest firmware for HBoot 1.39 from here http://forum.xda-developers.com/showthread.php?t=1957376 I downloaded the first 1.39 for WWE (x.xx.401.x - World Wide English (WWE))
No need to change your CID. Super CID works with any of them.
Now I just followed the usual steps explained many times here to flash the firmware.
You need to put the stock recovery back on. I got mine from here http://forum.xda-developers.com/showthread.php?t=1546970&highlight=htc+one+x+*stock* EDIT: dont think you need this step actually -will let one of the pro's confirm.
Then relock bootloader and reboot in RUU and flash the firmware.
When done unlock bootloader again, flash custom recovery and flash a ROM. You can skip the extra step of flashing the boot.img as with S-Off your custom recovery can do it.
As mentioned by Mr Hofs I have no idea what an RUU would do to S-Off, Ive never tried.
Good luck.

Related

[Q] Unable to load ROM

Hi guys,
Hoping someone can help, have bricked my Australian Optus stock One X. I have tried to follow all threads related to loading stock or custom roms from fastboot and am unable to. I still have CWM recovery 5.8.2.7 touch installed.
I had previously rooted it and installed Android Revolution HD 5.1.0 and seemed to be fine but was unstable and would crash and reboot in certain apps. In trying to revert back to stock I stupidly formatted the SD card, DUMB ASS!
I have downloaded stock rom 1.29.401.7-DUO, all-in-one rootkit, and the ARHD ROM and have tried to either:
1) flash ARHD with bootloader still unlocked, doesn't work
2) follow reflashing stock process ie flash stock recovery, relock bootloader, then flash stock ROM, and am getting stuck on just reflashing the stock recovery. When I try to open stock recovery it takes me to a black screen with a red ! in a triangle, this is with the bootloader relocked.
If anyone is able to help an enthusiast noob like me I'd be very appreciative and would also be more than willing to donate for the trouble.
MAKE SURE you have exactly the right RUU for your phone, whatever the rom was on you were using, ie, 1.26, 1.28, 1.29, you need the same version of RUU, i discovered the problem trying to flash RUUs and after 2 days finally got the correct one, thats when i realised, unlike on other phones, you cant downgrade the One X and when recovering it seems to prefer the one that matches what you were using.
Also make sure youre cid is supported in that RUU, ie, HTC 001, TMOB 054, etc etc, mine can only accept 401 roms, so they must match exactly, until we can get S-Off this problem will remain, dont worry about recovery, so the guide on in case of disaster, you cant go wrong with it, relock your bootloader and get your RUU installed, from their update it to your latest ics version and then if you must reflash your cwm and root it.
Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.
agentorange82 said:
Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.
Click to expand...
Click to collapse
You can get 1.28.980.10 from htcdev downloads. I would link but I'm a new user, just filter by One X, Optus, and it's there.
Thanks again for the help. I have seen those files on htcdev website, but don't know how to use them
I don't know how to load a RUU that is not a .exe file...if anyone is able to assist, again, I would really appreciate it and will donate once up and running again.
Edit: I just wanted to add that I have tried to follow the thread that explains how to load/flash recovery and boot images via fastboot in command prompt, and have not been able to. So I don't think I'm a complete dumb ass, but do need someone with the knowledge and patience to guide me through it. Please!
First thing first, do you have the right RUU with you ?
If not, maybe this is the one for you : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_258004_signed.exe
second: do you have fastboot directory set up on your pc ? and htc usb driver too ?
Just starting the download now, I think that could be the RUU I've been looking for. Yes I have the drivers and fastboot directory. Will give this RUU a go and let you know, thanks for the quick reply, ckpv5!
Most important before you run the RUU, you need to:
1) have a stock recovery flashed to you your device first (I believe you already have one)
2) relock the bootloader - fastboot oem lock
3) run RUU, it should work.
THANK YOU!
ckpv5, thank you for the link to the updated RUU. Phone is functioning again, stock. Donation coming your way. Thanks for all your help. agentorange82.

Need Help Getting Phone to Boot!

Hey Guys,
I'm reaching the point of frustration now. To try and cut a long story short, I had the Android Revolution 6 ROM on my rooted/unlocked HTC One X, and decided to update it to Android Revolution 13. I followed all the instructions, went to boot it, and it just sat on the HTC logo for an hour at which point I knew something went wrong. I repeated the steps, including wiping data using super wipe, without success either. I then decided to just select the "Factory reset" option on the boot menu, but this has also failed to boot after 30 minutes. I can also no longer boot into recovery. I've tried reloading CWM and other recovery ROM's onto the phone, but the phone resets as soon as they load.
At this point, I just want to get some form of OS on my phone. My phone is Unlocked, S-ON and has a CID of OPTUS001. I don't know if Factory reset will work if the phone is unlocked. It's all very time consuming as you normally don't know if the boot process has locked until you've waited ~20 minutes. I can't find my original ROM from when I bought the phone either, so I assume I need to obtain another one from somewhere, but I don't have any idea about CID compatibility, etc, and I'm finding this all very confusing and frustrating. All help is much appreciated. I have a feeling I need to replace my boot.img with a stock boot.img, but once again, where do I get that?
Thanks
the phone doesn't boot because you don't have the latest firmware installed, you need HBOOT 1.31 but you can't install it cause your CID is not compatible with it, you sjould go back to ICS and wait...
Did you load new firmware 1.31? This firmware is not compatible with Your CID... Did You read carefully this thread — http://forum.xda-developers.com/showthread.php?t=1924003
Sent from HOX with ARHD 13
You forgot that you need to update the firmware to 1.31.
You can also just install ARHD 9.7.2. Ensure you have the latest CWM 5.8.4.0
faatboot flash recovery recovery.img
and then flash the boot image:
fastboot flash boot boot.img
fastboot erase cache
And then copy the ROM on using recovery mount USB and flash it.
Thanks for all the help guys. I managed to get a stock recovery.img back onto the phone, and by re-locking the phone I was able to use the latest Optus RUU from htcruu.com.
So at least I've now got a working phone again.
Moving onto why ARHD didn't work, I had no idea about the firmware 1.31 compatibility requirement. I thought all HTC One X's were created equal. I didn't know about this CID nonsense. Can someone explain how I find out when my phone's CID becomes compatible, or perhaps a way to change my CID or some other means of getting Jelly Bean onto my phone. Apologies for being a noob.
wardrop said:
Thanks for all the help guys. I managed to get a stock recovery.img back onto the phone, and by re-locking the phone I was able to use the latest Optus RUU from htcruu.com.
So at least I've now got a working phone again.
Moving onto why ARHD didn't work, I had no idea about the firmware 1.31 compatibility requirement. I thought all HTC One X's were created equal. I didn't know about this CID nonsense. Can someone explain how I find out when my phone's CID becomes compatible, or perhaps a way to change my CID or some other means of getting Jelly Bean onto my phone. Apologies for being a noob.
Click to expand...
Click to collapse
without S-OFF no chance to change CID. Regarding CID compatible - http://forum.xda-developers.com/showthread.php?t=1924003
wardrop said:
Thanks for all the help guys. I managed to get a stock recovery.img back onto the phone, and by re-locking the phone I was able to use the latest Optus RUU from htcruu.com.
So at least I've now got a working phone again.
Moving onto why ARHD didn't work, I had no idea about the firmware 1.31 compatibility requirement. I thought all HTC One X's were created equal. I didn't know about this CID nonsense. Can someone explain how I find out when my phone's CID becomes compatible, or perhaps a way to change my CID or some other means of getting Jelly Bean onto my phone. Apologies for being a noob.
Click to expand...
Click to collapse
now you're on stock right? when you'll get the OTA update then you can install JB custom roms...
matt95 said:
now you're on stock right? when you'll get the OTA update then you can install JB custom roms...
Click to expand...
Click to collapse
Yeah, but I'm going to put on ARHD 9.7 I think.
Optus not compatible with JB yet

[Q] Installing Custom Roms

ok soo ive had time to finally sit down and start installing custom stuff to my hox. I went through all the steps to set it up and ive unlocked booloader, and instaled custom recovery.
I went to go flash a rom lets just say android revolution but i havent decided which yet. Im alittle confused about the instructions.
it turns out my HOX is s-off (it says s off on the top of bootloader screen). and my CID is 11111111 and my hboot is 1.39.
So these are my qs:
-What does s-off really mean? Does it let me skip any steps or does this matter.
-Why is my CID like that? After looking at this thread: http://forum.xda-developers.com/showthread.php?t=1975140, I don't see my CID listed. Did i get like a fake HOX or something? (When i go through the setup it doesn't let me uncheck the "provide annonymous info to HTC" agreement because it says my device is a test device if that helps...)
-What is a "Proper HBOOT version for Jelly Bean based ROM"? (This is from te Andoid revolution HD instructions) I think I have a correct HBoot but idk what im supposed to be looking for
This isnt my first time installing custom roms but it was much more simple with my old phones than this. I dont wanna eff anything up cause I cant afford to get another beautiful hox
Thanks in advance for the help guys :good:
PaKii94 said:
ok soo ive had time to finally sit down and start installing custom stuff to my hox. I went through all the steps to set it up and ive unlocked booloader, and instaled custom recovery.
I went to go flash a rom lets just say android revolution but i havent decided which yet. Im alittle confused about the instructions.
it turns out my HOX is s-off (it says s off on the top of bootloader screen). and my CID is 11111111 and my hboot is 1.39.
So these are my qs:
-What does s-off really mean? Does it let me skip any steps or does this matter.
-Why is my CID like that? After looking at this thread: http://forum.xda-developers.com/showthread.php?t=1975140, I don't see my CID listed. Did i get like a fake HOX or something? (When i go through the setup it doesn't let me uncheck the "provide annonymous info to HTC" agreement because it says my device is a test device if that helps...)
-What is a "Proper HBOOT version for Jelly Bean based ROM"? (This is from te Andoid revolution HD instructions) I think I have a correct HBoot but idk what im supposed to be looking for
This isnt my first time installing custom roms but it was much more simple with my old phones than this. I dont wanna eff anything up cause I cant afford to get another beautiful hox
Thanks in advance for the help guys :good:
Click to expand...
Click to collapse
- S-off is security off, you can flash complete roms from the recovery, no need to flash the boot.img with fastboot commands.
- your cid is kinda special, you are able to change it to any regio cid becase your phone is s-off. Its a lucky thing id say.....
- the proper hboot for JB are all hboots from 1.31 up to 1.39
You can put a rom onto the sdcard and perform a full wipe and then install the new rom.zip. you do not need to flash the boot.img seperatly like we have to do with s-on devices.....
Hope this helps
Sent from my GT-P5110 using xda app-developers app
Mr Hofs said:
- S-off is security off, you can flash complete roms from the recovery, no need to flash the boot.img with fastboot commands.
- your cid is kinda special, you are able to change it to any regio cid becase your phone is s-off. Its a lucky thing id say.....
- the proper hboot for JB are all hboots from 1.31 up to 1.39
You can put a rom onto the sdcard and perform a full wipe and then install the new rom.zip. you do not need to flash the boot.img seperatly like we have to do with s-on devices.....
Hope this helps
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
ok so i just ignore the boo.img stuff cause i dont need to flash it... sounds good makes life a bit simpler almost like flashing on my old phone . as for CID, if i change it to any old regular one can I change it back? is there any advantage to changing it? what does CID actually mean... also what does hboot mean/do? Im only interested in JB roms so i shouldnt have to worry about that right?
If you only want to install JB custom roms you dont need to change anything......flash away i dont know too much about changing the cid. But you are pretty much able to run all software from every country. Like mine cid is european so i can only flash the european software to it. You are able to change the cid so you are also able to flash official asian software and the bootloader is sort of the bios from a pc....
Sent from my GT-P5110 using xda app-developers app

Returning to Stock T-MOB101

Hi everybody,
I've been reading a lot of stuff since now but still have some unanswered questions.
I want to return to completely stock as for insurance or warranty purposes.
I originally got an german HTC One M8 with T-MOB101 cid.
I unlocked the bootloader as the temp-root variant did not work for me, s-off'ed, changed cid to Supercid and flashed ViperRom.
But now I have to send it in to insurance company because my display glass broke after dropping my htc one off about 1 Foot...:crying:
So how would be the optimal procedure to get as close to completely stock?
I know that after reverting everything the bootloader would still say relocked.
So my idea was to:
1. get an original T-MOB101 NAND backup and restore it (beforehand restore T-MOB101 cid)
2. flashing stock recovery
3. Removing Tampered (http://forum.xda-developers.com/showpost.php?p=51700320&postcount=1)
4. Setting Locked (http://forum.xda-developers.com/showthread.php?t=2708571)
5. play over an OTA firmware.zip
This would lead me to a stock rom with OTA capability, but would still show me the red warning as well as S-OFF.
As an alternative I read about hex edited hboots to get rid of the red warning or even Mask S-off as s-on.
However in the according thread i could not make out an hboot corresponding to the T-MOB101 CID. So I tried it on my own after having a look at stock and modified hboots.
I edited my own hboot according to those modification but am too scared to flash it as it could hard brick my phone....
So I ask you guys, am I on the right way and what would you do ?
Greetz F4t4l!tY
F4t4l!tY said:
Hi everybody,
I've been reading a lot of stuff since now but still have some unanswered questions.
I want to return to completely stock as for insurance or warranty purposes.
I originally got an german HTC One M8 with T-MOB101 cid.
I unlocked the bootloader as the temp-root variant did not work for me, s-off'ed, changed cid to Supercid and flashed ViperRom.
But now I have to send it in to insurance company because my display glass broke after dropping my htc one off about 1 Foot...:crying:
So how would be the optimal procedure to get as close to completely stock?
I know that after reverting everything the bootloader would still say relocked.
So my idea was to:
1. get an original T-MOB101 NAND backup and restore it (beforehand restore T-MOB101 cid)
2. flashing stock recovery
3. Removing Tampered (http://forum.xda-developers.com/showpost.php?p=51700320&postcount=1)
4. Setting Locked (http://forum.xda-developers.com/showthread.php?t=2708571)
5. play over an OTA firmware.zip
This would lead me to a stock rom with OTA capability, but would still show me the red warning as well as S-OFF.
As an alternative I read about hex edited hboots to get rid of the red warning or even Mask S-off as s-on.
However in the according thread i could not make out an hboot corresponding to the T-MOB101 CID. So I tried it on my own after having a look at stock and modified hboots.
I edited my own hboot according to those modification but am too scared to flash it as it could hard brick my phone....
So I ask you guys, am I on the right way and what would you do ?
Greetz F4t4l!tY
Click to expand...
Click to collapse
To tell you the truth, I don't think the insurance company will care about any software mods. Different story if you had to send it in to HTC.
GermanGuy said:
To tell you the truth, I don't think the insurance company will care about any software mods. Different story if you had to send it in to HTC.
Click to expand...
Click to collapse
Well, actually I would agree, but as they turn on the phone and a red warning pops up I could think of any crazy reason why they would deny the repair or exchange ^^.
Whatever that reason might be that would result in a broken glass caused by the software
Does the red text dissappear if I return S-ON, officially relock bootloader, stock recovery and cid?
F4t4l!tY said:
Well, actually I would agree, but as they turn on the phone and a red warning pops up I could think of any crazy reason why they would deny the repair or exchange ^^.
Whatever that reason might be that would result in a broken glass caused by the software
Does the red text dissappear if I return S-ON, officially relock bootloader, stock recovery and cid?
Click to expand...
Click to collapse
The only way to get rid off the red text is with a modifed HBOOT.
GermanGuy said:
The only way to get rid off the red text is with a modifed HBOOT.
Click to expand...
Click to collapse
Well ok, I feared that. You're not accidently fit in Hex-Editing ?
As I said, I already backed up my hboot and edited it as the other hboots I founds with the wrong cid. But I'm afraid of flashing it without anyone else who knows something about hexediting took a second look at it.
Also does the hboot get overwritten by a NAND backup? So if I'll restore I would have to modify that hboot and not the one I'm currently at?
F4t4l!tY said:
Well ok, I feared that. You're not accidently fit in Hex-Editing ?
As I said, I already backed up my hboot and edited it as the other hboots I founds with the wrong cid. But I'm afraid of flashing it without anyone else who knows something about hexediting took a second look at it.
Also does the hboot get overwritten by a NAND backup? So if I'll restore I would have to modify that hboot and not the one I'm currently at?
Click to expand...
Click to collapse
Sorry, have not done hexediting in a while. Hboot is part of firmware, does not get overwritten by restore backup.
Alright but thanks anyway.
If there is someone out there who could help, i would appreciate that .
Thx in advance!
F4t4l!tY said:
Alright but thanks anyway.
If there is someone out there who could help, i would appreciate that .
Thx in advance!
Click to expand...
Click to collapse
First you should flash the stock rom then stock recovery.This will remove your red text.then you should flash ruu.I would suggest not to change your cid.
Also if you are comfortable you can change your cid to supercid,mid to wwe mid then flash wwe fw and its recovery then flash the ruu.This will convert your phone to international htc with s-off and super cid and you will be able to take ota and you will have full 100% warranty.
Hey Jyotirdeb,
thanks for your input.
But there is still the problem, that I have to come to T-MOB101 firmware and not the WWE. Furthermore as far as I have read, the red text will only disappear if I flash stock recovery, stock ROM AND S-ON again. At least without a modified HBOOT.
Other problem is, that there are as far as i know no RUUs available for the M8 up to now. Correct me if I'm mistaken. At least I didn't find one, especially for cid T-MOB101.
F4t4l!tY said:
Hey Jyotirdeb,
thanks for your input.
But there is still the problem, that I have to come to T-MOB101 firmware and not the WWE. Furthermore as far as I have read, the red text will only disappear if I flash stock recovery, stock ROM AND S-ON again. At least without a modified HBOOT.
Other problem is, that there are as far as i know no RUUs available for the M8 up to now. Correct me if I'm mistaken. At least I didn't find one, especially for cid T-MOB101.
Click to expand...
Click to collapse
It is true that you have to be on stock rom and stock kernel.But you dont have to be s-on you can be s-off.And yes as far as I know there is EU ruu (unbranded) maybe you have to wait for hTC to release Ruu for other variant.I am sorry I cant be of more help.
Hmm, strange thing, as I actually read it again that there must be s-on and everything stock, to get rid of it, but nevermind.
Really, where could I get that RUU from? As far as I know only the Sprint or Verizon Variant does have a RUU not the International One.
Furthermore would I need the RUU from T-Mobile as the release it with their branding, not HTC.
F4t4l!tY said:
Hmm, strange thing, as I actually read it again that there must be s-on and everything stock, to get rid of it, but nevermind.
Really, where could I get that RUU from? As far as I know only the Sprint or Verizon Variant does have a RUU not the International One.
Furthermore would I need the RUU from T-Mobile as the release it with their branding, not HTC.
Click to expand...
Click to collapse
"Hmm, strange thing, as I actually read it again that there must be s-on and everything stock, to get rid of it, but nevermind."
If you have an s-on device you can change bootloader status to relocked but if you have soff device you can change bootloader stats to locked so you will get 100% warranty.I dont know about version or sprint but the ruu is available for unbranded EU model.
hi guys
i don t find the recovery stock of my htc one m8 cid tmob101 firmware 3.32.111.3 .
you can help me? thx
glesius said:
hi guys
i don t find the recovery stock of my htc one m8 cid tmob101 firmware 3.32.111.3 .
you can help me? thx
Click to expand...
Click to collapse
The site is in german... use google chrome to translate.
You'll find everything you need to restore T-MOB101 M8.
http://www.handy-faq.de/forum/htc_o...ne_m8_firmwaresammlung_ruus_otas_backups.html
harri2cool said:
The site is in german... use google chrome to translate.
You'll find everything you need to restore T-MOB101 M8.
http://www.handy-faq.de/forum/htc_o...ne_m8_firmwaresammlung_ruus_otas_backups.html
Click to expand...
Click to collapse
Actually, on that site there is a RUU for unbranded phones only. For T-MOB101 they have a nand backup and firmware. I'm still thinking whether I want to use that. That is, I have a similar issue as the OP, I mean, I want to reinstall Android, although I'm completely stock, unrooted, etc. It's just that the Lollipop update screwed everything up and I'm hoping that reinstalling will fix it. Unfortunately, for CID T-MOB101 no RUU is available. So, I either have to use the backup and then flash firmware, for which I have to root and install custom recovery first, or I have to wait till HTC comes up with Android 5.1.

Can't get my HTC One M9 back to stock [HELP NEEDED]

RELOCKED
S-ON
OS : 2.10.401.1
CID: HTC_0031
Hello Guys,
I have a major problem getting my HTC M9 back to stock!
My first problem began when i was trying to update my ViberRom from 5.1.1 to Marschmallow, the problem that i had was that my recovery could not update. But when i updated it to 3.0.0 or something like that, i couldn't boot my ViberRom (because that was still 5.1.1).
So in order to fix that problem i thought that i could return my HTC M9 back to stock with an RUU, however since i have the EU/International version (2.10.401.1), i could not use the .exe version HTC provided themselves on their own website. After looking on the internet i found an RUU which corresponded with my version (2.10.401.1) it was a ZIP file so i needed to either flash it or put it on my SD card.
After a while a new problem arose, I have no S-OFF, but after reading several threads i did not matter as long as i had the right RUU version or higher (as well as matching CID, MID). Several articles and threads also mentioned that when i wanted to flash an RUU with S-On i would need to re-lock my bootloader and so i did.
With a locked bootloader i tried flashing the RUU, but everytime when i do it my FASTBOOT.EXE crashes!
Sorry if i am being a NOOB right now, but i really don't know what to do now, My Rom won't boot and i cant acces my recovery. I already treid Unlocking my bootloader again, and after completing every step, including choosing the option to unlock it on the phone itself using the volume buttons, it still states: RELOCKED
I really hope you guys can help me with my problem!!
Kind regards,
Roan
(sorry for anything that may be not clear, English is not my native language)
Roanvdw said:
RELOCKED
S-ON
OS : 2.10.401.1
CID: HTC_0031
Hello Guys,
I have a major problem getting my HTC M9 back to stock!
My first problem began when i was trying to update my ViberRom from 5.1.1 to Marschmallow, the problem that i had was that my recovery could not update. But when i updated it to 3.0.0 or something like that, i couldn't boot my ViberRom (because that was still 5.1.1).
So in order to fix that problem i thought that i could return my HTC M9 back to stock with an RUU, however since i have the EU/International version (2.10.401.1), i could not use the .exe version HTC provided themselves on their own website. After looking on the internet i found an RUU which corresponded with my version (2.10.401.1) it was a ZIP file so i needed to either flash it or put it on my SD card.
After a while a new problem arose, I have no S-OFF, but after reading several threads i did not matter as long as i had the right RUU version or higher (as well as matching CID, MID). Several articles and threads also mentioned that when i wanted to flash an RUU with S-On i would need to re-lock my bootloader and so i did.
With a locked bootloader i tried flashing the RUU, but everytime when i do it my FASTBOOT.EXE crashes!
Sorry if i am being a NOOB right now, but i really don't know what to do now, My Rom won't boot and i cant acces my recovery. I already treid Unlocking my bootloader again, and after completing every step, including choosing the option to unlock it on the phone itself using the volume buttons, it still states: RELOCKED
I really hope you guys can help me with my problem!!
Kind regards,
Roan
(sorry for anything that may be not clear, English is not my native language)
Click to expand...
Click to collapse
Fastboot crashes because it can't handle files over 2 GB. There is a different fastboot you need to use called htc_fastboot. Search the forum for a link. Or I'll find one if i can. Commands are exactly the same as fastboot, just add "htc_" in front of fastboot.
Here you go:
https://www.androidfilehost.com/?fid=95916177934550031
jollywhitefoot said:
Fastboot crashes because it can't handle files over 2 GB. There is a different fastboot you need to use called htc_fastboot. Search the forum for a link. Or I'll find one if i can. Commands are exactly the same as fastboot, just add "htc_" in front of fastboot.
Here you go:
Click to expand...
Click to collapse
IT WORKED, very grateful man, very weird that i could not find this problem in the forum though, maybe i just suck at searching.
i have the same problem, i cant even find RUU.zip file, if you could help me with that, would really appreciate it

Categories

Resources