Peace ALL,
Hopefully someone can please help me!! I recently purchased a used OP2 off of Amazon. Phone received was in good shape and looked brand new. The problem I have however is that I can't bypass the initial set-up (I think it has something to do with Google factory Reset Protection).
Whenever the phone is in the initial setup process its asking for a gmail that was synced to the device before it was wiped--which of course I dont have access to. Is there any workaround for this?
Any help would be greatly appreciated
i had the same problem as i got it second hand.The thing with me was that i knew the owner.
The problem is that the previous owner wiped the device from the boot menu ( the one that looks like twrp) and not from the in menu setting.
this is why it asks for a previous mail.
I asked for his mail and password ,logged in, went to settings did a factory reset form the menu and all ok.I dont know what you could do without his mail and password.
Maybe unlock it put twrp custom rom open it and then reset it to factory settings?
Does anybody know if unlocking bootloader and flashing the stock ROM will bypass Google Device Protection (not sure if this will work as i think the OP2 is already "unlocked")?
Someone please help
I am having the same issue. I've read how you have to wait 72 hours but I am not sure if it will work.
Hi all!
I searched the entire forum for a question similar to mine, but didnt find any thread about it.
I rooted my S7 Edge G935FD using odin, and the startup screen where i get to input my pattern generates me an "incorrect" pattern!!
Once I reflash my firmare back to stock...everything works back as normal, and im able to input my pattern successfully and log in to the phone.
Am I missing something? ?
ahmedmohsin said:
I rooted my S7 Edge G935FD using odin, and the startup screen where i get to input my pattern generates me an "incorrect" pattern!!
Once I reflash my firmare back to stock...everything works back as normal, and im able to input my pattern successfully and log in to the phone.
Click to expand...
Click to collapse
Does disabling the pattern lock and then rooting it work?
Not sure what seems to be the issue, but this https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 works if you want to root ur phone. May as well flash a ROM (which will come with disable DM-Verity and root) while ur at it rather than root the phone using this method though (that's what I did anyways). I recommend Superman ROM.
Hope this helped
ahmedmohsin said:
Hi all!
I searched the entire forum for a question similar to mine, but didnt find any thread about it.
I rooted my S7 Edge G935FD using odin, and the startup screen where i get to input my pattern generates me an "incorrect" pattern!!
Once I reflash my firmare back to stock...everything works back as normal, and im able to input my pattern successfully and log in to the phone.
Am I missing something? ?
Click to expand...
Click to collapse
yes rooting or any major change to the operating system requires pin to be enable after the phone successful reboot and you get main, you can reset the pin to a pattern.
This is my understanding of what is need with any modifications to boot loader or kernal which rooting does.
I tried everything, from disabling fingerprint and pattern lock entirely to clearing the cache from the stock recovery menu, but still rooting or flashing TWRP cripples the phone into a Samsung logo stuck screen. The only way out is to re-flash back to complete stock.
Am I missing something? I recall rooting the S7 edge was much easier...whats going on?
Hello.
I have a serious problem.
tl;dr:
I forgot my pattern lock combination and I need my messages so I don't want to factory reset. Is there any other way?
Long story:
So I've forgotten my pattern lock combination and I have a job interview tomorrow at the address I received in a message.
I can't unlock my phone. I didn't write down the address anywhere else. And if I try to factory reset my phone it will get rid of all my messages.
So far I've tried:
dr.phonw - but for some reason it doesn't work on p9 lite
I've read online you can delete the password file for the pattern lock and it will unlock, I've tried using usb cable to access my files but I can't access the phone while it's locked.
I've tried installing a file manager from a sd card in recovery mode, but p9 lite doesn't have that function.
Do you have any other ideas I could try.
It might seem like a strange question, but I'm really panicking right now, the job interview is tomorrow and it's really important to me.
Any help is greatly appreciated.
So a mate of mine found an A5 recently without any identification on it. Thought he might as well keep it himself else it'll just be useless.
Problem is the phone's stuck in the initial setup so he asked me to unlock it. My plan was to install TWRP, wipe everything completely and flash the firmware again. I can't get to the settings to access the OEM unlock though. Is there any way to unlock the bootloader and/or get TWRP on there so I can completely wipe the phone?
Same situation here... How did it turned out?
Hey guys...I know I posted this in the persist thread, but I figured it might deserve a dedicated post here just in case there's a bigger issue at play or is something that's relatively unknown.
So long story short, unlike many on here I wanted to go back to a stock, locked, unrooted state after being unlocked & rooted (otherwise stock OOS) for a couple months. Unfortunately, upon doing this my fingerprint scanner stopped working (instantly errors with "enrollment was not completed - fingerprint registration error, please try again" when trying to enroll a fingerprint).
So when the guide came out the other day to repair the fingerprint scanner I tried it. I started off by re-unlocking my bootloader (from full stock, locked, unrooted) so that I could grab the persist partition backup that I hadn't done before. After rebooting suddenly, magically my fp scanner started working again. Then after verifying I could enroll several fingerprints, I booted to TWRP (didn't flash it, just booted) and flashed the magisk zip.
After this, I rebooted and backed up my now-working persist.img partition.
I then did a factory reset from the settings menu, which should return the device to 100% stock. After the reset, I verified during initial setup that the fp scanner was still working properly. I then rebooted to fastboot, and upon re-locking the bootloader received a g.co/ABH message in red saying the device was corrupt and that it would not boot.
I then used the latest 10.5.10 MSM tool to re-flash back to full stock again, which caused it to then boot up as expected. At this point, I tested the fp scanner again during initial device setup and it was once again back to not working.
I then re-enabled OEM unlocking in settings and rebooted to fastboot again. Another bootloader unlock. After reboot I tested the fp scanner again during initial device setup. Lo and behold, it's back to working again.
So I stopped midway through the fp enrollment (just hit back, didn't complete) and rebooted back into fastboot mode. Re-locked bootloader again and booted back up. FP scanner again back to not working with the same "enrollment was not completed - fingerprint registration error, please try again" error.
And once again I re-unlocked the bootloader, enrolled a FP during setup, and then used the MSM tool again. After MSM it again produced the same results - FP scanner wouldn't work upon reboot.
And before anyone asks - I am in contact with OP support for either a warranty replacement or a repair...but this whole situation just doesn't make even the slightest bit of sense to me. Basically my FP scanner works perfectly fine with an unlocked bootloader, but any attempt at re-locking it renders it useless. I do have a working persist backup, but obviously can't flash it from a locked state. Anyone else have any suggestions on something to try, or at least have any sort of theory as to why this behavior would be happening? I have never had a phone where attempting to RE-lock the bootloader has been such a freaking pain.
No one has any idea on this, or theories as to what could be taking place and causing this? OP support has been a total trainwreck so far.
Hi, Did you get a solution for this ? I am facing the same issue of fingerprint sensor not working after relocking the bootloader, although in my case I did not have to reflash the persist img. It works when unlocked and stops working when locked. As usual OP after sales are not really helpful. Thanks
Greetings,
same issue here.. has anybody an answer to this problem? It's driving me crazy...
Thank you very much!
shakathesaint said:
Greetings,
same issue here.. has anybody an answer to this problem? It's driving me crazy...
Thank you very much!
Click to expand...
Click to collapse
I've been trying to solve this issue today, as we speak. However, it seems like the guide to restore the FP reader does not apply to our phone (I have the OP8, but it behaves exactly the same) because we still need root to restore the FP reader, and it will be lost upon relock. In other words, we are stuck. OEM repair/replacement seems to be the only solution.
AarSyl said:
I've been trying to solve this issue today, as we speak. However, it seems like the guide to restore the FP reader does not apply to our phone (I have the OP8, but it behaves exactly the same) because we still need root to restore the FP reader, and it will be lost upon relock. In other words, we are stuck. OEM repair/replacement seems to be the only solution.
Click to expand...
Click to collapse
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Related, on 11.0.2.2 magisk and unlocked, my fingerprint sometimes won't recognize at all and forces password unlocks. No corrupt persist or delete and re register a finger solved it.
shakathesaint said:
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Click to expand...
Click to collapse
Oh, thank you! I will certainly try!
shakathesaint said:
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Click to expand...
Click to collapse
I'm writing just to update about the tests above: unfortunately neither of them is working, so I'm starting to think there's no other solution than sending the phone to RMA.
Has any one found a solution for this? Im facing exactly the same problem.