Axon 10 EDL Tool
BAT-program for Flash / Backup / Restore/ Bootloader Unlock
Qualcomm HS-USB QDLoader 9008 (COM ...)
!!! Whatever you do, you do at your own risk !!!"
!!! If you are not sure of yourself do not use this program !!!
Special requirements (read first) !!!
1. The program must be unpacked
2. Before using the program, make sure that:
- It is desirable to copy the program to the root of the disc, for example: C:\Axon10_EDL_Tool\ or D:\Axon10_EDL_Tool
- You launched this program as administrator
- You have drivers installed, preferably original for Axon 10
3. Read carefully what the program displays on the screen (I specially wrote the tips, the information is very useful, many questions disappear)
Features of the program:
1. Automatically reboot the phone into EDL mode
2. Unlock the bootloader for supported variants only
3. Finds the connected phone and forces the COM-port speed to 115200
4. Can flash , backup, restore
5. Analyzes folders for missing required files
6. and others ...)))
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: A2020 _......._ 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 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
3. Folder logs - contains all the logs of the program
4. Folder tools - contains all the necessary files for the program (do not touch it!)
Screenshots
View attachment 4422222 View attachment 4422148 View attachment 4422149 View attachment 4422150
View attachment 4422151 View attachment 4422152 View attachment 4422153 View attachment 4422154
View attachment 4422155 View attachment 4422156 View attachment 4422157 View attachment 4422158
View attachment 4422159 View attachment 4422160 View attachment 4422163 View attachment 4422165
View attachment 4422161 View attachment 4422162
For those who still do not understand how to flash (FAQ):
Question: I want to flash the full firmware for EDL mode, how to do this ???
Answer: Download and unzip the full firmware for EDL mode, for example A2017_B17_NOUGAT_FULL_EDL and put all its files in the folder Axon10_EDL_Tool\flash\full\. Run the program Axon10_EDL_Tool.bat and select the Flash -> Flash FULL EDL
Question: I want to flash a patched or original boot, how to do this ???
Answer: Download the boot you need, rename it to boot.img and place it in the folder Axon10_EDL_Tool\flash\boot\. Run the program Axon10_EDL_Tool.bat and select Flash -> Flash Boot
Question: I want to flash the modem, how to do this ???
Answer: Download or take the NON-HLOS.bin file from firmware and put it in the folder Axon10_EDL_Tool\flash\modem\. Run the program Axon10_EDL_Tool.bat and select Flash -> Flash Modem
!!! Download !!!
Axon 10 EDL Tool 3.2.5
Thanks !!!
[mention]djkuz[/mention] for his Axon7 EDL Tool
Reserved
Update!! The latest version can now automate unlocking the bootloader
yes cool and mega performance there is the Axon 10 but still cracked before my birthday
Thx :good:
Little Progress, Running Android 10 GSI (ARM64+GMS gsi_gms_arm64-QP1A.190771.020-5800535.zip )
if i want change chinese rom to global rom, i just put eu firmware into flash folder?
undergram said:
if i want change chinese rom to global rom, i just put eu firmware into flash folder?
Click to expand...
Click to collapse
Make sure you keep your modem if that makes a difference for your region.
Sent from my G8142 using Tapatalk
@Unjustified Dev
So this tool will not work on the A2020N2 Chinese 5G phone? If not is there a manual unlock BL process?
Thanks
EMS
@Unjustified Dev
I have the problem that you can make backup all partitions with the edl tool.
but if I select all partitions with the edl tool Restore All partitions I get an error
@Unjustified Dev
I believe in the two files (all.xml and full.xml) are errors in it
in the all.xml
missing z.b at last_parti each of the sectore
(Num_partition_sectors = "0")
and the size
(= Size_in_KB "0")
<!--program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="last_parti1.bin" label="last_parti" num_partition_sectors="0" partofsingleimage="false" physical_partition_number="1" readbackverify="false" size_in_KB="0" sparse="false" start_byte_hex="0x3a6000" start_sector="934"/ -->
<!--program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="last_parti2.bin" label="last_parti" num_partition_sectors="0" partofsingleimage="false" physical_partition_number="2" readbackverify="false" size_in_KB="0" sparse="false" start_byte_hex="0x3a6000" start_sector="934"/ -->
<!--program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="last_parti3" label="last_parti" num_partition_sectors="0" partofsingleimage="false" physical_partition_number="3" readbackverify="false" size_in_KB="0" sparse="false" start_byte_hex="0x140000" start_sector="320"/ -->
<!--program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="last_parti4.bin" label="last_parti" num_partition_sectors="0" partofsingleimage="false" physical_partition_number="4" readbackverify="false" size_in_KB="0" sparse="false" start_byte_hex="0x295767000" start_sector="2709351"/ -->
<!--program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="last_parti5" label="last_parti" num_partition_sectors="0" partofsingleimage="false" physical_partition_number="5" readbackverify="false" size_in_KB="0" sparse="false" start_byte_hex="0x6c0000" start_sector="1728"/ -->
I once looked at the all.xml from the a7
(<program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="last_parti5.bin" label="last_parti" num_partition_sectors="884" partofsingleimage="false" physical_partition_number="5" readbackverify="false" size_in_KB="3536.00" sparse="false" start_byte_hex="0x2487000" start_sector="9351"/>)
Chris axon 7 said:
@Unjustified Dev
I believe in the two files (all.xml and full.xml) are errors in it
in the all.xml
missing z.b at last_parti each of the sectore
(Num_partition_sectors = "0")
and the size
(= Size_in_KB "0")
<!--program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="last_parti1.bin" label="last_parti" num_partition_sectors="0" partofsingleimage="false" physical_partition_number="1" readbackverify="false" size_in_KB="0" sparse="false" start_byte_hex="0x3a6000" start_sector="934"/ -->
<!--program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="last_parti2.bin" label="last_parti" num_partition_sectors="0" partofsingleimage="false" physical_partition_number="2" readbackverify="false" size_in_KB="0" sparse="false" start_byte_hex="0x3a6000" start_sector="934"/ -->
<!--program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="last_parti3" label="last_parti" num_partition_sectors="0" partofsingleimage="false" physical_partition_number="3" readbackverify="false" size_in_KB="0" sparse="false" start_byte_hex="0x140000" start_sector="320"/ -->
<!--program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="last_parti4.bin" label="last_parti" num_partition_sectors="0" partofsingleimage="false" physical_partition_number="4" readbackverify="false" size_in_KB="0" sparse="false" start_byte_hex="0x295767000" start_sector="2709351"/ -->
<!--program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="last_parti5" label="last_parti" num_partition_sectors="0" partofsingleimage="false" physical_partition_number="5" readbackverify="false" size_in_KB="0" sparse="false" start_byte_hex="0x6c0000" start_sector="1728"/ -->
I once looked at the all.xml from the a7
(<program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="last_parti5.bin" label="last_parti" num_partition_sectors="884" partofsingleimage="false" physical_partition_number="5" readbackverify="false" size_in_KB="3536.00" sparse="false" start_byte_hex="0x2487000" start_sector="9351"/>)
Click to expand...
Click to collapse
It's commented out the allow the backup to complete but I don't support flashing all just yet. Just use full that's sufficient enough to fix any brick. If you need all, then you did something horribly wrong to the phone.
@Unjustified Dev
Hi,
Thanks for this tool. I need help with this error however
When I flashing full firmware, the program displaying on the screen:
!!! Not found important files, or detected SPARSE image !!!
The log file shows
ERROR: D:\Axon10_EDL_TOOL_v3.2.5\flash\full\userdata.img - SPARSE image!!!
ERROR: D:\Axon10_EDL_TOOL_v3.2.5\flash\full\vendor.img - SPARSE image!!!
ERROR: D:\Axon10_EDL_TOOL_v3.2.5\flash\full\system.img - SPARSE image!!!
ERROR: D:\Axon10_EDL_TOOL_v3.2.5\flash\full\system_other.img - SPARSE image!!!
The fireware downloaded here
https://forum.xda-developers.com/axon-10-pro/how-to/firmware-zte-axon-10-pro-ch-eu-edl-sd-t3934664
A2020G / Axon 10 Pro EU 1.3 EDL Software、P855A01V1.0.0B16_DL.zip
Many thanks
@Unjustified Dev
Hi,
Thanks for this tool. I need help with this error however
When I flashing full firmware, the program displaying on the screen:
!!! Not found important files, or detected SPARSE image !!!
The log file shows
ERROR: D:\Axon10_EDL_TOOL_v3.2.5\flash\full\userdata.img - SPARSE image!!!
ERROR: D:\Axon10_EDL_TOOL_v3.2.5\flash\full\vendor.img - SPARSE image!!!
ERROR: D:\Axon10_EDL_TOOL_v3.2.5\flash\full\system.img - SPARSE image!!!
ERROR: D:\Axon10_EDL_TOOL_v3.2.5\flash\full\system_other.img - SPARSE image!!!
The fireware downloaded here
https://forum.xda-developers.com/axon-10-pro/how-to/firmware-zte-axon-10-pro-ch-eu-edl-sd-t3934664
A2020G / Axon 10 Pro EU 1.3 EDL Software、P855A01V1.0.0B16_DL.zip
Many thanks
Did you read post 11?
you may try this version (russia) without any garanty:
https://4pda.ru/forum/index.php?showtopic=965431&view=findpost&p=88768840
@borisku
I have used the russia version 1.0,now my phone brick.What should I do :crying::crying::crying:
peter_0115 said:
@borisku
I have used the russia version 1.0,now my phone brick.What should I do :crying::crying::crying:
Click to expand...
Click to collapse
Download the correct firmware and use miflash
Sent from my G8142 using Tapatalk
Unjustified Dev said:
Download the correct firmware and use miflash
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
Could you tell me more? What's the correct fw?Where can I download it? My phone is China version.
Thanks a lot!
peter_0115 said:
Could you tell me more? What's the correct fw?Where can I download it? My phone is China version.
Thanks a lot!
Click to expand...
Click to collapse
China version of Axon10 have another partition table. You need edl firmware for china and edl tool for china.
Try...
https://forum.xda-developers.com/showpost.php?p=80316365&postcount=41
@djkuz
How can I help with translation?
I can help with English / Spanish
DrakenFX said:
@djkuz
How can I help with translation?
I can help with English / Spanish
Click to expand...
Click to collapse
Thank you friend! don’t worry, I already have an almost complete translation. as soon as I do, I’ll upload it here right away!
Related
Hi All,
Is there anyone busy with a custom ROM for the AC Ryan VEOLO?
A rom with Android 2.3 instead of would already be great. This would make it capable of running XBMC for android.
That could make it a great device!
Let's even hope we get Android 4.0.3 ICS. The mediaplayer division of Huawei made released a new player at the end of August based on the same Hi3716C CPU as the Veolo, the Himedia Q5. The latest firmware is available here : http://v.himedia-tech.cn/Q5/102/update.zip
Some ROM experts around who could help ?
A way to install the firmware you mention woud also be great!
Sorry, don't know how to flash, because some .img files have different sizes compared to the Veolo firmware, so I suppose the nand flash needs to be repartitioned. Also, there is no update_app.zip file, and there are more .img files in the update.zip than in the original firmware.
That's why I asked if some experts know how to do it. If so, I would be happy to try
jefke2 said:
Sorry, don't know how to flash, because some .img files have different sizes compared to the Veolo firmware, so I suppose the nand flash needs to be repartitioned. Also, there is no update_app.zip file, and there are more .img files in the update.zip than in the original firmware.
That's why I asked if some experts know how to do it. If so, I would be happy to try
Click to expand...
Click to collapse
Any news about this question?
There must be a people out there that could help us
Veolo
Hi ,
I was wondering is anybody on to this .
Is there anybody who is trying to fix a recovery and a rom for us ?
I would really appreciete this .
Or someone who can guide me in the right direction on how to do this on my own .
Thanks anyway .
Greetz Tim
Someone has managed to flash the Himedia Q5 ICS firmware on the Pearl Meteorit MMB 422 which is very similar to the Veolo : http://www.android-hilfe.de/pearl-meteorit-mmb-422-hdtv-forum/254851-toolbox-fuer-pearl-meteorit-mmb-422-hdtv-root-google-play-etc-12.html
I tried on the Veolo, but no luck Strange, because i can flash the Veolo with Meteorit MMB 422 firmware and back with no problems at all.
Hopefully someone can create a flashable package for the Veolo based on the Himedia Q5 firmware.
BTW, version 1.0.3 is available : http://v.himedia-tech.cn/Q5/103/update.zip
This firmware would be great because it has native DVD/BD ISO playback, and would also allow us to run XBMC ...
J.
Ac Ryan Veolo
That would be very great i really hope someone with some knowledge and experience can help us out .
I would be able to help with the development of the rom and i would to try compile it myself and test it on my own Veolo .
I just need some help in the right direction .
Someone can help me out please ?
Greetz Tim
Well, i have made a little recap of all godbox platform devices (of which the AC Ryan Veolo is also a clone) :
- AC Ryan Veolo, Android 2.2
- Pearl Meteorit MMB 422, Android 2.2 (info : http://www.pearl.de/a-PX1549-1600.shtml)
- Poppstar MS 40, Android 2.2 (info: http://www.poppstar.eu/poppstar-poppstar-ms40-1080p-android-media-adapter.html)
- Coolech Android Deluxe, Android 2.2 (info : http://en.coupoint.net/ but site seems to be down ATM)
- G-Mini Magicbox Atlas, Android 2.2 (info : http://www.g-mini.ru/products/27)
and then there's:
- Himedia Q5, Android 4.0.3 (info : http://www.himedia-tech.cn/product_show.php?id=37) => They have already published 2 ICS firmware versions, see links in posts above
- eGreat i10, Android 4.0.3 (no info on their website, but available from online shops)
We know the bootloader from the AC Ryan Veolo is not locked, because you can flash Meteorit and G-Mini firmware without any problem. Why can't the ICS firmware be flashed ? Maybe it has something to do with NAND partition sizes ?
My knowledge is really too limited to cook a ROM, but these devices are technically identical, so there's no reason it shouldn't work.
J.
Here's a link for the developers among us : http://blog.sina.com.cn/s/blog_602f87700100qfa1.html
Use Chrome 's built in translate function... It's about how to cook a ROM for the Hi3716C platform.
Good luck ... :good:
J.
http://acryan.com/sg/acr/support/ACR-VE91200/
Under the Other tab, it says Open Source code ? for VEOLO ?
veolo
guys, someone please help with custom Ics firmware for Veolo, there is no hope from the manufacturer...tx :angel:
Yet another update for the Himedia Q5 : http://v.himedia-tech.cn/Q5/104/update.zip
On the other hand, Poppstar has ICS firmware ready (originally released with Froyo), but it can't (yet) be flashed easily. Link: http://www.android-hilfe.de/4646864-post137.html
J.
And now it's russian company G-Mini that has ICS firmware ready for the Atlas (also identical to the Veolo) But as with Himedia and Poppstar firmware it can't be flashed without serial connection to the motherboard.
Any news about this ?
I have flashed the Poppstar MS-40 ICS firmware on the Veolo, using a CP2102 USB to TTL UART programmer. (you can get it here : http://www.android-hilfe.de/pearl-meteorit-mmb-422-hdtv-forum/366851-installationsanleitung-ics-update.html)
Everything was OK (smooth, remote control working great, etc.) I then wanted to try the Himedia firmware, so copied update.zip onto an SD card and started the update from the system settings menu. Everything went fine until the upgrade procedure stopped at the end. After waiting for 30 minutes, i pulled the power plug and tried to flash the Poppstar firmware again, but it failed. Apparently I now have bad NAND flash from 0x4a00000 up to 0x15000000 (the area where the system.img has to be written)
I tried this:
- modified the partition table (it's an XML file) and added the bad NAND flash area to the kernel partition and moved the system partition to 0x15000000. (other partitions modified as well)
- modified the bootargs.bin with these new partition locations and sizes, also modified kernel partition length.
I reflashed successfully but the Veolo does not boot, so does anyone know what i can try next ?
See XML partition table below, and modified bootargs.bin attached.
Code:
<?xml version="1.0" encoding="GB2312" ?>
<Partition_Info>
<Part Sel="1" PartitionName="fastboot" FlashType="Spi" FileSystem="None" Start="0" Length="448K" SelectFile="E:\Backup\acryan\acryan\fastboot-burn.bin" />
<Part Sel="1" PartitionName="bootargs" FlashType="Spi" FileSystem="None" Start="448K" Length="64K" SelectFile="E:\Backup\acryan\acryan\bootargs_mod.bin" />
<Part Sel="1" PartitionName="recovery" FlashType="Spi" FileSystem="None" Start="512k" Length="3520K" SelectFile="E:\Backup\acryan\acryan\recovery.img" />
<Part Sel="0" PartitionName="deviceinfo" FlashType="Spi" FileSystem="None" Start="4032K" Length="64K" SelectFile="" />
<Part Sel="1" PartitionName="baseparam" FlashType="Nand" FileSystem="None" Start="0" Length="6M" SelectFile="E:\Backup\acryan\acryan\base_hi3176c.img" />
<Part Sel="1" PartitionName="logo" FlashType="Nand" FileSystem="None" Start="6M" Length="8M" SelectFile="E:\Backup\acryan\acryan\logo.img" />
<Part Sel="0" PartitionName="fastplay" FlashType="Nand" FileSystem="None" Start="14M" Length="10M" SelectFile="" />
<Part Sel="0" PartitionName="cache" FlashType="Nand" FileSystem="None" Start="24M" Length="30M" SelectFile="" />
<Part Sel="0" PartitionName="misc" FlashType="Nand" FileSystem="None" Start="54M" Length="10M" SelectFile="" />
<Part Sel="1" PartitionName="kernel" FlashType="Nand" FileSystem="None" Start="64M" Length="272M" SelectFile="E:\Backup\acryan\acryan\kernel" />
<Part Sel="1" PartitionName="system" FlashType="Nand" FileSystem="Yaffs" Start="336M" Length="400M" SelectFile="E:\Backup\acryan\acryan\system.ics.yaffs2_8k24bits" />
<Part Sel="1" PartitionName="userdata" FlashType="Nand" FileSystem="Yaffs" Start="736M" Length="234M" SelectFile="E:\Backup\acryan\acryan\userdata.ics.yaffs2_8k24bits" />
<Part Sel="0" PartitionName="blackbox" FlashType="Nand" FileSystem="None" Start="970M" Length="4M" SelectFile="" />
<Part Sel="0" PartitionName="sdcard" FlashType="Nand" FileSystem="None" Start="974M" Length="3122M" SelectFile="" />
</Partition_Info>
Cheers
J.
I apparently did the same thing, I flashed the Himedia firmware but on a different clone of Veolo, the HD For All 900 (http://www.e-boda.ro/media-playere/media-player-mkv-full-hd-1080p-cu-sistem-de-operare-android-e-boda-hd-for-all-900.html).
I used a Nokia CA - 42 Cable and the Fastboot.exe (v 3.1).
Things did not went so well because I ended up with a bricked player since the uboot (aka akaboot) boot-loader 3.2.2 is not working with the HD For All 900's board.It gives me some error message and then it hangs, I cannot give any command through USB - SERIAL -UART (using putty).
The I managed also using the Fasboot.exe to put back the original fastboot 3.0 and it started again, I can give uboot commands but I ended up with wrong NAND partition layout so the kernel cannot start.
I will try to restore the old partition layout and I will come back to you because it seams you experience the same kind of problem with the partion layout.
---------- Post added at 01:55 PM ---------- Previous post was at 01:46 PM ----------
Hello
Can someone please re-upload the Poppstar MS-40 ICS firmware because the link on the German forum does not work anymore (The file was deleted).
Many Tanks
If you have a ttl card you can flash the popstar or atlas firmware even with a bricked player just choose serial instead of network in fastboot
---------- Post added at 03:17 PM ---------- Previous post was at 03:13 PM ----------
jefke2 said:
I have flashed the Poppstar MS-40 ICS firmware on the Veolo, using a CP2102 USB to TTL UART programmer. (you can get it here : http://www.android-hilfe.de/pearl-meteorit-mmb-422-hdtv-forum/366851-installationsanleitung-ics-update.html)
Everything was OK (smooth, remote control working great, etc.) I then wanted to try the Himedia firmware, so copied update.zip onto an SD card and started the update from the system settings menu. Everything went fine until the upgrade procedure stopped at the end. After waiting for 30 minutes, i pulled the power plug and tried to flash the Poppstar firmware again, but it failed. Apparently I now have bad NAND flash from 0x4a00000 up to 0x15000000 (the area where the system.img has to be written)
I tried this:
- modified the partition table (it's an XML file) and added the bad NAND flash area to the kernel partition and moved the system partition to 0x15000000. (other partitions modified as well)
- modified the bootargs.bin with these new partition locations and sizes, also modified kernel partition length.
I reflashed successfully but the Veolo does not boot, so does anyone know what i can try next ?
See XML partition table below, and modified bootargs.bin attached.
Code:
<?xml version="1.0" encoding="GB2312" ?>
<Partition_Info>
<Part Sel="1" PartitionName="fastboot" FlashType="Spi" FileSystem="None" Start="0" Length="448K" SelectFile="E:\Backup\acryan\acryan\fastboot-burn.bin" />
<Part Sel="1" PartitionName="bootargs" FlashType="Spi" FileSystem="None" Start="448K" Length="64K" SelectFile="E:\Backup\acryan\acryan\bootargs_mod.bin" />
<Part Sel="1" PartitionName="recovery" FlashType="Spi" FileSystem="None" Start="512k" Length="3520K" SelectFile="E:\Backup\acryan\acryan\recovery.img" />
<Part Sel="0" PartitionName="deviceinfo" FlashType="Spi" FileSystem="None" Start="4032K" Length="64K" SelectFile="" />
<Part Sel="1" PartitionName="baseparam" FlashType="Nand" FileSystem="None" Start="0" Length="6M" SelectFile="E:\Backup\acryan\acryan\base_hi3176c.img" />
<Part Sel="1" PartitionName="logo" FlashType="Nand" FileSystem="None" Start="6M" Length="8M" SelectFile="E:\Backup\acryan\acryan\logo.img" />
<Part Sel="0" PartitionName="fastplay" FlashType="Nand" FileSystem="None" Start="14M" Length="10M" SelectFile="" />
<Part Sel="0" PartitionName="cache" FlashType="Nand" FileSystem="None" Start="24M" Length="30M" SelectFile="" />
<Part Sel="0" PartitionName="misc" FlashType="Nand" FileSystem="None" Start="54M" Length="10M" SelectFile="" />
<Part Sel="1" PartitionName="kernel" FlashType="Nand" FileSystem="None" Start="64M" Length="272M" SelectFile="E:\Backup\acryan\acryan\kernel" />
<Part Sel="1" PartitionName="system" FlashType="Nand" FileSystem="Yaffs" Start="336M" Length="400M" SelectFile="E:\Backup\acryan\acryan\system.ics.yaffs2_8k24bits" />
<Part Sel="1" PartitionName="userdata" FlashType="Nand" FileSystem="Yaffs" Start="736M" Length="234M" SelectFile="E:\Backup\acryan\acryan\userdata.ics.yaffs2_8k24bits" />
<Part Sel="0" PartitionName="blackbox" FlashType="Nand" FileSystem="None" Start="970M" Length="4M" SelectFile="" />
<Part Sel="0" PartitionName="sdcard" FlashType="Nand" FileSystem="None" Start="974M" Length="3122M" SelectFile="" />
</Partition_Info>
Cheers
J.
Click to expand...
Click to collapse
Hai i am also busy to get the Himedia working on the veolo but do you succeeded or not ?
And how did you edit the bootargs.bin ?
kraakie256 said:
If you have a ttl card you can flash the popstar or atlas firmware even with a bricked player just choose serial instead of network in fastboot
---------- Post added at 03:17 PM ---------- Previous post was at 03:13 PM ----------
Hai i am also busy to get the Himedia working on the veolo but do you succeeded or not ?
And how did you edit the bootargs.bin ?
Click to expand...
Click to collapse
The flashing procedure seemed to go well at first, but did not succeed in the end. I read somewhere that there is a difference in how devices with 512 MB RAM (like the Veolo) and 1 GB RAM (like the Himedia Q5) so be careful At least, I now have a nice Himedia logo showing up at boot, but a bricked device nonetheless ...
I edited the bootargs.bin with Notepad++ in textmode, and used the hexeditor plugin to add (or remove) null bytes, the file has to be 64 KB exactly !
Cheers
J.
Try the Erase button in Fastboot 3.1.8
Hi,
I've an MMB-422 Mediaplayer. It's a copy of the Veolo (also based on Hi3716C). When I bought it 2 weeks ago the box was already upgraded to ICS 4.0.3. It was running nice and smooth. Then I did want to try the Update package for the HiMedia Q5, just as you did Jefke2.
I went with a broken box, it keeps on booting in Recovery. After I tried several things the only solution wich was working for me was the "Erase" button in the Fastboot 3.1 progam. I was a little bit scary because I thought that it would also erase the fastboot partition in the SPI memory. But with a Broken box I had tot do something, I deselected the fastbootpartiotion and hit the Erase button. Indeed......it erases ALL SELCTED PARTITIONS incl. the SPI partitions. But to my surprise the box still connected to fastboot 3.1 once I plugged the power out and directly again in the power socket (within a second).
I succesfully updated tot Meteorit ICS 4.0.3 firmware again and it's running very well!
We need a developer who has a working lg l9 ii to create these files, i think...
How to generate the 8660_msimage.mbn
8660_msimage.mbn is released in SW by default, actually, it includes the all the boot images and partition table there. MPRG8660.hex will download this image and reset to mass-storage mode. If customers have different HW settings, such as GPIO/DDR, the default 8660_msimage.mbn may not work for them, so customers need build their own 8660_msimage.mbn by themselves with following ways.
1. Have the QPST 2.7.366 or higher version installed.
2. Make a local folder, copy sbl1/sbl2/sbl3/rpm/tz images to this folder.
3. copy the emmcswdownload.exe from C:\Program Files\Qualcomm\QPST\bin to this folder.
4. Prepare the partition_boot.xml as below and copy the partition_boot.xml to the same folder as above.
<?xml version="1.0"?>
<image>
<physical_partition number="0">
<primary order="1" type="4d" bootable="true" label="SBL1" size="1000" readonly="false">
<file name="sbl1.mbn" offset="0"/>
</primary>
<primary order="2" type="51" bootable="false" label="SBL2" size="3000" readonly="false">
<file name="sbl2.mbn" offset="0"/>
</primary>
<primary order="3" type="45" bootable="false" label="SBL3" size="1500" readonly="false">
<file name="sbl3.mbn" offset="0"/>
</primary>
<primary order="4" type="5" bootable="false" label="EXT" size="1000000">
<extended order="1" type="47" label="RPM" size="1000" readonly="false">
<file name="rpm.mbn" offset="0"/>
</extended>
<extended order="2" type="46" label="TZ" size="1000" readonly="false">
<file name="tz.mbn" offset="0"/>
</extended>
</primary>
</physical_partition>
</image>
5. Run the emmcswdownload.exe tool to create OEM boot image with a command below.
emmcswdownload.exe -f 8660_msimage.mbn -x partition_boot.xml -s 1G -g 4M
6. The 8660_msimage.mbn will be generated in the folder.
OR:
How to build eMMC flash programmer MPRGXXXX.hex and msimage.mbn?
1. Please check if the SConscript is provided in "modem_proc/core p/tools/emmcbld/bulid". If not, you cannot build it with this release.
2. set build environment by executing RVCTXX.bat in build/ms folder
3. go to "modem_proc/core/bsp/build"
4. execute "build emmcbld BUILD_ID=xxxxxxxx"
5. The generated image is located in modem_proc/build/ms/bin/EMMCBLD/
6. MPRGXXXX.hex is eMMC programmer used to communicate with QPST to download msimage.mbn into eMMC.
7. msimage.mbn is used to enumerate the device as a USB mass storage device for all the image updates.
Please refer to modem_proc/core/bsp/tools/emmcbld/bulid/SConscript for how emmcbld and msimage are built and generated.
Using command line to creat 7x30_msimage.mbn
The eMMC Software Download Tool can also be used in Command Line mode for factory automation and creating boot images.
First find the location of your QPST install, normally under C:\Program Files(x86)\Qualcomm\ 5 QPST\bin, that contains your emmcswdownload.exe file. You can either map this location to your 6 path or refer to it directly from the cmd window.
The following command line options are supported for emmcswdownload.exe:
-f <filename> : direct output to <filename> instead of selected device
-s <size enum> : mass storage device size = { “1G”, “2G”, “4G”, etc }
-g <size enum> : write protect group size = { “4M”, “8M”, “16M”, etc }
-x <filename> : partition description file
-p <directory> : search path = path1;path2;…. Etc
-L <filename> : list all connected mass storage drives to <filename>
-i <filename> : image file to write to mass storage device
-w <drive> : mass storage drive to write image file to
In this command line:
–s and –g options are required, even if no sections are marked as read only
–s size is only used to set the size of the last partition; it does not affect the size of the output image
–g is the write-protect size for partitions marked as read only; if there are multiple read-only partitions, only the first and last partitions will be aligned on a protect size boundary
–L only dumps to the output file, not to stdout
emmcswdownload -f \tmp\7x30_msimage.mbn -x E:\emmc\partition_boot.xml -s 1G -g 64M -p E:\emmc\;
Original Post: http://4pda.ru/forum/index.php?s=&showtopic=643084&view=findpost&p=43253768
This does not help at all
neutrondev said:
This does not help at all
Click to expand...
Click to collapse
Why? To revive the smartphone lacks only these two files
JackPOtaTo said:
Why? To revive the smartphone lacks only these two files
Click to expand...
Click to collapse
Ok try then. You can't make the files like that but try if you want. I just told you .
neutrondev said:
Ok try then. You can't make the files like that but try if you want. I just told you .
Click to expand...
Click to collapse
I wrote that we need a developer who has a working l9 II to build these files:cyclops:
JackPOtaTo said:
I wrote that we need a developer who has a working l9 II to build these files:cyclops:
Click to expand...
Click to collapse
You can't build it like that, I tell you again. No device with your socket was unbricked. If it was that easy someone would of made them. Don't trust everything you read on the internet.
neutrondev said:
You can't build it like that, I tell you again. No device with your socket was unbricked. If it was that easy someone would of made them. Don't trust everything you read on the internet.
Click to expand...
Click to collapse
Hi , I have Coolpad devce "Qiku Terra" MSM8992 and the device is hard bricked. I do not have the required files such as MPRG8992.mbn, 8992_msimage.mbn etc. Can you suggest some ways to unbrick it???.
As per a post on xda of Coolpad device if emmc image of working phone (same model) is written on a sd card using HDD Raw copy then the phone can boot in fastboot mode. You think this would work??
Can you also help me with the right code to get the emmc image's initial partitions?? I would appreciate your response.
No even emergency/download mode?
JackPOtaTo said:
<?xml version="1.0"?>
<image>
<physical_partition number="0">
<primary order="1" type="4d" bootable="true" label="SBL1" size="1000" readonly="false">
<file name="sbl1.mbn" offset="0"/>
</primary>
<primary order="2" type="51" bootable="false" label="SBL2" size="3000" readonly="false">
<file name="sbl2.mbn" offset="0"/>
</primary>
<primary order="3" type="45" bootable="false" label="SBL3" size="1500" readonly="false">
<file name="sbl3.mbn" offset="0"/>
</primary>
<primary order="4" type="5" bootable="false" label="EXT" size="1000000">
<extended order="1" type="47" label="RPM" size="1000" readonly="false">
<file name="rpm.mbn" offset="0"/>
</extended>
<extended order="2" type="46" label="TZ" size="1000" readonly="false">
<file name="tz.mbn" offset="0"/>
</extended>
</primary>
</physical_partition>
</image>
Click to expand...
Click to collapse
Can you give me more details? I have a bricked Huawei Y6 (SCL-L21) that has Qualcomm cpu and I have the original firmaware in UPDATE.APP format (huawei default) but I can extract almost every partition inside that file, so looking at your xml, I have sbl1, rpm and tz partition, so do I need to delete sbl2 and sbl3 entries? and one more thing... Do I have to change the size attribute?
Waiting for your reply, thanks
Hi, I have a rooted working d605. I can help if you give me instructions.
So the people in Japan using this method are wrong ?
The code is not exactly correct but the theory seems correct.
Just for info.
I found out that to build a msimage.mbn for your phone, That you have to use a older version of QPST, The newest version does not work.
I built a 8960_msimage.mbn that matches my phone using the old version, QPST 2.7.366
For some reason newer versions of emmcswdownload.exe fails when trying to build a image.
New versions are not always better versions... Look at Windows 10.
TL;DR - This program is essentially like sbf/odin/and other such tools. Almost..
QPST/QFIL is a flashing tool for qualcomm devices. It can be used to flash the eMMC of our device.
This means that it can fix any software brick.
The only thing is, I can't seem to find the necessary files to flash.
HERE @tenfar started to do a bit of research on the topic.
Let's get this ball rolling and use the tool that Huawei uses! No more RMA's! (Hopefully)
QPST
engineer radioDon't flash unless you know what you're doing. It will disable radio
How this could potentially be used
EDIT: According to the pdf, the angler is supported in this release of BoardDiag! http://www.mylgphones.com/download-boarddiag-v2-99a.html
http://www.modaco.com/forums/topic/348787-guide-how-to-modify-your-partitions/
Solder emmc
I'm attempting to do a full eMMC backup now with
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/emulated/0/backup.img bs=512 count=30535646
tr4nqui1i7y said:
I'm attempting to do a full eMMC backup now with
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/emulated/0/backup.img bs=512 count=30535646
Click to expand...
Click to collapse
I have the backup.img. Going to try to decompile and see if it's actually any help.
Anyone know where to find the version of this for our device? 'prog_emmc_firehose_8936.mbn'
Our flash programmer file won't be firehose, afaik. still figuring this all out.
I've got a long night ahead of me Going to try to get the necessary files another way. Running the adb command yeilded corrupt imgs twice. Since it took about an hour each time, I'll have to find another way.
@Jammol want to get in on this?
Maybe we can find something like this for our device?
EDIT: Maybe there is a way to run fsck.repair against a usb device?
EDIT: Maybe I'll just try to change the physical eMMC at this point Like This
EDIT: But then we'd need to repartition memory Similar to this
In the process of making this over
Code:
partition_entries=14
partition_name=PrimaryGPT
start_block=0x0
file_name=PrimaryGPT.mbn
file_size=524288
partition_name=sbl1
start_block=0x20400
file_name=sbl1.mbn
file_size=524288
partition_name=rpm
start_block=0x20C00
file_name=rpm.mbn
file_size=524288
partition_name=tz
start_block=0x21000
file_name=tz.mbn
file_size=524288
partition_name=sdi
start_block=0x21400
file_name=sdi.mbn
file_size=524288
partition_name=aboot
start_block=0x21800
file_name=aboot.mbn
file_size=524288
partition_name=sbl1b
start_block=0x22C00
file_name=sbl1b.mbn
file_size=524288
partition_name=tzb
start_block=0x23400
file_name=tzb.mbn
file_size=524288
partition_name=rpmb
start_block=0x23800
file_name=rpmb.mbn
file_size=524288
partition_name=abootb
start_block=0x23C00
file_name=abootb.mbn
file_size=524288
partition_name=imgdata
start_block=0x37400
file_name=imgdata.mbn
file_size=1572864
partition_name=laf
start_block=0x38C00
file_name=laf.mbn
file_size=13631488
partition_name=boot
start_block=0x43C00
file_name=boot.mbn
file_size=8912896
partition_name=BackupGPT
start_block=0x3A3DC00
file_name=BackupGPT.mbn
file_size=524288
Using this INFO
@bitdomo gave thorough instructions here
OP updated.
I want to make a little comment about this boarddiag tool, and how it works.
Emmc test:
Erase: erase the whole emmc. Even if you select a partition from the dropdown menu,
Read only: Only reads random blocks from the emmc. If you check DUMP it will read back the amount of blocks of a the chosen partition given in the partition.txt
Write only: writes dummy data to the emmc (55AA hex values and some other other random writes on the actual partition).
Read/Write: writes dummy data to the emmc (55AA hex values and some other other random writes on the actual partition) and then verify them by reading it back
SDRAM test:
I think this test the memory. There is a Level option for it. I dont know what is the differance between the two.
PIMC ON:
No idea, but in some LG documentations it is for only APQ8064 chipset.
Restore boot img:
Restores the images.
How it know which partitions have to be restored?
There is a rawprogram0.xml in model\Nexus5 (MSM8974_HammerHead)\boot_partition_info folder.
The partitions declared here will be flashed to the device if you select nothing in the partititon dropdown menu or in the restore boot img dropdown menu
Boarddiag only cares about the "label" value (have to be tha same as in partition.txt) from rawprogram0.xml. The rest info like startblock, files size and file name will be acquired from the partition.txt.
Partition.txt is a binary file:
0x00-0x03: start block
0x04-0x07: file size in block numbers ( 1 block = 512 byte)
0x08-0x0F: always zero
0x10-0x2F: partition name (must be the same as the label value in rawprogram0.xml)
0x30-0x4F: file name
and the pattern goes on.
I wrote a little program which converts this binary partition.txt to an actual txt. You can get it from here
Copy the partition.txt to the same folder where the bin2txt and txt2bin exes are. Run bin2txt then it will create a readable_partition.txt file. Edit it with notepad++. The start block is in HEX and the file size is in bytes (must be multiple of 512). Partition entries is the number of partition declared in the partition.txt. If you done with the editing then run txt2bin and it will create a new_partition.txt file.
Click to expand...
Click to collapse
tr4nqui1i7y said:
@Jammol want to get in on this?
Click to expand...
Click to collapse
What's the current setup of your device? Meaning locked stock or unlocked?
I haven't messed with partitions that deep since the Lg Pro I think that's the same as the Nexus 4 but blocky.
I'll get my desktop setup today after work. Been using my work work laptop for adb (probably shouldn't).
Sent from my LG G4 using Tapatalk
@jimbridgman you enjoy working this deep don't you?
Sent from my Nexus 6P using XDA-Developers mobile app
Jammol said:
What's the current setup of your device? Meaning locked stock or unlocked?
I haven't messed with partitions that deep since the Lg Pro I think that's the same as the Nexus 4 but blocky.
I'll get my desktop setup today after work. Been using my work work laptop for adb (probably shouldn't).
Sent from my LG G4 using Tapatalk
Click to expand...
Click to collapse
I have two:
unlocked/rooted/rom'd
unlocked/corrupt eMMC
I see you posted with a G4, is your 6P bootlooped again/still?
My device is currently stuck in RELINK HS-USB QDLoader 9008 according to device manager.
I've tried miflash, qfil, and boarddiag.
Unfortunately they all require a programmer file, which I have no clue as to where we can get that package of files (programmer file, build.xml, and patch.xml)
I won't be rolling up my sleeves on this, as I've already been down the rabbit hole on this one. But, I will lend a hand. You might have better luck using this version. Also, here's the latest qd loader driver. Good luck.
kibmikey1 said:
I won't be rolling up my sleeves on this, as I've already been down the rabbit hole on this one. But, I will lend a hand. You might have better luck using this version. Also, here's the latest qd loader driver. Good luck.
Click to expand...
Click to collapse
Would happen to have any clues on how to find the files necessary for qfil on our device?
tr4nqui1i7y said:
Would happen to have any clues on how to find the files necessary for qfil on our device?
Click to expand...
Click to collapse
Normally those are taken from a backup from the system you're modifying. But if you don't have one, you need to either extract the defaults from a master (like a factory image or unpackaged full ota) or someone can extract the necessary files you need from their own backup and send them to you.
kibmikey1 said:
Normally those are taken from a backup from the system you're modifying. But if you don't have one, you need to either extract the defaults from a master (like a factory image or unpackaged full ota) or someone can extract the necessary files you need from their own backup and send them to you.
Click to expand...
Click to collapse
When I checked out the factory images I didn't see any mbn or xml files. Any chance you'd lend a hand? Checked the ota and didn't seem to find the right files either.
Maybe I just overlooked them.
Both can be found on g.co/ABH
tr4nqui1i7y said:
When I checked out the factory images I didn't see any mbn or xml files. Any chance you'd lend a hand? Checked the ota and didn't seem to find the right files either.
Maybe I just overlooked them.
Both can be found on g.co/ABH
Click to expand...
Click to collapse
You could try using cygwin to decompile the images, but I'm not sure if they're encrypted or not. If they are (and they probably are...) that would be no help. Another option would be to compile Android through llvm using this. It would give you the advantage of having it decompiled to the levels you need before encryption (mbn and xml files). You'll have to make the programmer file yourself. I'll give an example, using an 8660 from a Nexus 5. 8660_msimage.mbn is released in SW by default, actually, it includes the all the boot images and partition table there. MPRG8660.hex would download this image and reset to mass-storage mode.
1. Have the QPST 2.7.366 or higher version installed.
2. Make a local folder, copy sbl1/sbl2/sbl3/rpm/tz images to this folder.
3. copy the emmcswdownload.exe from C:\Program Files\Qualcomm\QPST\bin to this folder.
4. Prepare the partition_boot.xml as below and copy the partition_boot.xml to the same folder as above.
<?xml version="1.0"?>
<image>
<physical_partition number="0">
<primary order="1" type="4d" bootable="true" label="SBL1" size="1000" readonly="false">
<file name="sbl1.mbn" offset="0"/>
</primary>
<primary order="2" type="51" bootable="false" label="SBL2" size="3000" readonly="false">
<file name="sbl2.mbn" offset="0"/>
</primary>
<primary order="3" type="45" bootable="false" label="SBL3" size="1500" readonly="false">
<file name="sbl3.mbn" offset="0"/>
</primary>
<primary order="4" type="5" bootable="false" label="EXT" size="1000000">
<extended order="1" type="47" label="RPM" size="1000" readonly="false">
<file name="rpm.mbn" offset="0"/>
</extended>
<extended order="2" type="46" label="TZ" size="1000" readonly="false">
<file name="tz.mbn" offset="0"/>
</extended>
</primary>
</physical_partition>
</image>
5. Run the emmcswdownload.exe tool to create OEM boot image with a command below.
emmcswdownload.exe -f 8660_msimage.mbn -x partition_boot.xml -s 1G -g 4M
6. The 8660_msimage.mbn will be generated in the folder.
Again, it's just an example of building one, and it's using an older model, but I think you get it. Aside from that, the only other thing I can think for you would be to use the files Qualcomm's board support package (Dragonboard 810), which would come with purchasing it with an entire new motherboard, which is the equivalent of rma'ing it anyway. This would be me rolling my sleeves back down for tonight. Let me know how it goes!
kibmikey1 said:
You could try using cygwin to decompile the images, but I'm not sure if they're encrypted or not. If they are (and they probably are...) that would be no help. Another option would be to compile Android through llvm using this. It would give you the advantage of having it decompiled to the levels you need before encryption (mbn and xml files). You'll have to make the programmer file yourself. I'll give an example, using an 8660 from a Nexus 5. 8660_msimage.mbn is released in SW by default, actually, it includes the all the boot images and partition table there. MPRG8660.hex would download this image and reset to mass-storage mode.
1. Have the QPST 2.7.366 or higher version installed.
2. Make a local folder, copy sbl1/sbl2/sbl3/rpm/tz images to this folder.
3. copy the emmcswdownload.exe from C:\Program Files\Qualcomm\QPST\bin to this folder.
4. Prepare the partition_boot.xml as below and copy the partition_boot.xml to the same folder as above.
<?xml version="1.0"?>
<image>
<physical_partition number="0">
<primary order="1" type="4d" bootable="true" label="SBL1" size="1000" readonly="false">
<file name="sbl1.mbn" offset="0"/>
</primary>
<primary order="2" type="51" bootable="false" label="SBL2" size="3000" readonly="false">
<file name="sbl2.mbn" offset="0"/>
</primary>
<primary order="3" type="45" bootable="false" label="SBL3" size="1500" readonly="false">
<file name="sbl3.mbn" offset="0"/>
</primary>
<primary order="4" type="5" bootable="false" label="EXT" size="1000000">
<extended order="1" type="47" label="RPM" size="1000" readonly="false">
<file name="rpm.mbn" offset="0"/>
</extended>
<extended order="2" type="46" label="TZ" size="1000" readonly="false">
<file name="tz.mbn" offset="0"/>
</extended>
</primary>
</physical_partition>
</image>
5. Run the emmcswdownload.exe tool to create OEM boot image with a command below.
emmcswdownload.exe -f 8660_msimage.mbn -x partition_boot.xml -s 1G -g 4M
6. The 8660_msimage.mbn will be generated in the folder.
Again, it's just an example of building one, and it's using an older model, but I think you get it. Aside from that, the only other thing I can think for you would be to use the files Qualcomm's board support package (Dragonboard 810), which would come with purchasing it with an entire new motherboard, which is the equivalent of rma'ing it anyway. This would be me rolling my sleeves back down for tonight. Let me know how it goes!
Click to expand...
Click to collapse
What about making the xml files?
tr4nqui1i7y said:
What about making the xml files?
Click to expand...
Click to collapse
You can build xml files in eclipse. The Android NDK/SDK provided should have the template there to use.
Hello
I have a question to better than me
Android MM or N
Can I add root permissions for rom without custom recovery (TWRP, CWM, ect.) - means only via edit system.img and boot.img files (row files).
Without custom recovery no sense to do zip files to flash so only way is (I think) add manually systemless supersu to the kernel and rom "img" files.
I mean copy all sh, rc, libs, ect. files to specific folders ....
This is for spreadtrum SC7731G and SC8830 chipsets.
..or I think maybe edit xml file for coping and install specifics files in "pac" - install files for this devices.
PAC file has inside : system.img, boot.img, recovery.img, BT, CP, CSC, ect. and xml file.
XML file has script for install those files - and maybe add to PAC file supersu.zip and add to xml file script for install (flash) super su?
Any dev can do it? or give some ideas for it?
example from xml file:
<?xml version="1.0" encoding="UTF-8"?>
<!-- FlashTypeID: 0, means Nor Flash;1, means Nand Flash -->
<!-- File-Flag: 0, means this file need not input file path -->
<!-- 1, means this file need input file path -->
<!-- File-CheckFlag: 0, this file is optional -->
<!-- 1, must select this file -->
<!-- 2, means not check this file in pack -->
<!-- Mode: 0, not uesed; 1, means nand page size and oob care -->
<!-- File-Type: MasterImage,means it will add BOOT_PARAM -->
<!-- and OS_INFO information to file -->
<!-- File-ID: Can not be changed,it is used by tools -->
<!-- File-IDAlias: This is for GUI display can be changed -->
<BMAConfig>
<ProductList>
<Product name="SC77xx">
<SchemeName>SC77xx</SchemeName>
<FlashTypeID>1</FlashTypeID>
<Mode>0</Mode>
<NVBackup backup="1">
<NVItem name="Calibration" backup="1">
<ID>0xFFFFFFFF</ID>
<BackupFlag use="1">
<NVFlag name ="Replace" check ="0"></NVFlag>
<NVFlag name ="Continue" check ="0"></NVFlag>
</BackupFlag>
</NVItem>
<NVItem name="IMEI" backup="1">
<ID>0xFFFFFFFF</ID>
<BackupFlag use="0"></BackupFlag>
</NVItem>
<NVItem name="W_Calibration" backup="1">
<ID>0x12D</ID>
<BackupFlag use="1">
<NVFlag name ="Continue" check ="0"></NVFlag>
</BackupFlag>
</NVItem>
<NVItem name="BlueTooth" backup="1">
<ID>0x191</ID>
<BackupFlag use="1">
<NVFlag name ="Continue" check ="0"></NVFlag>
</BackupFlag>
</NVItem>
<NVItem name="BandSelect" backup="1">
<ID>0xD</ID>
<BackupFlag use="1">
<NVFlag name ="Continue" check ="0"></NVFlag>
</BackupFlag>
</NVItem>
<NVItem name="WIFI" backup="1">
<ID>0x199</ID>
<BackupFlag use="1">
<NVFlag name ="Continue" check ="1"></NVFlag>
</BackupFlag>
</NVItem>
<NVItem name="MMITest" backup="1">
<ID>0x19A</ID>
<BackupFlag use="1">
<NVFlag name ="Continue" check ="1"></NVFlag>
</BackupFlag>
</NVItem>
<NVItem name="WIFICal1" backup="1">
<ID>0x19F</ID>
<BackupFlag use="1">
<NVFlag name ="Continue" check ="1"></NVFlag>
</BackupFlag>
</NVItem>
<NVItem name="WIFICal2" backup="1">
<ID>0x1A0</ID>
<BackupFlag use="1">
<NVFlag name ="Continue" check ="1"></NVFlag>
</BackupFlag>
</NVItem>
<NVItem name="WIFICal3" backup="1">
<ID>0x1A1</ID>
<BackupFlag use="1">
<NVFlag name ="Continue" check ="1"></NVFlag>
</BackupFlag>
</NVItem>
</NVBackup>
<Partitions>
<!-- size unit is MBytes -->
<!--
<Partition id="splloader" size="0"/>
<Partition id="ubootloader" size="0"/>
-->
<Partition id="prodnv" size="5"/>
<Partition id="miscdata" size="1"/>
<Partition id="wmodem" size="15"/>
<Partition id="wdsp" size="2"/>
<Partition id="wfixnv1" size="1"/>
<Partition id="wfixnv2" size="1"/>
<Partition id="wruntimenv1" size="1"/>
<Partition id="wruntimenv2" size="1"/>
<Partition id="wcnmodem" size="5"/>
<Partition id="wcnfixnv1" size="1"/>
<Partition id="wcnfixnv2" size="1"/>
<Partition id="wcnruntimenv1" size="1"/>
<Partition id="wcnruntimenv2" size="1"/>
<Partition id="logo" size="1"/>
<Partition id="fbootlogo" size="1"/>
<Partition id="boot" size="18"/>
<Partition id="system" size="2550"/>
<Partition id="persist" size="2"/>
<Partition id="sysinfo" size="6"/>
<Partition id="cache" size="150"/>
<Partition id="recovery" size="17"/>
<Partition id="misc" size="1"/>
<Partition id="userdata" size="0xFFFFFFFF"/>
Click to expand...
Click to collapse
Thank You
anyone can help?
This is a manfiest to build lineage-17.1 with MiCode kernel from sources:
Based on initial device/vendor work by @alibei + MiCode Android Q sources.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="vendor"
fetch="https://github.com"
revision="lineage-17.1" />
<remote name="device"
fetch="https://github.com"
revision="lineage-17.1"/>
<remote name="kernel"
fetch="https://github.com"
revision="tucana-q-oss"/>
<remote name="sdclang"
fetch="https://github.com"
revision="pie" />
<!--Device Trees-->
<project path="device/xiaomi/tucana" name="b100dian/android_device_xiaomi_tucana" remote="device" />
<!-- Kernel-->
<project path="kernel/xiaomi/tucana" name="b100dian/Xiaomi_Kernel_OpenSource" remote="kernel" />
<!-- Vendor folders -->
<project path="vendor/xiaomi/tucana" name="b100dian/android_vendor_xiaomi_tucana" remote="vendor" />
<!-- Compiler -->
<project path="prebuilds/sdclang/linux-x86_64" name="ThankYouMario/proprietary_vendor_qcom_sdclang-8.0_linux-x86/"
remote="sdclang" />
</manifest>
updated 2020-04-08
What works:
- main camera
- selfie camera
- LTE
- calling
- sound
- accelerometer
- light sensor
- GPS
- wifi
What doesn't work:
- proximity sensor
- other cameras than main and selfie
Not tested:
- infrared port
- magentometer
This is the original post asking for help (any better way to make a collapsible quote?)
Spoiler: Original post 1
ORIGINAL POST1Hi ROM developers, I would like to build one of the UNOFFICIAL lineage-17.1 roms posted on this forum from sources.
(The reason is that I want to apply sailfish OS build on top of that on my Mi Note 10).
I started with this tucana.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="vendor"
fetch="https://github.com"
revision="lineage-17.1" />
<remote name="device"
fetch="https://github.com"
revision="lineage-17.1"/>
<remote name="kernel"
fetch="https://github.com"
revision="tucana-q-oss"/>
<remote name="hardware"
fetch="https://github.com"
revision="lineage-17.1" />
<!--Device Trees-->
<project path="device/xiaomi/tucana"
name="alibei/android_device_xiaomi_tucana" remote="device" />
<!-- Kernel-->
<project path="kernel/xiaomi/tucana"
name="MiCode/Xiaomi_Kernel_OpenSource" remote="kernel" />
<!-- Vendor folders -->
<project path="vendor/xiaomi/tucana"
name="alibei/android_vendor_xiaomi_tucana" remote="vendor" />
<!-- <project path="hardware/xiaomi"
name="LineageOS/android_hardware_xiaomi" remote="hardware"/> -->
</manifest>
I had a warning about using pre-built kernel and I commented out the usage of prebuilt one and pointed to vendor/tucana_user_defconfig (user means it wont work in userdebug?).
I've also 'fixed' some not-localized strings in some manifests (made them unlocalized, unfortunately lost changes in a repo sync --force sync..) - not big changes that cannot be re-done..
But the end result was a zipfile that when flashed, set me into bootloop to fastboot..
I did flash @alibei's lineage-18.1 and that works. Also, I've tried @Chemuski1's vendor/device repos (various other errors I can't remember).
So the question is, what xml file should I use to build a version of this?
(additional Qs: what are you folks using as a kernel for this device? Is the MiCode one any good? Is there guide to extract the vendor and device files myself?).
Thanks!
P.S. I'm not interested in some advanced android feature for this, mainly the most important peripherals to work (GSM, camera)
Spoiler: Original post 2
ORIGINAL POST 2:I have gotten one step closer: I managed to build the kernel (only) with instructions from MiCode , qcom clang 8.0 and these changes.
Now I need to test that it boots by re-packing it into boot.img and dtbo.img.
But first, I need to be able to unpack and repack the boot.img and dtbo.img from the device without any changes.
I did manage to unpack boot.img and repack it back (same kernel) and make it boot, with instructions more or less here https://gist.github.com/b100dian/40c8dbe746ff181aff71ee10a75a5f3c
What id did _not_ manage is to do the same (unpack/repack) test for dtbo.img
It seems the image from tucana has .dtb files but also a kernel.
(the size is 32M and unmkbootimg actually extracts a kernel from it, while imjtool actually extracts dtb files)
So the next question is: have you ever seen a dtbo.img with both dtb files and kernel and if so, what to use to extract it all and repack it?
(I have a booting lineage-17.1, not everything working, editing first post and title now)
For the wifi and audio you have to setup the config for modules. I think in my other thread on update 2 it has it on the bottom. It will add it during the build process.
Only managed to add wifi myself. Audio I am unable to merge in. Micode has the sources for wifi audio and drivers. Hope it helps, so you can add it.
I think in my case the vendor proprietary blobs are not complete, looking for the way to extract then afresh. If that fails then I'll follow up with your BoardConfig wifi changes. Thank!
Update: audio and wlan kernel modules are now build inline and work. Thanks @Squida for the nudge in the right direction!
Update: ultrasound proximity works after https://github.com/b100dian/Xiaomi_Kernel_OpenSource/commit/3c8506f460b405e8af6851e7d875212dde3ca8a6 (at least if you boot the kernel with MIUI, haven't tested with lineage)