At the end of the upgrade the webpage indicated that it was successful. But in reality I got a boot loop.
I have tried to use the tftp recovery with both the r44715(which was working before) and the stock firmware(ArcherC9v3_eu_1_2_0_up_boot_160713). The images have been renamed to ArcherC9v3_tp_recovery.bin and are read from the tftp server(hence, router is happy with the name) and I guess the router tries to flash it, but the result is the same: boot loop.
[I know, it is weird that my c9v4 asks for c9v3 recovery images. I think it might be a development typo when copy-pasting.]
Do you have any suggestions on how to fix this?
If I have no other option than using the serial connection, is there any guide for c9v4/c9v3?
Thank you very much, dale_gribble39.
The procedure described there worked well. It is suitable for a bricked c9v3/c3v4 no matter what caused it. (i.e. not just for jffs2 bug)
That is a definite possibility. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Thu Sep 08, 2022 13:37 Post subject:
ndom wrote:
I suspect the boot loop is caused by the reset to factory settings because:
while running r44715 I issued through the console `nvram erase && reboot` Result: successful factory reset
in the upgrade from r44715 to r49866 I selected "After flashing, reset to Default Settings". Result: boot loop
in the upgrade from r44715 to r50057 I did not select "After flashing, reset to Default Settings". Result: successful upgrade
in the upgrade from r44715 to r50057 I did select "After flashing, reset to Default Settings". Result: boot loop
while running r50057 I issued through ssh `nvram erase && reboot` Result: boot loop
Please feel free to check the attached boot logs.
Does this have anything to do with jffs2 being enabled by default in the recent firmware builds?
Is there any solution to factory reset without bricking the router when running the latest firmwares?
disconnect the uart. it crashed in the serial driver
in addition. this is a wanted reboot. the reboot happens just once and is normal while reconfiguration if you start the device from a old configuration. so log is incomplete. since it doesnt show the second boot _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
I see that you flashed the "fix" .bin file, but never entered "go" for the device to reprogram itself or did anything to finish recovery. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
What gives you this idea? Its not enabled by default afaik.
It is my guessing since jffs2 is listed in the wiki as the main brick culprit. What other things do you think can brick the router on a simple factory reset?
dale_gribble39 wrote:
I see that you flashed the "fix" .bin file, but never entered "go" for the device to reprogram itself or did anything to finish recovery.
If you are referring to the latest lines in the log file, I disconnected the UART before flashing the stock firmware. [hence, no more logs] The router has been recovered successfully, no problem with that.
You may think I'm obsessive, but please also check your power supply, since it has previously been reported that bootloop was in fact due to a lack of power, ie voltage dropping way below nominal voltage at startup, because under certain conditions, device was asking more amperage than rated.
So, if you can, please live check input voltage while running, it would be great.
You may think I'm obsessive, but please also check your power supply, since it has previously been reported that bootloop was in fact due to a lack of power, ie voltage dropping way below nominal voltage at startup, because under certain conditions, device was asking more amperage than rated.
So, if you can, please live check input voltage while running, it would be great.
This never occurred me...but I don't have any other more powerful power supply, all the TP-Link's and Asus I have are all rated the same voltage/amperage, and in the past I tested with a different power supply and the boot loop persisted.
Today I also gave my 5c on another thread also regarding a C9 and posted the issues I found with this device.
Today I have made another attempt to factory reset my c9v4 with the goal of measuring the voltage. Since there was a new build (r50176) I have tried it. The big news is that the rooter does not enter the boot loop anymore when resetting it to factory settings.
Phil9992 wrote:
You may think I'm obsessive, but please also check your power supply, since it has previously been reported that bootloop was in fact due to a lack of power, ie voltage dropping way below nominal voltage at startup, because under certain conditions, device was asking more amperage than rated.
So, if you can, please live check input voltage while running, it would be great.
I have also checked the voltage and it remains stable at 12.15.
