BRAND DIGOO, Model DG-MYQ

[ghost]

I you find these appropriate, you can add them to the readme.

The serial (I have no picture) pins are by the side of the micros SD card. The pins are Rx Gnd Tx, and they are 3 little soldering pads with holes.

Telnet was enabled by default.

telnet 192.168.1.148
Trying 192.168.1.148...
Connected to 192.168.1.148.
Escape character is '^]'.

localhost login: root
Password: cxlinux
BusyBox v1.20.2 (2017-11-07 11:47:24 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# 

First: vi /home/wps_supplicant.conf
home folder is permanent and can be changed.

mount
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro,relatime)
proc on /proc type proc (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
/dev/mtdblock3 on /home type jffs2 (rw,relatime)
# 

vi /home/wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant
update_config=1
network={
ssid="YOUR_SSID"
key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
pairwise=TKIP CCMP
scan_ssid=1
group=CCMP TKIP WEP104 WEP40
psk="clear_text_password"
}
# 

Second: configure camera with the mobile app.
Disable the cloud access: commenting all as shown
./cloud.ini & ./cloud_oversea.ini

[SERVERINFO]
#server_name=arcsoft.com
#xmpp_server_ip=xmpp.icloseli.com.
#relay_server_ip=relayus-w.arcsoftcloud.com
#auto_update_server_ip=update.icloseli.com.
#lecam_purchase_server_ip=esd.icloseli.com.
#upns_pnserver=upns.icloseli.com.
#upns_xmpp_name=arcsoft.com
#upns_xmpp_ip=xmpp.icloseli.com.
##argus_api_server_ip=argus.icloseli.com.
#argus_server_ip=argus.icloseli.com.
#relay_server_domain_name=relay.icloseli.com.
#stun_server_ip=
#cloud_auth_server_name=api.icloseli.com.
#bell_server_ip=
# 

In config.cfg screw up the ID's

# cat ./config.cfg
devicename=Camera
username=youremail_form phone_registration@gmail.com
unifiedid=youremail_form phone_registration@gmail.com1552099689206
locale=1en_US
motionsensitivity=80
timezone=
cameraoffstauts=1
camerawifi=your_SSID
sounddetection=1
soundsensitivity=90
turnontime=0
unmutetime=0
hdvideo=1
cloudrecordtime=0
cameraratote=0
facedetection=0
tamperdetection=1
cloudrecordstatus=1
upnsdid=1555410
#cloudtoken=magic:****
cloudtoken=magic:screw_this-----
clouddid=SCREW_THIS
#clouddid=******
configmotiondetection=1
devled=1
devinfrared=1
devnightmode=2
checkupdateinterval=0
updateprestatus=0
volumemute=1
checkdisabledupdate=0
antiflicker=50
getrebootlog=0
updateid=
updatetype=0
updateversion=
secret=
notificationinterval=10
personcountsch=0
personstauts=0
personcounttime=0

Save.

Edit start.sh, Look for: <<<<

echo V > /dev/watchdog  ## if you don't want watchdog <<<<<<<<<<<
#/bin/wpa_supplicant -B B -Dwext -iwlan0 -c/home/wpa_supplicant.conf &
# exit # <<<<<  you can exit and run the /tmp/p2pcam   manually

cd /tmp
(
export CLOSELICAMERA_LOGMAXLINE=1000
./p2pcam 
echo -e '[data]\ntime = '`date +%s` > /home/reboot.time
if [ -f /tmp/firmware.bin ]; then
    /bin/sdc_tool -d $BOARD_ID /tmp/firmware.bin
    sync
#   reboot  ## if you don't want reboot <<<<<<<<<<<
else
    echo "Crashed ? dump log..."
    #killall -10 tees ## if you don't want killall <<<<<<<<<<<
fi
)&

If you did not run p2pcam you can configure your wifi form shell

/bin/wpa_supplicant -B -iwlan0 -Dwext -c /home/wpa_supplicant.conf &
ifconfig wlan0 192.168.1.233 netmask 255.255.255.0
route add default gw 192.168.1.1 wlan0

The camera wont access the cloud anymore.

[TungstenE2]

thx, will give this a try!

[TungstenE2]

I renamed start.sh via FTP and after reboot the DG-MYQ seems to be bricked.
Already tried reset button and several ways by using persitent hack or debug_cmd.sh to revert to original naming. Seems like nothing is working.

Anbody solved this issue?

[ghost]

Hi,
No I did not get that far, But I have a serial soldered just in case.
https://github.com/comarius/digoo-DG-MIQ-720p towards the bottom of the page.

[TungstenE2]

do you also power on USB in order to get VCC?

I have USB FTDI Adapter for flashing ESP. Should this work? How to adress cam using telnet in this way? I have done image of the camera using dd. Can I flash the image back to the camera using the serial connection? Can you guide me? Thx!

[ghost]

Hi, Here is how I did this. I did the soldering as soon I got the camera. I have the same FTDI. I did not connected the power to the serial. I went over the serial connection, then I ran in ti your git, and I found out that the telnet is available. Then I cut them [image: image.png] I did everything over the telnet then. You cannot upload over the serial. You can try different methods though. Do you get the shell over the serial or not? If yes, just vi there and edit and save the file you deleted. or you can share the rootfs onto a NFS I can give you more details, then change the files onto your shared drive on PC. If you dont get the shell do you get the u-boot prompt ? at u-boot you can try if you have the ums connect the USB as well to your PC connect the serial over serial at u-boot prompt you can try try: uboot> mmc rescan mmc list # see your mmc then try connect the USB as well to your PC connect the serial over serial at u-boot prompt you can try ums mmc MMC_BLOCK_# This if the ums is there should mount a drive onto your computer which is the emmc from the camera, If you need the missing file I can sent them to you.

…

On Sun, Feb 16, 2020 at 6:56 AM TungstenE2 ***@***.***> wrote: do you also power on USB in order to get VCC? I have USB FTDI Adapter for flashing ESP. Should this work? How to adress cam using telnet in this way? I have done image of the camera using dd. Can I flash the image back to the camera using the serial connection? Can you guide me? Thx! [image: 15818539870380] <https://user-images.githubusercontent.com/39955685/74604133-5d247c00-50bb-11ea-8a10-b62dc2e8938a.jpg> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7?email_source=notifications&email_token=AB5PRAJQQTJVFOZNEU2IJLTRDESWFA5CNFSM4G4WL65KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4EYQA#issuecomment-586697792>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5PRAKOCVJ5GSQADMD2IZ3RDESWFANCNFSM4G4WL65A> .

[TungstenE2]

Thx, the FTDI adapter shows up in Windows on USB serial port COM3.
How do I telnet to this COM3 using eg MobaXterm ? Tried like in Screenshot below.
Did you set the FTDI adapter to 5v or 3.5V?

[TungstenE2]

ok, I get something like this

[ghost]

Ohh you-re on windows. You don't telnet You use putty for serial communication, Connect over UART https://store.chipkin.com/articles/using-putty-for-serial-com-connections-hyperterminal-replacement/ The speed I don't remember you can try 9600 38400 115200, try all speed from Upper 115200 to lower 9600, until you see the shell. Then try to mount the nfs like in the section *get file system* @ https://github.com/comarius/digoo-DG-MIQ-720p I dont know how to do that on windows but you can find it out there. https://www.poftut.com/how-to-mount-nfs-share-in-linux-and-windows/ Let em know if you have any progress.

…

On Sun, Feb 16, 2020 at 11:38 AM TungstenE2 ***@***.***> wrote: Thx, the FTDI adapter shows up in Windows on USB serial port COM3. How do I telnet to this COM3 using eg MobaXterm ? Tried like in Screenshot below. Did you set the FTDI adapter to 5v or 3.5V? [image: grafik] <https://user-images.githubusercontent.com/39955685/74608617-09c62400-50e3-11ea-800f-036c4135d750.png> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7?email_source=notifications&email_token=AB5PRAM2766F5C7JNR2XOADRDFTXXA5CNFSM4G4WL65KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4LYVQ#issuecomment-586726486>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5PRAI6UPPDRCEEW3OM6ZLRDFTXXANCNFSM4G4WL65A> .

[ghost]

I have not seen your screen shot. THat's promising. Try different speeds for UART starting at 115200, then go lower until you see the right characters. 9600, 14,400, 19,200, 38,400, 57,600, and 115,200

…

On Sun, Feb 16, 2020 at 11:45 AM TungstenE2 ***@***.***> wrote: ok, I get something like this [image: grafik] <https://user-images.githubusercontent.com/39955685/74608752-231ba000-50e4-11ea-94c6-c9bddac21d4e.png> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7?email_source=notifications&email_token=AB5PRAPYIOS3OUWKZKJFDO3RDFUTLA5CNFSM4G4WL65KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4L6XA#issuecomment-586727260>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5PRAOZCQKGQB5P3GCRNT3RDFUTLANCNFSM4G4WL65A> .

[ghost]

digooo home folder

…

On Sun, Feb 16, 2020 at 11:48 AM Co M ***@***.***> wrote: I have not seen your screen shot. THat's promising. Try different speeds for UART starting at 115200, then go lower until you see the right characters. 9600, 14,400, 19,200, 38,400, 57,600, and 115,200 On Sun, Feb 16, 2020 at 11:45 AM TungstenE2 ***@***.***> wrote: > ok, I get something like this > [image: grafik] > <https://user-images.githubusercontent.com/39955685/74608752-231ba000-50e4-11ea-94c6-c9bddac21d4e.png> > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#7?email_source=notifications&email_token=AB5PRAPYIOS3OUWKZKJFDO3RDFUTLA5CNFSM4G4WL65KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4L6XA#issuecomment-586727260>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AB5PRAOZCQKGQB5P3GCRNT3RDFUTLANCNFSM4G4WL65A> > . >

[TungstenE2]

To be honest I give up. The pads are very small for my soldering and I tried serveral times to connect.
btw 5v soldering pad is on the other side just next to the 3 holes.

Also my SD card slot is broken.

So I declare this a brick. Not worth spending more time ob this cam.

Thx for your help.