Related
Hi there,
Here is a command line tool that can extract and rebuild a flash.bin file for the LG KS20.
First, the options available :
Code:
LGFlashMuncher.exe [options] path [output]
EXTRACT Options ---(at least one option required)-----------------------------
-r : extract Raw data
-h : extract header
-m : extract MBR
-p : extract partitions
-t : trim extracted partitions
-l : output layout informations to file 'flash.xml'
-o : output OS.nb compatible file
output : path to output directory (must exists)
CREATE Options ---(all options required)-------------------------------------
-c file : create new flash.bin outputed to 'file'
(MBR and fat partition are taken from original flash.bin)
-e file : use 'file' for header
-0 file : use 'file' for partition 0 (boot)
-1 file : use 'file' for partition 1 (rawfs)
-2 file : use 'file' for partition 2 (imgfs)
COMMON Option ---------------------------------------------------------------
path : path to flash.bin file
Next, how to extract data from a flash.bin to a directory named output :
Code:
LGFlashMuncher.exe -htmlp FLASH.bin output
How to rebuild a new flash.bin :
Code:
LGFlashMuncher.exe -c newflash.bin -e header.bin -0 part_0_BOOT.bin -1 part_1_RAWFS.bin -2 part_2_IMGFS.bin FLASH.bin
(This rebuild process requires an existing flash.bin file)
At the moment, this tool use the partition layout and the empty fat32 (last partition) found in the original flash.bin file. The next step will be rebuild the partition layout.
I've made some test with this tool, but I cannot be sure it will work in all situations. Spocky had a preview of this tool a couple of days ago, and he successfully built a french 10G and a french 10A : I'm sure he will soon share his knowledge...
Very Nice job !
Thank.
Très bon travail MisterJP.
Merci.
Does this mean we can flash the files we extract with pdocread? (part00.raw, etc)
I think that for the moment only part02.raw
@+
dorik2k said:
Does this mean we can flash the files we extract with pdocread? (part00.raw, etc)
Click to expand...
Click to collapse
If the generated files are image of your phone partitions, then I guess it's possible if you respect the partitions order.
Hi, misterjp
In your LGFlashMuncher.exe there is an option:
-o : output OS.nb compatible file
I am just wondering is it FLASH.bin to OS.nb?
And is there any way to convert OS.nb back to FLASH.bin?
The reason that i want to do that is because in that case, i can convert a OS.nb which hv a larger partition table to Flash.bin for cooking
Thx in advance
Hi raykisi,
Sorry, but this tool is not able at this time to re-build an Flash.bin from an OS.nb file. It was just a test option while I was testing my code.
I'm planning on updating this tool, but it takes time and I don't have many these days.
JP.
o...gd to hear that you are going to update this tool, we would wait, take you time. And thx for your great work
Hey, sorry about the question.. i know i'm such a noob, but i'm brazilian and my "english understanding" is kind of weak sometimes.. So...
Is there any way to extract the Flash.bin and others of my current ROM? I mean, the actual ROM of my phone?
I'm asking this because here in Brazil we have the MS25/MS20.. A kind of KS20 without 3G, wifi, and front camera devices.. but same processor and same everithing else.. so, I think LG BRASIL will not provide the roms so early, but the v10a are full of bugs! Also i can`t flash with a KS20 rom, because that missing devices and because my operator phone frequency is 850 MHz (VIVO).
well, someone have an idea? Or a link? Or a read recomendation?
Brazilian people are really needing help with this, and we are getting tired to search with no answers..
Thank`s a lot!
As you know, we were unable to extract ext4 from Sony ICS firmwares. I took a look at the problem and found out that Sony changed the way sin are generated.
I wrote a quick and (very) dirty command line tool to extract sin properly, it's now possible to extract a working system.ext4.
Usage:
sin2raw <sin file> <output file> [size[K|M|G]]
Usage examples:
sin2raw system.sin system.ext4
sin2raw userdata.sin userdata.ext4
sin2raw kernel.sin kernel.elf
Note:
For linux, there are two versions, sin2raw for 64 bits and sin2raw32 for 32 bits. I strongly recommend using the 64 bits one, 2 gig+ ext4 files are safer with this one.
Release history:
v 0.2:
new: partition size is extracted to generate file, specifying file size is not needed anymore.
new: loader.sin is detected and handled properly.
fix: block header sizes are int, not short.
fix: win32 compatibility.
fix: various size fixes for 32 bits cpu.
code cleanup.
v 0.1 :
Initial release
FAQ
*obsolete* What is size param / 1G ?
When extracting ext4, you have to specify the original partition size on phone. For instance, on xperia S, system is exactly 1 gig, so you have to add 1G. Userdata partition is almost 2 gig, you have to add 2097120K instead of 1G
(Ugly) source code is there, pre-built binaries for windows and linux are attached to this post.
More details to come soon on sin format in second post.
Background:
So, here is the deal: basically, new ext4 sins are using something that was in sin format but that we didn't dig into.
Sin is like this:
Code:
-----------------------
| Sin Header (15 bytes) |
-----------------------
| Block descriptors |
-----------------------
| File Header |
-----------------------
| File Data |
-----------------------
Block descriptors are like this:
Code:
---------------
| target_offset |
---------------
| block_count |
---------------
| block_length |
---------------
| payload_size |
---------------
| payload |
---------------
I presume payload is block signature. A block descriptor is working like this: takes "block_length" bytes from sin "data" and put them at "target_offset" on target device/file.
Up to ics, all block target_offsets were contiguous and that's why sin2img was working. With ics, they are not, explaining why sin2img doesn't work anymore.
History:
2012/08/16 18:00: new analysis, used in 0.2
2012/08/16 11:00: pdfs with more detailed information
it works, thx.
but with only this option 1G added.
Code:
sin2raw system.sin system.ext4 1G
:good:Great job! Thank you very much, i just got extract problem on new *.sin files.
Let me test this tool,I will give some feedback soon.
---------- Post added at 01:50 PM ---------- Previous post was at 01:44 PM ----------
DearTanker said:
:good:Great job! Thank you very much, i just got extract problem on new *.sin files.
Let me test this tool,I will give some feedback soon.
Click to expand...
Click to collapse
It works now,:laugh:,but what is "1G" means?
It seems output file system.ext4 size is 1G?
sorry for my pool english.
---------- Post added at 02:00 PM ---------- Previous post was at 01:50 PM ----------
can extract userdata.sin too,but when extract userdata.sin it will run out space of disk..
Thanks for the info..I will try it.
1G is output file size, 1 gigabyte, you can also use 1024M.
When extracting ext4, you have to specify the phone system partition size if you want to be able to mount it. System partition is 1 gig on Xperia S, I don't know about the other xperias.
If you extract other files like kernel.sin, you don't need to specify output file size.
can extract userdata.sin too,but when extract userdata.sin it will run out space of disk..
Click to expand...
Click to collapse
userdata.sin is almost 2GB, use this:
sin2raw userdata.sin userdata.ext4 2097120K
it will mount properly.
letama said:
userdata.sin is almost 2GB, use this:
sin2raw userdata.sin userdata.ext4 2097120K
it will mount properly.
Click to expand...
Click to collapse
thx, it works on userdata now
but why 2G does not work?
matchung said:
thx, it works on userdata now
but why 2G does not work?
Click to expand...
Click to collapse
Because partition is not exactly 2gig, more 1.999
Why is the system folder not available after converting sin to ext4?
Sharaz22, what do you mean by not available after converting ? This tool extracts a .ext4 image file, you have to mount it to see files. For instance:
mkdir system
sudo mount -o loop -t ext4 system.ext4 system
On windows, I don't know, I know there are some options but never looked at them.
I have mounted the system.ext4 image but there is no system folder in there all the other folder are available e.g. apps xbin etc.
Ah, got it. Well, system.ext4 is the system folder content. In android, system directory is coming from a partition that is mounted to an empty system directory. This is exactly this partition you have there.
Just want to confirm that this tool works fine. I can create pre-rooted image much easier. Don't need to create it from Nandroid anymore. Thanks
Sent from my LT26i using xda premium
Thanks for the feedback!
I'm working on a new release, 0.1 has issues with kernel extracts and hopefully I should be able to compute ext4 size automatically.
And a special thanks to Androxyde for his help!
Thanks,
It's work fine!
New version 0.2 is out, extract is much better now (previous one has few bugs) and size parameter is not needed anymore.
Check first post for details.
its working very fast and without bugs, thats nice, thanks!
I'm using Windows 7 Ultimate 32bit. About sin2raw, how do I open & use it You know, when I left-clicked on "sin2raw.exe", a command windows did appear in just one second, then it disappeared...
banking.amateur said:
I'm using Windows 7 Ultimate 32bit. About sin2raw, how do I open & use it You know, when I left-clicked on "sin2raw.exe", a command windows did appear in just one second, then it disappeared...
Click to expand...
Click to collapse
Sin2raw is a command line tool. You have to use it in a cmd.exe window. Or you could use last FlashTool as Androxyde added the same algorithm in his tool.
!!!IMPORTANT!!!
This is only information thread. Not Use this for Device.
Where We find Modem/Bootloader file?
In (example) this file: Dellvenuepro_2250.1800.219.7720_bootloader_logo_info.pkg.cab
open example in 7zip:
--go to OEM_8X50_MODEM.cab.pkg:
We have 3 file:
--15b74b9d-d86c-4e9e-967e-11bfeaad51e3.dsm
--MODEM -> bootloader file
--ver.ver -> contains a modem version(open this in normal Notepad)
How to - update this package?
We Update this .cab file via CAB Sender
Info:
In package - OEM_8X50_LOGO.cab.pkg We find Dell LOGO
!!!IMPORTANT!!!
This is only information thread. Not Use this for Device.
Nokser
Huawei Update Extractor
After messing around a bit with the perl tools available for extracting Huawei update.app files,
i got the idea to create an own (windows) tool.
Requirements
(All versions <= v0.9.9.3 need .Net Framework 3.5)
Latest version uses .Net Framework 4.6.1
Install
Extract the content of the zip to a folder somewhere on your system.
Execute HuaweiUpdateExtractor.exe
I'm planning to create an installer sometime.
Usage
Press the browse (...) button and select an update.app file. Select a device or unknown and press on the open button.
You'll see the content of the update.app file in the listview.
Select one or more files and right click. Choose Extract selected from the context menu.
Choose the ouput folder and press ok.
Or just right click on the list and select Extract all, choose the output folder again and press ok.
Press close on the extract window.
You can sort the list on sequence, filename and size. Just press on the desired column header.
Command line:
HuaweiUpdateExtractor extract input output [profile]
HuaweiUpdateExtractor repack input output profile
Profile
The profiles.xml file is used to identify the files in the update.app file. Every file in the update.app has a sequence or type, which is also
shown in the list. Those sequences or types are used to identify the file/device partition.
Example:
Code:
<?xml version="1.0"?>
<Profiles>
<Profile name="Unknown" author="worstenbrood">
<Files/>
</Profile>
<Profile name="Huawei G510-0100" author="worstenbrood">
<Files>
<File sequence="00000000" partition="/dev/block/mmcblk0p17">system.img</File>
<File sequence="40000000" partition="/dev/block/mmcblk0p13">recovery.img</File>
<File sequence="80000000" partition="/dev/block/mmcblk0p03">baseband.img</File>
<File sequence="EC000000">version.txt</File>
<File sequence="E4000000">splash.raw565</File>
<File sequence="FC000000" partition="/dev/block/mmcblk0p12">boot.img</File>
<File sequence="70000000" partition="/dev/block/mmcblk0p16">cust.img</File>
<File sequence="30000000" partition="/dev/block/mmcblk0p18">userdata.img</File>
<File sequence="FE000000" filetype="signature">signature</File>
<File sequence="FF000000" filetype="checksum">crc</File>
</Files>
</Profile>
<Profile name="Huawei P6" author="worstenbrood">
<Files>
<File type="system" partition="/dev/block/mmcblk0p16">system.img</File>
<File type="cache" partition="/dev/block/mmcblk0p17">cache.img</File>
<File type="cust" partition="/dev/block/mmcblk0p18">cust.img</File>
<File type="userdata" partition="/dev/block/mmcblk0p19">userdata.img</File>
<File type="modemimage" partition="/dev/block/mmcblk0p13">modemimage.img</File>
<File type="boot" partition="/dev/block/mmcblk0p12">boot.img</File>
<File type="recovery" partition="/dev/block/mmcblk0p11">recovery.img</File>
<File type="md5rsa" filetype="signature">signature</File>
<File type="crc" filetype="checksum">crc</File>
</Files>
</Profile>
</Profiles>
<Profiles>
- Root tag of the xml file.
<Profile>
- Identifies a device
- attribute name: name of the device
- attribute author: author of the device
<Files>
- File root tag
<File>
- Identifies a file
- attribute sequence: sequence of the file in update.app
- attribute type: type of the file in the update.app
- attribute partition: destination partition on the device
- attribute filetype: can be one of the following values:
* signature: used to identify the signature file
* checksum: used to identify the checksum file
- value: file name
You can add or edit devices. If you want them to integrate in newer version, pm 'em to me.
I'm gonna make some auto update for the device file somewhere in the future
To add your devices profile you'll have to identify your device partitions and map them against the files inside the update.app.
Thread about identifying partitions: http://forum.xda-developers.com/showthread.php?t=1959445
Roadmap
- You tell me ...
Credits
ZeBadger ([email protected]) for figuring out the file headers
S34Qu4K3 for the P6 partition layout
ngamyarthar for adding ALOT of devices!
Changelog
v0.9.1.0
- Create update zip works now, this requires to have a PERFECT device entry in the devices file. The sequence is used to identify the file AND partition. Only files that have these two will be included in the zip. USE WITH CAUTION, MAKE SURE THE PARTITION IS CORRECT OR YOU'LL END UP FLASHING THE WRONG IMAGES TO THE WRONG PARTITION !! I'M NOT RESPONSABLE FOR BRICKING YOUR DEVICE! IF YOU DON'T KNOW WHAT YOU'RE DOING, THEN DON'T USE IT!
v0.9.1.1
- Added Type to the filelist (shows INPUT for g510 roms, but shows some useful info on P6 roms)
v0.9.2.0
- Files now can also be identified by the type attribute in devices.xml
- Added P6 device
v0.9.3.0
- Crc check during extract
- Crc check during creating flashable zip
- Added row to see file is flashable
v0.9.5.0
- Added repack
- Added icons and tooltip
- Added settings
- Experimental, no signing on repack, crc file gets generated
- Alot of stuff i forgot
v0.9.6.0
- Added command line options
v0.9.7.0
- Added G300 profile (thx ZeBadger)
- Added detailed info about the file (libmagic) in the tooltip on the extract list. This way it is easier to identify files inside the update.
(see screenshot). It will detect ext/fat/... partitions.
v0.9.7.1
- Alot of devices added in profiles (Credits to ngamyarthar, thanks alot dude!)
- Added android boot/recovery image recognition in magic.mgc
v0.9.7.2
- Made setup
-v0.9.7.4
- App will now remember last used profile.
- Fixed bug in repack code (remainder writing)
- Added signing options (During repack, once set, it will use the selected keyfile (PEM format) and algorithm to create the signature file. If there is no file selected or the file doesn't exist, it will use the existing signature file.)
Example of keyfile content:
Code:
-----BEGIN RSA PRIVATE KEY-----
MIICXgIBAAKBgQDU9GF9tdk59edEXWX4MEJNjMqGce/CqqGZSDBwnAzHITZYBm+y
ZEVkaOGGdPY7rmmWO6w3P/+nPVHO0kxA1/J+FY+sbUF7uz0kzVDxuW6t5KDc9Qr4
NRAE1ZzX0eB0aYpLImlqI7yigih6ds+Yp83mTbF+BiaFTLLtMVdWS7wQiwIDAQAB
AoGBAMok2E4+Sl9sfwU0K1E2bhmzJaQNj2wYEKGyFtkuKCr16eIQ6gJKkFxJ+ppp
eDsaynujVUx04bbczEUo9t0un603s5HAGq6USO5flERco0TlNw7xnTornPPrNxfU
sXOtIGzb0FlRuC129JqZJ9QsfvOyt3KIWwmJqc0R/k0xB8uRAkEA9+v1ohNXB8CL
plhQOtq0ueWrf9CCCeiqhf6ijg7UEegMLGKZ2gFMvMNwuojz/pbQmHdWTU9eC0k1
3yiAwHtcLQJBANvkvjXdzCYHO6nWOH1vf8DRLwCnwEteyxJ2qnrqKLS3fxCjWN4h
4vSNqgC9uoLEb/6T/72XTdG9gS8GsuoAupcCQBZ4eIb8IcM+HGozTvJGqGLBAk5P
Y7nqMKp8bddaWLZWxeOv/CnaPE5PmIQPra3BlZ58EoJnUyrKs+tKDIFlrPECQQC9
Ie0cxc4e81+0/+WMtkdq4EGOTbsO2NTP57NQj3E9pwqqk+UPApSEBgkwJAB1E2LE
1CVGvAoaGeYwPZHLxZ63AkEAugR+cC+5/BtTeMeXEcijnU0qkgkwLCMgTB1DIoMm
X0/wRGPPmZpGmMStHd+87ZxQSOiq5nAyZ4riFXLziUNOlA==
-----END RSA PRIVATE KEY-----
-v0.9.7.5
- Default sorting on filename
- Small changes in structure of profiles.xml
-v0.9.7.6
- Added progress for signing and checksum generation
- Extract/CreateZip order by offset
- Repack order by Signature, Checksum, Files
-v0.9.7.7
- Doubleclick on item in extract files listview copies tooltip text to clipboard
- Added detailed android boot/recovery image detection to magic.mgc
- Added SecVRL header (the 2048 byte header in front of fastboot/boot/recovery image) detection
-v0.9.7.8
- Added timestamp options in settings
- Added tooltips in settings
- Some ui changes (which hopefully fix the missing "..." button issue)
-v0.9.7.9
- Some small ui fixes
- When saved location of the app is on a monitor that isn't attached anymore, app location is restored to center of primary screen.
-v0.9.8.0
- Some small ui changes
- Sort profiles by name
- Remember last used directory
- Added profile for Huawei G526 (Credits Roman Dmitriev)
-v0.9.9.0
- Added compatibility for wine/mono
- Fixed bug in settings (Verify header checksum)
- Made the app localizable (Download the Resources_EN example, if you make a translation, make sure that your assembly start with "Resources_" and ends with the TwoLetterISOLanguageName (eg. EN for english) of your culture and put the assembly in the same directory as the application)
- Added profile for Huawei Ascend Mate 7 (Thanks to sketchykingy)
-v0.9.9.1
- Added missing translatable resources (updated Resources_EN)
- Added profile for Huawei MediaPad X1 7.0 (7D-503L) (Credits ElectroMyStyle)
-v0.9.9.2
- Fixed int overflow (extracting big files)
-v0.9.9.3
- Added drag/drop for files and folders.
-v0.9.9.5 - 12/12/2016
- Upgraded to .Net Framework 4.6.1
- Fixed libmagic calling convention
- Huawei Mediapad M2 8.0 (M2-802L) profile by @beast.in.black
- Huawei Ascend P8 (GRA-L09) profile by @nexolight
- Huawei Mate S profile by @philipp900
- Huawei P8 lite profile by @linus2014
- Huawei Honor 5x (Kiwi-L2X) profile by @deadman96385
26122015
Created an opensource c# library to work with update.app files:
https://github.com/worstenbrood/HuaweiUpdateLibrary
Enjoy
Download
- v0.9.9.3: Setup - Zip
- v0.9.9.5: Zip
Mirror
Donate if you like my work.
Is it possible to repack update.app?
If so, could you implemet such feature?
xan said:
Is it possible to repack update.app?
If so, could you implemet such feature?
Click to expand...
Click to collapse
Since i almost finished update zip creation (new version tomorrow), i have put it on the roadmap (already thought about it anyway )
The problem is sign the app, not repack it
Sent from my HUAWEI P6-U06 using xda app-developers app
S34Qu4K3 said:
The problem is sign the app, not repack it
Sent from my HUAWEI P6-U06 using xda app-developers app
Click to expand...
Click to collapse
I dont think its signed, but it has a per file per block checksum which should be correct...
worstenbrood said:
I dont think its signed, but it has a per file per block checksum which should be correct...
Click to expand...
Click to collapse
So, repack is useless, i tried it, you need to resign the app to make the new checksums match or it will give you an error when you flash it via default recovery.
Don't missunderstand me, is a great tool, and simplifies the unpack/repack for more unexperienced users, but without the sign, you can't flash it, that's what i say that is a bit useless (like the other scripts to unpack and repack)
S34Qu4K3 said:
So, repack is useless, i tried it, you need to resign the app to make the new checksums match or it will give you an error when you flash it via default recovery.
Don't missunderstand me, is a great tool, and simplifies the unpack/repack for more unexperienced users, but without the sign, you can't flash it, that's what i say that is a bit useless (like the other scripts to unpack and repack)
Click to expand...
Click to collapse
I'll investigate some more when i have the time. Also the signing part is why i actually made a function to create a flashable zip from it, this way you CAN flash it with a custom recovery (ok you need an unlocked bootloader, but why would'nt you do that anyway )
worstenbrood said:
I'll investigate some more when i have the time. Also the signing part is why i actually made a function to create a flashable zip from it, this way you CAN flash it with a custom recovery (ok you need an unlocked bootloader, but why would'nt you do that anyway )
Click to expand...
Click to collapse
That's great
Huawei Update Extractor
v0.9.2.0
- Files now can also be identified by the type attribute in devices.xml
- Added P6 device
Click to expand...
Click to collapse
Please add Ascend P2
Thanks
Carlos Varella said:
Please add Ascend P2
Thanks
Click to expand...
Click to collapse
S34Qu4K3 made a nice post on how to identify the partitions on your phone, after identifying them you have to map them to the files inside the update.app. Since i don't have access to an P2 i'm counting on you guys to complete the devices.xml file.
http://forum.xda-developers.com/showthread.php?t=2398404
Excellent work Worstenbrood! :good:
The tool is very good. I've tried with several Update.app and all OK.
It would be very interesting to get to repack the file Update.app because still do not have a custom recovery bootable. With the current cwm recovery can not extract files. Img a partition.
May you work on the file repack Update.app
The author Genokolar the custom recovery of Honor 2 miui port and a large majority of Huawei moblies have to pack and repack the file Update.app (over 4 months ago):
https://github.com/genokolar/unpacker_huawei/blob/master/unpack.php
That really says there that forked from tewilove / unpacker_huawei
Best Regards
Next version will have a repack function included, i'm adjusting the UI but most of the repacking code is already written.
worstenbrood said:
Next version will have a repack function included, i'm adjusting the UI but most of the repacking code is already written.
Click to expand...
Click to collapse
Excellent news!
Update to v0.9.5.0, added repack function, it only repacks the file + recalculates all checksums and the checksum file. No signing is done yet ! Since i have no access to a huawei device atm it would be nice to see some results (i'm wondering if the order of the files inside the update.app is important)
Thank you for the update. BTW, the Huawei Ascend Mate has the same partition information as the P6 so should be easy to add to the tool. I've been using it to unpack Mate updates with success.
flibblesan said:
Thank you for the update. BTW, the Huawei Ascend Mate has the same partition information as the P6 so should be easy to add to the tool. I've been using it to unpack Mate updates with success.
Click to expand...
Click to collapse
Then it is just a matter of cloning the P6 profile inside the profiles.xml and changing the Name attribute or changing the name so that it suits both...
Any updates may be sent to me
worstenbrood said:
Then it is just a matter of cloning the P6 profile inside the profiles.xml and changing the Name attribute or changing the name so that it suits both...
Any updates may be sent to me
Click to expand...
Click to collapse
Confirm, it work too with D1QXL
Amazing, I found anywhere and none of them work. Great Tool
My I ask one feature? pack/unpack *.img
In my device, Ascend D1 Quad XL, every image has additional 2048 header before ANDROID magic word.
To extract boot.img/recovery.img, dsixda's Android Kitchen remove the 2048 header, save as new boot.img then extract it. Repack it.
But then, the repack image have no 2048 header. So I can't flash it manually to device.
Would yo learn/track this 2048 header
Thank's
twins.7 said:
Confirm, it work too with D1QXL
Amazing, I found anywhere and none of them work. Great Tool
My I ask one feature? pack/unpack *.img
In my device, Ascend D1 Quad XL, every image has additional 2048 header before ANDROID magic word.
To extract boot.img/recovery.img, dsixda's Android Kitchen remove the 2048 header, save as new boot.img then extract it. Repack it.
But then, the repack image have no 2048 header. So I can't flash it manually to device.
Would yo learn/track this 2048 header
Thank's
Click to expand...
Click to collapse
Thanks.
I want to keep the app as generic as possible, you can easily write a bat file that does that
worstenbrood said:
Thanks.
I want to keep the app as generic as possible, you can easily write a bat file that does that
Click to expand...
Click to collapse
No, I mean this 2048 header are unique. That's why I need your help to determine contain of header.
without that header I can't flash img to device. Each change in img, the header must change too.
twins.7 said:
Confirm, it work too with D1QXL
Amazing, I found anywhere and none of them work. Great Tool
My I ask one feature? pack/unpack *.img
In my device, Ascend D1 Quad XL, every image has additional 2048 header before ANDROID magic word.
To extract boot.img/recovery.img, dsixda's Android Kitchen remove the 2048 header, save as new boot.img then extract it. Repack it.
But then, the repack image have no 2048 header. So I can't flash it manually to device.
Would yo learn/track this 2048 header
Thank's
Click to expand...
Click to collapse
twins.7 said:
No, I mean this 2048 header are unique. That's why I need your help to determine contain of header.
without that header I can't flash img to device. Each change in img, the header must change too.
Click to expand...
Click to collapse
Share an image with me (with the header included) and i'll take a look when i have some time.
How to Port MT6582 to MT6582
OR,
How to Port all MTK Device KITKAT & JellyBean(MT65xx & MT65xx)
It is very esy.....
Requirements :
*Windows XP/7/8
* 7-Zip
* Notepad++
* Java Jdk
*Cywing
* Boot.img Unpack/Repack Tools or Android kitchen
* Stock ROM
*Port RomRom
[N.B : There are two type roms
1. Stock rom [ orginal rom from your mobile ]
2. Port rom [ Whichever you want to port rom ]]
*SO NOW PORTING START......
# TIPS FOR SYSTEM FOLDER
+++ Replace it from your stock rom to the port rom
##jelly Bean
*system/etc/firmware [[Delete to port Rom & Copy from Stock Rom]]
*system/etc/permission/platform.xml
*system/etc/permission/handheld_core_hardware.xml
*system/lib/hw [[Delete to port Rom & Copy from Stock Rom]]
*system/lib/modules [[Delete to port Rom & Copy from Stock Rom]]
*system/lib/ libaudio.primary.default.so
*system/lib/ libcamdrv.so
*system/lib/libcamalgo.so
*system/lib/libcameracustom.so
*system/lib/libdpframework.so
*system/lib/ libsensorservice.so
*system/lib/libvcodecdrv.so
*system/lib/libsync.so
*system/usr/keylayout
##KITKAT ONLY
*system/bin/pq
*system/bin/vold
*system/etc/bluetooth
*system/etc/firmware
*system/etc/permission/platform.xml
*system/etc/permission/handheld_core_hardware.xml
*system/etc/wifi
*system/etc/apns-conf.xml
*system/lib/egl [[Delete to port Rom & Copy from Stock Rom]]
*system/lib/hw [[Delete to Port Rom & Copy from Stock Ron]]
*system/lib/modules [[Delete to port rom & Copy from stock rom]]
*system/lib/libaudio.primary.default.so
*system/lib/libcamdrv.so
*system/lib/libcamalgo.so
*system/lib/libcameracustom.so
*system/lib/libcameraservice.so
*system/lib/libdpframework.so
*system/lib/libsensorservice.so
*system/lib/lilbinput.so
*system/lib/libinputservice.so
*system/lib/libvcodecdrv.so
*system/lib/libsync.so
*system/usr/keylayout
*system/vendor [[Delete to Port Rom & Copy from stock rom Stock Rom ]]
*system/xbin/libmnlp_mt65xx
[N.B Some Rom Not Port, Flow The Next 2 Step ]
STEP 1
*system/bin/pq
*system/bin/vold
*system/etc/bluetooth
*system/etc/firmware
*system/etc/permission/platform.xml
*system/etc/permission/handheld_core_hardware.xml
*system/etc/wifi
*system/etc/apns-conf.xml
*system/lib [Delete Port Lib Folder And Pest Stock Lib Folder ]
*system/usr/keylayout
*system/vendor [[Delete to Port Rom & Copy from stock rom Stock Rom]]
*system/xbin/libmnlp_mt65xx
STEP 2
## Delete to some folder port rom & copy form same folder stock rom
*system/bin
*system/etc
*system/lib
*system/usr
*system/vendor
*seystem/xbin
N.B : Some rom not port
[ FIXING PROBLEM ]
Sim card problem :
*system/bin
SD Card Problem :
*system/bin/vold
*system/etc/vold.fstab
*system/etc/vold.fstab.nand
Camera Focus Problem :
*system/lib/libcameraservice.so
Boot loop problem :
*system/lib/libandroid_runtime.so
*system/lib/libandroid_servers.so
*system/lib/libmedia_jni.so
Other Problem :
*system/etc/dhcpcd
*system/etc/permissions
*system/etc/security
*system/etc/audio
*system/etc/bluetooth
*system/etc/wifi
*system/lib/drm
*system/lib/egl
*system/lib/soundfx
* Replace the stock boot.img to port rom
* Now open the Port rom folder go to META-INF/google/Android / and open updater-script in Notpad++
And change these line.......
[mmcblkOp3 ----- mmcblkOp9]
* Now go to back the folder of port rom and you will see two folder and one file name
+ META-INF
+ system
+ boot.img
* Now select these 2 folder 1 file and click right mouse button and click on 7zip ->> add to archive
* Now a dialouge box should
appear!
* Configure the Format like This:
Archive format: ZIP
Compression Level : Normal
Compression Method: Deflate
Dictoioany Size: 32k
Word Size 32
* Now Start Zipping and Push the
ZIP to your Memory Card
* Go to Recovery >> Install ZIP &
Wipe Data
Finished!!
[# Camera Drive problem fixing]
* Extract the boot.img for android kitchen [ Both stock & port boot.img]
* and open init.rc/# camera
* Find these missing line port to stock boot.img and whole missing line paste it (#Camera)
Example :
#Camera
chmod 0660 /dev/camera-sysram
chmod 0660 /dev/camera-isp
chmod 0660 /dev/camera-pipemgr
chmod 0660 /dev/kd_camera_hw
chmod 0660 /dev/kd_camera_flashlight
chmod 0660 /dev/kd_camera_hw_bus2
chmod 0660 /dev/FM50AF
chmod 0660 /dev/OV8825AF
chmod 0660 /dev/OV88252AF
chmod 0660 /dev/OV8850AF
chmod 0660 /dev/CAM_CAL_DRV
chown system camera /dev/camera-sysram
chown system camera /dev/camera-isp
chown system camera /dev/camera-pipemgr
chown system camera /dev/kd_camer
______________A.s. Noman Khan
Hi I got a mtk6582 device, I got a similar phone in Malaysia/Indonesia they called it Evercoss A7V in my country we call it cloudfone excite 502q, i was able to install their rom (Galaxy S5) the only thing here is the camera, it says could not connect to the camera... what steps should I do?
tested?
I guess the first question I have to ask is have you tested this on any custom ROM?
"...It is very esy....." REALLY?!?
Did you do it practically? If so then could you please mention from which device to which you ported???
Because I can see many senior developers here are trying to do it. But, there is no success... but, you did it with just mere notepad. BRAVO!
solv
sirhca13 said:
Hi I got a mtk6582 device, I got a similar phone in Malaysia/Indonesia they called it Evercoss A7V in my country we call it cloudfone excite 502q, i was able to install their rom (Galaxy S5) the only thing here is the camera, it says could not connect to the camera... what steps should I do?
Click to expand...
Click to collapse
MT6582 mobile camera not conect:
STEP 1:
copy these from stock ROM to port ROM
system\lib\hw\camera.default.so
(N.B.if you have two files like camera.goldfish.so delete this the one with the goldfish)
system/lib/ libcamdrv.so
system/lib/libcamalgo.so
system/lib/libcameracustom.so
system/lib/libdpframework.so
system\etc\permissions\android.hardware.camera.xml
STEP 2:
unpcack the boot.img from Port ROM
open init.rc file add/replace below lines
#Camera
#chmod 0660 /dev/FM50AF
chmod 0660 /dev/OV8825AF
chmod 0660 /dev/CAM_CAL_DRV
#chown system camera /dev/FM50AF
chown system camera /dev/OV8825AF
chown system camera /dev/CAM_CAL_DRV
& repack boot.img
####
Camera Force closed or camera not conect :
copy these from stock rom to port Rom
system\lib\hw\camera.default.so
system\lib\libcamera_client.so
system\lib\libcameracustom.so
system\lib\libcameraprofile.so
system\lib\libcameraservice.so
system\lib\libmhal.so
system\lib\libmhalcontent.so
system\lib\libmhaldrv.so
system\lib\libmhalmdp.so
system\lib\libmhalpipe.so
system\lib\libmhalscenario.so
system\lib\libmhalutility.so
system\etc\permission\android.hardware.camera.front.xml
system\etc\permission\android.hardware.camera.xml
FOR CAMERA NOT CONNECTED ISSUE /CAMERA GREEN /CAMERA FORCE CLOSE "unfortunately camera has stopped"
Replace first libcamdrv.so (needed for 6582
devices) and check if not success then replace
libcameraservice.so from/lib.
Camera Focus Problem :
system/lib/libcameraservice.so
system/lib/libfeatureio.so from
[NB:These step not required for some mobile]
Thanks Bro for the Guide
thanks bro for this nice guide :good:
but bro my phone get bricked every time while porting this rom (http://forum.xda-developers.com/android/development/themed-aosp-kk-gionee-m2-t2949199) to my micromax a120 kk.
Bro please help me.... how can i port this rom to my device. :crying:
i try to port to my lenovo s860...
4.2.2 JB for miui and aosp..
bug on internal storage unmount and loudspeaker problem..
i try many time to put vold.fstab and vold.fstab.nand...but still problem
on camera show "Please insert sd card before using camera"
but this s860 doesnt have sdcard slot..
please help me...
Sd card mount
ghaf85 said:
i try to port to my lenovo s860...
4.2.2 JB for miui and aosp..
bug on internal storage unmount and loudspeaker problem..
i try many time to put vold.fstab and vold.fstab.nand...but still problem
on camera show "Please insert sd card before using camera"
but this s860 doesnt have sdcard slot..
please help me...
Click to expand...
Click to collapse
Replace Stock to Port...
System/bin/vold
How to port Lollipop ROM from Android one Device to Micromax Unite 2 both being MT6582 device, but OS, Android one being 5.1, and Unite 2 5.0???
Good day. may carry the rom 5.0 lollipop doogee DG700 any other mtk6582? regards
error
Hi big thanks for you bro!:good:
btw my device is accessgo a4e which spesification is similiar to wiko raibow.
I got problen after porting wiko raibow's ROM (Cleankat by umang) to my device there was a message from CMW "Installation aborted" when I was flashing the rom
can you help me?
Try to flash through another CWM
Sent from my Micromax A106 using XDA Free mobile app
Everything is operating normally
but
Opened off screen is black
light sensor does not work
Full light continuously
How do I fix
good but
hey bro i ported some roms to my 6582 but i have a problem is when i port and flash my custom rom, my cel lost the imei and i dont have any solution (MTK droid and tools, xposed, mobile uncle tools etc) <-------------- anithing of this apps could restore my imei help pls:crying::crying::crying::good:
Can I port lollipop?
Selviiin said:
hey bro i ported some roms to my 6582 but i have a problem is when i port and flash my custom rom, my cel lost the imei and i dont have any solution (MTK droid and tools, xposed, mobile uncle tools etc) <-------------- anithing of this apps could restore my imei help pls:crying::crying::crying::good:
Click to expand...
Click to collapse
Hello sir,
Use mobile uncle imei writer tool. Just install it on PC and fallow the process on prompt window.its so easy.and after you making that file (file name should like this MP_0B1).
=>>copy that file and paste it on below location in your phone root.
Root >> data >> nvram >> Md >> Nvd_imei >> place that file and change the permissions to rw-rw-rw.
=>> Restart it and you back to your signal......
A.S.Noman Khan said:
How to Port MT6582 to MT6582
OR,
How to Port all MTK Device KITKAT & JellyBean(MT65xx & MT65xx)
It is very esy.....
Requirements :
*Windows XP/7/8
* 7-Zip
* Notepad++
* Java Jdk
*Cywing
* Boot.img Unpack/Repack Tools or Android kitchen
* Stock ROM
*Port RomRom
[N.B : There are two type roms
1. Stock rom [ orginal rom from your mobile ]
2. Port rom [ Whichever you want to port rom ]]
*SO NOW PORTING START......
# TIPS FOR SYSTEM FOLDER
+++ Replace it from your stock rom to the port rom
##jelly Bean
*system/etc/firmware [[Delete to port Rom & Copy from Stock Rom]]
*system/etc/permission/platform.xml
*system/etc/permission/handheld_core_hardware.xml
*system/lib/hw [[Delete to port Rom & Copy from Stock Rom]]
*system/lib/modules [[Delete to port Rom & Copy from Stock Rom]]
*system/lib/ libaudio.primary.default.so
*system/lib/ libcamdrv.so
*system/lib/libcamalgo.so
*system/lib/libcameracustom.so
*system/lib/libdpframework.so
*system/lib/ libsensorservice.so
*system/lib/libvcodecdrv.so
*system/lib/libsync.so
*system/usr/keylayout
##KITKAT ONLY
*system/bin/pq
*system/bin/vold
*system/etc/bluetooth
*system/etc/firmware
*system/etc/permission/platform.xml
*system/etc/permission/handheld_core_hardware.xml
*system/etc/wifi
*system/etc/apns-conf.xml
*system/lib/egl [[Delete to port Rom & Copy from Stock Rom]]
*system/lib/hw [[Delete to Port Rom & Copy from Stock Ron]]
*system/lib/modules [[Delete to port rom & Copy from stock rom]]
*system/lib/libaudio.primary.default.so
*system/lib/libcamdrv.so
*system/lib/libcamalgo.so
*system/lib/libcameracustom.so
*system/lib/libcameraservice.so
*system/lib/libdpframework.so
*system/lib/libsensorservice.so
*system/lib/lilbinput.so
*system/lib/libinputservice.so
*system/lib/libvcodecdrv.so
*system/lib/libsync.so
*system/usr/keylayout
*system/vendor [[Delete to Port Rom & Copy from stock rom Stock Rom ]]
*system/xbin/libmnlp_mt65xx
[N.B Some Rom Not Port, Flow The Next 2 Step ]
STEP 1
*system/bin/pq
*system/bin/vold
*system/etc/bluetooth
*system/etc/firmware
*system/etc/permission/platform.xml
*system/etc/permission/handheld_core_hardware.xml
*system/etc/wifi
*system/etc/apns-conf.xml
*system/lib [Delete Port Lib Folder And Pest Stock Lib Folder ]
*system/usr/keylayout
*system/vendor [[Delete to Port Rom & Copy from stock rom Stock Rom]]
*system/xbin/libmnlp_mt65xx
STEP 2
## Delete to some folder port rom & copy form same folder stock rom
*system/bin
*system/etc
*system/lib
*system/usr
*system/vendor
*seystem/xbin
N.B : Some rom not port
[ FIXING PROBLEM ]
Sim card problem :
*system/bin
SD Card Problem :
*system/bin/vold
*system/etc/vold.fstab
*system/etc/vold.fstab.nand
Camera Focus Problem :
*system/lib/libcameraservice.so
Boot loop problem :
*system/lib/libandroid_runtime.so
*system/lib/libandroid_servers.so
*system/lib/libmedia_jni.so
Other Problem :
*system/etc/dhcpcd
*system/etc/permissions
*system/etc/security
*system/etc/audio
*system/etc/bluetooth
*system/etc/wifi
*system/lib/drm
*system/lib/egl
*system/lib/soundfx
* Replace the stock boot.img to port rom
* Now open the Port rom folder go to META-INF/google/Android / and open updater-script in Notpad++
And change these line.......
[mmcblkOp3 ----- mmcblkOp9]
* Now go to back the folder of port rom and you will see two folder and one file name
+ META-INF
+ system
+ boot.img
* Now select these 2 folder 1 file and click right mouse button and click on 7zip ->> add to archive
* Now a dialouge box should
appear!
* Configure the Format like This:
Archive format: ZIP
Compression Level : Normal
Compression Method: Deflate
Dictoioany Size: 32k
Word Size 32
* Now Start Zipping and Push the
ZIP to your Memory Card
* Go to Recovery >> Install ZIP &
Wipe Data
Finished!!
[# Camera Drive problem fixing]
* Extract the boot.img for android kitchen [ Both stock & port boot.img]
* and open init.rc/# camera
* Find these missing line port to stock boot.img and whole missing line paste it (#Camera)
Example :
#Camera
chmod 0660 /dev/camera-sysram
chmod 0660 /dev/camera-isp
chmod 0660 /dev/camera-pipemgr
chmod 0660 /dev/kd_camera_hw
chmod 0660 /dev/kd_camera_flashlight
chmod 0660 /dev/kd_camera_hw_bus2
chmod 0660 /dev/FM50AF
chmod 0660 /dev/OV8825AF
chmod 0660 /dev/OV88252AF
chmod 0660 /dev/OV8850AF
chmod 0660 /dev/CAM_CAL_DRV
chown system camera /dev/camera-sysram
chown system camera /dev/camera-isp
chown system camera /dev/camera-pipemgr
chown system camera /dev/kd_camer
______________A.s. Noman Khan
Click to expand...
Click to collapse
I think this should work if both roms have the same kernel
Sent from my B15Q using XDA Free mobile app
Thanks for the guide!
Can i use this guide to port rom for my device?
But i my stock rom is aosp lollipop.
Which files or folders i must change?
Please help me!
5.1 to mt6582
Harikrish44 said:
How to port Lollipop ROM from Android one Device to Micromax Unite 2 both being MT6582 device, but OS, Android one being 5.1, and Unite 2 5.0???
Click to expand...
Click to collapse
try this : http://en.miui.com/thread-156445-1-1.html