UK xt1092 received - X 2014 General

The title should have "update"... Thanks autoincorrect.
Sent from my XT1052 using XDA Free mobile app

Mine's just on the way down.

Just got mine but it won't update. I have no idea why. Maybe it's because I have a custom recovery?
It says it's expected to have a version ie victara and I have cm_victara. Any one know how to get this to update? My phone is currently rebooting constantly unless I turn it off myself.

Custom recovery is why. Look for guides to reflash

kboya said:
Custom recovery is why. Look for guides to reflash
Click to expand...
Click to collapse
I just used multi tool to install the stock recovery and wipe but it still won't work. Any ideas?

Please can someone upload the GB Retail firmware for the XT1092 if they have now got this successfully. Thanks!

Thats interesting, so the EU and GB versions have the same baseband.
Might be alright to stick to the EU firmware for now then, maybe it gets the next update faster

There's nothing on the surface to mark it out as being GB specific.
To be fair, I'm not sure a week's update difference is enough for me to care.

transmission1 said:
Please can someone upload the GB Retail firmware for the XT1092 if they have now got this successfully. Thanks!
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36

Diesel779 said:
Here you go: http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Click to expand...
Click to collapse
Hey any ideas how i can go about installing that? Ive tried to use Multi tool to get stock but now it says my phone is xt1095 but it was originally xt1092 :/ ive tried to find the uk stock firmware but no luck.

AllenLoyola23 said:
Hey any ideas how i can go about installing that? Ive tried to use Multi tool to get stock but now it says my phone is xt1095 but it was originally xt1092 :/ ive tried to find the uk stock firmware but no luck.
Click to expand...
Click to collapse
It's a factory image you can flash it over anything you currently have running. Open the Multi tool folder and you will see some called 'msfastboot' Make a new folder on your desktop and place that in there, then download the factory image I gave you the link for and extract it into the same folder you placed the msfastboot into. Then, whilst in that folder hold the shift key on your keyboard and then right click on your mouse and select 'open a command window here' Then put your phone in fastboot by turning it off and holding the power and volume down keys at the same time. Then, in the terminal you opened earlier type these commands one at a time:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin (REMOVES YOUR CUSTOM BOOTLOGO (Not neccessary))
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata (FACTORY RESETS YOUR FLASH MEMORY (Not neccessary))
mfastboot erase customize (REMOVES MOTOMAKER CUSTOMIZATIONS (Not neccessary))
mfastboot erase clogo (REM
mfastboot reboot

AllenLoyola23 said:
Hey any ideas how i can go about installing that? Ive tried to use Multi tool to get stock but now it says my phone is xt1095 but it was originally xt1092 :/ ive tried to find the uk stock firmware but no luck.
Click to expand...
Click to collapse
Multi-Tool is made for the XT1095, so that's probably why. It even says that in the title.
You can use my guide here, to convert your phone back to XT1092 and get RETEUALL instead.

Lafenear said:
Multi-Tool is made for the XT1095, so that's probably why. It even says that in the title.
You can use my guide here, to convert your phone back to XT1092 and get RETEUALL instead.
Click to expand...
Click to collapse
Diesel779 said:
It's a factory image you can flash it over anything you currently have running. Open the Multi tool folder and you will see some called 'msfastboot' Make a new folder on your desktop and place that in there, then download the factory image I gave you the link for and extract it into the same folder you placed the msfastboot into. Then, whilst in that folder hold the shift key on your keyboard and then right click on your mouse and select 'open a command window here' Then put your phone in fastboot by turning it off and holding the power and volume down keys at the same time. Then, in the terminal you opened earlier type these commands one at a time:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin (REMOVES YOUR CUSTOM BOOTLOGO (Not neccessary))
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata (FACTORY RESETS YOUR FLASH MEMORY (Not neccessary))
mfastboot erase customize (REMOVES MOTOMAKER CUSTOMIZATIONS (Not neccessary))
mfastboot erase clogo (REM
mfastboot reboot
Click to expand...
Click to collapse
Thanks guys. I'm stuck tho. It says I'm missing AdbWinApi.DLL which is a driver right? I've got AndroidSDK tho so I don't why that's popping up.

AllenLoyola23 said:
Thanks guys. I'm stuck tho. It says I'm missing AdbWinApi.DLL which is a driver right? I've got AndroidSDK tho so I don't why that's popping up.
Click to expand...
Click to collapse
I wouldn't bother with the RETEU version if you're in the UK, the link I gave you is to the official RETGB factory image. As regards your problem try putting the msfastboot in your ADB folder and also extract your RETGB zip into the same folder, then open up a terminal in that folder and run the commands. Also, have you put your phone in fastboot and let Window automatically install the fastboot driver for your device?
Edit to add: If you are having problems though the RETEU is the same and you'll still receive official OTA's in the future. Just try what I typed above and if all else fails follow the other posters guide to install rthe RETEU version.

Diesel779 said:
I wouldn't bother with the RETEU version if you're in the UK, the link I gave you is to the official RETGB factory image. As regards your problem try putting the msfastboot in your ADB folder and also extract your RETGB zip into the same folder, then open up a terminal in that folder and run the commands. Also, have you put your phone in fastboot and let Window automatically install the fastboot driver for your device?
Edit to add: If you are having problems though the RETEU is the same and you'll still receive official OTA's in the future. Just try what I typed above and if all else fails follow the other posters guide to install rthe RETEU version.
Click to expand...
Click to collapse
Got it. I actually almost couldn't find my ADB folder. Somehow I didn't have in C: and had it installed in my documents folder. dumb.
But yeah I managed to get it. This means I get all future OTAs right? and Even if I don't I could still use that method to update? And thanks so much guys. Really appreciate it, I thought I was never going to get Lollipop on this.

AllenLoyola23 said:
Got it. I actually almost couldn't find my ADB folder. Somehow I didn't have in C: and had it installed in my documents folder. dumb.
But yeah I managed to get it. This means I get all future OTAs right? and Even if I don't I could still use that method to update? And thanks so much guys. Really appreciate it, I thought I was never going to get Lollipop on this.
Click to expand...
Click to collapse
Yes, you will get all future OTA's. This is an official RETGB retail image. It's exactly what you would have got if you had received the OTA normally, but instead of upgrading you've done a fresh install.

Diesel779 said:
Yes, you will get all future OTA's. This is an official RETGB retail image. It's exactly what you would have got if you had received the OTA normally, but instead of upgrading you've done a fresh install.
Click to expand...
Click to collapse
Is there a way to flash 4.4.4 images again? i went straight to L when i got my phone and didn't get a chance to test it out on kitkat, but it fails to flash the partition or motoboot image as the current version is too high, do you know how to bypass the checks?

IINexusII said:
Is there a way to flash 4.4.4 images again? i went straight to L when i got my phone and didn't get a chance to test it out on kitkat, but it fails to flash the partition or motoboot image as the current version is too high, do you know how to bypass the checks?
Click to expand...
Click to collapse
don' t worry about this

Diesel779 said:
It's a factory image you can flash it over anything you currently have running. Open the Multi tool folder and you will see some called 'msfastboot' Make a new folder on your desktop and place that in there, then download the factory image I gave you the link for and extract it into the same folder you placed the msfastboot into. Then, whilst in that folder hold the shift key on your keyboard and then right click on your mouse and select 'open a command window here' Then put your phone in fastboot by turning it off and holding the power and volume down keys at the same time. Then, in the terminal you opened earlier type these commands one at a time:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin (REMOVES YOUR CUSTOM BOOTLOGO (Not neccessary))
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata (FACTORY RESETS YOUR FLASH MEMORY (Not neccessary))
mfastboot erase customize (REMOVES MOTOMAKER CUSTOMIZATIONS (Not neccessary))
mfastboot erase clogo (REM
mfastboot reboot
Click to expand...
Click to collapse
Thank you for your link.
Could I ask, If i flash this over my european moto x will it turn it into a GB version in settings and receive future OTA updates? I assume it should.
Likewise do I need to unlock my boot loader to flash this, or will putting into fast boot do.
Thanks for your advice in advance.

nookcoloruser said:
Thank you for your link.
Could I ask, If i flash this over my european moto x will it turn it into a GB version in settings and receive future OTA updates? I assume it should.
Likewise do I need to unlock my boot loader to flash this, or will putting into fast boot do.
Thanks for your advice in advance.
Click to expand...
Click to collapse
Yes and yes and no you don' t need to unlock. But why do this as the reteu model received the update before the retgb model, you can just sideload the ota if you didn't get it yet?

Related

[XT1063] downgrade to 21.11.17 4.4.4 then update to 22.21.28 5.0.2

Bootloader unlock required to avoid downgrade PIV Signature errors in fastboot.
Download firmware for XT1063 21.11.17 here
http://motofirmware.com/files/download/950-retuglb-xt1063-444-kxb2185-17-cid9-cfcxmlzip/
I flashed firmware using @Shawn5162's scrpt, but replaced the 21.11.23 files with the ones from the link above.
http://forum.xda-developers.com/showthread.php?t=2957167
or you can do it manually via fastboot:
adb reboot bootloader
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 modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot flash erase cache
Fastboot flash erase userdata
fastboot reboot
Then I applied all the following OTAs successfully:
Note: download and copy all OTAs to SD card downloads folder then install via STOCK Recovery apply update from SD Card
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-16-t2965161
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-25-t2978658
http://forum.xda-developers.com/showthread.php?p=58136321
Please hit the thanks if it worked and report back.
P.S.
Still unable to lock bootloader until 5.0 firmware released.
Android The Greek said:
First my bootloader is unlocked as I would always get PIV Signature errors in fastboot when downgrading.
Second, I have not be able to look the bootloader at all since I have been on Lollipop before.
Download firmware for XT1063 21.11.17 here
http://motofirmware.com/files/download/950-retuglb-xt1063-444-kxb2185-17-cid9-cfcxmlzip/
I then flashed firmware using Shawn152's scrpt, but replacing the 21.11.23 files with the ones from the link above.
or you can do it manually:
adb reboot bootloader
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 modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot flash erase cache
Fastboot flash erase userdata
fastboot reboot
Then I applied all the following OTAs successfully:
Note: download and copy all OTAs to SD card downloads folder then install via STOCK Recovery apply update from SD Card
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-16-t2965161
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-25-t2978658
Please hit the thanks if it worked and report back. This should help all those stuck on 22.11.6. Please make sure you go all the way back to 21.11.17 first before reporting back.
Click to expand...
Click to collapse
I presume that you MAY NOT have to flash whole rom, if you 'JUST' flashed the needed version of recovery then you can upgrade with a OTA zip (can't test as only got xt1068) maybe someone can test this - but obviously some OTA's rely on being updated in order.
This is for XT1063 Only!
Android The Greek said:
Bootloader unlock required to avoid downgrade PIV Signature errors in fastboot.
Download firmware for XT1063 21.11.17 here
http://motofirmware.com/files/download/950-retuglb-xt1063-444-kxb2185-17-cid9-cfcxmlzip/
I flashed firmware using @Shawn5162's scrpt, but replaced the 21.11.23 files with the ones from the link above.
http://forum.xda-developers.com/showthread.php?t=2957167
or you can do it manually via fastboot:
adb reboot bootloader
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 modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot flash erase cache
Fastboot flash erase userdata
fastboot reboot
Then I applied all the following OTAs successfully:
Note: download and copy all OTAs to SD card downloads folder then install via STOCK Recovery apply update from SD Card
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-16-t2965161
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-25-t2978658
Please hit the thanks if it worked and report back. This should help all those stuck on 22.11.6. Please make sure you go all the way back to 21.11.17 first before reporting back.
P.S.
Still unable to lock bootloader.
Click to expand...
Click to collapse
Bootloader can easily be locked. I've done it & even made a one click to do it as well. However I was able to update to 5.0 without the bootloader being locked. I'm back on KitKat for the third time. I'm not willing to give up root & deal with all the bugs of L.
There is also a custom ROM in these forms that run smoother than the stock & easier to install but still has the root bug.
kingmt01 said:
Bootloader can easily be locked. I've done it & even made a one click to do it as well. However I was able to update to 5.0 without the bootloader being locked. I'm back on KitKat for the third time. I'm not willing to give up root & deal with all the bugs of L.
There is also a custom ROM in these forms that run smoother than the stock & easier to install but still has the root bug.
Click to expand...
Click to collapse
What model do you have?
I can assure you I am not new at this, I bought my phone from Amazon with 21.11.23 and there was an addition added at some point that prevents a downgrade and in turn does not allow the system to be flashed with a locked or unlocked bootloader if you start with the command Fastboot oem lock begin.
if you have an XT1063 please tell me how you locked your bootloader without modifying anything that will then be unreversable.
Don't take it the wrong way, but I have seen people create tools that edit the hex to show bootloader locked then they can no longer unlock it or corrupt the phone and brick.
Android The Greek said:
What model do you have?
I can assure you I am not new at this, I bought my phone from Amazon with 21.11.23 and there was an addition added at some point that prevents a downgrade and in turn does not allow the system to be flashed with a locked or unlocked bootloader if you start with the command Fastboot oem lock begin.
if you have an XT1063 please tell me how you locked your bootloader without modifying anything that will then be unreversable.
Don't take it the wrong way, but I have seen people create tools that edit the hex to show bootloader locked then they can no longer unlock it or corrupt the phone and brick.
Click to expand...
Click to collapse
ETA: I'm not going to get upset over anything in a forum. I just post info to the best of my knowledge in hope to be helpful to someone else. Sometimes that changes as more knowledge is gained.
I have a xt1063 .17 & I did use "fastboot oem lock begin" I don't remember every command but the one click also restored the stock firmware at the same time. I'll have to look at my files in a few. I only made about 20 one clicks & was writing & rewriting a how to guide all at the same time as I was trying to figure it out & get on 5.0 all at the same time. Like I said tho my bootloader is unlocked again & it doesn't seem to affect the ability to flash OTA.
---------- Post added at 12:43 PM ---------- Previous post was at 11:55 AM ----------
OK. I used mfastboot to lock it.
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot oem lock
kingmt01 said:
ETA: I'm not going to get upset over anything in a forum. I just post info to the best of my knowledge in hope to be helpful to someone else. Sometimes that changes as more knowledge is gained.
I have a xt1063 .17 & I did use "fastboot oem lock begin" I don't remember every command but the one click also restored the stock firmware at the same time. I'll have to look at my files in a few. I only made about 20 one clicks & was writing & rewriting a how to guide all at the same time as I was trying to figure it out & get on 5.0 all at the same time. Like I said tho my bootloader is unlocked again & it doesn't seem to affect the ability to flash OTA.
---------- Post added at 12:43 PM ---------- Previous post was at 11:55 AM ----------
OK. I used mfastboot to lock it.
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot oem lock
Click to expand...
Click to collapse
I never said anything about needing to relock it. I just said I have not been able to for those of us that want 5.0.1 and want to lock the bootloader. If you are able to price steps on how you downgraded from 5.0 and locked the boot loader I sure would want to try it myself.
Ideally I would add in the commands above fastboot OEM lock begin and fastboot OEM unlock for those who want a relocked boot loader before flashing the otas. Its just not possible if you are not on 21.11.17 to begin with because of the signed zip downgrade verification
Android The Greek said:
I never said anything about needing to relock it. I just said I have not been able to for those of us that want 5.0.1 and want to lock the bootloader. If you are able to price steps on how you downgraded from 5.0 and locked the boot loader I sure would want to try it myself.
Ideally I would add in the commands above fastboot OEM lock begin and fastboot OEM unlock for those who want a relocked boot loader before flashing the otas. Its just not possible if you are not on 21.11.17 to begin with because of the signed zip downgrade verification
Click to expand...
Click to collapse
Stating that it didn't need locked to flash 5.0 is just added info for anyone fallowing the thread & based on my experience. That may change for flashing 5.0.1.
These commands was ran from a modified 21.11.17 build to lock the bootloader. I thought I read ether in this thread or another thread that you already found a way to flash back to the stock firmware 21.11.17 without the downgrade error. If your on stock 21.11.17 now then you could give the lock command a try from mfastboot. I restored a Nandroid to get back to KitKat from Lollipop.
The one click I made was for those that had tampered with their stock 21.11.17 & wanted to be back to stock & locked. I didn't even know there was a 21.11.23 build at the time.
kingmt01 said:
Stating that it didn't need locked to flash 5.0 is just added info for anyone fallowing the thread & based on my experience. That may change for flashing 5.0.1.
These commands was ran from a modified 21.11.17 build to lock the bootloader. I thought I read ether in this thread or another thread that you already found a way to flash back to the stock firmware 21.11.17 without the downgrade error. If your on stock 21.11.17 now then you could give the lock command a try from mfastboot. I restored a Nandroid to get back to KitKat from Lollipop.
The one click I made was for those that had tampered with their stock 21.11.17 & wanted to be back to stock & locked. I didn't even know there was a 21.11.23 build at the time.
Click to expand...
Click to collapse
Correct!
Android The Greek said:
Bootloader unlock required to avoid downgrade PIV Signature errors in fastboot.
Download firmware for XT1063 21.11.17 here
http://motofirmware.com/files/download/950-retuglb-xt1063-444-kxb2185-17-cid9-cfcxmlzip/
I flashed firmware using @Shawn5162's scrpt, but replaced the 21.11.23 files with the ones from the link above.
http://forum.xda-developers.com/showthread.php?t=2957167
or you can do it manually via fastboot:
adb reboot bootloader
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 modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot flash erase cache
Fastboot flash erase userdata
fastboot reboot
Then I applied all the following OTAs successfully:
Note: download and copy all OTAs to SD card downloads folder then install via STOCK Recovery apply update from SD Card
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-16-t2965161
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-25-t2978658
Please hit the thanks if it worked and report back. This should help all those stuck on 22.11.6. Please make sure you go all the way back to 21.11.17 first before reporting back.
P.S.
Still unable to lock bootloader.
Click to expand...
Click to collapse
Worked like a charm! Thank you so much, Updated my moto g 2014 xt1063 21.11.23 KitKat 4.4.4 Amazon unocked global using this method. :good:
Thank you for reporting in appreciate it
help
hello,i am somewhat new to these things but surely i can do it with detailed steps(thanks for those)
so here is the thing,i bought Moto G2 from amazon last month and my mobile has these details
System Version:-
21.11.23.titan_retuglb.retuglb.en.US retus
Build Number- KXB21.85-23
i am bored with KitKat ..
a few ques:-
After this tricky update will i be eligible for future updates too?
Can i root after the Lolipop update?
WIl this method format my mobile?
Thanks.
(sry for newbie type ques )
kkriop said:
hello,i am somewhat new to these things but surely i can do it with detailed steps(thanks for those)
so here is the thing,i bought Moto G2 from amazon last month and my mobile has these details
System Version:-
21.11.23.titan_retuglb.retuglb.en.US retus
Build Number- KXB21.85-23
i am bored with KitKat ..
a few ques:-
After this tricky update will i be eligible for future updates too?
Can i root after the Lolipop update?
WIl this method format my mobile?
Thanks.
(sry for newbie type ques )
Click to expand...
Click to collapse
You will get updates. You can Root, however I do not think there is a stable root yet. If you unlock your boot loader it will format, if you already unlocked your boot loader then you will not loose your data.
Android The Greek said:
You will get updates. You can Root, however I do not think there is a stable root yet. If you unlock your boot loader it will format, if you already unlocked your boot loader then you will not loose your data.
Click to expand...
Click to collapse
Its fine w/o root..as far as i am getiing lollipop experience.. My bootloader is unlcoked..will do the thing and post ..thanks again
kkriop said:
Its fine w/o root..as far as i am getiing lollipop experience.. My bootloader is unlcoked..will do the thing and post ..thanks again
Click to expand...
Click to collapse
No problem
Android The Greek said:
No problem
Click to expand...
Click to collapse
downgrade complete now the issue is when i check System Updates it doesnt pick up Lollipop update
and these manual update links doesnt open is there any mirror link?? :crying:
Do you mean you cannot download from mega?
Which one you need I'll put it in my Dropbox and pm you
Android The Greek said:
Do you mean you cannot download from mega?
Which one you need I'll put it in my Dropbox and pm you
Click to expand...
Click to collapse
The two from mega (first two) third one is already on dropbox so not a prob for that..
Thank u very much
so is safe to install ota updates with bootloader unlocked?
CrazyGenio said:
so is safe to install ota updates with bootloader unlocked?
Click to expand...
Click to collapse
Yes an unlocked boot loader has no effect on anything except the abity to flash a custom recovery. If your unlocked and have it all stock, then you should be good

[GUIDE] [XT1022] Restore Stock 4.4.4 firmware

Many users are not able to manually update their XT1022 to 5.0.2 as they are not having stock firmware on their phones. That's why while updating they are encountering these errors and they are fed up !
The common errors being faced are :
Status 7 error while installation/unexpected contents error/System says a new update is ready to be installed and when you press "I am in", the phone reboots and while installation you see a dead android "android with a red error mark" and then the phone reboots to 4.4.4 and says that the last update was unsuccessful !
To avoid these errors, you need to be on stock firmware before updating manually.
Please note that if you are flashing pure untouched ROM/pure optimised ROM, then it doesn't mean you are flashing STOCK FIRMWARE ! FIRMWARE means a lot more. And you can't flash firmware through recovery !
Many people are flashing pure XT1022 ROM and then they are saying that "I have flashed Stock firmware but then also I am getting UNEXPECTED CONTENTS ERROR WHILE UPDATING" !
If you want to flash stock firmware, follow these steps :
Download and install Moto E drivers on your pc. Link : https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/99012/p/30,6720,9146
Download mfastboot files and extract the files in a folder. Link : https://drive.google.com/folderview?id=0B05Crz57q4zgZE1aVW5FT1RsUUU&usp=sharing
Download Stock firmware for XT1022 and extract the files to the same folder. Link : https://drive.google.com/file/d/0B05Crz57q4zgY2lWUE9KZjlGeVU/view?usp=sharing
Now, reboot your phone into bootloader by pressing volume down + power for a few seconds. You will see the bootloader screen.
Go to the folder where you have extracted Stock Firmware and mfastboot files and open command prompt there (Press shift + right mouse button and click on open command prompt)
Now, its the time to enter commands. Execute these lines of command one by one checking that each command you executed returned ok !
commands :
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
If every command you entered was successfully executed, your phone will reboot into stock firmware !
Now, you can upgrade to 5.0.2 manually
Hit thanks, if helped
prince.d.emperor said:
Many users are not able to manually update their XT1022 to 5.0.2 as they are not having stock firmware on their phones. That's why while updating they are encountering these errors and they are fed up !
The common errors being faced are :
Status 7 error while installation/unexpected contents error/System says a new update is ready to be installed and when you press "I am in", the phone reboots and while installation you see a dead android "android with a red error mark" and then the phone reboots to 4.4.4 and says that the last update was unsuccessful !
To avoid these errors, you need to be on stock firmware before updating manually.
Please note that if you are flashing pure untouched ROM/pure optimised ROM, then it doesn't mean you are flashing STOCK FIRMWARE ! FIRMWARE means a lot more. And you can't flash firmware through recovery !
Many people are flashing pure XT1022 ROM and then they are saying that "I have flashed Stock firmware but then also I am getting UNEXPECTED CONTENTS ERROR WHILE UPDATING" !
If you want to flash stock firmware, follow these steps :
Download and install Moto E drivers on your pc. Link : https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/99012/p/30,6720,9146
Download mfastboot files and extract the files in a folder. Link : http://dl-1.va.us.xda-developers.com/2/4/2/7/6/6/7/mfastboot-v2.zip?key=gTbaSY_MHMqZMNf7yehIpg&ts=1423902465
Download Stock firmware for XT1022 and extract the files to the same folder. Link : https://mega.co.nz/#!SUZA3AbR!P_qdV24-ZpqSwKhCPjifBcd7en7Y7AkBZpRApb2loHs
Now, reboot your phone into bootloader by pressing volume down + power for a few seconds. You will see the bootloader screen.
Go to the folder where you have extracted Stock Firmware and mfastboot files and open command prompt there (Press shift + right mouse button and click on open command prompt)
Now, its the time to enter commands. Execute these lines of command one by one checking that each command you executed returned ok !
commands :
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
If every command you entered was successfully executed, your phone will reboot into stock firmware !
Now, you can upgrade to 5.0.2 manually
Hit thanks, if helped
Click to expand...
Click to collapse
Both mfastboot and stock firmware links are not working..
Pls update it with new links...
And also I need the stock recovery...
I think the problem lies in the recovery..
I will upload it on Google drive by evening !
And recovery file is there in Stock firmware.
Sent from my XT1022 using XDA Free mobile app
salman.student said:
Both mfastboot and stock firmware links are not working..
Pls update it with new links...
And also I need the stock recovery...
I think the problem lies in the recovery..
Click to expand...
Click to collapse
Link updated !
Do check :good:
prince.d.emperor said:
Link updated !
Do check :good:
Click to expand...
Click to collapse
Thank u very much
version downgraded for partition error ..
YES!!!!!!!!!!!!!!!!!!!!!
salman.student said:
Both mfastboot and stock firmware links are not working..
Pls update it with new links...
And also I need the stock recovery...
I think the problem lies in the recovery..
Click to expand...
Click to collapse
yES! yES! YES! AFTER TRYING 11 TIMES AND INVESTING A 13 HOURS I FINALLY ABLE TO UPDATE AFTER I FLASH THE STOCK RECOVERY IMG FROM THIS THREAD- http://forum.xda-developers.com/moto-e/general/stock-recovery-recovery-img-t3031437
NOTE I HAVE MOTO E XT1022,UNROOTED AND BL LOCKED. I FLASHED 4.4.4 WITH THE HELP OF THIS THREAD PREVIOUSLY!
ALTAST I GOT LOLLIPOP
Worked like a charm. Thanks.

Stock 6.0/Marshmallow firmware for Latin America (RETLA) XT1072 (fast download)

https://drive.google.com/file/d/0B9JdPPX_cXeAODFEeVlGMkpsREU/view?usp=docslist_api (685mb)
how i can install this?
hitsegam said:
how i can install this?
Click to expand...
Click to collapse
Mfastboot or "apply update from sdcard" there's many guides on the forums
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
I made a zip whit minimal fastboot + mfastboot v2 and a bat file, extract the rom files in the same folder as fastboot and bat file, run the bat as admin
Fastboot+mfastbootv2
BAT File
dr.nic said:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
I made a zip whit minimal fastboot + mfastboot v2 and a bat file, extract the rom files in the same folder as fastboot and bat file, run the bat as admin
Fastboot+mfastbootv2
BAT File
Click to expand...
Click to collapse
Great stuff. Thankyou
my phone still stuck in the motorola animation 10 min and more
T.T
hitsegam said:
my phone still stuck in the motorola animation 10 min and more
T.T
Click to expand...
Click to collapse
Same here
LuuchoRocha said:
Same here
Click to expand...
Click to collapse
First boot takes a long time. 25mins for most people
Unified firmware thread request
I appreciate a lot your efforts. This will help a load of people who bricked their devices, want to factory reset or just reflash or update to 6.X. However, you should take down all your pages and instead upload all the firmwares in an unified thread, so you won't need to search separately.
benjausen said:
I appreciate a lot your efforts. This will help a load of people who bricked their devices, want to factory reset or just reflash or update to 6.X. However, you should take down all your pages and instead upload all the firmwares in an unified thread, so you won't need to search separately.
Click to expand...
Click to collapse
I did them separately so they would be easier to find, rather than clicking a thread and searching through pages
Sent from my thea using XDA Labs
Hemphiz said:
I did them separately so they would be easier to find, rather than clicking a thread and searching through pages
Sent from my thea using XDA Labs
Click to expand...
Click to collapse
You can actually put a list of all firmwares and an explanation in the first post. So please do that.
benjausen said:
You can actually put a list of all firmwares and an explanation in the first post. So please do that.
Click to expand...
Click to collapse
No. I wont be doing that.
Can I install it with TWRP? or is there a way to convert this to a flasheable zip?
SirGustav said:
Can I install it with TWRP? or is there a way to convert this to a flasheable zip?
Click to expand...
Click to collapse
Not unless someone on the forums has. I'm not sure. If not. It's relatively quite easy to flash. Not as hard as it seems
SirGustav said:
Can I install it with TWRP? or is there a way to convert this to a flasheable zip?
Click to expand...
Click to collapse
Hi dude! Of course there is a way to make a flashable zip from this.
Here is :angel:
LuuchoRocha said:
Hi dude! Of course there is a way to make a flashable zip from this.
Here is :angel:
Click to expand...
Click to collapse
Is that not for things like flashing custom recoveries? I assumed you had to use kitchen tools to make a stock rom flashable zip... Though times do change
Hemphiz said:
Is that not for things like flashing custom recoveries? I assumed you had to use kitchen tools to make a stock rom flashable zip... Though times do change
Click to expand...
Click to collapse
Well the easiest way is with a kitchen but you can do it without one.
I think in edify we have some functions to flash images

New update (MPJ24.139-63) released on September 9, 2016 for moto G4 plus.

I have found that the new update is not a newer Android version but a security patch according to identifications made in July 2016.
Total size of update is 508.4 MB.
Some people have reported problems with notification sounds.
Do we have any more news about this update.?
Please upload stock rom for indian variant moto g4plus xt1643
i have installed a stock rom and it was US but now my phone is unable to connect to any wifi or mobile network plz upload anywhere else than filefactory
I have installed the update and everything is working fine for me.
help
jack_04 said:
I have installed the update and everything is working fine for me.
Click to expand...
Click to collapse
can u backup ur rom nd upload
navi74644 said:
can u backup ur rom nd upload
Click to expand...
Click to collapse
My phone is not rooted. So I guess I can not take ROM backup.
no need to be rooted
jack_04 said:
My phone is not rooted. So I guess I can not take ROM backup.
Click to expand...
Click to collapse
just put it in fastboot mode and pull the rom
navi74644 said:
just put it in fastboot mode and pull the rom
Click to expand...
Click to collapse
Can You Tell Me How To pull the rom In fastboot mode?
I hv installed updates..
There is a problem after that..
Sim 1 is automatically Off after sm time..
How is your phone working now?
jack_04 said:
I have installed the update and everything is working fine for me.
Click to expand...
Click to collapse
Motorola claims that they have solved all the reported issues except heating because of its board.
Many people have found that notification volume is decreased to 30%.
Could you share detailed information about what is included in update?
Have you reported this with Motorola?
Milan Samani said:
I hv installed updates..
There is a problem after that..
Sim 1 is automatically Off after sm time..
Click to expand...
Click to collapse
If you are using unrooted phone the I would suggest you to report this with Motorola. Let us know how do they respond and if they are willing to offer any quick solution to this issue.
first thing first: I have rooted using systemless root method. so if I update to this latest patch will I have to root it again? and will it be a complete factory reset or I can expect my apps persisting after update?
Sent from my Moto G (4) using Tapatalk
is there any way to update my unlocked bootloader phone ? I tried everything.. Flashed stock recovery... Unroot my phone.. Flash fire etc. nothing works.. Any suggestion will be appriciate.
navi74644 said:
i have installed a stock rom and it was US but now my phone is unable to connect to any wifi or mobile network plz upload anywhere else than filefactory
Click to expand...
Click to collapse
Same thing happened to me ! What I did is I just gave my mobile to service centre they flashed original firmware( don't forget to remove warning image )
I got this update and after updating, I am facing low notification sound.
Sent from my Moto G (4) using Tapatalk
By my ear notification sound is about 60% what it was before (this is sitting two devices next to each other and comparing the updated device at max volume with the non-updated device, when the nud's volume bar was at ~60℅ they sounded equal). Incidentally 100℅ on the non-updated device was probably a bit too loud.
I've contacted Moto and requested they acknowledge the issue and provide a timeframe for a solution; I have threatened to return both devices to my supplier. I'll share the reply.
The US unlocked XT1644 didnt get any updates. Anybody expecting android 7.0 before the holidays is going to be disappointed.
Pranav Kumar said:
Same thing happened to me ! What I did is I just gave my mobile to service centre they flashed original firmware( don't forget to remove warning image )
Click to expand...
Click to collapse
how to remove warning nd here did get it flashed again i mean which service centre
navi74644 said:
how to remove warning nd here did get it flashed again i mean which service centre
Click to expand...
Click to collapse
relock the bootloader and flash the stock rom again.
steps:
Flashing Stock Firmware:
1) Download firmware for XT1643 from https://drive.google.com/file/d/0B1N...tsRU1RTVk/view
2) Download mfastboot from https://drive.google.com/file/d/0B5j...ew?usp=sharing
3) Extract the firmware into the folder containing mfastboot.
4) Reboot the phone into Bootloader (power off, then press the power and volume down buttons simultaneously).
5) Execute these commands and make sure you receive an 'OKAY' after each command.
Code: just type first mfastboot oem lock,then enter this commands
mfastboot oem lock
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem lock
mfastboot reboot
anhoxhrs said:
relock the bootloader and flash the stock rom again.
steps:
Flashing Stock Firmware:
1) Download firmware for XT1643 from https://drive.google.com/file/d/0B1N...tsRU1RTVk/view
2) Download mfastboot from https://drive.google.com/file/d/0B5j...ew?usp=sharing
3) Extract the firmware into the folder containing mfastboot.
4) Reboot the phone into Bootloader (power off, then press the power and volume down buttons simultaneously).
5) Execute these commands and make sure you receive an 'OKAY' after each command.
Code: just type first mfastboot oem lock,then enter this commands
mfastboot oem lock
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem lock
mfastboot reboot
Click to expand...
Click to collapse
brother the given link doest not exist plz update ur drive download link it will be highly thankful to u
navi74644 said:
brother the given link doest not exist plz update ur drive download link it will be highly thankful to u
Click to expand...
Click to collapse
Lol this guy who mentioned the stepd just did a copy paste.the url he provided is incomplete.the complete url is - https://drive.google.com/file/d/0B1N6dGU7FEXsSjR3QUtsRU1RTVk/view

Moto g6 plus on startup bootloop

Hi, I have looked for this problem, but cannot find any answers. I tried to flash a copy of the official rom on my phone, The bootloader is unlocked but not rooted. It seemed to go well, but now is on a permante startup loop.
I can get into fastboot and recovery, is there any way I can recover from this?
in fastboot it says baseband not found.
Any help will be really appreciated
First I need to know which firmware exactly do you flashed on your device?
Baseband not found is normal...
WoKoschekk said:
First I need to know which firmware exactly do you flashed on your device?
Baseband not found is normal...
Click to expand...
Click to collapse
I'm not sure, can you tell me how to find it,
Sorry for being so stupid
Barb28n said:
I'm not sure, can you tell me how to find it,
Sorry for being so stupid
Click to expand...
Click to collapse
Ok... I guess you flashed the wrong firmware. But that's no problem. Just answer the questions below and you'll get a link to the correct firmware. Once you flash it your device will be fine again.
do you have a moto g6 plus?
where are you from? there are different firmwares
e.g. for Europe, India, etc.
It is the moto g6 plus, international version,
WoKoschekk said:
Ok... I guess you flashed the wrong firmware. But that's no problem. Just answer the questions below and you'll get a link to the correct firmware. Once you flash it your device will be fine again.
do you have a moto g6 plus?
where are you from? there are different firmwares
e.g. for Europe, India, etc.
Click to expand...
Click to collapse
It is the moto g6 plus, international version, bought from Amazon, Just wondering if I had the right firmware, and put it on the sd card,could I flash it from there? the bootloader is unlocked, but not rooted.
Thanks for any help
Barb28n said:
It is the moto g6 plus, international version, bought from Amazon, Just wondering if I had the right firmware, and put it on the sd card,could I flash it from there? the bootloader is unlocked, but not rooted.
Thanks for any help
Click to expand...
Click to collapse
No, you have to flash it via fastboot. However you can also try the Lenovo moto flash tool that does it for you
Barb28n said:
Hi, I have looked for this problem, but cannot find any answers. I tried to flash a copy of the official rom on my phone, The bootloader is unlocked but not rooted. It seemed to go well, but now is on a permante startup loop.
I can get into fastboot and recovery, is there any way I can recover from this?
in fastboot it says baseband not found.
Any help will be really appreciated
Click to expand...
Click to collapse
What exactly have you done...? Do you know how to flash a new firmware or not??
---------- Post added at 05:53 AM ---------- Previous post was at 05:19 AM ----------
A little guide to get the correct firmware for your device:
1. go to fastboot mode
2. type the following command
Code:
fastboot getvar ro.carrier
the output will be:
Code:
ro.carrier: [I]your software channel[/I]
3. follow this link:
https://mirrors.lolinet.com/firmware/moto/evert/official/
and choose "your software channel"
(e.g. reteu / retail / retin, etc.)
4. download the latest firmware
***********************************************
How to flash a new firmware
https://forum.xda-developers.com/g6-plus/how-to/firmware-moto-g6-g6plus-t3789274
But do not use the firmware from this page!!
!!Only use the firmware you downloaded in step 4. !!
juampapo546 said:
No, you have to flash it via fastboot. However you can also try the Lenovo moto flash tool that does it for you
Click to expand...
Click to collapse
Can you explain how to do that please, I think I tried the moto flash tool,and it couldn't find my phone.
Barb28n said:
Can you explain how to do that please, I think I tried the moto flash tool,and it couldn't find my phone.
Click to expand...
Click to collapse
https://forum.xda-developers.com/g6-plus/how-to/firmware-moto-g6-g6plus-t3789274
WoKoschekk said:
https://forum.xda-developers.com/g6-plus/how-to/firmware-moto-g6-g6plus-t3789274
Click to expand...
Click to collapse
Thanks, I will try it, I have done it before,but not for a while. Trying to keep this a se
cret from Hubby as he will go ballistic!! LOL
WoKoschekk said:
https://forum.xda-developers.com/g6-plus/how-to/firmware-moto-g6-g6plus-t3789274
Click to expand...
Click to collapse
Thank you, thankyou, it worked, now I have to try and get rid of the warning message about the bootloader being unlocked, You are an absolute star !!!
Barb28n said:
Thank you, thankyou, it worked, now I have to try and get rid of the warning message about the bootloader being unlocked, You are an absolute star !!!
Click to expand...
Click to collapse
Download and extract the logo.zip attachment. It contains a logo.bin file. Copy logo.bin to /sdcard (internal storage), open terminal app and type:
Code:
su
dd if=/sdcard/logo.bin of=/dev/block/by-name/logo`getprop ro.boot.slot_suffix`
Reboot and enjoy your new logo!
On the top left corner you'll see the 'Verity mode is set to disabled' message which is quiet normal.
I am having the same exact problem as the OP (except I haven't done anything to my phone lately, it just ran out of battery, shut down, and went into endless bootloop after I charged it up).
I tried following the above instructions (my software channel is RETLA) and found two "latest" versions as of this posting (and both zip files were found identical by the diff command, as were their contents after I unzipped them)-- XT1926-6_EVERT_RETLA_SS_9.0_PPWS29.116-11-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and XT1926-7_EVERT_RETLA_DS_9.0_PPWS29.116-11-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I tried flashing the XT1926-7 one and my phone is still in a boot loop. Since the other file is identical, I'm not expecting it to work either. So, which version of these firmwares is the correct one to use?
I thought that the point was that all these would work with a G6plus in the RETLA channel and some were just newer than others.
Thanks.
---------- Post added at 07:00 AM ---------- Previous post was at 06:07 AM ----------
I tried an earlier one, XT1926-7_EVERT_RETLA_DS_9.0_PPWS29.116-11-8_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and got...
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Click to expand...
Click to collapse
I went back to the earliest available 9.0 firmware, XT1926-7_EVERT_RETLA_9.0_PPW29.116-11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, flashed that, and still the above message.
Can anybody help?
Thanks.
---------- Post added at 07:03 AM ---------- Previous post was at 07:00 AM ----------
I do have TWRP installed on my SD card. Can that be used to unbrick the phone?
---------- Post added at 07:20 AM ---------- Previous post was at 07:03 AM ----------
...and wiping the cache from TWRP didn't fix it either -- still the same message about data being corrupt. Now I'm truly out of ideas.
Boot into fastboot mode to see which FW is the correct one for you.
Barb28n said:
Hi, I have looked for this problem, but cannot find any answers. I tried to flash a copy of the official rom on my phone, The bootloader is unlocked but not rooted. It seemed to go well, but now is on a permante startup loop.
I can get into fastboot and recovery, is there any way I can recover from this?
in fastboot it says baseband not found.
Any help will be really appreciated
Click to expand...
Click to collapse
Well, i read this post and answers till the end, as it describes very well my problem, but no such solution, so if someone could help would be great !
The device is Moto G6 plus XT1926-8 and i still have all acess to fastboot, and recovery by pressing keys, i've already flashed this roms:
XT1926-8_EVERT_RETBR_9.0_PPWS29.116-16-18_subsidy-DEFAULT_regulatory-DEFAULT_CFC
XT1926-8_EVERT_RETBR_9.0_PPWS29.116-16-15_subsidy-DEFAULT_regulatory-DEFAULT_CFC
stockrom.net_XT1926-8_EVERT_RETBR_9.0_PPWS29.116-16-11_subsidy-DEFAULT_regulatory-DEFAULT_CFC
in this order, but always got an infinite bootloop that sometime comes to inicial screens where you can click "start" set wifi, etc, but the device always restart no matter i click into it, or wait till a suposed "end" of restart rotine, that never came, always come to a restart showing my unlocked bootloader screen etc etc. I could suggest now try flashing a android 8 version rom, but for my experience, i have fear (not knowledge) that could something go wrong with radios and i finish not getting signal, so i came here looking for some help, if anyone knows something please help ! i will monitor this page so i can get any answer ! Thanks in advance !
ASPViTo said:
if anyone knows something please help ! i will monitor this page so i can get any answer ! Thanks in advance !
Click to expand...
Click to collapse
I've got some questions:
- did you flash Magisk or other tools like a "disable-dm_verity.zip"?
- userdata erased?
- correct boot slot?
Boot into recovery and try to "wipe (user)data". Maybe this will fix the bootloop.
Barb28n said:
Hi, I have looked for this problem, but cannot find any answers. I tried to flash a copy of the official rom on my phone, The bootloader is unlocked but not rooted. It seemed to go well, but now is on a permante startup loop.
I can get into fastboot and recovery, is there any way I can recover from this?
in fastboot it says baseband not found.
Any help will be really appreciated
Click to expand...
Click to collapse
WoKoschekk said:
I've got some questions:
- did you flash Magisk or other tools like a "disable-dm_verity.zip"?
- userdata erased?
- correct boot slot?
Boot into recovery and try to "wipe (user)data". Maybe this will fix the bootloop.
Click to expand...
Click to collapse
Hi bro, and thanks for the attention !
Answers: No, never used magisk. No other tools for root, if is this your question ! Only tool i have used is "Moto Auto Flash Tool v8.2 By Jamesjerss" that i used to unlock bootloader. All other flash process was done was using that list of commands everyone knows:
mfastboot getvar max-sparse-size
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot flash oem_b oem_other.img
mfastboot flash vendor vendor.img_sparsechunk.0
mfastboot flash vendor vendor.img_sparsechunk.1
mfastboot flash vendor vendor.img_sparsechunk.3
mfastboot flash vendor vendor.img_sparsechunk.4
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase DDR
mfastboot oem fb_mode_clear
mfastboot reboot
About that command "mfastboot erase userdata" you mention,
I found that this command is always used in the list above "user data erased" was used on all tryes of flashsing!
- correct boot slot?
I dont know what you mean about, maybe something like "fix" boot slot, if so, no, i dont know how to do it, if you can provide a link for me to read about, i thank you, if there was a chance of the device stop this infinites restarts.
Boot into recovery and wipe all data, i did every flash attempt, that had fail, as way to recover the device, no sucess so far, phone stills rebooting to unlocked bootloader screen that goes to motorola logo, that goes to briefly entrance of welcome screen, or nor this, restart reboot again, i observed that after various tries it hangs alone and stills a black screen, that only goes out if i long press power button looking a forced shut off, but it doenst stays turned of, this restart process, restart again. Any clues or ideas ?
ASPViTo said:
mfastboot flash vendor vendor.img_sparsechunk.0
mfastboot flash vendor vendor.img_sparsechunk.1
mfastboot flash vendor vendor.img_sparsechunk.3
mfastboot flash vendor vendor.img_sparsechunk.4
Click to expand...
Click to collapse
Did you use exactly the same commands? Apart from the fact that you should count 0,1,2,3 and 4 your firmware has only two vendor.img sparse files.
WoKoschekk said:
Did you use exactly the same commands? Apart from the fact that you count 0,1,2,3 and 4 your firmware has only two vendor.img sparse files.
Click to expand...
Click to collapse
mfastboot getvar max-sparse-size
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot flash system system.img_sparsechunk.12
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot flash oem_b oem_other.img
mfastboot flash vendor vendor.img_sparsechunk.0
mfastboot flash vendor vendor.img_sparsechunk.1
mfastboot flash vendor vendor.img_sparsechunk.3
mfastboot flash vendor vendor.img_sparsechunk.4
mfastboot flash vendor vendor.img_sparsechunk.5
mfastboot flash vendor vendor.img_sparsechunk.6
mfastboot flash vendor vendor.img_sparsechunk.7
mfastboot flash vendor vendor.img_sparsechunk.8
mfastboot flash vendor vendor.img_sparsechunk.9
mfastboot flash vendor vendor.img_sparsechunk.10
mfastboot flash vendor vendor.img_sparsechunk.11
mfastboot flash vendor vendor.img_sparsechunk.12
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase DDR
mfastboot oem fb_mode_clear
mfastboot reboot
used this one, something that can improved ?
ASPViTo said:
used this one, something that can improved ?
Click to expand...
Click to collapse
yes, don't use it!
Where did you get the firmware from?
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
Every single command applies to the corresponding file within the firmware.zip. The first command list you posted is the correct one but those two lines vendor.img...3+4 are useless because the files don't exist and cannot be flashed. Delete them and try again.

Categories

Resources