My Moto G6 play failed to boot. Have now idea how to fix or if can be? It just happened while the phone was on sitting idle. Tried to connect to Software Upgrade Assistant but it didn't pick my phone up. Went through the menu and tried factory reset even and it still brought this error up.
Any thoughts? Error is summarized below
Thanks
failed to validate boot image
ERROR: failed to pass validation, backup to fast boot
Now got it connected up to Software Repair Assistant and it's been running for 15minutes stuck on below. Any ideas?
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant
AP Factbook Flash Mode (Secure)
USB connected
cmd: getvarroduct
cmd: getvar:secure
cmd: getvar:version-bootloader
cmd: getvar:cid
cmd: getvar:ro.build.fingerprint
cmd: getvar:ro.build.version.full
cmd: getvar:ro.build.version.full
cmd: getvar:serialno
cmd: getvar:imei
cmd: getvar:sku
cmd: getvar:ro.carrier
Tried to re-install the Software with the help of Smart Assistant Tool but it kept failing halfway through with no meaningful error message. Any thoughts? Is it now a brick?
Gazza76 said:
Tried to re-install the Software with the help of Smart Assistant Tool but it kept failing halfway through with no meaningful error message. Any thoughts? Is it now a brick?
Click to expand...
Click to collapse
Hey dude! It is a little old, but do you get a solution for your problem? I have the same issue, and now that I´m willing to lost everything on my phone it does not allow to do a factory reset. Damn phone...
Paulista666 said:
Hey dude! It is a little old, but do you get a solution for your problem? I have the same issue, and now that I´m willing to lost everything on my phone it does not allow to do a factory reset. Damn phone...
Click to expand...
Click to collapse
Gazza76, I don´t know exactly why, but I just charge my phone all the way, and try again expecting that was some battery protection. Maybe if the battery is below some threshold it stop the boot to avoid issues. But no, keeping having the same problem.
But, I pluged in the computer with LSMA installed and it let me reinstall all firmware. It recommends the right firmware, you download it through the app, and install it really fast in my opinion. Could be a solution for you if you are with the problem yet...
Related
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
unlock it using flash tool, just press unlock wait and enter the code.. done
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
try using different usb cable/ different port.
Had same problem....some driver was missing
Sent from my C5503 using xda app-developers app
I've finally gotten flash tool to work, however now it gives me an error saying that my device cannot be officially unlocked,
EDIT: i'm pretty sure i've unlocked the bootloader now, as flashtool had me enter an unlock code and my device has had all of its data reset.
however my issues continue as now flashtool utterly refuses to pick up my device. I have re-installed all drivers, flashtool, etc but still nothing.
sometimes it may have conflicts when flashtool and other tools use their own instance of adb or fastboot. I think the best thing to do now is reinstalling regular drivers normally. don't forget to enable usb debugging...
this may be useful :
Code:
[I]ADB_PATH[/I]\adb kill-server
exit
create a text file, paste this code then save it as ADB - Kill.cmd
I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!
arman92 said:
I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!
Click to expand...
Click to collapse
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.
CYoung234 said:
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.
Click to expand...
Click to collapse
Yes I did try the RootZenFone tool, but it didn't work either.
Unfortunately I forgot to "Forget the wireless networks" (I just disabled the WiFi), and the RootZenFone failed rooting my device...
Is there any way to get it work again?
HELP ME!!
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!
arman92 said:
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!
Click to expand...
Click to collapse
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.
Done! I'm Root
CYoung234 said:
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.
Click to expand...
Click to collapse
I've followed the instructions in this page : http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
I successfully made it flash the Asus official ROM, but every time the freaking "Unfortunately Asus Demo has stopped" showed up.
I tried 4 different ROMs, still I got the error. I tried the RootZenFone-1.4.6r.apk everytime, no chance. The rooting process was interrupted by the "Unfortunately Asus Demo has stopped"
Then I figured out that when the tablet is connected to a power source (e.g. USB charge or PC), the error come up more frequent, so I disconnected the USB cable and tried the RootZenFone again, after a fresh ROM recovery, this time it successfully finished the rooting process. Huurrraaaay!!
So for every one else that has the same issue: just disconnect the USB cable and you are good to go!
Thanks for everyone that helped.
Hi Community,
I was rooted and got some nasty popup virus, then I factory reseted through settings. Everything was fine, then I entered in my software "superuser" and he said he would reinstall something, then booom bootloop!
I tried factory resetting through fastboot didnt work;
I tried flashing stockrom, latest rom, downgrade rom and the error is the same:
Verifying update package...
E: footer is wrong
Update package verification took 0.2 s (result 1).
E: Signature verification failed
E: error: 21
Installation aborted
ADB doesnt recognize my device!!! guess because after rebooting I never re authorized usb debugging mode or oem..
What Can I do now? any help appreciated
Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
Everything is described there.
If your Device is on Android One, don't take the Rom from the thread but from this link: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again
AdB dont recognize my device fastboot sees im plugged in but adb wont see the device
irongas said:
AdB dont recognize my device fastboot sees im plugged in but adb wont see the device
Click to expand...
Click to collapse
I believe you don't need adb to recognize your device if your flashing OEM firmware from the bootloader (and you have the bootloader unlocked). As long as you can boot into the bootloader you should be able to flash the stock firmware. I got my Moto x4 into a bootloop and was able to revert it back to the stock firmware even though my phone didn't have usb debugging enabled and my PC wasn't authorized for my phone. Follow these commands
screwyou00 said:
I believe you don't need adb to recognize your device if your flashing OEM firmware from the bootloader (and you have the bootloader unlocked). As long as you can boot into the bootloader you should be able to flash the stock firmware. I got my Moto x4 into a bootloop and was able to revert it back to the stock firmware even though my phone didn't have usb debugging enabled and my PC wasn't authorized for my phone. Follow these commands
Click to expand...
Click to collapse
thanks for the response, but i cant load any commands, because I cant connect my pc to the phone. Ive got an option called "apply update from sd card" and "Apply update from ADB" when i try the first it gives error 21, when i try the second it comes to a blank screen asking me to "Now send the package you want to apply to the device with "adb sideload <filename>" and I cant, because there is no connection..
irongas said:
thanks for the response, but i cant load any commands, because I cant connect my pc to the phone. Ive got an option called "apply update from sd card" and "Apply update from ADB" when i try the first it gives error 21, when i try the second it comes to a blank screen asking me to "Now send the package you want to apply to the device with "adb sideload <filename>" and I cant, because there is no connection..
Click to expand...
Click to collapse
Did you install Motorola fastboot drivers?
The menu what you talk about is Recovery. Look if there's an option to boot to bootloader. If not go down to reboot the device and keep VOL-Down pressed so it reboots to bootloader. There you can just use fastboot commands.
sleeptab said:
Did you install Motorola fastboot drivers?
I did, I used to workaround with adb and sending commands, but the command prompt would recognize my device, now, even in bootloader when I plug it in bootloader says: usb plugged in, but the pc wont see my device... im almost crying here lol
Click to expand...
Click to collapse
RESOLVED!
hEY i JUST looked in device manager and there was a driver issue, then I reinstalled the driver from the pc adb phone, and it came back to liiiife!!! I just followed the second sequence and boom its working
Thank you a looot guys!!! sorry being such a noob! =)
Have a nice one!!
Hello, I have a problem with a motorola moto Z3 play of 128gb, as they tell me I was updating and ran out of battery and now starts in red letters that say the following:
Your device didin't start up succesfully
if this a Verizon device, use the Software Repair Asistant on computer to repair your device.
connect your device to your computer, to get the Software Repair Assistant.
if this is not a Verizon device, or Software Repair Assistant did not help for any reason, please contact your customer care center for further asistant.
AP Fastboot Flah Mode (Secure)
SSM: abl csv roll back 0.7
Not bootable A / B slot
Failed to boot Linux, Failling back to fastboot
Fastboot reason: Fail-trough from normal boot mode
when I want to connect it to flash it, the computer does not recognize me fastboot mode, nor adb, I put the commands "fastboot devices" or "ADB devices" and obviously it does not let me do anything, someone to help me out of that state or guide me a little to revive it, please !! ...
Sorry for my bad english.
Hi Guys,
My phone suddenly stuck at this screen since may :
Android Recovery
Xiaomi/jasmine/jasmine_sprout
9/PKQ1.180904.001/V10.0.9.0.PDIMIXM
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data store on this device.
- Try again
- Factory data reset
If i press try again, sometime it will go to fastboot screen.
I can go into recovery mode here but i not sure which step i should do next.
Reboot system nowreboot to bootloader
apply update from ADB
apply update from sd CARD
wipe data/factory reset
Mount/sstem
view recovery logs
run graphics test
run locale test
power off
I'm not a very tech savvy person, i would really appreciate some help as i have data inside my phone which i need. So if possible i would like to retain the data.
I tried like EDL,fastboot,and flashing none seem to work. Of course I may be doing it wrong.
Can anyone guide me step by step I be happy to give an reward via paypal.
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
blazessdd said:
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
Click to expand...
Click to collapse
Thank you so much for replying.
Nope, but I can do EDL to unlock bootloader, I already disassemble the device a few times.
Just that every time I try to flash it , it give me some error. like Bluetooth error or the version error .
Which I watch thousand of video to work but it's doesn't help. Or maybe I just watched the wrong video
Ok tell me exactly what are you doing and where you have downloaded the rom.
If it's corrupted and you try to flash it you will lose the data... Was debug USB activated on developer settings?
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
epilifio said:
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
Click to expand...
Click to collapse
You can try to short the edl points so you can flash the ROM again
blazessdd said:
You can try to short the edl points so you can flash the ROM again
Click to expand...
Click to collapse
I already made this attempt, "adb reboot edl" reports the message "error: '(null)' not found
Xiaomi never again