Remove SIM-lock patch generator

Quote:

---

Originally Posted by simox

It is an absolutely normal behavior, because SETool2 Lite reads the information about SIM locks from GDFS, but it still contain the network locks, because it is untouched. However we modified(unlocked by patch) the MAIN firmware, thus it will allow any SIM card, independently from the GDFS content.

---

Thanks Simox, I was just about to ask the same question. However is there any way I can confirm if the patch works without another SIM card?

I also noticed in SETool2, it says:

RESTORATION FILE NOT PRESENT
"R4EK001_CXC1250316_GENERIC_HN"
YOU MUST PERFORM FULL FLASHING FOR PATCH UNLOCK

Any idea what this means?

Hmmm, running into some small problems. I'm using XS++ 3.1 with the following files:

W810_R4EK001_FS_AMERICA_2_RED49.fbn
W810_R4EK001_MAIN_GENERIC_HN_RED49.mbn
W810_CDA102555_15_R2A_Generic_AMERICA_1 (customization pack)

After flashing/unbranding, my phone turns on okay but when I use your SimLockPatchGen on the R4EK001 Main and flash the script with SETool2, the phone won't turn on. I have to reflash the main the XS++. But do I lose the patch I just flashed?

Quote:

---

Originally Posted by wongnog

Hmmm, running into some small problems. I'm using XS++ 3.1 with the following files:

W810_R4EK001_FS_AMERICA_2_RED49.fbn
W810_R4EK001_MAIN_GENERIC_HN_RED49.mbn
W810_CDA102555_15_R2A_Generic_AMERICA_1 (customization pack)

After flashing/unbranding, my phone turns on okay but when I use your SimLockPatchGen on the R4EK001 Main and flash the script with SETool2, the phone won't turn on. I have to reflash the main the XS++. But do I lose the patch I just flashed?

---

Yes you will lost patch so - use Setool2lite and put Main + .vkp like on first page this section

@wongnog

Quote:

---

when I use your SimLockPatchGen on the R4EK001 Main and flash the script with SETool2, the phone won't turn on

---

It doesn't turn on because the rest(oration) file for your firmware is missing. You need to download the R4EK001_CXC1250316_GENERIC_HN from somewhere, or make one for yourself with [SeToolLiteFolder]\make_rest\ssw2rest.exe, and then copy the generated rest file to [SeToolLiteFolder]\rest\ folder.

Quote:

---

Originally Posted by simox

It doesn't turn on because the rest(oration) file for your firmware is missing. You need to download the R4EK001_CXC1250316_GENERIC_HN from somewhere, or make one for yourself with [SeToolLiteFolder]\make_rest\ssw2rest.exe, and then copy the generated rest file to [SeToolLiteFolder]\rest\ folder.

---

THANK YOU, worked like a charm! Maybe you should put that in the first page as part of the flashing instructions, I don't think it's that clear to ppl like me that have never used SETool2 before. Just to clarify something though, if I were to update camera or sound drivers using FAR Manager + SEFP, I have to reflash the Main so I will lose all patches and have to reapply, am I correct?

Quote:

---

Maybe you should put that in the first page as part of the flashing instructions

---

It's not a bad idea...

Quote:

---

Just to clarify something though, if I were to update camera or sound drivers using FAR Manager + SEFP, I have to reflash the Main so I will lose all patches and have to reapply, am I correct?

---

It is correct what you wrote, BUT if you make a rest file for SEFP (*), then you can flash that instead of entire MAIN, and you will not loose any patch.

* - in [SEFP folder]\rest\ folder there is a mkrest.exe(or something like that). With that tool you can make a rest file for SEFP.

Quote:

---

Originally Posted by simox

It is correct what you wrote, BUT if you make a rest file for SEFP (*), then you can flash that instead of entire MAIN, and you will not loose any patch.

---

Great to know! So can I use XS++ and flash the rest file instead of main, or do I have to use SETool2 to do that (load the rest file in the Restoration line)

Use XS++, and flash the rest file as MAIN(select it in MAIN firmware box).
Note: Apparently XS++ will never finish the rest file flashing. When it flashed 4 blocks(I think), or wait about 30 seconds (it should be more than enough), then stop the flashing operation. XS++ will give you a warning message, but just ignore it, it is completely safe in this situation.

Quote:

---

Originally Posted by simox

Note: Apparently XS++ will never finish the rest file flashing. When it flashed 4 blocks(I think), or wait about 30 seconds (it should be more than enough), then stop the flashing operation. XS++ will give you a warning message, but just ignore it, it is completely safe in this situation.

---

Thanks simox. I noticed the same thing when I flashed the bootloader with XS++ (before using FAR Manager + SEFP), but all seems to be fine.

Is it work fine with W810i CID50?