Related
Greetings!
Sadly I was able to brick my Nexus 4. I used Nexus 4 Toolkit. After that not worked (same error just not such detailed) I used a Guide with a "flash-all.bat". The Flash-all.bat throw following error:
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
archive does not contain 'boot.sig'
error: out of memory
So I whiped all Data in hope to fix it but no way.
After Flashing 4.3 (same Error as above) I was able to use my Handy again on 4.3
So it seems I have some error. Would be great if someone can throw me some tips how to fix all.
Ehnoah said:
Greetings!
Sadly I was able to brick my Nexus 4. I used Nexus 4 Toolkit. After that not worked (same error just not such detailed) I used a Guide with a "flash-all.bat". The Flash-all.bat throw following error:
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
archive does not contain 'boot.sig'
error: out of memory
So I whiped all Data in hope to fix it but no way.
After Flashing 4.3 (same Error as above) I was able to use my Handy again on 4.3
So it seems I have some error. Would be great if someone can throw me some tips how to fix all.
Click to expand...
Click to collapse
Firstly is it unlocked? "fastboot oem unlock"
Secondly if you don't mind losing you data you might try.
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
Hey Thanks for reply! Yes it is unlocked. I will try what you talked about.
Timboe73 said:
Firstly is it unlocked? "fastboot oem unlock"
Secondly if you don't mind losing you data you might try.
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
Click to expand...
Click to collapse
NVM: It seems switch USB-Port helped. Dunno why.
Looking at the errors I don't think so though, seems more like something else with fastboot. You should try flashing each image files individually instead of using a toolkit.
edit: yeah i figure.
sent from tapatalk
try other a usb port
sometimes is able to be these problems
Hello I'm trying to flash stock ROM via adb, specifically cust.img, boot.img, system.img, Because I've bricked my phone and it stuck on huawei logo, but when i try to flash, i got the following error "FAILED (remote: Command not allowed)"
Code:
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (304183 KB)...
OKAY [195.875s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 195.899s
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21690 KB)...
OKAY [ 13.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.694s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [314.622s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 314.665s
Please how I can unbrick my phone and reinstall the firmware
Obs. My bootloader is unlocked and I'm using TWRP recovery
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens.
In later days, we've got a lot of troubleshooting topic opened up with your problem, the users cannot flash even with unlocked bootloader, and yet, there's no real solution to them.
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
daviddosa said:
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens..
Click to expand...
Click to collapse
Yes, it shows PHONE unlocked in red name, and I've made the root using an app called kingroot
I've tried to erase cache and userdata using adb but I can't, still got the same error "FAILED (remote: Command not allowed)"
I can't make dload method because I don't have stock recovery, and I can't flash the stock recovery using adb because its keep saying "FAILED (remote: Command not allowed)".
I don't know what to do
sokkoban said:
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
Click to expand...
Click to collapse
I'm using windows 7 is this moment, maybe I try to flash using Linux later
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
daviddosa said:
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
Click to expand...
Click to collapse
So I tried to create a flashable zip using the Huawei Update Extractor however, was not possible, it's showing the following message "no suitable files selected. Check profiles.xml"
I've tried also creating flashable zip manually and flash it using TWRP, but TWRP reboot every time I try to flash theses files, that's why I think dload method work only with stock recovery
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
Thanks for the help but this method didn't work, everytime I try to flash the files, I got the same error "FAILED (remote: Command not allowed)” I don't know what is happening my bootloader is unlocked, why I can't flash the files with adb
Code:
target max-download-size: 450MB
sending 'boot' (21690 KB)...
OKAY [ 13.912s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.919s
target max-download-size: 450MB
sending 'recovery' (34264 KB)...
OKAY [ 21.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 21.985s
target max-download-size: 450MB
sending 'cust' (304183 KB)...
OKAY [191.580s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 191.603s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [366.120s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 366.144s
ROM flashed , if all went well
You must be restarted.
If you leave the recovery to hard reset and restart the phone
Created by sokoban. Thank you for using my release
rebooting...
finished. total time: 0.054s
Pressione qualquer tecla para continuar. . .
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
sokkoban said:
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Same issue with Huawei G6-U10
I'm having the same problem with Huawei Ascend G6-U10
Currently running on ROM b146, since it has some issues I was trying to downgrade or upgrade ( there is a b330 out).
I'm not an expert.
This morning I've unlocked the boot loader and then tried to flash a couple of different ROMs and I always get the same error message:
c:\adb>fastboot flash BOOT ./G6-U10verb330/boot.img
target reported max download size of 536870912 bytes
sending 'BOOT' (9696 KB)...
OKAY [ 0.310s]
writing 'BOOT'...
FAILED (remote: Command not allowed)
finished. total time: 0.321s
c:\adb>fastboot oem get-bootinfo
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
I'm guessing this is not a G6-U10 specific issue so if anyone can give any hint it'll be very appreciated.
Thanks.
I have the same problem with a honor 4x.
Rooted with kingroot. We haven't writing permission in /system. That's why we can't install the recovery. If you try to install superSU and update the binary I guess you get an error.
Now the question is: how we can do to make writeble /system with fast boot?
"mount -o rw,remount -t ext3 /dev/block/xxxxxxxxx /system" in terminal doesn't work...
Similar thing happened to me. Even if command for showing unlocked bootloader said it was unlocked that was false because I used Kingroot previously. Only thing that helped was to unlock the bootloader through fastboot again. Then it was really unlocked and I could flash recovery (in my case TWRP) which before I was unable to.
Diego Sousa said:
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Click to expand...
Click to collapse
Have you tried it with linux yet?
And have you used the Update.APP and dload method?
Maybe a driver problem? Have administrator rights? And debug mode on?
Try to connect your phone (power on) to the pc and wait to be recognized. In cmd type this:
Code:
adb devices
It has to show you your serial number right? If doesn't your device is not being recognized by adb.
Next type:
Code:
adb reboot-bootloader
This will restart your phone into fastboot and now you can type "fastboot devices" like first command and it has to show you your serial number again.
Try rebooting into bl with this, not by plugin in the phone, and install the rom again
Huawei P8 Lite
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Have you tried install it in twrp? You don't have a twrp backup of stock rom?
In this case if you go in the Huawei eRecovery you can restore stock rom and twrp will be overwrited downloading the last rom , i tried it with my p8 lite 2017 .
Tuki2 said:
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Click to expand...
Click to collapse
What are you using to go into fastboot mode? Is it ADB from Android SDK?? It turns out that using ADB from Android SDK lets you flash small files but not large files... I suggest you try flashing the file through Minimal ADB & Fastboot
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
i have the same issue as well, but just with Cust.img
Guide for installing new security update with fastboot and with a bootloader-unlocked Pixel XL.
This is basically the same thing as usual but with the new structure.
If you have modified a little the stock android (hosts file, root, kernel, etc.), you may experience a fail in OTA update;
If you have a bootloop/soft brick/not sure of the state of your android system;
This is the solution.
This WILL NOT delete your data and apps. This will remove your custom kernel/root/hosts/recovery through (which is a good thing because it will be clean then).
I assume you already have anything to do fastboot command. If not, see this good thread.
1) Download your system image for Marlin (Pixel XL) on google website.
For November update, there are 3 versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon
2) Unzip the file marlin-nde63v-factory-a66866ba.zip
3) Unzip inside the new directory (marlin-nde63v) the image-marlin-nde63v.zip
4) Reboot into bootloader
Code:
adb reboot bootloader
5) Execute fastboot commands (assuming the bin is on your PATH)
Code:
fastboot flash bootloader bootloader-marlin-*.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
Here we go, you have a fresh unrooted vanilla android with latest security patch.
6) To add TWRP and Root:
Code:
fastboot boot /path/to/twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip
Root thread for more information.
TWRP thread for more information.
** Reserved **
cam30era said:
@firewave,
Thanks for posting the guide. Just like Nexus devices except for the slot files. After unzipping the factory image, I do notice 15 additional files (other than boot, system, vendor, etc) that I've never seen before on a Nexus device. Do you happen to know what those are for, and why we don't flash them if doing a manual fastboot flash?
Thanks, in advance....
Click to expand...
Click to collapse
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.
firewave said:
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.
Click to expand...
Click to collapse
aboot is actually part of the bootloader.
death2all110 said:
aboot is actually part of the bootloader.
Click to expand...
Click to collapse
yep, it's why I'm unsure what to do with. Probably nothing.
I will loopmount the file at home and see.
Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.
wx9kvh said:
Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.
Click to expand...
Click to collapse
In the op in bold, he said it will not erase your data or apps
C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result
dablitzkrieg said:
C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result
Click to expand...
Click to collapse
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
chapelfreak said:
In the op in bold, he said it will not erase your data or apps
Click to expand...
Click to collapse
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.
wx9kvh said:
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.
Click to expand...
Click to collapse
That makes sense, our posts are an hour apart or so.
Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
I appreciate the help. The link you provided me, I've downloaded it, but for some reason cant launch the app after I unzip the file. I've been at this for like 4 hours. I've tried so many different things and can't get past the Google screen. Please help
I was able to utilize the old tool. I'm all set. Thanks
chapelfreak said:
That makes sense, our posts are an hour apart or so.
Click to expand...
Click to collapse
Lol. No big deal haha.
Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
Scott...can I flash the radio.img from V to the Verizon X. This radio is horrible
ADB Sideload Works too
Alternatively, use the instructions found on this page followed by a re-flash of your preferred kernel and a fastboot boottoroot to regain root.
https://developers.google.com/android/nexus/ota
So i just followed all of these instructions, and when going into about phone, it shows that i am now on an N build and still with the October security patch. What did i miss?
Update :
I believe I fixed the issue. The little window with the commands in it for some reason had scrolled up and I missed the flashing the "bootloader-marlin-*" step.
Update 2 :
I am now on X with the November security update. GREAT GUIDE!
Followed it to a T and soft bricked mine so now trying to find a way to fix or toss it out the windows haha. Just a heads up guys.
Ended up using the skipsoft tool and pushing a factory update same results but lost data/apps no biggie.
This is odd i followed the instructions trying to flash X to my phone coming from NDE63P and somehow ended up on NDE63N (Ignore this i missed a command)
What steps do I need to add if I want to completely restore back to factory settings (format userdata)? Or would it be the same to just factory reset through the newly restored stock recovery?
Hi,
I am currently flashing my Nexus 6P with OS 7.1.1
After executing flash-all.bat as suggested on Android factory images i get the below error:
"sending 'bootloader' (3532 KB)...
OKAY [ 0.103s]
writing 'bootloader'...
OKAY [ 0.202s]
finished. total time: 0.317s
rebooting into bootloader...
OKAY [ 0.081s]
finished. total time: 0.084s
sending 'radio' (48728 KB)...
OKAY [ 1.086s]
writing 'radio'...
OKAY [ 2.175s]
finished. total time: 3.267s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.018s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1473177068 bytes
error: update package missing system.img
Press any key to exit..."
Can anyone help out in this? Not sure what does failed to allocate -1473177068 bytes means? How can I solve this.
Try flashing each IMG file manually.
Don't use the flash-all.bat program. Manually type in your fastboot commands.
Extract that big ZIP you have in the same folder with your flash-all.bat. You'll see a bunch of img files called vendor.img, system.img, etc.
Once extracted, run the following commands in order. Replace "partition" with the img file name. Example: fastboot format system
fastboot format partition (if it gives an error, try fastboot erase partition).
fastboot flash partition imgfile
fastboot format cache
fastboot reboot-bootloader
Examples of what things should look like:
fastboot format system
fastboot flash system system.img
fastboot format cache
fastboot reboot-bootloader
<once rebooted, shouldn't take more than 2 seconds>
fastboot format vendor
fastboot flash vendor vendor.img
fastboot format cache
fastboot reboot-bootloader
<again, reboot, ~2 seconds>
If at any time it says it can't format memory type or something similar, usually this is for bootloader, radio and boot partitions, use fastboot erase boot (fastboot erase bootloader, fastboot erase radio).
Do this for each of the files, except for userdata - don't even flash that, just format userdata and skip the flash userdata part.
Also, flash your recovery of TWRP, the latest, and make sure that you boot to recovery first, before you boot the phone all together.
Did you verify the checksum of the image?
DON'T DO THAT...
Wiltron said:
fastboot erase bootloader
Click to expand...
Click to collapse
This will be your last fastboot command... Phone bricked.
To the OP, you should solve your flash-all problem as this script is the recommended way to flash factory images. You need some disk space (like 4 or 5GB)
rchtk said:
DON'T DO THAT...
This will be your last fastboot command... Phone bricked.
Click to expand...
Click to collapse
As long as you flash the bootloader again prior to rebooting you're fine.
I do this weekly with new builds of various ROMs.
Wiltron said:
As long as you flash the bootloader again prior to rebooting you're fine.
I do this weekly with new builds of various ROMs.
Click to expand...
Click to collapse
I find it way too risky tbh and don't see any added value in doing this.
rchtk said:
I find it way too risky tbh and don't see any added value in doing this.
Click to expand...
Click to collapse
Yeah, no reason to advise this. Especially in a thread of someone who may or may not be comfortable using fastboot. Risk > Reward 100%
Not like any 'gremlins' get left behind when updating a bootloader.
OP, just read and follow the beginner sticky thread and you'll do just fine. This one.
RoyJ said:
Yeah, no reason to advise this. Especially in a thread of someone who may or may not be comfortable using fastboot. Risk > Reward 100%
Not like any 'gremlins' get left behind when updating a bootloader.
OP, just read and follow the beginner sticky thread and you'll do just fine. This one.
Click to expand...
Click to collapse
Thank you RoyJ.....it worked
I did the "fastboot flash system system.img" and it says "FAILED <remote: data too large>. Never have any problem with the monthly updates before.
wormbaby11 said:
I did the "fastboot flash system system.img" and it says "FAILED <remote: data too large>. Never have any problem with the monthly updates before.
Click to expand...
Click to collapse
Googling wasn't much help in this case, found threads mostly for old HTC phones around 2013. However I did find one user trying to install 7.1 on his 5X which was able to solve his own issue by updating his Android tools in the SDK.
If you don't already have it, download and install the Android SDK. Follow the link I posted above and there's a section about how to install it.
Open the SDK Manager and under the section named "Tools" you should see; "Android SDK Tools" & "Android SDK Platform-tools".
Check to see if there's an update. I just noticed there is an available update on my PC. SDK Tools & SDK Platform-tools updated versions are 25.2.3 & 25.0.1, respectively. Update and reboot your PC and that should solve your issue. Let us know if that works for you.
Edit: Also, this is more than just a monthly security update. It was a bump up from 7.0.0 to 7.1.1. In any version bump like that, it never hurts to make sure the SDK is up to date.
Thanks Roy, that did the trick.
RoyJ said:
Googling wasn't much help in this case, found threads mostly for old HTC phones around 2013. However I did find one user trying to install 7.1 on his 5X which was able to solve his own issue by updating his Android tools in the SDK.
If you don't already have it, download and install the Android SDK. Follow the link I posted above and there's a section about how to install it.
Open the SDK Manager and under the section named "Tools" you should see; "Android SDK Tools" & "Android SDK Platform-tools".
Check to see if there's an update. I just noticed there is an available update on my PC. SDK Tools & SDK Platform-tools updated versions are 25.2.3 & 25.0.1, respectively. Update and reboot your PC and that should solve your issue. Let us know if that works for you.
Edit: Also, this is more than just a monthly security update. It was a bump up from 7.0.0 to 7.1.1. In any version bump like that, it never hurts to make sure the SDK is up to date.
Click to expand...
Click to collapse
Glad to hear you got it working!
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work
hello friends I have the motorola g5 plus xt1680 by telcel. I have the bootloader blocked and I also have many files in memory that I do not want to lose.
I got a security patch which I downloaded and installed correctly, after updating my mistake I let the cell phone completely discharge, reaching the battery at 0%, after this I can not turn on the device stays in the motorola logo.
I have already tried to flash firmwares using adb but I can not mark me error, errors similar to this one:
fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling
gpt.default.xml
FAILED (remote failure)
finished. total time: 0.066s
for more than download firmware images, all of them make me the same error and I can not find the solution on the internet.
I have been several days and can not find a solution, it is very important not to lose my files that I have on my cell phone.
Would any of you help me please?
Have u tried using the Moto Smart Assist to reflash the phone? It should automatically detect the correct firmware for you.
But if you want to flash one of the firmwares you have, leave out the "fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img" commands and the flash should work fine. Apparently the update you took updated the partition tables on your device so you either have to flash without downgrading or flash using the exact firmware that the gpt.bin file is using.
If you need to get your files off first, download TWRP here, and then copy it into the directory where you have fastboot and run
"fastboot flash recovery twrp-3.2.3-1-potter.img" and then scroll down with the vol keys until you get reboot to recovery. (If it doesn't flash correctly you may have to push vol key down to reboot bootloader and try flash again) After inside TWRP, you should be able to use your password to decrypt your data and then use a USB cable to get your things off the phone or take a TWRP backup of your data / internal storage partitions and restore those after a fresh flash.
Drkmatr1984 said:
Have u tried using the Moto Smart Assist to reflash the phone? It should automatically detect the correct firmware for you.
But if you want to flash one of the firmwares you have, leave out the "fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img" commands and the flash should work fine. Apparently the update you took updated the partition tables on your device so you either have to flash without downgrading or flash using the exact firmware that the gpt.bin file is using.
If you need to get your files off first, download TWRP here, and then copy it into the directory where you have fastboot and run
"fastboot flash recovery twrp-3.2.3-1-potter.img" and then scroll down with the vol keys until you get reboot to recovery. (If it doesn't flash correctly you may have to push vol key down to reboot bootloader and try flash again) After inside TWRP, you should be able to use your password to decrypt your data and then use a USB cable to get your things off the phone or take a TWRP backup of your data / internal storage partitions and restore those after a fresh flash.
Click to expand...
Click to collapse
thanks, I had already tried to revive my phone with moto smart assist but the software tells me that my phone is not compatible.
I can install twrp if I have the bootloader blocked or I need to open the bootloader to use twrp? but when I open the bootloader my phone restarts from the factory that will erase all my files
I think I've already got the most recent security patch that is updated, apparently this is:
https://mega.nz/#!jxUEXazJ!TVU8n458ZZwd5TfP12I_uEvslYgGc5vakyUaOeSqMOs
can I install that version on my cellphone without any risk ?
then I can flash it without losing my data by omitting the command fastboot erase userdata or is it more advisable to use the ocpion of twrp to recover my data as you explain my friend?
Thank you very much for the help
Well, if the bootloader is locked, then you can't flash TWRP until you unlock it, which you can't do because you can't get into the system to enable OEM unlocking from developer options. So you're pretty limited to what you can do...
I believe fastboot flashing everything using the exact same firmware as your most recent update, but omitting the gpt.bin, bootloader, and userdata commands would work.
I tried to flash the last ota for the motorola g5 plus and now I can install almost everything but when it comes time to flash the following commands it marks me error:
fastboot erase customize
fastboot erase logo
and now how do I fix that I reboot the device and it keeps giving me boot on the motorola logo
c:\Herramientas ADB\platform-tools>fastboot erase customize
erasing 'customize'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.006s
c:\Herramientas ADB\platform-tools>fastboot erase clogo
erasing 'clogo'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.005s
and now how can I solve that someone help me
july48 said:
I tried to flash the last ota for the motorola g5 plus and now I can install almost everything but when it comes time to flash the following commands it marks me error:
fastboot erase customize
fastboot erase logo
and now how do I fix that I reboot the device and it keeps giving me boot on the motorola logo
c:\Herramientas ADB\platform-tools>fastboot erase customize
erasing 'customize'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.006s
c:\Herramientas ADB\platform-tools>fastboot erase clogo
erasing 'clogo'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.005s
and now how can I solve that someone help me
Click to expand...
Click to collapse
Why don't use ADB pull command to pull the data from device and run the all command of flashing except bootloader and gpt.
riyan65 said:
Why don't use ADB pull command to pull the data from device and run the all command of flashing except bootloader and gpt.
Click to expand...
Click to collapse
I think the problem is he can't get past bootloader so no ADB commands for him to have access to, and his bootloader is locked and since his system won't boot he can't turn on OEM unlocking to unlock it to flash TWRP or something similar to give him ADB commands.
july48 said:
I tried to flash the last ota for the motorola g5 plus and now I can install almost everything but when it comes time to flash the following commands it marks me error:
fastboot erase customize
fastboot erase logo
and now how do I fix that I reboot the device and it keeps giving me boot on the motorola logo
c:\Herramientas ADB\platform-tools>fastboot erase customize
erasing 'customize'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.006s
c:\Herramientas ADB\platform-tools>fastboot erase clogo
erasing 'clogo'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.005s
and now how can I solve that someone help me
Click to expand...
Click to collapse
Your problems are not related to the errors for "customize" and "clogo". These entries are for customazions made by Moto Maker and it's normal that they fail if you don't have any of these.
If your device doesn't boot you may have downgraded your bootloader in the past.
I have already tried to omit the bootloader and gpt commands, and I still have the same problems only in that part of the code, having the bootloader blocked limits me a lot, I do not know if I have to wait for the firmware of my phone company Telcel to flash it by adb and see if only so I retrieve the phone.
I do not know what else to try if there is any other solution
july48 said:
I have already tried to omit the bootloader and gpt commands, and I still have the same problems only in that part of the code, having the bootloader blocked limits me a lot, I do not know if I have to wait for the firmware of my phone company Telcel to flash it by adb and see if only so I retrieve the phone.
I do not know what else to try if there is any other solution
Click to expand...
Click to collapse
If you have the most recent firmware you don't need to omit the bootloader and gpt commands, and the clogo and customize commands almost always fail, you don't even really need them.
If it's still not booting I'm not sure what else to tell you to try. Someone in another one of my posts suggested trying to boot with "fastboot boot boot.img" and then possibly you could switch on OEM unlocking from the developer options, then reboot, unlock bootloader, and flash again or flash TWRP and use recovery to recover from there.
But I'm not guaranteeing that will do anything other than be stuck at boot logo.