Related
Ok heres is what happen yesterday, I successfully root my HD XT925 using Dan's motochopper (Thanks Dan!!) no problem at all then I found a bootanimation thread I pick the bootanimation_dna.zip and I went to system/media and rename the original bootanimation.zip to bootanimationOLD.zip, copy the DNA file and rename it to bootanimation.zip, everything OK so far... then I restart my XT925 and it starts doing the DNA bootanimation BUT almost to finish it got stuck!! and since then I was not able to use the phone, I try to recovery, wipe data etc. etc. and nothing it starts booting, show motorola logo then the animation starts and it gets stuck...
so after several hours of unsuccessful tries to get it work and looking into several places, I found the stock firmware (JB 4.1.2 Telcel -MX) I downloaded to flash it and see if that works... bad idea!!
I tried flash the firmware with fastboot and using RSD lite (v6.1.5) with the same results:
fastboot reason: boot menu selected
usb conected
downgrade security version
update gpt_main version failed
preflash validation failed for gpt
now the cell is stuck on fastboot mode, it says: Fastboot Reason: Flash Failure
So I'm overwhelm and I don't know what to do...
a couple of things, I try using the firmware directly as I downloaded and the RSD gave me this error:
"Flailed flashing process. Unknonw fastboot command. (getvar)"
then I read somewhere here at XDA that I should remove a line from the xml fle... <step operation="getvar" var="max-download-size" />
try again and I got this:
"Failed flashing process. 2/22 flash partition "partition_signed" -> Phone returned FAIL.
and the cell shows:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Any idea what I'm doing wrong???
Thakns guys!!
no one?
same problem, help please !
Foxtom, you're spamming many threads. Please stop.
Sent from my RAZR Maxx HD
Since you have an XT925, if you don't mind unlocking your bootloader (through motorola no need for any hacks), you can then flash anything through RSD and it won't fail because of version errors or anything
Sent from my GT-N5110 using XDA Premium 4 mobile app
I personnaly used a self made script to flash stock roms, RSD Lite is always bugging me for instructions like this one.
Here is an example :
Code:
@echo off
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot reboot-bootloader
echo. When the screen comes back on, press any key to continue!
pause
fastboot flash partition partition_signed
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot flash boot boot_signed
fastboot erase cache
fastboot flash system system_signed
fastboot flash recovery recovery_signed
fastboot flash modem modem_signed
fastboot flash devtree devtree_signed
fastboot flash logo logo
fastboot flash cdrom cdrom_signed
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg_signed
fastboot erase cache
fastboot erase tombstones
echo. Press a key to reboot the phone
pause
fastboot reboot
All you have to do, is replace the "xxxx_signed" with the filenames you have in your rom.
And save this in a textfile called "xxxx.bat".
Then (if the fastboot.exe files are in the same folder) execute the script and it will flash your XT925.
I personnaly used that script with the stock rom Retail/France and it worked perfectly.
Tell me if you need more details.
rename the original bootanimation.zip to bootanimationOLD.zip,
here's your problem, if you see tutorials in the themes and apps section, it tell you to rename your old one .bak as in backup
and then paste new bootanimation...try that out!
Hi everyone,
Yesterday I finally got the message that I could update my phone to Lollipop 5.0.2, I downloaded it and pressed install. When it rebooted it started to install but after like 1/3 an error message popped up.
There's not much detail to it, it's just the little android guy laying on his back and above him it says "Error!", that's it. My phone was rooted before, but I unrooted it before installing, I also did a recovery,
I used the phone recovery for this, so not a custom recovery. The bootloader is still unlocked.
I hope there is a solution for this, although I've read quite a few negative things about Lollipop here, I'd still love to try it out.
Cheers.
I'm having same problem.. But i will clean flash stock firmware image 4.4.4 and then try again
eddydc1 said:
I'm having same problem.. But i will clean flash stock firmware image 4.4.4 and then try again
Click to expand...
Click to collapse
Is there a guide somewhere on how to do this?
Having the same issue. After the reboot I opened a shell on the phone via adb and found this in /cache/recovery/last_log:
Code:
Finding update package...
I:Update location: /cache/Blur_Version.210.12.40.falcon_umts.Retail.en.DE.zip
Opening update package...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1462 bytes; signature 1439 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
installing gptupgrade updater extensions
file_contexts path is present in /tmp/file_contexts
mount point :/system location: /dev/block/platform/msm_sdcc.1/by-name/system , file system type :ext4script aborted: Package expects build fingerprint of motorola/falcon_retde/falcon_umts:4.4.4/KXB21.14-L1.40/36:user/release-keys or motorola/falcon_retde/falcon_umts:5.0.2/LXB22.46-28.1/1:user/release-keys; this device has motorola/falcon_retde/falcon_umts:4.4.2/KLB20.9-1.10-1.9.1/1:user/release-keys.
Package expects build fingerprint of motorola/falcon_retde/falcon_umts:4.4.4/KXB21.14-L1.40/36:user/release-keys or motorola/falcon_retde/falcon_umts:5.0.2/LXB22.46-28.1/1:user/release-keys; this device has motorola/falcon_retde/falcon_umts:4.4.2/KLB20.9-
E:Error in /cache/Blur_Version.210.12.40.falcon_umts.Retail.en.DE.zip
(Status 7)
Installation aborted.
Installation aborted.
I:Saving locale "de_DE"
blk: partition "" size 2387968 not a multiple of io_buffer_size 524288
blk: partition "" size 1077248 not a multiple of io_buffer_size 524288
blk: partition "" size 694288384 not a multiple of io_buffer_size 524288
blk: partition "" size 5930614784 not a multiple of io_buffer_size 524288
E:v->blk_device = misc
partition_name = /dev/block/platform/msm_sdcc.1/by-name/misc
qe 1/1
Rebooting...
I find this part particulary interesting:
Code:
this device has motorola/falcon_retde/falcon_umts:4.4.2/KLB20.9-1.10-1.9.1/1:user/release-keys
A little bit further up in the logs it also says:
Code:
ro.build.fingerprint=motorola/falcon_retde/falcon_umts:4.4.2/KLB20.9-1.10-1.9.1/1:user/release-keys
But the fingerprint acording to /system/build.prop is:
Code:
ro.build.fingerprint=motorola/falcon_retde/falcon_umts:4.4.4/KXB21.14-L1.40/36:user/release-keys
Any ideas?
docnetwork said:
A little bit further up in the logs it also says:
Code:
ro.build.fingerprint=motorola/falcon_retde/falcon_umts:4.4.2/KLB20.9-1.10-1.9.1/1:user/release-keys
But the fingerprint acording to /system/build.prop is:
Code:
ro.build.fingerprint=motorola/falcon_retde/falcon_umts:4.4.4/KXB21.14-L1.40/36:user/release-keys
Any ideas?
Click to expand...
Click to collapse
I had the same problem. The reason is, that you have an 4.4.2 recovery.img on your 4.4.4 phone.
I extracted recovery.img from XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip, then flashed that with "fastboot flash recovery recovery.img", then sideloaded the OTA and the update is progressing right now. Root does not seem to affect the OTA update.
Good luck :fingers-crossed:
Success
Thank's for the tip, I imagined something like this would be the problem, but I didn't know what to do about it. So these were my steps:
Download stock image
I took the image from here: https://mega.co.nz/#F!bY8ijBYT!ADhZkHUmbGiWRfLWIO2N7A
Filename: XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip
Extract recovery.img
unzip XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip
Look for recovery.img (MD5: 29f19a6b903ebf58e6fc8e6e7bd0457d)
Reboot into bootloader
adb reboot-bootloader
Flash recovery.img
fastboot flash recovery recovery.img
If this is stuck at "<waiting for device>" check if you can see the device by calling: fastboot devices
For me this showed "no permissions", so I tried: sudo fastboot devices
That gave me my device, so I also called: sudo fastboot flash recovery recovery.img
Which gave me:
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.462s]
writing 'recovery'...
OKAY [ 1.172s]
finished. total time: 1.634s
Reboot the phone
I wanted to select "Normal Powerup" using the volume keys, but pressing the volume key already initiated the reboot.
Trigger the update
Settings -> About the phone -> Softwareupdate (or however it is translated)
This did the trick for me. Good luck for the rest of you!
Permanent solution
-Download 5.0.2 Stock image
https://drive.google.com/file/d/0B5uo5LCdnblrcHJMblF3MlhaUjQ/edit
-Flash it
Paste in CMD (adb) one by one:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
Or
just make a batch file of these codes and execute the batch file
bhumik147 said:
-Download 5.0.2 Stock image
https://drive.google.com/file/d/0B5uo5LCdnblrcHJMblF3MlhaUjQ/edit
-Flash it
Paste in CMD (adb) one by one:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
Or
just make a batch file of these codes and execute the batch file
Click to expand...
Click to collapse
This will wipe the whole device, which is something that I wanted to avoid. But might be an alternative if my earlier solution doesn't work.
docnetwork said:
Thank's for the tip, I imagined something like this would be the problem, but I didn't know what to do about it. So these were my steps:
Download stock image
I took the image from here: https://mega.co.nz/#F!bY8ijBYT!ADhZkHUmbGiWRfLWIO2N7A
Filename: XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip
Extract recovery.img
unzip XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip
Look for recovery.img (MD5: 29f19a6b903ebf58e6fc8e6e7bd0457d)
Reboot into bootloader
adb reboot-bootloader
Flash recovery.img
fastboot flash recovery recovery.img
If this is stuck at "<waiting for device>" check if you can see the device by calling: fastboot devices
For me this showed "no permissions", so I tried: sudo fastboot devices
That gave me my device, so I also called: sudo fastboot flash recovery recovery.img
Which gave me:
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.462s]
writing 'recovery'...
OKAY [ 1.172s]
finished. total time: 1.634s
Reboot the phone
I wanted to select "Normal Powerup" using the volume keys, but pressing the volume key already initiated the reboot.
Trigger the update
Settings -> About the phone -> Softwareupdate (or however it is translated)
This did the trick for me. Good luck for the rest of you!
Click to expand...
Click to collapse
I did it two times with no success. The update went with a reboot and stuck at "no command" logo.
docnetwork said:
This will wipe the whole device, which is something that I wanted to avoid. But might be an alternative if my earlier solution doesn't work.
Click to expand...
Click to collapse
Well the thing is with this error you cant ever update through ota officially, and other option is root flashable file which will ruin the ROM in this case, so you will have to lose data anyway, better flash it clean
I actually did update via ota, the way I wrote in the description. So, I only sideloaded the recovery.img. But maybe I was just lucky, given that it's not working for everyone. In that case it would be interesting to know if the problem with the fingerprint is actually the same.
If you get the Android guy with the red triangle and 'no command' you aren't technically in recovery yet.
(While on the screen with the android guy and red triangle) Hold volume up for 10 seconds, then while still holding volume up, press the power button and release both at the same time.
It's a weird bug, but should be good to go after that.
CodyF86 said:
If you get the Android guy with the red triangle and 'no command' you aren't technically in recovery yet.
(While on the screen with the android guy and red triangle) Hold volume up for 10 seconds, then while still holding volume up, press the power button and release both at the same time.
It's a weird bug, but should be good to go after that.
Click to expand...
Click to collapse
So, what do you do when you are in that recovery screen then? thanks.
runittwiice said:
So, what do you do when you are in that recovery screen then? thanks.
Click to expand...
Click to collapse
If you followed my guide then you only ever enter recovery during the update in stage 6. For me the update started automatically. Did you flash stock recovery first?
docnetwork said:
If you followed my guide then you only ever enter recovery during the update in stage 6. For me the update started automatically. Did you flash stock recovery first?
Click to expand...
Click to collapse
Yes I followed every step you posted, but my phone won't update. Did you wipe?
It's really weird, because before when my phone was a custom rom etc, I got the official update notification from Motorola, but it wouldn't update and now that I have flashed the official files back onto it, I don't get the update notification anymore no matter how many times I press "Check for updates", the Motorola Update Service is updated..
It's really weird..
runittwiice said:
Yes I followed every step you posted, but my phone won't update. Did you wipe?
Click to expand...
Click to collapse
No, I did not wipe. I did exactly the steps that I described earlier. And I also still got the official OTA notification once I updated the recovery image. Additionally my phone was rooted and bootloader unlocked, when I did all she steps. However I needed to get root back one the update to lollipop was done.
Hi all.
I somehow managed to get my LG-P505R in what I believe to be a soft-bricked state.
I can access fastboot mode as well as emergency mode. I have tried to flash the stock kdz file following probably just about all guides I could locate here. I have also tried to flash recovery.img (clockworkmod image also), boot.img and system.mbn via fastboot but am still unable to boot into either system or recovery. I have all of the .mbn files extracted from the original kdz file and I would like to try to flash them through fastboot. My issue is that I do not know which mbn file goes to which partition. I also am not too sure of the exact partition names to flash.
I have tried the obvious ones like, fastboot flash amss amss.mbn. The result is
sending 'partition' (0 KB)...
OKAY [ 0.046s]
writing 'partition'...
FAILED (remote: unknown partition name)
finished. total time: 0.096s
same result with all except for recovery, boot, system and splash.
Here is a list of the files extracted from kdz if the info can help.
amss.mbn
amsshd.mbn
appsboot.mbn
appsboothd.mbn
boot.img
oemsbl.mbn
oemsblhd.mbn
partition.mbn
qcsbl.mbn
qcsblhd_cfgdata.mbn
recovery.img
splash.img
system.mbn
the system.mbn is originally extracted in 3 different files, system.mbn.0, system.mbn.1 and system.mbn.2
Does anyone have any insight on how I might be able to recover?
Hi, i just bought a Google Pixel from Ebay an tried to install an factory image for Android 9 from the Google Website. After fastboot the flash-all.sh (ive got Ubuntu) it got stuck a on the bootscreen (The Google Logo flashes in an instance and the Screen goes black again). Unfortunally the device is locked again (bootloader ist locked), so adb is not working. fastboot works but when i install some other factory images from the google website the problem with the flashing bootscreen reappears.
Loading into bootloader works:
Product/Variant: sailfish-US-PVT
Serial Number FA72H0300560
CPU: MSM8996SG-AB 0x10001
UFS: 32 GB Samsung
DRAM:4096MB Hynix LPDDR4
Boot-slot: a
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Could anyone help?
Thanks in advance.
Not sure but I think U can try booting into TWRP using "fastboot flash recovery twrp" command in CMD and than switch boot slot to b, my pixel is in the same situation - I can't boot into slot a and switching to b works
oh sry, the command is "fastboot boot path/to/twrp.img"
Thanks for your help, but it didn't work.
When I try to fastboot with following commands, it says:
sudo ./fastboot boot twrp-3.2.3-1-sailfish.img
Code:
Downloading 'boot.img' OKAY [ 0.785s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 0.963s
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Double-check the checksum of the downloaded file.
Open the flash-all.sh file in a text editor, and manually run each of the flash commands individually. See if any of them throw an error.
You might also try to install the OTA.
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
ArchArch said:
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
Click to expand...
Click to collapse
You need to re-unlock your bootloader first, then. Try fastboot flashing unlock .
No luck.
sudo ./fastboot flashing unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.007s
sudo ./fastboot oem unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.038s
ArchArch said:
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Click to expand...
Click to collapse
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Levan_i said:
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Click to expand...
Click to collapse
He's using linux. The reason his flashes have been unsuccessful is because the bootloader is locked.
Tanks for your efforts so far...
Just for clarification: The initial plan was to root my device, according to the XDA-Guide for rooting an Pixel XL Android 9.0 (with the Files for my "Sailfish"-Pixel) https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
First when I bought the Pixel the "OEM Unlock"-Option in the Developers-Menu was greyed out.
So i tried out, beneath some other guides, the XDA-Guide for unlocking a Verizon Pixel and it worked. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
So I thought its an VerizonPixel, installed an Verizon Image from the Google Website, got always the message at bootup that an unlocked bootloader is some sort of threat, closed the Bootloader and the flashing bootscreen-problem began…
i wnat to root https://www.xda-developers.com/root/
when i try
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
i also try
fastboot oem unlock
it show
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
what should i do ??
chatofking said:
i wnat to root https://www.xda-developers.com/root/
when i try
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
Rename the patched boot.img to "boot.img", then place the patched .img in your fastboot folder on PC then type:
fastboot flash boot boot.img
When you place the file in your fastboot folder, you don't need to include the path to the file in the command, it automatically looks for the file in the fastboot folder by default when you do not enter a path. Renaming the file to "boot.img" isn't necessarily required, but, it does simplify things for fastboot and makes the command easier to remember and type.
The same applies if you want to flash a system.img, recovery.img, etc.. Just change the name of the file to "system.img" or "recovery.img" and place it/them in your fastboot folder and it simplifies your commands to:
fastboot flash system system.img
And
fastboot flash recovery recovery.img
Also, try this for the failed command
FAILED (remote: Unable to open fastboot HAL): Unlock Bootloader Fix
In this tutorial, we will show you the steps to fix the FAILED (remote: Unable to open fastboot HAL) error when unlocking the bootloader.
www.droidwin.com
now i got same message
D:\platform-tools>fastboot flash boot boot.img
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Droidriven said:
Also, try this for the failed command
FAILED (remote: Unable to open fastboot HAL): Unlock Bootloader Fix
In this tutorial, we will show you the steps to fix the FAILED (remote: Unable to open fastboot HAL) error when unlocking the bootloader.
www.droidwin.com
Click to expand...
Click to collapse
im already try this verify cmd location, install fastboot driver & boot fastboot mode nothing change.
Code:
D:\platform-tools>fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
what should i do ??
chatofking said:
i wnat to root https://www.xda-developers.com/root/
when i try
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
You've to unlock device's bootloader. Hence 1st of all if you want to manage the / operate on the bootloader you have to move device into fastboot mode and then run on device if it's launched 2015 or later
Code:
fastboot flashing unlock
[code]
instead of the outdated
[code]
fastboot oem-unlock
xXx yYy said:
You've to unlock device's bootloader. Hence 1st of all if you want to manage the / operate on the bootloader you have to move device into fastboot mode and then run on device if it's launched 2015 or later
Code:
fastboot flashing unlock
[code]
instead of the outdated
[code]
fastboot oem-unlock
Click to expand...
Click to collapse
when i try
D:\platform-tools>fastboot flashing unlock
it show
Code:
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
i use https://developer.android.com/studio/releases/platform-tools
what should i do ??
The platform tools you actually use are meant to be used with Google devices only.
Use the Android USB-tools provided by your device's manufacturer.
xXx yYy said:
The platform tools you actually use are meant to be used with Google devices only.
Use the Android USB-tools provided by your device's manufacturer.
Click to expand...
Click to collapse
i use mtp driver
update Portable Devices to MTP USB Device
but when i enter fastboot mode
it become Android Device Android Bootloader Interface.
where is extracted the driver package folder ?? https://www.xda-developers.com/download-android-usb-drivers/
I'm having simular issue with my specter 8 tablet. I unlock the bootloader and give me the normal prompt. I go back do everything else and will execute reboot devices ect. However won't flash patch_boot.img brings up message
FAILED (remote: 'Download is not allowed on locked devices').