You know very little in the Garmin navigation device, may be worth to extend their knowledge?
Printable View
You know very little in the Garmin navigation device, may be worth to extend their knowledge?
orly? Take a good look at this picture. [Only registered and activated users can see links. Click Here To Register...]Quote:
Originally Posted by Alexander2010 [Only registered and activated users can see links. Click Here To Register...]
This is the logic board of the nuvi 205. like I said before: it's basecally a computer. It has an OMAP processor, a nand flash that stores the firmware and maps, a sdram memory module.
"System memory for the processor comes from 32Mbyte of DDR SDRAM from Hynix Semiconductor Inc. for working memory and 2Gbyte of iNAND flash from Sandisk Corp. The latter holds all mapping data and system codes (for download to DDR SDRAM) with the inclusion of a NAND controller to manage the host processor interface. Wear-leveling and error correction along with SD or SPI bus interface formatting are all handled in the controller chip, copackaged with what is almost certainly multilevel-cell (MLC) NAND silicon."
All the units from garmin have basically the same design. They only add more modules (like bluetooth and tv) and more memory, and sometime a bigger screen.)
So don't come here and say I know little about my unit. It's all software based dude. Theres no secret kill switch inside the hardware. Garmin wins money with they software (one of the best available) But even they software is almost the same in all units of the same range, with a few modifications.
If above post has "Dislike" button, definitely I will click it.
I always backup my original "memory" data ( not from mass storage) before converting.
At least I can compare what different is (within memory not mass storage)
Many kind of data stored within memory not mass storage.
For example you will never find Garmin lock code from mass storage.
I bricked my original 2xxx firmware unit just flashed non-important memory region. :banghead:
You have 2 above post. Which author you dislike?:Animated60:Quote:
Originally Posted by albert_chong [Only registered and activated users can see links. Click Here To Register...]
Sure I dislike the one which with less POST.
From his first post "tutorial", he should write "Do it at your own risk !" because he has told that "It's not 100% safe but works", in case someone follow his tutorial and kill the Nuvi.
Of course, he should also write a Thanks to turboccc for using his RGN_tools from the tutorial.
Just my 2 cents.
@cliny
Please don't take this post the wrong way. I am trying to diffuse this, not make it worse. I appreciate that you have a good basic knowledge of your unit and that you feel that you fully understand what's happening when you flash another firmware to it. I know a bit more that most garmin users, but i'm not an expert, and you also described yourself the same way in post #10. What we are in fact is 'enthusiastic amatuers' and maybe the only probable difference between you and i is that i don't have the goanies to try what you did. Not because i don't have the knowledge to do it, i do. It's because i also know that such cross-flashing can all too often result in a brick, sometimes immediately but all too often a little later just when you think it can't and won't happen. And when someone the stature of aekhong, catymag, kunix, Alexander2010 and many others not posted in this thread (lolypop000, ddabcd277 etc, way too many to mention) uses the term brick, they mean it... a pretty looking brick; an interesting paperweight; dead and irrecoverable; kaput. They don't mean 'bricked' the way a friend of mine meant when he asked me to look at his 'bricked' nuvi... it was just stuck on 'loader loading', easily fixed. But to him, it was bricked, and i was a 'guru'... i'm not, and i felt like a fraud, but it was way beyond his understanding both as to what had happened to it, and how i 'fixed' it. These 'gods' are way, way, way more above us mere mortals . They know stuff that we can't appreciate so it's best to just accept what they are saying and be aware that your 1300 may just crash and burn one day without warning, or even brick if you try to flash back to original. You may be lucky and it may never happen, which i hope for your sake. But if you get lucky, it doesn't mean they are wrong, it just means ... that you are lucky! Our good friend dasilvarsa has got away with it in that other thread i referred you too in Post #2, and like you did, he had flashed back and forth with other asian fw before the japanese 1480. Not to say that his 1300 won't still die just out of the blue or if he flashes back to original again... who knows? But he would have known of and acknowledged the risk i'm sure. I have made countless posts warning inexperienced members against cross flashing asian fw onto us/eu units. I'm not saying you are inexperienced, i know that you are experienced just by the very fact you have managed to combine the jap fw with the original 5.80 boot bin successfully. But albert_chong is alsolutely right, we 'mortals' could not do this stuff without the tools invented by the 'gods' in this case, turboccc, another of my 'too many to mention'.
It maybe will put it more into context if i mention something that either Alex or kunix probably will not mention here, and i hope nobody minds me saying this: They have made a fw called 'DeLuxe' which combines elements of asian fw with 13/14xx, it enables routes and mp3 and much more. It's not been done in the 'blunt instrument' way that you and dasilvarsa have done.... it has been done with finese and afaik it has never resulted in a brick, but i don't pretend to understand HOW it's been done, i just accept that it HAS been done (like my friend with the boot loop, you see what i mean?). Info:
It seems neadrenalin also had a hand in it too. Another 'God' imo. It translates understandably enough into English. It probably will also into Portuguese althought your English seems fine.Code:http://www.gps-forum.ru/cgi-bin/forum/showpost.pl?Board=gpsgeneral&Number=122019
Please, please, don't piss these guys off. We need them here. And don't expect them to explain or be offended when they don't. They know that most of us just wouldn't understand anyway, and they would have to show some of their 'trade secrets' to justify to you why your method is risky and their method isn't. We get enough of their knowledge now, free.
You may not like to hear this, but if Alex hadn't replied at post #4, my next question to you was going to be "Do you understand that there are risks in what you have done? And you really should be warning people that it's not totally safe or inexperienced members will blame you if they brick their units". When Alex got involved, there was no need for me so i pulled my head in. You may not like this suggestion either, but i hope you take it in the spirit that it's offered: If i were you i'd now apologise to Alex, kunix and Caty and ask Alex to sell you DeLuxe. If you do, and he will, then i reckon that would be a good outcome.
:)
cliny, big thanks for Nuvi motherboard photo. I see this every week, but for another users this picture is interesting. But this picture is right not for all 1xxx, may be for 7-8 PCB version. Not only SanDisk memory bank can be used, I see Samsung memory at this time at broken Nuvi 1310 on my table:-). Different PMICs, different LCD controllers. Nuvi 1xxx produced in 2009 is not Nuvi 1xxx produced in 2011. And if you have 1 Nuvi - not say about all, please!
@Neil
Not all Asian firmwares can brick US unit for all model series.
1xxx / 2xxx is dangerous but not for 37xx series.
If you seek a "almost never dies" (by ordinary flashing ways) Nuvi you should try 37xx.
If you want to flash across all of Asian firmware you shoud buy 3750.
Ahh.. if only i was as rich as my SEA cousins! Stuck with my 1300 for now, but if i brick it ....? I was going to buy an EU 2585TV, but they seem to have more bugs than a night-time bbq in summer. Maybe a 37xx, if only.... (if wishes were horses, blind beggars would ride). Gotta brick the 1300 first. ;)
