A little problem happened today.
I'm using an A320FL Galaxy A3 2017 with a custom ROM (LineageOS 16.0 20190908 by McFy) which is rooted using Magisk v17.3 (to fix the missing Wi-Fi issue). TWRP 3.3.1.0 is up there, as well.
Today, I've tried to reset the phone and it bricked itself into an FRP lock, preventing me from entering the recovery or the phone (device will always report 'Custom binary blocked by FRP lock'). This has not happened for a few weeks until now (the phone has no password, PIN or fingerprint set, nor does it have encryption of any kind), so it kinda frightened me seeing that the internal storage and data are gone... Has anyone had any problems that are similar to mine?
systremor said:
A little problem happened today.
I'm using an A320FL Galaxy A3 2017 with a custom ROM (LineageOS 16.0 20190908 by McFy) which is rooted using Magisk v17.3 (to fix the missing Wi-Fi issue). TWRP 3.3.1.0 is up there, as well.
Today, I've tried to reset the phone and it bricked itself into an FRP lock, preventing me from entering the recovery or the phone (device will always report 'Custom binary blocked by FRP lock'). This has not happened for a few weeks until now (the phone has no password, PIN or fingerprint set, nor does it have encryption of any kind), so it kinda frightened me seeing that the internal storage and data are gone... Has anyone had any problems that are similar to mine?
Click to expand...
Click to collapse
Weird, it's like bootloader was relocked. How did you reset the phone?
The same thing happened to me and I had to reinstall an offcial ROM in order to fix it. The data was gone and I could do nothing to restore it.
I did a full reinstall from scratch (flashed stock ROM through Odin and flashed LOS, OpenGApps and Magisk again) and it hasn't happened again for month and a half, even after 3-4 OTA updates installed.
Related
So I just got a used s7 Edge and decided to root it (using Odin). After about 30 mins I noticed a Security alert that needed me to restart my phone. After restarting FRP was enabled to where I couldn't boot up. Normally I would just reinstall my stock rom, but this time it wont work because I had disabled USB Debugging after I rooted. Now I cant install a new rom, I tried booting to recovery and deleting the cache as well as factory resetting but that did nothing. Does anyone have any fixes for this? Btw this is a Canadian s7 edge so its model number is G935W8.
Hey all,
My phone updated today and ever since I cannot move past the initial lock screen. When unlocked, the UI appears to crash and send me back to the lock screen. My pin code works for turning the phone off, restarting the phone and putting it into emergency mode, which indicates some sort of UI crash.
Because this is a new account I can't post a link to a video of the issue directly, but the YouTube video code is: 8ZhlH-Tt-NU
I have tried the standard fixes like wiping the cache partition and booting into safe mode, but these don't seem to make any difference. Unfortunately I never logged into my Samsung account on this device, so their 'Find My Mobile' service is not an option. I am however signed into my Google account on the device and it does have wifi/network enabled.
The phone is running PPR1.180610.011/G965FXXU2CSA8
On the phones internal memory is a bunch of photos from a recent trip to Japan, I'm a fool for not backing these up sooner but I would hate to lose them.
Has anybody experienced anything like this before, and is there any way for me to get back into the phone, or atleast recover the photos that I took?
Thanks!
Edit:
One potential route out of this I can see is sideloading the same or a subsequent OTA update using ADB to hopefully fix the issue. Unfortunately despite some digging I can't find any updates that will allow installation from: PPR1.180610.011/G965FXXU2CSA8
If anybody has any information on this specific firmware version (Is it beta 3? beta 4? ect.), its installation path and where files relating to it may be listed/hosted it would be appreciated. Also how disasterous would it be to take a mismatched OTA upgrade and modify the metadata to allow it to be sideloaded onto the phone? I assume this would almost certainly break the OS completely but I'm not too sure.
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
profi_fahrer said:
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
Click to expand...
Click to collapse
Thanks for the reply Profi I had no idea using HOME_CSC would retain user data. I have tried flashing a few different versions of Pie (wish HOME_CSC) using Odin but with no luck, every time the phone boots I have the same problem. Do you know if there is a sure way to downgrade to Oreo while retaining user data? I have seen a few posts of people attemping this and getting stuck in bootloops, eventually requrining them to factory reset.
To give a final update on this. I attempted the Oreo downgrade, upon reboot the phone was stuck in a bootloop so I updated to Pie again. When the phone booted I tried the pin code as quickly as I could, and after some glitchy graphics on the screen it unlocked. From here I turn on the stay awake while plugged in feature in the developer options and managed to transfer all my data over to PC.
I don't believe it was the firmware changes that actually made any difference, because any further attempts to put my pin in, to remove the pin code for example, failed and cause the same crashing behaviour.
All data is recovered, I have factory reset the phone and all appears to be behaving as normal again. If anybody stumbles upon this with the same issue, all hope is not lost, but unfortunately I was unable to determine a realiable way to overcome it. It seems in this case it was just dumb luck.
Thanks for the assistance.
I'm using Samsung Galaxy S9 Plus (SM-G965F) (Android Pie 9.0) and I rooted my phone by using Magisk, after that I cannot setup PIN or pattern. After I setup PIN/pattern and I go to add biometrics screen, when I confirm my PIN/pattern, there's a popup tell me that "PIN/pattern is incorrect."
How I root my phone ?
1. Flash stock Android Pie firmware via Odin
2. Flash TWRP recovery
3. Boot into TWRP
4. Wipe data
5. Flash RMM-State_Bypass_Mesa_v2.zip
6. Flash no-verity-opt-encrypt-samsung-1.0.zip
7. Flash kernel ElementalX-S9-2.01.zip
8. Flash root file Magisk-v18.0.zip
9. Reboot
Did I do something wrong ?
OMG! Finally I've found someone reporting the same issue! My situation is a bit different, but the result is the same as yours. I have a Samsung Galaxy S9 (SM-G960F), and here are a few things worth noting:
I flashed the latest Pie-based firmware for the LUX-region from updato.com through ODIN
I flashed twrp-3.3.0-0-starlte.img.tar through ODIN
I tried flashing both no-verity-opt-encrypt-samsung-1.0.zip and no-verity-opt-encrypt-6.0.zip, and I flashed RMM-State_Bypass_Mesa_v2.zip
I did not flash a custom kernel
Finally, I flashed Magisk v19.2.zip
Everything seemed to work just fine (during my limited time on Pie), but I encountered the same weird behaviour as you when trying to set up my fingerprint. If I dared to reboot my phone after that, it got stuck in some weird loop where the SIM unlock screen will show for a split second, and then turn off again for a moment. That pattern was repeated continuously, and sometimes it rebooted itself. I could basically not get back into my phone.
Please, PLEASE, tell me you've figured this out!? Or if not you, then somebody else. For now, I've restored the backup I made through TWRP prior to flashing Android Pie, so I'm back to a rooted version of Android Oreo. I'll probably stay there unless I have a solution for this problem, cause I just can't see myself using my phone without root access.
The joys of being a power user...
Same problem
I'm using a Samsung S9 (SM-G9600) and my rooting process was quite the same as yours. Phone works just fine, but I can't seem to set any kind of lock screen (including fingerprints, which forbids me from using fingerprint unlock on other apps too).
It's Samsung security stuff, you'd have to remove it to be able to use security again.
As to what exactly you need to remove, I'm not really sure.
Anyone got any updates? I got the same problem. I tried removing the *.key files in twrp to reset the Pin. It does work and it resets the pin asking for a new one but when i set it to 0000 and try to register a fingerprint it says the pin is incorrect.
Hi everyone,
I have a Xiaomi A2 which went into a bootloop due to a buggy OTA update. It's a bug in the update, and a lot of people are affected. See this post for details.
I really a rather vanilla setup (original Android One ROM). The only exotic thing I did was to unlock the bootloader. Everything else is untouched.
When I installed the Oct 2020 OTA update my phone went into a boot loop. So I booted on TWRP from fastboot, and using adb pull /dev/block/mmcblk0p69 data.img I got an entire disk image of my data partition on my PC.
Using fastboot I then flashed the previous-working OS (version V11.0.14.0.QDIMIXM) but then when I boot my phone I now have a weird problem: my PIN isn't recognized anymore! If I try and remove /data/system/locksettings.db from TWRP, then it does remove the PIN and I can "log in" with a swipe, but then the phone gives me a never ending spinner. I assume something is wrong with File-Based Encryption and the fact that I didn't provide a PIN.
Question: why is my PIN not working anymore? How can I get it to work?
EDIT: IF RESET FACTORY DOESNT WORK FOR U JUST GO TO SERVICE CENTER(I did it after all)
Hello
My device is Global version with miui V13.0.4.0.SKIMIXM
my fingerprint stopped working a week ago, then i contaced the support and they said these solutions:
1-factory reset
2-wipe data
3-download latest package
4-clean fingerprint area
i did all and somethimes just right after booting device my fingerprint showed up and working but after about couple hours back to the problem.
on early time of this problem i had fingerprint setting but couldnt open it (couldnt add fingerprint hint) but after some times it removes from setting too then at last after wiping data and solution above , fingerprint never showed up. so i decided to flash the original rom with fastboot and after i did that my fingerprint comesback and was working but again after couple hours stopped.
the thing is if safe mode it was working. even after rebooting to normal working 2 or 3 times then after that stop working again. in safe mode CIT fingerprint tests passed successfully untill right now after half a day i dont have fingerprints even in safe mod.
so i think of downgrading to miui 12.5.7 just want to be sure is it safe to downgrade because when i wanted to flash miui13 it errored with rollback but i edited script and flash was successful.
script edit is safe for downgrade ?
and maybe is there any othe solution that im not aware of?
13eauty said:
Hello
My device is Global version with miui V13.0.4.0.SKIMIXM
my fingerprint stopped working a week ago, then i contaced the support and they said these solutions:
1-factory reset
2-wipe data
3-download latest package
4-clean fingerprint area
i did all and somethimes just right after booting device my fingerprint showed up and working but after about couple hours back to the problem.
on early time of this problem i had fingerprint setting but couldnt open it (couldnt add fingerprint hint) but after some times it removes from setting too then at last after wiping data and solution above , fingerprint never showed up. so i decided to flash the original rom with fastboot and after i did that my fingerprint comesback and was working but again after couple hours stopped.
the thing is if safe mode it was working. even after rebooting to normal working 2 or 3 times then after that stop working again. in safe mode CIT fingerprint tests passed successfully untill right now after half a day i dont have fingerprints even in safe mod.
so i think of downgrading to miui 12.5.7 just want to be sure is it safe to downgrade because when i wanted to flash miui13 it errored with rollback but i edited script and flash was successful.
script edit is safe for downgrade ?
and maybe is there any othe solution that im not aware of?
Click to expand...
Click to collapse
solution is service center...in theory no anti rollback....just check in script before flash
rayman95 said:
solution is service center...in theory no anti rollback....just check in script before flash
Click to expand...
Click to collapse
thansk for reply so youre saying that in theory there is no problem to downgrade with editing script but in real life God knows right?
Unfortunately I have the same problem on my MI11 Lite 5G.
I would be interested if I install a custom ROM e.g. CorvusOS 3.2-V v12.1 if it works with it
So if anyone has experience with it?
norryhox said:
Unfortunately I have the same problem on my MI11 Lite 5G.
I would be interested if I install a custom ROM e.g. CorvusOS 3.2-V v12.1 if it works with it
So if anyone has experience with it?
Click to expand...
Click to collapse
i tried some custom roms before i send my phone to the service center and none of them worked.today i recieved my phone back and everything is great after replacing fingerprint.