"<bootloader> Preflash Validation Failed." appears whenever I try to flash motoboot.img in the bootloader, and I'm just curious as to what this means. Thanks!
davidp799 said:
"<bootloader> Preflash Validation Failed." appears whenever I try to flash motoboot.img in the bootloader, and I'm just curious as to what this means. Thanks!
Click to expand...
Click to collapse
Motoboot.img is the bootloader. But when you flash stock 4.4.2 firmware, that image wont flash and will give you that error you say. Anyway you can relax since nothing happens if you flash back from 4.4.4 to 4.4.2 without flashing that partition. Ive downgraded to 4.4.2 a lot of times without motoboot and nothing happened to me..
Also, once you OTA upgrade for the first time to 4.4.4, you cant downgrade the bootloader (motoboot) to the one from 4.4.2, thats why it gives prevalidation error... But you can flash all the system of 4.4.2 without problems.
To sum up, bootloader motoboot.img isnt downgradable. Thats why we cannot downgrade to Jelly Bean 4.3 anymore... And we think this boot loader thing will happen again with lollipop... Maybe we won't go back to KitKat once we OTA upgrade to Lollipop, since Android 5.o will have a new boot loader, that's for sure...
MarckozZ said:
Motoboot.img is the bootloader. But when you flash stock 4.4.2 firmware, that image wont flash and will give you that error you say. Anyway you can relax since nothing happens if you flash back from 4.4.4 to 4.4.2 without flashing that partition. Ive downgraded to 4.4.2 a lot of times without motoboot and nothing happened to me..
Also, once you OTA upgrade for the first time to 4.4.4, you cant downgrade the bootloader (motoboot) to the one from 4.4.2, thats why it gives prevalidation error... But you can flash all the system of 4.4.2 without problems.
To sum up, bootloader motoboot.img isnt downgradable. Thats why we cannot downgrade to Jelly Bean 4.3 anymore... And we think this boot loader thing will happen again with lollipop... Maybe we won't go back to KitKat once we OTA upgrade to Lollipop, since Android 5.o will have a new boot loader, that's for sure...
Click to expand...
Click to collapse
Thanks for the response and yeah I figured. Lol I can't waitttttt for Lollipop! It's finally coming to us and we get to be one of the first users.
Related
SOLVED! SEE HERE!
So, I softbrick my XT1033 while I trying to upgrade from Motorola 5.0 to 5.0.1. After I tried many ways to solve the softbrick, the only solution was revert to 4.4.4 GPE and upgrade to 5.0.1 GPE.
So, please all understand that I did not want to install GPE (I already knew that I will lose dual sim on GPE), but was the only way to solve the softbrick.
But, I really don't like the GPE, and prefer the stock motorola rom for tons of reasons, but the main is the dual sim function and the camera/gallery apps.
So, my question is: Is there a way to return back from 5.0.1 GPE to stock 5.0.1?
Thanks!
Yes!
Try reading this topic:
http://forum.xda-developers.com/moto-g/help/xt1032-bricked-please-help-t2980601
Probably, you'll need to flash a new gpt.bin file. Once it's been done, you can flash the others files.
Cheers!
Ok... it works... but was a hard work to do...
1 - Downgrade from 5.0.1 GPE to 4.4.4 GPE(using fastboot, but without flashing gpt.bin and motoboot.img)
2 - Reboot into bootloader and reflash 4.4.4 GPE (now flashing gpt and motoboot)
3 - Reboot into bootloader and flash 4.4.4 Stock (flashing gpt and motoboot too). Start phone.
4 - Reboot into recovery and flash 5.0 Stock (adb sideload). Start phone, put 5.0.1 Stock update zip into internal memory.
5 - Reboot into recovery and flash 5.0.1 stock.
I had to download 6 differents roms and others files to solve this problem (about 2,2GB downloaded)...
And, WOW, now all is fine...
JAJAJAJA
Me too, brother. I had to download 4 or 5 different roms to make it run properly.
But, at least, I'm now running the 5.0.1!
Cheers!
danilocps87 said:
Ok... it works... but was a hard work to do...
1 - Downgrade from 5.0.1 GPE to 4.4.4 GPE(using fastboot, but without flashing gpt.bin and motoboot.img)
2 - Reboot into bootloader and reflash 4.4.4 GPE (now flashing gpt and motoboot)
3 - Reboot into bootloader and flash 4.4.4 Stock (flashing gpt and motoboot too). Start phone.
4 - Reboot into recovery and flash 5.0 Stock (adb sideload). Start phone, put 5.0.1 Stock update zip into internal memory.
5 - Reboot into recovery and flash 5.0.1 stock.
I had to download 6 differents roms and others files to solve this problem (about 2,2GB downloaded)...
And, WOW, now all is fine...
Click to expand...
Click to collapse
Hey mate, do you think the same process works in a xt1032 but with the corrects files?, thanks a lot
danilocps87 said:
Ok... it works... but was a hard work to do...
1 - Downgrade from 5.0.1 GPE to 4.4.4 GPE(using fastboot, but without flashing gpt.bin and motoboot.img)
2 - Reboot into bootloader and reflash 4.4.4 GPE (now flashing gpt and motoboot)
3 - Reboot into bootloader and flash 4.4.4 Stock (flashing gpt and motoboot too). Start phone.
4 - Reboot into recovery and flash 5.0 Stock (adb sideload). Start phone, put 5.0.1 Stock update zip into internal memory.
5 - Reboot into recovery and flash 5.0.1 stock.
I had to download 6 differents roms and others files to solve this problem (about 2,2GB downloaded)...
And, WOW, now all is fine...
Click to expand...
Click to collapse
Does step 2 downgrade the bootloader from 41.18 to 41.13?
Yeah Did some one with 41.18 bootloader tries this solution?
We cant go back to 41.13 bootloader...
Hi,
unfortunately I am not able to flash CM12 on my XT1032. Phone is unlocked, converted to GPE and flashed via OTA to GPE 5.0.1 so I have L bootloader. I tried many recoveries (TWRP 2.7.x.x-2.8.x.x), CWM, CWM PhilZ Touch, different CM12 versions but without succeed. The strangest thing is that latest CM11 can be installed without any problems. I have also tried to convert data partition from ext4 to f2fs.
When I am going to install .zip, I am always getting this error, no matter what I've tried:
Code:
E: executing updater binary
Cant mount /system.
Failed
I will welcome any suggestions, thank you!
I think i found a fix. Worked for me on XT 1032
That was my original post:
Okay sorry for that double posting, but i managed do find a solution to the error message while installing cm12 oder any other lollipop rom.
It seems like the system-partition size of the GPE 4.4.4 differs from the stock or cm12. Thats why i always got the error status 1 (installation aborted).
I tried to downgrade to 4.4.4 and 4.4.2 with no luck, always the same. But then i found a modified gpt.bin wich lets you "update" to the old stock 4.4.2 partition sizes.
So i flashed this gpt.bin and then the other files of the stock gpe 4.4.2. After the first boot i directly flashed the 13/01/15 nightly of cm and everything works as far as i can say now.
Here is the gpt.bin-file: http://forum.xda-developers.com/show...76&postcount=2
Thanks to Saphire007 for uploading.
priban said:
I think i found a fix. Worked for me on XT 1032
That was my original post:
Okay sorry for that double posting, but i managed do find a solution to the error message while installing cm12 oder any other lollipop rom.
It seems like the system-partition size of the GPE 4.4.4 differs from the stock or cm12. Thats why i always got the error status 1 (installation aborted).
I tried to downgrade to 4.4.4 and 4.4.2 with no luck, always the same. But then i found a modified gpt.bin wich lets you "update" to the old stock 4.4.2 partition sizes.
So i flashed this gpt.bin and then the other files of the stock gpe 4.4.2. After the first boot i directly flashed the 13/01/15 nightly of cm and everything works as far as i can say now.
Here is the gpt.bin-file: http://forum.xda-developers.com/show...76&postcount=2
Thanks to Saphire007 for uploading.
Click to expand...
Click to collapse
Thank you for your answer. According to many guides - GPE Lollipop bootloader and gpt.bin (when you updated via official OTA from Google) should have not been overridden with older versions because it can make your device bricked. Are you sure that this method is safe?
I am also considering to keep CM11 on my device and wait for official L images or new versions of recoveries/CM12.
Qaso said:
Thank you for your answer. According to many guides - GPE Lollipop bootloader and gpt.bin (when you updated via official OTA from Google) should have not been overridden with older versions because it can make your device bricked. Are you sure that this method is safe?
I am also considering to keep CM11 on my device and wait for official L images or new versions of recoveries/CM12.
Click to expand...
Click to collapse
I could flash CM11 without Problems but i got bootloops even with Retail EU Stock ROM (reboots on "Warning unlocked bootloader" message). I came from official GPE 5.0.1.
I think the gpt-file is modified because it was able to overwrite the lollipop gpt. The phone booted up and got me GPE 4.4.2 on which i could flash cm12 without any problem.
Works fine even after 1 day of heavy usage. Updated cm12 through cm-updater also. Maybe i was lucky, but it worked
priban said:
I could flash CM11 without Problems but i got bootloops even with Retail EU Stock ROM (reboots on "Warning unlocked bootloader" message). I came from official GPE 5.0.1.
I think the gpt-file is modified because it was able to overwrite the lollipop gpt. The phone booted up and got me GPE 4.4.2 on which i could flash cm12 without any problem.
Works fine even after 1 day of heavy usage. Updated cm12 through cm-updater also. Maybe i was lucky, but it worked
Click to expand...
Click to collapse
I found there is no need to revert phone back to KK. I've just flashed fixed gpt.bin and everything has started to work like a charm.
Link for fixed gpt.bin:
http://forum.xda-developers.com/showpost.php?p=57444986&postcount=1
GPT.bin -Fixed
Qaso said:
I found there is no need to revert phone back to KK. I've just flashed fixed gpt.bin and everything has started to work like a charm.
Link for fixed gpt.bin:
http://forum.xda-developers.com/showpost.php?p=57444986&postcount=1
Click to expand...
Click to collapse
Nice! I think this Fix could help many people! I wasnt sure if it worked so i tried to clean flash stock. But even better than it works without it
Qaso said:
I found there is no need to revert phone back to KK. I've just flashed fixed gpt.bin and everything has started to work like a charm.
Link for fixed gpt.bin:
http://forum.xda-developers.com/showpost.php?p=57444986&postcount=1
Click to expand...
Click to collapse
How did you get this?
gpt.bin is not flashing here:
"(bootloader) Preflash validation failed
FAILED (remote failure)"
"version downgraded for primary_gpt"
I was using stock Lollipop Soak Test, and I've tried to back to KitKat.
Now I can't boot to any version and I can't flash one. Bricked.
You are not bricked, I got the same message, fastboot flash recovery and then boot to it.
Sent from my Moto G using XDA Free mobile app
Months of Suffering Ended
priban said:
I think i found a fix. Worked for me on XT 1032
That was my original post:
Okay sorry for that double posting, but i managed do find a solution to the error message while installing cm12 oder any other lollipop rom.
It seems like the system-partition size of the GPE 4.4.4 differs from the stock or cm12. Thats why i always got the error status 1 (installation aborted).
I tried to downgrade to 4.4.4 and 4.4.2 with no luck, always the same. But then i found a modified gpt.bin wich lets you "update" to the old stock 4.4.2 partition sizes.
So i flashed this gpt.bin and then the other files of the stock gpe 4.4.2. After the first boot i directly flashed the 13/01/15 nightly of cm and everything works as far as i can say now.
Here is the gpt.bin-file: http://forum.xda-developers.com/show...76&postcount=2
Thanks to Saphire007 for uploading.
Click to expand...
Click to collapse
You have no idea how many months of frustration I've had with this thing only to find out that there's such an easy fix. THANK YOU!!!
priban said:
I think i found a fix. Worked for me on XT 1032
That was my original post:
Okay sorry for that double posting, but i managed do find a solution to the error message while installing cm12 oder any other lollipop rom.
It seems like the system-partition size of the GPE 4.4.4 differs from the stock or cm12. Thats why i always got the error status 1 (installation aborted).
I tried to downgrade to 4.4.4 and 4.4.2 with no luck, always the same. But then i found a modified gpt.bin wich lets you "update" to the old stock 4.4.2 partition sizes.
So i flashed this gpt.bin and then the other files of the stock gpe 4.4.2. After the first boot i directly flashed the 13/01/15 nightly of cm and everything works as far as i can say now.
Here is the gpt.bin-file: http://forum.xda-developers.com/show...76&postcount=2
Thanks to Saphire007 for uploading.
Click to expand...
Click to collapse
I'm pretty sure this isn't going to be replied but when I flash the gpt .bin it will typically erase everything and repartition it for the 4.4.2. So... I have to sideload a zipped official ROM or flash it from command?
There seem to be contradictory opinions regarding the downgrading procedure from 5.0.1 GPE(or other 5.0.x variants) to Motorola 4.4.4 KK .
So the question is: does flashing motoboot.img brick the device?
Examples:
http://forum.xda-developers.com/showpost.php?p=59286611&postcount=4
http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
http://forum.xda-developers.com/showpost.php?p=59135235&postcount=6
http://forum.xda-developers.com/moto-g/general/how-to-koodo-telus-downgrade-upgrade-lp-t3042110
Did I miss something or there is indeed a contradiction?
You cannot downgrade the 41.18 LP bootloader. If you try, you will receive a validation error.
So the worst case scenario for flashing motoboot.img is an validation error, but it will not brick the phone? I'm confused because here @LeopardSurd says that the phone can not boot if you do not flash motoboot.img.
sigma95 said:
So the worst case scenario for flashing motoboot.img is an validation error, but it will not brick the phone? I'm confused because here @LeopardSurd says that the phone can not boot if you do not flash motoboot.img.
Click to expand...
Click to collapse
This was simple my experience: flashed 4.4.4 without motoboot => the phone don't boot. Flashed only motoboot.img => phone don't boot. Flashed all the commands including motoboot.img => phone boots.
LeopardSurd said:
This was simple my experience: flashed 4.4.4 without motoboot => the phone don't boot. Flashed only motoboot.img => phone don't boot. Flashed all the commands including motoboot.img => phone boots.
Click to expand...
Click to collapse
Thanks for answering.
Did you get a validation error when you flashed motoboot.img?
It strange that some people could boot 4.4.4 without flashing motoboot.
I have not seen any posts where a person was able to downgrade from the LP 41.18 bootloader to a KK bootloader. I'd like to know how they did it because I would like to do the same.
I have searched the forum and I reached the following conclusion:
Flashing 4.4.4 motoboot.img does not brick your phone, but it gives a validation error.(But in some cases you can not boot without flashing it(see above))
(Has anyone bricked their phone by flashing 4.4.4 motoboot?)
The problem seems to appear only when upgrading from 4.4.2 to 4.4.4.
The validation error will stop the flash process.
I have a KitKat nandroid and 41.18 bootloader (right now I'm with Lollipop), it will brick my phone if I restore the nandroid to go back to KitKat?
The nandroid should not touch the bootloader.
Which version of LP is on your phone? Restoring may cause a bootloop.
audit13 said:
The validation error will stop the flash process.
Click to expand...
Click to collapse
As I understand it, the flashing process of the motoboot.img will be stopped(remote error), but you can continue flashing other files.
Several users reported that this method works(and it implies flashing motoboot.img), so I'm inclined to say that 4.4.4 motoboot does not cause loosing access to fastboot(hardbrick). The only side-effect should be the "line bug", which can be solved by turning the screen on&off.
Am I missing something?
I meant to say the validation error will stop the flash process for motoboot.img.
The line bug remains after downgrading from LP because everything is being downgraded to KK with the except of the bootloader which remains on LP. If there was a way to downgrade the bootloader to KK, the line issue would disappear.
audit13 said:
The nandroid should not touch the bootloader.
Which version of LP is on your phone? Restoring may cause a bootloop.
Click to expand...
Click to collapse
I am on stock 5.0.2 Lollipop :fingers-crossed:
@Feche, let us know what happens and best of luck:good:
audit13 said:
@Feche, let us know what happens and best of luck:good:
Click to expand...
Click to collapse
Hey, I managed to go back to KitKat and restore my nandroid but I had to do some things first:
Restore from Lollipop to KitKat is not possible since when restoring the data partition phone will freeze around 30mb~ mark and reboot.. so what I did was downgrade to stock 4.4.4 (via mfastboot) and then restore the nandroid.
The only problem is that if you want to go again to Lollipop you can't becouse when restoring the data partition the phone will reboot when reaching 99%.. what you can only restore is system partition, so you will end up with a fresh stock Lollipop.. I bet this is due to the repartitioning of Lollipop, we have to wait for a recovery (TWRP, CWM) with Lollipop support.
I think i t has something to do with the gtp.bin having to be flashed via fastboot before restoring a KK nandroid.
Great that it worked.
Feche said:
Hey, I managed to go back to KitKat and restore my nandroid but I had to do some things first:
Restore from Lollipop to KitKat is not possible since when restoring the data partition phone will freeze around 30mb~ mark and reboot.. so what I did was downgrade to stock 4.4.4 (via mfastboot) and then restore the nandroid.
The only problem is that if you want to go again to Lollipop you can't becouse when restoring the data partition the phone will reboot when reaching 99%.. what you can only restore is system partition, so you will end up with a fresh stock Lollipop.. I bet this is due to the repartitioning of Lollipop, we have to wait for a recovery (TWRP, CWM) with Lollipop support.
Click to expand...
Click to collapse
This is not related to your problem, but did you flash motoboot.img when you downgraded to 4.4.4?
sigma95 said:
This is not related to your problem, but did you flash motoboot.img when you downgraded to 4.4.4?
Click to expand...
Click to collapse
motoboot.img and gpt.bin won't flash since it gives validation error, the rest is the same
I just downgraded my XT1032 (falcon) from stock 5.0 to stock 4.4 and it won't boot anymore. I did it using the fastboot method (flashing several .img or .bin files using fastboot), as I had done it many times before in order to revert the phone to stock.
But this time it won't boot no matter what I do. It may be related to the fact that I accidentally tried to flash 4.4 partition table and bootloader (now I see the downgrading tutorials recommend against that) but I don't know what to do.
I tried pushing another ROM (in the ZIP format) via ADB, but when I try to install that ZIP in TWRP recovery, it says "unable to mount data" or "unable to mount storage". It also used to say "unable to mount system" but I think I fixed that with "fastboot format system" (which you can't do for /data).
I think I'd need Android 5 .img and .bin files in orden to fix this via fastboot, but Android 5 doesn't seem to exist in that format.
Can anyone think of a solution? Thanks in advance.
Does your phone still have the 41.18 bootloader on it?
I'm surprised that it bricked because I flash every partition except motoboot when downgrading my xt1032 8 GB from LP to KK.
U did it with unlocked bootloader or locked one..?? I am looking for a tutorial on downgrading to 4.4.4. from 5.0.2 for locked bootloader..
Unlocked bootloader. If possible, unlock the bootloader as you may not be able to downgrade without unlocking.
i am also faced this problem......after reflashing the kitkat os my moto g is booted(dont flash motoboot and gpt)
seshuganesh2011 said:
i am also faced this problem......after reflashing the kitkat os my moto g is booted(dont flash motoboot and gpt)
Click to expand...
Click to collapse
How did u reflashed..?? Can u tell me the xact procedure..?? And on Locked bootloader..??
kaymaddy said:
How did u reflashed..?? Can u tell me the xact procedure..?? And on Locked bootloader..??
Click to expand...
Click to collapse
i flashed on unlocked boot loader
I first restore to stock 4.4.4 from CM11 by manually flashing falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip. Everything worked.
After that, I try to upgrade to stock 5.1 by manually flashing XT1031_FALCON_BOOST_5.1_LPB23.13-56_cid9_CFC.xml.zip with mfastboot. Every part seemed to flashed successfully, but when it is finished, it won't boot and stuck at bootloader unlocked screen.
Now I cannot downgrade to 4.4.4 since the gpt.bin and motoboot.bin all failed preflash verification. I guess the bootloader won't allow downgrade. Even with all other parts successfully flashed, it is still stuck at booloader unlocked screen.
I also tried to flash twrp 2.8.7.0, but it also failed due to partition size different. (Is it because twrp can only be flashed under 4.4.4 bootloader?)
So I am stuck now. Please help me. How do I flash stock 5.1 and later CM12.1? Thanks in advance.
Try flashing the firmware with RSD Lite and see what happens.
Sent from my XT1031
Fixed. I found a stock rom 4.4.4 downgrade package from here.
https://www.reddit.com/r/MotoG/comments/3omnox/moto_g_xt1031_boost_lollipop_stock_rom/
It has same contents as the 4.4.4 stock rom package I downloaded from filefactory, except there is a fastboot.exe boundled in this package (dated 6/25/2014) that is newer than the one I was using (dated 3/20/2013). This one successfully restored my XT1031 to 4.4.4 stock.
Flashed of twrp and also flashed stock 5.1 optimized from twrp. Both went well.
kzqc said:
I first restore to stock 4.4.4 from CM11 by manually flashing falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip. Everything worked.
After that, I try to upgrade to stock 5.1 by manually flashing XT1031_FALCON_BOOST_5.1_LPB23.13-56_cid9_CFC.xml.zip with mfastboot. Every part seemed to flashed successfully, but when it is finished, it won't boot and stuck at bootloader unlocked screen.
Now I cannot downgrade to 4.4.4 since the gpt.bin and motoboot.bin all failed preflash verification. I guess the bootloader won't allow downgrade. Even with all other parts successfully flashed, it is still stuck at booloader unlocked screen.
I also tried to flash twrp 2.8.7.0, but it also failed due to partition size different. (Is it because twrp can only be flashed under 4.4.4 bootloader?)
So I am stuck now. Please help me. How do I flash stock 5.1 and later CM12.1? Thanks in advance.
Click to expand...
Click to collapse
Just install latest TWRP it is compatible with Lollipop or CWM then flash CM12.1
Paradox♀ said:
Just install latest TWRP it is compatible with Lollipop or CWM then flash CM12.1
Click to expand...
Click to collapse
Thanks.