Hi,
I was unlocked and rooted and I tried using the NRT to flash the M system image. It worked and I got the phone to boot once. It went through the Android is upgrading process and I used it for a few seconds and then it froze. I rebooted it by holding the power button. It now will not leave the bootloader. When I try to start it just flashes back into the bootloader. In the BL log it says "failed to validate boot image: ref=-1" So I tried re-flashing both manually and in the NRT. This is the error I get when flashing
(bootloader) failed to write primary GPT
(bootlaoder) failed to flash partition
FAILED (remote failure)
Any help would be appreciated.
Thanks
Try fastboot erase before fastboot flash
-----_--------_--------_----------_---_--------_------------
....read......read more........think.........think more.......read...........read more........
Stop using a toolkit and do it manually https://developers.google.com/android/nexus/images?hl=en
I said that I did it both manually and with the toolkit. Sorry you feel that since I didn't want to type all that in you are better than me. I figured it out though. I couldn't get into any recovery so I used the toolkit to boot into the temporary twrp. Formatted all the partitions and got it to flash successfully.
From what I can tell it tried encrypting and it ruined the partitions.
My nexus 6 received the update by ota and I have experienced the same thing.... Tech support was no help telling me to go to a sprint store. I'm not sure what caused the issues here... My phone did the normal Android is upgrading thing and and I left I to do its thing it booted up and I used to it. Make a phone call. After the call my phone froze when I tried to open all apps. I restarted the phone in the same way the first post did. How ever my phone booted up to the new Android boot screen , however the phone restarted again and this time into the bootloader. Can anyone help me with this?
Related
I have a stock Verizon Moto X (XT1060) that was running 4.4.4. I was on a flight Friday using the phone in airplane mode to run Spotify and Podkicker - noticed the phone was running a little hot so I shut the apps down for a while. Anyway, upon landing I take the phone off airplane mode and the usual minor flood of emails/texts/updates comes in. About 30 seconds after this the phone begins alternately flashing "Process android.process.acore has stopped" and "Process android.process.media has stopped." These cycled for about 5 displays of each, then would disappear for about 45 seconds, then start again. Tried resetting the phone, letting the battery die, no success.
Saturday I tried to navigate into settings to do a factory reset, but the screen froze whenever I tapped on the "backup and reset" menu. Could access all the other menus from settings (until the error cascade started again....). I was able to boot the phone into recovery mode and wiped the cache - nothing. Went back into recovery mode to do a factory reset and now I appear to be stuck in a boot loop - the Moto logo pops up, buzzes, and then does nothing for about a minute or two before trying again. I can get it into recovery mode and tried to wipe the cache and factory reset again, but still nothing.
Any thoughts? Tried looking at other threads but didn't seem to find anything like this. Thanks!
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
hbenz2008 said:
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
Click to expand...
Click to collapse
No luck, unfortunately. Still stuck on the Moto screen. I can force the phone to reset by holding down the power button and then get it into fastboot, my computer recognizes the fastboot device, and the code seems to have run fine. Thanks for the idea - any other thoughts?
If you can still get into fastboot mode you can try flashing only the stock 4.4.4 system.img via mfastboot. That will not wipe your data. If that does not work I would do a full return to stock via mfastboot or you can use rsd.
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
cmcgowan said:
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
Click to expand...
Click to collapse
No, don't need to unlock boot loader to flash the system.img just enable USB debugging in developer options. Tap build number 5 times to enable developer options. If you have never flashed anything before via fastboot rsd might be easier for you.
Thanks - I've used fastboot before on an older phone but never enabled USB debugging on this phone and now can't get to enable it since I'm stuck with this boot loop. Downloading the files from Moto now so will give it a shot tonight anyway. Can't really break it more than it's already broken since all I've got now is a shiny light up paperweight.
You will still need to download the stock images for 4.4.4 for Verizon and extract them. You can flash via rsd or simply flash just the system by running the command "mfastboot flash system system.img"
You will have to have the image file in the same folder as your mfastboot.exe I usually keep all mine in platform tools.
Sigh. Got everything downloaded but when I tried to flash either the boot image, recovery image, or system image, I ran into errors
Here's what displayed (sub boot/recovery for system - same basic error):
c:\{Path}\mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [16.793s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.756s
I was following option 5 from mark @ cdma forum's guide to return motox to stock (can't link b/c I don't have enough posts...) . No issues until I got to the flash boot boot.img step.
I'm assuming this is due to not having USB debugging enabled prior to my phone eating itself, though I'm not sure. Willing to try other things since I love my Moto X but my cheap replacement phone arrives tomorrow (hopefully) so at least its not the end of the world...
You are sure you got the 4.4.4 images? You did not try to downgrade right?
Yup. Definitely got the 4.4.4 images (went back to the Moto site and it will let me download the 4.4.4 immediately but made me request authorization for 4.4.2) and I know I was running the most recent version since I checked for an upgrade on my phone last week in the hope that Moto had released 5.0.
You are following this guide? http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
If USB debugging is not on you can manually boot you device to boot loader mode. Then fastboot or rsd should work fine.
---------- Post added at 11:36 PM ---------- Previous post was at 11:32 PM ----------
Moto X Restore and unbrick for any major US carrier: https://youtu.be/jhhktIkwi7Q
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
cmcgowan said:
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
Click to expand...
Click to collapse
You are opening the cmd screen from the same folder as your images and fastboot and mfastboot.exe correct? From your error it looks like your cmd screen is directed to your "C" drive.
Sorry, just didn't type out the whole thing - the cmd path is to the platform-tools folder where all of the files are also located...
Damn was hoping it was something simply like that. Have you tried rsd?
I haven't - didn't enable USB debugging and for whatever reason the package I downloaded from Moto doesn't include the XML file of instructions. Most of the links from the youtube video and some of the links from the XDA guide earlier are also dead so seems like I'm pretty much out of options. Thanks for all of your help - guess I'm going with the $80 replacement till I'm up for an upgrade!
This time I tried the flash-all.bat file. I did not notice big problems during the flashing process, (it mentioned missing .sig files). When flash-all.bat finished, I scrolled up to Recovery using the volume keys, hit the power key, and the screen changed to the first part of the boot sequence, the black screen with Google at the top and a small unlocked lock sign at the bottom... And there it has set for the past hour
It does not seem to connect to the usb port anymore, so I don't know where I go from here.
I have flashed factory images on my Nexus 6 several times, including each of the recent developer previews. I always used the fastboot commands. The bootloader is unlocked; the phone is not rooted, it was running preview 3.
Uh, what next?
OK, I got back to the bootloader.
Now when I try to flash the files one at a time, I get:
Motobootreflash validation for aboot
preflash validation failed
failed remote failure
I tried to upgrade from Android M preview 3 to 6.0 Marshmallow using the flash-all.bat.
There were error messages and the phone would not boot into recovery.
I went back to fastboot to flash files one at a time.
When I try to flash bootloader it fails with the "Preflash validation error" message.
Is this telling me that I can't flash the bootloader because it was already flashed during the (unsuccessful) flash-all.bat?
Can I flash the other files to get the phone back to working order?
I was on preview 3 and used flash-all.bat to go to the official 6.0 image. No issues on my end, the missing boot sig message is normal, phone took about 5 min but booted up clean. You might want to try downloading the factory image again, maybe it was partially corrupted? Should be recoverable since you can still get into the bootloader and access fastboot.
Update: I kept trying to reflash changing one thing at a time, until I finally tried my old, tired laptop with an old fastboot.exe on it.
With the old software on the old computer, Marshmallow flashed normally using the command line.
Hi people. I was trying to install a new ROM on my TF701, 'cause I was very sad to keep that stock 4.4.2.
Of course, I did a mess.
1st thing, I tried to unlock the boot with the Asus apk, but I was struck (it asked for google permission, I tried to give my correct password, but it rejected it. I saw - only too late - that maybe, if I had fully removed my google account before to use that tool, all should have been go right...).
Then, I used an utility to gain root (KingRoot4.1-release-20150703-for-xda.apk). It did the trick, but now I understand that maybe gaining the root rights it's different from "unlocking the boot". Sigh.
Then I used an utility (Flashify if my memory serves me right), to put a clockworkmod in my TF701.
I got the clockworkmod from a droidbasament link (db-blog/?p=3568).
I selected "boot" when the utility asked me what kind of img I was trying to flash... maybe I chose the wrong type again... However, it flashed the img. But now when I boot the device, I get a Signature Mismatch. Booting failed. Unrecoverable bootloader error (0x00000008), with the ASUS logo.
If I reboot with Power + Vol Down, I can get the fastboot USB download protocol, with the 3 icons in the middle of the screen.
I installed the Android SDK. I tried to take the clockworkmod recovery.img and move it in the tablet with:
fastboot boot recovery.img
but I get:
downloading 'boot.img'...
OKAY [ 0.932s]
booting...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.982s
So... the Bootloader is still locked, I imagine. Can I try to return to a full stock ROM, maybe using the microSD?
I tried to download TF701T_11.4.1.30_WW_Boot_TWRP_2870_signed.zip , put on the microSD, and launched RCK. It starts to install, but after a while I get the error broken droid picture.
I tried to rename the file to T4_SDUPDATE.zip, but I get the same results.
Am I screwed? Any help is welcome. Also, if I can fix the problem, I'll offer you a big beer! (paypal?)
So this morning i tried this. Kingroot didn't complete the root, some error happened, i didn't mind since i was just testing to see if i could root my phone for the first time [i've never done it before and it seemed simple enough].
I quit the app, a bunch of errors showed up, one after the other [i didn't register what exactly the windows said, i'm pretty sure it was a google application that stopped working]. The phone turned itself off.
i booted it up again, and it showed me the AP Fastboot Flash Mode screen. i know this from previously doing a factory reset, so i tried doing it again. After it wiped all of my data and custom, i tried rebooting it.
it showed me the motorola icon, but a few seconds later, i was back at the fastboot screen. i'm pretty desperate right now since this is my only phone. i tried selecting the "normal powerup" command, it didn't work. this is my screen right now:
"hab check failed for boot
failed to validate boot image
fastboot reason: fall-through from normal boot mode
USB conected
hab check failed for boot
failed to validate boot image
boot up failed"
none of the other commands, aside from Recovery, work. it takes me to the no command screen and all of the known options once i use the power+volume up command: reboot system now, reboot to bootloader, apply update from ABD, etc.
sorry if this thread reads weird, i'm sort of freaking out right now and english isn't my main language. thanks in advance to anyone who might help!
Check here
If you have questions PM me I will try to help. I got the same problem on Monday and solved it yesterday.
I have tried multiple times to install mr3 global image, I have all drivers installed and device showing however always get an error . However I managed to get it going but Fastboot stoped on system.img when using flash_all and I think that's what has caused my phone app to crash the whole phone when I try to ring someone... If any one can help it would much appreciated... Thank you
Sorted this by flashing to MR2 factory IMG and I run in to critical partition error but the .IMG files all seemed to carry on installing on the phone It ended up my phone not booting and saying device is corrupt and cannot be trusted thought phone was bricked, how ever I fixed it ...
even though it was already OEM unlocked I just fastboot OEM unlocked again and flashed MR2 and it booted .. updated OTA to MR3