Hi, I wonder if anyone can help me get out of this...
[EDIT: The fastboot option 'Normal powerup' eventually worked and phone seems to be back to normal]
So I finally decided I'd had enough of the Lollipop bugs and decided to downgrade to Kitkat following this guide -
http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
Instead of typing the commands in separately I created a .bat file, and when I ran it I got the 'Preflash validation failed' error message for boot.img and the system.img files so I cancelled the bat file. However, the recovery.img file appears to have been written correctly.
When I now try to boot my phone it only gets as far as fastboot, which displays the error message 'UTAG "flashfail" configured as fastboot.'
Searching these forums shows me a lot of contradictory information so I'm hoping someone out there knows exactly what to do. If it's relevant, the bootloader has never been unlocked, the phone never rooted and it was running the latest UK Lollipop (5.02, 5.1?)
Thanks for any help!
In fastboot mode enter:
fastboot oem fb_mode_clear
Now your phone should boot normally.
Hello guys
I flashed my Moto G XT1033 (1st 2013) with GPE 4.4.4 a long time ago. I used to have TWRP installed just in case. Last weekend I decide do download a CM ROM of Lollipop (5.1) and just installed it. Worked like a charm.
Later that day when I got home, Android itself started update process from Motorola! The progressbar was showing and never ended. Suddenly the phone powers off, never coming back.
Doing a quick research I was able to turn it on again to the bootloader, who says:
"Fastboot reason: Failed do initialize partition table"
Since then, I've tried every sort of methods to install ANYTHING on this phone, as for say:
- Boot loader seems locked again, as I see the message "Device is LOCKED. Status Code: 0"
- When trying "fastboot oem get_unlock_data" I get "Could not get unlock data"
- Trying to use a previous key that I have to unlock returned "fastboot oem unlock disabled!"
- Trying to flash partition with many gpt.bin files (from different versions), seems useless always returning "Pre-flash validation failed FAILED Remote Failure" and on the phone is says "version downgraded for primary_gpt"
It looks like I'm on a real trouble in here, since I cannot flash anything to the phone, or even unlock the bootloader.
Any help would be appreciated.
Have you tried following the instructions here?:
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
aha360 said:
Have you tried following the instructions here?:
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
Click to expand...
Click to collapse
Yes, everything works fine until step 15. These are actually the instructions I used to bring the phone "to life" again. All the after steps who tries to flash files to the phone, end up as "remote failure".
Success
aha360 said:
Have you tried following the instructions here?:
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
Click to expand...
Click to collapse
Fortunately I was able to completely restore my MotoG 2013 following the instructions from this post:
https://forum.xda-developers.com/showthread.php?t=2623587&page=6
It's noticeble that:
- I MUST flash mototboot.img FIRST because this unlocks the bootloader
- This ALLOWS do flash gpt.bin
- Then you should flash AGAIN the motoboot.img
- And go ahead flashing the other files --- OR --- flash a Custom recovery (TWRP in my case) and use sideload to load your prefered custom ROM.
Thanks to everyone
I did rooting and installed custom rom 7.1.2. But LTE calling works only when data turned on. Where as it was working stock firmware. HenceI tried ti revert stock firmware. It failed. Even after two hours, id did not update.
Then I saw twrp restore also not working. HenceI tried reinstalled twrp. Now it shows an image with words erasing and warning msg phone unlocked alternatively.
What should I do to get back stock firmware.
Kindly guide me with step by step.
If any more info needed from me, kindly convey.
Problem was solved by omitting two lines
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
in the list of commands.
Okay my friend brought me his Moto G XT1032 says on the back in black writing. Although its a Telus so make me wonder if its actually a XT1034?
I can get into Fastboot and send and receive commands no problem, says its writing okay, version 41.1a.
Recovery does not work no matter which one I flash. When is does load its 3.0.2.0 I think and just hangs. I was able to get into a recovery using the windows out script in install. However it does not install just loads temp in memory I think. I cannot access any of the file system gives me errors. I have tried in twrp and using every fastboot command I could find.
Tried RSDLite and doesn't see or find the phone.
No matter what I try I cannot write to this thing. Bootloader is unlocked. I'm not sure where to go from here. I have tried reinstalling boot loader and it says it takes and returns 411A in fastboot. I even tried downgrading boot loader and it gave me an error.
Thinking maybe a gpe -non gpe thing?
Suggestions of what do try next ?
Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?
Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.
Both failed. I attached the errors I recieved.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/
It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.
Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?
Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!