Router will not factory reset and settings are frozen, Any ssh nuke code or ways to fix this. ax 86u pro

[Jack-Sparr0w]

Don't know any way of fixing this. about to buy new router. everything in log says read only. tried to nuke with ssh and don't know nuke code for ax86u pro. no format option for ssh. like wtf. Im feeling pretty sick from all of this.

 

[degrub]

i would try multiple factory resets. unplug the router for 10 minutes between attempts.

 

[Jack-Sparr0w]

Its cooked Im really depressed. nothing is gonna fix this i tried

 

[degrub]

out of warranty ?

did you try the other reset methods as well ?

 

[kstamand]

SSH into router and nvram erase; nvram commit; reboot not work for resetting your router?

Or possibly the Asus firmware rescue utility - https://www.asus.com/us/support/faq/1000814/?

 

[Twiglets]

It is sounding like the jffs filesystem is broken/damaged in some way. (Guess !!!???)
You can check the status of the Memory Technology Devices (MTD) subsystem in the router using mtd-utils.

THIS IS GOING VERY LOW LEVEL AND VERY RISKY IF YOU DO NOT UNDERSTAND WHAT YOU ARE DOING !!!!!
SORRY I AM NOT AN EXPERT AND CANNOT HELP IF YOU BREAK THINGS, SO TAKE CARE AND READ EVERYTHING BEFORE YOU JUMP IN.

There are others on this site who know much more.


At a minimum you can run 'mtdinfo --all' to list all the mtd devices and their statuses.

One of the mtd devices will be 'jffs2' which the '/jffs' filesystem is mounted on.

I get on my RT-AX86U_Pro the following:


mtd12
Name: jffs2
Type: ubi
Eraseblock size: 126976 bytes, 124.0 KiB
Amount of eraseblocks: 413 (52441088 bytes, 50.0 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
Character device major/minor: 90:24
Bad blocks are allowed: false
Device is writable: true

Question:
What do you get on your Router ... It may help someone to identify the problem ?

You can, in extremis, try to reformat the jff2 device and the following may help you to do this.

Fix full /jffs without factory reset [Dates back to 2020 from a User called toaruScar]

^^^^^^^ contains instructions to to reconstruct a JFFS2 system BUT this would be at your own risk !!!

I have never tried it and cannot say it will work, just trying to give you some information that may help.

===================================================================================
I WILL REPEAT DO NOT DO ANYTHING IF YOU DO NOT UNDERSTAND WHAT YOU ARE DOING !!!
===================================================================================

Please do join in, if you can help @Jack-Sparr0w or correct me if I am wrong.

 

[dave14305]

I bookmarked Merlin’s posts in this thread in case a crisis ever hit my router.

Solved - GT-AX6000 Write Protected aka Borked

"The Griswald Kid Did It Again" After the alpha/beta testing Q4 2023, I was doing a Factory Restore so I could have a fresh RMerlin install. After doing the Factory Restore, then a usb drive format a command asking "do you want to make this drive write protected?", and clicking Y borked my 6000...

www.snbforums.com

 

[Twiglets]

All related !!!
Via the magic of Google without any nasty 'AI' involved at all !!!


UBIFS is a new flash file system developed by Nokia engineers with help of the University of Szeged. In a way, UBIFS may be considered as the next generation of the JFFS2 file-system.

JFFS2 file system works on top of MTD devices, but UBIFS works on top of UBI volumes and cannot operate on top of MTD devices. In other words, there are 3 subsystems involved:

• MTD subsystem, which provides uniform interface to access flash chips. MTD provides an notion of MTD devices (e.g., /dev/mtd0) which basically represents raw flash;
• UBI subsystem, which is a wear-leveling and volume management system for flash devices; UBI works on top of MTD devices and provides a notion of UBI volumes; UBI volumes are higher level entities than MTD devices and they are devoid of many unpleasant issues MTD devices have (e.g., wearing and bad blocks); see here for more information;
• UBIFS file system, which works on top of UBI volumes.

See http://www.linux-mtd.infradead.org/doc/general.html [Everything you wanted to know about MTD, UBI, UBIFS et al.

 

[kstamand]

@Jack-Sparr0w, there’s a number of options and good information from @Twiglets and @dave14305. Hopefully, one / some of the offered options helps you fix your current circumstances and avoid having to buy another router. Best of luck!!

 

[Clark Griswald]

I bookmarked Merlin’s posts in this thread in case a crisis ever hit my router.

Solved - GT-AX6000 Write Protected aka Borked

"The Griswald Kid Did It Again" After the alpha/beta testing Q4 2023, I was doing a Factory Restore so I could have a fresh RMerlin install. After doing the Factory Restore, then a usb drive format a command asking "do you want to make this drive write protected?", and clicking Y borked my 6000...

www.snbforums.com

FYI our GT-AX6000 is still going strong! Thank You to all Forum Members and especially RMerlin for breathing life back into my borking of our 6000!

 

[Jack-Sparr0w]

rm -rf /jffs/scripts/*
rm: can't remove '/jffs/scripts/dnsmasq.postconf': Read-only file system
rm: can't remove '/jffs/scripts/firewall': Read-only file system
rm: can't remove '/jffs/scripts/firewall-start': Read-only file system
rm: can't remove '/jffs/scripts/init-start': Read-only file system
rm: can't remove '/jffs/scripts/killmon.sh': Read-only file system
rm: can't remove '/jffs/scripts/post-mount': Read-only file system
rm: can't remove '/jffs/scripts/pre-mount': Read-only file system
rm: can't remove '/jffs/scripts/service-event': Read-only file system
rm: can't remove '/jffs/scripts/services-start': Read-only file system
rm: can't remove '/jffs/scripts/services-stop': Read-only file system
rm: can't remove '/jffs/scripts/unmount': Read-only file system

 

[Jack-Sparr0w]

mtdinfo --all
Count of MTD devices: 13
Present MTD devices: mtd0, mtd1, mtd2, mtd3, mtd4, mtd5, mtd6, mtd7, mtd8, mtd9, mtd10, mtd11, mtd12
Sysfs interface supported: yes

mtd0
Name: brcmnand.0
Type: nand
Eraseblock size: 131072 bytes, 128.0 KiB
Amount of eraseblocks: 2048 (268435456 bytes, 256.0 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
OOB size: 108 bytes
Character device major/minor: 90:0
Bad blocks are allowed: true
Device is writable: true

mtd1
Name: loader
Type: nand
Eraseblock size: 131072 bytes, 128.0 KiB
Amount of eraseblocks: 16 (2097152 bytes, 2.0 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
OOB size: 108 bytes
Character device major/minor: 90:2
Bad blocks are allowed: true
Device is writable: true

mtd2
Name: image
Type: nand
Eraseblock size: 131072 bytes, 128.0 KiB
Amount of eraseblocks: 2016 (264241152 bytes, 252.0 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
OOB size: 108 bytes
Character device major/minor: 90:4
Bad blocks are allowed: true
Device is writable: true

mtd3
Name: crashlog
Type: nand
Eraseblock size: 131072 bytes, 128.0 KiB
Amount of eraseblocks: 4 (524288 bytes, 512.0 KiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
OOB size: 108 bytes
Character device major/minor: 90:6
Bad blocks are allowed: true
Device is writable: true

mtd4
Name: metadata1
Type: ubi
Eraseblock size: 126976 bytes, 124.0 KiB
Amount of eraseblocks: 0 (1280 bytes, 1.2 KiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
Character device major/minor: 90:8
Bad blocks are allowed: false
Device is writable: true

mtd5
Name: metadata2
Type: ubi
Eraseblock size: 126976 bytes, 124.0 KiB
Amount of eraseblocks: 0 (1280 bytes, 1.2 KiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
Character device major/minor: 90:10
Bad blocks are allowed: false
Device is writable: true

mtd6
Name: bootfs1
Type: ubi
Eraseblock size: 126976 bytes, 124.0 KiB
Amount of eraseblocks: 85 (10878392 bytes, 10.3 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
Character device major/minor: 90:12
Bad blocks are allowed: false
Device is writable: true

mtd7
Name: rootfs1
Type: ubi
Eraseblock size: 126976 bytes, 124.0 KiB
Amount of eraseblocks: 462 (58662912 bytes, 55.9 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
Character device major/minor: 90:14
Bad blocks are allowed: false
Device is writable: true

mtd8
Name: bootfs2
Type: ubi
Eraseblock size: 126976 bytes, 124.0 KiB
Amount of eraseblocks: 83 (10601936 bytes, 10.1 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
Character device major/minor: 90:16
Bad blocks are allowed: false
Device is writable: true

mtd9
Name: rootfs2
Type: ubi
Eraseblock size: 126976 bytes, 124.0 KiB
Amount of eraseblocks: 403 (51171328 bytes, 48.8 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
Character device major/minor: 90:18
Bad blocks are allowed: false
Device is writable: true

mtd10
Name: data
Type: ubi
Eraseblock size: 126976 bytes, 124.0 KiB
Amount of eraseblocks: 166 (21078016 bytes, 20.1 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
Character device major/minor: 90:20
Bad blocks are allowed: false
Device is writable: true

mtd11
Name: defaults
Type: ubi
Eraseblock size: 126976 bytes, 124.0 KiB
Amount of eraseblocks: 67 (8507392 bytes, 8.1 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
Character device major/minor: 90:22
Bad blocks are allowed: false
Device is writable: true

mtd12
Name: jffs2
Type: ubi
Eraseblock size: 126976 bytes, 124.0 KiB
Amount of eraseblocks: 413 (52441088 bytes, 50.0 MiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 2048 bytes
Character device major/minor: 90:24
Bad blocks are allowed: false
Device is writable: true

 

[Jack-Sparr0w]

Ended up buying a new router, be careful with VLAN

 

[bennor]

Another suggested method to dealing with the dreaded read-only JFFS.
https://www.snbforums.com/threads/j...annot-format-restore.85631/page-4#post-923419