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?
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?
Hi All! I've installed the rooted stock 4.4.4 image that @gokart2 has made available (great work, btw!) and it's working great, except for one thing -- the built-in version of Titanium Backup is having problems reading my license file, and even after buying the PRO version from the play store, it still doesn't make any of the PRO/donate features available. Is anybody else having this problem or know how to fix it?
Thanks!
Dave
RobinATL said:
Hi All! I've installed the rooted stock 4.4.4 image that @gokart2 has made available (great work, btw!) and it's working great, except for one thing -- the built-in version of Titanium Backup is having problems reading my license file, and even after buying the PRO version from the play store, it still doesn't make any of the PRO/donate features available. Is anybody else having this problem or know how to fix it?
Thanks!
Dave
Click to expand...
Click to collapse
Did you try uninstalling TiB/U and the Pro key and then reinstalling them from the playstore?
Wansanta said:
Did you try uninstalling TiB/U and the Pro key and then reinstalling them from the playstore?
Click to expand...
Click to collapse
Because @gokart2 made it built-in, you can't uninstall it, at least I haven't found a way to do it yet.
RobinATL said:
Because @gokart2 made it built-in, you can't uninstall it, at least I haven't found a way to do it yet.
Click to expand...
Click to collapse
Is your bootloader unlocked?
Wansanta said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes
RobinATL said:
Yes
Click to expand...
Click to collapse
is there some reason you need to use a rooted stock image? Why not just root your phone by hand? It takes all of 10 minutes to do it and you can install TiBU from the playstore and it will work fine.
Wansanta said:
is there some reason you need to use a rooted stock image? Why not just root your phone by hand? It takes all of 10 minutes to do it and you can install TiBU from the playstore and it will work fine.
Click to expand...
Click to collapse
Because when I went looking for a stock image to revert to from the CM11 nightly, that was the only one that I could find. If you can point me to a fully stock version of 4.4.4 for the Sprint 1st Gen, I'd be happy to flash that
RobinATL said:
Because when I went looking for a stock image to revert to from the CM11 nightly, that was the only one that I could find. If you can point me to a fully stock version of 4.4.4 for the Sprint 1st Gen, I'd be happy to flash that
Click to expand...
Click to collapse
Just checked here and it looks like 4.4.2 is the last sbf for Sprint. Has Sprint Moto X not been updated to 4.4.4 yet?
According to Sprint, 4.4.4 was released on 8/20/2014
RobinATL said:
According to Sprint, 4.4.4 was released on 8/20/2014
Click to expand...
Click to collapse
OK, well I don't know why there is no sbf yet. I know a poster here would make unofficial FXZs before the SBFs were released but I don't know how he did it.
I think I am going to test returning to stock 4.4.2 after having my bootloader upgraded to 4.4.4 and then either taking the 4.4.4 OTA or using the Motorola Device Manager to update me to 4.4.4 on an unlocked Verizon device. If it works I will let you know.
I still have to make sure I understand how the OTA updater script works versus Motorola Device Manger b/f I do it.
I have a 4.4.2 rooted nandroid that I can return to and unroot. Do you have any nandroids of your system on 4.4.2?
Edited - just found what I was looking for:
http://forum.xda-developers.com/showpost.php?p=50721066&postcount=18
Q9Nap said:
you CAN reapply the ota after flashing back to 4.4. the updater script sees that the motoboot parts and gpt are already upgraded and just skips them; you will not brick.
Click to expand...
Click to collapse
Sprint 4.4.4 fxz:
http://www.filefactory.com/file/6ti...4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
all thanks to daywalker04
Q9Nap said:
Sprint 4.4.4 fxz:
http://www.filefactory.com/file/6ti...4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
all thanks to daywalker04
Click to expand...
Click to collapse
Thanks - can you confirm for me that I can revert back to a 4.4.2 nandroid and take the 4.4.4 OTA again on Verizon unlocked bootloader? I know I can go back to my 4.4.2 nandroid after upgrading to 4.4.4 b/c I have done it several times. When I do, presumably everything goes back to 4.4.2 but the bootloader and partition table, which stay on 4.4.4. And since the OTA updater script will see that I am on 4.4.4 bootloader and partition table, it will just skip patching those and just patch the files that are on 4.4.2., so I can take the 4.4.4 OTA again, correct?
Thanks!
Wansanta said:
Thanks - can you confirm for me that I can revert back to a 4.4.2 nandroid and take the 4.4.4 OTA again on Verizon unlocked bootloader? I know I can go back to my 4.4.2 nandroid after upgrading to 4.4.4 b/c I have done it several times. When I do, presumably everything goes back to 4.4.2 but the bootloader and partition table, which stay on 4.4.4. And since the OTA updater script will see that I am on 4.4.4 bootloader and partition table, it will just skip patching those and just patch the files that are on 4.4.2., so I can take the 4.4.4 OTA again, correct?
Thanks!
Click to expand...
Click to collapse
yes.
you just quoted me saying that in post #10 of this thread; am i missing something?
why would you want to bother with the 4.4.4 ota when the 4.4.4 fxz is available?
Q9Nap said:
yes.
Click to expand...
Click to collapse
Q9Nap said:
you just quoted me saying that in post #10 of this thread; am i missing something?
Click to expand...
Click to collapse
Sorry those quotes were from other threads - I was just quoting you b/c I have never done these things myself yet and I am going off of what you were saying and you were saying it in those posts better than I could and so I quoted you. I just wanted to make sure I understood what you were saying b/c a lot of people here claim you will brick your device if you do that. I don't think that is true just confirming it.
Q9Nap said:
why would you want to bother with the 4.4.4 ota when the 4.4.4 fxz is available?
Click to expand...
Click to collapse
Because when I was on 4.4.2 rooted, I did a nandroid but then flashed the 4.4.2 system and recovery to return to stock and then took the 4.4.4 OTA. Then when I went to restore my texts messages using Titanium Backup from my 4.4.2 nandroid, it restores them perfectly BUT I can no longer receive texts. I can send texts fine, but I can't receive them.
When I restored my texts I selected data only and also had the correct settings in preferences but for whatever reason no one has been able to tell me, Titanium B/U messes with the 4.4.4 messanging app or maybe my APNs? Idk, but I have reproduced this about 5 times now everytime it is exactly the same - I cannot receive texts after restoring my texts from my 4.4.2 nandroid.
I then tried SMS b/u and restore and it can't restore all of my old texts. So now I want to go back to my 4.4.2 nandroid, unroot, return to stock recovery and then take the 4.4.4 OTA to keep my texts. I can't think of any other way to do it.
Wansanta said:
Sorry those quotes were from other threads - I was just quoting you b/c I have never done these things myself yet and I am going off of what you were saying and you were saying it in those posts better than I could and so I quoted you. I just wanted to make sure I understood what you were saying b/c a lot of people here claim you will brick your device if you do that. I don't think that is true just confirming it.
Because when I was on 4.4.2 rooted, I did a nandroid but then flashed the 4.4.2 system and recovery to return to stock and then took the 4.4.4 OTA. Then when I went to restore my texts messages using Titanium Backup from my 4.4.2 nandroid, it restores them perfectly BUT I can no longer receive texts. I can send texts fine, but I can't receive them.
When I restored my texts I selected data only and also had the correct settings in preferences but for whatever reason no one has been able to tell me, Titanium B/U messes with the 4.4.4 messanging app or maybe my APNs? Idk, but I have reproduced this about 5 times now everytime it is exactly the same - I cannot receive texts after restoring my texts from my 4.4.2 nandroid.
I then tried SMS b/u and restore and it can't restore all of my old texts. So now I want to go back to my 4.4.2 nandroid, unroot, return to stock recovery and then take the 4.4.4 OTA to keep my texts. I can't think of any other way to do it.
Click to expand...
Click to collapse
Hmm, did you at any point switch from stock mms app to hangouts app for sms?
Maybe go back to working config and switch to hangouts for sms, then reply to the texts through hangouts so they are backed up that way.
Not sure this will work, but worth a shot...
I don't have a problem with you quoting me, just don't understand why you were asking for verification.
Q9Nap said:
Hmm, did you at any point switch from stock mms app to hangouts app for sms?
Click to expand...
Click to collapse
I did but then I undid that and same result. Then I restored from a 4.4.4 nandroid that was made before I did that. After restoring my texts again using TiBU, still the same problem.
But if I restored using SMS B/U and Restore, I could send and receive texts but SMSBU&R can't restore all of my texts for me nor can it tell me which texts it can't restore. It just tells me the number that it can't restore.
Clearly TiBU is doing more than just restoring my texts but I can't figure out what it is doing.
Q9Nap said:
I don't have a problem with you quoting me, just don't understand why you were asking for verification.
Click to expand...
Click to collapse
Because you are the only poster here who will say you won't brick if you downgrade your system after upgrading your bootloader and who will say that trying to downgrade the partition table and bootloader won't brick, it will just fail. Everyone else tells people they will brick. I just wanted to confirm that I really understood what you were saying b/c what you are saying is the complete opposite of what every other person here who gives advice says.
The others just say across the board - downgrading or attempting to downgrade will brick.
I realize that your comments are specific to those with unlocked bootloaders, but others here will make no distinction and say across the board that you will brick if you attempt to downgrade or if you upgrade then go back to an earlier system and then take the OTA.
Basically what has happened is a guy who used to post here and no longer does said that even those with unlocked bootloaders can't downgrade without bricking, which is false, but it has been repeated here so many times in all of the stickies and so many threads that people think it is true and just keep repeating it and repeating it and repeating it.
I just needed more reassurance that I understood you correctly given that others have posted misinformation here repeatedly to the point it is now accepted as fact when it is not true. Thanks.
Q9Nap said:
I don't have a problem with you quoting me, just don't understand why you were asking for verification.
Click to expand...
Click to collapse
SUCCESS!!! Kind of.
I returned to my 4.4.2 nandroid, disabled the Xposed Installer, flashed the stock recovery, unfroze all of the apps I had frozen, including Motorola OTA, and unrooted. Then I took the 4.4.4 OTA again and had all of my texts, woot!!
HOWEVER, I still can't receive texts!!!!!! I found this thread on AC and it seems like others have this problem too after taking the 4.4.4 OTA. Drats. At least now I know it isn't TiBU.
Well at least I know I can downgrade and take an OTA fine.
RobinATL said:
Hi All! I've installed the rooted stock 4.4.4 image that @gokart2 has made available (great work, btw!) and it's working great, except for one thing -- the built-in version of Titanium Backup is having problems reading my license file, and even after buying the PRO version from the play store, it still doesn't make any of the PRO/donate features available. Is anybody else having this problem or know how to fix it?
Thanks!
Dave
Click to expand...
Click to collapse
I apologize for just seeing this. You should have PM'd me, I would have walked you through it. All you need to do is download a file explorer app (like ES file explorer), and go to system/app/com.keramidas.TitaniumBackup.apk and delete it. Then re-install from the play store.
Q9Nap said:
Sprint 4.4.4 fxz:
http://www.filefactory.com/file/6ti...4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
all thanks to daywalker04
Click to expand...
Click to collapse
I don't know if it was a bad DL, since I only tried the free DL option, but it wouldn't let me run the zip using TWRP. i did the normal wipes and it failed. do I need to do something different?
agentcelsius said:
I don't know if it was a bad DL, since I only tried the free DL option, but it wouldn't let me run the zip using TWRP. i did the normal wipes and it failed. do I need to do something different?
Click to expand...
Click to collapse
This isn't a flashable zip, it's a collection of fastboot partition images a.k.a Fastboot Xml Zip (FXZ). There are many tutorials on how to use them...
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
timmytron said:
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
Click to expand...
Click to collapse
Oh god are you on the US version (SGH-I537)? If you're on the international version (I9295) ignore this post but otherwise, you need to read and take in my short rant. Trust me I wish this weren't the case, but it is, and it's important:
The Galaxy S4 Active i537 has a locked bootloader. There is no way around this, no ifs ands or buts. You simply cannot flash custom ROMs or recoveries. That's it, end of story as far as CM, CWM, AOSP and such things are concerned. That being said there is a sort of recovery called SafeStrap which you can use to make nandroid backups, flash mods and STOCK-BASED roms, but it's not a true custom recovery in the sense that we had been used to, because of this locked bootloader nightmare.
OK so I think you're gonna want to check out this thread. It's all about how to install any firmware from download mode, I think you're gonna have to go with NE3 or NH3.
Let me reiterate. NO CUSTOM ROMS. NO CWM. No Paranoid, no cyanogenmod, no AOSP, no crossing go before going directly to jail. Sorry for the stupid joke but seriously, you have got to keep your phone on stock-based roms (of which there are unfortunately few).
Firmware download links
timmytron said:
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
Click to expand...
Click to collapse
What phone do you have (i537 or i9295) and what version of firmware were you on?
Devo7v said:
What phone do you have (i537 or i9295) and what version of firmware were you on?
Click to expand...
Click to collapse
i537 and second to last, I537UCUCNE3
Okay, :laugh: I'm back. FINALLY found some MD5 files that loaded. In the process of updating and putting things back they way they were. Thank you to all who viewed/helped!
Is there a way to mark this as "Resolved"?
Web browser login, edit, advanced.
Add "solved" to title?
same problem with my i537, need help
timmytron said:
Okay, :laugh: I'm back. FINALLY found some MD5 files that loaded. In the process of updating and putting things back they way they were. Thank you to all who viewed/helped!
Is there a way to mark this as "Resolved"?
Click to expand...
Click to collapse
Need help, having the same problem
baddhabbitz88 said:
Need help, having the same problem
Click to expand...
Click to collapse
Have you used ODIN before?
i537 Stuck in download mode
timmytron said:
Have you used ODIN before?
Click to expand...
Click to collapse
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
baddhabbitz88 said:
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
Click to expand...
Click to collapse
Okay. Well I'm not sure where I got the files either. What I'm going to do is upload them (please do keep in mind that it's a huge file) to my Drive account and I will link it here when complete. You are on the AT&T i537 version?
baddhabbitz88 said:
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
Click to expand...
Click to collapse
Did you get my PM?
timmytron said:
Okay. Well I'm not sure where I got the files either. What I'm going to do is upload them (please do keep in mind that it's a huge file) to my Drive account and I will link it here when complete. You are on the AT&T i537 version?
Click to expand...
Click to collapse
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
baddhabbitz88 said:
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
Click to expand...
Click to collapse
Well AT&T decided to completely lock us out on this particular version on this particular phone. At least we have *ROOT*.
baddhabbitz88 said:
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
Click to expand...
Click to collapse
You need to make sure you are flashing a version that is the same or more recent than the version you are currently on. You cannot downgrade your firmware or else you'll end up with a bootloop.
Devo7v said:
You need to make sure you are flashing a version that is the same or more recent than the version you are currently on. You cannot downgrade your firmware or else you'll end up with a bootloop.
Click to expand...
Click to collapse
k will try to find a more updated version but that is part of the problem is locating the firmware I need + this started doing it on its own and really never dug into it to no which firmware was on it other than rooted months ago with towelroot
---------- Post added at 09:36 PM ---------- Previous post was at 09:04 PM ----------
timmytron said:
Did you get my PM?
Click to expand...
Click to collapse
yeah I got it thanks but it didn't work still digging
baddhabbitz88 said:
k will try to find a more updated version but that is part of the problem is locating the firmware I need + this started doing it on its own and really never dug into it to no which firmware was on it other than rooted months ago with towelroot
---------- Post added at 09:36 PM ---------- Previous post was at 09:04 PM ----------
yeah I got it thanks but it didn't work still digging
Click to expand...
Click to collapse
Always check the stickies.
http://forum.xda-developers.com/showthread.php?t=2892445
Hi !
I have a big trouble with my Moto X since I bricked it after trying to update the OS.
I was on LP 5.0 and I saw somewhere that an update was available so I searched for that and launched the update.
The problem was I didn't know that it's dangerous to do so with a rooted phone...
So, now, my Moto X is staying on the "splash screen" and if I force the power off, the Moto X restarts... and stays on the splash screen, again...
Is someone can help me to unbricked my phone ?
Thank you very much for your help :highfive:
A+
Edit : for information, it's a French Moto X 2014 (so I think it's a XT1052)
Smh
Can you get into fastboot? From off, hold volume down and touch the power for a second and continue holding volume down.
kcustom11 said:
Can you get into fastboot? From off, hold volume down and touch the power for a second and continue holding volume down.
Click to expand...
Click to collapse
Yes, but I don't remember if I update the bootloader.
The choices I have are :
- Normal powerup
- Recovery
- Factory
- Barcodes
- BP Tools
- QCOM
Thank you for your help
You're not bricked then. I don't know what the recovery instructions are for the French model. Do they have factory images on the support page?
You can volume up on recovery to get into recovery to see options about clear cache and factory reset. Those might help, but I doubt it. I would try.
If you care about your data you can adb pull in recovery to get stuff off your sdcard before you factory reset.
benjo22 said:
Yes, but I don't remember if I update the bootloader.
The choices I have are :
- Normal powerup
- Recovery
- Factory
- Barcodes
- BP Tools
- QCOM
Thank you for your help
Click to expand...
Click to collapse
What model phone do you have XT1092? Do you have the 5.0 system.img for your phone?
kcustom11 said:
You're not bricked then. I don't know what the recovery instructions are for the French model. Do they have factory images on the support page?
You can volume up on recovery to get into recovery to see options about clear cache and factory reset. Those might help, but I doubt it. I would try.
If you care about your data you can adb pull in recovery to get stuff off your sdcard before you factory reset.
Click to expand...
Click to collapse
I don't know if I they have the factory image. Cna you tell where I could get it ? (or where I need to search ?)
Actually, I have a back of my data so I don't care about it. So can you tell me how to use ADB in order to do a factory reset? (ADB is already installed)
JulesJam said:
What model phone do you have XT1092? Do you have the 5.0 system.img for your phone?
Click to expand...
Click to collapse
I think you're right and the French model is 1092 and not 1095 as I thought. But I don't have the system.img...
it looks like motorola didn't post images for models other than the PE xt1095. try the factory reset in recovery. if that doesn't work.
try this.
http://forum.xda-developers.com/mot...tory-image-android-5-0-lollipop-moto-t3001221
kcustom11 said:
it looks like motorola didn't post images for models other than the PE xt1095. try the factory reset in recovery. if that doesn't work.
try this.
http://forum.xda-developers.com/mot...tory-image-android-5-0-lollipop-moto-t3001221
Click to expand...
Click to collapse
Thank you, but in your opinion, there is no other way to fixe my problem ? I'm a little scared of flashing a new image, mainly because I'm not sur at 100% that it's a XT1092.
benjo22 said:
I think you're right and the French model is 1092 and not 1095 as I thought. But I don't have the system.img...
Click to expand...
Click to collapse
You should search for it online and post in the Motorola forums that their OTA messed up your system and ask them for the files. And email and chat and ask them that way too.
---------- Post added at 01:10 AM ---------- Previous post was at 01:09 AM ----------
benjo22 said:
Thank you, but in your opinion, there is no other way to fixe my problem ? I'm a little scared of flashing a new image, mainly because I'm not sur at 100% that it's a XT1092.
Click to expand...
Click to collapse
Put your phone in bootloader mode, connect to your computer and start Motorola Device Manager to see if MDM can repair your phone.
Go into recovery (volume up to select). Try a factory reset and clear the cache first. Attempt to reboot.
Then follow JulesJam advice and try MDM
In the bootloader, the bar code option will tell you your phone version to see if you have the XT1092 (volume up to select)
If that doesn't work, you'll have to go to the link I gave you and flash the 1092 images.
or send it back to motorola
kcustom11 said:
or send it back to motorola
Click to expand...
Click to collapse
I don't think that is how it works outside the US. I think they have to send it to service centers where they decide whether or not it is a warranty issue and if you have rooted or unlocked the bootloader, they refuse the warranty service. At least that is how it is in Brazil.
AFAIK, only the Pure Edition maintains its warranty if you unlock and root.
I know with my XT1096, the qe is now 1/1 after MoFo so I worry that I couldn't get warranty services for it. Good thing I have MotoCare and if I end up with a problem, I am just dropping it in a bucket of water so that it can't be turned on again and paying the $39 deductible.
I didn't say it was on warranty. That's why it should be the last option. I imagine Motorola owns the service centers so you would still be sending it to Motorola.
I wouldn't worry too much about flashing those images. It should work if nothing else does. I think there's also another forum about how to convert the 1092 to a 1095. You can do that if you really want the 5.1 right away. You have to be mindful of the radios though.
kcustom11 said:
I didn't say it was on warranty.
Click to expand...
Click to collapse
But if it isn't on warranty and you are not w/in the 14 day return period, then you have to pay for service.
---------- Post added at 02:31 AM ---------- Previous post was at 02:21 AM ----------
kcustom11 said:
I imagine Motorola owns the service centers so you would still be sending it to Motorola.
Click to expand...
Click to collapse
Idk but it didn't seem that way with the Brazilian phones but maybe.
JulesJam said:
But if it isn't on warranty and you are not w/in the 14 day return period, then you have to pay for service.
Click to expand...
Click to collapse
Obviously
Let me tell you first that it isn't bricked yet, This thing is happening only because you tried to update your device with a custom recovery, to solve the issue you have to go on stock recovery and on the stock Rom as well. That's it and it will work again..
But keep in mind never downgrade, i mean don't flash a lower Rom than what you are on right now otherwise it may surely result in a Bricked Phone:what:
Sent from my XT1052
kcustom11 said:
Obviously
Click to expand...
Click to collapse
well then I wouldn't advise sending it back, I would try to fix it myself since it is just software.
---------- Post added at 02:48 AM ---------- Previous post was at 02:47 AM ----------
vijayid_94 said:
Let me tell you first that it isn't bricked yet, This thing is happening only because you tried to update your device with a custom recovery, to solve the issue you have to go on stock recovery and on the stock Rom as well. That's it and it will work again..
But keep in mind never downgrade, i mean don't flash a lower Rom than what you are on right now otherwise it may surely result in a Bricked Phone:what:
Sent from my XT1052
Click to expand...
Click to collapse
The problems are when you try to downgrade the bootloader and/or partition table or when you downgrade after upgrading and then take an OTA.
Thanks to everyone !
I think that I will try to flash the image because using the MDM doesn't fix anything. But it was written that my current version is :"22.121.1.victara_oraeu.oraeuall.en.eu".
Furthemore, I had this problem when I was trying to install an update. Do you think it's a downgrade if I flash the available version of system.img ? And consequently I risk a real brick ?
Edit : an other question : on the tutorial that explain how to flash a img, it's written that we need to use "Motorola fastboot utility " and not the Android fastboot utility. I installed the sdk android and the MDM program, but the sole fastboot program a have is the android one. Do you know where I can find the Motorola fastboot utility ?
Thanks again )
Hi everyone !
Finally, I decided to launch the flash with the stock rom for XT1092. And it perfectly worked !
I still have a two questions :
- why I don't have anymore the update Moto proposed me at the benining ? Moreover the stock flashed seems to be an old one.
- In the futur, if a need to do an update, how can I do to avoid this problem ?
Thank you very much once again )
benjo22 said:
Hi everyone !
Finally, I decided to launch the flash with the stock rom for XT1092. And it perfectly worked !
I still have a two questions :
- why I don't have anymore the update Moto proposed me at the benining ? Moreover the stock flashed seems to be an old one.
- In the futur, if a need to do an update, how can I do to avoid this problem ?
Thank you very much once again )
Click to expand...
Click to collapse
What Android Version are you running - go to settings and find out the android version. Also, what bootloader version are you running - put the device in bootloader mode, it is a number beginning with a 60.