I am in the process of checking commits between 40400 and 40439 to see what the possible culprit is, well, I am trying, but svn is choking on it's own vomit.
Starting program at 0x00008000
Uncompressing Linux...
XZ-compressed data is corrupt
-- System halted
And there we have it. Thanks for posting that info.
now start router and within 10 seconds it will load the file to memory.
now wait and now you can get into openwrt probably trough 192.168.1.1 (in browser) use username root and pw admin and now I could load an old dd-wrt version.
I hope this will help you too.
Cant believe I got this working again by myself
Thanks, I tried and failed though, it wouldn't seem to do anything in tftp64. Is there anything else I should be doing in tftp64? The led on router lights up when the lan cable is connected.
now start router and within 10 seconds it will load the file to memory.
now wait and now you can get into openwrt probably trough 192.168.1.1 (in browser) use username root and pw admin and now I could load an old dd-wrt version.
I hope this will help you too.
Cant believe I got this working again by myself
Thanks, I tried and failed though, it wouldn't seem to do anything in tftp64. Is there anything else I should be doing in tftp64? The led on router lights up when the lan cable is connected.
That was the same with me. But you have to set your adapter in windows to the right ipaddresses as I subscripted earlier. If the vmlinux file is in the same folder you just have to start te program and go to logviewer and restart program. You dont have to do anything in tftp64 because your router should as folder the file itself. good luck trying.
Joined: 08 May 2018 Posts: 14244 Location: Texas, USA
Posted: Sat Jul 27, 2019 14:58 Post subject:
tinkeruntilitworks wrote:
its my bad for flashing before coming here
its my bad for not knowing how to recover
why is it still posted bricking routers?
For reference, I presume. They usually do not remove the forum post so people will hopefully see the post and heed the warnings. And I just love how the "oh, it's nothing, it affects some units, but not all" eventually winds up with a bricking build because of the initial kernel panic I reported a while back. But, again, I have no glue
its my bad for flashing before coming here
its my bad for not knowing how to recover
why is it still posted bricking routers?
For reference, I presume. They usually do not remove the forum post so people will hopefully see the post and heed the warnings. And I just love how the "oh, it's nothing, it affects some units, but not all" eventually winds up with a bricking build because of the initial kernel panic I reported a while back. But, again, I have no glue
Somehow, I knew that kernel panic on reboot and those error messages would eventually bite someone in the ass.
if im able to recover or get another router
should i get a build before this then? or would i be missing out on an important security update? the previous build seemed to work fine but i don't know about under the hood
Posted: Sat Jul 27, 2019 17:48 Post subject: R8000 bricked too
Hi,
first post here on this forum. Been only reading it so far, while diving in to the DD-WRT stuff.
Reporting an R8000 as bricked by Build 40439.
Same same.
I will try to recover it (tomorrow) while I am running on the backup unit. I am not sure I can contribute much except stating that the R8000 also doesn't like this build, but if you have anything you would want me to test, i can do, since I now have two of those things (just got a used one for a few bucks). Unfortunately i have no serial interface hardware to go down that road, but I am gladly taking any other "good ideas". Thanks.
Joined: 08 May 2018 Posts: 14244 Location: Texas, USA
Posted: Sat Jul 27, 2019 18:23 Post subject:
Yeah, I didn't have serial recovery pieces and parts until my first brick. The last sentence of the warning in the OP up top in red is there for a reason. I found out the hard way
Yeah, I didn't have serial recovery pieces and parts until my first brick. The last sentence of the warning in the OP up top in red is there for a reason. I found out the hard way
All good, not complaining. I knew what was coming and I have had a few "soft bricks" on older Netgears. Never needed serial. TFTP was always enough. Not this time though. Guess now its just my turn. _________________ Not a pro - pleez don't hit me, just here to get halp pleez and help wherever I can.
Posted: Sat Jul 27, 2019 20:43 Post subject: Re: New Firmware
labrok wrote:
Has anyone tgried the new firmware r40443? I am a bit afraid to try it again if anyone do succesfull flash inform us guys!
yea tis working on RT-N12D1 / E2500 / E1200v2
The RT-N12D1 is only one I run 24/7 and he is just a WAP... all good.
Same ol VAP problem --- I tested on the others.
Joined: 08 May 2018 Posts: 14244 Location: Texas, USA
Posted: Sat Jul 27, 2019 21:05 Post subject: Re: New Firmware
mrjcd wrote:
labrok wrote:
Has anyone tgried the new firmware r40443? I am a bit afraid to try it again if anyone do succesfull flash inform us guys!
yea tis working on RT-N12D1 / E2500 / E1200v2
The RT-N12D1 is only one I run 24/7 and he is just a WAP... all good.
Same ol VAP problem --- I tested on the others.
So, it doesn't break Broadcom MIPS? I guess I'll open a new build thread, since nobody else has yet
@labrok, if THIS build only breaks ARM, then I wouldn't bother as I have seen no commits to revert what I think broke things. Just my $0.02
Last edited by kernel-panic69 on Sat Jul 27, 2019 21:24; edited 3 times in total