yashsingh1/xdaforums huggingface dataset:
[Moto X Q&A] KidJoe:
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 ----------

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.
[Moto X Q&A] arcanexvi:
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
[Moto X Q&A] gunnyman:
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.
[Moto X Q&A] kzoodroid:
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.
[Moto X Q&A] KidJoe:
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://xdaforums.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://xdaforums.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.
[Moto X Q&A] kzoodroid:
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.
[Moto X Q&A] gunnyman:
I think you're confused. My bootloader is LOCKED. I can flash SIGNED factory images for MY PHONE just fine.
[Moto X Q&A] kzoodroid:
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.
[Moto X Q&A] gunnyman:
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.
[Moto X Q&A] KidJoe:
Not sure I follow what you are trying to say.

read through these two threads -> http://xdaforums.com/showthread.php?t=2534060 and http://xdaforums.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.
[Moto X Q&A] kzoodroid:
That first thread you referenced (http://xdaforums.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 ----------

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://xdaforums.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.
[Moto X Q&A] kzoodroid:
So you are saying you can flash the factory images for the dev. editions to any other phone without unlocking the bootloader? Because all I've been saying is no you can't irregardless of where you get the files from. If you can do that through moto fastboot then that is new to me but then again I am new to Motorolla phones. The Nexus line you have to unlock the bootloader to flash factory images from Google using fastboot and I assumed the dev. editions phones would behave like nexus phones when I gave my response..
[Moto X Q&A] jayboyyyy:
i have been watching this just for entertainment value, but I can't fathom how you could have read what he wrote and got the idea that he said you can flash any def edition's images to any other phone.

He said, look at verizon dev edition and verizon consumer edition. they are the same, i.e. they can both be flashed to the consumer edition. I don't understand how you interpreted that to mean any dev edition can be flashed to any phone...

also, everything he said was dead on accurate. id also like the explanation he requested between your ROM and factory image discussion... that's what was keeping me coming back lol. i'm really hoping your explanation of the differences between the two is as good as what im expecting.
[Moto X Q&A] kzoodroid:
The SBF files are not all factory images downloaded from Motorolla.com most are OTA's, hence me calling them ROM's, OTA's are not factory images they are ROMs. Factory image files have to be released by Motorolla and you download them from them as SBF did. The SBF factory images aren't these magical files that you can flash to a device with a locked bootloader, the same rules still apply to them. So you see my point?

And I'm totally lost on this thread. According to these people here this phone is able to do what no Nexus device is able to do and that is flash factory images without an unlocked bootloader.
[Moto X Q&A] jayboyyyy:
Bro what sbf compiles is the same as a factory image. This is what the guy already told you. Verizon dev factory image can be flashed on a vze consumer edition because they are the same thing. No difference. So the security checks are the same. This is why on dev phone you must first be on a factory fw before trying to push the ota/factory image/sbf factory image. Unless someone decompiles the stuff to allow you to flash it through twrp which I haven't seen done personally. But that may be out there. This is not a difficult concept if you would stop thinking that dev factory image is somehow different then the consumer edition fw that sbf compiled.
[Moto X Q&A] kzoodroid:
Yes I know that. But where I got lead astray is that this thread was about the OP wanted to know if he could flash the factory images of the GSM dev edition to his locked AT&T carrier phone and all of a sudden its about how the consumer and dev editions are the same? All I can fathom is why are these guys saying you can flash factory images to a locked phone which to me was the main point of this thread not that the files are the same.

---------- Post added at 11:03 PM ---------- Previous post was at 10:36 PM ----------

This is the OP's post:

Q] Replace AT&T image with Developer Edition: Is it possible to deploy the Moto X DE image on Moto X AT&T (X1508) device?

I'm looking at it as can I flash the factory images of the dev. ed. on my locked carrier phone and the answer is no not without unlocking it. How it got switched to are the consumer and dev editions the same is beyond me.

---------- Post added at 11:24 PM ---------- Previous post was at 11:03 PM ----------

And I should add this exercise in futility hasn't been a total waste, I learned about moto fastboot.
[Moto X Q&A] quirrelicious:
I'm not sure if this is deviating from the original topic, but for a locked at&t moto x (XT1058), is it possible to flash the stock ROM for Rogers on it?

Asking this as the Rogers version supports LTE Band 7, which the hardware XT1058 can support, but not supported through the at&t ROM.
[Moto X Q&A] zivoro:
By the end of the day , kzoodroid is right :)

I have XT1508 from AT&T and I wan to get rid from all the AT&T "goodies" (I'm not looking for developing, and I can't run rooted as I'm reading mails from corporate- with Citrix Worx, which is yet another saga).

Assuming the HW of the AT&T and of the developers version (GSM) are the same, thoughts I can install the DE image and bye bye (that was my original question).

Here are the fact after few trials and errors (I'd mainly used RSD Light and Motorola Fastboot) -

1- I have no problems to load the ATT images from SBF (both v4.4 and v4.2).

2- I can't load the DE image from Motorola site.

3- I'd tried to play with some components between the two packages, thoughts the most important is to be able to replace the system.img. No matter what I'm doing, the device rejecting it during the extraction.

4- Based on the above, my understanding kzoodroid was right all the way, so far the fastboot is locked, I can't install DE components on AT&T XT1508 (BTW, the DE image is named XT1503)

As quick workaround, I'm using exDialer to replace the native contacts (which bring the annoying AT&T address book all the time), and tried to disable other AT&T processes as possible.

Hope it's clear what the "OP" looked for.
[Moto X Q&A] arcanexvi:
Seriously. How has this gotten so long and drawn out?

If you own a carrier device and it is locked you may only flash signed images meant for that specific carrier/device. Doesn't matter who releases them (Motorola or a carrier sbf recovery file) as that's just semantics. These files all source from Motorola as this is how they get signed.

If you have an unlocked device (carriers that allow it or a Dev edition) you can flash images for the wrong device and engineering builds if you care to tinker and you can install a custom recovery and kernels/builds etc as the encrypted signature check will be disabled. There are other ways around some of this (read: safestrap) but as far as this conversation is concerned the above is true. This is as clear cut as I can make it for you folks.
[One (M7) Q&A, Help & Troubleshooting] ruud.walraven:
I'm the next one in line with the same question, but no other answers helped me yet. What I did wrong was adb sideloading the OTA file using CWM recovery. That part I understand, so completely my own fault.

However, the update is still on the SD card and I tried to load stock recovery via fastboot so that I can install OTA from the SD card. What I get is something I find a lot of others have as well; the recovery fails to mount sd card 5 times. When I try to "Apply from SD card" I get an error "Check cid failed! --invalid operation--" and the phone reboots. The same error happens to users in many places, an example here: androidcentral . com/how-manually-update-your-google-play-edition-htc-one-android-44-kitkat

I think I can recover the phone with instructions (I can't post URLs yet) that will install a different recovery and uses adb sideload. But it also erases the sdcard which I try to avoid.

So, Is there anyone who can advice me what to do? If it cannot be avoided that my sdcard will be wiped; so be it. But I will manage doing that, I'm looking for an alternative at the moment. I suspect that if I find the correct recovery version that it will "mount" the "sdcard" (which I think is an emulation because the HTC One has no sdcard??) will also allow me to recover my phone with sdcard intact. But I find it difficult to find the correct recovery.img. I've tried two versions *can't find numbers back right now, will post if needed*.

HTC One, converted into GPe (so tampered and unlocked)

HBOOT 1.44
[One (M7) Q&A, Help & Troubleshooting] mbroeders:
Ruud, I don't know if I completely understand your story, but you are able to get into stock recovery right? If so, do not choose 'Apply from SD card', but 'Apply from phone'. I got the same error messages (fails to mount SD card...), but if the OTA file is on your phone, you have to choose phone storage.
[One (M7) Q&A, Help & Troubleshooting] ruud.walraven:
I should have mentioned that the other options (apply from phone and apply from cache) don't work either. One thing I am unsure about is if this is indeed the stock recovery.img I put back on. Is there a single recovery.img for HTC One, or a list where I can find which one came standard so I can put it back. My suspicion is that that recovery will work, although the guy I bought the phone from may have installed recovery/images that may have reformatted everything in a way that stock won't work any longer...
[One (M7) Q&A, Help & Troubleshooting] ruud.walraven:
I noticed most people need to post fastboot getvars all. Makes sense to figure out what software I need so here it is:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.14.3250.13

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.29.401.12

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: 1234567890AB

(bootloader) imei: 123456789000000

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__102

(bootloader) battery-status: good

(bootloader) battery-voltage: 4295mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too many links))
[One (M7) Q&A, Help & Troubleshooting] mbroeders:
Are you sure this is the GPe version? I get a feeling that you have the Sense version and then it won't work of course. (sorry if I'm wrong)
[One (M7) Q&A, Help & Troubleshooting] ruud.walraven:
I've tried a whole range of things that didn't help. Don't want to preserve the sd card any longer.

Flashed recovery versions: 1.29.401.12, 2.24.401.8, 3.07.1700.1 and 3.58.1700.5.

Neither version was able to reinstall from sdcard. But I found out later that I may have done *something* to the sdcard (see CWM below)

Next I flashed CWM to try flashing a nandroid. However during the process I couldn't browse my sdcard anymore. Before flashing above recoveries I had CWM and then I could see all files. May have done something wrong.

After trying the mentioned nandroid a few times I realized that I am S-ON.

I have been trying to get S-OFF for the last few hours because I found a file I want to use on my phone (See htc1guru . com/2013/11/android-4-4-kit-kat-google-edition-3-58-1700-5-ruu-ota-files/). I've looked at Moonshine, but my phone is not in the list of supported rom versions (1.29.401.12). I tried Revone, but get error = 1.

So now I'm not sure what to do next!!
[One (M7) Q&A, Help & Troubleshooting] ruud.walraven:
I am absolutely sure I have a Sense version originally. I bought it from someone who unlocked the bootloader and replaced the sense firmware with GPe. OTA was working because I OTA-ed to 4.3. I've contacted him this morning, but he says to have no idea what files he used.
[One (M7) Q&A, Help & Troubleshooting] ipfreelytech:
you bought it from an idiot.

you can't properly convert to GPE with s-on. That's why your hboot, mainver and cid are all wrong for a GPE conversion.

I assume you're boot-loader unlocked? flash cwm or TWRP. Then restore this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__102-1-29-401-12-2013-05-16-zip/

after restoring that nandroid try to s-off with revone and or rumrunner.

Revone: http://xdaforums.com/showthread.php?t=2314582

Rumrunner: http://xdaforums.com/showthread.php?t=2488772

once your s-off you can properly convert your phone to GPE. The problem wasn't just that you flashed it with a custom recovery but that the phone was never in a proper state to receive OTA for GPE!

use the RUU from here once your s-off to convert to GPE 4.4 : http://xdaforums.com/showthread.php?t=2358781

you'll also want to go supercid with fastboot oem writecid 11111111
[One (M7) Q&A, Help & Troubleshooting] ruud.walraven:
I'm downloading all required files right now. In the meantime looking into everything to make sure to not further brick it once S-OFF. Tricky business!

There's one question I found: according to this thread SuperCid 11111111 doesn't get OTA and the best bet for me would be HTC__001. Is that correct, or can I also choose from HTC_001 or GOOGL001? (the latter I remember reading is supposed to be good too). In any case ... I suppose I can best follow your instructions and I can change the cid to whatever needed afterwards anyway.

edit: It took 1.5 hours to download the nandroid, but something must have gone wrong because the file cannot be opened by winzip nor 7z. After the failed opening of the file I've md5-ed the entire zip file and it doesn't match the checksum on the download link. So started download again...
[One (M7) Q&A, Help & Troubleshooting] ruud.walraven:
I have a problem; the download stops at different points, never completing. Must be a problem in the connection or at htc1guru. Is there an alternative file/download/mirror I can use as well? Have searched google for the same file with no results.
[One (M7) Q&A, Help & Troubleshooting] ruud.walraven:
I was finally able to download the file through FF. Every time the download failed I started again, but paused and replaced the .part file with the failed download. When you resume FF detects the last bit and resumes from there. Best part was that I got my Chrome 900+MB download and used that as .part file. So I could resume nearly finished. Ran the checksum to be sure nothing funny had happened because of my tinkering. To quote Borat: great success.

However, after restoring the nandroid through CWM I tried both Revone and Rumrunner. Revone fails error = 1 and Rumrunner assumes I start from my homescreen (which I can't). A bit unwise, but I tried anyway from both fastboot and CWM but in neither case will Rumrunner continue. It claims there is no ADB connection (even though the phone shows up in adb devices).

So I am stuck for now. Still looking at as many posts about S-OFF as I can to see if I find some vital piece of inof I missed or something I can still try. But for now I'd like some idea's how to achieve S-OFF..
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
What is the date in your hboot version? If after June, then revone won't work. Have you tried moonshine?
[One (M7) Q&A, Help & Troubleshooting] ruud.walraven:
hboot has a date? Hboot is 1.44 and bootloader start screen says apr 12 2013, is that what you mean?

My version (1.29.401.12) is not supported by moonshine for as far as I can tell.

I also notice now that fastboot getvars bootmode says: fastboot. Shouldn't this be disabled for revone and/or rumrunner?
[One (M7) Q&A, Help & Troubleshooting] ruud.walraven:
Just a question: In a sense I can't have messed anything up that bad because I'm S-ON. So if I would install the 4.3 release that was on the device before I sideloaded the 4.4 OTA through CWM, wouldn't it just work because all things point to the correct places? Since I broke it with adb sideloading, I could restore the device probably just as well, right?

In any case; I still would want to S-OFF my device to go through ipfreelytech's steps and get a functioning 4.4 GPe. But So far I found that Moonshine doesn't support my device and for both rumrunner and revone I need to start from a booted up android homescreen. So all three options don't seem to work. Did I really brick my phone, or is there still hope??
[One (M7) Q&A, Help & Troubleshooting] ziolooo:
I had same problem on my device. I decided to install CWM instead of TWRM, downloaded RUU 4.2.2 and flashed it. Next I get update to 4.3 and 4,4 later and now everytning works perfect.