I was wondering if there is a way to change the new style of the file types that clockwork makes. I know its good to keep the filesystem (ie ext4) but if there is ever a problem that i know is not due to a corrupt system (like when you change the name of the file folder or etc) you cant seem to just flash the files manually with fastboot. so really im wondering can we convert these back to an .img that we can manually flash or is there nothing we can do? Is there another nandroid app that will make the relevant files in .img form (data.img, system.img, userdata.img and boot.img)?
Related
Ok so I decided that I wanted to see what all the Froyo fuss was about, so I started getting my phone ready following instructions on the site. I own a Samsung i-9000m (in canada from bell - actually sasktel but we get phones from bell). anyways, I figured i'd do a rom manager backup. I did one, had some trouble with my phone and now I need to do a restore. Reading on the web they all point to an update.zip file. All I have is the following on my internal SD
ClockworkMod\2010-11-24-14.32.54\ and the following files in that folder:
cache.img
datadata.img
system.img
data.img
nandroid.md5
I tried restoring from rom manager but it doesn't find any files, I've booted into recovery but doesn't recognize the img files......any help would be amazing. Am I missing a step, google is no help
loooks like i needed the recovery update.zip file i'm assuming.....for some reason I didn't have it in the clockworkmod folder....
When I downloaded the shipped-roms, there are lots of .img files
I want to open them, but I dont know how to open, can anyone tell me?
How to open and edit the .img files.
On Linux you can mount the file if your kernel supports the yaffs filesystem, the other (easy) way is with a tool called unyaffs.
Hello! Before posting, i search this forum but not found nothing understandable. I wont to modify .ftf file of sony xperia e single sim, edit some apps and repack in fleshable ftf again, but i have some problems. Ok i'm doo next:
1. Extract flashtool via winrar.
2. Copy system.sin to flashtool directory and extract with sin editor, and get 2 files system.ext4 and system.partinfo, but with flashtool only possible to extract yaffs2 files. 3. Here is big problem, i tryed menny softwares for opening ext4 images in windows, but only ext2 exploer can modify this files, but totaly inaccesible with screen readers like as jaws.
4. I found some tutoryals for mounting in linux but i can not understand linux commands as well, for example did i must know exactly syze of system partition to mount ext4 image, maby exist some gui program for linux from wich can mount end edit ext4 images?
Finally, does possible making flashable img or ftf file for sonny phones for custom roms? For example, easyer to me is flashing custom roms via fastboot, because in some situations for cm recovery i need sited assistance.
Thanks, and best regards.
iksi said:
Hello! Before posting, i search this forum but not found nothing understandable. I wont to modify .ftf file of sony xperia e single sim, edit some apps and repack in fleshable ftf again, but i have some problems. Ok i'm doo next:
1. Extract flashtool via winrar.
2. Copy system.sin to flashtool directory and extract with sin editor, and get 2 files system.ext4 and system.partinfo, but with flashtool only possible to extract yaffs2 files. 3. Here is big problem, i tryed menny softwares for opening ext4 images in windows, but only ext2 exploer can modify this files, but totaly inaccesible with screen readers like as jaws.
4. I found some tutoryals for mounting in linux but i can not understand linux commands as well, for example did i must know exactly syze of system partition to mount ext4 image, maby exist some gui program for linux from wich can mount end edit ext4 images?
Finally, does possible making flashable img or ftf file for sonny phones for custom roms? For example, easyer to me is flashing custom roms via fastboot, because in some situations for cm recovery i need sited assistance.
Thanks, and best regards.
Click to expand...
Click to collapse
I have looked around to repack an extacted system.sin but never found how to do it. To dump the ext4 img just use ext2 explorer after it has finished extracting & loading click save in the toolbar and choose the folder where you want to save it.
gavster26 said:
I have looked around to repack an extacted system.sin but never found how to do it. To dump the ext4 img just use ext2 explorer after it has finished extracting & loading click save in the toolbar and choose the folder where you want to save it.
Click to expand...
Click to collapse
hello! I can't found ext2 explorer, i only found ext2explore, but this software is totaly unusable for me, don't works with screen readers.
P. s. whats your problem when you try making system.sin?
iksi said:
hello! I can't found ext2 explorer, i only found ext2explore, but this software is totaly unusable for me, don't works with screen readers.
P. s. whats your problem when you try making system.sin?
Click to expand...
Click to collapse
There's no tutorial on how to build one or a tool. Not for windows anyway.
Welcome. Today I am going to teach you how to modify your android boot logo!
Modify at your own risk! I strongly recommend that you do not try this. But if your going to attempt this, make a BACKUP! I will explain the backup process down the page!
This method has been tested on the Galaxy S6. I RECOMMEND you do NOT attempt this method on any other smartphone other than the S6!
I own a Samsung Galaxy S6 [SDK21 ARM64] and my carrier is Straighttalk. This method might possibly work with the newer Android smartphones. In other words, attempting to do my method will probably not work with androids running 4.4.2 or lower. I will first explain why.
According to what I researched, there is a file in the root directory of the Android system that contains a file called "initlogo.rle". That is your boot logo. Older Android phones had this. The .rle is a bitmap extension and cannot be edited with Android. Actually, let me rephrase that, the .rle COULD MAYBE possibly be edited if you were to download the right tools off of the Play Store but computers can identify .rle as a bitmap very easily and can be opened. Windows computers can open .rle according to what I researched.
The initlogo.rle is also part of the boot.img. The boot.img contains the kernel and the boot files (like init.rc), that are necessary for the phone to boot up. Modifying your boot.img requires a computer. You can't just replace the initlogo.rle with another one. To make changes to a boot.img, you need to unpack the ramdisk, replace or modify the files, repack, and THEN flash the modified boot.img to make the changes.
Newer Android smartphones don't have initlogo.rle. Or at least MINE doesn't. Instead, I had to search for my boot logo which took my quite a while. After searching deep into the android system and messing around with the files, I came accross PARAM.
If you were to go in the /dev/block/platform directory, you would come accross a file called PARAM. Mine was in the directory /dev/block/platform/15577000.ufs/by-name. Inside that directory is basically the whole system. You will find files like BOOT, EFS, OTA and all that. You will also notice that all those files look empty. They all show 0.00B. I don't know exactly why that is, but they aren't really empty files.
My official boot logo was in the file "PARAM". What I did was copied it to my internal directory and attempted to extract it. After trying different extensions, I founded out that .tar is the correct extension. So to extract it, I renamed "PARAM", to "PARAM.tar". After doing that, you will be able to actually extracted it and be left with files with .jpg. Basically pictures inside it. I used root browser. :good:
Inside, you should find "logo.jpg". And whatta ya know! It's your boot logo!
I used PicArt to create a custom boot logo. It is a really great app! You can get it off the Play Store. Then I renamed it to logo.jpg and replaced the original logo.jpg with my newer one. Make sure it is named "logo.jpg" or there will be errors!
Now the last step is to archive the files through .tar format. I used root browser to do that. To correctly archive the files, multi-select the .jpg files. In other words, DON'T SELECT THE "PARAM" FOLDER!!!
When archiving the files, use LZMA compression option along with tar.(Look for that with root browser). This will not compress the files as much which will reduce the risk of errors.
Once it's archived, rename the new archive file to just "PARAM".
LAST STEP! Before overwriting your PARAM, copy your modified PARAM into the /system folder and set the correct attributes (PERMISSIONS) to -rwxrwxrwx. Now you are ready. Copy "PARAM" to the same director where you originally got your unmodified PARAM file. It will ask you if you want to overwrite. Say yes.
I was now introduced with a different boot logo. My phone never got bricked during the process. However, with Android, ANYTHING can happen, so I will give you some advice. If you have a custom recovery, you can easily restore PARAM. Make a copy of your original PARAM and put it in your internal directory. If something ever goes wrong, you can use the file manager (like with TeamWin) and replace the currupt PARAM with your backup PARAM. Then set the permissions to -rwxrwxrwx or 0777
I strongly recommend that you do not try this. Yes, I took the risk and was able to safely change my boot logo. However, not all Android devices are the same so be very careful if you are attempting to do this one an Android device OTHER than the Galaxy S6.
Leave comments if you have any questions!
Hello, I´m a newbie on this matters.
I´m trying to cook a custom rom from a stock rom for this android pc with RK3328 chip. The rom I´ve downloaded is an 8.1 android image version, an the app I used is RK3xxx_firmware_tools_5.78.35.00 that I´ve downloaded from the chinagadgetsreviews.
When I uncompressed the rom.img, system.img and boot.img with this app, I got three folders called: "Android", (with a "Image" subfolder with the boot.img, kernel.img, recovery.img... and a package-file file), "boot", (with a boot.img.unkrnl.dump folder who contains many folders and .rc files, boot.img.unkrnl.cfg file and boot.img.cfg file), and "system", (with the app, etc, bin... folders and the build.prop, compatibility_matrix.xml, manifest.xml and vendor files). Also got a system_statfile with these 3 folders.
I´d like to remove some apps from this rom and include others, and if it is possible, changing the recovery.img from it. The recovery partition has 64MB of size, and the original recovery.img has only 9057 KB. The recovery.img I´d like to install is the twrp_RK3328_v3110 adapted for this chip (who has only 5258 KB), but I wonder if I could simply replace the original recovery.img with this twrp one on the "Image" subfolder I said (renaming it first to recovery.img) and after repack the rom, or, like I'm afraid, more things have to be done.
Thanks a lot in advance.
Anybody doesn't know how?
porkero said:
Hello, I´m a newbie on this matters.
I´m trying to cook a custom rom from a stock rom for this android pc with RK3328 chip. The rom I´ve downloaded is an 8.1 android image version, an the app I used is RK3xxx_firmware_tools_5.78.35.00 that I´ve downloaded from the chinagadgetsreviews.
When I uncompressed the rom.img, system.img and boot.img with this app, I got three folders called: "Android", (with a "Image" subfolder with the boot.img, kernel.img, recovery.img... and a package-file file), "boot", (with a boot.img.unkrnl.dump folder who contains many folders and .rc files, boot.img.unkrnl.cfg file and boot.img.cfg file), and "system", (with the app, etc, bin... folders and the build.prop, compatibility_matrix.xml, manifest.xml and vendor files). Also got a system_statfile with these 3 folders.
I´d like to remove some apps from this rom and include others, and if it is possible, changing the recovery.img from it. The recovery partition has 64MB of size, and the original recovery.img has only 9057 KB. The recovery.img I´d like to install is the twrp_RK3328_v3110 adapted for this chip (who has only 5258 KB), but I wonder if I could simply replace the original recovery.img with this twrp one on the "Image" subfolder I said (renaming it first to recovery.img) and after repack the rom, or, like I'm afraid, more things have to be done.
Thanks a lot in advance.
Click to expand...
Click to collapse
All I can say is, extract the ROM until you get to the system folder then look for /system/app and /system/priv-app folders, delete the apps you don't want and add the ones you want. Then, remove your recovery.img and place your TWRP.img in its place then repack everything into the file format that you need then try flashing it.
If that doesn't work, you'll have to start doing your own research to get your ROM put together correctly.
Sent from my SM-S767VL using Tapatalk