• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[TOOL] [TISSOT] Low-level Backup/Restore/Unbrick toolkit for Mi A1

Search This thread

CosmicDan

Senior Member
Jun 19, 2009
5,890
7,736
34
Sydney
Google Pixel 3 XL
Xiaomi Poco X3 Pro
What?

A Windows (only) toolkit for making full backup/restore of all Mi A1 partitions to/from your PC.

  • Utilizes EMMCDL in Qualcomm EDL mode - only needs fastboot access (unlocked BL) or testpoint (for bricked devices, maybe locked ones too - not sure)
  • Backups create a rawprogram0.xml file which could also be restorable in MiFlash if you choose (untested - not part of toolkit goal).
  • See FAQ at bottom for details about how to use EDL mode.

--------------------------------

Why?

Mainly to...

  • ...backup all your hidden/system partitions that TWRP cannot (e.g. persist) to keep them safe.
  • ...recover your device in the event of a brick

--------------------------------

How?

Requirements

  • Windows PC ONLY
  • Qualcomm EDL drivers (can get them from here, among other places)
  • Fastboot access working with driver (generic binary and driver work fine, it's all over the place
  • If you're firm-bricked (stuck in Diagnostic mode) you need to disassemble and bridge the test-points to kick it out of diagnostic mode - but that's beyond the scope of this thread/tool.

Setup

  1. Download the latest version from GitHub (link at bottom) and extract
  2. Connect your device with a quality USB-C cable (original worked well). Some cheap cables, or USB2 > USB-C adapters can cause the process to fail.
  3. Boot into fastboot and run the command...
    Code:
    fastboot oem edl
    ...you may see an error, that's normal. Device should now have blank screen and a white flashing light.
  4. Install the QDLoader driver. You may see this in device manager if you've not installed it yet...
    [Link because XDA forum keeps breaking my IMG tags whenever I edit]
    ...just right click > properties > update driver, the usual thing (if you downloaded the smaller driver pack ZIP from above). Then it should look like this...
    [Link because XDA forum keeps breaking my IMG tags whenever I edit]
  5. If your COM port in device manager (see above) is not COM30, you need to-
    1. Edit the config.ini in the toolkit folder
    2. Replace com30 with whatever your port is
  6. Now you're ready to use the tool.

Usage

The toolkit is pretty self-explanatory. But first you need to select which partitions you want to backup with option 1. Two partition lists are already included:

  • partition_list.all.txt - this list selects all partitions that exist on the Mi A1. Note that backing up system(_a/_b) and especially userdata will take a VERY LONG TIME. Also note that the backup images are NOT compressed; so expect to have 32GB space free for example (if you have a 32GB device).
  • partition_list.skip-systems-and-userdata.txt - this will backup all partitions except system(_a/_b) and userdata. More useful, since we backup system and userdata in TWRP anyway. All the other firmware partitions come to only about 500MB.
Once you select the list you want to use, you can run the backup with 2 - just enter a folder name and it'll go there.

Restore does not require a partition list to be loaded; since the partition table is stored inside the backup as rawpartition0.xml. You can manually edit this file if you want to selectively restore partitions - just delete the whole line of partitions you don't want to restore. Note that changing any of these values will NOT repartition the device - you'll only corrupt your partition table if you do this.

Well I guess that's it, I will update this guide after feedback (it's a bit rough, I am kind of rushing lol).

--------------------------------

Where?


Download the latest version on GitHub:
https://github.com/CosmicDan-Android/MiA1LowLevelBackupRestoreTool
... simply press the green 'Clone or download' button on the right, then 'Download ZIP'.

--------------------------------

Who?

  • Special thanks to @emuzychenko for his batch script wizardry which this is mostly based on. You can see his original tool and scripts here. I just re-wrote it all to be more user friendly and convenient for me and others.

--------------------------------

History



2018-05-23

  • Added config option to change transfer speed (reducing may help with freezes)

2018-05-15


  • Fixed crashing when path containing tool has spaces
  • Added a "debug mode" that won't instantly close the Window in event of a hard crash (why oh why did I ever use Batch again...)
  • Added a "persist-only" partition list
2018-05-14

  • Initial version


--------------------------------

FAQ

Q) EDL mode? Eh?
A) EDL mode, or "Emergency DownLoad" mode, is a low-level mode for flashing devices. It is entered by the command:
Code:
fastboot oem edl
EDL mode is used to read/write to the eMMC more directly. It is used by this tool, as well as flashing with MiFlash.
Other important notes:
  • You will need good QDLoader drivers. These drivers gave me the best results.
  • You can exit EDL mode by holding Power button for ~10 seconds. Hold with VolDn to reboot into fastboot again, as one might expect.
  • Make sure you use a good USB-C cable.
  • Sometimes the flashing process can freeze. It will always report success when done. If it freezes, you need to reboot EDL mode. Try a different USB port or cable if you keep experiencing freezes.


Q) I get a freeze or hang when trying backup/restore partitions
A) First, make sure it's actually frozen. Open log.txt in the tool folder, and then open it again to see if it's changed.

If not, make sure you're using the driver linked in this post, as it proved to be most reliable by myself and others. You can also try these things (recommended in this order):

  • Reboot to EDL mode again;
  • Use a different (better) cable;
  • Use a different USB port;
  • Reduce the transfer speed in config.ini (be sure to read the comments)
  • Use a different PC;

Of course all are welcome to post their questions/suggestions and so on. Happy flashing!
 
Last edited:

rubenswing

Senior Member
Mar 28, 2008
389
72
26.8500° N, 80.9200° E
First of all it doesn't work for me with a locked bootloader, I had to unlock the bootloader and followed the instructions, after opening the program and selecting any option in the tool simply closes the window and nothing happens. I tried it 4 times but no use, it just closes the command prompt window
 

CosmicDan

Senior Member
Jun 19, 2009
5,890
7,736
34
Sydney
Google Pixel 3 XL
Xiaomi Poco X3 Pro
First of all it doesn't work for me with a locked bootloader, I had to unlock the bootloader and followed the instructions, after opening the program and selecting any option in the tool simply closes the window and nothing happens. I tried it 4 times but no use, it just closes the command prompt window

Oh derp to me; of course locked bootloader can't access fastboot at all can it! Shows how experienced I am with locked devices :p thanks - updated thread with statement of unlocked BL requirement.

Re: Your crash, I realized right away that that is very likely because the program path has spaces in it. I fixed that now, just download the tool again and it should work. If not though, there is now a _debug tool that will show you the error instead of instantly closing. But I'm 90% sure that the problem you had is now fixed.
 
  • Like
Reactions: jucaftp

cherryb8844

Senior Member
May 24, 2015
369
123
So you mention that all partition. Mean I can make persist and IMEI partition (I don't know whatever it called in our device in Samsung it's called efs) backup to. I did backup of IMEI partition via qpst tool (it's .qcnfile) but I wanted to make more backup. My WiFi is broken since I installed custom rom so I restored it via persist resurrect tool.
Thanks for your hardwork making thing easy for us.
 

CosmicDan

Senior Member
Jun 19, 2009
5,890
7,736
34
Sydney
Google Pixel 3 XL
Xiaomi Poco X3 Pro
So you mention that all partition. Mean I can make persist and IMEI partition (I don't know whatever it called in our device in Samsung it's called efs) backup to. I did backup of IMEI partition via qpst tool (it's .qcnfile) but I wanted to make more backup. My WiFi is broken since I installed custom rom so I restored it via persist resurrect tool.
Thanks for your hardwork making thing easy for us.

If IMEI is on EFS, yes it will do that but TWRP also has EFS backup/restore.

This tool will do absolutely every partition, there is literally nothing else on the storage that needs to be backed up. Only thing it can't do is repartition device, that has to be done manually (I have another thread about that).
 
  • Like
Reactions: cherryb8844

rubenswing

Senior Member
Mar 28, 2008
389
72
26.8500° N, 80.9200° E
Oh derp to me; of course locked bootloader can't access fastboot at all can it! Shows how experienced I am with locked devices :p thanks - updated thread with statement of unlocked BL requirement.

Re: Your crash, I realized right away that that is very likely because the program path has spaces in it. I fixed that now, just download the tool again and it should work. If not though, there is now a _debug tool that will show you the error instead of instantly closing. But I'm 90% sure that the problem you had is now fixed.

Yep it's working very much now as expected and a big thank you :good: I now could backup up all the partitions on my device :)
 
  • Like
Reactions: CosmicDan

ekistece

Member
Mar 12, 2018
38
12
flash_factory.bat

Which are the files that are nuked when you do a flash_factory? I know modemst1, modemst2 and persist are the important ones that are mentioned in the threads. There's any other data you should backup? I see there's a lot more partitions other than the usual ones, they hold irrecoverable data too? Also I'have seen that to recover IMEI people use a qualcomm tool, do you need that process or you can just flash modemst1 and modemst2 to recover IMEI?
 

CosmicDan

Senior Member
Jun 19, 2009
5,890
7,736
34
Sydney
Google Pixel 3 XL
Xiaomi Poco X3 Pro
Which are the files that are nuked when you do a flash_factory? I know modemst1, modemst2 and persist are the important ones that are mentioned in the threads. There's any other data you should backup? I see there's a lot more partitions other than the usual ones, they hold irrecoverable data too? Also I'have seen that to recover IMEI people use a qualcomm tool, do you need that process or you can just flash modemst1 and modemst2 to recover IMEI?

Check the factory_flash.bat, it flashes everything. Also the rawpartition0.xml (which is used in edl mode, factory_flash.bat is only for fastboot mode). So backup everything.

I don't know where Imei is stores, so just backup everything.

Qualcomm tool IMEI recovery is for injecting IMEI into existing partition somewhere. Not necessary if you already have full IMG backups.
 

thepandas

Member
Jan 12, 2018
47
35
Noob Questions :confused:

1. Ok, so consider i have used your tool and worked as intended. so currently the Phone will be in 'edl mode' how can i reboot it back to system (i guess fastboot commands wont work in edl mode).


2. After creating backup, How should i restore partions ?...
using twrp or CMD....?
(Does Tool backup Partitions as img or zip file....?)

3. Does this tool allows user to restore partition individually or one has restore all the backup data as a whole (i.e all backup partions)

Thanks again for the amazing tool :angel: :good:
 
  • Like
Reactions: pooniaprashant

CosmicDan

Senior Member
Jun 19, 2009
5,890
7,736
34
Sydney
Google Pixel 3 XL
Xiaomi Poco X3 Pro
Noob Questions :confused:

1. Ok, so consider i have used your tool and worked as intended. so currently the Phone will be in 'edl mode' how can i reboot it back to system (i guess fastboot commands wont work in edl mode).


2. After creating backup, How should i restore partions ?...
using twrp or CMD....?
(Does Tool backup Partitions as img or zip file....?)

3. Does this tool allows user to restore partition individually or one has restore all the backup data as a whole (i.e all backup partions)

Thanks again for the amazing tool :angel: :good:

1) Hold power button for 10+ seconds to reboot

2) You restore them with the same tool, there is a restore option in the menu, it's right there ?

3) The restore will restore everything listed in rawpartitions0.xml inside the IMG backup folder. If you want to exclude some partitions in restore, delete the corresponding XML line. This is already explained in the OP.
 

SmallTarzan

Senior Member
Nov 28, 2014
244
127
Bratislava
Great job. Was just wondering if is everything going well if is this error displayed in the log:
Code:
Version 2.15
PblHack: Error - 1836597052
Did not receive Sahara hello packet from device

!!!!!!!! WARNING: Flash programmer failed to load trying to continue !!!!!!!!!

Dumping data to file RR-FULL\system_b.img
Dumping at start sector: 0 for sectors: 0 to file: RR-FULL\system_b.img
.0" encoding="UTF-8" ?><data><log value="XML (0 bytes) not validated" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" /></data>
Programming device using SECTOR_SIZE=512

<?xml version = "1.0" ?><data><configure MemoryName="emmc" ZLPAwareHost="1" SkipStorageInit="0" SkipWrite="0" MaxPayloadSizeToTargetInBytes="16384"/></data>
<?xml version="1.0" encoding="UTF-8" ?><data><log value="[email protected] [email protected]" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="16384" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="8953" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="16384" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="8953" /></data>
Connected to flash programmer, starting dump
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="1" physical_partition_number="0" start_sector="1"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
Sectors remaining 1

Downloaded raw image at speed 30 KB/s
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 0" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="32" physical_partition_number="0" start_sector="2"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
Sectors remaining 32

Downloaded raw image at speed 16384 KB/s
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 0" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="6291456" physical_partition_number="0" start_sector="7477248"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
hRead = INVALID_HANDLE_VALUE, zeroing input buffer
Should I leave it and let it continue? Because it's been frozen for some time now.
 

rubenswing

Senior Member
Mar 28, 2008
389
72
26.8500° N, 80.9200° E
Great job. Was just wondering if is everything going well if is this error displayed in the log:
Code:
Version 2.15
PblHack: Error - 1836597052
Did not receive Sahara hello packet from device

!!!!!!!! WARNING: Flash programmer failed to load trying to continue !!!!!!!!!

Dumping data to file RR-FULL\system_b.img
Dumping at start sector: 0 for sectors: 0 to file: RR-FULL\system_b.img
.0" encoding="UTF-8" ?><data><log value="XML (0 bytes) not validated" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" /></data>
Programming device using SECTOR_SIZE=512

<?xml version = "1.0" ?><data><configure MemoryName="emmc" ZLPAwareHost="1" SkipStorageInit="0" SkipWrite="0" MaxPayloadSizeToTargetInBytes="16384"/></data>
<?xml version="1.0" encoding="UTF-8" ?><data><log value="[email protected] [email protected]" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="16384" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="8953" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="16384" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="8953" /></data>
Connected to flash programmer, starting dump
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="1" physical_partition_number="0" start_sector="1"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
Sectors remaining 1

Downloaded raw image at speed 30 KB/s
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 0" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="32" physical_partition_number="0" start_sector="2"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
Sectors remaining 32

Downloaded raw image at speed 16384 KB/s
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 0" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="6291456" physical_partition_number="0" start_sector="7477248"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
hRead = INVALID_HANDLE_VALUE, zeroing input buffer
Should I leave it and let it continue? Because it's been frozen for some time now.

At the very end of the log file does it give a status?
 

SmallTarzan

Senior Member
Nov 28, 2014
244
127
Bratislava
At the very end of the log file does it give a status?

No, it doesn't.
Code:
Sectors remaining 1792
Sectors remaining 1760
Sectors remaining 1728
Sectors remaining 1696
Sectors remaining 1664
Sectors remaining 1632
Sectors remaining 1600
Sectors remaining 1568
Sectors remaining 1536
Sectors remaining 1504
Sectors remaining 1472
Sectors remaining 1440
Sectors remaining 1408
Sectors remaining 1376
Sectors remaining 1344
Sectors remaining 1312
Sectors remaining 1280
Sectors remaining 1248
Sectors remaining 1216
Sectors remaining 1184
Sectors remaining 1152
Sectors remaining 1120
Sectors remaining 1088
Sectors remaining 105

It's been stuck at this for like 30 minutes now, I've closed it.
 

rubenswing

Senior Member
Mar 28, 2008
389
72
26.8500° N, 80.9200° E
No, it doesn't.
Code:
Sectors remaining 1792
Sectors remaining 1760
Sectors remaining 1728
Sectors remaining 1696
Sectors remaining 1664
Sectors remaining 1632
Sectors remaining 1600
Sectors remaining 1568
Sectors remaining 1536
Sectors remaining 1504
Sectors remaining 1472
Sectors remaining 1440
Sectors remaining 1408
Sectors remaining 1376
Sectors remaining 1344
Sectors remaining 1312
Sectors remaining 1280
Sectors remaining 1248
Sectors remaining 1216
Sectors remaining 1184
Sectors remaining 1152
Sectors remaining 1120
Sectors remaining 1088
Sectors remaining 105

It's been stuck at this for like 30 minutes now, I've closed it.
Could you upload the log file
 

CosmicDan

Senior Member
Jun 19, 2009
5,890
7,736
34
Sydney
Google Pixel 3 XL
Xiaomi Poco X3 Pro
You need a better USB cable or try a different port.

It will report success if it finishes OK. But that is a communication error when it freezes.

Also reboot EDL mode. And keep the window active, don't go play a game while it's doing stuff :p
 

SmallTarzan

Senior Member
Nov 28, 2014
244
127
Bratislava
You need a better USB cable or try a different port.

It will report success if it finishes OK. But that is a communication error when it freezes.

Also reboot EDL mode. And keep the window active, don't go play a game while it's doing stuff :p

I am using an USB-C cable I bought from a shop the other day, and I was in the EDL mode. I wasn't playing a game during the backup either!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 49
    What?

    A Windows (only) toolkit for making full backup/restore of all Mi A1 partitions to/from your PC.

    • Utilizes EMMCDL in Qualcomm EDL mode - only needs fastboot access (unlocked BL) or testpoint (for bricked devices, maybe locked ones too - not sure)
    • Backups create a rawprogram0.xml file which could also be restorable in MiFlash if you choose (untested - not part of toolkit goal).
    • See FAQ at bottom for details about how to use EDL mode.

    --------------------------------

    Why?

    Mainly to...

    • ...backup all your hidden/system partitions that TWRP cannot (e.g. persist) to keep them safe.
    • ...recover your device in the event of a brick

    --------------------------------

    How?

    Requirements

    • Windows PC ONLY
    • Qualcomm EDL drivers (can get them from here, among other places)
    • Fastboot access working with driver (generic binary and driver work fine, it's all over the place
    • If you're firm-bricked (stuck in Diagnostic mode) you need to disassemble and bridge the test-points to kick it out of diagnostic mode - but that's beyond the scope of this thread/tool.

    Setup

    1. Download the latest version from GitHub (link at bottom) and extract
    2. Connect your device with a quality USB-C cable (original worked well). Some cheap cables, or USB2 > USB-C adapters can cause the process to fail.
    3. Boot into fastboot and run the command...
      Code:
      fastboot oem edl
      ...you may see an error, that's normal. Device should now have blank screen and a white flashing light.
    4. Install the QDLoader driver. You may see this in device manager if you've not installed it yet...
      [Link because XDA forum keeps breaking my IMG tags whenever I edit]
      ...just right click > properties > update driver, the usual thing (if you downloaded the smaller driver pack ZIP from above). Then it should look like this...
      [Link because XDA forum keeps breaking my IMG tags whenever I edit]
    5. If your COM port in device manager (see above) is not COM30, you need to-
      1. Edit the config.ini in the toolkit folder
      2. Replace com30 with whatever your port is
    6. Now you're ready to use the tool.

    Usage

    The toolkit is pretty self-explanatory. But first you need to select which partitions you want to backup with option 1. Two partition lists are already included:

    • partition_list.all.txt - this list selects all partitions that exist on the Mi A1. Note that backing up system(_a/_b) and especially userdata will take a VERY LONG TIME. Also note that the backup images are NOT compressed; so expect to have 32GB space free for example (if you have a 32GB device).
    • partition_list.skip-systems-and-userdata.txt - this will backup all partitions except system(_a/_b) and userdata. More useful, since we backup system and userdata in TWRP anyway. All the other firmware partitions come to only about 500MB.
    Once you select the list you want to use, you can run the backup with 2 - just enter a folder name and it'll go there.

    Restore does not require a partition list to be loaded; since the partition table is stored inside the backup as rawpartition0.xml. You can manually edit this file if you want to selectively restore partitions - just delete the whole line of partitions you don't want to restore. Note that changing any of these values will NOT repartition the device - you'll only corrupt your partition table if you do this.

    Well I guess that's it, I will update this guide after feedback (it's a bit rough, I am kind of rushing lol).

    --------------------------------

    Where?


    Download the latest version on GitHub:
    https://github.com/CosmicDan-Android/MiA1LowLevelBackupRestoreTool
    ... simply press the green 'Clone or download' button on the right, then 'Download ZIP'.

    --------------------------------

    Who?

    • Special thanks to @emuzychenko for his batch script wizardry which this is mostly based on. You can see his original tool and scripts here. I just re-wrote it all to be more user friendly and convenient for me and others.

    --------------------------------

    History



    2018-05-23

    • Added config option to change transfer speed (reducing may help with freezes)

    2018-05-15


    • Fixed crashing when path containing tool has spaces
    • Added a "debug mode" that won't instantly close the Window in event of a hard crash (why oh why did I ever use Batch again...)
    • Added a "persist-only" partition list
    2018-05-14

    • Initial version


    --------------------------------

    FAQ

    Q) EDL mode? Eh?
    A) EDL mode, or "Emergency DownLoad" mode, is a low-level mode for flashing devices. It is entered by the command:
    Code:
    fastboot oem edl
    EDL mode is used to read/write to the eMMC more directly. It is used by this tool, as well as flashing with MiFlash.
    Other important notes:
    • You will need good QDLoader drivers. These drivers gave me the best results.
    • You can exit EDL mode by holding Power button for ~10 seconds. Hold with VolDn to reboot into fastboot again, as one might expect.
    • Make sure you use a good USB-C cable.
    • Sometimes the flashing process can freeze. It will always report success when done. If it freezes, you need to reboot EDL mode. Try a different USB port or cable if you keep experiencing freezes.


    Q) I get a freeze or hang when trying backup/restore partitions
    A) First, make sure it's actually frozen. Open log.txt in the tool folder, and then open it again to see if it's changed.

    If not, make sure you're using the driver linked in this post, as it proved to be most reliable by myself and others. You can also try these things (recommended in this order):

    • Reboot to EDL mode again;
    • Use a different (better) cable;
    • Use a different USB port;
    • Reduce the transfer speed in config.ini (be sure to read the comments)
    • Use a different PC;

    Of course all are welcome to post their questions/suggestions and so on. Happy flashing!
    4
    Noob Questions :confused:

    1. Ok, so consider i have used your tool and worked as intended. so currently the Phone will be in 'edl mode' how can i reboot it back to system (i guess fastboot commands wont work in edl mode).


    2. After creating backup, How should i restore partions ?...
    using twrp or CMD....?
    (Does Tool backup Partitions as img or zip file....?)

    3. Does this tool allows user to restore partition individually or one has restore all the backup data as a whole (i.e all backup partions)

    Thanks again for the amazing tool :angel: :good:

    1) Hold power button for 10+ seconds to reboot

    2) You restore them with the same tool, there is a restore option in the menu, it's right there ?

    3) The restore will restore everything listed in rawpartitions0.xml inside the IMG backup folder. If you want to exclude some partitions in restore, delete the corresponding XML line. This is already explained in the OP.
    2
    thx . just now . lowbackup has done . only several minutes . sorry for my english .
    2
    The tool hangs everytime, no matter how I do my setup.
    Stock cable, port changed to COM10 according to my Device Manager(W10 64bit), no spaces or anything in the directory, even tried giving Administrator Privileges to the batch file.
    Nothing works, it hangs mid of backuping modem_a or modem_b
    Here are some logs.
    I live in South Korea, so my laptop's Windows language is Korean. Can it be a cause of the problem?

    <edit>
    Okay, I think I found the answer myself.
    1. You must reenter EDL mode everytime you fail to try another attempt.
    2. [IMPORTANT] Please update EDL driver to the one provided in the OP. Somehow I already had a driver, but it must have been a faulty one. Updating driver solved the problem.

    Thanks to the developers! Now I'm going to use Treblizer~
    1
    First of all it doesn't work for me with a locked bootloader, I had to unlock the bootloader and followed the instructions, after opening the program and selecting any option in the tool simply closes the window and nothing happens. I tried it 4 times but no use, it just closes the command prompt window

    Oh derp to me; of course locked bootloader can't access fastboot at all can it! Shows how experienced I am with locked devices :p thanks - updated thread with statement of unlocked BL requirement.

    Re: Your crash, I realized right away that that is very likely because the program path has spaces in it. I fixed that now, just download the tool again and it should work. If not though, there is now a _debug tool that will show you the error instead of instantly closing. But I'm 90% sure that the problem you had is now fixed.