Lenovo IdeaPad 330S-15ARR - 330S_ARR_V06

[gusto]

I followed post number 29. I found the region 1EE000 - 1EE22F and replaced it.
However, I do not know if it is enough to replace only this region 1EE000 - 1EE22F (I did not replace the Win key)
The BIOS you sent me starts in the hex editor like this

00000000: 0100 003e ffff ffff ffff ffff ffff ffff ...>............
00000010: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000020: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000030: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000040: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000050: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000060: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000070: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000080: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000090: ffff ffff ffff ffff ffff ffff ffff ffff ................
000000a0: ffff ffff ffff ffff ffff ffff ffff ffff ................
000000b0: ffff ffff ffff ffff ffff ffff ffff ffff ................
000000c0: ffff ffff ffff ffff ffff ffff ffff ffff ................
000000d0: ffff ffff ffff ffff ffff ffff ffff ffff ................
000000e0: ffff ffff ffff ffff ffff ffff ffff ffff ................
000000f0: ffff ffff ffff ffff ffff ffff ffff ff0f ................
00000100: 5048 434d 0007 0002 0000 0e00 9503 0e00 PHCM............
00000110: 9003 0000 8000 0000 0000 0000 0000 0000 ................
00000120: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000130: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000140: 37f4 50b9 456a 82bf 44cf 1024 35f5 af3b 7.P.Ej..D..$5..;
00000150: 9397 2339 2ba1 212d 9943 4b36 f4e3 874e ..#9+.!-.CK6...N

And the one I extracted via innoextract starts like this

00000000: d3af 0be2 1499 4f4f 9537 3129 e090 eb3c ......OO.71)...<
00000010: 5000 0000 0000 0100 f084 8800 0000 0000 P...............
00000020: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000030: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000040: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000050: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000060: 78e5 8c8c 3d8a 1c4f 9935 8961 85c3 2dd3 x...=..O.5.a..-.
00000070: a084 8800 0000 0000 5f46 5648 fffe 0400 ........_FVH....
00000080: 4800 1eec 6000 0002 a084 8800 0100 0000 H...`...........
00000090: 0000 0000 0000 0000 ffff ffff ffff ffff ................
000000a0: ffff ffff ffff ffff b6aa f000 6802 00f8 ............h...
000000b0: d95f e99c 196e e740 9a8f ebad 7f78 e0c5 ._...n.@.....x..
000000c0: 5002 0000 3c02 0200 e889 9d0f 5992 764f P...<.......Y.vO
000000d0: a5af 0c89 e340 23df 3802 0000 0002 f10e .....@#.8.......
000000e0: 1474 71a7 16c6 7749 9420 8447 12a7 35bf .tq...wI. .G..5.
000000f0: de59 aa51 f2fd a34e bc63 875f b784 2ee9 .Y.Q...N.c._....
00000100: bd0a bca2 7da0 2f53 f808 c6b0 1b76 d316 ....}./S.....v..

If I can see correctly, I looked for the PHCM sequence in BIOS.cap and it looks like this (region starts at 00000310):
Otherwise, I have to delete everything up to line 0300 (including)

00000300: 00ee 606c 16c3 954c a684 cdc7 e703 3311 ..`l...L......3.
00000310: 07aa 0100 1800 80f8 0100 003e ffff ffff ...........>....
00000320: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000330: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000340: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000350: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000360: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000370: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000380: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000390: ffff ffff ffff ffff ffff ffff ffff ffff ................
000003a0: ffff ffff ffff ffff ffff ffff ffff ffff ................
000003b0: ffff ffff ffff ffff ffff ffff ffff ffff ................
000003c0: ffff ffff ffff ffff ffff ffff ffff ffff ................
000003d0: ffff ffff ffff ffff ffff ffff ffff ffff ................
000003e0: ffff ffff ffff ffff ffff ffff ffff ffff ................
000003f0: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000400: ffff ffff ffff ffff ffff ffff ffff ffff ................
00000410: ffff ffff ffff ff0f 5048 434d 0007 0002 ........PHCM....
00000420: 0000 0e00 9503 0e00 9003 0000 8000 0000 ................
00000430: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000440: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000450: 0000 0000 0000 0000 37f4 50b9 456a 82bf ........7.P.Ej..
00000460: 44cf 1024 35f5 af3b 9397 2339 2ba1 212d D..$5..;..#9+.!-
00000470: 9943 4b36 f4e3 874e 0000 0000 0000 0000 .CK6...N........

This looks more like the BIOS you uploaded to the forum.
However, it still does not match 8388608 bytes.
So I moved to the end of the file (extracted from the original BIOS (NTB)) and saw that at the end offset 007FFFF0. I deleted everything from offset 00800000.

00800000: 83fb 0076 2950 5152 b806 0000 800f a2c1 ...v)PQR........
00800010: e910 662b 0f66 8b5f 0466 03d9 5a59 580f ..f+.f._.f..ZYX.
00800020: b7db c1e3 0a3b c376 058b c30f 6ed8 5251 .....;.v....n.RQ
00800030: 2500 80ff ff0f bdc8 0f84 d100 0000 510f %.............Q.
00800040: b3c8 5060 b801 0000 000f a2c1 eb18 81e3 ..P`............
....

Now the file matches closely with what I extracted from NTB.

-rw-r--r-- 1 gusto gusto 8388608 okt 31 10:42 BIOS_test.cap

I edited the BIOS in the hex editor as it is written in # 29. However, it is not written anywhere that I have to cut the beginning and end of the file.
I am also attaching pictures and a file that I edited. It should match the one from volinakis (however md5sum doesn't match).
I don't have NTB at the moment, so I can't check if mine is correct.

[volinakis]

I would like to ask again.
Using innoextract in Linux, I extracted this from the exe file

-rw-rw-r-- 1 gusto gusto 8946928 dec 18 2019 BIOS.cap
-rw-rw-r-- 1 gusto gusto 55 dec 18 2019 default.rsp
-rw-rw-r-- 1 gusto gusto 524800 dec 18 2019 DosFlash.exe
-rw-rw-r-- 1 gusto gusto 7191544 dec 18 2019 SctWinFlash64.exe
-rw-rw-r-- 1 gusto gusto 465912 dec 18 2019 WinFlash64.exe

If you notice the BIOS.cap has 8946928 bytes. However, the file BIOS.bin.zip that you uploaded to the forum has 8388608 bytes.

-rw-r--r-- 1 gusto gusto 8388608 okt 29 11:21 BIOS.bin

Am I making a mistake somewhere when I open BIOS.cap in the hex editor?
Do I still need to do something with BIOS.cap?

read what i wrote in previous post: you HAVE TO edit BIOS.CAP in order to get right length. you are welcome.

[fmarquis]

Hello,
I read all this thread again and again, bought a.programer and managed to read my corrupted chip. I extracted all required data and put them on one of the template Bios from this forum.
But now I can't seem to write the chip with the new bios. I think that I may have burnt it :/ The software can't detect it.

What can I do ?
Buy a new chip and try to replace it on the motherboard ?
Is there a way to confirm that the current chip is burnt ?
Thanks

[gusto]

you have to use innoextract to get bios image from update. Then edit with any hex editor to get right length - 8.388.608 bytes. Then transfer DMI.

try this one:

I would like to ask again.
Using innoextract in Linux, I extracted this from the exe file

-rw-rw-r-- 1 gusto gusto 8946928 dec 18  2019 BIOS.cap
-rw-rw-r-- 1 gusto gusto      55 dec 18  2019 default.rsp
-rw-rw-r-- 1 gusto gusto  524800 dec 18  2019 DosFlash.exe
-rw-rw-r-- 1 gusto gusto 7191544 dec 18  2019 SctWinFlash64.exe
-rw-rw-r-- 1 gusto gusto  465912 dec 18  2019 WinFlash64.exe

If you notice the BIOS.cap has 8946928 bytes. However, the file BIOS.bin.zip that you uploaded to the forum has 8388608 bytes.

-rw-r--r-- 1 gusto gusto 8388608 okt 29 11:21 BIOS.bin

Am I making a mistake somewhere when I open BIOS.cap in the hex editor?
Do I still need to do something with BIOS.cap?

[gusto]

I used innoextractor and extracted bios.cap, but there was no match out of 8,388,608 bytes.
So I uploaded the one you gave me to the bios. I started NTB and it works great.

[volinakis]

Thank you. I followed your instructions in post #29.
First, I downloaded the official bios for my NTB from lenovo's website.
I'm not sure if I extracted the bios bin correctly from the exe file.
I used the 7zip program to extract. From the extracted files, it seems that bin will be this file [0] (6575 Kb). However, when I open file [0] in HxD, I don't like it at all (I am attaching file [0]).
Can you please check if [0] is really correctly extracted from the exe file?

you have to use innoextract to get bios image from update. Then edit with any hex editor to get right length - 8.388.608 bytes. Then transfer DMI.

try this one:

[gusto]

Thank you. I followed your instructions in post #29.
First, I downloaded the official bios for my NTB from lenovo's website.
I'm not sure if I extracted the bios bin correctly from the exe file.
I used the 7zip program to extract. From the extracted files, it seems that bin will be this file [0] (6575 Kb). However, when I open file [0] in HxD, I don't like it at all (I am attaching file [0]).
Can you please check if [0] is really correctly extracted from the exe file?

[peste]

S/N: YD04LKXG
Model: 81FB
Factory ID: GXSC

Do you still need some data?

read post# 28

[gusto]

S/N: YD04LKXG
Model: 81FB
Factory ID:  GXSC

Do you still need some data?

[peste]

I used flashrom in Linux for the dump. I read the bios 3 times and got the same dump files (verified via md5sum). I read the whole forum, but I'm afraid to edit the file in the hex editor so I don't mess something up.
My NTB is a Lenovo IdeaPad 330S-15ARR - 330S_ARR_V06. Winbound 25q64fws10 is written on the bios.
Could someone help me with bios editing?

post the S/N, etc.

[gusto]

I used flashrom in Linux for the dump. I read the bios 3 times and got the same dump files (verified via md5sum). I read the whole forum, but I'm afraid to edit the file in the hex editor so I don't mess something up.
My NTB is a Lenovo IdeaPad 330S-15ARR - 330S_ARR_V06. Winbound 25q64fws10 is written on the bios.
Could someone help me with bios editing?

[gusto]

Hello, I would like to ask a question. After a lot of problems with the delivery company, I finally received the programmer (see # 145 post). However, when I looked at the chip, I found out that it is not CH341A, but CH341B (the eshop declared CH341A).
Will this programmer also work?

[hoaca388]

Hi
Need help, with this laptop:
- Lenovo ideapad 330S-15ARR
- model name: 81FB
- s/n: YD05RC99
(ship: W25Q64FWSSIQ)

-Issues: laptop turn on but no image (black screen)
Thank you

Your original file is full of 00 bits, reread the chip.

[SMDFlea]

Thread merged with existing topic.

[aminsab]

Hi
Need help, with this laptop:
- Lenovo ideapad 330S-15ARR
- model name: 81FB
- s/n: YD05RC99
(ship: W25Q64FWSSIQ)

-Issues: laptop turn on but no image (black screen)
Thank you

[albologna]

READ POST #82..

Perfect. Working. Thank you

[peste]

Please Help IdeaPad 330S-15ARR
It boots but No Image
SN : PF1HYUDK
Attached Original BIOS

READ POST #82..

[albologna]

Please Help IdeaPad 330S-15ARR
It boots but No Image
SN : PF1HYUDK
Attached Original BIOS

[gusto]

I ordered this programmer and I am waiting for delivery. I've read this thread and now I'm confused 🤔

[SMDFlea]

I want to buy a programmer in a local e-shop. In NTB I have this BIOS 25q64fwsig. This BIOS supposedly works at 1.8V. Do I also need a 1.8V adapter for the programmer?
The eshop shows that the programmer also supports WINBOND W25Q64.

There`s more info about the CH341A here https://www.badcaps.net/forum/troubl...21#post1622421 .