[marcospoffo]

I'm on the bench with an ID4, replacing the hdd with a new 240gb ssd.


I opened SSH and created the create_hdd.sh partition, format, mount, directories successfully using Putty.

Usb, bt audio, music collection, cd etc worked again. I flashed the Iba and installed the new fsc with the map. everything is OK.

But after doing any fdl or reboot, the evo starts without working the above functions, as if the hdd was still defective. After 1 minute, without me doing anything, it recognizes and everything works again.

My question is: could this be happening because the ssd doesn't have the necessary requirements? or what could be going on?

[dasi]

I'm on the bench with an ID4, replacing the hdd with a new 240gb ssd.


I opened SSH and created the create_hdd.sh partition, format, mount, directories successfully using Putty.

Usb, bt audio, music collection, cd etc worked again. I flashed the Iba and installed the new fsc with the map. everything is OK.

But after doing any fdl or reboot, the evo starts without working the above functions, as if the hdd was still defective. After 1 minute, without me doing anything, it recognizes and everything works again.

My question is: could this be happening because the ssd doesn't have the necessary requirements? or what could be going on?

can help you remotely

[Yah]

Hello,
I have the same issue with ID4, replaced hdd with ssd, flashed the unit with the latest psdzdata.
Before any fdl changes, it works normally, but after fdl coding i.e. VIM, the navigation and bluetooth takes time to activate, sometimes 30 minutes and sometimes 5 minutes.
I would be interested in solving this issue if possible, because I was thinking that is hardware issue.

[juantg93]

I'm on the bench with an ID4, replacing the hdd with a new 240gb ssd.


I opened SSH and created the create_hdd.sh partition, format, mount, directories successfully using Putty.

Usb, bt audio, music collection, cd etc worked again. I flashed the Iba and installed the new fsc with the map. everything is OK.

But after doing any fdl or reboot, the evo starts without working the above functions, as if the hdd was still defective. After 1 minute, without me doing anything, it recognizes and everything works again.

My question is: could this be happening because the ssd doesn't have the necessary requirements? or what could be going on?

can help you remotely

After everything he has done, surely if you tell him what he has to do, he is capable of understanding it and doing it.