I was using a kingroot(One click root) app to root my moto E2 (4G-LTE) and it crashed in the middle and my phone is not booting up
when ever i m trying to switch it on i m getting message" hab check failed for boot". its getting stuck to it after displaying motorola logo. I tried other boot options such as
normal powerup
recovery
factory
barcodes
bp tools
qcom
but all this didnt worked.
messages i m getting are
hab checked failed for boot
failed to validate boot image
Fast boot reason : Fall-through from normal boot mode .
then it displays following
AP Fastboot FlashMode (Secure)
BL: 80.20(sha-76fb222, 2015-12-09 07:35:50)
Baseband: M8916_2020629.41.03.21.51R SURNIA_EMEA_DSDS
Product/Variant: surnia XT1521 8gb P3
Serial Number: TA38501LL4
CPU: MSM8916
eMMC: 8GB Samsung RV=07 PV=01 TY=57
DRAM: 1024mb Samsung S8 SSRAM DIE=4gb
console [null]: null
battery: ok
Device is LOCKED. Status code: 0
Software status: official
Transfer Mode: USB Connected (Connected the USB)
and i toggled up and down volume button and enter in to recovery mode but it doesn't have any command only image of Android with red ! on it belly and after few minutes it goes back to the starting screen automatically
after googling the issues, i installed adb and fastboot to unlock the bootloader
fastboot oem get_unlock_data
I pasted the lock code in Motorola’s official page and received the unlock code
fastboot oem unlock UNIQUE_KEY_FROM_EMAIL
but it showing this error
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.025s
As I can't boot and entered into GUI of android. is there is anyway to enable the "Allow OEM unlock" from developer optiont through some other source
And i tried this too
fastboot -w -u
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.096s]
erasing 'cache'...
OKAY [ 0.018s]
finished. total time: 0.121s
Or Is there any way to bring my phone back in working condition
Thanks
rupeshchan said:
I was using a kingroot(One click root) app to root my moto E2 (4G-LTE) and it crashed in the middle and my phone is not booting up
when ever i m trying to switch it on i m getting message" hab check failed for boot". its getting stuck to it after displaying motorola logo. I tried other boot options such as
normal powerup
recovery
factory
barcodes
bp tools
qcom
but all this didnt worked.
messages i m getting are
hab checked failed for boot
failed to validate boot image
Fast boot reason : Fall-through from normal boot mode .
then it displays following
AP Fastboot FlashMode (Secure)
BL: 80.20(sha-76fb222, 2015-12-09 07:35:50)
Baseband: M8916_2020629.41.03.21.51R SURNIA_EMEA_DSDS
Product/Variant: surnia XT1521 8gb P3
Serial Number: TA38501LL4
CPU: MSM8916
eMMC: 8GB Samsung RV=07 PV=01 TY=57
DRAM: 1024mb Samsung S8 SSRAM DIE=4gb
console [null]: null
battery: ok
Device is LOCKED. Status code: 0
Software status: official
Transfer Mode: USB Connected (Connected the USB)
and i toggled up and down volume button and enter in to recovery mode but it doesn't have any command only image of Android with red ! on it belly and after few minutes it goes back to the starting screen automatically
after googling the issues, i installed adb and fastboot to unlock the bootloader
fastboot oem get_unlock_data
I pasted the lock code in Motorola’s official page and received the unlock code
fastboot oem unlock UNIQUE_KEY_FROM_EMAIL
but it showing this error
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.025s
As I can't boot and entered into GUI of android. is there is anyway to enable the "Allow OEM unlock" from developer optiont through some other source
And i tried this too
fastboot -w -u
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.096s]
erasing 'cache'...
OKAY [ 0.018s]
finished. total time: 0.121s
Or Is there any way to bring my phone back in working condition
Thanks
Click to expand...
Click to collapse
this is moto e1 section in forum this is not for moto e2..and you have to unlock bootloader if u want root or install custom rom..this is not mtk devices in mtk devcies this kingroot works ..u cant root or install using kingroot ...just ask in moto e2 section:silly::silly:
Flash (through fastboot)stock image for your device.
That's it.
I hope there must be a stock image for your variant in moto e 2015 forum.
-z3r0- said:
Flash (through fastboot)stock image for your device.
That's it.
I hope there must be a stock image for your variant in moto e 2015 forum.
Click to expand...
Click to collapse
Thank you very much for this! Worked perfect
Found the stock image (MOTO E2 (4G-LTE)) Indian Version here : motoe2015customs.blogspot.ae/2016/02/stock-rom-60-marshmallow-surnia-xt1521.html
I flashed only following and my phone boot up back to normal
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
rupeshchan said:
Thank you very much for this! Worked perfect
Found the stock image (MOTO E2 (4G-LTE)) Indian Version here : motoe2015customs.blogspot.ae/2016/02/stock-rom-60-marshmallow-surnia-xt1521.html
I flashed only following and my phone boot up back to normal
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
One question dude, were you on marshmallow before trying kingroot?
Yes bro!!
rupeshchan said:
Yes bro!!
Click to expand...
Click to collapse
Okay then flash Systemless SuperSu to root.
Will you explain "how to" step by step? If possible?? Or share the link, please
First of allunlock your phone's bootloader, here's a guide : http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Then download latest twrp recovery from here : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
Flash it through the commands you used for stock recovery.
Download latest supersu from here and flash it in twrp : http://download.chainfire.eu/supersu
-z3r0- said:
First of allunlock your phone's bootloader, here's a guide : http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Then download latest twrp recovery from here : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
Flash it through the commands you used for stock recovery.
Download latest supersu from here and flash it in twrp : http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
Thanks a lot. :fingers-crossed:
help me
rupeshchan said:
Thank you very much for this! Worked perfect
Found the stock image (MOTO E2 (4G-LTE)) Indian Version here : motoe2015customs.blogspot.ae/2016/02/stock-rom-60-marshmallow-surnia-xt1521.html
I flashed only following and my phone boot up back to normal
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
same problem happened to me
model is moto e xt-1521
i am not able to go dev settings
jhn
a bit similer with this case
my friend bought it 20 days ago and he unlock it
but he cant flash twrp as like guides
he had no expirience before this
so i get tablet and tried to solve the problem but
fastboot doesnt work properly
fastboot devices/reboot/device-info works
but
fastboot flash recovery twrp.img/ flash boot boot.img(guide on carbon rom)/boot twrp.img/and etc that for flashing or change any system
does not work
massage like failed(long link/bigger than max allowed)
changing everytime i try
i though there might some issues when my friend unlock the bootloader
so i 'fastboot oem lock' and try to unlock again
but from then fastboot not work properly
can be boot or 'adb reboot fastboot' to fastboot
but it become unknown device on windows device manager
fastboot command not work
when mi flash try to detect device, fastboot mode end and 'press any key to power off' screen came out
some times it working for few seconds so i try unlock with official xiaomi tool but tool said 'already unlocked'
right after i locked bootloader i used 'fastboot oem device-info' and checked bootloader is locked
i can switch oem unlock on/off in developer option but it doesnt change anything
i searched as i can and edl mode looks last
but few things to consider
1. its official chinese rom and working now
2. i dont know broken fastboot can be restored with flashing rom with edl (i flash rom with update app in settings but not solved)
3. adb reboot edl doesnt work it just rebooted(should teardown it but i dont know what pin to short)
the reason why i trying to install custom rom(or eu rom) is my friend and i not live in native english country
hope i get some help
thx
Ryzen CPU?
thE_29 said:
Ryzen CPU?
Click to expand...
Click to collapse
ryzen 1, 2, intel sandy etc
tried all i got
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
KrakmanCz said:
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
Click to expand...
Click to collapse
nope
cant go into edl mode until i teardown it
miflash 2018 doesnt connect with pad on fastboot mode
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
chocodesk said:
ryzen 1, 2, intel sandy etc
tried all i got
Click to expand...
Click to collapse
Ok, when you also tried Intel.. But Ryzen CPUs have major problems with the flash tool and the tablet. Would not do anything on Ryzen PCs.
KrakmanCz said:
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
Click to expand...
Click to collapse
on basic
with was detected as fastboot before
but know its unknown on device manager
update driver doesnt work
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Dannyboy3210 said:
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Click to expand...
Click to collapse
i tried 2.0 and 3.0
not work
tablet owner decide to use it on stock chinese rom
not in my hand now
$ adb reboot bootloader
List devices on fastboot :
$ fastboot devices
XXXXXX fastboot
Check if bootloader is unlocked :
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.003s
Flash TWRP recovery :
$ fastboot flash recovery recovery.img
Sending 'recovery' (54400 KB) OKAY [ 1.540s]
Writing 'recovery' OKAY [ 0.410s]
Finished. Total time: 1.952s
Reboot your device
$ fastboot reboot
Rebooting
Finished. Total time: 0.000s
I installed TWRP on MIUI 10 using this description. On the end , after TWRP installed - I rebooted again to TWRP and installed stock rom at once . I not tested , but theory says , MIUI will reflash recovery if it will be booted in this situation .
Sorry to piggy-back off this post, but I'm having a similar issue with my Mi Pad I just received:
I can boot it into Fastboot mode no problem, even see it listed when I use the "Fastboot devices" command. When I run the OEM info everything comes back true for unlocked.
However, when I try to flash anything I get the max size error or just a "FAILED" and it kicks the Mi Pad to a black screen with the white text "Press any key to shut down".
Any ideas?
*edit*
I've continued testing, and I'm really at a loss here. See the response I'm getting using fastboot:
\minimal_adb_fastboot_1.4.3_portable>fastboot flash boot kernel.img
target didn't report max-download-size
sending 'boot' (15060 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I can transfer files in windows no problem... I can use adb commands no problem... fastboot just doesnt seem to work.
I figured out my issue. You cannot use USB 3 ports to connect and run fastboot commands. I bought a cheap USB 2 hub, ran the cable from that and had no problems at all.
So i just unlocked the device and Re-flashed it with mi flash tool, now the Phone is stuck at Fastboot mode.
i get this
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
finished. total time: 0.001s
Click to expand...
Click to collapse
is my bootloader unlocked?
also when i do set active a, this happens
C:\Users\user>fastboot -set active=a
< waiting for device >
I have tired every solutions i found online still no luck.
Connect the phone to pc and type in "fastboot devices" - do you see any device listed?
Also the correct command is:
fastboot --set-active=a
_mysiak_ said:
Connect the phone to pc and type in "fastboot devices" - do you see any device listed?
Also the correct command is:
fastboot --set-active=a
Click to expand...
Click to collapse
Yes i do but the command doesn't exist in fastboot please help
PS C:\tmp\platform-tools> fastboot --set active=a
C:\adb\fastboot.exe: unrecognised option `--set'
Click to expand...
Click to collapse
Also it says waiting for device it has been more then 30 minutes.
Now the Phone is rebooing at Andriod One Logo.
SpectreZ said:
Yes i do but the command doesn't exist in fastboot please help
Click to expand...
Click to collapse
Again, type it correctly.
In other words, spot the difference
fastboot --set-active=a (what I wrote)
fastboot --set active=a (what you wrote)
Do you see android/fastboot device in your device manager on the PC when you connect it to the PC in fastboot mode?
Edit: also replace fastboot.exe and adb.exe in c:\ADB\ folder as this one is being used. Or remove this folder from Windows PATHS.
_mysiak_ said:
Again, type it correctly.
In other words, spot the difference
fastboot --set-active=a (what I wrote)
fastboot --set active=a (what you wrote)
Do you see android/fastboot device in your device manager on the PC when you connect it to the PC in fastboot mode?
Edit: also replace fastboot.exe and adb.exe in c:\ADB\ folder as this one is being used. Or remove this folder from Windows PATHS.
Click to expand...
Click to collapse
I see Kedacom USB Device - Andorid Bootloader interface.
and i cannot remove the folder from C adb.
I have used mi Flash tool and while checking the log i saw boot was flashed at B so i erased the b boot useing fastboot also a
then I Reflash the B as 1st and A as 2nd the phone was able to make thru Recovery but when i restarted i went back into 0 again
SpectreZ said:
I see Kedacom USB Device - Andorid Bootloader interface.
and i cannot remove the folder from C adb.
I have used mi Flash tool and while checking the log i saw boot was flashed at B so i erased the b boot useing fastboot also a
then I Reflash the B as 1st and A as 2nd the phone was able to make thru Recovery but when i restarted i went back into 0 again
Click to expand...
Click to collapse
Are you sure that phone is in fastboot and not in recovery? What do you see on the phone screen?
You are doing too many things at once, focus on one thing and once you get it solved, move to another one. Also please provide answers to all questions, they are essential for troubleshooting.
1. Reinstall drivers and ADB - https://forum.xda-developers.com/showthread.php?t=2588979
2. Reboot phone in fastboot, connect it to the PC and type in "fastboot devices" - do you see any device connected?
Phone is now Started so what i did was.
* erased system_a
* erased system_b
also
* erased boot_a
* erased boot_b
I think the system is in B now.
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:35a1981490a2
(bootloader) product:laurel_sprout
(bootloader) max-download-size:804261888
(bootloader) kernel:uefi
all:
finished. total time: 0.438s
C:\Users\fahim>
Click to expand...
Click to collapse
and now the device started successfully still i think i messed up and i did everything you said.
Answer: i was on the Bunny screen Fastboot and yes " Fastboot devices " showed my device,
Can you kindly Guide me how do i factory set it? so i won't have any problem i Messed up because i didn't saw the note at StockRom in this forums where something is wrong in slots
C:\Users\fahim>fastboot --set-active-a
fastboot: unknown option -- set-active-a
Click to expand...
Click to collapse
SpectreZ said:
Phone is now Started so what i did was.
* erased system_a
* erased system_b
also
* erased boot_a
* erased boot_b
I think the system is in B now.
and now the device started successfully still i think i messed up and i did everything you said.
Answer: i was on the Bunny screen Fastboot and yes " Fastboot devices " showed my device,
Can you kindly Guide me how do i factory set it? so i won't have any problem i Messed up because i didn't saw the note at StockRom in this forums where something is wrong in slots
C:\Users\fahim>fastboot --set-active-a
fastboot: unknown option -- set-active-a
Click to expand...
Click to collapse
I guess you again did not follow given advice. You are still using old fastboot. In this case use "fastbot set_active a"
_mysiak_ said:
SpectreZ said:
Phone is now Started so what i did was.
* erased system_a
* erased system_b
also
* erased boot_a
* erased boot_b
I think the system is in B now.
and now the device started successfully still i think i messed up and i did everything you said.
Answer: i was on the Bunny screen Fastboot and yes " Fastboot devices " showed my device,
Can you kindly Guide me how do i factory set it? so i won't have any problem i Messed up because i didn't saw the note at StockRom in this forums where something is wrong in slots
C:\Users\fahim>fastboot --set-active-a
fastboot: unknown option -- set-active-aI guess you again did not follow given advice. You are still using old fastboot. In this case use "fastbot set_active a"
Click to expand...
Click to collapse
My Apologies, My Mind was rushing
Which one is the latest? can you tell me? please
Click to expand...
Click to collapse
Click to expand...
Click to collapse
1) update your ADB/Fastboot from the link I provided and use "fastboot --set-active=a"
or
2) keep what you have and use "fastboot set_active a"
_mysiak_ said:
1) update your ADB/Fastboot from the link I provided and use "fastboot --set-active=a"
or
2) keep what you have and use "fastboot set_active a"
Click to expand...
Click to collapse
Oh God thanks it worked, Can you tell me why there is A and B ? i mean 2 slots? also how do i get the device into factory fresh ?
Like the 1st time when i bought this. thank you soo much + Liked
If i use Mi Flash tool again, So am gonna be in Danger again too?
You can use MiFlash, but before flashing you need to make sure that your active partition is A (with commands mentioned before).
To restore to 100% stock:
1. set partition A as active
2. run MiFlash WITHOUT locking bootloader (or run script flash_all.bat)
3. start the phone, if everything works, move to the next step (ONLY IF PHONE WORKS)
4. run MiFlash with bootloader lock (or run script flash_all_lock.bat) or run "fastboot flashing lock"
5. after reboot, your phone should start as if it came from a factory
_mysiak_ said:
You can use MiFlash, but before flashing you need to make sure that your active partition is A (with commands mentioned before).
To restore to 100% stock:
1. set partition A as active
2. run MiFlash WITHOUT locking bootloader (or run script flash_all.bat)
3. start the phone, if everything works, move to the next step (ONLY IF PHONE WORKS)
4. run MiFlash with bootloader lock (or run script flash_all_lock.bat) or run "fastboot flashing lock"
5. after reboot, your phone should start as if it came from a factory
Click to expand...
Click to collapse
Thanks Everything is now great. However what is slot count? and what happens when it hits 0? also i locked the device via fastboot flashing lock.
It should be number of slots. 2 = boot_a + boot_b
It it hits 0, I guess you have serious problem as bootloader doesn't see any boot partition.
More info in the source code: https://android.googlesource.com/pl...otctrl/+/refs/heads/nougat-dev/boot_control.c
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