Forum Replies Created
-
AuthorPosts
-
April 18, 2018 at 2:10 am #142050
Hi Hodin,
I did those and nothing happened. It still won’t boot to the OS. To clarify, I can install the Win10 without problem but the bios cannot boot to the OS. Upon looking in the CMD command there is no boot manager created even you access EFI\Microsoft\Boot and apply fix boot commands the is no boot manager found in there to begin with. I just gave up finding solution for it that is why I returned the unit even I like the lappy.
April 17, 2018 at 11:15 am #142030Yes I had the same error. I didn’t back-up anything form the laptop since I though everything will be smooth. I tried typing “exit” and it just loops back. I also tried a lot of CMD commands as taught by my mentors and seen in the net but I still failed. there is no Boot manager and I cannot create a boot manager even I reconstruct (which is very tedious and time consuming) from a running laptop.
I also tried the Yepo 737S reset here “RESET” but the error still prevailed. Luckily I was able to refund the product but I really like that laptop; the sturdiness and quality seems very fine and it doesn’t heat so much unlike what I read from others.
My cousin who is IT said that its probably has missing drivers that was originally installed prior fresh reinstall; or that Win10 had caused an error and affected somehow the eMMC reader which is bad.
By this I’m afraid to try the Jumper EZbook 3 Pro itself as I may encounter the same problem from that unit. I do not want to refund again.
<hr />
By the way I read your post on the thread you linked.
It happened that I had an M.2 SSD with the unit I purchased. I tried reinstalling the OS on the SSD and still I end up with the EFI error. I also tried reinstalling without the SSD and still EFI error. I almost tried everything, but I guess there should be a driver to be installed while in recovery mode to make a boot manager that the EFI can read to boot the OS installed, but before i tried, I already have the unit refunded for warranty purposes.
Hope my input helps.
April 10, 2018 at 2:21 am #141759Hi,
I fresh reinstall my YEPO 737A to Win10 in the 128GB Rom but I wasn’t able to boot to the OS instead it always boot to the EFI and causes a “Device mapping table” error. Installing the OS to the 64GB rom also has the same error.
will reflashing the bios to jumper fix this issue? or did i do something wrong? I didn’t have the original image drive/drivers from the pre-installed OS since i didn’t expect to encounter such problem like this.
Thanks
-
AuthorPosts

