Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 17 of 17 FirstFirst ... 7151617
Results 161 to 167 of 167
  1. #161
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    904
    Rep Power
    141

    Default

    Quote Originally Posted by fgafga View Post
    4- yes, but after holing switch for a while
    Please detail how it was seen by PC. For example: By File Explorer (Mass Storage Mode), or in Device Manager (preboot mode), or by one of Garmin's programs like MapSource/BaseCamp, or ?

    8- garmin cure, updater.exe doesn't recognize the device usb port.
    Both pro-boot mode and Garmin USB Drivers loaded are required for that.

    9-no
    Are you sure pre-boot isn't available? Most devices which boot only to the logo still have preboot. If it was stuck on logo screen then it's easier to find and maintain preboot but devices which reach the logo then either turn off or attempt to re-boot are more difficult.

    The vast majority of devices which will turn on and show the logo even briefly can be recovered with persistence.

  2.    Advertissements


  3. #162
    Junior Member
    Join Date
    Jul 2020
    Location
    BE
    Posts
    4
    Rep Power
    0

    Question

    Hi Everyone ! I'm totally new here.. but begging for help, i feel hopeless to throw away such an expensive device ...
    It's my first post, out of desperation :p!


    BMW NAVIGATOR V , Firmware version 3.5 , HWID 1451 .

    2) Why and how the device got bricked.
    Laptop battery died during a Garmin Express update...

    3) Symptoms: what's wrong in your device?

    Stuck on Loarding screen (but not even the "loading maps, just the BMW motorrad logo/garmin, with nothing else below it)
    Not recognized by PC
    4) Does your pc sees your device ?
    NO (Only in preboot in Device MNGR)
    5) List all the procedures you already tried to unbrick it and their results and errors messages obtained.
    Garmincure3 procedure (according to the tutorial) - Flashing Complete the cure(based on 3.5 Firmware from garmin) without any error, but the GPS doesn't go in Mass Storage Mode
    Quickcure3 - same

    Usb isn't flakky/badly connecting. it's really gps related only (It detect the pre boot fine)
    6) Do you have Garmin USB Drivers installed ? Garmin: USB Drivers Updates & Downloads
    Yes, and it's working properly on another unit.

    8) Write down if you already read or tried GarminCure3 tool - the new way to create cure firmwares for Garmin devices

    How to unbrick a nüvi - step by step guide
    Yes. as mentionned before
    9) Can you reach preboot mode? If no ,have you followed this? Garmin devices preboot mode
    I Can reach preboot mode.

    10) Probably no , but do you have NV backup?
    No, but i've got another device,same model on hands...
    Last edited by Nerox; 30th July 2020 at 10:56 PM.

  4. #163
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    904
    Rep Power
    141

    Default

    @Nerox
    It's a little concerning that you've not been able to connect it in Mass Storage Mode after loading Cure firmware. However, it has the ability to reach preboot so there's still hope. Are you sure that you made the Cure3 fw properly? Even tho' QuickCure also didn't work that's not conclusive because QC doesn't work to restore MSM for all bricked devices, only for most. If you made Cure3 fw just once then do it again from scratch or try flashing [Only registered and activated users can see links. ] that i just made.
    Spoiler: Decryption Key if Needed
    ID4SpNwtjlizr-GRSNqytIz5cuqo1lKvNJwhRg-AQME

  5. #164
    Junior Member
    Join Date
    Jul 2020
    Location
    BE
    Posts
    4
    Rep Power
    0

    Default

    Hi Butters,

    I responded from my smatphone..but apparently it wasn't posted.
    First of all, thanks for your support and your..promptness, i wasn't expecting that!

    I've tried at least 10 time to make the cur3fw...
    I've tried to flash with yours..
    Still the same, sadly, it gets recognized while in pre boot then disconnect after a sucessfull flash.

    Does using the old "RGN_tool" could help ?(just a tought)

    I feel.. at loss ..
    Is there a way to read the chip directly from the PCB? Perhaps?... Since i've a working unit

    Thanks foryour support!

  6. #165
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    904
    Rep Power
    141

    Default

    Quote Originally Posted by Nerox View Post
    ..........
    I've tried at least 10 time to make the cur3fw...
    I've tried to flash with yours..
    Still the same, sadly, it gets recognized while in pre boot then disconnect after a sucessfull flash.
    It's an unusual problem to have a device when in preboot to be recognized in Device Manager but then not being seen in Mass Storage Mode when Cure fw is properly loaded. There is possibility of actual flash chip damage but we'll proceed assuming it's only a 'soft' problem, not physical damage.

    Some questions:
    1. Have you checked in Disk Management that it's being allocated a drive letter by the system when you attempt to connect in MSM?
    2. Does the other Nav V you have connect and get recognized by the same PC?
    3. Are you using only a REAR USB2 port directly (not front port or USB3 port or via a hub)?
    4. Does Windows play a 'ding/dong' sound when you connect or disconnect either of the Nav devices?
    5. Have you tried a different rear USB2 port, various USB cables and/or different PC? (even tho' a certain cable, port or PC might work for the healthy Nav V)


    Does using the old "RGN_tool" could help ?(just a tought)
    No, not specifically in this case. RGN_Tool is useful to split or combine the BIN files from or into a firmware file and to convert an RGN file into a GCD file and vice versa.

    I feel.. at loss ..
    Is there a way to read the chip directly from the PCB? Perhaps?... Since i've a working unit
    No sure what you're asking there .... other than you might mean can the chip be reprogramed perhaps? If so, yes but you need special kit and skills to do so and regardless it's beyond what's needed here. If the flash chip has actual physical damage it cannot be reprogrammed and chip replacement is not economically viable anyway.

    If you're asking if the flash memory can be dumped, the answer is "maybe" but it depends on whether it's getting far enough into the boot process before sticking on the splash screen. To be able to read from and write to a microSD it needs to progress at least as far as 'Loading Maps', it's after that that fw_all.bin in region 14 [hex 0E] executes Ldr.bin on a media card to enable initiation of TXT commands and thereby access the internal flash memory/regions to write to them or copy [dump] them back to the card. We may have to try that, see below.

    Thanks foryour support!
    My pleasure, i don't mind a challenge.

    If you've checked all the points asked above but still can't access MSM then re-flash ORIGINAL fw as an RGN file in preboot (you can make an RGN using GarminCure3.exe or RGN_Tool, name it ONLY as 145101000350.rgn for safety). Then remove the battery to access the microSD slot and follow this:
    • Download this ZIP file [Only registered and activated users can see links. ] and extract it directly to a CLEAN microSD of at least 8GB formatted FAT32 (you can use a large card 64GB> but you may have to reformat it from exFAT to FAT32, Nav V can't read exFAT);
    • Insert the card into the device and replace the battery and cover but don't turn it on manually or hold the screen;
    • Plug it into a suitable power supply which will power it on (don't use a PC usb port for this);
    • Observe the screen to see if 'Loader' appears in some seconds. If it does, leave it undisturbed until it finishes which will take quite a while.

    It'll try to boot and stick on the logo screen when finished but if Loader doesn't show and it goes straight to the logo screen then the dump hasn't worked. If it does work then in the SD's Garmin folder there'll be a copy of it's nonvol memory as 41_backup.bin and the folder named 'BackUpFileSystem' will be populated). Good luck, please report back the result.

  7. #166
    Junior Member
    Join Date
    Jul 2020
    Location
    BE
    Posts
    4
    Rep Power
    0

    Firmware

    Hi Butters, Thanks again Butters - I'm glad i can be a "distraction" in your eternalnsupport to the gps community

    1. [*]Have you checked in Disk Management that it's being allocated a drive letter by the system when you attempt to connect in MSM?
      ..Yes, i've checked, but... IT DOES NOT get an allocated drive letter...since it's only detected in pre-boot
    2. Does the other Nav V you have connect and get recognized by the same PC?
      Yes, with the same cable, same port
    3. Are you using only a REAR USB2 port directly (not front port or USB3 port or via a hub)?
      ..Is usb 2.0 still a thing ? I've only usb 3.0 - But i did "RTFM-Cure3" and used a port on the motherboard itself as precognized.
    4. Does Windows play a 'ding/dong' sound when you connect or disconnect either of the Nav devices?
      For the defective one, only during pre-boot. As soon as it leave pre-boot and tries to boot "normally" it does'nt get detected .
      And it only gets detected in the Device manager under "Garmin Devices"
      For the Working one - Yes, and it's getting detected by garmin express and is able to be put in MTP via the menus of the unit.
    5. Have you tried a different rear USB2 port, various USB cables and/or different PC? (even tho' a certain cable, port or PC might work for the healthy Nav V)

    I've tried two USB ports, but only one computer. I'll try with one friend's laptop. But it's still usb 3 ,and windows 10.
    and... the annoying thing here, is that i get the "successfull patch" every f*** time . So it doesn't seem's like a transfer issue. And if eMMC (internal memory) was defective, i wouldn't be able to flash... it's still a 70mb file to send, i doubt that the rom is that big



    No sure what you're asking there .... other than you might mean can the chip be reprogramed perhaps? If so, yes but you need special kit and skills to do so and regardless it's beyond what's needed here. It was indeed my question. But i've googled it..and, well, the device itself cost like 150 euros to read the Emmc.. + the fact that i sould know how to desolder , reballing etc... soo , yes. A bit too high level repair for me

    If you're asking if the flash memory can be dumped, the answer is "maybe" but it depends on whether it's getting far enough into the boot process before sticking on the splash screen. To be able to read from and write to a microSD it needs to progress at least as far as 'Loading Maps', It's after that that fw_all.bin in region 14 [hex 0E] executes Ldr.bin on a media card to enable initiation of TXT commands and thereby access the internal flash memory/regions to write to them or copy [dump] them back to the card.
    ...It never went that far, sadly



    If you've checked all the points asked above but still can't access MSM then re-flash ORIGINAL fw as an RGN file in preboot (you can make an RGN using GarminCure3.exe or RGN_Tool, name it ONLY as 145101000350.rgn for safety). Then remove the battery to access the microSD slot and follow this:
    • Download this ZIP file [Only registered and activated users can see links. ] and extract it directly to a CLEAN microSD of at least 8GB formatted FAT32 (you can use a large card 64GB> but you may have to reformat it from exFAT to FAT32, Nav V can't read exFAT);
      -Done
    • Insert the card into the device and replace the battery and cover but don't turn it on manually or hold the screen;
      ...So, my issue is that it's turning itself on as soon as battery is connected.
      I've tried to connect the usb cable then the battery,
      i've also tried to 1) Disconnect battery 2) put back cover so i don't get the warnin msg, 3) put usb charging cable
    • Plug it into a suitable power supply which will power it on (don't use a PC usb port for this);
    • Observe the screen to see if 'Loader' appears in some seconds. If it does, leave it undisturbed until it finishes which will take quite a while.

    It'll try to boot and stick on the logo screen when finished but if Loader doesn't show and it goes straight to the logo screen then the dump hasn't worked. If it does work then in the SD's Garmin folder there'll be a copy of it's nonvol memory as 41_backup.bin and the folder named 'BackUpFileSystem' will be populated). Good luck, please report back the result.

    It Didn't ..

    What about doing a backup of my other nav via micro sd and then try to use it in the defective one - aka "clone" it..?
    Thanks for your help !

  8. #167
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    904
    Rep Power
    141

    Default

    Quote Originally Posted by Nerox View Post
    ..............[*]Are you using only a REAR USB2 port directly (not front port or USB3 port or via a hub)?
    ..Is usb 2.0 still a thing ? I've only usb 3.0 - But i did "RTFM-Cure3" and used a port on the motherboard itself as precognized.
    USB3 is designed to be backwardly compatible with 2 and even 1 but it's not perfect in that regard. I've had Garmins and other devices which are not variously seen via any USB3 port or a front desktop USB2 or thru' a hub, but recognized fine with a rear USB2 on a desktop. There are plenty of old PCs around, even an old slow under-powered Win XP desktop gathering dust is worth a try provided it has Garmin USB drivers loaded. Modern laptops/desktops are just less likely to 'play nice' with bricked Garmins using USB3 ports. Sometimes having Garmin Express or other 'helper' software running silently in the background can interfere too so make sure there's nothing of Garmin's running and kill it if there is.

    [*]Does Windows play a 'ding/dong' sound when you connect or disconnect either of the Nav devices?
    For the defective one, only during pre-boot. As soon as it leave pre-boot and tries to boot "normally" it does'nt get detected .
    And it only gets detected in the Device manager under "Garmin Devices"
    For the Working one - Yes, and it's getting detected by garmin express and is able to be put in MTP via the menus of the unit.
    As i said, bricked devices can be tricky with connection but the fact that it's seen in device manager when in preboot but not in MSM with cure fw loaded is a little troubling. Flash damage is indicated especially if you get the same behavior using a desktop with rear USB2 which is why i'd like you to try that if possible. Keep in mind that 'bricked' devices are sometimes VERY flaky.

    [*]Have you tried a different rear USB2 port, various USB cables and/or different PC? (even tho' a certain cable, port or PC might work for the healthy Nav V)[/LIST]
    I've tried two USB ports, but only one computer. I'll try with one friend's laptop. But it's still usb 3 ,and windows 10.
    and... the annoying thing here, is that i get the "successfull patch" every f*** time . So it doesn't seem's like a transfer issue. And if eMMC (internal memory) was defective, i wouldn't be able to flash... it's still a 70mb file to send, i doubt that the rom is that big
    That statement about not being able to flash if the internal memory was defective isn't absolute. Minor flash damage can indeed allow some functionality and not others. I have a Samsung 16GB microSD right here which still has MSM but i've tried to re-format with Windows and every 3rd party soft i've got, even LLFTOOL.EXE reports the format as successful but all files are still there. I can 'add' or 'remove' individual files but they simply disappear or reappear. Flash damage manifests in different ways. Let's hope that's not what your Nav V has and keep trying because software brickings and region corruptions aren't all the same in their symptoms either. Just as there's degrees and types of hardware damage, software problems vary too and in that card's case the flash controller is shot.

    No sure what you're asking there .... other than you might mean can the chip be reprogramed perhaps? If so, yes but you need special kit and skills to do so and regardless it's beyond what's needed here. It was indeed my question. But i've googled it..and, well, the device itself cost like 150 euros to read the Emmc.. + the fact that i sould know how to desolder , reballing etc... soo , yes. A bit too high level repair for me

    If you're asking if the flash memory can be dumped, the answer is "maybe" but it depends on whether it's getting far enough into the boot process before sticking on the splash screen. To be able to read from and write to a microSD it needs to progress at least as far as 'Loading Maps', It's after that that fw_all.bin in region 14 [hex 0E] executes Ldr.bin on a media card to enable initiation of TXT commands and thereby access the internal flash memory/regions to write to them or copy [dump] them back to the card.
    ...It never went that far, sadly
    Ok, we'll try another way below.

    ...So, my issue is that it's turning itself on as soon as battery is connected.
    I've tried to connect the usb cable then the battery,
    i've also tried to 1) Disconnect battery 2) put back cover so i don't get the warnin msg, 3) put usb charging cable
    Holding the power button for between 10 and 30 seconds should force it off with the battery in it anyway. It should also work without the battery in provided there's enough power from the USB source, because in most Garmin devices the battery isn't an essential part of the power circuitry. Anyway, it doesn't seem that your problem is it's not fully off for your attempts (it can't enter preboot unless it's fully off and you've got preboot).

    What about doing a backup of my other nav via micro sd and then try to use it in the defective one - aka "clone" it..?
    Thanks for your help !
    Forget that. Rare devices such as some dog-trackers can indeed be 'cloned' but most cannot and certainly not this one. Every time it boots it will update region 41 (non-vol memory) and re-write the GarminDevice.xml. Regardless, to even unsuccessfully try that we'd need to have it read/write from and to the card. But that's our next move, to try another way of using the microSD. Please follow this:
    • REMOVE the file named "Ldr.bin" from the 1541 folder on your microSD card. There should only be one file named "update.txt" remaining in 1541 folder.
    • Place the card into the device and ensure it's fully OFF.
    • Open this extracted RGN file [Only registered and activated users can see links. ] in Updater.exe and leave it's GUI open and visible for quick initiation.
    • Have the PC with USB cable connected, hold Nav screen, plug in USB cable to it then quickly start Updater.exe to flash.

    In explanation, the only content in this RGN file is boot.bin (Ldr.bin) which has been modified to bypass the requirement of the firmware initiation's for using the TXT commands in update.txt. This is definitive, if this doesn't work to dump region 41 and the internal folders and files then it's flash damage and irrecoverable using software means. If it works, then we'll keep going. Good luck this time.

    EDIT: IMPORTANT! I've just realized i've made a typo in the HWID folder name on the SD card kit. It's "1451" when it should be "1541" so please change that before proceeding.
    Last edited by Butters; Today at 12:07 AM.

 

 

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •