Have you tried boot.bin + logo.bin ?
I have a weird problem with a 1490T where I am unable to flash boot.bin.
It is stuck in a reboot loop. I got this off of ebay, so I dont know what was done to get it into this state.
- The reboot behavior is just that garmin logo appears for about 5 seconds then reboots. No text displayed at the bottom.
- I can put it into pre-boot fine. PC and updater sees garmin usb device just fine.
- In preboot mode, i verified using g7towin that HW ID is 0972:
"nuvi 14xx Series Software Version 4.10 ID: 972"
- in preboot, i attempt to flash regular stock software, 0972-580.rgn, which has boot.bin, fw1_resources.bin, and fw_all.bin:
-- the first step seems to attempt to put the nuvi into a loader mode, but on this nuvi it goes quickly: "loader loading", reboot, to "software loading..." to "software missing" and sits there for a few seconds
-- on the pc, updater waits for a few seconds, and then goes to "erasing", and then throws up the error "The GARMIN device is unable to program the requested memory region."
-- the unit goes back into it's reboot loop
i have also tried:
- creating cure fw with kunix garmincure3. this works great on other 1490 nuvis i have tried it on, but this one it doesnt work, because it never flashes properly
- multiple other older versions of fw for 14xx (0972). all with similar failed result.
I did more experimenting with rgn_tool and attempting to create my own firmware versions to load.
I noticed that if i just put in fw1_resources.bin and fw_all.bin (with no boot.bin in first section), it seemed to load via webupdater, but that doesnt quite work.
It attempts to flash via webupdater, but didnt seem to do anything on the device (plus it was in Loader Loading... state so i think it was waiting for us to send it a ramloader)
Anyhow, it doesnt seem to want to let me update the boot.bin, cause everytime it's always back to the "nuvi 14xx Series Software Version 4.10 ..." in updater when in pre-boot mode. It wont update to recent boot.bin.
I have recovered several "dead" nuvis, but this one doesnt want to come back... I always thought if we can get it into pre-boot mode, it must be "revivable", right?!
Have you tried boot.bin + logo.bin ?
i'm not sure it is ok to flash mtk firmware. the bootloader claims it has hwid=972, and i would believe it. but anyway, ramloaders from mtk and non-mtk 13xxs have different base addressess, thus flashing the wrong one won't brick the device.
as i remember bootloader always displays "loader loading" while flashing any regions. other captions are displayed by boot.bin. so, nothing unusual here.
zeroj, did we meet at gpspassion.org? if you are zerojj there then you are probably clever enough to create a firmware with an infinite loop at the very beginning and flash it without boot.bin. this way you can check if the device still accepts new firmwares.
also i suggest flashing a firmware with wrong format (for example, with the ending 5a a5 ff ff erased). this is one more way to check if firmware is being really flashed (you should see system software missing).
a few weeks ago i've seen a device with similar "software missing" on this forum. as i remember we didn't recover it.
Last edited by kunix; 9th March 2012 at 19:41.
When i flash to JPN FW with no change to FW i have software missing and hwid change to JPN.
hmmm, it could be...
but then you can't just flash it with boot.bin from mtk device because it just won't run.
1. i tried boot.bin + logo.bin (saved from rgn14.bin of working 1490) - no luck
2. lolypop, im in US - cant download from that sharing site
3. yes same zerojj
4. alexander2010 - i dont have icq but i do have skype or yahoo messenger. i tried replying to your pm, but your box is full
I can always get this back into pre-boot. Seems to be some disagreement here whether I make things worse by trying mtk boot bin.
Maybe this was a MTK device that somebody flashed with us fw and it made it 972 hwid?
Serial number looks similar to other US device that was 972 hwid (starts with 1T).
Anyhow, i probably look at it again tommorow.
I've looked at both boot.bins and I've discovered that the bootloader and the x-loader from MTK boot.bin have totally different loading addressess from non-MTK ones.
So, I don't know how to execute the non-MTK bootloader on a MTK device. At least, it's impossible to do accidentally.
And I don't think someone would do such stupid things intentionally.
So i guess maybe flash or ram is hosed on this unit... Sad...
Hi, it's possibile to share this cure fw garmincure3?
LE: I found in the forum...
Last edited by yo3; 4th April 2012 at 14:58. Reason: wrong