Hi. Has anyone managed to root Ulefone Armor X5?
The phone is based on MediaTek Helio P23 MT6763, 64-bit Processor.
Baseband: MOLY.LR12A.R2.MP.V91.7.P4
Kernel: 4.4.146#2 wed Sep 25 16:10:16 CST 2019
Build Nr: Armor_X5_MH1_EEA_V01
I have installed the drivers uploaded onto Mega by the Ulefone company here:
https://mega.nz/#F!t64QzRxA!SxZFFl3WrgujTaFshrFuKA!03YnGSYa
I have created the patched boot.img by Magisk Manager 7.5.0.
Enabled the OEM Unlock and USB Debugging thru the Developer options.
Thru ADB, successfully reboots to fastboot by "adb reboot bootloader". The PC recognizes it as typing "adb devices" gives the serial number.
And so far that's all.
Typing "fastboot oem unlock" or "fastboot flashing unlock" gives no result on the phone screen. The ADB says: waiting for device.
I am following most of the steps explained here:
https://forum.xda-developers.com/android/general/root-ulefone-armor-6-tutorial-t3948089
Any advice on what I am doing wrong?
Is it possible to brick it or bootloop by flashing the patched boot.img directly?
Many thanks.
zhekozhekov said:
Hi. Has anyone managed to root Ulefone Armor X5?
The phone is based on MediaTek Helio P23 MT6763, 64-bit Processor.
Baseband: MOLY.LR12A.R2.MP.V91.7.P4
Kernel: 4.4.146#2 wed Sep 25 16:10:16 CST 2019
Build Nr: Armor_X5_MH1_EEA_V01
I have installed the drivers uploaded onto Mega by the Ulefone company here:
https://mega.nz/#F!t64QzRxA!SxZFFl3WrgujTaFshrFuKA!03YnGSYa
I have created the patched boot.img by Magisk Manager 7.5.0.
Enabled the OEM Unlock and USB Debugging thru the Developer options.
Thru ADB, successfully reboots to fastboot by "adb reboot bootloader". The PC recognizes it as typing "adb devices" gives the serial number.
And so far that's all.
Typing "fastboot oem unlock" or "fastboot flashing unlock" gives no result on the phone screen. The ADB says: waiting for device.
I am following most of the steps explained here:
https://forum.xda-developers.com/android/general/root-ulefone-armor-6-tutorial-t3948089
Any advice on what I am doing wrong?
Is it possible to brick it or bootloop by flashing the patched boot.img directly?
Many thanks.
Click to expand...
Click to collapse
If your PC Is not seeing device in fastboot. It may be you need to update your fastboot.exe
In my case there was two possibilities. In Windows 10 I gave myself higher
admin rights clicking right in the folder of my fastboot programm. I tried a little bit, but there is no big thing to get a positive answer writing (before of course I switch on under developer settings usb debugging and gave answer in phone screen) :
fastboot devices
Better and easier is it on Linux, because writing sudo in front of fastboot and ready is it:
sudo fastboot devices
sudo fastboot flashing unlock
or
sudo fastboot flashing unlock_critical
:good:
Hi,
Recently rooted mine Armor X5 (with some pains) so remember mistakes I did and you might be doing.
First, confirm that fastboot sees your device ("fastboot devices") . If you get "waiting for device" then
try different ADB & fastboot installers (e.g. 15 seconds ADB Installer 1.4.3 or ADB installer v1.3
Good luck
waldem88 said:
Hi,
Recently rooted mine Armor X5 (with some pains) so remember mistakes I did and you might be doing.
First, confirm that fastboot sees your device ("fastboot devices") . If you get "waiting for device" then
try different ADB & fastboot installers (e.g. 15 seconds ADB Installer 1.4.3 or ADB installer v1.3
Good luck
Click to expand...
Click to collapse
Thanks for the advice. I am still waiting for someone to give detailed instructions of rooting it.
Did you flash and use TWRP or flashed the patched boot.img straight? Cheers.
waldem88 said:
Hi,
Recently rooted mine Armor X5 (with some pains) so remember mistakes I did and you might be doing.
First, confirm that fastboot sees your device ("fastboot devices") . If you get "waiting for device" then
try different ADB & fastboot installers (e.g. 15 seconds ADB Installer 1.4.3 or ADB installer v1.3
Good luck
Click to expand...
Click to collapse
just got my phone bro. would you be kind in sharing the method you used to root your armor x5.. thanks.
I have the some problem.
In other device, fastboot are work alright.
I try to edit (repack) Zip Rom with replace boot_verified.img with img from magisk, and instal with SP multi port from official site, its error' on boot.img....
Any idea to verify signature boot_verified.img from magisk.???
Sorry for my bad English..
A Solution
Hi, popping in to say I had the same exact problem. After you enter fastboot through the command "adb reboot bootloader", go into device manager and look for Armor X5, right-click update drivers, and then select search for drivers online. It should automatically update with the adb driver.
( I also found the code at the end of the romprovider tutorial titled "How to create a prerooted patched boot.img with magisk" useful, although fair warning it did wipe my device clean )
My input
I'll say this: There is 2, yes, two fastboot 'modes' in this fone, and is provable thus: adb reboot bootloader - shows a black screen with the tiniest of writing, and...
adb reboot recovery - boots us into (origional) recovery, where we can choose to boot into fastboot, however, when booting into this mode, at the top of the screen we see fastbootd - note the 'd' at the end? fastboot commands work, but dont stick, appear to write succesfully.
So when people say they cant use fastboot commands, this is why!
I got as far as:
adb reboot fastboot
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock <-success - bootloader unlocked, and can be relocked.
fastboot -i 0x0E8D flash boot boot.img <- magisk_patched.img (did not show anything to say it worked)
fastboot -i 0x0E8D flash recovery twrp.img <- twrp (tried all available twrp versions, none worked so far, reckon we need a twrp built for this particular fone)
After reflashing the boot, fone bootlooped.
After flashing recovery, fone bootlooped.
So hopefully someone will chip in, because it's not normal that we can apparently flash anything with bootloader unlocked, but now we cant.. I'll point out my fone is an android 10, probably the reason no other twrp's will work, most likely being made on android 9
I have 30 years programming experience, just getting old and cranky...
Seems my thread starter was moved to god knows where, (bang go donations until I see something worth donating to lol), I AM a developer, who buys toys just to hack them!! So may threads in dev section have ZERO useable information, 'scuse the coment :/
Hi, on my side I am stuck in the same way because I found several versions:
- mt6762
- mt6763
i feel all twrp and magisk are for 6763.
Can you confirm which version you have?
Sorry but I'm stuck months too and I really need to root my phone ;-(
Pachacouti said:
I'll say this: There is 2, yes, two fastboot 'modes' in this fone, and is provable thus: adb reboot bootloader - shows a black screen with the tiniest of writing, and...
adb reboot recovery - boots us into (origional) recovery, where we can choose to boot into fastboot, however, when booting into this mode, at the top of the screen we see fastbootd - note the 'd' at the end? fastboot commands work, but dont stick, appear to write succesfully.
So when people say they cant use fastboot commands, this is why!
I got as far as:
adb reboot fastboot
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock <-success - bootloader unlocked, and can be relocked.
fastboot -i 0x0E8D flash boot boot.img <- magisk_patched.img (did not show anything to say it worked)
fastboot -i 0x0E8D flash recovery twrp.img <- twrp (tried all available twrp versions, none worked so far, reckon we need a twrp built for this particular fone)
After reflashing the boot, fone bootlooped.
After flashing recovery, fone bootlooped.
So hopefully someone will chip in, because it's not normal that we can apparently flash anything with bootloader unlocked, but now we cant.. I'll point out my fone is an android 10, probably the reason no other twrp's will work, most likely being made on android 9
I have 30 years programming experience, just getting old and cranky...
Seems my thread starter was moved to god knows where, (bang go donations until I see something worth donating to lol), I AM a developer, who buys toys just to hack them!! So may threads in dev section have ZERO useable information, 'scuse the coment :/
Click to expand...
Click to collapse
error for me too
you are win?
Using win 7 x64,
Phone is on Android 10_Q
Mtk 6765
This is an aarm64, meaning a 64-bit fone, no instructions available so far work, because they are all for android 9, lot's of 'Q' root's, but not for what they call 'A' only boot, which is not the same as A/B partitioning.
All I'm reading now is the same tut's on hundreds of websites giving the same old information... and the fact root is gone. From what I read, My fone is so up to date that I'm where most will be shortly, and with root devs too busy keeping old hat alive... Figure it out: TWRP is actually dead, now. This is why they no longer accept requests here. Twrp cannot be loaded in a dynamic partition setup, (so far) it wont even fastboot boot twrp.img, not happening with ANY twrp. So forget TWRP. Twrp is old hat to my fone.
Magisk, haha, not one version works for true 64bit, (Not implemented yet), and prob never will be, say tata magisk and say tata su, cause we cant write to the deduped ext4 system, root is kinda pointless now, cause if we cant read/write... Overlayfs is the fix I read, in about 5 years...
So its writing custom kernels for the A only tat's the way I read...
Wake up, it's time to experience the cave in to google domination... their AI patc things much quicker than waiting on devs working on what used to work...
Fingers crossed they get round to the new updates instead of concentrating on what works for ONE fone...
Pachacouti said:
Using win 7 x64,
Phone is on Android 10_Q
Mtk 6765
This is an aarm64, meaning a 64-bit fone, no instructions available so far work, because they are all for android 9, lot's of 'Q' root's, but not for what they call 'A' only boot, which is not the same as A/B partitioning.
All I'm reading now is the same tut's on hundreds of websites giving the same old information... and the fact root is gone. From what I read, My fone is so up to date that I'm where most will be shortly, and with root devs too busy keeping old hat alive... Figure it out: TWRP is actually dead, now. This is why they no longer accept requests here. Twrp cannot be loaded in a dynamic partition setup, (so far) it wont even fastboot boot twrp.img, not happening with ANY twrp. So forget TWRP. Twrp is old hat to my fone.
Magisk, haha, not one version works for true 64bit, (Not implemented yet), and prob never will be, say tata magisk and say tata su, cause we cant write to the deduped ext4 system, root is kinda pointless now, cause if we cant read/write... Overlayfs is the fix I read, in about 5 years...
So its writing custom kernels for the A only tat's the way I read...
Wake up, it's time to experience the cave in to google domination... their AI patc things much quicker than waiting on devs working on what used to work...
Fingers crossed they get round to the new updates instead of concentrating on what works for ONE fone...
Click to expand...
Click to collapse
Hello, I have the same phone, any news about rooting etc.. ?
Hi,
I got my Armor X5 P22 Mediatek MT6762, Android 10 phone a couple of days ago to replace an ageing Moto G5S. I have unlocked the bootloader on several previous Android phones, but found doing so on this X5 a bit harder.
Assuming you have enabled 'Developer Options' etc on the phone and installed the Mediatek drivers and 'Minimal ADB and Fastboot' on your PC/laptop, I would suggest that once you are in Fastboot mode and have confirmed that Fastboot recognises your device with the command "Fastboot devices", that you next enter the command
Fastboot /?
This will bring up all the Fastboot commands and options installed on your phone. I then used
Fastboot flashing get_unlock_ability which returned an 8 digit number:-
D:\Minimal ADB and Fastboot>fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.015s]
finished. total time: 0.015s
I have no idea what the 8 digit number means, as I thought it would return '1' or '0' .
However I then did the following:
D:\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (remote: GetVar Variable Not found)
finished. total time: 6.704s
D:\Minimal ADB and Fastboot>fastboot reboot
(bootloader) Start unlock flow
rebooting...
On rebooting the phone, a warning appeared on the Home Screen for 5 seconds stating that the bootloader was unlocked, the phone could not be trusted and my warranty was void. The phone was factory reset.
On re-enabling 'Developer Options' and checking the 'OEM unlocking' option the phone confirms that 'Bootloader is already unlocked'
Don't know whether this helps anyone else struggling to unlock their phone.
The 'fastboot flashing unlock' command might be unnecesary.
regards
bjlabuk said:
Hi,
I got my Armor X5 P22 Mediatek MT6762, Android 10 phone a couple of days ago to replace an ageing Moto G5S. I have unlocked the bootloader on several previous Android phones, but found doing so on this X5 a bit harder.
Assuming you have enabled 'Developer Options' etc on the phone and installed the Mediatek drivers and 'Minimal ADB and Fastboot' on your PC/laptop, I would suggest that once you are in Fastboot mode and have confirmed that Fastboot recognises your device with the command "Fastboot devices", that you next enter the command
Fastboot /?
This will bring up all the Fastboot commands and options installed on your phone. I then used
Fastboot flashing get_unlock_ability which returned an 8 digit number:-
D:\Minimal ADB and Fastboot>fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.015s]
finished. total time: 0.015s
I have no idea what the 8 digit number means, as I thought it would return '1' or '0' .
However I then did the following:
D:\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (remote: GetVar Variable Not found)
finished. total time: 6.704s
D:\Minimal ADB and Fastboot>fastboot reboot
(bootloader) Start unlock flow
rebooting...
On rebooting the phone, a warning appeared on the Home Screen for 5 seconds stating that the bootloader was unlocked, the phone could not be trusted and my warranty was void. The phone was factory reset.
On re-enabling 'Developer Options' and checking the 'OEM unlocking' option the phone confirms that 'Bootloader is already unlocked'
Don't know whether this helps anyone else struggling to unlock their phone.
The 'fastboot flashing unlock' command might be unnecesary.
regards
Click to expand...
Click to collapse
Hello, could you flash twrp on this phone? I have the same one (mt6762, Android 10) and couldnt find a working twrp Port...
Deleted link to unofficial twrp site
maxxvd said:
Hello, could you flash twrp on this phone? I have the same one (mt6762, Android 10) and couldnt find a working twrp Port...
Click to expand...
Click to collapse
You dont have same fone, you have mt6762, I have mt6765
This worked for me (am using a mac so my terminal lingo may be different)
Device: Ulefone X5 2019
Chipset MT6763
Processor: arm64-v8a, A-only system partition
Reset device
Enable developer options, USB debugging, and OEM unlock, then in terminal, do:
adb device
adb reboot bootloader
fastboot flashing unlock_critical
Device is now unlocked and reboots (unlocked warning now appears on reboot screen)
——
Then I installed TWRP & Magisk:
Re-enable developer options, USB debugging, and OEM unlock
To flash the TWRP recovery.img: Copy the TWRP recovery.img into the platform-tools folder, and from that folder, do:
adb reboot bootloader
fastboot flash recovery recovery.img
Then once finished, hold down the power and volume up buttons until it shuts down and restarts (restarts in TWRP recovery)
——
• Download the latest Magisk installer file and put it in the ADB (platform-tools) tools folder (or in your device storage)
• Inside TWRP, go to Advanced > ADB Sideload, then do adb sideload Magisk.zip (replace Magisk.zip with the Magisk zip filename )
Swipe the slider to install Magisk
Tap Reboot System
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
dary1361 said:
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
Click to expand...
Click to collapse
See this thread:
[Moto G Play](2021)(guamna) Stock firmware
Moto G Play (2021) Stock Firmware Codename: guamna Model: XT-2093 Rescue and Smart Assistant (LMSA) https://mirrors.lolinet.com/firmware/moto/guamna/official/ https://t.me/s/MotoUpdatesTracker?q=#guamna [Index] Motorola Stock Firmware...
forum.xda-developers.com
residentorca said:
See this thread:
[Moto G Play](2021)(guamna) Stock firmware
Moto G Play (2021) Stock Firmware Codename: guamna Model: XT-2093 Rescue and Smart Assistant (LMSA) https://mirrors.lolinet.com/firmware/moto/guamna/official/ https://t.me/s/MotoUpdatesTracker?q=#guamna [Index] Motorola Stock Firmware...
forum.xda-developers.com
Click to expand...
Click to collapse
This might be a stupid question. But isn't stock firmware what the device comes with? I'm trying to "de-google" my phone.
dary1361 said:
This might be a stupid question. But isn't stock firmware what the device comes with? I'm trying to "de-google" my phone.
Click to expand...
Click to collapse
You can root it and use Magisk to clean things up but no de-Googling. Check out the thread.
Any device that launched with Android 8 or newer is compatible with GSIs. Any device that launched with Android 10 or newer use super.img, which require the extra step of repacking rather than flashing directly. This is what I would recommend if you want ROM support on a brand new device.
dary1361 said:
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
Click to expand...
Click to collapse
https://drive.google.com/file/d/1DydHY_Q_paR4QcLhhyE8ih3hYZpqK3RM/view?usp=drivesdk is a device tree with a build error bootctrl if we get this working we can build ROMs and twrp
I have a TWP I ported it from the stock recovery and one from Guamp which is the G9
svoc said:
https://drive.google.com/file/d/1DydHY_Q_paR4QcLhhyE8ih3hYZpqK3RM/view?usp=drivesdk is a device tree with a build error bootctrl if we get this working we can build ROMs and twrp
Click to expand...
Click to collapse
Hey I can’t access the file for some reason. Care to reupload? I’m trying to get a port started but I can’t find the device tree anywhere and can’t find a good guide to make one myself.
Hey you go I got a few more errors fixed but don't have time I'm on a new phone right now sorry hope you get it working by the way look at the trwp it will have some device trees you can use to get started
I want to know if there's a custom ROM for this device.
Hold on, there is a custom ROM for this device.
[ROM][13][guamna] AOSP 13 [Monthly Builds]
AOSP 13 This is a moto-common project release under the codename guamna /* * 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...
forum.xda-developers.com
dary1361 said:
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
Click to expand...
Click to collapse
You can use a Treble system Image! <See below for files>
To flash,
Step #1: Use the treble info app to see if your phone supports treble (Optional, I know the moto g play 2021 is compatible)
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Step #3: Download 15-second adb installer (I Prefer this because its fast than searching for drivers) Download Here: https://androiddatahost.com/wp-content/uploads/15_Second_ADB_Installer_v1.3.0.zip
Step #3.5: I assume you enabled oem unlock and bootloader, but if not, instructions are below
Step #4: Unlock your bootloader
(Step #1: Enable OEM by going to about phone and tap build number 7 times (I'm sure you know the rest )
Step #2 Hold Vol down, (While holding Vol down) connect to PC.
Step #3: Go to https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Sign into google or moto id, and follow steps to get unlock code (For bootloader unlock))
WARNING!! DATA ON DEVICE IS GONE!! WARANTY NOW VOID!!
Step #5: Run the command in CMD (as admin): adb devices (Starts ADB service)
Then run: fastboot devices (Your device should be connected)
Then run: fastboot oem unlock <unlock code here> (From website provided)
Then: You should get a message saying: Warning Blah Blah Blah. Just read the message
DONE! (Should reboot to factory settings)
Step #6: Turn device off, then hold Vol down, and connect to PC
Step #1: Make sure to have put the <imagename>.img you downloaded earlier in the adb folder in your windows local disk (and renamed it to "system.img" to make flashing easier)
Step #7: Reboot to fastbootd by running: "fastboot reboot fastboot" in CMD
Then run: fastboot erase system
Then: fastboot flash system system.img (Might get error message!) (To fix, run "fastboot delete-logical-partition product_a" Then run "fastboot flash system system.img" again)
Then wait. . .
After, run "fastboot -w"
Then: "fastboot reboot"
DONE!!!!!! Enjoy
Files Below!!!
WolfHunter16 said:
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Click to expand...
Click to collapse
Now, if I were to download a rom from the site, would it be A only? B? A/B?
They are all A/B, just check the filenames. If you read the release notes, they state there is no A-only build yet.
WolfHunter16 said:
You can use a Treble system Image! <See below for files>
To flash,
Step #1: Use the treble info app to see if your phone supports treble (Optional, I know the moto g play 2021 is compatible)
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Step #3: Download 15-second adb installer (I Prefer this because its fast than searching for drivers) Download Here: https://androiddatahost.com/wp-content/uploads/15_Second_ADB_Installer_v1.3.0.zip
Step #3.5: I assume you enabled oem unlock and bootloader, but if not, instructions are below
Step #4: Unlock your bootloader
(Step #1: Enable OEM by going to about phone and tap build number 7 times (I'm sure you know the rest )
Step #2 Hold Vol down, (While holding Vol down) connect to PC.
Step #3: Go to https://accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone/bootloader/unlock-your-device-b
Sign into google or moto id, and follow steps to get unlock code (For bootloader unlock))
WARNING!! DATA ON DEVICE IS GONE!! WARANTY NOW VOID!!
Step #5: Run the command in CMD (as admin): adb devices (Starts ADB service)
Then run: fastboot devices (Your device should be connected)
Then run: fastboot oem unlock <unlock code here> (From website provided)
Then: You should get a message saying: Warning Blah Blah Blah. Just read the message
DONE! (Should reboot to factory settings)
Step #6: Turn device off, then hold Vol down, and connect to PC
Step #1: Make sure to have put the <imagename>.img you downloaded earlier in the adb folder in your windows local disk (and renamed it to "system.img" to make flashing easier)
Step #7: Reboot to fastbootd by running: "fastboot reboot fastboot" in CMD
Then run: fastboot erase system
Then: fastboot flash system system.img (Might get error message!) (To fix, run "fastboot delete-logical-partition product_a" Then run "fastboot flash system system.img" again)
Then wait. . .
After, run "fastboot -w"
Then: "fastboot reboot"
DONE!!!!!! Enjoy
Files Below!!!
Click to expand...
Click to collapse
I haven't been able to get my sim card to be detected, is this a known issue or am I missing something?
Download your stock rom and flash radio.img to restore cell signal
svoc said:
Download your stock rom and flash radio.img to restore cell signal
Click to expand...
Click to collapse
Thanks for the tip! I knew I was missing a detail.
WolfHunter16 said:
You can use a Treble system Image! <See below for files>
To flash,
Step #1: Use the treble info app to see if your phone supports treble (Optional, I know the moto g play 2021 is compatible)
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Step #3: Download 15-second adb installer (I Prefer this because its fast than searching for drivers) Download Here: https://androiddatahost.com/wp-content/uploads/15_Second_ADB_Installer_v1.3.0.zip
Step #3.5: I assume you enabled oem unlock and bootloader, but if not, instructions are below
Step #4: Unlock your bootloader
(Step #1: Enable OEM by going to about phone and tap build number 7 times (I'm sure you know the rest )
Step #2 Hold Vol down, (While holding Vol down) connect to PC.
Step #3: Go to https://accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone/bootloader/unlock-your-device-b
Sign into google or moto id, and follow steps to get unlock code (For bootloader unlock))
WARNING!! DATA ON DEVICE IS GONE!! WARANTY NOW VOID!!
Step #5: Run the command in CMD (as admin): adb devices (Starts ADB service)
Then run: fastboot devices (Your device should be connected)
Then run: fastboot oem unlock <unlock code here> (From website provided)
Then: You should get a message saying: Warning Blah Blah Blah. Just read the message
DONE! (Should reboot to factory settings)
Step #6: Turn device off, then hold Vol down, and connect to PC
Step #1: Make sure to have put the <imagename>.img you downloaded earlier in the adb folder in your windows local disk (and renamed it to "system.img" to make flashing easier)
Step #7: Reboot to fastbootd by running: "fastboot reboot fastboot" in CMD
Then run: fastboot erase system
Then: fastboot flash system system.img (Might get error message!) (To fix, run "fastboot delete-logical-partition product_a" Then run "fastboot flash system system.img" again)
Then wait. . .
After, run "fastboot -w"
Then: "fastboot reboot"
DONE!!!!!! Enjoy
Files Below!!!
Click to expand...
Click to collapse
It works! This has been kicking my butt left right and sideways for weeks but this worked. Thanks!
WolfHunter16 said:
You can use a Treble system Image! <See below for files>
To flash,
Step #1: Use the treble info app to see if your phone supports treble (Optional, I know the moto g play 2021 is compatible)
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Step #3: Download 15-second adb installer (I Prefer this because its fast than searching for drivers) Download Here: https://androiddatahost.com/wp-content/uploads/15_Second_ADB_Installer_v1.3.0.zip
Step #3.5: I assume you enabled oem unlock and bootloader, but if not, instructions are below
Step #4: Unlock your bootloader
(Step #1: Enable OEM by going to about phone and tap build number 7 times (I'm sure you know the rest )
Step #2 Hold Vol down, (While holding Vol down) connect to PC.
Step #3: Go to https://accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone/bootloader/unlock-your-device-b
Sign into google or moto id, and follow steps to get unlock code (For bootloader unlock))
WARNING!! DATA ON DEVICE IS GONE!! WARANTY NOW VOID!!
Step #5: Run the command in CMD (as admin): adb devices (Starts ADB service)
Then run: fastboot devices (Your device should be connected)
Then run: fastboot oem unlock <unlock code here> (From website provided)
Then: You should get a message saying: Warning Blah Blah Blah. Just read the message
DONE! (Should reboot to factory settings)
Step #6: Turn device off, then hold Vol down, and connect to PC
Step #1: Make sure to have put the <imagename>.img you downloaded earlier in the adb folder in your windows local disk (and renamed it to "system.img" to make flashing easier)
Step #7: Reboot to fastbootd by running: "fastboot reboot fastboot" in CMD
Then run: fastboot erase system
Then: fastboot flash system system.img (Might get error message!) (To fix, run "fastboot delete-logical-partition product_a" Then run "fastboot flash system system.img" again)
Then wait. . .
After, run "fastboot -w"
Then: "fastboot reboot"
DONE!!!!!! Enjoy
Files Below!!!
Click to expand...
Click to collapse
Each time I try this I get to 6/7 flashing system_a and then it says operation not permitted... banging my head against the wall here.
sending sparse 'system_a' 5/7 (262084 KB)...
OKAY [ 7.256s]
writing 'system_a' 5/7...
OKAY [ 3.463s]
sending sparse 'system_a' 6/7 (262124 KB)...
OKAY [ 7.248s]
writing 'system_a' 6/7...
FAILED (remote: Operation not permitted)
finished. total time: 61.098s
Any ideas?
Edit: I'm in fastbootd mode but delete-logical-partition still doesn't work.
stoag said:
Each time I try this I get to 6/7 flashing system_a and then it says operation not permitted... banging my head against the wall here.
sending sparse 'system_a' 5/7 (262084 KB)...
OKAY [ 7.256s]
writing 'system_a' 5/7...
OKAY [ 3.463s]
sending sparse 'system_a' 6/7 (262124 KB)...
OKAY [ 7.248s]
writing 'system_a' 6/7...
FAILED (remote: Operation not permitted)
finished. total time: 61.098s
Any ideas?
Edit: I'm in fastbootd mode but delete-logical-partition still doesn't work.
Click to expand...
Click to collapse
Make sure you have the current version of fastboot, AND that it's the one that you're using. Ran into that problem mysself, updated my PATH incorrectly and had it pointing to the wrong fastboot.exe.
First time poster.... please go gentle on me. Not entirely new to custom roms and TWRP, but really stuck here. I am trying to install a CrDroid ROM. Phone is not networked locked and brand new. What I managed to do so far:
1. Reset the phone
2. reboot into Recovery (Mi Recovery)
3. Wipe data
4. Unlocked the phone (using offical Mi Unlock)
I then proceeded to boot into Fastboot and flashed the TWRP (twrp-3.7.0_12-0-onclite), renamed to recovery. But after flashing and rebooting I can only get into Fastboot, or boot it normally. Holding down the Volume+Up and Power button doesn't get me anywhere but Fastboot. (Same for Volume-Down and Power Up). I tried both un-pluggin the phone from the PC immediately after flashing is finished, and using Fastboot Reboot command, but all to no avail. Its Fastboot or normal boot only.
I also tried whats suggested here upto the vbmeta image, but didn't make a difference. When sending the 'fastboot boot recovery.img' command, I get the following error:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.939s]
booting...
FAILED (remote: unknown reason)
finished. total time: 1.502s
Trying this guide for a 'custom' boot image from this page also didnt help
Really hoping there is a way to get this resolved. But totally stuck here. Have access to both Mac OS and Windows 10. If anyone can point me in the right direction it would be wonderful!
Ok, small update - in hope to help others...
I went ahead and used 'XiaoMiTool V2'to see if it might help to load a different ROM. When starting the app, I choose the 'Bricked' device option, even it wasnt bricked. I choose the Global ROM 12. (The phone showed up as unknown and I didnt sign in with the Mi Account).
After the new ROM was on it, phone started normally and went through the setup. Had to re-enable Developer Options, USB Debugging, but even so it still didnt work - installing the TWRP just kept bringing me back to Fastboot.
However, the TWRP from this page did work: https://twrp.me/xiaomi/xiaomi-mi439.html
I also took no chances and held the Volume up button pressed and with the Command window open and 'fastboot reboot'typed out, hit the Enter key at the same time as pressing the Power button on the phone.
Worked for me!
Try to install PitchBlack Recovery it's very compable PBRP-pine-3.1.0 _OFFICIAL
Timesnaps said:
First time poster.... please go gentle on me. Not entirely new to custom roms and TWRP, but really stuck here. I am trying to install a CrDroid ROM. Phone is not networked locked and brand new. What I managed to do so far:
1. Reset the phone
2. reboot into Recovery (Mi Recovery)
3. Wipe data
4. Unlocked the phone (using offical Mi Unlock)
I then proceeded to boot into Fastboot and flashed the TWRP (twrp-3.7.0_12-0-onclite), renamed to recovery. But after flashing and rebooting I can only get into Fastboot, or boot it normally. Holding down the Volume+Up and Power button doesn't get me anywhere but Fastboot. (Same for Volume-Down and Power Up). I tried both un-pluggin the phone from the PC immediately after flashing is finished, and using Fastboot Reboot command, but all to no avail. Its Fastboot or normal boot only.
I also tried whats suggested here upto the vbmeta image, but didn't make a difference. When sending the 'fastboot boot recovery.img' command, I get the following error:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.939s]
booting...
FAILED (remote: unknown reason)
finished. total time: 1.502s
Trying this guide for a 'custom' boot image from this page also didnt help
Really hoping there is a way to get this resolved. But totally stuck here. Have access to both Mac OS and Windows 10. If anyone can point me in the right direction it would be wonderful!
Click to expand...
Click to collapse
You are trying to install onclite (Redmi 7) recovery on pine (Redmi 7A) ???
mi439 TWRP works for me as well & even successfully flash the rom/gapps. but when it comes to rooting with Magisk, i failed to flash nor install it properly. hope someone/somebody would make a tutorial for flashing/installing Magisk.