Yes I don't know what happened I tried rooting it again because upon reboot I was unrooted and it screwed it up. It wouldn't boot just kept going to twrp and than the system wouldn't read in twrp so now I'm flashing stock again. I've been doing this for 5 years and have never had 1 single problem. I've even made a couple of custom roms for nexus 6 and S2 tablet but everything screws this P.O.S up. It sucks I like the phone but the development is extremely difficult
when it kept going back to twrp all you needed to do was format data in Twrp then it would have booted but you would have been back to a clean system as im sure you know format data wipes internal but it would have got it working again. Flashing stock via mi flash is a bit longwided for what you needed to do. This is a bit glitchy anyway because after updating the rom usually you will lose root and need to re root again because the boot.img is overwritten with whatever rom you flash but you shouldnt have got stuck in Twrp. If stuck in Twrp like this again format the data as it will save time having to use miflash to install stock again.
I understand all that I totally didn't think about format data. I don't understand why twrp was downgraded with 3.5.1 after flashing EU update. Do you know? What should I do if it does it again?
I mean how to properly install twrp update? What way do you recommend
There's so many ways 1. Install recovery ramdisk in advance
2. Install this twrp in advance
3. Fastboot flash
4. Inject twrp after flashing zip.
I don't know which one does what
well the reason the Twrp was changed because wen you flashed the updateed rom i believe Miui eu used the Nebrassy twrp as there built in recovery hence that will be flashed whenever you flash EU. While using EU roms ther is no need to flash twrp again because it is already included altho it is not the version stated here still functions without issue and u can flash magisk etc through it . So basically just update rom and you will always have Twrp because its the recovery used in EU by default you dont need to do anything extra.
Any reason why TWRP fastboot wouldnt be detected by win 11 (with driver signing disabled) ??
Fastboot worked with stock recovery.. Now I flashed TWRP and a ROM but when I reboot to fastbook the drivers are not being detected.
Fastboot worked with stock recovery.. Now I flashed TWRP and a ROM but when I reboot to fastbook the drivers are not being detected.
Hi, I have a Poco F3 and installed the last vasishat TWRP after unlocking my device, also installed a custom ROM DotOS 5.2.
Everything is fine, I installed and configured some app, configured some option of the system ( dark mode, fingerprint...), all ok. I did a backup before install magisk, I backed up boot, data and super partitions. Just for test, I restored immediately without wiping anything. At reboot, I had to configure my phone from scratch, and at the end I saw some apps already installed but the above configurations missing...
Maybe I'm wrong in some way...could someone explain the correct procedure to backup/recover the entire system? Reading around, I understood about limitation, but If I read this post I understand that I could be able to create a backup of my system and roll-back It, I don't need to install any new custom ROM, just create "snapshot" of my system sometimes...
Thank you
Last edited:
Hey guys, did a search of the thread and found this post. After four months, it seems like ADB Sideload is still broken. Are there any indications on when or if this will be addressed? Thanks, and apologies if I'm mistaken.
You can backup your files by using Swift Backup or TitaniumBackup.
I mainly use Swift Backup, with root access. Most of my app data can be restored with some app exceptions where the app is not accepting data after being restored and needs to be cleared for the app to be accessed.
I'm having the same problem on windows 10. It does get detected in miflash and adb fastboot though. This phone makes me extremely nervous and I have tons of experience with everything I have even made custom roms but nothing works right. I don't know how if possible to make a twrp backup to restore it. I thought it wasn't but I get conflicting reports. So twrp basically can flash zips and that's it so it should be said on opening page no backs ups or restore.
I fixed mine by rebooting with driver enforcement disabled.. Then update driver.. have disk.. .pointing to the xaiomi drivers previously installed (wouldnt detect drivers on disk no matter what tried)..
And yes.. Its an odd phone it a few ways.
You are losing me a little bit, driver enforcement disabled is that driver signature verification on windows your talking about?
Update drivers I think I understand you mean update Xiaomi USB drivers?
pointing to the xaiomi drivers previously installed?
Just to clarify we are talking about fastboot mode right?
Not twrp mode or recovery mode, the little animal working on the Android bot.
Yeah will be more clear.. My problems were 2 fold.. Firstly the ADB driver was accepted fine but the fastbook driver wasnt getting past this
gearupwindows.com
First time round simple reboot into that mode was good.. and I managed to flash everything for the first time..
But something got futzed with my FB driver since I did that and to flash again later it simply wasnt having it.. If you looked at device manager in win you could see a warning on the device / driver pairing.
It 'should' have been a simple (remove device) update driver and point it to the driver files on the hard disk. But again despite finding 3 different fastboot drivers for this phone, and having it previously working.. None would work.
What I had to do was (while booted into no driver enforcement mode) update driver, browse for drivers on this machine, let me pick from drivers on this device.. Or similar wording.. In there I could choose google or Xaiomi options likely because I had it working before. I picked the Xaiomi and then it worked while in that boot mode and now appears to work even in normal boot mode, which logically it shouldnt if the driver fails the boot enforcement but I dont know.
Hope that helps.
How to Disable Driver Signature Enforcement on Windows 11/10? | Gear up Windows 11 & 10
Disable driver signature enforcement on Windows 11/10 with our step-by-step guide. Install unsigned drivers and customize your system settings.
gearupwindows.com
First time round simple reboot into that mode was good.. and I managed to flash everything for the first time..
But something got futzed with my FB driver since I did that and to flash again later it simply wasnt having it.. If you looked at device manager in win you could see a warning on the device / driver pairing.
It 'should' have been a simple (remove device) update driver and point it to the driver files on the hard disk. But again despite finding 3 different fastboot drivers for this phone, and having it previously working.. None would work.
What I had to do was (while booted into no driver enforcement mode) update driver, browse for drivers on this machine, let me pick from drivers on this device.. Or similar wording.. In there I could choose google or Xaiomi options likely because I had it working before. I picked the Xaiomi and then it worked while in that boot mode and now appears to work even in normal boot mode, which logically it shouldnt if the driver fails the boot enforcement but I dont know.
Hope that helps.
Hi.. just read on XDA: TWRP 3.6.0 is out:
TWRP 3.6.0 released with support for devices that launched with Android 11
Yeah, and we have official support now, Nebrassy's TWRP has received the go ahead
Dumb it down a bit. What is now the go-for recovery for our Poco devices? (link please)
What is meant with 'go-ahead'. To release/maintain a fork or are some alteration integrated in the official release of TWRP?
This is also a nice opportunity to list any changes or reasons to adopt it maybe
Let me start with a link to what this is all about-> TWRP 3.6.0 is out now for most currently supported devices.
And link to our devices topic -> [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project. (maintained by Nebrassy btw)
Unofficial TWRP for A12
androidfilehost.com
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
Hello everyone, I have a problem flashing TWRP on the Poco F3. When I try via fastboot boot twrp.img, I always get the error: "FAILED (remote: Unrecognized command boot)", and when I install : fastboot flash boot twrp.img, and then install current recovery, I can boot the system won't start anymore, and it keeps rebooting into TWRP. I can then only format, flash TWRP again, and then install a ROM (Bliss ectr....), but then TWRP is gone again?!? How can I solve this problem?
I've done it now, it worked with the skkk.img for A12. With this TWRP the fastboot boot command worked
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
55
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
FEATURES AND FIXES:
- No need to reboot TWRP after flashing ROM, to flash gapps or any other zips. All zips you flash after a ROM will automatically go to the new slot.
- No need to flash TWRP everytime after flashing a ROM. TWRP automatically flashes itself after a zip (Controllable via a toggle)
- Supports Hentai OS encrypted devices
- Supports flashing MIUI zips
- Supports Vibration
- Supports wiping data without wrecking encryption.
BUGS:
On encrypted devices, if u unmount and remount /data, it will show garbage files in storage. This is because of metadata encryption and to fix it, reboot recovery.
SUPPORTS AND TESTED ON:
Mi11x (aliothin)
UNSUPPORTED (BUT MAY WORK):
Poco F3, Redmi K40 (alioth)
FLASHING INSTRUCTIONS:
Boot into attached boot.img using the following command:
Code:fastboot boot twrp-aliothin.img
Once booted, go to Advanced -> Press "Flash current booted TWRP"
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
- You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device.
If not, then you have to format data before flashing the ROM - You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
- Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
- Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
- If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
- If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
- If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
- Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
- Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
CREDITS:
@Nebrassy for original TWRP and device tree. I also repurposed some of his commits from gerrit.
SOURCE CODE:
Kernel (Prebuilt): https://github.com/ArrowOS-Devices/android_kernel_xiaomi_alioth
DOWNLOADS:
https://drive.google.com/file/d/1oY5WxfXYPRLumCcaPPFGuq9OhtB3CM_X/view?usp=sharing
MD5:- 0909f61c83ce9876843dabba5bf1247e
TELEGRAM GROUP LINKS:
https://t.me/PocoF3GlobalOfficial
https://t.me/pocoF3GlobalUpdates23New build uploaded. Download link stays the same.
CHANGES:
* Fix a bug due to which some ROMs failed to flash if currently on a custom ROM.
* Fix "flash current TWRP" failing when decryption failed.
* Fix data wipe not wiping ROM data completely.
Also, it seems if the ROM you are flashing does not support encryption, you can format your data partition after a reboot (as opposed to what I mentioned in the known limitations section earlier.)12New build uploaded.
CHANGES:-
* Fixed TWRP auto flash error after flashing ROM. (It was due to magisk)
* Fixed fastbootd commands returning "command not allowed on locked device"
Limitations have been updated to mention an issue with flashing magisk and backuptool after ROM flash :-
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
