Question Need help, Can't figure out how to change my ROM - Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40

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

Related

Pixel C - fastboot unsupported command

Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !
Did you unlock your device first with "fastboot oem unlock"?
redukt said:
Did you unlock your device first with "fastboot oem unlock"?
Click to expand...
Click to collapse
Yes i did this before, i was running on Remix OS
I don't know if this is of relevance but there were new fastboot commands introduced from Android M (?) and I have recollection about "partial unlock" - two flags required to be set and if only one was set it could be reported that the bootloader was unlocked but fastboot saw it as locked. Above may be totally wrong.
Here's the difference between old and current fastboot commands. Note the new lock/unlock commands
Code:
************************ OLD **************************************
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
************************ NEW **************************************
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.
-Yazh- said:
Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !
Click to expand...
Click to collapse
Hi, I'm just wondering if you were able to fix your tablet. I ran into the same problem as you here and am not able to find a solution to it.
Hi !!
Sorry for bad news, but i didn't found any solution since my Pixel C was bricked. Maybe there is a solution, but I dropped it before finding it.
I hope you find something to fix it !
@viii_xvi Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html
peterk-1 said:
Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
Click to expand...
Click to collapse
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
peterk-1 said:
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?
viii_xvi said:
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?
Click to expand...
Click to collapse
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.
peterk-1 said:
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.
Click to expand...
Click to collapse
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
fastboot: usage: no command
Click to expand...
Click to collapse
viii_xvi said:
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
Click to expand...
Click to collapse
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.
rhmanoa said:
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.
Click to expand...
Click to collapse
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.
viii_xvi said:
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.
Click to expand...
Click to collapse
Just bought today, same issue, have you solved it?
mansonstein said:
Just bought today, same issue, have you solved it?
Click to expand...
Click to collapse
No, I didn't manage to fix it.
did you found a solution yet?
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command
richardwia said:
did you found a solution yet?
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command
Click to expand...
Click to collapse
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.
viii_xvi said:
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.
Click to expand...
Click to collapse
really?where I can find the“fix fastboot in advanced options”?
richardwia said:
really?where I can find the“fix fastboot in advanced options”?
Click to expand...
Click to collapse
I believe I'm not qualified to help you as I disposed of my tablet months ago. All the advice I've given is off of memory and may not be accurate. That being said, I won't help you anymore in fear of giving inaccurate information that may lead to bricking of your tablet.
I have a pixel C, flashed with latest 3-rd pixel experience before, someday i tried to flash back to factory image, hit the same trouble like this topic, i came here several times before, no solution, today, i found another article about this , it's solved my trouble.
sorry i am new here, i couldn't share the outside article link.
would like to share what i did on my pixel c.
1. root your pixel c
2. adb shell //this command could be executed under recovery mode too.
3. su
4. fwtool vbnv write dev_boot_fastboot_full_cap 1
5. adb reboot fastboot
then you could flash anything you want.
I had this just now - I finally got fed up of my Pixel C being so laggy and also chrome opening up as blank pages (I switched to brace to fix this, but it's abit crashy).
Anyhow I found that after
adb reboot bootloader
that
fastboot flash recovery twrp.img
was failing for me in the "Writing" stage
I discovered that the fix was to use
adb flashing unlock
then it will ask you a question (power button to confirm and one of teh volume keys to cancel).
after this it spins with erasing for a while and then comes back to fastboot after which
fastboot flash recovery twrp.img
Worked, after this you get an annoying 30s delay for each restart, I think that can be fixed by
adb flashing lock
I'll verify this when I've finished flashing a usable ROM to my Pixel C...

[GUIDE] How to root your Asus Zenfone 6 without TWRP | Info about A/B

Hey guys and girls,
This is a bit of copy and paste for from my guide for the HTC U12+. I thought it might be helpful to people here too.
If you find mentions of the HTC U12+ please notify me and I will correct them.
I couldn´t find any guide on how to root the Asus Zenfone 6 without twrp yet, so I thought maybe it´s good to have one. It´s also useful for people who don´t like to boot/flash the recovery but want root access.
I also decided now to do a little write up about the A/B slot partition system.
General Information about the A/B slot partition system and seamless updates
Google firstly introduced seamless updates on the Pixel Phones and with it the A/B partition system.
So this means, contrary to non A/B devices, there are two copys of most partitions except userdata.
We have two system (system_a and system_b), two boot (boot_a and boot_b) and two vendor (vendor_a and vendor_b) partitions, amongst others (can be found further down in the partition list but let´s concentrate on these).
When booted in the OS, one slot is actively used and the other is "inactive".
The main advantage that emerges now is, that in case an OTA arrives the "inactive" partitions get updated, while the OS is running. That means while the actual OTA is happening you can use your phone just like you always do.
The following reboot will boot into the former "inactive" slot and use the seamless updated partitions. This happens seamless and just with a reboot. So OTAs are much faster!
If you are interested further here are some links:
https://www.xda-developers.com/list-android-devices-seamless-updates/
https://source.android.com/devices/tech/ota/ab/
https://source.android.com/devices/tech/ota/ab/ab_faqs
Here’s another writeup from the XDA portal!
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
But here are a few tips and tricks:
How to reboot to bootloader to be able to use fastboot:
From booted OS with buttons: Press and hold power down until the screen goes black, then press and hold power and vol up to enter bootloader
non responding and the phone isn´t booting: press and hold power plus volume up to enter bootloader
From the OS or recovery via ADB (requires USB Debugging enabled in dev options):
Code:
adb reboot bootloader
How to get the active slot:
Code:
fastboot getvar current-slot
How to set the active slot:
A word of advice. If you don´t know what you´re doing you should probably not change slots. Because my U12+ only has a working A Slot. The B slot is without the first OTA or flashing a RUU unbootable.
Set active slot to a:
Code:
fastboot --set-active=a
Set active slot to b:
Code:
fastboot --set-active=b
How to extract the boot.img from a firmware.zip
1. Download the firmware zip from here : https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
2. Follow the steps described here: https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
3. Obtain your boot.img
How to root your phone without TWRP
Prerequisites:
- unlocked bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries (can always be found here
- working adb and fastboot environment
- magisk-patched boot.img
How to:
1. Download the latest magisk manager from here and install it on your phone: https://github.com/topjohnwu/MagiskManager/releases
2. Get a boot.img that fits your current firmware. Look at the point above, how to extract it from an Asus firmware zip.
Important: if you decide to use a pre-patched boot.img (available below), download it and place it in your fastboot folder, then skip to step 11!
3. Copy the extracted boot.img to your phone
4. Open the magisk manager app and tap two times on install
5. Now choose patch boot.img file and select the previously extracted boot.img you copied to your phone in the upcoming file chooser
6. Wait for the boot.img to be patched
7. Now connect your phone to your pc and make sure usb debugging is enabled in developer options
8. Open up a terminal in your fastboot folder and make sure adb is working by typing
Code:
adb devices
into terminal which should return your serial number
9. Pull the patches boot.img to your fastboot folder via:
Code:
adb pull /sdcard/Download/magisk_patched.img
10. Reboot to bootloader:
Code:
adb reboot bootloader
11. Flash the magisk patched boot.img:
Code:
fastboot flash boot magisk_patched.img
12. Congratulations you´re now rooted.
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609
Is it possible to do this and still get OTA updates from ASUS?
sidamos77 said:
Is it possible to do this and still get OTA updates from ASUS?
Click to expand...
Click to collapse
You need to unlock the bootloader for this which will prevent you from getting ota updates automatically from asus. But you can install updates manually.
Ok, great, thank you.
Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.
Any way to unofficially unlock the Bootloader?
vasra said:
Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.
Click to expand...
Click to collapse
In Europe unlocking the bootloader and rooting doesn't legally void warranty. It was ruled this way a few years ago.
Freak07 said:
[...]
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609
Click to expand...
Click to collapse
The folder WW_PHONE-16.1210.1904.75-0 which is the firmware my device has, is empty. Do you still have the prepatched boot.img of that version ? ASUS doesn't have that version for download anymore.
Thanks in advance.
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
GRöder said:
how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-26#post-2433773
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-37#post-2442236
Use Translator.
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
the getvar command returns the following output:
Do you have any advice for me ?
Edit:
After being curious and trying which worked, I tried to flash it at the active slot b explicitly: which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.
Freak07 said:
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.
Click to expand...
Click to collapse
That might have been the the point. In fact, I did download them, but I used (definately outdated, because on my pc since literally years) a minimal adb and fastboot installation.
I didn't think about it, as this is my first A/B device.
I won't try it now with the latest ones, because it worked and I don't want to destroy something (since we still dont have a working TWRP for backup & recovery) but I guess you're right, and the problem were the outdated binaries.
Thank you.
GRöder said:
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.
isthisadagger said:
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.
Click to expand...
Click to collapse
In fact, I tried that before I tried the stock-recovery-method (found it at the ASUS FAQ-pages), but it didn't work, even after a reboot, no notification showed up.
GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks
Ya how do we unlock the bootloader without asus knowing it
MirkoMirko9 said:
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks
Click to expand...
Click to collapse
nikhil18 said:
Ya how do we unlock the bootloader without asus knowing it
Click to expand...
Click to collapse
I used the official app, while the device was connected to the internet. So yes, ASUS knows that I unlocked the device.
The device was still at the -75 firmware, when I did it.
 @MirkoMirko9 If you can live with asus knowing that you unlocked the device, try it again with active internet connection.
As far as I know, there is no other method yet.
unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?
QuazIqbal said:
unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=79817571&postcount=31
magisk_patched boot.img for .156 firmware is uploaded to the patched boot.imgs folder

Question [Solved] Stuck in fastboot with locked bootloader

HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
ClementNerma said:
HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
Click to expand...
Click to collapse
please , i want to know , how can i give fastboot on my redmi7 device
H R Habib said:
please , i want to know , how can i give fastboot on my redmi7 device
Click to expand...
Click to collapse
This is a forum dedicated to the Poco F3 so I think you should ask it on the Redmi 7's forum
Use MiFlash to flash the fastboot Version of stock.
ClementNerma said:
HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
Click to expand...
Click to collapse
Don't flash recovery. Use this command instead:
Code:
fastboot boot recovery.img
and it will boot into recovery. Then you can install recovery ramdisk.
Phoost said:
Use MiFlash to flash the fastboot Version of stock.
Click to expand...
Click to collapse
I didn't find an official MiFlash tool and I don't trust closed-source tools for this kind of things.
avidduo said:
Don't flash recovery. Use this command instead:
Code:
fastboot boot recovery.img
and it will boot into recovery. Then you can install recovery ramdisk.
Click to expand...
Click to collapse
I tried that but it didn't work.
EDIT: After re-trying several times, I was finally able to make it work by booting with ArrowOS' recovery. TWRP was not accepted, but ArrowOS' one was
So I've been able to flash the Xiaomi.EU rom, I'll stick with it for now.

Question Anyone had problems rooting OOS13 final

I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
I also had issues booting the boot.img. I took the risk of flashing it and it worked.
Airwolf79 said:
I also had issues booting the boot.img. I took the risk of flashing it and it worked.
Click to expand...
Click to collapse
Using what command? Just fastboot flash boot rootedimage.img?
Kind of reticent to do that cos there's no linux MSM tool
djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
Also having that issue on the NA varient. So f-ing annoying.
djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
Go into recovery and factory reset. That happen to me once when flashing in fastboot from bootloader.
djsubterrain said:
Using what command? Just fastboot flash boot rootedimage.img?
Kind of reticent to do that cos there's no linux MSM tool
Click to expand...
Click to collapse
Yeah, I know. I'm on a Mac, so, same boat. Yes, I flashed with "fastboot flash boot boot.img", specifically renaming the patched img to boot.img. This used to be the standard way of doing it, although I realize it's safer to boot the img.
My mistake, you are trying to get root, correct?
TheGhost1951 said:
My mistake, you are trying to get root, correct?
Click to expand...
Click to collapse
Try fastboot enhanced maybe? Nope, sorry, that is for windows only I believe.
TheGhost1951 said:
Try fastboot enhanced maybe? Nope, sorry, that is for windows only I believe.
Click to expand...
Click to collapse
Being on a MAC, I really don't have a clue bud..
Actually found the linux version of MSM tool (It's really just a Qualcomm tool) so I might try flashing directly, will need to grab the appropriate MSM image just in case.
Made a guide here for anyone else in Linux but I haven't tested yet
djsubterrain said:
Actually found the linux version of MSM tool (It's really just a Qualcomm tool) so I might try flashing directly, will need to grab the appropriate MSM image just in case.
Made a guide here for anyone else in Linux but I haven't tested yet
Click to expand...
Click to collapse
Did root work?
If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.
mustangtim49 said:
If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.
Click to expand...
Click to collapse
You did actually read my post, right?
mustangtim49 said:
If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.
Click to expand...
Click to collapse
I'm still getting a bootloop
LuckyTheCoder said:
I'm still getting a bootloop
Click to expand...
Click to collapse
Of course, once it goes wrong, it stays wrong. Did you use the fastboot flash boot command? Either way, msn tool and start from scratch.
mustangtim49 said:
Of course, once it goes wrong, it stays wrong. Did you use the fastboot flash boot command? Either way, msn tool and start from scratch.
Click to expand...
Click to collapse
I did, yes. MSN tool? Like fully reset?
LuckyTheCoder said:
I did, yes. MSN tool? Like fully reset?
Click to expand...
Click to collapse
It will!
TheGhost1951 said:
It will!
Click to expand...
Click to collapse
:/
LuckyTheCoder said:
:/
Click to expand...
Click to collapse
I can't count the number of times I have started from scratch just from trying different things and crashing!
TheGhost1951 said:
I can't count the number of times I have started from scratch just from trying different things and crashing!
Click to expand...
Click to collapse
How in the world am I supposed to back it up?

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

Categories

Resources