Database Info

G930F FingerPrintSezor Fail after factory reset.

Hello, Houston i have a problem,
before installing android 8 I used the fingerprint and it worked perfectly even after I installed perfectly without any errors Android 8 has performed as well but 2 days ago I gave a factory reset and receive the message "Attention" Make Sure the Home key is clean and dry, then try again.
I mentioned that I tried to give factory reset from the combination of the 3 buttons
* but to:
Wipe data / factory reset - works fine
Wipe chache partiton: E: Failed to clear BCB Message: failed / misc partition.
Ayone else have this problem? or if anyone knows any resolution
https://imgur.com/a/9wD5KPg.

Try doing a factory reset or flash the system again through odin.

FPSkillerPC said:
Try doing a factory reset or flash the system again through odin.
Click to expand...
Click to collapse
I did that not working....

machiavely said:
I did that not working....
Click to expand...
Click to collapse
I make a downgrade android 7 and still fingerprint error is the same

I have a similar error after downgrade from 8 to 7. I can't set a lock because settings app crash.
I did a fingerprint test using combination and works perfect so i upgrade again to 8 Oreo and fingerprint doesn't work.
Any suggestion?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

CyraX_THC said:
I have a similar error after downgrade from 8 to 7. I can't set a lock because settings app crash.
I did a fingerprint test using combination and works perfect so i upgrade again to 8 Oreo and fingerprint doesn't work.
Any suggestion?
Click to expand...
Click to collapse
I am also recieving the exact same issue however its there when recovery is started, having said that though my finger print sensor is working perfectly still and i have no app crashes in the settings, the only thing i can put it Down to is the new firmware may be partitioned slightly different as i did notice it took a very long tine to flash the oreo frinware compared to all other firmwares i have flashed,
This is the first update for oreo so is bound to be buggy as its in the beta stages of testing the next OTA update brought out will more than likely combat the issue id say its just a bug.

Impossible to reinstall a rom after root

Hello guys,
I'm new here, I've read a lot about your different topics and I'm admirative for some level god members with their answers :good: :laugh:
Indeed I'm a dev, but for websites so it's a bit different with phones for me, and I will try to explain as detailed as I can.
I have a samsung SM G965F, bought in Poland (I work here for the moment); And indeed tried to root it for private purposes.
I followed a tutorial; I was on Pie 9 (****tiest ever update for me); from there OEM in DEV tools was activated, and the TWRP was installed.
the phone wasn't root, but I had the TWRP options (when push Volume up+bixby+lock) so thought I'm on the good way, but only after, and there is my mistake, I understood by reading something that I should make faster an operation when enabled the OEM (before it start to delete all my infos) that I should switch to recovery mode (or installation) and if not there was a story with 7 days to wait.
So the phone was just reseted with only memory card datas not deleted, and the phone was working, just the OEM always disabled, and when you select to enable it it says "ok we reboot the phone you will loose all your files etcc..." and anyway after many attempts, it says always the same after the reboots, and never is enabled after. So I tried to install a new rom, and then I thought I had a problem, in the installation it was written "Secure Check Fail : PIT".
So I tried to found the right rom, with the number "6" inside as per this screen :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then the Secure Check Fail : PIT dissapeared and now its just Fail in Odin.
Also, I tried to reboot normally but it says that there was an error and I need to reinstall with smart view or smart touch, I don't really remember, so I just reinstalled the first TWRP and now the screen of my phone is looping on Samsung, and rebooting.
I'm lost, I spent from 3pm to 4 am yesterday in the internet to found a solution, so my final option is write to ask your help guys.
Hope you can help me, thank you in advance
PS: Sorry for the big picture, there is no acceptance unfortunately for resizing codes, or maybe I just still don't have access to this option cuz I have less than 10 messages, if need delete it or explain me if you need pictures, I did it 10 min ago, even if there is not a lot to do because i'm limited with my phone now

Bootloader error when starting Moto G3

A relative brought me his Moto G3 (XT1542) because it did not turn him on, he told me that the device was being updated and turned it off without knowing that something bad could happen, then he wanted to turn it on and send it to the following screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When "Start" was selected using the power button, the Motorola logo was displayed for a fraction of a second and the following screen appeared:
No matter which option is selected, "Bootloader Log" appears in all.
I have already tried to load the stock firmware but it does not take it, the same error continues.
I already thank you if you can help me solve this, it is already giving me headaches
Sorry for my bad English, I had to translate it because I don't speak that language.

As our phones are old this software may or may not work but give it a try,
https://support.lenovo.com/gb/en/downloads/ds101291
HTH

R1ffR4ff said:
As our phones are old this software may or may not work but give it a try,
hXXps://support.lenovo.com/gb/en/downloads/ds101291
HTH
Click to expand...
Click to collapse
did this work? I am stuck at the same problem

This error is indicative that either the ramdisk or kernel is corrupted. However, this is a soft brick and can be restored by using fastboot mode or RSD-Lite to flash an official firmware package to your device. Doing so will restore the device back to a factory stock state (but will not relock the bootloader if it has been unlocked. But, since relocking the bootloader carries no advantage except warranty related advantages, this is of little consequence). Official firmware packages for the Moto G 2015 can be found here https://mirrors.lolinet.com/firmware/moto/osprey/official/
Select the most current package for your variant. There are numerous guides here on XDA for restoring Moto devices using fastboot or RSD-Lite. The best fastboot guide I have seen is @lost101's tutorial & firmware repo here https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
(Official firmware is available at either of the above links. Just choose a link and find the most current build for your device.) @R1ffR4ff's earlier post linking the Lenovo Motorola Smart Assistant should also fully restore your device, and is less complicated than manually flashing an official firmware package. As such, the methods outlined in my post should only be used if the Smart Assistant did not do the trick.

Please help! FRP bypass Huawei P30.

I am editing this post as I have become more educated in the last three months since I made the original.
I bought a broken phone. It had a bad battery and could not switch on in order for the phone to be reset. Neither could the seller provide me with any account info in order to remove the account before or after the reset was done I bought the phone from a repair shop as it was abandoned by the first owner as it was deemed uneconomical by them to repair.
I have replaced the screen and the battery with OEM items and have been trying for 2 months to get the phone unlocked.
Details that may be important
P30 ELE-L09
EMUI 10.1
What I have tried:
Every tutorial on YouTube related to P30 FRP lock and EMUI 10, and even some for other related Huawei devices like P20 and P30 lite.
I have tried eRecovery methods of update and restore, USBOTG method to update and both downgrade firmware. Everything fails. The recovery has buttons for emergency backup, but if I select this it reboots the phone back to the OOB setup. Also if I try to reboot to Safe mode, it does the same thing just in Safe mode.
HiSuite Proxy. @IProfessor This is still where I have issues as I feel that this is the most likely to succeed. Sadly every time the firmware reaches the point it will begin to install, it stalls and fails. I have logged it and will post them up here.
I believe the FRP lock is blocking me from resetting this device somehow, I just cannot figure out how and how to circumvent it. I am am being patient and I have time, the phone is not for daily use, yet.

Deleted.
New update

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The process fails after the files are decompressed

Up.
Anybody with a solution that doesn't involve paying for it?

I'm looking for an answer too..

I took the phone to my local cellphone repair guy.
He had a guy that flashed the firmware directly to motherboard. The only downside is these guys sometimes use the wrong region firmware, as is my case.
Total spend was R350 ZAR.
P.S. are you not also on the vwclubsa forum?

Magisk hide "Settings" app force closing

A few weeks ago, my hidden Magisk Manager (hidden as "Settings") stopped working. When I try and launch the generic Settings app it sets up, I get the normal FC menu ("Settings keeps stopping") error. I also get it when I open up any app that I previously allowed root access to, but obviously I cannot add new apps superuser access. I also get the FC every time I reboot the phone.
I haven't updated my OnePlus 9 Pro since the ColorOS 12 update came out, as 1) was not a fan, and 2) everything I read said I'd need to wipe the phone to get root back. Needless to say, it's been a while. My phone is currently on the 11.2.10.10.LE15AA version.
This just started happening one day, but I have no idea why. I am not sure what version of Magisk I am on, because I can't open the app. I also tried downloading the latest and installing the APK, but when I launch it, it's says things need to be "fixed" and to reboot. I then get the choice the normal Magisk installer brings up. I tried doing a direct install, but it failed. I also tried to restore the boot image, but it said the backup wasn't found (never seen that either, as I restore images every time I do an OTA).
Not sure what to do at this point. I'm at a complete loss. I would appreciate any help you guys can provide!

Do a LOGCAT to get the very reason why Magisk is not working.

I tried to get it as quickly as possible to minimize clutter, but it's still pretty long. I believe I've found where in the log the FC I captured (by looking for "zygote", but not sure what to make of it. It sounds like a file or something is missing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Doesn't seem like the logcat file got attached.
Oh well, here's a link:
FilePost
filepost.io