Guys,
I downloaded the nAa kernel file (.zip) and i couldnt find the .ftf file in it. Which is the only thing that we have to use for flashing the kernel. Am i missing any thing? or are there any other download link. Please help.
ZIP? What file have you been downloading?
--> http://minicm.googlecode.com/files/E15_nAa-11_2.6.29.6-nAa-11.ftf
The link, copied out of nAa's OP post of his thread, clearly links to a FTF - not a ZIP.
You now got the FTF or did your browser download a ZIP again?
This .zip file is the .ftf file but with changed filetype. Simply change the filetype manualy and everything will be ok
Hey thanks man.. can i go ahead and flash this kernel file? i am just asking agian to ensure that i dont brick my phone
Bolussimo said:
This .zip file is the .ftf file but with changed filetype. Simply change the filetype manualy and everything will be ok
Click to expand...
Click to collapse
i am downloading the file from the nAa post where its mentioned to download the .ftf file here.. however which i click on it, it will download the zip file where i see one folder and two other files but no ftf file. So should i change the file type from .zip to .ftf?
ghost9685 said:
So should i change the file type from .zip to .ftf?
Click to expand...
Click to collapse
yes. i had this problem problem too
just rename it... and at the end set .ftf
ghost9685 said:
Hey thanks man.. can i go ahead and flash this kernel file? i am just asking agian to ensure that i dont brick my phone
Click to expand...
Click to collapse
dont worry.... don't make brick... If kernel is incorrect, flashtool drop error, and no change... The ftf extension is uncompressed zip... simply rename ftf, and flash with flashtool... The extension change is browser bug... I see the bug in Opera... If installed winzip, or winrar, and download a file with non zip or rar extension, but filetype is zip or rar, teh browser rename it...
Daveee10 said:
The ftf extension is uncompressed zip...
Click to expand...
Click to collapse
WRONG! A FTF (FlashToolFirmware) bundle actually IS a compressed and signed ZIP file carrying a .ftf extension instead of .zip. It's the same as a APK being a ZIP (sometimes even signed) carrying compiled data inside or as a Java JAR being a ZIP carrying Java classes and stuff inside.
All of them are ZIPs, hence COMPRESSED!
Daveee10 said:
The extension change is browser bug... I see the bug in Opera... If installed winzip, or winrar, and download a file with non zip or rar extension, but filetype is zip or rar, teh browser rename it...
Click to expand...
Click to collapse
You may want to add Internet Explorer to that list ... the 2nd most stupid browser right behind that thing from that Norwegian drama queens who will happily ***** about competition to the EU trade commission.
ghost9685 said:
Hey thanks man.. can i go ahead and flash this kernel file? i am just asking agian to ensure that i dont brick my phone
Click to expand...
Click to collapse
First make sure you've unlocked your BL...
Sent from my E15i using xda premium
@B.Jay:
Sorry. You're right. The FTF is signed file, and a ZIP archive, but the compression level is zero. Far as I know. Correct me if I'm wrong, because, i don't know all, but willing to learn the more...
I don't know people why use the IE... That a dead browser... Almost nothing is not supported
They use IE to download another browser Sorry for OT
Daveee10 said:
@B.Jay:
Sorry. You're right. The FTF is signed file, and a ZIP archive, but the compression level is zero. Far as I know. Correct me if I'm wrong, because, i don't know all, but willing to learn the more...
Click to expand...
Click to collapse
Yes, you're right that a FTF is a zero-compression level ZIP (-0 commandline parameter of PKZIP which means "store only"). Ignore the slight difference in packed and unpacked size, that's just the PKZIP header and metadata:
Code:
$ zipinfo ./X8_E15i_Baseband_015.ftf
Archive: X8_E15i_Baseband_015.ftf
Zip file size: 27949955 bytes, number of entries: 8
-rw---- 2.0 fat 107 bX defN 11-Mar-03 08:29 META-INF/MANIFEST.MF
-rw---- 2.0 fat 408307 bl defN 11-Mar-03 08:29 amss_fs.sin
-rw---- 2.0 fat 731045 bl defN 11-Mar-03 08:29 fota1.sin
-rw---- 2.0 fat 639 bl defN 11-Mar-03 08:29 cache.sin
-rw---- 2.0 fat 6181914 bl defN 11-Mar-03 08:29 kernel.sin
-rw---- 2.0 fat 731045 bl defN 11-Mar-03 08:29 fota0.sin
-rw---- 2.0 fat 19792794 bl defN 11-Mar-03 08:29 amss.sin
-rw---- 2.0 fat 98883 bl defN 11-Mar-03 08:29 loader.sin
8 files, 27944734 bytes uncompressed, 27949017 bytes compressed: [COLOR="Red"]0.0%[/COLOR]
APKs, in this example the signed version of the xRecovery installer, are compressed.
Code:
$ zipinfo ./xRecovery_Installer_v0.1.apk
Archive: xRecovery_Installer_v0.1.apk
Zip file size: 1712242 bytes, number of entries: 19
-rw---- 2.0 fat 1249 bX defN 11-Jan-15 06:08 META-INF/MANIFEST.MF
-rw---- 2.0 fat 1302 bl defN 11-Jan-15 06:08 META-INF/CERT.SF
-rw---- 2.0 fat 1714 bl defN 11-Jan-15 06:08 META-INF/CERT.RSA
-rw---- 2.0 fat 4432 bl defN 11-Jan-15 06:08 resources.arsc
-rw---- 2.0 fat 14368 bl defN 11-Jan-15 06:08 classes.dex
-rw---- 1.0 fat 694 b- stor 10-Dec-15 20:52 res/drawable/warning_16.png
-rw---- 2.0 fat 2740 bl defN 11-Jan-15 06:08 res/layout/main.xml
-rw---- 2.0 fat 735308 bl defN 11-Jan-15 06:08 res/raw/busybox
-rw---- 1.0 fat 1984 b- stor 10-Dec-15 20:52 res/drawable-ldpi/icon.png
-rw---- 1.0 fat 1009 bx stor 10-Dec-15 20:52 res/drawable/block_16.png
-rw---- 2.0 fat 1668 bl defN 11-Jan-15 06:08 AndroidManifest.xml
-rw---- 2.0 fat 2263040 bl defN 11-Jan-15 06:08 res/raw/xrecovery.tar
-rw---- 1.0 fat 3797 b- stor 10-Dec-15 20:52 res/drawable-mdpi/icon.png
-rw---- 1.0 fat 1116 b- stor 10-Dec-15 20:52 res/drawable/info_16.png
-rw---- 1.0 fat 1005 b- stor 10-Dec-15 20:52 res/drawable/search_16.png
-rw---- 2.0 fat 471 bl defN 11-Jan-15 06:08 res/raw/chargemon
-rw---- 1.0 fat 617 b- stor 10-Dec-15 20:52 res/drawable/tick_16.png
-rw---- 1.0 fat 6314 b- stor 10-Dec-15 20:52 res/drawable-hdpi/icon.png
-rw---- 2.0 fat 596 bl defN 11-Jan-15 06:08 res/menu/mainmenu.xml
19 files, 3043424 bytes uncompressed, 1709796 bytes compressed: [COLOR="red"]43.8%[/COLOR]
The same goes for xRecovery and CWM update ZIPs, they are actually compressed to reduce filesize - and of course .jar files are also compressed.
As for the browser ZIP vs FTF glitch - that most likely happens when the browser decides that since the web-server reports a "application/x-zip" header the extension should therefore be .zip and not something else (like .ftf). That is actually a somewhat lousy configuration of the web-server software in question as one can influence what the server reports in relation to extensions (i.e. setting .ftf to "application/x-binary").
Like we already worked out IE and Opera are notoriously known to tinker around with file extensions based on the header they get from the web-server - Firefox and Chrome/Chromium honor the filenames as given by the web-server.
droidx8 said:
First make sure you've unlocked your BL...
Sent from my E15i using xda premium
Click to expand...
Click to collapse
Yes, thanks. I have done that
ghost9685 said:
Yes, thanks. I have done that
Click to expand...
Click to collapse
Thanks every one.. it was the Opera which converted the .ftf to .zip.. I opened the link with IE and i did get the .ftf file.. Thanks every one for help I have flashed the nAa Kernel... but why i am not able to see the kernel version on my device in the settings? and i am not able to mount my SD card. Any suggestions?
ghost9685 said:
I have flashed the nAa Kernel... but why i am not able to see the kernel version on my device in the settings? and i am not able to mount my SD card. Any suggestions?
Click to expand...
Click to collapse
As I wrote in the other thread of yours...
GingerDX is not meant to work with nAa's Kernel.
nAa's Kernel is meant for MiniCM7 (and other custom ROMs based thereon also requiring nAa's Kernel to operate). In there you will find the missing settings.
GingerDX is meant to work on Stock Kernel (with the Stock Kernel Modules AddOn), LinuxDX (the Kernel made by doixanh) and Alfs (the Kernel made by alfsamsung).
Related
Dear frends... I'm a beginner... I have extracted boot.img file from .tar.md5 file... I have added COOPER.rle(with my custom splash screen) file to the ramdisk... then i created boot.img file with my new cooper.rle file... copied this boot.img to the firmware folder which i exracted from .tar.md5 file.. This is wer I am struck now... I dont kno to create the .tar.md5 file for odin... how do i create?? pls elp me bros... My aim is to change the bootlogo (Splash screen).... anybody help me with that...
Go to freeyourandroid.com,there's a guide iin there that explans this
Insert witty sentence here
arunagiriarun said:
Dear frends... I'm a beginner... I have extracted boot.img file from .tar.md5 file... I have added COOPER.rle(with my custom splash screen) file to the ramdisk... then i created boot.img file with my new cooper.rle file... copied this boot.img to the firmware folder which i exracted from .tar.md5 file.. This is wer I am struck now... I dont kno to create the .tar.md5 file for odin... how do i create?? pls elp me bros... My aim is to change the bootlogo (Splash screen).... anybody help me with that...
Click to expand...
Click to collapse
Easy ... Flash the boot.img from recovery!
SnowPluralism said:
Easy ... Flash the boot.img from recovery!
Click to expand...
Click to collapse
He needs an updater script for that
Insert witty sentence here
Prawesome said:
He needs an updater script for that
Insert witty sentence here
Click to expand...
Click to collapse
I'll post one here in a bit
Sent from my GT-S5830 using xda premium
---------- Post added at 05:34 PM ---------- Previous post was at 05:25 PM ----------
Dude drag your boot.img file into the zip file in the attachment
Copy file to sd-card
Boot Into ClockWorkMode Recovery
Flash It ... Done ...
help me..
SnowPluralism said:
I'll post one here in a bit
Sent from my GT-S5830 using xda premium
---------- Post added at 05:34 PM ---------- Previous post was at 05:25 PM ----------
Dude drag your boot.img file into the zip file in the attachment
Copy file to sd-card
Boot Into ClockWorkMode Recovery
Flash It ... Done ...
Click to expand...
Click to collapse
Thanks a lot for your reply frends...
I have done as u told... But i'm trapped in bootloop... i have tried every option but stil i'm not able to correct it.. Now I planned to flash with original gingerbread firmware...
All I wanted to do is to change the Splash SCreen(Boot Logo which reads SAMSUNG GALAXY ACE)..
Wat I have done is the following...
1. I have converted a .png file (320X280) into .rle file and named it as COOPER.rle
2. Then I have renamed a Firmware.tar.md5 file into Firmware.tar..
3. Then I extracted Firmware.tar by using winrar..
4. Then I copied the boot.img file which is in Firmware folder which i extracted from Firmware.tar to some other location say D:\
5. Then I unpacked the boot.img file with the help of the tutorial which i have attached attached
6. Then I copied the COOPER.rle which i created in the 1st point and pasted in ramdisk.
7. Then I packed the boot.img file. This is how i created the boot.img.
Pls tell me if I have done anything wrong..... And do help me to change the Splash screen (Boot logo which reads SAMSUNG GALAY ACE)...
Thanks in advance...
Any replies???????:crying:
Hey,
After a lot searching i have extract my .kdz file to 2 different files. a .dll and a .dz file. I am searching how can i get those files working in the Smartflashtool. Sow i need a app bin and a CP bin, On this moment i need to know how can i get those files?
- Can i extract a .kdz to a .wdb and .dll sow after that i can extract those to app bin and cp bin?
- Can i extract a .dz file after that compile it to .wdb and do the first step again?
- Is it possible to get from the .dz file also the app bin and the cp bin?
Wrong section sorry
Johrans said:
Hey,
After a lot searching i have extract my .kdz file to 2 different files. a .dll and a .dz file. I am searching how can i get those files working in the Smartflashtool. Sow i need a app bin and a CP bin, On this moment i need to know how can i get those files?
- Can i extract a .kdz to a .wdb and .dll sow after that i can extract those to app bin and cp bin?
- Can i extract a .dz file after that compile it to .wdb and do the first step again?
- Is it possible to get from the .dz file also the app bin and the cp bin?
Wrong section sorry
Click to expand...
Click to collapse
1)
kdz is a archive format, you can't choose what you get out of it. (It's like saying I want a image out of that random zip file)
Click to expand...
Click to collapse
2)
Ask novassoc He said some time ago he's working on dz files.
It should already be possible to extract dz file though, Check on the Optimus G forum.
I don't know to what it extracts possible bin/fls.
Click to expand...
Click to collapse
3)
Again I don't know to what it extracts and if or if not it's possible to revert to dz format. Should be possible.
Click to expand...
Click to collapse
I can give you lot more info about bin files if your interested, but you'd have to ask novassoc about kdz and wdb.
If dz decompiles to bin/fls then you should be able to create the dz file again, but after extracting the bin/fls file you should not create a bin/fls file again. It's possible, but it could kill your phone since emergency recovery usually relies on first or second stage bootloader and the bin/fls files overwrites it when flashing it on your phone and if something goes wrong.
xonar_ said:
1)
2)
3)
I can give you lot more info about bin files if your interested, but you'd have to ask novassoc about kdz and wdb.
If dz decompiles to bin/fls then you should be able to create the dz file again, but after extracting the bin/fls file you should not create a bin/fls file again. It's possible, but it could kill your phone since emergency recovery usually relies on first or second stage bootloader and the bin/fls files overwrites it when flashing it on your phone and if something goes wrong.
Click to expand...
Click to collapse
Thanks, Let we say we have the next files from different phones like the lg L5 e610 it has as firmware files a .dz and a .dll i know the .kdz files haves those files from those firmware. and also when it isnt a .kdz file its possible to encrypt it to .kdz
You know a lot about bin files. What contains a App.bin and a CP.bin when you use it for the SmartFlashTool. Because i wanne try to get from the Firmware files like ( .kdz or .dll or .dz) a app.bin and cp.bin,
Johrans said:
Thanks, Let we say we have the next files from different phones like the lg L5 e610 it has as firmware files a .dz and a .dll i know the .kdz files haves those files from those firmware. and also when it isnt a .kdz file its possible to encrypt it to .kdz
You know a lot about bin files. What contains a App.bin and a CP.bin when you use it for the SmartFlashTool. Because i wanne try to get from the Firmware files like ( .kdz or .dll or .dz) a app.bin and cp.bin,
Click to expand...
Click to collapse
Yes. There is already a tool somewhere to create kdz archive (One of LG's ones, you just have to use WindowsEnabler to get the option)
The bin file (AP) is basically a collection of data blocks and each data blocks usually correspond to partitions on the device.
The first meg is the header which contains the info about all the data blocks
like size on file,offset on file,size on device,offset on disk etc.
The layout of the header seems to be different for each phone. You can identify what type of bin file it is from it's magic number.
Then after the header the data blocks are just appended to the file. Doesn't have to be since the header allows there to be gaps and overlapping data blocks, but thats not practical so it will probably never be any other way.
You can check my tool for extracting bin files here. You can get alot more info on exactly how it's set out in my git by reading the sources.
I don't know to much about the fls file (CP) besides that it does a raw write of everything after what appears to be the header to somewhere in my phones nv partition and contains baseband information.
xonar_ said:
Yes. There is already a tool somewhere to create kdz archive (One of LG's ones, you just have to use WindowsEnabler to get the option)
The bin file (AP) is basically a collection of data blocks and each data blocks usually correspond to partitions on the device.
The first meg is the header which contains the info about all the data blocks
like size on file,offset on file,size on device,offset on disk etc.
The layout of the header seems to be different for each phone. You can identify what type of bin file it is from it's magic number.
Then after the header the data blocks are just appended to the file. Doesn't have to be since the header allows there to be gaps and overlapping data blocks, but thats not practical so it will probably never be any other way.
You can check my tool for extracting bin files here. You can get alot more info on exactly how it's set out in my git by reading the sources.
I don't know to much about the fls file (CP) besides that it does a raw write of everything after what appears to be the header to somewhere in my phones nv partition and contains baseband information.
Click to expand...
Click to collapse
Thanks, but still i am thinking why are there extractors for the kdz-> to cab -> to.wdb and .dll -> to App bin and CP bin but not from the kdz-> to cab -> .dz and .dll -> to App bin and CP bin.
is there sow big difference between the .dz and .wdb
I don't know much about what your talking here. I know that the complete firmware from LG comes in a v....kdz package. I know that ...cab containers are Microsoft's preferred format (something like ...zip or ...rar). I know ...bin stands for a lot BINary data files. I know that ...dll stands for Dynamic Data Library. That APPlications are often called app ...
... and I have the feeling that a lot different things are mixed together here. Sure xonar knows what he is talking about but the rest sounds like not much clue and the rest filled up with things you heard somewhere.
Sent from my LG-P970 using xda app-developers app
SaschaKH said:
I don't know much about what your talking here. I know that the complete firmware from LG comes in a v....kdz package. I know that ...cab containers are Microsoft's preferred format (something like ...zip or ...rar). I know ...bin stands for a lot BINary data files. I know that ...dll stands for Dynamic Data Library. That APPlications are often called app ...
... and I have the feeling that a lot different things are mixed together here. Sure xonar knows what he is talking about but the rest sounds like not much clue and the rest filled up with things you heard somewhere.
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
Let me try to explain a litle for y.
You know that a kdz file contains a cab file. Every cab file contains a .dll file.
But not every cab file contains a wdb.
Sow what i need is a wdb file from a cab what doesnt have a wdb file. Or i need a extractor what makes from a .dz file and a .dll file a cp Bin and Ap bin. ( .dz file is the other file what could be in the cab without a .wdb,)
For some more information: When you use the SmartFlashTool. You need 2 files the CP Bin and AP bin.
You can use a extractor to get from a KDZ file a wdb and .dll file. ( From those its possible to create the CP Bin and AP bin)
But when you dont have de WDB file but you have a .DZ file then i cant create a CP bin and AP bin.
thats the problem. Sow now how can i fix that
Johrans said:
Let me try to explain a litle for y.
You know that a kdz file contains a cab file. Every cab file contains a .dll file.
But not every cab file contains a wdb.
Sow what i need is a wdb file from a cab what doesnt have a wdb file. Or i need a extractor what makes from a .dz file and a .dll file a cp Bin and Ap bin. ( .dz file is the other file what could be in the cab without a .wdb,)
For some more information: When you use the SmartFlashTool. You need 2 files the CP Bin and AP bin.
You can use a extractor to get from a KDZ file a wdb and .dll file. ( From those its possible to create the CP Bin and AP bin)
But when you dont have de WDB file but you have a .DZ file then i cant create a CP bin and AP bin.
thats the problem. Sow now how can i fix that
Click to expand...
Click to collapse
Have you tried
DZ-Creator / DZ-Decrypter
or
DZTools
If that fails then you have to reverse engineer your dz file yourself.
The DZ file can't be converted to bin/fls from the looks of it. That is if your dz file is similar to the dz file in the KS20.
That dz file is a collection of data blocks much like the bin file, but they aren't interchangable and I don't think SFT will work with them.
xonar_ said:
Have you tried
DZ-Creator / DZ-Decrypter
or
DZTools
If that fails then you have to reverse engineer your dz file yourself.
The DZ file can't be converted to bin/fls from the looks of it. That is if your dz file is similar to the dz file in the KS20.
That dz file is a collection of data blocks much like the bin file, but they aren't interchangable and I don't think SFT will work with them.
Click to expand...
Click to collapse
OKey sow if i understand this correctly is the .dz a kind of like the bin file. If i read correctly on this forum the wdb is also a collection off files like a zip file.
I think your are right it isnt possible to replace the .dz for a .wdb sow i can flash it in the SFT
Johrans said:
OKey sow if i understand this correctly is the .dz a kind of like the bin file. If i read correctly on this forum the wdb is also a collection off files like a zip file.
I think your are right it isnt possible to replace the .dz for a .wdb sow i can flash it in the SFT
Click to expand...
Click to collapse
Yes.
I don't think it's possible to flash dz file to your phone with SFT.
xonar_ said:
Yes.
I don't think it's possible to flash dz file to your phone with SFT.
Click to expand...
Click to collapse
Thanks for the answers, i know its possible with the kdz flasher but that tool isnt real stable and doesnt do a factory reset after the flash. it must be manual then.
Hello guys!
I'm a developing the AOXP ROM for our lovely Z3Cs. But I do not know how to deodex the stock rom.
Can I deodex the prerooted firmware zip created with PRFCreator??? It is based on the latest .291 firmware.
If any of you experienced developers can help me I would be grateful!
Thank you!
If you need any new information, I will add it to this post.
Deodexer for Pc running Windows Os.
You have to install lastest .Net Framework and Java too.
I dont know how to repack the system.ext4 partition into prerooted.zip, but i know how to deodex this partition.
6.0.1 rom .291:
Copy /framework, /app, /priv-app, build.prop, odex.framework.sqsh, odex.app.sqsh, odex.priv-apk.sqsh from /system to /*Work space* folder, use lastest 7zip to extract .sqsh files, then copy all .odex files to /apk/*apk name*/oat. make sure correct .apk and .odex name.
then running SVAdeodexer, choose /*Work space* folder and check /apk, /priv-apk, /framework to deodex.
all deodexed apps will be placed in /SVAdeodexer folder (the folder containing deodexer app)
*** app file (.apk) from /framework wont be deodexed, u should copy that app to /apk, after deodexed, copy that app back to /framework.
then delete /framework, /app, /priv-app, odex.framework.sqsh, odex.app.sqsh, odex.priv-app.sqsh, /odex.framework, /odex.app, /odex.priv-app from system.ext4 partiotion and copy /framework, /app, /priv-app deodexed back to system.ext4
xtbtvd12399 said:
Deodexer for Pc running Windows Os
You have to install lastest .Net Framework and Java too.
Click to expand...
Click to collapse
Thank you so much for replying... Will this work with sony roms? I mean, the structure of sony roms is different(system.sin etc) ???
panzerox123 said:
Thank you so much for replying... Will this work with sony roms? I mean, the structure of sony roms is different(system.sin etc) ???
Click to expand...
Click to collapse
you can use Flashtool converting sytem.sin into system.ext4
xtbtvd12399 said:
you can use Flashtool converting sytem.sin into system.ext4
Click to expand...
Click to collapse
But can I convert it back to system.sin after that?
panzerox123 said:
But can I convert it back to system.sin after that?
Click to expand...
Click to collapse
I never try it before. May not...
xtbtvd12399 said:
I never try it before. May not...
Click to expand...
Click to collapse
Hmmm... I'll try using Slimm Roms files, with permission ofcourse
panzerox123 said:
Hmmm... I'll try using Slimm Roms files, with permission ofcourse
Click to expand...
Click to collapse
Slimm Rom contain a system.ext4 file, isnt a .sin file
xtbtvd12399 said:
Slimm Rom contain a system.ext4 file, isnt a .sin file
Click to expand...
Click to collapse
Oh wait! I remember now...
Can I convert it back to a system.ext4 file after altering.. not system.sin.... :good:
panzerox123 said:
Oh wait! I remember now...
Can I convert it back to a system.ext4 file after altering.. not system.sin.... :good:
Click to expand...
Click to collapse
Try this. Required Cygwin (emulate Linux on Windows)
hello! I had a request for anyone running stock odexed firmware (.291)
Can you pull the system folder for that version and upload it for me? Thanks!
Edit: with odex files pls!
P.s. I need the untouched version without root. Thanks!
HERE are stock ftf firmwares. Choose one and download it.
Rename *.ftf to *.zip and extract a file system.sin using 7zip.
Open Flashtool, use function "Sin Editor" to convert system.sin -> system.ext4. Then use this to "save" /system folder.
There are some files *.sqsh that contain .odex files. this sqsh file link to odex file of the app. Use 7zip 16.04 to extract *.sqsh file, you will see odex files
---------- Post added at 04:22 PM ---------- Previous post was at 04:17 PM ----------
Eg: odex.app.sqsh contains all odex of /app folder.
Extract sqsh file and copy odex file to folder (ex: copy AnonymousData.odex to /app/AnonymousData/oat/arm/, then you have stock AnonymousData apk with odex file . )
xtbtvd12399 said:
HERE are stock ftf firmwares. Choose one and download it.
Rename *.ftf to *.zip and extract a file system.sin using 7zip.
Open Flashtool, use function "Sin Editor" to convert system.sin -> system.ext4. Then use this to "save" /system folder.
There are some files *.sqsh that contain .odex files. this sqsh file link to odex file of the app. Use 7zip 16.04 to extract *.sqsh file, you will see odex files
---------- Post added at 04:22 PM ---------- Previous post was at 04:17 PM ---------
Eg: odex.app.sqsh contains all odex of /app folder.
Extract sqsh file and copy odex file to folder (ex: copy AnonymousData.odex to /app/AnonymousData/oat/, then you have stock AnonymousData apk with odex file . )
Click to expand...
Click to collapse
Thank you so much! I am learning to deodex my ROM myself.
I will try it this weekend.
But aren't the odex files generated when you run android the first time?
This is wierd
EDIT: I downloaded the ftf from flash
tool and expanded it. I do not see any files *.sqsh files in any folders . Just empty
panzerox123 said:
Thank you so much! I am learning to deodex my ROM myself.
I will try it this weekend.
But aren't the odex files generated when you run android the first time?
This is wierd
Click to expand...
Click to collapse
I dont know this much. But odex files arent generated in system partition. They create odex file in system partition for faster first time bootup maybe.
---------- Post added at 06:14 AM ---------- Previous post was at 06:12 AM ----------
panzerox123 said:
EDIT: I downloaded the ftf from flash
tool and expanded it. I do not see any files *.sqsh files in any folders . Just empty
Click to expand...
Click to collapse
You need to extract system.sin and convert to system.ext4 first . the sqsh file must be in system partition.
xtbtvd12399 said:
I dont know this much. But odex files arent generated in system partition. They create odex file in system partition for faster first time bootup maybe.
---------- Post added at 06:14 AM ---------- Previous post was at 06:12 AM ----------
You need to extract system.sin and convert to system.ext4 first . the sqsh file must be in system partition.
Click to expand...
Click to collapse
I've done that. The folders are empty...
panzerox123 said:
I've done that. The folders are empty...
Click to expand...
Click to collapse
ohh. something wrong here. i ll check it tonight.
normally, the odex.app.sqsh, odex.framework.sqsh, odex.priv-app.sqsh must be in system partition.
xtbtvd12399 said:
ohh. something wrong here. i ll check it tonight.
normally, the odex.app.sqsh, odex.framework.sqsh, odex.priv-app.sqsh must be in system partition.
Click to expand...
Click to collapse
There are efolders in the system partions with those names. But they are empty
panzerox123 said:
There are efolders in the system partions with those names. But they are empty
Click to expand...
Click to collapse
Yes. Those folders are empty, but those are sqsh files near those folders . Check it
xtbtvd12399 said:
Yes. Those folders are empty, but those are sqsh files near those folders . Check it
Click to expand...
Click to collapse
Ill check. But is there a *.sqsh for every apk?
And if not, if I extract the .sqsh file, will it give me the odex for every apk?
Thanks
panzerox123 said:
Ill check. But is there a *.sqsh for every apk?
And if not, if I extract the .sqsh file, will it give me the odex for every apk?
Thanks
Click to expand...
Click to collapse
Yes, they contain all odex files
xtbtvd12399 said:
Yes, they contain all odex files
Click to expand...
Click to collapse
Ok thanks. I'll try once i get home
I checked it already.
Hope this can help you .
If you want to fully deodex your system, there are 2 more sqsh files. /system/etc/product/ and /system/etc/customizations/.
and there are 2 more odexed app with odex file: /system/vendor/app/ims/ & /system/vendor/app/ChromeCustomizations/
-----------------
There are symlinks between /system/$app/*app_name*/oat/arm/ and odex.$apk.sqsh/arm/*app_name*.odex
So the odex file show in folder is a shortcut from sqsh file. Sony made this
xtbtvd12399 said:
I checked it already.
Hope this can help you .
If you want to fully deodex your system, there are 2 more sqsh files. /system/etc/product/ and /system/etc/customizations/.
and there are 2 more odexed app with odex file: /system/vendor/app/ims/ & /system/vendor/app/ChromeCustomizations/
Click to expand...
Click to collapse
Thanks:good:
Found in firmware Finder.. It seems to be for P30 Pro.
http://update.dbankcdn.com/TDS/data/files/p3/s15/G4705/g1755/v304788/f1/full/update_full_base.zip
I want to extract it so I can get apks such as the launcher or camera app. I have managed to extract UPDATE.APP and I saw inside a file called SUPER. img which I suppose is equivalent to the usual system.img however I can't extract it. I tried different tools but I failed.
Does anyone know how to unpack that SUPER.img file?
orpheliaca said:
Found in firmware Finder.. It seems to be for P30 Pro.
http://update.dbankcdn.com/TDS/data/files/p3/s15/G4705/g1755/v304788/f1/full/update_full_base.zip
I want to extract it so I can get apks such as the launcher or camera app. I have managed to extract UPDATE.APP and I saw inside a file called SUPER. img which I suppose is equivalent to the usual system.img however I can't extract it. I tried different tools but I failed.
Does anyone know how to unpack that SUPER.img file?
Click to expand...
Click to collapse
Hi m8, even if you manage to unzip the SUPER.img file (you can try with 7zip, maybe it will work, don't bet on it) you can't install those apk's on EMUI 9.1, because they are different.
On EMUI 10 you can push those apk's (and camera libs folders) only if you're rooted and have bootloader unlocked.
Later edit: or you can rename it to system.img and try using this tool. Ignore, the tool is not available anymore
SilviuO said:
Hi m8, even if you manage to unzip the SUPER.img file (you can try with 7zip, maybe it will work, don't bet on it) you can't install those apk's on EMUI 9.1, because they are different.
On EMUI 10 you can push those apk's (and camera libs folders) only if you're rooted and have bootloader unlocked.
Later edit: or you can rename it to system.img and try using this tool. Ignore, the tool is not available anymore
Click to expand...
Click to collapse
I still have hopes as based on my experience not always the system app are only restricted to the new Android SDK. So maybe those two apks will be compatible with android P SDK or can easily be modes to make them compatible
However I didn't find a way to unpack SUPER.img despite trying different methods..
hi,
but full update it works?! did you tried?
thanks.
stefanz08 said:
hi,
but full update it works?! did you tried?
thanks.
Click to expand...
Click to collapse
I tried it just now and it did not work on my P30 Pro!
How did the full update work for you? Can you please tell how you managed to flash full update?
you can used my method:https://blog.cofface.com/archives/2954.html
cofface said:
you can used my method:https://blog.cofface.com/archives/2954.html
Click to expand...
Click to collapse
any repack method for super.img back with same hashed and header.if possible i can pay for it
---------- Post added at 05:04 PM ---------- Previous post was at 05:02 PM ----------
pakfixrom said:
any repack method for super.img back with same hashed and header.if possible i can pay for it
Click to expand...
Click to collapse
unpack already supported superR kitchen pro version
pakfixrom said:
any repack method for super.img back with same hashed and header.if possible i can pay for it
---------- Post added at 05:04 PM ---------- Previous post was at 05:02 PM ----------
unpack already supported superR kitchen pro version
Click to expand...
Click to collapse
superR kitchen pro version,Unpack is ok but can't repack. I am looking forward to the repack tool
I've extracted using: imjtool.
http://newandroidbook.com/tools/imjtool.html
Once you've extracted hw_product, cust, vendor, system, odm how do you extract those files?
someone managed to open and close Super.img ??