Develop Bugs

Any working TWRP for EMUI Oreo 8.0?

"fastboot flash recovery twrp.img" doesn't work. Gives me an "FAILED (remote: partition length get error)" error while I tried to flash TWRP that I downloaded from "unlock bootloader" XDA page. I have unlocked my bootloader, but couldn't install TWRP and proceed further. Noob here. Any help is appreciated. Thanks in advance.
This is what I got:
F:\Phone\Honor 7x\adb>fastboot flash recovery twrp_Honor_7x.img
target reported max download size of 471859200 bytes
sending 'recovery' (25158 KB)...
OKAY [ 0.634s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.649s

The New Partition Name in Oreo is recovery_ramdisk for Recovery.
Gesendet von meinem BND-L21 mit Tapatalk

johination said:
The New Partition Name in Oreo is recovery_ramdisk for Recovery.
Gesendet von meinem BND-L21 mit Tapatalk
Click to expand...
Click to collapse
Thanks mate !:good:

This twrp does not want to boot up.

error still not resolved
johination said:
The New Partition Name in Oreo is recovery_ramdisk for Recovery.
Gesendet von meinem BND-L21 mit Tapatalk
Click to expand...
Click to collapse
i am still getting following error
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (34634 KB)...
OKAY [ 1.214s]
writing 'recovery_ramdisk'...
FAILED (remote: partition error)
finished. total time: 1.235s

passengerUS$ said:
i am still getting following error
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (34634 KB)...
OKAY [ 1.214s]
writing 'recovery_ramdisk'...
FAILED (remote: partition error)
finished. total time: 1.235s
Click to expand...
Click to collapse
what file and command did you use?

mrmazak said:
what file and command did you use?
Click to expand...
Click to collapse
I have used all these commands and n all of them give errors
1) fastboot flash recovery twrp.img
2) fastboot flash recovery_ramdisk twrp.img
3) fastboot flash ramdisk twrp.img

passengerUS$ said:
I have used all these commands and n all of them give errors
1) fastboot flash recovery twrp.img
2) fastboot flash recovery_ramdisk twrp.img
3) fastboot flash ramdisk twrp.img
Click to expand...
Click to collapse
number 2 is correct, as long as your twrp.img is correct oreo recovery.
number 3 has put twrp into your (boot) , this is possibly a bad move.

mrmazak said:
number 2 is correct, as long as your twrp.img is correct oreo recovery.
number 3 has put twrp into your (boot) , this is possibly a bad move.
Click to expand...
Click to collapse
Number 2 is also not working I think I have to wait for official twrp oreo recovery image

passengerUS$ said:
Number 2 is also not working I think I have to wait for official twrp oreo recovery image
Click to expand...
Click to collapse
Im on oreo and am using this twrp on my L24 https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447. I used the 0.3.img. I've used it to backup and then flashed magisk 16 with no problems.

Joebloeh said:
Im on oreo and am using this twrp on my L24 https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447. I used the 0.3.img. I've used it to backup and then flashed magisk 16 with no problems.
Click to expand...
Click to collapse
Did you make the backup through TWRP or ADB? I'm using the same one and every time I go to make a back up it fails at system.img. Also do you know how to use decryption with it?

stuck on logo screen
Joebloeh said:
Im on oreo and am using this twrp on my L24 https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447. I used the 0.3.img. I've used it to backup and then flashed magisk 16 with no problems.
Click to expand...
Click to collapse
i flashed it it wroked perfectly thanks man you saved my day

Hold upppppppp.
Don't use Huawei p10 recovery. I tried it and it just got me stuck on the TWRP splash screen.
Just do "fastboot flash recovery_ramdisk complete_twrp_ramdisk.img"
I use this and it works flawlessly.
https://forum.xda-developers.com/devdb/project/dl/?id=28883

It worked do you have any super su version that works with it because when u install super su it shows ramdisk aborting installation error

passengerUS$ said:
It worked do you have any super su version that works with it because when u install super su it shows ramdisk aborting installation error
Click to expand...
Click to collapse
I would advise not to flash SuperSU. Magisk is the way to go. And you don't give enough details so I (and other people) can't really help you.
You're flashing it through TWRP?

crayonicle said:
I would advise not to flash SuperSU. Magisk is the way to go. And you don't give enough details so I (and other people) can't really help you.
You're flashing it through TWRP?
Click to expand...
Click to collapse
Yes I have flashed it through twrp
Now I want to root my device but when I install supersu in through twrp zip installation it shows
Checking patch status, attempting to find stock backup
Stock restore failed, attempting ramdisk restore
Ramdisk restore failed aborting
Do you need any extra information then pls comment

passengerUS$ said:
Yes I have flashed it through twrp
Now I want to root my device but when I install supersu in through twrp zip installation it shows
Checking patch status, attempting to find stock backup
Stock restore failed, attempting ramdisk restore
Ramdisk restore failed aborting
Do you need any extra information then pls comment
Click to expand...
Click to collapse
Do you get the same error with Magisk? Try Magisk please then report back.

crayonicle said:
Hold upppppppp.
Don't use Huawei p10 recovery. I tried it and it just got me stuck on the TWRP splash screen.
Just do "fastboot flash recovery_ramdisk complete_twrp_ramdisk.img"
I use this and it works flawlessly.
https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
When I first installed the p10 recovery it did hang up on the splash screen for at least a minute. But, now when I enter recovery it hangs more like ten or fifteen seconds.

crayonicle said:
Do you get the same error with Magisk? Try Magisk please then report back.
Click to expand...
Click to collapse
I tried magisk and it worked I was able to successfully root my phone thanks man
---------- Post added at 04:21 PM ---------- Previous post was at 04:17 PM ----------
Joebloeh said:
When I first installed the p10 recovery it did hang up on the splash screen for at least a minute. But, now when I enter recovery it hangs more like ten or fifteen seconds.
Click to expand...
Click to collapse
Use the 0.3 IMG the other updated images hang up on Honor 7x when I used the latest one my twrp got stuck on twrp logo then I flashed it with 0.3 IMG as mentioned in the comment and It worked flawlessly

this is the recovery to use for 7x oreo right?

Can't flash TWRP - rollback warning. Please advise

I have Chinese 6gb 128gb Mi Max 3 with latest China stable ROM. Finally i decided to get root but i can't flash TWRP over fastboot as in all instructions. My bootloader is unlocked. I get following warning
J:\Xiaomi Mi Max 3 - root>fastboot flash recovery twrpteamwin.img
target reported max download size of 536870912 bytes
sending 'recovery' (61164 KB)...
OKAY [ 1.333s]
writing 'recovery'...
(bootloader) Security Warning: rollback version downgrading,
(bootloader) which may make your device enter to EDL state!!!
(bootloader) Warning: If you want force flashing, try do
(bootloader) 'fastboot oem ignore_anti' before!
FAILED (remote: Please check your package anti version!!!)
finished. total time: 1.353s
I tried 3 versions of TWRP. I also installed latest global stable ROM. Same error. What should i do? Please help...

Same for me. Tried
Code:
C:\platform-tools>fastboot flash recovery twrp-3.3.0-0-nitrogen.img
Sending 'recovery' (61164 KB) OKAY [ 1.325s]
Writing 'recovery' (bootloader) Security Warning: rollback version downgrading,
(bootloader) which may make your device enter to EDL state!!!
(bootloader) Warning: If you want force flashing, try do
(bootloader) 'fastboot oem ignore_anti' before!
FAILED (remote: 'Please check your package anti version!!!')
fastboot: error: Command failed
Is it safe to do the oem ignore_anti thing and force it or would it brik my device?
Device should be official global 64gb 4 gb RAM bootloader unlocked official with 720h waiting periode. Currently MIUI Global 10.2.1.0 installed.

That's what I'm trying to figure out, if it's safe to override it. I don't want to brick my phone. Right now i had installed China beta ROM which has a root built in. But Android Auto refuses to work with this ROM. So i have to either go back to China stable without root, or flash TWRP somehow

So i tried it with
Code:
fastboot oem ignore_anti
At least twrp has started. If do not flash any old miui it should work. I think i go with the EU developer one. or may be RR GSI.

bigScreenUser said:
So i tried it with
Code:
fastboot oem ignore_anti
At least twrp has started. If do not flash any old miui it should work. I think i go with the EU developer one. or may be RR GSI.
Click to expand...
Click to collapse
PLease let me know if you were able to flash ROM after that! I'm waiting for your reply and biting my nails

Try
fastboot boot twrp.img
And then flash twrp.img through booted recovery.

bigScreenUser said:
So i tried it with
Code:
fastboot oem ignore_anti
At least twrp has started. If do not flash any old miui it should work. I think i go with the EU developer one. or may be RR GSI.
Click to expand...
Click to collapse
So, did it work? Were you able to flash ROM after overriging ARB warning during TWRP install?

If anyone is interested in overcoming this error: I have done the following, here are my steps:
My phone: China Stable ROM, 6Gb/128Gb Mi Max 3
- Make sure oyu have unlocked bootloader
- I flashed Global Stable ROM first, with the chinese software tool: essentially just automated flashing via fastboot, but any method works. Custom ROMs would be flashed after TWRP.
- Copy TWRP image on a flash drive, make sure it's accessible from the phone
- Phone in fastboot mode, conenct to PC "fastboot boot twrp-tw3300.img" (renamed latest teamwin TWRP image for Mi Max 3)
- Phone boots in TWRP
- Select flash - image - and flash TWRP from inside TWRP (no wiping, nothing else, flash image to recovery partition)
- If root is desired, flash Magisk.
- Reboot to recovery, to see that it sticks
- Reboot to system
- Install Magisk apk, check root.

Sorry for late reply, was bussy getting RR GSI up and running. But sadly it was stuck in bootloop. So i flashed a room from mi-glob roombuilder. This worked so far succesfully, but the chines dialoges do not go well with me.
From my understanding, the warning from the Booloader ist just a warning. In this case may be triggered by ARB, wich means that fastboot or the BL can not guarantee that the room or recovery will work on that phone or may even brick it or is at least not from the vendor.
After you type in :
Code:
fastboot oem ignore_anti
basically this compatibillity check is disabled. After that you can flash any room or recovery you like. If you do flash an older firmware on an ARB activated device you will produce a nice paperwight. But that is another topic.
I do not know, which part (bootloader or fastboot) is responsible for the warning, as i am a total noob regarding flashing android devices.

[STOCK][FASTBOOT] Fastboot Flashable Images For OnePlus 7T

Disclaimer :
Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Your warranty will be void if you tamper with any part of your device / software.
Download :
OnePlus7TOxygen_14.I.05_OTA_fastboot
Code:
ro.vendor.build.date=Wed Sep 25 21:54:29 CST 2019
ro.vendor.build.date.utc=1569419669
ro.vendor.build.fingerprint=OnePlus/OnePlus7T/OnePlus7T:10/QKQ1.190716.003/1909250940:user/release-keys
ro.vendor.build.id=QKQ1.190716.003
ro.vendor.build.tags=release-keys
ro.vendor.build.type=user
ro.vendor.build.version.incremental=1909250940
ro.vendor.build.version.release=10
ro.vendor.build.version.sdk=29
ro.product.vendor.brand=OnePlus
ro.product.vendor.device=OnePlus7T
ro.product.vendor.manufacturer=OnePlus
ro.product.vendor.name=OnePlus7T
Fastboot Commands :
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash logo_a logo.img
fastboot flash logo_b logo.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
Credits :
jamflux
Regards,
acervenky

reserved

Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.

RohanAJoshi said:
Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.
Click to expand...
Click to collapse
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky

acervenky said:
Download the attachment, and flash it using this command :
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
OK, I will try this and report you back soon.

acervenky said:
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b

RohanAJoshi said:
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b
Click to expand...
Click to collapse
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky

acervenky said:
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky
Click to expand...
Click to collapse
which file should i dowload ?
stock or mod ?

RohanAJoshi said:
which file should i dowload ?
stock or mod ?
Click to expand...
Click to collapse
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky

acervenky said:
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky
Click to expand...
Click to collapse
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.

RohanAJoshi said:
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.
Click to expand...
Click to collapse
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?

How2Kritin said:
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?
Click to expand...
Click to collapse
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"

cultofluna said:
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"
Click to expand...
Click to collapse
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky

acervenky said:
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky
Click to expand...
Click to collapse
I did, initially but it said that the /system, /vendor and /product partitions couldn’t be mounted. When I tried to restore I got stuck in the fastboot mode. After that, I’ve used your file and got stuck with the qualcomm crashdump mode.

FIXED
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!

I wonder, if a T-Mobile 7T is unlocked can we use this method to install the international firmware on it?

Is this for EU Model?

Hot-Proton said:
Is this for EU Model?
Click to expand...
Click to collapse
No, Global!
Regards,
acervenky

Ok that is bad. Wait for EU Version.

for T-Mobile no, I messed up mine, it boots but no wifi and data. I did a remote session with oneplus but they can't fix it, they don't have the firmware for the tmobile version, unless if someone has already patched the MSM, but sadly nothing yet
---------- Post added at 07:50 AM ---------- Previous post was at 07:48 AM ----------
How2Kritin said:
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!
Click to expand...
Click to collapse
how did you reach out to him, just wanna know if there's a fix for my wifi and data no connections, T-Mobile unlock bootloader, tried flashing the modem from here but no effect and when I tried deleting it, sim card cannot be detected

Development [RECOVERY][OFFICIAL] TWRP for ASUS ROG Phone 6/6 Pro (Qualcomm ONLY)

Official TWRP is now available: https://twrp.me/asus/rogphone6.html
IMPORTANT NOTES:
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2201

It doesn't work! Either flashing or just booting via fastboot gives an error message. Tried to install twrp app...it crashes all the time, couldn't even flash the zip...
I also had to reflash the raw because the phone was stuck in bootloader mode.

I can't flash the img either. I'm on tencent version, is it the difference?
Code:
fastboot flash recovery_a twrp.img
Sending 'recovery_a' (102400 KB) OKAY [ 2.319s]
Writing 'recovery_a' FAILED (remote: 'Flashing non-hlos image is not allowed in lock state')
fastboot: error: Command failed

minazukix said:
I can't flash the img either. I'm on tencent version, is it the difference?
Code:
fastboot flash recovery_a twrp.img
Sending 'recovery_a' (102400 KB) OKAY [ 2.319s]
Writing 'recovery_a' FAILED (remote: 'Flashing non-hlos image is not allowed in lock state')
fastboot: error: Command failed
Click to expand...
Click to collapse
The message seems to indicate that your device bootloader isn't unlocked...

Captain_Throwback said:
The message seems to indicate that your device bootloader isn't unlocked...
Click to expand...
Click to collapse
I have unlocked the bootloader already.
I can flash to WW by flashall_AFT.cmd, like here https://androplus.org/en/entry/rog-phone-6-china-to-global-conversion/

minazukix said:
I have unlocked the bootloader already.
I can flash to WW by flashall_AFT.cmd, like here https://androplus.org/en/entry/rog-phone-6-china-to-global-conversion/
Click to expand...
Click to collapse
Flashing RAW doesn't require an unlocked bootloader.
I'm just telling you what the message from the bootloader is saying. I don't control that, sorry.

Captain_Throwback said:
Flashing RAW doesn't require an unlocked bootloader.
I'm just telling you what the message from the bootloader is saying. I don't control that, sorry.
Click to expand...
Click to collapse
I've already unlocked my phone with the official unlock device app.
I have the boot loader is unlocked warning screen when my phone power on.
Also, I can flash the patched boot.img to get root.
Code:
fastboot flash boot magisk_patched-25200-boot.img
Sending 'boot_a' (98304 KB) OKAY [ 0.301s]
Writing 'boot_a' OKAY [ 0.240s]
I think my bootloader should be unlocked.

minazukix said:
I've already unlocked my phone with the official unlock device app.
I have the boot loader is unlocked warning screen when my phone power on.
Also, I can flash the patched boot.img to get root.
Code:
fastboot flash boot magisk_patched-25200-boot.img
Sending 'boot_a' (98304 KB) OKAY [ 0.301s]
Writing 'boot_a' OKAY [ 0.240s]
I think my bootloader should be unlocked.
Click to expand...
Click to collapse
Then try just
Code:
fastboot flash recovery twrp.img
without the slot suffix and see if that works. That'll just flash TWRP to the active slot.

Just read carefully on the page that you've downloaded the twrp.img. I saw a short brief guide on how to flash TWRP recovery as below: (using termux or any terminal on your phone)
1. Copy downloaded file and Place it in the root of your /sdcard folder and rename it to twrp.img.
2. Type following command on termux or any terminal (on your phone).
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_a
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_b
Ps_1: it works for me, after failed to flash via fastboot due to locked state. (my phone is rooted with Magisk)
All credit to: Captain_Throwback.
I take no credit at all.
Ps_2: your phone must rooted.

tuannghia1985 said:
Just read carefully on the page that you've downloaded the twrp.img. I saw a short brief guide on how to flash TWRP recovery as below: (using termux or any terminal on your phone)
1. Copy downloaded file and Place it in the root of your /sdcard folder and rename it to twrp.img.
2. Type following command on termux or any terminal (on your phone).
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_a
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_b
Ps_1: it works for me, after failed to flash via fastboot due to locked state. (my phone is rooted with Magisk)
All credit to: Captain_Throwback.
I take no credit at all.
Ps_2: your phone must rooted.
Click to expand...
Click to collapse
Hi! It worked, thanks a lot! The only problem is no otg support...which makes flashing a bit a pain in the... Now I'm experimenting. I've had issues with voice typing and Android Auto, so through TWRP I'm trying to fix them.

fux1976 said:
Hi! It worked, thanks a lot! The only problem is no otg support...which makes flashing a bit a pain in the... Now I'm experimenting. I've had issues with voice typing and Android Auto, so through TWRP I'm trying to fix them.
Click to expand...
Click to collapse
Yes, it works for me too.
You can use adb push/pull to transfer files in TWRP.

fux1976 said:
Hi! It worked, thanks a lot! The only problem is no otg support...which makes flashing a bit a pain in the... Now I'm experimenting. I've had issues with voice typing and Android Auto, so through TWRP I'm trying to fix them.
Click to expand...
Click to collapse
I'm not get any trouble with voice typing by google keyboard, not try Android auto yet? If you got trouble about Device is certified then try MagiskHide props config (magisk module) and using a verified fingerprint (mine is using fingerprint from rog phone 5). Everything is fine even google wallet.

minazukix said:
Yes, it works for me too.
You can use adb push/pull to transfer files in TWRP.
Click to expand...
Click to collapse
Thanks, that's the best option to push file directly via abd push.

tuannghia1985 said:
I'm not get any trouble with voice typing by google keyboard, not try Android auto yet? If you got trouble about Device is certified then try MagiskHide props config (magisk module) and using a verified fingerprint (mine is using fingerprint from rog phone 5). Everything is fine even google wallet.
Click to expand...
Click to collapse
I just flashed the latest raw zip(WW-AI2201-32.2810.2210.220-REL-2210-M2.13.33.24-ASUS_1.1.1-Phone-user-20221109.raw), then everything is working well (e.g. /vendor/factory/COUNTRY is already WW).
I don't use voice typing, Android auto, google pay and fingerprint either, but I just tested the fingerprint features, there is no problems. I pass safetynet and hide root by this Method 2: https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/

tuannghia1985 said:
I'm not get any trouble with voice typing by google keyboard, not try Android auto yet? If you got trouble about Device is certified then try MagiskHide props config (magisk module) and using a verified fingerprint (mine is using fingerprint from rog phone 5). Everything is fine even google wallet.
Click to expand...
Click to collapse
Everything is working fine, except these 2 features. Voice typing at first is working but after downloading my configuration (google backup) and my apps, it stops. I can live without it. I've tried several ways: no way of making it work. So I gave up..Maybe with Android 13... as everything was fine on Android 11 on my deceased Rog2. I have Magisk props (safetynet: passed, banking apps ok). But Android auto keeps crashing..Never mind. I have a spare phone to use when I'm driving.

So if you try to fastboot Boot the twrp Image you end up with a destroyed device with no return? Or do i misunderstand that?

Einheit-101 said:
So if you try to fastboot Boot the twrp Image you end up with a destroyed device with no return? Or do i misunderstand that?
Click to expand...
Click to collapse
It says unbootable, not destroyed. RAW should fix it without a problem. It's just a long road to take, including having to wipe the device, for not following a simple instruction.

Hi guys, I want to flash this but I have 2 quick questions:
1. Can I FOTA after install TWRP ?
2. Do I need to reflash it every FOTA ?

fux1976 said:
It doesn't work! Either flashing or just booting via fastboot gives an error message. Tried to install twrp app...it crashes all the time, couldn't even flash the zip...
I also had to reflash the raw because the phone was stuck in bootloader mode.
Click to expand...
Click to collapse
hi how to reflash raw rom , i cant run flashh aft my phone stuck stock recovery help

Captain_Throwback said:
It says unbootable, not destroyed. RAW should fix it without a problem. It's just a long road to take, including having to wipe the device, for not following a simple instruction.
Click to expand...
Click to collapse
how to flash raw ? my laptop cant run flash all AFT pls help

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