Database Users

[REF]The Complete Moto X Guides/Information Thread

So this thread started as just a guide for root but with all the questions being asked lately I have decided to turn it into a full blown info thread this is going to take some time and some section might be empty so please bare with me.
Device Variants
(this display is not 100% correct still working out some issues and info!)
XT1049 - Republic Wireless
XT1052 - European - Sim ?
XT1053 -T-Mobile US, Dev Ed
XT1055 - US Cellular - Sim ?
XT1056 - Sprint - Sim Unlocked
XT1058 - AT&T, Rogers, Claro, Movistar, Vivo, Oi, TIM - Sim Unlocked
XT1060 - Verizon - Sim Locked
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What Devices Can Unlock There Bootloader
In this section we are going to go over what devices can have there bootloader unlocked and what ones can't this is very simple.
(if it dose not says Dev Ed next to the carrier then I am talking about consumer model.
Locked Bootloader – Verizon, AT&T, Republic Wireless
Unlockable Bootloader – Sprint, US Cellular, T-Mobile, Rogers, all Dev editions
Personally these are the ones I am not sure about yet so if you have one please let me know so I can add them.
? - Claro, Movistar, Vivo, Oi, TIM
If you want to check to see if your device is unlockable please go to motorola's website below
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Downgrading Bootloader
there has been a lot of issues around this process so I want to post the info right at the top so people stop bricking there device and we can get past this
here is a quick list of what can be done with bootloader downgrading
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
here is a thread dedicated to the discussion of bootloaders and modems
http://forum.xda-developers.com/showthread.php?t=2635366
Informative Thread Google Cached
READ CAREFULLY
WARNING
DO NOT FLASH THE NEW 4.4.2 SBF FIRMWARE UNLESS YOUR CARRIERS FIRMWARE IS AVAILABLE.
FOLKS HAVE FLASHED OTHER CARRIERS FIRMWARE AND AS A RESULT THEY HAVE NO DATA CONNECTION,
YOU CAN NOT DOWNGRADE, SO IF THIS HAPPENS CHANCES ARE YOU'LL HAVE A PHONE THATS UNUSABLE UNTIL AND IF YOUR CARRIERS SBF SHOWS UP.
THERE IS A CHANCE THAT EVEN AFTER YOU FLASH THE CORRECT FIRMWARE, YOUR RADIO SIGNAL MAY NEVER WORK
I will not in any fashion help anyone to upgrade nor downgrade their moto, this thread is for info only. I personally will not take any responsibility for any issues. You own it ., you alone broke it
Motorola bootloader unlocking website https://motorola-global-portal.custh...-your-device-a
WARNING WARNING
DO NOT FLASH ANY OTA 4.4.2 ,OTA ROM OR ANY SUCH MEANS OF UPGRADING WITHOUT HAVING YOUR SPECIFIC CARRIER 4.4.2 SBF FIRMWARE AS A BACK UP
WARNING WARNING WARNING
IF YOU HAVE A LOCKED BOOTLOADER ONLY FLASH YOUR SPECIFIC CARRIERS SBF FIRMWARE, OTHERWISE YOU WILL END UP WITH A HARD BRICKED DEVICE
************************************************** ********
If you Frankenstein a way of downgrading do not post it here, this thread is not about tricks, hacks or any such garbage. This thread is to inform folks in the correct way of maintaining your moto to work. Plain and simple
There's a tremendous amount of firmware flashing which is causing harm to many users phones.
Realize that having a unlocked boot loader moto, regardless if its a DE will also suffer from hard bricks.
Unlocked boot loaders can flash other variants system.img's without to many issues
Modems are a different story, some user report no data with European modems, so I suggest using your specific carriers modems
Stay away from motoboot.img (boot loader) or gpt.bin(partition table) be warned
Remember you and you alone are responsible for any hard bricks
********************************
This is a simple chart what can and can't not be downgraded, Thanks to Dray_jr 
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
************************************************** **************
WARNING if you manage to flash back to 4.4 or even 4.2.2 with the new 4.4.2 BOOTLOADER DO NOT UNDER ANY CIRCUMSTANCE ACCEPT ANY OTA, YOU WILL HARD BRICK YOUR DEVICE, PROOF BELOW
Quote
******** "it was running on 4.4.2 software, then i downgrade to 4.2.2. all was fine, but OTA killed it.
So after that, i read that 4.4.2 instaled new bootloader =( that cant be downgraded, and can bricked the phone, it was my mistake =(
So i think i should sent it to Motorola and if i lucky one, they should repair it, or resend new one. or if bad luck i will throw it to the trash =)"*******
Files inside sbf firmware:
Motoboot.img (bootloader)
gpt.bin ( Partition table)
NON_HLOS (modem)
System
Recovery
Bootloaders:
4.4.2 North , Central & South America:
Rogers 30.B4
US Cellular 30.B4
Brazil Retail 30.B4
T-Mobile 30.B4
Sprint 30.B4
Europe:
UK 30.B3
Modems:
Rogers 4.4.2
Stock Recovery:
Rogers Stock Recovery 4.4.w
4.2.2 pre camera boot loader 30.70
4.2.2 post camera bootloader 30.71
Issues:,
Confirmed by Steve x , you can not downgrade bootloader from 4.4.2
WARNING WARNING
The Brazilian phone and central American phones will not have a data connection with the uk or DE firmware, so do not flash any European firmware, be warned
I will credit correct posters when i get back to my pc
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Custom Recovery's
Now this is fairly simple there are 3 custom recovery options for us right now 2 for unlocked bootloaders and 1 for locked
here are the options we have and links to there threads for info and downloading
TWRP
http://techerrata.com/browse/twrp2/ghost
CWM
http://forum.xda-developers.com/showthread.php?t=2612149
Safestrap
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How to Take OTA on Root Device
flashallthetime said:
Ok tired of answering thus question constantly
To accept and flash an ota you must have the following phone set up
1) Stock recovery. No it will no flash with twrp or cwm
2) All root removed completely from your system
3) Xposed framework completely removed from your system, uninstalling will not work,you need to flash the xposed Disabler zip
4) Any mods to any system file must be reverted to stock
5) Running the stock odex ROM
6) Any system apps frozen must be unfrozen
If you have at any point of time flashed any 4.4.2 firmware along with the boot loader 30.B3 or 30.B4
DO NOT FLASH THE OTA, YOU WILL HAVE A HARD BRICKED MOTO
HOPE THIS HELPS
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting Locked Bootloader
[SIZE="3"]Step one[/SIZE]
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
RockMyMoto(4.2.2 root exploit)
http://forum.xda-developers.com/attachment.php?attachmentid=2369524&d=1383521170
Cydia Impactor(Required for 4.2.2 root exploit)
http://www.cydiaimpactor.com/
MotoWpNoMo(Kill Write Protect on Locked Bootloaders)
Win - http://www.rumrunner.us/MotoWpNoMo-0.0.4.zip
Linux - http://www.rumrunner.us/MotoWpNoMo-0.0.4.tar
SlapMyMoto(4.4 Root exploit)
http://forum.xda-developers.com/attachment.php?attachmentid=2463879&d=1387477699
RSD Lite(Used for downgrading to 4.2.2 camera update)
https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
4.2.2 Camera Update Firmware(download firmware for your device)
http://forum.xda-developers.com/showthread.php?t=2568334
Below are Complete Kits that i put together for Each Carrier Moto X
it contains all the files needed to Root/Downgrade/Return To Stock or what ever you need to do.
I will be posting Links as i upload them.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step two
Downgrade to 4.2.2 Camera Update
If you are on the 4.4 update already your are going to have to downgrade your device to 4.2.2 camera update. The best way to do this is to follow the guide in the link below.
Ok so more and more people are Bricking there phone with RSD Lite so i am going to add in the guide to manually flash all the img's because i no longer will refer to RSD Lite for the fact that i dont find it safe anymore.
To Flash back to 4.2.2 Camera Update Manually Follow the Below Steps it is very simple.
1. download the correct 4.2.2 CU firmware for your Carrier
2. open the .zip files and extract the files into your folder with ADB and MFastBoot.
3. Boot your phone into the bootloader
4. Run the below commands one by one
Code:
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
i recommend wiping your device also but that is up to you
Code:
fastboot erase userdata
fastboot erase cache
Now it is time to move on to Step three and root your device
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Three
Rooting 4.2.2 camera update and disabling write protection
Before you can start to root 4.4 you first need to root 4.2.2 camera update and disable write protection. below are two links the first one is to root 4.2.2 camera update and the second one is for disabling write protection
4.2.2 Camera Root Exploit
http://forum.xda-developers.com/showthread.php?t=2509590
Disable Write Protection
http://forum.xda-developers.com/showthread.php?t=2551113
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Four
Returning back to stock again so you can start rooting 4.4
i know you have already done this but in order to root 4.4 you have to be completely stock. So use the same guide and firmware as the last time to restore your device to stock again i no longer will recommend RSD Lite so below is the steps to manually flash your device back to stock
1. download the correct 4.2.2 CU firmware for your Carrier
2. open the .zip files and extract the files into your folder with ADB and MFastBoot.
3. Boot your phone into the bootloader
4. Run the below commands one by one
Code:
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
i recommend wiping your device also but that is up to you
Code:
fastboot erase userdata
fastboot erase cache
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Five
Root 4.4 Finally
Now that we are back to 4.2.2 camera update it is finally time to start the process to root 4.4 just follow the guide below and you will finally have your device on 4.4 with Root
4.4 Root Guide
http://forum.xda-developers.com/showthread.php?t=2538896
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How To Unlock Your Bootloader
Unlock your Bootloader
This Will Erase your Data/ Factory Reset your phone
In order to install TWRP/CWM and SuperSU you need to first unlocked your boot loader. below is a link to Motorola's guide to do just that.
Click on the link below and pick your Moto X by what carrier you are with
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215/action/auth
im going to try and do this the best i can but no matter what i do your going to have to go to the moto website to get the unlock key
download the SDK and install it.
locate ware it was installed normally (C:\Program Files\Android\android-sdk)
open Command Prompt and type
Code:
CD C:\Program Files\Android\android-sdk\platform-tools
put phone into bootloader
type below commands in CMD
type
Code:
fastboot oem get_unlock_data
it should come back with something like this
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Now we need to remove all the (bootloader) and make the key into one line
we then need to paste this into the box on the bottom of the Moto unlock page and hit the button "Can my Device be Unlocked"
if your device can be unlocked you need to accept the license agreement and then click the button to request your key. It will then email you your unlock key.
Copy your unlock key then click the link Step 3
now if you left your device connected and everything ware it was then great if not we need to put are phone back into bootloader and open a CMD and CD it to the same directory as before.
then type
Code:
fastboot oem unlock UNIQUE_KEY
ware Unique_key being the code you copied from your email.
now your bootloader is unlocked.
Sorry this guide is not great but it is the best i can do for the fact that you have to be on the moto website to get your unlock key. i hope this helps somewhat.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting Unlocked Bootloader
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
TWRP Recovery
http://techerrata.com/browse/twrp2/ghost
CWM Recovery
http://forum.xda-developers.com/showthread.php?t=2612149
SuperSU
http://download.chainfire.eu/supersu
MFastboot(Used for flashing TWRP)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
How to install TWRP/CWM Recovery and SuperSU
Now that you have your bootloader unlocked its time to install are custom recovery and SuperSU so we have Root
Before we worry about that phone please make sure you have installed the SDK and then copied the mfastboot files over to the directory your ADB is in.
also before we put the phone into bootloader mode we need to copy the SuperSU.zip over to are phone
Now that we have all that moved over everything that we need. it is time to get are phone into the bootloader you can do that by turning off your phone, Then turning it back on while holding volume down + the power button.
once into the bootloader plug your USB cable in and set your phone down.
now we need to open a CMD window and CD to the directory ware we placed the MFastBoot files.
this is my location but i use the Moto X toolkit yours is going to be ware ever you install the SDK
so in the CMD window type the command below but change the path to ware your files are located
Code:
CD C:\Program Files\stillthisguy\Moto X Toolkit
now that we are in the right location it is time to install TWRP/CWM we are going to do that by typeing the commands below
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
or what ever the name of your recovery img is
as soon as you type the above command to flash TWRP/CWM we need to boot the phone into recovery before we let it boot to android we can do that via the buttons below.
click the Volume - button until it highlights Recovery then press the Volume + button to select it and it should boot into recovery.
If you do not immediately boot your phone into recovery after you flash it, recovery wont work.
here is a step by step that might help everyone abit
Cozume said:
Try this:
1) Put device in bootloader mode while not connected to PC using the buttons (Volume Down + Power);
2) Connect device to PC using USB cord;
3) mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
4) fastboot reboot-bootloader
5) Disconnect device from PC;
6) Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and then pressing the Volume Up button to select the recovery mode; and
7) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
If that doesn't work, repeat but omit step 4.
Click to expand...
Click to collapse
Now click on Install and find your SuperSU.zip that we copied over and click on it and install it. when it is done installing you can reboot your phone and enjoy having root access.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
For firmware Download pick what firmware you want from the link below
http://sbf.droid-developers.org/phone.php?device=0
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
Code:
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 flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
Enjoy
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Full OTG support on 4.4.2 or older builds via Qualcomm settings
aviwdoowks ask for me to include his guide in my post so here yall go if you need support the link below is to the original thread
OP Thread
Update
This is, at least, a stock/rootless solution. The OTG/UsbDisk is now system wide! /storage/UsbDisk! Root Explorer/Explorer (free)! The standard issue "Documents" apk browses it too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You may use many apps to browse your new /storage/UsbDisk, this is a good one.
https://play.google.com/store/apps/details?id=fm.clean
You need to create a shortcut to qualcomm settings.
The: com.qualcomm.qualcommsettings.apk is in your system/app!
I posted it for custom rom users, but it will not show up even if you install it.
I use Super Manager donation. The free version works too. (apk manager, choose activity button. The gear: launches the activity, the arrow creates a shortcut on homescreen.). I use Xperia launcher.
Then enable usb mass storage and OTG mode - peripheral. The usb will get reset but there is no need to keep it on. OTG mode sticks. Edit: try it w/o the usb checked it may not be needed at all.
Done.
Go File manager, /storage. Permissions will be rwx even from the free version.
You have a new mount/unmount option in settings/storage:
Be sure to use (^ above button) the unmount command as forgetting you have a write operation in progress and yanking out the otg adapter can trash your SD card!
I do not wonder why Moto did not enable this ability!
No need to download the attached apk. It is in your system apps already. But some custom ROMs may not have it.
USEonlyIFnotONyourPHONE.4.4.2com.qualcomm.qualcommsettings.apk
USEonlyIFnotONyourPHONE4.4.0.com.qualcomm.qualcommsettings.apk
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Credits
jcase
beaups
TechSavvy2
zhp pilot
Hashcode
Phil3759
flashallthetime
aviwdoowks
if i forgot anyone please let me know

Nice guide! First to reply, lucky!
Sent from my XT1058 using Tapatalk

I guess it would be nice to add the root tutorial for unlocked bootloader, even though it's a quick process. Some people might have little worry about voiding warranty.
Sent from my Moto X

RenSoAbrupt said:
I guess it would be nice to add the root tutorial for unlocked bootloader, even though it's a quick process. Some people might have little worry about voiding warranty.
Sent from my Moto X
Click to expand...
Click to collapse
ok sounds good i will add it
guide for unlocked Bootloaders has been added i think i got everything right lol. please let me know if there are any error's or is i am missing anything. enjoy

Thanks much for this.
Wish things were a lot more straight forward though.

Sorry but I'm not going to grab someone's guide and remake it most of the guides I linked to the creator has done a very good job with them so I want them to get the credit for it
Sent from my XT1056 using XDA Premium 4 mobile app

Yes! This is exactly what I needed. I had the jist of what needed to be done, but had trouble wrapping my head around the correct order of all the different steps. When a root process requires links to 10 different guides, you really need a Master guide like this. Thanks
Sent from my Nexus 7

No problem man glade it helped
Sent from my XT1056 using XDA Premium 4 mobile app

dray_jr said:
No problem man glade it helped
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i have botloader unlocked
i flashed recovery
///solved to get into recovery
when i boot into recovery says no comands

danger2u said:
i have botloader unlocked
i flashed recovery
///solved to get into recovery
when i boot into recovery says no comands
Click to expand...
Click to collapse
i answered your question in your thread in Q and A

TWRP problem...
So I flashed TWRP to my phone. The flash went through fine, but when I tried to boot into recover it just comes up with the No Command error. Any thoughts?

AceBearpaws said:
So I flashed TWRP to my phone. The flash went through fine, but when I tried to boot into recover it just comes up with the No Command error. Any thoughts?
Click to expand...
Click to collapse
Yes this is a very common problem and i am going to edit the OP to try and make sure people dont make this mistake.
ok this is a simple fix
1.boot you phone into bootloader
2. CD adb to the folder with your recovery in it
3. re run the fastboot flash recovery imagename.img
4. do not boot your phone into android
5. right after your phone flashes TWRP type adb reboot recovery
6.it should boot right into recovery this time
for some reason after your flash TWRP you have to immediately boot your phone into recovery before you allow youe device to boot into android or you will have this issue.

Thanks! I'll give it a shot tonight!
---------- Post added at 12:40 PM ---------- Previous post was at 12:09 PM ----------
easting said:
Thanks! I'll give it a shot tonight!
Click to expand...
Click to collapse
Anyone try on XT1060 (VZW)?

I've got a problem hopefully you can help.
I've unlocked my bootloader via the moto website and getting the warning when I restart to say the bootloader is unlocked. I seem to be installing the recovery ok but when I typing adb reboot recovery I'm getting error: device not found.
When I have my phone turned on and I type adb devices it lists my phone. When I'm in fastboot and type adb devices my computer doesn't find my phone.
Do you have any ideas?

Thanks!
dray_jr said:
Yes this is a very common problem and i am going to edit the OP to try and make sure people dont make this mistake.
ok this is a simple fix
1.boot you phone into bootloader
2. CD adb to the folder with your recovery in it
3. re run the fastboot flash recovery imagename.img
4. do not boot your phone into android
5. right after your phone flashes TWRP type adb reboot recovery
6.it should boot right into recovery this time
for some reason after your flash TWRP you have to immediately boot your phone into recovery before you allow youe device to boot into android or you will have this issue.
Click to expand...
Click to collapse
Yeah I actually tracked down your post on another thread, and got it all fixed.
Though I will say this, once I flashed when I typed in adb reboot recovery it said it could not find my device for some reason. If this happens to anyone else you can still get recovery to work as described above with one small difference. It seems the moto x has a tendency to turn right back on the second you turn it off from fastboot. If you are ready for it you can quickly hit power + volume down quickly before it has a chance to boot, and it will get you back into fastboot and the recovery image will work from there.
Thanks!
~ Ace

AceBearpaws said:
Yeah I actually tracked down your post on another thread, and got it all fixed.
Though I will say this, once I flashed when I typed in adb reboot recovery it said it could not find my device for some reason. If this happens to anyone else you can still get recovery to work as described above with one small difference. It seems the moto x has a tendency to turn right back on the second you turn it off from fastboot. If you are ready for it you can quickly hit power + volume down quickly before it has a chance to boot, and it will get you back into fastboot and the recovery image will work from there.
Thanks!
~ Ace
Click to expand...
Click to collapse
Hi Ace
When you are in bootloader does adb reboot recovery work at all for you? How did you get it to reboot into recovery. I just tried flashing the recovery, restarting straight into bootloader and still cant use adb reboot recovery and selecting recovery boots android and starts the phone.

matust said:
Hi Ace
When you are in bootloader does adb reboot recovery work at all for you? How did you get it to reboot into recovery. I just tried flashing the recovery, restarting straight into bootloader and still cant use adb reboot recovery and selecting recovery boots android and starts the phone.
Click to expand...
Click to collapse
I would try reflashing the recovery one more time sounds like something went wrong
Sent from my XT1056 using XDA Premium 4 mobile app

When I flash 4.2.2 (camera update) to downgrade, the device gets stuck at boot splash. Typically with other devices I've owned, this is a sign of a bad kernel flash or an incompatible kernel. Though I've run through multiple times and get the same issue every time.
VZW locked bootloader.
Flashing using mfastboot for Linux.
Bootloader and terminal show successful data transfer and flash on all partitions.
Boot splash just shows the "M" logo without "a Google company" written underneath.
Flashing back to 4.4 yields no issues.
Any thoughts?
Sent from my XT1060 using Tapatalk

dray_jr said:
I would try reflashing the recovery one more time sounds like something went wrong
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've flashed the recovery several times before trying to reboot into recovery and it still isn't working. When I flash the recovery I get the acknowledgement on the command line and the phone. So I think the recovery is flashing. I have set up adb on another computer to try again and its not working either.
When my phone is in fastboot if I type adb devices I get error: no device found. If I type fastboot devices my phone shows up. Any other ideas? This is frustrating me to no ends!
---------- Post added at 08:23 AM ---------- Previous post was at 07:44 AM ----------
After doing some more googling it looks like adb commands won't work when your in fastboot. adb commands only work while the phone is on or in recovery. This sounds like why adb devices won't list the device and why adb reboot recovery won't reboot it to recovery

Ok I now have TWRP installed...yay
There may have been a problem with my firmware from the 4.4 OTA that was stopping me from installing twrp. I reinstalled the stock moto firmware using method 2 from here http://forum.xda-developers.com/showthread.php?t=2446515
I then followed the guide from this thread and installed TWRP with the exception that adb reboot recovery doesn't work in fastboot and did as Ace said and rebooted straight to fastboot and selected recovery from there.
Happy days

[GUIDE] Moto G XT1033/ XT1032 Lollipop 5.0 Installation

I finally managed to install Brazil Lollippop 5.0 OTA on XT1033. I mentioned the detailed process below, following it correctly will get you lollipop on your device.
Note: To install this OTA on your XT1033 you should have your Bootloader unlocked. I don't hold any responsibility if you brick your device.
Downgrading is causing some serious Issues. Be careful
thanks @deeplyyoung for screenshots
ROOTING TUTORIAL CAN BE FOUND HERE :
http://forum.xda-developers.com/moto-g/general/guide-root-xt1032-xt1033-moto-g-running-t2965507
TUTORIAL FO INSTALLING CUSTOM RECOVERY AFTER INSTALLING LOLLIPOP ON MOTO G
http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905
Converting your Asia XT1033 into Brazil version by restoring this Brazil retail file
DOWNLOAD THESE FILES
Lollipop OTA File:
MEGA1--> https://mega.co.nz/#!XMxUgZYC!AnUkb3...Hd3p3kU0xrVhmM
MEGA2-->https://mega.co.nz/#!PoQVEZyL!Jm92SU...jzN9aiO5iOmWLc
MEDIAFIRE-->http://www.mediafire.com/download/0x...asil.en.BR.zip
DEV-HOST--> http://d-h.st/buH [WORKING - Checked 24.12.14]
MEDIAFIRE --> http://www.mediafire.com/download/w112mtufl414nat/Blur_Version.210.12.40.falcon_umtsds.Brasil.en.BR.zip [WORKING Checked 24.12.14]
BRAZIL RETAIL 4.4.4 :
Filefactory--> http://www.filefactory.com/file/7koj5z8zk1mf/XT1033_RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml.zip
Mediafire--> http://www.mediafire.com/download/5...4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml.zip
Google Drive--> https://drive.google.com/file/d/0Bxf-Y_J8GLrJQndtNzhUQmFIV1E/view
Dev- Host--> http://d-h.st/7sG
----------------------------------------------------------------
mFastbootv2 : http://forum.xda-developers.com/attachment.php?attachmentid=2427667&d=1385958280
Minimal ADB & Fastboot Drivers: https://drive.google.com/file/d/0B1S0LCuXCnnmOWhnUk1ZWVdQakE/view?usp=sharing
You Can read this article on my blog too : http://www.mightygeekstuff.com/install-android-5-0-lollipop-ota-zip-moto-g-2013-xt1033/
Steps to Restore Brazil Retail 4.4.4 Firmware:
NOTE: Flashing this Retail 4.4.4 Firmware will will all the userdata, so backup important files before doing this.
1) Reboot the phone into bootloader mode. There are 2 ways to do this.a) The 'hardware' way.a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.​b) The 'software' way.a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open "Minimal ADB and Fastboot".
Type:
Code:
[SIZE=4]adb reboot-bootloader[/SIZE]
You should see the Moto G bootloader screen with the following options:
Code:
Code:
Normal
Powerup
Recovery
Factory
Barcodes
BP Tools
2) Now place & extract the Brazillian Retail File & mFastbootv2.zip in a same folder. Now rightclick anywhere inside the folder while holding Left Shift & select 'Open Command Window Here'. This will take you to the command prompt.
3) Now execute each & every command mentioned below one by one in the same order
Code:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
4) After executing the steps mentioned above, you should now be rebooted into a fully stock Moto G Brazillian firmware.
5) Now connect your phone to the computer & copy the Lollipop OTA zip file in the root of your internal SD card.
Steps to Flash Lollipop OTA onto XT1033:
1) Turn off you phone & boot it into bootloader mode by holding ' Volumed Down + Power ' for 3 seconds.
2) You will be provided with the below options
Code:
Normal Powerup
Recovery
Factory
Barcodes
BP Tools
Navigate & highlight Recovery using Volume Down button & press Volume Up button only once.
3) Now you'll come up with the following screen. Don't hesitate its common.Just carefully press ' Volume Up + Power ' for 3 seconds & release the buttons which will reveal new options on the screen.
4) Now select the option apply update from SD card & select the OTA file which you've copied earlier
5) Now the update starts, wait for a while it will take 15 minutes to update & Voila you finally managed to get lollipop on your device.
LEAVE A COMMENT ON MY WEBSITE, EVEN A THANKS WILL BE APPRECIATED.
COMMENT AT
http://www.mightygeekstuff.com/install-android-5-0-lollipop-ota-zip-moto-g-2013-xt1033/​
I Hope This Helped you, Please hit Thanks as a Token of Appreciation ​

My device is show this in installation:
"system/app/LatinImeGoogle.apk" has unexpected contents.
Installation aborted.
Anybody help me?
Sent from my XT1033 using XDA Free mobile app

waltinho2 said:
My device is show this in installation:
"system/app/LatinImeGoogle.apk" has unexpected contents.
Installation aborted.
Anybody help me?
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
did you modify the OTA ? I mead did you edit any files inside it ?
This type of error occurrs when OTA is modded.

Nooo, I'm just downloaded the zip and put on root folder.
Sent from my XT1033 using XDA Free mobile app

waltinho2 said:
Nooo, I'm just downloaded the zip and put on root folder.
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
@waltinho2 will u b kind enough to upload & share the recovery image of brazilian firmware if u have downloaded it..thanks[emoji1] [emoji1]

Locked Bootloader
lilsidsri said:
I finally managed to install Brazil Lollippop 5.0 OTA on XT1033.
Note: to install this OTA on your XT1033 you should have your Bootloader unlocked.
screenshots will be added soon
Step 1 ) Convert your Asia XT1033 into Brazil version by restoring the Brazil retail file mentioned in this thread
http://forum.xda-developers.com/moto-g/general/link-xt1033-ota-5-0-lollipop-brazilian-t2963565
Step 2 ) After successfully restoring Brazil stock firmware, download and place the OTA file in the root of your internal Sd card.
Step 3 ) No boot into bootloader by powering on your device while holding ' Power + Vol Dwn ' for 3 seconds & select Recovery option.
Step 3) Now you'll face a screen with Green android & Red riangle image, dont worry now just press ' Vol Up + Power ' for 3 seconds and you'll get recovery options.
Step 4) Now select the option apply update from SD card & select the OTA file.
Step 4) wait for the updation process to finish & enjoy Lollipop on your device.
HIT THANKS IF THIS HELPED YOU.
Click to expand...
Click to collapse
Hi There, I have XT1033 the Asia Retail version, non rooted, bootloader locked any way of me getting the lollipop update installed on my phone....

sandyisgood said:
Hi There, I have XT1033 the Asia Retail version, non rooted, bootloader locked any way of me getting the lollipop update installed on my phone....
Click to expand...
Click to collapse
No you cant.. wait for update for Asia retail

Everything going well thill step 4, when I select the file to update i get the following messages:
-Finding Update Package
-Opening Update Package
-Verifying Update Package
-Installation aborted
Do you know why?

sandyisgood said:
Hi There, I have XT1033 the Asia Retail version, non rooted, bootloader locked any way of me getting the lollipop update installed on my phone....
Click to expand...
Click to collapse
I'm on asia retail too, no way to do it besides waiting or converting to BR

That Retail BR link is dead.

joaovitor2763 said:
Everything going well thill step 4, when I select the file to update i get the following messages:
-Finding Update Package
-Opening Update Package
-Verifying Update Package
-Installation aborted
Do you know why?
Click to expand...
Click to collapse
Have u flashed Braz 4.4.3 stock & then u updated OTA? if yes download Braz stock 4.4.4 and give a try, as same happened with me last nyt thrice n then I downloaded the Brazilian stock 4.4.4 n successfully updated ... @lilsidsri few ss for yr ref..

deeplyyoung said:
Have u flashed Braz 4.4.3 stock & then u updated OTA? if yes download Braz stock 4.4.4 and give a try, as same happened with me last nyt thrice n then I downloaded the Brazilian stock 4.4.4 n successfully updated ... @lilsidsri few ss for yr ref..
Click to expand...
Click to collapse
Link for bazil 4.4.4 is not working.
Can you please upload it on Gdrive?
Thanks

deeplyyoung said:
Have u flashed Braz 4.4.3 stock & then u updated OTA? if yes download Braz stock 4.4.4 and give a try, as same happened with me last nyt thrice n then I downloaded the Brazilian stock 4.4.4 n successfully updated ... @lilsidsri few ss for yr ref..
Click to expand...
Click to collapse
I first installed the brazil retail 4.4.4 just as you may see bellow:

Meuuks13 said:
That Retail BR link is dead.
Click to expand...
Click to collapse
Worked fine for me...will try to upload on drive.
Sent from my XT1033 using XDA Free mobile app

deeplyyoung said:
Have u flashed Braz 4.4.3 stock & then u updated OTA? if yes download Braz stock 4.4.4 and give a try, as same happened with me last nyt thrice n then I downloaded the Brazilian stock 4.4.4 n successfully updated ... @lilsidsri few ss for yr ref..
Click to expand...
Click to collapse
yes, I installed 4.4.4 & then installed the OTA.
And everything is working very smooth.

Somebody plz provide retail brazil 4.4.4 mirror?
Sent from my Moto G using XDA Free mobile app

Hi if anyone was successful in updating can you please upload a nandroid backup

Same problem
joaovitor2763 said:
Everything going well thill step 4, when I select the file to update i get the following messages:
-Finding Update Package
-Opening Update Package
-Verifying Update Package
-Installation aborted
Do you know why?
Click to expand...
Click to collapse
I'm exactly the same problem, unlocked the bootloader,
I'm using the stock retail Br 4.4.4 and it did not work,
someone help?
I dont know what to do!

The link for Brazil Retail 4.4.4 is dead. Please re-upload the ROM again preferably on Devhost or Mediafire.

This might be weird but no matter what key combination I try after choosing recovery from bootloader I just cannot see the extra options. So I am unable to flash the new OS. My phone is running on 4.4.4 brazil version and the boot loader is unlocked (status:3)
Edit: The actual procedure is as follows (it worked like this on my phone):
1. Enter recovery
2. Hold volume up key for about 10 seconds
3. While still holding the volume up key press the power button and hold both the keys for few seconds
4. Release and you'll have the option to install from SD card.

Need Help Bro. My asus zenfone 5 stuck at Asus logo and wont boot

I have asus zenfone 5 T00F , i just using it for daily use, after that i root it and no problem.. unroot it also no problem, after a month using it, suddenly some app crash then i reboot it..
when reboot it it stuck at Asus Logo.
i can go to the bootloader but the imei and serial number was not correct , (i attach some picture about it)
already tried this
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455 and
http://forum.xda-developers.com/zenfone-5/help/zenfone-5-a500cg-zenfone-6-a600cg-t3354645 but it also not working.
my recovery said E: Error cant mount cache and etc (i also attach picture about it)
any kind of solution ? already searching at asus forum also dont find solution
Thanks before.. and sorry if my english is so bad

Try this Method
De-grade to Kitkat by downloading Kitkat firmware UL-ASUS_T00F-WW-2.22.40.540-user ( Kitkat).
Then Extract Fastboot.img, Boot.img and recovery.img
flash these files throufgh fastboot, for that downoad minimal adb tools and connect your phone through usb when in fastboot mode
flash these files by clicking right while holding shift on the ADB tools folder in Blank space and choose Open command window here .
then type these 4 commands :
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader [wait for the fastboot mode to reopen in phone then]
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after these 4 commands go to recovery through selecting recovery from fastboot.
In recovery, select Update from adb. Now copy firmware.zip in that ADB tools folder which is UL-ASUS_T00F-WW-2.22.40.540-user.zip and rename it to update.zip for ease.
now type in Cmd :
adb sideload update.zip
after this clear data/cache in phone and Your phone will boot.

bludyvenom said:
Try this Method
De-grade to Kitkat by downloading Kitkat firmware UL-ASUS_T00F-WW-2.22.40.540-user ( Kitkat).
Then Extract Fastboot.img, Boot.img and recovery.img
flash these files throufgh fastboot, for that downoad minimal adb tools and connect your phone through usb when in fastboot mode
flash these files by clicking right while holding shift on the ADB tools folder in Blank space and choose Open command window here .
then type these 4 commands :
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader [wait for the fastboot mode to reopen in phone then]
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after these 4 commands go to recovery through selecting recovery from fastboot.
In recovery, select Update from adb. Now copy firmware.zip in that ADB tools folder which is UL-ASUS_T00F-WW-2.22.40.540-user.zip and rename it to update.zip for ease.
now type in Cmd :
adb sideload update.zip
after this clear data/cache in phone and Your phone will boot.
Click to expand...
Click to collapse
Already tried that and also not working bro , i attach some picture about it.
adb sideload not flashing the firmware and just stopped with /cache mount error

xbeelzx said:
I have asus zenfone 5 T00F , i just using it for daily use, after that i root it and no problem.. unroot it also no problem, after a month using it, suddenly some app crash then i reboot it..
when reboot it it stuck at Asus Logo.
i can go to the bootloader but the imei and serial number was not correct , (i attach some picture about it)
already tried this
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455 and
http://forum.xda-developers.com/zenfone-5/help/zenfone-5-a500cg-zenfone-6-a600cg-t3354645 but it also not working.
my recovery said E: Error cant mount cache and etc (i also attach picture about it)
any kind of solution ? already searching at asus forum also dont find solution
Thanks before.. and sorry if my english is so bad
Click to expand...
Click to collapse
Your phone partition has broke need to repartition. Try this http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557
Choose nr 13 Zenfone Rescue
Sent from my ASUS_T00F using XDA-Developers mobile app

paktepu said:
Your phone partition has broke need to repartition. Try this http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557
Choose nr 13 Zenfone Rescue
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
already try nr 13 bro. when i press 13, the xfstk running.. when it want to repartitioning emmc (maybe it should automatically enter bootloader), i manually enter the bootloader then the script running , some error occured and when it finish flashing same error still occured x,x
i attach some picture about it

xbeelzx said:
already try nr 13 bro. when i press 13, the xfstk running.. when it want to repartitioning emmc (maybe it should automatically enter bootloader), i manually enter the bootloader then the script running , some error occured and when it finish flashing same error still occured x,x
i attach some picture about it
Click to expand...
Click to collapse
How is the result when you finish it?
I didnt see something wrong in there.
Sent from my ASUS_T00F using XDA-Developers mobile app

paktepu said:
How is the result when you finish it?
I didnt see something wrong in there.
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
still stuck at asus logo bro, and recovery still error mount cache

Moto Z Play | Resources all in one thread

Hey guys
I just thought we should have a 1-stop-guide for our amazing Moto Z Play. Generally people have to look through various threads before obtaining the real info, this thread was created so that people would find the resources easily without wasting time, looking here and there for information.. I will try to update the thread on regular basis as and when the new developments arrive...
Note: I want to thank all the devs for their efforts. None of this is my creation , i just collected & compiled all the info from various sources, credit as usual goes to original devs
PS: The thread is complete now...Just have to add the images for easy understanding...All the info posted here is latest development with correct info...There is no chance you will brick your phone by following this guide unless you do something wrong...
************************************************** ************************************************** ***************
INDEX​************************************************** ************************************************** ***************
Drivers | ADB installer
Unlocking Bootloader (Official Method)
Flashing TWRP and Rooting via TWRP
Back up / Restoring EFS (IMEI)
Restoring original Boot Logo after unlocking bootloader
Installing Xposed Framework
Flashing/ Restoring back to Stock Rom
Changing DPI without root
Remove Ascending Ringtones/Notifications
************************************************** ************************************************** **************
1) Drivers | ADB installer
​1) Motorola Drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installer (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
_______________________________________
​
2) Unlocking Bootloader (Official Method)
​
Files needed:
1) Motorola Drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
Note: Unlocking the bootloader erases all the data on the phone, make a backup of your imp stuff before unlocking
Method:
1) First of all visit this official Moto Unlocking site & register yourself or login via Google
https://motorola-global-portal.custh...-a/action/auth
2) Enable USB debugging & OEM unlock on the phone (Go to settings -> development options (if they do not have it enabled go to settings-> about the phone and below where it says "Compilation number" tap 7 times to activate the development options).. In the developer options, select "OEM unlock" it will ask for password / PIN / pattern and once activated, we look for "Debugging via USB" and we activate it also, then proceed to turn off the phone)
3) Turn on the phone by pressing Vol down + Power button together for 5 seconds until we get a screen like this:
4) Open adb command window and type:
Code:
fastboot devices
If your device appears on the command window you can continue with the guide, if your phone is not listed, install the Moto drivers correctly and verify if adb is working or not...
5) In the same adb command window type:
Code:
fastboot oem get_unlock_data
You will see numbers displayed like this, copy the code and paste it into notepad..Now eliminate the paragraph break so that there is only one line without spaces… Copy the entire code & login into your Moto account…Now paste the code on the same Moto webpage which was given above…
The unlock code will be sent to your registered email. There will appear an email with the number similar to this:
5)Without disconnecting the phone from the PC & without closing the window of the CMD, we return & we put this code:
Code:
fastboot oem unlock (enter code that was provided in the email)
6) You will be asked to re-enter the same command again, re-enter the code to confirm and finally unblock the bootloader
7) After re-entering the command, you will bootloader unlocked message
_______________________________________
3) Flashing TWRP and Rooting via TWRP
​
Note: Custom recovery (TWRP) woks only after unlocking your bootloader… Before flashing this recovery unlock your bootloader and enable USB debugging…
​
Files required:
1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
3) TWRP for Moto Z Play (https://mega.nz/#!yZ4lUCYB!-nN0jj2Ws5Z7RNyBT7S8m4gsrdOxTlK3nTjn9zOtx6s)
Method:
1) Download the above recovery, boot the phone in fastboot mode & open adb command window
2) In the adb command window type
Code:
fastboot flash recovery recovery.img
3) After executing the command, disconnect your phone & with the volume + or volume keys - we move until it says "Recovery Mode" . Press the power button to confirm the entry to the recovery.
4) Once you enter the recovery, select the right button & a menu to choose the language is displayed, it only brings Chinese and English so we will put it in English to know what to do.
5) We will see that it asks for a password, it is the same password that you put to encrypt the phone at the beginning when they set up the factory phone and always asks them to turn on the phone, it can be a password / PIN / pattern
6) Once the password has been entered, the recovery main menu will appear, we will go to "Advanced" and then "Install SU", it will ask if we want to root the phone, we accept by sliding and we wait for it to do the process. Then we give in "Reboot System" to restart and the phone will ignite with root
_______________________________________
4) Backing up / Restoring EFS (IMEI)
Note: This works only if you have TWRP recovery... Please backup your EFS using the method below before flashing any rom including stock rom
​
Backing up EFS (IMEI):
Method:
1) Boot the phone into TWRP recovery
2) Go to "Backup"
3) Select EFS
4) Create backup by sliding
5) Once finished, restart the phone
6) After restarting the phone, copy the TWRP folder from the internal memory to the SD, DO NOT CUT and PASTE, just copy with a file browser. Later from the SD card can be copied to the PC
Restoring lost IMEI / EFS:
Method:
1) Boot the phone into TWRP recovery
2) Go to "Restore"
3) Select folder (location where you have kept a backup of your EFS)
4) Restore by sliding
5) Wipe cache and dalvik and start phone normally
_______________________________________
5) Restoring original Boot Logo after unlocking bootloader
​
PS: This is used to remove unlocked bootloader warning when the phone is turned on (the black screen with letters)
Credit goes to : G4liant
Files needed:
1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
3) Original Motorola Bootlogo (https://mega.nz/#!zNIFHBiY!hbdgUwl9oWjrXbirwXKijviWW0nS_06MViU48yHmSD4)
Method:
1) Boot the phone in fastboot mode, open adb window on pc and type
Code:
fastboot flash logo logo.bin
2) Once the flashing is finished, restart the phone with this command:
Code:
fastboot reboot
When you turn it on, we will notice that we have the original motorola boot logo again and that the previous warning does not appear even when the bootloader of our device is unlocked
_______________________________________​
6) Installing Xposed Framework
​
Files needed:
1) [FONT=&quot]Have TWRP installed (If not installed refer to section #3 on this thread)
2) Download latest Xposed Installer.zip (http://dl-xda.xposed.info/framework/sdk23/arm/ )
3) Download latest Xposed Apk (https://forum.xda-developers.com/showthread.php?t=3034811)
Optional: Download latest Xposed un-installer but ARM 32 version not ARM 64 (http://dl-xda.xposed.info/framework/uninstaller/ )[/FONT]
Method:
1) Copy Xposed installation .zip, Xposed uninstaller (optional) and the Xposed APK to the internal memory (the TWRP does not mount the external SD so do not bother copying it to the External Memory)
2) Install the Xposed APK but DO NOT open it.
3) Enter recovery mode and open TWRP, Choose language and enter password to decrypt your device
4) Once the password is entered, the main recovery menu will appear, select "Install" and a file manager will appear, we will navigate the file down and look for the Xposed installer .zip, something like this:
5) Select the Xposed installer .zip and it will open a zip installer, slide to accept the flash of the .zip and wait for the process to finish. Then we give in "Wipe Dalvik / cache" and then to "Reboot System" to reboot and the phone will light up with Xposed already working.
_______________________________________
​
7) Flashing/ Restoring back to Stock Rom
​
IMPORTANT: First locate the firmware for your country / operator / area / continent to avoid changing baseband or other things that make the phone does not work as it should.
Credit goes to: Khanov XDA
Stock Rom links:
[FONT=&quot]Stock China
http://www.filefactory.com/file/6814...LT_CFC.xml.zip
Rogers Canada
http://www.filefactory.com/file/57g6...LT_CFC.xml.zip
Retail Latino America
http://www.filefactory.com/file/6pt8...%20%281%29.zip
Retail Latin America
https://mega.nz/#!WBYX3awb!qR1zitz1O...M1tnq1OwWDYDYA
Retail Europe
http://www.filefactory.com/file/4ora...C_EMEA.xml.zip
Retail Canada
http://www.filefactory.com/file/64wm...LT_CFC.xml.zip
Movistar Colombia
http://www.filefactory.com/file/10sv...LT_CFC.xml.zip.
Verizon
http://www.filefactory.com/file/60ty...LT_CFC.xml.zip
A Repository with several firmwares including Indian:
https://mirrors.lolinet.com/firmware...ison/official/[/FONT]
[FONT=&quot]
Files needed: [/FONT]
[FONT=&quot]1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
3) Firmware chosen from above links[/FONT]
[FONT=&quot]
[/FONT]
Method 1 (Manually by using adb commands):
1) Boot the phone into fastboot mode and open adb command window on pc
Code:
fastboot devices
This will show us if the phone is correctly connected and installed the drivers, it will detect the PC in fastboot mode and we can continue with the tutorial we will put these commands in the order they are, you can put them one at a time and pressing enter to execute it
Code:
[SIZE=2][B][FONT=Century Gothic]fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system system.img_sparsechunk.10
fastboot flash NON-HLOS.bin modem [COLOR=Red]([/COLOR][COLOR=Red][I]can skip this and thus [U]would[/U] prevent loss of IMEI)[/I][/COLOR]
fastboot erase modemst1 [I] [COLOR=Red](can skip this and thus [U]would[/U] prevent loss of IMEI)[/COLOR][/I]
fastboot erase modemst2 [COLOR=Red][I]([/I][/COLOR][COLOR=Red][I]can skip this and thus [U]would[/U] prevent loss of IMEI)[/I][/COLOR]
fastboot flash fsg fsg.mbn [COLOR=Red][I](can skip this and thus [U]would[/U] prevent loss of IMEI)[/I][/COLOR]
fastboot erase cache
fastboot erase userdata [COLOR=Red]([/COLOR][COLOR=Red][I]can skip this and thus [U]would[/U] prevent loss of your data (Internal storage)[/I][/COLOR]
[/FONT][/B][/SIZE][SIZE=2][B][FONT=Century Gothic] fastboot oem fb_mode_clear
fastboot reboot
[/FONT][/B][/SIZE]
Your phone will reboot and will be restored to stock rom
In case an error occurs during OTA, even after doing the above step flash the modem by typing:
NOTE: You will find these files (NON-HLOS.bin, fsg.mbn, adspso.bin etc) along with the systemchunk files you downloaded
Code:
[/FONT][/B][/SIZE][/SIZE][SIZE=2][SIZE=2][B][FONT=Century Gothic]fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
Now reboot the phone and apply OTA... It will succeed
Method 2 (Using software ; RSD lite to flash) :
Files needed:
1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
3) RSD lite (http://rsdlite.com/rsd-lite-download/)
4) Stock Rom from the links provided above
Method:
1) Enable USB debugging
2) Download RSDlite and Stock Rom zip file
3) Open RSDlite and browse button (next to file name textbox)... Find and select "flashfile.xml" from the downloaded zip file (extract the zip file)
4) Boot the phone into fastboot mode and connect the phone to pc; RSD lite shows ID if connected
5) Click start button…Now flashing process has started…It will flash files one by one…Wait for it till it shows reboot…
[FONT=&quot]6) Handset will automatically restart after flashing process completes[/FONT]
_______________________________________
8) Changing DPI without root
​
Files needed:
1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
Method:
Note: The DPI used here is 420... You can adjust the DPI according to your own taste... The default DPI is 480
1) Open ADB command window and enter:
Code:
[FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B]adb shell wm density 420[/B][/B][/B][/FONT][/B][/B][/B][/FONT]
2) Reboot your phone to apply the effects system wide
Reverting back to stock DPI:
Method:
1) Open ADB command window and enter:
Code:
[FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B]adb shell wm density 480"[/B][/B][/B][/FONT] or "[/B][/B][/B][/FONT][FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B]adb shell wm size reset" (If the 1st one doesnt work or some apps show wrong layouts like Snapchat etc[/B][/B][/B][/FONT][/B][/B][/B][/FONT][/B][/B][/B][/FONT][/B][/B][/B][/FONT][/B][/B][/B][/FONT]
2) Reboot your phone to apply the effects system wide
_______________________________________
9) Remove Ascending Ringtones/Notifications
Files needed:
1) TWRP
2) Ringtones / Notifications mod (http://cloud.tapatalk.com/s/58221f724bc3b/Ascending_audio_fix_motozplay.zip)
Method:
1) Download the mod and copy it to internal storage. Boot the phone in TWRP
2) Select install and locate the file in the file manager... Select the file and flash it
Reverting back to stock (Ascending ringtones):
Method:
1) Download this file [FONT=&quot]https://www.dropbox.com/s/otsir98jjlqnb85/Ascending_audio_stock_motozplay.zip?dl=0https://www.dropbox.com/s/otsir98jjlqnb85/Ascending_audio_stock_motozplay.zip?dl=0
2) Copy it to internal storage & boot the phone in TWRP... Select install and locate the file
3) Select the file and flash it[/FONT]
​

reserved...

reserved

Nicely work

Really nice thread. Just one thing...
Could you credit me for the modified logo.bin?
https://forum.xda-developers.com/showpost.php?p=69273602&postcount=37

Can I flash logo.bin zip in twrp?

Nope, has to be unzipped and flashed in fastboot, which shouldn't make much of a difference, as it has only to be done once. No need for reflashing after switching your custom rom.

G4liant said:
Really nice thread. Just one thing...
Could you credit me for the modified logo.bin?
https://forum.xda-developers.com/showpost.php?p=69273602&postcount=37
Click to expand...
Click to collapse
Sure man...Edited the OP... :good: Actually i found it on another site it didnt mention anyone so i posted like that only....Anyways nice work

Thanks and very useful.

Hey guys, it takes an incredibly long time to download the stock ROM, anybody have a solution for this? It also just stops and says 'network error' at 0.3gb. So I can't unbrick my phone really.

coolkingler1 said:
Hey guys, it takes an incredibly long time to download the stock ROM, anybody have a solution for this? It also just stops and says 'network error' at 0.3gb. So I can't unbrick my phone really.
Click to expand...
Click to collapse
More firmware found here https://mirrors.lolinet.com/firmware/moto/addison/official/
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
More firmware found here https://mirrors.lolinet.com/firmware/moto/addison/official/
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I found a good mirror at the Rooting thread but thanks!

TWRP flashing file download link dead
3rd section file needed are not expanding when that button is clicked some kind of glitch I think can you share the link directly.

abhilash_s_j said:
3rd section file needed are not expanding when that button is clicked some kind of glitch I think can you share the link directly.
Click to expand...
Click to collapse
Nope works fine for me...anyways here is the direct link:
https://mega.nz/#%21yZ4lUCYB%21-nN0jj2Ws5Z7RNyBT7S8m4gsrdOxTlK3nTjn9zOtx6s

Thank you for the effort

Thanks for your work!
Sent from my Nexus 6 using XDA-Developers Legacy app

TWRP flashing file download link dead
3rd section file needed are not expanding when that button is clicked some kind of glitch I think can you share the link directly.
---------- Post added at 01:37 AM ---------- Previous post was at 01:14 AM ----------
After flashing the original firmware of my device, there is no network signal, i cannot make calls, cannot use data, in general the SIM does not work. Does anyone knows how to solve this?

kkarora said:
TWRP flashing file download link dead
3rd section file needed are not expanding when that button is clicked some kind of glitch I think can you share the link directly.
---------- Post added at 01:37 AM ---------- Previous post was at 01:14 AM ----------
After flashing the original firmware of my device, there is no network signal, i cannot make calls, cannot use data, in general the SIM does not work. Does anyone knows how to solve this?
Click to expand...
Click to collapse
Check your IMEI, I think that you have lost It.

Hitachy said:
Check your IMEI, I think that you have lost It.
Click to expand...
Click to collapse
Yes IMEI is showing 0. How to restore it back...?

kkarora said:
Yes IMEI is showing 0. How to restore it back...?
Click to expand...
Click to collapse
If you have a twrp backup, restore It. If you don't have, assistance.

[Root][Oreo][Guide] How to flash and root G5 with (opt. remove encryption)

Hello guys,
after testing around for days i thought it might be helpfull to post the honestly pretty easy procedure to install stock Oreo, root it and remove encryption if needed.
Disclaimer:
I am not responsible for bricked devices, dead SD-cards, lost data, etc.
Back up your data, app settings, be sure you remember your passwords, your device will be empty!​
Edit: It seems, theres a bug that, if you read this post on XDA labs, won't show you everything, it seems like it randomly skips some parts.
What you need:
Unlocked Bootloader
Motorola USB drivers
15 sec adb and fastboot uploaded by myself since the original links aren't working anymore https://multifilemirror.com/hgxxyrfyd7rx.
I originally got them from here (you may have to go into your device manager and select the adb drivers for your phone f.e. when you want to use adb push in recovery, see original xda site).
This will also install the google drivers.
TWRP 32bit (v.3.2.3-0)
TWRP 64bit (v.3.2.1-0)
Disable Dm-Verity & ForceEncrypt from here
Magisk and MagiskManager. Newest should probably work, i used Magisk-18.0 and MagiskManager-6.1.0
Most recent Oreo firmware (edit 08.19)
(I used this Oreo firmware found in this post)
Steps:
Be sure you backed up your data and app settings, your pictures, downloads, etc. It will all be lost!
Please read all steps before you begin.
Extract the firmware into your adb folder (where you installed adb, should contain 4 files), copy both twrp (32 & 64 bit) in there, too.
Boot into bootloader (hold power+vol down) and open a terminal inside your adb folder (shift+rightclick) and type in
Code:
fastboot flash recovery name_of_twrp64bit_file.img
Boot into recovery (select recovery with vol buttons, then press power) and make a backup of EFS partition and persist folder (use file manager under advanced) and make another backup of system, boot and data and save both backups and persist to your SD-card or better your computer, too.
reboot into bootloader and check if your bootloader version is B.8.31 or above.
If it is B.8.31 or above DON'T FLASH BOOTLOADER!!! Because if you flash bootloader of the same version or below, it would hardbrick your device!
That also means if you f.e. want to downgrade to Nougat, just ignore following lines:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Also, unless youre sure your persist is absolutly ok (check here), please also omit the following lines:
Code:
fastboot erase modemst1
fastboot erase modemst2
They would reset your IMEI and usually it gets restored from your persist, but only if its not buggy.
Even if your persist is fine, as far as i know theres no harm in not using this commands (my persist is fine and i didnt use them).
Now paste following commands in your command promt in adb, in case you are BELOW B.8.31, add the bootloader commands from above between the first and second line:
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Please make sure that it really flashed all sparsechunk 0-8.
Let your phone reboot itself after installation is done, then return to bootloader and flash twrp 64bit:
Code:
fastboot flash recovery name_of_twrp64bit_file.img
Boot into recovery, since your device is encrypted it will ask for a password, click cancel, then go to WIPE and click on FORMAT DATA and confirm with yes.
This will remove the encryption of your data partition.
Go back to twrp main page and click on REBOOT then RECOVERY.
Once back in twrp, either copy Disable Disable_Dm-Verity_ForceEncrypt.zip and Magisk-18.zip and MagiskManager-6.1.apk to your SD-card or use
Code:
adb push name_of_file /external_sd
or
adb push name_of_file /sdcard
to copy the files to your SD-card (external_sd) or Internal-Storage (sdcard). For this you may have to manually configure your adb drivers in device manager, see here under Notes.
In twrp go now to INSTALL and flash "disable-dm-verity&encrypt" an then REBOOT and SYSTEM.
Return to recovery and flash "Magisk-18.0.zip", wipe Cache/Dalvik at the end and reboot System
Once System has rebooted, install MagiskManager-6.1.0.apk from your SD-card.
MagiskManager should say that Magisk is installed and in settings under security, your phone should be decrypted.
Note: MagiskManager will only show full information when it has internet access, all you see without is if Magisk is installed.
If you want to encrypt your device again, do it but flash twrp 32bit, too, if it asks for a password, it should be your usual password which you also have to enter on every boot.
Some explanation:
Why twrp 64bit?
Because twrp 32bit is able to bypass encryption, however, it causes some problems:
In fact, probably every twrp without the bypass encryption feature would work f.e. older 32bit version 3.1.0. but 64bit offers some features as EFS backup.
If you flash 32bit directly it can bypass the standard encryption but formatting data fails every time when you booted System previously.
When you reboot recovery and format data again it works, but it needs to fail first, just rebooting into recovery 2 times doesnt work.
I dont know what would happen if you (after using your phone normally) reboot recovery and f.e. want to do a backup from data, though im sure i testet it out, but i probably forgot.
You need it later when you want to encrypt your phone again, for me it didnt decrypt data after i reencrypted my phone using my password.
Why reboot System between flashing Disable-encryption and Magisk?
If you do not, you get heavy lags in the first 2 minutes after rebooting System, MagiskManager will say that Magisk isnt installed and then your phone will crash and reboot. But after that 2. reboot everything works fine again, Magisk is back, no lags.
I remembered this post from Johny Cipeli, between flashing no-verity and magisk he wrote to reboot, so i tried and it worked without lags and crash.
You don't need to remove encryption:
You can root your phone without flashing Disable_dm-verity_and_force-encrypt, use then twrp 32bit, dont format data, just flash magisk.
I can say that it should work, because that was one of my first attempts (and it worked for me), however i didnt write down what i was doing so i cant tell you step by step.
Additional:
In case you're searching Viper4Arise for Oreo, the Aroma installer won't work, use the Magisk module and install in MagiskManager. You can download it here from Zackptg5
If youre also annoyed by that One-Nav vibration, you can try using ExKernelManager app and activate the powersave mode. Although i think its officially not for G5, the app works, maybe that only refers to the Kernel and not to the app.
I tried Flyhigh Kernel, it didnt boot after flashing it, if you know a working Kernel for G5 which can disable One-Nav vibration, please write an answer.
My device:
Rooted Stock Oreo 8.1.0: OPP28.85-16
Bootloader: B.8.31
Model: XT1676 reteu
Stock Kernel
Thanks to:
Snoop05 for 15 sec adb and fastboot.
TheFixItMan for twrp.
Zackptg5 for "Universal DM-Verity, ForceEncrypt, Disk Quota Disablers".
topjohnwu for Magisk.
freeZbies for Official Oreo 8.1.0 OPP28.85-16 Fastboot Firmware.
Wolfcity, woozie.2007 and TheFixItMan for answering many of my questions!

- reserved -

ok friend, thank you for this. I think you dont need to flash twrp 64, i only flash official twrp 32, which indeed doesnt have the option for backup persist, but only efs. Maybe is someone else that will try your method to decrypt, I will try next time when I flash the stock, maybe to the next patch update. Good luck and A happy new year !!!
---------- Post added at 01:31 AM ---------- Previous post was at 01:26 AM ----------
LE: You cant root without format data partition, because flashing twrp, when twrp decrypt data you cant see anything on data partition, so you need to format it even if dont need to decrypt the phone

Nice guide @G5-User7080 .
For me everything seems to be correct, I can´t say anything device specific as I own a potter but there shouldn´t be big differences.
There´s one sentence I´m not sure about:
G5-User7080 said:
Because if you flash bootloader of the same version or below, it would hardbrick your device!
That also means if you f.e. want to downgrade to Nougat, just ignore following lines.....
Click to expand...
Click to collapse
It´s clear that downgrading the bootloader can hardbrick your device but why should there be any risk in flashing the same bootloader?
If I flash the fastboot firmware I´m on shouldn´t it be ok? Where did you get that information from?
I´m about to do that on a device of a friend of mine , he is rooted on 7.0 and wants to go the way to flash the firmware he´s on and after that take the OTA up to Oreo.
He could flash the Oreo firmware directly but he prefers to use the firmware from which he knows it´s working and is the correct one.
Very careful guy.
Edit: I just recognized that the part you called steps incl.the part I quoted isn't visible in XDA Labs, I'm only able to see it in mobile browser. Also some download links aren't there, on XDA Labs there is only the one for the 64bit recovery visible, not the one for 32bit. Maybe it's some kind of format problem, bb codes or else.

Some screenshots from XDA Labs and Chrome mobile to show the differences.

Wolfcity said:
It´s clear that downgrading the bootloader can hardbrick your device but why should there be any risk in flashing the same bootloader?
If I flash the fastboot firmware I´m on shouldn´t it be ok? Where did you get that information from?
Click to expand...
Click to collapse
I read this more then one time, although i could just find one source for now: "Flashing bootloader of equal or minor version will hardbrick your device" from Oreo Fastboot firmware.
I dont know why flashing bootloader of the same version would do lead to a hardbrick, but didnt want to try it out myself, also i see no problem in not flashing the bootloader when you already have the same version.
Wolfcity said:
Edit: I just recognized that the part you called steps incl.the part I quoted isn't visible in XDA Labs, I'm only able to see it in mobile browser. Also some download links aren't there, on XDA Labs there is only the one for the 64bit recovery visible, not the one for 32bit. Maybe it's some kind of format problem, bb codes or else.
Click to expand...
Click to collapse
Thats weird, i dont have XDA labs (thats the mobile app, right?), i wrote it on XDA desktop version and only used the size, code, color and list tags, hmm maybe it has problems with the sorted list, for every other part i used the unsorted ones with dots instead of numbers.
Quick test:
Test One:
this is made
in an unordered
list, using
list tags
Test Two:
this is now made
in an ordered list
counting from one to four
using list=1 tags
Can you read both lists with each four points?
And thanks for mentioning the bootloader thing,.. i realized i forgot to paste the lines in to flash bootloader in case you are below b8.31 ehee..

Wolfcity said:
Some screenshots from XDA Labs and Chrome mobile to show the differences.
Click to expand...
Click to collapse
wtf, it just skips random parts ?!!!
I have no idea what could cause this.. ill better add a note at the beginning of the post...wow

To flash the same vers of bootloader is not a problem, only the below one will hardbrick the phone

G5-User7080 said:
wtf, it just skips random parts ?!!!
I have no idea what could cause this.. ill better add a note at the beginning of the post...wow
Click to expand...
Click to collapse
Your lists are both readable.
I took a look at the BB codes as it's known that some of them are not working on XDA Labs like SIZE or HIGHLIGHT. In that case the BB codes are shown in the text but there's nothing missing.
Maybe it has something to do with the use of
[*] in your text?
Edit: Have you changed something in your text now? It seems to be complete on XDA Labs now too...

Wolfcity said:
Your lists are both readable.
I took a look at the BB codes as it's known that some of them are not working on XDA Labs like SIZE or HIGHLIGHT. In that case the BB codes are shown in the text but there's nothing missing.
Maybe it has something to do with the use of
[*] in your text?
Edit: Have you changed something in your text now? It seems to be complete on XDA Labs now too...
Click to expand...
Click to collapse
the [*] just create new lines for a list, and yes, i edited it two times, first, i added that one should use the bootloader commands in case of being below b831 and then i added the info about missing things on xda labs, but i didnt change anything on the lists itself,...