Develop Bugs

[Official]TWRP Recovery for Moto G4 Plus

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
We have our set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
Motorola Moto G4 Plus
NOTE: If you are flashing TWRP for the first time then you need to check this thread and then flash TWRP.
XDA:DevDB Information
TWRP Recovery for the Moto G4 Plus
Contributors
yeshwanthvshenoy, pranav01
Device Tree:https://github.com/TeamWin/android_device_motorola_athene
Version Information
Status: Stable
Created 2016-05-26
Last Updated 2017-05-03

Reserved!

Awesome! Will try it out right now

awesome......will try it and let u know......

Great work !!

Thanks people..... great work..... I'll try it now.....
---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------
It requires unlocked bootloader right?

cool_sid said:
Thanks people..... great work..... I'll try it now.....
---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------
It requires unlocked bootloader right?
Click to expand...
Click to collapse
yes it require unlocked bootloader

on flashing it says image not signed or corrupt ..... please guide

[email protected] said:
on flashing it says image not signed or corrupt ..... please guide
Click to expand...
Click to collapse
Don't worry. You will get this even if you flash the stock recovery or the stock kernel via fastboot. Just reboot to recovery and it will be fine.

when i boot into recovery mode
it still says Anrdoid Recovery
motorola/ athene_retail/athene

[email protected] said:
when i boot into recovery mode
it still says Anrdoid Recovery
motorola/ athene_retail/athene
Click to expand...
Click to collapse
Reboot to recovery after flashing the twrp image. Then reboot your device from recovery.
If you reboot your phone from fastboot aftwr flashing twrp, it gets overwritten by stock recovery.

Silesh.Nair said:
Reboot to recovery after flashing the twrp image. Then reboot your device from recovery.
If you reboot your phone from fastboot aftwr flashing twrp, it gets overwritten by stock recovery.
Click to expand...
Click to collapse
He is right. Flash twrp and boot into recovery, if you boot normally, it will patch back the recovery.

Thanks mate, it did worked, installed xposed tweaked my phone , but after installing xposed file manager refuses to open

[email protected] said:
Thanks mate, it did worked, installed xposed tweaked my phone , but after installing xposed file manager refuses to open
Click to expand...
Click to collapse
Don't you need SuperSu for Xposed? I never use Xposed so have no idea. Were you able to root the device or how did you get it working?

after instaling TWRP , i installed xposed .......... i dont think i need root or for what ........... with xposed i installed ADblocker and vibrate on call connect .......... its charm now

Error!!
C:\Users\xxxx\Downloads\mfastboot-v2>mfastboot flash recovery twrp_athene_20150526.img
target max-sparse-size: 256MB
sending 'recovery' (12498 KB)...
OKAY [ 0.453s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
Downloaded from gdrive link. Tried several times. Same error.
Someone help?

carreddy said:
C:\Users\xxxx\Downloads\mfastboot-v2>mfastboot flash recovery twrp_athene_20150526.img
target max-sparse-size: 256MB
sending 'recovery' (12498 KB)...
OKAY [ 0.453s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
Downloaded from gdrive link. Tried several times. Same error.
Someone help?
Click to expand...
Click to collapse
Just reboot to recovery. It shows this error even when flashing the stock recovery. Works fine.

carreddy said:
C:\Users\xxxx\Downloads\mfastboot-v2>mfastboot flash recovery twrp_athene_20150526.img
target max-sparse-size: 256MB
sending 'recovery' (12498 KB)...
OKAY [ 0.453s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
Downloaded from gdrive link. Tried several times. Same error.
Someone help?
Click to expand...
Click to collapse
@Silesh.Nair is right. Even if you flash stock boot.img or recovery.img, you will get the error but just flash and reboot to recovery immediately(if you boot normally, stock rom will replace twrp with stock recovery). i do believe that Moto is just trying to scare us not to flash anything via fastboot

Okay folks, we are now Official Enjoy!

Hi ... the phone is bootloader unlocked and twrp installed and xposed is installed as well
now if there is an Android N update .... can i still update my phone and if no ... how do i update my phone
(supersu) is not installed
Regards

i want to go back stock recovery and relock the bootloader

Plss help me i unlocked the bootloader and installed twrp after that my system app deleted like Huawei care and not applying themes and font i formated the phone but not worked i wamt to go back on nougt or oreo beta rom currently twrp working fine pls help me my model number is bnd al10

moinkazi said:
Plss help me i unlocked the bootloader and installed twrp after that my system app deleted like Huawei care and not applying themes and font i formated the phone but not worked i wamt to go back on nougt or oreo beta rom currently twrp working fine pls help me my model number is bnd al10
Click to expand...
Click to collapse
delete

allrockedout said:
This is stock recovery. Flash in twrp as image. Select recovery ramdisk as partition.
After flash. Reboot to recovery from twrp. That should take you to stock recovery. There you can do a factory reset.
https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=sharing
If you also flashed magisk or root. You will need to flash kernel as well. I was able to flash in fastboot mode. https://drive.google.com/file/d/1hYHlyNpJUfvYzM9EOli2ASKp3cnx98_L/view?usp=sharing
Click to expand...
Click to collapse
When i hve to flash kernal bro after flash stock recovery or before ? And how to flash? Through twrp or fastboot mood and bro i don't understand this line ( Select recovery ramdisk as partition) pls tell me step by step

moinkazi said:
When i hve to flash kernal bro after flash stock recovery or before ? And how to flash? Through twrp or fastboot mood and bro i don't understand this line ( Select recovery ramdisk as partition) pls tell me step by step
Click to expand...
Click to collapse
The recovery I posted before was for bl24 usa version ORRRREEEEEOOOOO ONNNNLLYYY. You need to get correct recovery_ramdisk.img and kernel.img for your device. First flash stock recovery_ramdisk in twrp as img. When you select the recovery img twrp will ask you where you want to install it. Select ramdisk recovery. If you rooted your device than you need kernel. You need to flash that in fastboot. Make sure your frp is unlocked. If you don't flash kernel your device won't reboot. To extract those img for your device. You need to download update.zip for your device. Google Huawei update extractor. Download that. Select update zip in application then update.app. Extract kernel.img and recovery_ramdisk.img.
To get update.zip for your device download Huawei firmware finder in play store. Download only update.zip
In Huawei update extractor you will get an error when trying to open update.zip. go to settings and unclick first box in settings and try open. You will see like 20 or 30 files.

allrockedout said:
The recovery I posted before was for bl24 usa version. You need to get correct recovery_ramdisk.img and kernel.img for your device. First flash stock recovery_ramdisk in twrp as img. When you select the recovery img twrp will ask you where you want to install it. Select ramdisk recovery. If you rooted your device than you need kernel. You need to flash that in fastboot. Make sure your frp is unlocked. If you don't flash kernel your device won't reboot. To extract those img for your device. You need to download update.zip for your device. Google Huawei update extractor. Download that. Select update zip in application then update.app. Extract kernel.img and recovery_ramdisk.img.
To get update.zip for your device download Huawei firmware finder in play store. Download only update.zip
In Huawei update extractor you will get an error when trying to open update.zip. go to settings and unclick first box in settings and try open. You will see like 20 or 30 files.
Click to expand...
Click to collapse
Thnks bro

Perfect time to find this post. I am getting the OTA update notification but it won't install on TWRP. My strategy is to return to stock (unrooted and stock recovery) to get the OTA. Once I am on that, get TWRP and Resurrection Remix.

allrockedout said:
The recovery I posted before was for bl24 usa version...
Click to expand...
Click to collapse
BND-L24 you mean?

duckredbeard said:
BND-L24 you mean?
Click to expand...
Click to collapse
Si

allrockedout said:
Si
Click to expand...
Click to collapse
Is there any way I could flash the kernel in twrp recovery before or after the stock recovery is flashed?

duckredbeard said:
Is there any way I could flash the kernel in twrp recovery before or after the stock recovery is flashed?
Click to expand...
Click to collapse
I tried flash recover ramdisk than kernel in twrp, rebooted to stock recovery and factory reset. But wouldn't boot, than booted to fastboot and flashed kernel, fastboot flash kernel kernel.img and it rebooted and was all good. Just my experience.

Just trying to avoid using adb.

duckredbeard said:
Just trying to avoid using adb.
Click to expand...
Click to collapse
You could try flashing kernel in twrp just saying wouldn't boot for me. You could try flashing kernel in twrp reboot to twrp than flash stock ramdisk. Not sure

allrockedout said:
You could try flashing kernel in twrp just saying wouldn't boot for me. You could try flashing kernel in twrp reboot to twrp than flash stock ramdisk. Not sure
Click to expand...
Click to collapse
Think I just might flash both in fastboot. If I put the files in my folder with my adb, what would the commands be?
fastboot flash recovery RECOVERY_RAMDIS.img
fastboot flash kernel KERNEL.img
Would that be right?

duckredbeard said:
Think I just might flash both in fastboot. If I put the files in my folder with my adb, what would the commands be?
fastboot flash recovery RECOVERY_RAMDIS.img
fastboot flash kernel KERNEL.img
Would that be right?
Click to expand...
Click to collapse
Fastboot flash recovery_ramdisk recovery_ramdis.img

allrockedout said:
Fastboot flash recovery_ramdisk recovery_ramdis.img
Click to expand...
Click to collapse
Going to do this one then the kernel...
Not super worried, seems there are unbrick tools out there.
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
What state should the phone be in for this? TWRP recovery? Bootloader? Booted to Android?

duckredbeard said:
Going to do this one then the kernel...
Not super worried, seems there are unbrick tools out there.
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
What state should the phone be in for this? TWRP recovery? Bootloader? Booted to Android?
Click to expand...
Click to collapse
You can boot to fastboot from twrp than start flashing

allrockedout said:
You can boot to fastboot from twrp than start flashing
Click to expand...
Click to collapse
My reboot options in TWRP are System, Power off, Recovery, and Bootloader.
Assuming Bootloader is the one I am to select?
Sorry for all the questions...i have never restored stock kernel or recovery. Just trying to get it back to stock to take the OTA so I can get back to TWRP and install Resurrection Remix.

duckredbeard said:
My reboot options in TWRP are System, Power off, Recovery, and Bootloader.
Assuming Bootloader is the one I am to select?
Sorry for all the questions...i have never restored stock kernel or recovery. Just trying to get it back to stock to take the OTA so I can get back to TWRP and install Resurrection Remix.
Click to expand...
Click to collapse
Yeah bootloader is correct. Good luck.

allrockedout said:
Yeah bootloader is correct. Good luck.
Click to expand...
Click to collapse
PS C:\adb> Fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.135s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 1.167s
Didn't see the fail. Flashed kernel just after the above...
PS C:\adb> fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.853s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.868s
So they both failed. At least it rebooted to android!

duckredbeard said:
PS C:\adb> Fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.135s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 1.167s
Didn't see the fail. Flashed kernel just after the above...
PS C:\adb> fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.853s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.868s
So they both failed. At least it rebooted to android!
Click to expand...
Click to collapse
Is frp and bootloader unlocked when rebooting to fastboot both are red?

[RECOVERY][UNOFFICIAL][EFS][ARM/ARM64][3.3.1-0] Team Win Recovery Project

Team Win Recovery Project 3.3.1-0​
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Features
Code:
-- build 5 --
* ARM build
* Encryption blobs from OPJ28.111-22
-- build 4 --
* Removed busybox until is officially added into twrp
-- build 3 --
* Added system_image
* Added busybox
-- build 2 --
* Fixed encryption
* Rebased tree, cleaned it up
* Removed Treble
-- build 1 --
* EFS backup (fsc, fsg, modem, persist in one option)
* Treble support (mount /oem as /vendor)
Flashing guide
In bootloader/fastboot mode:
Code:
fastboot flash recovery <recovery_name.img>
Downloads
Here
XDA:DevDB Information
Team Win Recovery Project, ROM for the Moto G4 Plus
Contributors
Lyuu
Source Code: https://github.comLyuu17/android_device_motorola_athene
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2018-09-15
Last Updated 2019-11-04

ha ha, first reply

Can we flash non-treble ROMs or do we have to revert to previous non-treble recovery?

rahulsj92 said:
Can we flash non-treble ROMs or do we have to revert to previous non-treble recovery?
Click to expand...
Click to collapse
I'd say you have all options, no need to go back.
If you flash a non-treble ROM, it will contain a boot.img which boots the old way, without dependency on the vendor.img.
If you flash a treble ROM, you need to have flashed a specific treble boot.img plus a vendor.img before you reboot.

Is it as stable as a non-treble recovery or it has some bugs?

Kartik Shankhavaram said:
Is it as stable as a non-treble recovery or it has some bugs?
Click to expand...
Click to collapse
Afaik: Super-stable, nothing to worry about.
It just adds the option to flash to certain partitions (Vendor or OEM), and to backup those.
otherwise there is nothing specific for treble.
About bugs: for sure it has bugs, like any piece of software (nothing significant that I am aware of though).
You can try it without flashing. In fastboot mode, do this:
Code:
fastboot boot recovery.img

jer194 said:
Afaik: Super-stable, nothing to worry about.
It just adds the option to flash to certain partitions (Vendor or OEM), and to backup those.
otherwise there is nothing specific for treble.
About bugs: for sure it has bugs, like any piece of software (nothing significant that I am aware of though).
You can try it without flashing. In fastboot mode, do this:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Thanks! Would definitely try out this twrp!

great work
all the best for treble

Has anyone successfully installed a treble based rom with this recovery?

I guess this recovery can be installed through Rajat's twrp or is it necessary to install through PC??

mannered_hooligan said:
I guess this recovery can be installed through Rajat's twrp or is it necessary to install through PC??
Click to expand...
Click to collapse
Both ways

Lyuu said:
Both ways
Click to expand...
Click to collapse
Thanks .. I'll try this recovery and ArrowOS after my exam

Hey, so I'm not sure if decryption is working in this recovery? I tried decrypting my data partition (encrypted from lineageOS 14.1) but it claims the password is incorrect (despite the fact that the same password decrypts the partition OK with shreps' TWRP) does decryption work for anyone?

mannered_hooligan said:
I guess this recovery can be installed through Rajat's twrp or is it necessary to install through PC??
Click to expand...
Click to collapse
Yup. Generally, recovery versions overwrite your current version.

Could anybody help me? I'm facing the following issue:
E:\XT1641\Flashear\root\twrp-3.2.3-0>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (15390 KB)...
OKAY [ 0.493s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.123s]
finished. total time: 0.621s

ebol94 said:
Could anybody help me? I'm facing the following issue:
E:\XT1641\Flashear\root\twrp-3.2.3-0>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (15390 KB)...
OKAY [ 0.493s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.123s]
finished. total time: 0.621s
Click to expand...
Click to collapse
The (bootloader) Image not signed or corrupt message is nothing to worry about. At that point, you should just need to choose to reboot to recovery from the bootloader menu and all should be ok.

ETA?

Ekaksh Janweja said:
ETA?
Click to expand...
Click to collapse
Trolling 100

Does somebody else also has wrong date/time set in this TWRP version? I'm at the typical 1970/01/01 date.
I found Issue 640 in the official TWRP Github project itself - sorry I cannot post external links due to restrictions - but its rather old from 2016 although people have still reported this as being an issue last year. Actually I cannot imagine that this is (still) a problem for everyone though this issue is still open.

987654

Can't flash TWRP after 11.0.12.0

Hi, I was on 11.0.11 and after flashing 11.0.12 from TWRP
miui_GINKGOGlobal_V11.0.12.0.PCOMIXM_912960e1fc_9.0.zip
I can't flash TWRP
twrp-3.4.0-1-ginkgo.img
in fastboot mode even though there isn't an error
Code:
fastboot flash recovery twrp-3.4.0-1-ginkgo.img
Sending 'recovery' (65536 KB) OKAY [ 1.564s]
Writing 'recovery' OKAY [ 0.277s]
Finished. Total time: 1.868s
if I try to boot into recovery TWRP isn't there, it's on stock recovery. My bootloader is unlocked if it isn't obvious.
If I do
fastboot reboot recovery
after flashing TWRP, it doesn't boot into TWRP but instead into normal phone mode, not recovery.
If I do
fastboot reboot recovery
after flashing TWRP and then keep pressing the recovery key combo (PWR+VOLUP) it doesn't boot any recovery, it just keeps rebooting

-

Hacker?pcs said:
Hi, I was on 11.0.11 and after flashing 11.0.12 from TWRP
miui_GINKGOGlobal_V11.0.12.0.PCOMIXM_912960e1fc_9.0.zip
I can't flash TWRP
twrp-3.4.0-1-ginkgo.img
in fastboot mode even though there isn't an error
Code:
fastboot flash recovery twrp-3.4.0-1-ginkgo.img
Sending 'recovery' (65536 KB) OKAY [ 1.564s]
Writing 'recovery' OKAY [ 0.277s]
Finished. Total time: 1.868s
if I try to boot into recovery TWRP isn't there, it's on stock recovery. My bootloader is unlocked if it isn't obvious.
If I do
fastboot reboot recovery
after flashing TWRP, it doesn't boot into TWRP but instead into normal phone mode, not recovery.
If I do
fastboot reboot recovery
after flashing TWRP and then keep pressing the recovery key combo (PWR+VOLUP) it doesn't boot any recovery, it just keeps rebooting
Click to expand...
Click to collapse
Download twrp fastboot mode.
Download TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8
Download TWRP TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8 - in MiFirm ✅ - Xiaomi MIUI Firmware - ROM - TWRP download free and max speed - The biggest Xiaomi Mi download
mifirm.net

J. Harry Potter said:
Download twrp fastboot mode.
Download TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8
Download TWRP TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8 - in MiFirm ✅ - Xiaomi MIUI Firmware - ROM - TWRP download free and max speed - The biggest Xiaomi Mi download
mifirm.net
Click to expand...
Click to collapse
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP

Hacker?pcs said:
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Click to expand...
Click to collapse
Then ig.......try after reseting your device or clean flash latest miui with mi flash tool.(your bootloader needs to be unlocked)

Hacker?pcs said:
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Click to expand...
Click to collapse
By the way this is a different method. this should have worked. what did you do ?

J. Harry Potter said:
Then ig.......try after reseting your device or clean flash latest miui with mi flash tool.(your bootloader needs to be unlocked)
Click to expand...
Click to collapse
My bootloader is unlocked, I'm with Magisk since I bought the device, I usually to update download the recovery rom
Miui Updates
Redmi Note 8 Global Stable V11.0.12.0 OTA Apply for V11.0.11.0 https://bigota.d.miui.com/V11.0.12.0.PCOMIXM/miui-blockota-ginkgo_global-V11.0.11.0.PCOMIXM-V11.0.12.0.PCOMIXM-a0ac2f3c57-9.0.zip Recovery ROM...
t.me
and flash it then flash Magisk then TWRP to recovery, sometimes I forget though TWRP and then flash it from fastboot. I forgot it now but now it doesn't flash via fastboot for some reason
J. Harry Potter said:
By the way this is a different method. this should have worked. what did you do ?
Click to expand...
Click to collapse
As I've said, it acts like the official TWRP, it either reboots to fastboot or to normal phone mode.

Hacker?pcs said:
My bootloader is unlocked, I'm with Magisk since I bough the device, I usually to update download the recovery rom
Miui Updates
Redmi Note 8 Global Stable V11.0.12.0 OTA Apply for V11.0.11.0 https://bigota.d.miui.com/V11.0.12.0.PCOMIXM/miui-blockota-ginkgo_global-V11.0.11.0.PCOMIXM-V11.0.12.0.PCOMIXM-a0ac2f3c57-9.0.zip Recovery ROM...
t.me
and flash it then flash Magisk then TWRP to recovery, sometimes I forget though TWRP and then flash it from fastboot. I forgot it now but now it doesn't flash via fastboot for some reason
As I've said, it acts like the official TWRP, it either reboots to fastboot or to normal phone mode.
Click to expand...
Click to collapse
i don't know how you flashed that twrp. Just open EN_Recovery-twrp-oneclick-EN then press enter. and then boot your phone to fastboot mode and connect to pc. then in pc type 2 and then i hope it will work

J. Harry Potter said:
i don't know how you flashed that twrp. Just open EN_Recovery-twrp-oneclick-EN then press enter. and then boot your phone to fastboot mode and connect to pc. then in pc type 2 and then i hope it will work
Click to expand...
Click to collapse
I've flashed it with the fastboot I have from Android SDK, didn't run the script. I've checked it out and saw that it flashes the misc.bin file too, I've tried flashing it but now I'm stuck on fastboot... ffs
I've downloaded the official Fastboot rom
ginkgo_global_images_V11.0.12.0.PCOMIXM_20201119.0000.00_9.0_global_37804edbcb.tgz
but I can't flash its misc.bin, it says Volume full...
fastboot continue
says "system has been destroyed"
I really don't want to wipe data and start fresh with Mi Flash tool ffs

Hacker?pcs said:
I've flashed it with the fastboot I have from Android SDK, didn't run the script. I've checked it out and saw that it flashes the misc.bin file too, I've tried flashing it but now I'm stuck on fastboot... ffs
I've downloaded the official Fastboot rom
ginkgo_global_images_V11.0.12.0.PCOMIXM_20201119.0000.00_9.0_global_37804edbcb.tgz
but I can't flash its misc.bin, it says Volume full...
never heard of volume full problem. place the fastboot rom in desktop menu. and install necessary drivers that need to flash via mi flash tool
Click to expand...
Click to collapse

J. Harry Potter said:
never heard of volume full problem. place the fastboot rom in desktop menu. and install necessary drivers that need to flash via mi flash tool
Click to expand...
Click to collapse
Well the misc.bin from your link is 8KB, the misc.img from fastboot rom tgz is 8MB
It sucks because mi flash tool erases data...
EDIT
THANK GOD,
fastboot erase misc
fixes the destroyed problem and lets me boot.
I figured it out from the bat script in the tgz fastboot rom, it doesn't flash the contained 4MB misc.img, it just has "fastboot %* erase misc" near the end
Problem that I can't flash TWRP again so I can't root :/

Hacker?pcs said:
Well the misc.bin from your link is 8KB, the misc.img from fastboot rom tgz is 8MB
It sucks because mi flash tool erases data...
EDIT
THANK GOD,
fastboot erase misc
fixes the destroyed problem and lets me boot.
I figured it out from the bat script in the tgz fastboot rom, it doesn't flash it, it just has "fastboot %* erase misc" near the end
Problem that I can't flash TWRP again so I can't root :/
Click to expand...
Click to collapse
so now you can boot.
if you have a pc just store your data in pc and then flash miui. then ig it will clear all the bugs u r facing and then you can try to flash twrp

J. Harry Potter said:
so now you can boot.
if you have a pc just store your data in pc and then flash miui. then ig it will clear all the bugs u r facing and then you can try to flash twrp
Click to expand...
Click to collapse
Yeah seems to the only way, something blocks the custom TWRP recovery and a clean slate may be the only way

Hacker?pcs said:
Yeah seems to the only way, something blocks the custom TWRP recovery and a clean slate may be the only way
Click to expand...
Click to collapse
don't forget to flash VBMETA after so the custom recovery (twrp or orangefox) persist

Question Need help, Can't figure out how to change my ROM

Exactly a year ago I bought Poco F3, unlocked the bootloader and installed ArrowOS. Now I'm trying to figure out how to change my ROM and I can't really find any answers. I have the ArrowOS recovery and it's useless, I can't install another recovery with it. My fastboot also seems to be broken(?), it has a different logo and it's detected on my computer when I do (fastboot devices) but other than that it gives me a bunch of errors
I would like to at least know how to change the recovery. Is it possible that my bootloader got locked? One last thing, when I installed ArrowOS I used TWRP and updated it using OTA updates, now TWRP is gone.
Please help me

You need fastboot for TWRP.

It could not have gotten locked, no.

Arealhooman said:
It could not have gotten locked, no.
Click to expand...
Click to collapse
I just found a guide on Youtube for flashing twrp and I followed it to the (fastboot boot <TWRP>) part and I got this error
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Does this mean it got locked..?

Uh….maybe… did you lock it… what does it say in dev Setting sunder oem unlock.

Arealhooman said:
Uh….maybe… did you lock it… what does it say in dev Setting sunder oem unlock.
Click to expand...
Click to collapse
I don't have any oem unlock option in ArrowOS and I never locked anything wtf, I just used it as a normal phone and only did OTA updates + sometimes FW updates when required
Is there anyway to fix it?

ADB & Fastboot Binaries: https://developer.android.com/studio/releases/platform-tools
OrangeFox Recovery (recommended): https://orangefox.download/device/alioth
Install the Recovery ZIP by either ADB Sideload in ArrowOS Recovery
or you can extract the "recovery.img" and fastboot boot it ("fastboot boot recovery.img") and select "Install current Recovery"
Then you simply flash the ROM.zip (select "Reflash Recovery after ROM Flash") -> Reboot Recovery -> Format Data
The OTA Update has replaced your TWRP with ArrowOS Recovery, because ROM Updates replace the boot-partition (along with other system related partitions). The boot-partition contains the recovery-environment.
Only install Custom Recoveries from inside the Recovery, because Fastboot can only replace partitions entirely (and boot-partitions contains both bootloader & recovery)
The bootloader of the Poco F3 cannot (or shouldn't) be locked on Custom Software.

gobertel said:
I just found a guide on Youtube for flashing twrp and I followed it to the (fastboot boot <TWRP>) part and I got this error
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Does this mean it got locked..?
Click to expand...
Click to collapse
Download these:
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/boot.img/download
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/vendor_boot.img/download
First link, "fastboot flash boot boot.img"
Second link, "fastboot flash vendor_boot vendor_boot.img"
Then Fastboot booting into your Recovery-file should work.

Also, what's the problem with ArrowOS anyway? We've ArrowOS MiPa, it's a good and reliable ROM.

cyanGalaxy said:
Download these:
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/boot.img/download
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/vendor_boot.img/download
First link, "fastboot flash boot boot.img"
Second link, "fastboot flash vendor_boot vendor_boot.img"
Then Fastboot booting into your Recovery-file should work.
Click to expand...
Click to collapse
I noticed that these are for ArrowOS 13, I'm on 12.1 and they did not work
Do you also suggest I go into fastboot by which method because each one looks different
Recovery > Advanced > Enter fastboot
Or
Hold power button with volume down method
Also I'm just looking to update to Android 13 in general

Thank you for helping me out by the way

gobertel said:
I noticed that these are for ArrowOS 13, I'm on 12.1 and they did not work
Do you also suggest I go into fastboot by which method because each one looks different
Recovery > Advanced > Enter fastboot
Or
Hold power button with volume down method
Also I'm just looking to update to Android 13 in general
Click to expand...
Click to collapse
Both methods of booting into Fastboot is the same I would guess.
Yes we do have ArrowOS MiPa, you should only need to flash the ArrowOS 13 MiPa ROM ZIP in Recovery, but I rather recommend you using OrangeFox or TWRP for that.
What do you mean by "did not work". "Did not work" can mean anything.

Are you using the latest official ADB & Fastboot Binaries? The ones I've given you?
If yes, you can use this Payload Dumper Tool, to extract the "vendor_boot.img" and "boot.img" from ArrowOS 12. Maybe those from Arrow v12 can be flashed.
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com

cyanGalaxy said:
Both methods of booting into Fastboot is the same I would guess.
Yes we do have ArrowOS MiPa, you should only need to flash the ArrowOS 13 MiPa ROM ZIP in Recovery, but I rather recommend you using OrangeFox or TWRP for that.
What do you mean by "did not work". "Did not work" can mean anything.
Click to expand...
Click to collapse
fastboot flash boot boot.img
Sending 'boot_a' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
fastboot boot recovery.img
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Another thing to add is I still I get the unlock symbol when booting up the phone, I dont know if that makes a difference

cyanGalaxy said:
Are you using the latest official ADB & Fastboot Binaries? The ones I've given you?
If yes, you can use this Payload Dumper Tool, to extract the "vendor_boot.img" and "boot.img" from ArrowOS 12. Maybe those from Arrow v12 can be flashed.
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes I'm using the exact one you gave me and I will try it

gobertel said:
Yes I'm using the exact one you gave me and I will try it
Click to expand...
Click to collapse
Yup try it.
Else, here I have the vendor_boot.img & boot.img from the latest ArrowOS MiPa (February). More up-to-date than the SourceForge links.
Either the 2 files from ArrowOS v12, or the latest v13 ones that I've uploaded here, should definitely work.
Also try rebooting Fastboot Mode.

XDA doesn't let me upload the boot.img ඞ

cyanGalaxy said:
XDA doesn't let me upload the boot.img ඞ
Click to expand...
Click to collapse
Starting to think I should just give up, no matter what I do I get (Download is not allowed on locked devices)
The fastboot method you suggested does not work, it gets stuck on (waiting for any devices) but the recovery one works although like I said, I get the error no matter what I do
Is it locked or what?? I'm trying to figure that out and if it is how did it even get locked in the first place
I'm guessing there's no way to resolve it and that I'll be stuck on Android 12 for eternity
So sorry for wasting your time, I always end up with weird issues in everything

gobertel said:
Starting to think I should just give up, no matter what I do I get (Download is not allowed on locked devices)
The fastboot method you suggested does not work, it gets stuck on (waiting for any devices) but the recovery one works although like I said, I get the error no matter what I do
Is it locked or what?? I'm trying to figure that out and if it is how did it even get locked in the first place
I'm guessing there's no way to resolve it and that I'll be stuck on Android 12 for eternity
So sorry for wasting your time, I always end up with weird issues in everything
Click to expand...
Click to collapse
Waiting for any devices means your PC does not detect the phone.
Download this: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
And install the USB driver.
And no it's not locked, the Unlocked symbol during Boot is normal. I think it was a bug with older ArrowOS Bootloader versions. Not quite sure.

cyanGalaxy said:
Waiting for any devices means your PC does not detect the phone.
Download this: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
And install the USB driver.
And no it's not locked, the Unlocked symbol during Boot is normal. I think it was a bug with older ArrowOS Bootloader versions. Not quite sure.
Click to expand...
Click to collapse
IT WORKED. Thank you so much, it was a driver issue but the exact version you gave me didn't work, I had to find another one