Cannot boot to os anymore after trying to unluck over patterns - Xiaomi Poco F1 Questions & Answers

Hi my dad tryed to unluck over fingerprint, becaus it doesnt work he unlocked over patterns, after that he got a black screen.
On boot instantly the recovery pops up with the options "reboot", "wipe data", "connect with mi assistant".
What i tried:
-rebooting
-hard shut down (10sec power button)
-wasnt able to connect with Mi Pc Suite inside "connect with mi assistant" neither on fastboot (there i got the message "connect in normal mode")
What we can do to revover the os withouth wiping the data ?

There's no way other than factory reset, which you can do from recovery.
If you fingerprint doesn't work then it's probably defective. If under warranty, inform Xiaomi.

Windoors said:
There's no way other than factory reset, which you can do from recovery.
If you fingerprint doesn't work then it's probably defective. If under warranty, inform Xiaomi.
Click to expand...
Click to collapse
Is there atleast a way to save data on it ?
Edit:
Well i "wiped all data" now. I dont see any chance to restore anything withouth a custom recovery or connection to pc.

Danny94 said:
Is there atleast a way to save data on it ?
Edit:
Well i "wiped all data" now. I dont see any chance to restore anything withouth a custom recovery or connection to pc.
Click to expand...
Click to collapse
Well, if you couldn't boot into/go past lockscreen then you can just factory reset from stock recovery. No need for custom ROM/recovery for that. Stock one allows for factory reset.

Related

[Q] Stuck in boot loop, exhausted almost all optons

LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
whitechameleon said:
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
Click to expand...
Click to collapse
i have now tried to flash the firmware while in download mode using a less than legitimately obtained lg R&D tool. however, i need V10F_00.kdz and i am facing a bit of censorship. any kind soul willing to host this file on dropbox or similar so i can download it?
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
J2270A said:
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
Click to expand...
Click to collapse
believe me i have. the only combo i can get to is download mode. there is a combo for a hard reset, but my touch buttons arent active during boot.

[Request] Tips to save a phone that restarts itself

Hi all, my question prescinds from a phone particular model. The problem is that for some sort of software issue, the phone restarts itself after few seconds that rom unlock appear. I'm sure that is a sw issue because in recovery mode it stays alive and when he does the application update after a dalvik cache wipe, all goes well too!
It's not possible to enable usb debug because it restarts too soon and in recovery (cwm) it's not possible to connect via adb. It's not a rooted phone. Also in safe mode it stucks in bootloop
What i can do before a factory reset?
phantastic_ said:
Hi all, my question prescinds from a phone particular model. The problem is that for some sort of software issue, the phone restarts itself after few seconds that rom unlock appear. I'm sure that is a sw issue because in recovery mode it stays alive and when he does the application update after a dalvik cache wipe, all goes well too!
It's not possible to enable usb debug because it restarts too soon and in recovery (cwm) it's not possible to connect via adb. It's not a rooted phone. Also in safe mode it stucks in bootloop
What i can do before a factory reset?
Click to expand...
Click to collapse
Looks like its bootlooping ... Yes its a software issue ... I don't think u have any option other than factory reset ... Take a backup first before u do that...or perhaps u can use a logcat if u know what it is
i will try to take backup in sd card and retrieve some useful data from this.
how can i use logcat if can't connect through adb?

[Q] Oppo Neo 5 Softbricked

Hi guys, I really need your help.
I'm new at this rooting stuffs and I tried to root my Oppo Neo 5.
I tried so many softwares like OneClickRoot, FramaRoot, and Kingroot but none seemed to work.
So I resorted to an app called oppo tools
It worked at first but I got really annoyed when my status bar suddenly colored to red when my phone discharges to 15% so I unrooted my phone and rooted back again. I really thought that was going to fix my problem but that's where the bootloop issue started.
I tried to flash some custom recovery zip but it failed since I only have a stock recovery.
But the thing is, I found a guide that says to rename the clockworkrecovery img to PG86IMG.zip.
So I did tried that and as soon as I flashed the zip from my stock recovery, my phone hanged.
I long-pressed the power button to restart and boot into recovery mode but nothing seems to happen.
I'll try to explain a bit more on how it looks when I boot my device.
When it boots normally (I mean not pressing the volume to enter recovery mode) it will only show the logo but when I try to go into recovery mode it will show the logo with a little text on the lower left portion "Recovery Mode"
Before I flashed the PG86IMG.zip, recovery mode was still working and the charging screen when off is working too.
but after I flashed the zip, every time I try to recovery mode the logo shows up with the little text but RECOVERY MODE isn't working. When I charge my phone it automatically boots up and shows the logo and text like it's trying to go recovery mode (I'm just trying to charge? It's going to recovery mode)
I tried using "adb devices" on cmd but it's not detecting any devices.
I'm really out of ideas guys, I know not all people use this model but what would be your suggestion?
A suggestion on how to fix this would really be appreciated :good:
I'm sorry I'm really new at this, please correct me if I did something wrong starting this thread. :angel:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Salman Al-Badgail said:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Click to expand...
Click to collapse
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
DeepBricked said:
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
Click to expand...
Click to collapse
You made a soft brick, not to worry flash it with correct stock firmware, if the phone is in warranty than ask them to do flash, this will take approx 10-30min. If it isn't in warranty than you should try it own or else pay some amount and the rest they will do.
Salman.
how about bootloop, cant enter recovery, reboot continiously when turn on even going to recovery, only fastboot isnt rebooting automaticaly but pc days drivers not succesfuly installed, and when off it qont detect by pc because of rebooting auto,
where can i find a rom for my oppo neo 5
pls help me pls

Serious Factory Reset issues

So my phone is in a terrible state, app permissions dot work properly in google apps, settigns backup recovery . factory reset does not work.
I cannot get my win 10 machine to connect have followed all tutorials, under device managerit shows up being as portable device. (Erro Code 19).
I tried Simple factory reset and it just restarts,
My wifi will not switch on.
Can someone please tell me the simplist way to do a full factory reset on this device, i can access the internet using my cellular network.
Many thanks
Millay
Can you use Flash Tool? I mean my computer does not recognise my P9000 but when I turn the device off, prepare Flash Tool, connect the USB cable and turn the device on it works.
I think that should be the most easy way to perform factory reset/flash the stock ROM.
Millay said:
So my phone is in a terrible state, app permissions dot work properly in google apps, settigns backup recovery . factory reset does not work.
I cannot get my win 10 machine to connect have followed all tutorials, under device managerit shows up being as portable device. (Erro Code 19).
I tried Simple factory reset and it just restarts,
My wifi will not switch on.
Can someone please tell me the simplist way to do a full factory reset on this device, i can access the internet using my cellular network.
Many thanks
Millay
Click to expand...
Click to collapse
I dont have the device yet but im thinking you could factory reset going to fastboot and doing fastboot erase userdata, no recovery mode needed and should most certainly work

Stuck in bootloop, potential soft/hard brick

Hello XDA.
After whipping my Moto E out the other day, I noticed that turning it on results in it just... laying there and showing me the "WARNING - BOOTLOADER UNLOCKED" message.
Around 1 1/2 years ago, it just turned itself on after clicking the power button once. Now, not even Fastboot mode helps, as choosing any of the options listed there results in the warning mentioned above. For clarification, here is everything in short:
The phone does NOT turn on normally
Using any option in the Fastboot boot menu restarts the loop (i. e. instantly goes back to warning message)
NEITHER does Minimal ADB and Fastboot recognize the device, NOR does the phone recognize the connection to any PC (I've tried 4 different PCs)
Since Fastboot is unresponsive, suggestions to restore stock recovery are useless to me
Suggestions to perform a factory reset are also useless, since Fastboot is unresponsive.
So, am I right if I suppose that this is a hard brick? Or is this somehow salvageable? If so, please help me...
Thanks in advance!
DeBedenHasen said:
Hello XDA.
After whipping my Moto E out the other day, I noticed that turning it on results in it just... laying there and showing me the "WARNING - BOOTLOADER UNLOCKED" message.
Around 1 1/2 years ago, it just turned itself on after clicking the power button once. Now, not even Fastboot mode helps, as choosing any of the options listed there results in the warning mentioned above. For clarification, here is everything in short:
The phone does NOT turn on normally
Using any option in the Fastboot boot menu restarts the loop (i. e. instantly goes back to warning message)
NEITHER does Minimal ADB and Fastboot recognize the device, NOR does the phone recognize the connection to any PC (I've tried 4 different PCs)
Since Fastboot is unresponsive, suggestions to restore stock recovery are useless to me
Suggestions to perform a factory reset are also useless, since Fastboot is unresponsive.
So, am I right if I suppose that this is a hard brick? Or is this somehow salvageable? If so, please help me...
Thanks in advance!
Click to expand...
Click to collapse
If its stuck on boot, its definitely not hard brick.
What was the android version when you wiped data?
Was there any custom recovery you used to wipe data?
You possibly wiped /system too, wiping system can result in bootloop.
Daman5202 said:
If its stuck on boot, its definitely not hard brick.
Click to expand...
Click to collapse
That's a relief. Thanks.
What was the android version when you wiped data?
Click to expand...
Click to collapse
I'm not sure about it, but I think it was 4.x.
Was there any custom recovery you used to wipe data?
Click to expand...
Click to collapse
No, there wasn't.
You possibly wiped /system too, wiping system can result in bootloop.
Click to expand...
Click to collapse
Sorry, but that doesn't make sense. The phone's been rooted for almost 2 years now, and 1 year ago, it turned on perfectly fine.
But let's assume that actually happened somehow, how do I recover from this?

Categories

Resources