Database Users

[Answers] Solutions to Common Problems - Look Here Before Posting in Q&A

The purpose of this thread is to hopefully limit the number of repeat questions / calls for help in Q&A.
(if I see one more request to help fix a boot loop I'm going to strangle someone! )
The first place you should always look for information is the Beginners Guide. Tons of good stuff there.
If anyone has any additional helpful information, post below and I will add it to the OP.
If you find that any of the links are broken, please let me know so I can fix them.
If files are not available at the linked resource, they are available at the bottom of this post.
And always remember xda rule #1:
"Search before posting: Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news."
ADB not connecting to / can't find device:
Check to make sure you have the correct drivers installed on your PC.
Try disconnecting then reconnecting USB cable from PC.
On your PC open task manager, kill all instances of adb.exe, then start again.
Battery won't charge to 100%
1) Pull battery while charging
2) Wait for the question mark, then replace battery
3) Let battery charge for 1-2 hours
4) Wipe battery stats in CWM
Or try ravilov's Battery Fix app.
Battery too Low to Recover from Problem
Charge your battery with a wall charger, or use a USB cable.
Boot Loop
1) Pull battery
2) Replace battery while holding the volume down button
3) Use volume down to navigate to either recovery or fastboot, then press volume up
Once in:
Recovery - restore your backup or re-flash ROM
Fastboot - flash newer version of recovery or re-flash ROM
Fastboot Information
See post #2
Hard Brick
Consider using your device as a paperweight or doorstop. (or donate it to a dev)
Maybe if you are really lucky, something here might help.
Ram Low After Bootloader Unlock
Ramfix
Recovery Not Working (Just Rooted & Unlocked Bootloader)
You most likely followed a guide or used an automated tool with an outdated version of recovery.
Download the most recent version of CWM, then flash with fastboot (see post #3).
Return to Stock
The best and safest way to return to stock is by restoring the nandroid backup you made when you first installed CWM.
The next best way to return to stock is by flashing a fruit cake with CWM. Fruitcakes can be found here, and at the two links on the bottom of this post. There are some international fruit cakes available at the Atrix Reboot Project.
The third option is to fastboot flash a boot and system image (see post #4) from a fruit cake (links below). Or, fastboot flash a stock nandroid backup.
The least safe and least desirable method is to flash an sbf. This should only be used as a last resort (see entry for Hard Brick).
Rooting
The easiest way to root: Link
The way that you will learn something: Link1 Link2
There is not an established method for rooting the newest OTA (4.5.145). Exiting methods are hit or miss.
Sleep of Death (SOD)
Some users have had success with doubling the minimum CPU clock speed.
With CM7/9/10 you can adjust the clock speed in settings. Otherwise, try SetCPU.
This problem is not well understood, and usually the only real cure is returning to stock.
Soft Brick (Failed to boot XXXX)
Read this post, install software (Iinked below), select option 3.
Soft Keys not Working
Try Button Savior from the Play Store
Touchscreen - Dead Spot Quick Fix
Link
Touchscreen Replacement
Link
YouTube Video
_______________________________
Information Resources:
Atrix 4G Information Repository
_______________________________
File Resources:
A lot of the links in this forum are dead. But thanks to SamCripp and Zeljko1234, many of the files can be found below.
Atrix Reboot Project
[Fruit Cakes] Kernel, Unlock - Backup links
_______________________________
Downloads:
My AFH Atrix Folder
_______________________________

Setting up fastboot and ADB
Useful fastboot info and commands: Link1 Link2
1) Download and install 7Zip
2) Download and extract attached fastboot & ADB file
3) Download and install Motorola drivers
4) Create a new folder on your hard drive named "Android" (c:\Android)
5) Place all contents of the fastboot & ADB folder (5 files) in "Android" folder
6) Attach your phone to the PC via USB (use a port closest to the power supply)
7) In the USB settings make sure USB Mass Storage is selected
8) Reboot phone while holding volume down until you see "fastboot"
9) Press volume up to initiate fastboot
10) On your PC click the Start menu, then in the search box type "cmd"
11) In the command prompt type the following commands (no quotes, hit enter after each command)
11a) "cd c:/android"
11b) "fastboot devices"
If fastboot is working properly you should see something that looks like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Me>cd c:/android
c:\Android>fastboot devices
TA20703SX9 fastboot
c:\Android>

Flashing recovery with fastboot
1) Set up fastboot as described in post #2
2) Download the most recent CWM available Link
3) Place recovery image in c:\Android
4) Type the following commands (no quotes, hit enter after each command)
4a) "fastboot flash recovery recovery-clockwork-5.0.2.0-olympus.img" (note: the name of your recovery image may be different)
4b) "fastboot reboot"
If everything was successful, you should see something like this:
Code:
c:\Android>fastboot flash recovery recovery-clockwork-5.0.2.0-olympus.img
sending 'recovery' (4824 KB)... OKAY [ 0.575s]
writing 'recovery'... OKAY [ 0.592s]
finished. total time: 1.169s
c:\Android>fastboot reboot
rebooting...
finished. total time: 0.002s
c:\Android>

Fastboot flashing boot and system images - Returning to Stock
1) Set up fastboot as described in post #2
2) Download one set of boot and system images from post #1, or unzip a fruit cake and use those images.
3) Place boot and system images in c:\Android
4) Type the following command (no quotes, hit enter after each command)
4a) "fastboot erase cache"
4b) "fastboot erase userdata"
4c) "fastboot flash boot boot.img"
4d) "moto-fastboot flash system system.img"
4e) "fastboot reboot"
If successful, you should see something like this:
(Note: If you forget to use moto-fastboot to flash the system image (like I did), you will see the "INFOImage too big" error.)
Code:
c:\Android>fastboot erase cache
erasing 'cache'... OKAY [ 2.073s]
finished. total time: 2.073s
c:\Android>fastboot erase userdata
erasing 'userdata'... OKAY [ 5.393s]
finished. total time: 5.394s
c:\Android>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.979s]
writing 'boot'... OKAY [ 0.610s]
finished. total time: 1.591s
c:\Android>fastboot flash system system.img
sending 'system' (327680 KB)... INFOImage is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.001s
c:\Android>moto-fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 29.155s]
writing 'system'... OKAY [ 13.965s]
sending 'system' (65536 KB)... OKAY [ 7.582s]
writing 'system'... OKAY [ 3.442s]
c:\Android>fastboot reboot
rebooting...
finished. total time: 0.010s
c:\Android>

Miscellaneous
All:
Set up fastboot as described in post#2
Place .img in c:\Android
Fastboot flash radio
fastboot flash radio radio.img
fastboot reboot
Fastboot flash boot logo
fastboot flash logo logo.bin
fastboot reboot

Reserved 3

Reserved.

Thank you so much for sharing these with us!!!!!:good:

Awesome post!

a lot of useful information =) this help me a lot

Excellent compilation !!
This is a one stop thread for those Atrix owners looking to get their doubts and queries about the bootloader unlocking procedure answered comprehensively. It sure did that for me!!

In Atrics (CM9) - 14/11/12, every time the super user privileges to provide a program, get the reboots when the screen turns off. The super user is already updated and nothing!

freezerj said:
In Atrics (CM9) - 14/11/12, every time the super user privileges to provide a program, get the reboots when the screen turns off. The super user is already updated and nothing!
Click to expand...
Click to collapse
Reinstall the rom
Enviado desde mi MB860 usando Tapatalk 2

HDMI Problem
hello guys, sorry if i didn't follow rules, but maybe some1 can answer me.
i have HDMI mirroring problem. when i attach phone on Lapdock, it says No Signal, Input : HDMI.
any solutions?

I'm using a jb custom rom and the 3g sometimes turns itself on without me initiating it! Any ideas?
Spilled from my Atrix4g utilizing Tapatalk

This is not a help thread.
Questions go in Q&A.
Please keep the discussion relevant to info in the OP.
Thanks!

Incoming Calls no contact Names
I have recently installed miui android version 4.1.2(MIUI 2.12.7)
However I everytime i get a call, the caller's name is not shown and instead i get to see only the number in the format +254722XXXXXX!! This despite having saved the contacts name and number in my google account which is synced. Im using a motorola Atrix (MB860),Carrier is Airtel Kenya
thanks in advance for any help

In case of infinite loop - Alternative method
Yeah,
I tried another method that worked like a charm for me :
- Start in fastboot mode (maintain power + volume down --> repeat down to choose fastboot --> validate with up volume)
- On your computer, open "cmd" command (windows + R --> CMD)
- Type : "fastboot -w" this command will erase user data
- Type : "fastboot reboot"
That is all.

[GUIDE][SPRINT-1056] Unlock SiM, Flash Retail LolliPop 5.1,Stop PRL updates

Dear All,
A few days ago SPRINT moto X 1056 gets Firmware Update of about 5.4 MB.. After that update alot of people which have moto x 1056 and they are not using Sprint network get them sim locked.. Sim was not recognized and default network was selected "sprint" on the mobile and also the nv-items files were changed to Read Only Mode. Also after the update.. People keep getting UPDATE PRL on every restart.
Click to expand...
Click to collapse
I have also got in trouble after this update and researched about 3 days to get my problem solved.
The things u need to do is to
Install Motorola Drivers.
Backup Your Personal Data.
Install adb + fastboot (I recommend to use mfastboot).
Unlock Your Boot Loader.
Flash TWRP Recover throug fastboot.
Wipe Everything " System, Cache, Dalvik Cache, Internal Storage, Data" (After this u will have no OS in your mobile)
(OPTIONAL: If your phone have "SPC code" . Then you need to Flash "161.44.32.ghost_sprint.Sprint.en.US[1].zip" through TWRP. and get your SPC code then unlock the sim) In my Case i dont have SPC code set in my phone and i was able to unlock sim without giving SPC code on firmware 4.4.4 pre 5.4 mb update.
Click to expand...
Click to collapse
Flash Firmware "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml"
Unlock Sim
Flash LolliPop 5.1 "Version: 222.21.15.ghost_row.Retail.en.US" (To Remove Update PRL messages/things)
Remove Bootloader Warning Message (Flash [GHOST] Moto-WinterBoot-20150419-STABLE)
Note: This GUIDE is for MOTO X SPRINT [XT1056]
Now Lets Get Starting with Steps.
1. Install Motorola Drivers.
Downlod the drivers from the following link and install it.
"https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481"
Or
"http://motofirmware.center/files/file/41-motorola_end_user_driver_installation_640_32bitzip/"
Click to expand...
Click to collapse
2. Backup Your Personal Data.
Connect your device to your PC. Check Usb Options selected to "MTP" on your device.
Backup your personal data on phone.
Click to expand...
Click to collapse
3. Install adb + fastboot (I recommend to use mfastboot).
You can install adb + fastboot by installing Android-SDK. To Install Android SDK. Download the Standalone Android-SDK from following Link.
"http://developer.android.com/sdk/index.html#Other"
and now watch the following Guide to install and set parameters of Android-SDK.
"https://www.youtube.com/watch?v=oaNM-lt_aHw"
OR as i said i Recommend to use "mfastboot"
You can download mfastboot from following link
"http://www.mediafire.com/download/6b3aw3dq8omefyw/mfastboot-v2.zip"
Just download and unzip it to use
Click to expand...
Click to collapse
4. Unlock BootLoader:
You can easily unlock bootloader of your device by clicking
"https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b"
OR watch this video for 100% Success.
https://www.youtube.com/watch?v=3sxgz7jxRMw
Click to expand...
Click to collapse
5. Flash TWRP Recover throug fastboot.
Download latest TWRP recovery from link
"http://techerrata.com/browse/twrp2/ghost"
Now, Install TWRP using this site method.
"https://twrp.me/devices/motorolamotox2013.html"
Click to expand...
Click to collapse
6. Wipe Everything " System, Cache, Dalvik Cache, Internal Storage, Data" (After this u will have no OS in your mobile)
After installing recovery . Go to recovery by following method.
Hold and press VOL DOWN + POWER button for 5 secs and release.
Now u r in bootloader. Go to recovery by VOL DOWN button and select by VOL UP button.
Now go to WIPE > Advanced > and then wipe All folders. except USB OTG.
Now you have NO OS installled on ur Moto X.
Reboot to Recovery to bootloader again.
Click to expand...
Click to collapse
7. Flash Firmware "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml"
Now its time to flash the pre 5.4 mb update firmware to your moto x xt1056.
Download the firmware from here
"http://www.filefactory.com/file/6tiwapkl82jl/"
And flash through fastboot. just extract the zip file and copy all files and folders in "Mfastboot folder" 0r "android-sdk folder"
Now open Mfastboot folder and press "Shift key + Right Click" now click "Open Command Prompt here"
Perform the following steps as i have performed .
Click to expand...
Click to collapse
C:\mfastboot-v2>mfastboot devices
T063204CVP fastboot
C:\mfastboot-v2>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.275s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.468s]
finished. total time: 0.743s
C:\mfastboot-v2>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.368s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing aboot ...
OKAY [ 5.049s]
finished. total time: 5.419s
C:\mfastboot-v2>mfastboot flash logo logo.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'logo' (628 KB)...
OKAY [ 0.343s]
writing 'logo'...
OKAY [ 0.879s]
finished. total time: 1.224s
C:\mfastboot-v2>fastboot flash boot boot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.920s]
writing 'boot'...
OKAY [ 1.358s]
finished. total time: 2.280s
C:\mfastboot-v2>mfastboot flash recovery recovery.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (10240 KB)...
OKAY [ 0.928s]
writing 'recovery'...
OKAY [ 0.968s]
finished. total time: 1.898s
C:\mfastboot-v2>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [ 16.692s]
writing 'system'...
OKAY [ 10.502s]
sending 'system' (262144 KB)...
OKAY [ 16.684s]
writing 'system'...
OKAY [ 9.854s]
sending 'system' (262144 KB)...
OKAY [ 16.683s]
writing 'system'...
OKAY [ 8.245s]
sending 'system' (114215 KB)...
OKAY [ 7.443s]
writing 'system'...
OKAY [ 3.613s]
finished. total time: 89.725s
C:\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53804 KB)...
OKAY [ 3.664s]
writing 'modem'...
OKAY [ 2.468s]
finished. total time: 6.134s
C:\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.437s]
finished. total time: 0.439s
C:\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.445s]
finished. total time: 0.445s
C:\mfastboot-v2>mfastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'fsg' (1223 KB)...
OKAY [ 0.386s]
writing 'fsg'...
OKAY [ 0.828s]
finished. total time: 1.216s
C:\mfastboot-v2>mfastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.164s]
finished. total time: 0.165s
C:\mfastboot-v2>mfastboot reboot
rebooting...
finished. total time: 0.001s
C:\mfastboot-v2>
C:\mfastboot-v2>
Click to expand...
Click to collapse
Now please Proceed to Next POST.

2nd Post
After flashing the 4.4.4 firmware. Now the device should boot and start the Android. But notice after starting and every restart It automatically checks the Profile and PRL activations. Now time to unlock your Sim.
8. Unlock Sim.
To unlock your sim follow the following guide here on XDA.
"http://forum.xda-developers.com/showpost.php?p=54338871&postcount=2"
Note: In my case i have checked and there is no SPC code needed to sim unlock. No need to check spc code checkbox in NV-ITEMS-READER-WRITER software.
So the you just connect your phone to nv items reader writer software and flash only
nv-unlock.txt
nv-unlock2,txt
unlock-domestic.txt
nv-ruim files need SPC code to write . If u dont have SPC code set in your phone for enable / disable DIAG PORT then you dont need to write nv-ruim files.
Click to expand...
Click to collapse
Congrats. U have Sim-Unlocked Moto X Sprint .
9. Flash LolliPop 5.1 "Version: 222.21.15.ghost_row.Retail.en.US"
Download LolliPop Retail 5.1 from following link.
"https://drive.google.com/file/d/0BzTDEHw-bGypMGhfdEFVczd1dHM/view"
This is XT1053 untouched Retail ROM
Open TWRP recovery. and Flash the ROM by clicking Install . Select the location where you copy the zip rom in internal memory.
After installing the ROM , Reboot to TWRP Recovery again and WIPE CACHE and DALVIK CACHE.
Then reboot to system. Now it should start the OS 5.1 and there should not PRL updation on start and restart.
Click to expand...
Click to collapse
Now you have unlocked your sim and have Lolipop 5.1 with Stock System Version 222.21.15
10. Remove Boot-loader Warning .
Download your favorite Boot Animation Image from the link
"https://drive.google.com/folderview?id=0Bx0JlaDkWMGAfkpQcGl2M3NCWi11SmZ5N3hiV05EdFFERzRrNUhBcjNjb0JXRU5fQ2lDZjg&usp=drive_web "
Copy it in mobile memory. and Then install through TWRP. Again now wipe Dalvik Cache and Cache. Restart to System.
Click to expand...
Click to collapse
For StageFright Update:
Make your nandroid backup first.
Now Download this System image from "https://mega.nz/#!LwEXWRLB!NAQBXMwI6aoNNw7VXB_u3m3XjEOSiZ_bUGcbBL1ykTk"
Now flash this system.img through TWRP.
Clear your Cache and Dalvik Cache.
Download the Stagefright System 222.27.5 TWRP backup from the above link
Unzip the Stagefright System 222.27.5 folder to your computer
Copy the Stagefright System 222.27.5 folder to your phones internal storage, to the TWRP/BACKUPS/TA0000008VJ/ directory
Reboot your phone into recovery (TWRP)
Click Restore and select the Stagefright System 222.27.5 folder
Verify that the System partition is selected and then Swipe to Restore
Clear your cache
Click to expand...
Click to collapse
Now this update should flash and phone should work fine,
Credits Goes to mastarifla
Now You have Sim Unlocked Lolipop 5.1 with Removed Bootloader Warning Message.

Credits
All Credits Goes to
XDA-Developers
Ghost_Developer for
http://forum.xda-developers.com/moto-x/themes-apps/ghost-original-bootanimations-unlocked-t3087294
Perseus for
http://forum.xda-developers.com/moto-x/general/index-welcome-to-motorola-moto-x-t2558785
d_shadow for
http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
VitaTaf for
http://forum.xda-developers.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843
samwathegreat for
http://forum.xda-developers.com/showpost.php?p=54338871&postcount=2

My Sprint 2013 Moto X just got an update last night and now this is happening to the phone. It has no calling capabilities now but has data. This is also not a developer edition phone so I don't see how iwould be able to do all of this like unlocking the bootloader and all this flashing. It seems like put simply, sprint pushed out an update and bricked my phone in terms of making and receiving calls. Is there no other solution to this? What would they do if I take it to the store?

Files for getting SPC
For those who needs the SPC, here are the links for the needed files:
4.4.2 TWRP Flashable ROM (thanks to Aaron Nickolopoulos for uploading and sharing the link)
4.4.2 Modem (can be flashed thru RSD Lite or fastboot) (uploaded by me )
Advice for the future: Use EFS Professional to change SPC to 000000

m0ndul said:
For those who needs the SPC, here are the links for the needed files:
4.4.2 TWRP Flashable ROM (thanks to Aaron Nickolopoulos for uploading and sharing the link)
4.4.2 Modem (can be flashed thru RSD Lite or fastboot) (uploaded by me )
Advice for the future: Use EFS Professional to change SPC to 000000
Click to expand...
Click to collapse
this in regards to me?

emerica243 said:
this in regards to me?
Click to expand...
Click to collapse
To all of us, happened to me also

fastboot.exe has stopped working when flashing system.img.
Any one had this problem ?
C:\android-sdk\platform-tools>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
Thats all it gives me then crashes

you have to use mfastboot flash system system.img

m0ndul said:
For those who needs the SPC, here are the links for the needed files:
4.4.2 TWRP Flashable ROM (thanks to Aaron Nickolopoulos for uploading and sharing the link)
4.4.2 Modem (can be flashed thru RSD Lite or fastboot) (uploaded by me )
Advice for the future: Use EFS Professional to change SPC to 000000
Click to expand...
Click to collapse
hi there can u please tell me how to get spc on 4.4.4 motox sprint i would really appreciate ur help
EDIT: got my spc by downgrading to 4.4.2

yar_nl said:
you have to use mfastboot flash system system.img
Click to expand...
Click to collapse
If you're using mfastboot, then yes that's the command.
I'm using android-sdk. For android sdk comand is :
fastboot flash system system.img
Managed to make it work with RSD lite.
Sent from my iPhone 6s Plus using Tapatalk

Superpopsss said:
If you're using mfastboot, then yes that's the command.
I'm using android-sdk. For android sdk comand is :
fastboot flash system system.img
Managed to make it work with RSD lite.
Sent from my iPhone 6s Plus using Tapatalk
Click to expand...
Click to collapse
See this thread of why use mfastboot for details http://mark.cdmaforums.com/MotoX-mFastboot.htm
---------- Post added at 04:01 PM ---------- Previous post was at 03:53 PM ----------
For those who know their MSL/SPC code see --> http://forum.xda-developers.com/showpost.php?p=63585276&postcount=959

yar_nl said:
See this thread of why use mfastboot for details http://mark.cdmaforums.com/MotoX-mFastboot.htm
---------- Post added at 04:01 PM ---------- Previous post was at 03:53 PM ----------
For those who know their MSL/SPC code see --> http://forum.xda-developers.com/showpost.php?p=63585276&postcount=959
Click to expand...
Click to collapse
Good to know, but it's easier to use rds lite then manually flashing all the files needed :
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit

Superpopsss said:
Good to know, but it's easier to use rds lite then manually flashing all the files needed :
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
Click to expand...
Click to collapse
http://www.droidviews.com/restore-moto-x-to-stock-firmware-using-rsd-lite/

yar_nl said:
http://www.droidviews.com/restore-moto-x-to-stock-firmware-using-rsd-lite/
Click to expand...
Click to collapse
Exactly, takes 1 min compared to the potential errors you could encounter by flashing manually.

Superpopsss said:
fastboot.exe has stopped working when flashing system.img.
Any one had this problem ?
C:\android-sdk\platform-tools>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
Thats all it gives me then crashes
Click to expand...
Click to collapse
Please use mfastboot

emerica243 said:
My Sprint 2013 Moto X just got an update last night and now this is happening to the phone. It has no calling capabilities now but has data. This is also not a developer edition phone so I don't see how iwould be able to do all of this like unlocking the bootloader and all this flashing. It seems like put simply, sprint pushed out an update and bricked my phone in terms of making and receiving calls. Is there no other solution to this? What would they do if I take it to the store?
Click to expand...
Click to collapse
Take it to sprint store is the best solution.

Hi, can you please let me know how did you install 4.4.2 thought TWRP. I downloaded 4.4.2 from the link provided here.
Thanks
MAJID
​
ameraze said:
hi there can u please tell me how to get spc on 4.4.4 motox sprint i would really appreciate ur help
EDIT: got my spc by downgrading to 4.4.2
Click to expand...
Click to collapse
---------- Post added at 09:38 AM ---------- Previous post was at 09:35 AM ----------
Hello, I followed till step 8, but my phone is still giving sim card error, any other suggestion?
flopadmi said:
After flashing the 4.4.4 firmware. Now the device should boot and start the Android. But notice after starting and every restart It automatically checks the Profile and PRL activations. Now time to unlock your Sim.
8. Unlock Sim.
Congrats. U have Sim-Unlocked Moto X Sprint .
9. Flash LolliPop 5.1 "Version: 222.21.15.ghost_row.Retail.en.US"
Now you have unlocked your sim and have Lolipop 5.1 with Stock System Version 222.21.15
10. Remove Boot-loader Warning .
Now You have Sim Unlocked Lolipop 5.1 with Removed Bootloader Warning Message.
Click to expand...
Click to collapse
---------- Post added at 09:59 AM ---------- Previous post was at 09:38 AM ----------
Hi,
if i install only 4.4.2 modem file, shall it be helpful to run SPC utility?
and if yes....then do i have to execute all below commands or just the first one?
C:\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53804 KB)...
OKAY [ 3.664s]
writing 'modem'...
OKAY [ 2.468s]
finished. total time: 6.134s
C:\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.437s]
finished. total time: 0.439s
C:\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.445s]
finished. total time: 0.445s
m0ndul said:
For those who needs the SPC, here are the links for the needed files:
4.4.2 TWRP Flashable ROM (thanks to Aaron Nickolopoulos for uploading and sharing the link)
4.4.2 Modem (can be flashed thru RSD Lite or fastboot) (uploaded by me )
Advice for the future: Use EFS Professional to change SPC to 000000
Click to expand...
Click to collapse

hmajid_039 said:
Hi, can you please let me know how did you install 4.4.2 thought TWRP. I downloaded 4.4.2 from the link provided here.
Thanks
MAJID
​
---------- Post added at 09:38 AM ---------- Previous post was at 09:35 AM ----------
Hello, I followed till step 8, but my phone is still giving sim card error, any other suggestion?
---------- Post added at 09:59 AM ---------- Previous post was at 09:38 AM ----------
Hi,
if i install only 4.4.2 modem file, shall it be helpful to run SPC utility?
and if yes....then do i have to execute all below commands or just the first one?
C:\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53804 KB)...
OKAY [ 3.664s]
writing 'modem'...
OKAY [ 2.468s]
finished. total time: 6.134s
C:\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.437s]
finished. total time: 0.439s
C:\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.445s]
finished. total time: 0.445s
Click to expand...
Click to collapse
If u have downloaded 4.4.2 rom then open twrp recovery and click on install.. Then select zip file....
If u have downloaded 4.4.2 firmware then u need to flash through mfastboot or rsd lite...
Yes if u need only to flash modem then please execute the all three commands representing modem...
For unlock sim. Please tell me rather u can enable / disable ur DIAG port with spc code or without soc code ?

Hi, I have 4.4.2 rom with zim file. I did the same through twrp. But after that my phone goes black after showing statrup moto logo/animation..
Currently again i am back on 4.4.4 with sim card error.
And I am also unable to enable DIAG port.

Please Help me! I can't flash stock rom

Hello I'm trying to flash stock ROM via adb, specifically cust.img, boot.img, system.img, Because I've bricked my phone and it stuck on huawei logo, but when i try to flash, i got the following error "FAILED (remote: Command not allowed)"
Code:
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (304183 KB)...
OKAY [195.875s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 195.899s
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21690 KB)...
OKAY [ 13.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.694s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [314.622s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 314.665s
Please how I can unbrick my phone and reinstall the firmware
Obs. My bootloader is unlocked and I'm using TWRP recovery

Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens.
In later days, we've got a lot of troubleshooting topic opened up with your problem, the users cannot flash even with unlocked bootloader, and yet, there's no real solution to them.

I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux

daviddosa said:
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens..
Click to expand...
Click to collapse
Yes, it shows PHONE unlocked in red name, and I've made the root using an app called kingroot
I've tried to erase cache and userdata using adb but I can't, still got the same error "FAILED (remote: Command not allowed)"
I can't make dload method because I don't have stock recovery, and I can't flash the stock recovery using adb because its keep saying "FAILED (remote: Command not allowed)".
I don't know what to do
sokkoban said:
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
Click to expand...
Click to collapse
I'm using windows 7 is this moment, maybe I try to flash using Linux later

Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.

daviddosa said:
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
Click to expand...
Click to collapse
So I tried to create a flashable zip using the Huawei Update Extractor however, was not possible, it's showing the following message "no suitable files selected. Check profiles.xml"
I've tried also creating flashable zip manually and flash it using TWRP, but TWRP reboot every time I try to flash theses files, that's why I think dload method work only with stock recovery

Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file

sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
Thanks for the help but this method didn't work, everytime I try to flash the files, I got the same error "FAILED (remote: Command not allowed)” I don't know what is happening my bootloader is unlocked, why I can't flash the files with adb
Code:
target max-download-size: 450MB
sending 'boot' (21690 KB)...
OKAY [ 13.912s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.919s
target max-download-size: 450MB
sending 'recovery' (34264 KB)...
OKAY [ 21.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 21.985s
target max-download-size: 450MB
sending 'cust' (304183 KB)...
OKAY [191.580s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 191.603s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [366.120s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 366.144s
ROM flashed , if all went well
You must be restarted.
If you leave the recovery to hard reset and restart the phone
Created by sokoban. Thank you for using my release
rebooting...
finished. total time: 0.054s
Pressione qualquer tecla para continuar. . .

This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo

sokkoban said:
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble

Same issue with Huawei G6-U10
I'm having the same problem with Huawei Ascend G6-U10
Currently running on ROM b146, since it has some issues I was trying to downgrade or upgrade ( there is a b330 out).
I'm not an expert.
This morning I've unlocked the boot loader and then tried to flash a couple of different ROMs and I always get the same error message:
c:\adb>fastboot flash BOOT ./G6-U10verb330/boot.img
target reported max download size of 536870912 bytes
sending 'BOOT' (9696 KB)...
OKAY [ 0.310s]
writing 'BOOT'...
FAILED (remote: Command not allowed)
finished. total time: 0.321s
c:\adb>fastboot oem get-bootinfo
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
I'm guessing this is not a G6-U10 specific issue so if anyone can give any hint it'll be very appreciated.
Thanks.

I have the same problem with a honor 4x.
Rooted with kingroot. We haven't writing permission in /system. That's why we can't install the recovery. If you try to install superSU and update the binary I guess you get an error.
Now the question is: how we can do to make writeble /system with fast boot?
"mount -o rw,remount -t ext3 /dev/block/xxxxxxxxx /system" in terminal doesn't work...

Similar thing happened to me. Even if command for showing unlocked bootloader said it was unlocked that was false because I used Kingroot previously. Only thing that helped was to unlock the bootloader through fastboot again. Then it was really unlocked and I could flash recovery (in my case TWRP) which before I was unable to.

Diego Sousa said:
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Click to expand...
Click to collapse
Have you tried it with linux yet?
And have you used the Update.APP and dload method?

Maybe a driver problem? Have administrator rights? And debug mode on?
Try to connect your phone (power on) to the pc and wait to be recognized. In cmd type this:
Code:
adb devices
It has to show you your serial number right? If doesn't your device is not being recognized by adb.
Next type:
Code:
adb reboot-bootloader
This will restart your phone into fastboot and now you can type "fastboot devices" like first command and it has to show you your serial number again.
Try rebooting into bl with this, not by plugin in the phone, and install the rom again

Huawei P8 Lite
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here

Have you tried install it in twrp? You don't have a twrp backup of stock rom?
In this case if you go in the Huawei eRecovery you can restore stock rom and twrp will be overwrited downloading the last rom , i tried it with my p8 lite 2017 .

Tuki2 said:
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Click to expand...
Click to collapse
What are you using to go into fastboot mode? Is it ADB from Android SDK?? It turns out that using ADB from Android SDK lets you flash small files but not large files... I suggest you try flashing the file through Minimal ADB & Fastboot

sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
i have the same issue as well, but just with Cust.img

Phone bricked after a crash - Flash modem_a error

Hello,
I have a Mi A1 since one week and I have already a large problem.
The problem began with a basic crash on an app (Facebook). The phone didn't respond and I turned off the phone.
When I turned on, the phone was stuck on the boot image (White screen with Mi Logo and Google colors). I tried to turn off and on several times but it didn't work.
I opened the phone and disconnected the battery but always the same problem.
Then, I booted the phone in fastboot and unlocked it via the command fastboot oem unlock. Then I tried to flash the stock ROM via fastboot. I choosed this version : Android 7.1.2 Nougat (N2G47H.7.12.7) because I had the last update (from : https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/).
Immediately i have this error :
Code:
fastboot flash modem_a C:\Users\Lau\Desktop\tissot_images_7.12.7_7.1\images\modem.img ||
target reported max download size of 536870912 bytes
sending 'modem_a' (86016 KB)...
OKAY [ 2.466s]
writing 'modem_a'...
FAILED (remote: flash write failure)
finished. total time: 2.499s
"Flash modem_a error"
I tried to flash with Miflash tool 2017.7.20 but I have the same message, Flash modem_a error.
I also tried to boot the phone in EDL Mode with fastboot_edl, the phone reboot, I have a message your device software cannot be checked for corruption and then the boot screen (with the messsage "Unlocked") and after 30 seconds, I have the black screen with the droid and "No command" (https://scache.vzw.com/kb/images/google/pixel/android_system_recovery_no_command.jpg )
Someone should have an idea to restore the phone ?!
Thanks a lot !

That screen with "No command" is usually related to the recovery. If I remember well, once in that screen, you have to press and hold power button for few seconds then press and release volume up button to enter in recovery. By reading your post I can see you didn't even try the most easy thing: A factory Reset! Try to wipe data from recovery if you can enter in it.
The modem error could be related at the fact that you're flashing a firmware that is not global or for your country. Try to change firmware version and make sure it is the right firmware region.
Inviato dal mio G8141 utilizzando Tapatalk

Thank for the quick answer.
I thinked to the recovery but I didn't know how to acces. With your help, I found and I made a wipe data. It made 5 minutes I have the message Formatting /data.... It seems too long... :/
EDIT : I stopped the wiping, it's seems it was block.
When you spoke of an other firmware, do have you a link ? Here is the information of my phone
Code:
xiaomi/tissot/tissot_sprout
71.2/N2G47H/7.12.19

This is a link to the October release of the Rom
https://androidfilehost.com/?fid=745849072291684522
This is a guide of how to flash it with Mi Flash Tool
https://forum.xda-developers.com/mi-a1/how-to/rom-factory-images-t3688548
If you are not able to flash with Mi Flash tool, try this guide to Flash manually via fastboot.
Once in fastboot (i suggest you to use the official one included in Android SDK becouse are the most updated ones and don't use some other installer like minimal. Add installer for Windows) follow this guide to Flash firmware images manually. It's for nexuses but the fastboot commands are universal
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Inviato dal mio G8141 utilizzando Tapatalk

Thank you for the link, that was I made.
I tried to flash manually the ROM with fastboot and I found a clue, the filesystem seems not normal...
I have this message :
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.009s
EDIT : And I have the last version of fastboot/adb from there : https://developer.android.com/studio/releases/platform-tools.html

lolo1410 said:
Thank you for the link, that was I made.
I tried to flash manually the ROM with fastboot and I found a clue, the filesystem seems not normal...
I have this message :
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.009s
EDIT : And I have the last version of fastboot/adb from there : https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
You must flash to system_a or system_b, "system" partition really doesn't exist.

Indeed, it's work now, it's flashing !
I noticed that for TWRP, there is also a "slot A" and "slot B". Is it new in Android ? Is there 2 kind of system ?
EDIT :
Unfortunately, it didn't work...
I had this message :
C:\adb_new>fastboot flash system_a system.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/6 (522959 KB)...
OKAY [ 15.867s]
writing 'system_a' 1/6...
FAILED (remote: flash write failure)
finished. total time: 15.898s
And here is the log for Miflash :
Code:
[16:52:10 28ba25530704]:MiFlash 2017.7.20.0
[16:52:10 28ba25530704]:image path:C:\Users\Lau\Downloads\tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf\tissot_images_7.12.19_7.1
[16:52:10 28ba25530704]:env android path:"C:\Users\Lau\Desktop\miflash\Source\ThirdParty\Google\Android"
[16:52:10 28ba25530704]:script :C:\Users\Lau\Downloads\tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf\tissot_images_7.12.19_7.1\flash_all_except_storage.bat
[16:52:10 28ba25530704]:Physical Memory Usage:1355776 Byte
[16:52:10 28ba25530704]:$fastboot -s 28ba25530704 getvar product 2>&1 | findstr /r /c:"^product: *tissot" ||
[16:52:10 28ba25530704]:product: tissot
[16:52:10 28ba25530704]:$fastboot -s 28ba25530704 oem unlock ||
[16:52:11 28ba25530704]:...
[16:52:11 28ba25530704]:$fastboot -s 28ba25530704 flash modem_a C:\Users\Lau\Downloads\tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf\tissot_images_7.12.19_7.1\images\modem.img ||
[16:52:11 28ba25530704]:(bootloader) Device already : unlocked!
[16:52:11 28ba25530704]:eek:KAY [ 0.030s]
[16:52:11 28ba25530704]:finished. total time: 0.030s
[16:52:13 28ba25530704]:target reported max download size of 536870912 bytes
[16:52:13 28ba25530704]:sending 'modem_a' (86016 KB)...
[16:52:13 28ba25530704]:error:"Flash modem_a error"
[16:52:13 28ba25530704]:"Flash modem_a error"
[16:52:13 28ba25530704]:error:"Flash modem_a error"
[16:52:13 28ba25530704]:process exit.
[16:52:13 28ba25530704]:flashSuccess False
[16:52:13 28ba25530704]:isFactory False CheckCPUID False
[16:52:13 28ba25530704]:before:flashSuccess is False set IsUpdate:True set IsDone True
[16:52:13 28ba25530704]:after:flashSuccess is False set IsUpdate:false set IsDone true

Can you boot into TWRP (use version 3.1.1-0 or 3.1.1-1 "fastboot boot twrp.img")? Do you see /data partition?

Yes I can boot into but I can't install it. Before I tried to flash manually, I was able to unlock the data partition but not anymore (Error : E: Decrypt took too long, killing process - Failed to decrypt data)
I have an access with adb shell.

Some people had luck with flashing persist.img from August update, you might try that as well. There is also a chance that your flash memory is damaged and you will need to visit a service center.

Okay try this.
Download the latest build (android n) from mi firmwares official page.
Unzip the file (http://en.miui.com/forum.php?mod=viewthread&tid=1415168&extra=page=1&mobile=2)
Download miflashtool (http://en.miui.com/thread-807252-1-1.html)- guide & tool.
Past the path in the tool.
Click refresh
Click flash
Boom your good.
Make sure to select clean flash and lock.
ADB and fastboot should be installed.

_mysiak_ said:
Some people had luck with flashing persist.img from August update, you might try that as well. There is also a chance that your flash memory is damaged and you will need to visit a service center.
Click to expand...
Click to collapse
I flashed "persist.img" succesfully but always the same problem, stucked on Boot...
zeyaan said:
Okay try this.
Download the latest build (android n) from mi firmwares official page.
Unzip the file (http://en.miui.com/forum.php?mod=viewthread&tid=1415168&extra=page=1&mobile=2)
Download miflashtool (http://en.miui.com/thread-807252-1-1.html)- guide & tool.
Past the path in the tool.
Click refresh
Click flash
Boom your good.
Make sure to select clean flash and lock.
ADB and fastboot should be installed.
Click to expand...
Click to collapse
I already tried several times but I have always errors (See log of previously post). With Miflash, I succeeded to flash the 2 boot et 2 system but phone is always blocked.
I tried to wipe via TWRP but it blocks on "Formatting Data using make_ext4fs...".
I think I'm good to send it at a service center...

There's a TWRP backup of first beta build oreo.Try restoring it.

Same Problem.

inally he managed to flash the ROM action, thank you very much to everyone for your patience and help, especially PALMATRON and fosco_
He used the tutorial of this link: https://xiaomifirmware.com/roms/down...-xiaomi-mi-a1/
1. Tools Download r26 for Windows.
2. Unzipped the instruments on disk C of my computer.
3. Unzipped the files of the last ROM available for the Xiaomi Mi A1 in the folder C: \ Tools so that the Images folder and the flashing scripts that come with the ROM are included in it.
4. Then double click on flash_all.bat to delete everything and just leave the boot loader open.
5. Automatically start flashing and take about 10-15 minutes and voila!
https://uploads.tapatalk-cdn.com/20171123/37d3867bf5d0fb7967a03a05869914ae.jpg

Try do with clean and lock or just clean i was have the same problem and i fix this only with miflash and after when my mi a1 restarts on boot i copy with terminal persist.img

thanks a lot
Saved my life, thanks. The rom on this link works PERFECTLY - my Mi A1 was stuck on botlooping after a fail tentative to root it.
XDVRMX said:
This is a link to the October release of the Rom
https://androidfilehost.com/?fid=745849072291684522
This is a guide of how to flash it with Mi Flash Tool
https://forum.xda-developers.com/mi-a1/how-to/rom-factory-images-t3688548
If you are not able to flash with Mi Flash tool, try this guide to Flash manually via fastboot.
Once in fastboot (i suggest you to use the official one included in Android SDK becouse are the most updated ones and don't use some other installer like minimal. Add installer for Windows) follow this guide to Flash firmware images manually. It's for nexuses but the fastboot commands are universal
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Inviato dal mio G8141 utilizzando Tapatalk
Click to expand...
Click to collapse

[GUIDE] How to Flash Android 8.1/9.0 on Lenovo Z5 (WiFi and Data also working now)

Hi Guys,
I have finally successfully flashed a phh AOSP 8.1 provided in the following thread to Lenovoz5
Before proceeding, here are the basics,
Do not Ever ever ever EVER flash zui_3.9.075_Z5_L78011_multi
Bootloader needs to be unlocked only if you wantto flash custom Android 9.0 Pie roms,
If you want to stick to stock Lenovo rom, then you do not need to unlock bootloader.
If you start your phone and it says "Your device is corrupt" then your phone has zui_3.9.075_Z5_L78011_multi.
This rom is a dirty version of stock rom, that Chinese sellers sells your phone with. This is not the original rom.
Always use "L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst" for unlocking bootloader, 075, this version is the only version that allows unlocking bootloader.
With other versions like L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.390_ST_180809_qpst, L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.200_ST_180809_qpst
This option is hidden by manufacturer under Developer options.
If you start your phone and you dont get option to activate via Wifi or Network, then your phone doesnt have stock rom and it has been tweaked by your seller.
Here is the download link for stock rom, do not use the rom that has _multi in its name.
https://mega.nz/#F!9953xR6a!76EEVKmW3LtjE7tYPF2Z1Q
If you get Sahara error when flashing through QFIL
1) Make sure your phone is in edl mode, follow the video for that
2) Make sure the config is correctly set in Settings within QFIL
3) Try changing USB ports on your PC, It only works on USB 2.0, will throw error on USB 3.0 and 3.1
Make sure you go through this thread, each and every question is answered already.
If you have any questions, make sure to list out everything you did and what you are trying to do,
My phone doesnt start
I cant proceed
I cant flash
I am stuck
I cant unlock bootloader
This doesnt help, please post full description with screenshots , what you have done to your phone after your received it from your seller, what you want,
Google the basics, bootloader unlocking, stock rom, custom rom, Android 8.0, Android 9.0 etc
I have created Lenovo z5 group on telegram, pls post there if you have any questions, i dont check xda, but i will respond on telegram whenever i can.
Check out this video on how to flash using qfil
https://youtu.be/TdkNaKpiiUw
Go through this thread and read all the posts, most of your questions is probably already answered.
I would recommend if you are not good at flashing then back up all partitions on external sd card. (WIFI and data working now )
To backup stock partitions,
1. Unlock bootloader
2. Flash TWRP through fastboot
3. Boot to TWRP and do a full back up of all partitions.
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
All the credits for the rom goes to developers in that thread, i have only flashed it to Lenovo z5.
Flashing guide for Android 8.1: (Everything is working on Android 9.0, check out second post in this thread.)
What you will need:
ADB: https://www.mediafire.com/file/8j84x6j1g2xb8z6/adb.zip/file
TWRP.img https://drive.google.com/open?id=1yj9Vu-1YqR8kxMReP5pZerpLa-PKnZ1z
boot.img - This is the same boot.img in stock qpst from L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.200_ST_1807 21_qpst
or get it from here https://drive.google.com/open?id=14WNBcstAB3A40fafEhI2NWMAhGBtJge_
vbmeta.img https://drive.google.com/open?id=1dTIuxwKnfZFrE7HFtYSMqUx6gItXvxEB
ROM - system-arm64-ab-gapps-su.img from the above link
superuser flash file (To be flashed through TWRP recovery) https://drive.google.com/open?id=1w0PHZFvfYvExBAEnyDyqBpBjMGLBoLes
superuser apk(not necessary to install) https://drive.google.com/open?id=1XU9pydDRPOZ2weq14j6S-hveM98C8zHe
Procedure to Flash custom rom on Lenovo Z5:
Step 1: Flash stock version L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst using qfil mentioned earlier in this thread
(After flashing this stock rom, if your phone goes in to boot loop then don't worry about it, continue with the rest of the process)
Step 2:Unlock bootloader (This will void your warranty) (unlocking command: fastboot flashing unlock)
Step 3: boot to bootloader
Flash with the following commands.
1. adb reboot bootloader
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. fastboot flash boot_a boot.img
4. fastboot flash boot_b boot.img
5. fastboot -w flash system_a system-arm64-ab-gapps-su.img
6. fastboot -w flash system_b system-arm64-ab-gapps-su.img
7. fastboot flash boot twrp.img
8. Once twrp is flashed, do not turn off or restart your phone, press volume down twice, select option boot to recovery
9. Flash superuser flash file(mentioned above)
10. Do not clear any data or cache, we already did that, Start and Enjoy!
After completing these steps please wait for about 25 to 30 mins
(My logs when i flashed the rom)
c:\adb>adb reboot bootloader
c:\adb>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Sending 'vbmeta' (4 KB) OKAY [ 0.018s]
Writing 'vbmeta' OKAY [ 0.037s]
Finished. Total time: 0.079s
c:\adb>fastboot flash boot_a boot.img
Sending 'boot_a' (52261 KB) OKAY [ 1.795s]
Writing 'boot_a' OKAY [ 0.037s]
Finished. Total time: 1.842s
c:\adb>fastboot flash boot_b boot.img
Sending 'boot_b' (52261 KB) OKAY [ 1.798s]
Writing 'boot_b' OKAY [ 0.036s]
Finished. Total time: 1.843s
c:\adb>fastboot flash system_a system-arm64-ab-gapps-su.img
Sending sparse 'system_a' 1/3 (524284 KB) OKAY [ 18.954s]
Writing sparse 'system_a' 1/3 OKAY [ 0.006s]
Sending sparse 'system_a' 2/3 (488160 KB) OKAY [ 20.940s]
Writing sparse 'system_a' 2/3 OKAY [ 0.005s]
Sending sparse 'system_a' 3/3 (514508 KB) OKAY [ 21.349s]
Writing sparse 'system_a' 3/3 OKAY [ 0.010s]
Finished. Total time: 68.562s
c:\adb>fastboot flash system_b system-arm64-ab-gapps-su.img
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 12466167 4k blocks and 3121152 inodes
Filesystem UUID: 98e2d366-b46f-11e8-9d3d-3d9d543f2291
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending sparse 'system_b' 1/3 (524284 KB) OKAY [ 19.159s]
Writing sparse 'system_b' 1/3 OKAY [ 0.037s]
Sending sparse 'system_b' 2/3 (488160 KB) OKAY [ 20.708s]
Writing sparse 'system_b' 2/3 OKAY [ 0.007s]
Sending sparse 'system_b' 3/3 (514508 KB) OKAY [ 21.250s]
Writing sparse 'system_b' 3/3 OKAY [ 0.007s]
Erasing 'userdata' OKAY [ 3.849s]
Sending 'userdata' (4348 KB) OKAY [ 0.167s]
Writing 'userdata' OKAY [ 0.007s]
Finished. Total time: 73.993s
c:\adb>fastboot flash boot twrp.img
Sending 'boot_a' (58524 KB) OKAY [ 2.021s]
Writing 'boot_a' OKAY [ 0.007s]
Finished. Total time: 2.041s
c:\adb>adb reboot bootloader
c:\adb>fastboot erase cache
Erasing 'cache' FAILED (remote: 'Check device console.')
Finished. Total time: 0.013s
Not working:
Notification LED (Thanks to DarkerMaster)
Pictures taken by camera are always 90 degrees rotated
Google Camera app is crashing
Working on Android 8.1:
Call
Camera
Fingerprint reader
WIFI
Mobile data ...
Almost everything
I am still testing the device. I will post details later.
Android 8.1
https://drive.google.com/open?id=1k1bgp3sLedy-e5vqYKZF47WXRIVfO-tN
https://drive.google.com/open?id=11RAiDNS-1_bv7ceYJDLriOuGtMIkfbXt
https://drive.google.com/open?id=1hDrJHaKKHhowWJSvVUN3Y9scZeCMMLIz
https://drive.google.com/open?id=1bvKErzYwF9qH87Leie_acnwElINM8qxQ
https://drive.google.com/open?id=1Sg5mHLgm6_Bl4xz3ZBrgq7sLDbrveGWg
https://drive.google.com/open?id=1XxaiVKaImXZ64mH-TwuXcXNEFaTn2ydK
https://drive.google.com/open?id=1ABII2x3hWMKwgTr8mVxI-cYTiej1lVlN
https://drive.google.com/open?id=1rn7CXYnhiiiDBYoF_K1us9vXjgTMOigq
Imp:
If you have flashed one of these Roms, and you can boot in to it successfully, please do not use Factory reset. If you do, then the rom wont boot, since Magisk/SU is installed.
If you still do, then boot to Bootloader, flash vbmeta, boot_a, boot_b, twrp, Magisk(Android 9)/SU(Android 8).
If you have unlocked bootloader, do not relock it, ever
Special Thanks to phhusson for his [AOSP 8.1] [2018-08-16] Phh-Treble
Experimental:
Zui FM Radio app (Not working yet!)
Please note this is still under development, i am only posting it here, if anyone wants to work on it.
https://drive.google.com/open?id=1raHCHhMxOQVM8L0rbSjoKeTVLmbtBSIc
Don't forget to hit that Thanks button !
Cheers

Android 9.0 flashing guide
Back up all partitions on external sd card.
Check out this video on how to flash using qfil
https://youtu.be/TdkNaKpiiUw
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Rom: PixelExperienceP-arm64-ab.zip
All the credits for the rom goes to developers in that thread, i have only flashed it to Lenovo z5.
What you will need:
TWRP.img https://drive.google.com/open?id=1yj9Vu-1YqR8kxMReP5pZerpLa-PKnZ1z
boot.img - This is the same boot.img in stock qpst from L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.200_ST_1807 21_qpst
or get it from here https://drive.google.com/open?id=14WNBcstAB3A40fafEhI2NWMAhGBtJge_
vbmeta.img https://drive.google.com/open?id=1dTIuxwKnfZFrE7HFtYSMqUx6gItXvxEB
ROM - PixelExperienceP-arm64-ab.img from the above link
Magisk superuser flash file (To be flashed through TWRP recovery) https://drive.google.com/open?id=1FV_ogrSU488bpI_hhuyA8rHm3Fj_xLqb
Magisk superuser apk https://drive.google.com/open?id=1hi_58d1nJ-PNe3aPKb_0YsLrh5ElOXVn
Step 1: Flash stock version L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst using qfil mentioned earlier in this thread
(After flashing this stock rom, if your phone goes in to boot loop then don't worry about it, continue with the rest of the process)
Step 2:Unlock bootloader (This will void your warranty) (unlocking command: fastboot flashing unlock)
Step 3: boot to bootloader
Flash with the following commands.
1. adb reboot bootloader
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. fastboot flash boot_a boot.img
4. fastboot flash boot_b boot.img
5. fastboot -w flash system_a PixelExperienceP-arm64-ab.img
6. fastboot -w flash system_b PixelExperienceP-arm64-ab.img
7. fastboot flash boot twrp.img
8. Once twrp is flashed, do not turn off or restart your phone, press volume down twice, select option boot to recovery
9. Flash Magisk flash file(mentioned above, once this is done take pictures of the TWRP logs)
10. Do not clear any data or cache, we already did that
11. On first boot install Magisk apk mentioned above. That's it !
Not working:
Notification LED
Working on Android 9:
Call
Camera
Fingerprint reader
WIFI
Mobile data(4G not sure about 3G)
Google Camera (If app crashes then follow procedure in this thread https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-enable-camera2-api-t3419579 )
Almost everything
Android 9.0
https://drive.google.com/open?id=1L_q2b8V0V7lIafcQsMVbKgqyRq3Tt2Hp
https://drive.google.com/open?id=1grkAu-FhZ56LKN82ubXYN3163ChTUVwr
https://drive.google.com/open?id=1yd5B0HN9Bund6UbJrEScbRsvrofExtT2
https://drive.google.com/open?id=1lWnH408p6aIREmEzl8IIKyE4UKS5V0Nk
https://drive.google.com/open?id=12EDJRbNm_4KVPD72FJ4Yem0gt3XE-BVr
https://drive.google.com/open?id=1RBt2miHzcvC9punEytJd_9aRyDwwhtV9
https://drive.google.com/open?id=1saTXcINKgbjw4HKxvRrSlbPrYk6GJfRr
https://drive.google.com/open?id=1QfLT5_gUk6k3U7o6ZJig8skn7Ckr--GK
https://drive.google.com/open?id=1pWJxmxO-ZzdNdGCK4LVO_zqxKpCQV5fG
Some snaps taken from the phone
https://drive.google.com/open?id=1w0GCNHKjuhE3x_A6xAwVgkYua0pMWGj-
https://drive.google.com/open?id=1GZ4LXyBHOL-zWEXrJVSMRPc07Nabg-eB
https://drive.google.com/open?id=1kTyVHk2Gr8LHekjvn7AwtnC92xrj0_7G
https://drive.google.com/open?id=1qgADqYoePMN9B5OMcpXw2pUc5DYXPCLI
If Windows doesnt detect phone in File Transfer mode:
Enable Developer options, turn off USB debugging.
If Mobile data doesnt work:
Settings > mobile data > Preferred network type = 4G and Choose your network providers Access point, if there is none then create one.
Special Thanks to EnesSastim and phhusson for their [9.0][GSI] PixelExperience P - UNOFFICIAL
Follow this process if you want to remove encryption:
This will delete the os and data on your phone. please backup everything before proceeding. External SD card will be untouched.
Flash L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.390_ST_180809_qpst via qfil (This step is to flash latest persist, firmware, vendor etc images available in 390, if you want to stay on 075 and you already have this stock image flashed, then you can skip this step)
TWRP: https://forum.xda-developers.com/an...overy-lenovo-z5-special-edition-twrp-t3850041
boot.img and persist.img are from version 390 of stock rom. (you can also use 075 images)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash boot recovery-TWRP-3.2.3-1002-LENOVO_Z5-CN-wzsx150.img
Press volume down button twice and go to Recovery
(change language to english if needed)
In recovery backup all of your partitions on to External SD card.
Mount system, persist, firmware
Advanced > RM Forceencrypt
Select Remove DMVerity and Remove Forceencrypt
Swipt to confirm
(This should not throw any error in red fonts, should show Done in the end)
(If it says failed to mount Persist, then reboot to bootloader, fastboot flash persist persist.img)
In recovery goto Wipe
Select Format Data
type Yes (This will remove the encryption)
Reboot to bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash persist persist.img
fastboot -w flash system_a PixelExperienceP-arm64-ab.img
fastboot -w flash system_b PixelExperienceP-arm64-ab.img
fastboot flash boot twrp.img (older version of TWRP)
Boot to TWRP and flash Magisk
Here is the link to the video
https://www.youtube.com/watch?v=brS5tqfx2BQ&index=3&list=PLNqXvI29Azcg9lxA_n6ltytf9aFhn3T1d&t=1081s
download for 075
https://mega.nz/#F!9953xR6a!76EEVKmW3LtjE7tYPF2Z1Q
Return to Stock:
Downloads : ZUI5 https://drive.google.com/open?id=1IL8Pu3Ame9gu6jqAAkBQrEiRL1a93rHK
ZUI10 https://drive.google.com/open?id=1ANAZXbbygyZHAVNGmgoPimJ1fIKbK38D
Credits for ZUI 5 and Zui 10 goes to @M.Z.F and the original developer of the images in these zip files.
https://forum.xda-developers.com/android/development/lenovo-z5-custom-roms-pie-t3904607
Steps to return to stockbackup your data or everything will be wiped)
IF you are on Android 9.0
1) go to TWRP and back up all partitions on SD card (persist, vendor, system, data, boot, firmware, ... )
Step 2 and 3 will turn encryption on, so if u want to disable encryption, after step 3, flash recovery-TWRP-3.2.3-1020-LENOVO_Z5-CN-wzsx150.img and disable encryption. v 474 has new firmware and i have seen better call reception and data connectivity.
2) Flash stock L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst through QFIL
3) Flash stock L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.474_ST_190118_qpst through QFilL
4) Boot to bootloader
5) go to Zui5 folder (link is above) and click on Batch.bat file
6) Press 2, Hit enter, enter, enter
7) phone will automatically restart and boot to ZUI5
8) go to ZUI10 folder and click on Batch.bat
7) Press 2, Hit enter, enter, wait for phone to restart.
Congrats you are back to stock ZUI.
Don't forget to hit that Thanks button !
Cheers

Wooow! A few questions%
Have you tested camera? How is the quality?
Also Android 9 working ok? What is the file.Zip that should be downloaded and flashed from the Pixel Experience list in the second link?
First link of Android 8.1 doesn't work.
Thanks!

nfraccar said:
Wooow! A few questions%
Have you tested camera? How is the quality?
Also Android 9 working ok? What is the file.Zip that should be downloaded and flashed from the Pixel Experience list in the second link?
First link of Android 8.1 doesn't work.
Thanks!
Click to expand...
Click to collapse
Thanks for letting me know about the broken link, i have updated it.
I have everything working on Android 8.1 , not tried 9 yet. I will test camera quality tomorrow during day time. But camera does work.
Second link is the boot image.

GREAT!
Wanna go home quickly and play with my Z5!!!

Thank you for your work!!
Notification led work?
Did you tried Google Camera?

Also would you be so kind to explain how to flash another image? For example from AOSP 8.1 to 9.0?or viceversa. Thanks

nfraccar said:
Also would you be so kind to explain how to flash another image? For example from AOSP 8.1 to 9.0?or viceversa. Thanks
Click to expand...
Click to collapse
I have tried that multiple times for Android 9.0, wifi and data just doesnt work, may be we will have to wait for new firmware from Lenovo.

rendroid15 said:
I have tried that multiple times for Android 9.0, wifi and data just doesnt work, may be we will have to wait for new firmware from Lenovo.
Click to expand...
Click to collapse
Is it always possible to reflash stock ZUI?
How?
Thank you for Your kind support

nfraccar said:
Is it always possible to reflash stock ZUI?
How?
Thank you for Your kind support
Click to expand...
Click to collapse
Unless you mess with Vendor and stock firmware partitions, you can always go back to ZUI.
For flashing stock ZUI, please see below thread, it has all the information you need including downloads
https://forum.xda-developers.com/android/help/help-lenovo-z5-chinese-updates-t3812110

DarkerMaster said:
Thank you for your work!!
Notification led work?
Did you tried Google Camera?
Click to expand...
Click to collapse
Google Camera is crashing on start up. I have tried 6 different versions. No luck.
Push Notifications are working so it rings but the led is not blinking.

rendroid15 said:
Google Camera is crashing on start up. I have tried 6 different versions. No luck.
Push Notifications are working so it rings but the led is not blinking.
Click to expand...
Click to collapse
Of course you enabled camera 2 API right?

Yo rendroid, I managed to get my phone working again (first time in a week, woo hoo!)
Since flashing the system image didn't work with the adb, I put it in my phone's storage and flashed it with twrp.
(Btw, enabling the file extensions to be seen in file explorer didn't help with flashing the system image)
I was actually surprised it worked!
So my phone now has a working rom on it but I have a few problems:
-WiFi and Data not working. (The wifi toggle actually causes the phone to freeze. However, it breaks itself out and crashes the wifi toggle, leaving you to use the phone again)
-This is a minor issue but the notifications aren't cropped right (cut off and stuff)
This honestly has been a major breakthrough for me ( now that my phone isn't a paperweight anymore) and it's all thanks to you and the other devs for your hard work.
If you could help me with the wifi and data issue, that would the final piece to the puzzle and I could stop using my malfunctioning S4.

Cirus61 said:
Yo rendroid, I managed to get my phone working again (first time in a week, woo hoo!)
Since flashing the system image didn't work with the adb, I put it in my phone's storage and flashed it with twrp.
(Btw, enabling the file extensions to be seen in file explorer didn't help with flashing the system image)
I was actually surprised it worked!
So my phone now has a working rom on it but I have a few problems:
-WiFi and Data not working. (The wifi toggle actually causes the phone to freeze. However, it breaks itself out and crashes the wifi toggle, leaving you to use the phone again)
-This is a minor issue but the notifications aren't cropped right (cut off and stuff)
This honestly has been a major breakthrough for me ( now that my phone isn't a paperweight anymore) and it's all thanks to you and the other devs for your hard work.
If you could help me with the wifi and data issue, that would the final piece to the puzzle and I could stop using my malfunctioning S4.
Click to expand...
Click to collapse
nice !
now for the wifi and data
i need you to flash the same rom using fastboot not twrp
The File explorer setting was just to see if the file has any extensions. So if you dont see an extension then add .img in the end.
I think there is a bug in twrp that is causing wifi and data to not work.

I have tried flashing the 8.1 and it has given me error in all files by fastboot

rng30 said:
I have tried flashing the 8.1 and it has given me error in all files by fastboot
Click to expand...
Click to collapse
can you post the screenshots?
Its most likely you dont have adb installed,
You can get it from here https://forum.xda-developers.com/showthread.php?t=2317790

nfraccar said:
Of course you enabled camera 2 API right?
Click to expand...
Click to collapse
not yet, i am testing stock rom right now.

rendroid15 said:
not yet, i am testing stock rom right now.
Click to expand...
Click to collapse
Then Google Cam can't work. Activate camera 2 API if you have time and try again Google Cam!

rendroid15 said:
nice !
now for the wifi and data
i need you to flash the same rom using fastboot not twrp
The File explorer setting was just to see if the file has any extensions. So if you dont see an extension then add .img in the end.
I think there is a bug in twrp that is causing wifi and data to not work.
Click to expand...
Click to collapse
Well crap. Just when I thought everything was good. The file does the .img extension but for some reason adb just can't find it even though it's literally in the same folder. I'll try again and let you know.

Cirus61 said:
Well crap. Just when I thought everything was good. The file does the .img extension but for some reason adb just can't find it even though it's literally in the same folder. I'll try again and let you know.
Click to expand...
Click to collapse
try this, copy all files directly in adb folder, get rid of folder "Minimal adb drivers", the spaces in that folder name may be the problem.
If that doesnt work then just rename the rom name to rom.img and use that in fastboot command.