Hi
I recently upgraded a Honor 5c to Nougat(which works)NRD90M test keys build. I did this through Flashfire to try and preserve root. It failed(what a surprise).
The device is recognised now with 'fastboot devices', by running ADB using root in Linux.
I can get into bootloader screen using fastboot and have unlocked the phone AGAIN to be sure. BUT, cannot flash TWRP which is vital. The error now is:
Sending 'boot.img' (24464 KB) OKAY [ 0.869s]
Booting FAILED (remote: 'Command not allowed') fastboot: error: Command failed
This suggests the phone is locked which is absurd. I think this is a permission problem within Android, it that possible?
It doesn't matter how I'm going to root, if I can't communicate the whole thing is usesless.
The same issue continues with ADB in Win10
Any thoughts hear, because I've trawled Google.
thanks
To clarify things: ADB and Fastboot are 2 completly different things. Fastboot deals with device's bootloader, whereas ADB deals with device's Android OS.
Run this command sequence
Code:
fastboot devices
fastboot getvar all 2>%TEMP%\phoneinfo.txt
fastboot reboot
type "%TEMP%\phoneinfo.txt" | more
which will get you a list of various variables on the phone with model and such useful things.
jwoegerbauer said:
To clarify things: ADB and Fastboot are 2 completly different things. Fastboot deals with device's bootloader, whereas ADB deals with device's Android OS.
Run this command sequence
Code:
fastboot devices
fastboot getvar all 2>%TEMP%\phoneinfo.txt
fastboot reboot
type "%TEMP%\phoneinfo.txt" | more
which will get you a list of various variables on the phone with model and such useful things.
Click to expand...
Click to collapse
Excuse if this format is incorrect
Thanks for that.
ADB and Fastboot are 2 completly different things
Click to expand...
Click to collapse
Sure
fastboot devices
Click to expand...
Click to collapse
MQH4C17330000094 fastboot
fastboot getvar all 2>%TEMP%\phoneinfo.txt
Click to expand...
Click to collapse
Returns to prompt
fastboot reboot
Click to expand...
Click to collapse
Works
type "%TEMP%\phoneinfo.txt" | more
Click to expand...
Click to collapse
getvar:all FAILED (remote: 'Command not allowed')
Finished. Total time: 0.005s
Same thing again
Cliff
cliffhanger54 said:
getvar:all FAILED (remote: 'Command not allowed')
Click to expand...
Click to collapse
That a Fastboot cmd does not work ( e.g. error Command not allowed ) is not unusual because Fastboot is different from version to version and also depends on how OEM/Carrier implemented it.
Again:
Bootloader and Android OS are different things, as this is same on PC where UEFI/BIOS and Windows OS are different things, too. A device's bootloader doesn't depend on any permissions granted within device's OS. A bootloader is a kind of software that runs as soon as you start up your phone. It tells the phone which programs are loading in order to make your phone run smoothly. This software packages all the instructions that are supposed to boot the Android OS, and initializes hardware and serves as security checkpoint.
Don't mix things up.
BTW:
Whether device's bootloader is unlockable / is already unlocked or not is stored in system file named build.prop.
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then unlocking bootloader is supported otherwise it's not.
or
Code:
fastboot devices
fastboot oem device-info
If "Device unlocked: true" is shown then bootloader is unlockedd.
jwoegerbauer said:
That a Fastboot cmd does not work ( e.g. error Command not allowed ) is not unusual because Fastboot is different from version to version and also depends on how OEM/Carrier implemented it.
Again:
Bootloader and Android OS are different things, as this is same on PC where UEFI/BIOS and Windows OS are different things, too. A device's bootloader doesn't depend on any permissions granted within device's OS. A bootloader is a kind of software that runs as soon as you start up your phone. It tells the phone which programs are loading in order to make your phone run smoothly. This software packages all the instructions that are supposed to boot the Android OS, and initializes hardware and serves as security checkpoint.
Don't mix things up.
BTW:
Whether device's bootloader is unlockable / is already unlocked or not is stored in system file named build.prop.
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then unlocking bootloader is supported otherwise it's not.
or
Code:
fastboot devices
fastboot oem device-info
If "Device unlocked: true" is shown then bootloader is unlockedd.
Click to expand...
Click to collapse
Thanks again for answering. I understand what you say. I've used Linux for 20 years and understand the differences. But where does this leave us/me. I should be able to flash TWRP into the recovery partition surely? Or are we dependent on software versions here as you say? It would be relatively easy in Linux and of course Android is based on it.
cliffhanger54 said:
I should be able to flash TWRP into the recovery partition surely?
Click to expand...
Click to collapse
TWRP completely removes device's default /recovery partition if it exists ( exists only on A-only Android devices), TWRP creates its own in device's /boot partition.
To flash TWRP on A-only ( or on current active boot slot if it's an A/B ) device
Code:
fastboot devices
fastboot flash boot <PATH_ON_PC_TO_YOUR_TWRP_IMAGE_HERE>
jwoegerbauer said:
TWRP completely removes device's default /recovery partition if it exists ( exists only on A-only Android devices), TWRP creates its own in device's /boot partition.
To flash TWRP on A-only ( or on current active boot slot if it's an A/B ) device
Code:
fastboot devices
fastboot flash boot <PATH_ON_PC_TO_YOUR_TWRP_IMAGE_HERE>
Click to expand...
Click to collapse
Thanks I think I've tried this one. I do get a different response though:
'fastboot: error: cannot get boot partition size'
I've seen suggestions that formating the boot partition is required - sounds extreme.
Why not simply re-flash device's Stock ROM to restore it to its original state ?
:good:
Sukrus said:
:good:
Click to expand...
Click to collapse
Yes wouldn't that be great. Have tried that from the beginning when I couldn't flash TWRP.
Put the Update.app on the SDcard, reboot the phone, hold down the buttons(tried them all), Bingo, it always takes me to eRecovery and how useless that is.
I have backups of Marshmallow with TWRP and Flashfire, which is why I took the flash TWRP route.
Wish I'd never upgaded now, although was forced to because of banking.
thanks
@cliffhanger54
I have noticed that current thread basically is a duplicate of this thread you started on XDA some days ago, too.
jwoegerbauer said:
@cliffhanger54
I have noticed that current thread basically is a duplicate of this thread you started on XDA some days ago, too.
Click to expand...
Click to collapse
Yes, couldn't really get anyone to answer, needed more info. Apologies. Will cease other question
Cliff
cliffhanger54 said:
Yes, couldn't really get anyone to answer, needed more info. Apologies. Will cease other question
Cliff
Click to expand...
Click to collapse
Right. After many attempts at other things I became convinced this was a locked bootloader problem despite the phone saying it was unlocked. Anyway have persisted in unlocking the phone several times and am now at a screen saying 'Your device is unlocked' but it also says 'you device is booting now'. But that's as far as it goes. If I turn the phone off it comes back to this screen and holding the power button+-volume also comes back to this screen, i.e I can't turn it off. How do I get back to the bootloader/fastboot mode or is this a genuine brick?
thanks
Cliff
cliffhanger54 said:
Right. After many attempts at other things I became convinced this was a locked bootloader problem despite the phone saying it was unlocked. Anyway have persisted in unlocking the phone several times and am now at a screen saying 'Your device is unlocked' but it also says 'you device is booting now'. But that's as far as it goes. If I turn the phone off it comes back to this screen and holding the power button+-volume also comes back to this screen, i.e I can't turn it off. How do I get back to the bootloader/fastboot mode or is this a genuine brick?
thanks
Cliff
Click to expand...
Click to collapse
Okay finally solved it. Let the battery run down as all I was getting was a bootloop. I was then able to get into fastboot mode with the necessary keys. From here i flashed TWRP but this required numerous attempts with different versions, finally got '3.1.1 venus' to load and the rest was straight forward!
thanks to everyone
Related
When I plug my phone in fastboot on to my pc, fastboot detects it. When I then try to run a command, it says:
FAILED (command write failed (Unknown error))
finished. total time: 0.580s
After this, the screen of my phone just stays the same, except no button input works, not even holding down the power button for 10 seconds. The only way I can get out of this, is by actually pulling out the battery. After this, my phone works normally again.
How can i make the command of my PC get to my phone?
kayaven said:
When I plug my phone in fastboot on to my pc, fastboot detects it. When I then try to run a command, it says:
FAILED (command write failed (Unknown error))
finished. total time: 0.580s
After this, the screen of my phone just stays the same, except no button input works, not even holding down the power button for 10 seconds. The only way I can get out of this, is by actually pulling out the battery. After this, my phone works normally again.
How can i make the command of my PC get to my phone?
Click to expand...
Click to collapse
Do commands (like adb install .apk) work fine when phones turned on or does it freeze still ?
Will_Xda said:
Do commands (like adb install .apk) work fine when phones turned on or does it freeze still ?
Click to expand...
Click to collapse
adb will detect my phone, but as soon as I run a command, it freezes and no writing will come trough, so no they do not work.
Oh, and for some more info on my phone:
- The bootloader hasn't been unlocked;
- Running Android 4.1.1
- Already wiped it (backup gone wrong so I lost all stuff :/)
Could it be because my USB ports are just lame? (USB 2.0)
kayaven said:
adb will detect my phone, but as soon as I run a command, it freezes and no writing will come trough, so no they do not work.
Oh, and for some more info on my phone:
- The bootloader hasn't been unlocked;
- Running Android 4.1.1
- Already wiped it (backup gone wrong so I lost all stuff :/)
Could it be because my USB ports are just lame? (USB 2.0)
Click to expand...
Click to collapse
It will only work on USB2.0 for me and not on USB3.0. what operating system are you using ?
What are you trying or wish to do?
Which command?
Will_Xda said:
It will only work on USB2.0 for me and not on USB3.0. what operating system are you using ?
Click to expand...
Click to collapse
I'm using Windows 7 Ultimate x64, fastboot and adb are both running normal for the rest.
RuudM said:
What are you trying or wish to do?
Which command?
Click to expand...
Click to collapse
Well, i am trying to unlock my bootloader, but any command that writes to the phone will freeze it.
Unlocking bootloader: If I remember well, you need to have an unlock-code from HTC. Try the steps on this page from HTC Developer. Click on the picto 'unlock bootloader'.
Tutorial for the rest can be found here
RuudM said:
Unlocking bootloader: If I remember well, you need to have an unlock-code from HTC. Try the steps on this page from HTC Developer. Click on the picto 'unlock bootloader'.
Tutorial for the rest can be found here
Click to expand...
Click to collapse
I've already done that, but the command I need to run in order to get that code freezes it.
Sorry if the next is a bit 'low-profile' but it is difficult to tell where you are stuck
Just to be sure: I assume you have selected the right phone and downloaded the right fastboot-version (Windows, Linux or OsX) on HTC.com. Unpacked size of fastboot for Windows is (at this moment, from HTC) 183.651 bytes.
Phone: you are in the bootloader-screen, and (for Windows) you have a DOS-box opened on your desktop and able to execute the fastboot command.
What happens if you type in 'fastboot devices'? Does it respond?
If so, typing 'fastboot oem get_identifier_token' should respond as well. Or is that the part where you are getting stuck?
RuudM said:
Sorry if the next is a bit 'low-profile' but it is difficult to tell where you are stuck
Just to be sure: I assume you have selected the right phone and downloaded the right fastboot-version (Windows, Linux or OsX) on HTC.com. Unpacked size of fastboot for Windows is (at this moment, from HTC) 183.651 bytes.
Phone: you are in the bootloader-screen, and (for Windows) you have a DOS-box opened on your desktop and able to execute the fastboot command.
What happens if you type in 'fastboot devices'? Does it respond?
If so, typing 'fastboot oem get_identifier_token' should respond as well. Or is that the part where you are getting stuck?
Click to expand...
Click to collapse
I've got the original Android SDK fastboot, but that won't really matter, I suppose. The rest is the same. Furthermore, when i use the 'fastboot devices', it responds, but when i use something like 'fastboot oem get_identifier_token', it says FAILED (command write failed (Unknown error)), and the phone gets stuck.
I really have no idea why this is happening, i will now test if the official HTC fastboot works... :fingers-crossed:
-----------
Omg I'm an idiot, i just had it open on hboot and not fastboot >.<
I didn't know the difference Thanks a lot anyway everyone!
I neglected to flash vendor.img when installing the M preview and did "fastboot reboot" after flashing everything else manually. Now whenever my N9 boots, it only shows the Google logo. I've tried going into Recovery and wiping/factory reset with no success.
Is there any way I can a) flash the remaining vendor.img; or b) return my N9 back to 5.1.1?
shaiwon said:
I neglected to flash vendor.img when installing the M preview and did "fastboot reboot" after flashing everything else manually. Now whenever my N9 boots, it only shows the Google logo. I've tried going into Recovery and wiping/factory reset with no success.
Is there any way I can a) flash the remaining vendor.img; or b) return my N9 back to 5.1.1?
Click to expand...
Click to collapse
Boot back into your bootloader, and "fastboot flash vendor vendor.img"
That's what I'm trying to do but I don't know how to connect the tablet with my Mac to run the command in fastboot. When I type "adb devices", it no longer lists my device as attached. Would appreciate instructions in how to connect again through USB to flash the vendor image.
shaiwon said:
That's what I'm trying to do but I don't know how to connect the tablet with my Mac to run the command in fastboot. When I type "adb devices", it no longer lists my device as attached. Would appreciate instructions in how to connect again through USB to flash the vendor image.
Click to expand...
Click to collapse
There's not enough information here to help you.
So if I understand well, you previously were able use ADB and fastboot on this computer?
Does your computer recognize your N9? Can you see the N9's SDcard from your Mac?
If yes, then is "USB debugging" enabled in Developer Options?
When you try ADB devices, did you click the "always allow/trust connection with this computer" popup on your N9's screen?
cam30era said:
There's not enough information here to help you.
So if I understand well, you previously were able use ADB and fastboot on this computer?
Does your computer recognize your N9? Can you see the N9's SDcard from your Mac?
If yes, then is "USB debugging" enabled in Developer Options?
When you try ADB devices, did you click the "always allow/trust connection with this computer" popup on your N9's screen?
Click to expand...
Click to collapse
Before flashing the preview image using fastboot, I had USB debugging enabled. When rebooting after flashing all the files (except vendor.img), the tablet would power on and show only the "Google" logo and go no further. So I tried booting into fastboot and recovery, but when I plug in the tablet to my Mac and try "adb devices", it doesn't recognize it being connected.
Since I cannot turn the N9 on fully to go into Developer Options and enable USB debugging again, how do I connect it to my Mac again so I can flash the remaining file and complete the setup?
In the same boat here. Enabled USB debugging, OEM unlocked, flashed the device manually (build failed, did the .img's sequentially), now the device gets stuck on the Google logo at boot. Attempted recovery and reset, no joy. Gets stuck on the Google logo. When back in the Fastboot menu, meanwhile, my Mac - previously able to see the device via adb - lists no connected devices so I can't reflash.
I assume I'm going to have to go the RMA route?
sogrady said:
In the same boat here. Enabled USB debugging, OEM unlocked, flashed the device manually (build failed, did the .img's sequentially), now the device gets stuck on the Google logo at boot. Attempted recovery and reset, no joy. Gets stuck on the Google logo. When back in the Fastboot menu, meanwhile, my Mac - previously able to see the device via adb - lists no connected devices so I can't reflash.
I assume I'm going to have to go the RMA route?
Click to expand...
Click to collapse
Hi, sogrady...
You don't need ADB to flash anything... All you need is FASTBOOT and a working connection to your PC/Mac.
----
ADB debugging is irrelevant when it comes to running fastboot flash commands. ADB is only meaningful when running a fully booted version of Android OR when running a Recovery... Stock or Custom.
Providing your Nexus 9 bootloader is unlocked, you should be able to run fastboot flash commands without problem.
To confirm you have a working fastboot connection, and with the device booted into it's bootloader, type...
Code:
fastboot devices
This should return your N9s unique device id... If it doesn't, you likely have a driver/connectivity issue... but it has nothing to do with ADB debugging - On or Off.
Rgrds,
Ged.
sogrady said:
In the same boat here. Enabled USB debugging, OEM unlocked, flashed the device manually (build failed, did the .img's sequentially), now the device gets stuck on the Google logo at boot. Attempted recovery and reset, no joy. Gets stuck on the Google logo. When back in the Fastboot menu, meanwhile, my Mac - previously able to see the device via adb - lists no connected devices so I can't reflash.
I assume I'm going to have to go the RMA route?
Click to expand...
Click to collapse
I thought so too, but I found a solution.
Check out my post here: http://forum.xda-developers.com/nexus-9/help/help-boot-loop-os-n-t3122167#post61051773
Hopefully, it helps.
Unfortunately, fastboot can't see the device either:
Code:
ferro$ fastboot devices
ferro$
This is with the Nexus 9 connected and in fastboot mode. As for it being a driver issue, everything that I've seen suggests that specific to Windows, and I'm on Mac. Is that accurate, or are there drivers I need to install on a Mac?
GedBlake said:
Hi, sogrady...
To confirm you have a working fastboot connection, and with the device booted into it's bootloader, type...
Code:
fastboot devices
This should return your N9s unique device id... If it doesn't, you likely have a driver/connectivity issue... but it has nothing to do with ADB debugging - On or Off.
Rgrds,
Ged.
Click to expand...
Click to collapse
sogrady said:
Unfortunately, fastboot can't see the device either:
Code:
ferro$ fastboot devices
ferro$
This is with the Nexus 9 connected and in fastboot mode. As for it being a driver issue, everything that I've seen suggests that specific to Windows, and I'm on Mac. Is that accurate, or are there drivers I need to install on a Mac?
Click to expand...
Click to collapse
No drivers on a Mac. And the command should be "./fastboot devices". You need the "period" and "backslash" before the command.
cam30era said:
No drivers on a Mac.
Click to expand...
Click to collapse
So assuming fastboot doesn't see the device, then, I'm out of options and looking at an RMA?
cam30era said:
And the command should be "./fastboot devices". You need the "period" and "backslash" before the command.
Click to expand...
Click to collapse
Why would this be? I've placed both adb and fastboot both in the machine's PATH, so executing them with the ./ prefix is unnecessary. Certainly worked just fine the first time around without them.
sogrady said:
So assuming fastboot doesn't see the device, then, I'm out of options and looking at an RMA?
Why would this be? I've placed both adb and fastboot both in the machine's PATH, so executing them without the ./ preference is unnecessary. Certainly worked just fine the first time around without them.
Click to expand...
Click to collapse
Hi, again sogrady....
Don't give up so easily...
When you say "I'm out of options", what options have you tried exactly?
Another computer? Another USB cable? A different USB port on a computer?? There could be several variables causing problems for you.
One other point, are you certain your Nexus 9 is fully booted into fastboot mode, and not just the HBOOT bootloader...
You should see something like my attached screenshot...
If you see this, then all things being equal, fastboot commands should work without problems.
Hope this helps...
Rgrds,
Ged.
sogrady said:
Why would this be? I've placed both adb and fastboot both in the machine's PATH, so executing them with the ./ prefix is unnecessary. Certainly worked just fine the first time around without them.
Click to expand...
Click to collapse
Update the binaries, they may be outdated.
You can use my script for this: http://forum.xda-developers.com/android/general/adb-fastboot-binaries-os-x-inclusive-t2941205
Happy to report success - well, partial success anyway. Per @GedBlake, I swapped in a new machine and cable, and per @simmac I made sure my binaries were updated. As it turns out, this was unnecessary: my mistake, after looking at @GedBlake's screenshot was that I was not down in fastboot, I was in hboot. As soon as dropped down into fastboot, voila:
Code:
Macintosh-3:volantis-MPZ44Q sogrady$ fastboot devices
HT4CRJT01274 fastboot
So, problem solved I figured. I re-downloaded the M image to my new machine, checked the MD5 and attempted to flash all. As with the previous iteration, it failed due to a new (to me) set of errors:
Code:
error: cannot load 'system.img'
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
ERROR: usb_write failed with status e00002ed
ERROR: usb_write failed with status e000404f
sending 'vendor' (147127 KB)...
ERROR: usb_write failed with status e000404f
FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
ERROR: could not get pipe properties
ERROR: could not get pipe properties
rebooting...
ERROR: usb_write failed with status e0004061
finished. total time: 0.000s
Macintosh-3:volantis-MPZ44Q sogrady$ fastboot reboot
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting...
ERROR: usb_write failed with status e00002ed
At which point I figured that I would simply load the *.img's manually, one by one. But fastboot had by this point become squirrelly about even seeing the machine.
Code:
Macintosh-3:volantis-MPZ44Q sogrady$ fastboot devices
ERROR: could not get pipe properties
ERROR: could not get pipe properties
???????????? fastboot
At which point I decided to simply see if I could go back and load 5.1.1 and deal with M later. While that flash-all.sh script failed as well, I was able to put 5.1.1 back on via the following manually:
Code:
fastboot flash bootloader bootloader-flounder-3.44.1.0123.img
fastboot reboot-bootloader
unzip image-volantis-lmy47x.zip
cd image-volantis-lmy47x
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
fastboot reboot
At which point the device booted back up into 5.1.1. So big thanks folks for helping me restore an otherwise bricked machine! Much appreciated. Hope the steps help anyone else caught in a bricking cycle.
And if anyone has any idea why my M load failed, I'd be all ears because I would like to load that up at some point. For now, though, I'm just happy to have a working machine again.
Update: Ok, strike the above. Re-ran that process for the Android M build and it went off without a hitch this time, although the setup wizard failed so the build itself looks to be buggy. That at least is not related to the flashing process, however, so proceed to flash M onto the device if you're willing to try and get past those issues.
I just waited 360 hours and unlocked a new Mi8 dipper as I have done with 5 Xiaomi phones previously. Everything looks normal. MiUI v10 says it is unlocked. With USB debugging activated the device code shows up with the 'adb devices' command. However when it comes to actually modifying the bootloader in Fastboot mode things look very locked in place. In the terminal console 'abd devices' command shows no devices. Similarly when trying to load TWRP with 'fastboot flash recovery TWRP. img' command it searches to find no device and ends with a fault. I have tried with 3 different USB-C cables on three different PC's. Two with Windows 10 with ADB tools and another on current ArchLinux with 4.20 kernel and ADB tools.
Incidentally, my wife has an untouched and therefore unlocked Pocophone F1. It does the same thing as above.
Has anyone heard of such a tbing? Is it possible that Xiaomi thinks this phone has been unlocked when in fact the bootloader is still locked?
As far as a fix goes,the unlock tool says its locked and won't try again to unlock it. This would be utterly painful were it not for Lawnchair launcher coming to the user experience rescue.
It is your computer, try to reinstall adn, driver, etc,..
If bootloader is locked, you still can type fastboot devices, but cannot flash anything with the error that you dont have permission to edit partiton.
khanhdx said:
It is your computer, try to reinstall adn, driver, etc,..
If bootloader is locked, you still can type fastboot devices, but cannot flash anything with the error that you dont have permission to edit partiton.
Click to expand...
Click to collapse
Thanks. Will try again in different variations. A few questions:
1. Is it advisable or not advisable to use a USBv3 or 3.1 port instead of USBv2 ?
2. I have tried a few different Windows 10 drivers from various sources. Can you recommend any specific driver for Xiaomi?
Thanks for helping. I will be very disappointed if I can't mod this phone.
p-we said:
Thanks. Will try again in different variations. A few questions:
1. Is it advisable or not advisable to use a USBv3 or 3.1 port instead of USBv2 ?
2. I have tried a few different Windows 10 drivers from various sources. Can you recommend any specific driver for Xiaomi?
Thanks for helping. I will be very disappointed if I can't mod this phone.
Click to expand...
Click to collapse
I think no different between USB2 and USB3 in this case.
Try uninstall all driver and app related to xiaomi.
Then Disable Signed Driver Enforcement.
Then install latest Miflash: http://en.miui.com/a-234.html (file at step 1)
Then open Mi Unlock folder (the one u found MiUnlock.exe), hold Shift + right click, select open PowerShell here.
Type cmd, enter.
Reboot phone to fastboot, connect to pc.
Type fastboot devices, enter.
khanhdx said:
I think no different between USB2 and USB3 in this case.
Try uninstall all driver and app related to xiaomi.
Then Disable Signed Driver Enforcement.
Then install latest Miflash: http://en.miui.com/a-234.html (file at step 1)
Then open Mi Unlock folder (the one u found MiUnlock.exe), hold Shift + right click, select open PowerShell here.
Type cmd, enter.
Reboot phone to fastboot, connect to pc.
Type fastboot devices, enter.
Click to expand...
Click to collapse
I think I'm close. I installed MIFlash and installed drivers. I now see the device ID in Windows PowerShell in fastboot mode which I did not have before:
C:\Users\wdirk\Downloads\miflash_unlock-en-3.3.827.31\miflash_unlock_en_3.3.827.31>fastboot devices
46265bfe fastboot
But when I enter 'fastboot flash recovery twrp.img' (the twrp.img file is in the same directory), the phone immediately goes to another mode (no fastboot logo with very small text on top left of screen) and nothing happens. So fastboot sees the device but will not write twrp recovery. Ideas?
So I tried Minimal ADB and Fastboot again. Positive that the device shows up:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
46265bfe fastboot
But goes into blank screen with very small text on top left with more inforation this time:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (41796 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
p-we said:
I think I'm close. I installed MIFlash and installed drivers. I now see the device ID in Windows PowerShell in fastboot mode which I did not have before:
C:\Users\wdirk\Downloads\miflash_unlock-en-3.3.827.31\miflash_unlock_en_3.3.827.31>fastboot devices
46265bfe fastboot
But when I enter 'fastboot flash recovery twrp.img' (the twrp.img file is in the same directory), the phone immediately goes to another mode (no fastboot logo with very small text on top left of screen) and nothing happens. So fastboot sees the device but will not write twrp recovery. Ideas?
So I tried Minimal ADB and Fastboot again. Positive that the device shows up:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
46265bfe fastboot
But goes into blank screen with very small text on top left with more inforation this time:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (41796 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
Click to expand...
Click to collapse
I never face any case like this. So maybe i can help you.
Try install different version of TWRP maybe can help..
ShafiX94 said:
Try install different version of TWRP maybe can help..
Click to expand...
Click to collapse
Very strange but I followed your steps on another PC in exactly the same way and now it has flashed TWRP successfully. It did require using blue USB3 port
Thank-you! :good:
Glade to hear you solved it.
For the record: I had the exact same problem as yours. If I recall correctly, the only thing I had to do was to rename the recovery file to: recovery.img then wait a minute or so. Which is strange, but worked.
First tried to boot Pitchblack recovery when it succeeded then tried it with TWRP (recovery.img).
If anyone finds themselves here. Go to https://forum.xda-developers.com/mi-8/how-to/guide-to-issues-flashing-unlocked-mi8-t3911389
p-we said:
If anyone finds themselves here. Go to https://forum.xda-developers.com/mi-8/how-to/guide-to-issues-flashing-unlocked-mi8-t3911389
Click to expand...
Click to collapse
I am glad that you sorted your issue.
But I can assure you that the issue was strictly caused by your PC. It truly should not matter which USB port you use. We have 3 Mi8 in our house and I have unlocked 2 of them using an older laptop with a broken usb 3.0 port.
For the benefit of others who may experience this issue.
Always. remove peripheral devices from the PC such as an external hard drive, when perform tasks such as unlocking the bootloader or unbricking a phone.
Windows should be up to date and I can tell you that professionally, we absolutely require that people temporarily disable windows defender and antivirus when attempting to resolve these kinds of issues, as you are indeed affecting the bootloader of the device.
Windows antivirus will often remove files that it miscategorises as a virus. In example, if you attempt to download and install the All In One Tool, windows defender will neuter the software 90% of the time.
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
first of i apologise if i have bad english
ok so i had this device for some time and decited to root it (my first time rooting a phone). And i need to unlock bootloader to flash stuff and i have all necessary things on my pc (platform tools,drivers,) everything seems to be working but as soon as i get into bootloader the only command that works is "fastboot devices" Any other commands dont work. I tried everything online and this is my only other thing left to do. I've been researching for 2 days at this point and i am almost certain that the commands are disabled by the company itself (like huawei) did anybody else ever root/unlock bootloader for this device because i didnt find any actual root guide for the particular device (besides from the auto generated ones like https://rootguia.com/how-to-flash-caterpillar-cat-s31/ https://mobilewithdrivers.com/unlock-bootloader/cat-s31-16gb-2gb-ram )
The exact error is:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
(and this error is for every single command that uses fastboot besides from fastboot devices. Adb works just fine)
I tried:
reinstalling drivers
installing drivers that are "prepared" for the cat s31
changing cable
changing port to usb 2.0
reinstalling platform tools (from official google site)
checking device manager for the device (it shows up as android bootloader interface)
trying alternative oem unlock commands (fastboot oem unlock, fastboot flashing unlock and 2 other commands that i cant remember rn)
having oem unlocking and usb debugging enabled from the developer options
in my opinion the only explanation is the commands being disabled by default and even if it was it wouldnt be known if it was since most people dont root or purchase this device
please help me out here
fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
or
command finished but unlocking not allowed?
you can try to dump ROM, maybe it's possible to unlock bootloader on devinfo partition
https://github.com/bkerler/edl
aIecxs said:
fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
or
command finished but unlocking not allowed?
you can try to dump ROM, maybe it's possible to unlock bootloader on devinfo partition
https://github.com/bkerler/edl
Click to expand...
Click to collapse
sorry i forgot to mention im running android 8.1 oreo on this device and devinfo partition method will not work according to what i read
Never mind. anyway, if you dump phone in edl mode (or download stock ROM somewhere else) you can search aboot for device specific fastboot oem commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com
aIecxs said:
Never mind. anyway, if you dump phone in edl mode (or download stock ROM somewhere else) you can search aboot for device specific fastboot oem commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com
Click to expand...
Click to collapse
what do you mean by dump phone into edl mode do i download one of these https://ministryofsolutions.com/2022/01/cat-s31-edl-firmware-android-8-1-official-rom.html and install it from recovery mode and try to get it in edl mode and will it not work if i dont dump
just extract that ROM you found
aIecxs said:
just extract that ROM you found
Click to expand...
Click to collapse
and do what. im new to the rooting stuff
find the file aboot.mbn (or similar) and analyze for fastboot commands
aIecxs said:
find the file aboot.mbn (or similar) and analyze for fastboot command
Click to expand...
Click to collapse
so i downloaded the file and these are the things in the firmware file (attachement)
i cant find a file that looks or resambles aboot.mbn
it's emmc_appsboot.mbn so download strings for windows (see link post #4) and try to find fastboot commands, maybe you are lucky and find the proper command to unlock bootloader.
edit: not sure about Windows 10/11 comes with strings binary (powershell?)
aIecxs said:
it's emmc_appsboot.mbn so download strings for windows (see link post #4) and try to find fastboot commands, maybe you are lucky and find the proper command to unlock bootloader.
edit: not sure about Windows 10/11 comes with strings binary (powershell?)
Click to expand...
Click to collapse
sooo turns out win11 strings commands are kinda different or broken (probably not im just dumb) i just used notepad with ctrl+f and couldnt find anything besides the text that says are you sure you want to unlock bootloader but that is probably not related since i didnt find any commands or anything. So im actually going to attach the emmc_appsboot.mbn i know it looks sketchy you dont have to download it its totally understandable but if you do please do give it a check and respond. I want to get this done one way or another its 1 am i want to sleep ;(
could it be true that they made a truly un unlockable unrootable device
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
maybe there is more in secondary bootloader sbl1.mbn
aIecxs said:
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
Click to expand...
Click to collapse
trust me i have tried many many many many times and only got a
FAILED (remote: 'unknown command')
fastboot: error: Command failed
edit: the only place oem unlock is mentioned is a text that says oem unlock not allowed which might be default text by android or whatever but cat devs somehow messed it up somehow??
aIecxs said:
I had a look but there are no fastboot commands in it. However "oem unlock" is mentioned, so the usual fastboot oem unlock should work.
maybe there is more in secondary bootloader sbl1.mbn
Click to expand...
Click to collapse
just saw the edit i will check now
nope nothing related no oem unlock no fastboot no flashing no flash nothing is mentioned ill attach it if you want to look
oem unlock not allowed is standard text if one forgot to enable oem unlocking in developer options in android settings.
maybe flash this ROM maybe it is unlockable?
aIecxs said:
oem unlock not allowed is standard text if one forgot to enable oem unlocking in developer options in android settings.
maybe flash this ROM maybe it is unlockable?
Click to expand...
Click to collapse
from recovery using the flash firmware with adb option??
edit: i meant apply update from adb
edit2: what if i hard reset from recovery would that reset the firmware?
edl firmware cannot flashed from recovery. power off phone, press both volume keys and plug in usb-cable. check VID/PID from windows device manager. if you see device ID (05c6:9008) the phone is in EDL mode. you can now use EDL tool (post #2) and backup current ROM. then you can flash other ROM.
aIecxs said:
It's edl firmware cannot flashed from recovery
Click to expand...
Click to collapse
so what do i download that can be flashed from recovery