Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Wed Apr 01, 2020 16:08 Post subject:
kretex wrote:
kernel-panic69 wrote:
Ok, what about flashing 42617, doing all your normal configurations and not resetting when upgrading, did you try that?
r42617 boot normal with or without reset sir
Ok, I guess I need to be clearer. Flash 42617, do your normal router configurations, save, reboot. Flash the next or latest firmware version without resetting your configs to default and test to see if it will work correctly after flashing without resetting your configurations. Does this make sense? _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Ok, what about flashing 42617, doing all your normal configurations and not resetting when upgrading, did you try that?
r42617 boot normal with or without reset sir
Ok, I guess I need to be clearer. Flash 42617, do your normal router configurations, save, reboot. Flash the next or latest firmware version without resetting your configs to default and test to see if it will work correctly after flashing without resetting your configurations. Does this make sense?
yes I do according to your suggestion, upgrade next above 42617 until the last build without reset is still bootloop. Build r42617 and down boot normally.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Thu Apr 02, 2020 15:52 Post subject:
Ok. The only thing I can suggest is to flash 42617 with default configuration changing only the password, then upgrade to latest and then step by step doing your normal configuration to see what is causing the bootloop. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Ok. The only thing I can suggest is to flash 42617 with default configuration changing only the password, then upgrade to latest and then step by step doing your normal configuration to see what is causing the bootloop.
yup I was doing that too still bootloop.
fresh flash from uboot console or via webflash build r42681 r42729 r42747 r42803 r42819 all build was bricked/bootloop the router.
for now stay on latest beta build r42617 maybe the good solution
I hope tplink-mr series (tl-mr3420v1) user's read my post before they get brick/bootloop
luckily I have breed u-boot mod on my router
sorry for my bad english
Are you sure the modified bootloader isn't the problem?
I don't know sir.
I have been using u-boot breed for a long time since I use OpenWRT, and for almost 1 year using DDWRT and almost all beta releases I tried until I finally found Bootloop start from r42681-r42819 latest beta build.
btw how to make log when I flash the firmware sir?? sorry for noob question
You can either log via PuTTY or copy and paste. Latter is a little trickier to do, but it works. If I knew it wouldn't take a month to get to me, I'd say just send the damn thing here and let me get it sorted, but. Insert me screaming in the background, "WTF is this @#$%^&*! R9000 I ordered last month?!?!?" _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Posted: Wed Nov 08, 2023 3:49 Post subject: Still happening with r53915 (2023)
This still happening, I tried to flash r53915 of Nov. 11st 2023
This is the message from serial console
Code:
U-Boot 1.1.4 (Jan 25 2011 - 12:09:11)
AP99 (ar7241 - Virian) U-boot
DRAM:
sri
ar7240_ddr_initial_config(133): virian ddr1 init
#### TAP VALUE 1 = 0xf, 2 = 0x10 [0x0: 0x1f]
32 MB
id read 0x100000ff
sector count = 64
Flash: 4 MB
Using default environment
In: serial
Out: serial
Err: serial
Net: ag7240_enet_initialize...
No valid address in Flash. Using fixed address
No valid address in Flash. Using fixed address
Virian MDC CFG Value ==> 4
: cfg1 0xf cfg2 0x7014
eth0: 00:03:7f:09:0b:ad
eth0 up
Virian MDC CFG Value ==> 4
: cfg1 0xf cfg2 0x7214
eth1: 00:03:7f:09:0b:ad
ATHRS26: resetting s26
ATHRS26: s26 reset done
eth1 up
eth0, eth1
Autobooting in 1 seconds
## Booting image at 9f020000 ...
Uncompressing Kernel Image ... OK
