Bringing bricked Xiaomi STYJ02YM back to life

[utterances-bot]

Bringing bricked Xiaomi STYJ02YM back to life

https://blog.lupin.rocks/bringing-bricked-xiaomi-styj02ym-back-to-life/

[szerwi]

Continuing our conversation from Github. I've tried to change Tx with Rx. After that, before connecting USB to motherboard both (Rx and Tx) LEDs are on and after connecting only Tx LED is on. I went back to pin assignment from your photo but still no text on Linux.

[mLupine]

@szerwi The only thing I can suggest for now is to try different pin combinations. I was sure that the one I put on the picture was correct, but now I don't really know anymore. I'm still sure that the square one was RX - maybe I got the other two wrong. Try to change them - you're not connecting external power so there's no risk in trying different combinations.

[szerwi]

@mLupine you are right, you made a mistake on the photo :) The correct order is (from up to down): 1 - Tx in the vacuum (connected to Rx in the converter) 2 - GND 3 - Rx in the vacuum

After that everything went smooth and the vacuum is up and working :) Thank you so much for your help.

[mLupine]

@szerwi Damn, sorry for that. I already fixed the picture in the article.

Glad that I could help anyway. Enjoy your vacuum 😉

[Cjrff]

@szerwi How did you do "the uggly part" ? On which pin did you put your conductive tool ?

[szerwi]

@Cjrff I short circuited 2-3 pins from the up, in the place where the arrow on the picture is.

[mLupine]

According to the NAND chip's specs, it should be totally safe to connect the RE# pin to one of the Vss pins. In theory, it should not allow any data to be read from the chip without having to cause any short circuits. You can give it a try.

[szerwi]

@mLupine I've tried to update the vacuum to v47 software, but now I have "stuck on 80%" problem. Did you have that too? You said that you updated your vacuum to v47. Are there any known bugs in this version? BTW: While debricking my vacuum I downloaded package described as v46 on your previous tutorial, but the app shows that I have v45 version.

[mLupine]

@mLupine I've tried to update the vacuum to v47 software, but now I have "stuck on 80%" problem. Did you have that too? You said that you updated your vacuum to v47. Are there any known bugs in this version? BTW: While debricking my vacuum I downloaded package described as v46 on your previous tutorial, but the app shows that I have v45 version.

While I managed to execute the v47 update successfully, it doesn't mean that you'd be able to do so too. It's a completely different problem. Just follow the steps described in the other guide to work around the issue and force the update.

[szerwi]

@mLupine and what about my other 2 questions? Did you spot any bugs in v47 version? And did you described v46 package correctly, because my vacuum shows that current version is v45.

[mLupine]

@mLupine and what about my other 2 questions? Did you spot any bugs in v47 version? And did you described v46 package correctly, because my vacuum shows that current version is v45.

Well, I'm equally unsatisfied with the cleaning quality of v44, v46 and v47. The algorithms didn't get any worse (I don't think they could), but also didn't get any better. There were some new options added in v47, though, so I'd advise you to install it.

About the version - I'll check it later today. This, however, was the package that my vacuum tried to download when it wanted to update to v46.

[Cjrff]

According to the NAND chip's specs, it should be totally safe to connect the RE# pin to one of the Vss pins. In theory, it should not allow any data to be read from the chip without having to cause any short circuits. You can give it a try.

I'm not sure i well understand... I thought you want to disable flash memory at the beginning but if we connect RE pin to VSS pin, it will able "Read" aspect no ?

[mLupine]

According to the NAND chip's specs, it should be totally safe to connect the RE# pin to one of the Vss pins. In theory, it should not allow any data to be read from the chip without having to cause any short circuits. You can give it a try.

I'm not sure i well understand... I thought you want to disable flash memory at the beginning but if we connect RE pin to VSS pin, it will able "Read" aspect no ?

Not quite. When you connect those two together, the pin will always be in an active state, which should render it completely unusable and make any communication with the chip impossible.

[Cjrff]

Finally it works for me !! And you can add connecting pin 8 and 13 for the dirty part (little less dirty thus), seems that worked for me. So cool, thank you so much

[ricardocmc]

It would be great to make it possible to convert the v7 into v8. Apart from different languages and native support for European servers in the official Xiaomi home app, we'd be able to use smart assistants, i.e. Google home and Amazon Alexa. This would make the device so much better!!😁

[mLupine]

It would be great to make it possible to convert the v7 into v8. Apart from different languages and native support for European servers in the official Xiaomi home app, we'd be able to use smart assistants, i.e. Google home and Amazon Alexa. This would make the device so much better!!😁

Hold your horses for now, as it's not as straightforward as it might seem 😉

While yes, technically, flashing the V8 on to a V7 device should not be a problem with just some minor changes to the partition layout, it does not mean that you'd be able to use the device on European servers straight away. If you have ever tried to connect your V7 device to an EU server, you will never be able to connect that device to that server, even if you flash the V8 firmware onto it.

The reason for that is simple - every device connected to a Xiaomi cloud has a unique did/key/mac combination. When you pair your device with the cloud for the first time on each server, the server remembers what device used those keys and will not ever let you change it. The only way around that issue is to (a) not try to connect your new V7 devices to an EU server (which I think most of us did, hoping that magically it was going to work), or (b) change the did/key/mac combination on your device to another one, that has never been used.

And this is the funny bit - it doesn't even have to be a key from another vacuum. You can buy an air purifier, humidifier, or anything else that connects directly to Xiaomi's cloud (using Wi-Fi), extract the keys from there, and put them on your vacuum after flashing the V8 firmware. Only then you'd be able to connect it to an EU server (but the other device that you extracted the keys from will never work on that server).

And now you might be thinking — "if I have a new key combination and change the device identifier from V7 to V8 while staying on the V7 firmware, will I be able to connect to a European server?" Well, it would work. It does, in fact, work, I tried it a few days ago. The device can be connected this way, but the map will not be displayed in the app if you're using an iPhone or the unmodded version of the Android app. I think we can all agree that it makes it useless.

I haven't tried flashing V8 firmware onto my V7 vacuum yet, though. For now, I'm not doing anything about it as I have other projects to focus on. I'm not sure if it's worth the effort. To be honest, I don't think it is :)

[ricardocmc]

@mLupine, thank you for the explanation, I did not know about the keys/server pair. Although virtual assistants integration would be cool, at least it was cheaper than the international version😁 Still hopeful though🙂 And, of course, thank you for your great work on this little machine! You're a legend!

[paolinho91]

Hi @mLupine, really thanks for you work! It's simply awesome. I'm writing here because unfortunately i'm stuck at final step: when i run fastboot_test i obtain this

sunxi#fastboot_test
run usb fastboot
sunxi_fastboot_init
recv addr 0x41000000
send addr 0x5d2893e0
delay time 0
usb init ok

but when i execute in a new shell fastboot devices it doesn't return any. I tried with sudo but same fail. What can i try? Any advice? Thank you very much.

[mLupine]

Hi @mLupine, really thanks for you work! It's simply awesome. I'm writing here because unfortunately i'm stuck at final step: when i run fastboot_test i obtain this

sunxi#fastboot_test
run usb fastboot
sunxi_fastboot_init
recv addr 0x41000000
send addr 0x5d2893e0
delay time 0
usb init ok

but when i execute in a new shell fastboot devices it doesn't return any. I tried with sudo but same fail. What can i try? Any advice? Thank you very much.

If fastboot can't find your device, there has to be something wrong with the micro USB connection. First check, if the cable you're using is not a power-only one with the data pins not connected. Then, check if the device is visible in lsusb. If it is, then there has to be something wrong with either your fastboot version or device drivers in your system.

[Medtesh]

Thank you, now it’s clear why everything stopped, this is the problem of supplying only power for the microUSB connector, to facilitate the reset of depressed sessions and the safety of braking the boot process from Flash memory. we will try further. Thank you very much for your work and messages.

[paolinho91]

Then, check if the device is visible in lsusb. If it is, then there has to be something wrong with either your fastboot version or device drivers in your system.

Ok, i found a cable! I execute fastboot_test and now i obtain:

sunxi#fastboot_test
run usb fastboot
sunxi_fastboot_init
recv addr 0x41000000
send addr 0x5d288e78
delay time 0
usb init ok
set address 0x8

last row is new! So i found a new device in lsusb : Bus 001 Device 009: ID 1f3a:1010 Onda (unverified)

now, when i execute fastboot devices i obtain

$ sudo fastboot devices
Android Fastboot    fastboot

So i executed

fastboot flash boot boot.img

and i obtain:

target reported max download size of 33554432 bytes
sending 'boot' (4096 KB)...
OKAY [  0.745s]
writing 'boot'...
FAILED (remote: download: partition boot does not exist)
finished. total time: 0.766s

:(

[Medtesh]

It turned out to get deeper, but I have an archive from v3.5.3__0047, 46 closed on your site. All files were transferred and recorded, but I am not sure that my path to unpacking the archive was correct. now I can always easily and simply connect the command line to the screen through the USB converter. """""""""""""""""""""" [ 1.235]sunxi flash init ok fail to find part named env Using default environment

In: serial Out: serial Err: serial --------fastboot partitions-------- mbr not exist base bootcmd=run setargs_nand boot_normal bootcmd set setargs_nand key 0 cant find rcvy value cant find fstbt value no misc partition is found to be run cmd=run setargs_nand boot_normal sunxi_serial: sn_filename is not exist serial is: 27a7890c2009fffff583 Net: usb_etherWarning: failed to set MAC address

WORK_MODE_BOOT board_status_probe sunxi_bmp_logo_display sunxi secure storage is not supported private partition is not exist [ 1.324]Hit any key to stop autoboot: 0 cant find part named boot sunxi_flash - sunxi_flash sub-system

Usage: sunxi_flash read command parmeters : parmeters 0 : addr to load(hex only) parmeters 1 : the name of the part to be load [parmeters 2] : the number of bytes to be load(hex only) if [parmeters 2] not exist, the number of bytes to be load is the size of the part indecated on partemeter 1 boota: bad boot image magic, maybe not a boot.img? sunxi# """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" subsequent attempts to transfer files from the archive failed. my knowledge is very modest, I can accurately repeat what was written.

[mLupine]

Then, check if the device is visible in lsusb. If it is, then there has to be something wrong with either your fastboot version or device drivers in your system.

Ok, i found a cable! I execute fastboot_test and now i obtain:

sunxi#fastboot_test
run usb fastboot
sunxi_fastboot_init
recv addr 0x41000000
send addr 0x5d288e78
delay time 0
usb init ok
set address 0x8

last row is new! So i found a new device in lsusb : Bus 001 Device 009: ID 1f3a:1010 Onda (unverified)

now, when i execute fastboot devices i obtain

$ sudo fastboot devices
Android Fastboot  fastboot

So i executed

fastboot flash boot /home/paolo/Documenti/FuffyII/target_sys/boot.img

and i obtain:

target reported max download size of 33554432 bytes
sending 'boot' (4096 KB)...
OKAY [  0.745s]
writing 'boot'...
FAILED (remote: download: partition boot does not exist)
finished. total time: 0.766s

:(

During device boot, Uboot should print something like "fastboot partitions", followed by a list of partitions. Can you share it?

It turned out to get deeper, but I have an archive from v3.5.3__0047, 46 closed on your site. All files were transferred and recorded, but I am not sure that my path to unpacking the archive was correct. now I can always easily and simply connect the command line to the screen through the USB converter. """""""""""""""""""""" [ 1.235]sunxi flash init ok fail to find part named env Using default environment

In: serial Out: serial Err: serial --------fastboot partitions-------- mbr not exist base bootcmd=run setargs_nand boot_normal bootcmd set setargs_nand key 0 cant find rcvy value cant find fstbt value no misc partition is found to be run cmd=run setargs_nand boot_normal sunxi_serial: sn_filename is not exist serial is: 27a7890c2009fffff583 Net: usb_etherWarning: failed to set MAC address

WORK_MODE_BOOT board_status_probe sunxi_bmp_logo_display sunxi secure storage is not supported private partition is not exist [ 1.324]Hit any key to stop autoboot: 0 cant find part named boot sunxi_flash - sunxi_flash sub-system

Usage: sunxi_flash read command parmeters : parmeters 0 : addr to load(hex only) parmeters 1 : the name of the part to be load [parmeters 2] : the number of bytes to be load(hex only) if [parmeters 2] not exist, the number of bytes to be load is the size of the part indecated on partemeter 1 boota: bad boot image magic, maybe not a boot.img? sunxi# """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" subsequent attempts to transfer files from the archive failed. my knowledge is very modest, I can accurately repeat what was written.

This is completely fine. Now type fastboot_test and follow the guide.

[Cjrff]

Then, check if the device is visible in lsusb. If it is, then there has to be something wrong with either your fastboot version or device drivers in your system.

Ok, i found a cable! I execute fastboot_test and now i obtain:

sunxi#fastboot_test
run usb fastboot
sunxi_fastboot_init
recv addr 0x41000000
send addr 0x5d288e78
delay time 0
usb init ok
set address 0x8

last row is new! So i found a new device in lsusb : Bus 001 Device 009: ID 1f3a:1010 Onda (unverified)

now, when i execute fastboot devices i obtain

$ sudo fastboot devices
Android Fastboot  fastboot

So i executed

fastboot flash boot boot.img

and i obtain:

target reported max download size of 33554432 bytes
sending 'boot' (4096 KB)...
OKAY [  0.745s]
writing 'boot'...
FAILED (remote: download: partition boot does not exist)
finished. total time: 0.766s

:(

Somebody was facing same issue. He disconected all, turned off the vacuum and he restarted all from the beginning. Short circuit should not be necessary again and obviously, it works for him now.

[paolinho91]

During device boot, Uboot should print something like "fastboot partitions", followed by a list of partitions. Can you share it?

Hi, thanks for you reply. This is my boot: vacuum_boot.txt

[mLupine]

During device boot, Uboot should print something like "fastboot partitions", followed by a list of partitions. Can you share it?

Hi, thanks for you reply. This is my boot: vacuum_boot.txt

Can you also execute printenv in that Uboot shell and share the output? Is that a V7 vacuum or a V8?

[paolinho91]

Can you also execute printenv in that Uboot shell and share the output? Is that a V7 vacuum or a V8?

Of curse! I attached it. My vacuum is chinese version, so if i'm not wrong is a V7. vacuum_boot_printenv.txt

[mLupine]

Can you also execute printenv in that Uboot shell and share the output? Is that a V7 vacuum or a V8?

Of curse! I attached it. My vacuum is chinese version, so if i'm not wrong is a V7. vacuum_boot_printenv.txt

There's the problem. I don't know how it could happen, but for some reason Uboot has cleared partition layout from its env variables (see: partitions=). You can manually add the value of the var from some other V7 robot, but I don't think I have a copy of it 😟

[paolinho91]

There's the problem. I don't know how it could happen, but for some reason Uboot has cleared partition layout from its env variables (see: partitions=). You can manually add the value of the var from some other V7 robot, but I don't think I have a copy of it.

Ok...is there anyone that can help me with this? Thanks a lot

[Medtesh]

hi, I have one that is in the same state, there is another that has not been exposed to Ubot, there is a fully working robot. But my knowledge is only enough to repeat.

did you upload files from which firmware version?

пн, 13 апр. 2020 г. в 09:49, Pablo notifications@github.com:

There's the problem. I don't know how it could happen, but for some reason Uboot has cleared partition layout from its env variables (see: partitions=). You can manually add the value of the var from some other V7 robot, but I don't think I have a copy of it.

Ok...is there anyone that can help me with this? Thanks a lot

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mLupine/lupin.rocks/issues/2#issuecomment-612776940, or unsubscribe https://github.com/notifications/unsubscribe-auth/APEQEPUANGGLZQR66WDUIV3RMKYZFANCNFSM4MCE3NEA .

-- С Уважением Захаров Сергей +7-926-245-79-44

[mLupine]

hi, I have one that is in the same state, there is another that has not been exposed to Ubot, there is a fully working robot. But my knowledge is only enough to repeat. did you upload files from which firmware version? пн, 13 апр. 2020 г. в 09:49, Pablo notifications@github.com: …

If you follow the guide with the working robot, when you launch the Uboot shell, type printenv and share the output with us. Then, if you want to recreate the partition layout on the broken one, type saveenv partitions value_from_the_working_one

[Medtesh]

your tips in the output file https://yadi.sk/d/j_dkv-SZ6nWCvQ

[projek01]

@mLupine Hi, first off thank you very very much for taking the time to help all of us. Your work and time committed to this cause is awesome.

I am so far having issues getting either my Ubuntu or Windows PC from seeing the device as a "fastboot" device. Once I short the memory pins, I see the following added to lsusb: Bus 003 Device 039: ID 1f3a:efe8 Onda (unverified) V972 tablet in flashing mode.

fastboot devices shows nothing at the moment.

Is it possible that my vacuum is more bricked than everyone else's causing fastboot to not show up?

Thanks again!

[projek01]

Turns out, I was intermittently getting into the shell. Sometimes the sunxi# would show up and sometimes it would freeze. After trying a bunch of times, 1f3a:1010 finally showed up.

Due to the amount of times I had to try, I decided to play it safe and solder small wires to pin 8 and 13 suggested by mLupine. I extended pin 8 and 13 along with the serial connections into the battery compartment in the event that a firmware update bricks it again.

Thank you very much mLupine for doing this for the community. I definitely owe you a beer!

[paolinho91]

If you follow the guide with the working robot, when you launch the Uboot shell, type printenv and share the output with us. Then, if you want to recreate the partition layout on the broken one, type saveenv partitions value_from_the_working_one

Anybody with a working robot can help me? For me uboot doesn't see the robot's memory partitions :(

[duini]

Hi. I followed the first article and could get root access. Then a week later when i had a ttl-adapter i did the second part. My robot was still stuck on update before. But strangly after shorting the pins it worked again even without the fastboot part. I then updated successfully via the xiaomi app to v47. But later when I wanted to install valetudo, I noticed that i lost my root access. And I can't make it work again. I can pull the adb_shell and it is the origanl one again, but whenever I try to push the edited one i get this error:

adb: error: failed to copy 'adb_shell' to '/bin/adb_shell': remote I/O error
adb_shell: 0 files pushed, 0 skipped. 0.0 MB/s (56 bytes in 0.007s)

anyone has an idea what I'm doing wrong?

[Jesusek]

Hi, my symphtoms are: robot is ofline in app. When tried reset wifi then I was unnable to connect to robot (even couldnt see robots wifi net when tried to find it manually). But tried a lot of hard reset and after this cure robot is still ofline but capable to work when started by push start button, more over he still remember layout of flat and where is his base. What can be wrong? Thanks for all hard work which you already done by this two manuals. (sorry for my english) Any idea?

[avit88]

Hello, Thanks for help. When I make a short circuit, the boot loop stop but i don't have the # in the terminal. I can't tape any command

screen:

[ 4.922770] [hotplug]: try to kill cpu:3 failed! [ 4.929709] Rebooting in 5 seconds.. [ 9.940502] Restarting Linux version 3.4.39 (robotics@rs) (gcc version 5.2.0 (OpenWrt GCC 5.2.0 70-1-1) ) #567 SMP PREEMPT Thu Jun 20 02:54:56 UTC 2019 [ 9.940593]

Anyone have a idee ? Thanks for help

[avit88]

I have a new error when I flash boot.img :

[ 161.848]SUNXI_USB_FASTBOOT_SETUP [ 161.851]fastboot command = getvar:has-slot:boot [ 161.855]getvar [ 161.860]SUNXI_USB_FASTBOOT_SETUP [ 161.863]fastboot command = getvar:max-download-size [ 161.868]getvar response: OKAY0x02000000 [ 161.872]SUNXI_USB_FASTBOOT_SETUP [ 161.876]fastboot command = getvar:is-logical:boot [ 161.880]getvar [ 161.884]SUNXI_USB_FASTBOOT_SETUP [ 161.887]fastboot command = download:00400000 [ 161.892]download Starting download of 4194304 BYTES Starting download of 4 MB download response: DATA00400000 [ 162.076]fastboot transfer finish [ 162.088]SUNXI_USB_FASTBOOT_SETUP [ 162.091]fastboot command = flash:boot [ 162.095]flash sunxi fastboot download FAIL: partition boot does not exist probe it as a dram address sunxi fatboot download FAIL: it is not a dram address

[avit88]

The global session ... Maybe I burn my chip

uboot:nand version: 3 5003 20170418 1437
nand : get id_number_ctl fail, 1
uboot:nand info: 9590dac2 ffffff06 28c 0 0
nand : get sorting_flag fail, a
nand : get CapacityLevel fail, 5eb96e90
not burn nand partition table!
NB1 : nftl num: 1
 init nftl: 0
NB1 : NAND_LogicInit ok, result = 0x0
[      2.260]sunxi flash init ok
fail to find part named env
Using default environment

In:    serial
Out:   serial
Err:   serial
--------fastboot partitions--------
mbr not exist
base bootcmd=run setargs_nand boot_normal
bootcmd set setargs_nand
key 0
cant find rcvy value
cant find fstbt value
no misc partition is found
to be run cmd=run setargs_nand boot_normal
sunxi_serial: sn_filename is not exist
serial is: 2737890c2047fffff965
Net:   usb_etherWarning: failed to set MAC address

WORK_MODE_BOOT
board_status_probe
sunxi_bmp_logo_display
sunxi secure storage is not supported
private partition is not exist
[      2.348]Hit any key to stop autoboot:  0
sunxi#

Thanks for your help

[xengosam]

Hi @mLupine,

my viomi seems bricked after some silly file editing to run valetudo.. its locked in this state:

WORK_MODE_BOOT board_status_probe sunxi_bmp_logo_display sunxi secure storage is not supported [ 1.371]usb burn from boot delay time 0 [ 1.442]usb prepare ok usb sof ok vbus pc exist ,limit to pc [ 1.833]usb probe ok [ 1.835]usb setup ok ==== try to handshake ====
set address 0x2f [ 4.837]timer occur [ 4.872]do_burn_from_boot usb : have no handshake [ 4.877]Hit any key to stop autoboot: 0 fatload partition name: boot -> 2

Booting kernel from Legacy Image at 43800000 ...

Image Name: ARM OpenWrt Linux-3.4.39 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3340112 Bytes = 3.2 MiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK [ 5.156][mmc]: MMC Device 2 not found [ 5.160][mmc]: mmc not find,so not exit NAND_UbootExit NB1 : NAND_LogicExit nand release dma:0 reload config to 0x43000000 [ 5.164] Starting kernel ...

i already tried to flash the binaries to the robot, but no success .. it seems stuck..

do you have any idea how to fix it?

Thank you and best regards, xengosam

[mostafaalyousif]

i was using my robot (STY T J02YM) (note that i have an extra T in the middle) and my Mi Home App subscribed to beta updates .. then i got an update but i did not notice the version number yesterday, i hit update and it got stuck on 80% then disconnected from wifi then stuck on bootloop ..

can i use your method above to restore it? my previous version was 017 .. now i will be installing (from your instructions) 046 or 047 ..

the thing is i have other devices and i am on European server (Turkey to be more specific) .. my questions are: 1) will i still be able to use my robot on european servers? cuz my other devices are there and i cannot change my server 2) i was using my robot 017 with google assistant .. 046 and 047 can be used with google assistant? 3) which one do you recommend 046 or 047?

thanks a lot!

[mostafaalyousif]

@projek01 how did you manage to run the shell on Windows PC?

[avit88]

Putty software works well on windows. I use Google USB driver (ABD) : You have to manually select the ABD driver after "fastboot-test".

[mostafaalyousif]

@avit88 thanks alot .. do you have any comments on my previous long question? :):

will i still be able to use my robot on european servers? cuz my other devices are there and i cannot change my server i was using my robot 017 with google assistant .. 046 and 047 can be used with google assistant? which one do you recommend 046 or 047? thanks a lot!

[mostafaalyousif]

@avit88 what would be the host name or ip?

[avit88]

select serial and select the good serial line Com line and speed can be found in the device manager : look at cp210x.

[mostafaalyousif]

@avit88 thanks a lot .. i might need to ask something else :) so, sorry for the trouble from now .. have a good day/night

[brokenvacuum]

hey there, I am very rookie at such stuff but there is nothing to loose. so I decided to try this method to recover my broken vacuum.

so I need help :)

I connected vacuum to my pc (as explained above and only GND led is on). I could get lots of texts in linux which ended with "starting kernel..."

so that's time to short-circuit the pins. I tried to do it as explained above (with 2-3 pins) but I can't get any result on linux. there is some flashes on pins but no result. what should I do right now?

thanks a alot.

[mostafaalyousif]

@brokenvacuum many recommended short-circuiting pins 8 and 13 .. you might wanna give that a shot