JioFiber Root Access [How to] [with Proof]

  • Thread starter Thread starter itsyourap
  • Start date Start date
  • Replies Replies 52
  • Views Views 13,732
I have an really old jio fibre router which has old firmware but the guide you mentioned is updated to newer firmwares and the old guide links are broken and in the new guide the way of getting key.txt from router is not working. POST request is working but i’m not getting any key in the Pendrive. Can anyone please share old guide to do this? and if i somehow got this working on old router can i change to old router myself or request jio people to use my old router router?
 
i got the key.ext from the new method but im unable to decrypt the backup. getting bad decrypt on firmware JCOW411_R2.30.2 any help would be appreciated
 
@f0r3he4d I don't know if this is still relevant, I'm on JCO404 Firmware R3.7, things have really gone bad in this firmware to the point that I'm searching all this and trying them all, the key.txt cannot decrypt the .ENC file in my case too, but what worked for me is the Keyguesser.py script, with that I'm able to decrypt/encrypt the *.enc file, but when I try to restore the enc file modified for Telnet access, it shows bad password, I tried with a strong password for root in the first line of the enc file, but it gets to the same HTML source screen, now it seems it's able to set the new password, but doesn't restore the new file. images attached for reference

Anyone else faced this issue or any suggestions? @itsyourap you still exploring this?


Source
 
@malhar_ch you have to modify checksum if you actually want to import the file. But that doesn't really matter as import of config is not needed to be able to telnet to the router. You just want the system to parse the config once. As you said that you got the message stating password is changed, then that means you were successful in changing the password and should be able to telnet to the router.

Do note that its not persistent and it will not work after router reboot. You have to redo the whole procedure again. To make it persistent you have to add a custom script as mentioned here
 
Hi @hacked2.57 I tried that too, just after I got this message I tried to telnet but it didn't work, I tried to remove the password altogether and tried to import that gave me checksum error, I modified the config.checksum and set it to "0" that didn't help either, now I'm suspecting, whether root password is actually getting changed or not, or it's failing on that stage, as I can see the prompt twice.
 
@hacked2.57 No, by prompt I mean the text, see the screenshot I attached on #14, I used a password with combination of uppercase, lowercase, symbols and numbers, as without them it throws bad password: too weak, that screenshot is also attached on #14
 
Back