because of modem update in hydrogen os 2.5 this whole mess starts pls help
Rohanlovely said:
because of modem update in hydrogen os 2.5 this whole mess starts pls help
Click to expand...
Click to collapse
This new modem firmware is quite unstable, I advise you against using it. My solution to get working second SIM was to restore OOS 3.1 modem and format modemst1, modemst2 and persist partitions. Not until after formatting the partitions did it work again (CM14 keept rebooting/crashing).
pitrus- said:
This new modem firmware is quite unstable, I advise you against using it. My solution to get working second SIM was to restore OOS 3.1 modem and format modemst1, modemst2 and persist partitions. Not until after formatting the partitions did it work again (CM14 keept rebooting/crashing).
Click to expand...
Click to collapse
How u got back the sim 2 working ?
pitrus- said:
This new modem firmware is quite unstable, I advise you against using it. My solution to get working second SIM was to restore OOS 3.1 modem and format modemst1, modemst2 and persist partitions. Not until after formatting the partitions did it work again (CM14 keept rebooting/crashing).
Click to expand...
Click to collapse
how do you format the partitions? through TWRP? so steps are, flash oos 3.1 then format the modemst1 and 2?
Rohandd said:
how do you format the partitions? through TWRP? so steps are, flash oos 3.1 then format the modemst1 and 2?
Click to expand...
Click to collapse
Sim 2 start working after that ?? U tried that ?
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
pitrus- said:
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
Click to expand...
Click to collapse
could you please list out the exact steps you have done to fix your issue?
there are many users who are getting this issue including me.
please list the steps with the links of files you flashed. it would be a great help.
pitrus- said:
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B9IqSEI0OM37RTM5M09Ib180U0E/view
I got it
Persist.img for oneplus 2?
Rohanlovely said:
https://drive.google.com/file/d/0B9IqSEI0OM37RTM5M09Ib180U0E/view
I got it
Persist.img for oneplus 2
Click to expand...
Click to collapse
Did you tried with this??
any fix??
ashu01 said:
Did you tried with this??
any fix??
Click to expand...
Click to collapse
My laptop windows crashed after repairing that i will try
Rohanlovely said:
My laptop windows crashed after repairing that i will try
Click to expand...
Click to collapse
can you join this telegram group link
https://telegram.me/joinchat/CbL5zUA-vInKg1B5M8baqQ
Had the same problem
Hi,
Just to give you all a quick background. I was in the same situation as you. Flashed H2OS didn't like the jumpy signal therefore wanted to go back to OOS.
First boot of OOS resulted in no connectivity (no wifi, no data, no Bluetooth). I followed the method above and deleted modemst1 and modemst2 and formatted modemst (all done thru fastboot)
Once I did that I was able to boot into OOS to get the signals. As petris said above, wiping and then booting into the software results in a fresh re-write of those modem partitions.
At this point I factory resetted the OOS software (just to be safe) and also installed the stock recovery (somehow my device wasn't booting into TWRP everytime I installed it).
After the factory reset I checked my IMEI's and saw my IMEI2 as 0. Luckily I don't use slot 2 so getting it to show IMEI wasn't a priority. However my camera wasn't working. Everytime I opened up the camera it would show a black screen for 30 seconds and then close with a message showing "Unknown error"
At this point I tried searching the persist.img file that someone suggested in this thread. I downloaded that from google drive and clean flashed it thru fastboot.
After a reboot I was able to get the camera working again.
So all in all for now everything works as expected. I am on the latest OOS 3.1.0 software and have no intentions of doing anything else until there is fix for IMEI2. I am regularly checking oneplus forums where people like me have esclated the issues. I think on the recognized developers Naman is working for a fix and seeing into this issue.
TLDR : IMEI2 shows 0
ashu01 said:
can you join this telegram group link
https://telegram.me/joinchat/CbL5zUA-vInKg1B5M8baqQ
Click to expand...
Click to collapse
now new is problem started in my mobile telegram guys i able start d 2nd sim in my mobile but now sim 1 imei is 0
Rohanlovely said:
https://drive.google.com/file/d/0B9IqSEI0OM37RTM5M09Ib180U0E/view
I got it
Persist.img for oneplus 2
Click to expand...
Click to collapse
u tried it? works?
lockmunk said:
u tried it? works?
Click to expand...
Click to collapse
I tried and was fine.
First i did full wipe, then flash this zip + any rom and rom started fine.
pitrus- said:
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
Click to expand...
Click to collapse
I get this error while trying to format modem
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
rajatdixit said:
Hi,
Just to give you all a quick background. I was in the same situation as you. Flashed H2OS didn't like the jumpy signal therefore wanted to go back to OOS.
First boot of OOS resulted in no connectivity (no wifi, no data, no Bluetooth). I followed the method above and deleted modemst1 and modemst2 and formatted modemst (all done thru fastboot)
Once I did that I was able to boot into OOS to get the signals. As petris said above, wiping and then booting into the software results in a fresh re-write of those modem partitions.
At this point I factory resetted the OOS software (just to be safe) and also installed the stock recovery (somehow my device wasn't booting into TWRP everytime I installed it).
After the factory reset I checked my IMEI's and saw my IMEI2 as 0. Luckily I don't use slot 2 so getting it to show IMEI wasn't a priority. However my camera wasn't working. Everytime I opened up the camera it would show a black screen for 30 seconds and then close with a message showing "Unknown error"
At this point I tried searching the persist.img file that someone suggested in this thread. I downloaded that from google drive and clean flashed it thru fastboot.
After a reboot I was able to get the camera working again.
So all in all for now everything works as expected. I am on the latest OOS 3.1.0 software and have no intentions of doing anything else until there is fix for IMEI2. I am regularly checking oneplus forums where people like me have esclated the issues. I think on the recognized developers Naman is working for a fix and seeing into this issue.
TLDR : IMEI2 shows 0
Click to expand...
Click to collapse
Did u get such type of an error:
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
If not just tel me the steps u followed
ashokmor007 said:
I get this error while trying to format modem
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
Did u get such type of an error:
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
If not just tel me the steps u followed
Click to expand...
Click to collapse
Make sure your bootloader is unlocked
rajatdixit said:
Make sure your bootloader is unlocked
Click to expand...
Click to collapse
yes it is unlocked
Related
All of a sudden all sensor are not working .even fp or proximity sensor not showing or working ...
Try this:
Download Attachment
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot.
Wagi99 said:
Try this:
Download Attachment
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot.
Click to expand...
Click to collapse
What is this supposed to do? Will it cure the dead home button/fingerprint as well?
My OPT shows no sensros
hi
mine is the same issue with OPT after recovering from hard brick.
Can anybody please help out this ..
tried so many methods
1. flashed custom roms including original OOS 3.0
2. flashed H2 OS
3. Done hard reset
4. formatted using TWRP recovery
5......... no use by any of these
Had the same.
And have a solution for you!
http://forum.xda-developers.com/oneplus-2/help/sensors-broken-persist-partition-t3395967
Solution is on post #18
Hey guys, I am desperate and in deep need of help.
I have a bootloop problem. My device isn't rooter nor I unlocked bootloader.
My Asus for a long time had a problem that whenever I tried to reboot it, it would bootloop.
This would go for a while and then all of a sudden it would boot.
I tried to install an OTA upgrade and this error occurred:
E: error in @/cache/recovery/block.map
(Status 7)
E:fota_return_code 409
Instalation FOTA error
Instalation aborted
My device is not booting right now, stuck in bootloop.
I tried to install the raw firmware after that, witch can be found in firmware27(the forum is not allowing me to post the link.)
It looks like it has installed stock system, recovery, boot, etc, but it still doesn't boot. I really need help!!!
Thanks!
Maybe, you meet the same situation.
1) Important!! Backup your modemst1/modemst2/fsg partition first!!
2) Try fastboot erase these partition.
3) Your phone may entry zenui desktop normally.
4) Re-build imei, it may be okay for your case.
chchtono said:
Maybe, you meet the same situation.
1) Important!! Backup your modemst1/modemst2/fsg partition first!!
2) Try fastboot erase these partition.
3) Your phone may entry zenui desktop normally.
4) Re-build imei, it may be okay for your case.
Click to expand...
Click to collapse
I copied the modemst1, modemst2 and fsg to my sd card and erased the partitions from fastboot, booted successfully, now can u tell me how to rebuild imei. I have custom rom, Resurrection Remix.
ankushjangid said:
I copied the modemst1, modemst2 and fsg to my sd card and erased the partitions from fastboot, booted successfully, now can u tell me how to rebuild imei. I have custom rom, Resurrection Remix.
Click to expand...
Click to collapse
Follow this post https://forum.xda-developers.com/zenfone-2-laser/help/help-donor-qcn-file-ze550kl-z00ld-ww-t3520647
chchtono said:
Maybe, you meet the same situation.
1) Important!! Backup your modemst1/modemst2/fsg partition first!!
Click to expand...
Click to collapse
How do I backup these partitions ?
Thanks !
Hey guys, a while ago I tried going back to stock with the official Motorola Factory image. I wasn't getting any security OTAs, so I tried again with this image: CLARK_RETUS_6.0_MPHS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip by Motorola-Firmware-Team It was an update behind despite being uploaded on 1/26/17. I totally reset my phone and now I'm getting the latest update notification, but it won't update because of this error: [IMG="Sorry for the BLUR (see what I did there?)"]
I get that this error happens a lot and yes, I know I went back to stock correctly and I'm pretty sure I flashed my modem correctly. Anyone know what I'm doing wrong?
pswiifanwmi said:
Hey guys, a while ago I tried going back to stock with the official Motorola Factory image. I wasn't getting any security OTAs, so I tried again with this image: CLARK_RETUS_6.0_MPHS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip by Motorola-Firmware-Team It was an update behind despite being uploaded on 1/26/17. I totally reset my phone and now I'm getting the latest update notification, but it won't update because of this error: [IMG="Sorry for the BLUR (see what I did there?)"]
I get that this error happens a lot and yes, I know I went back to stock correctly and I'm pretty sure I flashed my modem correctly. Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
We can't see your image of your error. Can you link a screen shot on imgur or something?
acejavelin said:
We can't see your image of your error. Can you link a screen shot on imgur or something?
Click to expand...
Click to collapse
Whoops! Sorry 'bout that! Okay, XDA won't let me post pictures since I haven't posted enough so let me try this. imgur . com / a / wYX1F
Does that work?
pswiifanwmi said:
Whoops! Sorry 'bout that! Okay, XDA won't let me post pictures since I haven't posted enough so let me try this. imgur . com / a / wYX1F
Does that work?
Click to expand...
Click to collapse
Yeah, I got it... You have a incomplete flash on 18-8 or you used a ROM not for your device. You need to reflash the modem stack from 18-8 image and try the update again.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify an OKAY after each step, if you don't get one, do it again.
Then if it still fails to update, can you post output of `fastboot getvar all` and mask out your IMEI number?
acejavelin said:
Yeah, I got it... You have a incomplete flash on 18-8 or you used a ROM not for your device. You need to reflash the modem stack from 18-8 image and try the update again.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
And verify an OKAY after each step, if you don't get one, do it again.
Then if it still fails to update, can you post output of `fastboot getvar all` and mask out your IMEI number?
Click to expand...
Click to collapse
How did you know that would work?! The script I've been running had those steps in them and they said okay each time, so what made this attempt any different? Was it the cache clearing that happened right afterward that messed everything up or the lack of a reboot after flashing system, recovery, logo and boot?
I used the same files I'd been using, but I copied them again for good measure. Guess they got corrupted the first time huh?
Thanks so much for your help!
pswiifanwmi said:
How did you know that would work?! The script I've been running had those steps in them and they said okay each time, so what made this attempt any different? Was it the cache clearing that happened right afterward that messed everything up or the lack of a reboot after flashing system, recovery, logo and boot?
I used the same files I'd been using, but I copied them again for good measure. Guess they got corrupted the first time huh?
Thanks so much for your help!
Click to expand...
Click to collapse
Lucky guess, and I figured it was a radio issue from the error message. And I know the modem stack messes up a lot, especially when flashed too fast... There is a reason we recommend doing it manually and not with a script. ?
Hi, after install MIUI 10 my sensors stop to work (only GPS works correctly).
After one day of try to solve it, i solve it .
Problem was in corrupeted persist.img.
In xiaomi note 3 on EDL or Fastboot flash persist img is not flashed.
Fastboot erase fpersist and fastboot flash persist persist.img dont work (error - cant be written).
To solve problem, copy to phone memory persist.img file from fastboot img, boot twrp which can flash persist partition, install/flash img at persist partition. Everything works perfectly.
Edit: flashed persist partition only via Mi Flash with modified rawprogram0 and flash_all script. Sensors working now
dromaczek said:
Hi, after install MIUI 10 my sensors stop to work (only GPS works correctly).
After one day of try to solve it, i solve it .
Problem was in corrupeted persist.img.
In xiaomi note 3 on EDL or Fastboot flash persist img is not flashed.
Fastboot erase fpersist and fastboot flash persist persist.img dont work (error - cant be written).
To solve problem, copy to phone memory persist.img file from fastboot img, boot twrp which can flash persist partition, install/flash img at persist partition. Everything works perfectly.
Click to expand...
Click to collapse
Now I have the same problem as you
Could you please share your persist.img to save my phone xiaomi note3?
I would really appreciate it if you do this.
Please
Hello! I did the TWRP persist.img flash as described, but all the sensors still not working... Do you have any idea?
dromaczek said:
Hi, after install MIUI 10 my sensors stop to work (only GPS works correctly).
After one day of try to solve it, i solve it .
Problem was in corrupeted persist.img.
In xiaomi note 3 on EDL or Fastboot flash persist img is not flashed.
Fastboot erase fpersist and fastboot flash persist persist.img dont work (error - cant be written).
To solve problem, copy to phone memory persist.img file from fastboot img, boot twrp which can flash persist partition, install/flash img at persist partition. Everything works perfectly.
Click to expand...
Click to collapse
Hi, same problem here! Can you explain better how do i get the persist img and where i can download the fastboot img. Thanks
---------- Post added at 09:58 AM ---------- Previous post was at 09:24 AM ----------
Manwex said:
Edit: flashed persist partition only via Mi Flash with modified rawprogram0 and flash_all script. Sensors working now
Click to expand...
Click to collapse
Can you make a guide on what to do?
freddyededdy said:
Hi, same problem here! Can you explain better how do i get the persist img and where i can download the fastboot img. Thanks
---------- Post added at 09:58 AM ---------- Previous post was at 09:24 AM ----------
Can you make a guide on what to do?
Click to expand...
Click to collapse
Sorry, I already deleted scripts so you will have to waste a couple of minutes and do it by yourself. You can take a look at this video how it works, I've checked and it's explained well.
https://www.youtube.com/watch?v=Qf0XhhnpQEo
Just download fastboot ROM for Mi Note 3 (jason) and follow the video.
Persist.img is in fastboot rom archive (unpack). Flash with twrp
i found this tutorial and this work perfectly
dromaczek said:
Hi, after install MIUI 10 my sensors stop to work (only GPS works correctly).
After one day of try to solve it, i solve it .
Problem was in corrupeted persist.img.
In xiaomi note 3 on EDL or Fastboot flash persist img is not flashed.
Fastboot erase fpersist and fastboot flash persist persist.img dont work (error - cant be written).
To solve problem, copy to phone memory persist.img file from fastboot img, boot twrp which can flash persist partition, install/flash img at persist partition. Everything works perfectly.
Click to expand...
Click to collapse
this maybe can help u
https://alfa-roid.blogspot.com/2019/05/fix-sensor-mi-note-3-jason.html
Didn't want to post because I thought I would solve the issue with a simple MiFlash restore to stock, but oh well, here I go:
Due to my excitement about the Pie update (Beta), I got a fastboot flashable zip that was posted on a thread and attempted to flash it myself, manually.
Commands I executed (one by one, not through the bat script):
Code:
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash abootbak aboot.img
fastboot flash lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot set_active a
I probably should never have flashed all this but I will explain what happened in case someone more savvy knows exactly what happened and lends a helping hand.
So all the commands passed fine, except for the fastboot flash system ones. I executed the first one and it flashed parts of 500mb or so on the partition, around 6 times. Same on the system_b.
I suppose that these flash onto the different slots (A/B), correct me if I'm wrong. Then rebooted and it would bootloop (don't blame anyone since I f'd up) and I was like "Okay then, guess I will restore with MiFlash.
Well I did. First weird thing to notice, it would only take around 213 seconds, while it would normally take around 300 seconds so I suspected I might have messed up. Note that I always restore to the April security patch to be able to enable Camera2API. Booted fine, then it was time for me to input my SIM's PIN. I do so, and a message shows up saying "SIM PIN operation failed" and after that it would close and re-open the PIN prompt, basically every time I tried to type the PIN. It basically wouldn't even let me input the PIN itself. Sometimes, if I'm fast enough I can successfully submit it but it's still messed up and doesn't work properly.
I know, I shouldn't have flashed the thing in the first place (since it's also supposed to be confidential), but I did and I regret doing so. For anyone interested, the bootloader is unlocked and I can enter fastboot mode normally. Didn't try flashing a different stock image since this is the one I always use and it works.
If anyone has got any idea about what happened here and if there's any solution, I would be really thankful.
Update: Also tried flashing one of the 8.1 fastboot images. It flashed without errors. While booting though, it crashed like 2 seconds after asking for my PIN.
michkost858 said:
Update: Also tried flashing one of the 8.1 fastboot images. It flashed without errors. While booting though, it crashed like 2 seconds after asking for my PIN.
Click to expand...
Click to collapse
Try booting without simcard, if you are able to boot, toggle off sim pin from settings and try booting with simcard
apexashwin said:
Try booting without simcard, if you are able to boot, toggle off sim pin from settings and try booting with simcard
Click to expand...
Click to collapse
Have tried this. Boots fine without SIM card. In fact, even with the SIM card in I can press the back button and skip the prompt but it will pop up again. But I still can't properly use the SIM
Why flash April update? You can enable camera2api on any ota update! :/
WhatzIt2Ya said:
Why flash April update? You can enable camera2api on any ota update! :/
Click to expand...
Click to collapse
I don't think it's what matters at the moment.
michkost858 said:
I don't think it's what matters at the moment.
Click to expand...
Click to collapse
Ugh, yes it does. You need the latest modems etc. for it to flash properly. That's why, you see in custom rom threads say, 'you must be on latest stock firmware before flashing'.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
michkost858 said:
I don't think it's what matters at the moment.
Click to expand...
Click to collapse
So, before you flash pie beta update. You MUST be on latest November update for it to flash properly.
WhatzIt2Ya said:
Ugh, yes it does. You need the latest modems etc. for it to flash properly. That's why, you see in custom rom threads say, 'you must be on latest stock firmware before flashing'.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
So, before you flash pie beta update. You MUST be on latest November update for it to flash properly.
Click to expand...
Click to collapse
Just to be clear. I wasn't trying to flash any extra firmware after failing to install the Pie Beta flashable. I tried rolling back to stock.
Also, I was in the latest November update, before flashing the Pie beta flashable, so that's not what's wrong.
About the reason I flash the April update, it's just so I don't get wipes when I lock/unlock the bootloader on the process of enabling Camera2API.
Right now, I just want to get back to stock, didn't try flashing the Pie beta a second time after I failed and I won't.
Also my IMEIs are correct, if that matters in any way. I believe something got corrupted in the partitions (might be bsing) but yeah. Now whatever version I'm on (7.1,8.0,8.1) the issue still persists.
So I'd like to make a full restore, from the ground up, I suppose.
Try install lastest stock firmware using Miflash with Mi A1 in EDL Mode (search here in the forum how to get it there). If it works, then you can flash April firmware or do whatever you want.
nitroax said:
Try install lastest stock firmware using Miflash with Mi A1 in EDL Mode (search here in the forum how to get it there). If it works, then you can flash April firmware or do whatever you want.
Click to expand...
Click to collapse
I guess I can try that but will that be any different than flashing the same firmware with MiFlash on fastboot?
Also, should I change something on the flash scripts of the fastboot images so that they work properly on EDL mode (saying this cause I read somewhere that they shouldn't have the 'fastboot reboot bootloader' command to prevent bricks, might be bs)?
michkost858 said:
I guess I can try that but will that be any different than flashing the same firmware with MiFlash on fastboot?
Also, should I change something on the flash scripts of the fastboot images so that they work properly on EDL mode (saying this cause I read somewhere that they shouldn't have the 'fastboot reboot bootloader' command to prevent bricks, might be bs)?
Click to expand...
Click to collapse
I had a similar problem. Solved restoring persist and EfS backup.
sipollo said:
I had a similar problem. Solved restoring persist and EfS backup.
Click to expand...
Click to collapse
Hmm, I don't have such a backup. Is there a way to restore one?
michkost858 said:
Have tried this. Boots fine without SIM card. In fact, even with the SIM card in I can press the back button and skip the prompt but it will pop up again. But I still can't properly use the SIM
Click to expand...
Click to collapse
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
michkost858 said:
Hmm, I don't have such a backup. Is there a way to restore one?
Click to expand...
Click to collapse
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
manpildo said:
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
Click to expand...
Click to collapse
Yes this is a known bug. This should fix pin issue
manpildo said:
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
Click to expand...
Click to collapse
.:Addicted:. said:
Yes this is a known bug. This should fix pin issue
Click to expand...
Click to collapse
Thanks for pointing me in the right direction. Will be watching over the thread linked.