You see now what i ment in my previous post…
Anyway, good luck and all the best.
Pleas if you can check this bios dump if there is trace of failed updated or anything that can prevent surface from booting? Thanks.
Surface pro 5
Model 1796
Mobo M1007506-015
SN: 054826391553
Bios dump
There’s one 0x1000 Block missing in the beginning of the second padding. But this padding does contain _FIT_ and there’s an additional error message about parsing ACM:
Try: Surface5flashinglogo2.zip (6.5 MB)
Thanks for working your magic. It is booting now. Windows up and running. All good!! This is attempt to fix my daughters Surface pro as she uses it for drawing with pen. Thankfully she kept backup of all her drawings. Now its back to life I just need to put it back together. You made her smile and we saved anoter MS product going to bin and polluting our planet Point is Surface Pro is a crap machine, another Mobo I tried to fix, with HW problem, I cannot even find replacement transistor which was burned. Shame. Anyway, your help is much appreciated.
I wonder why MS keeps everything twice (despite NVRAM) in bios region but doesn’t use it? Anyway, that really seems to be an erased but not rewritten block in this case.
Thanks for the feedback!
Can we speculate what caused this issue? There should be some safety protocol in place when anything gets erased and boot fails last known working copy is used. PC mobos got two bios chips for this purpose. Surface being quiet expensive piece of hardware when new should be more fault proof. I don’t get it.
Sorry, you don’t understand the concept. Expensive meaning durability and repairability was maybe the case a little earlier in the last century.
Today you got complete > 40.000$ vehicles stranded by f*#@ up firmware updates:
Hi there, I’m new to the forum and I also have some trouble with a Surface Pro 5. The problem is slightly different : lost touch capability after firmware update, but I think it might be related to this topic. I’m no expert for this kind of repair (I understand it’s not simple) but not a total newbie either (I was PHP developer before and like to manipulate electronics). I don’t want to waste anyone’s time, so my question is :
Could someone point me to a guide to repair the “firmware update” (or try to) or some kind of detailed steps so I can figure out where to start ?
Thanks
Please open your own thread, or maybe a mod may do this for you.
You need a dump of your firmware (CH341 programmer) in any case.
Regarding the touch: There was a possible fix posted at badcaps:
https://www.badcaps.net/forum/troubleshooting-hardware-devices-and-electronics-theory/troubleshooting-laptops-tablets-and-mobile-devices/bios-requests-only/92053-ms-surface-no-touchscreen-after-cleaning-me-firmware-fix
But if I remember correctly this didn’t work for all machines.
Tôi cũng gặp tình trạng lên logo window rồi tắt rồi lên rồi tắt lặp đi lặp lại . tôi có thử bios bạn đăng lên nhưng chỉ lên logo window và đứng im
English speaking forum.
If you have problems with a Surface I’d recommend starting your own thread.
(Google translate might be of help.)
Hello I’m new. I have an error with surface pro 5 M1007506-015 . The situation shows the window logo then turns off and the logo appears again then turns off continuously like that. I tried another bios, loaded it into the bios chip with ch341 and the window logo just stood still and nothing happened. Is it still a bios error or a hardware error? please help . would like to thank
Sorry for the confusion regarding a new thread, seems moderator doesn’t agree.
Please post / attach your dump / backup of the original bios / firmware.
Can you please look at this bios dump, the surface laptop 4 stays stuck on windows logo and does not boot / get into UEFI. Thanks
SL4-original-v1.zip (6.2 MB)
Completely different machine. MS doesn’t provide a full firmware image. You dump contains 2 a 100% identical (redundant?) UEFI volumes, the proprietary AMD stuff in padding, and an a little messy NVRAM.
=> Sorry, nothing obvious in static parts, looks more lit hardware to me. You could try with empty NVRAM and see if / what it writes again into NVRAM when trying to start up but I foubt that will help you any farther.
Surface Laptop model 1769
SN: 007127472557
Motherboard: M1029273-001
WIndows logo appear for few seconds in the loop and not booting Windows.
Please could you check my bios dump. Link below.
Many thanks.
@ukpicasso
Since you had already posted 2 similar requests about your problem into this thread, I have moved your 3rd help request here.
Good luck!
Download link doesn’t work with my browser.
@lfb6
I was able to download it and to upload the file as *.rar archive to my MEGA account.
>Here< is the download link.
Edit: The File and the MEGA link have meanwhile been removed, because they are not needed anymore.
Thanks @Fernando !
I can’t find anything speial, ME seems to be cleaned, as always the static bios consists of 4 duplicate efi volumes which are 100 identical- didn’t compare to stock, but both volumes havin the same error seems not very probable, the pair of paddings is identical, too.
NVRam has lots of free space and doesn’t look suspicious either…