1.1.5? well thats probably why. and what model us or non us? u didnt say
I can't verify now because I've flashed to 1.1.4. But, I think that it was a typo when I wrote 1.1.5 earlier. I'm pretty sure it came loaded with 1.1.4.168206.
I'm pretty sure that it's a US model. Bought in the US via Amazon.
Thank you. That looks over my head. I've used tftp to restore other routers to OEM. So, thought it might be the same (I didn't have to use serial. Just software: pumpKIN).
Anyway, on to the good news! Progress!
It looks like I now have dd-wrt installed which should be good news for others wanting to buy and flash in US right now (no idea of course if you will also get one with a workable firmware though).
This is what worked for me:
1. Flash to OEM firmware OLDER than 1.1.4.168206. I happened across a 1.1.3.166845
2. Restore factory defaults.
3. 30/30/30
4. Flash Kong's current factory-to-ddwrt build.
5. Enjoy.
My only concern now is that it worked for me on the very first flash. So, does that mean that stock FW is still on the second partition, waiting to mess something up at some point? Is that secure to have firmware on the second partition with a password of "admin"? Is there a way to wipe that partition or check that it has dd-wrt on it?
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Fri May 06, 2016 1:13 Post subject:
ubootenv get boot_part checks what partition its set on, ubootenv set boot_part 1 or 2 sets which partition to next boot off of. its not like a computer u cant access the other partition while its not running it, doesnt matter what ur login info is for the other ddwrt or stock fw image _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
ubootenv get boot_part checks what partition its set on, ubootenv set boot_part 1 or 2 sets which partition to next boot off of. its not like a computer u cant access the other partition while its not running it, doesnt matter what ur login info is for the other ddwrt or stock fw image
Thank you.
If I use ubootenv to switch to the other partition and it turns out to be oem, is there a way through oem firmware to switch back again?
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Fri May 06, 2016 2:48 Post subject:
flash back to ddwrt on it since u found a working solution, just flash whatever non encrypted stock fw that worked then flash ddwrt img, dont need to reset between do that after ddwrt is on it if u want. to go back to stock use the webrevert file.
backup the stock fw img in case linksys takes it down later in attempt to get everyone on fcc's encryption _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Thank you. That looks over my head. I've used tftp to restore other routers to OEM. So, thought it might be the same (I didn't have to use serial. Just software: pumpKIN).
Anyway, on to the good news! Progress!
It looks like I now have dd-wrt installed which should be good news for others wanting to buy and flash in US right now (no idea of course if you will also get one with a workable firmware though).
This is what worked for me:
1. Flash to OEM firmware OLDER than 1.1.4.168206. I happened across a 1.1.3.166845
2. Restore factory defaults.
3. 30/30/30
4. Flash Kong's current factory-to-ddwrt build.
5. Enjoy.
My only concern now is that it worked for me on the very first flash. So, does that mean that stock FW is still on the second partition, waiting to mess something up at some point? Is that secure to have firmware on the second partition with a password of "admin"? Is there a way to wipe that partition or check that it has dd-wrt on it?
I'm glad it worked out for you! A little late but maybe it will help someone in the future. I had a EA8500-WM with 8830-22537 Rev A00. I did this for my buddy as well and he had a EA8500 with Rev A00. I don't know the other numbers for his model.
To clarify--when I said manual login, I never connected the internet to the router. Once it was in factory default state I never let it complete its 'quick setup' procedure where it attempted to connect to the internet. I had to manually login using the admin/password credentials in the webgui in order to do anything. When I did attempt the flash it would always say it succeeded even when it appeared to boot back up as the old linksys firmware. Then after a couple tries, it said the flash succeeded and it actually did succeed.
flash back to ddwrt on it since u found a working solution, just flash whatever non encrypted stock fw that worked then flash ddwrt img, dont need to reset between do that after ddwrt is on it if u want. to go back to stock use the webrevert file.
backup the stock fw img in case linksys takes it down later in attempt to get everyone on fcc's encryption
Good advice. I backed up the set of relevant firmwares.
Too afraid to switch partitions though. I spent a lot of time getting it to this point. Given my limited knowledge in this area, I might just let sleeping partitions lie.
moonglows wrote:
I'm glad it worked out for you! A little late but maybe it will help someone in the future. I had a EA8500-WM with 8830-22537 Rev A00. I did this for my buddy as well and he had a EA8500 with Rev A00. I don't know the other numbers for his model.
To clarify--when I said manual login, I never connected the internet to the router. Once it was in factory default state I never let it complete its 'quick setup' procedure where it attempted to connect to the internet. I had to manually login using the admin/password credentials in the webgui in order to do anything. When I did attempt the flash it would always say it succeeded even when it appeared to boot back up as the old linksys firmware. Then after a couple tries, it said the flash succeeded and it actually did succeed.
Thank you. Definitely good information. With the 2x and 3x flash requirement, without having seen it work before, it's difficult to deduce whether or not a flash worked or if you're just on your first leg of the process. Knowing that it should say "success" can help someone move on to other variations if they get the "can't connect to router" message instead.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sat May 07, 2016 7:19 Post subject:
wheaton4prez wrote:
tatsuya46 wrote:
flash back to ddwrt on it since u found a working solution, just flash whatever non encrypted stock fw that worked then flash ddwrt img, dont need to reset between do that after ddwrt is on it if u want. to go back to stock use the webrevert file.
backup the stock fw img in case linksys takes it down later in attempt to get everyone on fcc's encryption
Good advice. I backed up the set of relevant firmwares.
Too afraid to switch partitions though. I spent a lot of time getting it to this point. Given my limited knowledge in this area, I might just let sleeping partitions lie.
moonglows wrote:
I'm glad it worked out for you! A little late but maybe it will help someone in the future. I had a EA8500-WM with 8830-22537 Rev A00. I did this for my buddy as well and he had a EA8500 with Rev A00. I don't know the other numbers for his model.
To clarify--when I said manual login, I never connected the internet to the router. Once it was in factory default state I never let it complete its 'quick setup' procedure where it attempted to connect to the internet. I had to manually login using the admin/password credentials in the webgui in order to do anything. When I did attempt the flash it would always say it succeeded even when it appeared to boot back up as the old linksys firmware. Then after a couple tries, it said the flash succeeded and it actually did succeed.
Thank you. Definitely good information. With the 2x and 3x flash requirement, without having seen it work before, it's difficult to deduce whether or not a flash worked or if you're just on your first leg of the process. Knowing that it should say "success" can help someone move on to other variations if they get the "can't connect to router" message instead.
this unit seems pretty unbrickable via serial connect. ive done it so i can guide u if u want.. (broken nightly build, i got "greedy" so...ya..) _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Posted: Tue May 10, 2016 23:45 Post subject: EA8500 JFFS2
Hey guys,
Wondering if you can help me out here. I just can't seem to figure out how to get JFFS working on my EA8500 with dd-wrt because I want to setup Pixelserv on it. I did it once about 5 or 6 years ago on a different router, and it was really easy back then, but now I just can't seem to get it to work correctly.
I tried turning it on in the administration section but all I get is:
Total / Free Size 1280.00 KB / 0
I also tried with an old USB 2.0 stick in the USB2|eSata port. Formatted it as ext2 and mounted it in the Services section and told it to mount the partition to /jffs and for disk info I get:
Diskspace /dev 0 / 512.0K 0%
Diskspace /jffs 1.3M / 0 100%
Diskspace /jffs 1.3M / 0 100%
I noticed Kohmei's post from February, and he talks about the webgui trying to mount the wrong mtd section, but I'm trying to mount a USB Drive, so I feel like I'm missing some other step somewhere. Can someone help me out or at least give me a shove in the right direction?
Thanks
PS: Forgot to mention I'm running DD-WRT v3.0-r29134 std (02/19/16). Will it help if I upgrade to a newer version maybe?
PPS: Upgrading to the newest release here ftp://ftp.dd-wrt.com/betas/2016/05-10-2016-r29621/linksys-ea8500/ seems to have me worse off than before. My Router is now stuck in a reboot loop it seems. Can't access via webgui, ssh nor ping. And the lights on the back seem to work normally for a bit and then cycle through left to right (which I'm assuming is a reboot).
