Crashed linux Installation on N42C-4 - No BIOS anymore

Good evening!
Gentlemen I need your help!
My N42C-4 configuration: 8GB Ram,SSD 240GB - runs flawless - but then.......
I've tried to install Ubuntu Linux on the eMMC of my N42c-4....So far so good _ unfortunately something happened and the installation crashed.
I tried to go back to Bios to change the Boot order back to the original(working) one - but no chance...
Any thoughts?
Any help would be VERY apriciated!

Thanks in Advance,Manfred
 
Good Morning,
after rereading my first post I think the real problem is a little unclear - so I try again:

I have erased the eMMC by accident(my 73 years old brain was a little slow at the moment.....)
The engine started but did'nt boot and I have no acess to the bios - conclusion:the bios is originally on the eMMC and not on a chip

Any tipps or tricks to get a bios?

On the Motherboard in the diagonally corners are 3(ground,RX,TX) and 4 pins would it be possible to copy a bios via these pins to the eMMC?

Greetings,Manfred
 
Hello Manfred, I'm afraid I have no idea how to get you out of this, hopefully some one on the forum with more experience in this avenue will chime in and get you back on track :unsure:(y)
 
Good Morning,
after rereading my first post I think the real problem is a little unclear - so I try again:

I have erased the eMMC by accident(my 73 years old brain was a little slow at the moment.....)
The engine started but did'nt boot and I have no acess to the bios - conclusion:the bios is originally on the eMMC and not on a chip

Any tipps or tricks to get a bios?

On the Motherboard in the diagonally corners are 3(ground,RX,TX) and 4 pins would it be possible to copy a bios via these pins to the eMMC?

Greetings,Manfred

Which Ubuntu image were you using & which installation procedure were you actually following? (Got links, for example?)

Have you tried simply disconnecting the CMOS battery & see if a complete BIOS reset clears this issue? (30 seconds is usually long enough, but disconnect the CMOS battery for 5+ mins just to be certain all settings have cleared & obviously ensure the device is mains isolated too.)

Otherwise, your conclusion that the BIOS is installed on the eMMC isn't the case. It's hardware integrated. (The N42C-4 is a good example, in that one can completely disable the eMMC from the BIOS, yet the BIOS & an OS installed on an additional SSD/HDD will continue to function just fine. Were the BIOS truly installed to the eMMC the system would completely fail the very second any end user saved the BIOS settings that disabled their eMMC & they'd never be able to re-enable the eMMC (without going through the above procedure) as they'd be locked out of the BIOS.)

From your description it sounds as if you're already fully aware of the correct procedure, but just in case (as occasionally users having a hardware crisis can completely miss basic steps).....

To enter the BIOS you may need to repeatedly spam the delete key the moment the system powers on & continue until the system actually enters the BIOS.

After that, in your context what does "no chance" actually mean? I.e. what does the system do when you attempt to enter the BIOS? Is the power LED illuminated on the front of the device? Is it still the normal blue colour or has it changed? Do you still get the MINIX splash screen when you initially power the device on?

Also, try removing any extra RAM you may have installed (especially if you're mixing modules & the additional after market RAM is different to the factory original module). Or, if you completely replaced the original RAM with a matching pair (which is the recommended method), either remove the after market RAM & just install the original module alone or try removing just one of the after market modules at a time, & then try another reboot & accessing the BIOS again after each RAM change. (While unlikely, it's not at all unheard of for something like a RAM module to fail while a user was upgrading an OS & the symptoms then perceived to have been caused by software when it was actually a simultaneous hardware failure. Obviously you'll need to troubleshoot these other possible causes independently to be absolutely certain.) Remember to take the normal precautions for handling internal components less you also directly cause another new problem in trying to correct the original.

You could also try the same procedure while cycling out the SSD you've installed as well. (If there's even a remote possibility that your next step may be to declare the device as bricked, then there's nothing to lose by first troubleshooting all possible variables that could potentially be a factor.)

Try that lot for now & see if anything happens to shake loose, (so to speak) ;).
 
@Villa / @Skynet / @gufone ....

The OP has PM'd & tells me he now can't seem to respond with any additional posts under this thread.

Is there anything from the forum side that's potentially blocking them please?

Otherwise, this thread could also be marked as SOLVED. OP has now got the device running again :).
 
Thanks for checking. Didn't think there would be an issue, must be another problem with another device the OPS end :rolleyes:.

The original problem is now apparently solved anyway :).
 
Back
Top