yashsingh1/xdaforums huggingface dataset:
[HTC One S] amokkx:
C:\Program Files\Android\android-sdk\platform-tools>adb shell
shell@android:/ $ dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for read: Permission denied
1|shell@android:/ $ su
su
1|shell@android:/ $ dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for read: Permission denied

anyone knows why i cant push mmcblk0p4 to the sdcard? :o

I even updated the SDK, still the same.
[HTC One S] Darknites:
Do it on the phone.
[HTC One S] d0nat0:
just completed this on hboot 1.14 running virtuous ville. no issues.
[HTC One S] beni8978:
There is one guy that has supercid11111111 on a S3 device,and he bought the device so.

Can he help somehow to make supercid available for all S3 users?

Sent from a HTC
[HTC One S] beni8978:
Anyone?

Sent from a HTC
[HTC One S] dc211:
running cm10.1 right? You need to go to developer settings and allow root from adb
[HTC One S] syntropic:
Are you suggesting now we should do it all on the phone (although I can't figure out how you would mod the partition from the phone...but maybe)?? Or do the hex editing on the PC, copy it to SD, and then use shell to dd it to system?

And I figured out where the settings were (the stricken portion below).... wow, it has been a long time since I have gotten my hands dirty!

And Darknites (or someone)...I am having ADB connect problems, and I just wanted to confirm... should USB storage be turned on? or kept off?

Also... it has been awhile since I have had to fire up ADB... I want to confirm fastboot, debugging. and other settings on BB8, but I cannot seem to find any developer settings... since I don't see them, I presume the OS has changed the method of access to them. I see certain options in notifications, besides fastboot, where is "allow mock locations":, etc.? Notifications offers me to turn on USB storage...which I have used in the past if I wanted to copy to the SDCard, but I am bewildered as to location of other typical developer settings.

Could someone let me know where Android hides them now?

Thanks!
[HTC One S] syntropic:
OK....

My adb connection problems are due to drivers. I have not used adb in awhile and maybe the original drivers became corrupt or I uninstalled them inadvertanly.

Anyway, I have installed HTC Sync. And HTC Sync manager starts when I plug my phone into the USB --> PC.

I realize that this may not necessarily mean the drivers are installed correctly, so I was thinking about uninstalling and re-installing HTC Sync.

But before I do, I just wanted to inquire whether there is package with just the drivers? I don't know why I need to install a 50MB piece of software I have no intention of ever using. HTC is so annoying sometimes.

I will download HTC sync, but if someone knows how to extract the driver files (which I can see in Program Files (x86)/HTC/HTC Driver), install them, and uninstall HTC sync, PLEASE let me know.
[HTC One S] Darknites:
I did everything but the hexing on the phone.

---------- Post added at 05:08 AM ---------- Previous post was at 05:07 AM ----------

That wasn't out when I SuperCID and think I was on a sense rom at the time.

---------- Post added at 05:10 AM ---------- Previous post was at 05:08 AM ----------

The All-In-One Toolkit just has the drivers.
[HTC One S] evol4g:
wow... i went to do this and i already had super cid.... weird.. lol
[HTC One S] striped121:
Guys. Do I need to be on a stock RUU for this? as i'm getting..... " cannot open for read: Permission denied " when I try to dump the partition?

EDIT:::: I've just checked and my CID is already ... INFOcid: 1111111

Does this mean I can S-OFF now without a problem?
[HTC One S] ultimul:
are you rooted? permission denied looks like you're not rooted, or did not get root from shell

if you're already super cid, you can go for s-off
[HTC One S] striped121:
Im rooted and running jellybam.

I tried to s-off but i get no model id just a blank space where it should be. anyway i continued with PJ4010000-OneS.zip.

All the steps went fine apart from theses commands:-

adb shell chmod 744 /data/local/tmp/soffbin3

adb shell su -c "/data/local/tmp/soffbin3

After each of these commands i got a blank space again ( no text like after 1st command ) so i rebooted anyway just to see but im still s-on? Thanks for the reply.
[HTC One S] ultimul:
there is no output to display from those commands, just the prompt

I guess you had some errors before, I just did the whole thing acquiring super cid included, and it works just fine,
[HTC One S] striped121:
But i get no return information when i: adb shell getprop ro.aa.modelid.

What rom are you on? Could the rom im on be the reason maybe?
[HTC One S] droidkevlar:
You wont get any return info with that command from what I rem. When I was testing the s-off, jcase had me do that command and it returned nothing. He said it was fine and I went fwd and got soff with no issues.
[HTC One S] striped121:
Ahh ok thanks for clearing that up for me ill try it from a sense rom tomorrow:p
[HTC One S] ultimul:
changing rom is not gonna do something;

you're working at shell level, not UI level;

try again, type everything like in those lines and you'll have it; be sure you have all it needs: unlocked, root, supercid and it should work
[HTC One S] striped121:
im getting this error when ii flash the zip....

FAILED (remote: 99 unknown fail)

edit: i tried again and its work. thanks a million dude for you help:)
[HTC One S] Buickguy:
I have done the Supercid and S-off... My boot loader appears to be unlocked still, I have not used my new unlock code from HTCdev. The original link for the SuperCID mod, from from the One X forum, http://xdaforums.com/showthread.php?p=26516911#post26516911 shows unlocking the bootloader again as step #12... Is it necessary to do the Unlock again??

Like I said, my boot loader shows as unlocked still (along with CID=1111111, and S-Off)
[HTC One S] slainbybeats:
AW: Super cid: 11111111

No it isn't.
[HTC One S] dashivang:
I followed everything perfectly and this is what happened

As you can see everything in cmd goes well, no errors but in the end i end up with the same GLOBA001 cid

which mean the problem is in my hex editing

but

everything appears how it should be

Why didnt my cid change?
[HTC One S] ultimul:
did you reboot your phone?
[HTC One S] dashivang:
I did, i just rebooted to check again and its still GLOBA001

I went to my phones SD card and found 2 files:

mmcblk0p4MOD which i reopened with HxD to see that it had 11111111 cid

and

mmcblk0p4 which i reopened with HxD to see that it had GLOBA001 cid

should i switch their file names so the original has 11111111 and the MOD had GLOBA001?
[HTC One S] ryanshew:
No, don't switch them

HTC_One_S | Root_Box | Bubba_Kernel_2.8b | S-OFF
[HTC One S] dashivang:
re-did the entire process, same results globa001
[HTC One S] Crono88:
I've same problem...

dashivang, have you mtp connection only?
[HTC One S] skinzy98:
So I've rootwd my mothers phone and I used the all in one toolkit to do it. I'm trying to get s-off and when I type in su it says such not found what am I doing wrong?
[HTC One S] dashivang:
im a noob in all of this

i dont know what mtp connection is

i have it plugged in with debugging enabled
[HTC One S] yuan_1202:
Hboot 2.15 cid o2___001

Followed the steps in the [UNLOCK] AT&T Bootloader Unlock Through HTC-Dev post

But just no success. Gone through it so many time exactlly as instructed. but kept reading the same O2___001.

Really do not understand.

I read somewhere about HTC managed to prevent changing CID after Feb?

But I also read some ppl with HBOOT 2.15 succeeded.

Any help would be much appreciated!!!
[HTC One S] Crono88:
same problem...i've also hboot 2.15 and cid TIM...
[HTC One S] Kizi_PL:
Odp: Super cid: 11111111

Same for me hboot 2.15

Wysłane z mojego HTC One S za pomocą Tapatalk 2
[HTC One S] Crono88:
how to do?
[HTC One S] yuan_1202:
I hate HTC......
[HTC One S] slainbybeats:
AW: Super cid: 11111111

Prevent Cid changes? How did they do that? ^^ I guess I am not affected as I already got S Off, right? If I can't change anymore as well, I am stuck on scid. Not funny xD
[HTC One S] real187:
I was aready on jb hboot before i did this.

Stille worked 4 me. That HTC preventid cid change is not true

Verstuurd van mijn One S met Tapatalk
[HTC One S] yuan_1202:
But the fact is the procedure just doesn't work for me.

Can't think of anything I have done wrong.
[HTC One S] Crono88:
and you are not alone
[HTC One S] CuzCrostyPwns:
Yes! It worked for me. thanks a lot of sharing this
[HTC One S] Twist79:
Worked for two HTC__102 HTC one S without any problems.

Build Date Dec. 2012
[HTC One S] PUTALE:
question, now that I have S-OFF and SCID and unlocked. Can I run TMo USA's RUU on the phone to recover to the stock? Or I must change the SCID back to the TMo before I can flash the RUU? DO i need to relock it, or anything else I need to do?
[HTC One S] scotty1223:
from the lock status thread:

hope that helps :)

---------- Post added at 05:44 PM ---------- Previous post was at 05:30 PM ----------

guys,looks like JB firmware is now write protecting mmcblk0p4 on s on phones :mad: we need to start looking for some sort of work around(maybe similar to the original DNA method). since we have htcdev unlock for root,trashing a different partition and reinumerating them may work.

original DNA superCID method: http://www.androidpolice.com/2012/11/24/exclusive-how-to-unlock-the-droid-dnas-bootloader/

revised DNA method: http://xdaforums.com/showthread.php?t=2109862

anyone want to dig into the possibilities of either?

i venture to guess that you were allready s off,or you somehow had only the hboot installed,and not the entire new set of firmware.

this is going to become a bigger prollem as more folks OTA to JB prior to trying to root.
[HTC One S] Crono88:
Who try?
[HTC One S] wheeliemonster:
OK guys. Just thought I'd share this with you.

I sent my phone back to HTC to repair the helicoptering issue and before I did I had to do the following (NOT NECESSARILY IN THIS ORDER!)

Return bootsplash image to stock

Return HBOOT to stock (with warning - I had flashed a modded HBOOT without the red text)

Return SuperCID to normal

Return ROM to stock JB

Re-lock bootloader (I reset it to LOCKED, not RE-LOCKED)

Return to S-ON from S-OFF

I did have HBOOT 1.13, but when I returned everything to stock I put HBOOT 2.15 on.

I completely RUUed with the latest 3.16 software.

So, everything was back to normal before I sent it off for repair but with the latest firmware on...

It's now come back and I have managed to:

Unlock Bootloader

Flash Custom Recovery

Root

SuperCID

S-OFF

All without problems... I certainly don't see any write-protection on mmcblk0p4...

Not saying that this is definitely the case - just sharing my experience!
[HTC One S] abrarabbu:
I think it is kind of write protected.

I accepted OTA.

Now when i try to S-off every thing goes well but i dont see any change.

Help/
[HTC One S] scotty1223:
Not sure if something can be kind of write protected. ;) if there is no write protection,there must be something prohibiting some folks from having success.

So you ran the 3.16 ruu,and it successfully updated all partitions?

Perhaps those having trouble should try relock,run the same ruu,then reunlock,and try again.
[HTC One S] tominozh:
I did OTA update (3.16). Got root after that, supercid, and S-Off without any issues. If it works for my phone should work for every phone.

Edit. The original boot.IMG had some sort of write protection, that you couldn't permanently uninstall system apps when booted to android. (They would come back after reboot) Not sure if that has anything to do with that.
[HTC One S] scotty1223:
there has got to be some factor,as some folks are indeed having troubles. maybe after a certain build date? maybe if you had superCIDed prior? i have no idea. but there are several cases ive read about/tried to help on where everything looks 100% correct but the CID just doesnt change :eek:

maybe a fastboot getvar all from the folks that have done it from 3.16 and those unable would turn up something?
[HTC One S] Darknites:
I know one thing for sure, it not having SuperCID pior because I had that for about 6 months and everything is fine for me.
[HTC One S] wheeliemonster:
I was on a CM10.1 based ROM before needing to return to stock, so I ran the 3.16 RUU, I didn't do an OTA.

But as I said above, I'm happily back to S-OFF, SuperCID, etc. even after that. Will run a fastboot getvar all very shortly and update my post...

EDIT: here it is:

(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: SH23ZWXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4091mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
[HTC One S] scotty1223:
i dont quite understand your answer. had you unlocked/superCIDed before? then went back to stock CID,updated to 3.16.401.8,then superCIDed again?

or had you NEVER unlocked or supercided prior to doing it now?

come on guys,as much detail as possible is needed for us to figure this out for the folks its not working for.
[HTC One S] Darknites:
I SuperCID in September or there about to flash the 2.31 RUU. I did Hboot downgrade when that come out. It stayed like that in till S-Off come out and when I went to test BB8 build I done and it didn't boot and the only thing that worked was bootloader:confused::confused: so used the same RUU I used before and then S-Off and is all fine.
[HTC One S] xander1993:
is there ONE S C2 (s3 variant) s-off?
[HTC One S] Darknites:
Nope because you can't SuperCID.
[HTC One S] taxtax:
I tried to supercid my TmobileDE Phone, after the 3.16.111.7 OTA and failed.

I restored my stock ICS 4.0.4 nandroid, tried again and failed again.

I tried also with the generic 4.0.4 Europe kernel without success.

The same with the Viper ROM.

Here are my variables:

(bootloader) version: 0.5

(bootloader) version-bootloader: 2.15.0000

(bootloader) version-baseband: 1.11.50.05.28

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: HT26BWXXXXXX

(bootloader) imei: 3599XXXXXXXXXXX

(bootloader) product: vle

(bootloader) platform: HBOOT-8960

(bootloader) modelid: PJ4010000

(bootloader) cidnum: T-MOB101

(bootloader) battery-status: good

(bootloader) battery-voltage: 3778mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-64bedd38

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0
[HTC One S] tominozh:
I was rooted, then I took 3.16 ota in December. Then when we got Facepalm s-off I changed to supercid and got s-off. Then change my cid back to HTC__001.
[HTC One S] taxtax:
I take the last OTA (3.16.111.7of Tmobile DE) in 28 February. This means after the S-Off Released. So maybe this is the reason that I can't Supercid. Maybe HTC has locked something.

The previous Tmobile DE firmware (3.16.111.5) released in 1 February. Is there anybody with this firmware that has tried to Supercid his phone?
[HTC One S] tominozh:
Oh, that's different then. I updated to jb on 25.12.2012. Its this one

http://xdaforums.com/showthread.php?t=2063848

That updated my hboot to 2.15.
[HTC One S] CazeW:
I bought a new unbranded One S a week ago, updated all OTAs (3.16.401.8 being the latest), unlocked bootloader, flashed recovery, root, SuperCID, S-Off in that order with the toolkit and didn't have any problems what so ever.
[HTC One S] Crono88:
the case must be another
[HTC One S] taxtax:
Finally I realized that the mmcblk0p4 partition and the CID temporarily changes.

And with fast reboot (from settings) the modified mmcblk0p4 remains.

But when reboot normally, the bootloader restores the original mmcblk0p4 partition.
[HTC One S] yuan_1202:
HTC is gay
[HTC One S] Sneakyghost:
AW: Super cid: 11111111

that's really odd. Are you the only one with this weird behavior?

I've never encountered a self-resetting CID nor have I read about that before. Sounds like some crap but then again your posts sound quite reasonable too :p

I'd be interested to see the outcome of other people testing that with other 3.16 variants. Maybe T-Mobile requested that lock to keep users with them and their stuff?

Sent from Viper 2.2
[HTC One S] abrarabbu:
Even I have same problem.

All the process goes good and when i reboot, i get the same CID back.

Its one s with bell now UNLOCKED

Tried many times.

Any help will be appreciated. Thanks

I have a question.. Do we have to change CID to 11111111 or to HTC__001???
[HTC One S] taxtax:
Additionaly every time I copy the modified mmcblk0p4 and the phone reboots:

-in 4.0.4 version shows the red message: This is a build for developement purposes only....

-in 4.1.1 version doesn't shows the above, boots, and popups an error report message:

The phone has just recovered from an abnormal.... (in translation)

Both of them with the 2.15 bootloader which is exactly the same with the general european 2.15.
[HTC One S] scotty1223:
that makes sense. when you reboot with "fastboot" checked,the phone just goes to sleep,doesnt really turn off,so the "wake up" process is likely different than the real "boot" process. the important thing,however,is to get it to read 11111111 long enuff to try and read the update file in fastboot in order to get facepalm to work ;)

i think in both cases the bootloader realizes that something has been modified. in ics software,it just trows up the warning on the splash. in jb it gives the abnormal reset error,and in both cases,restores the originaly mmcblk0p4 from the emmc

wow thats fantastic... really helpful. thanks :rolleyes:

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

write protection is nothing new. its been in place around vital parts like the bootloader and radios for quite some time- thats why we fight to achieve s-off. so we have no limits or write protections to deal with. the "self resetting CID" is simply the write protection restoring the origial memory block. newer phones are further complicating things by "enumerating partitions" i.e.,one checks the next,checks the next,etc. as booted so any disruption in the chain can cause the device to reset the corrupt block,not boot,or hard brick.

this write protection has nothing to do with t mobile. the bootloader unlock via htcdev is still available to us,wich is the only thing a carrier could request. write protection and enumerationg partitions and complex boot sequences and signitures are htc;s way of trying to prevent us from having full access.

my only guess at this point is that some 2.15 hboots are employing the write protect,while some arent(maybe a change as firmwares are released). it really doesnt make sense... unless the folks that have gotten away with it have some other variable we dont know(like being s off :eek:)
[HTC One S] Sneakyghost:
Yeah i am aware of the first part of your post. I was solely referring to what you wrote in the quoted part.

My thought was, that T-Mobile Updates have gotten a particular difference in them that does this check while the WWE updates have not.

I have three WWE One S and one Special Edition.

None do that. All keep the altered p4.

Then i have not read about this behavior anywhere else but here.

This does not state that i don't believe it. I am just very interested and am following this discussion.
[HTC One S] taxtax:
A picture is a thousand words

The first screen capture, shows the files-partitions before reboot (shorted with time). Almost all partitions have the date-time of phone boot.

The mmcblk0p4 is modified and has the newer time.

The second screen capture, shows the files-partitions after reboot. The date-time of them is updated with the date-time of the new reboot.

The original mmcblk0p4 has already restored.
[HTC One S] scotty1223:
not everyone having the prollem is on t mobile,its varied. some are on t mobile,some are on other carriers.
[HTC One S] Crono88:
I've tim carrier (italian) and cid "locked"
[HTC One S] dannydro:
error [159] image error

ruu 3.16

i know i have supercid and relocked bootloader. used a tmo ruu no problem to downgrade my hboot. any pointers ?
[HTC One S] scotty1223:
The newer ruus are encrypted to keep us from unpacking them and shuffling images around. The older hboots are unable to unpack the new ruu. You'll need hboot 2.15 in place to unpack and install the 3.16 ruu.
[HTC One S] Phantom Pt. II:
Edit: figured it out. Thanks for this!
[HTC One S] scotty1223:
if you need it(wasnt near my PC yesterday):

http://www.mediafire.com/download.php?rd7oz1cixvo84b6
[HTC One S] Phantom Pt. II:
Can I still run any RUU after getting super cid?
[HTC One S] scotty1223:
yes
[HTC One S] Aktivehate:
Easy method this, only the offset doesn't match for my case.
[HTC One S] scotty1223:
if your making a general statement... ok.

if you want any help or advice,were gonna need more info ;)
[HTC One S] Tim2246:
can you help?

Ok so i spent literately 36 hours reading and trying and couldn't achieve what i wanted to.

So i started out with a factory 2.35.12 710 the newest htc one s all updates done.

Hboot1.4

I got sick of waiting for the official jb release so I said fck this and did s-off root the usual routine with no issues and set my cid to HTC__001.

reloLocked the boot loader and tried to run the RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4

and no matter what i tried.

locking the boot loader.

unlocking the boot loader i couldn't run the ruu.

It would mahke it to signature update verify or some **** and failed.

After like I said 36 hours of trolling and trying.

Now i ended up saying screw it and installed the newest trickdroid 9.0 booted up. Then rebooted and flashed the 9.1 update through twrp and of course cleared caches.

rebooted let it load and then rebooted again, and flashed the wifi partitions through twrp.

every thing works great. Cudos Torx!!

But the battery life is uggh, it eats the battery lol.

however the wifi data rate is awesome it flies at a steady 24mbit constant and on hspa+, HSPA, im getting between 7912 to 14683 constant.

Better speeds then on factory 2.35 with the newest ota as of march 2013.

And am happy over all with the rom.

However is this a true Jelly bean rom?

and is there any benefit to use the JB H.boot?

And Also

I cant let it GO!

I need to know why couldnt i flash the above ruu?

I had cid HTC__001 and still do :)

Did i need to flash a different hboot in order to run that ruu?

Also can you shoot me a link or a quick tutorial on how to flash ruu through fast boot versuses running the ruu?

People are saying I do not need to ever run a ruu again now.

I can just unpack the ruu and install through fastboot?

Whats the difference.

what do i need to do?

Thank you all for your help.

Lastly I'm still on

VLE PVT SHIP S-OFF RL

CID-HTC__001

hboot 1.14.0004

radio 1.08ts.50.02.6

OpenDSP-v31.1.0.45.0015

eMMC-boot

Aug 14 2012,18:01:48

Thank you all and again CUDOS TORX.

Nice rom.

NIce work
[HTC One S] scotty1223:
read posts 294 and 296 ;)

to run RUUs from fastboot,use this: