Does it exist or not yet? Can i help to debug it?
It is similar, but not the same hardware (and would require a dedicated firmware image).
there was no interest so I abandoned... if you have high skill then it's possible... otherwise likely not worth your time investment...
even then without a PR you will have to perpetually build and patch to keep any local install going...
runs well tho...
Meh, ok, so it's not an option without a shitload of work
I also have a Netgear R7000 that I could use, but it has Broadcom drivers and they are closed source...
Thanks, any installation pointers?
-go to the web interface
-login via ssh with admin
-type 'touch /.iwantabrick'
-go back to the web interface and flash it
doubt it will brick anything... worst case scenario... you'll have to hook up uart/serial and repair a few uboot commands...
I tried it. After the upload I get a message that the patch is invalid
I reset the device to factory settings before trying + created the .iwantabrick file in the /
if you pm me the results of;
uname -a cat /proc/cmdline fdisk -l /dev/mmcblk0 cat /proc/mtd df -h strings /dev/mtd9 cat /proc/sys/kernel/syno_hw_version grep '^unique' /etc/synoinfo.conf
i can look into what's going on...
sure, tnx, in your pm box
edit: I can get on discord for a chat if you like as well.
need to check it out only ever tested on stock oem fw version
i'll do some research and likely upgrade mine (or you'd need to downgrade) to sort out what's going on...
this from your command line is pretty standout-ish doesn't exist on mine;
i'd heard they'd changed the 'pat'/factory logic so this adds-up...
edit: turns out I sent you the wrong pat file... just as well given your uboot env was slightly different... serial is exactly what was needed here
I did some research. Downgrading appears not to be possible.
meh... you were pretty fast with the commands...
manual install is fairly simple(and this way you know how to easily revert or fix stuff)... the pat / factory was just to make it look good...
serial kinda helps alot tho'...
Alright, you've convinced me. Ive disassembled the device and got my FTDI interface at 3.3v. I've found the UART interface at the bottom corner of the device next to the two push buttons.
PIN 1 = Vcc
PIN 2 = GND
PIN 6 = RX
What pin is TX?
Edit: I'm suspecting PIN 4 with the weird voltage. Testing...
see above from thread bugger didnt finish it
Ok. I have access indeed using GND = 2, RX = 6, TX = 4 connected.
I can halt on U-boot using ^C and have access to the root prompt as well.
Tell me what to do
ok first you want a 'raw' copy of 'printenv'
for your backup purposes
(pm me this too need to make sure nothing too odd there)
ok looks good... now we make a copy of bootmmc;
setenv bootoem 'mmc rescan;ext2load mmc 0:1 $kload zImage;ext2load mmc 0:1 $rload rd.bin;ext2load mmc 0:1 $dtbload dtb.dtb;bootipq; run bootresc' setenv bootcmdoem 'run syno_bootargs; run bootmmc'
( run printenv after that to check it was stored correctly )
Looks good indeed. added a bootoem env variable with an exact copy of bootmmc.
we want to create a command that will boot us from usb (for now)... !!! we won't 'saveenv' until this is done and tested...!!!
lemme lookup my notes...
this is only part of it still finding the rest... likely wont be perfect as 3am;
setenv wrtbootarg 'setenv bootargs console=ttyMSM0,115200n8 init=/sbin/init root=/dev/sda2 rootwait' setenv wrtgo 'usb start; ext2load usb 0:1 $kload kernel; run wrtbootarg; bootm $kload'
next bit is optional while testing... or you can just run 'run wrtgo':
setenv bootcmd 'run wrtgo'
!don't save this!
i will upload the 'kernel' and a rootfs.tar.gz ... you need to make a usb stick with;
-partition1 ext2 (just place kernel here)
-partition2 ext4 (extract rootfs.tar.gz here)