Related
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
smash_07 said:
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
Click to expand...
Click to collapse
Hi,
This is a SENSATION forum.
malybru said:
Hi,
This is a SENSATION forum.
Click to expand...
Click to collapse
Yes I noticed it i already asked the moderation if they could move the thread to the Desire S section.
I need to find this out to? I dont want to root my Desire S, I just want to changde CID so i could put unbranded software to it...?
You can just create a GoldCard and make it work, without root or S-Off.
Earlier today I created a GoldCard and upgraded my DS using the European RUU and I'm S-ON & Unrooted.
See here: http://forum.xda-developers.com/showthread.php?p=19171606
doghous said:
You can just create a GoldCard and make it work, without root or S-Off.
Earlier today I created a GoldCard and upgraded my DS using the European RUU and I'm S-ON & Unrooted.
See here: http://forum.xda-developers.com/showthread.php?p=19171606
Click to expand...
Click to collapse
Yes I know that works I have a Goldcard. The thing here is that I would like the phone to be completely unbranded without the need os special cards so in case i want to sell it or send it to warranty it won't be noticed that i changed something there. So if there is a way to re write de CID it would be good.
Well i actually successfully installed the unbranded european ROM 1.28.401.1 using the gold card. But now i can't receive OTA updates. Is there a way to get it to work?
Why don't you run the European RUU 2.10 version (RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed) from the following link:
http://forum.xda-developers.com/showthread.php?t=1002506
That's what I did
smash_07 said:
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
Click to expand...
Click to collapse
Just to answer your question:
(I may need to be corrected on this one)
Based on my observation and experimentation. The CID that you are trying to change, or the CID that the RUU is checking is actually on the build.prop on your phone.
Code:
ro.aa.maincid
But there are two checks that I've observed. Even though you changed the maincid, the corresponding cwkey should be changed accordingly.
cwkey created on your phone corresponds on what is on the build.prop and I believe is also being checked by RUUs.
And maybe just to be on the safe side, RUUs do check what is on your build.prop. If they are not what your RUU wants, it will not push through. Hence, you need a GoldCard.
I myself don't exactly, by codes, know how the GoldCard bypasses the checks. All I do know, is that it works.
Skanob said:
Just to answer your question:
(I may need to be corrected on this one)
Based on my observation and experimentation. The CID that you are trying to change, or the CID that the RUU is checking is actually on the build.prop on your phone.
Code:
ro.aa.maincid
But there are two checks that I've observed. Even though you changed the maincid, the corresponding cwkey should be changed accordingly.
cwkey created on your phone corresponds on what is on the build.prop and I believe is also being checked by RUUs.
And maybe just to be on the safe side, RUUs do check what is on your build.prop. If they are not what your RUU wants, it will not push through. Hence, you need a GoldCard.
I myself don't exactly, by codes, know how the GoldCard bypasses the checks. All I do know, is that it works.
Click to expand...
Click to collapse
So what that means is the phone has to stay branded? There is no way that we can fully unbrand the phone by changing the CID?
And after we use the Goldcard what happens to the CID of the phone?
smash_07 said:
So what that means is the phone has to stay branded? There is no way that we can fully unbrand the phone by changing the CID?
And after we use the Goldcard what happens to the CID of the phone?
Click to expand...
Click to collapse
The goldcard does not alter the CID. It just tells the bootloader to ignore the CID check when running a RUU.
One way to alter the CID is to XTC clip the phone.
Well i ended up doing what you all suggested and flashed the RUU with the 2.10 european rom with the goldcard in it.
But something went wrong and my Desire S is in a strange situation. For some reason the Goldcard did not work like the first time and gave me a CID error. But it flashed the hboot 2.00.0002 but retained the 1.28 rom i had installed on it. I have used the HTCDev method to unlock the bootloader but everytime i try to flash the 1.28 RUU again (to flash the old hboot again) it gives me an "unknown error" that is actually a security error.
Is there a way to get the old hboot back?
smash_07 said:
Well i ended up doing what you all suggested and flashed the RUU with the 2.10 european rom with the goldcard in it.
But something went wrong and my Desire S is in a strange situation. For some reason the Goldcard did not work like the first time and gave me a CID error. But it flashed the hboot 2.00.0002 but retained the 1.28 rom i had installed on it. I have used the HTCDev method to unlock the bootloader but everytime i try to flash the 1.28 RUU again (to flash the old hboot again) it gives me an "unknown error" that is actually a security error.
Is there a way to get the old hboot back?
Click to expand...
Click to collapse
My reply to this post of yours is already a hint.
Use search PLEASE.
Hi,
Apologies that this will very much be a noob post but help would be very much appreciated. I bought a HTC sensation XE which was imported from Taiwan. I wanted to use an RUU that is from Europe (the most recent one I found, 1.73.401.4), so that I wouldn't have all the branded apps. To do this, I first followed the htcdev unlocking guide, and then tried to change the CID to superCID, which it did not allow. Instead, I changed the CID to HTC__001 which I thought would work for Europe RUU. I then tried running the RUU exe file, but it eventually came up with a 155 error and did not install. From what I can gather, this is because I actually needed S-OFF to change the regions of the device.
I read that it was best to undo the htcdev lock (or perhaps even to not have done it in the first place). So, I ran "fastboot oem lock". This seems to have worked, because the bootloader now reads 'RELOCKED'. However, when I load the phone and click on bootloader it flashes a load of green lines like this:
sd checking...
loading...[PG58DIAG.zip]
No image!
Loading...[PG58DIAG.nbh]
No image or wrong image!
...
Otherwise it seems to be loading the original ROM without any issues. I cannot find any files on the SD card that include PGD58DIAG in their name. I have now changed the CID to HTC__622, but I'm not sure if this was the original one (is there any way to find out now?).
Does anybody have suggestions on how I proceed from here? Just to recap:
- Taiwanese import HTC sensation XE
- Used HTCdev to unlock, but have now relocked
- Have changed the CID to HTC__001 and now to HTC_622; may not be original.
The questions I have are:
1) Are the green lines of text that I am getting about PG58DIAG important?
2) If I want to debrand the phone and ideally move to European unbranded RUU, what should I do now? Should I try S-OFF and then changing to superCID as in the guide by Alexp999 here (http://forum.xda-developers.com/showthread.php?t=1193033) - i.e. is it safe to do this, despite the green lines of text and having re-locked the htcdev?
Thank you so much for any assistance. I've really tried looking everywhere on here and can't seem to find a guide or thread that takes into account all my issues!
Oliver
**********
Software number 1.77.709.104
Baseband version 10.58.9035.00U_10.15.9035.02_2
Build number 1.77.709.104 CL239628 release-keys
Hboot: 1.18
1. That green "loading img" message you keep getting almost always normally occurs when you enter boot loader....it checks for RUU file in sdcard root folder. This is normal.
2. Root...super cid...the fastboot flash ruu
Just as FYI. Wasn't sure if you knew this so forgive me if you did.
RUU flashed in fast boot must my named "PG58IMG.zip"
RUU must be in root folder of sdcard
Sent from my HTC Pyramid using XDA
Choose the correct firmware from here
super sid not needed
Read and follow the instructions carefully
Thanks for the advice and the reassurance! From the sounds of things I shouldn't go ahead until I have the original RUU downloaded in case things go wrong. Can't seem to find it for 1.77.709.104 anywhere, so perhaps I'll wait to change ROMs until it gets posted somewhere!
Hi folks,
I'd like to buy a Sensation next month. I have read here and there and just want to ask you as Sensation owners because I trust xda-opinions more than any other
So, is it right I don't need to buy a Sensation XE for having better battery and higher cpu speed?
I read there is an overclocked ROM for Sensation putting it to 1,5 GHz instead of 1,2.
When I first heard about overclocking it was years ago in context of a normal pc. They said it will overheat and ruin the CPU. But since the Sensation and Sensation XE share the same hardware it should be harmless? Anyone who has deeper knowledge in overclocking arm cpu's ? Would be interesting in general for me.
Next is, I heard the EVO 3D battery fits into the Sensation and has more mA/h.
Or should I buy Sensation XE battery instead of Evo 3D?
Question 3 just for my interest: Sensation's codename is Pyramid. What's the XE's ?
Thanks in advance for your answers.
As far as I'm concerned, both the Sensation and the sensation XE have the same chipset. The Sensation's CPU was underclocked in order to sell the XE as the superior phone with beats. The XE and evo have the same capacity, both also have the temp. sensor.
Sent from my HTC Sensation 4G using XDA
theq86 said:
Hi folks,
I'd like to buy a Sensation next month. I have read here and there and just want to ask you as Sensation owners because I trust xda-opinions more than any other
So, is it right I don't need to buy a Sensation XE for having better battery and higher cpu speed?
I read there is an overclocked ROM for Sensation putting it to 1,5 GHz instead of 1,2.
When I first heard about overclocking it was years ago in context of a normal pc. They said it will overheat and ruin the CPU. But since the Sensation and Sensation XE share the same hardware it should be harmless? Anyone who has deeper knowledge in overclocking arm cpu's ? Would be interesting in general for me.
Next is, I heard the EVO 3D battery fits into the Sensation and has more mA/h.
Or should I buy Sensation XE battery instead of Evo 3D?
Question 3 just for my interest: Sensation's codename is Pyramid. What's the XE's ?
Thanks in advance for your answers.
Click to expand...
Click to collapse
Hi,
1.Correct.No need to spend extra on xe.
2.All Sensations can be clocked/overclocked up to 1.8 GHZ(currently)
3.Choice of battery is yours.
4.EVO,XE,Anker battery all fit.
5. Sensation(XE,4G) = Pyramid.
Basically yes, no need to spend the extra cash. You can install an XE rom to a Sensation. Just buy a higher capacity because the stock one is bad, only 1520 mah.
Sent from my HTC Sensation using XDA
Okay, next questions regarding S-OFF.
As I could read there is currently no way to S-OFF pyramids > HBOOT 1.18.0000 and no way to downgrade hboot to 1.18.0000 if stock version is higher, right?
has anyone tested the method of changing the main version in the misc partition to be able to downgrade?
theq86 said:
Okay, next questions regarding S-OFF.
As I could read there is currently no way to S-OFF pyramids > HBOOT 1.18.0000 and no way to downgrade hboot to 1.18.0000 if stock version is higher, right?
has anyone tested the method of changing the main version in the misc partition to be able to downgrade?
Click to expand...
Click to collapse
Hi,
Hboot 1.18.0000 IS capable of s-off.
Check HERE and HERE
malybru said:
Hi,
Hboot 1.18.0000 IS capable of s-off.
Check HERE and HERE
Click to expand...
Click to collapse
Yes, sure, I read it See above, I meant HBOOTS higher than 1.18.0000 ;-)
theq86 said:
Yes, sure, I read it See above, I meant HBOOTS higher than 1.18.0000 ;-)
Click to expand...
Click to collapse
Hi,
You are correct about higher than 1.18.0000
theq86 said:
Okay, next questions regarding S-OFF.
As I could read there is currently no way to S-OFF pyramids > HBOOT 1.18.0000 and no way to downgrade hboot to 1.18.0000 if stock version is higher, right?
has anyone tested the method of changing the main version in the misc partition to be able to downgrade?
Click to expand...
Click to collapse
Downgrading your hboot shouldn't be necessary. Just a hassle if you ask me. One way is using tacoroot to first gain temp root, then running revolutionary.
I would suggest that you try the Revolutionary tool first of all. Stay far away from HTCDev.
If Revolutionary should fail, then go for Taco Root. Stay far away from HTCDev, as chance of bricking is slightly higher than normal.
So yes 1.18 is still easily doable, whereas 1.27 is much harder. So don't upgrade to ICS if you want to root.
Sent from my HTC Sensation Z715e using xda premium
Okay, thx.
I expect HBOOTS higher than 1.18.0000 still to support the revolutionary method. Unfortunately the rev tool does not allow it. Seems as if the rev team is making a long sleep at the moment.
But when I have hands on a Sensation I could try some methods of downgrading that I learned from other htc phone experiences.
thanks for your help guys.
Sgt.Incontro said:
Downgrading your hboot shouldn't be necessary. Just a hassle if you ask me. One way is using tacoroot to first gain temp root, then running revolutionary.
I would suggest that you try the Revolutionary tool first of all. Stay far away from HTCDev.
If Revolutionary should fail, then go for Taco Root. Stay far away from HTCDev, as chance of bricking is slightly higher than normal.
So yes 1.18 is still easily doable, whereas 1.27 is much harder. So don't upgrade to ICS if you want to root.
Sent from my HTC Sensation Z715e using xda premium
Click to expand...
Click to collapse
In fact, the htcdev method just changes 4 bytes in the misc partition to indicate LOCKED, RELOCKED and UNLOCKED state. So this is easily reversable ;-)
theq86 said:
In fact, the htcdev method just changes 4 bytes in the misc partition to indicate LOCKED, RELOCKED and UNLOCKED state. So this is easily reversable ;-)
Click to expand...
Click to collapse
Hi,
I thought the HTC DEV method only unlocks the recovery and system partitions .
It leaves the radio partition locked.
Do you have a reverse for this?
Well, I can only speak of my HTC Wildfire S experiences. But the methods we developed over there seem to be HTC generic.
So, here's how htcdev works:
The Bootloader (hboot) "talks" to the radio via some kind of remote procedure call. the radio firmware itself is capable of writing without security to any place on the phone.
so whenever you flash something, be it a RUU, a PG***IMG.zip, or via fastboot it is done via the bootloader.
Now, for some older phones the bootloader had to be upgraded in order to use htcdev. Newer devices already have hboots capable of being unlocked.
So what's happening? We found out, that all the get_identifier_token stuff is not necessary to unlock the bootloader. This is just done by HTC to get our devices identifiers for their database to tell they have been unlocked, hence warranty screwed.
The funny and dumb thing now is, that the only thing the process changes is 4 bytes in the misc partition. At some offset :
HTCU indicates an unlocked device
HTCL indicates a re-locked device (fastboot oem lock will relock it but leaving a trace for htc)
empty (hex 00 00 00 00) indicates an untouched device.
So what happens if you have HTCU ?
The bootloader will recognize unlocked state and disable the signature check for /system, /recovery, /boot and some other partitions.
The NAND write lock on /system e.g. is done by the kernel. A vanilla kernel will remove the restrictions.
This is why even with locked bootloader, ClockworkMod Recovery is able to write on protected partitions ;-)
(at least on mtd based phones, sensation is eMMc based)
The radio is yet protected by another security measure. It's blocks are marked as bad and the radio area is usually not mapped to any partition.
I'm very interested in how this all is done on Pyramid. Maybe we can get new ideas from it.
theq86 said:
Well, I can only speak of my HTC Wildfire S experiences. But the methods we developed over there seem to be HTC generic.
So, here's how htcdev works:
The Bootloader (hboot) "talks" to the radio via some kind of remote procedure call. the radio firmware itself is capable of writing without security to any place on the phone.
so whenever you flash something, be it a RUU, a PG***IMG.zip, or via fastboot it is done via the bootloader.
Now, for some older phones the bootloader had to be upgraded in order to use htcdev. Newer devices already have hboots capable of being unlocked.
So what's happening? We found out, that all the get_identifier_token stuff is not necessary to unlock the bootloader. This is just done by HTC to get our devices identifiers for their database to tell they have been unlocked, hence warranty screwed.
The funny and dumb thing now is, that the only thing the process changes is 4 bytes in the misc partition. At some offset :
HTCU indicates an unlocked device
HTCL indicates a re-locked device (fastboot oem lock will relock it but leaving a trace for htc)
empty (hex 00 00 00 00) indicates an untouched device.
So what happens if you have HTCU ?
The bootloader will recognize unlocked state and disable the signature check for /system, /recovery, /boot and some other partitions.
The NAND write lock on /system e.g. is done by the kernel. A vanilla kernel will remove the restrictions.
This is why even with locked bootloader, ClockworkMod Recovery is able to write on protected partitions ;-)
(at least on mtd based phones, sensation is eMMc based)
The radio is yet protected by another security measure. It's blocks are marked as bad and the radio area is usually not mapped to any partition.
I'm very interested in how this all is done on Pyramid. Maybe we can get new ideas from it.
Click to expand...
Click to collapse
Hi,
This is all very interesting and may well apply to the Sensation.
I have bookmarked this post for future reference.
I can only thank you,as I am out of thanks for the day.
When I get my Sensation next month I wil definately experiment a little and try to make use of some of our experience we made over there at wfs forums.
theq86 said:
When I get my Sensation next month I wil definately experiment a little and try to make use of some of our experience we made over there at wfs forums.
Click to expand...
Click to collapse
Hi,
I look forward to your results...
malybru said:
Hi,
This is all very interesting and may well apply to the Sensation.
I have bookmarked this post for future reference.
I can only thank you,as I am out of thanks for the day.
Click to expand...
Click to collapse
Ha don't worry malybru I hit the thanks button for you, just wish I could hit it again for me lol.
At theq86, I am really looking forward to having someone such as yourself working with the Sensatio. Oh and I am also book marking that post.
T-Macgnolia said:
Ha don't worry malybru I hit the thanks button for you, just wish I could hit it again for me lol.
At theq86, I am really looking forward to having someone such as yourself working with the Sensatio. Oh and I am also book marking that post.
Click to expand...
Click to collapse
Hi T,
Good to see you here.
Thanks for that.
I believe theq86 has something that could be very useful to a lot of people trying to s-off from a higher hboot than 1.18.0000
theq86 said:
Well, I can only speak of my HTC Wildfire S experiences. But the methods we developed over there seem to be HTC generic.
So, here's how htcdev works:
The Bootloader (hboot) "talks" to the radio via some kind of remote procedure call. the radio firmware itself is capable of writing without security to any place on the phone.
so whenever you flash something, be it a RUU, a PG***IMG.zip, or via fastboot it is done via the bootloader.
Now, for some older phones the bootloader had to be upgraded in order to use htcdev. Newer devices already have hboots capable of being unlocked.
So what's happening? We found out, that all the get_identifier_token stuff is not necessary to unlock the bootloader. This is just done by HTC to get our devices identifiers for their database to tell they have been unlocked, hence warranty screwed.
The funny and dumb thing now is, that the only thing the process changes is 4 bytes in the misc partition. At some offset :
HTCU indicates an unlocked device
HTCL indicates a re-locked device (fastboot oem lock will relock it but leaving a trace for htc)
empty (hex 00 00 00 00) indicates an untouched device.
So what happens if you have HTCU ?
The bootloader will recognize unlocked state and disable the signature check for /system, /recovery, /boot and some other partitions.
The NAND write lock on /system e.g. is done by the kernel. A vanilla kernel will remove the restrictions.
This is why even with locked bootloader, ClockworkMod Recovery is able to write on protected partitions ;-)
(at least on mtd based phones, sensation is eMMc based)
The radio is yet protected by another security measure. It's blocks are marked as bad and the radio area is usually not mapped to any partition.
I'm very interested in how this all is done on Pyramid. Maybe we can get new ideas from it.
Click to expand...
Click to collapse
This actually explains how did I manage to downgrade my Desire. It wasn't possible until I have manually wiped out entire phone's memory with QtAdb. After reboot recovery was reporting error with misc partition. After that RUU wasn't complaining about main version being newer.
Odoslané z môjho HTC Sensation XE with Beats Audio Z715e
Hello,
I am quite confused about the term SuperCID and what it means. My sister got a HTC One S. I unlocked and unrooted it for her quite a long time ago. Now, I want to get S-off but I can't do it because I don't have SuperCID. I read on the forum and some people say that Super CID means your phone is unlocked, while other say you have to use the command "fastboot oem readcid" to check if you get SuperCID.
I use "fastboot oem readcid" on the HTC One S and it shows TMOB010. Then does that mean that I don't have SuperCID? Then what exactly is SuperCID when the HTC One S is already shown "Unlocked and Tampered" on the fastboot screen. Pleas let me know. I am quite confused with all this terminology. I can look up direction to get SuperCID but I want to be sure that the phone has it or not before I proceed.
Thank you for your help
vi6s said:
Hello,
I am quite confused about the term SuperCID and what it means. My sister got a HTC One S. I unlocked and unrooted it for her quite a long time ago. Now, I want to get S-off but I can't do it because I don't have SuperCID. I read on the forum and some people say that Super CID means your phone is unlocked, while other say you have to use the command "fastboot oem readcid" to check if you get SuperCID.
I use "fastboot oem readcid" on the HTC One S and it shows TMOB010. Then does that mean that I don't have SuperCID? Then what exactly is SuperCID when the HTC One S is already shown "Unlocked and Tampered" on the fastboot screen. Pleas let me know. I am quite confused with all this terminology. I can look up direction to get SuperCID but I want to be sure that the phone has it or not before I proceed.
Thank you for your help
Click to expand...
Click to collapse
SuperCID will be a seven digit string of the same number (1111111, 2222222 etc). These CIDs gain special access to partitions normally locked down (how they test stuff). Having this CID means you can do more stuff, meaning write different sectors etc.
So TMOB010 means you don't have it.
To make a complete answer; unlocked is just when you unlock your phone via HTC's website which allows you special access to partitions and fastboot, however not all partitions are accessible - whereas with SuperCID you can access them all.
ZackehSoul said:
SuperCID will be a seven digit string of the same number (1111111, 2222222 etc). These CIDs gain special access to partitions normally locked down (how they test stuff). Having this CID means you can do more stuff, meaning write different sectors etc.
So TMOB010 means you don't have it.
To make a complete answer; unlocked is just when you unlock your phone via HTC's website which allows you special access to partitions and fastboot, however not all partitions are accessible - whereas with SuperCID you can access them all.
Click to expand...
Click to collapse
correction.
supercid does not allow special acces of different partitions, who told you that.
its just a masterkey for stock softwareversion implementation, nothing more.
its either a eng-hboot or a s-off implementation that gives you that freedom.
real187 said:
correction.
supercid does not allow special acces of different partitions, who told you that.
its just a masterkey for stock softwareversion implementation, nothing more.
its either a eng-hboot or a s-off implementation that gives you that freedom.
Click to expand...
Click to collapse
That's incorrect. You can have a stock HBOOT and be S-ON with SuperCID. SuperCID isn't the implementation, it's a way to gain the implementation. And it allows you special access in that it's a masterkey...
Example; I gain S-OFF with Moonshine. Does that mean I have SuperCID? No. Does that mean I have an ENG HBOOT? Yes. Can I reflash that HBOOT to stock and keep S-OFF? Yes.
SuperCID allows the flashing of any ROM regardless of the carrier it was meant for (special access) and it also allows for the writing of Ext_ROM (special access, again - see CID LOCK).
ZackehSoul said:
That's incorrect. You can have a stock HBOOT and be S-ON with SuperCID. SuperCID isn't the implementation, it's a way to gain the implementation. And it allows you special access in that it's a masterkey...
Example; I gain S-OFF with Moonshine. Does that mean I have SuperCID? No. Does that mean I have an ENG HBOOT? Yes. Can I reflash that HBOOT to stock and keep S-OFF? Yes
SuperCID allows the flashing of any ROM regardless of the carrier it was meant for (special access) and it also allows for the writing of Ext_ROM (special access, again - see CID LOCK).
Click to expand...
Click to collapse
No supercid is just a generic cid.
It has no hardware advantage over a stock cid. It's mainly used for unbranding.
I always have my devices on stock hboot and stock cid. Only s-off is what I want.
Haven't found anything I couldn't flash.
Like your link says VENDERLOCK thus software.
It's the unlock (xda-dev) part that provides the access of certain partitions.
With s-off even more is available.
S-off and hboot have no direct relation.
Example: Lower stock hboots can flash radio with only a unlocked device. Higher can't.
What's the difference a device unlocked supercid and a device unlocked unbranded cid. ?
Is there any rom custom that can't be flashed with just unlocking,
Lets make it supercid can I flash more roms?
Its just an coincidence that with the newer devices supercid was needed for getting s-off. It didn't used to be that way.
Hell easy unlocking didn't even exist.
It was s-off or bust mostly.
The link you give is not that clear.
ext_rom have you read there description?
I don't think that's a really secured partition. Do you?
Typing on a phone is fukd if it gets to big.
Verstuurd van mijn HTC One S met Tapatalk
real187 said:
No supercid is just a generic cid.
It has no hardware advantage over a stock cid. It's mainly used for unbranding.
I always have my devices on stock hboot and stock cid. Only s-off is what I want.
Haven't found anything I couldn't flash.
Like your link says VENDERLOCK thus software.
It's the unlock (xda-dev) part that provides the access of certain partitions.
With s-off even more is available.
S-off and hboot have no direct relation.
Example: Lower stock hboots can flash radio with only a unlocked device. Higher can't.
What's the difference a device unlocked supercid and a device unlocked unbranded cid. ?
Is there any rom custom that can't be flashed with just unlocking,
Lets make it supercid can I flash more roms?
Its just an coincidence that with the newer devices supercid was needed for getting s-off. It didn't used to be that way.
Hell easy unlocking didn't even exist.
It was s-off or bust mostly.
The link you give is not that clear.
ext_rom have you read there description?
I don't think that's a really secured partition. Do you?
Typing on a phone is fukd if it gets to big.
Verstuurd van mijn HTC One S met Tapatalk
Click to expand...
Click to collapse
Yeah exactly it removes the vendor lock which gives you access to write partitions you otherwise wouldn't be allowed to in that way.
I think we're actually arguing the same point here dude Think I misread your point about HBOOT in the second post.
ZackehSoul said:
Yeah exactly it removes the vendor lock which gives you access to write partitions you otherwise wouldn't be allowed to in that way.
I think we're actually arguing the same point here dude Think I misread your point about HBOOT in the second post.
Click to expand...
Click to collapse
Hmm...., so, based on the info, it means SuperCID is not that different from generic CID. However, you need it to get S-Off, which in turn allows you to write to different partition. Because my ultimate goal is to get S-off to update my sister phone to the CyanogenMod 10.2. Is that correct or did I miss anything?
vi6s said:
Hmm...., so, based on the info, it means SuperCID is not that different from generic CID. However, you need it to get S-Off, which in turn allows you to write to different partition. Because my ultimate goal is to get S-off to update my sister phone to the CyanogenMod 10.2. Is that correct or did I miss anything?
Click to expand...
Click to collapse
Blunt answer: you need superCID for S-OFF, unlock isn't enough by itself.
with new windows phone recovery-tool 2.0.3+: http://go.microsoft.com/fwlink/?LinkID=525569
it downloads the RUU nbh and the UEFI nbh to the following path:
C:\ProgramData\HTC\Packages\Products\0P6B1400-T-MOB010
named like:
RUU_signed_2061.30.15001.531.nbh
UEFI_signed_2061.30.15001.531.nbh
i grabbed the download links with fiddler for people without the device:
Code:
https://softwarerepo.blob.core.windows.net/softwarerepo/80c33a50-3c4b-448b-9981-e5cd74d32236/UEFI_signed.nbh
https://softwarerepo.blob.core.windows.net/softwarerepo/80c33a50-3c4b-448b-9981-e5cd74d32236/RUU_signed.nbh
mainos partition is decrypted on-device during flashing (device model specific encryption).
the same also works for other variants of the htc one w8 like verizon and at&t.
would be cool if someone could post those rom url's too.
there is no tool to decrypt the mainos partition sadly but i hope someone skilled creates it.
Will it be possible to flash the T-mobile RUU on a Verizon phone? I need to get rid of the lock on the 4G channels on the verizon version.
in theory, modelid check on device will make it fail.
HD2Owner said:
in theory, modelid check on device will make it fail.
Click to expand...
Click to collapse
Any way to change model id with regestry hack? Maybe the same hack that allowed non-Lumia devices to install wp 10 technical preview?
that is not the same. it would have no effect in this case.
modelID is checked by bootloader before flashing. it aborts at 1% with error.
what you want is a signaturecheck/mid/cid unlocked bootloader. and you're not alone.
even if you reverse-engineer the bootloader and patch it, you need a way to get it on the device.
both things are incredibly difficult with wp8 nowadays because of the security measurements.
the previous work i did on wm/wp7 custom roms is not possible for wp8 until that happens.
The recovery tool does not work with the Verizon version of this phone (at least when i tested it the day the build came out). I had to use the leaked rom to flash back to Windows 8.1 on my Verizon Windows M8
I do have the Verizon .nbh's lying somewhere, will look for it when I get home