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
Related
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)?
Hey guys,
it seems that the original OLiFE.tar.gz file with system.img, recovery.img and boot.img is offline, and i need these files for flashing
it with frankstools.
Has anybody got a copy of the OLiFE.tar.gz or can explain to me how to get the system.img, recovery.img and boot.img out
of a nvflash android rom?
i want to flash http://forum.xda-developers.com/showthread.php?t=1852702 this ubuntu image
thanks in advance
Im uploading OLiFE prime atm but its gonna take a loooooooong time with my upload connection lol
I'm currently downloading: OLiFE-Prime-Edition.tar.gz
curti.nogg said:
I'm currently downloading: OLiFE-Prime-Edition.tar.gz
Click to expand...
Click to collapse
lol ive just been uploading it for like the last 6 hours.... oh well now we have a mirror
Thanks a lot! Yesterday I was desperate because the whole Internet relied on lilstevies server
If you already have an android rom installed use the olife -> backup -> stock option and then copy the files from the backup folder to the images folder
Ok any nvflashable image has this three components included, they are just named blob.APP, this is system.img, blob.LNX, this is boot.img, and blob.SOS, this is recovery.img.
Just rename them and you have your files.
Ananasnonym said:
Ok any nvflashable image has this three components included, they are just named blob.APP, this is system.img, blob.LNX, this is boot.img, and blob.SOS, this is recovery.img.
Just rename them and you have your files.
Click to expand...
Click to collapse
Cheers couldn't remember the files to re-name, ill chuck that up on the install guide
Any chance someone still has a valid link? I’ve dug up an old TF101 which could still be useful on Ubuntu…
Hi Guys
I need some basic help/understanding about Android ROM modification.
In particular for an Android MX TV Box - but the questions is generic and applies to any ROM I guess.
The Rom im flashing has the following files (and works perfectly):
factory_update_param.aml
hd18d_mx4.zip
recovery.img
I am able to successfully restore my box with this image (so I know that the image is working fine).
Within the hd18d_mx4.zip there is:
Directotories: data, META-INF, recovery, system
files: boot.img, bootloaded.img, logo.img
I tried to do a very basic step of deleting a single system.apk file from the system/app folder (no other changes) and I am unable to flash this firmware.
Any ides - what am i doing wrong?? It seems like i cant make any modifications to the zip file or there are problems.
I tried using dsixda Rom kitchen, and even if put rom in working directory, and then immediately
Please help - this is driving me mad!! Aaarrghghg
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!
Hi,
I am trying to port a rom, it had the file system.new.dat, I managed to extract the system folder from it, now I have made the changes I wanted, but I need to return the system folder to be system.new.dat
Or if there is any flash without having to go back to .new.dat
someone help me please!!