yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] meadhros:
Just want to recognize you for your use of "asshat"....a term regularly used by my wife...first time I ever saw it used elsewhere...kudos.:D
[AT&T, Rogers HTC One X, Telstra One XL] JeepFreak:
Which partitions are not signature checked/writable? I didn't see the list posted. I'm going to go through everything again, but I want to start with those.

Thanks,

Billy
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
Out of random curiosity and a hunch, if I remember correct a person, rogers device got S off while unlocking bootloader? If that's the case has anyone tried using that persons unlock token with a relocked bootloader to unlock?
[AT&T, Rogers HTC One X, Telstra One XL] eraste:
Good idea but isint the unlock token tied to each individual imei? would this cause issues?
[AT&T, Rogers HTC One X, Telstra One XL] equlizer:
You cannot use anyone's token. If we could, we wouldn't be having all these problems:rolleyes:
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
I was thinking of World of Warcraft, with their random 8 digit key thing. It works the same way. I was able to use my uncles for mine when I couldnt log in once by changing my identifier. it uses 16*8 diff variations. I just was curious if itd be the same but if its tied with the IMEI,we could all just spoof our IMEI's momentarily ;)

Edit** doing some research on this. It'd work but the original IMEI would become barred on the At&t network apparently. As if the phone became stolen.
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
I found that the dev htc one X's have these changes. RO.AA Maincid - HTC__01 and RO.AA Mainsku -401. I just can't locate where to change these :(. My idea is.. change these relock bootloader. resend to HTCdev the unlock crap. then unlock bootloader and see?
[AT&T, Rogers HTC One X, Telstra One XL] ThisWasATriumph:
Hmm I wonder... If we change our CID to HTC__01 and unlock, will it become S-off as well? This happened to one person. I wonder what his CID was...

Who wants to try it?

Also shouldn't it be HTC__001? That's the full 8 digits.
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
Your right HTC__001. That's my bad. I was tired. I've been comparing an engineering unit to mine. Only thing is I think I have to make these changes in diag mode through hboot rather than through a build.prop editor. Even if I edit everything via a build.prop editor it doesn't stick while in fastboot.
[AT&T, Rogers HTC One X, Telstra One XL] grankin01:
No dice on just changing the CID. It registers on my device as HTC__001 but after unlock still shows S=On. :(
[AT&T, Rogers HTC One X, Telstra One XL] ThisWasATriumph:
I think it may be more simple than that. I hex edited my mmcblk0p4MOD file to HTC__001 instead of CWS__001 but I'm hesitant to push it back to my phone because I already have it unlocked and I don't really want to go through the nightmare I went through the first time, except with the added risk of a brick... You should make sure the CID is really HTC__001 on the engineering unit by doing the fastboot oem readcid command in adb.

edit: nevermind I guess its more complicated after all haha
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
Just try it for us ;)
[AT&T, Rogers HTC One X, Telstra One XL] grankin01:
I just did. The command fastboot oem writecid HTC__001 changed my CID to just that and I made sure with both getvar all and oem readcid. I then locked the phone, got a new unlock_code.bin, and unlocked the device again. It still shows S=On. :(
[AT&T, Rogers HTC One X, Telstra One XL] ThisWasATriumph:
Looks like grankin01 already did.

So then I guess we should start looking around for the MainSKU variable next and try that. In combination with the HTC__001 CID of course.
[AT&T, Rogers HTC One X, Telstra One XL] grankin01:
It might work but I don't think S=Off is going to be quite that easy.

BTW, when you are set supercid the "fastboot oem writecid" command actually works for you instead of erroring out. I had set mine supercid but had a couple of places where it still showed CWS__001. I typed that command and it erased the backup CID and seems to have set all the other identifiers for it to SuperCID. :D
[AT&T, Rogers HTC One X, Telstra One XL] eraste:
Ahhh thats why i am having that issue i was wondering why the build.prop still had CWS__001 in some areas. Ill try that fasboot oem writecid command.

THanks
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
There's an app called cidgetter on the play store. I used that to see the complete build.prop file for the ENG unit. And CWS__001 for cids pop up everywhere I've been changing them to HTC__001. Main sku to 401. And the att identifiers been changing those to HTC.

After the bootloader thing I really maybe possibly be this easy *fingers crossed*
[AT&T, Rogers HTC One X, Telstra One XL] ThisWasATriumph:
Good to know thanks.

Well, there is some aspect of Niceppl's phone that is different that allowed him to get s-off through HTCDev. I'm working off the assumption that it was not just a random fluke and that there is a variable or two in the software that presented itself as a dev device. One must be the CID but I have no clue what the second or other ones are...

---------- Post added at 04:17 PM ---------- Previous post was at 04:10 PM ----------

I somehow doubt the fastboot oem get_identifier_token command reads off the build.prop but I guess it's worth a shot...
[AT&T, Rogers HTC One X, Telstra One XL] K4get:
could the dialer codes do anything
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
I keep getting invalid MMI code.
[AT&T, Rogers HTC One X, Telstra One XL] K4get:
the only one I got to do anything was the htc code
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
Could it be as simple as s-off phones having a different bootloader and we just need to dd the bootloader from am s-off phone onto an s-on phone?
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
i have compared the dd of hboot from my s-off unit and the one in ruu with hex

its the same

p.s kinda busy with life these days. i know some of yoy pmed me

i will try to get back to you asap

sorry
[AT&T, Rogers HTC One X, Telstra One XL] ThisWasATriumph:
Did you do these comparisons before or after updating? By updating to a newer ATT firmware, the difference might have been lost.
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
eh...?

I compared after i unlocked and s-offed, when i was still on rogers firmware, and compared with rogers ruu.
[AT&T, Rogers HTC One X, Telstra One XL] ThisWasATriumph:
Ah ok, I had assumed you had flashed an At&t Ruu after changing your CID. Still, I think there must be a difference in one of your partitions... We have to figure out why you got S-off. If the difference is in a place protected by the S-on/off then we're screwed...
[AT&T, Rogers HTC One X, Telstra One XL] equlizer:
When i try and change the cid i get this error:

C:\htc one x>fastboot oem writecid 11111111

...

(bootloader) elite_init_sd, SD card already power on

(bootloader) sdhw_7xxx_open: id=0

(bootloader) [SD_HW_ERR] SD: No device attached

(bootloader) 902910 902E20

FAILED (status read failed (No such file or directory))

finished. total time: 1.258s

But when i do adb devices it shows it connected. How do i change my cid? Im bootloader unlocked and rooted 1.73
[AT&T, Rogers HTC One X, Telstra One XL] grankin01:
What is your CID right now? If it is ROGER001 then you will have to hex edit mmcblk0p4 again to change it to 11111111. Then you can go back to fastboot and do your writecid command and it should work fine. ;)
[AT&T, Rogers HTC One X, Telstra One XL] equlizer:
some are saying it will re lock me. Is that correct?
[AT&T, Rogers HTC One X, Telstra One XL] ThisWasATriumph:
changing CIDs cannot relock you on its own
[AT&T, Rogers HTC One X, Telstra One XL] grankin01:
I changed mine from 11111111 to HTC__001 while I was unlocked and it never relocked mine so you shouldn't have a problem. The 'fastboot oem writecid 11111111' command hasn't worked for me unless I already had the CID spoofed as SuperCID. Then it works fine. ;)

---------- Post added at 11:15 PM ---------- Previous post was at 11:14 PM ----------

Beat me to it by seconds lol!
[AT&T, Rogers HTC One X, Telstra One XL] equlizer:
Now i get this (after running oneclick supercid)

C:\htc one x>fastboot oem writecid 11111111

...

(bootloader) Start Verify: 3

(bootloader) Start Verify: 3

(bootloader) TZ_HTC_SVC_DISABLE ret = 534642032 (0x1FDDFD70)

FAILED (status read failed (Too many links))

finished. total time: 1.138s

how do i confirm it changed?
[AT&T, Rogers HTC One X, Telstra One XL] ThisWasATriumph:
good now fastboot getvar cid to confirm.
[AT&T, Rogers HTC One X, Telstra One XL] equlizer:
says its cid 11111111 :D Rebooting! thx ;)

But.....[ro.aa.cidlist] [ROGER001] and same with maincid says ROGER001

[ro.cwkey]: ROGER001
[AT&T, Rogers HTC One X, Telstra One XL] Root-Maniac:
hope this doesnt sound to stupid but is there possibly an extra partition on the s off device telling the system to be s off???
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
well.. its not a stupid question. but previous hboot builds all have the S=on/off in an hboot partition.
[AT&T, Rogers HTC One X, Telstra One XL] Root-Maniac:
What I ment is there an extra partition or mmcblk that's on the s off device that has not been discovered?? I'm no dev so I'm sorry of these are stupid questions..
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
OH!! My bad, sorry. No there is not.
[AT&T, Rogers HTC One X, Telstra One XL] nugzo:
Edit: moved to PM
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
i think at this step, one of the dev(prefer he knows chinese..or better if he's in hk or china) got a device that's s-offed by "white card" and compare with a s-on unit to see where are the changes...maybe?

an idea won't hurt...
[AT&T, Rogers HTC One X, Telstra One XL] ThisWasATriumph:
I've been reading about s-off in the international and One S threads as well as for other HTC phones and I think it will be much easier to trick HTCdev into doing it for us rather that changing it manually. The methods to do that are very complicated, have been patched or require additional equipment. So far there haven't been any solid leads...
[AT&T, Rogers HTC One X, Telstra One XL] elbermu:
Are you S-Off?, can you send me a dump of mmcblk0p8? Wondering why that partition is all filled with 0's for an S-Off device.
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
yes...it's all 0s....do you still need it?..
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
Niceppl, may I get mmcblk0p4? I'm now curious about this too.

Edit** sorry, I meant mmcblk0p8
[AT&T, Rogers HTC One X, Telstra One XL] elbermu:
No, not needed then, is weird, mine is not that way. Wondering why yours is all 0?
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
Mmcblk0p8 aperently looks to become an Ext 4 with S=Off.
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
0p4 or 0p8?
[AT&T, Rogers HTC One X, Telstra One XL] elbermu:
yes, I think the same.
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
0p8.

Thank you
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
And mmcblk0p-7,8 and 13 are s-on s-on, s-off respectively.
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
it's all 0s...like all..
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
Odd why its wiped like that.
[AT&T, Rogers HTC One X, Telstra One XL] elbermu:
13 is the same for s-off and s-on...

~/android/play$ md5sum s-off/mmcblk0p13.img mine/mmcblk0p13.img

0cf320bf7bd847a8429a423a8d529ea6 s-off/mmcblk0p13.img
0cf320bf7bd847a8429a423a8d529ea6 mine/mmcblk0p13.img
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
can someone send me the dd of 0p7 and 0p8 from a s-on unit?

goodplayer@gmail.com
[AT&T, Rogers HTC One X, Telstra One XL] Zarboz:
with htc unlock doesnt it emulate your modified system partition?

just wondering looking in here

SBL3 Image Loaded, Delta.RPM Image Loaded, Delta.TZ Image Loaded, Delta.boot_auth.boot_hash.boot_flash_trans_sdcc.boot_flash_trans_sdcc_factory.boot_flash_dev_sdcc.fs_hotplug_api.c.Assertion phy_hdev != NULL failed.fs_hotplug_dev_state.c.Assertion phy_hdev->dev_state == HPDEV_UNDISCOVERED failed.Assertion phy_hdev->dev_state == HPDEV_DISCOVERED failed.Assertion phy_hdev->dev_state == HPDEV_UNMOUNTED failed.Assertion phy_hdev->dev_state == HPDEV_UNINITIALIZED || phy_hdev->dev_state == HPDEV_LOCKED || phy_hdev->dev_state == HPDEV_FORMATTING || phy_hdev->dev_state == HPDEV_UNMOUNTED failed.Assertion phy_hdev->dev_state == HPDEV_MOUNTED failed.Assertion phy_hdev->dev_state == HPDEV_UNINITIALIZED failed.fs_hotplug_iter.c.Assertion 0 failed.fs_hotplug_legacy_hdev.c.Assertion phy_hdev->legacy_hdev != NULL failed.fs_hotplug_partition.c.Assertion parti->is_locked == 0 failed.Assertion parti->is_formatting == 0 failed.Assertion parti->is_locked == 1 failed.Assertion parti->is_formatting == 1 failed.Assertion parti->ref_cnt >= 1 failed.Assertion hdev_name != NULL failed.Assertion parti != NULL failed.fs_hotplug_poll.c.Assertion phy_hdev->bdev_handle == NULL failed.Assertion phy_hdev->parti_list == NULL failed.Assertion phy_hdev->hdev_list == NULL failed.fs_blockdev_devnull_driver.c.Assertion devnull_ops != NULL failed./hdev/dev.null.BDEV_DEVNULL_DRIVER.BDEV_SD_DRIVER./hdev/sdc1./hdev/sdc2./hdev/sdc3./hdev/sdc4.fs_blockdev_sd_driver.c.Assertion sdcc_ops != NULL failed.fs_hotplug_parser.c.Assertion blk_cnt != 0 failed.fs_blockdev_sd.c.Assertion sd_data != NULL failed.Assertion handle != NULL failed.Assertion sdcc_handle != NULL failed.Assertion bytes_per_block != NULL failed.Assertion blocks != NULL failed.Assertion bdev != NULL failed.Assertion dev->driveno < max_sd_slots failed.......C...øÿÿÿ....................C..

these are lines 00018c70-00019390

notice this part right here

Delta.boot_auth.boot_hash.boot_flash_trans_sdcc.boot_flash_trans_sdcc_factory.boot_flash_dev_sdcc.fs_hotplug_api.c.Assertion phy_hdev != NULL failed.fs_hotplug_dev_state.c.Assertion phy_hdev->dev_state == HPDEV_UNDISCOVERED failed.Assertion phy_hdev->dev_state == HPDEV_DISCOVERED failed.Assertion phy_hdev->dev_state == HPDEV_UNMOUNTED failed.Assertion phy_hdev->dev_state == HPDEV_UNINITIALIZED || phy_hdev->dev_state == HPDEV_LOCKED |

the portions talking about hpdev flag noted

also this part from line 5460-5480 caught my eye

SDRAM_HW_Init : interface_name %d, chip_select %
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
is this from 0p8?
[AT&T, Rogers HTC One X, Telstra One XL] elbermu:
sent

10 chars here
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
Acording to niceppl mmcblk0p13 is also all 0's.

Wtf?!
[AT&T, Rogers HTC One X, Telstra One XL] Zarboz:
yes

lol

mmcblk0p13

HTC-SECURITY-REC
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
yes..it is

ok..i compared 0p7 0p8 s-on vs s-off

0p7 has alot of diff...

0p8 is totally diff...s-off is just empty on mine....

for 0p13...i dont have the dd from s-on so i dont know how it looks like..

but mine shows like below:

HTC-SECURITY-REC:00000000000000000000.....

0 throughout....till the end.

i think the key is in 0p7...maybe depends on what 0p7 it wipe the 0p8 and 0p13 blk..
[AT&T, Rogers HTC One X, Telstra One XL] Zarboz:
your blk13 is the same as mine and i am s-on

the difference in is p7 and p8
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
what about all other blks...

i dont have a s-on unit to compare....

hope 0p7 and 0p8 are the only ones...

not sure if 0p7 is diff because of 0p8... or the other way around...

let's assume if those are the only difference.... what is the next step for us to do...

is 0p8 writeable blk? anyone dare to wipe it and unlock again?
[AT&T, Rogers HTC One X, Telstra One XL] Zarboz:
if i wasnt in the middle of house hunting and moving i would be happy to risk my device...

but i cant right now

wtf is this

/home/jonglin/repos/8960_sbl/core/boot/secboot3/common/boot_flash_trans_sdcc.c..ÔŒ..L.../home/jonglin/repos/8960_sbl/core/boot/secboot3/common/boot_flash_dev_sdcc.c.....Ç......”¤...ú../home/jonglin/repos/8960_sbl/core/boot/secboot3/common/boot_flash_dev_sdcc_if.c
[AT&T, Rogers HTC One X, Telstra One XL] Adam5400:
My p8 is empty as well, but I'm S-ON.

(I have a One S, but for all intents and purposes, other than hardware differences the partition structure is all the same.)
[AT&T, Rogers HTC One X, Telstra One XL] Zarboz:
completely different for s-off stuff unless we find a weakness with the processor coding
[AT&T, Rogers HTC One X, Telstra One XL] Adam5400:
The CID was in the exact same place, same offset even. Obviously the radios, and hboot are different, but I've been following this thread and all of the partition structure is the same and the same exploits work.
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
I'm fedexing my s-on but unlocked unit back to HTC tomorrow for glass replacement. If you want something tested with DD or pushing an img to a partition, I'm your guy....post back ASAP.
[AT&T, Rogers HTC One X, Telstra One XL] Zarboz:
adb shell
$su
# dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7
# dd if=/dev/block/mmcblk0p8 of=/sdcard/mmcblk0p8
# exit
$ exit

adb pull /sdcard/mmcblk0p7
adb pull /sdcard/mmcblk0p8

with HXD replace the contents of those files with all 0's

ensure the file sizes are EXACTLY the same

adb push mmcblk0p13 /sdcard
adb push mmcblk0p8 /sdcard

adb shell
$su
#dd if=/sdcard/mmcblk0p7 of=/dev/block/mmcblk0p7
#dd if=/sdcard/mmcblk0p8 of=/dev/block/mmcblk0p8
#exit
$exit

adb reboot bootloader

if all went well you MIGHT see some changes

there is also a HUGE possibility this will just brick the device
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
I assume the P13 in the second section of instructions was a mistake.

I think this is a bad idea. my P7 parition contains a lot of strings, my P8 partition contains what seems like hardware checks based on the strings. How about I just get these files to you? Do you have P7/P8 from an S-on?
[AT&T, Rogers HTC One X, Telstra One XL] elbermu:
p7 seems to be a database, I tell for the structure, but 8 maybe is something we can shot, p13 has the same hash even in different versions, so if you are willing to take the chance, just:

adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/mmcblk0p8.img"
adb pull /sdcard/mmcblk0p8.img mmcblk0p8MOD.img
dd if=/dev/zero of=mmcblk0p8MOD.img bs=1 count=$(stat -c%s mmcblk0p8MOD.img)
adb push mmcblk0p8MOD.img /sdcard/
adb shell su -c "dd if=/sdcard/mmcblk0p8MOD.img of=/dev/block/mmcblk0p8"

Edit: Modified second line, forgot the original file
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
Digging through P8 there's a ton of stuff in mine. Dram, cpu frequencies, sbl_init, etc. I'm not very knowledgeable here but I feel like our s-on hboot is calling p8 for all of the security initialization. If we kill it without an hboot built for s-off we are just going to blow it up. Thoughts?

---------- Post added at 09:08 PM ---------- Previous post was at 09:05 PM ----------

and on my MAC the dd to zero everything is producing "no value for specified count" error - and error is in stat command, mac doesn't like -c switch
[AT&T, Rogers HTC One X, Telstra One XL] elbermu:
hboot is the same for s-on and s-off.

For mac, uff, not much knowledge in there, but check if this command return an integer:

ls -l mmcblk0p8MOD.img | awk {'print $5'}

if so, replace with this line:

dd if=/dev/zero of=mmcblk0p8MOD.img bs=1 count=$(ls -l mmcblk0p8MOD.img | awk {'print $5'})
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
OK got it DD'd. No brick, but no s-off. Repulled mmcblk0p8 after reboot from /dev/block and opened in hex editor to confirm the 00'd file stuck. It did.
[AT&T, Rogers HTC One X, Telstra One XL] ptesmoke:
Redo the htcdev unlock....
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
One step ahead of you. relocked, then unlocked (after producing new token). no dice. S-ON. At once point I did have a "security warning" on the hboot screen up near the tampered notice. It's gone now FWIW. S-on and bl-unlocked still.

Why don't we dd all the damn partitions off that s-off device? ;)

---------- Post added at 09:58 PM ---------- Previous post was at 09:53 PM ----------

What does P7 look like on our s-off device? I'm willing to try that as well. But we have about 30 minutes before I sign out and this thing is going fedex tomorrow.
[AT&T, Rogers HTC One X, Telstra One XL] JeepFreak:
My money is on 2, 8, or 11. If you need those from an s-off device, hit me up.

Billy
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
check your pm.
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
ok if you are willing to do it, i will dd all partition and put in my dropbox tmr

leave ur dropbox email below or pm me.
[AT&T, Rogers HTC One X, Telstra One XL] Zarboz:
He is mailing the unit back for maintainence
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
lol............. .......
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
Anyone know how to DD the hboot file itself?

IDEA- get the hboot file. Modify it. Use the computer to create a ram disk (like with Photoshop) or for the some of us with crazy ammount of Ram in our computers use it to store modified hboot file. Reboot phone to fastboot and push new hboot file/image with modified files.

I don't know how to DD the hboot.
[AT&T, Rogers HTC One X, Telstra One XL] JeepFreak:
Uhhh... that doesn't make a lick a sense to me, but hboot is mmcblk0p12.

HTH,

Billy
[AT&T, Rogers HTC One X, Telstra One XL] Adam5400:
Hboot is signature checked at start up; if you modify it in anyway and then put it back, the device will be bricked.

Someone in the One S forums just edited a string in Hboot, not even code and it caused the sig check to fail and bricked his device.

Edit:

Though if you did just want to look around in Hboot in a hex editor or whatever you can pull the image like this:

su

dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12.img

Then you can take it off of the sdcard partition and look around on your computer. Just don't flash it back.
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
the hboot is the same for both s-on and off unit...

i verified....

its alos the same as the one in ruu....which make sense..
[AT&T, Rogers HTC One X, Telstra One XL] elbermu:
hboot is the same for s-on and s-off

md5sum mine/mmcblk0p12.img s-off/mmcblk0p12.img
9f8bc020ef18bdaddcc1cf851af6bd30 mine/mmcblk0p12.img
9f8bc020ef18bdaddcc1cf851af6bd30 s-off/mmcblk0p12.img
[AT&T, Rogers HTC One X, Telstra One XL] Prfndhatrdofman:
Does someone need all of the partitions from an S-Off device? I have an S-Off AT&T device. I already gave the partitions from it to sk806 but I can provide a link to download if needed.
[AT&T, Rogers HTC One X, Telstra One XL] nugzo:
So you are the lucky one :) Thank you for all of your help!
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
thx i was gonna do it tmr...

i need s-on images hehe
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
There's the mystery come to light. Thank you for your help :)!

If it's cool with you may I get the DL link? It'd be greatly appreciated.
[AT&T, Rogers HTC One X, Telstra One XL] Adam5400:
I wasn't suggested they weren't...

I was just responding to that guy because he wanted to change hboot or something.
[AT&T, Rogers HTC One X, Telstra One XL] ThisWasATriumph:
I suggest we create some sort of shared dropbox folder containing s-on and off partitions so we have better access to this stuff.
[AT&T, Rogers HTC One X, Telstra One XL] dkirchik:
I was planning on trying a poison idea from iPhone 3g days. My main concern is trying to get the computer to act as a bootable microsd to the phone. In theory it can be done allocating 3-4gb of ram.
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
yea we should... prefer both with same fresh ruu...

if someone with s-on would like to create that with me. pm me
[AT&T, Rogers HTC One X, Telstra One XL] JeepFreak:
I'll email it to you tomorrow AM since I have your addy already.

Billy
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
Not shipping shattered device back until later today or tomorrow. If you want any of the other s-off parititions dd'd and tested, advise asap.

---------- Post added at 07:42 AM ---------- Previous post was at 07:40 AM ----------

It's not particularly funny, this glass is weak.