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]How to install Lollipop update on moto E

Hi guys this is the tutorial for those guys who are facing problem installing android l on their moto E.
These are the Steps you need to follow
1. Download the stock firmware for your device and use it bring your device to its initial state.(for rooted users only)
2.Now boot your Device And Complete the Setup
3.Install Motorola Update Services v4.0 from the play store.
4.Download lollipop rom from http://filestorm.cf/rL (No need to rename it or even worry about what it is called.)
5.Download Minimal Adb and fastboot from https://drive.google.com/file/d/0B1S0LCuXCnnmOWhnUk1ZWVdQakE/view and install it
6.Copy the rom in C:\Program Files x86\Minimal Adb and Fastboot(there must a folder like this)
7.Use this to fix the problem of device not found even before it arises http://www.dominantwire.com/2012/11/how-to-solve-adb-device-not-found-error.html (YourDevice must be on And USB debugging must be on)
8.Power of your Device And boot it into bootloader and then recovery and select install from adb and connect your device to your pc.
9.In the Folder In STEP-6 , Press the Left Shift and then left Click and select Open command window here.
10.In Command prompt Type "adb device" without quotes and it Must show you your Device.
11.After that type "adb sideload <Paste the rom name (full with .zip)>"(Don't use quotes or <>)
12. Wait and you will have lollipop Installed on your Device.
Note:-
If after step 10 no device is found try step 7 again
Hit Thanks if it Helped:good::good::good::good::good::good::good:
Credits
1.Threads which helped me installed it.
2.tech_master for uploading the OTA.
3.XDA

this is the eror got
http://forum.xda-developers.com/showpost.php?p=58792976&postcount=6
---------- Post added at 05:54 PM ---------- Previous post was at 05:54 PM ----------
this is the eror got
http://forum.xda-developers.com/showpost.php?p=58792976&postcount=6

No I installed it via adb and didn't faced any issue and by the way I am replying via lollipop rom
Sent from my XT1022 using XDA Free mobile app

SO how is lollipop on moto E ? stable ? fast ?

The ROM is great no lags faced the apps are now working smoother but missing the multiuser settings and SD card functionality
Sent from my XT1022 using XDA Free mobile app

what do you mean with "SD card functionnality" ? SD card access is no more available ? every photo or so must be saved in internal mem ? ?
or simply app move to SD Card is impossible (already the case with 4.4.4) ?

Too bad it´s not working for me. Sideload is working until it reaches 100% after that it says Installation aborted.
Having a xtc1021, flashed India 4.4.4 Stockrom 1022 before.
Too bad.

Brother the zip verifies your device before proceeding with flashing According to me you must download the zip for XT1021 and then try installing
Sent from my XT1022 using XDA Free mobile app

I am sorry if I quoted it wrong you can put media and pictures on the SD card and move app to SD card also but as with KitKat you cannot put the data of apps(obb) in the ext SD card and run the apps
Sent from my XT1022 using XDA Free mobile app

coolsabi98 said:
I am sorry if I quoted it wrong you can put media and pictures on the SD card and move app to SD card also but as with KitKat you cannot put the data of apps(obb) in the ext SD card and run the apps
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
So that's no big deal, it acts the same way as KitKat.

Hi i get a error /system/app/3c_main.apk has unexpected contents, instillation aborted

kraftmaschine said:
Too bad it´s not working for me. Sideload is working until it reaches 100% after that it says Installation aborted.
Having a xtc1021, flashed India 4.4.4 Stockrom 1022 before.
Too bad.
Click to expand...
Click to collapse
Exactly same is happening with me.What to do.?

Brazillian lollipop update in moto e xt1021 retail BR
Steps followed by me to get lillipop working 100% in xt1021.
Get the zip file in https://mega.co.nz/#!wVsQmajI!tmEkvt...jtAS2GwF5fncws
Extract the files
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
if you have bootloader unlocked: fastboot oem lock begin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
if you have bootloader unlocked: fastboot.exe oem lock
fastboot reboot
Apply your Google Account
Get the zip file in https://mega.co.nz/#!IJ9SVCaT!watj3-...GnKkg8od_kthLw
Put this zip file in root internal memory
In Fone go to Settings, About Phone, System Updates
After detect and apply update your Moto E have Lollipop 5.0.2
if you have a bootloader unlocked warning in boot phone after update to lillipop
Get the zip file in https://mega.co.nz/#!MFVkCQ7J!W7SmL3...rWDXoHW5hz6l44
unzip the file
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
fastboot flash logo logo.bin
fastboot reboot
Enjoy.
Hit Thank's if you like help.

Hello i have question. Does lollipop update fix the random reboot issue specially when you're pressing power button?

if you apply soak test lollipop into stock 4.4.4 you don't have any random reboot, it's work perfect to me.
I suggest you to restore stock 4.4.4 (not 4.4.2) and update to lollipop soak test.

How do i download the file. Its asking for a key? Thanks in advance.

Im trying to install via sideload adb but everytime i put my phone to restore adb the pc cant recognize my phone, but i see xt1021 question marked on device manager

Hey guys, i am on 5.0.2. Did anyone face the issue where the call function was not working in the dialer ? I mean, i tried calling numbers but it wouldn't just work. It worked after rebooting though. Just wanna make sure it wasn't a bug cause if someone else too faced this, then the soak testers should report this in their feedback. Besides of course the multiuser and the sd card functionality for hd games !
Thanks
Sent from my XT1022 using XDA Free mobile app

kraftmaschine said:
Too bad it´s not working for me. Sideload is working until it reaches 100% after that it says Installation aborted.
Having a xtc1021, flashed India 4.4.4 Stockrom 1022 before.
Too bad.
Click to expand...
Click to collapse
BROTHERS,...
I THINK THE METHOD OF PUTTING THE ZIP FILE IN EXTERNAL SD CARD AND CHECK FOR UPDATE FROM THE PHONE PHONE ITSELF WILL WORK FINE FOR EVERYONE.....
THE IMPORTANT POINT MANY GUIDES MISSING IS THE FACT THAT "WE HAVE TO RENAME THE ZIP FILE IN TO "Blur_Version.22.21.32.condor_retaildsds.retaildsdsall.en.03.zip" FROM "Blur_Version.21.12.40.condor_retaildsds.retaildsdsall.en.03.zip" (THE ONE ORIGINALLY WE FIND ON THE DOWNLOAD)
NB: no quotes needed in name.
Try this.... i have done it successfully after many failed side loading attempts. all the best...

[XT1022] 5.1 Stock Firmware

Need to be flashed via fastboot
Doesn't matter which ROM you are using !
Just flash it !
You will be on stock 5.1​
Steps :
Download and install Moto E drivers on your pc. Link : https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/99012/p/30,6720,9146
Download mfastboot files and extract the files in a folder. Link :https://drive.google.com/folderview?id=0B05Crz57q4zgZE1aVW5FT1RsUUU&usp=sharing
Download Stock firmware for XT1022 and extract the files to the same folder. Link :https://drive.google.com/file/d/0B05Crz57q4zgbFQ5b0dDck5yWGc/view?usp=sharing
Now, reboot your phone into bootloader by pressing volume down + power for a few seconds. You will see the bootloader screen.
Go to the folder where you have extracted Stock Firmware and mfastboot files and open command prompt there (Press shift + right mouse button and click on open command prompt)
Now, its the time to enter commands. Execute these lines of command one by one checking that each command you executed returned ok !
Hit thanks, if helped

It don't stuck in recovery logo flicking ?

which commands?

Which command to be used

Shaikh Arbaaz said:
Which command to be used
Click to expand...
Click to collapse
Use this command bat Retail.bat in zip file.

prince.d.emperor said:
Need to be flashed via fastboot
Doesn't matter which ROM you are using !
Just flash it !
You will be on stock 5.1​
Steps :
Download and install Moto E drivers on your pc. Link : https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/99012/p/30,6720,9146
Download mfastboot files and extract the files in a folder. Link :https://drive.google.com/folderview?id=0B05Crz57q4zgZE1aVW5FT1RsUUU&usp=sharing
Download Stock firmware for XT1022 and extract the files to the same folder. Link :https://drive.google.com/file/d/0B05Crz57q4zgbFQ5b0dDck5yWGc/view?usp=sharing
Now, reboot your phone into bootloader by pressing volume down + power for a few seconds. You will see the bootloader screen.
Go to the folder where you have extracted Stock Firmware and mfastboot files and open command prompt there (Press shift + right mouse button and click on open command prompt)
Now, its the time to enter commands. Execute these lines of command one by one checking that each command you executed returned ok !
Hit thanks, if helped
Click to expand...
Click to collapse
Already posted on XDA for all versions. Why you duplicate the post.http://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111

Have you tried it??
Will it cause bootloop as it occurs it many cases.

chaithanya0207 said:
Already posted on XDA for all versions. Why you duplicate the post.http://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
Click to expand...
Click to collapse
I didn't duplicate.
I respect that post but that has been edited and the stock ROM for XT1022 has been added later to that post.

thanx

Is this working?
Which are the fastboot/adb commands?
All of them are to be executed when flashing?
My Phone isn't booting, how to flash Stock ROM?

chaithanya0207 said:
Already posted on XDA for all versions. Why you duplicate the post.http://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
Click to expand...
Click to collapse
Those are OTA, not Fastboot Files,Broo.
Thnx to this Broo for the Fastboot files,

lul
thank you

Can the rom zip file be flashed from the stock recovery?, i dont have twrp and my pc wont detect my phone when i its connected via usb cable. My moto e is bootloader unlocked, and its stuck at the bootloader unlocked warning message and i can boot to recovery, so i was thinking mabe i could flash the stock rom zip file from the stock recovery

Soooo, theoretically if one were to follow these same steps on a XT803C (Straight talk Moto E CDMA variant), would this boot or brick? Haha, sorry I know how tough that is to answer, but this phone is $26 on NewEgg & I'd love to break it, I don't care about modem working, it will never have service just wifi only, so I figured id ask xD

Thanks

i have stucked at bootloader while iam flashing it says preflash verification failed and i didn't even root my device,please help me

I can't thank you enough for this OP. You're a live saver.

hey guys i am stuck.......
this screenshot would explain it all.......
please help......
https://drive.google.com/open?id=1Qaim6BJPdXRc97G0nXYz6dhleNoU9FYc

[ZE552KL/Z012DC] Canadian Thread - Unlock, Root, Update to Nougat

This thread will be for the Canadian version of ZE552KL, and will be updated with specific info relevant to Z012DC model found in Canada (Canada Computers, Staples, other retailers). It has WW SKU number.
It took me a while and some searching to figure all steps out. I also modified Asus N and M firmware to remove version checks. Without this step - i was stuck with error 7 in TWRP. The only difference between Z012D and Z012DC seems to be in Fastboot and ADB drivers, TWRP recovery, system images seem to work well so far.
Steps:
1. Download Fastboot and ADB Drivers. For me usb driver on ZE552KL Asus download page didn't work. Select "Only install driver", you do not need to update your drivers via DRP.
Fastboot driver (for Vendor VID_18D1&PID_D00D): http://drivers.drp.su/Telephone/Hua...03.00/Huawei-FORCED-Allx64-2.00.03.00-drp.exe
ADB Driver (for VID_18D1&PID_D002): http://drivers.drp.su/Telephone/Leshcat/WinAll/Leshcat-WinAll-drp.exe
2. Save the following files on your External SD Card:
Modified M image UL-ASUS_Z012D-WW-13.20.10.152-user.zip
Modified N image UL-ASUS_Z012D-WW-14.2015.1701.8-user.zip
SuperSU - latest version from here
no-verity-opt-encrypt-5-1.zip. Give thanks to @kaffeine1 , without him - we would all be stuck with black screens
3. Save ADB and Fastboot files on your computer, and extract; give thanks to @snowwolf725
4. Download newer recovery (TWRP 3.1.0) from here
5. Unlock bootloader via unofficial unlock method; give thanks to @snowwolf725
6. Get into fastboot by turning off the phone, and pressing volume up + power. Install recovery that you downloaded in step #4:
Code:
fastboot flash recovery twrp-3.1.0-0-Z012D.img
7. Follow the steps this guide by @kaffeine1 . Skip the steps of downloading Nougat and Marshmallow firmware from Asus site, as you have already downloaded and saved both firmwares in Step #2 . Also skip the last step - do not reboot into Nougat, but go back to fastboot mode.
8. Root Nougat - follow steps under #2 here:
https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926
How to update to the latest version of OS:
1. Go to Asus Site, download latest WW image UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
2. Extract UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip\META-INF\com\google\android\updater_script , edit, remove first two lines, and put back into the zip file (e.g. using 7zip)
3. Extract from above zip file boot.img , and flash it via: fastboot flash boot boot.img
4. Flash recovery: fastboot flash recovery twrp-3.1.0-0-Z012D.img
5. Reboot into recovery, and flash:
- Firmware that you modified in #2
- no-verity-opt-encrypt-5.1.zip
- Latest SuperSU
- Rooted.zip (from step #8 above)
6. Reboot mobile, and enjoy new version!
Phone info as purchased:
Model Number: ASUS_Z012DC
Android version: 6.0.1
Baseband version: M3.10.42-Libra_080001
Build number: MMB29P.WW_Phone-13.20.10.152-20161222
Manufacture date (on the box): January 2017
Latest version - UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
Model Number: ASUS_Z012DC
Android version: 7.0
Baseband version: M3.10.47-Libra_080001
Build number: NRD90M.WW_Phone-14.2020.1703.28-20170410
Special thanks to:
- @jcadduono for TWRP recovery
- @snowwolf725 for guide unlock bootloader
- @kaffeine1 for guide how to upgrade to N from M

Reserved for future use

can i follow this step for ZE520KL ?

I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks

lastremnant said:
can i follow this step for ZE520KL ?
Click to expand...
Click to collapse
no, I do not think so. these are different phones.

DilipRB said:
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
Click to expand...
Click to collapse
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.

anterus said:
no, I do not think so. these are different phones.
Click to expand...
Click to collapse
nevermind sir, it worked for me

Strange things do happen!!!
anterus said:
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
Click to expand...
Click to collapse
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????

DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update

lastremnant said:
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
Click to expand...
Click to collapse
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks

DilipRB said:
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
Click to expand...
Click to collapse
i found it ...
apktool from :
https://forum.xda-developers.com/showthread.php?t=1989533
Sorry this was for apks... but i guess same principle aplies... when i can i shall try and post the outcome

DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
I noticed that in some cases TWRP doesn't "stick", and gets overridden by default bootloader. Specific check is essentially useless - just to prevent flash of improper image. Just remove the check in the new FW, or use modified FW that has the check removed. I think in your case you can just re-flash TWRP since your bootloader is unlocked?

I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens

DilipRB said:
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
Click to expand...
Click to collapse
flash modified images through twrp - with links in OP

Well my wife liked the phone so much, that she "kindly requested" me to gift it to her... now she is the proud owner of a canadian vertion of ZE552KL and i got myself a ZS570KL
thanks a lot for all your help.
P.D. : i think she was not happy with the time i was spending with the device.

I know this is going to sound super dumb, but the unofficial bootloader unlock still triggers the bootup message and voids the warranty, right?

This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...

DilipRB said:
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
Click to expand...
Click to collapse
That's what some manufacturers do, like Motorola and HTC. But from back when I unlocked the BL on my Zenfone 2 Laser, I remember that all it did (as far as I could tell) was unlock the bootloader and set a flag in the bootloader that made it say it was unlocked that couldn't be reversed. No need for fancy registration systems when you can just boot up the phone and take a look.

What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?

Jarrick said:
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Click to expand...
Click to collapse
Updated OP with instructions regarding how to upgrade to the latest version of N - just tested steps myself. Should be applicable to all future versions of N posted on Asus site. Enjoy!

[BND-L22 / BND-AL10C675] Back to Stock / Unbrick your Honor 7X Indian Variants

Hello All, this guide will help to unbrick or back to stock firmware on Indian Variants BND-L22 and BND-AL10C675
Dont try it on other variant otherwise you will fail to install and may loose your IMEI number.
Do it on your own risk. I will not be responsible for any damage to your phone.
I am not a developer so i cant help you much if this update process fails.
PreRequisites :
1. Bootloader Locked/ReLocked/UnLocked
2. Stock Recovery/TWRP. it works with TWRP, still i suggest you use stock one. Download stock recovery for BND from here
https://mega.nz/#!KixHHCKJ!4hw_lHQGYa_0BJ79lou4m34Fmi23wBctbbvdSCyvCYE
3. SD card (at least 5gb free memory)
Preparations :
1. Backup your data
2. if you are on twrp, just flash Stock recovery via Fastboot or MT
command ' fastboot flash recovery recovery.img '
3. Lock/relock your bootloader ( you may test it on unloacked bootloader)
command ' fastboot oem relock (unlock code) '
4. download this tar. gz file, extract it and Copy 'dload' folder on your SD card, put SD card in your phone
https://mega.nz/#!SuwDUTCJ!iaBnYIbLlMggGId_COuu-xY9pZ2Tec66si5PEcEhovM
This is full Stock Rom not just an OTA update.
5. charge your phone to at least 50%
Steps :
1. switch off your phone and wait for 10 secs
2. press vol.up + vol.down + power keys simultaneously
3. keep keys pressing for few seconds and your phone will boot into automatic update package installer.
4. wait till updating/installing done. If process is stucked at 99%, dont worry just wait for few mins.
5. after updating package done, your phone will boot into stock system. congratulations

Dr.Anshuman said:
Hello All, this guide will help to unbrick or back to stock firmware on Indian Variants BND-L22 and BND-AL10C675
Dont try it on other variant otherwise you will fail to install and may loose your IMEI number.
Do it on your own risk. I will not be responsible for any damage to your phone.
I am not a developer so i cant help you much if this update process fails.
PreRequisites :
1. Bootloader Locked/ReLocked (I've not tried on UnLocked bootloaders)
2. Stock Recovery (I've not tried on TWRP). Download stock recovery for BND from here
https://mega.nz/#!nyY1QRpR!gp5k4nqkQUfktrD2B5Qb1OhhAXmO5Mi2aaMPz8CD8Ts
3. SD card (at least 5gb free memory)
Preparations :
1. Backup your data
2. if you are on twrp, just flash Stock recovery via Fastboot or MT
command ' fastboot flash recovery recovery.img '
3. Lock/relock your bootloader ( you may test it on unloacked bootloader)
command ' fastboot oem relock (unlock code) '
4. download this tar. gz file, extract it and Copy 'dload' folder on your SD card, put SD card in your phone
https://mega.nz/#!SuwDUTCJ!iaBnYIbLlMggGId_COuu-xY9pZ2Tec66si5PEcEhovM
This is full Stock Rom not just an OTA update.
5. charge your phone to at least 50%
Steps :
1. switch off your phone and wait for 10 secs
2. press vol.up + vol.down + power keys simultaneously
3. keep keys pressing for few seconds and your phone will boot into automatic update package installer.
4. wait till updating/installing done. If process is stucked at 99%, dont worry just wait for few mins.
5. after updating package done, your phone will boot into stock system. congratulations
Click to expand...
Click to collapse
How come you got the stock image of bnd al-10?

Asder.mko said:
How come you got the stock image of bnd al-10?
Click to expand...
Click to collapse
Its Unofficial.

Dr.Anshuman said:
Its Unofficial.
Click to expand...
Click to collapse
That doesn't matter if it works. I'm having unlocked bootloader.
Let me check and confirm whether it works or not on unlocked device.

Dr.Anshuman said:
Hello All, this guide will help to unbrick or back to stock firmware on Indian Variants BND-L22 and BND-AL10C675
Dont try it on other variant otherwise you will fail to install and may loose your IMEI number.
Do it on your own risk. I will not be responsible for any damage to your phone.
I am not a developer so i cant help you much if this update process fails.
PreRequisites :
1. Bootloader Locked/ReLocked (I've not tried on UnLocked bootloaders)
2. Stock Recovery (I've not tried on TWRP). Download stock recovery for BND from here
https://mega.nz/#!nyY1QRpR!gp5k4nqkQUfktrD2B5Qb1OhhAXmO5Mi2aaMPz8CD8Ts
3. SD card (at least 5gb free memory)
Preparations :
1. Backup your data
2. if you are on twrp, just flash Stock recovery via Fastboot or MT
command ' fastboot flash recovery recovery.img '
3. Lock/relock your bootloader ( you may test it on unloacked bootloader)
command ' fastboot oem relock (unlock code) '
4. download this tar. gz file, extract it and Copy 'dload' folder on your SD card, put SD card in your phone
https://mega.nz/#!SuwDUTCJ!iaBnYIbLlMggGId_COuu-xY9pZ2Tec66si5PEcEhovM
This is full Stock Rom not just an OTA update.
5. charge your phone to at least 50%
Steps :
1. switch off your phone and wait for 10 secs
2. press vol.up + vol.down + power keys simultaneously
3. keep keys pressing for few seconds and your phone will boot into automatic update package installer.
4. wait till updating/installing done. If process is stucked at 99%, dont worry just wait for few mins.
5. after updating package done, your phone will boot into stock system. congratulations
Click to expand...
Click to collapse
If you have a twrp already why bother to install drivers and go for ADB you can just flash the recovery.img from twrp .It works too .just a suggestion

trixter127 said:
If you have a twrp already why bother to install drivers and go for ADB you can just flash the recovery.img from twrp .It works too .just a suggestion
Click to expand...
Click to collapse
hiiiiiiii dear....pls tell me .....this is official indian Rom for honor 7x ..........and does it contains preinstalled gapps.......

trixter127 said:
If you have a twrp already why bother to install drivers and go for ADB you can just flash the recovery.img from twrp .It works too .just a suggestion
Click to expand...
Click to collapse
yes, but when it comes to complete stock, i prefer fastboot commands.

gouravbharat2014 said:
hiiiiiiii dear....pls tell me .....this is official indian Rom for honor 7x ..........and does it contains preinstalled gapps.......
Click to expand...
Click to collapse
this is a complete Firmware including gApps.

Dr.Anshuman said:
yes, but when it comes to complete stock, i prefer fastboot commands.
Click to expand...
Click to collapse
Well, thanks for the post

Dr.Anshuman said:
this is a complete Firmware including gApps.
Click to expand...
Click to collapse
thanks a ton.........

Hi !
It work on BND-L21C432 ?
Thanks !

Thanks
Awesome it worked

saifuddin.slatewala said:
Awesome it worked
Click to expand...
Click to collapse
Model? Ota working?

DaRkLinK_35 said:
Hi !
It work on BND-L21C432 ?
Thanks !
Click to expand...
Click to collapse
This is only for L22 and AL10C675, dont try it on other versions.

Dr.Anshuman said:
This is only for L22 and AL10C675, dont try it on other versions.
Click to expand...
Click to collapse
Ok thanks for you reply !

Username.php said:
Model? Ota working?
Click to expand...
Click to collapse
honor 7x model: BND-AL10

can we use this method to roll back the faceunlock update as its having annoying touch problems? (Indian Version)

Yes it will rollback to earlier version one without face lock

saifuddin.slatewala said:
Yes it will rollback to earlier version one without face lock
Click to expand...
Click to collapse
thanks, do i need to factory reset or just flash this file on top of faceunlock from recovery?
also after this flashing, can we still get OTA updates as normal?

Thank you so much mate. I am back on stock ROM and I did get Oreo ota today just because of you.