Question How do I install ArrowOS 13.1 - Xiaomi Mi Pad 5 Pro

Hi All,
I'm trying to install ArrowOS13.1 on my Mipad 5 Pro without sucess and wondered if anyone had been sucessful?
I tried some stesp I found here https://forum.xda-developers.com/t/arrowos-v13-1-mi-pad-5-pro-12-4-dagu-step-to-install.4579335/ but just up to the flashing the payload file as I don't think the vendor boot etc are required since I think those steps were to get the elish rom working on a dagu device.
From the start it didn't go well. I had the Lynnrin rom on originally. When I went to flash 13.1 it worked, but although I had the vanlla version the tablet had gapps on it, Doh, I need to wipe the data partition. So I did that with XiaomiToolv2 (i think it was a few days ago), but after that no booting at all. Damn, ok lets recover with XiaominToolv2, i've done that before sucessfully. That failed becuase because no matter what I could not get into fastbootd mode. But i eventually got the machine flashed by using the flash_all.bat file in the stock rom from XiaomiToolv2 by using an updated fastboot and shortening the file path to the rom. What I didn't realise at the time was thatit was now a different version of the rom (MIUI 14 now)
So great I've got stock back. Now I try to flash the payload filefor 13.1 which flashes, but won't boot. I tried swapping slots for booting but that didn't help.
Has getting it on MIUI 14 locked me out?
I don't want to flash back to MIUI 13 stock as I've heard XIAOMI has an anti rollback thing in place that bricks devices (but I think but not willing to bet, that this doesn't have anti rollback)
Thanks

Hey crass00,
If you're still wondering on how to install Arrow 13.1 on elish, I think you can just follow Lynnrin's past instructions on installing Arrow 12. Copy-pasted below (credit to Lynnrin, modified for clarity, link replaced with the new one you posted in another thread):
Spoiler: Install Custom ROM on Mi Pad 5 Pro (elish)
1. Unlock bootloader
2. Reboot to fastboot
3. Flash MIUI Recovery by this command fastboot flash boot miui_recovery.img
4. Reboot to recovery by this command fastboot reboot recovery, and format data on MIUI Recovery
5. Hold power button + volume down, when screen off, release power button, release all button when it get in bootloader.
6. Flash AOSP recovery by this command fastboot flash boot aosp_recovery.img
7. Reboot to recovery by this command fastboot reboot recovery
8. Enter to sideload mode by this command adb reboot sideload-auto-reboot
9. Sideload zip by this command adb sideload ***.zip (change ***.zip to the Arrow13.1 ROM zip file, in my case I used Arrow-v13.1-elish-OFFICIAL-20230426-GAPPS.zip)
10. Once that custom ROM installed on your Pad.
p.s. on number 9, when sideloading the ROM, the percentage progress seems to be stuck at 47% for a long time for me, don't panic and just leave it for a few minutes, it will magically finish the process and reboot the tab automatically.
I don't think there's any need to flash back to MIUI 13 as I've also made the mistake of flashing it to MIUI 14 first, and there doesn't seem to be any problems so far.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Super that worked. Many thanks.
I actually tried this way last night but failed at the step to delete data. I don't read chinese so couldn't delete data, figured I'd just wiped the device fully with a MIUI restore anyway so whats the need and moved on. That was a mistake With the confirmation it works i installed google translate on my phone to find my way though the menu.
I hope now once an update comes out the data delete step isn't required. That could get annoying if it is

Yeah, I'm wondering about that too actually.
My assumption is that the aosp_recovery.img is already installed as the recovery, so maybe we could just start from step 7?
I'm completely unsure though.
For other devices that I used usually there's a working TWRP recovery and I could just do flashing/updating through TWRP.
At least there doesn't seem to be any major bugs for this Arrow 13.1 build for elish (dagu in the other thread has camera problem).

What's wrong with the official instructions from the maintainer?
Instructions thread for (elish) MiPad 5 Pro on ArrowOS - HackMD
# Instructions thread for (elish) MiPad 5 Pro on ArrowOS This blog post is dedicated to [Xiaomi Pad
hackmd.io

Didn't notice it

i can verify this device does not have anti-rollback
I once went from android 12 to android 11
and from android 13 to android 12
so it should be just fine
it's just that sometimes miflash showed an error after flashing

I succesfully flashed this on enuma after 2 attempts using Lynnrin's past instructions but with the newer build
first attempt was with miui 13 (Android 12) but it automatically stopped at 47% and rebooted so it didn't fully flash arrow
for my second attempt I first flashed miui 14 (android 13) and then did the same process again but this time it worked just fine
I guess the logic is that you have to be on the android version you want to flash
camera works (on dagu it doesn't for some reason)
and the xiaomi smart pen also works
edit: is it just me or does the wifi feel slower?

niveZz said:
I succesfully flashed this on enuma after 2 attempts using Lynnrin's past instructions but with the newer build
first attempt was with miui 13 (Android 12) but it automatically stopped at 47% and rebooted so it didn't fully flash arrow
for my second attempt I first flashed miui 14 (android 13) and then did the same process again but this time it worked just fine
I guess the logic is that you have to be on the android version you want to flash
camera works (on dagu it doesn't for some reason)
and the xiaomi smart pen also works
edit: is it just me or does the wifi feel slower?
Click to expand...
Click to collapse
All process being run by AOSP recovery will stop at 47%. But you will be noticed by a line of message saying successfully or not.
In my case, I flashed MIUI Android 12 and using A13 GSI ROM. Everything works fine except the GSI ROMs do not support Xiaomi peripherals.

How do I install Magisk using this rom?
I tried following this but then devices wont boot up again

Related

Magisk Root without custom Recovery and without losing Encryption

So, I unlocked my bootloader a couple of days ago, but when I got into the point of flashing TWRP, I realized that there is no custom recovery that supports device encryption.
For that reason I didn't root my phone but there is a way around that.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
1. Download the latest Magisk Manager from here and install it.
2. Download latest ROM from here and depending on your device.
3. Extract boot.img file from the ROM .zip file and copy it to phones internal storage.
4. Open Magisk Manager and go to settings. Select the Beta channel (stable did not work for me).
5. Go to home and select install magisk. Select patch boot image, and select the boot.img that we extracted earlier. Now a new file patched_boot.img will be created. Copy it to your PC.
6. Boot device into fastboot.
7. Execute fastboot flash boot /path/to/patched_boot.img .
8. Reboot device and you are rooted
All credits go to Magisk. I shared this, only because there are no such relevant information in this sub forum
But now we have 10.2.17 and no download link. Tomorrow I can unlock my bootloader. Would it also work, if I download and modify the boot.img from 10.2.15?
Sent from my [device_name] using XDA-Developers Legacy app
Many thanks, but I'm on 10.2.17. Could you kindly provide the patched boot img file?
You can download the whole ROM here:
http://bigota.d.miui.com/V10.2.17.0...AGlobal_V10.2.17.0.PFAEUXM_53263ccd41_9.0.zip
Sent from my MI 9 using Tapatalk
*delete*
radii said:
Many thanks, but I'm on 10.2.17. Could you kindly provide the patched boot img file?
Click to expand...
Click to collapse
Got it working.
I have the 10.2.17 prepatchedboot.img. XDA does not allow me to attach to this post. If anyone can suggest easy (ie without setting up account) method of upload can do so
Ok got it, will give it a try.
radii said:
Got it working.
I have the 10.2.17 prepatchedboot.img. XDA does not allow me to attach to this post. If anyone can suggest easy (ie without setting up account) method of upload can do so
Click to expand...
Click to collapse
i need it , can you upload to dropbox? thanks.
The boot.img is in the Link from Captus.
Sure send username and password
radii said:
Got it working.
I have the 10.2.17 prepatchedboot.img. XDA does not allow me to attach to this post. If anyone can suggest easy (ie without setting up account) method of upload can do so
Click to expand...
Click to collapse
I tried with the latest boot.img but no luck. It stuck in fastboot screen so I had to flash the original one! I will give it another try though!
Edit:
Success. I patched the image again and it worked, I do not know what was the problem the first time.
WOUAHOUU ! it work very fine ! I routed my Mi9 (global original stock rom) in 15 seconds without changing recovery and without putting TWRP .. the top !
I wonder why this tutorial is not in the first position of the root procedure.
With this procedure, are the updates always done by OTA or does it need a new way?
up ? because global rom just changed for 10.2.22 with a ota update. How can we do ?
Strange. My global rom is 10.2.9.0
So, this method gives full root acces? Like any other, more complicated, method? Any limitations?
Btw, what cpu governors does the default kernel support? Can they be changed with a Kernel Manager (Adiutor etc) after this root method?
So, full root : I think that yes.. all my apks that require root work perfectly. It 'seems that there is non limitation.
but, I answer my own question: As with a modified recovery, the OTA no longer work either when it's a fix. But OTA work perfectly when it'a a full update.
SO ! This is the link for Global ROM 10.2.22 : https://bigota.d.miui.com/V10.2.22....AGlobal_V10.2.22.0.PFAEUXM_745a374eee_9.0.zip
Tuto to do full update and root :
We launch the update ota normally.
the phone reboots and announces that the update can not be done in this version.
Phone reboots normaly. You restart the OTA update : Phone then launches automatically a FULL update version 10.2.22
On the PC, We download the global rom and extract the boot.img
Then we use magisk to modify boot.img as in post nbr 1 page 1 and use adb for flashing the modified boot.img
Rooted !
No luck with global rom is 10.2.9.0
tried patching multiple times using beta and stable.
roll back to boot.img original.
Hi guys,
just got my brand-new Mi 9 a few days ago and rooting it drives me nuts.
I have rooted many devices but here my problem:
After using TWRP and Magisk, the system fails to boot, always goes into TWRP.
Then I used the method described here, the system fails to boot and goes into MI-Recovery.
When I flash back the original boot.img, the device boots fine.
Can anyone please help?
Thanks
Robert
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ChingghisKhan said:
Hi guys,
just got my brand-new Mi 9 a few days ago and rooting it drives me nuts.
I have rooted many devices but here my problem:
After using TWRP and Magisk, the system fails to boot, always goes into TWRP.
Then I used the method described here, the system fails to boot and goes into MI-Recovery.
When I flash back the original boot.img, the device boots fine.
Can anyone please help?
Thanks
Robert
Click to expand...
Click to collapse
Always flash ROM and fully boot into ROM first.
Then reboot after setup back in to TWRP and only then flash Magisk.
Flashing ROM + Magisk is fine with AOSP/Lineage etc. but MIUI ROMs always fail to boot if you install Magisk at the same time as an MIUI ROM
ChingghisKhan said:
Hi guys,
just got my brand-new Mi 9 a few days ago and rooting it drives me nuts.
I have rooted many devices but here my problem:
After using TWRP and Magisk, the system fails to boot, always goes into TWRP.
Then I used the method described here, the system fails to boot and goes into MI-Recovery.
When I flash back the original boot.img, the device boots fine.
Can anyone please help?
Thanks
Robert
Click to expand...
Click to collapse
Try to use the beta channel of magisk. It will probably do the trick!

[CLOSED][UNOFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 6.1 | Plate2 |

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
1 . Download twrp-3.4.0-0-PL2_sprout.img & twrp-installer-3.4.0-0-PL2_sprout.zip copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot boot twrp-3.4.0-0-PL2_sprout.img
6. now your phone will boot in to twrp
7. now copy twrp installer.zip in to your phone from pc using type c usb cable
8. now flash twrp installer zip ( this will make your twrp permanent )
10. now flash magisk or what ever your wish and press reboot system
11. now if you people want to boot in to twrp? power off your phone connect to pc or charger
& wait for battery logo and press volume up and power button for 8 seconds now you will boot in to twrp
Download Android 11 Twrp-3.4.0-0 From Here
Download Android 10 Twrp-3.4.0-0 From Here
​
XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 6.1
Contributors
Raghu varma
Source Code: https://github.com/Nokia-SDM660/android_device_nokia_PL2_sprout-TWRP
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Stable Version: 3.x
Stable Release Date 2020-06-25
Created 2020-06-25
Last Updated 2020-06-25
Changelog - Thu Jun 25 12:41:03 UTC 2020
================================
* https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
Great work bro
This can work with locked bootloader ?
Is it compatible with android 9?
When you first start TWRP can you allow changes in the system ?
ativi said:
Is it compatible with android 9?
Click to expand...
Click to collapse
i think yes, cause it booted right away! and installation was successful. I am curently using aosp extended 9.0 official and it works
---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------
hizaoui said:
Great work bro
This can work with locked bootloader ?
Click to expand...
Click to collapse
No! You need to unlock your bootloader before using this.
Hi,
First thanks for your great work.
But I have a problem.
After doing a full backup and doing some testing, I restored my whole backup. The process succeeded. But I am stuck in a bootloop,my phone boots to the point, where I can see the LOS 17.1 Logo, But does not continue. Have waited for 30 minutes a few times now.
I tried the built in bootloop fix, But it does not fix my problem.
Thanks in advance
Good day every one
Well, yesterday Google released android 11 for pixel handsets.
Soon you people can expect custom roms from my hand mean while i released android 11 twrp builds and with the help of my builds we will go forward accordingly on time for future releases towards custom roms and ports.
Soon I will release road map towards beta program make sure to keep an eye on my xda profile , threads and project updates & don't forget to donate if you love my work and also make sure to hit thanks button.
TWRP Changelog
* initial android 11.0 twrp builds released
Thank you
Thanks, finally a permanent TWRP for the device. (sticking to 10, as a game I play can't handle 11 correctly)
After fastboot boot twrp-3.4.0-0-PL2_sprout.img
Sending 'boot.img' (42412 KB) OKAY [ 1.206s]
Booting OKAY [ 5.049s]
Finished. Total time: 6.466s
Im stuck on android one screen any idea why ?
Hi! I'd like to install TWRP on my Nokia6.1 2018 however whenever I reboot to download mode for whatever reason the device isn't found anymore through ADB and because of that I can't do fastboot devices as it yields nothing and when I skipped it, it just waited for a device forever. What's weird is that it is connected, even windows says that.
KappaTheCapper said:
Hi! I'd like to install TWRP on my Nokia6.1 2018 however whenever I reboot to download mode for whatever reason the device isn't found anymore through ADB and because of that I can't do fastboot devices as it yields nothing and when I skipped it, it just waited for a device forever. What's weird is that it is connected, even windows says that.
Click to expand...
Click to collapse
While phone is in fastboot mode, open device manager. Locate the unknown device and update its driver. Choose fastboot driver from existing drivers. It will install the driver and will work
KappaTheCapper said:
Hi! I'd like to install TWRP on my Nokia6.1 2018 however whenever I reboot to download mode for whatever reason the device isn't found anymore through ADB and because of that I can't do fastboot devices as it yields nothing and when I skipped it, it just waited for a device forever. What's weird is that it is connected, even windows says that.
Click to expand...
Click to collapse
While phone is in fastboot mode, open device manager. Locate the unknown device and update its driver. Choose fastboot driver from existing drivers. It will install the driver and will work
Follow this,
fastboot flash recovery (drag recovery here or insert path)
press enter, it will fail saying something about a-b slots
Then finallay do,
fastboot boot (drag recovery here or insert path)
press enter
should boot your TWRP now
dmilz said:
fastboot flash recovery (drag recovery here or insert path)
press enter, it will fail saying something about a-b slots
Then finallay do,
fastboot boot (drag recovery here or insert path)
press enter
should boot your TWRP now
Click to expand...
Click to collapse
Thanks, I had same problem and this is working. Anyway the problem is, I have to do this every time I want to TWRP. Is there any way how to fix this and be able to avoid `flash recovery` part?
edit: removed
Looks like can't decrypt with Android 11. I'm 100 % sure that password is correct. With Android 10 it worked fine.
Are there any plans for updates? Thanks.
Hello people,
I accidently flashed the twrp-3.4.0-0-PL2_sprout.img file and now I am stuck in the androidone loading screen anytime I try to boot to that file in order to flash the twrp-installer-3.4.0-0-PL2_sprout.zip file.
Also when I try to boot the recocery I am stuck in the loading screen of TWRP.
any suggestion to fix that ?
maxischr said:
Hello people,
I accidently flashed the twrp-3.4.0-0-PL2_sprout.img file and now I am stuck in the androidone loading screen anytime I try to boot to that file in order to flash the twrp-installer-3.4.0-0-PL2_sprout.zip file.
Also when I try to boot the recocery I am stuck in the loading screen of TWRP.
any suggestion to fix that ?
Click to expand...
Click to collapse
The device has 2 boot slots. Try switching with fastboot --set-active: https://www.techmesto.com/possible-fix-nokia-smartphone-stuck-on-download-mode-after-ota-update/
I cannot file the download link for the twrp installer.zip file. I have the image file but cannot find the zip file on the github download site.

Unofficial TWRP 3.4.2b Recovery for Redmi 9 (lancelot/Indian Prime) - Miui 11.

Source: https://unofficialtwrp.com/xiaomi-redmi-9-root-twrp-3-4-1/ The author wrote this: all issues fixed!
Thanks to the developer for the energy and time. Developer: wzsx150.
This is a working unofficial TWRP recovery for Redmi 9 for Miui 11. Tested on android 10, Miui Global 11.0.6 rom.
Miui 12 is work? I do not know. Everyone doesn't know. It probably won't work.
Original file: https://www.mediafire.com/file/auj2wh2lh8lzp47/3.4.2+Redmi+9+CN+EN.rar/file I modified this a bit.
What is required for installation:
Twrp img (blue) (recovery.img): Download
vbmeta_redmi9.img Download
1: Unlock bootloader
2: installed adb & fastboot drivers Download
3: Optional: Mtk usb driver Download
3a: Let the phone battery be charged to more than 50% !!!
(4: Everyone is at their own risk)
(5: Backup all data, recommended. Save idea 1, Save idea 2
6: Turn off the phone
7: Then press the volume down button + power on button to enter fastboot succes fastboot screen
8: Now connect your phone to your computer (windows emits a connection sound)
9: Open one a cmd/command line, where you downloaded the files cmd
10: Issue the two commands one after the other
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta_redmi9.img
11: You ready. Restart the phone in recovery mode
fastboot reboot recovery
12: If you did everything right, this picture will welcome you
12.a: If recovery asks you for a security pattern, enter what you use on your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
12: If you messed up something, don't worry. Someone here will help. (It can usually be restored with Adb or fastboot, which is broken)
13: A few pictures of the program
14: Four colors are available: blue, red, brown, purple.
Blue TWRP Recovery: Download
Red TWRP Recovery: Download
Braun TWRP Recovery: Download
Purple TWRP Recovery: Download
For now, only Chinese and English language are available! The other languages are being prepared. Soon. As there will be time for it.
It doesn't hurt to have these:
Qualcomm HS-USB QDLoader 9008 Driver 64-bit [Windows] Qualcomm driver
MediaTek MT65xx Preloader VCOM USB Driver [32-bit & 64-bit] Mediatek Vcom driver
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 Adb & fastboot drivers
MTK usb driver Download
SDK Platform tools Download
Google usb driver Download
Thanks for watching. If you liked my job, you can invite me for a beer.
Paypal: [email protected]
Crypto: 3FJuZGaw98oefj45AiypytaJzyATuRn7dE
Reserved
I saw this at telegram yesterday
Is this updated version?
SunuWijaya said:
I saw this at telegram yesterday
Is this updated version?
Click to expand...
Click to collapse
Where did you see that? (I don't understand) Two versions of this have been made. This is the second.
short question,what have you modified and how did you testet which things,we have no custom rom,what about backup and restore,did you testet,what about flashing zips in general and are all partitions rw?Thanx!!!!
-CALIBAN666- said:
short question,what have you modified and how did you testet which things,we have no custom rom,what about backup and restore,did you testet,what about flashing zips in general and are all partitions rw?Thanx!!!!
Click to expand...
Click to collapse
Hello. Well ... there weren't many tests available yet.
What I modified:
1: Skins / colors
2: Spelling mistakes
3: Syntax errors 2-3 pieces
What I was able to test in recovery:
1: Install zip / img: works
2: Backup and restore partition / data: works
3: Mount partitions: works
4: Wipe / advanced wipe: works
5: Reboot "all: works
6: Terminal: works
7: ADB Sideload: works
8: File manager: works
9: Settings "all works, except multilanguage.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
Other. For everyone. It also became a fifth skin. Orange / black. Download
------------------------------------------------------------------------------------------------------------------------------------------------------------------------​It's different again. For everyone. I noticed a mistake yet. I haven’t used recovery in a long time, so I didn’t notice the error. After a while, twrp recovery disappears. And the original recovery will be again. I don't understand why .... If you twrp recovery in flash fastboot mode again, you have twrp again. For a while.
Can dis twrp flash kernel?
Meggyi said:
Hello. Well ... there weren't many tests available yet.
What I modified:
1: Skins / colors
2: Spelling mistakes
3: Syntax errors 2-3 pieces
What I was able to test in recovery:
1: Install zip / img: works
2: Backup and restore partition / data: works
3: Mount partitions: works
4: Wipe / advanced wipe: works
5: Reboot "all: works
6: Terminal: works
7: ADB Sideload: works
8: File manager: works
9: Settings "all works, except multilanguage.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
Other. For everyone. It also became a fifth skin. Orange / black. Download
View attachment 5164259
------------------------------------------------------------------------------------------------------------------------------------------------------------------------​It's different again. For everyone. I noticed a mistake yet. I haven’t used recovery in a long time, so I didn’t notice the error. After a while, twrp recovery disappears. And the original recovery will be again. I don't understand why .... If you twrp recovery in flash fastboot mode again, you have twrp again. For a while.
Click to expand...
Click to collapse
Ok,big thanx for info.Cheers!!!
SunuWijaya said:
Can dis twrp flash kernel?
Click to expand...
Click to collapse
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Meggyi said:
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Click to expand...
Click to collapse
Just try to flash stock kernel
Afaik the issue with the missing twrp recovery is normal and only on miui based rom,on custom roms there is no issue like that.Most Xiaomi/Redmi devices do that.
Meggyi said:
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Click to expand...
Click to collapse
Yes it is have custom kernel named Minati-Xenodrome
How to use twrp to flash GSI ?
-CALIBAN666- said:
Afaik the issue with the missing twrp recovery is normal and only on miui based rom,on custom roms there is no issue like that.Most Xiaomi/Redmi devices do that.
Click to expand...
Click to collapse
Yeah, I get it. I didn’t have many phones that miui had. That makes sense. Stupid miui
Good job....I flash custom kernal...and it successful...but can this twrp able to go fastbootd as you mentioned and flash gsi like stock recovery?
Have you flashed a rom?
The solution for the issue that twrp is gone after some times is to flash the no-verity-opt-encrypt file for the device directly after flash of recovery,after this twrp is permanent,for the file check source link in first post.Cheers!!!!
Thank you very much, but my Redmi 9 China version cannot boot after flashing into twrp.
On Redmi 9 China version, I sorted out this version to be available.It seems that it can only be used for MIUI11
zhihuiyuze channel
论坛附件,Redmi9 twrp且可以在中国版使用
t.me
Google Drive Education Edition cannot share files (so use Telegram
There is another problem. It seems that if I use your modified version, /cust fails.
What we can do with this TWRP on lancelot?
I have the Redmi 9 (lancelot) with MIUI 11 installed. My bootloader is unlocked, I've the adb & fastboot drivers installed. I would really like to install that TWRP. While I'm flashing both files, cmd gives no errors, everything is fine. But at the end, I can not boot into recovery with "fastboot reboot recovery" from the cmd, it gives me an error. If I leave fastboot mode and try to enter TWRP manually by holding the volume and power key, it doesn't work. My device will get stuck inside a bootloop.
I'm able to fix the bootloop with disabling DAA & SLA protection in the MTK mode and flashing back the stock firmware with SP Flashtool. I tried it 3 times, every time the same issue and having to flash back the stock firmware. Do you have any tips to fix that? Or is there another or updated version I could try?
Edit: Nvm, got it working

Moto E6S XT-2053-1 Unlock Bootloader, Disable Verity, ROOT Magisk, TWRP

I am perfom this Sorry for my english, I am from Ukraine
Download archive!
We unpack. Install the adb and mtk preloader drivers, if they are not installed, restart the computer.
In the smart, turn on the developers menu, in it - "Allow OEM unlock" and "USB debugging" and connect the smart to the computer.
We drop valuable photo data from the smart to the computer for any, and, without disconnecting the smart from the PC, run the script (with the phone connected to the PC and loaded into the android phone. Reboot_to_fastboot_getvar current-slot.bat (not from the admin, just click twice).
Smart will look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
we allow - put a daw, ok. We are waiting for the smart to reboot into fastboot, when the barcode appears on the smart screen, before that we do not press anything in the script
I did the scripts step by step, after each operation in the script window, press enter to continue, and so on until each script is closed
We look at our current slot in the window and remember the letter - a or b:
In the script, press enter so that the smart reboots and the script closes.
Run flash_tool.exe, go to this tab and check the boxes, as in the screenshot:
So we consider the necessary versions of orig. files, so as not to download and sew a specific firmware version for this instruction.
(And best of all, all the checkboxes, except for system, vendor, userdata - they are not critical, if they are not removed, it will take up a lot of space on the computer up to +74 gb, but I did not put these checkboxes, there must be some risk and passion )
We press "Read Back" and only then we connect the switched off smart to the PC, we wait, at the end we disconnect the bodies, do not touch it: sveta:
Go to this tab, remove all checkboxes! And we only put on lk_ with the letter of a non-your slot that we looked at, for example, you had slot "a" - so we put a check on lk_b and vice versa :
Click "Download" and connect the switched off smart to the PC (it was already turned off: sveta
As it flashes, we close the USB flash drive window, disconnect and turn on the smart, after loading, we connect it to the PC again, we already run the script
Unlock_Moto_E6S.bat, wait until the body reboots into a fastboot (to the barcode on the screen) and only then press the input step by step to continue in the script until it is completely closed.
Everything, the bodies are unlocked. Now you can get an excellent and fast root from Magisk, try other firmware, unsubscribe which one is buggy, which one flies. I haven't tried yet. Now I will write how to flash orig. kernel with magisk root (attached magisk boot for xt2053-1 4/64 fw RETEU 288-60-6-29 https://mirrors.lolinet.com/firmware/moto/fiji/official/RETEU/
Additionally, there is a script in the folder to delete the message when loading that the bootloader is unlocked, it does not interfere much, but I deleted it. Since this is not important, I separated it from the main script, since I did not test it on different versions of the firmware, in theory it should work on all versions, you can try after unlock. Or throw off ROM_45 from your firmware, I'll remove it from it. I now have the latest firmware flashed, it is on the server, but for some reason it did not fly through the air. If you flash it, then you can safely delete the message from the bootloader with my script, there is a file from it)
I am flash in slot_b Android 12 GSI, work. And i have in slot_a original system
severagent007 said:
I am flash in slot_b Android 12 GSI, work. And i have in slot_a original system
Click to expand...
Click to collapse
dude!! followed all your steps and i now have a bootloader unlocked and rooted device. how did you figure out the lk and signature to unlock that??
proof attached below
Слава Украине!!!
can the mods move this to the moto e6s forum so we can spread the news?
luridphantom said:
can the mods move this to the moto e6s forum so we can spread the news?
Click to expand...
Click to collapse
I took the first firmware I got to try from here: https://4pda.to/forum/index.php?showtopic=892755
but the firmware itself is everywhere, for example here:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
DeveloperLuke Roms - Browse /GSIs at SourceForge.net
sourceforge.net
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You can try to sew any GSI arm64 a/b from anywhere you find and choose the one you like, because smart supports Project Treble.
If you like one and will look cool and work firmware, post links here!
Tested it and it worked! Thanks a lot!
Now looking for delevoping some roms to this device
Im having a little problem, i tried to flash a GSI with "fastboot -u flash system gsi.img", the device didn't boot. Then i tried to flash the stock with the SP Flash Tool, and i throws an error (status_sec_dl_ forbidden), then i flashed it with Lenovo Rescue and Smart Assistant. I tried to flash via fastboot the patched magisk image but it throws an signature error.
Any help? Tha device still says that is unlocked
refrigerador67 said:
Im having a little problem, i tried to flash a GSI with "fastboot -u flash system gsi.img", the device didn't boot. Then i tried to flash the stock with the SP Flash Tool, and i throws an error (status_sec_dl_ forbidden), then i flashed it with Lenovo Rescue and Smart Assistant. I tried to flash via fastboot the patched magisk image but it throws an signature error.
Any help? Tha device still says that is unlocked
Click to expand...
Click to collapse
did you use the auth file that comes with sp flash tool? without that your device wont boot properly
Yes, i used the correct download agent and auth file
interesting, i followed all his steps and had no problem rooting it. try backtracking with his scripts again?
Solved it, also me and a developer are working on a new, more simple and automated script. Still haven't figured out how to flash the lk via script.
When is done i will post a complete guide in the moto e6s forums on how to do it, i think it might work well, but i would have to test in a non-unlocked device
Can someone please make a video with explanation, I didn't understand very well what is done, so I won't touch anything, but I thank those who record a video explaining it to me (I'm Brazilian)
Here you have a more straight forward guide, note that is still in testing
[GUIDE] How to unlock bootloader on E6s
Hello, in this guide i will show you how to unlock the bootloader on Moto E6s ;) (Sadly for now this guide is Windows only) CAUTION You are doing this AT YOUR OWN RISK! I will NOT take responsibility if you brick your device! Also, remember to...
forum.xda-developers.com
Excuse my ignorance, do you think it is compatible for the XT2053-5 model?
cannot use fastboot flash boot magiskboot.img
sign failed
partition flash is not allowed
hey is the moto e6+ twrp work on e6s

General [SHARED] Pixel Experience 12 Renoir | OFFICIAL | Android 12 | Updated: 2022/04/26

Im just sharing, im currently testing Plus version.​
Pixel Experience 12 Renoir | OFFICIAL | Android 12 | Updated: 20220715
Instructions here and summary:
Unlock bootloader
Stock MIUI MANDATORY:
Included 13.0.4.0 firmware, so you don't need to flash it manually
(According to Xiaomi, all the fastboot roms are safe to upgrade and downgrade with xiaomi flash or console flash, also, if the rom dont have de fastboot file [e.g. fastboot.exe], you must to get it, maybe with sdk platform tools)
Into Fastboot (adb reboot fastboot or power off / reboot and press power + vol -)
fastboot flash vendor_boot this.img
fastboot flash boot recovery_file_from_rom_url.img
fastboot reboot recovery
Factory Reset, then Format data / factory reset
Return to Main and Apply update > ADB sideload
from pc terminal: adb sideload rom.zip
Back arrow in the top left of the screen, then “Reboot system now”
Enjoy
Latest build​July 15, 2022 19:44
Maintainers​Patryk Zimnicki
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any idea why do we need to use the provided vendor_boot image? Since i have used the rom just flashing the system partition.
razor_1911 said:
Any idea why do we need to use the provided vendor_boot image? Since i have used the rom just flashing the system partition.
Click to expand...
Click to collapse
From the wiki
Warning: This platform requires the vendor boot partition to be flashed for recovery to work properly, the process to do so is described below.
Click to expand...
Click to collapse
Installed flawlessly in a jp versión, even the original base firmware was the jp not te eu provided and the ROM works fine, I notice some upgrade on bass from the speakers, It sounds awesome, I've nevea used Pixel roms so I dunno if Is normal to miss the autobrightness icon on settings panel, battery works pretty nice, alarms, sounds, vibrations, all works fine. Thanks to the dev.
Installed flawlessly also. But unfortunately, Wi-Fi did not work. After booting up, it hangs for quite long time searching for wi-fi networks until it quits and the wi-fi slider moves to the left. I chose to use carrier data to finish setting up my renoir phone, and then tried every trick possible to get wi-fi working, to no avail.
Then flashed DotOS... same story.
Had to go back to Xiaomi.EU rom.
maralvar71 said:
Installed flawlessly also. But unfortunately, Wi-Fi did not work. After booting up, it hangs for quite long time searching for wi-fi networks until it quits and the wi-fi slider moves to the left. I chose to use carrier data to finish setting up my renoir phone, and then tried every trick possible to get wi-fi working, to no avail.
Then flashed DotOS... same story.
Had to go back to Xiaomi.EU rom.
Click to expand...
Click to collapse
You need to flash V12.5.7.0.RKIEUXM Stable firmware before installing PE.
DanielTheHam said:
You need to flash V12.5.7.0.RKIEUXM Stable firmware before installing PE.
Click to expand...
Click to collapse
Can't do. I'm on stock renoir_global_images_V13.0.4.0.SKIMIXM_20220412, Miui13. I might brick the phone because of ARB.
What is ARB?
And i have question also about Magisk is it possible to be rooted?
maralvar71 said:
Can't do. I'm on stock renoir_global_images_V13.0.4.0.SKIMIXM_20220412, Miui13. I might brick the phone because of ARB.
Click to expand...
Click to collapse
If you're worried just flash stock V12.5.7.0 and start the installation process from there.
razor_1911 said:
And i have question also about Magisk is it possible to be rooted?
Click to expand...
Click to collapse
Maybe, just install TWRP and flash magisk
Steps and Link
I am on xiaomi.eu miui 13 version right now and I can't downgrade because my ARB is 1. Stock 12.5.7.0 EEA is ARB 0. Is there any fix to change that and downgrade without bricking my phone?
------------------
Nevermind. I just edit install script file.
I was on 13.0.4 global
Unlocked bootloader
Installed 12.5.7 full stock
After that all by instructions
All went smoothly no problems
So far works fine, thanks allot
Found a bug, after a while maybe like a 5-6 days, the phones does not ring or vibrate when ringing. After a restart is the same again, probably that vendor image is broken.
How is the SoT / battery? Better than miui or similar?
Personally, I installed it 1 week ago, and at first glance, everything worked flawlessly.
I was actually amazed of how good it worked! Until..
I realised the battery was.. TERRIBLE.
The battery don't lasts a lot, and for some reason, when i don't use my phone (sleep mode + airplane mode), It uses 20-30% for.. nothing.
I'm probably going to switch to LineageOS.
razor_1911 said:
And i have question also about Magisk is it possible to be rooted?
Click to expand...
Click to collapse
It indeed can be rooted, personally to root it i used a tool to get all the .imgs of the ROM, and patch it, then reflash.
If you are scared about that, TWRP should work just fine too.
Lolo280374 said:
It indeed can be rooted, personally to root it i used a tool to get all the .imgs of the ROM, and patch it, then reflash.
If you are scared about that, TWRP should work just fine too.
Click to expand...
Click to collapse
yeah i rooted it by the provided boot image in magisk, thanks.
Lolo280374 said:
Personally, I installed it 1 week ago, and at first glance, everything worked flawlessly.
I was actually amazed of how good it worked! Until..
I realised the battery was.. TERRIBLE.
The battery don't lasts a lot, and for some reason, when i don't use my phone (sleep mode + airplane mode), It uses 20-30% for.. nothing.
I'm probably going to switch to LineageOS.
Click to expand...
Click to collapse
Same here, but I do this after flash a new rom and battery drain ok
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
I used to 13.0.4 global rom
Installation complete according to the guide
but recieved phone number is two number overlap
Had to go back to global rom

Categories

Resources