Related
This is a guide that is strictly for those who are as impatient as I am to get Lollipop on their Moto G (2014). I know there are several guides for folks in the US, and other countries as well, but currently there is no OTA for Canada yet. We are literally left out in the cold. So, I thought I would put a collaborative guide together so the Canadians can enjoy some 5.0, too!
First and foremost, if you F up your phone, that's on you. This will void your warranty, and I am in no way responsible for any stupidity you conjure up during the process.
I have only tested this on the XT1064, which is the single SIM US/Canada model.
The issue when trying to simply follow the upgrade guide for the XT1064 is that the OTA file looks for a 4.4.4 variant of Android that needs to be the same region as where the OTA came from. If you try to install it on the Canadian versions, you will get an error. So, here goes:
1. Unlock your bootloader. Follow this wonderful guide: http://forum.xda-developers.com/mot...wip-unlock-bootloader-moto-g-2nd-gen-t2875728
2. Download the US version of 4.4.4, it can be found here: http://www.filefactory.com/file/2ygnt0x45vcr/RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
3. Extract the above file to the same location you installed Minimal ADB in the first step (C:\Program Files(x86)\Minimal ADB and Fastboot)
4. Turn your phone off and disconnect it from the computer. Press and hold the volume down (-) button and power button to get into Fastboot mode. Connect your phone to the computer.
5. Run Minimal ADB and run these commands:
PHP:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot reboot
I removed the modem commands on purpose, and I will explain why later.
6. Once the phone has rebooted, plug it in to the computer and follow this guide: http://forum.xda-developers.com/moto-g-2014/development/lollipop-moto-g-2014-xt1064-t2937361
You should now have Lollipop on your Canadian XT1064!
If you have issues with the WiFi or cellular, you may have to flash the modem commands again from the old file. I had to download the original Canadian ROM (http://www.filefactory.com/file/78znv8hx0tvt/RETCA_XT1064_4.4.4_KXB21.85-16_cid14_CFC.xml.zip) and using Fastboot flash the following:
PHP:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
After that I had no issues and everything seems to be working as it should. You can relock your bootloader afterwards if you like as well.
Thanks to the other contributors above, I was simply trying to put a quick guide together for us Canadian folks who wish to get Lollipop, too!
Cheers!
This is great - although I think I'm still "out in the cold." I have 11.24 and couldn't flash the above due to "downgrading." Unless I'm missing something... Any ideas?
This worked for me! Thanks for the awesome tutorial!
brianshayne said:
This is great - although I think I'm still "out in the cold." I have 11.24 and couldn't flash the above due to "downgrading." Unless I'm missing something... Any ideas?
Click to expand...
Click to collapse
At which part do you get an error? Are you trying to use a script to flash, or are you doing exactly step by step like mentioned above? I had the latest of the late on my Moto G 2014, so I know that these steps work on it.
Is your bootloader unlocked as mentioned above?
NexusChrist said:
At which part do you get an error? Are you trying to use a script to flash, or are you doing exactly step by step like mentioned above? I had the latest of the late on my Moto G 2014, so I know that these steps work on it.
Is your bootloader unlocked as mentioned above?
Click to expand...
Click to collapse
Yeah - I'm not sure what the problem was - originally it wouldn't take the US ROM due to a downgrade error. Tried it again, after a factory reset and for some reason it went through. Flashing Lollipop and the modem after was no issue at all - so good to go now. It's beautiful.
Thanks for the follow-up.
AKA: I should have just ignored downgrade error + HAB fail on phone, the first time around
I am getting hab check failed for boot when i use the command " fastboot flash boot boot.img "
please help
ramzilla136 said:
I am getting hab check failed for boot when i use the command " fastboot flash boot boot.img "
please help
Click to expand...
Click to collapse
Disregard the error and move on to the next command. You are going to get a few errors. Don't worry.
installing update
verifying current system
/system/app/3c_main.apl has unexpected contents
installation aborted
this is after i run the commands and upload from sd card...
followed your commands and tried few fresh zips
can you please help, it won't let me install the lollipop file
Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot erase cache
fastboot erase userdata
fastboot reboot
TiGuy82 said:
Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Is this procedure better? Any enhancement? Thanks.
Botsok said:
Is this procedure better? Any enhancement? Thanks.
Click to expand...
Click to collapse
This one just avoid you to flash USA KitKat and then Lollipop. This one goes directly to Lollipop.
Doesn't flash Modem/Radio from USA Lollipop because doesn't work on Canadian models, at least didn't work with WIND Mobile model.
WIND canada moto G XT1064 lollipop
Thanks very much for posting this. and thanks for posting the link for 5.02 from MEGA which is a lot faster than filefactory!
I've attached a link to the original Wind 4.4 modem files in case someone's modem doesn't work afterwards, if they followed the top post original instructions and accidentally flashed the US KitKat 4.4 modems.. instead of downloading that huge file from filefactory.com (extremely slow site), the link has just the 2 files (22MB).
https://mega.co.nz/#!dk430ZBZ!diHa6V-rcidHFc3niGjshk-2A9ELbqZtCnb63pFK010
Also may be worth mentioning to ignore the "hab check failed" messages when flashing lollipop. (I was using mfastboot)
TiGuy82 said:
Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Just a super-dooper-uber Thanks To NexusChrist!
Who ever you are, I tried to follow your system. it didn't work for me, infact I lost wifi connection, but anyways what I did was I used another script for this (http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167) And this worked, but now I lost Cellular Service....Big problem eh? Well no more, thanks to you. I downloaded the Canadian rom, and just to be more specific (cause it was kinda vague in the tutorial, (Extract the files again to the Mininal ADB fastboot file location the whole c drive thing yenno?)) And I ran that php and BAM thank you so much I was worried out of my MIND that I f'ed up my phone somehow. Foreal, bless your soul....or your XT1064?
No XT1064s were hurt in the making of this post
UnderAppreciatedDev said:
Who ever you are, I tried to follow your system. it didn't work for me, infact I lost wifi connection, but anyways what I did was I used another script for this (http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167) And this worked, but now I lost Cellular Service....Big problem eh? Well no more, thanks to you. I downloaded the Canadian rom, and just to be more specific (cause it was kinda vague in the tutorial, (Extract the files again to the Mininal ADB fastboot file location the whole c drive thing yenno?)) And I ran that php and BAM thank you so much I was worried out of my MIND that I f'ed up my phone somehow. Foreal, bless your soul....or your XT1064?
No XT1064s were hurt in the making of this post
Click to expand...
Click to collapse
That happened because you flash the modem from Lollipop... Just flash the modem in OP and you will be ok.
spiritflare said:
Thanks very much for posting this. and thanks for posting the link for 5.02 from MEGA which is a lot faster than filefactory!
I've attached a link to the original Wind 4.4 modem files in case someone's modem doesn't work afterwards, if they followed the top post original instructions and accidentally flashed the US KitKat 4.4 modems.. instead of downloading that huge file from filefactory.com (extremely slow site), the link has just the 2 files (22MB).
Also may be worth mentioning to ignore the "hab check failed" messages when flashing lollipop. (I was using mfastboot)
Click to expand...
Click to collapse
Just a tad bit curious I also have a Wind Mobile Moto G2 and i'm just wondering how you unlocked the bootloader in the first place. If you could please share the process on how you did it that would be great.
Anyone know how we can get the LP bootloader on the Canadian version?
I'd like to be able to update my CM12.
Thanks!
Awesome
I'm on Bell &
everything is working 100% radio/wifi/bluetooth all good
Thanks
This is a great guide. But I'm wondering if we've been given any explanation on why Canadian Moto G's aren't getting OTA updates? It's April and my Moto G is saying up to date with 4.4.4. It's from wind if that matters.
I understand we can do this work around. I'm just trying to understand why we're not getting updates.
Kewjoe said:
This is a great guide. But I'm wondering if we've been given any explanation on why Canadian Moto G's aren't getting OTA updates? It's April and my Moto G is saying up to date with 4.4.4. It's from wind if that matters.
I understand we can do this work around. I'm just trying to understand why we're not getting updates.
Click to expand...
Click to collapse
Your carrier is most likely the reason since they have the final say on updates.
Tel864 said:
Your carrier is most likely the reason since they have the final say on updates.
Click to expand...
Click to collapse
But what about the people that bought their phones from Staples. It's unlocked and not associated to any carrier. They are directly under Motorola and still no update at all. Phone are getting 5.1 update already, but we're still at 4.4.4
What's so different in the Canadian market from the US one that the update can't come fast? Specially if the phone is not associated to a carrier and the update should come directly from Motorola
i just restored my moto x pure back to lolipop due to issue and no my wifi wont work so i ca update my phone to marhsmellow, the switch keeps turning on and off and doesnt show no networks. it frusterating
Flash LP radio for 5.1.1 If you plan on staying on LP.
Sent from my XT1575 using Tapatalk
patt2k said:
Flash LP radio for 5.1.1 If you plan on staying on LP.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
where can i get that? also im going to upgrade to marshmallwo which is why im trying to get wifig oing!
tecnikstr0be said:
where can i get that? also im going to upgrade to marshmallwo which is why im trying to get wifig oing!
Click to expand...
Click to collapse
You don't need wifi to update to marshmallow. Just sideload ota. And you will be OK.
Sent from my XT1575 using Tapatalk
patt2k said:
You don't need wifi to update to marshmallow. Just sideload ota. And you will be OK.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
well i flash non-hols.bin and no my wifi works and the update to marshmallow appeared and is downloading. so for now on i will get OTA updates normally now since i used return to stock tool? with marshmallow everything i need will be updated? modems too?
tecnikstr0be said:
well i flash non-hols.bin and no my wifi works and the update to marshmallow appeared and is downloading. so for now on i will get OTA updates normally now since i used return to stock tool? with marshmallow everything i need will be updated? modems too?
Click to expand...
Click to collapse
It should update your radio after mm ota
Sent from my XT1575 using Tapatalk
patt2k said:
It should update your radio after mm ota
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
it said there was a problem updating my moto x pure edition. no changes were made. installation unsuccesful...
patt2k said:
It should update your radio after mm ota
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
what do i do?
Do you have custom recovery? Is your system partition completely stock? If you ever had root then you system partition is no completely stock. Its an easy fix. I just downloaded the LP firmware but just flashed the all the system partition files and then did the OTA. No problems. I literally did that about half an hour ago. I had a rooted MPXE on 5.1. I flashed stock recovery and the system partition then took the OTA.
razieltov said:
Do you have custom recovery? Is your system partition completely stock? If you ever had root then you system partition is no completely stock. Its an easy fix. I just downloaded the LP firmware but just flashed the all the system partition files and then did the OTA. No problems. I literally did that about half an hour ago. I had a rooted MPXE on 5.1. I flashed stock recovery and the system partition then took the OTA.
Click to expand...
Click to collapse
Can you guide me in how you do this with the partition? Yes I have rooted it before,I want my phone back to normal already! If not I'll get a nexus 6p
Download firmware from here.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Do you know how to use fastboot?
It will be a zip file. Unzip it. There is a batch file called Flash-all. If you right click it and click edit. It will show you everything that it does. If you have a customer recovery then copy and paste this part
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot erase cache
fastboot reboot
That will flash the stock recovery and the system partition and then you will be able to do the OTA.
razieltov said:
Download firmware from here.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Do you know how to use fastboot?
It will be a zip file. Unzip it. There is a batch file called Flash-all. If you right click it and click edit. It will show you everything that it does. If you have a customer recovery then copy and paste this part
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot erase cache
fastboot reboot
That will flash the stock recovery and the system partition and then you will be able to do the OTA.
Click to expand...
Click to collapse
Yes I have fast boot installed and Motorola drivers.. So I all do is turn on my bootlaoder and afb then put those commands?
razieltov said:
Download firmware from here.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Do you know how to use fastboot?
It will be a zip file. Unzip it. There is a batch file called Flash-all. If you right click it and click edit. It will show you everything that it does. If you have a customer recovery then copy and paste this part
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot erase cache
fastboot reboot
That will flash the stock recovery and the system partition and then you will be able to do the OTA.
Click to expand...
Click to collapse
what if I don't have a custom recovery but lollipop that does a error when I try to update to marshmallow or a old marshmallow version?
tecnikstr0be said:
what if I don't have a custom recovery but lollipop that does a error when I try to update to marshmallow or a old marshmallow version?
Click to expand...
Click to collapse
Then don't worry about flashing stock recovery.
razieltov said:
Then don't worry about flashing stock recovery.
Click to expand...
Click to collapse
So why does it do an error when I download ota marshmallow while installing and fails?
Because your system partition isn't completely stock. That is why you have to reflash the stock system partition.
razieltov said:
Download firmware from here.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Do you know how to use fastboot?
It will be a zip file. Unzip it. There is a batch file called Flash-all. If you right click it and click edit. It will show you everything that it does. If you have a customer recovery then copy and paste this part
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot erase cache
fastboot reboot
That will flash the stock recovery and the system partition and then you will be able to do the OTA.
Click to expand...
Click to collapse
which exact rom did you get from the page you linked me? There's 3 and BTW I have twrp installed... Do I remove it? I want the most recent marshmallow I messed up messing with my phone
tecnikstr0be said:
which exact rom did you get from the page you linked me? There's 3 and BTW I have twrp installed... Do I remove it? I want the most recent marshmallow I messed up messing with my phone
Click to expand...
Click to collapse
TWRP is custom recovery so you do need to flash stock recovery.
On that page click on the button under 5.1.1
Then click on the button under XT1575 Firmware
Then download the 5.1.1 FIRMWARE
razieltov said:
TWRP is custom recovery so you do need to flash stock recovery.
On that page click on the button under 5.1.1
Then click on the button under XT1575 Firmware
Then download the 5.1.1 FIRMWARE
Click to expand...
Click to collapse
OK so after I download that I flash it by wiping my phone with custom twrp and putting the file in the backups folder and restoring it? I disregard those fastboot commands you told me? After restoring it and when I boot into the phone. When it tells me to download marshmallow, I install it but when its installing it gives me an error. What do I do from there if that happens?
tecnikstr0be said:
OK so after I download that I flash it by wiping my phone with custom twrp and putting the file in the backups folder and restoring it? I disregard those fastboot commands you told me? After restoring it and when I boot into the phone. When it tells me to download marshmallow, I install it but when its installing it gives me an error. What do I do from there if that happens?
Click to expand...
Click to collapse
No you download the firmware and then you do the fastboot commands. The fastboot commands will install stock recovery and the stock system paritition. The OTA won't work with TWRP. You can install TWRP after the OTA. Also if you wan't root make sure you use the systemless root not the regular SuperSU. If you wan't to do that we can discuss it after you do the OTA.
Hello everyone
2 days ago I received the message that finally the update for my device was available, specifically NPJ25.93-14, the download was made and proceeded to install, the installer only advanced very little and failed the installation, I check the recovery log And so I could understand the installation script failed because I did not find the expected base version:
Verifying Current System
script aborted: Error E3002:
Packaged expects build thumbprint of 7.0/NPJ25.93-14/16:user/release-keys or
6.0.1/MPJ24.139-48/48:user/release-key; this device has 6.0.1/MPJ24.139-64/65:user/release-key
E:Error in @/cache/recovery/block.map
I would appreciate your help in analyzing the cause of failure in the installer and how I can solve it to perform the installation of the update successfully.
Thank you
what the.., i don't know why the log says " 6.0.1/MPJ24.139-64/65" if you really have 48. So.. maybe you can reinstall your rom
lerg96 said:
what the.., i don't know why the log says " 6.0.1/MPJ24.139-64/65" if you really have 48. So.. maybe you can reinstall your rom
Click to expand...
Click to collapse
In fact I did, reinstall the firmware using the official provided by motorola.
suarezj said:
In fact I did, reinstall the firmware using the official provided by motorola.
Click to expand...
Click to collapse
did you install in the past a -64 rom?
Maybe if you had 64 previously and you tried to install 48 it really was not installed correctly because it was a downgrade
There is not a ota for -64 that you can use for nougat around the forum?
like many of us, I have a rooted, bootloader unlocked retus xt1625 with TWRP installed. Has anyone been able to get the nougat update to install? My version is MPJ24,139-49
I tried to run the update and it booted into my twrp recovery. But I got the same message as above
Does some sort of downgrade need to happen allow it to accept the update?
lerg96 said:
did you install in the past a -64 rom?
Maybe if you had 64 previously and you tried to install 48 it really was not installed correctly because it was a downgrade
There is not a ota for -64 that you can use for nougat around the forum?
Click to expand...
Click to collapse
honestly I can't ensure if the phone had a firmware version 64 or not, i've changed firmware 2 times, both firmware were stock Motorola.
I'm going to check my computer, I sure leave a copy of the firmware that I installed at that moment and I'll be able to check the version
*******************************************************************************************************
Following the recommendation, perform a firmware download provided by motorola again, I did a clean installation again and the result is exactly the same again, the motorola website indicates that the version is 64, but the phone still indicates is The installed version is 48. Assuming I could have done a dowgrade from 64 to 48, the question is, is there a way to correct this?
well buddy, really i can't tell you. Maybe you can try forcing a update downloading the ota and changing the line that verify your rom in the zip file. If you're in the correct build version for the update maybe you can have a success update
For all this process you need TWRP, because the stock recovery verify if the zip file is signed. (Motorola and i are not responsible for any damage)
Finally solved
suarezj said:
Hello everyone
2 days ago I received the message that finally the update for my device was available, specifically NPJ25.93-14, the download was made and proceeded to install, the installer only advanced very little and failed the installation, I check the recovery log And so I could understand the installation script failed because I did not find the expected base version:
Verifying Current System
script aborted: Error E3002:
Packaged expects build thumbprint of 7.0/NPJ25.93-14/16:user/release-keys or
6.0.1/MPJ24.139-48/48:user/release-key; this device has 6.0.1/MPJ24.139-64/65:user/release-key
E:Error in @/cache/recovery/block.map
I would appreciate your help in analyzing the cause of failure in the installer and how I can solve it to perform the installation of the update successfully.
Thank you
Click to expand...
Click to collapse
Well, I've finally been able to resolve the problem with the firmware update, how? simple ..
1.- Download a firmware for the version of my phone, I decided on the 64 version due to the inconsistency that my phone had between what the updater detected and the build that the phone reported as installed. My objective was not to downgrade
I did not want to make firmware downgrade
https://firmware.center/firmware/Motorola/Moto%20G4%20%28Plus%29/Stock/XT1625-XT1644_ATHENE_RETUS_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2.- I did the installation using the fastboot method
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
3.- When the phone reboot after the installation check the compilation version and the inconsistency had disappeared. Check if there were pending updates and yes, had one. Download and install without problems.
Thank you all for your time and collaboration. :good:
Dear Team, I have MotoG4 Plus (Model XT1643).
Post selecting the data migration from internal storage to SD card, the phone stopped booting.
[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode
Kindly suggest
Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?
Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.
You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?
chetana22 said:
Dear Team, I have MotoG4 Plus (Model XT1643).
Post selecting the data migration from internal storage to SD card, the phone stopped booting.
[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode
Kindly suggest
Click to expand...
Click to collapse
Are u using dummy bootloader I guess not orginal
---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------
No need to reflash u have to upgrade the bootloader then u have to flash the stock rom
@ Echo
Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?
<<<< I was transferring data from phone memory to memory card via an option which says move media to SD card >>>>
Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.
You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?
<<<< I have no idea about stock ROM build. If you can help, how would I know since my device is not starting? >>>>
@ usha55
Are u using dummy bootloader I guess not orginal
<<<< I do not know >>>>
---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------
No need to reflash u have to upgrade the bootloader then u have to flash the stock rom
<<<< How do I upgrade? Please guide >>>>
@chetana22 thas makes confusion if you write post like that.
You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.
____Mdd said:
@chetana22 thas makes confusion if you write post like that.
You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.
Click to expand...
Click to collapse
Hi.
Im not able to upload the image. Pl. find baseband details below.
Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST
Pls let me know steps to reflash boot.img
chetana22 said:
Hi.
Im not able to upload the image. Pl. find baseband details below.
Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST
Pls let me know steps to reflash boot.img
Click to expand...
Click to collapse
If you have locked bootloader, flashing of older boot.img may not work. You need to flash whole firmware.
See here,
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138/page8
Download it and flash it, instructions are given there.
If you have important data on your phone, say photos/videos/or any file, then skip "erase userdata" command.. when you get device working, copy your data and then wipe your device.
Tried the method as given.
At the end ..it is repeatedly showing
FAILED (remote failure)
chetana22 said:
Tried the method as given.
At the end ..it is repeatedly showing
FAILED (remote failure)
Click to expand...
Click to collapse
Which stock firmware are you flashing that gives you this error? Please mention the build number.
You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash as per below commands if you want to save your data (no need to re-lock your bootloader).
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
It does not work
echo92 said:
Which stock firmware are you flashing that gives you this error? Please mention the build number.
You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash as per below commands if you want to save your data (no need to re-lock your bootloader).
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
It does not work
al3al3al3jandr0 said:
It does not work
Click to expand...
Click to collapse
What didn't work, please describe more about what happened?
From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.
Now the error sends it to me in the boot.img
echo92 said:
What didn't work, please describe more about what happened?
From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.
Click to expand...
Click to collapse
Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img
al3al3al3jandr0 said:
Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img
Click to expand...
Click to collapse
1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.
2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.
Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.
3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.
thank you
echo92 said:
1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.
2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.
Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.
3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.
Click to expand...
Click to collapse
ok thank you very much, you're right I'll have to wait
Sir, how to fix no found bootimage in m0t0 g4plus XT1643
Adityashankar said:
Sir, how to fix no found bootimage in m0t0 g4plus XT1643
Click to expand...
Click to collapse
Did this happen suddenly, and is this with the stock firmware or using a custom ROM?
You could try flashing the Oreo stock firmware: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Hello team, I have the same problem like chetana22 but with motorola one xt-1941-4. When i was transfering (probably) virus file from internal storage to usb flash memory, the phone stopped booting.
I have inportant and private files on internal storage, phone have quarantee... What can i do? Pls help
flash latest stock rom and skip the following instruction while flashing
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
MOTOROLA G5S PLUS - Start up failed
My phone is G5s PLUS ... Sorry
Hi All,
Moto G4 Plus XT1643 is my phone model.
Was not being used for past 6 months, and it got stuck the boot screen .
Tried the factory reset, it got stuck in the fast boot.
Then tried the tool given by Lenovo, no luck. The "fast boot" option in the software fails.
Anyway, came to our good old XDA.
tried the options in the forum https://forum.xda-developers.com/t/...c-01-security-patch-fastboot-7-0-8-1.3608138/
Now, i am stuck with the below screens, i have attached them
Allso, do i need to start a separate thread?
Kindly help me out.
Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?
squanch123 said:
Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?
Click to expand...
Click to collapse
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.
squanch123 said:
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.
Click to expand...
Click to collapse
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?
echo92 said:
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?
Click to expand...
Click to collapse
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?
squanch123 said:
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?
Click to expand...
Click to collapse
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?
echo92 said:
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?
Click to expand...
Click to collapse
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.
squanch123 said:
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.
Click to expand...
Click to collapse
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).
echo92 said:
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).
Click to expand...
Click to collapse
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?
squanch123 said:
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?
Click to expand...
Click to collapse
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).
echo92 said:
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).
Click to expand...
Click to collapse
Yes that worked
Thank you very much for your help :victory: