yashsingh1/xdaforums huggingface dataset:
[HTC One X] Thunder07:
ya i was just thinking the same... and they could limit everything outside the numbers hex as an abstract

but also they'll need to take length into account as 1.29000 > 1.29

but ya its doable :/

EDIT:

it was a stab in the dark... but thats as much as we can do

also considering how i set the radiover = **Thunder07** i did take it into account but didnt think htc would be this smart...

unless a phone was hacked like this :p
[HTC One X] audioslim:
Not exactly true. If its evaluated as string its very possible
[HTC One X] Thunder07:
As a pure string you can't... You can only see if they are the same or not but not higher or lower...

But as kholk said they can convert them to hex and compared them.

Sent from my HTC One X
[HTC One X] arabmed:
i tray use this command fastboot update (file name)

i tray use this command fastboot update (file name)

i put file ota update i reseve this:

C:\htcsen>fastboot update update.zip

archive does not contain 'android-info.txt'

archive does not contain 'android-product.txt'

error: update package has no android-info.txt or android-product.txt

i put file firmware.zip from ota i reseve this

C:\htcsen>fastboot update firmware.zip

Whoops: didn't find expected signature

read_central_directory_entry failed

error: failed to access zipdata in 'Ysⁿ■'

i put file rom.zip from ruu :

C:\htcsen>fastboot update rom29-12-eur.zip

Whoops: didn't find expected signature

read_central_directory_entry failed

error: failed to access zipdata in 'ن¶↓┼ù☼àخGىtv»ج╬é▄}x%P≈ⁿDً╜╩♂„¤→UçةùقWس╞èJ╙2

dëً~N/ٍسوû8ئiy~■│╧╖←←\m■░{ ùث*☺└حٌùْ>*▼∟7╕@n╠ة~û(├K♫#▀◄»G♀'

then i put hboot zip file (hboot_CL21401_stable.img) and see

C:\htcsen>fastboot update PJ46IMG.zip

archive does not contain 'boot.img'

error: update package missing boot.img

i add boot image to this file and see

C:\htcsen>fastboot update hbootcl21410boot.zip

archive does not contain 'boot.sig'

archive does not contain 'recovery.img'

archive does not contain 'system.img'

error: update package missing system.img

i add all img file to hboot1214 zip and see

C:\adb>fastboot update hboot_CL21401_stable.zip

archive does not contain 'boot.sig'

archive does not contain 'recovery.img'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: 0.96.0000

Baseband Version.....: 2.1204.127.19

Serial Number........: HT251*******

--------------------------------------------

sending 'boot' (4278 KB)...

OKAY [ 1.279s]

writing 'boot'...

(bootloader) Format partition LNX done

OKAY [ 0.484s]

sending 'system' (960424 KB)...

FAILED (remote: (00000006))

finished. total time: 2.168s

the fastboot dont chek for expected signature and start sending file ?????
[HTC One X] arabmed:
factboot dont chek signature of zip file ??????

factboot dont chek signature of zip file ??????
[HTC One X] orb3000:
On topic posting will make you stay away from a ban
[HTC One X] Thunder07:
Just to be technically correct the phone checks for signature and not fastboot,

I'll have a look at this later but is your bootloader unlocked... If so you can flash kernel & recovery using the normal way or through HTC ruu through a zip which isn't signed,

If you have an locked bootloader it probably won't flash without a signature.

But it would be something if it did but I don't see it being that easy.

Sent from my HTC One X
[HTC One X] arabmed:
but factboot cheks for signaure for other file

but factboot cheks for signaure for other file and dont send file to phone

C:\htcsen>fastboot update firmware.zip

Whoops: didn't find expected signature

read_central_directory_entry failed

error: failed to access zipdata in 'Ysⁿ■'

C:\htcsen>fastboot update rom29-12-eur.zip

Whoops: didn't find expected signature

read_central_directory_entry failed

error: failed to access zipdata in 'ن¶↓┼ù☼àخGىtv»ج╬é▄}x%P≈ⁿDً╜╩♂„¤→UçةùقWس╞èJ╙2

dëً~N/ٍسوû8ئiy~■│╧╖←←\m■░{ ùث*☺└حٌùْ>*▼∟7╕@n╠ة~û(├K♫#▀◄»G♀'

the firmware.zip and rom29-12-eur.zip has signature from htc

C:\adb>fastboot update hboot_CL21401_stable.zip

archive does not contain 'boot.sig'

archive does not contain 'recovery.img'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: 0.96.0000

Baseband Version.....: 2.1204.127.19

Serial Number........: HT251*******

--------------------------------------------

sending 'boot' (4278 KB)...

OKAY [ 1.279s]

writing 'boot'...

(bootloader) Format partition LNX done

OKAY [ 0.484s]

sending 'system' (960424 KB)...

FAILED (remote: (00000006))

finished. total time: 2.168s

the hboot_CL21401_stable.zip dont have

rom29-12-eur.zip + hboot_CL21401_stable.img = hboot_CL21401_stable.zip
[HTC One X] AliceXES:
We have the source code for fastboot, so there are 2 variants:

a) most likely - phone will reject the file with a wrong signature, even if fastboot sends it

b) this may work :)
[HTC One X] mkrle:
Phone checks for signature, and not fastboot.
[HTC One X] audioslim:
Sorry mate your wrong when comparing strings the ascii values of the chars are compared and yes they can be greater equal less than or otherwise. 1 as in ASCII char 49 is less than A which us ASCII char 65 thats how string comparison works

Ps im a senior analyst programmer i do this all day.long
[HTC One X] promise forever:
Here is the way for unlocked one x to get super cid ,any help?
[HTC One X] ste1164:
Couldnt we use the temp root method to get super CID? Or will we lose it when the phone reboots.
[HTC One X] Rusty!:
Quite possibly, it could all be done from an ADB shell.
[HTC One X] glukosio:
i'm trying but i can't find anything in mmcblk0p17 nor in mmcblk0p4... p17 contains only 00 in every point and p4 is full of various letters but nothing about CID
[HTC One X] Rusty!:
Well 17 is definitely misc, which is what needed editing on the AT&T One X.
[HTC One X] KrisPerry:
Translation?
[HTC One X] glukosio:
maybe it's only on at&t hox... because in mine i can't find anything... just empty space

EDIT: i found something in p17! FNOC (adr. hex 23FC), and later 1.1204.105.14 (adr. hex 7000)... i'll search it all, maybe i'll find something
[HTC One X] Rusty!:
Nah, misc on the AT&T One X is mmcblk0p4

Might be for a One XL though, but it would be bit of a co-incidence for the T3 HOX to have the same misc partition # as a HOXL.
[HTC One X] xmoo:
Guys, here the new HBOOT 1.12 which is included in the 2.15 Test RUU.

This is a SHIP HBOOT.

Release date of HBOOT June 28.
[HTC One X] Thunder07:
Yes this is not directly,

I didn't say you can't I just said not directly.

Sent from my HTC One X
[HTC One X] Thunder07:
You should label it for s-off only and won't give s-off before you are spammed.

Sent from my HTC One X
[HTC One X] VIIRU§:
Do take this the wrong way I thought New hboot is bad for any hope for S-OFF
[HTC One X] Thunder07:
not always...

its not like we found a exploit that htc fixed and its very unlikely they'll find it out themselves... doesnt mean they cant

or that they dont check threads like this to block any lead we have on future exploits to limit the number of s-off

just aswell their update could have introduced an exploit that wasnt available before hand due to bad coding on their part
[HTC One X] VIIRU§:
Idk about HTC but I know Apple hires people to use sites like this and monitor exploits for jailbreaks and other cydia apps.
[HTC One X] Thunder07:
"adb shell strings /dev/block/mmcblk0p17"

stuff they you'll find are mainver ,FNOC ,radiover

i had a look at the site which says its for htc one x S720e which i googled

its codename is supreme but its a tegra 3, so i dont know if they are the same

i used an online ocr to get the text and this is my translation

he also mentions the mmcblk0p4 which might mean he has a different kernel for this or something

actually he reminds be of blubbers... but it makes no sense as this information was not mapped

if you have access to the site give us the zip file he takes about in the pictures if he has it attached

edit:

i think its useless though they are different they are the same every other way

http://www.ug7.net/phone/View/32/685.htm

both of them say its for the T version which i guess refers to HTC One V T320e

anyway the zip will be helpful
[HTC One X] glukosio:
your translation seems to be a chinese story :D

however... i don't have mainver in myne mmcblk0p17 but only FNOC and radiover. if you have mainver maybe you can change it and put the file again into /dev/block?
[HTC One X] Thunder07:
you cant change it... well you can but after reboot it becomes null

try

fastboot oem rebootRUU

fastboot reboot

adb shell strings /dev/block/mmcblk0p17

and the mainver would probably be there
​
[HTC One X] glukosio:
i changed and put the file back to /dev/block, and after normal reboot it seems to be the same, but after rebooting into fastboot don't change, so i think that it's only fastboot that change files... maybe if we can flash hboot without entering in fastboot it will pass security :confused:

EDIT: can't do the same with mmcblk0p9... don't want to overwrite... i think it's more protected

EDIT2: i did it.. i overwrote the mmcblk0p9 but after normal reboot it become normal :(
[HTC One X] arabmed:
how ?

EDIT2: i did it.. i overwrote the mmcblk0p9 but after normal reboot it become normal :([/QUOTE]

how you overwrote the mmcblk0p9
[HTC One X] glukosio:
adb shell rm /dev/block/mmcblk0p9
adb shell dd if=/sdcard/mmcblk0p9 of=/dev/block/mmcblk0p9

EDIT: tried to set permission with chmod 444 but doesn't work :(
[HTC One X] HebeGuess:
Nope, they said is not for T-version(T mobile?).

And the attachment is just nessasary adb files.

---------- Post added at 05:23 AM ---------- Previous post was at 04:55 AM ----------

http://www.ug7.net/phone/View/32/685.htm

the post doen't mentions anything about s-off but only modifying CID for unlocked One V.

HERE is my streamlined and resorted translations based on my understanding:

1、'adb shell' follow by 'su', then 'dd if=/dev/block/mmcblk0p21 of=/sdcard/mmcblk0p21'; the partition should be duplicated on your sd.

2、go to the sd path and look for 'mmcblk0p4' file, open in hexeditor change 'HTC__E11' to '11111111' (this original CID should differ on devices).

3、Enter 'fastboot reboot-bootloader', and go into hboot > fastboot usb

4、Enter 'fastboot oem writecid 11111111'

5、Enter 'fastboot reboot-bootloader'

6、Enter' fastboot getvar cid' to confirm your CID was '11111111'

7、Back to charging mode then key in 'dd if=/sdcard/mmcblk0p21 of=/dev/block/mmcblk0p21', then 'fastboot reboot bootloader'

8、Then go into fastboot and check wether your CID is '11111111'

Hell, I think they just simply cut and paste the artitle somewhere, cause is can be seen on elsewhere too.. and for this link, the paragraph, sentences, steps just looks a-like meesed together..
[HTC One X] Thunder07:
That's a bit different it's for a different phone aswell we need the one for xda.cn

Because these simple steps are useless in our phone

Sent from my HTC One X
[HTC One X] HebeGuess:
While the method above, i can seen they apply on One S too..

And from other sources i saw, they just push back the file 'mmcblk0p4' right after editing it..

Pretty sure the webpages is cut and pasted stuff, and mess-up the steps too.
[HTC One X] mattman83:
It looks like the same instructions used on ATT HOX, which should also work (or at least be similar) for the One S. But it's totally useless for us.

M.
[HTC One X] Rusty!:
That 'guide' is just a mash up of other phones :D
[HTC One X] glukosio:
we don't have mmcblk0p21, the last one is p20 (in mine hox)
[HTC One X] Alex240188:
may aswell stop wasting your time looking at superCID guys, its not going to work on tegra 3 this way

open up root explorer

navigate to /dev/block/platform/sdhci-tegra.3/by-name

here you can see the 3 letter assignment for each mmcblk

mmcblk0p1 - WLN

mmcblk0p2 - WDM etc...

now go and grab yourself a few seconds of mmcblk0 (dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0)

after a few seconds hit ctrl+c

now pull the small segment of mmcblk0 from your sdcard and hex it

straight away you can see ordering of partitions in the 3letter format

BCT - (likely HW information)

PT. - (?)

EBT - (eboot?)

DIA - (probably diagnostics)

BIF - (?)

GP1 - (?)

WLN - (mmcblk0p1)

WDM - (mmcblk0p2)

as you can see there are 6 partitions completely hiddent in android but they are there and as such is where you are going to find CID

EDIT - HTC-BOARD-INFO!@ž...HTC__001XXXXXXXXXXXXXXX.....

found at 00A00000 - 00A00020 (where XXXXXX is my IMEI)

mmcblk0p1 doesnt start until 00E00000 so well before the first partition that we can access
[HTC One X] arabmed:
i fond this

see (htc)

adb shell

su

cat proc/partitions

major minor #blocks name

7 0 40572 loop0

179 0 30535680 mmcblk0

179 1 6144 mmcblk0p1

179 2 2048 mmcblk0p2

179 3 6144 mmcblk0p3

179 4 8192 mmcblk0p4

179 5 8192 mmcblk0p5

179 6 16384 mmcblk0p6

179 7 16384 mmcblk0p7

179 8 16384 mmcblk0p8

179 9 4096 mmcblk0p9

179 10 4096 mmcblk0p10

179 11 28672 mmcblk0p11

179 12 1310720 mmcblk0p12

179 13 327680 mmcblk0p13

179 14 26476544 mmcblk0p14

179 15 2248704 mmcblk0p15

179 16 2048 mmcblk0p16

179 17 2048 mmcblk0p17

179 18 6144 mmcblk0p18

179 19 22528 mmcblk0p19

179 20 2048 mmcblk0p20

254 0 40572 dm-0

and this (htc)

cat proc/emmc

dev: size erasesize name

mmcblk0p5: 00800000 00001000 "recovery"

mmcblk0p4: 00800000 00001000 "boot"

mmcblk0p12: 50000000 00001000 "system"

mmcblk0p13: 14000000 00001000 "cache"

mmcblk0p17: 00200000 00001000 "misc"

mmcblk0p1: 00600000 00001000 "wlan"

mmcblk0p2: 00200000 00001000 "WDM"

mmcblk0p20: 00200000 00001000 "pdata"

mmcblk0p3: 00600000 00001000 "radiocab"

mmcblk0p14: 650000000 00001000 "internalsd"

mmcblk0p15: 89400000 00001000 "userdata"

mmcblk0p19: 01600000 00001000 "devlog"

mmcblk0p16: 00200000 00001000 "extra"

this not from htc from (lg )

1.

/etc # cd /

2.

~ # mount /dev/block/

3.

loop0 mmcblk0boot0

4.

loop1 mmcblk0boot1
[HTC One X] Alex240188:
im aware you can check them like this but what im saying is that the partition that your cid is on, is not available in any of the mmcblk partitions

except for 0 which is your entire nand and impractical to remove & reflash (actually if you remove it you probably wont be able to reflash without jtag)
[HTC One X] Thunder07:
And that's why blubbers made partition 26 you map hidden nand section what ofc can't be written to

Sent from my HTC One X
[HTC One X] arabmed:
its befor mmcblk0p1

in lg phone its like this mmcblk0boot0 and mmcblk0boot1

in htc one x theris 2 particion

loop0 is 40 mega bayt

dm-0 is 40 mega bayt
[HTC One X] Thunder07:
http://xdaforums.com/showpost.php?p=25788378&postcount=1295
[HTC One X] dezborders:
I posted this exact same information 2 months ago and editing mmcblk0 (the entire nand memory) was discounted as not possible by the main devs. Also as has been said, edits to most of these partitions revert to original at next reboot. I think this entire area of discussion is a dead end.
[HTC One X] Jhinta:
I have seen that boot0 when booting terminal native its there.

Verstuurd van mijn HTC One X met Tapatalk
[HTC One X] WIIstpM:
Hello everybody I created a thread about my bro's HOX which seems dead (no LED no boot) and someone told me to check this thread... because:

When I connect the HOX on the PC it started to install the drivers for "APX" but always fails... He/she told me to check this thread where someone may hopefully help me... here'sy thread

http://xdaforums.com/showthread.php?t=1812615
[HTC One X] Thunder07:
see if you can convice show-p you have apx in irc

and if he can help...

but if the phone is undamaged and you have the latest recovery it should recharge...

however if he doesnt you and you have another HOX which you can open swap batteries and charge

Edit: he's not online now but wait is all what you can do
[HTC One X] lordlegion1985:
Phone also stuck in APX mode

Hi just thought i would update here that I also have a phone stuck in APX mode this is what as happened so far.

Phone was working fine until it randomly freezed performed soft reset and the phone didnt recover black screen no charging light nothing what so ever I left the phone plugged into my PC overnight and still nothing.

So I opened up the phone and phsyically unplugged the battery and left the phone for an hour plugged battery back in and stull nothing exect the phone will now be detected via my PC (Device manager, APX etc)

I have managed to get the phone to start charigng (red light) twice by simply reseating the battery and plugging in USB cable took around 10 attempts of doing this to get it to charge however both times i was able to turn the phone on and it worked fine but again once i turned the device off it would again be stuck in APX mode.

I dont have any damange to he phone that would of caused the phone to stop working.

My phone is rooted and running a custom recovery open to any suggestions or if anyone would like me to play around with it let me know.

Ive got another HOX on order so im not that botherd if this one ends up being permanantly damaged.
[HTC One X] arabmed:
see this

http://androidroot.mobi/t3_nvflash/comment-page-2/#comments
[HTC One X] angusc:
Great find!

Sent witH desire from One X
[HTC One X] boe323:
Seems to me that everyones given up, we wont be getting s-off anytime soon.
[HTC One X] Adrianiii:
+1
[HTC One X] Genkville:
It's a shame. Well hey ho!
[HTC One X] mattman83:
Seems to me like the devs doing the real work in here don't post any more because of inane posts saying it isn't happening any more, or that we should try "X" (which has been discussed half a dozen times and shot down half a dozen times).

Really, given the state of this thread, why would anyone post anything constructive in here any more?

M.
[HTC One X] nicu96:
i found some website on the net chencen2000.blogspot.ch/2011/04/flash-nvidia-tegra-apx-device.html?m=1

i know that the device he uses has a tegra 2 but couldn't it be that the apx mode works similar for the HOX?

i know there isn't a /proc/naz10_diag/force_recovery file present on the HOX and i didn't found something similar with grep in /proc but it also could be somewhere else...

it's just a thoght and nothing more it could be impossible because of tegra 3 or whatever i don't know...
[HTC One X] theDroidfanatic:
Not trying to be rude or anything, but since we got to know that Xmoo and football have S- OFF due to Diag files they cannot provide (Since someone could lose his job), have we gotten anywhere further towards achieving S OFF? Thanks.
[HTC One X] techmatlock:
Nope. We don't have a team working on exploiting the phone.
[HTC One X] orb3000:
.

Comments like this are not helping anyone here all the effort from the Devs at least need to have our total trust and support please avoid another post like this one.

And to al please stay on topic!
[HTC One X] in_deed:
Hard to stay on topic when you really don't see any real development taking place towards S-Off.

The devs have their S-Off and they are content with that and as far as I understand, they won't provide the diag file since it'll jeopardise their ''source/s''. I'm happy for them :)

Rest of us (hundreds/thousands/tens of thousands/more ?), well... tough luck.

I'm moving on and getting the bootloader unlocked via HTC itself. Not happy, but no choice either.

A big middle finger to HTC nevertheless. Maybe it's got a lot to learn if it needs to survive, starting with working with the masses, not against them.

/Rant over.
[HTC One X] jacho6380:
Exactly, it's sad .....
[HTC One X] VIIRU§:
Sprint 4G LTE got S-off via lazypanda. Maybe it could help us. They had a stock HTC Rom with root and removed some HTC stuff. It's in their original development section
[HTC One X] KamikaZeeFu:
It's a different chipset (qualcomm) so sadly no use.

helpful post is helpful
[HTC One X] marleyb:
true, wish I had wait a lil longer before buying the HOX, it;s catching dust at home while my primary phone is my old desire HD. Guess I'll gonna put it on e-bay. Development while keeping warranty is dead street on the HOX
[HTC One X] ZeDestructor:
HTC seems to be pretty cool about htcdev unlocks and warranty. a couple of users have sent in their unlocked devices and HTC/Carrier took care of them, no questions asked. Please read some more.
[HTC One X] godutch:
check here, overal HTC in the netherlands seems to be more relaxed than the uk

http://gathering.tweakers.net/forum/list_messages/1498471/0
[HTC One X] marleyb:
Yeah read all about it, but rather not gonna gamble how bad the weekend was, of the engineer who got your phone on his desk on monday morning ;) HTC statement is legal clear to unlocking:good:
[HTC One X] Rusty!:
I'm also wary of unlocking mine at the moment, since it's not long back from repair. To be honest I'm finding it pretty damn good as a stock device anyway, so I'm not fretting yet.
[HTC One X] shiningarmor:
same stuff in malaysia

walk into htc centre

CS : hi how can i help u

me : i think my phone has problem. bla bla bla..

CS : oh is it? can demo let me see?

me : *demos:

CS : hmm ok, come bak in 2 weeks.

2 weeks later,

CS : here u go! all patched up and good to go!

no problems ever since.
[HTC One X] theDroidfanatic:
Oh :(

---------- Post added at 04:16 PM ---------- Previous post was at 04:16 PM ----------

Dude, he was trying to help, come on :P
[HTC One X] Thunder07:
i've never gone through an OTA update so i dont know the exact process... if someone would care to eliberate

however i do know that the original recovery is required to be able to flash it,

my best guess because the recovery does the flashing,

know i know that CWM cant do it (just like our Android OS cant) and i was thinking why??

so i did a bit of research and i found that CWM is made up of a ramdisk & zimage,

now the question is, is original recovery made up just the same or was CWM built differently,

because if they are the same surely our answer could be there...

while we dont have full access to emmc the recovery does and is able to flash even hboot,

so the answer could be in the original recovery zimage, no??

well i tried the normal way to unpack it,

./unpackbootimg recovery_signed.img
BOARD_KERNEL_CMDLINE U▒£9þ▀║Æ├☻øÞÉtÒYÊı,=⌂O#f@dJ►║í│üá$♂¯OÞ~diþ:Ä«·├♀¸Vo÷W♥zH☼▀♠ìÏA|qV↨1Á▲þ¡hß■-▬e0£÷ñ×ì▄▒ê ñ_↔§#6£A§'SÙ
Ì2╬‼¼═■8♫┘¸♦o*¸▓ó↕Q«u╬☻*▲RD$D~Ö6ôô║←$7yfïf☺z¸¶LX-Å|∟Í×4ï7AXÓÂôJ2E PóÉÁ¨┐½←½SX▀↨f|®▼ø►É*TÃANDROID!┤K>
BOARD_KERNEL_BASE f782cf76
PAGE_SIZE -887585110
Error: wrong pagesize: -887585110

with no luck... while this is disappointment

is at least shows that the recovery has a kernel "BOARD_KERNEL_CMDLINE" as it has a kernel cmdline.

now how to extract the zimage???
[HTC One X] jonhyxda:
Maybe this helps:

http://xdaforums.com/showthread.php?t=777380
[HTC One X] Thunder07:
Thanks for the try but

The Title says "How to unpack/repack initramfs in zImage"

Step 1. Extract cpio'ed initramfs file from zImage

what i need is the zImage itself
[HTC One X] godutch:
flashing happens in fastboot not in recovery, or well there seem to be 2 parts maybe kernel and hboot are only flashed in fastboot and then the rom.zip part in the recovery
[HTC One X] Alex240188:
Recovery is capable of flashing new Hboot etc. As that is what we used to do on the old nexus one but the protection on this phone will not allow us to do that
[HTC One X] Thunder07:
And the original recovery is still able to,

As it's how OTA firmware.zip is flashed....

Unless im wrong the recovery itself does the flash and doesn't require fastboot.....

As far as I'm concerned fastboot is only accessible through the pc anyway.

Unlike what was said.

what gives the recovery that special permission, it either the ramdisk or zimage, the zimage being the most likely

If we can extract them we could test that theory.

Sent from my HTC One X
[HTC One X] Rusty!:
It's the update-binary that does that stuff, what gives the recovery 'permission' is the digital signatures.
[HTC One X] Thunder07:
Not true because that means we can use CWM to flash them just the same,

Because the file will be signed either way.

Sent from my HTC One X
[HTC One X] Rusty!:
Not quite, stock recovery uses things signed with release keys, CWM uses things signed with test keys. Stock .zips can only be installed via CWM with the signature checks disabled.