Ask about the subfolders exist in the edl mode thread - ZTE Axon 7 Questions & Answers

Hi everyone , sorry for my lot questions , am still not familiar with , this is my first experience with things like that , the edl tool is so helpful and i found many people recommended it so i will unloack my bootloader after downgrading from oreo to naugat and then upgrad and flash twrp , Then format and boot into B02 and then flash LOS 16 but i want to ask please here about the subfolders ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// Structure of program folders:
1. Folder flash - in this folder you need to copy the files you want to flash
Subfolders:
folder full - if you want to flash full firmware (official, adapted for EDL mode), then in this folder you need to put all the files from the firmware for EDL mode:
its name usually looks like this: A2017 _......._ FULL_EDL
folder boot - if you want to flash your kernel file, you need to put a file named: boot.img in this folder (the file name must be exactly that!)
folder recovery - if you want to flash your recovery file, you need to put a file named: recovery.img in this folder (the file name must be exactly that!)
folder modem - if you want to flash your modem file, you need to put a file named: NON-HLOS.bin in this folder (the file name must be exactly that!)
folder splash - if you want to flash your splash file, you need to put a file named: splash.img in this folder (the file name must be exactly that!)
2. Folder backup - the folder contains backup copies of the phone partitions created by the program
Subfolders:
folder all - this folder contains backups of all partitions, except userdata
folder full - this folder contains backup of all partitions included in the FULL EDL firmware
folder boot - this folder contains a backup of the boot partition
folder recovery - this folder contains a backup of the recovery partition
folder modem - this folder contains a backup of the modem partition
folder splash - this folder contains a backup of the splash partition
folder efs - this folder contains backup of the efs partition
3. Folder unlock - contains all the necessary files to unlock (do not touch it!)
4. Folder logs - contains all the logs of the program
5. Folder tools - contains all the necessary files for the program (do not touch it!) ---------------------->My question here about the subfolders should i just make the twrp recommended in the folder recovery and the two roms b 02 and b 12 in the folder flash or all the folders i should make in them some files ( folder backup , folder boot , folder modem , folder splash, folder unloack , folder logs ,foler tools ) if yes tell me what i should put in those folder exactly .am in a mess . thanks and please help me

1. twrp goes into folder recovery - named: recovery.img - flash
2. boot into twrp, install ROM zips from there
or
put B02 into folder full - A2017 _......._ FULL_EDL and flash
reboot
install LOS from TWRP

Related

[GUIDE] How to extract system files from stock firmware

First of all: Tool to be used in this guide was developed by user And_pda from Russian 4pda.ru forum. So all credits must go to And_pda
The original thread (in Russian) is here. Actually the original thread is about several tools to works with different images for different phones. But we will talk only about Moto X.
The guide will describe how to extract all files from system partition from stock firmware. The tools works under Windows (I personally tested it on Win 7).
If you unzip any stock firmware (for instance ROGERS-CA_GHOST_KXA20.16-1.26_cid14_CFC_1FF.xml.zip) you will find one file, which represents system partition: system.img.
To extract all files from system.img please do:
1. Download ImgExtractor_1_3_4.rar and extract it.
2. Create directory System in the folder where system.img is located;
3. Copy ImgExtractor.exe into the folder where system.img is located;
4. Run CMD and "cd" to the folder where system.img is located
5. In CMD run the following: ImgExtractor system.img System
After ImgExtractor finished you will have all system files and folders in System directory.
That's all
PS. ImgExtractor also can extract modem firmware (NON-HLOS.bin)

Creating a Flashable zip problem

Hi I created a bootanimation and want to make it flashable. I followed tutorials from the net and xda. I got two files META-INF and system.
I put my bootanimation.zip in system/media. That's all. I didn't touch META-INF .
After flashing the zip in cwm, it says Installation aborted . Need Help please...
thats because the flashable zip wasnt for your phone
status 0 - wrong update binary
status 6 - wrong update script
here is my template for you
simply download it
open it in winrar (or if using phone just unzip everything)
open the system foler
you will notice a framework folder that is currently empty
you can leave this folder as it is
just create folders to where you want to flash the file to
for example your bootanimation.zip create the following
in the system folder create a folder called media
in the media folder place your bootanimation.zip
the same is true for any other files you want to flash
if you want to flash a file to system/framework just put a file in that folder
if you want to flash a file to system/app just create a folder called app in the system folder and put what you want to flash there
if on winrar you just have to open the zip and right click and create a folder - no need to unzip everything
if on phone and you have unzipped everything just zip everything back up when done
flashable zip template can be download from here
if you are using stock rom you need to enable custom boot animations first using the custom boot enabler zip
(if you already have a custom boot animation and bootanimation.zip working in a custom rom then you dont need to do this)
Ovafloa_X said:
Hi I created a bootanimation and want to make it flashable. I followed tutorials from the net and xda. I got two files META-INF and system.
I put my bootanimation.zip in system/media. That's all. I didn't touch META-INF .
After flashing the zip in cwm, it says Installation aborted . Need Help please...
Click to expand...
Click to collapse
If just a bootanimanion, push using root browser only
Or using a another flashable bootanimation file and the replace the bootanimation.zip with yours
I attch it . Credits to its maker
works perfectly! thanks

[GUIDE] How to extract system files from stock firmware on Windows

First of all: Tools to be used in this guide were developed by user And_pda from Russian 4pda.ru forum. So all credits must go for And_pda.
The original thread (in Russian) is here. Actually the original thread is about several tools to works with different images for different phones. But we will talk only about Moto X 2014.
The guide will describe how to extract all files from system partition from stock firmware. The tools works under Windows (I personally tested them on Win 7).
As an example we will use FXZ for Brazilian firmware RETBR_XT1097_4.4.4_KXE21.187-30.3_cid12_CFC.xml.zip - the only full firmware available at the moment.
If you unzip stock firmware you will get 5 files, which represents system partition: system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, system.img_sparsechunk.3 and system.img_sparsechunk.4.
There are two steps to be performed to get system file extracted.
Step 1 - it will convert 5 files (system.img_sparsechunk.0, 1, 2, 3, 4) into temporary file system_motoX2.img:
1. Download Sparse-to-Img.zip and extract it.
Lets assume that it is extracted to C:\Sparse-to-Img. If not you have to modify ConvertMotoX2.bat file.
You have to edit the string set wf=C:\Sparse-to-Img\Cygwin\ according to path where you extracted archive.
2. Copy ConvertMotoX2.bat to the folder where stock firmware is unzipped (i.e. where system.img_sparsechunk.0, 1, 2, 3, 4 are located)
3. Run CMD and "cd" to the folder where where stock firmware is unzipped
4. In CMD run ConvertMotoX2.bat. File system_motoX2.img will be created.
Step 2 - it will extract all files and folders from system_motoX2.img:
1. Download ImgExtractor.zip and extract it.
2. Create directory System in the folder where system_motoX2.img is located;
3. Copy ImgExtractor.exe into the folder where system_motoX2.img is located;
4. Run CMD and "cd" to the folder where system_motoX2.img is located
5. In CMD run the following: ImgExtractor system_motoX2.img System
After ImgExtractor finished you will have all system files and folders in System directory.
That's all
PS. ImgExtractor also can extract files from modem firmware (i.e. form NON-HLOS.bin)
So, this can be done to manualy re-lock bootloader, right? I quoted the steps needed to get .img that would be use to flash using fastboot and before fastboot lock, right? If I'm wrong let me know and I'll delete this post, so it doens't confuses anyone.
Al936 said:
Brazilian firmware RETBR_XT1097_4.4.4_KXE21.187-30.3_cid12_CFC.xml.zip
If you unzip stock firmware you will get 5 files, which represents system partition: system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, system.img_sparsechunk.3 and system.img_sparsechunk.4.
Step 1 - it will convert 5 files (system.img_sparsechunk.0, 1, 2, 3, 4) into temporary file system_motoX2.img:
1. Download Sparse-to-Img.zip and extract it.
Lets assume that it is extracted to C:\Sparse-to-Img. If not you have to modify ConvertMotoX2.bat file.
You have to edit the string set wf=C:\Sparse-to-Img\Cygwin\ according to path where you extracted archive.
2. Copy ConvertMotoX2.bat to the folder where stock firmware is unzipped (i.e. where system.img_sparsechunk.0, 1, 2, 3, 4 are located)
3. Run CMD and "cd" to the folder where where stock firmware is unzipped
4. In CMD run ConvertMotoX2.bat. File system_motoX2.img will be created.
Click to expand...
Click to collapse
Thanks,
Nochnoy said:
So, this can be done to manualy re-lock bootloader, right? I quoted the steps needed to get .img that would be use to flash using fastboot and before fastboot lock, right? If I'm wrong let me know and I'll delete this post, so it doens't confuses anyone.
Thanks,
Click to expand...
Click to collapse
I am sure that flashing temporary file system_motoX2.img will not allow you to manually re-lock bootloader. And I do not recommend to flash it.
wow, Great!
Al936 said:
First of all: Tools to be used in this guide were developed by user And_pda from Russian 4pda.ru forum. So all credits must go for And_pda.
The original thread (in Russian) is here. Actually the original thread is about several tools to works with different images for different phones. But we will talk only about Moto X 2014.
The guide will describe how to extract all files from system partition from stock firmware. The tools works under Windows (I personally tested them on Win 7).
As an example we will use FXZ for Brazilian firmware RETBR_XT1097_4.4.4_KXE21.187-30.3_cid12_CFC.xml.zip - the only full firmware available at the moment.
If you unzip stock firmware you will get 5 files, which represents system partition: system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, system.img_sparsechunk.3 and system.img_sparsechunk.4.
There are two steps to be performed to get system file extracted.
Step 1 - it will convert 5 files (system.img_sparsechunk.0, 1, 2, 3, 4) into temporary file system_motoX2.img:
1. Download Sparse-to-Img.zip and extract it.
Lets assume that it is extracted to C:\Sparse-to-Img. If not you have to modify ConvertMotoX2.bat file.
You have to edit the string set wf=C:\Sparse-to-Img\Cygwin\ according to path where you extracted archive.
2. Copy ConvertMotoX2.bat to the folder where stock firmware is unzipped (i.e. where system.img_sparsechunk.0, 1, 2, 3, 4 are located)
3. Run CMD and "cd" to the folder where where stock firmware is unzipped
4. In CMD run ConvertMotoX2.bat. File system_motoX2.img will be created.
Step 2 - it will extract all files and folders from system_motoX2.img:
1. Download ImgExtractor.zip and extract it.
2. Create directory System in the folder where system_motoX2.img is located;
3. Copy ImgExtractor.exe into the folder where system_motoX2.img is located;
4. Run CMD and "cd" to the folder where system_motoX2.img is located
5. In CMD run the following: ImgExtractor system_motoX2.img System
After ImgExtractor finished you will have all system files and folders in System directory.
That's all
PS. ImgExtractor also can extract files from modem firmware (i.e. form NON-HLOS.bin)
Click to expand...
Click to collapse
functionally perfect in extraction system, of moto maxx (XT1225) thanks :good:

7.19.401.2 Data / Preload files

Heres a flashable zip built from the new Lollipop OTA containing the required Data / Preload files which get deleted when you unlock the bootloader, these work if you are on 6.09.401.11 and possibly 6.09.401.12 and are required to update successfully.
Copy zip to your internal storage and boot into TWRP recovery, flash like you would with anything else, reboot the phone, then boot to fastbootUSB and flash your stock recovery, you should now beable to update.
The zip can be edited and the files in the preload folder can be replaced with your own if you are not on the 401 international RUU, you can find your own files inside your OTA.zip/data/preload, just copy it to your PC, extract the contents of that preload folder found in the ota and replace the files in my flashable zip, save, copy to insternal storage, and then flash as per above instructions.
https://www.androidfilehost.com/?fid=95916177934535033
Hit the thanks button if this helped you. :good:

Question about creating TWRP flashable file

Hey all, I've looked all over an can't find the answer to this... I have a NAND backup I made using TWRP, however, I had the problem many have had with getting errors when trying to restore it. So I thought I'd try a different way by creating a TWRP flashable file from the NAND files. I have taken the files from the backup and extracted them using CYGWIN. I read a thread here:
https://forum.xda-developers.com/showthread.php?t=2746044
But I'm stuck on a couple of things... First, the part about using the META-INF folder from another ROM... I've checked the files in in the META-INF folder and notice that the updater-script is what loads the files and directories. But none of the META-INF files I have found matches my backup files.
The files I want to flash are the complete system folder, complete data folder and the boot.img file. Is it possibly to flash these with TWRP without the META-INF folder/files? If I have to use the META-INF how do I make sure all the files and folders are flashed?
Would it be better to create an ODIN flashable file and just use Odin to do the flash? If so should I put the system and data folders into one file and then use the boot.img (or would I put the boot.img finle into a tar) in the Bootloader spot in Odin?
Thanks in advance.

Categories

Resources