NP700Z7C unable to boot (bricked)

Hi everyone. I've met this forums looking for a solution on this issue.
I have a NP700Z7C - S01US bought back in september 2012. It came with W7, but it was updated to W8 and then W8.1. It worked without problems for a few months, and then one day, after a Windows 8.1 update, it hangs up on the logo screen. I'm not getting a loop as it seems to happen to many people, just it freezes on the Samsung logo.

I've read as many threads as I found about this matter. But nothing seems to work on my case.
I can't go through the logo screen, being unable to enter to the bios (F2), samsung recovery (F4), boot selector (F10), or Win8 Advanced Startup Options (F8, shift+F8, even ctrl+F8).

I have also tried to reset the CMOS/NVRAM by disconnecting both batteries and flush all the power left. Even disconnect the HDD seems to not working for me.
I've followed the instructions here and created a bootable version of Win 8 by downloading RUFUS and Win 8.1 iso. I does not work either. Also tried this but it goes to a close end as well.

I have not idea what else to try, and I hope you can throw me some bone here.

Thank you very much in advance,
Ilán

 

Can I try to format and install a new windows on the drive and try to start with that? Or is it going to be blocked by UEFI anyway?

 

Hi Melior, welcome to NBR.

I am sorry to hear about this, you're the second such case we've had recently.

Most of these semi-bricked cases are Win8 models (with the new UEFI/SecureBoot BIOS) that can be revived using the procedure discussed in the thread linked below. There is a summary/guide in post #7, but you want to read the entire thread.

http://forum.notebookreview.com/threads/samsung-series-7-np700z5c-s03ca-my-last-hope.762595/

You need to be able to boot something for this procedure, and in most of these cases a USB flash drive can be booted if (a) it is properly formatted (matching the UEFI or CSM setting in BIOS) AND (b) by disconnecting the HDD/SSD in order to force an external boot source. That is all discussed in that thread.

If no booting is possibly (even after disconnecting the HDD) there is the possibility of an emergency flash as described by member @urkopineda in post #59 of that same thread. But not many have succeeded in doing that.

Finally, if all those fail, there is the option of physically re-flashing the BIOS with an (E)EPROM burner, which some repair centers should be able to do. That, too, is discussed in that thread, starting by member @Villtord in post #82.

For all of these you will need BIOS files for your model which, if you don't have them already (saved after an earlier BIOS update), can be located and downloaded using the thread linked below, by carefully following member @isosunrise's guide in the opening post. There is more good discussion later in that thread as well.

http://forum.notebookreview.com/threads/samsung-laptops-roll-back-bios-updates.696197/

Finally, you can check member @Brian D's thread linked below. He has so far been unable to unbrick his NP700Z7C, even after trying the procedures discussed here, but his thread contains more good advice.

http://forum.notebookreview.com/threads/it-is-official-np700z7c-s01us-is-a-lemon.771836/

Note that this all assumed the problem is from the BIOS/CMOS/NVRAM. If you have an actual motherboard defect, of course none of this will work.

But there is also the possibility you simply have a defect HDD. If you have another HDD or SSD, that is definitely worth trying.

Good luck. Please keep us posted

 

You posted this just as I was writing my other response. I understood this was a Win7 model, which means UEFI shouldn't be the problem. Or did you enable UEFI Boot on it before installing Win8/8.1?

Also, I understood that you are currently unable to boot anything -- not even an external USB. That is why I suggested disconnecting the HDD (in order to force booting the USB). You then use that to clear the CMOS/NVRAM corruption that may be causing the problem.

But again, testing with another HDD is a good idea.

Do NOT format the HDD in another computer yet -- particularly if it's a GPT (UEFI) installation. That will only make it more difficult to boot, since the HDD contains the EFI boot code.

 

Dannemand beat to the punch, twice now. He has much better info than I could give, I am assuming from what you are saying that with windows 8 you enabled uefi. as in his second post watch the format of the drive and efi info.

 

@TANWare: LOL, sorry about that

You're spot on: If UEFI was enabled and the EFI partition is damaged, that could be the problem right there. And in any case make sure the USB is formatted as GPT/FAT32.

We haven't had many reports of NVRAM corruption (where F2 doesn't work and external devices won't boot) on Win7 models, which have the simpler UEFI implementation. But that could be just because most users don't enable UEFI on them. Maybe they are just as prone when it is enabled.

 

Hi @ Dannemand, thank you for your quick response. I already read the first post you have mentioned, and tried several things. Non of them have worked for me. I'll check the @Brian D's post as you mentioned and see if I can get some help from him.

As far as the configuration, I'm not really sure if enabled the UEFI option after win8.1 install. I have some troubles in the past with the expressChache as well and the only solution I have found in that time was not to install the EC driver. As soon as I installed the EC driver, the PC frizzes and the only thing I could do was to start the Win8 intallation all over again. But I don't know if this is related or not.
What is really having me lost here is that my Win8.1 seems to work fine for a while. And then, after a minor updated (I guess), this happened. I've remember having some troubles after restarting the PC, it hungs up sometimes, but shuting down the computer used to solved it without troubles.

I'll try what you've mentioned about installing Windows in another disc. Any recomendation? Any special type, or just plain win8.1? Do I just need to connect the HDD to another PC and follow the windows installation?

I've already tried this. Disconnected the HDD and try to boot from the USB (even tried to format in several ways with Rufus software, GTP/UEFI and MBR/BIOS)

I'll wait on this then. No need to get things worse yet

As some people here mentioned it's been a while since I had to struggle with this kind of stuffs and all the UEFI situation is new to me. And I really apreciate your help.

 

Thank you for the update.

The symptoms you describe would mostly be explained by a defect HDD -- including the sporadic freezes, made worse when you install ExpessCache (which begins to cache the HDD after it is installed).

But it is troublesome that you cannot boot from an external USB, even after disconnecting the HDD. That would indicate something else is wrong -- and makes it difficult to solve.

A defect iSSD (the small SSD used by EC) could cause the EC issues you describe AND inability to boot as well -- or very long boot delays while Windows tries to contact the iSSD (even if EC is not installed). Did you try cold boot, then waiting maybe 10 minutes?

There is one scenario (short of a motherboard/iSSD defect) that would prevent booting even with the HDD disconnected: If UEFI was enabled, and Windows was installed from USB stick on an ExpressCache-model. This would cause the EFI partition to be written to the iSSD (due to a confusion on the part of Windows Setup) and UEFI/NVRAM registering this location. However, since the iSSD is not visible during boot, the computer becomes unbootable. If BIOS is also inaccessible (due to corrupted NVRAM) you effectively have a bricked laptop. This is discussed in member @KcKepz's thread linked below:

http://forum.notebookreview.com/thr...when-function-buttons-are-not-showing.755985/

Here are the things I would try, some of which you may have tried already:

1) Cold reboot with HDD connected and wait a LONG time (as described above) for access to the iSSD to time out (in case you have a defect iSSD).

2) Since you don't know if UEFI is enabled, create a Windows Setup USB stick formatted as MBR/NTFS. Use Microsoft's old ISO/USB tool (which doesn't support UEFI). Then try booting that with the HDD disconnected.

3) In case UEFI was indeed enabled, try again creating a Windows Setup USB stick as GPT/FAT32, this time using the manual steps in member @Obyboby's Win8.x Install Guide. See if that will boot with the HDD disconnected.

4) If you have another 2.5 HDD or SSD or can borrow one (anyone will do) you could indeed try formatting it in another PC and install Windows. But DON'T complete the installation: When it is finished copying files and wants to reboot the first time, turn off the PC and move the HDD to the Sammy. Now see if it will boot. Try both as UEFI (GPT) and as legacy BIOS/CSM (MBR) -- again, since we don't know what your computer is set to.

The purpose of all of these are just to try ANYTHING to boot the computer, so that you can clear the NVRAM as described in the first thread I linked.

If all that fails, the only other things I can think of are (1) Emergency Flash as described by @urkopineda or (2) physical re-flashing of the BIOS chip as described by @Villtord. There are a few other reports of these fixes which you can find with the NBR Search function (I don't have the links handy).

If the iSSD is defect (or anything else on the motherboard) you really need a new motherboard. Maybe some repair shops are able to replace the iSSD, though I never heard of it.

There could be other hardware issues I didn't think of. TANWare and John have much better understanding of those.

 

Another issue is these supposedly have 6GB ram, 2 soldered and 4 in a stick You can try a boot without the memory stick. If not then I am in agreement where it is a 90% chance or better where the iSSD was dying and is now dead. While the iSSD is not software initialized prior to bios it is powered up and needs to pass its power up test. This could be from just a long delay to never continuing the power up.

Other, as pointed out, if it doesn't power up and looks to the iSSD device number for the EFI information you are again dead in the water. The advantage here would be it did look for the block meaning a blind flash COULD work.

The working theory is if you can get to the search point of the EFI pre/post internal devices then the system is recoverable. The problem is there is no way to identify that the system has gotten to that point. EEPROM burning has the same issue, getting it to search the right block and then is the system 100% functional where you will not have a further issue.

One thing about the links to the blind flash. It is free to try but it should only be considered as a last resort.

 

Hi @Dannemand and @ANWare, thanks again for your quick response.

Wouldn't the pc be stuck as soon as I have intalled the Win8.1 in this case? A read about it, but seems to not be my case.

Alredy tried this. Leaving the pc even overnight, but nothing happened.

I've tried this as well. But is it any difference between MBR/NTFS from Microsoft tool and Rufus? I've tried both MBR/NTFS and GPT/FAT32 with Rufus.

This seems promising and I'll try it as soon as I get another HDD to try. Maybe I can get one borrow this weekend. Which OS I try with? will Win8.1 be accurate? And finally, how do I try both UEFI (GPT) and BIOS/CSM (MBR) in a windows instalation? from differents sticks?

I've read about this as well but I left it as a last result due to seems to be risky. If the HDD doesn't work, I'll try it.

Removing the iSSD from the board will do any difference? Or it will fail due to the lack of it anyway?

Already tried without RAM. It was my first aproach, discard the defective RAM. Even tried with anotrher one. Didn't know it has a soldered one.

Blind falsh is the same as "Emergency Flash"??

Thanks you both a ton for all the theories you've gave me!
I hope on of the hit the nail!

 

Yes the blind flash is the emergency recovery flash. Without any ram I do not think even the logo will show as it needs the base ram for that 640kb. Since the 2 of the 6 is there you are ok there.

 

Ok thanks, I'll try the intall on a new HDD first. And then if that doesn't work, I'll try this.

 

Hi, I'm sorry for the delay but I couldn't get any HHD to try with. I have now managed to try the option with another disk but sadly it doesn't work either.

Reading again the thread, I found that what @Dannemand said it's probably the most accurate option here:

I don't remember installing Win8 from a DVD so I assume that the USB install was what I did then. It didn't get me any issue at that time but maybe plus the iSSD problem it was what got me here.

What do you suggest now? Must I try the Emergency flash? Or is there another "simpler/less riskier" option to try with first?

Thanks a lot for your help anyway!

 

The other user, with a G7A gamer, tried installing windows from another machine on a hdd fresh and running sysprep and then putting it back into his Samsung. You could pull the hdd and try that from another machine. You may need to do this though on a machine that is UEFI. Also not too sure if you would need Windows 7 or Windows 8.x to get this too work.

Edit; Actually any system hanging at the logo or circular reboot from the logo can try this method.

Edit 2; I would suggest the other system you use does not have an iSSD, in this way you can be sure the UEFI info is on the HDD/SSD.