[T-Mobile myTouch 4G Slide] Blue6IX:
Okay - Here are some things to think about from the Sensation forum:

- Where I posted above about the S-ON tactic:

right after a person tried it, it worked out, then they claimed they were bricked here:

http://xdaforums.com/showpost.php?p=16192660&postcount=661

A little later in the thread the user who got bricked fixed it here:

http://xdaforums.com/showpost.php?p=16194018&postcount=669

So it looks like the command:

fastboot oem writesecureflag 3

...might be a good place to start if not ultimately it.

Our hboots have both the writesecureflag and readsecureflag commands.

If I run the command:

fastboot oem readsecureflag

I get:

(bootloader) secure_flag: 0
OKAY [ 0.000s]
finished. total time: 0.000s

Is this the same zero shown in this command:

fastboot oem checkSbl1

That gives me:

(bootloader) sbl1 signature checking...
(bootloader) TZ_HTC_SVC_VERIFY_BOOTLOADER ret = 0
(bootloader) sbl1 verified successfully
OKAY [ 0.078s]
finished. total time: 0.078s

Are these more clues to lead to the validity of the writesecureflag command?

So does that mean S-OFF is 0 as it seems to be showing?

What about values 1 and 2 - do they exist? (Anything to do with locked/unlocked?)

Can someone S-ON UNLOCKED run the fastboot commands:

fastboot oem readsecureflag

...and:

fastboot oem checkSbl1

And print the output here for us?

Could I also get someone S-ON LOCKED to try those same commands and print the output please?

----

Going back to the first post in the thread where XDA search brought me to the writesecureflag command, we find a goldmine of info, here is the link:

to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on

...and come to find out the person who got bricked and fixed was actually the OP.

The first posting supports the writesecureflag argument as the S-ON trigger.

Notations are pretty clear about returning to stock first - and i'm getting worried about not knowing the difference between an RUU and a PG59IMG.zip file - is there any? What's the distinction?

Also supplies the Sensations version of our PG59IMG.zip file for a custom recovery, which i've already put together for us Here, and another reference to doing supercid like thrice43 mentioned before in this thread.

The fastboot command I gave for writing the CID:

fastboot oem writecid 11111111

...is also given here as well, so it looks like we already know the right way to do that too.

----

Also found this from another Sensation thread:

How to Remove Custom Recovery/Root/Hboot and Keep Stock S-Off/Stock S-ON

Is this:

..and again the importance of a real RUU is in front of us.

Can someone explain what would make an RUU different from our PG59IMG.zip? It seems like they have both of these abilities over at the Sensation forums but a distinction is made between them.

Something about it being an .exe file like I brought up earlier?

This understanding will be vital to us continuing forward - any help anyone can give me on clarifying that would be awesome.

It looks like we can, in fact, find a lot of good info over in the Sensation forum and prevent us from re-inventing the wheel.

I have to run for a few hours, but i'll be back hopefully soon and see where we can take this.

I'm eager to see if S-ON will be possible so I can have a test device for this project.

Edit:

I'm not ignoring you - just got a lot to add, sort it out later! :D

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

..and of course, before I left I just had to push it a little further:

On device 2:

I ran the fastboot command:

fastboot oem readpid

Which returned:

(bootloader) pid: 111
OKAY [ 0.000s]
finished. total time: 0.000s

...and then did something I shouldn't have, which was run a command in fastboot I had no idea what would happen from doing:

fastboot oem gencheckpt

Which printed:

(bootloader) Start Verify: 0
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) setup_tag addr=0x40400100 cmdline add=0x801E59D0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x28500
(bootloader) TAG:hero panel = 0x2940024
(bootloader) TAG:engineerid = 0x1
(bootloader) TAG: PS ID = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is T-MOB010
(bootloader) setting->cid::T-MOB010
(bootloader) serial number: [B]NUMBER REMOVED BY Blue6IX[/B]
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =544
(bootloader) active commandline: poweron_status=1 board_doubleshot.disabl
(bootloader) e_uart3=0 diag.enabled=0 board_doubleshot.debug_uart=0 userd
(bootloader) ata_sel=0 androidboot.emmc=true androidboot.pagesize=2048 sk
(bootloader) uid=0 ddt=20 androidboot.lb=0 androidboot.baseband=11.16.350
(bootloader) 4.20_2 androidboot.cid=T-MOB010 androidboot.batt_poweron=go
(bootloader) od_battery androidboot.carrier=TMUS androidboot.mid=PG591000
(bootloader) 0 androidboot.keycaps=qwerty androidboot.dq=FAIL androidboot
(bootloader) .mode=recovery androidboot.serialno=[B]REMOVED[/B] androidboot
(bootloader) .bootloader=1.45.0013 zygote_oneshot=off msm_watchdog.enable
(bootloader) =1 no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) aARM_Partion[8].name=radio
(bootloader) aARM_Partion[9].name=adsp
(bootloader) aARM_Partion[A].name=radio_config
(bootloader) aARM_Partion[B].name=modem_st1
(bootloader) aARM_Partion[C].name=modem_st2
(bootloader) partition number=13
(bootloader) Valid partition num=13
(bootloader) TZ_HTC_SVC_SET_DDR_MPU ret = 0
(bootloader) smem 50005000 (phy 50005000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_LOG_OPERATOR ret = 0
(bootloader) TZ_HTC_SVC_MEMPROT ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 6381568 (0x616000)
(bootloader) jump_to_kernel: machine_id(3149), tags_addr(0x40400100), ker
(bootloader) nel_addr(0x40408000)
(bootloader) -------------------hboot boot time:686441 msec
FAILED (status read failed (Too many links))
finished. total time: 5.953s

... and it threw me into my recovery, which was cwm 5.0.2.7

You can imagine my panic. Quick search of the command gave me a bit of relief, and I powered off the device. Powered back up and it booted fine, seems to work fine, but I have no SIM card in this device and have no time to check it further right now.

This output may be useful to the cause, though, and some things to note from it:

All the TZ data near the bottom...

What are these:

msm_watchdog.enable=1

zygote_oneshot=off

androidboot.dq=FAIL

...and now i'm really out of time before I could post the rest but the output is there.

Catch you guys later!