Related
Source: http://sbf.droid-developers.org/dinara/list.php
Thank you very much to Pzyduck and his firmware team for finding and leaking these FXZ's for the Atrix HD to us to use!
DO NOT FLASH AT&T ON BELL AND VICE-VERSA!
AT&T FXZ-> http://sbf.droid-developers.org/dinara/7.7.1Q-115_MB886_FFW-14_SIGNED_CFC.xml.zip
System Version: 77.10.16.MB886.ATT.en.US
Bell FXZ-> http://sbf.droid-developers.org/dinara/7.7.1Q-115_MB886_BELL_FFW-12_SIGNED_CFC.xml.zip
System Version: ???
You can find the 32 bit Motorola USB Drivers here:
http://rootingmydroid.com/FILESYSTE..._End_User_Driver_Installation_5.9.0_32bit.msi
And 64 bit here:
http://rootingmydroid.com/FILESYSTE..._End_User_Driver_Installation_5.9.0_64bit.msi
RSD Lite 5.7 for flashing these can be found here:
http://rootingmydroid.com/FILESYSTEM/DEVELOPMENT/UDPATES/-RSD-LITE/RSDLite57.zip
Happy flashing... make sure that you have plenty of battery life before attempting this or you are using a Motorola Factory-style cable.
mattlgroff said:
Source: http://sbf.droid-developers.org/dinara/list.php
Thank you very much to Pzyduck and his firmware team for finding and leaking these FXZ's for the Atrix HD to us to use!
AT&T FXZ-> http://sbf.droid-developers.org/dinara/7.7.1Q-115_MB886_FFW-14_SIGNED_CFC.xml.zip
System Version: 77.10.16.MB886.ATT.en.US
Bell FXZ-> http://sbf.droid-developers.org/dinara/7.7.1Q-115_MB886_BELL_FFW-12_SIGNED_CFC.xml.zip
System Version: ???
You can find the 32 bit Motorola USB Drivers here:
http://rootingmydroid.com/FILESYSTE..._End_User_Driver_Installation_5.9.0_32bit.msi
And 64 bit here:
http://rootingmydroid.com/FILESYSTE..._End_User_Driver_Installation_5.9.0_64bit.msi
RSD Lite 5.7 for flashing these can be found here:
http://rootingmydroid.com/FILESYSTEM/DEVELOPMENT/UDPATES/-RSD-LITE/RSDLite57.zip
Happy flashing... make sure that you have plenty of battery life before attempting this or you are using a Motorola Factory-style cable.
Click to expand...
Click to collapse
I am new to motorola phones. Can someone explain what this is?
A leaked update? Is this version rootable? And on that note, is an unlocked bootloader required for root?
Sent from my phone.
Markyzz said:
I am new to motorola phones. Can someone explain what this is?
A leaked update? Is this version rootable? And on that note, is an unlocked bootloader required for root?
Sent from my phone.
Click to expand...
Click to collapse
Firmware Stock/Official :good:
Thanks you matt
MIRROR: http://forum.xda-developers.com/showthread.php?p=30714649#post30714649
Markyzz said:
I am new to motorola phones. Can someone explain what this is?
A leaked update? Is this version rootable? And on that note, is an unlocked bootloader required for root?
Sent from my phone.
Click to expand...
Click to collapse
These are files that can be used to truly factory restore your phone. If you had a custom rom installed, this would put you back to stock.
You use Motorola's RSD Lite program to flash to your phone while it is in AP Fastboot mode.
This will work on locked bootloaders because they are signed files from Motorola meant for flashing in this way.
EDIT: As Pzyduck says above, these are official firmware not leaks
Don't flash AT&T on Bell or vice versa, you may get trapped because of secure versions.
(btw. I know, it's codenamed qinara, and not dinara, but meh, too lazy to fix it )
Skrilax_CZ said:
Don't flash AT&T on Bell or vice versa, you may get trapped because of secure versions.
(btw. I know, it's codenamed qinara, and not dinara, but meh, too lazy to fix it )
Click to expand...
Click to collapse
If you look inside the files themselves Motorola was too lazy to fix it too! They use both throughout lol.
Thanks to mattlgroff for posting here
---------- Post added at 04:03 AM ---------- Previous post was at 04:01 AM ----------
Pzyduck said:
Firmware Stock/Official :good:
Thanks you matt
MIRROR: http://forum.xda-developers.com/showthread.php?p=30714649#post30714649
Click to expand...
Click to collapse
Can these files be modded to allow root before they are installed on the phone?
reddog said:
Thanks to mattlgroff for posting here
---------- Post added at 04:03 AM ---------- Previous post was at 04:01 AM ----------
Can these files be modded to allow root before they are installed on the phone?
Click to expand...
Click to collapse
On 2 accounts we wouldn't be able to do this.
1) The phone will only take signed images for system in AP Fastboot. There are sig checks on flashing and on boot (we can assume this, we can test more obviously since we have FXZ backups).
I didn't want to test flashing a rooted system dd'd out before because we had no FXZ's to test. Now that we have them it might be worth it to try it out. Worst case use these FXZ.
Rooted system.img: you can get the entire partitions here which includes it: http://crackflasher.com/dev/mattlgroff/MB886.ATT.en.US/AtrixHdPartitions.zip
Be extra careful flashing things you do not have backups for...
2) The system.img.ext4 file inside of these are not only compressed, but appear to be encrypted as well.
mattlgroff said:
On 2 accounts we wouldn't be able to do this.
1) The phone will only take signed images for system in AP Fastboot. There are sig checks on flashing and on boot (we can assume this, we can test more obviously since we have FXZ backups).
I didn't want to test flashing a rooted system dd'd out before because we had no FXZ's to test. Now that we have them it might be worth it to try it out. Worst case use these FXZ.
Rooted system.img: you can get the entire partitions here which includes it: http://crackflasher.com/dev/mattlgroff/MB886.ATT.en.US/AtrixHdPartitions.zip
Be extra careful flashing things you do not have backups for...
2) The system.img.ext4 file inside of these are not only compressed, but appear to be encrypted as well.
Click to expand...
Click to collapse
Any luck flashing this yet?
popfan said:
Any luck flashing this yet?
Click to expand...
Click to collapse
No one's tried to my knowledge, also the system.img.ext4 is not encrypted, but its compression methods are unknown.
mattlgroff said:
No one's tried to my knowledge, also the system.img.ext4 is not encrypted, but its compression methods are unknown.
Click to expand...
Click to collapse
i tried but nothing. only error when installing
There is a new firmware listed as MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip has anyone tried to to flash this yet? Is this 4.1.1 OTA that we have now? I need to know because like an idiot I tried to flash back to 4.0.4 from 4.1.1 and now it fastboots on every reboot. Super annoying. Anyway I need to flash to 4.1.1 to fix this apparently.
Tried it says unknown command flash failed unknown flash boot command so u can try but no good phone still OK so I got lucky
Sent from my MB886 using xda app-developers app
Long story, but I lost my /system folder on my stock Att xt1058 running 4.4.2.
I have an unlocked bootloader.
Can anyone upload to a Dropbox, or somewhere else, just the system partition so I can restore via nandroid on TWRP? Otherwise I am stuck waiting for the SBF, since I can no longer downgrade.
Thanks
Sent from my Moto X using Tapatalk
Well...
This is untested, but it is a flashable zip that I made from a dump of my ATT 4.4.2 /system. The kernel is included within the zip, but it is not automatically flashed, and you will need to use fastboot to flash it. (I intended this to be used with safestrap..)
165.44.1.ghost_att: http://www.androidfilehost.com/?fid=23329332407581236
Let me know if this flashable zip works. I will post it with the instructions for locked bootloaders...
Will work on this in a few hours.
Just so I am clear, flash zip in recovery, pull boot.img out of the zip, and flash boot.img manually via fastboot. Right?
Sent from my Moto X using Tapatalk
cpetersen2791 said:
Will work on this in a few hours.
Just so I am clear, flash zip in recovery, pull boot.img out of the zip, and flash boot.img manually via fastboot. Right?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Exactly.
I see it was downloaded 9 times before me. I didn't have any luck with both TWRP and Philz's recovery. Flash stalled on "extracting system files" for 5+ minutes.
I would take the entire TWRP backup if you can upload that.
UPDATE: I deleted the boot.img out of the zip file, and it flashed, then manually flashed boot.img.
UPDATE 2: No radio, nor wifi to connect...Suggestions? I feel i am so close!
Ctrl-Freak said:
Well...
This is untested, but it is a flashable zip that I made from a dump of my ATT 4.4.2 /system. The kernel is included within the zip, but it is not automatically flashed, and you will need to use fastboot to flash it. (I intended this to be used with safestrap..)
165.44.1.ghost_att
Let me know if this flashable zip works. I will post it with the instructions for locked bootloaders...
Click to expand...
Click to collapse
OMG, I think this file will help me to rescue my brick!!!!!
Can I manually flash this firmware on my device using fastboot tool?I have no idea about what safestrap is,please no hate.
It's still a WIP, after flashing, I didn't have radio. Will work on that tomorrow. If we get it going, I'll post something, with Ctrl-Freak's approval.
Sent from my Moto X using Tapatalk
Ctrl-Freak said:
Exactly.
Click to expand...
Click to collapse
I download your zip and find out this is not a firmware...OTZ
I can only wait until the sbf file released.
cpetersen2791 said:
UPDATE 2: No radio, nor wifi to connect...Suggestions? I feel i am so close!
...
It's still a WIP, after flashing, I didn't have radio...
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
I can say that the 4.4 modem works fine with 4.4.2. Are you running a 4.4.x modem? If so, you might be experiencing "the radio" problem (One symptom, is that it shows "unknown" in status.)
This radio problem has plagued me in safestrap. No matter what 4.4.x rom I tried to flash, if I was already running 4.4.x, I could not TWRP /system, fastboot boot.img and keep a working radio. I had no idea the problem might persist with an unlocked bootloader's TWRP.
In the past, to fix the radio problem, I always need to downgrade to 4.2.2 (using fastboot->system, boot, modem and recovery.) Then I root, safestrap, load 4.4.x rom using safestrap's TWRP, then fastboot radio and kernel. After that the radio problem disappears.
However... Other people seem to be successful by doing a factory reset in safestrap's TWRP. For instance, look at these instructions: http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-1-4-13-2014-t2716657
Safestrap Version
-If you are already on 4.4.2 then boot into Safestrap and factory reset, do not wipe the system then install to the STOCK slot.
-If your not on 4.4.2 then go here and follow the instructions from my stock rom thread http://rootzwiki.com/topic/116025-ro...52-kitkat-442/ I don't feel like reposting them in here.
Click to expand...
Click to collapse
Previously, I looked at a rom that was intended for the above instructions. That rom basically did the same as mine: It formatted and loaded /system.
Ctrl-Freak said:
I can say that the 4.4 modem works fine with 4.4.2. Are you running a 4.4.x modem? If so, you might be experiencing "the radio" problem (One symptom, is that it shows "unknown" in status.)
This radio problem has plagued me in safestrap. No matter what 4.4.x rom I tried to flash, if I was already running 4.4.x, I could not TWRP /system, fastboot boot.img and keep a working radio. I had no idea the problem might persist with an unlocked bootloader's TWRP.
In the past, to fix the radio problem, I always need to downgrade to 4.2.2 (using fastboot->system, boot, modem and recovery.) Then I root, safestrap, load 4.4.x rom using safestrap's TWRP, then fastboot radio and kernel. After that the radio problem disappears.
However... Other people seem to be successful by doing a factory reset in safestrap's TWRP. For instance, look at these instructions: http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-1-4-13-2014-t2716657
Previously, I looked at a rom that was intended for the above instructions. That rom basically did the same as mine: It formatted and loaded /system.
Click to expand...
Click to collapse
Those are all Verizon Radio's. Do you think I can grab the ATT version 4.4 radio and manually flash? I have that sbf available. Or will the Verizon work in an ATT xt1058
cpetersen2791 said:
Those are all Verizon Radio's. Do you think I can grab the ATT version 4.4 radio and manually flash? I have that sbf available. Or will the Verizon work in an ATT xt1058
Click to expand...
Click to collapse
Sorry. I wasn't telling you to get that rom or the Verizon radio, I was pointing out that a factory reset in TWRP may help with the radio issue.
Long story, but I lost my /system folder on my stock Att xt1058 running 4.4.2.
Click to expand...
Click to collapse
So I am guessing that you took the OTA to originally get to 4.4.2. You should already be running that modem. If that is true, I would not change it.
Ctrl-Freak said:
So I am guessing that you took the OTA to originally get to 4.4.2. You should already be running that modem. If that is true, I would not change it.
Click to expand...
Click to collapse
I factory reset prior to installing, should i wipe /system as well? I am running AOSP roms (PAC) now, and there is no problem with the radio.
I took the OTA, so I dunno what the radio problem would be. Wifi wouldn't turn on either, so i dunno if it's just a radio issue.
i am fortunate to be unlocked bootloader, so i got a copy of the GPE xt1053 posted here as well, and it appears it will work. I think i am gonna try to flash that, then your files w/o a wipe. How does that sound? Unless you got other ideas.
cpetersen2791 said:
I factory reset prior to installing, should i wipe /system as well? I am running AOSP roms (PAC) now, and there is no problem with the radio.
I took the OTA, so I dunno what the radio problem would be. Wifi wouldn't turn on either, so i dunno if it's just a radio issue.
i am fortunate to be unlocked bootloader, so i got a copy of the GPE xt1053 posted here as well, and it appears it will work. I think i am gonna try to flash that, then your files w/o a wipe. How does that sound? Unless you got other ideas.
Click to expand...
Click to collapse
I do not fully understand the radio/wifi issue, so all of my ideas would be trial and error. Give your plan a go and let us know. I would love to know what causes this issue, as a solution should help us using safestrap.
Another thought. Maybe I have to flash the radio, even though I haven't changed. Kind of like flashing the boot.img. I haven't changed that either, but it had to be flashed to boot.
Do you know where I can grab the radio IMG? Can't seem to find it around.
I supposed I can pull it from Att 4.4 sbf. Which files tho, just the Non-hlos.bin file? I don't have the xml here @ the office so I don't know what to look for.
Thanks again for your help
Sent from my Moto X using Tapatalk
Ctrl-Freak said:
I do not fully understand the radio/wifi issue, so all of my ideas would be trial and error. Give your plan a go and let us know. I would love to know what causes this issue, as a solution should help us using safestrap.
Click to expand...
Click to collapse
Found this...
it's OS 4.4 (140.44.5), will that run into the brick issue?
It's already rooted/unlocked bootloader but, I did everything alright and this is what happened.
can someone help me get if fixed ? thanks
obs: it didn't brick or anything.. just fails when I try to upgrade.
This is what's written:
Updating partition details...
Installing '/sdcard/Blur_Version.212.44.22.ghost
checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of motorola/gh
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/Blur_Version.212.44.
Updating partition details...
FAILED.
HomeWipe cache/dalvik Robot System
Liooh said:
It's already rooted/unlocked bootloader but, I did everything alright and this is what happened.
can someone help me get if fixed ? thanks
obs: it didn't brick or anything.. just fails when I try to upgrade.
This is what's written:
Updating partition details...
Installing '/sdcard/Blur_Version.212.44.22.ghost
checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of motorola/gh
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/Blur_Version.212.44.
Updating partition details...
FAILED.
HomeWipe cache/dalvik Robot System
Click to expand...
Click to collapse
Sorry, I didn't mark the Q question.
Liooh said:
Sorry, I didn't mark the Q question.
Click to expand...
Click to collapse
Are you sure of the file your attempting to use.? Maybe you have an FXZ zip file, and you would need to flash with RSDLite or adb..not TWRP..double check what you are attempting..
Also..make sure you are using the correct file for your device..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
Are you sure of the file your attempting to use.? Maybe you have an FXZ zip file, and you would need to flash with RSDLite or adb..not TWRP..double check what you are attempting..
Also..make sure you are using the correct file for your device..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
Click to expand...
Click to collapse
I've wondered that too but I'm using the one that was recommended. The one with the Lite I already did and it proceeded well.
Do you know where I can find more files like that then ? (not firmwares)
Liooh said:
I've wondered that too but I'm using the one that was recommended. The one with the Lite I already did and it proceeded well.
Do you know where I can find more files like that then ? (not firmwares)
Click to expand...
Click to collapse
OMGoodness.. I'm not really sure Sir..I have a XT1060 DEV..but I haven't kept up with the Moto X lately (in the past month)..So..I'm not really the one to help you with newer versions..Are you sure 4.4.3 is right for your device.?
I'd suggest do research in here (XDA) and know what is the latest..I'm assuming that you are trying to flash an OTA..but if you have a file someone has "ported" or something of that nature..go back to where you downloaded the file and research..
Even if you have an OTA zip..I'd suggest maybe know the file more, maybe it should be unzipped and run an XML file..I honestly am not familiar with the file you are attempting to use..
Maybe post a link to where you found the file and myself and others can go look at what file and its purpose..then maybe we can assist you more..Sorry I can't help you more at this time..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
OMGoodness.. I'm not really sure Sir..I have a XT1060 DEV..but I haven't kept up with the Moto X lately (in the past month)..So..I'm not really the one to help you with newer versions..Are you sure 4.4.3 is right for your device.?
I'd suggest do research in here (XDA) and know what is the latest..I'm assuming that you are trying to flash an OTA..but if you have a file someone has "ported" or something of that nature..go back to where you downloaded the file and research..
Even if you have an OTA zip..I'd suggest maybe know the file more, maybe it should be unzipped and run an XML file..I honestly am not familiar with the file you are attempting to use..
Maybe post a link to where you found the file and myself and others can go look at what file and its purpose..then maybe we can assist you more..Sorry I can't help you more at this time..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
Click to expand...
Click to collapse
It was an youtube video, his device is the same as mine XT1058, his device went perfectly.
Liooh said:
It was an youtube video, his device is the same as mine XT1058, his device went perfectly.
Click to expand...
Click to collapse
Oh..OK..maybe contact that one to help you..go back to the video and post a comment/question..maybe someone there can help..
Also maybe post a link here..and we can go look ourselves and maybe help you.?
Also..make sure you have a good download..not corrupted..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
Whatever you are trying to flash can't be flashed with twrp so there's problem number one...
Sent from my XT1060
Liooh said:
It's already rooted/unlocked bootloader but, I did everything alright and this is what happened.
can someone help me get if fixed ? thanks
obs: it didn't brick or anything.. just fails when I try to upgrade.
This is what's written:
Updating partition details...
Installing '/sdcard/Blur_Version.212.44.22.ghost
checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of motorola/gh
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/Blur_Version.212.44.
Updating partition details...
FAILED.
HomeWipe cache/dalvik Robot System
Click to expand...
Click to collapse
Yep, @rocketsaucev2 is right. You appear to be attempting to flash the update.zip from custom recovery. It is well documented that you must have STOCK recovery in order to flash an official update.zip
samwathegreat said:
Yep, @rocketsaucev2 is right. You appear to be attempting to flash the update.zip from custom recovery. It is well documented that you must have STOCK recovery in order to flash an official update.zip
Click to expand...
Click to collapse
It's already STOCK.
Isn't the 4.4.2 you're talking about ?
Liooh said:
It's already STOCK.
Isn't the 4.4.2 you're talking about ?
Click to expand...
Click to collapse
No, it isn't. The screenshots you uploaded CLEARLY show custom recovery. You need to flash stock recovery back before you can take any updates.
If you don't know the difference between stock and custom recovery, you aren't ready to update. You need to Read, Read, Read....
This would be a good start: http://mark.cdmaforums.com/MotoX-OTA.html (Thanks @KidJoe for the well-written documentation)
samwathegreat said:
No, it isn't. The screenshots you uploaded CLEARLY show custom recovery. You need to flash stock recovery back before you can take any updates.
If you don't know the difference between stock and custom recovery, you aren't ready to update. You need to Read, Read, Read....
This would be a good start: http://mark.cdmaforums.com/MotoX-OTA.html (Thanks @KidJoe for the well-written documentation)
Click to expand...
Click to collapse
Hi friend..
Yes I did everything.
Here me explaining everything: http://forum.xda-developers.com/and...ns-problem-t2810890/post54034992#post54034992
Liooh said:
Hi friend..
Yes I did everything.
Here me explaining everything: http://forum.xda-developers.com/and...ns-problem-t2810890/post54034992#post54034992
Click to expand...
Click to collapse
I'm trying really hard to explain it to you but you just aren't getting it....
This is what you wrote in the post you linked:
1- Return to STOCK(Mine is 4.4.2) But I did stock it to 4.4.2. OK!
2- Install the TWRP to install the SuperSU. OK, Everything's fine.
3- After it, my dev is already rooted.
OK, look at step number 2: YOU INSTALLED TWRP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
When you flashed TWRP, you REPLACED stock recovery with custom recovery (TWRP).
As I've been trying to make you understand, OTAs will -----ONLY----- install if you have STOCK RECOVERY.
You will need to flash stock recovery BACK (replacing TWRP), THEN you can accept the update!!!!
Afterwards, you can flash TWRP back.
This is well documented everywhere.....you will have to do this EVERYTIME a new OTA comes out.
You can NOT accept an OTA if you have TWRP installed.
Do you understand now?
samwathegreat said:
I'm trying really hard to explain it to you but you just aren't getting it....
This is what you wrote in the post you linked:
1- Return to STOCK(Mine is 4.4.2) But I did stock it to 4.4.2. OK!
2- Install the TWRP to install the SuperSU. OK, Everything's fine.
3- After it, my dev is already rooted.
OK, look at step number 2: YOU INSTALLED TWRP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
When you flashed TWRP, you REPLACED stock recovery with custom recovery (TWRP).
As I've been trying to make you understand, OTAs will -----ONLY----- install if you have STOCK RECOVERY.
You will need to flash stock recovery BACK (replacing TWRP), THEN you can accept the update!!!!
Afterwards, you can flash TWRP back.
This is well documented everywhere.....you will have to do this EVERYTIME a new OTA comes out.
You can NOT accept an OTA if you have TWRP installed.
Do you understand now?
Click to expand...
Click to collapse
But I did STOCK and no updates came up.
Liooh said:
But I did STOCK and no updates came up.
Click to expand...
Click to collapse
I'm convinced that you aren't even reading what I'm writing......
Let me make this easy for you:
Do this:
1. Return to Stock 4.4.2
2. Accept the OTA (DO NOT FLASH TWRP)
3. After you accept the OTA, and you are running 4.4.3, NOW you can install TWRP
YOU CANNOT ACCEPT THE OTA IF TWRP IS INSTALLED!!!!! I've told you this SO many times now.....
TWRP is your problem. You must NOT install TWRP and root (supersu) until AFTER you accept the OTA.
It has ALWAYS been like this. This is nothing new.
Please read my posts carefully. If you follow those instructions, it WILL work.........
samwathegreat said:
I'm convinced that you aren't even reading what I'm writing......
Let me make this easy for you:
Do this:
1. Return to Stock 4.4.2
2. Accept the OTA (DO NOT FLASH TWRP)
3. After you accept the OTA, and you are running 4.4.3, NOW you can install TWRP
YOU CANNOT ACCEPT THE OTA IF TWRP IS INSTALLED!!!!! I've told you this SO many times now.....
TWRP is your problem. You must NOT install TWRP and root (supersu) until AFTER you accept the OTA.
It has ALWAYS been like this. This is nothing new.
Please read my posts carefully. If you follow those instructions, it WILL work.........
Click to expand...
Click to collapse
When I go back to STOCK doesn't the TWRP break ? Because whenever I go back to stock and try to click on "Recovery" Dev stops working. That's what I did man..
1- Back to STOCK perfectly.
2- No Updates comes up. What's this OTA update you're talking about ? where does it pops up ? I'M SURE I DIDN'T RECEIVE ANY right after I stock it... I even checked it in the System Updates...
Liooh said:
When I go back to STOCK doesn't the TWRP break ? Because whenever I go back to stock and try to click on "Recovery" Dev stops working. That's what I did man..
1- Back to STOCK perfectly.
2- No Updates comes up. What's this OTA update you're talking about ? where does it pops up ? I'M SURE I DIDN'T RECEIVE ANY right after I stock it... I even checked it in the System Updates...
Click to expand...
Click to collapse
YES, you do NOT want TWRP (or you can't accept the update).
OTA = "Over the air update" = update to 4.4.3
What method are you using to return to stock? Tell me you aren't just doing a "factory reset". How exactly are you "returning to stock"?
If you install TWRP = updates DISABLED.
samwathegreat said:
YES, you do NOT want TWRP (or you can't accept the update).
OTA = "Over the air update" = update to 4.4.3
What method are you using to return to stock? Tell me you aren't just doing a "factory reset". How exactly are you "returning to stock"?
If you install TWRP = updates DISABLED.
Click to expand...
Click to collapse
I tried many.. RSDLite, Manual flashing and that one that is recommended for people with problems with "boot loop" and the first I tried two days ago that erased all my data, cache, everything..
The thing is, is that every method seems to work fine but I just don't receive the update '-'
Actually I receive that upgrade that is something that pops up for 3 seconds saying "Upgrading android, installing apps." Then my Dev initializes normal but still dealing with the 4.4.2...
Liooh said:
I tried many.. RSDLite, Manual flashing and that one that is recommended for people with problems with "boot loop" and the first I tried two days ago that erased all my data, cache, everything..
The thing is, is that every method seems to work fine but I just don't receive the update '-'
Click to expand...
Click to collapse
Please just try.
1. Return to Stock (just use RSD Lite) YES, this will erase EVERYTHING.
2. Go to settings > About Device > System Update
3. Update to 4.4.3 will install.
4. After 4.4.3 successfully installs, NOW you can flash TWRP (ONLY after you are on 4.4.3)
Please just try it.....
---------- Post added at 08:21 PM ---------- Previous post was at 07:36 PM ----------
Liooh said:
Actually I receive that upgrade that is something that pops up for 3 seconds saying "Upgrading android, installing apps." Then my Dev initializes normal but still dealing with the 4.4.2...
Click to expand...
Click to collapse
That is because you flashed TWRP, as I've been trying to make you understand.....
Is Spanish your native language?
If so, perhaps this page will explain it better than I can:
http://getmovil.com/motorola/instalar-android-4-4-3-moto-x-root/
samwathegreat said:
Please just try.
1. Return to Stock (just use RSD Lite) YES, this will erase EVERYTHING.
2. Go to settings > About Device > System Update
3. Update to 4.4.3 will install.
4. After 4.4.3 successfully installs, NOW you can flash TWRP (ONLY after you are on 4.4.3)
Please just try it.....
Click to expand...
Click to collapse
See now ?
The problem: Overnight my Moto X (xt1056) went dark. Was 80%+ charged, woke up and dead as a door nail.
The day before I took 4.4.4 OTA, flashed TWRP, rooted, backed up the ROM. All turned out fine.
Now when it boots it gets about 80% of the way through the boot animation and then it goes black and nothing ever happens. So I went into recovery and attempted to flash my backup but it fails. NO!!! It says cannot mount \system. Now I cannot wipe anything and I can't mount anything and I cant flash any ROMs.
I have tried flashing back to stock using some unbricking articles, but they all result the same way.
I think I need to reflash the gpt.bin for 4.4.4, but I can't find one. I am open to any ideas, and let me know if you need any other info.
Thanks XDA community!
cnelson3225 said:
The problem: Overnight my Moto X (xt1060) went dark. Was 80%+ charged, woke up and dead as a door nail.
The day before I took 4.4.4 OTA, flashed TWRP, rooted, backed up the ROM. All turned out fine.
Now when it boots it gets about 80% of the way through the boot animation and then it goes black and nothing ever happens. So I went into recovery and attempted to flash my backup but it fails. NO!!! It says cannot mount \system. Now I cannot wipe anything and I can't mount anything and I cant flash any ROMs.
I have tried flashing back to stock using some unbricking articles, but they all result the same way.
I think I need to reflash the gpt.bin for 4.4.4, but I can't find one. I am open to any ideas, and let me know if you need any other info.
Thanks XDA community!
Click to expand...
Click to collapse
How about a standard RSD XML restore?
aviwdoowks said:
How about a standard RSD XML restore?
Click to expand...
Click to collapse
I have tried RSD Lite... but with 4.4.2 not 4.4.4
Not sure what you mean by RSD XML...
cnelson3225 said:
I have tried RSD Lite... but with 4.4.2 not 4.4.4
Not sure what you mean by RSD XML...
Click to expand...
Click to collapse
Did the OTA "take" bringing it to 444? So if you try 442 that would be a downgrade? Right. Try Rsd lite with 444 unmodified. Edit,
But you may have a brick due to the 442 flash.
cnelson3225 said:
I have tried RSD Lite... but with 4.4.2 not 4.4.4
Not sure what you mean by RSD XML...
Click to expand...
Click to collapse
You can't downgrade!!!! Never attempt to flash a previous version. Best/easiest way to BRICK your device!
He means using RSD Lite. But use the 4.4.4 SBF. Use this one: http://sbf.droid-developers.org/download.php?device=0&file=940
samwathegreat said:
You can't downgrade!!!! Never attempt to flash a previous version. Best/easiest way to BRICK your device!
He means using RSD Lite. But use the 4.4.4 SBF. Use this one:
Click to expand...
Click to collapse
Just to clarify, the ROM says VZW but this is Sprint, will it matter?
Are you xt1060 or Sprint? Yes it matters.
---------- Post added at 08:27 PM ---------- Previous post was at 08:24 PM ----------
Choose your phone
http://sbf.droid-developers.org/
cnelson3225 said:
Just to clarify, the ROM says VZW but this is Sprint, will it matter?
Click to expand...
Click to collapse
Yep, there IS NO Sprint XT1060.
All XT1060s are VERIZON. Big deal, and big difference. Your first post said you have an XT1060...........
You are in a tough situation if you are using a Sprint Device. The ONLY 4.4.4 SBF that has been released is for Verizon. You may have a brick for possibly weeks until the Sprint 4.4.4 SBF is released....
I don't think there is a 444 xt1056 XML ? There is a thread in the dev sec.
Edit but there is no firmware link- XML/Rsd file so you are stuck til a release is out.
samwathegreat said:
Yep, there IS NO Sprint XT1060.
All XT1060s are VERIZON. Big deal, and big difference. Your first post said you have an XT1060...........
You are in a tough situation if you are using a Sprint Device. The ONLY 4.4.4 SBF that has been released is for Verizon. You may have a brick for possibly weeks until the Sprint 4.4.4 SBF is released....
Click to expand...
Click to collapse
I apologize, it is xt1056 Sprint
http://forum.xda-developers.com/showpost.php?p=46834711&postcount=1
There is no solution here. You must wait for the official XML.
Let others note : do not downgrade. Which is what happened here. The borked OTA was just bad luck or an example of how things can go wrong. But the op would be stranded anyway with no XML to fix it yet. But He will not know til the XML comes.
aviwdoowks said:
http://forum.xda-developers.com/showpost.php?p=46834711&postcount=1
There is no solution here. You must wait for the official XML.
Let others note : do not downgrade. Which is what happened here. The borked OTA was just bad luck or an example of how things can go wrong. But the op would be stranded anyway with no XML to fix it yet. But He will not know til the XML comes.
Click to expand...
Click to collapse
But there is a 4.4.4 ROM there, is that not what I want? I apologize for being such a noob but I don't know what the difference between a XML and SBF are? Well I know what an XML is... Just not in relation to my issue.
cnelson3225 said:
But there is a 4.4.4 ROM there, is that not what I want? I apologize for being such a noob but I don't know what the difference between a XML and SBF are? Well I know what an XML is... Just not in relation to my issue.
Click to expand...
Click to collapse
Notice how 444 has no firmware button while the others do. Rsd can only flash firmware. Roms are flashed by custom recovery & they only touch boot, system, data & recovery. Rsd does much more. You have borked partitions that, hopefully, only firmware & RSD (or fastboot) can fix.
cnelson3225 said:
But there is a 4.4.4 ROM there, is that not what I want? I apologize for being such a noob but I don't know what the difference between a XML and SBF are? Well I know what an XML is... Just not in relation to my issue.
Click to expand...
Click to collapse
The "XML" is a file inside the SBF that instructs RSD Lite which operations to perform. For all practical purposes, they mean the same thing....
There is ONLY a 4.4.4 SBF for Verizon. You do not want to flash this to your sprint phone - most likely it will get no service.
I'm sorry that your phone is in a non-functional state, but it definitely sounds like you had modified something that caused the OTA update to go wrong. Unless you want to risk permanently bricking your phone, you will do this:
Put it in a drawer somewhere. Re-activate an old device to use in the meantime. Wait until the official 4.4.4 SBF is leaked for the Sprint XT1056 (could be tomorrow, could be next month - no one knows). When it is leaked and appears on the droid-developers site, you can ATTEMPT to flash it, and hopefully you will recover.
Bummer. Bad situation to be in....
aviwdoowks said:
Notice how 444 has no firmware button while the others do. Rsd can only flash firmware. Roms are flashed by custom recovery & they only touch boot, system, data & recovery. Rsd does much more. You have borked partitions that, hopefully, only firmware & RSD (or fastboot) can fix.
Click to expand...
Click to collapse
Oh I get it now! So now I need to hope someone releases the firmware and hope that when I flash it it fixes the problem. Right? lol
Of course the OTA (Blur.update.zip) needs an intact partition/phone structure to add on to so it is of no value now.
samwathegreat said:
The "XML" is a file inside the SBF that instructs RSD Lite which operations to perform. For all practical purposes, they mean the same thing....
There is ONLY a 4.4.4 SBF for Verizon. You do not want to flash this to your sprint phone - most likely it will get no service.
I'm sorry that your phone is in a non-functional state, but it definitely sounds like you had modified something that caused the OTA update to go wrong. Unless you want to risk permanently bricking your phone, you will do this:
Put it in a drawer somewhere. Re-activate an old device to use in the meantime. Wait until the official 4.4.4 SBF is leaked for the Sprint XT1056 (could be tomorrow, could be next month - no one knows). When it is leaked and appears on the droid-developers site, you can ATTEMPT to flash it, and hopefully you will recover.
Bummer. Bad situation to be in....
Click to expand...
Click to collapse
So if I flash VZW it will work but I won't have service? That would be great because I don't have service now! I was already waiting for Ting to whitelist the Moto X. So if I run that now, I can check back when (if) Ting opens up and perhaps the Sprint one is out. Right?
cnelson3225 said:
Oh ...
Click to expand...
Click to collapse
You risk loosing your imei or worst. If you find someone who has done it? Flashed Vzw to a sprint phone, testimony....
cnelson3225 said:
So if I flash VZW it will work but I won't have service? That would be great because I don't have service now! I was already waiting for Ting to whitelist the Moto X. So if I run that now, I can check back when (if) Ting opens up and perhaps the Sprint one is out. Right?
Click to expand...
Click to collapse
It isn't without risk....but another member says that he did it successfully. A member in my SIM-UNLOCK thread has flashed the VZW firmware to his Sprint Moto X. He did not lose the IMEI, and since he used my sim-unlock method, the phone works on any GSM carrier.
But DO NOT take this as me saying that you SHOULD do this, or that it is safe. I'm warning you that it COULD make your condition worse or could cause irreversible damage. I have NOT done this myself, and I would never recommend it.
It *Might* work for you, but *ONLY* if you have unlocked the bootloader, and its still quite risky. If you do it, you are doing it completely at your own risk - I'm not responsible for anything that goes wrong.
I understand. I already F'd up once by taking a risk, I think I learned my lesson. I will wait a bit for the Sprint firmware and if that pans out then I can rethink it.
So the Sprint ROMs page you linked me is the place to watch if it comes?
Hello mighty XDA developers,
Reason(?):
I have f**ked my XT1097 (Bootloader unlocked, Telus, Canada). I tried to root my Lollipop phone with bhp090808's multi-tool V4.1. Somehow the tool was unsuccessful on rooting my phone. It installed supersu and that was that.
With Supersu installed, apps were somehow unable to download from Google Play, therefore I disabled it and the problem was gone. I was then in vacation so I have no access of Windows so I left it at that for a week, phone ran normally.
After I got back form vacation, I reverted my phone back to stock recovery and 4.4.4 with the Multi-tool, in order to try re-rooting the phone. I might or might not have started the root process when I was in 4.4.4 (I honestly don't remember). Afterwards my phone's wifi stopped working (cannot be turned on or off, with the status of "Turning Wifi On"). The phone also reboots itself after around 1 minute.
I have a bad flash, now whenever I update to Lollipop, my wifi stops working and I get nonstop reboots. Phone is perfectly fine when I stay in KK
and I have lost my IMEI
Tried methods:
- I have tried erasing the phone by going into the backup and reset menu to reset the phone,the same problems remain.
- I have tried clearing the phone by erasing data and catch from stock recovery, the same problems remain.
- I have tried using the Muti-Tool to revert back to stock. but then the phone restarts every time before adb can do anything
- I have tried using RSD, flashing the Brazilian XT1097 .img into the phone. Despite a successfully flash, the same problems remain.
Problem:
- Phone's wifi is stuck
- Phone keeps rebooting (safe mode or not)
- When phone is powered off, it will restart itself and then go on the reboot loop again (even when i boot into safe mode and turn it off form there)
- Phone does not turn off without rebooting itself other than powering off from Recovery
- Phone Cannot be charged
Help needed!
I really messed my phone up and need help! Please can someone suggest a solution? I dont have TWRP so I cannot wipe system and reinstall
Motosurf
BlueEditionE6 said:
After I got back form vacation, I reverted my phone back to stock recovery and 4.4.4
Click to expand...
Click to collapse
It is dangerous to downgrade a Moto X. This is not a Nexus device.
---------- Post added at 03:59 AM ---------- Previous post was at 03:57 AM ----------
BlueEditionE6 said:
I dont have TWRP so I cannot wipe system and reinstall
Click to expand...
Click to collapse
Press and hold the power button to shut it off and then immediately press and hold the vol down and then press and hold power. Hold both for about 4 seconds and release. This should put you into fastboot mode. Then plug the device into your computer and start Motorola Device Manager.
---------- Post added at 04:00 AM ---------- Previous post was at 03:59 AM ----------
BlueEditionE6 said:
ps. the phone's battery is so low that it cant do anything. Wondering if the phone charges in Recovery mode. Battery status says charging, but I am not sure?
Click to expand...
Click to collapse
Do you have a turbo charger or know anyone who does?
JulesJam said:
It is dangerous to downgrade a Moto X. This is not a Nexus device.
---------- Post added at 03:59 AM ---------- Previous post was at 03:57 AM ----------
Press and hold the power button to shut it off and then immediately press and hold the vol down and then press and hold power. Hold both for about 4 seconds and release. This should put you into fastboot mode. Then plug the device into your computer and start Motorola Device Manager.
---------- Post added at 04:00 AM ---------- Previous post was at 03:59 AM ----------
Do you have a turbo charger or know anyone who does?
Click to expand...
Click to collapse
yea i wasnt having trouble getting into fastbootmode. And turns out the phone does charge while in recovery
BlueEditionE6 said:
yea i wasnt having trouble getting into fastbootmode. And turns out the phone does charge while in recovery
Click to expand...
Click to collapse
OK so did you reflash system?
JulesJam said:
OK so did you reflash system?
Click to expand...
Click to collapse
reflashed KK, when i update to L, it does the same thing again.
BlueEditionE6 said:
reflashed KK, when i update to L, it does the same thing again.
Click to expand...
Click to collapse
Are you taking the OTA to get back to L? And if so, are you completely stock when you take the OTA?
JulesJam said:
Are you taking the OTA to get back to L? And if so, are you completely stock when you take the OTA?
Click to expand...
Click to collapse
Reverted to KK from the multi-tool and used the ota (XT1095), as well as reverted back to KK and used the xt1097 ota. same issue. I cannot find the XT1097 KK img
BlueEditionE6 said:
Reverted to KK from the multi-tool and used the ota (XT1095), as well as reverted back to KK and used the xt1097 ota. same issue. I cannot find the XT1097 KK img
Click to expand...
Click to collapse
If you are not completely stock 100%, it is best not to take the OTA b/c the OTA is a patch.
I would revert back to whatever version of KK system you did before, and also have a stock recovery. Then use Motorola Device Manager to get back to L. MDM should flash the correct version of system for your device.
Do you have MDM on your computer?
JulesJam said:
If you are not completely stock 100%, it is best not to take the OTA b/c the OTA is a patch.
I would revert back to whatever version of KK system you did before, and also have a stock recovery. Then use Motorola Device Manager to get back to L. MDM should flash the correct version of system for your device.
Do you have MDM on your computer?
Click to expand...
Click to collapse
Motorola Device Manager? Does it work like that ? No the problem is I dont have my original firmware, The web does not seem to have victara_retca.retca.en.ca.tkpca. kk nor L. Put up a seperate post asking if anyone has it on xda and on MotoFirmware
BlueEditionE6 said:
Motorola Device Manager? Does it work like that ? No the problem is I dont have my original firmware, The web does not seem to have victara_retca.retca.en.ca.tkpca. kk nor L. Put up a seperate post asking if anyone has it on xda and on MotoFirmware
Click to expand...
Click to collapse
Motorola Device Manager should download it and install it to your phone if you flash back to kit kat and then run MDM with your phone connected to your computer.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Also, you will end up with a copy of the firmware on your computer in :
c:\programdata\motorola\sue\firmwares
JulesJam said:
Motorola Device Manager should download it and install it to your phone if you flash back to kit kat and then run MDM with your phone connected to your computer.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Also, you will end up with a copy of the firmware on your computer in :
c:\programdata\motorola\sue\firmwares
Click to expand...
Click to collapse
just to be sure, even if i flash into a 1095 kk, mdm would flash me back to 1097?
BlueEditionE6 said:
just to be sure, even if i flash into a 1095 kk, mdm would flash me back to 1097?
Click to expand...
Click to collapse
You have to flash the stock Telus firmware.
Use rsdlite or mfastboot to return your phone to stock 5.0.1.
You can download it here: (yes it will take a few hours)
http://www.filefactory.com/file/7hv608q62qc5/RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip
Steve-x said:
You have to flash the stock Telus firmware.
Use rsdlite or mfastboot to return your phone to stock 5.0.1.
You can download it here: (yes it will take a few hours)
http://www.filefactory.com/file/7hv608q62qc5/RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip
Click to expand...
Click to collapse
OH WOW THANKS! i have been looking for this all along!
BlueEditionE6 said:
just to be sure, even if i flash into a 1095 kk, mdm would flash me back to 1097?
Click to expand...
Click to collapse
All you can do is try, you have flashed back to KK before so you know it doesn't brick your phone. I am only talking about flashing the SYSTEM (system.img) back to kit kat, not the bootloader or the partition table. If you have a custom recovery, I don't think it will work though. I think you need a stock recovery. The recovery can be lollipop.
When I flash my Verizon XT1096 back to kitkat system, with lollipop stock recovery, MDM will flash my system back to lollipop.
I understand about the issue with the different models, and I can't tell you whether MDM will have a problem with that or not, but if it does, it will just do nothing. You have flashed back to XT1095 KK before so I don't see why it would hurt to see what MDM does. It will be able to tell you have an XT1097 so it won't try to install a system for an XT1095.
Steve-x said:
You have to flash the stock Telus firmware.
Use rsdlite or mfastboot to return your phone to stock 5.0.1.
You can download it here: (yes it will take a few hours)
http://www.filefactory.com/file/7hv608q62qc5/RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip
Click to expand...
Click to collapse
Hi steve, I am getting "Failed flashing process. 3/21 flash partition "gpt.bin" -> Phone returned FAIL
Did i do something wrong?
EDIT: replaced the gpt file and the motoboot file with the 5.0.1 file.
EDIT 2: at 4.4.4 rectca, imei and radio is back, but there is no update to L, if I rsd the 5.0.1 rectca, the same issue comes back
What else have you all flashed, if you tried the 5.1 soak you likely will have to skip flashing gpt and motoboot.
Steve-x said:
What else have you all flashed, if you tried the 5.1 soak you likely will have to skip flashing gpt and motoboot.
Click to expand...
Click to collapse
I have tried flashing the 5.0 update front the multi tool. I tried removing get and process stopped
Sent from my XT1080 using XDA Premium 4 mobile app
Well I really feel like there is something you're not telling us that you've done in the past to the phone. Please try to give detailed answers.
#1 - Are you 100% sure it is a Telus phone and not a Wind Mobile XT1097?
#2 - When flashing the Telus 5.0.1 image what does the phone say when the process fails?
#3 - You mention flashing 4.4.4 - do you mean a full image or just some of the files like you are mixing and matching some 4.4.4 and some 5.0.1?
#1 - Are you 100% sure it is a Telus phone and not a Wind Mobile XT1097?
No, I won this poem from Motorola and it arrived to my doorsteps unlocked. It might be on Wind, sorry I didn't think of this possibility
#2 - When flashing the Telus 5.0.1 image what does the phone say when the process fails?
The process doesn't fail while fishing to L, it only failed when I tried to flash it from the broken L to KK. When my phone is on L, the wifi, signal doesn't work, and it reboots. As shown in the video
https://youtu.be/pDCCr2BE4n0
#3 - You mention flashing 4.4.4 - do you mean a full image or just some of the files like you are mixing and matching some 4.4.4 and some 5.0.1?[/QUOTE]
Well like I said I tried flashing the KK that you linked to me, but then it gets stuck at gpt and motoboot. So I got the two files from the L zip and KK flashes successfully. Works like a charm too. Other than that fact that it doesn't update
Extra info. I have had TWRP and CM12.1 just because it was the only way for the phone to charge
Sent from my XT1080 using XDA Premium 4 mobile app
It all sounds pretty weird. I suspect the phone may actually be a Wind mobile retail edition. They come factory unlocked, the Telus version would be locked.
The link I gave was Lollipop 5.0.1 for the Telus version. Being I think you have the Wind mobile here is the link for the Wind mobile 4.4.4:
http://www.filefactory.com/file/38yhbfahth0p/RETCA_XT1097_4.4.4_KXE21.187-52_cid14_CFC.xml.zip
When you download the file and try to flash using rsdlite gpt and motoboot will fail as they cannot be downgraded. This is not a problem. Just edit the xml file to remove them and then flash the entire package with rsdlite. When done you will be on factory 4.4.4. At that point you should get prompted to update to 5.0.1.