Hi guys,
i am trying to login to my pixel 5 (android 12 beta1), when i set the pin it goes back to the lockscreen.
If I try a wrong pin it says it is wrong.
I did a wipe data but booting the phone is again asking for the PIN. Digiting it it goes back to the previous screen (if I want to move data from preious phones).
I Can't use fastboot for flashing beacuse now i don't have enabled the USB debug.
Any advice?
Thanks
I managed to flash via ADB but i am facing still the same issue.
if i try to bypas the frp with the google account it goes back to the previous screen as weel.
have you tried booting to recovery and selecting factory reset from there?
Related
Hi all,
Hope someone is able to help, I have an Mi5 Pro and simply wanted to do a factory reset of the stock MiUi. My phone is global rom version completely stock.
I simply backed everything up, then went into settings --> about --> factory reset
After the phone seemed to do the reset it came back with a screen with the image of a phone and a cable asking to be plugged in.
So I installed the Mi PC software and the phone drivers, restarted the PC and plugged the phone in.
It recognises that it's been plugged in and the PC software starts to 'look for updates' then I get the error "Reading Device Information Failed"
I've tried to get into Fastboot but every time I do, the phone wont go past the Fastboot logo screen with the white creature repairing the android.
All I wanted was to do a stock factory reset.
Thanks in advance for any information.
Cheers,
Matt
The "screen with the image of a phone and a cable asking to be plugged in" comes when you try to boot into recovery. Because the bootloader is locked it won't allow to reboot in recovery and will show this screen.
I'll suggest, download the latest MIUI rom from en.miui.com and flash through fastboot.
I have a LG straight talk phone an after I factory reset it ask for a pin /password to decrypt
IMEI: 356810-06-202592-1
I'm a having a similar issue, when I try to factory reset my Mi5 vía Settings, it suddenly turns off and when I get it to turn on (because it's difficult, I don't know exactly how I did it) nothing was erased.
Here is my reply on another thread
https://forum.xda-developers.com/showpost.php?p=70473798&postcount=2
HI!
I was using fusion os 8.0 so when I reboot the phone yesterday it asked me for a pin...
I entered twrp and tried by deleting the .key archives and lockscreen.sha and the related files.
After that I tried again with my last password but didn't work. After entering several wrong passwords the phone did a factory reset and right now I have negative attempts on entering the pin... The phone boots to a black screen with a prompt asking for a number, a keyboard and an emergency call button.
I can enter to twrp and I have an old miui 9 backup
Hello. After rebranding my phone from PRA-AL00X to PRA-LX1 it's stuck on the Factory reset screen after it gets to 99%. I don't know what to do. I can't enter fastboot either. But I have a question: why when I plug it in, when the factory reset screen is there, my PC makes a sound effect as it's connected to my phone (you know, the usual sound when you plug something into your PC). Can it still be saved? Thank you.
Probably a system partition size complication. Are you using RecoveryOreoNoCheck?
Read this or this.
Something weird happened. So, last night I left my phone to run out of battery. Today, after booting it again it worked. But it rebooted itself after it got into Android, and now it's stuck again on the factory reset process at 99%.
EDIT: I think I managed to figure it out. So, after my phone runs out of battery it restarts normally, into Android. After that I need to let it charge for some time, because of the low battery it may shutdown. I will update soon if I figure it out completely.
EDIT 2: It seems that after I enter my pin to unlock my device it reboots itself. Why is that?
Is there any way I can enter erecovery mode without enabling developer options and usb debugging? Because once I input my pin, my device restarts.
EDIT: Seems like I managed to enter my pin without my device restarting. I think it was restarting because the battery was low.
I have another question. Why after I manage to boot my phone, when I try to reboot to bootloader, it reboots, and enters again the Factory reset screen?
PoweredLights said:
I have another question. Why after I manage to boot my phone, when I try to reboot to bootloader, it reboots, and enters again the Factory reset screen?
Click to expand...
Click to collapse
Like I said in my previous post
Probably a system partition size complication. Are you using RecoveryOreoNoCheck?
Read this or this.
Click to expand...
Click to collapse
So as stated from the user on that link who solved the problem, try formatting the system partition then try to install the update again.
Regarding your other posts, if the update installation obviously failed or encountered some issues then by some coincidence it boots back, that doesn't mean it got fixed. The problem is still there and will become even a bigger problem, if it's not fixed.
You don't have to enable Developer Options or USB Debugging, to boot into eRecovery.
CrimsonBloodfang said:
Like I said in my previous post
So as stated from the user on that link who solved the problem, try formatting the system partition then try to install the update again.
Regarding your other posts, if the update installation obviously failed or encountered some issues then by some coincidence it boots back, that doesn't mean it got fixed. The problem is still there and will become even a bigger problem, if it's not fixed.
You don't have to enable Developer Options or USB Debugging, to boot into eRecovery.
Click to expand...
Click to collapse
The problem is, I can't enter bootloader nor erecovery. I'll try to factory reset with the phone booted up.
EDIT: After factory resetting from settings, when the phone was booted up, it works now. I tried to reboot it and it reboots fine, without the factory reset screen appearing. And thank you very much for your help. I will now try to install Oreo for PRA-LX1.
The only problem I have now, is: my system version is now named NRD90M test-keys.
EDIT: I fixed my phone. I reinstalled through eRecovery the newest available EMUI version and NRD90M test-keys dissapeared. Now it works fine, even if I am on Nougat. I am waiting for the EMUI 8 update, this time not forcing my phone to install it.
PoweredLights said:
The problem is, I can't enter bootloader nor erecovery. I'll try to factory reset with the phone booted up.
EDIT: After factory resetting from settings, when the phone was booted up, it works now. I tried to reboot it and it reboots fine, without the factory reset screen appearing. And thank you very much for your help. I will now try to install Oreo for PRA-LX1.
The only problem I have now, is: my system version is now named NRD90M test-keys.
EDIT: I fixed my phone. I reinstalled through eRecovery the newest available EMUI version and NRD90M test-keys dissapeared. Now it works fine, even if I am on Nougat. I am waiting for the EMUI 8 update, this time not forcing my phone to install it.
Click to expand...
Click to collapse
Hi,
I have the same issue with Phone Always going to factory reset.
Only draining it makes it boot up normally.
I also did the factory reset from within android. Now it does a factory reset lowlevel and again it hangs on 99%.
Did you also have this?
I tried installing a couple of custom ROMs in my Mi Max 2. When setting one of these ROMs, I set PIN lock to its screen.
After that, my TWRP is PIN locked as well. I must enter PIN to unlock my TWRP and to access it.
So the question is: How to unset TWRP lock? Is there in TWRP itself a command/option to unset TWRP lock?
(TWRP is official 3.2.3.0, ROM I using is EU Nougat.)
zost said:
I tried installing a couple of custom ROMs in my Mi Max 2. When setting one of these ROMs, I set PIN lock to its screen.
After that, my TWRP is PIN locked as well. I must enter PIN to unlock my TWRP and to access it.
So the question is: How to unset TWRP lock? Is there in TWRP itself a command/option to unset TWRP lock?
(TWRP is official 3.2.3.0, ROM I using is EU Nougat.)
Click to expand...
Click to collapse
maybe u can try and flash twrp again, see if it resets and removes that PIN. also try other twrp versions to see if that helps.
you set encryption > then the lock is the pin to encryption and that has nothing to do with twrp .. it just trying to decrypt storage to work on it
try using that pin
if it didn't work you can always factory reset from twrp and it will recognize the storage.. provided that nothing valuable on the storage
also if you can boot to the system i had a pretty bizzare bug the can be useful for you
i installed reachability cursor app on xtended rom and force closing the app makes it lose the accessibility permission
after enabling it for the second time freezes the device and then if you force restart with power long press it stops asking for the code in twrp and while booting..
maybe specific to the rom but worth a shot if that's your case
jbmc83 said:
maybe u can try and flash twrp again, see if it resets and removes that PIN. also try other twrp versions to see if that helps.
Click to expand...
Click to collapse
I tried flashing same TWRP again as well as almost dozen of other TWRP versions for Oxygen. Nothing changed, I still must enter PIN password when entering TWRP and the same password when booting into system (from TWRP or from phone turned off).
kalawy said:
you set encryption > then the lock is the pin to encryption and that has nothing to do with twrp .. it just trying to decrypt storage to work on it
try using that pin
if it didn't work you can always factory reset from twrp and it will recognize the storage.. provided that nothing valuable on the storage
also if you can boot to the system i had a pretty bizzare bug the can be useful for you
i installed reachability cursor app on xtended rom and force closing the app makes it lose the accessibility permission
after enabling it for the second time freezes the device and then if you force restart with power long press it stops asking for the code in twrp and while booting..
maybe specific to the rom but worth a shot if that's your case
Click to expand...
Click to collapse
I must enter same PIN password when booting into TWRP and when booting into system (from a) TWRP, or b) from phone turned off, or c) after resetting the phone when in system).
It is needless to say that phone screen is not locked in any way - by PIN/phrase password or by fingerprint. That leads me to conclusion that something should be (re)set/changed in TWRP itself.
Factory reset in TWRP didnot help. I will try to repeat the trick with xtended ROM and reachability cursor app.
you need perform format data
zost said:
I must enter same PIN password when booting into TWRP and when booting into system (from a) TWRP, or b) from phone turned off, or c) after resetting the phone when in system).
It is needless to say that phone screen is not locked in any way - by PIN/phrase password or by fingerprint. That leads me to conclusion that something should be (re)set/changed in TWRP itself.
Factory reset in TWRP didnot help. I will try to repeat the trick with xtended ROM and reachability cursor app.
Click to expand...
Click to collapse
i wonder what will happen if you set a new pin in the current rom you running and made it ask for it at boot
then removed it?!
Or you may try this https://forum.xda-developers.com/doogee-mix/how-to/fixed-how-to-remove-data-encryption-twrp-t3757595
rino64a said:
you need perform format data
Click to expand...
Click to collapse
Thank you. I will try that tomorrow.
kalawy said:
i wonder what will happen if you set a new pin in the current rom you running and made it ask for it at boot
then removed it?!
Click to expand...
Click to collapse
"...and made it ask for it at boot" - I already tried that. EU ROM has the option to PIN lock the screen, but it hasnot the option to ask a PIN at boot. So with EU ROM, at boot it will ask for same PIN as for the TWRP an after a boot it will ask for screen PIN as set in EU ROM.
zost said:
"...and made it ask for it at boot" - I already tried that. EU ROM has the option to PIN lock the screen, but it hasnot the option to ask a PIN at boot. So with EU ROM, at boot it will ask for same PIN as for the TWRP an after a boot it will ask for screen PIN as set in EU ROM.
Click to expand...
Click to collapse
as far as i can remember it was present in mi-globe and mi globe is the same as EU
it's there .. maybe in another place
Please post a screenshot or just shoot your screen.
P.S. You should ask in
"Xiaomi Mi Max 2 Questions & Answers"
or
"Xiaomi Mi Max 2 Guides, News, & Discussion" .
My Pixel 4XL no longer boots to home screen...it will reboot fine but gets stuck on PIXEL IS STARTING.
I've tried safe mode and recovery modes but not 100% sure what to do.
I want to avoid factory reset as I want to get some physical media off of the phone first. I tried connecting to a PC and selected USB File Transfer but it never would mount the drive.
Can I get my media off of this without a factory reset or can a recovery/safe mode option work?
If you don't do any mod to your phone, I think press power button longer and force phone reboot. Your problem can be fixed !
garak0410 said:
My Pixel 4XL no longer boots to home screen...it will reboot fine but gets stuck on PIXEL IS STARTING.
I've tried safe mode and recovery modes but not 100% sure what to do.
I want to avoid factory reset as I want to get some physical media off of the phone first. I tried connecting to a PC and selected USB File Transfer but it never would mount the drive.
Can I get my media off of this without a factory reset or can a recovery/safe mode option work?
Click to expand...
Click to collapse
If you are rooted try this...(assuming you installed some Magisk modules)
Once phone reboots and you are on PIXEL IS STARTING screen see if you can access settings via drop-down. If you can, go to Settings -> Apps -> Magisk. Once there you should have the option to open magisk. Once you open magisk go to the modules section and disable all the modules then reboot.
Try flash boot image magisk A core only
---------- Post added at 11:12 AM ---------- Previous post was at 11:11 AM ----------
Also try to flash sysytem, you have to make some change on Run all bat file. It will flash other partitions other than data
Once you've tried the us easier stuff as mentioned above or possibly following this post you can get it back by flashing the full image with the wipe removed. Your phone will come up like nothing happened other than if you were rooted it will be gone and you'll have to root again. There several guides you can reference if you're not familiar with the procedures.
krabman said:
Once you've tried the us easier stuff as mentioned above or possibly following this post you can get it back by flashing the full image with the wipe removed. Your phone will come up like nothing happened other than if you were rooted it will be gone and you'll have to root again. There several guides you can reference if you're not familiar with the procedures.
Click to expand...
Click to collapse
Agreed. Download the latest full image, modify the "flash-all.bat" file to remove the "-w" Then Boot the phone to fastboot and run the modified batch flash-all file, you should be good.
garak0410 said:
My Pixel 4XL no longer boots to home screen...it will reboot fine but gets stuck on PIXEL IS STARTING.
I've tried safe mode and recovery modes but not 100% sure what to do.
I want to avoid factory reset as I want to get some physical media off of the phone first. I tried connecting to a PC and selected USB File Transfer but it never would mount the drive.
Can I get my media off of this without a factory reset or can a recovery/safe mode option work?
Click to expand...
Click to collapse
Is you bootloader unlocked? If so, you can flash the factory image and remove the "-w" command as suggested above, but if your bootloader is not unlocked this will not be an option. If you are on a locked bootloader, you can sideload an OTA image (which really is a full factory image). This will not wipe your phone or do a factory reset. It will however replace your OS with a clean version. Hopefully that fixes the issue. If not, then you will have to do a factory reset in order to "clean out" the problem.