Fastboot rebooting /corrupted - Xiaomi Poco F1 Questions & Answers

I am on Vendor_fw 12.0.2.0 and on Awaken android 11. I did a full wipe - cache,data and flashed crdroid which in turn changed my recovery from TWRP to its custom recovery. Now i am unable to flash anything using fastboot. Whenever i enter fastboot flash command, even before flashing starts, the phone reboots. I have tried changing recovery using adb sideload and it doesn't work. I even tried flashing other customs roms and i keep getting Signature verification failed and wrong footer error command. I can now only flash roms with pixel base. I can't even flash magisk. I tried using Miflash and even then no luck. Any solution to fully wipe everything and i can start from scratch?

Related

[Q] Broken system, recovery and bootloader flash failes - What to do?

First of, I'm running Cyanogenmod 12.1 on my Z2.
On the install it vanished my TWRP Recovery, so I decided to reflash it using their app - this was unsucessfull. I thought I would flash it the next day using adb, so I didn't mind.
However in the next hours I needed to reboot the phone - resulting in the Sony logo and nothing more. So I bootet into the CM recovery and tried to reflash the CyanDelta zip - this failed and resulted in "footer is wrong - signature verification failed - Installation aborted". The next thing I tried was flashing a zip by adb recovery sideload - this failed as well and resulted in "protocol fault (no status)".
This was when I tried to boot into the bootloader using the recovery menu entry. The screen got black, the LED lighted up blue and nothing happened forever. The same thing occours when I try to boot into the bootloader by hardware keys (hold VolUp and insert MicroUSB cable).
So, in short:
I can't boot android
I can't install zips by CM recovery
I can't boot into the bootloader [EDIT: I can.]
I can't install nandroid backups since the CM recovery doesn't offer that
Any idea?
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
the_crevis said:
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
Click to expand...
Click to collapse
Ah, I feel dumb now. I might be damaged from the informational Nexus bootloader.
So, I tried to flash a new recovery - fastboot flash twrp-2.8.6.0-sirius.img - which succeded, but it still boots the CM Recovery. Buh.
Seems like something is overriding the recovery on boot. So lets erase everything:
Code:
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot flash twrp-2.8.6.0-sirius.img
Aaaand - still CM Recovery.
I also tried to flash a stock image as you suggested, however:
Code:
fastboot flash system system.sin
sending 'system' (1800183 KB)...
FAILED (remote: data too large)
finished. total time: 0.002s
No worries, I came from a nexus 4 and it confused me as well at first. Try exacting http://forum.xda-developers.com/xperia-z2/development/kernel-m5-kernel-t2858912 and flashing the boot image via fastboot. That should give you a working recovery.
As I said, flashing a recovery by fastboot results in the CM Recovery.
I just tried to wipe my device using the CM Recovery, it told me it was unable to mount /data - my guess? The filesystem is ****ed up.
EDIT: I got it. Seems like TWRP needs some custom stuff to work (which is provided by CM). Flashing philz worked fine and allowed me to sideload a proper ROM. Everything fine now

[SD625] Trouble installing TWRP despite flashing Lazyflasher + SuperSU

Cross-post from here
I have a frustrating issue.
After booting into fastboot mode, I type the following commands where recovery.img is the TWRP mido image. I also have lazyflasher and SuperSU on my SD card, but onto that later...
I type :
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
The phone boots into TWRP perfectly. I then flash the lazyflasher zip file. However when I try to boot back into recovery, the Mi logo briefly appears, then nothing... black screen.
So at the moment, I don't care about what is on internal storage. I went to wipe-->format data, then rebooted straight into bootloader to try and flash TWRP again. However this also gives me a black screen when I try and boot into recovery after installing Lazyflasher. I tried again, however I also flashed SuperSU immediately after lazyflasher. Rebooting into recovery from TWRP gives me a black screen again.
Should I perhaps try to flash a custom kernel? I am lost for other solutions.
TLDR: TWRP unsuccessful after: fastboot flash recovery, then fastboot boot recovery.img, then flashing lazyflasher, followed by flashing SuperSU, then choosing Reboot-->Recovery.
bigpavmate said:
Cross-post from here
I have a frustrating issue.
After booting into fastboot mode, I type the following commands where recovery.img is the TWRP mido image. I also have lazyflasher and SuperSU on my SD card, but onto that later...
I type :
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
The phone boots into TWRP perfectly. I then flash the lazyflasher zip file. However when I try to boot back into recovery, the Mi logo briefly appears, then nothing... black screen.
So at the moment, I don't care about what is on internal storage. I went to wipe-->format data, then rebooted straight into bootloader to try and flash TWRP again. However this also gives me a black screen when I try and boot into recovery after installing Lazyflasher. I tried again, however I also flashed SuperSU immediately after lazyflasher. Rebooting into recovery from TWRP gives me a black screen again.
Should I perhaps try to flash a custom kernel? I am lost for other solutions.
TLDR: TWRP unsuccessful after: fastboot flash recovery, then fastboot boot recovery.img, then flashing lazyflasher, followed by flashing SuperSU, then choosing Reboot-->Recovery.
Click to expand...
Click to collapse
Also, once just flash lazyflasher.zip /super su from twrp > next reboot into system from twrp! Do not choose reboot to recovery for the first time. Boot to system..
Okay guys, I have found the solution, although I would still like to know WHY this happened!
I used fastboot + Xiaomi Flash Tool to flash the latest stable ROM. I then enabled USB Debugging, and did all the same steps which resulted in being able to boot into recovery normally! I didn't flash lazyflasher this time because I flashed SuperSU instead, apparently it patches the dm-verity thing too. This was a suggestion from this post

Bricked-Endless flashing modem at fastboot (EDL Mode)

Hi!
I was trying to install new ROM via OrangeFox (R10.0) but it always give me the error 7. Trying to solve this now my phone only gets to fastboot via EDL and when trying to flash stock ROM it got stuck endless at flash modem.
Things i did (Using OrangeFOX R10.0 and Flash Tools 2019.12.06):
-Install ROM directly, as i always do. Gives me the error 7 saying "if it is the correct device".
-Install latest firmware then ROM. The firmware install says that its already find same version on device and install again, but trying to install ROM after still give error 7.
-Install firmware, wipe all, reboot, rom. Still error 7
-Tried to go back to stock but from recovery ROM gives error 7 and from fastboot gives me the Mismatching device.
-Tried to format first data partition (via OragenFox), but still gives me the same error.
-Tried to fix the "Mismatching device" on fastboot flash doing this www.youtube.com/watch?v=_osMF9EubhI. When trying to flash first gives modem error and after say Write command error.
-Last thing i tried was flashing stock ROM (lastest V11.0.2 and V10.0.2) via fastboot on EDL mode, but it gets endless flash modem (see image = https://i.imgur.com/BuT3rIl.png)
At moment, my phone doesnt boot anymore even at recovery or normal fastboot, only via EDL. I think its something related to modem files, but i dont know how to format or recovery the partition that have modem installed.
If someone can really help, i will be really thankfull!!
Have you tried using another usb port/cable? If you are using USB 3.0 port than try it on USB 2.0 port as 3.0 have sometimes issues. Also try re-downloading your ROM.
Please use emmcdl tool and try to flash stock rom from there. Worked for one of my friend.

touches not working in recovery

My TWRP was not loading (just a logo) and I forgot to root my device. I tried other versions and OrangeFox instead, and then "swipe to unlock" appeared, but touches are not working at all. Only side buttons are working.
*Everything works fine in MIUI
Twrp recovery works without root. That's why you can install magisc to root your phone using twrp. Try more twrp project and try to enter multiple times to recovery. I had the same problem and after 2-3 attempts it works. I'm using pitch black recovery And I recommend it with confidence
You can find this recovery here :
https://forum.xda-developers.com/t/...crypted_data-v2-9-0-base-twrp-v3-3-1.4000857/
As I tryed a loot of twrp project this was the most stable for me. Just flash it using fast boot. Or you can boot it Instead of flashing.
Code for boot : fastboot boot twrp.img
You can use this if you have problems on flashing the recovery.. So after you boot on it you can flash the zip file using twrp if it won't flash using your pc / cmd.
INFO:
If you want root and you got boot loop after flashing Magisk with TWRP(Phone stuck at boot process up to 2-3minutes ) boot twrp and format your DATA. DON'T WIPE! FORMAT!
**WIPE/FORMAT DATA**
*Restart your phone and be patient the boot may take some time after perform data format*
Now you should have the Magisk installed! (The data format does not wipe Magisk Manager from the system (!). It will be there.)
-------------
(!) If something goes wrong you can flash again the stock rom downloaded and repeat the process (!)
------------------

Asus Zenfone Max M2 [X01AD] not booting into system after flashing cutsom ROM(s)

I have unlocked my bootloader using official Asus tool, I then went on to flash TWRP 5.3.x.x. using fastboot and also formatted userdata and cache from fastboot itself to remove encryption. Recovery works fine.
I have tried flashing both these ROMs. [links below]
[ROM][OFFICIAL][11.0][X01AD] Arrow OS
[ROM][11][5.R] Project Sakura [2021/03/19][UNOFFICIAL]
I followed the instructions, formatted data using TWRP, wiped system, vendor, cache, data, dalvik.
I then flashed the ROM from TWRP itself, and I have also tried to install it through ADB sideloading. Then I wipe dalvik/cache.
Both instances, the installation happens fine but when I reboot phone gets stuck in fastboot mode. I resolve that by flashing 'vbmeta.img'.
Then phone starts booting but gets stuck in a loop bootloader-->ASUS logo-->"Powered by Android"-->bootloader
So basically, it does not boot into system.
I have even flashed stock A10 firmware from here Stock Vendor and Firmware images for Asus Max M2 but still no resolution.
I have also tried manually mounting system partition from TWRP, doesn't work.
Any help would be much appreciated.
Connect phone and PC via USB-cable and in Windows command prompt run this command sequence
Code:
fastboot devices
fastboot reboot
to take back phone to it's normal ANDROID mode.
arko2000 said:
I have unlocked my bootloader using official Asus tool, I then went on to flash TWRP 5.3.x.x. using fastboot and also formatted userdata and cache from fastboot itself to remove encryption. Recovery works fine.
I have tried flashing both these ROMs. [links below]
[ROM][OFFICIAL][11.0][X01AD] Arrow OS
[ROM][11][5.R] Project Sakura [2021/03/19][UNOFFICIAL]
I followed the instructions, formatted data using TWRP, wiped system, vendor, cache, data, dalvik.
I then flashed the ROM from TWRP itself, and I have also tried to install it through ADB sideloading. Then I wipe dalvik/cache.
Both instances, the installation happens fine but when I reboot phone gets stuck in fastboot mode. I resolve that by flashing 'vbmeta.img'.
Then phone starts booting but gets stuck in a loop bootloader-->ASUS logo-->"Powered by Android"-->bootloader
So basically, it does not boot into system.
I have even flashed stock A10 firmware from here Stock Vendor and Firmware images for Asus Max M2 but still no resolution.
I have also tried manually mounting system partition from TWRP, doesn't work.
Any help would be much appreciated.
Click to expand...
Click to collapse
hello did you finally find the solution? I also can't move on any custom rom starts in fastboot mode
Is it possible that no one has a solution to this problem? I've been getting annoyed for three days and trying...
Is there any resolution anyone found out? I am stuck at the same problem for days. @N3I3 @arko2000
@Drigio @N3l3 @arko2000
FIX "BOOTLOOP ISSUE" AFTER FLASHING CUSTOM FIRMWARE IN ANDROID 10
Click to expand...
Click to collapse
Requirements:
vbmeta.img (For A10)
ADB & Fastboot (In case you don't have one)
Instructions:
Install ADB-and-Fastboot++_v1.0.6.exe and run.
Copy the commands below.
Commands:
Code:
fastboot erase vbmeta
- OPTIONAL
Code:
fastboot flash --disable-verity vbmeta 'location of vbmeta'
- OR DRAG THE A10 vbmeta
Code:
fastboot reboot
Hope this helps!
I HAVING ALSO SAME PROBLEM CAN ANY ONE FIX IT..

Categories

Resources