Are you sure update.txt is re-executed when you re-insert the SD card? Can you test it by issuing something like "copy,1:/1.bin,1:/2.bin"?
Are you sure update.txt is re-executed when you re-insert the SD card? Can you test it by issuing something like "copy,1:/1.bin,1:/2.bin"?
Yes, of course.
because after update.txt is executed, will create 2 files name "Update.log" and "Last_id.bin".
I will deleted both files for the next update.txt.
just now After executed without "reboot" command, now
My bad, its can't be executed update.txt anymore, no any responsive.
Write in update.txt the same command that you have before and write on end command reboot and all will work.
But you must add also update.log on SD,remove only last_id.bin.
Thanks lolypop000,
it's work.
Hi kunix,Quote:
Originally Posted by kunix [Only registered and activated users can see links. Click Here To Register...]
Test "copy,1:/1.bin,1:/2.bin"
1.bin contain 68 61 70 70 79
2.bin contain 62 69 72 74 68 64 61 79
After update.txt is executed
result:
Parsing "copy,1:/1.bin,1:/2.bin"
Success
Parsing "reboot"
Success
1.bin contain 68 61 70 70 79
2.bin contain 68 61 70 70 79
After finished read from page 1 to page 5..i found i dont understand anything about "REGION " as all of you talking like Region 41 or any region,Ha ha ha...but nevermind...will keept reading another post...who knows i will understand it somedays..just sad to know some of Nuvi 255W is bricked...i love the old Nuvis compared to the new 1...
Hmmm ... me to - look like i miss something. Well - i have at me Nuvi 12xx with damaged eMMC IC ( Loader ... freeze after try to cure it, due to erase / write process cannot be done ) - i was take out an working eMMC IC from Nuvi 200 ( with damaged PCB after bad charger ) - and voila - the Nuvi 12xx try to start - well now is time to bring it back to life due to different FW inside the eMMC IC cannot drive LCD, ect ... BUT ... there is BUT - at eMMC is stored different HW ID and Updater not work, also device ID will be different and paid lifetime maps updates will disappear .
There after reading seem i must make an empty SD card with :
root -
- Garmin ->
>-Updater->
>-0971-> ( due to the small beast 12xx was with 0971 HWID ) and inside will be
- ldr.bin ( renamed boot.bin extracted from nuvi12xx_GCDFile__620_971.gcd with RGN_Tool_V084 )
- Update.txt ( with needed comands )
- some more may be ?
and after this - put card in Nuvi 12xx and invoke an preboot mode.
Well - what a command set must be to erase current FW on eMMC, put new one, change HWID stored and original Device ID itself ?
Who can explain?
WBR, DebeliaMark, BG
1) The HWID has changed (use g7towin.exe to determine it), so you would have to use some other folder name, not 0971.
2) Moreover, normal SD card update won't start, as fw_all.bin doesn't start. You need [Only registered and activated users can see links. Click Here To Register...].
3) Moreover, why do you want to use the SD card method when you can put the device into pre-boot mode and use updater.exe?
Just rename the RGN file from 09710100yyyy.rgn to xxxx0100yyy.bin, where xxxx is the HWID in decimal notation.
Thus you would flash the original firmware back.
But it's not going to work immediately, as NV memory is from a different model. You would have to run "ergn,41" from update.txt to erase it.
Actually, I don't like the whole idea of taking a chip from a different model. It shouldn't work at all unless the hardware and CPU boot configuration are very similar on both models.