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!!
Related
I want to modify the Saihon X6 ROM, but the system.img is different from I've ever met, they put the system.img into 8 img, now do not know how to load, don't know how to modify it, I need help, need a detailed tutorial. Thank you
ht tp://pan.baidu.com/s/1pJAvLer
if u wanna extract system.img then use dsixda kitchen.
put the img file in update original update folder then go to cygwin and choose make a working folder from rom.
it will identify your img file and then give an opt to extract it.
I noticed that oreo was released on the Mate 9, I needed to grab some files from this device, particularly a file named "gps.default.so" or something around that located somewhere in system/lib64 or system/lib but a system dump would definitly be nicer.
Or, you can help me out in extracting the oreo firmware, I've downloaded it and extracted UPDATE.APP and used HuaweiUpdaterExtracter to then grab the system.img. But I can't mount it or extract anything from it. soo yeahhh
Extraction
Yuvch122 said:
I noticed that oreo was released on the Mate 9, I needed to grab some files from this device, particularly a file named "gps.default.so" or something around that located somewhere in system/lib64 or system/lib but a system dump would definitly be nicer.
Or, you can help me out in extracting the oreo firmware, I've downloaded it and extracted UPDATE.APP and used HuaweiUpdaterExtracter to then grab the system.img. But I can't mount it or extract anything from it. soo yeahhh
Click to expand...
Click to collapse
You can use superr's Android kitchen to extract everything from the system.img, he has a free version https://forum.xda-developers.com/apps/superr-kitchen
And for your information, that "update extractor" doesn't give you usable images as it strips the necessary header from the image. I had to use "splitupdate.pl" to get usable images. I have the extracted images, and there is no file called "gps.default.so" anywhere in the Oreo images, not in /system/lib, /system/lib64 or in /vendor/lib, /vendor/lib64. I do not have a dump of the nouget to check but the file does not exist in the Oreo images
EDIT:
Found the file, it is in the vendor partition, specifically /vendor/lib64/hw so you're going to have to extract vendor.img to get the file.
Hello guys,
i want to extract CSC from a rom and want to make it flashable but I don't know how to do it.
Can anyone suggest me how can i do that?
which tools are used?
any guides or tutorial will be much helpfull.
Doing all this to make volte work in my s6.
Thanks.
Hello,
if you have any flashable zip that is for kernel for example or for fonts that is runnable on your s6
& the flashable zip is not for custom rom & non AROMA ......
extract it
then put your folders on it ..... then zip it again.....
for example
you want to add "BTU" CSC
After extract that zip you have it before ...... remove the folders except META-INF
& put system folder.... inside system folder put csc folder..... inside csc folder put BTU folder ....
& put all containing folder inside BTU folder....
finally zip it
main zip will contain META-INF folder & system folder that you put it & put everything inside it.
Regards,
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
Hello I have two HTCu11's one is completely untouched the other has been customized. On the untouched I have loaded TWRP and the disable encrypt with magisk. I did a factory reset on the untouched to where it was literally sitting at the Welcome screen. I then took a backup which obviously I should be able to use on any U11 with the right signature. I want to now create a flashable zip so I moved the files to my pc. The guide I was reading says:
You’ll see a file named system.ext4.win which is the System partition backup of your device. Rename it to system.ext4.tar (Changing its extension from .win to .tar)
However in my backup there are three files named:
system.ext4.win000
system.ext4.win001
system.ext4.win002
Logic would just say that this is a split archive and I need to rename all of them to .tar and then do the unzip. Is this correct?
If there is a better guide for creating a flashable zip from TWRP I would gladly look at it. The guide I was using is:
Create Flashable Zip From CWM/TWRP Backup
Create Flashable Zip from a Nandroid backup and flash them using any of the recovery. Follow this step-by-step guide to make a flashable Zip by yourself.
www.droidviews.com
Thanks
So I got an answer on renaming files which was to just rename them to win000.tar, win001.tar, and win002.tar. Next opened the archive with 7-Zip and extracted to a completely different folder called NewHTCU11. A lot of the stuff extracted however there were supposedly according to 7-zip 15 errors. All were the same where it stated:
Can not open output file. The system cannot find the path specified. S:\(specified directory\specified filename