Thanks for the post. Wanted to modify the firmware of your DriveSmart 50 RUS LMT (HWID=2267). To start making a BackUp, but I can not understand what region I use? In the example mentioned 41/154, and that is for me to use?
Printable View
Thanks for the post. Wanted to modify the firmware of your DriveSmart 50 RUS LMT (HWID=2267). To start making a BackUp, but I can not understand what region I use? In the example mentioned 41/154, and that is for me to use?
DriveSmart 50 will be region 152. It has hidden RWFS partition so path to the media card should be "2:/". BTW, HWID 2267 is US/EU firmware version.
Fixed update.txt (from "rrgn,154,2:/154.bin
reboot" to "rrgn,152,2:/152.bin"
reboot). The root of the SD 152.bin does not appear in the update.log (Drive Software Version 5.60, UID: ....., HWID:.....
Parsing "rrgn,152,2:/152.bin"
Error
Parsing "reboot")
As soon as I return to update.txt (rrgn,154,2:/154.bin
reboot)
The root of the SD 154.bin appears in the update.log(Drive Software Version 5.60, UID: ........., HWID: .........
Success
Parsing "reboot")
What's the meaning of that?
It means I'm a goose because i made a typo and didn't check the wording before I posted. Region 154 is correct. Sorry for the confusion.Quote:
Originally Posted by Ver Wolf [Only registered and activated users can see links. Click Here To Register...]
EDIT: Best edit your last post to remove the UID & HWID numbers or some trickster could clone your device.
Thanks Butters!!! And the I already wanted to launch script with all regions 1-200! :)))
There are even more possible regions in a nuvi device, a total of 254 or 255 from memory. However many aren't populated and therefore copy as empty (0 bytes in the BIN file) and some may not even exist as you've already found with 152. Some may even be duplicates of others. You should exclude regions 48 and 83 because one will contain the entire file system, i.e. at least one of those two will be populated and the other will be either empty or a duplicate. Easier to just do a simple copy/paste of the visible files with hidden and system files shown in windows folder options than to have to convert from 48.bin or 83.bin, also it takes a long time to copy large regions to bin file on SD.
Good afternoon . Help! My screen shows and does not write a file.
GARMIN DRIVE 61 <PartNumber>006-B2588-00</PartNumber>
<SoftwareVersion>370</SoftwareVersion>
apdate log = Drive Software Version 3.70, UID: 39591967xx, HWID: 39591967xx
------------------------------------------------------------------------------
Parsing "rrgn, 154,2: /154.bin "
Error
Parsing "reboot "
Error: invalid command 'reboot '
Error
[Only registered and activated users can see links. Click Here To Register...]
Remove the spaces on the command line. They should not be there.;)Quote:
Originally Posted by Alex40 [Only registered and activated users can see links. Click Here To Register...]
Parsing "rrgn,154,2:/154.bin"
Success
Parsing "reboot "
Error: invalid command 'reboot '
Error
Thank you ! I had to remove one more space after "reboot "
has become
Drive Software Version 3.70, UID: 39591967xx, HWID: 39591967xx
------------------------------------------------------------------------------
Parsing "rrgn,154,2:/154.bin"
Success
Parsing "reboot"
[Only registered and activated users can see links. Click Here To Register...]
I successfully pierced the device, but he did not see the cards.
I want to flash a second time. on the screen Image.
[Only registered and activated users can see links. Click Here To Register...]
What to do ?
