Database Develop

[Q] Why is there an *.exe file in the factoryfs.rfs

Hello,
I extracted the factoryfs.rfs file from JPX with MagicIso and noticed that there is a SWD-V300_WiMAX_Setup.exe file under system(maybe system/bin) and an autorun.inf in the same folder. So I wonder why? I thougt the Galaxy S don't have WiMAX? Can I safely delete that file?

Very interesting...
What rom are you on?

Yeah quite interesting. Why an exe is included? Hasn't any expert programmers noticed this?

Why not upload the files here? We can then see what OS this exe file is for, maybe it's not supposed to be there.
Autorun.inf is used in CDs/DVDs in Windows to get them to launch a file when the disc is inserted. I don't know if it is used in Linux or anything else.

Just tested an original rom nothing like that inside .
jje

hidden .iso file in galaxy s XWJS5
I also found the same file using stock XWJS5 (2.2.1).
It's under /system/etc/autorun.iso
The iso file list is as above:
AUTORUN.exe
AUTORUN.INF
SWD-V300_WiMAX_Setup.exe
Samsung had a prototype on the forge with model name "Samsung SWD-V300 Cosmos".
Now what does this have to do with galaxy s ? Probably nothing, but who knows.
BR
PS: File link: www#multiupload#com/6UJHZ4ATNB (replace # with . ) sorry cna't post outside links.

CyberKareca said:
I also found the same file using stock XWJS5 (2.2.1).
It's under /system/etc/autorun.iso
The iso file list is as above:
AUTORUN.exe
AUTORUN.INF
SWD-V300_WiMAX_Setup.exe
Samsung had a prototype on the forge with model name "Samsung SWD-V300 Cosmos".
Now what does this have to do with galaxy s ? Probably nothing, but who knows.
BR
PS: File link: www#multiupload#com/6UJHZ4ATNB (replace # with . ) sorry cna't post outside links.
Click to expand...
Click to collapse
I can confirm the contents of the ISO. I found it in the newest Darky's ROM.
I can't see any reasons for this being in the fs? I want to delete it.

Some details for ya...
Just came across this myself. I was thinking maybe it was something similar to HTC's use of a CD-Rom USB interface, which loads an iso image containing drivers. Which frankly would make sense, seeing as most of us see a CD-Rom drive when plugged in via USB, well us Vibrant guys anyways, not sure about I9000. Out of curiosity I installed it on one of my VM testers. There's really not much there, and it seems somewhat dated. Here ya go.
Found this in Trigger 3.0.1. Also, the .inf lists quite a few files, but I never saw them. The installer extracted out to the following. C7xVX32S.sys, C7xVOIP.inf, an msi installer, and a few directories. The tester was 7 x86 Ultimate.
SWD-300_WiMAX_Drivers / 2ce9a.msi
C7xVX32S.sys details
Code:
Length Of Struc: 03A0h
Length Of Value: 0034h
Type Of Struc: 0000h
Info: VS_VERSION_INFO
Signature: FEEF04BDh
Struc Version: 1.0
File Version: 4.1.5.12
Product Version: 4.1.5.12
File Flags Mask: 0.63
File Flags: DEBUG; PRIVATE BUILD;
File OS: NT (WINDOWS32)
File Type: DRV
File SubType: DRV NETWORK
File Date: 00:00:00 00/00/0000
Struc has Child(ren). Size: 836 bytes.
Child Type: StringFileInfo
Language/Code Page: 1033/1200
CompanyName: Samsung Electronics
FileDescription: Samsung WiBro/mWiMAX USB Device Driver
FileVersion: 4.01.0512.D
InternalName: C7xx VOIP Driver for Windows XP/2000
LegalCopyright: Copyright (c) Samsung. All rights reserved.
OriginalFilename: C7xVverS.sys
ProductName: Samsung WiBro/mWiMAX USB Adapter
ProductVersion: 4.01.0512.D
Child Type: VarFileInfo
Translation: 1033/1200
C7xVOIP.inf dump
Code:
;
; File Name: C7xxVoIP.inf
; Integrated USB Driver installation file for C7xx (WiBro and mWiMAX)
;
; File created on 07/22/2008
;
; Copyright (c) 2007, 2008, 2009 Samsung Electronics
;--------- Version Section ---------------------------------------------------
[Version]
Signature = "$WINDOWS NT$"
Class = Net
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
Provider = %Provider%
DriverVer = 07/17/2009, 4.02.0717
CatalogFile = C7xVCSDK.cat
;--------- DestinationDirs Section -------------------------------------------
[DestinationDirs]
DefaultDestDir = 10
C7xxVoIP_Files_Driver.ntx86 = 12
C7xxVoIP_Files_Driver.ntx86.6.0 = 12
C7xxVoIP_Files_Driver.ntamd64.6.0 = 12
;--------- SourceDiskNames and SourceDiskFiles Section -----------------------
; These sections identify source disks and files for installation.
[SourceDisksNames]
1 = %DiskId1%,,,""
[SourceDisksFiles]
C7xVX32S.sys = 1,.\NT32,
C7xVV32S.sys = 1,.\VT32,
C7xVV64S.sys = 1,.\VT64,
;--------- Manufacturer and Models Sections ----------------------------------
[Manufacturer]
%MfgName% = C7xxVoIP_Mfg, ntx86.6.0, ntamd64.6.0
[C7xxVoIP_Mfg]
; DisplayName Section DeviceId
%WiBro_DeviceDesc% = C7xxVoIP.ntx86, USB\VID_055D&PID_A150&MI_00 ; SWM-S15K
%WiBro_DeviceDesc% = C7xxVoIP.ntx86, USB\Vid_04e8&Pid_6735 ; Download mode PID
[C7xxVoIP_Mfg.ntx86.6.0]
; DisplayName Section DeviceId
%WiBro_DeviceDesc% = C7xxVoIP.ntx86.6.0, USB\VID_055D&PID_A150&MI_00 ; SWM-S15K
%WiBro_DeviceDesc% = C7xxVoIP.ntx86.6.0, USB\Vid_04e8&Pid_6735 ; Download mode PID
[C7xxVoIP_Mfg.ntamd64.6.0]
; DisplayName Section DeviceId
%WiBro_DeviceDesc% = C7xxVoIP.ntamd64.6.0, USB\VID_055D&PID_A150&MI_00 ; SWM-S15K
%WiBro_DeviceDesc% = C7xxVoIP.ntamd64.6.0, USB\Vid_04e8&Pid_6735 ; Download mode PID
; --------- Windows XP 32 -----------------
[C7xxVoIP.ntx86]
Characteristics = 0x84 ; NCF_HAS_UI & NCF_PHYSICAL
BusType = 15 ; PnP bus
CopyFiles = C7xxVoIP_Files_Driver.ntx86
AddReg = C7xxVoIP.reg, C7xxVoIP.params.reg
[C7xxVoIP.ntx86.Services]
AddService = C7xVCSDK, %FLG_ADDREG_NOCLOBBER%, C7xxVoIP_Service.ntx86, C7xxVoIP.EventLog
[C7xxVoIP_Service.ntx86]
DisplayName = %C7xxVoIP_SvcDesc%
ServiceType = %SERVICE_KERNEL_DRIVER%
StartType = %SERVICE_DEMAND_START%
ErrorControl = %SERVICE_ERROR_NORMAL%
ServiceBinary = %12%\C7xVX32S.sys
LoadOrderGroup = NDIS
[C7xxVoIP_Files_Driver.ntx86]
C7xVX32S.sys,,,2
; --------- Windows Vista 32 -----------------
[C7xxVoIP.ntx86.6.0]
Characteristics = 0x84 ; NCF_HAS_UI & NCF_PHYSICAL
BusType = 15 ; PnP bus
CopyFiles = C7xxVoIP_Files_Driver.ntx86.6.0
AddReg = C7xxVoIP.reg, C7xxVoIP.params.reg
[C7xxVoIP.ntx86.6.0.Services]
AddService = C7xVCSDK, %FLG_ADDREG_NOCLOBBER%, C7xxVoIP_Service.ntx86.6.0, C7xxVoIP.EventLog
[C7xxVoIP_Service.ntx86.6.0]
DisplayName = %C7xxVoIP_SvcDesc%
ServiceType = %SERVICE_KERNEL_DRIVER%
StartType = %SERVICE_DEMAND_START%
ErrorControl = %SERVICE_ERROR_NORMAL%
ServiceBinary = %12%\C7xVV32S.sys
LoadOrderGroup = NDIS
[C7xxVoIP_Files_Driver.ntx86.6.0]
C7xVV32S.sys,,,2
; --------- Windows Vista 64 -----------------
[C7xxVoIP.ntamd64.6.0]
Characteristics = 0x84 ; NCF_HAS_UI & NCF_PHYSICAL
BusType = 15 ; PnP bus
CopyFiles = C7xxVoIP_Files_Driver.ntamd64.6.0
AddReg = C7xxVoIP.reg, C7xxVoIP.params.reg
[C7xxVoIP.ntamd64.6.0.Services]
AddService = C7xVCSDK, %FLG_ADDREG_NOCLOBBER%, C7xxVoIP_Service.ntamd64.6.0, C7xxVoIP.EventLog
[C7xxVoIP_Service.ntamd64.6.0]
DisplayName = %C7xxVoIP_SvcDesc%
ServiceType = %SERVICE_KERNEL_DRIVER%
StartType = %SERVICE_DEMAND_START%
ErrorControl = %SERVICE_ERROR_NORMAL%
ServiceBinary = %12%\C7xVV64S.sys
LoadOrderGroup = NDIS
[C7xxVoIP_Files_Driver.ntamd64.6.0]
C7xVV64S.sys,,,2
; --------- Registry keys --------------------
[C7xxVoIP.reg]
HKR, Ndi, Service, 0, "C7xVCSDK"
HKR, NDI\Interfaces, UpperRange, 0, "ndis5"
HKR, NDI\Interfaces, LowerRange, 0, "ethernet"
[C7xxVoIP.EventLog]
AddReg = C7xxVoIP.AddEventLog.reg
[C7xxVoIP.AddEventLog.reg]
HKR, , EventMessageFile, 0x00020000, "%%SystemRoot%%\System32\netevent.dll"
HKR, , TypesSupported, 0x00010001, 7
;-------------------------------------------------------------------------------
; Optional Custom Parameters in the Registry ("Advanced" menu).
[C7xxVoIP.params.reg]
; Statistics interval (debug only)
HKR, NDI\params\StatsInterval, ParamDesc, 0, %ParamStatInt%
HKR, NDI\params\StatsInterval, type, 0, "int"
HKR, NDI\params\StatsInterval, default, 0, "10"
HKR, NDI\params\StatsInterval, optional, 0, "0"
HKR, NDI\params\StatsInterval, min, 0, "0"
HKR, NDI\params\StatsInterval, max, 0, "60"
; Wakeup timeout after S3/S4 states
HKR, NDI\params\WakeupTimeout, ParamDesc, 0, %ParamWakeTout%
HKR, NDI\params\WakeupTimeout, type, 0, "long"
HKR, NDI\params\WakeupTimeout, default, 0, "100000"
HKR, NDI\params\WakeupTimeout, optional, 0, "0"
HKR, NDI\params\WakeupTimeout, min, 0, "100000"
HKR, NDI\params\WakeupTimeout, max, 0, "2000000"
; Device remote wake-up
HKR, NDI\params\RWU, ParamDesc, 0, %ParamRWU%
HKR, NDI\params\RWU, type, 0, "enum"
HKR, NDI\params\RWU, default, 0, "1"
HKR, NDI\params\RWU, optional, 0, "0"
HKR, NDI\params\RWU\enum, "0", 0, %ParamDisable%
HKR, NDI\params\RWU\enum, "1", 0, %ParamEnable%
; No halt on suspend
HKR, NDI\params\NoHalt, ParamDesc, 0, %ParamNHOS%
HKR, NDI\params\NoHalt, type, 0, "enum"
HKR, NDI\params\NoHalt, default, 0, "1"
HKR, NDI\params\NoHalt, optional, 0, "0"
HKR, NDI\params\NoHalt\enum, "0", 0, %ParamNo%
HKR, NDI\params\NoHalt\enum, "1", 0, %ParamYes%
; Linkspeed indication
HKR, NDI\params\Linkspeed, ParamDesc, 0, %ParamSpeed%
HKR, NDI\params\Linkspeed, type, 0, "long"
HKR, NDI\params\Linkspeed, default, 0, "1000000"
HKR, NDI\params\Linkspeed, optional, 0, "0"
HKR, NDI\params\Linkspeed, min, 0, "10000"
HKR, NDI\params\Linkspeed, step, 0, "10000"
HKR, NDI\params\Linkspeed, max, 0, "1000000"
; Maximum send queue depth
HKR, NDI\params\SndQLimit, ParamDesc, 0, %ParamSQL%
HKR, NDI\params\SndQLimit, type, 0, "int"
HKR, NDI\params\SndQLimit, default, 0, "500"
HKR, NDI\params\SndQLimit, optional, 0, "0"
HKR, NDI\params\SndQLimit, min, 0, "100"
HKR, NDI\params\SndQLimit, max, 0, "1500"
; Maximum receive queue depth
HKR, NDI\params\RcvQLimit, ParamDesc, 0, %ParamRQL%
HKR, NDI\params\RcvQLimit, type, 0, "int"
HKR, NDI\params\RcvQLimit, default, 0, "500"
HKR, NDI\params\RcvQLimit, optional, 0, "0"
HKR, NDI\params\RcvQLimit, min, 0, "100"
HKR, NDI\params\RcvQLimit, max, 0, "1500"
; Suspend timeout
HKR, NDI\params\SuspendTimeout, ParamDesc, 0, %ParamSuspend%
HKR, NDI\params\SuspendTimeout, type, 0, "long"
HKR, NDI\params\SuspendTimeout, default, 0, "10000"
HKR, NDI\params\SuspendTimeout, optional, 0, "0"
HKR, NDI\params\SuspendTimeout, min, 0, "1000"
HKR, NDI\params\SuspendTimeout, step, 0, "1000"
HKR, NDI\params\SuspendTimeout, max, 0, "30000"
; Suspend timeout in connected state
HKR, NDI\params\SuspendNetTimeout, ParamDesc, 0, %ParamNetSuspend%
HKR, NDI\params\SuspendNetTimeout, type, 0, "long"
HKR, NDI\params\SuspendNetTimeout, default, 0, "900"
HKR, NDI\params\SuspendNetTimeout, optional, 0, "0"
HKR, NDI\params\SuspendNetTimeout, min, 0, "500"
HKR, NDI\params\SuspendNetTimeout, step, 0, "100"
HKR, NDI\params\SuspendNetTimeout, max, 0, "10000"
;--------- Strings Section ---------------------------------------------------
[Strings]
MfgName = "Samsung Electronics"
Provider = "Samsung Electronics"
C7xxVoIP_SvcDesc = "Samsung CMC7xx CSD VoIP Network Driver"
WiBro_DeviceDesc = "Samsung USB VoIP Adapter"
DeviceClassName = "Class for Network USB devices"
DiskId1 = "CMC7xx CSD VoIP Device Installation Disk #1"
; Parameters
ParamStatInt = "Statistics Interval"
ParamSpeed = "Linkspeed"
ParamSQL = "Send Queue Limit"
ParamRQL = "Receive Queue Limit"
ParamWakeTout = "S3/S4 Wakeup Timeout"
ParamRWU = "Remote WakeUp"
ParamNHOS = "No Halt On Suspend"
ParamDisable = "Disable"
ParamEnable = "Enable"
ParamNo = "No"
ParamYes = "Yes"
ParamSuspend = "Suspend Timeout"
ParamNetSuspend = "Connected Suspend Timeout"
REG_SZ = 0x00000000
REG_MULTI_SZ = 0x00010000
REG_EXPAND_SZ = 0x00020000
REG_BINARY = 0x00000001
REG_DWORD = 0x00010001
REG_NONE = 0x00020001
SERVICE_KERNEL_DRIVER = 0x00000001
SERVICE_FILE_SYSTEM_DRIVER = 0x00000002
SERVICE_ADAPTER = 0x00000004
SERVICE_RECOGNIZER_DRIVER = 0x00000008
SERVICE_BOOT_START = 0x0
SERVICE_SYSTEM_START = 0x1
SERVICE_AUTO_START = 0x2
SERVICE_DEMAND_START = 0x3
SERVICE_DISABLED = 0x4
SERVICE_ERROR_IGNORE = 0x00000000
SERVICE_ERROR_NORMAL = 0x00000001
SERVICE_ERROR_SEVERE = 0x00000002
SERVICE_ERROR_CRITICAL = 0x00000003
FLG_ADDREG_NOCLOBBER = 0x00000002
FLG_ADDREG_DELVAL = 0x00000004
FLG_ADDREG_APPEND = 0x00000008
FLG_ADDREG_KEYONLY = 0x00000010
FLG_ADDREG_OVERWRITEONLY = 0x00000020
FLG_ADDREG_64BITKEY = 0x00001000
FLG_ADDREG_KEYONLY_COMMON = 0x00002000
FLG_ADDREG_32BITKEY = 0x00004000

[Guide] Unlock your bootloader

WARNING
This process will factory reset your device and wipe the internal memory.
You do this at your own risk. I advise you NOT TO DO THIS as there are risks involved, including, but not limited to, bricking your brand new tablet and renderingit useless. You also may void the warranty. I take NO RESPONSIBILITY for any damage. Again, if you decide to follow these steps, it is entirely at your own risk
Prepare:
If you're a Windows user, you might want to refer here. Chainfire has posted an updated stock ROM which does the unlocking for you. If you're a Linux user, you could try flashing Chainfires image using Heimdall but AFAIK, this has not been tested.
Method 1
Download and install the JAVA SDK from here http://www.oracle.com/technetwork/java/javase/downloads/index.html
Download the Android SDK from here http://developer.android.com/sdk/index.html
Follow the instructions here to download the USB drivers http://developer.android.com/sdk/installing.html
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
Download the fastboot zip attached to this post (includes both Win and Linux version) and extract the files to your "<PATH TO ANDROID SDK>\tools" folder
***Do not leave any blank lines before the first “;”
Code:
;
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
Now to get started…
1) Power off your tablet
2) Hold the VOLUME DOWN button and press the POWER button (your tablet will power on and you will see the BACKUP and USB icons)
3) Use VOLUME DOWN to select the USB icon, and then press VOLUME UP to confirm the selection.
4) You should now be in fastboot mode (the word FASTBOOT should appear somewhere in the top left corner)
5) If Windows doesn’t automatically detect the device, go to device manager and find the ‘Fastboot’ device. Right-click and select update driver, choose to manually install and browse to the “<PATH TO ANDROID SDK>\extras\google\usb_driver\” folder.
6) Open a command prompt and do
Code:
cd "<PATH TO SDK FOLDER>\tools"
fastboot devices
7) Confirm that your device is detected. If it says “waiting for device”, you need to check that the drivers are installed correctly.
8) In the Command window, type:
Code:
fastboot oem unlock
9) On your Tab, Use the VOLUME DOWN button to select YES and then press VOLUME UP to confirm
10) VIOLA! You are unlocked. Note that these instructions are a work-in-progress. As always, your questions and comments are welcome. OSX / Linux instructions coming soon!
Linux Instructions (thanks to Draco32)
Get your Tab into fastboot mode;
1) Power off your Tab and power it back on while holding VOLUME DOWN
2) Highlight the USB icon by pressing VOLUME DOWN
3) Press VOLUME UP to confirm your selection (Fastboot Mode)
4) Download the Tegra 2 compatible fastboot (attached to this post) and put it somewhere in your path (eg /usr/bin)
5) Plug your device into the PC using the provided USB cable.
6) Open a terminal and type
Code:
fastboot devices
this will list the device but it will be a strign of numbers
7) type
Code:
fastboot oem unlock
your tab will then have a yes no option to unlock the bootloader select yes with VOLUME DOWN, and press VOLUME UP to confirm
8) Your bootloader is now unlocked power off the device and power it back on the device will boot and have an unlocked padlock when loading. Also this will factory reset your device this includes everything on the 16 gb storage.
Now that you're done head over here to get root access.
EDIT:
ORIGINAL POST:
Guide for unlocking is here:
http://411technology.wordpress.com/
If you power off your device and power it on again using the volume rocker (NOT THE POWER BUTTON), you get the OEM unlock Screen.
Looks like we might have an unlockable bootloader. If so, I love this thing even more now!
Im off to play with it now. Will be back to post pics shortly. Text from the screen is below
Left:
ODIN3 Download Mode
(Protocol v2)
Reason: Force Key
Secure Mode: Secure
Check Signature: Check
OEM Lock: Lock
Waiting USB Cable...
Click to expand...
Click to collapse
Right Hand Side:
Unlock Bootloader?
-------------------------------
If you unlock the bootloader.....
Click to expand...
Click to collapse
(continues on with crap about the risks etc)
Will post pics shortly. Time to break this thing

Fastboot Windows Driver INF File (Galaxy Tab 10.1/v ONLY!)
Code:
;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 12/06/2010,4.0.0000.00000
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat
;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; "Required section not found in INF file".
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg
[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1
[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64
[Google.NTx86]
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
[Google.NTamd64]
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT
[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall
[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys
[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install
[WinUSB_Install]
KmdfLibraryVersion = 1.9
[USB_Install.HW]
AddReg = Dev_AddReg
[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"
[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles
[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01009.dll,WdfCoInstaller","WinUSBCoInstaller2.dll"
[CoInstallers_CopyFiles]
WinUSBCoInstaller2.dll
WdfCoInstaller01009.dll
[DestinationDirs]
CoInstallers_CopyFiles=11
[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64
[SourceDisksFiles.x86]
WinUSBCoInstaller2.dll = 1
WdfCoInstaller01009.dll = 1
[SourceDisksFiles.amd64]
WinUSBCoInstaller2.dll = 2
WdfCoInstaller01009.dll = 2
[Strings]
ProviderName = "Google, Inc."
SingleAdbInterface = "Android ADB Interface"
CompositeAdbInterface = "Android Composite ADB Interface"
SingleBootLoaderInterface = "Android Bootloader Interface"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Phone"

Correct the title - instead of unlockable should be unlocked.
BTW, what's the advantage?

bcmobile said:
EDIT:
Guide for unlocking is here:
http://411technology.wordpress.com/
If you power off your device and power it on again using the volume rocker (NOT THE POWER BUTTON), you get the OEM unlock Screen.
Click to expand...
Click to collapse
It would appear the SGT 10.1v is another Samsung device with a "3 button recovery" lottery. I have been trying every combo of hardware keys from powered off state on mine and am unable to get the screen you have descibed.
I can however get into a "download mode" (Picture of an android dude doing "road works" and a flashing USB symbol with the word "Downloading") on my device - by pressing the power button and then an instant later pressing the left side of the volume rocker (doesn't seem to work if you press them simultaniously).
Hopefully a smart cookie will figure out a way to put a different firmware in with Odin to enable these options on devices like mine (much like the 3BR fix for the SGS).
Edit - Nevermind, got into it. For me it was Press Power, then an instant later volume left and hold both. When you see a screen with a android dude and a usb symbol - pressing right volume gives you the unlock screen, pressing right volume highlights the USB then pressing right volume to select it puts the device in "fastboot" mode.
Woo hoo!!

myself11 said:
Correct the title - instead of unlockable should be unlocked.
BTW, what's the advantage?
Click to expand...
Click to collapse
Since it is not shipped as unlocked, I actually think unlockable is more appropriate
Advantage is that you can flash unsigned ROMs - no hacks required. This is normally only found on the Nexus handsets so it's a pretty big deal for Devs / hackers.

Hi Guys,
I am unable to get the fastboot drivers working. I can install them correctly. ADB devices appears in device manager but when i type i get nothing back. It's like the fastboot device is not connected?
Do i need a newer version of the SDK?
For some reason SDK manager is not working on my PC at work so i am using an older sdk version.
D:\adbsdkold\android-sdk-windows-1.5_r3\tools>fastboot devices
D:\adbsdkold\android-sdk-windows-1.5_r3\tools>fastboot oem unlock
< waiting for device >
^C

Draco32 said:
Hi Guys,
I am unable to get the fastboot drivers working. I can install them correctly. ADB devices appears in device manager but when i type i get nothing back. It's like the fastboot device is not connected?
Do i need a newer version of the SDK?
For some reason SDK manager is not working on my PC at work so i am using an older sdk version.
D:\adbsdkold\android-sdk-windows-1.5_r3\tools>fastboot devices
D:\adbsdkold\android-sdk-windows-1.5_r3\tools>fastboot oem unlock
< waiting for device >
^C
Click to expand...
Click to collapse
If you look at the response from "fastboot devices" command it cannot see any devices.
Post your anroid_winusb.inf (\android-sdk-windows\extras\google\usb_driveranroid_winusb.inf) may just be entered in wrong section/misspell
Also what state is it in? your device might just not be in fastboot
P.S. update your SDK no reason not to

Android Driver
Hey,
I'm using the Nexus S driver thats probably the issue. It reads like this at present.
Can you upload the Google USB drivers as the SDK doesn't seem to be working for me.
--------------------android_winusb.inf------------------------------------------
;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 12/06/2010,4.0.0000.00000
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat
;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; "Required section not found in INF file".
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg
[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1
[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64
[Google.NTx86]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
;
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
[Google.NTamd64]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT
[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall
[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys
[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install
[WinUSB_Install]
KmdfLibraryVersion = 1.9
[USB_Install.HW]
AddReg = Dev_AddReg
[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"
[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles
[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01009.dll,WdfCoInstaller","WinUSBCoInstaller2.dll"
[CoInstallers_CopyFiles]
WinUSBCoInstaller2.dll
WdfCoInstaller01009.dll
[DestinationDirs]
CoInstallers_CopyFiles=11
[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64
[SourceDisksFiles.x86]
WinUSBCoInstaller2.dll = 1
WdfCoInstaller01009.dll = 1
[SourceDisksFiles.amd64]
WinUSBCoInstaller2.dll = 2
WdfCoInstaller01009.dll = 2
[Strings]
ProviderName = "Google, Inc."
SingleAdbInterface = "Android ADB Interface"
CompositeAdbInterface = "Android Composite ADB Interface"
SingleBootLoaderInterface = "Android Bootloader Interface"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Phone"

Yer that looks correct for a 32bit-OS but if your running 64bit-OS put it under "Google.NTamd64"
Also make sure you follow the guide bcmobile post to the letter to get into fastboot
Power off your tablet
Press the VOLUME DOWN button (your tablet will power on and you will see the BACKUP and USB icons)
Use VOLUME UP to select the USB icon, and then press VOLUME DOWN to select it.
You should now be in fastboot mode (the word FASTBOOT should appear somewhere in the top left corner)
If your computer doesn't automatically detect the device, go to device manager and find the 'Fastboot' device. Right-click and select update driver, choose to manually install and browse to the "C:\android-sdk-windows\extras\google\usb_driver\" folder.
Click to expand...
Click to collapse

50-3 said:
Yer that looks correct for a 32bit-OS but if your running 64bit-OS put it under "Google.NTamd64"
Also make sure you follow the guide bcmobile post to the letter to get into fastboot
Click to expand...
Click to collapse
Followed the guide correctly i have fast boot coming up on the tablet just no devices are shown when i do fast boot devices i will have a look when i get home.
Also the part of the guide where it says Volume Up to move it over to the USB icon is incorrect. It's actually Volume Down to move to the USB icon when selecting the fastboot option.
Cheers,
Adrian

Draco32 said:
Followed the guide correctly i have fast boot coming up on the tablet just no devices are shown when i do fast boot devices i will have a look when i get home.
Also the part of the guide where it says Volume Up to move it over to the USB icon is incorrect. It's actually Volume Down to move to the USB icon when selecting the fastboot option.
Cheers,
Adrian
Click to expand...
Click to collapse
Well if you have the right driver file config and in fastboot only thing left i can think of is that windows hasn't been told to use the driver
If your computer doesn't automatically detect the device, go to device manager and find the 'Fastboot' device. Right-click and select update driver, choose to manually install and browse to the "C:\android-sdk-windows\extras\google\usb_driver\" folder.
Click to expand...
Click to collapse
Or it's an old version of SDK tools but i do think that is it.
Anyway sorry i couldn't have been more help

Draco32 said:
Followed the guide correctly i have fast boot coming up on the tablet just no devices are shown when i do fast boot devices i will have a look when i get home.
Also the part of the guide where it says Volume Up to move it over to the USB icon is incorrect. It's actually Volume Down to move to the USB icon when selecting the fastboot option.
Cheers,
Adrian
Click to expand...
Click to collapse
Go into device manager and find the fastboot device. Right click and uninstall it. Unplug the tab and Reboot your PC. Put your tab into fastboot mode before reconnecting
Thanks for pointing out the vol up / down error. I had the old galaxy tab which had them the other way around since it was designed to be used in portrait mode. Ill correct it in the guide later tonight.
Sent from my GT-P7100 using XDA Premium App

bcmobile said:
Advantage is that you can flash unsigned ROMs - no hacks required. This is normally only found on the Nexus handsets so it's a pretty big deal for Devs / hackers.
Click to expand...
Click to collapse
Noob question: but we will still need devs that cook ROM's, right? It isn't as simple as grab Google's update and install it on 10.1v, is it?

myself11 said:
Noob question: but we will still need devs that cook ROM's, right? It isn't as simple as grab Google's update and install it on 10.1v, is it?
Click to expand...
Click to collapse
Unfortunately no, But if were lucky the Devs will push them out quickly

Hi Everyone,
Just to let you know i managed to unlock the bootloader. I used ubuntu linux and fastboot method to get it unlocked.
Get your Tab into fastboot mode;
1. Power + Volume Down
2. Highlight the USB icon by pressing Volume Down
3. Press Volume Up to select the USB icon (Fastboot Mode)
Download the Tegra 2 compatible fastboot from this threadhttp://forum.xda-developers.com/showthread.php?t=1055754;
1. Plug your device into the PC using the provided USB cable.
2. open a terminal and type fastboot devices this will list the device but it will be a strign of numbers
3. type "fastboot oem unlock" your tab will then have a yes no option to unlock the bootloader select yes with Volume Up
5. Your bootloader is now unlocked power off the device and power it back on the device will boot and have an unlocked padlock when loading. Also this will factory reset your device this includes everything on the 16 gb storage.
Cheers,
Draco

A little off-topic, but didn't want to open a new topic: is australian radio version different from european version?

Draco32 said:
Hi Everyone,
...
5. Your bootloader is now unlocked power off the device and power it back on the device will boot and have an unlocked padlock when loading. Also this will factory reset your device this includes everything on the 16 gb storage.
Click to expand...
Click to collapse
Hi everybody,
I received my 10.1v yesterday (Vodafone, Germany) and have noticed that it allready boots with an unlocked padlock. Does this mean that I have an allready unlocked Tab? This is strange ...

smack said:
Hi everybody,
I received my 10.1v yesterday (Vodafone, Germany) and have noticed that it allready boots with an unlocked padlock. Does this mean that I have an allready unlocked Tab? This is strange ...
Click to expand...
Click to collapse
Cool!
Yes that should mean it's unlocked. Apparently the 10.1 is shipping unlocked as well so I guess I shouldn't be surprised.
If you want to be sure, go into fastboot mode using steps 1-4 above and it should say:
Lock State: UNLOCKED
...on the fastboot screen

unlucky, if I Hold the VOLUME DOWN button and press the POWER button , the tablet goes to the normal UI, I cannot understand.......
I did not see anything about BACKUP and USB icons

For those who are having diffficulties unlocking the bootloader, follow all steps mentioned in the guide, and then enter the device in USB mode but don't plug it to the pc.
Open the cmd and type:
cd "<PATH TO SDK FOLDER>\tools"
fastboot devices
fastboot oem unlock (and it will appear a notification saying waiting for device)
Only nows, in USB mode, plug the tab to the PC.
After that choose in the tab "yes" and your bootloader is unlocked.
Hope this could help!

Modify android_winusb.inf for the 70b IT with ADB

If you have the new 7 It with android 3.2 or android 2.2
for use ADB
add on your android_winusb.inf
Search [Google.NTx86]
Search ;Archos Gen8
Add those two lines
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1569
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1569&MI_01
and also
Search [Google.NTamd64]
Search ;Archos Gen8
Add those two lines
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1569
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1569&MI_01
and save the file !
Enjoy !!

[Q][KFHD7]Can't mount /data

Alright, So I'll admit I messed up the whole process and I'm basically trying to unbrick it at this point. I installed TWRP 2.4.4.0 on my KFHD 7" wiped everything then realized I never pushed the fioles to flash onto the KF before I did this. After messing around with my adb drivers for a while (I had to spoof them and add values to the android_usb.inf for it to even show up now) I can use adb while in TWRP and it shows my device as "recovery" I was able to push files to it earlier, but now I can't mount "/data" which is where I pushed those files earlier. I do have a stock-boot.img a stock-recovery.img and a stock-system.img (Or at least I hope, Idk if it got wiped) I'm not all to familiar with adb or fastboot commands to know what I can do to get anything back or at least get /data back.
If any of y'all could help me out, that'd be great, otherwise I now have a really expensive paper-weight.
1 more thing. I don't have ADB when I'm in fastboot. It shows up as an "Android composite ADB interface" in Device manager, but when I run adb (even after restarts) it never shows up in adb devices. Once again I had to spoof that driver because it was showing up as "Unknown Device' (I checked hardware ID's and it was the kindle 0x1949 that I installed the drivers for)
KFFA Isn't seeming to work, I've tried there drivers as well, no dice while the Kindle is in TWRP or in Fastboot.
I have the SDK and my own custom ADB Drivers installed, If you want me to post the .inf here for reference, I can.
EDIT: Okay, I've really screwed up, i flashed the stock boot, now all I get is a orange kindle fire logo. and so far IDK how to get into recovery. The logo doesn't animate at all, I'm guessing I have no OS installed, I think I just bricked it for good, unless I can get into a fastboot. HELP!!!

Android_usb.inf
These are reflected in both NTx86 and NTamd64
Code:
;Kindle Fire #These are the HW ID's for Amazon Kindle Fire OS
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
;Kindle Fire #These are the HW ID's for Fastboot
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0007
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0100
;Kindle Fire HD 7 #These are the HW ID's for TWRP
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0216

[Q] How to create an image from a stock KDZ file for nvflashing

Good day to all dev and to the community,
first of, i know this is not the right thread to post but im kinda desperate now.
i purchase a phone which is optimus ex su880 (nearest family is su660)
i tried updating using the LG updater but unfortunately i bricked my phone.
right now, i can no longer boot to S/w / normal mode and my only solution is to flash it via NVflash.
but my problem is, because of the lack of support for this phone. i cant find any image or .bat file to re install the ICS rom back.
now, my question is if we can create a .bat file/image from a Stock KDZ rom?
i can boot to APX but i have no firmware to flash.
your exeperties is highly appreciated.
i already spent 3 days looking for an answer but to no avail...hope you can enlighten me.

Hi alamatnitotoy,
seems that you have to deal with Tegra 250 AP20H a.k.a. Ventana.
In the first place, have you managed to read your partition table?

Can you send me link where I can download the rom for your phone?
Edit: I managed to download v10m kdz. I am flashing to my p990. Hopefuly i could get the necessary files this way to make you an nvflash rom
Edit2: Download my attachment, please. Extract the rar, then run flash.bat. It should flash the bootloader to your phone after that you can put your phone into S/W download mode to flash any original rom.
I hope it is going to work.

thanks
thank you very much sir.. you save my day...

Click, click, click....
How to create, or, can you create it for me?

tryin said:
Click, click, click....
How to create, or, can you create it for me?
Click to expand...
Click to collapse
If you have su880 it will work for you as well, but if your partition layout got damaged it won't.
When I get home I will make a tutorial how to obtain bootloader.

bitdomo said:
If you have su880 it will work for you as well, but if your partition layout got damaged it won't.
When I get home I will make a tutorial how to obtain bootloader.
Click to expand...
Click to collapse
No no sorry, I have been misunderstood, I wanted to say that this posts don't explain how to create an nvflash image from a stock KDZ file, but only have the solution handed on a plate, or better, in an archive , which is not very educational I think...
But if all goes well for alamatnitotoy....
Thanks anyway for your thought, don't worry...

Well, let the tutorial begin!
Download a kdz rom. In my case I downloaded v10m
Download AIO-toolkit for p990
Start AIO-toolkit select option number 5, then select option number 1. Drag and drop the kdz file to the AIO-toolkit window and hit enter. It will convert the kdz file into smartflash format. When the process finished (the smartflash files are in the root directory of the AIO-toolkit in the v10m folder), you can choose to extract the smartflash file. Choose yes. Then select option number 2. On the next screen select option A or E, it does not matter which you choose because the partitions are in a different order in a su880 smartflash file. So, you have to figure out which partition is which after the extraction. I choosed option A. The extracted files will be in the root directory of AIO-toolkit in the extracted_files folder.
Compare the extracted files with any other bootloader file from p990 or su660 to find out which file is the bootloader, but hopefully the file named bootloader.img is truly the bootlader.
SU880 is the brother phone of P990 and SU660, therefore I suggested that the bootloader partition for SU880 is the 4th partition just like for SU660 and P990
Open bootloader.img in hex editor, delete the bunch of FF hex values from the end of the file then save it.
Now you have to download nvflash and copy the bootloader.img to the nvflash folder.
Create a flash.bat file. fill it with this content:
Code:
nvflash.exe --bl bootloader.img --download 4 bootloader.img
Connet your phone in nvflash mode
Double click on flash.bat and hope the best
After the flashing is done restart your phone to S/W download mode and smartflash the previously converted rom to smarthflash format
Now you have a working su880 with a bootloader which you can use with nvflash
To create an nvflash rom, you need the following files:
bootloader (we have it already)
partition table configuration file
bct file (Binary Configuration Table)
system.img
boot.img (kernel)
recovery.img
Obtaining partition table:
Connect phone in nvflash mode and run nvflash with the following command:
Code:
nvflash.exe --bl bootloader.img --getpartitiontable su880_pt_table.txt
Now you have to convert it by hand to a partition config file. Use su660 or p990 config files as a sample to create it for su880.
Rename the file to partition.cfg
The rest of the files:
You have 2 ways to get the rest of the files by figuring out which extraded files are which files, or use nvflash.
If you choose nvflash then you can read back the partitions from your phone to your computer by this command:
Code:
nvflash.exe --bl bootloader.img --read N FILENAME
N is for the number of the partition and FILENAME is for the name of the file you want to save. After the firt partition read use this command to save the rest of the partitions
Code:
nvflash.exe -r --download N FILENAME
Check the partition config file for which partition has which number.
Name of the partition you need:
APP: system.img
LNX: boot.img (kernel)
SOS: recovery.img
When you read back all partition on the list above (or figured whcih extracted partition file is which partition) then you have to obtain the bct file.
Obtaining bct file:
Run nvflash with this command:
Code:
nvflash.exe --bct su880.bct --getbct --bl bootloader.img
After the command got execudet you will have the btc file on your computer.
Now you have everything. Just one thing left.
Create a flash.bat file and fill it with this content:
Code:
nvflash.exe --bct su880.bct --setbct --odmdata 0xC8000 --configfile partition.cfg --create --bl bootloader.img --go
I haven't tested it yet, because I don't have su880 phone. The only thing which bothers is that I am not 100% sure that my partition config file is correct. I am uploading my work, maybe you can test, but there is a high chance it will brick your phone. I beleive you can still smartflash any rom if you try it and it bricks your phone. I tried it on my p990 just for testing every script is written correctly and I don't made a typo. So it flashed correctly, but since my phone is not a su880 I can not tell is it going to work.
Finally my work is uploaded. Download here

Very good work bitdomo!
Sure very instructive!
Only one question, what's the meaning of
Code:
--odmdata 0xC8000
? Why that address?

tryin said:
Very good work bitdomo!
Sure very instructive!
Only one question, what's the meaning of
Code:
--odmdata 0xC8000
? Why that address?
Click to expand...
Click to collapse
Actually I don't know what is that, I would love to know it as well. This addres is there in every nvflash rom for su660 and p990. To get this information you have to extract the bct file.
The program which extract bct file is here. You have to compile it on linux. At the end of this read me there is an example how to use this program.
Performing that command for su880.btc will lead you to a file like this:
Code:
Version = 0x00020001;
BlockSize = 0x00004000;
PageSize = 0x00000200;
PartitionSize = 0x01000000;
OdmData = 0x000c8000;
# Bootloader used = 1;
# Bootloaders max = 4;
# BCT size = 4080;
# Hash size = 16;
# Crypto offset = 16;
# Crypto length = 4064;
# Max BCT search blocks = 64;
#
# These values are set by cbootimage using the
# bootloader provided by the Bootloader=...
# configuration option.
#
# Bootloader[0].Version = 0x00000001;
# Bootloader[0].Start block = 384;
# Bootloader[0].Start page = 0;
# Bootloader[0].Length = 923444;
# Bootloader[0].Load address = 0x00108000;
# Bootloader[0].Entry point = 0x00108000;
# Bootloader[0].Attributes = 0x00000004;
SDRAM[0].MemoryType = NvBootMemoryType_LpDdr2;
SDRAM[0].PllMChargePumpSetupControl = 0x00000008;
SDRAM[0].PllMLoopFilterSetupControl = 0x00000000;
SDRAM[0].PllMInputDivider = 0x0000000c;
SDRAM[0].PllMFeedbackDivider = 0x000002f8;
SDRAM[0].PllMPostDivider = 0x00000000;
SDRAM[0].PllMStableTime = 0x0000012c;
SDRAM[0].EmcClockDivider = 0x00000001;
SDRAM[0].EmcAutoCalInterval = 0x00000000;
SDRAM[0].EmcAutoCalConfig = 0xe0a61111;
SDRAM[0].EmcAutoCalWait = 0x00000000;
SDRAM[0].EmcPinProgramWait = 0x00000000;
SDRAM[0].EmcRc = 0x00000017;
SDRAM[0].EmcRfc = 0x00000032;
SDRAM[0].EmcRas = 0x00000010;
SDRAM[0].EmcRp = 0x00000007;
SDRAM[0].EmcR2w = 0x00000008;
SDRAM[0].EmcW2r = 0x00000005;
SDRAM[0].EmcR2p = 0x00000003;
SDRAM[0].EmcW2p = 0x0000000b;
SDRAM[0].EmcRrd = 0x00000004;
SDRAM[0].EmcRdRcd = 0x00000007;
SDRAM[0].EmcWrRcd = 0x00000007;
SDRAM[0].EmcRext = 0x00000003;
SDRAM[0].EmcWdv = 0x00000003;
SDRAM[0].EmcQUseExtra = 0x00000006;
SDRAM[0].EmcQUse = 0x00000007;
SDRAM[0].EmcQRst = 0x00000004;
SDRAM[0].EmcQSafe = 0x0000000a;
SDRAM[0].EmcRdv = 0x0000000e;
SDRAM[0].EmcRefresh = 0x0000059f;
SDRAM[0].EmcBurstRefreshNum = 0x00000000;
SDRAM[0].EmcPdEx2Wr = 0x00000004;
SDRAM[0].EmcPdEx2Rd = 0x00000004;
SDRAM[0].EmcPChg2Pden = 0x00000007;
SDRAM[0].EmcAct2Pden = 0x00000008;
SDRAM[0].EmcAr2Pden = 0x00000001;
SDRAM[0].EmcRw2Pden = 0x00000011;
SDRAM[0].EmcTxsr = 0x00000036;
SDRAM[0].EmcTcke = 0x00000003;
SDRAM[0].EmcTfaw = 0x00000013;
SDRAM[0].EmcTrpab = 0x00000008;
SDRAM[0].EmcTClkStable = 0x00000007;
SDRAM[0].EmcTClkStop = 0x00000002;
SDRAM[0].EmcTRefBw = 0x0000062d;
SDRAM[0].EmcFbioCfg1 = 0x00000000;
SDRAM[0].EmcFbioDqsibDlyMsb = 0x00000000;
SDRAM[0].EmcFbioDqsibDly = 0x2c2c2c2c;
SDRAM[0].EmcFbioQuseDlyMsb = 0x00000000;
SDRAM[0].EmcFbioQuseDly = 0x14141414;
SDRAM[0].EmcFbioCfg5 = 0x00000282;
SDRAM[0].EmcFbioCfg6 = 0x00000003;
SDRAM[0].EmcFbioSpare = 0x00000000;
SDRAM[0].EmcMrsResetDllWait = 0x00000000;
SDRAM[0].EmcMrsResetDll = 0x00000000;
SDRAM[0].EmcMrsDdr2DllReset = 0x00000000;
SDRAM[0].EmcMrs = 0x00000000;
SDRAM[0].EmcEmrsEmr2 = 0x00000000;
SDRAM[0].EmcEmrsEmr3 = 0x00000000;
SDRAM[0].EmcEmrsDdr2DllEnable = 0x00000000;
SDRAM[0].EmcEmrsDdr2OcdCalib = 0x00000000;
SDRAM[0].EmcEmrs = 0x00000000;
SDRAM[0].EmcMrw1 = 0x0001008a;
SDRAM[0].EmcMrw2 = 0x00020004;
SDRAM[0].EmcMrw3 = 0x00030002;
SDRAM[0].EmcMrwResetCommand = 0x003f0000;
SDRAM[0].EmcMrwResetNInitWait = 0x0000000a;
SDRAM[0].EmcAdrCfg1 = 0x00070303;
SDRAM[0].EmcAdrCfg = 0x01070303;
SDRAM[0].McEmemCfg = 0x00100000;
SDRAM[0].McLowLatencyConfig = 0x80000003;
SDRAM[0].EmcCfg2 = 0x00000403;
SDRAM[0].EmcCfgDigDll = 0xf0000413;
SDRAM[0].EmcCfgClktrim0 = 0x00000000;
SDRAM[0].EmcCfgClktrim1 = 0x00000000;
SDRAM[0].EmcCfgClktrim2 = 0x00000000;
SDRAM[0].EmcCfg = 0x0001ff00;
SDRAM[0].EmcDbg = 0x01000020;
SDRAM[0].AhbArbitrationXbarCtrl = 0x00010000;
SDRAM[0].EmcDllXformDqs = 0x00000010;
SDRAM[0].EmcDllXformQUse = 0x00000008;
SDRAM[0].WarmBootWait = 0x00000001;
SDRAM[0].EmcCttTermCtrl = 0x00000802;
SDRAM[0].EmcOdtWrite = 0x00000000;
SDRAM[0].EmcOdtRead = 0x00000000;
SDRAM[0].EmcZcalRefCnt = 0x00000000;
SDRAM[0].EmcZcalWaitCnt = 0x00000023;
SDRAM[0].EmcZcalMrwCmd = 0x000a0056;
SDRAM[0].EmcMrwZqInitDev0 = 0x800a00ff;
SDRAM[0].EmcMrwZqInitDev1 = 0x400a00ff;
SDRAM[0].EmcMrwZqInitWait = 0x00000001;
SDRAM[0].EmcDdr2Wait = 0x00000000;
SDRAM[0].PmcDdrPwr = 0x00000000;
SDRAM[0].ApbMiscGpXm2CfgAPadCtrl = 0x77ffc000;
SDRAM[0].ApbMiscGpXm2CfgCPadCtrl2 = 0x08080040;
SDRAM[0].ApbMiscGpXm2CfgCPadCtrl = 0x77fffff8;
SDRAM[0].ApbMiscGpXm2CfgDPadCtrl2 = 0x00000000;
SDRAM[0].ApbMiscGpXm2CfgDPadCtrl = 0x77fffff8;
SDRAM[0].ApbMiscGpXm2ClkCfgPadCtrl = 0x77ffc000;
SDRAM[0].ApbMiscGpXm2CompPadCtrl = 0x01f1f008;
SDRAM[0].ApbMiscGpXm2VttGenPadCtrl = 0x00005500;
For p990:
Code:
Version = 0x00020001;
BlockSize = 0x00004000;
PageSize = 0x00000200;
PartitionSize = 0x01000000;
OdmData = 0x000c8000;
# Bootloader used = 0;
# Bootloaders max = 4;
# BCT size = 4080;
# Hash size = 16;
# Crypto offset = 16;
# Crypto length = 4064;
# Max BCT search blocks = 64;
DevType[0] = NvBootDevType_Sdmmc;
DeviceParam[0].SdmmcParams.ClockDivider = 0x0000000c;
DeviceParam[0].SdmmcParams.DataWidth = NvBootSdmmcDataWidth_8Bit;
DeviceParam[0].SdmmcParams.MaxPowerClassSupported = 0x00000000;
DevType[1] = NvBootDevType_Sdmmc;
DeviceParam[1].SdmmcParams.ClockDivider = 0x0000000c;
DeviceParam[1].SdmmcParams.DataWidth = NvBootSdmmcDataWidth_8Bit;
DeviceParam[1].SdmmcParams.MaxPowerClassSupported = 0x00000000;
DevType[2] = NvBootDevType_Sdmmc;
DeviceParam[2].SdmmcParams.ClockDivider = 0x0000000c;
DeviceParam[2].SdmmcParams.DataWidth = NvBootSdmmcDataWidth_8Bit;
DeviceParam[2].SdmmcParams.MaxPowerClassSupported = 0x00000000;
DevType[3] = NvBootDevType_Sdmmc;
DeviceParam[3].SdmmcParams.ClockDivider = 0x0000000c;
DeviceParam[3].SdmmcParams.DataWidth = NvBootSdmmcDataWidth_8Bit;
DeviceParam[3].SdmmcParams.MaxPowerClassSupported = 0x00000000;
SDRAM[0].MemoryType = NvBootMemoryType_LpDdr2;
SDRAM[0].PllMChargePumpSetupControl = 0x00000008;
SDRAM[0].PllMLoopFilterSetupControl = 0x00000000;
SDRAM[0].PllMInputDivider = 0x0000000c;
SDRAM[0].PllMFeedbackDivider = 0x00000258;
SDRAM[0].PllMPostDivider = 0x00000000;
SDRAM[0].PllMStableTime = 0x0000012c;
SDRAM[0].EmcClockDivider = 0x00000001;
SDRAM[0].EmcAutoCalInterval = 0x00000000;
SDRAM[0].EmcAutoCalConfig = 0xe0a61111;
SDRAM[0].EmcAutoCalWait = 0x00000000;
SDRAM[0].EmcPinProgramWait = 0x00000000;
SDRAM[0].EmcRc = 0x00000012;
SDRAM[0].EmcRfc = 0x00000027;
SDRAM[0].EmcRas = 0x0000000d;
SDRAM[0].EmcRp = 0x00000006;
SDRAM[0].EmcR2w = 0x00000007;
SDRAM[0].EmcW2r = 0x00000005;
SDRAM[0].EmcR2p = 0x00000003;
SDRAM[0].EmcW2p = 0x0000000b;
SDRAM[0].EmcRrd = 0x00000003;
SDRAM[0].EmcRdRcd = 0x00000006;
SDRAM[0].EmcWrRcd = 0x00000006;
SDRAM[0].EmcRext = 0x00000003;
SDRAM[0].EmcWdv = 0x00000003;
SDRAM[0].EmcQUseExtra = 0x00000006;
SDRAM[0].EmcQUse = 0x00000007;
SDRAM[0].EmcQRst = 0x00000004;
SDRAM[0].EmcQSafe = 0x00000009;
SDRAM[0].EmcRdv = 0x0000000d;
SDRAM[0].EmcRefresh = 0x0000045f;
SDRAM[0].EmcBurstRefreshNum = 0x00000000;
SDRAM[0].EmcPdEx2Wr = 0x00000004;
SDRAM[0].EmcPdEx2Rd = 0x00000004;
SDRAM[0].EmcPChg2Pden = 0x00000006;
SDRAM[0].EmcAct2Pden = 0x00000008;
SDRAM[0].EmcAr2Pden = 0x00000001;
SDRAM[0].EmcRw2Pden = 0x0000000f;
SDRAM[0].EmcTxsr = 0x0000002a;
SDRAM[0].EmcTcke = 0x00000003;
SDRAM[0].EmcTfaw = 0x0000000f;
SDRAM[0].EmcTrpab = 0x00000007;
SDRAM[0].EmcTClkStable = 0x00000007;
SDRAM[0].EmcTClkStop = 0x00000002;
SDRAM[0].EmcTRefBw = 0x000004e0;
SDRAM[0].EmcFbioCfg1 = 0x00000000;
SDRAM[0].EmcFbioDqsibDlyMsb = 0x00000000;
SDRAM[0].EmcFbioDqsibDly = 0x34343434;
SDRAM[0].EmcFbioQuseDlyMsb = 0x00000000;
SDRAM[0].EmcFbioQuseDly = 0x00000000;
SDRAM[0].EmcFbioCfg5 = 0x00000282;
SDRAM[0].EmcFbioCfg6 = 0x00000002;
SDRAM[0].EmcFbioSpare = 0x00000000;
SDRAM[0].EmcMrsResetDllWait = 0x00000000;
SDRAM[0].EmcMrsResetDll = 0x00000000;
SDRAM[0].EmcMrsDdr2DllReset = 0x00000000;
SDRAM[0].EmcMrs = 0x00000000;
SDRAM[0].EmcEmrsEmr2 = 0x00000000;
SDRAM[0].EmcEmrsEmr3 = 0x00000000;
SDRAM[0].EmcEmrsDdr2DllEnable = 0x00000000;
SDRAM[0].EmcEmrsDdr2OcdCalib = 0x00000000;
SDRAM[0].EmcEmrs = 0x00000000;
SDRAM[0].EmcMrw1 = 0x0001008a;
SDRAM[0].EmcMrw2 = 0x00020004;
SDRAM[0].EmcMrw3 = 0x00030002;
SDRAM[0].EmcMrwResetCommand = 0x003f0000;
SDRAM[0].EmcMrwResetNInitWait = 0x0000000a;
SDRAM[0].EmcAdrCfg1 = 0x00060302;
SDRAM[0].EmcAdrCfg = 0x01060302;
SDRAM[0].McEmemCfg = 0x00080000;
SDRAM[0].McLowLatencyConfig = 0x80000003;
SDRAM[0].EmcCfg2 = 0x00000403;
SDRAM[0].EmcCfgDigDll = 0xe0000413;
SDRAM[0].EmcCfgClktrim0 = 0x00000000;
SDRAM[0].EmcCfgClktrim1 = 0x00000000;
SDRAM[0].EmcCfgClktrim2 = 0x00000000;
SDRAM[0].EmcCfg = 0x0001ff00;
SDRAM[0].EmcDbg = 0x01000020;
SDRAM[0].AhbArbitrationXbarCtrl = 0x00010000;
SDRAM[0].EmcDllXformDqs = 0x00000010;
SDRAM[0].EmcDllXformQUse = 0x00000008;
SDRAM[0].WarmBootWait = 0x00000001;
SDRAM[0].EmcCttTermCtrl = 0x00000802;
SDRAM[0].EmcOdtWrite = 0x00000000;
SDRAM[0].EmcOdtRead = 0x00000000;
SDRAM[0].EmcZcalRefCnt = 0x00000000;
SDRAM[0].EmcZcalWaitCnt = 0x0000001b;
SDRAM[0].EmcZcalMrwCmd = 0x000a0056;
SDRAM[0].EmcMrwZqInitDev0 = 0x800a00ff;
SDRAM[0].EmcMrwZqInitDev1 = 0x400a00ff;
SDRAM[0].EmcMrwZqInitWait = 0x00000001;
SDRAM[0].EmcDdr2Wait = 0x00000000;
SDRAM[0].PmcDdrPwr = 0x00000000;
SDRAM[0].ApbMiscGpXm2CfgAPadCtrl = 0x77ffc000;
SDRAM[0].ApbMiscGpXm2CfgCPadCtrl2 = 0x08080040;
SDRAM[0].ApbMiscGpXm2CfgCPadCtrl = 0x77fffff8;
SDRAM[0].ApbMiscGpXm2CfgDPadCtrl2 = 0x00000000;
SDRAM[0].ApbMiscGpXm2CfgDPadCtrl = 0x77fffff8;
SDRAM[0].ApbMiscGpXm2ClkCfgPadCtrl = 0x77ffc000;
SDRAM[0].ApbMiscGpXm2CompPadCtrl = 0x01f1f008;
SDRAM[0].ApbMiscGpXm2VttGenPadCtrl = 0x00005500;
If you check the begining of the su880.bct config you can see the odmdata is the same as in the p990.bct config.
That is why I put that --odmdata 0xc8000.

I downloaded bct_dump some time ago, from here, but this is my BCT file:
Version = 0x00020001;
BlockSize = 0x00004000;
PageSize = 0x00000200;
PartitionSize = 0x01000000;
# Bootloader used = 1;
# Bootloaders max = 4;
# BCT size = 4080;
# Hash size = 16;
# Crypto offset = 16;
# Crypto length = 4064;
# Max BCT search blocks = 64;
#
# These values are set by cbootimage using the
# bootloader provided by the Bootloader=...
# configuration option.
#
# Bootloader[0].Version = 0x00000001;
# Bootloader[0].Start block = 288;
# Bootloader[0].Start page = 0;
# Bootloader[0].Length = 891020;
# Bootloader[0].Load address = 0x00108000;
# Bootloader[0].Entry point = 0x00108000;
# Bootloader[0].Attributes = 0x00000004;
DevType[0] = NvBootDevType_Sdmmc;
DeviceParam[0].SdmmcParams.ClockDivider = 0x0000000c;
DeviceParam[0].SdmmcParams.DataWidth = NvBootSdmmcDataWidth_8Bit;
DeviceParam[0].SdmmcParams.MaxPowerClassSupported = 0x00000000;
DevType[1] = NvBootDevType_Sdmmc;
DeviceParam[1].SdmmcParams.ClockDivider = 0x0000000c;
DeviceParam[1].SdmmcParams.DataWidth = NvBootSdmmcDataWidth_8Bit;
DeviceParam[1].SdmmcParams.MaxPowerClassSupported = 0x00000000;
DevType[2] = NvBootDevType_Sdmmc;
DeviceParam[2].SdmmcParams.ClockDivider = 0x0000000c;
DeviceParam[2].SdmmcParams.DataWidth = NvBootSdmmcDataWidth_8Bit;
DeviceParam[2].SdmmcParams.MaxPowerClassSupported = 0x00000000;
DevType[3] = NvBootDevType_Sdmmc;
DeviceParam[3].SdmmcParams.ClockDivider = 0x0000000c;
DeviceParam[3].SdmmcParams.DataWidth = NvBootSdmmcDataWidth_8Bit;
DeviceParam[3].SdmmcParams.MaxPowerClassSupported = 0x00000000;
SDRAM[0].MemoryType = NvBootMemoryType_LpDdr2;
SDRAM[0].PllMChargePumpSetupControl = 0x00000008;
SDRAM[0].PllMLoopFilterSetupControl = 0x00000000;
SDRAM[0].PllMInputDivider = 0x0000000c;
SDRAM[0].PllMFeedbackDivider = 0x00000258;
SDRAM[0].PllMPostDivider = 0x00000000;
SDRAM[0].PllMStableTime = 0x0000012c;
SDRAM[0].EmcClockDivider = 0x00000001;
SDRAM[0].EmcAutoCalInterval = 0x00000000;
SDRAM[0].EmcAutoCalConfig = 0xe0a61111;
SDRAM[0].EmcAutoCalWait = 0x00000000;
SDRAM[0].EmcPinProgramWait = 0x00000000;
SDRAM[0].EmcRc = 0x00000012;
SDRAM[0].EmcRfc = 0x00000027;
SDRAM[0].EmcRas = 0x0000000d;
SDRAM[0].EmcRp = 0x00000006;
SDRAM[0].EmcR2w = 0x00000007;
SDRAM[0].EmcW2r = 0x00000005;
SDRAM[0].EmcR2p = 0x00000003;
SDRAM[0].EmcW2p = 0x0000000b;
SDRAM[0].EmcRrd = 0x00000003;
SDRAM[0].EmcRdRcd = 0x00000006;
SDRAM[0].EmcWrRcd = 0x00000006;
SDRAM[0].EmcRext = 0x00000003;
SDRAM[0].EmcWdv = 0x00000003;
SDRAM[0].EmcQUseExtra = 0x00000006;
SDRAM[0].EmcQUse = 0x00000007;
SDRAM[0].EmcQRst = 0x00000004;
SDRAM[0].EmcQSafe = 0x00000009;
SDRAM[0].EmcRdv = 0x0000000d;
SDRAM[0].EmcRefresh = 0x0000045f;
SDRAM[0].EmcBurstRefreshNum = 0x00000000;
SDRAM[0].EmcPdEx2Wr = 0x00000004;
SDRAM[0].EmcPdEx2Rd = 0x00000004;
SDRAM[0].EmcPChg2Pden = 0x00000006;
SDRAM[0].EmcAct2Pden = 0x00000008;
SDRAM[0].EmcAr2Pden = 0x00000001;
SDRAM[0].EmcRw2Pden = 0x0000000f;
SDRAM[0].EmcTxsr = 0x0000002a;
SDRAM[0].EmcTcke = 0x00000003;
SDRAM[0].EmcTfaw = 0x0000000f;
SDRAM[0].EmcTrpab = 0x00000007;
SDRAM[0].EmcTClkStable = 0x00000007;
SDRAM[0].EmcTClkStop = 0x00000002;
SDRAM[0].EmcTRefBw = 0x000004e0;
SDRAM[0].EmcFbioCfg1 = 0x00000000;
SDRAM[0].EmcFbioDqsibDlyMsb = 0x00000000;
SDRAM[0].EmcFbioDqsibDly = 0x34343434;
SDRAM[0].EmcFbioQuseDlyMsb = 0x00000000;
SDRAM[0].EmcFbioQuseDly = 0x00000000;
SDRAM[0].EmcFbioCfg5 = 0x00000282;
SDRAM[0].EmcFbioCfg6 = 0x00000002;
SDRAM[0].EmcFbioSpare = 0x00000000;
SDRAM[0].EmcMrsResetDllWait = 0x00000000;
SDRAM[0].EmcMrsResetDll = 0x00000000;
SDRAM[0].EmcMrsDdr2DllReset = 0x00000000;
SDRAM[0].EmcMrs = 0x00000000;
SDRAM[0].EmcEmrsEmr2 = 0x00000000;
SDRAM[0].EmcEmrsEmr3 = 0x00000000;
SDRAM[0].EmcEmrsDdr2DllEnable = 0x00000000;
SDRAM[0].EmcEmrsDdr2OcdCalib = 0x00000000;
SDRAM[0].EmcEmrs = 0x00000000;
SDRAM[0].EmcMrw1 = 0x0001008a;
SDRAM[0].EmcMrw2 = 0x00020004;
SDRAM[0].EmcMrw3 = 0x00030002;
SDRAM[0].EmcMrwResetCommand = 0x003f0000;
SDRAM[0].EmcMrwResetNInitWait = 0x0000000a;
SDRAM[0].EmcAdrCfg1 = 0x00060302;
SDRAM[0].EmcAdrCfg = 0x01060302;
SDRAM[0].McEmemCfg = 0x00080000;
SDRAM[0].McLowLatencyConfig = 0x80000003;
SDRAM[0].EmcCfg2 = 0x00000403;
SDRAM[0].EmcCfgDigDll = 0xe0000413;
SDRAM[0].EmcCfgClktrim0 = 0x00000000;
SDRAM[0].EmcCfgClktrim1 = 0x00000000;
SDRAM[0].EmcCfgClktrim2 = 0x00000000;
SDRAM[0].EmcCfg = 0x0001ff00;
SDRAM[0].EmcDbg = 0x01000020;
SDRAM[0].AhbArbitrationXbarCtrl = 0x00010000;
SDRAM[0].EmcDllXformDqs = 0x00000010;
SDRAM[0].EmcDllXformQUse = 0x00000008;
SDRAM[0].WarmBootWait = 0x00000001;
SDRAM[0].EmcCttTermCtrl = 0x00000802;
SDRAM[0].EmcOdtWrite = 0x00000000;
SDRAM[0].EmcOdtRead = 0x00000000;
SDRAM[0].EmcZcalRefCnt = 0x00000000;
SDRAM[0].EmcZcalWaitCnt = 0x0000001b;
SDRAM[0].EmcZcalMrwCmd = 0x000a0056;
SDRAM[0].EmcMrwZqInitDev0 = 0x800a00ff;
SDRAM[0].EmcMrwZqInitDev1 = 0x400a00ff;
SDRAM[0].EmcMrwZqInitWait = 0x00000001;
SDRAM[0].EmcDdr2Wait = 0x00000000;
SDRAM[0].PmcDdrPwr = 0x00000000;
SDRAM[0].ApbMiscGpXm2CfgAPadCtrl = 0x77ffc000;
SDRAM[0].ApbMiscGpXm2CfgCPadCtrl2 = 0x08080040;
SDRAM[0].ApbMiscGpXm2CfgCPadCtrl = 0x77fffff8;
SDRAM[0].ApbMiscGpXm2CfgDPadCtrl2 = 0x00000000;
SDRAM[0].ApbMiscGpXm2CfgDPadCtrl = 0x77fffff8;
SDRAM[0].ApbMiscGpXm2ClkCfgPadCtrl = 0x77ffc000;
SDRAM[0].ApbMiscGpXm2CompPadCtrl = 0x01f1f008;
SDRAM[0].ApbMiscGpXm2VttGenPadCtrl = 0x00005500;

tryin said:
I downloaded bct_dump some time ago, from here, but this is my BCT file:
Version = 0x00020001;
BlockSize = 0x00004000;
PageSize = 0x00000200;
PartitionSize = 0x01000000;
# Bootloader used = 1;
# Bootloaders max = 4;
# BCT size = 4080;
# Hash size = 16;
# Crypto offset = 16;
# Crypto length = 4064;
# Max BCT search blocks = 64;
#
# These values are set by cbootimage using the
# bootloader provided by the Bootloader=...
# configuration option.
#
# Bootloader[0].Version = 0x00000001;
# Bootloader[0].Start block = 288;
# Bootloader[0].Start page = 0;
# Bootloader[0].Length = 891020;
# Bootloader[0].Load address = 0x00108000;
# Bootloader[0].Entry point = 0x00108000;
# Bootloader[0].Attributes = 0x00000004;
DevType[0] = NvBootDevType_Sdmmc;
DeviceParam[0].SdmmcParams.ClockDivider = 0x0000000c;
DeviceParam[0].SdmmcParams.DataWidth = NvBootSdmmcDataWidth_8Bit;
DeviceParam[0].SdmmcParams.MaxPowerClassSupported = 0x00000000;
DevType[1] = NvBootDevType_Sdmmc;
DeviceParam[1].SdmmcParams.ClockDivider = 0x0000000c;
DeviceParam[1].SdmmcParams.DataWidth = NvBootSdmmcDataWidth_8Bit;
DeviceParam[1].SdmmcParams.MaxPowerClassSupported = 0x00000000;
DevType[2] = NvBootDevType_Sdmmc;
DeviceParam[2].SdmmcParams.ClockDivider = 0x0000000c;
DeviceParam[2].SdmmcParams.DataWidth = NvBootSdmmcDataWidth_8Bit;
DeviceParam[2].SdmmcParams.MaxPowerClassSupported = 0x00000000;
DevType[3] = NvBootDevType_Sdmmc;
DeviceParam[3].SdmmcParams.ClockDivider = 0x0000000c;
DeviceParam[3].SdmmcParams.DataWidth = NvBootSdmmcDataWidth_8Bit;
DeviceParam[3].SdmmcParams.MaxPowerClassSupported = 0x00000000;
SDRAM[0].MemoryType = NvBootMemoryType_LpDdr2;
SDRAM[0].PllMChargePumpSetupControl = 0x00000008;
SDRAM[0].PllMLoopFilterSetupControl = 0x00000000;
SDRAM[0].PllMInputDivider = 0x0000000c;
SDRAM[0].PllMFeedbackDivider = 0x00000258;
SDRAM[0].PllMPostDivider = 0x00000000;
SDRAM[0].PllMStableTime = 0x0000012c;
SDRAM[0].EmcClockDivider = 0x00000001;
SDRAM[0].EmcAutoCalInterval = 0x00000000;
SDRAM[0].EmcAutoCalConfig = 0xe0a61111;
SDRAM[0].EmcAutoCalWait = 0x00000000;
SDRAM[0].EmcPinProgramWait = 0x00000000;
SDRAM[0].EmcRc = 0x00000012;
SDRAM[0].EmcRfc = 0x00000027;
SDRAM[0].EmcRas = 0x0000000d;
SDRAM[0].EmcRp = 0x00000006;
SDRAM[0].EmcR2w = 0x00000007;
SDRAM[0].EmcW2r = 0x00000005;
SDRAM[0].EmcR2p = 0x00000003;
SDRAM[0].EmcW2p = 0x0000000b;
SDRAM[0].EmcRrd = 0x00000003;
SDRAM[0].EmcRdRcd = 0x00000006;
SDRAM[0].EmcWrRcd = 0x00000006;
SDRAM[0].EmcRext = 0x00000003;
SDRAM[0].EmcWdv = 0x00000003;
SDRAM[0].EmcQUseExtra = 0x00000006;
SDRAM[0].EmcQUse = 0x00000007;
SDRAM[0].EmcQRst = 0x00000004;
SDRAM[0].EmcQSafe = 0x00000009;
SDRAM[0].EmcRdv = 0x0000000d;
SDRAM[0].EmcRefresh = 0x0000045f;
SDRAM[0].EmcBurstRefreshNum = 0x00000000;
SDRAM[0].EmcPdEx2Wr = 0x00000004;
SDRAM[0].EmcPdEx2Rd = 0x00000004;
SDRAM[0].EmcPChg2Pden = 0x00000006;
SDRAM[0].EmcAct2Pden = 0x00000008;
SDRAM[0].EmcAr2Pden = 0x00000001;
SDRAM[0].EmcRw2Pden = 0x0000000f;
SDRAM[0].EmcTxsr = 0x0000002a;
SDRAM[0].EmcTcke = 0x00000003;
SDRAM[0].EmcTfaw = 0x0000000f;
SDRAM[0].EmcTrpab = 0x00000007;
SDRAM[0].EmcTClkStable = 0x00000007;
SDRAM[0].EmcTClkStop = 0x00000002;
SDRAM[0].EmcTRefBw = 0x000004e0;
SDRAM[0].EmcFbioCfg1 = 0x00000000;
SDRAM[0].EmcFbioDqsibDlyMsb = 0x00000000;
SDRAM[0].EmcFbioDqsibDly = 0x34343434;
SDRAM[0].EmcFbioQuseDlyMsb = 0x00000000;
SDRAM[0].EmcFbioQuseDly = 0x00000000;
SDRAM[0].EmcFbioCfg5 = 0x00000282;
SDRAM[0].EmcFbioCfg6 = 0x00000002;
SDRAM[0].EmcFbioSpare = 0x00000000;
SDRAM[0].EmcMrsResetDllWait = 0x00000000;
SDRAM[0].EmcMrsResetDll = 0x00000000;
SDRAM[0].EmcMrsDdr2DllReset = 0x00000000;
SDRAM[0].EmcMrs = 0x00000000;
SDRAM[0].EmcEmrsEmr2 = 0x00000000;
SDRAM[0].EmcEmrsEmr3 = 0x00000000;
SDRAM[0].EmcEmrsDdr2DllEnable = 0x00000000;
SDRAM[0].EmcEmrsDdr2OcdCalib = 0x00000000;
SDRAM[0].EmcEmrs = 0x00000000;
SDRAM[0].EmcMrw1 = 0x0001008a;
SDRAM[0].EmcMrw2 = 0x00020004;
SDRAM[0].EmcMrw3 = 0x00030002;
SDRAM[0].EmcMrwResetCommand = 0x003f0000;
SDRAM[0].EmcMrwResetNInitWait = 0x0000000a;
SDRAM[0].EmcAdrCfg1 = 0x00060302;
SDRAM[0].EmcAdrCfg = 0x01060302;
SDRAM[0].McEmemCfg = 0x00080000;
SDRAM[0].McLowLatencyConfig = 0x80000003;
SDRAM[0].EmcCfg2 = 0x00000403;
SDRAM[0].EmcCfgDigDll = 0xe0000413;
SDRAM[0].EmcCfgClktrim0 = 0x00000000;
SDRAM[0].EmcCfgClktrim1 = 0x00000000;
SDRAM[0].EmcCfgClktrim2 = 0x00000000;
SDRAM[0].EmcCfg = 0x0001ff00;
SDRAM[0].EmcDbg = 0x01000020;
SDRAM[0].AhbArbitrationXbarCtrl = 0x00010000;
SDRAM[0].EmcDllXformDqs = 0x00000010;
SDRAM[0].EmcDllXformQUse = 0x00000008;
SDRAM[0].WarmBootWait = 0x00000001;
SDRAM[0].EmcCttTermCtrl = 0x00000802;
SDRAM[0].EmcOdtWrite = 0x00000000;
SDRAM[0].EmcOdtRead = 0x00000000;
SDRAM[0].EmcZcalRefCnt = 0x00000000;
SDRAM[0].EmcZcalWaitCnt = 0x0000001b;
SDRAM[0].EmcZcalMrwCmd = 0x000a0056;
SDRAM[0].EmcMrwZqInitDev0 = 0x800a00ff;
SDRAM[0].EmcMrwZqInitDev1 = 0x400a00ff;
SDRAM[0].EmcMrwZqInitWait = 0x00000001;
SDRAM[0].EmcDdr2Wait = 0x00000000;
SDRAM[0].PmcDdrPwr = 0x00000000;
SDRAM[0].ApbMiscGpXm2CfgAPadCtrl = 0x77ffc000;
SDRAM[0].ApbMiscGpXm2CfgCPadCtrl2 = 0x08080040;
SDRAM[0].ApbMiscGpXm2CfgCPadCtrl = 0x77fffff8;
SDRAM[0].ApbMiscGpXm2CfgDPadCtrl2 = 0x00000000;
SDRAM[0].ApbMiscGpXm2CfgDPadCtrl = 0x77fffff8;
SDRAM[0].ApbMiscGpXm2ClkCfgPadCtrl = 0x77ffc000;
SDRAM[0].ApbMiscGpXm2CompPadCtrl = 0x01f1f008;
SDRAM[0].ApbMiscGpXm2VttGenPadCtrl = 0x00005500;
Click to expand...
Click to collapse
I tested the cbootimg you sent. It does not show OdmData line for me too, but the cbootimg from the nvidia git site shows it.

bitdomo said:
I tested the cbootimg you sent. It does not show OdmData line for me too, but the cbootimg from the nvidia git site shows it.
Click to expand...
Click to collapse
Many thanks for your test, I'll try the nvidia one when i have a minute...

dear bitdomo,
My phone too stuck on logo LG. I try extracting KDZ su880 rom. I have got img files. ( recovery.img, bootloader.img...)
I want to flash them via NVflash but i dont know command... Can you help me command to flash recovery.img & bootloadet.img ?
*my bootloader.img was extracted from su880 KDZ , i think no need EDIT with HEX Editor & delete the bunch of FF hex values from the end of the file.
i try using bootloader.bin in bootloader_installer ultility. Run install_gb_bootloader.bat. Seem all was complete. But cannot connect to S/W mode
Thanks !

Copy every img file to your nvflash folder (bootloader.img, recovery.img, boot.img (kernel) )
Open a cmd.
Go to your nvflash folder in cmd.
Connect phone in APX mode to PC
Type these commands in cmd:
Code:
nvflash.exe --bl bootloader.img --download 4 bootloader.img
nvflash.exe -r --download 6 recovery.img
nvflash.exe -r --download 12 boot.img
nvflash.exe -r --go
(-r = --resume)
Wait until the screen goes off or wait 15-20 seconds then unplug your phone.
If the sending bootloader hangs up at some point then delete the FF hex valuess from the end of the bootloader.img and try again.
You can find a bootloader in my attachment of this post which already has FF hex values removed.

bitdomo said:
Copy every img file to your nvflash folder (bootloader.img, recovery.img, boot.img (kernel) )
Open a cmd.
Go to your nvflash folder in cmd.
Connect phone in APX mode to PC
Type these commands in cmd:
Code:
nvflash.exe --bl bootloader.img --download 4 bootloader.img
nvflash.exe -r --download 6 recovery.img
nvflash.exe -r --download 12 boot.img
nvflash.exe -r --go
(-r = --resume)
Wait until the screen goes off or wait 15-20 seconds then unplug your phone.
If the sending bootloader hangs up at some point then delete the FF hex valuess from the end of the bootloader.img and try again.
You can find a bootloader in my attachment of this post which already has FF hex values removed.
Click to expand...
Click to collapse
There are no words to show my gratitude! I reallythrilling now. My phone was rescued, my friend !

Seem Those commands not working with imgs extract from v19c, bitdomo ? I flash v19c KDZ via MartFlash---> Root---> Install Recovery ( but failed )----> Phone stuck logo LG...
I cannot flash bootloader.img,although i delete the FF hex valuess from the end of the bootloader.img.

I am a bit lost. To make things clear please anwser these questions:
1. If I understand well you were able to unbrick your phone with the instruction I wrote to you. Right?
2. What recovery do you want to flash and how? Send me a link for that recovery or the app which flashes the recovery.
3. Can you post here what error message appears when you try to nvflash bootloader? Copy the content of the whole cmd window here, please.
There is a final version of ics rom v20c for su880. v19c is a beta rom if I am not mistaken. I can send you a link if you are intrested in v20c
Edit: v19c is an ics rom and ics rom has locked bootloader therefore it cannot be used with nvflash. You have to use the bootloader from my attachment to flash v19c bootloader.
nvflash.exe --bl mybootloader.img --download 4 v19cbootloader.img
Sent from my LG-P990 using xda app-developers app

bitdomo said:
I am a bit lost. To make things clear please anwser these questions:
...
Click to expand...
Click to collapse
Thanks for help, bitdomo !
1. I unbricked phone with the instruction you wrote , in the previous with v10m kdz. Then I reflash with v19c KDZ & install recovery ( below tut) , Phone brick.
2. I want to install any recovery to flash a custom rom (Jelly Bean). And i folow this link: http://forum.xda-developers.com/showthread.php?t=2281636
3. cmd window when i flash booloader & recovery img file with the contruction you wrote ( with img files extract from v19c kdz )---> view attachment picture.
4. I use the bootloader from your attachment with edit in BAT file [ nvflash.exe --bl mybootloader.img --download 4 v19cbootloader.img ],then run new BAT file, a cmd window appear in the moment ( about 1/3 second) and disappear. nothing is happend...
If v19c cannot be used with nvflash, can you creat BAT file to run & flash stock recovery v19c ?

picture cmd window