Skip to main content

Bricked (and unbricked) my Moto X 2nd Gen XT1095

I have recently been having issues with my Moto X receiving incoming calls.  Even though the same person that would call me could text me at the same time frame.  Fortunately I have a Nexus 6... unfortunately I travel weekly for work and can't deal my phone's bullshit right now.  So, I wipe my Nexus, re-image it with shamu, install all my apps, Google Authenticator, etc.. configure all logins and authentication.  Then I realize why I had been using my Moto X instead of my Nexus 6.  Advantages that the Moto X have: size, nuance functionality (karate chop flashlight, auto-silence off-hours, etc...).  Motorola does some cool stuff.

Anyhow.. .one not cool thing about Motorola is the guarded approach to distributing their Images.  (which, there may be a legitimate reason for that.... so, I will remain somewhat neutral about the subject).

I managed to find an image to use and made a few huge assumptions:
  • that an invalid image will not load
  • that a non-stock image will NOT allow Android Pay and/or Google Wallet to work

One big mistake I made (lesson I learned) the system image file does NOT (or should not) be a single file.  I first attempted to concatenate all the sparsechunk.x files to system.img and flashed that way.  No bueno!

mkdir -p ~/AndroidImages/MOTOX
cd $_
wget http://path.to.rom/
unzip VICTARA_TMO_XT1095_6.0_MPE24.49-18_cid9_CFC.xml.zip 


fastboot oem fb_mode_set
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
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier att
fastboot oem fb_mode_clear


NOTE:  I am not 100% positive that "att" is the correct carrier string.








Comments

Post a Comment

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...
2 comments
Read more

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.
Post a Comment
Read more

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more