DISCLAIMER:
What you do with Your Device is Your Responsibility!
I am not responsible for anything that happens to your device.
I'll try to help you solve the problem, if I can!
I wanted to change my XT1033 into GPe, and well procedure isn't that hard, but it required installing two firmwares one over the other that is
GB first and then selective flashing of GPe. And as i frequently change between GPE, GB, AsiaRetail. I made custom scripts for each one of them. I also Mixed the firmware of GPe and GB to make one single firmware which can be directly flashed over XT1033 using one single bat to convert GPe.
I am lending the major part of work from @ffosilva who in turn gives credit to @oldblue910 on thread
[FASTBOOT] Google Play Edition images (semi-official)
I know similar threads already exist, I am starting a new one with the aim of keeping the thread Noob-Friendly, And provide a single download to convert into GPe. I am also adding the package to change the Unlocked bootloader logo to GPe version. and providing a bat script to make it easier for newbies!Downloads
You can download the Mixed-Firmware From:
1.Here (GDrive)
2.Here (progammingnerds.com) by @tanmay190
Mirrors Needed!
Pre-Requisite: Installed Motorola Drivers.
Instructions:
Download the Package and Extract it to a folder
Reboot the phone into Bootloader (Power+VolumeDown).
Double Click XT1033_to_GPe.bat to begin
OR
Run Following commands from the Command Prompt after cd-ing to the folder, one by one
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash fsg fsg_intl.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot erase cache
mfastboot erase userdata
Reboot into system to be booted into GPe version.
And there you have it the XT1033 converted to Moto G GPe.
Quick Useful Links/Tips:
CWM for GPe
Philz Recovery for GPe
Command to flash a recovery "fastboot flash recovery filename.img" (without quotes) where filename.img is the filename (It has to be in the same folder) of the recovery image that you are flashing. To go back to stock recovery you can find the recovery.img from the download package above and flash using the same command!
If you use CWM/Philz, when you exit the recovery while phone is unrooted, It will ask you that your phone is not rooted, Install su? You c5. an select yes to root your phone. and later install SuperSU from Play Store.
SuperSU flashable zip if you Think flashing SuperSU directly is better! I find the above method a lot faster!
If anything goes wrong, Use This Guide to Get Back to Stock
[Stock][Firmware Package][XT1033] Asia Retail - Alt. Link [4.4.2][Lock Bootloader]
Any Mirrors to Download Links are welcome.
Hit Thanks if it helps!
Thanks. What is the purpose of fsg partition?
Sent from my XT1033 using Tapatalk
Dual SIM?
Sent from my Moto G using XDA Free mobile app
I dont know, do you know if it is related to dualsim? Lets say we converted a xt1033 into gpe with this and get one sim working. Can we flash stock based xt1032 custom roms on this gpe rom ? Gpe roms use ext4 filesystem whereas motorola roms use f2fs.
Lets say I want to keep f2fs file system and get one sim working with stock based xt1032 custom roms. What should i do ?
Sent from my XT1033 using Tapatalk
Convert it to GB
Semseddin said:
I dont know, do you know if it is related to dualsim? Lets say we converted a xt1033 into gpe with this and get one sim working. Can we flash stock based xt1032 custom roms on this gpe rom ? Gpe roms use ext4 filesystem whereas motorola roms use f2fs.
Lets say I want to keep f2fs file system and get one sim working with stock based xt1032 custom roms. What should i do ?
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Flash a full GB firmware, you will get a single sim working! and you will also have a f2fs!
I could install this rom but recovery does not recognize the sd card.
I can't install any thing.
How can I fix this problem?
i don't know if it's just my mobile , but when i use single sim rom ( i mean xt1032/gpe rom ) audio in real racing 3 and nfs most wanted gets laggy , and sometimes audio repeat itself for every 3-4 seconds . gameloft games are fine tho . i tried replacing xt1032's "audio.primary.msm8226.so"
file with xt1032's "audio.primary.msm8226.so" but i lost sound completely .
Well
mobilephone01 said:
I could install this rom but recovery does not recognize the sd card.
I can't install any thing.
How can I fix this problem?
Click to expand...
Click to collapse
flash latest philz recovery or flash gpe specific recovery,anyway you'll get encryption error on custom roms
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon_gpe
rr46000 said:
flash latest philz recovery or flash gpe specific recovery,anyway you'll get encryption error on custom roms
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon_gpe
Click to expand...
Click to collapse
I'm using latest philz recover.
If the same thing happen when I install the custom rom. I'll wait till you fix this problem.
Thank you.
Changed the method, Foolproof this time!
mobilephone01 said:
I'm using latest philz recover.
If the same thing happen when I install the custom rom. I'll wait till you fix this problem.
Thank you.
Click to expand...
Click to collapse
Changed the method, Foolproof this time!
Sorry had to change the files in downloads as well!
I found another thread with a similar concept but a better implementation, I am borrowing the files from them and just adding a couple things!
But it should work now!
And again, I already did this here.
thelegendofzeth said:
And again, I already did this here.
Click to expand...
Click to collapse
And again two people said they didnt understand!
I wrote in description the aim is to make it noob friendly!
And its not like your original work! I'd probably take that comment from @ffosilva
mfastboot.exe crash and can't install. Please fix it.
mobilephone01 said:
mfastboot.exe crash and can't install. Please fix it.
Click to expand...
Click to collapse
Right on it!
EDIT: Crash fixed, it was a command issued when bootloader was offline, ideally it should've waited, but i dont know whats wrong. I paused the script for a while It is working fine now!
Download the mfastboot+logo_bin.zip again!
mfastboot does not crash but still does not work.
Maybe not install all GPe file? Finishes very quick and still remain previous rom.
Do I have to download GPe file?
mobilephone01 said:
mfastboot does not crash but still does not work.
Maybe not install all GPe file? Finishes very quick and still remain previous rom.
Do I have to download GPe file?
Click to expand...
Click to collapse
You have to download two files! 1. Mixed-Firmware 2.mfastboot+logo_bin.zip
deej_roamer said:
You have to download two files! 1. Mixed-Firmware 2.mfastboot+logo_bin.zip
Click to expand...
Click to collapse
You changed the both files?
mobilephone01 said:
You changed the both files?
Click to expand...
Click to collapse
The first file was fine! There was no fault with the firmware. It was a scripting problem on my side, I've changed only the script
deej_roamer said:
Right on it!
EDIT: Crash fixed, it was a command issued when bootloader was offline, ideally it should've waited, but i dont know whats wrong. I paused the script for a while It is working fine now!
Download the mfastboot+logo_bin.zip again!
Click to expand...
Click to collapse
On some systems mfastboot crashes after the reboot command The best work around is to add "mfastboot continue" after the reboot command in the bat script
deej_roamer said:
The first file was fine! There was no fault with the firmware. It was a scripting problem on my side, I've changed only the script
Click to expand...
Click to collapse
I could not install. It was finished 1 second for install after click XT1033_to_GPe.bat. Is it normal?
Booting previous rom. Nothing changed.
Related
If you Softbricked your phone and are stucked at the Google Unlocked Logo you're right here... the major point of this is to unbrick the phone and not to set it in derivation condition and btw.... unbrick flashing etc at your own risk
Download:
https://drive.google.com/file/d/0B6IdzeLKSZoGX1NzZTlmNVdKeWM/edit?usp=sharing
THIS IS THE GERMAN STOCK ROM MOTOROLA XT1032! IT'S REPORTED THAT THERE COULD BE NO GSM SIGNAL & WIFI!!!!
Hey Guys,
i dont know if this is posted somehere here at the MotoG XDA section....
I tried the MotoG GPe Rom and received an OTA Update to Android 4.4.4 and installed it. After reverting to Motorola stock rom or GPe 4.4.2 the phone stucks in the boot logo and won't boot up anymore.
So here's is MY fix for the problem and i hope i can help some... it's a temporal fix right now to unbrick the half-bricked MotoG for further development
1. Restart Phone in Bootloader
Power + Volume down to enter the bootloader mode and flash the GPe Recovery as *.img file from Philz with fastboot command
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
2. Enter the Recovery Mode
Enter the recovery mode with selecting "Recovery" and hit the volume up to enter it.
In recovery mode you will get some error messages like in the attached phote below. To fix these messages:
Mounts and Storage --> hit "format /cache" and "format /data and /data/media (/sdcard)"
Click to expand...
Click to collapse
3. Push CWM Backup to /sdcard
You have to push a cwm Backup to the /sdcard to restore it later
Download my package with adb and cwm backup and unzip it wherever you want after the extraction and double click at "111 push cwm files to sdcard.bat" to push all need files to tranfer them to the sdcard
adb push boot.img /sdcard/clockworkmod/backup/2014/boot.img
adb push cache.context /sdcard/clockworkmod/backup/2014/cache.context
adb push cache.ext4.tar /sdcard/clockworkmod/backup/2014/cache.ext4.tar
adb push cache.ext4.tar.a /sdcard/clockworkmod/backup/2014/cache.ext4.tar.a
adb push data.context /sdcard/clockworkmod/backup/2014/data.context
adb push data.f2fs.tar /sdcard/clockworkmod/backup/2014/data.f2fs.tar
adb push data.f2fs.tar.a /sdcard/clockworkmod/backup/2014/data.f2fs.tar.a
adb push nandroid.md5 /sdcard/clockworkmod/backup/2014/nandroid.md5
adb push recovery.img /sdcard/clockworkmod/backup/2014/recovery.img
adb push recovery.log /sdcard/clockworkmod/backup/2014/recovery.log
adb push system.context /sdcard/clockworkmod/backup/2014/system.context
adb push system.ext4.tar /sdcard/clockworkmod/backup/2014/system.ext4.tar
adb push system.ext4.tar.a /sdcard/clockworkmod/backup/2014/system.ext4.tar.a
Click to expand...
Click to collapse
4. Restore CWM Backup
Restore the CWM backup from "Restore from /sdcard" select the 2014 folder and confirm... after sucessful restoring you are able to boot up your MotoG
I hope this worked as a temporal fix Feedback or critics are welcome!!!!
fl4m3y said:
Download link will follow in 1 or 2 hours... it's still uploading to my gdrive
Hey Guys,
i dont know if this is posted somehere here at the MotoG XDA section....
I tried the MotoG GPe Rom and received an OTA Update to Android 4.4.4 and installed it. After reverting to Motorola stock rom or GPe 4.4.2 the phone stucks in the boot logo and won't boot up anymore.
So here's is MY fix for the problem and i hope i can help some... it's a temporal fix right now to unbrick the half-bricked MotoG for further development
1. Restart Phone in Bootloader
Power + Volume down to enter the bootloader mode and flash the GPe Recovery as *.img file from Philz with fastboot command
2. Enter the Recovery Mode
Enter the recovery mode with selecting "Recovery" and hit the volume up to enter it.
In recovery mode you will get some error messages like in the attached phote below. To fix these messages:
3. Push CWM Backup to /sdcard
You have to push a cwm Backup to the /sdcard to restore it later
Download my package with adb and cwm backup and unzip it wherever you want after the extraction and double click at "111 push cwm files to sdcard.bat" to push all need files to tranfer them to the sdcard
4. Restore CWM Backup
Restore the CWM backup from "Restore from /sdcard" select the 2014 folder and confirm... after sucessful restoring you are able to boot up your MotoG
I hope this worked as a temporal fix Feedback or critics are welcome!!!!
Click to expand...
Click to collapse
I haven't had the need to try this but I think its good I'm going to stick with CWM for a while until the update for non GPE devices is out or android L..
Sent from my Moto G using XDA Free mobile app
will have a link
Waiting the downlod link :good:
cecoicov said:
will have a link
Click to expand...
Click to collapse
borimol said:
Waiting the downlod link :good:
Click to expand...
Click to collapse
Download Link is online...
Phone works, but does not recognize the SIM card and no WIFI
cecoicov said:
Phone works, but does not recognize the SIM card and no WIFI
Click to expand...
Click to collapse
Can you now flash official 4.4.2 stock (non GPE)?
cecoicov said:
Phone works, but does not recognize the SIM card and no WIFI
Click to expand...
Click to collapse
works fine for me
borimol said:
Can you now flash official 4.4.2 stock (non GPE)?
Click to expand...
Click to collapse
no... flashing with fastboot wont work until we get the GPe Factory Image (I hope) or another fix... this is a "work around" but the problem isn't fixed
after flash with official stock 4.4.2 (non GPE) does phone not start again
cecoicov said:
after flash with official stock 4.4.2 (non GPE) does phone not start again
Click to expand...
Click to collapse
Fastboot flashes doesn't work until there is a real fix... if the stuck on boot logo persist just follw my tutorial to unbrick the phone
Ок, thanks for the help but I guess I will seek another solution
cecoicov said:
Phone works, but does not recognize the SIM card and no WIFI
Click to expand...
Click to collapse
Same issue occurred to me, the IMEI paste seems to be gone rendering the phone useless for (data) network usage. There's no way to restore the IMEI at the moment.
ok this worked for me
started cyanogenmod????????
i could not test wifi or network
but off course i am dumb, and had to try to restore a nandroid backup of gep 4.4.4, i did and phone ask for password (because of encryption of file system), then i tried again to recover using this method and did not worked, used adb gpe 4.4.2, then again this method and nothing
what the hell
firts time could recover, now it wont recover anymore, stays on google logo lol
--------------
some time latter i managed to boot it again
it started stock android in german?'
i believe there is no signal
maurocds said:
some time latter i managed to boot it again
it started stock android in german?'
i believe there is no signal
Click to expand...
Click to collapse
It's the open german version without any provider stuff... i cant upload th english version because i cant flash via fastboot. the only possibility is to install an english custom rom via cwm. therfore you need to replace the GPe CWM recovery to normal philz recovery because of the filesystem
fl4m3y said:
It's the open german version without any provider stuff... i cant upload th english version because i cant flash via fastboot. the only possibility is to install an english custom rom via cwm. therfore you need to replace the GPe CWM recovery to normal philz recovery because of the filesystem
Click to expand...
Click to collapse
hey man, i sent you a PM, read it fast
-----------
ok i booted my phone again after flashing this, then flashing gpe, then this again lol
you have to be patient while pushing the data, it takes a lot, then after that, you must disable md5 on recovery or else it will fail, then you can restore cwm fine and boot
firmware is stock 442 german, but you can change into english
thanks, no matter what i tried i never could boot
at least the phone work,
have to test more about signal stuff
Due to some personal information (google account) i was forced to deactivate the public access to the file.... password changed of my account and now it should be fine
so download is activated again
Hey,
I´ve been using GPE 4.4.4 recently too and I wanted to go back to German retail 4.4.2. in order to try to catch an OTA. It´s quite easy to do, just beware of one thing. You have to RETAIN the partition table (gpt.bin) from GPE. Do not flash gpt.bin from the target firmware - 4.4.2 in this case, just avoid the step "fastboot flash partition gpt.bin". If you did it already, you can try following: extract gpt.bin from GPE 4.4.4 OTA zip and copy it and replace gpt.bin in your 4.4.2 firmware folder and then flash it using standard procedure.
Also maybe the same thing applies to logo.bin, but of this one I´m not sure. I avoided to flash it too just in case. Now I´m on fully working German retail 4.4.2. No OTA yet, though, but that´s another story.
anyone has the gpt.bin from the GPe 4.4.4????
I want to flash via fastboot the GPe 4.4.2 Version and after the OTA Update to 4.4.4
and btw... thank you for the hint!!!!
View attachment gpt.7z
fl4m3y said:
anyone has the gpt.bin from the gpe 4.4.4????
I want to flash via fastboot the gpe 4.4.2 version and after the ota update to 4.4.4
and btw... Thank you for the hint!!!!
Click to expand...
Click to collapse
from ota gpe 444
drfr said:
Hey,
I´ve been using GPE 4.4.4 recently too and I wanted to go back to German retail 4.4.2. in order to try to catch an OTA. It´s quite easy to do, just beware of one thing. You have to RETAIN the partition table (gpt.bin) from GPE. Do not flash gpt.bin from the target firmware - 4.4.2 in this case, just avoid the step "fastboot flash partition gpt.bin". If you did it already, you can try following: extract gpt.bin from GPE 4.4.4 OTA zip and copy it and replace gpt.bin in your 4.4.2 firmware folder and then flash it using standard procedure.
Also maybe the same thing applies to logo.bin, but of this one I´m not sure. I avoided to flash it too just in case. Now I´m on fully working German retail 4.4.2. No OTA yet, though, but that´s another story.
Click to expand...
Click to collapse
THIS DID NOT WORK FOR ME
I AM ON 4.4.4 gpe
AND JUST WANTED TO TEST
so i put the 4.4.4 ota gpt.bin in the stock 4.4.2 image , and the stock gpe 4.4.2, and both flashes were stuck on logo, did not booted,
Hi all,
Just got the notification to update my french Moto X (2014) XT1092.
Here is the link
LINK
Just flash it via stock recovery.
WARNING : The update will only succeed if you have a RETEUALL or RETIN XT1092 (it won't work for RETGB and RETDE) AND an untouched sytem (no root, xposed, or removed system apps...)
If you have a RETGB or RETDE, no worries you'll just need to convert your phone into a RETEUALL.
Here is how to do this :
1) You'll need an unlocked bootloader, as well as fastboot and adb drivers installed on your computer.
2) First you'll need to download the RETEUALL factory image : here and extract it.
3) Then you'll need to execute each command in a terminal window
Code:
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 flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
4) After that you'll be able to take the OTA
benfiller said:
Hi all,
Just got the notification to update my french Moto X (2014) XT1092.
Here is the link
LINK
Will post screenshots as soon as the OTA finishes
Edit : OTA finished
Click to expand...
Click to collapse
I am getting below mentioned error
<Error>
<Code>ExpiredToken</Code>
<Message>The provided token has expired.</Message>
<Details>Request has expired: 1418383039</Details>
</Error>
Is it the same as the UK version?
Mine says retgb instead of reteu.
Sent from my XT1092 using Tapatalk
Cheers for this, but it looks like the link is down?
I got the file,
but once I try to sideload, it complaints that the fingerprint is not the same.
Yeah, the link is expired. I will mirror it as soon as I can !
You must have a completely untouched (no root, no xposed, no removed system apps etc...) system to pass the OTA.
mcnovy said:
I got the file,
but once I try to sideload, it complaints that the fingerprint is not the same.
Click to expand...
Click to collapse
what's your version retin reteu ????
nandroidz said:
what's your version retin reteu ????
Click to expand...
Click to collapse
21.21.45.victara_retde.retdeall.en.DE.retde
bought in Germany
i think its bcos urs is retde.retdeall
benfiller said:
Yeah, the link is expired. I will mirror it as soon as I can !
You must have a completely untouched (no root, no xposed, no removed system apps etc...) system to pass the OTA.
Click to expand...
Click to collapse
Are these steps the enough to revert the change or do I have to factory reset (I am asking because as far as I know Motorola haven't released factory images for variants other than XT1095)?
1) uninstall xposed through the app then remove the app itself with other modules.
2) completely remove root through SuperSu (Full unroot option).
3) restore stock recovery (link please if possible?)
4) I didn't add or remove system apps other than SuperSu
Thanks,
hasm_747 said:
Are these steps the enough to revert the change or do I have to factory reset (I am asking because as far as I know Motorola haven't released factory images for variants other than XT1095)?
1) uninstall xposed through the app then remove the app itself with other modules.
2) completely remove root through SuperSu (Full unroot option).
3) restore stock recovery (link please if possible?)
4) I didn't add or remove system apps other than SuperSu
Thanks,
Click to expand...
Click to collapse
I'll upload a twrp backup of my stock untouched 4.4.4 system+boot
hey thanks a lot for the link. Its working on my Moto X XT1092 indian version.
benfiller said:
I'll upload a twrp backup of my stock untouched 4.4.4 system+boot
Click to expand...
Click to collapse
Thanks mate,
So after flashing this backup. Do I have to restore the stock recovery or is that not required for the update?
hasm_747 said:
Thanks mate,
So after flashing this backup. Do I have to restore the stock recovery or is that not required for the update?
Click to expand...
Click to collapse
Yes, you'll need stock recovery to do the update.
I'll post it to with the twrp backup
New link is up, check the OP
benfiller said:
New link is up, check the OP
Click to expand...
Click to collapse
Doesn't work for me
Sent from my XT1092 using XDA Free mobile app
undeadadd said:
Doesn't work for me
Sent from my XT1092 using XDA Free mobile app
Click to expand...
Click to collapse
OTA or link ? The link works fine for me, either on phone or computer
benfiller said:
OTA or link ? The link works fine for me, either on phone or computer
Click to expand...
Click to collapse
The links not working on my phone lol
Sent from my XT1092 using XDA Free mobile app
undeadadd said:
The links not working on my phone lol
Sent from my XT1092 using XDA Free mobile app
Click to expand...
Click to collapse
Weird, what does it say ?
benfiller said:
Weird, what does it say ?
Click to expand...
Click to collapse
<Error>
<Code>ExpiredToken</Code>
<Message>The provided token has expired.</Message>
<Details>Request has expired: 1418383039</Details>
</Error>
Sent from my XT1092 using XDA Free mobile app
Hi i just received the announcement that 22.26.1.en.de is ready to install.
I´m currently on official 21.11.14 ret.de
So, check your phones, should be availabale for all now !
:good:
Here is a link to OTA file.
http://www.filefactory.com/file/4ky9luc6apeb/ota.zip
Update with unlocked Bootloader
Hi everybody,
I've got an error message. How do i update with an unlocked and rooted Phone?
dpdp73 said:
Here is a link to OTA file.
http://www.filefactory.com/file/4ky9luc6apeb/ota.zip
Click to expand...
Click to collapse
retde 5.0.2 ota.zipmirror of 385mb OTA retde zip
Same here. 21.11.14 retde. Can't wait to get home to update. Finally!
Sent from my XT1068 using XDA Free mobile app
minifamilie said:
Hi everybody,
I've got an error message. How do i update with an unlocked and rooted Phone?
Click to expand...
Click to collapse
You have to restore any changes to /system, use unroot option in SuperSU and reflash stock recovery.
dpdp73 said:
You have to restore any changes to /system, use unroot option in SuperSU and reflash stock recovery.
Click to expand...
Click to collapse
I'm in the same boat. I can restore a backup to revert my /system (mostly, I think I only have to remove su afterwards), but could you link the stock recovery?
TheCreat said:
I'm in the same boat. I can restore a backup to revert my /system (mostly, I think I only have to remove su afterwards), but could you link the stock recovery?
Click to expand...
Click to collapse
Recovery depends on your system, search for your specific firmware and there will be file recovery.img inside, then just "fastboot flash recovery recovery.img".
TheCreat said:
I'm in the same boat. I can restore a backup to revert my /system (mostly, I think I only have to remove su afterwards), but could you link the stock recovery?
Click to expand...
Click to collapse
stock DE 4.4.4 in my signature
reefuge said:
stock DE 4.4.4 in my signature
Click to expand...
Click to collapse
Well, thank you (both) very much. Downloading/installing now...
TheCreat said:
Well, thank you (both) very much. Downloading/installing now...
Click to expand...
Click to collapse
Were you successful???
minifamilie said:
Were you successful???
Click to expand...
Click to collapse
Unfortunately, no. While the update seemed to complete, the system wouldn't boot afterwards: I got a "No Command" error whenevery I tried to boot. This was shown on a recovery-screen with the android bot in the middle (similar to the screen you see while the update is applied).
I'm now trying to reflash most things (but not wiping my data just yet), including /system, but unfortunately the update has to be downloaded again and it's rather slow...
If that doesn't work either, I'll have to do a full return-to-stock with a complete wipe, but I'd rather not...
With the second attempt the update finally worked fine. Booting obviously takes ages the first time, but afterwards it was fine.
I can recommend to just re-flash the important partitions instead of manually trying to restore the stock state. What I did and what worked was the following (using files for RETDEALL_XT1068_4.4.4_KXB21.85-14_Easy_Installer, linked in the signature of reefuge on the first page of this thread):
Code:
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe 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.exe flash system system.img_sparsechunk.3
mfastboot.exe erase cache
Notably, I didn't wipe (except cache of course), flash the partitions or the modem
TheCreat said:
With the second attempt the update finally worked fine. Booting obviously takes ages the first time, but afterwards it was fine.
I can recommend to just re-flash the important partitions instead of manually trying to restore the stock state. What I did and what worked was the following (using files for RETDEALL_XT1068_4.4.4_KXB21.85-14_Easy_Installer, linked in the signature of reefuge on the first page of this thread):
Code:
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe 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.exe flash system system.img_sparsechunk.3
mfastboot.exe erase cache
Notably, I didn't wipe (except cache of course), flash the partitions or the modem
Click to expand...
Click to collapse
If i understood right, your data wasn't wiped, right?!
minifamilie said:
If i understood right, your data wasn't wiped, right?!
Click to expand...
Click to collapse
Yes exactly.
Unrelated: I don't know to what exactly this is related (Rom? version?), but it seems the lollipop version of XPosed doesn't work on this ROM, it bootloops when installed...
Xposed for lolipoop is in alpha, it still doesn't work on many roms and devices.
But your bootloop rescued me from trying
Sent from my XT1068 using XDA Free mobile app
Change from global Version to retde?
Has anyone tried to change from the global version (Indian rom) to the German version?
I had mine bought on kitkat as German retail and then changed to global rom from India to go to Lollipop.
Any way to change back to German retde?
MrIngenieur said:
Has anyone tried to change from the global version (Indian rom) to the German version?
I had mine bought on kitkat as German retail and then changed to global rom from India to go to Lollipop.
Any way to change back to German retde?
Click to expand...
Click to collapse
Yes in my signature use the DE version (4.4.4) then OTA update to DE lollipop
But im already on lollipop not 4.4.4..
So change should be from 5.02 global india to 5.02 retde german... Any idea?
Sent from my XT1068 using XDA Free mobile app
MrIngenieur said:
But im already on lollipop not 4.4.4..
So change should be from 5.02 global india to 5.02 retde german... Any idea?
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
NO Full german (DE) 5.0.2 firmware available yet , so must downgrade to 4.4.4 de and then ota to 5.0.2 DE lollipop
DO NOT RESTORE BACK TO 4.4. THIS WILL BRICK YOUR PHONE.
--UPDATE--
JUST FLASH THIS! (In stock recovery) https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view
--
(if the above doesn't work, or if you are not on totally stock, use the following method)
Here is how to upgrade from 23.11.14 to 23.16.3
What you need: https://yadi.sk/d/cBaKACE7hQH9Y (upgrade from stock 5.0 to 23.16.3)
http://www.graffixnyc.com/motox.php (stock 5.0 image. You need to use this one. The one found in Motorola's site WILL NOT WORK WITH THIS METHOD)
Unzip the stock 5.0 image
Boot into fastboot
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 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
Boot into recovery
adb sideload Blur_Version.22.21.11.victara_tmo.tmo.en.US.zip
reboot!
can i only update via adb sideload ? from 23.11.14 to 23.16.3 ?? without back to stock 5.0 ?
Grzesiek1010 said:
can i only update via adb sideload ? from 23.11.14 to 23.16.3 ?? without back to stock 5.0 ?
Click to expand...
Click to collapse
if you're on 23.11.14 you have to go back to 5.0 in order to update to the newest 5.1 (23.16.3).
You can also copy the zip over and flash within recovery, if you prefer. I always think sideload is easier (though actually, now that I think about it, I copied it over and flashed from within recovery myself...)
bongostl said:
if you're on 23.11.14 you have to go back to 5.0 in order to update to the newest 5.1 (23.16.3).
You can also copy the zip over and flash within recovery, if you prefer. I always think sideload is easier (though actually, now that I think about it, I copied it over and flashed from within recovery myself...)
Click to expand...
Click to collapse
ok but what with all apps data setting ?
Grzesiek1010 said:
ok but what with all apps data setting ?
Click to expand...
Click to collapse
you have to do a full wipe.
if you're rooted, you could do a titanium backup, etc...
bongostl said:
you have to do a full wipe.
if you're rooted, you could do a titanium backup, etc...
Click to expand...
Click to collapse
better wait for official update too much risk lost data ...
I successfully downgraded to 5.0, and I've attempted the sideload method twice and failed. Each time it says there is an error in the package, status 7. I get the same result when I apply update from sd card. Any ideas?
---------- Post added at 12:25 PM ---------- Previous post was at 11:43 AM ----------
Be advised: some of us are discovering you can't do the OTA to 23.16.3 if you are on 5.0 46_11.11. Apparently you need to be on 5.0 46_11.10.
Use the files I posted.... That's what I used
It's necessary to downgrade to 5.0, even if I'm getting an OTA system update popup from 23.11.14?
leffer said:
It's necessary to downgrade to 5.0, even if I'm getting an OTA system update popup from 23.11.14?
Click to expand...
Click to collapse
If you're on 23.11.14 and you're getting the OTA alert for 23.16.3, then no you don't have to downgrade. Just take the OTA. You should try to capture the OTA if you're rooted
sivarticus85 said:
If you're on 23.11.14 and you're getting the OTA alert for 23.16.3, then no you don't have to downgrade. Just take the OTA. You should try to capture the OTA if you're rooted
Click to expand...
Click to collapse
I am rooted... How do I capture the OTA?
Sent from my XT1095 using XDA Forums
leffer said:
I am rooted... How do I capture the OTA?
Sent from my XT1095 using XDA Forums
Click to expand...
Click to collapse
The OTA is downloaded to the /cache folder. Copy it from your phone to a computer. Can you take a screenshot of the OTA alert?
Success!
Stanleywinthrop said:
Be advised: some of us are discovering you can't do the OTA to 23.16.3 if you are on 5.0 46_11.11. Apparently you need to be on 5.0 46_11.10.
Click to expand...
Click to collapse
I had this problem initially as well because I downgraded to 5.0 using the official Motorola 5.0 firmware downloaded from the Motorola website, which is apparently 46-11.11.
I had to use this one-day-older version instead, which is apparently 46-11.10: TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip. I found it and downloaded it from here: http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/
So... I downloaded the firmware from that link, followed the OP instructions almost exactly*, and I was able to upgrade from 23.11.14 to 23.16.3 successfully.
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
thenestor said:
I had this problem initially as well because I downgraded to 5.0 using the official Motorola 5.0 firmware downloaded from the Motorola website, which is apparently 46-11.11.
I had to use this one-day-older version instead, which is apparently 46-11.10: TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip. I found it and downloaded it from here: http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/
So... I downloaded the firmware from that link, followed the OP instructions almost exactly*, and I was able to upgrade from 23.11.14 to 23.16.3 successfully.
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
Click to expand...
Click to collapse
thanks for your help. I tried to download from your link and for some reason the file will not extract. However, I noticed that your image file is named exactly as the image file linked in the OP to this thread. Are they one in the same?
sivarticus85 said:
The OTA is downloaded to the /cache folder. Copy it from your phone to a computer. Can you take a screenshot of the OTA alert?
Click to expand...
Click to collapse
Here is my current version... http://imgur.com/ae2O6PW
Here is my OTA notification... http://imgur.com/hZZB0DZ
The file name is Blur_Version.23.11.14.victara_tmo.tmo.en.US.zip - is that weird?
Here is a link to the file: https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view?usp=sharing
File Size: 163.7MB
MD5: d8c44d25d0479ef40ad5f092ff7ffd39
I'm sure this upload is gonna get flagged in no time on Google Drive... So somebody else should upload it if possible.
And...success finally. FYI you cannot use the method found in the OP to update the stock 5.0 image from motorola's website. You MUST use the stock image found in the OP.
thenestor said:
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
Click to expand...
Click to collapse
Good catch! I have fixed the original post
Stanleywinthrop said:
And...success finally. FYI you cannot use the method found in the OP to update the stock 5.0 image from motorola's website. You MUST use the stock image found in the OP.
Click to expand...
Click to collapse
I've updated the original post to make this clearer.
anyone able to root this new OTA?
CF auto root was working on every previous OTA from 4.4 to 5.0 and 5.1 but now causes boot loops. I am able to TWRP back to the unrooted build to get me out of the bootloops.
leffer said:
Here is my current version... http://imgur.com/ae2O6PW
Here is my OTA notification... http://imgur.com/hZZB0DZ
The file name is Blur_Version.23.11.14.victara_tmo.tmo.en.US.zip - is that weird?
Here is a link to the file: https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view?usp=sharing
File Size: 163.7MB
MD5: d8c44d25d0479ef40ad5f092ff7ffd39
I'm sure this upload is gonna get flagged in no time on Google Drive... So somebody else should upload it if possible.
Click to expand...
Click to collapse
Thanks! And no, the name is normal. The OTA filename always states the version you need to be on to install it, not the version that it contains.
Hi all,
I have a bit of an issue with the latest OTA update currently being pushed out and looking for help how best to proceed.
I have unlocked and rooted the phone previously and recovery is TWRP. My phone is encrypted.
When I accepted the updated the phone rebooted and showed the TWRP splash screen which flashes on and off endlessly. If I turn the phone off and on again it restarts fine but after a few seconds the update process starts again. I am currently stuck in this loop.
Any advice as to how I can get out of this without wiping my phone?
I am wondering if I could flash the standard recovery to remove TWRP if this would work. Could it and if so, where can i get the standard recovery image.
Thanks and sorry of this is already covered, I searched but couldn't find it.
For XT1575.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
If you want to update be on stock rom i.e. unrooted and no xposed,nothing added or removed from system and also flash stock recovery.
After successful update flash twrp.
So, if I want to install the lastest update it's enough to unroot, remove xposed and flash stock recovery? Or it's better to flash full stock through fastboot?
So I managed to find a link to the full image for my device (XT1572 so the above link wouldn't work to the best of my knowledge - but thanks anyway @Hitti2)
I flashed the standard recovery and rebooted which stopped the endless loop. The update still fails to install but I can live with that for now.
I'll investigate further what I need to do to get the update to take properly but for now I have a functioning phone which is a good start to the day.
Thanks all.
Sent from my XT1572 using Tapatalk
Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]
There is a whole thread dedicated to this update in general.
lafester said:
There is a whole thread dedicated to this update in general.
Click to expand...
Click to collapse
Maybe there is but as I stated in the OP, I couldn't find the right information at the time of posting. Maybe helpful would be to also link the thread as it may help others.
@lafester could you link thread please.
Sent from my XT1572 using Tapatalk
Boot image?
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
user7743 said:
Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]
Click to expand...
Click to collapse
nathlynn22 said:
@lafester could you link thread please.
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
This one possibly?
http://forum.xda-developers.com/moto-x-style/general/xt1575-february-2016-security-update-t3323126
---------- Post added at 10:42 PM ---------- Previous post was at 09:50 PM ----------
chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.
chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
evandena said:
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.
Click to expand...
Click to collapse
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software
Thanks so much for trying to help. I went ahead and flashed the boot and recovery files for my model. I did the Boot image first, no luck. then i did the recovery, and this time andy thought a bit longer before giving me the Error! message. And then instead of my phone doing an autoreboot, it was stuck on the dead Andy and I needed to do hold down the power button to get it to shut down.
Anyone have any additional thoughts?
user7743 said:
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software
Click to expand...
Click to collapse
I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.
This phone has never been able to take OTAs for some reason. I wish I understood why. I tried to leave the thing stock to keep things simple, but it wasn't to be... anyway...
Thanks for the advice. Any idea where to get a download of the .zip files (is it really more than one zip file, or was that a typo)? I tried searching, but can't seem to find the right things to search for.
Also, once i have the zip file(s):
1) Do I just install it via TWRP like any other zip file?
2) to get rid of the OTA prompt, do i wipe the cache and reboot before or after i install the update via the zip?
Many thanks!
InFamousD147 said:
I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.
Click to expand...
Click to collapse
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse
chuck-fu said:
Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Click to expand...
Click to collapse
I have the 1572 RETEU, but you can find the stock firmware here: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
If it's like the stock firmware that I have for the 1572 it should have all the img files and the system chunks. You just need to flash all the chunks like this:
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
This has to be done because Marshmallow doesn't allow any modification in the system or the boot image, and will not proceed with the OTA if the ROM is not full stock.
EDIT: You will not loose any data, but any modification to the system partition will be undone.
Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?
chuck-fu said:
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?
Click to expand...
Click to collapse
I just let the normal OTA install after flashing system, boot and recovery, without wiping any partition. Maybe you can try a flash all the zip to make sure it's full stock and see if the OTA install. Just make a backup before in case nothing change.