ZTE Blade A813 - Firmware



Rep: (470)
ZTE Blade A813 - Firmware
PictureZTE_T617, P829A10.
Description | Discussion пїЅ | Firmware пїЅ

Important information
Dear forum users!

When creating messages on your existing problems, please specify the following information:

Full title installed and installed firmware.
Whether applied: Wipe / Clear Data / Clearing Data. If it was used, then how completely: formatted or no internal memory. Those. You can briefly write: I flashed with Wipe, but without memory format.
Availability / absence ROOT rights both on the existing firmware and last.
What was installed On the firmware, which applications or changes were integrated into the firmware (both in the new and in the previous one)
What's happening (What an error or what does not work).

This information will give the most complete picture of your problem, and perhaps thanks to this form of inquiry, you will be promptly helped to solve your problem.

Drivers and Utilities

Firmware

Recovery and Kernels

Instructions

miscellanea

Screenshots + review

There is no curator in the subject. For filling caps, please contactmoderatorssection through a buttonPictureunder the messages to which you want to add links.

Post has been editedAkella_MC - 26.11.17, 21:29
Reason for editing: Several firmware based on CM 12.1.



Rep: (12)
Bacup NV, EFS parameters on ZTE Blade A813 smartphones.

IMPORTANT!!!! Never upload NV parameters backups to the network !!!! In the case of restoring a full copy of your device to another, and you and the recovered may have huge problems. Everything that you do, you do at your own peril and risk, at your own responsibility. This is a description of recovery methods for personal use.


"Introduction"
. I hasten to inform you that you are prepared for the backup optionNV, EFS The parameters of our devices. Having such a backup, we can not be afraid of the loss of 3G / 4G communication, (parameters Esn or MEID) Voice loss (IMEI) and other thousand parameters will not be lost, which necessarily happens after the restoration of the brick apparatus (how to restore from the hardbroke, while there is no method, but I work on it.). Sections EFS, NV, Persist When restoring bricks, shaped virtually, that is, empty, but with the possibility of recording the main parameters there. After recording, the sections become read-only, be careful. Bacups are also needed with the problems acquired with the network, Wi-Fi, etc. That's what you need backups. They will not save your media files, or the contents of SD-cards, will not save the installed programs, but will save something, without which the device cannot call, nor enter the Internet will not be able to. That is, save all the factory settings and the parameters of your device to work with data networks.


"Removing parameters in a QCN file. This option is suitable for all NUBIA devices and very many ZTE devices (on Qualcomm). And not only ZTE, but with reservations."
Of course, many have heard, and faced with such a program asQPST . Released her company Qualcomm, and she came up with the standard record NV, EFS parameters into one small hex file QCN .
This standard is used by all of us respected program.Nubia tools . Many tried to backup NV With its help, but nothing turned out. By default, our devices are closed by a diagnostic port, with which programming and reading occurs. NV parameters. The port opens only after recovery from heavy brick. And the backup needs to be done on a working body. Without configuring the diagnostic port, the backup cannot be made. What to do?
I still found on our great joy, how the diagnostic port is turned on on a standard working body !!!!!!!!. Under the standard working body, I understand the body with stock firmware. You can try on other firmware, but the stock will exactly succeed.

Prerequisites for to start making backupHB Parameters B. QCN file:

1. The Root rights.
2. Included debugging via USB.
3. Download and unzip utilityAdb. For ease of description I unpack it into the folder C: \ ADB
4. Download and installed programNubia tools.
5. Installed driver for the smartphone. lieHERE

Let's turn on the port.

Run the command prompt (Start, and in the search bar, enter CMD)
In the command line, change the current way, on the way where the brokenAdb . For example, if the utility is unpacked in Paka C: \ ADB, we write on the command line:

cd C: \ adb


And press Enter.
After this string on the command line will look like this:

Attached Image


Next, write the command line
adb devices


the answer should look like this******** device , And it is said that the ADB is working properly.
Attached Image


If the answer is kind******* unautorized or ******** offline , It means you have not verified the key fingerprint on a smartphone, while turning debugging. Perevotknite phone cord and confirm the debug screen (tick and Oak).
Debug can be included so. When connected to select itemPC sync , remove the cable and insert again, window appears Enable USB debugging And at the bottom put a tick Remember choosing .

Further, the write command line as shown in the screenshot below, after each of the two rows of press Enter.
adb shell
su

Attached Image


As a result, the cursor invitation should begin with the wordroot Now the fun part. At the command prompt, write
setprop persist.sys.usb.config diag, adb


and hear how the computer finds a new unit. This is our diagnostic port. In the Device Manager can observe it
Attached Image
Attached Image


In the device manager, the Ports section appears
ZTE Handset Diagnostic Interface port.

Go inPropertiesthis port and tabOptionsPort at the top value set 115,200 bits per second.

RunNubia tools ,

ChooseTools / Settings.
The top line put 115200
Four lower values ​​- 0


double click on the sectionBackup .
Click settings and set up inserting
- in the top line the value is 115200
- SPC manual (000000)
Exit the settings.


We pressRefresh - there is a port. ( START until we press)
Choosing a place where the archive will be savedQCN and click Start All on the panel.

After a small amount of time you have readyQCN backup.)))

Recover through it by selecting the tabRestore

NubiaTools downloadHERE
Firewood at the portHERE
AdbHERE

Diagnostic port back can not be closed, but if there was an irresistible urge, then:
adb shell
su
setprop persist.sys.usb.config none


by analogy with the above described.

As a result, we get a small file of a few tens of kilobytes, and 1 filenv.qcn inside. Dostavt it from the archive is not necessary.

You can backup and make the programQPST Software Download , but this is another song, and it is better for non-engineers not to enter there (Cherevato for many, therefore I do not describe it). Who knows how to work for her, you can backup her port allows.



IMPORTANT!!!!!Never post a QCN file in sharing. !!! It is strictly forbidden to produce the same settings !!!!!!


Tested on your device, everything works.



Turn on the menu item"For the developer" , Come in "Settings" , "About phone" and tapam 6 times on the item "Build Number" Voila appeared menu item "For the developer"



All the information found in the branchZTE Blade S6


Post has been editedsergej4388 - 19.08.16, 14:38
Reason for editing: In the header



Rep: (12)
TWRP recovery 3.0

Be sure to make backup recovery before all manipulations !!!!!! Responsibility for the collision of the phone (s) I do not carry everything on your own and risk !!!



Necessary software.

1-setKingROOT , get RUTH the rights.
2-then putRashr
3-download to the phone.Attached filerecovery.img(22.3 MB)

Instruction
Go inRashr - backup - Press " + "At the bottom for backup recovery and kernel.
Next, clickFirmware - Recovery from the catalog And choose our recovery.img which downloaded, we flash and load in the recovery by choosing Recovery mode.



TWRP port made on the basis of custom recovery fromLenovo K3 Music Lemon - Firmware

Post has been editeddjonkor - 14.10.16, 23:51
Reason for editing: In the header



Rep: (470)
Instructions for the ZTE Blade A813 firmware, using Custom Recovery TWRP


Remember that no one is responsible for your actions besides you.
The phone must be maximally charged and in no case can you remove the memory card in the firmware process!
Before all manipulations with the device doBackpack NV, EFS parameters.
After a successful end, we save and store this file as an eye zenitsa.

Read carefully! Each item, post, sequence and all instructions.


Detailed actions for those who flashFOR THE FIRST TIME!

1. We getKingrootand replace kinguser onSuper-Sume + Pro
2. InstallationTWRP Recovery through the application Rashr

3. Go to TWRP (on the phone off the phone, climb the volume swing + and the power button and wait for the appearance of the TWRP logo on the phone screen, release. The main menu TWRP will be loaded)
4. Most importantly, make a backup of your system through TWRP! Remember, sometimes this backup can save "life" to your phone!
Instructions for creating a backup.
Choose Russian (who wants what)
To do this, click on SELECT LANGUAGE, we will find a list of languages. Choose the Russian language by click OK!
Then put a tick on (no longer show it when loading)
Move the "swipe" below "Allow Changes"
Screenshot
Attached Image
Attached Image
Attached Image
Attached Image


- in TWRP click on the button "Backup "
- We are looking for an oblong frame in the middle of the screen with the inscription - "Choice of the drive", click on it and choose your Micro SDCard (you can understand by the number of MB)
- Choose all ticks
- Moving the "swipe" below and starts to create a backup
- wait for the end, at the top there is an inscription - "Backup completed successfully "And the" Restart in OS "button appears, click on it.
Screenshot
Attached Image
Attached Image
Attached Image

5. Download the firmware hereAP_P829A10V1.0.0B10.And put it in the root of the memory card. (Remember that for some firmware there are individual aspects that are not described in the instructions, but each firmware is a description or information on the individual installation on the forum)
6. Again go to TWRP.
7. Press "Cleaning", press the "Selective Cleaning" button and select Dalvik Cache, System, Data and Cache items. We carry out the "swipe" and the cleaning process will begin.
Note: The SYSTEM item removes the firmware from the phone, so if after this cleaning, you will change your mind or you will not work, you will not be able to boot into Android. Therefore, this item is recommended to apply with caution or when it is required due to the features of the firmware, or fashion
8. We return to the main menu TWRP and select "Installation", looking for the firmware you need and click on it, the firmware process will go. (If you do not see your firmware, we are looking for an oblong frame at the top of the screen with the inscription - "Select the drive", click on it and choose your flash card (you can understand by the number of MB))
9. After the firmware is completed, make Cache / Dalvick Cache cleaning by pressing the appropriate.
10. Final! Click on the "Restart in OS" button
Screenshot
Attached Image
Attached Image


If you correctly completed all actions, the phone will reboot and starts up your new firmware. At the end of the download, the phone will need to re-configure itself as a new one, or perform recovery (recovery) from the previously prepared !!!
Files


Post has been editedSattarvoybek - 13.10.16, 02:02



Rep: (47)
By diligenceSattarvoybek , we have the first firmware in our topic. Updated factory sewing V6.0. A few hours later, the flight is normal, failures and errors were not observed. The firmware is improved, the GPS icon in the status bar now disappears when it is turned off. Most likely a lot of small modifications. Who will use, unsubscribe. The approximation sensor was not particularly checked, although I did not have any problems with it on the past run. At first glance, the work of the smartphone improved. We will use further and unsubscribe about errors or good impressions.
Screenshots
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image


Post has been editedbelozzini - 27.09.16, 04:20



Rep: (2)
Error, + on the password archive



Rep: (2)
1
Attached Image


Post has been editedMagnat.mg - 28.09.16, 18:49
Reason for editing: Violation of the rules of section 3..8.



Rep: (470)
* gora2000,
Can you remove the log in the recovery?



Rep: (0)
Similar error. try to recover from backup



Rep: (38)
* Sattarvoybek,
What password on the archive with the firmware?



Rep: (470)
* Alien.McKenn,
Here isthistry



Rep: (47)
SattarvoyBek @ 09/27/2016, 21:59*
Try it
It seals from recovery 3.0.2.R4 with wipes
With the help of the same recovery restored backup. Fully works.

Post has been editedbelozzini - 27.09.16, 19:27



Rep: (0)
Established from the second link. The sensor also works illogical. During the call, SMS comes and the screen is activated, the ear presses anything.

Post has been editedOlegm9. - 27.09.16, 21:41



Rep: (55)
And what, just from the flash drive not updating? Necessarily via TVP and rut?



Rep: (0)
Works at first glance faster, but this may be due to the fact that it insisted from the zero and the software did not load a lot there as the previous firmware. Yes, and the Loncher did not change while the stock left the stock.



Rep: (0)
* Olegm9
Firmware did not give results?



Rep: (0)
As for the approximation sensor, nothing has changed. The screen is activated during a conversation from the coming SMS and the second incoming call. Everything remains and left.



Rep: (4)
Olegm9 @ 09/28/2016, 17:23*
As for the approximation sensor, nothing has changed. The screen is activated during a conversation from the coming SMS and the second incoming call. Everything remains and left.

Tried to put a softening from myfasting?
I am still satisfied ...

Post has been editedM-i-x - 29.09.16, 21:01



Rep: (0)
Softinka helped.



Rep: (0)
M-I-X @ 09/29/2016, 21:01*
...
Tried to put a softening from myfasting?
I am still satisfied ...

Softinka does not help. If you speak and comes a second call, the phone lights the screen with all the subsequent "ear" presses.



Rep: (4)
Softinka does not help. If you speak and comes a second call, the phone lights the screen with all the subsequent "ear" presses.

Well, if only with the second call, then not such a big trouble. It is necessary to see who is calling that ..))


Full version    

Help     rules

Now: 03.02.21, 19:02