[Samsung Captivate Glide] steadfasterX:
Thats perfect. just wanted to be sure.

Ok some news and they will not satisfying you..

As I use since 10 years now linux based desktops only I first tried the whole nvflash thing with my linux machine but I was not able to get it working first. The reason was not linux but I had trouble even get INTO the apx mode on the samsung device. To figure out what happens and because you using windows too I thought it would be a test to test that in windows.

So I setup a laptop with a windows installed just to find out that my dev device gets into the apx mode but directly disappears..!!

Long story short: At the end I was able to get the apx mode working after 2 days spent on only this one ;)

So what next. I just wanted to start and ... first of all read again. The nvflash procedure was new to me so I need to understand first how and what I can do with it in detail.

When it comes to the communication between the pc and the apx mode it ends up in most times with an error like "Command send failed (usb write failed)".

--> That means this command is not supported without a valid encrypted communication! To have this communication encrypted you need the SBK (Command send failed (usb write failed) which is known by Samsung only so no chance to get further here.

The good: In theory even there is a need for the SBK there is a command working without it: "create" (well I'm technically not be able to confirm that but read on)

This subcommand of the nvflash tool would reinitialize the complete device like repartitioning and so on - hey thats enough for us right?

Ok so the bad now:

The create command needs the following to work correctly => a BCT file, a bootloader, a configuration file

Well the bootloader is normally the fastboot mode on other devices. Our device hasn't this mode available so we would need a bootloader which enables the communication like fastboot would do.

Then it would be easy to fetch the BCT like this:

nvflash (--resume) --bl bootloader.bin --getbct --bct i927.bct --go

(resume may not needed here)

And the config file needed well the structure is like this:

[partition]
name=SOS
id=8
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=recovery.img

The above is for 1 partition only think about doing the whole definitions for all partitions. Easy when you (or someone like me) has a working device in front of.

The whole command which would reinitialize the device would be at the end:

nvflash -bct i927.bct --setbct --configfile desaster_recovery.cfg --create --bl bootloader.bin --odmdata (unsure about the setting here) --go

So:

I have absolutely NO idea how to get a really good working bootloader file which is able to communicate fine

Without the bootloader I can not fetch the BCT which is absolutely required, too

In my tests I used the bootloader provided by [MENTION=5112223]bubor[/MENTION] (http://dualhoki.vim.hu/bubor/dev/bootloader.tar.md5). I extracted it and the resulting bootloader.bin was used in my tests (maybe wrong maybe not).

I also tried other bootloaders from similar device types and even uboot for the S2. all without success.

As long as we cannot get a good bootloader running in nvidia fastboot mode we will stuck here. Or... maybe I understood something wrong and there has to be another way but all I tried end up with this result

Too bad but without any suggestions on how that bootloader thing can be setup correctly - or having a fastboot mode - we cannot fix your device. Sorry. If anyone reads this and know what I'm doing wrong maybe let me know ;)

Some readings:

BCT internals => http://http.download.nvidia.com/tegra-public-appnotes/bct-overview.html

How to get BCT => http://xdaforums.com/showthread.php?t=934023

nvflash internals => http://http.download.nvidia.com/tegra-public-appnotes/flashing-tools.html

APX + SBK + nvflash internals => http://www.androidroot.mobi/pages/the-inner-workings-of-secure-boot-key-and-nvflash/