The story is that, I flashed a custom 7.1.2 ROM all gone successful and I put in PIN and fingerprint as Security.I rebooted because I want to install SuperSU after successful SU flashing the screen prompt "To Start You Android, Enter your PIN" I was confident to enter my PIN but after hitting OK it says that my PIN is wrong. So I entered several times but no success. I panicked so flashing miui eu rom. It was my option hoping that all will be good after installation. But still the "To Start You Android, Enter your PIN"
As I've searched now I need to delete the .key files on data/system folder but since I flashed different ROMs back and forth maybe those files has been deleted also.
To cut this long story, I am still stucked with the "To Start You Android, Enter your PIN"
What I am gonna do now?
Please help me.
My device is Redmi Note 4x (SD), Unlocked and with TWRP installed
Aciong.Aksaya said:
The story is that, I flashed a custom 7.1.2 ROM all gone successful and I put in PIN and fingerprint as Security.I rebooted because I want to install SuperSU after successful SU flashing the screen prompt "To Start You Android, Enter your PIN" I was confident to enter my PIN but after hitting OK it says that my PIN is wrong. So I entered several times but no success. I panicked so flashing miui eu rom. It was my option hoping that all will be good after installation. But still the "To Start You Android, Enter your PIN"
As I've searched now I need to delete the .key files on data/system folder but since I flashed different ROMs back and forth maybe those files has been deleted also.
To cut this long story, I am still stucked with the "To Start You Android, Enter your PIN"
What I am gonna do now?
Please help me.
My device is Redmi Note 4x (SD), Unlocked and with TWRP installed
Click to expand...
Click to collapse
Format Data via twrp. Good to go.
Note that you'll loose all your data.
Thanks @sachin n.
This has been resolved.
I guess you may be using twrp to install the ROM when there is no formatted data partition,
Andy，xu said:
I guess you may be using twrp to install the ROM when there is no formatted data partition,
Click to expand...
Click to collapse
Nah, MIUI itself encrypted. You've to FORMAT data via TWRP inorder to get rid of encryption. No option.
BTW, check #3, it has been fixed.
sachin n said:
Nah, MIUI itself encrypted. You've to FORMAT data via TWRP inorder to get rid of encryption. No option.
BTW, check #3, it has been fixed.
Click to expand...
Click to collapse
As a Chinese user, also witnessed the development of XIAOMI over the past few years. In the Chinese market, the main price is correct. But still hungry sales so far. Feeling like a monkey! MIUI is the same, once slogan: for the fever and students. Has now become the "ADUI". Bloated, ad implanted, or even better than Flyme. Hope MIUI9 can change. There is a month on the closed .....
Related
Title says it all, I already posted in the cm12.1 thread but I can't get my phone to not be encrypted. I would seriously appreciate some help..
Oggie7797 said:
@invisiblek thanks for keeping this device alive along with others. I am about to ship off to bootcamp and I was going to give my DNA to my mom. Well, I am trying to get my device to decrypt but for the life of me I can't. I encrypted inside of CM12.1 a month or two ago and half way into a reboot i need to do my password to boot. I have reset the phone from phone settings, and even tried wiping EVERYTHING including internal storage inside of TWRP yet half way into a pure clean flash of CM12.1 (sideload zips from recovery using adb) It STILL wants me to do my password and phone says it is encrypted in settings. I even wiped everything (again) and obviously bootlooped into htc logo until i rebooted into recovery where twrp asked for my password to unencrypt...lol I am not trying to complain but I don't want her to deal with the super long reboot and having to remember my password everytime it tries to boot. I would really appreciate any help!
Edit:
Just flashed TWRP 2.8.7.1 from mdmower hoping it would actually kill the encryption but didn't work.
https://android.cmphys.com/twrp-dlx/
Click to expand...
Click to collapse
@santod040 you're a dlx wizard perhaps you could even help if ya had a sec lol
I was in a dilemma from many days between MIUI and CM and today I flashed it after taking NANDROID backup of MIUI and after using CM for a while I decided to roll back to MIUI. All went smoothly to the point where I tried unlocking my phone from lockscreen after the boot-up and now it says that the password is wrong even though I am entering the right one.
I've owned a RedMi 1S before and I never faced any such problems in that, I am new to this device and I should say that the process here is very much different from my previous device, there are a lot of partitions to backup here and it's much more elaborate.
So, there is a chance that I may have done something wrong here. If I did please educate me.
The only thing I did was un-checking both the FIRMWARE options i.e FIRMWARE ROM and FIRMWARE emmc, in the restore screen.
To fix this using twrp file manager rename files privacy_password_setting.key and gatekeeper.pattern.key (if you're using pattern, for lock code it'll be something similar) in /data/system. The system will just behave as there was never a lockscreen password in a first place. Had the same issue and after playing with files managed to get past that lock.
Mount system in TWRP(uncheck "mount system as read only") and type the code below in twrp terminal which is found under advanced.
rm /data/system/locksettings.db
Click to expand...
Click to collapse
Flash the Rom with EDL next time.
It's probably the security Firmware (fingerprint) from CM that messes with MIUI.
Try to flash stock Firmware.
This worked for me.. thank you so much..
So after updating my bootloader to the new version so I can run Android Nougat however I wasn't getting any LTE connection and decided to restore the EFS backup I had from android MM.
My phone started having problem more problems (SIM card not being detected) and I decided to run the OPX recovery and switch back to default.
However this resulted in my bootloader getting locked for some reason and whenever I try to reboot my phone the screen is black and the LED indicator turns white.
I can boot into the factory OPX recovery but I'm forced to use the volume and lock buttons because I can't use my touchscreen whilst using this (no idea whether this is normal).
I can still boot into fastboot mode and have tried to sideload a new ROM however this has been to no avail.
Hey, I got that exact same problem. All was fine, did a backup and wiped as every time to try out a new rom. It boot normaly and was tweaking the rom. Then I decided to restore my backup, wiped as every time and restored my backup. Till then my SIM card is not being detected and some strange things happend like I couldn't enter the recovery with advanced reboot. After that I followed the unbrick guide and my bootloader is also locked but could not boot into the rom. After bootscreen the screen is black and the LED turns white. I can also boot into the factory OPX recovery.
What happened here? Anyone some ideas?
I had the same problem, I had to trick oneplus-support to do it on warranty, see http://forum.xda-developers.com/showpost.php?p=70182036&postcount=16 and http://forum.xda-developers.com/showpost.php?p=70184136&postcount=18
Today I got my phone back with a new mainboard.
Hmm, okay thanks for your reply. But is it really a hardware problem? It sounds weird but maybe replacement is a way...
It strange, since I had the problem with my phone there are 3-4 new threads now in this forum were people have exactly this problem, black screen with white led.
I will not flash my phone again in the foreseeable future and just use gravitybox instead.
Mutchatcho said:
Hey, I got that exact same problem. All was fine, did a backup and wiped as every time to try out a new rom. It boot normaly and was tweaking the rom. Then I decided to restore my backup, wiped as every time and restored my backup. Till then my SIM card is not being detected and some strange things happend like I couldn't enter the recovery with advanced reboot. After that I followed the unbrick guide and my bootloader is also locked but could not boot into the rom. After bootscreen the screen is black and the LED turns white. I can also boot into the factory OPX recovery.
What happened here? Anyone some ideas?
Click to expand...
Click to collapse
I did the exact same thing as you and ended up in this situation.
adefigo said:
I had the same problem, I had to trick oneplus-support to do it on warranty, see http://forum.xda-developers.com/showpost.php?p=70182036&postcount=16 and http://forum.xda-developers.com/showpost.php?p=70184136&postcount=18
Today I got my phone back with a new mainboard.
Click to expand...
Click to collapse
How did you unlock the bootloader or even install KingRoot? The problem is that my bootloader is locked, that I have no way to unlock it, no proper recovery and that I can't boot into my ROM.
Also does anyone know whether Simplesurance would cover my phone? Since it does state it covers "incorrect use" (or something along those lines).
Miniheadshot said:
How did you unlock the bootloader or even install KingRoot? The problem is that my bootloader is locked, that I have no way to unlock it, no proper recovery and that I can't boot into my ROM.
Also does anyone know whether Simplesurance would cover my phone? Since it does state it covers "incorrect use" (or something along those lines).
Click to expand...
Click to collapse
With the new mainboard and the new rom build, it is impossible to use twrp or root. I didn't know that when I wrote I would be using gravitybox from now on and not flash custom roms again.
Just a quick update. Got my phone back and they also replaced the mainboard. It's now on the latest OOS but I can do everything as before. So hopefully it will survive longer as before - what ever it was...
Mutchatcho said:
Just a quick update. Got my phone back and they also replaced the mainboard. It's now on the latest OOS but I can do everything as before. So hopefully it will survive longer as before - what ever it was...
Click to expand...
Click to collapse
What is your built number?
adefigo said:
What is your built number?
Click to expand...
Click to collapse
You mean build number of OOS? Honestly don't know cause I directly flashed AOSPExtended + Arsenic. :silly: but was the v3.1.4.
Mutchatcho said:
You mean build number of OOS? Honestly don't know cause I directly flashed AOSPExtended + Arsenic. :silly: but was the v3.1.4.
Click to expand...
Click to collapse
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
adefigo said:
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
Click to expand...
Click to collapse
Ah okay, I didn't know that. Obviously then I got maybe the other one.. but not sure if this makes the difference.
What you guys are describing as a common flash of new ROM and wipe to restore backup sounds like something's left out. Did you change twrp versions between flashing and restoring? Was your backup with 3.0.2 twrp and new flash with 3.0.3?
Cause these issues usually occur when recovery versions change
dchrono said:
What you guys are describing as a common flash of new ROM and wipe to restore backup sounds like something's left out. Did you change twrp versions between flashing and restoring? Was your backup with 3.0.2 twrp and new flash with 3.0.3?
Cause these issues usually occur when recovery versions change
Click to expand...
Click to collapse
No, did not change twrp versions during flashing new ROM and wipe to restore backup. Don't know if I remember correctly but I think I was on Bluesparks twrp (was it 3.0.0?) and did not change that during the processes.
i also had same problem
i try to update my twrp recovery with flashify. it was successful but now i cant boot into recovery. i dnt know bootloader is locked or not. i can use many fastboot commands like fastboot reboot-bootloader, fastboot continue. please help me. i try many times to update or remove twrp but nothing happend. rom is working.
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt work, so I tried re-restoring EFS, wiping, formatting and wipe+flashing various ROMs all with a still unrecognised sim. Finally I decided I had enough a used the MsmDownloadTool, but it softbricked my phone with the blank screen and white LED if I try to boot into system.
I never changed twrp version during this until it was removed by MsmDownloadTool.
I also noticed that adb sideloading using OOS's old stock recovery with a OOS OTA zip doesnt work, it either gets stuck at logo or loops. Sideloading newer OTA zips kills the phone more because I tried to flash a MM zip and found that recovery no longer works. I've tried redownloading the MsmDownloadTool package and using this other modified MsmDownloadTool here a few replies down https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Another thing I noticed is that windows detects a bunch of unreadable local drives, with one readable containing only an 'images' folder, with useful-looking stuff like adsp.b00, adsp.b01 all the way to adsp.b12 and also .mbt files. I can provide the full list if it's useful. It's also detected in the device manager as "Marshall London HS-USB Diagnostics 9006 (COM6)" under Ports.
I really hope that I don't need to send this phone back to oneplus.
Clae said:
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt work, so I tried re-restoring EFS, wiping, formatting and wipe+flashing various ROMs all with a still unrecognised sim. Finally I decided I had enough a used the MsmDownloadTool, but it softbricked my phone with the blank screen and white LED if I try to boot into system.
Click to expand...
Click to collapse
Exactly what I did and what happened to my phone. I had to send it back to repair and got it back with a new mainboard in a state that I cannot use twrp any more.
adefigo said:
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
Click to expand...
Click to collapse
Did you try to adb sideload flash the 3.1.4 on the 14 version?
Clae said:
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt phone back to oneplus.
Click to expand...
Click to collapse
I had flashed a ROM and wanted to restore a backup of MOOS. The back up restored no problem but when I booted it wouldn't detect sim trays and no wifi. When I typed *#06# no iemi's and finally when I checked about phone I had no baseband. I had a back up of efs and persist but wouldnt help. If this sounds like your issue or if anyone's having this problem its actually easy fix. With adb commands had to delete modem1 and modem2 files. I had my doubts but after reboot sims trays detected, wifi and iemi's restored.
Hi, guys
my phone is Huawei p10 Lite (WAS-LX2)
Note: if you have a bricked huawei p10 lite of any kind (incl WAS-LX2) (or a NZ model)
and you want to know how i finally fixed mine, jump down to the end where it says
GOOD NEWS
quick synopsis: unlocked bootloader, flashed twrp, now i get an error (255) when trying to create backup using twrp..
you can read the rest if you want but the above basically covers it please help
so i have unlocked my bootloader and flashed twrp, before i did this i did a factory reset through androids settings, the phone is also only two months old.. but i cannot create a backup using twrp, it always fails in the same place when backing up data, does this mean my stock rom that has never been altered in anyway ect is somehow corrupt? wtf? i havnt even rooted it yet, i was going to make a backup first (of a known good rom.. lol)
i am assuming the data files are part of the rom? not something you can ignore.. they were one of the few things selected by default.. i have tried rebooting phone a few times, formatting sd card etc (64gb) so there is plenty of space...
any help would be much appreciated
the tutorial i was following is here: https://forum.xda-developers.com/p10/how-to/twrp-how-to-root-p10-lite-t3617418
my phones full build (or do i mean firmware number?..) number: WAS-LX2C706B170
android version 7.0
emui 5.1
any more info, just ask..
also, ive heard that once you have installed twrp/ unlocked bootloader you cannot use system update or androids factory reset without bricking your phone? is that true? otherwise i want to try that, i just want to root my damn phone already... or... its been a long time since i last rooted a phone... you dont need root to make a twrp rom backup do you? nah, surely not..?
or could my twrp install be corrupt? the tutorial said to drag and drop the downloaded file into cmd, but that wasnt working so i entered the location manually, it still appeared to install fine that way though so surely thats not it. i dont know
ok, i just bricked my phone... i did a factory reset in twrp, thinking it was... a factory reset... i googled whether it was safe first and everything came up clean... but it is not it wiped the os or something and now i just get a boot loop... what the hell? how could i be so stupid?! and how could twrp not warn me.. it was just a factory reset? and i havnt even rooted it yet, at this point i would probably prefer it was rooted in the hope their would be more options available to me to un brick it.. ok now i really need someones help.. why am i drinking and trying to watch tv while doing this, i am so stupid, this is the best and most expensive phone ive ever owned, what have i done?! sorry sorry ill calm down...
so if my firmware number is: WAS-LX2C706B170 then can i use one of these (also for huawei p10 lite) and if so what would be the difference? why are the numbers slightly different? same phone model, different firmware/ slightly...
here they are:
WAS-LX2C706B120
WAS-LX2C185B121
and they each had a OTA and a full firmware version too.
here is the link: https://romfirmware.com/2017/08/04/huawei-p10-lite-was-lx2/
but before i try these things, is there any saving my current stock rom? i dont understand how a factory reset could prevent it from booting properly..? its not actually bootlooping, it either gets stuck on logo, or goes to black screen but you can still see the volume slider when pressing volume buttons, see the home and back buttons (which do nothing) and hear the lock sound when you press the power button... still always a black screen though.. i guess its possible i knocked the format data button in twrp but im 95% sure i didnt. if i remove twrp and install stock recovery would i be able to get the stock rom working that way? or is there any way to do an OTA update/ fix as i havnt rooted it yet so it should be capable (except i cant boot to rom..) if i hold down all buttons it seems to try to do something... it says emui then goes to 4% then says software install failed: the update package does not exsist. please download the package again... reboot system now..? whats that all about?
ok, so i have found a possible solution but would like confirmation from someone who knows these things first...
i found this tool: Huawei Firmware Finder (Team MT)
link: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
and using this i have found my exact firmware, apparently straight from the official huawei update servers. the firmware number matches exactly, but there is no mention of it being for a huawei p10 lite so not 100% sure its a good idea, but if the whole firmware number matches perfectly and its the only one of its kind it must be the right one surely? and the size is the same as other huawei p10 lite firmwares..
here is the direct link:http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1514/g104/v89953/f2/full/update.zip
please someone else chime in to give me some advice...
is there any risk with flashing roms, or can i always still access twrp recovery to flash a new rom if i brick the phone?
cheers all
ok UPDATE:
i tried the repair file system option in twrp on the data partition just for fun (wrong word, im not having fun..) because i thought this rom was a lost cause..
upon reboot a huawei warning pops up saying the data partition has some serious damage and offers to try a low level format, it finishes successfully then restarts.
no change, still broken, but it offers to do a full format of data due to serious damage.
after restart phone boots fine, and enters setup wizard for first boot etc... perfect.
problem is, i still cant backup the data partition in twrp, still get same error:
createTarFork() process ended with ERROR: 255
bacjup failed..??
did i somehow get a brand new phone with a bad flash of a stock rom straight from the manuafacturer? with a slightly corrupted data partition... is there anyway to fix this? or can i assume the rom i downloaded from huaweis servers for my exact firmware is correct and i can use that as a backup in case i need it?
or in case my data is corrupt should i try to install that rom now?
or should i try to reflash twrp first and see if i can get a successful backup?
or should i just forget all this crap now my phone works and go straight to rooting it?
i really need some professional advice here.. lol
clearly i aint no expert
ok, so i noticed the frp was still locked for some reason so using adb, i relocked and unlocked bootloader, now frp is unlocked too, reflashed twrp, wiped dalvik cach/ cache, tried backup again...
no change, still fails on data partition, same error 255...?!
im lost,
close to trying to flash that rom i found...
or at least just rooting already..
OK UPDATE: first the bad news, then the good news:
so i gave up on backing up my data partition, as it was clearly somehow corrupt?...
so i went ahead and rooted my phone, everything was more or less working untill i used apps2sd...
that required several reboots and partitioning my sd card etc, then it said something about needing systemless root and a reboot, i went ahead with that and then my phone started bootlooping again, this time there was no fixing it, i of course tried removing sd card too.. nothing..
so i tried restoring to the rom i found using huawei firmware finder tool, that didnt work, using twrp to install zip, i got error -9? (couldnt find that one on the net..)
tried unzipping and putting update.app in dload folder on root of sd card, then booting to erecovery pressing vol- vol+ and power button, that also failed. now i was stressed near tears, this was the third day of research and trying to fix this... so i searche dhigh and wide, and gave up on stock roms, i figured that a custom rom designed for my chipset (hi6250)
and said to work on a huawei p10 lite then it should at least semi work on my phone, i did more research and the rom creator said to only use his version of TWRP to flash their ROM, so i reflashed to theirs... BIG mistake, if the custom recovery is the only thing you can boot into and the only way to access boot loader, do NOT risk losing it.. i did.. i lost my recovery..
so there for i lost my bootloader, so therefore i lost my ability to use ADB, or connect to pc in any way. i wanted to step in front of a bus at this point... but then there was:
GOOD news:
so i resorted to trying the official recovery roms on XDA for p10 lites, only i had been avoiding them as none of the build/ firmware numbers matched mine at all.. but i went ahead and clicked on the first download, (here is the link to post: https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097) - you might find a few comments from me near the end there, lol..
anyway , once downloaded i unzipped and just pasted the dload folder straight to sd card and rebooted phone with all three buttons depressed. to my amazement when the huaei erecovery came up it started installing!!!? wow, i tried not to get my hopes up though..
first boot restarted after blue huawei splash logo, second boot went back to erecovery, offered factory reset and wipe cache(so i did), now it boots up perfectly every time like new, everything works! even gave me NZ language options etc, even though my build number didnt match any of those above, its still worked and even better it still shows all the correct information under about phone.
my build number was: WAS-LX2C706B170
so i can confirm it works for nz huawei p10 lites with 4gb ram and dual sim and WAS-LX2 builds
hope this helps someone else out there like me
tags: all official huawei rom,stock rom,twrp.stock,backup,official,rom finder,nandroid,back up, save,solution,fix,help,stuck,advice,simple,easy,guide,tutorial,root,huawei,p10,p10 lite,huawei p10 lite,was-lx1,was-lx2,firmware,iso,image,zip,file,download,error 255,255,error,createTarFork(),
Hey, just wanted to say thank you for posting this!
I'm from New Zealand, and have the exact same phone and the exact same issue.
Your "good news" section was exactly what I was looking for, and helped me fix my phone.
Cheers, George
update copy
Hi was wondering if you have a copy of the update you used as it is near impossible to get from the link on the other thread. Another Kiwi with a bricked phone.
All good, after 4 hours it finally downloaded. I will keep a copy in case anyone needs it. WAS-LX2
My phone is encrypted and After I flashed an update of a custom rom it required me to enter a password to start android
I did my screen pin and it won't accept it. I tried default_password it did not work too, also twrp has locked me out of my data
don't tell me to wipe my data its really important and I need it.
And this is why we backup....
The encryption key was unique to the old version of Android, even re-flashing stock is NO guarantee of recovering data...
Sorry...
Masterx1200 said:
My phone is encrypted and After I flashed an update of a custom rom it required me to enter a password to start android
I did my screen pin and it won't accept it. I tried default_password it did not work too, also twrp has locked me out of my data
don't tell me to wipe my data its really important and I need it.
Click to expand...
Click to collapse
As i know, u cant recover ur data now. Phone data need to be formatted. Sr. Or someone can help u. Good luck.
Masterx1200 said:
My phone is encrypted and After I flashed an update of a custom rom it required me to enter a password to start android
I did my screen pin and it won't accept it. I tried default_password it did not work too, also twrp has locked me out of my data
don't tell me to wipe my data its really important and I need it.
Click to expand...
Click to collapse
LOL! Its funny, while Im reading your post, Im clean flashing my phone from bootlegger to xiaomi eu stable rom. Cleared up security pin, flashed DFE magisk v19.3 prior and after flashing the rom, and guess what? Ended up in same situation as you. HAHAHA! I think Im gonna give up with this whole decryption thing. Its really s**ks, sometimes DFE works and sometimes it just wouldnt work. I think I have lost my data and flashed fastboot rom for 10 times since playing with this device.
Anyway, theres no other way to get back the data that we lost. Its just, FRUSTRATING and really wasting our time to decrypt the whole phone back.
cangcan said:
LOL! Its funny, while Im reading your post, Im clean flashing my phone from bootlegger to xiaomi eu stable rom. Cleared up security pin, flashed DFE magisk v19.3 prior and after flashing the rom, and guess what? Ended up in same situation as you. HAHAHA! I think Im gonna give up with this whole decryption thing. Its really s**ks, sometimes DFE works and sometimes it just wouldnt work. I think I have lost my data and flashed fastboot rom for 10 times since playing with this device.
Anyway, theres no other way to get back the data that we lost. Its just, FRUSTRATING and really wasting our time to decrypt the whole phone back.
Click to expand...
Click to collapse
exactly the same as you it has happened to me more than one time!!
anyways I managed to make it accept my password by going to the previous build where the password was set up originally.
but the smiles and happiness didn't continue for long, it showed me a message saying that the decryption was unsuccessful and I have to reset my phone to use it again.
I finally gave here I put up a good fight, I did reset my phone and this time I flashed DFE. this phone is so trippie man you have to do a backup before flashing anything!!
also if you are locked up from your phone that means it was encrypted before, id rather my phone be decrypted atleast when I run into issues I can have my data back. this whole encryption thing forces you to wipe your phone, but give what I said a try go back to the previous rom and try unlocking it there. good luck man.