Quote:
Originally Posted by JayDi
As can see, software got loader already from somewhere.
Make sure about you had try generic SC7731x , not E.
Yes the software got the loader from a similar model that its able to do almost everything.
I have a lot of model STYLO K7 tab and most of them the software is able to service them but fails on some regardless using the same settings on software.
look at the log below for the some that its able to do
Operation : Identify [ v2.04 ]
BootMode : FLASH
1. Power off device, wait 10-15 seconds
2. Press and hold BooKey ( 1 : BOTH VOL , 2 : VOL+ , 3 : VOL- )
3. Insert cable in device!
Wait for device …
Device Connected!
BootVersion : SPRD3
Boot : INF : 0_SC7731x_BASE : SC7731GEA_eMMC_1GB_NS
Sending Init Boot …
Boot sent!
Kick FDL …
BootVersion : Spreadtrum Boot Block version 1.1
Protocol setup …
Port speed : 921600
Sending Flash Boot …
Boot sent!
Kick FLASH FDL …
ProtoEx : : TRCC not supported!
FDL : Control transfered!
Boot Done!
Device info :
Patch Level : MRA58K
Display ID : Stylo-K7_v04_20180404
Ver. Incmt : eng.wsq.20180404.162258
Ver. CodeName : REL
Ver. Release : 6.0
Sec. Patch : 2017-04-05
Build Time : 1522830240
Product Model : Stylo K7
Product Brand : Stylo
Product Name : si7537sc
Product Device : sp7731g_1h10
Product Board : sp7731gea_hdr
Product Manfct : Stylo
Board Platform : sc8830
Product Info : sp7731g_1h10
Platform Version: MOCORTM_14B_MP_7731G_W16.28.2_Debug
Project Version: sc7731g_CP0_modem
BASE Version: TM_BASE_W16.28.2
MMI Version: sc7731g_modem
HW Version: sc7731g_CP0_modem
CMP_Time : 07-04-2016 12:49:15
MODEM TAG : MOCORTM_14B_MP_7731G_W16.28.2_Debug_TM_BASE_W16.28 .2_sc7731g_CP0_modem_sc7731g_CP0_modem_sc7731g_mod em
UserData : STATE : PLAIN
Done!
And the other this is how shows-
2. Press and hold BooKey ( 1 : BOTH VOL , 2 : VOL+ , 3 : VOL- )
3. Insert cable in device!
Wait for device …
Device Connected!
BootVersion : SPRD3
Boot : INF : 0_SC7731x_BASE : SC7731GEA_eMMC_1GB_NS
Sending Init Boot …
Boot sent!
Kick FDL …
ERROR : FDL NOT started!
Error : Fail to boot FDL!
Unsupported device with selected fdl! Change settings!
Reconnect Power/Cable!
Please help
Operation : Identify [ v2.07 ]
BootMode : FLASH
1. Power off device, wait 10-15 seconds
2. Press and hold BooKey ( 1 : BOTH VOL , 2 : VOL+ , 3 : VOL- )
3. Insert cable in device!
Wait for device …
Device Connected!
BootVersion : SPRD3
Boot : PAC : GEN_RU_P963F01V1.0.0B13_DL.pac
Sending Init Boot …
Boot sent!
Kick FDL …
BootVersion : Spreadtrum Boot Block version 1.1
Protocol setup …
Port speed : 921600
Sending Flash Boot …
Boot sent!
Kick FLASH FDL …
FDL : 0x0004
FDL : EMMC_RO : False ; EMMC_PART : True ; EMMC_RPMB_SET : True
FDL : Control transfered!
Boot Done!
Device info :
Patch Level : PPR1.180610.011
Display ID : GEN_RU_V10_VITA_V1.4
Ver. Incmt : 20200306.082522
Ver. CodeName : REL
Ver. Release : 9
Sec. Patch : 2020-02-05
Build Time : 06.03.2020
Product Model : ZTE Blade V10 Vita RU
Product Brand : ZTE
Product Name : GEN_RU_P963F01
Product Device : P963F01
Product Manfct : ZTE
Product Info : P963F01
Product Name : s9863a1h10_Natv
Product Device : s9863a1h10
Product Board : sprout
Board Platform : sp9863a
Содержание
- ZTE V10 vita не прошивается, нужен правильный FDL.
- MARADER
- maxim’ka
- Error fail to boot fdl
- Error fail to boot fdl
- Infinity A035f samsung
- merdjiosse
- Infinity-Box
- merdjiosse
- ZTE Blade A5 2019 проблема с коннектом
- flashmax
- Вложения
- TELEDOKtor
- Вложения
- uploads
- Ces69
- flashmax
- Ces69
- Вложения
- flashmax
- Ces69
- uploads
- flashmax
- uploads
- sinko
- Stick2
ZTE V10 vita не прошивается, нужен правильный FDL.
MARADER
Может у кого есть??
Infinity-Box Chinese Miracle II : SPD/USC Module [SP2] v2.09
Load IDBase v8331 Ok!
Operation : Identify [ v2.09 ]
BootMode : FLASH
1. Power off device, wait 10-15 seconds
2. Press and hold BooKey ( 1 : BOTH VOL , 2 : VOL+ , 3 : VOL- )
3. Insert cable in device!
Wait for device .
Device Connected!
BootVersion : SPRD3
Boot : INF : 0_SC9863x_BASE : SC9863A_eMMC_3GB_0S
Sending Init Boot .
Boot sent!
Kick FDL .
>>> ERROR : FDL NOT started!
>>> Error : Fail to boot FDL!
>>> Unsupported device with selected fdl or settings! Change settings!
maxim’ka
Operation : Identify [ v2.07 ]
BootMode : FLASH
1. Power off device, wait 10-15 seconds
2. Press and hold BooKey ( 1 : BOTH VOL , 2 : VOL+ , 3 : VOL- )
3. Insert cable in device!
Wait for device .
Device Connected!
BootVersion : SPRD3
Boot : PAC : GEN_RU_P963F01V1.0.0B13_DL.pac
Sending Init Boot .
Boot sent!
Kick FDL .
BootVersion : Spreadtrum Boot Block version 1.1
Protocol setup .
Port speed : 921600
Sending Flash Boot .
Boot sent!
Kick FLASH FDL .
FDL : 0x0004
FDL : EMMC_RO : False ; EMMC_PART : True ; EMMC_RPMB_SET : True
FDL : Control transfered!
Device info :
Patch Level : PPR1.180610.011
Display ID : GEN_RU_V10_VITA_V1.4
Ver. Incmt : 20200306.082522
Ver. CodeName : REL
Ver. Release : 9
Sec. Patch : 2020-02-05
Build Time : 06.03.2020
Product Model : ZTE Blade V10 Vita RU
Product Brand : ZTE
Product Name : GEN_RU_P963F01
Product Device : P963F01
Product Manfct : ZTE
Product Info : P963F01
Product Name : s9863a1h10_Natv
Product Device : s9863a1h10
Product Board : sprout
Board Platform : sp9863a
Источник
Error fail to boot fdl
You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.
Registration is fast, simple and absolutely free so please — Click to REGISTER!
If you have any problems with the registration process or your account login, please contact contact us .
1. Power off device, wait 10-15 seconds
2. Press and hold BooKey ( 1 : BOTH VOL , 2 : VOL+ , 3 : VOL- )
3. Insert cable in device!
Wait for device .
Device Connected!
BootVersion : SPRD3
Boot : INF : 0_SC9863x_BASE : SC9863_eMMC_3GB_RS
Sending Init Boot .
Boot sent!
Kick FDL .
ERROR : FDL NOT started!
Error : Fail to boot FDL!
Unsupported device with selected fdl! Change settings!
Источник
Error fail to boot fdl
Load IDBase v10107 Ok!
Operation : Identify [ v2.03 ]
BootMode : FLASH
1. Power off device, wait 10-15 seconds
2. Press and hold BooKey ( 1 : BOTH VOL , 2 : VOL+ , 3 : VOL- )
3. Insert cable in device!
Wait for device .
Device Connected!
BootVersion : SPRD3
Boot : INF : 0_SC7731E_BASE : SC7731E_eMMC_1GB_RS
Sending Init Boot .
Boot sent!
Kick FDL .
ERROR : FDL NOT started!
Error : Fail to boot FDL!
Unsupported device with selected fdl! Change settings!
Open : SPD_PROG.xml
Reading package .
Read package finished!
Created by Infinity-Box (c) 2020
Chinese Miracle II : Spreadtrum / UniSoc Service Module
Device Info file : _Android_info.txt
Patch Level : OPM2.171019.012
Display ID : GFIVE_GPAD702_20190105
Ver. Incmt : 51111
Ver. CodeName : REL
Ver. Release : 8.1.0
Sec. Patch : 2018-11-05
Build Time : 1546692842
Product Model : GPAD702
Product Brand : GFIVE
Product Name : GPAD702
Product Device : GPAD702
Product Manfct : GFIVE
Product Info : sp7731e_1h10
Product Board : GPAD702
Board Platform : sp7731e
Operation : Flash Firmware [ v2.03 ]
Setting : Update NVRAM : False
Setting : Force NVRAM : False
Setting : Update PMT : True
1. Power off device, wait 10-15 seconds
2. Press and hold BooKey ( 1 : BOTH VOL , 2 : VOL+ , 3 : VOL- )
3. Insert cable in device!
Wait for device .
Device Connected!
BootVersion : SPRD3
Boot : INF : INFINITY FW PACKAGE
Sending Init Boot .
Boot sent!
Kick FDL .
ERROR : FDL NOT started!
Error : Fail to boot FDL!
Unsupported device with selected fdl! Change settings!
Operation : Identify [ v2.03 ]
BootMode : FLASH
1. Power off device, wait 10-15 seconds
2. Press and hold BooKey ( 1 : BOTH VOL , 2 : VOL+ , 3 : VOL- )
3. Insert cable in device!
Wait for device .
Device Connected!
BootVersion : SPRD3
Boot : INF : 0_SC7731E_BASE : SC7731E_eMMC_1GB_RS
Sending Init Boot .
Boot sent!
Kick FDL .
ERROR : FDL NOT started!
Error : Fail to boot FDL!
Unsupported device with selected fdl! Change settings!
Источник
Infinity A035f samsung
merdjiosse
Member
Infinity-Box
merdjiosse
Member
Device Connected!
BootVersion : SPRD3
Boot : PAC : ums9230_4h10_Natv-userdebug-gms_QOGIRL6_R_SIGN.pac
Sending Init Boot .
Boot sent!
Kick FDL .
BootVersion : Spreadtrum Boot Block version 1.1
Protocol setup .
Port speed : 921600
Sending Flash Boot .
Boot sent!
Kick FLASH FDL .
FDL : 0x0020
FDL : EMMC_RO : False ; EMMC_PART : True ; EMMC_RPMB_SET : True
FDL : RAW : 0x0002
FDL : FLH : 0x400000
FDL : Control transfered!
>>> Error : Device NOT INITIALIZED ! Initialize it first via «IDENTIFY» !
>>> Make sure you have made «IDENTIFY» first!
Operation : Identify [ v2.14 ]
BootMode : FLASH
1. Power off device, wait 10-15 seconds
2. Press and hold BooKey ( 1 : BOTH VOL , 2 : VOL+ , 3 : VOL- )
3. Insert cable in device!
Wait for device .
Device Connected!
BootVersion : SPRD3
Boot : INF : UNISOC : ums9230_4h10_Natv
Sending Init Boot .
Boot sent!
Kick FDL .
BootVersion : Spreadtrum Boot Block version 1.1
Protocol setup .
Port speed : 921600
Sending Flash Boot .
>>> ERROR : FLASH FDL NOT started!
>>> Error : Fail to boot FDL!
>>> Unsupported device with selected fdl or settings! Change settings!
Operation : Flash Firmware [ v2.14 ]
Setting : Update NVRAM : False
Setting : Force NVRAM : False
Setting : Update PMT : True
1. Power off device, wait 10-15 seconds
2. Press and hold BooKey ( 1 : BOTH VOL , 2 : VOL+ , 3 : VOL- )
3. Insert cable in device!
Wait for device .
Device Connected!
BootVersion : SPRD3
Boot : PAC : ums9230_4h10_Natv-userdebug-gms_QOGIRL6_R_SIGN.pac
Sending Init Boot .
Boot sent!
Kick FDL .
BootVersion : Spreadtrum Boot Block version 1.1
Protocol setup .
Port speed : 921600
Sending Flash Boot .
Boot sent!
Kick FLASH FDL .
FDL : 0x0020
FDL : EMMC_RO : False ; EMMC_PART : True ; EMMC_RPMB_SET : True
FDL : RAW : 0x0002
FDL : FLH : 0x400000
FDL : Control transfered!
PMTMng : Load PMT
PMTMng : 0x35
PMTMng : Update PMT Ok!
Источник
ZTE Blade A5 2019 проблема с коннектом
flashmax
Есть ZTE Blade A5 2019 с дохлой EMMC, хочу сделать бекам nvram, но телефон нормально не конектится.
Если выбрать готовый пресет ZTE Blade A5 A7 2019 или прошивку — идет лог и потом окошко ошибки
Device Connected!
BootVersion : SPRD3
Boot : INF : ZTE : ZTE_BLADE_A5_A7_[2019]
Sending Init Boot .
Boot sent!
Kick FDL .
BootVersion : Spreadtrum Boot Block version 1.1
Protocol setup .
Port speed : 921600
Sending Flash Boot .
Boot sent!
Kick FLASH FDL .
FDL : 0x0004
FDL : EMMC_RO : True ; EMMC_PART : False ; EMMC_RPMB_SET : True
FDL : Control transfered!
UserData : STATE : DAMAGED
— > INFO : Remove cable from device to switch it off!
Done!
Elapsed: 00:04:18
Если выбрать пресет SC9863A_eMMC_3GB_0S
Device Connected!
BootVersion : SPRD3
Boot : INF : 0_SC9863x_BASE : SC9863A_eMMC_3GB_0S
Sending Init Boot .
Boot sent!
Kick FDL .
>>> ERROR : FDL NOT started!
>>> Error : Fail to boot FDL!
>>> Unsupported device with selected fdl or settings! Change settings!
Вложения
TELEDOKtor
Вложения
uploads
Ces69
flashmax
Sending Flash Boot .
>>> ERROR : FLASH FDL NOT started!
>>> Error : Fail to boot FDL!
>>> Unsupported device with selected fdl or settings! Change settings!
а вот не факт, может восстановится, а может и нет
есть горький опыт ZTE L8 — есть две ревизии, одна чужим бекапом восстанавливается, другая — нет.
хотел перестраховаться слив nvram
по поводу ISP — поделитесь распиновкой, что-то не нашел
Ces69
Вложения
flashmax
Ces69
uploads
Sending Flash Boot .
>>> ERROR : FLASH FDL NOT started!
>>> Error : Fail to boot FDL!
>>> Unsupported device with selected fdl or settings! Change settings!
а вот не факт, может восстановится, а может и нет
есть горький опыт ZTE L8 — есть две ревизии, одна чужим бекапом восстанавливается, другая — нет.
хотел перестраховаться слив nvram
по поводу ISP — поделитесь распиновкой, что-то не нашел
flashmax
uploads
sinko
Stick2
Bus Mode : 1 bit
Bus speed : Auto
Device : Kingston eMMC D26032
Page size : 512 B
Block size : 512 B
Block count : 61341696
Size : 29.25 GB (29952.00 MB)
Manufacturer ID : 0X70
Device/BGA : BGA (Discrete embedded)
OEM/Application ID : 0X00
Product name : D26032
Product revision : 1.0
Product serial number : (hex) 25DFEA0F
Manufacturing date : 12/2020
CSD structure : CSD version No. 1.2
SPEC version : 4.1, 4.2, 4.3, 4.4, 4.41, 4.5,
Data read access time1: 40 ms
TRAN speed : 26 MHz
READ block length : 512 Bytes
WP group enable : YES
Revision 1.8 (for MMC v5.1)
Erase block size : 512 Kbytes
Boot1 size : 4096 Kbytes
Boot2 size : 4096 Kbytes
RPMB size : 4096 Kbytes
Partition config : (0x08) 00001000
Boot partition enable : Boot partition 1
(Bus width = 1Bit)
Boot ACK : No boot acknowledge sent (default)
Boot bus conditions : (0x00) 00000000
Boot bus width : x1 (sdr) or x4 (ddr) bus width in boot operation mode (default)
Reset boot bus conditions : Reset bus width to x1, single data rate and backward compatible timings after boot operation (default)
Boot mode : Use single data rate + backward compatible timings in boot operation (default)
RST_n function : (0x01) RST_n signal is permanently enabled
Partitioning support : Device supports partitioning features
Enhanced attribute : Device can have enhanced technological features in partitions and user data area.
Max enhanced data size: 10174464 Kbytes
Partitions attribute : 0x0
Part setting completed: 0x0
GP partition 1 size : 0 b
GP partition 2 size : 0 b
GP partition 3 size : 0 b
GP partition 4 size : 0 b
Enhanced area size : (0x0) 0 b
Enhanced area start : (0x0) 0 b
Backup EXT_CSD saved to file C:/Program Files (x86)/Medusa Pro Software/EXT_CSD Backups/D26032_02_10_2022_23_59_13.bin.
P00: GPT (00000000, 00000800) 1024 KB
P01: prodnv (00000800, 00002800) 5 MB
P02: miscdata (00003000, 00000800) 1024 KB
P03: recovery (00003800, 00014000) 40 MB
P04: misc (00017800, 00000800) 1024 KB
P05: trustos (00018000, 00003000) 6 MB
P06: trustos_bak (0001B000, 00003000) 6 MB
P07: sml (0001E000, 00000800) 1024 KB
P08: sml_bak (0001E800, 00000800) 1024 KB
P09: uboot (0001F000, 00000800) 1024 KB
P10: uboot_bak (0001F800, 00000800) 1024 KB
P11: uboot_log (00020000, 00002000) 4 MB
P12: logo (00022000, 0000A000) 20 MB
P13: fbootlogo (0002C000, 00001800) 3072 KB
P14: l_fixnv1 (0002D800, 00001000) 2048 KB
P15: l_fixnv2 (0002E800, 00001000) 2048 KB
P16: l_runtimenv1 (0002F800, 00001000) 2048 KB
P17: l_runtimenv2 (00030800, 00001000) 2048 KB
P18: gpsgl (00031800, 00000800) 1024 KB
P19: gpsbd (00032000, 00000800) 1024 KB
P20: wcnmodem (00032800, 00005000) 10 MB
P21: persist (00037800, 00001000) 2048 KB
P22: ztecfg (00038800, 00004000) 8 MB
P23: ztepersist (0003C800, 00010000) 32 MB
P24: l_modem (0004C800, 0000C800) 25 MB
P25: l_deltanv (00059000, 00000800) 1024 KB
P26: l_gdsp (00059800, 00005000) 10 MB
P27: l_ldsp (0005E800, 0000A000) 20 MB
P28: pm_sys (00068800, 00000800) 1024 KB
P29: boot (00069000, 00011800) 35 MB
P30: dtb (0007A800, 00004000) 8 MB
P31: dtbo (0007E800, 00004000) 8 MB
P32: system (00082800, 00700000) 3584 MB
P33: cache (00782800, 0004B000) 150 MB
P34: vendor (007CD800, 000C8000) 400 MB
P35: product (00895800, 00032000) 100 MB
P36: vbmeta (008C7800, 00000800) 1024 KB
P37: vbmeta_bak (008C8000, 00000800) 1024 KB
P38: userdata (008C8800, 031B77DF) 24.86 GB
Searching Android build info.
Disk/Image size : 50000000 bytes
Device sector size : 512 bytes
Partition offset : 534528
Number of sectors : 7340032
Device Manufacturer : ZTE
Build ID : PPR1.180610.011
Display Build ID : GEN_RU_A5_2019_V2.2
Device Model : ZTE Blade A5 2019RU
Device Name : GEN_RU_P963F30P
Architecture ABI : arm64-v8a
Architecture ABI List : arm64-v8a,armeabi-v7a,armeabi
Build Description : s9863a1h10_Natv-user 9 PPR1.180610.011 302 release-keys
Writing EXT_CSD succesfully complete!
Please disconnect battery and USB cable.
Bus Mode : 1 bit
Bus speed : Auto
Device : Kingston eMMC D26032
Page size : 512 B
Block size : 512 B
Block count : 61341696
Size : 29.25 GB (29952.00 MB)
Manufacturer ID : 0X70
Device/BGA : BGA (Discrete embedded)
OEM/Application ID : 0X00
Product name : D26032
Product revision : 1.0
Product serial number : (hex) 25DFEA0F
Manufacturing date : 12/2020
CSD structure : CSD version No. 1.2
SPEC version : 4.1, 4.2, 4.3, 4.4, 4.41, 4.5,
Data read access time1: 40 ms
TRAN speed : 26 MHz
READ block length : 512 Bytes
WP group enable : YES
Revision 1.8 (for MMC v5.1)
Erase block size : 512 Kbytes
Boot1 size : 4096 Kbytes
Boot2 size : 4096 Kbytes
RPMB size : 4096 Kbytes
Partition config : (0x78) 01111000
Boot partition enable : User area
(Bus width = 1Bit)
Boot ACK : Boot acknowledge sent during boot operation Bit
Boot bus conditions : (0x00) 00000000
Boot bus width : x1 (sdr) or x4 (ddr) bus width in boot operation mode (default)
Reset boot bus conditions : Reset bus width to x1, single data rate and backward compatible timings after boot operation (default)
Boot mode : Use single data rate + backward compatible timings in boot operation (default)
RST_n function : (0x01) RST_n signal is permanently enabled
Partitioning support : Device supports partitioning features
Enhanced attribute : Device can have enhanced technological features in partitions and user data area.
Max enhanced data size: 10174464 Kbytes
Partitions attribute : 0x0
Part setting completed: 0x0
GP partition 1 size : 0 b
GP partition 2 size : 0 b
GP partition 3 size : 0 b
GP partition 4 size : 0 b
Enhanced area size : (0x0) 0 b
Enhanced area start : (0x0) 0 b
Backup EXT_CSD saved to file C:/Program Files (x86)/Medusa Pro Software/EXT_CSD Backups/D26032_03_10_2022_00_00_47.bin.
P00: GPT (00000000, 00000800) 1024 KB
P01: prodnv (00000800, 00002800) 5 MB
P02: miscdata (00003000, 00000800) 1024 KB
P03: recovery (00003800, 00014000) 40 MB
P04: misc (00017800, 00000800) 1024 KB
P05: trustos (00018000, 00003000) 6 MB
P06: trustos_bak (0001B000, 00003000) 6 MB
P07: sml (0001E000, 00000800) 1024 KB
P08: sml_bak (0001E800, 00000800) 1024 KB
P09: uboot (0001F000, 00000800) 1024 KB
P10: uboot_bak (0001F800, 00000800) 1024 KB
P11: uboot_log (00020000, 00002000) 4 MB
P12: logo (00022000, 0000A000) 20 MB
P13: fbootlogo (0002C000, 00001800) 3072 KB
P14: l_fixnv1 (0002D800, 00001000) 2048 KB
P15: l_fixnv2 (0002E800, 00001000) 2048 KB
P16: l_runtimenv1 (0002F800, 00001000) 2048 KB
P17: l_runtimenv2 (00030800, 00001000) 2048 KB
P18: gpsgl (00031800, 00000800) 1024 KB
P19: gpsbd (00032000, 00000800) 1024 KB
P20: wcnmodem (00032800, 00005000) 10 MB
P21: persist (00037800, 00001000) 2048 KB
P22: ztecfg (00038800, 00004000) 8 MB
P23: ztepersist (0003C800, 00010000) 32 MB
P24: l_modem (0004C800, 0000C800) 25 MB
P25: l_deltanv (00059000, 00000800) 1024 KB
P26: l_gdsp (00059800, 00005000) 10 MB
P27: l_ldsp (0005E800, 0000A000) 20 MB
P28: pm_sys (00068800, 00000800) 1024 KB
P29: boot (00069000, 00011800) 35 MB
P30: dtb (0007A800, 00004000) 8 MB
P31: dtbo (0007E800, 00004000) 8 MB
P32: system (00082800, 00700000) 3584 MB
P33: cache (00782800, 0004B000) 150 MB
P34: vendor (007CD800, 000C8000) 400 MB
P35: product (00895800, 00032000) 100 MB
P36: vbmeta (008C7800, 00000800) 1024 KB
P37: vbmeta_bak (008C8000, 00000800) 1024 KB
P38: userdata (008C8800, 031B77DF) 24.86 GB
Searching Android build info.
Disk/Image size : 50000000 bytes
Device sector size : 512 bytes
Partition offset : 534528
Number of sectors : 7340032
Device Manufacturer : ZTE
Build ID : PPR1.180610.011
Display Build ID : GEN_RU_A5_2019_V2.2
Device Model : ZTE Blade A5 2019RU
Device Name : GEN_RU_P963F30P
Architecture ABI : arm64-v8a
Architecture ABI List : arm64-v8a,armeabi-v7a,armeabi
Build Description : s9863a1h10_Natv-user 9 PPR1.180610.011 302 release-keys
Источник
-
#1
Code:
Chinese Miracle II [SPD module] v 1.27
Set mode to : SP SC77xx [Model Select]
Loading : 11.pac
CRVersion : BP_R1.0.0
PacCPUinfo : sp9832e_1h10
PacVersion : 11
FastCheck : 0x0000096CA9
Loading files ...
File : fdl1-sign.bin
File : fdl2-sign.bin
File : sp9832e_1h10.xml
Load Ok!
Start at : [09-Apr-19 / 1:22:03 PM]
Operation : Format File System / Reset Settings [ v1.27 ]
Settings : SmartFormat is On
1. Remove battery. Insert battery back
2. Press and hold 'VolumeUp' and 'VolumeDown' keys
-> Alternative : just ONE 'VolumeUp' or 'VolumeDown' key
3. Insert cable
==== Wait for phone...
Phone found! [ 13 ]
Port Opened
Sync...
InitBoot Done [ 0x81 ] , Ver : SPRD3
Sync...
Sending FDL
[Info] : If SW freeze here more, than 15 seconds - remove cable
PickUp loaders from pac
FDL Ready!
Boot Ver : Spreadtrum Boot Block version 1.1
Sending FLASH FDL
FLASH FDL Ready!
Boot Ok!
FlashMode Set : Ok!
Checking Structure ...
Detected eMMC Flash , Structure detect Ok!
eMMC phone detected! Will use 'Safe Format' mode!
UserData : PART_MOUNT failed! Part Damaged! Will use Repair Mode!
Mount : /cache
Size : 0x0000000007300000
State : 0x0001
Prepare Ok! Format Ok!
Don't touch phone, until it fully bootup to "Welcome Screen"!
Android 5.x/6.x : Reset FRP Lock
Reset Ok!
Done!
Elapsed: 00:00:29
Reconnect Power/Cable!
Finish at : [09-Apr-19 / 1:22:32 PM]
-
Itel A23 FRP.rar
218.5 KB
· Views: 2,633
-
#2
it’s spd cpu brother very easy just put your phone in fastboot mode and remove frp with fastboot commands
1.fastboot devices
2.fastboot erase persist
3.fastboot reboot
FRP DONE
-
#3
it’s spd cpu brother very easy just put your phone in fastboot mode and remove frp with fastboot commands
1.fastboot devices
2.fastboot erase persist
3.fastboot reboot
FRP DONE
ok sir
when you got this set in hand try your solution
and if not work try my way hope your work done
its have signed FDL1 and FDL2 hope you understand
rest SPD cpu work with your trick but this one note
-
#4
Bro but which tool we have to use
-
#5
Infinity CM2SPD use this for FRP reset or format
-
#6
Working 100%.. Thanks bro
-
#7
i tell a23
Working 100%.. Thanks bro
Operation : Format FS / Reset Settings [ v2.07 ]
Mode : Default [ Reset Settings + FRP ]
BootMode : FLASH
1. Power off device, wait 10-15 seconds
2. Press and hold BooKey ( 1 : BOTH VOL , 2 : VOL+ , 3 : VOL- )
3. Insert cable in device!
Wait for device …
Device Connected!
BootVersion : SPRD3
Boot : INF : 0_SC9832E_BASE : SC9832E_eMMC_1GB_RS
Sending Init Boot …
Boot sent!
Kick FDL …
ERROR : FDL NOT started!
Error : Fail to boot FDL!
Unsupported device with selected fdl or settings! Change settings!
Reconnect Power/Cable!
— — — Updated — — —
plz help
i tell a23 frp
-
#9
itel a23 jio file link
Google Drive — Virus scan warning
— — — Updated — — —
itel a23 jio file link
https://drive.google.com/u/0/uc?id=16gA17jc7VnMnOKnUZetK85P5eFQAQP65&export=download
4.4.2. скоро будут в любой хлам ставить. Чтобы получить дельный совет, надо задать дельный вопрос.
Для начала можно попробовать поставить ВОТ ЭТУ (http://www.ddixlab.com/public/digma/tabletpc/optima/optima_prime_tt7000pg/)
Для прошивки можно попробовать другой флешер, чем Вы шили не указали, вот все хвалят ЭТОТ (https://yadi.sk/d/9k1X1NMVoXtP8)
Ссылочка (http://www.ddixlab.com/public/digma/tabletpc/optima/) на каталог прошивок
Инструкция по прошивке скопипаст из интернета.
1. скачиваем прошивку и прошивальщик (ResearchDownload или UpgradeDownload)
2. распаковываем прошивку и в прошивальщике нажимаем шестерёнку
3. нажимаем кнопку стрелочка
4. подключаем выключенный аппарат с зажатой клавишей громкость + или —
(у меня планшет определился программой, но не стал прошиваться при зажатой клавише громкость+. я передёрнул кабель и подключил с зажатой клавишей громкость-)
5. когда в столбце Progress будет написано Previous Passed отключаем кабель от планшета и включаем
Еще очень немаловажный вопрос. На какой ОС прошиваете? Такая проблема как у вас возникает при использовании семерки. Можно решить 2 способами. 1) Поставить рядом с 7 винХР и прошить оттуда, либо при запуске флешера поставить галочку в свойствах «Всегда выполнять от имени администратора» и зайти во вкладку совместимость и запустить программу в режиме совмести с вин98.
Для начала можно попробовать поставить ВОТ ЭТУ — эту я и пробовал, 2 раза скачивал. (http://www.ddixlab.com/public/digma/tabletpc/optima/optima_prime_tt7000pg/)
Версии прошивальщика пробовал все.
На XP вообще не прошивается, как будто не видит.
Шью Spreadtrum на 7-ке, нормально выходило, с правами админа пробовал тоже.
Вот может попробовать прошивку с другой буквой?? С M?
Или как можно по серийнику определить заводскую прошивку?
На планшете — ID: 317115
SN — DTT7000PGBK41B9R24716
Для прошивки можно попробовать другой флешер, чем Вы шили не указали, вот все хвалят ЭТОТ (https://yadi.sk/d/9k1X1NMVoXtP8)
Скачал этот, в нем при нажатии на СТРЕЛКУ ,выдает ошибку:
Init BMFiles failed!
Это из чего?
Здравствуйте! Помогите разобраться. При прошивке флешером процесс останавливается через 3-5 сек и дальше не шьется. Почему?
Вот что пишет прошивальщик: Failed Incompatible Partition.
Пошаговая инструкция по исправлению ResearchDownload Incompatible Partition
Перед исправлением ошибки убедитесь, что скачана официальная прошивка из проверенного источника, так как неоригинальное ПО может повредить ваше устройство. Скачать официальные прошивки можно здесь. Если с прошивкой всё хорошо – переходите к исправлению ошибки:
- Откройте ResearchDownload
- Перейдите в Настройки
- Выберите пункт Backup
- В левом нижнем углу уберите галочки с трех последних пунктов
- Устанавливайте прошивку
Готово! Вы исправили Incompatible Partition в ResearchDownload! Если что-то не получилось или возникли вопросы – пишите в комментарии!
программа ResearchDownload_2.9.8004 Latest version — ССЫЛКА
Рекомендуем
5 комментариев:
у меня Lenovo A390t,что то не получается,и нету в бекапе ProdNv, PhaseCheck, не подскажешь в чём проблема?
делал как в видео показано?
У меня просто теперь пишет [Removed] Waiting.
Пробывал и с галочками, и без галочек, всё равно так-же.
Ох, братан, спасибо тебе огромное! Наконец я его восстановил благодаря тебе! Только после прошивки заводских nv удалось вернуть родные имеи с помощью writeimei. А каких только танцев с бубнов я не вытворял до этого.
This update adds the support of additional devices including devices with unisoc T610. Is it possible to root those devices now using cm2?
X3non
Recognized Contributor
Posts: 22,062
Threads: 571
Joined: Jul 2014
Reputation:
332
(17-01-2021, 03:24 PM)zhelan Wrote: This update adds the support of additional devices including devices with unisoc T610. Is it possible to root those devices now using cm2?
cm2 doesn’t root devices, normal operations such as read / write firmware, read / write nv e.t.c
you can check their changelog on their website for more info regarding what new features and device support the new update brings
zhelan
Enthusiastic Member
Posts: 12
Threads: 5
Joined: Jun 2020
Reputation:
0
But couldn’t it be used to root it. I mean :
1. Extract firmware
2. patch with magisk
3. Write firmware
Or it is not possible?
X3non
Recognized Contributor
Posts: 22,062
Threads: 571
Joined: Jul 2014
Reputation:
332
(18-01-2021, 04:32 PM)zhelan Wrote: But couldn’t it be used to root it. I mean :
1. Extract firmware
2. patch with magisk
3. Write firmwareOr it is not possible?
that depends on the device
Posts: 49,280
Threads: 1,347
Joined: Oct 2013
Reputation:
432
(18-01-2021, 04:32 PM)zhelan Wrote: But couldn’t it be used to root it. I mean :
1. Extract firmware
2. patch with magisk
3. Write firmwareOr it is not possible?
Tested it on the Hisense A5 Pro CC, doesn’t work.
Can’t speak for other Unisoc Tiger T610 devices
Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can’t wait.
(This post was last modified: 21-01-2021, 02:53 PM by hovatek.)
Posts: 13
Threads: 1
Joined: Oct 2019
Reputation:
0
(21-01-2021, 02:52 PM)hovatek Wrote:
(18-01-2021, 04:32 PM)zhelan Wrote: But couldn’t it be used to root it. I mean :
1. Extract firmware
2. patch with magisk
3. Write firmwareOr it is not possible?
Tested it on the Hisense A5 Pro CC, doesn’t work.
Can’t speak for other Unisoc Tiger T610 devices
Which drivers did you use for the Hisense A5 Pro CC? I tried several but I always get error like Fail to init handshake protocol, or other errors that I should connect the device again.
Did you press both voulme buttons when plugging in`?
Posts: 49,280
Threads: 1,347
Joined: Oct 2013
Reputation:
432
(02-02-2021, 10:24 AM)Timo Helfer Wrote: Which drivers did you use for the Hisense A5 Pro CC? I tried several but I always get error like Fail to init handshake protocol, or other errors that I should connect the device again.
Did you press both voulme buttons when plugging in`?
Here’s the log
Code:
Infinity-Box Chinese Miracle II : SPD/USC Module [SP2] v2.10
Load IDBase v8331 Ok!
Operation : Identify [ v2.10 ]
BootMode : FLASH
1. Power off device, wait 10-15 seconds
2. Press and hold BooKey ( 1 : BOTH VOL , 2 : VOL+ , 3 : VOL- )
3. Insert cable in device!
Wait for device ...
Device Connected!
BootVersion : SPRD3
Boot : INF : 0_UT61x_BASE : UT61x_eMMC_4GB_0S
Sending Init Boot ...
Boot sent!
Kick FDL ...
>>> ERROR : FDL NOT started!
>>> Error : Fail to boot FDL!
>>> Unsupported device with selected fdl or settings! Change settings!
Reconnect Power/Cable!
Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can’t wait.
(This post was last modified: 03-02-2021, 01:38 PM by hovatek.)