Linksys 32X oem firmware is out........

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.)
Goto page Previous  1, 2, 3 ... 6, 7, 8, 9, 10, 11  Next
Author Message
ghoffman
DD-WRT User


Joined: 03 Jan 2010
Posts: 451

PostPosted: Sun Oct 01, 2017 17:22    Post subject: Reply with quote
not to move this topic back to dd-wrt, but - has anyone been able to flash a stock wrt32x, (or more speciifcally a wrt3200acm converted to wrt32x with the above procedures), with the 9/27 factory-to-ddwrt.bin ?

from the stock firmware gui, i get an immediate 'invalid firmware' message if i leave it with the .bin extension. if i change the extgension to .img, the file, the image starts to upload but after about a minute i get an 'error flashing image' message. the router remains operational with stock firmware.

edit: already asked and aswered by inelliboy in the wrt3200acm thread:


Quote:
It will not flash from the WRT32X GUI for some reason, possibly the file size, apart from the bin extension which also prevents it.
Just use sysupgrade -n -v factory-to-ddwrt.bin


still the reason why is not clear
Sponsor
adi-brasov
DD-WRT User


Joined: 03 May 2017
Posts: 126

PostPosted: Sun Oct 01, 2017 17:53    Post subject: Reply with quote
Hi,
as i dont have serial cable i tried an succeeded to flash using only dd-wrt.
i used rango.img from download: http://www108.zippyshare.com/v/lgm43Bri/file.html , provided by @inteliboy on page 2 of this thread.
important : dd-wrt must be on part 1, since i cannot flash under 10mb because mtds are locked.
copy rango.img to /tmp using winscp.
the trick is to place rango.img at right possition (ie 132mb offset) :

#cd /tmp
#dd if=/dev/zero of=wrt32x.img bs=1048576 count=42
#cat rango.img >> wrt32x.img
#mtd erase mtd7
#mtd -f write wrt32x.img mtd7
#ubootenv set altnandboot 'setenv bootargs console=ttyS0,115200 root=/dev/mtdblock8 mtdparts=armada-nand:2048K(uboot)ro,128K(u_env),256K(s_env),256K@8064K(devinfo),123m@9m(firmware1),123m@132m(firmware2);nand read $defaultLoadAddr $altKernAddr $altKernSize; bootz $defaultLoadAddr'
#ubootenv set altKernAddr 0x8400000
#ubootenv set altFwSize 0x7b00000
#ubootenv set boot_part=2
#reboot

and it worked.

i tried using the wrt32x.img from linksys, extracting kernel and root and use them by appending to kernel null bytes until 3mb and appending root.but this not working (i think is something with rootfs, but i am working in blind without serial output).
tryng with linksys wrt32x image i had some fail to boot.but since u-boot primary boot is not altered (and mtdparts are the stock ones) i got back to dd-wrt easy with simple 3 power method Smile.

Can anyone tell if it is posible to sysupgrade to the same partition ?
ghoffman
DD-WRT User


Joined: 03 Jan 2010
Posts: 451

PostPosted: Sun Oct 01, 2017 19:52    Post subject: Reply with quote
on wrt32x converted from wrt3200acm:
forcing the factory-to-ddwrt.bin fails with 'platform image check' fail message.

the devinfo mtd partition shows
hw_version=48SAM203.SGD
modelNumber=WRT3200ACM-CA

i'm wondering if these need to be wrt32x values for firmware flashing to work?

does anyone have the corresponding values from a true wrt32X?
inteliboy
DD-WRT Novice


Joined: 03 May 2011
Posts: 42
Location: Poland

PostPosted: Sun Oct 01, 2017 20:03    Post subject: Reply with quote
mtd0 is the u-boot bootloader
what do you mean by soft-block?

@ghoffman

you need to flash via sysupgrade -v -n factory-to-ddwrt.bin
untill BrainSlayer figures out specifics of flashing via GUI.

Anyway good night to all, I'm too tipsy to think right now Very Happy

_________________
Router/AP: WRT3200ACM > WRT32X @ DD-WRT firmware
LINK: 100/10 Mbps
Irken Skoodge
DD-WRT Novice


Joined: 26 Aug 2013
Posts: 24

PostPosted: Sun Oct 01, 2017 20:29    Post subject: Reply with quote
I have a wrt32x and this is the partitions that are on it

dev: size erasesize name
mtd0: 00200000 00020000 "u-boot"
mtd1: 00020000 00020000 "u_env"
mtd2: 00040000 00020000 "s_env"
mtd3: 005c0000 00020000 "unused_area"
mtd4: 00040000 00020000 "devinfo"
mtd5: 07b00000 00020000 "kernel1"
mtd6: 07800000 00020000 "ubi"
mtd7: 07b00000 00020000 "kernel2"
mtd8: 07800000 00020000 "rootfs2"
mtd9: 00100000 00020000 "BBT"
ghoffman
DD-WRT User


Joined: 03 Jan 2010
Posts: 451

PostPosted: Sun Oct 01, 2017 20:36    Post subject: Reply with quote
@ intelliboy:
i used sysupgrade -n -v factory-to-ddwrt.bin. see below:

Code:

root@hoffman254:/tmp# sysupgrade -n -v factory-to-ddwrt.bin
Invalid image type.
Image check 'platform_check_image' failed.


@irken:
please look in your mtd4 dump - i'd be very interested in the values in strings for modelNumber and hw_version

thanks
cybrnook
DD-WRT User


Joined: 08 Jan 2014
Posts: 288

PostPosted: Sun Oct 01, 2017 20:46    Post subject: Reply with quote
try changing extension to .img
ghoffman
DD-WRT User


Joined: 03 Jan 2010
Posts: 451

PostPosted: Sun Oct 01, 2017 20:49    Post subject: Reply with quote
cybrnook wrote:
try changing extension to .img


tried that.

but figured it out:

i downgraded stock firmware from .208 to .201.
then the sysupgrade worked.

linksys is trying to plug holes it seems.
inteliboy
DD-WRT Novice


Joined: 03 May 2011
Posts: 42
Location: Poland

PostPosted: Sun Oct 01, 2017 20:51    Post subject: Reply with quote
try sysupgrade -n -v -F
are you sure you are flashing WRT32X DDWRT image and not WRT3200ACM?

EDIT: okay, thats weird

_________________
Router/AP: WRT3200ACM > WRT32X @ DD-WRT firmware
LINK: 100/10 Mbps
Irken Skoodge
DD-WRT Novice


Joined: 26 Aug 2013
Posts: 24

PostPosted: Sun Oct 01, 2017 21:06    Post subject: Reply with quote
ghoffman wrote:
@ intelliboy:
i used sysupgrade -n -v factory-to-ddwrt.bin. see below:

Code:

root@hoffman254:/tmp# sysupgrade -n -v factory-to-ddwrt.bin
Invalid image type.
Image check 'platform_check_image' failed.


@irken:
please look in your mtd4 dump - i'd be very interested in the values in strings for modelNumber and hw_version

thanks

hw_version=48SAM204.0GA
modelNumber=WRT32X
lanbudget
DD-WRT Novice


Joined: 22 May 2012
Posts: 16

PostPosted: Sun Oct 01, 2017 21:13    Post subject: Reply with quote
inteliboy wrote:
mtd0 is the u-boot bootloader


So, if I backup mtd0, I am backing up the u-boot? Strange, because mtd0 is 2048K while the WRT32X u-boot is only 955K


inteliboy wrote:

what do you mean by soft-block?

I mean that the stock firmware will be smart enough to check hw_version and modelNumber parameters and stop working if not WRT32X values.
ghoffman
DD-WRT User


Joined: 03 Jan 2010
Posts: 451

PostPosted: Sun Oct 01, 2017 23:14    Post subject: Reply with quote
i edited the mtd4 dump to update to the wrt32X values:
hw_version=48SAM204.0GA
modelNumber=WRT32X

however, mtd4 is write-protected and cannot be unlocked with the mtd tools in dd-wrt.

thus i think the process for complete transition of a wrt3200acm to wrt32x should also include modifying those devinfo values from the u-boot command line via serial port. as i recall, the devinfo partition can be modified using tools that are like the nvram tool:
devinfo set hw_version=48SAM204.0GA
devinfo modelNumber=WRT32X
devinfo commit
but dd-wrt does not have access to the devinfo tool.

more to come. thanks for all your help
adi-brasov
DD-WRT User


Joined: 03 May 2017
Posts: 126

PostPosted: Mon Oct 02, 2017 10:17    Post subject: Reply with quote
@Irken Skoodge , i understand that you have the black wrt32x.
can you pls post here a full output of fw_printenv ?
Irken Skoodge
DD-WRT Novice


Joined: 26 Aug 2013
Posts: 24

PostPosted: Mon Oct 02, 2017 13:32    Post subject: Reply with quote
adi-brasov wrote:
@Irken Skoodge , i understand that you have the black wrt32x.
can you pls post here a full output of fw_printenv ?


root@WRT32X:~# fw_printenv
CASset=max
MALLOC_len=5
MPmode=SMP
SMT-2D=NJ2PH22000D1X01
altFwSize=0x7B00000
altKernAddr=0x8400000
altKernSize=0x0600000
altnandboot=setenv bootargs console=ttyS0,115200 root=/dev/mtdblock8;nand read $defaultLoadAddr $altKernAddr $altKernSize; bootz $defaultLoadAddr
autoload=no
baudrate=115200
boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scr
boot_part_ready=3
bootargs_dflt=$console $nandEcc $mtdparts_lgcy $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel
bootargs_end=:-redacted-:255.255.255.0:Armada38x:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd_auto=stage_boot $boot_order
bootcmd_fdt=tftpboot 0x2000000 $image_name;tftpboot $fdtaddr $fdtfile;setenv bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_fdt_boot=tftpboot 0x2000000 $image_name; setenv bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_fdt_edit=tftpboot $fdtaddr $fdtfile; fdt addr $fdtaddr; setenv bootcmd $bootcmd_fdt_boot
bootcmd_lgcy=tftpboot 0x2000000 $image_name;setenv bootargs $console $nandEcc $mtdparts_lgcy $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootm $loadaddr;
bootdelay=3
cacheShare=no
console=console=ttyS0,115200
defaultLoadAddr=0x2000000
device_partition=0:1
disaMvPnp=no
eeeEnable=no
enaClockGating=no
enaCpuStream=no
enaFPU=yes
enaMonExt=no
enaWrAllo=no
eth1addr=-redacted-
eth1mtu=1500
eth2addr=-redacted-
eth2mtu=1500
eth3addr=-redacted-
eth3mtu=1500
ethact=egiga0
ethaddr=-redacted-
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fdt_skip_update=no
fdtaddr=0x1000000
fdtfile=armada-38x-modular.dtb
fileaddr=1000000
filesize=21E0000
firmwareName=venom.img
flash_alt_image=tftpboot $defaultLoadAddr $firmwareName && nand erase $altKernAddr $altFwSize && nand write $defaultLoadAddr $altKernAddr $filesize
flash_pri_image=tftpboot $defaultLoadAddr $firmwareName && nand erase $priKernAddr $priFwSize && nand write $defaultLoadAddr $priKernAddr $filesize
ide_path=/
image_name=uImage
initrd_name=uInitrd
ipaddr=192.168.1.1
kernel_addr_r=2080000
lcd0_enable=0
lcd0_params=640x480-16@60
lcd_panel=0
limit_dram_size=yes
loadaddr=0x02000000
loads_echo=0
mtddevname=uboot
mtddevnum=0
mtdids=nand0=armada-nand
mtdparts=mtdparts=armada-nand:2048K(uboot)ro,128K(u_env),256K(s_env),256K@8064K(devinfo),123m@9m(firmware1),123m@132m(firmware2)
mvNetConfig=mv_net_config=4,(-redacted-,0:1:2:3),mtu=1500
mv_pon_addr=-redacted-
nandEcc=nfcConfig=4bitecc
nandboot=setenv bootargs console=ttyS0,115200 root=/dev/mtdblock6;nand read $defaultLoadAddr $priKernAddr $priKernSize; bootz $defaultLoadAddr
netbsd_en=no
netmask=255.255.255.0
netretry=no
partition=nand0,0
pcieTune=no
pexMode=RC
priFwSize=0x7B00000
priKernAddr=0x0900000
priKernSize=0x0600000
pxe_files_load=:default.arm-armadaxp-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
ramdisk_addr_r=2880000
rootpath=/srv/nfs/
run_script=no
sata_delay_reset=0
sata_dma_mode=yes
script_addr_r=3000000
script_name=boot.scr
sd_detection_dat3=no
serverip=192.168.1.254
silent=1
standalone=fsload 0x2000000 $image_name;setenv bootargs $console $nandEcc $mtdparts_lgcy root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm 0x2000000;
stderr=serial
stdin=serial
stdout=serial
update_both_images=tftpboot $defaultLoadAddr $firmwareName && nand erase $priKernAddr $priFwSize && nand erase $altKernAddr $altFwSize && nand write $defaultLoadAddr $priKernAddr $filesize && nand write $defaultLoadAddr $altKernAddr $filesize
usb0Mode=host
usbActive=0
usbType=2
vxworks_en=no
yuk_ethaddr=-redacted-
boot_part=1
bootcmd=run nandboot
auto_recovery=yes
ghoffman
DD-WRT User


Joined: 03 Jan 2010
Posts: 451

PostPosted: Mon Oct 02, 2017 17:01    Post subject: Reply with quote
ghoffman wrote:
i edited the mtd4 dump to update to the wrt32X values:
hw_version=48SAM204.0GA
modelNumber=WRT32X

however, mtd4 is write-protected and cannot be unlocked with the mtd tools in dd-wrt.

thus i think the process for complete transition of a wrt3200acm to wrt32x should also include modifying those devinfo values from the u-boot command line via serial port. as i recall, the devinfo partition can be modified using tools that are like the nvram tool:
devinfo set hw_version=48SAM204.0GA
devinfo modelNumber=WRT32X
devinfo commit
but dd-wrt does not have access to the devinfo tool.

more to come. thanks for all your help


although mtd4 cannot be unlocked, mtd3 can be, and mtd4 is mapped to a segment within mtd3.

so - i editted the mtd3 partition to include the updated hw_version and modelNumber as above. i *think* this completes the conversion of wrt3200acm to wrt32x
Goto page Previous  1, 2, 3 ... 6, 7, 8, 9, 10, 11  Next Display posts from previous:    Page 7 of 11
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.) All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum