can anyone pls help with how to root the Lenovo TB-x306f
i already unlocked the bootloader but that's as far as i was able to go with it.
i want to also like to install a recovery to flash the evolutionx rom if someone can pls help me and others that needs the same help.
GOD BLESS
I second that. There's nothing out there.
What I tried was to download the original ROM patch the boot.img with magical, replace in LMSA download folder and start a rescue. Didn't help. Got boot loop.
Ok, maybe a bit more details on what I tried already:
1. Enabled developer options. Good.
2. OEM unlocked. ADB connected. Good.
3. Boot to bootloader working. Good.
4. fastboot not listing the device after fastboot devices. Not good.
5. Googling around, found an universal root method with Magisk. Good.
6. Donwloaded, installed and ran RSA (Lenovo Rescue and Smart Assistant). Connected to device. Good.
7. Entered Rescue and using that downloaded the original ROM. Good.
C:\ProgramData\LMSA\Download\RomFiles\TB_X306F_S100134_210120_BMP
8. Copied boot.img to device, installed MagiskManager, patched image with magisk, downloaded the image to PC, replaced the original boot image with the patched one. Good.
9. Started the Rescue procedure in RSA. Rom flased. Good.
10. Bootloop. Bad.
No idea why would that not work, any help, pointers, ideas appreciated.
EDIT: There's a new ROM version now: TB_X306F_S100152_210205_BMP
For a preface, I have the same Tablet as OP. I tried to unlock the bootloader, following seemingly every guide out there but, no success so far. I've enabled debugging, activated OEM unlock and, adb detects my device but, after I send it to fastboot (adb reboot bootloader), no more commands work. I've updated the driver in Manager as one guide suggested but, still nothing.
I used command (fastboot OEM unlock) to continue but nothing. What am I doing wrong?
So just a tip for those that are looking for a guide to do a complete bootloader unlock for TB-X306F, there isn't one. I found a bunch of different ways to go about unlocking the bootloader from different Lenovo devices. First thing is that you need Minimal ABD Fastboot v1.4.3 if Platform Tools or LeTools doesn't work. Use CMD with admin rights, not PowerShell.
Everything else to unlock it is the same from all the guides out there. Make sure to use "fastboot flashing unlock" when unlocking instead of "fastboot oem unlock" or "fastboot oem unlock-go" if they dont work.
Second tip is for root when installing the Magisk patched boot image. While you're getting the boot.img, make sure to also grab the vbmeta.img from the ROM folder and place it in the Minimal ADB Fastboot folder where you will be using CMD. Do all the steps to get the patched boot image. Once you got the boot.img patched, enter fastboot then enter the command "fastboot --disable-verification flash vbmeta vbmeta.img" This will disable verification needed to boot correctly. After that, enter the command "fastboot flash boot <name of .img>" like normal to flash the patched boot.img from magisk. Then fastboot reboot.
This is what I did to get my TB-X306F unlocked and rooted. YMMV.
Different threads that I read to get to where I got, credit goes to them:
LENOVO Tab M10 Plus
After receiving my LENOVO Tab M10 Plus TB-X606F I tried to root my tablet. my Firmware version is TB-X606F_RF01_200103 - loaded the Lenovo Rescue and Smart Assistant (V5.0.0.25) - enabled OEM unlock - downloaded magisk - installed ADB now my...
forum.xda-developers.com
Lenovo M10 HD 2nd Gen X306F boot loop if boot.img is patched - android 10 · Issue #3832 · topjohnwu/Magisk
I recently installed magisk manager and extracted the boot.img from tb-x306f_rf01_200926 upon doing a fastboot flash boot magisk_patched.img , the machine goes into a boot loop. Am I doing somethin...
github.com
TWRP for LENOVO Tab M10 FHD - TB-X606F?
Hello, Possessing two tablets of this brand, I was wondering if a custom recovery existed for this one, I can look everywhere on all the forums, Russian, English, etc ... But, I do not find. If anyone can create one with this SOURCE CODE from...
forum.xda-developers.com
Lenovo tab m8
Hello, Any root and custom ROM available for the Lenovo tab m8 tb8505 variant? The stock rom feels good for the price but if something better to make the tab feel nicer.. Thanks :) :)
forum.xda-developers.com
By any chance can u pls.... Make a video on the steps u explained including on where to get that file needed. Pls thank u and GOD BLESS YOU. If u can find the time to do it .
I apologize for asking for so much help on this.
I too would very much care to see a video of the process but, I have no problem trying it first hand to myself. This tablet is just weird. It can be detected but, as soon as I boot into fastboot, it can't pick it up anymore even though, I had grabbed all of the recommended tools so far such as the fast Boot and the bundle.
A detailed guide would be good enough too
Following @doink_doink 's post (and some bootloops after...) I finally managed to root my Lenovo M10 HD 2 gen (TB-X306X) with magisk. I'll attempt to write a simple guide for who's still interested with rooting this kind of devices since there's not much literature online.
Rooting Lenovo M10 X306X (should also work for other models)
I am by no means held responsible for eventual damage you can inflict on your device, follow the underlying steps of your own accord.
Desktop Tools:
Minimal ADB and Fastboot
Lenovo Rescue Smart Assistant (LRSA from now on)
MTK (Mediatek) Preload Drivers (If your device isn't listed in fastboot)
Mobile Tools:
Magisk Manager App
Steps:
1 - From LRSA click on "Rescue" Tab
2 - Select the model of your tablet and then download
3 - From "Downloads" in the top right corner of the LRSA, click on "Open" to go into the LRSA download folder
4 - Connect your device and set it into USB Debugging and File Transfer
5 - Copy boot.img from LRSA download folder into the device's download folder
6 - Run Magisk Manager App on your device
7 - From Magisk Manager App choose "Install" on the right side of Magisk
8 - Choose the only option "Select and patch a file"
9 - Choose the boot.img you previously copied into the device's download folder
10 - Copy the new file "patched_boot.img" or similar name to the folder where Minimal ADB and Fastboot was installed
11 - Copy the file vbmeta.img from LRSA download folder to Minimal ADB and Fastboot folder
12 - From your device's settings enable developer options and enable OEM Unlock
13 - Execute a cmd session with administrator privileges
14 - Execute in the cmd: adb reboot bootloader (if everything went right the device should reboot in fastboot mode)
15 - Execute in the cmd: fastboot flashing unlock
16 - Execute in the cmd: fastboot --disable-verification flash vbmeta vbmeta.img
17 - Execute in the cmd: fastboot flash boot patched_boot.img
18 - Execute in the cmd: fastboot reboot
The device should correctly reboot and everything should be good to go now.
If something bad happens, like a bootloop or something, turn off the device and use the LRSA to rescue your device.
I don't get around to checking my email as often as I used to so I just now got around to seeing this but, I will try this after I get home from work in 10 hours plus time. If I can get this to successfully work, I will be flat out amazed. I had gotten to the point where I had just given up any and all hope that I would get it to work.
Show
Chairos said:
Following @doink_doink 's post (and some bootloops after...) I finally managed to root my Lenovo M10 HD 2 gen (TB-X306X) with magisk. I'll attempt to write a simple guide for who's still interested with rooting this kind of devices since there's not much literature online.
Rooting Lenovo M10 X306X (should also work for other models)
I am by no means held responsible for eventual damage you can inflict on your device, follow the underlying steps of your own accord.
Desktop Tools:
Minimal ADB and Fastboot
Lenovo Rescue Smart Assistant (LRSA from now on)
MTK (Mediatek) Preload Drivers (If your device isn't listed in fastboot)
Mobile Tools:
Magisk Manager App
Steps:
1 - From LRSA click on "Rescue" Tab
2 - Select the model of your tablet and then download
3 - From "Downloads" in the top right corner of the LRSA, click on "Open" to go into the LRSA download folder
4 - Connect your device and set it into USB Debugging and File Transfer
5 - Copy boot.img from LRSA download folder into the device's download folder
6 - Run Magisk Manager App on your device
7 - From Magisk Manager App choose "Install" on the right side of Magisk
8 - Choose the only option "Select and patch a file"
9 - Choose the boot.img you previously copied into the device's download folder
10 - Copy the new file "patched_boot.img" or similar name to the folder where Minimal ADB and Fastboot was installed
11 - Copy the file vbmeta.img from LRSA download folder to Minimal ADB and Fastboot folder
12 - From your device's settings enable developer options and enable OEM Unlock
13 - Execute a cmd session with administrator privileges
14 - Execute in the cmd: adb reboot bootloader (if everything went right the device should reboot in fastboot mode)
15 - Execute in the cmd: fastboot flashing unlock
16 - Execute in the cmd: fastboot --disable-verification flash vbmeta vbmeta.img
17 - Execute in the cmd: fastboot flash boot patched_boot.img
18 - Execute in the cmd: fastboot reboot
The device should correctly reboot and everything should be good to go now.
If something bad happens, like a bootloop or something, turn off the device and use the LRSA to rescue your device.
Click to expand...
Click to collapse
Hi I have the same device I have my patched boot.img and vbmeta.img but when I adb reboot bootloader fastboot commands don't work anymore fastboot flashing unlock says <waiting for device> and every other command. I have latest fastboot drivers google USB drivers I've done everything I have no hope please reply and help me
Hello231 said:
Show
Hi I have the same device I have my patched boot.img and vbmeta.img but when I adb reboot bootloader fastboot commands don't work anymore fastboot flashing unlock says <waiting for device> and every other command. I have latest fastboot drivers google USB drivers I've done everything I have no hope please reply and help me
Click to expand...
Click to collapse
* I have the TB-X306F***
Hello231 said:
Show
Hi I have the same device I have my patched boot.img and vbmeta.img but when I adb reboot bootloader fastboot commands don't work anymore fastboot flashing unlock says <waiting for device> and every other command. I have latest fastboot drivers google USB drivers I've done everything I have no hope please reply and help me
Click to expand...
Click to collapse
I'm currently experiencing the same issue. I have done everything, followed every step provided by Chairos and it wont surpass beyond the <Waiting for device> message. I just got this device today for a fair price, hoping I could root the device, and typical me forgot to research if it was officially compatible with TWRP.
cratee said:
I'm currently experiencing the same issue. I have done everything, followed every step provided by Chairos and it wont surpass beyond the <Waiting for device> message. I just got this device today for a fair price, hoping I could root the device, and typical me forgot to research if it was officially compatible with TWRP.
Click to expand...
Click to collapse
I got it for free for online classes but that's not the problem twrp is out for this device unofficialy but many say that it works, anyways good luck on u mate I gave up on rooting this device I can't do it anymore I've been trying for 4 months but nothing still if I had the Chance and the correct guide I would definitely do it
cratee said:
I'm currently experiencing the same issue. I have done everything, followed every step provided by Chairos and it wont surpass beyond the <Waiting for device> message. I just got this device today for a fair price, hoping I could root the device, and typical me forgot to research if it was officially compatible with TWRP.
Click to expand...
Click to collapse
Make sure you have the latest MTK usb drivers.
Hello Everyone,
I apologize for the delay but I didn't get notified of your replies.
I also got the waiting for device problem, but as @Yahoo Mike says, it's the MTK USB drivers that are used to communicate with the device in fastboot mode. Latest drivers should do.
Let me know if you're still experiencing the problem after installing the latest MTK drivers, since it depends on which motherboard the tablet has but all models should use mediatek.
Worked like a charm! Thanks.
Can anyone please confirm if there is a TWRP even unofficial IMG out there? And if any kind soul could share the file too I would be so grateful thanks
worked beautifully ...
just the installation of the latest MTK drivers is not very typical. however, you can follow this guide to install MTKL drivers and disable the driver signature enforcement
Download MTK USB Drivers for Windows 11, 10 - Driver Easy
To flash files to your MediaTek chipset phones, you need to have the latest MediaTek drivers installed. We'll show you how to install the MTK driver easily.
www.drivereasy.com
When you Restart: go to Advanced Options to find the Driver Signature Disablement option
I received yesterday my TB-X306X, with Android 10 and with software version S100184_210325_BMP. First thing to do was to unlock and root the tablet, without any issue, thanks to clear indications found on this thread.
Has anybody been able to find working TWRP for this tablet ?
Related
Hello guys,
i have a bricked rooted oneplus x
I had issues with the rooted rom so i flashed the newest stock rom via twrp
The phone boots up and showed the usual otimizing apps message. After the proccess is done it just the usual "let me helpt set up your phone page" and then restarts
I cant acces twrp anymore and when i try to acces the stock recovery it just shows a oneplus logo
I do have access to fastboot though (i hope that leaves some hope)
I have tried the MegaUnbrickGuide here in the forum but i wasn't able to install the drivers i need for that method
One more thing whenever i try
Code:
fastboot boot recovery.img
i get the "remote dtb not found" message
Does that have to do with developer options not being unlocked?
Any ideas on how to just get some form of working os installed on the device
(i dont care wheter rooted or not at this point have been trying stuff for hours now)
regards
Jan
First download Minimal ADB and Fastboot and install it.
Go into fastboot mode.
1. Re-unlock your bootloader using the command - fastboot oem unlock
2. After doing that, download the latest version of TWRP(which at the time of writing this is 3.1.0) and rename it to 'recovery.img'
3. Open a command window in the place you have downloaded the recovery by pressing the shift key and right clicking and then choosing the option Open Command WIndow Here... Flash the recovery using the command fastboot flash recovery recovery.img
4. Boot into it using the command fastboot boot recovery.img
5. If it still gives 'remote dtb not found' then follow this guide: https://forum.xda-developers.com/oneplus-x/help/opx-remote-dtb-solution-t3480274
6. If it boots into recovery, your phone is now fine and go ahead and flash whatever ROM you want.
Cheers!
please some can you help with the porting of twrp for this phone
even some help with official firmware v217 then we can root with magiusk and recovery image
this phone has the mtk processor MT6765
Infinix hot 8 pliss, i can instal twrp
Yes, help sir ? :good:
Infinix Hot 8 Need Support
Please really need support for root and twrp for this device,, this device is really nice,,
guys again some try and get the firmware v217 so we can extract the boot.img for magisk
i hope a update is coming soon plan to get thta to find this boot.img
online the v174 firmware is not the same
OTA Update for Infinix
X650C-H626DE-P-191005V224.zip
240Mb
capture via usbdebugg
http://www.mediafire.com/file/24dmq3hk7wbu6b3/X650C-H626DE-P-191005V224.zip/file
Mtk(mediatek) processor devices are not supported by custom ROM developers. Don't expect custom rom support for hot infinix 8. Sorry.
Did anyone try Readback in SP Flash tool? So far, I have not been successful in doing so.
got it
To unlock Bootloaded withour error in Fastboot use command
fastboot flashing unlock
and then on the phone select volume up key to acknowledge
phone is booted into fresh android
and now rooted with magisk
thnx guys all done for now
off topic if you have a pihole on rasberry pie you can see that this phone is THE WORST i do mean UTTER DISREGUARD for user privacy and send EVERYTHING and i mean EVERTHING home to china
included is user app usage
user data
crash analytics
with root i will NOW TAKE CARE to THIS
any one needs boot.img modified for firmware 216 for magisk root will upload it
darylzero said:
phone is booted into fresh android
and now rooted with magisk
thnx guys all done for now
off topic if you have a pihole on rasberry pie you can see that this phone is THE WORST i do mean UTTER DISREGUARD for user privacy and send EVERYTHING and i mean EVERTHING home to china
included is user app usage
user data
crash analytics
with root i will NOW TAKE CARE to THIS
any one needs boot.img modified for firmware 216 for magisk root will upload it
Click to expand...
Click to collapse
Screenshots
and UPLOAD THE orignal+patched BOOT.img
With complete VERSION INFO
Sent from my Infinix-X650C using XDA Labs
Boot.img Magisk patched
https://www.mediafire.com/file/0nzyd8t9yu8vqpd/magisk_patched.img/file
Original Boot.img
http://www.mediafire.com/file/32gtumg9q6r46bi/boot.img/file
downloaded the uploaded firmware from google drive v236 i think
used techno tool to flash this to phone to VERIFY the firmwareis good and proper
once the firmware was verified and phone booted i uploaded the boot.img from that firmware v236 to magisk on phone and patched it
got this patched boot.img back to computer
now for the flashing part
install ADB drivers
on phone activate usb debug and oem unlock in developer mode in settings
check ADB is working and sees phone n computer via usb with command
"adb shell"
shouls show a valid response indicating phone is ADB ready
next get it into Fastboot mode with command
"adb reboot bootloader"
wait till phone reboots into fastboot mode check fastboot mode is active with this command
"fastboot devices"
now to unlock bootloader in fastboot else it will give error
use command
"fastboot flashing unlock "
this will also give a acknowledge on the phone that BOOTLOADER will now b unlocked and press volume up to agree
once bootloader is unlocked in fast boot next it to flash the magisk boot.img patched
i have uploaded this to medifire please download
place this file named
magisk_patched.img on desktop
use command boot
"fastboot flash boot (( need to drag and drop the file magisk_patched.img from desktop here ))"
wait till magic is done
after use to
"fastboot reboot "
after phone reboot it will b factory reset and rooted check root with magisk manager installed
root checked verified
https://www.mediafire.com/view/a2ivwbm530gdb9v/Screenshot_20191210-122733.png/file
Thank you very much.
My phone now has root access
Are you installed TWRP Recovery in your device.???
darylzero said:
Boot.img Magisk patched
https://www.mediafire.com/file/0nzyd8t9yu8vqpd/magisk_patched.img/file
Original Boot.img
http://www.mediafire.com/file/32gtumg9q6r46bi/boot.img/file
downloaded the uploaded firmware from google drive v236 i think
used techno tool to flash this to phone to VERIFY the firmwareis good and proper
once the firmware was verified and phone booted i uploaded the boot.img from that firmware v236 to magisk on phone and patched it
got this patched boot.img back to computer
now for the flashing part
install ADB drivers
on phone activate usb debug and oem unlock in developer mode in settings
check ADB is working and sees phone n computer via usb with command
"adb shell"
shouls show a valid response indicating phone is ADB ready
next get it into Fastboot mode with command
"adb reboot bootloader"
wait till phone reboots into fastboot mode check fastboot mode is active with this command
"fastboot devices"
now to unlock bootloader in fastboot else it will give error
use command
"fastboot flashing unlock "
this will also give a acknowledge on the phone that BOOTLOADER will now b unlocked and press volume up to agree
once bootloader is unlocked in fast boot next it to flash the magisk boot.img patched
i have uploaded this to medifire please download
place this file named
magisk_patched.img on desktop
use command boot
"fastboot flash boot (( need to drag and drop the file magisk_patched.img from desktop here ))"
wait till magic is done
after use to
"fastboot reboot "
after phone reboot it will b factory reset and rooted check root with magisk manager installed
root checked verified
https://www.mediafire.com/view/a2ivwbm530gdb9v/Screenshot_20191210-122733.png/file
Click to expand...
Click to collapse
Are you installed TWRP Recovery in your device.i want TWRP recovery.can I install TWRP recovery after root my device.tel me.
https://forum.xda-developers.com/android/help/infinix-hot-8-t3986799/post80598837
Check this Thread for complete guide on
* UNLOCKING-BOOTLOADER
* ROOTING
* TWRP
* OPTIMIZATION
* UN-BRICKING
* CUSTOM-ROM
Sent from my Infinix-X650C using XDA Labs
How can I root my infinix hot 8 v x650D
Misbahu said:
How can I root my infinix hot 8 v x650D
Click to expand...
Click to collapse
Same method as I stated above.. just use compatible TWRP
Sent from my Infinix-X650C using XDA Labs
darylzero said:
Boot.img Magisk patched
https://www.mediafire.com/file/0nzyd8t9yu8vqpd/magisk_patched.img/file
Original Boot.img
http://www.mediafire.com/file/32gtumg9q6r46bi/boot.img/file
downloaded the uploaded firmware from google drive v236 i think
used techno tool to flash this to phone to VERIFY the firmwareis good and proper
once the firmware was verified and phone booted i uploaded the boot.img from that firmware v236 to magisk on phone and patched it
got this patched boot.img back to computer
now for the flashing part
install ADB drivers
on phone activate usb debug and oem unlock in developer mode in settings
check ADB is working and sees phone n computer via usb with command
"adb shell"
shouls show a valid response indicating phone is ADB ready
next get it into Fastboot mode with command
"adb reboot bootloader"
wait till phone reboots into fastboot mode check fastboot mode is active with this command
"fastboot devices"
now to unlock bootloader in fastboot else it will give error
use command
"fastboot flashing unlock "
this will also give a acknowledge on the phone that BOOTLOADER will now b unlocked and press volume up to agree
once bootloader is unlocked in fast boot next it to flash the magisk boot.img patched
i have uploaded this to medifire please download
place this file named
magisk_patched.img on desktop
use command boot
"fastboot flash boot (( need to drag and drop the file magisk_patched.img from desktop here ))"
wait till magic is done
after use to
"fastboot reboot "
after phone reboot it will b factory reset and rooted check root with magisk manager installed
root checked verified
https://www.mediafire.com/view/a2ivwbm530gdb9v/Screenshot_20191210-122733.png/file
Click to expand...
Click to collapse
I have an Infinix Hot 8 X650B.
I am trying to root the device. I have installed all ADB required files and the drivers.
The computer detects the drivers and the device is showing in ADB Device list.
But it's not being listed in fastboot devices check, and no fastboot command is working.
Please what can I do?
Papichoolo said:
I have an Infinix Hot 8 X650B.
I am trying to root the device. I have installed all ADB required files and the drivers.
The computer detects the drivers and the device is showing in ADB Device list.
But it's not being listed in fastboot devices check, and no fastboot command is working.
Please what can I do?
Click to expand...
Click to collapse
Try Installing driver's on an different computer and check if it loads to fastboot.
Sent from my Infinix-X650C using XDA Labs
AshhRED said:
Try Installing driver's on an different computer and check if it loads to fastboot.
Sent from my Infinix-X650C using XDA Labs
Click to expand...
Click to collapse
I tried on a different PC with Windows 7, same issue. ADB Loads and detects, but fastboot doesn't.
It shows under ADB Devices but when I type, adb reboot bootloader.
The phone goes into fastboot mode, but isn't detected when using command, fastboot devices.
Drivers and eveything is setup correct on it too.
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
I have read multiple guides how to root android phones but it was without success.
I saw that you have to enable DSB bugging and OEM however I dont have the option to unlock OEM on my phone.
I downloaded many files including SDK with twrp.img, Odin with twrp.tar? (is it the same as twrp.img?).
So the first step is to install twrp on my phone. The first thing I did was using odin program. I added the twrp tar file to the AP section but it didnt work. It says: Installation failure. You need to unlock your device to install a custom OS. What do I need to do here?
I also tried cmd command by clicking it in the SDK map containing the twrp.img of my model.
I wrote adb devices to check whether there is an android phone connected to my PC -> I saw my phone on the cmd screen.
Then I wrote adb reboot bootloader -> it rebooted my phone.
Next, I wrote fastboot flash recovery twrp-3.1.0-0-zeroltezt.img -> it says waiting for any devices?
Can someone help me? I have been stuck for 8 hours only to try to install twrp in my phone....
Hi! I would like to mod my AC2003 upgraded to oxygenos 12.1 (android 12) version AC2003_11_F.13
Could you please tell me the steps to proceed? I can't find a guide that answers all my questions ... Do I need to unlock the bootloader first? Then the recovery and the rom? I would be oriented towards the pixel experience, can it be a good choice? Does it support 2 sims? How to do with the root for the bank's applications? Many questions, and nowhere to start ... Thanks in advance
Copy all important phone data, it will be wiped!
- Download adb platform tools here
- Download adb drivers here
- Enable developer settings -> Enable OEM unlock.
- Reboot into Fastbot mode: Turn off the phone, hold down vol+ and vol-, then power on the phone.
- Connect the phone to the computer, run "fastboot devices". If not recognized, ensure driver is installed in the device manager, install from downloaded adb drivers.
- Run "fastboot oem unlock", accept in the phone prompt, the phone will be wiped!
- Boot again in fastboot, flash the recovery: "fastboot flash recovery recovery_file".
- Unplug the USB, I found the recovery to not work properly if the usb was already plugged in before booting.
- Boot into recovery mode: Hold Vol+ and turn on the phone.
- Go to Update... Install from ADB, connect the USB.
- In the computer, run "adb sideload rom_file"
- I'd recommend issuing a factory reset after this, just in case.
- NEVER run "fastboot oem lock" with modded system, it'll brick your phone! (Can be fixed, but just don't do it)
- Enjoy
Ex. for Pixel rom:
- Recovery file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.img
- ROM file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.zip
I wasn't happy with custom roms. Too many bugs. So I also post how to return to factory:
- Download fastboot ROM from here, unzip file.
- Boot the phone into fastboot mode, connect the USB, run "flash-all.bat", it'll take a while, it'll reboot afterwards
- You're now with stock system. You can upgrade to OOS11/12 using the zips from here, also check F.13, copying them to the phone, going to the updater and selecting "Local update".
- Better do OOS10->OOS11->OOS12, just in case! I'd stay with OOS 11.1.11.11, OOS12 is a battery drainer!
- Ensure to make a factory reset when done with updating.
- Now you're stock, you can also relock the bootloader by booting into fastboot and running "fastboot oem lock".
Be aware that you will miss some camera features with any custom rom... Full camera features are only available with the stock rom..
Thats why I moved back to stock rom and debloated all unuseable stuff...
But a custom rom offers many other opportunities that the stock rom doesn't have...
dabyd64 said:
Copy all important phone data, it will be wiped!
- Download adb platform tools here
- Download adb drivers here
- Enable developer settings -> Enable OEM unlock.
- Reboot into Fastbot mode: Turn off the phone, hold down vol+ and vol-, then power on the phone.
- Connect the phone to the computer, run "fastboot devices". If not recognized, ensure driver is installed in the device manager, install from downloaded adb drivers.
- Run "fastboot oem unlock", accept in the phone prompt, the phone will be wiped!
- Boot again in fastboot, flash the recovery: "fastboot flash recovery recovery_file".
- Unplug the USB, I found the recovery to not work properly if the usb was already plugged in before booting.
- Boot into recovery mode: Hold Vol+ and turn on the phone.
- Go to Update... Install from ADB, connect the USB.
- In the computer, run "adb sideload rom_file"
- I'd recommend issuing a factory reset after this, just in case.
- NEVER run "fastboot oem lock" with modded system, it'll brick your phone! (Can be fixed, but just don't do it)
- Enjoy
Ex. for Pixel rom:
- Recovery file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.img
- ROM file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.zip
I wan't happy with custom roms. Too many bugs. So I also post how to return to factory:
- Download fastboot ROM from here, unzip file.
- Boot the phone into fastboot mode, connect the USB, run "flash-all.bat, it'll take a while, it'll reboot afterwards
- You're now with stock system. You can upgrade to OOS11/12 using the zips from here, also check F.13, copying them to the phone, going to the updater and selecting "Local update".
- Better do OOS10->OOS11->OOS12, just in case! I'd stay with OOS 11.1.11.11, OOS12 is a battery drainer!
- Ensure to make a factory reset when done with updating.
- Now you're stock, you can also relock the bootloader by booting into fastboot and running "fastboot oem lock".
Click to expand...
Click to collapse
Wow! You wrote the bible for the beginner ... I don't know how to thank you for your patience, now I have a great starting point
I've a problem, fastboot can't see my device... I've installed the oneplus drivers, but windows continues to use Microsoft's drivers. I tried to update the drivers from the device manager indicating as drivers those installed in the Oneplus folder, but windows keeps telling me not to find drivers compatible with an x64 system in that folder. I also tried to disable the digital signature check, without success. This is on both windows 11 and windows 10 PCs. I've also enabled debug usb...
There's no problem using Windows drivers.
Isn't the phone recognized as fastboot device?
Attach device manager screenshot.
dabyd64 said:
There's no problem using Windows drivers.
Isn't the phone recognized as fastboot device?
Attach device manager screenshot.
Click to expand...
Click to collapse
It seems you're not in fastboot Mode?
Do you see this screen?
dabyd64 said:
It seems you're not in fastboot Mode?
Do you see this screen?
Click to expand...
Click to collapse
The cable was the problem...Now i've tried with it's original cable and yes, i can see it! Thank you so much...
dabyd64 said:
Copy all important phone data, it will be wiped!
- Download adb platform tools here
- Download adb drivers here
- Enable developer settings -> Enable OEM unlock.
- Reboot into Fastbot mode: Turn off the phone, hold down vol+ and vol-, then power on the phone.
- Connect the phone to the computer, run "fastboot devices". If not recognized, ensure driver is installed in the device manager, install from downloaded adb drivers.
- Run "fastboot oem unlock", accept in the phone prompt, the phone will be wiped!
- Boot again in fastboot, flash the recovery: "fastboot flash recovery recovery_file".
- Unplug the USB, I found the recovery to not work properly if the usb was already plugged in before booting.
- Boot into recovery mode: Hold Vol+ and turn on the phone.
- Go to Update... Install from ADB, connect the USB.
- In the computer, run "adb sideload rom_file"
- I'd recommend issuing a factory reset after this, just in case.
- NEVER run "fastboot oem lock" with modded system, it'll brick your phone! (Can be fixed, but just don't do it)
- Enjoy
Ex. for Pixel rom:
- Recovery file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.img
- ROM file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.zip
I wasn't happy with custom roms. Too many bugs. So I also post how to return to factory:
- Download fastboot ROM from here, unzip file.
- Boot the phone into fastboot mode, connect the USB, run "flash-all.bat", it'll take a while, it'll reboot afterwards
- You're now with stock system. You can upgrade to OOS11/12 using the zips from here, also check F.13, copying them to the phone, going to the updater and selecting "Local update".
- Better do OOS10->OOS11->OOS12, just in case! I'd stay with OOS 11.1.11.11, OOS12 is a battery drainer!
- Ensure to make a factory reset when done with updating.
- Now you're stock, you can also relock the bootloader by booting into fastboot and running "fastboot oem lock".
Click to expand...
Click to collapse
After flash recovery, when i go to the recovery mode, i see this mex:
"The current image (boot/recovery) have been destroted and can not boot. Please flash the correct image or contact customer service to fix"
Fortunately i have solved with msm....
It's a known thing that you can flash on any custom ROM only if you're on oxygenOS 10 or 11 version. Respectively, if you are on android 12, then you first need to flash with unbrick tool (msmtool) anroid 10 (EU/Global/India) or android 11 (India).
gorro8 said:
It's a known thing that you can flash on any custom ROM only if you're on oxygenOS 10 or 11 version. Respectively, if you are on android 12, then you first need to flash with unbrick tool (msmtool) anroid 10 (EU/Global/India) or android 11 (India).
Click to expand...
Click to collapse
Hi,
I am on OS12 stock currently.
At which stage of the guide posted above I need to use the unbrick tool ?
Many thanks
Hi bro.
If you want to flash any custom ROM, then you need to go to unbrick tools thread, download drivers and MSM tool firmware and step by step flash it.
After that flash custom rom you need also with it instruction in the thread.