Lenovo IdeaPad 330S-15ARR - 330S_ARR_V06

[tyl85]

330S-15ARR Laptop (ideapad) - Type 81FB


Serial _ PF1KW1XA

Oh yeah!

[tyl85]

330S-15ARR Laptop (ideapad) - Type 81FB


Serial _ PF1KW1XA

Thanks, let's try this babe

[hoaca388]

Serial image was disappear

330S-15ARR Laptop (ideapad) - Type 81FB


Serial _ PF1KW1XA

[tyl85]

Serial number ?

Serial image was disappear

[hoaca388]

Same notebook 330s-15ARR
I have black screen solid white power button light
The lcd goes to dark (every pixel on) backlight off, no image

Thanks in advance

Serial number ?

[tyl85]

Same notebook 330s-15ARR
I have black screen solid white power button light
The lcd goes to dark (every pixel on) backlight off, no image

Thanks in advance

[javo]

Re: Lenovo IdeaPad 330S-15ARR - 330S_ARR_V06

hi every one
i had thesame Lenovo IdeaPad 330S-15ARR
it was no power

found out it has short on main power rail
ive tried to find the schematic for the board but failed.
so i tried to check what is heating up,, found the mosfet frying itself,,
ive removed the mosfet and injected 19v to the source( not sure yet if what type it is)
ive done this because there are so much short caps around that area,
then I found a bad cap very far from where i expected,
its a filter capacitor,
when removed, finaly i had charging light but no display, i suspected that i may had a currupted bios
I did used the posted bios from this thread but didnt work, i looked for another bios chip that is work for 1.8v then I rewrite my old bios file, the the thing came back to life

note: the mosfet is q5901
the bad cap has no label, i can send a photo
I will upload my bios file for the future errors related on bios. this is working bios file

Thank you very much.It worked for me.

[gusto]

I didn't say you were wrong.
I can't tell if it would work with

00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

but with

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

it definitely works

Sorry, I'm not an expert, that's why I'm asking.

[volinakis]

After some time I came back to it. I did
1. cut the beginning of the file from 0 to 0000317 (792 bytes) see
2. cut the end of the file, everything from offset 0080000 to the end 008881D0 (557528 bytes) see
3. I replaced DMI offset 001EE000 - 001EE220 (560 bytes) see
Now the file has the correct size 8388608 bytes, but the md5sum does not match your file

I searched for the problem and compared the files.

BIOS.my BIOS.volinakis differ: byte 11588379, line 126499

see offset 01EE220
my

00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

your

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

There is only a difference between 00 and FF. Either I am wrong or you are.

for sure i am wrong, that's why "I uploaded the one you gave me to the bios. I started NTB and it works great." ...

[gusto]

I don't even know where to start ... read bios guides of this forum, you don't even read what I wrote ...

my bios start with hex 0100 003e and you cut from 00ee 606c - 48 more bytes ...

After some time I came back to it. I did
1. cut the beginning of the file from 0 to 0000317 (792 bytes) see
2. cut the end of the file, everything from offset 0080000 to the end 008881D0 (557528 bytes) see
3. I replaced DMI offset 001EE000 - 001EE220 (560 bytes) see
Now the file has the correct size 8388608 bytes, but the md5sum does not match your file

I searched for the problem and compared the files.

BIOS.my BIOS.volinakis differ: byte 11588379, line 126499

see offset 01EE220
my

00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

your

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

There is only a difference between 00 and FF. Either I am wrong or you are.

[gusto]

Try to insert the clip several times and read again. As I already wrote, I managed to make a clip after 5-6 attempts. If you don't succeed, de-solder the chip with hot air and use an adapter.
I ordered this and there are more options than flashing the bios

BTW, I'm not an expert, I'm just a consumer too, just trying to help.

[fmarquis]

Yes I used a clip and the 1.8v adapter, it tooks maybe 7-8 tries for it to work and read something that wasn't full zeroes.
The extracted BIOS looked fine, I extracted the bytes required and put them on the template bios found on this thread.
But now, I can't seem to write it back :/
Is there a way to know if the chip is not dead ?
If it is, can I order a new blank chip and try to switch it on the motherboard (won't be easy with my fat fingers :/ )

[gusto]

Did you use a clip or another method for writing and reading?
I managed to clip after 5-6 attempts.

[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

hello, anyone with an advice on the best next step in my case ?
Thx

[SMDFlea]

hepl me disable ram onboard ideapad 330s-15arr

Try this --> https://www.badcaps.net/forum/troubl...20#post3232220 .If it doesn`t work or you can`t get it to work post your backup and laptop serial number

[mt418]

hepl me disable ram onboard ideapad 330s-15arr

[volinakis]

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


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.

I don't even know where to start ... read bios guides of this forum, you don't even read what I wrote ...

my bios start with hex 0100 003e and you cut from 00ee 606c - 48 more bytes ...

[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