Need Help - Poco F1 Android 12 Stuck in Recovery - Xiaomi Poco F1 Questions & Answers

I flashed an unofficial Evolution X v6.5 Rom For my Poco F1 today,
it was working fine but then I tried to Reboot into MY Custom Recovery( OrangeFox ) using the Advance Restart Option Exist in Rom.
OrangeFox Recovery Opening Image was Showing but it didn't opened, My phone shut down and rebooted again into the Same OrangeFox Opening Image and then shut down again.
It stuck into Recovery Opening Bootloop.
I tried holding the power button to reboot into system but noting is happening, It is showing same Recovery Opening Image and then shutting down,
I tried holding the power button + Volume UP Button, Same thing was happening Recovery Opening Image and then shutting down.
Luckily when I tried holding the power button + Volume down Button, It opened the bootloader.
So I thought Something happened to the OrangeFox recovery file So I installed the TWRP Recovery with My PC.
BUT Now It showing TWRP Opening Image and then shutting down. Same Recovery Bootloop.
Something( Maybe the Rom ) preventing me from rebooting into any recovery.
I should mention that I didn't installed any new app or anything, I just flashed the rom and then finished the Google setup.
I managed to shut down the phone by holding all 3 button for about 20sec.
But it's not charging anymore, if I plug the to phone to charger it start the whole Recovery Bootloop again.
Please Let me know if you know of any possible solutions.

I managed to fix that issue, In Future if anyone else got same problem in any phone, Then Follow this,
At First Hold all three button for about 25sec to shut down your phone,
at this situation your phone won't charge, if your battery completely drained then your phone might get hard brick, so shut down it at first.
Then download a stable & trustable rom and put that in SD Card or Pendrive( in this case you will be needed an OTG to plug the perdrive into your phone )
Then download the latest TWRP or any other Recovery in your PC. You really need the latest custom Recovery( 0 - 3 Months Old ).
I should let you know, You need to install ADB & Fastboot Drivers on your PC to perform any normal rooting process on your phone, And Download "Android Platform Tools".
Open CMD in "Android Platform Tools" Folder
Connect your phone to your PC in bootloader mode by holding down Power + Volume Down Button.
Then Type in CMD - fastboot devices
To check your device is properly connected or not. If your phone is connected properly then CMD will show a random number and fastboot. If not then connect the phone properly and check the driver.
Then Type - fastboot erase userdata
It will erase all your internal and data.
Then Type - fastboot flash recovery "PUT HERE THE LATEST CUSTOM RECOVERY FULL PATH"
It will flash the custom recovery, IN above command after writing recovery give a space then write the full path or hold and drag the latest custom recovery to command prompt, it will automatically write the full path for you.
After flashing the recovery now you can open the recovery.
Now Open the custom recovery immediately by holding down Power + Volume UP Button.
Then Wipe the Old Rom and flash the new downloaded rom from SD Card or Pendrive.
AND there you go, Now you can reboot into your new system or recovery.

Related

[Q] OT107 - Enter fastboot or recovery on rooted device

I got a tablet device (Omega OT107) I've rooted it using
Code:
ro.kernel.qemu
method.
Next I'm triying to flash Custom Recovery and my problems started here.
What I've tried:
1.
Code:
flash_image recovery
- no success process of flashing never ends
2. Install bootmenu to /data/bootmenu
3. Installed 2 different 2Init's
None of this worked or even had an impact on how device works (it always boots in android correctly).
I've tried to boot it to fastboot mode to flash recovery from there but there is a problem that I have.
Volume(up or down) + Power buttons starts device to Android not to bootloader (I've read you need to remove and reinsert battery to make it work, but device has a build in batery and needs to be taken apart to remove it so I did not tryed it)
Code:
adb reboot bootloader
- boots to what I think is a bootloader (screen is black(no light is comming out of it)) when connected to Windows PC it is seen as Android Bootloader Interface (Android-SDK driver).
Code:
fastboot devices
does not discover any devices, clicking volume or power button does nothing.
Code:
adb reboot recovery
- boots devices it what seems to be useless recovery mode. At start there is a standing android dude with fireball on his chest, and imidietly changes to a lying position with his chest oppened and an exclamation mark comming out of it (I've red it is ok and I need to press Volume(down/up) + Power buttons to open recovery menu but it does not happen).
My question is:
Is it normal to some devices bootloader to look like mine? How to make it discoverable to fastboot?
I had this issue and I fixed with "press all the buttons!" and suddenly I sow recovery menu...to factory reset. if it doesn't work repeat with rebooting with pin
Does someone knows a way how to hard reset this thing?? ^^
about firmware
Any idea where find the firmware for this tablet?
Mine is now freeze on recovery logo
hard reset OT107
1.Turn off our tablet.
2 We press the MENU button at the same time + POWER HOUSE click and hold
3.Wait until the Android image.
4.Then VOL + button and the POWER and appears to us to Recovery Mode
5.Navigation is Vol-i + and confirmed by pressing POWER.

My stuck in "No command" after booting

I'm a bit stuck here, would appreciate some assistance.
I tried to root my device (UMI Plus) by yesterday using 'SP Flash tool' by flashing TWRP and then installing SuperSU. That went fine, but after booting my Google Play Services kept rebooting rendering the device unusable. In an attempt to fix this I tried a "Factory Reset" via the Android settings menu which I guess was a bad idea because it started auto booting into Recovery... At that point no matter what I did I ended up back in Recovery.. Reboot to system, factory data reset.. all rebooted the phone back into TWRP recovery.
So I thought I would just try putting the default recovery back on the device again but whenever I power off the device and connect it to my PC it boots into recovery.. The phone needs to be powered off for SP Flash Tools to work. Tried loading recovery image via fastboot but the volume rockers don't work in fastboot so I can't confirm the action.
After some digging I read online that holding down VolUp + Power can 'force' into preload mode, which seems to have some success. I can see the device boot into "Preloader mode" in device manager in Windows, but it loses connection after about 3 seconds. So I did that with my SP flash tool ready and it seems to have erased recovery mode. Oops! Now whenever I try to get into recovery it just says "No command". No combination of button pressing, button holding, button releasing or anything will change this (This is the only answer I could find on Google!). Neither fastboot or adb can see the device either. It shows up as "MTP USB device" in device manager in Windows...
Is it doomed? I can't figure out what to do next...
P.S. The full ROM is available here but in RAR format.. which seems strange to me...
http://community.umidigi.com/thread-11462-1-1.html
Poke

Can't boot in fastboot mode

Hi,
I tried to flash lineageos 16 on my bkl09 emui9.
It was working but it was impossible to install app by play store... I tried many times to re-flash lineage img.
I'm actually blocked on TWRP. But it doesn't launch. When i start my phone, it boots on twrp, and the phone stays on the twrp boot screen but doesn't launch.
I can't turn the phone into fastboot mod by pressing vol- and power . It just restarts and reboot recovery twrp and block on boot screen twrp without launching...
I plug my phone on my computer, it reconized as adb devices but when I try to turn into fastboot mode by adb, nothing happen...
I hope there's a solution !
(and sorry for my english ... :/
power off the phone, put USB port in phone, press volume down key, now connect USB port to PC with volume down key press. it should boot to fastboot.
Rob1hn said:
Hi,
I tried to flash lineageos 16 on my bkl09 emui9.
It was working but it was impossible to install app by play store... I tried many times to re-flash lineage img.
I'm actually blocked on TWRP. But it doesn't launch. When i start my phone, it boots on twrp, and the phone stays on the twrp boot screen but doesn't launch.
I can't turn the phone into fastboot mod by pressing vol- and power . It just restarts and reboot recovery twrp and block on boot screen twrp without launching...
I plug my phone on my computer, it reconized as adb devices but when I try to turn into fastboot mode by adb, nothing happen...
I hope there's a solution !
(and sorry for my english ... :/
Click to expand...
Click to collapse
Try this command
Code:
adb reboot fastboot
miststudent2011 said:
Try this command
Code:
adb reboot fastboot
Click to expand...
Click to collapse
hi. Please, help, i cant reboot to fsstboot. If i do this from app or from adb my phone just reboots twice. I can boot into recovery and into download mode
Don't reboot into fastboot, boot into fastboot.
1st hold the up and down and power to start up so that it shows more than that "...is now booting". Then power off and press "down" and "power" with USB plugged to enter fastbboot. In fastbbot, flash the userdata.img and the cache.img (This cleans data and cache totally) from Huawei's updates, then you will be able to get into TWRP without being stucked.

Stuck in recovery mode

I accidently flashed the lineage 16 recovery instead of lineage 17.1 recovery. I tried to install the 17.1 update through updater but my phone stuck into recovery mode. Neither I can boot into bootloader nor to android. I can''t flash anything. Power + volume down and connect the cable also not working to go into bootloader. Even bootloader option within the recovery also brings me back to recovery mode. ...adb devices command is also showing "device offline". Any help will be appreciated.
you should start from the beginning
is your bootloader still unlocked?
stukka2006 said:
you should start from the beginning
is your bootloader still unlocked?
Click to expand...
Click to collapse
I can't go into fastboot mode. Is there any other way to check it?
Thank you @stukka2006 for replying me. I guess I saved my phone. So here what I did-
1. Extracted the stock firmware (Luckily I had one but can be found in the forum) and copied the dload folder to sdcard (as I was not able to access internal storage). (@stukka2006 your hint to start from the beginning)
2. Power off the phone and pressed Both volume buttons + power button simultaneously. After the vibration I left the power button while still holding both vol buttons till software update screen appears. But software update failed. So I just touched the reboot now option. The phone rebooted to fastboot mode.
3. I installed TWRP but was not able to reboot to recovery through commands and system reboot command brings me back to fastboot mode. So I again power off the device with cable connected and pressed both vol buttons. This time phone showed recovery screen (Should have worked with normal button shortcuts also, I guess) and I flashed the rom and rebooted normally.
Everything is working fine now except that I lost the data.
Happy you got all clear my friend !!!
[email protected]@wk said:
Thank you @stukka2006 for replying me. I guess I saved my phone. So here what I did-
1. Extracted the stock firmware (Luckily I had one but can be found in the forum) and copied the dload folder to sdcard (as I was not able to access internal storage). (@stukka2006 your hint to start from the beginning)
2. Power off the phone and pressed Both volume buttons + power button simultaneously. After the vibration I left the power button while still holding both vol buttons till software update screen appears. But software update failed. So I just touched the reboot now option. The phone rebooted to fastboot mode.
3. I installed TWRP but was not able to reboot to recovery through commands and system reboot command brings me back to fastboot mode. So I again power off the device with cable connected and pressed both vol buttons. This time phone showed recovery screen (Should have worked with normal button shortcuts also, I guess) and I flashed the rom and rebooted normally.
Everything is working fine now except that I lost the data.
Click to expand...
Click to collapse
You are quite lucky to have the stock ROM.
methuselah said:
You are quite lucky to have the stock ROM.
Click to expand...
Click to collapse
Yeah...who knows when you need it.

M4 Aqua (E2303) bricked - fastboot works but weirdly, flashmode does not

Hi!
M4 Aqua, E2303
Brief history, what I did before:
- On a full stock OS, first, I unlocked bootloader with fastboot oem unlock, which went through nicely.
- After that, I followed this thread to install custom recovery (twrp). Went through nicely (fastboot flash recovery recovery.img and fastboot flash boot boot.img).
- I was able to boot into recovery (twrp), and with the Install function, selecting Conceptify .zip it installed, rebooted.
- On the boot, the Conceptify gear logo was stuck spinning for a very long time. Then I just tried going into TWRP again to install Conceptify again, maybe for the second try it installs without the boot issue.
After this, I was no longer able to enter twrp recovery again. Okay, tried to flash the .img's again (boot and recovery), maybe I can at least get into TWRP recovery again, but no luck, despite both flash commands going through (both sending, writing were OKAY), without errors.
Current symptoms at this point:
- I still can get into fastboot (vol Up + usb plug in; LED red, then blue), and my PC can recognize the phone being in fastboot correctly, with serial number (in fastboot devices). It can still perform the flash/erase commands, but whenever I try fastboot reboot or fastboot reboot-bootloader, it doesn't reboot the phone. At this point, fastboot devices gives back a device in fastboot mode, but with a lot of question marks (?) instead of the serial number. On unplugging it, LED stays blue, like it is frozen or somthing. I kill the phone off with the power cutoff switch (next to microsd).
- holding just Power to turn on phone: Sony logo on the white background and is stuck. After a while I kill off with power cutoff.
- holding Power + vol Up, it vibrates once every 2 seconds or so. Nothing on screen, when I stop holding the buttons, stop vibrating. It however stays in a weird state, cause I can't get into fastboot for example (vol down + usb plug in; like I can do when it was powered off completely). I kill off with power cutoff.
- holding Power + vol Down: Sony logo on the white bkg, and stuck. After a while I kill off with power cutoff.
- tried the all-button hold: Power + vol Down + vol Up for 30 seconds, it was just vibrating every 2-seconds.
- flashmode with Flashtool: I downloaded a stock .ftf, loaded into FlashTool, but upon asking to connect the phone while holding vol Down, it can't detect it. The phone however lights red, then green on the LED light. Tried with both a new Flashtool (0.9.32.0, and a recommended older one as well: 0.9.18.6).
Is there something else I could try to get a working TWRP recovery again, and be able to boot into it?
Thanks for your help!
My M4 (E2312) have pretty much the same symptoms: can not boot anything and just stuck on SONY logo, Flashtool does not recognize phone in flashmode (Vol -), just fastboot. And using fastboot to flash system, boot, recovery shows finished processes but phone does nothing new. And phone does not response well to USB, only after a reset then it updates the status.
I have Pexo ROM v3, custom TWRP, SkyMelon 9 I think,Rooted SuperSU and Magisk( has conflicts so when I boot some pop up says X app has stopped working. When I install some more apps to use it was ok, then the pop ups show up more and more and then it decides to boot loop to the stage we are now.
I have tried install 0.9.33 and 0.9.23.1( somehow only 0.9.23.1 can install 3 drivers), Xperia Companion, Emma, ggsetup 3.2.0.1, Driver SONY so0104 (so0113 ADB interface- status show it cannot start),
So either it is the drivers on computer, the computer USB ports, the phone's software or hardware defects lead to software that caused it.
bdnlspam said:
Hi!
M4 Aqua, E2303
Brief history, what I did before:
- On a full stock OS, first, I unlocked bootloader with fastboot oem unlock, which went through nicely.
- After that, I followed this thread to install custom recovery (twrp). Went through nicely (fastboot flash recovery recovery.img and fastboot flash boot boot.img).
- I was able to boot into recovery (twrp), and with the Install function, selecting Conceptify .zip it installed, rebooted.
- On the boot, the Conceptify gear logo was stuck spinning for a very long time. Then I just tried going into TWRP again to install Conceptify again, maybe for the second try it installs without the boot issue.
After this, I was no longer able to enter twrp recovery again. Okay, tried to flash the .img's again (boot and recovery), maybe I can at least get into TWRP recovery again, but no luck, despite both flash commands going through (both sending, writing were OKAY), without errors.
Current symptoms at this point:
- I still can get into fastboot (vol Up + usb plug in; LED red, then blue), and my PC can recognize the phone being in fastboot correctly, with serial number (in fastboot devices). It can still perform the flash/erase commands, but whenever I try fastboot reboot or fastboot reboot-bootloader, it doesn't reboot the phone. At this point, fastboot devices gives back a device in fastboot mode, but with a lot of question marks (?) instead of the serial number. On unplugging it, LED stays blue, like it is frozen or somthing. I kill the phone off with the power cutoff switch (next to microsd).
- holding just Power to turn on phone: Sony logo on the white background and is stuck. After a while I kill off with power cutoff.
- holding Power + vol Up, it vibrates once every 2 seconds or so. Nothing on screen, when I stop holding the buttons, stop vibrating. It however stays in a weird state, cause I can't get into fastboot for example (vol down + usb plug in; like I can do when it was powered off completely). I kill off with power cutoff.
- holding Power + vol Down: Sony logo on the white bkg, and stuck. After a while I kill off with power cutoff.
- tried the all-button hold: Power + vol Down + vol Up for 30 seconds, it was just vibrating every 2-seconds.
- flashmode with Flashtool: I downloaded a stock .ftf, loaded into FlashTool, but upon asking to connect the phone while holding vol Down, it can't detect it. The phone however lights red, then green on the LED light. Tried with both a new Flashtool (0.9.32.0, and a recommended older one as well: 0.9.18.6).
Is there something else I could try to get a working TWRP recovery again, and be able to boot into it?
Thanks for your help!
Click to expand...
Click to collapse
Yes, I also tried installing conceptify but it doesnt work. At this point its better if you stick with the stock rom, remove as much bloatware as possible and consider it a phone because almost none of the ROMs here work stability wise, or they maybe stable but some features like display brightness or speakers dont work. So I recommend you install stock rom via flashtool and then unlock the bootloader via flashtool again and install twrp again. Also if possible try reinstalling the drivers for the phone in flashtool. Hope this works mate.
Not my name said:
Also if possible try reinstalling the drivers for the phone in flashtool.
Click to expand...
Click to collapse
Thanks for your answer!
Unfortunately, I still can't make Flashtool recognize my M4 as booted in flashmode. Tried installing the drivers with \Flashtool\drivers\Flashtool-drivers.exe , but choosing the "Flashmode drivers" option, it failed during the install (I guess cause there wasnt a connected device that supports it), tried both with phone being connected in flashmode (volDown + plug-inUSB), and phone disconnected as well.
bdnlspam said:
Thanks for your answer!
Unfortunately, I still can't make Flashtool recognize my M4 as booted in flashmode. Tried installing the drivers with \Flashtool\drivers\Flashtool-drivers.exe , but choosing the "Flashmode drivers" option, it failed during the install (I guess cause there wasnt a connected device that supports it), tried both with phone being connected in flashmode (volDown + plug-inUSB), and phone disconnected as well.
Click to expand...
Click to collapse
Can you try it on a Linux PC I guess?

Categories

Resources