GSM Shop GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > Product Support Sections > Hard/Software Products (official support) > Octopus/Octoplus > Octopus Samsung/Octoplus Samsung


Closed Thread
 
LinkBack Thread Tools Display Modes
Old 10-29-2014, 08:01   #31 (permalink)
Product Supporter
 
Octopus box's Avatar
 
Join Date: Oct 2009
Location: Romania, Bucharest
Posts: 99,797
Member: 1146942
Status: Offline
Sonork: 100.1587278
Thanks Meter: 27,405

Please look here: http://forum.gsmhosting.com/vbb/f684...olved-1873400/.
 
Old 10-29-2014, 08:44   #32 (permalink)
Freak Poster
 
ralel's Avatar
 
Join Date: Dec 2006
Location: Philippines
Posts: 461
Member: 405730
Status: Offline
Thanks Meter: 184
Quote:
Octopus box
that thread is for WIN 7 only..

not for xp..
 
Old 10-29-2014, 08:51   #33 (permalink)
Freak Poster
 
Join Date: Mar 2011
Location: Dallas
Posts: 331
Member: 1543792
Status: Offline
Sonork: N/A
Thanks Meter: 12
Look it seems this is happening with all unofficial FTDI chips. Look at the device manager for the chip and look to see if the Product ID is all 0000.

http://imageshack.com/a/img674/1452/rosyww.png

If it is either of those the latest FTDI driver update has screwed the chip up and rewritten the product ID so the drivers do not recognise the software. You must install a serial to usb driver and then rewrite the product id with a EPT back up.

Read about it here.
http://forum.gsmhosting.com/vbb/f452...wered-1866322/
 
Old 10-29-2014, 09:03   #34 (permalink)
Freak Poster
 
Join Date: Mar 2011
Location: Dallas
Posts: 331
Member: 1543792
Status: Offline
Sonork: N/A
Thanks Meter: 12
And do not use or update to the latest FTDI drivers because that's what kills the PID.
 
Old 10-29-2014, 09:33   #35 (permalink)
No Life Poster
 
shoaibrao's Avatar
 
Join Date: Dec 2006
Location: GSM WORLD
Posts: 3,295
Member: 412843
Status: Offline
Sonork: 100.1604902
Thanks Meter: 497
Donate money to this user
@Octopus box And Team
Plz Discover Any Solution For Us As Infinity Box And SPT Box
And Worked On Windows 8/8.1 Is Not Feasible For Us
Because Only For One Box We Have To Get An Other PC With Windows 8/8.1
Thanks Anticipation
 
Old 10-29-2014, 15:23   #36 (permalink)
Freak Poster
 
Join Date: Oct 2014
Posts: 160
Member: 2277451
Status: Offline
Thanks Meter: 18
Quote:
Originally Posted by shoaibrao View Post
@Octopus box And Team
Plz Discover Any Solution For Us As Infinity Box And SPT Box
And Worked On Windows 8/8.1 Is Not Feasible For Us
Because Only For One Box We Have To Get An Other PC With Windows 8/8.1
Thanks Anticipation
For win 8.x go here http://forum.gsmhosting.com/vbb/f684...ndows-1871180/
 
Old 10-30-2014, 03:11   #37 (permalink)
Freak Poster
 
bettsy's Avatar
 
Join Date: Feb 2004
Age: 47
Posts: 295
Member: 53422
Status: Offline
Thanks Meter: 20
I have had success in simply changing the PID in the ftdibus.inf and ftdiport.inf files


download from ftdi
CDM v2.10.00 WHQL Certified.exe

extract with winrar


Open your device manager - right click the device in question. goto hardware ids:
VID_0403&PID_0000

open your ini files in notepad and replace the one of the pids with your pid.

find and replace all

save ini

use amended driver info

has worked for me on a number of other devices.


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXX
ftdibus.ini:

; FTDIBUS.INF
;
; Copyright © 2000-2014 Future Technology Devices International Limited
;
; USB serial converter driver installation file for Windows 2000, XP, Server 2003, Vista, Server 2008,
; Windows 7, Server 2008 R2 and Windows 8 (x86 and x64).
;
;
; THIS SOFTWARE IS PROVIDED BY FUTURE TECHNOLOGY DEVICES INTERNATIONAL LIMITED ``AS IS'' AND ANY EXPRESS
; OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
; FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL FUTURE TECHNOLOGY DEVICES INTERNATIONAL LIMITED
; BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
; BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
; INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
; (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
; THE POSSIBILITY OF SUCH DAMAGE.

; FTDI DRIVERS MAY BE USED ONLY IN CONJUNCTION WITH PRODUCTS BASED ON FTDI PARTS.

; FTDI DRIVERS MAY BE DISTRIBUTED IN ANY FORM AS LONG AS LICENSE INFORMATION IS NOT MODIFIED.

; IF A CUSTOM VENDOR ID AND/OR PRODUCT ID OR DESCRIPTION STRING ARE USED, IT IS THE RESPONSIBILITY OF
; THE PRODUCT MANUFACTURER TO MAINTAIN ANY CHANGES AND SUBSEQUENT WHQL RE-CERTIFICATION AS A RESULT OF
; MAKING THESE CHANGES.
;


[Version]
Signature="$Windows NT$"
DriverPackageType=PlugAndPlay
DriverPackageDisplayName=%DESC%
Class=USB
ClassGUID={36fc9e60-c465-11cf-8056-444553540000}
Provider=%FTDI%
CatalogFile=ftdibus.cat
DriverVer=01/27/2014,2.10.00

[SourceDisksNames]
1=%DriversDisk%,,,

[SourceDisksFiles]
ftdibus.sys = 1,i386
ftbusui.dll = 1,i386
ftd2xx.dll = 1,i386
FTLang.Dll = 1,i386

[SourceDisksFiles.amd64]
ftdibus.sys = 1,amd64
ftbusui.dll = 1,amd64
ftd2xx64.dll = 1,amd64
ftd2xx.dll = 1,i386
FTLang.Dll = 1,amd64

[DestinationDirs]
FtdiBus.NT.Copy = 10,system32\drivers
FtdiBus.NT.Copy2 = 10,system32
FtdiBus.NTamd64.Copy = 10,system32\drivers
FtdiBus.NTamd64.Copy2 = 10,system32
FtdiBus.NTamd64.Copy3 = 10,syswow64


[Manufacturer]
%Ftdi%=FtdiHw,NTamd64

[FtdiHw]
%USB\VID_0403&PID_0000.DeviceDesc%=FtdiBus.NT,USB\ VID_0403&PID_0000
%USB\VID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.N T,USB\VID_0403&PID_6010&MI_00
%USB\VID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.N T,USB\VID_0403&PID_6010&MI_01
%USB\VID_0403&PID_6011&MI_00.DeviceDesc%=FtdiBus.N T,USB\VID_0403&PID_6011&MI_00
%USB\VID_0403&PID_6011&MI_01.DeviceDesc%=FtdiBus.N T,USB\VID_0403&PID_6011&MI_01
%USB\VID_0403&PID_6011&MI_02.DeviceDesc%=FtdiBus.N T,USB\VID_0403&PID_6011&MI_02
%USB\VID_0403&PID_6011&MI_03.DeviceDesc%=FtdiBus.N T,USB\VID_0403&PID_6011&MI_03
%USB\VID_0403&PID_6014.DeviceDesc%=FtdiBus.NT,USB\ VID_0403&PID_6014
%USB\VID_0403&PID_6015.DeviceDesc%=FtdiBus.NT,USB\ VID_0403&PID_6015

[FtdiHw.NTamd64]
%USB\VID_0403&PID_0000.DeviceDesc%=FtdiBus.NTamd64 ,USB\VID_0403&PID_0000
%USB\VID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.N Tamd64,USB\VID_0403&PID_6010&MI_00
%USB\VID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.N Tamd64,USB\VID_0403&PID_6010&MI_01
%USB\VID_0403&PID_6011&MI_00.DeviceDesc%=FtdiBus.N Tamd64,USB\VID_0403&PID_6011&MI_00
%USB\VID_0403&PID_6011&MI_01.DeviceDesc%=FtdiBus.N Tamd64,USB\VID_0403&PID_6011&MI_01
%USB\VID_0403&PID_6011&MI_02.DeviceDesc%=FtdiBus.N Tamd64,USB\VID_0403&PID_6011&MI_02
%USB\VID_0403&PID_6011&MI_03.DeviceDesc%=FtdiBus.N Tamd64,USB\VID_0403&PID_6011&MI_03
%USB\VID_0403&PID_6014.DeviceDesc%=FtdiBus.NTamd64 ,USB\VID_0403&PID_6014
%USB\VID_0403&PID_6015.DeviceDesc%=FtdiBus.NTamd64 ,USB\VID_0403&PID_6015

[ControlFlags]
ExcludeFromSelect=*

[FtdiBus.NT]
CopyFiles=FtdiBus.NT.Copy,FtdiBus.NT.Copy2
AddReg=FtdiBus.NT.AddReg

[FtdiBus.NTamd64]
CopyFiles=FtdiBus.NTamd64.Copy,FtdiBus.NTamd64.Cop y2,FtdiBus.NTamd64.Copy3
AddReg=FtdiBus.NT.AddReg

[FtdiBus.NT.Services]
AddService = FTDIBUS, 0x00000002, FtdiBus.NT.AddService

[FtdiBus.NTamd64.Services]
AddService = FTDIBUS, 0x00000002, FtdiBus.NT.AddService

[FtdiBus.NT.AddService]
DisplayName = %SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\system32\drivers\ftdibus.sys
LoadOrderGroup = Base
AddReg = FtdiBus.NT.AddService.AddReg

[FtdiBus.NT.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,ftdibus.sys
HKR,,EnumPropPages32,,"ftbusui.dll,FTBUSUIPropPage Provider"

[FtdiBus.NT.AddService.AddReg]
;HKR,Parameters,"LocIds",1,31,00,00,00,32,00,00,00 ,00
;HKR,Parameters,"RetryResetCount",0x10001,50


[FtdiBus.NT.Copy]
ftdibus.sys

[FtdiBus.NT.Copy2]
ftbusui.dll
ftd2xx.dll
FTLang.dll

[FtdiBus.NTamd64.Copy]
ftdibus.sys

[FtdiBus.NTamd64.Copy2]
ftbusui.dll
ftd2xx.dll,ftd2xx64.dll
FTLang.dll

[FtdiBus.NTamd64.Copy3]
ftd2xx.dll

[Strings]
Ftdi="FTDI"
DESC="CDM Driver Package - Bus/D2XX Driver"
DriversDisk="FTDI USB Drivers Disk"
USB\VID_0403&PID_0000.DeviceDesc="USB Serial Converter"
USB\VID_0403&PID_6010&MI_00.DeviceDesc="USB Serial Converter A"
USB\VID_0403&PID_6010&MI_01.DeviceDesc="USB Serial Converter B"
USB\VID_0403&PID_6011&MI_00.DeviceDesc="USB Serial Converter A"
USB\VID_0403&PID_6011&MI_01.DeviceDesc="USB Serial Converter B"
USB\VID_0403&PID_6011&MI_02.DeviceDesc="USB Serial Converter C"
USB\VID_0403&PID_6011&MI_03.DeviceDesc="USB Serial Converter D"
USB\VID_0403&PID_6014.DeviceDesc="USB Serial Converter"
USB\VID_0403&PID_6015.DeviceDesc="USB Serial Converter"
SvcDesc="USB Serial Converter Driver"
ClassName="USB"


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXX
ftdiport.ini

; FTDIPORT.INF
;
; Copyright © 2000-2014 Future Technology Devices International Limited
;
; USB serial port driver installation file for Windows 2000, XP, Server 2003, Vista, Server 2008,
; Windows 7, Server 2008 R2 and Windows 8 (x86 and x64).
;
;
; THIS SOFTWARE IS PROVIDED BY FUTURE TECHNOLOGY DEVICES INTERNATIONAL LIMITED ``AS IS'' AND ANY EXPRESS
; OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
; FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL FUTURE TECHNOLOGY DEVICES INTERNATIONAL LIMITED
; BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
; BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
; INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
; (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
; THE POSSIBILITY OF SUCH DAMAGE.

; FTDI DRIVERS MAY BE USED ONLY IN CONJUNCTION WITH PRODUCTS BASED ON FTDI PARTS.

; FTDI DRIVERS MAY BE DISTRIBUTED IN ANY FORM AS LONG AS LICENSE INFORMATION IS NOT MODIFIED.

; IF A CUSTOM VENDOR ID AND/OR PRODUCT ID OR DESCRIPTION STRING ARE USED, IT IS THE RESPONSIBILITY OF
; THE PRODUCT MANUFACTURER TO MAINTAIN ANY CHANGES AND SUBSEQUENT WHQL RE-CERTIFICATION AS A RESULT OF
; MAKING THESE CHANGES.
;


[Version]
Signature="$Windows NT$"
DriverPackageType=PlugAndPlay
DriverPackageDisplayName=%DESC%
Class=Ports
ClassGUID={4d36e978-e325-11ce-bfc1-08002be10318}
Provider=%FTDI%
CatalogFile=ftdiport.cat
DriverVer=01/27/2014,2.10.00

[SourceDisksNames]
1=%DriversDisk%,,,

[SourceDisksFiles]
ftser2k.sys=1,i386
ftserui2.dll=1,i386
ftcserco.dll = 1,i386

[SourceDisksFiles.amd64]
ftser2k.sys=1,amd64
ftserui2.dll=1,amd64
ftcserco.dll = 1,amd64

[DestinationDirs]
FtdiPort.NT.Copy=10,system32\drivers
FtdiPort.NT.CopyUI=10,system32
FtdiPort.NT.CopyCoInst=10,system32

[ControlFlags]
ExcludeFromSelect=*

[Manufacturer]
%FTDI%=FtdiHw,NTamd64

[FtdiHw]
%VID_0403&PID_0000.DeviceDesc%=FtdiPort.NT,FTDIBUS \COMPORT&VID_0403&PID_0000
%VID_0403&PID_6010.DeviceDesc%=FtdiPort.NT,FTDIBUS \COMPORT&VID_0403&PID_6010
%VID_0403&PID_6011.DeviceDesc%=FtdiPort.NT,FTDIBUS \COMPORT&VID_0403&PID_6011
%VID_0403&PID_6014.DeviceDesc%=FtdiPort.NT,FTDIBUS \COMPORT&VID_0403&PID_6014
%VID_0403&PID_6015.DeviceDesc%=FtdiPort.NT,FTDIBUS \COMPORT&VID_0403&PID_6015

[FtdiHw.NTamd64]
%VID_0403&PID_0000.DeviceDesc%=FtdiPort.NTamd64,FT DIBUS\COMPORT&VID_0403&PID_0000
%VID_0403&PID_6010.DeviceDesc%=FtdiPort.NTamd64,FT DIBUS\COMPORT&VID_0403&PID_6010
%VID_0403&PID_6011.DeviceDesc%=FtdiPort.NTamd64,FT DIBUS\COMPORT&VID_0403&PID_6011
%VID_0403&PID_6014.DeviceDesc%=FtdiPort.NTamd64,FT DIBUS\COMPORT&VID_0403&PID_6014
%VID_0403&PID_6015.DeviceDesc%=FtdiPort.NTamd64,FT DIBUS\COMPORT&VID_0403&PID_6015

[FtdiPort.NT.AddService]
DisplayName = %SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\system32\drivers\ftser2k.sys
LoadOrderGroup = Base


; -------------- Serenum Driver install section
[SerEnum_AddService]
DisplayName = %SerEnum.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %12%\serenum.sys
LoadOrderGroup = PNP Filter

[FtdiPort.NT.AddReg]
HKR,,EnumPropPages32,,"ftserui2.dll,SerialPortProp PageProvider"

[FtdiPort.NT.Copy]
ftser2k.sys

[FtdiPort.NT.CopyUI]
ftserui2.dll

[FtdiPort.NT.CopyCoInst]
ftcserco.dll

[FtdiPort.NT]
CopyFiles=FtdiPort.NT.Copy,FtdiPort.NT.CopyUI
AddReg=FtdiPort.NT.AddReg

[FtdiPort.NTamd64]
CopyFiles=FtdiPort.NT.Copy,FtdiPort.NT.CopyUI
AddReg=FtdiPort.NT.AddReg

[FtdiPort.NT.HW]
AddReg=FtdiPort.NT.HW.AddReg

[FtdiPort.NTamd64.HW]
AddReg=FtdiPort.NT.HW.AddReg


[FtdiPort.NT.Services]
AddService = FTSER2K, 0x00000002, FtdiPort.NT.AddService
AddService = Serenum,,SerEnum_AddService
DelService = FTSERIAL

[FtdiPort.NTamd64.Services]
AddService = FTSER2K, 0x00000002, FtdiPort.NT.AddService
AddService = Serenum,,SerEnum_AddService
DelService = FTSERIAL


[FtdiPort.NT.HW.AddReg]
HKR,,"UpperFilters",0x00010000,"serenum"
HKR,,"ConfigData",1,11,00,3F,3F,10,27,00,00,88,13, 00,00,C4,09,00,00,E2,04,00,00,71,02,00,00,38,41,00 ,00,9C,80,00,00,4E,C0,00,00,34,00,00,00,1A,00,00,0 0,0D,00,00,00,06,40,00,00,03,80,00,00,00,00,00,00, D0,80,00,00
HKR,,"MinReadTimeout",0x00010001,0
HKR,,"MinWriteTimeout",0x00010001,0
HKR,,"LatencyTimer",0x00010001,16


[FtdiPort.NT.CoInstallers]
AddReg=FtdiPort.NT.CoInstallers.AddReg
CopyFiles=FtdiPort.NT.CopyCoInst

[FtdiPort.NTamd64.CoInstallers]
AddReg=FtdiPort.NT.CoInstallers.AddReg
CopyFiles=FtdiPort.NT.CopyCoInst

[FtdiPort.NT.CoInstallers.AddReg]
HKR,,CoInstallers32,0x00010000,"ftcserco.Dll,FTCSE RCoInstaller"


;---------------------------------------------------------------;

[Strings]
FTDI="FTDI"
DESC="CDM Driver Package - VCP Driver"
DriversDisk="FTDI USB Drivers Disk"
PortsClassName = "Ports (COM & LPT)"
VID_0403&PID_0000.DeviceDesc="USB Serial Port"
VID_0403&PID_6010.DeviceDesc="USB Serial Port"
VID_0403&PID_6011.DeviceDesc="USB Serial Port"
VID_0403&PID_6014.DeviceDesc="USB Serial Port"
VID_0403&PID_6015.DeviceDesc="USB Serial Port"
SvcDesc="USB Serial Port Driver"
SerEnum.SvcDesc="Serenum Filter Driver"


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXX




It's worth a shot for you guys!
 
Old 10-30-2014, 03:12   #38 (permalink)
Freak Poster
 
bettsy's Avatar
 
Join Date: Feb 2004
Age: 47
Posts: 295
Member: 53422
Status: Offline
Thanks Meter: 20
http://www.ftdichip.com/Drivers/CDM/...0Certified.exe
 
Old 10-30-2014, 03:34   #39 (permalink)
Freak Poster
 
bettsy's Avatar
 
Join Date: Feb 2004
Age: 47
Posts: 295
Member: 53422
Status: Offline
Thanks Meter: 20
http://www.filedropper.com/ftdipid0000

Can someone try this and post result?
 
Old 10-30-2014, 05:35   #40 (permalink)
No Life Poster
 
gsmnitinmobile's Avatar
 
Join Date: Jun 2011
Location: sonu
Posts: 660
Member: 1595511
Status: Offline
Sonork: nnn
Thanks Meter: 121
CDM 2.08.28 WHQL Certified - Download - 4shared

nitin mobile
 
Old 10-30-2014, 08:27   #41 (permalink)
No Life Poster
 
shoaibrao's Avatar
 
Join Date: Dec 2006
Location: GSM WORLD
Posts: 3,295
Member: 412843
Status: Offline
Sonork: 100.1604902
Thanks Meter: 497
Donate money to this user
My Box PID Is

USB\VID_0403&PID_0000\A9GN755H

Can You Make INF File For Me?
I Am Using Windows XP 32 Bit SP3
Thanks Anticipation
 
Old 10-30-2014, 08:38   #42 (permalink)
Freak Poster
 
ralel's Avatar
 
Join Date: Dec 2006
Location: Philippines
Posts: 461
Member: 405730
Status: Offline
Thanks Meter: 184
somehow i still managed to flash lower level of samsung phone using JAF BOA as an interface



hope this team to work for this essue.
 
Old 10-30-2014, 09:14   #43 (permalink)
Freak Poster
 
ralel's Avatar
 
Join Date: Dec 2006
Location: Philippines
Posts: 461
Member: 405730
Status: Offline
Thanks Meter: 184
Quote:
bettsy
Quote:
http://www.filedropper.com/ftdipid0000

Can someone try this and post result?

this solution really worked for me

you solved my long long time problem LOL!

 
Old 10-30-2014, 09:31   #44 (permalink)
No Life Poster
 
shoaibrao's Avatar
 
Join Date: Dec 2006
Location: GSM WORLD
Posts: 3,295
Member: 412843
Status: Offline
Sonork: 100.1604902
Thanks Meter: 497
Donate money to this user
Quote:
Originally Posted by shoaibrao View Post
My Box PID Is

USB\VID_0403&PID_0000\A9GN755H

Can You Make INF File For Me?
I Am Using Windows XP 32 Bit SP3
Thanks Anticipation
Plz Help For PID Plz.............
 
Old 10-30-2014, 09:47   #45 (permalink)
Freak Poster
 
Join Date: Mar 2011
Location: Dallas
Posts: 331
Member: 1543792
Status: Offline
Sonork: N/A
Thanks Meter: 12
Quote:
Originally Posted by shoaibrao View Post
Plz Help For PID Plz.............
You either mod the inf file to accept the 0000 PID or change the PID of your box. The info is on here please read and do it.
 
Closed Thread

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 



All times are GMT +1. The time now is 07:17.



Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.23578 seconds with 8 queries

SEO by vBSEO