I do not know if questions on the topic of firmware are resolved here, but still I’m taking a chance. There is an official firmware and a locked modem (for a telecom operator). There is a ported СyanogenMod from the donor device. So, this is the most operator lock where manifested? What files are responsible for it? The fact is that I noticed a completely different code in system/framework/telephony-common.jar . It turns out that all the telephony system applications depend on this framework ??

I have come a long way (I just need to call one method)

 system/framework/telephony-common.jar/classes.dex >> dex2jar >> classes.dex.dex2jar.jar >> JdGui >> com/android/internal/telephony/IccCard/supplyNetworkDepersonalization(String nck, Message complete);
  • one
    When replacing you are unlikely to get a brick, but 80%, that the phone and much of the work will not work. I will not tell you how it is, because there are no details, but on LG G2, the time is reduced to get the root, replace the contents of the carrier folder with the correct one and delete telephony.db, otacerts.zip. telephony-common.jar does not need to be modified. - VAndrJ
  • one
    I meant that I need telephony-common.jar exclusively for testing (as on the official firmware). As for your unlock method, yes, on some models it is possible to crank it - once, twice and ready, but on some special ones (Micromax Q415. Qualcomm) where such children’s loopholes are hidden and the frameworks are modified (+ the modem itself) this cannot be done. I imagine the unlock by usual search from 00000001 to 99999999. There is simply no other way. But I am confused that there is such a thing as trying to enter the correct nck and possibly the interval between attempts (is it or not) - Flippy
  • one
    more specifically, the telephony-common has been modified by the manufacturer - in the IccCard interface there is a GetPersoLockedRetries method that returns the remaining input attempts. In the micromax we were in a hurry and wrote it with a capital letter, this method appeared in the system update, along with it and the interface for entering the NCK code I decompiled and studied all this - Flippy
  • one
    in cyan, there is no method and there is no interface for entering the code at all, the firmware is ported and naturally the links between the modem and the stuffing have disappeared, it turns out to test the application so that telephon-common is native and I don’t want to flash native firmware and test, After all, in fact, the block on the operators on cyan remains, then the firmware does not touch this moment and therefore the interface to this thing can be done, but what if telephony-common does not make friends with telephony applications (especially the process com.android.phone I think it will fall right away) - Flippy
  • @Flippy question still relevant? - Lex Hobbit

0