Related
As I was following the guide to improve the galaxy's quadrant score, I messed on one of the lines and overwrote the playlogos1 file that was meant to be renamed to playlogosnow.
I'm currently running JM5; do I need a file from the same version or can I take it from something like froyo which I found?
Or will this require me to reflash, and is it safe to do so without the file?
you need this file only to play the startup animation. if you don't care for the animation you can just delete it or replace it with a script (as you did, i suspect?!).
anyway, you can take this file from any firmware to replace your's...
Ah damn. Just to be on the safe side as I had no idea of the file's importance, I've just finished reflashing the firmware to restore it.
Thanks anyway.
SYUNIXT said:
Ah damn. Just to be on the safe side as I had no idea of the file's importance, I've just finished reflashing the firmware to restore it.
Thanks anyway.
Click to expand...
Click to collapse
you'r welcome ... if you want to do the fix again:
the playlogos1 file ist just the binary that play's the animation. it will be started with root-permissions, so you can replace it to run custom commands as root. in our case we want it to
*) make the loop device and set it up
*) mount the ext2.data file
to make the fix permanent.
mine looks like (you have to make the ext2.data file, format it, copy the data and relink before!!!!):
busybox mknod /dev/loop0 b 7 0
busybox losetup /dev/loop0 /data/ext2.data
busybox mount -t ext2 -o noatime,nodiratime /dev/loop0 /data/ext2.data_mp
and if you want your sgs to play the startup animation. you have to rename playlogos1 to something else and start it from the script...got it?
but again, if the file is not there (eg. you deleted it) nothing bad will happen, you will just not see the animation. the sound will still play and everything else will be fine
Can anyone provide me with the playlogos1 file, or somewhere that I can get it? I updated my rom and it somehow was erased.
ayinyesh said:
Can anyone provide me with the playlogos1 file, or somewhere that I can get it? I updated my rom and it somehow was erased.
Click to expand...
Click to collapse
Try OCLF from the market - it used to have a restore playlogo script.
http://www.youtube.com/comment?lc=8KNWgMta4EvqAcKfdwk-z2flON7mZ3RxQDynukPTSjk
Fix boot screen after one click lag fix:
1: Download playlogosnow megaupload. com/?d=M1N9RFMM
2: place the file on your internal sd.
3: replace (copy past) the file using a root manager in /system/bin
4: reboot
Should have posted this in Q&A....
jodue said:
you need this file only to play the startup animation. if you don't care for the animation you can just delete it or replace it with a script (as you did, i suspect?!).
anyway, you can take this file from any firmware to replace your's...
Click to expand...
Click to collapse
You better not advice people to brick their phones. Missing playlogo1 causes your sgs wont boot because it freezes trying to load playlogos1. Thanks for the advice, now i have bricked phone.
I have created a autobackup script for the EFS partition that contains information for your IMEI number.
I am addressing all ROM Developers to include this script in their ROM's!
What does this script do? It creates efs_autobackup folder on your SDCard and then tars the whole EFS partition into efs-backup.tar.gz file. Once this file is created, you can safely copy it to your PC. The script also looks for that file on reboot and if the file exists, it won't create another one.
What are the benefits of the tar file?
It keeps the permissions information for your EFS partition, so that when you want to restore your EFS partition, you only need to extract that file with the RootExplorer to your EFS partition and overwrite the old files. It sets the permissions automatically for you, so you don't need to mess or handle that yourself.
Please Developers, include this in your ROM so that users that forget to backup their EFS partition, don't have to regret that.
INSTRUCTIONS:
For Users:
If you are on ROM that don't have this script integrated - you can flash the attached zip file in your Recovery to integrate the script.
For Developers:
Either take the file from the attached zip or create 01efstar file (very important to name it with 01 prefix, since it runs as first when the Phone starts, otherwise it won't work) in the /system/etc/init.d folder with this content:
Code:
#!/system/bin/sh
# EFS Autobackup script for Samsung Nexus S
# By Brainmaster
mount /dev/block/platform/s3c-sdhci.0/by-name/media /sdcard
if [ ! -f /sdcard/efs_autobackup/efs-backup.tar.gz ];
then
mkdir /mnt/sdcard/efs_autobackup
busybox tar zcvf /sdcard/efs_autobackup/efs-backup.tar.gz /efs
fi
umount /sdcard
Reserved 1.
What a good idea.
Should I implement this on the radio zip file too?
window7 said:
Should I implement this on the radio zip file too?
Click to expand...
Click to collapse
No, this is ROM based. If the ROM don't support the scripts, then it won't work.
BUT, I am working on a version that can do this directly in the recovery (undependable from ROM) - then you can integrate it in every Radio flash file.
Well done,good job !
Sent from my Nexus S using XDA App
brainmaster said:
No, this is ROM based. If the ROM don't support the scripts, then it won't work.
BUT, I am working on a version that can do this directly in the recovery (undependable from ROM) - then you can integrate it in every Radio flash file.
Click to expand...
Click to collapse
you only have to modify the updater-swcript? easy as a pie!
Sent from my Nexus S using XDA Premium App
i hope ur miui rom has this or else should i flash it?
Borky_16 said:
you only have to modify the updater-swcript? easy as a pie!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Not so easy to mount the efs partition through the updater-script.
ancilary said:
i hope ur miui rom has this or else should i flash it?
Click to expand...
Click to collapse
From the next release on. If you want you can flash the script now.
yeah i dunno, first i made my own script and put into etc/init.d (running netarchy 1.3.9 which obv supports init.d scripts) - no dice. so i removed that file and flashed the zip and still getting no backup on sd.
ideas?
brainmaster said:
Not so easy to mount the efs partition through the updater-script.
Click to expand...
Click to collapse
oh that is right! :O forgot about it
Script successfully injected into my current installation of CM nightly, and successfully executed on reboot.
Uploaded the resulting file to Dropbox -- where I know I'll never lose it!
Two thumbs up!
I will include this script in my next rom update. I believe every dev should do the same.
Sent from my Google Nexus S using XDA Premium App
Good idea to put this into every ROM. Some people probably are not aware of the danger and if anything happens at least they can find the backup files on their sdcard. Maybe one should also add a small text file as an explanation what this backup is good for, so they do not accidentally delete it. Maybe you could also change the backup file on the sdcard to read-only.
Btw, you can also make a simple backup image with 'dd if=/dev/block/mtdblock6 of=efs.img'.
And for the record: I wondered why the /efs partition is mounted read-write and thought it might be a good idea change this to read-only. Problem was, without write access to /efs the SIM card would not unlock anymore. So not a good idea.
Just got my phone back from Regenersis with the IMEI restored! Shows that it can be done!
Ezekeel said:
Good idea to put this into every ROM. Some people probably are not aware of the danger and if anything happens at least they can find the backup files on their sdcard. Maybe one should also add a small text file as an explanation what this backup is good for, so they do not accidentally delete it. Maybe you could also change the backup file on the sdcard to read-only.
Btw, you can also make a simple backup image with 'dd if=/dev/block/mtdblock6 of=efs.img'.
And for the record: I wondered why the /efs partition is mounted read-write and thought it might be a good idea change this to read-only. Problem was, without write access to /efs the SIM card would not unlock anymore. So not a good idea.
Click to expand...
Click to collapse
Actually it should be as follows seeing as we get a read-only error;
dd if=/dev/block/mtdblock6 of=/mnt/sdcard/efs.img
Sent from my Nexus S using XDA Premium App
atrixboy said:
Actually it should be as follows seeing as we get a read-only error;
dd if=/Dec/block/mtdblock6 of=/months/sdcard/efs.img
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Please, IF you want to use the option to make efs.img (I don't know why would you like to do that, because tar is easier to extract and keeps the permissions), THEN you need right command.
You misspelled allot.
Code:
dd if=/dev/block/mtdblock6 of=/sdcard/efs.img
Yea I realised that after I hit post. I agree rfs is much nicer and cleaner to deal with.
dd if=/dev/block/mtdblock6 of=/mnt/sdcard/efs.img
Or efs.rfs. however you prefer. Rfs being the more logical
Sent from my Nexus S using XDA Premium App
brainmaster said:
Please, IF you want to use the option to make efs.img (I don't know why would you like to do that ...)
Click to expand...
Click to collapse
Because mtd6 contains more than the visible files mounted on /efs, such as the wimax keys.
My question is how to restore the partition without having to worry about this:
Dees_Troy said:
Using dd on mtd devices is a bad idea when it comes time to restore. It's a quick path to a brick. It tends to inadvertently mark blocks as bad.
Click to expand...
Click to collapse
Maximilian Mary said:
Because mtd6 contains more than the visible files mounted on /efs, such as the wimax keys.
My question is how to restore the partition without having to worry about this:
Click to expand...
Click to collapse
Darn. I did not know that.
Turns out one should use nanddump and nandwrite from mtd-utils (http://git.infradead.org/mtd-utils.git). Maybe someone can compile a version for Android. That would be quite useful.
Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
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)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.
Rycon33 said:
Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
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)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.
Click to expand...
Click to collapse
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones
gregbradley said:
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones
Click to expand...
Click to collapse
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
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
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?
Rycon33 said:
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
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
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?
Click to expand...
Click to collapse
wait, let me boot into linux and I will check
gregbradley said:
wait, let me boot into linux and I will check
Click to expand...
Click to collapse
mate, btw I'm only using cygwin in win7 if that matters on my issue
Rycon33 said:
mate, btw I'm only using cygwin in win7 if that matters on my issue
Click to expand...
Click to collapse
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,
gregbradley said:
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,
Click to expand...
Click to collapse
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?
gregbradley said:
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?
Click to expand...
Click to collapse
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework
Rycon33 said:
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework
Click to expand...
Click to collapse
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.
gregbradley said:
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.
Click to expand...
Click to collapse
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained
Rycon33 said:
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained
Click to expand...
Click to collapse
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.
Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app
gregbradley said:
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.
Click to expand...
Click to collapse
asterix005 said:
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app
Click to expand...
Click to collapse
ok mates, thank you very much, I managed to de-odexed my stock ROM:good:
This is what I did. Using flashtool, I dumped my system.sin file to get a ext4 file. Then I open it with ext4 reader and extracted the contents. I then placed it in a folder called 'system' and proceed with the android kitchen.
Humans have evolved to be smarter, but there's one thing we can't get rid off. It's human stupidity.
If you still want to deodex playstationcertified.odex rename it to com.playstation.playstationcertified.odex.
That did the trick for me in earlier firmware versions.
Sent from my phone using XDA Premium
i try many times but it's all show this
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
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67
lucky92 said:
i try many times but it's all show this
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
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67
Click to expand...
Click to collapse
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?
gregbradley said:
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?
Click to expand...
Click to collapse
i tried extract thee system.sin into ext4 and rename it to sysmtem.img but no luck
update: after re-dump system.sin and press countinue, it's seem ok, maybe my fault.
Thank you anyway :laugh:
Sorry but I have another question, after i make a flashable zip and flash through CWM, it always stuck at Sony logo, any idea ?
Hello guys, I've been struggling since two and a half hours now to unpack boot.img taken from cm10.1 zip (get.cm). I have an error about the magic header, here it is.
Code:
Android Magic not found in boot.img. Giving up.
Fyi, I need to unpack/repack the boot image to change the bootlogo and kernel.
I've tried with any tool available (dsixda kitchen, championswimmer kernel kitchen, simple mkbootimg or unmkbootimg, xperia boot tools and more), no results. Anyone please?
Try asking in the question and answer section, that may help
Sent from the luxury of my tent
That's actually a kernel.elf, not boot.img Rename it to kernel.elf, and use the kernel kitchen to extract it's contents.
..
NuriJ said:
That's actually a kernel.elf, not boot.img Rename it to kernel.elf, and use the kernel kitchen to extract it's contents.
..
Click to expand...
Click to collapse
Thank you man, you're a lifesaver. It works.
NuriJ said:
That's actually a kernel.elf, not boot.img Rename it to kernel.elf, and use the kernel kitchen to extract it's contents.
..
Click to expand...
Click to collapse
Hi.. I found this dead thread when i googled for the same thing that OP also had,, I managed to unpack the kernel's boot.img by renaming it to kernel.elf.. I have to edit init,rc file in order to get bootclasspath lines from a cm10 fxp kernel and put it in my port ROM's init.rc and replace the bootclasspath.. But i never found init.rc file anywhere, there is an init file which doesn't have a bootclasspath but only PATH.. Can u help me with this?
tOrNadO_007™ said:
Hi.. I found this dead thread when i googled for the same thing that OP also had,, I managed to unpack the kernel's boot.img by renaming it to kernel.elf.. I have to edit init,rc file in order to get bootclasspath lines from a cm10 fxp kernel and put it in my port ROM's init.rc and replace the bootclasspath.. But i never found init.rc file anywhere, there is an init file which doesn't have a bootclasspath but only PATH.. Can u help me with this?
Click to expand...
Click to collapse
Are you looking in ramdisk?
NuriJ said:
Are you looking in ramdisk?
Click to expand...
Click to collapse
Yes.. I did that too.. Unfortunately all the methods didn't work.. One simple method worked though.. Change the permissions of all the unpacked files and mount the ramdisk.img and then extract it and change contents of any file of your choice and then repack it.. It works like a charm..
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)