Hy guys if some one rooted their WT19i live with walkman phone
then please copy your system apps folder using root explorer and upload them
from original WT19i stock ROM
i really need them
You may get all files in a few steps:
1. Download firmware file (take it here).
2. Open it with 7-zip or WinRAR and extract somewere system.sin.
3. Download and unpack Direct SIN & YAFFS UnPacker in the same folder with system.sin.
4. Open console (cmd) from this folder and type:
aIUP.exe system.sin 4096 apps_LIVE
5. Your apps will appear in apps_LIVE folder.
Please delete my post
Can you use them with CM ?
.: SID :. said:
You may get all files in a few steps:
1. Download firmware file (take it here).
2. Open it with 7-zip or WinRAR and extract somewere system.sin.
3. Download and unpack Direct SIN & YAFFS UnPacker in the same folder with system.sin.
4. Open console (cmd) from this folder and type:
aIUP.exe system.sin 4096 apps_LIVE
5. Your apps will appear in apps_LIVE folder.
Click to expand...
Click to collapse
Please tell me if i want to extract other mobile phone sin files then what will be the command for them
i want to extract Xperia Arc sin files to .... ?????????????
and i am thankful to you for your info.......
The command will be the same.
Someone please tell me some basic of data.img system.img boot.img files
their use
and how to edit them ?
Or post some links explaining these.
ip2op01 said:
Someone please tell me some basic of data.img system.img boot.img files
their use
and how to edit them ?
Or post some links explaining these.
Click to expand...
Click to collapse
http://stackoverflow.com/questions/3879717/what-is-purpose-of-using-system-img-in-android
http://en.wikipedia.org/wiki/Disk_image
http://en.wikipedia.org/wiki/Boot_image
these may help, or may not. But hopefully so, if not try looking around stackoverflow a bit more.
ip2op01 said:
Someone please tell me some basic of data.img system.img boot.img files
their use
and how to edit them ?
Or post some links explaining these.
Click to expand...
Click to collapse
1.
boot.img : be similar with bootstrap in the PC's BIOS,aim to boot the android OS;
data.img : this file includes some user data and system data;
system.img : this file includes some packages and some lib file.
ramdisk.img : emulator's FS(file system)
2.
when the android OS start, emulator loads those image file to ramdisk FS, create "system" file directory and "data" file directory.so you should think that those are android OS component.
3.
(1)unpack:
a. tool-------"unyaffs" download link : http://code.google.com/p/unyaffs/downloads/list
b. command------./unyaffs system.img
(2)pack:
a. tool-------"mkyaffs2image" location:android/out/host/linux-x86/bin or search internet
b. make this tool
c. command------ ./mkyaffs2image <directory> <out_file>
I know this, try myself
Thanks guys
ip2op01 said:
Thanks guys
Click to expand...
Click to collapse
My English is poor,it's my pleasure,you can understand it.
enyblock said:
1.
boot.img : be similar with bootstrap in the PC's BIOS,aim to boot the android OS;
data.img : this file includes some user data and system data;
system.img : this file includes some packages and some lib file.
ramdisk.img : emulator's FS(file system)
2.
when the android OS start, emulator loads those image file to ramdisk FS, create "system" file directory and "data" file directory.so you should think that those are android OS component.
3.
(1)unpack:
a. tool-------"unyaffs" download link : http://code.google.com/p/unyaffs/downloads/list
b. command------./unyaffs system.img
(2)pack:
a. tool-------"mkyaffs2image" location:android/out/host/linux-x86/bin or search internet
b. make this tool
c. command------ ./mkyaffs2image <directory> <out_file>
I know this, try myself
Click to expand...
Click to collapse
So, if I have a ROM with the .img file extension I should flash it as "System" (In TWRP)???
Hi guys!
I have cooked my rom!
Deodexed - rooted and zipaligned!
I have tryed flash with recovery.. it's OK!
when the phone starts I get an error
"the application has stopped working "
what is the APK name of message?
How to solve this error?
I have Galaxy S3
Only thing I can suggest is grabbing a logcat and seeing what is crashing, you aren't giving a whole lot of info there.
how do I view the logcat?
After you have recorded it then just open it in a text editor.
Sent from my SCH-R760 using Tapatalk 2
how do i view logcat?
Click to expand...
Click to collapse
not sure if you ment how to open the logcat file
or how to actually get the logcat file.
heres how to get it.
use adb
best way to do it.
you need to have adb setup on your computer
connect device to computer
open terminal or cmd
Code:
adb
this will give you usage info about adb if not adb needs to be added to PATH
Code:
adb logcat -d > path/to/ desktop/logcat.txt
you can find market app that will save logcat to your sd card
if I remember correctly "alogcat"
This is my logcat
App "Message" crashed!
http://paste.ubuntu.com/1062350/
line 7777
Help please :'(
Did you remove CSC folder?
I never had a folder csc
Code:
[email protected]:~/Scrivania/ROM/WORKING_062512_024231/system$ ls
app cameradata framework media usr vsc
bin etc hdic preloaddata vendor wakeupdata
build.prop fonts lib tts voicebargeindata xbin
roxdragon said:
I never had a folder csc
Code:
[email protected]:~/Scrivania/ROM/WORKING_062512_024231/system$ ls
app cameradata framework media usr vsc
bin etc hdic preloaddata vendor wakeupdata
build.prop fonts lib tts voicebargeindata xbin
Click to expand...
Click to collapse
You didn't extract it , it's included on the "cache.img", we can work without it on sgs2 but it's a must on sgs3.
Code:
============================================================
Android Kitchen 0.196 - by dsixda (xda-developers.com)
============================================================
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add /data/app functionality
14 - Add Nano text editor + sysro/sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Tools for boot image (unpack/re-pack/etc.)
21 - Unpack data.img
22 - Sign APK or ZIP file(s)
23 - Convert update-script or updater-script
24 - Miscellaneous options / Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
Enter option: 0
============================================================
Android Kitchen 0.196 - by dsixda (xda-developers.com)
============================================================
1 - Set up working folder from ROM
2 - Add root permissions
3 - Add BusyBox
4 - Disable boot screen sounds
5 - Add wireless tethering
6 - Zipalign all *.apk files to optimize RAM usage
7 - Change wipe status of ROM
8 - Change name of ROM
9 - Check update-script for errors
10 - Show working folder information
0 - ADVANCED OPTIONS
99 - Build ROM from working folder
u - Update/About kitchen
x - Exit
Enter option:
How to extract cache.img?
with kitchen?
i have execute this:
Code:
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
? s
----------------------------------------------------------------------
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
Other formats:
Samsung Galaxy S:
- factoryfs.rfs + optional cache.rfs/zImage
- PDA.tar.md5 + optional CSC.tar.md5/PHONE.tar.md5
- PDA.tar + optional CSC.tar/PHONE.tar
- TAR/ZIP file containing factoryfs.rfs + more
- TAR/ZIP file containing PDA.tar.md5/PDA.tar + more
Samsung Galaxy S Plus:
- system.img.ext4 + optional cache.img.ext4/boot.img
- TAR/ZIP file containing system.img.ext4 + more
Samsung Galaxy SII:
- factoryfs.img + optional cache.img/zImage
- system.img.ext4 + optional cache.img.ext4/boot.img
- TAR/ZIP file containing factoryfs.img/system.img.ext4 + more
- system.ext4.tar + optional boot.img (Nandroid backup)
Huawei:
- APP file from Huawei software update (e.g. UPDATE.APP)
----------------------------------------------------------------------
Press Enter to continue, or type 'x' to abort:
Available ROMs:
(1) system.img and boot.img
Enter selection number (default=1, cancel=0):
Found original_update/system.img
Found original_update/boot.img
The new working folder will be named WORKING_062712_171010
Change the name (y/n)? (default: n):
Creating working folder WORKING_062712_171010 ...
Copying boot.img ...
Copying system.img ...
Adding an update-script ...
"system.img" -> "../system.img.ext4"
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
Analyzing system.img.ext4 ...
Compiling simg2img ...
simg2img successfully compiled
Converting system.img.ext4 into a format for unpacking ...
computed crc32 of 0xb9d9b0e7, expected 0x00000000
Mounting ext4_system.img to loopback device and then extracting files ...
..............
..........
...
N.B
Code:
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
into my original_update have:
Code:
[email protected]:~/Scrivania/ROM/original_update$ ls
boot.img cache.img hidden.img modem.bin recovery.img system.img
Can you help me please? Thank u
roxdragon said:
Code:
============================================================
Android Kitchen 0.196 - by dsixda (xda-developers.com)
============================================================
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add /data/app functionality
14 - Add Nano text editor + sysro/sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Tools for boot image (unpack/re-pack/etc.)
21 - Unpack data.img
22 - Sign APK or ZIP file(s)
23 - Convert update-script or updater-script
24 - Miscellaneous options / Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
Enter option: 0
============================================================
Android Kitchen 0.196 - by dsixda (xda-developers.com)
============================================================
1 - Set up working folder from ROM
2 - Add root permissions
3 - Add BusyBox
4 - Disable boot screen sounds
5 - Add wireless tethering
6 - Zipalign all *.apk files to optimize RAM usage
7 - Change wipe status of ROM
8 - Change name of ROM
9 - Check update-script for errors
10 - Show working folder information
0 - ADVANCED OPTIONS
99 - Build ROM from working folder
u - Update/About kitchen
x - Exit
Enter option:
How to extract cache.img?
with kitchen?
i have execute this:
Code:
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
? s
----------------------------------------------------------------------
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
Other formats:
Samsung Galaxy S:
- factoryfs.rfs + optional cache.rfs/zImage
- PDA.tar.md5 + optional CSC.tar.md5/PHONE.tar.md5
- PDA.tar + optional CSC.tar/PHONE.tar
- TAR/ZIP file containing factoryfs.rfs + more
- TAR/ZIP file containing PDA.tar.md5/PDA.tar + more
Samsung Galaxy S Plus:
- system.img.ext4 + optional cache.img.ext4/boot.img
- TAR/ZIP file containing system.img.ext4 + more
Samsung Galaxy SII:
- factoryfs.img + optional cache.img/zImage
- system.img.ext4 + optional cache.img.ext4/boot.img
- TAR/ZIP file containing factoryfs.img/system.img.ext4 + more
- system.ext4.tar + optional boot.img (Nandroid backup)
Huawei:
- APP file from Huawei software update (e.g. UPDATE.APP)
----------------------------------------------------------------------
Press Enter to continue, or type 'x' to abort:
Available ROMs:
(1) system.img and boot.img
Enter selection number (default=1, cancel=0):
Found original_update/system.img
Found original_update/boot.img
The new working folder will be named WORKING_062712_171010
Change the name (y/n)? (default: n):
Creating working folder WORKING_062712_171010 ...
Copying boot.img ...
Copying system.img ...
Adding an update-script ...
"system.img" -> "../system.img.ext4"
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
Analyzing system.img.ext4 ...
Compiling simg2img ...
simg2img successfully compiled
Converting system.img.ext4 into a format for unpacking ...
computed crc32 of 0xb9d9b0e7, expected 0x00000000
Mounting ext4_system.img to loopback device and then extracting files ...
..............
..........
...
N.B
Code:
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
into my original_update have:
Code:
[email protected]:~/Scrivania/ROM/original_update$ ls
boot.img cache.img hidden.img modem.bin recovery.img system.img
Can you help me please? Thank u
Click to expand...
Click to collapse
Use "24" option on Advanced options then "Extract_SGS2_CSC_from_cache.img", i think cache.img must be the root working folder, it will convert it to ext, then follow the displayed steps.
wanam said:
Use "24" option on Advanced options then "Extract_SGS2_CSC_from_cache.img", i think cache.img must be the root working folder, it will convert it to ext, then follow the displayed steps.
Click to expand...
Click to collapse
Code:
PLUGIN SCRIPTS
--------------------------------------
(1) Extract_SGS_CSC_from_cache.rfs
(2) Decompile_and_Compile_Deodexed_File
(3) Install_SGS2_CWM_Manager
(4) Batch_Deodex
(5) Sample
(6) Extract_SGS2_Kernel_Initramfs
(7) ReadMe
(8) Extract_SGS2_CSC_from_cache.img
--------------------------------------
0 - Exit r - Refresh list
Enter an option: 8
Samsung Galaxy S2 CSC Extractor
-------------------------------
This script will extract the CSC (Customer Software Customization)
from the cache.img of a stock Samsung Galaxy S2 firmware. The CSC
comes in a file called 'sec_csc.zip' which contains location and
carrier-specific configurations and software.
Proceed (y/n)? (default: y):
Creating folder /home/gianni/Scrivania/ROM/csc_062712_205036 ...
---> Place stock cache.img or cache.img.ext4 into the folder mentioned above <--
Press Enter to continue
Compiling simg2img ...
simg2img successfully compiled
Unpacking cache.img into a format for unpacking ...
computed crc32 of 0x20453d0a, expected 0x00000000
Mounting ext4_cache.img to loopback device and then extracting files ...
[sudo] password for gianni:
Finished! Your file is at csc_062712_205036/sec_csc.zip.
You can unzip this file and copy the contents of the 'system'
folder to your ROM's system folder.
I have a package "sec_csc.zip"
I have extracted sec_csc.zip and i have into *.zip
META-INF
system
i need copy all files into system to /WORKING_FOLDER/system? and META-INF?
now??
Solved thank u
Another quesyion..
How to remove default app during installation of custom rom?
MyTaxy.apk, videohub, rhs hotel .... etc...?
Sent from my GT-I9300 using xda app-developers app
This script removes unnecessary files and adds the file
Script deletes files...
Code:
system/app/Apollo.apk");
system/app/Browser.apk");
system/app/Calculator.apk");
system/app/Calendar.apk");
system/app/CMWallpapers.apk");
system/app/Email.apk");
system/app/LatinIME.apk");
system/app/Term.apk");
system/app/VideoEditor.apk");
system/app/CMFileManager.apk");
system/app/Exchange2.apk");
system/app/Galaxy4.apk");
system/app/Gallery2.apk");
system/app/NoiseField.apk");
system/app/LiveWallpapersPicker.apk");
system/app/MagicSmokeWallpapers.apk");
system/app/PhaseBeam.apk");
system/app/VoicePlus.apk");
delete_recursive ("/system/media/audio/notifications");
delete_recursive ("/system/media/audio/ringtones");
system/media/audio/notifications
system/media/audio/ringtones
Leaves only one ringtone and notification
Sets the modified host file patched program AdFree
With this script you can free up about 100 mb
Installation: Flash file via recovery
Download v1.0 :http://d-h.st/6ew
Download v1.1 : http://d-h.st/IQR
For version 22.05.14 CM 11 use version v1.0 which does not remove the standard live wallpaper, without them off point wallpaper
Hoping someone can help me. Using the stock OS for a motorola moto G(3rd gen) and the windows command prompt, I can flash install system.img_sparsechunk.# files succesfully and the phone works great. However, I want to slim down this OS and remove some of the bloatware.
So, I unpacked system.img_sparsechunk.#'s into a system.img file using 'sparse converter.exe'. Then further decompressed it into folders and files using 'img extractor.exe'. Removed a few unimportant apps from the app folder and then made it back into a system.img file using 'make_ext4fs.exe & cygwin1.dll' which I got from the MTK Thai Developers Tool Unpack Repack package. Finally, I convert system.img into system.img_sparsechunk# files with 'sparse converter.exe' and I flashed to the moto G. This is unsuccessful. The phone is never gets past the bootloader unlocked screen and eventually goes to recovery. Is there something I'm doing wrong along the way in my unpack and repack?
These are the files from the stock OS:
boot.img
bootloader.img
flashfile.xml
fsg.mbn
gpt.bin
logo.bin
NON-HLOS.bin
OSPREY_RETUS_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.info.txt
recovery.img
servicefile.xml
slcf_rev_b_default_v1.0.nvm
system.img
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
system.img_sparsechunk.5
system.img_sparsechunk.6
Here are my steps more detailed:
1. sparseConverter_1.0.1 /decompress system.img_sparsechunk.0 system.img
A. This creates system.img
2. imgExtractor.exe system.img systemUnpack
A. This unpacks to files and folders
3. Modify files within 'systemUnpack' folder
4. make_ext4fs.exe -l 1200M system.img g:\rootAndroidMotoG3\osModXT1540\systemUnpack
A. Determine the size of the 'systemUnpack' folder. Round up to the nearest 100 Mb and substitute this
number for 1200.
B. This makes system.img
5. sparseConverter_1.0.1 /compress system.img . 256MB
A. This makes system.img_sparsechunk files
6. Enter bootloader mode on the MotoG.
7. Type: 'c:\adb\fastboot flash system system.img_sparsechunk1'. Type this for all of the system.img_sparsechunk#'s
Thanks
ACFH said:
I think you need put "-a system" in make_ext4fs command. Read this:
https://forum.xda-developers.com/ge...packing-editing-packing-roms-img-dat-t3350261
Click to expand...
Click to collapse
Thanks, it worked.