Related
Is it possible to deploy the Moto X DE image on Moto X AT&T (X1508) device?
THX
No. Not without unlocking the bootloader, which is unpossible.
Root is not enough?
gunnyman said:
No. Not without unlocking the bootloader, which is unpossible.
Click to expand...
Click to collapse
I can root it, will not work?
zivoro said:
I can root it, will not work?
Click to expand...
Click to collapse
No, rooting is not sufficient.
The AT&T SW, mainly AT&T contacts, drive me nuts...
Must clean it.
gunnyman said:
No. Not without unlocking the bootloader, which is unpossible.
Click to expand...
Click to collapse
Um, I don't believe that to be true.
The Dev Edition ROM and the "consumer edition" rom appear to be the exact same.
They are both signed, and will not impact the bootloader status.
KidJoe said:
Um, I don't believe that to be true.
The Dev Edition ROM and the "consumer edition" rom appear to be the exact same.
They are both signed, and will not impact the bootloader status.
Click to expand...
Click to collapse
Go ahead and try it then.
Firmwares are signed for the devices they are meant for. Unlocking the bootloader bypasses this check.
KidJoe said:
Um, I don't believe that to be true.
The Dev Edition ROM and the "consumer edition" rom appear to be the exact same.
They are both signed, and will not impact the bootloader status.
Click to expand...
Click to collapse
You need an unlocked bootloader to flash factory images.
gunnyman said:
Go ahead and try it then.
Firmwares are signed for the devices they are meant for. Unlocking the bootloader bypasses this check.
Click to expand...
Click to collapse
Dev X on Verizon and "Consumer"/MotoMaker X on Verizon are both XT1060. So if roms are signed for the devices they are meant for, they are both signed for XT1060.
The only difference is the ability to unlock the boot loader or not. And this can't be changed by the ROM you flash.
As a test, would you agree that the "VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip" from http://sbf.droid-developers.org/ghost/list.php is the "Consumer" edition of the ROM?
---------- Post added at 10:37 AM ---------- Previous post was at 10:32 AM ----------
kzoodroid said:
You need an unlocked bootloader to flash factory images.
Click to expand...
Click to collapse
And what are these? -> http://sbf.droid-developers.org/ghost/list.php
They are factory images, properly signed by Moto, that can be flashed to devices with locked or unlocked bootloaders.
My bootloader is unlocked so I can't test but the ones directly from the moto site are "dev" recovery images. They might be signed differently (like the engineering builds). The ones on sbf droid are retail files and will work fine for their proper device but cannot be shifted to another.
Ex: vzw images will not work on an att device. (however they will work if you have a Dev edition)
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Sent from my XT1060 using Tapatalk
Look. There's a check done by either the hardware or the software image that prevents flashing firmware meant for one phone on a different phone. If it worked don't you think there would be threads explaining how to do it? It doesn't work. There is no way to flash firmware meant for the dev edition moto x on the at&t moto x.
KidJoe said:
[/COLOR]And what are these? -> http://sbf.droid-developers.org/ghost/list.php
They are factory images, properly signed by Moto, that can be flashed to devices with locked or unlocked bootloaders.
Click to expand...
Click to collapse
Where does it say they can be flashed without an unlocked bootloader? That site just looks like a repository for firmware and OTA's. Even a Nexus device you can't flash firmware in fastboot without an unlocked bootloader.
kzoodroid said:
Where does it say they can be flashed without an unlocked bootloader? That site just looks like a repository for firmware and OTA's. Even a Nexus device you can't flash firmware in fastboot without an unlocked bootloader.
Click to expand...
Click to collapse
The many threads here on XDA of users with locked boot loaders using them to flash back to 4.2.2, or to prep for the KK update. ANd those are full ROM files, not OTA updates.
---------- Post added at 11:24 AM ---------- Previous post was at 11:03 AM ----------
gunnyman said:
Look. There's a check done by either the hardware or the software image that prevents flashing firmware meant for one phone on a different phone. If it worked don't you think there would be threads explaining how to do it? It doesn't work. There is no way to flash firmware meant for the dev edition moto x on the at&t moto x.
Click to expand...
Click to collapse
Not sure where the checks exactly are, as the XML and RSD will just start flashing.
However, as an example, the files being flashed from VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip are exactly the same as those in MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip. Same when doing a FC /B, and the MD5 listed in the respective XML files.
Granted, the GSM Dev Edition and ATT version do support different bands, so have different radio code in their roms.
As for flashing a rom meant for another model, well people with locked boot loaders HAVE cross flashed parts (and in some cases all) of firmwares meant for other phones using fastboot... Example a few posts in -> http://forum.xda-developers.com/showthread.php?t=2445955 (start with the comments where the 4.4 leak appeared, as the 4.3 leak that started it was an engineering build). This was flashed onto T-Mo, ATT, and even Verizon X's. As well as -> http://forum.xda-developers.com/showthread.php?t=2517577 which talked about the leaked ATT 4.4... One post of particular note is post #38 of that thread which says "NOTE: Do not try this on VZW DE the radios will not work. Tried it." so at least one person flashed the ATT ROM on to their Verizon X.
Those aren't factory image files which the op needs to do what he wants. To flash factory images (.IMG) files requires an unlocked boot loader.
Sent from my XT1053 using xda app-developers app
kzoodroid said:
Those aren't factory image files which the op needs to do what he wants. To flash factory images (.IMG) files requires an unlocked boot loader.
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
I think you're confused. My bootloader is LOCKED. I can flash SIGNED factory images for MY PHONE just fine.
gunnyman said:
I think you're confused. My bootloader is LOCKED. I can flash SIGNED factory images for MY PHONE just fine.
Click to expand...
Click to collapse
Only the Moto X has factory images available so whatever you are flashing aren't factory images. What I am talking about here is using fastboot commands (fastboot flash boot boot.img, etc.) to install the factory images to a phone, not zip files. Fastboot flashing of factory images can only be done with an unlocked bootloader. I think what you are doing is installing a zipped rom through recovery or adb which is different.
If the OP unlocks his bootloader he will be able to flash the factory images for the dev edition onto his phone using fastboot. He will not be able to flash the dev edtion zip rom files to his phone as there is a version\compatability checker built in to those.
By the way those files on the sbf.droid-developers website are not factory images they are full rom's.
kzoodroid said:
Only the Moto X has factory images available so whatever you are flashing aren't factory images. What I am talking about here is using fastboot commands (fastboot flash boot boot.img, etc.) to install the factory images to a phone, not zip files. Fastboot flashing of factory images can only be done with an unlocked bootloader. I think what you are doing is installing a zipped rom through recovery or adb which is different.
If the OP unlocks his bootloader he will be able to flash the factory images for the dev edition onto his phone using fastboot. He will not be able to flash the dev edtion zip rom files to his phone as there is a version\compatability checker built in to those.
By the way those files on the sbf.droid-developers website are not factory images they are full rom's.
Click to expand...
Click to collapse
So am I.
I've also flashed manually on my mac. fastboot flash boot.omg fastboot flash system.img etc etc all work fine on my locked bootloader phone.
kzoodroid said:
....What I am talking about here is using fastboot commands (fastboot flash boot boot.img, etc.) to install the factory images to a phone, not zip files. Fastboot flashing of factory images can only be done with an unlocked bootloader. ...
Click to expand...
Click to collapse
Not sure I follow what you are trying to say.
read through these two threads -> http://forum.xda-developers.com/showthread.php?t=2534060 and http://forum.xda-developers.com/showthread.php?t=2525495&page=2 and see how many Verizon users with LOCKED BOOTLOADERS used FASTBOOT to flash recovery, boot, system, and in some cases NON-HLOS.bin and fsg.mbn to undo root and return to stock in preparation for the KK update...
You are saying that it can't be done??
granted, due to size of system and others, a special "motorola fastboot" was needed, because the regular fastboot.exe which comes down with the Android SDK/Platformtools can't handle files that big. But they certainly used....
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
while the phone was restarted into the fastboot menu
And if you read the other threads I linked previously, fastboot flash commands were used to flash certain components of the T-Mobile KK 4.4 leak onto NON-T-Mobile phones, including Verizon and ATT that had locked boot loaders.
KidJoe said:
The many threads here on XDA of users with locked boot loaders using them to flash back to 4.2.2, or to prep for the KK update. ANd those are full ROM files, not OTA updates.
---------- Post added at 11:24 AM ---------- Previous post was at 11:03 AM ----------
Not sure where the checks exactly are, as the XML and RSD will just start flashing.
However, as an example, the files being flashed from VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip are exactly the same as those in MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip. Same when doing a FC /B, and the MD5 listed in the respective XML files.
Granted, the GSM Dev Edition and ATT version do support different bands, so have different radio code in their roms.
As for flashing a rom meant for another model, well people with locked boot loaders HAVE cross flashed parts (and in some cases all) of firmwares meant for other phones using fastboot... Example a few posts in -> http://forum.xda-developers.com/showthread.php?t=2445955 (start with the comments where the 4.4 leak appeared, as the 4.3 leak that started it was an engineering build). This was flashed onto T-Mo, ATT, and even Verizon X's. As well as -> http://forum.xda-developers.com/showthread.php?t=2517577 which talked about the leaked ATT 4.4... One post of particular note is post #38 of that thread which says "NOTE: Do not try this on VZW DE the radios will not work. Tried it." so at least one person flashed the ATT ROM on to their Verizon X.
Click to expand...
Click to collapse
That first thread you referenced (http://forum.xda-developers.com/showthread.php?t=2445955) says right in the first post you need an unlocked bootloader. I then went 5 pages deep and saw another post which stated you have to have an unlocked boot loader to flash these. I saw one mention of pushing/pulling the images files using adb but nothing saying that worked. One other thread you linked to is about flashing a leak and you don't need an unlocked bootloader to flash a leaked rom.
What the OP wants to do is flash the factory images onto his phone and the only phone that has true factory images available from motorolla is the dev. ed. and to flash those you need to be unlocked. He can try installing one of the full ROM files for the dev ed if he likes but that is totally different than what I am talking about.
---------- Post added at 03:26 PM ---------- Previous post was at 03:08 PM ----------
KidJoe said:
Not sure I follow what you are trying to say.
read through these two threads -> http://forum.xda-developers.com/showthread.php?t=2534060 and http://forum.xda-developers.com/showthread.php?t=2525495&page=2 and see how many Verizon users with LOCKED BOOTLOADERS used FASTBOOT to flash recovery, boot, system, and in some cases NON-HLOS.bin and fsg.mbn to undo root and return to stock in preparation for the KK update...
You are saying that it can't be done??
granted, due to size of system and others, a special "motorola fastboot" was needed, because the regular fastboot.exe which comes down with the Android SDK/Platformtools can't handle files that big. But they certainly used....
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
while the phone was restarted into the fastboot menu
And if you read the other threads I linked previously, fastboot flash commands were used to flash certain components of the T-Mobile KK 4.4 leak onto NON-T-Mobile phones, including Verizon and ATT that had locked boot loaders.
Click to expand...
Click to collapse
Those threads are all Verizon developer edition phones and everything I've read says you need an unlocked boot loader. I haven't hit a post that says someone used fastboot to flash image files to a locked phone but I'm also not going to hunt thru 30 pages to find one. I go 12 pages in and see nothing mentioned and move on.
---------- Post added at 03:55 PM ---------- Previous post was at 03:26 PM ----------
Okay here I see what you are talking about http://forum.xda-developers.com/showthread.php?t=2526783. It's different than what I am talking about as those files are not the factory image files those are image files out of a ROM or a leaked ROM. It's not the same thing as taking the factory image files for the GSM dev. edition and flashing them to a non dev. edition phone. I should mention here that the factory images cannot be flashed with any recovery, they can only be installed with fastboot.
In these threads you flash the full ROM first in a custom recovery then use fastboot to flash the boot, system and recovery images out of that ROM to the phone. Flashing ROM's doesn't require an unlocked bootloader nor does flashing image files from that ROM. You're basically over writing the exact same files that are on the phone since you just installed them. What I am talking about is restoring a phone back to factory condition using the factory image files (the same images Motorolla uses to install it to the phone in the factory) not the image files from a ROM. Two different things here. Yes the OP could try and install a dev. ed. ROM with TWRP then flash the image files with fastboot but then again that's not what I am talking about and that is not guaranteed to work.
kzoodroid said:
What the OP wants to do is flash the factory images onto his phone and the only phone that has true factory images available from motorolla is the dev. ed. and to flash those you need to be unlocked. He can try installing one of the full ROM files for the dev ed if he likes but that is totally different than what I am talking about.
Click to expand...
Click to collapse
Again, the files inside the Verizon "consumer" rom, and the one you get from the Dev Web site are the SAME, the only difference is the XML in the one erases a few extra things while flashing with RSDLite.
And to flash those files Moto has for the dev edition, you do not need to have your bootloader unlocked. I've been able to flash my Verizon Moto X Dev Edition with my boot loader locked. (using both moto's fastboot, as well as RSDLite).
kzoodroid said:
Those threads are all Verizon developer edition phones and everything I've read says you need an unlocked boot loader. I haven't hit a post that says someone used fastboot to flash image files to a locked phone but I'm also not going to hunt thru 30 pages to find one. I go 12 pages in and see nothing mentioned and move on
Click to expand...
Click to collapse
Not sure where you got the idea that ALL were Dev edition owners. Those threads were for returning to "stock" so they could take the updates. Those who had boot loops and such were rooted with RockMyMoto and such, they had to root that way due to locked boot loader which made it impossible for them to flash custom recovery and flash TWRP to then install SuperSU from inside TWRP to root.. (i.e. with an unlocked bootloader you can install TWRP then install SUperSU to root, no need to use Pwnmymoto, rockmymoto or the like).
If you are basing it on the model number of the phone listed in thread poster signatures... keep in mind the Verizon X Dev Edition is the XT1060. The Verizon MotoMaker X, or the uncustomized X you get from Verizon's web site is also the XT1060.
kzoodroid said:
Okay here I see what you are talking about http://forum.xda-developers.com/showthread.php?t=2526783. It's different than what I am talking about as those files are not the factory image files those are image files out of a ROM or a leaked ROM. It's not the same thing as taking the factory image files for the GSM dev. edition and flashing them to a non dev. edition phone. I should mention here that the factory images cannot be flashed with any recovery, they can only be installed with fastboot
In these threads you flash the full ROM first in a custom recovery then use fastboot to flash the boot, system and recovery images out of that ROM to the phone. Flashing ROM's doesn't require an unlocked bootloader nor does flashing image files from that ROM. You're basically over writing the exact same files that are on the phone since you just installed them. What I am talking about is restoring a phone back to factory condition using the factory image files (the same images Motorolla uses to install it to the phone in the factory) not the image files from a ROM. Two different things here. Yes the OP could try and install a dev. ed. ROM with TWRP then flash the image files with fastboot but then again that's not what I am talking about and that is not guaranteed to work.
Click to expand...
Click to collapse
First, those threads instructing people to fastboot flash recovery, system and boot were due to them rooting with RockMyMoto and PwnMyMoto which overwrites the stock recovery to trick and give R/W. They are being instructed to flash the Recovery.IMG, Boot.IMG and System.IMG out of the downloaded SBF/FXZ ROM file. Not flash a custom recovery and then install anything from the custom recovery.
Only when it comes to Rooting a Dev Edition, or consumer edition with unlockd boot loader (like T-Mobile, Sprint or other, but NOT ATT or Verizon non-Dev), are people being instructed to flash a custom recovery (like TWRP) then install SuperSU from inside TWRP to root.
Next, can you please explain to me what you mean by "factory image" because it seems as though your thinking is different than mine. You're saying the only "factory images" that exist are for the X Dev Edition, right? And that those at http://sbf.droid-developers.org/ghost/list.php are NOT factory images, but rather ROMs.
Ok, while you help me understand what you believe the differences to be, please download the VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip from http://sbf.droid-developers.org/ghost/list.php since it is the "consumer" rom. Then visit Moto's web site https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images , and request/download the Verizon X Developer edition rom. Unzip them both to separate folders. then compare the files contained in each (hint the included XML includes the MD5 hash for each file, but you can do a FC /B in windows too). Other than the XML for the one containing the extra "erase" statements, they are the same. No difference. The XML would be opened in RSDLite to flash that way. The individual files could be flashed with moto's fastboot. Then do the same for the T-Mobile version and the GSM Developer edition roms. Again, you'll see the files contained are the same.
kzoodroid said:
Yes the OP could try and install a dev. ed. ROM with TWRP then flash the image files with fastboot but then again that's not what I am talking about and that is not guaranteed to work.
Click to expand...
Click to collapse
Actualy, no the OP can't install a dev ed rom with TWRP, as to flash a custom or recovery that hasn't been signed by moto, you need an unlocked boot loader. But the bootloader on the ATT X can't be unlocked.
Actually, at this point, there is no use for me to continue. I've said enough, and given my reasons. Feel free to disagree with me.
I am in desperate need of this firmware, currently in a bootloader loop, cannot get to recovery or anything else. Have tried flashing the original stock firmware via RSD Lite and Moto X Toolkit, but I get the following message:
Failed to hab check for gpt_main: 0x35
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer. 0xdead
No SP Partition found
Fasboot Reason: Invalid CID
Can anyone provide the firmware?
So even with bootloader you can't flash recovery and flash anything? Is your bootloader locked?
Sent from my XT1056 using Tapatalk
tjeeeeee said:
So even with bootloader you can't flash recovery and flash anything? Is your bootloader locked?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
My bootloader was unlocked, but after trying to flash a firmware via RSD Lite, I cannot flash anything and it's stuck in bootloader, and it says it's locked now. Though I never locked it. If I try to flash a system.img or boot.img or recovery.img it gives me errors about not having permissions. From what I understand I need to flash the camera update firmware, since that's what the OTA was that I was trying to install. Scoured the internet for that camera update firmware, can't find it anywhere except sbf.droid-developers.org and the site is down currently.
Have you tries unlocking the bootloader again?
Sent from my XT1056 using Tapatalk
tjeeeeee said:
Have you tries unlocking the bootloader again?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Yeah, when I do fastboot oem get-unlock-code I get a message that says "Restricted oem command" and "FAILED (remote failure)"
Well you may be SOL until that site comes back up :/
Sent from my XT1056 using Tapatalk
theres a stock odex adn deodexed rom on this forum somehwere, I got it lastnight and downloaded it. It has an xbin in the odex though, i think that is keeping the ota form flashing. but you can atleast flash that rom to get a working phone again. thats what I had to do that last night. Ill see if I can find a link to it. if not I will post it on my drive.
---------- Post added at 06:12 PM ---------- Previous post was at 06:10 PM ----------
http://forum.xda-developers.com/showthread.php?t=2499594 here it is. flash the odexed worked for me. but i still cant get the kitkat ota to flash even with using the revercory image that is in the kitkat ota with this rom. I think the xbin or maybe build prop in this rom may be preventing the kitkat ota to flash,
---------- Post added at 06:14 PM ---------- Previous post was at 06:12 PM ----------
this is where the factory image to rsdlite back should be, http://sbf.droid-developers.org/
but they had hdd crashes as noted on that site. hopefuly they can recover the data and have the images because i searched everywhere and they are the only one anyone links to for rsdlite images.
So I used the 4.4 root tutorial without any problems and then flashed the 4.4.2 update via sdcard.
The deal is that my supersu seems to be damaged, thought I still have root, the xposed framework can´t seem to receive supersu permission.
So I want to downgrade to the 4.4.
How should I do this?
alemonte said:
So I used the 4.4 root tutorial without any problems and then flashed the 4.4.2 update via sdcard.
The deal is that my supersu seems to be damaged, thought I still have root, the xposed framework can´t seem to receive supersu permission.
So I want to downgrade to the 4.4.
How should I do this?
Click to expand...
Click to collapse
Term "Downgrade" refers to "lowering" you version, in this case from 4.4 to 4.2.2. Now you just need to go back to 4.4
I am not sure whether your bootloader unlocked or not and what you version is, but I think this one will help http://forum.xda-developers.com/showthread.php?t=2603358 or this one http://forum.xda-developers.com/showthread.php?t=2538896
okaban said:
Term "Downgrade" refers to "lowering" you version, in this case from 4.4 to 4.2.2. Now you just need to go back to 4.4
I am not sure whether your bootloader unlocked or not and what you version is, but I think this one will help http://forum.xda-developers.com/showthread.php?t=2603358 or this one http://forum.xda-developers.com/showthread.php?t=2538896
Click to expand...
Click to collapse
Ok, so I have a locked bootloader. My guess is that I have the last version since I made the update to 4.4.2.
By having a locked bootloader I think I can´t downgrade to 4.2.2, right?
So I wanted to go back to 4.4 by following the commands below:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
But right on the first fastboot, I get this error:
downgraded security version
Update gpt_main version failed
preflash validation for GPT
alemonte said:
Ok, so I have a locked bootloader. My guess is that I have the last version since I made the update to 4.4.2.
By having a locked bootloader I think I can´t downgrade to 4.2.2, right?
So I wanted to go back to 4.4 by following the commands below:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
But right on the first fastboot, I get this error:
downgraded security version
Update gpt_main version failed
preflash validation for GPT
Click to expand...
Click to collapse
you can't go back to the complete 4.4 package and honestly im not even going to tell you how to get 4.4 running because i wont be responsible for you hardbricking your phone.
4.4.2 has a new bootloader and 4.4 has a diffrent bootloader you cant downgrade the 4.4.2 bootloader at all. it is a one way street sorry
dray_jr said:
you can't go back to the complete 4.4 package and honestly im not even going to tell you how to get 4.4 running because i wont be responsible for you hardbricking your phone.
4.4.2 has a new bootloader and 4.4 has a diffrent bootloader you cant downgrade the 4.4.2 bootloader at all. it is a one way street sorry
Click to expand...
Click to collapse
OK! I know I messed up updating to 4.4.2 rooted. Should've stayed on 4.4 but my X was having issues after disconnecting from Wifi to connect to LTE. Anyways..I´ll be returning the phone and getting a new one today! Tnks a lot for the help!
alemonte said:
Ok, so I have a locked bootloader. My guess is that I have the last version since I made the update to 4.4.2.
By having a locked bootloader I think I can´t downgrade to 4.2.2, right?
So I wanted to go back to 4.4 by following the commands below:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
But right on the first fastboot, I get this error:
downgraded security version
Update gpt_main version failed
preflash validation for GPT
Click to expand...
Click to collapse
Most likely you tried to downgrade to the very first 4.2.2 (.31 in case of XT1058). It's not possible. You need the one after, with camera update (.54 for XT1058, for example, http://sbf.droid-developers.org/phone.php?device=0)
okaban said:
Most likely you tried to downgrade to the very first 4.2.2 (.31 in case of XT1058). It's not possible. You need the one after, with camera update (.54 for XT1058, for example, http://sbf.droid-developers.org/phone.php?device=0)
Click to expand...
Click to collapse
please dont downgrade to 4.2.2 camera update downgrade to 4.4 you just have to not flash the gpt file but flash everything else.
if you flash 4.2.2 Camera update and then take the OTA for 4.4 you will brick your phone.
dray_jr said:
please dont downgrade to 4.2.2 camera update downgrade to 4.4 you just have to not flash the gpt file but flash everything else.
if you flash 4.2.2 Camera update and then take the OTA for 4.4 you will brick your phone.
Click to expand...
Click to collapse
So, is it possible to go from 4.4.2 to 4.4 without bricking or not? Just asking for clarification because of
4.4.2 has a new bootloader and 4.4 has a diffrent bootloader you cant downgrade the 4.4.2 bootloader at all. it is a one way street sorry
Click to expand...
Click to collapse
okaban said:
Term "Downgrade" refers to "lowering" you version, in this case from 4.4 to 4.2.2. Now you just need to go back to 4.4
I am not sure whether your bootloader unlocked or not and what you version is, but I think this one will help http://forum.xda-developers.com/showthread.php?t=2603358 or this one http://forum.xda-developers.com/showthread.php?t=2538896
Click to expand...
Click to collapse
Please do not advise any users to downgrade!
It is well documented that if you downgrade to ANY version, once on 4.4.2, you will brick your phone! It is literally all over the Moto X forums.
Wouldn't you feel awful if the OP followed your advice and bricked their phone???
---------- Post added at 09:03 PM ---------- Previous post was at 09:00 PM ----------
EchoHelix said:
So, is it possible to go from 4.4.2 to 4.4 without bricking or not? Just asking for clarification because of
Click to expand...
Click to collapse
NO! I have no idea why anyone would advise you to do that.....
Whatever exploit you had used to root on 4.4 does not work on 4.4.2
The only way to root (and achieve write-protect-disable), now that you are on 4.4.2 is to unlock the bootloader. Even with unlocked bootloader, you still can't downgrade without bricking.
I'll just add my two cents as well....as perfectly said already above....I'll just add....
NO. Do not ever try to downgrade to any version if you are on 4.4.2 or higher already. Unless you don't care at all if you brick and have the cash for a new phone or an old phone you'd be happy using again.
No. Some will debate this, and they should keep it to themselves.....unless they are offering to replace your phone if their advice bricks you. ?
---------- Post added at 03:21 PM ---------- Previous post was at 03:17 PM ----------
@okaban , please do not advice people to downgrade, or lead them to believe its safe.
If you want to try it, go ahead....but keep it to yourself. Too many aren't confident with this stuff and will end up with a paperweight because you led them to believe they could do it.
So please, do not suggest downgrading. Its irresponsible and hazardous advice.
Thanks! ?
samwathegreat said:
Please do not advise any users to downgrade!
It is well documented that if you downgrade to ANY version, once on 4.4.2, you will brick your phone! It is literally all over the Moto X forums.
[cut]
The only way to root (and achieve write-protect-disable), now that you are on 4.4.2 is to unlock the bootloader. Even with unlocked bootloader, you still can't downgrade without bricking.
Click to expand...
Click to collapse
KJ said:
I'll just add my two cents as well....as perfectly said already above....I'll just add....
NO. Do not ever try to downgrade to any version if you are on 4.4.2 or higher already. Unless you don't care at all if you brick and have the cash for a new phone or an old phone you'd be happy using again.
No. Some will debate this, and they should keep it to themselves.....unless they are offering to replace your phone if their advice bricks you. ?
Click to expand...
Click to collapse
Sorry, quoted because I wanted to try and emphasize this advice... and add...
The GPT.BIN in 4.4.3 has been updated as well.. so Once you have either 4.4.2 or 4.4.3 on your phone, DO NOT ATTEMPT TO DOWNGRADE!!!
If you try and downgrade only "parts" things wont work properly... example: Those who had 4.4.2 and downgraded only system.img and boot.img found issues going settings -> security... (it kicked them out). And other flakey things happened. When they attempted to update, things got worse.
4.4.4 will likely see updates to motoboot.img(bootloader) and GPT.BIN(partition table)... So the same warnings will apply.
It does NOT matter if your bootloader is unlocked or not. These same warnings and caveats apply!!
KidJoe said:
Sorry, quoted because I wanted to try and emphasize this advice... and add...
The GPT.BIN in 4.4.3 has been updated as well.. so Once you have either 4.4.2 or 4.4.3 on your phone, DO NOT ATTEMPT TO DOWNGRADE!!!
If you try and downgrade only "parts" things wont work properly... example: Those who had 4.4.2 and downgraded only system.img and boot.img found issues going settings -> security... (it kicked them out). And other flakey things happened. When they attempted to update, things got worse.
4.4.4 will likely see updates to motoboot.img(bootloader) and GPT.BIN(partition table)... So the same warnings will apply.
It does NOT matter if your bootloader is unlocked or not. These same warnings and caveats apply!!
Click to expand...
Click to collapse
Good point at the end. After 4.4.2....some thought their unlocked phone was immune to these warnings.....or their dev edition....which every one should know now is no different than any other unlocked phone. Aside from intact warranty.
Great addition KidJoe! Doesn't matter the phone, locked, unlocked or dev edition......none can safely downgrade.
The moto x is nothing like a Nexus in this regard.
Guys, any help will be appreciated. Was trying to restore stock OS and flashed a Brazilian version and maybe flashed incompatible radio. Now i dont see any network or even an IMEI number in the settings. I think i need a US version of 4.4.4. Cant seem to find the US version anywhere, can only find Brazilian and European.
Cheers!
Yeah I'm in the same boat, must have flashed an incompatible radio because I can't connect to any network, and I get no information whatsoever in the Status section of the About phone settings. Any help with this would be greatly appreciated!
---------- Post added at 05:57 AM ---------- Previous post was at 05:05 AM ----------
And also I have tried flashing the radio from the tool kit still with no luck
Sent from my XT1095 using XDA mobile app
commrade11 said:
Yeah I'm in the same boat, must have flashed an incompatible radio because I can't connect to any network, and I get no information whatsoever in the Status section of the About phone settings. Any help with this would be greatly appreciated!
---------- Post added at 05:57 AM ---------- Previous post was at 05:05 AM ----------
And also I have tried flashing the radio from the tool kit still with no luck
Sent from my XT1095 using XDA mobile app
Click to expand...
Click to collapse
Wich version do you have. get system files from www.motofirmware.com. it is yout best chance
I am in the same boat
I did the same thing I followed some instructions in the main thread that said to
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
I didnt have anything backed up which is my fault but honestly before spending all day today trying to fix my phone I didn't really understand a whole lot about the partitions. Anyhow my phone has unknow baseband and unknown IMEI If anyone figures this out please post the solution as I am totally stumped
Also I would be happy to make a small cash donation to anyone who can get me back to working state.
---------- Post added at 04:51 AM ---------- Previous post was at 04:02 AM ----------
Ok guys I think I figured it out, I was able to get my IMEI and baseband back.
Here is what I did.
OMG im so happy right now...
if you are on ATT or Tmobile
Go here:
http://motofirmware.com/files/getdownload/114-att-xt1097-444-kxe21187-38-cid1-cfcxmlzip/
Download and extract this.
Get the following two files and put them in the same directory as your Fastboot.
fsg.mbn
NON-HLOS.bin
Now just do these commands in fastboot:
Code:
fastboot flash system modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbm
fastboot reboot
Reboot
Seeing as how they didn't release the recovery image for the XT1095 you probably flashed the XT1097 which is the Brazilian model of the phone meaning you are screwed until we get a normal recovery image for the XT1095.
How do you define screwed?
w9jds said:
Seeing as how they didn't release the recovery image for the XT1095 you probably flashed the XT1097 which is the Brazilian model of the phone meaning you are screwed until we get a normal recovery image for the XT1095.
Click to expand...
Click to collapse
lol seeing as I spent all day just trying to get my phone to register ANY baseband or imei number this is the nice kind of screwed
Yeah, I did the same thing as well. Since your IMEI number got wiped, you're out of luck. I just took the plunge and called Motorola support to get a replacement. Even though it was still under warranty, I still got charged the $125 physical damages fee for a replacement. Sorry about that.
My device came initially out of the box as an XT1097 as my carrier is TELUS. After rooting it and everything like that, my phone thinks it's an XT1095. I have the Motorola Toolkit and there is a NON-HLOS.bin file as well as fsg.mbn file that I've flashed to my device following the steps from above, still with no success. I have unknown IMEI and baseband as well as unknown showing in a few other spots in my status settings. I'm just wondering if it's worth trying anything else or if I should just take it to my carrier to have them send it in and hope for the best.
commrade11 said:
My device came initially out of the box as an XT1097 as my carrier is TELUS. After rooting it and everything like that, my phone thinks it's an XT1095. I have the Motorola Toolkit and there is a NON-HLOS.bin file as well as fsg.mbn file that I've flashed to my device following the steps from above, still with no success. I have unknown IMEI and baseband as well as unknown showing in a few other spots in my status settings. I'm just wondering if it's worth trying anything else or if I should just take it to my carrier to have them send it in and hope for the best.
Click to expand...
Click to collapse
How did you root it? The multi-tool method or superboot method?
you can always flash the entire phone using the flashfile xml as reference even for the steps, it will convert your phone back to "stock"
If anyone needs the download for AT&T and the firmware site isn't working PM/email me. I needed it and had to scour the internet for link cause the motofirmwares site was down for maintenance.
Correct me if I'm wrong, but cant you just go here graffixnyc.com/motox.php
and download the stock modem? Sorry if that is completely different than what you were asking for.
Does anyone have the XT1068 radio firmware??
I need it to fix may radio....
Thanks,
Electric Flute said:
Does anyone have the XT1068 radio firmware??
I need it to fix may radio....
Thanks,
Click to expand...
Click to collapse
You had to be more specific. KK or L radio , also you region is important. (EU, US , Asia , LA...)
Sorry,
Lollipop and I'm from Brazil.
Electric Flute said:
Sorry,
Lollipop and I'm from Brazil.
Click to expand...
Click to collapse
the brazil lollipop is in my signature click the 5.0.2 and download and use the files from inside or better still flash whole firmware using the easy installer - if you've broken radio what else have you broken or flashed wrong firmware
---------- Post added at 10:41 AM ---------- Previous post was at 10:18 AM ----------
reefuge said:
the brazil lollipop is in my signature click the 5.0.2 and download and use the files from inside or better still flash whole firmware using the easy installer - if you've broken radio what else have you broken or flashed wrong firmware
Click to expand...
Click to collapse
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Brazil lollipop radio Firmware
Somebody from Brazil and with rooted Lollipop could extract it for you.
Type in terminal
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/radio_firmware.img
Sent from my XT1068 using XDA Free mobile app
reefuge said:
the brazil lollipop is in my signature click the 5.0.2 and download and use the files from inside or better still flash whole firmware using the easy installer - if you've broken radio what else have you broken or flashed wrong firmware
---------- Post added at 10:41 AM ---------- Previous post was at 10:18 AM ----------
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Brazil lollipop radio Firmware
Click to expand...
Click to collapse
Hello Reefuge,
Thank you very much for the radio firmware file! I flashed it and my radio phone worked again.
But I still have the same original problem, that's why I was messing before with radio files: I can't connect to WCDMA. Even with *#*#4636#*#* my option is always locked to "GSM only".
Any idea why?
XT1068 with Quantum 2.1.2 by Shawn
Electric Flute said:
Hello Reefuge,
Thank you very much for the radio firmware file! I flashed it and my radio phone worked again.
But I still have the same original problem, that's why I was messing before with radio files: I can't connect to WCDMA. Even with *#*#4636#*#* my option is always locked to "GSM only".
Any idea why?
XT1068 with Quantum 2.1.2 by Shawn
Click to expand...
Click to collapse
try the global firmware 5.0.2 (DSDSALL) as regional like de / br will be locked down to certain bands only - global should have all unlocked
reefuge said:
the brazil lollipop is in my signature click the 5.0.2 and download and use the files from inside or better still flash whole firmware using the easy installer - if you've broken radio what else have you broken or flashed wrong firmware
---------- Post added at 10:41 AM ---------- Previous post was at 10:18 AM ----------
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Brazil lollipop radio Firmware
Click to expand...
Click to collapse
Hi reefuge,
this didn't help in my case.
My phone is XT1068 retaildsds running on Android M. It has SIM card detecting issues for couple of weeks already. Normally I restarted the phone and got radio back, but since yesterday multiple reboots / reinserting (replacing) SIM card doesn't work any more.
I tried reflash my modem using 4 lines of code you mentioned with the current firmware from here. But it didn't help.
Although I strongly suspect this is hardware issue, I want to try other software side solutions if you can provide any.
Thanks.
Qi