{
"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"
}
MyUi 5.0 [] Moto G(9) Power
Android 13 Stock
Date: 02/01/2023
Build: Stock 13
Dev: @Veeronez
Changelog:
- 4Gb Ram Boost
- 30 fonts straight from Ricedroid
- Vendor r/w with multitasking optimizations and forced encryption disabled
- Fixed fingerprint
- Includes moto camera 2 with new design
- Includes root
- Moto Dolby (magisk module)
Notes
If you format it by twrp using the "yes" function, your phone will be decrypted, consequently twrp will be able to access the files in the internal memory
After the first boot go to
Settings/apps/default apps and set dialer app as default for calls
Register your fingerprint and after that use the fix fod module to remove the icon from the lock screen and fix the FM radio
bugs:
let me know if you find
Installation
check this command
fastboot getvar anti
If any value appears stop the process
In case everything is ok↓
Extract it on your computer and run the automatic installer
Download
- Gdrive -
If Motorola doesn't do it, I do
Kernel Source: Latest Stock
Veronez said:
View attachment 5825173
MyUi 5.0 [] Moto G(9) Power
Android 13 Stock
Date: 02/01/2023
Build: Stock 12
Dev: @Veeronez
Changelog:
- 4Gb Ram Boost
- 30 fonts straight from Ricedroid
- Vendor r/w with multitasking optimizations and forced encryption disabled
- Fixed fingerprint
- Includes moto camera 2 with new design
- Includes root
- Moto Dolby (magisk module)
Notes
If you format it by twrp using the "yes" function, your phone will be decrypted, consequently twrp will be able to access the files in the internal memory
After the first boot go to
Settings/apps/default apps and set dialer app as default for calls
Register your fingerprint and after that use the fix fod module to remove the icon from the lock screen and fix the FM radio
bugs:
let me know if you find
Installation
check this command
fastboot getvar anti
If any value appears stop the process
In case everything is ok↓
Extract it on your computer and run the automatic installer
Download
- Gdrive -
If Motorola doesn't do it, I do
Kernel Source: Latest stock
Click to expand...
Click to collapse
9/10 La cámara no funciona
pablo xd said:
9/10 La cámara no funciona
Click to expand...
Click to collapse
Use gcam
Veronez said:
Usar gcam
Click to expand...
Click to collapse
Excelente, es mucho mejor que MyUI 4. no tiene reinicios, con la cámara y la radio no hay problemas que hay soluciones (solo con el módulo magicks solo se corrige la huella dactilar y la radio no, no es que me afecte pero solo estoy aclarando) En realidad me gustó esta rom 10/10
Mod translation: Excellent, it is much better than MyUI 4. it does not have reboots, with the camera and the radio there are no problems that there are solutions (only with the magicks module only the fingerprint is corrected and the radio does not, it is not that it affects me but I am only clarifying) I actually liked this rom 10/10
@Veronez
do you have any tutorials?
When entering adb.exe nothing happens
I hv got bug there are 2 commands that always fails
+ fastboot erase product
Erasing 'product_a' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
+ fastboot resize-logical-partition product_a 0x0
Resizing 'product_a' FAILED (remote: '')
fastboot: error: Command failed
+ fastboot erase system
Erasing 'system_a' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
+ fastboot resize-logical-partition system_a 4000000000
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
+ fastboot erase vendor
Erasing 'vendor_a' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
fastboot erase product and fastboot erase system but the subsequent command runs.. so this doesn't show any problems until it reaches to OOTB setup.. there my touch screen is unable to work.. but all my device buttons are working
can't seem to find any solution.. tried everything.. right now i flashed my phone back to stock rom..
I think the problem has to do with " encryption setting " or something IDK..
EDIT : I m doing all this on my Arch Linux.. so i m gonna try it again on windows.. maybe from there it works
nvm found the solution... just don't flash if u have custom recovery flashed like twrp..
always flash ur recovery to oem one first, and then install..
also my fingerprint sensor is not working.. like It's not showing in security
For those who are having a hard time installing the rom, it's simple, first of all they need to have the fastboot unlocked, already having that we need to have the file already unzipped, after that we need to use the sdk platform tools, well from here everything is more easy they need to delete (those that are selected in the image) those files after that in another folder they pass the rom files after that they pass all the tools files of the sdk platform and already having the cell phone in fastboot connected to the computer they execute the file named _flash_stock_ doesn't want so much experience for installation at least that's how I installed it, I'm happy because it's very stable, it has its cons but I'm not complaining
Help!! my cmd apears "target reported max download size"
Can I use twrp for the installation?
LucasGam289 said:
Can I use twrp for the installation?
Click to expand...
Click to collapse
no, it has an automatic installer, just read above in a comment that says how to install it, it's not that complicated
luizzz gomez said:
no, it has an automatic installer, just read above in a comment that says how to install it, it's not that complicated
Click to expand...
Click to collapse
I did the automatic installation but it does not download and start the phone normally (and that I have the bootloader unlocked)
LucasGam289 said:
I did the automatic installation but it does not download and start the phone normally (and that I have the bootloader unlocked)
Click to expand...
Click to collapse
did you use sdk tools?
luizzz gomez said:
did you use sdk tools?
Click to expand...
Click to collapse
Yeah, i installed the rom twice and it sends me to the normal version of my phone :/
LucasGam289 said:
Yeah, i installed the rom twice and it sends me to the normal version of my phone :/
Click to expand...
Click to collapse
how weird. For my part I am satisfied
luizzz gomez said:
how weird. For my part I am satisfiedView attachment 5862527
Click to expand...
Click to collapse
Wouldn't it be necessary to delete the system in sdk?
LucasGam289 said:
Wouldn't it be necessary to delete the system in sdk?
Click to expand...
Click to collapse
Look, don't get so complicated, you need the platform-tools folder, well, with that you extract the rom, and there in another folder you put the platform-tools folder and then the rom and delete what says "Pablo" Then you run that installer having the cell phone in recovery mode already there connected to the cell phone with the computer or laptop via cable, you run the installer and if it doesn't start you do the same but deleting those same files selected by Pablo but those from the platform tools folder and run the automatic installer, I'm not telling you that it's like that, I don't remember well but one of those two It must be
Related
Alright, I don't really want to do this, since the rom is not finished yet but I need help and I thought that releasing it would attract developers, so here it is, the first rom for our P8 Lite (ALE-L21)
Current Status: Developer Preview
The rom is at an early development stage, since I don't have enough time to figure out how to make RIL work.
Just flash the rom if you know what you are doing, it isn't stable or functional, it's just a preview, and a waste of time if you don't know how to do things properly.
What works:
Audio
Camera
Wifi
Most apps
Some other things
What DOESN'T work:
NFC
Bluetooth (It used to work, however it's not my priority)
RIL (3G , 2G, GPRS...)
GPS (I haven't tested it but I guess it isn't working)
Playing some kind of media files
How to install it:
Wipe data/cache (factory reset) after installation
Flash boot and system.img via fastboot.
Download
Remember to backup everything before flashing, I am not responsible of Data loss, phone bricking, or whatever.
Device Source: https://github.com/XePeleato/android_device_huawei_p8lite_alel21
Kernel source: https://github.com/XePeleato/android_ALE-L21_kernel
We need some help over there, so if you want to help and are skilled in Java, drop a message.
I also want to thank everyone who helped me on Github.
I guess that's it, if anyone could move this to the development section it would be really nice.
Have a nice day!
info
any screenshots maybe? im happy that someone is working on rom for this phone
Hello...
This ROM is also compatible with model ALE-L02 and L23?
Thank y!
Hello @XePeleato that compilation must be to install?
Enviado desde mi hi6210sft mediante Tapatalk
Awesome, I've been following your development on GitHub. Very happy with your progress!
Keep it going, as soon as you get RIL working, I'll get it on my phone. Can't stand this EMUI thing.
Either way, thank you for your great work and best of luck!
I do not know exactly how I installed . Can you explain in detail ?
Did you see this HiKey board? (Google for it I still can't post links to external pages :\ ) There is full documentation about Kirin 620 and even a Android port with USB OTG support (of course source is open). May be you try to enable USB OTG?
Install ROM
Xpredator 20 said:
I do not know exactly how I installed . Can you explain in detail ?
Click to expand...
Click to collapse
For install:
1. You must be unlocked bootloader
2. Enable ADB debugging in advanced options (tapping serveral times on about phone > compilation and you'll get that option in settings) and connect the phone to the PC
3. Download android studio SDK and then go to C:\Users\Yourusersname\AppData\Local\Android\sdk\platform-tools
4. Open a cmd terminal (shift + right click)
5. Download the TWRP recovery 3.0 that XePeleato made from his github (sorry I can't post links yet)
6. Now in cmd write: adb reboot bootloader and the adb drivers will be installed in your PC (if not, download ADB Driver Install)
7. Place the recovery.img from the recovery zip to the folder where you opened the terminal (platform-tools)
8. Now write in cmd: fastboot flash recovery recovery.img
9. Write in cmd: fastboot reboot recovery
10. DO A COMPLETE BACKUP (that's important)
11. Now download the ROM and place the system.img and the boot.img of the .zip in the same folder as before.
12. Write in cmd: fastboot flash boot boot.img
13. Write in cmd: fastboot flash system system.img
14. Write in cmd: fastboot reboot recovery
15. Now in recovery select wipe > advanced wipe and select data and cache
16. Install Gapps for 5.1.1 if you want.
That's it, hope it works.
If you share screenshots to see the pre-appearance, I'm totally interested in this project.
Enviado desde mi ALE-L21 mediante Tapatalk
Screenshots
C'mon guys, haven't you already seen AOSP? Well... Here you got the screenshots:
{
"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"
}
Last screenshot is from the 5.0.1 release, but anyway.
I love AOSP, I just needed to see that it was not disguised EMUI
Enviado desde mi ALE-L21 mediante Tapatalk
wilburyh said:
For install:
1. You must be unlocked bootloader
2. Enable ADB debugging in advanced options (tapping serveral times on about phone > compilation and you'll get that option in settings) and connect the phone to the PC
3. Download android studio SDK and then go to C:\Users\Yourusersname\AppData\Local\Android\sdk\platform-tools
4. Open a cmd terminal (shift + right click)
5. Download the TWRP recovery 3.0 that XePeleato made from his github (sorry I can't post links yet)
6. Now in cmd write: adb reboot bootloader and the adb drivers will be installed in your PC (if not, download ADB Driver Install)
7. Place the recovery.img from the recovery zip to the folder where you opened the terminal (platform-tools)
8. Now write in cmd: fastboot flash recovery recovery.img
9. Write in cmd: fastboot reboot recovery
10. DO A COMPLETE BACKUP (that's important)
11. Now download the ROM and place the system.img and the boot.img of the .zip in the same folder as before.
12. Write in cmd: fastboot flash boot boot.img
13. Write in cmd: fastboot flash system system.img
14. Write in cmd: fastboot reboot recovery
15. Now in recovery select wipe > advanced wipe and select data and cache
16. Install Gapps for 5.1.1 if you want.
That's it, hope it works.
Click to expand...
Click to collapse
I installed mine. I wonder if the problem is corrected when the sim card?
This ROM is also compatible with model ALE-L02 and L23?
SkopiX said:
perfect work man but this rom belongs to DEVELOPMENT section, not general
and this is not 1st custom rom, there is already 1 custom rom and 1 flashable via TWRP
still perfect work
Click to expand...
Click to collapse
Since I needed 10 posts to post it there.
Is there any other rom ? I'd love to know what rom is that, maybe RIL is fixed there.
but these 2 roms are modified emui. They aren't based on pure AOSP
Your work it's on facebook, without your name...
Enviado desde mi ALE-L21 mediante Tapatalk
dominj97 said:
but these 2 roms are modified emui. They aren't based on pure AOSP
Click to expand...
Click to collapse
thats true didnt realize diferences, I just saw "rom" not aosp
@XePeleato I guess RIL can be fixed by some dirty hacks on binaries.
I worked before on Xperia devices (CMs, AOSPs, ports) but maybe I can help a bit.
Hi all,
I have this device since saturday and i noticed that there is a sririous lack of aosp roms.
Since i'm not very far with my Java skills i wanted to know if there are peoople willing to join up and develope a custom ROM flashable tru twrp.
Those are my ideas, anybody in ?
Greetings,
Justin.
Its kernel can oc ?
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
Required Downloads:
Download ADB & Fastboot files.
Motorola USB Drivers
Download the latest Moto G8 Play Stock ROM and move it to the PC
1.- Extract and Patch Boot.image using Magisk
•First of all, download and extract the ROM to your PC.
•Attach your device via USB cable and copy only the boot.img file from the extracted folder to your device storage
•Launch Magisk Manager. When a popup appears asking to install Magisk, select INSTALL and choose install again.
•Tap on “Patch Boot Image File”.
Install patched boot image TWRP
•Navigate to internal storage and select your phone’s boot image that you transferred earlier.
•Wait for a couple of seconds. Magisk will start patching the boot image.
•Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and replace it in the same extracted ROM folder on your PC.
2.- Install the Patched Boot Image on Moto G8 Play
•Now, extract the ADB & Fastboot tool, then move the patched boot image file to the same folder.
•Press and hold down the Shift key + right-mouse-click to open the command window/PowerShell.
•Next, enter the following command in order to flash the “patched_boot.img” to install Magisk and root your Android device:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
*Please replace [patched_boot.img] with the name of the boot image file you downloaded followed by the .img extension.
•Wait for the flashing process to complete.
•Finally, type in the command to reboot your device.
fastboot reboot
That’s it.
hey, i tried this but i think i missed something and i ended in a bootloop
tried to flash many of stocks rom and still in bootloop, any help? or any tuto to follow? this site is empty /
first unlock the bootloader, then flash the rom
Unfortunately doesn't work... I have unlocked the bootloader, boot.img is from latest stock rom, Magisk Manager is up to date. Nothing bad happens after I flash and reboot, but Magisk Manager shows that "Magisk is NOT installed". Am I missing something else?
EDIT: I would like to add that while boot.img is 32MB in size, magisk_patched.img is only 15MB... makes me wonder.
didnt work for me, think i killed the phone aahaha
now its say "no bootable a/b slot" sad, and any firmware that i flash its the same, obv the bootloader is unlocked
seumenezes said:
Unfortunately doesn't work... I have unlocked the bootloader, boot.img is from latest stock rom, Magisk Manager is up to date. Nothing bad happens after I flash and reboot, but Magisk Manager shows that "Magisk is NOT installed". Am I missing something else?
EDIT: I would like to add that while boot.img is 32MB in size, magisk_patched.img is only 15MB... makes me wonder.
Click to expand...
Click to collapse
I have the same problem
Anyone ?
I have used this.commands but in the smartphone gives the message "command is not implemented" and the process dont work!
This doesn't work, it only will cause a bootloop on your cellphones, don't try it. If you already did it go to: https://forum.xda-developers.com/moto-g8-play/help/moto-g8-play-boot-loop-t4082055 you can restore to before
This causes bootloop
Who have this problem, contact me at [email protected] that i'll help you.
Como se cual es la ROM que tengo que descargar para mi telefono?
thedarkdestroyer said:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
Required Downloads:
Download ADB & Fastboot files.
Motorola USB Drivers
Download the latest Moto G8 Play Stock ROM and move it to the PC
1.- Extract and Patch Boot.image using Magisk
•First of all, download and extract the ROM to your PC.
•Attach your device via USB cable and copy only the boot.img file from the extracted folder to your device storage
•Launch Magisk Manager. When a popup appears asking to install Magisk, select INSTALL and choose install again.
•Tap on “Patch Boot Image File”.
Install patched boot image TWRP
•Navigate to internal storage and select your phone’s boot image that you transferred earlier.
•Wait for a couple of seconds. Magisk will start patching the boot image.
•Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and replace it in the same extracted ROM folder on your PC.
2.- Install the Patched Boot Image on Moto G8 Play
•Now, extract the ADB & Fastboot tool, then move the patched boot image file to the same folder.
•Press and hold down the Shift key + right-mouse-click to open the command window/PowerShell.
•Next, enter the following command in order to flash the “patched_boot.img” to install Magisk and root your Android device:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
*Please replace [patched_boot.img] with the name of the boot image file you downloaded followed by the .img extension.
•Wait for the flashing process to complete.
•Finally, type in the command to reboot your device.
fastboot reboot
That’s it.
Click to expand...
Click to collapse
-----------
I tried it and I got a boot freeze after the boot flash.
I followed this tutorial and I could recover my ROM:
https://www.youtube.com/watch?v=54XLyaP4o2g&t=322s
Root Moto G8 Play
Seguir todos os passo do tutorial chegou a dar sucesso na instalação da patched mas ao abrir o magisk ainda não consta instalado ou seja não tá indo
Libni Souza, only English, please.
The same happened with me: the magisk didn't install successfully.
Magisk Not Installed - ERRORS IN GUIDE
1. THIS GUIDE CAUSES THE PHONE TO BOOTLOOP
Magisk Not Installed Error - ERRORS IN GUIDE * used updated magisk and give permissions
Don't use this guide. Not sure why it is still here.
could you send me the most current TWRP for Moto G8 play?
Hello. Sorry for grammar errors but i'm studying english right now.
For who do this tutorial and now have your moto G8 play brick, this can help.
youtube.com/watch?v=svtPdIVoloE
This tutorial works perfectly, you must flash the patched boot in the partition boot a and boot b. in case of bootloop you must flash the original boot from the rom that you downloaded earlier
(sorry i use google translator)
uma dica galera o cel deve está com bateria acima de 60%
I AM NOT RESPONSIBLE FOR ANY ERROR, DAMAGE OR LOST ON YOUR DEVICE!
Hello, I saw in the last posts that person couldn't install root in the Moto G8 Play, but I got it and I'll show how to do it.
First, you need the bootloader unlocked, if you don't know what is it, search in youtube how to do it.
Second, you need the motorola drivers, download here (run and install the file).
Third, you need the platform-tools with adb and fastboot, you can download here to Windows; here to Mac; here to Linux.
Get ready 'cause now it's time to pay attention because if you do something wrong, you'll get a bootloop.
First you need the ROM Stock (ROM Default), you have two ways to find it, the first is searching in Google "Moto G8 Play Rom Stock", I won't show a download link, 'cause it's variable, if I show a link, these link will be the brazilian ROM 'cause I'm from Brazil, but if you do this search, it'll work, the second option is downloading the Motorola Rescue and Smart Assintant. You just need to conect your cellphone in fastboot mode on your pc and open the Motorola Rescue and Smart Assintant, you select to rescue your device, log in your account and click to download ROM, the rom will be saved in a hide folder in Windows, you'll need to enable the hidden files. Follow those steps:
{
"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"
}
After:
Perfect, now you're able to see the hidden folder. After you opened the app, selected the rescue, loged in your account and with your device connected in fastboot mode downloaded the rom (after you download ROM, don't click in rescue device, it'll format your data"), you'll open the file explorer, open the Windows "C:", now open the hidden folder "ProgramData", now the folder "RSA", now "Download" and for last "RomFiles", your rom will be there. Open your rom folder and copy "boot.img" file to your device in a place that you can access because you'll need to use this ".img". An additional: if your Windows is in english, maybe those files will be in the normal folder "ProgamData", I don't know how it works when the windows is in english. I think if Windows is in another language, ir create a hidden folder to install 'cause the default name to install is "ProgamData", but Windows in another languages don't have this folder 'cause the folder is in another language. As I said, I don't know how it works, person with windows in english, tell me how this folder is wrote to me fix this in the future, thank you.
All right, now, paste this file on your device.
Open Magisk and click in install:
Click in "Select and Patch a File":
Choose your "boot.img" file:
For last, wait it appear:
Now, open your cellphone folder on pc, open the "Download" folder, and copy the ".img" that Magisk generated. Extract platform-tools with adb and fastboot that you downloaded here to Windows; here to Mac and here to Linux.
Open platform-tools folder that you extracted
And paste the Magisk ".img" that you copied
Now reboot your cellphone in fastboot mode
In the platform-tool folder type "cmd" in the search bar and press enter, like this:
A window will be open:
Now, type: fastboot devices
It'll show if the device is connected
If the device is connect, start the commands in these order:
fastboot flash boot_a "your magisk.img name"
fastboot flash boot_b "your magisk.img name"
fastboot reboot
Now, if everything worked, the device will reboot
If device rebooted normally, follow those steps:
Open Magisk and click in install again:
Now click in "Direct Install (Reccommended)":
Now click in rebbot at the bottom right of the screen:
All right.
If device rebooted normally again, everything worked again.
Now, you can download a root tester in Play Store or you can download "Termux" (Linux terminal on Android) and type the command "su", if Magisk screen appear asking permission, it means it worked.
If the device enter in a bootloop, use the Rescue and Smart Assistant to rescue your cellphone, enter in the fastboot mode and open the app on pc, how you already had installed the ROM, you just need to click to start rescue, the app will flash the rom and the device will come back to the normal.
If you need some help, I'm here to answer you when you need and when I can.
Good luck, Android lovers!
Worked for me !! Thanks !! Now my Moto G8 Play Android 10 is rooted. I already had known this method by others generics guides and it has never worked before. Your guide differences are
1) partition name is boot_a and not simply boot
2) this device has 2 boot partitions: boot_a and boot_b differently others
.....
......
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
.....
.....
Best Regards
Hello everyone, problem.
after unbrick procedure
I am with miui 10 android 8.1.0.011019
boot in twrp format data wipe , yes
error failed to mont '/data' ( invalid argument )
install Magisk-v15.3 last line
failed to mont '/data' ( invalid argument)
... done
install MagiskManager-v5.5.5.apk
i don't get root permissions .
where am i wrong? thank you
patrizi said:
Hello everyone, problem.
after unbrick procedure
Click to expand...
Click to collapse
boot in twrp format data wipe , yes
Reboot Twrp
Format again
If still the same error.
Use this tool(does not lock the bootloader) :https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Flash a fastboot rom https://xiaomirom.com/en/rom/redmi-6a-cactus-global-fastboot-recovery-rom/
and install twrp and try again
A thousand thanks . in order to perform the procedure I had to try 4 versions of MiFlash, to find the complete one .
i went back to miui 9.6 android 8.1.0 English / Chinese language .
now everything should be fine.
Thanks again, good evening everyone
same exact problem
failed to mont '/data' ( invalid argument)
... done
possible ?
NOSS8 said:
boot in twrp format data wipe , yes
Reboot Twrp
Format again
If still the same error.
Use this tool(does not lock the bootloader) :https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Flash a fastboot rom https://xiaomirom.com/en/rom/redmi-6a-cactus-global-fastboot-recovery-rom/
and install twrp and try again
Click to expand...
Click to collapse
Drive with fastboot, I'm working on it
do I find on the forum? thank you
patrizi said:
Drive with fastboot, I'm working on it
do I find on the forum? thank you
Click to expand...
Click to collapse
What's the problem now?
NOSS8 said:
What's the problem now?
Click to expand...
Click to collapse
Good morning .
turned on this morning I find:
android system
there's an internal problem with your device. contact your manufacturer for details, ok. with audio notification
pressed ok everything seems to be OK / working
current firmware: miui 9.6 stable 9.6.3.0 (ocbcnfd). android version 8.1.0. android security patch level 2018-05-05
installed with MiFlash20210226 where I selected clean all in automatic configuration.
writes with 70 - 100 seconds the green line does not fill completely, shows reboot alert with pc notification sound, the phone is in fastboot
does not reboot, has not completed writing, the count does not stop I have waited up to 780 seconds does not reboot, does not
complete writing, stopped at that point, I unplugged the cable and restarted manually. as before failed to mont '/ data' (invalid argument)
TWRP always cactus Italian, previously I have tried others without Italian does not format DATA.
still write problem for protection? that zone (date) has not been overwritten.
you can do a deep format (eliminate protection problems) with fastboot or how?
thank you
patrizi said:
Good morning .
turned on this morning I find:
android system
Click to expand...
Click to collapse
Post the Miflash log.
If android 11 Use https://androidfilehost.com/?fid=14655340768118443054
NOSS8 said:
Post the Miflash log.
If android 11 Use https://androidfilehost.com/?fid=14655340768118443054
Click to expand...
Click to collapse
good morning , installed TWRP-3.3.0-0423-REDMI6A-CN-wzsx150
fixed format error , I install Magisk-v15.3 reboot does not install app MagiskManager-v5.5.5.apk goes into error starts in recovery
I try to delete everything again without errors ,
reboot, delete everything again
install lineageos without errors restart ,
vibrates does not turn on, I also tried detach / attach battery it's bricked now,
procedure for recovery
error: status_sec_img_type-mismatch (0xc002002a) hint verified boot is enabled please download signed image (cust-verified.img) or disable verified boot.
searched for info by mistake
everything is correct, i made no mistakes, i have to try with latest version of flasch tool
I can not understand . thank you
patrizi said:
good morning , installed TWRP-3.3.0-0423-REDMI6A-CN-wzsx150
Click to expand...
Click to collapse
If it's this rom, it's Magisk v21.4
https://forum.xda-developers.com/t/rom-unofficial-lineage-os-17-1.4252127/
Redmi 6a(cactus) Download
Magisk: Download
Recovery redmi 6a: TWRP OrangeFox
Google Apps: OpenGApps (use arm/10.0 nano gapps)
Or https://forum.xda-developers.com/t/...6-lineageos-16-0-for-xiaomi-redmi-6a.3982609/
Magisk version should be 19.3 or below only
NOSS8 said:
If it's this rom, it's Magisk v21.4
https://forum.xda-developers.com/t/rom-unofficial-lineage-os-17-1.4252127/
Redmi 6a(cactus) Download
Magisk: Download
Recovery redmi 6a: TWRP OrangeFox
Google Apps: OpenGApps (use arm/10.0 nano gapps)
Or https://forum.xda-developers.com/t/...6-lineageos-16-0-for-xiaomi-redmi-6a.3982609/
Magisk version should be 19.3 or below only
Click to expand...
Click to collapse
I followed all the info for the recovery.
with SP_Flash_Tool I always have the same error
I have tried with different versions of Global Recovery ROM (cactus)
error: status_sec_img_type-mismatch (0xc002002a) hint verified boot is enabled please download signed image (cust-verified.img) or disable verified boot.
with can I use instead of SP_Flash_Tool?
or a basic file to start in fastboot and send manually?
I can't get over the error
thank you
patrizi said:
I followed all the info for the recovery.
with SP_Flash_Tool I always have the same error
I have tried with different versions of Global Recovery ROM (cactus)
error: status_sec_img_type-mismatch (0xc002002a) hint verified boot is enabled please download signed image (cust-verified.img) or disable verified boot.
with can I use instead of SP_Flash_Tool?
or a basic file to start in fastboot and send manually?
I can't get over the error
thank you
Click to expand...
Click to collapse
with SP_Flash_Tool:
don't use that but Miflash or better download the Fastboot rom correspond to the rom you want to install (the last one seems) then extract the zip from the TGZ file and run the flash all.bat included in the zip.
NOSS8 said:
with SP_Flash_Tool:
don't use that but Miflash or better download the Fastboot rom correspond to the rom you want to install (the last one seems) then extract the zip from the TGZ file and run the flash all.bat included in the zip.
Click to expand...
Click to collapse
the phone, however, is in brik, it does not turn on, pressed the power key vibrates , nothing else
Does Miflash work with the unbrik procedure?
thank you
patrizi said:
the phone, however, is in brik, it does not turn on, pressed the power key vibrates , nothing else
Does Miflash work with the unbrik procedure?
thank you
Click to expand...
Click to collapse
I never told you about .SP_Flash_Tool.
Mi Flash only works if fastboot mode is possible otherwise only EDL Mode will be able to recover the phone.
NOSS8 said:
I never told you about .SP_Flash_Tool.
Mi Flash only works if fastboot mode is possible otherwise only EDL Mode will be able to recover the phone.
Click to expand...
Click to collapse
i noticed that the error always occurs after writing the same file
in my case "odmdtbo" at this point I have:
error : status_sec_img_too_large (0xc0020005)
hint
Verified boot in enabled .
Please download signed image(cust-verified.img) or disable verified boot .
I can't find info to disable verification.
the file is safe and I tried like this:
disconnect phone, uncheck write files before the error
connect phone, write, answer: writing completed disconnect phone
invert selection of file writing boxes (check for no selection errors)
connect phone write
writing completed disconnect phone
turn on phone in fastboot mode
turns on and enters fastboot
SP_Flash_Tool does not connect to the phone (first attempt)
test connection with Mi Flash, here it is ok
select file to write,
ok start writing never ends.
fastboot always ok
I'll try again tomorrow.
i can't understand these writing problems
patrizi said:
i noticed that the error always occurs after writing the same file
in my case "odmdtbo" at this point I have:
Click to expand...
Click to collapse
(again)can you post the log of Miflash!!!!!
Edit the flash all bat script and delete:
fastboot %* flash cust %~dp0images/cust.img || @ECHO "Flash cust error" && exit 1
save and exit.
NOSS8 said:
(again)can you post the log of Miflash!!!!!
Edit the flash all bat script and delete:
fastboot %* flash cust %~dp0images/cust.img || @ECHO "Flash cust error" && exit 1
save and exit.
Click to expand...
Click to collapse
I have edited, not complete writing, I insert log
thank you
NOSS8 said:
(again)can you post the log of Miflash!!!!!
Edit the flash all bat script and delete:
fastboot %* flash cust %~dp0images/cust.img || @ECHO "Flash cust error" && exit 1
save and exit.
Click to expand...
Click to collapse
The bootloader is locked you must unlock it before using Miflash.
Review the method post#2
image path:E:\android\6a\111new1111\ROOT\soft\cactus-8-11-8\cactus_global_images_8.11.8_20181108.0000.00_8.1_global
Path too long E:\Miflash\cactus11
if you manage to unlock it use this method post#11
NOSS8 said:
The bootloader is locked you must unlock it before using Miflash.
Review the method post#2
image path:E:\android\6a\111new1111\ROOT\soft\cactus-8-11-8\cactus_global_images_8.11.8_20181108.0000.00_8.1_global
Path too long E:\cactus11
if you manage to unlock it use this method post#11
Click to expand...
Click to collapse
bootloader is locked ??
I have already performed post procedure 2
not complete writing
I have to use a recent file or older?
I do not understand .
thank you
patrizi said:
bootloader is locked ??
I have already performed post procedure 2
not complete writing
I have to use a recent file or older?
I do not understand .
thank you
Click to expand...
Click to collapse
You have selected:
[12:37:55 bf4b07ea7d2a]:script :E:\android\6a\111new1111\ROOT\soft\cactus-8-11-8\cactus_global_images_8.11.8_20181108.0000.00_8.1_global\flash_all_lock.bat
result
[12:37:56 bf4b07ea7d2a]:err:FAILED (remote: not allowed in locked state)
You've made this mistake before.
Right path; E:\Miflash\cactus11
{
"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"
}
Hi folks,
I got working twrp now
Hope we will gain more customrom soon
What working
- backup
- install
- restore
- mount system data cache
- sideload
- advance
- else etc etc
Please welcome anyone able to fix the bugs
Todo / Bugs
- No MTP / OTG mode
- Log text font size too small
- Sideload
Credits
@hiitsmeh
{
"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"
}
Installation
Enabling developer Option
- go to setting - about - software information - and tap build number 8 times
- go back to setting main page - scroll to last bottom - u will find developer option
- open developer option tick / enable adb debugging and oem unlock
Unlocking bootloader and installing TWRP
- ( on computer ) open cmd and run "adb devices"
- ( on watch ) choose always allow debugging from this computer
- ( on computer ) run cmd "adb reboot bootloader"
- ( on computer ) run cmd "fastboot oem unlock"
- ( on watch ) press top button to choose UNLOCK BOOTLOADER then bottom button to sellect ok
- PAY ATTENTION HERE
WATCH WILL REBOOT ONCE AND ERASING PROGRESS BAR APEAR
DONT LET IT BOOT INTO SYSTEM
WHEN IT VIBRATE AND REBOOT PRESS TOP BUTTON
IT WILL GO INTO BOOT OPTION
CHOOSE REBOOT INTO FASTBOOT
THEN ON PC RUN CMD "fastboot flash recovery Beluga_twrp.img"
- Reboot into TWRP
- WIPE DATA WITH TYPING YES
- REBOOT TWRP AGAIN
- THIS TIME FLASH DM-VERIFY.ZIP
this file available on storage partition
*** Thanks to @hiitsmeh again for this great idea ***
This time i cant brain too much anymore because tired with this recovery for a week
Your browser is not able to display this video.
Root and disable dm verify
- Boot into system
- Finnish the setup until home screen menu
- Push theese files into watch via adb :-
adb push -p mgk.zip /storage/emulated/0/mgk.zip
adb push -p mgk.apk /storage/emulated/0/mgk.apk
- Boot into twrp and flash both zip magisk and dmv
- Boot into system and install magisk apk via adb with this command
adb install mgk.apk.
If you think want do small donation
U can buy me a chocolate bar
Donate via paypall or skrill @ [email protected]
DOWNLOAD BELUGA_V3_TWRP.img
INBOX ME FOR PRO VERSION [PAID]
- fix too small font size on log report
- big adjust all xml to fit on watch better size
VIDEO 1 UNLOCKING BOOTLOADER AND INSTALL TWRP
VIDEO 2 ROOTING INSTALL DMV AND MAGISK
awww thank you so much for making this work
umm where i can download the file?
hey man, i was going to ask something, i was able to come to the last stage. I flashed the DM_V.zip but now my watch won't connect to the os app how can I fix it
bro pls help I am in bad condition
namıkadam said:
hey man, i was going to ask something, i was able to come to the last stage. I flashed the DM_V.zip but now my watch won't connect to the os app how can I fix it
bro pls help I am in bad condition
Click to expand...
Click to collapse
umm maybe u can try wipe dalvik, cache, and data?
hiitsmeh said:
umm maybe u can try wipe dalvik, cache, and data?
Click to expand...
Click to collapse
thanks i will try
do you have any communication with the owner when is the next video coming
namıkadam said:
thanks i will try
do you have any communication with the owner when is the next video coming
Click to expand...
Click to collapse
i dunno, but you can dm him for more info
hiitsmeh said:
i dunno, but you can dm him for more info
Click to expand...
Click to collapse
via which app
namıkadam said:
thanks i will try
do you have any communication with the owner when is the next video coming
Click to expand...
Click to collapse
Which video?
How to root?
Give me few hour hope i able to upload tonight
of this video
Will there be a follow up video?
namıkadam said:
of this video
Will there be a follow up video?
Click to expand...
Click to collapse
Yes uploading about 1 hour
nelikp said:
Evet yaklaşık 1 saat yükleniyor
Click to expand...
Click to collapse
Thank you bro For information
namıkadam said:
Thank you bro For information
Click to expand...
Click to collapse
What your watch condition now?
is it bootloader unlocked?
twrp installed?
nelikp said:
Şimdi saatinizin durumu nedir?
bootloader kilidi açık mı?
twrp yüklü mü?
Click to expand...
Click to collapse
Saati kurdum DM.V.zip'i flashladım ve kurulumu tamamladım ama şimdi adb push hatası alıyorum nasıl çözeceğimi bilmiyorum
DM.V.zip Dosyayı flash ettikten sonra twrp'yi tekrar flashlamalı mıyım?
sorry bad eng
namıkadam said:
Saati kurdum DM.V.zip'i flashladım ve kurulumu tamamladım ama şimdi adb push hatası alıyorum nasıl çözeceğimi bilmiyorum
DM.V.zip Dosyayı flash ettikten sonra twrp'yi tekrar flashlamalı mıyım?
sorry bad eng
Click to expand...
Click to collapse
try push to your sdcard
Can you upload DM-VERIFY.ZIP, please? I can't find this file.
UPDATE V3
DOWNLOAD
V3_TWRP.img
dm_v.zip inside storage folder like this video
Your browser is not able to display this video.
Roxt said:
Can you upload DM-VERIFY.ZIP, please? I can't find this file.
Click to expand...
Click to collapse
see post 18 here
TWRP Error 255 ?
Thank you for this great Tutorial! I have flashed TWRP, DM-VERIFY.ZIP and Magisk.zip.
Full Backup with TWRP worked at the beginning. After I set up the watch I got an Error 255. "recovery.log" shows following:
" ubject_r:recovery_data_file:s0
I:addFile '/data/misc/SzRZq53GAnIGMCyt9rz5CB/B6sacA6lTgxx0jkF9q4TXqJUV9Ok3X61QyXLSqXGsMG' including root: 0
==> set selinux context: ubject_r:recovery_data_file:s0
I:Error adding file '/data/misc/SzRZq53GAnIGMCyt9rz5CB/B6sacA6lTgxx0jkF9q4TXqJUV9Ok3X61QyXLSqXGsMG' to '/data/media/0/TWRP/BACKUPS/100c095c/1970-12-24--15-46-31_PXDR201012001_release-keys/data.f2fs.win "
Also I noticed that I can find theFolder "SzRZq53GAnIGMCyt9rz5CB" in "/data/misc/" using filemanager of TWRP. With Rootexplorer I can't find that folder.
So what can I do, is there a workaround for this issue?
Since there's no Legion Y70 section, I'm posting this here in hopes of helping those who may have bricked their device (like I did).
Requirements:
1. Stock rom. I used L71091_CN_SECURE_USER_Q00041.0_S_ZUI_14.0.697_ST_221216_QPST.zip but any version will work.
2. QPST, QFIL, and Qualcomm drivers installed. I installed them from here: https://qpsttool.com/qpst-tool-v2-7-496
Steps:
1. Extract the stock rom zip to a folder with no spaces. For example I used C:\Stock\
2. Open QFIL, click on Configuration->Firehose configuration
3. Set the configuration settings as shown in attached file config.png (reset state machine should be checked, device type UFS)
{
"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"
}
4. Back in the main QFIL window, select:
Build type : Meta build
Programmer Path: Select the xbl_s_devprg_ns.melf file from where you extracted your stock rom .zip
Content XML: select contents.xml
Storage types: ufs (in the middle and in the bottom right corner too!)
RawProgram and Patch: Select all available files in the rom directory.
For RawProgram, there should be 9 files: rawprogram_unsparsed0, retain_userdata, unsparsed4, and rawprogram 0 to 5
For patch, there should be 6 files: patch0 to 5
5. With the phone off and unplugged, hold volume up + volume down at the same time
6. Plug the phone into a USB slot on your computer while still holding the volume up+down buttons. Wait for Qualcomm HS-USB QDLoader 9008 (COMx) to appear on top of the QFIL screen. You can now release the volume buttons.
7. Click Download Content.
Voila!
My phone was bricked/bootlooping giving me a QUALCOMM CRASHDUMP error on boot up for several days now after trying to load a custom rom and I kept getting SAHARA FAIL error in QFIL while trying to reflash stock in EDL mode. Finally the above settings worked!
sso003 said:
Since there's no Legion Y70 section, I'm posting this here in hopes of helping those who may have bricked their device (like I did).
Requirements:
1. Stock rom. I used L71091_CN_SECURE_USER_Q00041.0_S_ZUI_14.0.697_ST_221216_QPST.zip but any version will work.
2. QPST, QFIL, and Qualcomm drivers installed. I installed them from here: https://qpsttool.com/qpst-tool-v2-7-496
Steps:
1. Extract the stock rom zip to a folder with no spaces. For example I used C:\Stock\
2. Open QFIL, click on Configuration->Firehose configuration
3. Set the configuration settings as shown in attached file config.png (reset state machine should be checked, device type UFS)
View attachment 5866435
4. Back in the main QFIL window, select:
Build type : Meta build
Programmer Path: Select the xbl_s_devprg_ns.melf file from where you extracted your stock rom .zip
Content XML: select contents.xml
Storage types: ufs (in the middle and in the bottom right corner too!)
RawProgram and Patch: Select all available files in the rom directory.
For RawProgram, there should be 9 files: rawprogram_unsparsed0, retain_userdata, unsparsed4, and rawprogram 0 to 5
For patch, there should be 6 files: patch0 to 5
View attachment 5866437
5. With the phone off and unplugged, hold volume up + volume down at the same time
6. Plug the phone into a USB slot on your computer while still holding the volume up+down buttons. Wait for Qualcomm HS-USB QDLoader 9008 (COMx) to appear on top of the QFIL screen. You can now release the volume buttons.
7. Click Download Content.
Voila!
My phone was bricked/bootlooping giving me a QUALCOMM CRASHDUMP error on boot up for several days now after trying to load a custom rom and I kept getting SAHARA FAIL error in QFIL while trying to reflash stock in EDL mode. Finally the above settings worked!
Click to expand...
Click to collapse
(Solved)i keep getting SAHARA FAil error too in QFIL.. Can u tell me how did you solve this problem? and where did you find stock rom? i have only zui14 220914 rom and this rom has a SAHARA error
—— i chose the wrong stock rom. It is not working on QFIL
.
.
.
wjswnsgk0204 said:
(Solved)i keep getting SAHARA FAil error too in QFIL.. Can u tell me how did you solve this problem? and where did you find stock rom? i have only zui14 220914 rom and this rom has a SAHARA error
—— i chose the wrong stock rom. It is not working on QFIL
Click to expand...
Click to collapse
Hello, maybe it's late but for those who need it, I had the same problem as you, that always came up until I came across some advice on why it usually happens, in my case it was that the connection was made before time, We must configure everything long before placing and connecting the mobile in EDL mode, be careful it must be a 100% original USB cable of any brand for the data transmission to be successful... I hope it works for you...
credits: https://www.getdroidtips.com/sahara-fail-error-in-qfil/
where can we find the stock rom
kalid191 said:
donde podemos encontrar la stock rom
Click to expand...
Click to collapse
Hello, this link is https://drive.google.com/file/d/1bRKqkWb7RDcrnXZEnS701T87nfgHxUrk/view?usp=share_link
GustavoRj98 said:
Hello, this link is https://drive.google.com/file/d/1bRKqkWb7RDcrnXZEnS701T87nfgHxUrk/view?usp=share_link
Click to expand...
Click to collapse
thank you so much,
another file i want to ask for is vbmeta.img do you know where can i find it
kalid191 said:
thank you so much,
another file i want to ask for is vbmeta.img do you know where can i find it
Click to expand...
Click to collapse
Here we go
(Credits for the people on 4pda)
This is super helpful! I've linked your guide in my discord server (for Y70 owners) if you don't mind. If anyone is interested in joining, here is the invite: https://discord.gg/r5VMszTGVr
Please feel free to share the link around or invite others. There are help and support channels, and a resources one too. I'm hoping we can attract more people there and have more things shared amongst each other.
jimbi87 said:
Here we go
(Credits for the people on 4pda)
Click to expand...
Click to collapse
What is this??
A alguno le funciona las aplicaciones de streaming como Netflix, HBO, Crunchyroll, etc después de flashear???
Where can I find stock ROM for Legion Y70?
Something is wrong with the display. There is a bar in the middle of the screen that is displayed in a different shade. I have a factory protective film on my screen.
hello , why Programmer Path not work for me , cant click ?
G14R said:
A alguno le funciona las aplicaciones de streaming como Netflix, HBO, Crunchyroll, etc después de flashear???
Click to expand...
Click to collapse
I have the same doubt. You managed to find out.
Discord users have stated that it works using Magisk