Related
Is there a way to avoid the message you get when you reboot after unlocking the Bootloader? The black screen where you can wait 5 seconds or tap the power to go on...
I understand that is correct to show it...but it's boring and I'm already aware of it.
http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171/page7
maybe try and follow the instruction on post number 69
Thanks for the reply but that's for Moto X. Actually before Robin I was using a Moto X and I know that procedure, point is that on Moto X was just a screenshot before booting and nothing else, here looks a bit different and you can also skip it pressing the power button. Plus I would avoid to flash/use the logo.bin of Moto X...
Can anyone of Nextbit team provide any info? Thanks !
I also don´t like the screen... the opportunity to hide would be great.
here's the same, maybe someone can make a xposed module?
kcl0801 said:
here's the same, maybe someone can make a xposed module?
Click to expand...
Click to collapse
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
uberlaggydarwin said:
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
Click to expand...
Click to collapse
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
kcl0801 said:
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
Click to expand...
Click to collapse
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
any luck on the nag screen yet? maybe gone in the july update? =D lol
I get this message Everytime, any ideas? Help would be great
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
makbomb said:
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
Click to expand...
Click to collapse
Thanks that worked
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Replace "recovery.img" at the end with the actual twrp filename and it should work.
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Saaber said:
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Click to expand...
Click to collapse
The last several message in this thread regarding 'recovery.img' was for someone trying to flash TWRP in fastboot, it has nothing to do with the 5-second nag screen.
Since khang never responded, I'm assuming this won't change and the nag screen will remain. I'm so used to keeping my finger on the power button when i reboot that it's almost habit now, so really doesn't bother me too much.
How can a device that is marketed for its unlockable bootloader and warranty coverage have an jnlockable bootloader experience that is worse than basically all devices. You don't see unlocked Sony or LG phones having boot screens that require user input. The only device I know of that is worse is the Pixel c, which has a 30 second "integrity check" if the bootloader is unlocked.
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
IS this going to change? really annoyed by it
..It's only 5 seconds, the only reason it seems longer is the fact that the message merges in with the boot logo
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
Very old thread here, but could you guys maybe release an optional "developer/enthusiast" bootloader update that gets rid of that nag screen? Or at least give the option to confirm the warning in future updates, like "I have read and understood this warning. Don't show again."
I am posting hoping some progress may or may not have been made on this. Its atrocious.
Why is it when I set a fingerprint, I set a pattern for the mandatory backup security but when I try to unlock with fingerprint it asks for a pattern saying "Pattern required to enable fingerprint"?
As far as I know, as an extra security, a pattern/pin code is necessary when the phone is restarted/ switched on, once you chose to use the fingerprint scanner.
Howling Wolf said:
As far as I know, as an extra security, a pattern/pin code is necessary when the phone is restarted/ switched on, once you chose to use the fingerprint scanner.
Click to expand...
Click to collapse
It's every time I lock it
Sent from my HTC 10 using Tapatalk
Finally figured it out.
It happens when screen is locked by a 3rd party app, in my case I use nova double tap to lock screen.
Was wondering why (and forgot to mention) it seemed random.
Edit: for Nova users looking for a workaround, if you enable screen off by root access method it will use a secure lock and enable the fingerprint to unlock.
Heisenberg420 said:
Finally figured it out.
It happens when screen is locked by a 3rd party app, in my case I use nova double tap to lock screen.
Was wondering why (and forgot to mention) it seemed random.
Edit: for Nova users looking for a workaround, if you enable screen off by root access method it will use a secure lock and enable the fingerprint to unlock.
Click to expand...
Click to collapse
yeah a lot of screenapp does ask.... if you are on elementalx you could use button mapper which gives you the same functionality of double to sleep and more doesn't ask for patter/pin everytime you unlock
This started to happen to me after a bug crashed the phone and had to force restart it holding volume down + power. I only have the default launcher so I guess it's factory reset time for me
Heisenberg420 said:
Why is it when I set a fingerprint, I set a pattern for the mandatory backup security but when I try to unlock with fingerprint it asks for a pattern saying "Pattern required to enable fingerprint"?
Click to expand...
Click to collapse
For what it's worth, I had the same issue (until I found this thread) and it was caused by Action Laucher 3. The launcher was set as a Device Administrator and was granted permission to "Power screen off". Once I removed that permission my troubles were over.
Seems to me that it makes sense once you have a fingerprint setup, to require a pin as well. Why? Because what if the fingerprint reader stops working? You won't be able to login?!?!
Not sure until the poster above mentions a pattern is required. Normally it is a pin if you want. Then the PIN required upon restart option as well that is there.
Of course, if you are rooted, you can delete the system files that control/store that...but if not rooted with TWRP, you would have to try a master reset I would assume?!?!
IDK...guess I never thought of testing that out...haha
Guys, i hope it's ok if i conquer this thread for my question but i got serious issues here.
Got my 10 back from repair today and restored my backup.
But dumb me it seems as if i set a password/patern whatever and i can't remember it.
So after the first restart i can't unlock my phone cause it's asking for the code (and won't let unlock only with fingerprint) and i can't remember.
All combination that i would have used are wrong and now i got a working phone back again (after almost 2 month of repairing) and can't unlock it.
Is there any way of bypassing/ignoring the restart password or is it possible to only unlock it again with the fingerprint that is stored?
As i don't know what i should do if i don't get my phone unlocked
bmwbasti said:
Guys, i hope it's ok if i conquer this thread for my question but i got serious issues here.
Got my 10 back from repair today and restored my backup.
But dumb me it seems as if i set a password/patern whatever and i can't remember it.
So after the first restart i can't unlock my phone cause it's asking for the code (and won't let unlock only with fingerprint) and i can't remember.
All combination that i would have used are wrong and now i got a working phone back again (after almost 2 month of repairing) and can't unlock it.
Is there any way of bypassing/ignoring the restart password or is it possible to only unlock it again with the fingerprint that is stored?
As i don't know what i should do if i don't get my phone unlocked
Click to expand...
Click to collapse
Try a factory reset via Android Device Manager.
I don't know what Android Device Manager is but I could do the reset in TWRP too. It's about not losing all of my data or a possibility to get that device unlocked without the code. It would be no problem as my fingerprint is stored. Damn, I could just hit my head against a wall or alternatively just cry like a baby. I never forgot a password or code in my whole life and by now it happens
bmwbasti said:
I don't know what Android Device Manager is but I could do the reset in TWRP too. It's about not losing all of my data or a possibility to get that device unlocked without the code. It would be no problem as my fingerprint is stored. Damn, I could just hit my head against a wall or alternatively just cry like a baby. I never forgot a password or code in my whole life and by now it happens
Click to expand...
Click to collapse
Log in here https://www.google.com/android/devicemanager
Using the account your phone is used with.
Thx, but there I only have the options of letting the phone ring, lock it down or wiping it. As stated above I could do that easily in recovery, too.
I'm looking for a way of not having to wipe the phone (if there is one....)
bmwbasti said:
Thx, but there I only have the options of letting the phone ring, lock it down or wiping it. As stated above I could do that easily in recovery, too.
I'm looking for a way of not having to wipe the phone (if there is one....)
Click to expand...
Click to collapse
To be honest, I don't think so. There were loopholes before, but they have been closed. :/
So doing a factory reset and restoring /data is the only way of getting back control of my phone again (without losing too much data)?
I think i will get rid of locking my phone with fingerprint again as there seems not ot be a failsafe mechanic for forgetting a (backup) mechanic
OK, so it seems that I have to throw that piece of aluminum against the wall. The code seems to interact with /data, because after restoring only /data I have to put in the forgotten password again.
bmwbasti said:
OK, so it seems that I have to throw that piece of aluminum against the wall. The code seems to interact with /data, because after restoring only /data I have to put in the forgotten password again.
Click to expand...
Click to collapse
I really suggest starting from zero, when you get everything set, then set a password.
Thanks for your advice, but it's not about starting from zero. I've already done this twice today
It's about at least being able to get (some of) the data of /data
Hello devs, seems like I am in trouble. I am using TWRP in Asus Zenfone 2 - A008D Model, Bootloader is Unlocked. So, after I flashed Cyanogen Mod 13 and GAPPS-x86-6.0-Micro, I rebooted the device. All apps got upgraded at first and when Cyanogen started showing the initial setup, device suddenly started locking and unlocking itself, repeatedly! It is not stopping at all. I had to force close it using power-button. This happens for all ROMs including stock ROM. Any solutions? Thanks.
Sample video : youtube.com/watch?v=VmvAJSVGmt0
P.S: Let me know how do I get logcat info at such situation. (I can barely click anything) :crying: Help needed.
Update: The issue is resolved in stock ROM by turning off the Asus Cover. May I know how do I resolve the same issue when I do initial boot using CyanogenMod 13 (i.e, while setup).
It looks like your phone thinks you're using the smart view cover.
I don't know whether this is the case, but on other phones the smart view cover is detected using magnets, so, do you have any strong magnetic source around that could interfere?
Anyway, I think your best option is trying to disable the ASUS smart cover app. If your phone is rooted and you can access it through adb while connected to a pc, you can disable apps using adb shell command. More info here:
http://android.stackexchange.com/questions/56620/enable-and-disable-system-apps-via-adb
The only thing you need to know is the package name for the app. According to its details page on Google Play, it's com.asus.flipcover2. Once disabled, reboot the phone and see if it works. You can also uninstall the app completely.
jman0 said:
It looks like your phone thinks you're using the smart view cover.
I don't know whether this is the case, but on other phones the smart view cover is detected using magnets, so, do you have any strong magnetic source around that could interfere?
Anyway, I think your best option is trying to disable the ASUS smart cover app. If your phone is rooted and you can access it through adb while connected to a pc, you can disable apps using adb shell command. More info here:
android.stackexchange.com/questions/56620/enable-and-disable-system-apps-via-adb
The only thing you need to know is the package name for the app. According to its details page on Google Play, it's com.asus.flipcover2. Once disabled, reboot the phone and see if it works. You can also uninstall the app completely.
Click to expand...
Click to collapse
Hey jman0, thanks a lot for the reply. The issue is resolved in stock ROM. Now, can you please tell me how to resolve the same issue in CyanogenMod 13. When I finish flashing, the initial setup is ruined because of the frequent locking and unlocking. Any solutions? Thanks.
kunalrohidasmhatre said:
Hey jman0, thanks a lot for the reply. The issue is resolved in stock ROM. Now, can you please tell me how to resolve the same issue in CyanogenMod 13. When I finish flashing, the initial setup is ruined because of the frequent locking and unlocking. Any solutions? Thanks.
Click to expand...
Click to collapse
I don't really know. I've never used CM13 with this phone. Sorry
jman0 said:
I don't really know. I've never used CM13 with this phone. Sorry
Click to expand...
Click to collapse
Oh, that is totally fine. Thanks anyways.
Hello forum,
I configurate the fingerprint to use in my OP3, and it works very fine, but still appear the option to unlock the phone (padlock) so passing a finger up just to unlock.
I want to configurate that don´t show that option for unlock, it´s possible?
Thanks in advance.
It will ask for lock code 1st time after reboot... That how the android security works nothing can do.
albertfs78 said:
Hello forum,
I configurate the fingerprint to use in my OP3, and it works very fine, but still appear the option to unlock the phone (padlock) so passing a finger up just to unlock.
I want to configurate that don´t show that option for unlock, it´s possible?
Thanks in advance.
Click to expand...
Click to collapse
If u are using marshmallow there is an xposed module for that. If not then u will only do that once after reboot.
But if u mean completely removing the pin then thats not possible.
If you have a smartwatch(any other bluetooth wearable) you can use smartlock to get rid of the pin
I´m using the last version: Android 7 (OxygemOS 4.0.3)
So when I push the right side button for show the scream, at first time appear the NOK image, then i put my finger in the padlock and change the icone for the OK image (check the circle green or red on the image).
I always want to appear the OK image only and forever, it´s possible??
see attach files....
NOK image:
OK image:
I use fingerprint+pattern.
It shows pattern on restart or on ocasion. Mostly just fingerprint. And it's a good fingerprint comparing with other phones.
Received today the official European Pie Update. And now it doesn't let me unlock the phone with finger prints or code. And can't shut it down, only restart. Help appreciated.
I do have the same problem - it's not possible to unlock the phone. I restarted the phone into "safe mode" (long-press power button on screen and select "safe mode") but the problem persists.
I can get phone calls and SMS and all, but i only get a black screen if i try to unlock. Only way to get into the GUI is by restarting the phone...
If someone knows what to do besides a factory reset, I would highly appreciate it!
Same in Sweden. Didn´t do backup so hard reset is last thing i whant to try. I have a symbol on the screen i have never seen before, looks like a torx screw .Does anybodu know what that symbol is?
This is just awkward...
I couldn't wait any longer and had to reset my device and now it works again. I was able to login after each reboot so I could make a backup. But it's cumbersome anyway.
This is so bad from LG - after launching a "Software Upgrade Center" and waiting months to get android pie, this was the first time I had problems with an update... Never again LG...
Had to do a hard reset too. Then it worked
I have this problem, too
I'll wait a little bit, maybe we can find another solution, I don't want to wipe my phone, I was to lazy to createa backup
Might be related to the issue I'm having. Google Play Services have stopped working after a failed Play Store update this morning. Phone won't unlock properly with fingerprint, and is scrolling slowly. I'm in the US on Verizon. Updated on Friday and had been working fine until that corrupted update. G710vm20a
Sent from my LM-G710VM using Tapatalk
Someone please give advice, or help me fix it because i can't reset it... i have too much irreplaceable stuff on it.
Ok, I haven't had a problem, but I did a clean install of the leaked kdz from a few days ago. I had a fresh Google backup and sdcard, so I didn't loose anything.
kiszidomi said:
Someone please give advice, or help me fix it because i can't reset it... i have too much irreplaceable stuff on it.
Click to expand...
Click to collapse
Hello. Have you found a solution to the problem? If so, please share how you did it without wiping the phone.
SwedenLGG7 said:
Hello. Have you found a solution to the problem? If so, please share how you did it without wiping the phone.
Click to expand...
Click to collapse
Hi, i couldn't find anything, I had to wipe it. Sorry to disappoint.