Database Develop

[Q] What am I doing wrong?

No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request

Shwaguy said:
No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request
Click to expand...
Click to collapse
In safe strap did you ever change to 'safe system' before you started wiping?
/Droid3

Yes sir. I followed Hashcode's procedures from his site. I am sure it is just something small and easy that will get me going in the right direction.
I have it back on the "non-safe" mode at the moment and now all I have is a wifi connection. I checked the APN and nothing was listed. Entered the Telus APN info and it doesn't save so I grabbed an APN manager from the market. It says it is active but still no connection. I am thinking of doing a factory reset to see if that will help.
I just turned 40 today and getting my phone working again would be a great gift.

Shwaguy said:
Yes sir. I followed Hashcode's procedures from his site. I am sure it is just something small and easy that will get me going in the right direction.
I have it back on the "non-safe" mode at the moment and now all I have is a wifi connection. I checked the APN and nothing was listed. Entered the Telus APN info and it doesn't save so I grabbed an APN manager from the market. It says it is active but still no connection. I am thinking of doing a factory reset to see if that will help.
I just turned 40 today and getting my phone working again would be a great gift.
Click to expand...
Click to collapse
My suggestion is to start over then..sbf your phone if you have one so you have atleast stock..then reroot it and do not install bootstrap or anything else..just instal safestrap..then go to nonsafe system..I don't think you need to wipe anything if its your first time but you can wipe anyway if you want lol then flash a rom (say cm9 or steeldroid or whatever) then reboot..it will take a while for your first boot but it should boot..let me know if this helps! Just don't boot up until after you flash a rom lol and remember safe rom is your stock rom and nonsafe is you're new rom that you're trying to flash
/Droid3

beard0 said:
My suggestion is to start over then..sbf your phone if you have one so you have atleast stock..then reroot it and do not install bootstrap or anything else..just instal safestrap..then go to nonsafe system..I don't think you need to wipe anything if its your first time but you can wipe anyway if you want lol then flash a rom (say cm9 or steeldroid or whatever) then reboot..it will take a while for your first boot but it should boot..let me know if this helps! Just don't boot up until after you flash a rom lol and remember safe rom is your stock rom and nonsafe is you're new rom that you're trying to flash
/Droid3
Click to expand...
Click to collapse
Non safe is the stock. Safe is the one you're flashing.
Sent from my XT862 using xda premium

Thanks beard0, I have not seen a sbf file for the 860 Bell. Found a system dump but thanks to the fbi it is unavailable.
Another problem popped up unfortunately. I lost connectivity. I just have wifi now. Last month when I got the phone I entered the apn info from the Telus website and everything was fine. Now when I try it I get a message saying that "mmc field must be 3 digits" I thought that info was grabbed from the sim? Regardless, I added the rest of the info required, saved, but it doesn't save the info?? I tried apn manager and it had Telus listed, selected that but still no luck. After much searching I just did the factory reset, added apn info and still have no connectivity.
I have spent so many hours on these problems and really don't know where to go from here. Going to root/safestrap etc now.

Out of curiosity I tried turning on simlock. It says no simcard detected. It worked fine for over a month and still works in my backflip though. I think the gf has a simcard in her phone so I am going to see if it reads hers when she gets here.

Shwaguy said:
No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request
Click to expand...
Click to collapse
Maybe dumb question..
After rthe steps did you Flashed the actual ROM????
Just askbecause i dont see it. Mentioned
Also, If you disable safe systemthen youshould be able to go back to regular stock.....
Enviado desde mi XT862 usando Tapatalk

Ya, I flashed the rom, tried the alpha 6 ics one also. It was after doing this then rebooting (still in safe) that i got the bootloop issue. I disabled safe system and went back.
Seems it doesn't really matter now though. It doesn't seem to be reading my simcard. No service (except wifi), Tried enabling simlock, says there is no card in it. Card works in my Backflip. I tried the g/f's Bell card and still no service, etc. Going to search around a bit and see if anything pops up but I may be sending it back. lol

Enter password to use encrypted device storage

I have a problem.
When installling TW Roms (latest ones) I get "Enter password to use encrypted device storage" - and no matter what passwords I try - it doesn't go further.
When I clean install other roms, it works.
Any Idea?
Search function doesn't work on this site, maybe there are some others with similar problems, hopefully it is curable!

Hae you ever used encryption or exchange or vpn?
Sent from my GT-N7000 using xda premium

lio02 said:
I have a problem.
When installling TW Roms (latest ones) I get "Enter password to use encrypted device storage" - and no matter what passwords I try - it doesn't go further.
When I clean install other roms, it works.
Any Idea?
Search function doesn't work on this site, maybe there are some others with similar problems, hopefully it is curable!
Click to expand...
Click to collapse
Have you encrypted your phone in the past or perhaps its secondhand?
Try formatting your sdcard + flashing a different kernel using odin and try again..

After trying everything in a similar scenario, I input the wrong password about 15 times on a TW-based ROM - then everything was deleted and it was fine

giatros said:
After trying everything in a similar scenario, I input the wrong password about 15 times on a TW-based ROM - then everything was deleted and it was fine
Click to expand...
Click to collapse
I tried didn't work. Although mine is stock rom. ANy update on this OP

xaragen said:
I tried didn't work. Although mine is stock rom. ANy update on this OP
Click to expand...
Click to collapse
What happened when you did that?

giatros said:
What happened when you did that?
Click to expand...
Click to collapse
Nothing kept on saying try again.
I went into recovery (stock recovery) and did factory reset and wipe cache. Still the same screen.

xaragen said:
Nothing kept on saying try again.
I went into recovery (stock recovery) and did factory reset and wipe cache. Still the same screen.
Click to expand...
Click to collapse
Did you persist enough times? After some point there is a timer that you can't try for a couple of minutes and then a countdown...

giatros said:
Did you persist enough times? After some point there is a timer that you can't try for a couple of minutes and then a countdown...
Click to expand...
Click to collapse
after reboot I am still trying. Will update if it gives me anything other then try again.
I do not remember setting up any encryption. Though I did at some point used exchange but deleted that account after a while. So when I updated nothing was on it no passwords.
---------- Post added at 04:23 PM ---------- Previous post was at 03:54 PM ----------
Yeah no luck. I lost count as to how many time I tried again. It remained the same.

I can only suggest installing the xperia-sized ROM by AminX..... this is the one that let me reset.
Sent from my GT-N7000 using xda app-developers app

SOLVED.
Ok guys just a quick update. I haven't had time and forgot about this thread but here's what I did and I am posting here so that somebody in same situation could benefit. I created a note to self in past and found it.
"In case I ever get that annoying Encryption message.
Do the following:
1) For this method to work you must have access to SDcard or internal memory.
2) If you dont have access, make sure you have Superuser file on any type of Memory (internal or external).
(On the sidenote I will always keep that in internal as well as external card from now on.)
3) Fire up Odin - Install Clockwork Recovery in PDA - Do Not Check reset time.
4) START....
5) Install zip from sdcard... superuser
a) it will fail first time with error code 0.
b) do it again (dont worry about that).
6) Fire up odin again.
7) Rename the MD5 i717 file to TAR. (see NOTE)
8) PDA that ****.
9) START and wait....
10) PASS you're done. Thank PAST ME...!!!! "
NOTE : Now I think this will work for other devices than just I717. You must get a stock rom TAR for your device. Dont get the latest but the one before latest.
After booting is complete and the device no longer asks for passcode. Go into security settings of the device. Then Setup a password lock for your device. Make sure its password lock and is at-least 8 characters. NOTE DOWN THAT PASSWORD
REBOOT.
Device will ask for password to unclock, Enter it and then go to security settings again and disable password unlock it or simply set it to slide.
Make sure you have NOT enabled any device Administrators in security settings. Most commonly people with exchange accounts on phone have that.
After this you can flash the any ROM you intend to flash (On stock rom it will still appear.) and if that encryption screen comes up use the password you setup previously.
Again I cant guarantee this will work for individual devices but yeah It worked for me and my friends device (both i717). Its now a goto method to get rid of it.

xaragen said:
Ok guys just a quick update. I haven't had time and forgot about this thread but here's what I did and I am posting here so that somebody in same situation could benefit. I created a note to self in past and found it.
"In case I ever get that annoying Encryption message.
Do the following:
1) For this method to work you must have access to SDcard or internal memory.
2) If you dont have access, make sure you have Superuser file on any type of Memory (internal or external).
(On the sidenote I will always keep that in internal as well as external card from now on.)
3) Fire up Odin - Install Clockwork Recovery in PDA - Do Not Check reset time.
4) START....
5) Install zip from sdcard... superuser
a) it will fail first time with error code 0.
b) do it again (dont worry about that).
6) Fire up odin again.
7) Rename the MD5 i717 file to TAR. (see NOTE)
8) PDA that ****.
9) START and wait....
10) PASS you're done. Thank PAST ME...!!!! "
NOTE : Now I think this will work for other devices than just I717. You must get a stock rom TAR for your device. Dont get the latest but the one before latest.
After booting is complete and the device no longer asks for passcode. Go into security settings of the device. Then Setup a password lock for your device. Make sure its password lock and is at-least 8 characters. NOTE DOWN THAT PASSWORD
REBOOT.
Device will ask for password to unclock, Enter it and then go to security settings again and disable password unlock it or simply set it to slide.
Make sure you have NOT enabled any device Administrators in security settings. Most commonly people with exchange accounts on phone have that.
After this you can flash the any ROM you intend to flash (On stock rom it will still appear.) and if that encryption screen comes up use the password you setup previously.
Again I cant guarantee this will work for individual devices but yeah It worked for me and my friends device (both i717). Its now a goto method to get rid of it.
Click to expand...
Click to collapse
After trying this method for a few hours it turns out that I had to downgrade, only after that there was an override on the encryption password requirement. Just in case you don't mind reinstalling evrything.

[Q] Rooted Captivate running 2.3 freezes after Android load

Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.

ktvanhorne said:
Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.
Click to expand...
Click to collapse
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.

BWolf56 said:
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.
Click to expand...
Click to collapse
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT

ktvanhorne said:
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT
Click to expand...
Click to collapse
My guess is that something got corrupted, so yes, software issue. Find the required Odin and 2.3 kernel for the I9000 and flash them in download mode. It should run fine after that.

Got things resolved
Thanks for the help. I tried to follow your steps, but I could never get the phone connected to the PC. It would charge, but not connect to let Odin in. (It will connect to another PC without issues. I uninstalled and reinstalled the drivers, but no dice). However, in the process of putting the phone into download mode and rebooting it back somehow got me into the recovery screen. I did a factory reset through there and it worked.
Thanks for the help of all the contributers to the site.
K

TWRP asking for password

Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?

Please search next time...
The password is as follows: (type or exactly as written below)
default_password

Pilz said:
Please search next time...
The password is as follows: (type or exactly as written below)
default_password
Click to expand...
Click to collapse
I typed it as you wrote it with the underscore and no uppercase letters but it gives me Password Failed, Please Try Again
I actually made a quick search before posting and I tried this password before.. Another solution is to wipe data/factory reset but if possible I'd like just to re-install TWRP or remove the password somehow

you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.

xBeerdroiDx said:
you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.
Click to expand...
Click to collapse
I assumed he already did this, but in which case we have all been here at one point. I learned the hard way twice now...

kal eh said:
Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?
Click to expand...
Click to collapse
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me

TheSkillfulTroll said:
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me
Click to expand...
Click to collapse
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.

xBeerdroiDx said:
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.
Click to expand...
Click to collapse
Op said he doesn't want to wipe data and he doesn't have access to recovery (I think) saw your post about manual flashing though, pretty good
Sent from my Nexus 6 using XDA Free mobile app

ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?

sinceg1 said:
ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?
Click to expand...
Click to collapse
could be a twrp bug? are you on the latest version? you can try just updating the recovery, via fastboot or app(like flashify). if that doesnt work you can try wiping out the recovery partition(via fastboot) then reflashing the recovery.

yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?

sinceg1 said:
yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?
Click to expand...
Click to collapse
why? all that is is flashing supersu or removing it? that had nothing to do with your recovery. you dont need root to have a custom recovery.

ok, so it seems the next thing to try is wipe recovery partition then reflash recovery. i'll begin looking into how to do that. thank you again.

Had this problem last night, if you have a pattern password try using this:
1 2 3
4 5 6
7 8 9
I had an upper case L and it translated to 2589 and that's what unlocked it for me. Hope this helps someone

Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...

mclisme said:
Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...
Click to expand...
Click to collapse
Are you encrypted?

i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?

sinceg1 said:
i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?
Click to expand...
Click to collapse
Absolutely. If your storage is encrypted, TWRP cannot access it without you entering a password. If you don't enter the password, your storage would appear to be blank to recovery.
I personally prefer to wipe my entire device and keep a kernel that does not enforce encryption. Encryption (in my opinion) makes life difficult for rooted users.

seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.

sinceg1 said:
seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.
Click to expand...
Click to collapse
I'm new to the N6 so I am not sure about decrypting as a process. I just did a full wipe, flashed a kernel that doesnt force encryption .

Password doesn't always work.

My 4-digit password works just fine during normal use. But after upgrading to oxygenOS 5.0.1 (OTA) , I decided I wanted to revert back to nougat. So I load my backup in twrp and reboot, and it asks for my password rather than fingerprint to unlock screen because of reboot. And that's when my password is not recognized.
This is the only password Ive ever used for my phone so its definitely the right one. I can also see notifications and accept calls, it just won't unlock the screen. I also tried the default code for my simcard but even removing it doesnt make a difference.
Next, I restore my backup for 5.0.1. that I made prior to restoring nougat, and the same thing happens, password doesn't work. I had to do a factory reset to get my phone working again.
Still determined to get good old android 7 back, I install the original recovery as to upgrade from the oneplus website. And upon booting to recovery my password is once again not recognized.
I'm now back on twrp and have no problems with my passcode. But I think this is strange so maybe someone here has an idea about what's going on.

If you're restoring a backup, you have to remove gatekeeper.pattern (or password).key and locksettings.db, once removed it will work

I moved those files from data/system to data and it worked. Thank you very much!
I noticed this also removes the lock if you set it from another computer using the 'my devices' section of your google account. But it does not remove the lock notification, to do that you simply have to set a new password from your phone.

And that's how easy it is to "hack" an Android phone. Pretty sure you can do this using adb from the stock recovery. Maybe I will try it one day.

ast00 said:
And that's how easy it is to "hack" an Android phone. Pretty sure you can do this using adb from the stock recovery. Maybe I will try it one day.
Click to expand...
Click to collapse
AFAIK stock recovery allows only sideloading via adb

przemcio510 said:
AFAIK stock recovery allows only sideloading via adb
Click to expand...
Click to collapse
Not sure about Oneplus, but we have a Prestigio tablet here and I managed to delete an entire partition from the stock recovery. Wipe data didn't help a bootloop so I actually wiped it for good.
I hope other manufacturers aren't that foolish, but I'm not sure they know better.