My Nook just auto downloaded and installed an update that screwed up my device! Anyone else see this? WTF?
Does it automatically do the update? was your Nook Color rooted?
foxfire235 said:
My Nook just auto downloaded and installed an update that screwed up my device! Anyone else see this? WTF?
Click to expand...
Click to collapse
Yeah, does it do it automatically. I have my Nook Color at home connected to my Wi-Fi. Hopefully, it doesn't download just download it without me being there =T
foxfire235 said:
My Nook just auto downloaded and installed an update that screwed up my device! Anyone else see this? WTF?
Click to expand...
Click to collapse
How did it screw it up? I haven't received an update, been tethering all day
What is your software version in settings after the update?
I was using a rooted nook. It bricked it, and I couldn't get past the B&N logo on boot. I just had to do a factory reset.
After the factory reset, I got a confirmation dialog that said - "your nook has been updated to software version 1.0.0" ??? that doesn't seem like an update. Although maybe that's the factory default?
foxfire235 said:
I was using a rooted nook. It bricked it, and I couldn't get past the B&N logo on boot. I just had to do a factory reset.
Click to expand...
Click to collapse
Not to be a pr*ck, but if you're still able to do a factory reset, that would mean it wasn't "bricked", or did I miss something there?
Did the unit want to auto-update again once you reset?
-CC
clockcycle said:
Not to be a pr*ck, but if you're still able to do a factory reset, that would mean it wasn't "bricked", or did I miss something there?
-CC
Click to expand...
Click to collapse
I guess we have different definitions of brick. What would you call a device that doesn't boot?
A
A device that doesn't boot is a soft-brick
a brick cannot be fixed through trivial methods.
foxfire235 said:
I guess we have different definitions of brick. What would you call a device that doesn't boot?
Click to expand...
Click to collapse
As I understood "brick" means it's totally useless, other than as a paper weight or a door stop, essentially just dead weight.
I think if your device doesn't boot, but you can still recover, would be exactly that. {my device didn't boot, I had to factory reset it}
-CC
I wonder if they have something in there to detect a change to the OS that forces it to re-download ?
clockcycle said:
As I understood "brick" means it's totally useless, other than as a paper weight or a door stop, essentially just dead weight.
I think if your device doesn't boot, but you can still recover, would be exactly that. {my device didn't boot, I had to factory reset it}
-CC
Click to expand...
Click to collapse
in the venacular, "brick" means that the device is dead and cannot be fixed without replacing hardware. If a 'simple' reset will restore the device to working order, it isn't bricked it is just in a bad state.
We try to avoid the term "brick" when describing anything else because we don't want to gve the impression that we might be saying "I just did what I read in your post on the forum and now my device is broken beyond repair".
I'm fairly certain (but not 100% positive) that FW version 1.0.0 is installed automatically when you are registering the NC for the first time (like when the OOB setup is first done). After my initial setup I checked the version and 1.0.0 was installed.
And I've also noticed that if you do a factory reset and re-initiate the device 1.0.0 is automatically installed.
I'd like to see some verification that there is new software out there than this one user's report. Confirmation?
PHiZ said:
I'd like to see some verification that there is new software out there than this one user's report. Confirmation?
Click to expand...
Click to collapse
I remember somewhere, that there was a way to trigger it, or something like that... but its not a new firmware but just a redownload of 1.0
I think this is a known issue for some users after they root. I've read it before on here somewhere and in IRC.
MBM or Pokey9000 can confirm but i'm pretty sure it's nothing to be concerned with. Just re-root and see if you have anymore issues.
Mine was updated to 1.0.0 as well but I was still able to root it and do Angry Birds though.
nk414 said:
Mine was updated to 1.0.0 as well but I was still able to root it and do Angry Birds though.
Click to expand...
Click to collapse
People need to clarify more what they are talking about here.
Did you have it rooted before it was "updated" ?
Apparently these devices were rooted. While I'm sure there's a small, very small minority of XDA-ers who don't mess with their devices, the rest of us do. From a statistical standpoint it would stand to reason that these NCs were rooted.
Related
Good day,
As of about two days ago my Captivate (rooted, side loading enabled) would get stuck "obtaining address" when trying to hook up to wifi. It does this with my home access point as well as municipal wifi. It says "obtaining address" for about 3-5 minutes then says "could not connect" or similar.
I tried uninstalling all recent apps - no dice. I just reset my Captivate first through the settings menu and then through the volume buttons/power button method. It still is not working. Any ideas? Should I return it for another one? Since I did a total factory reset twice, I don't see how it can be a software problem... then again, I am new to Android.
Thanks, gents and ladies.
If you are within 30 days, I'd return.
Sent from my SAMSUNG-SGH-I897 using XDA App
cappysw10 said:
If you are within 30 days, I'd return.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Is there anything I should do besides having already reset the phone - so as not to void the warranty? The rooting and sideloading mods should be undone now, right?
Thanks for the help.
See if you can manually set an IP address. Sounds like DHCP is having issues for some reason.
Also, I am not certain but I think I remember reading that even a factory reset might leave remnant files around. Do a search (I am too lazy) and if I am right, look into wiping the phone and then reseting it.
elgo said:
Is there anything I should do besides having already reset the phone - so as not to void the warranty? The rooting and sideloading mods should be undone now, right?
Thanks for the help.
Click to expand...
Click to collapse
Rooting your phone voids your warranty. Have you done a Odin one click restore back to JFS 6 stock. That should fix your issue, and if it doesn't you know you probably need to return the phone.
ianwood said:
See if you can manually set an IP address. Sounds like DHCP is having issues for some reason.
Also, I am not certain but I think I remember reading that even a factory reset might leave remnant files around. Do a search (I am too lazy) and if I am right, look into wiping the phone and then reseting it.
Click to expand...
Click to collapse
Thanks Ian - I did a factory data reset and then reset it - let me see if I can find another way to wipe the phone. About to try manual DHCP as well.
Thanks for all the help!
flashman2002 said:
Rooting your phone voids your warranty. Have you done a Odin one click restore back to JFS 6 stock. That should fix your issue, and if it doesn't you know you probably need to return the phone.
Click to expand...
Click to collapse
Will the Odin one click restore unroot my phone (therefore un-voiding the warranty?) Thanks. I use a Mac but I can run Odin under VMWare.
elgo said:
Will the Odin one click restore unroot my phone (therefore un-voiding the warranty?) Thanks. I use a Mac but I can run Odin under VMWare.
Click to expand...
Click to collapse
I re-wiped the phone and it works now. I suppose this means it's not a hardware problem!
elgo said:
I re-wiped the phone and it works now. I suppose this means it's not a hardware problem!
Click to expand...
Click to collapse
Guys, thanks so much for your help. Greatly appreciated.
elgo said:
I re-wiped the phone and it works now. I suppose this means it's not a hardware problem!
Click to expand...
Click to collapse
Is there anyway to do this without wiping the phone?
I have using this ROM for over a week, when suddenly this issue popped up today. I don't want to go through the painful process of restoring all my settings.
after doing a firmware restore http://forum.xda-developers.com/showthread.php?p=63606722 I am no able to get any screen activity at all. No boot animations, I have even tried to boot into the bootloader and still nothing....
I am pretty sure this thing is dead now....
Anyone have any suggestions on how or if it can be fixed?
plugged in to the usb port in its current state it is not recognized.
I keep seeing somethign by the name of MT65xx Preloader flashing in and out of my device manager.
Okay so I guess the firmware that I tried to flash was not the one that I had installed. So does this mean this device is now bricked for good? Can this be unbricked? All the threads I read say I have to be able to get into fastboot, as of this moment I can not get into fastboot.
which firmware version before restore and which one will be restore. Case you attempt to restore 5.01 over 5.11 it may brick your fire.
wuhoatu said:
which firmware version before restore and which one will be restore. Case you attempt to restore 5.01 over 5.11 it may brick your fire.
Click to expand...
Click to collapse
I believe that I have done this. I think the firmware that I had used 5.2.2 and I know that I had the 5.1.1 update so that would mean that I had the 5.4 firmware.
So 5.4 to 5.2 and I am pretty sure the tablet is done for =\
SurgeHawk said:
I believe that I have done this. I think the firmware that I had used 5.2.2 and I know that I had the 5.1.1 update so that would mean that I had the 5.4 firmware.
So 5.4 to 5.2 and I am pretty sure the tablet is done for =\
Click to expand...
Click to collapse
Yep it's time to return it.
http://forum.xda-developers.com/amazon-fire/general/fireos-5-1-1-attempted-downgrade-t3263960
Do you think its worth even trying to see if they will give me another one.
SurgeHawk said:
Do you think its worth even trying to see if they will give me another one.
Click to expand...
Click to collapse
Last I looked the support pages tell you to install 5.0.1 if you have problems and need to reset your Fire, so yeah.
Besides I've seen them returned for worse on here.
Hi.
A friend asked my help with his Yarvik tab10-410. Being a bit more easy to me, I'm forced to ask help.
This tablet was infected with malware. According to what I can see and read about, it might have been rooted before. Every time I go to recovery and apply factory reset, the malware keeps annoying. even without internet connection.
Tried safe mode and nothing. In comparison to my son's Chuwi alike, I noticed that there is no internal sdcard (at least it won't mount).
Don't know what I can do beside applying some based code: custom rom, stock OS, whatever.
But neither of them appeared in my googling hours.
Does anybody have a solution? My knowledge is Android matters is very limited, but I follow instructions very well.
I only was able to root my smartphone to remove some bloatware.
Thanks.
kAbUkIx said:
Hi.
A friend asked my help with his Yarvik tab10-410. Being a bit more easy to me, I'm forced to ask help.
This tablet was infected with malware. According to what I can see and read about, it might have been rooted before. Every time I go to recovery and apply factory reset, the malware keeps annoying. even without internet connection.
Tried safe mode and nothing. In comparison to my son's Chuwi alike, I noticed that there is no internal sdcard (at least it won't mount).
Don't know what I can do beside applying some based code: custom rom, stock OS, whatever.
But neither of them appeared in my googling hours.
Does anybody have a solution? My knowledge is Android matters is very limited, but I follow instructions very well.
I only was able to root my smartphone to remove some bloatware.
Thanks.
Click to expand...
Click to collapse
Are you able to boot into Android at all ?
DrGreenway said:
Are you able to boot into Android at all ?
Click to expand...
Click to collapse
First of all, thank you for replying.
Yes. I can boot the Android 4.2.2 installed in this brick. Normal and Safe mode.
kAbUkIx said:
First of all, thank you for replying.
Yes. I can boot the Android 4.2.2 installed in this brick. Normal and Safe mode.
Click to expand...
Click to collapse
Chanced are that you've already tried this but just in case, there is a hard reset option for this specific tablet.
http://www.hardreset.info/devices/yarvik/yarvik-tab10-410-noble-101/
This might work if you're trying to do a factory reset.
That's what I ment by factory reset. Since even after that the malware appears, that's why I think the tablet might have been infected as root.
Hi, You need to find a factory image to flash to your device, if not you cant fix that infection.
Semseddin said:
Hi, You need to find a factory image to flash to your device, if not you cant fix that infection.
Click to expand...
Click to collapse
Does anyone know where can I find it?
Yarvik (brand) seems to be dying if not already dead. Bankruptcy was (according to news I read) part of brand's history.
Thank you
kAbUkIx said:
Does anyone know where can I find it?
Yarvik (brand) seems to be dying if not already dead. Bankruptcy was (according to news I read) part of brand's history.
Thank you
Click to expand...
Click to collapse
You solved the problem? I cant find a stock rom
Hi.
Couldn't find any rom. Had to send my friend to oficial support. It took almost 1 month to regain control of that "brick".
Bye
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
You flashed Npreview radio on a marshmallow build?
Dead-neM said:
You flashed Npreview radio on a marshmallow build?
Click to expand...
Click to collapse
Yes! Yes I did. Could this be an issue?
H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
im going to guess, try a different kernel. as its the kernel that will boot up the device?
H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)
Dead-neM said:
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)
Click to expand...
Click to collapse
the N radio, is the same exact radio that google released for the may security patch. so the N radio, is the latest official radio for the nexus 6. so no, that wont be the problem.
simms22 said:
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
I wonder if it is. I'm using the newest Elite kernel for Marshmallow, it's always been my go to kernel. It's strange because after turning the device off, I can't turn it back on instantly, screen stays black as if it's not 100% shut down yet. I have to wait a bit before turning it back on, or entering the bootloader.
simms22 said:
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.
Yoinx said:
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.
Click to expand...
Click to collapse
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.
Yoinx said:
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.
Click to expand...
Click to collapse
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.
Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
I flash each partition manually.
H4X0R46 said:
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.
Click to expand...
Click to collapse
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.
Yoinx said:
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.
Click to expand...
Click to collapse
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe
H4X0R46 said:
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe
Click to expand...
Click to collapse
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).
Yoinx said:
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).
Click to expand...
Click to collapse
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol
H4X0R46 said:
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol
Click to expand...
Click to collapse
Depends, I've never really looked into unbricking this phone. Never had to yet.
Depending on the phone you can use tools like QHUSB and similar which let you reflash partitions just through the USB connection.
I know it's late but it could also be just the rom setup. I know a while ago there were commits that shut the device screen and buttons off before it was done shutting down (to make it appear faster) this made devices seem bricked for a short period. I don't know what ever happen to those commits, so I can't say for sure that it is them. But your issue fits perfectly.
So have I been flashing the bootloader wrong all along? I flashed in twrp a couple times but I try to flash them individually and wipe after flashing.
Sent from my Nexus 6 using XDA-Developers mobile app
Anybody able to find out why? I'm surprised to see I'm not the only one having this issue, it's annoying really.
So all of a sudden the s21 is asking for password after restart. I use the same password or 4 variations of it for these accounts. However I cannot login. I can goto web or new device and log in to my Google and Samsung accounts. But the device does t want to allow this.
I’ve seen options to flash firmware back one, I’ve done this in past. And can walk through most options. I tried ADB. But it is not enabled. And that’s become a major issue. If I could do any kind of backup, retrieval of the photos and contacts. That’s all I care about. The rest is not a big deal.
Anyone have any kind of insight? Direction? Thoughts? I can see the device in find my, but there aren’t any options to unlock. Just send message and erase.
I am willing to try almost anything, and if there’s a paid service I will try that. I’ve never seen this screen before, and have never had this issue. It does not make sense.
I purchased a new device and setup with passwords no problem. But there isn’t a backup on Google of the phone there. I tried wiping tge cache and that didn’t help either. I attached a photo of what the screen looks like.
Fwiw. I have photos of wedding and brother that just passed. i don’t want to lose those. I am desperate for any answer. Someone with tech support said I could send device to LV and they can do it. Takes two weeks and phone might not be useable afterwards.
Have you tried using Odin to flash the latest firmware?
What exactly does the password screen look like?
Electronic Punk said:
Have you tried using Odin to flash the latest firmware?
What exactly does the password screen look like?
Click to expand...
Click to collapse
I have not tried flashing anything yet. I was afraid of messing things up. But I’m familiar with the process and am willing to try
Stop stealing phones
Back up your files and do a factory reset
0rigin said:
Stop stealing phones
Click to expand...
Click to collapse
What the hell are you talking about?
Samarimama said:
Back up your files and do a factory reset
Click to expand...
Click to collapse
How would I back it up if I can’t log in?
Electronic Punk said:
Have you tried using Odin to flash the latest firmware?
What exactly does the password screen look like?
Click to expand...
Click to collapse
I do have a question about Odin, I downloaded from XDA. But it says to delete Google account before flashing or it will have problems. Wouldn’t that cause me to lose data?
No, if you back up with smart switch
Or you can bypass
0rigin said:
Stop stealing phones
Click to expand...
Click to collapse
Heffro said:
What the hell are you talking about?
Click to expand...
Click to collapse
Fellas, let's try to keep it civil. If you don't have anything of substance to contribute, it really doesn't need to be posted in this thread.
Bill720 said:
Fellas, let's try to keep it civil. If you don't have anything of substance to contribute, it really doesn't need to be posted in this thread.
Click to expand...
Click to collapse
It is 0rigins that make it first
And we didn't solved this problem
This happened to a friend of mine and i was able to "solved" it because he had a custom recovery TWRP.
I copied his files to a PC, while the phone was in recovery mode, then do a factory reset.
Later i found out that was an easier way to unlock the phone:
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
But all this requires a TWRP recovery. If you don´t have that, i guess that the password you need is the one that you have set on the device, while configuring fingerprints.
If you have "find my phone" enable, you should be able to reset that password using a browser on a PC...
Have you found out any other solution?