Jump to content
AVIC411.com

Condi's HACKMODE v2.2 - AUTOINSTALL! working also with F40BT, X940BT etc! [updated: 27.09.2012]


Recommended Posts

No offence taken and im cool. It's just the matter of taking a generalized question and turning it technical. The handbrake ground is certainly not the issue. Its got the bypass applied and yes I can watch movies it a 130bt. Its not options being grey'd out. They are available but just wont execute

Link to post
Share on other sites
  • Replies 1.2k
  • Created
  • Last Reply

Top Posters In This Topic

Sorry not going to retype everything I already said

I've checked my X930BT with V1.4 of hackmode - it starts to play from same source and same spot where it was shut off (i've used SD and DVD full of mp3s.

I suggest you to put everything back from your backup and check it, then put v1.4 hack again- and check it again.

Link to post
Share on other sites

Those pics are off a x930bt. I've been looking at the copies of sirfflash and sirfsocmgr that I have. Neither one supports the spansion model in the x930bt but it looks easy to add from the sirfflash manual.

 

To support additional flash types:

1. Obtain the device code (ID), manufacturer code (ID), capacity, and sector map

information for the intended flash type. This information is typically available from

the flash data sheet.

2. Using a text editor, open the CHIPLIST.TXT file.

3. Using the same format that is already in the file, add the device name, manufacturer

name, device code, manufacturer code, capacity and sector map information, and

the driver file name at the bottom of the existing list.

The driver file name must be GENERIC.BIN.

4. Follow the steps detailed in “Downloading Software using SiRFflash” on page 5-1.

Link to post
Share on other sites

Hi guys,

 

I'm currently also looking for a solution to mod the PRG files without the risk of bricking. The coredll.dll has to be changed 8)

I bought a f930bt and when i came home I discovered that it was locked with a password. The first thing I did was dumping the following chip:

 

EEPROM

IC1303

S-93C56BD0I-I8

The dump is in the attachment. Maybe it could be usefull. It was an huge challenge to solder to that SMD chip.

After a search I found that I could retreive the password in testmode->file manager. So that problem is gone.

 

Now on the CC monitor unit PCB there is a jtag connector (CN4621). This has the following pinout:

 

1 TMS

2 TDI

3 TDO

4 TCK

5 GNDD

6 ?

7 NTRST (P-NTRST)

8 P-TDI

9 P-TMS

10 P-TCK

11 RTCK (P-RTCK)

12 P-TDO

13 NSRST (P-NSRST)

14 TEST4 (TESTMODE4)

15 JTGRST (JTG_RST)

 

Everything with a P- for it is from the CPU (tt4421).

An interresting thing is the TESTMODE4 pin. Maybe this is just to enter test mode I don't know.

 

If you have a look at http://forum.gps-club.ru/index.php?showtopic=19265 and translate it you will notice that they connect a gps with a simulair cpu to usb.

I found out that the tt4421 cpu has a usb OTG. This means that we can connect it to a computer instead of an peripheral device. This could be a way to flash/restore the nand.

I don't think pioneer will open an avic when it is bricked. There is a way without opening it.

On the russian page you will read that they connect it with a kind of usb to rs232 cable. On PRDM-0028-A4_HowToRepairHW_Nboot.pdf (russian page) I see for beeing able to choose something from the nboot debug message log you need to hold the power and reset buttons. We need to find a way to choose the option 8 so we can start SIRFSoCMgr and dump and update the NK Image.

You can also update the nboot and eboot from this.

 

If all that could not work than we have to look at the JTAG connector. This has TDI, TMS, TCK, TDO, NSRST, NTRST and JTGRST.

eepromdump.zip

Link to post
Share on other sites

I think you should connect the normal external usb connector (the cable that also has the audio jack input) to your computer. This usb connector is the USB1 controller on the tt4421 chip. This controller has a normal pin assignment (positive and negative data pins). See page 261 on the developer manual.

The cn4001 pads is the USB0 controller. This usb0 controller has ULPI interface to connect. I don't know what it is exactly but is has a totally different pin assignment. (see page 232 on the developer manual).

developer manual: http://www.4shared.com/get/ARDbpkFH/CSM-00364_RevC_SiRFprima_Devel.html

Link to post
Share on other sites

ULPI is an industry standard interface for a chip to connect to an external USB PHY (the part of a chip that handles sending and receiving the bits over the cable). You'd have to build some sort of circuit with a transceiver chip, a USB connector and whatever other support circuits to provide required power/config to the transceiver to connect your stuff to USB0. Example: http://www.slscorp.com/products/santacruz-snap-on-board/usb-20-ulpi.html

 

The cn4001 pads is the USB0 controller. This usb0 controller has ULPI interface to connect. I don't know what it is exactly but is has a totally different pin assignment. (see page 232 on the developer manual).

developer manual: http://www.4shared.c...rima_Devel.html

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...



×
×
  • Create New...