can you guys help me with the pin lock issue? Phone got messed up due to the new update as i forgot to disable the automatic update on restart option on developer settings. The phone ended up with bootloop , so had to restore from old twrp backup and re-update. However, the pin lock (fingerprint, screenlock) doesnt seem to work anymore. Neither Factory reset nor deleting the locksettings.db solve that pin lock problem. The old backup was encrypted. However after restoring the encryption was gone. That's when the screen lock issue appeared. Is there anyway to fix it without flashing stock rom? Or how do I encrypt the phone again?
What happens when you try to set a pincode?
Have you tried booting into recovery and using the recovery option to wipe and format all data?
Well I tried that but it didn't work. What I did was simply restored the old backup from twrp which was encrypted. However for reason the encryption was lost when formatting and reflashing through twrp. Phone works just fine , the only thing that broke was the lockscreen pin setup. New pin/pattern/password doesn't seem to get set. Now it's like a house without a lock
I had a similar problem. For me the persist partition broke when restoring the TWRP backup. As a result, I couldn't enter a fingerprint. Maybe the problem is similar with you.
I then flashed the "persist.img" separately.
I took it from the TWRP backup and changed the ending from ".emmc.win" to ".img" and then flashed the whole thing via fastboot. Command is "Fastboot flash persist * .img"
Credits to HofaTheRipper
--------------------------------------------------------------------
Ich hatte ein ähnliches Problem. Bei mir ist die persist partition beim wiederherstellen des TWRP Backups kaputt gegangen. Dadruch konnte ich keinen Fingerabdruck eingeben. Vieleicht ist bei dir das Problem ähnlich.
Ich habe dann die "persist.img" separat geflasht.
Ich habe sie aus dem TWRP Backup entnommen und die Endung geändert von ".emmc.win" in ".img" und das ganze dann per fastboot geflasht. Befehl ist "Fastboot flash persist *.img"
Credits to HofaTheRipper
I've had a similar issue with the pin code as well, it seems to be a completely seperate thing to the persist image.
From my understanding the persist partition contains sensor calibration data, which is unique to each and every device, and your camera and fingerprint require that partition to be completely stock and unaltered to work (so if you flash someone else's persist partition or completely wipe the partition, you will need to reflash it using your own device's unique data to get those features working again)
That doesn't appear to be what caused the Pincode issue in my case. (and probably not what caused OP's issue either I'm guessing)
I ran a pseudo-scientific experiment; I reformatted my device using recovery's reformat option; completely wiping all data from the phone. Setting a pincode from this completely stock state worked fine. I then used TWRP to flash in my Data partition only, from a TWRP backup that WAS NOT encrypted; The result was an immediately failure to set a pincode. The symptom was when you try to set a pincode, it never actually gets set; The phone asks you to enter the pincode, then enter it again to verify, and then simply seems to pretend nothing happened and no pincode is applied no matter how often you repeat the process.
So in my case, it was definitely an issue with restoring the DATA partition.
I then ran another experiment flashing in the same DATA partition using fastboot flash commands, and the same thing occurred.
Then finally, I repeated both flashing methods, using a DATA partition from a backup where hte DATA was encrypted (ie had a pincode set), and those resulted in a bootloop, where the phone refused to boot with an encrypted data partition.
I never ended up finding a fix to the phone being unable to set a pincode, so instead I reformatted all data, and set up the phone from scratch again.
Whilst my phone still had it's original data, but no pincode could be set, I simply backed up all photos and notes and other things i knew would be lost, then went ahead and did a final, permanant reformat to stock. Then proceeded to set up the phone from scratch again, reinstalling all apps and configuring all data again; As the phone was reset to scratch, the pincode was working again.
7tyjupiter said:
Zombnombs said:
I've had a similar issue with the pin code as well, it seems to be a completely seperate thing to the persist image.
From my understanding the persist partition contains sensor calibration data, which is unique to each and every device, and your camera and fingerprint require that partition to be completely stock and unaltered to work (so if you flash someone else's persist partition or completely wipe the partition, you will need to reflash it using your own device's unique data to get those features working again)
That doesn't appear to be what caused the Pincode issue in my case. (and probably not what caused OP's issue either I'm guessing)
I ran a pseudo-scientific experiment; I reformatted my device using recovery's reformat option; completely wiping all data from the phone. Setting a pincode from this completely stock state worked fine. I then used TWRP to flash in my Data partition only, from a TWRP backup that WAS NOT encrypted; The result was an immediately failure to set a pincode. The symptom was when you try to set a pincode, it never actually gets set; The phone asks you to enter the pincode, then enter it again to verify, and then simply seems to pretend nothing happened and no pincode is applied no matter how often you repeat the process.
So in my case, it was definitely an issue with restoring the DATA partition.
I then ran another experiment flashing in the same DATA partition using fastboot flash commands, and the same thing occurred.
Then finally, I repeated both flashing methods, using a DATA partition from a backup where hte DATA was encrypted (ie had a pincode set), and those resulted in a bootloop, where the phone refused to boot with an encrypted data partition.
I never ended up finding a fix to the phone being unable to set a pincode, so instead I reformatted all data, and set up the phone from scratch again.
Whilst my phone still had it's original data, but no pincode could be set, I simply backed up all photos and notes and other things i knew would be lost, then went ahead and did a final, permanant reformat to stock. Then proceeded to set up the phone from scratch again, reinstalling all apps and configuring all data again; As the phone was reset to scratch, the pincode was working again.
Click to expand...
Click to collapse
7tyjupiter said:
I had a similar problem. For me the persist partition broke when restoring the TWRP backup. As a result, I couldn't enter a fingerprint. Maybe the problem is similar with you.
I then flashed the "persist.img" separately.
I took it from the TWRP backup and changed the ending from ".emmc.win" to ".img" and then flashed the whole thing via fastboot. Command is "Fastboot flash persist * .img"
Credits to HofaTheRipper
--------------------------------------------------------------------
Ich hatte ein ähnliches Problem. Bei mir ist die persist partition beim wiederherstellen des TWRP Backups kaputt gegangen. Dadruch konnte ich keinen Fingerabdruck eingeben. Vieleicht ist bei dir das Problem ähnlich.
Ich habe dann die "persist.img" separat geflasht.
Ich habe sie aus dem TWRP Backup entnommen und die Endung geändert von ".emmc.win" in ".img" und das ganze dann per fastboot geflasht. Befehl ist "Fastboot flash persist *.img"
Credits to HofaTheRipper
Click to expand...
Click to collapse
Cheers mate, it works . Thanks you're a lifesaver!!!!
Click to expand...
Click to collapse
Related
I'm working on it for about 2 days and do not know what to do anymore.
My phone worked perfectly, except it's rooted the rest is original.
On saturday I tried to convert an user app to system app and brick the operation system. So... sideloaded a stock room downloaded from ASUS suport page and "vuala", the phone was back to normal, them i think, if i install TWRP next time i brick my phone ll be easier ro restore if i had a backup.
Then i perform the procedures in this topic: http://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
In TWRP i did a backup of my system and it ask me to install root on the device, what i did . After that the system start to freeze and rebbot randomly even without user interaction.
-My first step was factory reset, not work.
-Removed root, and factory reset again. not work
Wipe system and data partition, re-flash by ADB sideload the stock room, steel freezing and rebooting
I've downloaded the original stock rom V3.23.40.60, replaced the fastboot and recovery to original V3.23.40.60, re-flash dnx_fwr_ctp_a500cg.bin and ifwi_ctp_a500cg.bin from original image V3.23.40.60.
-Removed SD card, microSD and reflashed everithig again. still not work.
After all the probelm persists. Someone have any idea what's going on? My knowledge about mobiles is't enough to deal with this probelma alone.
I start thinking about hardware inssue but it's rly weird.
Some questions:
-There are another partitions on the device that can be restored to factory or reseted?
-Change bootloader or recovery can directly influence the operation system?
-Is there a program I can test internal storage of my device and RAM?
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Lazer Bear said:
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Click to expand...
Click to collapse
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data ?
MigoMujahid said:
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data
Click to expand...
Click to collapse
Thanks for the input, I was thinking something along those lines but I wasn't totally sure, I always avoided dirty flashing as I heard of people having issues. Happily, it worked! Weirdest think I saw in a while, it gave me a bunch of errors with System partition (unable to mount, unmount, find), then it gave a "proceeding to patch system partition unconditionally", then it completed. The whole thing took less than 20secs so I do not think it even actually flashed the ROM. Now I am just getting some Play Services error, likely need to reinstall gapps, but phone boots just fine!
I rooted my x829 and flashed TWRP (v3.0.2-1) and Lineage 13.1. Since I want to try other ROMs to see if they can fix the fp sensor problem, I use TWRP to back up this ROM and wiped/reflashed other ROMs. Later I tried to restore this ROM, everything seems fine but the recovered ROM lost my unlock pattern. This prevented me from unlocking the screen. I have to wipe and flash the ROM again. When I back up, I selected system, data and boot. After I restore, I wiped cache and dalvik. Not sure what I did wrong. Anyone has idea or is it possible the TWRP has some bug related to backup/restore? Thanks a lot.
don't know the cause but it's easy to fix.
https://forum.xda-developers.com/showthread.php?p=71494297
Gesendet von meinem LEX820 mit Tapatalk
My wife's poco went to a bootloop after normal day of operations. First WhatsApp stopped working, after she tried to reset the system it never booted again.
Phone full stock, never before unlocked. Without SD card.
After that I did a factory reset. Seemed fine. After that a newest OTA update. Went smooth.
Since then the gyroscope is not working and the camera is taking long to launch
After googling away for 2 hours I figured it may be something with corrupted persist position, which is not easy if not impossible to flash. Miflash won't write it in either normal not edl.
Twrp s function to install IMG has only 4 position options not including persist.
One custom mi8 twrp has an option to write persist position but I hesitated to do it since it's not for Poco and I fear I may brick the phone.
Any help would be great
Gesendet von meinem POCOPHONE F1 mit Tapatalk
If you have TWRP installed all you need to do is flash something in where you lose TWRP then go in to stock recovery and do a complete wipe then open rom as normal and set up for developers option the boot it to download mode and flash your custom recovery as needed......
Hello!
Yesterday, I updated my phone from A10 to A12 with full OTA and applied magisk on inactive slot.
After rebooting, all seems to work, no bootloop, android was optimizing apps... so far so good, I reached the point where my patter was asked. There was no problem with it.
The problem appeared when trying to open any APP and the android answer was (for any app) "Failed to read the app data. Cannot start the app"
Okay, I tried to go to settings and was unable to do so. After putting phone in airplane mode, settings worked but clearing apps cache or data did not help.
Trying to fastboot boot twrp.img did not work until I found https://github.com/rabilgic/twrp_device_oneplus_hotdogb/tree/Android-12.1 by another xda user.
Even being another device it worked (afaik they were unified twrp so they should work for both). However, once booted, the first problem appears. Inserting my patter did not decrypt the data in twrp... Booting into system removing pattern and try TWRP again and nothing changed...
Checking in twrp the data/data lead see all folders and files encrypted there... So this is probably why any app is working...
After reading, I saw that fbev2 was applied to A12 so this might be the problem. My guess was that flashing a A11 rom might save my data since the encryption should be the same older one v1. However, I am unable to flash ROMS with TWRP... Tried with OTG or sideload, but both failed. I would like to know if there is a way to flash an older rom (A10 whcih was my original one or A11) to decrypt the data or make the A12 decryption work to recover all my apps and data.
I do not know if flashing any further (of if I had already) lost the decryption keys or what is going on.
I had extracted the .img from a full A10 OTA (OOS) and I am hesitant of flashing all 32 images to the phone or if that will wipe data partition.
How can I proceed if possible without losing data with a flash, or how can I decrypt the data to make it work with A12?