i am finding it annoying to put pin each time i have to unlock screen/wake up prior to update to nougat it was simply FP only for unlock/wakeup and pin was required only on restart of phone or after power off.
any solution forunlock with FP without pin ?
thanks for understanding my problem
asharma7 said:
i am finding it annoying to put pin each time i have to unlock screen/wake up prior to update to nougat it was simply FP only for unlock/wakeup and pin was required only on restart of phone or after power off.
any solution forunlock with FP without pin ?
thanks for understanding my problem
Click to expand...
Click to collapse
What? That's not normal. The normal is PIN required just after reboot. After that you just unlock using fingerprint.
Sent from my Honor 8 using XDA Labs
But i am unable to get unlock with FPS alone and each time i have to enter pin...i have factory reset also on bln-l22c675b320 offical update
I updated to nougat and unlock with only fp
No pin required
May be u had finger print and pin before updating to nougat
I had simple swipe unlock, no fp, no pin on MM right before updating to nougat
---------- Post added at 06:52 AM ---------- Previous post was at 06:43 AM ----------
Not sure but May b roll back to MM, keep simple swipe lock and then update to nougat
---------- Post added at 06:57 AM ---------- Previous post was at 06:52 AM ----------
Means, set screen unlock password to none (no password, no pin, no pattern), this will remove fp also
Then update to nougat
doctor007 said:
I updated to nougat and unlock with only fp
No pin required
May be u had finger print and pin before updating to nougat
I had simple swipe unlock, no fp, no pin on MM right before updating to nougat
Click to expand...
Click to collapse
This doesn't matter. You can upgrade without doing this.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
This doesn't matter. You can upgrade without doing this.
Click to expand...
Click to collapse
Exactly, this is my case where everything has remained as it should.
Anyway OP, this sounds really weird; try to remove pin code from security settings and to remove fingerprint too (just to test), then reboot your phone and put 'em on again. If the error persists, you could try to rollback to MM or full wipe it and then check if things get better...
Related
I wipe the rom out of my phone and I can do the oem unlock now to do bootloader and install a new rom, can anyone help me ?
how would you wipe the rom from your phone without unlocking it ? , also flash factory firmware to restore your phone to a woking state
lol.. how did you do that? it shouldn't be possible to wipe your firmware without oem unlock
HelpMeruth said:
lol.. how did you do that? it shouldn't be possible to wipe your firmware without oem unlock
Click to expand...
Click to collapse
yea i thought the same thing .. :/
If you still have a bootloader, you should still be able to raise the unlock request code through adb.
---------- Post added at 03:43 PM ---------- Previous post was at 03:41 PM ----------
The entire sequence is run from the bootloader and doesn't require ROM to boot.
mven45 said:
If you still have a bootloader, you should still be able to raise the unlock request code through adb.
---------- Post added at 03:43 PM ---------- Previous post was at 03:41 PM ----------
The entire sequence is run from the bootloader and doesn't require ROM to boot.
Click to expand...
Click to collapse
But it does require OEM Unlocking be enabled in Developer Options first, or it won't work. I think that is OP's issue.
Sent from my MotoG3 using Tapatalk
I have an lg leon with android 5.0.1 and i dont find the enable OEM button in the developer settings :/
Borduni said:
I have an lg leon with android 5.0.1 and i dont find the enable OEM button in the developer settings :/
Click to expand...
Click to collapse
Wrong forum...
I'm curious to know if there isnt an adb command that will enable oem unlock without having to boot into ROM?
mven45 said:
I'm curious to know if there isnt an adb command that will enable oem unlock without having to boot into ROM?
Click to expand...
Click to collapse
Without booting into ROM means via Fastboot (not ADB), and no, OEM Unlocking was specifically designed to not be done from the bootloader or by any means other than the "owner" allowing on a working system. Meaning it is designed so that it can't be done without proper permissions. So far no one has found a way to enable OEM Unlocking on a device that has it implemented, without booting into the ROM and doing it through the developer menu.
Seems foolish and against the spirit of asop.
mven45 said:
Seems foolish and against the spirit of asop.
Click to expand...
Click to collapse
No, actually it doesn't at all... AOSP is the open source android project, the core of Android, and like any good operating system it has security features to protect personal information and property. The features are not blocked or removed, they are clearly available with a few extra steps, under normal circumstances the situation the OP has cannot exist and they should be able to just send the phone in for repair because this is device failure.
I have a moto g3
I tried to root it with kingroot apk and suddenly it made device to turn off and not getting on
And i took it to service center and they gave me the device and now its asking google account password and its saying it need only that password when i registered the device and i forgot that
Now how to bypass this or how to remove everything and install custom rom by rooting it but i cant do cuz its a locked bootloader now
Plz show some way to this prblm
tvschaitanya said:
I have a moto g3
I tried to root it with kingroot apk and suddenly it made device to turn off and not getting on
And i took it to service center and they gave me the device and now its asking google account password and its saying it need only that password when i registered the device and i forgot that
Now how to bypass this or how to remove everything and install custom rom by rooting it but i cant do cuz its a locked bootloader now
Plz show some way to this prblm
Click to expand...
Click to collapse
bro even i have the same problem did the service center said if the warranty was void or not?
---------- Post added at 11:28 AM ---------- Previous post was at 11:24 AM ----------
rohit951000 said:
bro even i have the same problem did the service center said if the warranty was void or not?
Click to expand...
Click to collapse
and how much time they took for the process?
AND i do remember my google password!
hi, i saw your problem ..
is your device working now ?? i am eager to share my knowledge if there is any problem..
You can try lost101's fastboot flashing method to make the phone bootable at least. I am pretty sure FRP will triggered so people with password are lucky.
Broadcasted from Zeta Reticuli
FRP cannot be bypassed on the Moto G 2015 with a locked bootloader, and the bootloader cannot be unlocked well FRP is active because you need to get to the Dev Options and enable it to be unlocked or enable ADB.
It's a catch-22, FRP cannot be bypassed well locked, and you cannot unlock well FRP is actively protecting the device, which is EXACTLY how it should work... no password, no access... if you "forgot" your password or google account, that rests clearly on the owner.
No amount of flashing ROMs, factory resets, flashing factory images, etc., is going to get around this. Get the correct Google account and password, throw it in the trash, or throw it in a drawer and hope someday someone might find an exploit around the FRP on the Moto G3, for now, there is no way.
rohit951000 said:
bro even i have the same problem did the service center said if the warranty was void or not?
---------- Post added at 11:28 AM ---------- Previous post was at 11:24 AM ----------
and how much time they took for the process?
AND i do remember my google password!
Click to expand...
Click to collapse
service center people can do it
they took 500rs
for that and gave back within 2hours
Hi Guys! im trying to lock my bootloader again for warranty reasons. i just cant seem to be able to do it, can anyone give me a little guide or link me to one? would be much appreciated. im having current EMUI 4.0 version on it.
go here and download honor multitool:
http://forum.xda-developers.com/honor-6/general/honor6-multi-tool-t2963060
plug the phone to the pc, then open the multitool, select B (Bootloader) then use the key 2 (Re-lock) you must have the code you used to unlock it. Follow the procedure and you are locked again.
no use..
even if you locked your bootloader again... they will somehow find it out that you havd unlocked it before, so/.
thilak devraj said:
no use..
even if you locked your bootloader again... they will somehow find it out that you havd unlocked it before, so/.
Click to expand...
Click to collapse
It says in fastboot mode, bootloader relocked so they will know for sure
code will be 1 instead of 0 even if u unlock so its useless
They dont take warranty serious. I had bootloader unlocked, cwm flashed, bootloop, no unlock key, no adb function( remote:command not allowed) and they fixed it. Didn't had to pay one cent. Now i learned from my mistakes
Sent from my H60-L04 using XDA-Developers Legacy app
Lukalion said:
They dont take warranty serious. I had bootloader unlocked, cwm flashed, bootloop, no unlock key, no adb function( remote:command not allowed) and they fixed it. Didn't had to pay one cent. Now i learned from my mistakes
Sent from my H60-L04 using XDA-Developers Legacy app
Click to expand...
Click to collapse
oh my god, they didnt charged you?? thats the first time i ever heard !! WARRANTY FOR AN UNLOCKED PHONE??
ps: glad you did it out ..:laugh:
how to root H6-L04C636B860 EMUI 4.0.1 marshmallow
:crying:
---------- Post added at 04:08 PM ---------- Previous post was at 03:54 PM ----------
how to root H6-L04C636B860 EMUI 4.0.1 marshmallow
kecikla said:
:crying:
---------- Post added at 04:08 PM ---------- Previous post was at 03:54 PM ----------
how to root H6-L04C636B860 EMUI 4.0.1 marshmallow
Click to expand...
Click to collapse
first you need to unlock bootloader (you have to know something about adb and fastboot, else check in youtube , its the best), then you have to flash twrp , then flash supersu
i suggest you to search in youtube..
I'm tired of looking for but cannot find. .over 3month already. .
http://www.pantomath.xyz/honor-6-root-guide-marshmallow-emui-4-0-twrp/
Hope this can help
Sent from my H60-L04 using XDA-Developers Legacy app
I can't enter recovery (Your device is corrupt . It can't be trusted and may not work properly) .
Bootloader is locked .
What happens if you try to reboot to the OS?
Sent from my ONEPLUS A3003 using Tapatalk
Google vendor image download and the. Flash all???? Strange your bootloader is locked. Have you played with custom ROMs on this device ? I can't just presume u have.
Sent from my Pixel using Tapatalk
@usernome, this belongs in the Q&A section. Please report your own post to a moderator to ask them to move it by clicking the exclamation point in the triangle /!\ in the lower left corner of your first post in this thread.
Fed2x said:
What happens if you try to reboot to the OS?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
That's how it came . I don't know what happened .
iamdarren said:
Google vendor image download and the. Flash all????
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I tried that . I get some errors . I will post the log later .
You said earlier it came like this? Did you buy this phone and then you turned it on and this happened? It's very important you explain as best as you can so I can help you properly.
The phone was simlocked . Someone unlocked it (he unlocked the bootloader and then unlocked it with a box) . The phone was then sold to a customer who said that he wanted to update OTA . Then the phone became bricked .
Sent from my HTC Desire 820 using Tapatalk
If you try to unlock the bootloader with fastboot flashing unlock does it work or do you get an error? If you can't unlock the bootloader and flash the full factory image, you will likely have to try to get it replaced by Google.
exad said:
If you try to unlock the bootloader with fastboot flashing unlock does it work or do you get an error? If you can't unlock the bootloader and flash the full factory image, you will likely have to try to get it replaced by Google.
Click to expand...
Click to collapse
I can't unlock the bootloader (OEM unlock is not activated) .
There is no possibility to flash it even if the bootloader is locked ?
usernome said:
I can't unlock the bootloader (OEM unlock is not activated) .
There is no possibility to flash it even if the bootloader is locked ?
Click to expand...
Click to collapse
No you cant flash it if the bootloader is unlocked.
TonikJDK said:
No you cant flash it if the bootloader is unlocked.
Click to expand...
Click to collapse
So , if I brick my phone by mistake , Google left me no possibility to repair it ?
usernome said:
So , if I brick my phone by mistake , Google left me no possibility to repair it ?
Click to expand...
Click to collapse
If you brick your phone with a locked bootloader it wasn't your fault. Nothing you can do to it, can't root it, can't mod it. Just like any other locked phone. If it dies, send it to them for warranty.
usernome said:
I can't unlock the bootloader (OEM unlock is not activated) .
There is no possibility to flash it even if the bootloader is locked ?
Click to expand...
Click to collapse
No, basically everything you described was a terrible idea and it makes zero sense to intentionally lock the bootloader of a phone you just finished hooking up to a black box to forcibly modify software.
Never lock the bootloader of a modified device, that is just a given.
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
usernome said:
So , if I brick my phone by mistake , Google left me no possibility to repair it ?
Click to expand...
Click to collapse
They absolutely left you with the possibility to repair it.
Then you turned that possibility off and locked the bootloader...
scryan said:
No, basically everything you described was a terrible idea and it makes zero sense to intentionally lock the bootloader of a phone you just finished hooking up to a black box to forcibly modify software.
Never lock the bootloader of a modified device, that is just a given.
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
They absolutely left you with the possibility to repair it.
Then you turned that possibility off and locked the bootloader...
Click to expand...
Click to collapse
If you lock your bootloader with custom firmware what happens exactly? I know unlocking wipes the device but I can't remember what happened the last time I had to lock my bootloader. I've read it doesn't wipe. I was doing things too quickly to remember for myself..
What do you mean sim locked?
seshaz said:
What do you mean sim locked?
Click to expand...
Click to collapse
holy sh*t I'm a scrub I thought unlocking your phones bootloader magically allowed you to switch networks.
mark7807 said:
holy sh*t I'm a scrub I thought unlocking your phones bootloader magically allowed you to switch networks.
Click to expand...
Click to collapse
Lmao
---------- Post added at 02:42 AM ---------- Previous post was at 02:41 AM ----------
seshaz said:
Lmao
Click to expand...
Click to collapse
Well there is that and then there's the fact that the pixel is carrier unlocked. Sounds like this guy had no clue what he was doing with this phone. Also like to know what "box" you hooked the phone up to
Has the original poster tried to unlock bootloader again? The pic in the OP shows fastboot. That looks potentially hopeful. Hope that OTA wasn't 7.1.2
Hopefully the seller was legit, maybe the phone is still under warranty??? Waiting sucks, but if it's under warranty you can fix it for free. Might be worth the wait. If not if that's not an option...
I'm guessing this is a Verizon phone? If so, start worrying, bit don't quit, unless you are prepared to spend more money on a new phone. As long as you have fastboot, you have options.
I dont have open my bootloader but in bootloader i see FRP is Unlock. The other is locked but why is FRP Unlock?
Rommco05 said:
If is locked bootloader you can make one test. Go to Developer section and check OEM. I think right now is enabled. So disable OEM and again check FRP in fastboot. Don't forget, before unlocking bootloader always enable OEM, becasue if you unlock bootloder with OEM disabled you can't anymore switch to enable
Click to expand...
Click to collapse
You're right, if FRP is unlocked = OEM enabled by the respective voice on developer options menu
I have unlocked boot loader but by accident must have left this Oem enabled because now I am getting error on fastboot screen about FRP enabled and I am not allowed to flash anything via fastboot
So do I need to relock the bootloader now in order to have the option inside of developers options to Oem enabled?
I have read that people that unlock and then relock the bootloader have run into many problems after doing so
Somebody help me, please. I am really depressed, I feel now that I will be stuck on build 360 for the rest of my life. And I cant even sell the phone used in this condition because i dont want the bad karma of selling a crippled phone to an innocent victim. It is against my religious beliefs to inflict harm purposefully onto another. So I am in bad shape PERMANENT if I cannot get this working. Also I am in bad financial condition also have lost alot of money on other tragedies recently in my personal life. Im really depressed about this =(
fc3211 said:
Somebody help me, please. (...)
Click to expand...
Click to collapse
Hey explain more, please; from which situation you stumbled here? Have you already tried dload method? You have custom recovery or not? Can't know what to do without an easy resume about how you came here
RedSkull23 said:
Hey explain more, please; from which situation you stumbled here? Have you already tried dload method? You have custom recovery or not? Can't know what to do without an easy resume about how you came here
Click to expand...
Click to collapse
I have rooted Honor 6x BLN-L24C567B630 with OpenKitin Twrp
I have tried dload method (But I can only get the 365 and 366 builds. Even though I am currently on Build 360 I am not able to obtain the dload files for 360 because on the website the files are not available to download.
So I have tried to unzip the build 365 files into the dload folder of my SDcard and then power off phone and held the 3 buttons to turn it on but the update always fails at 5%
I have FRP lock (that is my big problem) and I am no longer able to change it inside of developer options because the option is greyed out after i unlocked my bootloader. I have also tried to boot into fastboot to flash the stock boot.img and recovery.img but flashing fails because of the FRP lock.
The only other idea I can think is to relock the bootloader and hope that this will allow me to then go to developer options to turn off the FRP lock that is giving me so much trouble. But I want to confirm with you that this will be okay because I dont want to permanently brick my phone. I am afraid to relock the bootloader because I have read posts of others who did so and have catastrophic results.
So any advice? Else I am stuck on build 360 for the rest of my life. If I could relock the bootloader and loose root permanently and go back to stock I would be okay with that. I cant even sell the phone used because it has system notification about build 365 ota update available but when you try to install it the update fails (because of the FRP lock and the fact that I have TWRP). So eBay customer would immediately try to run the system update and it would fail and then they would complain to me and ask me to refund their money.
So unless I can fix this issue phone is not capable of being sold. How do you think I will feel when Oreo update is distributed and I will be the only one that cannot install it because of my FRP lock?
UPDATE: I think I see what I was doing wrong, I was tryinf to flash build 365 and build 366 even though I am currently on build 360. So I downloaded again the build 360 files and unzipped it into the dload folder.
THis time it went all the way to 100% and it says it was a success. But after that it restarted the phone and now I am at the blue HONOR splash screen and has been over 5 minutes stuck there so I am getting nervous again.
Uggggg.... Its been over 15 minutes now and its still stuck at the blue splash screen that says HONOR.
How long should I wait before I try to hold down the power button to restart the phone? Im planning to wait at least 1 hour. I have it with the charger plugged in.
Boy I hope I didnt brick the thing permanently. Thats the last thing I need this week with all my other problems that I am struggling with
---------- Post added at 07:35 PM ---------- Previous post was at 06:40 PM ----------
I finally got impatient and rebooted it by holding down the power button but it remained stuck on the splash screen. Then I tried holding down Volume up + Power and I was at black Emui recovery and there was option to do factory reset. I pressed FACTORY RESET and phone looks like it is okay now, I was able to get into the Emui white screen where it asks you what language and begins new phone setup. What a relief! I think I may be okay, will update this thread after completing setup procedure
---------- Post added at 07:48 PM ---------- Previous post was at 07:35 PM ----------
Booya, baby! I am back up and running. And I thank you kindly to all the gurus on this forum to help me save my phone from my own mistakes. I dont plan to root again, I am snake-bitten now after this scary experience. I am snake-bitten now and too afraid to root again
Huawei is just too dangerous with the FRP lock thing. If anyone is reading this old thread and having the same problem than feel free to PM me and I will be happy to help you step-by-step if you run into the same issue.
The main secret is that you have to flash the dload of the EXACT SAME BUILD that you had before trying to update. The mistake I made was the fact that I was rooted and I tried to use dload to upgrade up to build 365 but that is impossible. If you are rooted (and if you failed to turn off the FRP lock inside of developers options prior to unlocking your bootloader) than you can only use dload to restore to stock on the same build as you currently have. I am assuming that if you are not rooted than you can also utilize dload method to upgrade to a newer build BUT NOT IF YOU ARE ROOTED. That was the main lesson I learned