Develop Bugs

[Q] Can i flash JB rom with Sense with CID: 11111111?

Hi,
I would like to flash the newest InsertCoin rom to my One X, but i can't figure out if it will work.
In this thread http://forum.xda-developers.com/showthread.php?t=1920060 it says that i need a certain CID - and my CID is 111111, so it doesn't match (and i tried to change it, but can't).
So - does anyone know if it will work?
And if it doesn't work, will it brick my phone og will i loose any information? (i made a backup in recovery)

fakta said:
Hi,
I would like to flash the newest InsertCoin rom to my One X, but i can't figure out if it will work.
In this thread http://forum.xda-developers.com/showthread.php?t=1920060 it says that i need a certain CID - and my CID is 111111, so it doesn't match (and i tried to change it, but can't).
So - does anyone know if it will work?
And if it doesn't work, will it brick my phone og will i loose any information? (i made a backup in recovery)
Click to expand...
Click to collapse
your CID doesn't support the latest JB Firmware...so DO NOT FLASH THAT!

Hmm... That's not what i was hoping for...
So i will have to find a way to change my CID...?
Do you know how i got that CID? As far as i can read, everybody else has more "random" CID's... I'm an HTC ambassador (i work at a phone company in Denmark) so maybe i got a pre-production model?

fakta said:
Hmm... That's not what i was hoping for...
So i will have to find a way to change my CID...?
Do you know how i got that CID? As far as i can read, everybody else has more "random" CID's... I'm an HTC ambassador (i work at a phone company in Denmark) so maybe i got a pre-production model?
Click to expand...
Click to collapse
you can't change your CID cause you are not S-OFF.... you will have to wait.... every phone has a different cid

Dammit...
Thanks for the help anyway
I actually considered flashing it just to try, but i think you just saved my phone...
And i suppose no one knows when we will get S-OFF...?

You know... i might be missing something here, but isn't CID - 11111111 SuperCID??
Surely that would mean the device is already S-Off??

In recovery it says from the top:
UNLOCKED
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.12.0000
and so on...
I'm guessing that means it is ON?

Yeah that means it's S-ON, but if you had CID 11111111 then thats SuperCID and the CID restrictions wouldn't apply to you.
I don't quite understand how you can have a SuperCID device thats S-On, but if it's a special one from HTC, then who knows?

Mines the same. Weird combo from what I've been reading on here... hopefully there'll no more restrictions or anything... no waiting until every other CID has it first!
Sent from my GT-I9300 using xda app-developers app

Brownie2k said:
Yeah that means it's S-ON, but if you had CID 11111111 then thats SuperCID and the CID restrictions wouldn't apply to you.
I don't quite understand how you can have a SuperCID device thats S-On, but if it's a special one from HTC, then who knows?
Click to expand...
Click to collapse
So in other words i can "safely" flash the JB rom?
If it doesn't work anyway, can i get back to ICS without a wipe?
I think i'm just about to get VERY happy

If you do have CID: 11111111 then yes, i'd say you can safely flash the new HBOOT, BUT because you're not S-Off, you can't go back to HBOOT 1.12.
You need to make a nandroid backup of you ICS Rom so if you don't like Jellybean, then you can go back to ICS through restoring. Beware though, things like CM10 etc don't work on the new HBOOT at the moment.

did you try fastboot oem writecid HTC_001 while in bootloader ? if device stops responding until reboot it means it wont work

Yes you can..my HOX has S-OFF and SuperCid and i was able to flash the new hboot.

volcomnator999 said:
Yes you can..my HOX has S-OFF and SuperCid and i was able to flash the new hboot.
Click to expand...
Click to collapse
Not all SuperCID devices are S-Off. S-Off also allows you to flash an older hboot, which cannot be done with SuperCID alone.

Yes this looks like superCID but I don't know if it will support the JB firmware... Better not to try

matt95 said:
Yes this looks like superCID but I don't know if it will support the JB firmware... Better not to try
Click to expand...
Click to collapse
The worst that could happen is that the new hboot is rejected. That's seems like an entirely recoverable scenario.

Then what does SUPER CID mean if you cannot flash the new Hboot, so it isn't that SUPER!

webpatrick said:
Then what does SUPER CID mean if you cannot flash the new Hboot, so it isn't that SUPER!
Click to expand...
Click to collapse
It means you can run any RUU

It will support the new HBOOT i'd imagine, If you've got SuperCID it's like being region free.
I can't see why it wouldn't work, it's worked for other people, thats one of the advantages of being S-Off, so you can SuperCID and flash any HBOOT (+Downgrade if you're S-Off)

Brownie2k said:
It will support the new HBOOT i'd imagine, If you've got SuperCID it's like being region free.
I can't see why it wouldn't work, it's worked for other people, thats one of the advantages of being S-Off, so you can SuperCID and flash any HBOOT (+Downgrade if you're S-Off)
Click to expand...
Click to collapse
He is not s-off

[Q] How can I change the CID of my S-OFF One X?

My phone is S-OFF and it is SuperCID(11111111), I found out that I won't receive updates if my phone has this CID. I want to change it to a\n unbranded CID where I can receive the JB OTA. I don't know how, though. Also, what CID do you think will receive the earliest JB OTA once it comes out? And if I am going to change my CID to an unbranded one, can I revert it back to SuperCID once I receive the update?

jed27.galvez said:
My phone is S-OFF and it is SuperCID(11111111), I found out that I won't receive updates if my phone has this CID. I want to change it to a\n unbranded CID where I can receive the JB OTA. I don't know how, though. Also, what CID do you think will receive the earliest JB OTA once it comes out? And if I am going to change my CID to an unbranded one, can I revert it back to SuperCID once I receive the update?
Click to expand...
Click to collapse
just run a RUU and that will make you s-on and with the RUU's CID...

That doesn't sound useful, why would you want to lose S-Off?
HTC_001 is probably the most likely to be first, but I'm not sure if the OTA will work. Do you have stock 2.17.401.2 and stock recovery?

BenPope said:
That doesn't sound useful, why would you want to lose S-Off?
HTC_001 is probably the most likely to be first, but I'm not sure if the OTA will work. Do you have stock 2.17.401.2 and stock recovery?
Click to expand...
Click to collapse
yep i agree, i wouldn't ever ever ever flash a RUU only to get official updates! we will get the official update before it will be released worldwide

I am currently on stock 2.17.401.2 after flashing the RUU a month ago. Before that, I was on 1.15.401.1(!). Stock recovery? I don't know what that means, sorry. Anyway, I don't want to lose my S-OFF just so I can receive updates. I know s-off phones can change CID by fastboot blah blah. Something about writing a command, ugh, I'm not really sure.

You wouldn't even need to flash the RUU...
If you're S-Off, you could just use fastboot oem writecid HTC__001 if you really wanted too, which would change your CID to HTC__001 and keep you S-Off, but i'd say staying SuperCID is the best idea, and just flash one of the many JB roms that are out there.

Brownie2k said:
You wouldn't even need to flash the RUU...
If you're S-Off, you could just use fastboot oem writecid HTC__001 if you really wanted too, which would change your CID to HTC__001 and keep you S-Off, but i'd say staying SuperCID is the best idea, and just flash one of the many JB roms that are out there.
Click to expand...
Click to collapse
I get that. But I am still in the process of learning things since this is my first Android phone. Things are still complicated specially because the tuts on inbstalling custom ROMs are all about S-ON HOXs. Anyway, if I change my CID to a normal unbranded one, can I revert it back to SuperCID?

Yes you could.
You'd just do fastboot oem writecid 11111111.
To get updates though, you'd need to have a locked bootloader, stock rom etc... You phone would basically become a Unbranded European One X. Not sure if flashing the update would put you S-On, which means you'd be stuck as a HTC__001.
Basically if you wanted to try Jellybean, you'd just have to flash the required firmware, followed by a custom recovery then flash the rom. You don't need to unlock bootloader because you're S-Off.

Brownie2k said:
Yes you could.
You'd just do fastboot oem writecid 11111111.
To get updates though, you'd need to have a locked bootloader, stock rom etc... You phone would basically become a Unbranded European One X. Not sure if flashing the update would put you S-On, which means you'd be stuck as a HTC__001.
Basically if you wanted to try Jellybean, you'd just have to flash the required firmware, followed by a custom recovery then flash the rom. You don't need to unlock bootloader because you're S-Off.
Click to expand...
Click to collapse
... and as an added bonus you don't need to flash the boot.img of a custom rom before flashing the Rom itself, as we s-on peeps need to. You can just flash the entire custom rom at once from the custom recovery.
I.E. you won't need a computer when you want to try another rom
Sent from my HTC One X using Tapatalk 2

That's my problem! There should be a thread about S-OFF phones and what to do with them. Haha.

jed27.galvez said:
That's my problem! There should be a thread about S-OFF phones and what to do with them. Haha.
Click to expand...
Click to collapse
Well to be fair, it's very rare to find an S-Off One X at the moment, so count yourself very very lucky!
You hold one big big big advantage over us all though, you can downgrade your HBOOT back to 1.12 if you didn't like Jellybean. Currently for the most of us, with compatible CID's, once we're on HBOOT 1.28, thats it, there is no way back which means things like CM10 etc doesn't work for us.

Actually, you can use CM10 with hboot 1.28, but you have to use the special boot.img posted in the CM10 thread. It works for hboot 1.23 and hboot 1.28.
http://forum.xda-developers.com/showpost.php?p=32486421&postcount=7308

RUU OPTUS_001 x.xx.980.x AUSTRALIA

Hi,
I have been searching for an RUU for the australia optus branded HTC one V (CID 980 or OPTUS_001) but have had no luck.... does anyone know where I can get it? I would be eternally grateful as my one V constantly reboots due to a radio update ota...
Have since rooted and installed many different custom roms with no change in the outcome... so i unfortunately need the RUU otherwise the phone is going to have to become a paper weight.
I've also tried many other RUU;s for different CIDs but with no luck (they all say wrong CID).
I would even be prepared to pay someone if they needed me to!!!

check the htcdev website. if an ruu was released for your device,it would be there.

There's no RUU for OPTUS001 CID as of what I know.

MameTozhio said:
There's no RUU for OPTUS001 CID as of what I know.
Click to expand...
Click to collapse
Ok thanks guys. So am I right in saying that there is NO way I can change my CID (to 111111) because its not possible to gain S-Off on the HTC One V?
Then this means there is no way I can use another RUU to revert the phone back to stock because it will only accept the OPTUS001 RUU?

Lollipop RUU Error 130

Hello,
I have the unlocked version of the M8 (I believe...) It's a European model and is unlocked to all carriers.
My CID is HTC_001 but when I go to install the RUU that was released not long ago I get the Error 130 returned.
Is this just me being stupid due to lack of sleep?

Try following this guide: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
You may need to s-off to get the superCID. I would highly recommend to do so.

nathankk said:
Hello,
I have the unlocked version of the M8 (I believe...) It's a European model and is unlocked to all carriers.
My CID is HTC_001 but when I go to install the RUU that was released not long ago I get the Error 130 returned.
Is this just me being stupid due to lack of sleep?
Click to expand...
Click to collapse
Error 130 is wrong MID.
You're trying to flash the wrong RUU. Which one are you trying to install? You need an RUU that is 401.

xunholyx said:
Error 130 is wrong MID.
You're trying to flash the wrong RUU. Which one are you trying to install? You need an RUU that is 401.
Click to expand...
Click to collapse
My Meid is 0000000000 and I am trying to install the latest one they released on the HTC website.

Cid HTC__001 is WWE *.**401.* so you need a wwe 401 ruu. If you do not have s-off you cant flash any other ruu files !
Read more here
http://forum.xda-developers.com/showthread.php?t=2911563
And what's your goal ? What do you want to achieve ?

Mr Hofs said:
Cid HTC__001 is WWE *.**401.* so you need a wwe 401 ruu. If you do not have s-off you cant flash any other ruu files !
Read more here
http://forum.xda-developers.com/showthread.php?t=2911563
And what's your goal ? What do you want to achieve ?
Click to expand...
Click to collapse
Thank you! I guess I will just have to wait until Lollipop comes through an OTA update.

Htc m9 bootloop after flashing recovery...

Hello,
So i wanted to uptade my htc m9u to 7 nougat. i unlocked my bootloader then i flashed twrp recovery and installed root, but when i tried to reboot it remains stuck on loop with logo screen and the red text under it...what can i do?
i found some useful files here: androidfilehost.com/?w=search&s=3.36.709.3&type=files
this is the file that passed the loop: boot_3.36.709.3_root.img....but now my touchscreen is not working at all...
please help...
thanks...

Are you aware that only certain versions of twrp work with certain firmwares.
You need to try to return your phone to its stock state. See flippy's or sneakyghosts threads for help before you completely knacker your phone.
Beamed in by telepathy.

I did not know that only certain version of twrp work with my firmware....
I found a stock recovery for my version i flashed it but it is still looping bootscreen...
In the bootloader it says. Unlocked s-on software status:modified

That may be because you flashed all sorts.. As I already said, you need to go back to stock state with the proper ruu for your phone otherwise you dont know what is stopping the phone from booting so it'll stay like that.
Most likely you've flashed a firmware for the wrong device and that'll be it, dead phone.
As far as I know, you can't flash standard m9 firmware on an m9u.
Beamed in by telepathy.

Ok...but i flashed one stock that paseed the bootloader but the touch is not working...what can i do?
That means that i have a bricked phone ...it cant be undone?

shivadow said:
As far as I know, you can't flash standard m9 firmware on an m9u.
Click to expand...
Click to collapse
Not sure how you define "standard" but the M9u is a overall name for the GSM M9 that doesn't distinguish between hima_ul and hima_uhl. The version with SKU 709 is the same as the 401 one if you look at the hardware.
@Tymmybike: As already mentioned by shivadow, read my thread (and flash a RUU).
However, I don't know what you've been doing there or why you've been doing it. If you want to update your phone's firmware you just need to use the software update function of the stock rom. Flashing TWRP and rooting your phone doesn't make any sense at all since they can break the OTA function if not used correctly due to the block-based OTAs that google introduced with android 5.
And just for the record: The bootloop probably got caused by flashing an incompatible SuperSU version. You wouldn't be the first who did that mistake.
Sent from my HTC One M9 using XDA Labs

I made that mistake too.. I make a lot of mistakes.. Dont know if you noticed.. Its quite difficult..
Beamed in by telepathy.

Flippy498 said:
Not sure how you define "standard" but the M9u is a overall name for the GSM M9 that doesn't distinguish between hima_ul and hima_uhl. The version with SKU 709 is the same as the 401 one if you look at the hardware.
@Tymmybike: As already mentioned by shivadow, read my thread (and flash a RUU).
However, I don't know what you've been doing there or why you've been doing it. If you want to update your phone's firmware you just need to use the software update function of the stock rom. Flashing TWRP and rooting your phone doesn't make any sense at all since they can break the OTA function if not used correctly due to the block-based OTAs that google introduced with android 5.
And just for the record: The bootloop probably got caused by flashing an incompatible SuperSU version. You wouldn't be the first who did that mistake.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I can't find the correct RUU for my model:
kernel: lk
product: htc_himauhl
version: 1.0
version-main: 3.36.709.3
boot-mode: download
version-baseband: 01.01_U11440792_97.00.51203G_F
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: HTC__032
i tried from sku 709 and says didn't match cid, also the one in 401 is not working either...
what can i do?
Flippy498 i wanted to uptade normally but it said: your phone is not using a stock rom or sometging like that.

Tymmybike said:
I can't find the correct RUU for my model
version-main: 3.36.709.3
mid: 0PJA10000
cid: HTC__032
i tried from sku 709 and says didn't match cid, also the one in 401 is not working either...
what can i do?
Flippy498 i wanted to uptade normally but it said: your phone is not using a stock rom or sometging like that.
Click to expand...
Click to collapse
That doesn't surprise me if I look at the data you gave me. (For your own safety: remove your IMEI from your post, btw.) Your CID doesn't belong to your SKU. Is the phone S-OFF? I guess you bought it second hand since it looks like the previous owner borked it. However, the problem should be fixable.
What do you mean with you tried "the one" 401 RUU. There are 7 different 401 RUUs in the ReadMe thread. Try to flash the 3.x one. If that isn't possible and if the phone isn't S-OFF then you'll need to use sunshine for getting S-OFF and being able to fix the phone. If you're lucky and the previous owner used sunshine, as well, then you won't have to pay, again.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
That doesn't surprise me if I look at the data you gave me. (For your own safety: remove your IMEI from your post, btw.) Your CID doesn't belong to your SKU. Is the phone S-OFF? I guess you bought it second hand since it looks like the previous owner borked it. However, the problem should be fixable.
What do you mean with you tried "the one" 401 RUU. There are 7 different 401 RUUs in the ReadMe thread. Try to flash the 3.x one. If that isn't possible and if the phone isn't S-OFF then you'll need to use sunshine for getting S-OFF and being able to fix the phone. If you're lucky and the previous owner used sunshine, as well, then you won't have to pay, again.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
i tried to flash the 3.35.401.12 and it's not working...
for what and why i have to pay?
how do i install sunshine? because i saw it's a .apk

"Doesn't work" can mean anything. What's the exact error message?
Sunshine gets installed like any other apk. Open the file with a file explorer on your phone and let android install the app. It's a paid app. That's why I said you might need to pay. However, that might be unnecessary if your phone already is S-OFF.

Flippy498 said:
Well, it would help if you would use the correct RUU for your firmware and not just a random one...
Sunshine is a paid app.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
i tried to install 3.36.709.3 but is not working because it has the wrong cid, like you said i think the previous owner messed it up.
i downloaded form the sunshine website the latest apk(when do i have to pay), sorry but i dont't understand...how can i install the apk if my phone is not booting?
sorry if i am annoing but i can't seem to understand...

Tymmybike said:
i tried to install 3.36.709.3 but is not working because it has the wrong cid, like you said i think the previous owner messed it up.
Click to expand...
Click to collapse
Yeah, I know. I edited my last post. I confused this thread with another one I'm currently writing in. Sorry. If the phone isn't booting then you aren't able to install/use sunshine.
Edit: Didn't you say earlier that you got out of the bootloop? Is your bootloader still unlocked? Is TWRP still installed? If the last two questions can be answered with yes you could restore the stock backup that corresponds your current firmware via TWRP. This would at least solve the bootloop problem. If needed, you could then use the sunshine app to set the phone S-OFF.

Flippy498 said:
Yeah, I know. I edited my last post. I confused this thread with another one I'm currently writing in. Sorry. If the phone isn't booting then you aren't able to install/use sunshine.
Click to expand...
Click to collapse
well when i installed the 3.35.401.32 from cid: HTC__032 it says: 19 RU_MAIN_VER_FAIL os-version in android-info missing or i
when i intsall the 3.36.709.3 from vid CID: HTC__621 it says: 7 RU_CID_FAIL cid in android-info mismatched

As far as I know there is no 3.35.401.32 RUU. I guess that's just a typo and you meant a 12 at the end, didn't you?
Is the phone S-ON or S-OFF? Depending on that answer we would need to set it S-OFF before we can continue (c.f. the edit of my last post)...

Flippy498 said:
As far as I know there is no 3.35.401.32 RUU. I guess that's just a typo and you meant a 12 at the end, didn't you?
Is the phone S-ON or S-OFF? Depending on that answer we would need to set it S-OFF before we can continue (c.f. the edit of my last post)...
Click to expand...
Click to collapse
yeah it wa a typo i meant 12
the phone is s-on
i got out of bootloop if i flashed boot_3.36.709.3_root.img but the touchscreen is not working at all....
the bootloader is unlocked and the twrp is still installed(i installed it now)....

Alright. Then restore the backup that corresponds to your current firmware version. Files and instructions are located in the ReadMe thread. After that you need to install the sunshine app and get S-OFF. Then you need to follow the conversion guide in the ReadMe thread. Choose the CID and the RUU according to the firmware that you actually want to use. If you want to use the 401 firmware then please try HTC__001 instead of the CID that your phone is using at the moment. After that your phone should be fixed.
Sent from my HTC One M9 using XDA Labs