as well, after you upload the bin to the /tmp folder.
Also, is it fine to revert like this, because since i followed previous guide and made a backup of the whole mtd content, should i just copy the backup mtd whit:
and restore whole mtdor just writing the kernel partition is enough?
Because openwrt create additional stuffs on mtd, so the point is:
Write kernel
Restore whole MTD
Which one? or both?
Until now , the device is running 2,5 days (uptime). Rock solid, I hope it stays like this. And hey, I've got SSH access so I can monitor, externally trigger a reboot and etc. in case it hangs.
Just for completeness, in case anyone else flashes the snapshot firmware and likes to setup the Quectel QMI modem under OpenWrt:
vim /etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option packet_steering '1'
option ula_prefix 'fdba:727a:8cdf::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '192.168.1.1' # Adjust to your LAN
config interface 'wan'
option proto 'qmi'
option pdptype 'ipv4' # You can also select dual stack here
option apn 'internet.t-d1.de' # Adjust to your carrier APN
option auth 'none'
option device '/dev/cdc-wdm0'
option modes 'all'
option delay '60' # Delay, timeout required because the modem didn't send/receive bytes on the WAN interface after boot up.
option timeout '300'
Don't ever write to mtd0. That's a backup you hope you'll never need.
Note also that mtd0 in the OEM firmware is a partition spanning all the flash. That''s not present in OpenWrt, so all the mtd-numbers will be off by one. And you won't really use the (OEM) mtd0 backup for anything except exploring the empty spaces. Which aren't so empty after all.
The OpenWrt kernel+rootfs splitting changes the mtd-numbering as well, adding the rootfs between the two Kernel partitions.
IMHO, tt's best to refer to partitions by name to avoid any numbering confusion. I kept the OEM names everywhere these map one-to-one with the OEM firmware.
I believe you should use mtd write to restore the backup as well. You might want to cut away the empty (all ff's) space at the end before writing it back.
And there should normally not be any reason to restore any other partition than "Kernel", and possibly "Kernel2" if you updated that with e.g. the Openwrt recovery initramfs.
So i was in full openwrt.
At this point i didn't know how to fix the mtd partitions, so i just followed your advice.
Uploaded 100ABUV5C0.bin which is latest OEM firmware in /tmp
That looks fine to me. You did it all like I would have.
Using the latest downloaed OEM image, like
100ABUV5C0.bin
should be preferred if that is an option.
But this isn't always the case if the device is running an operator specific firmware. These are only available from the operator, and often not anywhere public. Which means that you need the backup if you want to revert to that specific firmware.
Might sound like a strange thing to want, but local market conditions or operator restrictions can make it necessary.
So, what about firmware on the module? can it be modified by zyxel?
Today i received the latest module firmware, but quectel referer said, zyxel could have programmed the module, so installing an official firmware, i might loose something. is it possible?
So he asked me to ask the producer, but, as you know, zyxel do not give full firmware pubicly, they only offer Dfota upgrade. Probably they would say i should not install it.
I am only guessing, but I don't think ZyXEL does anything to the modem module firmware. But they do change some modem settings. These should survive a modem firmware upgrade though.
You might have noticed one of the modified settings: The modem has a ZyXEL IMEI, completely different from the Quectel one engraved on the module rf shield.
Yep, the problem is, im not doing upgrade, i would install a complete modem firmware, whit QFirehose, i dont have an upgrade to apply,thats zyxel department.
Upgrading whit QFirehose or qflash is different then Dfota.
Unless it does not matter much.
do i need to remove the sim, even when upgrading whit qfirehose?
or its ok, or maybe i have to issue a cfun=0 before?
Also, does exist a reset command for the module?
maybe it could help, after an upgrade, just like when you upgrade the firmware, a reset is in order to avoid errors, maybe even for the module is the same?
NVM, QFirehose put the modem in update mode, just like when you want to upload a smartphone firmware, and you put it in download mode. after that, it just install whole firmware inside, and thats it.
Problem is, why i wasnt able to use QFirehose from my linux pc?
They give the whole tool, but there is makefile etc so the source code inside, but also QFirehose binary, so i thought it was an already compiled and working program.
But, despite it does start, it always failedupdating the module.
Meanwhile from inside ROOter on another router, which have latest version of qfirehose, it worked.
Can it be a matter of kernel on my pc?
Because obviously since both ROOter whit same kernel, maybe thats why it worked.
Or maybe i had to run the program whit sudo?
@bmork Tusen takk! Thank you so much for all your detailed feedback on this subject.
I did the same, bought a used Telenor antenna, thinking that of course they have not locked it down, they have been quite good with not locking things down before at least in my experience. So now I know why I struggle to access the NR7101.
A quick and easy way, if I buy a used zyxel 8702 to set it up in bridge, could I still use another SIM card in NR7101?
If my main goal is to use ICE sim card in this router, is how you explained the quickest way to get here?
If too much hassle, perhaps better just buy a B818 with 4g? Helping my parents... They will notice a big difference I think...
@Morgan With all you did now, is it worth all the time to unlock it? Did you get it up and running well without too much hassle properly?
Using OpenWrt (or any vendor-independent solution) will always require some additional work and maintenance. I believe it's a disservice to users to recommend it as an "easy" solution to any problem, so I won't do that. OpenWrt has lots of advantages. But you can't add flexibility without complexity, which can also be seen as a disadvantage.
The methods I've documented in the device page and in this thread can also be used to install standard OEM firmware without any operator restrictions. But that's really off topic here. And I can't tell if that will allow ICE SIMs since it also depends on ICE, and I haven't tried it myself.
You won't be able to run OpenWrt on a B818, so asking for recommendations wrt that device in this forum should not be necessary.
@bmork
I'm currently trying to do the modem firmware DFOTA upgrade. I took those steps, but then, nothing happens and internet is still connected. I also tried to hit "Stop" on the "wwan0" interface in LUCI, but still error 701.
picocom /dev/ttyUSB2
(...)
at
OK
ati
Quectel
RG502Q-EA
Revision: RG502QEAAAR11A03M4G
OK
at+cgact?
+CGACT: 1,1
OK
at+cgatt?
+CGATT: 1
OK
at+qfotadl="http://get.dyn.mork.no/nr7101/RG502QEAAAR11A03M4G-RG502QEAAAR11A06M4G.zip"
OK
+QIND: "FOTA","HTTPSTART"
+QIND: "FOTA","HTTPEND",701
I've also seen that error. I don't know why, but disconnecting the modem first sometimes helps (don't do this unless you're connected locally by LAN or console):
@bmork Sorry, I don't understand. Could you just tell me how to properly disconnect the modem? I've never done DFOTA through OpenWrt/SSH before so never disconnected the modem before (do I need to open the case and unplug USB? I think that's not what you mean).
