yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mdecker:
So since yesterday I went back to CM 10.2 ROM and I'm able to send and receive calls but then, it may be spotty.

OEM USB cable when I'm at my computer plugged into a USB Hub (one port for charging) and at night I have it plugged into a dock (forget what brand, got it free when my bro ordered one for his HTC ONE and they shipped one for an S4)

This is what I figured, just hoping it could have been software related.

Found a used Galaxy Nexus cheap so I ordered one of those... should tie me over till I'm ready to get a better phone next year (or later).

Thanks for the help.
[Moto X Android Development] mattlgroff:
#include <external/cyanogenmod/std_disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

-----------------------

PLEASE USE THE NEW RECOVERIES BY DHACKER29 THIS IS DISCONTINUED

CWM

TWRP

Discontinued - Downloads and Links:

Unofficial CWM Recovery 6.0.3.6 for Moto X --- 8/25/2013 WORKING!

Mirror^

Superuser by Koush -- If you want to root.

SuperSu by Chainfire -- If you want to have root. Pick this one, or the one above. Not both.

Stock Motorola Recovery for Moto X --- If you want to return to stock, or take OTA's.

Motorola Fastboot Files --- Windows/Mac/Linux

Motorola USB Drivers 6.2 [Windows 32/64]

Thanks to:

Google for Android.

Koush for CWM.

Jackpot Calvin for Ramdisk fix.

rob43 for pointing out Fstab error.

hidea for testing over XDA and Skype.
[Moto X Android Development] gabo_e30:
Hey Matt,

Nice to see you again.!

So how do u unlock the bootloader? Is it as simple as a nexus 4 or like the Atrix HD?
[Moto X Android Development] mattlgroff:
It's done with the Official Motorola Unlock Tool on their website. You enter the 'get_unlock_data' and get a code emailed to you.
[Moto X Android Development] djpry:
now thats what we call superfast
[Moto X Android Development] kornklown69:
was this done on an at&t model?
[Moto X Android Development] mattlgroff:
Verizon Engineering unit.
[Moto X Android Development] kornklown69:
dang I was hoping at&t with all the info about bootloaders being unlockable :(
[Moto X Android Development] ludeboy:
Does this work for you? It just boots into the stock recovery.
[Moto X Android Development] mattlgroff:
It does not work yet, as it says next to the download link.
[Moto X Android Development] ludeboy:
No offense, but why did you release this if it doesn't work?
[Moto X Android Development] mattlgroff:
To get it tested and allow anyone wishing to collaborate to do so.
[Moto X Android Development] ludeboy:
I don't understand what there is to test since you already said it doesn't work. Perhaps you should change the OP so it's a bit more clear of your intentions.
[Moto X Android Development] jmill75:
Did you not see the large work in progress header? As he said this is for anyone to work or test on. Did you come here to help or complain?

Obviously you do not know who he is. Great to see this is being worked on.
[Moto X Android Development] mattlgroff:
I posted this before it was tested. Now its been edited.

I'll be posting my test branches in github and will link in this thread. Anyone willing to contribute is more than welcome.

So far the normal methods for booting CWM are not doing so well on the Moto X. Might require something proprietary.

EDIT: Added the Github to the OP.
[Moto X Android Development] ludeboy:
Thank you very much. When I saw this thread it looked like you had already tested it. It was confusing when it said "tested. does not boot." so I tried it out to test it. I'm all for development but I was misled in your original post so thank you for editing it.

---------- Post added at 05:30 AM ---------- Previous post was at 04:56 AM ----------

Please don't misunderstand me. As a person that donates, I do appreciate all developers and I will open my wallet for my appreciation. I just don't want anyone to be mislead and blame you for any wrong-doings. If you need a tester, don't hesitate to hit me up! There aren't many of us (yet).
[Moto X Android Development] matt99017d:
I'll be willing..... Permitting we can find a work around for att.... If something happens I have insurance and my AHD_MAXX as a backup.
[Moto X Android Development] thund3rbay:
Thanks matt for you great JOB !
[Moto X Android Development] mk1151:
mattlgroff - great to see you working on the moto X

There are many that are less concerned with bootloader than they are with root (myself included). I know you're working off a Verizon flavor, I'm on AT&T - what do you think the chances are of getting root without cracking the bootloader open?

I did a few searches and haven't seen anything come up.

Thanks again for your hard work.
[Moto X Android Development] JackpotClavin:
Possible fix

Hey, I don't have a Motorola X, but I do have a Motorola Droid Razr M and I've been experimenting with getting the Moto X sbfs to boot on my Razr M, (which I have), but I ran into issues with the devtree loading up the touch firmware, so I'll have to wait for kernel source.

However, I did fool around with the boot images for the Motorola X and realized that the ramdisk offset isn't set in your BoardConfig.mk

Try adding:

BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x02200000

And rebuild
[Moto X Android Development] mattlgroff:
Thanks, I'll have to give it a shot! Added to the github.

Also, the DROID Ultra kernel source is out, might be of some help.

http://sourceforge.net/projects/ultra.motorola/files/XT1080-XT1030/

EDIT: Updated OP with new build of CWM to try out.
[Moto X Android Development] rob43:
Your recovery.fstab is completely off. The first parameter is not for the device path.
[Moto X Android Development] mattlgroff:
Transposed them, my mistake. I was thinking halfway between the old version of .fstab and the new one (seen here). Fixed and gave credit to you in the commit.

EDIT: OP updated with latest build.
[Moto X Android Development] JackpotClavin:
Did it actually boot with the ramdisk address?
[Moto X Android Development] mattlgroff:
No one has tested it yet to my knowledge. We are relying on Rogers Moto X users who have unlocked, since the AT&T Retail is not unlockable. Hopefully we'll know soon enough.
[Moto X Android Development] JackpotClavin:
Booted on my Droid Razr M, so it should boot on everybody's Moto X/Ultra/Maxx devices as well. The recovery fstab is borked though on the build in the OP. I'll pull one off the stock recovery and pastebin it here in a sec

http://pastebin.com/9YDxeTgF

I just added /dev/block/platform/msm_sdcc.1/by-name/ in front of the device name so instead of it saying just boot, it says /dev/block/platform/msm_sdcc.1/by-name/boot

That's what it should look like for a recovery built with CM10.1 (Android 4.2) sources
[Moto X Android Development] mattlgroff:
Its currently set for Moto X Dev blocks instead of /by-name/ as it was previously, so it may be fine on Moto X. Let's hope :)

Getting it booted though is excellent! Thanks again for the tip.
[Moto X Android Development] JackpotClavin:
I looked at your recovery.fstab sources and they looked good. For some reason your recovery.fstab from the latest image in the OP looks like this: http://pastebin.com/bu0Egs4a, so that xda garbage probably screwed with the recovery parsing the fstab. Clobbering and building once again should get everything 100%
[Moto X Android Development] mattlgroff:
Damn raw github download. I'll have to rebuild when I get back.
[Moto X Android Development] mattlgroff:
EDIT
[Moto X Android Development] hidea:
I just unlocked my Bootloader. Rooted the phone.

If it's not *too* dangerous, I'm willing to try this!
[Moto X Android Development] mattlgroff:
You can flash back the stock recovery.IMG if it fails :)

http://batakang.com/ftp/recovery/ghost/stockrecovery.img
[Moto X Android Development] :
Tryed on my moto x ... flash succeful ... can enter to recovery... get error on the screen ... some malformated recovery.fstab...

Can't mount sd card...

formatting work great ...
[Moto X Android Development] mattlgroff:
Could you pull the recovery.log?

adb pull /tmp/recovery.log
[Moto X Android Development] :
no problem i will try this afternoon or tomorrow morning...

I have just make a noob error ;p Try to flash the att firmware with 10% battery ... phone is bricked... but pleasant surprise the phone charge in the fastboot mode... ( battery : OK (charging) ) i will leave my phone charge and after i try to recovery the recovery.log
[Moto X Android Development] mattlgroff:
That's nice of Motorola to have charging in fastboot, took them way too long!
[Moto X Android Development] :
Yes this is very nice... and a good surprise...
[Moto X Android Development] mattlgroff:
I wonder if userdata being 'f2fs' filesystem would cause an issue with CWM. Certainly haven't seen that filesystem used with it personally.

EDIT: Found another fstab issue, building a new one and will post to OP.
[Moto X Android Development] hidea:
Any specific testing method you'd like us to run?
[Moto X Android Development] mattlgroff:
Try wiping cache, if all seems to work fine and not show errors (and buttons work) then just let us know your results please.

Thanks!
[Moto X Android Development] hidea:
weird. I can't reboot normally from Fastboot. Or booting into Recovery. I have to manually press the power button to boot the phone into the OS

Seems that I can't format Cache.

ends there.

Buttons work.
[Moto X Android Development] mattlgroff:
Please see if adb works or if you can pull the /tmp/recovery.log so we can see the full error.
[Moto X Android Development] hidea:
Starting recovery on Sun Aug 25 00:01:43 2013
framebuffer: fd 4 (720 x 1280)
CWM-based Recovery v6.0.3.6
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p33 (null) 0
2 /cache ext4 /dev/block/mmcblk0p36 (null) 0
3 /recovery emmc /dev/block/mmcblk0p34 (null) 0
4 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
5 /data f2fs /dev/block/mmcblk0p40 (null) -16384
6 /system ext4 /dev/block/mmcblk0p38 (null) 0
7 /modem ext4 /dev/block/mmcblk0p1 (null) 0
8 /customize ext4 /dev/block/mmcblk0p39 (null) 0

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
Warning: No file_contexts
Warning: No file_contexts
I:device_recovery_start()
Command: "/sbin/recovery"

ro.boot.hardware=qcom
ro.boot.emmc=true
ro.boot.serialno=
ro.boot.baseband=msm
ro.boot.mode=normal
ro.boot.bootloader=0x3070
ro.boot.cid=0xE
ro.boot.hwrev=0x8300
ro.boot.radio=0x1
ro.boot.modelno="Moto
ro.boot.device=ghost
ro.boot.secure_hardware=1
ro.boot.write_protect=0
ro.serialno=
ro.bootmode=normal
ro.baseband=msm
ro.bootloader=0x3070
ro.hardware=qcom
ro.revision=33536
ro.emmc=0
ro.factorytest=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=JDQ39E
ro.build.display.id=ghost-eng 4.2.2 JDQ39E eng.mattlgroff.20130825.000839 test-keys
ro.build.version.incremental=eng.mattlgroff.20130825.000839
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Sun Aug 25 00:09:08 CEST 2013
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=mattlgroff
ro.build.host=ROM-*****
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=ghost
ro.product.device=ghost
ro.product.board=ghost
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=ghost
ro.build.description=ghost-eng 4.2.2 JDQ39E eng.mattlgroff.20130825.000839 test-keys
ro.build.fingerprint=Android/ghost/ghost:4.2.2/JDQ39E/eng.mattlgroff.20130825.000839:eng/test-keys
ro.build.characteristics=default
ro.cm.device=ghost
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
[Moto X Android Development] mattlgroff:
I don't see the error happening here, just the boot up. Could you pull from the recovery after trying to wipe the cache please?

EDIT: Did some testing with hidea and made some progress. Internal SDcard is now working fine, and I'm working on trying to figure out fixes for the other errors.
[Moto X Android Development] :
I have try the new version... Try to format cache... Phone freeze and can t get recovery.log
[Moto X Android Development] mattlgroff:
Could you run

adb shell tail -f /tmp/reco*

while in Recovery,but before wiping cache? It might tell us the issue.
[Moto X Android Development] hidea:
Is that the same build OUDHS we tested last night?

I'll run the same code before wiping cache. I'm good to test again tonight!
[Moto X Android Development] mattlgroff:
Made a change to touch_dev.idc, so it's a bit different.

Thanks again.
[Moto X Android Development] hidea:
Sorry, no dice. Touch is still non-responsive!
[Moto X Android Development] mattlgroff:
OK.
[Moto X Android Development] :
Sorry i am not a home again this afternoon ... i will help you later... thanks to you for your great job
[Moto X Android Development] mattlgroff:
Updated OP :) - working.
[Moto X Android Development] pixeldrew:
Nice work, what is held on userdata/data anyway?
[Moto X Android Development] mattlgroff:
User installed apps, contacts, texts, recent calls, and basically anything else that does not come with the phone from the factory.

In the meantime I'd recommend using an app like Helium or TitaniumBackup to back up those types of things to the cloud, since there is no external-sdcard.. Currently this CWM can create the backup, 'data.f2fs.tar' but it cannot be restored. This is due to CWM not yet supporting the f2fs filesystem that Motorola is using for the /data/ partition in this phone.

TWRP looks like it does support it, but I'm having compilation problems with it.
[Moto X Android Development] hidea:
Well, TiBackup is able to read the Nandroid backups.

Here's the content of my data backup.
[Moto X Android Development] mattlgroff:
Great work-around :good:
[Moto X Android Development] :
Great job matlgroff and hidea !

---------- Post added 26th August 2013 at 12:04 AM ---------- Previous post was 25th August 2013 at 11:56 PM ----------

Just flashed the SuperSU binarie...

All work great !

Prefer this method as the boot.img ...
[Moto X Android Development] mattlgroff:
Sent this to hidea, but figured I'd post this as well. Working on getting the /data/ backups to restore with this test build:

Download CWM F2FS Test

The problem was most likely that the nandroid-restore function was ignoring /data/ backups because it's an f2fs and not one of their listed filesystems.

const char *filesystems[] = { "yaffs2", "ext2", "ext3", "ext4", "vfat", "rfs", NULL };

As previous tests, please provide the /tmp/recovery.log if there is any issues (No File_Contexts does not count ;) ).

adb pull /tmp/recovery.log

Also, if someone can grab the /tmp/recovery.log from this TWRP test build, that will also help out. - Touch is not working, it's an f2fs compatibility test.

Download TWRP F2FS Test
[Moto X Android Development] hidea:
CWM_test_f2fs yields excellent result. I was able to create a new backup (.tar) and restored data with it.

TWRP, not so much. It's still not recognizing the f2fs format.
[Moto X Android Development] jadsru1:
can't unlock ATT ??

I tried the moto unlock site but doesn't seem to work with AT&T for now. Curious it unlock vzw phones but not ATT when it's not even out yet on big red :(
[Moto X Android Development] mattlgroff:
The Official tool does not unlock Retail AT&T and Retail Verizon models. It will unlock any other model of Moto X.
[Moto X Android Development] ludeboy:
Does this work on your VZW unit? Getting the same thing as the prior version.
[Moto X Android Development] mattlgroff:
That was papi92's unit, but he no longer has it. It was an Eng unit and could be unlocked, and now he has a locked AT&T model.
[Moto X Android Development] ludeboy:
I just want one that works with the VZW ENG unit :D
[Moto X Android Development] mattlgroff:
Are you saying this doesn't? They should use the same kernels.
[Moto X Android Development] ludeboy:
It boots up to an open chest android with "No command" at the bottom. Holding up and pressing power takes me to the stock recovery.
[Moto X Android Development] mattlgroff:
After flashing this recovery in fastboot go directly into Recovery. If you boot the stock recovery will re-write because of /system/etc/install-recovery.sh.

You could also just remove that file with root while booted, so it's not a future problem for you flashing a Custom Recovery.
[Moto X Android Development] ludeboy:
I do boot into recovery right after fastboot and it just boots up normally into Android! :mad:
[Moto X Android Development] mattlgroff:
Then remove install-recovery.sh with root... the recovery should boot fine on your device, it's just your device keeps wiping it off! :rolleyes:
[Moto X Android Development] ludeboy:
lol. i'm trying to get cwm so that i can root my phone.

doh! i'm such an idiot. i been pressing the power button instead of up for select. all good now. thanks!
[Moto X Android Development] mattlgroff:
Flash in fastboot.

Unplug the device from the computer.

Force power it off (Power + Volume Down for 8 seconds, if its the same as previous Moto phones).

Go into Recovery directly. Do not pass go, do not collect $200. If you cannot get this to work then use the "rooted boot.img" in this Development section and get root before you do it, I left exact directions in the OP (edited it).

Install-recovery.sh is extremely annoying to explain, and doesn't work the same on every phone for some reason.
[Moto X Android Development] ludeboy:
I installed SuperSU.zip in recovery. Aw snaps!
[Moto X Android Development] mattlgroff:
"Fixed" the No file_context message.
[Moto X Android Development] flashallthetime:
Seems as though I can't unlock the boot loader, just tried and it said I can't unlock it, I'm with rogers canada:eek::eek::eek:
[Moto X Android Development] hidea:
Did you go through Motorola's website?
[Moto X Android Development] flashallthetime:
Bigger yapper on that one:)
[Moto X Android Development] mattlgroff:
Try again but removing all spaces from the string, including new lines. One continuous thing.
[Moto X Android Development] flashallthetime:
I'll was just going to do that, I'm such a frigging , yap just got the unlocking code sent to me

So its now unlocked , I guess the next step is to run recovery, do I run it through adb ?
[Moto X Android Development] hidea:
So… you unlocked your bootloader then.
[Moto X Android Development] mattlgroff:
Boot into fastboot mode if you want to flash it without already having root.

adb reboot bootloader

^^but you should learn the device button combos
[Moto X Android Development] flashallthetime:
Oh yes, easy breezy
[Moto X Android Development] hidea:
All rooted then, good sire?
[Moto X Android Development] flashallthetime:
No just unlocked the bootloader, tomorrow I root it, well its rooted now , thank to the op for this:D:D:D I'll take you out for a Canadian beer

:beer::beer::beer:
[Moto X Android Development] dew.man:
Got the recovery installed and did a backup. All good so far. But now I can't find the actual backup files. I browsed /sdcard/clockworkmod from my computer, and there's only a tiny 135 byte file there. I tried adb shell ls and don't see anything at all.

I know I'm just being stupid and overlooking something simple, but I've been up most of the night and everything is turning blurry so any help would be appreciated...
[Moto X Android Development] hidea:
You could use one of the Play Store apps to manage your backups:

https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore.pro

https://play.google.com/store/apps/details?id=com.free.alpha.cwmbackup
[Moto X Android Development] flashallthetime:
Works as I see a backup of over 1 GB now
[Moto X Android Development] dew.man:
That's the part I don't get - TiBackup finds the backup and shows me contents, but I can't seem to find it on the sdcard. Not even with Root Explorer!

So where is CWM putting the backup?
[Moto X Android Development] flashallthetime:
I believe I found it with root explorer, look for mnt folder

Sent on my Moto X
[Moto X Android Development] dew.man:
Sure enough it's buried in /mnt/shell/emulated
[Moto X Android Development] mattlgroff:
Added that information to the OP.

Thanks!
[Moto X Android Development] snrbobo:
Worked like a charm! Unlocked bootloader, and rooted device! thanks mattlgroff!
[General Questions and Answers] nikk95:
Hello Every on I have a Motorola Droid Razr XT910 with 4.1.2 EU.Retail f/w so i wanted to root it when i followed the steps and root it it gets stuck on boot loop after the restart... i reflashed the f/w and tried again via another method no avail :( can anyone help me with this stupid problem and i tried with fully charged battery :(
[Nexus 7 (2013) Q&A] subnormyle:
Does anyone know if there is a way to disable the rotation of the navigation bar on CM 10.2?
[Sprint LG Optimus G] griffstert:
I was originally on a CM rom but decided to give a stock based rom a try and it flashed and booted successfully. Now I want to go back to CM and flashed another CM rom but now it won't boot. It flashes the LG logo for a half a second and then just hangs at a blank screen. Any ideas?
[Sprint LG Optimus G] kmull4:
I encountered something like that a while ago. I solved it by shutting it down (hold power button for 20 or so seconds) then let it sit for about an hour.. It booted up after that. Hopefully it works!

If not, you might have to lgnpst
[Sprint LG Optimus G] prowlingfox:
Please provide more information so we may better help you...

Which AOSP-based ROM did you flash before you encountered the problem?

Did you wipe everything before flashing?

Did you flash anything in addition to the new ROM?

Are you still able to get into TWRP Recovery?
[Sprint LG Optimus G] griffstert:
Yes, I'm still able to get into twrp but restoring now fails.I went from BeanStalk to Vectus Slim to NexOGen to SuperNexus (never booted), now I can't flash any stock or cm based rom without it hanging. I always wipe system, cache, dalvik, and data before flashing into another rom. I only flash the rom and gapps.
[Sprint LG Optimus G] griffstert:
do you guys think if formatting the card and sideloading a rom might help?
[Sprint LG Optimus G] EFEXR:
Did you ever flash a teenybin?
[Sprint LG Optimus G] griffstert:
I don't believe I have. I never had any issues until now.
[Sprint LG Optimus G] griffstert:
I found this thread which seems similar to the problems I'm having. It seems like formatting data could fix the problem. If not, i'll try LGPNST and flashing teenybins next.

Thread: http://xdaforums.com/showthread.php?t=2342985&page=2
[Sprint LG Optimus G] EFEXR:
I believe flashing a teenybin was recommended for CM so occurances like the LG logo to black screen would not occur. This happened to me, so I know by experience. A lot of people dont do it because it seemed to complicated and flashed CM and nothing happened, most likely it will happen to them sooner or later.

Good luck with the teenybin, I'm pretty sure that will solve your problem, as that solved my LG logo to black screen problem months ago