Database Info

HTC EVO 4G LTE updated to 1.22.651.3 ?

Anyone Rooted update to the new HTC EVO 4G LTE updated to 1.22.651.3 ?

gomfam said:
Anyone Rooted update to the new HTC EVO 4G LTE updated to 1.22.651.3 ?
Click to expand...
Click to collapse
I have been trying to update since last night to no avail... I keep getting a failure notice "Error Flashing zip /sdcard/ext_sd/OTA_JEWEL_CL_ICS_40_Sprint_WWE_1.22.652.3-1.13" once I try to install it with the Team recovery app.

Cybnex said:
I have been trying to update since last night to no avail... I keep getting a failure notice "Error Flashing zip /sdcard/ext_sd/OTA_JEWEL_CL_ICS_40_Sprint_WWE_1.22.652.3-1.13" once I try to install it with the Team recovery app.
Click to expand...
Click to collapse
I was finally able to update

gomfam said:
I was finally able to update
Click to expand...
Click to collapse
How did you do it. I am unable to update

I'm with you guys. When I try to update I get this from TeamWinRecovery's error log:
/sdcard/Download/OTA_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3-1.13.651.1_release_268352pdwvnjlt5q0w5qsi.zip ...
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
Installing update...
script aborted: assert failed: check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" ,
"SPCS_001") == "t"
assert failed: check_cid(getprop("ro.cid"), "00000000" , "11111111" , "22222222" , "33333333" , "44444444" , "55555555" , "66666666" , "77777777" , "88888888" , "99999999" , "SPCS_001") == "t"
E:Error in /tmp/sideload/package.zip
(Status 7)
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p35 | ext4 | 1277951 | 926668 | 1 | f |
| data | /dev/block/mmcblk0p37 | ext4 | 2260991 | 550776 | 1 | f |
| boot | /dev/block/mmcblk0p21 | emmc | 16384 | 16384 | 0 | i |
| recovery | /dev/block/mmcblk0p22 | emmc | 16383 | 16383 | 0 | i |
| cache | /dev/block/mmcblk0p36 | ext4 | 229375 | 4260 | 1 | f |
| sdcard2 | /dev/block/mmcblk1p1 | vfat | 7768064 | 4882560 | 1 | n |
| sdcard | /dev/block/mmcblk0p38 | vfat | 10418176 | 2442368 | 1 | n |
| andsec | /sdcard | vfat | 32 | 32 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | ext4 | 0 | 0 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
Error flashing zip '/sdcard/Download/OTA_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3-1.13.651.1_release_268352pdwvnjlt5q0w5qsi.zip'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'

The best option right now is to download and flash either the odexed or deodexed version of the Rooted Stock ROM, which can be found here on xda - http://forum.xda-developers.com/showthread.php?t=1766628

EFS, modemst1, modemst2, fsg, backup partitions - Backup needed and what do they do?

Sorry for posting this in Android Development, but I think this is important information that many other people might want to know as well:
In addition to the EFS partition, there are several partitions on our n9005 devices that do not exist in official odin roms.
This means that they must be unique to your phone, and they might be as important to back up as the EFS folder to prevent IMEI loss or other problems (like those bootloops many people get when flashing kernels, which appear to be tied to corrupted modemst1 partitions).
These partitions are: modemst1, modemst2, fsg, fsc, backup, dbi, ddr, pad
You can see them by executing the following command:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
---
CWM does not back up EFS at all afaik, and the EFS backup tools usually only take the EFS partition while ignoring the others.
TWRP is the only one which also backs up modemst1 and modemst2 as far as I can tell. (it creates 2 additional efs backup files with 3MB in size - which is exactly the size of these partitions.)
--
From further research (this was discussed in the S3 forum) it turns out that the "fsg" and the "backup" partitions are meant to take copies of the modemst1 and modemst2 partitions - this can be done/forced by executing "reboot nvbackup" in terminal or with adb. So these partitions are meant to hold the backups of modemst1 and modemst2. But I'm not sure if our devices ship with these backups already made - the S3's apparently did not, so users had to do this backup themselves. (and/or use dd to also create image backups of these partitions)
People in the S3 forum reported that when they had corrupted modemst1 and/or modemst2 partitions (and no backup available) that while they still had their imei through EFS backup (or written to the phone with qualcomm tool) that they could only use the phone on roaming with these partitions corrupted.
---
So does anyone actually know more about this? Please lets use this thread to figure out (and then create some sort of sticky with the info) what these partitions actually do and if they need backup.
The "bootloop" fix goes as far as formatting modemst1 and modemst2 (I done it myself too in terminal before) to fix the bootloop issue. And its said that the partitions contents are just recreated then. But from which source? EFS or the fsg / backup partitions? etc.
This really needs some further investigation I think.
---
What I also did was to compare all the backups I had and see if they were the same or if they did differ.... and the weird thing is that EVERY single backup I have of my EFS folder or the modemst1 and modemst2 partitions do differ in checksum and also in binary diff.
Even the EFS folder did change over the time it seems. (partially this is caused by me editing the wifi mac ... but even before I did that the efs backups did differ from backup to backup).
But nonetheless, it seems that my phone is actually working alright. I have my imei, and I can just normally log in to my carrier network (can only test hsdpa+ though) and wifi is alright too.
So it appears that modemst1 and modemst2 indeed get recreated if they are formatted, but what about those other partitions. Unfortunately (since I only have one backup of these, made by hand) I cannot compare them to see if they also changed over the time.
--
Last but not least: modemst1, modemst2, fsg (meant to have copy of modemst1) and backup (meant to hve copy of modemst2) also differ on my device..... (can you guys who are fit in the terminal maybe also test if the partitions differ on your phones or if they are indeed copies?)
...
Would really like to understand these partitions more...

Thank you so much, always wondered what all those things meant and what they did...very informative

thanks you for making this thread.
so we can understand it.
i edited and made a windows efs backup tool for making backup and restore EFS, modemst1, modemst2.
and i will edit aroma method too.
... if we need more backup of more partitions, i will edit EFS Tool for them (dd backup/restore method)
http://forum.xda-developers.com/showpost.php?p=49460571&postcount=4

so I got some more infos:
I checked the "fsg" and "backup" partition, and they did not change over the course of all my actions. Even the partitions on the system are exactly the same as they were when I took backups. (remember: EFS and modemst1 and modemst2 constantly changed, and I could not find 2 exact copies in my backups).
So this means fsg and backup are indeed left untouched.
----
Since they are meant to hold backups of modemst1 and modemst2 which can be restored with "reboot nvrestore" I tried that as well.
But apparently they do not contain valid backups when you first get your phone (just like in the S3 case).
When I tried nvrestore the device rebooted and showed a message like "no nvbackup found" in red letters. (phone was stuck in this mode, even with forced reboot by holding down power - only pulling the battery got my device back to normal life... man was I scared when this message kept reappearing on hard reset)..
---
So in turn this means, the best thing to do when you get a new N3 (and didnt mess up modemst1 and modemst2 yet by flashing) that you should run "reboot nvbackup" in terminal.
This will fill the fsg and backup partition with valid copies of modemst1 and modemst2 which later can be restored with "reboot nvrestore".
---
Still not sure what these partitions are really about - they seem to be the "nvram" of the device (whatever that is lol) ... and I *think* there are things stored like carrier specific settings from what I understood. So simlock and netlock etc is stored there apparently. But since the note3's are all simlock free as far as I know (at least our n9005s) this should not really be important to us.
But when they are corrupted we get the bootloops.
These can be fixed by simply formatting the partitions, but I'm not 100% sure if this has any downsides yet. (aka if we need our original modemst1 and modemst2, or if it does not matter....)
ADD: I read in another post that someone lost his imei when his modemst1 got corrupted/formatted. But I can just say that I manually formatted modemst1 and modemst2 before (if you try this, back them up first though!!!!!!!) and I kept my imei and could connect phone to carrier etc. So the imei does not seem to be stored there really.
---
Someone has to know more about this, please enlighten us.....

Interesting subject...
To add bits, pit file dump:
Code:
PIT dump v1.0 by LeTama
- 30 partitions in PIT file
- Format string = [COM_TAR2MSM8974]
01|APNHLOS | 0x00002000 | 0x00007800 | 8192 | 30720 | 15360 KB | NON-HLOS.bin
02|MODEM | 0x00009800 | 0x0001CB80 | 38912 | 117632 | 58816 KB | modem.bin
03|SBL1 | 0x00026380 | 0x00000400 | 156544 | 1024 | 512 KB | sbl1.mbn
04|DBI | 0x00026780 | 0x00000040 | 157568 | 64 | 32 KB | sdi.mbn
05|DDR | 0x000267C0 | 0x00000040 | 157632 | 64 | 32 KB |
06|ABOOT | 0x00026800 | 0x00001000 | 157696 | 4096 | 2048 KB | aboot.mbn
07|RPM | 0x00027800 | 0x00000400 | 161792 | 1024 | 512 KB | rpm.mbn
08|TZ | 0x00027C00 | 0x00000400 | 162816 | 1024 | 512 KB | tz.mbn
09|PAD | 0x00028000 | 0x00005000 | 163840 | 20480 | 10240 KB |
10|PARAM | 0x0002D000 | 0x00005000 | 184320 | 20480 | 10240 KB | param.bin
11|EFS | 0x00032000 | 0x00007000 | 204800 | 28672 | 14336 KB | efs.img.ext4
12|MODEMST1 | 0x00039000 | 0x00001800 | 233472 | 6144 | 3072 KB | nvrebuild1.bin
13|MODEMST2 | 0x0003A800 | 0x00001800 | 239616 | 6144 | 3072 KB | nvrebuild2.bin
14|BOOT | 0x0003C000 | 0x00005800 | 245760 | 22528 | 11264 KB | boot.img
15|RECOVERY | 0x00041800 | 0x00006800 | 268288 | 26624 | 13312 KB | recovery.img
16|FOTA | 0x00048000 | 0x00006800 | 294912 | 26624 | 13312 KB |
17|BACKUP | 0x0004E800 | 0x000037EE | 321536 | 14318 | 7159 KB |
18|FSG | 0x00051FEE | 0x00001800 | 335854 | 6144 | 3072 KB |
19|FSC | 0x000537EE | 0x00000002 | 341998 | 2 | 1 KB |
20|SSD | 0x000537F0 | 0x00000010 | 342000 | 16 | 8 KB |
21|PERSIST | 0x00053800 | 0x00004000 | 342016 | 16384 | 8192 KB | persist.img.ext4
22|PERSDATA | 0x00057800 | 0x00004800 | 358400 | 18432 | 9216 KB | persdata.img.ext4
23|SYSTEM | 0x0005C000 | 0x00480000 | 376832 | 4718592 | 2359296 KB | system.img.ext4
24|CACHE | 0x004DC000 | 0x00096000 | 5095424 | 614400 | 307200 KB | cache.img.ext4
25|HIDDEN | 0x00572000 | 0x0000F000 | 5709824 | 61440 | 30720 KB | hidden.img.ext4
26|USERDATA | 0x00581000 | 0x00000000 | 5771264 | 0 | 0 KB | userdata.img.ext4
70|PGPT | 0x00000000 | 0x00000022 | 0 | 34 | 17 KB | pgpt.img
71|PIT | 0x00000022 | 0x00000010 | 34 | 16 | 8 KB | MSM8974.pit
72|MD5 | 0x00000032 | 0x00000020 | 50 | 32 | 16 KB | md5.img
73|SGPT | 0x03A3DFDF | 0x00000021 | 61071327 | 33 | 16 KB | sgpt.img
-----------------
- signature /trailer size = [4204]
It's showing more locations than the one exposed by kernel like pgpt /sgpt (primary/secondary gpt partition table), pit table, md5 (?).
Last, there is the rpmb partition that we can't see without knowing the access key.

genius.lizard2 said:
thanks you for making this thread.
so we can understand it.
i edited and made a windows efs backup tool for making backup and restore EFS, modemst1, modemst2.
and i will edit aroma method too.
... if we need more backup of more partitions, i will edit EFS Tool for them (dd backup/restore method)
http://forum.xda-developers.com/showpost.php?p=49460571&postcount=4
Click to expand...
Click to collapse
Thank you, worked perfectly.:good:

I can't flash rom higher than JB, please help

My sensation is in stock ICS, already s-off, unlocked bootloader, hboot 1.27, with TWRP but i can't flash any rom which is higher than JB. Here is the log when i flash LP rom (liquid smooth)
ui_print
package_extract_file: can't open /dev/block/platform/msm_sdcc.1/by-name/boot for write: No such file or directory
unmount of /system failed; no such volume
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
\ ) ( )\ ) )\ )
(()/ ( ( )\ ( (()/((()/(
(_)) ((_) (_)_) /((_)(_)) (_))
| | (_) / _ \ (_))( |_ _| | \
| |__ | || (_) || || | | | | |) |
|____||_| \__\_\ \_,_||___| |___/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
<%%% Liquid-lollipop %%%>
<%%% By LiquidSmooth %%%>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
script succeeded: result was [=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-] * Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
Filesystem 1K-blocks Used Available Use% Mounted on
df: /dev/block/mmcblk1p2: can't find mount point
32
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p22 | ext4 | 819199 | 698884 | 1 | f |
| data | /dev/block/mmcblk0p23 | ext4 | 1223409 | 215056 | 1 | f |
| boot | /dev/block/mmcblk0p20 | emmc | 16384 | 16384 | 0 | i |
| recovery | /dev/block/mmcblk0p21 | emmc | 16383 | 16383 | 0 | i |
| cache | /dev/block/mmcblk0p24 | ext4 | 122839 | 4168 | 1 | f |
| sdcard | /dev/block/mmcblk1p1 | vfat | 1929244 | 1457056 | 1 | n |
| | | | 0 | 0 | 0 | n |
| andsec | /sdcard | vfat | 0 | 0 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | ext4 | 0 | 0 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'settings'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'mount'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'

Boa134 said:
My sensation is in stock ICS, already s-off, unlocked bootloader, hboot 1.27, with TWRP but i can't flash any rom which is higher than JB. Here is the log when i flash LP rom (liquid smooth)
ui_print
package_extract_file: can't open /dev/block/platform/msm_sdcc.1/by-name/boot for write: No such file or directory
unmount of /system failed; no such volume
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
\ ) ( )\ ) )\ )
(()/ ( ( )\ ( (()/((()/(
(_)) ((_) (_)_) /((_)(_)) (_))
| | (_) / _ \ (_))( |_ _| | \
| |__ | || (_) || || | | | | |) |
|____||_| \__\_\ \_,_||___| |___/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
<%%% Liquid-lollipop %%%>
<%%% By LiquidSmooth %%%>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
script succeeded: result was [=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-] * Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
Filesystem 1K-blocks Used Available Use% Mounted on
df: /dev/block/mmcblk1p2: can't find mount point
32
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p22 | ext4 | 819199 | 698884 | 1 | f |
| data | /dev/block/mmcblk0p23 | ext4 | 1223409 | 215056 | 1 | f |
| boot | /dev/block/mmcblk0p20 | emmc | 16384 | 16384 | 0 | i |
| recovery | /dev/block/mmcblk0p21 | emmc | 16383 | 16383 | 0 | i |
| cache | /dev/block/mmcblk0p24 | ext4 | 122839 | 4168 | 1 | f |
| sdcard | /dev/block/mmcblk1p1 | vfat | 1929244 | 1457056 | 1 | n |
| | | | 0 | 0 | 0 | n |
| andsec | /sdcard | vfat | 0 | 0 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | ext4 | 0 | 0 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'settings'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'mount'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
Click to expand...
Click to collapse
Did you try with another recovery?
Try with 4 ext recovery

rzr86 said:
Did you try with another recovery?
Try with 4 ext recovery
Click to expand...
Click to collapse
I already tried CWM and 4ext but they are all the same

Boa134 said:
I already tried CWM and 4ext but they are all the same
Click to expand...
Click to collapse
Did you use any wipe option from TWRP?

rzr86 said:
Did you use any wipe option from TWRP?
Click to expand...
Click to collapse
I think it's factory reset, or wipe user data... In the past, when I used
4ext, i chose an option that format all partition (except Sd card) Is that the problem?

Boa134 said:
I think it's factory reset, or wipe user data... In the past, when I used
4ext, i chose an option that format all partition (except Sd card) Is that the problem?
Click to expand...
Click to collapse
the issue probably came from twrp
lots of users faced that
some version of twrp breaks /data and /cache partition
did you try to flash any ics custom rom?

rzr86 said:
the issue probably came from twrp
lots of users faced that
some version of twrp breaks /data and /cache partition
did you try to flash any ics custom rom?
Click to expand...
Click to collapse
No, i flashed CM10 JB and Viper JB

Boa134 said:
No, i flashed CM10 JB and Viper JB
Click to expand...
Click to collapse
did you ask in the rom thread?
probably you need to do something with f2fs system from twrp but i am not sure

rzr86 said:
did you ask in the rom thread?
probably you need to do something with f2fs system from twrp but i am not sure
Click to expand...
Click to collapse
Your Sensation has root access, right? If so, can you please take a screen shot of the path /dev/block/platform/msm_sdcc.1/ (any file explorer)... I think my sensation misses some files in that folder

Boa134 said:
Your Sensation has root access, right? If so, can you please take a screen shot of the path /dev/block/platform/msm_sdcc.1/ (any file explorer)... I think my sensation misses some files in that folder
Click to expand...
Click to collapse
here you are

ZTE 5G Gone black

After trying to flash my phone with lineage OS via adb it has gone black. Only EDL working.
I tried to flash a Android 9 1.6 for recovery, but with following log. Can anyone help?
============================================================================================================
15:32:28: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
15:32:28: DEBUG: CHANNEL DATA (16 bytes) <-- TARGET to HOST
15:32:28: DEBUG: CharsInBuffer = 16
15:32:28: DEBUG: printBuffer:5435 PRETTYPRINT Buffer is 16 bytes
15:32:28: DEBUG: printBuffer:5512 04 00 00 00 10 00 00 00 0D 00 00 00 01 00 00 00 ................
15:32:28: DEBUG: printBuffer:5525
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
15:32:28: {ERROR: DetermineTag:6236 XML not formed correctly. Expected a < character at loc 0
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
15:32:28: {ERROR: GetNextPacket:7310 3. TAG not found or recognized
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
15:32:28: {ERROR: GetNextPacket:7320
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13rog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work

Did you make an EDL backup before performing this procedure?
What is the model number of your phone?
Gararoth said:
After trying to flash my phone with lineage OS via adb it has gone black. Only EDL working.
I tried to flash a Android 9 1.6 for recovery, but with following log. Can anyone help?
============================================================================================================
15:32:28: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
15:32:28: DEBUG: CHANNEL DATA (16 bytes) <-- TARGET to HOST
15:32:28: DEBUG: CharsInBuffer = 16
15:32:28: DEBUG: printBuffer:5435 PRETTYPRINT Buffer is 16 bytes
15:32:28: DEBUG: printBuffer:5512 04 00 00 00 10 00 00 00 0D 00 00 00 01 00 00 00 ................
15:32:28: DEBUG: printBuffer:5525
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
15:32:28: {ERROR: DetermineTag:6236 XML not formed correctly. Expected a < character at loc 0
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
15:32:28: {ERROR: GetNextPacket:7310 3. TAG not found or recognized
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
15:32:28: {ERROR: GetNextPacket:7320
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13rog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
Click to expand...
Click to collapse

ZTE BLACK 5g a20n2
Hi thx for your reply - i got i to work again... BUT!!!
->
->
I wanted to update the firmware of my zte axon 10 pro. I installed a 1.6 version with EDL tool. Android is working, but then i realized the SIM-CARD wont work....!!!! Then i saw that the firmware i installed was for the 4G version.. I than found a firmware for my a2020n2...
ztedevices.com/cn/supports/zte-a2020n2-pro/[/url]
only problem is, i am not able to install the SD version because update now thinks i have the 4G version.... Only possible way would be to install force via 5G EDL version - but i can only find SD -Card versions and they won'T work...
any help??

Gararoth said:
Hi thx for your reply - i got i to work again... BUT!!!
->
->
I wanted to update the firmware of my zte axon 10 pro. I installed a 1.6 version with EDL tool. Android is working, but then i realized the SIM-CARD wont work....!!!! Then i saw that the firmware i installed was for the 4G version.. I than found a firmware for my a2020n2...
ztedevices.com/cn/supports/zte-a2020n2-pro/[/url]
only problem is, i am not able to install the SD version because update now thinks i have the 4G version.... Only possible way would be to install force via 5G EDL version - but i can only find SD -Card versions and they won'T work...
any help??
Click to expand...
Click to collapse
I don't have experience actually doing this but I have seen plenty of people mention doing it and it working - google "payload dumper xda" and you'll find a thread explaining how to use a python script that will take the SD card payload.bin and unpack it. You should then be able to use those files with the EDL tool.

ZTE BLACK 5g a20n2
bobthenormal said:
I don't have experience actually doing this but I have seen plenty of people mention doing it and it working - google "payload dumper xda" and you'll find a thread explaining how to use a python script that will take the SD card payload.bin and unpack it. You should then be able to use those files with the EDL tool.
Click to expand...
Click to collapse
I tried that and i managed to dump the payload bin. installing via EDL Tool 5G says: Not found important files, or detected SPARSE image... and MiFlash won't work either... I have bootloader unlocked but no root.... any help?

Gararoth said:
I tried that and i managed to dump the payload bin. installing via EDL Tool 5G says: Not found important files, or detected SPARSE image... and MiFlash won't work either... I have bootloader unlocked but no root.... any help?
Click to expand...
Click to collapse
When you try to use MiFlash what is your error?
If it's the hello packet issue - try this. Get MiFlash ready, all set up to hit "flash". Reset the phone (long press power) into EDL - as the phone is booting up into EDL, keep hitting refresh in MiFlash. The second the phone shows up, hit flash

ZTE BLACK 5g a20n2
Before i read your suggestion, i managed to install a 5G version via EDL-Tool 5G with success, but i am stuck in a bootloop... tried to get the battery to 0%, but as soon as i connect the phone via usb, bootloop is starting again, what now?

Gararoth said:
Before i read your suggestion, i managed to install a 5G version via EDL-Tool 5G with success, but i am stuck in a bootloop... tried to get the battery to 0%, but as soon as i connect the phone via usb, bootloop is starting again, what now?
Click to expand...
Click to collapse
How fast is the bootloop? 3 seconds or more like 8?
I assume by bootloop you mean the ZTE logo.

ZTE BLACK 5g brick
It's 3 seconds ZTE Screen. I waited some days to have zero power and tried to get in EDL mode... but no chance. When there is enough power again it starts autmatically with the ZTE screen 3 secs.

Gararoth said:
It's 3 seconds ZTE Screen. I waited some days to have zero power and tried to get in EDL mode... but no chance. When there is enough power again it starts autmatically with the ZTE screen 3 secs.
Click to expand...
Click to collapse
You couldn't get in EDL mode? That's very unlikely if the buttons aren't broken... it's part of the boot process that's stored in hardware, so you can't really lose it.
You're holding down BOTH the Vol+ and Vol- buttons? And plugged into a computer? If so and you hold those down while it bootloops (no need to press the power button), the loops should stop and the phone stay black. That indicates it's in EDL mode and you should see it show up in Device Manager.
If it doesn't, you might need the USB drivers. You can get them from the tools I posted in the Guide section, or probably from ZTE (I'm not sure).

ZTE BLACK 5g
You were right.... i switched to edl mode via adb and this won't work with a boot loop... i didnt know about the volume up and down command you saved my life.. only thing now is that i have to find a 5G img that works.. with EDL tool i manage to install the images resulting everytime in a bootloop. 3secs.... lineageOS boots to recovery with and error "cannot load android system" - installation via Miflash doesnt work exept A2020G_PRO_V1.6_FULL_EDL (but thats 4G and doesn't regognize the SIM card) - i will try some other images and let you know.

ZTE BLACK 5g
I managed now to install lineageOS16 after a factory reset in recovery mode! But the same .. regognizing the SIM Card but no mobile netzwork... working on other phone...
Gararoth said:
You were right.... i switched to edl mode via adb and this won't work with a boot loop... i didnt know about the volume up and down command you saved my life.. only thing now is that i have to find a 5G img that works.. with EDL tool i manage to install the images resulting everytime in a bootloop. 3secs.... lineageOS boots to recovery with and error "cannot load android system" - installation via Miflash doesnt work exept A2020G_PRO_V1.6_FULL_EDL (but thats 4G and doesn't regognize the SIM card) - i will try some other images and let you know.
Click to expand...
Click to collapse

ZTE BLACK 5g
I now tried to install the original firmware A2020N3 Pro (A1) SD card software package(378980B2730A1_AT_EEA_A2020N3_Pro_V1.20) i dumped the payload bin and installed via EDL5G and MIFlash.. bothe installation worked. ending in a bootllop....

Gararoth said:
I now tried to install the original firmware A2020N3 Pro (A1) SD card software package(378980B2730A1_AT_EEA_A2020N3_Pro_V1.20) i dumped the payload bin and installed via EDL5G and MIFlash.. bothe installation worked. ending in a bootllop....
Click to expand...
Click to collapse
I might be able to get the SD card package to apply with my tools, but I need some things:
a) List of the files from the payload (just copy-paste a "dir" of the directory, filenames and file sizes)
b) If in those files you have a bunch of files starting with GPT, like gpt_main0.bin, etc. Copy them all into a zip file and upload them (no personal information in them, they're partition sector information for the hard disk)
c) just to double check - download the tools I uploaded and follow the instructions in that thread to run GPT backup... that will get a bunch of gpt files - zip those up and upload them too
With those I'll modify the tools to work with your phone variant and you may be able to manually flash the payload files.

Axon 10 Pro Fully bricked

Hi,
I tried to flash my A2020G, as I have with other phones before. I got stuck in a Bootloop but managed to recover with the US firmware and was able to install twrp. In twrp I completely wiped and formatted the data, as i normally do. Then, I couldnt send a zip file over, so I tried to reboot. Bad Idea! I lost my recovery (Device corrupt). So I reflashed the firmware, but still got stuck in a bootloop, tried everything, nothing got me out. So I flashed the Axon 7 firmware. Even worse Idea. Now, the screen stays black, none of the combinations work. When I plug it in it connects and the Programmer of the edl tool connects as well. I reflashed everything but the screen still stays black. No acces to fastboot as well. Now I'm helpless and hope someone can help me out! When I do edl reset, it gives me this error, maybe that can help.
12:11:48: INFO: Sending <power>
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
12:11:50: {ERROR: XML not formed correctly. Expected a < character at loc 0}
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
12:11:50: {ERROR: 3. TAG not found or recognized}
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
12:11:50: {ERROR:
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13rog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
}
Writing log to 'D:\gfrtill\Downloads\Axon10Pro_(More)_EDL_Tools_v1.1d\Axon10Pro_(More)_EDL_Tools_v1.1d\Reset (from EDL)\port_trace.txt', might take a minute
Log is 'D:\gfrtill\Downloads\Axon10Pro_(More)_EDL_Tools_v1.1d\Axon10Pro_(More)_EDL_Tools_v1.1d\Reset (from EDL)\port_trace.txt'
Press any key to exit

Error has now gone, still no output though. Im guessing i might have ruined one of the drivers?!?