Hey,
I was running Android P Beta, and had an OTA update today.
As it's been said on the beta topic, it apparently put me back on Oreo (the pattern lock is different on P).
But now I can't unlock the phone with the pattern at boot. When I put it the right pattern, it gives me a black screen, and ask me to unlock again.
So nothing's coming up, no wifi, no backup etc.
Does anyone have an idea on how to solve this **** ?
Thanks guys.
Deeptwix said:
Hey,
I was running Android P Beta, and had an OTA update today.
As it's been said on the beta topic, it apparently put me back on Oreo (the pattern lock is different on P).
But now I can't unlock the phone with the pattern at boot. When I put it the right pattern, it gives me a black screen, and ask me to unlock again.
So nothing's coming up, no wifi, no backup etc.
Does anyone have an idea on how to solve this **** ?
Thanks guys.
Click to expand...
Click to collapse
Boot to Recovery mode. Wipe/factory reset and reboot system.
koschey_immortal said:
Boot to Recovery mode. Wipe/factory reset and reboot system.
Click to expand...
Click to collapse
Thanks for your answer.
I know I could do that, but I'd like to be able to get some data back first (like whatsapp messages).
Whichi is why I'm trying to find a workaround, but so far it's not really a success.
have you tried android unlock my phone method?
Go to google and sign in. Then go to find/locate my device and then check the option unlock my phone. It will help surely.
Styleshman said:
have you tried android unlock my phone method?
Go to google and sign in. Then go to find/locate my device and then check the option unlock my phone. It will help surely.
Click to expand...
Click to collapse
i think that OTA update on Android P is in real "Android 0 8.1 June Update", as mentioned here, if this true that's the reason why you have problems
Related
I get asked a lot how I rooted my Huawei Honor Note 8 so I thought I'd do a basic how to from memory on how I did it. It's relatively easy to do.
You'll need your phone's bootloader unlocked.
The files from Huawei's forums http://club.huawei.com/thread-10828573-1-1.html or https://drive.google.com/file/d/0BwyaxIga7s0qc0ZKRGtsdndwV3M/view?usp=sharing
The app is in chinese but has some english on the buttons.
To unlock bootloader:
Got bootloader unlock code with the app on the playstore "DC Huawei Bootloader Codes" (took about 8 hours to get)
Enable USB debugging on the phone & connect it to the computer.
Unlock the bootloader with the program downloaded. Use the first button on the first tab labeled bootloader. Put in unlock code in the pop up box & click ok.
To root:
Enable USB debugging on the phone & connect it to the computer.
Flash the recovery_twrp.img file with the program downloaded. Use the 2nd button on the first tab labeled recovery.
To change twrp into english, click on the 3rd down 2nd row button & then click on the globe button. The globe is really hard to hit! Keep trying till you get it Then select English.
Install SuperSU with TWRP
Should now be rooted!
Question. Is there anything I should do like backup my bootloader or something before starting this process?
benmeroff said:
Unlocking your bootloader will wipe the device; factory reset for sure, and I believe it also erases your internal storage (don't quote me on that though, not sure for this phone), but your OS will remain whatever stock version you had installed until you flash something else.
Click to expand...
Click to collapse
I did not backup anything.
Ok thanks.. I appreciate it
I have a question, or making a root and unlock the bootloader is associated with a full reset your data and settings that can be done root without losing data?
Nope
Sent from my EDI-AL10 using Tapatalk
Hi guys
I unlocked my note 8 successfully . In startup screen show your devives is unlocked and can not be trusted every time i restar the phone is it normal?
Second thing i flashed twrp by clicking on recovery button then after restarted i clicked on 3rd button of second row to change to english but it didnt say click on english
How to enter twrp recovey i tried pressing power button and volume up nothing happened
Plz help
Yuppers.. not trusted cuz ya unlocked it.
Should be volume up & power. You can also do it with the app. The 2nd tab... recovery. Will boot it into recovery too.
You have to click the globe button on the far right to get to the language. It's a ***** to hit! BTW... TWRP has reverted back to chinese a few time now for some reason on mine. It's kind of annoying considering how hard it is to hit that one button.
Questions about the root process
1) why do you need the unlock code?
2) Where can I find SuperSU for honor note 8? Can someone please provide a link?
3) Has anyone succeeded rooting?
Thanks in advance for the answers.
Please Help!
Everything was find, I unlocked the bootloader, installed TWRP, when I flashed SuperSU it bootloops!
Can someone please help.....
I'm not sure why it would be boot looping. I'd flash it again. Might even try a factory reset before flashing too. You're the first I've heard of with that problem. Make sure you're on version 22.
Sent from my EDI-AL10 using Tapatalk
problem solved
riffy504 said:
I'm not sure why it would be boot looping. I'd flash it again. Might even try a factory reset before flashing too. You're the first I've heard of with that problem. Make sure you're on version 22.
Sent from my EDI-AL10 using Tapatalk
Click to expand...
Click to collapse
The problem solved. I downloaded the latest version of SuperSU (2.78) , flashed it again with TWRP and everything loaded find.
I have a rooted device too.
Thanks for your answers!:good::fingers-crossed:
Glad to hear it worked out!
i downloaded "DC Huawei Bootloader Codes" then i entered my Note 8 IMEI and waited for 8 hrs and got an email telling me it is failed and i tries the other IMEI "since it's dual sim card phone" but no luck, same message.
Please help
The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days. Huawei site error
DC Huawei Bootloader Codes not working
please help
Hi,
I read of the possibility of the root of honor note 8 through oneclickroot, kingroot, etc.
It must first be unlocked bootloader or the software will to unlock?
For unlocking the bootloader you must use to force pay program dc-unlocker?
Thank you
DC Huawei Bootloader Code get but not unlock
Bootloader unlock codes
Hello guys... I have two Honor Note 8 phones and i wanna unlock them..
Official method - how to get Bootloader unlock codes does not work, so i downloaded dc-unlocker APP on google play..
Added there EMEIs, paid and was waiting almost 20 hours to get mails - operation failed..
I really dont know about any other way how to get these codes..
Can anyone help me please?
Thanks!
2Duky said:
Hello guys... I have two Honor Note 8 phones and i wanna unlock them..
Official method - how to get Bootloader unlock codes does not work, so i downloaded dc-unlocker APP on google play..
Added there EMEIs, paid and was waiting almost 20 hours to get mails - operation failed..
I really dont know about any other way how to get these codes..
Can anyone help me please?
Thanks!
Click to expand...
Click to collapse
in the app, there is another way to get it. choose not by imei.
write the developer of the app you did not get the code and you want a refund, and pay for the second method. this is how i did it.
arielisrl said:
in the app, there is another way to get it. choose not by imei.
write the developer of the app you did not get the code and you want a refund, and pay for the second method. this is how i did it.
Click to expand...
Click to collapse
Great! Many thanks for your quick reply! I contacted dc-unlocker support and thats what they replied..
Hello, this codes is from factory DB. Sorry, but there not all phones present in this db.
This happens frequently if phone has MEID .
But you can read code by cable, we support almost all huawei.
If reading by cable not acceptable we can do refund.
Im waiting for their next answers at my qustions, what exactly have i do..
I have to download their soft probably and make everything there..
I had no time to check their forum yet, im sure there will be instructions..
EDIT:
Oki so i used DC-unlocker software, received these codes and unlocked Bootloader successfully!
I have rooted both phones already!
I had an issues with ADB drivers on Win10 and on Win7 as well, could not find my devices in devices manager but i have solved it!
TWRP 3.02 with preinstalled SuperSU works fine on B027.. In one of my phones i had B029 so i had to downgrade to B027..
On B029 doesnt work flash command in cmd.. Stuck on "waiting for device"..
So I messed up with trying to get my phone to global rom without unlocking the bootloader.
A little backstory: I have an 1062 which had an android 8.1, I didn't have my bootloader unlocked.
So I've tried to make my phone Global by using this method https://forum.xda-developers.com/no...-to-convert-nokia-7-china-variant-to-t3769541 . I think it was done successfully and my phone instatly asked me to update to the newer android, so I did it. It was a 1.4 gb update and after it was done I was welcomed by a default android settings screen which asked me to log in to my google account. So I tried and found out that my touch doesn't work at all. I can see the animation that says Welcome and I my phone reacts to Volume up\down and power buttons, but no reaction to my fingers whatsoever. I've tried wiping in the recovery mode, it didn't help.
I can't even find out my imei or get my Rom version.
Is there anything that can help? I'm obviously willing to get my bootloader unlocked if I can get my Imei and rom vers.
Hi ,
i just flashed the factory image for android 11 with full wipe ( was on last beta ).
My phone refuses to complete the face unlock configuration. Telling me that it can't add new face data and that i should remove one before retrying...
i'm rooted and i already tryed a magisk module supposed to fix face unlock but no luck
help please ? ^^
baleskoil said:
Hi ,
i just flashed the factory image for android 11 with full wipe ( was on last beta ).
My phone refuses to complete the face unlock configuration. Telling me that it can't add new face data and that i should remove one before retrying...
i'm rooted and i already tryed a magisk module supposed to fix face unlock but no luck
help please ? ^^
Click to expand...
Click to collapse
Did you find a solution?
Nope
I found someone with the same problem here :
https://support.google.com/pixelphone/thread/24855830?hl=en
Any Idea how i Can try to reproduce the same effect without having to lock/unlock my bootloader ?
baleskoil said:
I found someone with the same problem here :
https://support.google.com/pixelphone/thread/24855830?hl=en
Any Idea how i Can try to reproduce the same effect without having to lock/unlock my bootloader ?
Click to expand...
Click to collapse
As of right now me and you are the only two that seem to have this issue.when I get home from work I'm going to go ahead and I'm actually going to relock my bootloader and and do everything and then I'm going to unlock it and see what happens.I can let you know in this thread if it works for me and that way you don't have to waste your time unlocking and relocking
Yes please
i would say lock and unlock again and just install everything again
baleskoil said:
Yes please
Click to expand...
Click to collapse
So i locked the bootloader ,then unlocked it and did a fresh install of 11 and i have face unlock back
Good .
I need to reflash the Factory image before relocking right ?
To be safe
baleskoil said:
Good .
I need to reflash the Factory image before relocking right ?
To be safe
Click to expand...
Click to collapse
I locked the bootloader then rebooted back into the boot loader and unlocked it and then flashed
Works for me too.
In past issues with face unlock, the fix was to perform a factory reset (Settings - System - Reset options - Erase all data) before flashing a new rom. Supposedly the chip that face data is stored is not cleared until you do a factory reset. Unsure if a full wipe clears the chip. You can try this next time ... may be easier than doing a bootloader lock/unlock.
neo_lithic3K said:
In past issues with face unlock, the fix was to perform a factory reset (Settings - System - Reset options - Erase all data) before flashing a new rom. Supposedly the chip that face data is stored is not cleared until you do a factory reset. Unsure if a full wipe clears the chip. You can try this next time ... may be easier than doing a bootloader lock/unlock.
Click to expand...
Click to collapse
I tried that and it's a no go. Looks like bootloader is the way for now.
fezzy102 said:
I tried that and it's a no go. Looks like bootloader is the way for now.
Click to expand...
Click to collapse
Hi, My face unlock is also messed up after updating to Android 11 (it keeps saying “fit face into frame” without letting me register my ugly face...)
Did you encounter the problem after rooting? I’m trying to figure out how to solve this, as I had no success with factory reset or flashing OTAs and factory images
seipersei said:
Hi, My face unlock is also messed up after updating to Android 11 (it keeps saying “fit face into frame” without letting me register my ugly face...)
Did you encounter the problem after rooting? I’m trying to figure out how to solve this, as I had no success with factory reset or flashing OTAs and factory images
Click to expand...
Click to collapse
I had the exact same problem as you. face unlock became unreliable after the Android 11 upgrade, so I deleted face data and tried to set up again. It keeps saying 'fit face into frame' no matter the angle or the lighting. Did a factory reset and no improvement. I have never rooted or unlocked the bootloader on this phone. I informed google support and they are sending me a replacement.
Just to share an experience with the community: After android 11 update I was having glitches with face unlock. (Totally stock, no root & all latest ota) This got worse until it wouldn't work at all. Deleting face & starting over didn't work as it just refused to even acknowledge trying to register anything. Then the auto brightness starting flicking up and down and finally half the screen disappeared under green flickering. A factory hard reset made no difference. I even did it twice but the welcome screen on rebooting was still covered in green flickering. Searching for a new phone reluctantly. I picked up my pixel 4xl again to see if I could think of a way of selling it for any purpose & it was fine! Set up & reinstalled a backup & everything including face unlock works perfectly like new. What was all that about!?
Can you describe full algorithm for noob, please?
Stiil don`t working
fezzy102 said:
I tried that and it's a no go. Looks like bootloader is the way for now.
Click to expand...
Click to collapse
I've done relocking bootloader, but it didn`t help, face unlock still not working, OC is stock, latest.
I dunno what's the situation of you guys
But let me share my experience
I was having lock screen lags in Android 11
So I flashed the previous Android 10 image
It broke the face unlock and still broken even after flashing the full Android 11 image with wipe
What I did was flashing back to Android 10 again
Then update to Android 11 through OTA
This also was the method in r beta to fix face unlock issues
kingkong0821 said:
I dunno what's the situation of you guys
But let me share my experience
I was having lock screen lags in Android 11
So I flashed the previous Android 10 image
It broke the face unlock and still broken even after flashing the full Android 11 image with wipe
What I did was flashing back to Android 10 again
Then update to Android 11 through OTA
This also was the method in r beta to fix face unlock issues
Click to expand...
Click to collapse
This is a known problem, and so far Google has not fixed it. Unsure if they ever will.
Sent from my Pixel 4 XL using Tapatalk
I don't have my username or password for my US997 G6 and I tried loading the .kdz ROM from the factory using LGUP and the phone in Download Mode. That didn't really start from a clean slate since the problem still happens.
After boot it it wants to connect to wifi in the new phone setup and then get me to login to google. I can't login. The phone has an unlocked bootloader, I get scary danger text when initially powering it on but I can only do download mode I think?
How could I lay a ROM on it that wipes the FRP account w/out booting to fastboot? Is there a hack I could do? I'd hate to toss the phone, it still is a great device.
Do you have android 7.0? Or newer?
If you have nougat than you can unlock it in 5-15 seconds making initial configuration screen crash and ending up on home screen.
WojtekCC said:
Do you have android 7.0? Or newer?
If you have nougat than you can unlock it in 5-15 seconds making initial configuration screen crash and ending up on home screen.
Click to expand...
Click to collapse
It is Android 8. Are there any tips to make the initial configuration screen crash for that version?
powershift said:
It is Android 8. Are there any tips to make the initial configuration screen crash for that version?
Click to expand...
Click to collapse
I dont know, it was working on android 7.
Try this
https://www(dot)youtube(dot)com/watch?v=sGXc1sQkG2s
There is only one way to find out.
If didn't, try searching in youtube "lg g6 frp" or something like that.
WojtekCC said:
I dont know, it was working on android 7.
***Mod edit: link removed***
Click to expand...
Click to collapse
I did have Android 7. I followed that tutorial but when the screen was bypassed, the phone did an automatic wipe and did a factory reset and put the phone back to a brick state.
Motivated by that video, I retried the steps but this time after connecting to WIFI and before doing the bypass, I disabled the internet on the WIFI hotspot but kept the WIFI connection UP. Then followed the steps so Android couldn't connect to the internet and it let me in. Thank you!!
Factory Reset Protection is generally an anti-theft measure; the best way around it is to reset your Google password.
Otherwise, a method for FRP unlock is available on the XDA Portal.
@powershift if this is a device you recently purchased, I'd suggest contacting the seller. If it actually is your device, try resetting your Google account password using a PC.
If you still need it done I can let you know what I did, and share the files. Spent about 14 hours finally figuring out a method around the FRP. It will depend what version it's on though
TBurn420 said:
If you still need it done I can let you know what I did, and share the files. Spent about 14 hours finally figuring out a method around the FRP. It will depend what version it's on though
Click to expand...
Click to collapse
Hey can you dm me I got a second hand lgv20 but the steps shouldn't be so different, it's a ls997 and it's on 7.0 zv5
So.... I removed my Pixel 5 form the beta 13 program, selected update on the devices and had it download Android 12 a few weeks back. On reboot I get the "device is corrupt" error with visit the g.co/ABH link. If I hit the power button that error loops, and trying a hard / factory reset does nothing.
I tried several of the steps but since I cannot get into Dev mode to unlock the bootloader I'm kind of stuck.
The most I have been able to do is with the rescue tool, but that throws a "software on device is newer then this tool" error and wont go forward.
Any suggestions? Should I just send in to a repair shop? Or move on?
I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA
xunholyx said:
I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA
Click to expand...
Click to collapse
Tried both types of cables, no luck...
grmacd said:
Tried both types of cables, no luck...
Click to expand...
Click to collapse
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.
V0latyle said:
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.
Click to expand...
Click to collapse
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
Unfortunate and I feel for you.
It's generally advisable to always unlock the bootloader when running any kind of beta software, just because of this eventuality - if something goes wrong, you need to have a way to recover the device.
grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
You should be able to boot to recovery from the bootloader
I can boot to recovery, but the software wont sideload since the boot locker is locked.
My one hope is the fact Rescue mode on the web is throwing "software on the device older then this tool" so I am hoping once that gets a newer version I will be ok. So into the drawer it goes...
But you don't need an unlocked bootloader to sideload an OTA....
xunholyx said:
But you don't need an unlocked bootloader to sideload an OTA....
Click to expand...
Click to collapse
Ok... perhaps I will give it another try tomorrow.
grmacd said:
Ok... perhaps I will give it another try tomorrow.
Click to expand...
Click to collapse
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now
xunholyx said:
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now
Click to expand...
Click to collapse
So this AM I downloaded the newest ZIP file and followed the step on the site - after about 10 minutes presto the phone is back up and running with Android 13! Thanks for your help!