My moto g (xt1032) was running smoothly on Lollipop 5.1, Magisk rooted, until some apps kept crashing so I decided to reboot the phone (Used to fix the issue) but after booting the screen went blank, nothing showing, the only thing that shows was "Turn off" when i hold the power button, so I decided to boot into TWRP (Bootloader was Unlocked) and flash a 5.1 ROM that I used to successfully flash and work, but as soon as it finished and i press reboot, the screen goes black, no boot logo or anything, it only boots on the "Locked" bootloader.
Now the bootloader is showing version 41.1A . I tried to flash the firmware stock image that I used to flash before(GPE 5.1), i keep getting the same errors:
sending 'partition' (32 KB)...
OKAY [ 5.050s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.389s
I tried other 5.1 stock retail firmwares, same thing. anyone can help?
Related
This started with a brand new Boost Mobile Moto G (XT1031).
It was taken right from the box and unlocked using oem unlock.
After the unlock it booted to the stock image then was powered off and booted to fastboot.
Once in fastboot TWRP 2.7.1.0 recovery was flashed.
When trying to boot into recovery it would only loop.
Tried to boot normally and it would only loop.
Flashed the device back to stock using all the available firmwares from sbf.droid-developers.org for Boost US and it still wont boot.
Tried other recovery images and the only one I was able to get working was Philz Touch 6.55.
Wiped and formated everything and rebooted the phone and it went straight to recovery.
Using Philz recovery tried to install CyanogenMod 11 and bool loop proceeded.
I took another working Moto G and flashed Philz recovery and made a back up onto a usb drive using an otg cable.
On the broken device tried to restore from the backup and it said it was completed but it ran way to fast and didn't seem to restore completely and failed to boot.
I've gone through every method of recovery i could find and nothing seems to be working
This phone is kicking my butt, any help would be greatly appreciated.
manicresin said:
This started with a brand new Boost Mobile Moto G (XT1031).
It was taken right from the box and unlocked using oem unlock.
After the unlock it booted to the stock image then was powered off and booted to fastboot.
Once in fastboot TWRP 2.7.1.0 recovery was flashed.
When trying to boot into recovery it would only loop.
Tried to boot normally and it would only loop.
Flashed the device back to stock using all the available firmwares from sbf.droid-developers.org for Boost US and it still wont boot.
Tried other recovery images and the only one I was able to get working was Philz Touch 6.55.
Wiped and formated everything and rebooted the phone and it went straight to recovery.
Using Philz recovery tried to install CyanogenMod 11 and bool loop proceeded.
I took another working Moto G and flashed Philz recovery and made a back up onto a usb drive using an otg cable.
On the broken device tried to restore from the backup and it said it was completed but it ran way to fast and didn't seem to restore completely and failed to boot.
I've gone through every method of recovery i could find and nothing seems to be working
This phone is kicking my butt, any help would be greatly appreciated.
Click to expand...
Click to collapse
What did you use to flash? fastboot or mfastboot?
280
oversleeper said:
What did you use to flash? fastboot or mfastboot?
Click to expand...
Click to collapse
I used mfastboot.
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Try to use the bootloader refresh tool, for someone worked.:good:
oversleeper said:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Try to use the bootloader refresh tool, for someone worked.:good:
Click to expand...
Click to collapse
I ran the bootloader refresh after modifying the bat file for the correct cpu.
The boot loader version is showing it was updated but the device is still not booting.
[EDIT] I did try to reflash the stock frimware and there where some erros i wasnt getting before
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash aboot emmc_appsboot.mbn
sending 'aboot' (512 KB)...
OKAY [ 0.051s]
writing 'aboot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.335s
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash motoboot motoboot.img
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
Motoboot: Preflash validation for tz
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.407s
On a whim I decided to try the retail firmware and was able to get the phone to boot to stock, but I tried to load TWRP again and it went back to the boot looping state.
I really don't understand what is wrong with this phone because this are for the company I work for and we have flash about a thousand this exact same way and have never ran into this issue.
I am going to try philz recovery to see if it cause the normal boot process to break and if not I try loading the a custom rom from there.
manicresin said:
I ran the bootloader refresh after modifying the bat file for the correct cpu.
The boot loader version is showing it was updated but the device is still not booting.
[EDIT] I did try to reflash the stock frimware and there where some erros i wasnt getting before
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash aboot emmc_appsboot.mbn
sending 'aboot' (512 KB)...
OKAY [ 0.051s]
writing 'aboot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.335s
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash motoboot motoboot.img
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
Motoboot: Preflash validation for tz
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.407s
Click to expand...
Click to collapse
Pretty normal, you got errors because you upgraded the bootloader to the last version, so you can't downgrade it. Now you can: try to flash the 4.4.2 stock boost version (without flashing gpt.bin and motoboot.img) or if doesn't work due to upgraded bootloader, just wait few days until the 4.4.4 firmware for boost will be downloadable. It's already realeased don't worry, look https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/100754/p/30,6720,9050
EDIT: It's a boost version, it's pretty different... You can't flash whatever you want so easily... search for some guide, I can't help about boost version.
The boost 4.4.2 stock firmware failed but the retail version worked, I'm try that with philz recovery to see if I can get CM 11 to work. If that fails ill wait for the 4.4.4 boost firmware.
Thanks for the help
I know some people love TWRP and only use TWRP and some people only use ClockWorkMod Recovery, but since you've been trying with TWRP humour me and flash this, it's the latest ClockWorkMod Recovery 6.0.5.0 compiled from source.
Flash it then try to flash a CM nightly or something like that...clear cache and dalvik cache first then do a factory reset then flash.
ClockWorkMod Recovery 6.0.5.0
CodyF86 said:
I know some people love TWRP and only use TWRP and some people only use ClockWorkMod Recovery, but since you've been trying with TWRP humour me and flash this, it's the latest ClockWorkMod Recovery 6.0.5.0 compiled from source.
Flash it then try to flash a CM nightly or something like that...clear cache and dalvik cache first then do a factory reset then flash.
Click to expand...
Click to collapse
I downloaded your recovery image and flashed it, wiped everything and reset.
Installed cm-11-20140903-NIGHTLY-falcon from usbdisk, it said completed only after ~20 seconds but there where no errors.
Rebooted the device and the cyanogenmod animated boot logo was displayed.
The phone booted fine was is working, now to try and see if I can get my image loaded.
Thanks for the recommendation, I didn't think to try CWM since Philz recovery is based on it, but it failed to load CM 11.
So my Moto 4g has freeze and reboot during the last official lollipop update and now my phone is unable to boot
I try to reflash a stock rom using fastboot mode (and mflashtool) but I got errors
sending 'recovery' (10240 KB)...
OKAY [ 0.382s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.770s
After searching on xda forum it seems that the bootloader is locked so I'v try to use motorola's website to get the unlocked code (https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a) but I'v always get the error "Your device does not qualify for bootloader unlocking"
I've try to remove place and using the Unlock Data Scrub Tool but always the same issue.
As my phone is unable to boot is there anyway to unbrick it ? Maybe and official tool able to flash with locked bootloader or something ?
I have a bricked moto g turbo which is locked so i cant flash firmware files i tried getting bootloader unlock code but a error shows up to tick allow bootloader unlock in developer options but i can't turn on my phone so I cant enable that option. please help
You don't need to be unlocked to flash factory firmware. Just go to http://forum.xda-developers.com/showthread.php?t=3169639 and get the correct firmware and follow the instructions in http://forum.xda-developers.com/showthread.php?t=3187750 and flash your device.
Bootloader unlock is only needed for downgrading, root, and flashing custom ROMs and recovery. It is not needed to flash a full factory image that is the same or newer.
And for the record, if OEM Unlocking is not enabled, the bootloader cannot be unlocked.
fastboot flash partition gpt.bin
sending 'partition' (32 KB)... OKAY
writing 'partition'... (bootloader) Preflash validation failed
FAIL
FAILED (remote failure)
Execution time is 1(s)
getting error
Hi i have the same error. But my problem is with the módem. I cant take signal. I try flash the original rom and don't work
Do you have the log file?
Hi. I got a Moto Maxx with Android Marshmallow (Telcel carrier).
After trying several roms, I decided to go back to stock, since I couldn't find a Marshmallow rom, I decided to update from 4.4. I installed "Mexico Retail Stock Kitkat /// RETLA_XT1225_4.4.4_KXG21.50-9_cid12_subsidy-DEFAULT_CFC.xml.zip" from this thread. Everything went fine, although I lost the custom recovery during the process.
Then, from the software updater option on the phone, I updated to Lollipop. Unfortunately, it didn't updated. Instead, I got a bricked phone. It didn't turned on.
In order to recover it. I followed this guide. The phone turned on again, and now I am stuck on an "empty" bootloader. The upper half of the screen only shows "Start", similar to the picture from the guide.
But I can't flash any stock rom. It seems by doing the steps of that guide, I re-locked my phone. I can't unlock it because, while I know my unlock bootloader code, mfastboot tells me I must enable "Enable OEM Unlock" in the developer settings (which I can't reach).
Trying to flash any stock rom gives me the following errors:
Code:
[B]>mfastboot flash partition gpt.bin[/B]
[I]target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.104s[/I]
>[B]mfastboot flash bootloader bootloader.img[/B]
[I]target max-sparse-size: 256MB
sending 'bootloader' (2159 KB)...
OKAY [ 0.112s]
writing 'bootloader'...
[B](bootloader) Motoboot: Unknown partition name[/B]
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.202s[/I]
>[B]mfastboot flash radio radio.img[/B]
[I]target max-sparse-size: 256MB
sending 'radio' (85457 KB)...
OKAY [ 2.753s]
writing 'radio'...
[B](bootloader) Motoboot: Unknown partition name[/B]
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.802s[/I]
>[B]mfastboot.exe flash system system.img_sparsechunk.0[/B]
[I]target max-sparse-size: 256MB
sending 'system' (253363 KB)...
OKAY [ 8.205s]
writing 'system'...
[B](bootloader) Permission denied[/B]
FAILED (remote failure)
finished. total time: 8.226s[/I]
I can't access to recovery. Please, help me :crying::crying::crying:
Why do people relock their bootloader?
With an unlocked bootloader you can flash other region images, if necessary, like Brazil. With locked bootloader your need Mexico. Your may even need your carrier firmware.
ChazzMatt said:
Why do people relock their bootloader?
Click to expand...
Click to collapse
It wasn't my intention. The phone bricked, and in order to return to bootloader I followed that guide. It worked but it seems that during the process it locked the phone.
But you went from Marshmallow 6.0.1 back to Lollipop 5.0.2. You can't do that unless you omit gpt.bin in your flash commands. Otherwise you will get bootloop or brick your phone.
I assume at one time you had stock Marshmallow on the phone before trying custom ROMs? Or at the least, probably had flashed Marshmallow radio and bootloader?
With unlocked bootloader you can downgrade back to Lollipop or Kitkat, but you need to omit gpt.bin.
I would also omit recovery.img, to keep TWRP.
---------- Post added at 03:23 PM ---------- Previous post was at 03:14 PM ----------
See this thread, but you'll need your region firmware.
https://forum.xda-developers.com/showthread.php?t=3662683
ChazzMatt said:
But you went from Marshmallow 6.0.1 back to Lollipop 5.0.2. You can't do that unless you omit gpt.bin in your flash commands. Otherwise you will get bootloop or brick your phone.
I assume at one time you had stock Marshmallow on the phone before trying custom ROMs? Or at the least, probably had flashed Marshmallow radio and bootloader?
With unlocked bootloader you can downgrade back to Lollipop or Kitkat, but you need to omit gpt.bin.
I would also omit recovery.img, to keep TWRP.
Click to expand...
Click to collapse
Yes, as I said. The phone had Stock Marshmallow. I unlocked my bootloader, I tried custom roms, tried TWRP, I even could go back to stock KitKat (by omitting gpt.bin)
The problem came when I accepted to update to OTA Lollipop. The phone bricked; the screen didn't turned on. And while I found a guide that could unbrick the phone, I ended without recovery and with a relocked phone.
jairjy said:
Yes, as I said. The phone had Stock Marshmallow. I unlocked my bootloader, I tried custom roms, tried TWRP, I even could go back to stock KitKat (by omitting gpt.bin)
The problem came when I accepted to update to OTA Lollipop. The phone bricked; the screen didn't turned on. And while I found a guide that could unbrick the phone, I ended without recovery and with a relocked phone.
Click to expand...
Click to collapse
Because while you had downgraded to Kitkat, but you still had Marshmallow bootloader. You can't take OTA, because it will install bootloader and you cannot downgrade bootloader.
Have we discussed this before, because someone else did EXACTLY the same thing. Downgraded to Kitkat, then tried to take Lollipop OTA --which tries to install Lollipop bootloader!
Help. I got an error today while trying to power on. It was something along the lines of validation failed. Cannot boot.
Then i tried installing the stock rom with the help of fastboot. It was going well. It even had success. But then I ran the command fastboot reboot and the phone doesn't turn on. Stays on black screen. Tried charging. No luck. I don't get any visual confirmation. Can I do anything to fix this phone?
Good. Via ADB the command adb devices or fastboot devices returns something? And the computer even recognizes him? It could be the same case that happened to me.
A year ago his screen turned bran and I sent in an assistance (it was updated in android stock 6.0, until it happened)... Only with the ROM it had, the system did not recognize the new screen (which was changed). Result: They downgraded the android (returned to 5.0) and now I'm breaking to solve an error, i can not even flash any twrp .... The message is
sending 'partition' (32 KB)...
OKAY [ 0.135s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.732s
Same issue here. I've been attemting to run stock firmware on mine. But I've been getting the same error. Idk if it's fixable and my recovery boot is corrupted.