v138 - Stuck in bootloop after flashing

11 posts / 0 new
Last post
komugi
komugi's picture
v138 - Stuck in bootloop after flashing

I've done it multiple times now, once with all settings in place, twice with NVRAM wipe -- it ends up booting once -- with tomato, when I change any settings, it starts resetting itself constantly. I had to use the USB TTL cable to de-brick it twice already... Went back to v137 -- all stable.

 

Is anyone having this issue with the v138 on r7000?

komugi
komugi's picture
on Shibby v138 btw.

on Shibby v138 btw.

RogueScholar
RogueScholar's picture
Yes, you're not alone. I'm

Yes, you're not alone. I'm unable to avoid an eventual bootloop on 138, though it'll often work for a day or so before succumbing. This is my second unbricking now, and I'm back to 137 once it's complete.

microchip
microchip's picture
Seems v138 is hit for some

Seems v138 is hit for some and miss for others. I'm not sure what causes this. My r7000 is doing just fine on v138

microchip
microchip's picture
If someone's experiencing

If someone's experiencing this on 138, do an NVRAM reset and see if you still have it

komugi
komugi's picture
@microchip - NVRAM reset does

@microchip - NVRAM reset does make it get out of the bootloop, however that only lasts until I change a setting -- FIrst one I usually change is in Basic/Wireless settings.

komugi
komugi's picture
Alright, for an update, on

Alright, for an update, on v138 -- I am able to replicate it successfully based on condition -- when my r7000 isn't connected to the modem (Arris SB6190/SB6183) it will boot without bootloop -- after it is completely booted up, reinsert the CAT cable to the cable modem, and it will acquire IP address and stay stable.

 

Now if it stays plugged into the Arris SB6190/SB6183 cable modem (not sure if it is because of the Arris modems or DHCP issues?) -- it will continue the bootloop

AWindowsKrill
AWindowsKrill's picture
I'm able to reproduce, just

I'm able to reproduce, just wish I saw this earlier, would have saved a few hours of trying to figure out what the hell happened, i'm on a TP-Link modem.

coldtech
coldtech's picture
I'm having kind of the same

I'm having kind of the same issue, I used Shibby on my r7000 before without issues but went back to stock for some time.

 

Now I reflashed Shibby with v138 including NVRAM wipe twice, but now the router reboots after anything between 5 and 30 minutes. This seems to happen with any version above 132 though, I tried all the newer ones without success.

 

Does anyone have a solution to this? NVRAM wipe does not seem to help.

 

I have it configured as Ethernet bridge at the moment, when using shibby before I think I used it as a regular access point.

komugi
komugi's picture
Seems like it is a bug on

Seems like it is a bug on v138 -- possibly due to new drivers. Won't be resolved with NVRAM wipe, I've tried multiple times, and decided to stay with v137 until Shibby releases his next version.

carpenv
carpenv's picture
I just flashed v138 and now I

I just flashed v138 and now I can't access the r7000.

I'm able to ping it just for few seconds at 192.168.1.1, then it reboots

Is there a way to go back via lan  or I have to buy the usb adaper and debrick it?

Tnx in advance.