yashsingh1/xdaforums huggingface dataset:
[Moto X General] krazzyvishal:
Help please...

So I have a Moto X XT1052 (India variant). I unlocked its bootloader and rooted it about two months ago.

Today, Motorola released the 4.4.4 update for this and so to get the OTA, I decided to return to complete stock because I had done several modifications in system and all the hell.

Now I have successfully done all that using RSD Lite, also relocked the bootloader.

Now, I heard that on bootloader 30B4, taking OTAs will hard brick the device. So now though I am completely stock, unrooted, and on (re)locked bootloader, should I still not take the OTA? It's my first time with a Moto so I just want to be careful. This info may help:

C:\ROOT MOTO X>fastboot getvar all
[B][COLOR="Red"]version-bootloader: 30B4[/COLOR][/B]
version: 0.5
cpu: MSM8960 Pro CS
ram: 2048MB Hynix S4 SDRAM DIE=4Gb
emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
product: ghost
revision-hardware: 0x8300
radio: 0x3
secure: yes
mid: 026b
serialno: TA643018FY
qe: qe 2/1
[B][COLOR="Red"]unlocked: no[/COLOR][/B]
iswarrantyvoid: yes
max-download-size: 805306368
uid: <hidden>
imei: <hidden>
meid:
sku: 000000000000000
cid: 0x07
iccid:
date: 03-20-2014
cust_md5:
reason: Key pressed
ro.build.date: Tue Mar 4 14:24:37 CST 2014
ro.build.id: KLA20.16-1.38
ro.build.tags: release-keys
ro.build.type: user
ro.build.user: hudsoncm
ro.build.version.codename: REL
ro.build.version.incremental: 32
ro.build.version.release: 4.4.2
ro.mot.build.customerid: RETASIA
ro.product.name: ghost_retasia
ro.build.fingerprint[0]: motorola/ghost_retasia/ghost:4.4
ro.build.fingerprint[1]: .2/KLA20.16-1.38/32:user/release
ro.build.fingerprint[2]: -keys
ro.build.version.full[0]: Blur_Version.161.44.38.ghost_row
ro.build.version.full[1]: .AsiaRetail.en.03
kernel.version[0]: Linux version 3.4.42-gb2a7112 (h
kernel.version[1]: udsoncm@ilclbld53) (gcc version
kernel.version[2]: 4.7 (GCC) ) #1 SMP PREEMPT Tue M
kernel.version[3]: ar 4 14:55:10 CST 2014
all:
finished. total time: 0.159s

C:\ROOT MOTO X>

So should I take the upcoming OTA ? :confused:

Please help. Thank you.
[Moto X General] KidJoe:
If you had 4.4.2 on your phone, modified it, and then ran RSDLite to flash the full SBF of your phone, without any errors, then your phone should be proper to take the OTA update.

I believe 30.B4 is the current Bootloader version for most X's on 4.4.2, but I don't have mine in front of me to confirm.

The biggest issue would be if you've ever tried downgrading to 4.4 or 4.2.2 w/camera fix AFTER having 4.4.2 on your phone, then taking OTA. as that causes issues with GPT.BIN and MOTOBOOT.IMG which can not be downgraded safely/successfully and appear to be the main cause of issues and bricking.

If you can grab your 4.4.2 SBF and follow Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html without getting errors, you should be fine taking an OTA.
[Moto X General] krazzyvishal:
Thanks again, no I have done exactly what you said in the first four lines and never downgraded it below 4.4.2. When I received the Moto X it was on 4.3 and as soon as I powered it up, 4.4.2 OTA was available. Took that then played (rooted, unlocked) and now back to stock using RSD Lite.

I think I can go fine with the OTA that I'll receive. Thanks once again for your valuable help. ?

sent from my Moto X
[Moto X General] sumeetprashant:
Hi guys got my Moto X a week back... I was just wondering the optimal temperature range for X I am usually getting 34°-39°C in normal use without using any heavy apps. Even when I use whatsapp or open play store this is the normal temperature I am getting and while charging it goes upto 42°-46°C. I just want to know whether its normal for you guys as well. Please pardon me if I am asking this in the wrong forum.
[Moto X General] krazzyvishal:
Now if I even just modify the boot logo to hide the boot loader unlocked warning, will the phone be not fine for an OTA?

sent from my Moto X
[Moto X General] KidJoe:
Using a modified logo.bin doesn't impact ability to take OTA.
[Moto X General] jtquen:
Is the Sprint Moto X SIM unlocked?
[Moto X General] :
Nope. And only unlockable for International use. And I believe you need to be a sprint customer for a period of time to get that even.
[Moto X General] mtotho:
perhaps I didn't do enough research but I tried the locked bootloader root method (verizon) and something went wrong.

I downloaded the verizon 4.2.2 camera update and extracted it. I then ran the first fastboot command, here is the results

mike-linux VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml # fastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.236s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.077s

Now the phone is stuck in fastboot. On the screen it says "fastboot reasons: flash failure".

Might downloading the stock firmware, extracting and flashing the same gpt.bin fix the issue? I am currently downloading but I don't want to further mess myself up.

(bootloader) version-bootloader: 30B4

(bootloader) sku: XT1060

(bootloader) reason: Flash Failure

thanks

Mike

EDIT: allelujah!, I did exactly that. Downloaded latest stock 4.4.2. Extracted it, ran "fastboot flash partition gpt.bin", it succeeded and phone booted back to normal. Now I just have to figure out what I screwed up with initially..
[Moto X General] :
Now that you're on 4.4.2......I hope you know there's no downgrading?? Not without extreme risk of being phone less? ;)
[Moto X General] KidJoe:
You had 4.4.2 on your phone and tried downgrading to 4.2.2. You can't. GPT.BIN and MOTOBOOT.IMG will get in the way and prevent downgrade.

There are many warnings about possibly bricking if you have 4.4.2 and above on your phone, and try to downgrade your rom!

At this point, If I was you, I would consider flashing the ENTIRE 4.4.2 SBF, to your phone using mFastboot (see Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html ) to make sure all parts of your phone are on consistent versions, otherwise you will brick if you take an OTA.
[Moto X General] razzlepi:
Can't get 4.4.2 OTA

Long story short: I'm with Republic Wireless. Rooted my Moto X, saw RW was getting KitKat, and unrooted via this method (can't post link because new: htt p://t heunlockr.c om/2013/11/09/unroot-moto- x-all-versions/) on my GFs computer. No update, still on 4.2.2. RW says they're done with rollout, and because I was rooted they can't help. Finally heard back from Motorola - they won't help. I guess I could just flash up to 4.4.2 but I would like to get back on the regular release cycles and OTAs.

tl;dr: Do I have to do anything special to start receiving OTAs after unrooting?

Possible reason: I don't think I uninstalled xposed before unrooting. Really can't remember, but my SD card doesn't have the exposed disabler zip. Would that make a difference?

I'm can work my way around instructions, but I'm not super technical and these things kind of scare me sometimes, hence wanting to get on OTAs and not manually flashing things.

Thanks!
[Moto X General] mschumacher69:
Follow this guide to flash back to stock:

http://xdaforums.com/showthread.php?t=2446515

You can either flash the same 4.2.2 that you had and then take the 4.4.2 ota or flash 4.4.2 directly.
[Moto X General] razzlepi:
So what I did wasn't flashing back to stock? What is the difference here?
[Moto X General] KidJoe:
What process did you use to root? Since you have Republic Wireless, your bootloader is locked unless you paid the China Middleman for the unlock code. This means you likely used SlapMyMoto/RockMyMoto or the like to root, and since you are on 4.2.2, you might have also used to MotoWpNoMo to disable write protection.

To get back to "stock" the best way is to flash the stock SBF file as [MENTION=2642571]mschumacher69[/MENTION] has directed you. Either flash the 4.2.2 version that is on your phone now, and take any OTA updates that are available, or just flash the 4.4.2 SBF.

Remember to backup your data first just in case!

Keep in mind, if you did NOT unlock your bootloader, you can NOT root 4.4.4 when it comes, and while you can root 4.4.2, you can't disable write protection (meaning you have to re-root every time you power off/on, and any changes you make root wise wont survive either)
[Moto X General] razzlepi:
I only used RockMyMoto and didn't worry about MotoWpNoMo. I know I can't get permanent root when I go up to KK but I've decided I'm fine with that. I'm curious how the unrooting method I used is different from what has been recommneded here.
[Moto X General] KidJoe:
I can't use the link to the unroot method you used.. even trying to remove spaces, it doesn't work, so I can't compare... Then again, to be honest, I don't know all the changes RockMyMoto made.

But flashing back to stock using the SBF will set you completely back to out of the box, make sure all parts are on your phone, at consisten versions, etc...

Like if I'm not mistaken, RockMyMoto played with recovery, or pointers to recovery, that when you selected to boot recovery you actually booted normally with write protection disabled. A normal "unroot" process probably wont account for that, so it likely can't/wont fix it. Where as flashing the SBF will.

Think of flashing the SBF as formatting your hard drive and re-installing Windows from the original discs. Where as that unroot process probably was like runing windows repair.

If you tried checking for an OTA and one doesn't come down, you can flash the RW 4.4.2 SBF and not have to worry about checking for an update as you'll already be on 4.4.2.
[Moto X General] KidJoe:
Consider flashing... Android 4.4.2 Blur_Version.165.44.12.ghost_row.RepublicWireless.en.US that is available at http://sbf.droid-developers.org/phone.php?device=0

If successful, you'll be on the latest level that has been pushed to the republic wireless X
[Moto X General] zeidatz:
Hi :)
[Moto X General] n311.dunkle:
Stuck on step 5

The sbf firmwares don't seem to like my phones. They boot but have a wierd home screen. Settings-About says firmware is 4.2.2 but has a slightly different build number from SBF (ATT_XT1058_4.2.2-13.9.0Q2.X-116-X-17-54_CFC_1FF ..... phone says factory_ghost-userdebug 4.2.2 13.9.0Q2.X-118-GHOST_GNPO-20 25 test-keys.

Not sure what the failure is caused by but it always fails at boot.img
[Moto X General] mschumacher69:
You're probably flashing parts of the sbf instead of the full sbf and you're probably attempting to downgrade, so u have mismatched versions of the different sbf files. It is recommended not to flash parts of the sbf and not to downgrade. Only flash a full sbf that is of the same or higher version of the one installed on our phone.
[Moto X General] n311.dunkle:
I'm using the full firmware off sbf.developers minus the getvar line and I'm pretty dang sure I'm not downgrading. Just trying to flash stock. When the 4.2.2 kept failing I tried the 4.4 and still no luck. Take a look at the pictures I attached. The home screen looks like some under developed ROM.

update: Motorola Device Manager reads the software version when it's booted up as "N/A" but in fastboot MDM reads it as 140.44.5.ghost_att.ATT.en.US (4.4) so the bootloader looks like it got an upgrade but not the rest of it. Why would flashing 4.4 fail at the boot.img if it matches? Has anyone seen this? I don't have much prior history on the phone but I've never had problems "upgrading".
[Moto X General] mschumacher69:
Where are u downloading the sbf from?
[Moto X General] samwathegreat:
OK, well first, boot.img is the KERNEL, which explains exactly why you are getting the strange "user debug" build number. (since this is where it fails)

This appears to have at one point been a test-phone or prototype. I also noticed that you have a sticker showing "NO IMEI" on the phone. I'm really curious where it came from.

I'm also curious exactly where you are getting your SBF files...you mention sbf developers, but are you using a firmware from this specific page? http://sbf.droid-developers.org/phone.php?device=0

If so you have come across a really strange phone and/or batch of phones that were likely early prototypes. While we have ZERO documentation that suggests boot.img (the kernel) cannot be downgraded it is possible that a prototype phone is different.

It is also possible that if this is indeed some kind of prototype, that the official firmware won't flash, even though it's signed with release-keys, because an early prototype would not be able to validate the authenticity of those release-keys. Notice that the CURRENT KERNEL is signed with TEST KEYS?!?! This would not be possible on a production model....not without unlocking the bootloader.

My only suggestion for you would be to attempt to unlock the bootloader.....but since Moto won't give you the code.....and you don't even have an IMEI to even --possibly-- get one from the "China Middleman", I don't have a clue what you might do.

Its possible that the phone DID have some kind of engineering bootloader previously, but if you flashed ANY SBF -- and motoboot.img (the bootloader) succeeded, you have overwritten it.

I'd love to know more about this/these phone(s). VERY interesting, indeed. Do you have more like it? If so, TRY flashing JUST boot.img, BEFORE you flash motoboot.img. In fact, try flashing EVERYTHING before you flash motoboot.img. This may allow the other partitions to succeed flashing (if some kind of prototype - engineering bootloader is/was on them).

I can't wait to hear more...
[Moto X General] samwathegreat:
[MENTION=1872802]dray_jr[/MENTION] :

Would you consider updating your custom recovery info in the OP to link to the latest official TWRP version for the X (supports all variants of the X, all android versions, and even supports the "Droid" line-up).

The official website is here: http://techerrata.com/browse/twrp2/ghost

They keep the most recent version posted there. Currently 2.7.1.1.

The one linked in your OP is extremely out-of-date, and is reported to have issues with the latest android versions. Also, it was from before the X got "official" support from the TWRP team. We should all be using the new official version now.

Thanks!
[Moto X General] dray_jr:
updated OP with new recovery. here within the next couple days i will try and update this post. i have been to busy with work and have not been on
[Moto X General] hisun2006in:
MFastboot link seems to be dead

MFastboot url is not working,

Can someone please add a new url?
[Moto X General] Rooster03:
mfastboot

i googled "moto x mfastboot" and found it on the second link
[Moto X General] KidJoe:
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip

Its the mfastboot from the 4.4.2 developer recovery images direct from Moto's web site. (its the same as the one that was in the 4.4 recovery images that were on Moto's site)
[Moto X General] rodohmes:
I'm using a Sprint Moto X and have the 4.4.4 OTA waiting for me, but I'm unlocked and rooted and need to flash the stock recovery.img. Does anybody have that file easily accessible? Or can direct me to it's location. I've been searching for too long and can't seem to find it.
[Moto X General] glarepate:
It's in this archive file:

http://sbf.droid-developers.org/download.php?device=0&file=734

MD5sum -- 4A4140813A624BDE629079062CD0545E
[Moto X General] samwathegreat:
Sprint 4.4.2 STOCK Recovery image attached.

Had to zip it to meet the size limits. Unzip and flash. Enjoy :good:
[Moto X General] rodohmes:
Excellent. Just what I needed. Thank you sir.

Side note: I forgot to change a build prop edit and deactivate SuperSU, so the first attempt at taking the OTA failed. Made the necessary changes, tried again and bingo!
[Moto X General] PraterMade:
Returning to Stock with a Locked Verizon

Just looking for confirmation before proceeding...

Does anyone know if the "Returning to Stock" procedure works for the Verizon variant with a locked bootloader? I had rooted my phone when it was possible but accidentally took an OTA update. Leaving me with a working, but not quite rooted phone.

Thanks ahead of time.
[Moto X General] :
If you are talking about flashing a lower version, no. You could easily mess your phone up good, or brick now, or down the road.

It's all over this forum. Google "bricked moto x xda" to read all the unhappy campers that tried to downgrade.
[Moto X General] PraterMade:
Thanks for the quick reply but no, I am currently at 4.4.2. I could flash with the same version or up to 4.4.4. Not looking to get root working again, just would like to get back to a clean stock phone.

Thanks again.
[Moto X General] :
Then you can flash 4.4.2 or higher no problem. But if you go to 4.4.4, you'll have no root option if your bootloader is locked as of now.
[Moto X General] DJMaj07:
I'm on Sprint. Trying to return back to 4.4.4 completely stock. I looked for the 4.4.4 firmware but the website listed in the OP only goes up to 4.4.2. Is it safe to use that to get back to 4.4.2 stock and then take the OTA to 4.4.4?

Also, if that is NOT possible, can I at least flash the 4.4.2 stock recovery safely?
[Moto X General] 1dtms:
If I plan to order the XT1053 Moto X right now and it comes shipped with whatever the latest firmware they give me,

Can I go ahead and start following directs on first page for unlocking bootloader and than rooting without downgrading first? Regardless of whatever firmware they currently ship with?
[Moto X General] mschumacher69:
You won't be able to downgrade. You might be able to flash the 4.4.2 stock recovery, but you might brick if u take an OTA later.

Yes
[Moto X General] x000x:
hope this is the place to ask. Is there a generic, stock moto rom that I could use that does not rely on the carrier for updates? i have unlocked the bootloader and will soon set up the custom recovery. my phone currently has 139.4.6.ghost_row.acg.en.us

and is 4.2.2
[Moto X General] mschumacher69:
There is a Retail US ROM that works on the XT1053 and XT1058. U can use it if u have one of those 2 models.
[Moto X General] x000x:
the model i have is XT1050.
[Moto X General] mschumacher69:
This is a CDMA variant, the Retail US ROM is a GSM ROM. There might be a way to switch it to CDMA after flashing it and using the radio files from your original ROM, but mixing different files from different ROMs is not recommended because you would risk bricking when taking an OTA.
[Moto X General] x000x:
I see, so I suppose the only alternative would be 3rd part rom? I'm ok with that, but not sure which (if any) are compatible with the XT1050.
[Moto X General] mschumacher69:
All 3rd party roms should be compatible with all variants because they don't touch your radio files. U can try CM, keep in mind that you would lose all Moto goodies such as Touchless Control and Active Notifications.
[Moto X General] 1dtms:
I have XT1053 unlocked bootloader and rooted, I would now like to install GravityBox for this phone, which instructions has the correct link/version for me to install this?
[Moto X General] samwathegreat:
Search: "Xposed"

Once Xposed is installed, you can download the latest GravityBox straight from Xposed.
[Moto X General] KidJoe:
PMJI,

They all get updates from a carrier except possibly the XT1053 variant which is sold as GSM Dev Edition, the GSM Unlocked (ships with T-Mobile SIM), and GSM Unlocked (ships with Net10 SIM). Even then, that doesn't mean it will always get the update first and the fastest. (it hasn't received 4.4.4 yet)

Per Moto's page, the 4.4.4 update for your ROM is listed as "Coming Soon" https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/94927/p/30,6720,8696 just like the USCellular X 4.4.4 update.

Because you have the XT1050, and its CDMA, trying an alternate rom might be a challenge. You could possibly flash the Verizon XT1060 firmware, but you might need to tweak settings in its Build.Prop, and its CDMA authentication settings might not match. Then there is the question/risks of what will happen IF you run into problems and want to revert to the XT1050 ROM since only the 4.4.2 SBF is leaked. At the same time, since your phone is still on 4.4.2, if you flash everything but the modem files from the VZW 4.4.4 sbf, you still have the potential of build.prop edits, and might encounter other issues (due to miss matched parts on the phone). That brings up the risks of flashing parts of the VZW 4.4.4, with the left over parts of 4.4.2 still there, (i.e. mixed matched parts) when the next OTA comes.

Looking at Moto's web site, I get that updates aren't that timely for you. But unless you want to use a 3rd party rom, or risk the potential issues, you're safest bet is just waiting on the updates for your variant of X.
[Moto X General] x000x:
under "Rooting Unlocked Bootloader" the google drive link to mfastboot(Used for flashing TWRP) no longer works. is there an alternative link somewhere?
[Moto X General] KidJoe:
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
[Moto X General] yayayesi:
mfastboot link

HI! So I was referred to this page because I wiped my system on my moto x and was told that following your steps to return to stock should help fix it. Just wondering about the mfastboot link, it seems to have expired. Any chance you've uploaded it anywhere else? Thanks!
[Moto X General] :
See post right above yours. ?

[MENTION=1872802]dray_jr[/MENTION] anyway to fix link? ?
[Moto X General] abhishekpujar:
I am small time trader, I got the Moto X from sprint and used the GSM unlock guide on xda and unlocked it for GSM use and sold it. After a few days the customer complained that the phone doesn't boot after receiving an OTA update. I asked him to send the phone back to me. I tried to turn it on but it reaches the boot logo and just dies. I CAN access fastboot. The device says UNLOCKED status 3. I tried downloading the latest sprint 4.4.2 sbf and tried flashing it back to stock using both manual and RSD lite both the ways i get the same error, "preflash validation failed". I tried searching for the past 2 days but still couldnt find the exact issue as mine and with so many bricked moto x around im scared to do anything experimental. I am guessing the phone took an OTA to 4.4.4 and thus this problem. Can anyone please help me out here? Thanks.
[Moto X General] :
Chances are the phone was previously downgraded it sounds like. And taking the OTA after is usually an instant brick.

You may need the 4.4.4 sbf files to flash with fastboot or RSDLite. If they aren't available yet... Might need to wait it out I'm afraid.

This thread may help otherwise....

http://xdaforums.com/showthread.php?t=2629057
[Moto X General] yayayesi:
Thanks!

I've downloaded everything, however I do not know if this is a problem or not. I tried running the mfastboot after extracting and placing on my desktop, but it says the program can't start because AdbWinApi.dll is missing. Did I do something wrong or should I continue to step 2?
[Moto X General] :
Best to put mfastboot in the same folder as fastboot, since that is where you need your files you are flashing too.

And mfastboot isn't a file you click.... It's used in a command prompt just like fastboot.
[Moto X General] abhishekpujar:
I wanted to follow the guide in the link you have given but the op's case is different. He was not even able to get into fastboot. I can easily access it. So thought the method would be different for me? BTW thanks for the reply.
[Moto X General] dray_jr:
fixed mfastboot link with link provided by user KidJoe(thanks bro)
[Moto X General] 1dtms:
Is there a way to use the native tethering to tether for XT1053 with unlocked boot loader and rooted?

I was following this thread but it seems that tmobile fixed this to prevent it from working now

http://xdaforums.com/moto-x/themes-apps/tmo-tmobile-native-tether-fix-4-4-2-t2644867
[Moto X General] nish0021:
stock recovery

Can anyone post a link to download stock recovery for moto x xt1052 running 4.4.4??

Any help appreciated!
[Moto X General] mschumacher69:
Download the 4.4.4 zip for your model/carrier from the link below and extract the recovery file from it:

http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
[Moto X General] nish0021:
Can u plz tell me which one is the Asia retail model?

Sent from my XT1052