Chevrolet Cruze Forums banner
361 - 380 of 519 Posts
In the United States the pin or resistor definitely need to be desoldered. I tested 4 Chevrolet branded boxes and 1 Buick branded box (incorrectly sold as a Chevrolet Cruze box) and all 5 refused to write to the EEPROM unless the protection was disabled. They use the same radio and ISSI EEPROM in the United Kingdom (although it is branded Daewoo), so most likely would also need the write protection disabled.
Just to throw out another idea - perhaps your burner doesn't have enough drive to overcome the resistor for some reason but wrx5's burner does. I'd think the resistor is just a pull-up. Perhaps 1K ohm at the lowest. That doesn't seem like something that should be a struggle for the burner.
 
Just to throw out another idea - perhaps your burner doesn't have enough drive to overcome the resistor for some reason but wrx5's burner does. I'd think the resistor is just a pull-up. Perhaps 1K ohm at the lowest. That doesn't seem like something that should be a struggle for the burner.
Tried 2 different burners, the second one was the same one wrx5 used. Just to be safe, I even used a "Y" USB cable designed to provide power to a USB device from 2 USB ports. There is always the possibility of a defective one in a batch, but I dont think that is the case here.
 
Tried 2 different burners, the second one was the same one wrx5 used. Just to be safe, I even used a "Y" USB cable designed to provide power to a USB device from 2 USB ports. There is always the possibility of a defective one in a batch, but I dont think that is the case here.
I don't know if that makes a difference or not but I used USB3 port.
 
The Buick and the last Cruze radio came from 2016 vehicles also. Plus, your radio says the same as mine: HW build date 20NOV2014. So, there has been no change to hardware design in over 2 years.
How about chip brand? in the picture you have posted, the brand was ISSI. However, it was different in my case. I am not sure if this makes a difference or not.
 
How about chip brand? in the picture you have posted, the brand was ISSI. However, it was different in my case. I am not sure if this makes a difference or not.
As I said, I do think that is where the difference lies. I can't find any information about the specific chip you have, just the general family. It could be programmed or designed differently.
 
I'm technically on vacation for a couple weeks right now (job hunting), so the mylink project is on the back burner for a while.
Got a new job yesterday, front end parts sales for a private salvage yard here. Didn't tell them why, but when they asked what I was asking for in terms of pay or perks, I asked for first view of all radios pulled from GM vehicles dated 2010 and newer. :)
 
Got a new job yesterday, front end parts sales for a private salvage yard here. Didn't tell them why, but when they asked what I was asking for in terms of pay or perks, I asked for first view of all radios pulled from GM vehicles dated 2010 and newer. :)
Congrats. Sounds like you may have an inside track on radios. :)
 
Can anyone tell me the approximate size of the original image file when you read the VIN chip? Just trying to verify that the image is complete before making any changes as I can consistently get the previous VIN number but the image file size isn't always the same. :(
 
16,384 bytes

I find it odd you'd get different sizes. I'd think the software would pull data until the settings it was given had been cycled though. If it was unable to complete, then it should signal an error. Do you have the right chip type selected?
 
16,384 bytes

I find it odd you'd get different sizes. I'd think the software would pull data until the settings it was given had been cycled though. If it was unable to complete, then it should signal an error. Do you have the right chip type selected?
It was the POS chip reader that was causing the issue. Got a new reader and it has consistently read and written the image without issue. :)

Might open another thread since I am moving on to a separate part of this same project. Moving an image from one style headunit, (in this instance a GMC Terrain Nav), to make it a compatible with the Cruze Nav control panel.

Terrain system works fine but none of the buttons are actually mapped correctly. At least the touch screen works! :)

The Terrain unit even has Text Messaging that my original unit did not even though my Cruze headunit is supposedly "newer", (and I am using the exact same phone)?
 
I recently upgraded my Spark (similar to Cruze) from a standard radio to a Mylink unit. In doing so I had to reprogram the eprom (essentially erased it) to avoid getting the "Locked" message. I got a lot of help in my project from reading this Cruze site and thought it appropriate to publish what I did here in hopes that it might help somebody else in a similar situation.
 
I recently upgraded my Spark (similar to Cruze) from a standard radio to a Mylink unit. In doing so I had to reprogram the eprom (essentially erased it) to avoid getting the "Locked" message. I got a lot of help in my project from reading this Cruze site and thought it appropriate to publish what I did here in hopes that it might help somebody else in a similar situation.
When you say "erased" you mean erase just the VIN or the whole chip?
 
361 - 380 of 519 Posts