[X]Assistant

[AdViNTa]

ZTE Blade A510 - Firmware

Description | Discussion пїЅ | games and apps пїЅ | Accessories пїЅ | ZTE Blade A510 Owners Club пїЅ | Modification and decorations пїЅ | Firmware пїЅ

Important information!

Before performing any actions from this topic,be sure to backup NVRAM, so you do not have to suffer then with the restoration
Before asking a question, please read the cap andFAQ

Question Template

Question Creation Template

Please stick to this pattern.

[b] Audit of the device: [/ b]
[b] Firmware: [/ b]
[b] Instructions for which acted: [/ b]
[b] Description of the problem: [/ b]
[B] What did you do: [/ B]
[SPOILER = Screenshots] [/ SPOILER] (if present)

Example

Audit of the apparatus: 2
Firmware:RR 5.7.4
Instructions for which acted:(In this case there are none)
Description of the problem:The system does not start after the firmware. etc

Screenshots

(In this case, they are not)

Drivers and Utilities

• Drivers
  
• SP Flash Tool
  
• Adb run
  
• Mediatek backup device Android 6.0 Marshmallow

Official firmware

Survey post on available firmwarehere

Information on revisions and firmware on them

Russian firmware

• Stock_RU_B07_Deodex
  
• Blade_a510v.1.0.0B07 under FT
  
• Dump firmware B06
  
• RU B01
  
• RU_BLADE_A510V1.0.0B02For SP Flash Tool for TWRP
  
• RU_BLADE_A510V1.0.0B03For SP Flash Tool
  
• RU_BLADE_A510V1.0.0B04For SP Flash Tool For TWRP (with Root rights) - For Stock Recovery

Belarusian firmware

• BY_BLADE_A510V1.0.0B03 for SP Flash Tool
  
• BY_BLADE_A510V1.0.0B05 for SP Flash Tool Update from B03 for stock recovery without root
  
• Backup B07 for SP FlashTool

Unofficial firmware

X32 firmware

Android 6

• Cyanogen mod 13
  
• Zte V7
  
• ikitel
  
• Wiko U Feel
  
• XOS
  
• OUKITEL UI
  
• Resurrection Remix 5.7.4
  
• SlimRom6
  
• ZTE BLADE X3
  
• Micromax Q409
  
• MOS! Dea-v0.1
  
• Doogee X6S 6.0
  
• MIUI 8 v7.5.27 x32
  
• AOSP 6.0 for Flash Tool
  
• AOSP Android 6.0.1 kernel 3.18.19 h32
  
• EMUI 4.1 x32
  
• Lenovo Vibe UI x32
  
• TouchWiz Samsung x32
  
• Fira os
  
• Lineage 13 (Android 6.0.1 kernel 3.18.19 x32)

Android 7

• Slim 7.1.1
  
• MoKee 7.1.2
  
• AOKP 7.1.2
  
• XenonHD 7.1.2
  
• AospExtended-v4.6
  
• PornAOSP (Android 7.1.2 x32 3.18.19)
  
• ViperOS-Coral-v3.1.1 x32(From source)
  
• Lineage OS 14.1(From source)
  
• CrDroid 3.8.7 r37 Android 7.1.2(From source)
  
• Resurrection Remix 5.8.5 x32
  
• Resurrection Remix 5.8.3 for Flash Tool
  
• Resurrection Remix 5.8.3 Kernel 3.18.19 x32 (Android 7.1.2)
  
• Resurrection Remix 5.8.0 x32
  
• Resurrection Remix 5.8.2 x32
  
• Resurrection Remix 5.8.5 x32(From source)
  
• DND DarkNess reDefined V2 x32 Android 7.1.2 kernel 3.18.19
  
• XenonHD
  
• XOSP
  
• Lineage 14.1 for TWRP | Lineage 14.1 for SP flash Tool
  
• Mokee 7.1.1 | MoKee 7.1.1 x32 adapted under the Flash Tool

X64 firmware

Android 6

• Flyme 6 x64 3.18.19
  
• Resurrection Remix 5.7.4 (2.0) | x64
  
• MIUI 9 Global 7.9.15 kernel 3.18.19
  
• MIUI 8 x64fromDobrozhevatel

Android 7

• dotOS (Android 7.1.2)
  
• AOSP Extended v4.5 x64

DotOS port on kernel 3.18.35

Instructions

• New way to repair IMEI
  
• Another way to restore imei
  
• System customization
  
• How to increase device performance?
  
• Instructions for installing custom recovery TWRP and getting root rights
  
• Instructions for restoring the phone after unsuccessful flashing to the factory state
  
• Firmware with SP FlashTool,BACKUP NVRAM, decoupling from the operator, installing TWRP(detailed with pictures)
  
• Firmware official updates via TWRP
  
• Installing Recovery and getting root rights
  
• Instructions for the recovery of flew IMEI-codes
  
• Instructions - firmware, decoupling from the operator, custom recovery, root, restore Imei
  
• NVRAM recovery: IMEI, mac-WiFi, mac-Bluetooth and serial. (If there is no backup)
  
• For those who have a 4032 error after flashing

Recovery

• TWRP 3.1.0
  
• TWRP 3.0.3 for ZTE Blade A510 (jemmini)
  
• TWRP 3.0.2 x64forBYB03,RuB01
  
• TWRP 3.0.2 x32forBYB05, B07, B08RuB02, B03, B04
  
• TWRP flies after reboot

miscellanea

• Ported Applications
  
• A510 NVRAM
  
• Engineering menu mod
  
• Performance. Energy saving. Optimization.
  
• Files to restore imei using Maui META 3G
  
• Dual boot patcher - Partial solution to the problem with DualBootPatcher
  
• Power fix patch
  
• Backup Nvram / Nvdata
  
• Remapping memory. Increase the userdata section by reducing other sections
  
• Solving the problem of not turning on the screen after flashing the phone
  
• Patch switching mode 3G / LTE between SIM-cards
  
• Patch work of gestures on the off screen for B05
  
• Patch bypass google for twrp
  
• Fix NVRAM error, Warning err = 0x10 for TWRP
  
• No image after firmware
  
• How to remove the onscreen buttons
  
• Headphone Volume Solution
  
• How to bypass Google account
  
• Another way to decouple Google account
  
• Transferring files (games & applications) to sdcard
  
• Unpacked system.img image from ZTE A510 B03 64bit firmware
  
• Modems and Unbind from the operator for TWRP
  
• Device info- device info
  
• Face recognition

There is no curator in the subject. For questions about filling the caps, please contact the section moderators using the "Complaint" button.

Post has been editeddestroyer71 - 19.04.19, 14:49

Reason for editing: A510 NVRAM

[ar2b]

AdViNTado a good deed
I restored it through Maui meta, everything rises, you need to remove the error x10 nrav Wi-Fi

[AdViNTa]

ar2b,and thisZTE Blade A510 - Discussion (Post ar2b # 51513483)Does not help?

[ar2b]

AdViNTa, I also requested yours to switch, and for the sims and the console I looked there in both there are not enough commands to mount the unmount of the system partition. It must be manually. Tomorrow again I ask. I want to sleep head does not cook ...

[Artyom545]

And how to root the zte blade a510, and not so to install the firmware + root?

[Ki6erPanK]

ar2b, Download sp meta, firewood, and find the apdb file and you will be happy. For instructions on how to do this, look in the Beeline smart 4 topic.

Posted 08/20/2016 05:24:

ar2b, APDB file, so as not to search

Attached files

APDB_MT6735_S01_L1.MP3_W15.zip(24.87 KB)

[ar2b]

Artyom545, you just need to install custom recovery and flash root

Posted 08/20/2016 08:29:

Ki6erPanK, you did not understand, in zip archives there is a sh installation script in which there are not enough lines to mount the system partition.

You will manually fix it and everything will be sewn

[AdViNTa]

ar2b, everything is fine with mounting. At least in the script for Sims. And in your mount system and do not need. There in the data file is copied.

[ar2b]

AdViNTathat something does not go on my b05

[AdViNTa]

ar2b,what is not going? How determined that does not go? What are you doing? Details are needed if you want help.
I personally checked in before writing here.

[Ki6erPanK]

ar2b, if you're talking about a fixed connection, then I, too, have all the rules

[ar2b]

Ki6erPanKFix fix and does not work.
I'll try with my hands

Posted 08/20/2016 5:38 PM:

AdViNTa,

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id = MRA58K
ro.build.display.id = EU_BLADE_A510V1.0.0B01
ro.build.version.incremental = 20160618.161555
ro.custom.build.version = EU_P635A50V1.0.0B01
ro.build.sw_internal_version = EU_P635A50V1.0.0B01
ro.build.version.sdk = 23
ro.build.version.preview_sdk = 0
ro.build.version.codename = REL
ro.build.version.all_codenames = REL
ro.build.version.release = 6.0
ro.build.version.security_patch = 2016-06-01
ro.build.version.base_os =
ro.build.hardware = u66A
ro.build.date = Sat Jun 18 16:18:19 CST 2016
ro.build.date.utc = 1466237899
ro.build.type = user
ro.build.user = daihaigang
ro.build.host = SCL-8SH25
ro.build.tags = release-keys
ro.build.flavor = full_ztesh6735m_35u_m-user
ro.product.model = ZTE BLADE A510
ro.product.model_zte =
ro.product.brand = ZTE
ro.product.name = P635A50_BAIE_LIFE
ro.product.device = P635A50
ro.product.board = MT6735P
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi = armeabi-v7a
ro.product.cpu.abi2 = armeabi
ro.product.cpu.abilist = armeabi-v7a, armeabi
ro.product.cpu.abilist32 = armeabi-v7a, armeabi
ro.product.cpu.abilist64 =
ro.product.manufacturer = ZTE
ro.product.locale = en-US
ro.wifi.channels =
ro.board.platform = mt6735m
# ro.build.product is obsolete; use ro.product.device
ro.build.product = ztesh6735m_35u_m
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description = full_ztesh6735m_35u_m-user 6.0 MRA58K 20160618.161555 release-keys
ro.build.fingerprint = ZTE / P635A50_BAIE_LIFE / P635A50: 6.0 / MRA58K / 20160618.161555: user / release-keys
ro.build.characteristics = default
ro.build.sar_vrsion =
# end build properties
#
# from device / ztesh / ztesh6735m_35u_m / system.prop
#
#
# system.prop for generic sdk
#

rild.libpath = mtk-ril.so
rild.libargs = -d / dev / ttyC0


# MTK, Infinity, 20090720 {
wifi.interface = wlan0
# MTK, Infinity, 20090720}

# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc = 1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p = 1
# MTK, mtk03034 20110318}

# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia = 0
# MTK, mtk03034 20101213}


#
wifi.tethering.interface = ap0
#

ro.opengles.version = 196608
# ro.kernel.qemu = 1
# ro.kernel.qemu.gles = 0

wifi.direct.interface = p2p0
dalvik.vm.heapgrowthlimit = 128m
dalvik.vm.heapsize = 256m

# USB MTP WHQL
ro.sys.usb.mtp.whql.enable = 0

# Power off opt in IPO
sys.ipo.pwrdncap = 2

ro.sys.usb.storage.type = mtp, mass_storage

# USB BICR function
ro.sys.usb.bicr = yes

# USB Charge only function
ro.sys.usb.charging.only = yes

# audio
ro.camera.sound.forced = 0
ro.audio.silent = 0

ro.zygote.preload.enable = 0
persist.sys.timezone = Europe / London

# temporary enables NAV bar (soft keys)
# qemu.hw.mainkeys = 0
# modify by zter daijinguo 10175444
# disable the NAV bar
qemu.hw.mainkeys = 1

ro.kernel.zio = 38,108,105,16
# ro.kernel.qemu = 1
# ro.kernel.qemu.gles = 0
# ro.boot.selinux = disable

ro.sf.lcd_density = 320

# performance
ro.mtk_perf_simple_start_win = 1
ro.mtk_perf_fast_start_win = 1
ro.mtk_perf_response_time = 1

# 0x001 {***** added for gesture *****
ro.sys.zteg_path = / sys / bus / i2c / devices / 1-0038
ro.sys.zteg_file = tpd_wake_gesture
0x001} ******************************

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone = The_party.ogg
ro.config.notification_sound = Glow.ogg
drm.forwardlock.only = true
ro.carrier = unknown
ro.config.alarm_alert = Dawn_of_the_jungle.ogg
dalvik.vm.heapgrowthlimit = 128m
dalvik.vm.heapsize = 256m
ro.mediatek.chip_ver = S01
ro.mediatek.version.release = EU_BLADE_A510V1.0.0B01
ro.mediatek.platform = MT6735
ro.telephony.sim.count = 2
persist.radio.default.sim = 0
persist.radio.multisim.config = dsds
persist.gemini.sim_num = 2
ro.gemini.smart_sim_switch = false
ril.specific.sm_cause = 0
bgw.current3gband = 0
ril.external.md = 0
ro.sf.hwrotation = 0
curlockscreen = 0
ro.mediatek.gemini_support = true
drm.service.enabled = true
fmradio.driver.enable = 1
ril.first.md = 1
ril.flightmode.poweroffMD = 1
ril.telephony.mode = 0
dalvik.vm.mtk-stack-trace-file = / data / anr / mtk_traces.txt
mediatek.wlan.chip = CONSYS_MT6735
mediatek.wlan.module.postfix = _consys_mt6735
ril.read.imsi = 1
ril.radiooff.poweroffMD = 0
ro.frp.pst = / dev / block / platform / mtk-msdc.0 / 11230000.msdc0 / by-name / frp
ro.sys.usb.storage.type = mtp, mass_storage
ro.mediatek.version.branch = alps-mp-m0.mp1
ro.mediatek.version.sdk = 4
ro.setupwizard.mode = OPTIONAL
ro.com.google.gmsversion = 6.0_r2
ro.com.google.clientidbase = android-zte
ro.com.google.clientidbase.ms = android-zte
ro.com.google.clientidbase.yt = android-zte
ro.com.google.clientidbase.am = android-zte
ro.com.google.clientidbase.gmm = android-zte
ro.mtk_gemini_support = 1
persist.radio.gemini_support = 1
ril.current.share_modem = 2
ro.mtk_audio_profiles = 1
ro.mtk_audenh_support = 1
ro.mtk_besloudness_support = 1
ro.mtk_bessurround_support = 1
ro.mtk_bt_support = 1
ro.mtk_wappush_support = 1
ro.mtk_agps_app = 1
ro.mtk_voice_unlock_support = 1
ro.mtk_voice_contact_support = 1
ro.mtk_audio_tuning_tool_ver = V1
ro.mtk_wlan_support = 1
ro.mtk_gps_support = 1
ro.mtk_omacp_support = 1
ro.mtk_search_db_support = 1
ro.mtk_dialer_search_support = 1
ro.mtk_dhcpv6c_wifi = 1
ro.have_aacencode_feature = 1
ro.mtk_oma_drm_support = 1
ro.mtk_cta_drm_support = 1
ro.mtk_widevine_drm_l3_support = 1
ro.mtk_eap_sim_aka = 1
ro.mtk_fm_recording_support = 1
ro.mtk_audio_ape_support = 1
ro.mtk_flv_playback_support = 1
ro.mtk_send_rr_support = 1
ro.mtk_emmc_support = 1
ro.mtk_tetheringipv6_support = 1
ro.mtk_shared_sdcard = 1
ro.mtk_enable_md1 = 1
ro.mtk_flight_mode_power_off_md = 1
ro.mtk_pq_support = 2
ro.mtk_miravision_support = 1
ro.mtk_miravision_image_dc = 1
ro.mtk_wifi_mcc_support = 1
ro.mtk_sim_hot_swap = 1
ro.mtk_thumbnail_play_support = 1
ro.mtk_bip_scws = 1
ro.mtk_world_phone_policy = 0
ro.mtk_perfservice_support = 1
ro.mtk_cta_set = 1
ro.mtk_mobile_management = 1
ro.mtk_antibricking_level = 2
ro.mtk_cam_mfb_support = 0
ro.mtk_lte_support = 1
ro.mtk_rild_read_imsi = 1
ro.sim_refresh_reset_by_modem = 1
ro.mtk_passpoint_r1_support = 1
ro.mtk_bg_power_saving_support = 1
ro.mtk_bg_power_saving_ui = 1
ro.have_aee_feature = 1
ro.sim_me_lock_mode = 0
ro.mtk_dual_mic_support = 1
ro.mtk_is_tablet = 0
ro.mtk_ims_support = 1
ro.mtk_volte_support = 1
persist.mtk.volte.enable = 1
persist.dbg.volte_avail_ovr = 1
ro.mtk_voice_extension_support = 1
wfd.dummy.enable = 1
ro.mediatek.project.path = device / ztesh / ztesh6735m_35u_m
persist.mtk.wcn.combo.chipid = -1
service.wcn.driver.ready = no
service.wcn.coredump.mode = 2
ro.com.android.mobiledata = false
persist.radio.mobile.data = 0.0
persist.meta.dumpdata = 0
ro.mtk_md_sbp_custom_value = 125
ro.mtk_default_ime = com.android.inputmethod.latin.LatinIME
persist.sys.dalvik.vm.lib.2 = libart
dalvik.vm.isa.arm.variant = cortex-a53
dalvik.vm.isa.arm.features = default
net.bt.name = Android
dalvik.vm.stack-trace-file = / data / anr / traces.txt
ro.expect.recovery_id = 0x4ec32e972b971e504dda06b76abd1d220beb07930000000000000000000000

Post has been editedvelikashkin - 20.08.16, 18:18

Reason for editing: under spoiler

[AdViNTa]

ar2b, if this is your build.prop after the patch, then everything is ok. What is the problem?
remove the sheet or hide under the spoiler

[kardens]

[email protected], 20:40

* Kardens, let's start with what are you going to do?

Fu, damn ... sorry ... completely messed up with this phone .. I can not get rid of the binding to Google after reset
How to overcome taking into account the fact that the company is not at hand and I cannot format the frp section?

Post has been editedkardens - 20.08.16, 21:15

[ar2b]

kardens, log in to google account.

[alf-aleksey]

Kardens @ 08/20/2016, 9:13 PM

...
How to overcome taking into account the fact that the company is not at hand and I cannot format the frp section?

Enter the factory recovery (co-combination of the volume button + and the button on) and do wipe data / factory reset. The phone will reset to factory settings.

Post has been editedalf-aleksey - 20.08.16, 21:33

[kardens]

Alf-aleksey @ 08/08/2016, 9:32 PM

Enter the factory recovery (co-combination of the volume button + and the button on) and do wipe data / factory reset. The phone will reset to factory settings.

those. Do you think that I, knowing how to format a frp partition (just can’t do it), can't push two buttons? ok, let's start over and with correcting your own feed:

The phone after the reset asks for the data of the Google account, which was originally registered. I tried all the methods available to me (I am lying in a military hospital, there is no computer at hand). I got to the settings via * # * # 4636 # * # * but there is no more deadlock: the accounts are empty, the reset via backup / restore does not give anything. I feel "the truth is somewhere near," but I can’t grab it ... What should I do?

Thank.

[ar2b]

kardens, remember your mail or make a format through a computer. No more solutions. Point

[Lex2512]

Hello everyone, I need help, when decoupling from an Google account, emei wrote null, I could not find where to drive the numbers through the instructions in the engineering menu.
And for the rest of the programs, you need 2 modem files and an APBD for the zte blade a 510 not find where I cannot, can anyone have a skinte pliz.

Custom recovery does not start, how many did not try to get a root (

[ar2b]

Lex2512, maui meta latest version will help you

[Lex2512]

and modem files and other files are not needed there, or in a bit more detail (