TechTablets › Forums › Jumper Discussion › EZBook series › how to update bios ezb3pro v4 to v5
- This topic has 62 replies, 7 voices, and was last updated 8 years, 3 months ago by
Juha Pirinen.
-
AuthorPosts
-
January 15, 2018 at 9:09 pm #77032
Not sure, but the original v4 doesn’t have the keyboard problem, do yours must be a v4.5 🙂
January 15, 2018 at 9:15 pm #77034I do not know for sure… what is the difference between the 4 and 4.5?? i bought mine november the 14th and it arrive november 25 with the september bios, with the power limit locked but i can change the emmc (sandisk df4064) speed over the chipset tab.
January 15, 2018 at 9:25 pm #77036I just bricked my device trying to do so, I ‘m trying to recover now by reprogramming the EPROM after the bad flash.
If I’ll get it to work I’ll try to write what I did and what went wrong so everyone can avoid my mistakes.
Go easy on the bios!
January 15, 2018 at 9:46 pm #77037I just bricked my device trying to do so, I ‘m trying to recover now by reprogramming the EPROM after the bad flash. If I’ll get it to work I’ll try to write what I did and what went wrong so everyone can avoid my mistakes. Go easy on the bios!
sorry to hear that… did you try to update from 4 to 5??? if you bricked the bios maybe you need to reprogram it
January 16, 2018 at 8:51 am #77051I just bricked my device trying to do so, I ‘m trying to recover now by reprogramming the EPROM after the bad flash. If I’ll get it to work I’ll try to write what I did and what went wrong so everyone can avoid my mistakes. Go easy on the bios!
sorry to hear that… did you try to update from 4 to 5??? if you bricked the bios maybe you need to reprogram it
I tried to downgrade to get the power limit option from V5 (build 09/03/17) to V4 (08/**/17)
I made a stupid mistake and now the power button just light up the power indicator but screen has no sign of life.
“Luckly” I saved my .rom BIOS before doing the silly thing.
Now I’m trying to understand which EPROM programmer should I get and if ISP of the EPROM is possible.
January 16, 2018 at 9:16 am #77052I’m interested in what stupid mistake you did? I have V4.5 with keyboard lag and I’m quite pissed with it. Going to flash V4 bios and hope it will fix that. Found instructions from the other thread. So in uefi shell just backup first and then flash jumper.rom.
EDIT: Or is the jumper.rom the edited version for the yepo and the other jumper file the original and it must that one?
January 16, 2018 at 12:10 pm #77057I’m interested in what stupid mistake you did? I have V4.5 with keyboard lag and I’m quite pissed with it. Going to flash V4 bios and hope it will fix that. Found instructions from the other thread. So in uefi shell just backup first and then flash jumper.rom. EDIT: Or is the jumper.rom the edited version for the yepo and the other jumper file the original and it must that one?
I tried to flash from windows with the exe utility, flashing in the uefi shell should be fine!
I hope for success! 🙂
January 16, 2018 at 12:59 pm #77059I’m interested in what stupid mistake you did? I have V4.5 with keyboard lag and I’m quite pissed with it. Going to flash V4 bios and hope it will fix that. Found instructions from the other thread. So in uefi shell just backup first and then flash jumper.rom. EDIT: Or is the jumper.rom the edited version for the yepo and the other jumper file the original and it must that one?
I tried to flash from windows with the exe utility, flashing in the uefi shell should be fine! I hope for success!
flashing the v5 bios from the uefi shell should work??
January 16, 2018 at 4:02 pm #77061Dont do it in the efi shell either. Just bricked mine. FUCK.
Power button does nothing. Removed battery for awhile and now it turns on but screen stays black.
January 16, 2018 at 4:46 pm #77062Dont do it in the efi shell either. Just bricked mine. FUCK. Power button does nothing. Removed battery for awhile and now it turns on but screen stays black.
fuck! how did you do that??
January 16, 2018 at 5:21 pm #77064Booted efi shell and flashed the bios dated from August. Original bios was dated end of september. That’s it. Bricked.
I’ll buy Lenovo Yoga next, I’m sick of these machines when you dont know what you get. This was very good laptop for the price IF there wasnt the keyboard lag… And that’s why I tried to flash older bios in the first Place.
January 16, 2018 at 5:27 pm #77065Booted efi shell and flashed the bios dated from August. Original bios was dated end of september. That’s it. Bricked. I’ll buy Lenovo Yoga next, I’m sick of these machines when you dont know what you get. This was very good laptop for the price IF there wasnt the keyboard lag… And that’s why I tried to flash older bios in the first Place.
did you check if the device id of both bios files (your dumped one and the new one) were the same?
January 16, 2018 at 5:55 pm #77067Nice, maybe i had luck. Successfully downgraded my V5 to V4 BIOS (unlocked) with that Jumper.rom file from Yepo’s guy via UEFI shell, as described in the read.me. Just updated boot block and main block nothing else. All files are in his Google Drive.
If somebody can check BIOS EEPROM type from (8 pins black cube) the mainboard, i can tell you whitch external programmer is ok to recover the laptop.
January 16, 2018 at 5:58 pm #77068Nice, maybe i had luck. Successfully downgraded my V5 to V4 BIOS (unlocked) with that Jumper.rom file from Yepo’s guy via UEFI shell, as described in the read.me. Just updated boot block and main block nothing else. All files are in his Google Drive. If somebody can check BIOS EEPROM type from (8 pins black cube) the mainboard, i can tell you whitch external programmer is ok to recover the laptop.
wow, congratulations! what date was your bios??
by the way, i think that this is the bios chip, could you please tell us what is the correct programmer?
Attachments:
You must be logged in to view attached files.January 16, 2018 at 5:58 pm #77069Here is original which I dumped before flashing, and the older one which I flashed.
Attachments:
You must be logged in to view attached files. -
AuthorPosts
- You must be logged in to reply to this topic.

