At this rate, if it happens again, you are better off filing for lemon law, since its the 3rd time that they are replacing the head unit.howie411 wrote: ↑Wed May 22, 2019 5:02 amJust a heads up, I dropped my Rogue off for an oil change yesterday and mentioned the rebooting again. (3rd time I've had the dealership look at it) Got a call from them yesterday afternoon saying they had a case open with Nissan and were told to replace the head unit. I'll see what the notes say when I actually get the pick up the car. On a side note they gave me a brand new Nissan Kick to drive (85 miles on it). The acceleration is much better than my Rogue.
Ha, oddly enough I enjoyed the few days with the Kicks, even though it was the base model. Also the NAV system screen was much nicer then my Rogue (though didn't support Android Auto).datechboss101 wrote: ↑Wed May 22, 2019 1:21 pmAt this rate, if it happens again, you are better off filing for lemon law, since its the 3rd time that they are replacing the head unit.howie411 wrote: ↑Wed May 22, 2019 5:02 amJust a heads up, I dropped my Rogue off for an oil change yesterday and mentioned the rebooting again. (3rd time I've had the dealership look at it) Got a call from them yesterday afternoon saying they had a case open with Nissan and were told to replace the head unit. I'll see what the notes say when I actually get the pick up the car. On a side note they gave me a brand new Nissan Kick to drive (85 miles on it). The acceleration is much better than my Rogue.
Ah, the Kicks as your loaner. Living with that car is one heck of a nightmare for me. I am a big guy, and that car ain't easy to drive. The steering wheel touches my knees (its a flat-bottom) and to adjust the seat takes time, but then when I have to lower the seat, I have to move the seat front. Its very irritating. I have my seat all the down and all the back in both the Rogue and the MDX and not a single darn issue. And that Kicks is super slow (I can totally achieve the same MPGs in the Rogue), even the acceleration. Our Kicks is nothing but problems, but then it was Made in Mexico and it was the first model year, and sat in the dealer lot from July 2018 to December 2018.
Corporate Nissan is a slap on the face. You are better off getting a lemon law lawyer at this point. Nissan won't care about its owners, as its really shown. I'd be surprised if they actually listened to their customers. Plus, your Rogue is still under the 3 years/36k mile warranty (unless you are over 36k miles).
Book Marking This!!! Great Post!!!aloyr wrote: ↑Tue May 07, 2019 6:57 amI am posting this because I was able to fix the repeated radio reboots in the 2018 Nissan Rogue I drive, and this thread is the closest thing I've found to my issue on the web. Maybe this will help the next guy...
While inconvenient, this beats arguing with Nissan and having your HU replaced, as there is most likely nothing wrong with it.
Ah, before I forget: to those that said that the map is unrelated to the rest of the unit: this is incorrect. Everything is connected inside the car, and a corrupt map data file can indeed cause the whole system to panic and to end up rebooting in an attempt to fix itself.
I hope this helps the next guy.
-A
aloyr wrote: ↑Tue May 07, 2019 6:57 amI am posting this because I was able to fix the repeated radio reboots in the 2018 Nissan Rogue I drive, and this thread is the closest thing I've found to my issue on the web. Maybe this will help the next guy...
The issue in my Rogue had to do with the radio rebooting frequently. Sometimes it wouldnt happen until I started driving, sometimes it would happen right after I turned the car on.
My case was the same as the situation described by @teeshot. I had done an update to the NC/SC map, and after that the reboots begun. It seems that TomTom messed up the stand-alone map update file for at least the NC/SC region. I'm not sure about the other regions.
There is no way to undo that update from the car. There is no point downloading all other updates either... yeah, I tried that too.
The way to fix this is as follows:
- grab a 16GB usb stick or bigger (some 16GB sticks won't work because they are actually 14.2GB and the update you will need is 14.7GB, so I used a 32GB stick)
- plug the usb stick into your Rogue's USB port (the same one used for carplay / android auto), and go to information -> system updates -> map updates -> copy date to usb (or something like that, I'm doing this from memory)
- remove the stick from the Rogue when told to do so and go to your computer
- download Nissan's map update tool for PC or Mac, install it, and launch it
- plug the usb stick into your computer
- navigate to the map update tab that will contain the single consolidated download package (as opposed to the per-region downloads), and download that - this will take you a while
- once that is done, eject the stick from your computer and go to your car
- start the car, do not drive (as that will trigger the reboot issue), and make sure that the radio will not start the reboot cycle while parked. if it does, try to hold down the power button until it shuts down, and restart the car, making sure that the radio won't auto-reboot.
- once the radio is stable while parked, plug in the usb stick and go to the same place in the settings: info -> system updates -> map updates -> install map data from usb stick. this will take a while as well. do not turn your car off nor drive it while this is going on.
- once the process is done, restart your car for good measure, and hopefully your problem will be fixed like mine was.
While inconvenient, this beats arguing with Nissan and having your HU replaced, as there is most likely nothing wrong with it.
Ah, before I forget: to those that said that the map is unrelated to the rest of the unit: this is incorrect. Everything is connected inside the car, and a corrupt map data file can indeed cause the whole system to panic and to end up rebooting in an attempt to fix itself.
I hope this helps the next guy.
-A
Thanks for posting this!aloyr wrote: ↑Tue May 07, 2019 6:57 amI am posting this because I was able to fix the repeated radio reboots in the 2018 Nissan Rogue I drive, and this thread is the closest thing I've found to my issue on the web. Maybe this will help the next guy...
The issue in my Rogue had to do with the radio rebooting frequently. Sometimes it wouldnt happen until I started driving, sometimes it would happen right after I turned the car on.
My case was the same as the situation described by @teeshot. I had done an update to the NC/SC map, and after that the reboots begun. It seems that TomTom messed up the stand-alone map update file for at least the NC/SC region. I'm not sure about the other regions.
There is no way to undo that update from the car. There is no point downloading all other updates either... yeah, I tried that too.
The way to fix this is as follows:
- grab a 16GB usb stick or bigger (some 16GB sticks won't work because they are actually 14.2GB and the update you will need is 14.7GB, so I used a 32GB stick)
- plug the usb stick into your Rogue's USB port (the same one used for carplay / android auto), and go to information -> system updates -> map updates -> copy date to usb (or something like that, I'm doing this from memory)
- remove the stick from the Rogue when told to do so and go to your computer
- download Nissan's map update tool for PC or Mac, install it, and launch it
- plug the usb stick into your computer
- navigate to the map update tab that will contain the single consolidated download package (as opposed to the per-region downloads), and download that - this will take you a while
- once that is done, eject the stick from your computer and go to your car
- start the car, do not drive (as that will trigger the reboot issue), and make sure that the radio will not start the reboot cycle while parked. if it does, try to hold down the power button until it shuts down, and restart the car, making sure that the radio won't auto-reboot.
- once the radio is stable while parked, plug in the usb stick and go to the same place in the settings: info -> system updates -> map updates -> install map data from usb stick. this will take a while as well. do not turn your car off nor drive it while this is going on.
- once the process is done, restart your car for good measure, and hopefully your problem will be fixed like mine was.
While inconvenient, this beats arguing with Nissan and having your HU replaced, as there is most likely nothing wrong with it.
Ah, before I forget: to those that said that the map is unrelated to the rest of the unit: this is incorrect. Everything is connected inside the car, and a corrupt map data file can indeed cause the whole system to panic and to end up rebooting in an attempt to fix itself.
I hope this helps the next guy.
-A
That's not new, corrupt GPS data can definitely send units off in the weeds. We've even heard of instances where units reboot only at a certain geographic location. There are about seven different interconnected modules inside a Bosch Navi, and a malfunction in pretty much any of them can cause reboots. I don't recall if your '18 has an SD card or WiFi downloadable, but one thing you can try in either case is disconnecting the battery to force the unit to come up cold and re-read the data from scratch. If it's a WiFi type, try reloading the whole local map. If it's an SD, turn it back in as defective and try a different one. The last thing to try would be a factory data wipe from the service menu.
I started this thread in 2018, so I was basically just saying it was resolved for the longest time then it came back. The 2018 model uses downloadable maps. Regardless its pretty ridiculous their system crashes due to a map updateVStar650CL wrote: ↑Sat Jun 05, 2021 8:34 pmThat's not new, corrupt GPS data can definitely send units off in the weeds. We've even heard of instances where units reboot only at a certain geographic location. There are about seven different interconnected modules inside a Bosch Navi, and a malfunction in pretty much any of them can cause reboots. I don't recall if your '18 has an SD card or WiFi downloadable, but one thing you can try in either case is disconnecting the battery to force the unit to come up cold and re-read the data from scratch. If it's a WiFi type, try reloading the whole local map. If it's an SD, turn it back in as defective and try a different one. The last thing to try would be a factory data wipe from the service menu.
Nissan is hardly the only brand with radios that misbehave from GPS or other forms of data corruption. It's an industry-wide problem caused by too much different firmware and hardware integrated into the same box. The more features people ask for, the worse it's likely to get.