Hello all,
Last i encountered a issue regarding the password right after a reboot to system when i fully restored with TWRP.
I was really furious becouse i had no idea how to fix this.
After a couple of tries i have found a fix.
When you are about to do a nandroid backup,
Stay in system,
Go to settings-> lockscreen-> password-> And choose none.
I repeat none. If you dont you will encounter the problem.
Now you can go to TWRP and do a nandroid backup. Do whatever you want and after you did what you want, and you want to restore, you can do it without any problems. Reboot and then you can go set a security again.
paulo boë said:
Hello all,
Last i encountered a issue regarding the password right after a reboot to system when i fully restored with TWRP.
I was really furious becouse i had no idea how to fix this.
After a couple of tries i have found a fix.
When you are about to do a nandroid backup,
Stay in system,
Go to settings-> lockscreen-> password-> And choose none.
I repeat none. If you dont you will encounter the problem.
Now you can go to TWRP and do a nandroid backup. Do whatever you want and after you did what you want, and you want to restore, you can do it without any problems. Reboot and then you can go set a security again.
Pls hit thanks if this helped. That way i can see how many people got the same problem as me
Click to expand...
Click to collapse
If you forgot the unlock password, you can try this: [Guide]Hacking And Bypassing Android Password/Pattern/Face/PI. There are more similar guides.
#Henkate said:
If you forgot the unlock password, you can try this: [Guide]Hacking And Bypassing Android Password/Pattern/Face/PI. There are more similar guides.
Click to expand...
Click to collapse
Its not about forgetting... Ill explain tomorrow. In my country its 2.28 am.
#Henkate said:
If you forgot the unlock password, you can try this: [Guide]Hacking And Bypassing Android Password/Pattern/Face/PI. There are more similar guides.
Click to expand...
Click to collapse
There is this weired glitch. That for example your code is 1234, you make a nandroid backup, install a new rom, then decided that that rom wasnt good and you want to restore. After restore you reboot to system and then when you type in you passcode, 1234, it just gives you an error that the code is wrong.
paulo boë said:
There is this weired glitch. That for example your code is 1234, you make a nandroid backup, install a new rom, then decided that that rom wasnt good and you want to restore. After restore you reboot to system and then when you type in you passcode, 1234, it just gives you an error that the code is wrong.
Click to expand...
Click to collapse
Well, the purpose of the guide ive shared is to remove lockscreen password / pattern and it is helpful in the case youve mentioned.
But yeah, the workaround youve mentioned is okay too.
Yesterday, ive just experienced this on my Huawei Nova when i restored my backup. After reboot, i have to type the lockscreen password as i cant unlock with fingerprint first time after reboot and i was typing the right password, but it was telling me that its wrong. Whats strange is that ive restored the backup 2-3 times before and there wasnt any problem with it.
And ive just used those commands (like in that guide):
Code:
adb shell
su
cd /data/system
rm *.key
reboot
Then the password was gone. However, i still had to type the password to set up a new one and it turned out that i could type anything (even "1") and then i could set up a new password.
Related
Hi there,
I just read a lot of threads in this section, but it realy seems as nobody was as stupid as me.
Today I decided to root my Prime and it was all simple.
I used vipermod to root, unlock and install cwm.
I made Titanium Backup of all my Apps (nothing important here), and made a backup via cwm.
With cwm I flashed Virtuous Prime and all was fine.
Then I made the big mistakes:
-I restored most of the apps with Titanium Backup.
-I used a code to unlock my prime and I also wanted to test the encryption.
After the reboot that comes after the encryption, I entered the key, and the Prime booted.
As the lockscreen appears I entered my lockscreen code (which is the same as the encryption code) and it was ... wrong!
I don't know exactly how this happend, but maybe it was due to the Titanium Backup that I restored. Maybe I restored a system app which included the code?! I don't know.
So I couldn't enter my device, but I still had cwm, so I thought this wouldn't be a problem.
I thought I could do a factory reset, and all would be ready to go.
I did a factory reset, wipe cache, wipe dalvik - nothing helped.
It was a problem, because cwm didn't let me do anything, neither restore my backup (not found, because encrypted) nor flash the ROM again (the same here).
The only thing left I tried, was formating all the things, that I could format, but this sucked me even harder in this desaster. Now my Prime got bootloops and I don't know anything to do.
Any ideas or help is apreciated!
I would thank you so much, if anyone could help me get my Prime back to me!
have you tried to adb into your device from a PC? there's a thread in developement section called do's n donts of unlocking. I think it tells you in there how to get out of bootloop.
Thanks for your answer!
You mean this, right?
Seems as I'm nearly at Brick 2, even if I don't get "unrecoverable bootloader error", but my Device also hangs in this splashscreen with the "Eee Pad" in the middle.
Looks like I'm lost
Edit: Needed a bit to get familiar with adb, but I was able to push the rom again on the sdcard.
I fullwiped and installed the rom. First reboot askes me for encryption code, then the rom needs a bit to start.
Problem remaining: The code on the lockscreen is still wrong. I can't enter my device
Is there there any possibility (if even a full wipe doesn't help) to get back to my device?
Solved: I just had to wipe via the boot menu (voldown + power button, then wait the 5 secs)
Encrypted partition has gone!
I used TWRP 3.0.2.0 to backup my N9 a couple of days ago. Today I used the backup to restore my N9 but now my password doesn't work. I tried restoring again and it still does not work. Google Device Manager won't let me reset it. It says I already have a password lock. Is there anything I can do or do I have to factory reset?
In case you mean your lockscreen password not working after you restored your nandroid, that's normal and will happen everytime unless you completely remove the lockscreen pattern before making a nandroid backup. Nevertheless you can remove the lockscreen aftewards in TWRP by doing what the OP of this thread suggests: http://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
Master05 said:
In case you mean your lockscreen password not working after you restored your nandroid, that's normal and will happen everytime unless you completely remove the lockscreen pattern before making a nandroid backup. Nevertheless you can remove the lockscreen aftewards in TWRP by doing what the OP of this thread suggests: http://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
Click to expand...
Click to collapse
Thank you very much! This was the issue.
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..
got my X today and testet some custom roms, but after i tested omni, my phone always ask for a password to encrypt the system partition but i never set one.
is there a "general password" or something to get rid of that?
this is happened when you re flash stock rom and check MASTER RESET but never wipe internal storage.
you will have to reflash / wipe all, there is no other way (at least not that I know of)
all data will be lost and you will get your internal storage back
i do a full wipe now, but i still encounter this problem. cant believe its just about master-reset because even if i dont wipe it, i get questioned about the password wich i dont know. if i enter "default_password" it says "your password is correct but your files are corrupted please go back to your recovery and wipe your system" but in TWRP this password doesnt work and i cant wipe anything besides cache. I cant even set a pasword if i'm on stock .252
never thought it would be such a pain in the ass to flash a custom-rom on the X...
so, after some tests, even if i set a pattern lock, after flashing any custom-rom it says my pattern is wrong. i don't know what to do to get rid of this, i hope some of you guys can help me because at this level i just only can use stock-rom
[Edit]
after more research, i found a tipp on a guide for One+ that data (encryption) can be erased in twrp. So, i did and wow, it works. good to know.
Aaskereija said:
so, after some tests, even if i set a pattern lock, after flashing any custom-rom it says my pattern is wrong. i don't know what to do to get rid of this, i hope some of you guys can help me because at this level i just only can use stock-rom
[Edit]
after more research, i found a tipp on a guide for One+ that data (encryption) can be erased in twrp. So, i did and wow, it works. good to know.
Click to expand...
Click to collapse
thank you! i didn't know that!
life is diy project!
Hey, so basically just title. Trying to set a password on my phone, but it doesn't work.
I have used the TWRP and the stock recovery to wipe and format all data. Everything is stock except for the fact I have TWRP installed.
After doing a fresh wipe + reformat, phone works exactly as expected. You can set a pincode, and do everything you want with a fresh phone. To remove variables in a scientific manner, I've also tried flashing in TWRP, then boot back to system, and trying to set a passcode again. Still works. Then boot into TWRP, and only restore back in the DATA partition, and bam. Passcode can no longer be set. So the issue definitely only occurs after using TWRP to restore the data partition.
Trying to set a password seems to work as expected at first; Enter the pincode once, then enter the pincode again a 2nd time to verify. At first everything looks good, but the pincode never actually got applied. Repeat infinitely, no password ever actually sticks. Can't register a fingerprint or face unlock, as without a password, the phone prompts an error that you need a password before you can use those features. I've included a picture of the password menu after trying to set a password; Notice how it says "turn ON password", where as normally its meant to say turn OFF password, thus implying no password was ever set (because it wasn't)
Anyone happen to know why this is and/or how to solve it? Phone works perfectly fine, it's just scary not being able to lock a phone with your personal stuff on it.
Also, seeing as my end goal is simply getting a phone with my data on it, is there a way to flash in the data partition using fastboot? Usually it'd be a simple command like "fastboot flash data data.img" but in this case, TWRP saves the DATA partition (many gigs) in multiple chunks, named data.f2fs.win000, data.f2fs.win001, etc etc. Theres a good dozen or so files and not sure how to flash them all in at once.
Any solutions still appreciated! I guess i could redownload all my apps and set them up manually from a wiped stock phone again, but that's a good few hours of fiddling that I'd like to avoid.
Zombnombs said:
Any solutions still appreciated! I guess i could redownload all my apps and set them up manually from a wiped stock phone again, but that's a good few hours of fiddling that I'd like to avoid.
Click to expand...
Click to collapse
fastboot flash data data.f2fs.win000
And so on for win001
Restore partationsif there any data image file then flash that file
pankspoo said:
fastboot flash data data.f2fs.win000
And so on for win001
Restore partationsif there any data image file then flash that file
Click to expand...
Click to collapse
i thought flashing data.f2fs.win000 would overwrite the old data? So if i then flash 001 and 002 wouldn't that erase the older data?
Zombnombs said:
i thought flashing data.f2fs.win000 would overwrite the old data? So if i then flash 001 and 002 wouldn't that erase the older data?
Click to expand...
Click to collapse
NO twrp decided big data partition in to. 000,0001,002 chunks and restore it to specific chunk.
As per my idea just try see what's happens
pankspoo said:
NO twrp decided big data partition in to. 000,0001,002 chunks and restore it to specific chunk.
As per my idea just try see what's happens
Click to expand...
Click to collapse
So let me see if i undesrtand you correctly. You're saying i should do "fastboot flash data data.f2fs.win000", wait and let that fully flash in, then do "fastboot flash data data.f2fs.win001", wait for that, and keep going for every single data file?
From my understanding, the flash command will overwrite the old data with the new data, hence isn't that kind of pointless?
What do you mean by
pankspoo said:
Restore partationsif there any data image file then flash that file
Click to expand...
Click to collapse
What data image files are you talking about?
There is obviously the dozen or so data win.000, to win001 and so on from the nandroid backup that we are trying to restore. Is there something else?
Show me u rs data backup pic