Thanks Guys for all your input and help.
Stupid question? Where do I get boot.bin from?
As was said, at least worth a try.
I'm a bit too stubborn to give up by selling for parts, you never know when a cure pops up suddenly!
You have to navigate to get to the good.
[Only registered and activated users can see links. ] Password for my files: gpspower.net
Please don't flood my pm box with questions you can post on forum!! You won't hear back from me.
Galaxy S5 Kitkat 4.4.2 / Nuvi1200->1250 / Nuvi3790T->34xx / Nuvi 2200 / Nuvi 66 / Oregon 600
Thanks Guy's for your perseverence and patience with me - I've built up quite a collection of Garmin tools so far!
For lolypop's info (I can't send PM's yet as I'm still a 'Newbie' or should that be 'Nuvi !?!) - holding the on/off switch left didn't work. I tried holding for a few minutes - no good, same old 'blinking' white screen.
Kunix, you mentioned an update.txt file. It contains:
Is that correct for what I am trying to achieve?
I unzipped the OnSDCard files to a SD card and it created a root folder 'OnSDcard'. Does the size of card matter? I used 512Mb.
Also tried with the Garmin folder and 14.bin in the root - still didn't boot up.
I see ldr.bin is a few folders deeper - should this be in the root?
I would like to try this first before I open the case and risk breaking the ribbon connectors next time!
update.txt file is correct, it rewrites the firmware region with 14.bin. Maybe it's not what you need here (actually, you need to rewrite that wrong bootloader), but it's a safe way to check if ldr.bin is executed.
There should be the following files on the SD card (you can omit update.log):
If it still doesn't work, then I have a few ideas:
1) Maybe the bootloader has another HWID (why else would it brick the device? Can you give me that device-bricking RGN?), so you need the appropriate ldr.bin.
2) On some devices (at least, on 13xx) the bootloader is responsible for initializing LCD controller. White screen means that it's most likely initialized incorrectly. So you won't see anything even if ldr.bin is executed. Try using update.txt with some command inside that creates files, like "rrgn,14,1:/14-1.bin".
Last edited by kunix; 3rd April 2012 at 06:52 PM.
Kunix, I guess you are asking me where I got the firmware from which caused the problem?
I am unable to post links so will have to tell you where it is.
GpsPasSion forum under:
English Forums - Hardware
Garmin nüvi forums
Service firmware .rgn for nuvi 205w/255w/265w
File name fw_nuvi2x5W_ID0827_en_v500+cure.rar
Are you able to dissect and understand what may have happened from the file?
Just to recap, it originally had v6.40 and I sucessfully flashed (holding top left corner of screen) to 6.10 and back to 6.40 before using the v5.00 cure, when it crashed. The original v6's showed the Garmin Logo first then brief white screen and reboot, now just white and for longer (logo bypassed maybe?).
Haven't got any further yet but will try your suggestions in next few days.
Does the SD card need any volume name, or best left blank? I will experiment with some options.
More details in case you need them:
Circuit board v3 code on board 105-01392-03, ID shown as NUVI 2 Series Software 6.40, no waypoints, tracks, almanacs nor routes.
ID 827 (you already know). Do you need the Unit ID (10 digits)?
Last edited by hamgray; 6th April 2012 at 03:30 PM. Reason: wrong information
Well I had a go at the SD boot idea you mentioned but regret no differnce to the symptom.
Tried different commands and also battery disconnected.
However, I did notice when putting the box back together that (as I feared) part of the ribbon cable has broken.
It's the part with 4 connections, there's also a twin strip which looks ok and the multi strand for the display I guess which also looks ok.
I guess I managed to break it when I opened it previously, or do you think this could have been the original problem?
Do you know what these 4 connections do?
How feasible is it to try and solder thin wires to bridge the ends? (I have done soldering before so willing to hava go).
Any ideas now please?
Hi, hamgray, I'm not a hardware guy, so I can't say anything valuable concerning that ribbon.
The cure firmware seems to be ok, but it's very old. I still have an idea that your device is newer that the firmware and, therefore, it's not fully supported. So, maybe the screen is white because the LCD is unknown to the bootloader? Alexander2010 says that he's already seen exactly this problem (2x5W/5.00 cure/white screen), and the devices could still be flashed in pre-boot mode if connected to the PC. But looks like it's not your case, because you don't rely on the picture of the screen while entering pre-boot mode as I understand from the first message from here: [Only registered and activated users can see links. ]
So, we can continue experimenting after you've fixed the ribbon.
Have made one effort to repair the ribbon cable, but not looking good. I can't get to the copper strips easily for soldering.
I have searched the Internet (eBay etc.) and it looks to me that the four wire ribbon could be for the touch screen part. If so, this would explain the loss of touch which I had previously. I would also 'guess' that the 2 connection ribbon may be power and the multi-strand connector is for the display.
I'm begining to think that even if I get the ribbon joined I will still have the softare/firmware problem I started with.
Slowly losing faith and confidence as it probably can't even be used for spares now?
Just a follow-up to say that I soldered the broken ribbon cable (as best I could), carefully put it back together and still have the same problem.
It may be the soldering broke on reassembly, or it has another problem.
I've had enough of it, fortunately was a donation so nothing lost, and it's going in the bin.
I would like to give a BIG thankyou to all those who tried their best to help me out, it was very much appreciated.
This thread can now be closed - thanks.