(bootloader) Preflash validation failed - Moto G Q&A, Help & Troubleshooting

Hi I've Installed Chainfire(dumbest idea ever) -I had GLTools with only default plugin- ,too check whenever It would be possible to run Portal-So memory is almost full ,so I couldn't do neither full CWM backup ,and Advanced Backup didn't worked for me.
So What I did was flash 4.4.2(and I was on 4.4.4 europe rom -XT1032)
I have Fastboot Reason: UTAG *flashfail* configured as fastboot(no not after installing chainfire)
I was flashing with my premade /.sh file (fastboot flash partition gpt.bin etc.) and it seems like what have been flasheed is:
wirting 'partition'...
(bootloader) Preflash validation failed
FAILED(remote failure)
wirting 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
witing 'boot'...
OKAY
'system' -sparechunk.0
FAILED (data transfer failure (No such file or directory)) - lol? ,I've actually modified VM to have 512 mb of ram instead of 1536mb and cores from 2 to 1.
*fastboot resets*
Fastboot Reason: UTAG *flashfail* configured as fastboot
'system'-sparechunk.1
OKAY
and the rest wasn't flashed ,What can I do ,...I've just clicked factory(up button-congrats idiot-I wanted to go into recovery to say that I can go there and do something from there *facepalm* and clicked Up button ,because I was on factory option).
Okay ,so know I have no UTAG error recovery still works ,phone gets stuck on unlocked bootloader disclamer.
Btw before I started to install chainfire I've followed some instructions:
Code:
Backup
[B] * boot into recovery
* adb backup -f boot.img boot
* adb backup -f system.img system[/B]
Restore
[B] * boot into recovery[/B]
* adb shell echo -n boot > /tmp/ro.bu.restore
* adb restore boot.img
[I][B] * adb shell echo -n system > /tmp/ro.bu.restore
* adb restore system.img[/B][/I]
I've followed ,Failed
As boot.img from 4.4.2 have flashed can I actually flash that( * adb backup -f boot.img boot) boot.img and I don't magic will help me. Or can Actually someone who Have XT1032 falcon_umts do like CWM Backup without any personal stuff and I would try to flash it(Preloader/boot is not corrupted- device unlocked etc.-) ,when I used Used factory then everything seems to be working(expect for the android of course... and I don't know whenever VM will work If I don't have everything flashed).
Btw I can't Flash System.img from before I've destroyed it with Chainfire ,because the size is more than 600/700 mb and it just out numbers max number for sending system partition to fastboot.

Not saying this will definitely work, but if you get the gpt.bin and emmc_appsboot.mbn files from the 4.4.4 OTA zip (probably floating around here) and overwrite the originals from 4.4.2 in your factory image (delete the old ones or rename them to something else), then do the following:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Then flash as normal according to the guide that's floating around here, but leave out the gpt.bin and emmc_appsboot.mbn (you already flashed these) and the motoboot.img or it will brick it!

I just installed Paranoid Android ontop of it(adb sideload-I couldn't get into CWM ,and by accidently clicking factory in fastboot I could then go to CWM) and it works-then I launch PA install minimal gapps then factory reset it in cwm delete all data and slowly update pa update by update(installing 4.4RC2 into 4.45 is an bad idea for overall performance and stability) -I just kinda paniced.And I think ,because I was using generic fastboot instead of provided in guide ,preloadder didn't get corrupted(when to look at It only boot have been flashed correctly , and PA have boot.img in package).
So far so good.

This error has been associated with locked bootloader.

I know but my is still unlocked.
Btw that message "Preflash validation failled" supposed to show after booting too fastboot(actually that sounds like a total bull****) or on flasher linux terminal.

Shuttwind215 said:
I know but my is still unlocked.
Btw that message "Preflash validation failled" supposed to show after booting too fastboot(actually that sounds like a total bull****) or on flasher linux terminal.
Click to expand...
Click to collapse
My moto's bootloader is unlocked too, but it still gives the error...
Found an article:
https://giorgiosadventures.wordpres...rom-gpe-4-4-4-to-stock-and-recover-softbrick/
Try this... Lets see if it helps...
BTW, I got this error after converting xt1033 to gpe, then OTA'ing it to 5.0.1, then downgrading to 4.4.2.

@layman806 My moto g allready work look at post #3 this is what I did it[it looks extremly confusing]. It mightn't work for you through
,but if yours moto g have unlocked bootloader then you can do a lot ,and your situation isn't that bad.

lost101 said:
This error has been associated with locked bootloader.
Click to expand...
Click to collapse
i have unlocked my bootloader but i still get that error. every other command executes perfectly but this gpt.bin doesnt
any solution?

khiladi_786 said:
i have unlocked my bootloader but i still get that error. every other command executes perfectly but this gpt.bin doesnt
any solution?
Click to expand...
Click to collapse
I have the exact same problem on my xt1031 motog. I cant get any roms to boot and I cant figure out what version of gpt.bin i need to use. I get the same error.
Driving me crazy.

not solved
I am flashing the stock rom into my moto g3 but it keep tellin preflash validation failed........I did everything ......still not solved.......help me out please..........
on bootloader it shows....
device is unlocked. status code :3
software status: official
it is bit odd.....

heisenberg1546 said:
I am flashing the stock rom into my moto g3 but it keep tellin preflash validation failed........I did everything ......still not solved.......help me out please..........
on bootloader it shows....
device is unlocked. status code :3
software status: official
it is bit odd.....
Click to expand...
Click to collapse
This subforum is not for your phone. https://forum.xda-developers.com/2015-moto-g is the place for you.
If you are getting a 'pre-flash validation' error - even with the latest available firmware image - then you have to either wait for an even newer firmware image or unlock Bootloader and flash a ROM zip.

help me plseeeeeeeeeeeeee i m getting preflash validation failed error on gpt.bin and sparsechunk plseee help me anyone i m using moto g3 xt1550 and trying to flash marshmallow.

Related

Recover a 4.4.4 downgrade brick! (Temporal solution)

So, i have noted a increased number of threads about people who have soft-bricked their phones downgrading from 4.4.4 GPE after recieving the OTA, since it includes a new partition table and there's no firmware image yet.
Worry not, i have found a solution for your problem. This method only let's you use custom ROMs (sadly), but it's meant to be a temporal solution while we wait for a 4.4.4 GPE image anyways.
So, without further ado, here's my fix:
You will need:
-The good ol' Android SDK
http://developer.android.com/sdk/index.html#download
-Motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
-A custom recovery. I recommend TWRP, since is the only one i have tested.
Official TWRP Images for Moto G: http://techerrata.com/file/twrp2/xt1032/openrecovery-twrp-2.7.1.1-xt1032.img
-The gpt.bin from 4.4.4 (this is the partition table)
I extracted it from the OTA file and uploaded to my Dropbox: https://dl.dropboxusercontent.com/u/82658555/gpt.bin
-A custom ROM of your choice (obligatory) + GApps (optional)
What to do:
Once you have the Android SDK, decompress the folder sdk/platform-tools in a place of your choice.
Inside this folder, put gpt.bin, the custom recovery image and the ROM and GApps zip's.
Start your phone on fastboot. Connect it.
Inside your decompressed platform-tools folder, hold shift and right click inside the folder. Select "Open command window here".
Make sure your phone is properly connected by typing "fastboot devices" (without the quotation marks). The command prompt should show your phone serial number.
Now we start the real deal. Fist of all, flash gpt.bin using this command:
fastboot flash partition gpt.bin
Make sure it ends on "OKAY"
Now, flash the recovery
fastboot flash recovery nameoftherecoveryfile.img
Once this is done, enter recovery using the fastboot menu on your phone (use Vol- to highlight "Recovery", and then press Vol+)
Now your phone should boot on recovery mode. If you recieve an error like "Can't mount /system/", don't worry, this is normal (there's no system partiton yet, after all). Now you can use ADB command with your PC. Once again, to be sure everything is connected properly,tyipe on the console:
adb devices
Once that is done, it's time to give your phone the custom ROM, so you can flash it. Type (or copy/paste)
adb push NameoftheROMfile.zip /sdcard/ NameoftheROMfile.zip
If you have GApps, do the same for those
adb push GApps.zip /sdcard/ GApps.zip
Now you can finally disconnect your phone from the PC! You are almost done, select "Install" in your recovery, and flash your ROM zip, then the GApps if you have them.
Once it's done, you can reboot to system.
And you will have a working Moto G again!!
Enjoy it, and don't brick it again
the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file
maurocds said:
the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file
Click to expand...
Click to collapse
From my experience, you don't have to enter sideload mode in recovery to push a file, sideload mode is for pushing OTAs. And remember, the ADB push command requires you to put the exact name of the file to transfer twice, that could have failed for you.
You can't use fastboot devices on recovery because you can only use ADB commands in recovery, you were supposed to use "adb devices".
Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.
masa86 said:
Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.
Click to expand...
Click to collapse
Not many people do NAND backups these days.
Sad, because they're really useful, and there wouldn't be as many "HALP BRICKED PHONE" threads.
It Doesn't work only say failed xD
Fresroqir said:
It Doesn't work only say failed xD
Click to expand...
Click to collapse
Care to explain what failed?
tatazeuz said:
Care to explain what failed?
Click to expand...
Click to collapse
The install for the custom rom and gapps
Fresroqir said:
The install for the custom rom and gapps
Click to expand...
Click to collapse
What error did you receive? Did you flashed gpt.bin correctly?
tatazeuz said:
What error did you receive? Did you flashed gpt.bin correctly?
Click to expand...
Click to collapse
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)
Fresroqir said:
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)
Click to expand...
Click to collapse
got.bin is the partition table of the Moto G. Its the file that indicates to the phone the size, name and number of partitions it should have.
So, I know TWRP said in red letters Failed, but I'm interested what is the specific error, what did it said on the command prompt of TWRP.
Error flashing zip sdcard pa falconzip
and then there comes this updating partitution details and do i need to put the rom twice in the cmd?
and do i need a cutom rom with 4.4.4????????
yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading
Fresroqir said:
and do i need a cutom rom with 4.4.4????????
Click to expand...
Click to collapse
maurocds said:
yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading
Click to expand...
Click to collapse
I used the latest version of PA + Stock GApps
Thanks!
Edit: Nope... Still same problem. Looks like the gpt file flashed but everything else is the same.
It still doesn't work for me i got th whole time failed and i don't know what i need to do ;(
It says: Z:\New folder\Android>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.025s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.372s]
finished. total time: 0.399s
is that good?
EDIT:it looks that sideload works and not that push command
EDIT: nvm i am stuck at bootanimation
EDIT: this wont work it says failed all the time at twrp
I'm kind of confused. Why couldn't people downgrade and go back to stock by reflashing all of the files from an older stock image, including the motoboot and gpt? I would think this would work...although with people saying that they are unable to downgrade I'm not willing to try upgrading to 4.4.4 myself.
What errors are people seeing if they try to flash gpt and motoboot from, say, 4.4.2 stock or 4.4.2 GPE?
-- Nathan
not work for me..
every recovery stay on black screen and return vibration on touch screen
:/
help > http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
i think this fix doesn't work because i can only sideload my roms and gapps xD

[SOLVED] [CM11] [XT1032] Stuck at boot splash logo

Hello,
I have a Motorola Moto G XT1032 on which I have successfully unlocked the bootloader. I can access to recovery (CWM 6.0.4.7) and transfer files using adb in this mod. However, CWM does not get past the splash logo (I do get the occasionnal lag when CWM rebuilds the cache, but this is another minor issue). I have tried the following ROMs, installed each after formatting /system, /data and /cache:
cm-11-20140308-SNAPSHOT-M4-falcon.zip
cm-11-20140405-SNAPSHOT-M5-falcon.zip
cm-11-20140504-SNAPSHOT-M6-falcon.zip
cm-11-20140613-NIGHTLY-falcon.zip
cm-11-20140730-NIGHTLY-falcon.zip
cm-11-20140823-NIGHTLY-falcon.zip
None worked. I did checked the md5 checksums. I have also tried installing GApps using gapps-kk-20140606-signed.zip .
I do not know how to get more information on what happens when CM11 stucks during the boot. 'Show log' from recovery only prints some configuration information as well as:
Code:
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
From what I undersood, extendedcommand is an optional executable used to launch stuff at boot.
I found some ideas from another thread and tried locking/unlocking oem:
Code:
$ fastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.057s]
finished. total time: 0.057s
$ fastboot oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.037s]
finished. total time: 0.037s
$ fastboot oem unlock
...
(bootloader) Device already unlocked!
FAILED (remote failure)
finished. total time: 0.008s
Additionnally I also reinstalled recovery:
Code:
$ fastboot erase recovery
$ fastboot flash recovery CWM-swipe-6.0.4.7-falcon.img
I did have a message "Mismatched partition size (recovery)" but CWM starts fine. I then reinstalled CM11 again, but it did not help either.
Would you have further instruction to try and get CM11 to work?
Just a short post to avoid the thread from being buried down into oblivion.
Same happened to me days ago. I was unable to install any custom ROM. I was in Enhdroix and I flashed the original version of my ROM via fast boot but every time I tried to install a custom was stocked and bootlogo. Some how I figured that the boot loader of the original version was corrupted so I flashed a different stock ROM, after that was able to install custom.
The recovery message is normal you can check videos or post.
Hope this helps my friend.
To prevent any further problems, I also recommend that you flash twrp or philz recovery because the stock cwm recovery is outdated and it will give you problems while flashing ROMs in the future...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
ThisIsMadness said:
Just a short post to avoid the thread from being buried down into oblivion.
Click to expand...
Click to collapse
Check previous answers
Thanks for your help, I finally got it to work!
If someone gets stuck with the same problem, here is what I did:
first, fastboot flash recovery to TWRP
reinstalling (wipe and so) CM11 from TWRP did not work any better
I reinstalled a stock ROM following http://forum.xda-developers.com/showthread.php?t=2542219
I did not boot at all (no logo), but I could still get to fastboot
I reinstalled TWRP, and then CM11
it worked!
From my own diagnosis, I must have accidentely corrupted a partition with fastboot flash. Or maybe I wiped something that I should not have. Anyway, by reinstalling stock, I restored all the partitions and could install CM11. I do not think CWM is to blame here.

[Q] Flashed 5.1 GPE Stock ROM; Now It Won't Boot / Has Damaged Partition

Hi guys
I have a retail XT1032 from germany and I wanted to throw 5.1 at it.
I downloaded the GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip and fired every fastboot command that was given in the servicefile.xml flashfile.xml.
After that my phone was stuck at the google logo with the little lock. I tried several combinations of waiting and reflashing and naturally none of it worked.
Then I flashed TWRP which told me it couldn't mount /system, /data, /cache and /sdcard. I did a manual format of these and did the whole fastboot procedure again... didn't work.
Next thing i tried was installing cyanogenmod on the newly and freshly repaired filesystems. Now my phone started but it had no signal. I did some "fastboot flash modem..." with a bunch of images and flashed a few radio.zip files but none of it worked :/
Now i'm sitting here with either a cyanogenmod with no service or a freshly flashed GPE 5.1 which won't boot. And I think I can't go back because of the new gpt.bin, boot.bin and motoboot.bin.
little detail I forgot: everytime i do a "fastboot flash partition gpt.bin" in my terminal it says:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.324s
and on the phone:
Code:
version downgraded for primary_gpt
Which is weird since it's the same gpt.bin I already flashed (41.19 btw.).
I suspect that's the reason for the damaged partitions but have no idea if I'm right and what to do about it
Any suggestions?
'Preflash validation failed' is normal. You would only NOT see it, if you flash a newer motoboot.img / gpt.bin.
Try flashing the GPE Optimized zip here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Also, in TWRP check /data is formatted to EXT4. See FAQ in above thread for more.
lost101 said:
'Preflash validation failed' is normal. You would only NOT see it, if you flash a newer motoboot.img / gpt.bin.
Try flashing the GPE Optimized zip here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Also, in TWRP check /data is formatted to EXT4. See FAQ in above thread for more.
Click to expand...
Click to collapse
Well it's not only that the preflash validation message comes up but the whole flash of gpt.bin fails.
Data is ext4 (i also tried f2fs but... yeah...) and i tried the recovery-flashable gpe.zip files but it didn't change anything.
But thank you very much
treax said:
Well it's not only that the preflash validation message comes up but the whole flash of gpt.bin fails.
Data is ext4 (i also tried f2fs but... yeah...) and i tried the recovery-flashable gpe.zip files but it didn't change anything.
Click to expand...
Click to collapse
Could you provide more information? Does the GPE zip flash and boot up - you just have no signal?
lost101 said:
Could you provide more information? Does the GPE zip flash and boot up - you just have no signal?
Click to expand...
Click to collapse
No it won't boot at all. While flashing one of the gpe.zips it stops with
Code:
E:Error executing updater binary in zip '/sdcard/gpe.zip'
I attached two screenshots. First one shows the partition situation right after flashing the GPE with fastboot. The second one is the error from above
That's a common error. Reboot recovery and try flashing again.
lost101 said:
That's a common error. Reboot recovery and try flashing again.
Click to expand...
Click to collapse
Nope didn't work.
Yesterday I flashed that brasil 5.0.2 image. Nothing failed and my bootloader version was 41.18 afterwards. But again the partitions weren't mountable and the system wouldn't boot. Fixed it with TWRP and flashed CM again. Now it boots and I have service... weird.
It looks a little bit like I can't flash a stock ROM now without breaking that damn thing.
@treax - look what @d3vileyes says here: http://forum.xda-developers.com/showpost.php?p=60682467&postcount=19

Hard bricked? Can't get into recovery, can't unlock bootloader

Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,
rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?
therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?
heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,
Bump!
Does anyone have any other suggestion please?
Thanks,
Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!
Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.
I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?
I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..

Recovery installation failed

Hello,
I have a Moto G (XT1032) since 3 years and all of a sudden, it didn't boot. I had the Stock ROM, I never installed a new ROM or Recovery...
I unlocked my phone and then tried to install TWRP to boot on recovery and make a backup of my data.
I tried several recoveries (twrp-2.8.6.0-xt1032, twrp-3.0.0.0_2-falcon, twrp-3.1.0-0-falcon, twrp-3.1.0-0-xt1032 & clockwork-touch-6.0.4.7-falcon).
I have no problem to send the recovery on the phone. In the fastboot mode on the phone, it says the installation is okay and then, I choose "Recovery" in the fastboot mode on the phone.
The phone reboot and I have the android logo with "No Command". I find this blog : https://wasconet.com/solution-moto-g-android-recovery-mode-no-command/ and so I hold the power button and press the volume up button to enter recovery mode screen.
The problem is, I access the default recovery — which is not TWRP, only a basic recovery where I can't mount the phone. This recovery says :
Android system recovery
LPBS23.13-56-2
...
From there I can reboot, apply update from sdcard or ADB, wipe data/factory, wipe cache, reboot to bootloader, power down or view recovery logs.
What can I do to install a good recovery and to mount my phone to make a backup ?
Thanks guys !
Lately it happens with the latest versions of twrp. Do not boot or boot once, then return the Stock Recovery again.
In my case I can not install v3.1 because it throws me max download size error. :silly:
Try the v3.0.2-2. It works without any problem over my old falcon.
https://dl.twrp.me/falcon/twrp-3.0.2-2-falcon.img.html
I'm not sure if the command works on the Falcon, but first try starting it without flashing it
fastboot boot twrp-3.0.2-2-falcon.img
By the way, can i assume that having Lollipop you have the latest version of the bootloader (41.1A)?
Thanks, it worked ! I made a backup of my files.
Now I try since this morning to install a new ROM... I tried "Factory" in the fastboot mode => Phone blocks on "Bootloader unlock".
With TWRP, I havea lot of problem with the mount. I can see the data but to copy files, it was not possible.
I mount the sdcard in Read Write with the terminal on the phone to copy the Lineage ROM. I tried to install it but I receive an error "1001".
I use now the last version of TWRP, the 3.1.0 with the command fastboot boot. This version works but I have the same error to install Lineage.
I also tried to install the stock version EU 5.1 Stock ROM (Untouched) (522mb) (from here https://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510) with adb sideload.
I saw "succesful" but the phone is always block on the "Bootloader unlock" image...
The bootloader version is indeed 41.1A.
Someone should have an idea to install a system ? (any system, I don't care, I just want a phone that I can use )
Thanks a lot !
Usually error 1001 relates to an encrypted or unreadable partition.
Have you used fastboot or mfastboot to install the system again?
Try Repair or Change file system using twrp.
Wipe>>Advanced Wipe>>
Then try to install any ROM.
If doesn't work. Inside of TWRP go to Advanced>Terminal Emulator
Then execute the command df
That should list you the partitions. Share it and if you know how to take it please share the recovery log after doing all this.
I use fastboot to just boot on the recovery.
To install, I don't tried fastboot or mfastboot. I find a guide to flash with mfastboot, I will try.
Yesterday I made all the wipe possible. Today I made a Repair on the system partition.
Here is the result of the df command :
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 446184 20 446164 0% /dev
tmpfs 446184 20 446164 0% /tmp
/dev/block/mmcblk0p33
667328 11836 655492 2% /cache
/dev/block/mmcblk0p36
5789552 5210064 528432 91% /data
/dev/block/mmcblk0p36
5789552 5210064 528432 91% /sdcard
I noticed something strange yesterday. I tried several times to delete files on the "sdcard" partition, where I found the pictures, whatsapp, ... I deleted some files with Windows (MTP Mode) and the files are always there after delete with no error message. I don't know if it's important or not.
lolo1410 said:
I I noticed something strange yesterday. I tried several times to delete files on the "sdcard" partition, where I found the pictures, whatsapp, ... I deleted some files with Windows (MTP Mode) and the files are always there after delete with no error message. I don't know if it's important or not.
Click to expand...
Click to collapse
When you unlock the bootloader, all your personal data should be deleted normally, but that didn't happen. The internal memory partition is recognized (that's good) but is unreadable, obviously corrupted. (Sorry for not noticing before)
Try installing the firmware again using mfastboot avoiding BOOTLOADER (motoboot) AND GPT files to see if works. If didn't, flash it again including GPT file (Partitions table).
If it still doesn't work, you'll have to figure out how to repartition the entire phone memory.
----------
By the way, never try to restore that DATA BACKUP. Like i say before, it's corrupted. Search a way to decompress and takes only the important files.
Thanks a lot for your time !
Indeed, it's seems there is a probleme with the filesystem.
I tried a flash of GPT & Bootloader but it didn't work.
Here is the log :
C:\adb\tmp>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.026s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.320s
&
C:\adb\tmp>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.093s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.370s
But I'm not sure if I choose the good firmware & bootloader.
On this link (http://www.filefactory.com/folder/c6cdedc45a775d27), which version can I take ?
Here is the information that I have for the phone :
Motorola G XT1032 - Type M0DEB - FCCID ihdt56pf1 buyed in Belgium
AP Fastboot Flash Mode (S)
41.1A (2015-04-10)
CPU MSM8226 CS
eMMC : 8GB Sandisk
DRAM : 1024MB Samsung S4
Try with one of these, and again. DONT FLASH BOOTLOADER (Usually cant be flashed after unlock but, I do not think you want a paperweight)
Retail EU 5.1
https://www.androidfilehost.com/?fid=24052804347848287
Retail EU 5.1 (NEWER BUILD)
https://www.androidfilehost.com/?fid=24499762636006646
You can download others from Here
https://forum.xda-developers.com/mo...rmware-t3110795?_e_pi_=7,PAGE_ID10,4937194410
After several tests, I find a good package, this : XT1032_FALCON_RETFR_5.1_LPBS23.13-56-2_cid7_CFC.xml
I had no error.
I see your message too late, I flash the bootloader
But it's a 41.1A version, here is the info on this package :
BUILD REQUEST INFO:
SW Version: falcon_retfr-user 5.1 LPBS23.13-56-2 2 release-keysMSM8626BP_1032.3116.98.00R
MBM Version: 41.1A
Modem Version: MSM8626BP_1032.3116.98.00R
FSG Version: MSM8626BP_FSG_01.101.00R
Build Fingerprint: motorola/falcon_retfr/falcon_umts:5.1/LPBS23.13-56-2/2:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 221.201.2.falcon_umts.Retail.en.FR
Model number: Moto G
Android Version: 5.1
Baseband Version: MSM8626BP_1032.3116.98.00R
Build Number: LPBS23.13-56-2
Build Date: Fri Feb 26 06:59:41 CST 2016
OTHER MISC VERSION INFO:
Subsidy Lock Config: None
Blur Version: Blur_Version.221.201.2.falcon_umts.Retail.en.FR
Version when read from CPV: falcon_retfr-user 5.1 LPBS23.13-56-2 2 release-keys
I followed the guide here https://forum.xda-developers.com/showthread.php?t=2542219 and no error during all the command. I switch off the phone and unfortunately, no boot...
It's block on the "Warning bootloader unlocked" screen...
The phone is still alive and that's good. Keep trying others roms if you want. But as I said before, surely the internal memory of the phone is corrupt. Unfortunately, I can't help you with that.
Maybe here over XDA there's a tutorial about how to solve your problem.
Okay, thanks a lot for your help.
I just tried the Retail EU 5.1 (NEWER BUILD) and same result : no error but blocks on the boot..
I will continue to test other ROM
I ended up in the same situation when trying to flash GPe on MotoG XT1032; the device was only able to boot into fastboot
After booting into TWRP, I formatted the /data partition again (in order to fallback to F2FS instead of ext4) and I used adb sideload to transfer "XT1032_Retail_Brazil_51_Untouched.zip" (you can find it on xda, under "Stock Motorola Lollipop ROM Collection" thread).
Phone was in full working condition once more

Categories

Resources